[Bug 404331] Re: X locks up when scrolling on Radeon Mobility M6 LY
If intrepid was somewhat better, jaunty has been considerably worse, often freezing up within an hour using Firefox (I think it's particularly common scrolling immediately after switching into the Firefox window). I did have visual effects working for a while, and there also seemed to be a reliable way to produce a lockup using compiz 'Paint fire on screen' with some high values for particle size and number. In the case of intrepid and jaunty, not only does the cursor become jerky (longer timeout?), and I've not seen the screen corruption, but the slowdown is gradual over a course of about 2 seconds, as if whatever resource is getting locked is slowly approaching saturation. Then a few seconds after that the laptop fan comes on as CPU usage hits 100%. The difference in jaunty is it seems to happen more readily, whereas I got the impression in intrepid it sometimes approached this slowup and halt, but recovered. There's nothing special in Xorg.log: the last lines are about monitor detection. xserver-xorg-video-radeon/jaunty uptodate 1:6.12.1-0ubuntu2 xserver-xorg-video-ati/jaunty uptodate 1:6.12.1-0ubuntu2 xserver-xorg-core/jaunty uptodate 2:1.6.0-0ubuntu14 libgl1-mesa-dri/jaunty-updates uptodate 7.4-0ubuntu3.1 libgl1-mesa-glx/jaunty-updates uptodate 7.4-0ubuntu3.1 libdrm2/jaunty uptodate 2.4.5-0ubuntu4 Nothing similar to this happens on the laptop under Windows XP (although occasionally there is a driver BSOD on boot), so if it's a hardware timing issue, it's one that could be worked around, as a last resort by resetting the card and driver. Anyway, my current workaround is Option "DRI" "false" And that seems to be working. Have I filed this against the wrong package? ** Attachment added: "backtrace and variables during lockup on jaunty" http://launchpadlibrarian.net/29819801/gdb-Xorg21-jaunty.txt -- X locks up when scrolling on Radeon Mobility M6 LY https://bugs.launchpad.net/bugs/404331 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 404331] Re: X locks up when scrolling on Radeon Mobility M6 LY
Couldn't install upgrades with build-dep or aptitude, so upgraded to 8.10 Intrepid, xserver-xorg-core 2:1.5.2-2ubuntu3.1 , xserver-xorg- video-ati 1:6.9.0+git20081003.f9826a56-0ubuntu2.1. Very similar effect has occurred once, (although cursor movement was slow/jerky after lockup this time). -- X locks up when scrolling on Radeon Mobility M6 LY https://bugs.launchpad.net/bugs/404331 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 404331] Re: X locks up when scrolling on Radeon Mobility M6 LY
Backtrace for Intrepid attached - it looks like essentially the same problem in the same function (RADEONCPGetBuffer). It may be slightly less frequent now, twice in three days. Might as well upgrade to Jaunty now... ** Attachment added: "backtrace during lockup on intrepid" http://launchpadlibrarian.net/29700302/gdb-Xorg12intrepid-wth-symbols.txt -- X locks up when scrolling on Radeon Mobility M6 LY https://bugs.launchpad.net/bugs/404331 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 404331] [NEW] X locks up when scrolling on Radeon Mobility M6 LY
Public bug reported: Binary package hint: xserver-xorg-video-ati This was a Ubuntu 8.04 fresh install on Viglen Dossier LX. Every few hours, apparently randomly, everything freezes apart from the mouse pointer. Ctrl-Alt-F1 or Ctrl-Alt-Del does nothing, but I can ping the laptop. Typically this occurs when scrolling up or down in Firefox using touchpad or keyboard, and there is some screen corruption at the bottom of the scroll bar (as if a blit failed or was interrupted?). The symptoms aren't quite the same as bug #36596, bug #248438: it does seem closest to bug #184430 which was attributed to a faulty adapter, but again doesn't sound identical, nor to (Debian bug) #459428 which sounded unresolved. No visual effects, because it claims they are not available; before the hang I can switch to a console. I've tried Option "RenderAccel" "off" and Option "AGPMode" "2" for "Configured Video Device" but neither seems to help, nor reducing AGP aperture in BIOS. Xorg.0.log shows the uninformative: mieqEnequeue: out-of-order valuator event; dropping. tossed event which came in late mieqEnequeue: out-of-order valuator event; dropping. tossed event which came in late tossed event which came in late tossed event which came in late reported elsewhere. An strace shows EBUSY errors: 22:30:05 [b7f64410] read(37, "\233\7\2\0E\"\203\2\233\4\5\0F\"\203\2:\"\203\0028\0\0"..., 4096) = 208 22:30:05 [b7f64410] ioctl(7, 0xc0286429, 0xbff07634) = -1 EBUSY (Device or resource busy) (I'll upload fuller strace and try getting more info via SSH as described at https://wiki.ubuntu.com/X/Backtracing ) ProblemType: Bug Architecture: i386 Date: Fri Jul 24 20:03:45 2009 DistroRelease: Ubuntu 8.04 Package: xserver-xorg-video-ati 1:6.8.0-1ubuntu1 PackageArchitecture: i386 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/opt/real/RealPlayer LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: xserver-xorg-video-ati Uname: Linux 2.6.24-24-generic i686 ** Affects: xserver-xorg-video-ati (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug -- X locks up when scrolling on Radeon Mobility M6 LY https://bugs.launchpad.net/bugs/404331 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 404331] Re: X locks up when scrolling on Radeon Mobility M6 LY
** Attachment added: "strace showing EBUSY" http://launchpadlibrarian.net/29496977/Xstrace-lockup-ebusy.txt.gz ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/29496978/Dependencies.txt -- X locks up when scrolling on Radeon Mobility M6 LY https://bugs.launchpad.net/bugs/404331 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 404331] Re: X locks up when scrolling on Radeon Mobility M6 LY
** Attachment added: "lspci, lsmod, dmesg and module versions in case not already included" http://launchpadlibrarian.net/29497012/X-addinfo.txt ** Description changed: Binary package hint: xserver-xorg-video-ati This was a Ubuntu 8.04 fresh install on Viglen Dossier LX. Every few hours, apparently randomly, everything freezes apart from the mouse pointer. Ctrl-Alt-F1 or Ctrl-Alt-Del does nothing, but I can ping the laptop. Typically this occurs when scrolling up or down in Firefox using touchpad or keyboard, and there is some screen corruption at the bottom of the scroll bar (as if a blit failed or was interrupted?). - The symptoms aren't quite the same as #36596, #248438: it does seem - closest to #184430 which was attributed to a faulty adapter, but again - doesn't sound identical, nor to Debian bug #459428 which sounded - unresolved. No visual effects, because it claims they are not + The symptoms aren't quite the same as bug #36596, bug #248438: it does + seem closest to bug #184430 which was attributed to a faulty adapter, + but again doesn't sound identical, nor to (Debian bug) #459428 which + sounded unresolved. No visual effects, because it claims they are not available; before the hang I can switch to a console. I've tried Option "RenderAccel" "off" and Option "AGPMode" "2" for "Configured Video Device" but neither seems to help, nor reducing AGP aperture in BIOS. Xorg.0.log shows the uninformative: mieqEnequeue: out-of-order valuator event; dropping. tossed event which came in late mieqEnequeue: out-of-order valuator event; dropping. tossed event which came in late tossed event which came in late tossed event which came in late reported elsewhere. An strace shows EBUSY errors: 22:30:05 [b7f64410] read(37, "\233\7\2\0E\"\203\2\233\4\5\0F\"\203\2:\"\203\0028\0\0"..., 4096) = 208 22:30:05 [b7f64410] ioctl(7, 0xc0286429, 0xbff07634) = -1 EBUSY (Device or resource busy) (I'll upload fuller strace and try getting more info via SSH as described at https://wiki.ubuntu.com/X/Backtracing ) ProblemType: Bug Architecture: i386 Date: Fri Jul 24 20:03:45 2009 DistroRelease: Ubuntu 8.04 Package: xserver-xorg-video-ati 1:6.8.0-1ubuntu1 PackageArchitecture: i386 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/opt/real/RealPlayer LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: xserver-xorg-video-ati Uname: Linux 2.6.24-24-generic i686 -- X locks up when scrolling on Radeon Mobility M6 LY https://bugs.launchpad.net/bugs/404331 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 404331] Re: X locks up when scrolling on Radeon Mobility M6 LY
I've not tried, but am about to try installing xserver-xorg-core 2:1.6.0-0ubuntu14 and xserver-xorg-video-ati 1:6.12.1-0ubuntu2 from Jaunty, and will report back. 3 backtraces attached, occurring at 2 different places where it seems to get stuck and use all available CPU: #2 0xb7b2896d in drmDMA () from /usr/lib/libdrm.so.2 #3 0xb7ac8b64 in RADEONCPGetBuffer (pScrn=0x821bd90) at ../../src/radeon_accel.c:521 #4 0xb7ad008b in RADEONSetupForSolidFillCP (pScrn=0x821bd90, color=16777215, rop=6, planemask=4294967295) at ../../src/radeon_accelfuncs.c:137 #2 0xb7b6f96d in drmDMA () from /usr/lib/libdrm.so.2 #3 0xb7b0fb64 in RADEONCPGetBuffer (pScrn=0x821bd90) at ../../src/radeon_accel.c:521 #4 0xb7b0fcfb in RADEONCPFlushIndirect (pScrn=0x821bd90, discard=1) at ../../src/radeon_accel.c:575 ** Attachment added: "3 backtraces following lockups, mostly not scrolling" http://launchpadlibrarian.net/29581247/gdb-Xorg-backtraces.txt -- X locks up when scrolling on Radeon Mobility M6 LY https://bugs.launchpad.net/bugs/404331 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 475185] Re: Epson Stylus SX410 hybrid printer/scanner isn't in detected as a scanner by xsane
My Epson Stylus Photo RX620 is also not apparently supported by xsane
although listed on the sane site as supported by epson2 ("epson" is
commented out in the default /etc/sane.d/dll.conf).
On connection I get a "no devices available" warning, although xsane
loads. If I run xsane from the command line I get a segfault when the
printer is on. However sometimes "scanimage -d epson2" does produce
output (although I can't get it in Gimp's File > Create > xsane dialogue
and the scan button doesn't work) and scanimage -L also lists the device
(currently more often than not). So is it more likely to be a problem
with xsane than libsane?
found USB scanner (vendor=0x04b8 [EPSON], product=0x0811 [USB2.0 MFP])
at libusb:001:002
I created a /etc/udev/rules.d/45-libsane.rules with
SYSFS{idVendor}=="04b8", SYSFS{idProduct}=="0811", MODE="664", GROUP="scanner"
"man sane-dll" doesn't seem to be in the package. "man sane-epson2" is.
libsane/karmic uptodate 1.0.20-4ubuntu3
libsane-extras/karmic uptodate 1.0.20.1ubuntu1
sane-utils/karmic uptodate 1.0.20-4ubuntu3
xsane/karmic-updates uptodate 0.996-2ubuntu1.1
xsane-common/karmic-updates uptodate 0.996-2ubuntu1.1
xsane-doc/karmic-updates uptodate 0.996-2ubuntu1.1
Quite sure it's not a permissions issue - I'm a member of saned / lp /
lpadmin groups and also happens as root.
I may try to get more info on the segmentation fault. I also see the
"Unhandled message" warning mentioned in comment 2 above,
--
Epson Stylus SX410 hybrid printer/scanner isn't in detected as a scanner by
xsane
https://bugs.launchpad.net/bugs/475185
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 418448] Re: pulseaudio crashed with SIGILL in pa_volume_memchunk()
> Anyone *not* using an Athlon XP and encountering this bug? Mobile Intel(R) Pentium(R) III CPU - M 1066MHz ...but I'm not sure it's the same bug although it has the same title. Recently upgraded to Karmic, and got this on login. Crashed when trying it with valgrind (attached). Please don't spend any time on this as the system has various other problems and I'm reinstalling Jaunty soon, but just in case it's related... ** Attachment added: "valgrind.log" http://launchpadlibrarian.net/31108799/valgrind.log -- pulseaudio crashed with SIGILL in pa_volume_memchunk() https://bugs.launchpad.net/bugs/418448 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 495796] [NEW] update manager/synaptic to warn if security updates disabled
Public bug reported: Binary package hint: synaptic For the wishlist? It is possible to accidentally disable security updates, either in Software Sources, or in sources.list. As well as being a security problem, I only noticed this when a PPA required a higher version of a package than was installed for that version, which confused me. I'd suggest that when exiting synaptic, the user should be warned if security updates are disabled. This could perhaps also be a balloon produced when update manager checks? ProblemType: Bug Architecture: i386 Date: Sat Dec 12 09:10:53 2009 DistroRelease: Ubuntu 9.10 Package: synaptic 0.62.7ubuntu6 ProcEnviron: PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-16.53-generic SourcePackage: synaptic Uname: Linux 2.6.31-16-generic i686 ** Affects: synaptic (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- update manager/synaptic to warn if security updates disabled https://bugs.launchpad.net/bugs/495796 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 495796] Re: update manager/synaptic to warn if security updates disabled
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/36714463/Dependencies.txt ** Attachment added: "XsessionErrors.txt" http://launchpadlibrarian.net/36714464/XsessionErrors.txt -- update manager/synaptic to warn if security updates disabled https://bugs.launchpad.net/bugs/495796 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 480010] Re: Playback 10% too fast after resume
Daniel T Chen wrote: > It looks like you should pass a module parameter specifying > the clock rate (in Hz, not KHz) to snd-intel8x0. It should be fairly > straightforward when looking at: > > modinfo snd-intel8x0|grep -i ^parm I created a /etc/modprobe.d/options.conf with options snd-intel8x0 ac97_clock=44100 and after reloading the driver, the playback was 10% too *slow*. Using options snd-intel8x0 ac97_clock=48000 it's correct, but then still 10% too fast after suspend/resume. So I don't think it's that parameter. Here are the other parms: parm: index:Index value for Intel i8x0 soundcard. (int) parm: id:ID string for Intel i8x0 soundcard. (charp) parm: ac97_clock:AC'97 codec clock (0 = whitelist + auto-detect, 1 = force autodetect). (int) parm: ac97_quirk:AC'97 workaround for strange hardware. (charp) parm: buggy_semaphore:Enable workaround for hardwares with problematic codec semaphores. (bool) parm: buggy_irq:Enable workaround for buggy interrupts on some motherboards. (bool) parm: xbox:Set to 1 for Xbox, if you have problems with the AC'97 codec detection. (bool) parm: spdif_aclink:S/PDIF over AC-link. (int) parm: enable:bool parm: joystick:int Not sure if it's worth trying any of the others. > > The alsa-utils initscript is somewhat misleadingly named. It really > does not do anything to the sound driver other than (re)storing mixer > levels. OK, thanks. That explains it. > That is precisely what I'm referring to. The sampling rate correction > apparently requires a reset, but what I'm driving at is whether PA > needs to be restarted. In other words, why does having PA running when > you suspend make a difference? To answer that question I suspect I'll > need output; see https://wiki.ubuntu.com/PulseAudio/Log . Attached. (I thought it might be merely the fact that the driver had a use count of 1 from pulseaudio [PA} that was relevant. So is the bug in the driver or PA?) BTW not surprisingly, the effect is also evident in Flash video. ** Attachment added: "pulseverbose.log" http://launchpadlibrarian.net/35537479/pulseverbose.log -- Playback 10% too fast after resume https://bugs.launchpad.net/bugs/480010 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 558998] Re: [lucid] compiz-gnome broken because of metacity update
After a restart from a partial upgrade from Karmic to Lucid, neither compiz nor metacity are started on login - so no decorations or window manager. metacity --replace would work, but can't always get focus into gnome- Terminal, so easiest thing is to go to Appearance > visual effects and switch between metacity and compiz. But visual effects do not remain on when logging in again. Have purged and reinstalled compiz, compiz-gnome and lots of metacity and gdm packages, but problem persists. -- [lucid] compiz-gnome broken because of metacity update https://bugs.launchpad.net/bugs/558998 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 558998] Re: [lucid] compiz-gnome broken because of metacity update
After reinstalling most of the system, I tried logging in in GNOME safe mode, and metacity was running correctly. Big clue that it was something to do with the GNOME session, and I remembered I'd stored various startup applications. So if starting metacity on the command line as above and then going to System > Preferences > Startup Applications > Options tab > click on "Remember Currently-running Application" and tick "automatically remember" seemed to work. So this isn't apparently related to the compiz-gnome package, but to the upgrade process and its effect on the saved session. Might be the same as bug 563171 and/or bug 560065 which don't mention compiz-gnome. -- [lucid] compiz-gnome broken because of metacity update https://bugs.launchpad.net/bugs/558998 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 421842] Re: screen corruption and segfaults with radeon m6 ly
On Live CD alpha-5 dmesg is full of [ 1044.070800] [drm:radeon_cp_start] *ERROR* radeon_cp_start called without lock held, held -2147483648 owner e3d01240 e3d01b40 [ 1044.070834] [drm:radeon_cp_idle] *ERROR* radeon_cp_idle called without lock held, held -2147483648 owner e3d01240 e3d01b40 ... [ 1047.360532] [drm:radeon_cp_idle] *ERROR* radeon_cp_idle called without lock held, held -2147483648 owner e3d01240 e3d01b40 [ 1047.371003] [drm:radeon_cp_reset] *ERROR* radeon_cp_reset called without lock held, held -2147483648 owner e3d01240 e3d01b40 [ 1047.371062] [drm:radeon_cp_start] *ERROR* radeon_cp_start called without lock held, held -2147483648 owner e3d01240 e3d01b40 [ 1047.371097] [drm:radeon_cp_idle] *ERROR* radeon_cp_idle called without lock held, held -2147483648 owner e3d01240 e3d01b40 Also attaching a ps from alpha-5 live CD showing the 'dd' command associated with the hang. Alt+SysRq+K didn't work, nor gdm restart, but Alt+SysRq+B did reboot. ** Attachment added: "process forest during hang (obtained with ssh)" http://launchpadlibrarian.net/31403893/ps-freeze.txt -- screen corruption and segfaults with radeon m6 ly https://bugs.launchpad.net/bugs/421842 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 421842] Re: screen corruption and segfaults with radeon m6 ly
** Attachment added: "List of fglrx-related files and complete package list" http://launchpadlibrarian.net/31403771/fglrx-list -- screen corruption and segfaults with radeon m6 ly https://bugs.launchpad.net/bugs/421842 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 421842] Re: screen corruption and segfaults with radeon m6 ly
I don't have enough memory (640M) to update Live CD to latest, but have now tried with alpha-5. There are reproducible screen problems with alpha-5 (e.g. hang after resizing a window), where everything seems fine in alpha-4. I have not seen the screen corruption in alpha-4 either, but attach an example from alpha-5. * alpha-4 live CD - fine * alpha-5 live CD - screen corruption and hangs (apparently doing something with dd and rsyslogd) * current HD Karmic (with DRI off) - screen corruption * current HD Karmic (with DRI on) - screen corruption and hangs On the hard drive, in fact I had installed and uninstalled the fglrx driver earlier on, under Hardy, as an attempt to fix the lockups in bug 404331, but not since upgrading to intrepid. I followed instructions at https://wiki.ubuntu.com/X/Troubleshooting/FglrxInteferesWithRadeonDriver and there are no packages, but a few files related to fglrx. I tried both methods to reinstall with no effect on the 'tartan' corruption, and in fact went further in purging libgl1-mesa-glx libgl1-mesa-dri and xserver-xorg-core, and then reinstalling ubuntu-desktop. Anything other packages it might be worth purging? hald? BTW on that wiki page, I think sudo apt-get remove --purge fglrx* should be sudo apt-get remove --purge 'fglrx*' ** Attachment added: "sometimes corruption affects whole window, sometimes part" http://launchpadlibrarian.net/31403765/Screenshot-livecd-alpha-5.png -- screen corruption and segfaults with radeon m6 ly https://bugs.launchpad.net/bugs/421842 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 425551] Re: package openssh-server 1:5.1p1-6ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Attachment added: "AptOrdering.txt" http://launchpadlibrarian.net/31412926/AptOrdering.txt ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/31412927/Dependencies.txt ** Attachment added: "Dmesg.txt" http://launchpadlibrarian.net/31412928/Dmesg.txt ** Attachment added: "DpkgTerminalLog.txt" http://launchpadlibrarian.net/31412929/DpkgTerminalLog.txt -- package openssh-server 1:5.1p1-6ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 https://bugs.launchpad.net/bugs/425551 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 425551] [NEW] package openssh-server 1:5.1p1-6ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: Binary package hint: openssh-server Running Karmic alpha-4 live CD, used synaptic to install abiword (and dependencies) and openssh-server. I'm retyping the following from the synaptic terminal window: Setting up openssh-server (1:5.1p1-6ubuntu1) ... Can't exec "/usr/bin/chage": Input/output error at /usr/sbin/adduser line 440. Stopped: `/usr/bin/chage -M 9 sshd' returned exit code 16777215. Exiting. Removing user `sshd' ... It then retries and fails again. I didn't get this with the same procedure with Karmic alpha-5, so it may have been fixed. ProblemType: Package Architecture: i386 Date: Mon Sep 7 07:33:58 2009 DistroRelease: Ubuntu 9.10 ErrorMessage: subprocess installed post-installation script returned error exit status 1 LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Alpha i386 (20090812.3) Package: openssh-server 1:5.1p1-6ubuntu1 ProcVersionSignature: Ubuntu 2.6.31-5.24-generic SourcePackage: openssh Title: package openssh-server 1:5.1p1-6ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Uname: Linux 2.6.31-5-generic i686 ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 -- package openssh-server 1:5.1p1-6ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 https://bugs.launchpad.net/bugs/425551 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 404331] Re: X locks up when scrolling on Radeon Mobility M6 LY
I've also just reproduced this problem (Firefox scrolling) on fresh Jaunty 9.04 live CD, using a 3COM wireless card rather than ndisgtk. I think this means we can rule out anything to do with persistent configuration errors or corrupted packages, or realplayer or ndiswrapper (and probably nothing to do with IRQ conflict with the PCMCIA card). I think we may be dealing with at least 3 separate bugs - this one 404331 has been present since HDD was formatted and Windows XP and Hardy installed. It only hangs when DRI is enabled, and then Xorg takes 99% of CPU and cursor movement is jerky. It was definitely present in Jaunty, but I'm *not* 100% convinced it's in Karmic, because the other, newer bugs mask it (including one in alpha-5 live CD which causes distorted screen corruption a different freeze involving dd and rsyslogd and stationary cursor; and the reproducible effect I've only seen on latest karmic on the installed version with 'tartan' window corruption) and also I have DRI turned off just in case on the HD installation. I'll continue to test, but I'm not sure which bug to concentrate on (about to try upgrading individual packages on live CD to alpha-5). This one (404331) is annoyingly infrequent, because I usually have to turn DRI and work for an hour or two before it happens, meaning losing some work... -- X locks up when scrolling on Radeon Mobility M6 LY https://bugs.launchpad.net/bugs/404331 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 425551] Re: package openssh-server 1:5.1p1-6ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Please ignore. This seems to be down to an error on the CD I burned. These things happen, I suppose. [ 9831.171058] SQUASHFS error: zlib_inflate error, data probably corrupt [ 9831.171075] SQUASHFS error: squashfs_read_data failed to read block 0x26f7b907 [ 9831.171084] SQUASHFS error: Unable to read fragment cache entry [26f7b907] [ 9831.171091] SQUASHFS error: Unable to read page, block 26f7b907, size d1e2 ** Changed in: openssh (Ubuntu) Status: New => Invalid -- package openssh-server 1:5.1p1-6ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 https://bugs.launchpad.net/bugs/425551 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 421842] Re: screen corruption and segfaults with radeon m6 ly
Some more information from M6 LY world... 1) Starting from Karmic alpha-4 (LiveCD), which works, I can upgrade xserver-xorg-video-radeon to the karmic repository version, and xserver- xorg-core and all the -video packages, compiz, and hal/libhal, and finally install libdrm-radeon1 to get DRI functionality back (otherwise it tends to fall back on vesa). I can't upgrade libgl1-mesa-dri because of bug 420617. After all this, everything still seems to work fine, compiz effects and all. This makes me suspect libgl1-mesa-dri (or maybe the window-decorator?). 2) With the latest updates, the 'tartan' screen corruption still occurs if and only if DRI is off. By latest, I mean libgl1-mesa-dri/karmic uptodate 7.6.0~git20090817.7c422387-0ubuntu3 ubuntu-desktop/karmic uptodate 1.167 I'm not sure the best way to test this on the live CD - unload the drm module? 3) With the latest updates and if and only if DRI is on, I still get hangs/crashes where either (a) with NoTrapSignals left as false, I get reams of error messages like the above 'radeon_cp_start called without lock held', and a lockup where the cursor is stationary, and I can't attach a gdb. (b) with NoTrapSignals false, a crash in Xorg as follows: Sep 7 20:41:23 laptop23 kernel: [ 213.306512] Xorg[3115]: segfault at 14 ip 00f740c5 sp bfd247c0 error 4 in radeon_dri.so[f24000+255000] Sep 7 20:41:25 laptop23 kernel: [ 215.127370] agpgart-intel :00:00.0: AGP 2.0 bridge Sep 7 20:41:25 laptop23 kernel: [ 215.127401] agpgart-intel :00:00.0: putting AGP V2 device into 4x mode Sep 7 20:41:25 laptop23 kernel: [ 215.127433] pci :01:00.0: putting AGP V2 device into 4x mode Sep 7 20:41:25 laptop23 kernel: [ 215.376447] [drm] Setting GART location based on new memory map Sep 7 20:41:25 laptop23 kernel: [ 215.376467] [drm] Loading R100 Microcode Sep 7 20:41:25 laptop23 kernel: [ 215.376513] [drm] writeback test succeeded in 1 usecs Sep 7 20:43:29 laptop23 kernel: [ 339.623068] Xorg[5247]: segfault at 14 ip 00f200c5 sp bfb98040 error 4 in radeon_dri.so[ed+255000] Would a core dump be useful? Also under the same conditions, I get the partial distortion of a window as shown in the 517K PNG. The easiest way to produce this is to drag a window over a window that does not have the focus. The segfault (or hang) is most easily produced by enlarging a window that is about 600w x 400h until it is say 1100w x 700h, or starting an application that would produce a larger window. 4) Ctrl-Alt-F1 isn't changing to text mode properly with the very latest updates. 5) I won't be able to confirm bug 404331 is fixed for me until this one is fixed, since if DRI is enabled, this bug happens more frequently. -- screen corruption and segfaults with radeon m6 ly https://bugs.launchpad.net/bugs/421842 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 421842] Re: screen corruption and segfaults with radeon m6 ly
** Attachment added: "backtrace for two crashes (dri on, after resize)" http://launchpadlibrarian.net/31462051/gdb-Xorg27-karmic.txt -- screen corruption and segfaults with radeon m6 ly https://bugs.launchpad.net/bugs/421842 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 421842] Re: screen corruption and segfaults with radeon m6 ly
Can reproduce all these bugs on latest updates and alpha-5 live CD, but not alpha-4. To reproduce 'tartan' effect with alpha-5, uninstall compiz-gnome, logout, and run GNOME System Monitor (also seems to occur when there is no window manager, so don't think it's a metacity problem). Compiz Segfault apparently depends on area of window, not height or width. Best workaround remains Option "DRI" "false". ** Changed in: xserver-xorg-video-ati (Ubuntu) Status: Incomplete => Confirmed -- screen corruption and segfaults with radeon m6 ly https://bugs.launchpad.net/bugs/421842 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 479219] Re: lockup when resuming after hibernation (drempels using 100% CPU)
** Attachment added: "output of top and pmap and backtrace on drempels" http://launchpadlibrarian.net/35423925/screensave-cpu2.txt ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/35423926/Dependencies.txt ** Attachment added: "XsessionErrors.txt" http://launchpadlibrarian.net/35423927/XsessionErrors.txt -- lockup when resuming after hibernation (drempels using 100% CPU) https://bugs.launchpad.net/bugs/479219 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 479219] [NEW] lockup when resuming after hibernation (drempels using 100% CPU)
Public bug reported: Binary package hint: gnome-screensaver When returning from hibernation, sometimes the screensaver triggers and there is no login box and no way to unlock the computer. With the "drempels" screensaver and "regard the computer as idle after 1 minute", the machine appeared to load the hibernation file correctly, but I got a single frame of the screensaver during the "fade up". I was able to switch to Ctrl+Alt+F1 and kill drempels at which point the 9.10 welcome/login screen appeared. One problem is the lockup, but a second point is that the screensaver should not trigger in that situation - it was as if it was the time the machine was hibernating was counted as idle time. I've had a similar problem with the "euphoria" screensaver, where Ctrl+Alt+F1 has not worked and it has not been possible to log in remotely. ProblemType: Bug Architecture: i386 Date: Mon Nov 9 13:42:09 2009 DistroRelease: Ubuntu 9.10 Package: gnome-screensaver 2.28.0-0ubuntu3 ProcEnviron: PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic SourcePackage: gnome-screensaver Uname: Linux 2.6.31-14-generic i686 ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- lockup when resuming after hibernation (drempels using 100% CPU) https://bugs.launchpad.net/bugs/479219 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 479219] Re: lockup when resuming after hibernation (drempels using 100% CPU)
BTW the closest bug I can find is Bug 366737. Here is /var/log/Xorg.0.log and some extracts from .xsession-errors (Mplayer has been writing info messages to that file): /usr/bin/xmodmap: unable to open file '/usr/share/apps/kxkb/ubuntu.xmodmap' for reading /usr/bin/xmodmap: 1 error encountered, aborting. (gnome-settings-daemon:3360): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed (polkit-gnome-authentication-agent-1:3443): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed (gnome-settings-daemon:3360): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed Window manager warning: Failed to read saved session file /home/cedric/.config/metacity/sessions/10aa311b48e787157712576699255479150032820033.ms: Failed to open file '/home/cedric/.config/metacity/sessions/10aa311b48e787157712576699255479150032820033.ms': No such file or directory (nautilus:3418): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed Tracker-Message: Checking directory exists:'/home/cedric/.cache/tracker' Tracker-Message: Registering DBus service... Name:'org.freedesktop.Tracker' Starting log: File:'/home/cedric/.local/share/tracker/trackerd.log' Failure: Module initalization failed ** Message: Reading of RFKILL events failed ** Message: killswitches state 3 (firefox:18782): Gdk-WARNING **: XID collision, trouble ahead ** (nm-applet:3422): DEBUG: foo_client_state_changed_cb ** (nm-applet:3422): DEBUG: going for offline with icon: notification-network-wireless-disconnected ** (nm-applet:3422): DEBUG: going for offline with icon: notification-network-wireless-disconnected ** (nm-applet:3422): DEBUG: foo_client_state_changed_cb (gnome-power-manager:3423): devkit-power-gobject-WARNING **: Couldn't suspend: not authorized (gnome-power-manager:3423): devkit-power-gobject-WARNING **: Couldn't hibernate: not authorized ** (gnome-screensaver-preferences:9115): DEBUG: Found best visual for GL: 0x21 ** Attachment added: "/var/log/Xorg.0.log" http://launchpadlibrarian.net/35424703/Xorg.0.log -- lockup when resuming after hibernation (drempels using 100% CPU) https://bugs.launchpad.net/bugs/479219 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 478685] Re: broken compiz / graphics stack / ati drivers
I think this is a duplicate of (parts 1 and 3 of) bug 421842 - your notifications look just like the ones reported there, in Gnome and KDE. What does System Monitor look like with effects off? Here's an example: http://launchpadlibrarian.net/31041978/Screenshot-System%20Monitor- tartan2.png Quote "screen corruption with the system monitor, compiz, and notifications but also with Gnometris. Don't those applications all use Cairo or is it coincidental?" I found these problems are not present with xf86-video-ati-6.12.4, but are in the HEAD version of xf86. Someone else found a workaround (at the expense of performance) in xorg.conf: Option "AccelMethod" "EXA" -- [M6] broken compiz / graphics stack / ati drivers (128MB) https://bugs.launchpad.net/bugs/478685 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 480010] Re: Playback 10% too fast after resume
** Attachment added: "AlsaDevices.txt" http://launchpadlibrarian.net/35478132/AlsaDevices.txt ** Attachment added: "ArecordDevices.txt" http://launchpadlibrarian.net/35478141/ArecordDevices.txt ** Attachment added: "BootDmesg.txt" http://launchpadlibrarian.net/35478156/BootDmesg.txt ** Attachment added: "Card0.Amixer.values.txt" http://launchpadlibrarian.net/35478166/Card0.Amixer.values.txt ** Attachment added: "Card0.Codecs.codec97.0.ac97.0.0.txt" http://launchpadlibrarian.net/35478177/Card0.Codecs.codec97.0.ac97.0.0.txt ** Attachment added: "Card0.Codecs.codec97.0.ac97.0.0.regs.txt" http://launchpadlibrarian.net/35478190/Card0.Codecs.codec97.0.ac97.0.0.regs.txt ** Attachment added: "CurrentDmesg.txt" http://launchpadlibrarian.net/35478200/CurrentDmesg.txt ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/35478205/Dependencies.txt ** Attachment added: "PciMultimedia.txt" http://launchpadlibrarian.net/35478206/PciMultimedia.txt ** Attachment added: "XsessionErrors.txt" http://launchpadlibrarian.net/35478207/XsessionErrors.txt -- Playback 10% too fast after resume https://bugs.launchpad.net/bugs/480010 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 480010] [NEW] Playback 10% too fast after resume
Public bug reported: If the laptop hibernates or suspends and then resumes, there is an odd effect when starting (at least) mplayer video and rhythmbox (probably totem and VLC too). Video and audio playback is noticeably too fast: a 5 min song will play in 4min 35sec of real-time, and about a major second out of tune. I'm guessing the sound card clock is set wrongly on resume. Running mpg321 (with default or -o oss or -o alsa09) will reset it so that playback is correct (mpg321 -o esd does not); restarting pulseaudio (not sure the best way to do this) doesn't seem to have any effect, but sudo alsa force-reload also restores to correct pitch/timing. Ubuntu 9.10 2.6.31-14-generic on Viglen Dossier laptop, soundcard: Intel 82801CA-ICH3 with AD1886 ProblemType: Bug AplayDevices: List of PLAYBACK Hardware Devices card 0: I82801CAICH3 [Intel 82801CA-ICH3], device 0: Intel ICH [Intel 82801CA-ICH3] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer', '/dev/sequencer', '/dev/sequencer2'] failed with exit code 1: Card0.Amixer.info: Card hw:0 'I82801CAICH3'/'Intel 82801CA-ICH3 with AD1886 at irq 5' Mixer name : 'Analog Devices AD1886' Components : 'AC97a:41445361' Controls : 38 Simple ctrls : 24 Date: Tue Nov 10 13:47:08 2009 DistroRelease: Ubuntu 9.10 Package: alsa-base 1.0.20+dfsg-1ubuntu5 PackageArchitecture: all ProcEnviron: PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic SourcePackage: alsa-driver Uname: Linux 2.6.31-14-generic i686 ** Affects: linux Importance: Undecided Status: New ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- Playback 10% too fast after resume https://bugs.launchpad.net/bugs/480010 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 480010] Re: Playback 10% too fast after resume
** Also affects: linux Importance: Undecided Status: New -- Playback 10% too fast after resume https://bugs.launchpad.net/bugs/480010 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 480010] Re: Playback 10% too fast after resume
What do you mean exactly by "the sound driver"? Sorry, I don't really understand linux sound (particularly PulseAudio). As I mention above, "alsa force-reload" does work around the bug, restoring correct pitch and timing. However, "/etc/init.d/alsa-utils restart" apparently has no effect (probably because pulseaudio is loaded). If I killall pulseaudio (so can remove the sound driver) sudo modprobe -r snd_intel8x0 sudo modprobe snd_intel8x0 then that *is* also a valid workaround, yes. I also now notice that if pulseaudio is not loaded and using the snd_intel8x0 module, then suspend and resume does not trigger the bug. (There was something similar in Hardy that set all mixers to 0 after resume, IIRC again only if the sound driver was actually in use when suspending or hibernating. I may be misremembering. BTW the 10% ratio is approximately that between 48kHz and 44.1kHz - could that be significant?) -- Playback 10% too fast after resume https://bugs.launchpad.net/bugs/480010 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 404331] Re: X locks up when scrolling on Radeon Mobility M6 LY
I don't think it's bug 363238, since those are slowdowns rather than lockups and the logs don't seem to match. However, but it hasn't happened in my hacked radeon_drv.so I've been using (without compiz), so it probably has been fixed in 6.12.2. I'm leaving this open for the moment just because I'm not sure what the situation will be in the final karmic release. -- X locks up when scrolling on Radeon Mobility M6 LY https://bugs.launchpad.net/bugs/404331 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 421842] Re: screen corruption and segfaults with radeon m6 ly
My problems 1-3 above still exist with ubuntu-desktop/unknown uptodate 1.174 xserver-xorg-video-ati/unknown uptodate 1:6.12.99+git20090929.7968e1fb-0ubuntu1 xserver-xorg-video-radeon/unknown uptodate 1:6.12.99+git20090929.7968e1fb-0ubuntu1 (and also sometimes console switching with Ctrl+Alt+F1 still doesn't change to text mode.) As Luca says, problem 3 (tartan screen corruption and font problems with visual effects off) disappears with Option "AccelMethod" "EXA" and in fact so do problems 1-2 (crashing and general screen corruption which only occur with Compiz effects enabled). je - if you have time, could you try typing in Abiword with visual effects off? ** Attachment added: "failure to really narrow down tartan problem with git" http://launchpadlibrarian.net/33786587/bisect-tartan.txt -- screen corruption and segfaults with radeon m6 ly https://bugs.launchpad.net/bugs/421842 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 421842] Re: screen corruption and segfaults with radeon m6 ly
It looks like 2 or 3 separate bugs all introduced into radeon_drv.so since Jaunty. From latest karmic, if I do sudo dpkg -i --force-downgrade xserver-xorg-video- radeon_6.12.1-0ubuntu2_i386.deb everything is fine. Compiz effects are a bit slow, but I don't get segfaults or any screen corruption. So I tracked through the git versions... 1) A small amount of screen corruption around the window borders (with DRI and compiz visual effects) seems to have been introduced between xf86-video-ati-6.12.1 and xf86-video-ati-6.12.2. (I think the console/mode switching problems may have started during this period too, but were later fixed.) 2) The segfault was introduced between xf86-video-ati-6.12.2 and xf86-video-ati-6.12.3 in commit 3c348091ae5d88ef3cb850889ca74674e0530b4e (see attached) The conditions to produce this involve resizing a window or doing an operation larger than particular dimensions (with DRI and compiz visual effects), and it looks like the bad commit sets some dimension maxima too optimistically. Changing a line to xf86CrtcSetSizeRange (pScrn, 320, 200, 2560, 1200); stops the segfault, but I guess problems may go deeper than just that line, because it shouldn't segfault at all. This bug is also associated with screen corruption over large areas when a window with focus is dragged over one without focus. 3) The "tartan" patterns and font rendering problems (which only occur *without* DRI and compiz visual effects) are not present in xf86-video- ati-6.12.4, but are in the master head. I don't know how to locate these to an exact commit because of a merge and some compilation problems. Please let me know if I should do anything else, like report these upstream. I'd suggest this bug (421842) concentrates on the segfault (number 2 above), and I could open another ubuntu bug for number 3). Hope this isn't too confusing. ** Attachment added: "git outputs showing commit causing segfault, and a diff with working values" http://launchpadlibrarian.net/32483821/xf86-video-ati-bisect-segfault.txt -- screen corruption and segfaults with radeon m6 ly https://bugs.launchpad.net/bugs/421842 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 421842] [NEW] [karmic] screen corruption and segfaults with radeon m6 ly
Public bug reported: Binary package hint: xorg After an upgrade from 9.04 to 9.10 (which was interrupted as a result of bug 404331), several new problems have appeared. Font rendering in Abiword shows a grid pattern which alters as each character is added to text; certain applications and windows (reliably System Monitor and the NetworkManager 'connected' pop-up) instead of ordinary contents display a pattern that I can best describe as tartan (although the attached images aren't in tartan colours); with DRI on, when a window goes out of focus is it often corrupted; and (also only when DRI is disabled) when creating a large window (e.g. for Thunderbird), Xorg segfaults, part of the left hand of the screen appears on the right and I am returned to the GDM greeter. Nevertheless, this problem does not occur when running from Karmic live CD alpha-4. (see 404331 for additional info). (Since these problems are new in Karmic, and the upgrade was not at all smooth and required some recovery, I suppose they could be the result of corrupt packages.) ProblemType: Bug Architecture: i386 CurrentDmesg: [ 119.832047] Clocksource tsc unstable (delta = -156359368 ns) [ 134.069580] ndiswrapper (iw_set_auth:1585): invalid cmd 12 [ 135.005185] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 145.624053] wlan0: no IPv6 routers present Date: Mon Aug 31 10:13:51 2009 DistroRelease: Ubuntu 9.10 Lsusb: Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Viglen LX Package: xorg 1:7.4+3ubuntu5 PccardctlIdent: Socket 0: no product info available Socket 1: no product info available PccardctlStatus: Socket 0: no card Socket 1: 3.3V 32-bit PC Card ProcCmdLine: root=UUID=8e3337bc-42ea-4a6f-868e-0c3859558c80 ro quiet splash ProcEnviron: PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.28-15.49-generic RelatedPackageVersions: xserver-xorg 1:7.4+3ubuntu5 libgl1-mesa-glx 7.6.0~git20090817.7c422387-0ubuntu3 libdrm2 2.4.12+git20090801.45078630-0ubuntu1 xserver-xorg-video-intel 2:2.8.1-1ubuntu1 xserver-xorg-video-ati 1:6.12.99+git20090825.fc74e119-0ubuntu1 SourcePackage: xorg Uname: Linux 2.6.28-15-generic i686 dmi.bios.date: 08/07/02 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: R1.16 dmi.board.name: Almador System CLEVO:4200-000 dmi.board.vendor: CLEVO Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrR1.16:bd08/07/02:svnViglen:pnLX:pvr0090F503C297:rvnCLEVOCorporation:rnAlmadorSystemCLEVO4200-000:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: LX dmi.product.version: 00:90:F5:03:C2:97 dmi.sys.vendor: Viglen fglrx: Not loaded system: distro: Ubuntu architecture: i686kernel: 2.6.28-15-generic ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- [karmic] screen corruption and segfaults with radeon m6 ly https://bugs.launchpad.net/bugs/421842 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 421842] Re: [karmic] screen corruption and segfaults with radeon m6 ly
** Attachment added: "Some messages from Xorg crashes" http://launchpadlibrarian.net/31041868/radeon-karmic-segfaults-etc.txt ** Attachment added: "BootDmesg.txt" http://launchpadlibrarian.net/31041869/BootDmesg.txt ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/31041870/Dependencies.txt ** Attachment added: "Lspci.txt" http://launchpadlibrarian.net/31041871/Lspci.txt ** Attachment added: "PciDisplay.txt" http://launchpadlibrarian.net/31041872/PciDisplay.txt ** Attachment added: "ProcCpuinfo.txt" http://launchpadlibrarian.net/31041873/ProcCpuinfo.txt ** Attachment added: "ProcInterrupts.txt" http://launchpadlibrarian.net/31041874/ProcInterrupts.txt ** Attachment added: "ProcModules.txt" http://launchpadlibrarian.net/31041875/ProcModules.txt ** Attachment added: "UdevDb.txt" http://launchpadlibrarian.net/31041876/UdevDb.txt ** Attachment added: "UdevLog.txt" http://launchpadlibrarian.net/31041877/UdevLog.txt ** Attachment added: "XorgConf.txt" http://launchpadlibrarian.net/31041878/XorgConf.txt ** Attachment added: "XorgLog.txt" http://launchpadlibrarian.net/31041879/XorgLog.txt ** Attachment added: "XorgLogOld.txt" http://launchpadlibrarian.net/31041880/XorgLogOld.txt ** Attachment added: "Xrandr.txt" http://launchpadlibrarian.net/31041881/Xrandr.txt ** Attachment added: "glxinfo.txt" http://launchpadlibrarian.net/31041882/glxinfo.txt ** Attachment added: "setxkbmap.txt" http://launchpadlibrarian.net/31041883/setxkbmap.txt ** Attachment added: "xdpyinfo.txt" http://launchpadlibrarian.net/31041884/xdpyinfo.txt ** Attachment added: "xkbcomp.txt" http://launchpadlibrarian.net/31041885/xkbcomp.txt -- [karmic] screen corruption and segfaults with radeon m6 ly https://bugs.launchpad.net/bugs/421842 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 421842] Re: [karmic] screen corruption and segfaults with radeon m6 ly
** Attachment added: "abiword showing font corruption" http://launchpadlibrarian.net/31041951/Screenshot-abiword-fontrendering.png -- [karmic] screen corruption and segfaults with radeon m6 ly https://bugs.launchpad.net/bugs/421842 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 421842] Re: [karmic] screen corruption and segfaults with radeon m6 ly
** Attachment added: "System Monitor might look like this" http://launchpadlibrarian.net/31041978/Screenshot-System%20Monitor-tartan2.png -- [karmic] screen corruption and segfaults with radeon m6 ly https://bugs.launchpad.net/bugs/421842 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 421842] Re: [karmic] screen corruption and segfaults with radeon m6 ly
** Attachment added: "or System Monitor might look like this" http://launchpadlibrarian.net/31042043/Screenshot-System%20Monitor-tartan.png -- [karmic] screen corruption and segfaults with radeon m6 ly https://bugs.launchpad.net/bugs/421842 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 404331] Re: X locks up when scrolling on Radeon Mobility M6 LY
** Attachment added: "Xorg log (from installed, buggy Karmic)" http://launchpadlibrarian.net/31042669/Xorg.0.log -- X locks up when scrolling on Radeon Mobility M6 LY https://bugs.launchpad.net/bugs/404331 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 404331] Re: X locks up when scrolling on Radeon Mobility M6 LY
** Attachment added: "dmesg (from installed, buggy Karmic)" http://launchpadlibrarian.net/31042681/dmesg -- X locks up when scrolling on Radeon Mobility M6 LY https://bugs.launchpad.net/bugs/404331 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 404331] Re: X locks up when scrolling on Radeon Mobility M6 LY
Thanks for that, but it looks like whatever improvements have been made in the PPA, they don't affect this bug (or the new bug 421842). I hadn't actually reinstalled the OS or run a live CD since reporting this, just upgraded using Update Manager. The Karmic live CD (alpha-4) seems to cause none of these problems: the most likely differences I can think of are that I have ndisgtk (with a Broadcom 43xx/Linksys PCI card) on the version installed on the hard drive; I had installed and uninstalled the proprietary RealPlayer; or the memory usage is different (I've run memtest86+ for a few hours with no errors). DRI and Compiz is enabled when running the Live CD, there is no xorg.conf to edit that I can see, but scrolling in Firefox is very slow. At least it rules out a simple hardware fault; I can't see how this could be down to a corrupt binary, since each package has probably been freshly downloaded since first reporting this bug, and it must be something in the configuration. I'll attach files from the Live and installed versions for comparison. DRI-only issues mentioned in bug 421842 include segfaults and screen corruption on the window losing focus. ** Attachment added: "DRI-related segfaults, latterly with PPA" http://launchpadlibrarian.net/31042513/radeon-karmic-segfaults-etc.txt -- X locks up when scrolling on Radeon Mobility M6 LY https://bugs.launchpad.net/bugs/404331 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 404331] Re: X locks up when scrolling on Radeon Mobility M6 LY
** Attachment added: "lspci (from installed, buggy Karmic)" http://launchpadlibrarian.net/31042700/lspci -- X locks up when scrolling on Radeon Mobility M6 LY https://bugs.launchpad.net/bugs/404331 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 404331] Re: X locks up when scrolling on Radeon Mobility M6 LY
** Attachment added: "Xorg log - OK live Karmic alpha-4" http://launchpadlibrarian.net/31042726/Xorg.0.log -- X locks up when scrolling on Radeon Mobility M6 LY https://bugs.launchpad.net/bugs/404331 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 404331] Re: X locks up when scrolling on Radeon Mobility M6 LY
** Attachment added: "lsmod - OK live Karmic alpha-4" http://launchpadlibrarian.net/31042777/lsmod -- X locks up when scrolling on Radeon Mobility M6 LY https://bugs.launchpad.net/bugs/404331 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 404331] Re: X locks up when scrolling on Radeon Mobility M6 LY
** Attachment added: "dmesg - OK live Karmic alpha-4" http://launchpadlibrarian.net/31042750/dmesg -- X locks up when scrolling on Radeon Mobility M6 LY https://bugs.launchpad.net/bugs/404331 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 404331] Re: X locks up when scrolling on Radeon Mobility M6 LY
** Attachment added: "lsmod (from installed, buggy Karmic)" http://launchpadlibrarian.net/31042706/lsmod -- X locks up when scrolling on Radeon Mobility M6 LY https://bugs.launchpad.net/bugs/404331 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 404331] Re: X locks up when scrolling on Radeon Mobility M6 LY
** Attachment added: "lspci - OK live Karmic alpha-4" http://launchpadlibrarian.net/31042753/lspci -- X locks up when scrolling on Radeon Mobility M6 LY https://bugs.launchpad.net/bugs/404331 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 480010] Re: Playback 10% too fast after resume
Here are a few more possible clues. There's what may be a related bug at https://bugzilla.redhat.com/show_bug.cgi?id=496119 . Perhaps either the fix in 2.6.30 was incomplete or actually caused this suspend/resume problem. (Also as mentioned adding the options line has no effect on the bug, presumably because it only takes effect on module load, not resume). The clock measurement seems fine for me: Nov 10 12:40:57 laptop23 kernel: [ 18.584052] intel8x0_measure_ac97_clock: measured 54053 usecs (2598 samples) Nov 10 12:40:57 laptop23 kernel: [ 18.584061] intel8x0: clocking to 48000 But this same setting of the clock does not seem to happen on resume after which I get similar symptoms to those in the Red Hat report (i.e. too fast). Is there any way to print the current values of the clock registers on the card? This is what PulseAudio does during suspend and resume: lI: main.c: Got signal SIGUSR2. I: module.c: Loaded "module-cli-protocol-unix" (index: #17; argument: ""). I: alsa-sink.c: Increasing wakeup watermark to 80.00 ms I: client.c: Created 3 "UNIX socket client" D: cli.c: CLI got EOF from user. I: client.c: Freed 3 "UNIX socket client" I: client.c: Created 4 "UNIX socket client" D: alsa-sink.c: Requested to rewind 65536 bytes. D: alsa-sink.c: Limited to 47144 bytes. D: alsa-sink.c: before: 11786 D: alsa-sink.c: after: 11786 D: alsa-sink.c: Rewound 47144 bytes. D: sink.c: Processing rewind... D: source.c: Processing rewind... I: module-device-restore.c: Storing volume/mute/port for device sink:alsa_output.pci-_00_1f.5.iec958-stereo. D: cli.c: CLI got EOF from user. I: client.c: Freed 4 "UNIX socket client" I: client.c: Created 5 "UNIX socket client" D: cli.c: CLI got EOF from user. I: client.c: Freed 5 "UNIX socket client" I: client.c: Created 6 "UNIX socket client" I: module-device-restore.c: Storing volume/mute/port for device source:alsa_input.pci-_00_1f.5.analog-stereo. D: cli.c: CLI got EOF from user. I: client.c: Freed 6 "UNIX socket client" D: alsa-source.c: Read hardware volume: 0: 42% 1: 42% I: client.c: Created 7 "UNIX socket client" D: sink.c: Suspend cause of sink alsa_output.pci-_00_1f.5.iec958-stereo is 0x0001, suspending I: alsa-sink.c: Device suspended... D: source.c: Suspend cause of source alsa_input.pci-_00_1f.5.analog-stereo is 0x0001, suspending I: alsa-source.c: Device suspended... D: reserve-wrap.c: Device lock status of reserve-monitor-wrap...@audio0 changed: not busy D: cli.c: CLI got EOF from user. I: client.c: Freed 7 "UNIX socket client" D: module-udev-detect.c: /dev/snd/controlC0 is accessible: yes I: module-suspend-on-idle.c: Source alsa_input.pci-_00_1f.5.analog-stereo idle for too long, suspending ... I: module-suspend-on-idle.c: Sink alsa_output.pci-_00_1f.5.iec958-stereo idle for too long, suspending ... I: module-device-restore.c: Synced. I: client.c: Created 8 "UNIX socket client" D: cli.c: CLI got EOF from user. I: client.c: Freed 8 "UNIX socket client" I: client.c: Created 9 "UNIX socket client" I: module-device-restore.c: Storing volume/mute/port for device sink:alsa_output.pci-_00_1f.5.iec958-stereo. D: cli.c: CLI got EOF from user. I: client.c: Freed 9 "UNIX socket client" I: client.c: Created 10 "UNIX socket client" D: cli.c: CLI got EOF from user. I: client.c: Freed 10 "UNIX socket client" I: client.c: Created 11 "UNIX socket client" I: module-device-restore.c: Storing volume/mute/port for device source:alsa_input.pci-_00_1f.5.analog-stereo. D: cli.c: CLI got EOF from user. I: client.c: Freed 11 "UNIX socket client" D: alsa-source.c: Read hardware volume: 0: 42% 1: 42% I: client.c: Created 12 "UNIX socket client" D: cli.c: CLI got EOF from user. I: client.c: Freed 12 "UNIX socket client" Apparently nothing relevant. I don't think it's related to PA as such. If I kill pulseaudio, then use mpg321 to play back through the "-o alsa" device and suspend and resume, playback continues at the correct pitch/speed. If I play back using "-o alsa09" or "-o oss" then, after resume, playback is too fast (and continues to be when I restart pulse-session; restarting PA doesn't fix it; starting an application that uses ALSA does). So could it be something to do with restoring instances of open devices that use snd_intel8x0 only once? ** Bug watch added: Red Hat Bugzilla #496119 https://bugzilla.redhat.com/show_bug.cgi?id=496119 -- Playback 10% too fast after resume https://bugs.launchpad.net/bugs/480010 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 480010] Re: Playback 10% too fast after resume
Thanks. Putting default-sample-rate = 48000 into /etc/pulse/daemon.conf does indeed fix it for PulseAudio (which is practically all I use). However, a "mpg321 -o alsa" stream is still 10% too fast on suspend/resume, so presumably there is also an issue in the sound driver? -- Playback 10% too fast after resume https://bugs.launchpad.net/bugs/480010 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 480010] Re: Playback 10% too fast after resume
(correction: I meant "mpg321 -o alsa09") -- Playback 10% too fast after resume https://bugs.launchpad.net/bugs/480010 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1574351] Re: package libperl5.22 5.22.1-9 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of packag
Confirming this is a problem with multiarch in this direction, and the workaround still works: $ dpkg --print-architecture i386 $ dpkg --print-foreign-architectures amd64 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1574351 Title: package libperl5.22 5.22.1-9 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1574351/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641099] Re: PCManFM & Nautilus crash immediately after opening
This is annoyingly intermittent, in particular because there is a
pattern of pcmanfm crashing after launch for 4-6 times in a row, then
you attempt a fix and it appears to work after that. Could it be
dependent on some uninitialised data? I can try a memtest.
Sometimes launching from gnome-terminal without any other changes stops
the crash. I've also tried letting the window open and then choosing a
shortcut from 'Places' and it stays open. So maybe it's related to a
file in my home directory (I have some weird stuff there like tcpdumps).
Note that current options are 'Show thumbnails of files' is not ticked,
but 'Only show thumbnails for local files' is ticked - not that that
combination makes much sense.
I also tried
mkdir causing-pcmanfm-probs && find . -maxdepth 1 -type f -mtime -365 | grep
-v '\./\.' | xargs -I{} mv {} causing-pcmanfm-probs/
and that seemed to allow pcmanfm to open - this time :)
I could try gdb on a dumped core to get some clues, but I always find it
difficult to get one with Apport installed.
PS: comment 2 should read 'with no changes'.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641099
Title:
PCManFM & Nautilus crash immediately after opening
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1641099/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1289977] Re: Ubuntu 14.04 Update breaks grub, resulting in "error: symbol 'grub_term_highlight_color' not found"
My guess is this is a regression in grub-mkconfig between 2.00-19ubuntu2.1 and 2.02~beta2-9. Neither of the situations in Phillip Susi's comment 64 applies to my case. Maybe there are several different possible causes for Grub2 not booting after an upgrade, and I'm not yet convinced these are distinct bugs. In the case of this Lenovo laptop, there's only one drive, no EFI, but grub is installed to a partition. It came with Windows on 3 partitions, so I installed Lubuntu 13.04 to a logical partition, sda5; I later enlarged and moved that partition (Partition table entries are not in disk order) and upgraded to saucy (the only change I made to /etc/default/grub was to comment out GRUB_CMDLINE_LINUX=""). Then today I did the dist-upgrade through the Software Updater and there were no visible errors, but on reboot I got the grub rescue prompt with error "symbol 'grub_term_highlight_color' not found" and the same error in response to "insmod linux". The following warning was in the dist- upgrade log: Installing for i386-pc platform. grub-install: warning: File system `ext2' doesn't support embedding. grub-install: warning: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and their use is discouraged.. Installation finished. No error reported. parted -l output for the drive: Model: ATA ST9250411AS (scsi) Disk /dev/sda: 250GB Sector size (logical/physical): 512B/512B Partition Table: msdos Number Start End SizeType File system Flags 1 1049kB 1259MB 1258MB primary ntfs boot 2 1259MB 91.3GB 90.0GB primary ntfs 4 91.3GB 194GB 103GB extended 5 91.3GB 111GB 20.0GB logical ext4 6 111GB 191GB 80.0GB logical ext4 7 191GB 194GB 2999MB logical 3 239GB 250GB 11.0GB primary ntfs chrooted to sda5 to run debconf-show grub-pc: grub-pc/timeout: 3 grub2/device_map_regenerated: grub-pc/disk_description: grub-pc/install_devices_failed_upgrade: true * grub-pc/install_devices: /dev/disk/by-id/ata-ST9250411AS_5VG7HNEE-part5 grub2/linux_cmdline_default: splash quiet grub-pc/hidden_timeout: false grub-pc/mixed_legacy_and_grub2: true grub-pc/install_devices_disks_changed: grub2/kfreebsd_cmdline_default: quiet splash grub-pc/chainload_from_menu.lst: true grub-pc/postrm_purge_boot_grub: false grub-pc/partition_description: grub2/kfreebsd_cmdline: grub-pc/install_devices_empty: false grub-pc/kopt_extracted: false grub-pc/install_devices_failed: false grub2/linux_cmdline: I booted from USB with 13.04 and did grub-install with "--root- directory=/mnt/sda5" as in Sylvain's helpful comment 79 and could then boot from sda (sometimes sda and sdb are reversed booting from USB). However, on running dpkg-reconfigure grub-pc from within 14.04 as Phillip suggested with the same settings (install to sda5), the problem re-emerged on next boot. A grub-install using 13.10 also seemed to fix it. After a grub-install in 14.04, I can no longer reproduce the grub failure, and am not sure which of these conditions are relevant. It could be that steps to reproduce are: install grub 2.00 only to an ext4 partition; run the 2.02 update-grub on it and reboot. What with this and niggles like losing lxkeymap and clipit (and synaptic listing all origins) "Trusty" isn't living up to its name for me yet. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1289977 Title: Ubuntu 14.04 Update breaks grub, resulting in "error: symbol 'grub_term_highlight_color' not found" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-upgrader/+bug/1289977/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1309698] Re: Lubuntu does not handle /etc/xdg/autostart
See also bug 1308348 ; nm-applet isn't loading since upgrade to 14.04, nor is clipit. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1309698 Title: Lubuntu does not handle /etc/xdg/autostart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxsession/+bug/1309698/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641099] [NEW] PCManFM & Nautilus crash immediately after opening
Public bug reported: Running Ubuntu 16.04.1 LTS ; LXDE, lightdm but not Lubuntu, pcmanfm 1.2.4 (my usual file manager) briefly displays the initial screen and folder side pane, but (possibly on attempting to show home directory contents) crashes. This produced at least one automatic apport report. Nautilus had the same behaviour; didn't try Caja. Removing libnautilus- extension1a and nautilus seemed to fix it last week, but the problem returned today. Running pcmanfm on command line had produced: Gtk-Message: Failed to load module "atk-bridge" Installing libatk-adaptor stopped this warning, but pcmanfm still crashed silently. However, reinstalling: libatk-adaptor (2.18.1-2ubuntu1) libatk-bridge2.0-0 (2.18.1-2ubuntu1) libatk1.0-0 (2.18.0-1) libatk1.0-data (2.18.0-1) libatk1.0-dev (2.18.0-1) seems to have fixed it. Hard to reproduce perhaps, but may happen again, and wanted to log the history and possible workaround. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pcmanfm 1.2.4-1 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 CurrentDesktop: LXDE Date: Fri Nov 11 11:15:22 2016 InstallationDate: Installed on 2009-12-12 (2525 days ago) InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) SourcePackage: pcmanfm Udisks_dump: Error: [Errno 2] No such file or directory: 'udisks' UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pcmanfm (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641099 Title: PCManFM & Nautilus crash immediately after opening To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1641099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641099] Re: PCManFM & Nautilus crash immediately after opening
Started segfaulting again, but resolved spontaneously and showed the files on the third try, with not changes. I also have Caja and Nemo installed, and intend to try Nemo if it happens again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641099 Title: PCManFM & Nautilus crash immediately after opening To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1641099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641099] Re: PCManFM & Nautilus crash immediately after opening
A few more notes:
strace shows:
...
connect(11, {sa_family=AF_LOCAL, sun_path="/tmp/.pcmanfm-socket--0-cedric"},
32) = 0
fcntl64(11, F_GETFL)= 0x2 (flags O_RDWR)
stat64(".", {st_mode=S_IFDIR|0755, st_size=20480, ...}) = 0
stat64("/home/cedric", {st_mode=S_IFDIR|0755, st_size=20480, ...}) = 0
fstat64(11, {st_mode=S_IFSOCK|0777, st_size=0, ...}) = 0
write(11, "/home/cedric\n0\n", 15) = 15
close(11) = 0
close(11) = -1 EBADF (Bad file descriptor)
exit_group(0) = ?
+++ exited with 0 +++
deleting this named socket also seems to allow pcmanfm to launch. Why
does it try to close it twice?
Jan 20 10:53:29 PC-2 kernel: [ 2998.031176] pcmanfm[7486]: segfault at 0
ip b6dad314 sp bfd299ec error 4 in libfm.so.4.0.4[b6d9c000+51000]
pcmanfm ~ crashes
pcmanfm ~/Documents doesn't.
Caja seems to always work.
Memtest OK.
libfm-data:all/xenial-updates 1.2.4-1ubuntu1.1 uptodate
libfm-extra4:i386/xenial-updates 1.2.4-1ubuntu1.1 uptodate
libfm-gtk-data:all/xenial-updates 1.2.4-1ubuntu1.1 uptodate
libfm-gtk4:i386/xenial-updates 1.2.4-1ubuntu1.1 uptodate
libfm-modules:i386/xenial-updates 1.2.4-1ubuntu1.1 uptodate
libfm4:i386/xenial-updates 1.2.4-1ubuntu1.1 uptodate
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641099
Title:
PCManFM & Nautilus crash immediately after opening
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1641099/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641099] Re: PCManFM & Nautilus crash immediately after opening
A few more notes:
strace shows:
...
connect(11, {sa_family=AF_LOCAL, sun_path="/tmp/.pcmanfm-socket--0-cedric"},
32) = 0
fcntl64(11, F_GETFL)= 0x2 (flags O_RDWR)
stat64(".", {st_mode=S_IFDIR|0755, st_size=20480, ...}) = 0
stat64("/home/cedric", {st_mode=S_IFDIR|0755, st_size=20480, ...}) = 0
fstat64(11, {st_mode=S_IFSOCK|0777, st_size=0, ...}) = 0
write(11, "/home/cedric\n0\n", 15) = 15
close(11) = 0
close(11) = -1 EBADF (Bad file descriptor)
exit_group(0) = ?
+++ exited with 0 +++
deleting this named socket also seems to allow pcmanfm to launch. Why
does it try to close it twice?
Jan 20 10:53:29 PC-2 kernel: [ 2998.031176] pcmanfm[7486]: segfault at 0
ip b6dad314 sp bfd299ec error 4 in libfm.so.4.0.4[b6d9c000+51000]
pcmanfm ~ crashes
pcmanfm ~/Documents doesn't.
Caja seems to always work.
Memtest OK.
libfm-data:all/xenial-updates 1.2.4-1ubuntu1.1 uptodate
libfm-extra4:i386/xenial-updates 1.2.4-1ubuntu1.1 uptodate
libfm-gtk-data:all/xenial-updates 1.2.4-1ubuntu1.1 uptodate
libfm-gtk4:i386/xenial-updates 1.2.4-1ubuntu1.1 uptodate
libfm-modules:i386/xenial-updates 1.2.4-1ubuntu1.1 uptodate
libfm4:i386/xenial-updates 1.2.4-1ubuntu1.1 uptodate
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641099
Title:
PCManFM & Nautilus crash immediately after opening
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1641099/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1393175] Re: atop floods /run partition (causes no DNS server problem)
This affected me on a laptop using atop:i386 1.26-2 on Ubuntu 14.04.5 (upgraded from 12.04 I think(. I'd woken the laptop shortly before midnight, and at about 3am, the wireless connection was up but with no DNS. $ sudo dnsmasq dnsmasq: failed to open pidfile /var/run/dnsmasq.pid: No space left on device There was 300M in /run/atop/atop.acct root 4999 1 0 981 1948 0 00:00 ?00:01:35 /usr/bin/atop -a -w /var/log/atop/atop_20171029 600 This was in /etc/cron.d/atop # start atop daily at midnight 0 0 * * * root invoke-rc.d atop _cron So is this a packaging problem? I'd agree with urraca that /var/run (symlink to tmpfs /run) is the wrong place. How about /tmp? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1393175 Title: atop floods /run partition (causes no DNS server problem) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/atop/+bug/1393175/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581535] Re: libnl upgrade breaks Network Manager
Saw this today on Lubuntu 14.04.4. After the following upgrades (from dpkg.log): upgrade libnl-route-3-200:amd64 3.2.21-1 3.2.21-1ubuntu1 upgrade libnl-genl-3-200:amd64 3.2.21-1 3.2.21-1ubuntu1 upgrade libnl-3-200:amd64 3.2.21-1 3.2.21-1ubuntu1 NetworkManager then crashed. Manually configuring /etc/network/interfaces and then upgrade libnm-util2:amd64 0.9.8.8-0ubuntu7.2 0.9.8.8-0ubuntu7.3 upgrade libnm-glib4:amd64 0.9.8.8-0ubuntu7.2 0.9.8.8-0ubuntu7.3 upgrade network-manager:amd64 0.9.8.8-0ubuntu7.2 0.9.8.8-0ubuntu7.3 And NetworkManager runs without crashing, and nm-applet runs without crashing, but only shows in the system tray before disappearing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1581535 Title: libnl upgrade breaks Network Manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1581535/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1318371] Re: jitsi crashes without visible cause
*** This bug is a duplicate of bug 1306901 *** https://bugs.launchpad.net/bugs/1306901 The debug log mentions "symbol lookup error: /usr/lib/jni/libjdic_misc.so: undefined symbol: JAWT_GetAWT" so I believe this is a duplicate of bug 1306901. ** This bug has been marked a duplicate of bug 1306901 jitsi crashes when receiving a call -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1318371 Title: jitsi crashes without visible cause To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jitsi/+bug/1318371/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1306901] Re: jitsi crashes when receiving a call
Reproducible: Running jitsi 2.4.4997 (1ubuntu1 build from Trusty) from the command line; receiving XMPP text message from Pidgin; crash "symbol lookup error: /usr/lib/jni/libjdic_misc.so: undefined symbol: JAWT_GetAWT". Using the build from https://download.jitsi.org/deb/binary/jitsi_2.4.4997-1_i386.deb receives and displays XMPP message as expected. Although still plenty of SEVERE errors visible when running on the command line, it seems usable. I therefore suspect one of the Ubuntu patches is the cause. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1306901 Title: jitsi crashes when receiving a call To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jitsi/+bug/1306901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 404331] Re: X locks up when scrolling on Radeon Mobility M6 LY
A little more information in case it gives any clues: As well as the 3 scenarios above (triggering under identical conditions as far as I can see), there is a fourth after all: d) As a) but the screen blanks. That is, there is a momentary pause, the screen goes entirely black, but I am able to (say) Ctrl+Alt+F1, llogin and sudo reboot. So the screen blanking is a random event happening in about 25% of cases. Type a) is probably more common than the others. I'm attaching a drawing of what the might happen to the scrollbar in the application window when the freeze happens. There are black horizonal bars across the scrollbar, with a further few white pixels immediately below, and sometimes the status line is corrupted. As I mention, any screenshot I can produce is corrupted. If I restart gdm (and/or X) from the console after the freeze, I get the fade into the greeter background (the brown ubuntu spotlight) but the login dialogue is not drawn (usually that space is occupied by a faded version of whatever was on the screen before the gdm restart). So it's similar to the situation after the freeze in a) before restarting gdm: the background is drawn correctly, but any other windows cannot be written. I'm pretty sure that if I could change the video mode (to text, say, and back again), gdm would display correctly. Is there any way to do this - resizecons or xvidtune don't seem to help? If I comment the Option "DRI" "false" workaround (which seemed to work for lucid), and enable Compiz, visual effects seem to work correctly until the freeze. It's fairly easy now to reproduce a freeze: turn visual effects no normal or high, visit a page like this in Epiphany and scroll down - I can scroll down a page or two before the freeze. Also, when this happens it seems Compiz crashes because the title bars disappear. Very little is logged about the problem in Xorg.0.log (I've just added -logverbose to /etc/X11/xinit/xserverrc in case that helps.) Once it's got into this state (a), switching with Ctrl+Alt and back again to the frozen Xorg gives: (II) AIGLX: Suspending AIGLX clients for VT switch [dix] couldn't enable device 9 [dix] couldn't enable device 9 [dix] couldn't enable device 9 [dix] couldn't enable device 9 [dix] couldn't enable device 9 (II) Open ACPI successful (/var/run/acpid.socket) (II) AIGLX: Resuming AIGLX clients after VT switch but of course I'm still in the state of having X frozen with only the cursor working. -- X locks up when scrolling on Radeon Mobility M6 LY https://bugs.launchpad.net/bugs/404331 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 404331] Re: X locks up when scrolling on Radeon Mobility M6 LY
** Attachment added: "drawing of what scrollbar looks like during freeze" http://launchpadlibrarian.net/52634073/Screenshot-scrollbar-reconstruction.png -- X locks up when scrolling on Radeon Mobility M6 LY https://bugs.launchpad.net/bugs/404331 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 404331] Re: X locks up when scrolling on Radeon Mobility M6 LY
** Attachment added: "corrupted screenshot, obtained by doing Alt+PrtSc and saving blind" http://launchpadlibrarian.net/52634121/Screenshot-corrupted.png -- X locks up when scrolling on Radeon Mobility M6 LY https://bugs.launchpad.net/bugs/404331 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 404331] Re: X locks up when scrolling on Radeon Mobility M6 LY
Unfortunately, I think this was never resolved. On upgrading karmic to lucid, the problem re-emerged, even though I was using the Option "DRI" "false" workaround. I've been suffering lockups/crashes at about the same frequency, every 2-3 hours say, for several months (except when I use Windows, which is very tempting - there's a additional and probably separate problem that lucid never resumes successfully from hibernate or suspend.) Again, the lockups are most common when scrolling in Firefox or switching between windows (as if it's a DMA/timing thing?). Again, there's often a corruption of the scroll bar visible either side of the slider, and the bottom 10% of the window hasn't scrolled. However, what happens next differs from the problem as in hardy-jaunty with DRI true. At approximately equal frequency it may be one of: a) The cursor is still moving but the screen not updating (eg I have system monitor in the top panel and it stops). CPU usage is not particularly high. The only thing I can do in Gnome is click on the buttons on the taskbar to minimise applications, and Gnome will redraw the desktop background correctly. I can use Ctrl+Alt+F1 to switch to a text console and reboot cleanly. I've tried taking a screenshot of this state, but it has been saved as a distorted PNG. b) There is a complete freeze: the corruption in the Firefox window may be visible, but the cursor won't move. Even Alt+SysRq+E keys won't work and I have to manually power-cycle. c) As b, but the screen blanks after a fraction of a second, and remains blank. I know in this situation Alt+SysRq won't do anything. With a different Xorg configuration (I may have changed AccelMethod, plus there have been some xorg driver upgrades) I've also seen X/gdm crash and restart after a): (II) Sleep Button: Close (II) UnloadModule: "evdev" (II) Power Button: Close (II) UnloadModule: "evdev" ddxSigGiveUp: Closing log I got a backtrace from a) but never uploaded it, as it wasn't very revealing: #0 0x00daa422 in __kernel_vsyscall () #1 0x0040b93d in ___newselect_nocancel () at ../sysdeps/unix/syscall-template.S:82 #2 0x080a3f77 in WaitForSomething (pClientsReady=0x9b74aa0) at ../../os/WaitFor.c:229 #3 0x080721b0 in Dispatch () at ../../dix/dispatch.c:375 #4 0x08066d7a in main (argc=8, argv=0xbfc3a6d4, envp=0xbfc3a6f8) at ../../dix/main.c:285 -- X locks up when scrolling on Radeon Mobility M6 LY https://bugs.launchpad.net/bugs/404331 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 404331] Re: X locks up when scrolling on Radeon Mobility M6 LY
delayed reopening ** Changed in: xserver-xorg-video-ati (Ubuntu) Status: Fix Released => New -- X locks up when scrolling on Radeon Mobility M6 LY https://bugs.launchpad.net/bugs/404331 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065576] [NEW] Snap inoperable on upgrade: Failed to lock state file/restart snapd.mounts-pre.target
Public bug reported: The first symptom of this that I noticed yesterday was when installing and upgrading packages with synaptic. The system seemed to hang for some minutes on a hook related to snapd, with a message like: > Failed to restart snapd.mounts-pre.target: Operation refused, unit snapd.mounts-pre.target may be requested by dependency only (it is configured to refuse manual start/stop). Extracts of journal around that time: May 12 20:40:54 cedric-x553sa snapd[1024]: main.go:151: Exiting on terminated signal. May 12 20:40:57 cedric-x553sa snapd[1024]: overlord.go:515: Released state lock file May 12 20:40:57 cedric-x553sa snapd[12216]: overlord.go:271: Acquiring state lock file May 12 20:40:57 cedric-x553sa snapd[12216]: overlord.go:276: Acquired state lock file May 12 20:40:57 cedric-x553sa snapd[12216]: patch.go:64: Patching system state level 6 to sublevel 1... May 12 20:40:57 cedric-x553sa snapd[12216]: patch.go:64: Patching system state level 6 to sublevel 2... May 12 20:40:57 cedric-x553sa snapd[12216]: patch.go:64: Patching system state level 6 to sublevel 3... May 12 20:40:57 cedric-x553sa snapd[12216]: daemon.go:247: started snapd/2.62+22.04 (series 16; classic)> May 12 20:40:57 cedric-x553sa snapd[12216]: daemon.go:340: adjusting startup timeout by 1m25s (pessimist> May 12 20:40:58 cedric-x553sa snapd[12216]: backends.go:58: AppArmor status: apparmor is enabled and all> May 12 20:42:35 cedric-x553sa snapd[12777]: overlord.go:271: Acquiring state lock file May 12 20:42:35 cedric-x553sa snapd[12777]: overlord.go:252: Adjusting startup timeout by 1m0s May 12 20:43:35 cedric-x553sa snapd[12777]: overlord.go:273: Failed to lock state file From dpkg.log: 2024-05-12 20:40:38 startup packages configure 2024-05-12 20:40:38 configure snapd:amd64 2.62+22.04 2024-05-12 20:40:38 status unpacked snapd:amd64 2.62+22.04 2024-05-12 20:40:39 status half-configured snapd:amd64 2.62+22.04 2024-05-12 20:48:34 status installed snapd:amd64 2.62+22.04 2024-05-12 20:48:34 configure libglib2.0-0:amd64 2.72.4-0ubuntu2.3 This is the version I was upgrading from: 2024-05-04 08:10:20 status installed snapd:amd64 2.61.3+22.04 2024-05-12 20:40:23 upgrade snapd:amd64 2.61.3+22.04 2.62+22.04 With the same message logged every minute the system is awake: May 12 20:40:57 cedric-x553sa snapd[12216]: daemon.go:340: adjusting startup timeout by 1m25s (pessimisti c estimate of 30s plus 5s per snap) May 12 20:40:58 cedric-x553sa snapd[12216]: backends.go:58: AppArmor status: apparmor is enabled and all features are available May 12 20:42:35 cedric-x553sa snapd[12777]: overlord.go:271: Acquiring state lock file May 12 20:42:35 cedric-x553sa snapd[12777]: overlord.go:252: Adjusting startup timeout by 1m0s May 12 20:43:35 cedric-x553sa snapd[12777]: overlord.go:273: Failed to lock state file May 12 20:43:35 cedric-x553sa snapd[12777]: cannot run daemon: fatal: could not lock state file: timeout for state lock file expired May 12 20:43:36 cedric-x553sa snapd[13637]: overlord.go:271: Acquiring state lock file May 12 20:43:36 cedric-x553sa snapd[13637]: overlord.go:252: Adjusting startup timeout by 1m0s May 12 20:44:36 cedric-x553sa snapd[13637]: overlord.go:273: Failed to lock state file May 12 20:44:36 cedric-x553sa snapd[13637]: cannot run daemon: fatal: could not lock state file: timeout for state lock file expired Then the following morning I come to restart Firefox from the GUI and nothing happens. Message in the log is: May 13 08:48:00 cedric-x553sa snapd[30528]: cannot run daemon: fatal: could not lock state file: timeout for state lock file expired `journalctl -xeu` gives little extra info on the restarts: May 13 08:50:02 cedric-x553sa systemd[1]: Starting Snap Daemon... ░░ Subject: A start job for unit snapd.service has begun execution ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit snapd.service has begun execution. ░░ ░░ The job identifier is 40288. May 13 08:50:02 cedric-x553sa snapd[30651]: overlord.go:271: Acquiring state lock file May 13 08:50:02 cedric-x553sa snapd[30651]: overlord.go:252: Adjusting startup timeout by 1m0s May 13 08:51:02 cedric-x553sa snapd[30651]: overlord.go:273: Failed to lock state file May 13 08:51:02 cedric-x553sa snapd[30651]: cannot run daemon: fatal: could not lock state file: timeout for state lock file expired May 13 08:51:02 cedric-x553sa systemd[1]: snapd.service: Main process exited, code=exited, status=1/FAILU RE ░░ Subject: Unit process exited ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ An ExecStart= process belonging to unit snapd.service has exited. A process 'snap-failure' was present. I tried `systemctl restart snapd` and `systemctl restart snapd.apparmor`. Nothing looks abnormal in logs: May 13 08:55:55 cedric-x553sa systemd[1]: tmp-syscheck\x2dmountpoint\x2d3295765805.mount: Deactivated successfully. May 13 08:55:55 cedric-x553sa snapd[31733]: backends.go:58: AppArmo
