Thanks for the heads up. I think I'll stop updating until the storm passeszerozero wrote:this is not a breakage per-se (at least not yet )
- as you all know (if following this topic closely) gnome 3.8 is coming to testing (not tomorrow but soon)
- when that happens, and if the present version of cinnamon is not updated to gain gnome 3.8 compatibility, cinnamon will break.
- it's probably a good idea to install a light DE ot WM alongside cinnamon for the "rainy days"
Upgrade Warnings: LMDE tracking TESTING [10-11-14]
Forum rules
LMDE 2 has reached end of support as of 1-1-2019
LMDE 2 has reached end of support as of 1-1-2019
Re: Upgrade Warnings: LMDE tracking TESTING [25-05-13]
-
- Level 4
- Posts: 357
- Joined: Fri Sep 17, 2010 9:55 pm
Re: Upgrade Warnings: LMDE tracking TESTING [25-05-13]
Just a heads up. Xfce 4.10.x is now in testing.
I've been running 4.10.x from Siduction for many months without incident. Install of 4.10.x from Debian testing went fine. Everything appears to be in working order.
I've been running 4.10.x from Siduction for many months without incident. Install of 4.10.x from Debian testing went fine. Everything appears to be in working order.
Re: Upgrade Warnings: LMDE tracking TESTING [25-05-13]
- Deluge crashes with python error if you try to remove a torrent.
- Xfce xkb-plugin will not let you define a hotkey to switch layouts, the option has disappeared.
- Xfce 4.10 screenlock broken. Xscreensaver daemon is not started.
Edit: It seems that Xfce 4.8 always started the screensaver, a bug that's fixed in 4.10. So I had to create an autostart entry for xscreensaver. http://bugzilla.xfce.org/show_bug.cgi?id=7826
- Xfce xkb-plugin will not let you define a hotkey to switch layouts, the option has disappeared.
- Xfce 4.10 screenlock broken. Xscreensaver daemon is not started.
Edit: It seems that Xfce 4.8 always started the screensaver, a bug that's fixed in 4.10. So I had to create an autostart entry for xscreensaver. http://bugzilla.xfce.org/show_bug.cgi?id=7826
Last edited by maxibuntu on Sat Jun 08, 2013 5:50 pm, edited 1 time in total.
Re: Upgrade Warnings: LMDE tracking TESTING [25-05-13]
Upgraded to Cinnamon 1.8.8+lmde and mdm 1.2.5+lmde . Previous problems with mdm and nemo are solved. Only problem seems to be a noticeable startup delay with the cinnamon panels loading on boot. Worth the upgrade though
Re: Upgrade Warnings: LMDE tracking TESTING [25-05-13]
Neat, I hadn't seen the upgrade was available.twelph wrote:Upgraded to Cinnamon 1.8.8+lmde and mdm 1.2.5+lmde . Previous problems with mdm and nemo are solved. Only problem seems to be a noticeable startup delay with the cinnamon panels loading on boot. Worth the upgrade though
Is there a better way to preview MDM themes than log in, choose one, and log out?
Re: Upgrade Warnings: LMDE tracking TESTING [25-05-13]
In a terminal --> mdm-theme-emulatormockturtl wrote: Is there a better way to preview MDM themes than log in, choose one, and log out?
And load the index.html file of the theme you want to try.
Is that me or there is still not a new kernel in testing ? I think the 3.2.0.4 is still the only one in testing. An I right ?
Re: Upgrade Warnings: LMDE tracking TESTING [25-05-13]
killer de bug wrote:Is that me or there is still not a new kernel in testing ? I think the 3.2.0.4 is still the only one in testing. An I right ?
Code: Select all
zerozero@home ~ $ uname -a
Linux home 3.2.0-4-amd64 #1 SMP Debian 3.2.41-2 x86_64 GNU/Linux
Re: Upgrade Warnings: LMDE tracking TESTING [25-05-13]
Oh right. My kernel is :
But 3.8.1 and 3.8.2 are in Sid since a few weeks and have not be pushed in testing. Why ?
3.9 is already there... Is there something I am missing ?
Code: Select all
emmanuel@manu-laptop ~ $ uname -a
Linux manu-laptop 3.2.0-4-amd64 #1 SMP Debian 3.2.32-1 x86_64 GNU/Linux
3.9 is already there... Is there something I am missing ?
Re: Upgrade Warnings: LMDE tracking TESTING [25-05-13]
[url=http://release.debian.org/migration/testing.pl?package=linux]Ben has some homework on his desk [/url]
Re: Upgrade Warnings: LMDE tracking TESTING [25-05-13]
ok. I didn't knew this website.
Looks like the next Kernel will be 3.9. Fine !
Looks like the next Kernel will be 3.9. Fine !
Re: Upgrade Warnings: LMDE tracking TESTING [25-05-13]
Neat, thanks. (For reference, themes are in /usr/share/mdm/html-themes/. [url=http://forums.linuxmint.com/viewtopic.php?f=25&t=126979]Thread here[/url].killer de bug wrote:In a terminal --> mdm-theme-emulatormockturtl wrote: Is there a better way to preview MDM themes than log in, choose one, and log out?
And load the index.html file of the theme you want to try.
Re: Upgrade Warnings: LMDE tracking TESTING [25-05-13]
Switched from lmde repo to pinned debian testing at a higher priority than mint repos, with unstable and experimental repos pinned at -10 so they only install if forced. when I did apt-get distupgrade, I got the errors pasted in below with the new kernels failing to install. To make that long story short, pango and plymouth conflicted, with pango updated to a higher version than plymouth allowed. this caused the kernels to not install. the workaround was to get the latest plymouth, 0.8.8-9 from experimental to replace 0.8.8-6 that is in testing and unstable.
note that your repos need to be pinned as above for this to work.
Code: Select all
sudo apt-get install -t experimental plymouth
Code: Select all
Processing triggers for fontconfig ...
Setting up initramfs-tools (0.112) ...
update-initramfs: deferring update (trigger activated)
Setting up linux-image-3.2.0-4-686-pae (3.2.41-2) ...
Running depmod.
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/dkms 3.2.0-4-686-pae /boot/vmlinuz-3.2.0-4-686-pae
dkms.conf: Error! No 'BUILT_MODULE_NAME' directive specified for record #0.
Error! Bad conf file.
File:
does not represent a valid dkms.conf file.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.2.0-4-686-pae /boot/vmlinuz-3.2.0-4-686-pae
update-initramfs: Generating /boot/initrd.img-3.2.0-4-686-pae
/usr/sbin/dkms: line 1841: echo: write error: Broken pipe
cp: cannot stat `/usr/lib/i386-linux-gnu/pango/1.6.0/module-files.d/libpango1.0-0.modules': No such file or directory
E: /usr/share/initramfs-tools/hooks/plymouth failed with return 1.
update-initramfs: failed for /boot/initrd.img-3.2.0-4-686-pae with 1.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-3.2.0-4-686-pae.postinst line 696.
dpkg: error processing linux-image-3.2.0-4-686-pae (--configure):
subprocess installed post-installation script returned error exit status 1
Setting up linux-image-3.2.0-4-486 (3.2.41-2) ...
Running depmod.
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/dkms 3.2.0-4-486 /boot/vmlinuz-3.2.0-4-486
dkms.conf: Error! No 'BUILT_MODULE_NAME' directive specified for record #0.
Error! Bad conf file.
File:
does not represent a valid dkms.conf file.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.2.0-4-486 /boot/vmlinuz-3.2.0-4-486
update-initramfs: Generating /boot/initrd.img-3.2.0-4-486
/usr/sbin/dkms: line 1841: echo: write error: Broken pipe
cp: cannot stat `/usr/lib/i386-linux-gnu/pango/1.6.0/module-files.d/libpango1.0-0.modules': No such file or directory
E: /usr/share/initramfs-tools/hooks/plymouth failed with return 1.
update-initramfs: failed for /boot/initrd.img-3.2.0-4-486 with 1.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-3.2.0-4-486.postinst line 696.
dpkg: error processing linux-image-3.2.0-4-486 (--configure):
subprocess installed post-installation script returned error exit status 1
Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-3.2.0-4-686-pae
cp: cannot stat `/usr/lib/i386-linux-gnu/pango/1.6.0/module-files.d/libpango1.0-0.modules': No such file or directory
E: /usr/share/initramfs-tools/hooks/plymouth failed with return 1.
update-initramfs: failed for /boot/initrd.img-3.2.0-4-686-pae with 1.
dpkg: error processing initramfs-tools (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
linux-image-3.2.0-4-686-pae
linux-image-3.2.0-4-486
initramfs-tools
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
Setting up initramfs-tools (0.112) ...
update-initramfs: deferring update (trigger activated)
Setting up linux-image-3.2.0-4-486 (3.2.41-2) ...
Running depmod.
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/dkms 3.2.0-4-486 /boot/vmlinuz-3.2.0-4-486
dkms.conf: Error! No 'BUILT_MODULE_NAME' directive specified for record #0.
Error! Bad conf file.
File:
does not represent a valid dkms.conf file.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.2.0-4-486 /boot/vmlinuz-3.2.0-4-486
update-initramfs: Generating /boot/initrd.img-3.2.0-4-486
/usr/sbin/dkms: line 1841: echo: write error: Broken pipe
cp: cannot stat `/usr/lib/i386-linux-gnu/pango/1.6.0/module-files.d/libpango1.0-0.modules': No such file or directory
E: /usr/share/initramfs-tools/hooks/plymouth failed with return 1.
update-initramfs: failed for /boot/initrd.img-3.2.0-4-486 with 1.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-3.2.0-4-486.postinst line 696.
dpkg: error processing linux-image-3.2.0-4-486 (--configure):
subprocess installed post-installation script returned error exit status 1
Setting up linux-image-3.2.0-4-686-pae (3.2.41-2) ...
Running depmod.
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/dkms 3.2.0-4-686-pae /boot/vmlinuz-3.2.0-4-686-pae
dkms.conf: Error! No 'BUILT_MODULE_NAME' directive specified for record #0.
Error! Bad conf file.
File:
does not represent a valid dkms.conf file.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.2.0-4-686-pae /boot/vmlinuz-3.2.0-4-686-pae
update-initramfs: Generating /boot/initrd.img-3.2.0-4-686-pae
/usr/sbin/dkms: line 1841: echo: write error: Broken pipe
cp: cannot stat `/usr/lib/i386-linux-gnu/pango/1.6.0/module-files.d/libpango1.0-0.modules': No such file or directory
E: /usr/share/initramfs-tools/hooks/plymouth failed with return 1.
update-initramfs: failed for /boot/initrd.img-3.2.0-4-686-pae with 1.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-3.2.0-4-686-pae.postinst line 696.
dpkg: error processing linux-image-3.2.0-4-686-pae (--configure):
subprocess installed post-installation script returned error exit status 1
Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-3.2.0-4-686-pae
cp: cannot stat `/usr/lib/i386-linux-gnu/pango/1.6.0/module-files.d/libpango1.0-0.modules': No such file or directory
E: /usr/share/initramfs-tools/hooks/plymouth failed with return 1.
update-initramfs: failed for /boot/initrd.img-3.2.0-4-686-pae with 1.
dpkg: error processing initramfs-tools (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
linux-image-3.2.0-4-486
linux-image-3.2.0-4-686-pae
initramfs-tools
Re: Upgrade Warnings: LMDE tracking TESTING [25-05-13]
rcrath
interesting
i saw this happening consistently in sid with plymouth and linux > 3.9
it's the first time i see it being reported with linux 3.2.x
interesting
i saw this happening consistently in sid with plymouth and linux > 3.9
it's the first time i see it being reported with linux 3.2.x
Re: Upgrade Warnings: LMDE tracking TESTING [25-05-13]
interesting...I got new pango several days ago and my system still working fine. I'm not really sure but this problem might only affect on 32bit system.
Re: Upgrade Warnings: LMDE tracking TESTING [25-05-13]
kurotsugi
maybe not 64bit/32bit related
first time i saw this was on the 28th may http://forums.solydxk.com/viewtopic.php?f=35&t=240&start=160#p7202 (64bit system tracking sid) and that led me to this bug report >> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702040 (and as you see also a 64bit system)
maybe not 64bit/32bit related
first time i saw this was on the 28th may http://forums.solydxk.com/viewtopic.php?f=35&t=240&start=160#p7202 (64bit system tracking sid) and that led me to this bug report >> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702040 (and as you see also a 64bit system)
Re: Upgrade Warnings: LMDE tracking TESTING [25-05-13]
I also got the pango problem with kernels: linux-image-3.2.0-4-amd64 and linux-image-3.9-6.dmz.1-liquorix-amd64.
Also is anybody affected by this: https://bugs.launchpad.net/pidgin/+bug/1108056 - Pidgin freezing at startup 75% of the time.
It seems that if I disable the xmpp accouts (gtalk) it get's a little bit better.
Also is anybody affected by this: https://bugs.launchpad.net/pidgin/+bug/1108056 - Pidgin freezing at startup 75% of the time.
It seems that if I disable the xmpp accouts (gtalk) it get's a little bit better.
Re: Upgrade Warnings: LMDE tracking TESTING [25-05-13]
Printing problems today (unable to send data to printer). What I did to fix it is reinstall all cups related packages, remove the printer through the GUI and add it again. Now it works again.
Re: Upgrade Warnings: LMDE tracking TESTING [25-05-13]
it might be easier for us if you could list the package needed to reinstalled. new LMDE user might doesn't know which packages are related to cups.
Re: Upgrade Warnings: LMDE tracking TESTING [25-05-13]
New LMDE users should not be tracking testing.
Re: Upgrade Warnings: LMDE tracking TESTING [25-05-13]
even though we already said 'don't' so many times, there are still some new user driven by their pure curiosity who jumped into testing. I believe this thread is not made only for LMDE experts. the main purpose of this thread is to help anyone who follow testing - regardless their knowledge on LMDE - to fix their problem after an update broke their system. please also consider that your information might also useful to find the package which causing this bugs so that the devs could quickly fix it.