No shutdown button and unclean shutdown...

English Install/Boot/Login
1

hi there!

Shutdown my lappy this way:

systemctl poweroff

cause no shutdown button…

http://postimg.org/image/jhc05skfz/

systemd-analyze 
Startup finished in 6.878s (kernel) + 45.425s (userspace) = 52.304s


systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

graphical.target @45.417s
└─multi-user.target @45.417s
  └─sshd.service @45.032s +384ms
    └─network.target @45.007s
      └─NetworkManager.service @41.051s +3.955s
        └─basic.target @41.010s
          └─timers.target @41.009s
            └─systemd-tmpfiles-clean.timer @41.005s
              └─sysinit.target @41.004s
                └─apparmor.service @39.158s +1.846s
                  └─systemd-tmpfiles-setup.service @38.996s +161ms
                    └─local-fs.target @38.995s
                      └─var-lock.mount @38.986s +8ms
                        └─local-fs-pre.target @38.985s
                          └─systemd-remount-fs.service @4.790s +34.194s
                            └─systemd-readahead-replay.service @3.214s +1.546s


 systemctl status systemd-remount-fs.service
systemd-remount-fs.service - Remount Root and Kernel File Systems
   Loaded: loaded (/usr/lib/systemd/system/systemd-remount-fs.service; static)
   Active: active (exited) since Tue 2014-03-18 08:25:46 CST; 2h 15min ago
     Docs: man:systemd-remount-fs.service(8)
           http://www.freedesktop.org/wiki/Software/systemd/APIFileSystems
  Process: 266 ExecStart=/usr/lib/systemd/systemd-remount-fs (code=exited, status=0/SUCCESS)
 Main PID: 266 (code=exited, status=0/SUCCESS)

hope some expert help me…too much time to get KDE desktop working( 1:20 sec) | win7 take it 20 sec… something is rotten in this system!
tia!

2

Hi
Can you check the output from the dmesg command for acpi errors and also look in your ~/.xsession-errors file as well.

3 
dmesg

http://paste.opensuse.org/80952986

~/.xsession-errors-:0 

