katapult freezes on opening and must be killed.

Bug #97584 reported by gordon
2
Affects Status Importance Assigned to Milestone
katapult (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: katapult

Press alt spacebar and Katapult screen apears. It freezes in the middle of the screen until killed. Stopping KDE doesn't seem to affect it, but shutting down the system does kill it.

ProblemType: Bug
Architecture: i386
Date: Wed Mar 28 16:36:45 2007
DistroRelease: Ubuntu 7.04
Uname: Linux grisedale 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686 GNU/Linux

Revision history for this message
Brian Murray (brian-murray) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. With which version of katapult did you notice this issue? I was unable to reproduce it with version 0.3.1.4-0ubuntu5. Thanks in advance.

Changed in katapult:
assignee: nobody → brian-murray
status: Unconfirmed → Needs Info
Revision history for this message
gordon (gschnare) wrote : Re: [Bug 97584] Re: katapult freezes on opening and must be killed.

That's the version I have installed. Since I reported the bug, Katapult won't even load, so I don't know if it is a bug, if it somehow got corrupted during installation, or if something else is going on. Removing and reinstalling doesn't work.

Gordon Schnare

-----Original Message-----
>From: Brian Murray <email address hidden>
>Sent: Mar 28, 2007 5:04 PM
>To: <email address hidden>
>Subject: [Bug 97584] Re: katapult freezes on opening and must be killed.
>
>Thanks for taking the time to report this bug and helping to make Ubuntu
>better. With which version of katapult did you notice this issue? I
>was unable to reproduce it with version 0.3.1.4-0ubuntu5. Thanks in
>advance.
>
>** Changed in: katapult (Ubuntu)
> Assignee: (unassigned) => Brian Murray
> Status: Unconfirmed => Needs Info
>
>--
>katapult freezes on opening and must be killed.
>https://launchpad.net/bugs/97584

Revision history for this message
Brian Murray (brian-murray) wrote :

Do you happen to be using beryl or compiz? If you start katapult in a terminal what information is returned? Thanks again.

Revision history for this message
gordon (gschnare) wrote :

On Friday March 30 2007 1:33:49 pm Brian Murray wrote:
> Do you happen to be using beryl or compiz? If you start katapult in a
> terminal what information is returned? Thanks again.

Neither beryl or compiz are installed. Here's what shows up when I try to
start Katapult in Konsole:

X Error: BadDevice, invalid or uninitialized input device 167
  Major opcode: 146
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 167
  Major opcode: 146
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
Ignored duplicate item: Scribus
Ignored duplicate item: Gnumeric Spreadsheet

I get the same information, however, (down to the "failed to open device"
part) if I open another program such as Kate or gnumeric in Konsole, but Kate
and gnumeric open and function anyway.

I have reinstalled katapult and it begins to load but doesn't open. I have
tried dpkg, apt and adept, but they all say that it has been successfully
loaded.

I don't know if it is equipment related or not. My computer is a Lenovo T-60
dual core, which can be a little squirrely at times. Katapult works with
Fiesty on my Dell Inspiron 8200.

Gordon Schnare

Changed in katapult:
assignee: brian-murray → nobody
status: Needs Info → Confirmed
Revision history for this message
Martin Meredith (mez) wrote :

Hi there! can you try deleting ~/.kde/share/config/katapultrc and restarting katapult? This should fix your problem

Revision history for this message
Harald Sitter (apachelogger) wrote :

 We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in katapult (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.