Bug#950590: evolution: Reportbug information for evolution is out of date: gitlab, not bugzilla
Package: evolution Version: 3.30.5-1.1 Severity: normal Dear Maintainer, The reportbug information for evolution, wherein you redirect people to upstream, seems arguably out-of-date, in that you send people to bugzilla.gnome.org, which is no longer accepting new bugs, and ask for a Forwarded-To: header which links to same. A pointer to https://gitlab.gnome.org/GNOME/evolution would seem more appropriate (and helpful: it's *really* non-obvious how to find package pages on gitlab!), and the sample bug link should probably be something like https://gitlab.gnome.org/GNOME/evolution/issues/772. Best regards, Conrad -- System Information: Debian Release: 10.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-6-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages evolution depends on: ii dbus 1.12.16-1 ii evolution-common 3.30.5-1.1 ii evolution-data-server 3.30.5-1 ii libc6 2.28-10 ii libcamel-1.2-623.30.5-1 ii libclutter-gtk-1.0-0 1.8.4-4 ii libecal-1.2-19 3.30.5-1 ii libedataserver-1.2-23 3.30.5-1 ii libevolution 3.30.5-1.1 ii libglib2.0-0 2.58.3-2+deb10u2 ii libgtk-3-0 3.24.5-1 ii libical3 3.0.4-3 ii libnotify4 0.7.7-4 ii libsoup2.4-1 2.64.2-2 ii libwebkit2gtk-4.0-37 2.26.3-1~deb10u1 ii libxml22.9.4+dfsg1-7+b3 ii psmisc 23.2-1 Versions of packages evolution recommends: ii evolution-plugin-bogofilter 3.30.5-1.1 ii evolution-plugin-pstimport 3.30.5-1.1 ii evolution-plugins3.30.5-1.1 ii yelp 3.31.90-1 Versions of packages evolution suggests: pn evolution-ews pn evolution-plugins-experimental ii gnupg 2.2.12-1+deb10u1 ii network-manager 1.14.6-2+deb10u1 -- debconf-show failed
Bug#942645: owncloud-client: "Server version unsupported" message unhelpful
Package: owncloud-client Version: 2.5.1.10973+dfsg-1 Severity: normal Dear Maintainer, I've connected to a server but am receiving a message "The server version 9.0.2.2- is unsupported! Proceed at your own risk." This message is confusing, since it doesn't give any clue as to what the client version is. The Debian package version, 2.5.1.10973+dfsg-1, is so wildly at odds with 9.0.2.2 that there doesn't seem a meaningful comparison. Is this a protocol version? Indeed, Internet discussions of same indicate that there's no meaningful comparison between the two at all, but it looks as if pre-10 servers are obsolete. Perhaps the client could indicate what server versions it supports, and suggest a judgement as to whether it's the client or the server that needs an upgrade? Best, Conrad -- System Information: Debian Release: 10.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-6-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages owncloud-client depends on: ii libc6 2.28-10 ii libgcc1 1:8.3.0-6 ii libowncloudsync0 2.5.1.10973+dfsg-1 ii libqt5core5a 5.11.3+dfsg1-1 ii libqt5dbus5 5.11.3+dfsg1-1 ii libqt5gui55.11.3+dfsg1-1 ii libqt5keychain1 0.9.1-2 ii libqt5network55.11.3+dfsg1-1 ii libqt5sql5-sqlite 5.11.3+dfsg1-1 ii libqt5webkit5 5.212.0~alpha2-21 ii libqt5widgets55.11.3+dfsg1-1 ii libqt5xml55.11.3+dfsg1-1 ii libstdc++68.3.0-6 ii owncloud-client-l10n 2.5.1.10973+dfsg-1 Versions of packages owncloud-client recommends: ii owncloud-client-doc 2.5.1.10973+dfsg-1 owncloud-client suggests no packages. -- no debconf information
Bug#942644: owncloud-client: Password box doesn't strip trailing newline
Package: owncloud-client Version: 2.5.1.10973+dfsg-1 Severity: normal Dear Maintainer, When adding a new server, the password dialog doesn't strip a trailing newline. Seems that most password fields do that these days. Context is password stores where one copies a whole line (e.g. with triple click in a terminal), which includes the trailing newline: when this kind of content is pasted into the vast majority of password fields, the trailing newline (possibly CR/LF) gets stripped. Not so with Owncloud Client, which reports an authentication failure as a result. To reproduce: - If you have a terminal-based password store, the password may well be displayed on its own line in the terminal. - The easiest way to copy this is just to triple-click, selecting the whole line, including trailing newline. - When pasted into the OwnCloud add server dialog's password field, the newline isn't stripped out, resulting in authentication failure. - Expected behaviour would be that the trailing newline is stripped, and authentication succeeds. Best, Conrad -- System Information: Debian Release: 10.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-6-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages owncloud-client depends on: ii libc6 2.28-10 ii libgcc1 1:8.3.0-6 ii libowncloudsync0 2.5.1.10973+dfsg-1 ii libqt5core5a 5.11.3+dfsg1-1 ii libqt5dbus5 5.11.3+dfsg1-1 ii libqt5gui55.11.3+dfsg1-1 ii libqt5keychain1 0.9.1-2 ii libqt5network55.11.3+dfsg1-1 ii libqt5sql5-sqlite 5.11.3+dfsg1-1 ii libqt5webkit5 5.212.0~alpha2-21 ii libqt5widgets55.11.3+dfsg1-1 ii libqt5xml55.11.3+dfsg1-1 ii libstdc++68.3.0-6 ii owncloud-client-l10n 2.5.1.10973+dfsg-1 Versions of packages owncloud-client recommends: ii owncloud-client-doc 2.5.1.10973+dfsg-1 owncloud-client suggests no packages. -- no debconf information
Bug#942099: gnome-shell: Screensaver doesn't power down monitor ("Server does not have the DPMS Extension")
Package: gnome-shell Version: 3.30.2-9 Severity: normal Dear Maintainer, Not entirely sure where this report should go, but the gnome-screensaver package says that gnome-shell does screensaving these days.. Before I upgraded to buster and Wayland, Debian would send my monitor to sleep when the screensaver kicked in. It doesn't do this any more. There's nothing in Device Settings for my monitor, or Power Management Settings, about sending the monitor to sleep. Investigating, I find that "xset q" reports "Server does not have the DPMS Extension". This thread suggests that I might be wrong to investigate using "xset", but whatever xset's been replaced with clearly isn't working. https://unix.stackexchange.com/questions/316929/display-is-not-capable-of- dpms-after-gnome-wayland-update The busctl invocations described in the thread do work: busctl --user set-property org.gnome.Mutter.DisplayConfig /org/gnome/Mutter/DisplayConfig org.gnome.Mutter.DisplayConfig PowerSaveMode i 1 Did the upgrade from stretch fail to install some crucial package? Where should I now be configuring Gnome to send my monitor to sleep? Best, Conrad -- System Information: Debian Release: 10.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-6-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnome-shell depends on: ii dconf-gsettings-backend [gsettings-backend] 0.30.1-2 ii evolution-data-server3.30.5-1 ii gir1.2-accountsservice-1.0 0.6.45-2 ii gir1.2-atspi-2.0 2.30.0-7 ii gir1.2-freedesktop 1.58.3-2 ii gir1.2-gcr-3 3.28.1-1 ii gir1.2-gdesktopenums-3.0 3.28.1-1 ii gir1.2-gdm-1.0 3.30.2-3 ii gir1.2-geoclue-2.0 2.5.2-1 ii gir1.2-glib-2.0 1.58.3-2 ii gir1.2-gnomebluetooth-1.03.28.2-4~deb10u1 ii gir1.2-gnomedesktop-3.0 3.30.2.1-2 ii gir1.2-gtk-3.0 3.24.5-1 ii gir1.2-gweather-3.0 3.28.2-2 ii gir1.2-ibus-1.0 1.5.19-4+deb10u1 ii gir1.2-mutter-3 3.30.2-7 ii gir1.2-nm-1.01.14.6-2 ii gir1.2-nma-1.0 1.8.20-1.1 ii gir1.2-pango-1.0 1.42.4-7~deb10u1 ii gir1.2-polkit-1.00.105-25 ii gir1.2-rsvg-2.0 2.44.10-2.1 ii gir1.2-soup-2.4 2.64.2-2 ii gir1.2-upowerglib-1.00.99.10-1 ii gjs 1.54.3-1 ii gnome-backgrounds3.30.0-1 ii gnome-settings-daemon3.30.2-3 ii gnome-shell-common 3.30.2-9 ii gsettings-desktop-schemas3.28.1-1 ii libatk-bridge2.0-0 2.30.0-5 ii libatk1.0-0 2.30.0-2 ii libc62.28-10 ii libcairo21.16.0-4 ii libcanberra-gtk3-0 0.30-7 ii libcanberra0 0.30-7 ii libcroco30.6.12-3 ii libecal-1.2-19 3.30.5-1 ii libedataserver-1.2-233.30.5-1 ii libgcr-base-3-1 3.28.1-1 ii libgdk-pixbuf2.0-0 2.38.1+dfsg-1 ii libgirepository-1.0-11.58.3-2 ii libgjs0g 1.54.3-1 ii libglib2.0-0 2.58.3-2+deb10u1 ii libglib2.0-bin 2.58.3-2+deb10u1 ii libgstreamer1.0-01.14.4-1 ii libgtk-3-0 3.24.5-1 ii libical3 3.0.4-3 ii libjson-glib-1.0-0 1.4.4-2 ii libmutter-3-03.30.2-7 ii libnm0 1.14.6-2 ii libpango-1.0-0 1.42.4-7~deb10u1 ii libpangocairo-1.0-0 1.42.4-7~deb10u1 ii libpolkit-agent-1-0 0.105-25 ii libpolkit-gobject-1-00.105-25 ii libpulse-mainloop-glib0 12.2-4+deb10u1 ii libpulse012.2-4+deb10u1 ii libsecret-1-00.18.7-1 ii libstartup-notification0
Bug#941123: gdm3: action-middle-click-titlebar 'lower' is ignored: can't set window to lower on title bar middle-click
Package: gdm3 Version: 3.30.2-3 Severity: normal Dear Maintainer, In previous incarnations of Debian, middle-clicking on the title bar lowered windows (moved them to the back of the stack, making other windows visible). More recently this was relegated to a "tweak". Now even that doesn't work. Using either the tweaks app, a manual edit of gtk-*.0/settings.ini, or the command line dconf write /org/gnome/desktop/wm/preferences/action-middle-click-titlebar "'lower'" .. it should be possible to configure middle clicking on a title bar to lower the window in question. This no longer works. Other values, such as "minimize", do still work. It would be nice if "lower" functionality could be restored. Best, Conrad -- System Information: Debian Release: 10.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-6-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gdm3 depends on: ii accountsservice 0.6.45-2 ii adduser 3.118 ii cinnamon [x-window-manager] 3.8.8-1 ii cinnamon-session [x-session-manager] 3.8.2-1 ii dconf-cli 0.30.1-2 ii dconf-gsettings-backend 0.30.1-2 ii debconf [debconf-2.0] 1.5.71 ii gir1.2-gdm-1.03.30.2-3 ii gnome-session [x-session-manager] 3.30.1-2 ii gnome-session-bin 3.30.1-2 ii gnome-settings-daemon 3.30.2-3 ii gnome-shell 3.30.2-9 ii gnome-terminal [x-terminal-emulator] 3.30.2-2 ii gsettings-desktop-schemas 3.28.1-1 ii libaccountsservice0 0.6.45-2 ii libaudit1 1:2.8.4-3 ii libc6 2.28-10 ii libcanberra-gtk3-00.30-7 ii libcanberra0 0.30-7 ii libgdk-pixbuf2.0-02.38.1+dfsg-1 ii libgdm1 3.30.2-3 ii libglib2.0-0 2.58.3-2+deb10u1 ii libglib2.0-bin2.58.3-2+deb10u1 ii libgtk-3-03.24.5-1 ii libkeyutils1 1.6-6 ii libpam-modules1.3.1-5 ii libpam-runtime1.3.1-5 ii libpam-systemd241-7~deb10u1 ii libpam0g 1.3.1-5 ii librsvg2-common 2.44.10-2.1 ii libselinux1 2.8-1+b1 ii libsystemd0 241-7~deb10u1 ii libwrap0 7.6.q-28 ii libx11-6 2:1.6.7-1 ii libxau6 1:1.0.8-1+b2 ii libxcb1 1.13.1-2 ii libxdmcp6 1:1.1.2-3 ii lsb-base 10.2019051400 ii metacity [x-window-manager] 1:3.30.1-2 ii muffin [x-window-manager] 3.8.2-1 ii mutter [x-window-manager] 3.30.2-7 ii policykit-1 0.105-25 ii procps2:3.3.15-2 ii ucf 3.0038+nmu1 ii x11-common1:7.7+19 ii x11-xserver-utils 7.7+8 ii xfce4-session [x-session-manager] 4.12.1-6 ii xfce4-terminal [x-terminal-emulator] 0.8.7.4-2 ii xfwm4 [x-window-manager] 4.12.5-1 ii xterm [x-terminal-emulator] 344-1 Versions of packages gdm3 recommends: ii at-spi2-core2.30.0-7 ii desktop-base10.0.2 ii x11-xkb-utils 7.7+4 ii xserver-xephyr 2:1.20.4-1 ii xserver-xorg1:7.7+19 ii zenity 3.30.0-2 Versions of packages gdm3 suggests: ii gnome-orca3.30.1-1 pn libpam-fprintd ii libpam-gnome-keyring 3.28.2-5 -- debconf information: gdm3/daemon_name: /usr/sbin/gdm3 * shared/default-x-display-manager: gdm3
Bug#939407: gtk-3-examples: Paste from closed GTK3 applications is broken under Wayland (clipboard vanishes on exit)
Package: gtk-3-examples Version: 3.24.5-1 Severity: normal Dear Maintainer, This has been reported upstream, but since no fix has been forthcoming in *three years*, there's no due date, and the issue "needs design", it would be interesting to know whether Debian has a workaround: this seems like a major usability fail. https://gitlab.gnome.org/GNOME/gtk/issues/587 If I copy some data from a GTK3 application and then close the app, the clipboard is cleared. This is unexpected: usual behaviour is for copied data to survive application closure. To reproduce: - Open gtk3-demo, expand the "Entry" section and double-click on "Entry Buffer". - This will open a text field; type in some text and and press control-C to copy it. - Select a text field in another window and press control-V: the copied text is pasted/inserted, as expected. - Close gtk3-demo. - Select a text field in another window and press control-V: nothing appears. The clipboard is empty (or perhaps never existed). Expected behaviour would be that the second attempt to paste would work exactly the same as the first. -- System Information: Debian Release: 10.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gtk-3-examples depends on: ii dconf-gsettings-backend [gsettings-backend] 0.30.1-2 ii libatk-bridge2.0-0 2.30.0-5 ii libatk1.0-0 2.30.0-2 ii libc62.28-10 ii libcairo-gobject21.16.0-4 ii libcairo21.16.0-4 ii libepoxy01.5.3-0.1 ii libfontconfig1 2.13.1-2 ii libfreetype6 2.9.1-3 ii libgdk-pixbuf2.0-0 2.38.1+dfsg-1 ii libglib2.0-0 2.58.3-2 ii libgtk-3-0 3.24.5-1 ii libharfbuzz0b2.3.1-1 ii libpango-1.0-0 1.42.4-7~deb10u1 ii libpangocairo-1.0-0 1.42.4-7~deb10u1 ii libpangoft2-1.0-01.42.4-7~deb10u1 ii libwayland-client0 1.16.0-1 ii libwayland-cursor0 1.16.0-1 ii libwayland-egl1 1.16.0-1 ii libx11-6 2:1.6.7-1 ii libxcomposite1 1:0.4.4-2 ii libxcursor1 1:1.1.15-2 ii libxdamage1 1:1.1.4-3+b3 ii libxext6 2:1.3.3-1+b2 ii libxfixes3 1:5.0.3-1 ii libxi6 2:1.7.9-1 ii libxinerama1 2:1.1.4-2 ii libxkbcommon00.8.2-1 ii libxrandr2 2:1.5.1-1 gtk-3-examples recommends no packages. gtk-3-examples suggests no packages. -- no debconf information
Bug#939374: pinentry-tty doesn't support control-U
Package: pinentry-tty Version: 1.1.0-2 Severity: normal Dear Maintainer, Use of control-U to kill (entirely delete) the current line of text has been fairly standard during password entry on Linux for decades; it's very disorienting that pinentry-tty doesn't support it. Looks as if a user has submitted a (tiny!) patch upstream to enable this, but not clear what upstream think of it: https://dev.gnupg.org/T4583 Best regards, Conrad -- System Information: Debian Release: 10.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages pinentry-tty depends on: ii libassuan0 2.5.2-1 ii libc6 2.28-10 ii libgpg-error0 1.35-1 pinentry-tty recommends no packages. Versions of packages pinentry-tty suggests: pn pinentry-doc -- no debconf information
Bug#933174: wayland: Brightness bar not displayed when adjusting screen brightness
Source: wayland Severity: normal Dear Maintainer, When I operate my laptop's screen brightness buttons, an overlay appears, usually with a bar showing the current level. Since upgrading to buster+wayland, the overlay appears, but the bar doesn't: it's always blank. Just noticed that this is *not* the case prior to login; I assume that the gdm greeter doesn't use wayland? Best regards, Conrad -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#932115: openstv: Homepage is confusing; arguably even wrong?
Package: openstv Version: 1.6.1-1.2 Severity: minor Dear Maintainer, The homepage for OpenSTV is listed as www.openstv.org, which redirects to the home page of OpaVote, the private company which originated the package but then (in 2011?) took it closed-source. That's kindof confusing since you can't get the source there, or even (nowadays) very much information at all about the software. The redirect seems to have been in place since August 2016. The last public version of OpenSTV was 1.7, six years ago; it would be pretty cool to know the provenance of Debian's OpenSTV 1.6: where is it really from, now? Is there a fork or a repo somewhere? Best, Conrad -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages openstv depends on: ii python 2.7.16-1 ii python-wxgtk3.0 3.0.2.0+dfsg-8 openstv recommends no packages. Versions of packages openstv suggests: ii python [python-profiler] 2.7.16-1 ii python2 [python-profiler] 2.7.16-1 -- no debconf information
Bug#931749: cryptsetup: "no longer required" on encrypted system!
Package: cryptsetup Version: 2:2.1.0-5 Severity: normal Dear Maintainer, So this is probably a buster upgrade issue, but not sure where to report it.. After upgrading to buster, deborphan --guess-dummy (seemingly correctly) identified cryptsetup as a transitional dummy package, suitable for removal. However after removing cryptsetup, apt now tells me all the time that cryptsetup-bin, cryptsetup-initramfs and cryptsetup-run "were automatically installed and are no longer required". But my system's LUKS1-on-LVM-RAID-1.. Running "apt autoremove" at this point would surely cause chaos? Conrad -- Package-specific info: -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages cryptsetup depends on: ii cryptsetup-initramfs 2:2.1.0-5 ii cryptsetup-run2:2.1.0-5 cryptsetup recommends no packages. cryptsetup suggests no packages. -- debconf information: cryptsetup/prerm_active_mappings: true
Bug#931747: gnome-terminal: Window dimensions tooltip missing when resizing under Wayland
Package: gnome-terminal Version: 3.30.2-2 Severity: normal Dear Maintainer, Buster upgrade issue: when resizing gnome-terminal windows under Wayland, there's no window dimensions tooltip. Logging in under Classic Gnome, the tooltip's there. Bug reported elsewhere too: https://bugzilla.redhat.com/show_bug.cgi?id=1306260 Best, Conrad -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnome-terminal depends on: ii dbus-user-session [default-dbus-session-bus] 1.12.16-1 ii dbus-x11 [dbus-session-bus] 1.12.16-1 ii dconf-gsettings-backend [gsettings-backend] 0.30.1-2 ii gnome-terminal-data 3.30.2-2 ii gsettings-desktop-schemas 3.28.1-1 ii libatk1.0-0 2.30.0-2 ii libc6 2.28-10 ii libdconf1 0.30.1-2 ii libglib2.0-0 2.58.3-2 ii libgtk-3-03.24.5-1 ii libpango-1.0-01.42.4-6 ii libuuid1 2.33.1-0.1 ii libvte-2.91-0 0.54.2-2 ii libx11-6 2:1.6.7-1 Versions of packages gnome-terminal recommends: ii gvfs 1.38.1-5 ii nautilus-extension-gnome-terminal 3.30.2-2 ii yelp 3.31.90-1 gnome-terminal suggests no packages. -- no debconf information
Bug#931744: gnome-terminal: "Show bold text in bright colours" has no effect
Package: gnome-terminal Version: 3.30.2-2 Severity: normal Dear Maintainer, Buster upgrade issue: after upgrading to buster I find bold text barely noticeable. I'm pretty sure that prior to upgrade it was highlighted with a brighter colour. I can see a "Show bold text in bright colours" checkbox in my colour scheme, and it's checked, but turning it on and off has no effect (unlike, say, checking the "Highlight colour" box, which has an instant effect). Holds true for six of the schemes I've tried (including "colours from system theme" checkbox), Solarized Dark being my "usual". Best, Conrad -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnome-terminal depends on: ii dbus-user-session [default-dbus-session-bus] 1.12.16-1 ii dbus-x11 [dbus-session-bus] 1.12.16-1 ii dconf-gsettings-backend [gsettings-backend] 0.30.1-2 ii gnome-terminal-data 3.30.2-2 ii gsettings-desktop-schemas 3.28.1-1 ii libatk1.0-0 2.30.0-2 ii libc6 2.28-10 ii libdconf1 0.30.1-2 ii libglib2.0-0 2.58.3-2 ii libgtk-3-03.24.5-1 ii libpango-1.0-01.42.4-6 ii libuuid1 2.33.1-0.1 ii libvte-2.91-0 0.54.2-2 ii libx11-6 2:1.6.7-1 Versions of packages gnome-terminal recommends: ii gvfs 1.38.1-5 ii nautilus-extension-gnome-terminal 3.30.2-2 ii yelp 3.31.90-1 gnome-terminal suggests no packages. -- no debconf information
Bug#911417: udisks2: Uses hardware clock for timestamps on removable media; should be UTC?
Package: udisks2 Version: 2.1.8-1 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** This may be a feature, or an issue with something higher up (e.g. Gnome) or lower down (e.g. mount), so please do point me elsewhere if that's appropriate. I have two very similar systems running jessie, but recently noticed that files written to VFAT removable media were an hour out between the two - i.e. a file written at 19:00 on one would show as 20:00 on the other (currently my timezone is GMT+1, BST). I eventually tracked this down to the fact that the desktop ran its hardware clock on local time (LOCAL in /etc/adjtime), while the laptop had been switched to hardware clock on UTC (UTC in /etc/adjtime). During the process of trying to work out why adjtime affects removable media, I found a number of claims on the Internet that Debian now insists on writing all VFAT removable media in UTC, because using local time must eventually result in insanity (or similar). My experience suggests that the time used on VFAT removable media is in fact the hardware clock time, which seems surprising: two jessie machines that display identical clock times will as a result stamp files on a memory card with different times according to whether they're running their hardware clock on LOCAL or UTC. That's a surprising point from which to control such a behaviour. Is this intentional? My search-fu isn't up to finding the point in the automount stack where this decision is made or documented.. *** End of the template - remove these template lines *** -- System Information: Debian Release: 9.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-8-amd64 (SMP w/8 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 /bin/dash Init: systemd (via /run/systemd/system) Versions of packages udisks2 depends on: ii dbus 1.10.26-0+deb9u1 ii libacl12.2.52-3+b1 ii libatasmart4 0.19-4+b1 ii libc6 2.24-11+deb9u3 ii libglib2.0-0 2.50.3-2 ii libgudev-1.0-0 230-3 ii libpam-systemd 232-25+deb9u4 ii libpolkit-agent-1-00.105-18 ii libpolkit-gobject-1-0 0.105-18 ii libsystemd0232-25+deb9u4 ii libudisks2-0 2.1.8-1 ii parted 3.2-17 ii udev 232-25+deb9u4 Versions of packages udisks2 recommends: ii dosfstools 4.1-1 ii eject2.1.5+deb1+cvs20081104-13.2 ii exfat-utils 1.2.5-2 ii gdisk1.0.1-1 ii ntfs-3g 1:2016.2.22AR.1+dfsg-1 ii policykit-1 0.105-18 Versions of packages udisks2 suggests: pn btrfs-progs | btrfs-tools ii cryptsetup-bin 2:1.7.3-4 ii mdadm 3.4-4+b1 pn reiserfsprogs pn xfsprogs -- no debconf information
Bug#869617: libutempter0: Helper executable multiply broken: can't add, can't del
Package: libutempter0 Version: 1.1.6-4 Severity: important Dear Maintainer, Hi there, I've been looking at trying to use libutempter0 to cope with the fact that since stretch, gnome-terminal no longer even touches utmp. This has been a little bumpier than anticipated, as utempter_add_record returns without error even though it fails. This appears to be down to the helper program, /usr/lib/../utempter, failing, and add_record then ignoring that fail. If you run utempter manually you get a failure exit status when trying to add (which utempter_add_record then ignores). The problem seems to be utempter.c's use of ptsname() to get the device name: this call fails. On advice from Christian Persch on the gnome-terminal team I tried replacing this call with ttyname(): utempter seems to behave correctly after making this change, and indeed my workaround for gnome-terminal then seems to work. So it'd be great to see a patch to this to replace the ptsname(STDIN_FILENO) call in utempter.c with a call to ttyname(STDIN_FILENO). Might also be worth patching the utempter library functions so that they fail if execution of utempter fails. Regards, Conrad -- System Information: Debian Release: 9.1 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-3-amd64 (SMP w/8 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 /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libutempter0 depends on: ii libc6 2.24-11+deb9u1 libutempter0 recommends no packages. libutempter0 suggests no packages. -- no debconf information
Bug#869119: gnome-terminal: Wheel/touchpad scrolling hangs terminal in vi/less
Package: gnome-terminal Version: 3.22.2-1 Severity: normal Dear Maintainer, * What led up to the situation? When using a full-terminal program (e.g. less, vim) in gnome-terminal, mouse wheel/touchpad scrolling seems to hang the terminal for a bit. This becomes particularly aggravated if you scroll up and down quite a bit (as might happen while scanning a long document, for example). * What exactly did you do (or not do) that was effective (or ineffective)? Started vim or less on a long file. Then swiped or mouse-wheeled down and up. * What was the outcome of this action? Scrolling stopped, and the terminal became non-responsive (even control-Z/suspend won't work, for example). * What outcome did you expect instead? Expected it to keep scrolling in response to input, or to react to my typing. There's no indication of high load while this is happening by the way. -- System Information: Debian Release: 9.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gnome-terminal depends on: ii dconf-gsettings-backend [gsettings-backend] 0.26.0-2+b1 ii gnome-terminal-data 3.22.2-1 ii gsettings-desktop-schemas3.22.0-1 ii libatk1.0-0 2.22.0-1 ii libc62.24-11+deb9u1 ii libdconf10.26.0-2+b1 ii libglib2.0-0 2.50.3-2 ii libgtk-3-0 3.22.11-1 ii libnautilus-extension1a 3.22.3-1 ii libpango-1.0-0 1.40.5-1 ii libuuid1 2.29.2-1 ii libvte-2.91-00.46.1-1 ii libx11-6 2:1.6.4-3 Versions of packages gnome-terminal recommends: ii dbus-user-session [default-dbus-session-bus] 1.10.18-1 ii dbus-x11 [dbus-session-bus] 1.10.18-1 ii gvfs 1.30.4-1 ii yelp 3.22.0-1 gnome-terminal suggests no packages. -- no debconf information
Bug#802919: unison: synchronization incompatibility when built with Ocaml versions pre/post-4.02
Package: unison Version: 2.48.3-1 Followup-For: Bug #802919 Dear Maintainer, Just to add another voice to this, particularly re: the oddness that stretch ships with ocaml-4.02, while its unison is compiled with -4.01. I realise it's heinous, but I do kindof think the solution has to be to ship both ocaml-4.01 and -4.02 builds of unison (and possibly as a result, ocaml itself). Possibly some pressure should be put on upstream to (1) catch the relevant exception and flag the ocaml version dependency, and (2) (as mentioned earlier in this thread) make the ocaml version explicit in unison's "-version" output and (possibly more a Debian packaging issue?) its executable filenames. This mess is certainly not Debian's fault, but it would greatly ease others' experience if both versions of unison were easily available as part of the official distribution. With a mixture of stretch, jessie and other machines, I've ended up installing three different builds of unison on one box. Conrad -- System Information: Debian Release: 9.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages unison depends on: ii libc6 2.24-11+deb9u1 Versions of packages unison recommends: ii openssh-client [ssh-client] 1:7.4p1-10 Versions of packages unison suggests: pn unison-all -- no debconf information
Bug#866795: gnome-contacts: No CardDAV support?
Package: gnome-contacts Version: 3.22.1-1+b2 Severity: important Dear Maintainer, [I suspect this is closely related to my encountering a similar problem wrt CalDAV calendars, submitted as bug #866794 versus gnome-calendar; please mark as duplicate/move to gnome-online-accounts if that's where this should really reside] I've just upgraded from jessie to stretch, and now cannot find a means of adding my CardDAV server as a source of contacts: there's a huge list of options, but nothing that seems to support CardDAV, which I used successfully on jessie. Currently the only way to add an address book seems to be to add an account, but the list of account types doesn't seem to include anything that would permit use of a CardDAV URL. I can't see any mention of DAV in the release notes either for this or for stretch itself. Any suggestions please? Regards, Conrad -- System Information: Debian Release: 9.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gnome-contacts depends on: ii dconf-gsettings-backend [gsettings-backend] 0.26.0-2+b1 ii libatk1.0-0 2.22.0-1 ii libc62.24-11+deb9u1 ii libcairo21.14.8-1 ii libchamplain-0.12-0 0.12.15-1 ii libcheese-gtk25 3.22.1-1+b1 ii libcheese8 3.22.1-1+b1 ii libclutter-1.0-0 1.26.0+dfsg-3 ii libclutter-gtk-1.0-0 1.8.2-2 ii libedataserver-1.2-223.22.7-1 ii libedataserverui-1.2-1 3.22.7-1 ii libfolks-eds25 0.11.3-2 ii libfolks-telepathy25 0.11.3-2 ii libfolks25 0.11.3-2 ii libgdk-pixbuf2.0-0 2.36.5-2 ii libgee-0.8-2 0.18.1-1 ii libgeocode-glib0 3.20.1-2 ii libglib2.0-0 2.50.3-2 ii libgnome-desktop-3-123.22.2-1 ii libgoa-1.0-0b3.22.5-1 ii libgtk-3-0 3.22.11-1 ii libpango-1.0-0 1.40.5-1 ii libpangocairo-1.0-0 1.40.5-1 ii libtelepathy-glib0 0.24.1-1.1 gnome-contacts recommends no packages. gnome-contacts suggests no packages. -- no debconf information
Bug#866794: gnome-calendar: No CalDAV support?
Package: gnome-calendar Version: 3.22.4-2 Severity: important Dear Maintainer, I've just upgraded from jessie to stretch, and while I note the pleasing UI of the new calendar which replaces evolution, I cannot find a means of adding CalDAV calendars to it: there's a huge list of options, but nothing that seems to support CalDAV, which I used successfully on jessie. Currently if I try to add a calendar, it asks me to add an account, but the list of account types doesn't seem to include anything that would permit use of a CalDAV URL. I can't see any mention of DAV in the release notes either for this or for stretch itself. Any suggestions please? Regards, Conrad -- System Information: Debian Release: 9.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gnome-calendar depends on: ii dconf-gsettings-backend [gsettings-backend] 0.26.0-2+b1 ii gsettings-desktop-schemas3.22.0-1 ii libatk1.0-0 2.22.0-1 ii libc62.24-11+deb9u1 ii libcairo-gobject21.14.8-1 ii libcairo21.14.8-1 ii libecal-1.2-19 3.22.7-1 ii libedataserver-1.2-223.22.7-1 ii libedataserverui-1.2-1 3.22.7-1 ii libgdk-pixbuf2.0-0 2.36.5-2 ii libglib2.0-0 2.50.3-2 ii libgoa-1.0-0b3.22.5-1 ii libgtk-3-0 3.22.11-1 ii libical2 2.0.0-0.5+b1 ii libicu57 57.1-6 ii libpango-1.0-0 1.40.5-1 ii libpangocairo-1.0-0 1.40.5-1 ii libsecret-1-00.18.5-3.1 ii libsoup2.4-1 2.56.0-2 ii libxml2 2.9.4+dfsg1-2.2 Versions of packages gnome-calendar recommends: ii evolution-data-server 3.22.7-1 gnome-calendar suggests no packages. -- no debconf information
Bug#845530: evince: Search doesn't navigate (by index or 'next') to found results
Package: evince Version: 3.14.1-2+deb8u1 Severity: normal Dear Maintainer, *** 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 *** When I search for text in Evince, it finds results but doesn't seem to support navigation to those results. For example, if I search for "thanks to" in this document: http://www.blogs.hss.ed.ac.uk/crag/files/2016/10/algocracy.pdf I get a result, but neither by clicking or double-clicking on the result in the results index pane, nor by clicking on the "next" or "previous" arrows, can I navigate to that result. I have to manually scroll through the document until I reach the (correctly highlighted) text. I've verified this with other documents, and used (for example) xpdf to check that such search navigation is possible in the documents I'm testing with. This *may* be a duplicate of the below bug, but it's worded in a way I can't easily follow: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=586318 Conrad -- System Information: Debian Release: 8.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-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 Init: systemd (via /run/systemd/system) Versions of packages evince depends on: ii evince-common 3.14.1-2+deb8u1 ii gnome-icon-theme-symbolic 3.12.0-1 ii libatk1.0-02.14.0-1 ii libc6 2.19-18+deb8u6 ii libcairo-gobject2 1.14.0-2.1+deb8u1 ii libcairo2 1.14.0-2.1+deb8u1 ii libevdocument3-4 3.14.1-2+deb8u1 ii libevview3-3 3.14.1-2+deb8u1 ii libgdk-pixbuf2.0-0 2.31.1-2+deb8u5 ii libglib2.0-0 2.42.1-1+b1 ii libgtk-3-0 3.14.5-1+deb8u1 ii libnautilus-extension1a3.14.1-2 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-01.36.8-3 ii libsecret-1-0 0.18-1+b1 ii libxml22.9.1+dfsg1-5+deb8u3 ii shared-mime-info 1.3-1 ii zlib1g 1:1.2.8.dfsg-2+b1 Versions of packages evince recommends: ii dbus-x11 1.8.20-0+deb8u1 ii gvfs 1.22.2-1 Versions of packages evince suggests: ii nautilus 3.14.1-2 ii poppler-data 0.4.7-1 ii unrar 1:5.2.7-0.1 -- no debconf information
Bug#834178: gdm3: Password visible as plaintext during gdm3 login
Package: gdm3 Version: 3.14.1-7 Followup-For: Bug #834178 Dear Maintainer, I can confirm this bug, or something closely related: I'd booted my computer but not logged in; after coming back to it the screen had blanked, but I typed in my username and password anyway. As the screen came back up I saw my password visible in plaintext just before the successful login kicked in. Couldn't trivially reproduce unfortunately. Showing login password on-screen is a bit of a dangerous problem. I'll continue to try reproducing, but it's obviously a bit of a Heisenbug unfortunately. Conrad -- System Information: Debian Release: 8.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-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 Init: systemd (via /run/systemd/system) Versions of packages gdm3 depends on: ii accountsservice 0.6.37-3+b1 ii adduser 3.113+nmu3 ii dconf-cli 0.22.0-1 ii dconf-gsettings-backend 0.22.0-1 ii debconf [debconf-2.0] 1.5.56 ii gir1.2-gdm3 3.14.1-7 ii gnome-session [x-session-manager] 3.14.0-2 ii gnome-session-bin 3.14.0-2 ii gnome-settings-daemon 3.14.2-3 ii gnome-shell 3.14.4-1~deb8u1 ii gnome-terminal [x-terminal-emulator] 3.14.1-1+deb8u1 ii gsettings-desktop-schemas 3.14.1-1 ii libaccountsservice0 0.6.37-3+b1 ii libaudit1 1:2.4-1+b1 ii libc6 2.19-18+deb8u4 ii libcanberra-gtk3-00.30-2.1 ii libcanberra0 0.30-2.1 ii libgdk-pixbuf2.0-02.31.1-2+deb8u5 ii libgdm1 3.14.1-7 ii libglib2.0-0 2.42.1-1+b1 ii libglib2.0-bin2.42.1-1+b1 ii libgtk-3-03.14.5-1+deb8u1 ii libpam-modules1.1.8-3.1+deb8u1+b1 ii libpam-runtime1.1.8-3.1+deb8u1 ii libpam-systemd215-17+deb8u4 ii libpam0g 1.1.8-3.1+deb8u1+b1 ii librsvg2-common 2.40.5-1+deb8u2 ii libselinux1 2.3-2 ii libsystemd0 215-17+deb8u4 ii libwrap0 7.6.q-25 ii libx11-6 2:1.6.2-3 ii libxau6 1:1.0.8-1 ii libxdmcp6 1:1.1.1-1+b1 ii libxrandr22:1.4.2-1+b1 ii lsb-base 4.1+Debian13+nmu1 ii metacity [x-window-manager] 1:3.14.3-1 ii mutter [x-window-manager] 3.14.4-1~deb8u1 ii policykit-1 0.105-8 ii ucf 3.0030 ii x11-common1:7.7+7 ii x11-xserver-utils 7.7+3+b1 ii xfce4-session [x-session-manager] 4.10.1-10 ii xfce4-terminal [x-terminal-emulator] 0.6.3-1+b1 ii xfwm4 [x-window-manager] 4.10.1-3 ii xterm [x-terminal-emulator] 312-2 Versions of packages gdm3 recommends: ii at-spi2-core 2.14.0-1 ii desktop-base 8.0.2 ii gnome-icon-theme 3.12.0-1 ii gnome-icon-theme-symbolic 3.12.0-1 ii x11-xkb-utils 7.7+1 ii xserver-xephyr 2:1.16.4-1 ii xserver-xorg 1:7.7+7 ii zenity 3.14.0-1 Versions of packages gdm3 suggests: ii gnome-orca3.14.0-4+deb8u1 ii libpam-gnome-keyring 3.14.0-1+b1 -- debconf information: gdm3/daemon_name: /usr/sbin/gdm3 * shared/default-x-display-manager: lightdm
Bug#800018: s3cmd: sync leaves empty temp file after permission denied error
Package: s3cmd Version: 1.5.0~rc1-2 Severity: normal Tags: upstream Dear Maintainer, On receipt of a permission error during s3cmd sync, a local empty temporary file is left. Would be nice if it was deleted. The particular remote error I'm getting is this one: WARNING: Remote file S3Error: 403 (Forbidden): s3://[blahblahblah] -> [1 of 136] etc. After this, all files which failed to sync because of permission errors seem to have an associated empty temp file left behind, e.g. ".s3cmd.MJ8Peb.tmp". Over repeated syncs, the numbers rapidly mount... Best regards, Conrad -- System Information: Debian Release: 8.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-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 Init: systemd (via /run/systemd/system) Versions of packages s3cmd depends on: ii python-dateutil 2.2-2 pn python:any Versions of packages s3cmd recommends: ii python-magic 1:5.22+15-2 s3cmd suggests no packages. -- debconf-show failed
Bug#788432: evolution: Calendar imports default to Birthhdays Anniversaries calendar
Package: evolution Version: 3.12.9~git20141130.241663-1+b1 Severity: normal Dear Maintainer, Some time over the last few months, Evolution has started to suggest my Contacts/Birthdays Anniversaries calendar as the default when importing events (e.g. .ics file received in email), rather than On This Computer/Personal. I can't find an option in the UI to choose default calendar for import, and all kinds of web searching around terms such as gnome evolution import event default calendar has turned up nothing. To reproduce: - Find a .ics file, or similar. - Run evolution --import foo.ics. - An import dialog pops up describing the event. - Click Next. - The dialog progresses to calendar choice. At this point I'd like it to default to my Personal calendar, but it now defaults to Birthdays. This behaviour is not evident with Evolution 3.4.4 on my laptop (where it still defaults to Personal). Interestingly, on my laptop (which is working ok), if I right-click to choose properties for the two calendars, neither of them has Mark as default calendar checked, while on my desktop (which is doing the wrong thing), Personal has Mark as default calendar checked. The wording of that checkbox is confusing, but as far as I can tell, it actually means This is the default calendar, and unchecking it is in a sense impossible since even if you un- check it, it'll be checked again next time you open the calendar's properties. Nevertheless, changing which one is checked as default seems to have no impact on --import's behaviour. This regression looks as if it should be trivially fixable, but I can't find the fix. Any suggestions? Or do you think this is an upstream problem? Conrad -- System Information: Debian Release: 8.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-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 Init: systemd (via /run/systemd/system) Versions of packages evolution depends on: ii dbus 1.8.18-0+deb8u1 ii debconf [debconf-2.0] 1.5.56 ii evolution-common 3.12.9~git20141130.241663-1 ii evolution-data-server 3.12.9~git20141128.5242b0-2+deb8u2 ii gnome-icon-theme 3.12.0-1 ii libatk1.0-02.14.0-1 ii libc6 2.19-18 ii libcamel-1.2-493.12.9~git20141128.5242b0-2+deb8u2 ii libclutter-gtk-1.0-0 1.6.0-1 ii libecal-1.2-16 3.12.9~git20141128.5242b0-2+deb8u2 ii libedataserver-1.2-18 3.12.9~git20141128.5242b0-2+deb8u2 ii libevolution 3.12.9~git20141130.241663-1+b1 ii libglib2.0-0 2.42.1-1 ii libgtk-3-0 3.14.5-1 ii libical1a 1.0-1.3 ii libnotify4 0.7.6-2 ii libsoup2.4-1 2.48.0-1 ii libwebkitgtk-3.0-0 2.4.8-2 ii libxml22.9.1+dfsg1-5 ii psmisc 22.21-2 Versions of packages evolution recommends: ii bogofilter 1.2.4+dfsg1-3 ii evolution-plugins 3.12.9~git20141130.241663-1+b1 ii spamassassin 3.4.0-6 ii yelp 3.14.1-1 Versions of packages evolution suggests: pn evolution-ews none pn evolution-plugins-experimental none ii gnupg 1.4.18-7 ii network-manager 0.9.10.0-7 -- debconf information: evolution/kill_processes: evolution/needs_shutdown: -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784064: id3v2: Doesn't exit with a failure code on nonexistent file
Package: id3v2 Version: 0.1.12-2.1 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** id3v2 fails when invoked on a nonexistent file, but returns 0 to the shell, so the shell doesn't recognise the failure. Reproduce as follows (for example): id3v2 --track=1/1 nonexistent_file.mp3 Couldn't stat file 'nonexistent_file.mp3' echo $? 0 I'd expect the $? above to be 1 (failure), not 0. Without this scripts that use id3v2 erroneously run past failures. *** End of the template - remove these template lines *** -- System Information: Debian Release: 8.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-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 Init: systemd (via /run/systemd/system) Versions of packages id3v2 depends on: ii libc62.19-18 ii libgcc1 1:4.9.2-10 ii libid3-3.8.3c2a 3.8.3-15 ii libstdc++6 4.9.2-10 ii zlib1g 1:1.2.8.dfsg-2+b1 id3v2 recommends no packages. id3v2 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#766044: gnome-terminal: Custom text/background colour should offer colours from currently selected palette scheme
Package: gnome-terminal Version: 3.14.0-1 Severity: normal Dear Maintainer, * What led up to the situation? - I wanted to use a custom palette and custom text background colours (specifically, the Solarized scheme). * What exactly did you do (or not do) that was effective (or ineffective)? - I went to the Colours tab on Profile preferences, and selected the built-in Solarized *palette* colour scheme. There was an immediate surprise here, in that it didn't change the terminal text and background colours. - Then, under Text and Background Colour, I disabled Use colours from system theme and selected the Built-in theme Solarized dark for text and background. - Unexpectedly this used black as a background colour rather than Solarized's base02 (which I believe is the usual default), so I clicked on Background colour to set it myself. * What was the outcome of this action? - The palette in the colour picker is completely unrelated to the Solarized palette which I selected earlier, which meant I had to separately look up the colour numbers for the Solarized palette, identify base02's RGB code and manually enter that in the background colour picker. * What outcome did you expect instead? - I think it would be appropriate to include the currently selected terminal colour palette when picking text and background colours. - I also think it would be appropriate for palette schemes to automatically select associated text and background schemes, but that's a smaller issue. -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16-2-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 gnome-terminal depends on: ii dconf-gsettings-backend [gsettings-backend] 0.22.0-1 ii gconf-service3.2.6-3 ii gnome-terminal-data 3.14.0-1 ii gsettings-desktop-schemas3.14.0-1 ii libatk1.0-0 2.14.0-1 ii libc62.19-11 ii libcairo-gobject21.12.16-5 ii libcairo21.12.16-5 ii libdconf10.22.0-1 ii libgconf-2-4 3.2.6-3 ii libgdk-pixbuf2.0-0 2.30.8-1+b1 ii libglib2.0-0 2.42.0-2 ii libgtk-3-0 3.14.1-1 ii libnautilus-extension1a 3.14.0-1 ii libpango-1.0-0 1.36.8-2 ii libpangocairo-1.0-0 1.36.8-2 ii libuuid1 2.20.1-5.11 ii libvte-2.91-00.38.0-1 ii libx11-6 2:1.6.2-3 Versions of packages gnome-terminal recommends: ii dbus-x11 1.8.8-2 ii gvfs 1.22.0-1+b1 ii yelp 3.14.0-1 gnome-terminal 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#748211: os-prober: Dangerous failure during kernel upgrade (probed NFS?)
Package: os-prober Version: 1.58 Severity: normal Dear Maintainer, *** Please consider answering these questions, where appropriate *** os-prober can appear to hang, possibly while trying to probe a hung NFS server, and attempts to kill this (typically invoked during kernel upgrade) can leave you with a machine which can't mount drives that it needs to probe, because the kernel upgrade has removed/updated the running kernel's FS modules. I'm not sure what the best way of dealing with this is, but two that occur to me are: - If os-prober hung because it was trying to probe my NFS mount, then should it really be doing that? Does it make sense to os-probe network drives during a kernel upgrade? - If it hung because it was trying to load fuse/ntfs kernel modules which had just been rendered unloadable by updates from the (3.2.0-4 to 3.2.0-4, so far as I can see: same version) partial kernel upgrade, then perhaps os-prober should be run before the existing kernel's modules are replaced? Sequence of events: - I was performing a kernel upgrade as part of a typical aptitude upgrade command. An NFS server that I usually mount (listed as auto,_netdev in /etc/fstab) had failed, so the just-booted system was, at a guess, still trying to mount it in the background, although I'd not noticed this at the time. - The grub configuration update appeared to hang. No error messages, it just stopped part way through the list of installed OSes. It found Linux but stopped before finding Windows. - After a while I killed the upgrade (suspend, kill %1), hoping to work out what was wrong and re-run the upgrade. Subsequent attempts to run dpkg --configure -a, or aptitude reinstall kernel failed due to locked dpkg files. - lsof on the lock files wouldn't terminate. I noticed the hung nfs mount process, killed that and then found and killed the tail of the os-probe process chain. This allowed me to run dpkg --reconfigure and aptitude update/reinstall. - However by this stage my running kernel's modules had been obliterated by the upgrade, and os-prober couldn't load fuse.ko in order to probe the Windows 7 partitions (which aren't mounted by default). - This left me in the somewhat scary situation of knowing I had a partially upgraded kernel, no way of completing the upgrade, and not knowing whether I could safely reboot. - As it turned out, reboot worked and I could then run the reinstall safely. *** End of the template - remove these lines *** -- System Information: Debian Release: 7.5 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages os-prober depends on: ii libc6 2.13-38+deb7u1 os-prober recommends no packages. os-prober 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#682581: xfce4-settings: No way to disable accessibility features?
Package: xfce4-settings Version: 4.8.3-2 Severity: normal Dear Maintainer, I have nothing enabled in xfce4-accessibility-settings, but if I leave my finger on the shift key for a few seconds, Slow Keys activates. I would expect that if Use Slow Keys is not ticked in the accessibility settings dialog, then I should not be able to activate the feature from the keyboard. It looks as if this setting is actually there to turn the feature on immediately (rather than to allow its enablement by pressing shift). Obviously it's perfectly reasonable to have it available by *default*, however there should I think be some way to prevent its activation altogether for those who don't want it. I often pause at the start of sentences with one finger on the shift key, ready for the opening capital letter, so being unable to prevent Slow Keys' activation is a little awkward. Similarly, tapping my finger on the shift key activates sticky keys, and it would be handy to be able to prevent that too. Regards, Conrad -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xfce4-settings depends on: ii libc6 2.13-33 ii libcairo2 1.12.2-2 ii libdbus-1-3 1.6.0-1 ii libexo-1-0 0.6.2-5 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libglib2.0-02.32.3-1 ii libgtk2.0-0 2.24.10-1 ii libnotify4 0.7.5-1 ii libpango1.0-0 1.30.0-1 ii libx11-62:1.5.0-1 ii libxcursor1 1:1.1.13-1 ii libxfce4ui-1-0 4.8.1-1 ii libxfce4util4 4.8.2-1 ii libxfconf-0-2 4.8.1-1 ii libxi6 2:1.6.1-1 ii libxklavier16 5.2.1-1 ii libxrandr2 2:1.3.2-2 ii xfconf 4.8.1-1 Versions of packages xfce4-settings recommends: ii x11-utils 7.7~1 ii xfce4-volumed 0.1.13-3 xfce4-settings suggests no packages. -- debconf-show failed -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682581: Acknowledgement (xfce4-settings: No way to disable accessibility features?)
Argh sorry, this is a known gdm-as-login-manager issue. I only searched xfce-settings's open bug list. Sorry. Conrad -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681982: gnome-terminal: Cursor does not change when unfocused
Package: gnome-terminal Version: 3.4.1.1-1 Severity: important Dear Maintainer, I've recently upgraded to wheezy from stable; in stable, gnome-terminal would change its cursor from a solid box to an empty box when it lost focus. This appears to no longer be the case. Coupled with Gnome 3's disinclination to provide any clear indication as to which window is currently focused (it changes the colour of the window title text, which is at the other end of the screen from where my cursor is most of the time), this makes it very easy to mistakenly think you're focused and start typing into the wrong window. It would be extremely helpful if you could restore the empty box cursor for unfocused windows. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnome-terminal depends on: ii gconf-service 3.2.5-1 ii gnome-terminal-data3.4.1.1-1 ii gsettings-desktop-schemas 3.4.2-1 ii libatk1.0-02.4.0-2 ii libc6 2.13-33 ii libgconf-2-4 3.2.5-1 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libglib2.0-0 2.32.3-1 ii libgtk-3-0 3.4.2-2 ii libice62:1.0.8-2 ii libpango1.0-0 1.30.0-1 ii libsm6 2:1.2.1-2 ii libvte-2.90-9 1:0.32.2-1 ii libx11-6 2:1.5.0-1 Versions of packages gnome-terminal recommends: ii gvfs 1.12.3-1+b1 ii yelp 3.4.2-1 gnome-terminal 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#681682: Acknowledgement (gnome-control-center: uid 1000 ignored in User Accounts; should honour /etc/login.defs UID_MIN)
The machine started honouring UID_MIN after a reboot. Please close, very sorry for wasting your time! Conrad -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681683: Acknowledgement (gdm3: Hardcoded to ignore UID 1000? Should honour UID_MIN from /etc/login.defs.)
The machine started honouring the new UID_MIN value after a reboot. Please close, very sorry for wasting your time! Conrad -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681682: gnome-control-center: uid 1000 ignored in User Accounts; should honour /etc/login.defs UID_MIN
Package: gnome-control-center Version: 1:3.4.2-2 Severity: normal Dear Maintainer, *** Please consider answering these questions, where appropriate *** I've just upgraded to wheezy from stable, and my user no longer appears in the greeter nor in System Settings' User Accounts list. It may be modern policy for Debian that user accounts should not be created below UID 1000, but for account compatibility with a large number of other machines, NFS, Mac OS etc. my UID is 501. After logging in (have to click other and type my username), if I try System Settings-User Accounts, I get a dialogue with My Account and Other Accounts sections; there's nothing under My Account, even though I have clearly logged in and must have an account... This may be an upstream issue, but as far as I can see Gnome fixed this two or three years ago by honouring /etc/login.defs' UID_MIN setting. *** End of the template - remove these lines *** -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') 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 gnome-control-center depends on: ii accountsservice0.6.21-5 ii apg2.2.3.dfsg.1-2 ii desktop-file-utils 0.20-0.1 ii gnome-control-center-data 1:3.4.2-2 ii gnome-desktop3-data3.4.2-1 ii gnome-icon-theme 3.4.0-2 ii gnome-icon-theme-symbolic 3.4.0-2 ii gnome-menus3.4.2-3 ii gnome-settings-daemon 3.4.2-3 ii gsettings-desktop-schemas 3.4.2-1 ii libatk1.0-02.4.0-2 ii libc6 2.13-33 ii libcairo-gobject2 1.12.2-2 ii libcairo2 1.12.2-2 ii libcanberra-gtk3-0 0.28-4 ii libcanberra0 0.28-4 ii libcheese-gtk213.4.2-1 ii libcheese3 3.4.2-1 ii libclutter-1.0-0 1.10.8-1 ii libcogl-pango0 1.10.2-6 ii libcogl9 1.10.2-6 ii libcolord1 0.1.21-1 ii libcomerr2 1.42.4-3 ii libcups2 1.5.3-1 ii libdbus-1-31.6.0-1 ii libdbus-glib-1-2 0.100-1 ii libfontconfig1 2.9.0-6 ii libgcrypt111.5.0-3 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libglib2.0-0 2.32.3-1 ii libgnome-bluetooth10 3.4.1-1 ii libgnome-desktop-3-2 3.4.2-1 ii libgnome-menu-3-0 3.4.2-3 ii libgnomekbd7 3.4.0.2-1 ii libgnutls262.12.20-1 ii libgoa-1.0-0 3.4.2-1 ii libgssapi-krb5-2 1.10.1+dfsg-1 ii libgstreamer0.10-0 0.10.36-1 ii libgtk-3-0 3.4.2-2 ii libgtop2-7 2.28.4-3 ii libjson-glib-1.0-0 0.14.2-1 ii libk5crypto3 1.10.1+dfsg-1 ii libkrb5-3 1.10.1+dfsg-1 ii libnm-glib40.9.4.0-5 ii libnm-gtk0 0.9.4.1-1+b1 ii libnm-util20.9.4.0-5 ii libnotify4 0.7.5-1 ii libpango1.0-0 1.30.0-1 ii libpolkit-gobject-1-0 0.105-1 ii libpulse-mainloop-glib02.0-3 ii libpulse0 2.0-3 ii libsocialweb-client2 0.25.20-2 ii libupower-glib10.9.17-1 ii libwacom2 0.5-1 ii libx11-6 2:1.5.0-1 ii libxcomposite1 1:0.4.3-2 ii libxdamage11:1.1.3-2 ii libxext6 2:1.3.1-2 ii libxfixes3 1:5.0-4 ii libxi6 2:1.6.1-1 ii libxklavier16 5.2.1-1 ii libxml22.8.0+dfsg1-4 ii zlib1g 1:1.2.7.dfsg-13 Versions of packages gnome-control-center recommends: ii cups-pk-helper 0.2.1.2-1 ii gnome-online-accounts 3.4.2-1 ii gnome-session 3.4.2.1-1 ii gnome-user-guide 3.4.2-1 ii iso-codes 3.37-1 ii mesa-utils 8.0.1-2+b3 ii mousetweaks3.4.2-1 ii policykit-1-gnome 0.105-2 Versions of packages gnome-control-center suggests: ii gnome-screensaver 3.4.1-1 ii gstreamer0.10-pulseaudio 0.10.31-3 ii libcanberra-gtk-module0.28-4 ii x11-xserver-utils 7.7~3 -- 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#681683: gdm3: Hardcoded to ignore UID 1000? Should honour UID_MIN from /etc/login.defs.
Package: gdm3 Version: 3.4.1-2 Severity: normal Dear Maintainer, I've just upgraded to wheezy from stable, and my user no longer appears in the greeter; I can still log in by selecting Other and typing my account name. It may be modern policy for Debian that user accounts should not be created below UID 1000, but for account compatibility with a large number of other machines, NFS, Mac OS etc. my normal user account's UID is 501. This may be an upstream issue, but as far as I can see Gnome fixed this two or three years ago by honouring /etc/login.defs' UID_MIN setting. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') 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 gdm3 depends on: ii accountsservice 0.6.21-5 ii adduser 3.113+nmu3 ii dconf-gsettings-backend 0.12.1-2 ii dconf-tools 0.12.1-2 ii debconf [debconf-2.0] 1.5.44 ii dpkg1.16.4.3 ii gir1.2-freedesktop 1.32.1-1 ii gir1.2-glib-2.0 1.32.1-1 ii gnome-session [x-session-manager] 3.4.2.1-1 ii gnome-session-bin 3.4.2.1-1 ii gnome-session-fallback [x-session-manager] 3.4.2.1-1 ii gnome-settings-daemon 3.4.2-3 ii gnome-terminal [x-terminal-emulator]3.4.1.1-1 ii gsettings-desktop-schemas 3.4.2-1 ii libaccountsservice0 0.6.21-5 ii libatk1.0-0 2.4.0-2 ii libattr11:2.4.46-8 ii libaudit0 1:1.7.18-1.1 ii libc6 2.13-33 ii libcairo-gobject2 1.12.2-2 ii libcairo2 1.12.2-2 ii libcanberra-gtk3-0 0.28-4 ii libcanberra00.28-4 ii libdbus-1-3 1.6.0-1 ii libdbus-glib-1-20.100-1 ii libfontconfig1 2.9.0-6 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libglib2.0-02.32.3-1 ii libglib2.0-bin 2.32.3-1 ii libgtk-3-0 3.4.2-2 ii libpam-modules 1.1.3-7.1 ii libpam-runtime 1.1.3-7.1 ii libpam0g1.1.3-7.1 ii libpango1.0-0 1.30.0-1 ii librsvg2-common 2.36.1-1 ii libselinux1 2.1.9-5 ii libupower-glib1 0.9.17-1 ii libwrap07.6.q-23 ii libx11-62:1.5.0-1 ii libxau6 1:1.0.7-1 ii libxdmcp6 1:1.1.1-1 ii libxklavier16 5.2.1-1 ii libxrandr2 2:1.3.2-2 ii lsb-base4.1+Debian7 ii lxsession [x-session-manager] 0.4.6.1-3 ii metacity [x-window-manager] 1:2.34.3-2 ii policykit-1-gnome 0.105-2 ii sawfish [x-window-manager] 1:1.5.3-2.1+b1 ii twm [x-window-manager] 1:1.0.6-1 ii upower 0.9.17-1 ii x11-common 1:7.7+1 ii x11-xserver-utils 7.7~3 ii xterm [x-terminal-emulator] 278-1 Versions of packages gdm3 recommends: ii desktop-base 7.0.0 ii gnome-icon-theme 3.4.0-2 ii libatk-adaptor [at-spi] 2.5.3-1 ii x11-xkb-utils7.7~1 ii xserver-xephyr 2:1.12.1.902-1 ii xserver-xorg 1:7.7+1 ii zenity 3.4.0-2 Versions of packages gdm3 suggests: ii gnome-mag 1:0.16.3-1 ii gnome-orca3.4.2-2 ii gnome-shell 3.4.1-8 pn gok none ii libpam-gnome-keyring 3.4.1-4 -- debconf information: * shared/default-x-display-manager: gdm3 gdm3/daemon_name: /usr/sbin/gdm3 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#657666: w3m: -dump -o display_link_number=1 lists links in slightly random order
Package: w3m
Version: 0.5.3-5
Severity: normal
Tags: patch
Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
I recently discovered w3m's -dump -o display_link_number=1 options,
and find them really useful. One minor niggle is that the links are
actually listed in an order quite close to, but not the same as, the
number that's displayed. So for example for one document I have, links
1-10 are presented in the order 1-7,9,10,8 in the References list at the
end of the dump. I attach a patch which sorts them according to number.
*** End of the template - remove these lines ***
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.1.0-1-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 w3m depends on:
ii libbsd0 0.3.0-1
ii libc62.13-24
ii libgc1c2 1:7.1-8
ii libgpm2 1.20.4-4
ii libssl1.0.0 1.0.0g-1
ii libtinfo55.9-4
ii zlib1g 1:1.2.3.4.dfsg-3
Versions of packages w3m recommends:
ii ca-certificates 20111211
Versions of packages w3m suggests:
pn man-db2.6.0.2-3
pn menu 2.1.46
pn migemonone
pn mime-support 3.51-1
pn w3m-elnone
pn w3m-img none
-- no debconf information
Description: Sort anchors by sequence number in -dump.
See above.
.
w3m (0.5.3-5.1) unstable; urgency=low
.
* Non-maintainer upload.
* Sort anchors by sequence number in -dump.
Author: Conrad J.C. Hughes (for Debian package stuff) debb...@xrad.org
---
The information above should follow the Patch Tagging Guidelines, please
checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here
are templates for supplementary fields that you might want to add:
Origin: vendor|upstream|other, url of original patch
Bug: url in upstream bugtracker
Bug-Debian: http://bugs.debian.org/bugnumber
Bug-Ubuntu: https://launchpad.net/bugs/bugnumber
Forwarded: no|not-needed|url proving that it has been forwarded
Reviewed-By: name and email of someone who approved the patch
Last-Update: -MM-DD
--- w3m-0.5.3.orig/main.c
+++ w3m-0.5.3/main.c
@@ -1258,6 +1258,12 @@ dump_extra(Buffer *buf)
#endif
}
+static int
+cmp_anchor_hseq(const void *a, const void *b)
+{
+return (*((const Anchor **) a))-hseq - (*((const Anchor **) b))-hseq;
+}
+
static void
do_dump(Buffer *buf)
{
@@ -1278,18 +1284,23 @@ do_dump(Buffer *buf)
int i;
saveBuffer(buf, stdout, FALSE);
if (displayLinkNumber buf-href) {
+ int nanchor = buf-href-nanchor;
printf(\nReferences:\n\n);
- for (i = 0; i buf-href-nanchor; i++) {
- ParsedURL pu;
- static Str s = NULL;
- if (buf-href-anchors[i].slave)
+ Anchor **in_order = New_N(Anchor *, buf-href-nanchor);
+ for (i = 0; i nanchor; i++)
+ in_order[i] = buf-href-anchors + i;
+ qsort(in_order, nanchor, sizeof(Anchor *), cmp_anchor_hseq);
+ for (i = 0; i nanchor; i++) {
+ ParsedURL pu;
+ static Str s = NULL;
+ if (in_order[i]-slave)
continue;
- parseURL2(buf-href-anchors[i].url, pu, baseURL(buf));
- s = parsedURL2Str(pu);
- if (DecodeURL)
+ parseURL2(in_order[i]-url, pu, baseURL(buf));
+ s = parsedURL2Str(pu);
+ if (DecodeURL)
s = Strnew_charp(url_unquote_conv
(s-ptr, Currentbuf-document_charset));
- printf([%d] %s\n, buf-href-anchors[i].hseq + 1, s-ptr);
+ printf([%d] %s\n, in_order[i]-hseq + 1, s-ptr);
}
}
}
Bug#657666: Acknowledgement (w3m: -dump -o display_link_number=1 lists links in slightly random order)
By the way, I didn't look into W3M's memory management terribly carefully. Since it appears to use a garbage collector, I assumed that there was no need to free in_order, but I do notice references to a GC_free function: perhaps I should call GC_free(in_order) after all? Regards, Conrad -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#654575: sound-juicer: Retrieves impossible track listings
Package: sound-juicer Version: 2.32.0-1 Severity: normal Dear Maintainer, *** Please consider answering these questions, where appropriate *** Sound Juicer can retrieve track listings that are impossible for the CD it's looking at. For example, with the re-release of CAN's Tago Mago with a bonus live CD (disc IDs SmXL4f5V4NvTIQ6gcmnkAY4P8DU- and PAjsiFGgheQLNdPwBAW2iJaC_k4- on MusicBrainz, link below), insertion of either CD (seven tracks and three tracks respectively) can retrieve a single *ten*-track listing comprising both track lists, concatenated. This listing clearly isn't appropriate to either individually, unless there's some way for it to be separated into two parts. It would seem appropriate for Sound Juicer to sanity check the results from disc ID queries and ignore those which just don't make sense. Certainly, being presented with ten tracks for a three-track CD seems likely to result in trouble. http://musicbrainz.org/release/d0154297-5df3-4885-9a26-9d337b27218d/discids Regards, Conrad *** End of the template - remove these lines *** -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-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 sound-juicer depends on: ii gconf2 2.32.4-1 ii gstreamer0.10-plugins-base 0.10.35-1 ii gstreamer0.10-plugins-good 0.10.30-2.1 ii libatk1.0-0 2.2.0-2 ii libbrasero-media0 2.30.3-3 ii libc6 2.13-23 ii libcanberra-gtk00.28-3 ii libdbus-glib-1-20.98-1 ii libgconf2-4 2.32.4-1 ii libglib2.0-02.28.6-1 ii libgnome-media0 2.30.0-1 ii libgstreamer0.10-0 0.10.35-1 ii libgtk2.0-0 2.24.8-2 ii libmusicbrainz3-6 3.0.2-2 ii libpango1.0-0 1.29.4-2 Versions of packages sound-juicer recommends: ii eject 2.1.5+deb1+cvs20081104-9 Versions of packages sound-juicer suggests: ii brasero 2.30.3-3 ii gstreamer0.10-lamenone ii gstreamer0.10-plugins-really-bad none ii gstreamer0.10-plugins-ugly0.10.18-3+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#632892: tcsh: Race condition with savehist merge (possible patch included)
Package: tcsh
Version: 6.17.02-4.1
Severity: normal
Tags: patch
An acknowleged problem with tcsh's savehist merge feature is that it
doesn't operate atomically, and so may corrupt the history file if
many shells exit at once, such as will happen when logging out of a
gnome session with many tcsh terminals open. This became a recurrent
problem for me recently.
I include a possible patch to deal with this: creating and locking a
.history.lock file during savehist merge operations. After applying
the patch you can activate the feature by adding lock to the savehist
value:
set savehist=(999 merge lock)
As currenly implemented, (999 lock) will be ignored, as will (999 lock
merge). It has to be (number merge lock).
I've used fcntl in order to have some hope that this works for
NFS-mounted home directories, but I've no idea whether its use could
introduce portability problems --- I've only tried it out on my amd64
Debian Linux system, where it *appears* to work. Hope it proves
useful.
Regards,
Conrad
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.39-2-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 tcsh depends on:
ii libc6 2.13-7 Embedded GNU C Library: Shared lib
ii libncurses5 5.9-1 shared libraries for terminal hand
tcsh recommends no packages.
tcsh suggests no packages.
-- no debconf information
diff -rc tcsh-6.17.02~/debian/changelog tcsh-6.17.02/debian/changelog
*** tcsh-6.17.02~/debian/changelog 2011-07-06 19:20:17.0 +0100
--- tcsh-6.17.02/debian/changelog 2011-07-06 19:20:36.428843121 +0100
***
*** 1,3
--- 1,11
+ tcsh (6.17.02-4.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Add 'lock' option to savehist merge, so it doesn't corrupt the history
+ when you log out of X with multiple shells open.
+
+ -- Conrad J.C. Hughes (for Debian package stuff) debb...@xrad.org Wed, 06 Jul 2011 19:20:30 +0100
+
tcsh (6.17.02-4) unstable; urgency=high
* new maintainer Closes: #592093
diff -rc tcsh-6.17.02~/sh.decls.h tcsh-6.17.02/sh.decls.h
*** tcsh-6.17.02~/sh.decls.h 2010-05-12 16:01:52.0 +0100
--- tcsh-6.17.02/sh.decls.h 2011-07-06 19:20:39.336895138 +0100
***
*** 285,290
--- 285,291
extern void xclose (int);
extern void xclosedir (DIR *);
extern int xcreat (const char *, mode_t);
+ extern int xlockfcntl(int, int, struct flock *);
extern struct group *xgetgrgid (gid_t);
extern struct passwd *xgetpwnam (const char *);
extern struct passwd *xgetpwuid (uid_t);
diff -rc tcsh-6.17.02~/sh.hist.c tcsh-6.17.02/sh.hist.c
*** tcsh-6.17.02~/sh.hist.c 2010-05-12 17:26:26.0 +0100
--- tcsh-6.17.02/sh.hist.c 2011-07-06 19:20:39.336895138 +0100
***
*** 1214,1219
--- 1214,1241
}
}
+ /* Bundle lock file descriptor and path name together for lockfile_cleanup().
+ */
+ struct lockfile {
+ int fd;
+ Char *path;
+ };
+
+ /* Close and unlink lock file and free its path.
+ */
+ static void
+ lockfile_cleanup(void *v_description)
+ {
+ struct lockfile *description = v_description;
+ if (description-fd != -1) {
+ /* Unlink while we have it open to eliminate race conditions, not that I
+* guess it matters. May cause trouble under NT? */
+ unlink(short2str(description-path));
+ xclose(description-fd);
+ }
+ xfree(description-path);
+ }
+
/* Save history before exiting the shell. */
void
rechist(Char *fname, int ref)
***
*** 1221,1226
--- 1243,1249
Char*snum;
int fp, ftmp, oldidfds;
struct varent *shist;
+ struct lockfile lock_info;
static Char *dumphist[] = {STRhistory, STRmhT, 0, 0};
if (fname == NULL !ref)
***
*** 1267,1272
--- 1290,1310
didfds = 0;
if ((shist = adrof(STRsavehist)) != NULL shist-vec != NULL)
if (shist-vec[1] eq(shist-vec[1], STRmerge)) {
+ if (shist-vec[2] eq(shist-vec[2], STRlock)) {
+ lock_info.path = Strspl(fname, STRdotlock);
+ lock_info.fd = xcreat(short2str(lock_info.path), 0600);
+ if (lock_info.fd != -1) {
+ struct flock lock_details;
+ lock_details.l_type = F_WRLCK;
+ lock_details.l_whence = SEEK_SET;
+ lock_details.l_start = 0;
+ lock_details.l_len = 0; /* Whole file */
+ /* If it fails --- well, we tried... */
+ (void) xlockfcntl(lock_info.fd, F_SETLKW, lock_details);
+ }
+ /* Free the path, and if appropriate closeunlink the file. */
+ cleanup_push(lock_info
