Processed: [bts-link] source package gdm3

Thu May 24 18:39:59 BST 2018

Processing commands for control at bugs.debian.org:

> #
> # bts-link upstream status pull for source package gdm3
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg00001.html
> #
> user debian-bts-link at lists.debian.org
Setting user to debian-bts-link at lists.debian.org (was debian-bts-link at lists.debian.org).
> # remote status report for #656092 (http://bugs.debian.org/656092)
> # Bug title: usability: should ask for password right away, if there is only one user
> #  * http://bugzilla.gnome.org/show_bug.cgi?id=637566
> #  * remote status changed: NEW -> RESOLVED
> #  * remote resolution changed: (?) -> OBSOLETE
> #  * closed upstream
> tags 656092 + fixed-upstream
Bug #656092 [gdm3] usability: should ask for password right away, if there is only one user
Added tag(s) fixed-upstream.
> usertags 656092 - status-NEW
Usertags were: status-NEW.
Usertags are now: .
> usertags 656092 + status-RESOLVED resolution-OBSOLETE
There were no usertags set.
Usertags are now: resolution-OBSOLETE status-RESOLVED.
> # remote status report for #658290 (http://bugs.debian.org/658290)
> # Bug title: gdm-simple-slave[31794]: WARNING: Failed to set slave bus name on parent: Message did not receive a reply (timeout by message bus)
> #  * http://bugzilla.gnome.org/show_bug.cgi?id=669250
> #  * remote status changed: NEEDINFO -> RESOLVED
> #  * remote resolution changed: (?) -> OBSOLETE
> #  * closed upstream
> tags 658290 + fixed-upstream
Bug #658290 [gdm3] gdm-simple-slave[31794]: WARNING: Failed to set slave bus name on parent: Message did not receive a reply (timeout by message bus)
Added tag(s) fixed-upstream.
> usertags 658290 - status-NEEDINFO
Usertags were: status-NEEDINFO.
Usertags are now: .
> usertags 658290 + status-RESOLVED resolution-OBSOLETE
There were no usertags set.
Usertags are now: status-RESOLVED resolution-OBSOLETE.
> # remote status report for #680020 (http://bugs.debian.org/680020)
> # Bug title: gdm3: time is incorrect after wake-up
> #  * http://bugzilla.gnome.org/show_bug.cgi?id=679317
> #  * remote status changed: NEW -> RESOLVED
> #  * remote resolution changed: (?) -> OBSOLETE
> #  * closed upstream
> tags 680020 + fixed-upstream
Bug #680020 [gdm3] gdm3: time is incorrect after wake-up
Added tag(s) fixed-upstream.
> usertags 680020 - status-NEW
Usertags were: status-NEW.
Usertags are now: .
> usertags 680020 + status-RESOLVED resolution-OBSOLETE
There were no usertags set.
Usertags are now: resolution-OBSOLETE status-RESOLVED.
> # remote status report for #721388 (http://bugs.debian.org/721388)
> # Bug title: gdm3: anyone can change the user's next session in a more-or-less hidden way
> #  * http://bugzilla.gnome.org/show_bug.cgi?id=707839
> #  * remote status changed: NEW -> RESOLVED
> #  * remote resolution changed: (?) -> OBSOLETE
> #  * closed upstream
> tags 721388 + fixed-upstream
Bug #721388 [gdm3] gdm3: anyone can change the user's next session in a more-or-less hidden way
Added tag(s) fixed-upstream.
> usertags 721388 - status-NEW
Usertags were: status-NEW.
Usertags are now: .
> usertags 721388 + status-RESOLVED resolution-OBSOLETE
There were no usertags set.
Usertags are now: resolution-OBSOLETE status-RESOLVED.
> # remote status report for #851974 (http://bugs.debian.org/851974)
> # Bug title: choice of "gnome classic" session sticks, and make it impossible to go back to default "gnome" session
> #  * http://bugzilla.gnome.org/show_bug.cgi?id=781064
> #  * remote status changed: NEW -> RESOLVED
> #  * remote resolution changed: (?) -> OBSOLETE
> #  * closed upstream
> tags 851974 + fixed-upstream
Bug #851974 [gdm3] choice of "gnome classic" session sticks, and make it impossible to go back to default "gnome" session
Added tag(s) fixed-upstream.
> usertags 851974 - status-NEW
Usertags were: status-NEW.
Usertags are now: .
> usertags 851974 + status-RESOLVED resolution-OBSOLETE
There were no usertags set.
Usertags are now: resolution-OBSOLETE status-RESOLVED.
> # remote status report for #883971 (http://bugs.debian.org/883971)
> # Bug title: gparted won't start on Wayland
> #  * http://bugzilla.gnome.org/show_bug.cgi?id=789867
> #  * remote status changed: NEW -> RESOLVED
> #  * remote resolution changed: (?) -> OBSOLETE
> #  * closed upstream
> tags 883971 + fixed-upstream
Bug #883971 [gdm3] gparted won't start on Wayland
Bug #880601 [gdm3] gdm fails to give wayland an Xauthority file, preventing running applications as root
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
> usertags 883971 - status-NEW
Usertags were: status-NEW.
Usertags are now: .
> usertags 883971 + status-RESOLVED resolution-OBSOLETE
There were no usertags set.
Usertags are now: status-RESOLVED resolution-OBSOLETE.
> # remote status report for #883971 (http://bugs.debian.org/883971)
> # Bug title: gparted won't start on Wayland
> #  * http://bugzilla.gnome.org/show_bug.cgi?id=789867
> #  * remote status changed: NEW -> RESOLVED
> #  * remote resolution changed: (?) -> OBSOLETE
> #  * closed upstream
> tags 883971 + fixed-upstream
Bug #883971 [gdm3] gparted won't start on Wayland
Bug #880601 [gdm3] gdm fails to give wayland an Xauthority file, preventing running applications as root
Ignoring request to alter tags of bug #883971 to the same tags previously set
Ignoring request to alter tags of bug #880601 to the same tags previously set
> usertags 883971 - status-NEW
Usertags were: status-RESOLVED resolution-OBSOLETE.
Usertags are now: status-RESOLVED resolution-OBSOLETE.
> usertags 883971 + status-RESOLVED resolution-OBSOLETE
Usertags were: resolution-OBSOLETE status-RESOLVED.
Usertags are now: resolution-OBSOLETE status-RESOLVED.
> # remote status report for #590534 (http://bugs.debian.org/590534)
> # Bug title: gdm3: changes xkb options
> #  * http://bugzilla.gnome.org/show_bug.cgi?id=640018
> #  * remote status changed: NEW -> RESOLVED
> #  * remote resolution changed: (?) -> OBSOLETE
> #  * closed upstream
> tags 590534 + fixed-upstream
Bug #590534 [gdm3] gdm3: changes xkb options
Added tag(s) fixed-upstream.
> usertags 590534 - status-NEW
Usertags were: status-NEW.
Usertags are now: .
> usertags 590534 + status-RESOLVED resolution-OBSOLETE
There were no usertags set.
Usertags are now: resolution-OBSOLETE status-RESOLVED.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
590534: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=590534
656092: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656092
658290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658290
680020: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680020
721388: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721388
851974: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851974
880601: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880601
883971: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883971
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems