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.