Bug#250547: gnome-cpufreq-applet: 0.1.3-1 crashes the Gnome panel on ppc

[Wolfgang Pfeiffer]

Hi Michel

On Sun, 2004-05-23 at 23:44, Michel Dänzer wrote:
> On Sun, 2004-05-23 at 20:32, Wolfgang Pfeiffer wrote:
> > 
> > After upgrading yesterday gnome-cpufreq-applet to 0.1.3-1, and then 
> > trying to add gnome-cpufreq-applet to the Gnome Panel, the latter 
> > became completely unusable. I.e. I couldn't select a menu item from 
> > there any more.
> > And I could not see anything from gnome-cpufreq-applet at the panel: No icon,
> > no picture. Nothing. IIRC.
> > 
> > I went back to 0.1.2-1, which works without problems here.
> > 
> > Sorry I can't tell more: But the crash was so ugly, that the whole
> > Gnome Session became unusable, due perhaps also to my attempts to fix
> > the problem. And that's why I decided to move back quickly
> > to the previous version.
> 
> I can't reproduce this, it works perfectly on my TiBook. Did the whole
> session freeze for you?

No. IIRC *not* the whole gnome session became unusable: This was a
mistake in my first bug report. Only the panel became unusable. Which in
the end meant I had to do a /etc/init.d/gdm stop 
on a console to log out of Gnome. This because the usable panel here is
the only way out of Gnome. Via the logout menu there. BTW: Is there a
keyboard shortcut to start a logout out of a Gnome session? I didn't
find one so far.

The whole problem rose, IIRC, after doing a
packages update, which included the upgrade  of the
gnome-cpufreq-applet: A reboot was following. Reboot here means I'll be
thrown in a new Gnome session. And this was where the problems started:
I don't remember by now whether after the first reboot the panel was
completely gone or whether it was simply unusable. Unusable hear means:
It didn't response any more to my mouse clicks.
I *think* it didn't react any more:

The launchers that were set up on the panel by myself and not by Gnome
(default ?) panel settings were gone. I didn't see the CPU frequency
applet any more on the panel after the first reboot. IIRC

Let me make this clear: I was in doubt whether it made sense to file a
bug report:

1
Because I removed the latest gnome-cpufreq-applet version and downgraded
to now 0.1.2-1

2
Because I can't be very specific on what was happening: I was so
occupied by the idea to get quickly back to the status quo ante when the
panel was working as expected, that I didn't bother much of making notes
on what exactly is happening when, when the problems appeared.

I decided to write the report in spite of my doubts, as some sort of a
warning message, just in case others might run into the same problems.

After all it took me half of the last weekend to get Gnome back to a
working status.

>  If so, that would rather be an X server and/or
> kernel problem.

Just had a look to /var/log/(messages/syslog/kern.log/XFree86.0.log) and
didn't find any hints on what was going wrong. ~/.xsession-errors here
seems to be rewritten very quickly with the new, current logs. So the
latter didn't help, too.

Sorry.

Best Regards
Wolfgang

-- 
Profile, links: http://profiles.yahoo.com/wolfgangpfeiffer