rosegarden/yoshimi issues Leap-15.4 upgrade

0 views
Skip to first unread message

bad sector

unread,
Jun 17, 2022, 4:20:18 PMJun 17
to
N.B. during upgrade, dependency check offered to replace many Leap-15.3 pacman packages with suse Leap-15.4 packages, offer accepted in view of recent discussion to the effect that (zypper) knows which packages SHOULD be from pacman.

------------------------------------------------------------------
vlc video play:"Codec not supported. VLC could not decode format h264 (H264 - MPEG-4 AVC (part 10))"
------------------------------------------------------------------
rosegarden (rg-21.06.1-bp154-1.51-x86_64 installed, NO dependency ussues!)
though software.opensuse.org says NO rosegarden for Leap-15.4
what IS "bp"?

# rosegarden
libGL error: MESA-LOADER: failed to open nouveau: /usr/lib64/dri/nouveau_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib64/dri, suffix _dri)
libGL error: failed to load driver: nouveau
Cannot lock down 86611866 byte memory area (Cannot allocate memory)
Cannot use real-time scheduling (RR/5)(1: Operation not permitted)
JackClient::AcquireSelfRealTime error
[AlsaDriver] setCurrentTimer(): WARNING: using system timer with only 250 Hz resolution!
[Composition] getTrackById( 0 ): WARNING: Track ID not found.
[Composition] Available track ids are:
[AlsaDriver] renameDevice(): WARNING: Cannot find device 1 in port map
Segmentation fault (core dumped)

Mesa-dri-nouveau installed:
# rosegarden
Cannot lock down 86611866 byte memory area (Cannot allocate memory)
Cannot use real-time scheduling (RR/5)(1: Operation not permitted)
JackClient::AcquireSelfRealTime error
[AlsaDriver] setCurrentTimer(): WARNING: using system timer with only 250 Hz resolution!
[Composition] getTrackById( 0 ): WARNING: Track ID not found.
[Composition] Available track ids are:
[AlsaDriver] renameDevice(): WARNING: Cannot find device 1 in port map
Segmentation fault (core dumped)
------------------------------------------------------------------
yoshimi-2.2.0-lp154.7.1.x86_64.rpm ..downloaded from software.opensuse.org & installed with dependency alert (or abort? really?)

# yoshimi
"yoshimi: error while loading shared libraries: libreadline.so.8: cannot open shared object file: No such file or directory"
------------------------------------------------------------------
many programs that had been instaklled under Leap-16.3 removed (had to be reinstalled under 15.4)
kwrite, seamonkey, gftp ..just to name these

Andrew

unread,
Jun 17, 2022, 4:34:58 PMJun 17
to
That should not have happened with Seamonkey, it certainly did not
happen with me.
Render unto Packman what which belongs to Packman - if Packman carries
packages then you should be getting them from there, section 13.2 of
https://opensuse-guide.org/codecs.php should help.
No idea about nouveau, I don't have any hardware with Nvidia video left
- both AMD and Intel try harder to keep Linux users happy.

--
This mail has been tested by https://RKIvirus.com/ and has been found to
contain Covid-19. Disinfect after reading.

Malcolm

unread,
Jun 17, 2022, 4:35:55 PMJun 17
to
Hi
The upgrade recommendation is to disable any OBS repos...
See: <https://en.opensuse.org/SDB:System_upgrade#Extra_repositories_handling>

--
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
Tumbleweed 20220616 | GNOME Shell 42.2 | 5.18.4-1-default
HP Z440 | Xeon E5-2690 V3 X24 @ 2.60GHz | AMD RX550/Nvidia Quadro T400
up 2:07, 2 users, load average: 0.50, 0.65, 0.46

bad sector

unread,
Jun 17, 2022, 5:29:57 PMJun 17
to
seamonkey may haver been a mistake on my part (but there are quite a few other, replace it with hplip which I must have). Seamonkey is actusally the best mozilla as far as I'm concerned.





bad sector

unread,
Jun 17, 2022, 5:37:37 PMJun 17
to
I don't understand why packages that are NOT in incompatibility conflict with 15.4 packages essential for the system upgrade should be removed (kwrite, gftp, hplip, some others).




Malcolm

unread,
Jun 17, 2022, 6:02:07 PMJun 17
to
On Fri, 17 Jun 2022 17:37:30 -0400
bad sector <forgetski@postit_INVALID_.gov> wrote:
<snip>
> >>
> > Hi
> > The upgrade recommendation is to disable any OBS repos...
> > See:
> > <https://en.opensuse.org/SDB:System_upgrade#Extra_repositories_handling>
> >
>
> I don't understand why packages that are NOT in incompatibility
> conflict with 15.4 packages essential for the system upgrade should
> be removed (kwrite, gftp, hplip, some others).
>
Hi
I suspect they may have been @System packages, installed manually,
installed from an OBS repo?

Adding some verbosity during the upgrade may glean more info, I always
use -vvv for up or dup.

--
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
Tumbleweed 20220616 | GNOME Shell 42.2 | 5.18.4-1-default
HP Z440 | Xeon E5-2690 V3 X24 @ 2.60GHz | AMD RX550/Nvidia Quadro T400
up 3:36, 2 users, load average: 0.17, 0.38, 0.39

bad sector

unread,
Jun 17, 2022, 7:03:53 PMJun 17
to
On 6/17/22 18:02, Malcolm wrote:
> On Fri, 17 Jun 2022 17:37:30 -0400
> bad sector <forgetski@postit_INVALID_.gov> wrote:
> <snip>
>>>>
>>> Hi
>>> The upgrade recommendation is to disable any OBS repos...
>>> See:
>>> <https://en.opensuse.org/SDB:System_upgrade#Extra_repositories_handling>
>>
>> I don't understand why packages that are NOT in incompatibility
>> conflict with 15.4 packages essential for the system upgrade should
>> be removed (kwrite, gftp, hplip, some others).
>>
> Hi
> I suspect they may have been @System packages, installed manually,
> installed from an OBS repo?

