Bug#902437: xwayland: Firefox crashes Wayland on some web pages
Package: xwayland Version: 2:1.20.0-2 Severity: important Dear Maintainer, My apologies for ruining your day with what looks like a tricky driver bug. I hate debugging such things, myself. I'm marking this "important", because the issue makes me not dare to browse the web: I've had to reboot my system several times a day lately. If you think it should be a lower severity, please downgrade. Also, I made a wild guess at which package to report this issue against, and I am so utterly, comically ignorant of everything in a modern Debian desktop system that I may have guessed wrongly; please reassign if so. I run Debian sid on two different laptops: a Lenovo Thinkpad X220, and a Lenovo Yoga 900. Both use an Intel graphics card or chip. For the past week or two, the X220 has been crashing from time to time. I thought it might be bad memory in the laptop, so I switched to the Yoga. Then the Yoga started crashing. After much headbanging and wailing, I've manged to find way to reproduce the crash. I use Firefox as my web browser, and certain web pages trigger the crash reproducibly. One such web page is here: http://johannesbrodwall.com/2018/06/24/forget-about-clean-code-lets-embrace-compassionate-code/ What happens is that Firefox does not render that page, only updates the page title in the window title, and then becomes unresponsive. Menus don't react in anyway. i can't close the tab or window with Ctrl-W, or by clicking on the window close button. After a few more seconds, the whole desktop stops working, meaning that pressing the capslock key no longer toggles the LED. The mouse cursor may or may not work. If it does work, moving it to the top left corner of the GNOME desktop makes the mouse not work anymore. Also, the desktop does not do the "whoosh" feature of GNOME where it shows all windows on the current virtual desktop, and the "dock" on the left side of the screen. The machine seems to work otherwise: I can log into it via ssh, and run commands on the command line. I can restart gdm3 from the ssh session, but if I log back in, it doesn't work: I get a dark grey screen, no windows, and nothing else for about half a minute, and then it's back to the gdm3 login screen. Logging in as a different user seems to work. There's nothing new in dmesg output, when the crash happens. I've run the in-kernel memtest on the Yoga, and it resports no problems. (I've not bothered to run it on the X220 yet. I can, if it'd be helpful to you.) I reconfigured gdm3 on the Yoga to start Xorg instead of Wayland, and now the web page above works fine in Firefox. No crash.. The webpage renders fine under Wayland using Chromium. I am OK with this workaround, but I assume the bug should be fixed if Wayland is to be the default in Debian. The problem is reproducible for me. If others can reproduce it, it should be doable on any X220, which is, or used to be, a common laptop. I will be keeping mine in storage for a while, so that if there's a need, I can try new package versions to see if they fix the problem. Happy hunting. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.16.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages xwayland depends on: ii libaudit1 1:2.8.3-1 ii libbsd0 0.9.1-1 ii libc6 2.27-3 ii libdrm2 2.4.92-1 ii libegl1 1.0.0+git20180308-3 ii libepoxy0 1.4.3-1 ii libgbm1 18.1.2-1 ii libgcrypt20 1.8.3-1 ii libgl1 1.0.0+git20180308-3 ii libpixman-1-0 0.34.0-2 ii libselinux1 2.8-1 ii libsystemd0 239-1 ii libwayland-client0 1.15.0-2 ii libxau6 1:1.0.8-1+b2 ii libxdmcp6 1:1.1.2-3 ii libxfont2 1:2.0.3-1 ii libxshmfence1 1.3-1 ii xserver-common 2:1.20.0-2 xwayland recommends no packages. xwayland suggests no packages. -- no debconf information
Bug#403101: xbase-clients: please don't install by xhost default
Package: xbase-clients Version: 1:7.1.ds-3 Severity: wishlist Justification: not worth delaying etch for xbase-clients contains xhost, which in the modern world (after 1995, when ssh was first released) is rarely the right tool, but it is so easy that the Internet is full of advice to use xhost + to allow X programs to use a remote server. It would be nice if Debian would move xhost to a separate package, not installed by default (priority extra, not depended-on by anything, not part of a task). Since xhost is occasionally useful for people who do understand what they're doing, the xbase-clients package could then contain a little script like this: #!/bin/sh echo xhost is rarely useful, please use ssh -X or xauth instead. echo See /usr/share/doc/xbase-clients/README.xhost for information. That script and the real xhost binary could then be alternatives, so that installing the xhost package would make xhost magically work. -- Close your mind to stress and pain, hack till you're no longer sane. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#382776: xfs: upgrading from sarge, then purging, leaves /etc/X11/fs/xfs.options
Package: xfs Version: 1:1.0.1-5 When testing xfs with piuparts, we get the following error: 2m11.6s ERROR: Package purging left files on system: /etc/X11 owned by: x11-common, xfs /etc/X11/fs owned by: xfs /etc/X11/fs/xfs.options This happens when upgrading from sarge to etch to sid, and then removing and purging the package. The full piuparts log file is at: http://piuparts.cs.helsinki.fi/bugged/xfs_1:1.0.1-5.log I haven't studied the package in detail, but just in case a guess is good: perhaps a previous version of the package contained the xfs.options conffile, and a newer one no longer does? If so, you may have hit the dpkg feature where it won't remove the conffile from disk in this case, and you need to do it manually from package maintainer scripts, if removing is the right thing to do. -- Programming should be fun, otherwise you're doing something wrong. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#382360: xutils: upgrading from sarge, then purging, leaves /etc/X11/rstart/*
Package: xutils Version: 7.1.ds-1 When testing another package (artwiz-cursor, but it happens with other packages too) with piuparts, we found the following problem with xutils: 2m17.3s ERROR: Package purging left files on system: /etc/X11 owned by: x11-common /etc/X11/rstart /etc/X11/rstart/commands /etc/X11/rstart/commands/@List /etc/X11/rstart/commands/ListContexts /etc/X11/rstart/commands/ListGenericCommands /etc/X11/rstart/commands/x11r6 /etc/X11/rstart/commands/x11r6/@List /etc/X11/rstart/commands/x11r6/LoadMonitor /etc/X11/rstart/commands/x11r6/Terminal /etc/X11/rstart/config /etc/X11/rstart/contexts /etc/X11/rstart/contexts/@List /etc/X11/rstart/contexts/default /etc/X11/rstart/contexts/x11r6 This happens when upgrading from sarge to etch to sid, and then removing and purging the package. In the sarge version of xutils, those files seem to be conffiles, but in the etch version they no longer are part of the package. dpkg does not remove conffiles from disk when they are dropped from a package during an upgrade; you may want to remove the files in postrm during purge, I guess. The full log file is at http://piuparts.cs.helsinki.fi/bugged/artwiz-cursor_1:1.3-5.log I hope this is helpful. -- Fundamental truth #2: Attitude is usually more important than skills. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#351326: xserver-xorg: trouble purging
Package: xserver-xorg Version: 6.9.0.dfsg.1-4 While I was testing xserver-xfree86 (which just depends on xserver-xorg) with piuparts, I got the following error: 0m12.6s ERROR: Command failed (status=256): 'chroot /tmp/tmpS7lFxN dpkg --purge --pending' (Reading database ... 6930 files and directories currently installed.) Removing xserver-xorg ... Purging configuration files for xserver-xorg ... Removing any system startup links for /etc/init.d/xserver-xorg ... dpkg: error processing xserver-xorg (--purge): subprocess post-removal script returned error exit status 20 Unfortunately, the X packages have maintainer scripts that scare me and confuse me, so I failed to find the reason for this problem. Sorry. I have attached the bzip2'd piuparts log file. If I can provide assistance in debugging this, please don't hesitate to ask. -- Connection resented by peer xserver-xfree86_6.9.0.dfsg.1-4.log.bz2 Description: application/bzip
Bug#351067: xfs: missing depends on debconf stuff
Package: xfs Version: 6.9.0.dfsg.1-4 While testing xfs with piuparts, I ran into the following problem: Setting up xfs (6.9.0.dfsg.1-4) ... /var/lib/dpkg/info/xfs.postinst: line 13: /usr/share/debconf/confmodule: No such file or directory dpkg: error processing xfs (--configure): subprocess post-installation script returned error exit status 1 You need to depend on debconf-2.0 | debconf, I guess. -- Fundamental truth #3: Communication is difficult. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#348224: x11-common: leaves /etc/init.d/x11-common on disk after purge
Package: xfree86-common,x11-common Version: 6.9.0.dfsg.1-3 I found the following problem while testing, with piuparts, upgrades from sarge via etch to sid of xfree86-common. The bug itself may instead be in x11-common, which, however, didn't exist in sarge as far as I can tell. The problem, as reported by piuparts, is this: 1m58.9s ERROR: Package purging left files on system: /etc/init.d/x11-common /etc/rcS.d/S70x11-common I've checked it with a manual upgrade from sarge in a chroot. I couldn't figure out in a brief examination where the bug actually is: the X packaging is big and daunting (which is fine, given the size and importance of the package), and I didn't have the time to look at it in detail. The piuparts log file is about 170 kilobytes; if it helps, I'll be happy to mail it, but due to the size I'm not attaching it here. The command used for testing was: sudo piuparts -ab sarge.tar.gz -d sarge -d etch -d sid xfree86-common (where sarge.tar.gz is a tarball of the chroot containing a base sarge installation with minor modifications to configuration files, used for optimization, leave the b sarge.tar.gz part away to try it without a tarball). -- Never underestimate the power of a small tactical Lisp interpreter. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#330588: xserver-xorg: doesn't remove /etc/rcS.d link
Package: xserver-xorg Version: 6.8.2.dfsg.1-7 According to piuparts: 0m10.9s ERROR: Package purging left files on system: /etc/rcS.d/S71xserver-xorg The postinst seems to call update-rc.d, but the prerm and postrm do not. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#328487: libfs6: doesn't clean up a shlib symlink?
Package: libfs6 Version: 6.8.2.dfsg.1-6 Testing libfs6 with piuparts, I get: 0m6.9s ERROR: Package purging left files on system: /usr/X11R6 owned by: libfs6 /usr/X11R6/lib owned by: libfs6 /usr/X11R6/lib/libFS.so.6 In the postrm, when $1 is remove, deregister_x_lib_dir_with_ld_so is called before ldconfig. This means that ldconfig does not know that it needs to go remove dangling symlinks in /usr/X11R6/lib. Calling them in the other order would seem correct, I think, but admittedly I'm not very familiar with shlibs stuff. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#317553: xfree86-common: leaves two files in /tmp on purge
su, 2005-07-10 kello 03:12 +1000, Daniel Stone kirjoitti: If the two are /tmp/.X11-unix and /tmp/.ICE-unix, I don't think we should bother removing them. They're required for any X work, and /tmp gets cleaned on reboot anyway. If xfree86-common is purged, X programs aren't going to work, I think, so removing the files on purge should be ok? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#317553: xfree86-common: leaves two files in /tmp on purge
Package: xfree86-common Version: 4.3.0.dfsg.1-14 Severity: normal Upon purge, xfree86-common leaves two files (or directories) in /tmp, which it should remove for cleanliness. This is not, however, a bug that actually affects anything much. This bug report is just a reminder that we agreed at Debconf5 that cleanliness is good. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.10-1-686 Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8) Versions of packages xfree86-common depends on: ii debconf 1.4.51 Debian configuration management sy ii debianutils 2.14.1 Miscellaneous utilities specific t xfree86-common recommends no packages. -- debconf information: xfree86-common/experimental_packages: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
