Your message dated Thu, 27 Feb 2025 16:31:27 +0000 with message-id <[email protected]> and subject line Bug#1095508: Removed package(s) from unstable has caused the Debian Bug report #711594, regarding vino: Vino does not refresh screen once it is connected 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.) -- 711594: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711594 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: vino Version: 3.4.2-1+b1 Severity: important Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these lines *** After updating several packages last week vino-server will not work properly anymore. It seems there is a problem with the combination of Vino and ATI drivers ( and one of the packages emntioned below). I have the fglrx packages from the repository installed. A search on the web suggested a problem with compiz-effects earlier, but I don't know how this relates to Gnome 3. Updates installed: libfs6 (2:1.0.4-1) to 2:1.0.4-1+deb7u1 libgl1-mesa-dri (8.0.5-4) to 8.0.5-4+deb7u1 libgl1-mesa-dri:i386 (8.0.5-4) to 8.0.5-4+deb7u1 libgl1-mesa-glx (8.0.5-4) to 8.0.5-4+deb7u1 libgl1-mesa-glx:i386 (8.0.5-4) to 8.0.5-4+deb7u1 libglapi-mesa (8.0.5-4) to 8.0.5-4+deb7u1 libglapi-mesa:i386 (8.0.5-4) to 8.0.5-4+deb7u1 libglu1-mesa (8.0.5-4) to 8.0.5-4+deb7u1 libglu1-mesa:i386 (8.0.5-4) to 8.0.5-4+deb7u1 libx11-6 (2:1.5.0-1) to 2:1.5.0-1+deb7u1 libx11-6:i386 (2:1.5.0-1) to 2:1.5.0-1+deb7u1 libx11-data (2:1.5.0-1) to 2:1.5.0-1+deb7u1 libx11-xcb1 (2:1.5.0-1) to 2:1.5.0-1+deb7u1 libx11-xcb1:i386 (2:1.5.0-1) to 2:1.5.0-1+deb7u1 libxcb-dri2-0 (1.8.1-2) to 1.8.1-2+deb7u1 libxcb-glx0 (1.8.1-2) to 1.8.1-2+deb7u1 libxcb-glx0:i386 (1.8.1-2) to 1.8.1-2+deb7u1 libxcb-render0 (1.8.1-2) to 1.8.1-2+deb7u1 libxcb-render0:i386 (1.8.1-2) to 1.8.1-2+deb7u1 libxcb-shape0 (1.8.1-2) to 1.8.1-2+deb7u1 libxcb-shm0 (1.8.1-2) to 1.8.1-2+deb7u1 libxcb1 (1.8.1-2) to 1.8.1-2+deb7u1 libxcb1:i386 (1.8.1-2) to 1.8.1-2+deb7u1 libxcursor1 (1:1.1.13-1) to 1:1.1.13-1+deb7u1 libxcursor1:i386 (1:1.1.13-1) to 1:1.1.13-1+deb7u1 libxext6 (2:1.3.1-2) to 2:1.3.1-2+deb7u1 libxext6:i386 (2:1.3.1-2) to 2:1.3.1-2+deb7u1 libxfixes3 (1:5.0-4) to 1:5.0-4+deb7u1 libxfixes3:i386 (1:5.0-4) to 1:5.0-4+deb7u1 libxi6 (2:1.6.1-1) to 2:1.6.1-1+deb7u1 libxi6:i386 (2:1.6.1-1) to 2:1.6.1-1+deb7u1 libxinerama1 (2:1.1.2-1) to 2:1.1.2-1+deb7u1 libxinerama1:i386 (2:1.1.2-1) to 2:1.1.2-1+deb7u1 libxp6:i386 (1:1.0.1-2) to 1:1.0.1-2+deb7u1 libxrandr2 (2:1.3.2-2) to 2:1.3.2-2+deb7u1 libxrandr2:i386 (2:1.3.2-2) to 2:1.3.2-2+deb7u1 libxrender1 (1:0.9.7-1) to 1:0.9.7-1+deb7u1 libxrender1:i386 (1:0.9.7-1) to 1:0.9.7-1+deb7u1 libxres1 (2:1.0.6-1) to 2:1.0.6-1+deb7u1 libxt6 (1:1.1.3-1) to 1:1.1.3-1+deb7u1 libxt6:i386 (1:1.1.3-1) to 1:1.1.3-1+deb7u1 libxtst6 (2:1.2.1-1) to 2:1.2.1-1+deb7u1 libxtst6:i386 (2:1.2.1-1) to 2:1.2.1-1+deb7u1 libxv1 (2:1.0.7-1) to 2:1.0.7-1+deb7u1 libxv1:i386 (2:1.0.7-1) to 2:1.0.7-1+deb7u1 libxvmc1 (2:1.0.7-1) to 2:1.0.7-1+deb7u2 libxxf86dga1 (2:1.1.3-2) to 2:1.1.3-2+deb7u1 libxxf86vm1 (1:1.1.2-1) to 1:1.1.2-1+deb7u1 libxxf86vm1:i386 (1:1.1.2-1) to 1:1.1.2-1+deb7u1 xserver-xorg-video-openchrome (1:0.2.906-2) to 1:0.2.906-2+deb7u1 Falling back to VESA and the Classic Gnome will allow for a remote connection. Removing Wheezy's fglrx package and installing the official recent AMD driver will render my computer completely useless (another bug concerning libGL.so.1 location) and is no option. -- System Information: Debian Release: 7.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=nl_NL.utf8, LC_CTYPE=nl_NL.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages vino depends on: ii dconf-gsettings-backend [gsettings-backend] 0.12.1-3 ii libavahi-client3 0.6.31-2 ii libavahi-common3 0.6.31-2 ii libavahi-glib1 0.6.31-2 ii libc6 2.13-38 ii libcairo2 1.12.2-3 ii libdbus-glib-1-2 0.100.2-1 ii libgcrypt11 1.5.0-5 ii libglib2.0-0 2.33.12+really2.32.4-5 ii libgnome-keyring0 3.4.1-1 ii libgnutls26 2.12.20-7 ii libgtk-3-0 3.4.2-6 ii libice6 2:1.0.8-2 ii libjpeg8 8d-1 ii libnotify4 0.7.5-1 ii libsm6 2:1.2.1-2 ii libsoup2.4-1 2.38.1-2 ii libtelepathy-glib0 0.18.2-2 ii libx11-6 2:1.5.0-1+deb7u1 ii libxdamage1 1:1.1.3-2 ii libxext6 2:1.3.1-2+deb7u1 ii libxfixes3 1:5.0-4+deb7u1 ii libxtst6 2:1.2.1-1+deb7u1 ii zlib1g 1:1.2.7.dfsg-13 Versions of packages vino recommends: ii gvfs 1.12.3-4 Versions of packages vino suggests: ii gnome-user-guide 3.4.2-1+build1 ii vinagre 3.4.2-2 -- no debconf information
--- End Message ---
--- Begin Message ---Version: 3.22.0-7+rm Dear submitter, as the package vino has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1095508 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing [email protected]. Debian distribution maintenance software pp. Paul Tagliamonte (the ftpmaster behind the curtain)
--- End Message ---
