[Bug 546105] Re: Simple Scan failed to scan: Error communicating with scanner

2010-05-21 Thread voltaire
I am running Lucid and I also get this error message. My scanner is an Epson Perfection 610 which can't take multiple pages. The scan works as expected, it's only that I get a pop-up window after the scan is complete: Failed to scan, Error communicating with scanner, "Change Scanner" or "Close".

[Bug 123460] Re: Rhythmbox:Error while saving song information:Internal GStreamer problem

2010-05-08 Thread voltaire
A re-install of rhythmbox didn't help but removing the xml file rhythmdb.xml (~/.local/share/rhythmbox/rhythmdb.xml) helped me start the application again (after which it re-scans the music database automatically). -- Rhythmbox:Error while saving song information:Internal GStreamer problem https:

[Bug 123460] Re: Rhythmbox:Error while saving song information:Internal GStreamer problem

2010-05-08 Thread voltaire
I had a Rhythmbox opened in a background window and as I was editing tags with EasyTag, It crashed Rhythmbox and since then whenever I want to open it there a fairly long delay and it comes with the pop-up: Error while saving song information. Internal GStreamer problem; file a bug. I am using U

[Bug 73012] Re: Wrong Refresh Rate after installing NVIDIA driver (1.0-9629)

2007-05-03 Thread Voltaire
Same on my Computer with Kubuntu Feisty Fawn with latest updates and a NVidia 6600. Please find attached the needed information. I'm using the binary-only Nvidia Driver 1.0.9755. The xorg.conf is an unmodified and autogenerated version from nvidia-settings. $ sudo dpkg -l nvidia\* | grep ii ii nv

[Bug 103603] Re: X server at 100% CPU

2007-04-29 Thread Voltaire
This is now fixed for me. After removing the Network Card (eth1) the system runs stable. -- X server at 100% CPU https://bugs.launchpad.net/bugs/103603 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ub

[Bug 110304] Re: Feisty crash possibly related to mdadm/raid5

2007-04-26 Thread Voltaire
The Output of mdadm --query --detail shows that your RAID is currently rebuilding (Rebuild Status : 4% complete). The UUID and the Status of the drives seems to be OK. It's hard to guess what the reason for the crash was. -- Feisty crash possibly related to mdadm/raid5 https://bugs.launchpad.net/

[Bug 110304] Re: Feisty crash possibly related to mdadm/raid5

2007-04-26 Thread Voltaire
Sorry. This means: "Did your computer crash while booting?" -- Feisty crash possibly related to mdadm/raid5 https://bugs.launchpad.net/bugs/110304 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-

[Bug 110304] Re: Feisty crash possibly related to mdadm/raid5

2007-04-26 Thread Voltaire
Could you please give some more information on the Crash? Did your computer while booting? Or was your system up and running? After fixing Bug 107080 on my System, it has run normally aside from bug 103603 which is not connected to my RAID problems. -- Feisty crash possibly related to mdadm/raid5

[Bug 107080] Re: Wrong RAID UUID on PATA RAID5 partitions after Feisty Upgrade

2007-04-26 Thread Voltaire
As far as I know the UUID in mdadm.conf is the Device UUID for md0 which is used in /etc/fstab to mount the drive. The UUID reported by mdadm --examine is the UUID of the RAID Partition which must be the same for all Members of a raid. Could you please attach a copy of /etc/mdadm/mdadm.conf

[Bug 103603] Re: X server at 100% CPU

2007-04-26 Thread Voltaire
After upgrading to Feisty I have the same Problem. When I left my computer for several hours alone the Desktop seems to work (Clock changes, Knewsticker is running) but when I move the mouse the Display freeze and the Keyboard stops working. In some cases the effect could happen after a few minute

[Bug 107080] Re: Wrong RAID UUID on PATA RAID5 partitions after Feisty Upgrade

2007-04-18 Thread Voltaire
I succede in recovering my Partition. It's not clearly stated in the manual, but you can recreate a RAID which Superblocks are messed up. The most important part is to store the RAID Informations of each partion at a safe place: $ sudo mdadm --examine /dev/* // where * is every member of your

[Bug 107080] Wrong RAID UUID on PATA RAID5 partitions after Feisty Upgrade

2007-04-16 Thread Voltaire
Public bug reported: Binary package hint: mdadm I had created a RAID5 Array on Edgy: /dev/sda4 - SATA /dev/sdb1 - SATA /dev/hda1 - PATA /dev/hdb1 - PATA It works flawlessly for two months with several reboots. On Friday, 13 April 2007 I upgraded to Feisty (bad day?) and run into the probl

[Bug 68808] Re: slow kdm/kde startup since upgrade to edgy

2006-11-19 Thread Voltaire
As there seems to be not real solution until now, a workaround is to install gdm with 'sudo apt-get install gdm' and select it instead of kdm. -- slow kdm/kde startup since upgrade to edgy https://launchpad.net/bugs/68808 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ub

[Bug 68808] Re: slow kdm/kde startup since upgrade to edgy

2006-11-04 Thread Voltaire
Same on my Notebook System. I made an upgrade from Dapper to Edgy with setting everthing in /etc/apt/sources.list from dapper to edgy, sudo apt-get dist-upgrade on my Desktop and my Notebook. On the Desktop, everything works fine. The Notebook needs around 1 minute from closing the bootscreen to t