[Pkg-tigervnc-devel] Processed (with 5 errors): Re: Bug#776746: gnome-session: GNOME crashes during a remote desktop access

Fri Mar 13 21:18:25 UTC 2015

Processing commands for control at bugs.debian.org:

> severity 776746 normal
Bug #776746 [gnome-session] gnome-session: "Oh no! Something has gone wrong" when X server lacks Composite extension
Severity set to 'normal' from 'serious'
> clone 776746 -2 -3 -4
Bug #776746 [gnome-session] gnome-session: "Oh no! Something has gone wrong" when X server lacks Composite extension
Bug 776746 cloned as bugs 780434-780436
> retitle 776746 gnome-session: "Oh no! Something has gone wrong" when used under Xvnc
Bug #776746 [gnome-session] gnome-session: "Oh no! Something has gone wrong" when X server lacks Composite extension
Changed Bug title to 'gnome-session: "Oh no! Something has gone wrong" when used under Xvnc' from 'gnome-session: "Oh no! Something has gone wrong" when X server lacks Composite extension'
> reassign -2 tightvncserver 1.3.9-6.5
Bug #780434 [gnome-session] gnome-session: "Oh no! Something has gone wrong" when X server lacks Composite extension
Bug reassigned from package 'gnome-session' to 'tightvncserver'.
No longer marked as found in versions gnome-session/3.14.0-2.
Ignoring request to alter fixed versions of bug #780434 to the same values previously set
Bug #780434 [tightvncserver] gnome-session: "Oh no! Something has gone wrong" when X server lacks Composite extension
Marked as found in versions tightvnc/1.3.9-6.5.
> retitle -2 tightvncserver: no support for Composite extension as required by GNOME 3, Compiz, etc.
Bug #780434 [tightvncserver] gnome-session: "Oh no! Something has gone wrong" when X server lacks Composite extension
Changed Bug title to 'tightvncserver: no support for Composite extension as required by GNOME 3, Compiz, etc.' from 'gnome-session: "Oh no! Something has gone wrong" when X server lacks Composite extension'
> reassign -3 vnc4server 4.1.1+X4.3.0-37.4
Bug #780435 [gnome-session] gnome-session: "Oh no! Something has gone wrong" when X server lacks Composite extension
Bug reassigned from package 'gnome-session' to 'vnc4server'.
No longer marked as found in versions gnome-session/3.14.0-2.
Ignoring request to alter fixed versions of bug #780435 to the same values previously set
Bug #780435 [vnc4server] gnome-session: "Oh no! Something has gone wrong" when X server lacks Composite extension
Marked as found in versions vnc4/4.1.1+X4.3.0-37.4.
> retitle -3 vnc4server: no support for Composite extension as required by GNOME 3, Compiz, etc.
Bug #780435 [vnc4server] gnome-session: "Oh no! Something has gone wrong" when X server lacks Composite extension
Changed Bug title to 'vnc4server: no support for Composite extension as required by GNOME 3, Compiz, etc.' from 'gnome-session: "Oh no! Something has gone wrong" when X server lacks Composite extension'
> severity -4 wishlist
Bug #780436 [gnome-session] gnome-session: "Oh no! Something has gone wrong" when X server lacks Composite extension
Severity set to 'wishlist' from 'normal'
> retitle -4 gnome-session: please give clearer GUI message for missing Xserver features
Bug #780436 [gnome-session] gnome-session: "Oh no! Something has gone wrong" when X server lacks Composite extension
Changed Bug title to 'gnome-session: please give clearer GUI message for missing Xserver features' from 'gnome-session: "Oh no! Something has gone wrong" when X server lacks Composite extension'
> block 776746 by -2 -3 650394
Bug #776746 [gnome-session] gnome-session: "Oh no! Something has gone wrong" when used under Xvnc
776746 was not blocked by any bugs.
776746 was not blocking any bugs.
Added blocking bug(s) of 776746: 650394, 654924, 780434, and 780435
> affects 776746 + xrdp
Bug #776746 [gnome-session] gnome-session: "Oh no! Something has gone wrong" when used under Xvnc
Added indication that 776746 affects xrdp
> On Fri, 13 Mar 2015 at 19:25:54 +0000, Simon McVittie wrote:
Unknown command or malformed arguments to command.
> > This is all very unfortunate, but I don't see any way it can change
Unknown command or malformed arguments to command.
> > for Debian 8, and I don't think it should be considered a release-critical
Unknown command or malformed arguments to command.
> > bug in GNOME.
Unknown command or malformed arguments to command.
> Niels in the release team doesn't think so either, so I'm downgrading
Unknown command or malformed arguments to command.
Too many unknown commands, stopping here.

Please contact me if you need assistance.
-- 
776746: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776746
780434: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780434
780435: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780435
780436: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780436
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems