[gentoo-user] KDE plasma upgrade heads up for possible problem

[gentoo-user] KDE plasma upgrade heads up for possible problem

[Dale]

Howdy,

I just did a KDE plasma upgrade to 5.15.  I ran into a slight problem
that may or may not affect others so I wanted to give a heads up just in
case.  Everything builds fine.  I had no compile or install failures. 
What I did run into tho was a missing or more likely crashed
kicker/panel/thingy that is at the bottom of my screen.  It's the thing
that has the clock, desktop switcher, clip board and the K menu as
well.  I never can remember what they call that this week.  Anyway, when
I logged in, it came up for just a second or two and then disappeared. 
Obviously, you can't switch desktops in the normal way but if you use
the ctrl and functions keys, it doesn't act or look like it normally
should since there doesn't appear to be any background at all.  Example,
I have Kpatience on desktop 6.  If I switch to it with the ctrl function
keys, I can play the game normally.  However, if I switch to what at
startup is a empty desktop, #5 for example, the game still shows but
doesn't work.  If I switch back to desktop 6, it works as it should
again.  Whatever it is, it doesn't redraw the screen when you switch if
you don't have something already running there.  Other programs behaved
in a similar way.  It makes it look like all desktops are on one desktop
yet switching still works.  It's plenty weird.  Also, there is no K menu
so you can't start any programs that doesn't open from a saved session
on login.  Trust me, if you run into this, you won't miss it.  Even if
you don't notice the panel thingy at the bottom missing, you will notice
the rest.  It gets in your face and yells loudly that something ain't
right.  lol

What little bit of error I found mentioned something about a missing
input.  To be honest tho, I'm not sure it was related to what I saw
happening.  None of the errors looked like a complete failure but more
as a informational type message.  Sort of like video drivers that have
the "--" or "II".  They show something didn't work as expected but it
found a way around it or works without it. 

I don't have enough info to file a bug.  The way I fixed it, I did a
emerge -e world.  It might be that a emerge -ek would fix it but to be
sure, I let it recompile everything.  It didn't quite finish when I
tried to login and it worked normally.  If I had a clue what package it
was that was causing this, I'd certainly file a bug but it could be any
number of packages.  I suspect it is a dependency myself.  Something
needed to be rebuilt but wasn't for some reason.

I hope no one runs into this but if you do, make sure you at least have
a back up GUI installed, even if it doesn't give you anything but the
basics, at least you have a GUI.  You may also want to make sure you
have time to deal with this just in case you do run into this problem. 
Having something so you can go back to 5.14 easily may work as well. 

Best of luck to all.  I hope no one else hits this.  It was plenty weird. 

Dale

:-)  :-)

Re: [gentoo-user] KDE plasma upgrade heads up for possible problem

[Michael Cook]

