[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#608704: marked as done (release-notes: recommend to close any running X server?)



Your message dated Mon, 3 Jan 2011 22:43:57 +0100
with message-id <20110103214357.GR13280@glenfiddich.ikibiki.org>
and subject line Re: Bug#608704: release-notes: recommend to close any running X server?
has caused the Debian Bug report #608704,
regarding release-notes: recommend to close any running X server?
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 owner@bugs.debian.org
immediately.)


-- 
608704: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=608704
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release-notes
Severity: wishlist


Hello,

I want to ask, if it would make sense to advice the user, to
close any running X server when doing an dist-upgrade.

Pro: 
you would reduce the risk of getting an unaccessable system,
when during new startup of e.g. gdm an error occures and X
is not responding/is hanging and you cannot switch back to
virtual console.
(I did a test dist-upgrade some time ago, and I had exactly
this problem: when restarting gdm, the system hung up, keyboard
was not responding, I had no chance to switch to virtual console.
See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=604724)


Contra:
?
Maybe no cons. X sessions are not for use in this situation
anyway, because they are likely to be terminated.
And the upgrade process is to be performed from the virtual
console or ssh.



Greetings

Holger

-- 

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Created with Sylpheed 2.5.0
    under DEBIAN GNU/LINUX 5.0.0 - L e n n y
        Registered LinuxUser #311290 - http://counter.li.org/
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =





--- End Message ---
--- Begin Message ---
On Sun, Jan 02, 2011 at 04:54:06PM -0500, Hendrik Boom wrote:
> On Sun, Jan 02, 2011 at 09:49:26PM +0100, Holger Wansing wrote:
> > Package: release-notes
> > Severity: wishlist
> > 
> > I want to ask, if it would make sense to advice the user, to
> > close any running X server when doing an dist-upgrade.

Actually already advised:
http://www.debian.org/releases/squeeze/i386/release-notes/ch-upgrading.fr.html#upgrade-preparations

> > Pro: 
> > you would reduce the risk of getting an unaccessable system,
> > when during new startup of e.g. gdm an error occures and X
> > is not responding/is hanging and you cannot switch back to
> > virtual console.
> > (I did a test dist-upgrade some time ago, and I had exactly
> > this problem: when restarting gdm, the system hung up, keyboard
> > was not responding, I had no chance to switch to virtual console.
> > See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=604724)
> 
> I have this problem in squeeze even without doing any upgrade.  After 
> logging out from an X session that was started fro gdm, the system is 
> hung up as described.  Perhaps the real solution would be to fix gdm?  I 
> have no way to shut down X as recommended.  The only thing I can do is 
> to boot the system without X in the first place.  Of course, this is 
> already a squeeze system, so it may not be relevant to the 
> lenny->squeeze upgrade.
 

-- 
Simon Paillard


--- End Message ---

Reply to: