Description of problem: Go there: http://www.golem.de/news/anwalt-popcorn-time-nutzer-werden-nicht-auf-filesharing-hingewiesen-1501-111827.html Mark and copy the Line "Durchschnittlich fordern die Münchener Anwälte Waldorf Frommer 815 Euro von den Nutzern." until you are under the green bar. (See here: http:////i.imgur.com/7806PAy.png). Go to Pidgin, paste the copyied text. Now you should see something like that in pidgin http://i.imgur.com/XHJe3b8.png now remove this text line that appears. (just hit backspace a several times). I can repruce it everytime. If you've got any questions just reply me by mail pidginbug atsignthingyat WOERM dotsignthingy AT. Version-Release number of selected component: pidgin-2.10.11-1.fc21 Additional info: reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: pidgin crash_function: sighandler environ: executable: /usr/bin/pidgin kernel: 3.17.8-300.fc21.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #2 sighandler at gtkmain.c:179 #4 gtk_widget_set_size_request at gtkwidget.c:8048 #5 gtk_imhtml_size_allocate at gtkimhtml.c:414 #10 gtk_widget_size_allocate at gtkwidget.c:4122 #11 gtk_scrolled_window_size_allocate at gtkscrolledwindow.c:1433 #12 g_cclosure_marshal_VOID__BOXEDv at gmarshal.c:1160 #13 _g_closure_invoke_va at gclosure.c:831 #16 gtk_widget_size_allocate at gtkwidget.c:4122 #17 gtk_box_size_allocate at gtkbox.c:500 #18 g_cclosure_marshal_VOID__BOXEDv at gmarshal.c:1160 Potential duplicate: bug 971451
Created attachment 985319 [details] File: backtrace
Created attachment 985320 [details] File: cgroup
Created attachment 985321 [details] File: core_backtrace
Created attachment 985322 [details] File: dso_list
Created attachment 985323 [details] File: limits
Created attachment 985324 [details] File: maps
Created attachment 985325 [details] File: open_fds
Created attachment 985326 [details] File: proc_pid_status
Created attachment 985327 [details] File: var_log_messages
Created attachment 985328 [details] File: 2015-01-28-204106_465x127_scrot.png
Created attachment 985329 [details] File: screenshot-www golem de 2015-01-28 20-39-46.png
Sorry for the horrible grammar, I was in hurry and I was using the gnome-abrt reporting functionality for the first time.
Ping :)
Another user experienced a similar problem: Pidgin 2.10.x crash when erasing <hr >s in chat window (see https://bugzilla.redhat.com/show_bug.cgi?id=1236550 ) How to reproduce: - create an account (e.g. bonjour protocol) - open a chat with another user - cut & paste an HTML <hr/> - try to delete it using the backspace key - watch Pidgin instantly crashing. reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: pidgin crash_function: sighandler executable: /usr/bin/pidgin kernel: 3.18.8-201.fc21.x86_64 package: pidgin-2.10.11-2.fc21 reason: pidgin killed by SIGABRT runlevel: N 5 type: CCpp uid: 1010
*** Bug 1236550 has been marked as a duplicate of this bug. ***
https://developer.pidgin.im/ticket/16609 cross-link to Pidgin-bugtracker. Similar problem with Debian Testing - so not Fedora specific.
Actually, I just found that a ticket has been opened 17 months ago regarding this issue: https://developer.pidgin.im/ticket/15994 No news since.
Hi, I've closed my issue at the Pidgin bugtracker (duplicate) and linked it to your issue. I hope someone will dig into it.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
*** Bug 1357800 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.