Bug 1246917 - unetbootin requests to be run as root but fails to display properly when run as root
Summary: unetbootin requests to be run as root but fails to display properly when run ...
Keywords:
Status: CLOSED DUPLICATE of bug 1229874
Alias: None
Product: Fedora
Classification: Fedora
Component: unetbootin
Version: 22
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Kalpa Welivitigoda
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-07-26 23:08 UTC by Alex Villacís Lasso
Modified: 2015-08-04 10:09 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-08-04 10:09:40 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Alex Villacís Lasso 2015-07-26 23:08:18 UTC
Description of problem:
When run as a normal user, unetbootin displays a message requesting to be run as root.

When run as root, unetbootin just displays a gray window. The console shows the following messages:
[alex@karlalex ~]$ su - -c '/usr/bin/unetbootin'
Contraseña: 
X Error: BadAccess (attempt to access private resource denied) 10
  Extension:    130 (MIT-SHM)
  Minor opcode: 1 (X_ShmAttach)
  Resource id:  0x125
X Error: BadShmSeg (invalid shared segment parameter) 128
  Extension:    130 (MIT-SHM)
  Minor opcode: 5 (X_ShmCreatePixmap)
  Resource id:  0x7d
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode: 62 (X_CopyArea)
  Resource id:  0x2000010
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode: 62 (X_CopyArea)
  Resource id:  0x2000010


Version-Release number of selected component (if applicable):
unetbootin-608-3.fc22.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Attempt to run /usr/bin/unetbootin as root
2.
3.

Actual results:
Blank window and X errors on console

Expected results:
Application widgets should display normally

Additional info:

When run anyway as an ordinary user, unetbootin performs all of the steps for creating the USB stick, except that it *silently* fails to run syslinux on it. The user is left with an unbootable stick with no warning at all.

Comment 1 Lubomir Rintel 2015-08-04 10:09:40 UTC

*** This bug has been marked as a duplicate of bug 1229874 ***


Note You need to log in before you can comment on or make changes to this bug.