Summary: | =net-libs/gtk-vnc-0.5.2 - No screen updates. | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Lukas Elsner <bugs-gentoo> |
Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | bugs-gentoo, virtualization |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Lukas Elsner
2013-07-05 10:59:33 UTC
Which version of gtk-vnc is this? Can you also try earlier / later versions? Is this a regression? Did it work before? Can you try a different remote server? First of all, thanks trying to help out on this Problem. Since I didnt get any answer in gentoo forums on this, I assume that it also could a weird local Problem. But I really have no clue what It could be about. Is this a regression? Did it work before? Since I am always virtualizing with virt-manager, it was working fine for months. Then, there were some weeks, without booting any VM. Also there was a complete Hardware change (new Laptop, but without a whole reinstall) Can you try a different remote server? Tried several virtual machines through virt-viewer and some remote servers throug vinage. Same issue everywhere. Which version of gtk-vnc is this? le@w530 /lu $ eix gtk-vnc [I] net-libs/gtk-vnc Available versions: 0.5.0-r1 0.5.1 (~)0.5.2 {examples gtk3 +introspection pulseaudio python sasl vala PYTHON_TARGETS="python2_6 python2_7"} Installed versions: 0.5.2(04:24:48 AM 07/02/2013)(gtk3 introspection pulseaudio python -examples -sasl -vala PYTHON_TARGETS="python2_7 -python2_6") Homepage: https://live.gnome.org/gtk-vnc Description: VNC viewer widget for GTK Can you also try earlier / later versions? Later versions will be difficult! :D When masking 0.5.2, I also have to downgrade virt-viewer, and some other packages. I can try, but I didnt do, yet. Any more Infos, I can give? same problem with gtk-vnc-0.5.1 :( There is a 9999 version in the gnome overlay. Anyhow, assigned to the maintainers since I barely know this package. Thank you for the extra information. also tried 0.5.0-r1 without success. removed gtk3 useflag and merged vinagre 2.xx - no success added gnome overlay now and upgrading all packages. however, gtk-vnc-9999 seems to throw some errors while building. but this is another bug I think... Another hint...maybe... Spice connections with virt-viewer and vinagre behaving exactly the same as VNC connections! tried to get some debug output: le@w530 /lu $ spicy -h localhost -p 5900 --spice-debug [...] (spicy:19213): GSpice-DEBUG: /var/tmp/portage/net-misc/spice-gtk-0.20/work/spice-gtk-0.20/gtk/spice-channel.c:1194 display-2:0: Peer version: 2:2 (spicy:19213): GSpice-DEBUG: /var/tmp/portage/net-misc/spice-gtk-0.20/work/spice-gtk-0.20/gtk/spice-channel.c:1691 display-2:0: spice_channel_recv_link_msg: 2 caps (spicy:19213): GSpice-DEBUG: /var/tmp/portage/net-misc/spice-gtk-0.20/work/spice-gtk-0.20/gtk/spice-channel.c:1701 display-2:0: got common caps 0:0xB (spicy:19213): GSpice-DEBUG: /var/tmp/portage/net-misc/spice-gtk-0.20/work/spice-gtk-0.20/gtk/spice-channel.c:1707 display-2:0: got channel caps 0:0x12 (spicy:19213): GSpice-DEBUG: /var/tmp/portage/net-misc/spice-gtk-0.20/work/spice-gtk-0.20/gtk/spice-channel.c:2601 test cap 0 in 0xB: yes (spicy:19213): GSpice-DEBUG: /var/tmp/portage/net-misc/spice-gtk-0.20/work/spice-gtk-0.20/gtk/spice-channel.c:2601 test cap 1 in 0xB: yes (spicy:19213): GSpice-DEBUG: /var/tmp/portage/net-misc/spice-gtk-0.20/work/spice-gtk-0.20/gtk/spice-channel.c:2601 test cap 3 in 0xB: yes (spicy:19213): GSpice-DEBUG: /var/tmp/portage/net-misc/spice-gtk-0.20/work/spice-gtk-0.20/gtk/spice-channel.c:1736 display-2:0: use mini header: 1 (spicy:19213): GSpice-DEBUG: /var/tmp/portage/net-misc/spice-gtk-0.20/work/spice-gtk-0.20/gtk/spice-channel.c:1100 cursor-4:0: channel up, state 2 (spicy:19213): GSpice-DEBUG: /var/tmp/portage/net-misc/spice-gtk-0.20/work/spice-gtk-0.20/gtk/spice-channel.c:930 cursor-4:0: Closing the connection: spice_channel_read() - ret=0 (spicy:19213): GSpice-DEBUG: /var/tmp/portage/net-misc/spice-gtk-0.20/work/spice-gtk-0.20/gtk/spice-channel.c:2091 cursor-4:0: channel has error, breaking loop (spicy:19213): GSpice-DEBUG: /var/tmp/portage/net-misc/spice-gtk-0.20/work/spice-gtk-0.20/gtk/spice-channel.c:2345 cursor-4:0: Coroutine exit cursor-4:0 (spicy:19213): GSpice-DEBUG: /var/tmp/portage/net-misc/spice-gtk-0.20/work/spice-gtk-0.20/gtk/spice-channel.c:2137 cursor-4:0: Delayed unref channel 0x1b10e40 (spicy:19213): GSpice-DEBUG: /var/tmp/portage/net-misc/spice-gtk-0.20/work/spice-gtk-0.20/gtk/spice-channel.c:1100 display-2:0: channel up, state 2 (spicy:19213): GSpice-DEBUG: /var/tmp/portage/net-misc/spice-gtk-0.20/work/spice-gtk-0.20/gtk/channel-display.c:901 display-2:0: spice_display_channel_up: cache_size 83886080, glz_window_size 12582912 (bytes) (spicy:19213): GSpice-DEBUG: /var/tmp/portage/net-misc/spice-gtk-0.20/work/spice-gtk-0.20/gtk/spice-channel.c:913 display-2:0: Read error Error receiving data: Connection reset by peer (spicy:19213): GSpice-CRITICAL **: recv hdr: Connection reset by peer (spicy:19213): GSpice-DEBUG: /var/tmp/portage/net-misc/spice-gtk-0.20/work/spice-gtk-0.20/gtk/spice-channel.c:2118 got socket error: 25 (spicy:19213): GSpice-DEBUG: /var/tmp/portage/net-misc/spice-gtk-0.20/work/spice-gtk-0.20/gtk/spice-channel.c:2345 display-2:0: Coroutine exit display-2:0 (spicy:19213): GSpice-DEBUG: /var/tmp/portage/net-misc/spice-gtk-0.20/work/spice-gtk-0.20/gtk/spice-channel.c:2137 display-2:0: Delayed unref channel 0x1b14420 (spicy:19213): GSpice-DEBUG: /var/tmp/portage/net-misc/spice-gtk-0.20/work/spice-gtk-0.20/gtk/decode-glz.c:372 decode_header: 32x23, id 0, ref 0 (spicy:19213): GSpice-DEBUG: /var/tmp/portage/net-misc/spice-gtk-0.20/work/spice-gtk-0.20/gtk/decode-glz.c:372 decode_header: 32x23, id 1, ref 0 (spicy:19213): GSpice-DEBUG: /var/tmp/portage/net-misc/spice-gtk-0.20/work/spice-gtk-0.20/gtk/decode-glz.c:372 decode_header: 32x23, id 2, ref 0 (spicy:19213): GSpice-DEBUG: /var/tmp/portage/net-misc/spice-gtk-0.20/work/spice-gtk-0.20/gtk/decode-glz.c:372 decode_header: 32x23, id 3, ref 0 [...] And vinagre (in vnc mode) gives many of this: (vinagre:27102): gtk-vnc-DEBUG: /var/tmp/portage/net-libs/gtk-vnc-0.5.2/work/gtk-vnc-0.5.2/src/vncconnection.c Requesting framebuffer update at 0,0 size 720x1280, incremental 1 (vinagre:27102): gtk-vnc-DEBUG: /var/tmp/portage/net-libs/gtk-vnc-0.5.2/work/gtk-vnc-0.5.2/src/vncconnection.c Read error Error receiving data: Resource temporarily unavailable (vinagre:27102): gtk-vnc-DEBUG: /var/tmp/portage/net-libs/gtk-vnc-0.5.2/work/gtk-vnc-0.5.2/src/vncconnection.c FramebufferUpdate type=7 area (720x91) at location 0,91 (vinagre:27102): gtk-vnc-DEBUG: /var/tmp/portage/net-libs/gtk-vnc-0.5.2/work/gtk-vnc-0.5.2/src/vncconnection.c Read error Error receiving data: Resource temporarily unavailable (vinagre:27102): gtk-vnc-DEBUG: /var/tmp/portage/net-libs/gtk-vnc-0.5.2/work/gtk-vnc-0.5.2/src/vncconnection.c Read error Error receiving data: Resource temporarily unavailable (vinagre:27102): gtk-vnc-DEBUG: /var/tmp/portage/net-libs/gtk-vnc-0.5.2/work/gtk-vnc-0.5.2/src/vncconnection.c Read error Error receiving data: Resource temporarily unavailable (vinagre:27102): gtk-vnc-DEBUG: /var/tmp/portage/net-libs/gtk-vnc-0.5.2/work/gtk-vnc-0.5.2/src/vncconnection.c Read error Error receiving data: Resource temporarily unavailable (vinagre:27102): gtk-vnc-DEBUG: /var/tmp/portage/net-libs/gtk-vnc-0.5.2/work/gtk-vnc-0.5.2/src/vncconnection.c Read error Error receiving data: Resource temporarily unavailable (vinagre:27102): gtk-vnc-DEBUG: /var/tmp/portage/net-libs/gtk-vnc-0.5.2/work/gtk-vnc-0.5.2/src/vncconnection.c Read error Error receiving data: Resource temporarily unavailable (vinagre:27102): gtk-vnc-DEBUG: /var/tmp/portage/net-libs/gtk-vnc-0.5.2/work/gtk-vnc-0.5.2/src/vncconnection.c Notify update area (720x91) at location 0,91 I really need my virtual machines! Will spend a lot of beer for the right hint! :) I made a complete fresh installation from stage3. Problem is still there! :( removed some overlays (x11,sunrise,gnome), got the following downgrades and gtkmm was building fine. I think gnome-overlay is the faulty one here! (sorry for double posting, but this solved two problems at once! :D) Calculating dependencies... done! [nomerge ] mate-base/mate-file-manager-1.6.1-r1::mate-overlay USE="introspection -debug (-gtk3) -mate -xmp" [ebuild UD ] gnome-base/gvfs-1.14.2::gentoo [1.15.4::gnome] USE="afp archive bluetooth bluray cdda fuse gphoto2 gtk http udev udisks -avahi -doc -gdu -gnome-keyring -ios -samba -systemd (-gnome-online-accounts%) (-mtp%*)" 1,433 kB [ebuild N ] media-sound/pavucontrol-2.0 USE="nls" 0 kB [ebuild NS ] dev-cpp/gtkmm-3.6.0:3.0 [2.24.4:2.4] USE="X (-aqua) -doc -examples {-test} (-wayland)" 0 kB [ebuild UD ] x11-libs/gtk+-3.6.3-r2:3::gentoo [3.7.14:3::gnome] USE="X cups introspection (-aqua) -colord -debug (-egl) -examples (-packagekit) {-test} -vim-syntax (-wayland) -xinerama" 12,964 kB [nomerge ] media-sound/gmpc-11.8.16 USE="nls unique -xspf" [nomerge ] net-libs/libsoup-2.40.3:2.4 USE="introspection ssl -debug -samba {-test}" [ebuild UD ] net-libs/glib-networking-2.34.2::gentoo [2.35.9::gnome] USE="gnome libproxy ssl -smartcard {-test}" 339 kB [nomerge ] www-client/google-chrome-29.0.1547.18_alpha210974:unstable USE="plugins" LINGUAS="de -am -ar -bg -bn -ca -cs -da -el -en_GB -es -es_LA -et -fa -fi -fil -fr -gu -he -hi -hr -hu -id -it -ja -kn -ko -lt -lv -ml -mr -ms -nb -nl -pl -pt_BR -pt_PT -ro -ru -sk -sl -sr -sv -sw -ta -te -th -tr -uk -vi -zh_CN -zh_TW" [ebuild UD ] dev-libs/atk-2.6.0::gentoo [2.7.91::gnome] USE="introspection nls" 0 kB [ebuild UD ] x11-libs/cairo-1.12.14-r2::gentoo [1.12.14-r3::x11] USE="X glib opengl svg xcb (-aqua) -debug -directfb -doc (-drm) (-gallium) -legacy-drivers -openvg (-qt4) -static-libs (-gles2%) (-valgrind%)" 0 kB [ebuild UD ] dev-libs/glib-2.34.3:2::gentoo [2.35.8:2::gnome] USE="-debug (-fam) (-selinux) -static-libs -systemtap {-test} -utils -xattr" 0 kB [ebuild UD ] sys-devel/make-3.82-r4::gentoo [3.82-r5::gnome] USE="nls -static" 0 kB (In reply to lukas elsner from comment #10) > removed some overlays (x11,sunrise,gnome), got the following downgrades and > gtkmm was building fine. > > I think gnome-overlay is the faulty one here! > So removing gnome-overlay made this issue go away? I think so, but cannot confirm exactly! Are you still hitting this? (with updated tree) you mean with using gnome overlay? At first try only with main tree, if it's solved, would be nice to get the offending package from overlay (specially since now most of the packages should be newer in the main tree and, then, you should only get a few updated from overlay) I am very busy right now, but will try the next days if readding gnome-overlay will make some problems. I readded gnome overlay, had just a few updates and everything is working fine. So no problems so far... Will close for now then, thanks for feedback |