

zerozero wrote:@kmb42vt,
yes, i can confirm that: if i try to install hunspell, synaptic wants to remove thunderbird, even if i say yes, after when i want to install thunderbird back, hunspell gets removedso at least atm both it's a no-go


OpenOffice: http://wiki.services.openoffice.org/wiki/Dictionaries (but only download MySpell spelling dictionaries—not Hunspell dictionaries for OpenOffice 2.0.2 onwards)



viking777 wrote:As someone who doesn't use either OO or LO I feel a little bit detached from the present problems, but they really don't present any mystery. This is what the mozillazine.org/dictionaries page says:OpenOffice: http://wiki.services.openoffice.org/wiki/Dictionaries (but only download MySpell spelling dictionaries—not Hunspell dictionaries for OpenOffice 2.0.2 onwards)
OK so it doesn't mention LO but maybe it has been updated since that was released. The point is that it makes it quite clear that hunspell is not compatible.


gorade wrote:Running LMDE 64-bit I ran into trouble trying to use Mintupdater and thus changed to console: sudo apt-get update and sudo apt-get dist-upgrade. That seemed to work fine until I installed AMD Catalyst™ 11.2 Proprietary Linux x86 Display Driver revnr: 11.2 rev date.2/15/2011. The driver seemingly worked fine and I could reboot without problems, but...
then I ran update/upgrade and then Gnome didn't start. It stopped with a blank screen and no respons to key board or mouse.
When I changed to fglrx from repos it worked again.
Thus I infere there is something incompatible between the non free original version and some upgraded program in LMDE. I am not savvy enough to guess what, but I will keep away from the proprietary ATI Catalyst.

kmb42vt wrote:
Thanks for the info. It's strange though as it doesn't explain why Hunspell appears to be compatible with Thunderbird on LM 10 then or at least in my case it is and my LM 10 install is pretty much standard. Or perhaps it isn't? I keep forgetting everything I do to my Mint installs.






zerozero wrote:@mads @gorade there's already, besides your reports, another one from rdonnelly viewtopic.php?f=141&t=68729 on the same issue;
i assume that the problem arises from using the proprietary driver with the AMD graphic cards? is this correct?







