Bug 1163579

Created attachment 956919 [details]
File: backtrace

Created attachment 956920 [details]
File: cgroup

Created attachment 956921 [details]
File: core_backtrace

Created attachment 956922 [details]
File: dso_list

Created attachment 956923 [details]
File: environ

Created attachment 956924 [details]
File: limits

Created attachment 956925 [details]
File: maps

Created attachment 956926 [details]
File: open_fds

Created attachment 956927 [details]
File: proc_pid_status

Created attachment 956928 [details]
File: var_log_messages

Another user experienced a similar problem:

Trying to report a crash about this same crash which occured after reporting another bug.
Ladies and gentlemen, we have an inception here.
I just reported this bug manually, see #1177333 - maybe this time I'm able to send a full collection of data.
I just used abrt-cli, maybe this one will actually work. If yes, I'll mark #1177333 as duplicate to this one.

reporter:       libreport-2.3.0
backtrace_rating: 4
cmdline:        report-gtk -- /var/tmp/abrt/ccpp-2014-12-26-08:22:38-3407
crash_function: _gdk_x11_display_error_event
executable:     /usr/bin/report-gtk
kernel:         3.17.7-300.fc21.x86_64
package:        libreport-gtk-2.3.0-5.fc21
reason:         report-gtk killed by SIGTRAP
runlevel:       N 5
type:           CCpp
uid:            1000

*** Bug 1177333 has been marked as a duplicate of this bug. ***

Another user experienced a similar problem:

ABRT gui crashes after filling in the "How did this problem happen..." page. (I am having to report this via abrt-cli)

I am using Fedora 21 with MATE desktop.

reporter:       libreport-2.3.0
backtrace_rating: 4
cmdline:        report-gtk -- /var/tmp/abrt/ccpp-2015-01-05-13:49:22-1654
crash_function: _gdk_x11_display_error_event
executable:     /usr/bin/report-gtk
kernel:         3.17.7-300.fc21.x86_64
package:        libreport-gtk-2.3.0-5.fc21
reason:         report-gtk killed by SIGTRAP
runlevel:       N 5
type:           CCpp
uid:            1000

I hit this every time I want to report this gnome-shell crash:
https://retrace.fedoraproject.org/faf/reports/514537/

libreport crashes once I check "I don't know what caused this" and hit Forward.

Created attachment 982954 [details]
Occurs for me every time when I try send this report

I just filed this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1185157

So the crash must be related to the highlighting of potentially sensitive data.

Two days ago I was trying to debug this with Company from #gtk+ on gimpnet. I sent him the whole abrt directory, but report-gtk didn't crash for him. Can the sensitive data detection differ on different machines / under different users?

(In reply to Kamil Páral from comment #17)
Yes, it can. You have to run "report-gtk -e report_Bugzilla -- /var/tmp/abrt/$DIR" to skip the steps which taint the data. With that command line, I can reproduce the crash with your problem directory on F21. I am going to try to reproduce it on Rawhide.

Created attachment 983479 [details]
A gtk application crashing due to too long line in GtkTreeView row

Run ./example.c and you will see. 5039 is the maximum possible characters per single line.

I believe this is a bug in GTK.

Crashes for me as well:

$ bash example.c 

(example:22413): Gdk-ERROR **: The program 'example' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 242 error_code 11 request_code 130 (MIT-SHM) minor_code 5)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
example.c: line 56: 22413 Trace/breakpoint trap   (core dumped) ./example

Running the example or report-gtk with this envvar makes the app not crash:

$ GTK_DEBUG=no-pixel-cache report-gtk -e report_Bugzilla -- /var/tmp/abrt/$DIR

+1, I can't report bug in Nemo due to this bug

Dear users, I wanted to work around this issue by forcing GtkTreeView to wrap long lines, but it seems to be harder than one might think. I have to find a more reliable way how to fix this crash on libreport's side ... I apologise for any inconvenience this might have caused you.

I have to admit that I don't see support for >5000 character lines as a priority. That is not a useful UI, regardless whether we crash or not. Just break your lines.

Thanks Matthias! What is the best way to wrap lines in GtkTreeView rows? I found several tutorials but all of those were suggesting adding about 100 lines of code. Setting "Wrap size" & "Wrap mode" to some values in glade does not work.

Company said he already pushed a fix for this bug into gtk. But I still don't know in which gtk version the fix should appear and how long it will take.

So, it should be in 3.15.5.

I guess this is the update for F21:
https://admin.fedoraproject.org/updates/gtk3-3.14.8-2.fc21

(In reply to Kamil Páral from comment #29)
> I guess this is the update for F21:
> https://admin.fedoraproject.org/updates/gtk3-3.14.8-2.fc21

It does not say it fixes this bug and the example.c file still crashes for me, so I assume the fix has not been pushed to F21 yet. Reopening. Matthias, can you clarify? Thanks.

The fix is 7eecb16404b9fdcd1377e1a159f5e94f079e24b7, which is in 3.15.5. It has not been backported to 3.14 (yet)

the fix was included in 3.14.9