Your message dated Wed, 03 Sep 2014 14:08:30 +0400
with message-id <[email protected]>
and subject line Re: Bug#760365: qemu-system-x86: Showing "Could not initialize 
SDL(No available video device)" since last upgrade
has caused the Debian Bug report #760365,
regarding qemu-system-x86: Showing "Could not initialize SDL(No available video 
device)" since last upgrade
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
760365: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760365
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: qemu-system-x86
Version: 2.1+dfsg-2
Severity: important

I've been running "qemu-system-x86_64 -display sdl [..]" for months without
problems. Now it shows an error

"Could not initialize SDL(No available video device) - exiting"

I'm hoping for a soon fix.



-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages qemu-system-x86 depends on:
ii  ipxe-qemu           1.0.0+git-20131111.c3d1e78-2
ii  libaio1             0.3.109-4
ii  libasound2          1.0.28-1
ii  libbluetooth3       5.21-3
ii  libbrlapi0.6        5.0-2+b1
ii  libc6               2.19-10
ii  libcurl3-gnutls     7.37.1-1
ii  libfdt1             1.4.0+dfsg-1
ii  libgcc1             1:4.9.1-4
ii  libglib2.0-0        2.40.0-5
ii  libgnutls-deb0-28   3.3.6-2
ii  libiscsi2           1.12.0-2
ii  libjpeg8            8d1-1
ii  libncurses5         5.9+20140712-2
ii  libpixman-1-0       0.32.6-3
ii  libpng12-0          1.2.50-2
ii  libpulse0           5.0-6
ii  librados2           0.80.5-1
ii  librbd1             0.80.5-1
ii  libsasl2-2          2.1.26.dfsg1-11
ii  libsdl1.2debian     1.2.15-10
ii  libseccomp2         2.1.1-1
ii  libspice-server1    0.12.5-1
ii  libssh2-1           1.4.3-3
ii  libtinfo5           5.9+20140712-2
ii  libusb-1.0-0        2:1.0.19-1
ii  libusbredirparser1  0.7-1
ii  libuuid1            2.20.1-5.8
ii  libvdeplug2         2.3.2-4
ii  libx11-6            2:1.6.2-3
ii  libxen-4.3          4.3.0-3+b1
ii  libxenstore3.0      4.4.0-2
ii  qemu-system-common  2.1+dfsg-2
ii  seabios             1.7.5-1
ii  zlib1g              1:1.2.8.dfsg-1

Versions of packages qemu-system-x86 recommends:
ii  qemu-utils  2.1+dfsg-2

Versions of packages qemu-system-x86 suggests:
ii  kmod     18-1
pn  ovmf     <none>
pn  samba    <none>
pn  sgabios  <none>
pn  vde2     <none>

-- no debconf information

--- End Message ---
--- Begin Message ---
03.09.2014 13:56, Sebastian Pipping wrote:
> # sudo xterm
> No protocol specified
> Warning: This program is an suid-root program or is being run by the root 
> user.
[...]

First, don't run qemu as root, it is not supposed to be run with superuser
privileges.

And second, if you want your X11 environment to be accessible across sudo,
configure sudo to pass $DISPLAY and $XAUTHORITY variables, so that X clients
will be able to connect to your X server.

This has nothing to do with qemu.  So closing this bugreport.

Thanks,

/mjt

--- End Message ---

Reply via email to