Bug 564388 - [abrt] crash in hplip-gui-3.9.8-28.fc12
Summary: [abrt] crash in hplip-gui-3.9.8-28.fc12
Keywords:
Status: CLOSED DUPLICATE of bug 543286
Alias: None
Product: Fedora
Classification: Fedora
Component: hplip
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Tim Waugh
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:eb62292786344dd4ab90d756d53...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-02-12 15:55 UTC by Morten Arnesen
Modified: 2010-02-24 22:25 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-02-22 13:47:49 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (603 bytes, text/plain)
2010-02-12 15:55 UTC, Morten Arnesen
no flags Details
backtrace (562 bytes, text/plain)
2010-02-18 13:45 UTC, nakieb
no flags Details

Description Morten Arnesen 2010-02-12 15:55:56 UTC
abrt 1.0.6 detected a crash.

architecture: i686
cmdline: python /usr/bin/hp-systray --force-startup
component: hplip
executable: /usr/bin/python
kernel: 2.6.31.12-174.2.19.fc12.i686.PAE
package: hplip-gui-3.9.8-28.fc12
rating: 4
reason: Process was terminated by signal 11 (Segmentation fault)
release: Fedora release 12 (Constantine)

backtrace
-----
BFD: Warning: /var/cache/abrt/ccpp-1265990124-5549/coredump is truncated: expected core file size >= 14819328, found: 2322432.
Core was generated by `python /usr/bin/hp-systray --force-startup'.
Program terminated with signal 11, Segmentation fault.
#0  0x02053c7e in ?? ()

Thread 1 (Thread 5549):
Cannot access memory at address 0xbf9dd570
From        To          Syms Read   Shared Object Library
0x005eb830  0x00602ccf  Yes (*)     /lib/ld-linux.so.2
(*): Shared library is missing debugging information.
No symbol "__abort_msg" in current context.
No symbol "__glib_assert_msg" in current context.

Comment 1 Morten Arnesen 2010-02-12 15:55:58 UTC
Created attachment 390515 [details]
File: backtrace

Comment 2 Tim Waugh 2010-02-12 16:04:28 UTC
For some reason the coredump was truncated, making the stack trace completely useless.

Are you able to trigger this on demand, or was it just a one-off?

Comment 3 nakieb 2010-02-18 13:45:18 UTC
Created attachment 394901 [details]
backtrace

Please check attached Backtrace.

Comment 4 Tim Waugh 2010-02-18 14:50:33 UTC
Same, backtrace is truncated.

Comment 5 nakieb 2010-02-18 16:22:09 UTC
 Bug 543286 - This might be a companion crash

Comment 6 nakieb 2010-02-20 00:41:35 UTC
When trying to reproduce this bug , I opened hplip-gui ., right-clicked hplip apllet in ntification area , chose quit and crash happened; Same as the first time of crash when abrt redirected me to this bug  . This time report was not truncated and abrt redirected me to BUG559454 which is a duplicate of BUG543286 . Please check these bugs.

Comment 7 nakieb 2010-02-21 22:18:57 UTC
(In reply to comment #2)
> For some reason the coredump was truncated, making the stack trace completely
> useless.
> 
> Are you able to trigger this on demand, or was it just a one-off?    

This crash can always created on demand by the following steps:
1.Open hplip-gui while printer is not connected 
2. right-click hplip apllet in noticication area 
3. Chose quit 
4. Crash happnes
5. If crash report is truncated , abrt redirect to this bug
OR if crash report is complete , abrt redirect to bug559454

Comment 8 Jiri Popelka 2010-02-22 13:47:49 UTC
(In reply to comment #7)
> 5. If crash report is truncated , abrt redirect to this bug
> OR if crash report is complete , abrt redirect to bug559454    
Agree.
1.run hp-toolbox from command line
2.menu Device->Quit so you get the prompt line again
3.Right click on HP icon in notification area and select Quit
When the backtrace is not complete it looks like the one in Description of this bug.
When it is complete, abrt redirects to #559454 (duplicate of #543286).
Backtrace contains:
#0  XFreeColormap (dpy=0x0, cmap=113246220) at FreeCmap.c:43
43	FreeCmap.c: No such file or directory.
	in FreeCmap.c
so this is certainly duplicate of #543286.

*** This bug has been marked as a duplicate of bug 543286 ***


Note You need to log in before you can comment on or make changes to this bug.