complete non response to task

[Au]

Binary package hint: ubiquity

Having clicked the mouse ubiquity response was non existent so after 60 seconds exited the open program through clicking on quit

ProblemType: Crash
Architecture: i386
Date: Tue Mar 20 04:58:11 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
InterpreterPath: /rofs/usr/bin/python2.5
Package: ubiquity 1.3.24
ProcCmdline: /usr/bin/python /usr/lib/ubiquity/bin/ubiquity kde-ui
ProcCwd: /home/ubuntu
ProcEnviron:
 PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/lib/ubiquity/bin/ubiquity', 'kde-ui']
SourcePackage: ubiquity
Uname: Linux ubuntu 2.6.20-9-generic #2 SMP Mon Feb 26 03:01:44 UTC 2007 i686 GNU/Linux

[Colin Watson (cjwatson)]

Hmm. So, it seems that you launched two copies of ubiquity at once by accident (this often happens to Kubuntu users, because KDE only requires you to single-click on desktop icons but a lot of people habitually double-click). The crash is from the second one, and is harmless; more recent versions of ubiquity have a better locking system and should exit more quietly rather than crashing.

However, none of that explains why the other copy of ubiquity wasn't responding, and there are no signs in the log files. Would you mind grabbing a more recent daily build from http://cdimage.ubuntu.com/kubuntu/daily-live/current/ and seeing if you can still reproduce the lack of response? Also, please tell me what you clicked on that seemed to prompt the hang.

[Andrew Starr-Bochicchio (andrewsomething)]

We are closing this bug report because it lacks the information we need to investigate the problem. Please reopen it if you can give us the missing information. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New".

Thanks