On 3/5/19 7:47 PM, Dale wrote:
> Howdy,
> 
> I just did a KDE plasma upgrade to 5.15.  I ran into a slight problem
> that may or may not affect others so I wanted to give a heads up just in
> case.  Everything builds fine.  I had no compile or install failures.
> What I did run into tho was a missing or more likely crashed
> kicker/panel/thingy that is at the bottom of my screen.  It's the thing
> that has the clock, desktop switcher, clip board and the K menu as
> well.  I never can remember what they call that this week.  Anyway, when
> I logged in, it came up for just a second or two and then disappeared.
> Obviously, you can't switch desktops in the normal way but if you use
> the ctrl and functions keys, it doesn't act or look like it normally
> should since there doesn't appear to be any background at all.  Example,
> I have Kpatience on desktop 6.  If I switch to it with the ctrl function
> keys, I can play the game normally.  However, if I switch to what at
> startup is a empty desktop, #5 for example, the game still shows but
> doesn't work.  If I switch back to desktop 6, it works as it should
> again.  Whatever it is, it doesn't redraw the screen when you switch if
> you don't have something already running there.  Other programs behaved
> in a similar way.  It makes it look like all desktops are on one desktop
> yet switching still works.  It's plenty weird.  Also, there is no K menu
> so you can't start any programs that doesn't open from a saved session
> on login.  Trust me, if you run into this, you won't miss it.  Even if
> you don't notice the panel thingy at the bottom missing, you will notice
> the rest.  It gets in your face and yells loudly that something ain't
> right.  lol
> 
> What little bit of error I found mentioned something about a missing
> input.  To be honest tho, I'm not sure it was related to what I saw
> happening.  None of the errors looked like a complete failure but more
> as a informational type message.  Sort of like video drivers that have
> the "--" or "II".  They show something didn't work as expected but it
> found a way around it or works without it.
> 
> I don't have enough info to file a bug.  The way I fixed it, I did a
> emerge -e world.  It might be that a emerge -ek would fix it but to be
> sure, I let it recompile everything.  It didn't quite finish when I
> tried to login and it worked normally.  If I had a clue what package it
> was that was causing this, I'd certainly file a bug but it could be any
> number of packages.  I suspect it is a dependency myself.  Something
> needed to be rebuilt but wasn't for some reason.
> 
> I hope no one runs into this but if you do, make sure you at least have
> a back up GUI installed, even if it doesn't give you anything but the
> basics, at least you have a GUI.  You may also want to make sure you
> have time to deal with this just in case you do run into this problem.
> Having something so you can go back to 5.14 easily may work as well.
> 
> Best of luck to all.  I hope no one else hits this.  It was plenty weird.
> 
> Dale
> 
> :-)  :-)
> 
> 
Doing a revdep-rebuild.sh found the issue for me. (Note the newer 
version of this script without .sh did not find the issue)

Re: [gentoo-user] KDE plasma upgrade heads up for possible problem

[Philip Webb]

190305 Michael Cook wrote:
> On 3/5/19 7:47 PM, Dale wrote:
>> I just did a KDE plasma upgrade to 5.15.  I ran into a slight problem
> > that may or may not affect others so I wanted to give a heads up
-- snip --
> Doing a revdep-rebuild.sh found the issue for me.
> Note the newer version of this script without .sh did not find the issue.

So what was the actual problem & how did you solve it ??
Don't just leave us in suspense (sigh).

