LMDE BREAKAGES - (Tracking SID!) -{CLOSED}

[zerozero]

They were clearly using a 32bit calendar.

it's explained then feel lot safer now

[cwwgateway]

I realized that the first time I tried Sid was after the freeze, so I've never experienced a really unstable moment. I have to say that both Testing and Sid aren't changing much - I'm trying to resist the urge to apt-pin newer stuff from experimental.

When Testing isn't frozen, do Sid kernels move faster? I understand Debian committed to the 3.2 kernel for wheezy, but I'm curious how quickly kernels (and anything, really) move in Sid when testing isn't frozen. I guess it doesn't really matter if you use Liquorix/Siduction/Aptosid kernels.

[zerozero]

cww,
it moves don't worry about that
the question with the deep-freeze is that it lasts too long (+/- 6 months is a normal release lifetime) and we forget how it was/get used to this calm.

in the last cycle the kernel froze at 2.6.32 and reopen at .38 and we were pretty up to date until the freeze at 3.2 and we are already at 3.6.9-1 in experimental (meaning that the next update in testing end fev/beg march will be a big jump )

[jackmetal]

That 'is' going to be a pretty big jump. I've been thinking about moving to one of the aforementioned kernels (Liquorix/Siduction/Aptosid) recently. Maybe now would be a good time to look into it. It seems that Liquorix gets a good bit of love around here; would that tend to be the most recommended kernel to go with or are there some others I should look into?

cww,
in the last cycle the kernel froze at 2.6.32 and reopen at .38 and we were pretty up to date until the freeze at 3.2 and we are already at 3.6.9-1 in experimental (meaning that the next update in testing end fev/beg march will be a big jump )

[zerozero]

i can only recommend (read only use) the debian kernels and liquorix.
have no experience with the others.
the ones i use work well (i had a few issues with liquorix in the past but now we are in tune )

[GeneC]

...............I think i see the issue with the Mayans. They were clearly using a 32bit calendar................

Hi Greg

Can 128 bit be far away.....

[GregE]

would that tend to be the most recommended kernel to go with or are there some others I should look into?

Just my usage. I run 3.6.9-1 from experimental and it is good. I have run Liquorix and had no issues with the kernel, but I have issues with the Liquorix repository. The problem is when you use multi-arch wine, the Liquorix repo has a 64bit packaged version of wine that will wreck your multi-arch system unless you are careful to use pinning or turn the repo on and off as you update kernels. If you do not use wine then that is not an issue.

It can be of benefit to run newer xorg and video driver versions with newer kernels and they too can be obtained from experimental. But this is not necessary, I would only do that if you have a need to solve a specific problem.

Finally, there can be issues with compiler versions. There is a default version on your system and you need to run a matching kernel (compiled with the correct compiler version) otherwise you run into all sorts of issues - eg modules not compliling. The good news is that as long as you keep one copy of 3.2 installed as a fallback you cannot get into too much trouble.

Code: Select all

gcc --version

So my mixed Sid/Experimental system sits at these versions at the moment.

gcc (Debian 4.7.2-14) 4.7.2

And experimental kernel SMP Debian 3.6.9-1~experimental.1 x86_64 GNU/Linux

[Viking78]

Haha 32-bit mayan-calendar... Sorry for commenting on off-topics, but for the record it should be known that the Mayans used a 13moon calendar, each month 29 days. Actually much better than ours, cause they didn't have to throw in a day extra in february every 4 years, their calendar simply followed the new/full moon-cycle in Nature. They also had an amazing way to add numbers and other maths. Also, they have never said the word doomsday, it's the media who have used it. I also knew religions love to use it, holy-wood too. But the Mayans believe in time-cycles, and all of their 18-19 calendars have to be considered as wheels, so when a cycle ends, a new one starts. Just like our calendar, no one believe the world would end just because the last date in the back are december 31st? But it was a funny comment, just like these http://www.dimension1111.com/2012-humor.html

[jackmetal]

GregE (and zerozero), Thanks for the kernel tips and heads-up on a couple problems to watch for. For now, I think I'll stick with the debian kernel (probably experimental) on my main machines and try out Liqourix (and maybe others) on some of my VM's for testing.

Thanks again!

would that tend to be the most recommended kernel to go with or are there some others I should look into?