/etc/X11/xim: Checking whether an input method should be started.
sourcing /etc/sysconfig/language to get the value of INPUT_METHOD
INPUT_METHOD is not set or empty (no user selected input method).
Trying to start a default input method for the locale en_US.UTF-8 ...
There is no default input method for the current locale.
Dummy input method "none" (do not use any fancy input method by default)
startkde: Starting up...
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
kbuildsycoca4 running...
Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)
QDBusConnection: name 'org.kde.kglobalaccel' had owner '' but we thought it was ':1.5'
QObject::connect: Cannot connect (null)::resourceScoreUpdated(QString, QString, QString, double) to NepomukPlugin::resourceScoreUpdated(QString, QString, QString, double)
QObject::connect: Cannot connect (null)::recentStatsDeleted(QString, int, QString) to NepomukPlugin::deleteRecentStats(QString, int, QString)
QObject::connect: Cannot connect (null)::earlierStatsDeleted(QString, int) to NepomukPlugin::deleteEarlierStats(QString, int)
QCoreApplication::sendPostedEvents: Cannot send posted events for objects in another thread
QCoreApplication::sendPostedEvents: Cannot send posted events for objects in another thread
QCoreApplication::sendPostedEvents: Cannot send posted events for objects in another thread
QCoreApplication::sendPostedEvents: Cannot send posted events for objects in another thread
QDBusObjectPath: invalid path ""
plasma-desktop(1885)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability 
plasma-desktop(1885)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability 
plasma-desktop(1885)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability 
plasma-desktop(1885): ""geometry" - conversion of "58,2,0,25" to QRectF failed" 
plasma-desktop(1885): ""geometry" - conversion of "58,2,0,25" to QRectF failed" 
plasma-desktop(1885): ""geometry" - conversion of "58,2,0,25" to QRectF failed" 
plasma-desktop(1885)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability 
plasma-desktop(1885)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability 
plasma-desktop(1885)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability 
plasma-desktop(1885)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability 
QGraphicsLinearLayout::insertItem: cannot insert null item
plasma-desktop(1885)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability 
plasma-desktop(1885): ""geometry" - conversion of "58,2,0,25" to QRectF failed" 
Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)
kded(1855)/kdeui (Wallet): The kwalletd service has been disabled 
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
plasma-desktop(1885)/kdeui (Wallet): The kwalletd service has been disabled 
QGraphicsLinearLayout::removeAt: invalid index 0
========================>  7 0
static bool QDeclarativeMetaType::isModule(const QByteArray&, int, int) Qt 4.7 import detected; please note that Qt 4.7 is directly reusable as QtQuick 1.x with no code changes. Continuing, but startup time will be slower. 
Failed to initialize the desktop files database 
kded(1855)/Network Management (NetworkManager backend) ConnectionDbus::fromDbusMap: Setting  "802-1x" not initialized 
kded(1855)/Network Management (NetworkManager backend) ConnectionDbus::fromDbusMap: Setting  "ipv4" not initialized 
kded(1855)/Network Management (NetworkManager backend) ConnectionDbus::fromDbusMap: Setting  "ipv6" not initialized 
kded(1855)/Network Management (NetworkManager backend) ConnectionDbus::fromDbusMap: Setting  "802-1x" not initialized 
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
kded(1855)/Network Management (NetworkManager backend) ConnectionDbus::fromDbusMap: Setting  "802-1x" not initialized 
Adding key-mgmt: wpa-psk 
kded(1855)/Network Management (NetworkManager backend) ConnectionDbus::fromDbusMap: Setting  "802-1x" not initialized 
file:///usr/lib/kde4/imports/org/kde/plasma/components/SectionScroller.qml:103: TypeError: Result of expression 'listView' [null] is not an object.
file:///usr/lib/kde4/imports/org/kde/plasma/components/SectionScroller.qml:175: ReferenceError: Can't find variable: sectionsRepeater
file:///usr/lib/kde4/imports/org/kde/plasma/components/SectionScroller.qml:103: Error: Cannot assign [undefined] to QString
file:///usr/share/kde4/apps/plasma/plasmoids/notifier/contents/ui/devicenotifier.qml:224:13: QML QDeclarativeListView_QML_63: Possible anchor loop detected on fill.
file:///usr/share/kde4/apps/plasma/plasmoids/notifier/contents/ui/devicenotifier.qml:224:13: QML QDeclarativeListView_QML_63: Possible anchor loop detected on fill.
file:///usr/share/kde4/apps/plasma/plasmoids/notifier/contents/ui/devicenotifier.qml:224:13: QML QDeclarativeListView_QML_63: Possible anchor loop detected on fill.
file:///usr/share/kde4/apps/plasma/plasmoids/notifier/contents/ui/devicenotifier.qml:224:13: QML QDeclarativeListView_QML_63: Possible anchor loop detected on fill.
file:///usr/share/kde4/apps/plasma/plasmoids/notifier/contents/ui/devicenotifier.qml:224:13: QML QDeclarativeListView_QML_63: Possible anchor loop detected on fill.
file:///usr/share/kde4/apps/plasma/plasmoids/notifier/contents/ui/devicenotifier.qml:224:13: QML QDeclarativeListView_QML_63: Possible anchor loop detected on fill.
file:///usr/share/kde4/apps/plasma/plasmoids/notifier/contents/ui/devicenotifier.qml:224:13: QML QDeclarativeListView_QML_63: Possible anchor loop detected on fill.
Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)
link XMLID_34_ hasn't been detected!
link XMLID_34_ hasn't been detected!
link XMLID_36_ hasn't been detected!
file:///usr/share/kde4/apps/plasma/plasmoids/battery/contents/ui/CompactRepresentation.qml:73:9: QML Column: Cannot specify top, bottom, verticalCenter, fill or centerIn anchors for items inside Column
file:///usr/lib/kde4/imports/org/kde/plasma/components/Button.qml:194:5: QML Row: Possible anchor loop detected on fill.
file:///usr/lib/kde4/imports/org/kde/plasma/components/Button.qml:194:5: QML Row: Possible anchor loop detected on fill.
link XMLID_34_ hasn't been detected!
link XMLID_34_ hasn't been detected!
link XMLID_36_ hasn't been detected!
Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)
QGridLayoutEngine::addItem: Cell (0, 1) already taken
QGridLayoutEngine::addItem: Cell (0, 1) already taken
QGridLayoutEngine::addItem: Cell (0, 1) already taken
QGridLayoutEngine::addItem: Cell (0, 1) already taken
file:///usr/share/kde4/apps/plasma/packages/org.kde.systemtray/contents/ui/IconsList.qml:53:9: QML MouseRedirectArea: Binding loop detected for property "width"
Failure: Module initialization failed
usage: synaptikscfg -h] --version] {init,load,save} ...
synaptikscfg: error: no touchpad found
New PolkitAgentListener  0x8b25690 
Adding new listener  PolkitQt1::Agent::Listener(0x8c43c78) for  0x8b25690 
Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)
QSystemTrayIcon::setVisible: No Icon set
Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)
I/O warning : failed to load external entity "/usr/share/qalculate/prefixes.xml"
I/O warning : failed to load external entity "/usr/share/qalculate/currencies.xml"
I/O warning : failed to load external entity "/usr/share/qalculate/units.xml"
I/O warning : failed to load external entity "/usr/share/qalculate/functions.xml"
I/O warning : failed to load external entity "/usr/share/qalculate/datasets.xml"
I/O warning : failed to load external entity "/usr/share/qalculate/variables.xml"
I/O warning : failed to load external entity "/usr/share/qalculate/currencies.xml"
I/O warning : failed to load external entity "/home/os/.qalculate/eurofxref-daily.xml"
I/O warning : failed to load external entity "/home/os/.qalculate/eurofxref-daily.xml"
Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)

