[Bug 493399] [NEW] digikam: symbol lookup error: /usr/lib/libdigikamcore.so.1
Public bug reported: Binary package hint: digikam Cannot run digikam in lucid linux test system. Full error message: digikam: symbol lookup error: /usr/lib/libdigikamcore.so.1: undefined symbol: _ZN9QHashData13detach_helperEPFvPNS_4NodeEPvEPFvS1_Ei Description:Ubuntu lucid (development branch) Release:10.04 digikam: Installed: 2:1.0.0~beta6-1ubuntu2 Candidate: 2:1.0.0~beta6-1ubuntu2 Version table: *** 2:1.0.0~beta6-1ubuntu2 0 500 http://us.archive.ubuntu.com lucid/main Packages 100 /var/lib/dpkg/status ** Affects: digikam (Ubuntu) Importance: Undecided Status: New -- digikam: symbol lookup error: /usr/lib/libdigikamcore.so.1 https://bugs.launchpad.net/bugs/493399 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 415589] Re: g-p-m does not turn off the display after specified time-out
KDE turns screen off as expected; gnome-power-manager 2.27.92 does not on same machine. -- g-p-m does not turn off the display after specified time-out https://bugs.launchpad.net/bugs/415589 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 282214] Re: Nvidia does not work with Geforce 6100
Evidently FIXED for my system by 185.18.04. Will continue to test. -- Nvidia does not work with Geforce 6100 https://bugs.launchpad.net/bugs/282214 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 282214] Re: Nvidia does not work with Geforce 6100
Not fixed by 180.44. -- Nvidia does not work with Geforce 6100 https://bugs.launchpad.net/bugs/282214 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 305794] Re: kernel 2.6.28 fails to install
Is this a duplicate of bug #305706? -- kernel 2.6.28 fails to install https://bugs.launchpad.net/bugs/305794 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 305834] Re: Kernel 2.6.28-2-generic does not include 173.14.15 driver, 173.14.12 doesnt compile
Is this a duplicate of bug #305706? -- Kernel 2.6.28-2-generic does not include 173.14.15 driver, 173.14.12 doesnt compile https://bugs.launchpad.net/bugs/305834 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 305706] Re: [jaunty] nvidia 173.14.12 module fails to build with linux-image-2.6.28-2-generic
Same issue for me. I can install nvidia's 173.14.15 (from ftp://download.nvidia.com/XFree86/Linux-x86/173.14.15/) without a hitch and it runs fine. Is this just a matter of building the Ubuntu package using 173.14.15 instead of 173.14.12? Unfortunately, none of the newer drivers (including 177) are compatible with my on-board GPU. -- [jaunty] nvidia 173.14.12 module fails to build with linux-image-2.6.28-2-generic https://bugs.launchpad.net/bugs/305706 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 305706] Re: [jaunty] nvidia 173.14.12 module fails to build with linux-image-2.6.28-2-generic
Update: I cobbled together a nvidia-173-kernel-source package using the 173.14.15 beta package at: ftp://download.nvidia.com/XFree86/Linux-x86/173.14.15/NVIDIA-Linux-x86-173.14.15-pkg1.run It compiled via DKMS on a test machine without difficulty under kernel 2.6.28-4-generic. I wouldn't think of uploading this package because my packaging skills are rudimentary (I wouldn't trust this package any farther than I can throw it) but it was a proof of concept that if the package is built with the 173.14.15 beta it will build properly under DKMS. I can't install nvidia-glx-173 because of bug #308410. -- [jaunty] nvidia 173.14.12 module fails to build with linux-image-2.6.28-2-generic https://bugs.launchpad.net/bugs/305706 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 183456] Re: Trying to load a sf2 file with asfxload returns sfxload: no memory left
Is incomplete still appropriate for this bug? It is still present in current distributions, does not appear to be a duplicate, and should not be allowed to expire. ** Changed in: awesfx (Ubuntu) Status: Incomplete = New -- Trying to load a sf2 file with asfxload returns sfxload: no memory left https://bugs.launchpad.net/bugs/183456 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 183456] Re: Trying to load a sf2 file with asfxload returns sfxload: no memory left
Same here, identical setup to Marcus. -- Trying to load a sf2 file with asfxload returns sfxload: no memory left https://bugs.launchpad.net/bugs/183456 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 298552] [NEW] Unable to mount digital camera -- Error initializing camera: -53: Could not claim the USB device
*** This bug is a duplicate of bug 267238 *** https://bugs.launchpad.net/bugs/267238 Public bug reported: On Jaunty test system, could not mount USB digital camera -- received error message Error initializing camera: -53: Could not claim the USB device. I found that /etc/udev/rules.d/45-libgphoto2.rules was missing. I tried reinstalling libgphoto2-2 but the file was not installed (would this have been installed with a different package?). Downloaded extra copy from http://webs.ono.com/jesusvpct/45-libgphoto2.rules and the camera now mounts fine. ** Affects: libgphoto2 (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Unable to mount digital camera + Unable to mount digital camera -- Error initializing camera: -53: Could not claim the USB device ** This bug has been marked a duplicate of bug 267238 libgphoto2 missing udev rules? -- Unable to mount digital camera -- Error initializing camera: -53: Could not claim the USB device https://bugs.launchpad.net/bugs/298552 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 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
Adding ENV{DEVTYPE}==partition to line 59 of 60-persistent-
storage.rules was working until reboot. After reboot, the Add. Sense:
No additional sense information error has now recurred when the USB
drive is connected. I've verified that line 59 of the file still says
ENV{DEVTYPE}==partition, IMPORT{program}=vol_id --export $tempnode
Back to square one, I guess.
--
USB Hard Drive Not Accessible, vol_id hangs
https://bugs.launchpad.net/bugs/264789
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 264789] Re: USB Hard Drive Not Accessible
Fixed for me. -- USB Hard Drive Not Accessible https://bugs.launchpad.net/bugs/264789 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 282214] Re: Nvidia does not work with Geforce 6100
Is this the same bug being discussed over at nvidia in these threads? http://www.nvnews.net/vbulletin/showthread.php?t=116946 http://www.nvnews.net/vbulletin/showthread.php?t=115209 http://www.nvnews.net/vbulletin/showthread.php?t=114346 If so, see here for a very clumsy workaround: http://www.nvnews.net/vbulletin/showpost.php?p=1763467postcount=22 Basically, change xorg.conf to use vesa driver and start X, then change xorg.conf to use nvidia driver and restart X. I'm affected by this bug, but the workaround works for me. -- Nvidia does not work with Geforce 6100 https://bugs.launchpad.net/bugs/282214 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 264789] Re: USB Hard Drive Not Accessible
For me, the sudo rmmod ehci_hcd workaround listed above will stop the external drive and the error messages temporarily, but then the drive and messages restart after a brief delay. Apparently the module has not reloaded at this point, because repeating the command yields ERROR: Module ehci_hcd does not exist in /proc/modules Reloading the module with sudo modprobe ehci_hcd has no effect, but then unloading the module again will stop the drive and messages again temporarily. None of this allows me to actually mount the drive. -- USB Hard Drive Not Accessible https://bugs.launchpad.net/bugs/264789 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 273372] Re: USB Mass storage device sense error
Same problem here in Intrepid. USB external drive that worked fine under previous versions. At drive power on: [ 914.916077] usb 2-2: new high speed USB device using ehci_hcd and address 8 [ 915.089329] usb 2-2: configuration #1 chosen from 1 choice [ 915.106215] scsi8 : SCSI emulation for USB Mass Storage devices [ 915.123024] usb-storage: device found at 8 [ 915.123039] usb-storage: waiting for device to settle before scanning [ 920.121121] usb-storage: device scan complete [ 920.124114] scsi 8:0:0:0: Direct-Access ST312002 6A 8.01 PQ: 0 ANSI: 0 [ 920.192753] sd 8:0:0:0: [sdh] 234441649 512-byte hardware sectors (120034 MB) [ 920.197056] sd 8:0:0:0: [sdh] Write Protect is off [ 920.197073] sd 8:0:0:0: [sdh] Mode Sense: 03 00 00 00 [ 920.197078] sd 8:0:0:0: [sdh] Assuming drive cache: write through [ 920.200621] sd 8:0:0:0: [sdh] 234441649 512-byte hardware sectors (120034 MB) [ 920.209086] sd 8:0:0:0: [sdh] Write Protect is off [ 920.209103] sd 8:0:0:0: [sdh] Mode Sense: 03 00 00 00 [ 920.209108] sd 8:0:0:0: [sdh] Assuming drive cache: write through [ 920.210153] sdh: sdh1 [ 920.231119] sd 8:0:0:0: [sdh] Attached SCSI disk [ 920.233270] sd 8:0:0:0: Attached scsi generic sg9 type 0 [ 920.571207] sd 8:0:0:0: [sdh] Sense Key : No Sense [current] [ 920.571225] sd 8:0:0:0: [sdh] Add. Sense: No additional sense information [ 920.725607] sd 8:0:0:0: [sdh] Sense Key : No Sense [current] [ 920.725626] sd 8:0:0:0: [sdh] Add. Sense: No additional sense information [ 920.876208] sd 8:0:0:0: [sdh] Sense Key : No Sense [current] [ 920.876227] sd 8:0:0:0: [sdh] Add. Sense: No additional sense information [ 921.028211] sd 8:0:0:0: [sdh] Sense Key : No Sense [current] [ 921.028229] sd 8:0:0:0: [sdh] Add. Sense: No additional sense information The last two lines loop endlessly and the disk churns continuously. Unable to mount sdh or sdh1. Not recognized under lsusb or parted. Then at drive power down: [ 1066.328064] usb 2-2: reset high speed USB device using ehci_hcd and address 8 [ 1066.384097] usb 2-2: USB disconnect, address 8 [ 1066.391536] scsi 8:0:0:0: [sdh] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK,SUGGEST_OK [ 1066.391553] end_request: I/O error, dev sdh, sector 234441648 [ 1066.391561] __ratelimit: 137 callbacks suppressed [ 1066.391567] Buffer I/O error on device sdh, logical block 234441648 [ 1066.391633] Buffer I/O error on device sdh, logical block 234441648 [ 1066.391718] Buffer I/O error on device sdh, logical block 234441640 [ 1066.391735] Buffer I/O error on device sdh, logical block 234441641 [ 1066.391751] Buffer I/O error on device sdh, logical block 234441642 [ 1066.391766] Buffer I/O error on device sdh, logical block 234441643 [ 1066.391781] Buffer I/O error on device sdh, logical block 234441644 [ 1066.391796] Buffer I/O error on device sdh, logical block 234441645 [ 1066.391811] Buffer I/O error on device sdh, logical block 234441646 [ 1066.391827] Buffer I/O error on device sdh, logical block 234441647 -- USB Mass storage device sense error https://bugs.launchpad.net/bugs/273372 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 270732] Re: Xorg crashed with SIGSEGV
** Attachment added: Xorg log http://launchpadlibrarian.net/17634071/Xorg.0.log.old ** Attachment added: CoreDump.gz http://launchpadlibrarian.net/17634072/CoreDump.gz ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/17634073/Dependencies.txt ** Attachment added: LsMod.txt http://launchpadlibrarian.net/17634074/LsMod.txt ** Attachment added: LsPci.txt http://launchpadlibrarian.net/17634075/LsPci.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/17634076/ProcMaps.txt ** Attachment added: ProcStatus.txt http://launchpadlibrarian.net/17634077/ProcStatus.txt ** Attachment added: Registers.txt http://launchpadlibrarian.net/17634078/Registers.txt ** Attachment added: XorgConf.txt http://launchpadlibrarian.net/17634079/XorgConf.txt ** Attachment added: XorgLog.txt http://launchpadlibrarian.net/17634080/XorgLog.txt ** Attachment added: XorgLogOld.txt http://launchpadlibrarian.net/17634081/XorgLogOld.txt ** Attachment added: Xrandr.txt http://launchpadlibrarian.net/17634082/Xrandr.txt ** Attachment added: setxkbmap.txt http://launchpadlibrarian.net/17634083/setxkbmap.txt ** Attachment added: xdpyinfo.txt http://launchpadlibrarian.net/17634084/xdpyinfo.txt ** Visibility changed to: Public ** This bug is no longer flagged as a security issue ** Attachment removed: Xorg log http://launchpadlibrarian.net/17634071/Xorg.0.log.old -- Xorg crashed with SIGSEGV https://bugs.launchpad.net/bugs/270732 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 251314] Re: hardy-proposed: networking regression with linux-backports-modules-2.6.24-20.20
I also noted that linux-backports-modules-2.6.24-20-generic includes the following module: /2.6.24-20-generic/updates/compat-wireless-2.6/drivers/net/wireless/rt2x00/rt61pci.ko but that linux-backports-modules-2.6.24-20-rt does not appear to include this module. -- hardy-proposed: networking regression with linux-backports-modules-2.6.24-20.20 https://bugs.launchpad.net/bugs/251314 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
