Will this bug be fixed in the next version of Ubuntu? In gutsy it is
still present. Trying to copy a file bigger in size then the filesystem
can handle (4gb on fat32 for instance) although enough space is
available will still make nautilus disappear and reappear shortly
afterwards. Not really a
*** This bug is a duplicate of bug 70535 ***
https://bugs.launchpad.net/bugs/70535
I am using Gutsy Gibbon with all updates applied and experienced the
same crash as well. I will install gdb and post the log later on. It
would indeed be better to have nautilus present the user with the
I have the same problem. Although I do not experience the high cpu
amount, I do have a job lingering in the print job window after job
completion. When I cancel the job and a new job was issued, the new job
is finally printed. Please fix this because it is a bit annoying to have
a job printed upon
Same here. When the samba share is auto mounted in /etc/fstab, HAL fails to
initialise, the desktop is stalled for a couple of minutes. Then the desktop
appears, and the samba share gets mounted. When doing lshal immediately in a
terminal I got a message saying that HAL could not be connected
Thanks for the work around (I did not know I could change this in Alacarte
which I did just now manually)
Anyway, glad to be of some help.
--
Name of Configure Printers wrong
https://launchpad.net/bugs/49893
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
Public bug reported:
For some reason at some point the name of the menu entry for access to
configuration of printers (can be found under System-Administration) has been
changed to Busy Printing (it is actually in dutch Bezig met afdrukken so I am
not exactly sure what it says in English..