Just my usage. I run 3.6.9-1 from experimental and it is good. I have run Liquorix and had no issues with the kernel, but I have issues with the Liquorix repository. The problem is when you use multi-arch wine, the Liquorix repo has a 64bit packaged version of wine that will wreck your multi-arch system unless you are careful to use pinning or turn the repo on and off as you update kernels. If you do not use wine then that is not an issue.

It can be of benefit to run newer xorg and video driver versions with newer kernels and they too can be obtained from experimental. But this is not necessary, I would only do that if you have a need to solve a specific problem.

Finally, there can be issues with compiler versions. There is a default version on your system and you need to run a matching kernel (compiled with the correct compiler version) otherwise you run into all sorts of issues - eg modules not compliling. The good news is that as long as you keep one copy of 3.2 installed as a fallback you cannot get into too much trouble.

Code: Select all

gcc --version

So my mixed Sid/Experimental system sits at these versions at the moment.

gcc (Debian 4.7.2-14) 4.7.2

And experimental kernel SMP Debian 3.6.9-1~experimental.1 x86_64 GNU/Linux

[Brian49]

I'm running Aptosid kernel 3.7 at the moment, and it works fine. The Liquorix kernels also work well, but I don't like the amount of hard-drive space they take up (about 30Mb more than other flavours), I believe due to the inclusion of many more drivers and filesystems.

[autocrosser]

Anyone seen a problem with the libfreetype6 update within the last couple of days? I installed a SSD on Thursday & everything was great until I rebooted today...I had kept the harddrive that I cloned from & thru trial/n/error settled on the libfreetype6 update as causing a bork to GDM.....

Anyone else updated to 2.4.9-1.1 (unstable)?

[karashata]

I noticed last night when I got home and booted my computer after yesterday's update that GDM wouldn't start, nor could I manually start X...

I wonder if that was the package responsible then... I'll get back to you in a moment and let you know what I find out...

EDIT: Apparently that's not the right package, at least on my system. Logging out immediately showed the issue, downgrading back to 2.4.9-1 from Testing did not fix it, nor did rebooting after downgrading.

I'm going through my update history to try to find the package breaking GDM and Xorg on my system, I'll get back to you again once I've figured it out...

[cwwgateway]

On my aptosid Xfce and siduction RazorQT installs (both using LightDM) everything works, so I think this is GDM specific. Neither distros have added a patched libreetype6 to their repos, so it is the default one from sid. I wonder if it's graphics driver related?

[GeneC]

Code: Select all

gene@zordon:~$ apt-cache policy libfreetype6
libfreetype6:
  Installed: 2.4.9-1.1
  Candidate: 2.4.9-1.1
  Version table:
 *** 2.4.9-1.1 0
        700 http://http.us.debian.org/debian/ unstable/main amd64 Packages
        100 /var/lib/dpkg/status

No problem here using Light DM...
Nvidia 313.09

[zerozero]

Code: Select all

zerozero@debian:~$ apt-cache policy libfreetype6 gdm
libfreetype6:
  Installed: 2.4.9-1.1
  Candidate: 2.4.9-1.1
  Version table:
 *** 2.4.9-1.1 0
        500 http://ftp.debian.org/debian/ unstable/main amd64 Packages
        100 /var/lib/dpkg/status
gdm:
  Installed: 2.20.11-4
  Candidate: 2.20.11-4
  Version table:
 *** 2.20.11-4 0
        100 /var/lib/dpkg/status


no problem here either (not using any of those fancy DM though)

[karashata]

Anyone able to give me a list of just the updates from the 29th? Unfortunately my list is full of updates since a couple weeks ago (had to revert to an old backup), and it was working fine until yesterday's updates, so it would be nice to narrow the list down to only those packages from yesterday (the rest should all be safe...)

[GeneC]

Dec 29th Updates

Code: Select all

Commit Log for Sat Dec 29 13:38:24 2012


