Public bug reported:
Occurred while copying an 8GB backup file from an internal HD to a USB
HD. The Nautilus process crashed while unattended, likely after the
screensaver had kicked in. ("Blank Screen" was selected for the
screensaver to reduce CPU load.)
** Affects: nautilus (Ubuntu)
Imp
Crash file for Nautlius attached...
** Attachment added: "Crash file for Nautlius HD to USB HD crash"
http://librarian.launchpad.net/4971336/_usr_bin_nautilus.1001.crash
--
Nautilus copy to USB hard drive crashed
https://launchpad.net/bugs/70535
--
ubuntu-bugs mailing list
ubuntu-bugs@lists
Found the smoking gun: Nautilus died after copying 4294967295 bytes =
2^32-1 bytes -- a 4GB boundary error.
--
Nautilus copy to USB hard drive crashed
https://launchpad.net/bugs/70535
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
'cp' crashed with the same problem, at the same point in the file. (No
suprise there.)
--
Nautilus copy to USB hard drive crashed
https://launchpad.net/bugs/70535
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
This is odd: Nautilus was able to copy this file initially from one
internal HD to another, without crashing at 4GB. In this case, the
source HD was NTFS and the destination was ext3.
--
Nautilus copy to USB hard drive crashed
https://launchpad.net/bugs/70535
--
ubuntu-bugs mailing list
ubunt
Workaround: Divide files > 4GB with 'split', then copy the pieces, then
join them again with 'cat'.
--
Nautilus copy to USB hard drive crashed
https://launchpad.net/bugs/70535
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Aha! This is *not* a 'cp' or Nautilus bug, per se -- I think this is a
problem with this USB hard drive. Now the question is, is it a
particular idiosyncrasy with this external drive, or is it a fundamental
limitation of USB technology? (If the latter, then Nautilus --and
'cp'?-- would be improv
"Hence it really looks like only the binary drivers (at least nvidia,
haven't tested fglrx) are affected."
That being the case, perhaps someone ought to prove it out by installing
the Nvidia drivers from the 8.04 era into a fresh install of 9.10 and
demonstrating that binary nvidia + compiz + xdam
I'm experiencing the same problem, and tracked it down to the 'exec'
line in the '.desktop' file. I'm seeing the same behavior, whether I
use the menu editor to create the '.desktop' file, or if I hand-edit the
file to modify the 'exec' line.
Ironically, I ran into this with Wine, just as the ori
AHA!!! It's NOT a bug in the 'exec' parser!!!
I found it... It's a bug in the way the menu editor & Wine
create/manage/display the menus. It's not acting consistently!
Here's what's happening: I'm running 64-bit Karmic. I have an
application I installed in Wine 1.1.38 called "MyApp". When "
This being the case, then at least "the developers"/Canonical should
take the responsibility to produce the script you mention, "such that
when someone connects to a machine that has desktop effects enabled, the
effects could be automatically switched off for that remote control
session, and then s
I, too, have a fresh install of 10.10 with all the updates... And I see
the same behavior as well.
In my case, I have a /boot partition (/dev/sda3) and two RAID-1
partitions containing 10.04 (/dev/md8) and 10.10 (/dev/md9). It will
boot as expected to 10.10 (which was installed after 10.04), but
Martin, et al, please take a look at Bug 551790 -- it appears that the
fix for this has not gotten into Lucid or Maverick (or has regressed).
551790 has been 'confirmed', but it's not assigned to anyone...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
Appears to be related to Bugs 392836, 462961, and 551790.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/508901
Title:
update-grub sets wrong root argument
--
ubuntu-bugs mailing list
ubuntu-bugs@l
Just to add to my comment above in #4, I have checked partition UUIDs
using 'blkid', 'mdadm --detail', and 'tune2fs' and everything is
consistent and as it should be, except for what 'update-grub' generates.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
More... After patching my 'grub.cfg' file, I was able to reboot into
10.04. I then ran 'update-grub' within 10.04 to see what it would
generate. Lucid has the same problem as Maverick: With a single, common
'/boot' partition, it applies the UUID for the Lucid partition to Lucid
and Maverick root
Bug 508901 appears to be another case of this...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/551790
Title:
lucid update-grub wrong root=UUID=
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu
Public bug reported:
Attempted to build 'bmcwl' from "5.60.48.36+bdcom-0ubuntu3" while trying
to get Broadcom 4313 wireless to work in UNE 10.04 on an Acer Aspire One
D255.
Eventually succeeded instead in building Broadcom STA driver from source
obtained from Broadcom website, which did get the w
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/686811
Title:
package bcmwl-kernel-source 5.60.48.36 bdcom-0ubuntu3 failed to
install/upgrade: bcmwl kernel module failed to build
--
ubuntu-bugs ma
We need to add one more option: The remote host port number for the SSH
connection. Reason: It's not good practice to expose an open Port 22 to
the Internet; it attracts relentless break-in attempts from all over the
world.
I use a custom port number for SSH into my VNC server machine (stealthed
20 matches
Mail list logo
