No Shutdown

[GoinEasy9]

I've seemed to have lost my Shutdown menu option in System. Also, the icon in the lower right of the login screen doesn't work with reboot or shutdown, Trying to reboot from terminal as root gives me an error:

[root@fedora14dw32 GoinEasy9]# reboot
Trace/breakpoint trap (core dumped)

But "shutdown now" from terminal works.

Is anyone else seeing this? This is a fresh install from when RC3 was released, and started happening when I encountered this error:
https://bugzilla.redhat.com/show_bug.cgi?id=622662
which was a non-stop loop on AVC notifications that I could stop using dismiss right after login. AVC problem is gone with new selinux-policy.

[tox]

I've seemed to have lost my Shutdown menu option in System. Also, the icon in the lower right of the login screen doesn't work with reboot or shutdown, Trying to reboot from terminal as root gives me an error:

[root@fedora14dw32 GoinEasy9]# reboot
Trace/breakpoint trap (core dumped)

But "shutdown now" from terminal works.

Is anyone else seeing this? This is a fresh install from when RC3 was released, and started happening when I encountered this error:
https://bugzilla.redhat.com/show_bug.cgi?id=622662
which was a non-stop loop on AVC notifications that I could stop using dismiss right after login. AVC problem is gone with new selinux-policy.

is this similiar to your issue? http://lists.fedoraproject.org/pipermail/devel/2010-August/141016.html

[GoinEasy9]

Hey dexta
No, not really, I didn't try with a timeout. "Shutdown now" works, but is the only way I can shutdown. Going to shutdown and check logs.

[ovadyah]

same here, no shutdown offered under System, just log out user.
reboot does not work either when trying from log on screen.
both work for me from su in terminal

[GoinEasy9]

I'm also now getting a security alert every time I boot up, but clicking on the alert, it tells me I have no alerts to view.