Upgraded the following packages:
cups (1.5.3-2.11) to 1.5.3-2.11.1
cups-client (1.5.3-2.11) to 1.5.3-2.11.1
cups-common (1.5.3-2.11) to 1.5.3-2.11.1
cups-ppdc (1.5.3-2.11) to 1.5.3-2.11.1
libcups2 (1.5.3-2.11) to 1.5.3-2.11.1
libcupscgi1 (1.5.3-2.11) to 1.5.3-2.11.1
libcupsdriver1 (1.5.3-2.11) to 1.5.3-2.11.1
libcupsimage2 (1.5.3-2.11) to 1.5.3-2.11.1
libcupsmime1 (1.5.3-2.11) to 1.5.3-2.11.1
libcupsppdc1 (1.5.3-2.11) to 1.5.3-2.11.1
libnspr4 (2:4.9.4-1) to 2:4.9.4-2
libnspr4-0d (2:4.9.4-1) to 2:4.9.4-2
libfreetype6 (2.4.9-1) to 2.4.9-1.1
libfreetype6-dev (2.4.9-1) to 2.4.9-1.1


Dec 28

Code: Select all

Commit Log for Fri Dec 28 19:04:17 2012


Upgraded the following packages:
grub-common (1.99-23.1) to 1.99-24
grub-pc (1.99-23.1) to 1.99-24
grub-pc-bin (1.99-23.1) to 1.99-24
grub2-common (1.99-23.1) to 1.99-24
cups (1.5.3-2.10) to 1.5.3-2.11
cups-client (1.5.3-2.10) to 1.5.3-2.11
cups-common (1.5.3-2.10) to 1.5.3-2.11
cups-ppdc (1.5.3-2.10) to 1.5.3-2.11
libcups2 (1.5.3-2.10) to 1.5.3-2.11
libcupscgi1 (1.5.3-2.10) to 1.5.3-2.11
libcupsdriver1 (1.5.3-2.10) to 1.5.3-2.11
libcupsimage2 (1.5.3-2.10) to 1.5.3-2.11
libcupsmime1 (1.5.3-2.10) to 1.5.3-2.11
libcupsppdc1 (1.5.3-2.10) to 1.5.3-2.11


[zerozero]

i updated on the 26th and today

Code: Select all

Start-Date: 2012-12-26  21:42:17
Commandline: apt-get dist-upgrade
Install: linux-image-3.7.0-1.dmz.1-liquorix-amd64:amd64 (3.7.0-1, automatic), linux-headers-3.7.0-1.dmz.1-liquorix-amd64:amd64 (3.7.0-1, automatic)
Upgrade: console-setup:amd64 (1.88, 1.89), console-setup-linux:amd64 (1.88, 1.89), linux-image-liquorix-amd64:amd64 (3.6.0-11, 3.7.0-1), xkb-data:amd64 (2.5.1-2.1, 2.5.1-3), debconf-i18n:amd64 (1.5.48, 1.5.49), keyboard-configuration:amd64 (1.88, 1.89), linux-headers-liquorix-amd64:amd64 (3.6.0-11, 3.7.0-1), debconf:amd64 (1.5.48, 1.5.49), libsqlite3-0:amd64 (3.7.15-1, 3.7.15.1-1)
End-Date: 2012-12-26  21:44:13


Code: Select all

