Bug#884829: Still present in Debian 11
A small update: I managed to rebuild the xserver-xorg-core package with the patch applied, but the leak persists. So while it manifests the same way and can be triggered by the same application, my problem seems to have a different cause. On a second thought, it makes sense: if I understand it correctly, XAA, EXA, UXA etc. were replaced by Glamor in recent years. And from the Xorg log it seems that that's what my laptop uses (Intel HD 5500), so I should not experience any issues coming from the EXA code, right? I'm not very experienced with Valgrind, but I'll send an update if I manage to set it up and find anything of interest. Martin P.S. I had no clue about this transition to Glamor; Debian now generally works well out of the box, so I'm not learning about new stuff by constantly fixing stuff. :))
Bug#884829: Still present in Debian 11
Hi, I can confirm this bug still exists in xserver-xorg-core 2:1.20.11-1+deb11u1; I have been suffering from it ever since I upgraded from Debian 10 to Debian 11 a few months ago. The memory usage of Xorg process keeps growing until eventually the laptop becomes unresponsive and OOM killer starts reaping random processes and everything comes crashing down. In my case, I tracked the problem mainly to xfdesktop4 and xfce4-panel (leaking about 5 MB per hour when the machine is idle). Only when I kill both of them the increase in memory consumption stops, although the already consumed memory is not released. Using the machine makes the rate of leaking worse, so clearly there are many other sources that can trigger the leak. I can also confirm that if I install audacious and play it with the visualization on, the leak increases to about 57 MB per hour, so the problem I experience is very likely the same one as reported here. I'm really happy to finally learn I'm not crazy and someone else noticed the issue as well (although I did not expect it to go all the way back to 2017). Is there anything I can do to help move this along? Should I try testing the patch? Or open a bug report upstream? Thanks, Martin
Bug#778355: linux-image-3.16.0-4-amd64: Unable to mount SD card with ext4 after suspend
Package: src:linux Version: 3.16.7-ckt2-1 Severity: normal Dear Maintainers, I ran into a problem with an SD card using the ext4 filesystem; it seems, that after suspending my laptop and removing the card, it cannot be mounted again unless I reboot the whole system, since ext4 vacated the mountpoint, but some internal kernel structures still see the card as mounted (if I understand it correctly). The mount attempt fails with message mount: mount /dev/mmcblk0p2 on /mnt/virtual failed: File exists and in dmesg, I can see 3 Call Traces and some references to already existing /proc/fs/ext4/mmcblk0p2 and /proc/fs/jbd2/mmcblk0p2-8 (that are still stuck there even after I physically disconnect the card). It seems that the issue was first discovered 3 years ago by Stefan Bader, but he was not able to do anything about it: https://bugs.launchpad.net/debian/+bug/913860 Has the situation described in comment #4 improved? I do not understand the details, but I assume this patch may have something to do with it: http://www.spinics.net/lists/linux-fsdevel/msg71295.html It seems that the patch was not accepted, though, the issue is likely more complex than ext4 forgets to clean up its stuff after forced unmount. Best regards, Martin Pavelek -- Package-specific info: ** Version: Linux version 3.16.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 4.8.3 (Debian 4.8.3-16) ) #1 SMP Debian 3.16.7-ckt2-1 (2014-12-08) ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 root=UUID=0d377c28-a14d-4365-ab55-3d9f001fb7b5 ro quiet pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 nmi_watchdog=0 acpi_osi= ** Tainted: WO (4608) * Taint on warning. * Out-of-tree module has been loaded. ** Kernel log: [3094115.511827] [811c55ca] ? do_mount+0x23a/0xac0 [3094115.511830] [81155bfd] ? memdup_user+0x3d/0x70 [3094115.511832] [811c6141] ? SyS_mount+0x81/0xc0 [3094115.511835] [8150d32d] ? system_call_fast_compare_end+0x10/0x15 [3094115.511836] ---[ end trace 016da6b94d1a2c2a ]--- [3094115.516396] [ cut here ] [3094115.516401] WARNING: CPU: 3 PID: 4804 at /build/linux-CMiYW9/linux-3.16.7-ckt2/fs/proc/generic.c:315 proc_register+0xc0/0x140() [3094115.516402] proc_dir_entry 'jbd2/mmcblk0p2-8' already registered [3094115.516403] Modules linked in: rtsx_usb_sdmmc usbtouchscreen xt_connmark iptable_mangle vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) msr btrfs xor raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c nls_utf8 nls_cp437 vfat fat mmc_block dm_crypt algif_skcipher af_alg dm_mod ipt_MASQUERADE iptable_filter iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables bridge stp llc rfcomm tun ctr ccm rtsx_usb_ms mmc_core memstick rtsx_usb bnep binfmt_misc cpufreq_powersave cpufreq_userspace cpufreq_conservative cpufreq_stats pci_stub ecb btusb bluetooth 6lowpan_iphc uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common videodev media hid_generic usbhid hid usb_storage joydev arc4 iwldvm mac80211 x86_pkg_temp_thermal intel_powerclamp [3094115.516441] intel_rapl coretemp kvm_intel kvm crc32_pclmul crc32c_intel ghash_clmulni_intel asus_nb_wmi asus_wmi sparse_keymap aesni_intel iTCO_wdt snd_hda_codec_hdmi iTCO_vendor_support iwlwifi aes_x86_64 lrw gf128mul glue_helper ablk_helper i915 cfg80211 cryptd snd_hda_codec_realtek evdev pcspkr snd_hda_codec_generic psmouse serio_raw sg rfkill wmi drm_kms_helper int3403_thermal snd_hda_intel ehci_pci button xhci_hcd snd_hda_controller ehci_hcd snd_hda_codec drm usbcore snd_hwdep snd_pcm_oss tpm_tis mei_me snd_mixer_oss i2c_algo_bit tpm battery mei snd_pcm video shpchp lpc_ich snd_timer snd soundcore i2c_i801 mfd_core usb_common i2c_core processor ac loop fuse parport_pc ppdev lp parport autofs4 ext4 crc16 mbcache jbd2 sd_mod crc_t10dif crct10dif_generic ahci crct10dif_pclmul crct10dif_common [3094115.516478] libahci libata scsi_mod thermal thermal_sys [last unloaded: rtsx_usb_sdmmc] [3094115.516482] CPU: 3 PID: 4804 Comm: mount Tainted: GW O 3.16.0-4-amd64 #1 Debian 3.16.7-ckt2-1 [3094115.516483] Hardware name: ASUSTeK COMPUTER INC. UX31A/UX31A, BIOS UX31A.219 06/14/2013 [3094115.516485] 0009 81507263 880043d03bf0 81065847 [3094115.516487] 8800acb5b7c0 880043d03c40 88010b654940 8800c87e5ec0 [3094115.516489] 88003956c940 810658ac 8172f548 0028 [3094115.516491] Call Trace: [3094115.516495] [81507263] ? dump_stack+0x41/0x51 [3094115.516498] [81065847] ? warn_slowpath_common+0x77/0x90 [3094115.516501] [810658ac] ? warn_slowpath_fmt+0x4c/0x50 [3094115.516503] [812095f0] ? proc_register+0xc0/0x140 [3094115.516505] [8120976c] ? proc_mkdir_data+0x4c/0x70 [3094115.516514] [a00b768c] ? jbd2_stats_proc_init+0x1c/0x60 [jbd2] [3094115.516522] [a00baa21
Bug#773112: pm-utils: Enabling wireless power saving by default may severely harm network performance
Package: pm-utils Version: 1.4.1-15 Severity: important Hello everyone, three days ago I upgraded my ~2 months old Jessie system to the current state and around the same time I started experiencing severe problems with my wireless connectivity. First I blamed the poor-quality UPC wireless router and mediocre signal quality, but all other devices worked perfectly so I looked deeper into that and I noticed that somehow my wireless card got into power saving mode. Disabling it instantly solved all problems and the network is usable again. E.g. ping -c 100 google.com: power save enabled: 100 packets transmitted, 94 received, 6% packet loss, time 103229ms rtt min/avg/max/mdev = 21.034/84.491/232.543/36.534 ms power save disabled: 100 packets transmitted, 100 received, 0% packet loss, time 103188ms rtt min/avg/max/mdev = 19.154/25.336/136.978/16.462 ms This example, however, does not reflect the full scale of the problem: anything that needs a little more bandwidth basically stops working altogether. It is likely to be strongly hardware dependent (I'm using Intel Centrino Advanced-N 6235 wireless card on an Asus UX31A laptop), but enabling power saving by default for everything seems to me as a very poor choice, since not everyone has the skill to track down the issue and make the necessary adjustments to prevent the power saving mode being automatically set. I'm not sure whether the change was introduced in this package or somewhere else, but I figured pm-utils is the one responsible for turning it on (in /usr/lib/pm-utils/power.d/wireless) so it should decide whether or not it is the default setting. Could you point me (or reassign the bug) to the right place if I'm mistaken? I'm labeling it only as important since I don't even know for sure who or what broke it, but I assume the priority should be bigger since it potentially breaks the wireless networking for many people (at least those with the same wireless card). Thanks, Martin Pavelek -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (990, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages pm-utils depends on: ii powermgmt-base 1.31+nmu1 Versions of packages pm-utils recommends: ii ethtool 1:3.16-1 ii hdparm 9.43-1.1 ii kbd 1.15.5-2 ii procps 2:3.3.9-8 ii vbetool 1.1-3 Versions of packages pm-utils suggests: ii cpufrequtils008-1 ii radeontool 1.6.3-1 ii wireless-tools 30~pre9-8 -- 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#680514: xserver-xorg-video-intel: freezes also occuring in Jessie
Package: xserver-xorg-video-intel Version: 2:2.21.15-2+b2 Followup-For: Bug #680514 Hi there, I'm experiencing this issue over one month now and I'm running an up to date jessie system (kernel 3.16.0-4-amd64, xserver-xorg-video-intel 2:2.21.15-2+b2, xserver-xorg-core 2:1.16.1.901-1). I'm not able to find any trigger for the lock-up, the bug just randomly appears out of the blue. Once I also found my laptop frozen this way in the morning; the system was idle for at least several hours when the lock-up occured. As reported earlier, it is still possible to SSH into the machine; what I think was not reported is that it is _sometimes_ possible to revive the system by executing pm-suspend via SSH - the screen goes off for a while, turns immediately back on and everything works perfectly again. Sometimes, however, the pm-suspend succeeds and xserver remains frozen even after waking up, no matter how many times I try executing pm-suspend. In the latter case I also noticed that it takes more time than usual to finish suspending. Any idea what should I look for when it happens again? I'm running into this bug few times a week so I could try to learn more, but the logs do not seem to reveal anything useful.. -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Oct 4 2013 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 2397280 Nov 3 22:52 /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) Xorg X server configuration file status: -rw-r--r-- 1 root root 152 May 22 2014 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: --- Section Device Identifier Intel Graphics Driver intel Option AccelMethod sna Option TearFree true EndSection /etc/X11/xorg.conf.d does not exist. KMS configuration files: /etc/modprobe.d/radeon-kms.conf: options radeon modeset=1 Kernel version (/proc/version): --- Linux version 3.16.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 4.8.3 (Debian 4.8.3-13) ) #1 SMP Debian 3.16.7-2 (2014-11-06) Xorg X server log files on system: -- -rw-r--r-- 1 root root 20725 Dec 11 18:23 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [ 3.985] X.Org X Server 1.16.1.901 (1.16.2 RC 1) Release Date: 2014-11-02 [ 3.985] X Protocol Version 11, Revision 0 [ 3.985] Build Operating System: Linux 3.2.0-4-amd64 x86_64 Debian [ 3.985] Current Operating System: Linux hx31 3.16.0-4-amd64 #1 SMP Debian 3.16.7-2 (2014-11-06) x86_64 [ 3.985] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 root=UUID=0d377c28-a14d-4365-ab55-3d9f001fb7b5 ro quiet pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 nmi_watchdog=0 acpi_osi= [ 3.985] Build Date: 03 November 2014 09:44:08PM [ 3.985] xorg-server 2:1.16.1.901-1 (http://www.debian.org/support) [ 3.985] Current version of pixman: 0.32.6 [ 3.985]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 3.985] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 3.985] (==) Log file: /var/log/Xorg.0.log, Time: Thu Dec 11 18:21:02 2014 [ 3.987] (==) Using config file: /etc/X11/xorg.conf [ 3.987] (==) Using system config directory /usr/share/X11/xorg.conf.d [ 3.994] (==) No Layout section. Using the first Screen section. [ 3.994] (==) No screen section available. Using defaults. [ 3.994] (**) |--Screen Default Screen Section (0) [ 3.994] (**) | |--Monitor default monitor [ 3.994] (==) No device specified for screen Default Screen Section. Using the first device section listed. [ 3.994] (**) | |--Device Intel Graphics [ 3.994] (==) No monitor specified for screen Default Screen Section. Using a default monitor configuration. [ 3.994] (==) Automatically adding devices [ 3.994] (==) Automatically enabling devices [ 3.994] (==) Automatically adding GPU devices [ 3.997] (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. [ 3.997]Entry deleted from font path. [ 4.025] (==) 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 [ 4.025] (==) ModulePath set to /usr/lib/xorg/modules [ 4.025] (II) The
Bug#628199: ImportError: /usr/lib/libQtOpenGL.so.4: undefined symbol
Package: python-qt4 Version: 4.8.3-2+b1 Severity: normal Hi, I've run into quite mystical issue after recently dist-upgrade -ing my system (Debian testing, not updated for a while). After the upgrade, I'm unable to run an application named Anki, given the following error message: $ anki Traceback (most recent call last): File /usr/bin/anki, line 8, in module ankiqt.run() File /usr/share/anki/ankiqt/__init__.py, line 139, in run import forms File /usr/share/anki/ankiqt/forms/__init__.py, line 36, in module import clayout File /usr/share/anki/ankiqt/forms/clayout.py, line 333, in module from PyQt4 import QtWebKit ImportError: /usr/lib/libQtOpenGL.so.4: undefined symbol: _ZTI11QStrokerOps I've tried to reinstall everything related to python and Qt to be sure it isn't somehow caused by file damage, no effect. The mystical thing about this is, that I tried to upgrade to the versions in SID (same error), tried to downgrade to the versions in stable (differend library, but again undefined symbol) and even tried to build python-qt4 from original source (again the same error as here). Everything without success. The maker of the application suggested to report bug to the package maintainer, as the only explanation still seems to be that something is wrong with python-qt. If it is not caused by something specific to my system, steps to reproduce should be easily: # apt-get install anki $ anki Martin -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.36+ (SMP w/2 CPU cores; PREEMPT) Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages python-qt4 depends on: ii libc6 2.13-4 Embedded GNU C Library: Shared lib ii libgcc1 1:4.6.0-2 GCC support library ii libpython2.6 2.6.6-10 Shared Python runtime library (ver ii libqt4-declarative4:4.7.3-1 Qt 4 Declarative module ii libqt4-designer 4:4.7.3-1 Qt 4 designer module ii libqt4-help 4:4.7.3-1 Qt 4 help module ii libqt4-network4:4.7.3-1 Qt 4 network module ii libqt4-script 4:4.7.3-1 Qt 4 script module ii libqt4-scripttools4:4.7.3-1 Qt 4 script tools module ii libqt4-svg4:4.7.3-1 Qt 4 SVG module ii libqt4-test 4:4.7.3-1 Qt 4 test module ii libqt4-xml4:4.7.3-1 Qt 4 XML module ii libqt4-xmlpatterns4:4.7.3-1 Qt 4 XML patterns module ii libqtassistantclient4 4.6.3-3Qt Assistant client library (runti ii libqtcore44:4.7.3-1 Qt 4 core module ii libqtgui4 4:4.7.3-1 Qt 4 GUI module ii libqtwebkit4 2.1.0~2011week13-1 Web content engine library for Qt ii libstdc++64.6.0-2The GNU Standard C++ Library v3 ii python2.6.6-14 interactive high-level object-orie ii python-sip [sip-api-8 4.12.1-1+b2Python/C++ bindings generator runt ii python-support1.0.13 automated rebuilding support for P python-qt4 recommends no packages. Versions of packages python-qt4 suggests: pn python-qt4-dbgnone (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#595189: xserver-xorg-input-all: no support for WALTOP tablets
Package: xserver-xorg-input-all Version: 1:7.5+6 Severity: normal After xorg has switched to direct udev-based hardware detection instead of using HAL, I've been unable to get my tablet working. I've been using patched waltop driver and since I don't really understand the udev rules system, I can't prevent evdev driver (which is not working) from taking it over. Anyway, this doesn't change the fact, that WALTOP tablets don't work in Debian without self-help and good knowledge about udev etc. (virtually every how-to found on the web still refers to getting it working using HAL). There are three possible ways, how to get it working: 1) Patched version of xserver-xorg-input-wacom driver with disabled vendor-ID check. linuxacom driver was working well with WALTOP tablets until the vendor- ID check blocked any devices other than Wacom. More information for example at https://bugs.launchpad.net/ubuntu/+source/xf86 -input-wacom/+bug/392825 2) There are several reports in Ubuntu bug tracking system, that some people succeeded by installing the wizardpen driver (now available from https://launchpad.net/~doctormo/+archive/xorg-wizardpen, it was dead project for several years). 3) Fixing the xserver-xorg-input-evdev driver. At this moment, when I plug in the tablet (Genius G-pen F350), evdev is loaded to handle it. It appears to be working at first, but as soon as I click at the surface (or push any button at the pen) the cursor stops moving. It moves only when i hold some button, the tip is in contact with the tablet, or if the pen is taken out of range and back again. By loading a evbug module I've found out, that even though the cursor doesn't move anymore, the events are generated as usual, so the problem is most likely somewhere in the xorg evdev driver, not in the kernel support. ( 4) there's also the official driver from Wacom, but it doesn't work with new kernel and xorg and as far as I know, it's probably based on the linuxwacom driver) The best solution would be using the Wacom driver because it includes tools for testing and setting some advanced options. The same goes for wizardpen, but one can't be sure, if the development won't stop again... -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.36-rc3 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (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
