LMDE Breakages (Tracking SID)

Archived topics about LMDE 1
Forum rules
User avatar
GregE
Level 4
Level 4
Posts: 472
Joined: Sun Jan 16, 2011 6:24 am
Location: Melbourne, Australia

Re: LMDE Breakages (Tracking SID) May 7, 2013

Postby GregE » Wed Oct 16, 2013 1:41 am

If it is still a problem, try apt-get install lightdm and accept lightdm as the default, then reboot. If the problem is related to xorg then that will not help. All the Gnome stuff is transitioning to 3.8. Try and get your Xfce back running then you can clean up Gnome update issues.

Reading the Debian Forums for another issue I noticed your problem is widespread. Installing LightDM and changing the default will probably help, otherwise run dpkg-reconfigure gdm3 - or both

User avatar
Gerd50
Level 5
Level 5
Posts: 734
Joined: Wed Jul 22, 2009 3:42 pm
Location: Fishtown, Germany

Re: LMDE Breakages (Tracking SID) May 7, 2013

Postby Gerd50 » Thu Oct 17, 2013 6:34 am

Thank's GregE, lightdm helps. I could du today and reboot into a working screen :)
I believe in everything, except humans.

LM9, Debian Testing Xfce, Debian Sid Xfce - CPU/Amd64 2,6Ghz, Graphics/Nvidia 9600 GT, Sound/SB Audigy4 emu10K1

wayne128
Level 10
Level 10
Posts: 3418
Joined: Tue Jul 13, 2010 12:15 am

Re: LMDE Breakages (Tracking SID) May 7, 2013

Postby wayne128 » Wed Oct 23, 2013 11:30 pm

fully d-u on debian xfce sid.
running new kernel 3.11.5-1

root@hp8000:/home/wayne# apt-get update && apt-get dist-upgrade
....
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@hp8000:/home/wayne# uname -a
Linux hp8000 3.11-1-686-pae #1 SMP Debian 3.11.5-1 (2013-10-17) i686 GNU/Linux



so far no issue.

it resolved my older issue of vlc2.08 taking more than 10 seconds to play network shared file.

now it takes about 2.5-3 second and starts playing.
gnome-mplayer takes a little over 1 second to start playing.

abickerton
Level 1
Level 1
Posts: 23
Joined: Tue Jul 10, 2012 3:01 pm

Re: LMDE Breakages (Tracking SID) May 7, 2013

Postby abickerton » Tue Dec 10, 2013 5:23 pm

- Skype cannot be installed right now.

Is it safe to install systemd yet?, there are packages that try to pull in systemd as dependencies.

kurotsugi
Level 6
Level 6
Posts: 1041
Joined: Fri Jan 25, 2013 3:54 am

Re: LMDE Breakages (Tracking SID) May 7, 2013

Postby kurotsugi » Tue Dec 10, 2013 6:01 pm

there are 1 or 2 visible bug but IMO systemd is quite stable for daily use at this moment. nevertheless, I recommend to avoid install systemd-sysvinit package. we'll need to add 'init=/lib/systemd/systemd' on our boot parameter to activate it.

wayne128
Level 10
Level 10
Posts: 3418
Joined: Tue Jul 13, 2010 12:15 am

Re: LMDE Breakages (Tracking SID) May 7, 2013

Postby wayne128 » Thu Jan 16, 2014 3:20 am

not updated for a while.

try to d-u today, a long list of bugs.

Code: Select all

682 upgraded, 63 newly installed, 4 to remove and 0 not upgraded.
Need to get 0 B/506 MB of archives.
After this operation, 254 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
grave bugs of libopenjpeg2 (1.3+dfsg-4.6 → 1.3+dfsg-4.7+b1) <Outstanding>
 #734238 - Fix for CVE-2013-6045 breaks decoding of chroma-subsampled images
