Bug 120116
Summary: | Rhythmbox crashes on startup itself after upgrading from RedHat 9 to Fedora Core 2 test 2 | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Siddharth Toshniwal <tsiddharth> | ||||
Component: | rhythmbox | Assignee: | Colin Walters <walters> | ||||
Status: | CLOSED NEXTRELEASE | QA Contact: | |||||
Severity: | high | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | rawhide | ||||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | i386 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2004-04-08 14:46:42 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Siddharth Toshniwal
2004-04-06 06:16:47 UTC
Which RPM? Can you give me the exact URL? rpm was: rhythmbox-0.7.2-1 URL: http://mirrors.kernel.org/fedora/core/development/i386/Fedora/RPMS/rhythmbox-0.7.2-1.i386.rpm This is one of the mirrors picked up by up2date on its own. I noticed that the fedora site: http://download.fedora.redhat.com/pub/fedora/linux/core/test/1.91/i386/os/Fedora/RPMS/ has a different (older) version of rhythmbox today. Dunno if it was rolled back or that's the version its supposed to be.... thanks, Siddharth. I can't reproduce this. I purged all my GConf configuration related to Rhythmbox, reinstalled the rhythmbox-0.5.4 rpm with --nodeps, verified that: gconftool-2 -g /apps/rhythmbox/state/play_order returned: "No value set for `/apps/rhythmbox/state/play_order'" Then I installed rhythmbox-0.7.2-1.i386.rpm, launched Rhythmbox, and it worked fine. I suspect something else other than Rhythmbox went wrong on your system. If you can come up with a verifiable way to reproduce this problem, please feel free to reopen this bug. Hi Colin, Took a look at the code using the sources released with gnome 2.6 (downloaded from: http://ftp.gnome.org/pub/GNOME/sources/rhythmbox/0.7/rhythmbox-0.7.2.tar.bz2) From the gdb backtrace that I've sent across earlier in this report and with reference to the file: rhythmbox-0.7.2/shell/rb-shell-player.c On line: 964, we invoke eel_gconf_get_string() which may be returning NULL.... only in case there is something wrong with the gconf settings or so. I noticed this function returns an empty string most usually if the key is not found, but sometimes in error scenarios it _may_ return NULL. Hence we may add a guard against that possibility as is done on line 1003 of that same file (rb-shell-player.c). This should fix the issue as the backtrace suggests it is a NPR. You may please take it as an enhancement to the existing code.... I'm still not able to figure out exactly what is wrong with my Gconf2/eel2 installation. In case I can do that, I'll give further steps to reproduce it at your end. Meanwhile you can change the code for this defensive check.... please revert if this is okay. thanks, Siddharth. PS: My Gconf2 version is: GConf2-2.6.0-3 and eel version is: eel2-2.6.0-1. Anything wrong with these? Created attachment 99227 [details]
suggested fix for null-pointer-read
The suggested fix is enclosed within the comments:
/* ---- Siddharth: Change for seg-fault fix begins ---- */ and
/* ---- Siddharth: Change for seg-fault fix ends ---- */
It's true that eel_gconf_get_string can return NULL in some error conditions, and we should probably handle it. Still though, the fact that it is returning NULL means your system is messed up somehow elsewhere. It shold never return NULL in any kind of normal conditions. I will apply a change similar to your suggested fix. By the way, you should investigate the "diff" program :) |