Bug#922113: pulseaudio-module-zeroconf: module-zeroconf-discover not listed, update the package description
Package: pulseaudio-module-zeroconf Version: 12.2-3 Severity: minor Dear Maintainer, the package description says: " This module enables PulseAudio to publish available sinks and sources via zeroconf (aka. Avahi, mdns). The module is called module-zeroconf-publish. " while the package itself also contains module-zeroconf-discover, required for finding PA sources and sinks in the network. Please update the description so that it includes the discover module, e.g.: " This package enables PulseAudio to publish and discover available sinks and sources via zeroconf (aka. Avahi, mdns). The PulseAudio modules are called module-zeroconf-publish and module-zeroconf-discover. " Checking the contents of the package reveals that both modules are there: $ dpkg -L pulseaudio-module-zeroconf /. /usr /usr/lib /usr/lib/pulse-12.2 /usr/lib/pulse-12.2/modules /usr/lib/pulse-12.2/modules/libavahi-wrap.so /usr/lib/pulse-12.2/modules/module-zeroconf-discover.so /usr/lib/pulse-12.2/modules/module-zeroconf-publish.so /usr/share /usr/share/doc /usr/share/doc/pulseaudio-module-zeroconf /usr/share/doc/pulseaudio-module-zeroconf/NEWS.Debian.gz /usr/share/doc/pulseaudio-module-zeroconf/NEWS.gz /usr/share/doc/pulseaudio-module-zeroconf/README /usr/share/doc/pulseaudio-module-zeroconf/changelog.Debian.gz /usr/share/doc/pulseaudio-module-zeroconf/copyright -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (900, 'testing'), (600, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-2-amd64 (SMP w/2 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), LANGUAGE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages pulseaudio-module-zeroconf depends on: ii avahi-daemon 0.7-4+b1 ii libavahi-client3 0.7-4+b1 ii libavahi-common3 0.7-4+b1 ii libc6 2.28-6 ii libcap2 1:2.25-2 ii libdbus-1-3 1.12.12-1 ii libpulse0 12.2-3 ii pulseaudio12.2-3 pulseaudio-module-zeroconf recommends no packages. pulseaudio-module-zeroconf suggests no packages. -- no debconf information
Bug#916590: telegram-desktop: [pulseaudio] cannot change the telegram-desktop audio output device in pavucontrol
Package: telegram-desktop Version: 1.4.0-1+b1 Severity: normal Whenever telegram-desktop is playing sound (e.g. audio file, voice message) and I try to redirect it to a non-default audio device using pavucontrol, a default device stays selected. Doesn't seem to be a problem with pulseaudio / pavucontrol, as selection works for other applications (tested with Firefox and Deadbeef). Might be related with #905822 but not sure. Using pulseaudio 12.2-2 and pavucontrol 3.0-4 Reproduction: 1. have a system with more than one audio device for playback (e.g. built-in soundcard and a USB soundcard) 2. open pavucontrol and go to the playback tab 3. open telegram and make it play sound (e.g. play an audio file or voice message) 4. try to change the output device for telegram expected: a different device is chosen and audio is played using it observed: no change, telegram still uses the default device -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (900, 'testing'), (600, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), LANGUAGE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages telegram-desktop depends on: ii libavcodec58 10:4.1-dmo3 ii libavformat58 10:4.1-dmo3 ii libavutil56 10:4.1-dmo3 ii libc6 2.28-2 ii libgcc1 1:8.2.0-9 ii libglib2.0-0 2.58.1-2 ii liblzma5 5.2.2-1.3 ii libminizip1 1.1-8+b1 ii libopenal11:1.19.1-1 ii libopus0 1.3~beta+20180518-1 ii libqt5core5a [qtbase-abi-5-11-2] 5.11.2+dfsg-7 ii libqt5dbus5 5.11.2+dfsg-7 ii libqt5gui55.11.2+dfsg-7 ii libqt5network55.11.2+dfsg-7 ii libqt5widgets55.11.2+dfsg-7 ii libssl1.1 1.1.1a-1 ii libstdc++68.2.0-9 ii libswresample310:4.1-dmo3 ii libswscale5 10:4.1-dmo3 ii libx11-6 2:1.6.7-1 ii libxxhash00.6.5-2 ii qt5-image-formats-plugins 5.11.2-2 ii zlib1g1:1.2.11.dfsg-1 Versions of packages telegram-desktop recommends: ii fonts-open-sans 1.11-1 telegram-desktop suggests no packages. -- no debconf information
Bug#884352: virtualenvwrapper: Python interpreter inside virtualenv breaks after system python upgrade
Package: virtualenvwrapper Version: 4.3.1-2 Severity: important Dear Maintainer, after upgrading system-wide Python installation (in my case from 3.5.3 to 3.5.4), virtualenvs may break due to the outdated interpreter (somevirtualenv/bin/python3) inside the venv, trying to work with a newer stdlib. The problem is that mkvirtualenv copies rather than symlinks the python interpreter binary, but symlinks the modules from standard library (e.g. /usr/lib/python3.5). Whenever python3.5 is updated in the system (e.g. via apt), the virtualenv is pointed at newer library (i.e. 3.5.4), but still uses the old interpreter (3.5.3), breaking compatibility. Reproduction: 1. install python3.5 = 3.5.3 2. make some virtualenv using /usr/bin/python3.5 ($ mkvirtualenv -p /usr/bin/python3.5 somevirtualenv) 3. upgrade python3.5 to 3.5.4 4. enter the virtualenv ($ workon somevirtualenv) 5. open python3 ($ python3) 6. try importing an incompatible module (>>> import ctypes) Import threw exception: ImportError: /home/elegant/virtualenvs/rpi2casterd/lib/python3.5/lib-dynload/_ctypes.cpython-35m-x86_64-linux-gnu.so: undefined symbol: _PyUnicode_AsWideCharString Breaks anything that depends on it as well, making the virtualenv unusable until it's fixed. Workaround: 1. $ cd $WORKON_HOME/somevirtualenv/bin 2. $ mv python3 python3_old (put the old interpreter out of the way) 3. $ ln -s /usr/bin/python3.5 python3 (symlink the newer python3.5 from system) 4. $ workon somevirtualenv 5. $ python3 >>> import ctypes (everything OK) -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (900, 'testing'), (600, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 4.13.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), LANGUAGE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages virtualenvwrapper depends on: ii libjs-sphinxdoc1.6.5-2 ii python 2.7.14-3 ii python-stevedore 1.25.0-2 ii python-virtualenv 15.1.0+ds-1 ii virtualenv 15.1.0+ds-1 ii virtualenv-clone 0.2.5-1 Versions of packages virtualenvwrapper recommends: ii bash-completion 1:2.1-4.3 virtualenvwrapper suggests no packages. -- no debconf information
Bug#881988: speedtest-cli: Error message on no Internet connection
Package: speedtest-cli Version: 1.0.7-1 Severity: normal Dear Maintainer, I use speedtest-cli for checking the WAN connectivity on our network. When no Internet link is up (usually between the primary link failure and switchover) and I run speedtest to check the status, I get a message: $> speedtest Retrieving speedtest.net configuration... Cannot retrieve speedtest configuration ERROR: Expected: a message informing the user that speedtest is unable to connect with the Internet. Reproduction: run speedtest on a LAN without Internet connection. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (900, 'testing'), (600, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 4.13.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), LANGUAGE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages speedtest-cli depends on: ii python2.7.14-1 ii python-pkg-resources 36.6.0-1 speedtest-cli recommends no packages. speedtest-cli suggests no packages. -- no debconf information
Bug#871460: another example
I track testing/sid amd64 and update my system daily. Had to reboot today, and was surprised that the stock Debian wallpaper appeared instead of my favourite one. Tried to change it in cinnamon-settings, to no effect. I also noticed that a dark GTK3 theme stopped working as well (Firefox and Thunderbird used a standard bright gray theme). Keys assigned to launch a web browser or email client didn't work too. I reassigned them to custom launchers. I don't like any audio notifications for Cinnamon or FF/TB and was surprised to hear a sound when new mail arrived too... I read suggestions in this bug report and can confirm that removing the gnome-settings-daemon (probably a leftover from the past) actually helps. No more problems, the old wallpaper and themes are back. The culprit: Aptitude 0.8.8: log report Wed, Aug 16 2017 08:27:45 +0200 (...) [UPGRADE] gnome-settings-daemon:amd64 3.22.2-5 -> 3.24.3-1
Bug#843514: python3-nbconvert: missing dependency on python3-entrypoints
Package: python3-nbconvert Version: 4.2.0-2 Severity: important Dear Maintainer, python3-nbconvert cannot be imported - raises ImportError because of missing python3-entrypoints. Works after installing python3-nbconvert manually. $ipython3 [0] 16-11-07 11:10 Python 3.5.2+ (default, Sep 22 2016, 12:18:14) Type "copyright", "credits" or "license" for more information. IPython 5.1.0 -- An enhanced Interactive Python. ? -> Introduction and overview of IPython's features. %quickref -> Quick reference. help -> Python's own help system. object? -> Details about 'object', use 'object??' for extra details. In [1]: import nbconvert --- ImportError Traceback (most recent call last) in () > 1 import nbconvert /usr/lib/python3/dist-packages/nbconvert/__init__.py in () 2 3 from ._version import version_info, __version__ > 4 from .exporters import * 5 from . import filters 6 from . import preprocessors /usr/lib/python3/dist-packages/nbconvert/exporters/__init__.py in () > 1 from .export import * 2 from .html import HTMLExporter 3 from .slides import SlidesExporter 4 from .templateexporter import TemplateExporter 5 from .latex import LatexExporter /usr/lib/python3/dist-packages/nbconvert/exporters/export.py in () 7 from itertools import chain 8 > 9 import entrypoints 10 11 from traitlets.log import get_logger ImportError: No module named 'entrypoints' -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (900, 'testing'), (600, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 4.7.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages python3-nbconvert depends on: ii ipython3 5.1.0-2 ii python3-ipython 5.1.0-2 ii python3-jinja22.8-1 ii python3-jupyter-core 4.2.0-2 ii python3-mistune 0.7.3-1 ii python3-nbformat 4.1.0-2 ii python3-pygments 2.1.3+dfsg-1 ii python3-traitlets 4.3.1-1 pn python3:any python3-nbconvert recommends no packages. python3-nbconvert suggests no packages. -- no debconf information
Bug#842777: python3-spyder: broken dependency on python3-qtconsole (virtual package)
Package: python3-spyder Version: 3.0.1+dfsg1-1 Severity: serious Justification: Policy 3.5 Dear Maintainer, python3-spyder requires python3-qtconsole, which is a virtual package with no actual packages to provide it. So, python3-spyder cannot even be installed. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (900, 'testing'), (600, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 4.7.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#833719: tested, confirmed
Upgrading libnss3 worked for me as well; adding a hard dependency on >= 3.26 should solve the problem. I didn't have to upgrade libnspr4 (stays at 4.12-2).
Bug#830688: shellinabox: Some ANSI format sequences not rendered correctly
Package: shellinabox Version: 2.19 Severity: normal Tags: upstream Dear Maintainer, some ANSI formatting sequences don't work in shellinabox: -bold: echo '\x1b[1mtext\x1b[0m' -blinking: echo '\x1b[5mtext\x1b[0m' -dimmed: echo '\x1b[2mtext\x1b[0m' -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (900, 'testing'), (600, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 4.6.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages shellinabox depends on: ii adduser 3.115 ii libc62.22-13 ii libpam0g 1.1.8-3.3 ii libssl1.0.2 1.0.2h-1 ii lsb-base 9.20160629 ii zlib1g 1:1.2.8.dfsg-2+b1 shellinabox recommends no packages. Versions of packages shellinabox suggests: ii openssl 1.0.2h-1 -- Configuration Files: /etc/default/shellinabox changed: SHELLINABOX_DAEMON_START=1 SHELLINABOX_PORT=4200 SHELLINABOX_ARGS="-t --no-beep" -- no debconf information
Bug#829712: cinnamon: Display applications on the workspace where they were launched
Package: cinnamon Version: 3.0.4-1 Severity: minor Dear Maintainer, whenever I launch an application and switch the workspace while the program is starting up, the window appears on the new workspace, instead of the one where I launched it. Example: 1. set up a multi-workspace desktop (two are enough) 2. start an application which takes a few seconds to run, like firefox 3. quickly switch between workspaces 4. IS: application shows up on the new workspace SHOULD BE: application will stay where it was started -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (900, 'testing'), (600, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 4.6.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages cinnamon depends on: ii caribou 0.4.20-2 ii cinnamon-common 3.0.4-1 ii cinnamon-control-center 3.0.0-1 ii cinnamon-desktop-data3.0.2-1 ii cinnamon-screensaver 3.0.0-1 ii cinnamon-session 3.0.1-1 ii cinnamon-settings-daemon 3.0.1-2 ii cjs 3.0.1-2 ii cups-pk-helper 0.2.5-2+b1 ii dconf-gsettings-backend [gsettings-backend] 0.26.0-1 ii gir1.2-accountsservice-1.0 0.6.40-3 ii gir1.2-caribou-1.0 0.4.20-2 ii gir1.2-clutter-1.0 1.26.0-2 ii gir1.2-cmenu-3.0 3.0.1-1 ii gir1.2-cogl-1.0 1.22.0-2 ii gir1.2-gconf-2.0 3.2.6-3 ii gir1.2-gdkpixbuf-2.0 2.34.0-1 ii gir1.2-gkbd-3.0 3.6.0-1 ii gir1.2-glib-2.0 1.48.0-2 ii gir1.2-gnomedesktop-3.0 3.20.2-1 ii gir1.2-gtk-3.0 3.20.6-2 ii gir1.2-gtkclutter-1.01.8.0-1 ii gir1.2-javascriptcoregtk-3.0 2.4.11-2 ii gir1.2-keybinder-3.0 0.3.1-1 ii gir1.2-meta-muffin-0.0 3.0.4-1 ii gir1.2-networkmanager-1.01.2.2-2 ii gir1.2-notify-0.70.7.6-2 ii gir1.2-pango-1.0 1.40.1-1 ii gir1.2-polkit-1.00.105-15 ii gir1.2-soup-2.4 2.54.1-1 ii gir1.2-upowerglib-1.00.99.4-3 ii gir1.2-webkit-3.02.4.11-2 ii gkbd-capplet 3.6.0-1 ii gnome-backgrounds3.20-1 ii gnome-icon-theme-symbolic3.12.0-2 ii gnome-themes-standard3.20.2-3 ii gsettings-desktop-schemas3.20.0-3 ii libatk-bridge2.0-0 2.20.1-2 ii libatk1.0-0 2.20.0-1 ii libc62.22-13 ii libcairo21.14.6-1+b1 ii libcinnamon-menu-3-0 3.0.1-1 ii libcjs0 3.0.1-2 ii libclutter-1.0-0 1.26.0-2 ii libcogl-pango20 1.22.0-2 ii libcogl-path20 1.22.0-2 ii libcogl201.22.0-2 ii libcroco30.6.11-1 ii libgdk-pixbuf2.0-0 2.34.0-1 ii libgirepository-1.0-11.48.0-2 ii libgl1-mesa-glx [libgl1] 11.2.2-1 ii libglib2.0-0 2.48.1-1 ii libglib2.0-bin 2.48.1-1 ii libgstreamer1.0-01.8.2-1 ii libgtk-3-0 3.20.6-2 ii libjs-jquery 1.12.3-1 ii libmozjs-24-024.2.0-3 ii libmuffin0 3.0.4-1 ii libpango-1.0-0 1.40.1-1 ii libpangocairo-1.0-0 1.40.1-1 ii libstartup-notification0 0.12-4 ii libx11-6 2:1.6.3-1 ii libxfixes3 1:5.0.2-1 ii libxml2 2.9.3+dfsg1-1.2 ii mesa-utils 8.3.0-1 ii nemo 3.0.3-1 ii policykit-1-gnome0.105-3 ii python-dbus 1.2.4-1 ii python-gconf 2.28.1+dfsg-1.1 ii python-gi-cairo
Bug#827507: cinnamon-settings segfaults on entering power settings applet
Package: cinnamon Version: 3.0.4-1 Severity: normal Dear Maintainer, cinnamon-settings throws a segmentation fault whenever I try to open the power settings, be it from the panel applet or the settings window. Steps to reproduce: 1. open "cinnamon-settings" in terminal 2. enter the power settings 3. EXPECTED: you have the power settings applet HAPPENS: window closes, you get segmentation fault: $ cinnamon-settings [0] 16-06-17 8:01 Loading Power module [1](PID) segmentation fault cinnamon-settings (tested on a clean boot, with the same result) Power management was working about a month ago or so - possibly a regression. I'm using systemd 230-2 and upower 0.99.4-3. Hardware: Lenovo Thinkpad W500. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (900, 'testing'), (600, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 4.6.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages cinnamon depends on: ii caribou 0.4.20-1 ii cinnamon-common 3.0.4-1 ii cinnamon-control-center 3.0.0-1 ii cinnamon-desktop-data3.0.2-1 ii cinnamon-screensaver 3.0.0-1 ii cinnamon-session 3.0.1-1 ii cinnamon-settings-daemon 3.0.1-2 ii cjs 3.0.1-2 ii cups-pk-helper 0.2.5-2+b1 ii dconf-gsettings-backend [gsettings-backend] 0.26.0-1 ii gir1.2-accountsservice-1.0 0.6.40-3 ii gir1.2-caribou-1.0 0.4.20-1 ii gir1.2-clutter-1.0 1.26.0-2 ii gir1.2-cmenu-3.0 3.0.1-1 ii gir1.2-cogl-1.0 1.22.0-2 ii gir1.2-gconf-2.0 3.2.6-3 ii gir1.2-gdkpixbuf-2.0 2.34.0-1 ii gir1.2-gkbd-3.0 3.6.0-1 ii gir1.2-glib-2.0 1.48.0-2 ii gir1.2-gnomedesktop-3.0 3.20.2-1 ii gir1.2-gtk-3.0 3.20.6-1 ii gir1.2-gtkclutter-1.01.8.0-1 ii gir1.2-javascriptcoregtk-3.0 2.4.11-1+b1 ii gir1.2-keybinder-3.0 0.3.1-1 ii gir1.2-meta-muffin-0.0 3.0.4-1 ii gir1.2-networkmanager-1.01.2.2-2 ii gir1.2-notify-0.70.7.6-2 ii gir1.2-pango-1.0 1.40.1-1 ii gir1.2-polkit-1.00.105-15 ii gir1.2-soup-2.4 2.54.1-1 ii gir1.2-upowerglib-1.00.99.4-3 ii gir1.2-webkit-3.02.4.11-1+b1 ii gkbd-capplet 3.6.0-1 ii gnome-backgrounds3.20-1 ii gnome-icon-theme-symbolic3.12.0-2 ii gnome-themes-standard3.20.2-3 ii gsettings-desktop-schemas3.20.0-3 ii libatk-bridge2.0-0 2.20.1-2 ii libatk1.0-0 2.20.0-1 ii libc62.22-11 ii libcairo21.14.6-1+b1 ii libcinnamon-menu-3-0 3.0.1-1 ii libcjs0 3.0.1-2 ii libclutter-1.0-0 1.26.0-2 ii libcogl-pango20 1.22.0-2 ii libcogl-path20 1.22.0-2 ii libcogl201.22.0-2 ii libcroco30.6.11-1 ii libgdk-pixbuf2.0-0 2.34.0-1 ii libgirepository-1.0-11.48.0-2 ii libgl1-mesa-glx [libgl1] 11.2.2-1 ii libglib2.0-0 2.48.1-1 ii libglib2.0-bin 2.48.1-1 ii libgstreamer1.0-01.8.2-1 ii libgtk-3-0 3.20.6-1 ii libjs-jquery 1.12.3-1 ii libmozjs-24-024.2.0-3 ii libmuffin0 3.0.4-1 ii libpango-1.0-0 1.40.1-1 ii libpangocairo-1.0-0 1.40.1-1 ii libstartup-notification0 0.12-4 ii libx11-6 2:1.6.3-1 ii libxfixes3 1:5.0.1-2+b2 ii libxml2
Bug#763050: possible culprit: debugger plugin, turn it off as a workaround
Hi, I'm having the same problem right now on Jessie. It turns out that if I run geany -p (without loading plugins), it starts... When I run geany -v, I get: Geany-INFO: Geany 1.24.1, pl_PL.UTF-8 Geany-INFO: GTK 2.24.24, GLib 2.42.0 Geany-INFO: System data dir: /usr/share/geany Geany-INFO: User config dir: /home/elegant/.config/geany Geany-INFO: System plugin path: /usr/lib/x86_64-linux-gnu/geany Geany-INFO: Added filetype Graphviz (58). Geany-INFO: Added filetype Go (59). Geany-INFO: Added filetype Cython (60). Geany-INFO: Added filetype Scala (61). Geany-INFO: Added filetype Clojure (62). Geany-INFO: Added filetype Genie (63). Geany-INFO: Added filetype CUDA (64). Geany-INFO: Loaded: /usr/lib/x86_64-linux-gnu/geany/addons.so (Addons) Geany-INFO: Loaded: /usr/lib/x86_64-linux-gnu/geany/autoclose.so (Auto-close) Geany-INFO: Loaded: /usr/lib/x86_64-linux-gnu/geany/codenav.so (Code navigation) Attempt to unlock mutex that was not locked [1]4412 abort geany -v Looks like it stops running when trying to load one of the plugins. I've checked the ~/.config/geany/geany.conf to see which plugins were enabled. There is a line starting with active_plugins where you can see all enabled plugins. In my case, the plugin which followed codenav.so was debugger.so I've removed its path from the file. Geany started. To sum up, 1. geany -p (should run) 2. geany -v (should show you if it terminates abnormally during the plugin-loading phase) 3. edit ~/.config/geany/geany.conf 4. look for debugger.so in an active_plugins line - if found, delete the path and try running geany again. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749669: gksudo + fprintd: no prompt for PAM authentication based on fingerprint
Package: gksu Version: 2.0.2-6 Severity: important Dear Maintainer, I'm using a fingerprint reader and fprintd (0.5.1-1) package for the fingerprint functionality. The PAM policy is configured so that it asks for swiping a finger on a reader, and if that fails, asks for user password. Whenever I use gksudo, I don't get any window with a prompt for swiping my finger, even though the back end works: I can swipe the finger, press return and the gksudo'ed application starts. Test case: 1. enter: gksudo foo in a terminal window or run prompt (where foo is a placeholder name for an app; in my case, it was gparted and unetbootin) 2. you should get a gksudo prompt asking for swiping a finger - that doesn't happen, you don't get any box 3. if you now swipe your finger and press return on the keyboard, you're authorized and the app (foo) starts correctly Additional info: I'm using Debian jessie/sid amd64 with LXDE+Openbox desktop on a Lenovo T61p laptop computer. There were two kinds of palmrests for this series of machines: one didn't have a fingerprint reader and the other had. I've replaced the former with the latter. Everything besides gksudo worked out of the box after installing fprintd and enrolling my fingerprint: xscreensaver (unlocking screen), lightdm (user login), sudo, console login - all work correctly and display the proper prompts, which rules out a bug in fprintd or PAM. Before adding the fingerprint reader, gksudo worked correctly and asked for my password. $ uname -a: Linux blackcat 3.13-1-amd64 #1 SMP Debian 3.13.10-1 (2014-04-15) x86_64 GNU/Linux lsusb entry: Bus 002 Device 003: ID 0483:2016 STMicroelectronics Fingerprint Reader $ cat /etc/pam.d/common-auth: # # /etc/pam.d/common-auth - authentication settings common to all services # # This file is included from other service-specific PAM config files, # and should contain a list of the authentication modules that define # the central authentication scheme for use on the system # (e.g., /etc/shadow, LDAP, Kerberos, etc.). The default is to use the # traditional Unix authentication mechanisms. # # As of pam 1.0.1-6, this file is managed by pam-auth-update by default. # To take advantage of this, it is recommended that you configure any # local modules either before or after the default block, and use # pam-auth-update to manage selection of other modules. See # pam-auth-update(8) for details. # here are the per-package modules (the Primary block) auth[success=2 default=ignore] pam_fprintd.so max_tries=1 timeout=10 # debug auth[success=1 default=ignore] pam_unix.so nullok_secure try_first_pass # here's the fallback if no module succeeds authrequisite pam_deny.so # prime the stack with a positive return value if there isn't one already; # this avoids us returning an error just because nothing sets a success code # since the modules above will each just jump around authrequiredpam_permit.so # and here are more per-package modules (the Additional block) authoptionalpam_cap.so # end of pam-auth-update config -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-1-amd64 (SMP w/2 CPU cores) Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gksu depends on: ii libatk1.0-0 2.12.0-1 ii libc6 2.18-7 ii libcairo2 1.12.16-2 ii libfontconfig12.11.0-5 ii libfreetype6 2.5.2-1 ii libgconf2-4 3.2.6-2 ii libgdk-pixbuf2.0-02.30.7-1 ii libgksu2-02.0.13~pre1-7 ii libglib2.0-0 2.40.0-3 ii libgnome-keyring0 3.4.1-1 ii libgtk2.0-0 2.24.23-1 ii libpango1.0-0 1.36.3-1 ii libstartup-notification0 0.12-3 ii sudo 1.8.9p5-1 Versions of packages gksu recommends: ii gnome-keyring 3.8.2-2+b1 gksu 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