grave bugs of xserver-xorg-input-evdev (1:2.8.1-1+b2 → 1:2.8.2-1) <Outstanding>
 #734760 - xserver-xorg-input-evdev: ps2 keyboard maniacally retypes keys after one press. sometimes drops keys.
grave bugs of libwebkitgtk-3.0-0 (2.2.0-2 → 2.2.3-1) <Outstanding>
 #728789 - dwb: crash with segmentation fault very often
serious bugs of dh-python (1.20131003-1 → 1.20131021-1) <Outstanding>
 #733239 - dh-python: there is no script in the new version of the package - giving up-Jessie
serious bugs of keyboard-configuration (1.102 → 1.104) <Outstanding>
 #729321 - keyboard-configuration: changes /etc/default/keyboard upon upgrade without asking
serious bugs of rpcbind (0.2.0-8.2 → 0.2.1-2) <Outstanding>
 #734903 - rpcbind: fails to upgrade from 'wheezy' - trying to overwrite /usr/share/man/man8/rpcinfo.8.gz
serious bugs of samba-libs (2:4.0.10+dfsg-2 → 2:4.1.3+dfsg-2) <Outstanding>
 #732342 - samba-libs: hdb_samba4.so broken
 #732344 - samba-libs: hdb_samba4.so: too loose dependency on heimdal
serious bugs of iceweasel (24.0-2 → 24.2.0esr-1) <Outstanding>
 #735297 - iceweasel: Update the license to MPL 2.0
serious bugs of java-common (0.49 → 0.50) <Outstanding>
 #732282 - stop building java for sparc, sparc64, s390, kfreebsd-any
serious bugs of ruby1.9.1 (→ 1.9.3.484-1) <Outstanding>
 #653582 - Segfaults when running ruby-hpricot's test suite on ia64
serious bugs of system-config-printer (1.4.1-4 → 1.4.3-1) <Outstanding>
 #730516 - missing dependency on python-cairo
serious bugs of base-passwd (3.5.28 → 3.5.31) <Outstanding>
 #734946 - base-passwd: block from testing until all shell-fallout bugs are fixed
serious bugs of python-pexpect-doc (→ 3.0-2) <Outstanding>
 #732915 - [python-pexpect-doc] Undeclared conflict with python-pexpect < 3
Summary:
 dh-python(1 bug), keyboard-configuration(1 bug), libopenjpeg2(1 bug), rpcbind(1 bug), xserver-xorg-input-evdev(1 bug), samba-libs(2 bugs), iceweasel(1 bug), java-common(1 bug), libwebkitgtk-3.0-0(1 bug), ruby1.9.1(1 bug), system-config-printer(1 bug), base-passwd(1 bug), python-pexpect-doc(1 bug)
Are you sure you want to install/upgrade the above packages? [Y/n/?/...] y


Anyway, OS partition already backup, went ahead just to see what is the impact.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

root@hp8000:/home/wayne# uname -a
Linux hp8000 3.12-1-686-pae #1 SMP Debian 3.12.6-2 (2013-12-29) i686 GNU/Linux


Reboot,

Testing...
lost ability to browse Network shared files...
Error: Failed to open WorkGroup, Failed to retrieve share list from server: Connection refused.

Reinstall samba, problem went away.

User avatar
GeneC
Level 7
Level 7
Posts: 1599
Joined: Fri Sep 03, 2010 1:59 pm
Location: Maine, USA

Re: LMDE Breakages (Tracking SID) May 7, 2013

Postby GeneC » Thu Mar 27, 2014 8:23 am

Todays updates breaks some Gnome. (Transition from 3.10 to 3.12) best wait a bit to DU.

Code: Select all

Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
The following packages will be REMOVED:
  abiword libabiword-3.0 libchamplain-0.12-0 libchamplain-gtk-0.12-0 libcogl-pango12 libcogl12
The following NEW packages will be installed:
  libcogl-pango20 libcogl-path20 libcogl20 libwayland-egl1-mesa
