[Bug 398495] [NEW] Digicam edit crashes multple instances
Public bug reported: Binary package hint: digikam I'm on Kubuntu 9.04 updated. I am accessing photos to edit; from an NTFS drive but I do not this that is the problem. After (time consuming) total edits, Digicam and the edit window will freeze, go white windows if I close and open the window and will not recover, resulting work flow failure. Time lost. The last time, I was attempting to stop the auto trial of the restoration, upon starting restoration. Since I do not save after every editing improvement step, to limit JPEG losses, I lose all work (time) done. Several time before that, both today and weeks ago, I had the same crash but in slightly different processes, during edit flow. I believe this is top priority. DigiKam for me, would be tops of ALL other photo apps, if it worked. ** Affects: digikam (Ubuntu) Importance: Undecided Status: New -- Digicam edit crashes multple instances https://bugs.launchpad.net/bugs/398495 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 343919] Re: Nvidia MCP67 AHCI ata timeout exception with data loss
My comment above.. ...and it's workaround, may be more relevant to the Alert! /dev/disk busybox failure to boot problem, than this thread which was said to be the original duplicate bug. That's why it's here. I do not know if this bug is in fact the cause of being dropped to busybox but the workaround worked for me and I just wanted to leave a trail for those of us that might wide up here. I posted this (previously VERY hard to find) workaround in the other bug duplicate and in the forums. Hopefully this will cause many to stick with (K)ubuntu. We had no other kernel to boot, once the upgrade process nixed the newly installed one. Now we can move ahead. Obviously, this workaround can be used with any singular kernel boot failure (to get another one). Because SOMETIMES, another clean install wastes time (but clean installs are recommended). -- Nvidia MCP67 AHCI ata timeout exception with data loss https://bugs.launchpad.net/bugs/343919 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 315572] Re: alert! /dev/disk/by-uuid/be80cf42-e6f2-466c-bb73-7d664956a334 does not exist
*** This bug is a duplicate of bug 343919 *** https://bugs.launchpad.net/bugs/343919 See https://bugs.launchpad.net/bugs/343919 for my SOLUTION. Fix, way to boot again and upgrade. -- alert! /dev/disk/by-uuid/be80cf42-e6f2-466c-bb73-7d664956a334 does not exist https://bugs.launchpad.net/bugs/315572 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 343919] Re: Nvidia MCP67 AHCI ata timeout exception with data loss
From my saved partition and chroot with Hardy 8.04 (you could use a live CD), this is how I fixed my Jaunty 9.04 fresh, beta install; where I could boot again. I look everywhere and tries everything. NONE of th buzybox commands worked for me. I do NOT have raid and their was no UUID or /dev naming error. Only the following worked for me and I still do not know why the newly installed kernal failed to boot after upgrading it. Perhaps it didn't upgrade or something because once I got back in using chroot, I had to run the apt-get fix command it recommends. Unless that was a limit of the chroot, I don't know. This was ugly and I almost gave up. In a terminal (we're using sudo for root here) Where X is your correct drive number, like /dev/sda2 for example sudo mount /dev/sdaX /mnt (You can cut and paste the commands below) sudo mount --bind /dev /mnt/dev sudo mount --bind /proc /mnt/proc sudo mount --bind /sys /mnt/sys sudo cp /etc/resolv.conf /mnt/etc/resolv.conf sudo chroot /mnt /bin/bash Then: apt-get install etc. I believe I did a: apt-get update (then the suggested fix command and...) apt-get upgrade While the kernel didn't appear to be different I not sure that it wasn't a newer fix. It booted. Now, after doing upgrades back in Jaunty again, I'm about to reboot and try the newest kernel (it just installed). I hope this helps you as much as it did me! -- Nvidia MCP67 AHCI ata timeout exception with data loss https://bugs.launchpad.net/bugs/343919 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 315572] Re: alert! /dev/disk/by-uuid/be80cf42-e6f2-466c-bb73-7d664956a334 does not exist
*** This bug is a duplicate of bug 343919 *** https://bugs.launchpad.net/bugs/343919 WAIT!* Actually. since the title of this bug better *is* the problem I had I will post the solution here (to get the job done) and also in the ubuntu forums) so more can find it. From my saved partition and chroot with Hardy 8.04 (you could use a live CD), this is how I fixed my Jaunty 9.04 fresh, beta install; where I could boot again. I look everywhere and tries everything. NONE of th buzybox commands worked for me. I do NOT have raid and their was no UUID or /dev naming error. Only the following worked for me and I still do not know why the newly installed kernal failed to boot after upgrading it. Perhaps it didn't upgrade or something because once I got back in using chroot, I had to run the apt-get fix command it recommends. Unless that was a limit of the chroot, I don't know. This was ugly and I almost gave up. In a terminal (we're using sudo for root here) Where X is your correct drive number, like /dev/sda2 for example sudo mount /dev/sdaX /mnt (You can cut and paste the commands below) sudo mount --bind /dev /mnt/dev sudo mount --bind /proc /mnt/proc sudo mount --bind /sys /mnt/sys sudo cp /etc/resolv.conf /mnt/etc/resolv.conf sudo chroot /mnt /bin/bash Then: apt-get install etc. I believe I did a: apt-get update (then the suggested fix command and...) apt-get upgrade While the kernel didn't appear to be different I not sure that it wasn't a newer fix. It booted. Now, after doing upgrades back in Jaunty again, I'm about to reboot and try the newest kernel (it just installed). I hope this helps you as much as it did me! -- alert! /dev/disk/by-uuid/be80cf42-e6f2-466c-bb73-7d664956a334 does not exist https://bugs.launchpad.net/bugs/315572 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 155788] Re: KDE blocks digital camera detection as usb-scsi disk
None of this works for me. What I have to add is I continually plug and unplug the camera (Panasinic FZ18), eventually I can get files off the cameras internal memory. It doesn't last long though. It goes away and there seems to be no exact number of times to try. Maybe about 4 but sometimes many more. What in the world is wrong with KDE? This looks to me to be a small setting (guessing) or duplication or something but darned if I know what. Please help. At least with a working work-around. Let's get this in the upgrades too. It looks bad. very bad. -- KDE blocks digital camera detection as usb-scsi disk https://bugs.launchpad.net/bugs/155788 You received this bug notification because you are a member of Kubuntu Team, which is subscribed to kdebase in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 155788] Re: KDE blocks digital camera detection as usb-scsi disk
OK this is maddening but I will report what I found. Now, after many tries, what was working, KDE says, I do not have the right permissions. What's really interesting is, when it's not usually saying (by dmesg) waiting for the device to settle, it says Trying to read beyond the limits of the device or exact wording that is extremely similar. These happens with the internal memory or on my 1GB SD memory card in the cam(that works fine in a good reader). I used the cameras built in format on it's internal memory but it made no difference. I doubt the camera memory came in a differing state than it's internal format command leaves it. I have only formated my 1GB SD by the cameras built in format command. So, (like the internal) I don't think my external card is the issue. Notes: In camera formating may be the safest method of formating memory cards. Flash memory may have that skipped/blank area before the actual partition and that skip is for Flash alignment! Don't write over it! AKA, don't repartition when you format. Sometimes a particular format program also automatically changes the partition; before the actual format. IT WILL DESTABILIZE YOUR DRIVE! this may ve why so many are reported as duds. BUT, I read there MAY also be an issue with end of partition errors that the camera miss-detects, too. You would only see this as you run out of space and a file (perhaps a big movie) over writes the end, and you lose it. My internal memory does fine when it it filled up. Ironically, this attempt to access beyond end of device is the message I am getting above but not with the camera, with Kubuntu. So, it could definitely be related. Also, besides Windows tendency to format Flash for FAT32 when it may be best as FAT(VFAT16) for =4GB Flash, I also read Windows may format the partition similar to a floppy, rather than a hard drive. sda, instead of sda1 for example. This may be rejected by your differing devices (and firmware or drivers) and thus be incompatible across them. So that's Two things about the underlying partition of Flash; that you may not have considered. FYI All that said, it looks to be KDE and this worked before Gusty. Other than a USB reader for the SD or PTP mode with the camera (not fully functioning with internal memory but maybe we can transfer movie clips to a SD first, then use a USB adapter instead of the cam cable), what is the KDE work around that works? -- KDE blocks digital camera detection as usb-scsi disk https://bugs.launchpad.net/bugs/155788 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 129910] Re: Blank ttys when using vesafb (vga=xxx)
Come on guys. Please fix this with the fine and automatic upgrade system. It's been way too long. -- Blank ttys when using vesafb (vga=xxx) https://bugs.launchpad.net/bugs/129910 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 96905] Re: USB flash drive shown twice on the desktop
No. I have several flash drives; all singular partitions/standard and each one pulls up two (ANNOYING) file manager windows, even after I purged Dolphin (on Kubuntu) in favor of Konqueror. The second windows COMPLAINS about already being mounted. This happens almost at the same time. The newest one is a transflash/MicroSD in it's USB adapter. It is tiny and I do not think U3 or anything else is added. The others are NOT in any type of adapter but USB 2.0. I tried turning off auto file view pop-ups and it still show two each time. -- USB flash drive shown twice on the desktop https://bugs.launchpad.net/bugs/96905 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 160535] Re: Installing nvidia-glx-new restricted drivers increase gnome login time
Could this need the dpi set in the xorg.conf? -- Installing nvidia-glx-new restricted drivers increase gnome login time https://bugs.launchpad.net/bugs/160535 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 129910] Re: tty[1-6] are active but display nothing in Gutsy
Should I take that to mean, comment out (with #) blacklist nvidiafb (I have an old nvidia Geforce card) so that it is NOT blacklisted? I took this to say that vesafb and nvidiafb are the only ones in my file WITH a # so as not blacklisted. Right? -- tty[1-6] are active but display nothing in Gutsy https://bugs.launchpad.net/bugs/129910 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 157084] package update-manager 1:0.81 failed to install/upgrade: ErrorMessage: SystemError in cache.commit(): E:Sub-process /tmp/tmpgzoG09/backports/usr/bin/dpkg returned an error code (1), E:Sub
Public bug reported: Binary package hint: update-manager Great. 1. It's a good thing I'm already registered or I may not have stopped to file a report. Please allow non-registered bugs to be filed and do so in such a manner that if it is duplicate or inconsequential is can be quickly dismissed. 2. I could not easily tell is a similar bug has been filed. 3. Now that I'm here trying to report the details, I can NOT cut the text because it is being held up by the dialog that says its about to run a dpkg --configure -a (At least l can paste that). Once I click OK the details will surely be gone. Processing trigger for initramfs-tools... Generating ... etc.. IOError: [Errno 9] Bad file descriptor expect ver 94 or higher fatal ...1 client killed Seems to be the gist of it. ProblemType: Package Architecture: i386 Date: Thu Oct 25 10:19:28 2007 DistroRelease: Ubuntu 7.10 ErrorMessage: ErrorMessage: SystemError in cache.commit(): E:Sub-process /tmp/tmpgzoG09/backports/usr/bin/dpkg returned an error code (1), E:Sub-process /tmp/tmpgzoG09/backports/usr/bin/dpkg returned an error code (1) Package: update-manager 1:0.81 PackageArchitecture: all SourcePackage: update-manager Title: package update-manager 1:0.81 failed to install/upgrade: ErrorMessage: SystemError in cache.commit(): E:Sub-process /tmp/tmpgzoG09/backports/usr/bin/dpkg returned an error code (1), E:Sub-process /tmp/tmpgzoG09/backports/usr/bin/dpkg returned an error code (1) Uname: Linux LA1300 2.6.20-16-generic #2 SMP Sun Sep 23 19:50:39 UTC 2007 i686 GNU/Linux ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package -- package update-manager 1:0.81 failed to install/upgrade: ErrorMessage: SystemError in cache.commit(): E:Sub-process /tmp/tmpgzoG09/backports/usr/bin/dpkg returned an error code (1), E:Sub-process /tmp/tmpgzoG09/backports/usr/bin/dpkg returned an error code (1) https://bugs.launchpad.net/bugs/157084 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 157084] Re: package update-manager 1:0.81 failed to install/upgrade: ErrorMessage: SystemError in cache.commit(): E:Sub-process /tmp/tmpgzoG09/backports/usr/bin/dpkg returned an error code (1), E
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/10169699/Dependencies.txt -- package update-manager 1:0.81 failed to install/upgrade: ErrorMessage: SystemError in cache.commit(): E:Sub-process /tmp/tmpgzoG09/backports/usr/bin/dpkg returned an error code (1), E:Sub-process /tmp/tmpgzoG09/backports/usr/bin/dpkg returned an error code (1) https://bugs.launchpad.net/bugs/157084 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 30207] Re: media:/ does not handle floppy mounting correctly
Forgive me if I'm stating the obvious but for clarity, the above successful workaround does not repair the problem; with the Storage Media window and it's function with floppy drives. So this needs attention. What is the cause? This is fundamental for floppy drives. Also; quite frankly, it's a little embarassing. While the problem may well be with KDE, it is with KDE on Kubuntu. -- media:/ does not handle floppy mounting correctly https://launchpad.net/bugs/30207 -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
