Upgrade from Leap 15.1 to 15.2 Desktop Failure
Greetings, Just did an upgrade from my stable Leap 15.1 install to 15.2. I downloaded the DVD and did the upgrade from booting that. It asked me if I wanted to used the online repos as I have an internet connection so I said OK. Everything seemed to go well and booting into my KDE desktop. But clicking the gecko start menu gives an error. "Error loading QML file:file///sur/share/plasma/plasmoids/org.kde.plasma.kicker/contents/ui/main.qml:27:1: module "org.kde.plasma.private.kicker: is not installed" The system is running and I see my desktop widgets doing their thing. But I can't do anything. I can get to tty1 and login as root but I don't know what to do from there. I tried running yast in tty1 but get errors when I try software management. This system was first installed with Leap 15.0, upgraded to 15.1, now to a partially broken 15.2. Any suggestions most welcome. Jim F
On 19/12/2020 03.11, Jim Flanagan wrote:
Greetings,
Just did an upgrade from my stable Leap 15.1 install to 15.2. I downloaded the DVD and did the upgrade from booting that. It asked me if I wanted to used the online repos as I have an internet connection so I said OK. Everything seemed to go well and booting into my KDE desktop. But clicking the gecko start menu gives an error.
"Error loading QML file:file///sur/share/plasma/plasmoids/org.kde.plasma.kicker/contents/ui/main.qml:27:1: module "org.kde.plasma.private.kicker: is not installed"
The system is running and I see my desktop widgets doing their thing. But I can't do anything. I can get to tty1 and login as root but I don't know what to do from there.
I tried running yast in tty1 but get errors when I try software management.
Which errors? Give details, please.
This system was first installed with Leap 15.0, upgraded to 15.1, now to a partially broken 15.2.
Any suggestions most welcome.
The first step is to repair all rpm configs. Run "rpmconfigcheck" and repair all those that result. Some instructions here "<https://en.opensuse.org/SDB:Offline_upgrade>" (section "Stale configuration files"). If Plasma doesn't start, use another desktop, there are many. You can also try creating a new user. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 12/18/20 8:21 PM, Carlos E. R. wrote:
On 19/12/2020 03.11, Jim Flanagan wrote:
Greetings,
Just did an upgrade from my stable Leap 15.1 install to 15.2. I downloaded the DVD and did the upgrade from booting that. It asked me if I wanted to used the online repos as I have an internet connection so I said OK. Everything seemed to go well and booting into my KDE desktop. But clicking the gecko start menu gives an error.
"Error loading QML file:file///sur/share/plasma/plasmoids/org.kde.plasma.kicker/contents/ui/main.qml:27:1: module "org.kde.plasma.private.kicker: is not installed"
Above is the error when clicking the start menu.
The system is running and I see my desktop widgets doing their thing. But I can't do anything. I can get to tty1 and login as root but I don't know what to do from there.
I tried running yast in tty1 but get errors when I try software management.
Which errors? Give details, please.
Runing yast in tty1, then selecting Software Management returns this eerror: "Internal error. Please report a but report with logs. Run save_y2logs to get complete logs. Caller: /usr/lib64/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 'require' Details: Failed to load Module 'Packages' due to: Failed to load Module "AddOnProduct' due to "cannot load such file -- y2packager/repository"
This system was first installed with Leap 15.0, upgraded to 15.1, now to a partially broken 15.2.
Any suggestions most welcome.
The first step is to repair all rpm configs.
Run "rpmconfigcheck" and repair all those that result.
Some instructions here "<https://en.opensuse.org/SDB:Offline_upgrade>" (section "Stale configuration files").
If Plasma doesn't start, use another desktop, there are many. You can also try creating a new user.
Jim F
Jim Flanagan wrote:
On 12/18/20 8:21 PM, Carlos E. R. wrote:
On 19/12/2020 03.11, Jim Flanagan wrote:
Greetings,
Just did an upgrade from my stable Leap 15.1 install to 15.2. I downloaded the DVD and did the upgrade from booting that. It asked me if I wanted to used the online repos as I have an internet connection so I said OK. Everything seemed to go well and booting into my KDE desktop. But clicking the gecko start menu gives an error.
"Error loading QML
file:file///sur/share/plasma/plasmoids/org.kde.plasma.kicker/contents/ui/main.qml:27:1:
module "org.kde.plasma.private.kicker: is not installed"
Above is the error when clicking the start menu.
If you google it, there are a few hits on the very same - some issue with upgrading your account. I didn't see any obvious solution.
Runing yast in tty1, then selecting Software Management returns this eerror: "Internal error. Please report a but report with logs. Run save_y2logs to get complete logs.
Caller: /usr/lib64/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 'require'
Details: Failed to load Module 'Packages' due to: Failed to load Module "AddOnProduct' due to "cannot load such file -- y2packager/repository"
Something went wrong in your upgrade I think. On the assumption you have the standard set of repositories defined, running a "zypper dup" might clear up things. -- Per Jessen, Zürich (1.1°C)
On 19/12/2020 03.29, Jim Flanagan wrote:
On 12/18/20 8:21 PM, Carlos E. R. wrote:
On 19/12/2020 03.11, Jim Flanagan wrote:
Runing yast in tty1, then selecting Software Management returns this eerror: "Internal error. Please report a but report with logs. Run save_y2logs to get complete logs.
Caller: /usr/lib64/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 'require'
Details: Failed to load Module 'Packages' due to: Failed to load Module "AddOnProduct' due to "cannot load such file -- y2packager/repository"
Please run this long command: rpm -q -a --queryformat "%{INSTALLTIME}\t%{INSTALLTIME:day} \ %{BUILDTIME:day} %-30{NAME}\t%15{VERSION}-%-7{RELEASE}\t%{arch} \ %25{VENDOR}%25{PACKAGER} == %{DISTRIBUTION} %{DISTTAG}\n" \ | sort | cut --fields="2-" | tee rpmlist.txt \ | egrep -v "openSUSE Leap 15\.2|openSUSE_Leap_15.2|-lp152" \
rpmlist_hits.txt
And then: susepaste -n "Jim F" -t "possible wrong rpms" -e 151200 rpmlist_hits.txt And post on this thread the resulting link. This is documented here: <https://en.opensuse.org/SDB:Offline_upgrade#Packages_not_updated> I just reviewed that section. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 19/12/2020 12.44, Carlos E. R. wrote:
On 19/12/2020 03.29, Jim Flanagan wrote:
On 12/18/20 8:21 PM, Carlos E. R. wrote:
On 19/12/2020 03.11, Jim Flanagan wrote:
Runing yast in tty1, then selecting Software Management returns this eerror: "Internal error. Please report a but report with logs. Run save_y2logs to get complete logs.
Caller: /usr/lib64/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 'require'
Details: Failed to load Module 'Packages' due to: Failed to load Module "AddOnProduct' due to "cannot load such file -- y2packager/repository"
Please run this long command:
rpm -q -a --queryformat "%{INSTALLTIME}\t%{INSTALLTIME:day} \ %{BUILDTIME:day} %-30{NAME}\t%15{VERSION}-%-7{RELEASE}\t%{arch} \ %25{VENDOR}%25{PACKAGER} == %{DISTRIBUTION} %{DISTTAG}\n" \ | sort | cut --fields="2-" | tee rpmlist.txt \ | egrep -v "openSUSE Leap 15\.2|openSUSE_Leap_15.2|-lp152" \
rpmlist_hits.txt
And then:
susepaste -n "Jim F" -t "possible wrong rpms" -e 151200 rpmlist_hits.txt
And post on this thread the resulting link.
I forgot. I also want to see: zypper lr --details > repolist.txt susepaste -n "Jim F" -t "possible wrong rpms" -e 151200 repolist.txt And post on this thread the resulting link as well. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 12/19/20 5:47 AM, Carlos E.R. wrote:
On 19/12/2020 12.44, Carlos E. R. wrote:
On 19/12/2020 03.29, Jim Flanagan wrote:
On 12/18/20 8:21 PM, Carlos E. R. wrote:
On 19/12/2020 03.11, Jim Flanagan wrote:
Runing yast in tty1, then selecting Software Management returns this eerror: "Internal error. Please report a but report with logs. Run save_y2logs to get complete logs.
Caller: /usr/lib64/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 'require'
Details: Failed to load Module 'Packages' due to: Failed to load Module "AddOnProduct' due to "cannot load such file -- y2packager/repository"
Please run this long command:
rpm -q -a --queryformat "%{INSTALLTIME}\t%{INSTALLTIME:day} \ %{BUILDTIME:day} %-30{NAME}\t%15{VERSION}-%-7{RELEASE}\t%{arch} \ %25{VENDOR}%25{PACKAGER} == %{DISTRIBUTION} %{DISTTAG}\n" \ | sort | cut --fields="2-" | tee rpmlist.txt \ | egrep -v "openSUSE Leap 15\.2|openSUSE_Leap_15.2|-lp152" \
rpmlist_hits.txt
Ok trying to type this in tty is pretty trying. I typed it twice and still got it wrong. I read the artile you linked to on this one. So I don't have a txt file to send yet. Will try again in a bit.
And then:
susepaste -n "Jim F" -t "possible wrong rpms" -e 151200 rpmlist_hits.txt
Again, I'm not sure how to post a link from a tty terminal.
And post on this thread the resulting link.
I forgot. I also want to see:
zypper lr --details > repolist.txt
susepaste -n "Jim F" -t "possible wrong rpms" -e 151200 repolist.txt
And post on this thread the resulting link as well.
Jim F
On 19/12/2020 19.07, Jim Flanagan wrote:
On 12/19/20 5:47 AM, Carlos E.R. wrote:
On 19/12/2020 12.44, Carlos E. R. wrote:
On 19/12/2020 03.29, Jim Flanagan wrote:
On 12/18/20 8:21 PM, Carlos E. R. wrote:
On 19/12/2020 03.11, Jim Flanagan wrote:
Please run this long command:
rpm -q -a --queryformat "%{INSTALLTIME}\t%{INSTALLTIME:day} \ %{BUILDTIME:day} %-30{NAME}\t%15{VERSION}-%-7{RELEASE}\t%{arch} \ %25{VENDOR}%25{PACKAGER} == %{DISTRIBUTION} %{DISTTAG}\n" \ | sort | cut --fields="2-" | tee rpmlist.txt \ | egrep -v "openSUSE Leap 15\.2|openSUSE_Leap_15.2|-lp152" \ > rpmlist_hits.txt
Ok trying to type this in tty is pretty trying. I typed it twice and still got it wrong. I read the artile you linked to on this one. So I don't have a txt file to send yet. Will try again in a bit.
Why don't you paste the command? How do you copy and paste a file in Linux terminal? If you just want to copy a piece of text in the terminal, all you need to do is highlight it with your mouse, then press Ctrl + Shift + C to copy. To paste it where the cursor is, use the keyboard shortcut Ctrl + Shift + V .13 ago 2020 <https://www.maketecheasier.com/copy-paste-files-linux-command-line/>
And then:
susepaste -n "Jim F" -t "possible wrong rpms" -e 151200 rpmlist_hits.txt
Again, I'm not sure how to post a link from a tty terminal.
Just copy paste it from terminal to mail window, using the mouse. Otherwise, just post the number of the link, I can get the rest. Or do you mean that you don't have graphics on your computer, so can not paste to from mail? That you are running text mode? The easiest, is to access your machine using ssh from another machine. You can also activate the mouse in text mode starting service "gpm", but the wizard to configure it in YaST is gone. /etc/sysconfig/mouse: MOUSEDEVICE="/dev/psaux" MOUSETYPE="exps2" *Might* work. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 12/19/20 12:07 PM, Jim Flanagan wrote:
Again, I'm not sure how to post a link from a tty terminal.
Jim, You need to install the 'susepaste' package, then you can use the command-line commands that Carlos gave you to post to the susepaste site. The contents of the command will show up on: http://paste.opensuse.org/ You can see all the recent pastes at: https://paste.opensuse.org/lists The susepaste command just automates posting to the site. (it's just a bash script) -- David C. Rankin, J.D.,P.E.
On 20/12/2020 06.54, David C. Rankin wrote:
On 12/19/20 12:07 PM, Jim Flanagan wrote:
Again, I'm not sure how to post a link from a tty terminal.
Jim,
You need to install the 'susepaste' package, then you can use the command-line commands that Carlos gave you to post to the susepaste site. The contents of the command will show up on:
You can see all the recent pastes at:
https://paste.opensuse.org/lists
The susepaste command just automates posting to the site. (it's just a bash script)
He means the link that the susepaste command produces. He is in text mode and doesn't know how to put that in the email. There is no need to post the full link, we only need the number. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 12/20/20 5:18 AM, Carlos E. R. wrote:
He means the link that the susepaste command produces. He is in text mode and doesn't know how to put that in the email.
There is no need to post the full link, we only need the number.
Oh, duh.... Then you can redirect the output to a temporary file and read the output into the e-mail message (it's only 4-lines). Then delete the 3 you don't want :) -- David C. Rankin, J.D.,P.E.
On 22/12/2020 08.52, David C. Rankin wrote:
On 12/20/20 5:18 AM, Carlos E. R. wrote:
He means the link that the susepaste command produces. He is in text mode and doesn't know how to put that in the email.
There is no need to post the full link, we only need the number.
Oh, duh....
Then you can redirect the output to a temporary file and read the output into the e-mail message (it's only 4-lines). Then delete the 3 you don't want :)
Apparently, the "susepaste" command doesn't work for him. I don't know which is the error. He has to use the web. But he now has a full desktop working. Plasma runs, but the start menu is dead, so he is using IceWM. And yast package manager fails to start, but he can make do using "yast online update" instead. So there is some progress. I think the next step must be to handle the rpmorig/rpmnew files. This we do with "meld", but the last time we tried it would not run, I don't know now. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
* Carlos E. R. <robin.listas@telefonica.net> [12-22-20 04:24]: [...]
And yast package manager fails to start, but he can make do using "yast online update" instead.
So there is some progress.
I think the next step must be to handle the rpmorig/rpmnew files. This we do with "meld", but the last time we tried it would not run, I don't know now.
if meld will not run, try tkdiff it is very similar to meld. I used tkdiff before I knew about 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 freenode
On 22/12/2020 14.17, Patrick Shanahan wrote:
* Carlos E. R. <> [12-22-20 04:24]: [...]
And yast package manager fails to start, but he can make do using "yast online update" instead.
So there is some progress.
I think the next step must be to handle the rpmorig/rpmnew files. This we do with "meld", but the last time we tried it would not run, I don't know now.
if meld will not run, try tkdiff it is very similar to meld. I used tkdiff before I knew about meld.
YES! Very good idea. I must remember to edit the wiki. I have it installed, but totally forgot about it. I even see it in my notes. I have two others: utils diff: kdiff3 tkdiff * fldiff meld - very good edit / comparator -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 12/18/20 8:21 PM, Carlos E. R. wrote:
On 19/12/2020 03.11, Jim Flanagan wrote:
Greetings,
Just did an upgrade from my stable Leap 15.1 install to 15.2. I downloaded the DVD and did the upgrade from booting that. It asked me if I wanted to used the online repos as I have an internet connection so I said OK. Everything seemed to go well and booting into my KDE desktop. But clicking the gecko start menu gives an error.
"Error loading QML file:file///sur/share/plasma/plasmoids/org.kde.plasma.kicker/contents/ui/main.qml:27:1: module "org.kde.plasma.private.kicker: is not installed"
The system is running and I see my desktop widgets doing their thing. But I can't do anything. I can get to tty1 and login as root but I don't know what to do from there.
I tried running yast in tty1 but get errors when I try software management.
Which errors? Give details, please.
This system was first installed with Leap 15.0, upgraded to 15.1, now to a partially broken 15.2.
Any suggestions most welcome.
The first step is to repair all rpm configs.
Run "rpmconfigcheck" and repair all those that result.
Some instructions here "<https://en.opensuse.org/SDB:Offline_upgrade>" (section "Stale configuration files").
If Plasma doesn't start, use another desktop, there are many. You can also try creating a new user.
Running rpmconfigcheck lists over a screens worth of .rpmnew mentions. I have not found any man page to show me options for fixing this with rpmconfigcheck. I may try a new user but I'm way out of practice in command line. Jim F
On 19/12/2020 18.58, Jim Flanagan wrote:
On 12/18/20 8:21 PM, Carlos E. R. wrote:
On 19/12/2020 03.11, Jim Flanagan wrote:
...
Any suggestions most welcome.
The first step is to repair all rpm configs.
Run "rpmconfigcheck" and repair all those that result.
Some instructions here "<https://en.opensuse.org/SDB:Offline_upgrade>" (section "Stale configuration files").
If Plasma doesn't start, use another desktop, there are many. You can also try creating a new user.
Running rpmconfigcheck lists over a screens worth of .rpmnew mentions. I have not found any man page to show me options for fixing this with rpmconfigcheck.
I wrote the documentation on what you must do with the output of rpmconfigcheck (I sent you the link), so just do it. Yes, a pagefull, so you just have work to do. Get to it :-) -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 12/18/20 8:21 PM, Carlos E. R. wrote:
On 19/12/2020 03.11, Jim Flanagan wrote:
Greetings,
Just did an upgrade from my stable Leap 15.1 install to 15.2. I downloaded the DVD and did the upgrade from booting that. It asked me if I wanted to used the online repos as I have an internet connection so I said OK. Everything seemed to go well and booting into my KDE desktop. But clicking the gecko start menu gives an error.
"Error loading QML file:file///sur/share/plasma/plasmoids/org.kde.plasma.kicker/contents/ui/main.qml:27:1: module "org.kde.plasma.private.kicker: is not installed"
The system is running and I see my desktop widgets doing their thing. But I can't do anything. I can get to tty1 and login as root but I don't know what to do from there.
I tried running yast in tty1 but get errors when I try software management.
Which errors? Give details, please.
This system was first installed with Leap 15.0, upgraded to 15.1, now to a partially broken 15.2.
Any suggestions most welcome.
The first step is to repair all rpm configs.
Run "rpmconfigcheck" and repair all those that result.
Some instructions here "<https://en.opensuse.org/SDB:Offline_upgrade>" (section "Stale configuration files").
If Plasma doesn't start, use another desktop, there are many. You can also try creating a new user.
Creating a new user did not resolve this issue. Jim F
Jim Flanagan composed on 2020-12-18 20:11 (UTC-0600): ...
This system was first installed with Leap 15.0, upgraded to 15.1, now to a partially broken 15.2.
Any suggestions most welcome.
If you login to an IceWM session instead of Plasma, does everything there work? To confirm the upgrade went as it should have, from any of the vttys, try: sudo zypper ref sudo zypper dup If no errors, but still fubar Plasma, try: sudo zypper ve If trouble still, attach to an email (not cut and paste within) output from: sudo zypper lr -d Maybe first try something simpler. Logged on a vtty instead of Plasma, delete the content of ~/.cache/, then start a Plasma session. -- Evolution as taught in public schools, like religion, is based on faith, not on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
On 12/18/20 9:17 PM, Felix Miata wrote:
Jim Flanagan composed on 2020-12-18 20:11 (UTC-0600): ...
This system was first installed with Leap 15.0, upgraded to 15.1, now to a partially broken 15.2.
Any suggestions most welcome.
If you login to an IceWM session instead of Plasma, does everything there work?
To confirm the upgrade went as it should have, from any of the vttys, try:
sudo zypper ref sudo zypper dup
OK did the ref and it updated the repos. Running zypper dup returned: The following NEW package is going to be installed: openSUSE-release-ftp The following 7 packages are going to be REMOVED: aaa_base aaa_base-extras kpartx kpartx libefivar1 multipath-tools multipath-tools The following 9 packages are going to be upgraded: gio-branding-openSUSE glib2-lang glib2-tools libgio-2_0.0 libglib-2_0-0 libmodule-2_0.0 libgobject-2_0.0 libgthread-2_0.0 yast2-packager The new and updates packages returned no errors, but I got errors on deleting the 7 packages saying they weren't installed. At the first error I tried "retry", but got the same error. So I tried "ignore" on them all. On one I got a different message. Removing multipath-tools-0.7.9+195+suse.16740c5-lp151.2.12.1.x86_64 ..........done Additonal rpm output: Failed to try-restart multipath.services: Unit multipath.service not found. After installing the remaining updates it finished with this message. Problem occurred during or after installation or removal of packages: Failed to cache rpm database (1). History: - 'rpmdb2solv' '-r' '/' '-X' '-o' '/etc/products.d' '/var/cache/zypp/solv/@System/solv' 'o' '/var/cache/zypp/solv/@System/solvc1qmx9' rpmdb2solv: inconsistent rpm database, key 6548 not found. run 'rpm --rebuilddb' to fix. Please see the above error message for a hint. I think I got that typed correctly. BTW I was in tty while running in init 5 (that was on F7), I was in F1. Jim F
If no errors, but still fubar Plasma, try:
sudo zypper ve
If trouble still, attach to an email (not cut and paste within) output from:
sudo zypper lr -d
Maybe first try something simpler. Logged on a vtty instead of Plasma, delete the content of ~/.cache/, then start a Plasma session.
On 19/12/2020 19.39, Jim Flanagan wrote:
On 12/18/20 9:17 PM, Felix Miata wrote:
Jim Flanagan composed on 2020-12-18 20:11 (UTC-0600): ...
This system was first installed with Leap 15.0, upgraded to 15.1, now to a partially broken 15.2.
Any suggestions most welcome.
If you login to an IceWM session instead of Plasma, does everything there work?
To confirm the upgrade went as it should have, from any of the vttys, try:
sudo zypper ref sudo zypper dup
OK did the ref and it updated the repos. Running zypper dup returned:
You should not have done that till completed my instructions.
The following NEW package is going to be installed: openSUSE-release-ftp
The following 7 packages are going to be REMOVED: aaa_base aaa_base-extras kpartx kpartx libefivar1
I would be very worried at seeing that message.
After installing the remaining updates it finished with this message. Problem occurred during or after installation or removal of packages: Failed to cache rpm database (1). History: - 'rpmdb2solv' '-r' '/' '-X' '-o' '/etc/products.d' '/var/cache/zypp/solv/@System/solv' 'o' '/var/cache/zypp/solv/@System/solvc1qmx9' rpmdb2solv: inconsistent rpm database, key 6548 not found. run 'rpm --rebuilddb' to fix.
Oh shit. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 12/19/20 1:13 PM, Carlos E. R. wrote:
On 19/12/2020 19.39, Jim Flanagan wrote:
On 12/18/20 9:17 PM, Felix Miata wrote:
Jim Flanagan composed on 2020-12-18 20:11 (UTC-0600): ...
This system was first installed with Leap 15.0, upgraded to 15.1, now to a partially broken 15.2.
Any suggestions most welcome.
If you login to an IceWM session instead of Plasma, does everything there work?
To confirm the upgrade went as it should have, from any of the vttys, try:
sudo zypper ref sudo zypper dup
OK did the ref and it updated the repos. Running zypper dup returned:
You should not have done that till completed my instructions.
The following NEW package is going to be installed: openSUSE-release-ftp
The following 7 packages are going to be REMOVED: aaa_base aaa_base-extras kpartx kpartx libefivar1
I would be very worried at seeing that message.
After installing the remaining updates it finished with this message. Problem occurred during or after installation or removal of packages: Failed to cache rpm database (1). History: - 'rpmdb2solv' '-r' '/' '-X' '-o' '/etc/products.d' '/var/cache/zypp/solv/@System/solv' 'o' '/var/cache/zypp/solv/@System/solvc1qmx9' rpmdb2solv: inconsistent rpm database, key 6548 not found. run 'rpm --rebuilddb' to fix.
Oh shit.
Again, i'm rusty on command line. What now? Keep working on that long string to get the output, or is it too late? Or run zypper up? Jim Jim
On 19/12/2020 20.23, Jim Flanagan wrote:
On 12/19/20 1:13 PM, Carlos E. R. wrote:
On 19/12/2020 19.39, Jim Flanagan wrote:
On 12/18/20 9:17 PM, Felix Miata wrote:
Jim Flanagan composed on 2020-12-18 20:11 (UTC-0600):
...
Again, i'm rusty on command line. What now?
Keep working on that long string to get the output, or is it too late? Or run zypper up?
I need to see what is the result of those two commands I told you in order to decide what to do next. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 12/19/20 1:59 PM, Carlos E. R. wrote:
On 19/12/2020 20.23, Jim Flanagan wrote:
On 12/19/20 1:13 PM, Carlos E. R. wrote:
On 19/12/2020 19.39, Jim Flanagan wrote:
On 12/18/20 9:17 PM, Felix Miata wrote:
Jim Flanagan composed on 2020-12-18 20:11 (UTC-0600):
...
Again, i'm rusty on command line. What now?
Keep working on that long string to get the output, or is it too late? Or run zypper up?
I need to see what is the result of those two commands I told you in order to decide what to do next.
Ok I found a way to open a txt file in KDE without the start menu. From another computer I pasted the long rpm string into a txt file to edit it. With thumb drive then pasting into konsole, but I keep getting invalid field width. Jim
On 20/12/2020 00.14, Jim Flanagan wrote:
On 12/19/20 1:59 PM, Carlos E. R. wrote:
On 19/12/2020 20.23, Jim Flanagan wrote:
On 12/19/20 1:13 PM, Carlos E. R. wrote:
On 19/12/2020 19.39, Jim Flanagan wrote:
On 12/18/20 9:17 PM, Felix Miata wrote:
Jim Flanagan composed on 2020-12-18 20:11 (UTC-0600):
...
Again, i'm rusty on command line. What now?
Keep working on that long string to get the output, or is it too late? Or run zypper up?
I need to see what is the result of those two commands I told you in order to decide what to do next.
Ok I found a way to open a txt file in KDE without the start menu. From another computer I pasted the long rpm string into a txt file to edit it. With thumb drive then pasting into konsole, but I keep getting invalid field width.
If you have another computer, then just open konsole in that good computer, and run: ssh yourusername@IP_ADDRESS_of_bad_computer and then paste the command line in there. Or, create this script in the thumb drive: +++····················· #/bin/bash rpm -q -a --queryformat "%{INSTALLTIME}\t%{INSTALLTIME:day} \ %{BUILDTIME:day} %-30{NAME}\t%15{VERSION}-%-7{RELEASE}\t%{arch} \ %25{VENDOR}%25{PACKAGER} == %{DISTRIBUTION} %{DISTTAG}\n" \ | sort | cut --fields="2-" | tee rpmlist.txt \ | egrep -v "openSUSE Leap 15\.2|openSUSE_Leap_15.2|-lp152" \
rpmlist_hits.txt
zypper lr --details > repolist.txt ·····················++- And run it in the bad computer. The script will create files "rpmlist_hits.txt" and "repolist.txt" inside that thumb drive. If there is an error, you did not paste the script correctly. Then back in the good computer, upload those two files: susepaste -n "Jim F" -t "possible wrong rpms" -e 151200 rpmlist_hits.txt susepaste -n "Jim F" -t "possible wrong rpms" -e 151200 repolist.txt There are many ways to skin a cat. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 12/19/20 6:17 PM, Carlos E. R. wrote:
On 20/12/2020 00.14, Jim Flanagan wrote:
On 12/19/20 1:59 PM, Carlos E. R. wrote:
On 19/12/2020 20.23, Jim Flanagan wrote:
On 12/19/20 1:13 PM, Carlos E. R. wrote:
On 19/12/2020 19.39, Jim Flanagan wrote:
On 12/18/20 9:17 PM, Felix Miata wrote: > Jim Flanagan composed on 2020-12-18 20:11 (UTC-0600):
...
Again, i'm rusty on command line. What now?
Keep working on that long string to get the output, or is it too late? Or run zypper up?
I need to see what is the result of those two commands I told you in order to decide what to do next.
Ok I found a way to open a txt file in KDE without the start menu. From another computer I pasted the long rpm string into a txt file to edit it. With thumb drive then pasting into konsole, but I keep getting invalid field width.
If you have another computer, then just open konsole in that good computer, and run:
ssh yourusername@IP_ADDRESS_of_bad_computer
and then paste the command line in there.
Or, create this script in the thumb drive:
+++····················· #/bin/bash rpm -q -a --queryformat "%{INSTALLTIME}\t%{INSTALLTIME:day} \ %{BUILDTIME:day} %-30{NAME}\t%15{VERSION}-%-7{RELEASE}\t%{arch} \ %25{VENDOR}%25{PACKAGER} == %{DISTRIBUTION} %{DISTTAG}\n" \ | sort | cut --fields="2-" | tee rpmlist.txt \ | egrep -v "openSUSE Leap 15\.2|openSUSE_Leap_15.2|-lp152" \
rpmlist_hits.txt
zypper lr --details > repolist.txt ·····················++-
And run it in the bad computer. The script will create files "rpmlist_hits.txt" and "repolist.txt" inside that thumb drive.
If there is an error, you did not paste the script correctly.
Then back in the good computer, upload those two files:
susepaste -n "Jim F" -t "possible wrong rpms" -e 151200 rpmlist_hits.txt susepaste -n "Jim F" -t "possible wrong rpms" -e 151200 repolist.txt
There are many ways to skin a cat.
OK I got the rpm command to run via remote terminal in my macbook. Susepaste failed even tho zypper says its installed. Here's the contents of rpmlist_hits.txt Jim F Sat Feb 23 2019 Mon May 05 2014 gpg-pubkey 3dbdc284-53674dd4 (none) (none)openSUSE Project Signing Key <opensuse@opensuse.org> == (none) (none) Sat Feb 23 2019 Thu Mar 15 2018 gpg-pubkey 307e3d54-5aaa90a5 (none) (none)SuSE Package Signing Key <build@suse.de> == (none) (none) Sat Feb 23 2019 Wed Dec 07 2016 gpg-pubkey 39db7c82-5847eb1f (none) (none)SuSE Package Signing Key <build@suse.de> == (none) (none) Sun Feb 24 2019 Tue Feb 19 2019 logitechmediaserver 7.9.2-0.1.1550612824 noarch LogitechLogitech - please visit www.mysqueezebox.com/support == (none) (none) Mon Mar 04 2019 Mon Sep 15 2014 gpg-pubkey 1abd1afb-54176598 (none) (none)PackMan Project (signing key) <packman@links2linux.de> == (none) (none) Wed May 29 2019 Mon May 20 2019 libx265-169 3.0-lp150.1.7 x86_64 http://packman.links2linux.de packman@links2linux.de == Essentials / openSUSE_Leap_15.0 (none) Thu Aug 15 2019 Sun Aug 11 2019 libx265-176 3.1.2-lp150.1.1 x86_64 http://packman.links2linux.de packman@links2linux.de == Essentials / openSUSE_Leap_15.0 (none) Sun Nov 03 2019 Wed Oct 30 2019 libmac2 3.99_u4_b5_s7-lp150.5.3 x86_64 http://packman.links2linux.de packman@links2linux.de == Multimedia / openSUSE_Leap_15.0 (none) Sun Nov 03 2019 Tue Oct 22 2019 libfdk-aac1 0.1.6-lp150.2.6 x86_64 http://packman.links2linux.de packman@links2linux.de == Essentials / openSUSE_Leap_15.0 (none) Sun Nov 03 2019 Wed Oct 30 2019 libx264-155 0.155svn20190201-lp150.2.3 x86_64 http://packman.links2linux.de packman@links2linux.de == Essentials / openSUSE_Leap_15.0 (none) Sun Nov 03 2019 Wed Oct 30 2019 libx265-179 3.2-lp150.1.3 x86_64 http://packman.links2linux.de packman@links2linux.de == Essentials / openSUSE_Leap_15.0 (none) Sun Nov 03 2019 Wed Oct 30 2019 libxvidcore4 1.3.5-lp150.2.9 x86_64 http://packman.links2linux.de packman@links2linux.de == Essentials / openSUSE_Leap_15.0 (none) Sun Nov 03 2019 Wed Oct 30 2019 mac 3.99_u4_b5_s7-lp150.5.3 x86_64 http://packman.links2linux.de packman@links2linux.de == Multimedia / openSUSE_Leap_15.0 (none) Sun Nov 03 2019 Wed Oct 30 2019 asunder 2.9.3-lp150.1.10 x86_64 http://packman.links2linux.de packman@links2linux.de == Multimedia / openSUSE_Leap_15.0 (none) Fri Dec 11 2020 Thu Dec 03 2020 kernel-default 4.12.14-lp151.28.87.2 x86_64 openSUSE http://bugs.opensuse.org == openSUSE Leap 15.1 (none)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 El 2020-12-20 a las 16:16 -0600, Jim Flanagan escribió:
On 12/19/20 6:17 PM, Carlos E. R. wrote:
On 20/12/2020 00.14, Jim Flanagan wrote:
On 12/19/20 1:59 PM, Carlos E. R. wrote:
On 19/12/2020 20.23, Jim Flanagan wrote:
On 12/19/20 1:13 PM, Carlos E. R. wrote:
...
OK I got the rpm command to run via remote terminal in my macbook. Susepaste failed even tho zypper says its installed.
It is there. You are probably hit by a bug that should have been corrected, but I don't know because you did not paste the error here. This is your file: <https://susepaste.org/6481544> This is the filtered result: Sat Feb 23 2019 Mon May 05 2014 gpg-pubkey 3dbdc284-53674dd4 (none) (none)openSUSE Project Signing Key <opensuse@opensuse.org> == (none) (none) Sat Feb 23 2019 Thu Mar 15 2018 gpg-pubkey 307e3d54-5aaa90a5 (none) (none)SuSE Package Signing Key <build@suse.de> == (none) (none) Sat Feb 23 2019 Wed Dec 07 2016 gpg-pubkey 39db7c82-5847eb1f (none) (none)SuSE Package Signing Key <build@suse.de> == (none) (none) Sun Feb 24 2019 Tue Feb 19 2019 logitechmediaserver 7.9.2-0.1.1550612824 noarch LogitechLogitech - please visit www.mysqueezebox.com/support == (none) (none) Mon Mar 04 2019 Mon Sep 15 2014 gpg-pubkey 1abd1afb-54176598 (none) (none)PackMan Project (signing key) <packman@links2linux.de> == (none) (none) Wed May 29 2019 Mon May 20 2019 libx265-169 3.0-lp150.1.7 x86_64 http://packman.links2linux.de packman@links2linux.de == Essentials / openSUSE_Leap_15.0 (none) Thu Aug 15 2019 Sun Aug 11 2019 libx265-176 3.1.2-lp150.1.1 x86_64 http://packman.links2linux.de packman@links2linux.de == Essentials / openSUSE_Leap_15.0 (none) Sun Nov 03 2019 Wed Oct 30 2019 libmac2 3.99_u4_b5_s7-lp150.5.3 x86_64 http://packman.links2linux.de packman@links2linux.de == Multimedia / openSUSE_Leap_15.0 (none) Sun Nov 03 2019 Tue Oct 22 2019 libfdk-aac1 0.1.6-lp150.2.6 x86_64 http://packman.links2linux.de packman@links2linux.de == Essentials / openSUSE_Leap_15.0 (none) Sun Nov 03 2019 Wed Oct 30 2019 libx264-155 0.155svn20190201-lp150.2.3 x86_64 http://packman.links2linux.de packman@links2linux.de == Essentials / openSUSE_Leap_15.0 (none) Sun Nov 03 2019 Wed Oct 30 2019 libx265-179 3.2-lp150.1.3 x86_64 http://packman.links2linux.de packman@links2linux.de == Essentials / openSUSE_Leap_15.0 (none) Sun Nov 03 2019 Wed Oct 30 2019 libxvidcore4 1.3.5-lp150.2.9 x86_64 http://packman.links2linux.de packman@links2linux.de == Essentials / openSUSE_Leap_15.0 (none) Sun Nov 03 2019 Wed Oct 30 2019 mac 3.99_u4_b5_s7-lp150.5.3 x86_64 http://packman.links2linux.de packman@links2linux.de == Multimedia / openSUSE_Leap_15.0 (none) Sun Nov 03 2019 Wed Oct 30 2019 asunder 2.9.3-lp150.1.10 x86_64 http://packman.links2linux.de packman@links2linux.de == Multimedia / openSUSE_Leap_15.0 (none) Fri Dec 11 2020 Thu Dec 03 2020 kernel-default 4.12.14-lp151.28.87.2 x86_64 openSUSE http://bugs.opensuse.org == openSUSE Leap 15.1 (none) Ok there is nothing crucial in there. There is the kernel from Leap 15.1, which is not purged as the previous kernel is kept by default, and you also have kernel-default version 5.3.18-lp152.57.1 installed. So, no issue there - as long as you are really booting that second kernel. Then you have a bunch of packman files that you need to update. I'll tell you how, but first I must see your list of repos: zypper lr --details > repolist.txt susepaste -n "Jim F" -t "repository list" -e 151200 repolist.txt and paste here the link or at least the number. You also have "logitechmediaserver" which seems to be a proprietary package? About the old "gpg-pubkey", ignore them. - -- Cheers, Carlos E. R. (from openSUSE 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHkEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCX9/S0xwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVZaAAmMlahzMASexsmJOo01PS 5dZJHGIAn0MMzPvGRQnIzxETTygLSLEQeTnd =Hw0U -----END PGP SIGNATURE-----
On 20/12/2020 23.40, Carlos E. R. wrote:
Then you have a bunch of packman files that you need to update. I'll tell you how, but first I must see your list of repos:
zypper lr --details > repolist.txt susepaste -n "Jim F" -t "repository list" -e 151200 repolist.txt
and paste here the link or at least the number.
Now that you know how to ssh from your macbook, you can easily do it all :-) I will be checking the mail for some two or three hours, then I have to go to sleep. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 20/12/2020 23.53, Carlos E.R. wrote:
On 20/12/2020 23.40, Carlos E. R. wrote:
Then you have a bunch of packman files that you need to update. I'll tell you how, but first I must see your list of repos:
zypper lr --details > repolist.txt susepaste -n "Jim F" -t "repository list" -e 151200 repolist.txt
and paste here the link or at least the number.
Now that you know how to ssh from your macbook, you can easily do it all :-)
I will be checking the mail for some two or three hours, then I have to go to sleep.
Please paste also the result of "rpmconfigcheck" and I'll tell you which are the important ones to do. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 12/20/20 4:56 PM, Carlos E.R. wrote:
On 20/12/2020 23.53, Carlos E.R. wrote:
On 20/12/2020 23.40, Carlos E. R. wrote:
Then you have a bunch of packman files that you need to update. I'll tell you how, but first I must see your list of repos:
zypper lr --details > repolist.txt susepaste -n "Jim F" -t "repository list" -e 151200 repolist.txt
and paste here the link or at least the number.
Now that you know how to ssh from your macbook, you can easily do it all :-)
I will be checking the mail for some two or three hours, then I have to go to sleep.
Please paste also the result of "rpmconfigcheck" and I'll tell you which are the important ones to do.
https://paste.opensuse.org/65673093 I'm posting these thru the web interface. For some reason susepaste script fails. Many thanks, Jim F
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2020-12-20 at 17:00 -0600, Jim Flanagan wrote:
On 12/20/20 4:56 PM, Carlos E.R. wrote:
On 20/12/2020 23.53, Carlos E.R. wrote:
On 20/12/2020 23.40, Carlos E. R. wrote:
zypper lr --details > repolist.txt susepaste -n "Jim F" -t "repository list" -e 151200 repolist.txt
and paste here the link or at least the number.
Now that you know how to ssh from your macbook, you can easily do it all :-)
I will be checking the mail for some two or three hours, then I have to go to sleep.
Please paste also the result of "rpmconfigcheck" and I'll tell you which are the important ones to do.
https://paste.opensuse.org/65673093
I'm posting these thru the web interface. For some reason susepaste script fails.
Ok, let's see. I will leave the most important ones. /etc/bash.bashrc.rpmorig /etc/csh.login.rpmorig /etc/dbus-1/system.d/org.freedesktop.NetworkManager.conf.rpmorig /etc/default/grub.rpmnew /etc/grub.d/00_header.rpmnew /etc/grub.d/10_linux.rpmnew /etc/grub.d/20_linux_xen.rpmnew /etc/grub.d/95_textmode.rpmnew /etc/modprobe.d/10-unsupported-modules.conf.rpmnew /etc/my.cnf.rpmnew /etc/plymouth/plymouthd.conf.rpmnew /etc/profile.rpmorig /etc/pulse/client.conf.d/50-system.conf.rpmsave /etc/ssh/moduli.rpmnew /etc/ssh/ssh_config.rpmnew /etc/ssl/openssl.cnf.rpmnew /etc/sysconfig/SuSEfirewall2.d/services/mysql.rpmorig /etc/systemd/logind.conf.rpmnew /etc/xdg/kickoffrc.rpmsave /etc/xdg/servicemenu.knsrc.rpmorig /etc/zypp/zypp.conf.rpmnew Now, how to do them? It is easier if you can get the desktop running (notice that if plasma fails, you can use other desktops that are les finicky), or using another computer running Linux. Even a windows one if you install "MobaXterm". So, either locally in a graphic terminal, or remotely in an "ssh -X ..." session, you would do, for each line above (you may have to install meld first): meld /etc/bash.bashrc.rpmorig /etc/bash.bashrc or meld /etc/pulse/client.conf.d/50-system.conf.rpmsave /etc/pulse/client.conf.d/50-system.conf or meld /etc/plymouth/plymouthd.conf.rpmnew /etc/plymouth/plymouthd.conf Now, "meld" is an special editor that opens two files at the same time marking the differences between each file. An "*rpmsave" file is the old configuration file, while the file on the right hand above is the current active configuration file. You have to decide what things on the left hand file you want to copy to the right hand file (and do it), or not to copy. "meld" has visual guides to do that. Most often the differences are cosmetic. When done, save, and then delete the "*rpmsave" file or move to a backup directory. An "*rpmnew" file instead is a new configuration file, while the file in the right hand will this time be the old configuration file which is still active. Again, you have to decide what new things you want to copy over. When done, save, and then delete the "*rpmnew" file or move to a backup directory. The ".rpmorig" file I don't remember what it was. Long time no see. When done, reboot or restart each affected service, one by one. If you don't know what to do with some of the above entries, just mail me or the list both files and I'll edit them for you. It is really easy to do, just a chore, and complicated to explain. Must of the differences in the files are cosmetics, but some are important, and you never know when and where an important change is lurking. - -- Cheers, Carlos E. R. (from openSUSE 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCX9/zphwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVyIgAni9B4Fw+DtP9pjvQQRSJ 8OEEoF1bAJ4hxWJc1QGbuorVwLY7xetHoeRugQ== =8bBU -----END PGP SIGNATURE-----
On 12/20/20 4:40 PM, Carlos E. R. wrote:
El 2020-12-20 a las 16:16 -0600, Jim Flanagan escribió:
On 12/19/20 6:17 PM, Carlos E. R. wrote:
On 20/12/2020 00.14, Jim Flanagan wrote:
On 12/19/20 1:59 PM, Carlos E. R. wrote:
On 19/12/2020 20.23, Jim Flanagan wrote:
On 12/19/20 1:13 PM, Carlos E. R. wrote:
...
OK I got the rpm command to run via remote terminal in my macbook. Susepaste failed even tho zypper says its installed.
It is there. You are probably hit by a bug that should have been corrected, but I don't know because you did not paste the error here.
This is your file:
<https://susepaste.org/6481544>
This is the filtered result:
Sat Feb 23 2019 Mon May 05 2014 gpg-pubkey 3dbdc284-53674dd4 (none) (none)openSUSE Project Signing Key <opensuse@opensuse.org> == (none) (none) Sat Feb 23 2019 Thu Mar 15 2018 gpg-pubkey 307e3d54-5aaa90a5 (none) (none)SuSE Package Signing Key <build@suse.de> == (none) (none) Sat Feb 23 2019 Wed Dec 07 2016 gpg-pubkey 39db7c82-5847eb1f (none) (none)SuSE Package Signing Key <build@suse.de> == (none) (none) Sun Feb 24 2019 Tue Feb 19 2019 logitechmediaserver 7.9.2-0.1.1550612824 noarch LogitechLogitech - please visit www.mysqueezebox.com/support == (none) (none) Mon Mar 04 2019 Mon Sep 15 2014 gpg-pubkey 1abd1afb-54176598 (none) (none)PackMan Project (signing key) <packman@links2linux.de> == (none) (none) Wed May 29 2019 Mon May 20 2019 libx265-169 3.0-lp150.1.7 x86_64 http://packman.links2linux.de packman@links2linux.de == Essentials / openSUSE_Leap_15.0 (none) Thu Aug 15 2019 Sun Aug 11 2019 libx265-176 3.1.2-lp150.1.1 x86_64 http://packman.links2linux.de packman@links2linux.de == Essentials / openSUSE_Leap_15.0 (none) Sun Nov 03 2019 Wed Oct 30 2019 libmac2 3.99_u4_b5_s7-lp150.5.3 x86_64 http://packman.links2linux.de packman@links2linux.de == Multimedia / openSUSE_Leap_15.0 (none) Sun Nov 03 2019 Tue Oct 22 2019 libfdk-aac1 0.1.6-lp150.2.6 x86_64 http://packman.links2linux.de packman@links2linux.de == Essentials / openSUSE_Leap_15.0 (none) Sun Nov 03 2019 Wed Oct 30 2019 libx264-155 0.155svn20190201-lp150.2.3 x86_64 http://packman.links2linux.de packman@links2linux.de == Essentials / openSUSE_Leap_15.0 (none) Sun Nov 03 2019 Wed Oct 30 2019 libx265-179 3.2-lp150.1.3 x86_64 http://packman.links2linux.de packman@links2linux.de == Essentials / openSUSE_Leap_15.0 (none) Sun Nov 03 2019 Wed Oct 30 2019 libxvidcore4 1.3.5-lp150.2.9 x86_64 http://packman.links2linux.de packman@links2linux.de == Essentials / openSUSE_Leap_15.0 (none) Sun Nov 03 2019 Wed Oct 30 2019 mac 3.99_u4_b5_s7-lp150.5.3 x86_64 http://packman.links2linux.de packman@links2linux.de == Multimedia / openSUSE_Leap_15.0 (none) Sun Nov 03 2019 Wed Oct 30 2019 asunder 2.9.3-lp150.1.10 x86_64 http://packman.links2linux.de packman@links2linux.de == Multimedia / openSUSE_Leap_15.0 (none) Fri Dec 11 2020 Thu Dec 03 2020 kernel-default 4.12.14-lp151.28.87.2 x86_64 openSUSE http://bugs.opensuse.org == openSUSE Leap 15.1 (none)
Ok there is nothing crucial in there. There is the kernel from Leap 15.1, which is not purged as the previous kernel is kept by default, and you also have kernel-default version 5.3.18-lp152.57.1 installed. So, no issue there - as long as you are really booting that second kernel.
Then you have a bunch of packman files that you need to update. I'll tell you how, but first I must see your list of repos:
zypper lr --details > repolist.txt susepaste -n "Jim F" -t "repository list" -e 151200 repolist.txt
and paste here the link or at least the number.
You also have "logitechmediaserver" which seems to be a proprietary package?
This is the main use i have for this machine, its my music server. I love it. This is why I chose to do a 'upgrade' instead of an clean 'install'. I recall have a few problems getting it to run on Leap 15.0 and earlier openSUSE releases. Oddly it is working well, so I'm happy wiht that, especially during the Christmas season. I just can't do anyting on the computer desktop LOL.
About the old "gpg-pubkey", ignore them.
repolist.txt posted here https://paste.opensuse.org/73544223 If worse comes to worse, I could do a new clean install. That should get me a good clean working system, but I'm not sure how difficult it will be at that point to re-install 'logitechmediaserver". Thanks for the great help. Jim F
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2020-12-20 at 16:55 -0600, Jim Flanagan wrote:
On 12/20/20 4:40 PM, Carlos E. R. wrote:
...
You also have "logitechmediaserver" which seems to be a proprietary package?
This is the main use i have for this machine, its my music server. I love it. This is why I chose to do a 'upgrade' instead of an clean 'install'. I recall have a few problems getting it to run on Leap 15.0 and earlier openSUSE releases. Oddly it is working well, so I'm happy wiht that, especially during the Christmas season. I just can't do anyting on the computer desktop LOL. Ah, I see.
About the old "gpg-pubkey", ignore them.
repolist.txt posted here https://paste.opensuse.org/73544223 Ok, the repository list is "almost" perfect, only packman is missing.
You have to do: zypper ar -f -n "Packman Repository" "http://packman.inode.at/suse/openSUSE_Leap_15.2/" "Packman" then you should do: zypper up and tell here what is the result.
If worse comes to worse, I could do a new clean install. That should get me a good clean working system, but I'm not sure how difficult it will be at that point to re-install 'logitechmediaserver".
Thanks for the great help.
Welcome. Let's go step by step. - -- Cheers, Carlos E. R. (from openSUSE 15.1 x86_64 at Telcontar) El 2020-12-20 a las 16:55 -0600, Jim Flanagan escribió: -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCX9/uthwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVTQAAn1M2fT+tGh5P/ixWl1JY yNAyPRp0AJ9WcMGBbOGzavfcYd6xLxy2RwGLBQ== =MpJn -----END PGP SIGNATURE-----
On 12/20/20 6:39 PM, Carlos E. R. wrote:
On Sunday, 2020-12-20 at 16:55 -0600, Jim Flanagan wrote:
On 12/20/20 4:40 PM, Carlos E. R. wrote:
About the old "gpg-pubkey", ignore them.
repolist.txt posted here https://paste.opensuse.org/73544223 Ok, the repository list is "almost" perfect, only packman is missing.
You have to do:
zypper ar -f -n "Packman Repository" "http://packman.inode.at/suse/openSUSE_Leap_15.2/" "Packman"
then you should do:
zypper up
and tell here what is the result.
If worse comes to worse, I could do a new clean install. That should get me a good clean working system, but I'm not sure how difficult it will be at that point to re-install 'logitechmediaserver".
Thanks for the great help.
Welcome. Let's go step by step.
Here's what I get on zypper up. Should I proceed? jim@linux-j34m:~> sudo zypper ar -f -n "Packman Repository" "http://packman.inode.at/suse/openSUSE_Leap_15.2/" "Packman" [sudo] password for root: Adding repository 'Packman Repository' ...................................[done] Repository 'Packman Repository' successfully added URI : http://packman.inode.at/suse/openSUSE_Leap_15.2/ Enabled : Yes GPG Check : Yes Autorefresh : Yes Priority : 99 (default priority) Repository priorities are without effect. All enabled repositories share the same priority. jim@linux-j34m:~> sudo zypper up Retrieving repository 'Packman Repository' metadata ......................[done] Building repository 'Packman Repository' cache ...........................[done] Loading repository data... Reading installed packages... The following 21 package updates will NOT be installed: libavcodec57 libavcodec58 libavdevice57 libavfilter6 libavformat57 libavresample3 libavutil55 libavutil56 libgstphotography-1_0-0 libpostproc54 libswresample2 libswresample3 libswscale4 libvlc5 libvlccore9 vlc vlc-codec-gstreamer vlc-lang vlc-noX vlc-qt vlc-vdpau The following 33 packages are going to be upgraded: asunder cpp7 libblkid1 libfdisk1 libgfortran4 libjavascriptcoregtk-4_0-18 libmac2 libmount1 libQt5Concurrent5 libQt5Core5 libQt5DBus5 libQt5Gui5 libQt5Network5 libQt5OpenGL5 libQt5PrintSupport5 libqt5-qtbase-platformtheme-gtk3 libQt5Sql5 libQt5Sql5-mysql libQt5Sql5-sqlite libQt5Test5 libQt5Widgets5 libQt5Xml5 libsmartcols1 libuuid1 libwebkit2gtk3-lang libwebkit2gtk-4_0-37 libxvidcore4 mac tcl util-linux util-linux-lang util-linux-systemd webkit2gtk-4_0-injected-bundles 33 packages to upgrade. Overall download size: 43.5 MiB. Already cached: 0 B. After the operation, additional 4.5 MiB will be used. Continue? [y/n/v/...? shows all options] (y):
On 21/12/2020 19.07, Jim Flanagan wrote:
On 12/20/20 6:39 PM, Carlos E. R. wrote:
Welcome. Let's go step by step.
Here's what I get on zypper up. Should I proceed?
...
Overall download size: 43.5 MiB. Already cached: 0 B. After the operation, additional 4.5 MiB will be used. Continue? [y/n/v/...? shows all options] (y):
I would proceed, yes. I have the suspicion that you will need to do the "packman swith" too. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 12/21/20 2:09 PM, Carlos E. R. wrote:
On 21/12/2020 19.07, Jim Flanagan wrote:
On 12/20/20 6:39 PM, Carlos E. R. wrote:
Welcome. Let's go step by step.
Here's what I get on zypper up. Should I proceed?
...
Overall download size: 43.5 MiB. Already cached: 0 B. After the operation, additional 4.5 MiB will be used. Continue? [y/n/v/...? shows all options] (y):
I would proceed, yes.
I have the suspicion that you will need to do the "packman swith" too.
Hi Carlos, I did the "packman swith" already. Was at the top of the paste in my last posting. I installed meld, there is an error running it. Here's the melds install link:https://paste.opensuse.org/79740502 I did "zypper up", and ran the list of running packages at the end. Here's the output:https://paste.opensuse.org/96631676 Thanks, Jim F
On 21/12/2020 21.25, Jim Flanagan wrote:
On 12/21/20 2:09 PM, Carlos E. R. wrote:
On 21/12/2020 19.07, Jim Flanagan wrote:
On 12/20/20 6:39 PM, Carlos E. R. wrote:
Welcome. Let's go step by step.
Here's what I get on zypper up. Should I proceed?
...
Overall download size: 43.5 MiB. Already cached: 0 B. After the operation, additional 4.5 MiB will be used. Continue? [y/n/v/...? shows all options] (y):
I would proceed, yes.
I have the suspicion that you will need to do the "packman swith" too.
Hi Carlos,
I did the "packman swith" already. Was at the top of the paste in my last posting.
I installed meld, there is an error running it. Here's the melds install link:https://paste.opensuse.org/79740502
I don't see any error there, it worked.
I did "zypper up", and ran the list of running packages at the end. Here's the output:https://paste.opensuse.org/96631676
Yes, all normal, no problems. But you have to either restart those processes, or reboot. I would simply reboot. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 12/21/20 2:38 PM, Carlos E. R. wrote:
On 21/12/2020 21.25, Jim Flanagan wrote:
On 12/21/20 2:09 PM, Carlos E. R. wrote:
On 21/12/2020 19.07, Jim Flanagan wrote:
On 12/20/20 6:39 PM, Carlos E. R. wrote:
Welcome. Let's go step by step.
Here's what I get on zypper up. Should I proceed?
...
Overall download size: 43.5 MiB. Already cached: 0 B. After the operation, additional 4.5 MiB will be used. Continue? [y/n/v/...? shows all options] (y):
I would proceed, yes.
I have the suspicion that you will need to do the "packman swith" too.
Hi Carlos,
I did the "packman swith" already. Was at the top of the paste in my last posting.
I installed meld, there is an error running it. Here's the melds install link:https://paste.opensuse.org/79740502
I don't see any error there, it worked.
Here's what happens when I try the first package with meld. jim@linux-j34m:~> meld /etc/bash.bashrc.rpmorig /etc/bash.bashrc Unable to init server: Could not connect: Connection refused Unable to init server: Could not connect: Connection refused 2020-12-21 14:55:41,110 CRITICAL Gtk: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed Traceback (most recent call last): File "/usr/bin/meld", line 341, in <module> setup_resources() File "/usr/bin/meld", line 220, in setup_resources Gtk.IconTheme.get_default().append_search_path(icon_dir) AttributeError: 'NoneType' object has no attribute 'append_search_path' jim@linux-j34m:~>
I did "zypper up", and ran the list of running packages at the end. Here's the output:https://paste.opensuse.org/96631676
Yes, all normal, no problems. But you have to either restart those processes, or reboot. I would simply reboot.
I did reboot, no change. I get the kicker error in my desktop, a new user I set up yesterday and as root, all the same issue. But again, the desktop is up, just the start menu won't open. Jim F
On 21/12/2020 21.57, Jim Flanagan wrote:
On 12/21/20 2:38 PM, Carlos E. R. wrote:
On 21/12/2020 21.25, Jim Flanagan wrote:
...
I installed meld, there is an error running it. Here's the melds install link:https://paste.opensuse.org/79740502
I don't see any error there, it worked.
Here's what happens when I try the first package with meld.
jim@linux-j34m:~> meld /etc/bash.bashrc.rpmorig /etc/bash.bashrc Unable to init server: Could not connect: Connection refused Unable to init server: Could not connect: Connection refused
Is graphical mode running? Or are you doing it remotely, using either "ssh -X ..." or "ssh -Y ..."? Otherwise, it will not work.
I did "zypper up", and ran the list of running packages at the end. Here's the output:https://paste.opensuse.org/96631676
Yes, all normal, no problems. But you have to either restart those processes, or reboot. I would simply reboot.
I did reboot, no change. I get the kicker error in my desktop, a new user I set up yesterday and as root, all the same issue. But again, the desktop is up, just the start menu won't open.
AH! Well, that's a different thing altogether. Switch to another desktop, ditch plasma for the moment. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 12/20/20 6:39 PM, Carlos E. R. wrote:
On Sunday, 2020-12-20 at 16:55 -0600, Jim Flanagan wrote:
On 12/20/20 4:40 PM, Carlos E. R. wrote:
...
You also have "logitechmediaserver" which seems to be a proprietary package?
This is the main use i have for this machine, its my music server. I love it. This is why I chose to do a 'upgrade' instead of an clean 'install'. I recall have a few problems getting it to run on Leap 15.0 and earlier openSUSE releases. Oddly it is working well, so I'm happy wiht that, especially during the Christmas season. I just can't do anyting on the computer desktop LOL. Ah, I see.
About the old "gpg-pubkey", ignore them.
repolist.txt posted here https://paste.opensuse.org/73544223 Ok, the repository list is "almost" perfect, only packman is missing.
You have to do:
zypper ar -f -n "Packman Repository" "http://packman.inode.at/suse/openSUSE_Leap_15.2/" "Packman"
then you should do:
zypper up
and tell here what is the result.
If worse comes to worse, I could do a new clean install. That should get me a good clean working system, but I'm not sure how difficult it will be at that point to re-install 'logitechmediaserver".
Thanks for the great help.
Welcome. Let's go step by step.
I also found this searching the web. What about re-installing plasma.desktop or updating it? https://forums.opensuse.org/showthread.php/541072-no-menu-available-after-up... Jim F
On 21/12/2020 19.25, Jim Flanagan wrote:
On 12/20/20 6:39 PM, Carlos E. R. wrote:
On Sunday, 2020-12-20 at 16:55 -0600, Jim Flanagan wrote:
...
Welcome. Let's go step by step.
I also found this searching the web. What about re-installing plasma.desktop or updating it?
https://forums.opensuse.org/showthread.php/541072-no-menu-available-after-up...
I don't think it applies to your problem. He said he did a fresh install without formatting, and that's a recipe for problems. If you can not format, the correct procedure is "upgrade", as you did. But you got some advice from Patrick that might work [...] Ok, I see it didn't. Ok, what happens if, on the text console, you do: init 3 init 5 Tell the exact errors you get. Take a photo perhaps. *if it fails*, please run: update-alternatives --display default-displaymanager and tell the results. Mine: Telcontar:~ # update-alternatives --display default-displaymanager default-displaymanager - auto mode link best version is /usr/lib/X11/displaymanagers/sddm link currently points to /usr/lib/X11/displaymanagers/sddm link default-displaymanager is /usr/lib/X11/displaymanagers/default-displaymanager /usr/lib/X11/displaymanagers/console - priority 5 /usr/lib/X11/displaymanagers/gdm - priority 25 /usr/lib/X11/displaymanagers/kdm - priority 15 /usr/lib/X11/displaymanagers/lightdm - priority 15 /usr/lib/X11/displaymanagers/sddm - priority 25 /usr/lib/X11/displaymanagers/xdm - priority 10 Telcontar:~ # I don't remember if the default for a plasma systemd is "kdm"; you could try switching to "sddm" instead, but you might have to install it: zypper install sddm Once installed, to do the switch you would do: init 3 update-alternatives --set default-displaymanager \ /usr/lib/X11/displaymanagers/sddm init 5 And maybe with that you get a graphical login. Then, try to login to plasma, and if that fails, try other desktops till one works. You might have to install some extra pattern to get more desktops. Note: doc for update-alternatives: https://doc.opensuse.org/release-notes/x86_64/openSUSE/Leap/15.0/#general Section 5.2 -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 12/21/20 2:34 PM, Carlos E. R. wrote:
On 21/12/2020 19.25, Jim Flanagan wrote:
On 12/20/20 6:39 PM, Carlos E. R. wrote:
On Sunday, 2020-12-20 at 16:55 -0600, Jim Flanagan wrote:
...
Welcome. Let's go step by step.
I also found this searching the web. What about re-installing plasma.desktop or updating it?
https://forums.opensuse.org/showthread.php/541072-no-menu-available-after-up...
I don't think it applies to your problem. He said he did a fresh install without formatting, and that's a recipe for problems. If you can not format, the correct procedure is "upgrade", as you did.
But you got some advice from Patrick that might work [...] Ok, I see it didn't.
Ok, what happens if, on the text console, you do:
init 3 init 5
Tell the exact errors you get. Take a photo perhaps.
I can and have been going to tty (F1) and can log in as jim and root. I have run init 3 just ot shut down the desktop before i make changes. Then running init 5 takes me back to desktop login (KDE). I can do this in tty on that machine or thru temrinal on my macbook. I've even run init 6 via remote terminal to restart the machine, works fine. The system is up and running, and has been. That "logitechmediaserver" rpm is managed thru http://localhost:9000, that's the only display built in, so I don't see that that would be a problem. And it is working fine. I haven't done the rest of your suggestions below yet. I will shortly, but wanted to relay this. The desktop is up (and has been). Previous widgets are there and working. I can right click on the desktop and select the options present, and those work. From there I can open Dolphin, or select 'Leave' to logoff, restart etc, all of which work fine. Its just that when I click specifically on the Start gecko, I get the following bubble popup message just over the start gecko right where the menu should be: Error loading QML file: file:///usr/share/ plasma/plasmoids/org.kde.plasma.kicker/ contents/ui/main.qml27.1: module "org.kde.plasma.private.kicker" is not installed Before I proceed with the below, I'll wait to see if this provides any more clues as to what to do. Many thanks, Jim F
*if it fails*, please run:
update-alternatives --display default-displaymanager
and tell the results.
Mine:
Telcontar:~ # update-alternatives --display default-displaymanager default-displaymanager - auto mode link best version is /usr/lib/X11/displaymanagers/sddm link currently points to /usr/lib/X11/displaymanagers/sddm link default-displaymanager is /usr/lib/X11/displaymanagers/default-displaymanager /usr/lib/X11/displaymanagers/console - priority 5 /usr/lib/X11/displaymanagers/gdm - priority 25 /usr/lib/X11/displaymanagers/kdm - priority 15 /usr/lib/X11/displaymanagers/lightdm - priority 15 /usr/lib/X11/displaymanagers/sddm - priority 25 /usr/lib/X11/displaymanagers/xdm - priority 10 Telcontar:~ #
I don't remember if the default for a plasma systemd is "kdm"; you could try switching to "sddm" instead, but you might have to install it:
zypper install sddm
Once installed, to do the switch you would do:
init 3
update-alternatives --set default-displaymanager \ /usr/lib/X11/displaymanagers/sddm
init 5
And maybe with that you get a graphical login.
Then, try to login to plasma, and if that fails, try other desktops till one works. You might have to install some extra pattern to get more desktops.
Note: doc for update-alternatives:
https://doc.opensuse.org/release-notes/x86_64/openSUSE/Leap/15.0/#general
Section 5.2
On 21/12/2020 21.50, Jim Flanagan wrote:
On 12/21/20 2:34 PM, Carlos E. R. wrote:
On 21/12/2020 19.25, Jim Flanagan wrote:
On 12/20/20 6:39 PM, Carlos E. R. wrote:
On Sunday, 2020-12-20 at 16:55 -0600, Jim Flanagan wrote:
...
Welcome. Let's go step by step.
I also found this searching the web. What about re-installing plasma.desktop or updating it?
https://forums.opensuse.org/showthread.php/541072-no-menu-available-after-up...
I don't think it applies to your problem. He said he did a fresh install without formatting, and that's a recipe for problems. If you can not format, the correct procedure is "upgrade", as you did.
But you got some advice from Patrick that might work [...] Ok, I see it didn't.
Ok, what happens if, on the text console, you do:
init 3 init 5
Tell the exact errors you get. Take a photo perhaps.
I can and have been going to tty (F1) and can log in as jim and root. I have run init 3 just ot shut down the desktop before i make changes. Then running init 5 takes me back to desktop login (KDE).
Ok, Good. :-)
I can do this in tty on that machine or thru temrinal on my macbook. I've even run init 6 via remote terminal to restart the machine, works fine.
The system is up and running, and has been. That "logitechmediaserver" rpm is managed thru http://localhost:9000, that's the only display built in, so I don't see that that would be a problem. And it is working fine.
I haven't done the rest of your suggestions below yet. I will shortly, but wanted to relay this. The desktop is up (and has been). Previous widgets are there and working. I can right click on the desktop and select the options present, and those work. From there I can open Dolphin, or select 'Leave' to logoff, restart etc, all of which work fine.
Its just that when I click specifically on the Start gecko, I get the following bubble popup message just over the start gecko right where the menu should be:
Error loading QML file: file:///usr/share/ plasma/plasmoids/org.kde.plasma.kicker/ contents/ui/main.qml27.1: module "org.kde.plasma.private.kicker" is not installed
Ok, then I would switch to any other desktop except plasma till all other quirks are ironed out or someone finds how to solve that particular problem.
Before I proceed with the below, I'll wait to see if this provides any more clues as to what to do.
No, those instructions assumed that you did not get a graphical desktop and were trying to solve that. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 12/21/20 3:30 PM, Carlos E. R. wrote:
On 21/12/2020 21.50, Jim Flanagan wrote:
On 12/21/20 2:34 PM, Carlos E. R. wrote:
On 21/12/2020 19.25, Jim Flanagan wrote:
On 12/20/20 6:39 PM, Carlos E. R. wrote:
On Sunday, 2020-12-20 at 16:55 -0600, Jim Flanagan wrote:
...
Welcome. Let's go step by step.
I also found this searching the web. What about re-installing plasma.desktop or updating it?
https://forums.opensuse.org/showthread.php/541072-no-menu-available-after-up...
I don't think it applies to your problem. He said he did a fresh install without formatting, and that's a recipe for problems. If you can not format, the correct procedure is "upgrade", as you did.
But you got some advice from Patrick that might work [...] Ok, I see it didn't.
Ok, what happens if, on the text console, you do:
init 3 init 5
Tell the exact errors you get. Take a photo perhaps.
I can and have been going to tty (F1) and can log in as jim and root. I have run init 3 just ot shut down the desktop before i make changes. Then running init 5 takes me back to desktop login (KDE).
Ok, Good. :-)
I can do this in tty on that machine or thru temrinal on my macbook. I've even run init 6 via remote terminal to restart the machine, works fine.
The system is up and running, and has been. That "logitechmediaserver" rpm is managed thru http://localhost:9000, that's the only display built in, so I don't see that that would be a problem. And it is working fine.
I haven't done the rest of your suggestions below yet. I will shortly, but wanted to relay this. The desktop is up (and has been). Previous widgets are there and working. I can right click on the desktop and select the options present, and those work. From there I can open Dolphin, or select 'Leave' to logoff, restart etc, all of which work fine.
Its just that when I click specifically on the Start gecko, I get the following bubble popup message just over the start gecko right where the menu should be:
Error loading QML file: file:///usr/share/ plasma/plasmoids/org.kde.plasma.kicker/ contents/ui/main.qml27.1: module "org.kde.plasma.private.kicker" is not installed
Ok, then I would switch to any other desktop except plasma till all other quirks are ironed out or someone finds how to solve that particular problem.
OK, how do I switch to another desktop, and install one if needed?
Before I proceed with the below, I'll wait to see if this provides any more clues as to what to do.
No, those instructions assumed that you did not get a graphical desktop and were trying to solve that.
Understood. Will not work on the rest of that. Thanks, Jim F
On 21/12/2020 22.43, Jim Flanagan wrote:
On 12/21/20 3:30 PM, Carlos E. R. wrote:
On 21/12/2020 21.50, Jim Flanagan wrote:
...
Ok, Good. :-)
I can do this in tty on that machine or thru temrinal on my macbook. I've even run init 6 via remote terminal to restart the machine, works fine.
The system is up and running, and has been. That "logitechmediaserver" rpm is managed thru http://localhost:9000, that's the only display built in, so I don't see that that would be a problem. And it is working fine.
I haven't done the rest of your suggestions below yet. I will shortly, but wanted to relay this. The desktop is up (and has been). Previous widgets are there and working. I can right click on the desktop and select the options present, and those work. From there I can open Dolphin, or select 'Leave' to logoff, restart etc, all of which work fine.
Its just that when I click specifically on the Start gecko, I get the following bubble popup message just over the start gecko right where the menu should be:
Error loading QML file: file:///usr/share/ plasma/plasmoids/org.kde.plasma.kicker/ contents/ui/main.qml27.1: module "org.kde.plasma.private.kicker" is not installed
Ok, then I would switch to any other desktop except plasma till all other quirks are ironed out or someone finds how to solve that particular problem.
OK, how do I switch to another desktop, and install one if needed?
When you are at the login screen, after selecting your name, there will be somewhere to click and select another desktop. zypper pt lists the available patterns. There is "xfce" for instance. Or "lxqt". But XFCE is totally different from plasma, so in your case, probably better. I think: zypper install -t pattern xfce would install xfce. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 12/21/20 4:02 PM, Carlos E. R. wrote:
On 21/12/2020 22.43, Jim Flanagan wrote:
On 12/21/20 3:30 PM, Carlos E. R. wrote:
On 21/12/2020 21.50, Jim Flanagan wrote:
...
Ok, Good. :-)
I can do this in tty on that machine or thru temrinal on my macbook. I've even run init 6 via remote terminal to restart the machine, works fine.
The system is up and running, and has been. That "logitechmediaserver" rpm is managed thru http://localhost:9000, that's the only display built in, so I don't see that that would be a problem. And it is working fine.
I haven't done the rest of your suggestions below yet. I will shortly, but wanted to relay this. The desktop is up (and has been). Previous widgets are there and working. I can right click on the desktop and select the options present, and those work. From there I can open Dolphin, or select 'Leave' to logoff, restart etc, all of which work fine.
Its just that when I click specifically on the Start gecko, I get the following bubble popup message just over the start gecko right where the menu should be:
Error loading QML file: file:///usr/share/ plasma/plasmoids/org.kde.plasma.kicker/ contents/ui/main.qml27.1: module "org.kde.plasma.private.kicker" is not installed
Ok, then I would switch to any other desktop except plasma till all other quirks are ironed out or someone finds how to solve that particular problem.
OK, how do I switch to another desktop, and install one if needed?
When you are at the login screen, after selecting your name, there will be somewhere to click and select another desktop.
zypper pt
lists the available patterns.
There is "xfce" for instance. Or "lxqt". But XFCE is totally different from plasma, so in your case, probably better.
I think:
zypper install -t pattern xfce
would install xfce.
OK I logged into IceWM. Nice little desktop. Seems functional with a start menu that is working. However I still get that error in yast when I try to run Software Management. (Different post). I did edit a samba setting in yast and that seemed to work. So still having trouble with yast package management, and that KDE/plasma kicker error (but not on this dekstop). Jim F
On 21/12/2020 23.40, Jim Flanagan wrote:
On 12/21/20 4:02 PM, Carlos E. R. wrote:
...
OK I logged into IceWM. Nice little desktop. Seems functional with a start menu that is working.
However I still get that error in yast when I try to run Software Management. (Different post). I did edit a samba setting in yast and that seemed to work. So still having trouble with yast package management, and that KDE/plasma kicker error (but not on this dekstop).
At least, that gives you a workable desktop in which to do things and try to repair other things. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 12/21/20 5:12 PM, Carlos E. R. wrote:
On 21/12/2020 23.40, Jim Flanagan wrote:
On 12/21/20 4:02 PM, Carlos E. R. wrote:
...
OK I logged into IceWM. Nice little desktop. Seems functional with a start menu that is working.
However I still get that error in yast when I try to run Software Management. (Different post). I did edit a samba setting in yast and that seemed to work. So still having trouble with yast package management, and that KDE/plasma kicker error (but not on this dekstop).
At least, that gives you a workable desktop in which to do things and try to repair other things.
Yes it does! Thanks, Jim F
On 22/12/2020 00.32, Jim Flanagan wrote:
On 12/21/20 5:12 PM, Carlos E. R. wrote:
On 21/12/2020 23.40, Jim Flanagan wrote:
On 12/21/20 4:02 PM, Carlos E. R. wrote:
...
OK I logged into IceWM. Nice little desktop. Seems functional with a start menu that is working.
However I still get that error in yast when I try to run Software Management. (Different post). I did edit a samba setting in yast and that seemed to work. So still having trouble with yast package management, and that KDE/plasma kicker error (but not on this dekstop).
At least, that gives you a workable desktop in which to do things and try to repair other things.
Yes it does! Thanks,
Does meld work now? If it does, you could work at the rpm* files, one by one... I know it is tedious, but it should be done. And sometimes you get surprises. Doing without meld is possible, though. You just have to open both files on two windows of the same editor and work it out manually... It is even more tedious :-( I wish there were other editors of meld type. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 21/12/2020 23.40, Jim Flanagan wrote:
On 12/21/20 4:02 PM, Carlos E. R. wrote:
On 21/12/2020 22.43, Jim Flanagan wrote:
On 12/21/20 3:30 PM, Carlos E. R. wrote:
On 21/12/2020 21.50, Jim Flanagan wrote:
...
OK I logged into IceWM. Nice little desktop. Seems functional with a start menu that is working.
However I still get that error in yast when I try to run Software Management. (Different post). I did edit a samba setting in yast and that seemed to work. So still having trouble with yast package management, and that KDE/plasma kicker error (but not on this dekstop).
Notice that with "yast2 online_update" you can manage to do many of the jobs of the package manager. By default it shows the "patches" tab, but you can activate the "repositories" tab and do the job. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 12/21/20 6:43 PM, Carlos E. R. wrote:
On 21/12/2020 23.40, Jim Flanagan wrote:
On 12/21/20 4:02 PM, Carlos E. R. wrote:
On 21/12/2020 22.43, Jim Flanagan wrote:
On 12/21/20 3:30 PM, Carlos E. R. wrote:
On 21/12/2020 21.50, Jim Flanagan wrote:
...
OK I logged into IceWM. Nice little desktop. Seems functional with a start menu that is working.
However I still get that error in yast when I try to run Software Management. (Different post). I did edit a samba setting in yast and that seemed to work. So still having trouble with yast package management, and that KDE/plasma kicker error (but not on this dekstop).
Notice that with "yast2 online_update" you can manage to do many of the jobs of the package manager. By default it shows the "patches" tab, but you can activate the "repositories" tab and do the job.
Interesting, when I click on the Repositories tab I see a blue link above the packge listing saying: 'Switch system packages to the versions in this repository (Main repository)' Switch system packages is in blue and is an active link. Jim F
Heres the results of resolving the conflict list in yast. #### YaST2 conflicts list - generated 2020-12-21 19:04:51 #### libctf0-2.35.1-lp152.4.6.1.x86_64 requires libbfd-2.35.1.20201123-lp152.4.6.so()(64bit), but this requirement cannot be provided [ ] deinstallation of libctf0-2.35.1-lp152.4.6.1.x86_64 [ ] keep obsolete binutils-2.35.1-lp152.4.6.1.x86_64 [ ] break libctf0-2.35.1-lp152.4.6.1.x86_64 by ignoring some of its dependencies nothing provides this-is-only-for-build-envs needed by systemd-mini-234-lp152.31.13.1.x86_64 [ ] Following actions will be done: keep obsolete systemd-234-lp152.31.13.1.x86_64 keep obsolete udev-234-lp152.31.13.1.x86_64 [ ] deinstallation of systemd-network-234-lp152.31.13.1.x86_64 [ ] break systemd-mini-234-lp152.31.13.1.x86_64 by ignoring some of its dependencies #### YaST2 conflicts list END ### On Mon, Dec 21, 2020 at 7:09 PM Jim Flanagan <parttimelinux@gmail.com> wrote:
On 12/21/20 6:43 PM, Carlos E. R. wrote:
On 21/12/2020 23.40, Jim Flanagan wrote:
On 12/21/20 4:02 PM, Carlos E. R. wrote:
On 21/12/2020 22.43, Jim Flanagan wrote:
On 12/21/20 3:30 PM, Carlos E. R. wrote:
On 21/12/2020 21.50, Jim Flanagan wrote:
...
OK I logged into IceWM. Nice little desktop. Seems functional with a start menu that is working.
However I still get that error in yast when I try to run Software Management. (Different post). I did edit a samba setting in yast and that seemed to work. So still having trouble with yast package management, and that KDE/plasma kicker error (but not on this dekstop).
Notice that with "yast2 online_update" you can manage to do many of the jobs of the package manager. By default it shows the "patches" tab, but you can activate the "repositories" tab and do the job.
Interesting, when I click on the Repositories tab I see a blue link above the packge listing saying:
'Switch system packages to the versions in this repository (Main repository)'
Switch system packages is in blue and is an active link.
Jim F
On 22/12/2020 02.20, Jim Flanagan wrote:
Heres the results of resolving the conflict list in yast.
#### YaST2 conflicts list - generated 2020-12-21 19:04:51 ####
libctf0-2.35.1-lp152.4.6.1.x86_64 requires libbfd-2.35.1.20201123-lp152.4.6.so <http://libbfd-2.35.1.20201123-lp152.4.6.so>()(64bit), but this requirement cannot be provided
[ ] deinstallation of libctf0-2.35.1-lp152.4.6.1.x86_64
[ ] keep obsolete binutils-2.35.1-lp152.4.6.1.x86_64
[ ] break libctf0-2.35.1-lp152.4.6.1.x86_64 by ignoring some of its dependencies
What were you trying to do when you got that and the below paragraph? Were you trying to do a "Switch system packages to the versions in this repository"? What repository was activated on the left side? If you had "Main repository", notice that this switch would undo the packman switch, so it is not a good idea.
nothing provides this-is-only-for-build-envs needed by systemd-mini-234-lp152.31.13.1.x86_64
[ ] Following actions will be done: keep obsolete systemd-234-lp152.31.13.1.x86_64 keep obsolete udev-234-lp152.31.13.1.x86_64 [ ] deinstallation of systemd-network-234-lp152.31.13.1.x86_64
[ ] break systemd-mini-234-lp152.31.13.1.x86_64 by ignoring some of its dependencies
#### YaST2 conflicts list END ###
-- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 22/12/2020 02.09, Jim Flanagan wrote:
On 12/21/20 6:43 PM, Carlos E. R. wrote:
On 21/12/2020 23.40, Jim Flanagan wrote:
On 12/21/20 4:02 PM, Carlos E. R. wrote:
On 21/12/2020 22.43, Jim Flanagan wrote:
On 12/21/20 3:30 PM, Carlos E. R. wrote:
On 21/12/2020 21.50, Jim Flanagan wrote:
...
OK I logged into IceWM. Nice little desktop. Seems functional with a start menu that is working.
However I still get that error in yast when I try to run Software Management. (Different post). I did edit a samba setting in yast and that seemed to work. So still having trouble with yast package management, and that KDE/plasma kicker error (but not on this dekstop).
Notice that with "yast2 online_update" you can manage to do many of the jobs of the package manager. By default it shows the "patches" tab, but you can activate the "repositories" tab and do the job.
Interesting, when I click on the Repositories tab I see a blue link above the packge listing saying:
'Switch system packages to the versions in this repository (Main repository)'
Switch system packages is in blue and is an active link.
Has always been there :-) For example, if you select the packman repo and click on that "switch" link, you effectively do the "packman switch" (if you then accept). -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 12/21/20 3:30 PM, Carlos E. R. wrote:
On 21/12/2020 21.50, Jim Flanagan wrote:
On 12/21/20 2:34 PM, Carlos E. R. wrote:
On 21/12/2020 19.25, Jim Flanagan wrote:
On 12/20/20 6:39 PM, Carlos E. R. wrote:
On Sunday, 2020-12-20 at 16:55 -0600, Jim Flanagan wrote:
...
Welcome. Let's go step by step.
Ok, what happens if, on the text console, you do:
init 3 init 5
Tell the exact errors you get. Take a photo perhaps.
I can and have been going to tty (F1) and can log in as jim and root. I have run init 3 just ot shut down the desktop before i make changes. Then running init 5 takes me back to desktop login (KDE).
Ok, Good. :-)
I can do this in tty on that machine or thru temrinal on my macbook. I've even run init 6 via remote terminal to restart the machine, works fine.
Its just that when I click specifically on the Start gecko, I get the following bubble popup message just over the start gecko right where the menu should be:
Error loading QML file: file:///usr/share/ plasma/plasmoids/org.kde.plasma.kicker/ contents/ui/main.qml27.1: module "org.kde.plasma.private.kicker" is not installed
Ok, then I would switch to any other desktop except plasma till all other quirks are ironed out or someone finds how to solve that particular problem.
With the same kicker menu problem still present, I also get the following popup error when I run yast in console, then selecting Software Management pops up: Internal error. Please report a but report with logs. run the save_y2logs to get complete logs. Caller: /usr/lib64/ruby/2.5.0/rubygems/core_ext/kernel_require.rb: 59: in 'require' Details: Failed to load Module "Packages' due to: Failed to load Module 'AddOnProduct' due to: cannot load such file --r2packager/repository This is not new, but existed since I started looking into the failed kicker problem. Jim F
On 21/12/2020 22.56, Jim Flanagan wrote:
On 12/21/20 3:30 PM, Carlos E. R. wrote:
...
With the same kicker menu problem still present, I also get the following popup error when I run yast in console, then selecting Software Management pops up:
Internal error. Please report a but report with logs. run the save_y2logs to get complete logs.
Caller: /usr/lib64/ruby/2.5.0/rubygems/core_ext/kernel_require.rb: 59: in 'require'
Details: Failed to load Module "Packages' due to: Failed to load Module 'AddOnProduct' due to: cannot load such file --r2packager/repository
This is not new, but existed since I started looking into the failed kicker problem.
This is very strange. Try: open a terminal, then do: su - yast2 sw_single & or yast2 online_update & Do not use "sudo", and do not use "su". Use "su -", with the dash. If the above fails, try: rpm -q yast2-packager If it is missing, install it: zypper install yast2-packager Maybe, even if it is installed, install it again. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 12/21/20 4:14 PM, Carlos E. R. wrote:
On 21/12/2020 22.56, Jim Flanagan wrote:
On 12/21/20 3:30 PM, Carlos E. R. wrote:
...
This is not new, but existed since I started looking into the failed kicker problem.
This is very strange.
Try:
open a terminal, then do:
su - yast2 sw_single &
or
yast2 online_update &
Do not use "sudo", and do not use "su". Use "su -", with the dash.
If the above fails, try:
rpm -q yast2-packager
If it is missing, install it:
zypper install yast2-packager
Maybe, even if it is installed, install it again.
Ok I tried all of that. The second one 'yast2 online_update &' did open software update. But I didn't seen any packages populated in the list areas tot he left or right. didn't fix the yast issue. So I ran rpm - q and that package was installed. I removed it and installed it. It showed lots of other packages being removed, didn't see those on install. And, now in yast on the desktop, Update Software is not listed in Software anylonger. Sheesh.... Jim F
On 22/12/2020 00.04, Jim Flanagan wrote:
On 12/21/20 4:14 PM, Carlos E. R. wrote:
On 21/12/2020 22.56, Jim Flanagan wrote:
On 12/21/20 3:30 PM, Carlos E. R. wrote:
...
This is not new, but existed since I started looking into the failed kicker problem.
This is very strange.
Try:
open a terminal, then do:
su - yast2 sw_single &
or
yast2 online_update &
Do not use "sudo", and do not use "su". Use "su -", with the dash.
If the above fails, try:
rpm -q yast2-packager
If it is missing, install it:
zypper install yast2-packager
Maybe, even if it is installed, install it again.
Ok I tried all of that. The second one 'yast2 online_update &' did open software update. But I didn't seen any packages populated in the list areas tot he left or right. didn't fix the yast issue.
Well, that one only displays patches if there is any, otherwise it shows empty.
So I ran rpm - q and that package was installed. I removed it and installed it. It showed lots of other packages being removed, didn't see those on install. And, now in yast on the desktop, Update Software is not listed in Software anylonger.
Huh, you should not "remove" to do a re-install. In zypper I think you just have to "force" install. What do you get now when you do: yast2 sw_single & if parts of yast are missing, try: zypper install -t pattern yast2_basis Then: zypper se yast to find the name of parts, then install those you think you should have. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 12/21/20 5:12 PM, Carlos E. R. wrote:
On 22/12/2020 00.04, Jim Flanagan wrote:
On 12/21/20 4:14 PM, Carlos E. R. wrote:
On 21/12/2020 22.56, Jim Flanagan wrote:
On 12/21/20 3:30 PM, Carlos E. R. wrote:
...
This is not new, but existed since I started looking into the failed kicker problem.
This is very strange.
Try:
open a terminal, then do:
su - yast2 sw_single &
or
yast2 online_update &
Do not use "sudo", and do not use "su". Use "su -", with the dash.
If the above fails, try:
rpm -q yast2-packager
If it is missing, install it:
zypper install yast2-packager
Maybe, even if it is installed, install it again.
Ok I tried all of that. The second one 'yast2 online_update &' did open software update. But I didn't seen any packages populated in the list areas tot he left or right. didn't fix the yast issue.
Well, that one only displays patches if there is any, otherwise it shows empty.
So I ran rpm - q and that package was installed. I removed it and installed it. It showed lots of other packages being removed, didn't see those on install. And, now in yast on the desktop, Update Software is not listed in Software anylonger.
Huh, you should not "remove" to do a re-install. In zypper I think you just have to "force" install.
What do you get now when you do:
yast2 sw_single &
This opens software management but the same error popup comes up.
if parts of yast are missing, try:
zypper install -t pattern yast2_basis
The uninstall remobed 34 packages. This line installed 23 packages, plus yast2-packager I manually installed.
Then:
zypper se yast
to find the name of parts, then install those you think you should have.
I'll bump both lists to see what I trashed. Thanks again, Jim F
On 22/12/2020 00.30, Jim Flanagan wrote:
On 12/21/20 5:12 PM, Carlos E. R. wrote:
On 22/12/2020 00.04, Jim Flanagan wrote:
Huh, you should not "remove" to do a re-install. In zypper I think you just have to "force" install.
What do you get now when you do:
yast2 sw_single &
This opens software management but the same error popup comes up.
What, this? Internal error. Please report a but report with logs. run the save_y2logs to get complete logs. Caller: /usr/lib64/ruby/2.5.0/rubygems/core_ext/kernel_require.rb: 59: in 'require' Details: Failed to load Module "Packages' due to: Failed to load Module 'AddOnProduct' due to: cannot load such file --r2packager/repository Please, do not say "I get an error", we need to see the exact error. I was googling for a bit that error, and in one case it was a TW install, in another there were some TW repos in the mix. This is not the case, we reviewed your repository list and your list of packages. Another chap had the problem on 15.2 upgraded from 15.1 and they did not find the cause, but he had some etc directories in bad shape. <https://forums.opensuse.org/showthread.php/545284-LEAP-15-2-Yast-Error-Failed-to-load-Module-Packages>
if parts of yast are missing, try:
zypper install -t pattern yast2_basis
The uninstall remobed 34 packages. This line installed 23 packages, plus yast2-packager I manually installed.
Then:
zypper se yast
to find the name of parts, then install those you think you should have.
I'll bump both lists to see what I trashed. Ok.
We could also re-install (without a delete step, mind) ruby related packages. But I do not have much faith in that move. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 12/21/20 5:12 PM, Carlos E. R. wrote:
On 22/12/2020 00.04, Jim Flanagan wrote:
On 12/21/20 4:14 PM, Carlos E. R. wrote:
On 21/12/2020 22.56, Jim Flanagan wrote:
On 12/21/20 3:30 PM, Carlos E. R. wrote:
...
This is not new, but existed since I started looking into the failed kicker problem.
This is very strange.
Try:
open a terminal, then do:
su - yast2 sw_single &
or
yast2 online_update &
Do not use "sudo", and do not use "su". Use "su -", with the dash.
If the above fails, try:
rpm -q yast2-packager
If it is missing, install it:
zypper install yast2-packager
Maybe, even if it is installed, install it again.
Ok I tried all of that. The second one 'yast2 online_update &' did open software update. But I didn't seen any packages populated in the list areas tot he left or right. didn't fix the yast issue.
Well, that one only displays patches if there is any, otherwise it shows empty.
So I ran rpm - q and that package was installed. I removed it and installed it. It showed lots of other packages being removed, didn't see those on install. And, now in yast on the desktop, Update Software is not listed in Software anylonger.
Huh, you should not "remove" to do a re-install. In zypper I think you just have to "force" install.
What do you get now when you do:
yast2 sw_single &
if parts of yast are missing, try:
zypper install -t pattern yast2_basis
Then:
zypper se yast
to find the name of parts, then install those you think you should have.
OK I bumped the two lists and re-installed those missing ones that I inadvertently trashed. I added one in and it brought all the others along with it, 8 in total. So I think I'm back to where I started. Neither the plasma kicker problem or the yast problem is resolved. Not at all sure what to do now. My music server is working fine, and I do have a working IceWM desktop. In yast in desktop Software Management returns that same error, as does Software Repositories. Online Update does run but shows no updates in the boxes. I'm starting to think a fresh install will fix this, but I'm not in a hurry. And I'm learning more about how packages get installed thru zypper. Getting a bit of a clue to how that works. I still prefer yast if I can get it working. In any case, much appreciate your good help. Jim F
On 22/12/2020 01.52, Jim Flanagan wrote:
On 12/21/20 5:12 PM, Carlos E. R. wrote:
OK I bumped the two lists and re-installed those missing ones that I inadvertently trashed. I added one in and it brought all the others along with it, 8 in total. So I think I'm back to where I started.
Neither the plasma kicker problem or the yast problem is resolved.
Not at all sure what to do now. My music server is working fine, and I do have a working IceWM desktop.
In yast in desktop Software Management returns that same error, as does Software Repositories. Online Update does run but shows no updates in the boxes.
Did you see my post about using online update instead? There is a trick.
I'm starting to think a fresh install will fix this, but I'm not in a hurry. And I'm learning more about how packages get installed thru zypper. Getting a bit of a clue to how that works. I still prefer yast if I can get it working.
In any case, much appreciate your good help.
New errors mean learning new things... There is, of course, the avenue of reporting the yast error in bugzilla. There is a bug there, we just do not know what triggers it. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
Jim Flanagan composed on 2020-12-21 18:52 (UTC-0600):
...I'm learning more about how packages get installed thru zypper. Getting a bit of a clue to how that works. I still prefer yast if I can get it working.
Try this: sudo rpm -qa | egrep -v 'lp152|pm152' The output should reveal any packages that do not belong, or didn't get upgraded, plus logitechmediaserver. I have a script to do something similar using zypper: # cat /usr/local/bin/zypseo #!/bin/sh zypper --no-refresh se -si | grep 'tem Pac' | grep -v plication -- Evolution as taught in public schools, like religion, is based on faith, not on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
On 22/12/2020 02.32, Felix Miata wrote:
Jim Flanagan composed on 2020-12-21 18:52 (UTC-0600):
...I'm learning more about how packages get installed thru zypper. Getting a bit of a clue to how that works. I still prefer yast if I can get it working.
Try this:
sudo rpm -qa | egrep -v 'lp152|pm152'
We did that already. The list is here: https://susepaste.org/6481544 You only have to do the egrep and find them. They were only packman packages, because the upgrade had disabled the packman repo and had to be activated again. :-) -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 12/21/20 4:14 PM, Carlos E. R. wrote:
On 21/12/2020 22.56, Jim Flanagan wrote:
On 12/21/20 3:30 PM, Carlos E. R. wrote:
...
This is not new, but existed since I started looking into the failed kicker problem.
This is very strange.
Try:
open a terminal, then do:
su - yast2 sw_single &
or
yast2 online_update &
Do not use "sudo", and do not use "su". Use "su -", with the dash.
If the above fails, try:
rpm -q yast2-packager
If it is missing, install it:
zypper install yast2-packager
Maybe, even if it is installed, install it again.
Ok I tried all of that. The second one 'yast2 online_update &' did open software update. But I didn't seen any packages populated in the list areas tot he left or right. didn't fix the yast issue. So I ran rpm - q and that package was installed. I removed it and installed it. It showed lots of other packages being removed, didn't see those on install. And, now in yast on the desktop, Update Software is not listed in Software any longer. Sheesh.... Jim F
* Jim Flanagan <parttimelinux@gmail.com> [12-21-20 15:54]: [...]
Its just that when I click specifically on the Start gecko, I get the following bubble popup message just over the start gecko right where the menu should be:
Error loading QML file: file:///usr/share/ plasma/plasmoids/org.kde.plasma.kicker/ contents/ui/main.qml27.1: module "org.kde.plasma.private.kicker" is not installed
Before I proceed with the below, I'll wait to see if this provides any more clues as to what to do.
app is provided by plasma5-desktop as root: zypper -v in --force plasma5-desktop that should not hurt anything. -- (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 freenode
On 12/21/20 5:32 PM, Patrick Shanahan wrote:
* Jim Flanagan <parttimelinux@gmail.com> [12-21-20 15:54]: [...]
Its just that when I click specifically on the Start gecko, I get the following bubble popup message just over the start gecko right where the menu should be:
Error loading QML file: file:///usr/share/ plasma/plasmoids/org.kde.plasma.kicker/ contents/ui/main.qml27.1: module "org.kde.plasma.private.kicker" is not installed
Before I proceed with the below, I'll wait to see if this provides any more clues as to what to do.
app is provided by plasma5-desktop
as root: zypper -v in --force plasma5-desktop
that should not hurt anything.
After I reinstalled the packages I trashed, I got them all back and did the force install. This did not resolve either the plasma kicker problem or the yast2 error problem. Was a good try. Jim F
On 12/20/20 5:39 PM, Carlos E. R. wrote:
On Sunday, 2020-12-20 at 16:55 -0600, Jim Flanagan wrote:
On 12/20/20 4:40 PM, Carlos E. R. wrote:
...
You also have "logitechmediaserver" which seems to be a proprietary package?
This is the main use i have for this machine, its my music server. I love it. This is why I chose to do a 'upgrade' instead of an clean 'install'. I recall have a few problems getting it to run on Leap 15.0 and earlier openSUSE releases. Oddly it is working well, so I'm happy wiht that, especially during the Christmas season. I just can't do anyting on the computer desktop LOL. Ah, I see.
About the old "gpg-pubkey", ignore them.
repolist.txt posted here https://paste.opensuse.org/73544223 Ok, the repository list is "almost" perfect, only packman is missing.
You have to do:
zypper ar -f -n "Packman Repository" "http://packman.inode.at/suse/openSUSE_Leap_15.2/" "Packman"
then you should do:
zypper up
and tell here what is the result.
If worse comes to worse, I could do a new clean install. That should get me a good clean working system, but I'm not sure how difficult it will be at that point to re-install 'logitechmediaserver".
Thanks for the great help.
Welcome. Let's go step by step.
-- Cheers, Carlos E. R.
Carlos and all, Just to close the loop on this, I never did resolve the issues I had after upgrading from Leap 15.1 to 15.2. I never had the time to track all the dependency issues down. As relayed previously after that upgrade to 15.2, Plasma would not run. I was able to get a desktop using IceWM. But even at that, in IceWM and in command line, Yast failed, would not update any packages, so the system was locally functional but could not be trusted on the internet. In any case I recently did an upgrade from this partially functioning 15.2 to Leap 15.3. Happy to report the system seems to be functioning normally. Plasma desktop with KDE, and the auto updates work too, as does Yast updates. The only issue I've encountered so far is Firefox would open but render a blank grey page, no tab or menu buttons. I forced an update of that thru Yast in KDE and that is functioning well now too. Firefox even remembered all my previously open tabs! So far so good. Thanks for all the great help on this issue. Jim F
On 12/19/20 6:17 PM, Carlos E. R. wrote:
On 20/12/2020 00.14, Jim Flanagan wrote:
On 12/19/20 1:59 PM, Carlos E. R. wrote:
On 19/12/2020 20.23, Jim Flanagan wrote:
On 12/19/20 1:13 PM, Carlos E. R. wrote:
On 19/12/2020 19.39, Jim Flanagan wrote:
On 12/18/20 9:17 PM, Felix Miata wrote: > Jim Flanagan composed on 2020-12-18 20:11 (UTC-0600):
...
Again, i'm rusty on command line. What now?
Keep working on that long string to get the output, or is it too late? Or run zypper up?
I need to see what is the result of those two commands I told you in order to decide what to do next.
Ok I found a way to open a txt file in KDE without the start menu. From another computer I pasted the long rpm string into a txt file to edit it. With thumb drive then pasting into konsole, but I keep getting invalid field width.
If you have another computer, then just open konsole in that good computer, and run:
ssh yourusername@IP_ADDRESS_of_bad_computer
and then paste the command line in there.
Or, create this script in the thumb drive:
+++····················· #/bin/bash rpm -q -a --queryformat "%{INSTALLTIME}\t%{INSTALLTIME:day} \ %{BUILDTIME:day} %-30{NAME}\t%15{VERSION}-%-7{RELEASE}\t%{arch} \ %25{VENDOR}%25{PACKAGER} == %{DISTRIBUTION} %{DISTTAG}\n" \ | sort | cut --fields="2-" | tee rpmlist.txt \ | egrep -v "openSUSE Leap 15\.2|openSUSE_Leap_15.2|-lp152" \
rpmlist_hits.txt
zypper lr --details > repolist.txt ·····················++-
And run it in the bad computer. The script will create files "rpmlist_hits.txt" and "repolist.txt" inside that thumb drive.
If there is an error, you did not paste the script correctly.
Then back in the good computer, upload those two files:
susepaste -n "Jim F" -t "possible wrong rpms" -e 151200 rpmlist_hits.txt susepaste -n "Jim F" -t "possible wrong rpms" -e 151200 repolist.txt
Posted rpmlist.txt to https://paste.opensuse.org/6481544 Jim F
On 12/19/20 1:59 PM, Carlos E. R. wrote:
On 19/12/2020 20.23, Jim Flanagan wrote:
On 12/19/20 1:13 PM, Carlos E. R. wrote:
On 19/12/2020 19.39, Jim Flanagan wrote:
On 12/18/20 9:17 PM, Felix Miata wrote:
Jim Flanagan composed on 2020-12-18 20:11 (UTC-0600):
...
Again, i'm rusty on command line. What now?
Keep working on that long string to get the output, or is it too late? Or run zypper up?
I need to see what is the result of those two commands I told you in order to decide what to do next.
Is there a way to open konsole while I'm in KDE even with the start menu nor working? I can right click the desktop and open Dolphin from the popup menu. Can I get a console that way?
On 21/12/2020 22.58, Jim Flanagan wrote:
On 12/19/20 1:59 PM, Carlos E. R. wrote:
On 19/12/2020 20.23, Jim Flanagan wrote:
On 12/19/20 1:13 PM, Carlos E. R. wrote:
On 19/12/2020 19.39, Jim Flanagan wrote:
On 12/18/20 9:17 PM, Felix Miata wrote:
Jim Flanagan composed on 2020-12-18 20:11 (UTC-0600):
...
Again, i'm rusty on command line. What now?
Keep working on that long string to get the output, or is it too late? Or run zypper up?
I need to see what is the result of those two commands I told you in order to decide what to do next.
Is there a way to open konsole while I'm in KDE even with the start menu nor working? I can right click the desktop and open Dolphin from the popup menu. Can I get a console that way?
There is a shortcut, sure, but I don't know which it is in plasma. Try "Alt-F2", it works in XFCE. Someone else should comment on that. I can't verify, but google tells me that: "You can launch a terminal by pressing Ctrl + Alt + T or Ctrl + Shift + T" -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 2020-12-21 23:18, Carlos E. R. wrote:
There is a shortcut, sure, but I don't know which it is in plasma. Try "Alt-F2", it works in XFCE. Someone else should comment on that.
I can't verify, but google tells me that: "You can launch a terminal by pressing Ctrl + Alt + T or Ctrl + Shift + T"
Probably Alt-Space https://userbase.kde.org/Plasma/Krunner I can also use F10 on my lenovo laptop -- /bengan
Jim Flanagan composed on 2020-12-19 13:23 (UTC-0600):
run 'rpm --rebuilddb' to fix.
Again, i'm rusty on command line. What now?
run 'rpm --rebuilddb' to fix. Then repeat zypper dup, but don't Y if it reports aaa_base will be removed. If it does, then do zypper al aaa_bas* first, before proceeding with zypper dup. -- Evolution as taught in public schools, like religion, is based on faith, not on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
On 19/12/2020 22.15, Felix Miata wrote:
Jim Flanagan composed on 2020-12-19 13:23 (UTC-0600):
run 'rpm --rebuilddb' to fix.
Again, i'm rusty on command line. What now?
run 'rpm --rebuilddb' to fix. Then repeat zypper dup, but don't Y if it reports aaa_base will be removed. If it does, then do
zypper al aaa_bas*
first, before proceeding with zypper dup.
Better don't do anything till we get the needed information first. Specially, don't do any "zypper dup". -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 12/18/20 9:17 PM, Felix Miata wrote:
Jim Flanagan composed on 2020-12-18 20:11 (UTC-0600): ...
This system was first installed with Leap 15.0, upgraded to 15.1, now to a partially broken 15.2.
Any suggestions most welcome.
If you login to an IceWM session instead of Plasma, does everything there work?
To confirm the upgrade went as it should have, from any of the vttys, try:
sudo zypper ref sudo zypper dup
If no errors, but still fubar Plasma, try:
sudo zypper ve
If trouble still, attach to an email (not cut and paste within) output from:
sudo zypper lr -d
Maybe first try something simpler. Logged on a vtty instead of Plasma, delete the content of ~/.cache/, then start a Plasma session.
How do I delete this ~/.cache/ in command line. Yast Software Managment fails in KDE and tty. I think this might work. I also read a google search post on this exact issue wiht upgrading Leap 15.1 to 15.2. The poster uninstalled plasma and then reinstalled it. Said it worked. But I can't find that post again. Thanks, Jim F
* Jim Flanagan <parttimelinux@gmail.com> [12-20-20 18:36]:
On 12/18/20 9:17 PM, Felix Miata wrote:
Jim Flanagan composed on 2020-12-18 20:11 (UTC-0600): ...
This system was first installed with Leap 15.0, upgraded to 15.1, now to a partially broken 15.2.
Any suggestions most welcome.
If you login to an IceWM session instead of Plasma, does everything there work?
To confirm the upgrade went as it should have, from any of the vttys, try:
sudo zypper ref sudo zypper dup
If no errors, but still fubar Plasma, try:
sudo zypper ve
If trouble still, attach to an email (not cut and paste within) output from:
sudo zypper lr -d
Maybe first try something simpler. Logged on a vtty instead of Plasma, delete the content of ~/.cache/, then start a Plasma session.
How do I delete this ~/.cache/ in command line. Yast Software Managment fails in KDE and tty.
I think this might work. I also read a google search post on this exact issue wiht upgrading Leap 15.1 to 15.2. The poster uninstalled plasma and then reinstalled it. Said it worked. But I can't find that post again.
from the command line: rm -rf ~/.cache/ perhaps more prudent as you may recover, mv ~/.cache ~/.cache.hold and destroy later rm -rf ~/.cache.hold -- (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 freenode
On 12/20/20 5:52 PM, Patrick Shanahan wrote:
* Jim Flanagan <parttimelinux@gmail.com> [12-20-20 18:36]:
On 12/18/20 9:17 PM, Felix Miata wrote:
Jim Flanagan composed on 2020-12-18 20:11 (UTC-0600): ...
This system was first installed with Leap 15.0, upgraded to 15.1, now to a partially broken 15.2.
Any suggestions most welcome.
If you login to an IceWM session instead of Plasma, does everything there work?
To confirm the upgrade went as it should have, from any of the vttys, try:
sudo zypper ref sudo zypper dup
If no errors, but still fubar Plasma, try:
sudo zypper ve
If trouble still, attach to an email (not cut and paste within) output from:
sudo zypper lr -d
Maybe first try something simpler. Logged on a vtty instead of Plasma, delete the content of ~/.cache/, then start a Plasma session.
How do I delete this ~/.cache/ in command line. Yast Software Managment fails in KDE and tty.
I think this might work. I also read a google search post on this exact issue wiht upgrading Leap 15.1 to 15.2. The poster uninstalled plasma and then reinstalled it. Said it worked. But I can't find that post again.
from the command line: rm -rf ~/.cache/
perhaps more prudent as you may recover, mv ~/.cache ~/.cache.hold
and destroy later rm -rf ~/.cache.hold
So just enter the line as you typed it? No need to describe the ~/ ? Jim F
* Jim Flanagan <parttimelinux@gmail.com> [12-20-20 19:03]:
On 12/20/20 5:52 PM, Patrick Shanahan wrote: [...]
I think this might work. I also read a google search post on this exact issue wiht upgrading Leap 15.1 to 15.2. The poster uninstalled plasma and then reinstalled it. Said it worked. But I can't find that post again.
from the command line: rm -rf ~/.cache/
perhaps more prudent as you may recover, mv ~/.cache ~/.cache.hold
and destroy later rm -rf ~/.cache.hold So just enter the line as you typed it? No need to describe the ~/ ?
"~/" is bash shorthand for /home/<user>/ https://devhints.io/bash https://www.gnu.org/software/bash/manual/html_node/Tilde-Expansion.html but you must enter or copy and paste the exact line beginning with rm and/or mv. -- (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 freenode
On 12/20/20 6:07 PM, Patrick Shanahan wrote:
* Jim Flanagan <parttimelinux@gmail.com> [12-20-20 19:03]:
On 12/20/20 5:52 PM, Patrick Shanahan wrote: [...]
I think this might work. I also read a google search post on this exact issue wiht upgrading Leap 15.1 to 15.2. The poster uninstalled plasma and then reinstalled it. Said it worked. But I can't find that post again.
from the command line: rm -rf ~/.cache/
perhaps more prudent as you may recover, mv ~/.cache ~/.cache.hold
and destroy later rm -rf ~/.cache.hold So just enter the line as you typed it? No need to describe the ~/ ?
"~/" is bash shorthand for /home/<user>/
https://devhints.io/bash https://www.gnu.org/software/bash/manual/html_node/Tilde-Expansion.html
but you must enter or copy and paste the exact line beginning with rm and/or mv.
Deleting the contents of ~/.cache did not resolve this issue. Note, it happens logged in as me, also made a new user, no resolution, nor logged in as root. How can I uninstall and reinstall plasma in tty terminal? Thanks, Jim F
On 18/12/2020 21:11, Jim Flanagan wrote:
This system was first installed with Leap 15.0, upgraded to 15.1, now to a partially broken 15.2.
Tell me again: when is EOL for 15.1? -- “Reality is so complex, we must move away from dogma, whether it’s conspiracy theories or free-market,” -- James Glattfelder. http://jth.ch/jbg
On 20/12/2020 14.46, Anton Aylward wrote:
On 18/12/2020 21:11, Jim Flanagan wrote:
This system was first installed with Leap 15.0, upgraded to 15.1, now to a partially broken 15.2.
Tell me again: when is EOL for 15.1?
Early next year. January or February. Ah, exactly on January 31st 2021. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
participants (9)
-
Anton Aylward -
Bengt Gördén -
Carlos E. R. -
Carlos E.R. -
David C. Rankin -
Felix Miata -
Jim Flanagan -
Patrick Shanahan -
Per Jessen