The following packages will be upgraded:
  blends-common ca-certificates cpio dbus dbus-x11 evince-common evince-gtk foomatic-db gir1.2-clutter-1.0 gir1.2-cogl-1.0 gir1.2-coglpango-1.0
  gir1.2-json-1.0 gir1.2-packagekitglib-1.0 gnome-icon-theme gnome-icon-theme-symbolic hardinfo inxi libclutter-1.0-0 libclutter-gtk-1.0-0 libdbus-1-3
  libevdocument3-4 libevview3-3 libgmp10 libgmpxx4ldbl libgsf-1-114 libgsf-1-common libjson-glib-1.0-0 libjson-glib-1.0-common libpackagekit-glib2-16
  libpipeline1 libruby2.0 libtelepathy-glib0 lightdm-gtk-greeter linux-libc-dev mobile-broadband-provider-info openprinting-ppds ruby2.0 synaptic
38 upgraded, 4 newly installed, 6 to remove and 0 not upgraded.
Need to get 28.6 MB of archives.
After this operation, 18.3 MB disk space will be freed.
Do you want to continue? [Y/n] N


ALSO

http://forum.siduction.org/index.php?topic=4407.0
(to be removed)

Code: Select all

gdm3 gir1.2-mutter-3.0 gnome-games gnome-nibbles gnome-session gnome-shell
  gnome-shell-extensions libmutter0b libtotem0 lightsoff quadrapassel
  swell-foop totem

User avatar
GeneC
Level 7
Level 7
Posts: 1599
Joined: Fri Sep 03, 2010 1:59 pm
Location: Maine, USA

Re: LMDE Breakages (Tracking SID) May 7, 2013

Postby GeneC » Sat Mar 29, 2014 7:22 am

Safe to DU today.. cogl updates go through ok. (libcogl12 to libcogl20)

Code: Select all

Commit Log for Sat Mar 29 06:57:51 2014


Removed the following packages:
libcogl-pango12
libcogl12

