Package: unetbootin
Version: 549-2
Severity: normal

Hi all,
 I have four Desktop environments inside my system although most of
the time am on GNOME with gdm3. The others are for backups or when
showing off GNU/Linux to people.

Anyways, I called unetbootin from the CLI I got and still do  these messages :-


$ unetbootin
 shirish@deb-home:~$ Qt: Session management error: None of the
authentication protocols specified are support

after doing my stuff with unetbootin when I close the window it does
not come back to the command prompt and I had o use the combinatin
CTRL+C to take control back from the terminal.

As told before I do have KDE which means I understand from where QT
is/was coming but no idea why it's saying that . Maybe another bug
that needs to be filed ?

Lemme know if there is any query or something you want me to do.

Thanx in advance.
-- System Information:
Debian Release: wheezy/sid
 APT prefers unstable
 APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'),
(1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages unetbootin depends on:
ii  libc6           2.13-18
ii  libgcc1         1:4.6.1-9
ii  libqt4-network  4:4.7.3-7
ii  libqtcore4      4:4.7.3-7
ii  libqtgui4       4:4.7.3-7
ii  libstdc++6      4.6.1-9
ii  mtools          4.0.12-1
ii  p7zip-full      9.20.1~dfsg.1-3
ii  syslinux        2:4.04+dfsg-3
ii  udev            172-1

Versions of packages unetbootin recommends:
ii  extlinux                 2:4.04+dfsg-3
ii  unetbootin-translations  549-2

unetbootin suggests no packages.

-- no debconf information

-- 
          Regards,
          Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
065C 6D79 A68C E7EA 52B3  8D70 950D 53FB 729A 8B17



--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to