Bug 1050749 - [abrt] system-config-printer: _g_log_abort(): python2.7 killed by SIGABRT
Summary: [abrt] system-config-printer: _g_log_abort(): python2.7 killed by SIGABRT
Keywords:
Status: CLOSED DUPLICATE of bug 1048227
Alias: None
Product: Fedora
Classification: Fedora
Component: system-config-printer
Version: 20
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tim Waugh
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:b82c17d333075de56dcf0e10d27...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-09 01:34 UTC by collura
Modified: 2014-01-09 13:06 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-01-09 13:06:27 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (76.00 KB, text/plain)
2014-01-09 01:34 UTC, collura 		no flags Details
File: cgroup (177 bytes, text/plain)
2014-01-09 01:34 UTC, collura 		no flags Details
File: core_backtrace (47.55 KB, text/plain)
2014-01-09 01:34 UTC, collura 		no flags Details
File: dso_list (15.80 KB, text/plain)
2014-01-09 01:34 UTC, collura 		no flags Details
File: environ (2.98 KB, text/plain)
2014-01-09 01:34 UTC, collura 		no flags Details
File: limits (1.29 KB, text/plain)
2014-01-09 01:34 UTC, collura 		no flags Details
File: maps (85.35 KB, text/plain)
2014-01-09 01:34 UTC, collura 		no flags Details
File: open_fds (2.45 KB, text/plain)
2014-01-09 01:35 UTC, collura 		no flags Details
File: proc_pid_status (957 bytes, text/plain)
2014-01-09 01:35 UTC, collura 		no flags Details
File: var_log_messages (203 bytes, text/plain)
2014-01-09 01:35 UTC, collura 		no flags Details
View All

Description collura 2014-01-09 01:34:37 UTC 
Description of problem:
unknown.  had just successfully run and closed system-config-printer troubleshoot and about a minute later got this.

Version-Release number of selected component:
system-config-printer-1.4.3-2.fc20

Additional info:
reporter:       libreport-2.1.10
backtrace_rating: 4
cmdline:        /usr/bin/python /usr/share/system-config-printer/system-config-printer.py --debug
crash_function: _g_log_abort
executable:     /usr/bin/python2.7
kernel:         3.13.0-0.rc6.git0.1.fc21.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 _g_log_abort at gmessages.c:255
 #5 _gtk_rbtree_insert_after at gtkrbtree.c:465
 #6 gtk_tree_view_row_inserted at gtktreeview.c:8909
 #11 gtk_tree_model_row_inserted at gtktreemodel.c:1820
 #12 emit_row_inserted_for_node at gtkfilesystemmodel.c:309
 #13 node_set_visible_and_filtered_out at gtkfilesystemmodel.c:359
 #14 node_compute_visibility_and_filters at gtkfilesystemmodel.c:481
 #15 add_file at gtkfilesystemmodel.c:1867
 #16 _gtk_file_system_model_update_file at gtkfilesystemmodel.c:1941
 #17 gtk_file_system_model_query_done at gtkfilesystemmodel.c:1226
Comment 1 collura 2014-01-09 01:34:43 UTC 
Created attachment 847437 [details]
File: backtrace
Comment 2 collura 2014-01-09 01:34:46 UTC 
Created attachment 847438 [details]
File: cgroup
Comment 3 collura 2014-01-09 01:34:48 UTC 
Created attachment 847439 [details]
File: core_backtrace
Comment 4 collura 2014-01-09 01:34:50 UTC 
Created attachment 847440 [details]
File: dso_list
Comment 5 collura 2014-01-09 01:34:52 UTC 
Created attachment 847441 [details]
File: environ
Comment 6 collura 2014-01-09 01:34:55 UTC 
Created attachment 847442 [details]
File: limits
Comment 7 collura 2014-01-09 01:34:59 UTC 
Created attachment 847443 [details]
File: maps
Comment 8 collura 2014-01-09 01:35:02 UTC 
Created attachment 847444 [details]
File: open_fds
Comment 9 collura 2014-01-09 01:35:04 UTC 
Created attachment 847445 [details]
File: proc_pid_status
Comment 10 collura 2014-01-09 01:35:06 UTC 
Created attachment 847446 [details]
File: var_log_messages
Comment 11 collura 2014-01-09 02:12:17 UTC 
while filing this bug the root file system filled from 25percent to 100percent all of which was in /var/log/cups/error_log multi multi gigabyte file.

i had a few boots ago done cups debug 

  systemctl stop cups.service
  cat /dev/null > /var/log/cups/error_log
  cupsctl --LogLevel=Debug2
  systemctl start cups.service

but had later set it back to 

  systemctl stop cups.service
  cupsctl --no-debug-logging
  cat /dev/null > /var/log/cups/error_log
  systemctl start cups.service 

so not sure why file is growing so much with nothing going on.

maybe when i had reset to no debuglogging 
should i have used '--LogLevel=0' instead of '--no-debug-logging' ?

when looked at file was just regular looking log information, though chock full of goodness i am sure.  needed to get something done so punted the file for now but will try to preserve part of it next time.
Comment 12 Tim Waugh 2014-01-09 13:06:27 UTC 
The troubleshooter needs to ensure logging it set to minimal when it fetches the error_log.

*** This bug has been marked as a duplicate of bug 1048227 ***
Note You need to log in before you can comment on or make changes to this bug.