Upgraded the following packages:
a2ps (1:4.14-1.1) to 1:4.14-1.2
abiword (3.0.0-4+b1) to 3.0.0-4+b2
bsdutils (1:2.20.1-5.6) to 1:2.20.1-5.7
cups-filters (1.0.49-1) to 1.0.50-1
cups-filters-core-drivers (1.0.49-1) to 1.0.50-1
gir1.2-clutter-1.0 (1.14.4-3) to 1.18.0-2
gir1.2-cogl-1.0 (1.14.0-3) to 1.18.0-2
gir1.2-coglpango-1.0 (1.14.0-3) to 1.18.0-2
gnome-games (1:3.8+4) to 1:3.8+5
libabiword-3.0 (3.0.0-4+b1) to 3.0.0-4+b2
libblkid1 (2.20.1-5.6) to 2.20.1-5.7
libchamplain-0.12-0 (0.12.7-1) to 0.12.7-1+b1
libchamplain-gtk-0.12-0 (0.12.7-1) to 0.12.7-1+b1
libclutter-1.0-0 (1.14.4-3) to 1.18.0-2
libclutter-gtk-1.0-0 (1.4.4-3) to 1.4.4-3+b1
libcupsfilters1 (1.0.49-1) to 1.0.50-1
libdaemon0 (0.14-2) to 0.14-3
libffi6 (3.0.13-12) to 3.1~rc1-2
libfontembed1 (1.0.49-1) to 1.0.50-1
libgl1-nvidia-glx (331.49-1) to 331.49-2.siduction.1
libmount1 (2.20.1-5.6) to 2.20.1-5.7
libnm-glib-vpn1 (0.9.8.0-5) to 0.9.8.8-4
libnm-glib4 (0.9.8.0-5) to 0.9.8.8-4
libnm-gtk-common (0.9.8.8-1) to 0.9.8.8-2
libnm-gtk0 (0.9.8.8-1) to 0.9.8.8-2
libnm-util2 (0.9.8.0-5) to 0.9.8.8-4
libnvidia-ml1 (331.49-1) to 331.49-2.siduction.1
libopenjpeg5 (1.5.1-3) to 1.5.2-1
libparted0debian1 (2.3-16) to 2.3-17
libpulse-mainloop-glib0 (4.0-6+b1) to 5.0-1
libpulse0 (4.0-6+b1) to 5.0-1
libpulsedsp (4.0-6+b1) to 5.0-1
libuuid1 (2.20.1-5.6) to 2.20.1-5.7
libyaml-0-2 (0.1.4-3.1) to 0.1.4-3.2
modemmanager (0.5.2.0-2.1) to 1.0.0-4
mount (2.20.1-5.6) to 2.20.1-5.7
network-manager (0.9.8.0-5) to 0.9.8.8-4
network-manager-gnome (0.9.8.8-1) to 0.9.8.8-2
nvidia-alternative (331.49-1) to 331.49-2.siduction.1
nvidia-driver (331.49-1) to 331.49-2.siduction.1
nvidia-kernel-dkms (331.49-1) to 331.49-2.siduction.1
nvidia-kernel-source (331.49-1) to 331.49-2.siduction.1
nvidia-vdpau-driver (331.49-1) to 331.49-2.siduction.1
openssh-client (1:6.5p1-6) to 1:6.6p1-1
openssh-server (1:6.5p1-6) to 1:6.6p1-1
openssh-sftp-server (1:6.5p1-6) to 1:6.6p1-1
parted (2.3-16) to 2.3-17
php5-cgi (5.5.9+dfsg-1) to 5.5.10+dfsg-1
php5-common (5.5.9+dfsg-1) to 5.5.10+dfsg-1
pulseaudio (4.0-6+b1) to 5.0-1
pulseaudio-utils (4.0-6+b1) to 5.0-1
python-lxml (3.3.2-1) to 3.3.3-1
python-numpy (1:1.8.1~rc1-2) to 1:1.8.1-1
rsyslog (7.6.2-1) to 7.6.3-1
time (1.7-24) to 1.7-25
util-linux (2.20.1-5.6) to 2.20.1-5.7
vim (2:7.4.161-1) to 2:7.4.225-1
vim-common (2:7.4.161-1) to 2:7.4.225-1
vim-runtime (2:7.4.161-1) to 2:7.4.225-1
xserver-xorg-video-nvidia (331.49-1) to 331.49-2.siduction.1

Installed the following packages:
libcogl-pango20 (1.18.0-2)
libcogl-path20 (1.18.0-2)
libcogl20 (1.18.0-2)
libmbim-glib0 (1.8.0-1)
libmm-glib0 (1.0.0-4)
libqmi-glib0 (1.4.0-1)
libsystemd-id128-0 (204-8)
libwayland-egl1-mesa (10.1.0-4)

User avatar
GeneC
Level 7
Level 7
Posts: 1599
Joined: Fri Sep 03, 2010 1:59 pm
Location: Maine, USA

Re: LMDE Breakages (Tracking SID)

Postby GeneC » Mon Mar 31, 2014 7:36 am

SID is in for a bumby ride with the transition of Gnome from 3.8 to 3.10. We have seen the first of this in the last few posts. All is clear today (3.31.14) but watch out. This not only effects Gnome (shell, unity, et) users, but any DE using gnome apps.

From Siduction Forum....
http://forum.siduction.org/index.php?topic=4419.0
musca

Posts: 60

Pre Warning: pending gnome 3.10 transition

Hello dear gnome users,

according to the debian transition tracker https://release.debian.org/transitions/ the next transition to gnome 3.10 https://release.debian.org/transitions/ ... -3-10.html is already pending.
As soon as the first package of this series is uploaded the gnome desktop will be broken.

Stay tuned, read what apt puts on your screen and don't remove your whole desktop!

If you accidentally removed your gnome desktop by hitting the enter key too fast, please follow theese rules:
1. Don't panic!
2. Carry a towel with you.

