Bug 650801 – lyrics plugin ends in segfault

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 650801 - lyrics plugin ends in segfault


Summary:	lyrics plugin ends in segfault


Status:	RESOLVED OBSOLETE

Product:	rhythmbox
Classification:	Other
Component:	Plugins (other)
Version:	unspecified
Hardware:	Other Linux

Importance:	High critical
Target Milestone:	---
Assigned To:	RhythmBox Maintainers
QA Contact:	RhythmBox Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2011-05-22 15:59 UTC by lobo
Modified:	2018-05-24 15:57 UTC

See Also:
GNOME target:	---
GNOME version:	---

Attachments
Patch - Missing variable in Makefile.am (684 bytes, patch) 2011-05-25 08:08 UTC, Pablo Arroyo Loma	committed	Details \| Review

Description lobo 2011-05-22 15:59:44 UTC

when I try to configure lyrics plugin in rhythmbox it crash with this error:


Traceback (most recent call last):

+ Trace 227213

File "/usr/lib/rhythmbox/plugins/lyrics/LyricsConfigureDialog.py", line 46 in do_create_configure_widget
```
builder.add_from_file(rb.find_plugin_file(self, "lyrics-prefs.ui"))
```
File "/usr/lib/python2.7/site-packages/gi/types.py", line 44 in function
```
return info.invoke(*args)
```

TypeError: argument 1: Must be string, not NoneType

Segmentation fault

I'm on arch64 in gnome-shell and everything updated right now, rhythmbox version 2.90.1

Comment 1 Jonathan Matthew 2011-05-22 18:47:27 UTC

Thanks for taking the time to report this bug.
Without a stack trace from the crash it's very hard to determine what caused it.
Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!

Comment 2 Pablo Arroyo Loma 2011-05-25 08:08:41 UTC

Created attachment 188559 [details] [review]
Patch - Missing variable in Makefile.am

Comment 3 Matěj Cepl 2011-05-25 22:54:40 UTC

(In reply to comment #1)
> Thanks for taking the time to report this bug.
> Without a stack trace from the crash it's very hard to determine what caused
> it.
> Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces
> for more information on how to do so. Thanks in advance!

Is this the one?

Program terminated with signal 11, Segmentation fault.

+ Trace 227260

Thread 1 (Thread 0x7ff98a27c9e0 (LWP 5834))

#0 show_configure_cb
at peas-gtk-plugin-manager.c line 248
#1 g_closure_invoke
at gclosure.c line 767
#2 signal_emit_unlocked_R
at gsignal.c line 3252
#3 g_signal_emit_valist
at gsignal.c line 2983
#4 g_signal_emit
at gsignal.c line 3040
#5 gtk_real_button_released
at gtkbutton.c line 1827
#6 g_closure_invoke
at gclosure.c line 767
#7 signal_emit_unlocked_R
at gsignal.c line 3182
#8 g_signal_emit_valist
at gsignal.c line 2983
#9 g_signal_emit
at gsignal.c line 3040
#10 gtk_button_button_release
at gtkbutton.c line 1719
#11 _gtk_marshal_BOOLEAN__BOXED
at gtkmarshalers.c line 85
#12 g_closure_invoke
at gclosure.c line 767
#13 signal_emit_unlocked_R
at gsignal.c line 3290
#14 g_signal_emit_valist
at gsignal.c line 2993
#15 g_signal_emit
at gsignal.c line 3040
#16 gtk_widget_event_internal
at gtkwidget.c line 6114
#17 gtk_propagate_event
at gtkmain.c line 2597
#18 gtk_main_do_event
at gtkmain.c line 1872
#19 gdk_event_source_dispatch
#20 g_main_dispatch
at gmain.c line 2440
#21 g_main_context_dispatch
at gmain.c line 3013
#22 g_main_context_iterate
at gmain.c line 3091
#23 g_main_loop_run
at gmain.c line 3299
#24 gtk_main
at gtkmain.c line 1358
#25 main
at main.c line 332

Comment 4 Matěj Cepl 2011-05-25 22:55:53 UTC

Caught with rhythmbox-2.90.1-10.git20110502.fc15.x86_64

Comment 5 gatlin 2011-05-26 00:54:13 UTC

I tried to run a backtrace, but ABRT wasn't catching the crash. I tried using gdb, but this is the ouput that I got.

[Thread debugging using libthread_db enabled]

(rhythmbox:3083): Rhythmbox-WARNING **: Failed to connect to the session manager: None of the authentication protocols specified are supported


(rhythmbox:3083): Rhythmbox-WARNING **: couldn't connect to session bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[New Thread 0x7fffef08a700 (LWP 3084)]
[New Thread 0x7fffead6f700 (LWP 3085)]
g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.

Program received signal SIGTERM, Terminated.
[Switching to Thread 0x7fffef08a700 (LWP 3084)]
0x000000303520f31b in raise (sig=<optimized out>)
    at ../nptl/sysdeps/unix/sysv/linux/pt-raise.c:42
42				 sig);

Comment 6 Jonathan Matthew 2011-05-27 13:36:22 UTC

Review of attachment 188559 [details] [review]:

I committed this (with a better commit message).  Keeping the bug open because we shouldn't be crashing when a data file can't be found.

Comment 7 Jonathan Matthew 2011-05-27 13:38:46 UTC

I don't think the crash is libpeas' fault, despite that being where it actually happens.  When I tried this here, the pointer returned by the plugin's create_configure_widget was 0x8, which is not something it should have to deal with.

Comment 8 GNOME Infrastructure Team 2018-05-24 15:57:47 UTC

-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/rhythmbox/issues/1086.