kpdf crash when exit from suspend mode

Bug #105116 reported by nitto
4
Affects Status Importance Assigned to Milestone
kdegraphics (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: kdebase

After the boot I click on the exit button of the system menu.
Than I select the suspend button (the orange one). So I wait for suspension. After few seconds I push the power button of my laptop and insert my password, now if I try to open a pdf document or to start kpdf it fails.

My OS is Ubuntu 7.04 and my laptop is an Acer Aspire 1304LC.

Revision history for this message
nitto (nitto) wrote :
nitto (nitto)
description: updated
nitto (nitto)
description: updated
Revision history for this message
Marco Maini (maini10) wrote :

If do you know how to reproduce this bug and still have problem, please follow these instructions:
1) install kdebase-dbg
2) try to reproduce the crash in kpdf: please lauch kpdf from command line with option --nocrashhandler. After kpdf crashes, try /usr/share/apport/apport-checkreports to use apport to report automatically the problem.
3) Reproduce again the problem without --nocrashhandler option. After drkonqui crashes, try /usr/share/apport/apport-checkreports to use apport to report automatically the problem.

Please since Apport will open automatically new reports, insert here their numbers.
Thanks.

Changed in kdebase:
assignee: nobody → maini10
status: New → Incomplete
Revision history for this message
Marco Maini (maini10) 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 package name, under the Affects column, and change the Status back to "New". Thanks again!

Changed in kdebase:
assignee: maini10 → nobody
status: Incomplete → Invalid
Revision history for this message
nitto (nitto) wrote :

hello, I'll try the procedure after the middle of september, because I'm on holiday now and need a fast connection to install the package.

I'll report it as soon as possible.
Thanks

Nitto

nitto (nitto)
Changed in kdebase:
status: Invalid → New
Revision history for this message
nitto (nitto) wrote :

Now I'm working on a Ubuntu 7.04...

Ok, I followed the procedure.
I installed kdebase-dbg and I can reproduce the crash.
I launched kpdf from the command line with --nocrashhandler option and this is the output:

nitto@nittux:~$ kpdf --nocrashhandler
X Error: BadDevice, invalid or uninitialized input device 169
  Major opcode: 145
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 169
  Major opcode: 145
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 169
  Major opcode: 145
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 169
  Major opcode: 145
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
kbuildsycoca running...
Istruzione illecita (core dumped)

Now if I try to launch /usr/share/apport-checkreports it doesn't work. I don't know why.

After I launched kpdf without any option:

nitto@nittux:~$ kpdf
X Error: BadDevice, invalid or uninitialized input device 169
  Major opcode: 145
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 169
  Major opcode: 145
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 169
  Major opcode: 145
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 169
  Major opcode: 145
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
kbuildsycoca running...
KCrash: Application 'kpdf' crashing...
X Error: BadDevice, invalid or uninitialized input device 169
  Major opcode: 145
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 169
  Major opcode: 145
  Minor opcode: 3
  Resource id: 0x0
Failed to open device

Also after this command apport didn't work. If I launch it nothing appear in the command line.

Also no error messages appear after kpdf crash launched by graphic environment.

I'll wait for further suggestions
Nitto

Revision history for this message
nitto (nitto) wrote :

After I launched the command 'kpdf --nocrashhandler in /var/crash/ I found the attached file.

Is it of any help?

Thanks
Bye
Nitto

Revision history for this message
nitto (nitto) wrote :

Or this other one if I lunch only 'kpdf'

Changed in kdebase:
assignee: nobody → maini10
Revision history for this message
Marco Maini (maini10) wrote :

Thanks. Both files seem useful.

Revision history for this message
Marco Maini (maini10) wrote :
Revision history for this message
Marco Maini (maini10) wrote :
Revision history for this message
Marco Maini (maini10) wrote :

Please give a detailed description of steps to reproduce this. Thanks.

Changed in kdebase:
status: New → Incomplete
Revision history for this message
nitto (nitto) wrote :

After the boot I click on the exit button of the system menu.
Than I select the suspend button (the orange one). So I wait for suspension. After few seconds I push the power button of my laptop and insert my password, now if I try to open a pdf document or to start kpdf it fails.

My OS is Ubuntu 7.04 and my laptop is an Acer Aspire 1304LC.

Revision history for this message
Marco Maini (maini10) wrote :

Now, this report seems complete. Confirm this bug, but I'm unable to reproduce it in Gutsy,

description: updated
Changed in kdebase:
assignee: maini10 → nobody
status: Incomplete → Confirmed
Revision history for this message
nitto (nitto) wrote :

I reproduce it also in Gutsy Gibbon...
Nothing is changed.

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Anybody still able to reproduce this with Okular (KPDF-on-steroids) in Intrepid?

Changed in kdebase:
importance: Undecided → Low
status: Confirmed → Incomplete
Revision history for this message
Jonathan Thomas (echidnaman) 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 kdegraphics:
status: Incomplete → 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.