Usually your system can be repaired, at least when the transition is completely done.


greetings
musca

User avatar
GregE
Level 4
Level 4
Posts: 472
Joined: Sun Jan 16, 2011 6:24 am
Location: Melbourne, Australia

Re: LMDE Breakages (Tracking SID)

Postby GregE » Wed Apr 02, 2014 6:43 am

Thanks Gene.

Another piece of advice for those who choose this perilous path - always have Xfce4 installed. A basic Xfce setup uses very little disk space by modern standards and is very handy to have as a standby desktop.

This scenario is the big issue with Gnome. Distros like Ubuntu Gnome can update the lot in a new release, but rolling distros, like running Sid, can never have an easy transition. It would be nice to have a PPA like system where all the packages could be updated then released in one fell swoop not dribbled out to cause dependency hell. I am not sure 3.10 is going to be really released as most of the packages coming through are for 3.12. We might end up missing 3.10, like 3.6 was skipped. 3.10 might end up in Sid for a brief time but I would be surprised to ever see it in Testing. Time will tell.

User avatar
GeneC
Level 7
Level 7
Posts: 1599
Joined: Fri Sep 03, 2010 1:59 pm
Location: Maine, USA

Re: LMDE Breakages (Tracking SID)

Postby GeneC » Wed Apr 02, 2014 7:04 am

Hi Greg.

Very good point about XFCE. I find that the only times I have broken the Shell desktop is changing GTK themes or with a mis-matched new extension. Logging in to xfce makes the fix (changing theme back to a good one 'Adwaita' always works), or removing the offending extension is quite easy... 8)

--------------
PS
If you have broken your Gnome Shell desktop by changing theme and DO NOT have XFCE (or another DE to fall back on ).

This command will reload the default "Adwaita" theme

Code: Select all

gsettings set org.gnome.desktop.interface gtk-theme 'Adwaita'

wayne128
Level 10
Level 10
Posts: 3418
Joined: Tue Jul 13, 2010 12:15 am

Re: LMDE Breakages (Tracking SID)

Postby wayne128 » Fri Apr 04, 2014 3:35 am

trying to d-u debian xfce sid

capture the bug list first:

Do you want to continue? [Y/n] y
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
critical bugs of grub-pc-bin (2.00-22 → 2.02~beta2-8) <Outstanding>
#741464 - grub-pc-bin: hangs after displaying boot menu
grave bugs of systemd (→ 204-8) <Outstanding>
#743158 - systemd: sends private information without confirmation
serious bugs of systemd (→ 204-8) <Outstanding>
#743157 - systemd: disables networking permanently during tried suspend
#740345 - systemd: configuration/arch-any files under /usr/lib/
serious bugs of texlive-base (2013.20140215-1 → 2013.20140314-1) <Outstanding>
#742189 - upgrade from wheezy to jessie fails
Summary:
systemd(3 bugs), grub-pc-bin(1 bug), texlive-base(1 bug)
Are you sure you want to install/upgrade the above packages? [Y/n/?/...]



EDIT: Update

1. survived with full d-u.. db5.1-util held-back
quick check, all seems to work, no issue accessing NAS and play media files from NAS.

The following packages have been kept back:
db5.1-util
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
root@hp8000:/home/wayne#




2. grub version is 202-beta2-8, the bug might not hit this installtion
wayne@hp8000:~$ apt-cache policy grub-pc
grub-pc:
Installed: 2.02~beta2-8
Candidate: 2.02~beta2-8
Version table:
*** 2.02~beta2-8 0
500 http://ftp.jp.debian.org/debian/ sid/main i386 Packages
100 /var/lib/dpkg/status
wayne@hp8000:~$


3. notice systemd installed..
wayne@hp8000:~$ apt-cache policy systemd
systemd:
Installed: 204-8
Candidate: 204-8
Version table:
*** 204-8 0
500 http://ftp.jp.debian.org/debian/ sid/main i386 Packages
100 /var/lib/dpkg/status