Can't say, other than the Suse repos I've enabled Nvidia (need it for google-earth!) and Pacman. On ocasion GNOME but that usually came with problems sooner or later so for gnome I now usually just download and install one at a time from disk (gftp, sylpheed, etc.)

> Adding some verbosity during the upgrade may glean more info, I always
> use -vvv for up or dup.

For Leap I've been using exclusively Yast (zypper for TW); just minutes ago I tried some of the above linked suggests, lo and behold some 30 *.15.3's got removed or replaced with *.15.4's (would have thought that upgrade would have seen to this).

Then I went back to yast and am now waiting for all pacman repo packages to be upgraded to those versions.

What I'd really like is to get this done:

https://tinyurl.com/4xtzhsm9

with ALL the 9 packages shown at the top of the page swinging like chopper-blades loaded at the same time in both Leap AND Tumbleweed.

bad sector

unread,
Jun 21, 2022, 11:21:47 PMJun 21
to
On 6/17/22 19:03, bad sector wrote:
> What I'd really like is to get this done:
>
> https://tinyurl.com/4xtzhsm9
>
> with ALL the 9 packages shown at the top of the page swinging like chopper-blades loaded at the same time in both Leap AND Tumbleweed.

Leap still can't handle yoshi

just saw a yoshi Leap-15.0 upgrade minutes ago, but
one of its depends is STILL impossible to satisfy




Carlos E. R.

unread,
Jul 14, 2022, 1:45:49 PMJul 14
to
On 17/06/2022 22.20, bad sector wrote:
> N.B. during upgrade, dependency check offered to replace many Leap-15.3 pacman packages with suse Leap-15.4 packages, offer accepted in view of recent discussion to the effect that (zypper) knows which packages SHOULD be from pacman.

I don't remember.

But you should have the pacman repo enabled (for the target
distribution) during the zypper dup procedure, and with a lower number
priority.

In that situation, zypper should know what to do.

--
Cheers,
Carlos E.R.

Andrew

unread,
Jul 14, 2022, 3:15:38 PMJul 14
to
As an aside, Leap 15.4 warns you that those priority numbers are now
ignored.

Carlos E. R.

unread,
Jul 17, 2022, 9:24:10 AMJul 17
to
On 14/07/2022 21.15, Andrew wrote:
> Carlos E. R. wrote:
>> On 17/06/2022 22.20, bad sector wrote:
>>> N.B. during upgrade, dependency check offered to replace many
>>> Leap-15.3 pacman packages with suse Leap-15.4 packages, offer
>>> accepted in view of recent discussion to the effect that (zypper)
>>> knows which packages SHOULD be from pacman.
>>
>> I don't remember.
>>
>> But you should have the pacman repo enabled (for the target
>> distribution) during the zypper dup procedure, and with a lower number
>> priority.
>>
>> In that situation, zypper should know what to do.
>>
>
> As an aside, Leap 15.4 warns you that those priority numbers are now
> ignored.
>

AFAIK, that warning has been there for some years, but it was not true.

--
Cheers,
Carlos E.R.

bad sector

unread,
Jul 20, 2022, 10:40:28 PMJul 20
to
see what mean?

There's FAAAAAAR too many rumors and urban legends
for a 'supposedly mature' distro. End users should
not have to muck with ANY of this shit, even repo
handling should be seamless and entirely transparent.
Anyway, I'm back to where I was, got packman essentials
as well as packman enabled, selected as to-be-used,
and using only Yast as far as Leap is concerned. I'll
use zypper in Tumbleweed, then revise everything once
the future of Leap gets cleared up.




Carlos E.R.

unread,
Aug 2, 2022, 2:35:18 PMAug 2
to
On 2022-07-21 04:40, bad sector wrote:
> On 7/17/22 09:24, Carlos E. R. wrote:
>> On 14/07/2022 21.15, Andrew wrote:
>>> Carlos E. R. wrote:
>>>> On 17/06/2022 22.20, bad sector wrote:
>>>>> N.B. during upgrade, dependency check offered to replace many Leap-15.3 pacman packages with suse Leap-15.4 packages, offer accepted in view of recent discussion to the effect that (zypper) knows which packages SHOULD be from pacman.
>>>>
>>>> I don't remember.
>>>>
>>>> But you should have the pacman repo enabled (for the target distribution) during the zypper dup procedure, and with a lower number priority.
>>>>
>>>> In that situation, zypper should know what to do.
>>>>
>>>
>>> As an aside, Leap 15.4 warns you that those priority numbers are now ignored.
>>>
>>
>> AFAIK, that warning has been there for some years, but it was not true.
>>

>
> see what mean?
>
> There's FAAAAAAR too many rumors and urban legends
> for a 'supposedly mature' distro.

It is not an urban legend, it is an actual error message from the
software that has been there for some years. The actual situation and
actual meaning is confusing.

> End users should
> not have to muck with ANY of this shit, even repo
> handling should be seamless and entirely transparent.
> Anyway, I'm back to where I was, got packman essentials
> as well as packman enabled, selected as to-be-used,
> and using only Yast as far as Leap is concerned. I'll
> use zypper in Tumbleweed, then revise everything once
> the future of Leap gets cleared up.
>
>
>
>


--
Cheers, Carlos.
Reply all
Reply to author
Forward
0 new messages