Messages is adding lines as I'm watching:
Aug 14 22:25:35 fedora14dw32 abrt[2380]: not dumping repeating crash in '/usr/libexec/upowerd'
Aug 14 22:25:37 fedora14dw32 abrt[2415]: not dumping repeating crash in '/usr/libexec/upowerd'
Aug 14 22:25:37 fedora14dw32 abrt[2454]: not dumping repeating crash in '/usr/libexec/upowerd'
Aug 14 22:25:37 fedora14dw32 abrt[2492]: not dumping repeating crash in '/usr/libexec/upowerd'
Aug 14 22:25:37 fedora14dw32 abrt[2528]: not dumping repeating crash in '/usr/libexec/upowerd'
Aug 14 22:25:37 fedora14dw32 abrt[2557]: not dumping repeating crash in '/usr/libexec/upowerd'
Aug 14 22:25:38 fedora14dw32 dbus: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.137" (uid=500 pid=2344 comm="/usr/libexec/gdm-user-switch-applet) interface="org.gnome.DisplayManager.Settings" member="GetValue" error name="(unset)" requested_reply=0 destination="org.gnome.DisplayManager" (uid=0 pid=1209 comm="/usr/sbin/gdm-binary))
Aug 14 22:25:38 fedora14dw32 dbus: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.137" (uid=500 pid=2344 comm="/usr/libexec/gdm-user-switch-applet) interface="org.gnome.DisplayManager.Settings" member="GetValue" error name="(unset)" requested_reply=0 destination="org.gnome.DisplayManager" (uid=0 pid=1209 comm="/usr/sbin/gdm-binary))
Aug 14 22:25:38 fedora14dw32 dbus: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.137" (uid=500 pid=2344 comm="/usr/libexec/gdm-user-switch-applet) interface="org.gnome.DisplayManager.Settings" member="GetValue" error name="(unset)" requested_reply=0 destination="org.gnome.DisplayManager" (uid=0 pid=1209 comm="/usr/sbin/gdm-binary))
Aug 14 22:25:38 fedora14dw32 dbus: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.138" (uid=500 pid=2121 comm="nautilus) interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply=0 destination=":1.30" (uid=0 pid=1600 comm="/usr/sbin/console-kit-daemon))
Aug 14 22:25:39 fedora14dw32 abrt[2602]: not dumping repeating crash in '/usr/libexec/upowerd'
Aug 14 22:25:39 fedora14dw32 abrt[2638]: not dumping repeating crash in '/usr/libexec/upowerd'
Aug 14 22:25:44 fedora14dw32 abrt[2711]: not dumping repeating crash in '/usr/libexec/upowerd'
Aug 14 22:25:44 fedora14dw32 abrt[2675]: saved core dump of pid 2655 (/usr/libexec/upowerd) to /var/spool/abrt/ccpp-1281839144-2655.new/coredump (9375744 bytes)
Aug 14 22:25:44 fedora14dw32 abrtd: Directory 'ccpp-1281839144-2655' creation detected
Aug 14 22:25:44 fedora14dw32 abrtd: Crash is in database already (dup of /var/spool/abrt/ccpp-1281835986-3776)
Aug 14 22:25:44 fedora14dw32 abrtd: Deleting crash ccpp-1281839144-2655 (dup of ccpp-1281835986-3776), sending dbus signal
Aug 14 22:30:05 fedora14dw32 abrt[2891]: not dumping repeating crash in '/usr/libexec/upowerd'
Aug 14 22:30:05 fedora14dw32 abrt[2855]: saved core dump of pid 2835 (/usr/libexec/upowerd) to /var/spool/abrt/ccpp-1281839405-2835.new/coredump (9375744 bytes)
Aug 14 22:30:05 fedora14dw32 abrtd: Directory 'ccpp-1281839405-2835' creation detected
Aug 14 22:30:05 fedora14dw32 abrtd: Crash is in database already (dup of /var/spool/abrt/ccpp-1281835986-3776)
Aug 14 22:30:05 fedora14dw32 abrtd: Deleting crash ccpp-1281839405-2835 (dup of ccpp-1281835986-3776), sending dbus signal

Going to see if it's the same using upstart as the init

---------- Post added at 10:34 PM CDT ---------- Previous post was at 10:33 PM CDT ----------

Thanks ovadayah, misery loves company, at least it's just not me.

---------- Post added at 10:50 PM CDT ---------- Previous post was at 10:34 PM CDT ----------

No joy with init=/sbin/upstart, guess I'll see what provides upowerd ... surprise "upower". Upower came in during install for gdm, but, both were working after install. I'll try to dig a bit deeper.

[ovadyah]

Speaking of company, anyone else unable to use USB? It gives message "Unable to mount ******* Filesystem Not authorized" for both ext HD and thumbdrive. I get a similar error when trying to update with package kit, but not with yumex.:confused:

[GoinEasy9]

Well ovadayah, you have company. Just stuck in a usb stick and it came up with "You are not authorized" error. Got a similar error from packagekit when I tried to install gnome-system-log. It didn't ask for a password, just told me I wasn't authorized. My empty AVC error says it can't read the policy, but when I bring up SELinux troubleshooter from the menu, it shows the policy version.
And although abrt is not coming up for the error, I opened up /var/spool/abrt/ccpp-1281835986-3776 as per:
Aug 14 23:39:37 fedora14dw32 abrtd: Crash is in database already (dup of /var/spool/abrt/ccpp-1281835986-3776)
Aug 14 23:39:37 fedora14dw32 abrtd: Deleting crash ccpp-1281843577-3273 (dup of ccpp-1281835986-3776), sending dbus signal
and found:
Process /usr/libexec/upowerd was killed by signal 6 (SIGABRT)
Need to see if a bugzilla has been filed, or else put together these bits and file a new one.

[errorxp]

I also get the "core dumped" error while trying to reboot from terminal once in a while.

[JEO]

I lost the shutdown option from the system menu on my F14 also. The bug I hate though is that gedit won't work. Says has gtk 2 and 3 mixed in it or something and bombs.

[ovadyah]

Started a download ot rc4 live. See if that fixes anything.

[GoinEasy9]

@JEO
gedit is fixed, do an update.
@ovadyah
I also downloaded RC4, but if your updated, your going to wind up with the same system.

[ovadyah]

Thanks, I had been updated, save for two that would not work. I have extra hd's so I install the latest just to see how it all goes and sometimes it helps. I am through with the first updates, rebooted -- even though it does not request it......the other hundred or so will not go unless I reboot. The shutdown button is still there, and works.

YaHOOO the usb works :D

Wonder what will happen after all the updates :p

165 updates ran no problems, shutdown button not there -- usb does not work again. Phoooeeey

---------- Post added at 11:21 AM CDT ---------- Previous post was at 10:58 AM CDT ----------

Here is the link to the bugz listing.
https://bugzilla.redhat.com/show_bug.cgi?id=623257

Thanks to Tom London who pointed me in the right direction.
;)