but not sure how to interprete systemd..
read too many posts saying systemd would boot very fast.
however, in this installation it has added several seconds ! boot slower !!
used to be like 15-17 seconds, now... 24 seconds

dmesg on last few lines showed:
[ 14.981013] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 18.344515] Bluetooth: Core ver 2.17
[ 18.344536] NET: Registered protocol family 31
[ 18.344537] Bluetooth: HCI device and connection manager initialized
[ 18.344546] Bluetooth: HCI socket layer initialized
[ 18.344548] Bluetooth: L2CAP socket layer initialized
[ 18.344552] Bluetooth: SCO socket layer initialized
[ 18.365351] Bluetooth: RFCOMM TTY layer initialized
[ 18.365360] Bluetooth: RFCOMM socket layer initialized
[ 18.365368] Bluetooth: RFCOMM ver 1.11
[ 18.468330] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 18.468333] Bluetooth: BNEP filters: protocol multicast
[ 18.468340] Bluetooth: BNEP socket layer initialized
[ 21.979972] systemd-logind[2736]: New seat seat0.
[ 21.986639] systemd-logind[2736]: Watching system buttons on /dev/input/event4 (Power Button)
[ 21.986726] systemd-logind[2736]: Watching system buttons on /dev/input/event7 (Video Bus)
[ 21.986809] systemd-logind[2736]: Watching system buttons on /dev/input/event3 (Power Button)
[ 24.780855] systemd-logind[2736]: New session 1 of user wayne.
[ 24.780953] systemd-logind[2736]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display.




4 check on resume from suspend to see if hit by this bug:
#743157 - systemd: disables networking permanently during tried suspend

well, lucky, no issue resume from suspend and access to networking, both internet and home network

User avatar
GeneC
Level 7
Level 7
Posts: 1599
Joined: Fri Sep 03, 2010 1:59 pm
Location: Maine, USA

Re: LMDE Breakages (Tracking SID)

Postby GeneC » Fri Apr 04, 2014 9:23 am

Hi Wayne... :D

Fully updated today here. db5.1-util had been held back, but I uninstalled it (I dont need it). Yes, systemd does get installed, but if I understand correctly does not simply get implemented. You have to configure it.
From Siduction Wiki
(its in German. I use Google Translate for English)
http://wiki.siduction.de/index.php?title=Systemd

Introduction

systemd is init system, which competes with the best sysvinit and upstart stands. It was developed by the well-known developer Lennart Poettering Red Hat. What is sysvinit replace? present is relatively open, which is the future of both systems. I tend to systemd, as it has the more promising approach for me. However, presently preferred Ubuntu Upstart yet, and many approaches of systemd to be integrated by Upstart. Who wants to penetrate deeper into the matter, I recommend the blog of Lennart with the significant title Rethinking PID 1 PID 1 is always init, the first process to be started a booting system. systemd in Debian


Since about half a year is systemd found in debian / experimantal, currently in version 11-1. I installed it for a few days to test it. I also have a patch integrates the effects of cgroups to test.
Disclaimer :
The changes hereinafter described to the system are invasive. systemd is still in an experimental stage. The cgroups patch has yet to make its effect to the test and will not exceed 5% of the readers bring something. Therefore, these instructions are intended rather to advanced users. The systems used should have a backup. The system may be unbootable!
systemd install

First, the experimental repository must be enabled. Then we install:

Code: Select all

# Apt-get update && apt-get install-t experimental systemd dbus libpam-cgroup

Then the grub2 needs to be adjusted:

Code: Select all

# gedit / etc / default / grub

On the line: GRUB_CMDLINE_LINUX_DEFAULT = "quiet" we hang init = / bin / systemd , so that it looks like this:
GRUB_CMDLINE_LINUX_DEFAULT = "quiet init = / bin / systemd"

Now a:

Code: Select all

# Update-grub

