[Bug 70535] Nautilus copy to USB hard drive crashed
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)
Importance: Undecided
Status: Unconfirmed
--
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
[Bug 70535] Re: Nautilus copy to USB hard drive crashed
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.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 70535] Re: Nautilus copy to USB hard drive crashed
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
[Bug 70535] Re: Nautilus copy to USB hard drive crashed
'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
[Bug 70535] Re: Nautilus copy to USB hard drive crashed
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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 70535] Re: Nautilus copy to USB hard drive crashed
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
[Bug 70535] Re: Nautilus copy to USB hard drive crashed
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 improved by refusing any attempts to transfer files >= 4GB to a USB device, perhaps suggesting that the file be split first.) -- 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
[Bug 353126] Re: Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org prior to release 7.5
"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 + xdamage enabled = no problem. Or has this been done already? -- Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org prior to release 7.5 https://bugs.launchpad.net/bugs/353126 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 335712] Re: strange escape handling in Exec line of .desktop files
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 original reporter did. I'm trying to launch 'notepad' in Wine, giving it a path to a document to open. I've determined that the GUI editor seems to automatically double my backslash characters. Per the Wine documentation (and special character escaping rules), I expected to have to double the backslashes when I created the menu property. However, the GUI editor seems to handle this for me. The problem is THIS: When 'exec' execs the command, the parser is stripping out ALL of the backslash characters -- no matter how many you have in the line. And it doesn't seem to matter how you escape the line with various quotings & backslashing -- it still assiduously finds and strips them all out. If I copy the line and paste it into a terminal -- with the backslashes appropriately doubled -- then the line is parsed and executes correctly, launching 'notepad' with the text file displayed. But in the '.desktop' file, the 'exec' command's backslash stripping means there's no apparent way to make this work. One more thing the development team needs to do: Add a 'help' to explain what's required as far as quoting and escaping special characters when creating a command line. It takes a lot of Googling to find these rules... Cheers! -- strange escape handling in Exec line of .desktop files https://bugs.launchpad.net/bugs/335712 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 335712] Re: strange escape handling in Exec line of .desktop files
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 "MyApp" installs, it (meaning MyApp's installer, Wine, and Ubuntu in some combination unknown to the layman) creates a menu folder entry in 'Applications / Wine / Programs' called "MyApp". Inside the "MyApp" folder, the install process creates several '.desktop' files for MyApp.exe, a few other associated apps, and entries to run 'notepad' with arguments that are README files. In my case, one of these 'notepad' launchers works, one doesn't. Examining the two revealed that the one that doesn't work fails only because the README file argument, which contains '\' characters, isn't quoted with double-quotes. The one that works has a quoted argument. I.e., the 'exec' parser is working properly according to http://library.gnome.org/devel/desktop-entry-spec/ (under "The Exec key"), which states "If an argument contains a reserved character the argument must be quoted." Here's where it gets weird: When I ran 'System / Preferences / Main Menu' and edited the Properties for the "notepad README" item, I could clearly see the change appear in THIS directory & file: .local/share/applications/wine-Programs-MyApp-MyApp ReadMe.desktop by cat'ing the file in a terminal window. My changes appear, and it automatically doubles my backslashes... However, that's NOT the '.desktop' file that's launching the "notepad README" item! It turns out that MyApp's installer / Wine / Ubuntu is creating TWO sets of '.desktop' files... And when you attempt to launch a Wine app, it uses THIS directory & file: .local/share/applications/wine/Programs/MyApp/MyApp ReadMe.desktop which is NOT edited by using 'System / Preferences / Main Menu'. You have to manually edit this file (using, e.g., 'vi'). And it my case, that amounted to correcting the argument to 'notepad' by enclosing it in double-quotes to meet the rules of the 'exec' key field for '.desktop' files. Once done, it launched properly from ''Applications / Wine / Programs / MyApp', as expected. So WHY are two sets of '.desktop' files being created / maintained? That's the bug! It's not the parser for 'exec'. Oh, and we still need a 'help' for guidance on escaping/quoting special characters... :^) -- strange escape handling in Exec line of .desktop files https://bugs.launchpad.net/bugs/335712 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 353126] Re: Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org prior to release 7.5
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 switched back on after disconnect." They should include this script as part of the Lucid distro, and make it available in the repositories for 9.10, 9.04, etc. It should be enabled by default with an option to disable it (though I don't know why anyone would want to). It may not be a "fix", but it would enable VNC/Remote Desktop to function in a straightforward way -- without having to know about this problem and what its workaround is. I seriously doubt anyone feels the need to have compiz doing eye candy tricks while using VNC, so it might even be considered a desirable "feature" even after this issue is fixed. -- Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org prior to release 7.5 https://bugs.launchpad.net/bugs/353126 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 551790] Re: lucid update-grub wrong root=UUID=
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 /boot/grub/grub.cfg lists the UUID for the root of 10.10 for all the entries, both 10.10 and 10.04, making it not possible to boot 10.04 (without manually editing the grub.cfg file). This is a pain, obviously, because every update that rebuilds grub.cfg undoes my edits. Bug 392836 reported this problem for Karmic, but it was not fixed (then). Bug 462961 re-reported it, and Martin Pitt apparently came up with a patched update-grub that fixed it -- that patch was added to 'proposed packages' (Comment #17), but it doesn't look like it ended up in subsequent builds/versions. (Or it regressed.) -- 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 462961] Re: auto-resize install renders previous system with separate /boot unbootable
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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/462961 Title: auto-resize install renders previous system with separate /boot unbootable -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 508901] Re: update-grub sets wrong root argument
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@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 551790] Re: lucid update-grub wrong root=UUID=
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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/551790 Title: lucid update-grub wrong root=UUID= -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 551790] Re: lucid update-grub wrong root=UUID=
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 roots. I have noted that in the '00_header' section of the generated 'grub.cfg' file, it also lists the UUID of the '/boot' partition (correctly, as it does for each OS entry), as well as the UUID of the OS that was booted at the time the 'update-grub' command was issued (10.04 or 10.10 in my two test cases). Further, it lists the kernels in numerical sequence, regardless of which OS generates the 'grub.cfg' file -- likely because these are all contained in the '/boot' directory. But it appears to apply the *one* UUID listed in the '00_header' section to *all* the Linux boot lines, regardless of which partition they're actually located on. Here's what's interesting: Martin Pitt's patch, '969_os_prober_separate_boot' as described in Bug 462961 implies that the problem is in the '30_os-prober' section of building 'grub.cfg' -- but it's not... The problem arises while it's building the '10_linux' section, as it finds the kernels for all the Linux OSes in the one common '/boot' partition -- and makes the mistake of using the one UUID for all of them, too. Normally what happens when you install two *independent* versions of Ubuntu on a system is that the first one is detected and listed in the '10_linux' section, and the other one isn't found and listed until the '30_os-prober' section runs. Notice that in these cases, the other Ubuntu OSes are listed *after* the '20_memtest86+' section. But in the case of the problem I've described here and in comment #4, all Linux OSes are listed together first, before the '20_memtest86+' section, in the section generated by '10_linux'. So the problem likely lies there. This section is failing to determine the actual partitions that hold the root filesystems for the kernels found in the common '/boot' directory; it finds the first and appears to presume that it applies to all the kernels listed. That's NOT the case in general, however. Potentially, each kernel in '/boot' *could* be associated with a different root partition. But what is commonly done, of course, is that the *set of kernels* for each Ubuntu distro use a common root partition. And, of course, a multiboot system with two or more root filesystems can put all its kernels into one common boot directory. 'update-grub' needs to take this into account... -- 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 551790] Re: lucid update-grub wrong root=UUID=
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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 686811] [NEW] package bcmwl-kernel-source 5.60.48.36 bdcom-0ubuntu3 failed to install/upgrade: bcmwl kernel module failed to build
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 wireless to function. I removed the 'bcmwl' package. It should be obvious that the appropriate drivers need to be in the UNE install image, as there is no way to get on the internet to download drivers, et al, if there are no network drivers installed to begin with! ProblemType: Package DistroRelease: Ubuntu 10.04 Package: bcmwl-kernel-source 5.60.48.36+bdcom-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-21-generic i686 Architecture: i386 Date: Tue Dec 7 15:10:41 2010 ErrorMessage: bcmwl kernel module failed to build InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Release i386 (20100429.4) PackageVersion: 5.60.48.36+bdcom-0ubuntu3 SourcePackage: bcmwl Title: package bcmwl-kernel-source 5.60.48.36+bdcom-0ubuntu3 failed to install/upgrade: bcmwl kernel module failed to build ** Affects: bcmwl (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 lucid ubuntu-une -- 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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 686811] Re: package bcmwl-kernel-source 5.60.48.36 bdcom-0ubuntu3 failed to install/upgrade: bcmwl kernel module failed to build
-- 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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 578733] Re: no way to change username for ssh tunneling
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 and controlled by UFW & FWKNOP in my case). My router port-forwards this port for incoming SSH, while blocking port 22 traffic. Port 22 use is then restricted to use only within my LAN (for convenience). In addition, since I have more than one VNC server to connect to, I use different ports to "direct traffic" to the intended machine on my LAN. Both of these needs prevent use of Port 22 for outside VNC tunneling. Using my custom ports works fine, is secure, does not draw break-in attempts, and allows me to pick & choose which machine I connect to. The problem is, the "Use host" feature on 'vinagre' does not allow me to specify the port to direct my connection to, and it should. Note that "Connect to server..." in 'nautilus' *does* allow you to specify the port number -- and this application *is* compatible with the connection scheme I just mentioned. We need 'vinagre' to be equally compatible, so it needs similar features. In this day & age, secure connections are not an option... and shouldn't be complicated to implement. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/578733 Title: no way to change username for ssh tunneling -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