-- 
========================,,============================================
SUPPORT     ___________//___,   Philip Webb
ELECTRIC   /] [] [] [] [] []|   Cities Centre, University of Toronto
TRANSIT    `-O----------O---'   purslowatchassdotutorontodotca

Re: [gentoo-user] KDE plasma upgrade heads up for possible problem

[Dale]

Michael Cook wrote:
> On 3/5/19 7:47 PM, Dale wrote:
>> Howdy,
>>
>> I just did a KDE plasma upgrade to 5.15.  I ran into a slight problem
>> that may or may not affect others so I wanted to give a heads up just in
>> case.  Everything builds fine.  I had no compile or install failures.
>> What I did run into tho was a missing or more likely crashed
>> kicker/panel/thingy that is at the bottom of my screen.  It's the thing
>> that has the clock, desktop switcher, clip board and the K menu as
>> well.  I never can remember what they call that this week.  Anyway, when
>> I logged in, it came up for just a second or two and then disappeared.
>> Obviously, you can't switch desktops in the normal way but if you use
>> the ctrl and functions keys, it doesn't act or look like it normally
>> should since there doesn't appear to be any background at all.  Example,
>> I have Kpatience on desktop 6.  If I switch to it with the ctrl function
>> keys, I can play the game normally.  However, if I switch to what at
>> startup is a empty desktop, #5 for example, the game still shows but
>> doesn't work.  If I switch back to desktop 6, it works as it should
>> again.  Whatever it is, it doesn't redraw the screen when you switch if
>> you don't have something already running there.  Other programs behaved
>> in a similar way.  It makes it look like all desktops are on one desktop
>> yet switching still works.  It's plenty weird.  Also, there is no K menu
>> so you can't start any programs that doesn't open from a saved session
>> on login.  Trust me, if you run into this, you won't miss it.  Even if
>> you don't notice the panel thingy at the bottom missing, you will notice
>> the rest.  It gets in your face and yells loudly that something ain't
>> right.  lol
>>
>> What little bit of error I found mentioned something about a missing
>> input.  To be honest tho, I'm not sure it was related to what I saw
>> happening.  None of the errors looked like a complete failure but more
>> as a informational type message.  Sort of like video drivers that have
>> the "--" or "II".  They show something didn't work as expected but it
>> found a way around it or works without it.
>>
>> I don't have enough info to file a bug.  The way I fixed it, I did a
>> emerge -e world.  It might be that a emerge -ek would fix it but to be
>> sure, I let it recompile everything.  It didn't quite finish when I
>> tried to login and it worked normally.  If I had a clue what package it
>> was that was causing this, I'd certainly file a bug but it could be any
>> number of packages.  I suspect it is a dependency myself.  Something
>> needed to be rebuilt but wasn't for some reason.
>>
>> I hope no one runs into this but if you do, make sure you at least have
>> a back up GUI installed, even if it doesn't give you anything but the
>> basics, at least you have a GUI.  You may also want to make sure you
>> have time to deal with this just in case you do run into this problem.
>> Having something so you can go back to 5.14 easily may work as well.
>>
>> Best of luck to all.  I hope no one else hits this.  It was plenty
>> weird.
>>
>> Dale
>>
>> :-)  :-)
>>
>>
> Doing a revdep-rebuild.sh found the issue for me. (Note the newer
> version of this script without .sh did not find the issue)
>
>

Dang, I forgot about that command.  I may could have used that and had
the info needed to file a bug report so that the ebuild could be
changed/updated.  That may prevent others from getting stuck.  I haven't
used that command in a long long time.  It's been years I would guess. 

Maybe that will help others if they run into this. 

Dale

:-)  :-) 

Re: [gentoo-user] KDE plasma upgrade heads up for possible problem

[Michael Cook]

On 3/5/19 8:34 PM, Philip Webb wrote:
> 190305 Michael Cook wrote:
>> On 3/5/19 7:47 PM, Dale wrote:
>>> I just did a KDE plasma upgrade to 5.15.  I ran into a slight problem
>>> that may or may not affect others so I wanted to give a heads up
> -- snip --
>> Doing a revdep-rebuild.sh found the issue for me.
>> Note the newer version of this script without .sh did not find the issue.
> 
> So what was the actual problem & how did you solve it ??
> Don't just leave us in suspense (sigh).
> 

/usr/lib64/qt5/qml/QtQuick/XmlListModel/libqmlxmllistmodelplugin.so 
(symbol 
_ZN3QV46Object12insertMemberEPNS_6StringEPKNS_8PropertyENS_18PropertyAttributesE 
version Qt_5_PRIVATE_API not defined in file libQt5Qml.so.5 with link 
time reference)


dev-qt/qtxmlpatterns was also updated, must have built/linked against 
old libs due to using --jobs

Re: [gentoo-user] KDE plasma upgrade heads up for possible problem

[Mick]

[-- Attachment #1: Type: text/plain, Size: 1285 bytes --]

On Wednesday, 6 March 2019 03:15:14 GMT Michael Cook wrote:
> On 3/5/19 8:34 PM, Philip Webb wrote:
> > 190305 Michael Cook wrote:
> >> On 3/5/19 7:47 PM, Dale wrote:
> >>> I just did a KDE plasma upgrade to 5.15.  I ran into a slight problem
> >>> that may or may not affect others so I wanted to give a heads up
> > 
> > -- snip --
> > 
> >> Doing a revdep-rebuild.sh found the issue for me.
> >> Note the newer version of this script without .sh did not find the issue.
> > 
> > So what was the actual problem & how did you solve it ??
> > Don't just leave us in suspense (sigh).
> 
> /usr/lib64/qt5/qml/QtQuick/XmlListModel/libqmlxmllistmodelplugin.so
> (symbol
> _ZN3QV46Object12insertMemberEPNS_6StringEPKNS_8PropertyENS_18PropertyAttribu
> tesE version Qt_5_PRIVATE_API not defined in file libQt5Qml.so.5 with link
> time reference)
> 
> 
> dev-qt/qtxmlpatterns was also updated, must have built/linked against
> old libs due to using --jobs

Did you run 'emerge -a -v @preserved-rebuild' before trying revdep-rebuild, or 
revdep-rebuild.sh?

To date I have not found, or cannot recall, an occasion where revdep-rebuild 
rebuilt anything following a run of @preserved-rebuild.  I have stopped 
running revdep-rebuild.sh for years now thinking it is redundant.

-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [gentoo-user] KDE plasma upgrade heads up for possible problem

[Dale]

Mick wrote:
> On Wednesday, 6 March 2019 03:15:14 GMT Michael Cook wrote:
>> On 3/5/19 8:34 PM, Philip Webb wrote:
>>> 190305 Michael Cook wrote:
>>>> On 3/5/19 7:47 PM, Dale wrote:
>>>>> I just did a KDE plasma upgrade to 5.15.  I ran into a slight problem
>>>>> that may or may not affect others so I wanted to give a heads up
>>> -- snip --
>>>
>>>> Doing a revdep-rebuild.sh found the issue for me.
>>>> Note the newer version of this script without .sh did not find the issue.
>>> So what was the actual problem & how did you solve it ??
>>> Don't just leave us in suspense (sigh).
>> /usr/lib64/qt5/qml/QtQuick/XmlListModel/libqmlxmllistmodelplugin.so
>> (symbol
>> _ZN3QV46Object12insertMemberEPNS_6StringEPKNS_8PropertyENS_18PropertyAttribu
>> tesE version Qt_5_PRIVATE_API not defined in file libQt5Qml.so.5 with link
>> time reference)
>>
>>
>> dev-qt/qtxmlpatterns was also updated, must have built/linked against
>> old libs due to using --jobs
> Did you run 'emerge -a -v @preserved-rebuild' before trying revdep-rebuild, or 
> revdep-rebuild.sh?
>
> To date I have not found, or cannot recall, an occasion where revdep-rebuild 
> rebuilt anything following a run of @preserved-rebuild.  I have stopped 
> running revdep-rebuild.sh for years now thinking it is redundant.
>


I was told to run preserved-rebuild and did.  It built several packages
fine but failed on a package called guile or something like that.  Even
now it won't build.  I'm hoping it will get a better ebuild when I do my
next sync.  Also, during the regular emerge, it rebuilt a lot of
packages.  It picked up on some but it seems it missed one at least. 

Like you, I have not ran revdep-rebuild in so long, I forgot all about
it.  I wish I had thought of it because I'd like to report the bug if I
had enough info about what actually got broken. 

Dale

:-)  :-) 

[gentoo-user] Re: KDE plasma upgrade heads up for possible problem

[Nikos Chantziaras]

On 06/03/2019 14:39, Mick wrote:
> To date I have not found, or cannot recall, an occasion where revdep-rebuild
> rebuilt anything following a run of @preserved-rebuild.  I have stopped
> running revdep-rebuild.sh for years now thinking it is redundant.

@preserved-rebuild is only able to detect cases where the actual library 
file (*.so) got deleted. If the file is still there but there's runtime 
linking issues, it's not gonna find them. revdep-rebuild does find them, 
but not all of them. revdep-rebuild.sh finds cases revdep-rebuild does not.

It seems that the safest option is to run "emerge -a @preserved-rebuild" 
first, then "revdep-rebuild -i -- -a" and finally "revdep-rebuild.sh -i 
-- -a". (The "-- -a" is just so emerge asks you before emerging anything.)