Thus we are done by the system to boot with systemd.


Did not work for me. It booted, but could not open synaptic, nor use apt-get? I forget the details.
I will wait on systemd, from what I read many see no improvements.

kurotsugi
Level 6
Level 6
Posts: 1041
Joined: Fri Jan 25, 2013 3:54 am

Re: LMDE Breakages (Tracking SID)

Postby kurotsugi » Fri Apr 04, 2014 6:06 pm

that page was created on 2012. now we have 204 which quite stable for daily use. this page is better https://wiki.debian.org/systemd
but not sure how to interprete systemd..
read too many posts saying systemd would boot very fast.
however, in this installation it has added several seconds ! boot slower !!
used to be like 15-17 seconds, now... 24 seconds

you can run 'systemd-analyze blame' to find out why did it boot longer. as genec pointed above systemd isn't used by default. we need to add init=/lib/systemd/systemd on our boot parameter to use it. on most cases it will decrease the boot time but not a drastical ones since systemd isn't optimized yet.

User avatar
GeneC
Level 7
Level 7
Posts: 1599
Joined: Fri Sep 03, 2010 1:59 pm
Location: Maine, USA

Re: LMDE Breakages (Tracking SID)

Postby GeneC » Fri Apr 04, 2014 7:16 pm

kurotsugi wrote:that page was created on 2012. now we have 204 which quite stable for daily use. this page is better .........


Darn. Siduction should update their Wiki... :lol: In their defense the new iso come with systemd by default. My Siduction install is from early last summer, and still running like a freight train... I have had some hold-backs, but never a breakage with XFCE. I see the KDE guys have more issues.

wayne128
Level 10
Level 10
Posts: 3418
Joined: Tue Jul 13, 2010 12:15 am

Re: LMDE Breakages (Tracking SID)

Postby wayne128 » Fri Apr 04, 2014 8:07 pm

Hi GeneC,

OK I remove db5.1-util.

Tested what you wrote on configuring systemd using the wiki....

haha :mrgreen: ...... kernel panic around 3 second upon reboot, repeated for a few rounds.

So I remove the init=/bin/systemd on /etc/default/grub.
back to working.

Attempt to remove systemd, however it wants to remove network-manager which I am using so just let it stay to see how it evolves on future upgrade.

Edit: decided to remove systemd and network-manager

now, back to fast boot, 17 seconds
[ 10.832078] e1000e 0000:00:19.0: irq 46 for MSI/MSI-X
[ 10.832176] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 12.294569] input: ACPI Virtual Keyboard Device as /devices/virtual/input/input15
[ 13.676866] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
[ 13.676997] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 16.495530] Bluetooth: Core ver 2.17
[ 16.495552] NET: Registered protocol family 31
[ 16.495553] Bluetooth: HCI device and connection manager initialized
[ 16.495560] Bluetooth: HCI socket layer initialized
[ 16.495563] Bluetooth: L2CAP socket layer initialized
[ 16.495566] Bluetooth: SCO socket layer initialized
[ 16.508195] Bluetooth: RFCOMM TTY layer initialized
[ 16.508207] Bluetooth: RFCOMM socket layer initialized
[ 16.508216] Bluetooth: RFCOMM ver 1.11
[ 16.565484] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 16.565493] Bluetooth: BNEP filters: protocol multicast
[ 16.565500] Bluetooth: BNEP socket layer initialized
wayne@hp8000:~$




+1 on xfce. no issues on countless d-u with sid.

User avatar
GregE
Level 4
Level 4
Posts: 472
Joined: Sun Jan 16, 2011 6:24 am
Location: Melbourne, Australia

Re: LMDE Breakages (Tracking SID)

Postby GregE » Sat Apr 05, 2014 7:47 pm

To use systemd you need to install one package

Code: Select all

# apt-get install systemd-sysv


This will remove sysvinit-core and you will be using systemd rather than sysvinit and have a faster boot.

