On Fri, 8 Nov 2019 13:28:54 -0600 "David C. Rankin" wrote:

On 11/08/2019 02:50 AM, Felix Miata wrote:

...

David C. Rankin composed on 2019-11-08 02:24 (UTC-0600):

...

Any ideas what to check? Anything that could have been on in 42.3 that now has a conflict with the 15.0 packages? ModemManager? upower? wicked?

What non-current packages remain installed?

zypper --no-refresh se -si | grep 'tem Pac' | grep -v plication

Thank you Felix, I think I'm good there. I added a

... | awk -F'|' '{ print $1, $2, $4 }' to the end to shorten it up and I have:

i ImageMagick-config-6-SUSE 6.8.8.1-85.1 il MozillaThunderbird 52.9.1-71.1 i+ VirtualBox-5.2 5.2.34_133893_openSUSE132-1 i+ athena-jot 9.0-4.1 i epstool 3.08-1.11 i+ font-manager 0.7.3-1.3 i font-manager-lang 0.7.3-1.3 i+ fontmatrix 0.9.99+svn1220-2.1 i+ fontmatrix-lang 0.9.99+svn1220-2.1 i+ gcolor3 2.2-1.6 il geany 1.33-59.6 il geany-devel 1.33-59.6 il geany-lang 1.33-59.6 il geany-plugins 1.33-59.6 il geany-plugins-lang 1.33-59.6 i+ hunspell 1.3.2-7.4 i+ hunspell-tools 1.3.2-7.4 i+ kde3-digikam 0.9.6-53.3 i kde3-digikam-lang 0.9.6-53.3 i kdebindings3 3.5.10-113.19 i kdebindings3-ruby 3.5.10-113.19 il keepassx 0.4.3-9.1 i+ kernel-default 4.4.180-102.1 i kernel-default-devel 4.4.180-102.1 i kernel-devel 4.4.180-102.1 i kernel-source 4.4.180-102.1 i kernel-syms 4.4.180-102.1 i+ libfaad2-32bit 2.8.8-1.7 i+ libffi4-debuginfo 5.3.1+r233831-10.1 il libgeany0 1.33-59.6 i libgit2-24 0.24.1-10.6.1 i+ libgit2-devel 0.24.1-10.6.1 i+ libhttp-parser-suse0 2.6.2-3.3 i libjasper1 1.900.14-182.1 i liblua5_1 5.1.5-16.1 i libpodofo0_9_3 0.9.3-9.1 i libruby2_1-2_1 2.1.9-9.1 i+ libsox1 14.3.2-4.5 i libvpx1 1.3.0-8.1 i libvpx5 1.7.0-7.5 i libvpx6 1.8.1-7.1 i libx264-152 0.152svn20180305-5.3 i libx264-152-32bit 0.152svn20180305-5.3 i libx265-151 2.7-3.4 i libx265-169-32bit 3.0-1.2 i libx265-176-32bit 3.1.2-1.1 i+ menumaker 0.99.9-1.2 i python-M2Crypto 0.29.0-12.4.1 i python-six 1.11.0-9.4.1 i+ rdesktop 1.8.6-lp151.91.2 i+ rdesktop-debuginfo 1.8.3-7.1 i sqlite2 2.8.17-199.3 i+ xfe 1.42-1.1

I don't see anything above that would be resident and causing issue with the usb controller. Funny that zypper dup keeps the kernel from 42.3 under multiver. I wonder if it lets you attempt to boot it? That would be bad...

Am I missing something? Why would that be bad? Did the kernel ABI change? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 El 2019-11-08 a las 16:03 -0500, Felix Miata escribió:

David C. Rankin composed on 2019-11-08 13:28 (UTC-0600):

...

i kdebindings3 3.5.10-113.19

I don't see any such package on the mirrors for 15.0 or 15.1, but I do see it for TW.

That's important, should be doube checked. The commands I just posted would find such an error. - -- Cheers Carlos E. R. (from openSUSE 15.1 (Legolas)) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXcXiXhwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVHFMAn34D/PzCz9UlF/JxVgtw hO8eyhWwAJ0eNY1Mp5aM1GgejRy/ZDYSczFtRQ== =9QWv -----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 09/11/2019 10.06, David C. Rankin wrote:

On 11/08/2019 03:03 PM, Felix Miata wrote:

...

David C. Rankin composed on 2019-11-08 13:28 (UTC-0600):

...

i kdebindings3 3.5.10-113.19

I don't see any such package on the mirrors for 15.0 or 15.1, but I do see it for TW.

zypper dup left it as a "System Package" for some reason, e.g.

$ rqi kdebindings3 Name : kdebindings3 Version : 3.5.10 Release : 113.19 Architecture: x86_64 Install Date: Thu 31 Oct 2019 02:44:42 PM CDT Group : System/GUI/KDE Size : 24778496 License : GPL-2.0 and LGPL-2.1+ Signature : DSA/SHA1, Wed 30 Oct 2019 02:39:22 PM CDT, Key ID af92960d7c99e700 Source RPM : kdebindings3-3.5.10-113.19.src.rpm Build Date : Wed 30 Oct 2019 02:36:22 PM CDT Build Host : lamb62 Relocations : (not relocatable) Vendor : obs://build.opensuse.org/KDE:KDE3 URL : http://www.kde.org/ Summary : Bindings for Qt and KDE Libraries Description : This package contains generator applications for creating bindings for specific languages from Qt and KDE header files. Distribution: KDE:KDE3 / openSUSE_Leap_42.3

^^^^^^^^^^^^^^^^^^

