Bug#1006477: Broken firmware
> So, my conclusion is that there is something specific to the debian kernels > that is breaking this USB ethernet card. The IOMMU error is most likely caused by a bug in the VL805 firmware. It happens with the Debian kernel (and not mainline) as Debian patches the kernel to enable IOMMU by default. The updated VL805 firmware apparently fixes the bug, it can be installed using the VIA Windows tool (this did not work for me), or you can just turn off IOMMU.
Bug#1041114: sox error and audio glitch when -t not specified and libsox-fmt-pulse is not installed
Package: sox Version: 14.4.2+git20190427-3.5 Severity: normal Dear Maintainer, When `-t` is not specified then sox attempts to probe the audio driver as described at https://groups.google.com/g/linux.debian.bugs.dist/c/jCqdwFWPUKk/m/xi1AThVtMwkJ According to the list in that discussion, pulseaudio is the first driver to be probed on Linux. If libsox-fmt-pulse is not installed, then the probe fails with the error `play WARN alsa: can't encode 0-bit Unknown or not applicable`, and there is an audible pop glitch before the actual audio is played. $ play -t raw -r 48k -e signed -b 16 -c 1 dummy play WARN alsa: can't encode 0-bit Unknown or not applicable (note libsox-fmt-pulse was not installed by default on my system, the alsa driver was, so this warning and audio glitch would occur every time by default) -- System Information: Debian Release: 12.0 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.19.0-1-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages sox depends on: ii libc62.36-9 ii libsox-fmt-alsa 14.4.2+git20190427-3.5 ii libsox-fmt-base 14.4.2+git20190427-3.5 ii libsox3 14.4.2+git20190427-3.5 sox recommends no packages. Versions of packages sox suggests: pn libsox-fmt-all -- no debconf information
Bug#1039970: xserver-xorg-video-amdgpu debian patch downgrades ChangeLog
Package: xserver-xorg-video-amdgpu Version: 23.0.0-1 Small issue but I noticed that `apt-get source xserver-xorg-video-amdgpu` applies a patch (xserver-xorg-video-amdgpu_23.0.0-1.diff.gz) which downgrades the original ChangeLog from 23.0.0 to 19.1.0, e.g.: +++ xserver-xorg-video-amdgpu-23.0.0/ChangeLog @@ -1,697 +1,3 @@ -commit 7025aefcdf9673665588cf291c5d71beb39cce89 -Author: Shashank Sharma -Date: Wed Feb 22 18:00:23 2023 +0100 - -Bump version for the 23.0.0 release - -This release includes some bug fixes. - -Signed-off-by: Shashank Sharma - ... After the patch, is applied: $ head -n5 ChangeLog commit b467d2569a003da05ad222b0dc095bee5eec450a Author: Michel Dänzer Date: Fri Oct 11 17:10:10 2019 +0200 Bump version for the 19.1.0 release
Bug#994217:
According to stackoverflow, the fix is a small commit: https://stackoverflow.com/questions/66636441/pdf2image-library-failing-to-read-pdf-signed-using-docusign https://gitlab.freedesktop.org/poppler/poppler/-/merge_requests/749/diffs?commit_id=4f478daa6a9734b8f269a6586bdce2909844bb6f So perhaps this doesn't require a new version of poppler.
Bug#994217: poppler will not work with PDFs from docusign
Package: libpoppler102 Version: 20.09.0-3.1 Severity: normal Tags: upstream Dear Maintainer, Upstream says "I can confirm that 20.09.0 fails and 21.09.0 works. Please update :)" : https://gitlab.freedesktop.org/poppler/poppler/-/issues/1140
Bug#980975: cups error: Failed to create /var/spool/cups/tmp/.hplip
> However, the content is perplexing. I do not have Python or coding > skills but, looking at HPLIP's os_utils.py, I find Sorry, you are right, I thought I hadn't installed hplip but it is installed due to a dependency. The hpfax/hplip error appears when plugging in a USB printer: Jan 27 11:49:15 debian kernel: usb 3-1.4: new full-speed USB device number 12 using xhci_hcd Jan 27 11:49:18 debian kernel: usb 3-1.4: new high-speed USB device number 13 using xhci_hcd Jan 27 11:49:18 debian kernel: usb 3-1.4: New USB device found, idVendor=04a9, idProduct=26da, bcdDevice= 1.00 Jan 27 11:49:18 debian kernel: usb 3-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Jan 27 11:49:18 debian kernel: usb 3-1.4: Product: Canon CAPT USB Device Jan 27 11:49:18 debian kernel: usb 3-1.4: Manufacturer: Canon Jan 27 11:49:18 debian kernel: usb 3-1.4: SerialNumber: B296NEYm Jan 27 11:49:18 debian kernel: usblp 3-1.4:1.0: usblp0: USB Bidirectional printer dev 13 if 0 alt 0 proto 2 vid 0x04A9 pid 0x26DA Jan 27 11:49:18 debian systemd[1]: Started Configure Plugged-In Printer. Jan 27 11:49:18 debian udev-configure-printer[10637]: add usb-003-013 Jan 27 11:49:19 debian udev-configure-printer[10637]: device devpath is /devices/pci:00/:00:14.0/usb3/3-1/3-1.4 Jan 27 11:49:19 debian udev-configure-printer[10637]: MFG:Canon MDL:LBP3010/LBP3018/LBP3050 SERN:- serial:B296NEYm Jan 27 11:49:24 debian hpfax[10666]: [10666]: error: Failed to create /var/spool/cups/tmp/.hplip Jan 27 11:49:24 debian udev-configure-printer[10637]: no corresponding CUPS device found Jan 27 11:49:24 debian systemd[1]: configure-printer@usb-003-013.service: Succeeded.
Bug#980973: Cups attempts to probe, configure unsupported Canon USB printers
On Tue, 26 Jan 2021 at 13:44, Till Kamppeter wrote: > > Please report this to CUPS upstream at > > https://github.com/OpenPrinting/cups > > Note trhat CUPS is not maintained at Apple any more but at OpenPrinting now. > > We need the USB IDs (VID/PID) of all affected devices, at least of as > many devices as possible. > Ok I've compiled a USB ID list and opened https://github.com/OpenPrinting/cups/issues/80
Bug#980975: cups error: Failed to create /var/spool/cups/tmp/.hplip
Package: cups Version: 2.3.3op1-7 "Failed to create /var/spool/cups/tmp/.hplip" appears in the journal on bullseye. I am not using hplip, and have never installed it.
Bug#980974: apparmor blocks cups backend outgoing network connections
Package: cups Version: 2.3.3op1-7 After upgrading to bullseye, TCP connections from cupsd to localhost appeared to be blocked: Jan 23 23:39:29 debian audit[2172]: AVC apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=2172 comm="cupsd" capability=12 capname="net_admin" Jan 23 23:39:29 debian systemd[1]: Started CUPS Scheduler. Jan 23 23:39:29 debian kernel: kauditd_printk_skb: 10 callbacks suppressed Jan 23 23:39:29 debian kernel: audit: type=1400 audit(1611445169.589:22): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=2172 comm="cupsd" capability=12> Jan 23 23:39:29 debian systemd[1]: Started Make remote CUPS printers available locally. Jan 23 23:39:29 debian audit[2174]: AVC apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=2174 comm="cups-browsed" capability=23 capname="sys_nice" I worked around this with `aa-complain cupsd`, `aa-complain cups-browsed`, but I would guess that this should work without modifications, unless this (TCP connections from cupsd to backend driver) is considered non-standard usage?
Bug#980973: Cups attempts to probe, configure unsupported Canon USB printers
Package: cups Version: 2.3.3op1-7 Cups does not support Canon CAPT USB printers (this requires a proprietary driver which uses /dev/usb/lp0), but these printers are not blacklisted, so when one is plugged in, cups sets up a new, non-functional printer, and probes the USB device, the kernel logs as a USB disconnect, and disrupts operation of the Canon driver. Running lpstat also seems to do some probe and cause a USB device disconnect. The kernel logs: Jan 23 23:45:29 debian kernel: usblp0: removed It appears the fix would be to add CAPT printers to /usr/share/cups/usb/org.cups.usb-quirks as so: # Canon, Inc. LBP3010/LBP3018/LBP3050 Printer 0x04a9 0x26da blacklist etc.
Bug#980971: ghostscript lacks opvp support, breaks some printer backends
Package: ghostscript Version: 9.53.3~dfsg-6 As reported at https://bugzilla.redhat.com/show_bug.cgi?id=1899885 ghostscript upstream temporarily disabled opvp support, breaking Canon CAPT/UFR printer driver support in cups. This change has since been reverted upstream. I can confirm that the patch at https://git.ghostscript.com/?p=ghostpdl.git;a=patch;h=c6ce09aa5c9e does restore Canon printer functionality in bullseye.
Bug#864684: awscli fails with Regions that only support Signature Version 4
Package: awscli
Version: 1.4.2-1
Severity: important
awscli works on older AWS regions but fails on newer regions that require
version 4 signatures:
$ /usr/bin/aws --region eu-west-2 ec2 describe-instances
A client error (AuthFailure) occurred when calling the DescribeInstances
operation: AWS was not able to validate the provided access credentials
$ /usr/bin/aws --region eu-west-1 ec2 describe-instances
{
"Reservations": []
}
Relevant: https://forums.aws.amazon.com/message.jspa?messageID=578908
Bug#818480: libmlt memory corruption crashes openshot
Package: libmlt6 Version: 0.9.2-2 Severity: important Trying to use openshot to put together a simple sequence of videos but it crashes or hangs after a few minutes. It seems to be when changes are made and the timeline cursor is reposioned. This pretty much makes openshot unusable. Valgrind shows repeated memory corruption during this period resulting from free in mlt_frame_close: ==25301== Invalid write of size 4 ==25301==at 0x241E76F2: av_frame_unref (in /usr/lib/x86_64-linux-gnu/libavutil.so.54.3.0) ==25301==by 0x23341907: avcodec_decode_video2 (in /usr/lib/x86_64-linux-gnu/libavcodec.so.56.1.0) ==25301==by 0x28F6624D: producer_get_image (in /usr/lib/x86_64-linux-gnu/mlt/libmltavformat.so) ==25301==by 0x1015E356: mlt_frame_get_image (in /usr/lib/x86_64-linux-gnu/libmlt.so.0.9.2) ==25301==by 0x1C3E7DD4: filter_get_image (in /usr/lib/x86_64-linux-gnu/mlt/libmltxine.so) ==25301==by 0x1015E356: mlt_frame_get_image (in /usr/lib/x86_64-linux-gnu/libmlt.so.0.9.2) ==25301==by 0x135EC105: get_image (in /usr/lib/x86_64-linux-gnu/mlt/libmltcore.so) ==25301==by 0x1015E356: mlt_frame_get_image (in /usr/lib/x86_64-linux-gnu/libmlt.so.0.9.2) ==25301==by 0x135EADAD: filter_get_image (in /usr/lib/x86_64-linux-gnu/mlt/libmltcore.so) ==25301==by 0x1015E356: mlt_frame_get_image (in /usr/lib/x86_64-linux-gnu/libmlt.so.0.9.2) ==25301==by 0x135F03F0: filter_get_image (in /usr/lib/x86_64-linux-gnu/mlt/libmltcore.so) ==25301==by 0x1015E356: mlt_frame_get_image (in /usr/lib/x86_64-linux-gnu/libmlt.so.0.9.2) ==25301== Address 0x2a585ea0 is 576 bytes inside a block of size 584 free'd ==25301==at 0x4C29E90: free (vg_replace_malloc.c:473) ==25301==by 0x28F61CD3: producer_avformat_close (in /usr/lib/x86_64-linux-gnu/mlt/libmltavformat.so) ==25301==by 0x10177B4D: cache_object_close (in /usr/lib/x86_64-linux-gnu/libmlt.so.0.9.2) ==25301==by 0x10177BF7: mlt_cache_item_close (in /usr/lib/x86_64-linux-gnu/libmlt.so.0.9.2) ==25301==by 0x101624F8: mlt_property_close (in /usr/lib/x86_64-linux-gnu/libmlt.so.0.9.2) ==25301==by 0x1016473F: mlt_properties_close (in /usr/lib/x86_64-linux-gnu/libmlt.so.0.9.2) ==25301==by 0x1015DD6B: mlt_frame_close (in /usr/lib/x86_64-linux-gnu/libmlt.so.0.9.2) ==25301==by 0x101624F8: mlt_property_close (in /usr/lib/x86_64-linux-gnu/libmlt.so.0.9.2) ==25301==by 0x1016473F: mlt_properties_close (in /usr/lib/x86_64-linux-gnu/libmlt.so.0.9.2) ==25301==by 0x1015DD6B: mlt_frame_close (in /usr/lib/x86_64-linux-gnu/libmlt.so.0.9.2) ==25301==by 0x1796A41E: video_thread (in /usr/lib/x86_64-linux-gnu/mlt/libmltsdl.so) ==25301==by 0x4E3D0A3: start_thread (pthread_create.c:309) ==25301== ==25301== Invalid write of size 8 ==25301==at 0x241E76C6: av_frame_unref (in /usr/lib/x86_64-linux-gnu/libavutil.so.54.3.0) ==25301==by 0x23341907: avcodec_decode_video2 (in /usr/lib/x86_64-linux-gnu/libavcodec.so.56.1.0) ==25301==by 0x28F6624D: producer_get_image (in /usr/lib/x86_64-linux-gnu/mlt/libmltavformat.so) ==25301==by 0x1015E356: mlt_frame_get_image (in /usr/lib/x86_64-linux-gnu/libmlt.so.0.9.2) ==25301==by 0x1C3E7DD4: filter_get_image (in /usr/lib/x86_64-linux-gnu/mlt/libmltxine.so) ==25301==by 0x1015E356: mlt_frame_get_image (in /usr/lib/x86_64-linux-gnu/libmlt.so.0.9.2) ==25301==by 0x135EC105: get_image (in /usr/lib/x86_64-linux-gnu/mlt/libmltcore.so) ==25301==by 0x1015E356: mlt_frame_get_image (in /usr/lib/x86_64-linux-gnu/libmlt.so.0.9.2) ==25301==by 0x135EADAD: filter_get_image (in /usr/lib/x86_64-linux-gnu/mlt/libmltcore.so) ==25301==by 0x1015E356: mlt_frame_get_image (in /usr/lib/x86_64-linux-gnu/libmlt.so.0.9.2) ==25301==by 0x135F03F0: filter_get_image (in /usr/lib/x86_64-linux-gnu/mlt/libmltcore.so) ==25301==by 0x1015E356: mlt_frame_get_image (in /usr/lib/x86_64-linux-gnu/libmlt.so.0.9.2) ==25301== Address 0x2a585cc0 is 96 bytes inside a block of size 584 free'd ==25301==at 0x4C29E90: free (vg_replace_malloc.c:473) ==25301==by 0x28F61CD3: producer_avformat_close (in /usr/lib/x86_64-linux-gnu/mlt/libmltavformat.so) ==25301==by 0x10177B4D: cache_object_close (in /usr/lib/x86_64-linux-gnu/libmlt.so.0.9.2) ==25301==by 0x10177BF7: mlt_cache_item_close (in /usr/lib/x86_64-linux-gnu/libmlt.so.0.9.2) ==25301==by 0x101624F8: mlt_property_close (in /usr/lib/x86_64-linux-gnu/libmlt.so.0.9.2) ==25301==by 0x1016473F: mlt_properties_close (in /usr/lib/x86_64-linux-gnu/libmlt.so.0.9.2) ==25301==by 0x1015DD6B: mlt_frame_close (in /usr/lib/x86_64-linux-gnu/libmlt.so.0.9.2) ==25301==by 0x101624F8: mlt_property_close (in /usr/lib/x86_64-linux-gnu/libmlt.so.0.9.2) ==25301==by 0x1016473F: mlt_properties_close (in /usr/lib/x86_64-linux-gnu/libmlt.so.0.9.2) ==25301==by 0x1015DD6B: mlt_frame_close (in /usr/lib/x86_64-linux-gnu/libmlt.so.0.9.2) ==25301==by 0x1796A41E: video_thread (in
Bug#542899:
Does anyone have any comments on the man pages? If the pages are ok, can someone add them to the Debian package?
Bug#813907: fc-cache ignores .pcf files unless they are .gz gzip compressed
Package: fontconfig Version: 2.11.0-6.3 Severity: normal Dear Maintainer, .pcf font is not detected. This used to work, don't know why it doesn't now. There are no errors, and the font is correctly detected after being compressed with gzip. $ dpkg-reconfigure fontconfig-config Enable bitmap fonts. $ wget -q -O - http://pts-mini-gpl.googlecode.com/svn/trunk/fonts/fixedsc.tgz | (cd / && tar xzv) $ fc-cache -fv /usr/local/share/fonts/fixedsc /usr/local/share/fonts/fixedsc: caching, new cache contents: 0 fonts, 0 dirs /usr/local/share/fonts/fixedsc: caching, new cache contents: 0 fonts, 0 dirs /var/cache/fontconfig: cleaning cache directory /root/.cache/fontconfig: not cleaning non-existent cache directory /root/.fontconfig: not cleaning non-existent cache directory fc-cache: succeeded 0 fonts? And no errors or warnings? $ ls /usr/local/share/fonts/fixedsc fixedsc_6x13.pcf fixedsc_6x13_bold.pcf $ gzip /usr/local/share/fonts/fixedsc/* $ fc-cache -fv /usr/local/share/fonts/fixedsc /usr/local/share/fonts/fixedsc: caching, new cache contents: 2 fonts, 0 dirs /usr/local/share/fonts/fixedsc: caching, new cache contents: 2 fonts, 0 dirs /var/cache/fontconfig: cleaning cache directory /root/.cache/fontconfig: not cleaning non-existent cache directory /root/.fontconfig: not cleaning non-existent cache directory fc-cache: succeeded But 2 fonts are detected when gzipped?
Bug#782011: [Pkg-xfce-devel] Bug#782011:
On 22 August 2015 at 06:31, Yves-Alexis Perez cor...@debian.org wrote: But I personnaly don't see why lightdm should specifically log to journalct actually. Maybe it should log stuff to syslog directly, but I don't think depending on journalctl is the right thing to do. That's what I meant. At the moment, lightdm opens and manages log files directly. It would be better to use syslog (or even stdout/stderr) so it the logs are incorporated in to the system journal. e.g. http://0pointer.de/blog/projects/journal-submit.html
Bug#786784: python-urllib3: AttributeError: 'module' object has no attribute 'PROTOCOL_SSLv3'
Package: python-urllib3 Version: 1.9.1-3 Severity: serious $ python Python 2.7.9 (default, Mar 1 2015, 12:57:24) [GCC 4.9.2] on linux2 Type help, copyright, credits or license for more information. import requests Traceback (most recent call last): File stdin, line 1, in module File requests/__init__.py, line 53, in module from urllib3.contrib import pyopenssl File urllib3/contrib/pyopenssl.py, line 70, in module ssl.PROTOCOL_SSLv3: OpenSSL.SSL.SSLv3_METHOD, AttributeError: 'module' object has no attribute 'PROTOCOL_SSLv3' -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#786784: python-urllib3: AttributeError: 'module' object has no attribute 'PROTOCOL_SSLv3'
On 25 May 2015 at 16:11, Daniele Tricoli er...@mornie.org wrote: Are you using the packaged version on urllib3? If yes there is something really strange since I patched it as explained here: Sorry for the bogus bug report (I already closed it as invalid) - it turned out Python was picking up an older install of urllib3 on this system, which still had the bug. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782973: ifup wlanX fails for x0 because NetworkManager starts wpa_supplicant on unmanaged interface
Package: network-manager Version: 0.9.10.0-7 Severity: normal ifup fails for a wlan interface defined in /etc/network/interfaces when the interface is not wlan0 with wpa_supplicant: /sbin/wpa_supplicant daemon failed to start - wlan5 is defined in /etc/network/interfaces (there is no wlan0) - NetworkManager is running - USB wifi inserted and driver loaded - kernel driver creates network interface on wlan0 - systemd-udevd: renames network interface wlan0 to wlan5 - NetworkManager sets state unavailable (reason 'managed') - NetworkManager starts wpa_supplicant - NetworkManager sets state unmanaged (reason 'unmanaged') - wpa_supplicant is still running - `ifup wlan5` will now fail with: wpa_supplicant: /sbin/wpa_supplicant daemon failed to start because wpa_supplicant is already running. - This does not occur if wlan0 is unmanaged by creating a dummy entry in /etc/network/interfaces - ifup will work if NetworkManager is stopped and wpa_supplicant is killed Abbreviated log oddness: Apr 19 16:34:38 debian NetworkManager[2871]: info (wlan5): device state change: unmanaged - unavailable (reason 'managed') [10 20 2] Apr 19 16:34:38 debian dbus[2894]: [system] Activating via systemd: service name='fi.w1.wpa_supplicant1' unit='wpa_supplicant.service' Apr 19 16:34:38 debian NetworkManager[2871]: info (wlan5): device state change: unavailable - unmanaged (reason 'unmanaged') [20 10 3] This has been tested with two different wifi devices and the behaviour is the same. --- journal: Apr 19 16:34:37 debian kernel: usb 1-1: reset high-speed USB device number 2 using xhci_hcd Apr 19 16:34:37 debian kernel: mt7601u 1-1:1.0: ASIC revision: 76010001 MAC revision: 76010500 Apr 19 16:34:37 debian kernel: mt7601u 1-1:1.0: Warning: unsupported EEPROM version 0d Apr 19 16:34:37 debian kernel: mt7601u 1-1:1.0: EEPROM ver:0d fae:00 Apr 19 16:34:38 debian kernel: ieee80211 phy2: Selected rate control algorithm 'minstrel_ht' Apr 19 16:34:38 debian kernel: usbcore: registered new interface driver mt7601u Apr 19 16:34:38 debian kernel: mt7601u 1-1:1.0 wlan5: renamed from wlan0 Apr 19 16:34:38 debian NetworkManager[2871]: info rfkill1: found WiFi radio killswitch (at /sys/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/ieee80211/phy2/rfkill1) (driver mt7601u) Apr 19 16:34:38 debian systemd[1]: Starting Load/Save RF Kill Switch Status of rfkill1... Apr 19 16:34:38 debian systemd[1]: Started Load/Save RF Kill Switch Status of rfkill1. Apr 19 16:34:38 debian systemd-udevd[4036]: renamed network interface wlan0 to wlan5 Apr 19 16:34:38 debian NetworkManager[2871]: info (wlan5): using nl80211 for WiFi device control Apr 19 16:34:38 debian NetworkManager[2871]: info (wlan5): new 802.11 WiFi device (driver: 'mt7601u' ifindex: 4) Apr 19 16:34:38 debian NetworkManager[2871]: info (wlan5): exported as /org/freedesktop/NetworkManager/Devices/3 Apr 19 16:34:38 debian NetworkManager[2871]: info (wlan5): device state change: unmanaged - unavailable (reason 'managed') [10 20 2] Apr 19 16:34:38 debian NetworkManager[2871]: info (wlan5): preparing device Apr 19 16:34:38 debian dbus[2894]: [system] Activating via systemd: service name='fi.w1.wpa_supplicant1' unit='wpa_supplicant.service' Apr 19 16:34:38 debian NetworkManager[2871]: info devices added (path: /sys/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/net/wlan5, iface: wlan5) Apr 19 16:34:38 debian NetworkManager[2871]: info get unmanaged devices count: 2 Apr 19 16:34:38 debian NetworkManager[2871]: info (wlan5): device state change: unavailable - unmanaged (reason 'unmanaged') [20 10 3] Apr 19 16:34:38 debian systemd[1]: Starting WPA supplicant... Apr 19 16:34:38 debian dbus[2894]: [system] Successfully activated service 'fi.w1.wpa_supplicant1' Apr 19 16:34:38 debian systemd[1]: Started WPA supplicant. Apr 19 16:34:38 debian wpa_supplicant[4056]: Successfully initialized wpa_supplicant Apr 19 16:34:38 debian kernel: IPv6: ADDRCONF(NETDEV_UP): wlan5: link is not ready Apr 19 16:34:38 debian kernel: IPv6: ADDRCONF(NETDEV_UP): wlan5: link is not ready Apr 19 16:34:38 debian NetworkManager[2871]: info wpa_supplicant started --- NetworkManager debug output: NetworkManager[4782]: debug [1429479542.305521] [platform/nm-linux-platform.c:1850] event_notification(): netlink event (type 16) for link: wlan0 (5, family 0) NetworkManager[4782]: debug [1429479542.305988] [platform/nm-linux-platform.c:412] get_kernel_object(): get_kernel_object for link: wlan0 (5, family 0) NetworkManager[4782]: debug [1429479542.307262] [nm-rfkill-manager.c:354] handle_uevent(): udev rfkill event: action 'add' device 'rfkill2' NetworkManager[4782]: info rfkill2: found WiFi radio killswitch (at /sys/devices/pci:00/:00:14.0/usb1/1-3/1-3.1/1-3.1:1.0/ieee80211/phy3/rfkill2) (driver mt7601u) NetworkManager[4782]: debug [1429479542.307546] [nm-rfkill-manager.c:210] recheck_killswitches(): WiFi rfkill switch rfkill2 state now 1/0 NetworkManager[4782]: debug [1429479542.307654] [nm-rfkill-manager.c:210]
Bug#780686: linux-image-3.16.0-4-amd64: Intel GPU hang in intel_crtc_wait_for_pending_flips on IvyBridge, Haswell
Both of those fixes are included in 3.16.7-ckt7-1, the version you reported this against. Are you still seeing a similar problem? So they are. Hmm. I was getting a hang every day or so with 3.16.7-ckt7-1. With latest linux git I am getting zero hangs. There was also a report in the Launchpad bug from someone who was still getting hangs using a kernel with the fix. So it appears there is some other fix that is still missing, but there are a lot of drm/i915 changes between 3.16 and current git. Do you mass import drm fixes or do you require a cherry picked patch? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781858: apt: dangling pointer crash
On 6 April 2015 at 21:21, David Kalnischkies da...@kalnischkies.de wrote: I wonder what is so special about aptdaemon that it has problems now - so can someone please verify that this is really the problem and not just the first thing someone stumbled over while trying to find a culprit (no blame, it would be my first bet, too)? Ok so the deduction process started with: File /usr/lib/ python3/dist-packages/aptdaemon/progress.py, line 309, in _emit_acquire_item elif item.owner.mode: UnicodeDecodeError: 'utf-8' codec can't decode bytes in position 3-4: invalid continuation byte This is the bug pattern that apparently gets hit ~200 times a day. It is a python3 / UTF-8 problem. The switch to python3 means that strings are UTF-8 by default; whereas previously all strings were valid, now only UTF-8 strings are valid. The reported crashes are in the python wrapper function handling the get of 'mode'. All this function does is read Mode and convert it to a Python string (1 line of code). So Mode is not valid UTF-8. Why? What sets Mode? Mode is only set to string literals in apt source Apart from in one place... I saw the assignment before the comment (grep); the comment just confirmed it was an issue It's a crash with bad data at Mode, Mode is only ever set to string literals, except for the dangling pointer to random data. Anyway, if that is really a problem we can fix that in a more compatible way: Instead of assigning the decompProg string, we can go with decomp or unpack or similar such. Its used only for display proposes anyway and if a user sees a bzip2 21kB/42kB or a decomp 21/kB/42kB² should not matter much (trivial diff attached). Looks fine. ² 'decomp' mostly because apt has a tendency to use incomprehensible strings here – or does any normal user know what rred is? Most who see it think its a typo for 'read' after all. ;) I did wonder what Mode was for when I first saw it - apt-python describes Mode as A localized string such as 'Fetching' which indicates the current mode. But in the apt source, it was not localized, and never got set to anything as descriptive as Fetching, which initially made me think it was some other variable. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782011:
Package: lightdm Version: 1.10.3-3 Severity: wishlist gdm3 now puts the Xorg log in systemd journal (a Debian specific patch from bug #765771 also keeps the old style logs). It would be nice for consistency if lightdm also logged Xorg to the system journal, otherwise users might be confused as to why a command like `journalctl /usr/bin/Xorg` does not work on some Debian desktops. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781858: apt: dangling pointer crash
On 6 April 2015 at 13:46, Tomasz Buchert tom...@debian.org wrote:
This should do the trick.
Tomasz
From browsing the code it appears Mode can be assigned to multiple
times for the same Item, e.g.
{
Mode = copy;
...
Mode = decompProg.c_str()
}
In which case using strdup to create a new string for each assignment
will leak memory?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781932:
Why was the severity downgraded from 'serious'? Isn't the laptop display being non-functional a serious bug? One which could potentially impact every Debian laptop user with an Intel GPU and an external monitor? Which, presumably, would be quite a few people. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781932:
On 5 April 2015 at 15:20, Julien Cristau jcris...@debian.org wrote: On Sun, Apr 5, 2015 at 13:54:19 +0100, Chris Bainbridge wrote: Why was the severity downgraded from 'serious'? Isn't the laptop display being non-functional a serious bug? One which could potentially impact every Debian laptop user with an Intel GPU and an external monitor? Which, presumably, would be quite a few people. No, an issue with the display of a single laptop is not serious. How do you know the issue is only with the display of a single laptop? Have you tested any other (Intel) laptops with an external monitor? Particularly where the resolution of the laptop does not match that of the external monitor? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781932:
On 5 April 2015 at 15:32, Julien Cristau jcris...@debian.org wrote: On Sun, Apr 5, 2015 at 15:29:58 +0100, Chris Bainbridge wrote: On 5 April 2015 at 15:20, Julien Cristau jcris...@debian.org wrote: On Sun, Apr 5, 2015 at 13:54:19 +0100, Chris Bainbridge wrote: Why was the severity downgraded from 'serious'? Isn't the laptop display being non-functional a serious bug? One which could potentially impact every Debian laptop user with an Intel GPU and an external monitor? Which, presumably, would be quite a few people. No, an issue with the display of a single laptop is not serious. How do you know the issue is only with the display of a single laptop? Have you tested any other (Intel) laptops with an external monitor? Particularly where the resolution of the laptop does not match that of the external monitor? 1) if this was a general issue we'd have received a dozen reports by now 2) my laptop works just fine It is unlikely that this kind of bug would impact just one single laptop. It is more likely to impact a broader class, at the least IvyBridge Macbook, but possibly more broadly just IvyBridge laptop or perhaps SNB/IVB/HSW laptop. Without testing and/or understanding of the cause of the bug, I don't see how you can draw the conclusion that the bug only occurs on a single laptop. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781891: gdm3: xorg log to systemd journal
Package: gdm3 Version: 3.14.1-6 Severity: wishlist The preferred option of Gnome upstream (since 3.12) seems to be --enable-systemd-journal. Unless there are strong arguments against, then Debian should probably follow what upstream is doing, since that will be the standard way and what people end up documenting e.g. http://who-t.blogspot.co.uk/2014/03/viewing-xorglog-with-journalctl.html http://worldofgnome.org/in-gnome-3-12-systemd-will-track-xorg-logs/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781893: gnome-control-center: Gnome System Details shows wrong drive size (btrfs?)
Package: gnome-control-center Version: 1:3.14.2-3 Severity: minor Dear Maintainer, Gnome System Details shows Disk 848GB on a 128GB disk system (btrfs subvolumes causing confusion?) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781932: xserver-xorg-video-intel: laptop display unusable (blank) if external monitor is connected
Package: xserver-xorg-video-intel Version: 2:2.21.15-2+b2 Severity: serious Dear Maintainer, Hardware: IvyBridge HD4000 GPU on Macbook Pro 13 To reproduce: - Connect an external monitor on DP - Boot jessie - Log in to Gnome - Laptop display immediately goes blank This bug appears to be fixed in the latest upstream git. It is not known at which point it got fixed. xorg.log with working upstream git: (--) intel(0): Output eDP1 using initial mode 2560x1600 on pipe 0 (--) intel(0): Output DP2 using initial mode 1680x1050 on pipe 1 xorg.log with non-working jessie driver: (II) intel(0): Output eDP1 using initial mode 1680x1050 (II) intel(0): Output DP2 using initial mode 1680x1050 So the issue might be that the driver attempts to use the incorrect external monitor resolution 1680x1050 for the laptop display. Though xrandr reports the laptop display resolution 2560x1600 is in use: Screen 0: minimum 320 x 200, current 4240 x 1600, maximum 8192 x 8192 eDP1 connected primary 2560x1600+0+0 (normal left inverted right x axis y axis) 286mm x 179mm 2560x1600 59.97*+ 2048x1536 60.00 1920x1440 60.00 1856x1392 60.01 1792x1344 60.01 1920x1200 59.95 1920x1080 59.93 1600x1200 60.00 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1280x1024 60.02 1440x900 59.89 1280x960 60.00 1360x768 59.8059.96 1152x864 60.00 1024x768 60.00 800x600 60.3256.25 640x480 59.94 Attempting to manually change the mode with xrandr does nothing (not surprising, as xrandr reports the mode is already correct). -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Feb 20 2014 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 2401376 Feb 11 00:35 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) /etc/X11/xorg.conf does not exist. /etc/X11/xorg.conf.d does not exist. /etc/modprobe.d contains no KMS configuration files. Kernel version (/proc/version): --- Linux version 3.16.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt7-1 (2015-03-01) Xorg X server log files on system: -- -rw-r--r-- 1 root root 31378 Jul 28 2014 /var/log/Xorg.10.log -rw-r--r-- 1 root root 27023 Feb 28 17:54 /var/log/Xorg.3.log -rw-r--r-- 1 root root 27022 Feb 28 18:51 /var/log/Xorg.1.log -rw-r--r-- 1 root root 28596 Mar 1 01:31 /var/log/Xorg.2.log -rw-r--r-- 1 root root 42096 Apr 5 01:31 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [52.259] X.Org X Server 1.16.4 Release Date: 2014-12-20 [52.259] X Protocol Version 11, Revision 0 [52.259] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian [52.259] Current Operating System: Linux debian 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt7-1 (2015-03-01) x86_64 [52.259] Kernel command line: BOOT_IMAGE=/@jessie/boot/vmlinuz-3.16.0-4-amd64 root=UUID=61cc969e-5ba5-4e04-80ad-5e26d2f39c55 ro rootflags=subvol=@jessie quiet [52.259] Build Date: 11 February 2015 12:32:02AM [52.259] xorg-server 2:1.16.4-1 (http://www.debian.org/support) [52.259] Current version of pixman: 0.32.6 [52.259] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [52.259] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [52.259] (==) Log file: /var/log/Xorg.0.log, Time: Sun Apr 5 01:31:33 2015 [52.259] (==) Using system config directory /usr/share/X11/xorg.conf.d [52.260] (==) No Layout section. Using the first Screen section. [52.260] (==) No screen section available. Using defaults. [52.260] (**) |--Screen Default Screen Section (0) [52.260] (**) | |--Monitor default monitor [52.260] (==) No monitor specified for screen Default Screen Section. Using a default monitor configuration. [52.260] (==) Automatically adding devices [52.260] (==) Automatically enabling devices [52.260] (==) Automatically adding GPU devices [52.260] (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. [52.260] Entry deleted from font path. [52.260] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [52.260] (==) ModulePath set to /usr/lib/xorg/modules [52.260] (II) The server
Bug#781858: apt: dangling pointer crash
Package: apt Version: 1.0.9.7 Severity: serious Dear Maintainer, The apt source includes in apt-pkg/acquire-item.cc: // FIXME: this points to a c++ string that goes out of scope Mode = decompProg.c_str(); } Mode is a char ptr decompProg is a std::string When decompProg goes out of scope it will be destroyed, and its internal buffer that Mode points to will be freed. Any dereference of Mode will now return arbitrary data which can cause seemingly random and hard-to-debug crashes. python3-apt, for example, will read Mode and interpret it as UTF-8 (in python/acquire-item.cc:acquireitem_get_mode). Since the data is now essentially random, and not all byte sequences are valid UTF-8, this will cause a crash to intermittently occur in any application using python3-apt e.g. aptdaemon https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1060081 (the Ubuntu crash tracker http://errors.ubuntu.com gets about 200 crash reports a day for that bug). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781737: gparted: GUI hangs while doing libparted operations such as FAT16/FAT32 resizing
Package: gparted Version: 0.19.0-2 Severity: serious Tags: upstream Forwarded: https://bugzilla.gnome.org/show_bug.cgi?id=737022 The gparted GUI always hangs when gparted is doing some particular operations. If the screensaver/screenlock runs at this point, afterwards gparted windows will be gray, giving user the appearance that gparted has crashed. This bug is caused by long lasting (potentially hours) blocking IO operations being done on the GUI thread. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781738: gnucash: ImportError: No module named gnucash
Package: gnucash Version: 1:2.6.4-3 Severity: normal Dear Maintainer, On starting gnucash, it always fails to import some Python module: $ gnucash Traceback (most recent call last): File /usr/share/gnucash/python/init.py, line 3, in module from gnucash import * ImportError: No module named gnucash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781741: gnucash crash when click back on QIF import
Package: gnucash Version: 1:2.6.4-3 Severity: normal Dear Maintainer, To reproduce do: file - import - qif - forward - select - import - forward - start - forward - back - back Backtrace: In ice-9/boot-9.scm: 157: 3 [catch #t #catch-closure 1190ee0 ...] In unknown file: ?: 2 [apply-smob/1 #catch-closure 1190ee0] In qif-import/qif-file.scm: 557: 1 [qif-file:check-from-acct #f] In ice-9/boot-9.scm: 1381: 0 [#procedure 1af16c0 at ice-9/boot-9.scm:1380:4 (obj) #f] ice-9/boot-9.scm:1381:15: In procedure #procedure 1af16c0 at ice-9/boot-9.scm:1380:4 (obj): ice-9/boot-9.scm:1381:15: In procedure struct_vtable: Wrong type argument in position 1 (expecting struct): #f -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744231: gnucash: Crash on QIF import
On 2 April 2015 at 08:00, Dmitry Smirnov only...@debian.org wrote: Hi Chris, On Fri, 11 Apr 2014 17:41:09 Chris Bainbridge wrote: Start QIF import, at Set a date format for this QIF file select 'd-m-y'. Crash. I've noticed that upstream closed corresponding bug report [1] due to lack of information (they could not reproduce the problem). Do you still have this problem with GnuCash-2.6.4 ? I no longer have any of the problematic QIF files to test. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781666: xserver-xorg-video-intel: intel driver option TearFree does not work in Jessie
Package: xserver-xorg-video-intel Version: 2:2.21.15-2+b2 Severity: normal The Intel option TearFree does not work; tearing is still present. Setup is XFCE running on Ivy Bridge HD4000 with three monitors. This is fixed in the latest upstream git. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781716: gparted: partitioning fails due to lack of udisks2 locking and automount
Package: gparted Version: 0.19.0-2 Severity: serious Tags: upstream Forwarded: https://bugzilla.gnome.org/show_bug.cgi?id=745349 Gparted does not lock the disk being partitioned, so it will be automounted whilst gparted is operating on it, resulting in gparted failing mid-operation. This has been fixed upstream: https://git.gnome.org/browse/gparted/commit/?id=4acb8e4fbb9e01d33cc1e9fd89686a3818050690 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781604: `journalctl /dev/sda` shows empty log
Are you running the command as root? Yes. The error if you run journalctl as a regular user is different: No journal files were found. Whereas this just shows an empty log. This will potentially break any scripts or monitoring tools that query device information using this format, and people will expect `journalctl /dev/...` to work since it is the basic method of querying device logs in systemd. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781604: `journalctl /dev/sda` shows empty log
Package: systemd Version: 215-12 Severity: serious `man journalctl` says: Show all logs of the kernel device node /dev/sda: journalctl /dev/sda But: debian # journalctl /dev/sda -- Logs begin at Tue 2015-03-31 11:57:43 BST, end at Tue 2015-03-31 14:43:04 BST. -- debian # It does not work. Verified on both i386 and amd64 that there are no logs shown. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762047:
Okay, so I think your original problem is because the Xorg fbdev driver uses the colour depth from console by default, and I guess the login manager you're using can't deal with that. You may want to report that against the login manager package Filed at https://bugs.launchpad.net/lightdm/+bug/1438231 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781544: firmware-b43-installer breaks apt-get dist-upgrade to jessie
Package: firmware-b43-installer Version: 1:019-1 Severity: serious Dear Maintainer, On a dist-upgrade to jessie the network is not up at the point firmware-b43-installer.postinst is run, so the wget download fails. The script contains code that is supposed to ignore the error and exit 0 (success) in this case: wget --timeout=60 http://www.lwfinger.com/b43-firmware/broadcom-wl-5.100.138.tar.bz2 if [ $? -ne 0 ]; then echo Some problem occurred during the firmware download. Please check your internet connection. exit 0 Unfortunately this code does not work; because of the set -e at the start of the firmware-b43-installer.postinst, the wget failure causes the script to immediately exit and return an error code. The if [ $? -ne 0 ] check is never reached. The exact error in term.log is: Setting up firmware-b43-installer (1:019-1) ... No chroot environment found. Starting normal installation --2015-03-30 19:13:27-- http://www.lwfinger.com/b43-firmware/broadcom-wl-5.100.138.tar.bz2 Resolving www.lwfinger.com (www.lwfinger.com)... failed: Name or service not known. wget: unable to resolve host address ‘www.lwfinger.com’ dpkg: error processing package firmware-b43-installer (--configure): subprocess installed post-installation script returned error exit status 4 ... Errors were encountered while processing: firmware-b43-installer -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781560: lvm2 errors on every boot: initramfs scripts expect dmeventd (jessie)
Package: lvm2 Version: 2.02.111-2.1 Severity: normal Tags: patch lvm2 init scripts call vgchange without --sysinit resulting in errors on every boot: /sbin/dmeventd stat failed no such file or directory /sbin/dmeventd stat failed no such file or directory ... event registration failed: no such process ...snapshot segment monitoring function failed because dmeventd is not in the initramfs fix: replace --ignorelockingfailure with --sysinit in /usr/share/initramfs-tools/scripts/local-block/lvm2 /usr/share/initramfs-tools/scripts/local-top/lvm2 diff -ur scripts.orig/local-block/lvm2 scripts/local-block/lvm2 --- scripts.orig/local-block/lvm2 2015-01-17 22:35:47.0 + +++ scripts/local-block/lvm22015-03-31 00:36:16.828462329 +0100 @@ -30,7 +30,7 @@ eval $(dmsetup splitname --nameprefixes --noheadings --rows $dev) if [ $DM_VG_NAME ] [ $DM_LV_NAME ]; then - lvm lvchange -aly --ignorelockingfailure $DM_VG_NAME/$DM_LV_NAME + lvm lvchange -aly --sysinit $DM_VG_NAME/$DM_LV_NAME rc=$? if [ $rc = 5 ]; then echo Unable to find LVM volume $DM_VG_NAME/$DM_LV_NAME diff -ur scripts.orig/local-top/lvm2 scripts/local-top/lvm2 --- scripts.orig/local-top/lvm2 2015-01-17 17:13:22.0 + +++ scripts/local-top/lvm2 2015-03-31 01:11:11.852175626 +0100 @@ -27,12 +27,12 @@ # Take care of lilo boot arg, risky activating of all vg case $dev in fe[0-9]*) - lvm vgchange -aly --ignorelockingfailure + lvm vgchange -aly --sysinit exit 0 ;; # FIXME: check major /dev/root) - lvm vgchange -aly --ignorelockingfailure + lvm vgchange -aly --sysinit exit 0 ;; esac @@ -46,7 +46,7 @@ eval $(dmsetup splitname --nameprefixes --noheadings --rows $dev) if [ $DM_VG_NAME ] [ $DM_LV_NAME ]; then - lvm lvchange -aly --ignorelockingfailure $DM_VG_NAME/$DM_LV_NAME + lvm lvchange -aly --sysinit $DM_VG_NAME/$DM_LV_NAME rc=$? if [ $rc = 5 ]; then echo Unable to find LVM volume $DM_VG_NAME/$DM_LV_NAME -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780990: xserver-xorg-video-intel: hangs startx on logout if xrandr rotate is used in session
Package: xserver-xorg-video-intel Version: 2:2.21.15-2+b2 Severity: important Dear Maintainer, startx hangs on logout if xrandr rotate is used in session. There may be other ways to hang it but xrandr rotate is reliably repeatable. To reproduce: 1. Install minimal Jessie netinst system 2. apt-get install xorg blackbox # (bug does not seem to happen with gnome) 3. log in 4. startx 5. xrandr --output eDP1 --rotate left 6. right-click screen - exit 7. terminal is hung. Nothing responds - can not change terminal, ctrl-c, or anything. Installing the latest upstream git appears to fix this bug. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#542899: Processed: your mail
On 18 March 2015 at 11:35, Cyril Brulebois k...@debian.org wrote: Pretty sure that's in no way a serious bug. If you want it to happen, submit one. Artificially bumping the severity won't help. Isn't a missing man page a violation of the requirement stated in Debian Policy Manual 12.1? Hence violation of policy = severity serious? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#542899: Processed: your mail
On 18 March 2015 at 11:59, Holger Levsen hol...@layer-acht.org wrote: And really, the best way to get this fixed is to write the missing manpage. Attached. Please add to the Debian package. linux-boot-prober.8 Description: Binary data os-prober.8 Description: Binary data
Bug#780668: libgl1-mesa-dri: WebGL Intel GPU Hang stuck on render ring
Package: libgl1-mesa-dri Version: 10.3.2-1 Severity: normal Dear Maintainer, IvyBridge GPU HD4000 Visit http://www.fishgl.com in Chromium or Iceweasel GPU hangs This was fixed upstream by commit fd31628 commit fd31628 Author: Iago Toral Quiroga ito...@igalia.com Date: Tue Jul 29 12:36:31 2014 +0300 glsl: Optimize min/max expression trees Hang log: Mar 16 13:02:12 debian kernel: [drm] stuck on render ring Mar 16 13:02:12 debian kernel: [drm] GPU HANG: ecode 0:0x85ffeefa, in iceweasel [1818], reason: Ring hung, action: reset Mar 16 13:02:12 debian kernel: [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. Mar 16 13:02:12 debian kernel: [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI - DRM/Intel Mar 16 13:02:12 debian kernel: [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. Mar 16 13:02:12 debian kernel: [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. Mar 16 13:02:12 debian kernel: [drm] GPU crash dump saved to /sys/class/drm/card0/error Mar 16 13:02:14 debian kernel: [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp off Mar 16 13:02:19 debian kernel: [drm] stuck on render ring Mar 16 13:02:19 debian kernel: [drm] GPU HANG: ecode 0:0x85ff7c1a, in iceweasel [1818], reason: Ring hung, action: reset Mar 16 13:02:21 debian kernel: [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp off -- Package-specific info: glxinfo: name of display: :0.0 display: :0 screen: 0 direct rendering: Yes server glx vendor string: SGI server glx version string: 1.4 server glx extensions: GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_multisample, GLX_EXT_create_context_es2_profile, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_OML_swap_method, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_swap_control client glx vendor string: Mesa Project and SGI client glx version string: 1.4 client glx extensions: GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync GLX version: 1.4 GLX extensions: GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_create_context_es2_profile, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) Ivybridge Mobile OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.3.2 OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: GL_3DFX_texture_compression_FXT1, GL_AMD_conservative_depth, GL_AMD_draw_buffers_blend, GL_AMD_performance_monitor, GL_AMD_seamless_cubemap_per_texture, GL_AMD_shader_trinary_minmax, GL_AMD_vertex_shader_layer, GL_AMD_vertex_shader_viewport_index, GL_ANGLE_texture_compression_dxt3, GL_ANGLE_texture_compression_dxt5, GL_APPLE_object_purgeable, GL_ARB_ES2_compatibility, GL_ARB_ES3_compatibility, GL_ARB_base_instance, GL_ARB_blend_func_extended, GL_ARB_buffer_storage, GL_ARB_clear_buffer_object, GL_ARB_clear_texture, GL_ARB_compressed_texture_pixel_storage, GL_ARB_conditional_render_inverted, GL_ARB_conservative_depth, GL_ARB_copy_buffer, GL_ARB_copy_image, GL_ARB_debug_output, GL_ARB_depth_buffer_float,
Bug#780686: linux-image-3.16.0-4-amd64: Intel GPU hang in intel_crtc_wait_for_pending_flips on IvyBridge, Haswell
Package: src:linux Version: 3.16.7-ckt7-1 Severity: normal Dear Maintainer, As documented at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1384342 a GPU hang will regularly occur on Intel IvyBridge and Haswell GPUs. This was fixed upstream in patches 48bf5b2 and 2a92d5b which were included in Linux 3.19. Author: Chris Wilson ch...@chris-wilson.co.uk Date: Sat Dec 27 09:48:28 2014 + drm/i915: Ban Haswell from using RCS flips Like Ivybridge, we have reports that we get random hangs when flipping with multiple pipes. Extend commit 2a92d5bca1999b69c78f3c3e97b5484985b094b9 Author: Chris Wilson ch...@chris-wilson.co.uk Date: Tue Jul 8 10:40:29 2014 +0100 drm/i915: Disable RCS flips on Ivybridge to also apply to Haswell.
Bug#780488: linkchecker / linkchecker-gui desktop icons broken
Package: linkchecker Version: 9.3-1 Severity: minor Dear Maintainer, Linkchecker appears with broken icons on the desktop. Problem probably caused by Icon=logo48x48: $ cat /usr/share/applications/linkchecker.desktop [Desktop Entry] Name=LinkChecker Commandline GenericName=URL validator GenericName[de]=URL Validator Version=1.0 Type=Application Exec=linkchecker Terminal=true Categories=Network;WebDevelopment; Icon=logo48x48 -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages linkchecker depends on: ii libc62.19-15 ii python 2.7.8-4 ii python-requests 2.4.3-4 linkchecker recommends no packages. Versions of packages linkchecker suggests: pn clamav-daemon none ii linkchecker-gui 9.3-1 pn linkchecker-web none pn python-argcomplete none pn python-cssutils none ii python-gconf2.28.1+dfsg-1.1 pn python-geoipnone pn python-meliae none pn python-twillnone -- 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#780490: imagemagick desktop icons dupliated / one does not show
Package: imagemagick Version: 8:6.8.9.9-5 Severity: minor Dear Maintainer, 1. After installed imagemagick it appears twice in the desktop menu with exactly the same title. Is this correct? 2. One of these entries does not have an icon. Probably the error is Q16 instead of q16 in the following: $ cat /usr/share/applications/display-im6.desktop|grep -i icon Icon=display-im6.Q16 -- Package-specific info: ImageMagick program version --- animate: ImageMagick 6.8.9-9 Q16 x86_64 2015-01-05 http://www.imagemagick.org compare: ImageMagick 6.8.9-9 Q16 x86_64 2015-01-05 http://www.imagemagick.org convert: ImageMagick 6.8.9-9 Q16 x86_64 2015-01-05 http://www.imagemagick.org composite: ImageMagick 6.8.9-9 Q16 x86_64 2015-01-05 http://www.imagemagick.org conjure: ImageMagick 6.8.9-9 Q16 x86_64 2015-01-05 http://www.imagemagick.org display: ImageMagick 6.8.9-9 Q16 x86_64 2015-01-05 http://www.imagemagick.org identify: ImageMagick 6.8.9-9 Q16 x86_64 2015-01-05 http://www.imagemagick.org import: ImageMagick 6.8.9-9 Q16 x86_64 2015-01-05 http://www.imagemagick.org mogrify: ImageMagick 6.8.9-9 Q16 x86_64 2015-01-05 http://www.imagemagick.org montage: ImageMagick 6.8.9-9 Q16 x86_64 2015-01-05 http://www.imagemagick.org stream: ImageMagick 6.8.9-9 Q16 x86_64 2015-01-05 http://www.imagemagick.org -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages imagemagick depends on: ii imagemagick-6.q16 8:6.8.9.9-5 imagemagick recommends no packages. imagemagick 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#780143:
Axel's patch from upstream git fixes the issue (tested with fixedsc font in terminator).
Bug#780143:
severity 780143 serious retitle 780143 libfreetype6_2.5.2-3 makes some fonts unusable I'm not sure what fonts are affected by this bug, but the package bump should not be released with a bug that makes some unknown number of fonts unusable. Retitle as it is not clear that this bug affects only fixed fonts.
Bug#780143: libfreetype6:amd64: libfreetype6_2.5.2-3 breaks fixed font in terminal
Package: libfreetype6
Version: 2.5.2-3
Severity: important
Dear Maintainer,
Using font FixedSC from http://pts-mini-
gpl.googlecode.com/svn/trunk/fonts/fixedsc.tgz
(libfreetype6_2.5.2-2 was ok)
upgrade to libfreetype6_2.5.2-3
run gnome terminal or terminator
terminal text is corrupt: http://imgur.com/DQZtDBb
downgrade back to libfreetype6_2.5.2-2: terminal text is now ok
The bad patch seems to be: 0020-Fix-Savannah-bug-43547.-CVE-2014-9671.patch:
+/* we now check whether the `size' and `offset' values are reasonable: */
+/* `offset' + `size' must not exceed the stream size */
+tables = face-toc.tables;
+for ( n = 0; n toc-count; n++ )
+{
+ /* we need two checks to avoid overflow */
+ if ( ( tables-sizestream-size) ||
+ ( tables-offset stream-size - tables-size ) )
+ {
+error = FT_THROW( Invalid_Table );
+goto Exit;
+ }
+ tables++;
+}
+
This fails when:
tables-size=100
tables-offset=339968
stream-size=340040
tables-offset stream-size - tables-size
339968 340040-100(=339940)
..xsession-errors:
/usr/share/terminator/terminatorlib/window.py:384: PangoWarning: failed to
create cairo scaled font, expect ugly output. the offending font is 'FixedSC
11'
self.present()
/usr/share/terminator/terminatorlib/window.py:384: PangoWarning: font_face
status is: out of memory
self.present()
/usr/share/terminator/terminatorlib/window.py:384: PangoWarning: scaled_font
status is: out of memory
self.present()
/usr/share/terminator/terminatorlib/window.py:384: PangoWarning: shaping
failure, expect ugly output. shape-engine='BasicEngineFc', font='FixedSC 11',
text='
!#$%'()*+,-./0123456789:;=?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~'
self.present()
/usr/share/terminator/terminatorlib/window.py:384: PangoWarning: failed to
create cairo scaled font, expect ugly output. the offending font is 'FixedSC
Bold 11'
self.present()
/usr/share/terminator/terminatorlib/window.py:384: PangoWarning: shaping
failure, expect ugly output. shape-engine='BasicEngineFc', font='FixedSC Bold
11', text='
!#$%'()*+,-./0123456789:;=?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~'
self.present()
-- System Information:
Debian Release: 8.0
APT prefers testing-updates
APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages libfreetype6:amd64 depends on:
ii libc6 2.19-15
ii libpng12-0 1.2.50-2+b2
ii multiarch-support 2.19-15
ii zlib1g 1:1.2.8.dfsg-2+b1
libfreetype6:amd64 recommends no packages.
libfreetype6:amd64 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#780143:
Upstream: The problem you are describing in this bug report has already been fixed in version 2.5.5
Bug#779656:
0020-Fix-Savannah-bug-43547.-CVE-2014-9671.patch is buggy, see bug #780143
Bug#779682: texlive-base: install complains a4 is not valid for pdftex but says a4 is valid
Package: texlive-base Version: 2014.20141024-2 Severity: normal Dear Maintainer, texlive-base warns that a4 is not a valid setting for pdftex, but then recommends a command which says that a4 is valid. # apt-get install texlive-base Unmanageable system paper size (a4) The currently defined system-wide paper size is a4. However, the TeX configuration system cannot handle this paper size for pdftex. The setting will remain unchanged. The following command can show the list of known paper sizes for pdftex: texconfig pdftex paper # texconfig pdftex paper WARNING: On Debian, this change will NOT be persistent upon upgrades or changes to the libpaper settings! Usage: texconfig pdftex paper PAPER Valid PAPER settings: a4 letter -- Package-specific info: IMPORTANT INFORMATION: We will only consider bug reports concerning the packaging of TeX Live as relevant. If you have problems with combination of packages in a LaTeX document, please consult your local TeX User Group, the comp.text.tex user group, the author of the original .sty file, or any other help resource. In particular, bugs that are related to up-upstream, i.e., neither Debian nor TeX Live (upstream), but the original package authors, will be closed immediately. *** The Debian TeX Team is *not* a LaTeX Help Desk *** If you report an error when running one of the TeX-related binaries (latex, pdftex, metafont,...), or if the bug is related to bad or wrong output, please include a MINIMAL example input file that produces the error in your report. Please run your example with (pdf)latex -recorder ... (or any other program that supports -recorder) and send us the generated file with the extension .fls, it lists all the files loaded during the run and can easily explain problems induced by outdated files in your home directory. Don't forget to also include minimal examples of other files that are needed, e.g. bibtex databases. Often it also helps to include the logfile. Please, never send included pictures! If your example file isn't short or produces more than one page of output (except when multiple pages are needed to show the problem), you can probably minimize it further. Instructions on how to do that can be found at http://www.minimalbeispiel.de/mini-en.html (english) or http://www.minimalbeispiel.de/mini.html (german) ## minimal input file ## other files ## List of ls-R files -rw-r--r-- 1 root root 828 Mar 3 23:49 /var/lib/texmf/ls-R lrwxrwxrwx 1 root root 29 Oct 21 01:46 /usr/share/texmf/ls-R - /var/lib/texmf/ls-R-TEXMFMAIN lrwxrwxrwx 1 root root 31 Dec 2 13:39 /usr/share/texlive/texmf-dist/ls-R - /var/lib/texmf/ls-R-TEXLIVEDIST lrwxrwxrwx 1 root root 31 Dec 2 13:39 /usr/share/texlive/texmf-dist/ls-R - /var/lib/texmf/ls-R-TEXLIVEDIST ## Config files -rw-r--r-- 1 root root 475 Mar 3 23:44 /etc/texmf/web2c/texmf.cnf -rw-r--r-- 1 root root 3186 Mar 3 23:49 /var/lib/texmf/web2c/fmtutil.cnf lrwxrwxrwx 1 root root 32 Dec 2 13:39 /usr/share/texmf/web2c/updmap.cfg - /var/lib/texmf/updmap.cfg-DEBIAN Warning: language.dat cannot be found with kpsewhich! ## Files in /etc/texmf/web2c/ total 8 -rw-r--r-- 1 root root 283 Oct 21 01:46 mktex.cnf -rw-r--r-- 1 root root 475 Mar 3 23:44 texmf.cnf ## md5sums of texmf.d ca40c66f144b4bafc3e59a2dd32ecb9c /etc/texmf/texmf.d/00debian.cnf -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages texlive-base depends on: ii debconf [debconf-2.0] 1.5.55 ii dpkg 1.17.23 ii libpaper-utils 1.1.24+nmu4 ii tex-common 5.03 ii texlive-binaries 2014.20140926.35254-6 ii ucf3.0030 ii xdg-utils 1.1.0~rc1+git20111210-7.4 Versions of packages texlive-base recommends: ii lmodern 2.004.4-5 Versions of packages texlive-base suggests: ii evince [postscript-viewer] 3.14.1-1 ii ghostscript [postscript-viewer] 9.06~dfsg-2 pn perl-tk none pn xpdf-reader | pdf-viewer none Versions of packages tex-common depends on: ii debconf [debconf-2.0] 1.5.55 ii dpkg 1.17.23 ii ucf3.0030 Versions of packages tex-common suggests: ii debhelper 9.20141022 Versions of packages texlive-base is related to: ii tex-common5.03 ii texlive-binaries 2014.20140926.35254-6 -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a
Bug#529178:
The Dell 2209WA had some DVI hardware glitch that caused these mysterious blackouts. See extended discussion: http://en.community.dell.com/support-forums/peripherals/f/3529/t/19257125 And upstream: https://bugs.freedesktop.org/show_bug.cgi?id=89110 Some users reported that Sapphire fixed the problem with a BIOS update but for other manufacturers it was always an issue. Using an active DisplayPort adaptor was the recommended workaround in the end. Final comment from Dell: Posted by DELL-Chris I never could find a solid fix, several workarounds for PC, none for Macs. The issue does not occur for everyone and we could never replicate it in our lab.
Bug#779369: pyqt5-examples missing dependencies python3-pyqt5.{qtquick, qtopengl, qtmultimedia, qtsvg} etc.
On 1 March 2015 at 17:21, Scott Kitterman deb...@kitterman.com wrote: On Friday, February 27, 2015 07:43:08 PM Chris Bainbridge wrote: Package: pyqt5-examples Version: 5.3.2+dfsg-3 Severity: normal Dear Maintainer, pyqt5-examples should depend on all the libraries necessary to run the examples. ... We've discussed this a bit and don't really agree with the premise. The examples are provided as part of the documentation that goes with PyQt5 and are not really meant to be executed without further consideration. Is this consistent with other -examples packages in Debian? Afaics the qt*5-example packages all have proper dependencies and are executable after installation, as are qt4-demos, and non-executable examples are usually put in a -doc package (like python-qt4-doc).
Bug#779221: qtquickcontrols5-examples: resizing QT window is jerky, redraw/resize problem
On 26 February 2015 at 16:13, Lisandro Damián Nicanor Pérez Meyer perezme...@gmail.com wrote: I can't reproduce this behavior on an Intel card. This normally happens due to graphic driver's issues, qml tends to find them quite quickly ;) Since it appears on both Radeon and Intel on two completely different systems, it's probably a bug in QT rather than the actual graphics drivers. I posted screenshots taken during the window resize, the corruption of the window before repaint is visible: http://imgur.com/a/5AP01 It happens on both XFCE and Gnome, x86-32 and x86-64. Tested on both x86 with Radeon and amd64 with Intel graphics (Intel graphics has TearFree vsync on some this is not the problem) Do you mind to specify which drivers are you using in each case? xserver-xorg-video-radeon-7.5.0 xf86-video-intel-2.99.917 But I do not think this is a specific driver problem, it could be a general problem with Xorg.
Bug#779451: lightdm: dm-tool switch-to-user always returns to login screen
Package: lightdm Version: 1.10.3-3 Severity: normal Dear Maintainer, dm-tool switch-to-user always opens the logins screen (same as dm-tool switch-to-greeter) - which requires reentering the username and password. This even happens when dm-tool list-seats shows active sessions. Unless I'm missing something, fast user switching is supposed to avoid this. Using Debian Jessie with XFCE and Gnome. -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages lightdm depends on: ii adduser3.113+nmu3 ii consolekit 0.4.6-5 ii dbus 1.8.12-3 ii debconf [debconf-2.0] 1.5.55 ii libc6 2.19-13 ii libgcrypt201.6.2-4+b1 ii libglib2.0-0 2.42.1-1 ii libpam-systemd 215-11 ii libpam0g 1.1.8-3.1 ii libxcb11.10-3+b1 ii libxdmcp6 1:1.1.1-1+b1 ii lightdm-gtk-greeter [lightdm-greeter] 1.8.5-2 Versions of packages lightdm recommends: ii xserver-xorg 1:7.7+7 Versions of packages lightdm suggests: ii accountsservice 0.6.37-3+b1 ii upower 0.99.1-3.1 -- Configuration Files: /etc/apparmor.d/lightdm-guest-session b51cea1a1248cf9bf45f2e9024c7734f [Errno 2] No such file or directory: u'/etc/apparmor.d/lightdm-guest-session b51cea1a1248cf9bf45f2e9024c7734f' /etc/lightdm/lightdm.conf changed [not included] -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779371: qt4-demos: corrupt demo descriptions (seem to include source code?!)
Package: qt4-demos Version: 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 Severity: normal Dear Maintainer, Run: $ /usr/lib/x86_64-linux-gnu/qt4/bin/qtdemo Description is corrupt for following demos (seems to include source code?) Animation Framework Moving Blcoks, Stickman Main Windows Menus, DockWidgets QT Designer Calulator Builder, Calulator Form Desktop System Tray, Screenshot etc. etc. -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages qt4-demos depends on: ii libc6 2.19-13 ii libgcc1 1:4.9.1-19 ii libgl1-mesa-glx [libgl1] 10.3.2-1 ii libphonon44:4.8.0-4 ii libqt4-declarative4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-designer 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-help 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-network4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-opengl 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-script 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-scripttools4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-sql4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-svg4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-test 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-xml4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-xmlpatterns4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqtcore44:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqtdbus44:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libstdc++64.9.1-19 Versions of packages qt4-demos recommends: ii libqt4-declarative-gestures 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-declarative-particles 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 pn qt4-dev-tools none ii qt4-doc 4:4.8.6+git64-g5dc8b2b+dfsg-2 Versions of packages qt4-demos suggests: ii qt4-qmlviewer 4:4.8.6+git64-g5dc8b2b+dfsg-2+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#779373: qt4-demos: browser demo does not work
Package: qt4-demos Version: 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 Severity: normal Dear Maintainer, Click on Demonstrations Browser Launch Result: Could not launch the example. Ensure that it has been built. -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages qt4-demos depends on: ii libc6 2.19-13 ii libgcc1 1:4.9.1-19 ii libgl1-mesa-glx [libgl1] 10.3.2-1 ii libphonon44:4.8.0-4 ii libqt4-declarative4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-designer 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-help 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-network4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-opengl 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-script 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-scripttools4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-sql4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-svg4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-test 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-xml4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-xmlpatterns4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqtcore44:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqtdbus44:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libstdc++64.9.1-19 Versions of packages qt4-demos recommends: ii libqt4-declarative-gestures 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-declarative-particles 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 pn qt4-dev-tools none ii qt4-doc 4:4.8.6+git64-g5dc8b2b+dfsg-2 Versions of packages qt4-demos suggests: ii qt4-qmlviewer 4:4.8.6+git64-g5dc8b2b+dfsg-2+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#779369: pyqt5-examples missing dependencies python3-pyqt5.{qtquick, qtopengl, qtmultimedia, qtsvg} etc.
Package: pyqt5-examples Version: 5.3.2+dfsg-3 Severity: normal Dear Maintainer, pyqt5-examples should depend on all the libraries necessary to run the examples. For example: $ /usr/share/doc/pyqt5-examples/examples/qtdemo/qtdemo.py Click on Quick Animation Launch : Nothing happens $ python3 /usr/share/doc/pyqt5-examples/examples/quick/animation/animation.py Traceback (most recent call last): File /usr/share/doc/pyqt5-examples/examples/quick/animation/animation.py, line 49, in module from PyQt5.QtQuick import QQuickView ImportError: No module named 'PyQt5.QtQuick' etc. Also note there is another missing dependency: python3-pyqt5.qtopengl should depend on python3-opengl (the opengl demos need python3-opengl but even after install python3-pyqt5.qtopengl it is not installed). Even after that, an opengl demo seems to not work: $ /usr/share/doc/pyqt5-examples/examples/qtdemo/qtdemo.py Click on OpenGL OpenGL Window Launch: Crash/Hang (?) $ python3 /usr/share/doc/pyqt5-examples/examples/opengl/openglwindow.py Traceback (most recent call last): File /usr/share/doc/pyqt5-examples/examples/opengl/openglwindow.py, line 115, in exposeEvent self.renderNow() File /usr/share/doc/pyqt5-examples/examples/opengl/openglwindow.py, line 95, in renderNow self.m_gl = self.m_context.versionFunctions() ImportError: No module named 'PyQt5._QOpenGLFunctions_3_0' Traceback (most recent call last): File /usr/share/doc/pyqt5-examples/examples/opengl/openglwindow.py, line 115, in exposeEvent self.renderNow() File /usr/share/doc/pyqt5-examples/examples/opengl/openglwindow.py, line 100, in renderNow self.render(self.m_gl) File /usr/share/doc/pyqt5-examples/examples/opengl/openglwindow.py, line 165, in render gl.glViewport(0, 0, self.width(), self.height()) AttributeError: 'NoneType' object has no attribute 'glViewport' -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages pyqt5-examples depends on: ii libjs-jquery 1.7.2+dfsg-3.2 ii python3-pyqt5 5.3.2+dfsg-3 pyqt5-examples recommends no packages. Versions of packages pyqt5-examples suggests: pn qt5-doc none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779372: qt4-demos: QML UI demos do not run
Package: qt4-demos Version: 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 Severity: normal Dear Maintainer, Run: $ /usr/lib/x86_64-linux-gnu/qt4/bin/qtdemo In QML UI Components, clicking any demo then Display Results in the popup: Failed to launch the example. Could not launch the example. Ensure that it has been built. [Cancel] -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages qt4-demos depends on: ii libc6 2.19-13 ii libgcc1 1:4.9.1-19 ii libgl1-mesa-glx [libgl1] 10.3.2-1 ii libphonon44:4.8.0-4 ii libqt4-declarative4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-designer 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-help 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-network4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-opengl 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-script 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-scripttools4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-sql4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-svg4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-test 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-xml4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-xmlpatterns4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqtcore44:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqtdbus44:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libstdc++64.9.1-19 Versions of packages qt4-demos recommends: ii libqt4-declarative-gestures 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-declarative-particles 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 pn qt4-dev-tools none ii qt4-doc 4:4.8.6+git64-g5dc8b2b+dfsg-2 Versions of packages qt4-demos suggests: ii qt4-qmlviewer 4:4.8.6+git64-g5dc8b2b+dfsg-2+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#779373: Acknowledgement (qt4-demos: browser demo does not work)
Spectrum Analyzer does not work either
Bug#779221: qtquickcontrols5-examples: resizing QT window is jerky, redraw/resize problem
Package: qtquickcontrols5-examples Version: 5.3.2-2 Severity: normal Dear Maintainer, Run /usr/lib/x86_64-linux- gnu/qt5/examples/quick/dialogs/systemdialogs/systemdialogs Drag bottom-right window corner up/down to resize height of window. The window flickers and redraws with widgets in wrong place. If you go really, really slowly then this doesn't happen, but drag at a normal speed and it happens. Tested on both x86 with Radeon and amd64 with Intel graphics (Intel graphics has TearFree vsync on some this is not the problem) -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages qtquickcontrols5-examples depends on: ii libc62.19-13 ii libqt5core5a 5.3.2+dfsg-4+b1 ii libqt5qml5 5.3.2-4 ii libqt5widgets5 5.3.2+dfsg-4+b1 ii qml-module-qtquick-controls 5.3.2-2 ii qml-module-qtquick-dialogs 5.3.2-2 qtquickcontrols5-examples recommends no packages. qtquickcontrols5-examples 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#776673: xfce4-session: xflock4 does not have a man page
Package: xfce4-session Version: 4.10.1-10 Severity: minor Dear Maintainer, Looks like xflock4 is missing a man page. $ man xflock4 No manual entry for xflock4 See 'man 7 undocumented' for help when manual pages are not available. $ dpkg -L xfce4-session|grep /usr/bin /usr/bin /usr/bin/xfce4-session-logout /usr/bin/xfce4-session /usr/bin/xflock4 /usr/bin/xfce4-session-settings /usr/bin/startxfce4 $ dpkg -L xfce4-session|grep man /usr/share/man /usr/share/man/man1 /usr/share/man/man1/xfce4-session-settings.1.gz /usr/share/man/man1/xfce4-session-logout.1.gz /usr/share/man/man1/xfce4-session.1.gz /usr/share/man/man1/startxfce4.1.gz -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages xfce4-session depends on: ii libatk1.0-02.14.0-1 ii libc6 2.19-13 ii libcairo2 1.14.0-2.1 ii libdbus-1-31.8.12-3 ii libdbus-glib-1-2 0.102-1 ii libfontconfig1 2.11.0-6.3 ii libfreetype6 2.5.2-2 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libglib2.0-0 2.42.1-1 ii libgtk2.0-02.24.25-1 ii libice62:1.0.9-1+b1 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-01.36.8-3 ii libpangoft2-1.0-0 1.36.8-3 ii libpolkit-gobject-1-0 0.105-8 ii libsm6 2:1.2.2-1+b1 ii libwnck22 2.30.7-2 ii libx11-6 2:1.6.2-3 ii libxfce4ui-1-0 4.10.0-6 ii libxfce4util6 4.10.1-2 ii libxfconf-0-2 4.10.0-3 ii multiarch-support 2.19-13 ii xfce4-settings 4.10.1-2 ii xfconf 4.10.0-3 Versions of packages xfce4-session recommends: ii dbus-x11 1.8.12-3 ii libpam-systemd 215-10 ii systemd-shim 9-1 ii systemd-sysv 215-10 ii upower 0.99.1-3.1 ii x11-xserver-utils 7.7+3+b1 ii xfdesktop4 4.10.2-3 ii xfwm4 4.10.1-3 pn xscreensaver none Versions of packages xfce4-session suggests: pn fortunes-mod none ii sudo 1.8.10p3-1 -- 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#776674: xfce4-session: xflock4 does not turn off screen due to xset dpms race condition
Package: xfce4-session Version: 4.10.1-10 Severity: normal Dear Maintainer, /usr/bin/xflock4 does: for lock_cmd in \ xlock -mode blank \ slock set -- $lock_cmd if command -v -- $1 /dev/null 21; then $lock_cmd /dev/null 21 # turn off display backlight: xset dpms force off exit fi done But it does not work (presumably xset runs too quickly and slock turns the monitor back on?) It appears the xset call should be something like: sleep 1; xset dpms force off Using a hardcoded sleep does not seem elegant, but it is the suggested fix at http://askubuntu.com/questions/38776/trigger-screensaver-off-monitor and https://wiki.archlinux.org/index.php/Display_Power_Management_Signaling (Also, is there a purpose for doing set -- $lock_cmd when the process then immediately calls exit?) -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages xfce4-session depends on: ii libatk1.0-02.14.0-1 ii libc6 2.19-13 ii libcairo2 1.14.0-2.1 ii libdbus-1-31.8.12-3 ii libdbus-glib-1-2 0.102-1 ii libfontconfig1 2.11.0-6.3 ii libfreetype6 2.5.2-2 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libglib2.0-0 2.42.1-1 ii libgtk2.0-02.24.25-1 ii libice62:1.0.9-1+b1 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-01.36.8-3 ii libpangoft2-1.0-0 1.36.8-3 ii libpolkit-gobject-1-0 0.105-8 ii libsm6 2:1.2.2-1+b1 ii libwnck22 2.30.7-2 ii libx11-6 2:1.6.2-3 ii libxfce4ui-1-0 4.10.0-6 ii libxfce4util6 4.10.1-2 ii libxfconf-0-2 4.10.0-3 ii multiarch-support 2.19-13 ii xfce4-settings 4.10.1-2 ii xfconf 4.10.0-3 Versions of packages xfce4-session recommends: ii dbus-x11 1.8.12-3 ii libpam-systemd 215-10 ii systemd-shim 9-1 ii systemd-sysv 215-10 ii upower 0.99.1-3.1 ii x11-xserver-utils 7.7+3+b1 ii xfdesktop4 4.10.2-3 ii xfwm4 4.10.1-3 pn xscreensaver none Versions of packages xfce4-session suggests: pn fortunes-mod none ii sudo 1.8.10p3-1 -- 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#757435:
One bug report suggests this is fixed by upgrading to kernel 3.16.5 or later.
Bug#771247: chromium: translate does not work
Package: chromium Version: 38.0.2125.101-3 Severity: normal Dear Maintainer, Go to amazon.de Click translate icon (box between cookie and star to right of location bar) Click translate Page is being translated The page is not translated. (On start up, the browser shows the following, possibly related message: Google API keys are missing. Some functionality of Chromium will be disabled.) -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 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 chromium depends on: ii libasound2 1.0.28-1 ii libc62.19-13 ii libcairo21.14.0-2.1 ii libcap2 1:2.24-6 ii libcups2 1.7.5-7 ii libdbus-1-3 1.8.10-1 ii libexpat12.1.0-6+b3 ii libfontconfig1 2.11.0-6.1 ii libfreetype6 2.5.2-2 it libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libglib2.0-0 2.42.0-2 ii libgnome-keyring03.12.0-1+b1 ii libgtk2.0-0 2.24.25-1 ii libharfbuzz0b0.9.35-2 ii libjpeg62-turbo 1:1.3.1-10 ii libnspr4 2:4.10.7-1 ii libnss3 2:3.17.2-1 ii libpango-1.0-0 1.36.8-2 ii libpangocairo-1.0-0 1.36.8-2 ii libpci3 1:3.2.1-3 ii libspeechd2 0.8-6 ii libspeex11.2~rc1.2-1 ii libsrtp0 1.4.5~20130609~dfsg-1.1 ii libstdc++6 4.9.1-19 ii libudev1 215-5+b1 ii libx11-6 2:1.6.2-3 ii libxcomposite1 1:0.4.4-1 ii libxcursor1 1:1.1.14-1+b1 ii libxdamage1 1:1.1.4-2 ii libxext6 2:1.3.3-1 ii libxfixes3 1:5.0.1-2+b1 ii libxi6 2:1.7.4-1+b1 ii libxml2 2.9.1+dfsg1-4 ii libxrandr2 2:1.4.2-1+b1 ii libxrender1 1:0.9.8-1+b1 ii libxslt1.1 1.1.28-2+b2 ii libxss1 1:1.2.2-1 ii libxtst6 2:1.2.2-1+b1 ii xdg-utils1.1.0~rc1+git20111210-7.1 chromium recommends no packages. Versions of packages chromium suggests: ii chromium-inspector 38.0.2125.101-3 pn chromium-l10n none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769957: iceweasel does not use locale for google search but firefox does
Package: iceweasel
Version: 31.2.0esr-3
Severity: normal
Dear Maintainer,
Iceweasel does not localise the Google search but Firefox from upstream does,
indicating a potential packaging issue. To reproduce, set LANG=en_GB.utf8 and
then:
run iceweasel
ctrl-l
enter tv
= results from www.google.com
click shopping
= results from US sellers in $$$
download firefox-33.1.1.tar.bz2 and unpack
run firefox
ctrl-l
enter tv
= result from www.google.co.uk
click shopping
= results from UK sellers in £££
A downstream bug report from Iceweasel in Tails has some hints on this issue,
suggesting that the search engines locale is hardcoded to en-US and google.com.
The bug reporter writes that German, Spanish and French locales are also
affected. Bug report is fix localized iceweasel search engine at
https://labs.riseup.net/code/issues/5380
-- Package-specific info:
-- Extensions information
Name: Adblock Plus
Location: ${PROFILE_EXTENSIONS}/{d10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d}.xpi
Status: enabled
Name: cliget
Location: ${PROFILE_EXTENSIONS}/cli...@zaidabdulla.com.xpi
Status: enabled
Name: Default theme
Location:
/usr/lib/iceweasel/browser/extensions/{972ce4c6-7e08-4474-a285-3208198ce6fd}
Package: iceweasel
Status: enabled
Name: English (GB) Language Pack locale
Location:
/usr/lib/iceweasel/browser/extensions/langpack-en...@iceweasel.mozilla.org.xpi
Package: iceweasel-l10n-en-gb
Status: enabled
Name: Export Cookies
Location: ${PROFILE_EXTENSIONS}/exportcook...@aag.xpi
Status: enabled
Name: Firebug
Location: ${PROFILE_EXTENSIONS}/fire...@software.joehewitt.com.xpi
Status: enabled
-- Plugins information
Name: Gnome Shell Integration
Location: /usr/lib/mozilla/plugins/libgnome-shell-browser-plugin.so
Package: gnome-shell
Status: enabled
Name: Shockwave Flash (11.2.202.406)
Location: /usr/lib/flashplugin-nonfree/libflashplayer.so
Status: enabled
-- Addons package information
ii gnome-shell3.14.1-1 amd64graphical shell for the GNOME des
ii iceweasel 31.2.0esr-3 amd64Web browser based on Firefox
ii iceweasel-l10n 1:31.2.0esr- all English (United Kingdom) language
-- System Information:
Debian Release: jessie/sid
APT prefers testing-updates
APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 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 iceweasel depends on:
ii debianutils 4.4+b1
ii fontconfig2.11.0-6.1
ii libasound21.0.28-1
ii libatk1.0-0 2.14.0-1
ii libc6 2.19-13
ii libcairo2 1.14.0-2.1
ii libdbus-1-3 1.8.10-1
ii libdbus-glib-1-2 0.102-1
ii libevent-2.0-52.0.21-stable-1.1
ii libffi6 3.1-2
ii libfontconfig12.11.0-6.1
ii libfreetype6 2.5.2-2
ii libgcc1 1:4.9.1-19
it libgdk-pixbuf2.0-02.31.1-2+b1
ii libglib2.0-0 2.42.0-2
ii libgtk2.0-0 2.24.25-1
ii libhunspell-1.3-0 1.3.3-3
ii libnspr4 2:4.10.7-1
ii libnss3 2:3.17.2-1
ii libpango-1.0-01.36.8-2
ii libsqlite3-0 3.8.7.1-1
ii libstartup-notification0 0.12-4
ii libstdc++64.9.1-19
ii libvpx1 1.3.0-3
ii libx11-6 2:1.6.2-3
ii libxext6 2:1.3.3-1
ii libxrender1 1:0.9.8-1+b1
ii libxt61:1.1.4-1+b1
ii procps2:3.3.9-8
ii zlib1g1:1.2.8.dfsg-2
iceweasel recommends no packages.
Versions of packages iceweasel suggests:
pn fonts-mathjax none
pn fonts-oflb-asana-math none
ii fonts-stix [otf-stix] 1.1.1-1
ii libcanberra0 0.30-2.1
ii libgnomeui-0 2.24.5-3
ii libgssapi-krb5-2 1.12.1+dfsg-14
pn mozplugger none
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767712: vlc-nox: vlc vlsub does not seem to work
Package: vlc-nox Version: 2.2.0~pre4-1+b1 Severity: normal Dear Maintainer, View Download subtitles Search by hash / Search by name, neither seems to work. Search by hash shows Calculating movie hash next to a white box (progress bar?) and nothing happens. -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-3-amd64 (SMP w/4 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 vlc-nox depends on: ii liba52-0.7.4 0.7.4-17 ii libasound2 1.0.28-1 ii libass50.10.2-3 ii libavahi-client3 0.6.31-4 ii libavahi-common3 0.6.31-4 ii libavc1394-0 0.5.4-2 ii libavcodec56 6:11-2 ii libavformat56 6:11-2 ii libavutil546:11-2 ii libbasicusageenvironment0 2014.01.13-1 ii libbluray1 1:0.6.2-1 ii libc6 2.19-12 ii libcddb2 1.3.2-5 ii libcdio13 0.83-4.2 ii libchromaprint01.2-1 ii libcrystalhd3 1:0.0~git20110715.fdd2f19-11 ii libdbus-1-31.8.8-2 ii libdc1394-22 2.2.3-1 ii libdca00.0.5-7 ii libdirectfb-1.2-9 1.2.10.0-5.1 ii libdvbpsi9 1.2.0-1 ii libdvdnav4 5.0.1-1 ii libdvdread45.0.0-1 ii libebml4 1.3.0-2 ii libfaad2 2.7-8 ii libflac8 1.3.0-2 ii libfontconfig1 2.11.0-6.1 ii libfreetype6 2.5.2-2 ii libfribidi00.19.6-2 ii libgcc11:4.9.1-16 ii libgcrypt201.6.2-4 ii libgnutls-deb0-28 3.3.8-3 ii libgpg-error0 1.16-2 ii libgroupsock1 2014.01.13-1 ii libiso9660-8 0.83-4.2 ii libjpeg62-turbo1:1.3.1-8 ii libkate1 0.4.1-1.1 ii liblircclient0 0.9.0~pre1-1.1 ii liblivemedia23 2014.01.13-1 ii liblua5.2-05.2.3-1.1 ii libmad00.15.1b-8 ii libmatroska6 1.4.1-2 ii libmodplug11:0.8.8.4-4.1 ii libmpcdec6 2:0.1~r459-4.1 ii libmpeg2-4 0.5.1-6 ii libmtp91.1.8-1+b1 ii libncursesw5 5.9+20140913-1 ii libogg01.3.2-1 ii libopus0 1.1-2 ii libpng12-0 1.2.50-2 ii libpostproc52 6:0.git20120821-4 ii libraw1394-11 2.1.0-3 ii libresid-builder0c2a 2.1.1-14 ii libsamplerate0 0.1.8-8 ii libschroedinger-1.0-0 1.0.11-2.1 ii libshine3 3.1.0-2.1 ii libshout3 2.3.1-3 ii libsidplay22.1.1-14 ii libspeex1 1.2~rc1.2-1 ii libspeexdsp1 1.2~rc1.2-1 ii libstdc++6 4.9.1-16 ii libswscale36:11-2 ii libtag1c2a 1.9.1-2.1 ii libtheora0 1.1.1+dfsg.1-3.2 ii libtinfo5 5.9+20140913-1 ii libtwolame00.3.13-1.1 ii libudev1 215-5+b1 ii libupnp6 1:1.6.17-1.2 ii libusageenvironment1 2014.01.13-1 ii libusb-1.0-0 2:1.0.19-1 ii libvcdinfo00.7.24+dfsg-0.2 ii libvlc52.2.0~pre4-1+b1 ii libvlccore82.2.0~pre4-1+b1 ii libvorbis0a1.3.2-1.5 ii libvorbisenc2 1.3.2-1.5 ii libx264-1422:0.142.2431+gita5831aa-1+b1 ii libxml22.9.1+dfsg1-4 ii libzvbi0 0.2.35-3 ii zlib1g 1:1.2.8.dfsg-2 vlc-nox recommends no packages. Versions of packages vlc-nox suggests: pn libdvdcss2 none Versions of packages vlc depends on: ii fonts-freefont-ttf 20120503-4 ii libaa1 1.4p5-43 ii libavcodec566:11-2 ii libavutil54 6:11-2 ii libc6 2.19-12 ii libcaca00.99.beta19-2 ii libegl1-mesa [libegl1-x11] 10.3.1-1 ii libfreetype62.5.2-2 ii libfribidi0 0.19.6-2 ii libgcc1 1:4.9.1-16 ii libgl1-mesa-glx [libgl1]10.3.1-1 ii libgles1-mesa [libgles1]10.3.1-1 ii libgles2-mesa [libgles2]10.3.1-1 ii libice6 2:1.0.9-1 ii libpulse0 5.0-13 ii libqtcore4 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libsdl-image1.2 1.2.12-5+b4 ii libsdl1.2debian 1.2.15-10 ii libsm6 2:1.2.2-1 ii libstdc++6 4.9.1-16 ii libva-drm1
Bug#767713: vlc-plugin-vlsub description unclear
Package: vlc-plugin-vlsub Version: 0.9.12-1.1 Severity: normal Dear Maintainer, vlc-plugin-vlsub is described as an extension for VLC to download subtitles, but the vlc package already includes vlsub: $ dpkg -L vlc-nox|grep -i vlsub /usr/lib/vlc/lua/extensions/VLSub.luac It is not clear whether or not the package vlc-plugin-vlsub is necessary if the user wants subtitles (in which case it should be a dependency, as the vlc gui has the menu item Download subtitles), or whether vlc alone is sufficient (in which case, what is the purpose of this package?). -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766060: gdb: has no man page
Package: gdb Version: 7.7.1+dfsg-3 Severity: normal Dear Maintainer, gdb installs several binaries (gdb, gdbtui, gdb-add-index) that do not have man pages. gcore is the only binary that does have a man page. $ man gdb No manual entry for gdb See 'man 7 undocumented' for help when manual pages are not available. -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-2-amd64 (SMP w/4 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 gdb depends on: ii libc6 2.19-11 ii libexpat1 2.1.0-6 ii liblzma5 5.1.1alpha+20120614-2 ii libncurses5 5.9+20140913-1 ii libpython2.7 2.7.8-10 ii libreadline6 6.3-8 ii libtinfo5 5.9+20140913-1 ii zlib1g1:1.2.8.dfsg-2 Versions of packages gdb recommends: ii gdbserver 7.7.1+dfsg-3 ii libc6-dbg [libc-dbg] 2.19-11 Versions of packages gdb suggests: pn gdb-doc none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764531:
Package: installation-reports Boot method: USB Image version: debian-jessie-DI-b2-i386-xfce-CD-1.iso Date: 20141008 Machine: Virtualbox VM Processor: i5 Memory: 1GB Partitions: /dev/sda1 ext4 Output of lspci -knn (or lspci -nn): Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [O] Install boot loader:[O] Overall install:[E] Comments/Problems: * After install with network cable unplugged, iceweasel does not get installed, so clicking web browser icon on desktop does not launch anything. This is a regression from Wheezy, where iceweasel was installed and the web browser icon worked after a no cable install. Note that on a cable present install on real hardware with the same installer image, Iceweasel did get installed. * After install, `apt-get update` fails, it seems the cdrom is not being disabled like in previous Debian releases, this is a regression from Wheezy: Ign cdrom://[Debian GNU/Linux jessie-DI-b2 _Jessie_ - Official Snapshot i386 xfce-CD Binary-1 20141003-16:52] jessie InRelease Ign cdrom://[Debian GNU/Linux jessie-DI-b2 _Jessie_ - Official Snapshot i386 xfce-CD Binary-1 20141003-16:52] jessie Release.gpg Ign cdrom://[Debian GNU/Linux jessie-DI-b2 _Jessie_ - Official Snapshot i386 xfce-CD Binary-1 20141003-16:52] jessie Release Ign cdrom://[Debian GNU/Linux jessie-DI-b2 _Jessie_ - Official Snapshot i386 xfce-CD Binary-1 20141003-16:52] jessie/main i386 Packages/DiffIndex Ign cdrom://[Debian GNU/Linux jessie-DI-b2 _Jessie_ - Official Snapshot i386 xfce-CD Binary-1 20141003-16:52] jessie/main Translation-en_GB Err cdrom://[Debian GNU/Linux jessie-DI-b2 _Jessie_ - Official Snapshot i386 xfce-CD Binary-1 20141003-16:52] jessie/main i386 Packages Err cdrom://[Debian GNU/Linux jessie-DI-b2 _Jessie_ - Official Snapshot i386 xfce-CD Binary-1 20141003-16:52] jessie/main i386 Packages Err cdrom://[Debian GNU/Linux jessie-DI-b2 _Jessie_ - Official Snapshot i386 xfce-CD Binary-1 20141003-16:52] jessie/main i386 Packages Err cdrom://[Debian GNU/Linux jessie-DI-b2 _Jessie_ - Official Snapshot i386 xfce-CD Binary-1 20141003-16:52] jessie/main i386 Packages Ign cdrom://[Debian GNU/Linux jessie-DI-b2 _Jessie_ - Official Snapshot i386 xfce-CD Binary-1 20141003-16:52] jessie/main Translation-en Err cdrom://[Debian GNU/Linux jessie-DI-b2 _Jessie_ - Official Snapshot i386 xfce-CD Binary-1 20141003-16:52] jessie/main i386 Packages Failed to stat - stat (2: No such file or directory) W: Failed to fetch copy:/var/lib/apt/lists/partial/Debian%20GNU_Linux%20jessie-DI-b2%20%5fJessie%5f%20-%20Official%20Snapshot%20i386%20xfce-CD%20Binary-1%2020141003-16:52_dists_jessie_main_binary-i386_Packages Failed to stat - stat (2: No such file or directory) E: Some index files failed to download. They have been ignored, or old ones used instead. * Contrast with wheezy post-install apt-get where the cdrom lines are ignored: Ign cdrom://[Debian GNU/Linux 7.5.0 _Wheezy_ - Official amd64 xfce-CD Binary-1 20140426-13:35] wheezy Release.gpg Ign cdrom://[Debian GNU/Linux 7.5.0 _Wheezy_ - Official amd64 xfce-CD Binary-1 20140426-13:35] wheezy Release Ign cdrom://[Debian GNU/Linux 7.5.0 _Wheezy_ - Official amd64 xfce-CD Binary-1 20140426-13:35] wheezy/main amd64 Packages/DiffIndex Ign cdrom://[Debian GNU/Linux 7.5.0 _Wheezy_ - Official amd64 xfce-CD Binary-1 20140426-13:35] wheezy/main Translation-en_GB Reading package lists... Done -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764554: xfce4-panel: suspend icon missing
Package: xfce4-panel Version: 4.10.1-1 Severity: minor Dear Maintainer, The actions panel has a suspend action but the icon does not exist: http://imgur.com/xNsWstj The icon is set in plugins/actions/actions.c - the other actions all have corresponding icons and suspend is set to system-suspend.png but that icon does not exist. eg. lock-screen icon is set to system-lock-screen which corresponds to /usr/share/icons/HighContrast/scalable/actions/system-lock-screen.svg or /usr/share/icons/Tango/16x16/actions/system-lock-screen.png But suspend icon is set to system-suspend and there is no /usr/share/icons/.../system-suspend.png There is an icon /usr/share/icons/hicolor/48x48/apps/xfsm-suspend.png which looks like it could be used? -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-2-amd64 (SMP w/4 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-panel depends on: ii exo-utils 0.10.2-4 ii libatk1.0-0 2.12.0-1 ii libc6 2.19-11 ii libcairo2 1.12.16-5 ii libdbus-1-3 1.8.6-2 ii libdbus-glib-1-20.102-1 ii libexo-1-0 0.10.2-4 ii libfontconfig1 2.11.0-6.1 ii libfreetype62.5.2-2 ii libgarcon-1-0 0.2.1-2 ii libgdk-pixbuf2.0-0 2.30.8-1+b1 ii libglib2.0-02.42.0-1 ii libgtk2.0-0 2.24.24-1 ii libice6 2:1.0.9-1 ii libpango1.0-0 1.36.7-1 ii libsm6 2:1.2.2-1 ii libwnck22 2.30.7-2 ii libx11-62:1.6.2-3 ii libxext62:1.3.2-1 ii libxfce4ui-1-0 4.10.0-6 ii libxfce4util6 4.10.1-2 ii libxfconf-0-2 4.10.0-3 ii multiarch-support 2.19-11 xfce4-panel recommends no packages. xfce4-panel 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#763713: [Pkg-xfce-devel] Bug#763713: xfce4-power-manager-settings: minimum window size is too big
On 4 October 2014 09:15, Yves-Alexis Perez cor...@debian.org wrote: On jeu., 2014-10-02 at 01:30 +0100, Chris Bainbridge wrote: Running /usr/bin/xfce4-power-manager-settings opens a window with a default size that is wider than the screen. The buttons are expanded to be huge, taking up the majority of the horizontal space. The window can not be made smaller. The window is 453x509 here, which is hardly “wide”, especially by today standards. 1107x534 here. http://imgur.com/G7c6hDE -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763713: [Pkg-xfce-devel] Bug#763713: xfce4-power-manager-settings: minimum window size is too big
On 4 October 2014 11:55, Yves-Alexis Perez cor...@debian.org wrote: On sam., 2014-10-04 at 11:05 +0100, Chris Bainbridge wrote: On 4 October 2014 09:15, Yves-Alexis Perez cor...@debian.org wrote: On jeu., 2014-10-02 at 01:30 +0100, Chris Bainbridge wrote: Running /usr/bin/xfce4-power-manager-settings opens a window with a default size that is wider than the screen. The buttons are expanded to be huge, taking up the majority of the horizontal space. The window can not be made smaller. The window is 453x509 here, which is hardly “wide”, especially by today standards. 1107x534 here. http://imgur.com/G7c6hDE Also, it's quite possible to resize it. It can be resized to be bigger, but 1107x534 is the minimum size. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763713: [Pkg-xfce-devel] Bug#763713: xfce4-power-manager-settings: minimum window size is too big
The problem happens when the laptop battery is not recognised so the Linux kernel instead use the hex string ID of the manufacturer and model. These strings are 31 characters each. On the Device tab the left side contains a 1 line string of the full $manufacturer $model string, which for an unrecognised battery will be 63 characters long. The container expands to hold this and keep it on a single line, which causes the whole window to increase in size, which in turn expands all of the tabs to fit. The following patch will fix the width of the devices column at 200px to stop it from being expanded: diff --git a/settings/xfpm-settings.c b/settings/xfpm-settings.c index d736cd4..f27fa70 100644 --- a/settings/xfpm-settings.c +++ b/settings/xfpm-settings.c @@ -2093,6 +2093,8 @@ xfpm_settings_dialog_new (XfconfChannel *channel, gboolean auth_suspend, gtk_tree_view_set_rules_hint (GTK_TREE_VIEW (sideview),TRUE); col = gtk_tree_view_column_new (); +gtk_tree_view_column_set_sizing(col, GTK_TREE_VIEW_COLUMN_FIXED); +gtk_tree_view_column_set_fixed_width(col, 200); renderer = gtk_cell_renderer_pixbuf_new (); -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763713: [Pkg-xfce-devel] Bug#763713: xfce4-power-manager-settings: minimum window size is too big
On 4 October 2014 14:07, Chris Bainbridge chris.bainbri...@gmail.com wrote: The problem happens when the laptop battery is not recognised so the Linux kernel instead use the hex string ID of the manufacturer and model. These strings are 31 characters each. On the Device tab the left side contains a 1 line string of the full $manufacturer $model string, which for an unrecognised battery will be 63 characters long. The container expands to hold this and keep it on a single line, which causes the whole window to increase in size, which in turn expands all of the tabs to fit. Example: http://imgur.com/uv2sIXw -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#748753:
On 2 October 2014 10:41, Julien Cristau jcris...@debian.org wrote: On Wed, Oct 1, 2014 at 11:24:41 +0100, Chris Bainbridge wrote: Jessie gets frozen in 35 days. It would be a shame to see it released with buggy Intel GPU drivers that are no longer recommended or distributed by upstream. Upstream clearly doesn't recommend anything newer, since the only thing they've put out in the last year is a pile of git snapshots. Intel is now distributing their own drivers on 01.org - the latest version (2014Q3) includes xf86-video-intel 2.99.911. The recommendation to upgrade to at least 2.99.908 for important bug fixes came directly from their GPU developers. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#748753:
Is there any chance of this being fixed in time for Jessie? Jessie gets frozen in 35 days. It would be a shame to see it released with buggy Intel GPU drivers that are no longer recommended or distributed by upstream. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758619:
This bug now exists in Testing (glib2.0-2.42.0 has just been migrated to Testing). reportbug --ui=text xxx still works. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763610: virtualbox crash on resume VM with 3D acceleration + Intel GPU
Package: virtualbox
Version: 4.3.14-dfsg-1
Severity: important
Dear Maintainer,
https://www.virtualbox.org/ticket/11938
To reproduce:
- Install Ubuntu 14.04 in a VM
- Install VirtualBox tools from VB GUI
- Enable 3D acceleration
- Boot to desktop and login
- Make a snapshot
- Close VM
- Restore snapshot
- Start VM
- Crash!
The error is:
Failed to open a session for the virtual machine testvm
No error info.
Result Code:
NS_ERROR_CALL_FAILED (0x800706BE)
Component:
ProgressProxy
Interface:
IProgress {c20238e4-3221-4d3f-8891-81ce92d9f913}
I posted a backtrace at
https://www.virtualbox.org/ticket/11938#comment:25
The bug has been present in Debian Jessie for over 5 months now.
-- System Information:
Debian Release: jessie/sid
APT prefers testing-updates
APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16-2-amd64 (SMP w/4 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 virtualbox depends on:
ii adduser 3.113+nmu3
ii dpkg 1.17.13
ii libc62.19-11
ii libcurl3 7.38.0-2
ii libgcc1 1:4.9.1-15
ii libgsoap52.8.17-1
ii libpng12-0 1.2.50-2
ii libpython2.7 2.7.8-7
ii libsdl1.2debian 1.2.15-10
ii libssl1.0.0 1.0.1i-2
ii libstdc++6 4.9.1-15
ii libvncserver00.9.9+dfsg-6+b1
ii libvpx1 1.3.0-2.1
ii libx11-6 2:1.6.2-3
ii libxcursor1 1:1.1.14-1
ii libxext6 2:1.3.2-1
ii libxml2 2.9.1+dfsg1-4
ii libxmu6 2:1.1.2-1
ii libxt6 1:1.1.4-1
ii python 2.7.8-1
ii python2.72.7.8-7
ii zlib1g 1:1.2.8.dfsg-2
Versions of packages virtualbox recommends:
ii libgl1-mesa-glx [libgl1] 10.2.6-1
ii libqt4-opengl 4:4.8.6+git64-g5dc8b2b+dfsg-2
ii libqtcore44:4.8.6+git64-g5dc8b2b+dfsg-2
ii libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-2
ii virtualbox-dkms 4.3.14-dfsg-1
ii virtualbox-qt 4.3.14-dfsg-1
Versions of packages virtualbox suggests:
pn vde2none
pn virtualbox-guest-additions-iso none
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763713: xfce4-power-manager-settings: minimum window size is too big
Package: xfce4-power-manager Version: 1.4.0-2 Severity: normal Dear Maintainer, Running /usr/bin/xfce4-power-manager-settings opens a window with a default size that is wider than the screen. The buttons are expanded to be huge, taking up the majority of the horizontal space. The window can not be made smaller. -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-2-amd64 (SMP w/4 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-power-manager depends on: ii libc6 2.19-11 ii libdbus-1-3 1.8.6-2 ii libdbus-glib-1-2 0.102-1 ii libgdk-pixbuf2.0-02.30.8-1 ii libglib2.0-0 2.42.0-1 ii libgtk2.0-0 2.24.24-1 ii libnotify40.7.6-2 ii libupower-glib3 0.99.1-3 ii libx11-6 2:1.6.2-3 ii libxext6 2:1.3.2-1 ii libxfce4ui-1-04.10.0-6 ii libxfce4util6 4.10.1-2 ii libxfconf-0-2 4.10.0-3 ii libxrandr22:1.4.2-1 ii upower0.99.1-3 ii xfce4-power-manager-data 1.4.0-2 Versions of packages xfce4-power-manager recommends: ii libpam-systemd 208-8 ii xfce4-power-manager-plugins 1.4.0-2 xfce4-power-manager 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#728312: closed by Andreas Henriksson andr...@fatal.se (Re: Bug#728312: libpam-gnome-keyring: does not properly kill gnome-keyring-daemon before exit, race condition causes pam umount fail)
Does that mean the Wheezy package is being bumped to 3.12.0? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#542899:
os-prober man page is still missing in 1.64 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756815: ruby: missing man pages for testrb, rdoc, gem
Package: ruby Version: 1:2.1.0.1 Severity: normal Dear Maintainer, On jessie: $ man rdoc man: warning: /usr/share/man/man1/rdoc.1.gz is a dangling symlink No manual entry for rdoc etc. -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2-amd64 (SMP w/4 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 ruby depends on: ii ruby2.1 2.1.2-2 ruby recommends no packages. Versions of packages ruby suggests: pn rinone pn ruby-dev none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752894: trickle segfault crash, fix available
Package: trickle
Version: 1.07-10
Severity: normal
Tags: upstream patch
Dear Maintainer,
As reported here: https://bugs.archlinux.org/task/35872
trickle segfaults repeatedly on some applications (eg. bitcoin-qt). The
explanation and fix patch are available in the Arch bug report.
-- System Information:
Debian Release: jessie/sid
APT prefers testing-updates
APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.14-1-amd64 (SMP w/4 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 trickle depends on:
ii libbsd0 0.6.0-2
ii libc6 2.19-3
ii libevent-2.0-5 2.0.21-stable-1
trickle recommends no packages.
trickle suggests no packages.
-- no debconf information
--- trickle-overload.c.orig 2013-06-21 00:23:01.053833665 -0400
+++ trickle-overload.c 2013-06-21 01:19:03.574792790 -0400
@@ -393,18 +393,14 @@ select_delay(struct delayhead *dhead, st
}
static struct delay *
-select_shift(struct delayhead *dhead, struct timeval *inittv,
+select_shift(struct delayhead *dhead, struct timeval *difftv,
struct timeval **delaytv)
{
- struct timeval curtv, difftv;
struct delay *d;
struct sockdesc *sd;
- gettimeofday(curtv, NULL);
- timersub(curtv, inittv, difftv);
-
TAILQ_FOREACH(d, dhead, next) {
- if (timercmp(d-delaytv, difftv, ))
+ if (timercmp(d-delaytv, difftv, ))
break;
sd = d-sd;
@@ -413,7 +409,7 @@ select_shift(struct delayhead *dhead, st
}
if (d != NULL)
- timersub(d-delaytv, difftv, *delaytv);
+ timersub(d-delaytv, difftv, *delaytv);
else
*delaytv = NULL;
@@ -431,8 +427,8 @@ _select(int nfds, fd_set *rfds, fd_set *
{
struct sockdesc *sd;
fd_set *fdsets[] = { wfds, rfds }, *fds;
- struct timeval *delaytv, *selecttv = NULL, *timeout = NULL, _timeout,
- inittv, curtv, difftv;
+ struct timeval *delaytv, _delaytv, *selecttv = NULL, *timeout = NULL,
+ _timeout, inittv, curtv, difftv;
short which;
struct delayhead dhead;
struct delay *d, *_d;
@@ -462,15 +458,18 @@ _select(int nfds, fd_set *rfds, fd_set *
FD_ISSET(sd-sock, fds)
select_delay(dhead, sd, which)) {
FD_CLR(sd-sock, fds);
-nfds--;
}
gettimeofday(inittv, NULL);
curtv = inittv;
d = TAILQ_FIRST(dhead);
- delaytv = d != NULL ? d-delaytv : NULL;
+ if (d != NULL) {
+ _delaytv = d-delaytv;
+ delaytv = _delaytv;
+ } else
+ delaytv = NULL;
+ timersub(curtv, inittv, difftv);
again:
- timersub(inittv, curtv, difftv);
selecttv = NULL;
if (delaytv != NULL)
@@ -498,15 +497,15 @@ _select(int nfds, fd_set *rfds, fd_set *
#endif /* DEBUG */
if (ret == 0 delaytv != NULL selecttv == delaytv) {
- _d = select_shift(dhead, inittv, delaytv);
+ gettimeofday(curtv, NULL);
+ timersub(curtv, inittv, difftv);
+ _d = select_shift(dhead, difftv, delaytv);
while ((d = TAILQ_FIRST(dhead)) != _d) {
FD_SET(d-sd-sock, fdsets[d-which]);
- nfds++;
TAILQ_REMOVE(dhead, d, next);
free(d);
}
- gettimeofday(curtv, NULL);
goto again;
}
Bug#718272:
For example: if we release Debian Jessie with version 0.8 of bitcoin, and a security bug is found in that version and fixed upstream, the fix may be based on top of version 0.10 and unable to be ported to 0.8. A Debian package is allowed to bump versions for a security fix. Is this any different to the Chromium situation? Chromium-35 is already in wheezy despite only being released one month ago. Similar reasoning; Chromium upstream do not support backported security fixes, they just release a new version. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#718272:
Luke-Jr wrote: I agree with Scott's assessment, although I would note that Debian *does* have a suite that addresses the needs of Bitcoin: stable-updates. Mandatory protocol rule changes would seem to fall within the broken by the flow of time category. Thoughts? I agree. Scott Howard wrote: I think this is the way to go once bitcoin version 1.0 (or the equivalent) is released. It requires users to enable the stable-updates repository This is not necessary as the debian-installer already enables stable-updates by default. we should block migration to testing until either upstream supports stable releases or we have a volunteer that works closely enough with upstream code (an upstream developer) that is will to backport security and network- related fixes. Backporting is not necessary. The package can be version bumped for a security update, or version bumped in stable-updates for non-security changes. In the case of Bitcoin, mandatory network changes could arguably be considered security updates if they prevent the bitcoin server from working, because being unable to update the copy of the blockchain would open up additional attack vectors. tor has very similar restrictions (version 1.0, network protocol could change) and yet it is in both stable and testing. Testing already has other software (cgminger, bfgminer) that is reliant on the bitcoin protocol. Given all this, I do not think that the problems presented in this bug are a reason to hold up bitcoin from entering testing or, ultimately, stable. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750597: gnome-terminal default colours are black-on-black in XFCE (use colours from system theme)
Package: gnome-terminal Version: 3.12.2-1 Severity: normal Dear Maintainer, When starting gnome-terminal in XFCE, text is invisible because it is black-on- black. Unsetting Use colours from system theme in profile and selecting a Built-in scheme (eg. white on black) worksaround the problem. Would be nice if the default was white-on-black in XFCE, as it is a non-obvious problem for a user. -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/4 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 dconf-gsettings-backend [gsettings-backend] 0.20.0-2 ii gconf-service3.2.6-2 ii gnome-terminal-data 3.12.2-1 ii gsettings-desktop-schemas3.8.2-2 ii libatk1.0-0 2.12.0-1 ii libc62.18-7 ii libcairo-gobject21.12.16-2 ii libcairo21.12.16-2 ii libdconf10.20.0-2 ii libgconf-2-4 3.2.6-2 ii libgdk-pixbuf2.0-0 2.30.7-1 ii libglib2.0-0 2.40.0-3 ii libgtk-3-0 3.12.2-1 ii libnautilus-extension1a 3.8.2-3 ii libpango-1.0-0 1.36.3-1 ii libpangocairo-1.0-0 1.36.3-1 ii libuuid1 2.20.1-5.7 ii libvte-2.90-91:0.36.2-1 ii libx11-6 2:1.6.2-2 Versions of packages gnome-terminal recommends: ii dbus-x11 1.8.2-1 ii gvfs 1.20.2-1 ii yelp 3.12.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#748753: closed by maximilian attems m...@debian.org (Bug#748753: fixed in xserver-xorg-video-intel 2:2.99.911+git20140529-1~exp1)
I’m unsure if we want to upload random snapshot releases to sid, which is why I didn’t do that. Feel free to upload it to experimental, though. I wasn't actually suggesting making a random snapshot of the git source from upstream. The latest stable release from Intel is 2014Q1 which includes video-intel-2.99.910. Yes, it is a snapshot, but it is not a random one - it is the same one being used by Intel in the stable 1.0.5 release of their official Intel Graphics Installer. If it is good enough for Intel to use in a stable release of their graphics installer, then imho it ought to be good enough for Debian Unstable/Testing. 2.99.910 is also the version used in Ubuntu 14.04, which means it has already received much wider testing than any possible alternative snapshot. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#748753: closed by maximilian attems m...@debian.org (Bug#748753: fixed in xserver-xorg-video-intel 2:2.99.911+git20140529-1~exp1)
On 30 May 2014 16:28, maximilian attems m...@debian.org wrote: On Fri, May 30, 2014 at 11:52:39AM +0100, Chris Bainbridge wrote: I’m unsure if we want to upload random snapshot releases to sid, which is why I didn’t do that. Feel free to upload it to experimental, though. I wasn't actually suggesting making a random snapshot of the git source from upstream. Whatever you personally wish is fine for your own, but may not be for a distribution. In any case this is still only an experimental upload. The chosen version is a Maintainers decision and I didn't see you step up to such responsibility. Maximilian, firstly thank you for your work. I did not mean to sound unappreciative. If it would help, I would be happy to take responsibility for the decision to release video-intel-2.99.910 (or any other version recommended by upstream) to Debian unstable. The problem with putting an update into experimental is that it does not benefit the vast majority of users, who do not have experimental enabled. I did not open this bug just to fix my own personal problem, I opened this bug so that all Debian users with Intel graphics could get the benefit of a newer stack with significant bug fixes and which is being recommended by upstream. The Debian FAQ defines experimental as packages and tools which are still being developed, and are still in the alpha testing stage. Users shouldn't be using packages from here, because they can be dangerous and harmful even for the most experienced people. imho this is not the appropriate description of a driver that Intel is already shipping as part of their own enablement stack. A newer snapshot was deemed to have better hardware support thanks to all fixes piled up in git, both for Haswell and beyond. Yes, I'm not against having a git snapshot for experimental use but it is not going to fix the issue of the drivers in sid and jessie being 6 months behind what Intel and Ubuntu are both shipping today. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#748753: xserver-xorg-video-intel: please update, jessie/sid version 2.21.15 is 9 months old
Package: xserver-xorg-video-intel Version: 2:2.21.15-2+b1 Severity: normal Dear Maintainer, Please release an updated version of xserver-xorg-video-intel. The latest version in Debian is 2.21.15, which was released by upstream 9 months ago. Since then there have been many bug fixes and performance improvements. (The latest release of the Intel Graphics Stack from 01.org is 2014Q1, which includes video-intel-2.99.910, upstream recommends upgrading to at least 2.99.908 for bug fixes). -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.14-1-amd64 (SMP w/4 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 xserver-xorg-video-intel depends on: ii libc6 2.18-5 ii libdrm-intel1 2.4.54-1 ii libdrm22.4.54-1 ii libpciaccess0 0.13.2-1 ii libpixman-1-0 0.32.4-1 ii libudev1 204-8 ii libx11-6 2:1.6.2-1 ii libx11-xcb12:1.6.2-1 ii libxcb-dri2-0 1.10-2 ii libxcb-util0 0.3.8-2 ii libxcb11.10-2 ii libxv1 2:1.0.10-1 ii libxvmc1 2:1.0.8-1 ii xserver-xorg-core [xorg-video-abi-15] 2:1.15.1-1 xserver-xorg-video-intel recommends no packages. xserver-xorg-video-intel 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#748782: gnome-settings-daemon: man page describes --no-daemon option but it does not work
Package: gnome-settings-daemon Version: 3.8.5-2 Severity: normal Dear Maintainer, Not sure whether the problem here is an inaccurate man page, or broken option. The Changelog and NEWS of the source do refer to an option '--no-daemon' - so it existed at some point. man gnome-settings-daemon --no-daemon Do not detach the daemon process from its controlling terminal $ gnome-settings-daemon --no-daemon ** (gnome-settings-daemon:6733): WARNING **: Unknown option --no-daemon -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.14-1-amd64 (SMP w/4 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-settings-daemon depends on: ii dconf-gsettings-backend [gsettings-backend] 0.20.0-2 ii gsettings-desktop-schemas3.8.2-2 ii libc62.18-5 ii libcairo21.12.16-2 ii libcanberra-gtk3-0 0.30-2 ii libcanberra0 0.30-2 ii libcolord1 1.0.6-1 ii libcups2 1.7.2-3 ii libfontconfig1 2.11.0-5 ii libgdk-pixbuf2.0-0 2.30.7-1 ii libglib2.0-0 2.40.0-3 ii libgnome-desktop-3-7 3.8.4-2 ii libgtk-3-0 3.12.1-1 ii libgudev-1.0-0 204-8 ii libibus-1.0-51.5.5-1 ii liblcms2-2 2.6-1 ii libnotify4 0.7.6-2 ii libpackagekit-glib2-16 0.8.17-2 ii libpango-1.0-0 1.36.3-1 ii libpulse-mainloop-glib0 5.0-2 ii libpulse05.0-2 ii librsvg2-2 2.40.2-1 ii libupower-glib1 0.9.23-2+b2 ii libwacom20.8-1 ii libx11-6 2:1.6.2-1 ii libxfixes3 1:5.0.1-1 ii libxi6 2:1.7.2-1 ii libxkbfile1 1:1.0.8-1 ii libxtst6 2:1.2.2-1 ii nautilus-data3.8.2-3 ii systemd 204-8 Versions of packages gnome-settings-daemon recommends: ii pulseaudio 5.0-2 Versions of packages gnome-settings-daemon suggests: ii gnome-screensaver3.6.1-1 ii metacity [x-window-manager] 1:2.34.13-1 ii x11-xserver-utils7.7+2 ii xfwm4 [x-window-manager] 4.10.1-2 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746962: netcfg: wifi autoconfiguration after 3 second link detect timeout
Package: netcfg In bug #739668 (wheezy install report, see section 13) I had problems connecting from a laptop to a particular AP from a commercial wifi provider using the Debian installer. At the same time a phone next to the laptop had no such problems, and the same laptop running a non-Linux OS had no problems. The failure to connect was repeatable until at some point where it did connect, and it then worked from that point on (it seems some details were cached on the AP and it began to behave differently, rdnssd began to return the hostname that had been used on the first working connection). The log of the failed connection shows netcfg reporting: Reached timeout for link detection on wlan0 Commencing network autoconfiguration on wlan0 It looks like netcfg ignores that link is not up yet and tries to configure it anyway? Is this appropriate for wifi, should it not wait for the association to complete before trying to configure the interface? Bug #610752 mentions the 3 second timeout was introduced based on a bit of testing - was this testing done on Wifi connections, which may perhaps have higher delays than wired ones? With the closing of #414117, we've introduced a more robust method of detecting which network interfaces we want to configure have link. This is required because link autonegotiation (and other associated shenanigans like 802.1X authentication) can take some time. The problem is, the Ethernet spec is fairly quiet on the subject of precisely how long we need to wait. Based on a bit of testing, the value of 3 seconds for the wait time has been set as the default Bug #537271 comment says: btw, (unrelated to #537271), it seems to me that 3 seconds is a fairly short value for NETCFG_LINK_WAIT_TIME. i'm pretty sure i've seen link-up take longer than that on occasion before, depending on NIC chipset, switch, autonegotiation latency, etc. 5 - 10 seconds would be a more conservative default, given that there's no penalty if link-up occurs before the timeout. Logs follow. The logs of the failed connection show: Feb 20 06:21:32 netcfg[6576]: DEBUG: State is now 0 Feb 20 06:21:32 netcfg[6576]: DEBUG: Want link on wlan0 Feb 20 06:21:32 netcfg[6576]: INFO: Waiting time set to 3 Feb 20 06:21:32 netcfg[6576]: INFO: ethtool-lite: wlan0 is disconnected. Feb 20 06:21:35 netcfg[6576]: INFO: Reached timeout for link detection on wlan0 Feb 20 06:21:35 netcfg[6576]: DEBUG: Commencing network autoconfiguration on wlan0 Feb 20 06:21:35 netcfg[6576]: DEBUG: rdnssd started; PID: 7110 .. Feb 20 06:21:38 netcfg[6576]: DEBUG: ip line: 6: wlan0: NO-CARRIER,BROADCAST,MULTICAST,UP mtu 1500 qdisc mq qlen 1000 Feb 20 06:21:38 netcfg[6576]: DEBUG: ip line: link/ether 20:c9:d0:82:f9:31 brd ff:ff:ff:ff:ff:ff Feb 20 06:21:38 netcfg[6576]: INFO: No IPv6 support found... how does that happen? Feb 20 06:21:38 netcfg[6576]: DEBUG: Stopping rdnssd, PID 7110 Feb 20 06:21:38 netcfg[6576]: DEBUG: No RA received; attempting IPv4 autoconfig Feb 20 06:21:38 netcfg[6576]: WARNING **: Started DHCP client; PID is 7136 Feb 20 06:21:57 main-menu[298]: (process:6575): udhcpc (v1.20.2) started Feb 20 06:21:57 main-menu[298]: 6575): Sending discover... Feb 20 06:22:03 netcfg[6576]: DEBUG: Reading nameservers from /etc/resolv.conf Feb 20 06:22:03 netcfg[6576]: DEBUG: Read nameserver 192.168.0.1 Feb 20 06:22:03 netcfg[6576]: DEBUG: Read nameserver 192.168.1.1 [ 1012.239700] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07) [ 1012.300546] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 1043.990586] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07) [ 1044.051438] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 1224.676597] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07) [ 1224.737438] ADDRCONF(NETDEV_UP): wlan0: link is not ready The logs of a successful connection look like: Feb 20 06:52:06 netcfg[6604]: INFO: Activating interface wlan0 Feb 20 06:52:06 kernel: [ 296.020570] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07) Feb 20 06:52:06 netcfg[6604]: DEBUG: State is now 0 Feb 20 06:52:06 netcfg[6604]: DEBUG: Want link on wlan0 Feb 20 06:52:06 netcfg[6604]: INFO: Waiting time set to 3 Feb 20 06:52:06 kernel: [ 296.081405] ADDRCONF(NETDEV_UP): wlan0: link is not ready Feb 20 06:52:07 kernel: [ 296.264447] wlan0: authenticate with d4:ca:6d:25:d5:d7 (try 1) Feb 20 06:52:07 kernel: [ 296.272201] wlan0: authenticated Feb 20 06:52:07 kernel: [ 296.272406] wlan0: associate with d4:ca:6d:25:d5:d7 (try 1) Feb 20 06:52:07 kernel: [ 296.281454] wlan0: RX AssocResp from d4:ca:6d:25:d5:d7 (capab=0x421 status=0 ai d=2) Feb 20 06:52:07 kernel: [ 296.281458] wlan0: associated Feb 20 06:52:07 kernel: [ 296.282419] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready Feb 20 06:52:07 netcfg[6604]: INFO: ethtool-lite: wlan0 is connected. Feb 20 06:52:07 netcfg[6604]: INFO: Found link on wlan0 Feb 20
Bug#746963: check-missing-firmware only works with FAT filesystems but does not mention this
Package: debian-installer The installer says The firmware can be loaded from removable media, such as a USB stick or floppy. As a Linux user, it would seem reasonable to assume that it might work with ext2 formatted media, so the fact that it does not, should be stated: The firmware can be loaded from MSDOS/FAT-formatted removable media, such as a USB stick or floppy or The firmware can be loaded from MSDOS filesystem on removable media, such as a USB stick or floppy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746966: debian-live: HiDPI support needed for debian-installer
Package: debian-live After booting the netinst iso, the text of the Debian installer is very small on HiDPI displays, for many users it will be unreadable. This problem is going to get worse as higher resolution 4k laptops begin to appear. I am filing this against debian-live as it seems that early in the boot process would be the right place to reconfigure the console with larger fonts (similar to FONTSIZE in /etc/default/console-setup ) rather than in debian-installer itself, which afaik does not manipulate font sizes. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#739668:
0. error prefix is not set - mentioned in #700974 and #707998 but no specific open bug? 1. out-of-date documentation - bug #740500 2. missing documentation - bug #740500 3. bad GPT checksum - bug #740504 4. grub no hidpi - upstream (apparently some Ubuntu developers are working to fix it, search Ubuntu Developers Plan HiDPI Work On GRUB) 5. grub minor video corruption - something similar in bug #707998 and #700656 6. Debian installer no hidpi - bug #746966 7. Debian installer no hidpi - bug #746966 8. automatic keymap detection - bug #420818 9. check-missing-firmware incorrect missing list - bug #740502 10. check-missing-firmware incorrect bad copy fn - bug #740502 11. check-missing-firmware does not work with partitions - bug #740503 12. mmc0: Timeout - bug 711526 13. netcfg ignores link not up - bug #746962 14. check-missing-firmware case-sensitive - bug #740501 15. check-missing-firmware only works with FAT filesystems but does not mention this - bug #746963 16. 17. 18. 19. grub hidpi screen sizing fail - fixed upstream in later grub versions (now works ok on jessie, ubuntu 14) 20. [drm:intel_dsm_platform_mux_info] *ERROR* MUX INFO call failed - bug #685108 firmware-7.4.0-amd64-netinst.iso f1. No broadcom b43 firmware - bug #740499 Regarding the many reported problems with XFCE livecd, if I have time I will retry with the 7.5 livecd and post a separate bug. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747042: jessie installer errors: fbdev driver didn't call xf86SetGamma / Fatal server error
Package: xserver-xorg-video-fbdev-udeb Version: 1:0.4.4-1+b1 Booting debian-jessie-DI-a1-amd64-netinst.iso or debian-testing-amd64-netinst.iso(20140504) and starting Graphical Install, console shows: (WW) The fbdev driver didn't call xf86SetGamma to initialise the gamma values PLEASE FIX THE 'fbdev' DRIVER! (EE) Fatal server error: (EE) Server is already active for display 0 Despite this, xorg seems to work ok. Reproduced on laptop and VirtualBox. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#739669:
0. bad GPT checksum - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740504 1. grub no hidpi support - upstream 2. bad documentation - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740500 3. minor grub video corruption - ? 4. Debian installer hiDPI support - http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746966 5. Touchpad does not work - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734154 6. wifi not detected - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725714 7. can not load firmware - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725714 8. The fbdev driver didn't call xf86SetGamma - http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747042 9. Fatal server error - http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747042 10. Can not install on existing btrfs - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721847 11. ? b43 driver? 12. rdate: Invalid cookie received, packet rejected - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=502338 13. fixed upstream 14. no point pursuing until firmware bugs 725714 and 725714 get fixed The post install issues can be dealt with elsewhere. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
