Bug#794110: plasma-workspace: plasmashell segmentation fault (11) every few minutes (and restarted)
Package: plasma-workspace Version: 4:5.4.3-2 Followup-For: Bug #794110 Dear Maintainer, I confirm the bug is still present. Plasmashell crashes randomly, and, particularly annoyingly, it kills all konsole instances that were open at the moment of the crash, so after it is relaunched one looses the content of all open terminals. I also find sometimes several instances of plasmashell running after a few crashes. This is making the desktop environment close to unusable, as most time is spent restarting/resetting the environment instead of working. A release fixing all this would be much appreciated. Yes, I have seen there is a new one in experimental, but I am going to wait for it to reach testing before giving it a try. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=ia_FR.UTF-8, LC_CTYPE=ia_FR.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.utf8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages plasma-workspace depends on: ii dbus-x11 1.10.6-1 ii frameworkintegration 5.16.0-1 ii gdb 7.10-1+b1 ii kactivities 5.16.0-1 ii kde-cli-tools4:5.4.3-1 ii kded55.16.0-1 ii kinit5.16.0-1 ii kio 5.16.0-1 ii libc62.21-9 ii libcln6 1.3.4-1 ii libdbusmenu-qt5-20.9.3+15.10.20150604-1 ii libgcc1 1:5.3.1-11 ii libgps22 3.15-2 ii libice6 2:1.0.9-1+b1 ii libkf5activities55.16.0-1 ii libkf5auth5 5.16.0-1 ii libkf5baloo5 5.16.0-1 ii libkf5bookmarks5 5.16.0-1 ii libkf5completion55.16.0-1 ii libkf5configcore55.16.0-1 ii libkf5configgui5 5.16.0-1 ii libkf5configwidgets5 5.16.0-1 ii libkf5coreaddons55.16.0-1 ii libkf5crash5 5.16.0-1 ii libkf5dbusaddons55.16.0-1 ii libkf5declarative5 5.16.0-1 ii libkf5globalaccel-bin5.16.0-1 ii libkf5globalaccel5 5.16.0-1 ii libkf5guiaddons5 5.16.0-1 ii libkf5i18n5 5.16.0-1 ii libkf5iconthemes55.16.0-1 ii libkf5idletime5 5.16.0-1 ii libkf5itemviews5 5.16.0-1 ii libkf5jobwidgets55.16.0-1 ii libkf5js55.16.0-1 ii libkf5jsembed5 5.16.0-1 ii libkf5kdelibs4support5 5.16.0-1 ii libkf5kiocore5 5.16.0-1 ii libkf5kiofilewidgets55.16.0-1 ii libkf5kiowidgets55.16.0-1 ii libkf5networkmanagerqt6 5.16.0-1 ii libkf5newstuff5 5.16.0-1 ii libkf5notifications5 5.16.0-1 ii libkf5notifyconfig5 5.16.0-1 ii libkf5package5 5.16.0-1 ii libkf5plasma55.16.0-1 ii libkf5plasmaquick5 5.16.0-1 ii libkf5quickaddons5 5.16.0-1 ii libkf5runner55.16.0-1 ii libkf5screen64:5.4.3-1 ii libkf5service-bin5.16.0-1 ii libkf5service5 5.16.0-1 ii libkf5solid5 5.16.0-1 ii libkf5su55.16.0-1 ii libkf5texteditor55.16.0-1 ii libkf5textwidgets5 5.16.0-1 ii libkf5wallet-bin 5.16.0-1 ii libkf5wallet55.16.0-1 ii libkf5waylandclient5 4:5.4.3-1 ii libkf5waylandserver5 4:5.4.3-1 ii libkf5webkit55.16.0-1 ii libkf5widgetsaddons5 5.16.0-1 ii libkf5windowsystem5 5.16.0-1 ii libkf5xmlgui55.16.0-1 ii libkf5xmlrpcclient5 5.16.0-1 ii libksgrd74:5.4.3-1 ii libkworkspace5-5 4:5.4.3-2 ii libpam0g 1.1.8-3.2 ii libphonon4qt5-4 4:4.8.3-2 ii libplasma-geolocation-interface5 4:5.4.3-2 ii libprocesscore7
Bug#820709: konqueror: No file view, only file size view is available!
Package: konqueror Version: 4:15.08.3-1 Severity: grave Justification: renders package unusable Dear Maintainer, the current version of Konqueror only offers the File Size view, Cervisia View and File Search view. The usual file view/icon view/compact view modes have disappeared. This makes Konqueror next to useless on the desktop, and since many other application try to open directories using Konqueror, they become severely hindered too. This bug is extremely similar to the one reported 6 years ago here: http://www.aptosid.org/index.php?name=PNphpBB2&file=viewtopic&p=18031 I hope this provides some useful information -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.4.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=ia_FR.UTF-8, LC_CTYPE=ia_FR.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.utf8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages konqueror depends on: ii install-info6.1.0.dfsg.1-5 ii kde-baseapps-bin4:15.08.3-1 ii kde-baseapps-data 4:15.08.3-1 ii kde-runtime 4:15.08.3-1+b1 ii libc6 2.22-5 ii libkcmutils44:4.14.14-1+b1 ii libkde3support4 4:4.14.14-1+b1 ii libkdecore5 4:4.14.14-1+b1 ii libkdesu5 4:4.14.14-1+b1 ii libkdeui5 4:4.14.14-1+b1 ii libkfile4 4:4.14.14-1+b1 ii libkhtml5 4:4.14.14-1+b1 ii libkio5 4:4.14.14-1+b1 ii libkonq5abi14:15.08.3-1 ii libkonqsidebarplugin4a 4:15.08.3-1 ii libkparts4 4:4.14.14-1+b1 ii libqt4-dbus 4:4.8.7+dfsg-6 ii libqt4-qt3support 4:4.8.7+dfsg-6 ii libqt4-xml 4:4.8.7+dfsg-6 ii libqtcore4 4:4.8.7+dfsg-6 ii libqtgui4 4:4.8.7+dfsg-6 ii libstdc++6 5.3.1-13 ii libx11-62:1.6.3-1 Versions of packages konqueror recommends: pn dolphin4 ii kfind4:15.08.3-1 ii konqueror-nsplugins 4:15.08.3-1 ii kpart-webkit 1.3.4-2 Versions of packages konqueror suggests: ii konq-plugins 4:15.08.3-1 -- no debconf information
Bug#265795: Detailed explanation of the bug preventing user login
I think it is important to give a precise explanation of the bug reported by many people about an impossibility of logging in using the new kdm version, for the mantainer to reproduce it, and fix it properly. Description: After the upgrade to kdm 3.3.0-1, some users discover that they can no longer log in (kdm accepts the password, then nothing happens and the login screen appears again). Explanation: The new /etc/kde3/kdm/Xsession in kdm 3.3.0-1 tries to do some smart things, that include sourcing the appropriate environment variables depending on the user shell, and here is where the mechanics of the seeming irreproducibility of the bug lies. The code handling csh/tcsh is made up of the following lines */csh|*/tcsh) # [t]cshrc is always sourced automatically. # Note that sourcing csh.login after .cshrc is non-standard. set -a eval `$SHELL -c 'if (-f /etc/csh.login) source /etc/csh.login; if (-f ~/.login) source ~/.login; /bin/sh -c set | egrep -v "^(BASH_VERSINFO|EUID|PPID|UID|_)="'` set +a ;; Now, IF /bin/sh on the machine happens to be actually a link to bash, everything works like a charm, BUT if /bin/sh is just the usual, plain old sh, then the execution of this line simply aborts the execution of the /etc/kde3/kdm/Xsession script (notice that the first line of the file is also #! /bin/sh, invoking /bin/sh that on many machines is an alias for /bin/bash, but not on all machines). As a consequence, on a machine where the user has csh/tcsh as shell, AND /bin/sh is NOT the same as /bin/bash, Xsession aborts, and the user sees the surprising behaviour of kdm "resetting" Fix: On the machine I had at hand, I changed the occurrence of /bin/sh to /bin/bash in the first line of /etc/kde3/kdm/Xsession file, but of course, it would be better to understand WHY the execution of the script is stipped using the plain /bin/sh ... Hope this helps in getting a rock solid new version of kdm --Roberto Di Cosmo -- Professeur PPS E-mail: [EMAIL PROTECTED] Universite Paris VII WWW : http://www.dicosmo.org Case 7014 2, place Jussieu F-75251 Paris Cedex 05 FRANCE. -- Attachments: MIME accepted Word deprecated, http://www.rfc1149.net/documents/whynotword --
