Bug#954762: systraq: Annoying as Hell
Package: systraq Version: 20160803-3 Severity: critical Tags: security Justification: breaks unrelated software Dear Maintainer, You annoyed me with your jackass hourly cron job (once a day is sufficient) Now I'm annoying you. Enjoy Jackass Solution: uninstall Debian, go with a distro that doesn't use jackasses instead of developers. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages systraq depends on: ii adduser3.118 ii bsd-mailx 8.1.2-0.20180807cvs-1+b1 ii debsums2.2.5 ii exim4 4.93-12 ii exim4-daemon-light [mail-transport-agent] 4.93-12 ii filetraq 0.3 ii make 4.2.1-1.2 ii net-tools 1.60+git20180626.aebd88e-1 ii procps 2:3.3.16-4 systraq recommends no packages. systraq suggests no packages. -- no debconf information
Bug#954432: geophar: Fails to start
Package: geophar Version: 18.08.6+dfsg1-1 Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? Wanting to see if Geophar is useful to me. * What exactly did you do (or not do) that was effective (or ineffective)? I installed Geophar with its default dependencies from the package repository. After installing, I issued the following command in a terminal: geophar * What was the outcome of this action? After issuing the command in a terminal, the following lines were printed and the program exited: QSettings::value: Empty key passed QSettings::value: Empty key passed malloc(): unsorted double linked list corrupted Aborted * What outcome did you expect instead? The program to start and run. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages geophar depends on: ii jsmath 3.6e-2 ii python3 3.7.5-3 ii python3-kiwisolver 1.0.1-3 ii python3-matplotlib 3.1.2-2 ii python3-numpy1:1.17.4-5 ii python3-pep8 1.7.1-9 ii python3-pyqt55.14.1+dfsg-3 ii python3-pyqt5.qsci 2.11.2+dfsg-6 ii python3-pyqt5.qtsvg 5.14.1+dfsg-3 ii python3-scipy1.3.3-3 ii python3-stemmer 1.3.0+dfsg-2+b1 ii python3-sympy1.5.1-2.1 ii python3.73.7.7-1 Versions of packages geophar recommends: ii jsmath-fonts 1.3-3.1 ii libjs-mathjax 2.7.4+dfsg-1 Versions of packages geophar suggests: ii apache2 [httpd] 2.4.41-5 -- no debconf information
Bug#873370: kmenuedit: All versions in repositories are extremely out of date.
Package: kmenuedit Version: 4:5.8.4-1 Severity: grave Justification: renders package unusable Dear Maintainer, The out of date kmenuedit saves configuration files in the wrong directories, causing most menu edits to be lost. The newest version in repositories is 4.8.5. The newest version available from upstream is 5.10.5. The version of kmenuedit in the repositories does not work with the version of plasma that is available in the repositories. The recommended solution is to package a more up-to-date version for Debian and submit it. -- System Information: Debian Release: 9.1 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages kmenuedit depends on: ii kio 5.28.0-2 ii libc6 2.24-11+deb9u1 ii libkf5completion5 5.28.0-1 ii libkf5configcore5 5.28.0-2 ii libkf5configgui55.28.0-2 ii libkf5configwidgets55.28.0-2 ii libkf5coreaddons5 5.28.0-2 ii libkf5dbusaddons5 5.28.0-1 ii libkf5i18n5 5.28.0-2 ii libkf5iconthemes5 5.28.0-2 ii libkf5kdelibs4support5 5.28.0-1 ii libkf5kiowidgets5 5.28.0-2 ii libkf5service-bin 5.28.0-1 ii libkf5service5 5.28.0-1 ii libkf5sonnetcore5 5.28.0-2 ii libkf5sonnetui5 5.28.0-2 ii libkf5widgetsaddons55.28.0-3 ii libkf5xmlgui5 5.28.0-1 ii libqt5core5a5.7.1+dfsg-3+b1 ii libqt5dbus5 5.7.1+dfsg-3+b1 ii libqt5gui5 5.7.1+dfsg-3+b1 ii libqt5widgets5 5.7.1+dfsg-3+b1 ii libqt5xml5 5.7.1+dfsg-3+b1 ii libstdc++6 6.3.0-18 Versions of packages kmenuedit recommends: ii khotkeys 4:5.8.6-1 kmenuedit suggests no packages. -- no debconf information
Bug#870104: kio_http_cache_cleaner runs indefinitely after logging out of KDE
Package: kio Version: 5.28.0-2 Severity: normal Dear Maintainer, 2nd or 3rd graphical logins to Plasma Desktop by various users sometimes hang in diverse and weird ways. Upon investigation, many processes were found to still be running after users log out. Further investigating, kio_http_cache_cleaner seems to be consistently running after a log out, causing other processes to not quit on logout. Killing this process would end the other processes that had remained running, and the weird hangs never seem to happen if this process is killed after logging out. I would submit a patch, but I am not sure of how sddm controls the logout to ensure processes are terminated appropriately. -- System Information: Debian Release: 9.1 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages kio depends on: ii libacl1 2.2.52-3+b1 ii libc6 2.24-11+deb9u1 ii libgcc1 1:6.3.0-18 ii libgssapi-krb5-2 1.15-1 ii libkf5archive55.28.0-2 ii libkf5codecs5 5.28.0-1+b2 ii libkf5completion5 5.28.0-1 ii libkf5configcore5 5.28.0-2 ii libkf5configwidgets5 5.28.0-2 ii libkf5coreaddons5 5.28.0-2 ii libkf5dbusaddons5 5.28.0-1 ii libkf5i18n5 5.28.0-2 ii libkf5itemviews5 5.28.0-1 ii libkf5kiocore55.28.0-2 ii libkf5kiontlm55.28.0-2 ii libkf5kiowidgets5 5.28.0-2 ii libkf5notifications5 5.28.0-1 ii libkf5service-bin 5.28.0-1 ii libkf5service55.28.0-1 ii libkf5solid5 5.28.0-3 ii libkf5textwidgets55.28.0-1 ii libkf5wallet-bin 5.28.0-3 ii libkf5wallet5 5.28.0-3 ii libkf5widgetsaddons5 5.28.0-3 ii libkf5windowsystem5 5.28.0-2 ii libqt5core5a 5.7.1+dfsg-3+b1 ii libqt5dbus5 5.7.1+dfsg-3+b1 ii libqt5gui55.7.1+dfsg-3+b1 ii libqt5network55.7.1+dfsg-3+b1 ii libqt5script5 5.7.1~20161021+dfsg-2 ii libqt5widgets55.7.1+dfsg-3+b1 ii libqt5x11extras5 5.7.1~20161021-2 ii libqt5xml55.7.1+dfsg-3+b1 ii libstdc++66.3.0-18 ii libxml2 2.9.4+dfsg1-2.2 ii libxslt1.11.1.29-2.1 kio recommends no packages. kio suggests no packages. -- no debconf information
Bug#719461: Thanks
:D -- V. Brice Hunt Random quotation: Have you seen the latest Japanese camera? Apparently it is so fast it can photograph an American with his mouth shut! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#659832: Quick and dirty workaround using sudo
Until this bug can be fixed, I am using the following quick and dirty bash script to work around the issue. Note, this quick and dirty work around really is quick and dirty and may have security problems or other issues. The way it is written requires sudo, but if you don't mind entering passwords multiple times, it could be used with su -c instead of the first sudo and eliminate the second sudo in front of the su. I put this script in ~/bin/ as I'm the only one on my computer that ever needs to be root. I use this script in conjunction with a custom Konsole profile for whenever I need a root command line. This script, as written, gets your xauth magic cookie, asks for your user password once to add the magic cookie to root's xauth file, then immediately reuses the sudo authorization to start a root command line. ~/bin/mysux #!/bin/bash cookie=`xauth list $DISPLAY` sudo xauth add $cookie sudo su - -- BH Randomly selected fortune cookie: Rules for driving in New York: (1) Anything done while honking your horn is legal. (2) You may park anywhere if you turn your four-way flashers on. (3) A red light means the next six cars may go through the intersection. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671405: [laptop-mode-tools] usb-autosuspend enabled for all devices by default
Package: laptop-mode-tools Version: 1.60-1 Severity: normal --- Please enter the report below this line. --- By default, /etc/laptop-mode/conf.d/usb-autosuspend.conf enables laptop-mode- tools to turn the power off for many (all?) usb devices after three seconds of non-use when AC is unplugged. This behavior is unwelcome and causes problems the first time it happens. I do not have a single USB device that I want powered down while actively using my computer, even in power saving mode. My wired USB mouse, my bluetooth radio that I use to connect to my car's computer, various cameras, my laptop cooler, and my various usb mass storage devices all become annoying to use when the USB power is shut off after only a few seconds. If I am not using them, I typically will unplug them from the USB port just because I cannot have everything plugged simultaneously into my laptop. The fix for this bug is easy. It involves either disabling usb-autosuspend (set CONTROL_USB_AUTOSUSPEND=0 in /etc/laptop-mode/conf.d/usb-autosuspend.conf). Alternatively, you can set AUTOSUSPEND_USE_WHITELIST=1 and then whitelist the usb devices that you can be autosuspended with AUTOSUSPEND_USBID_WHITELIST= and AUTOSUSPEND_USBTYPE_WHITELIST= in the same file as above. You can use lsusb when the device is plugged in to determine its type and/or USB ID. I consider either of these solutions preferrable to blacklisting because most USB devices are designed to be used while they are plugged in and many of them have their own power-down routines and stop drawing power when they're not being used. --- System information. --- Architecture: amd64 Kernel: Linux 3.2.0-2-amd64 Debian Release: wheezy/sid 500 testing www.debian-multimedia.org 500 testing security.debian.org 500 testing ftp.us.debian.org --- Package information. --- Depends (Version) | Installed ==-+- lsb-base (= 3.0-10) | 4.1+Debian0 util-linux (= 2.13) | 2.20.1-4 psmisc | 22.16-1 Recommends (Version) | Installed =-+-=== hdparm| 9.39-1 sdparm| ethtool | 1:3.1-1 net-tools | 1.60-24.1 wireless-tools| 30~pre9-8 udev | 175-3.1 Suggests(Version) | Installed =-+-=== acpid | 1:2.0.16-1 OR apmd | 3.2.2-14 OR pbbuttonsd| OR pmud | hal | -- BH Randomly selected fortune cookie: Where do I find the time for not reading so many books? -- Karl Kraus -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
