Bug#862870: [Pkg-libvirt-maintainers] Bug#862870: virt-viewer: doesn't seem to support XSendEvent
On Tue, Aug 01, 2017 at 12:34:59PM -0300, Guido Günther wrote: > [ cc'ing the gtk+ maintainers ] > > Hi, > On Fri, May 19, 2017 at 01:44:41PM +0200, Guido Günther wrote: > > On Wed, May 17, 2017 at 11:40:22PM +0200, Cyril Brulebois wrote: > > > Package: virt-viewer > > > Version: 1.0-1 > > > Severity: important > > > > > > [ x-d-cc: debian-b...@lists.debian.org ] > > > > > > Hi, > > > > > > Trying to use xdotool (either on the command line or through its xdo > > > python bindings) fails when sending key events to a specific virt-viewer > > > window. In this case, XSendEvent is used instead of XTEST, which doesn't > > > seem to be supported by virt-viewer, and anything sent this way is > > > ignored. > > > > Is there a simple one liner to test this? > > It seems this is not working for any gtk+3 application. While xterm > works as described in the xdotool manpage a simple: > > zenity --entry --title xsendeventtest & > xdotool type --window $(xdotool search "xsendeventtest") asdf > > does not work here either. Maybe the gtk+ maintainers have and idea how > to get this working? > > > > It's possible to raise the virt-viewer window and then send key events > > > without specifying a target window, which is implemented using XTEST in > > > xdotool, but that means messing up with the focus in the surrounding > > > window environment, which is highly impractical. > > > > > > I've also tried switching from default spice to vnc, still no luck. No > > > changes when I tried 5.0-1 from a sid chroot. > > > > > > Any help/suggestion welcome, it prevents me from automating d-i tests > > > with libvirt. (While they do run fine with a “bare” kvm.) > > Can you point me to the code you run the tests with? You should be able > to use the same mechanism with libvirt as without it. > Cheers, Have you considered using virsh send-key to inject the key presses inside the guest? Christophe signature.asc Description: PGP signature
Bug#843471: libspice-client-gtk-3.0-5: virt-manager segfaults in libspice-client-gtk
Hey, On Sun, Nov 06, 2016 at 10:41:16PM +0100, Kjö Hansi Glaz wrote: > Package: libspice-client-gtk-3.0-5 > Version: 0.33-3 > Severity: normal > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate *** > >* What led up to the situation? > > I opened a VM with spice display in virt-manager > >* What exactly did you do (or not do) that was effective (or > ineffective)? > > I didn't identify the precise action that trigger the crash, but it > happened to me several times today. > >* What was the outcome of this action? > > A segfault, with the following backtrace when running under gdb (sorry, I > didn't find a -dbg package for libspice-client): > > Thread 1 "python2" received signal SIGSEGV, Segmentation fault. > strlen () at ../sysdeps/x86_64/strlen.S:106 > 106 ../sysdeps/x86_64/strlen.S: Aucun fichier ou dossier de ce type. > (gdb) > (gdb) bt > #0 0x76f7a496 in strlen () at ../sysdeps/x86_64/strlen.S:106 > #1 0x7fffa90e270d in () at > /usr/lib/x86_64-linux-gnu/libspice-client-gtk-3.0.so.5 > #2 0x7fffe4aaa230 in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 > #3 0x7fffe4aa9579 in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 > #7 0x7633645b in instance 0x57b799a0 [GtkInvisible]> (instance=0x57b799a0, > detailed_signal=0x7fffe4b31ca4 "selection-received") at > ././gobject/gsignal.c:3487 > #4 0x7631af75 in g_closure_invoke (closure=0x56b2ac80, > return_value=return_value@entry=0x0, n_param_values=3, > param_values=param_values@entry=0x7fffcf10, > invocation_hint=invocation_hint@entry=0x7fffce90) at > ././gobject/gclosure.c:804 > #5 0x7632cf82 in signal_emit_unlocked_R > (node=node@entry=0x565fd800, detail=detail@entry=0, > instance=instance@entry=0x57b799a0, > emission_return=emission_return@entry=0x0, > instance_and_params=instance_and_params@entry=0x7fffcf10) > at ././gobject/gsignal.c:3635 > #6 0x76335bcc in g_signal_emit_valist > (instance=instance@entry=0x57b799a0, signal_id=signal_id@entry=81, > detail=detail@entry=0, var_args=var_args@entry=0x7fffd138) at > ././gobject/gsignal.c:3391 This is most likely the crash fixed by this upstream commit: https://cgit.freedesktop.org/spice/spice-gtk/commit/?id=03c016bea939ee4a26e90d80fa1012a993a8ea47 Christophe signature.asc Description: PGP signature
Bug#784291: libspice-client-glib-2.0-8: vinagre throws symbol lookup error in libspice-client-glib-2.0.so.8
Hey, On Tue, May 05, 2015 at 01:39:36AM +0100, SI wrote: Installed vinagre: foo@bar:~# apt-get install vinagre Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: libspice-client-glib-2.0-8 libspice-client-gtk-3.0-4 The following NEW packages will be installed: libspice-client-glib-2.0-8 libspice-client-gtk-3.0-4 vinagre 0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded. Need to get 1,473 kB of archives. After this operation, 6,004 kB of additional disk space will be used. Do you want to continue? [Y/n] y Run vinagre and this error is thrown and programs halts: foo@bar:~# vinagre vinagre: symbol lookup error: /usr/lib/x86_64-linux-gnu/libspice-client- glib-2.0.so.8: undefined symbol: libusb_hotplug_register_callback This symbol is used/not used depending on a compile-time check, see http://cgit.freedesktop.org/spice/spice-gtk/tree/gtk/usb-device-manager.c#n280 and http://cgit.freedesktop.org/spice/spice-gtk/tree/configure.ac#n395 It's used when libusb 1.0.16 is detected at build-time, and you have libusb 1.0.19 installed, so this should be fine. Maybe this libusb_hotplug_register_callback symbol is missing from the libusb you are using and the version check is not enough? Christophe pgpRwmyv1t5DE.pgp Description: PGP signature
Bug#704229: [Spice-devel] spice-client: -w password (on the command line) is a security risk
On Sun, Apr 07, 2013 at 09:05:34PM -0500, Rob Browning wrote: (If possible, please preserve the 704229-forwarded address in any replies.) I reported the following bug to the Debian bug tracker, but realized it should probably just be forwarded upstream. Rob Browning r...@defaultvalue.org writes: Package: spice-client Version: 0.11.0-1 I think the spice client should probably support some other way of specifying the password since putting it on the command line makes it visible to any other users on the system. A reasonable alternative might be --password-file foo. (cf. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704229) The recommended client these days is remote-viewer which does not allow passing the password on the command line, so this is less of an issue Christophe pgpWWcE2zJp9z.pgp Description: PGP signature
Bug#354519: rhythmbox: miss duration for vbr mp3
Le lundi 27 février 2006 à 02:14 +0100, gpe92 a écrit : Package: rhythmbox Version: 0.9.3.1-1 Severity: important There is a problem with mp3 recording with lame in vbr mode. Rhythmbox considere them as 32kbps and does't display the good duration. Did you use the command-line lame tool to encode those mp3s, or sound-juicer with the gstreamer lame plugin? The latter is known not to put the correct header at the beginning of the encoded file, which prevents rhythmbox from detectecting its length properly. Christophe
Bug#306917: shared-mime-info: new version cause wrong icon and menu on zip file in nautilus
2005/4/29, Stewart Jeacocke [EMAIL PROTECTED]: The magic for application/vnd.sun.xml.calc matches zip files (since OOo files are zip files). zip files were special-cased in gnome-vfs last time I looked to make it use the mime type returned by an extension match when a file is sniffed as a zip file. Christophe
