Bug 546891 - SIGSEGV inside /usr/lib/libsmbclient.so.0 in /usr/share/system-config-printer/system-config-printer.py
Summary: SIGSEGV inside /usr/lib/libsmbclient.so.0 in /usr/share/system-config-printer...
Keywords:
Status: CLOSED DUPLICATE of bug 552658
Alias: None
Product: Fedora
Classification: Fedora
Component: system-config-printer
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Tim Waugh
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:455154a1aed1da2198a0d5d29d9...
: 548954 549255 550017 550496 551417 551426 551465 552374 552414 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-12-12 14:38 UTC by Bruce Drake
Modified: 2010-01-08 11:49 UTC (History)
16 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-01-08 11:49:57 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (23.90 KB, text/plain)
2009-12-12 14:38 UTC, Bruce Drake
no flags Details

Description Bruce Drake 2009-12-12 14:38:57 UTC
abrt 1.0.0 detected a crash.

How to reproduce
-----
1. Start from fresh system, updated.
2. Open "Printing" from System->Administration menu
3. Click on "New" button
4. Click on "Network Printer" to expand
5. Click on "Find Network Printer"
6. Click on "Find" button without data in the Host box.

Comment
-----
Notes on my local configuration:

This system is the only Linux system on my home network at the time this occurred.  My network is functional and has working exported printers available and visible under Fedora 11 but I have had no success in getting the Samba clients to connect in Fedora 12.

Attached file: backtrace
cmdline: python /usr/share/system-config-printer/system-config-printer.py
component: python
executable: /usr/bin/python
kernel: 2.6.31.6-162.fc12.i686.PAE
package: python-2.6.2-2.fc12
rating: 4
reason: Process was terminated by signal 11

Comment 1 Bruce Drake 2009-12-12 14:38:59 UTC
Created attachment 377877 [details]
File: backtrace

Comment 2 Dave Malcolm 2009-12-14 16:33:58 UTC
Thank you for reporting this bug.

How reproducible is this problem?  If you run the program from a terminal, is an error message printed?

What versions of system-config-printer and libsmbclient do you have installed?

Looking at the backtrace, it looks like the problem occurred in thread #1 inside a call to /usr/lib/libsmbclient.so.0; you'll probably need to install samba-debuginfo before we can figure out what the problem is (sorry, I'm not an expert at printer configuration).

Reassigning component from "python" to "system-config-printer" in the hope of more insight.

Comment 3 Tim Waugh 2009-12-14 16:57:22 UTC
The most obvious problem is that it is possible to click "Find" without having first entered a hostname.

I haven't been able to reproduce the crash here though.  As Dave suggested, installing samba-debuginfo will show exactly where the crash happens, and that might make it clear why it happens.

Comment 4 Jiri Popelka 2009-12-14 17:16:21 UTC
Here's the procedure.

Please run 'debuginfo-install system-config-printer samba libsmbclient' as root,
then use abrt to re-trace the crash: Application->System Tools->Automatic Bug Reporting Tool;
double-click on the line corresponding to this crash; then click 'Refresh'. 
Copy and paste the backtrace into this bug report by clicking on the text that
says "Core was generated by ...", right-clicking and selecting 'Select All',
right-clicking again and selecting 'Copy'.

Then, in this Bugzilla bug report, right-click on the additional comments box
and select 'Paste'.  Thanks!

Comment 5 Dave Malcolm 2009-12-21 19:32:34 UTC
*** Bug 548954 has been marked as a duplicate of this bug. ***

Comment 6 Dave Malcolm 2009-12-21 20:28:31 UTC
*** Bug 549255 has been marked as a duplicate of this bug. ***

Comment 7 Dave Malcolm 2009-12-23 15:19:52 UTC
*** Bug 550017 has been marked as a duplicate of this bug. ***

Comment 8 Dave Malcolm 2010-01-04 18:16:28 UTC
*** Bug 550496 has been marked as a duplicate of this bug. ***

Comment 9 Dave Malcolm 2010-01-04 18:53:00 UTC
*** Bug 551417 has been marked as a duplicate of this bug. ***

Comment 10 Dave Malcolm 2010-01-04 18:54:01 UTC
*** Bug 551426 has been marked as a duplicate of this bug. ***

Comment 11 Dave Malcolm 2010-01-04 18:54:47 UTC
*** Bug 551465 has been marked as a duplicate of this bug. ***

Comment 12 Dave Malcolm 2010-01-04 20:55:05 UTC
*** Bug 552374 has been marked as a duplicate of this bug. ***

Comment 13 Dave Malcolm 2010-01-05 17:52:38 UTC
*** Bug 552414 has been marked as a duplicate of this bug. ***

Comment 14 Tim Waugh 2010-01-08 11:49:57 UTC

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


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