Commit Log for Sun Mar 20 10:45:56 2011
Upgraded the following packages:
firmware-linux-free (2.6.32-30) to 2.6.32-31
gstreamer0.10-lame (0.10.17-0.0) to 0.10.17-0.2
libdate-manip-perl (6.21-1) to 6.22-1
libmailtools-perl (2.06-1) to 2.07-1
libnfsidmap2 (0.23-2) to 0.24-1
libpango1.0-0 (1.28.3-1+squeeze1) to 1.28.3-1+squeeze2
libpango1.0-common (1.28.3-1+squeeze1) to 1.28.3-1+squeeze2
libpango1.0-dev (1.28.3-1+squeeze1) to 1.28.3-1+squeeze2
libquicktime1 (3:1.2.2-0.3squeeze1) to 3:1.2.2-0.4
libraw1394-11 (2.0.6-1) to 2.0.7-1
libsmbclient (2:3.5.6~dfsg-5) to 2:3.5.8~dfsg-1
libwbclient0 (2:3.5.6~dfsg-5) to 2:3.5.8~dfsg-1
linux-base (2.6.32-30) to 2.6.32-31
linux-headers-2.6.32-5-686 (2.6.32-30) to 2.6.32-31
linux-headers-2.6.32-5-common (2.6.32-30) to 2.6.32-31
linux-image-2.6.32-5-686 (2.6.32-30) to 2.6.32-31
linux-libc-dev (2.6.32-30) to 2.6.32-31
python (2.6.6-3+squeeze5) to 2.6.6-3+squeeze6
python-gdbm (2.6.6-1) to 2.7.1-1
python-minimal (2.6.6-3+squeeze5) to 2.6.6-3+squeeze6
samba (2:3.5.6~dfsg-5) to 2:3.5.8~dfsg-1
samba-common (2:3.5.6~dfsg-5) to 2:3.5.8~dfsg-1
samba-common-bin (2:3.5.6~dfsg-5) to 2:3.5.8~dfsg-1
smbclient (2:3.5.6~dfsg-5) to 2:3.5.8~dfsg-1
xserver-common (2:1.7.7-11) to 2:1.7.7-13
xserver-xorg-core (2:1.7.7-11) to 2:1.7.7-13
xserver-xorg-video-intel (2:2.13.0-5) to 2:2.13.0-6
Commit Log for Mon Mar 21 10:13:36 2011
Upgraded the following packages:
avahi-daemon (0.6.28-4) to 0.6.29-1
gthumb (3:2.12.2-1) to 3:2.13.1-1
gthumb-data (3:2.12.2-1) to 3:2.13.1-1
libavahi-client3 (0.6.28-4) to 0.6.29-1
libavahi-common-data (0.6.28-4) to 0.6.29-1
libavahi-common3 (0.6.28-4) to 0.6.29-1
libavahi-core7 (0.6.28-4) to 0.6.29-1
libavahi-glib1 (0.6.28-4) to 0.6.29-1
libavahi-gobject0 (0.6.28-4) to 0.6.29-1
libavahi-ui0 (0.6.28-4) to 0.6.29-1
libgadu3 (1:1.10.0+r1059-1) to 1:1.10.1-1
libxt6 (1:1.0.9-2) to 1:1.1.1-1
Commit Log for Wed Mar 23 11:32:34 2011
Upgraded the following packages:
acpi-support-base (0.138-7) to 0.138-8
acpid (1:2.0.8-1) to 1:2.0.8-3
google-chrome-beta (10.0.648.151-r78498) to 11.0.696.16-r78799
libglib2.0-0 (2.28.1-1+b1) to 2.28.2-1
libglib2.0-bin (2.28.1-1+b1) to 2.28.2-1
libglib2.0-data (2.28.1-1) to 2.28.2-1
libglib2.0-dev (2.28.1-1+b1) to 2.28.2-1
libjs-prototype (1.6.1-1) to 1.7.0-2
live-config (2.0.15-1) to 3.0~a17-1
live-config-sysvinit (2.0.15-1) to 3.0~a17-1
python-clamav (0.4.1-4) to 0.4.1-5
python-pyclamav (0.4.1-4) to 0.4.1-5
udisks (1.0.2-3) to 1.0.2-4
Installed the following packages:
debian-installer-launcher (5)
kexec-tools (1:2.0.1-4)
live-tools (3.0~a3-1)
kexec allows one to load another kernel from the currently running Linux kernel. Normally one would load a kernel, and possibly an initial ramdisk, into the currently running kernel using kexec and then initiate a warm reboot by executing kexec again with appropriate option.



viking777 wrote:...I don't use a splashscreen so I can read it happening on screen- just about - I can't find it in any log file though...
gksudo gedit /etc/default/bootlogdBOOTLOGD_ENABLE=Yes



zerozero wrote:Atm i'm travelling, and only have my laptop with me (which is only running lmde-sid) but this bug with kexec-tools is also present in sid, rebooting to get to grub only gets us to login screen again.
Didn't have time to debug this, first because as i said, i'm travelling and because this is a single os comp



I take it this package isn't needed?

Is there any reason for me to reinstall and have this running?



mads wrote:viking777 wrote:...I don't use a splashscreen so I can read it happening on screen- just about - I can't find it in any log file though...
Boot logging is disabled by default. To enable, run
- Code: Select all
gksudo gedit /etc/default/bootlogd
There are only two lines there. Replace 'No' with 'Yes', like this:
- Code: Select all
BOOTLOGD_ENABLE=Yes
Next time you boot, you will see the log file "/var/log/boot"




Users browsing this forum: No registered users and 6 guests