atk_object_set_name: assertion `name != NULL' at startup

[jimav]

Binary package hint: rhythmbox

rhythmbox immediately reports the following errors on the terminal when starting up:

** (rhythmbox:7343): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed

** (rhythmbox:7343): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
WARNING: Unhandled message: interface=org.freedesktop.DBus.Introspectable, path=/, member=Introspect
[jima@lxjima ~]$ r
rhythmbox

** (rhythmbox:7422): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed

** (rhythmbox:7422): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
WARNING: Unhandled message: interface=org.freedesktop.DBus.Introspectable, path=/, member=Introspect

I'll attach an archive of .gconf/apps/rhythmbox in case anything in there is relevant

ProblemType: Bug
Architecture: amd64
Date: Sat Nov 14 13:59:49 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/rhythmbox
Package: rhythmbox 0.12.5-0ubuntu5
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: rhythmbox
Uname: Linux 2.6.31-14-generic x86_64

[Aaron (armahillo)]

I too am getting this error -- I just ran a bunch of updates yesterday and it stopped working. I *can* successfully play music in banshee, though.

[Dapepan (dapepan)]

I have the same problem, any update?

[Pedro Villavicencio (pedro)]

is this still an issue with latest packages?

[jimav (james-avera)]

Pedro, it still happens after doing apt-get update & upgrade. Does it not happen for you?

$dpkg-query -W rhythmbox
rhythmbox 0.12.5-0ubuntu5

The 'About' box says it is version 0.12.5

[Alexander Skiba (ghostlyrics)]

Yes, this still occurs with rhythmbox 0.12.5-0ubuntu5.

[Keith Wilson (keith-wilson)]

I get
** (rhythmbox:3731): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed

(different number) when I start rhythmbox in a terminal. It crashes frequently when playing songs, and sometimes plays two songs at once.
I am not a programmer. so may not understand any replies to this post, but I thought somebody ought to know!!!
Cheers

[Alexander Kiel (alexanderkiel)]

@Keith: This different number is the PID (process identifier).

I'm getting this message to. My version is 0.12.5-0ubuntu5.2. But I get this error not only at startup. Currently I have rhythmbox running for about 12 hours and I got 8 of this errors.

I don't know if this is related, but one day ago rhythmbox locked my whole GUI. I could move my mouse, but all Gnome panels and all apps where unresponsive. I had to log into my computer with ssh and kill rhythmbox.

[Nigel Babu (nigelbabu)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We have a new rhythmbox version in Lucid. If you could test this bug in the new version, this would help us a lot. If you can test it, and it is still an issue, we would appreciate if you could upload updated logs relevant for this particular issue so it can be reported to the developers of the software.

[jimav (james-avera)]

Nigel, The latest in the normal repos for Karmic is 0.12.5-0ubuntu5.2, which still has the problem.
If there is a later version I should try, please post instructions for how to get it. Thanks.

$ sudo apt-get update; sudo apt-get dist-upgrade
$ dpkg-query -W rhythmbox
rhythmbox 0.12.5-0ubuntu5.2
$ rhythmbox
** (rhythmbox:30031): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
** (rhythmbox:30031): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed

[Angel de Jesús Salinas Huerta (elseniordelosacentos)]

mmmm lo mismo aquí

the same here, i can't play my music; does the lucid lynx package works fine¿

[Tmarketing (javiermo-hotmail)]

There is no answer abut this error ??

** (rhythmbox:2907): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
** (rhythmbox:2907): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
WARNING: Unhandled message: interface=org.freedesktop.DBus.Introspectable, path=/, member=Introspect
(<unknown>:2918): GLib-WARNING **: g_set_prgname() called multiple times
(rhythmbox:2907): GLib-CRITICAL **: g_sequence_get: assertion `iter != NULL' failed
Fallo de segmentación

[Tmarketing (javiermo-hotmail)]

Fixed the problem: HOW:

Option 1 )

find the folder rhythmbox under,
/home/(your user name)/.local/share/rhythmbox

and erase the files inside,

Option 2)

Install Banshee and import the rhythmbox playlist files,
banshee open that files and rewrite them and fix the files.. (i think) even lost some playlists.. but fix the rhythmbox problem too.

i fix my rhythmbox in that waty after many days.. i hope help you too!

[JohnZollo (john-zollo)]

