Bug 953231 - YaST software manager sometimes allows to install YMP, while another YaST soft.manager window is opened, and fails
Summary: YaST software manager sometimes allows to install YMP, while another YaST sof...
Status: RESOLVED WONTFIX
Alias: None
Product: openSUSE Distribution
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Leap 42.3
Hardware: x86-64 openSUSE 42.1
: P3 - Medium : Normal with 5 votes (vote)
Target Milestone: Leap 42.3
Assignee: YaST Team
QA Contact: Jiri Srain
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-11-02 20:57 UTC by Mindaugas Baranauskas
Modified: 2019-07-11 11:03 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
Screen (162.34 KB, image/png)
2015-11-02 20:57 UTC, Mindaugas Baranauskas
Details
yast2 logs (3.93 MB, application/x-compressed-tar)
2015-11-02 20:58 UTC, Mindaugas Baranauskas
Details
additional yast2 logs (3.99 MB, application/x-compressed-tar)
2015-11-02 21:08 UTC, Mindaugas Baranauskas
Details
y2logs in oS Leap 42.3beta (992.39 KB, application/x-compressed-tar)
2017-06-15 08:13 UTC, Mindaugas Baranauskas
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mindaugas Baranauskas 2015-11-02 20:57:34 UTC
Created attachment 654275 [details]
Screen

I tryed to install packages via 1-click install (YMP file), but I forgot about earler opened YaST software manager dialog.
1-click installed failed to add repositories and exited.
Next, I selected to install 'mlocate' package via 1-click YMP file, that for sure exist in stardart repository. After about minute waiting appears orange dialog:

UI Syntax Error
Out of memory
Check the log file!

YaST software manager shoud normally _always_ detect, if anothar instance is active.
Comment 1 Mindaugas Baranauskas 2015-11-02 20:58:56 UTC
Created attachment 654276 [details]
yast2 logs
Comment 2 Mindaugas Baranauskas 2015-11-02 21:08:49 UTC
Created attachment 654277 [details]
additional yast2 logs

The one 'YaST software manager' opened already I really can not start new 'YaST software manager', but I can open almost unlimited number of 'YaST software manager' instances via 1-click install!
Comment 3 Mindaugas Baranauskas 2015-11-02 21:09:53 UTC
I believe, this behavior may a bit explain https://bugzilla.opensuse.org/show_bug.cgi?id=953038 behavior also.
Comment 4 Mindaugas Baranauskas 2015-11-02 21:12:06 UTC
Excusez-moi, https://bugzilla.opensuse.org/show_bug.cgi?id=953231 maybe related, not comment#3
Comment 5 Mindaugas Baranauskas 2015-11-02 21:13:41 UTC
Excusez-moi again. I can not found related bug.
Comment 6 Ladislav Slezák 2015-11-04 10:04:39 UTC
It should use the PackageLock.Connect() [*] call to verify that the package lock can be obtained before using the package management.

[*] https://github.com/yast/yast-yast2/blob/dcdabd8ca29da6ebbd60d5ee7efd1daadff3e5da/library/packages/src/modules/PackageLock.rb#L135
Comment 7 Mindaugas Baranauskas 2017-06-15 08:13:45 UTC
Created attachment 729042 [details]
y2logs in oS Leap 42.3beta

I can reproduce in openSUSE Leap 42.3beta:
1. open software manager
2. open http://software.opensuse.org/ymp/openSUSE:Leap:42.3/standard/chromium.ymp
3. go through dialogs of 1-click installer

[Ruby] yast/wfm.rb:275 Internal error. Please report a bug report with logs.
Run save_y2logs to get complete logs.
Details: undefined method `reduce' for nil:NilClass
Caller:  /usr/share/YaST2/modules/PackageSlideShow.rb:135:in `ListSum'
Comment 8 Tomáš Chvátal 2019-07-11 11:03:51 UTC
This is automated batch bugzilla cleanup.

The openSUSE 42.3 changed to end-of-life (EOL [1]) status. As such
it is no longer maintained, which means that it will not receive any
further security or bug fix updates.
As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
openSUSE (At this moment openSUSE Leap 15.1, 15.0 and Tumbleweed) please
feel free to reopen this bug against that version (!you must update the
"Version" component in the bug fields, do not just reopen please), or
alternatively create a new ticket.

Thank you for reporting this bug and we are sorry it could not be fixed
during the lifetime of the release.

[1] https://en.opensuse.org/Lifetime