[GoinEasy9]

Well I guess I need to search better on bugzilla, I should've used shutdown instead of upower. BTW- all of the other /var/spool/abrt entries were pointing towards gnome-panel, which seems to be the direction that bugzilla is taking. At least I'm learning as I investigate these things.

[ovadyah]

Yep, here also.....I was looking / searching for usb and could not find it....
This is one of the reasons I love Fedora, it stretches the ol grey matter. :cool:

[ovadyah]

I just did all the updates except the nautilus / libcamel one, still no usb use and cannot mount errors are still coming ..... plus no shutdown :confused:

the error reads "package: 1:nautilus-sendto-2.31.6-3.fc14.x86.64 (updates-testing)
Requires: libcamel-1.2.so.19() (64bit)

Is this the problem or something else

Thanks for the help.

[dd_wizard]

I just did all the updates except the nautilus / libcamel one, still no usb use and cannot mount errors are still coming ..... plus no shutdown :confused:

the error reads "package: 1:nautilus-sendto-2.31.6-3.fc14.x86.64 (updates-testing)
Requires: libcamel-1.2.so.19() (64bit)

Is this the problem or something else

Thanks for the help.
From what I see on my system:

[gene@Mobile-PC ~]$ yum list installed nautilus-sendto libcamel
Loaded plugins: auto-update-debuginfo, fastestmirror, presto, refresh-packagekit, remove-with-
: leaves, show-leaves, verify
Installed Packages
nautilus-sendto.x86_64 1:2.31.6-3.fc14 @updates-testing

[gene@Mobile-PC ~]$ locate libcamel
...
/usr/lib64/libcamel-1.2.so.19

[gene@Mobile-PC ~]$ yum whatprovides /usr/lib64/libcamel-1.2.so.19
...
evolution-data-server-2.31.6-1.fc14.x86_64 : Backend data server for Evolution
Repo : installed

[gene@Mobile-PC ~]$ yum list evolution-data-server
...
Installed Packages
evolution-data-server.x86_64 2.31.6-1.fc14 @/evolution-data-server-2.31.6-1.fc14.x86_64
Available Packages
evolution-data-server.i686 2.31.5-1.fc14 fedora

I'd say I downloaded the correct evolution-data-server from koji and installed it to get nautilus-sendto to update. You can do that, too, or wait for it to get pushed to updates-testing.

As for shutdown and the usb issues, they're being addressed in a couple of bugs. For now, "sudo shutdown" in a terminal window seems to be the simplest working alternative.

dd_wizard

[ovadyah]

Thanks very much for your explanation!

[errorxp]

Umm, I installed all updates from updates-testing and now after logging in I have no gnome panels. Shutdown and reboot doesn't work either (from login screen).

[JEO]

Try renaming .gconf directory in your home directory from runlevel 3. Sometimes it can prevent gnome-panel from starting (panels are buggy in the last 3 versions of Fedora).

[dd_wizard]

