[Bug 1277210]
Sadly no-one offered to take over the dragonegg project after I stepped down. I think it is dead. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1277210 Title: dragonegg: FTBFS: ABIHack.inc:1666:36: error: 'TARGET_CPU_DEFAULT_max' was not declared in this scope To manage notifications about this bug go to: https://bugs.launchpad.net/llvm/+bug/1277210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1219685] Re: libtcmalloc_minimal.so symlink not created
Thanks. Is this documented in the tcmalloc-minimal4 package somewhere? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1219685 Title: libtcmalloc_minimal.so symlink not created To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/google-perftools/+bug/1219685/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1219685] [NEW] libtcmalloc_minimal.so symlink not created
Public bug reported: The libtcmalloc-minimal4 package installs libtcmalloc_minimal.so.4.1.0 and creates a symlink libtcmalloc_minimal.so.4 to it. However no libtcmalloc_minimal.so is created, making it impossible to link programs with this package without creating the symlink manually. Traditionally this kind of symlink is created by the -dev package, but there is no libtcmalloc-minimal4-dev package. ** Affects: google-perftools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1219685 Title: libtcmalloc_minimal.so symlink not created To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/google-perftools/+bug/1219685/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 38561] Re: KDE applet has no Quit menu entry
Skim doesn't seem to exist any more, so no. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/38561 Title: KDE applet has no Quit menu entry To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/skim/+bug/38561/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1008525] Re: gzip -f zips files with .gz suffix, creating file.gz.gz
Hi Evan, > Please run > apport-collect 1008525 I did this and discovered that this tool is buggy :) If you are already logged into launchpad (as I was) then you don't get the authentification/permission question in the browser, you just get a message saying you are already logged in. Logging out then trying again worked. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1008525 Title: gzip -f zips files with .gz suffix, creating file.gz.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gzip/+bug/1008525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1008525] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1008525/+attachment/3175932/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1008525 Title: gzip -f zips files with .gz suffix, creating file.gz.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gzip/+bug/1008525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1008525] Re: gzip -f zips files with .gz suffix, creating file.gz.gz
apport information ** Tags added: apport-collected precise ** Description changed: Create a directory containing a file, for example: $ mkdir d $ touch d/f Now do (yes, running gzip twice): $ gzip -f -r d $ gzip -f -r d Look in the directory and you will find the file a.gz.gz. $ cd d $ ls f.gz.gz This is a change from ubuntu versions before precise pangolin: previously gzip would not recompress files ending in .gz when run in this way. + --- + ApportVersion: 2.0.1-0ubuntu8 + Architecture: amd64 + DistroRelease: Ubuntu 12.04 + EcryptfsInUse: Yes + NonfreeKernelModules: wl + Package: gzip 1.4-1ubuntu2 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16 + Tags: precise + Uname: Linux 3.2.0-24-generic x86_64 + UpgradeStatus: Upgraded to precise on 2012-04-29 (36 days ago) + UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1008525/+attachment/3175931/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1008525 Title: gzip -f zips files with .gz suffix, creating file.gz.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gzip/+bug/1008525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1008525] [NEW] gzip -f zips files with .gz suffix, creating file.gz.gz
Public bug reported: Create a directory containing a file, for example: mkdir d touch d/f Now do (yes, running gzip twice): gzip -f -r d gzip -f -r d Look in the directory and you will find the file a.gz.gz. This is a change from ubuntu versions before precise pangolin: previously gzip would not recompress files ending in .gz when run in this way. ** Affects: gzip (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1008525 Title: gzip -f zips files with .gz suffix, creating file.gz.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gzip/+bug/1008525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 738098] Re: ld: cannot find crti.o: No such file or directory
I am building GCC from upstream (I do some work on GCC). Are you planning to push a patch upstream? Another annoyance is that I have several custom versions of GCC I obtained from a commercial company. These all broke too, and I can't rebuild them myself. However Iain's LD_LIBRARY_PATH workaround is effective, so it's not the end of the world. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/738098 Title: ld: cannot find crti.o: No such file or directory -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 738098] Re: ld: cannot find crti.o: No such file or directory
Same problem here. For example, it is no longer possible to build gcc from source: once the build gets to the point where the new gcc needs to build a program linking fails with /usr/bin/ld: cannot find crti.o: No such file or directory /usr/bin/ld: cannot find -lc /usr/bin/ld: cannot find crtn.o: No such file or directory collect2: ld returned 1 exit status This is after recently updating natty on an x86-64 machine -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/738098 Title: ld: cannot find crti.o: No such file or directory -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 521055] Re: rsyslog is updated too late
I have the same problem (karmic). Rsyslog is started by an upstart script, which starts on event 'filesystem', while ltsp-client-setup is a System-V style init script, started at rcS. The result is that rsyslog starts before ltsp-client-setup has written /etc/rsyslog.d/50-ltsp. -- rsyslog is updated too late https://bugs.launchpad.net/bugs/521055 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 558852] Re: evince assert failure: *** glibc detected *** evince: munmap_chunk(): invalid pointer: 0xb5e00e18 ***
** Attachment added: "File crashing evince" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/558852/+attachment/1594144/+files/pw-affine2.dvi -- evince assert failure: *** glibc detected *** evince: munmap_chunk(): invalid pointer: 0xb5e00e18 *** https://bugs.launchpad.net/bugs/558852 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 528488] Re: [drm] failed to load kernel module "nouveau"
> Sorry; there was an error in the apport scripts that prevented them from > attaching the proper information to this bug. They have now been fixed. > Could you please re-run “apport-collect 528488”? after yesterdays updates, this problem has gone away, so please feel free to close. -- [drm] failed to load kernel module "nouveau" https://bugs.launchpad.net/bugs/528488 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 528488] Re: [drm] failed to load kernel module "nouveau"
apport information ** Tags added: apport-collected ** Description changed: Binary package hint: xserver-xorg-video-nouveau I'm not using the nouveau PPA. Recently nouveau arrived in the lucid repository, and was working fine for me (well done!). But after a recent update, when gdm starts I get the nv driver, not nouveau. In Xorg.0.log I see: [drm] failed to load kernel module "nouveau" I discovered the following work around: (1) stop gdm (2) modprobe lbm_nouveau (3) start gdm Doing "modprobe lbm_nouveau" causes the screen to go black, so I actually do "sleep 1m; start gdm" in another console before doing the modprobe. The result is that gdm starts up with the nouveau driver, and all is well. Here is the initial part of a diff of Xorg.0.log, between the one that failed to load nouveau, and the other that did load nouveau: 16c16 < (==) Log file: "/var/log/Xorg.0.log", Time: Fri Feb 26 14:44:07 2010 --- > (==) Log file: "/var/log/Xorg.0.log", Time: Fri Feb 26 14:45:57 2010 23c23 < (++) using VT number 7 --- > (--) using VT number 7 107c107 < (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory) --- > (II) Open ACPI successful (/var/run/acpid.socket) 207,208c207,214 < [drm] failed to load kernel module "nouveau" < (EE) [drm] failed to open device --- > drmOpenDevice: open result is 8, (OK) > drmOpenByBusid: Searching for BusID pci::01:00.0 > drmOpenDevice: node name is /dev/dri/card0 > drmOpenDevice: open result is 8, (OK) > drmOpenByBusid: drmOpenMinor returns 8 > drmOpenByBusid: drmGetBusid reports pci::01:00.0 > (II) [drm] nouveau interface version: 0.0.15 > (WW) Falling back to old probe method for vesa 216,225c222,315 < (II) Loading sub module "vbe" < (II) LoadModule: "vbe" < (II) Loading /usr/lib/xorg/modules/libvbe.so < (II) Module vbe: vendor="X.Org Foundation" < compiled for 1.7.5, module version = 1.1.0 < ABI class: X.Org Video Driver, version 6.0 < (II) Loading sub module "int10" ... ProblemType: Bug Architecture: amd64 Date: Fri Feb 26 15:35:59 2010 DistroRelease: Ubuntu 10.04 EcryptfsInUse: Yes NonfreeKernelModules: wl Package: xserver-xorg-video-nouveau 1:0.0.15+git20100219+9b4118d-0ubuntu2 ProcEnviron: LANGUAGE=en_GB.UTF-8 PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-14.20-generic SourcePackage: xserver-xorg-video-nouveau Uname: Linux 2.6.32-14-generic x86_64 + --- + Architecture: amd64 + DistroRelease: Ubuntu 10.04 + EcryptfsInUse: Yes + NonfreeKernelModules: wl + Package: xserver-xorg-video-nouveau 1:0.0.15+git20100219+9b4118d-0ubuntu2 + PackageArchitecture: amd64 + ProcEnviron: + LANGUAGE=en_GB.UTF-8 + PATH=(custom, user) + LANG=en_GB.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 2.6.32-14.20-generic + Tags: lucid + Uname: Linux 2.6.32-14-generic x86_64 + UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare sudo ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/39908229/Dependencies.txt -- [drm] failed to load kernel module "nouveau" https://bugs.launchpad.net/bugs/528488 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 528488] Re: [drm] failed to load kernel module "nouveau"
** Attachment added: "Xorg.0.log after modprobe of lbm_nouveau" http://launchpadlibrarian.net/39820555/Xorg.0.log -- [drm] failed to load kernel module "nouveau" https://bugs.launchpad.net/bugs/528488 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 528488] Re: [drm] failed to load kernel module "nouveau"
** Attachment added: "Xorg.0.log that fails to load nouveau" http://launchpadlibrarian.net/39820509/Xorg.0.log.old -- [drm] failed to load kernel module "nouveau" https://bugs.launchpad.net/bugs/528488 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 528488] Re: [drm] failed to load kernel module "nouveau"
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/39820456/Dependencies.txt -- [drm] failed to load kernel module "nouveau" https://bugs.launchpad.net/bugs/528488 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 528488] [NEW] [drm] failed to load kernel module "nouveau"
Public bug reported: Binary package hint: xserver-xorg-video-nouveau I'm not using the nouveau PPA. Recently nouveau arrived in the lucid repository, and was working fine for me (well done!). But after a recent update, when gdm starts I get the nv driver, not nouveau. In Xorg.0.log I see: [drm] failed to load kernel module "nouveau" I discovered the following work around: (1) stop gdm (2) modprobe lbm_nouveau (3) start gdm Doing "modprobe lbm_nouveau" causes the screen to go black, so I actually do "sleep 1m; start gdm" in another console before doing the modprobe. The result is that gdm starts up with the nouveau driver, and all is well. Here is the initial part of a diff of Xorg.0.log, between the one that failed to load nouveau, and the other that did load nouveau: 16c16 < (==) Log file: "/var/log/Xorg.0.log", Time: Fri Feb 26 14:44:07 2010 --- > (==) Log file: "/var/log/Xorg.0.log", Time: Fri Feb 26 14:45:57 2010 23c23 < (++) using VT number 7 --- > (--) using VT number 7 107c107 < (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory) --- > (II) Open ACPI successful (/var/run/acpid.socket) 207,208c207,214 < [drm] failed to load kernel module "nouveau" < (EE) [drm] failed to open device --- > drmOpenDevice: open result is 8, (OK) > drmOpenByBusid: Searching for BusID pci::01:00.0 > drmOpenDevice: node name is /dev/dri/card0 > drmOpenDevice: open result is 8, (OK) > drmOpenByBusid: drmOpenMinor returns 8 > drmOpenByBusid: drmGetBusid reports pci::01:00.0 > (II) [drm] nouveau interface version: 0.0.15 > (WW) Falling back to old probe method for vesa 216,225c222,315 < (II) Loading sub module "vbe" < (II) LoadModule: "vbe" < (II) Loading /usr/lib/xorg/modules/libvbe.so < (II) Module vbe: vendor="X.Org Foundation" < compiled for 1.7.5, module version = 1.1.0 < ABI class: X.Org Video Driver, version 6.0 < (II) Loading sub module "int10" ... ProblemType: Bug Architecture: amd64 Date: Fri Feb 26 15:35:59 2010 DistroRelease: Ubuntu 10.04 EcryptfsInUse: Yes NonfreeKernelModules: wl Package: xserver-xorg-video-nouveau 1:0.0.15+git20100219+9b4118d-0ubuntu2 ProcEnviron: LANGUAGE=en_GB.UTF-8 PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-14.20-generic SourcePackage: xserver-xorg-video-nouveau Uname: Linux 2.6.32-14-generic x86_64 ** Affects: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid -- [drm] failed to load kernel module "nouveau" https://bugs.launchpad.net/bugs/528488 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 496817] Re: xinput no longer works to set-ptr-feedback after the latest Xserver upgrade in Lucid
** Attachment added: "Output of dmesg" http://launchpadlibrarian.net/38339367/dmesg -- xinput no longer works to set-ptr-feedback after the latest Xserver upgrade in Lucid https://bugs.launchpad.net/bugs/496817 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 496817] Re: xinput no longer works to set-ptr-feedback after the latest Xserver upgrade in Lucid
** Attachment added: "/var/log/Xorg.0.log" http://launchpadlibrarian.net/38339359/xorg -- xinput no longer works to set-ptr-feedback after the latest Xserver upgrade in Lucid https://bugs.launchpad.net/bugs/496817 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 496817] Re: xinput no longer works to set-ptr-feedback after the latest Xserver upgrade in Lucid
I'm having the same problem: some device names are not recognized any more, in
my case "bcm5974".
As you can see below, "xinput list" shows this device, and I can manipulate it
using the id (12) but not the
name ("bcm5974"). I could use the name with karmic, but not since I upgraded
to lucid.
$ xinput list
⎡ Virtual core pointer id=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)]
⎜ ↳ "Logitech USB-PS/2 Optical Mouse" id=10 [slave pointer (2)]
⎜ ↳ "Macintosh mouse button emulation"id=14 [slave pointer (2)]
⎜ ↳ "bcm5974" id=12 [slave pointer (2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard id=5[slave keyboard (3)]
↳ "Power Button"id=6[slave keyboard (3)]
↳ "Video Bus" id=7[slave keyboard (3)]
↳ "Power Button"id=8[slave keyboard (3)]
↳ "Sleep Button"id=9[slave keyboard (3)]
↳ "Apple, Inc. Apple Internal Keyboard / Trackpad" id=11 [slave
keyboard (3)]
↳ "Built-in iSight" id=13 [slave keyboard (3)]
$ xinput set-int-prop "bcm5974" "Device Enabled" 8 0
unable to find device bcm5974
$ xinput set-int-prop 12 "Device Enabled" 8 0
** Attachment added: "Result of lspci -vvnn"
http://launchpadlibrarian.net/38339340/lspci
--
xinput no longer works to set-ptr-feedback after the latest Xserver upgrade in
Lucid
https://bugs.launchpad.net/bugs/496817
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 452834] Re: WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52 suspend_test_finish+0x7c/0x80()
** Attachment added: "AlsaDevices.txt" http://launchpadlibrarian.net/33774341/AlsaDevices.txt ** Attachment added: "AplayDevices.txt" http://launchpadlibrarian.net/33774342/AplayDevices.txt ** Attachment added: "ArecordDevices.txt" http://launchpadlibrarian.net/33774343/ArecordDevices.txt ** Attachment added: "BootDmesg.txt" http://launchpadlibrarian.net/33774344/BootDmesg.txt ** Attachment added: "Card0.Amixer.values.txt" http://launchpadlibrarian.net/33774345/Card0.Amixer.values.txt ** Attachment added: "Card0.Codecs.codec.0.txt" http://launchpadlibrarian.net/33774348/Card0.Codecs.codec.0.txt ** Attachment added: "CurrentDmesg.txt" http://launchpadlibrarian.net/33774349/CurrentDmesg.txt ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/33774350/Dependencies.txt ** Attachment added: "IwConfig.txt" http://launchpadlibrarian.net/33774351/IwConfig.txt ** Attachment added: "Lspci.txt" http://launchpadlibrarian.net/33774352/Lspci.txt ** Attachment added: "Lsusb.txt" http://launchpadlibrarian.net/33774353/Lsusb.txt ** Attachment added: "OopsText.txt" http://launchpadlibrarian.net/33774354/OopsText.txt ** Attachment added: "PciMultimedia.txt" http://launchpadlibrarian.net/33774355/PciMultimedia.txt ** Attachment added: "ProcCpuinfo.txt" http://launchpadlibrarian.net/33774356/ProcCpuinfo.txt ** Attachment added: "ProcInterrupts.txt" http://launchpadlibrarian.net/33774360/ProcInterrupts.txt ** Attachment added: "ProcModules.txt" http://launchpadlibrarian.net/33774361/ProcModules.txt ** Attachment added: "UdevDb.txt" http://launchpadlibrarian.net/33774363/UdevDb.txt ** Attachment added: "UdevLog.txt" http://launchpadlibrarian.net/33774364/UdevLog.txt ** Attachment added: "WifiSyslog.txt" http://launchpadlibrarian.net/33774365/WifiSyslog.txt -- WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52 suspend_test_finish+0x7c/0x80() https://bugs.launchpad.net/bugs/452834 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 452834] [NEW] WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52 suspend_test_finish+0x7c/0x80()
Public bug reported: Apple MacBook Pro 4.1, when resuming after suspend. ProblemType: KernelOops Annotation: Your system might become unstable now and might need to be restarted. Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: duncan 1906 F pulseaudio /dev/snd/pcmC0D0p: duncan 1906 F...m pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0x9b50 irq 20' Mixer name : 'Realtek ALC889A' Components : 'HDA:10ec0885,106b3800,00100103' Controls : 33 Simple ctrls : 19 Date: Fri Oct 16 08:42:28 2009 DistroRelease: Ubuntu 9.10 Failure: oops HibernationDevice: RESUME=UUID=3db3a6f0-89a5-4fc3-b177-c7683daca398 MachineType: Apple Inc. MacBookPro4,1 NonfreeKernelModules: wl nvidia Package: linux-image-2.6.31-14-generic 2.6.31-14.46 ProcCmdLine: root=UUID=ed31f11b-2aa0-43fb-bd89-1473a3200225 ro quiet splash ProcVersionSignature: Ubuntu 2.6.31-14.46-generic RelatedPackageVersions: linux-firmware 1.22 RfKill: 1: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux Tags: kernel-oops Title: WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52 suspend_test_finish+0x7c/0x80() Uname: Linux 2.6.31-14-generic x86_64 dmi.bios.date: 02/27/08 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP41.88Z.00C1.B03.0802271651 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F42C89C8 dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 2 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F42C89C8 dmi.modalias: dmi:bvnAppleInc.:bvrMBP41.88Z.00C1.B03.0802271651:bd02/27/08:svnAppleInc.:pnMacBookPro4,1:pvr1.0:rvnAppleInc.:rnMac-F42C89C8:rvrPVT:cvnAppleInc.:ct2:cvrMac-F42C89C8: dmi.product.name: MacBookPro4,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-kerneloops kernel-oops -- WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52 suspend_test_finish+0x7c/0x80() https://bugs.launchpad.net/bugs/452834 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 452057] Re: Document Viewer won't print DVI files, but prints .pdf files with no trouble.
Apparmor stops evince from running the helper program /usr/bin/dvipdfm, which evince uses when printing dvi files. Here's the apparmor audit line from dmesg: type=1503 audit(1255613594.858:24): operation="exec" pid=2889 parent=2876 profile="/usr/bin/evince" requested_mask="::x" denied_mask="::x" fsuid=1000 ouid=0 name="/usr/bin/dvipdfm" The result is that it is no longer possible to print dvi files. Presumably the apparmor profile for evince should be taught that running /usr/bin/dvipdfm is ok. -- Document Viewer won't print DVI files, but prints .pdf files with no trouble. https://bugs.launchpad.net/bugs/452057 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 419081] [NEW] [PATCH] wrong parameter quoting in diversion of start-stop-daemon
Public bug reported: The ltsp-server package diverts (in the client chroot) /sbin/start-stop-daemon to /sbin/start-stop-daemon.real. The new start-stop-daemon is a simple wrapper that calls start-stop-daemon.real if LTSP_HANDLE_DAEMONS is not set to false. Unfortunately the wrapper passes on the parameters using $*, which doesn't handle quoted parameters correctly. I noticed this because /etc/cron.daily/man-db does start-stop-daemon --start --pidfile /dev/null --startas /bin/sh \ --oknodo --chuid man -- -c \ "find /var/cache/man -type f -name '*.gz' -atime +6 -print0 | \ xargs -r0 rm -f" and the find-piped-to-xargs part gets expanded to the wrong thing by the start-stop-daemon wrapper, causing the contents of the entire root filesystem to be dumped to the output. This can be easily fixed as follows: --- /usr/share/ltsp/scripts/start-stop-daemon.orig 2009-08-26 09:35:44.0 +0200 +++ /usr/share/ltsp/scripts/start-stop-daemon 2009-08-26 09:35:57.0 +0200 @@ -4,5 +4,5 @@ # if [ "$LTSP_HANDLE_DAEMONS" != "false" ]; then -/sbin/start-stop-daemon.real $* +/sbin/start-stop-daemon.real "$@" fi ** Affects: ltsp (Ubuntu) Importance: Undecided Status: New -- [PATCH] wrong parameter quoting in diversion of start-stop-daemon https://bugs.launchpad.net/bugs/419081 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 220219] Re: hardy rc install fails to boot on macbook pro
I just installed karmic alpha 2 on this same laptop. It looks like the original fatal problem (2) is fixed. The installer crashed after update-grub failed with error 1. However after running update-grub by hand the machine could boot fine. With Hardy I couldn't get the machine to boot no matter what I did. I don't have any details on what went wrong with update-grub when run from the installer, since the installer didn't say, sorry. I also didn't try to reproduce problem (1). -- hardy rc install fails to boot on macbook pro https://bugs.launchpad.net/bugs/220219 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 294643] Re: ltsp-update-kernels removes all kernels from tftpboot dir if base is not /opt/ltsp
Still true in karmic. Here's the fix to ltsp-update-kernels:
@@ -145,7 +145,7 @@
for kernelpath in $(find $TFTPDIR/$TFTPBOOTDIR/$arch -name
'vmlinuz-*'); do
kernel=`basename $kernelpath`
version=${kernel##vmlinuz-}
-if [ ! -d /opt/ltsp/$arch/lib/modules/$version ]; then
+if [ ! -d $BASE/$arch/lib/modules/$version ]; then
echo "Removing $kernelpath"
removefiles
fi
--
ltsp-update-kernels removes all kernels from tftpboot dir if base is not
/opt/ltsp
https://bugs.launchpad.net/bugs/294643
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 209513] Re: After upgrade, "Update standard folders to current language" threatens to rename your home folder
After upgrading to karmic, I get the "Update standard folders to current language?" dialog with Current folder name = /home/duncan and New folder name = /home/duncan/Videos I had earlier changed the language to UK english. -- After upgrade, "Update standard folders to current language" threatens to rename your home folder https://bugs.launchpad.net/bugs/209513 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 369124] Re: heartbeat incompatible with drbd8-utils in jaunty
OK, here is a recipe to see this problem. I hope all the
steps are here!
(0) Install drbd8-utils and heartbeat.
(1) Create a fake disk
dd if=/dev/zero of=drbd_disk count=1M bs=1
losetup /dev/loop0 ./drbd_disk
(2) Create /etc/drbd.conf. I used:
global {
usage-count yes;
}
common {
protocol C;
}
resource r0 {
device/dev/drbd0;
meta-disk internal;
on maisy {
disk/dev/loop0;
address 192.168.0.4:7788;
}
on hazy {
disk/dev/loop0;
address 192.168.0.5:7788;
}
}
(3) Create the drbd disk:
drbdadm create-md r0
modprobe drbd
drbdadm attach r0
drbdadm syncer r0
drbdadm connect r0
mkfs.ext3 /dev/drbd0
(4) Turned off drbd: /etc/init.d/drbd stop
Stopped the drbd init script from running at startup (to avoid clashes
with heartbeat):
update-rc.d -f drbd remove
(5) Created /etc/ha.d/ha.cf, contents:
autojoin none
mcast eth2 239.0.0.43 694 1 0
warntime 5
deadtime 15
initdead 60
keepalive 2
node maisy
node hazy
crm yes
(6) Created an appropriate /etc/ha.d/authkeys file.
(7) Set up resources and constraints:
cibadmin -o resources -C -x resources.xml
cibadmin -o constraints -C -x constraints.xml
where these files contain:
resources.xml:
constraints.xml:
(8) Started heartbeat: /etc/init.d/heartbeat start
(9) Observed the following failure in the system logs:
May 4 15:09:11 maisy lrmd: [4150]: info: RA output:
(drbd_files:0:start:stdout)
May 4 15:09:11 maisy drbd[4491]: [4549]: DEBUG: r0 start: Module loaded.
May 4 15:09:11 maisy drbd[4491]: [4551]: DEBUG: r0: Calling drbdadm -c
/etc/drbd.conf state r0
May 4 15:09:11 maisy lrmd: [4150]: info: RA output:
(drbd_files:0:start:stderr) local: 586: state': bad variable name
May 4 15:09:11 maisy drbd[4491]: [4558]: ERROR: r0: Called drbdadm -c
/etc/drbd.conf state r0
May 4 15:09:11 maisy drbd[4491]: [4559]: ERROR: r0: Exit code 2
(10) Modified /usr/lib/ocf/resource.d/heartbeat/drbd to use "role"
rather than "state".
(11) Restarted heartbeat: /etc/init.d/heartbeat restart
(12) Observed that there is no longer such an error in the system logs:
May 4 15:28:06 maisy drbd[6359]: [6370]: DEBUG: r0: Calling drbdadm -c
/etc/drbd.conf role r0
May 4 15:28:06 maisy drbd[6359]: [6377]: DEBUG: r0: Exit code 0
May 4 15:28:06 maisy drbd[6359]: [6378]: DEBUG: r0: Command output:
Secondary/Unknown
--
heartbeat incompatible with drbd8-utils in jaunty
https://bugs.launchpad.net/bugs/369124
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 369124] Re: heartbeat incompatible with drbd8-utils in jaunty
Hi, I am now trying to come up with a simple recipe that will enable you to reproduce the problem. However, let me just point out that the current jaunty heartbeat sources has ./resources/OCF/drbd: DRBD_STATE=$(do_drbdadm state $RESOURCE) which results in the mentioned problematic output using jaunty drbdadm: $ sudo drbdadm state r0 'drbdadm state' is deprecated, use 'drbdadm role' instead. Primary/Unknown For the heartbeat developers it seems that the tricky question is how to use "state" or "role" depending on the installed drbd version. Ciao, Duncan. -- heartbeat incompatible with drbd8-utils in jaunty https://bugs.launchpad.net/bugs/369124 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 369124] Re: heartbeat incompatible with drbd8-utils in jaunty
Hi Andres, > So you are setting up MySQL with DRBD. the service I'm starting is not mysql, but otherwise it is essentially the same. Since the drbd disk isn't even considered for mounting, due to error output from drdbadm, it probably doesn't matter what service is started. > I'll try to reproduce this. > However, I've used this setup, and worked ok. Would you mind modying it > so it looks similar? I think you'll only need to add the > tag: > > > > > > > > > > > > > Thanks, I will experiment with it next week sometime. Ciao, Duncan. -- heartbeat incompatible with drbd8-utils in jaunty https://bugs.launchpad.net/bugs/369124 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 306165] Re: kmix main mute has no effect, unlike in alsamixer
Hi Harald, in jaunty it is slightly better. The mute button in the panel icon has no effect, however if you click the icon to get the full mixer window, then the mute button on Master works. Curiously, there is no volume slider in the icon, simply the word "speaker". Ciao, Duncan. -- kmix main mute has no effect, unlike in alsamixer https://bugs.launchpad.net/bugs/306165 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 369124] Re: heartbeat incompatible with drbd8-utils in jaunty
This is V2 (crm) style, set up following http://www.drbd.org/docs/about (Part IV, “DRBD-enabled applications”, section "Using DRBD in Heartbeat CRM-enabled clusters"). It's one drbd disk, and heartbeat simply mounts it. -- heartbeat incompatible with drbd8-utils in jaunty https://bugs.launchpad.net/bugs/369124 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 369124] [NEW] heartbeat incompatible with drbd8-utils in jaunty
Public bug reported: Binary package hint: heartbeat The version of drbd shipped with jaunty now outputs a warning when using "state" with drbdadm: 'drbdadm state' is deprecated, use 'drbdadm role' instead. Unfortunately when heartbeat sees this warning it thinks drbdadm has failed. The result is that heartbeat cannot be used with drbd in jaunty. There is a discussion on the heartbeat users list: http://www.gossamer-threads.com/lists/linuxha/users/54352 ** Affects: heartbeat (Ubuntu) Importance: Undecided Status: New -- heartbeat incompatible with drbd8-utils in jaunty https://bugs.launchpad.net/bugs/369124 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 264961] Re: GNU Binutils for Ubuntu, internal error, assign_file_positions_for_non_load_sections
I get this same error BFD: BFD (GNU Binutils for Ubuntu) 2.19.1 internal error, aborting at ../../bfd/elf.c line 4657 in assign_file_positions_for_non_load_sections BFD: Please report this bug. when running: /usr/bin/install -c -s -m 0755 /home/duncan/LLVM/llvm- objects/Release/bin/opt /usr/local/bin/opt I'm attaching the file /home/duncan/LLVM/llvm-objects/Release/bin/opt. ** Attachment added: "opt" http://launchpadlibrarian.net/24390921/opt -- GNU Binutils for Ubuntu, internal error, assign_file_positions_for_non_load_sections https://bugs.launchpad.net/bugs/264961 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 315912] Re: ata*: hard resetting link
I'm having a very similar problem:
Linux version 2.6.27-9-server (similar to original poster)
Ubuntu 8.10 (x86-64; same as original poster, except for 64 bit vs 32 bit)
16 SATA hard disks (WDC WD1500HLFS-0 Rev: 04.0; different disks to original
poster)
SCSI storage controller: Marvell Technology Group Ltd. MV88SX6081 8-port SATA
II PCI-X Controller (similar to original poster)
Doing raid5 (same as original poster).
Disabling the write cache (as suggested by original poster) also works for me.
Sample message from the logs:
ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x6 frozen
ata1.00: cmd 61/08:00:3f:75:77/00:00:11:00:00/40 tag 0 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata1.00: status: { DRDY }
ata1: hard resetting link
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata1.00: max_sectors limited to 256 for NCQ
ata1.00: max_sectors limited to 256 for NCQ
ata1.00: configured for UDMA/133
ata1: EH complete
sd 0:0:0:0: [sdc] 293046768 512-byte hardware sectors (150040 MB)
sd 0:0:0:0: [sdc] Write Protect is off
sd 0:0:0:0: [sdc] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support
DPO or FUA
--
ata*: hard resetting link
https://bugs.launchpad.net/bugs/315912
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 306165] [NEW] kmix main mute has no effect, unlike in alsamixer
Public bug reported: Binary package hint: kdemultimedia Description:Ubuntu 8.10 Release:8.10 If I click the kmix applet and try to unmute the main channel (called "Speaker"), then the tick disappears from the mute button, but sound is not unmuted. If I open the kmix mixer window, the Speaker channel is still shown as muted. I can toggle the muted button in the mixer window and it has no effect on the muted setting in the applet's menu; it also doesn't unmute sound. In alsamixer there is also a Speaker channel, and I can successfully mute/unmute sound using it. I systematically tried changing sound levels and muting/unmuting for all channels in kmix, and watching what happened in alsamixer. For all channels except Speaker any changes in kmix were immediately reflected in alsamixer. So it seems that only Speaker has a problem. Note that Speaker has no volume slider, it is only mute/unmute. Card: HDA Intel Chip: Realtek ALC889A $ kmix --version Qt: 4.4.3 KDE: 4.1.2 (KDE 4.1.2) KMix: 3.0 ** Affects: kdemultimedia (Ubuntu) Importance: Undecided Status: New -- kmix main mute has no effect, unlike in alsamixer https://bugs.launchpad.net/bugs/306165 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 220219] Re: hardy rc install fails to boot on macbook pro
> Since it's been a very long time since any additional info was added to > this bug, I'm just checking to see if this is still an issue, and find > out what additional work should be done on this bug. I'm afraid I can't help: I do not expect to do a clean install from CD on my macbook anytime soon. Sorry about that, Duncan. -- hardy rc install fails to boot on macbook pro https://bugs.launchpad.net/bugs/220219 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 279777] Re: [intrepid] xsane crashed with SIGSEGV (HP ScanJet 3800)
Vaguely similar problem here: xsane got itself into a strange state: preview window was blank (not the usual image and buttons) and left coloured dots as mouse was moved across it. This was after it failed to talk with the printer (HP PSC 750 printer + scanner) because it was being printed to. Attempting to press the "acquire preview button" (by guessing where it was) caused xsane to hang and finally crash after trying to close it. Restarting xsane and the printer did not help. Restarting the computer fixed the problem. -- [intrepid] xsane crashed with SIGSEGV (HP ScanJet 3800) https://bugs.launchpad.net/bugs/279777 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 248727] Re: Intrepid alpha-2: adept-notifier fails to launch adept-updater
> Your Adept isn't up to date. The latest version of Adept is 3.0~beta1. > the update removes most of the adept binaries because Adept manager, updater, > and installer all live in a single binary. adept_notifier has been replaced > with the update-notifier-kde package. You are correct: there seems to be a new adept available. "apt-get dist-upgrade" gives: The following packages have been kept back: adept gwenview However doing "apt-get install adept" does install the new version, removing a bunch of individual adept packages. I don't understand why dist-upgrade didn't do this though. -- Intrepid alpha-2: adept-notifier fails to launch adept-updater https://bugs.launchpad.net/bugs/248727 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 248727] Re: Intrepid alpha-2: adept-notifier fails to launch adept-updater
> This is a kdesudo problem that should be fixed by now. ;) I'm still seeing the same problem: clicking the icon saying that updated packages are available causes a window to turn up in the task bar for a split second before disappearing; .xsession-errors says "Could not find 'kdesu' executable." This is with up-to-date intrepid with kubuntu-desktop installed. $ adept_notifier -version Qt: 3.3.8b KDE: 3.5.10 Adept Notifier: 2.1 Cruiser $ kdesudo -version Qt: 4.4.1 KDE: 4.1.1 (KDE 4.1.1) KdeSudo: 3.1 This is on x86-64. -- Intrepid alpha-2: adept-notifier fails to launch adept-updater https://bugs.launchpad.net/bugs/248727 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 248727] Re: Intrepid alpha-2: adept-notifier fails to launch adept-updater
I get the same behaviour (clicking the icon saying that updated packages are available causes a window to turn up in the task bar for a split second before disappearing). In xsession-errors I get this line for every click: Could not find 'kdesu' executable. This is with an up-to-date intrepid. -- Intrepid alpha-2: adept-notifier fails to launch adept-updater https://bugs.launchpad.net/bugs/248727 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 244863] Re: grep -i does not work on Intrepid
*** This bug is a duplicate of bug 241990 *** https://bugs.launchpad.net/bugs/241990 > I should have said that this is a duplicate if and only if the -i > /--ignore-case option is broken when and only when your character > encoding is UTF-8: i.e. if you get the same results as Javier Noval in > bug 241990 comment 2: > > This case fails: > $ echo Y | LC_ALL=en_US.UTF-8 grep -i '[y]' > $ > > And this one works as expected: > $ echo Y | LC_ALL=C grep -i '[y]' > Y > $ > > But I’d be surprised if it’s a different bug! I get the same results here. -- grep -i does not work on Intrepid https://bugs.launchpad.net/bugs/244863 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 241990] [NEW] grep -i fails to work on intrepid
Public bug reported: Binary package hint: grep Hardy Heron (correct): $ echo A | grep -i a A Intrepid Ibis (wrong): $ echo A | grep -i a $ Same if you grep a file containing A. This is GNU grep 2.5.3. ** Affects: grep (Ubuntu) Importance: Undecided Status: New -- grep -i fails to work on intrepid https://bugs.launchpad.net/bugs/241990 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 220219] Re: hardy rc install fails to boot on macbook pro
** Attachment added: "lspci -vvnn" http://launchpadlibrarian.net/13848735/lspci-vvnn.log -- hardy rc install fails to boot on macbook pro https://bugs.launchpad.net/bugs/220219 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 220219] Re: hardy rc install fails to boot on macbook pro
** Attachment added: "dmesg" http://launchpadlibrarian.net/13848723/dmesg.log -- hardy rc install fails to boot on macbook pro https://bugs.launchpad.net/bugs/220219 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 220219] Re: hardy rc install fails to boot on macbook pro
** Attachment added: "/proc/version_signature" http://launchpadlibrarian.net/13848720/version.log -- hardy rc install fails to boot on macbook pro https://bugs.launchpad.net/bugs/220219 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 220219] Re: hardy rc install fails to boot on macbook pro
** Attachment added: "uname -a" http://launchpadlibrarian.net/13848545/uname-a.log -- hardy rc install fails to boot on macbook pro https://bugs.launchpad.net/bugs/220219 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 220219] Re: hardy rc install fails to boot on macbook pro
> If possible, could you look here to see if there is any further information > you could add for the developers? > https://wiki.ubuntu.com/KernelTeamBugPolicies#head-7c9e98e6569189358309145304b13711955aa3be > > This section in particular deals with gathering information at boot time. > https://wiki.ubuntu.com/KernelTeamBugPolicies#head-7f4ff7edd5c16604606f127412c80d5d13a647f1 Perhaps you have misunderstood: the machine fails to boot, not because of a kernel problem or a bootloader problem, but because the BIOS fails to find the bootloader in the first place! As mentioned in the bug report, gutsy installed fine, and upgraded perfectly to hardy. This shows that there is no problem with hardy's kernel or bootloader. It seems clear to me that there is something wrong with installation of grub in 8.04. In the "advanced" section of the installer you can see where it intends to install grub. I did take a peek and both gutsy and hardy were installing it to the same place (if I recall correctly, to (hd0) ). Note that the macpro has an unusual BIOS (EFI) and partition layout (GPT). Anyway, I will attach some info about the machine to the bug report. -- hardy rc install fails to boot on macbook pro https://bugs.launchpad.net/bugs/220219 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 220219] Re: hardy rc install fails to boot on macbook pro
Hi Jarlath, > Thanks for taking the time to report this bug and make ubuntu better. > Was this the live CD or the alternate CD you were using? it was the live CD ubuntu-8.04-rc-desktop-amd64.iso (md5sum 84bcc78154076ca4f2306319c73c186a). Best wishes, Duncan. -- hardy rc install fails to boot on macbook pro https://bugs.launchpad.net/bugs/220219 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 220219] [NEW] hardy rc install fails to boot on macbook pro
Public bug reported: I tried installing the ubuntu 8.04 64 bit hardy heron release candidate on a very recent macbook pro laptop (Santa Rosa). Two problems, one fatal, the other annoying: (1) Annoying problem: creating a swap partition blocked installation. I created two partitions, a ext3 partition mounted on /, and a 2GB swap partition. The installer happily formated the ext3 partition, but then gave an error saying it had failed to mount the swap partition (strange message: you do not mount swap partitions, you activate them). Both options "go back" and "continue" lead back to the partitioner. I worked around this by marking the swap partition as unused rather than swap, with the intention of setting it up by hand once the system was installed. (2) Fatal problem: the BIOS could not find a bootable partition. After the installation completed, the installer tried to reboot the laptop. However the machine failed to boot, with the BIOS complaining that it could not find a bootable partition. I played around with parted, setting bootable flags here and there, but couldn't get it to boot. I worked around this by installing the 64 bit version of ubuntu 7.10 (which did not have this booting problem or the swap problem) then upgrading to hardy heron. ** Affects: ubuntu Importance: Undecided Status: New -- hardy rc install fails to boot on macbook pro https://bugs.launchpad.net/bugs/220219 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 106139] Re: ata1.oo revalidation failed with 04/13 update
*** This bug is a duplicate of bug 106063 *** https://bugs.launchpad.net/bugs/106063 Me too. From the boot log (linux-image-2.6.20-14-generic, x86, acer laptop): ata1: PATA max UDMA/100 cmd 0x000101f0 ctl 0x000103f6 bmdma 0x00011860 irq 14 scsi0: ata_piix ata1.00: ata_hpa_resize1: sectors = 117210240, hpa_sectors = 16546944 ata1.00: ATA-6 HTS541060G9AT00, MB3OA60A, max UDMA/100 ata1.00: 117210240 sectors multi 16: LBA48 ata1.00: n_sectors mismatch 117210240 != 277611653397632 ata1.00: revalidation failed (errno=-19) ata1.00: limiting speed to UDMA/100: PIO3 ata1.00: failed to recover some devices, retrying in 5 seconds ata1.00: 117210240 sectors multi 16: LBA48 ata1.00: n_sectors mismatch 117210240 != 277611653397632 ata1.00: revalidation failed (errno=-19) ata1.00: disabled -- ata1.oo revalidation failed with 04/13 update https://bugs.launchpad.net/bugs/106139 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 69060] Re: Hibernates at 20% charge not 10%
I ran lshal once a minute until the laptop hibernated. I've attached the last four minutes. Oddly, the remaining charge percentage, which was slowly going down, neared 20% and then suddenly dropped down to 6%! Presumably this triggered the hibernation. ** Attachment added: "lshal at -4, -3, -2 and -1 minutes before hibernation" http://librarian.launchpad.net/4940433/lshal.tgz -- Hibernates at 20% charge not 10% https://launchpad.net/bugs/69060 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 69060] Hibernates at 20% charge not 10%
Public bug reported: With the latest edgy kde-guidance-powermanager my laptop hibernates when the battery charge is 20%. I think this is because powermanager thinks I have two batteries, though in fact there is only one physical battery slot. Probably it calculates that battery one with 20% charge and battery two at 0% charge means that charge is 10% of the total two battery charge (battery two doesn't actually exist, and can't exist). If so, maybe the logic should be changed to: hibernates when all batteries each have less than 10% charge. ** Affects: kde-guidance (Ubuntu) Importance: Undecided Status: Unconfirmed -- Hibernates at 20% charge not 10% https://launchpad.net/bugs/69060 -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 67081] Fix seems ok
> What is the level at this point in time? Is it below 50%? > guidance-power-manager has > CHARGE_LEVEL_THRESHOLD at 50%, which should prevent critical action if battery > level is above 50%. I think this is a bit high (5-15% might be more > appropriate), but I > would like to confirm that you were below 50% when this happened (so that we > know this threshold works). Yes, it seems it was below 50% (i.e. I wasn't able to get it to hibernate when the charge was more than 50%). Also, I tried the latest package, and it seems much better: even though the remaining time reported is often clearly bogus, I don't see warnings anymore with high charge levels. So thanks for fixing this! By the way, who is responsable for calculating the (bogus) remaining time? -- guidance-power-manager thinks battery is low way too early https://launchpad.net/bugs/67081 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 67081] lshal output
Here is the output of lshal. This is at 99% battery charge. A CD was newly inserted, and I notice that this caused guidance-power-manager to think there were only 8 minutes left (!) and issue a warning about low power. ** Attachment added: "lshal output" http://librarian.launchpad.net/4899140/lshal -- guidance-power-manager thinks battery is low way too early https://launchpad.net/bugs/67081 -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 67081] guidance-power-manager thinks battery is low way too early
Public bug reported: When running on battery power, guidance-power-manager warns that the battery is getting low when it is still 95% charged! Worse, it forces hibernation when the battery still has plenty of capacity left. Maybe it is confused by the fact that the laptop reports two battery slots, though only one is physically present, i.e. it is only possible to have one battery plugged in. klaptop didn't have this problem. I took a snapshot of /proc/acpi after the guidance-power-manager warning. Here's what was in /proc/acpi/battery: BAT1 alarm: unsupported present: yes design capacity: 4400 mAh last full capacity: 3211 mAh battery technology: rechargeable design voltage: 14800 mV design capacity warning: 250 mAh design capacity low: 100 mAh capacity granularity 1: 10 mAh capacity granularity 2: 25 mAh model number:01ZG serial number: battery type:LION OEM info:SMP present: yes capacity state: ok charging state: discharging present rate:0 mA remaining capacity: 3026 mAh present voltage: 9280 mV BAT2 present: no (alarm) present: no (info) present: no (state) Other info: Acer travelmate 800 lspci: 00:00.0 Host bridge: Intel Corporation 82855PM Processor to I/O Controller (rev 03) 00:01.0 PCI bridge: Intel Corporation 82855PM Processor to AGP Controller (rev 03) 00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 03) 00:1d.1 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 03) 00:1d.2 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 03) 00:1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 83) 00:1f.0 ISA bridge: Intel Corporation 82801DBM (ICH4-M) LPC Interface Bridge (rev 03) 00:1f.1 IDE interface: Intel Corporation 82801DBM (ICH4-M) IDE Controller (rev 03) 00:1f.3 SMBus: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller (rev 03) 00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 03) 00:1f.6 Modem: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Modem Controller (rev 03) 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon R250 Lf [FireGL 9000] (rev 01) 02:02.0 Ethernet controller: Broadcom Corporation BCM4401 100Base-T (rev 01) 02:04.0 Network controller: Intel Corporation PRO/Wireless LAN 2100 3B Mini PCI Adapter (rev 04) 02:06.0 CardBus bridge: O2 Micro, Inc. OZ711M1/MC1 4-in-1 MemoryCardBus Controller (rev 20) 02:06.1 CardBus bridge: O2 Micro, Inc. OZ711M1/MC1 4-in-1 MemoryCardBus Controller (rev 20) 02:06.2 System peripheral: O2 Micro, Inc. OZ711Mx 4-in-1 MemoryCardBus Accelerator 02:07.0 FireWire (IEEE 1394): Texas Instruments TSB43AB21 IEEE-1394a-2000 Controller (PHY/Link) ** Affects: kde-guidance (Ubuntu) Importance: Undecided Status: Unconfirmed -- guidance-power-manager thinks battery is low way too early https://launchpad.net/bugs/67081 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 51671] mkinitramfs should back up old initrd.img
Public bug reported: Currently mkinitramfs simply overwrites the existing initrd.img, without making a backup. Yesterday I upgraded initramfs-tools, which caused it to quietly create a new and broken initrd.img (why it was broken is another story). I discovered this on my next boot, which failed unpleasantly. [It was at first a surprise since, after all, I hadn't upgraded the kernel, so why should it fail all of a sudden?] But unfortunately I wasn't able to specify the old initrd.img in grub, because it had been deleted, replaced with the new broken one. Sitting there with a non booting system, it became very very clear to me that keeping a backup copy of the old initrd.img would be a very good thing to do! ** Affects: initramfs-tools (Ubuntu) Importance: Untriaged Status: Unconfirmed -- mkinitramfs should back up old initrd.img https://launchpad.net/bugs/51671 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
