USB startup disk creator crashes compiz

[Rüdiger Kupper]

Ubuntu Precise 12.04:
USB startup disk creator reproducibly crashes compiz as soon as the "Copying Files" info box appears. Compiz automatically restarts, and usb-creator keeps running.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: usb-creator-gtk 0.2.38
ProcVersionSignature: Ubuntu 3.2.0-30.48-generic 3.2.27
Uname: Linux 3.2.0-30-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu12
Architecture: amd64
Date: Sat Sep 8 22:26:37 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
SourcePackage: usb-creator
UpgradeStatus: Upgraded to precise on 2012-04-28 (133 days ago)

[Luis Alvarado (luisalvarado)]

Hi Rüdiger Kupper, I tried in 2 HP computers using 12.04. On both cases it worked correctly.
My questions then are:

1. Was the image correctly downloaded? Did you check the MD5?

2. Did you try in another USB port (Front ports, rear ports)?

[Rüdiger Kupper (ruediger.kupper)]

Hi Luis.

MD5 is correct.
But after rebooting, the crashes have changed: Compiz no longer crashes at the beginning of the copy process. Instead, it now crashes when usb-creator exits.

I wonder if these crashes can be somehow related to another issue I see trying to boot Ubuntu live session off USB? See Bug 1048000

[Rüdiger Kupper (ruediger.kupper)]

This is on a Thinkpad T61, 64-bit Ubuntu Precise.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Michele Giacomoli (michele-giacomoli)]

I have the same problem on a Dell Studio 1749, 64 bit, Ubuntu Precise

[Goury (madoo)]

Same on Acer Aspire Timeline Ultra M3 with use of intel graphics. I did not tried this with gt640m as i dont need it to run commpiz.

Every single time! Every time i make liveusb ith this tool it crashes compiz ni exacly same way!
Crashes all the way for last two months, always up-to-date with universe. multiverse and backports.
Yes, i did checked hashes and signatures for packages. Its all good.

[ethanay (ethan-y-us)]

Dell XPS m1330 w/Intel GM965 graphics on Ubuntu 32-bit w/latest updates onto Patriot 4gb flash drives

This bug occurs consistently at two points during the process:

1. durign the start of the copy process
2. During the "system policy requires authentification for installation of bootloader" prompt (where you need to enter your password to finish the process)

It's not a huge deal -- it seems to just cause compiz to crash. Here's my dmesg from the time I plugged into the flash drive through the entire process:

[23079.540277] usb 2-1: new high-speed USB device number 17 using ehci_hcd
[23079.661561] scsi13 : usb-storage 2-1:1.0
[23080.735284] scsi 13:0:0:0: Direct-Access Patriot Memory PMAP PQ: 0 ANSI: 4
[23080.738134] sd 13:0:0:0: Attached scsi generic sg2 type 0
[23081.753938] sd 13:0:0:0: [sdb] 7831552 512-byte logical blocks: (4.00 GB/3.73 GiB)
[23081.755384] sd 13:0:0:0: [sdb] Write Protect is off
[23081.755394] sd 13:0:0:0: [sdb] Mode Sense: 23 00 00 00
[23081.756849] sd 13:0:0:0: [sdb] No Caching mode page found
[23081.756858] sd 13:0:0:0: [sdb] Assuming drive cache: write through
[23081.762917] sd 13:0:0:0: [sdb] No Caching mode page found
[23081.762926] sd 13:0:0:0: [sdb] Assuming drive cache: write through
[23081.786275] sdb: sdb1
[23081.791038] sd 13:0:0:0: [sdb] No Caching mode page found
[23081.791049] sd 13:0:0:0: [sdb] Assuming drive cache: write through
[23081.791057] sd 13:0:0:0: [sdb] Attached SCSI removable disk
[23237.176824] ISO 9660 Extensions: Microsoft Joliet Level 3
[23237.176937] ISO 9660 Extensions: RRIP_1991A
[23238.922334] compiz[8802]: segfault at b76026f8 ip b76026f8 sp bfae190c error 15 in libc-2.15.so[b7602000+1000]
[23240.046091] composite sync not supported
[23386.873964] compiz[20471]: segfault at 19 ip 00000019 sp bffab47c error 14 in compiz[8048000+c000]
[23387.862662] composite sync not supported

Ubuntu seems to recover more-or-less gracefully, and it doesn't *seem* to affect the performance of the flash drive. If others can verify, then it might make sense to leave it "as-is" or with a brief popup window on startup that informs the user of the bug and that it is largely a cosmetic issue.