LMDE BREAKAGES - tracking TESTING

[yoav]

Thanks!

[narendra.d]

I needs some help.

My system is triple boot with LMDE (tracking Testing and installed ages ago) along with Crunchbang Waldorf and WinXP.

The issue is with the time setting going haywire every so often almost on every reboot. The RTC clock is set to UTC and the WinXP has its registry edited to read RTC as UTC. Auto update of time on WinXP is disabled. My time zone is Asia/Kolkatta. Crunchbang displays the time right always and does have ntp installed.

Its LMDE that is displaying the time wrong at almost every reboot. And writes the wrong time to the RTC. I have ntp installed, so the time corrects itself when connected to the net. I don't understand where the system is going wrong. I have tried dpkg-reconfigure tzdata, hwclock --systohc --utc and tried deleting the /etc/adjtime file as well, but to no effect.

My LMDE had most Mint stuff removed quite a while back and then some were reinstalled including mint-update and the pin priority in the /etc/preferences file was 500 for both mint and debian repos. Now everything is as per the original setting as it were meant to be for LMDE tracking Debian Testing. I use Gnome 3 and Gnome Classic if it matters, but have openbox installed as well but rarely use.. Are there multiple packages that are controlling time setting in my system because of the above.

How do i correct this? I would like to correct this in LMDE as thats where any goof up from my side might have happened and also because its the primary OS.. Is it possible other OS's are responsible? If yes, what to do and where?

[mockturtl]

apt-listbugs catches #689519

Subject: libapt-pkg4.12: SIGSEGV when used by apt-get or aptitude
Date: Wed, 3 Oct 2012 15:55:48 +0200

I don't know about you, but I don't like "segfault" and "APT" in the same sentence.

Code: Select all

$ sudo aptitude hold libapt-pkg4.12

The current version has been running a few days on my other laptop, and I haven't noticed trouble, so maybe it's nothing.

[zerozero]

i already have the bugger (but it seems that is behaving well so far)

Code: Select all

zerozero@deb-kde ~/Documents $ sudo apt-get install kde-icons-crystal
[sudo] password for zerozero:
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libcrypto++9 librados2 librbd1
Use 'apt-get autoremove' to remove them.
Recommended packages:
  kdebase
The following NEW packages will be installed:
  kde-icons-crystal
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 1,558 kB of archives.
After this operation, 3,490 kB of additional disk space will be used.
Get:1 http://ftp.debian.org/debian/ testing/main kde-icons-crystal all 3.7-3 [1,558 kB]
Fetched 1,558 kB in 1s (813 kB/s)             
Selecting previously unselected package kde-icons-crystal.
(Reading database ... 216943 files and directories currently installed.)
Unpacking kde-icons-crystal (from .../kde-icons-crystal_3.7-3_all.deb) ...
Setting up kde-icons-crystal (3.7-3) ...
zerozero@deb-kde ~/Documents $ apt policy libapt-pkg4.12
libapt-pkg4.12:
  Installed: 0.9.7.5
  Candidate: 0.9.7.5
  Version table:
 *** 0.9.7.5 0
        500 http://ftp.debian.org/debian/ testing/main amd64 Packages
        100 /var/lib/dpkg/status


[jackmetal]

Narendra.d, I've actually noticed the same issue. I boot into Windows 7 and the time is correct, I boot back into LMDE and the time is off (by 4 hours for me, every time - my TZ is EST). Luckily, I don't boot into Windows very often, so I don't really think about it but your post reminded me.

I'd like to resolve it too. Hopefully one of the LMDE gurus can point us in a direction to help solve it. I'll let you know if I run across anything.

I needs some help.

My system is triple boot with LMDE (tracking Testing and installed ages ago) along with Crunchbang Waldorf and WinXP.

The issue is with the time setting going haywire every so often almost on every reboot. The RTC clock is set to UTC and the WinXP has its registry edited to read RTC as UTC. Auto update of time on WinXP is disabled. My time zone is Asia/Kolkatta. Crunchbang displays the time right always and does have ntp installed.

Its LMDE that is displaying the time wrong at almost every reboot. And writes the wrong time to the RTC. I have ntp installed, so the time corrects itself when connected to the net. I don't understand where the system is going wrong. I have tried dpkg-reconfigure tzdata, hwclock --systohc --utc and tried deleting the /etc/adjtime file as well, but to no effect.

My LMDE had most Mint stuff removed quite a while back and then some were reinstalled including mint-update and the pin priority in the /etc/preferences file was 500 for both mint and debian repos. Now everything is as per the original setting as it were meant to be for LMDE tracking Debian Testing. I use Gnome 3 and Gnome Classic if it matters, but have openbox installed as well but rarely use.. Are there multiple packages that are controlling time setting in my system because of the above.

