[Bug 954143] New: Leap (KDE5) doesn't know what to do with an .rpm file. Chrome 64bit and Skype tested.
http://bugzilla.opensuse.org/show_bug.cgi?id=954143 Bug ID: 954143 Summary: Leap (KDE5) doesn't know what to do with an .rpm file. Chrome 64bit and Skype tested. Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Major Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers@suse.de Reporter: jedibeeftrix@ymail.com QA Contact: jsrain@suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:41.0) Gecko/20100101 Firefox/41.0 Build Identifier: Downloaded the rpm from google for 64bit Chrome and tried to click on it. Ark! Yast not even suggested, why? So, I add Yast as the preferred option for .rpm files and click on it again. Little Yast symbol pops up in a 'egg-timer' kind of way, few seconds later it disappears. Nothing. So i load up Yast, select import, and point it at the rpm. Error message. Is the whole problem because Leap is being clever and knows the 'opensuse' .rpm file is incompatible, or is this buggy behaviour? Same thing happens with Skype i586 .rpm from MS. Using 13.2 on my laptop i can open "apper software management" from the start menu. However, on Leap a start menu search for "apper" finds nothing. Likewise, "open with" on file properties cannot locate apper in system or utilities. Opening konsole in su and typing "run apper" gets nothing either... Reproducible: Always Steps to Reproduce: 1. download .rpm with "open with" (Yast) selected 2. open .rpm from download folder using Yast 3. open Yast, and "import" .rpm package from download folder 4. search for apper to use instead of Yast (nowhere to be found) Actual Results: nothing. system does not currently do anything with an .rpm file. Expected Results: .rpm opened with Yast, then proceeds to install using the Yast GUI Vanilla leap install working fine out the box, just can't modify it with new .rpm packages. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=954143
Martin Schlander
http://bugzilla.opensuse.org/show_bug.cgi?id=954143
http://bugzilla.opensuse.org/show_bug.cgi?id=954143#c3
--- Comment #3 from Martin Schlander
http://bugzilla.opensuse.org/show_bug.cgi?id=954143
http://bugzilla.opensuse.org/show_bug.cgi?id=954143#c4
Ignacio Taranto
http://bugzilla.opensuse.org/show_bug.cgi?id=954143
http://bugzilla.opensuse.org/show_bug.cgi?id=954143#c5
--- Comment #5 from Ignacio Taranto
http://bugzilla.opensuse.org/show_bug.cgi?id=954143
Antonio Larrosa
http://bugzilla.opensuse.org/show_bug.cgi?id=954143
Raul Malea
http://bugzilla.opensuse.org/show_bug.cgi?id=954143
Oliver Kurz
http://bugzilla.opensuse.org/show_bug.cgi?id=954143
Marcelo Junior
http://bugzilla.opensuse.org/show_bug.cgi?id=954143
http://bugzilla.opensuse.org/show_bug.cgi?id=954143#c6
--- Comment #6 from Marcelo Junior
http://bugzilla.opensuse.org/show_bug.cgi?id=954143
http://bugzilla.opensuse.org/show_bug.cgi?id=954143#c13
--- Comment #13 from Wolfgang Bauer
Ark is somehow still the default, but at least it's easily to work around by using "Open With -> Install/Remove Software".
This could probably be fixed by adding a "InitialPreference=x" line to the .desktop file. Ark has "InitialPreference=3", so x should be higher than 3. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=954143
http://bugzilla.opensuse.org/show_bug.cgi?id=954143#c14
--- Comment #14 from Marcelo Junior
http://bugzilla.opensuse.org/show_bug.cgi?id=954143
http://bugzilla.opensuse.org/show_bug.cgi?id=954143#c15
--- Comment #15 from Josef Reidinger
I requested this fix in 42.1 and included "InitialPreference=10" too. Worked pretty well, tested in a clean install.
Please do not create this direct maintenance fixes. We have infrastructure for it. Simple use git branch at github and after merge, it can be send as maintenance update. Otherwise it cause us trouble to keep it in sync with other maintenance updates. Keeping patches in git is much easier then in build service. 42.1 do not have own branch for packager, so one for SLE12 SP1 is used as documented in http://yastgithubio.readthedocs.io/en/latest/maintenance-branches/#maintenan... https://github.com/yast/yast-packager/tree/SLE-12-SP1 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=954143
http://bugzilla.opensuse.org/show_bug.cgi?id=954143#c16
--- Comment #16 from Marcelo Junior
Please do not create this direct maintenance fixes. We have infrastructure for it. Simple use git branch at github and after merge, it can be send as maintenance update. Otherwise it cause us trouble to keep it in sync with other maintenance updates. Keeping patches in git is much easier then in build service.
Thanks! Much better!
42.1 do not have own branch for packager, so one for SLE12 SP1 is used as documented in http://yastgithubio.readthedocs.io/en/latest/maintenance-branches/ #maintenance-branch-naming
Ok. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=954143
http://bugzilla.opensuse.org/show_bug.cgi?id=954143#c17
--- Comment #17 from Wolfgang Bauer
I requested this fix in 42.1 and included "InitialPreference=10" too.
The InitalPreference=10 still seems to be missing, could that be added too please? See bug#1001262. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=954143
http://bugzilla.opensuse.org/show_bug.cgi?id=954143#c18
--- Comment #18 from Wolfgang Bauer
(In reply to Marcelo Junior from comment #14)
I requested this fix in 42.1 and included "InitialPreference=10" too.
The InitalPreference=10 still seems to be missing, could that be added too please? See bug#1001262.
That is about 42.2. AFAICS the change has not been submitted to 42.1 at all (yet?). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=954143
http://bugzilla.opensuse.org/show_bug.cgi?id=954143#c20
--- Comment #20 from Wolfgang Bauer
the change was submitted but not approved yet.
Ah ok. Thank you for the information. (And thank you for taking care of this! ;-) ) I suppose we should mark bug#1001262 as duplicate then... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=954143
http://bugzilla.opensuse.org/show_bug.cgi?id=954143#c21
Wolfgang Bauer
http://bugzilla.opensuse.org/show_bug.cgi?id=954143
http://bugzilla.opensuse.org/show_bug.cgi?id=954143#c30
Pierre Bonamy
http://bugzilla.opensuse.org/show_bug.cgi?id=954143
http://bugzilla.opensuse.org/show_bug.cgi?id=954143#c31
Fabian Vogt
Given that, I'm in strong favour of applying the patch to avoid frustration for users knowing what they are doing.
AFAICS, as of today, a fresh install of released Leap 42.2 still prioritise Ark over Yast to open RPMs. Does this mean it is too late for 42.2?
I'm in favor of a maintenance update here, this was obviously forgotten. However, this is the YaST team's decision. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=954143
http://bugzilla.opensuse.org/show_bug.cgi?id=954143#c32
Fabian Vogt
We have reorganized the development branches to handle this kind of situations. I will adapt and re-target the pull request to go into Leap 42.2 ISO and to SLE-12-SP2 only as an maintenance update, so no need for SP2 release manager approval.
That change does not affect 42.1. As already said in comment#23, I would leave 42.1 out unless the maintenance team thinks different.
It looks like this got completely forgotten for the master branches, so it is missing in Leap 15.x and Tumbleweed. Please fix. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=954143
http://bugzilla.opensuse.org/show_bug.cgi?id=954143#c33
--- Comment #33 from Ancor Gonzalez Sosa
It looks like this got completely forgotten for the master branches, so it is missing in Leap 15.x and Tumbleweed. Please fix.
If fact it was kind of "put to rest" because it was controversial, both from the implementation point of view and about how advisable would be to offer that "single click" approach. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=954143
http://bugzilla.opensuse.org/show_bug.cgi?id=954143#c34
--- Comment #34 from Fabian Vogt
(In reply to Fabian Vogt from comment #32)
It looks like this got completely forgotten for the master branches, so it is missing in Leap 15.x and Tumbleweed. Please fix.
If fact it was kind of "put to rest" because it was controversial, both from the implementation point of view and about how advisable would be to offer that "single click" approach.
Looks like there is a misunderstanding. YaST opens RPMs already, but if other applications can also open RPMs, they get run instead. This applies to file archivers for example. This is obviously wrong so there shouldn't be any controversy around this. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=954143
http://bugzilla.opensuse.org/show_bug.cgi?id=954143#c35
--- Comment #35 from Fabian Vogt
(In reply to Ancor Gonzalez Sosa from comment #33)
(In reply to Fabian Vogt from comment #32)
It looks like this got completely forgotten for the master branches, so it is missing in Leap 15.x and Tumbleweed. Please fix.
If fact it was kind of "put to rest" because it was controversial, both from the implementation point of view and about how advisable would be to offer that "single click" approach.
Looks like there is a misunderstanding. YaST opens RPMs already, but if other applications can also open RPMs, they get run instead. This applies to file archivers for example.
This is obviously wrong so there shouldn't be any controversy around this.
Ping? -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com