The two shut down bugs and inability to mount usb storage devices are fixed by the packages linked to from this page (https://admin.fedoraproject.org/updates/polkit-0.97-5.fc14,polkit-gnome-0.97-4.fc14,glib2-2.25.14-2.fc14,upower-0.9.5-7.fc14?_csrf_token=435c4ae4dd210257fcc293011d123fe 87ee7d4cb). The good thing is, it's got +3 karma already so it should hit stable soon.

dd_wizard

[GoinEasy9]

Thanks dd, I see it koji ... page p43, but I'll wait, maybe NetworkManager will get into updates also.

---------- Post added at 11:18 PM CDT ---------- Previous post was at 11:05 PM CDT ----------

Updates coming in now, or at least they're coming through the update list. Large F14 update, crossing fingers.

[ovadyah]

Shutdown and reboot etc all work after tonights updates.

I also have USB devices working as they should.

Way to go!:D

[GoinEasy9]

Just got home ... good to hear ... can't wait.

---------- Post added at 10:44 PM CDT ---------- Previous post was at 09:44 PM CDT ----------

OK, well, did the update, but can't get network to come up automatically, still working on it.
The update brought in a new kernel, which placed itself in second position. The old kernel 2.6.35.2-9.fc14.i686.PAE stayed in the 0 slot, while the new kernel 2.6.35-3.fc14.i686.PAE was in the second slot. I had to edit grub.conf, well I could have changed default to = 1, but that would have just been a problem when the next kernel came in. When I finally booted into the new kernel, I had reboot and shutdown working again.

[andrewthomas]

The update brought in a new kernel, which placed itself in second position. The old kernel 2.6.35.2-9.fc14.i686.PAE stayed in the 0 slot, while the new kernel 2.6.35-3.fc14.i686.PAE was in the second slot. I had to edit grub.conf, well I could have changed default to = 1, but that would have just been a problem when the next kernel came in. When I finally booted into the new kernel, I had reboot and shutdown working again.

The newest kernel is the 2.6.35.2-9, not 2.6.35-3.
2-9>-3
thus 2-9 in the top spot.

[lewis41]

2.6.35-3.fc14 previous
2.6.35.2-9.fc14 next

Not were it simple to name it 2.6.35-3.xyz.fc14 ? My first impression was: why a kernel regression? Then after having spent a few minutes, with grub and this strange naming convention, realized that *35.2* is after *35-* but it was impossible to convince the machine!

[JEO]

2.6.35-3.fc14.i686.PAE

I think they should have named it
2.6.35.0-3.fc14.i686.PAE

To make it clearer for us humans.

[GoinEasy9]

I came home last night after a 12 hour shift ... lol ... your right, my bleary eyes were wrong. Now I've got to put it back, hah, it's still not the dumbest thing I've ever done.

[AdamW]

it's pretty simple. The stuff before the - is the upstream version. The stuff after it is the Fedora revision. The '3' in 2.6.35-3 and the '2' in 2.6.35.2-9 don't have anything to do with each other; 2.6.35-3 is 'upstream 2.6.35, 3rd Fedora revision'. 2.6.35.2-9 is 'upstream 2.6.35.2, 9th Fedora revision'.

For NetworkManager, do 'systemctl enable NetworkManager.service' then 'systemctl start NetworkManager.service' , or just update to the newer package in koji.

[GoinEasy9]

Thanks AdamW, I did learn something about the naming scheme from your post. Fortunately, I will see the dots and dashes better since learning of my goof. Last night only the numbers were registering, especially since the first time I saw them was when grub flashed by fast during boot, from that point on all I saw was the numbers. No excuses, just a localized brain fart.
BTW - NetworkManager from koji is working great. It's nice to see F14 stabilizing.

[lewis41]

Periodic human memory refresh with clear explanations, are always illuminating. :)

Installed from koji NetworkManager-0.8.1-5.git20100818 (i use only wired-ethernet) & gnome-panel-2.31.90-1 with no problems.