[Bug 1796443] Re: HP EliteBook 745 G5 (Ryzen 2500U) fails to boot unless `mce=off` is set on command line
Kernel linux-image-unsigned-4.19.0-999-generic_4.19.0-999.201810062200_amd64 still has this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796443 Title: HP EliteBook 745 G5 (Ryzen 2500U) fails to boot unless `mce=off` is set on command line To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1796443/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796443] Re: HP EliteBook 745 G5 (Ryzen 2500U) fails to boot unless `mce=off` is set on command line
Changing as requested. ** Changed in: linux (Ubuntu) Status: Triaged => Confirmed ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796443 Title: HP EliteBook 745 G5 (Ryzen 2500U) fails to boot unless `mce=off` is set on command line To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1796443/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796443] Re: HP EliteBook 745 G5 (Ryzen 2500U) fails to boot unless `mce=off` is set on command line
Note: bug also effect 18.04. Debian stable works, as it's based on 4.9. ** Description changed: My new Elitebook, with the latest bios 1.03.01, refuses to boot any kernel later than 4.10 unless mce=off is appended to the kernel command line. As in, there are no kernel messages at all after grub (yes, quiet and splash were removed from the command line). Perhaps it crashes before the efifb kicks in? System operates fine if mce=off is added to the kernel command line (and iommu=soft, but that's a separate issue, and fails with kernel output in that case). I opened upstream bug here : https://bugzilla.kernel.org/show_bug.cgi?id=201291 I bisected the problem down to this commit (and the few before it, which - also added extra MCE output, but didn't actually crash. + also added extra MCE output, but didn't actually crash): - 18807ddb7f88d4ac3797302bafb18143d573e66f is the first bad commit - commit 18807ddb7f88d4ac3797302bafb18143d573e66f - Author: Yazen Ghannam - Date: Tue Nov 15 15:13:53 2016 -0600 + 18807ddb7f88d4ac3797302bafb18143d573e66f is the first bad commit + commit 18807ddb7f88d4ac3797302bafb18143d573e66f + Author: Yazen Ghannam + Date: Tue Nov 15 15:13:53 2016 -0600 - x86/mce/AMD: Reset Threshold Limit after logging error - - The error count field in MCA_MISC does not get reset by hardware when the - threshold has been reached. Software is expected to reset it. Currently, - the threshold limit only gets reset during init or when a user writes to - sysfs. - - If the user is not monitoring threshold interrupts and resetting - the limit then the user will only see 1 interrupt when the limit is first - hit. So if, for example, the limit is set to 10 then only 1 interrupt will - be recorded after 10 errors even if 100 errors have occurred. The user may - then assume that only 10 errors have occurred. + x86/mce/AMD: Reset Threshold Limit after logging error + + The error count field in MCA_MISC does not get reset by hardware when the + threshold has been reached. Software is expected to reset it. Currently, + the threshold limit only gets reset during init or when a user writes to + sysfs. + + If the user is not monitoring threshold interrupts and resetting + the limit then the user will only see 1 interrupt when the limit is first + hit. So if, for example, the limit is set to 10 then only 1 interrupt will + be recorded after 10 errors even if 100 errors have occurred. The user may + then assume that only 10 errors have occurred. There are threads online about this being related to the latest bios. The upstream bug has acpidump attached. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: john 2015 F pulseaudio - /dev/snd/pcmC1D0p: john 2015 F...m pulseaudio - /dev/snd/controlC0: john 2015 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC1: john 2015 F pulseaudio + /dev/snd/pcmC1D0p: john 2015 F...m pulseaudio + /dev/snd/controlC0: john 2015 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Oct 5 23:24:45 2018 InstallationDate: Installed on 2018-09-30 (5 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) Lsusb: - Bus 005 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub - Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 005 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteBook 745 G5 ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=5cf73665-d2a3-4203-80fd-659faf1afea4 ro quiet splash iommu=soft mce=off RelatedPackageVersions: - linux-restricted-modules-4.18.0-8-generic N/A - linux-backports-modules-4.18.0-8-generic N/A - linux-firmware1.175 + linux-restricted-modules-4.18.0-8-generic N/A +
[Bug 1796443] [NEW] HP EliteBook 745 G5 (Ryzen 2500U) fails to boot unless `mce=off` is set on command line
Public bug reported: My new Elitebook, with the latest bios 1.03.01, refuses to boot any kernel later than 4.10 unless mce=off is appended to the kernel command line. As in, there are no kernel messages at all after grub (yes, quiet and splash were removed from the command line). Perhaps it crashes before the efifb kicks in? System operates fine if mce=off is added to the kernel command line (and iommu=soft, but that's a separate issue, and fails with kernel output in that case). I opened upstream bug here : https://bugzilla.kernel.org/show_bug.cgi?id=201291 I bisected the problem down to this commit (and the few before it, which also added extra MCE output, but didn't actually crash. 18807ddb7f88d4ac3797302bafb18143d573e66f is the first bad commit commit 18807ddb7f88d4ac3797302bafb18143d573e66f Author: Yazen Ghannam Date: Tue Nov 15 15:13:53 2016 -0600 x86/mce/AMD: Reset Threshold Limit after logging error The error count field in MCA_MISC does not get reset by hardware when the threshold has been reached. Software is expected to reset it. Currently, the threshold limit only gets reset during init or when a user writes to sysfs. If the user is not monitoring threshold interrupts and resetting the limit then the user will only see 1 interrupt when the limit is first hit. So if, for example, the limit is set to 10 then only 1 interrupt will be recorded after 10 errors even if 100 errors have occurred. The user may then assume that only 10 errors have occurred. There are threads online about this being related to the latest bios. The upstream bug has acpidump attached. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: john 2015 F pulseaudio /dev/snd/pcmC1D0p: john 2015 F...m pulseaudio /dev/snd/controlC0: john 2015 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Oct 5 23:24:45 2018 InstallationDate: Installed on 2018-09-30 (5 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) Lsusb: Bus 005 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteBook 745 G5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=5cf73665-d2a3-4203-80fd-659faf1afea4 ro quiet splash iommu=soft mce=off RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.175 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux StagingDrivers: r8822be UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/26/2018 dmi.bios.vendor: HP dmi.bios.version: Q81 Ver. 01.03.01 dmi.board.name: 83D5 dmi.board.vendor: HP dmi.board.version: KBC Version 08.47.00 dmi.chassis.asset.tag: 5CG838305Y dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ81Ver.01.03.01:bd07/26/2018:svnHP:pnHPEliteBook745G5:pvr:rvnHP:rn83D5:rvrKBCVersion08.47.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 745 G5 dmi.product.sku: 2MG23AV dmi.sys.vendor: HP ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic staging -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796443 Title: HP EliteBook 745 G5 (Ryzen 2500U) fails to boot unless `mce=off` is set on command line To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796443/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747138] [NEW] package resolvconf 1.79ubuntu9 failed to install/upgrade: triggers looping, abandoned
Public bug reported: Happened on upgrade to bionic on 2/2. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: resolvconf 1.79ubuntu9 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 Date: Sat Feb 3 00:58:50 2018 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2015-08-19 (899 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150818) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.19.0.4ubuntu1 apt 1.6~alpha7ubuntu1 SourcePackage: resolvconf Title: package resolvconf 1.79ubuntu9 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to bionic on 2018-02-03 (0 days ago) ** Affects: resolvconf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747138 Title: package resolvconf 1.79ubuntu9 failed to install/upgrade: triggers looping, abandoned To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1747138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1239247] [NEW] intel (haswell) mouse cursor invisible after resume
Public bug reported: Reporting for a different computer so I can't run xorg right now. Running Saucy as of 11 Oct 2013 (will get package versions shortly), a new Yoga 11s system with a haswell i5 processor and graphics.. everything works fine until the laptop is suspended and resumed. After resume, the mouse pointer is invisible. You can move the touchpad around and see things highlighting, so the mouse is actually there, its just not visible. Switching to a text console and back brings back the mouse cursor (ctrl-alt-f1 then ctrl-alt-f7). Is this a kernel problem or an xorg problem? Can it be worked around using swcursor? How does one set that nowadays in the post xorg.conf world? ** Affects: xorg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1239247 Title: intel (haswell) mouse cursor invisible after resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1239247/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1024768] Re: [xorg-edgers] Missing icons in unity launcher and app switcher after update
This bug may be fixed in quantal, but it is most definitely /not/ fix released in 12.04, the LTS release. I use 12.04 on an intel IVB laptop at work and have been patiently waiting for a fix for 12.04 to be released for 6 months now. My laptop works fine for a week or so, and then randomly the unity icons disappear and I need to reboot to get them back. According to comment #28 , I can downgrade mesa to 8.0.2 from main (instead of updates) and it will work again, but then I'm not getting mesa updates (which assumedly helps for intel IVB graphics, especially with docking/undocking stability, iirc). The current mesa version installed on 12.04 (from updates) is below, and exhibits this behavior: $ dpkg-query -l | grep libgl1-mesa-dri ii libgl1-mesa-dri8.0.4-0ubuntu0.2 free implementation of the OpenGL API -- DRI modules ii libgl1-mesa-dri:i386 8.0.4-0ubuntu0.2 free implementation of the OpenGL API -- DRI modules $ apt-cache showpkg libgl1-mesa-dri Package: libgl1-mesa-dri Versions: 8.0.4-0ubuntu0.3 (/var/lib/apt/lists/us.archive.ubuntu.com_ubuntu_dists_precise-updates_main_binary-amd64_Packages) Description Language: File: /var/lib/apt/lists/us.archive.ubuntu.com_ubuntu_dists_precise_main_binary-amd64_Packages MD5: 138eae85587ae78f60d36bcba9033eb1 Description Language: en File: /var/lib/apt/lists/us.archive.ubuntu.com_ubuntu_dists_precise_main_i18n_Translation-en MD5: 138eae85587ae78f60d36bcba9033eb1 8.0.4-0ubuntu0.2 (/var/lib/apt/lists/security.ubuntu.com_ubuntu_dists_precise-security_main_binary-amd64_Packages) (/var/lib/dpkg/status) Description Language: File: /var/lib/apt/lists/us.archive.ubuntu.com_ubuntu_dists_precise_main_binary-amd64_Packages MD5: 138eae85587ae78f60d36bcba9033eb1 Description Language: en File: /var/lib/apt/lists/us.archive.ubuntu.com_ubuntu_dists_precise_main_i18n_Translation-en MD5: 138eae85587ae78f60d36bcba9033eb1 8.0.2-0ubuntu3 (/var/lib/apt/lists/us.archive.ubuntu.com_ubuntu_dists_precise_main_binary-amd64_Packages) Description Language: File: /var/lib/apt/lists/us.archive.ubuntu.com_ubuntu_dists_precise_main_binary-amd64_Packages MD5: 138eae85587ae78f60d36bcba9033eb1 Description Language: en File: /var/lib/apt/lists/us.archive.ubuntu.com_ubuntu_dists_precise_main_i18n_Translation-en MD5: 138eae85587ae78f60d36bcba9033eb1 Is there a way to mark this package as fixed for quantal but not for precise? Or is the official answer for LTS support is to upgrade to 12.10, which isn't LTS?, or run another desktop shell?. This is a rather big black eye for ubuntu when I try to convince others to use it.. Or am I completely missing something, which is always a possibility... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1024768 Title: [xorg-edgers] Missing icons in unity launcher and app switcher after update To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1024768/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 844454] Re: Garbled Chars in xterm (Onieric)
*** This bug is a duplicate of bug 841103 *** https://bugs.launchpad.net/bugs/841103 ** This bug has been marked a duplicate of bug 841103 Text has artifacts when typing something in terminal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/844454 Title: Garbled Chars in xterm (Onieric) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/844454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 635258] Re: Garbled chars in xterm
Its baaack in Onieric Beta 1, intel 4500, unity 3d. To reproduce, just open xterm and start typing what you type will be garbles, but the output will be fine. Similar corruption to before, with a white box covering the first part of any letter typed, and scrolling leaving a few pixels of the fonts on the left side of the terminal window. Now to figure out how to re-open this bug against Onieric... Also, since this has now come back at least twice, and xterm has uncovered other previously unknown bugs (like nouveau w/ 3d support crashing Xorg with fixed width fonts) can we get the ubuntu QA team to add 'xterm' to a test case somewhere? xterm is a basic application, and problems like this with it often indicate real issues that other applications will eventually hit. Just run it, make sure you can type into the window, and that all the fonts look right on both the input and output text, and that it's white text on a black background. Its a simple 30 second test, and will catch issues like this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/635258 Title: Garbled chars in xterm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/635258/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 844454] [NEW] Garbled Chars in xterm (Onieric)
Public bug reported: Bug #635258 is back in Onieric Beta 1, intel 4500, unity 3d. To reproduce, just open xterm and start typing what you type will be garbles, but the output will be fine. Similar corruption to before, with a white box covering the first part of any letter typed, and scrolling leaving a few pixels of the fonts on the left side of the terminal window. I can't figure out how to reopen that bug for onieric, since its closed for maverick. Also, since this has now come back at least twice, and xterm has uncovered other previously unknown bugs (like nouveau w/ 3d support crashing Xorg with fixed width fonts) can we get the ubuntu QA team to add 'xterm' to a test case somewhere? xterm is a basic application, and problems like this with it often indicate real issues that other applications will eventually hit. Just run it, make sure you can type into the window, and that all the fonts look right on both the input and output text, and that it's white text on a black background. Its a simple 30 second test, and will catch issues like this. ** Affects: compiz (Ubuntu) Importance: Undecided Status: New ** Description changed: - Bug #635268 is back in Onieric Beta 1, intel 4500, unity 3d. To + Bug #635258 is back in Onieric Beta 1, intel 4500, unity 3d. To reproduce, just open xterm and start typing what you type will be garbles, but the output will be fine. Similar corruption to before, with a white box covering the first part of any letter typed, and scrolling leaving a few pixels of the fonts on the left side of the terminal window. I can't figure out how to reopen that bug for onieric, since its closed for maverick. Also, since this has now come back at least twice, and xterm has uncovered other previously unknown bugs (like nouveau w/ 3d support crashing Xorg with fixed width fonts) can we get the ubuntu QA team to add 'xterm' to a test case somewhere? xterm is a basic application, and problems like this with it often indicate real issues that other applications will eventually hit. Just run it, make sure you can type into the window, and that all the fonts look right on both the input and output text, and that it's white text on a black background. Its a simple 30 second test, and will catch issues like this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/844454 Title: Garbled Chars in xterm (Onieric) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/844454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 583760] Re: [PATCH] Mouse cursor dissappears with nouveau
I've been running the proposed kernel from natty for the past week-ish with no issues. Now to figure out how to change tags... ** Tags removed: verification-needed-natty ** Tags added: verification-done-natty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/583760 Title: [PATCH] Mouse cursor dissappears with nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/583760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 583760] Re: [PATCH] Mouse cursor dissappears with nouveau
I've been running the seth's kernel (natty amd64) all week with no regressions. Changed back to confirmed. ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/583760 Title: [PATCH] Mouse cursor dissappears with nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/583760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 583760] Re: [PATCH] Mouse cursor dissappears with nouveau
Thanks you, testing now. Its a work machine though so I can't really play until next week. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/583760 Title: [PATCH] Mouse cursor dissappears with nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/583760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 767970] Re: xterm font corruption and X crash with nouveau experimental 3d (not just Unity)
For the record, this is still an issue, and seems to happen with any program that uses the default font.. for example, 'gitk' will also cause X to crash. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/767970 Title: xterm font corruption and X crash with nouveau experimental 3d (not just Unity) To manage notifications about this bug go to: https://bugs.launchpad.net/null/+bug/767970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 583760] Re: Mouse cursor dissappears with nouveau
Still occurring with the latest Natty. Fedora is now including the work around patch in their stock kernels (called drm-nouveau-evo-hang.patch). I've been running this patch on top of the stock ubuntu kernels for months now with no negative side effect. The impact of the patch is low, as its with an experimental driver anyway. Without it, the system becomes nearly unusable when enough cursor hides/unhides happen which cause the buffer to wrap. The only thing the workaround does is shrink the size of the buffer by a few entries. While I would like a real fix, one doesn't appear to be coming from upstream anytime soon. The impact is low, the benefits are high, its an isolated patch that will only affect users with that hardware. Can we -please- get this workaround patch into a natty kernel update, or, at the very least into oneric's(sp?) kernel? The patch ported from fedora would be in driver/gpu/drm/nouveau/nv50_evo.c, approx. lilne 184: /* enable error reporting on the channel */ nv_mask(dev, 0x610028, 0x, 0x00010001 id); evo-dma.max = (4096/4) - 2 + evo-dma.max = ~7; evo-dma.put = 0; evo-dma.cur = evo-dma.put; evo-dma.free = evo-dma.max - evo-dma.cur; original patch from fedora 14: From d0301ece9e093c484f880893dc86d97848360892 Mon Sep 17 00:00:00 2001 From: Ben Skeggs bske...@redhat.com Date: Fri, 19 Nov 2010 18:50:57 +1000 Subject: [PATCH 2/2] drm-nouveau-evo-hang On some GF8+ boards, the display engine will stop processing its push buffer if a wrap-around occurs at a certain point. The exact cause is not known. This patch by David Dillow (rhbz#537065) is a safe enough work-around until it can be solved properly. Signed-off-by: Ben Skeggs bske...@redhat.com --- drivers/gpu/drm/nouveau/nv50_display.c |1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/drivers/gpu/drm/nouveau/nv50_display.c b/drivers/gpu/drm/nouveau/nv50_display.c index 11d366a..4e5402c 100644 --- a/drivers/gpu/drm/nouveau/nv50_display.c +++ b/drivers/gpu/drm/nouveau/nv50_display.c @@ -364,6 +364,7 @@ nv50_display_init(struct drm_device *dev) nv_wr32(dev, 0x610300, nv_rd32(dev, 0x610300) ~1); evo-dma.max = (4096/4) - 2; + evo-dma.max = ~7; evo-dma.put = 0; evo-dma.cur = evo-dma.put; evo-dma.free = evo-dma.max - evo-dma.cur; -- 1.7.3.2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/583760 Title: Mouse cursor dissappears with nouveau -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 767970] Re: xterm font corruption and X crash with nouveau experimental 3d (not just Unity)
Stack Trace added, should be enough to debug or at least file upstream. ** Summary changed: - xterm font corruption with unity and nouveau experimental 3d + xterm font corruption and X crash with nouveau experimental 3d (not just Unity) ** Description changed: Binary package hint: unity Running FOSS/3D-nouveau drivers on Natty as of today, xterm fonts are corrupted horribly on input (not on output). To reproduce: - install natty beta 2 - update all packages - Choose additional drivers and experimental FOSS/3d support - reboot. - - open xterm in reverse video mode 'xterm -rv' (so it's white-on-black, the true way things should be) + - open xterm in reverse video mode 'xterm -rv' (so it's white-on-black, the one true way) - type into the window, all fonts will be horribly corrupted, almost just plain white blocks. however, typing 'ls' blind, the output of ls is fine. but type anything else at the prompt and it works. + - If not immediately, this will cause X to crash. + + Update: This happens with or without Unity This is with an NV50-based video card. My home machine with a radeon 3450 running the FOSS drivers and unity runs xterm without this issue. - This seems similar to another xterm issue with compiz from maverick - (IIRC).. except it affected the intel driver, iirc. I'll see if I can - dig up that bug for reference. + Crash has this stacktrace: + Program received signal SIGSEGV, Segmentation fault. + 0x7f01e23f00e2 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 + (gdb) bt + #0 0x7f01e23f00e2 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 + #1 0x7f01e23f231e in malloc () from /lib/x86_64-linux-gnu/libc.so.6 + #2 0x7f01df964b44 in exaPrepareAccessReg_mixed (pPixmap=0x2516880, + index=0, pReg=0x0) at ../../exa/exa_migration_mixed.c:203 + #3 0x7f01df96f167 in ExaCheckImageGlyphBlt (pDrawable=0x23aef50, + pGC=0x13a5b50, x=2, y=13, nglyph=value optimized out, + ppci=value optimized out, pglyphBase=0x0) at ../../exa/exa_unaccel.c:326 + #4 0x004db8ab in damageText (pDrawable=0x23aef50, pGC=0x13a5b50, x=2, + y=13, count=value optimized out, chars=value optimized out, + fontEncoding=TwoD16Bit, textType=3) at ../../../miext/damage/damage.c:1486 + #5 0x004df4fc in damageImageText16 (pDrawable=0x23aef50, + pGC=0x13a5b50, x=2, y=13, count=value optimized out, + chars=value optimized out) at ../../../miext/damage/damage.c:1567 + #6 0x0042ff47 in doImageText (client=0x23ad880, c=0x7fffe7caccd0) + at ../../dix/dixfonts.c:1548 + #7 0x00431410 in ImageText (client=value optimized out, + pDraw=value optimized out, pGC=value optimized out, + nChars=value optimized out, data=value optimized out, + xorg=value optimized out, yorg=13, reqType=77, did=71303213) + at ../../dix/dixfonts.c:1590 + #8 0x0042b8d0 in ProcImageText16 (client=0x23ad880) + at ../../dix/dispatch.c:2320 + #9 0x0042e2a9 in Dispatch () at ../../dix/dispatch.c:431 + #10 0x00421a7e in main (argc=8, argv=value optimized out, + envp=value optimized out) at ../../dix/main.c:287 ** Changed in: mesa (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/767970 Title: xterm font corruption and X crash with nouveau experimental 3d (not just Unity) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 767970] Re: xterm font corruption and X crash with nouveau experimental 3d (not just Unity)
Not sure how to remove Unity from the affects line. If someone would do that, I'd appreciate it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/767970 Title: xterm font corruption and X crash with nouveau experimental 3d (not just Unity) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 767970] Re: xterm font corruption with unity and nouveau experimental 3d
Posting from phone, excuse brevity. Reproduced with classic desktop and got stack t trace with gdb. Not unity bug. Will update title tonight. Bug is in exa accel of damageText(). See attached info files. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/767970 Title: xterm font corruption with unity and nouveau experimental 3d -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 767970] Re: xterm font corruption with unity and nouveau experimental 3d
Can't upload attachments from a phone? Here's some info unlined: Just launching xterm causes xorg to crash as seen below: (gdb) cont Continuing. Program received signal SIGSEGV, Segmentation fault. 0x7f01e23f00e2 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) bt #0 0x7f01e23f00e2 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f01e23f231e in malloc () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x7f01df964b44 in exaPrepareAccessReg_mixed (pPixmap=0x2516880, index=0, pReg=0x0) at ../../exa/exa_migration_mixed.c:203 #3 0x7f01df96f167 in ExaCheckImageGlyphBlt (pDrawable=0x23aef50, pGC=0x13a5b50, x=2, y=13, nglyph=value optimized out, ppci=value optimized out, pglyphBase=0x0) at ../../exa/exa_unaccel.c:326 #4 0x004db8ab in damageText (pDrawable=0x23aef50, pGC=0x13a5b50, x=2, y=13, count=value optimized out, chars=value optimized out, fontEncoding=TwoD16Bit, textType=3) at ../../../miext/damage/damage.c:1486 #5 0x004df4fc in damageImageText16 (pDrawable=0x23aef50, pGC=0x13a5b50, x=2, y=13, count=value optimized out, chars=value optimized out) at ../../../miext/damage/damage.c:1567 #6 0x0042ff47 in doImageText (client=0x23ad880, c=0x7fffe7caccd0) at ../../dix/dixfonts.c:1548 #7 0x00431410 in ImageText (client=value optimized out, pDraw=value optimized out, pGC=value optimized out, nChars=value optimized out, data=value optimized out, xorg=value optimized out, yorg=13, reqType=77, did=71303213) at ../../dix/dixfonts.c:1590 #8 0x0042b8d0 in ProcImageText16 (client=0x23ad880) at ../../dix/dispatch.c:2320 #9 0x0042e2a9 in Dispatch () at ../../dix/dispatch.c:431 #10 0x00421a7e in main (argc=8, argv=value optimized out, envp=value optimized out) at ../../dix/main.c:287 01:00.0 VGA compatible controller: nVidia Corporation G98M [Quadro NVS 160M] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device 0233 Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at f500 (32-bit, non-prefetchable) [size=16M] Memory at e000 (64-bit, prefetchable) [size=256M] Memory at f200 (64-bit, non-prefetchable) [size=32M] I/O ports at df00 [size=128] [virtual] Expansion ROM at f400 [disabled] [size=128K] Capabilities: access denied Kernel driver in use: nouveau Kernel modules: nouveau, nvidiafb Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersion Description +++-===-===-== un libgl1 none (no description available) ii libgl1-mesa-dri 7.10.2-0ubuntu2 A free implementation of the OpenGL API -- DRI modules ii libgl1-mesa-dri-dbg 7.10.2-0ubuntu2 Debugging symbols for the Mesa DRI modules ii libgl1-mesa-dri-experimenta 7.10.2-0ubuntu2 A free implementation of the OpenGL API -- Extra DRI modules ii libgl1-mesa-glx 7.10.2-0ubuntu2 A free implementation of the OpenGL API -- GLX ru ii xorg1:7.6+4ubuntu3 X.Org X Window System un xorg-docs none (no description available) ii xorg-docs-core 1:1.5.99.901-1ubuntu1 Core documentation for the X.org X Window System un xorg-driver-input none (no description available) un xorg-driver-synaptics none (no description available) un xorg-driver-video none (no description available) un xorg-input-abi-12 none (no description available) un xorg-video-abi-10 none (no description available) un libdrm-nouveau1 none (no description available) ii libdrm-nouveau1a2.4.23-1ubuntu6 Userspace interface to nouveau-specific kernel DRM services -- runtime ii xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca X.Org X server -- Nouveau display driver (experimental) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/767970 Title: xterm font corruption with unity and nouveau experimental 3d -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 767970] Re: xterm font corruption with unity and nouveau experimental 3d
Thanks for looking into this. I fully realize its experimental, but Ubuntu is now providing an easy way to test these things so that bugs can be found. That's the purpose of testing. Plus, the last time something like this happened, it was a real bug in Compiz that was uncovered by a specific driver. I'm not saying you've got to hold up the Natty release or anything, I'm just reporting a bug. This is my work machine, so I can't spend too much time debugging, but I discovered something interesting today when I went to take a screenshot. Whenever I ran xterm, not long afterwards, X crashed (no mouse or keyboard, and I happened to not have sshd running at the time, but pings responded). So I couldn't get a screenshot. Same thing happened again when I ran xterm after rebooting.. that time the xterm window didn't even show before it crashed. The rest of the day, I didn't run xterm, and the system and Unity was fine. So, SOMETHING about xterm and unity causes the nouveau driver to crash. Tomorrow, assuming I have time, I'll try booting into regular gnome with and without compiz and see if i can repeat and get a screenshot. I'll also be logged in via ssh and see if I can get some debug output from either dmesg or .xsession-errors . gnome-terminal is fine, I ran it all day, but I much prefer xterm because it's faster and much less resource intensive. Also, a problem with xterm, the most fundamental X-windows program, suggests a latent problem that's bound to affect other applications. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/767970 Title: xterm font corruption with unity and nouveau experimental 3d -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 648618] Re: evolution memory leak
Saw this today at work, running latest natty. I configured my work calendar (through caldav) then configured my google calendars. went to a meeting and came back to discover e-calendar-factory consuming 2.5G RSS and climbing. I'll try disabling my google calendars and see if that's the issue. Note, I had 1 caldav and 2 google calendars configured. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/648618 Title: evolution memory leak -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 767970] [NEW] xterm font corruption with unity and nouveau experimental 3d
Public bug reported: Binary package hint: unity Running FOSS/3D-nouveau drivers on Natty as of today, xterm fonts are corrupted horribly on input (not on output). To reproduce: - install natty beta 2 - update all packages - Choose additional drivers and experimental FOSS/3d support - reboot. - open xterm in reverse video mode 'xterm -rv' (so it's white-on-black, the true way things should be) - type into the window, all fonts will be horribly corrupted, almost just plain white blocks. however, typing 'ls' blind, the output of ls is fine. but type anything else at the prompt and it works. This is with an NV50-based video card. My home machine with a radeon 3450 running the FOSS drivers and unity runs xterm without this issue. This seems similar to another xterm issue with compiz from maverick (IIRC).. except it affected the intel driver, iirc. I'll see if I can dig up that bug for reference. ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Description changed: Binary package hint: unity Running FOSS/3D-nouveau drivers on Natty as of today, xterm fonts are corrupted horribly on input (not on output). - To reproduce: + To reproduce: - install natty beta 2 - update all packages - Choose additional drivers and experimental FOSS/3d support - reboot. - open xterm in reverse video mode 'xterm -rv' (so it's white-on-black, the true way things should be) - - type into the window, all fonts will be horribly corrupted, almost just plain white blocks. however, typing 'ls' bline, the output of ls is fine. + - type into the window, all fonts will be horribly corrupted, almost just plain white blocks. however, typing 'ls' blind, the output of ls is fine. but type anything else at the prompt and it works. This is with an NV50-based video card. My home machine with a radeon 3450 running the FOSS drivers and unity runs xterm without this issue. + + This seems similar to another xterm issue with compiz from maverick + (IIRC).. except it affected the intel driver, iirc. I'll see if I can + dig up that bug for reference. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/767970 Title: xterm font corruption with unity and nouveau experimental 3d -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 767970] Re: xterm font corruption with unity and nouveau experimental 3d
ahh, here it is: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/635258 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/767970 Title: xterm font corruption with unity and nouveau experimental 3d -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 583714] Re: [drm] nouveau 0000:01:00.0: no space while unhiding cursor
The Fedora bug for this problem has a patch here: https://bugzilla.redhat.com/show_bug.cgi?id=537065#c53 . I've been running with the patch on my work machine which had the same problem for the past week and no problems with disappearing mouse pointers or no space kernel messages. Fedora is now including this patch in their kernel according to the last comment in that bug (however, the last time I checked upstream, they weren't yet). Please consider applying the patch from the fedora bug to the Ubuntu kernel. This is also a duplicate bug about mouse problems with nouveau which i believe is the same problems, butI can't find the bug right now. If I can, I'll post this there as well. ** Bug watch added: Red Hat Bugzilla #537065 https://bugzilla.redhat.com/show_bug.cgi?id=537065 -- [drm] nouveau :01:00.0: no space while unhiding cursor https://bugs.launchpad.net/bugs/583714 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 583714] Re: [drm] nouveau 0000:01:00.0: no space while unhiding cursor
For the record, the stock maverick kernel on the same box would start showing messages almost immediately, so this patch really does seem to fix the issue. Whether it's the correct fix (seems reasonable enough to me, it just leaves a little more space at the top of a buffer) I leave up to the developers, -- [drm] nouveau :01:00.0: no space while unhiding cursor https://bugs.launchpad.net/bugs/583714 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 558657] Re: mouse usage causes Xorg CPU usage to spike, and mouse pointer becomes less responsive
Ahh, this is the bug I meant. The Fedora bug for this problem has a patch here: https://bugzilla.redhat.com/show_bug.cgi?id=537065#c53 . I've been running with the patch on my work machine which had the same problem for the past week and no problems with disappearing mouse pointers or no space kernel messages. Fedora is now including this patch in their kernel according to the last comment in that bug (however, the last time I checked upstream, they weren't yet). Please consider applying this patch to the Ubuntu kernel. -- mouse usage causes Xorg CPU usage to spike, and mouse pointer becomes less responsive https://bugs.launchpad.net/bugs/558657 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 558657] Re: mouse usage causes Xorg CPU usage to spike, and mouse pointer becomes less responsive
I see similar problems on my work machine running an NV50-class (160M?) gpu with nouveau. not sure if this will help, but.. I think there are two bugs here. There is one bug in the nouveau driver and a hardware cursor where the hw cursor engine will eventually stop displaying the cursor, especially with two monitors (as each time you switch monitors it causes this cursor reset, or something). this is indicated by the no space for cursor type messages in the kernel log which eventually culminate in a message (from faded memoy) [drm] EvtChg blah..., and after that, the cursor won't show on one of the monitors again until a reboot. .I -occasionally- saw this in Lucid with two monitors (maybe once a month), but with maverick it happened every few hours at least. I switched to a software cursor and stopped using my second monitor. So, upshot is, you may want to try disabling the hardware cursor and see if you have better luck. The second is that now, using the software cursor, depending on where on the screen I am, just hovering the mouse over a spot in a gtk app causes cpu usage to spike in Xorg, like it's constantly re-drawing the widget that's under the mouse. Hover the mouse over Xterm window and everything's fine. Open a nautilus window and hover over the sidebar, Xorg jumps to 100% and stays there until you move the mouse off, but if you hover over the file icons or the menu, you're fine. Firefox and Thunderbird also have sensative areas of the app which cause cpu usage spikes. So, either we need to fix the hardware cursor in nouveau, or fix the software cursor cpu usage issues. In general, nouveau was much more stable under Lucid and under Maverick, at least on my box. I have no such issues at home running the intel or OSS radeon drivers. -- mouse usage causes Xorg CPU usage to spike, and mouse pointer becomes less responsive https://bugs.launchpad.net/bugs/558657 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 644943] Re: xterm fonts get corrupted while typing
Throwing my hat into the please fix for maverick release. This is really obnoxious, and easy to reproduce (just run xterm in compiz and start typing). It effect my systems with radeon, intel, and nouveau drivers. Please at least assign to someone so that it can be worked on. -- xterm fonts get corrupted while typing https://bugs.launchpad.net/bugs/644943 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 644943] Re: xterm fonts get corrupted while typing
Oh, and something productive to add instead of just whining: Another font artefact happens if you use the xterm popup windows (ctrl-right click, for example). Moving the mouse over the menu entries leaves lines under the menu text. Could the be somehow related to xterm now using true-type fonts? -- xterm fonts get corrupted while typing https://bugs.launchpad.net/bugs/644943 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 477915] Re: AisleRiot Solitaire Crashes GNOME! ... Ubuntu goes to login GDM screen
Happens all the time to my wife who playes spider a lot, to the point where she's regretting updating to karmic. She says that before it happens the cards will seem to stutter when she moves then fast. I tried disabling desktop effects to no benefit. Next, I'll try turning off UXA and go back to EXA. That should do it as UXA is mentioned in the backtrace at the top of this message. Intel X4500, x86_64. Also, a gentle nudge, is anyone working on this? The bug is still marked as incomplete, even though it appears the relevant logs have been attached. If someone is investigating it then please change it back from incomplete. -- AisleRiot Solitaire Crashes GNOME! ... Ubuntu goes to login GDM screen https://bugs.launchpad.net/bugs/477915 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 477915] Re: AisleRiot Solitaire Crashes GNOME! ... Ubuntu goes to login GDM screen
sigh. i forgot. EXA acceleration isn't available anymore. It was too stable... not shiny and new enough. (Yes, I'm aware why UXA is architecturally better, I'm just annoyed at major regressions in the stability of a highly visible driver, and that there's no way to fallback to the old, stable behaviour and I'm annoyed at hearing my wife swear at her computer all the time now... you'll have to excuse my frustration). Please post if you need any further information. Please note I may have misspoke above.. she has a GM965, which I thought was X4500 based but I could be wrong. Here is her full lspci -nnvvv 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller [8086:2a02] (rev 0c) Subsystem: Dell Device [1028:0286] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 29 Region 0: Memory at f6e0 (64-bit, non-prefetchable) [size=1M] Region 2: Memory at e000 (64-bit, prefetchable) [size=256M] Region 4: I/O ports at eff8 [size=8] Capabilities: access denied Kernel driver in use: i915 Kernel modules: i915 -- AisleRiot Solitaire Crashes GNOME! ... Ubuntu goes to login GDM screen https://bugs.launchpad.net/bugs/477915 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 421261] Re: xterm background colour used to be black, now white
Please fix. Still happening to me with up to date Karmic. xterms come up white, even though: j...@localhost:/etc/X11/Xresources$ cat x11-common ! $Id$ ! load color-specific resources for clients that have them #ifdef COLOR *customization: -color #endif ! make Xaw (Athena widget set) clients understand the delete key ! this causes problems with some non-Xaw apps, use with care ! *Text.translations: #override ~Shift ~Meta KeyDelete: delete-next-character() and /etc/X11/app-defaults/XTerm-color contains: ! Set the default text foreground and background colors. *VT100*foreground: gray90 *VT100*background: black Any chance to fix this before karmic release? -- xterm background colour used to be black, now white https://bugs.launchpad.net/bugs/421261 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 332945] Re: [Jaunty] Update Notifier icon would provide useful status information
On Thu, Apr 30, 2009 at 11:20 AM, Matthew Paul Thomas m...@canonical.comwrote: John Clemens: The issue of trying to guess when is the best time to interrupt people is a tricky problem for notifications in general. As getut pointed out, you're conflating interruption with notification. Notifications, like an icon appearing in the notification area and a transient bubble saying hey, you have updates is not an interruption. Notifications can happen at any time, you don't need to guess the best time. This is how they work in Intrepid. Interruptions are opening full blown applications that require user interaction without the user requesting them. You have chosen to interrupt people, which is where I think you're wrong. There is another way... Unfortunately, never is not a viable choice for a mass-market OS on an Internet-connected computer. If you have specific suggestions of heuristics we could use to choose more appropriate times, we'd be delighted to hear them. You're presenting a false choice. Noone is saying you shouldn't notify users of updates. A persistent notification of updates are available is EXACTLY what we want... like we had in intrepid. I can not suggest any heuristics for you, because it's impossible for update manager to know when would be a good time to update. The only entity that has that information is the user, so stop trying to make a decision for them. You're only guessing, and most of the time you're wrong. I design software all the time, and the first thing you look at when looking at an architecture diagram is find out if each part has enough knowledge to make the decision it needs to make. You need two pieces of information to install updates: 1) that updates are available, and 2) when would be a good time to install them. Update manager can only know number 1, the user is the only one who knows number 2. The proper thing to do in this case is tell the user there are updates available, and let them choose when to install them. The update manager notification method in intrepid understood these truths and acted accordingly. You would argue that opening update manager is a persistent notification, and I would disagree. It's a transient interruption. I've kept the jaunty way running on my box for a few days.. and I hate it. People, myself included, close the update window because we're annoyed at being interrupted, without installing updates. Once closed, there is no persistent reminder. In Intrepid, I got a small 20x20 icon that was a constant but unobtrusive reminder. In jaunty I get interrupted with at random intervals (random because of 'security updates', some of which I don't need). Improve the icon if you want, update the verbiage in the notification and tooltip; but don't guess randomly and then throw your arms up in the air when the user closes a random window that showed up and winds up not installing updates, only to repeat the process 7 days later. Please, please reconsider. -- John Clemens cle...@gmail.com -- [Jaunty] Update Notifier icon would provide useful status information https://bugs.launchpad.net/bugs/332945 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: Re: [Bug 332945] Re: [Jaunty] Update Notifier icon would provide useful status information
On Apr 29, 2009 10:10am, Matt Wheeler m...@funkyhat.org wrote He doesn't teach, but that is irrelevant, and confirms my point. If even IT staff are ignoring updates unless they are prompted by a window opening, how many normal users are doing the same? Unlike mac_v, I will not disparage your IT friend for not installing updates immediately. Sometimes there are valid reasons not to install updates. That updated kernel that contains a security fix for a filesystem I don't use, may actually break my wireless card, or my scsi controller. That new version of open office may break a plugin I'm using. It's happened in the past. In fact, good IT people will often test updates on a test machine before installing on their own systems. This goes for every OS, not just Ubuntu. Remember, almost all updates include new features (potential bugs) as well as bug fixes. Ubuntu can't test everything in your environment, just like Apple or MS can't. Using your logic above, would you prefer to have the entire screen gray out and the update manager pop up and be the only thing you can do? That would force people to update, even your IT friend... but is that a good thing? no. If that's what you want, then you should just install all updates automatically without asking the user. I know it's not what I want... Perhaps it's not a good time to install updates. Like you're at a friend's place with metered internet and don't want to run up their bill, or you're on a cell phone connection, or you're not even on a network at the time. Or your significant other is using your computer when the window comes up, they close it and forget to tell you about it. Instead of having a persistent, small icon in the corner of your screen telling you there are updates when you're ready, you have to maximize the update manager and then close it, and then remember to update at some other time because there's no reminder. See my earlier posts in this thread for use cases like the above which were never addressed. This change forces Ubuntu to make a lot of assumptions about my life and my usage. It's impossible for Ubuntu to know when would be a good time for me to update, therefore opening the update manager at random intervals is annoying, nagging, confusing and counterproductive. And that's without getting into the argument over whether auto-launching full, interactive applications without the user requesting them is good UI design or not. This is not an attack on the developers who do a wonderful job. I even understand the overall goal, although I think it's misguided. I simply think this change is wrong and makes Ubuntu more confusing, not less, and as someone who wants Ubuntu to be the best it can be I'd like to see it reverted. I am concerned that there is a bit of bunker mentality with the developers, which given some of the virtiol on this board is not completely unexpected, and I would encourage them to reconsider. -- [Jaunty] Update Notifier icon would provide useful status information https://bugs.launchpad.net/bugs/332945 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 332945] Re: [Jaunty] Update Notifier icon would provide useful status information
Strange, I sent a reply to this via email several hours ago, and it's not in the bug report. Does replying to a bug via email work? I'll post it through the web, and my apologies (and permission to delete one) if it shows up twice. On Thu, 2 Apr 2009, Matthew Paul Thomas wrote: John, one benefit of Ubuntu's package management system is that things like new virus definitions, new Java versions and so on can be combined into the single updates-available window, rather than appearing as separate windows. Point taken, but 1 or N, it's still confusing to the user to be presented with an application window that is not the direct result of an action they've taken, or part an application they're currently running (and even that's dubious). No, we have no plans to put up frequent reminders for restarting. https://lists.ubuntu.com/archives/ubuntu-devel/2009-February/027565.html Good! Glad to hear it. What's so wrong with the updates-available icon is that it's not obvious. https://lists.ubuntu.com/archives/ubuntu-devel/2009-February/027434.html The e-mail analogy fails because the envelope icon is much more obvious. https://lists.ubuntu.com/archives/ubuntu-devel/2009-February/027460.html So the real problem is that the bubble mechanism caused some people to click on the bubble, and that there can never be a perfect icon. I don't necessarily agree with that. By your appriach, any time the OS needs to notify you of anything else besides mail: (how many other 'icons' are universally acceptable? what's the one for web browser, for example? a globe? a firefox logo?) would need to launch the full application as a pop under to tell you whats going on. People have been trained by using other OS's that if they don't understand an icon, they hover over it, and a tooltip tells them what it means. If you're willing to accept the training received from other OS's that the envelope icon always means mail, then why is it so hard to accept other things learned from those OS's. You make a good point about asking people to update when they are disconnected from the Internet. However, I don't know how we would distinguish between disconnected and unable to connect right now, and disconnected but able to connect if asked. If you have particular ideas about how that could be done, please report that as a separate bug. It's an un-knowable. Even if the user has connectivity, perhaps they don't want to update because they're on a metered line (3G modem, at a friends house who has time warner cable modems, etc..). You can't know it, and popping up the full application to the user when you can't know if it's a good time or not does not make sense to me. I'll note that the above post(s) don't really address the main thrusts of my argument (I don't blame you, I shouldn't write rambling posts while going to bed): - That having a full, user-interactive application start up when the user didn't ask it to (even minimised), is downright confusing and freightening to the user, as they don't feel they have control over their own computer. If we thought people were confused by notification bubbles, just wait until full apps start popping up. Yes, update manager always ran before, but it ran in the background, without requiring user interaction. u-m-n was confined to a 22x22 pixel and was clearly - The lack of persistance. I know you claim that having update manager open is a persistent notification. I disagree. You can close update manager, and have no visual queue/reminder that you have updates. This conflation of 'notification' and 'action' may seem like a more efficient idea on the surface, but I disagree that it's a good idea in this case. Lets walk through some use cases, that might be constructive: 1) I want to know if there are updates ready for my computer: - Intrepid: 0 clicks, I check the notification area and can tell immediately if there are: - No updates, no icon - Non-critical updates, normal icon - Critical updates, red icon Total time: less than 1 second. - Jaunty:Mouse movement + 3 clicks + Desktop realestate. I grab my mouse, move it to the menus, click on System-Administration-Update manager. I then wait for UM to load, let it take up a third of my 1440x900 screen, just to see if the box is empty or not. I now have to move my mouse again to close the window. Total time on my fast box: 5 seconds Case 1 assumes that my desire to look for updates doesn't align with the time ubuntu thinks I should look for updates. It's also the worst case scenario in this paradigm shift, as it assumes that the user is proactively interested in updates. I would have assumed that the user saying during install that they didn't want updates installed autmatically would have indicated that, but perhaps not. 2)
[Bug 332945] Re: [Jaunty] Update Notifier icon would provide useful status information
Mark said: We all are complaining because we feel that pop-under or whaterer are just wrong, and we want ubuntu to be perfect :) And I see your point! We've been focused on the idea that the action itself should be immediately accessible to the user (rather than a notification followed by a clickable panel icon followed by the action :-)). But the windows itself could be minimised. Let's explore that. I think it may be too late for Jaunty but I'll see what we can do Please take this as constructive criticism, as it's meant that way. My wife and I have windows on our laptop, but we rarely boot into it since we run Ubuntu all the time. It's the windows that came with pre- installed on each machine so it has a lot of crapware that came from the manufacturer. When we do boot into it, not only do we have a bloated notification area, but we also have to click through several pop-up and pop-under windows (both!) that these applications bombard us with asking us to upgrade our virus definitions, our java version, or whatever. And because they're all loading more DLL's to show a full GUI instead of a notification, they slow the machine down. Often we start doing the thing we need to get done, and get interrupted by another one. If they just blinked away in the notification area, they'd be a lot less annoying. Plus, we're often puzzled to close an app in the foreground and find an update window sitting behind it.. we'll stare at it and go wait, I didn't launch that update app, what's going on?. This type of behaviour makes the user feel they're not in control of their own computer. Running interactive programs that the user didn't ask us to run is a confusing and bad paradigm, whether the window starts minimized or not. We often joke about how glad we are Ubuntu doesn't do that. You know what else is annoying? the annoying windows popup 'reboot now or remind me in 15 minutes after you install updates. Much more intrusive then the Intrepid reboot notification. Is that the type of thing we're moving to for the reboot notification as well? I understand that Mark is making a usability argument that he wants the action to be available immediately. But I don't understand what's so wrong with the 'Hey, I see I've got updates, I should click on the icon and install the updates'. How is that different then the normal 'Hey, I need to write an email, I'll click on the email icon to write my email'? I don't see a difference. Yes, we all agree the notification area was abused, but it was designed for just this case. Actually, take the email analogy further: Imagine if a mail notification applet checked for new mail, didn't actually tell you when you had new email, and then launched your heavyweight email app every 5 hours regardless of what you're doing (unless you got a 'high priority mail', then it would launch immediately). It also appears that this bug report has lost the fact that now there is NO notification that there are (non-critical) updates, allowing the user to decide when to install them. Instead, Ubuntu has (arbitrarily, though I assume user configurable in the future) when it will run the update manager and force the issue the issue on an unsuspecting user. If they decide to not do the updates at that time (after closing this random window that appeared on their desktop they didn't ask for), then there's no persistent notification that there are pending updates. I guess not until the next interval. I've been waiting for updates since I upgraded to jaunty, and now I know why I wasn't seeing them. Some people are interested in non-critical updates too. By focusing solely on the 'I want the user's action to be available immediately when the event happens' perceived problem, we've completely removed the persistent reminder. You've essentially dictated temporarily when you want updates installed, regardless of whether user wants to (or can, think modem users who actually -can't- update from a network at certain times). Without a persistent notification mechanism, they're likely to forget to update the next time they are on a network. (one thing my wife just pointed out, if you close the update window because you're not ready to install updates at that time, then now you've got to go digging through a menu to launch it again, instead of having an icon readily available on your desktop). Bottom line is, the goal of improving the use of the notification area is a noble one, but you've taken away the proper uses of the area and created a major usability regression. Running visible programs the user didn't ask for leads the user confusion and frustration, and the feeling like we're, frankly, back at Bug #1. -- [Jaunty] Update Notifier icon would provide useful status information https://bugs.launchpad.net/bugs/332945 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list
[Bug 268358] Re: evolution crashed with SIGSEGV in get_alignment()
I ran evolution under valgrind for about 5 hours that day on 9-12 and did not have the issue, so I'm afraid that there's not much more I can do. It looks to be non-reproducable. If you want to close it that way, I won't argue. I'll still attach the valgrind log but since the error didn't happen I don't think it'll be useful at all. I'll keep an eye out but I don't know what else I can do (and I need to use evolution regularly, so I can't always run it under valgrind as it's unusably slow). ** Attachment added: valgrind log from a run that did NOT have this crash. http://launchpadlibrarian.net/17888749/valgrind.log.gz -- evolution crashed with SIGSEGV in get_alignment() https://bugs.launchpad.net/bugs/268358 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 259503] Re: MASTER NetworkManager 0.7 crashed with SIGSEGV in nm_device_get_act_request()
Just wanted to comment that I haven't seen this problem recently on my system, so *knock-on-wood* the update seems to have fixed it for me. Thank you. -- MASTER NetworkManager 0.7 crashed with SIGSEGV in nm_device_get_act_request() https://bugs.launchpad.net/bugs/259503 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 268358] Re: evolution crashed with SIGSEGV in get_alignment()
I'll see what I can do. I'm afraid since this randomly happened it might be a while :/ . -- evolution crashed with SIGSEGV in get_alignment() https://bugs.launchpad.net/bugs/268358 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 256508] Re: nautilus crashed with SIGSEGV in cairo_surface_get_font_options()
I'm going to try and help the process along with the cairo folks, but can we consider disabling thumbnails for .svg images for Intrepid until this is fixed? I'm assuming somewhere there's a master list of mimetypes that cairo/gvfs/whatever checks to see if it should load a thumbnail for the file type, can't we just remove svg form that list for the time being? ..because once you get hit by this, it's bad.. especially if you copy an svg file to your desktop.. then you're hosed. -- nautilus crashed with SIGSEGV in cairo_surface_get_font_options() https://bugs.launchpad.net/bugs/256508 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 256508] Re: nautilus crashed with SIGSEGV in cairo_surface_get_font_options()
I tried the commit/patch mentioned in the cairo bug report and it does indeed fix the problem. Please consider adding that patch to the intrepid cairo package, or, if that's too risky, suppressing svg thumbnails as I mentioned above. -- nautilus crashed with SIGSEGV in cairo_surface_get_font_options() https://bugs.launchpad.net/bugs/256508 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 268358] [NEW] evolution crashed with SIGSEGV in get_alignment()
Public bug reported: Binary package hint: evolution Don't really have much more. It was open on another desktop (fullscreen, 1440x900) when I got notice that it crashed. ProblemType: Crash Architecture: amd64 DistroRelease: Ubuntu 8.10 ExecutablePath: /usr/bin/evolution Package: evolution 2.23.91-0ubuntu1 ProcAttrCurrent: unconfined ProcCmdline: evolution --component=mail ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 11 SourcePackage: evolution StacktraceTop: get_alignment (layout=value optimized out, pango_layout_get_extents_internal ( gtk_label_size_request (widget=0x1821810, IA__g_closure_invoke (closure=0x9131d0, signal_emit_unlocked_R (node=0x92efc0, detail=0, Title: evolution crashed with SIGSEGV in get_alignment() Uname: Linux 2.6.27-2-generic x86_64 UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Tags: apport-crash -- evolution crashed with SIGSEGV in get_alignment() https://bugs.launchpad.net/bugs/268358 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 268358] Re: evolution crashed with SIGSEGV in get_alignment()
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/17480214/Dependencies.txt ** Attachment added: Disassembly.txt http://launchpadlibrarian.net/17480215/Disassembly.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/17480216/ProcMaps.txt ** Attachment added: ProcStatus.txt http://launchpadlibrarian.net/17480217/ProcStatus.txt ** Attachment added: Registers.txt http://launchpadlibrarian.net/17480218/Registers.txt ** Attachment added: Stacktrace.txt http://launchpadlibrarian.net/17480219/Stacktrace.txt ** Attachment added: ThreadStacktrace.txt http://launchpadlibrarian.net/17480220/ThreadStacktrace.txt -- evolution crashed with SIGSEGV in get_alignment() https://bugs.launchpad.net/bugs/268358 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 267640] Re: nautilus crashed with SIGSEGV in cairo_surface_get_font_options()
*confused*.. ok, so firefox saved the apport data and resubmitted it somehow. groovy. Now to attach the offending file without browsing to it in firefox.. ** Visibility changed to: Public -- nautilus crashed with SIGSEGV in cairo_surface_get_font_options() https://bugs.launchpad.net/bugs/267640 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 267640] Re: nautilus crashed with SIGSEGV in cairo_surface_get_font_options()
** Attachment added: svg file that causes the problem. It's just a crude ciruit diagram. http://launchpadlibrarian.net/17369184/reversing_circuit.svg -- nautilus crashed with SIGSEGV in cairo_surface_get_font_options() https://bugs.launchpad.net/bugs/267640 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 102680] Re: appletouch does not function properly on 2nd gen macbook
As of the latest kernel update in Intrepid, 2.6.27-2, I'm ablw to 2 and 3 finger tap again, so I'll assume tht something was fixed in the driver between then and now, although nothing jumped out at me in the changelog. Ferdinand, is your problem fixed as well? if so I think you can close this bug at least in relation to Intrepid. -- appletouch does not function properly on 2nd gen macbook https://bugs.launchpad.net/bugs/102680 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 252046] Re: gvfs-hal-volume-monitor crashed with SIGSEGV in strlen()
Just got it while opening up a test file that was shown in archive manager. -- gvfs-hal-volume-monitor crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/252046 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 102680] Re: appletouch does not function properly on 2nd gen macbook
Also can confirm this. It happened after I upgraded to the 2.6.27-1 kernel (note I'm -very happy- with that decision, as I get KVM swapping ability and the ath9k driver.. this is the only problem I'm experiencing.). xorg was also upgraded at the same time, I believe, so it could also be that. Definite regression. My mouse, which was working fine without tweaking before the move to 2.6.27-1, now moves glacially slow, and I lost the ability to two-finger and three-finger tap to middle and right click. Adding the Option MinSpeed 0.4 line to /etc/xorg.conf seems to fix/help with the speed problem (the same might be achievable with 'gsynaptics', which I think changes the same value). But I have not found anything that enables tapping again. My xorg.conf is attached. How is the MinSpeed option normally set, and what could be changed? I'd cut and paste my exact versions of packages, but I have no middle mouse button anymore. linux-image-generic 2.6.27.1.1 xorg-xserver 1:7.4~1ubuntu1 xserver-xorg-input-synaptics 0.15.0+git20080820-1ubuntu1 ** Attachment added: xorg.conf http://launchpadlibrarian.net/17160620/xorg.conf -- appletouch does not function properly on 2nd gen macbook https://bugs.launchpad.net/bugs/102680 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 102680] Re: appletouch does not function properly on 2nd gen macbook
I'm confused as to how to set this bug to be on the 'Intrepid Ibex' radar screen, since the original bug was reported a year ago I'm afraid it's not on the Intrepid list to fix, and it needs to be. Also, this is on a macbook pro core2duo, using the applethouch kernel driver with the synaptics xorg driver. -- appletouch does not function properly on 2nd gen macbook https://bugs.launchpad.net/bugs/102680 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 261591] Re: network-manager-vpnc says there was a problem launching authentication dialog for VPN connection type
I'm not sure why this happened to me, but I just tried it again today, and the password dialog appeared and I connected just fine, even though the version of all the packages I mentioned appears to be the same. Since it works now, and the packages haven't changed, I'm going to close this as pilot error. Sorry for the false alarm. ** Changed in: network-manager-vpnc (Ubuntu) Status: New = Invalid -- network-manager-vpnc says there was a problem launching authentication dialog for VPN connection type https://bugs.launchpad.net/bugs/261591 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 261591] [NEW] network-manager-vpnc says there was a problem launching authentication dialog for VPN connection type
Public bug reported: Binary package hint: network-manager-vpnc This worked fine on Hardy, but fails on Intrepid. Running 'vpnc' from the command like also works. Network manager runs fine otherwise as well. This appears to be just an authentication dialog problem. +++-===-===-== ii network-manager 0.7~~svn20080818t061112+eni0-0ubunt network management framework daemon ii network-manager-gnome 0.7~~svn20080817t183748-0ubuntu1 network management framework (GNOME frontend) ii network-manager-vpnc0.7~~svn20080818t061112-0ubuntu1 network management framework (VPNC plugin) Trying to connect to my work VPN, I can see the option listed in the NM menu, but choosing it shows this dialog: There was a problem launching the authentication dialof for VPN connection type 'org.freedesktop.NetworkManager.vpnc'. Contact your system administrator. I contacted myself but I didn't get very far. This could be a configuration problem on my machine, but I don't understand why and I've never mucked with it other than upgrading to Intrepid about a month ago. Other relevant information: $ cat /etc/NetworkManager/VPN/nm-vpnc-service.name [VPN Connection] name=vpnc service=org.freedesktop.NetworkManager.vpnc program=/usr/lib/network-manager-vpnc/nm-vpnc-service [GNOME] auth-dialog=/usr/lib/network-manager-vpnc/nm-vpnc-auth-dialog properties=libnm-vpnc-properties $ ls -lah /usr/lib/network-manager-vpnc/ total 172K drwxr-xr-x 2 root root 4.0K 2008-08-21 16:52 . drwxr-xr-x 276 root root 96K 2008-08-26 15:05 .. -rwxr-xr-x 1 root root 31K 2008-08-18 17:15 nm-vpnc-auth-dialog -rwxr-xr-x 1 root root 19K 2008-08-18 17:15 nm-vpnc-service -rwxr-xr-x 1 root root 15K 2008-08-18 17:15 nm-vpnc-service-vpnc-helper from daemon.log: NetworkManager: WARN get_secrets_cb(): Couldn't get connection secrets: vpn-password-dialog.c.254 (nma_vpn_request_password): couldn't run VPN auth dialog.. Checking my gnome keyring, I see that the passwords in question are in my keyring and that nm-vpnc-auth-dialog has access to them. ** Affects: network-manager-vpnc (Ubuntu) Importance: Undecided Status: New -- network-manager-vpnc says there was a problem launching authentication dialog for VPN connection type https://bugs.launchpad.net/bugs/261591 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 259503] Re: MASTER NetworkManager 0.7 crashed with SIGSEGV in nm_device_get_act_request()
I believe this is the same bug I'm seeing. I'm using an external USB wireless card. I share this between two notebooks (both have unsupported internal cards), so I'm constantly pulling it from one notebook and putting it in the other. Under Hardy, this is no problem. Pull card out, plug it back in, network manager recovers. Under Intrepid, pulling the card out causes NM to crash. I have to plug the card back in and /etc/init.d/NetworkManager restart to make it work again. Definite regression from Hardy. rt73usb driver. Bus 005 Device 024: ID 050d:705a Belkin Components F5D7050A Wireless Adapter -- MASTER NetworkManager 0.7 crashed with SIGSEGV in nm_device_get_act_request() https://bugs.launchpad.net/bugs/259503 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 255805] Re: evolution compose widget not updating correctly
Confirmed, works for me with new gtk package. Thanks for following up on this with the GTK folks and a quick turnaround on the fix.. it makes writing work email on this machine a little less of an adventure ;) -- evolution compose widget not updating correctly https://bugs.launchpad.net/bugs/255805 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 255805] [NEW] evolution compose widget not updating correctly
Public bug reported: Binary package hint: evolution Don't know if this is an evolution bug, a GTK bug, or an X bug, but I only experience it with evolution on intrepid. It started happening yesterday. Start to compose a new message and start typing in the body of the message.. the text will show up in 3 places, where it should, on the top row offset by about 2 inches, and at the bottom of the screen offset by about 2 inches. Each keystroke seems to fix it for a split second and then it corrupts again. Covering the compose window and exposing it again doesn't cause the body widget (and only the body widget) to refreash. I'll post a screenshot. I'd suspect a GTK or an EXA bug, but I -only- experience this with evolution, and -only- in the compose message body widget... everything else seems fine. Again, this worked fine until yesterday, but I update infrequently, so this could have happened anytime in the past week or so. In the screenshot, you can see the obvious non-updating when a windows appeared over top of it, but the text I typed was 'this is a test', but you'll see that text 3 times in three different parts of the widget. Hardware: Macbook Pro radeon X1600 'ati' driver EXA acceleration metacity, no compiz running. $ sudo apt-cache policy evolution [sudo] password for jclemens: evolution: Installed: 2.23.6-0ubuntu1 Candidate: 2.23.6-0ubuntu1 Version table: *** 2.23.6-0ubuntu1 0 500 http://us.archive.ubuntu.com intrepid/main Packages 100 /var/lib/dpkg/status $ sudo apt-cache policy xserver-xorg xserver-xorg: Installed: 1:7.4~0ubuntu2 Candidate: 1:7.4~0ubuntu2 Version table: *** 1:7.4~0ubuntu2 0 500 http://us.archive.ubuntu.com intrepid/main Packages 100 /var/lib/dpkg/status $ sudo apt-cache policy libgtk2.0-0 libgtk2.0-0: Installed: 2.13.6-0ubuntu1 Candidate: 2.13.6-0ubuntu1 Version table: *** 2.13.6-0ubuntu1 0 500 http://us.archive.ubuntu.com intrepid/main Packages 100 /var/lib/dpkg/status ** Affects: evolution (Ubuntu) Importance: Undecided Status: New -- evolution compose widget not updating correctly https://bugs.launchpad.net/bugs/255805 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 255805] Re: evolution compose widget not updating correctly
** Attachment added: Screenshot-Compose Message.png http://launchpadlibrarian.net/16620552/Screenshot-Compose%20Message.png -- evolution compose widget not updating correctly https://bugs.launchpad.net/bugs/255805 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 217240] Re: kvm - qemu: could not open disk image
It appears this bug is NOT invalid. kvm as shipped with hardy does not open qcow files (plain qcow files, qcow2 files work fine). see debian bug report http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=470664 Unless there's an update I'm missing (quite possibly), this means people with existing qcow libraries can't use kvm on hardy without compiling kvm on thier own, or converting thier entire library of images to qcow2 (or some other format), which is a non-starter for some people who have tools that rely on qcow files. I'm always queasy about changing status on bugs that I neither reported nor worked on, so I'll leave the status for someone else to change now. -- kvm - qemu: could not open disk image https://bugs.launchpad.net/bugs/217240 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 210684] [NEW] gvfs/webdav can't rename files in nautilus
Public bug reported: Binary package hint: gvfs hardy updates as of today. Just set up a webdav share on my private network so my family could have (non-NFS) shares on thier computers. My laptop running hardy can connect to the dav share through nautilus and create and edit files, but it can not rename files. It says 'could not rename file, operation not supported by backend'. Seems like Konqueror can do it just fine so i don't think it's a server problem, i suspect a nautilus gvfs problem. Is the GVFS/webdav backend supposed to support renaming files? ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New -- gvfs/webdav can't rename files in nautilus https://bugs.launchpad.net/bugs/210684 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 205384] Re: [hardy] installer failure with existing RAID+LVM setup
I can confirm the black-on-black text using the alternate install CD on AMD64 (from today) while trying to install on a Dell Optiplex 755. vc1 in all it's ncurses/whiptail goodness is always fine, but switching VT's to anything else AFTER the first time (which works) results in black-on- black text with a blinking cursor. This is run through a KVM switch, but I doubt that's the problem since vc1 shows up fine. I also can't install because after it creates my standard ext3 root partition, it won't mount it. mount fails with 'Invalid argument' when run manually from a vc, even tough a manual mke2fs works fine on the same partition. But I'll open another bug for that. Earlier hardy LiveCD installs work fine on the same hardware, but i wanted a minimal, non-graphical install. -- [hardy] installer failure with existing RAID+LVM setup https://bugs.launchpad.net/bugs/205384 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 111461] Re: restricted-manager doesn't detect that my nvidia card requires restricted drivers
Not sure how I got on this bug, I think I reported a similar problem in gutsy for my nvidia 6150-based onboard graphics a while back. (is there any way to search for bugs marked a duplicate of this one?) Either way, my card now shows up in restricted manager on Hardy (I'm updating daily). So, for my card, this bug is fixed. My video card is: 00:05.0 VGA compatible controller: nVidia Corporation C51 [Geforce 6150 Go] (rev a2) or 00:05.0 0300: 10de:0244 (rev a2) But that does not mean Mark's problem is fixed, I'm just adding my info. -- restricted-manager doesn't detect that my nvidia card requires restricted drivers https://bugs.launchpad.net/bugs/111461 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 127868] Re: gnome-power-manager using between 2% and 10% of cpu.
I have not seen this in a long time, perhaps it was just some glitch in the gnome 2.19 timeframe? Either way, killing it and restarting it fixed it, so running with --verbose --no-daemon wasn't really an option. I'm OK with closing this bug as no longer reproducible, if you so choose. -- gnome-power-manager using between 2% and 10% of cpu. https://bugs.launchpad.net/bugs/127868 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 184919] [Hardy] Installer window too big on 800x600 screen.
Public bug reported: Running the live cd installer for hardy (daily build, from today). I tried to install it in a KVM instance. Once I booted with -std-vga (will open another bug for why cirrus detection fails), I got an 800x600 desktop screen. But when I run the installer, the windows is soo large I can't see the buttons on the bottom of the screen, and there's no way to get to them unless you manually move both panels at the top and bottom of the screen to be on the left/right sides, and move the window up... then you can see the top of the buttons to click on them. Not very useful :). Please make the window a bit smaller so it can run at 800x600, and preferably 640x480 in case the user has to fall back to 'vga' graphics. ** Affects: live-installer (Ubuntu) Importance: Undecided Status: New -- [Hardy] Installer window too big on 800x600 screen. https://bugs.launchpad.net/bugs/184919 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 184931] [Hardy] KVM emulated cirrus video card fails detection.
Public bug reported: Binary package hint: live-installer daily hardy snapshot downloaded today. Tried to install in a KVM instance, which emulated a cirrus logic 5446 video card. On booting the live cd, the install failed to start X-windows because it could not detect the video card. 'Continue' did work, but KVM will be the defacto virtulization platform in the future, casper or whatever it's called now should recognise it. (and any paravirt equivalents thereof afterwards). ** Affects: live-installer (Ubuntu) Importance: Undecided Status: New -- [Hardy] KVM emulated cirrus video card fails detection. https://bugs.launchpad.net/bugs/184931 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 153502] rhythmbox fails to import files with spaces.
Public bug reported: Binary package hint: rhythmbox Gutsy, Rhythmbox 0.11.2, Gnome desktop, fresh install, all updates. I went to reinstall my wifes computer (got rid of windows partition), so I backed up her old home directory including her music collection, tarred it up, and copied it a different server. She had been running feisty and using amarok to copy music to her ipod. I proceeded to install gutsy on her computer from scratch. I untarred her music collection into her new home 'Music' directory under gutsy, and I fired up rhythmbox to see if it would import the files fine (and thus she can stop using amarok), and after I checked the 'Watch for new files' option, I was greeted with only 6 songs, and 6178 import errors. Every file and directory that has a space in the name (or directory) produced a line like this: Couldn't access : file:///home/katy/Music/311/From%20Chaos/32%20Amber.mp3: File not found. Obviously, it seems it's taken the %20 a little too seriously :) A regular 'ls' on the directory seems to show spaces, and Rhythmbox appearently got it right at least at some point because it saw the file was there to begin with. This is kindav a big bug, as it makes rhythmbox completely useless for me at least, and I suspect quite a few others if you really can't import an existing directory tree with spaces in the filenames. ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New -- rhythmbox fails to import files with spaces. https://bugs.launchpad.net/bugs/153502 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 153502] Re: rhythmbox fails to import files with spaces.
for completeness's sake, the above file does exist: ~/Music$ ls 311/From\ Chaos/32\ Amber.mp3 311/From Chaos/32 Amber.mp3 And the 6 files that did import successfully happen to not have any spaces anywhere in the path or the file name. -- rhythmbox fails to import files with spaces. https://bugs.launchpad.net/bugs/153502 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 128845] restricted-manager 0.23 doesn't recognise my laptop's nvidia card.
Public bug reported: Binary package hint: restricted-manager I have a compaq v3000z with an nvidia 6150 [C51] video card that restricted-modules doesn't seem to think is an nvidia card. Info about my card: $ lspci -nvv -s 00:05.0 00:05.0 0300: 10de:0244 (rev a2) (prog-if 00 [VGA]) Subsystem: 103c:30b5 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- Latency: 0 Interrupt: pin A routed to IRQ 21 Region 0: Memory at c200 (32-bit, non-prefetchable) [size=16M] Region 1: Memory at d000 (64-bit, prefetchable) [size=256M] Region 3: Memory at c100 (64-bit, non-prefetchable) [size=16M] [virtual] Expansion ROM at 5000 [disabled] [size=128K] Capabilities: access denied $ cat /sys/devices/pci\:00/\:00\:05.0/modalias pci:v10DEd0244sv103Csd30B5bc03sc00i00 but searching for the first part of that string in the *.restricted file proves fruitless: $ cat /var/cache/restricted-manager/2.6.22-8-generic.restricted | grep pci\:v10DEd03F $ Looking at /var/cache/restricted-manager/2.6.22-8-generic.restricted, is there any particular reason it doesn't just use the 'alias:' llne from modinfo, which if used -would- have matched this string? $ modinfo nvidia | grep alias: alias: char-major-195-* alias: pci:v10DEd*sv*sd*bc03sc02i00* alias: pci:v10DEd*sv*sd*bc03sc00i00* $ $ dpkg --list *restricted* ii linux-restrict 2.6.20.5-15.20 Non-free Linux 2.6.20 modules on x86/x86_64 ii linux-restrict 2.6.20.5-16.28 Non-free Linux 2.6.20 modules on x86/x86_64 ii linux-restrict 2.6.22.1-6.8 Non-free Linux 2.6.22 modules on x86/x86_64 ii linux-restrict 2.6.22.2-7.2 Non-free Linux 2.6.22 modules on x86/x86_64 ii linux-restrict 2.6.22.2-8.4 Non-free Linux 2.6.22 modules on x86/x86_64 ii linux-restrict 2.6.22.2-8.4 Non-free Linux 2.6.22 modules helper script ii linux-restrict 2.6.22.8.8 Restricted Linux modules for generic kernels ii restricted-man 0.23 manage non-free hardware drivers ii ubuntu-restric 9 Commonly used restricted packages Not sure who controls the *.restricted file, so I'm filing under rstricted-manager for now. Please move to linux-restricted-modules if need be. ** Affects: restricted-manager (Ubuntu) Importance: Undecided Status: New -- restricted-manager 0.23 doesn't recognise my laptop's nvidia card. https://bugs.launchpad.net/bugs/128845 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 127868] gnome-power-manager using between 2% and 10% of cpu.
Public bug reported:
Binary package hint: gnome-power-manager
Running Gutsy 64-bit on a dual-core AMD 64-bit laptop (Compaq V3000z).
for the past 2 days my gnome-power-manager has been using between 2 and
10% of my cpu. Beagle was also showing up on the top list at about the
same usage, but after killing beagle, g-p-m still showed up.
I 'strace -f -p 'd gnome-power-manager and at least one thread seemed to
be stuck in a poll loop... i don't know if this is normal or not:
...
[pid 6726] read(22,
\1\0\0\0\377\377\377\377\tb\245F\0\0\0\0\357?\240#\0\0..., 128) = 32
[pid 6726] poll([{fd=22, events=POLLIN|POLLERR|POLLNVAL, revents=POLLIN}], 1,
-1) = 1
[pid 6726] ioctl(23, 0x4122, 0x3) = 0
[pid 6726] ioctl(23, 0x4122, 0x45b82) = 0
[pid 6726] ioctl(23, 0x4122, 0)= 0
[pid 6726] ioctl(23, 0x4122, 0x3) = 0
[pid 6726] ioctl(23, 0x4122, 0x45b82) = 0
[pid 6726] ioctl(23, 0x4122, 0x45b82) = 0
[pid 6726] ioctl(23, 0x4122, 0)= 0
[pid 6726] ioctl(23, 0x4122, 0x2c00ec50) = 0
[pid 6726] ioctl(23, 0x4122, 0x2c00f000) = 0
[pid 6726] ioctl(24, USBDEVFS_IOCTL, 0x2c009300) = 0
[pid 6726] ioctl(23, 0x4122, 0x4800) = 0
[pid 6726] ioctl(23, 0x4122, 0x3) = 0
[pid 6726] ioctl(23, 0x4122, 0x45b82) = 0
[pid 6726] ioctl(23, 0x4122, 0x45b82) = 0
[pid 6726] ioctl(23, 0x4122, 0)= 0
[pid 6726] ioctl(23, 0x4122, 0x2c00ec50) = 0
[pid 6726] ioctl(23, 0x4122, 0x2c00f000) = 0
[pid 6726] ioctl(24, USBDEVFS_IOCTL, 0x2c009300) = 0
[pid 6726] ioctl(23, 0x4122, 0x4800) = 0
[pid 6726] read(22,
\1\0\0\0\377\377\377\377\tb\245F\0\0\0\0\325\303\345$\0..., 128) = 32
[pid 6726] ioctl(23, 0x4122, 0x3) = 0
[pid 6726] ioctl(23, 0x4122, 0x45b82) = 0
[pid 6726] ioctl(23, 0x4122, 0x45b82) = 0
[pid 6726] poll([{fd=22, events=POLLIN|POLLERR|POLLNVAL, revents=POLLIN}], 1,
-1) = 1
[pid 6726] ioctl(23, 0x4122, 0x3) = 0
[pid 6726] ioctl(23, 0x4122, 0x45b82) = 0
[pid 6726] ioctl(23, 0x4122, 0)= 0
[pid 6726] read(22,
\1\0\0\0\0\201\377\377\tb\245F\0\0\0\0\272G+\0\0\0\0\1..., 128) = 32
[pid 6726] poll([{fd=22, events=POLLIN|POLLERR|POLLNVAL, revents=POLLIN}], 1,
-1) = 1
[pid 6726] ioctl(23, 0x4122, 0x3) = 0
[pid 6726] ioctl(23, 0x4122, 0x45b82) = 0
[pid 6726] ioctl(23, 0x4122, 0)= 0
[pid 6726] ioctl(23, 0x4122, 0x3) = 0
[pid 6726] ioctl(23, 0x4122, 0x45b82) = 0
[pid 6726] ioctl(23, 0x4122, 0x45b82) = 0
[pid 6726] ioctl(23, 0x4122, 0)= 0
[pid 6726] ioctl(23, 0x4122, 0x2c00ec50) = 0
[pid 6726] ioctl(23, 0x4122, 0x2c00f000) = 0
[pid 6726] ioctl(24, USBDEVFS_IOCTL, 0x2c009300) = 0
[pid 6726] ioctl(23, 0x4122, 0x4800) = 0
[pid 6726] read(22,
\1\0\0\0\377\377\377\377\tb\245F\0\0\0\0\242\343p\'\0\0..., 128) = 32
[pid 6726] ioctl(23, 0x4122, 0x3) = 0
[pid 6726] ioctl(23, 0x4122, 0x45b82) = 0
[pid 6726] ioctl(23, 0x4122, 0x45b82) = 0
[pid 6726] ioctl(23, 0x4122, 0)= 0
[pid 6726] ioctl(23, 0x4122, 0x2c00ec50) = 0
[pid 6726] ioctl(23, 0x4122, 0x2c00f000) = 0
[pid 6726] ioctl(24, USBDEVFS_IOCTL, 0x2c009300) = 0
[pid 6726] ioctl(23, 0x4122, 0x4800) = 0
[pid 6726] read(22, 0x41801bf0, 128) = -1 EAGAIN (Resource temporarily
unavailable)
[pid 6726] ioctl(23, 0x4122, 0x3) = 0
[pid 6726] ioctl(23, 0x4122, 0x45b82) = 0
[pid 6726] ioctl(23, 0x4122, 0x45b82) = 0
[pid 6726] poll([{fd=22, events=POLLIN|POLLERR|POLLNVAL, revents=POLLIN}], 1,
-1) = 1
[pid 6726] ioctl(23, 0x4122, 0x3) = 0
[pid 6726] ioctl(23, 0x4122, 0x45b82) = 0
[pid 6726] ioctl(23, 0x4122, 0)= 0
[pid 6726] read(22,
\1\0\0\0\377\377\377\377\tb\245F\0\0\0\0\211g\266(\0\0..., 128) = 32
[pid 6726] poll([{fd=22, events=POLLIN|POLLERR|POLLNVAL, revents=POLLIN}], 1,
-1) = 1
It was spinning in this poll loop at a -very- fast rate...i.e., there
was no waiting in the 'poll()' call in strace The even weirder part?
PID 6726 didn't exist on my system.
I 'kill -15'd gnome-power-manager and restarted it by hand and it seems
to be ok now. and strace of that process shows the much more expected
scenario of poll actually pausing a few seconds each through.
Given the strace output of the badly behaving process shows several
-EAGAIN returns (only one posted here, but there are several in the full
screen dump..sorry, didn't save it to a file, i'm cutting from my xterm
back buffer), I'm guessing something wasn't getting cleared from the
poll loop.. but that's just wild speculation.
I know it's not much to go on, but it was keeping my cpu from running
completely idle and thus made my cpu run hot all day.
If it happens again, I'll run some more straces and post those. Sorry I
can't give any more info now.
** Affects: gnome-power-manager (Ubuntu)
Importance: Undecided
Status: New
--
gnome-power-manager using between 2% and 10% of cpu.
https://bugs.launchpad.net/bugs/127868
You received this bug notification because you
[Bug 72814] Re: Crash at login
Should the status of this bug be changed from fixed, since it isn't for gutsy/ppc (on non-altivec machines)? Backing out this change: http://webcvs.freedesktop.org/liboil/liboil/configure.ac?r1=1.89r2=1.90 I'm able to make liboil-0.3.12 (from upstream) work on my G3. v0.3.9 - 0.9.10 also work, obviously, because they were released before this change. I'm a little surprised that -Wa,-maltivec causes issues because i thought that just enabled the assembler to use altivec, but, err, I can't argue with the fact that removing that option makes everything work on my system. -- Crash at login https://bugs.launchpad.net/bugs/72814 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 72814] Re: Crash at login
It doesn't appear that this is fixed in gutsy. I just hit it after an
upgrade to gutsy from feisty on my (non-altivec) iBook G3 900Mhz:
~$ gstreamer-properties
Error re-scanning registry , child terminated by signal
Run 'gstreamer-properties --help' to see a full list of available command line
options.
an strace -f gstreamer-properties shows this, which appears similar to
this bug:
...
[pid 13026] open(/usr/lib/liboil-0.3.so.0, O_RDONLY) = 15
[pid 13026] read(15,
\177ELF\1\2\1\0\0\0\0\0\0\0\0\0\0\3\0\24\0\0\0\1\0\1\207..., 512) = 512
[pid 13026] fstat64(15, {st_mode=S_IFREG|0644, st_size=408628, ...}) = 0
[pid 13026] mmap(0xdb4b000, 483044, PROT_READ|PROT_EXEC,
MAP_PRIVATE|MAP_DENYWRITE, 15, 0) = 0xdb4b000
[pid 13026] mprotect(0xdba1000, 61440, PROT_NONE) = 0
[pid 13026] mmap(0xdbb, 61440, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 15, 0x55000) = 0xdbb
[pid 13026] mmap(0xdbbf000, 7908, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xdbbf000
[pid 13026] mprotect(0x3002e000, 1696, PROT_READ|PROT_WRITE) = 0
[pid 13026] mprotect(0x3002e000, 1696, PROT_READ) = 0
[pid 13026] mprotect(0x7fdc9000, 4096,
PROT_READ|PROT_WRITE|PROT_EXEC|PROT_GROWSDOWN) = 0
[pid 13026] close(15) = 0
[pid 13026] munmap(0x30161000, 117470) = 0
[pid 13026] rt_sigaction(SIGSEGV, {0xf055570, [], 0}, {SIG_DFL}, 8) = 0
[pid 13026] time(NULL) = 1183183457
[pid 13026] rt_sigaction(SIGILL, {0xdb63bb0, [], 0}, {SIG_DFL}, 8) = 0
[pid 13026] --- SIGILL (Illegal instruction) @ 0 (0) ---
[pid 13026] rt_sigprocmask(SIG_UNBLOCK, [ILL], NULL, 8) = 0
[pid 13026] rt_sigaction(SIGILL, {SIG_DFL}, NULL, 8) = 0
[pid 13026] rt_sigaction(SIGILL, {0xdb63bb0, [], 0}, {SIG_DFL}, 8) = 0
[pid 13026] --- SIGILL (Illegal instruction) @ 0 (0) ---
[pid 13026] rt_sigprocmask(SIG_UNBLOCK, [ABRT], NULL, 8) = 0
[pid 13026] tgkill(13026, 13026, SIGABRT) = 0
[pid 13026] --- SIGABRT (Aborted) @ 0 (0) ---
Process 13026 detached
... read resumed , 1) = 0
--- SIGCHLD (Child exited) @ 0 (0) ---
close(3)= 0
waitpid(13026, NULL, 0) = 13026
...
~$ apt-cache showpkg liboil0.3
Package: liboil0.3
Versions:
0.3.12-1
--
Crash at login
https://bugs.launchpad.net/bugs/72814
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 90243] Re: [rt61] Lockups running Feisty on x86-64
This is still a problem as of 4/9/2007 (kernel 2.6.20-14). I just
removed the rt61 card from my system for now, but if it's at all
possible at this late date, please do -not- ship feisty with this bug.
It's very hard to diagnose ('Everything just stops, except mouse
movement!'), and rt61 cards aren't all that uncommon.
May I ask what exactly 'needs info' about this bug?
In my logs I found the following, but the machine ran for a while after
this and then locked up hours later. When it actually locks, there are
no messages saved in the logs, and I don't have a serial console
available right now. Removing the rt61 card from my system has restored
stability.
Apr 9 01:26:26 jennifer kernel: [ 357.311049]
Apr 9 01:26:26 jennifer kernel: [ 357.311050] Call Trace:
Apr 9 01:26:26 jennifer kernel: [ 357.311052] IRQ
[softlockup_tick+250/288] softlockup_tick+0xfa/0x120
Apr 9 01:26:26 jennifer kernel: [ 357.311107] [_end+129904608/2130489456]
:rt61:BeaconTimeout+0x0/0x30
Apr 9 01:26:26 jennifer kernel: [ 357.32] [update_process_times+87/144]
update_process_times+0x57/0x90
Apr 9 01:26:26 jennifer kernel: [ 357.311120]
[smp_local_timer_interrupt+52/96] smp_local_timer_interrupt+0x34/0x60
Apr 9 01:26:26 jennifer kernel: [ 357.311126]
[smp_apic_timer_interrupt+89/128] smp_apic_timer_interrupt+0x59/0x80
Apr 9 01:26:26 jennifer kernel: [ 357.311133] [apic_timer_interrupt+102/112]
apic_timer_interrupt+0x66/0x70
Apr 9 01:26:26 jennifer kernel: [ 357.311145] [_end+129901472/2130489456]
:rt61:MlmeJoinReqAction+0x0/0xe0
Apr 9 01:26:26 jennifer kernel: [ 357.311156] [_spin_unlock_irqrestore+8/16]
_spin_unlock_irqrestore+0x8/0x10
Apr 9 01:26:26 jennifer kernel: [ 357.311164] [try_to_del_timer_sync+83/96]
try_to_del_timer_sync+0x53/0x60
Apr 9 01:26:26 jennifer kernel: [ 357.311172] [del_timer_sync+12/32]
del_timer_sync+0xc/0x20
Apr 9 01:26:26 jennifer kernel: [ 357.311183] [_end+129901509/2130489456]
:rt61:MlmeJoinReqAction+0x25/0xe0
Apr 9 01:26:26 jennifer kernel: [ 357.311195] [_end+129877818/2130489456]
:rt61:MlmeHandler+0xda/0x160
Apr 9 01:26:26 jennifer kernel: [ 357.311205] [_end+129904608/2130489456]
:rt61:BeaconTimeout+0x0/0x30
Apr 9 01:26:26 jennifer kernel: [ 357.311211] [run_timer_softirq+322/448]
run_timer_softirq+0x142/0x1c0
Apr 9 01:26:26 jennifer kernel: [ 357.311221] [__do_softirq+95/208]
__do_softirq+0x5f/0xd0
Apr 9 01:26:26 jennifer kernel: [ 357.311229] [call_softirq+28/40]
call_softirq+0x1c/0x28
Apr 9 01:26:26 jennifer kernel: [ 357.311235] [do_softirq+44/144]
do_softirq+0x2c/0x90
Apr 9 01:26:26 jennifer kernel: [ 357.311240]
[smp_apic_timer_interrupt+94/128] smp_apic_timer_interrupt+0x5e/0x80
Apr 9 01:26:26 jennifer kernel: [ 357.311246] [apic_timer_interrupt+102/112]
apic_timer_interrupt+0x66/0x70
Apr 9 01:26:26 jennifer kernel: [ 357.311249] EOI
I hope this helps, and I hope this will be addressed before feisty
ships.
--
[rt61] Lockups running Feisty on x86-64
https://bugs.launchpad.net/bugs/90243
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 84359] Re: ATA: abnormal status 0x7F on port 0xD407
Core 2 Duo MBP here, same problem. 2.6.20-9 (and previous) worked just fine for me. Any chance we can bump the severity of this bug? The machine will not boot anymore. -- ATA: abnormal status 0x7F on port 0xD407 https://launchpad.net/bugs/84359 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 85943] Re: [apport] Xorg crashed with SIGSEGV while playing a movie in Totem
Me too. Has happened to me twice now. Both times using totem to play an MP3 stream from the internet. This is on a MacBook Pro, 64-bi,t with ati X1600 and fglrx. I suspect an ATI problem (duh). Steps to reproduce: go to wamu.org, click on 'listen live' and choose the 'mp3' stream. soon you'll be presented with your lovely gdm screen. -- [apport] Xorg crashed with SIGSEGV while playing a movie in Totem https://launchpad.net/bugs/85943 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 86328] live-package is uninstallable in feisty. (cdebootstrap version dependency)
Public bug reported: Binary package hint: live-package Trying to install live-package on feisty (amd64) results in: The following packages have unmet dependencies: live-package: Depends: cdebootstrap (= 0.3.15) but it is not going to be installed E: Broken packages This is because cdebootstrap in feisty is v. 0.3.9 . Does it really need cdebootstrap 0.3.15? If so, any word on when that will be updated? ** Affects: live-package (Ubuntu) Importance: Undecided Status: Unconfirmed -- live-package is uninstallable in feisty. (cdebootstrap version dependency) https://launchpad.net/bugs/86328 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 86328] Re: live-package is not installable in feisty (cdebootstrap version dependency)
ahh, I see now. Thanks. ** Summary changed: - live-package is uninstallable in feisty. (cdebootstrap version dependency) + live-package is not installable in feisty (cdebootstrap version dependency) -- live-package is not installable in feisty (cdebootstrap version dependency) https://launchpad.net/bugs/86328 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 83642] fancy isolinux screen on install isos hang xen/kvm HVM guests
Public bug reported: I'm working with ubuntu on Xen right now, and this is a very bad problem. Both the server and desktop install CD's, for both dapper and edgy, use fancy full screen (vbe based?) isolinux install screens. Could we please do away with these screens on the server or alternate install CD? These fancy screens are causing fully virtualized guests that try to boot from these CD's to crash before the boot screen is even drawn. This is true for both Xen and KVM. To clarify, this does not cause the -host- to crash, just the guest, but you get a blank screen and wonder what happened. Background (mostly speculation, but I think it's right): Intel designed VT in a strange way, such that only protected mode instructions are allowed o be virtualized. Anything done in real mode must be emulated...every instruction. The Xen and KVM folks have emulated enough to get things working, but have not handled every instruction, including apparently some of the fancy (VBE?) graphics isolinux on the ubuntu boot cd's is using. (FreeBSD's btx loader also has problems) For reference, AMD's SVM analogue does, in fact, virtualize real mode instructions on the processor, and I'm able to boot all install CD's just fine on an AMD machine. This is an Intel VT 'quirk'. The mini.iso network install CD loads just fine and works, and I can install over an emulated network. And that CD includes a splash screen w/ isolinux, so it's not all VBE operations that cause problems. You should still be able to have a splash screen, but more then that might cause the problems. I've filed a bug against Xen about this, and I just tried KVM and ran into the same issue, so I'm assuming it's th same problem. But until the Xen folks figure out what instructions need to be emulated, and take enough time to care, or Intel comes out with an updated VT implementation that does what AMD's does, we can't just boot up a ubuntu install CD on virtual machines and have it work. My requested solution is that isolinux use just the standard (preferably text) menu and options on the server and/or alternate install CD. Having one full, officially supported install CD that doesn't crash Xen/KVM when trying to install a ubuntu would go a long way towards helping those of us trying to use ubuntu in a virtual environment out. Besides, while I really appreciate all the fancy boot options for a desktop machine, but I would prefer a plain text option for servers anyway. I do, however, see why some would like the opposite. Would it be possible to get the feisty 'server' install CD to forgo the fancy bootup options? NOTE: I think I understand what's going on, but if I'm missing something obvious, please tell me. ** Affects: Ubuntu Importance: Undecided Status: Unconfirmed -- fancy isolinux screen on install isos hang xen/kvm HVM guests https://launchpad.net/bugs/83642 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 83642] Re: fancy isolinux screen on install isos hang xen/kvm HVM guests
To reproduce: Either install Xen, and try booting a HVM xen guest with one of the edgy or dapper full install cd's. Or: - Install feisty on an intel machine with VT enabled. - apt-get install kvm - sudo modprobe kvm-intel - sudo kvm -m 128 -cdrom path to edgy server iso -boot d witness the empty black box that comes up after the bios messages. - close that window. - repeat with '-cdrom path to edgy mini.iso' and witness it work as expected. -- fancy isolinux screen on install isos hang xen/kvm HVM guests https://launchpad.net/bugs/83642 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 79379] Re: gnome-app-install crash (Feisty Fawn 7.04 Herd 2)
Fresh install today (1/15/07..actually i installed dapper, and then upgraded to edgy and then feisty all today) and had the same problem. Would attach crash report but it has the same stack trace, so I don't see the need. -- gnome-app-install crash (Feisty Fawn 7.04 Herd 2) https://launchpad.net/bugs/79379 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 47513] Re: After hibernation, powernowd only controls one CPU
If you're using powernowd, you should be using the userspace governor, not the ondemand one. powernowd will automatically set this when starting up, which is why restarting powernowd solves the problems you are all seeing. When the system goes to sleep and comes back, apparently the kernel (or Ubuntu suspend scripts) aren't saving/restoring the right governor settings. This, to me, is a real bug, as suspend/restore is supposed to restore the system exactly how it was. powernowd has no way of knowing when a suspend happened, nor should it. I can try and work around this in powernowd by periodically polling the scaling_governor file and resetting it to userspace if someone changes it out from under us. But I know of use cases where that would break other people (some people like to run powernowd all the time, and just temporarily disable it by changing the governor to performance for a while, and then change it back to userspace and powernowd just works again, all without restarting powernowd. ) my guess is, if you run powernowd with the -d -vv options by hand and then suspend/resume, you'll see that it's actually chugging along as normal, trying to control both cpus, but it speed change requests are ignored by the fact the system is using the wrong governor after suspend. john.c (powernowd author, and someone who just noticed this on his company's macbook pro core duo running edgy) -- After hibernation, powernowd only controls one CPU https://launchpad.net/bugs/47513 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 47513] Re: After hibernation, powernowd only controls one CPU
Actually, I'm wrong, it looks like edgy has changed to using the 'ondemand ' governor by default instead of the actual powernowd daemon. So my daemon isn't even running anymore. Still the governor isn't getting restored correctly on both CPUs. this is a kernel and/or ubuntu script problem. Not a powernowd problem, unfortunately, so I can't help. john.c -- After hibernation, powernowd only controls one CPU https://launchpad.net/bugs/47513 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 62215] Re: 2.6.17-9.23 regression: crash at boot (amd64)
Confirmed here, looking at the screenshot looks like the exact same problem (RIP is in agp_generic_create_gatt_table()). Athlon X2 3800+, ULi chipset motherboard. ATI 9600LE (r300) video card. This is my first upgrade to edgy on this machine though. All my other machines that run edgy are my new notebooks which are pci-e internally, and they seem to work fine. 2.6.17-8-generic boots fine. -- 2.6.17-9.23 regression: crash at boot (amd64) https://launchpad.net/bugs/62215 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