It is a dependency for kdevelop. (still works) I don't know why it's not there for 15.0 -- but it's not. I don't see how that could be related to how kdebase and kdelibs are behaving regarding the styles. That is strange.

If you have other 15.0 installations without that package, remove it. I just told zypper to install kdevelop (then I aborted), and it does not complain about the absence of kdebindings3. - -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXcaUvQAKCRC1MxgcbY1H 1ctzAKCGZbxGQBxtjFuI0Y+lzdcx5bAQ+gCgk4hfo847uN5EfrFVsedYgwrFlFs= =n9Kn -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 El 2019-11-08 a las 14:14 -0600, David C. Rankin escribió:

On 11/08/2019 04:38 AM, Dave Howorth wrote:

...

Given how long [short] it is until EOL for 15.0, I think you'd do better to upgrade the machine again to 15.1 and see if the problem still exists. At least that way you'd have some chance of getting it fixed if it is still there.

Agreed and I'm damn sure going to do a wipe and reinstall instead of a zypper dup. I could have done 10 fresh-installs in the amount of time I've spent chasing these weird zypper dup side-effects. But I'll probably wait until 15.2 is out as 15.1 has vbox6 modules that throw 4 error messages up on the desktop every boot and I'd still have to patch the yast2-qt3 icons.

The upgrade of 15.0 to 15.1 is trivial compared to 42.3 to 15.0. The kernel and many things stay in the same basic version. I have upgraded 3 15.0 machines and the process was boring. - -- Cheers Carlos E. R. (from openSUSE 15.1 (Legolas)) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXcXjbxwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVDrwAn2u2f3A+juAyB6LOD9l8 Q2A8zHT2AJ0Z8/Yqmi0RJ0YxTgdYNZ+9nUrcpQ== =qBSH -----END PGP SIGNATURE-----

On 11/09/2019 08:15 AM, Per Jessen wrote:

...

Agreed and I'm damn sure going to do a wipe and reinstall instead of a zypper dup. I could have done 10 fresh-installs in the amount of time I've spent chasing these weird zypper dup side-effects. FWIW, I have done a few of those, from 42.3 and 15.0 - all clean. Only on servers though.

I wouldn't hesitate on server installs, the base dup went fine. (the mouse issue is a strange outlier). The hiccups have been with peripheral applications, desktop oddities and strange font issues that don't make sense and from what I can tell (given creating new users and checking behavior there) there is a system library file, symlink or stray config file somewhere that is causing the problem. I've searched and been trough the .rpmnew and .rpmsav differences and nothing of any significance was found. Little things like typing your password into the DM echos asterisks (actual '*') instead of the normal dot glyphs that are normally displayed. There is no way of explaining things like that (okay LOCALE, but that's correct) -- which is what got me started down the which font is the right font? issue. (however on the 15.0 and 15.1 fresh installs I have the same basic fonts selected by default and they show the dots correctly instead of the asterisks in the DM login.... Go figure. How do you sort out why one system is displaying asterisks instead of dots when you type your password in the DM? (it's not going to throw an error, it's just using some base mask character instead of what should be used by the desktop) The search goes on... -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 11/08/2019 05:41 AM, Carlos E.R. wrote:

On 08/11/2019 09.24, David C. Rankin wrote:

...

All,

I've watched this for the past couple of days since I updated to 15.0 from 42.3 with zypper dup. My usb controller has lost its mind and will just disconnect the mouse randomly -- then sometimes is reconnects moments later....

...

...

Any ideas what to check? Anything that could have been on in 42.3 that now has a conflict with the 15.0 packages? ModemManager? upower? wicked?

I would suggest to go ahead and continue to 15.1 :-D

If it was a bug, there is some posibility that it was solved. And if not solved but still a bug, you need 15.1 to report it.

Any extra repo, not the standard oss/non-oss plus packman?

Nothing crazy. I do have a number of repos enabled that I either pull build dependencies from or like x11wm, get fluxbox from (unless I had to build that for 15.0?) $ zlr | grep Yes | awk -F'|' -v OFS=" | " '{ print $1, $2 }' 1 | adobe 2 | cinelerra 4 | gnomeapps 6 | kde 8 | mozilla 9 | nonoss 10 | nvidia 11 | oss 12 | packman 14 | repo-debug 16 | repo-debug-update 21 | susetools 22 | update 23 | updtno 24 | videolan 26 | x11wm -- David C. Rankin, J.D.,P.E.

On 11/08/2019 03:42 PM, Carlos E. R. wrote:

Then you could generate this list:

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 \ | egrep -v "openSUSE_Leap_15.1|openSUSE\ Leap\ 15.1|-lp151" | less -S

change 15.1 to 15.0, add new entries as necesary; the concoction lists every thing that is not Leap 15.0. In the end there should be few exceptions listed, like cinelerra. But nothing that belongs to previous oS releases.

I have nothing post zypper dup (but I do have 65 entries), but the only think kde3 related is digikam (I removed kdebindings3). There were a lot of things that got switched from repo to repo. I had just run zypper -v dup -d -r packman --allow-v Not a month ago, and I had about 23 packages that were to scattered vendors again after the zypper dup. (I don't think the stuff will make any difference to the mouse -- but I fixed it anyway :) -- David C. Rankin, J.D.,P.E.

On 11/08/2019 06:04 AM, Werner Flamme wrote:

That reminds me of this behaviour I also had some years ago. I used powertop to adjust the "Power Saving" states of my USB interfaces.

I'd give powertop a try.

Thanks Werner, That was something I had not thought of. I checked and there isn't any power-saving being applied to the usb devices (they are listed 'bad'), but I was able to make the NMI watchdog 'good' :) -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org