Bug 25848

Summary: unetbootin gui is completely grayed out and cannot be used in any way
Product: Mageia Reporter: Kristoffer Grundström <lovaren>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED FIXED QA Contact:
Severity: major    
Priority: Normal CC: geiger.david68210
Version: Cauldron   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: unetbootin CVE:
Status comment:
Attachments: Here's the info from the terminal when trying to open Unetbootin
What Unetbootin window looks like now

Description Kristoffer Grundström 2019-12-09 05:21:36 CET
Description of problem: I just installed unetbootin in Cauldron and got no errors during the installation, but as soon as I ran it from Program -> Tools ->System tools I only see a gray gui after giving the root password when Unetbootin window appears.

Version-Release number of selected component (if applicable): 661-2

How reproducible: All the time.

Steps to Reproduce:
1. Install Unetbootin.
2. Open Program menu -> Tools -> System tools and click on Unetbootin.
3. Give the root password when asked.
4. When the window of Unetbootin appears it's completely grayed out making it unusable.
Comment 1 Kristoffer Grundström 2019-12-09 05:23:10 CET
Created attachment 11394 [details]
Here's the info from the terminal when trying to open Unetbootin
Comment 2 Kristoffer Grundström 2019-12-09 05:24:54 CET
Created attachment 11395 [details]
What Unetbootin window looks like now
Comment 3 David GEIGER 2019-12-09 08:00:29 CET
I found this:

https://github.com/unetbootin/unetbootin/issues/194

CC: (none) => geiger.david68210

Comment 4 Kristoffer Grundström 2019-12-09 10:22:04 CET
Doing QT_X11_NO_MITSHM=1 unetbootin as root did he trick to get a working gui, however this has to be done everytime someone wants to use Unetbootin.

No chance to get it patched since this has been existing since the 26th of October last year?
Comment 5 David GEIGER 2019-12-09 13:36:29 CET
Please test with patched unetbootin-661-3.mga8
Comment 6 Kristoffer Grundström 2019-12-09 15:58:33 CET
Issue fixed with the new update. Closing as RESOLVED FIXED.

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Comment 7 David GEIGER 2019-12-09 16:09:13 CET
I just submitted latest upstream release 675, patched to port it to Qt5 and also without the previous hack (QT_X11_NO_MITSHM=1).

Let's see how it goes.