(process:2067): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
kbuildsycoca4 running...
NOTE: child process received `Goodbye', closing down
plasma-desktop(1885) DeclarativeAppletScript::signalHandlerException: Exception caught:  QVariant(QVariantMap, QMap(("expressionBeginOffset", QVariant(int, 134) ) ( "expressionCaretOffset" ,  QVariant(int, 139) ) ( "expressionEndOffset" ,  QVariant(int, 139) ) ( "fileName" ,  QVariant(QString, "file:///usr/share/kde4/apps/plasma/plasmoids/org.packagekit.updater/contents/ui/main.qml") ) ( "lineNumber" ,  QVariant(int, 129) ) ( "message" ,  QVariant(QString, "Can't find variable: error") ) ( "sourceId" ,  QVariant(int, -1627793320) ) )  ) 
QGridLayoutEngine::addItem: Cell (0, 1) already taken
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 20 (X_GetProperty)
  Resource id:  0x260001a
Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)
Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)

tia!

4

Which display manager are you using?

When there’s no shutdown button, this usually means you are not allowed to shutdown.
If you’re using kdm, what settings do you have in KDE’s Systemsettings (“Configure Desktop”)->“Login Screen”->“Shutdown”?

What does this say?

grep SHUTDOWN /etc/sysconfig/displaymanager
5

hey man…thx a lot!

kdm

~> grep SHUTDOWN /etc/sysconfig/displaymanager
# that root can never login if DISPLAYMANAGER_SHUTDOWN is "auto" and
DISPLAYMANAGER_SHUTDOWN="none"
# that root can never login if DISPLAYMANAGER_SHUTDOWN is "auto" and
6

http://s8.postimg.org/6gcz45apd/z10.jpg](http://postimg.org/image/6gcz45apd/)

7

Maybe this is the problem?
I’m not sure whether this or KDE’s settings (which look fine btw.) take preference in this case.

Edit the file with a text editor and try to change that to

DISPLAYMANAGER_SHUTDOWN="all"
8

Hi
Hopefully wolfi323’s suggestion helps, but I see your running a git
kernel, and all those xsession-errors possibly don’t help?

Did you have the shutdown issue before upgrading the kernel? I’m also
assuming this is a 32bit system?

You do know the widows activation key works for both 32 and 64bit
installs?

–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE 13.1 (Bottle) (x86_64) GNOME 3.10.1 Kernel 3.11.10-7-desktop
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

9

On 2014-03-18 22:39, malcolmlewis wrote:
> Hi
> Hopefully wolfi323’s suggestion helps, but I see your running a git
> kernel, and all those xsession-errors possibly don’t help?

This is also curious:


    0.000000] Kernel command line:
BOOT_IMAGE=/boot/vmlinuz-3.13.6-19.g4727218-default
root=UUID=22dea9b8-1287-4ace-85a8-3c1ce05d9e3f quiet quiet liveinstall
acpi_backlight=vendor
resume=/dev/disk/by-id/ata-TOSHIBA_MK3259GSXP_52RDC3FOT-part5
splash=silent quiet showopts

liveinstall?

–
Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

10

Hi folks!

got now my **shut down **button back followin Wolfi instructions! :good:

and

I’ll appreciate if all of you can give me a hand in this mess…

Did you have the shutdown issue before upgrading the kernel? I’m also
assuming this is a 32bit system?

yep…it is 32 bit system

can’t remember when happened the shutdown issue!

You do know the widows activation key works for both 32 and 64bit
installs?

don’t follow you…

11

Hi
If you wanted to install a 64bit linux system, you can also install a 64bit windows system and use the same activation key…

12

Thx a lot for the advice homie! U ROCK!!

but…

worth it with 2 gb ram?

give me a tip…

You must spread some Reputation around before giving it to malcolmlewis again.
:open_mouth:

13

Hi
I would (well I do even with 2GB of ram with windows installs), but have a think about it for next time, look at some additional ram…

So anyway, you have the shutdown button back, does the system shutdown properly and restart without the checks?

14

Hi!

yep the system shutdown properly!

how to know it (*** the checks*** ) ?

> systemd-analyze 
Startup finished in 6.819s (kernel) + 19.465s (userspace) = 26.284s
os@linux-x0u1:~> systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

graphical.target @19.457s
└─multi-user.target @19.457s
  └─sshd.service @19.207s +249ms
    └─network.target @19.198s
      └─NetworkManager.service @15.119s +4.078s
        └─basic.target @15.070s
          └─timers.target @15.068s
            └─systemd-tmpfiles-clean.timer @15.068s
              └─sysinit.target @15.066s
                └─apparmor.service @9.408s +5.657s
                  └─systemd-tmpfiles-setup.service @8.952s +455ms
                    └─local-fs.target @8.950s
                      └─var-run.mount @8.944s +4ms
                        └─local-fs-pre.target @8.941s
                          └─systemd-remount-fs.service @3.614s +5.325s
                            └─systemd-readahead-replay.service @2.607s +951ms

tia!

15

…?.. …

16

Thought it was fixed? You have a further question?

17

the button was fixed

but …

how to know if

restart without the checks? Malcolm

…?..

18

Well, according to your latest systemd-analyze output, everything looks ok I’d say.
The system boots in 26 seconds (it took 52 seconds before), systemd-remount-fs.service takes 5 seconds to start (was 34 seconds).

Btw, depending on the filesystem you use and its configuration, fsck can be run periodically on boot (in regular intervals or after a certain amount of boots). So it can be normal that single boots take longer than most others.

For the ext filesystems, you can configure those automatic filesystem checks with “tune2fs”. For reiserfs with “tunefs.reiser”.

man tune2fs
man tunefs.reiser
19

On 2014-03-20 20:16, goro goren wrote:
>
> gogalthorp;2631710 Wrote:
>> Thought it was fixed? You have a further question?
>
> the button was fixed
>
> but …
>
> how to know if > restart without the checks? Malcolm

I would make sure to boot in verbose mode, so as to see the boot
messages. Look carefully to see if there is a filesystem check during boot.

I’m not sure this goes into the log.

–
Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

20

I think it does.

You can also run “debugreiserfs /dev/sda1” (for reiserfs) or “debugfs -R show_super_stats /dev/sda1” (for ext) to see when the last fsck was run. (replace /dev/sda1 with the appropriate device files for your partitions)