[Bug 1929155] [NEW] i cant upgrade from 18.04 to 20.04.02 "Cannot calculate the upgrade"
Public bug reported: sudo do-release-upgrade -d Fetched 44.5 MB in 5s (1,655 kB/s) Checking package manager Reading package lists... Done Building dependency tree Reading state information... Done Calculating the changes Calculating the changes Could not calculate the upgrade An unresolvable problem occurred while calculating the upgrade. This was likely caused by: * Unofficial software packages not provided by Ubuntu Please use the tool 'ppa-purge' from the ppa-purge package to remove software from a Launchpad PPA and try the upgrade again. If none of this applies, then please report this bug using the command 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. If you want to investigate this yourself the log files in '/var/log/dist-upgrade' will contain details about the upgrade. Specifically, look at 'main.log' and 'apt.log'. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.44 Uname: Linux 5.4.15-050415-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 CrashDB: ubuntu Date: Fri May 21 00:36:42 2021 InstallationDate: Installed on 2018-05-17 (1099 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: LANGUAGE=pt_BR:pt:en TERM=xterm-256color PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2021-05-21 (0 days ago) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade third-party-packages ** Attachment added: "main.log" https://bugs.launchpad.net/bugs/1929155/+attachment/5499156/+files/main.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929155 Title: i cant upgrade from 18.04 to 20.04.02 "Cannot calculate the upgrade" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1929155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922230] Re: small freezes when using multiple keyboards
** Description changed: I'm using 2 keyboards for gaming * and when i press a key on one of them, then press a key on the other (which happends some times per second, it's not rare at all) the game freezes a bit, something like 100ms i guess. It's really incapaciting, i can't use XFCE as my daily DE because of this bug - I'm pretty sure this bug comes from XFWM, because when i change it + I'm pretty sure this bug comes from XFWM, because when i change my WM (openbox --replace, for exemple), the bug is gone During my searches about this bug, i found one on Gnome which exactly looks like the one i'm describing : https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1858 It looks like a poor response to MappingNotify event (which indeed happends each time i have the freeze, when i press/release a key on a keyboard which is not the last keyboard which i pressed/released a key) * I don't really use 2 keyboards, but my mouse (Logitech G502), like many mouses with configurable additionnal buttons, is detected as a keyboard by the system, so nearly everytime i press on a mouse button, this bug happends Description: Ubuntu 20.04.2 LTS Release: 20.04 xfwm4: - Installé : 4.14.1-0ubuntu1 - Candidat : 4.14.1-0ubuntu1 - Table de version : - *** 4.14.1-0ubuntu1 500 - 500 http://fr.archive.ubuntu.com/ubuntu focal/universe amd64 Packages - 100 /var/lib/dpkg/status + Installé : 4.14.1-0ubuntu1 + Candidat : 4.14.1-0ubuntu1 + Table de version : + *** 4.14.1-0ubuntu1 500 + 500 http://fr.archive.ubuntu.com/ubuntu focal/universe amd64 Packages + 100 /var/lib/dpkg/status I expected no freeze when i use my keyboard or mouse Instead, each time i use my keyboard or mouse, my computer has a small freeze ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xfwm4 4.14.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Apr 1 13:30:45 2021 InstallationDate: Installed on 2021-03-10 (21 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: - LANGUAGE=fr_FR - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=fr_FR.UTF-8 - SHELL=/bin/zsh + LANGUAGE=fr_FR + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=fr_FR.UTF-8 + SHELL=/bin/zsh SourcePackage: xfwm4 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922230 Title: small freezes when using multiple keyboards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfwm4/+bug/1922230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922230] [NEW] small freezes when using multiple keyboards
Public bug reported: I'm using 2 keyboards for gaming * and when i press a key on one of them, then press a key on the other (which happends some times per second, it's not rare at all) the game freezes a bit, something like 100ms i guess. It's really incapaciting, i can't use XFCE as my daily DE because of this bug I'm pretty sure this bug comes from XFWM, because when i change it (openbox --replace, for exemple), the bug is gone During my searches about this bug, i found one on Gnome which exactly looks like the one i'm describing : https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1858 It looks like a poor response to MappingNotify event (which indeed happends each time i have the freeze, when i press/release a key on a keyboard which is not the last keyboard which i pressed/released a key) * I don't really use 2 keyboards, but my mouse (Logitech G502), like many mouses with configurable additionnal buttons, is detected as a keyboard by the system, so nearly everytime i press on a mouse button, this bug happends Description:Ubuntu 20.04.2 LTS Release:20.04 xfwm4: Installé : 4.14.1-0ubuntu1 Candidat : 4.14.1-0ubuntu1 Table de version : *** 4.14.1-0ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu focal/universe amd64 Packages 100 /var/lib/dpkg/status I expected no freeze when i use my keyboard or mouse Instead, each time i use my keyboard or mouse, my computer has a small freeze ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xfwm4 4.14.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Apr 1 13:30:45 2021 InstallationDate: Installed on 2021-03-10 (21 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/zsh SourcePackage: xfwm4 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xfwm4 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922230 Title: small freezes when using multiple keyboards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfwm4/+bug/1922230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 893681] Re: No space left on device during kernel update on btrfs
I forgot to specify that I don't have btrfs, indeed; in my case it was an ext4 partition. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/893681 Title: No space left on device during kernel update on btrfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/btrfs/+bug/893681/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 893681] Re: No space left on device during kernel update on btrfs
I had the same problem, too; in my case, I had enough free space, but I was out of inodes. You can check if it is the case for you with this command: df -i If the percentage of used inodes is near 100%, you can probably solve by deleting something (folders with tons of small files are your enemy). It would be nice to understand why the problem arises, though; maybe some badly tuned default params for small partitions? I'm using a netbook with a 4GB SSD disk. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/893681 Title: No space left on device during kernel update on btrfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/btrfs/+bug/893681/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 592295] Re: omapdss DISPC error: SYNC_LOST_DIGIT
Hi, I've got same issue on my pandaboard rel. A3. kernel is: = adriano@pandaboard:~$ uname -r 2.6.38-1208-omap4 = and the error printed out on serial console in a while(1) loop = [ 730.415527] omapdss DISPC error: SYNC_LOST_DIGIT, disabling TV = the distro is ubuntu headless 11.04 = adriano@pandaboard:~$ uname -a Linux pandaboard 2.6.38-1208-omap4 #11-Ubuntu SMP PREEMPT Fri Apr 15 16:34:35 UTC 2011 armv7l armv7l armv7l GNU/Linux = I hope to wrote on the right place, best regards Adriano -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/592295 Title: omapdss DISPC error: SYNC_LOST_DIGIT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-ti-omap4/+bug/592295/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 554172] Re: cups not starting at boot
*** This bug is a duplicate of bug 524186 *** https://bugs.launchpad.net/bugs/524186 ** Description changed: Binary package hint: cups Cups is not loading on my machine at boot, must run sudo /etc/init.d/cups start to after booting to print. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: cups 1.4.2-10 ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1 Uname: Linux 2.6.32-19-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Fri Apr 2 13:07:35 2010 InstallationMedia: Ubuntu 10.04 Lucid Lynx - Alpha i386 (20100401) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Connection refused MachineType: Dell Inc. Studio XPS 1340 Papersize: letter PpdFiles: Brother-HL-2170W-series: Brother HL-2170W Foomatic/pxlmono (recommended) ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-19-generic root=UUID=615bbe85-506a-4152-af5a-a5c2da303d83 ro quiet splash ProcEnviron: - LANG=en_US.utf8 - SHELL=/bin/bash + LANG=en_US.utf8 + SHELL=/bin/bash SourcePackage: cups dmi.bios.date: 09/08/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0Y279R dmi.board.vendor: Dell Inc. dmi.board.version: A11 dmi.chassis.asset.tag: 1234567890 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A11 dmi.modalias: dmi:bvnDellInc.:bvrA11:bd09/08/2009:svnDellInc.:pnStudioXPS1340:pvrA11:rvnDellInc.:rn0Y279R:rvrA11:cvnDellInc.:ct8:cvrA11: dmi.product.name: Studio XPS 1340 dmi.product.version: A11 dmi.sys.vendor: Dell Inc. -- cups not starting at boot https://bugs.launchpad.net/bugs/554172 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 215035] Re: Many special keys on Logitech Wave keyboard don't work
Package: udev Priority: important Section: admin Installed-Size: 1540 Maintainer: Scott James Remnant sc...@ubuntu.com Architecture: amd64 Version: 147~-6 Still not having my Window Zoom keys recognized on a Logitech Wave (Corded version) keyboard. Attached are udevadm monitor -e --udev, and udevadm info --export-db ** Attachment added: udevadm monitor -e --udev ; http://launchpadlibrarian.net/36797030/udevadm-e -- Many special keys on Logitech Wave keyboard don't work https://bugs.launchpad.net/bugs/215035 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 215035] Re: Many special keys on Logitech Wave keyboard don't work
** Attachment added: udev db http://launchpadlibrarian.net/36797036/udev-db.txt -- Many special keys on Logitech Wave keyboard don't work https://bugs.launchpad.net/bugs/215035 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 481053] Re: A while after login, mouse and keyboard events go only to a single window
Dug more here, and it's not metacity at fault at all. Reproducion steps: graphical bootup disabled,It also happens in the first GDM login session.If you click a name to start with, then the accessibility button is no longer interactive for clicks for some reason, and vice-versa, if you start by clicking the accessibility options, mouse clicks are afterwards not directed to the name list. Once you log in like this, the events only go to the top panel, no matter what WM I use. Attaching strace to metactiy shows events on the socket (fd/11) during mouse clicks, but no response happens. -- A while after login, mouse and keyboard events go only to a single window https://bugs.launchpad.net/bugs/481053 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 481053] Re: A while after login, mouse and keyboard events go only to a single window
Checked: Compiz bugs out as well, so I'd assume it's in the xorg layer. I I'm fast in getting a terminal open I can manage a compiz --replace or metacity --replace, and it still fails to function properly. Attached is the xorg.log ** Attachment added: Xorg log file http://launchpadlibrarian.net/35743621/xorg.bugged -- A while after login, mouse and keyboard events go only to a single window https://bugs.launchpad.net/bugs/481053 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 481053] Re: A while after login, mouse and keyboard events go only to a single window
Testing for tomorrow morning -- A while after login, mouse and keyboard events go only to a single window https://bugs.launchpad.net/bugs/481053 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 481053] [NEW] A while after login, mouse and keyboard events go only to a single window
Public bug reported: Binary package hint: metacity This has started to crop up recently after fresh boots on my Karmic system. On separate accounts, so it's not a local configruation issue for the user. Logon, start a few programs, and after a while you can no longer alt+tab or change the focused window. If you hit numlock it lights up, you can still switch out of the VT by ctrl+alt+F1 or similar. But no matter what you do in the X session you cannot switch focus to another window. If you start terminals you can launch applications from there ( the panel doesn't respond either, becuase it doesn't get focus) and starting an `xev` gives it focus, but it doesn't register any mouse clicks even when you click the window repeatedly. It does however register keyboard events. however, if you kill gnome-session (thus terminating your login session) and re-login, it suddenly works again and doesn't fark out. This leads me to believe that something is afoul in the original X session that is started, and it is fixed by restarting the X server. However, I cannot prove this hypothesis, so I'm still filing the bug against metacity, because alt tab doesn't work. ProblemType: Bug Architecture: amd64 Date: Thu Nov 12 01:34:04 2009 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: nvidia Package: metacity 1:2.28.0-0ubuntu1 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/zsh ProcVersionSignature: Ubuntu 2.6.31-15.50-generic SourcePackage: metacity Uname: Linux 2.6.31-15-generic x86_64 ** Affects: metacity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug -- A while after login, mouse and keyboard events go only to a single window https://bugs.launchpad.net/bugs/481053 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 481053] Re: A while after login, mouse and keyboard events go only to a single window
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/3562/Dependencies.txt ** Attachment added: XsessionErrors.txt http://launchpadlibrarian.net/3563/XsessionErrors.txt -- A while after login, mouse and keyboard events go only to a single window https://bugs.launchpad.net/bugs/481053 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 272418] Re: openbox/Gnome wont launch from gdm
#29: That is a workaround to use Openbox, it doesn't fix/make openbox a session of it's own, which is what the original report still is about. -- openbox/Gnome wont launch from gdm https://bugs.launchpad.net/bugs/272418 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 379343] Re: screensaver and display powermanagement do not work
Me too but it's on x86_64 rather than i386. Screensaver is set to idle at 1 minute, but doesn't turn on. Power management is set to work on 30 minute, but monitor is still on after a night. Activating it normally with gnome-screensaver-command --activate works, but then it still doesn't turn off the monitor. -- screensaver and display powermanagement do not work https://bugs.launchpad.net/bugs/379343 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 442737] Re: ubuntu-bug mdadm - Fails due to permission denied
** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/33007839/BootDmesg.txt ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/33007840/CurrentDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/33007841/Dependencies.txt ** Attachment added: GrubMenu.lst.txt http://launchpadlibrarian.net/33007842/GrubMenu.lst.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/33007843/Lspci.txt ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/33007844/Lsusb.txt ** Attachment added: MDadmExamine.dev.sda1.txt http://launchpadlibrarian.net/33007845/MDadmExamine.dev.sda1.txt ** Attachment added: MDadmExamine.dev.sdb1.txt http://launchpadlibrarian.net/33007846/MDadmExamine.dev.sdb1.txt ** Attachment added: MDadmExamine.dev.sdc1.txt http://launchpadlibrarian.net/33007847/MDadmExamine.dev.sdc1.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/33007848/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/33007849/ProcInterrupts.txt ** Attachment added: ProcMDstat.txt http://launchpadlibrarian.net/33007850/ProcMDstat.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/33007851/ProcModules.txt ** Attachment added: ProcMounts.txt http://launchpadlibrarian.net/33007852/ProcMounts.txt ** Attachment added: ProcPartitions.txt http://launchpadlibrarian.net/33007853/ProcPartitions.txt ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/33007854/UdevDb.txt ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/33007855/UdevLog.txt ** Attachment added: XsessionErrors.txt http://launchpadlibrarian.net/33007856/XsessionErrors.txt ** Attachment added: etc.blkid.tab.txt http://launchpadlibrarian.net/33007858/etc.blkid.tab.txt ** Attachment added: initrd.files.txt http://launchpadlibrarian.net/33007859/initrd.files.txt ** Attachment added: mdadm.conf.txt http://launchpadlibrarian.net/33007860/mdadm.conf.txt -- ubuntu-bug mdadm - Fails due to permission denied https://bugs.launchpad.net/bugs/442737 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 442737] [NEW] ubuntu-bug mdadm - Fails due to permission denied
Public bug reported: Binary package hint: mdadm When I was reporting : https://bugs.launchpad.net/bugs/442735 I noticed that ubuntu-bug will fail to report what it should because it lacked permission to run mdadm -E on the devices. This clearly makes the debugging less useful and I think it should prompt for a password to generate useful information. ProblemType: Bug Architecture: amd64 Date: Mon Oct 5 03:58:27 2009 DistroRelease: Ubuntu 9.10 MDadmExamine.dev.sda: Error: command ['/sbin/mdadm', '-E', '/dev/sda'] failed with exit code 1: mdadm: No md superblock detected on /dev/sda. MDadmExamine.dev.sdb: Error: command ['/sbin/mdadm', '-E', '/dev/sdb'] failed with exit code 1: mdadm: No md superblock detected on /dev/sdb. MDadmExamine.dev.sdc: Error: command ['/sbin/mdadm', '-E', '/dev/sdc'] failed with exit code 1: mdadm: No md superblock detected on /dev/sdc. MDadmExamine.dev.sdd: Error: command ['/sbin/mdadm', '-E', '/dev/sdd'] failed with exit code 1: mdadm: No md superblock detected on /dev/sdd. MDadmExamine.dev.sdd1: Error: command ['/sbin/mdadm', '-E', '/dev/sdd1'] failed with exit code 1: mdadm: No md superblock detected on /dev/sdd1. MDadmExamine.dev.sdd2: Error: command ['/sbin/mdadm', '-E', '/dev/sdd2'] failed with exit code 1: mdadm: No md superblock detected on /dev/sdd2. MDadmExamine.dev.sdd3: Error: command ['/sbin/mdadm', '-E', '/dev/sdd3'] failed with exit code 1: mdadm: No md superblock detected on /dev/sdd3. MDadmExamine.dev.sdd4: Error: command ['/sbin/mdadm', '-E', '/dev/sdd4'] failed with exit code 1: mdadm: No md superblock detected on /dev/sdd4. MDadmExamine.dev.sdd5: Error: command ['/sbin/mdadm', '-E', '/dev/sdd5'] failed with exit code 1: mdadm: No md superblock detected on /dev/sdd5. MDadmExamine.dev.sdd6: Error: command ['/sbin/mdadm', '-E', '/dev/sdd6'] failed with exit code 1: mdadm: No md superblock detected on /dev/sdd6. MachineType: Gigabyte Technology Co., Ltd. P35-DS4 NonfreeKernelModules: nvidia Package: mdadm 2.6.7.1-1ubuntu13 ProcCmdLine: root=UUID=79dc13f4-cbae-42ee-bb76-a110e8a381d7 ro quiet splash ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/zsh ProcVersionSignature: Ubuntu 2.6.31-11.38-generic SourcePackage: mdadm Uname: Linux 2.6.31-11-generic x86_64 dmi.bios.date: 07/21/2008 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F13 dmi.board.name: P35-DS4 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF13:bd07/21/2008:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS4:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS4:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P35-DS4 dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: mdadm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug -- ubuntu-bug mdadm - Fails due to permission denied https://bugs.launchpad.net/bugs/442737 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 442735] Re: dmraid /mdadm eats mdadm-managed raid in upgrading from 9.04 to 9.10 beta.
** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/33007445/BootDmesg.txt ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/33007446/CurrentDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/33007447/Dependencies.txt ** Attachment added: GrubMenu.lst.txt http://launchpadlibrarian.net/33007448/GrubMenu.lst.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/33007449/Lspci.txt ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/33007451/Lsusb.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/33007453/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/33007454/ProcInterrupts.txt ** Attachment added: ProcMDstat.txt http://launchpadlibrarian.net/33007455/ProcMDstat.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/33007456/ProcModules.txt ** Attachment added: ProcMounts.txt http://launchpadlibrarian.net/33007457/ProcMounts.txt ** Attachment added: ProcPartitions.txt http://launchpadlibrarian.net/33007458/ProcPartitions.txt ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/33007459/UdevDb.txt ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/33007460/UdevLog.txt ** Attachment added: XsessionErrors.txt http://launchpadlibrarian.net/33007461/XsessionErrors.txt ** Attachment added: etc.blkid.tab.txt http://launchpadlibrarian.net/33007462/etc.blkid.tab.txt ** Attachment added: initrd.files.txt http://launchpadlibrarian.net/33007463/initrd.files.txt ** Attachment added: mdadm.conf.txt http://launchpadlibrarian.net/33007465/mdadm.conf.txt -- dmraid /mdadm eats mdadm-managed raid in upgrading from 9.04 to 9.10 beta. https://bugs.launchpad.net/bugs/442735 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 442735] [NEW] dmraid /mdadm eats mdadm-managed raid in upgrading from 9.04 to 9.10 beta.
Public bug reported: Binary package hint: mdadm After rebooting into my newly upgraded 9.10 beta and rebooting a second time my raid was lost. Apperantly dmraid is loaded before mdadm- managed raid, thereby locking /dev/sda1 and others from the raid signature and thereby preventing mdadm from assembling the raid. This leads to massive data loss as dmraid also will erase the superblock/partition table on the devices. In my case the solution is to forcibly remove dmraid and reboot. After that you have to manually kill mountall in a single setup because mountaill will fail and go into a spin where it constantly and incessantly respawns fsck.ext3 (which fails and tells you to restart it without -p or -y ) On top of this the terminal is garbled forcing you to swap to another one. ( seems like a curses based prompt for interaction is overwritten turning the whole thing into garbage) once mountall is killed and all fsck-jobs pruned, you can re-create the partition tables on the lost disk, and set the type to Linux Raid Autodetect. Then you can once again do mdadm --assemble /dev/md0 /dev/sd[a-c]1 and wait for 24+ hours. Then you can fsck and hope that Ubuntu won't eat your raid again. This is -clearly- suboptimal, caused me a lot of grief and panic. On top of that the ubuntu-bug tool for mdadm doesn't stop to ask you for a password but happily tries to run mdadm -E on devices without permission to read them, generating what appears to be a bogus report. ProblemType: Bug Architecture: amd64 Date: Mon Oct 5 03:53:24 2009 DistroRelease: Ubuntu 9.10 MDadmExamine.dev.sda: Error: command ['/sbin/mdadm', '-E', '/dev/sda'] failed with exit code 1: mdadm: cannot open /dev/sda: Permission denied MDadmExamine.dev.sda1: Error: command ['/sbin/mdadm', '-E', '/dev/sda1'] failed with exit code 1: mdadm: cannot open /dev/sda1: Permission denied MDadmExamine.dev.sdb: Error: command ['/sbin/mdadm', '-E', '/dev/sdb'] failed with exit code 1: mdadm: cannot open /dev/sdb: Permission denied MDadmExamine.dev.sdb1: Error: command ['/sbin/mdadm', '-E', '/dev/sdb1'] failed with exit code 1: mdadm: cannot open /dev/sdb1: Permission denied MDadmExamine.dev.sdc: Error: command ['/sbin/mdadm', '-E', '/dev/sdc'] failed with exit code 1: mdadm: cannot open /dev/sdc: Permission denied MDadmExamine.dev.sdc1: Error: command ['/sbin/mdadm', '-E', '/dev/sdc1'] failed with exit code 1: mdadm: cannot open /dev/sdc1: Permission denied MDadmExamine.dev.sdd: Error: command ['/sbin/mdadm', '-E', '/dev/sdd'] failed with exit code 1: mdadm: cannot open /dev/sdd: Permission denied MDadmExamine.dev.sdd1: Error: command ['/sbin/mdadm', '-E', '/dev/sdd1'] failed with exit code 1: mdadm: cannot open /dev/sdd1: Permission denied MDadmExamine.dev.sdd2: Error: command ['/sbin/mdadm', '-E', '/dev/sdd2'] failed with exit code 1: mdadm: cannot open /dev/sdd2: Permission denied MDadmExamine.dev.sdd3: Error: command ['/sbin/mdadm', '-E', '/dev/sdd3'] failed with exit code 1: mdadm: cannot open /dev/sdd3: Permission denied MDadmExamine.dev.sdd4: Error: command ['/sbin/mdadm', '-E', '/dev/sdd4'] failed with exit code 1: mdadm: cannot open /dev/sdd4: Permission denied MDadmExamine.dev.sdd5: Error: command ['/sbin/mdadm', '-E', '/dev/sdd5'] failed with exit code 1: mdadm: cannot open /dev/sdd5: Permission denied MDadmExamine.dev.sdd6: Error: command ['/sbin/mdadm', '-E', '/dev/sdd6'] failed with exit code 1: mdadm: cannot open /dev/sdd6: Permission denied MachineType: Gigabyte Technology Co., Ltd. P35-DS4 NonfreeKernelModules: nvidia Package: mdadm 2.6.7.1-1ubuntu13 ProcCmdLine: root=UUID=79dc13f4-cbae-42ee-bb76-a110e8a381d7 ro quiet splash ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/zsh ProcVersionSignature: Ubuntu 2.6.31-11.38-generic SourcePackage: mdadm Uname: Linux 2.6.31-11-generic x86_64 dmi.bios.date: 07/21/2008 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F13 dmi.board.name: P35-DS4 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF13:bd07/21/2008:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS4:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS4:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P35-DS4 dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: mdadm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug -- dmraid /mdadm eats mdadm-managed raid in upgrading from 9.04 to 9.10 beta. https://bugs.launchpad.net/bugs/442735 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 442735] Re: dmraid /mdadm eats mdadm-managed raid in upgrading from 9.04 to 9.10 beta.
Please see : https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/442737 proper logs generated with admin privileges. -- dmraid /mdadm eats mdadm-managed raid in upgrading from 9.04 to 9.10 beta. https://bugs.launchpad.net/bugs/442735 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 442735] Re: dmraid /mdadm eats mdadm-managed raid in upgrading from 9.04 to 9.10 beta.
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/414251 appears related. -- dmraid /mdadm eats mdadm-managed raid in upgrading from 9.04 to 9.10 beta. https://bugs.launchpad.net/bugs/442735 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 442735] Re: dmraid /mdadm eats mdadm-managed raid in upgrading from 9.04 to 9.10 beta.
Further information: I'm not using the raid function on the mainboard, in fact it is explicitly disabled in bootup because it was being a hassle even in windows. I believe the main problem is: a) loadtime ordering mdadm vs. dmraid. mdadm -REALLY- should be allowed to scan and load the drives before dmraid is even close to my kernel's space. b) clobbering by dmraid on failed load. The fact that it wiped my partition table on a disk was unforgivable. c) bootup scripts failing on things like this and falling into semi-endless loops/spins without functional recovery.I realise this kind of failure isn't easy to generate in virtual hardware, but failure modes need to be tested more and functional. Having a GDM load on top of the endless loop of fsck's was even more damaging because I wasn't let in on the fact that something was seriously wrong. -- dmraid /mdadm eats mdadm-managed raid in upgrading from 9.04 to 9.10 beta. https://bugs.launchpad.net/bugs/442735 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 442735] Re: dmraid /mdadm eats mdadm-managed raid in upgrading from 9.04 to 9.10 beta.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=534274 Seems like another similarity here. ** Bug watch added: Debian Bug tracker #534274 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=534274 -- dmraid /mdadm eats mdadm-managed raid in upgrading from 9.04 to 9.10 beta. https://bugs.launchpad.net/bugs/442735 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 333718] Re: Liferea takes approx 2 seconds to act from pressing next to displaying anything but white.
*** This bug is a duplicate of bug 290666 *** https://bugs.launchpad.net/bugs/290666 Easiest way is to simply run a profiler on it and see ( oprofile works ) Not sure how well implemented the support for it is in Ubuntu as I have Gentoo-based systems for development rather. -- Liferea takes approx 2 seconds to act from pressing next to displaying anything but white. https://bugs.launchpad.net/bugs/333718 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 333718] Re: Liferea takes approx 2 seconds to act from pressing next to displaying anything but white.
*** This bug is a duplicate of bug 290666 *** https://bugs.launchpad.net/bugs/290666 The fix he does is basically turning liferea into a bit more fragile. What it does is turn the fsync() call into a no-op (no operation) , basically making it do nothing. On Linux, a call to fsync will in general (ext3/4, jfs) flush all applications unwritten data to disk, causing a momentary stall as it waits to return from this. Basically the slowdown you see is the program repeatedly (far too often, several times per second) asking for it's data to be written to disk, and waiting around for the system to make sure that it's there. For something like liferea that's completely bogus behaviour. -- Liferea takes approx 2 seconds to act from pressing next to displaying anything but white. https://bugs.launchpad.net/bugs/333718 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 367321] [NEW] Kernel issues after suspend
Public bug reported: Reports of Low memory corruption after suspend. System otherwise appears functional.. ProblemType: KernelOops Annotation: Your system might become unstable now and might need to be restarted. Architecture: amd64 DistroRelease: Ubuntu 9.04 Failure: oops HibernationDevice: RESUME=UUID=b96a985a-f4ec-4492-a26e-01a41b4eed0d MachineType: Gigabyte Technology Co., Ltd. P35-DS4 NonfreeKernelModules: nvidia Package: linux-image-2.6.28-11-generic 2.6.28-11.42 ProcCmdLine: root=UUID=79dc13f4-cbae-42ee-bb76-a110e8a381d7 ro quiet splash ProcVersionSignature: Ubuntu 2.6.28-11.42-generic SourcePackage: linux Tags: kernel-oops Title: [142019.819543] [ cut here ] ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-kerneloops kernel-oops -- Kernel issues after suspend https://bugs.launchpad.net/bugs/367321 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 367321] Re: Kernel issues after suspend
** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/25996478/BootDmesg.txt ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/25996479/CurrentDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/25996480/Dependencies.txt ** Attachment added: HalComputerInfo.txt http://launchpadlibrarian.net/25996481/HalComputerInfo.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/25996483/Lspci.txt ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/25996484/Lsusb.txt ** Attachment added: OopsText.txt http://launchpadlibrarian.net/25996485/OopsText.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/25996486/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/25996488/ProcInterrupts.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/25996489/ProcModules.txt -- Kernel issues after suspend https://bugs.launchpad.net/bugs/367321 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 363306] [NEW] Kernel issues after suspend
Public bug reported: I do not know if It's related to nvidia or not, but it happens all the time I suspend. Gigabyte mainboard (GA-P35-DS4) I've ran both memtest86+ for quite a few cycles (no errors) and a combination of memtester+cpuburn without issues (Cooling seems quite up to the task) so I'm led to conclude it's not a hardware issue. ProblemType: KernelOops Annotation: Your system might become unstable now and might need to be restarted. Architecture: amd64 DistroRelease: Ubuntu 9.04 Failure: oops MachineType: Gigabyte Technology Co., Ltd. P35-DS4 NonfreeKernelModules: nvidia Package: linux-image-2.6.28-11-generic 2.6.28-11.41 ProcCmdLine: root=UUID=79dc13f4-cbae-42ee-bb76-a110e8a381d7 ro quiet splash ProcVersionSignature: Ubuntu 2.6.28-11.41-generic SourcePackage: linux Tags: kernel-oops Title: [145199.816033] [ cut here ] ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-kerneloops kernel-oops -- Kernel issues after suspend https://bugs.launchpad.net/bugs/363306 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 363306] Re: Kernel issues after suspend
** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/25697977/BootDmesg.txt ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/25697978/CurrentDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/25697979/Dependencies.txt ** Attachment added: HalComputerInfo.txt http://launchpadlibrarian.net/25697980/HalComputerInfo.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/25697981/Lspci.txt ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/25697982/Lsusb.txt ** Attachment added: OopsText.txt http://launchpadlibrarian.net/25697983/OopsText.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/25697984/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/25697985/ProcInterrupts.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/25697986/ProcModules.txt -- Kernel issues after suspend https://bugs.launchpad.net/bugs/363306 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 363336] [NEW] [145199.816036] WARNING: at /build/buildd/linux-2.6.28/arch/x86/kernel/setup.c:719 check_for_bios_corruption+0xdd/0xe0()
Public bug reported: Gigabyte GA-P35-DS4 Mainboard + Intel Core2 Duo CPU, Nvidia binary drivers and this is the result after a suspend/resume cycle ProblemType: KernelOops Annotation: Your system might become unstable now and might need to be restarted. Architecture: amd64 DistroRelease: Ubuntu 9.04 Failure: oops MachineType: Gigabyte Technology Co., Ltd. P35-DS4 NonfreeKernelModules: nvidia Package: linux-image-2.6.28-11-generic 2.6.28-11.41 ProcCmdLine: root=UUID=79dc13f4-cbae-42ee-bb76-a110e8a381d7 ro quiet splash ProcVersionSignature: Ubuntu 2.6.28-11.41-generic SourcePackage: linux Tags: kernel-oops Title: [145199.816036] WARNING: at /build/buildd/linux-2.6.28/arch/x86/kernel/setup.c:719 check_for_bios_corruption+0xdd/0xe0() ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-kerneloops kernel-oops -- [145199.816036] WARNING: at /build/buildd/linux-2.6.28/arch/x86/kernel/setup.c:719 check_for_bios_corruption+0xdd/0xe0() https://bugs.launchpad.net/bugs/363336 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 363336] Re: [145199.816036] WARNING: at /build/buildd/linux-2.6.28/arch/x86/kernel/setup.c:719 check_for_bios_corruption+0xdd/0xe0()
** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/25699683/BootDmesg.txt ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/25699684/CurrentDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/25699685/Dependencies.txt ** Attachment added: HalComputerInfo.txt http://launchpadlibrarian.net/25699686/HalComputerInfo.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/25699687/Lspci.txt ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/25699688/Lsusb.txt ** Attachment added: OopsText.txt http://launchpadlibrarian.net/25699689/OopsText.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/25699690/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/25699691/ProcInterrupts.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/25699692/ProcModules.txt -- [145199.816036] WARNING: at /build/buildd/linux-2.6.28/arch/x86/kernel/setup.c:719 check_for_bios_corruption+0xdd/0xe0() https://bugs.launchpad.net/bugs/363336 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 363353] [NEW] Suspend/Resume error: report after a fresh shutdown/bootup cycle
Public bug reported: Gigabyte P35-DS4 mainboard. I suspect that this is an issue of a bug in Apport rather. Since the bug doesn't appear in the current dmesg, only in the old kernel logs. And that it has probably already reported it. ProblemType: KernelOops Annotation: Your system might become unstable now and might need to be restarted. Architecture: amd64 CurrentDmesg: [ 26.573346] r8169: eth0: link up [ 26.573353] r8169: eth0: link up [ 37.136025] eth0: no IPv6 routers present DistroRelease: Ubuntu 9.04 Failure: oops MachineType: Gigabyte Technology Co., Ltd. P35-DS4 NonfreeKernelModules: nvidia Package: linux-image-2.6.28-11-generic 2.6.28-11.41 ProcCmdLine: root=UUID=79dc13f4-cbae-42ee-bb76-a110e8a381d7 ro quiet splash ProcVersionSignature: Ubuntu 2.6.28-11.41-generic SourcePackage: linux Tags: kernel-oops Title: [145167.500400] [ cut here ] ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-kerneloops kernel-oops -- Suspend/Resume error: report after a fresh shutdown/bootup cycle https://bugs.launchpad.net/bugs/363353 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 363353] Re: Suspend/Resume error: report after a fresh shutdown/bootup cycle
** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/25700729/BootDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/25700730/Dependencies.txt ** Attachment added: HalComputerInfo.txt http://launchpadlibrarian.net/25700731/HalComputerInfo.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/25700733/Lspci.txt ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/25700734/Lsusb.txt ** Attachment added: OopsText.txt http://launchpadlibrarian.net/25700735/OopsText.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/25700736/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/25700737/ProcInterrupts.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/25700738/ProcModules.txt -- Suspend/Resume error: report after a fresh shutdown/bootup cycle https://bugs.launchpad.net/bugs/363353 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 333718] Re: Liferea takes approx 2 seconds to act from pressing next to displaying anything but white.
Here's another gui-debug log output that shows some interesting behaviours: Otherwise unloaded system ( an idle browser with a blank page, a music player and IM client running at the same time. Virtually nothing) GUI: reloading item list with node grinding.be GUI: itemlist merge took 0,033s GUI: item list selection changed to How six people in Moldova possibly saved an election GUI: set read status took 1,912s GUI: itemlist selection took 1,958s GUI: Fatal: no node with id ttmgyjx found! GUI: feed list selection changed to BB: Gadgets GUI: new selected node: BB: Gadgets GUI: loading item list with node BB: Gadgets GUI: Setting item list visibility mode: 0 GUI: reloading item list with node BB: Gadgets GUI: itemlist merge took 0,052s GUI: item list selection changed to Gizmodo mounted on maple blocks, sounds great GUI: set read status took 1,748s GUI: itemlist selection took 2,650s GUI: item list selection changed to Stealthy Ninja Jacket is Magical* GUI: set read status took 1,757s GUI: itemlist selection took 1,765s GUI: item list selection changed to The White Stripes reimagine two classic toy cameras into collector's items GUI: set read status took 1,353s GUI: itemlist selection took 1,362s GUI: item list selection changed to FamilyMap: Track your family using the same technology the government is using to track them GUI: set read status took 1,916s GUI: itemlist selection took 1,925s GUI: item list selection changed to Time Travel Cheatsheat GUI: set read status took 1,638s GUI: itemlist selection took 2,463s GUI: item list selection changed to CycleKarting, hand-built vintage race cars GUI: set read status took 1,916s GUI: itemlist selection took 1,925s GUI: item list selection changed to Gator Guard is a scareduck GUI: set read status took 1,435s GUI: itemlist selection took 1,443s GUI: item list selection changed to Today on Offworld GUI: set read status took 1,343s GUI: itemlist selection took 1,351s GUI: feed list selection changed to Planets GUI: new selected node: Planets GUI: loading item list with node Planets GUI: feed list selection changed to ..GNOME GUI: new selected node: ..GNOME GUI: loading item list with node ..GNOME GUI: Setting item list visibility mode: 0 GUI: reloading item list with node ..GNOME GUI: itemlist merge took 0,048s GUI: item list selection changed to (null) GUI: set read status took 1,411s GUI: itemlist selection took 1,449s GUI: feed list selection changed to ..Ubuntu GUI: new selected node: ..Ubuntu GUI: loading item list with node ..Ubuntu GUI: Setting item list visibility mode: 0 GUI: reloading item list with node ..Ubuntu GUI: itemlist merge took 0,039s GUI: item list selection changed to Guy Van Sanden: Controverses about Jaunty's new notification system GUI: set read status took 0,568s GUI: itemlist selection took 0,612s GUI: item list selection changed to Launchpad News: Karma — where did mine go? GUI: set read status took 0,556s GUI: itemlist selection took 0,565s GUI: item list selection changed to Thierry Carrez: How to find Java classes in the distribution GUI: set read status took 0,579s GUI: itemlist selection took 0,587s -- Liferea takes approx 2 seconds to act from pressing next to displaying anything but white. https://bugs.launchpad.net/bugs/333718 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 337294] Re: rhythmbox crashed with SIGSEGV in start_thread()
No, can't seem to reproduce it anymore. Good to close this. -- rhythmbox crashed with SIGSEGV in start_thread() https://bugs.launchpad.net/bugs/337294 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 333718] Re: Liferea takes approx 2 seconds to act from pressing next to displaying anything but white.
GUI: feed list selection changed to Slashdot GUI: new selected node: Slashdot GUI: loading item list with node Slashdot GUI: Setting item list visibility mode: 0 GUI: reloading item list with node Slashdot GUI: itemlist merge took 0,019s GUI: item list selection changed to Vista Post-SP2 Is the Safest OS On the Planet GUI: set read status took 0,611s GUI: itemlist selection took 0,647s GUI: item list selection changed to Android 1.5 SDK Is Released GUI: set read status took 0,531s GUI: itemlist selection took 0,540s GUI: item list selection changed to College Police Think Using Linux Is Suspicious Behavior GUI: set read status took 0,548s GUI: itemlist selection took 0,557s GUI: item list selection changed to NASA Taking Ethernet Into Deeper Space GUI: set read status took 0,587s GUI: itemlist selection took 0,596s GUI: item list selection changed to Microsoft Won't Vouch For Linux GUI: set read status took 0,741s GUI: itemlist selection took 0,750s --debug-gui shows some interesting things. -- Liferea takes approx 2 seconds to act from pressing next to displaying anything but white. https://bugs.launchpad.net/bugs/333718 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 333718] Re: Liferea takes approx 2 seconds to act from pressing next to displaying anything but white.
Hardware, Core2 duo ( clocked at 2.4GHz) with 6GB RAM, system on a sata-II disk. from this vmstat 1 log it's fairly obvious where I hit the load all button, but that's not a terribly high load either. if I run liferea with the --debug-all flag The whole thing slows down so much that it's hard to notice what would be the cause based on the output. procs ---memory-- ---swap-- -io -system-- cpu r b swpd free buff cache si sobibo in cs us sy id wa 1 0 0 2457988 171952 2628984006518 940 666 37 3 58 1 0 0 0 2457972 171952 262898400 0 0 113 105 0 0 100 0 0 0 0 2457972 171952 262898400 0 0 144 166 0 0 100 0 0 0 0 2457972 171952 262898400 0 0 220 1018 1 0 99 0 0 0 0 2457972 171956 262898000 056 233 1468 3 0 97 1 0 0 0 2457972 171956 262898400 0 0 118 122 1 0 99 0 0 0 0 2457972 171956 262898400 0 0 132 149 0 0 100 0 0 0 0 2457972 171956 262898400 0 0 202 1330 0 0 100 0 0 1 0 2457972 172024 262893200 0 540 476 837 0 0 69 30 2 1 0 2457972 172112 262892800 0 708 482 867 0 1 59 40 0 1 0 2457772 172220 262890000 0 632 441 431 1 0 61 39 0 1 0 2457624 172272 262895600 0 700 446 382 1 0 63 36 0 0 0 2457600 172384 262890400 0 700 543 922 0 1 52 47 0 1 0 2457600 172524 262888000 0 752 436 409 0 0 64 35 0 1 0 2457400 172640 262889600 0 684 471 506 0 1 63 35 0 1 0 2457352 172788 262887600 0 704 419 406 0 1 67 33 0 1 0 2457104 172932 26200 0 680 394 405 0 1 61 37 0 1 0 2456980 173092 262884800 0 684 466 412 1 0 61 37 0 1 0 2456756 173244 262888000 0 680 428 427 0 0 55 44 0 1 0 2456532 173384 262889600 0 692 429 387 0 0 65 35 0 1 0 2456484 173508 262889200 0 596 421 538 2 0 58 40 procs ---memory-- ---swap-- -io -system-- cpu r b swpd free buff cache si sobibo in cs us sy id wa 1 1 0 2456384 173636 262889600 0 640 376 332 1 1 60 39 0 1 0 2456236 173744 262891600 0 692 457 437 0 0 71 28 0 1 0 2456036 173868 262887600 0 688 488 13070 2 2 60 36 0 0 0 2455772 174000 262890400 0 624 641 3986 2 0 56 42 0 0 0 2455500 174056 26289520016 264 550 1570 15 2 70 13 2 0 0 2455500 174056 262900000 0 0 294 887 0 0 99 0 0 1 0 2455500 174092 262896400 0 232 388 951 2 0 91 8 1 0 0 2439700 174216 264431600 8 796 573 555 15 1 45 38 0 0 0 2455344 174216 262900800 0 16004 235 190 1 1 99 0 0 1 0 2455360 174252 262897200 0 240 334 367 1 0 91 8 0 0 0 2455360 174296 26290160012 252 260 289 1 1 86 13 0 1 0 2455160 174300 262901600 0 124 355 389 2 0 93 4 0 1 0 2454988 174436 262892400 0 772 371 351 1 0 62 38 0 0 0 2454588 174500 262900400 8 436 436 1060 2 0 72 26 3 0 0 2454556 174500 262907600 0 0 293 1970 10 0 90 0 -- Liferea takes approx 2 seconds to act from pressing next to displaying anything but white. https://bugs.launchpad.net/bugs/333718 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 333718] Re: Liferea takes approx 2 seconds to act from pressing next to displaying anything but white.
And here we get to the behaviour issues that I'm bothered by : GUI: feed list selection changed to ..GStreamer GUI: new selected node: ..GStreamer GUI: loading item list with node ..GStreamer GUI: Setting item list visibility mode: 0 GUI: reloading item list with node ..GStreamer GUI: itemlist merge took 0,025s GUI: item list selection changed to Web (Django) Developer opportunity GUI: set read status took 0,997s GUI: itemlist selection took 1,005s GUI: item list selection changed to Music GUI: set read status took 1,719s GUI: set read status took 2,322s GUI: set read status took 3,930s GUI: itemlist selection took 6,609s Otherwise unloaded system -- Liferea takes approx 2 seconds to act from pressing next to displaying anything but white. https://bugs.launchpad.net/bugs/333718 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 348672] Re: WARNING: at /build/buildd/linux-2.6.28/kernel/power/main.c:177 suspend_test_finish+0x80/0x90()
@Andres: Tested it recently and it checks out clear, which is why I'm a bit bummered and out of things to try right now. -- WARNING: at /build/buildd/linux-2.6.28/kernel/power/main.c:177 suspend_test_finish+0x80/0x90() https://bugs.launchpad.net/bugs/348672 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 348672] Re: WARNING: at /build/buildd/linux-2.6.28/kernel/power/main.c:177 suspend_test_finish+0x80/0x90()
Another Gigabyte mainboard here, but an Intel CPU, same issue I think. ** Attachment added: kern.log http://launchpadlibrarian.net/25284160/kern.log -- WARNING: at /build/buildd/linux-2.6.28/kernel/power/main.c:177 suspend_test_finish+0x80/0x90() https://bugs.launchpad.net/bugs/348672 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 333718] Re: Liferea takes approx 2 seconds to act from pressing next to displaying anything but white.
That still happens in the current version, also there's a HUGE lockup- like wait if you hit reload all feeds on this machine. It basically stands still for about a minute ( Metacity thinks it has hanged and will offer to force it to close for you) As for me, I have ~90 active feeds that I follow, to give an impression on the scale of things where I see a horrible slowdown. -- Liferea takes approx 2 seconds to act from pressing next to displaying anything but white. https://bugs.launchpad.net/bugs/333718 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 330814] Re: snd_pcm_avail_update() returning absurd values causes PulseAudio to abort
I: module-alsa-sink.c: Underrun! D: protocol-native.c: Requesting rewind due to end of underrun. I: module-alsa-sink.c: Underrun! D: protocol-native.c: Requesting rewind due to end of underrun. I: module-alsa-sink.c: Underrun! D: protocol-native.c: Requesting rewind due to end of underrun. I: module-alsa-sink.c: Underrun! D: protocol-native.c: Requesting rewind due to end of underrun. Still getting nasty glitches in my sound and underruns ( running pulseaudio -k; pulseaudio -v --log-target=stderr --log-level=debug -C ) 2-4 times per minute, makes it a rather unpleasant experience to listen to music Waves% apt-cache policy pulseaudio pulseaudio: Installed: 0.9.14-0ubuntu15 Candidate: 0.9.14-0ubuntu15 Version table: *** 0.9.14-0ubuntu15 0 500 http://se.archive.ubuntu.com jaunty/main Packages 100 /var/lib/dpkg/status Waves% apt-cache policy linux-image-2.6.28-11-generic linux-image-2.6.28-11-generic: Installed: 2.6.28-11.38 Candidate: 2.6.28-11.38 Version table: *** 2.6.28-11.38 0 500 http://se.archive.ubuntu.com jaunty/main Packages 100 /var/lib/dpkg/status -- snd_pcm_avail_update() returning absurd values causes PulseAudio to abort https://bugs.launchpad.net/bugs/330814 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 189192] Re: gdmsetup dialog is to big for 1024 x 768 resolution
Still an issue with the current version of Jaunty, (9.04, beta release) on a netbook (1024x768) with the jaunty netbook remix. This version also released with window clamping enabled, so I can not move the window above the top of the screen, it is thus impossible to correctly click the buttons in gdmsetup. -- gdmsetup dialog is to big for 1024 x 768 resolution https://bugs.launchpad.net/bugs/189192 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 330814] Re: snd_pcm_avail_update() returning absurd values causes PulseAudio to abort
Okay. Can someone provide a way to cherry-pick the alsa/hda ones that haven't made it upstream yet? I need a couple of thing from vanilla .29 ( No journal ext4 at least) and would like to try it out with functioning sound. -- snd_pcm_avail_update() returning absurd values causes PulseAudio to abort https://bugs.launchpad.net/bugs/330814 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 345770] Re: notify-osd crashed with SIGSEGV in ___fprintf_chk()
Waves% ls -alh ~/.cache/notify-osd.log -rw-r--r-- 1 root root 193 2009-03-20 03:02 /home/spider/.cache/notify-osd.log Now why it's owned by root, I do not know -- notify-osd crashed with SIGSEGV in ___fprintf_chk() https://bugs.launchpad.net/bugs/345770 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 345770] Re: notify-osd crashed with SIGSEGV in ___fprintf_chk()
removing it and hoping that this goes away. -- notify-osd crashed with SIGSEGV in ___fprintf_chk() https://bugs.launchpad.net/bugs/345770 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 349236] [NEW] Installer: choosing Swedish keyboard layout gives an OS that has English keyboard layout.
Public bug reported: Maybe this is #340308, maybe not: When I chose the installer (from USB stick) and select a keymap, it is forgotten as per #340308 when you get into the installer. This is annoying, but not fatal. However, when you correct the keyboard settings after selecting language, You _STILL_ get the main OS install, past reboot, with the wrong keyboard layout. Worse yet, the Gnome keyboard selector configuration for keyboard layouts is funky and doesn't work properly. The only way to make it register the proper keyboard layout is to add it, Select it. Then _remove_ English. In the end, this is a pita to work with. Hopefully this can be fixed now that the beta is out? ** Affects: ubuntu Importance: Undecided Status: New -- Installer: choosing Swedish keyboard layout gives an OS that has English keyboard layout. https://bugs.launchpad.net/bugs/349236 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 344057] Re: cpulimit.c: Received request to terminate due to CPU overload.
the CPU overload still happens here: grep CPU /var/log/user.log Mar 20 09:11:32 Waves pulseaudio[4586]: cpulimit.c: Received request to terminate due to CPU overload. Mar 20 09:11:43 Waves pulseaudio[6137]: cpulimit.c: Received request to terminate due to CPU overload. Mar 20 09:12:25 Waves pulseaudio[6232]: cpulimit.c: Received request to terminate due to CPU overload. Mar 20 09:56:51 Waves pulseaudio[6244]: cpulimit.c: Received request to terminate due to CPU overload. That was after all updates pulseaudio: Installed: 0.9.14-0ubuntu14 Candidate: 0.9.14-0ubuntu14 Version table: *** 0.9.14-0ubuntu14 0 500 http://se.archive.ubuntu.com jaunty/main Packages 100 /var/lib/dpkg/status uname -a Linux Waves 2.6.28-11-generic #35-Ubuntu SMP Wed Mar 18 21:55:34 UTC 2009 x86_64 GNU/Linux -- cpulimit.c: Received request to terminate due to CPU overload. https://bugs.launchpad.net/bugs/344057 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 344057] Re: cpulimit.c: Received request to terminate due to CPU overload.
Please see https://lists.ubuntu.com/archives/ubuntu-devel-discuss/2009-March/007501.html Installed it and will do further testing with it. -- cpulimit.c: Received request to terminate due to CPU overload. https://bugs.launchpad.net/bugs/344057 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 344112] [NEW] pulseaudio 0.9.14-0ubuntu12 still bugs on snd-hda-intel
Public bug reported: Binary package hint: pulseaudio Glitching playback this morning after a fresh boot of the computer, digging through the logs showed me this in /var/log/user.log : Mar 17 00:21:55 Waves bonobo-activation-server (spider-18074): could not associate with desktop session: Failed to connect to socket /tmp/dbus-FG87h0eKsk: Connection refuse d Mar 17 08:35:21 Waves pulseaudio[4360]: cpulimit.c: Received request to terminat e due to CPU overload. Mar 17 08:35:22 Waves pulseaudio[4670]: main.c: Called SUID root and real-time and/or high-priority scheduling was requested in the configuration. However, we lack the necessary privileges: Mar 17 08:35:22 Waves pulseaudio[4670]: main.c: We are not in group 'pulse-rt', PolicyKit refuse to grant us the requested privileges and we have no increase RLIMIT_NICE/RLIMIT_RTPRIO resource limits. Mar 17 08:35:22 Waves pulseaudio[4670]: main.c: For enabling real-time/high-priority scheduling please acquire the appropriate PolicyKit privileges, or become a member of 'pulse-rt', or increase the RLIMIT_NICE/RLIMIT_RTPRIO resource limits for this user. Mar 17 09:14:46 Waves pulseaudio[4673]: cpulimit.c: Received request to terminate due to CPU overload. Mar 17 09:14:46 Waves pulseaudio[6546]: main.c: Called SUID root and real-time and/or high-priority scheduling was requested in the configuration. However, we lack the necessary privileges: Mar 17 09:14:46 Waves pulseaudio[6546]: main.c: We are not in group 'pulse-rt', PolicyKit refuse to grant us the requested privileges and we have no increase RLIMIT_NICE/RLIMIT_RTPRIO resource limits. Mar 17 09:14:46 Waves pulseaudio[6546]: main.c: For enabling real-time/high-priority scheduling please acquire the appropriate PolicyKit privileges, or become a member of 'pulse-rt', or increase the RLIMIT_NICE/RLIMIT_RTPRIO resource limits for this user. Jaunty bug, yes This is probably related to the myriad of other bugs with pulseaudio here. At the times I was running a browser (random flash) and rhythmbox (mp3's playing) Waves% apt-cache policy pulseaudio pulseaudio: Installed: 0.9.14-0ubuntu12 Candidate: 0.9.14-0ubuntu13 Version table: 0.9.14-0ubuntu13 0 500 http://se.archive.ubuntu.com jaunty/main Packages *** 0.9.14-0ubuntu12 0 100 /var/lib/dpkg/status linux-image-2.6.28-9-generic: Installed: 2.6.28-9.31 Candidate: 2.6.28-9.31 Version table: *** 2.6.28-9.31 0 500 http://se.archive.ubuntu.com jaunty/main Packages 100 /var/lib/dpkg/status alsa-info output http://www.alsa-project.org/db/?f=e1b27086b7eecc059ea8ea45153dd39a82421d69 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- pulseaudio 0.9.14-0ubuntu12 still bugs on snd-hda-intel https://bugs.launchpad.net/bugs/344112 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 320875] Re: pulseaudio produces lots of log messages
Why thanks to the dupe, but my bug was revolving about the fact that pulseaudio doesn't do any kind of limiting on its output and will gladly DoS a system in an error-condition by attempting to flood the disk (since it cannot reach CPU quota due to the syslog eating just as much) -- pulseaudio produces lots of log messages https://bugs.launchpad.net/bugs/320875 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 337294] Re: rhythmbox crashed with SIGSEGV in start_thread()
Thought I did, *sigh* Repeatable quite often, simply by playing an album to the end. Reinstalling debug symbols and I'll see once more. Do I have to file a new report for apport to automatically updload stacktrace, or will it attach the new traces if I add to this? -- rhythmbox crashed with SIGSEGV in start_thread() https://bugs.launchpad.net/bugs/337294 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 337294] Re: rhythmbox crashed with SIGSEGV in start_thread()
(gdb) bt full #0 0x7f6228d8a610 in ?? () No symbol table info available. #1 0x7f624a67c459 in start_thread () from /lib/libpthread.so.0 No symbol table info available. #2 0x7f624317dfcd in clone () from /lib/libc.so.6 No symbol table info available. #3 0x in ?? () No symbol table info available. (gdb) info registers rax0x7f6228d8a610 140059568809488 rbx0xb0 176 rcx0x3 3 rdx0x30 48 rsi0x7f622c898950 140059630733648 rdi0x24effe038731744 rbp0x7f624a88c330 0x7f624a88c330 rsp0x7f622c898008 0x7f622c898008 r8 0x251b19038908304 r9 0x1 1 r100x3a98 15000 r110x7f6243112200 140060008718848 r120x7f622c898a20 140059630733856 r130x0 0 r140x7f624a88c280 140060133999232 r150x0 0 rip0x7f6228d8a610 0x7f6228d8a610 eflags 0x10202 [ IF RF ] cs 0x33 51 ss 0x2b 43 ds 0x0 0 es 0x0 0 fs 0x0 0 ---Type return to continue, or q return to quit--- gs 0x0 0 fctrl 0x37f895 fstat 0x20 32 ftag 0x 65535 fiseg 0x7f62 32610 fioff 0x45e6e047 1172758599 foseg 0x7f62 32610 fooff 0x2c8967c8 747202504 fop0x51f1311 mxcsr 0x1fa4 [ ZE PE IM DM ZM OM UM PM ] (gdb) thread apply all backtrace Thread 9 (Thread 0x7f622c898950 (LWP 23552)): #0 0x7f6228d8a610 in ?? () #1 0x7f624a67c459 in start_thread () from /lib/libpthread.so.0 #2 0x7f624317dfcd in clone () from /lib/libc.so.6 #3 0x in ?? () Thread 7 (Thread 0x7f622d099950 (LWP 23550)): #0 0x7f624a6802e9 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #1 0x7f6243a8a67c in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f6243a8aa32 in g_async_queue_pop () from /usr/lib/libglib-2.0.so.0 #3 0x7f624af89255 in action_thread_main (db=0x2978140) at rhythmdb.c:2865 #4 0x7f6243ad7c74 in ?? () from /usr/lib/libglib-2.0.so.0 #5 0x7f624a67c3ba in start_thread () from /lib/libpthread.so.0 #6 0x7f624317dfcd in clone () from /lib/libc.so.6 #7 0x in ?? () Thread 1 (Thread 0x7f624b3b1800 (LWP 23541)): #0 0x7f6243174496 in poll () from /lib/libc.so.6 #1 0x7f6243ab170f in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f6243ab1d3d in g_main_loop_run () from /usr/lib/libglib-2.0.so.0 #3 0x7f6246b32937 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0 #4 0x00422e41 in main (argc=value optimized out, argv=value optimized out) at main.c:330 #0 0x7f6228d8a610 in ?? () Erm.. or maybe rhythmbox-dbg and rhythmbox-dbgsym aren't the same and the package repo is... Annoying? -- rhythmbox crashed with SIGSEGV in start_thread() https://bugs.launchpad.net/bugs/337294 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 337294] Re: rhythmbox crashed with SIGSEGV in start_thread()
again with rhythmbox-dbgsym and glib's debug symbols: (gdb) bt full #0 0x7fca01f76610 in ?? () No symbol table info available. #1 0x7fca23861459 in start_thread () from /lib/libpthread.so.0 No symbol table info available. #2 0x7fca1c362fcd in clone () from /lib/libc.so.6 No symbol table info available. #3 0x in ?? () No symbol table info available. (gdb) thread apply all backtrace Thread 36 (Thread 0x7fca1059f950 (LWP 24020)): #0 0x7fca2386556d in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #1 0x7fca1d486675 in g_cond_timed_wait_posix_impl (cond=0x7fca080008c4, entered_mutex=0x7fca1cf1d748, abs_time=value optimized out) at /build/buildd/glib2.0-2.19.10/gthread/gthread-posix.c:242 #2 0x7fca1cc6f6bb in g_async_queue_pop_intern_unlocked (queue=0x2068780, try=0, end_time=0x7fca1059ef90) at /build/buildd/glib2.0-2.19.10/glib/gasyncqueue.c:365 #3 0x7fca1ccbe209 in g_thread_pool_thread_proxy (data=value optimized out) at /build/buildd/glib2.0-2.19.10/glib/gthreadpool.c:220 #4 0x7fca1ccbcc74 in g_thread_create_proxy (data=0x35b5fc0) at /build/buildd/glib2.0-2.19.10/glib/gthread.c:635 #5 0x7fca238613ba in start_thread () from /lib/libpthread.so.0 #6 0x7fca1c362fcd in clone () from /lib/libc.so.6 #7 0x in ?? () Thread 35 (Thread 0x7fca011ab950 (LWP 24019)): #0 0x7fca2386556d in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #1 0x7fca1d486675 in g_cond_timed_wait_posix_impl (cond=0x7fca080008c4, entered_mutex=0x7fca1cf1d748, abs_time=value optimized out) at /build/buildd/glib2.0-2.19.10/gthread/gthread-posix.c:242 #2 0x7fca1cc6f6bb in g_async_queue_pop_intern_unlocked (queue=0x2068780, try=0, end_time=0x7fca011aaf90) at /build/buildd/glib2.0-2.19.10/glib/gasyncqueue.c:365 #3 0x7fca1ccbe209 in g_thread_pool_thread_proxy (data=value optimized out) at /build/buildd/glib2.0-2.19.10/glib/gthreadpool.c:220 #4 0x7fca1ccbcc74 in g_thread_create_proxy (data=0x7fca09182070) at /build/buildd/glib2.0-2.19.10/glib/gthread.c:635 #5 0x7fca238613ba in start_thread () from /lib/libpthread.so.0 #6 0x7fca1c362fcd in clone () from /lib/libc.so.6 #7 0x in ?? () Thread 34 (Thread 0x7fca019ac950 (LWP 24018)): #0 0x7fca2386556d in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #1 0x7fca1d486675 in g_cond_timed_wait_posix_impl (cond=0x7fca080008c4, entered_mutex=0x7fca1cf1d748, abs_time=value optimized out) at /build/buildd/glib2.0-2.19.10/gthread/gthread-posix.c:242 #2 0x7fca1cc6f6bb in g_async_queue_pop_intern_unlocked (queue=0x2068780, try=0, end_time=0x7fca019abf90) at /build/buildd/glib2.0-2.19.10/glib/gasyncqueue.c:365 #3 0x7fca1ccbe209 in g_thread_pool_thread_proxy (data=value optimized out) at /build/buildd/glib2.0-2.19.10/glib/gthreadpool.c:220 #4 0x7fca1ccbcc74 in g_thread_create_proxy (data=0x7fca091970f0) at /build/buildd/glib2.0-2.19.10/glib/gthread.c:635 #5 0x7fca238613ba in start_thread () from /lib/libpthread.so.0 #6 0x7fca1c362fcd in clone () from /lib/libc.so.6 #7 0x in ?? () Thread 16 (Thread 0x7fca06ae6950 (LWP 23860)): #0 0x7fca01f76610 in ?? () #1 0x7fca23861459 in start_thread () from /lib/libpthread.so.0 ---Type return to continue, or q return to quit--- #2 0x7fca1c362fcd in clone () from /lib/libc.so.6 #3 0x in ?? () Thread 7 (Thread 0x7fca062e5950 (LWP 23846)): #0 0x7fca238652e9 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #1 0x7fca1cc6f67c in g_async_queue_pop_intern_unlocked (queue=0x1f6c1a0, try=0, end_time=0x0) at /build/buildd/glib2.0-2.19.10/glib/gasyncqueue.c:358 #2 0x7fca1cc6fa32 in IA__g_async_queue_pop (queue=0x1f6c1a0) at /build/buildd/glib2.0-2.19.10/glib/gasyncqueue.c:398 #3 0x7fca2416e255 in action_thread_main (db=0x21a0140) at rhythmdb.c:2865 #4 0x7fca1ccbcc74 in g_thread_create_proxy (data=0x2ff0810) at /build/buildd/glib2.0-2.19.10/glib/gthread.c:635 #5 0x7fca238613ba in start_thread () from /lib/libpthread.so.0 #6 0x7fca1c362fcd in clone () from /lib/libc.so.6 #7 0x in ?? () Thread 1 (Thread 0x7fca24596800 (LWP 23837)): #0 0x7fca1c359496 in poll () from /lib/libc.so.6 #1 0x7fca1cc9670f in g_main_context_iterate (context=0x1e2ca00, block=1, dispatch=1, self=value optimized out) at /build/buildd/glib2.0-2.19.10/glib/gmain.c:2761 #2 0x7fca1cc96d3d in IA__g_main_loop_run (loop=0x2ce9d50) at /build/buildd/glib2.0-2.19.10/glib/gmain.c:2656 #3 0x7fca1fd17937 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0 #4 0x00422e41 in main (argc=value optimized out, argv=value optimized out) at main.c:330 #0 0x7fca01f76610 in ?? () (gdb) info registers rax0x7fca01f76610 140505593112080 rbx0xb0 176 rcx
[Bug 340784] [NEW] [Jaunty] Pulseaudio fills my logfiles.
Public bug reported: Binary package hint: pulseaudio ls -lh syslog -rw-r- 1 syslog adm 140M 2009-03-10 22:50 syslog Waves% grep 'pulseaudio' syslog |wc -l 586824 Waves% wc -l syslog 589402 syslog For an example of what pulseaudio is doing, it's using ~80% cpu, 60% more in syslog, and my log is full of : Mar 10 22:44:24 Waves pulseaudio[4494]: alsa-util.c: snd_pcm_avail_update() returned a value that is exceptionally large: 13835058047658039424 bytes (418250295751 ms) Most l ikely this is a Linux bug. Please report this issue to the ALSA developers. Mar 10 22:44:24 Waves pulseaudio[4494]: alsa-util.c: snd_pcm_avail_update() returned a value that is exceptionally large: 13835058047658025088 bytes (418250295670 ms) Most l ikely this is a Linux bug. Please report this issue to the ALSA developers. Mar 10 22:44:24 Waves pulseaudio[4494]: alsa-util.c: snd_pcm_avail_update() returned a value that is exceptionally large: 13835058047658010752 bytes (418250295588 ms) Most l ikely this is a Linux bug. Please report this issue to the ALSA developers. Mar 10 22:44:24 Waves pulseaudio[4494]: alsa-util.c: snd_pcm_avail_update() returned a value that is exceptionally large: 13835058047658010852 bytes (418250295589 ms) Most l ikely this is a Linux bug. Please report this issue to the ALSA developers. Mar 10 22:44:24 Waves pulseaudio[4494]: alsa-util.c: snd_pcm_avail_update() returned a value that is exceptionally large: 13835058047657996516 bytes (418250295508 ms) Most l ikely this is a Linux bug. Please report this issue to the ALSA developers. Mar 10 22:44:24 Waves pulseaudio[4494]: alsa-util.c: snd_pcm_avail_update() returned a value that is exceptionally large: 13835058047657982180 bytes (418250295426 ms) Most l ikely this is a Linux bug. Please report this issue to the ALSA developers. Mar 10 22:44:24 Waves pulseaudio[4494]: alsa-util.c: snd_pcm_avail_update() returned a value that is exceptionally large: 13835058047657967844 bytes (418250295345 ms) Most l ikely this is a Linux bug. Please report this issue to the ALSA developers. Mar 10 22:44:24 Waves pulseaudio[4494]: alsa-util.c: snd_pcm_avail_update() returned a value that is exceptionally large: 13835058047657953508 bytes (418250295264 ms) Most l ikely this is a Linux bug. Please report this issue to the ALSA developers. Mar 10 22:44:24 Waves pulseaudio[4494]: alsa-util.c: snd_pcm_avail_update() returned a value that is exceptionally large: 13835058047657939172 bytes (418250295183 ms) Most l ikely this is a Linux bug. Please report this issue to the ALSA developers. Mar 10 22:44:24 Waves pulseaudio[4494]: alsa-util.c: snd_pcm_avail_update() returned a value that is exceptionally large: 13835058047657924836 bytes (418250295101 ms) Most l ikely this is a Linux bug. Please report this issue to the ALSA developers. Mar 10 22:44:24 Waves pulseaudio[4494]: alsa-util.c: snd_pcm_avail_update() returned a value that is exceptionally large: 13835058047657910500 bytes (418250295020 ms) Most l ikely this is a Linux bug. Please report this issue to the ALSA developers. Mar 10 22:44:24 Waves pulseaudio[4494]: alsa-util.c: snd_pcm_avail_update() returned a value that is exceptionally large: 13835058047657896164 bytes (418250294939 ms) Most l ikely this is a Linux bug. Please report this issue to the ALSA developers. Mar 10 22:44:24 Waves pulseaudio[4494]: alsa-util.c: snd_pcm_avail_update() returned a value that is exceptionally large: 13835058047657881828 bytes (418250294858 ms) Most l ikely this is a Linux bug. Please report this issue to the ALSA developers. Mar 10 22:44:24 Waves pulseaudio[4494]: alsa-util.c: snd_pcm_avail_update() returned a value that is exceptionally large: 13835058047657867492 bytes (418250294776 ms) Most l ikely this is a Linux bug. Please report this issue to the ALSA developers. Mar 10 22:44:24 Waves pulseaudio[4494]: alsa-util.c: snd_pcm_avail_update() returned a value that is exceptionally large: 13835058047657867648 bytes (418250294777 ms) Most l ikely this is a Linux bug. Please report this issue to the ALSA developers. Mar 10 22:44:24 Waves pulseaudio[4494]: alsa-util.c: snd_pcm_avail_update() returned a value that is exceptionally large: 13835058047657853312 bytes (418250294696 ms) Most l ikely this is a Linux bug. Please report this issue to the ALSA developers. Mar 10 22:44:24 Waves pulseaudio[4494]: alsa-util.c: snd_pcm_avail_update() returned a value that is exceptionally large: 13835058047657838976 bytes (418250294615 ms) Most l ikely this is a Linux bug. Please report this issue to the ALSA developers. Mar 10 22:44:24 Waves pulseaudio[4494]: alsa-util.c: snd_pcm_avail_update() returned a value that is exceptionally large: 13835058047657824640 bytes (418250294533 ms) Most l ikely this is a Linux bug. Please report this I was simply trying to play the new NIN video from vimeo. http://vimeo.com/3496673 pulseaudio: Installed: 0.9.14-0ubuntu11 Candidate: 0.9.14-0ubuntu11 Version table:
[Bug 336965] Re: [Jaunty Regression] Severe Audio Distortion
I'm still affected by this (latest update) and the only way for me to not get dropouts is to remove pulseaudio from the equation. Will there be an updated kernel package with working intel-hda drivers so we can expect Working Sound? -- [Jaunty Regression] Severe Audio Distortion https://bugs.launchpad.net/bugs/336965 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 337294] Re: rhythmbox crashed with SIGSEGV in start_thread()
Attached stacktrace. (Can't filter out sig33 since playback doesn't work then) ** Attachment added: gdb-rhythmbox.txt http://launchpadlibrarian.net/23426687/gdb-rhythmbox.txt -- rhythmbox crashed with SIGSEGV in start_thread() https://bugs.launchpad.net/bugs/337294 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 337122] Re: Pulseaudio glitches when playing music
** Attachment added: lspci.log http://launchpadlibrarian.net/23342306/lspci.log -- Pulseaudio glitches when playing music https://bugs.launchpad.net/bugs/337122 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 337122] [NEW] Pulseaudio glitches when playing music
Public bug reported: Binary package hint: pulseaudio When playing music with Rhythmbox is glitches and scratches, running pulseaudio from the console gives me the following (repeated, MANY times) E: module-alsa-sink.c: ALSA woke us up to write new data to the device, but there was actually nothing to write! Most likely this is a Linux bug. Please report this issue to the ALSA developers. We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail_update() returned 0. I: module-alsa-sink.c: Underrun! N: module-alsa-sink.c: Increasing minimal latency to 16.00 ms E: module-alsa-sink.c: ALSA woke us up to write new data to the device, but there was actually nothing to write! Most likely this is a Linux bug. Please report this issue to the ALSA developers. We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail_update() returned 0. E: module-alsa-sink.c: ALSA woke us up to write new data to the device, but there was actually nothing to write! Most likely this is a Linux bug. Please report this issue to the ALSA developers. We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail_update() returned 0. I: module-alsa-sink.c: Underrun! N: module-alsa-sink.c: Increasing wakeup watermark to 8.00 ms E: module-alsa-sink.c: ALSA woke us up to write new data to the device, but there was actually nothing to write! Most likely this is a Linux bug. Please report this issue to the ALSA developers. We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail_update() returned 0. E: module-alsa-sink.c: ALSA woke us up to write new data to the device, but there was actually nothing to write! Most likely this is a Linux bug. Please report this issue to the ALSA developers. We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail_update() returned 0. I: module-alsa-sink.c: Underrun! N: module-alsa-sink.c: Increasing minimal latency to 26.00 ms E: module-alsa-sink.c: ALSA woke us up to write new data to the device, but there was actually nothing to write! Most likely this is a Linux bug. Please report this issue to the ALSA developers. We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail_update() returned 0. alsa-info.sh results are here: http://www.alsa-project.org/db/?f=13a6834f1de4bf161dcf645f1e85d33550e0c975 Description:Ubuntu jaunty (development branch) Release:9.04 Updated Tue March 03 at 9:40 am. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- Pulseaudio glitches when playing music https://bugs.launchpad.net/bugs/337122 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 335240] [NEW] pulseaudio went on a spin and dragged Rhythmbox down with it.
Public bug reported: Binary package hint: pulseaudio E: alsa-util.c: snd_pcm_avail_update() returned a value that is exceptionally large: 13835058055282163644 bytes (418293516410 ms) Most likely this is a Linux bug. Please report this issue to the ALSA developers. Soft CPU time limit exhausted, terminating. Hard CPU time limit exhausted, terminating forcibly. zsh: abort pulseaudio Waves% After that, Rhythmbox crashed as well, and then the world was very sad. If I feed pulseaudio with some morphine, will it mellow down and do some music with me then? ( Bit tired of all the pulseaudio related bugs I'm hitting, it's hard to enjoy music now) Description:Ubuntu jaunty (development branch) Release:9.04 pulseaudio: Installed: 0.9.14-0ubuntu8 Candidate: 0.9.14-0ubuntu8 Version table: *** 0.9.14-0ubuntu8 0 500 http://se.archive.ubuntu.com jaunty/main Packages 100 /var/lib/dpkg/status rhythmbox: Installed: 0.11.6svn20090209-0ubuntu1 Candidate: 0.11.6svn20090209-0ubuntu1 Version table: *** 0.11.6svn20090209-0ubuntu1 0 500 http://se.archive.ubuntu.com jaunty/main Packages 100 /var/lib/dpkg/status ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- pulseaudio went on a spin and dragged Rhythmbox down with it. https://bugs.launchpad.net/bugs/335240 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 333718] [NEW] Liferea takes approx 2 seconds to act from pressing next to displaying anything but white.
Public bug reported: I just installed 9.04 to do some testing and I found liferea to be nearly unusable in the current version. I skim a _lot_ of feeds, and it's now stalling for about 2-3 seconds between each time, doing appearantly nothing. During this time it spikes to the top of the CPU usage ( too short for me to really notice how much) and it generally feels unresponsive. This is compared to 8.10 where it would fsync() storm and eat ram, but at least was responsive. Now it just feels like swimming in molasses. Description:Ubuntu jaunty (development branch) Release:9.04 liferea: Installed: 1.4.23-0ubuntu2 Candidate: 1.4.23-0ubuntu2 Version table: *** 1.4.23-0ubuntu2 0 500 http://se.archive.ubuntu.com jaunty/main Packages 100 /var/lib/dpkg/status ** Affects: liferea (Ubuntu) Importance: Undecided Status: New -- Liferea takes approx 2 seconds to act from pressing next to displaying anything but white. https://bugs.launchpad.net/bugs/333718 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 333717] [NEW] Liferea takes approx 2 seconds to act from pressing next to displaying anything but white.
Public bug reported: I just installed 9.04 to do some testing and I found liferea to be nearly unusable in the current version. I skim a _lot_ of feeds, and it's now stalling for about 2-3 seconds between each time, doing appearantly nothing. During this time it spikes to the top of the CPU usage ( too short for me to really notice how much) and it generally feels unresponsive. This is compared to 8.10 where it would fsync() storm and eat ram, but at least was responsive. Now it just feels like swimming in molasses. ** Affects: liferea (Ubuntu) Importance: Undecided Status: Invalid -- Liferea takes approx 2 seconds to act from pressing next to displaying anything but white. https://bugs.launchpad.net/bugs/333717 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 333717] Re: Liferea takes approx 2 seconds to act from pressing next to displaying anything but white.
Dupe ** Changed in: liferea (Ubuntu) Status: New = Invalid -- Liferea takes approx 2 seconds to act from pressing next to displaying anything but white. https://bugs.launchpad.net/bugs/333717 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 215035] Re: Many special keys on Logitech Wave keyboard don't work
I can verify that the keys still do not work properly in Ubuntu (9.04 nor 8.10) -- Many special keys on Logitech Wave keyboard don't work https://bugs.launchpad.net/bugs/215035 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 332862] Re: ubiquity crashed with ImportError in module()
Same here, but in the .1 release of the same day. -- ubiquity crashed with ImportError in module() https://bugs.launchpad.net/bugs/332862 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 223400] Re: When right-clicking on a Raw image, I cannot open it in the Gimp
Yes, it is a bit elitistic, but we are talking about a Fair bit more than simple jpeg compression error, you lose 4 bits per pixel channel of information as well. -- When right-clicking on a Raw image, I cannot open it in the Gimp https://bugs.launchpad.net/bugs/223400 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 223400] Re: When right-clicking on a Raw image, I cannot open it in the Gimp
Intrepid still does not have the right Mime-types. The Develop in UF-raw is _not_ an option for real use as it involves a meta-stage that is very lossy in comparison. (RAW-Jpeg-Edit is a _bad_ move compared to RAW-Edit) and frankly, even suggesting such a workflow shows an obvious lack of insight into why a photographer would use RAW to begin with. Also, Do note that while f-spot might expect a distinct copy, it should be fully acceptable to use F-spot as the launcher for further editing in the Gimp and not be expected to save the files in the exact same place and work location. For example, Editing would commonly involve changing format to the gimp's internal state so you can keep track of layers/channels, and then exports from that format to others. Now, Just what from this log is it that you expect to see, the page after page of [Debug 14:35:54.816] open uri = file:///media/store/ ..? -- When right-clicking on a Raw image, I cannot open it in the Gimp https://bugs.launchpad.net/bugs/223400 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 220005] Re: xrdp package doesn't work out of box
Hello all I ran into the same thing. There where two simply things i did to get it working perfectly. Just install tightvncserver (even though it doesnt get installed automatically with xrdp) Restart the system (it would not work until it was restarted for some reason) by looking at the log, I think the vncserver gets called from sesman (127.0.0.1:5910) so at least some type of vncserver has to be installed, i just used tightvncserver as stated above and it worked great ***after restarting the system***. So now using Remote Desktop from a windows box to my linux box works great. I tested it on two fresh installs of Ubuntu, gnome and KDE. To fix this whole thing it seems like the vncserver should be a dependent and it should prompt for a restart after a successful install. Hope this helps. -- xrdp package doesn't work out of box https://bugs.launchpad.net/bugs/220005 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 220005] Re: xrdp package doesn't work out of box
Eviltechie What exactly are the details of what your doing and errors your getting? What have you tried? Did you install xrdp and tightvncserver then restart? What is the error in the log that comes up when you try to connect? What version of ubuntu are you using (I use 8.04)? Are you trying to connect to a linux box thats in on your local network, remote, or vmware? What version of windows? Please provide some more details to make it easier to help. You should not need to have kde installed. I got it working on a vanilla gnome install without a problem. -- xrdp package doesn't work out of box https://bugs.launchpad.net/bugs/220005 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 205040] Re: Gossip loses accounts after update to Hardy Heron beta
Most probably, I'm not about to install an old version of Ubuntu just to see if there has been a magical fix of upgrade-path of the package when you move to a more recent version of Ubuntu. I'd expect that to be the maintainers job and resources to test. -- Gossip loses accounts after update to Hardy Heron beta https://bugs.launchpad.net/bugs/205040 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 272418] Re: openbox/Gnome wont launch from gdm
Verifying as well, it broke my upgrade path. Please note that the manpage of gnome-session still documents --choose- session and --choosesession as valid options. Waves% gnome-session --choose-session openbox ** (gnome-session:7119): WARNING **: Unknown option --choose-session Waves% gnome-session --choosesession openbox ** (gnome-session:7120): WARNING **: Unknown option --choosesession -- openbox/Gnome wont launch from gdm https://bugs.launchpad.net/bugs/272418 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 242263] [NEW] OpenJDK in Firefox cannot run applets over SSL
Public bug reported: Binary package hint: icedtea-gcjwebplugin I can run the following test applet using OpenJDK in Firefox: http://www.java.com/en/download/help/testvm.xml However, it fails if I try the same applet over https, using this url: https://www.java.com/en/download/help/testvm.xml The above URL does work using java-6-sun-1.6.0.06. The packages used are all the latest from updating against 8.04. Pat McNerthney ** Affects: icedtea-gcjwebplugin (Ubuntu) Importance: Undecided Status: New -- OpenJDK in Firefox cannot run applets over SSL https://bugs.launchpad.net/bugs/242263 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 218812] Re: evince crashed with SIGSEGV in gdk_cairo_set_source_pixbuf()
Unfortunately, Nope. I didn't keep it for tests. -- evince crashed with SIGSEGV in gdk_cairo_set_source_pixbuf() https://bugs.launchpad.net/bugs/218812 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 192457] Re: nautilus crashed with SIGSEGV
messages.0:May 5 09:45:52 Waves kernel: [164588.388120] nautilus[31854]: segfault at 0001 eip 0812f2b8 esp bfa7c620 error 4 Aye, I still do at least. -- nautilus crashed with SIGSEGV https://bugs.launchpad.net/bugs/192457 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 223400] Re: When right-clicking on a CR2 (Raw) image, I cannot open it in the Gimp
Hardy Heron 32bit ** Attachment added: example image. http://launchpadlibrarian.net/14358768/IMG_3994.CR2 -- When right-clicking on a CR2 (Raw) image, I cannot open it in the Gimp https://bugs.launchpad.net/bugs/223400 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 223400] [NEW] When right-clicking on a CR2 (Raw) image, I cannot open it in the Gimp
Public bug reported: I have a mix of jpeg and RAW (.CR2, canon) images. When browsing with Nautilus, I can double-click an .CR2 image and it opens in The Gimp, ( meaning: my mime types are configured correctly) but from inside f-spot, it will only recognize UFRaw, and will not let me open it in the Gimp. With normal JPEG's, I'm allowed to use the Gimp from inside f-spot. ** Affects: f-spot (Ubuntu) Importance: Undecided Status: New -- When right-clicking on a CR2 (Raw) image, I cannot open it in the Gimp https://bugs.launchpad.net/bugs/223400 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 179659] Re: evince crashed with SIGSEGV in TextLine::visitSelection()
http://www.cs.yale.edu/homes/aspnes/skip-graphs-journal.pdf Did it for me, I was randomly selecting/Clicking things as a distraction while reading, so doing repeated select/unselect movements. -- evince crashed with SIGSEGV in TextLine::visitSelection() https://bugs.launchpad.net/bugs/179659 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 205040] [NEW] Gossip loses accounts after update to Hardy Heron beta
Public bug reported: Binary package hint: gossip Gossip doesn't start properly / starts with empty account info, launching it from a terminal greets me with: Waves% gossip /home/spider/.gnome2/Gossip/accounts.xml:4: element account: validity error : Element account content does not follow the DTD, expecting (name , id , resource? , password? , server? , port? , auto_connect? , use_ssl? , use_proxy?), got (name auto_connect use_proxy parameter parameter parameter parameter ) /home/spider/.gnome2/Gossip/accounts.xml:4: element account: validity error : No declaration for attribute type of element account /home/spider/.gnome2/Gossip/accounts.xml:8: element parameter: validity error : No declaration for element parameter /home/spider/.gnome2/Gossip/accounts.xml:8: element parameter: validity error : No declaration for attribute name of element parameter /home/spider/.gnome2/Gossip/accounts.xml:8: element parameter: validity error : No declaration for attribute type of element parameter /home/spider/.gnome2/Gossip/accounts.xml:9: element parameter: validity error : No declaration for element parameter /home/spider/.gnome2/Gossip/accounts.xml:9: element parameter: validity error : No declaration for attribute name of element parameter /home/spider/.gnome2/Gossip/accounts.xml:9: element parameter: validity error : No declaration for attribute type of element parameter /home/spider/.gnome2/Gossip/accounts.xml:10: element parameter: validity error : No declaration for element parameter /home/spider/.gnome2/Gossip/accounts.xml:10: element parameter: validity error : No declaration for attribute name of element parameter /home/spider/.gnome2/Gossip/accounts.xml:10: element parameter: validity error : No declaration for attribute type of element parameter /home/spider/.gnome2/Gossip/accounts.xml:11: element parameter: validity error : No declaration for element parameter /home/spider/.gnome2/Gossip/accounts.xml:11: element parameter: validity error : No declaration for attribute name of element parameter /home/spider/.gnome2/Gossip/accounts.xml:11: element parameter: validity error : No declaration for attribute type of element parameter /home/spider/.gnome2/Gossip/accounts.xml:13: element account: validity error : Element account content does not follow the DTD, expecting (name , id , resource? , password? , server? , port? , auto_connect? , use_ssl? , use_proxy?), got (name auto_connect use_proxy parameter parameter parameter ) /home/spider/.gnome2/Gossip/accounts.xml:13: element account: validity error : No declaration for attribute type of element account /home/spider/.gnome2/Gossip/accounts.xml:17: element parameter: validity error : No declaration for element parameter /home/spider/.gnome2/Gossip/accounts.xml:17: element parameter: validity error : No declaration for attribute name of element parameter /home/spider/.gnome2/Gossip/accounts.xml:17: element parameter: validity error : No declaration for attribute type of element parameter /home/spider/.gnome2/Gossip/accounts.xml:18: element parameter: validity error : No declaration for element parameter /home/spider/.gnome2/Gossip/accounts.xml:18: element parameter: validity error : No declaration for attribute name of element parameter /home/spider/.gnome2/Gossip/accounts.xml:18: element parameter: validity error : No declaration for attribute type of element parameter /home/spider/.gnome2/Gossip/accounts.xml:19: element parameter: validity error : No declaration for element parameter /home/spider/.gnome2/Gossip/accounts.xml:19: element parameter: validity error : No declaration for attribute name of element parameter /home/spider/.gnome2/Gossip/accounts.xml:19: element parameter: validity error : No declaration for attribute type of element parameter /home/spider/.gnome2/Gossip/accounts.xml:21: element account: validity error : Element account content does not follow the DTD, expecting (name , id , resource? , password? , server? , port? , auto_connect? , use_ssl? , use_proxy?), got (name auto_connect use_proxy parameter parameter parameter parameter ) /home/spider/.gnome2/Gossip/accounts.xml:21: element account: validity error : No declaration for attribute type of element account /home/spider/.gnome2/Gossip/accounts.xml:25: element parameter: validity error : No declaration for element parameter /home/spider/.gnome2/Gossip/accounts.xml:25: element parameter: validity error : No declaration for attribute name of element parameter /home/spider/.gnome2/Gossip/accounts.xml:25: element parameter: validity error : No declaration for attribute type of element parameter /home/spider/.gnome2/Gossip/accounts.xml:26: element parameter: validity error : No declaration for element parameter /home/spider/.gnome2/Gossip/accounts.xml:26: element parameter: validity error : No declaration for attribute name of element parameter /home/spider/.gnome2/Gossip/accounts.xml:26: element parameter: validity error : No declaration
[Bug 195415] Re: Ubuntu 7.10 stops installing to USB drive
Dereck, That would be a long story. Ubuntu hijacked the MRB of the main hard drive of my computer even though I was installing it on another drive. When Ubuntu couldn't load on the USB drive because I didn't unmount it first, the computer and the USB hard drive became unusable. I received a GRUB error when I tried to boot the computer. I Gparted and formatted the USB drive to ntfs. I found that Dell provided an MBR fix .iso image that can be put on a cd. That restored my MBR and fixed the GRUB error. With the hard drive and the USB drive restored, Ubuntu installed flawlessly on the unmounted USB drive. I found the mounting problem by looking through the logs. I thought that I could put Ubuntu on a USB drive and use it on different machines. That does not seem to be a possibility. -- Ubuntu 7.10 stops installing to USB drive https://bugs.launchpad.net/bugs/195415 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 195415] Re: Ubuntu 7.10 stops installing to USB drive
The USB drive needs to be unmounted first. -- Ubuntu 7.10 stops installing to USB drive https://bugs.launchpad.net/bugs/195415 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 195415] Re: Ubuntu 7.10 locks up installing to USB drive
** Attachment added: debug.txt http://launchpadlibrarian.net/12182933/debug.txt -- Ubuntu 7.10 locks up installing to USB drive https://bugs.launchpad.net/bugs/195415 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 195415] [NEW] Ubuntu 7.10 locks up installing to USB drive
Public bug reported: When installing Ubuntu 7.10 from CD to 160 eGo USB drive, it locks up at 15%. The first time it destroyed half of the drive. With Cute Partition Manager I was able to restore drive. Tried different formats, fat32, fat32 LBA, linux and the problem persisted. I've formatted to ntfs and will try again tomorrow. ** Affects: ubuntu Importance: Undecided Status: New -- Ubuntu 7.10 locks up installing to USB drive https://bugs.launchpad.net/bugs/195415 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 195415] Re: Ubuntu 7.10 locks up installing to USB drive
** Attachment added: install-debug.txt http://launchpadlibrarian.net/12182967/install-debug.txt -- Ubuntu 7.10 locks up installing to USB drive https://bugs.launchpad.net/bugs/195415 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 195415] Re: Ubuntu 7.10 locks up installing to USB drive
** Attachment added: partman.txt http://launchpadlibrarian.net/12182960/partman.txt -- Ubuntu 7.10 locks up installing to USB drive https://bugs.launchpad.net/bugs/195415 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 195415] Re: Ubuntu 7.10 locks up installing to USB drive
** Attachment added: syslog.txt http://launchpadlibrarian.net/12182945/syslog.txt -- Ubuntu 7.10 locks up installing to USB drive https://bugs.launchpad.net/bugs/195415 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 195415] Re: Ubuntu 7.10 stops installing to USB drive
** Summary changed: - Ubuntu 7.10 locks up installing to USB drive + Ubuntu 7.10 stops installing to USB drive ** Description changed: - When installing Ubuntu 7.10 from CD to 160 eGo USB drive, it locks up at 15%. + When installing Ubuntu 7.10 from CD to 160 eGo USB drive, it stops at 15%. The first time it destroyed half of the drive. With Cute Partition Manager I was able to restore drive. - Tried different formats, fat32, fat32 LBA, linux and the problem persisted. + Tried different formats, fat32, fat32 LBA, linux and the problem persisted. I've formatted to ntfs and will try again tomorrow. -- Ubuntu 7.10 stops installing to USB drive https://bugs.launchpad.net/bugs/195415 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 152276] xorg-driver-fglrx not working causing system crash with new ati cards (2600 XT)
Public bug reported: Binary package hint: xorg-driver-fglrx Just install and enabling with restricted manager shows this ** Affects: linux-restricted-modules-2.6.22 (Ubuntu) Importance: Undecided Status: New -- xorg-driver-fglrx not working causing system crash with new ati cards (2600 XT) https://bugs.launchpad.net/bugs/152276 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 67072] firefox crash
Public bug reported:
Binary package hint: mozilla-firefox
firefox crach when wisiting page http://o2.pl
[...]
write(28, GIF89a\0\0\304\0\0\377\377\377\377\314\377\377\314\314..., 1024)
= 1024
gettimeofday({1161326413, 485382}, NULL) = 0
lseek(28, 81920, SEEK_SET) = 81920
write(28, \0\1\0\6\0\0\0\0\0\0\0\1E8oLE8oME_Gp\0\0\3\264\0\0\000..., 512) =
512
gettimeofday({1161326413, 486003}, NULL) = 0
gettimeofday({1161326413, 486212}, NULL) = 0
gettimeofday({1161326413, 486595}, NULL) = 0
gettimeofday({1161326413, 498291}, NULL) = 0
gettimeofday({1161326413, 505709}, NULL) = 0
gettimeofday({1161326413, 509318}, NULL) = 0
gettimeofday({1161326413, 510584}, NULL) = 0
gettimeofday({1161326413, 511310}, NULL) = 0
write(2, New\n, 4New
)= 4
write(3, 5\30\4\0\206\5\200\1\0\0\0\4\0\4\0005\1\4\0\207\5\200..., 2876) =
2876
read(3, 0xbf942b5c, 32) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=3, events=POLLIN, revents=POLLIN}], 1, -1) = 1
read(3, \26\0\347\217\252\0\200\1\252\0\200\1\250\0\200\1\0\0\0..., 32) = 32
read(3, \17\326\347\217\254\0\200\1\0\1\211\1v\1\377\0\377\377..., 32) = 32
read(3, \fE\347\217\254\0\200\1\6\0\0\0f\0\4\0\1\0\0\0\0\0\0\0..., 32) = 32
read(3, \f\360\347\217\254\0\200\1\0\0\4\0l\0\17\0\0\0 \10\2\0..., 32) = 32
read(3, \26\0M\223\225\5\200\1\225\5\200\1\0\0\0\0\0\0\0\0\240..., 32) = 32
read(3, \26\5N\223\224\5\200\1\224\5\200\1\332\2\200\1\0\0\271..., 32) = 32
read(3, \23\21O\223\225\5\200\1\225\5\200\1\0\5\200\1\1\0\0\300..., 32) = 32
read(3, \23\21P\223\224\5\200\1\224\5\200\1\0\5\200\1\1\0\0\300..., 32) = 32
read(3, \17\326P\223\225\5\200\1\2\242B\10\310{b\10\264\243\330..., 32) = 32
read(3, \1\0Q\223\3\0\0\0\\0\0\0\1\0\1\1\377\377\377\377\0\0\0..., 32) = 32
read(3, |\200C\0|\200C\0\0\0\0\0, 12) = 12
read(3, \1\30R\223\0\0\0\0\0\0\0\0\0\0\0\240\0\220\1\0\0\0\0\10..., 32) = 32
write(3, \2\30\4\0\225\5\200\1\0\10\0\0|\200K\0+\1\1\0, 20) = 20
read(3, 0xbf942b98, 32) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=3, events=POLLIN, revents=POLLIN}], 1, -1) = 1
read(3, \1\2T\223\0\0\0\0\202\0\200\1\4\0\0\0\4\0\0\0\0\0\0\0\360..., 32) = 32
write(3, \16\30\2\0\225\5\200\1, 8) = 8
read(3, 0xbf941fe8, 32) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=3, events=POLLIN, revents=POLLIN}], 1, -1) = 1
read(3, \1\30U\223\0\0\0\0\0\0\0\0\0\0\0\240\0\220\1\0\0\0\0\10..., 32) = 32
write(3, \1\30\r\0\226\5\200\1\225\5\200\1\0\0\0\0\240\0\220\1\0..., 100) =
100
read(3, 0xbf941f1c, 32) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=3, events=POLLIN, revents=POLLIN}], 1, -1) = 1
read(3, \20\21V\223\225\5\200\1\226\5\200\1\0\0\0\0\240\0\220\1..., 32) = 32
read(3, \1\0Y\223\3\0\0\0\\0\0\0\1\0\1\1\377\377\377\377\0\0\0..., 32) = 32
read(3, \0\0b\0\0\0b\0\0\0\0\0, 12) = 12
read(3, \1\30Z\223\0\0\0\0\0\0\0\0\0\0\0\240\0\220\1\0\0\0\0\10..., 32) = 32
write(3, \2\30\4\0\226\5\200\1\0\10\0\0\0\0z\0+\0\1\0, 20) = 20
read(3, 0xbf941fc8, 32) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=3, events=POLLIN, revents=POLLIN}], 1, -1) = 1
read(3, \1\2\\\223\0\0\0\0\202\0\200\1\4\0\0\0\4\0\0\0\0\0\0\0..., 32) = 32
write(32, +\0\1\0, 4) = 4
read(32, \16\0004\0\1\0\340\1\0\0\10\240T\34\10\251\243\31\10\350..., 32) =
32
read(32, \16\0005\0\1\0\340\1\0\0\10\240T\34\10\251\243\31\10\350..., 32) =
32
read(32, \16\0006\0\1\0\340\1\0\0\10\240T\34\10\251\243\31\10\350..., 32) =
32
read(32, \16\0007\0\1\0\340\1\0\0\10\240T\34\10\251\243\31\10\350..., 32) =
32
read(32, \16\0008\0\1\0\340\1\0\0\10\240T\34\10\251\243\31\10\350..., 32) =
32
read(32, \16\0009\0\1\0\340\1\0\0\10\240T\34\10\251\243\31\10\350..., 32) =
32
read(32, \16\0:\0\1\0\340\1\0\0\10\240T\34\10\251\243\31\10\350..., 32) = 32
read(32, \16\0;\0\1\0\340\1\0\0\10\240T\34\10\251\243\31\10\350..., 32) = 32
read(32, \16\0\0\1\0\340\1\0\0\10\240T\34\10\251\243\31\10\350..., 32) = 32
read(32, \16\0=\0\1\0\340\1\0\0\10\240T\34\10\251\243\31\10\350..., 32) = 32
read(32, \16\0\0\1\0\340\1\0\0\10\240T\34\10\251\243\31\10\350..., 32) = 32
read(32, \16\0?\0\1\0\340\1\0\0\10\240T\34\10\251\243\31\10\350..., 32) = 32
read(32, [EMAIL PROTECTED]\10\240T\34\10\251\243\31\10\350..., 32) = 32
read(32, \16\0A\0\1\0\340\1\0\0\10\240T\34\10\251\243\31\10\350..., 32) = 32
read(32, 0xbf942048, 32)= -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=32, events=POLLIN, revents=POLLIN}], 1, -1) = 1
read(32, \1\2B\0\0\0\0\0\202\0\200\1\4\0\0\0\4\0\0\0\377\377\377..., 32) = 32
write(32, \1\30\r\0\6\0\340\1\226\5\200\1\0\0\0\0\240\0\220\1\0\0..., 128) =
128
read(32, 0xbf942048, 32)= -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=32, events=POLLIN, revents=POLLIN}], 1, -1) = 1
read(32, \1\2H\0\0\0\0\0\202\0\200\1\4\0\0\0\4\0\0\0\0\0\0\0\360..., 32) = 32
write(3, +\30\1\0, 4) = 4
read(3, \20\21\\\223\226\5\200\1\6\0\340\1\0\0\0\0\240\0\220\1..., 32) =