But, as Gene says above, the Debian world is not quite ready yet. A dist-upgrade with the wrong packages can really muck things up. I know this because I trashed my system with an early play with systemd.

By all means read the wiki, https://wiki.debian.org/systemd for educational purposes. It will become the default soon enough and probably without too much effort from the end user.

Off topic but related - I have a system with two SSDs and the boot time difference for me is no more than two seconds. A 60GB SSD is now very cheap and more than big enough for a complete Linux install and then some. Put root on the SSD and swap and /home on a HDD and then boot in seconds. Then when systemd comes online it will boot faster than a speeding bullet.

kurotsugi
Level 6
Level 6
Posts: 1041
Joined: Fri Jan 25, 2013 3:54 am

Re: LMDE Breakages (Tracking SID)

Postby kurotsugi » Sun Apr 06, 2014 6:32 am

I've been using systemd on debian since ver 44 and I found it quite stable for daily use. systemd itself never broke. the things tend to broke in my system was cinnamon and gnome. switching to xfce have saved me alot from breakage.
This will remove sysvinit-core and you will be using systemd rather than sysvinit and have a faster boot.

for safety reason this step is not needed. we can use 'init=/lib/systemd/systemd/' to use systemd. even though systemd itself is quite stable but the transition from sysvinit to systemd might get rough. especially on sid.

wayne128
Level 10
Level 10
Posts: 3418
Joined: Tue Jul 13, 2010 12:15 am

Re: LMDE Breakages (Tracking SID)

Postby wayne128 » Sun Apr 20, 2014 6:37 am

few days ago sid wanted to remove network manager so I did not proceed.

today try to d-u, saw this bug
Debian Bug report logs - #745233
libhogweed2: should have versioned depend on newer libgmp10

https://bugs.debian.org/cgi-bin/bugrepo ... bug=745233

could not figure out if it can upset my installation..

there is no longer issue on network manager removal...
so I took the risk.

fully d-u.. reboot, check and all is well.

User avatar
GeneC
Level 7
Level 7
Posts: 1599
Joined: Fri Sep 03, 2010 1:59 pm
Location: Maine, USA

Re: LMDE Breakages (Tracking SID)

Postby GeneC » Sun Apr 20, 2014 9:20 am

Hi Wayne... :D

I use Wicd, so network manager was not an issue for me. All is fine here both with SID install and Debian Testing. I honestly dont understand all the issues that folks have with Debian distros utilizing Update Packs. (well, I do, too many updates all at once.. :shock: ..)

My feelings are that it is best to update daily and avoid the messes. Been running LMDE with its original (following Debian Testing repos) since it first came out (Dec, 2010) with few issues. Running SID (on Siduction) since last July, updating daily with no issues other than the occasional hold back. Never a real breakage.

Debian with Update Packs can never work as intended (prevent or even minimize breakages) unless there is a real and thorough testing of the Update Packs prior to general release. As it stands now you have about a half a dozen 'informal testers' (mostly just forum members) who update and report issues. Not an adequate method of testing, so you always see many issues with each new UP. I am afraid things will never be really 'stable' with the current testing of UP's. I personally would suggest anyone using Debian and not tracking a straight Debian Stable (that is, following Testing, and semi-rolling with UP's) to follow the existing forum threads to head off potential issues, and update daily. You will learn a lot more (have a chance to see what each package is, and does by looking at its description in Synaptic something easily done with the 5-20 daily updates, and not feasible with UP's and many hundreds of updates.

I also use this as an opportunity to find packages that are not really needed (Foreign language fonts, wifi drivers, et...for example) that I can remove and not have to constantly download and upgrade for no reason.. A win/Win all over as far as I am concerned.
A little more work overall, but satisfying and a good learning experience.

For those wanting (needing) a very stalble operating sytstem. I would recommend to any of my friends one of the Ubuntu based LTS distros.. :wink:


Return to “Archive”

Who is online

Users browsing this forum: No registered users and 2 guests