Bug#1055432: kontact: Attaching file to email tries to mount filesystems
Package: kontact Version: 4:22.12.3-1 Severity: grave Justification: causes non-serious data loss Dear Maintainer, Kontact email composition window "Attach file" should not try to mount filesystems that aren't already mounted and the user does not explicitly try to enter. Reproduce: 1. Set up an automounted filesystem, e.g. at /mnt/foobar 2. Mount it 3. Add /mnt/foobar to the sidebar either in Places, Recent Locations, or Remote, do not enter the directory (or come out of it after so it's not the last one you were in while the dialog is open) 4. Close the compose window 5. Umount /mnt/foobar 6. Compose another email and attach a file: /mnt/foobar gets mounted. I appreciate this is an attempt to be helpful, gathering information about known mountpoints, but the nature of autofs mountpoints is that they are not guaranteed to be always available to be mounted so causing an attempt to mount them without user explicitly asking for it is not good. This is especially bad when the mountpoint is an NFS mount: kontact will hang until autofs succeeds in mounting it. If the NFS server is never coming back, data loss follows as kontact will never recover from an uninterruptible system call. This is also highly annoying even when the server is available but /mnt/foobar is not yet mounted: opening the file selection dialog takes as long as it takes for the mount to finish, which is long enough to be annoying. Kontact needs to be selective in its helpfulness: avoid causing autofs mounts to be triggered if they are not yet mounted unless explicitly requested by the user. Cheers, Juha -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.4.0-2-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages kontact depends on: ii kdepim-runtime 4:22.12.3-2 ii libc62.37-12 ii libkf5configcore55.107.0-1 ii libkf5configgui5 5.107.0-1 ii libkf5configwidgets5 5.107.0-2 ii libkf5coreaddons55.107.0-1 ii libkf5crash5 5.107.0-1 ii libkf5grantleetheme5 [libkf5grantleetheme5-22.12]22.12.3-2+b1 ii libkf5guiaddons5 5.107.0-1 ii libkf5i18n5 5.107.0-1+b1 ii libkf5jobwidgets55.107.0-1 ii libkf5kcmutils5 5.107.0-2 ii libkf5kiogui55.107.0-1 ii libkf5kontactinterface5 [libkf5kontactinterface5-22.12] 22.12.3-1 ii libkf5libkdepim5 [libkf5libkdepim5-22.12]4:22.12.3-1 ii libkf5parts5 5.107.0-1 ii libkf5pimcommon5abi2 [libkf5pimcommon5-22.12]4:22.12.3-1 ii libkf5service-bin5.107.0-1 ii libkf5service5 5.107.0-1 ii libkf5widgetsaddons5 5.107.0-1 ii libkf5windowsystem5 5.107.0-1 ii libkf5xmlgui55.107.0-1+b1 ii libqt5core5a 5.15.10+dfsg-4 ii libqt5dbus5 5.15.10+dfsg-4 ii libqt5gui5 5.15.10+dfsg-4 ii libqt5webengine5 5.15.15+dfsg-2+b1 ii libqt5webenginecore5 5.15.15+dfsg-2+b1 ii libqt5webenginewidgets5 5.15.15+dfsg-2+b1 ii libqt5widgets5 5.15.10+dfsg-4 ii libstdc++6 13.2.0-6 Versions of packages kontact recommends: ii accountwizard 4:22.12.3-1 ii akregator 4:22.12.3-1 ii kaddressbook 4:22.12.3-1 ii kmail 4:22.12.3-1 ii knotes 4:22.12.3-1 ii korganizer 4:22.12.3-1 Versions of packages kontact suggests: pn gnokii -- no debconf information
Bug#923490: Do you still have this problem?
This no longer happens. Thanks for reminding me of the open bug. Please close as far as I'm concerned.
Bug#1000286: kdepim: akonadi_maildispatcher_agent fails to retrieve saved passwords
Package: kdepim Version: 4:21.08.1+5.115 Severity: normal Dear Maintainer, As of the upgrade to 4:21.08.1+5.113, kmail has been unable to send emails without asking for password. It looks like akonadi_maildispatcher_agent fails to retrieve the password from kwallet. akonadi_maildispatcher_agent is authorised to use the wallet and will even save the password there (on the first send on a new acccount), but never retrieves it from the despite it being there. Reproduce: create a new outgoing account, click "save password", send email, enter password, email goes out fine. Check kwallet: password has been saved, but send another email and kmail asks for password again instead of getting it from the wallet. Cheers, Juha -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.14.0-3-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_WARN Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages kdepim depends on: ii accountwizard4:21.08.1-1+b1 ii akonadiconsole 4:21.08.1-1+b1 ii akregator4:21.08.1-1+b1 ii kaddressbook 4:21.08.1-1+b1 ii kalarm 4:21.08.1-1+b1 ii kdepim-runtime 4:21.08.1-1+b1 ii kleopatra4:21.08.1-2 ii kmail4:21.08.1-1+b1 ii knotes 4:21.08.1-1+b1 ii konsolekalendar 4:21.08.1-1+b1 ii kontact 4:21.08.1-1+b1 ii korganizer 4:21.08.1-1+b1 Versions of packages kdepim recommends: ii kdepim-addons 21.08.1-2 kdepim suggests no packages. -- no debconf information
Bug#932080: sssd fails to start: #886483 raises from the dead
Package: sssd Version: 2.2.0-3 Severity: grave Justification: renders package unusable After upgrading to 2.2.0-3, sssd will not start (automatically). There are two failure modes, both likely related to #886483 I reported over a year ago. First failure mode happens if any services are listed in sssd.conf like (any service here will cause failure) service = pam, nss Startig sssd with systemctl will now (correctly) start the listed services, BUT it will also insist on trying to start the corresponding socket listener, which times out trying to get the socket, eventually causing systemd to kill the whole stack of processes, leaving no sssd processes running. It is, however, possible to start sssd manually from command line: "sssd -i" works as expected. Second failure mode is triggered by trying the obvious: commenting out the whole "service" line from sssd.conf. However, now sssd fails both from command line and from systemd because "sssd: SSSD couldn't load the configuration database [22]: Invalid argument." There does not seem to be any way of disabling all non-socket services but if at least one non-socket service is active, systemd will time out trying to load the corresponding socket. I even removed every .socket file related to sssd from my systemd but it didn't help (yes, I did a daemon-reexec and daemon-reload). Only fix I managed to find is a downgrade to 1.16.3-3.1. Cheers, Juha -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system)
Bug#923562: kmail: fails to copy sent email to sent mail folder
Package: kmail Version: 4:18.08.3-1 Severity: important Dear Maintainer, * What led up to the situation? I replied to an email in the Inbox of an imap account, which is set up to keep replies in the same folder. * What exactly did you do (or not do) that was effective (or ineffective)? Compose message, hit Control-Enter, answered "send as is" to the query about sending an unsigned message. * What was the outcome of this action? After a pause of several minutes, kmail claims the mail was sent, but that it failed to place a copy of the message in the sent mail folder. Instead, the mail is left in unread state in Outbox, strongly suggesting no email was sent. Network connectivity existed throughout. * What outcome did you expect instead? Mail sent, copy placed in inbox. -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-2-amd64 (SMP w/2 CPU cores) Kernel taint flags: TAINT_WARN Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages kmail depends on: ii akonadi-server 4:18.08.3-4 ii kdepim-runtime 4:18.08.3-1 ii kio 5.54.1-1 ii libc62.28-7 ii libgcc1 1:8.2.0-21 ii libgpgmepp6 1.12.0-6 ii libkf5akonadiagentbase5 4:18.08.3-4 ii libkf5akonadicontact54:18.08.3-1 ii libkf5akonadicore5abi2 4:18.08.3-4 ii libkf5akonadimime5 4:18.08.3-1 ii libkf5akonadisearch-bin 4:18.08.3-1 ii libkf5akonadisearch-plugins 4:18.08.3-1 ii libkf5akonadisearchdebug54:18.08.3-1 ii libkf5akonadisearchpim5 4:18.08.3-1 ii libkf5akonadiwidgets5abi14:18.08.3-4 ii libkf5bookmarks5 5.54.0-1 ii libkf5calendarcore5abi2 4:18.08.3-1 ii libkf5calendarutils5 4:18.08.3-2 ii libkf5codecs55.54.0-1 ii libkf5completion55.54.0-1 ii libkf5configcore55.54.0-1 ii libkf5configgui5 5.54.0-1 ii libkf5configwidgets5 5.54.0-1 ii libkf5contacts5 4:18.08.3-1 ii libkf5coreaddons55.54.0-1 ii libkf5crash5 5.54.0-1 ii libkf5dbusaddons55.54.0-1 ii libkf5followupreminder5 4:18.08.3-2 ii libkf5grantleetheme-plugins 18.08.3-1 ii libkf5gravatar5abi2 4:18.08.3-1 ii libkf5guiaddons5 5.54.0-1 ii libkf5i18n5 5.54.0-1 ii libkf5iconthemes55.54.0-1 ii libkf5identitymanagement518.08.3-2 ii libkf5itemmodels55.54.0-1 ii libkf5itemviews5 5.54.0-1 ii libkf5jobwidgets55.54.0-1 ii libkf5kcmutils5 5.54.0-1 ii libkf5kiocore5 5.54.1-1 ii libkf5kiofilewidgets55.54.1-1 ii libkf5kiowidgets55.54.1-1 ii libkf5kontactinterface5 18.08.3-1 ii libkf5ksieveui5 4:18.08.3-2 ii libkf5libkdepim-plugins 4:18.08.3-2 ii libkf5libkdepim5 4:18.08.3-2 ii libkf5libkdepimakonadi5 4:18.08.3-2 ii libkf5libkleo5 4:18.08.3-2 ii libkf5mailcommon5abi24:18.08.3-2 ii libkf5mailtransport5 18.08.3-2 ii libkf5mailtransportakonadi5 18.08.3-2 ii libkf5messagecomposer5abi1 4:18.08.3-1 ii libkf5messagecore5abi1 4:18.08.3-1 ii libkf5messagelist5abi1 4:18.08.3-1 ii libkf5messageviewer5abi1 4:18.08.3-1 ii libkf5mime5abi1 18.08.3-1 ii libkf5mimetreeparser5abi14:18.08.3-1 ii libkf5notifications5 5.54.0-1 ii libkf5notifyconfig5 5.54.0-1 ii libkf5parts5 5.54.0-1 ii libkf5pimcommon5abi2 4:18.08.3-2 ii libkf5pimcommonakonadi5abi1 4:18.08.3-2 ii libkf5pimtextedit5abi2 18.08.3-1 ii libkf5sendlater5 4:18.08.3-2 ii libkf5service-bin5.54.0-1 ii libkf5service5 5.54.0-1 ii libkf5sonnetui5 5.54.0-1 ii libkf5templateparser54:18.08.3-1 ii libkf5textwidgets5 5.54.0-1 ii libkf5tnef5 4:18.08.3-1 ii libkf5wallet-bin 5.54.0-1 ii libkf5wallet55.54.0-1 ii libkf5webengineviewer5abi1 4:18.08.3-1 ii libkf5widgetsaddons5 5.54.0-1 ii libkf5windowsystem5 5.54.0-1 ii libkf5xmlgui55.54.0-1 ii libqgpgme7 1.12.0-6 ii libqt5core5a 5.11.3+dfsg-5 ii libqt5dbus5 5.11.3+dfsg-5 ii libqt5gui5 5.11.3+dfsg-5 ii libqt5network5 5.11.3+dfsg-5 ii libqt5widgets5 5.11.3+dfsg-5 ii libqt5xml5 5.11.3+dfsg-5 ii libstdc++6
Bug#923490: kmail: random segfaults while idle
Package: kmail Version: 4:18.08.3-1 Severity: important Dear Maintainer, Kmail sometimes sigsegvs while (seemingly) idle. Needless to say this seriously degrades its usability. I think this has only ever happened while moving the mouse pointer across the window. Just moving, not clicking anything, not using mouse scroll wheel, just moving the pointer, not even stopping while kmail window is focused, so tooltip texts etc should not be activating. Backtrace follows. Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7c358dbf00 (LWP 7560))] Thread 39 (Thread 0x7f7b44bec700 (LWP 9712)): #0 0x7f7c4afc63a9 in futex_reltimed_wait_cancelable (private=0, reltime=0x7f7b44beb400, expected=0, futex_word=0x7f7b44beb5e8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7f7c4afc63a9 in __pthread_cond_wait_common (abstime=0x7f7b44beb4a0, mutex=0x7f7b44beb598, cond=0x7f7b44beb5c0) at pthread_cond_wait.c:533 #2 0x7f7c4afc63a9 in __pthread_cond_timedwait (cond=0x7f7b44beb5c0, mutex=0x7f7b44beb598, abstime=0x7f7b44beb4a0) at pthread_cond_wait.c:667 #3 0x7f7c4480fa37 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f7c4481230a in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f7c448123f2 in base::WaitableEvent::TimedWait(base::TimeDelta const&) () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f7c44816981 in base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f7c44817c7f in base::internal::SchedulerWorker::Thread::ThreadMain() () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f7c44820c81 in base::(anonymous namespace)::ThreadFunc(void*) () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f7c4afbffa3 in start_thread (arg=) at pthread_create.c:486 #10 0x7f7c4d78680f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 38 (Thread 0x7f7b453ed700 (LWP 9711)): #0 0x7f7c4afc63a9 in futex_reltimed_wait_cancelable (private=0, reltime=0x7f7b453ec400, expected=0, futex_word=0x7f7b453ec5e8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7f7c4afc63a9 in __pthread_cond_wait_common (abstime=0x7f7b453ec4a0, mutex=0x7f7b453ec598, cond=0x7f7b453ec5c0) at pthread_cond_wait.c:533 #2 0x7f7c4afc63a9 in __pthread_cond_timedwait (cond=0x7f7b453ec5c0, mutex=0x7f7b453ec598, abstime=0x7f7b453ec4a0) at pthread_cond_wait.c:667 #3 0x7f7c4480fa37 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f7c4481230a in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f7c448123f2 in base::WaitableEvent::TimedWait(base::TimeDelta const&) () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f7c44816981 in base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f7c44817e61 in base::internal::SchedulerWorker::Thread::ThreadMain() () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f7c44820c81 in base::(anonymous namespace)::ThreadFunc(void*) () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f7c4afbffa3 in start_thread (arg=) at pthread_create.c:486 #10 0x7f7c4d78680f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 37 (Thread 0x7f7b4df11700 (LWP 9710)): #0 0x7f7c4afc63a9 in futex_reltimed_wait_cancelable (private=0, reltime=0x7f7b4df10400, expected=0, futex_word=0x7f7b4df105e8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7f7c4afc63a9 in __pthread_cond_wait_common (abstime=0x7f7b4df104a0, mutex=0x7f7b4df10598, cond=0x7f7b4df105c0) at pthread_cond_wait.c:533 #2 0x7f7c4afc63a9 in __pthread_cond_timedwait (cond=0x7f7b4df105c0, mutex=0x7f7b4df10598, abstime=0x7f7b4df104a0) at pthread_cond_wait.c:667 #3 0x7f7c4480fa37 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f7c4481230a in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f7c448123f2 in base::WaitableEvent::TimedWait(base::TimeDelta const&) () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f7c44816981 in base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f7c44817e61 in base::internal::SchedulerWorker::Thread::ThreadMain() () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
Bug#923292: kmail randomly crashes when closing windows
Package: kmail Version: 4:18.08.3-1 Severity: normal Dear Maintainer, I do not like the "message preview pane", so I open each message in a separate window to read them. Sometimes, and as far as I can tell, at random, kmail will crash with a SIGSEGV when such message window OR compose message window is closed. It does not matter what causes the window to close, even sending a message sometimes causes a crash. Cheers, Juha -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-2-amd64 (SMP w/2 CPU cores) Kernel taint flags: TAINT_WARN Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages kmail depends on: ii akonadi-server 4:18.08.3-4 ii kdepim-runtime 4:18.08.3-1 ii kio 5.54.1-1 ii libc62.28-7 ii libgcc1 1:8.2.0-21 ii libgpgmepp6 1.12.0-6 ii libkf5akonadiagentbase5 4:18.08.3-4 ii libkf5akonadicontact54:18.08.3-1 ii libkf5akonadicore5abi2 4:18.08.3-4 ii libkf5akonadimime5 4:18.08.3-1 ii libkf5akonadisearch-bin 4:18.08.3-1 ii libkf5akonadisearch-plugins 4:18.08.3-1 ii libkf5akonadisearchdebug54:18.08.3-1 ii libkf5akonadisearchpim5 4:18.08.3-1 ii libkf5akonadiwidgets5abi14:18.08.3-4 ii libkf5bookmarks5 5.54.0-1 ii libkf5calendarcore5abi2 4:18.08.3-1 ii libkf5calendarutils5 4:18.08.3-2 ii libkf5codecs55.54.0-1 ii libkf5completion55.54.0-1 ii libkf5configcore55.54.0-1 ii libkf5configgui5 5.54.0-1 ii libkf5configwidgets5 5.54.0-1 ii libkf5contacts5 4:18.08.3-1 ii libkf5coreaddons55.54.0-1 ii libkf5crash5 5.54.0-1 ii libkf5dbusaddons55.54.0-1 ii libkf5followupreminder5 4:18.08.3-2 ii libkf5grantleetheme-plugins 18.08.3-1 ii libkf5gravatar5abi2 4:18.08.3-1 ii libkf5guiaddons5 5.54.0-1 ii libkf5i18n5 5.54.0-1 ii libkf5iconthemes55.54.0-1 ii libkf5identitymanagement518.08.3-2 ii libkf5itemmodels55.54.0-1 ii libkf5itemviews5 5.54.0-1 ii libkf5jobwidgets55.54.0-1 ii libkf5kcmutils5 5.54.0-1 ii libkf5kiocore5 5.54.1-1 ii libkf5kiofilewidgets55.54.1-1 ii libkf5kiowidgets55.54.1-1 ii libkf5kontactinterface5 18.08.3-1 ii libkf5ksieveui5 4:18.08.3-2 ii libkf5libkdepim-plugins 4:18.08.3-2 ii libkf5libkdepim5 4:18.08.3-2 ii libkf5libkdepimakonadi5 4:18.08.3-2 ii libkf5libkleo5 4:18.08.3-2 ii libkf5mailcommon5abi24:18.08.3-2 ii libkf5mailtransport5 18.08.3-2 ii libkf5mailtransportakonadi5 18.08.3-2 ii libkf5messagecomposer5abi1 4:18.08.3-1 ii libkf5messagecore5abi1 4:18.08.3-1 ii libkf5messagelist5abi1 4:18.08.3-1 ii libkf5messageviewer5abi1 4:18.08.3-1 ii libkf5mime5abi1 18.08.3-1 ii libkf5mimetreeparser5abi14:18.08.3-1 ii libkf5notifications5 5.54.0-1 ii libkf5notifyconfig5 5.54.0-1 ii libkf5parts5 5.54.0-1 ii libkf5pimcommon5abi2 4:18.08.3-2 ii libkf5pimcommonakonadi5abi1 4:18.08.3-2 ii libkf5pimtextedit5abi2 18.08.3-1 ii libkf5sendlater5 4:18.08.3-2 ii libkf5service-bin5.54.0-1 ii libkf5service5 5.54.0-1 ii libkf5sonnetui5 5.54.0-1 ii libkf5templateparser54:18.08.3-1 ii libkf5textwidgets5 5.54.0-1 ii libkf5tnef5 4:18.08.3-1 ii libkf5wallet-bin 5.54.0-1 ii libkf5wallet55.54.0-1 ii libkf5webengineviewer5abi1 4:18.08.3-1 ii libkf5widgetsaddons5 5.54.0-1 ii libkf5windowsystem5 5.54.0-1 ii libkf5xmlgui55.54.0-1 ii libqgpgme7 1.12.0-6 ii libqt5core5a 5.11.3+dfsg-5 ii libqt5dbus5 5.11.3+dfsg-5 ii libqt5gui5 5.11.3+dfsg-5 ii libqt5network5 5.11.3+dfsg-5 ii libqt5widgets5 5.11.3+dfsg-5 ii libqt5xml5 5.11.3+dfsg-5 ii libstdc++6 8.2.0-21 Versions of packages kmail recommends: ii accountwizard 4:18.08.3-1 ii gnupg 2.2.12-1 ii kdepim-addons 18.08.3-1 ii kdepim-themeeditors 4:18.08.3-1 ii mbox-importer 4:18.08.3-1 ii pim-data-exporter 4:18.08.3-1 ii pim-sieve-editor
Bug#923293: kmail: mailbox contents displayed wrong
Package: kmail Version: 4:18.08.3-1 Severity: normal Dear Maintainer, kmail will often show mailbox contents wrong: it will show the correct number of unread messages in the folders pane, but the actual messages displayed do not show all those unread messages (presumably not all read messages are shown either but not sure). Checking the akonadi status from akonadiconsole shows all the messages, including the ones kmail does not show, so kmail somehow gets out of sync with akonadi. This can be worked around by restarting kmail, but given the frequency that this happens, several times a day, it makes kmail's usability quite abysmal. Cheers, Juha -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-2-amd64 (SMP w/2 CPU cores) Kernel taint flags: TAINT_WARN Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages kmail depends on: ii akonadi-server 4:18.08.3-4 ii kdepim-runtime 4:18.08.3-1 ii kio 5.54.1-1 ii libc62.28-7 ii libgcc1 1:8.2.0-21 ii libgpgmepp6 1.12.0-6 ii libkf5akonadiagentbase5 4:18.08.3-4 ii libkf5akonadicontact54:18.08.3-1 ii libkf5akonadicore5abi2 4:18.08.3-4 ii libkf5akonadimime5 4:18.08.3-1 ii libkf5akonadisearch-bin 4:18.08.3-1 ii libkf5akonadisearch-plugins 4:18.08.3-1 ii libkf5akonadisearchdebug54:18.08.3-1 ii libkf5akonadisearchpim5 4:18.08.3-1 ii libkf5akonadiwidgets5abi14:18.08.3-4 ii libkf5bookmarks5 5.54.0-1 ii libkf5calendarcore5abi2 4:18.08.3-1 ii libkf5calendarutils5 4:18.08.3-2 ii libkf5codecs55.54.0-1 ii libkf5completion55.54.0-1 ii libkf5configcore55.54.0-1 ii libkf5configgui5 5.54.0-1 ii libkf5configwidgets5 5.54.0-1 ii libkf5contacts5 4:18.08.3-1 ii libkf5coreaddons55.54.0-1 ii libkf5crash5 5.54.0-1 ii libkf5dbusaddons55.54.0-1 ii libkf5followupreminder5 4:18.08.3-2 ii libkf5grantleetheme-plugins 18.08.3-1 ii libkf5gravatar5abi2 4:18.08.3-1 ii libkf5guiaddons5 5.54.0-1 ii libkf5i18n5 5.54.0-1 ii libkf5iconthemes55.54.0-1 ii libkf5identitymanagement518.08.3-2 ii libkf5itemmodels55.54.0-1 ii libkf5itemviews5 5.54.0-1 ii libkf5jobwidgets55.54.0-1 ii libkf5kcmutils5 5.54.0-1 ii libkf5kiocore5 5.54.1-1 ii libkf5kiofilewidgets55.54.1-1 ii libkf5kiowidgets55.54.1-1 ii libkf5kontactinterface5 18.08.3-1 ii libkf5ksieveui5 4:18.08.3-2 ii libkf5libkdepim-plugins 4:18.08.3-2 ii libkf5libkdepim5 4:18.08.3-2 ii libkf5libkdepimakonadi5 4:18.08.3-2 ii libkf5libkleo5 4:18.08.3-2 ii libkf5mailcommon5abi24:18.08.3-2 ii libkf5mailtransport5 18.08.3-2 ii libkf5mailtransportakonadi5 18.08.3-2 ii libkf5messagecomposer5abi1 4:18.08.3-1 ii libkf5messagecore5abi1 4:18.08.3-1 ii libkf5messagelist5abi1 4:18.08.3-1 ii libkf5messageviewer5abi1 4:18.08.3-1 ii libkf5mime5abi1 18.08.3-1 ii libkf5mimetreeparser5abi14:18.08.3-1 ii libkf5notifications5 5.54.0-1 ii libkf5notifyconfig5 5.54.0-1 ii libkf5parts5 5.54.0-1 ii libkf5pimcommon5abi2 4:18.08.3-2 ii libkf5pimcommonakonadi5abi1 4:18.08.3-2 ii libkf5pimtextedit5abi2 18.08.3-1 ii libkf5sendlater5 4:18.08.3-2 ii libkf5service-bin5.54.0-1 ii libkf5service5 5.54.0-1 ii libkf5sonnetui5 5.54.0-1 ii libkf5templateparser54:18.08.3-1 ii libkf5textwidgets5 5.54.0-1 ii libkf5tnef5 4:18.08.3-1 ii libkf5wallet-bin 5.54.0-1 ii libkf5wallet55.54.0-1 ii libkf5webengineviewer5abi1 4:18.08.3-1 ii libkf5widgetsaddons5 5.54.0-1 ii libkf5windowsystem5 5.54.0-1 ii libkf5xmlgui55.54.0-1 ii libqgpgme7 1.12.0-6 ii libqt5core5a 5.11.3+dfsg-5 ii libqt5dbus5 5.11.3+dfsg-5 ii libqt5gui5 5.11.3+dfsg-5 ii libqt5network5 5.11.3+dfsg-5 ii libqt5widgets5 5.11.3+dfsg-5 ii libqt5xml5 5.11.3+dfsg-5 ii libstdc++6 8.2.0-21 Versions of packages kmail recommends: ii accountwizard 4:18.08.3-1 ii gnupg
Bug#923291: kmail: syncing inbox(es) never finishes
Package: kmail Version: 4:18.08.3-1 Severity: normal Dear Maintainer, Very often, almost as often as not, syncing an imap inbox never finishes. It will get stuck at any progress level, from 0% to 100% (yes, it even gets stuck at 100%). This happens with at least google's imap servers as well as three different dovecot servers. Steps to reprocude: start kmail, let it run for a while, checking inboxes either manually or letting the automatic interval check do it for you. In less than 15 minutes at least one of the inboxes gets stuck. Sometimes normal operation can only be recovered by manually restarting the stuck agent, but sometimes only restarting the whole akonadi sorts it out. This makes kmail unusable for me due to the frequency of restarts: often I need to restart aknoadi between each two emails I read. Assuming this is not widespread, because if this is, the bug should be RC. Cheers, Juha -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-2-amd64 (SMP w/2 CPU cores) Kernel taint flags: TAINT_WARN Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages kmail depends on: ii akonadi-server 4:18.08.3-4 ii kdepim-runtime 4:18.08.3-1 ii kio 5.54.1-1 ii libc62.28-7 ii libgcc1 1:8.2.0-21 ii libgpgmepp6 1.12.0-6 ii libkf5akonadiagentbase5 4:18.08.3-4 ii libkf5akonadicontact54:18.08.3-1 ii libkf5akonadicore5abi2 4:18.08.3-4 ii libkf5akonadimime5 4:18.08.3-1 ii libkf5akonadisearch-bin 4:18.08.3-1 ii libkf5akonadisearch-plugins 4:18.08.3-1 ii libkf5akonadisearchdebug54:18.08.3-1 ii libkf5akonadisearchpim5 4:18.08.3-1 ii libkf5akonadiwidgets5abi14:18.08.3-4 ii libkf5bookmarks5 5.54.0-1 ii libkf5calendarcore5abi2 4:18.08.3-1 ii libkf5calendarutils5 4:18.08.3-2 ii libkf5codecs55.54.0-1 ii libkf5completion55.54.0-1 ii libkf5configcore55.54.0-1 ii libkf5configgui5 5.54.0-1 ii libkf5configwidgets5 5.54.0-1 ii libkf5contacts5 4:18.08.3-1 ii libkf5coreaddons55.54.0-1 ii libkf5crash5 5.54.0-1 ii libkf5dbusaddons55.54.0-1 ii libkf5followupreminder5 4:18.08.3-2 ii libkf5grantleetheme-plugins 18.08.3-1 ii libkf5gravatar5abi2 4:18.08.3-1 ii libkf5guiaddons5 5.54.0-1 ii libkf5i18n5 5.54.0-1 ii libkf5iconthemes55.54.0-1 ii libkf5identitymanagement518.08.3-2 ii libkf5itemmodels55.54.0-1 ii libkf5itemviews5 5.54.0-1 ii libkf5jobwidgets55.54.0-1 ii libkf5kcmutils5 5.54.0-1 ii libkf5kiocore5 5.54.1-1 ii libkf5kiofilewidgets55.54.1-1 ii libkf5kiowidgets55.54.1-1 ii libkf5kontactinterface5 18.08.3-1 ii libkf5ksieveui5 4:18.08.3-2 ii libkf5libkdepim-plugins 4:18.08.3-2 ii libkf5libkdepim5 4:18.08.3-2 ii libkf5libkdepimakonadi5 4:18.08.3-2 ii libkf5libkleo5 4:18.08.3-2 ii libkf5mailcommon5abi24:18.08.3-2 ii libkf5mailtransport5 18.08.3-2 ii libkf5mailtransportakonadi5 18.08.3-2 ii libkf5messagecomposer5abi1 4:18.08.3-1 ii libkf5messagecore5abi1 4:18.08.3-1 ii libkf5messagelist5abi1 4:18.08.3-1 ii libkf5messageviewer5abi1 4:18.08.3-1 ii libkf5mime5abi1 18.08.3-1 ii libkf5mimetreeparser5abi14:18.08.3-1 ii libkf5notifications5 5.54.0-1 ii libkf5notifyconfig5 5.54.0-1 ii libkf5parts5 5.54.0-1 ii libkf5pimcommon5abi2 4:18.08.3-2 ii libkf5pimcommonakonadi5abi1 4:18.08.3-2 ii libkf5pimtextedit5abi2 18.08.3-1 ii libkf5sendlater5 4:18.08.3-2 ii libkf5service-bin5.54.0-1 ii libkf5service5 5.54.0-1 ii libkf5sonnetui5 5.54.0-1 ii libkf5templateparser54:18.08.3-1 ii libkf5textwidgets5 5.54.0-1 ii libkf5tnef5 4:18.08.3-1 ii libkf5wallet-bin 5.54.0-1 ii libkf5wallet55.54.0-1 ii libkf5webengineviewer5abi1 4:18.08.3-1 ii libkf5widgetsaddons5 5.54.0-1 ii libkf5windowsystem5 5.54.0-1 ii libkf5xmlgui55.54.0-1 ii libqgpgme7 1.12.0-6 ii libqt5core5a 5.11.3+dfsg-5 ii libqt5dbus5 5.11.3+dfsg-5 ii libqt5gui5 5.11.3+dfsg-5 ii libqt5network5 5.11.3+dfsg-5 ii
Bug#923288: kmail does not exit
Package: kmail Version: 4:18.08.3-1 Severity: normal Dear Maintainer, kmail randomly refuses to exit. Upon closing the window or choosing to quit from the menu, the window disappears, but the process lingers and will not exit until given a TERM or KILL. Trying to start a new copy does nothing (presumably because the old copy is still alive). Cheers, Juha *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-2-amd64 (SMP w/2 CPU cores) Kernel taint flags: TAINT_WARN Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages kmail depends on: ii akonadi-server 4:18.08.3-4 ii kdepim-runtime 4:18.08.3-1 ii kio 5.54.1-1 ii libc62.28-7 ii libgcc1 1:8.2.0-21 ii libgpgmepp6 1.12.0-6 ii libkf5akonadiagentbase5 4:18.08.3-4 ii libkf5akonadicontact54:18.08.3-1 ii libkf5akonadicore5abi2 4:18.08.3-4 ii libkf5akonadimime5 4:18.08.3-1 ii libkf5akonadisearch-bin 4:18.08.3-1 ii libkf5akonadisearch-plugins 4:18.08.3-1 ii libkf5akonadisearchdebug54:18.08.3-1 ii libkf5akonadisearchpim5 4:18.08.3-1 ii libkf5akonadiwidgets5abi14:18.08.3-4 ii libkf5bookmarks5 5.54.0-1 ii libkf5calendarcore5abi2 4:18.08.3-1 ii libkf5calendarutils5 4:18.08.3-2 ii libkf5codecs55.54.0-1 ii libkf5completion55.54.0-1 ii libkf5configcore55.54.0-1 ii libkf5configgui5 5.54.0-1 ii libkf5configwidgets5 5.54.0-1 ii libkf5contacts5 4:18.08.3-1 ii libkf5coreaddons55.54.0-1 ii libkf5crash5 5.54.0-1 ii libkf5dbusaddons55.54.0-1 ii libkf5followupreminder5 4:18.08.3-2 ii libkf5grantleetheme-plugins 18.08.3-1 ii libkf5gravatar5abi2 4:18.08.3-1 ii libkf5guiaddons5 5.54.0-1 ii libkf5i18n5 5.54.0-1 ii libkf5iconthemes55.54.0-1 ii libkf5identitymanagement518.08.3-2 ii libkf5itemmodels55.54.0-1 ii libkf5itemviews5 5.54.0-1 ii libkf5jobwidgets55.54.0-1 ii libkf5kcmutils5 5.54.0-1 ii libkf5kiocore5 5.54.1-1 ii libkf5kiofilewidgets55.54.1-1 ii libkf5kiowidgets55.54.1-1 ii libkf5kontactinterface5 18.08.3-1 ii libkf5ksieveui5 4:18.08.3-2 ii libkf5libkdepim-plugins 4:18.08.3-2 ii libkf5libkdepim5 4:18.08.3-2 ii libkf5libkdepimakonadi5 4:18.08.3-2 ii libkf5libkleo5 4:18.08.3-2 ii libkf5mailcommon5abi24:18.08.3-2 ii libkf5mailtransport5 18.08.3-2 ii libkf5mailtransportakonadi5 18.08.3-2 ii libkf5messagecomposer5abi1 4:18.08.3-1 ii libkf5messagecore5abi1 4:18.08.3-1 ii libkf5messagelist5abi1 4:18.08.3-1 ii libkf5messageviewer5abi1 4:18.08.3-1 ii libkf5mime5abi1 18.08.3-1 ii libkf5mimetreeparser5abi14:18.08.3-1 ii libkf5notifications5 5.54.0-1 ii libkf5notifyconfig5 5.54.0-1 ii libkf5parts5 5.54.0-1 ii libkf5pimcommon5abi2 4:18.08.3-2 ii libkf5pimcommonakonadi5abi1 4:18.08.3-2 ii libkf5pimtextedit5abi2 18.08.3-1 ii libkf5sendlater5 4:18.08.3-2 ii libkf5service-bin5.54.0-1 ii libkf5service5 5.54.0-1 ii libkf5sonnetui5 5.54.0-1 ii libkf5templateparser54:18.08.3-1 ii libkf5textwidgets5 5.54.0-1 ii libkf5tnef5 4:18.08.3-1 ii libkf5wallet-bin 5.54.0-1 ii libkf5wallet55.54.0-1 ii libkf5webengineviewer5abi1 4:18.08.3-1 ii libkf5widgetsaddons5 5.54.0-1 ii libkf5windowsystem5 5.54.0-1 ii libkf5xmlgui55.54.0-1 ii libqgpgme7 1.12.0-6 ii libqt5core5a 5.11.3+dfsg-5 ii libqt5dbus5 5.11.3+dfsg-5 ii libqt5gui5 5.11.3+dfsg-5 ii libqt5network5 5.11.3+dfsg-5 ii libqt5widgets5 5.11.3+dfsg-5 ii libqt5xml5 5.11.3+dfsg-5 ii libstdc++6 8.2.0-21 Versions of packages kmail recommends: ii accountwizard 4:18.08.3-1
Bug#910531: kdepim-runtime: Authenticating to gmail using "Gmail" authentication type (oauth, kgapi?) leads to segfault
Package: kdepim-runtime Version: 4:18.08.1-1 Severity: grave Justification: renders package unusable Dear Maintainer, The "Gmail" authentication type [1] no longer works. Using it for existing akonadi gmail accounts or creating a new one, always results in a sigsegv (backtrace can be found at http://paste.debian.net/1046257/). This renders all gmail accounts with proper security unusable. There is a workaround, which reduces security: Allowing unsecure access and then creating an application password for akonadi, allows login and continued access to emails, but with significantly reduced security. Not sure if this is "grave": without the workaround I would imagine this warrants grave due to the ubiquitousness of gmail and with the workaround this causes a nasty decrease in security. [1] This is the authentication method listed in "Advanced" options in the account config. I am not sure what it actually is, but I suppose it uses libsasl2-modules-kdexoauth2. Cheers, Juha -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages kdepim-runtime depends on: ii akonadi-server 4:18.08.1-1 ii kio 5.49.0-1 ii kio-ldap 18.08.1-1 ii kio-sieve4:18.08.1-1 ii libc62.27-6 ii libgcc1 1:8.2.0-7 ii libkf5akonadiagentbase5 4:18.08.1-1 ii libkf5akonadicalendar5abi1 4:18.08.1-1 ii libkf5akonadicontact54:18.08.1-1 ii libkf5akonadicore5abi2 4:18.08.1-1 ii libkf5akonadimime5 4:18.08.1-2 ii libkf5akonadinotes5 4:18.08.1-1 ii libkf5akonadiwidgets5abi14:18.08.1-1 ii libkf5alarmcalendar5abi1 4:18.08.1-1 ii libkf5calendarcore5abi2 4:18.08.1-1 ii libkf5codecs55.49.0-1 ii libkf5completion55.49.0-1 ii libkf5configcore55.49.0-1 ii libkf5configgui5 5.49.0-1 ii libkf5configwidgets5 5.49.0-1 ii libkf5contacts5 4:18.08.1-1 ii libkf5coreaddons55.49.0-1 ii libkf5dbusaddons55.49.0-1 ii libkf5i18n5 5.49.0-1 ii libkf5identitymanagement518.08.1-1 ii libkf5imap5 18.08.1-1 ii libkf5itemmodels55.49.0-1 ii libkf5jobwidgets55.49.0-1 ii libkf5kdelibs4support5 5.49.0-1 ii libkf5kiocore5 5.49.0-1 ii libkf5kiowidgets55.49.0-1 ii libkf5mailtransport5 18.08.1-1 ii libkf5mailtransportakonadi5 18.08.1-1 ii libkf5mbox5 18.08.1-1 ii libkf5mime5abi1 18.08.1-1 ii libkf5notifications5 5.49.0-1 ii libkf5notifyconfig5 5.49.0-1 ii libkf5service-bin5.49.0-1 ii libkf5service5 5.49.0-1 ii libkf5textwidgets5 5.49.0-1 ii libkf5wallet-bin 5.49.0-1 ii libkf5wallet55.49.0-1 ii libkf5widgetsaddons5 5.49.0-1 ii libkf5windowsystem5 5.49.0-1 ii libkf5xmlgui55.49.0-1 ii libkolabxml1v5 1.1.6-3+b1 ii libkpimgapicalendar5 18.08.1-1 ii libkpimgapicontacts5 18.08.1-1 ii libkpimgapicore5abi1 18.08.1-1 ii libkpimgapitasks518.08.1-1 ii libkpimkdav5abi2 18.08.1-1 ii libqt5core5a 5.11.1+dfsg-9 ii libqt5dbus5 5.11.1+dfsg-9 ii libqt5gui5 5.11.1+dfsg-9 ii libqt5network5 5.11.1+dfsg-9 ii libqt5texttospeech5 5.11.1-2 ii libqt5webenginecore5 5.11.1+dfsg-5 ii libqt5webenginewidgets5 5.11.1+dfsg-5 ii libqt5widgets5 5.11.1+dfsg-9 ii libqt5xml5 5.11.1+dfsg-9 ii libsasl2-2 2.1.27~rc8-1 ii libsasl2-modules-kdexoauth2 18.08.1-1 ii libstdc++6 8.2.0-7 kdepim-runtime recommends no packages. kdepim-runtime suggests no packages. -- no debconf information
Bug#901680: imagemagick-6.q16: convert / drawing primitives: colourspace handling broken
Package: imagemagick-6.q16 Version: 8:6.9.9.39+dfsg-1 Severity: normal Dear Maintainer, I would expect convert foo.pdf'[0]' -draw "fill # rectangle 40,225 560,280" broken.jpg convert foo.pdf'[0]' temp.jpeg; convert temp.jpeg -draw "fill # rectangle 40,225 560,280" broken.jpg convert foo.pdf'[0]' temp.png; convert temp.png -draw "fill # rectangle 40,225 560,280" broken.jpg all to produce the same resulting image. They do not. The first two draw a *black*, opaque rectangle, which by the way is semi-transparent when viewed in windows 10 "photos" application, and the third line creates a *white*, opaque rectangle. Obviously, all should create a white rectangle. Cheers, Juha -- Package-specific info: ImageMagick program version --- animate: ImageMagick 6.9.9-39 Q16 x86_64 20180318 http://www.imagemagick.org compare: ImageMagick 6.9.9-39 Q16 x86_64 20180318 http://www.imagemagick.org convert: ImageMagick 6.9.9-39 Q16 x86_64 20180318 http://www.imagemagick.org composite: ImageMagick 6.9.9-39 Q16 x86_64 20180318 http://www.imagemagick.org conjure: ImageMagick 6.9.9-39 Q16 x86_64 20180318 http://www.imagemagick.org display: ImageMagick 6.9.9-39 Q16 x86_64 20180318 http://www.imagemagick.org identify: ImageMagick 6.9.9-39 Q16 x86_64 20180318 http://www.imagemagick.org import: ImageMagick 6.9.9-39 Q16 x86_64 20180318 http://www.imagemagick.org mogrify: ImageMagick 6.9.9-39 Q16 x86_64 20180318 http://www.imagemagick.org montage: ImageMagick 6.9.9-39 Q16 x86_64 20180318 http://www.imagemagick.org stream: ImageMagick 6.9.9-39 Q16 x86_64 20180318 http://www.imagemagick.org -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.15.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages imagemagick-6.q16 depends on: ii hicolor-icon-theme 0.17-2 ii libc6 2.27-3 ii libmagickcore-6.q16-5 8:6.9.9.39+dfsg-1 ii libmagickwand-6.q16-5 8:6.9.9.39+dfsg-1 Versions of packages imagemagick-6.q16 recommends: ii ghostscript 9.22~dfsg-2.1 ii libmagickcore-6.q16-5-extra 8:6.9.9.39+dfsg-1 ii netpbm 2:10.0-15.3+b2 Versions of packages imagemagick-6.q16 suggests: pn autotrace ii cups-bsd [lpr] 2.2.8-3 ii curl 7.60.0-2 pn enscript ii ffmpeg 7:3.4.2-2+b2 ii gimp 2.10.2-1 ii gnuplot-x11 [gnuplot]5.2.2+dfsg1-2 pn grads ii graphviz 2.40.1-3 ii groff-base 1.22.3-10 pn hp2xx pn html2ps pn imagemagick-doc ii libwmf-bin 0.2.8.4-12 ii mplayer 2:1.3.0-8 pn povray pn radiance ii sane-utils 1.0.25-4.1 ii texlive-binaries [texlive-base-bin] 2018.20180416.47457-4 pn transfig ii ufraw-batch 0.22-3 ii xdg-utils1.1.3-1 -- no debconf information
Bug#886483: sssd gets confused by existing config file
Package: sssd Version: 1.16.0-3 Severity: minor Dear Maintainer, There is a regression in 1.16.0-2 and -3, rendering existing sssd configurations unable to authenticate users. This happens if the old config file has services = nss, pam in it. This used to be "the right way" of doing things but now with socket activated nss and pam services sssd gets confused and its pam service no longer works. Removing said line fixes it (hence "Severity: minor") but this is highly confusign to the admin as the service seems to be up and running. The clue is in the log: Jan 06 14:50:47 rigel sssd_check_socket_activated_responders[8175]: (Sat Jan 6 14:50:47:876645 2018) [sssd] [main] (0x0010): Misconfiguration found for the pam responder. Jan 06 14:50:47 rigel sssd_check_socket_activated_responders[8175]: The pam responder has been configured to be socket-activated but it's still mentioned in the services' line in /etc/sssd/sssd.conf. Jan 06 14:50:47 rigel sssd_check_socket_activated_responders[8175]: Please, consider either adjusting your services' line in /etc/sssd/sssd.conf or disabling the pam's socket by calling: Jan 06 14:50:47 rigel sssd_check_socket_activated_responders[8175]: "systemctl disable sssd-pam.socket" Jan 06 14:50:47 rigel systemd[1]: sssd-pam-priv.socket: Control process exited, code=exited status=17 Jan 06 14:50:47 rigel systemd[1]: sssd-pam-priv.socket: Failed with result 'exit-code'. Jan 06 14:50:47 rigel systemd[1]: Failed to listen on SSSD PAM Service responder private socket. Jan 06 14:50:47 rigel systemd[1]: Dependency failed for SSSD PAM Service responder socket. Jan 06 14:50:47 rigel systemd[1]: sssd-pam.socket: Job sssd-pam.socket/start failed with result 'dependency'. Jan 06 14:50:47 rigel systemd[1]: Listening on SSSD NSS Service responder socket. Note how the log says "please consider" instead of "this is an error, this will not work" and later shows a failure. >From the first "please consider" message I would presume sssd is supposed to >gracefully recover. The service seems to start when needed and responds to some queries but always ends auth process with [sssd[pam]] [pam_dp_process_reply] (0x0010): Reply error. And this means auth failure for pam of course. Cheers, Juha P.S. This may be "works as intended" but considering it took me quite a while to figure out why my existing, working configuration got broken and google came up with no help at all, I would think at least getting this report onto google results would be helpful to some people. Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.13.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages sssd depends on: ii python3-sss 1.16.0-3 ii sssd-ad 1.16.0-3 ii sssd-common 1.16.0-3 ii sssd-ipa 1.16.0-3 ii sssd-krb51.16.0-3 ii sssd-ldap1.16.0-3 ii sssd-proxy 1.16.0-3 sssd recommends no packages. sssd suggests no packages. -- no debconf information
Bug#799833: still exists
Still exists in 1.9.1-1+b1. This bug is almost two years old with no activity what so ever from the maintainer. It the package still being maintained?
Bug#801084: regression from jessie
Hi! I upgraded from jessie to stretch a few days ago and bluetooth stopped working. With some digging around, it seems I'm affected by this bug. The trouble is exacerbated by the fact that the firmware file from the github link does not work on my bt adapter. It loads fine, no error messages, no nothing. No working hci0 either. I actually get a hci0: hci0: Type: Primary Bus: USB BD Address: 34:23:87:FF:76:12 ACL MTU: 1021:8 SCO MTU: 64:1 DOWN RX bytes:3374 acl:0 sco:0 events:409 errors:0 TX bytes:36217 acl:0 sco:0 commands:408 errors:0 but it cannot be brought up: # hciconfig hci0 up Can't init device hci0: Invalid request code (56) # Cheers, Juha
Bug#845090: [Pkg-alsa-devel] Bug#845090: /usr/bin/alsamixer: alsamixer -c0 starts pulseaudio
> > So in short, it's either all or nothing? I.e. if I want *some* programs, > > which are linked against libpulse0, > Hmm, are there applications which need pulseaudio to work? I do have There are, but probably best not mentioned aloud lest Stallman smites us. :) > a system which works fine without pulse. You can use pulse to > provide sound in a network which can other sound servers like > jackausio as well... Bluetooth audio without pulse..? (Not my usecase, but I think that's not doable, is it? My use case is the one where I get the Vengeanceful Avengers of Free Software smite me.) Cheers, Juha signature.asc Description: This is a digitally signed message part.
Bug#845090: [Pkg-alsa-devel] Bug#845090: /usr/bin/alsamixer: alsamixer -c0 starts pulseaudio
> > > I think the only chance to run alsamixer without starting pulse is > > > to pulseaudio -k and autospawn pulse. > > Is this not a bug? > Starting pulseaudio automagic is a feature implemented in pulseaudio;-) So in short, it's either all or nothing? I.e. if I want *some* programs, which are linked against libpulse0, *not* to mess my mixer settings up because libpulse0 automagically starts pulseudio even when the program is explicitly asked to use something else, my only option is to never allow pulseaudio to start, even if for some programs I would actually prefer that? This brings back memories of security bugs in Windows programs in the 90s which were claimed to be features by MS… MS has learned since… Cheers, Juha
Bug#845090: [Pkg-alsa-devel] Bug#845090: /usr/bin/alsamixer: alsamixer -c0 starts pulseaudio
> I think the only chance to run alsamixer without starting pulse is > to pulseaudio -k and autospawn pulse. Is this not a bug? Cheers, Juha
Bug#845090: [Pkg-alsa-devel] Bug#845090: /usr/bin/alsamixer: alsamixer -c0 starts pulseaudio
> > I think pulseaudio gets started by libasound.so.2 when it parses > > alsa.conf.d because pulseaudio has placed the above file there. > If pulsaudion is installed it runs as a per user session by default. I think you might have misunderstood the problem. Disabling pulseaudio's autospawn does not fix the bug, it merely hides it in many circumstances. Furthermore, in my case, I actually want to keep autospawn – for those programs which actually wants to use pulseaudio. But at the same time, I want alsamixer -c0 (and a host of other programs) not to mute my mixer. Cheers, Juha signature.asc Description: This is a digitally signed message part.
Bug#846278: light-locker fails to unlock
Package: light-locker Version: 1.7.0-3 Severity: important Dear Maintainer, Light-locker cannot unlock a locked screen with lxqt. When lxqt invokes light-locker to lock the screen, the usual "you will be redirected" message and subsequent lightdm login screen appear. Typing in the password leads to a successful pam authentication: Nov 29 19:26:19 rigel lightdm: pam_sss(lightdm:auth): authentication success; logname= uid=0 euid=0 tty=:1 ruser= rhost= user=juhaj but that's the last bit which works as expected. Next, I get a black screen, which is soon replaced by text-mode black screen with a blinking text-mode cursor at the top left corner. The actual X session is never recovered. It can be recovered, though, by logging into a free virtual terminal and using loginctl unlock-session 2 where 2 happens to be the session number I have been given. Cheers, Juha -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.8.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages light-locker depends on: ii dconf-gsettings-backend [gsettings-backend] 0.26.0-2 ii libc62.24-5 ii libcairo21.14.6-1.1 ii libdbus-1-3 1.10.12-1 ii libdbus-glib-1-2 0.108-1 ii libglib2.0-0 2.50.2-1 ii libgtk-3-0 3.22.3-2 ii libpango-1.0-0 1.40.3-3 ii libpangocairo-1.0-0 1.40.3-3 ii libsystemd0 232-3 ii libx11-6 2:1.6.3-1 ii libxext6 2:1.3.3-1 ii libxss1 1:1.2.2-1 ii lightdm 1.18.2-3 light-locker recommends no packages. light-locker suggests no packages. -- no debconf information
Bug#845090: [Pkg-alsa-devel] Bug#845090: /usr/bin/alsamixer: alsamixer -c0 starts pulseaudio
> What do you want to tell me here? It seems your pulseaudio > installation is a bit buggy. I can't reproduce. Apart from the bit about /usr/bin/pulseaudio being a script which simply records that pulseaudio has been started and then execs /usr/bin/ pulseaudio.real, pulseaudio and alsamixer are pristine jessie. The asound.conf, which does not refer to pulseaudio at all, is modified; default.pa is also modified, but it should not even be read in this case. I'm sorry I forgot to remove that debugging script at /usr/bin/pulseaudio but the result is the same with that removed. > default.pa comes from pulseaudio or xrdp package. There is no > instruction to start pulse in any alsa package. You are quite correct. The culprit is /usr/share/alsa/alsa.conf.d/pulse.conf placed there by the package pulseaudio. If you install pulseaudio and that file then exists, can you then reproduce? (Please see my very last paragraph, too!) Is this now a bug in pulseaudio? And what severity? I'd say this breaks unrelated software! > It seems that pulse is fired up by mpd? I think pulseaudio gets started by libasound.so.2 when it parses alsa.conf.d because pulseaudio has placed the above file there. Interestingly enough, said file starts with a comment: # PulseAudio alsa plugin configuration file to set the pulseaudio plugin as # default output for applications using alsa when pulseaudio is running. I would agree that this is probably the most commonly desired behaviour *when* pulseaudio is running. However, I would not expect this to start a fresh pulseaudio daemon when one is *not* running yet! One further bit of information which I just realised might be relevant: there is a pulseaudio server running on the machine, but it belongs to another user. Could it be pulseaudio/alsa just naively think "pulseaudio running, let's use it" without considering whether they actually *can* use it or not? And when it cannot be used, a new daemon is fired up? Just guessing. Cheers, Juha signature.asc Description: This is a digitally signed message part.
Bug#845090: [Pkg-alsa-devel] Bug#845090: /usr/bin/alsamixer: alsamixer -c0 starts pulseaudio
> alsamixer doesn't fire up any puls daemon. Please check whether > puls is running before starting alsamixer. It should not, but it certainly does: juhaj@meissa 18:07:16 ~> ps -flyu juhaj|grep pulseau S juhaj 9740 9724 0 99 19 2204 3488 - 18:07 pts/400:00:00 grep pulseau Today is 20.11.2016, I am running on tty 4 and currently controlling 0 jobs juhaj@meissa 18:07:31 ~> alsamixer -c0 /usr/bin/pulseaudio: line 3: /var/log/mpd/mpd.runs.pulseaudio.at: Permission denied W: [pulseaudio.real] main.c: /proc/self/exe does not point to /usr/bin/ pulseaudio, cannot self execute. Are you playing games? Today is 20.11.2016, I am running on tty 4 and currently controlling 0 jobs juhaj@meissa 18:07:39 ~> ps -flyu juhaj|grep pulseau S juhaj 9746 1 7 69 -11 10840 166267 - 18:07 ?00:00:00 / usr/bin/pulseaudio.real --start --log-target=syslog S juhaj 9752 9746 0 80 0 5336 30992 - 18:07 ?00:00:00 / usr/lib/pulseaudio/pulse/gconf-helper S juhaj 9756 9724 0 99 19 2160 3488 - 18:07 pts/400:00:00 grep pulseau Today is 20.11.2016, I am running on tty 4 and currently controlling 0 jobs juhaj@meissa 18:07:40 ~> I do not think this behaviour is correct. The user juhaj is pristine, and default.pa comes from the deb, except I've added load-module module-alsa-sink device=dmix:CARD=AudioPCI,DEV=1 just before .ifexists module-udev-detect.so load-module module-udev-detect .else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect .endif > BTW: do you have more then one soundcard installed? If not just run > alsamixer without any option. Your guess is correct. A total of three soundcards, although only two are relevant here: the third one is a webcam which only has a microphone, no speakers. Now that you mention it, while alsamixer -c1 and alsamixer -c2 also start pulseaudio, only alsamixer -c0 causes any volumes to change. Which makes me wonder perhaps load-module module-alsa-sink device=dmix:CARD=AudioPCI,DEV=1 has something to do with the changing of the mute setting. Having said that, I don't really mind if pulseaudio gets started as long as it does not screw up the mixer settings in the process: I can always configure other software to use alsa explicitly if I need to. So I still think the problem is that pulseaudio gets started in the first place. Cheers, Juha signature.asc Description: This is a digitally signed message part.
Bug#845090: /usr/bin/alsamixer: alsamixer -c0 starts pulseaudio
Package: alsa-utils Version: 1.0.28-1 Severity: normal File: /usr/bin/alsamixer Dear Maintainer, Running "alsamixer -c0" in order to adjust the ALSA mixer levels causes pulseaudio daemon to start. This is not just wrong and unexpected, but also causes unwanted side-effects in other programs, like mixer levels changing and other programs suddenly defaulting to using pa. Cheers, Juha -- System Information: Debian Release: 8.5 APT prefers stable APT policy: (995, 'stable'), (500, 'stable-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/bash Init: sysvinit (via /sbin/init) Versions of packages alsa-utils depends on: ii dialog 1.2-20140911-1 ii kmod18-3 ii libasound2 1.0.28-1 ii libc6 2.19-18+deb8u6 ii libncursesw55.9+20140913-1+b1 ii libsamplerate0 0.1.8-8 ii libtinfo5 5.9+20140913-1+b1 ii lsb-base4.1+Debian13+nmu1 ii whiptail0.52.17-1+b1 alsa-utils recommends no packages. alsa-utils suggests no packages. -- Configuration Files: /etc/init.d/alsa-utils changed [not included] -- no debconf information
Bug#845091: mpd starts pulseaudio even when configured not to use it
Package: mpd Version: 0.19.12-1~bpo8+1 Severity: normal Dear Maintainer, When mpd runs, it also runs pulseaudio. This is not just unnecessary, but also causes weird unwanted side-effects like muting of Master volume channel in alsa (which mpd is also not configured to use). Cheers, Juha -- System Information: Debian Release: 8.5 APT prefers stable APT policy: (995, 'stable'), (500, 'stable-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/bash Init: sysvinit (via /sbin/init) Versions of packages mpd depends on: ii adduser 3.113+nmu3 ii init-system-helpers 1.22 ii libadplug-2.2.1-0 2.2.1+dfsg3-0.1 ii libao41.1.0-3 ii libasound21.0.28-1 ii libaudiofile1 0.3.6-2+b1 ii libavahi-client3 0.6.31-5 ii libavahi-common3 0.6.31-5 ii libavcodec56 6:11.8-1~deb8u1 ii libavformat56 6:11.8-1~deb8u1 ii libavutil54 6:11.8-1~deb8u1 ii libbz2-1.01.0.6-7+b3 ii libc6 2.19-18+deb8u6 ii libcdio-cdda1 0.83-4.2 ii libcdio-paranoia1 0.83-4.2 ii libcdio13 0.83-4.2 ii libcurl3-gnutls 7.38.0-4+deb8u5 ii libdbus-1-3 1.8.20-0+deb8u1 ii libexpat1 2.1.0-6+deb8u3 ii libfaad2 2.7-8 ii libflac8 1.3.0-3 ii libfluidsynth11.1.6-2 ii libglib2.0-0 2.48.0-1~bpo8+1 ii libgme0 0.5.5-2 ii libicu52 52.1-8+deb8u3 ii libid3tag00.15.1b-11 ii libiso9660-8 0.83-4.2 ii libjack-jackd2-0 [libjack-0.116] 1.9.10+20140719git3eb0ae6a~dfsg-2 ii libmad0 0.15.1b-8 ii libmikmod33.3.7-1 ii libmms0 0.6.2-4 ii libmodplug1 1:0.8.8.4-4.1+b1 ii libmp3lame0 3.99.5+repack1-7+deb8u1 ii libmpcdec62:0.1~r459-4.1 ii libmpdclient2 2.9-1 ii libmpg123-0 1.20.1-2 ii libnfs4 1.9.5-2 ii libogg0 1.3.2-1 ii libopenal11:1.15.1-5 ii libopus0 1.1-2 ii libpulse0 7.1-2~bpo8+1 ii libresid-builder0c2a 2.1.1-14 ii libroar2 1.0~beta11-1 ii libsamplerate00.1.8-8 ii libshout3 2.3.1-3 ii libsidplay2 2.1.1-14 ii libsidutils0 2.1.1-14 ii libsmbclient 2:4.2.10+dfsg-0+deb8u3 ii libsndfile1 1.0.25-9.1+deb8u1 ii libsoxr0 0.1.1-1 ii libsqlite3-0 3.8.7.1-1+deb8u1 ii libstdc++64.9.2-10 ii libsystemd0 215-17+deb8u3 ii libupnp6 1:1.6.19+git20141001-1 ii libvorbis0a 1.3.4-2 ii libvorbisenc2 1.3.4-2 ii libvorbisfile31.3.4-2 ii libwavpack1 4.70.0-1 ii libwildmidi1 0.3.7-1 ii libwrap0 7.6.q-25 ii libyajl2 2.1.0-2 ii libzzip-0-13 0.13.62-3 ii lsb-base 4.1+Debian13+nmu1 ii zlib1g1:1.2.8.dfsg-2+b1 mpd recommends no packages. Versions of packages mpd suggests: ii avahi-daemon 0.6.31-5 ii gmpc [mpd-client]11.8.16-9 pn icecast2 ii mpc [mpd-client] 0.26-1 ii mpdris [mpd-client] 0.1.2-2 ii mpdris2 [mpd-client] 0.5-1 ii ncmpcpp [mpd-client] 0.5.10-2 ii pulseaudio 7.1-2~bpo8+1 ii qmpdclient [mpd-client] 1.2.2-2 -- Configuration Files: /etc/init.d/mpd changed [not included] /etc/mpd.conf changed [not included] -- no debconf information
Bug#798509: owncloud-client: 100% CPU load all the time
Dear Maintainers, Still present in 2.2.4+dfsg-1. This bug is rather severe and it has been present in the unstable for well over a year now with just a short question from you in all this time. I am sure your users would appreciate a status update and explanation of what is going on. At the very least, those of us also planning to upgrade to stretch in the not- so-distant future would be rather happy to see this resolved before freeze. Cheers, Juha
Bug#838826: [Pkg-utopia-maintainers] Bug#838826: network-manager kills network on upgrade
I'm sorry, but I do not have the time to try this again: I have a working network configuration with wicd now and going back to the version(s) I upgraded from when I experienced the problem is rather difficult because despite its excellence otherwise, Debian does not really handle package downgrades well (I'd have to basically downgrade sid to a dated version in archive). Please close. Cheers, Juha On Friday, 30 September 2016 16:59:20 BST Michael Biebl wrote: > Control: severity -1 important > > Am 28.09.2016 um 02:48 schrieb Michael Biebl: > > Any news? Can you provide the requested information? > > Since I haven't received further information and can't reproduce the > issue myself, I'm going to downgrade the severity. Unless I hear back > from you, I'll close the bug report in 10 days. > > Michael -- ------- | Juha Jäykkä, ju...@iki.fi | | http://koti.kapsi.fi/~juhaj/ | ---
Bug#838826: network-manager kills network on upgrade
Package: network-manager Version: 1.4.0-4 Severity: serious Justification: makes the system unusable Dear Maintainer, Upon upgrade to 1.4.0-4, network-manager disconnects network connections and does not reconnect (as far as I can tell, it does not even try). This is unacceptable as it makes remote management of systems impossible. Serious because a remote system become completely unusable after this until someone visits it physically (if one does not have suitable IPMI or something similar in place). This is also a regression from several years ago, when every upgrade and restart on network-manager disconnected the network before reconnecting them again. At least back then it managed to reconnect, so one only needed to run upgrades in a screen (sensible precaution for remote upgrades anyway). Now it does not reconnect, ever, so screen does not help. Cheers, Juha -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.7.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages network-manager depends on: ii adduser3.115 ii dbus 1.10.10-1 ii init-system-helpers1.45 ii libaudit1 1:2.6.6-1 ii libbluetooth3 5.36-1+b2 ii libc6 2.24-3 ii libglib2.0-0 2.50.0-1 ii libgnutls303.5.4-2 ii libgudev-1.0-0 230-3 ii libmm-glib01.6.2-1 pn libndp0 ii libnewt0.520.52.18-3 ii libnl-3-2003.2.27-1 pn libnm0 ii libpam-systemd 231-7 ii libpolkit-agent-1-00.105-16 ii libpolkit-gobject-1-0 0.105-16 ii libreadline6 6.3-8+b4 ii libselinux12.5-3 ii libsoup2.4-1 2.56.0-1 ii libsystemd0231-7 pn libteamdctl0 ii libuuid1 2.28.2-1 ii lsb-base 9.20160629 ii policykit-10.105-16 ii udev 231-7 ii wpasupplicant 2.5-2+v2.4-3 Versions of packages network-manager recommends: ii crda 3.13-1+b1 pn dnsmasq-base ii iptables 1.6.0-3 pn iputils-arping ii isc-dhcp-client 4.3.5~b1-1 ii modemmanager 1.6.2-1 ii ppp 2.4.7-1+3 Versions of packages network-manager suggests: pn libteam-utils -- no debconf information
Bug#798509: owncloud-client: 100% CPU load all the time
Package: owncloud-client Version: 2.2.2+dfsg-1 Followup-For: Bug #798509 Dear Maintainer, Just to confirm this but "still" appears in 2.2.2+dfsg-1. In fact, it only just appeared after latest upgrade, but as I am a bit lazy in upgradin my sid systems, I have no idea what the previous version was. It was certainly newer than the original reporter's version. I tried running owncloud under strace but then it suddenly behaves normally, so could not even find out WHAT it is doing consuming all my cpu. Cheers, Juha -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.7.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages owncloud-client depends on: ii libc6 2.24-1 ii libgcc1 1:6.2.0-2 ii libowncloudsync0 2.2.2+dfsg-1 ii libqt5core5a 5.6.1+dfsg-3+b1 ii libqt5dbus5 5.6.1+dfsg-3+b1 ii libqt5gui55.6.1+dfsg-3+b1 ii libqt5keychain0 0.5.0-1 ii libqt5network55.6.1+dfsg-3+b1 ii libqt5sql5-sqlite 5.6.1+dfsg-3+b1 ii libqt5webkit5 5.6.1+dfsg-5 ii libqt5widgets55.6.1+dfsg-3+b1 ii libqt5xml55.6.1+dfsg-3+b1 ii libssl1.0.2 1.0.2h-1 ii libstdc++66.2.0-2 ii owncloud-client-l10n 2.2.2+dfsg-1 owncloud-client recommends no packages. owncloud-client suggests no packages. -- no debconf information
Bug#831983: kde-telepathy-contact-list: ktp-contactlist no longer able to log in to gtalk, sip
Dear Martin, I was warned against upgrading to the 16.xx in experimental earlier. That warning related to other parts of KDE, though, so if telepathy (or your command below) does not pull in other parts of KDE from experimental, I'll try it out, BUT not for two weeks: the disc on the machine in question just broke and is now on it's way to Samsung and they say "two weeks"! Cheers, Juha On Thursday 21 Jul 2016 10:18:31 Martin Steigerwald wrote: > Dear Juha, > > Am Mittwoch, 20. Juli 2016, 23:40:41 CEST schrieb Juha Jäykkä: > > Package: kde-telepathy-contact-list > > Version: 15.08.3-1 > > Severity: important > > > > Dear Maintainer, > > > > After upgrading to 15.08.3-1, ktp-contactlist (or the plasma applets) no > > longer can log into gtalk or sip. These are possibly separate bugs as sip > > auth handler segfaults whereas gtalk simply does not become "available". > > It > > gives no error messages, warnings or any other indication that it is even > > trying to do anything. > > In case you feel adventurous I suggest you try out whether upgrading kde- > telepathy to the version in experimental fixes your issue. I see you have > experimental added to your sources list anyway. > > > -- System Information: > > Debian Release: stretch/sid > > > > APT prefers unstable > > APT policy: (500, 'unstable'), (1, 'experimental') > > > > Architecture: amd64 (x86_64) > > Foreign Architectures: i386 > > […] > > I used the following command to do just that on my sid system: > > apt -t experimental install kde-telepathy kde-telepathy-approver kde- > telepathy-auth-handler kde-telepathy-contact-list kde-telepathy-data kde- > telepathy-desktop-applets kde-telepathy-filetransfer-handler kde-telepathy- > integration-module kde-telepathy-kaccounts kde-telepathy-kpeople kde- > telepathy-minimal kde-telepathy-send-file kde-telepathy-text-ui qml-module- > org-kde-telepathy > > If you try this and it fixes the issue for you, please let us now. > > Thank you,
Bug#831983: kde-telepathy-contact-list: ktp-contactlist no longer able to log in to gtalk, sip
Package: kde-telepathy-contact-list Version: 15.08.3-1 Severity: important Dear Maintainer, After upgrading to 15.08.3-1, ktp-contactlist (or the plasma applets) no longer can log into gtalk or sip. These are possibly separate bugs as sip auth handler segfaults whereas gtalk simply does not become "available". It gives no error messages, warnings or any other indication that it is even trying to do anything. Cheers, Juha -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.6.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages kde-telepathy-contact-list depends on: ii kde-telepathy-data 15.08.3-1 ii kde-telepathy-kpeople 15.08.3-1+b1 ii libc6 2.23-1 ii libgcc1 1:6.1.1-9 ii libkf5completion5 5.23.0-1 ii libkf5configcore5 5.23.0-1 ii libkf5configgui55.23.0-1 ii libkf5configwidgets55.23.0-1 ii libkf5coreaddons5 5.23.0-1 ii libkf5dbusaddons5 5.23.0-1 ii libkf5i18n5 5.23.0-1 ii libkf5iconthemes5 5.23.0-1 ii libkf5notifications55.23.0-1 ii libkf5people5 5.23.0-1 ii libkf5peoplewidgets55.23.0-1 ii libkf5service-bin 5.23.0-1 ii libkf5service5 5.23.0-1 ii libkf5widgetsaddons55.23.0-1 ii libkf5windowsystem5 5.23.0-1 ii libkf5xmlgui5 5.23.0-1 ii libktpcommoninternals9 15.08.3-1+b1 ii libktplogger9 15.08.3-1+b1 ii libktpmodels9 15.08.3-1+b1 ii libktpwidgets9 15.08.3-1+b1 ii libqt5core5a5.6.1+dfsg-3 ii libqt5dbus5 5.6.1+dfsg-3 ii libqt5gui5 5.6.1+dfsg-3 ii libqt5widgets5 5.6.1+dfsg-3 ii libstdc++6 6.1.1-9 ii libtelepathy-qt5-0 0.9.6.1-6 Versions of packages kde-telepathy-contact-list recommends: ii kde-telepathy 15.08.3 kde-telepathy-contact-list suggests no packages. -- no debconf information
Bug#799157: gwenview: some menu and print options vanished
Package: gwenview Version: 4:15.08.3-1 Followup-For: Bug #799157 Just to confirm, this still exists on 4:15.08.3-1. Non-KDE printing works fine. Furthermore, it looks like simultaneously with vanishing printing options, the landscape option stopped working, too: it works on jessie's version using the same printer queue. The newer gwenview simply prints the long edge of the parallel to the short edge of the paper, centers it on the paper (both edges) and scales to maximum size (i.e. short edge size). I did ask gwenview to "fit to page". Cheers, Juha -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.2.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gwenview depends on: ii libc6 2.21-4 ii libexiv2-14 0.25-2.1 ii libgcc1 1:5.3.1-4 ii libjpeg62-turbo 1:1.4.1-2 ii libkf5activities5 5.16.0-1 ii libkf5baloo55.16.0-1 ii libkf5completion5 5.16.0-1 ii libkf5configcore5 5.16.0-1 ii libkf5configgui55.16.0-1 ii libkf5configwidgets55.16.0-1 ii libkf5coreaddons5 5.16.0-1 ii libkf5filemetadata3 5.16.0-1 ii libkf5i18n5 5.16.0-1 ii libkf5iconthemes5 5.16.0-1 ii libkf5itemmodels5 5.16.0-1 ii libkf5itemviews55.16.0-1 ii libkf5jobwidgets5 5.16.0-1 ii libkf5kdelibs4support5 5.16.0-1 ii libkf5kiocore5 5.16.0-1 ii libkf5kiofilewidgets5 5.16.0-1 ii libkf5kiowidgets5 5.16.0-1 ii libkf5notifications55.16.0-1 ii libkf5parts55.16.0-1 ii libkf5service-bin 5.16.0-1 ii libkf5service5 5.16.0-1 ii libkf5textwidgets5 5.16.0-1 ii libkf5widgetsaddons55.16.0-1 ii libkf5xmlgui5 5.16.0-1 ii liblcms2-2 2.6-3+b3 ii libphonon4qt5-4 4:4.8.3-2 ii libpng12-0 1.2.54-1 ii libqt5core5a5.5.1+dfsg-8 ii libqt5gui5 5.5.1+dfsg-8 ii libqt5opengl5 5.5.1+dfsg-8 ii libqt5printsupport5 5.5.1+dfsg-8 ii libqt5svg5 5.5.1-2 ii libqt5widgets5 5.5.1+dfsg-8 ii libqt5x11extras55.5.1-3 ii libstdc++6 5.3.1-4 ii libx11-62:1.6.3-1 ii phonon4qt5 4:4.8.3-2 Versions of packages gwenview recommends: ii kamera 4:4.14.2-1+b1 ii kio-extras 4:15.08.3-1 ii qt5-image-formats-plugins 5.5.1-2 gwenview suggests no packages. -- no debconf information
Bug#809696: Regression: GSSAPIKeyExchange yes stops working after 6.9p1-3
Package: openssh-client Version: 1:6.9p1-3 Severity: important Dear Maintainers, The version 6.9p1-3 is the last one where GSSAPIKeyExchange can succeed, that is the version at http://snapshot.debian.org/archive/debian/20151202T154902Z/pool/main/o/openssh/openssh-client_6.9p1-3_amd64.deb All newer versions fail. What I expect to see is (ssh -vv foo@bar): ... debug1: Offering GSSAPI proposal: gss-gex-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-group1-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-group14-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-gex-sha1-A/vxljAEU54gt9a48EiANQ==,gss-group1-sha1-A/vxljAEU54gt9a48EiANQ==,gss-group14-sha1-A/vxljAEU54gt9a48EiANQ==,gss-gex-sha1-bontcUwnM6aGfWCP21alxQ==,gss-group1-sha1-bontcUwnM6aGfWCP21alxQ==,gss-group14-sha1-bontcUwnM6aGfWCP21alxQ==,gss-gex-sha1-eipGX3TCiQSrx573bT1o1Q==,gss-group1-sha1-eipGX3TCiQSrx573bT1o1Q==,gss-group14-sha1-eipGX3TCiQSrx573bT1o1Q== debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug2: kex_parse_kexinit: gss-gex-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-group1-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-group14-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-gex-sha1-A/vxljAEU54gt9a48EiANQ==,gss-group1-sha1-A/vxljAEU54gt9a48EiANQ==,gss-group14-sha1-A/vxljAEU54gt9a48EiANQ==,gss-gex-sha1-bontcUwnM6aGfWCP21alxQ==,gss-group1-sha1-bontcUwnM6aGfWCP21alxQ==,gss-group14-sha1-bontcUwnM6aGfWCP21alxQ==,gss-gex-sha1-eipGX3TCiQSrx573bT1o1Q==,gss-group1-sha1-eipGX3TCiQSrx573bT1o1Q==,gss-group14-sha1-eipGX3TCiQSrx573bT1o1Q==,curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ecdsa-sha2-nistp256-cert-...@openssh.com,ecdsa-sha2-nistp384-cert-...@openssh.com,ecdsa-sha2-nistp521-cert-...@openssh.com,ssh-ed25519-cert-...@openssh.com,ssh-rsa-cert-...@openssh.com,ssh-dss-cert-...@openssh.com,ssh-rsa-cert-...@openssh.com,ssh-dss-cert-...@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519,ssh-rsa,ssh-dss,null debug2: kex_parse_kexinit: chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-...@lysator.liu.se debug2: kex_parse_kexinit: chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-...@lysator.liu.se debug2: kex_parse_kexinit: umac-64-...@openssh.com,umac-128-...@openssh.com,hmac-sha2-256-...@openssh.com,hmac-sha2-512-...@openssh.com,hmac-sha1-...@openssh.com,umac...@openssh.com,umac-...@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1,hmac-md5-...@openssh.com,hmac-ripemd160-...@openssh.com,hmac-sha1-96-...@openssh.com,hmac-md5-96-...@openssh.com,hmac-md5,hmac-ripemd160,hmac-ripemd...@openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: umac-64-...@openssh.com,umac-128-...@openssh.com,hmac-sha2-256-...@openssh.com,hmac-sha2-512-...@openssh.com,hmac-sha1-...@openssh.com,umac...@openssh.com,umac-...@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1,hmac-md5-...@openssh.com,hmac-ripemd160-...@openssh.com,hmac-sha1-96-...@openssh.com,hmac-md5-96-...@openssh.com,hmac-md5,hmac-ripemd160,hmac-ripemd...@openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: none,z...@openssh.com,zlib debug2: kex_parse_kexinit: none,z...@openssh.com,zlib debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: kex_parse_kexinit: gss-gex-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-group1-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-group14-sha1-toWM5Slw5Ew8Mqkay+al2g==,curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1 debug2: kex_parse_kexinit: ecdsa-sha2-nistp521,ssh-rsa debug2: kex_parse_kexinit: chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com debug2: kex_parse_kexinit: chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com debug2: kex_parse_kexinit: umac-64-...@openssh.com,umac-128-...@openssh.com,hmac-sha2-256-...@openssh.com,hmac-sha2-512-...@openssh.com,hmac-sha1-...@openssh.com,umac...@openssh.com,umac-...@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1 debug2: kex_parse_kexinit: umac-64-...@openssh.com,umac-128-...@openssh.com,hmac-sha2-256-...@openssh.com,hmac-sha2-512-...@openssh.com,hmac-sha1-...@openssh.com,umac...@openssh.com,umac-...@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1 debug2: kex_parse_kexinit: none,z...@openssh.com debug2: kex_parse_kexinit: none,z...@openssh.com debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2:
Bug#809695: openssh-server: Setting PermitRootLogin without-password disables GSSAPI Auth
Package: openssh-server Version: 1:7.1p1-5 Severity: important Dear Maintainer, Using ssh/SSAPI auth should work even if root login with password are disabled, however, it looks like the new 7.0 setting of "without-password" and prohibit-password inadvertently prevent GSSAPI auth to root, too. Please see http://lists.mindrot.org/pipermail/openssh-bugs/2015-September/015366.html for more details. Cheers, Juha -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.2.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages openssh-server depends on: ii adduser3.113+nmu3 ii debconf [debconf-2.0] 1.5.58 ii dpkg 1.18.3 ii init-system-helpers1.24 ii libaudit1 1:2.4.4-4 ii libc6 2.21-4 ii libcomerr2 1.42.13-1 ii libgssapi-krb5-2 1.13.2+dfsg-4 ii libkrb5-3 1.13.2+dfsg-4 ii libpam-modules 1.1.8-3.1 ii libpam-runtime 1.1.8-3.1 ii libpam0g 1.1.8-3.1 ii libselinux12.4-3 ii libssl1.0.21.0.2e-1 ii libsystemd0228-2 ii libwrap0 7.6.q-25 ii lsb-base 9.20150917 ii openssh-client 1:7.1p1-5 ii openssh-sftp-server1:7.1p1-5 ii procps 2:3.3.10-4+b1 ii zlib1g 1:1.2.8.dfsg-2+b1 Versions of packages openssh-server recommends: ii ncurses-term 6.0+20151024-2 ii xauth 1:1.0.9-1 Versions of packages openssh-server suggests: ii ksshaskpass [ssh-askpass] 4:5.4.3-1 ii kwalletcli [ssh-askpass] 2.12-5 pn molly-guard pn monkeysphere pn rssh pn ufw -- debconf information excluded
Bug#801988: openmpi-bin: incorrect dependency
Package: openmpi-bin Version: 1.6.5-9.1 Severity: normal Dear Maintainer, When upgrading from Jessie to > Jessie, there is a potential for problems with openmpi-bin due to an incorrect dependency on libhwloc5. If one installs libhwloc5 >= 1.11.0 from > Jessie onto a system with openmpi-bin from Jessie, mpirun will segfault in MPI_Init. Hence the dependency libhwloc5 (>= 1.10.0) should also have a conflict libhwloc5 (>= 1.11.0) Yes, I am aware of the fact that this is an unusual situation: it needs one to make a partial upgrade as otherwise openmpi-bin gets updated, too, but many people to cherry-pick newer versions from testing to their stables. In my case, I wanted libdolfin1.5 (not hwloc), which pulled a newer hwloc, but since the Conflicts: was not there, I was left with a sigsegving mpirun. Just for curiosity, the backtrace and symptoms are IDENTICAL to #790540 but the fix (or does it actually happen to be just pure luck?) there does not help here. Cheers, Juha -- System Information: Debian Release: 8.2 APT prefers stable APT policy: (1100, 'stable'), (1000, 'stable-updates'), (900, 'stable'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages openmpi-bin depends on: ii libc6 2.19-18+deb8u1 ii libhwloc5 1.10.0-3 ii libltdl72.4.2-1.11 ii libopenmpi1.6 1.6.5-9.1 ii openmpi-common 1.6.5-9.1 openmpi-bin recommends no packages. Versions of packages openmpi-bin suggests: ii gfortran4:4.9.2-2 pn openmpi-checkpoint -- no debconf information
Bug#801301: lxqt-common: missing lxqt-session or dependency providing it
Package: lxqt-common Version: 0.9.1+20150922-1 Severity: grave Justification: renders package unusable Dear Maintainer, Trying to start lxqt fails: ~> /usr/bin/startlxqt /usr/bin/startlxqt: 68: exec: lxqt-session: not found ~> This makes lxqt useless. Furthermore apt-file reveals no candidate packages containing said file so there is no workaround. Cheers, Juha -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) lxqt-common depends on no packages. Versions of packages lxqt-common recommends: ii oxygen-icon-theme 4:4.14.0-1 lxqt-common suggests no packages. -- no debconf information
Bug#799309: plasma-workspace: impossible to unlock screen-locker without a mouse
Package: plasma-workspace Version: 4:5.4.1-1 Severity: important Dear Maintainer, Since upgrading to plasma-workspace 4:5.4.1-1 I am no longer able to reliably unlock the KDE/plasma screen locker without plugging in a mouse or other similar pointing device. There does not seem to be any way to focus the password entry textedit box without a pointing device. Oddly enough, about 50% of the time, the box is focused automatically, allowing mouseless unlocking. Cheers, Juha -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages plasma-workspace depends on: ii dbus-x111.8.18-1 ii frameworkintegration5.13.0-1 ii gdb 7.7.1+dfsg-5 ii kactivities 5.13.0-1 ii kde-cli-tools 4:5.4.0-1 ii kded5 5.13.0-1 ii kinit 5.13.0-1 ii kio 5.13.0-1 ii libc6 2.19-18 ii libcln6 1.3.4-1 ii libdbusmenu-qt5-2 0.9.3+15.10.20150604-1 ii libgcc1 1:5.2.1-16 ii libgps213.11-3 ii libice6 2:1.0.9-1+b1 ii libkf5activities5 5.13.0-1 ii libkf5auth5 5.13.0-1 ii libkf5baloo55.13.0-2 ii libkf5bookmarks55.13.0-1 ii libkf5completion5 5.13.0-1 ii libkf5configcore5 5.13.0-1 ii libkf5configgui55.13.0-1 ii libkf5configwidgets55.13.0-2 ii libkf5coreaddons5 5.13.0-1 ii libkf5crash55.13.0-1 ii libkf5dbusaddons5 5.13.0-1 ii libkf5declarative5 5.13.0-1 ii libkf5globalaccel-bin 5.13.0-2 ii libkf5globalaccel5 5.13.0-2 ii libkf5guiaddons55.13.0-1 ii libkf5i18n5 5.13.0-1 ii libkf5iconthemes5 5.13.0-1 ii libkf5idletime5 5.13.0-1 ii libkf5itemviews55.13.0-1 ii libkf5jobwidgets5 5.13.0-1 ii libkf5js5 5.13.0-2 ii libkf5jsembed5 5.13.0-3 ii libkf5kdelibs4support5 5.13.0-3 ii libkf5kiocore5 5.13.0-1 ii libkf5kiofilewidgets5 5.13.0-1 ii libkf5kiowidgets5 5.13.0-1 ii libkf5networkmanagerqt6 5.13.0-1 ii libkf5newstuff5 5.13.0-1 ii libkf5notifications55.13.0-1 ii libkf5notifyconfig5 5.13.0-1 ii libkf5package5 5.13.0-2 ii libkf5plasma5 5.13.0-1 ii libkf5plasmaquick5 5.13.0-1 ii libkf5quickaddons5 5.13.0-1 ii libkf5runner5 5.13.0-1 ii libkf5screen6 4:5.4.0-1 ii libkf5service-bin 5.13.0-2 ii libkf5service5 5.13.0-2 ii libkf5solid55.13.0-1 ii libkf5su5 5.13.0-1 ii libkf5texteditor5 5.13.0-1 ii libkf5textwidgets5 5.13.0-1 ii libkf5wallet5 5.13.0-1 ii libkf5waylandclient54:5.4.0-1 ii libkf5waylandserver54:5.4.1-1 ii libkf5webkit5 5.13.0-1 ii libkf5widgetsaddons55.13.0-1 ii libkf5windowsystem5 5.13.0-3 ii libkf5xmlgui5 5.13.0-1 ii libkf5xmlrpcclient5 5.13.0-1 ii libksgrd7 4:5.4.0-1 ii libkworkspace5-54:5.4.1-1 ii libpam0g1.1.8-3.1 ii libphonon4qt5-4 4:4.8.3-2 ii libplasma-geolocation-interface54:5.4.1-1 ii libprocesscore7 4:5.4.0-1 ii libprocessui7 4:5.4.0-1 ii libqalculate5v5 0.9.7-9.1 ii libqt5core5a5.4.2+dfsg-9 ii libqt5dbus5 5.4.2+dfsg-9 ii libqt5gui5 5.4.2+dfsg-9 ii libqt5network5 5.4.2+dfsg-9 ii libqt5qml5 5.4.2-6 ii libqt5quick55.4.2-6 ii libqt5script5 5.4.2+dfsg-4 ii libqt5sql5 5.4.2+dfsg-9 ii libqt5webkit5 5.4.2+dfsg-3 ii libqt5widgets5 5.4.2+dfsg-9 ii
Bug#787814: get-iplayer: unable to download anything
Package: get-iplayer Version: 2.92-1 Severity: grave Justification: renders package unusable Dear Maintainer, When trying to download any program from iPlayer, since something like a week ago, all I get is ~ get-iplayer --pid=b05wdbyk get_iplayer v2.92, Copyright (C) 2008-2010 Phil Lewis This program comes with ABSOLUTELY NO WARRANTY; for details use --warranty. This is free software, and you are welcome to redistribute it under certain conditions; use --conditions for details. INFO: Episode-only pid detected INFO: Trying pid: b05wdbyk using type: tv INFO: Trying to stream pid using type tv INFO: pid not found in tv cache Matches: INFO: 1 Matching Programmes Not a SCALAR reference at /usr/bin/get-iplayer line 7099. Changing to --pid-recursive and giving the series pid makes no difference. Neither does trying some other series or trying with a direct URL. I think this warrants grave and possibly a duplicate of #787755 as I simultaneously lost the ability to search for programs too. Cheers, Juha -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages get-iplayer depends on: ii libwww-perl 6.08-1 ii libxml-simple-perl 2.20-1 ii perl5.20.2-4 ii rtmpdump2.4+20150115.gita107cef-1 Versions of packages get-iplayer recommends: pn atomicparsley none ii id3v2 0.1.12-2.1 pn libmp3-info-perl none Versions of packages get-iplayer suggests: ii ffmpeg 7:2.6.2-1 ii mplayer2 [mplayer] 2.0-728-g2c378c7-4+b1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770773: vdr: Incorrect use of getent in postinst script makes the package uninstallable
Package: vdr Version: 2.0.3-2+b1 Severity: serious Tags: patch Justification: The package is uninstallable: this is not a violation of DPM, but should not be in the archive at all instead. Dear Maintainer, Your package is uninstallable on a system where the user vdr and group vdr exist and the passwd and group databases do not support enumeration or systems where there are more than one such database and the vdr user and group are not defined in the primary one. Note that the first condition is fulfilled by any system where vdr is already installed, thus making it impossible to upgrade vdr (short of editing the postinst script). As the man page of getent mentions, the command getent passwd is not guaranteed to enumerate all users (likewise for getent group), yet this is exactly what the postinst script tries to do to determine if the user/group vdr exists. A very short patch is attached which correctly enumerates said user and group and takes the appropriate action in both cases. Best regards, Juha -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (995, 'testing'), (990, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages vdr depends on: ii adduser3.113+nmu3 ii debconf [debconf-2.0] 1.5.53 ii libc6 2.19-13 ii libcap21:2.24-6 ii libfontconfig1 2.11.0-6.1 ii libfreetype6 2.5.2-2 ii libgcc11:4.9.1-19 ii libjpeg62-turbo1:1.3.1-10 ii libstdc++6 4.9.1-19 ii psmisc 22.21-2 Versions of packages vdr recommends: ii fonts-freefont-ttf [ttf-freefont] 20120503-4 ii lirc 0.9.0~pre1-1.1 ii ttf-bitstream-vera 1.10-8 ii ttf-freefont 20120503-4 Versions of packages vdr suggests: pn vdr-plugin-dvbsddevice none -- Configuration Files: /etc/default/vdr changed [not included] /etc/vdr/command-hooks/commands.custom.conf changed [not included] /etc/vdr/command-hooks/order.commands.conf 6f3fafcaa16c454645c64a98bd064491 [Errno 2] No such file or directory: u'/etc/vdr/command-hooks/order.commands.conf 6f3fafcaa16c454645c64a98bd064491' /etc/vdr/command-hooks/order.reccmds.conf 87e4187bd6121964ce054223570caac4 [Errno 2] No such file or directory: u'/etc/vdr/command-hooks/order.reccmds.conf 87e4187bd6121964ce054223570caac4' /etc/vdr/groups.d/vdr.groups 01aa59f17312aeb7958106059937565f [Errno 2] No such file or directory: u'/etc/vdr/groups.d/vdr.groups 01aa59f17312aeb7958106059937565f' /etc/vdr/keymacros.conf changed [not included] /etc/vdr/svdrphosts.conf changed [not included] -- debconf information excluded --- /var/lib/dpkg/info/vdr.postinst.broken 2014-11-23 21:45:22.493063539 + +++ /var/lib/dpkg/info/vdr.postinst.working 2014-11-23 21:46:54.222673434 + @@ -75,12 +75,12 @@ # ensure that user and group 'vdr' exist USER=vdr GROUP=vdr -if ! getent group | grep -q ^$GROUP: ; then +if ! getent group $GROUP| grep -q ^$GROUP: ; then echo -n Adding group $GROUP.. addgroup --quiet --system $GROUP echo ..done fi -if ! getent passwd | grep -q ^$USER:; then +if ! getent passwd $USER| grep -q ^$USER:; then echo -n Adding user $USER.. adduser --system --home /var/lib/vdr --shell /bin/false \ --gecos VDR user --no-create-home \
Bug#729180: emacs24: checking for changed files and reverting buffers mayhem
Package: emacs24 Version: 24.3+1-1.1 Severity: important I am not sure if this is one or several bugs, but all these features are either new or newly turned on by default and they all seem to be related to a single feature, so I believe there is just one bug somewhere. Steps to reproduce: start emacs, visit a file, switch to another program and change the file you just visited (touch will do, but it really has to be a different program, running M-x shell or similar won't do). Nothing happens, just as supposed. Now switch back to emacs and it pops up an annoying dialog window about an altered file it is visiting almost immediately. Here is the first bug: *almost* immediately: if you are quick, you can alter the buffer before the window steals focus. Suppose you were not that fast, so the buffer is unaltered, and you answer no to the dialog. Here is the second bug: emacs shows another, identical, dialog. If you keep answering no, emacs shows 3-15 identical dialogs, asking the very same question. (It's possible it only shows 3 if you were not fast enough, I got too angry to test more, but it's quite possible the number of dialogs equals 3+number of changes you made before the dialog appeared.) Close emacs. Start is again, visit the file again, but this time alter the buffer before switching away and touching the file in a terminal (or whatever you like to do to make emacs think it has been altered) and then go back to emacs again. Answer no to the dialog as many times as emacs asks you and then save the buffer. Emacs now asks you the usual question about a file changed on disk, to which you should answer to save the buffer anyway. Here is the third bug: now emacs asks you whether you want to revert the buffer or overwrite the changed file with your buffer, but then immediately (you might be fast enough to answer that first, please be slow) asks the new question about discaring edits because the file your buffer is visiting has changed. At this point, emacs is unusable: the first question has apparently removed all keybindings since there is no way of making the second question go away. Any key I press causes the same message to be displayed: key is undefined. I cannot save the file, revert the buffer, or even C-g or Esc, because every key I can think of is undefined. Likewise mouse. (Menu works, but does not help.) Expected outcome: Bug 1: nothing. No questions, no dialogs, nothing. Or at least an option to turn this annoying new feature off. Bug 2: Just one question per buffer. Bug 3: Buffer saved according to my wish. Cheers, Juha -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages emacs24 depends on: ii emacs24-bin-common 24.3+1-1.1 ii gconf-service3.2.6-1 ii libasound2 1.0.27.2-1 ii libatk1.0-0 2.10.0-2 ii libc62.17-93 ii libcairo-gobject21.12.16-2 ii libcairo21.12.14-4 ii libdbus-1-3 1.6.14-1 ii libfontconfig1 2.10.2-2 ii libfreetype6 2.4.9-1.1 ii libgconf-2-4 3.2.6-1 ii libgdk-pixbuf2.0-0 2.28.2-1 ii libgif4 4.1.6-10 ii libglib2.0-0 2.36.4-1 ii libgnutls26 2.12.23-7 ii libgomp1 4.8.1-10 ii libgpm2 1.20.4-6.1 ii libgtk-3-0 3.8.4-1 ii libice6 2:1.0.8-2 ii libjpeg8 8d-1 ii libm17n-01.6.4-2 ii libmagickcore5 8:6.7.7.10-6 ii libmagickwand5 8:6.7.7.10-6 ii libotf0 0.9.13-1 ii libpango-1.0-0 1.32.5-5+b1 ii libpangocairo-1.0-0 1.32.5-5+b1 ii libpng12-0 1.2.49-4 ii librsvg2-2 2.36.4-2 ii libselinux1 2.1.13-2 ii libsm6 2:1.2.1-2 ii libtiff4 3.9.7-2 ii libtinfo55.9+20130608-1 ii libx11-6 2:1.6.1-1 ii libxft2 2.3.1-1 ii libxml2 2.9.1+dfsg1-3 ii libxpm4 1:3.5.10-1 ii libxrender1 1:0.9.8-1 ii zlib1g 1:1.2.8.dfsg-1 emacs24 recommends no packages. Versions of packages emacs24 suggests: pn emacs24-common-non-dfsg none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#664247: [Pkg-xfce-devel] Bug#664247: xfce4-notifyd: notifications never die
If I try to send a notification to xfce4-notifyd, the notification stays on the screen until xfce4-notifyd is killed. This happens regardless of the default timeout set with xfce4-notifyd-config. I am curious if you can reproduce this issue with xfce4-notifyd from unstable (0.2.4-2). There was bug that caused notification timeout not No, I cannot. So, from my point of view, #664247 can be closed. I think the other problems you mention are different and should not be dealt with here. Thanks. -Juha -- --- | Juha Jäykkä, ju...@iki.fi | | http://koti.kapsi.fi/~juhaj/ | --- signature.asc Description: This is a digitally signed message part.
Bug#701711: emacs24: svn support fails in a symlinked directory
Package: emacs24 Version: 24.2+1-2 Severity: normal vc-update and other vc-*-commands fail to detect an svn controlled directory when the directory is a symlink to an svn controlled directory. The new SVN working copy directory tree only has .svn directory at the topmost level and it seems emacs does 'chdir(..)' or something equivalent when it tries to find the .svn directory. However, if directory A is a symlink to an svn working copy directory B, then looking at A/.. is not the right place to look for .svn; instead, emacs should note that A is a symlink, readlink() and look at B/.. instead. Cheers, Juha -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages emacs24 depends on: ii emacs24-bin-common 24.2+1-2 ii gconf-service 3.2.5-1+build1 ii libasound2 1.0.25-4 ii libatk1.0-0 2.4.0-2 ii libc6 2.13-35 ii libcairo-gobject2 1.12.2-2 ii libcairo2 1.12.2-2 ii libdbus-1-3 1.6.8-1 ii libfontconfig1 2.9.0-7 ii libfreetype62.4.9-1 ii libgconf-2-43.2.5-1+build1 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libgif4 4.1.6-10 ii libglib2.0-02.33.12+really2.32.4-3 ii libgnutls26 2.12.20-1 ii libgomp14.7.1-7 ii libgpm2 1.20.4-6 ii libgtk-3-0 3.4.2-4 ii libice6 2:1.0.8-2 ii libjpeg88d-1 ii libm17n-0 1.6.3-2 ii libmagickcore5 8:6.7.7.10-4 ii libmagickwand5 8:6.7.7.10-4 ii libncurses5 5.9-10 ii libotf0 0.9.12-2 ii libpango1.0-0 1.30.0-1 ii libpng12-0 1.2.49-1 ii librsvg2-2 2.36.1-1 ii libselinux1 2.1.9-5 ii libsm6 2:1.2.1-2 ii libtiff43.9.6-9 ii libtinfo5 5.9-10 ii libx11-62:1.5.0-1 ii libxft2 2.3.1-1 ii libxml2 2.8.0+dfsg1-6 ii libxpm4 1:3.5.10-1 ii libxrender1 1:0.9.7-1 ii zlib1g 1:1.2.7.dfsg-13 emacs24 recommends no packages. Versions of packages emacs24 suggests: pn emacs24-common-non-dfsg none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#582953: kmail deleted all non-local incoming mail settings on upgrade
Juha, I think this bug is never going to be fixed unless someone can give us a clear path to reproducing it. I think you're the person in a best This happened at an upgrade, which does not happen all that often, especially now that wheezy is frozen, so it is rather hard to try to reproduce it as I do not have a spare machine to run test installs on. Sorry. OTOH, the version this happened with is already several KDE versions ago, so perhaps this can just be closed as soon as kdepim gets upgraded from the 4.4- family to 4.8 or whatever it eventually gets upgraded to. -Juha -- --- | Juha Jäykkä, ju...@iki.fi | | http://koti.kapsi.fi/~juhaj/ | --- signature.asc Description: This is a digitally signed message part.
Bug#360147: firefox: firefox doesn't inform the user that a print-to-file fails when the requested directory lacks write permission
Package: iceweasel
Version: 10.0.6esr-2
Followup-For: Bug #360147
The bug still exists.
Could the maintainers mark this with wontfix or something? The bug has been
open for over SIX YEARS so it is obvious it will never be fixed (unless by
accident).
-Juha
-- Package-specific info:
-- Extensions information
Name: Default theme
Location: /usr/lib/iceweasel/extensions/{972ce4c6-7e08-4474-a285-3208198ce6fd}
Package: iceweasel
Status: enabled
Name: F.B. Purity - Cleans Up Facebook
Location: ${PROFILE_EXTENSIONS}/f...@fbpurity.com.xpi
Status: user-disabled
Name: NoScript
Location: ${PROFILE_EXTENSIONS}/{73a6fe31-595d-460b-a920-fcc0f8843232}.xpi
Status: enabled
Name: Scholar H-Index Calculator
Location: ${PROFILE_EXTENSIONS}/{e55904c8-769b-4ffe-8d47-48f411f37d22}.xpi
Status: enabled
Name: Tab Kit
Location: ${PROFILE_EXTENSIONS}/tab...@jomel.me.uk
Status: app-disabled
Name: TabKit 2nd Edition
Location: ${PROFILE_EXTENSIONS}/tabk...@pikachuexe.amateur.hk.xpi
Status: enabled
-- Plugins information
Name: Java(TM) Plug-in 1.6.0_26
Location: /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/libnpjp2.so
Package: sun-java6-bin
Status: disabled
Name: Skype Buttons for Kopete
Location: /usr/lib/mozilla/plugins/skypebuttons.so
Package: kopete
Status: enabled
-- Addons package information
ii iceweasel 10.0.6esr-2 amd64Web browser based on Firefox
ii kopete 4:4.7.4-2+b1 amd64instant messaging and chat applic
ii sun-java6-bin 6.26-3 amd64Sun Java(TM) Runtime Environment
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages iceweasel depends on:
ii debianutils 4.3.3
ii fontconfig 2.9.0-7
ii libc6 2.13-35
ii libgdk-pixbuf2.0-0 2.26.1-1
ii libglib2.0-02.32.3-1
ii libgtk2.0-0 2.24.10-2
ii libnspr4-0d 4.9-1
ii libsqlite3-03.7.13-1
ii libstdc++6 4.7.1-7
ii procps 1:3.3.3-2
ii xulrunner-10.0 10.0.6esr-2
iceweasel recommends no packages.
Versions of packages iceweasel suggests:
ii fonts-stix [otf-stix] 1.1.0-1
ii libgssapi-krb5-2 1.10.1+dfsg-2
pn mozplugger none
Versions of packages xulrunner-10.0 depends on:
ii libasound21.0.25-4
ii libatk1.0-0 2.4.0-2
ii libbz2-1.01.0.6-4
ii libc6 2.13-35
ii libcairo2 1.12.2-2
ii libdbus-1-3 1.6.2-2
ii libdbus-glib-1-2 0.100-1
ii libevent-2.0-52.0.19-stable-3
ii libfontconfig12.9.0-7
ii libfreetype6 2.4.9-1
ii libgcc1 1:4.7.1-7
ii libgdk-pixbuf2.0-02.26.1-1
ii libglib2.0-0 2.32.3-1
ii libgtk2.0-0 2.24.10-2
ii libhunspell-1.3-0 1.3.2-4
ii libjpeg8 8d-1
ii libmozjs10d 10.0.6esr-2
ii libnotify40.7.5-1
ii libnspr4-0d 4.9-1
ii libnss3-1d3.13.3-1
ii libpango1.0-0 1.30.0-1
ii libpixman-1-0 0.26.0-3
ii libreadline6 6.2-8
ii libsqlite3-0 3.7.13-1
ii libstartup-notification0 0.12-1
ii libstdc++64.7.1-7
ii libvpx1 1.1.0-1
ii libx11-6 2:1.5.0-1
ii libxext6 2:1.3.1-2
ii libxrender1 1:0.9.7-1
ii libxt61:1.1.3-1
ii zlib1g1:1.2.7.dfsg-13
Versions of packages xulrunner-10.0 suggests:
ii libcanberra0 0.28-4
ii libgnomeui-0 2.24.5-2
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680211: emacs svn support is broken
The emacs package doesn't provide Emacs itself. I suppose that the real bug is in emacs23, because I have no such problem with emacs24. Sorry for the confusion. Yes, emacs23 is what I have. Cheers, Juha -- --- | Juha Jäykkä, ju...@iki.fi | | http://koti.kapsi.fi/~juhaj/ | --- signature.asc Description: This is a digitally signed message part.
Bug#625832: python-mpi4py: importing MPI fails
I cannot reproduce this with the version in stable, nor with the unstable version built on stable or in an unstable chroot. I am downgrading this bug and mark it unreproducible for now. How did you compile the above program, what architecture was this on and was it on an update unstable system? Can you try again with an updated unstable system? It seems to work on an up-to-date unstable now. And I am pretty sure it has been working for quite a long time for that matter: I do not recall the whole issue any longer, so it cannot have plagued me for a long time. As it is almost a year since I reported the bug, I cannot recall the exact specs of the system any longer: I can guess from the bug report which computer it was, but not the package versions apart from those present in the report, which are missing some thanks to my reporting it against the wrong package originally. But, as I see no changes to any of the openmpi packages since April 2011, it is hard to see why anything would have changed. From my point of view just mark this solved at the next upload. -Juha signature.asc Description: This is a digitally signed message part.
Bug#630839: close?
Should this not have been closed by the 1.8.1-1 upload? Cheers, Juha -- --- | Juha Jäykkä, ju...@iki.fi | --- signature.asc Description: This is a digitally signed message part.
Bug#667980: should this be reassigned?
This is not a bug in sssd, but in libldap-2.4-2, so should this actually be reassigned to libldap-2.4-2? I would do that, but the bug is already open there (#666230), so I am not sure what is the correct procedure. Reassign + merge? Cheers, Juha -- --- | Juha Jäykkä, ju...@iki.fi | --- signature.asc Description: This is a digitally signed message part.
Bug#666230: libldap-2.4-2: ldap_result returns -1 when called from sssd
Package: libldap-2.4-2 Version: 2.4.28-1.2 Severity: serious Tags: upstream patch Justification: breaks unrelated software on the system (which is rc-critical as per http://release.debian.org/wheezy/rc_policy.txt) After an upgrade from 2.4.25, sssd ldap lookups stop working due to ldap_result returning -1 even on success. Please see https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/929888 for details on the bug and http://www.openldap.org/its/index.cgi?findid=7167 for a patch. Cheers, Juha Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these lines *** -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libldap-2.4-2 depends on: ii libc6 2.13-27 ii libgcrypt111.5.0-3 ii libgnutls262.12.18-1 ii libsasl2-2 2.1.25.dfsg1-4 ii multiarch-support 2.13-27 libldap-2.4-2 recommends no packages. libldap-2.4-2 suggests no packages. -- Configuration Files: /etc/ldap/ldap.conf changed [not included] -- no debconf information -- debsums errors found: debsums: package libldap-2.4-2 is not installed -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#628444: iwlagn - MAC is in deep sleep, cannot restore wifi operation
This may or may not be related, but I thought it best to inform you about what I just saw anyway: I accidentally toggled the physical RF kill switch on my laptop and the result was very much reminiscent of the bug we are discussing (note the QoS and failure to remove key): Mar 22 20:13:47 rigel kernel: [1259943.614216] iwlwifi :03:00.0: RF_KILL bit toggled to disable radio. Mar 22 20:13:47 rigel kernel: [1259943.614350] iwlwifi :03:00.0: Not sending command - RF KILL Mar 22 20:13:47 rigel kernel: [1259943.614359] iwlwifi :03:00.0: Error sending REPLY_QOS_PARAM: enqueue_hcmd failed: -5 Mar 22 20:13:47 rigel kernel: [1259943.614366] iwlwifi :03:00.0: Failed to update QoS Mar 22 20:13:47 rigel kernel: [1259943.614374] iwlwifi :03:00.0: Not sending command - RF KILL Mar 22 20:13:47 rigel kernel: [1259943.614381] iwlwifi :03:00.0: Error sending REPLY_RXON: enqueue_hcmd failed: -5 Mar 22 20:13:47 rigel kernel: [1259943.614388] iwlwifi :03:00.0: Error clearing ASSOC_MSK on BSS (-5) Mar 22 20:13:47 rigel kernel: [1259943.614400] iwlwifi :03:00.0: Not sending command - RF KILL Mar 22 20:13:47 rigel kernel: [1259943.614407] iwlwifi :03:00.0: Error sending REPLY_RXON: enqueue_hcmd failed: -5 Mar 22 20:13:47 rigel kernel: [1259943.614414] iwlwifi :03:00.0: Error clearing ASSOC_MSK on BSS (-5) Mar 22 20:13:47 rigel kernel: [1259943.614422] wlan0: deauthenticating from 00:24:17:33:f4:f5 by local choice (reason=3) Mar 22 20:13:47 rigel kernel: [1259943.624234] iwlwifi :03:00.0: Not sending command - RF KILL Mar 22 20:13:47 rigel kernel: [1259943.624238] iwlwifi :03:00.0: Error sending REPLY_ADD_STA: enqueue_hcmd failed: -5 Mar 22 20:13:47 rigel kernel: [1259943.624242] ieee80211 phy0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-5) Mar 22 20:13:47 rigel kernel: [1259943.624339] iwlwifi :03:00.0: Not sending command - RF KILL Mar 22 20:13:47 rigel kernel: [1259943.624342] iwlwifi :03:00.0: Error sending REPLY_ADD_STA: enqueue_hcmd failed: -5 Mar 22 20:13:47 rigel kernel: [1259943.624346] ieee80211 phy0: failed to remove key (0, 00:24:17:33:f4:f5) from hardware (-5) Mar 22 20:13:47 rigel kernel: [1259943.624351] iwlwifi :03:00.0: Not sending command - RF KILL Mar 22 20:13:47 rigel kernel: [1259943.624354] iwlwifi :03:00.0: Error sending REPLY_REMOVE_STA: enqueue_hcmd failed: -5 Mar 22 20:13:47 rigel kernel: [1259943.624358] iwlwifi :03:00.0: Error removing station 00:24:17:33:f4:f5 Mar 22 20:13:47 rigel kernel: [1259943.624391] iwlwifi :03:00.0: Not sending command - RF KILL Mar 22 20:13:47 rigel kernel: [1259943.624394] iwlwifi :03:00.0: Error sending REPLY_RXON: enqueue_hcmd failed: -5 Mar 22 20:13:47 rigel kernel: [1259943.624397] iwlwifi :03:00.0: Error clearing ASSOC_MSK on BSS (-5) Mar 22 20:13:47 rigel kernel: [1259943.624425] iwlwifi :03:00.0: Not sending command - RF KILL Mar 22 20:13:47 rigel kernel: [1259943.624428] iwlwifi :03:00.0: Error sending REPLY_LEDS_CMD: enqueue_hcmd failed: -5 Mar 22 20:13:47 rigel kernel: [1259943.624433] iwlwifi :03:00.0: Not sending command - RF KILL Mar 22 20:13:47 rigel kernel: [1259943.624436] iwlwifi :03:00.0: Error sending REPLY_RXON: enqueue_hcmd failed: -5 Mar 22 20:13:47 rigel kernel: [1259943.624439] iwlwifi :03:00.0: Error clearing ASSOC_MSK on BSS (-5) Mar 22 20:13:47 rigel kernel: [1259943.624459] cfg80211: Calling CRDA to update world regulatory domain Mar 22 20:13:47 rigel kernel: [1259943.640238] iwlwifi :03:00.0: Not sending command - RF KILL Mar 22 20:13:47 rigel kernel: [1259943.640245] iwlwifi :03:00.0: Error sending REPLY_RXON: enqueue_hcmd failed: -5 Mar 22 20:13:47 rigel kernel: [1259943.640249] iwlwifi :03:00.0: Error clearing ASSOC_MSK on BSS (-5) After switching the radios back on, I get Mar 22 20:14:22 rigel kernel: [1259978.719860] iwlwifi :03:00.0: RF_KILL bit toggled to enable radio. but *absolutely* *nothing* *else*. No RF LED, nothing. However, unlike the bug we are discussing, reloading the iwlwifi module fixed this. Hope this helps, Juha -- --- | Juha Jäykkä, ju...@iki.fi | | http://www.maths.leeds.ac.uk/~juhaj | --- signature.asc Description: This is a digitally signed message part.
Bug#664905: notify-osd: notification timeout not respected
Package: notify-osd Version: 0.9.32-2 Severity: important If I try to send a notification to notify-osd, the notification stays on the screen for 10 seconds before timing out. This happens regardless of the timeout set by the client (clients tried: pynotify and notify-send). Cheers, Juha -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages notify-osd depends on: ii dconf-gsettings-backend [gsettings-backend] 0.10.0-3 ii libatk1.0-0 2.2.0-2 ii libc62.13-21 ii libcairo21.10.2-6.1 ii libdbus-1-3 1.4.16-1 ii libdbus-glib-1-2 0.98-1 ii libgdk-pixbuf2.0-0 2.24.0-1 ii libglib2.0-0 2.30.2-4 ii libgtk-3-0 3.2.3-1 ii libpango1.0-01.29.4-2 ii libpixman-1-00.23.8-1 ii libwnck-3-0 3.2.1-1 ii libx11-6 2:1.4.4-2 notify-osd recommends no packages. notify-osd suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#628444: iwlagn - MAC is in deep sleep, cannot restore wifi operation
My update (after a reboot caused by a crashed hibernation attempt at uptime ~8 days): juhaj@rigel uptime 00:18:27 up 14 days, 6:50, 9 users, load average: 0.00, 0.03, 0.05 juhaj@rigel cat /proc/cmdline BOOT_IMAGE=/vmlinuz-3.2.0-1-amd64 root=/dev/mapper/system-root ro quiet usbcore.autosuspend=1 video=intelfb:1440x900M@60 pcie_aspm=off juhaj@rigel grep . /sys/module/iwlwifi/parameters/* /sys/module/iwlwifi/parameters/11n_disable:0 /sys/module/iwlwifi/parameters/ack_check:N /sys/module/iwlwifi/parameters/amsdu_size_8K:1 /sys/module/iwlwifi/parameters/antenna_coupling:0 /sys/module/iwlwifi/parameters/auto_agg:Y /sys/module/iwlwifi/parameters/bt_ch_inhibition:Y /sys/module/iwlwifi/parameters/bt_coex_active:Y /sys/module/iwlwifi/parameters/fw_restart:1 /sys/module/iwlwifi/parameters/led_mode:0 /sys/module/iwlwifi/parameters/no_sleep_autoadjust:Y /sys/module/iwlwifi/parameters/plcp_check:Y /sys/module/iwlwifi/parameters/power_level:0 /sys/module/iwlwifi/parameters/power_save:N /sys/module/iwlwifi/parameters/queues_num:0 /sys/module/iwlwifi/parameters/swcrypto:0 /sys/module/iwlwifi/parameters/ucode_alternative:1 /sys/module/iwlwifi/parameters/wd_disable:0 (I think these are all defaults.) rigel kernel: [1073316.734468] iwlwifi :03:00.0: L1 Enabled; Disabling L0S juhaj@rigel uname -a Linux rigel 3.2.0-1-amd64 #1 SMP Fri Feb 17 05:17:36 UTC 2012 x86_64 GNU/Linux There have been TWO changes since I last had problems: 1. pcie_aspm=off 2. re-seating the iwlwifi mini-pci card in its socket I am starting to believe I am in the clear here, but I am not yet convinced since the root cause is still unknown. In any case, thanks for all of you for helping hunt this down. Dafydd: I think you might want to try pcie_asmp=off next Cheers, Juha -- --- | Juha Jäykkä, ju...@iki.fi | | http://www.maths.leeds.ac.uk/~juhaj | --- signature.asc Description: This is a digitally signed message part.
Bug#630839: ping
On Saturday 17 Mar 2012 13:39:50 Neil Williams wrote: There is a new version available in unstable, 1.2.1-4.4, please check if this bug is still affecting your systems. Many thanks for taking this up, but unfortunately the update makes no difference: (Sun Mar 18 11:06:35 2012) [sssd[be[MY.DOMAIN]]] [ldb] (0): WARNING: Module [memberof] not found - do you need to set LDB_MODULES_PATH? (Sun Mar 18 11:06:35 2012) [sssd[be[MY.DOMAIN]]] [ldb] (0): Unable to load modules for /var/lib/sss/db/cache_MY.DOMAIN.ldb: (null) (Sun Mar 18 11:06:35 2012) [sssd[be[MY.DOMAIN]]] [be_process_init] (0): fatal error opening cache database (Sun Mar 18 11:06:35 2012) [sssd[be[MY.DOMAIN]]] [main] (0): Could not initialize backend [5] And thereafter all other services fail, too. The only difference is that now sssd itself stays running when started with an empty /var/lib/sss/db whereas before it refused to start alltogether. Even now, once sssd is strated once and /var/lib/sss/db is populated, the next time it refuses to start. This bug should not really be so hard to fix: there is a new LTM version of sssd (1.8.1(!)) and who knows how many intermediate versions since 1.2.1. Ubuntu already has some of these packaged and taking those packages and repackaging them for Debian is almost trivial. There is one catch, though: these Ubuntu packages depend on other packages not present in Debian, but those packages come from sssd sources anyway (unless I missed some), so they can simply be all stuffed into a single sssd package for Debian if creating new packages and waiting for them to appear in unstable takes too long. For now, I am back to using my own packages compiled from Ubuntu's (oneiric) sources. Has anyone heard anything from the maintainer(s), btw? The last *FOUR* updates of this package are NMU's! I am cc'ing the latest NM uploader, too: I am more than willing to help with getting this resolved since come wheezy, I will have a big issue at my hands if this does not get fixed. I know how to get the Ubuntu packages to run on unstable, so if that helps anyone develop a solution to this, I am ready to assist. Cheers, Juha -- --- | Juha Jäykkä, ju...@iki.fi | | http://www.maths.leeds.ac.uk/~juhaj | --- signature.asc Description: This is a digitally signed message part.
Bug#630839: ping
Correction: I am currently using sssd 1.6.2 from https://fedorahosted.org/sssd/ but some dependencies are from oneiric, namely: libcollection, libdhash, libini-config, their -dev's and their dependencies (which are libpath-utils and libref-array, at least on my system). Also, when building 1.6.2, I use the debian/ from Debian sssd/1.2.1-4.3 because the Ubuntu debian/ includes dependencies on upstart which I do not use. I do not think there is any reason not to use 1.8.1, but 1.6.2 *WORKS* and it was the newest when I encountered and worked around this bug. Cheers, Juha -- --- | Juha Jäykkä, ju...@iki.fi | | http://www.maths.leeds.ac.uk/~juhaj | --- signature.asc Description: This is a digitally signed message part.
Bug#630839: ping
E: Unable to locate package libdhash-dev E: Unable to locate package libcollection-dev E: Unable to locate package libini-config-dev Like I said, libcollection, libdhash, libini-config, their -dev's are needed. More work for whoever ends up maintaining it. This is about as far as I'm willing to take this exercise. The only thing I'm likely to do about sssd now is to seek removal if this bug isn't fixed. These libs used to be part of sssd, up to at least 1.2.1, so I am not sure if they need individual packaging. Anyway, the current maintainer has already started maintaining said packages in Debian. However, I admit having them as separate packages is cleaner, but probably not worth it in the wheezy timescale. Would packaging all of these into one sssd package be acceptable for wheezy? 1.8.1 will need to be supported eventually, there is no point doing the work for 1.6.2 in a way that prevents 1.8.1 ever being possible. To do so would be very short sighted. I only mentioned that detail because that is what I happen to be running now. Of course, the current LTM version is the right way to go for packaging this un Debian. TBH I think sssd users are going to have to get used to not having sssd available in Debian and will need to migrate to something else. There I would be willing to take sssd if I had any experience in maintaining a Debian package (apart from some built for internal purposes). Therefore, I concur: the 84 users (according to popcon) who are using sssd at the moment will need to migrate to something else. However, I do not think there IS something else. At least I am not aware of ANY alternative to sssd. Are you? The closest thing I know of is libpam- ccreds, but that does not provide nss, just the equivalent of libpam-sss. Debian. This bug has already been open for 8 months without anyone actually providing a workable solution, likely due to a lack of interest in sssd in the long term. Perhaps the Ubuntu people would be of help here? They already package this and the only thing preventing me from using those packages directly is the fact that they depend on upstart. (I have not tested upstart, perhaps it is vastly superior to sysv-rc, but *depending* on it seems like a bad idea: I cannot believe a daemon really depends on upstart and would not work with sysv-rc.) If nobody cares enough to do the work, sssd will have to be removed. Agreed. I would hate to go to upstart (sysv-rc is not broken, so I would rather NOT replace it with anything), but unless I can get someone to help me get started with maintaining this and others, sssd will need to go. Where should I ask for mentor/sponsor? Please drop me from CC now, I've done what I can. The rest is down to those who have a reason to work on sssd. I don't. I still sent you this despite the request, I hope you are not offended. As the questions I ask are of a generic nature, I thought you might be able to answer them despite declaring otherwise. =) Cheers, Juha -- --- | Juha Jäykkä, ju...@iki.fi | | http://www.maths.leeds.ac.uk/~juhaj | --- signature.asc Description: This is a digitally signed message part.
Bug#630839: ping
I am sorry for replying to these accidentally in the LIFO order... Are you talking about: libipa-hbac-dev libsss-sudo-dev libsss-sudo0 python-libipa-hbac libipa-hbac0 sssd-tools libnss-sss libpam-sss python-sss sssd I do not think all of these are necessary, but it may be for some use cases. For my use case (auth and nss from kerberos, ldap and local files), just the following are needed: libnss-sss libpam-sss python-sss sssd The various *ipa-* packages probably relate to using RedHat's freeIPA (http://www.freeipa.org/page/Main_Page). I have no idea what sssd-tools contains and I do not know about the sudo-related packages either: sudo and sssd work fine without them. Of course, the various other dependencies and build-deps are required, too. Can you confirm that all the binary packages necessary to install sssd from Ubuntu onto standard Debian unstable are in the first list above? The dependencies I mentioned earlier (though possibly not before you wrote the email I am replying to) are: libcollection libdhash libpath-utils libref-array libini-config The last two are actually dependencies of the first three, not direct dependencies of sssd, but necessary anyway. An additional twist is this: https://bugzilla.redhat.com/show_bug.cgi?id=771484 In other words, sssd, even the Ubuntu versions, on Debian/sid *IS* *BROKEN* because of changes in libldap-2.4. The upstream libldap seems to fix this, likewise downgrading to 2.4.25-4, but at the moment, we would have sssd name lookups from ldap broken no matter what. Nice, isn't it? could be removed without causing problems elsewhere.) Someone who cares about sssd has to do the work. Like I said earlier, given suitable mentoring, I would be willing to take this up. Volunteers? Petter? =) Cheers, Juha -- --- | Juha Jäykkä, ju...@iki.fi | | http://www.maths.leeds.ac.uk/~juhaj | --- signature.asc Description: This is a digitally signed message part.
Bug#664247: [Pkg-xfce-devel] Bug#664247: xfce4-notifyd: notifications never die
If I try to send a notification to xfce4-notifyd, the notification stays on the screen until xfce4-notifyd is killed. This happens regardless of the default timeout set with xfce4-notifyd-config. What happens if you use notify-send? Maybe you *need* to call .close()? Oh, sorry. I my report was a bit misleading: the first paragraph was meant to include a mention that this is the behaviour with notify-send and the second paragraph just a confirmation that the behaviour is NOT due to notify-send, hence due to xfce4-notifyd. In short: it does not matter what client sends the notification, the behaviour is always the same. Cheers, -Juha -- --- | Juha Jäykkä, ju...@iki.fi | | http://www.maths.leeds.ac.uk/~juhaj | --- signature.asc Description: This is a digitally signed message part.
Bug#664247: xfce4-notifyd: notifications never die
Package: xfce4-notifyd Version: 0.2.2-1 Severity: important If I try to send a notification to xfce4-notifyd, the notification stays on the screen until xfce4-notifyd is killed. This happens regardless of the default timeout set with xfce4-notifyd-config. If using pynotify to show the notification, the .close() method is able to get rid of the notification, but the timeout is still not respected. -Juha -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages xfce4-notifyd depends on: ii libc6 2.13-21 ii libcairo2 1.10.2-6.1 ii libdbus-1-3 1.4.16-1 ii libdbus-glib-1-20.98-1 ii libgdk-pixbuf2.0-0 2.24.0-1 ii libglib2.0-02.30.2-4 ii libgtk2.0-0 2.24.7-1 ii libpango1.0-0 1.29.4-2 ii libx11-62:1.4.4-2 ii libxfce4ui-1-0 4.8.0-3 ii libxfce4util4 4.8.2-1 ii libxfconf-0-2 4.8.0-3 Versions of packages xfce4-notifyd recommends: ii libnotify-bin 0.7.4-1 xfce4-notifyd suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#664248: notification-daemon: notification timeout not respected
Package: notification-daemon Version: 0.7.3-1 Severity: important If I try to send a notification to notification-daemon, the notification stays on the screen for 5 seconds before timing out. This happens regardless of the timeout set by the client (clients tried: pynotify and notify-send). This used to work in squeeze. -Juha -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages notification-daemon depends on: ii libatk1.0-0 2.2.0-2 ii libc6 2.13-21 ii libcairo2 1.10.2-6.1 ii libcanberra-gtk3-0 0.28-3 ii libgdk-pixbuf2.0-0 2.24.0-1 ii libglib2.0-02.30.2-4 ii libgtk-3-0 3.0.12-2 ii libx11-62:1.4.4-2 notification-daemon recommends no packages. notification-daemon suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#628444: Info received (iwlagn - MAC is in deep sleep, cannot restore wifi operation)
that the memory slots and mini-pcie slots are behind the same cover in the X201 as well? Replugging it seems like a good idea... I wish they were! They are in X4? and X30? but not X200s, where I had to remove the keyboard and handrest to get to the card. Most annoying. Nevertheless, the RAM is quit directly on the opposite side of the motherboard compared to the miniPCI slots (there are two: one is empty, I guess it is meant for 3g), so I would not rule out the miniPCI card moving when addin RAM. Especially since I now have almost 3 days of uptime without problems! This is the record since my problems started except for disabling 802.11n and powersave completely, which gave me about a week. I will report back when I loose wifi again or in two weeks if I do not loose it by then (in which case I will assume it was indeed loose in its socket). [ 12.610618] iwlwifi :03:00.0: pci_resource_base = c90005794000 [ 12.610835] iwlwifi :03:00.0: irq 44 for MSI/MSI-X These are different, but I assume it does not matter. [ 12.611061] iwlwifi :03:00.0: L1 Disabled; Enabling L0S I get: [245082.407512] iwlwifi :03:00.0: L1 Enabled; Disabling L0S Does this have any effect? What are L1 and L0S anyway? [ 12.630680] iwlwifi :03:00.0: device EEPROM VER=0x11e, CALIB=0x4 My EEPROM VER=0x11f, but otherwise everything matches. Cheers, Juha -- --- | Juha Jäykkä, ju...@iki.fi | | http://www.maths.leeds.ac.uk/~juhaj | --- signature.asc Description: This is a digitally signed message part.
Bug#628444: Info received (iwlagn - MAC is in deep sleep, cannot restore wifi operation)
For a complete power-cycle, you may need to remove both the power cord and the battery. I don't think the Intel wireless cards have any Sure, I did: detach the cord and battery, wait ten minutes, then plug them back in. No use. The log messages you sent are indicative of a total failure of communication with the card. My suspicion would be that the hardware has developed a fault, but it could be as simple as the card being slightly loose in its slot. Total? How come? It does detect the card correct, except the revision, which is 0x instead of 0x24 as it should. My guess is the final error comes from the incorrect revision number – of course it probably fails already somewhere earlier and simply getting the revision right (which could be hard- coded in the driver) probably would not help. Having said that, are you setting the pcie_aspm kernel parameter? Like Shannon, I have not touched it at all, so it is probably off (whatever the default is). One thing I tries, is turn all PCI* related power-save features off from the BIOS, but that did not help. My most important question is: how do I get back to the working state? Going back in driver and kernel versions does not seem to help! I admit that the above sounds like a HW failure, but like Shannon, I do not believe it because a full *kernel* reboot *always* fixes the issue. Why would a faulty hardware get fixed when the kernel gets rebooted, but NOT when the computer power gets completely turned off and all the hardware reinitialised during a hibernate cycle. I even tried the following sequence: hibernate, unplug power cord and battery, wait a few minutes, plug back in, reboot *a* *different* *kernel*, see that the wifi works with this kernel, shut down, reboot with the original kernel, unsuspending from hibernate. At this point, the wifi does not work. I think this is quite a strong indication that this is NOT a HW issue. But what makes me most confused is that rolling back to versions of wireless- tools, firmware-iwlwifi, and kernel does not give me back a working system, which does suggest a hw failure. Shannon: FWIF, I have now rebooted with pci_aspm=off and we'll see what happens. Ben: I also replugged the wifi card. Also, I am back to 3.2.6 and newest firmware (I forgot to roll back the newest wireless tools). -Juha -- --- | Juha Jäykkä, ju...@iki.fi | | http://www.maths.leeds.ac.uk/~juhaj | --- signature.asc Description: This is a digitally signed message part.
Bug#628444: Info received (iwlagn - MAC is in deep sleep, cannot restore wifi operation)
It wasn't required to trigger the problem on my system either, but it seemed to happen a lot more often in the first few minutes after coming out of hibernation. Sorry, what I meant to say is that not hibernating does not help me at all. an illusion due to the irratic nature of the problem). How long did you run it on 2.6.39 previously? Perhaps it would have happened with 2.6.39 previously had you used it for a longer period? My longest uptimes would be of the order of a couple of months all the way up to 3.0, after which my longest uptime has been ~48 h, regardless of the version of the kernel, firmware, or wireless tools. One thing just occurred to me: I added 2 GB of memory (total 4 GB) at about the time these problems started. I cannot say for sure the problems did not start earlier, but it is quite possible they started after! (Please do not tell Lenovo that I added the memory myself as I still have on-site warranty for another year or so. =) ) If the replugging of the wifi card does not solve the problem, i.e. if it resurfaces, I will try going back to 2 GB to see if that helps. Cheers, Juha -- --- | Juha Jäykkä, ju...@iki.fi | | http://www.maths.leeds.ac.uk/~juhaj | --- signature.asc Description: This is a digitally signed message part.
Bug#628444: Info received (iwlagn - MAC is in deep sleep, cannot restore wifi operation)
tried at least 5 different versions. I have almost completely stopped using hibernate (suspend only) on my system and have not seen the problem in a long time and for my system at least, hibernate seems to be related I never thought it was a firmware issue before, so I never paid any attention to the firmware versions before. But now that I am back to 0.33, it looks stable – although it is just 24 hours since last problem, that is nevertheless towards the longer intervals. Usually it is just a couple of hours unless the workarounds are on, which they are not at the moment (because I wanted to test this). I never had any issues with hibernate or suspend and certainly neither was ever needed to trigger the bug. For example yesterday, I hit the bug after about 3 hours without ever putting the laptop off my lap meanwhile. While the firmware may play a role in the problem, at its core, there [...] to look at the Linux driver(s) for the flavor of PCI interface bus these cards plug-in to and the particular chip sets used to implement this bus on the known Lenovo machines having the problem (x201i, x200, ...). This is past my knowledge and understanding, but it seems reasonable enough. Is there anything I can do? If the pci bus is the reason, it might explain the random freezes I have been experiencing (see #575965 for details), too. Ok, so I just hit the problem while writing this up: 0.33 2.6.39 does not help. Attached is what happened when I turned the HW kill switch after the MAC went to unrecoverable deep sleep. Perhaps that backtrace can help figure this out. What is VERY strange here is the fact that I did not have this problem before going from 2.6.39 to 3.0.0, but not I have it even with 2.6.39! How can that be?!? What else is involved with talking to the wifi card except the kernel and the firmware? Do I need to downgrade iwconfig et al, too? This is *very* annoying. I now need to boot more than once a day compared to once every few months before! -Juha -- --- | Juha Jäykkä, ju...@iki.fi | | http://www.maths.leeds.ac.uk/~juhaj | --- [75926.876147] [ cut here ] [75926.876171] WARNING: at /build/buildd-linux-2.6_2.6.39-2-amd64-kuqdRa/linux-2.6-2.6.39/debian/build/source_amd64_none/drivers/net/wireless/iwlwifi/iwl-core.c:1428 iwl_mac_remove_interface+0x3b/0x72 [iwlagn]() [75926.876176] Hardware name: 74695KG [75926.876178] Modules linked in: hidp hid tun acpi_cpufreq mperf cpufreq_stats cpufreq_userspace cpufreq_powersave cpufreq_conservative parport_pc ppdev lp parport rfcomm bnep autofs4 binfmt_misc uinput fuse nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc coretemp loop kvm_intel kvm snd_hda_codec_conexant arc4 i915 snd_hda_intel drm_kms_helper snd_hda_codec ecb snd_hwdep drm snd_pcm_oss snd_mixer_oss snd_pcm iwlagn i2c_algo_bit snd_seq_midi snd_rawmidi i2c_i801 thinkpad_acpi btusb iTCO_wdt iTCO_vendor_support i2c_core nvram snd_seq_midi_event snd_seq ac tpm_tis tpm tpm_bios battery snd_timer snd_seq_device evdev power_supply wmi mac80211 snd cfg80211 psmouse serio_raw bluetooth crc16 rfkill button processor soundcore snd_page_alloc video xfs sha256_generic cryptd aes_x86_64 aes_generic cbc dm_crypt dm_mod sd_mod crc_t10dif uhci_hcd ahci libahci ata_generic libata ehci_hcd scsi_mod usbcore thermal thermal_sys e1000e [last unloaded: scsi_wait_scan] [75926.876271] Pid: 24244, comm: kworker/0:1 Not tainted 2.6.39-2-amd64 #1 [75926.876274] Call Trace: [75926.876282] [810458b4] ? warn_slowpath_common+0x78/0x8c [75926.876290] [a0355696] ? iwl_mac_remove_interface+0x3b/0x72 [iwlagn] [75926.876298] [a01d1401] ? rfkill_register+0x1c7/0x212 [rfkill] [75926.876309] [a02cbc4e] ? ieee80211_do_stop+0x312/0x476 [mac80211] [75926.876315] [a01d144c] ? rfkill_register+0x212/0x212 [rfkill] [75926.876324] [a02cbdc7] ? ieee80211_stop+0x15/0x19 [mac80211] [75926.876330] [812793ce] ? __dev_close_many+0x91/0xc7 [75926.876333] [812794d1] ? dev_close_many+0x8b/0xfb [75926.876336] [81279574] ? dev_close+0x33/0x4a [75926.876343] [a021eee3] ? cfg80211_rfkill_set_block+0x3d/0x69 [cfg80211] [75926.876349] [a01d0cee] ? rfkill_set_block+0x7f/0xd5 [rfkill] [75926.876355] [a01d0fbd] ? rfkill_epo+0x34/0x89 [rfkill] [75926.876360] [a01d14a9] ? rfkill_op_handler+0x5d/0x138 [rfkill] [75926.876365] [81059f07] ? process_one_work+0x1d1/0x2ee [75926.876369] [8105be67] ? worker_thread+0x12d/0x247 [75926.876372] [8105bd3a] ? manage_workers+0x177/0x177 [75926.876375] [8105bd3a] ? manage_workers+0x177/0x177 [75926.876379] [8105ef05] ? kthread+0x7a/0x82 [75926.876384] [81339ee4] ? kernel_thread_helper+0x4/0x10 [75926.876387
Bug#628444: Info received (iwlagn - MAC is in deep sleep, cannot restore wifi operation)
0.35, and if I still see this, I will go back to ~0.30 to see if that fixes the issue. Down to 0.33, no help if running kernel 3.2. Now testing 0.33 2.6.39... -Juha -- --- | Juha Jäykkä, ju...@iki.fi | | http://www.maths.leeds.ac.uk/~juhaj | --- signature.asc Description: This is a digitally signed message part.
Bug#628444: iwlagn - MAC is in deep sleep, cannot restore wifi operation
Hi Jonathan! Sorry I took a while to respond and apologies in advance for them being quite useless... - steps to reproduce, assuming I had the same hardware Use the computer. My maximum time without hitting the bug has been less than 48 hours before I added the following module options: 11n_disable=1 power_save=0 wd_disable=1 which some googling suggested might solve it. They do not, but they make it less frequent. With them, I can even get a WEEK without seeing this. But notice I have different hw than the original reporter: mine is X200s with Intel Corporation Ultimate N WiFi Link 5300 (pci-id: 8086:4236). - expected result, actual result, and how the difference indicates a bug (should be simple enough in this case) =) Expected result: wifi keeps working unless I switch it off using rf_kill, physical switch, unload the module, or turn off the computer. Actual result: suddenly, out of the blue, in the middle of typing an email in kmail, see attachment. Bug: the wifi card has certainly not changed into Unknown hardware type suddenly. - how reproducible it is (100% of the time? 50%?) 100% when waiting long enough between reboots. - which kernel versions you have tested, and results with each There were no problems in the 2.6-series. The bug occurs at least in the Debian kernel versions 3.2.0-1-amd64, 3.0.0-2-amd64, and 3.0.0-1-amd64. - full dmesg output from booting and reproducing the bug, as an attachment Do not have it now, if really necessary, will get it next time it occurs (which may be a while: I am back to 2.6.39 because I need to get work done). - any other weird observations or workarounds No workaround. Above module parameters alleviate the issue. This is a regression, so I suggest someone with time (if anyone has it) bisects 2.6 and 3.2... horrible task, I do not envy anyone doing that. upstream to a public mailing list. So the purpose of these questions is to collect data on what's known so far as a starting point. Please CC me if you do. Cheers, Juha -- --- | Juha Jäykkä, ju...@iki.fi | | http://www.maths.leeds.ac.uk/~juhaj | --- [252832.820219] iwlwifi :03:00.0: Error sending POWER_TABLE_CMD: time out after 2000ms. [252832.820229] iwlwifi :03:00.0: Current CMD queue read_ptr 134 write_ptr 135 [252832.820237] iwlwifi :03:00.0: set power fail, ret = -110 [252835.320320] iwlwifi :03:00.0: Error sending REPLY_QOS_PARAM: time out after 2000ms. [252835.320331] iwlwifi :03:00.0: Current CMD queue read_ptr 134 write_ptr 137 [252835.320338] iwlwifi :03:00.0: Failed to update QoS [252837.320249] iwlwifi :03:00.0: Error sending REPLY_RXON: time out after 2000ms. [252837.320259] iwlwifi :03:00.0: Current CMD queue read_ptr 134 write_ptr 140 [252837.320267] iwlwifi :03:00.0: Error clearing ASSOC_MSK on BSS (-110) [252839.320130] iwlwifi :03:00.0: Error sending REPLY_RXON: time out after 2000ms. [252839.320140] iwlwifi :03:00.0: Current CMD queue read_ptr 134 write_ptr 143 [252839.320148] iwlwifi :03:00.0: Error clearing ASSOC_MSK on BSS (-110) [252841.320273] iwlwifi :03:00.0: Error sending REPLY_ADD_STA: time out after 2000ms. [252841.320283] iwlwifi :03:00.0: Current CMD queue read_ptr 134 write_ptr 146 [252841.320296] ieee80211 phy0: failed to remove key (0, 00:24:17:33:f4:f5) from hardware (-110) [252843.320053] iwlwifi :03:00.0: Error sending REPLY_REMOVE_STA: time out after 2000ms. [252843.320057] iwlwifi :03:00.0: Current CMD queue read_ptr 134 write_ptr 149 [252843.320061] iwlwifi :03:00.0: Error removing station 00:24:17:33:f4:f5 [252845.324086] iwlwifi :03:00.0: Error sending REPLY_RXON: time out after 2000ms. [252845.324096] iwlwifi :03:00.0: Current CMD queue read_ptr 134 write_ptr 152 [252845.324104] iwlwifi :03:00.0: Error clearing ASSOC_MSK on BSS (-110) [252847.328250] iwlwifi :03:00.0: fail to flush all tx fifo queues [252849.328175] iwlwifi :03:00.0: Error sending POWER_TABLE_CMD: time out after 2000ms. [252849.328185] iwlwifi :03:00.0: Current CMD queue read_ptr 134 write_ptr 154 [252849.328192] iwlwifi :03:00.0: set power fail, ret = -110 [252851.328203] iwlwifi :03:00.0: Error sending REPLY_RXON: time out after 2000ms. [252851.328214] iwlwifi :03:00.0: Current CMD queue read_ptr 134 write_ptr 155 [252851.328222] iwlwifi :03:00.0: Error clearing ASSOC_MSK on BSS (-110) [252853.328234] iwlwifi :03:00.0: Error sending REPLY_ADD_STA: time out after 2000ms. [252853.328245] iwlwifi :03:00.0: Current CMD queue read_ptr 134 write_ptr 156 [252853.328258] ieee80211 phy0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-110) [252853.328380] cfg80211: Calling CRDA to update world regulatory domain
Bug#628444: Debian bug #628444
Hi Shannon! What is the status of the fix from Intel? I have the same problem since upgrading to 3.x series and it is VERY annoying - only way I can fix it is rebooting the kernel, so it really seems a kernel bug. Hibernating the system and doing a full power-off (unplug AC, remove battery, wait 60 seconds – this should do it) the laptop does NOT fix it, so I concur: the kernel must retain some bogus information somewhere since the hw has definitely lost its status info. Cheers, -Juha -- --- | Juha Jäykkä, ju...@iki.fi | | http://www.maths.leeds.ac.uk/~juhaj | --- signature.asc Description: This is a digitally signed message part.
Bug#630839: severity 630839 grave
severity 630839 grave thanks Hi! As the maintainer, and co-maintainer have been eerily silent on this, I decided to bump this up to grave. I feel this is justified because installing sssd 1.2.1-4.3 on a system relying on sssd for logins will make logging in to the system impossible (as sssd will not run). This is actually almost trivial to fix: grab the source package for Ubuntu's sssd and use that. It will also be necessary to add the packages libcollection, libdhash, and libini-config because the Ubuntu package depends on those, but after that it works. It is what I do now. Cheers, Juha -- --- | Juha Jäykkä, ju...@iki.fi | | http://www.maths.leeds.ac.uk/~juhaj | --- signature.asc Description: This is a digitally signed message part.
Bug#587158: bluetoothd: No DBus connection
Package: bluez Version: 4.96-3 Followup-For: Bug #587158 A bit more details on this: First, bluetoothd fails to talk to D-Bud: rigel:~# bluetoothd -nd bluetoothd[19780]: Bluetooth daemon 4.96 bluetoothd[19780]: src/main.c:parse_config() parsing main.conf bluetoothd[19780]: src/main.c:parse_config() discovto=0 bluetoothd[19780]: src/main.c:parse_config() pairto=0 bluetoothd[19780]: src/main.c:parse_config() pageto=8192 bluetoothd[19780]: src/main.c:parse_config() name=%h-%d bluetoothd[19780]: src/main.c:parse_config() class=0x000100 bluetoothd[19780]: src/main.c:parse_config() discov_interval=30 bluetoothd[19780]: src/main.c:parse_config() Key file does not have key 'DeviceID' bluetoothd[19780]: Unable to get on D-Bus rigel:~# Second, it used to work before last upgrade, but unfortunately I cannot recall which vresion that was. So this is a regression. Third, hcitool and friends do not work either (the MAC is my phone which is on, BT on, and 50 cm from rigel):: rigel:~# hcitool dev Devices: rigel:~# rigel:~# sdptool browse 00:25:CF:B4:58:FA Failed to connect to SDP server on 00:25:CF:B4:58:FA: No route to host rigel:~# Fourth, the version in squeeze works fine. This is what its hcitool says: rigel:~# hcitool dev Devices: hci000:22:68:E9:A3:DD rigel:~# Cheers, Juha -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages bluez depends on: ii dbus 1.4.16-1 ii libbluetooth3 4.96-3 ii libc6 2.13-21 ii libcap-ng0 0.6.6-1 ii libdbus-1-31.4.16-1 ii libglib2.0-0 2.28.8-1 ii libreadline6 6.2-7 ii libudev0 172-1 ii libusb-0.1-4 2:0.1.12-19 ii lsb-base 3.2-28 ii module-init-tools 3.16-1 ii python-dbus0.84.0-2 ii python-gobject 2.28.6-5 ii udev 172-1 bluez recommends no packages. bluez suggests no packages. -- Configuration Files: /etc/bluetooth/rfcomm.conf changed [not included] /etc/dbus-1/system.d/bluetooth.conf [Errno 2] No such file or directory: u'/etc/dbus-1/system.d/bluetooth.conf' -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#586747: Status?
Hi! What is the status of this and 593433? Any ETA? We have since progressed to python 2.7 and according to the tags, this is already fixed upstream. -Juha -- --- | Juha Jäykkä, ju...@iki.fi | | http://www.maths.leeds.ac.uk/~juhaj | --- signature.asc Description: This is a digitally signed message part.
Bug#648239: [Pkg-urxvt-maintainers] Bug#648239: rxvt-unicode: cursor is lost when xcompmgr -n is running
Thanks for the bug report. Which video driver are you using? xserver-xorg-video-intel, version does not seem to make much difference: the same bug happens with at least 2:2.15.0-3, 2:2.16.0-1, and 2:2.16.901-1. Also, changing the colours of rxvt, either background or foreground, makes no difference. Cheers, Juha -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#648238: libakonadi-kde4: akonadi imap resource segfaults
Package: libakonadi-kde4 Version: 4:4.6.5-1 Severity: normal Dear Maintainer, Using kontact/addressbook, deleting some contacts and akonadi imap resource crashes. I start it again and in 5 minutes it crashes again. This keeps repeating. My addressbook is on a kolab server, which is set up in akonadi as a disconnected imap server with 5 minute automatic update interval (so I guess that is where the interval between the segfaults comes from). Backtrace (from drkonqi): Application: Akonadi Resource (akonadi_imap_resource), signal: Segmentation fault [Current thread is 1 (Thread 0x7fae1847c760 (LWP 30263))] Thread 2 (Thread 0x7fae04d3a700 (LWP 30265)): #0 0xff60012e in ?? () #1 0x7fffd6bff7e7 in ?? () #2 0x7fae12c8ce86 in *__GI_clock_gettime (clock_id=1, tp=0x7fae04d39b70) at ../sysdeps/unix/clock_gettime.c:116 #3 0x7fae178248b4 in ?? () from /usr/lib/libQtCore.so.4 #4 0x7fae178e64ad in ?? () from /usr/lib/libQtCore.so.4 #5 0x7fae178e67e3 in ?? () from /usr/lib/libQtCore.so.4 #6 0x7fae178e524c in ?? () from /usr/lib/libQtCore.so.4 #7 0x7fae178e52f5 in ?? () from /usr/lib/libQtCore.so.4 #8 0x7fae129de3b2 in g_main_context_prepare () from /lib/libglib-2.0.so.0 #9 0x7fae129df2ad in ?? () from /lib/libglib-2.0.so.0 #10 0x7fae129df949 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #11 0x7fae178e5d06 in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/libQtCore.so.4 #12 0x7fae178ba372 in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/libQtCore.so.4 #13 0x7fae178ba56f in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/libQtCore.so.4 #14 0x7fae177d220f in QThread::exec() () from /usr/lib/libQtCore.so.4 #15 0x7fae164f2e73 in ?? () from /usr/lib/libkimap.so.4 #16 0x7fae177d4c25 in ?? () from /usr/lib/libQtCore.so.4 #17 0x7fae13941b40 in start_thread (arg=optimized out) at pthread_create.c:304 #18 0x7fae1408836d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #19 0x in ?? () Thread 1 (Thread 0x7fae1847c760 (LWP 30263)): [KCrash Handler] #6 0x7fae14995fe4 in KJob::isAutoDelete() const () from /usr/lib/libkdecore.so.5 #7 0x7fae149962c8 in KJob::emitResult() () from /usr/lib/libkdecore.so.5 #8 0x7fae164dad6c in KIMAP::Job::handleErrorReplies(KIMAP::Message const) () from /usr/lib/libkimap.so.4 #9 0x7fae164eece2 in KIMAP::SelectJob::handleResponse(KIMAP::Message const) () from /usr/lib/libkimap.so.4 #10 0x7fae164f1188 in KIMAP::SessionPrivate::responseReceived(KIMAP::Message const) () from /usr/lib/libkimap.so.4 #11 0x7fae164f2252 in KIMAP::Session::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkimap.so.4 #12 0x7fae178d187a in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4 #13 0x7fae16c739f4 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #14 0x7fae16c78881 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #15 0x7fae14f8bb96 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #16 0x7fae178bb16c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4 #17 0x7fae178be528 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQtCore.so.4 #18 0x7fae178e5843 in ?? () from /usr/lib/libQtCore.so.4 #19 0x7fae129deedd in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #20 0x7fae129df6b8 in ?? () from /lib/libglib-2.0.so.0 #21 0x7fae129df949 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #22 0x7fae178e5c9f in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/libQtCore.so.4 #23 0x7fae16d17a4e in ?? () from /usr/lib/libQtGui.so.4 #24 0x7fae178ba372 in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/libQtCore.so.4 #25 0x7fae178ba56f in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/libQtCore.so.4 #26 0x7fae178be717 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4 #27 0x7fae17fbf276 in Akonadi::ResourceBase::init(Akonadi::ResourceBase*) () from /usr/lib/libakonadi-kde.so.4 #28 0x00430c06 in Akonadi::ResourceBase::initImapResource (argc=optimized out, argv=optimized out) at /usr/include/akonadi/resourcebase.h:188 #29 0x7fae13fd1ead in __libc_start_main (main=optimized out, argc=optimized out, ubp_av=optimized out, init=optimized out, fini=optimized out, rtld_fini=optimized out, stack_end=0x7fffd6aabe48) at libc-start.c:228 #30 0x00412365 in _start () -Juha -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-2-amd64 (SMP
Bug#648239: rxvt-unicode: cursor is lost when xcompmgr -n is running
Package: rxvt-unicode Version: 9.12-1 Severity: normal When I run xcompmgr -n and rxvt-unicode, the cursor becomes invisible whenever it is on at the end of a line (like when writing a command or this report with nano). It makes following where I am on the terminal quite hard. In underline-cursor -mode, this does not happen, only for block cursor. Other possibly relevant things: URxvt*Curses: on URxvt*CursorColor: Black URxvt*ReverseWrap: True URxvt*ScrollBar:True URxvt*ScrollLines: 5000 URxvt*background: LightCyan URxvt*charClass:33:48,37:48,45-47:48,38:48,64:48 URxvt*externalBorder: 0 URxvt*foreground: Black URxvt*geometry: 100x45 URxvt*internalBorder: 0 URxvt*translations: #override Shift KeyPress Up: scroll-back(1,line) \n Shift KeyPress Down: scroll-forw(1,line) URxvt*visualBell: True URxvt.font: xft:DejaVu Sans Mono:size=6.38:weight=medium:antialias=true:hintstyle=100:autohint=0,xft:unifont,xft:freemono:pixelsize=13,xft:Code2000:antialias=false URxvt.saveLines:5000 The reminal itself is NOT set to be transparent. Cheers, -Juha -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages rxvt-unicode depends on: ii base-passwd 3.5.23 ii libc6 2.13-21 ii libfontconfig1 2.8.0-3 ii libgcc1 1:4.6.2-4 ii libgdk-pixbuf2.0-0 2.24.0-1 ii libglib2.0-02.28.8-1 ii libperl5.12 5.12.4-6 ii libx11-62:1.4.4-2 ii libxft2 2.2.0-3 ii libxrender1 1:0.9.6-2 ii ncurses-base5.9-4 Versions of packages rxvt-unicode recommends: ii ttf-dejavu 2.33-2 ii ttf-sazanami-gothic 20040629-12 rxvt-unicode suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#575965: xserver-xorg-video-intel: Random complete freezes of whole system
If I can find the said versions of packages somewhere, I am willing to give the newest versions a try, but otherwise I will stick to a working system. I am sorry about that, but I need to get work done on the dpkg-repack / snapshot.debian.org may help? I have been running the latest sid versions for two weeks now, with no change to the previous situation. That is, it works as well as before, but some freezes of a short duration (less than 5 minutes) still happen sometimes. It is bearable, but obviously still somehow broken, so I suggest keeping this open but at lower priority, like minor. -Juha -- --- | Juha Jäykkä, ju...@iki.fi | | http://www.maths.leeds.ac.uk/~juhaj | --- signature.asc Description: This is a digitally signed message part.
Bug#575965: xserver-xorg-video-intel: Random complete freezes of whole system
Do you still get those freezes with linux 3.0 or 3.1, X 1.11 and intel 2.16, or has the behaviour changed again? Given the plethora of problems with newer intel kernel drivers that people have reported all over the net, I have refrained from upgrading those parts, but with the current versions (kernel 2.6.39-2, xserver-xorg-intel-video 2:2.15.0-3, libdrm2 2.4.26-1, libdrm-intel1 2.4.26-1, xserver-xorg-core 2:1.10.2-2) I have not had a single X-related crash yet. The ~15 second freezes remain, but that is much more tolerable than either of the earlier symptoms (crashes or up to 15 *minute* freezes). If I can find the said versions of packages somewhere, I am willing to give the newest versions a try, but otherwise I will stick to a working system. I am sorry about that, but I need to get work done on the laptop. Cheers, Juha -- --- | Juha Jäykkä, ju...@iki.fi | | http://www.maths.leeds.ac.uk/~juhaj | --- signature.asc Description: This is a digitally signed message part.
Bug#630839: critical
Please bump this to critical. This breaks authentication and username - uid and groupname - gid mappings on systems relying on sssd, making such unimportant things as LOGGING ON TO A SYSTEM IMPOSSIBLE which I think deserves *at* *least* critical and yes, I know, there is nothing worse than critical. I would be surprised if this would not lead to security holes under some situations, too. Cheers, Juha -- --- | Juha Jäykkä, ju...@iki.fi | | http://www.maths.leeds.ac.uk/~juhaj | --- signature.asc Description: This is a digitally signed message part.
Bug#630142: Regression: bug #594541 is back?
Package: php-kolab-filter Version: 0.1.9-4 Severity: grave Justification: renders package unusable Hi! It seems the following was forgotten from the fix of #594541: Deprecated: Assigning the return value of new by reference is deprecated in /usr/share/horde3/lib/Horde/Kolab/Server/Object.php on line 216 as I still get it after a fresh install. I am choosing the original severity for the original reason. Cheers, Juha P.S. Should I have (how?) reopened the old bug? -- System Information: Debian Release: 6.0 APT prefers oldstable APT policy: (500, 'oldstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-xen-amd64 (SMP w/1 CPU core) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages php-kolab-filter depends on: ii horde3 3.3.8+debian0-2 horde web application framework ii php-auth1.6.2-1 PHP PEAR modules for creating an a ii php-net-imap1:1.1.0-1Provides an implementation of the ii php-net-lmtp1.0.1-1 PHP PEAR module implementing LMTP ii php-pear5.3.3-7+squeeze1 PEAR - PHP Extension and Applicati ii php5-cli5.3.3-7+squeeze1 command-line interpreter for the p ii php5-imap 5.3.3-7+squeeze1 IMAP module for php5 php-kolab-filter recommends no packages. Versions of packages php-kolab-filter suggests: pn phpunit none (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#625832: python-mpi4py: importing MPI fails
Package: python-mpi4py Version: 1.2.2-2 Severity: grave Justification: renders package unusable I am not sure I am blaming the correct package here, but orterun -n 1 python -c 'import mpi4py.MPI' hangs and never returns. Regardless of how I start orted. This used to work about a month ago (my previous upgrade). It may be that the problem is in python or openmpi as well, since trying a previously compiled, private version on mpi4py does exactly the same thing. But I leave that to someone smarter to decide. Cheers, Juha -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.38-2-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages python-mpi4py depends on: ii libc6 2.13-2 Embedded GNU C Library: Shared lib ii libopenmpi1.3 1.4.3-2.1 high performance message passing l ii python2.6.6-14 interactive high-level object-orie ii python-support1.0.13 automated rebuilding support for P Versions of packages python-mpi4py recommends: ii mpi-default-bin 0.6Standard MPI runtime programs Versions of packages python-mpi4py suggests: ii python-numpy 1:1.4.1-5 Numerical Python adds a fast array -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#617907: libgl1-mesa-dri-experimental: random crashes with OpenGL apps
Or you may want to upgrade to the latest kernel in experimental first. This was easier, so I tried this. Some progress: instead of crashing X, it now crashes the GPU: [drm] nouveau :05:00.0: GPU lockup - switching to software fbcon and makes the machine completely unusable: open ssh connections freeze, new sessions cannot be opened (it will connect to the port, but will freeze before authentication begins, during host authentication I think), virtual consoles cannot be changed etc. The only things which work are: mpd keeps playing music intermittently (every time I press a key, I hear a very short bit of music), tcp connections are accepted, ICMP ECHO is replied to and magic SysRq key combinations work (so I can sync umount reboot). Note that this is 2.6.38rc7, which was the newest a short while ago. It just took me this long to figure out why the machine occassionally freezes. Well, it does not really freeze, but you get the point. I installed 2.6.38-2-amd64 now and will see what happens with it before building the experimental libgl1. I noticed there is a newer X, too: any point in checking if installing that helps? Oh, and one more point: this lockup seems to happen much less frequently if I do not run opengl apps full-screen but in a window (which might be full-screen size, though). Cheers, Juha -- --- | Juha Jäykkä, ju...@iki.fi | | http://www.maths.leeds.ac.uk/~juhaj | --- signature.asc Description: This is a digitally signed message part.
Bug#502062: /etc/init.d/keymap.sh never set UTF-8 locale charmap when /usr isn't mounted
Package: console-common Version: 0.7.85 Severity: normal What is the status of this bug? It still exists in 0.7.85 (squeeze and sid). -Juha -- System Information: Debian Release: 6.0 APT prefers stable APT policy: (1200, 'stable'), (995, 'stable'), (990, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.38-rc6-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages console-common depends on: ii console-data2:1.10-9 keymaps, fonts, charset maps, fall ii console-tools 1:0.2.3dbs-69.1 Linux console and font utilities ii debconf [debconf-2.0] 1.5.36.1 Debian configuration management sy ii debianutils 3.4 Miscellaneous utilities specific t ii lsb-base3.2-23.2squeeze1 Linux Standard Base 3.2 init scrip console-common recommends no packages. console-common suggests no packages. -- debconf information: console-data/keymap/powerpcadb: console-data/keymap/ignored: console-data/keymap/full: console-data/keymap/template/keymap: * console-data/keymap/policy: Don't touch keymap console-data/bootmap-md5sum: none console-data/keymap/template/layout: console-data/keymap/family: qwerty console-data/keymap/template/variant: -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#616481: iotop: crash on non-ascii characters
I'm unable to reproduce your bug using the following commands: I do iotop -b -d 5 --only, but I cannot think of any reason why it should make any difference. Do you remember how you ran iotop and what commands were running that had ä on their command-lines? I cannot think of any. I cannot think of any which would ever have it. But it keeps occurring, just had another some time ago. I am running iotop on the background to catch a nasty iowait problem I have, so I do not even notice immediately, when it fails. But it is always in the same position. -Juha -- --- | Juha Jäykkä, ju...@iki.fi | | http://www.maths.leeds.ac.uk/~juhaj | --- signature.asc Description: This is a digitally signed message part.
Bug#575965: xserver-xorg-video-intel: Random complete freezes of whole system
[9402544.148312] [drm:intel_crtc_cursor_set], [9402544.148316] [drm:intel_crtc_cursor_set], cursor off [9402550.044010] [drm:intel_gpu_idle_timer], idle timer fired, downclocking Yeah probably, mainly I'm wondering if there's some clue when the freeze does happen. These are the only things happening. I also had one - possibly unrelated - crash, forcing me to reboot. I then upgraded to whatever was in sid a week ago and now there has been some improvement: the freezes are now quite short, perhaps 15 seconds or so. On the other hand, that means I do not have enough time to attach a debugger to X from another machine! Also, my Xorg process now has 31M RSS, while before reboot it had 300M... Perhaps there was (is?) a memory leak somewhere? Cheers, Juha -- --- | Juha Jäykkä, ju...@iki.fi | | http://www.maths.leeds.ac.uk/~juhaj | --- signature.asc Description: This is a digitally signed message part.
Bug#616481: iotop: crash on non-ascii characters
Package: iotop Version: 0.4-2 Severity: important While I am not quite certain where iotop found a non-ascii character from, I am certain it should not do this when it does: Traceback (most recent call last): File /usr/bin/iotop, line 16, in module main() File /usr/lib/pymodules/python2.6/iotop/ui.py, line 547, in main main_loop() File /usr/lib/pymodules/python2.6/iotop/ui.py, line 537, in lambda main_loop = lambda: run_iotop(options) File /usr/lib/pymodules/python2.6/iotop/ui.py, line 450, in run_iotop return run_iotop_window(None, options) File /usr/lib/pymodules/python2.6/iotop/ui.py, line 446, in run_iotop_window ui.run() File /usr/lib/pymodules/python2.6/iotop/ui.py, line 126, in run self.process_list.duration) File /usr/lib/pymodules/python2.6/iotop/ui.py, line 405, in refresh_display print l UnicodeEncodeError: 'ascii' codec can't encode character u'\xe4' in position 138: ordinal not in range(128) The unicode character (LATIN SMALL LETTER A WITH DIAERESIS) in question is part of the Finnish alphabet, so it probably will occur every now and then on command lines. And even if it does not, iotop should be unicode clean. Cheers, -Juha -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.36-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages iotop depends on: ii python [python-ctypes] 2.6.6-3+squeeze5 interactive high-level object-orie ii python-support 1.0.11 automated rebuilding support for P iotop recommends no packages. iotop suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#575965: xserver-xorg-video-intel: Random complete freezes of whole system
Hi, what's the current status now, please? I cannot be sure: while there are still random lockups, but no more crashes for 116 days (thats the age of my current X process). So, I am not sure if the freezes are the same thing: at least I can ping the machine now during a freeze. On one hand, that sounds even more like an X bug than a possible kernel issue since only the VT where X runs is frozen. On the other hand, I cannot do C-A-F1 to change virtual terminals during a freeze either: is the kernel not supposed to be handling this, not X? So that would point to a kernel issue. What would be the smartest way to proceed? Close this and reopen the same bug against both kernel and X (since I cannot tell which one it is)? Cheers, -Juha -- --- | Juha Jäykkä, ju...@iki.fi | | http://www.maths.leeds.ac.uk/~juhaj | --- signature.asc Description: This is a digitally signed message part.
Bug#575965: xserver-xorg-video-intel: Random complete freezes of whole system
Sound like different issues then. If I understand correctly, the freezes that still happen resolve themselves after some time? Yes. Usually just shy of a minute, sometimes over five. Load has shot up to 50 during that time, so there is certainly some io wait involved. X is involved in the vt switch (when you press C-A-F1, X gets SIGUSR1, This was new to me. Perhaps I should try chvt, then? Do you get anything in the X or kernel log when these freezes happen? Nothing out of the ordinary, that's why it is so hard to figure out what happens. What if you set /sys/module/drm/parameters/debug to 6? If the machine Done. What am I expecting? I guess these are benign: [9402544.148312] [drm:intel_crtc_cursor_set], [9402544.148316] [drm:intel_crtc_cursor_set], cursor off [9402550.044010] [drm:intel_gpu_idle_timer], idle timer fired, downclocking is reachable over the network, can you connect over ssh and attach gdb to the X process to get a stack trace? I will try to. If it is a longer one, it will be no problem, but on a shorter one I will have to be quick. Cheers, -Juha -- --- | Juha Jäykkä, ju...@iki.fi | | http://www.maths.leeds.ac.uk/~juhaj | --- signature.asc Description: This is a digitally signed message part.
Bug#603955: kdebase-workspace-bin: powerdevil unable to set any power profile
Package: kdebase-workspace-bin Version: 4:4.4.5-4 Severity: important Since a while ago, powerdevil has not been able to do anything useful. It keeps sending notices about unplugged AC etc, but it no longer changes power profiles, locks screen, suspends, hibernates etc. It also shows empty as currentProfile in plasma engine explorer. The battery plasmoid cannot change this to anything and neither can direct dbus calls. In short, powerdevil is useless. -Juha -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.36-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages kdebase-workspace-bin depends on: ii kaboom 1.1.2The Debian KDE settings migration ii kdebase-runtime 4:4.4.5-1runtime components from the offici ii kdebase-workspace-d 4:4.4.5-4shared data files for the KDE Plas ii kdebase-workspace-k 4:4.4.5-4KDE greet libraries for authentica ii libc6 2.11.2-7 Embedded GNU C Library: Shared lib ii libfontconfig1 2.8.0-2.1generic font configuration library ii libfreetype62.4.2-2 FreeType 2 font engine, shared lib ii libgl1-mesa-glx [li 7.7.1-4 A free implementation of the OpenG ii libglib2.0-02.24.2-1 The GLib library of C routines ii libice6 2:1.0.6-2X11 Inter-Client Exchange library ii libkde3support4 4:4.4.5-1the KDE 3 Support Library for the ii libkdecore5 4:4.4.5-1the KDE Platform Core Library ii libkdeui5 4:4.4.5-1the KDE Platform User Interface Li ii libkephal4 4:4.4.5-4API for easier handling of multihe ii libkfile4 4:4.4.5-1the File Selection Dialog Library ii libkio5 4:4.4.5-1the Network-enabled File Managemen ii libknewstuff2-4 4:4.4.5-1the Get Hot New Stuff v2 Library ii libknewstuff3-4 4:4.4.5-1the Get Hot New Stuff v3 Library ii libknotifyconfig4 4:4.4.5-1library for configuring KDE Notifi ii libkparts4 4:4.4.5-1the Framework for the KDE Platform ii libkpty44:4.4.5-1the Pseudo Terminal Library for th ii libkscreensaver54:4.4.5-4library of the KDE Screensaver sys ii libkutils4 4:4.4.5-1various utility classes for the KD ii libkworkspace4 4:4.4.5-4library for the kdebase workspace ii libnepomuk4 4:4.4.5-1the Nepomuk Meta Data Library ii libnepomukquery4a 4:4.4.5-1the Nepomuk Query Library for the ii libntrack-qt4-1 008-1qt4 API for ntrack ii libpam0g1.1.1-6.1Pluggable Authentication Modules l ii libphonon4 4:4.6.0really4.4.2-1 the core library of the Phonon mul ii libplasma3 4:4.4.5-1the Plasma Library for the KDE Pla ii libplasmagenericshe 4:4.4.5-4shared elements for all the plasma ii libpng12-0 1.2.44-1 PNG library - runtime ii libprocesscore4a4:4.4.5-4library for ksysguard based proces ii libprocessui4a 4:4.4.5-4library for ksysguard process user ii libqimageblitz4 1:0.0.6-2QImageBlitz image effects library ii libqt4-dbus 4:4.6.3-4Qt 4 D-Bus module ii libqt4-network 4:4.6.3-4Qt 4 network module ii libqt4-qt3support 4:4.6.3-4Qt 3 compatibility library for Qt ii libqt4-script 4:4.6.3-4Qt 4 script module ii libqt4-sql 4:4.6.3-4Qt 4 SQL module ii libqt4-xml 4:4.6.3-4Qt 4 XML module ii libqtcore4 4:4.6.3-4Qt 4 core module ii libqtgui4 4:4.6.3-4Qt 4 GUI module ii libsm6 2:1.2.0-1X11 Session Management library ii libsolid4 4:4.4.5-1Solid Library for KDE Platform ii libsolidcontrol44:4.4.5-4library for Solid based network ma ii libsolidcontrolifac 4:4.4.5-4library for Solid based network in ii libsoprano4 2.5.0+dfsg.1-1 libraries for the Soprano RDF fram ii libstdc++6 4.4.5-8 The GNU Standard C++ Library v3 ii libstreamanalyzer0 0.7.2-1+b1 streamanalyzer library for Strigi ii libusb-0.1-42:0.1.12-16 userspace USB programming library ii libx11-62:1.3.3-3X11 client-side library ii libxau6 1:1.0.6-1X11 authorisation library ii libxcursor1 1:1.1.11-1 X cursor management library ii libxext6
Bug#603634: stalonetray: show hidden icons
Package: stalonetray Version: 0.8.0-1 Severity: wishlist Some systray icons, notably many KDE4 applications and nm-applet, hide their systray icons under some circumstances. KDE4's systray has a show hidden icons button, which forces these hidden icons visible. The same functionality would be nice to have in stalonetray: currently I need to start plasmoidviewer periodically to force these hidden icons to show up. -Juha -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.36-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages stalonetray depends on: ii libc6 2.11.2-6 Embedded GNU C Library: Shared lib ii libx11-6 2:1.3.3-3 X11 client-side library ii libxpm4 1:3.5.8-1 X11 pixmap library stalonetray recommends no packages. stalonetray suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#594046: libpetsc3.1: C++ version should live in -cxx-{debug, opt}, not -c-{debug, opt}
Can you let me know if what's in alioth git now works for you? Sorry I did not yet reply to your previous email, but I can test that if you tell me how: warning: remote HEAD refers to nonexistent ref, unable to checkout. =) As to the previous email: I think if upstream has figured out a way to support both C++ and C in the same libraries, I'd like to leave it as such, it's simpler for everyone that way. Right? That seems ok. -- --- | Juha Jäykkä, ju...@iki.fi | | http://www.maths.leeds.ac.uk/~juhaj | --- signature.asc Description: This is a digitally signed message part.
Bug#599644: sssd: unable to resolve ldap group memberships
Package: sssd Version: 1.2.1-4 Severity: important Sssd is unable to figure out memberships of groups stored in ldap. This is caused by incorrect pathname somewhere within sssd. Workaround: create a symlink. Example: ~# id foobar uid=1001(foobar) gid=1001(foobar) groups=1001(foobar) ~# /etc/init.d/sssd stop ~# rm -rf /var/lib/sss/db/* ~# ln -s /usr/lib /usr/modules ~#/etc/init.d/sssd start ~# id foobar uid=1001(foobar) gid=1001(foobar) groups=1001(foobar),7(specialgroup) ~# Without the symlink, the debug log of sssd will say (Sat Oct 9 21:09:07 2010) [sssd[nss]] [ldb] (6): unable to load memberof from /usr/modules/ldb/memberof.so: /usr/modules/ldb/memberof.so: cannot open shared object file: No such file or directory Cheers, Juha -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.36-rc5-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages sssd depends on: ii libc-ares21.7.3-1library for asyncronous name resol ii libc6 2.11.2-6 Embedded GNU C Library: Shared lib ii libcomerr21.41.12-2 common error description library ii libdbus-1-3 1.2.24-3 simple interprocess messaging syst ii libk5crypto3 1.8.3+dfsg-1 MIT Kerberos runtime libraries - C ii libkrb5-3 1.8.3+dfsg-1 MIT Kerberos runtime libraries ii libldap-2.4-2 2.4.23-6 OpenLDAP libraries ii libldb0 1:0.9.14~git20100928-1 LDAP-like embedded database - shar ii libnspr4-0d 4.8.6-1NetScape Portable Runtime Library ii libnss3-1d3.12.7-1 Network Security Service libraries ii libpam0g 1.1.1-6Pluggable Authentication Modules l ii libpcre3 8.02-1.1 Perl 5 Compatible Regular Expressi ii libpopt0 1.16-1 lib for parsing cmdline parameters ii libselinux1 2.0.96-1 SELinux runtime shared libraries ii libsemanage1 2.0.45-1 SELinux policy management library. ii libtalloc22.0.1-1hierarchical pool based memory all ii libtdb1 1.2.1-2+b1 Trivial Database - shared library ii libtevent00.9.9~git20100928-2talloc-based event loop library - ii python2.6.6-3interactive high-level object-orie ii python-sss1.2.1-4Pam module for the System Security Versions of packages sssd recommends: ii bind9-host 1:9.7.1.dfsg.P2-2 Version of 'host' bundled with BIN ii ldap-utils 2.4.23-6 OpenLDAP utilities Versions of packages sssd suggests: ii libnss-sss1.2.1-4Nss library for the System Securit ii libpam-sss1.2.1-4Pam module for the System Security -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#593461: python2.6: time.strftime gives incorrect timezone name
I can't reproduce this. which locale do you use, are the locales generated and installed? Well, ~ export|egrep 'LANG|LC' declare -x LANG=en_GB.UTF-8 declare -x LC_ALL=en_GB.UTF-8 # locale-gen Generating locales (this might take a while)... en_GB.UTF-8... done en_US.UTF-8... done fi_FI.UTF-8... done Generation complete. ~ python -c 'import time; print time.strftime(%Z, time.localtime()); print time.strftime(%Z)' GMT BST What else would there have to be? BTW, did I remember to tag this sid? This appears to work on lenny, or, alternatively, just GMT/BST is broken: all the lennies I tried this on are on EEST, while the sids are on BST. -Juha -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#596764: ttf-dejavu: dejavu fonts no longer accessible as core X fonts
Package: ttf-dejavu Version: 2.31-1 Severity: normal After the latest upgrade (which, I admit, was long overdue), the dejavu fonts are no longer available as core X fonts. xlsfonts does not see them, which is not a surprise since the necessary files are absent from /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType. I tried reinstalling all the relevant (to my knowledge) packages to force regenerating the missing files, but to no avail. The packages reinstalled were libttf2 fontconfig fontconfig-config '?name(dejavu)' x-ttcidfont-conf defoma. I guess this has something to do with defoma being phased out, but I would really like to have dejavu fonts still. Cheers, Juha -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.35-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages ttf-dejavu depends on: ii ttf-dejavu-core 2.31-1 Vera font family derivate with add ii ttf-dejavu-extra 2.31-1 Vera font family derivate with add ttf-dejavu recommends no packages. ttf-dejavu suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#596380: network-manager: fails to re-establish system connections after using physical RF KILL switch
Package: network-manager Version: 0.8.1-2+b1 Severity: normal Some laptops, like my Lenovo, have a physical RF kill switch. It is a nice feature on a plane etc, but network-manager cannot handle its use. If I switch off the wireless from the physical switch, and then back on, nm is sometimes unable to re-establish the (system) connection. It does not happen on each switch, but once it happens, it keeps on happening until nm is restarted. All I get is two lines in syslog: NetworkManager[24082]: info (wlan0): supplicant interface state: starting - ready NetworkManager[24082]: info (wlan0): device state change: 2 - 3 (reason 42) Restarting network-manager solves the problem, but that is ridiculous since the whole point of using nm in the first place is to remove the necessity to have root access to reconfigure networks. (This particular connection needs to be system connection, though.) Cheers, Juha -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.35-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages network-manager depends on: ii adduser 3.112 add and remove users and groups ii dbus 1.2.24-3 simple interprocess messaging syst ii isc-dhcp-client 4.1.1-P1-9 ISC DHCP client ii libc6 2.11.2-2 Embedded GNU C Library: Shared lib ii libdbus-1-3 1.2.24-3 simple interprocess messaging syst ii libdbus-glib-1-2 0.88-2 simple interprocess messaging syst ii libgcrypt11 1.4.5-2LGPL Crypto library - runtime libr ii libglib2.0-0 2.24.1-1 The GLib library of C routines ii libgnutls26 2.8.6-1the GNU TLS library - runtime libr ii libgudev-1.0-0161-1 GObject-based wrapper library for ii libnl11.1-5 library for dealing with netlink s ii libnm-glib2 0.8.1-2+b1 network management framework (GLib ii libnm-util1 0.8.1-2+b1 network management framework (shar ii libpolkit-gobject-1-0 0.96-2 PolicyKit Authorization API ii libuuid1 2.17.2-3.1 Universally Unique ID library ii lsb-base 3.2-23.1 Linux Standard Base 3.2 init scrip ii udev 161-1 /dev/ and hotplug management daemo ii wpasupplicant 0.6.10-2 client support for WPA and WPA2 (I Versions of packages network-manager recommends: ii dns 2.55-1 A small caching DNS proxy and DHCP ii ipt 1.4.9-1 administration tools for packet fi ii mod 0.4+git.20100624t180933.6e79d15-1+b1 D-Bus service for managing modems ii net 0.8.1-1 network management framework (GNOM ii net 1:0.9~svn1141976-1 KDE system tray applet for control ii pol 0.96-2 framework for managing administrat ii ppp 2.4.5-4 Point-to-Point Protocol (PPP) - da Versions of packages network-manager suggests: pn avahi-autoipd none (no description available) -- Configuration Files: /etc/NetworkManager/NetworkManager.conf changed: [main] plugins=ifupdown,keyfile [ifupdown] managed=true /etc/NetworkManager/dispatcher.d/01ifupdown changed: if [ -z $1 ]; then echo $0: called with no interface 12 exit 1; fi export IFACE=$1 export LOGICAL=$1 export ADDRFAM=NetworkManager export METHOD=NetworkManager export VERBOSITY=0 case $2 in up) export MODE=start export PHASE=post-up exec run-parts /etc/network/if-up.d ;; down) export MODE=stop export PHASE=pre-down exec run-parts /etc/network/if-down.d ;; pre-up) export MODE=start export PHASE=pre-up exec run-parts /etc/network/if-pre-up.d ;; post-down) export MODE=stop export PHASE=post-down exec run-parts /etc/network/if-post-down.d ;; vpn-up) echo 'VPN - Doing nothing' ;; *) echo $0: called with unknown action \`$2' 12 exit 1 ;; esac -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#595638: python-pyexiv2: please package version 0.2.2 (or fix the package in experimental)
Package: python-pyexiv2 Version: 0.2.2-1 Severity: minor Uninstallable due to missing dependency on libexiv2-6. Please repackage 0.2.2 for sid/squeeze or at least fix the experimental version (which is a rebuild only). -Juha -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.35-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages python-pyexiv2 depends on: ii libboost-python1.42.0 1.42.0-4 Boost.Python Library ii libc6 2.11.2-2 Embedded GNU C Library: Shared lib ii libexiv2-90.20-2 EXIF/IPTC metadata manipulation li ii libgcc1 1:4.4.4-11 GCC support library ii libstdc++64.4.4-11 The GNU Standard C++ Library v3 ii python2.6.5-13 interactive high-level object-orie ii python-support1.0.9 automated rebuilding support for P python-pyexiv2 recommends no packages. python-pyexiv2 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#594046: libpetsc3.1: C++ version should live in -cxx-{debug, opt}, not -c-{debug, opt}
Package: libpetsc3.1 Version: 3.1.dfsg-7 Severity: wishlist PETSc, when compiled with C++ as C-language, should be installed in $(PETSC_ARCH)-cxx-opt, not in $(PETSC_ARCH)-c-opt. This is required by various third party libraries that depend on PETSc, such as TAO. It should be ok to symlink c-opt to cxx-opt (or the other way around). I admit, this distinction between cxx and c versions of the library, where --with-c-support gives c-compatibility anyway, is strange to me. I have the third party libraries compiled with CC, but all my own code is C and compiled with cc anyway, so I am fairly certain there is no need for PETSc --with-c-language=C version at all, but perhaps some exotic environment requires that - I do not know. The best solution would be, I think, to have both cxx and c versions available, but then we would have the immediate problem of which version gets used if both are installed. Perhaps the alternatives-system can handle that and anyone wishing to use the non-default version would just set PETSC_DIR and PETSC_ARCH manually? Or is there a nicer solution? -Juha P.S. My apologies to Don Pellegrino, I should have remembered to mention the -with-c-support flag in #580546. I hope I do not mess you up again! =) -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.35-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libpetsc3.1 depends on: ii libamd2.2.0 1:3.4.0-2approximate minimum degree orderin ii libatlas3gf-base [libla 3.8.3-24 Automatically Tuned Linear Algebra ii libblas3gf [libblas.so. 1.2-7Basic Linear Algebra Reference imp ii libc6 2.11.2-2 Embedded GNU C Library: Shared lib ii libgcc1 1:4.4.4-9GCC support library ii libgfortran34.4.4-9 Runtime library for GNU Fortran ap ii libhdf5-openmpi-1.8.4 1.8.4-patch1-2 Hierarchical Data Format 5 (HDF5) ii libhypre-2.4.0 2.4.0b-7 High Performance Matrix Preconditi ii liblapack3gf [liblapack 3.2.2-1 library of linear algebra routines ii libopenmpi1.3 1.4.2-3 high performance message passing l ii libscotch-5.1 5.1.8a.dfsg-2programs and libraries for graph, ii libspooles2.2 2.2-8SPOOLES SParse Object Oriented Lin ii libstdc++6 4.4.4-9 The GNU Standard C++ Library v3 ii libumfpack5.4.0 1:3.4.0-2sparse LU factorization library ii libx11-62:1.3.3-3X11 client-side library ii openmpi-bin 1.4.2-3 high performance message passing l ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime libpetsc3.1 recommends no packages. libpetsc3.1 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#593461: python2.6: time.strftime gives incorrect timezone name
Package: python2.6 Version: 2.6.6~rc1-1 Severity: important Python docs say: time.strftime(format[, t]) Convert a tuple or struct_time representing a time as returned by gmtime() or localtime() to a string as specified by the format argument. If t is not provided, the current time as returned by localtime() is used. However, time.strftime(%Z, time.localtime()) 'GMT' time.strftime(%Z) 'BST' So, either the docs are buggy or the module is buggy. This is actually relatively annoying, since there seems to be no way of getting strftime to output the correct timezone name when it is given the time argument. It means that there is no way of correctly printing timezone names for any other date time except local now time. -Juha -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.35-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages python2.6 depends on: ii libbz2-1.01.0.5-4high-quality block-sorting file co ii libc6 2.11.2-2 Embedded GNU C Library: Shared lib ii libdb4.8 4.8.30-1 Berkeley v4.8 Database Libraries [ ii libncursesw5 5.7+20100313-2 shared libraries for terminal hand ii libreadline6 6.1-3 GNU readline and history libraries ii libsqlite3-0 3.7.0-1.1 SQLite 3 shared library ii mime-support 3.48-1 MIME files 'mime.types' 'mailcap ii python2.6-minimal 2.6.6~rc1-1A minimal subset of the Python lan python2.6 recommends no packages. Versions of packages python2.6 suggests: ii binutils 2.20.1-13 The GNU assembler, linker and bina ii python2.6-doc2.6.6~rc1-1 Documentation for the high-level o pn python2.6-profiler none (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#585663: xorg: i915 and DRI leak memory
Can you attach your X and kernel logs, and track the contents of /sys/kernel/debug/dri/0/gem_objects (you can mount debugfs with 'mount -t debugfs none /sys/kernel/debug)? Sorry, I cannot: ever since 2:2.11.0-1, the problem either went away or is at least a LOT less severe. I now have 41 days old X process, and the unreclaimable kernel memory is 244584 kB, where it previously rose to a gigabyte in less than 14 days. The file /sys/kernel/debug/dri/0/gem_objects is 0 bytes long, how do I track its contents? Does this also happen with debian's 2.6.32 kernel? It happens with everything Debian (including experimental) has had since 2.6.31. Only the .35 kernels I have not tested (because the problem seems to have gone away before they came available). Cheers, Juha -- --- | Juha Jäykkä, ju...@iki.fi | | http://www.maths.leeds.ac.uk/~juhaj | --- signature.asc Description: This is a digitally signed message part.
Bug#582953: kmail deleted all non-local incoming mail settings on upgrade
On Monday 05 Jul 2010 12:26:42 Modestas Vainius wrote: Hello, btw, is your $HOME on ext4 or XFS? XFS -- --- | Juha Jäykkä, ju...@iki.fi | | http://www.maths.leeds.ac.uk/~juhaj | --- signature.asc Description: This is a digitally signed message part.
Bug#586747: python2.6-doc: please provide info documentation again
Package: python2.6-doc Version: 2.6.5+20100616-1 Severity: wishlist Up to python2.5-doc, the package contained documentation in info format. Browsing info pages is vastly easier and faster than html, so I would kindly request that documentation in info format be reinstated. Thank you. -Juha -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.34 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages python2.6-doc depends on: ii libjs-jquery 1.4.2-2JavaScript library for dynamic web python2.6-doc recommends no packages. Versions of packages python2.6-doc suggests: ii python2.6 2.6.5+20100616-1 An interactive high-level object-o -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#585663: xorg: i915 and DRI leak memory
Package: xorg Version: 1:7.5+6 Severity: important X with xserver-xorg-video-intel is no longer usable: is causes memory corruption which can only be solved by restarting X every week or so. A little bit of googling suggests this is related to DRI corrupting kernel memory, so I am not sure if this is kernel or X bug, please retarget as necessary. Symptoms: SUnreclaim slab increases by about 1 MB per minute, yielding about 1 GB of SUnreclaim within two weeks. This can be slowed down by not doing anything or speeded up by opening windows, moving them around, causing a program to draw stuff on screen etc. Basically any use of X increases the rate of memory corruption while just letting it idle (without a screensaver!) slows it down. Of course, slowing memory corruption speed down by doing nothing is not quite acceptable - if I did no want to do anything with X, I would not start X in the first place. Curiously, setting DRI and DRI2 to False and NoAccel to True do not seem to disable direct rendering: glxinfo still says; direct rendering: Yes. What else do I need to turn off to make X usable again? Here are the values of the relevant parts on /proc/meminfo right after logging off X but not yet shutting down kdm (i.e. X is still running) and immediately after shutting down kdm (and therefore X, too): Before: MemFree: 390412 kB Buffers: 0 kB Cached: 442828 kB SwapCached:52508 kB Active: 182880 kB Inactive: 405552 kB Active(anon): 88712 kB Inactive(anon): 110184 kB Active(file): 94168 kB Inactive(file): 295368 kB AnonPages:101876 kB Mapped:30536 kB Slab: 976616 kB SReclaimable: 23784 kB SUnreclaim: 952832 kB After: MemFree: 1460024 kB Buffers: 0 kB Cached: 395244 kB SwapCached:41652 kB Active: 106172 kB Inactive: 344176 kB Active(anon): 11348 kB Inactive(anon):49228 kB Active(file): 94824 kB Inactive(file): 294948 kB AnonPages: 21496 kB Mapped:11620 kB Slab: 47056 kB SReclaimable: 23716 kB SUnreclaim:23340 kB The culprit is kmalloc-32 according to slabinfo. Unfortunately I forgot to save its output. Its size was about 940MB anyway. I will be happy to provide more info as soon as the slab grows again in a few days. :/ -Juha P.S. I realise my xserver-xorg-video-intel is from experimental, but the older versions have been even less usable: mostly crashing or completely freezing at random (see #575965 for example). -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.34 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages xorg depends on: ii konsole [x-terminal-emulator] 4:4.4.3-1 X terminal emulator for KDE 4 ii libgl1-mesa-dri 7.7.1-2A free implementation of the OpenG ii libgl1-mesa-glx [libgl1] 7.7.1-2A free implementation of the OpenG ii libglu1-mesa 7.7.1-2The OpenGL utility library (GLU) ii lxterminal [x-terminal-emulat 0.1.7-1desktop independent vte-based term ii rxvt-unicode [x-terminal-emul 9.07-2 RXVT-like terminal emulator with U ii x11-apps 7.5+5 X applications ii x11-session-utils 7.5+1 X session utilities ii x11-utils 7.5+3 X11 utilities ii x11-xfs-utils 7.4+1 X font server utilities ii x11-xkb-utils 7.5+2 X11 XKB utilities ii x11-xserver-utils 7.5+1 X server utilities ii xauth 1:1.0.4-1 X authentication utility ii xfonts-100dpi 1:1.0.1100 dpi fonts for X ii xfonts-75dpi 1:1.0.175 dpi fonts for X ii xfonts-base 1:1.0.1standard fonts for X ii xfonts-scalable 1:1.0.1-1 scalable fonts for X ii xfonts-utils 1:7.5+2X Window System font utility progr ii xinit 1.2.0-1X server initialisation tool ii xkb-data 1.8-1 X Keyboard Extension (XKB) configu ii xorg-docs-core1:1.5-1Core documentation for the X.org X ii xserver-xorg 1:7.5+6the X.Org X server ii xterm [x-terminal-emulator] 258-1 X terminal emulator xorg recommends no packages. Versions of packages xorg suggests: ii xorg-docs 1:1.5-1Miscellaneous documentation for th -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#582953: kmail deleted all non-local incoming mail settings on upgrade
I suspect you had file system problems and kmail configs got eaten in the process ( ~/.kde/share/config/kmail* ). There might even be some leftovers with odd names ~/.kde/share/config/kmailrc*.new etc. Try recovering from them. The mail should still be there in ~/Mail or somewhere in ~/.kde/share/apps/kmail/ File system was clean both before and after. As to the configs getting eaten, yes, they did vanish. Likewise, ~/.kde/share/apps/kmail/ was empty apart from some directories after the upgrade. No files were present. Thus no mail. Unless you give more proof that it's really a problem with kmail, the next Quite impossible since the upgrade is done. nothing to do with it. However, if you upgrade with kmail/KDE running, sometimes odd things happen. What do you mean KDE running? I did not have kmail, but I did have kded and several other KDE-related processes running, but I never run KDE because it forces me to logout for upgrades; by running just openbox the only userspace program upgrades I need to log off for are X and openbox. If the deletion of data is due to odd things happening when upgrading while kde-related processes are running, this is a bug: very many people use graphical apt-front-ends to upgrade their machines and it simply must work. A logoff or reboot may be required, yes, but under no circumstances must user data be deleted without explicit permission. What was the upgrade doing inside $HOME anyway? Packages should not touch anything in $HOME. That said, there was that odd set of error messages at first start of kmail after the upgrade, so perhaps the package did not touch $HOME, but kmail itself, for some reason, deleted all its mail settings and data at first restart. I suggest you go though the kmail code to see where it does unlink() on its mail during startup and under what conditions that happens. Clearly, the only condition when that should happen is when the user explicitly asks kmail to delete messages. -Juha -- --- | Juha Jäykkä, ju...@iki.fi | | http://www.maths.leeds.ac.uk/~juhaj | --- signature.asc Description: This is a digitally signed message part.
Bug#582953: kmail deleted all non-local incoming mail settings on upgrade
Package: kmail Version: 4:4.4.3-1 Severity: critical Tags: squeeze sid Justification: causes serious data loss Kmail is running with dimap, imap, imap and pop3 accounts. All is well. I run aptitude safe-upgrade. Upon next login and start of kmail, all the said accounts are gone from the settings. During this startup of kmail (and the corresponding startup of akonadi), there were numerous messages about unreadable mail folders. These happened to be folders of the dimap account, but I suspect that is simply coincidence: kmail listed the folders first and someone destroyed them before kmail actually accessed them. This makes me wonder if akonadi is the real culprit here, after all, but I have no way of finding out. The safe-upgrade did not update kmail, but it did update akonadi-server. Critical: data loss: if pop3 account emails are on local disc instead of the server, those messages are lost. -Juha -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.34 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages kmail depends on: ii kdebase-runtime 4:4.4.3-1runtime components from the offici ii kdepim-runtime 4:4.4.3-1Runtime components for akonadi-kde ii kdepimlibs-kio-plug 4:4.4.3-1kio slaves used by KDE PIM applica ii libakonadi-contact4 4:4.4.3-1library for using the Akonadi PIM ii libakonadi-kde4 4:4.4.3-1library for using the Akonadi PIM ii libc6 2.10.2-9 Embedded GNU C Library: Shared lib ii libgcc1 1:4.4.4-2GCC support library ii libgpgme++2 4:4.4.3-1c++ wrapper library for gpgme ii libkabc44:4.4.3-1library for handling address book ii libkcal44:4.4.3-1library for handling calendar data ii libkde3support4 4:4.4.3-2the KDE 3 Support Library for the ii libkdecore5 4:4.4.3-2the KDE Platform Core Library ii libkdepim4 4:4.4.3-1KDE PIM library ii libkdeui5 4:4.4.3-2the KDE Platform User Interface Li ii libkhtml5 4:4.4.3-2the KHTML Web Content Rendering En ii libkimap4 4:4.4.3-1library for handling IMAP data ii libkio5 4:4.4.3-2the Network-enabled File Managemen ii libkldap4 4:4.4.3-1library for accessing LDAP ii libkleo44:4.4.3-1certificate based crypto library f ii libkmime4 4:4.4.3-1library for handling MIME data ii libknotifyconfig4 4:4.4.3-2library for configuring KDE Notifi ii libkontactinterface 4:4.4.3-1Kontact interface library ii libkparts4 4:4.4.3-2the Framework for the KDE Platform ii libkpgp44:4.4.3-1gpg based crypto library for KDE ii libkpimidentities4 4:4.4.3-1library for managing user identiti ii libkpimtextedit44:4.4.3-1library that provides a textedit w ii libkpimutils4 4:4.4.3-1library for dealing with email add ii libkresources4 4:4.4.3-1the KDE Resource framework library ii libksieve4 4:4.4.3-1KDE mail/news message filtering li ii libktnef4 4:4.4.3-1library for handling TNEF data ii libkutils4 4:4.4.3-2various utility classes for the KD ii libmailtransport4 4:4.4.3-1mail transport service library ii libmessagecore4 4:4.4.3-1message core library for KDE ii libmessagelist4 4:4.4.3-1message list library for KDE ii libmimelib4 4:4.4.3-1KDE MIME library ii libnepomuk4 4:4.4.3-2the Nepomuk Meta Data Library ii libphonon4 4:4.6.0really4.4.1-2 the core library of the Phonon mul ii libqt4-dbus 4:4.6.2-5Qt 4 D-Bus module ii libqt4-network 4:4.6.2-5Qt 4 network module ii libqt4-qt3support 4:4.6.2-5Qt 3 compatibility library for Qt ii libqt4-xml 4:4.6.2-5Qt 4 XML module ii libqtcore4 4:4.6.2-5Qt 4 core module ii libqtgui4 4:4.6.2-5Qt 4 GUI module ii libstdc++6 4.4.4-2 The GNU Standard C++ Library v3 ii libthreadweaver44:4.4.3-2the ThreadWeaver Library for the K ii perl5.10.1-12Larry Wall's Practical Extraction ii phonon 4:4.6.0really4.4.1-2 metapackage for the Phonon multime kmail recommends no packages. Versions of packages kmail suggests: pn clamav | f-prot-installer none (no description available) ii
Bug#575965: xserver-xorg-video-intel: Random complete freezes of whole system
On Wed, Mar 31, 2010 at 01:29:50 +0100, Juha Jäykkä wrote: I will wait for the next freeze: that and the new kernel are waiting. Should not take long. =( Got the experimental versions now: libdrm2: Installed: 2.4.18-3 libdrm-intel1: Installed: 2.4.18-3 linux-image-2.6.33-2-amd64: Installed: 2.6.33-1~experimental.4 xserver-xorg-video-intel: Installed: 2:2.10.903-1 And have not seen a single freeze yet, but I have not had complete ~5 min long freezes quite a few times. The symptoms look like https://bugzilla.kernel.org/show_bug.cgi?id=14933 or https://bugzilla.kernel.org/show_bug.cgi?id=14141, which should both be fixed now. The downside is that the freezes do not leave any traces in any logs, so I have absolutely no idea why they occur. =( The above mentioned bugs did. But no more crashes and no more complete freezes either, so hopes are high. -Juha -- --- | Juha Jäykkä, ju...@iki.fi | | http://www.maths.leeds.ac.uk/~juhaj | --- signature.asc Description: This is a digitally signed message part.