How do i correct this? I would like to correct this in LMDE as thats where any goof up from my side might have happened and also because its the primary OS.. Is it possible other OS's are responsible? If yes, what to do and where?

[mockturtl]

Narendra.d, I've actually noticed the same issue. I boot into Windows 7 and the time is correct, I boot back into LMDE and the time is off (by 4 hours for me, every time - my TZ is EST). Luckily, I don't boot into Windows very often, so I don't really think about it but your post reminded me.

I don't quite remember how I fixed it. I fiddled with the BIOS clock, changing from local time to GMT, or the other way around.

Installing ntp and opening port 123 in the firewall fixed my GNOME panel time.

With Windows displaying the wrong time, a manual NTP sync worked, so I set a task to trigger it at startup.

[voss749]

Qapla'! It turned out the phrase that paid was

Code: Select all

sudo apt-get install nvidia-kernel-dkms nvidia-glx build-essential nvidia-settings nvidia-xconfig --reinstall

I can't tell y'all how nice it is to be back up and running with the GUI.

Note to self: Stop upgrading with sudo apt-fast dist-upgrade. Apt-get seems to work more reliably, especially with the testing repos.

THANK YOU! You saved my ass! I had the same problem. Im guessing for future reference to reinstall the nvidia drivers before I reboot after any new kernel install.

[narendra.d]

@jackmetal and @mockturti: Thanks for responding.
My BIOS clock is already set to UTC. Both LMDE and Crunchbang have ntp installed, but I only can see LMDE writing the time to the BIOS clock during shutdown, and still get the time wrong at every boot. The time is off by varying degrees, from more than 5 1/2 hours (I am +5 1/2 hts from UTC) to about a Hour and half. I am thinking its LMDE that needs to be fixed. I did try deleting the /etc/adjtime file as well, thinking that it might be the cause, but didnt help.

Any more help from the experts on this forum please.

[BostonPeng]

Qapla'! It turned out the phrase that paid was

Code: Select all

sudo apt-get install nvidia-kernel-dkms nvidia-glx build-essential nvidia-settings nvidia-xconfig --reinstall

I can't tell y'all how nice it is to be back up and running with the GUI.

Note to self: Stop upgrading with sudo apt-fast dist-upgrade. Apt-get seems to work more reliably, especially with the testing repos.

THANK YOU! You saved my ass! I had the same problem. Im guessing for future reference to reinstall the nvidia drivers before I reboot after any new kernel install.

That's a lesson I learned the hard way. Glad I could help you solve your issue.

[squeezy]

THANK YOU! You saved my ass! I had the same problem. Im guessing for future reference to reinstall the nvidia drivers before I reboot after any new kernel install.

Now that you've got the driver installed using dkms, it'll be rebuilt automatically on kernel upgrades. dkms = Dynamic Kernel Module Support

[voss749]

THANK YOU! You saved my ass! I had the same problem. Im guessing for future reference to reinstall the nvidia drivers before I reboot after any new kernel install.

Now that you've got the driver installed using dkms, it'll be rebuilt automatically on kernel upgrades. dkms = Dynamic Kernel Module Support

I had DKMS, I still had to rerun it.

[BostonPeng]

THANK YOU! You saved my ass! I had the same problem. Im guessing for future reference to reinstall the nvidia drivers before I reboot after any new kernel install.

Now that you've got the driver installed using dkms, it'll be rebuilt automatically on kernel upgrades. dkms = Dynamic Kernel Module Support

I had DKMS, I still had to rerun it.

I had the same issue some time back, which is why I make a point to always manually update the drivers after updating my kernel and before rebooting.

[Chris M]

@jackmetal and @mockturti: Thanks for responding.
My BIOS clock is already set to UTC. Both LMDE and Crunchbang have ntp installed, but I only can see LMDE writing the time to the BIOS clock during shutdown, and still get the time wrong at every boot. The time is off by varying degrees, from more than 5 1/2 hours (I am +5 1/2 hts from UTC) to about a Hour and half. I am thinking its LMDE that needs to be fixed. I did try deleting the /etc/adjtime file as well, thinking that it might be the cause, but didnt help.

Any more help from the experts on this forum please.

I'm not sure if this excellent thread got buried or not, but this was a real nice one: Hacking LMDE

Wait, something's wrong with the clock. If you use another OS like Windows or Ubuntu, setting hardware clock to UTC is not a good idea, so:

Code: Select all

sed -r 's/^UTC=yes/UTC=no/ig' /etc/default/rcS | sudo tee /etc/default/rcS
sudo apt-get install ntp


This will disable UTC time and enable synchronizing with ntp servers. Set the time from panel. Reboot... WAIT, not yet!

Reboot is pretty broken now, it just reloads the kernel, skipping GRUB, so...

Code: Select all

sudo apt-get remove kexec-tools


...should fix the problem. Now we can

Code: Select all