I have the same error too. I delete .local/share/rhythmbox and .gconf/apps/rhythmbox. Still, same error. Please tell me what you need. I don't want to HAVE to update to lucid because Canonical is too lazy to fix their bugs. I'd rather use Fedora or CentOS or Windows for that matter.

[JohnZollo (john-zollo)]

Please let me know what logs you need. If there's a FAQ out there, I'll read it. Please send me the link (if there is one). I deleted those configs I mentioned above, please let me know if there's anything you all will need to fix this bug.

Thank you.
Sincerely,
John Zollo

Sorry about my tone before. I'm very disappointed in the stability of Ubuntu and the support of Canonical.

[Sebastien Bacher (seb128)]

Ubuntu is not made only by Canonical, your comments are offensive to the community and Canonical. Did you buy any support to Canonical or why do you think they should give your bugs extra importance over the hundred thousand other open bugs there?

Those updates are mostly volunters work and teams have limited ressources and usually focus on current stable versions and lts versions which are the most used versions. In any case could you get a stacktrace using gdb showing the error and describe what you do exactly to get the bug? Do you get it if accessiblity is not enabled in the users session?

[Sebastien Bacher (seb128)]

is anybody having the issue on lucid?

[jimav (james-avera)]

John,

My impression is that Ubuntu 9.10 was a real slapdash release, a victim of Ubuntu's policy to "ship on time no matter what".
I resisted upgrading to Lucid for a while but eventually did so and it is much better (though Lucid has its own regressions related to HAL being removed, e.g. Banshee can not recognize iPODs any longer.)

Anyway, I'm writing to say that moving to Lucid is probably worthwhile.

My suggestion, if you can manage it, is to move /home to its own disk partition, and then do a full install (not upgrade) onto a new root partition (50G is more than enough). You might be able to save your 9.10 system in another root partition as a backup.

Good luck.
-Jim

________________________________
From: JohnZollo <email address hidden>
To: <email address hidden>
Sent: Thu, June 17, 2010 2:04:54 PM
Subject: [Bug 482820] Re: atk_object_set_name: assertion `name != NULL' at startup

I have the same error too. I delete .local/share/rhythmbox and
.gconf/apps/rhythmbox. Still, same error. Please tell me what you
need. I don't want to HAVE to update to lucid because Canonical is too
lazy to fix their bugs. I'd rather use Fedora or CentOS or Windows for
that matter.

--
atk_object_set_name: assertion `name != NULL' at startup
https://bugs.launchpad.net/bugs/482820
You received this bug notification because you are a direct subscriber
of the bug.

Status in “rhythmbox” package in Ubuntu: Incomplete

Bug description:
Binary package hint: rhythmbox

rhythmbox immediately reports the following errors on the terminal when starting up:

** (rhythmbox:7343): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed

** (rhythmbox:7343): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
WARNING: Unhandled message: interface=org.freedesktop.DBus.Introspectable, path=/, member=Introspect
[jima@lxjima ~]$ r
rhythmbox

** (rhythmbox:7422): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed

** (rhythmbox:7422): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
WARNING: Unhandled message: interface=org.freedesktop.DBus.Introspectable, path=/, member=Introspect

I'll attach an archive of .gconf/apps/rhythmbox in case anything in there is relevant

ProblemType: Bug
Architecture: amd64
Date: Sat Nov 14 13:59:49 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/rhythmbox
Package: rhythmbox 0.12.5-0ubuntu5
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, user)
LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: rhythmbox
Uname: Linux 2.6.31-14-generic x86_64

To unsubscribe from this bug, go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/482820/+subscribe

[JohnZollo (john-zollo)]

Mr. Bacher, I am sorry about my comment before. I know Ubuntu is community maintained -- maybe that's the problem. Maybe I do need to start paying a company to provide me support. I am sick and tired of fixing every little bug and posting to sites like launchpad. I tried running Rhythmbox again with the configs deleted: it would start up, but when I exited the process is still running. I have no idea what's going on. In the meantime I am just going to use Winamp in Windows. I am sick of fixing bugs. If I feel like it, maybe I'll figure out how to use gdb and send you the stack.

I'm sorry -- this is just too much.
Sincerely,
John D. Zollo

[JohnZollo (john-zollo)]

I upgraded to lucid. It looks a lot better now. Will get back to you.

[jimav (james-avera)]

The "CRITICAL" message no longer occurs in 0.12.8-0ubuntu7 (Ubuntu 10.04); I think this ticket can be closed.