[Bug 256429] Re: Intrepid regression: carriage-return required after finger scan
I took the suggestion and upgraded to fprint for a couple of months. It is a downgrade. pam_thinkfinger at least prompts sensibly when doing the gsudo-type things. pam_fprint just sits there stupidly and you have to guess when something is waiting for a fingerprint scan or password. Combine that with not being able to type the password while a scan is being requested and you have a pretty frustrating piece of software... :-( -- Intrepid regression: carriage-return required after finger scan https://bugs.launchpad.net/bugs/256429 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 356293] Re: iwlagn intrepid - disabling/enabling wireless freezes system for a few seconds (e.g. enable/disable using nm-applet)
This doesn't happen in Lucid... or other recent versions... -- iwlagn intrepid - disabling/enabling wireless freezes system for a few seconds (e.g. enable/disable using nm-applet) https://bugs.launchpad.net/bugs/356293 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 356293] Re: iwlagn intrepid - disabling/enabling wireless freezes system for a few seconds (e.g. enable/disable using nm-applet)
Cool. Given that the bug actually existed and that I now know how to update the status, I changed it to fix released. ;-) ** Changed in: linux (Ubuntu) Status: Invalid = Fix Released -- iwlagn intrepid - disabling/enabling wireless freezes system for a few seconds (e.g. enable/disable using nm-applet) https://bugs.launchpad.net/bugs/356293 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 256429] Re: Intrepid regression: carriage-return required after finger scan
Good to hear that it works for you too, Nate. Yeah, the documentation has changed its recommendation for modifying package versions for PPAs, so I followed the new recommendation. Older packagers from PPAs (such as Jon's will probably look newer). You should be able to install mine by doing something like: apt-get install libpam-thinkfinger=0.3+r118-0ubuntu4ppamartinmeltin5 \ libthinkfinger0=0.3+r118-0ubuntu4ppamartinmeltin5 \ thinkfinger-tools=0.3+r118-0ubuntu4ppamartinmeltin5 After that, if you remove the other PPA from your /etc/apt/sources.list.d/ (or wherever), future updates should work. -- Intrepid regression: carriage-return required after finger scan https://bugs.launchpad.net/bugs/256429 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 256429] Re: Intrepid regression: carriage-return required after finger scan
Packages containing the patch are in my PPA at: https://launchpad.net/~martin-meltin/+archive/ppa A quick test seems to show that these packages fix the problem. If others can install, test and confirm then perhaps someone will build an official package for lucid -- Intrepid regression: carriage-return required after finger scan https://bugs.launchpad.net/bugs/256429 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 256429] Re: Intrepid regression: carriage-return required after finger scan
The patch linked to in comment #83 works for me. I'm trying to build a version for my PPA... but I just need to wait for various build messes to complete... I tried doing something useful with the package versions... -- Intrepid regression: carriage-return required after finger scan https://bugs.launchpad.net/bugs/256429 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 261695] Re: pidgin crashes in libmeanwhile just after connecting
We've had a working patch since Hardy. Is there a chance that someone could pick it up so that we could have a working version in Lucid... or the next release? -- pidgin crashes in libmeanwhile just after connecting https://bugs.launchpad.net/bugs/261695 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 417589] Re: Nautilus memory leak on regular usage for long hours
** Changed in: nautilus (Ubuntu) Status: Fix Released = In Progress -- Nautilus memory leak on regular usage for long hours https://bugs.launchpad.net/bugs/417589 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 417589] Re: Nautilus memory leak on regular usage for long hours
I'm not sure if it is the right thing to do but I've just moved the state of this bug back to In Progress. I've been running Nautilus for over 2 months. It is using 1.4GB of virtual memory: USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND martins 2674 0.0 4.5 1515596 139560 ? Sl2009 60:00 nautilus There's still a leak. Nautilus was showing 4 folders. 3 were very simple and one is a fairly large tree of OGGs. For the most part, the windows for these folders have just been sitting there open with nothing happening - nothing complex going on. Back on 13 December, when Nautilus was started, my system was up-to-date and had been running for just a few minutes... If there are thoughts that this might be due to a large amount of unmapped memory: mart...@rover:~$ free total used free sharedbuffers cached Mem: 30876162476252 611364 0 74072 430908 -/+ buffers/cache:19712721116344 Swap: 390851218294522079060 mart...@rover:~$ killall nautilus mart...@rover:~$ free total used free sharedbuffers cached Mem: 30876162331620 755996 0 74156 433976 -/+ buffers/cache:18234881264128 Swap: 3908512 7047283203784 That is, killing nautilus freed over 1GB of swap. Starting it again has it using ~100MB of virtual memory: USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND martins 6674 4.3 1.1 107728 35140 ?Sl 13:18 0:03 nautilus --no-desktop /home/martins This is while displaying the more complex folder containing OGGs. It certainly looks like in December there was still a serious leak in Nautilus. -- Nautilus memory leak on regular usage for long hours https://bugs.launchpad.net/bugs/417589 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 335394] Re: gnokii crashes with stack smashing detected error
0.6.27 is in Karmic so this could be closed. -- gnokii crashes with stack smashing detected error https://bugs.launchpad.net/bugs/335394 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 501990] [NEW] Disable touchpad while typing option causes disabled touchpad to be re-enabled
Public bug reported: Binary package hint: gnome-control-center In Ubuntu 9.10 (Karmic Koala) the Disable touchpad while typing option causes an otherwise disabled touchpad to be re-enabled after typing ceases. The expected behaviour is that a disabled touchpad stays disabled until it is explicitly re-enabled. To reproduce: 1. Enable the Disable touchpad while typing option in Properties - Mouse - Touchpad. 2. Disable the touchpad via the ACPI hotkey (Fn-F8 on my ThinkPad); or xinput set-int-prop SynPS/2 Synaptics TouchPad Synaptics Off 8 1 3. Type. 4. Stop typing: the touchpad has been enabled again. Disabling the Disable touchpad while typing option stops the touchpad from being re-enabled. This is a workaround. Another workaround is to completely disable the device by doing something like: xinput set-int-prop SynPS/2 Synaptics TouchPad Device Enabled 8 0 This seems to stop the above option in its tracks. The real fix would seem to be to have the Disable touchpad while typing option respect the Synaptics Off setting. The bug is in gnome-mouse-properties from: gnome-control-center: Installed: 1:2.28.1-0ubuntu1 ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- Disable touchpad while typing option causes disabled touchpad to be re-enabled https://bugs.launchpad.net/bugs/501990 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 359975] Re: evince sometimes yield error Error printing: Too many failed attempts
Does this also mean the bug is now as unlikely to be fixed in karmic as it was in jaunty? This means that novice users will be going for a whole year potentially unable to print PDFs. That's a disaster. :-( -- evince sometimes yield error Error printing: Too many failed attempts https://bugs.launchpad.net/bugs/359975 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 359975] Re: evince sometimes yield error Error printing: Too many failed attempts
This is sounding a little too much like a flame war. This is a bug report not a place to argue. Can people please find a better place to have their arguments? ;-) -- evince sometimes yield error Error printing: Too many failed attempts https://bugs.launchpad.net/bugs/359975 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 355998] Re: usb-storage: waiting for device to settle before scanning
That's great news, kbrock... you're welcome! -- usb-storage: waiting for device to settle before scanning https://bugs.launchpad.net/bugs/355998 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 355998] Re: usb-storage: waiting for device to settle before scanning
kbrock, the patch works with my v1, so I'm not sure what is happening with you. However, I'm running the version from my PPA rather than Michael Rooney's PPA. They should be the same though... Unsolved mystery... :-( -- usb-storage: waiting for device to settle before scanning https://bugs.launchpad.net/bugs/355998 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 355998] Re: usb-storage: waiting for device to settle before scanning
kbrock, it certainly looks like you have mrooney's PPA version of the package installed, so the bug should be fixed. Is your Sansa e260 a v1 or v2? There are hints for how to tell the difference at: http://www.rockbox.org/twiki/bin/view/Main/SansaE200v2#How_to_identify_an_e200_v2 The current patch only affects v1 e260s. If you have a v2 then perhaps a similar patch will work? -- usb-storage: waiting for device to settle before scanning https://bugs.launchpad.net/bugs/355998 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 355998] Re: usb-storage: waiting for device to settle before scanning
kbrock, the problem is that the package didn't build. I'm not sure why... but my guess is that you've actually downloaded the source from the PPA, you're patching it and then the build process is failing to patch it again. Hard to be certain though... Let's focus on whether you have the binary package from the PPA correctly installed. What output do you see if you run the following? apt-cache policy libgphoto2-2 -- usb-storage: waiting for device to settle before scanning https://bugs.launchpad.net/bugs/355998 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 355998] Re: usb-storage: waiting for device to settle before scanning
kbrock, provided you've done the previous 2 steps in comment 12 (apt-get source libgphoto2-2, wget ...) then the patch line should apply without any problems - you need to be in the directory containing the libgphoto2-2.4.2 subdirectory. It shouldn't make any difference but the only lines you need a sudo command for would be the the 1st 2 apt-get commands and the final dpkg commands - it is best to do as many steps as possible as you instead of as root. If you want to retry then I'd suggest rm -r libgphoto* ... probably with sudo if the only files and directories are hanging around. :-) Note that the very 1st apt-get command probably won't work. There is no package called debuild. You need devscripts instead because it contains the debuild command. That said, building a patched package will probably do you no more good than using a package from someone's PPA... So, when you say Have added Michael Rooney's PPA can you please explain the steps you did? After adding his PPA did you actually install the updated package from his PPA? :-) -- usb-storage: waiting for device to settle before scanning https://bugs.launchpad.net/bugs/355998 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 354264] Re: Imports all photos to the root of the home directory
Ummm... this is a regression that makes F-Spot close to useless for novice users... :-( I think the Ubuntu project needs a process that imports well tested fixes from individuals' PPAs. That would make this sort of thing easy to release a fix for... -- Imports all photos to the root of the home directory https://bugs.launchpad.net/bugs/354264 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 359975] Re: evince sometimes yield error Error printing: Too many failed attempts
Although comment #25 wasn't addressed to me... If this works sometimes and not others, I fail to see how it could be an authentication issue. Authentication isn't the sort of thing that comes and goes... :-) Note comment #15 where I observe that *no* network traffic is sent to the remote cups server. There's certainly no authentication issue there... -- evince sometimes yield error Error printing: Too many failed attempts https://bugs.launchpad.net/bugs/359975 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 359975] Re: evince sometimes yield error Error printing: Too many failed attempts
Well, that seems to remove any suggestion that this problem is HP- related or driver-related. The Lexmark X560n looks to be a Postscript printer: http://www.linuxprinting.org/show_printer.cgi?recnum=Lexmark-X560n Not HP and no need for conversion from Postscript to some other wacky format... -- evince sometimes yield error Error printing: Too many failed attempts https://bugs.launchpad.net/bugs/359975 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 359975] Re: evince sometimes yield error Error printing: Too many failed attempts
I'm seeing this too on an up-to-date 32-bit Jaunty install. Printing works sometimes. Other times, even printing the same PDF from evince it fails and I see errors like this in /var/log/cups/error_log: E [28/Jul/2009:08:45:20 +1000] cupsdReadClient: 10 IPP Read Error! When printing I run wireshark and I see *no* network traffic (except some unrelated broadcasts - definitely unrelated, they're for my Squeezebox). That's very weird considering it is meant to be an IPP error! /var/log/lpr.log seems to contain this sort of thing regardless of whether the job prints: Jul 28 09:15:58 hobo foo2hp2600-wrapper: foo2hp2600-wrapper -z1 -b1 -c -p9 -m1 -s7 -ol -d1 -Ghpclj2600n-1.icm Jul 28 09:16:05 hobo foo2hp2600-wrapper: gs -sPAPERSIZE=a4 -g4960x7016 -r600x600 -sDEVICE=bitcmyk -dCOLORSCREEN -dMaxBitmap=5 Jul 28 09:16:05 hobo foo2hp2600-wrapper: foo2hp -r600x600 -g4960x7016 -p9 -m1 -n1 -d1 -s7 -c -b1 -u 88x84 -l 88x84 -B -A There's plenty of disk space for the spooled job - nearly 6GB free. Here's a description of my configuration: * I export *raw* printer queues via IPP from a box running Debian stable. The box isn't powerful enough to run the required filters to avoid this. * I configure the printer on the client manually. The DeviceURI looks like this: DeviceURI ipp://slinky.ainslie.meltin.net:631/printers/beagle The printer uses this PPD file: ---8---8---8---8---8---8---8---8---8---8 *FormatVersion: 4.3 *FileVersion: 1.1 *LanguageVersion: English *LanguageEncoding: ISOLatin1 *PCFileName:FOO2HP.PPD *Manufacturer: HP *Product: (HP Color LaserJet 1600) *cupsVersion: 1.0 *cupsManualCopies: True *cupsModelNumber: 2 *cupsFilter: application/vnd.cups-postscript 100 foomatic-rip *cupsFilter: application/vnd.cups-pdf 0 foomatic-rip *%pprRIP:foomatic-rip other *ModelName: HP Color LaserJet 1600 *ShortNickName: HP Color LaserJet 1600 foo2hp *NickName: HP Color LaserJet 1600 Foomatic/foo2hp (recommended) ---8---8---8---8---8---8---8---8---8---8 I've tried switching to the very similar HP Color LaserJet CP1215 PPD file (since the printer is actually a CP1215) but the same amount of random failure occurs. :-( Is anyone seeing this bug with anything other than an HP printer? I wonder if foo2hp is randomly segv-ing... although there's nothing in any logs to suggest this... Can you please consider increasing the importance of this bug? Not being able to print seems like a pretty serious issue... -- evince sometimes yield error Error printing: Too many failed attempts https://bugs.launchpad.net/bugs/359975 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 356248] Re: [i946GZ] X gets stuck in D-wait state at logout
I don't think I've seen this particular bug since upgrading to Jaunty. That said, I've also switched to the -generic kernel from the -rt one for most uses... and have seem a big improvement in stability. -- [i946GZ] X gets stuck in D-wait state at logout https://bugs.launchpad.net/bugs/356248 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 355998] Re: usb-storage: waiting for device to settle before scanning
paulderol, what solution worked for you? What reverts when you do a full update? -- usb-storage: waiting for device to settle before scanning https://bugs.launchpad.net/bugs/355998 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 355998] Re: usb-storage: waiting for device to settle before scanning
OK, here's some better testing from me... I used a different Ubuntu 9.04 32-bit system where I hadn't tested this before. It has this sort of USB interface: 00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 01) The system is running up-to-date Jaunty with this kernel: Linux spot 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009 i686 GNU/Linux My Sansa e260 has an extra 8GB Micro SDHC card. It is running the old bootloader that boots into the original Sansa firmware when the device is off and then the USB is plugged in. It is also running Rockbox r20338-090317 - yes, that's from March... but it works... ;-) For each state of my Ubuntu system (see below) I did 2 tests: 1. From e260 off: With the e260's power off, I plugged in the USB cable and let the device boot into the original Sansa firmware. The expected result is that the filesystem on the built-in 4GB flash storage is mounted. 2. From e260 on: With the e260's power on, running Rockbox, I plugged in the USB cable and Rockbox detected the USB connection. The expected result is that the filesystems on both the built-in 4GB flash storage and the additional 8GB Micro SDHC card are separately mounted. That is, I should see 2 mounted filesystems. Tests: 1. Standard Jaunty system with no PPA packages. Both tests fail. I don't see any log messages after: usb-storage: waiting for device to settle before scanning 2. Jaunty system with my PPA packages, before reboot. Both tests pass - both filesystems are mounted. 3. Jaunty system with my PPA packages, after reboot. Both tests pass - both filesystems are mounted. Notes: * I'm running 32-bit Jaunty. * I have not attempted to apply any other fixes for this bug including configuration hacks involving modifications to or removal of: /usr/share/hal/fdi/preprobe/10osvendor/20-libgphoto2.fdi Logs for a successful test from e260 on look like this: [ 135.287119] usb-storage: waiting for device to settle before scanning [ 140.286255] usb-storage: device scan complete [ 140.288490] scsi 4:0:0:0: Direct-Access Rockbox Internal Storage 0.00 PQ: 0 ANSI: 4 [ 140.291855] scsi 4:0:0:1: Direct-Access Rockbox SD Card Slot 0.00 PQ: 0 ANSI: 4 [ 140.299720] sd 4:0:0:0: [sdf] 7854080 512-byte hardware sectors: (4.02 GB/3.74 GiB) [ 140.303079] sd 4:0:0:0: [sdf] Write Protect is off [ 140.303083] sd 4:0:0:0: [sdf] Mode Sense: 0b 00 00 08 [ 140.303085] sd 4:0:0:0: [sdf] Assuming drive cache: write through [ 140.313204] sd 4:0:0:0: [sdf] 7854080 512-byte hardware sectors: (4.02 GB/3.74 GiB) [ 140.316592] sd 4:0:0:0: [sdf] Write Protect is off [ 140.316596] sd 4:0:0:0: [sdf] Mode Sense: 0b 00 00 08 [ 140.316600] sd 4:0:0:0: [sdf] Assuming drive cache: write through [ 140.316607] sdf: sdf1 sdf2 [ 140.322322] sd 4:0:0:0: [sdf] Attached SCSI removable disk [ 140.322426] sd 4:0:0:0: Attached scsi generic sg6 type 0 [ 140.327849] sd 4:0:0:1: [sdg] 15523840 512-byte hardware sectors: (7.94 GB/7.40 GiB) [ 140.332506] sd 4:0:0:1: [sdg] Write Protect is off [ 140.332510] sd 4:0:0:1: [sdg] Mode Sense: 0b 00 00 08 [ 140.332513] sd 4:0:0:1: [sdg] Assuming drive cache: write through [ 140.344710] sd 4:0:0:1: [sdg] 15523840 512-byte hardware sectors: (7.94 GB/7.40 GiB) [ 140.350346] sd 4:0:0:1: [sdg] Write Protect is off [ 140.350352] sd 4:0:0:1: [sdg] Mode Sense: 0b 00 00 08 [ 140.350356] sd 4:0:0:1: [sdg] Assuming drive cache: write through [ 140.350364] sdg: sdg1 [ 140.365065] sd 4:0:0:1: [sdg] Attached SCSI removable disk [ 140.365172] sd 4:0:0:1: Attached scsi generic sg7 type 0 I wonder what's different about other people's configurations, apart from one failure occurring on a 64-bit system? -- usb-storage: waiting for device to settle before scanning https://bugs.launchpad.net/bugs/355998 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 355998] Re: usb-storage: waiting for device to settle before scanning
One interesting thing I haven't mentioned so far: my e260 is a v1. Are people who are still having problems using a v1 or v2? I've assumed v1 because people mention Rockbox... but I think Rockbox now (partially?) runs on v2. -- usb-storage: waiting for device to settle before scanning https://bugs.launchpad.net/bugs/355998 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 355998] Re: usb-storage: waiting for device to settle before scanning
It would be interesting if it matters... but my testing was only done on Ubuntu 9.04 32-bit. If anyone else tests the version from my PPA can they please post a comment? -- usb-storage: waiting for device to settle before scanning https://bugs.launchpad.net/bugs/355998 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 355998] Re: usb-storage: waiting for device to settle before scanning
I applied the patch in comment 10 https://bugs.launchpad.net/ubuntu/+source/libgphoto2/+bug/355998/comments/10 the quickest way possible (i.e. applied it to the source rather than integrating it into debian/patches/) and put the result in my PPA: https://launchpad.net/~martin-meltin/+archive/ppa I've tested it exactly once and it worked. ;-) -- usb-storage: waiting for device to settle before scanning https://bugs.launchpad.net/bugs/355998 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 355998] Re: usb-storage: waiting for device to settle before scanning
Oh, if it matters, my test was with rockbox firmware on a Sansa e260. -- usb-storage: waiting for device to settle before scanning https://bugs.launchpad.net/bugs/355998 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 121165] Re: /dev/.initramfs/progress_state is corrupted at shutdown
I don't think I've seen this problem since Gutsy. I think it was a race connected to the evms-induced double swap bug. evms seems to be gone and I don't think feisty is supported anymore, so I think this should be closed. -- /dev/.initramfs/progress_state is corrupted at shutdown https://bugs.launchpad.net/bugs/121165 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 269155] Re: Pathological crash on startup
I see this too in Jaunty: pathological: Installed: 1.1.3-8ubuntu2 Candidate: 1.1.3-8ubuntu2 Version table: *** 1.1.3-8ubuntu2 0 500 http://proxy jaunty/universe Packages 100 /var/lib/dpkg/status As mentioned above, turning off music and sound effects stops the crash. Running under gdb, I end up with this: (gdb) bt #0 0xb7713dde in pt_UpdateVoices () from /usr/lib/libmikmod.so.2 #1 0xb7715973 in Player_HandleTick () from /usr/lib/libmikmod.so.2 #2 0xb772024b in VC2_WriteSamples () from /usr/lib/libmikmod.so.2 #3 0xb7721e72 in VC2_WriteBytes () from /usr/lib/libmikmod.so.2 #4 0xb7722055 in VC_WriteBytes () from /usr/lib/libmikmod.so.2 #5 0xb773a2d2 in music_mixer () from /usr/lib/libSDL_mixer-1.2.so.0 #6 0xb7737c3b in ?? () from /usr/lib/libSDL_mixer-1.2.so.0 #7 0xb7b3ace2 in ?? () from /usr/lib/libSDL-1.2.so.0 #8 0xb7b4283b in ?? () from /usr/lib/libSDL-1.2.so.0 #9 0xb7b9071d in ?? () from /usr/lib/libSDL-1.2.so.0 #10 0xb80464ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #11 0xb7f7c49e in clone () from /lib/tls/i686/cmov/libc.so.6 So it definitely looks to be sound related. I notice that a couple of other SDL games (supertux2 - binary) and frozen-bubble (perl) work fine... so I wonder if there's a problem with python-pygame? Or perhaps it is specific to pathological? -- Pathological crash on startup https://bugs.launchpad.net/bugs/269155 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 261695] Re: pidgin crashes in libmeanwhile just after connecting
I doubt that most people here have a Windows machine! This bug has been reported against the Ubuntu Linux distribution. 2 options: * Pull the relevant parts out of this patch: http://ppa.launchpad.net/martin- meltin/ppa/ubuntu/pool/main/m/meanwhile/meanwhile_1.0.2-4~ppa4.jaunty.diff.gz (or grab the patches from elsewhere) and compile a new version yourself. * Search in Windows-specific forums to see if anyone else has built a patched version. Good luck! :-) -- pidgin crashes in libmeanwhile just after connecting https://bugs.launchpad.net/bugs/261695 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 373202] [NEW] When no photos are displayed, clicking on timeline crashes f-spot
Public bug reported: Binary package hint: f-spot In 8.10 (Intrepid), f-spot 0.5.0.3-0ubuntu4 can be made to crash as follows: 1. Double-click a tag to show only photos with that tag. 2. Select another tag that has no photos in common with the first tag and drag this tag onto the other tag in the search bar so that only photos with both tags (i.e. no photos!) are displayed. 3. Click on the timeline. This seems to reliably crash f-spot. I'm told that this still happens in 9.04 (Jaunty) Here's the backtrace: Exception in Gtk# callback delegate Note: Applications can use GLib.ExceptionManager.UnhandledException to handle the exception. System.IndexOutOfRangeException: Array index is out of range. at FSpot.PhotoQuery+PhotoCache.Get (Int32 index) [0x0] at FSpot.PhotoQuery.get_Item (Int32 index) [0x0] at FSpot.PhotoQuery.LookupItem (DateTime date, Boolean asc) [0x0] at FSpot.PhotoQuery.LookupItem (DateTime date) [0x0] at FSpot.TimeAdaptor.SetGlass (Int32 min) [0x0] at FSpot.GroupSelector+Glass.PositionChanged () [0x0] at FSpot.GroupSelector+Manipulator.SetPosition (Int32 position, Boolean update) [0x0] at FSpot.GroupSelector+Manipulator.SetPosition (Int32 position) [0x0] at FSpot.GroupSelector.OnButtonPressEvent (Gdk.EventButton args) [0x0] at Gtk.Widget.buttonpressevent_cb (IntPtr widget, IntPtr evnt) [0x0] at GLib.ExceptionManager.RaiseUnhandledException(System.Exception e, Boolean is_terminal) at Gtk.Widget.buttonpressevent_cb(IntPtr widget, IntPtr evnt) at Gtk.Widget.buttonpressevent_cb(IntPtr , IntPtr ) at Gtk.Application.gtk_main() at Gtk.Application.gtk_main() at Gtk.Application.Run() at Gnome.Program.Run() at FSpot.Driver.Main(System.String[] args) ** Affects: f-spot (Ubuntu) Importance: Undecided Status: New -- When no photos are displayed, clicking on timeline crashes f-spot https://bugs.launchpad.net/bugs/373202 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 373202] Re: When no photos are displayed, clicking on timeline crashes f-spot
David, can you please post a recipe that includes a timeline click for crashing the Jaunty version? -- When no photos are displayed, clicking on timeline crashes f-spot https://bugs.launchpad.net/bugs/373202 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 261695] Re: pidgin crashes in libmeanwhile just after connecting
I've submitted a PPA build for the patched meanwhile for Jaunty. The x86_64 version is built but the i386 version is still sitting in the queue waiting to be built. I haven't had time to upgrade to Jaunty yet, so when these are built can someone please test them? I'll remove them if they're broken... Details at: https://launchpad.net/~martin-meltin/+archive/ppa Thanks... -- pidgin crashes in libmeanwhile just after connecting https://bugs.launchpad.net/bugs/261695 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 261695] Re: pidgin crashes in libmeanwhile just after connecting
The Hardy and Intrepid packages in my PPA mentioned in comment 9 have now been tested for nearly 6 months with no adverse effects... sorry, I guess I should have mentioned that earlier. -- pidgin crashes in libmeanwhile just after connecting https://bugs.launchpad.net/bugs/261695 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 356293] Re: iwlagn intrepid - disabling/enabling wireless freezes system for a few seconds (e.g. enable/disable using nm-applet)
Thanks for the suggestion! Unfortunately the version in linux-backports-modules-2.6.27-11-generic looks to be the same version as in the main kernel package: mart...@rover:~$ modinfo /lib/modules/2.6.27-11-generic/updates/iwlagn.ko | grep '^version:' version:1.3.27ks mart...@rover:~$ modinfo /lib/modules/2.6.27-11-generic/kernel/drivers/net/wireless/iwlwifi/iwlagn.ko | grep '^version:' version:1.3.27ks Is there a way of finding out if patches have been applied? -- iwlagn intrepid - disabling/enabling wireless freezes system for a few seconds (e.g. enable/disable using nm-applet) https://bugs.launchpad.net/bugs/356293 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 356248] [NEW] X gets stuck in D-wait state at logout
Public bug reported: Binary package hint: xorg On Ubuntu 8.10, attempting to logout from GNOME often leaves the X server stuck in a D-wait state: root 5096 1.7 0.9 25484 19660 tty7 Ds+ 14:29 8:25 /usr/X11R6/bin/X :0 -br -audit 0 -auth /var/lib/gdm/:0.Xauth -nolisten tcp vt7 The box has one of these: 00:02.0 VGA compatible controller: Intel Corporation 82946GZ/GL Integrated Graphics Controller (rev 02) I'm attaching Xorg.0.log, which hasn't had anything written to it since gdm start time. However, it does tell us that the version of xorg-server is 2:1.5.2-2ubuntu3.1. I also have this version of the intel driver installed: ii xserver-xorg-video-intel 2:2.4.1-1ubuntu10.4 X.Org X server -- Intel i8xx, i9xx display driver This is the latest version from intrepid-updates. My xorg.conf has no customisations - just a bunch of boring default sections. This setup worked fine under Ubuntu 8.04, although I had to add a custom modeline and Virtual config. However, none of that is in my current xorg.conf. ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 8.10 Package: xorg 1:7.4~5ubuntu3 ProcEnviron: LC_COLLATE=POSIX PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin LANG=en_AU.UTF-8 SHELL=/bin/bash ProcVersion: Linux version 2.6.27-3-rt (bui...@palmer) (gcc version 4.3.2 (Ubuntu 4.3.2-1ubuntu11) ) #1 PREEMPT RT Mon Oct 27 03:05:19 UTC 2008 SourcePackage: xorg Uname: Linux 2.6.27-3-rt i686 Xrandr: setxkbmap: xdpyinfo: xkbcomp: ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug -- X gets stuck in D-wait state at logout https://bugs.launchpad.net/bugs/356248 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 356248] Re: X gets stuck in D-wait state at logout
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/24865787/Dependencies.txt ** Attachment added: LsMod.txt http://launchpadlibrarian.net/24865788/LsMod.txt ** Attachment added: LsPci.txt http://launchpadlibrarian.net/24865789/LsPci.txt ** Attachment added: XorgConf.txt http://launchpadlibrarian.net/24865790/XorgConf.txt ** Attachment added: XorgLog.txt http://launchpadlibrarian.net/24865791/XorgLog.txt ** Attachment added: XorgLogOld.txt http://launchpadlibrarian.net/24865792/XorgLogOld.txt -- X gets stuck in D-wait state at logout https://bugs.launchpad.net/bugs/356248 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 356293] [NEW] nm-applet hangs X/GNOME on state change
Public bug reported: Under Ubuntu 8.10, when I right-click on nm-applet in the notification area and uncheck Enable Wireless, my mouse and keyboard often stop working until the Disconnected notification pop-up appears. Enabling Show seconds on the GNOME clock confirms that the entire X (or GNOME?) session is hung, since the seconds on the clock stop updating for a couple of seconds... and then catch-up when the hang is complete. What's more, if I'm using ogg123 to play some music then the music stops too. This suggests that something a little more insidious is going on. dmesg shows nothing obvious, so it isn't clear whether the culprit is nm-applet or the iwlagn driver. Here's the version information: # apt-cache policy network-manager-gnome network-manager-gnome: Installed: 0.7~~svn20081020t000444-0ubuntu1.8.10.2 Candidate: 0.7~~svn20081020t000444-0ubuntu1.8.10.2 Version table: *** 0.7~~svn20081020t000444-0ubuntu1.8.10.2 0 500 http://proxy.ainslie.meltin.net intrepid-security/main Packages 500 http://proxy.ainslie.meltin.net intrepid-updates/main Packages 100 /var/lib/dpkg/status 0.7~~svn20081020t000444-0ubuntu1 0 500 http://proxy.ainslie.meltin.net intrepid/main Packages ** Affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New -- nm-applet hangs X/GNOME on state change https://bugs.launchpad.net/bugs/356293 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 164006] Re: Tracker, wrong parameters for dcraw
Load average is the average number of runnable processes over a minute (or 5 minutes or 15 minutes). A load average of 50 is not a 50% load on the CPU. It is potentially a 5000% load on the CPU - since dcraw is likely doing something very CPU intensive it probably is a 5000% load. I'm running the latest version of tracker that is available in Intrepid: mart...@spot:~$ apt-cache policy tracker tracker: Installed: (none) Candidate: 0.6.6-1ubuntu5.1 Version table: 0.6.6-1ubuntu5.1 0 500 http://proxy intrepid-updates/main Packages 0.6.6-1ubuntu5 0 500 http://proxy intrepid/main Packages I imagine this version is supported. It suggests imagemagick as a dependency: mart...@spot:~$ apt-cache show tracker | grep imagemagick Suggests: imagemagick, evince, djvulibre-bin, gnumeric Suggests: imagemagick, evince, djvulibre-bin, gnumeric The bug is new in Intrepid. -- Tracker, wrong parameters for dcraw https://bugs.launchpad.net/bugs/164006 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 164006] Re: Tracker, wrong parameters for dcraw
Yeah, I too don't have thumbnailing enabled and tracker put the load average on my system up to about 50. For now I've told tracker to ignore *.CR2 files. Also, this is a regression - this didn't happen under Hardy. One question I have is why tracker runs so many dcraw/identify processes in parallel? If it ran 1 at a time then this wouldn't be a problem... but it takes serious effort (or carelessness) to get the load average up to 50! -- Tracker, wrong parameters for dcraw https://bugs.launchpad.net/bugs/164006 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 335394] [NEW] gnokii crashes with stack smashing detected error
Public bug reported: Binary package hint: gnokii When trying to write the phonebook of my Nokia 6233, gnokii (version 0.6.26.dfsg-3) fails with a stack smashing detected error, as shown at the end of this message. This has been reported upstream: http://savannah.nongnu.org/bugs/?23941 The main problem is that, at least for my phone, gnokii is, therefore, completely useless. The version in Hardy worked quite well. Although stack smashing is mentioned, I'm not sure this is a real security problem... unless you can be tricked into attempting to load a specially crafted gnokii address book listing... which seems pretty unlikely. peace happiness, martin mart...@rover:~$ lsb_release -rd Description:Ubuntu 8.10 Release:8.10 mart...@rover:~$ gnokii --writephonebook -o tmp/foo.gnokii GNOKII Version 0.6.26 *** stack smashing detected ***: gnokii terminated === Backtrace: = /lib/tls/i686/cmov/libc.so.6(__fortify_fail+0x48)[0xb7eea6d8] /lib/tls/i686/cmov/libc.so.6(__fortify_fail+0x0)[0xb7eea690] /usr/lib/libgnokii.so.3[0xb8020554] /usr/lib/libgnokii.so.3[0xb7ff734a] /usr/lib/libgnokii.so.3[0xb7ff80be] /usr/lib/libgnokii.so.3[0xb7fc2a27] /usr/lib/libgnokii.so.3(gn_gsm_initialise+0x205)[0xb7fc2c55] /usr/lib/libgnokii.so.3(gn_lib_phone_open+0x52)[0xb7fc26c2] gnokii[0x804acb9] gnokii[0x804bbc3] gnokii[0x804bc72] /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5)[0xb7e06685] gnokii[0x804aa91] === Memory map: 08048000-08066000 r-xp 08:01 57743 /usr/bin/gnokii 08066000-08067000 r--p 0001d000 08:01 57743 /usr/bin/gnokii 08067000-08068000 rw-p 0001e000 08:01 57743 /usr/bin/gnokii 08068000-0806b000 rw-p 08068000 00:00 0 08bce000-08bef000 rw-p 08bce000 00:00 0 [heap] b7a38000-b7a45000 r-xp 08:01 573458 /lib/libgcc_s.so.1 b7a45000-b7a46000 r--p c000 08:01 573458 /lib/libgcc_s.so.1 b7a46000-b7a47000 rw-p d000 08:01 573458 /lib/libgcc_s.so.1 b7a5b000-b7a5c000 rw-p b7a5b000 00:00 0 b7a5c000-b7a9b000 r--p 08:01 378955 /usr/lib/locale/en_AU.utf8/LC_CTYPE b7a9b000-b7c9b000 r--p 08:01 568691 /usr/lib/locale/locale-archive b7c9b000-b7c9c000 rw-p b7c9b000 00:00 0 b7c9c000-b7ca r-xp 08:01 360841 /usr/lib/libXdmcp.so.6.0.0 b7ca-b7ca1000 rw-p 3000 08:01 360841 /usr/lib/libXdmcp.so.6.0.0 b7ca1000-b7ca2000 rw-p b7ca1000 00:00 0 b7ca2000-b7ca4000 r-xp 08:01 360837 /usr/lib/libXau.so.6.0.0 b7ca4000-b7ca5000 rw-p 1000 08:01 360837 /usr/lib/libXau.so.6.0.0 b7ca5000-b7ca7000 r-xp 08:01 573681 /lib/tls/i686/cmov/libdl-2.8.90.so b7ca7000-b7ca8000 r--p 1000 08:01 573681 /lib/tls/i686/cmov/libdl-2.8.90.so b7ca8000-b7ca9000 rw-p 2000 08:01 573681 /lib/tls/i686/cmov/libdl-2.8.90.so b7ca9000-b7cc r-xp 08:01 360845 /usr/lib/libxcb.so.1.0.0 b7cc-b7cc1000 r--p 00016000 08:01 360845 /usr/lib/libxcb.so.1.0.0 b7cc1000-b7cc2000 rw-p 00017000 08:01 360845 /usr/lib/libxcb.so.1.0.0 b7cc2000-b7cc3000 r-xp 08:01 367865 /usr/lib/libxcb-xlib.so.0.0.0 b7cc3000-b7cc4000 r--p 08:01 367865 /usr/lib/libxcb-xlib.so.0.0.0 b7cc4000-b7cc5000 rw-p 1000 08:01 367865 /usr/lib/libxcb-xlib.so.0.0.0 b7cc5000-b7cce000 r-xp 08:01 365843 /usr/lib/libpcsclite.so.1.0.0 b7cce000-b7ccf000 r--p 8000 08:01 365843 /usr/lib/libpcsclite.so.1.0.0 b7ccf000-b7cd rw-p 9000 08:01 365843 /usr/lib/libpcsclite.so.1.0.0 b7cd-b7cd1000 rw-p b7cd 00:00 0 b7cd1000-b7dbc000 r-xp 08:01 82024 /usr/lib/libX11.so.6.2.0 b7dbc000-b7dbd000 r--p 000ea000 08:01 82024 /usr/lib/libX11.so.6.2.0 b7dbd000-b7dbf000 rw-p 000eb000 08:01 82024 /usr/lib/libX11.so.6.2.0 b7dbf000-b7dc rw-p b7dbf000 00:00 0 b7dc-b7dcf000 r-xp 08:01 364142 /usr/lib/libXpm.so.4.11.0 b7dcf000-b7dd rw-p f000 08:01 364142 /usr/lib/libXpm.so.4.11.0 b7dd-b7de5000 r-xp 08:01 366741 /usr/lib/libbluetooth.so.3.0.2 b7de5000-b7de6000 r--p 00014000 08:01 366741 /usr/lib/libbluetooth.so.3.0.2 b7de6000-b7de7000 rw-p 00015000 08:01 366741 /usr/lib/libbluetooth.so.3.0.2 b7de7000-b7ded000 r-xp 08:01 573723 /lib/libusb-0.1.so.4.4.4 b7ded000-b7dee000 r--p 5000 08:01 573723 /lib/libusb-0.1.so.4.4.4 b7dee000-b7df rw-p 6000 08:01 573723 /lib/libusb-0.1.so.4.4.4 b7df-b7f48000 r-xp 08:01 573665 /lib/tls/i686/cmov/libc-2.8.90.so b7f48000-b7f4a000 r--p 00158000 08:01 573665 /lib/tls/i686/cmov/libc-2.8.90.so b7f4a000-b7f4b000 rw-p 0015a000 08:01 573665 /lib/tls/i686/cmov/libc-2.8.90.so b7f4b000-b7f4e000 rw-p b7f4b000 00:00 0 b7f4e000-b7f92000 r-xp 08:01 361043 /usr/lib/libical.so.0.33.0 b7f92000-b7f9a000 r--p 00044000 08:01 361043 /usr/lib/libical.so.0.33.0 b7f9a000-b7f9b000 rw-p 0004c000 08:01 361043 /usr/lib/libical.so.0.33.0 b7f9b000-b7f9d000 rw-p b7f9b000 00:00 0
[Bug 335394] Re: gnokii crashes with stack smashing detected error
gnokii-0.6.27 is released and seems to fix this bug. This seems logical since the fix is noted in the upstream bug a couple of months before 0.6.27 was released. I've tested 0.6.27 by building packages using the debian/ subdirectory from the buggy version, with appropriate changelog change and a couple of hacks to get it to build. It works fine for updating the phonebook on my Nokia 6233. I haven't tested anything else... since I don't use gnokii for anything else, so I'm not really setup to test it and more than that... I guess Jaunty probably needs 0.6.27. -- gnokii crashes with stack smashing detected error https://bugs.launchpad.net/bugs/335394 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 261695] Re: pidgin crashes in libmeanwhile just after connecting
I have hardy and intrepid packages in my PPA. I've been testing the hardy one since yesterday with no problems, others are testing the intrepid package. Details at: https://launchpad.net/~martin-meltin/+archive -- pidgin crashes in libmeanwhile just after connecting https://bugs.launchpad.net/bugs/261695 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 261695] Re: pidgin crashes in libmeanwhile just after connecting
** Attachment added: meanwhile-mwSametimeList_get.patch http://launchpadlibrarian.net/17105590/meanwhile-mwSametimeList_get.patch -- pidgin crashes in libmeanwhile just after connecting https://bugs.launchpad.net/bugs/261695 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 261695] [NEW] pidgin crashes in libmeanwhile just after connecting
Public bug reported: Something seems to have changed on a Sametime server I use, causing pidgin to die in libmeanwhile just after establishing a connection. I see the problem in libmeanwhile1-1.0.2-3 in Ubunutu 8.04 (Hardy). Attached is a patch that fixes (or works around) the problem by avoiding a NULL-pointer dereference. ** Affects: meanwhile (Ubuntu) Importance: Undecided Status: New -- pidgin crashes in libmeanwhile just after connecting https://bugs.launchpad.net/bugs/261695 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 124518] Re: anacron prints spurious debug message
Thanks Andreas! That looks good... I would have submitted a patch but I wasn't sure whether to direct it to stderr, remove it altogether (as you've done) or something else... :-) -- anacron prints spurious debug message https://bugs.launchpad.net/bugs/124518 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 124518] Re: anacron prints spurious debug message
Hi Andreas,
Yes, it still happens:
$ /usr/sbin/anacron -s -d -q -t ${HOME}/etc/anacrontab -S
${HOME}/var/spool/anacron
Checking against 24 with 31
If I redirect the above to /dev/null then I don't see it, so the output
is definitely going to stdout.
peace happiness,
martin
--
anacron prints spurious debug message
https://bugs.launchpad.net/bugs/124518
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 183474] Re: iwl4965 can't reconnect if AP is lost and then comes back
I can confirm that I saw this problem regularly under Gutsy. -- iwl4965 can't reconnect if AP is lost and then comes back https://bugs.launchpad.net/bugs/183474 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 208467] Re: Camera Device button Open F-spot Photo Manager doesn't work
Import now works fine when a media card is inserted. This is on a fresh install of Hardy. Right-clicking on a folder in Nautilus and selecting F-spot Photo Manager still causes an attempt to import from a camera or media card. This seems wrong. However, it is easy to work around by selecting Import from the toolbar in F-spot and then finding the relevant folder. This is starting to look good. Thanks for the great work! :-) -- Camera Device button Open F-spot Photo Manager doesn't work https://bugs.launchpad.net/bugs/208467 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 197589] Re: Numeric keypad no longer works after upgrade
Didn't see this bug on: 1 laptop upgrade from Gutsy to Hardy and 1 laptop fresh install of Hardy. However, since you have to go to some effort to switch on numeric keyboard mode on laptops, that doesn't tell us much. :-( -- Numeric keypad no longer works after upgrade https://bugs.launchpad.net/bugs/197589 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 208467] Re: Camera Device button Open F-spot Photo Manager doesn't work
I haven't tried with a new user yet. Something is deciding to import the photos from the card instead of the directory I've selected in Nautilus. f-spot-import was my 1st guess since it contains some logic that tries to figure out where to import from. Sorry I haven't had time to debug this further. Will try to make time on the weekend. -- Camera Device button Open F-spot Photo Manager doesn't work https://bugs.launchpad.net/bugs/208467 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 208467] Re: Camera Device button Open F-spot Photo Manager doesn't work
I don't see the problem with importing from a media card fixed by this update. I upgraded these packages from proposed-updates: 2008-06-01 11:23:19 status installed gvfs 0.2.4-0ubuntu1 2008-06-01 11:23:20 status installed gvfs-backends 0.2.4-0ubuntu1 2008-06-01 11:23:20 status installed nautilus 1:2.22.3-0ubuntu2 2008-06-01 11:23:20 status installed libc6 2.7-10ubuntu3 2008-06-01 11:23:29 status installed desktop-file-utils 0.15-1ubuntu4 It doesn't look like the updated .desktop file got recognised since I still see 2 items labeled other F-Spot Photo Manager item in the Nautilus media preferences. Do I need to restart Nautilus (or logout/login)? If I select the other F-Spot Photo Manager item as Michael Ellerman suggests above, then things work as expected. However, 1 further problem is that if I select a folder containing photos, right-click and choose Open with F-Spot Photo Manager then the F-Spot import dialog opens and it tries to import the photos from the media card I still have mounted! Could this be because that item runs /usr/bin/f-spot-import rather than /usr/bin/f-spot --import? I haven't tried to track it down and am out of time for now... :-( -- Camera Device button Open F-spot Photo Manager doesn't work https://bugs.launchpad.net/bugs/208467 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 202717] Re: Can't open multiple files from File Browser in F-Spot Photo Viewer
Will there be a delay before this hits the hardy-proposed repository? I don't see it there yet... but then I haven't used -proposed before. Thanks! -- Can't open multiple files from File Browser in F-Spot Photo Viewer https://bugs.launchpad.net/bugs/202717 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 202717] Re: Can't open multiple files from File Browser in F-Spot Photo Viewer
OK, got it - approx was caching Packages.bz2 a little too aggressively. The version in hardy-proposed fixes this bug. I'll add some comments to bug #208467 about this release and importing photos. -- Can't open multiple files from File Browser in F-Spot Photo Viewer https://bugs.launchpad.net/bugs/202717 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 208467] Re: Camera Device button Open F-spot Photo Manager doesn't work
The new version of f-spot in hardy-updates (0.4.3.1-0ubuntu1) does not fix this bug - not surprising, since the bug is in nautilus... :-) Behaviour: * Inserting a media card from a camera still results in failure in the form of a usage message from f-spot. * Saying f-spot-import dir from the command-line results in f-spot opening and displaying a pop- up saying it couldn't find a camera attached. * Saying f-spot --import dir successfully imports photos. Not sure this is useful, but I thought it couldn't hurt... :-) -- Camera Device button Open F-spot Photo Manager doesn't work https://bugs.launchpad.net/bugs/208467 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 202717] Re: Can't open multiple files from File Browser in F-Spot Photo Viewer
I'm a surprised to see this tagged with Low importance. Given that F-spot gets its own page in the list of Hardy features http://www.ubuntu.com/products/whatisubuntu/804features/photos/ I would have thought the prominence of the package, and the availability of a fix, would make the importance higher? :-) -- Can't open multiple files from File Browser in F-Spot Photo Viewer https://bugs.launchpad.net/bugs/202717 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 140853] Re: F-spot crash on changing tag icon
For anyone stuck on gutsy, I've applied the above patch and built a version of the package in my PPA: https://launchpad.net/~martin-meltin/+archive I've tested the i386 version and it definitely fixes the problem. -- F-spot crash on changing tag icon https://bugs.launchpad.net/bugs/140853 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 202717] Re: Can't open multiple files from File Browser in F-Spot Photo Viewer
To ensure that the patch fixes the bug and so that I (and others) have a working version I've uploaded a patched version to my PPA at: https://launchpad.net/~martin-meltin/+archive You'll want the hardy version (my gutsy package for f-spot fixes a bug in the gutsy version). I've tested the i386 version and the bug is fixed. -- Can't open multiple files from File Browser in F-Spot Photo Viewer https://bugs.launchpad.net/bugs/202717 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 202717] Re: Can't open multiple files from File Browser in F-Spot Photo Viewer
This is fixed upstream: http://svn.gnome.org/viewvc/f-spot/trunk/src/main.cs?r1=3883r2=3882pathrev=3883 That patch applies with a bit of fuzz. I've attached a rediffed version that should apply with no fuzz. ** Attachment added: Rediffed, fuzzless patch to src/main.cs to allow multiple files/uris to --view. http://launchpadlibrarian.net/14376970/f-spot-0.4.2-view-multiple.patch -- Can't open multiple files from File Browser in F-Spot Photo Viewer https://bugs.launchpad.net/bugs/202717 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 208467] Re: Camera Device button Open F-spot Photo Manager doesn't work
The above patch is now even more dodgy, since https://bugs.launchpad.net/ubuntu/+source/f-spot/+bug/202717 is fixed upstream, so multiple files/uris to --view are supported again. I've attached a rediffed patch to that bug. However, the import via nautilus problem is still there.. so this bug can focus on fixing the interaction between nautilus and f-spot... and we can forget about other f-spot problems. ;-) I guess that nautilus just needs to be told to use f-spot --import when trying to import. I still don't know what tells nautilus how to call f-spot. If someone can tell me where that happens then I'll create a patch. -- Camera Device button Open F-spot Photo Manager doesn't work https://bugs.launchpad.net/bugs/208467 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 208467] Re: Camera Device button Open F-spot Photo Manager doesn't work
Yep, I agree with the last 2 comments. So, given that changes in argument handling for f-spot has caused 2 bugs (this one and https://bugs.launchpad.net/ubuntu/+source/f-spot/+bug/202717), it would make sense to return the argument handling to the old behavour. Since f-spot is a script, it seems that the old behaviour could be emulated there: * If the 1st arg is --import, then don't touch anything - assume sanity. * If the 1st and only arg is a directory and it is directly under /media, then add a --import * Otherwise, for each file:// arg, add a --view arg before it. Also, the existing line saying: for arg in $* ; do is also a bug. If someone passes a filename called foo --trace=bar.jpg then the wrong thing will happen - yes, that is unlikely but the fix is easy! The above should just be: for arg; do A patch that does all of the above is attached. I've patched /usr/bin/f-spot rather than the source file... however, if the patch is useful then it should be easy to apply to the source file. Some of the code is bash-specific - without bash I think all is lost, since bash arrays provide a way of maintaining filenames with whitespace in them. ... and yes... the way of done it is a little bit insane, but it works for all of my desired use cases so far... :-) ** Attachment added: Patch to /usr/bin/f-spot to fix popular use cases. http://launchpadlibrarian.net/14335464/f-spot.patch -- Camera Device button Open F-spot Photo Manager doesn't work https://bugs.launchpad.net/bugs/208467 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 208467] Re: Camera Device button Open F-spot Photo Manager doesn't work
By the way, the above doesn't seem to fix f-spot --view dir or f-spot --view file://dir, which seems broken either way. It works in the gutsy version and the documentation seems to suggest it should work. :-( -- Camera Device button Open F-spot Photo Manager doesn't work https://bugs.launchpad.net/bugs/208467 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 208467] Re: Camera Device button Open F-spot Photo Manager doesn't work
Just to double-check before I do this... In my case I'm not actually plugging in a camera. I'm inserting an SD card from a camera into a reader. I assume that this should behave similarly to a camera, but since this bug was initially concerned with actual cameras I thought I'd check before I take you too far off the track! :-) So, do the above but insert my SD card instead of plugging in a camera? Thanks... -- Camera Device button Open F-spot Photo Manager doesn't work https://bugs.launchpad.net/bugs/208467 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 197589] Re: Numeric keypad no longer works after upgrade
Sorry, that was a bit over the top, especially out of context... :-( I'll send you an email explaining my frustration - it doesn't belong in this bug report. So, you'd like to see the output of: gconftool-2 --get /desktop/gnome/accessibility/keyboard/mousekeys_enable before and after an upgrade to Hardy on a system where the bug occurs? If so, I'll do that on a laptop that I'll upgrade soon and see if the bug occurs after that upgrade... -- Numeric keypad no longer works after upgrade https://bugs.launchpad.net/bugs/197589 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 208467] Re: Camera Device button Open F-spot Photo Manager doesn't work
There's still something weird going on that is related to this. If I insert media containing photos I expect the command specified by the gconf key /desktop/gnome/volume_manager/autophoto_command to be run. However, this isn't happening. Instead, nautilus is trying to launch its idea of what should be handling photos and it is broken. It seems to be launching f-spot via /usr/share/applications/f-spot.desktop. I'm not sure where this association with nautilus is made - too many moving parts to understand. However, f-spot can no longer be run in import mode without specifying the --import option and f-spot.desktop is not specifying that option. I just get a dumb usage message in ~/.xsession- errors. So, shouldn't autophoto_command be used for media containing photos? If not, the association with nautilus needs to be fixed so that f-spot- import is run rather than f-spot. By the way, it took about 3 hours (for an experienced Linux user) to work out that autophoto_command is being ignored and the problem has something to do with nautilus. So, if the reply is that shouldn't be happening can you please give me a nice list of gconf keys to check to try and figure out why it is happening? ;-) Thanks... peace happiness, martin -- Camera Device button Open F-spot Photo Manager doesn't work https://bugs.launchpad.net/bugs/208467 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 208467] Re: Camera Device button Open F-spot Photo Manager doesn't work
Aaarrrggghhh! /usr/share/applications/f-spot.desktop isn't being accessed when the media is inserted. So where does the association between nautilus and f-spot come from? Explain this to me and you'll get much better bug reports on this sort of thing... :-) Things I have checked: * There doesn't seem to be a relevant g-conf key. * There doesn't seem to be anything in f-spot.postinst... but then update-desktop-database could be doing anything - it is undocumented and in /usr/bin. :-( -- Camera Device button Open F-spot Photo Manager doesn't work https://bugs.launchpad.net/bugs/208467 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 202717] Re: Can't open multiple files from File Browser in F-Spot Photo Viewer
3 things to add: * In Gutsy, it was possible to select multiple files in Nautilus and open them in F-Spot. Therefore, the behaviour we're seeing in Hardy is a regression. * If this isn't going to be considered an F-Spot bug, then it is a bug in Nautilus since it allows you to select multiple files and attempt to view them using F-Spot. :-) * It is possible to work around this bug by right-clicking on a folder in Nautilus, selecting Open with Other Application and then selecting F-Spot Photo Viewer. One reason for doing this is that, when viewing multiple CR2 (Canon Raw) images, switching between images is an order of magnitude faster in F-Spot that it is in GThumb. -- Can't open multiple files from File Browser in F-Spot Photo Viewer https://bugs.launchpad.net/bugs/202717 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 202717] Re: Can't open multiple files from File Browser in F-Spot Photo Viewer
However, opening a whole folder doesn't maintain the sort order. The files are displayed in directory order (same as ls -U) rather than sorted alphabetically. Therefore, this isn't as useful as the old behaviour where multiple files could be selected and they would appear in F-Spot in the order they appeared in the Nautilus listing that they were selected from. -- Can't open multiple files from File Browser in F-Spot Photo Viewer https://bugs.launchpad.net/bugs/202717 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 197589] Re: Numeric keypad no longer works after upgrade
I'm seeing the same inconsistent behaviour as in comment 34. After the first reboot after the upgrade, the keypad was in the cursor control mode. This time it is in normal number mode. My upgrade was from Gutsy to the released version of Hardy. This would be a very frustrating bug for a novice user... still Ubuntu's main target audience? -- Numeric keypad no longer works after upgrade https://bugs.launchpad.net/bugs/197589 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 138094] Re: [Gutsy] desktop and keyboard freezes while mouse is moveable
Actually, I got it wrong: for me keyboard is fine. The mouse simply stops working and functions again after switching desktops. -- [Gutsy] desktop and keyboard freezes while mouse is moveable https://bugs.launchpad.net/bugs/138094 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 138094] Re: [Gutsy] desktop and keyboard freezes while mouse is moveable
I'm seeing a similar X-related lock-up several times a day under moderate usage. However, if I change desktops using Ctrl-Alt-Left/Right then the mouse and keyboard start working again. Is anyone else seeing this? This would point to some sort of bizarre window manager bug... or perhaps an X bug that can be worked around by the window manager sending some sort of refresh event when desktops are switched. This is with Gutsy, GNOME and recent Intel graphics (sorry, not sitting at the machine right now). No non-standard packages... -- [Gutsy] desktop and keyboard freezes while mouse is moveable https://bugs.launchpad.net/bugs/138094 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
Re: [Bug 109083] Re: No Python TMDA modules for python 2.5
Hi Chuck, Chuck == Chuck Short [EMAIL PROTECTED] writes: Chuck Added thanks for your patch. Chuck ** Changed in: tmda (Ubuntu) ChuckStatus: Confirmed = Fix Committed Thanks... At this stage I guess it is worth confirming that python2.5 will still be the default python version for Gutsy? If the default will be 2.6 then the patch will obviously need to be tweaked... :-) peace happiness, martin -- No Python TMDA modules for python 2.5 https://bugs.launchpad.net/bugs/109083 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 121165] Re: /dev/.initramfs/progress_state is corrupted at shutdown
Hi Juho. Just wondering if you've fixed the swap problem and whether this has caused the corruption on shutdown to go away. Unfortunately I've had to retired the machine where I was seeing the problem, so I can no longer test for this problem. It would be nice to if we were able to add some information to Bug #96715 to convince someone that the importance should change from undecide to real corruption has been observed so this should be fixed right now. :-) -- /dev/.initramfs/progress_state is corrupted at shutdown https://bugs.launchpad.net/bugs/121165 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 121165] Re: /dev/.initramfs/progress_state is corrupted at shutdown
I wonder if this is semi-random corruption related to Bug #96715? I've uninstalled evms and the swap space problem has gone away. Juho, when you do: cat /proc/swaps do you see the same partition used twice (once via /dev/mapper)? This bug is probably going to be very hard to debug... so this is a wild guess... but repeatable corruption has to be coming from somewhere. So I'm wondering if it happens when swapoff interacts with something else? Let's trawl through swap space for the above junk (which I have now seen several times): $ sudo dd if=/dev/sda2 | hexdump -C | grep '0(p' 01f35000 00 22 00 30 28 70 00 00 01 27 2d 4b 00 00 05 03 |..0(p...'-K| Apart from the non-printables, that looks familiar! Now, change the grep to less and browsing backwards, the previous non- NUL item in swap is: 01f34000 50 52 4f 47 52 45 53 53 5f 53 54 41 54 45 3d 33 |PROGRESS_STATE=3| That is *way* too much of a coincidence. There's obviously something weird happening with swap... I wonder if you have the double-swap issue and if the file corruption goes away completely if you resolve the double-swap issue? -- /dev/.initramfs/progress_state is corrupted at shutdown https://bugs.launchpad.net/bugs/121165 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 124518] anacron prints spurious debug message
Public bug reported: Binary package hint: anacron I assume that when anacron is run from the command line and there are no problems encountered then it should produce no output. However, if there's a @monthly entry in the anacrontab, then anacron prints a message like: Checking against 0 with 30 This looks a lot like a debug message and should probably be removed. The offending line of code is introduced by anacron_2.3-13ubuntu2.diff.gz into anacron-2.3/lock.c:consider_job() and looks like: printf (Checking against %d with %d\n, day_delta, period); I'm running with this option: -d Don't fork to the background. In this mode, Anacron will output informational messages to standard error, as well as to syslog. The output of jobs is mailed as usual. (among others), which only mentions output to stderr, not stdout. However, in this case the message is confusing because the user has no real idea of its context, so it probably should not be made to go to stderr but should probably be removed altogether. ** Affects: anacron (Ubuntu) Importance: Undecided Status: New ** Affects: anacron (Debian) Importance: Undecided Status: New -- anacron prints spurious debug message https://bugs.launchpad.net/bugs/124518 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 124518] Re: anacron prints spurious debug message
** Also affects: anacron (Debian) Importance: Undecided Status: New -- anacron prints spurious debug message https://bugs.launchpad.net/bugs/124518 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 109083] Re: No Python TMDA modules for python 2.5
I'm hoping to get someone's attention to have this package at least fixed for gutsy. My previous comment has the patch needed to fix the problem. :-) Thanks... -- No Python TMDA modules for python 2.5 https://bugs.launchpad.net/bugs/109083 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 121165] Re: /dev/.initramfs/progress_state is corrupted at shutdown
This happened again. Here are the contents of /dev/.initramfs/progress_state: 0(p'-KA Meaningless nonsense! Actually, the last 2 characters were some sort of scripted K (kappa?) and a scripted A (?), probably form some distant part of the console font. Whatever the case, the file contains rubbish. However, the rubbish is somewhat consistent because the Unterminated quoted string error is common. So, I'm wondering what this is? Filesystem corruption? The result of a bizarre race condition? Memory corruption? I'm betting against a hardware problem. I'm not seeing problems at other times, it seems relatively consistent and this only started occurring when I upgraded to Feisty. However, I've seen less likely coincidences :-) Ideas? Thanks... -- /dev/.initramfs/progress_state is corrupted at shutdown https://bugs.launchpad.net/bugs/121165 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 121165] /dev/.initramfs/progress_state is corrupted at shutdown
Public bug reported: Sometimes shutdown fails with the message: /dev/.initramfs/progress_state: 1: Syntax error: Unterminated quoted string error: '/etc/init.d/rc' exited outside the expected flow control. The only thing that writes to this file appears to be the update_progress() function in /usr/share/initramfs- tools/scripts/functions. I've even unpacked the initramfs for the current kernel to make sure that file isn't somehow corrupted. It looks fine. So /dev/.initramfs/progress_state ends up in an unusual state. Could this be a race condition? Is anything happening in parallel at shutdown? Could the file be partially written when it is sourced by /etc/init.d/rc? For now I've added something that prints the contents of /dev/.initramfs/progress_state before it is sourced by /etc/init.d/rc. However, if this is a race condition, I don't hold out much hope of actually seeing anything useful any time soon... So, any ideas? :-) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: Unconfirmed -- /dev/.initramfs/progress_state is corrupted at shutdown https://bugs.launchpad.net/bugs/121165 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 119415] wpa-conf managed appears no longer supported
Public bug reported: Package: wpasupplicant Version: 0.5.7-0ubuntu2 In Edgy /usr/share/doc/wpasupplicant/README.modes.gz used to say to put: wpa-conf managed in an /etc/network/interfaces stanza for an interfaces that were using WPA managed mode. However, in Feisty, doing this causes a failure... which is silent depending on the configuration. Therefore, wpasupplicant can mysteriously fail to start after an Edgy - Feisty upgrade. I don't see this change documented anywhere (NEWS, changelog, README.modes, ...) and the section on Hidden ssids in the above README still has a reference to this configuration option. So, I guess it is a documentation bug... Even though I hit this for the 2nd time it still took a while to work it out... :-) peace happiness, martin ** Affects: wpasupplicant (Ubuntu) Importance: Undecided Status: Unconfirmed -- wpa-conf managed appears no longer supported https://bugs.launchpad.net/bugs/119415 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 109083] Re: No Python TMDA modules for python 2.5
I have the same problem. Attached is the simple patch I used to rebuild a useful version of python-tmda for feisty. ** Attachment added: Patch to make python-tmda useful under feisty http://launchpadlibrarian.net/8034086/feisty-python-tmda.patch -- No Python TMDA modules for python 2.5 https://bugs.launchpad.net/bugs/109083 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 36252] Re: desktop/nautilus right-click eject problem
I'm very surprised that the fix for this hasn't made feisty-updates. I have several USB devices that I could unmount/eject just fine from the right-clock menu in Edgy but they are immediately remounted after being ejected in Feisty. Ways of fixing this so I can safely remove my devices include: * Reverting to the command line to unmount the filesystem. * Discover that I need to install a package from something called feisty-backports, figure out how to do that and then actually do it successfully. * Edit /usr/share/hal/fdi/policy/10osvendor/10-storage-policy.fdi to stop the devices being ejected. As an experienced Linux user all of these are OK for me. However, if this happens to inexperienced users it is a showstopper because they do not have the know-how to be expected to do any of the above. That is, from a usability point-of-view for inexperienced users: * This is a regression. * This is critical. Fixing this should be a high priority as it will affect a lot of Ubuntu's target users. -- desktop/nautilus right-click eject problem https://bugs.launchpad.net/bugs/36252 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
