Hi, Recently I upgraded my workstation from Leap to Tumbleweed. I'm using the KDE desktop. Looks like I can't shutdown anymore. When choosing the Shutdown option from the menu, graphics quit OK but I'm at a login console. No shutdown message, nothing, and I have to do a hard reset. Any suggestions ? Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : info@microlinux.fr Tél. : 04 66 63 10 32 Mob. : 06 51 80 12 12
On 2022-09-01 20:22, Nicolas Kovacs wrote:
Hi,
Recently I upgraded my workstation from Leap to Tumbleweed. I'm using the KDE desktop.
Looks like I can't shutdown anymore. When choosing the Shutdown option from the menu, graphics quit OK but I'm at a login console. No shutdown message, nothing, and I have to do a hard reset.
Any suggestions ?
Check if you have unresolved configuration files? run: rpmconfigcheck -- /bengan
Le 01/09/2022 à 20:37, Bengt Gördén a écrit :
Check if you have unresolved configuration files? run: rpmconfigcheck
Right, here goes: [root@alphamule:~] # rpmconfigcheck Searching for unresolved configuration files Please check the following files (see /var/adm/rpmconfigcheck): /etc/chrony.conf.rpmnew /etc/fonts/conf.d/30-metric-aliases.conf.rpmsave /etc/localtime.rpmnew /etc/nsswitch.conf.rpmnew /etc/postfix/main.cf.rpmnew /etc/postfix/master.cf.rpmnew /etc/pulse/client.conf.d/50-system.conf.rpmsave /etc/sane.d/dll.conf.rpmsave /etc/sudoers.rpmnew /etc/sysctl.conf.rpmnew /etc/vbox/vbox.cfg.rpmorig /etc/zypp/zypp.conf.rpmnew /var/lib/unbound/root.key.rpmnew Now what ? -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : info@microlinux.fr Tél. : 04 66 63 10 32 Mob. : 06 51 80 12 12
* Nicolas Kovacs <info@microlinux.fr> [09-01-22 15:11]:
Le 01/09/2022 à 20:37, Bengt Gördén a écrit :
Check if you have unresolved configuration files? run: rpmconfigcheck
Right, here goes:
[root@alphamule:~] # rpmconfigcheck Searching for unresolved configuration files Please check the following files (see /var/adm/rpmconfigcheck): /etc/chrony.conf.rpmnew /etc/fonts/conf.d/30-metric-aliases.conf.rpmsave /etc/localtime.rpmnew /etc/nsswitch.conf.rpmnew /etc/postfix/main.cf.rpmnew /etc/postfix/master.cf.rpmnew /etc/pulse/client.conf.d/50-system.conf.rpmsave /etc/sane.d/dll.conf.rpmsave /etc/sudoers.rpmnew /etc/sysctl.conf.rpmnew /etc/vbox/vbox.cfg.rpmorig /etc/zypp/zypp.conf.rpmnew /var/lib/unbound/root.key.rpmnew
Now what ?
example: meld /etc/chrony.conf.rpmnew /etc/chrony.conf resolve differences wanted (or not) save /etc/chrony.conf, rm /etc/chrony.conf.rpmnew go to the next or use tkdiff
-- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : info@microlinux.fr Tél. : 04 66 63 10 32 Mob. : 06 51 80 12 12
my, long sig :( -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc
Am 01.09.22 um 21:42 schrieb Patrick Shanahan:
* Nicolas Kovacs <info@microlinux.fr> [09-01-22 15:11]:
Le 01/09/2022 à 20:37, Bengt Gördén a écrit :
Check if you have unresolved configuration files? run: rpmconfigcheck
Right, here goes:
[root@alphamule:~] # rpmconfigcheck Searching for unresolved configuration files Please check the following files (see /var/adm/rpmconfigcheck): /etc/chrony.conf.rpmnew /etc/fonts/conf.d/30-metric-aliases.conf.rpmsave /etc/localtime.rpmnew /etc/nsswitch.conf.rpmnew /etc/postfix/main.cf.rpmnew /etc/postfix/master.cf.rpmnew /etc/pulse/client.conf.d/50-system.conf.rpmsave /etc/sane.d/dll.conf.rpmsave /etc/sudoers.rpmnew /etc/sysctl.conf.rpmnew /etc/vbox/vbox.cfg.rpmorig /etc/zypp/zypp.conf.rpmnew /var/lib/unbound/root.key.rpmnew
Now what ?
example: meld /etc/chrony.conf.rpmnew /etc/chrony.conf resolve differences wanted (or not) save /etc/chrony.conf, rm /etc/chrony.conf.rpmnew
go to the next
or use tkdiff
or use midnight commander menue command / compare-files (free tranlation from german) here you have two panels (i think in kdiff also) and you are able to chose what you like to have in your new configuration. -> this makes sense if you have edit the files before to your needs, otherwise it could be overwritten by new (unwanted) config. after that delete the .rmpnew and .rpmsave files. i strongly recomend to copy the .conf AND the .rpmnew/save file before to a backup dir, in case you destroy your config. simoN -- www.becherer.de
On 2022-09-02 07:36, Simon Becherer wrote:
Am 01.09.22 um 21:42 schrieb Patrick Shanahan:
* Nicolas Kovacs <> [09-01-22 15:11]:
Le 01/09/2022 à 20:37, Bengt Gördén a écrit :
Check if you have unresolved configuration files? run: rpmconfigcheck
Right, here goes:
[root@alphamule:~] # rpmconfigcheck Searching for unresolved configuration files Please check the following files (see /var/adm/rpmconfigcheck): /etc/chrony.conf.rpmnew /etc/fonts/conf.d/30-metric-aliases.conf.rpmsave /etc/localtime.rpmnew /etc/nsswitch.conf.rpmnew /etc/postfix/main.cf.rpmnew /etc/postfix/master.cf.rpmnew /etc/pulse/client.conf.d/50-system.conf.rpmsave /etc/sane.d/dll.conf.rpmsave /etc/sudoers.rpmnew /etc/sysctl.conf.rpmnew /etc/vbox/vbox.cfg.rpmorig /etc/zypp/zypp.conf.rpmnew /var/lib/unbound/root.key.rpmnew
Now what ?
example: meld /etc/chrony.conf.rpmnew /etc/chrony.conf resolve differences wanted (or not) save /etc/chrony.conf, rm /etc/chrony.conf.rpmnew
go to the next
or use tkdiff
or use midnight commander menue command / compare-files (free tranlation from german) here you have two panels (i think in kdiff also) and you are able to chose what you like to have in your new configuration. -> this makes sense if you have edit the files before to your needs, otherwise it could be overwritten by new (unwanted) config. after that delete the .rmpnew and .rpmsave files.
Thing is, meld compares both files and allows you to edit both files simultaneously, accepting or rejecting a change line by line, letter by letter, till you are happy, then save, or not.
i strongly recomend to copy the .conf AND the .rpmnew/save file before to a backup dir, in case you destroy your config.
Yes. -- Cheers / Saludos, Carlos E. R. (from 15.3 x86_64 at Telcontar)
Is kdiff3, for KDE, an equivalent tool to Gnome's meld? The man page hardly says anything. -- Robert Webb On Friday, September 2, 2022, 12:53:44 PM PDT, Carlos E. R. <robin.listas@telefonica.net> wrote: Thing is, meld compares both files and allows you to edit both files simultaneously, accepting or rejecting a change line by line, letter by letter, till you are happy, then save, or not.
* Robert Webb <webbdg@verizon.net> [09-02-22 20:08]:
Is kdiff3, for KDE, an equivalent tool to Gnome's meld? The man page hardly says anything. -- Robert Webb
On Friday, September 2, 2022, 12:53:44 PM PDT, Carlos E. R. <robin.listas@telefonica.net> wrote:
Thing is, meld compares both files and allows you to edit both files simultaneously, accepting or rejecting a change line by line, letter by letter, till you are happy, then save, or not.
just installed successfully in tumbleweed, but it does not appear to be as functional as meld or tkdiff, which as almost identical capacity as meld. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc
On 03/09/2022 05:50, Patrick Shanahan wrote:
* Robert Webb <webbdg@verizon.net> [09-02-22 20:08]:
Is kdiff3, for KDE, an equivalent tool to Gnome's meld? The man page hardly says anything. -- Robert Webb
On Friday, September 2, 2022, 12:53:44 PM PDT, Carlos E. R. <robin.listas@telefonica.net> wrote:
Thing is, meld compares both files and allows you to edit both files simultaneously, accepting or rejecting a change line by line, letter by letter, till you are happy, then save, or not.
just installed successfully in tumbleweed, but it does not appear to be as functional as meld or tkdiff, which as almost identical capacity as meld.
There is a utility for KDE called Kompare, which integrates kdiff functionality. Once installed, after selecting two files within the file manager (using Split mode in Dolphin if they are located in different directories), you'll find an option in the program menu or from the context menu to Compare Files. You can also start it directly from the main menu in Plasma. gumb
On 2022-09-01 21:08, Nicolas Kovacs wrote:
Now what ?
Follow this one: https://en.opensuse.org/SDB:Offline_upgrade#Stale_configuration_files PS. I have a "hunch" that Carlos has something to do with that page :) -- /bengan
On 2022-09-01 21:42, Bengt Gördén wrote:
On 2022-09-01 21:08, Nicolas Kovacs wrote:
Now what ?
Follow this one: https://en.opensuse.org/SDB:Offline_upgrade#Stale_configuration_files
PS. I have a "hunch" that Carlos has something to do with that page :)
Yep :-D -- Cheers / Saludos, Carlos E. R. (from 15.3 x86_64 at Telcontar)
On 9/1/22 13:22, Nicolas Kovacs wrote:
Hi,
Recently I upgraded my workstation from Leap to Tumbleweed. I'm using the KDE desktop.
Looks like I can't shutdown anymore. When choosing the Shutdown option from the menu, graphics quit OK but I'm at a login console. No shutdown message, nothing, and I have to do a hard reset.
Any suggestions ?
Niki
If resolving the .rpmnew doesn't resolve the issue, there is also an annoying setting that "only allow root shutdown" is set not only in kdmrc, but also there is a system setting -- that I dealt with in ? sysconfig ? (I can't recall exactly where) But that was new for me in the 15.4 install -- I'd never had a SUSE or openSUSE install set it before. Then Plymouth itself can cause the problem, e.g. see my post from 5/18/22 "Re: 15.4 Beta - Hangs on shutdown (will not turn off - stops with unresponsive text login shown)" My solution: <quote> Hah!, Killed two-birds with one stone. Removing plymouth, e.g. # zypper rm plymouth plymouth-branding-openSUSE plymouth-dracut plymouth-lang plymouth-plugin-label plymouth-plugin-two-step plymouth-scripts plymouth-theme-bgrt plymouth-theme-spinner cured the hang on shutdown issue as well. (I think I recall that being a solution for 15.0 as well) </quote> -- David C. Rankin, J.D.,P.E.
participants (8)
-
Bengt Gördén -
Carlos E. R. -
David C. Rankin -
gumb -
Nicolas Kovacs -
Patrick Shanahan -
Robert Webb -
Simon Becherer