sudo reboot


It's been a while since the above was posted, but that solution should still be good.

[squeezy]

I had DKMS, I still had to rerun it.

Hmmm, never had a problem with DKMS working properly for me.

[squeezy]

I'm not sure if this excellent thread got buried or not, but this was a real nice one: Hacking LMDE

Wait, something's wrong with the clock. If you use another OS like Windows or Ubuntu, setting hardware clock to UTC is not a good idea, so:

Code: Select all

sed -r 's/^UTC=yes/UTC=no/ig' /etc/default/rcS | sudo tee /etc/default/rcS


It's been a while since the above was posted, but that solution should still be good.

Setting UTC options in /etc/default/rcS was deprecated sometime ago. I don't know if it still works as a legacy setting. The current method for setting UTC is to edit /etc/adjtime and change the last line to read either UTC or LOCAL.

[narendra.d]

Setting UTC options in /etc/default/rcS was deprecated sometime ago. I don't know if it still works as a legacy setting. The current method for setting UTC is to edit /etc/adjtime and change the last line to read either UTC or LOCAL.

Thank You Chris M and squeezy. I know that time settings are now managed in /etc/adjtime. I do not know if putting anything in /etc/default/rcS will matter (just checked: there is nothing time related in rcS.).

I will go thru the post linked by Chris M and see if it makes sense to me and get back with any Q's or feedback.

Thanks once again.

[Chris M]

Setting UTC options in /etc/default/rcS was deprecated sometime ago. I don't know if it still works as a legacy setting. The current method for setting UTC is to edit /etc/adjtime and change the last line to read either UTC or LOCAL.

Thank You Chris M and squeezy. I know that time settings are now managed in /etc/adjtime. I do not know if putting anything in /etc/default/rcS will matter (just checked: there is nothing time related in rcS.).

I will go thru the post linked by Chris M and see if it makes sense to me and get back with any Q's or feedback.

Thanks once again.

Thanks squeezy for that info. My guess is that the old solution won't cut it since setting UTC options in /etc/default/rcS was deprecated. You could ask HTD via PM if he has another set of commands that can be run. Maybe its not needed and all you have to do is edit /etc/adjtime and re-boot. Don't know. Maybe squeezy can suggest something more robust. But good luck. It's been a while since I have fresh installed LMDE and had to deal with it.

[jackmetal]

I've edited my adjtime file a while back, but I haven't booted into Windows since then. I plan to boot into Windows sometime today to test. I'll let you know how it goes (hopefully that fixed it).

Now.....If I can just figure out why my battery is lasting half the time in LMDE as opposed to Windows, I'll be perfect.. In Windows my dual battery setup lasts 8-10 hours, in LMDE it's only last around 4.5... A real bummer, but I'm sure it's something to do with my particular laptop (HP 8460p), since I don't remember it happening with the old 8440p laptop.

Setting UTC options in /etc/default/rcS was deprecated sometime ago. I don't know if it still works as a legacy setting. The current method for setting UTC is to edit /etc/adjtime and change the last line to read either UTC or LOCAL.

Thank You Chris M and squeezy. I know that time settings are now managed in /etc/adjtime. I do not know if putting anything in /etc/default/rcS will matter (just checked: there is nothing time related in rcS.).

I will go thru the post linked by Chris M and see if it makes sense to me and get back with any Q's or feedback.

Thanks once again.

[lahirdenganselamat]

gdebi upgrade from 0.8.5 to 0.8.6 make gdebi un-usable

Code: Select all

aragorn@aragorn-1215b ~/Linux $ sudo gdebi-kde ia32-crossover_11.3.1-1_amd64.deb
Traceback (most recent call last):
  File "/usr/bin/gdebi-kde", line 67, in <module>
    help=unicode(_("Run non-interactive (dangerous!)"),"UTF-8"))
TypeError: decoding Unicode is not supported

Downgrade to 0.8.5 using gdebi from UP repo make it works again

[zerozero]

as you can see here http://www.mail-archive.com/debian-bugs ... 74765.html gdebi-gtk is not affected.
/joking.

tks for reporting it and we will see a fix sooner because of that

tbh i only now realized

Code: Select all

zerozero@deb-kde ~/Downloads $ sudo gdebi cinnamon-themes_2012.10.20_all.deb
[sudo] password for zerozero:
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Building data structures... Done
Building data structures... Done


Cinnamon themes
 A collection of the best themes available for Cinnamon.
Do you want to install the software package? [y/N]:N

zerozero@deb-kde ~/Downloads $ sudo gdebi-kde cinnamon-themes_2012.10.20_all.deb
Traceback (most recent call last):
  File "/usr/bin/gdebi-kde", line 67, in <module>
    help=unicode(_("Run non-interactive (dangerous!)"),"UTF-8"))
TypeError: decoding Unicode is not supported