Start-Date: 2012-12-31  00:09:23
Commandline: apt-get dist-upgrade
Install: linux-image-3.7.0-1.dmz.4-liquorix-amd64:amd64 (3.7.0-3, automatic), linux-headers-3.7.0-1.dmz.4-liquorix-amd64:amd64 (3.7.0-3, automatic)
Upgrade: libc-bin:amd64 (2.13-37, 2.13-38), libcupsppdc1:amd64 (1.5.3-2.10, 1.5.3-2.12), libcupsimage2:amd64 (1.5.3-2.10, 1.5.3-2.12), libcupscgi1:amd64 (1.5.3-2.10, 1.5.3-2.12), libcupsdriver1:amd64 (1.5.3-2.10, 1.5.3-2.12), libtie-ixhash-perl:amd64 (1.21-2, 1.22-1), cups-client:amd64 (1.5.3-2.10, 1.5.3-2.12), libnspr4-0d:amd64 (4.9.4-1, 4.9.4-2), linux-image-liquorix-amd64:amd64 (3.7.0-1, 3.7.0-3), libfreetype6:amd64 (2.4.9-1, 2.4.9-1.1), libfreetype6:i386 (2.4.9-1, 2.4.9-1.1), grub-pc:amd64 (1.99-23.1, 1.99-25), libc6-i386:amd64 (2.13-37, 2.13-38), cups-ppdc:amd64 (1.5.3-2.10, 1.5.3-2.12), libc6-i686:i386 (2.13-37, 2.13-38), locales:amd64 (2.13-37, 2.13-38), cups-common:amd64 (1.5.3-2.10, 1.5.3-2.12), libcups2:amd64 (1.5.3-2.10, 1.5.3-2.12), multiarch-support:amd64 (2.13-37, 2.13-38), cups:amd64 (1.5.3-2.10, 1.5.3-2.12), libnspr4:amd64 (4.9.4-1, 4.9.4-2), libfreetype6-dev:amd64 (2.4.9-1, 2.4.9-1.1), linux-headers-liquorix-amd64:amd64 (3.7.0-1, 3.7.0-3), grub-pc-bin:amd64 (1.99-23.1, 1.99-25), cups-bsd:amd64 (1.5.3-2.10, 1.5.3-2.12), libc6-dev:amd64 (2.13-37, 2.13-38), libgc1c2:amd64 (7.1-9, 7.1-9.1), grub-common:amd64 (1.99-23.1, 1.99-25), grub2-common:amd64 (1.99-23.1, 1.99-25), libcupsmime1:amd64 (1.5.3-2.10, 1.5.3-2.12), libc-dev-bin:amd64 (2.13-37, 2.13-38), libc6:amd64 (2.13-37, 2.13-38), libc6:i386 (2.13-37, 2.13-38)
End-Date: 2012-12-31  00:12:04
zerozero@debian:~$


[karashata]

@GeneC: Wow, that's... shorter than I expected.

The only thing on that list that apparently caused problems for one person here so far is libfreetype6, but downgrading that didn't fix the issue I'm having (which seems similar, but apparently must be caused by something else...)

I guess I'm going to have to revert to my backup again after all and try updating everything again (possibly avoiding that package, just in case) and see if my system still boots properly.

I can only think of one other thing I've done today that I also did yesterday and that was install the Steam for Linux beta client after fixing a couple dependencies in the package to match Debian package versions, it's possible that some of the dependencies it pulled in, while appearing to install cleanly enough, conflict with other packages on my system and cause it to fail to launch GDM and GNOME Shell after logging out or rebooting... I'll do the updates before bothering with that again and make sure everything still works properly, and if so, I may have to skip trying to use the Steam client on Debian until a proper package is built for it.

[GeneC]

I update daily..

How about todays updates??

Code: Select all

Commit Log for Sun Dec 30 19:21:23 2012


Upgraded the following packages:
cups (1.5.3-2.11.1) to 1.5.3-2.12
cups-client (1.5.3-2.11.1) to 1.5.3-2.12
cups-common (1.5.3-2.11.1) to 1.5.3-2.12
cups-ppdc (1.5.3-2.11.1) to 1.5.3-2.12
exo-utils (0.10.1-1) to 0.10.2-1
libc-bin (2.13-37) to 2.13-38
libc-dev-bin (2.13-37) to 2.13-38
libc6 (2.13-37) to 2.13-38
libc6-dev (2.13-37) to 2.13-38
libcups2 (1.5.3-2.11.1) to 1.5.3-2.12
libcupscgi1 (1.5.3-2.11.1) to 1.5.3-2.12
libcupsdriver1 (1.5.3-2.11.1) to 1.5.3-2.12
libcupsimage2 (1.5.3-2.11.1) to 1.5.3-2.12
libcupsmime1 (1.5.3-2.11.1) to 1.5.3-2.12
libcupsppdc1 (1.5.3-2.11.1) to 1.5.3-2.12
libexo-1-0 (0.10.1-1) to 0.10.2-1
libexo-common (0.10.1-1) to 0.10.2-1
libexo-helpers (0.10.1-1) to 0.10.2-1
libthunarx-2-0 (1.6.1-1) to 1.6.2-1
libtie-ixhash-perl (1.21-2) to 1.22-1
locales (2.13-37) to 2.13-38
multiarch-support (2.13-37) to 2.13-38
thunar (1.6.1-1) to 1.6.2-1
thunar-data (1.6.1-1) to 1.6.2-1
grub-common (1.99-24) to 1.99-25
grub-pc (1.99-24) to 1.99-25
grub-pc-bin (1.99-24) to 1.99-25
grub2-common (1.99-24) to 1.99-25