Bug 147675

I think the problem here is that the new modemlights applet depends on
gnome-system-tools which we don't ship

Is present now, but broken. Clicking on it brings up a dialog box saying "Please
start system-config-network with root permissions!".

That shouldn't be necessary. The 'ppp0' device is already configured for user
control -- all I need to do is 'ifup ppp0' and 'ifdown ppp0'.

Does this happen every time you click on the modem lights applet?

Do you have any idea which program generates the "Please start
system-config-network with root permissions!" ?

Actually it happens even before I click on the applet. All I need to do is wait
a few seconds after adding the applet to the panel.

The dialog box is identical to the one I get if I invoke 'system-config-network'
as myself; I assume that's that modem_applet is doing. 

Does it have the right Connection and Disconnection command in the Preferences
dialog ?

Hi,
This should be fixed in gnome-applets-2.10-5 in tomorrow's rawhide.  Can you
test it for me and close the bug if it works?

Sorry, it works better if I remove the old modem_applet which I'd built myself
after first discovering that modemlights had gone away. Its file in
/usr/share/bonobo/servers was overriding the new one from gnome-applets, because
the name changed.

The applet now works OK except for the fact that it has a tendency to die while
being configured (much as gnome-volume-control seems to when you configure that.
The segfaults in that seem to involve gtk_entry_set_visibility too, IIRC.)

Program received signal SIGABRT, Aborted.
[Switching to Thread 807413248 (LWP 3456)]
0x3005affc in raise () from /lib/libc.so.6
(gdb) bt
#0  0x3005affc in raise () from /lib/libc.so.6
#1  0x3005cb00 in abort () from /lib/libc.so.6
#2  0x0f7bc554 in g_logv () from /usr/lib/libglib-2.0.so.0
#3  0x0f7bc5cc in g_log () from /usr/lib/libglib-2.0.so.0
#4  0x0f7bc670 in g_assert_warning () from /usr/lib/libglib-2.0.so.0
#5  0x0191fd84 in gtk_entry_set_visibility () from /usr/lib/libgtk-x11-2.0.so.0
#6  0x0f7b30c4 in g_main_context_wakeup () from /usr/lib/libglib-2.0.so.0
#7  0x0f7b08d4 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#8  0x0f7b4bac in g_main_context_check () from /usr/lib/libglib-2.0.so.0
#9  0x0f7b5004 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#10 0x0e826414 in bonobo_main () from /usr/lib/libbonobo-2.so.0
#11 0x0f7bc554 in g_logv () from /usr/lib/libglib-2.0.so.0
#12 0x002f7573 in ?? ()
#13 0x0f7bc554 in g_logv () from /usr/lib/libglib-2.0.so.0
#14 0x6f72673a in ?? ()
#15 0x0f7bc554 in g_logv () from /usr/lib/libglib-2.0.so.0
Cannot access memory at address 0x7fc34144

So the stack trace isn't very useful; it's lacking debug symbols and it looks
pretty wrong.

If you remove the modem lights applet from you panel, run 
/usr/libexec/modemlights_applet2 in a terminal and then readd modemlights to
your panel, does anything get spewed to the terminal when you reproduce the problem?

If so, can you tell me what it says?

Also if that happens, can you install the debuginfo packages for gnome-applets,
gtk+, and glib and then remove modemlights from your panel, type:

gdb --args /usr/libexec/modemlights_applet2 --g-fatal-warnings
run

and then readd the modemlights applet to your panel, reproduce the problem and
then give me the stack trace.

Hi David,

Are you still seeing this problem?

Yes, but I missed comment #8 in which you requested more information -- sorry.
I'll  do that in the morning; poke me if I forget.

This report targets the FC3 or FC4 products, which have now been EOL'd.

Could you please check that it still applies to a current Fedora release, and
either update the target product or close it ?

Thanks.

Fedora Core 3 and Fedora Core 4 are no longer supported. If you could retest
this issue on a current release or on the latest development / test version, we
would appreciate that. Otherwise, this bug will be marked as CANTFIX one month
from now. Thanks for your help and for your patience.

The information we've requested above is required in order
to review this problem report further and diagnose/fix the
issue if it is still present.  Since there haven't been any
updates to the report in quite a long time now after we've
requested additional information, we're assuming the problem
is either no longer present in our current OS release, or
that there is no longer any interest in tracking the problem.

Setting status to CANTFIX, however if you still
experience this problem after updating to our latest Fedora
Core release and are still interested in Red Hat tracking
the issue, and assisting in troubleshooting the problem,
please feel free to provide the information requested above,
and reopen the report.

Thank you in advance.

(this message is mass message)