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

Bug#317622: marked as done (xserver-xfree86: X uses /root/bak_XF86/XF86Config-4_0 -- seriously.. )



Your message dated Fri, 22 Jul 2005 15:54:49 +0800
with message-id <523y87zjmwm.fsf@imfi.kspu.ru>
and subject line Bug#317622: xserver-xfree86: X uses /root/bak_XF86/XF86Config-4_0 -- seriously..
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 10 Jul 2005 07:49:25 +0000
>From jagginess@yahoo.ca Sun Jul 10 00:49:25 2005
Return-path: <jagginess@yahoo.ca>
Received: from web60115.mail.yahoo.com [209.73.178.98] 
	by spohr.debian.org with smtp (Exim 3.35 1 (Debian))
	id 1DrWZ3-0006jR-00; Sun, 10 Jul 2005 00:49:25 -0700
Received: (qmail 71919 invoked by uid 60001); 10 Jul 2005 07:48:54 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.ca;
  h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding;
  b=gt2DiEVISWw9+/s9mWcVrHLaYdKy+kUDn+dNtSNXD1y89Xztx5rz6q6FwfEg3MzICvrDs+3b+GgY4DfayIKN17WetdRt/gjKAX+wpyRR6shmihgVTFvF42vN2JVa5pJxWaw3jd1JwgTo7Nr1WZcaTr2zMcRCYoGVUnXtKNuNYGc=  ;
Message-ID: <[🔎] 20050710074854.71917.qmail@web60115.mail.yahoo.com>
Received: from [24.200.75.18] by web60115.mail.yahoo.com via HTTP; Sun, 10 Jul 2005 03:48:54 EDT
Date: Sun, 10 Jul 2005 03:48:54 -0400 (EDT)
From: - <jagginess@yahoo.ca>
Subject: xserver-xfree86: X uses /root/bak_XF86/XF86Config-4_0 -- seriously..           
To: submit@bugs.debian.org
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Delivered-To: submit@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
	autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 

Package: xserver-xfree86
Version: 2.6.0.8-1                                    
                                                      
      
Severity: critical                                    
                                               
                                                      
                                                      
      
*** Please type your report below this line ***   
(reportbug is currently broked, sorry for any
inconveniences this pasting may have..)               
                       
If this is the incorrect mail address I apologize, if
it would have to be resend please, please tell me and
I'll try to send it again to the  more accurate
recipient. This is a real ugly bug that would
infuriate many newbies if they try, and possibly very
likely to do something like the following.. I've also
sent this to the package maintainer of gdm.
                           

/etc/init.d/gdm without /etc/X11/XF86Config-4* or
/etc/X11/XF86Config
files may run (and without -xf86config)
/root/bak_XF86/XF86Config-4_0

wtf? No kidding..

so I had to move my XF86Config-4_0 and XF86Config-4_1
file to
/var/otherdir and solved the problem.

I marked this critical because there must be many
infuriated newbies not
knowing about lsof and their backup XF86Config-4*
files in /root being
used instead--

/root/XF86Config-4_* files may be used if
/etc/X11/XF86Config
/etc/X11/XF86Config-4 exist-- but if these files of
/etc/X11 don't offer
a stable configuration..

reportbug is broken when trying to send a message but
xserver-xfree86 is of the latest and I checked with a
filter to see if anyone reported something like this--
I used the filter "root".. this really is a funny
bug..never believed this could happen..

wtf?! I was surprised too...hope this gets looked
into, many newbies may
be extremely infuriarted as wtf is going on..or if its
their system's
filesystem going corrupt and X sometimes work blah
blah..thanks for any feedback..it would
greatly be appreciated..


goobit


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

---------------------------------------
Received: (at 317622-done) by bugs.debian.org; 22 Jul 2005 07:55:26 +0000
>From ejka@imfi.kspu.ru Fri Jul 22 00:55:26 2005
Return-path: <ejka@imfi.kspu.ru>
Received: from uejikov.g-service.ru [84.22.141.217] 
	by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
	id 1DvsNS-0007I2-00; Fri, 22 Jul 2005 00:55:26 -0700
Received: by uejikov.g-service.ru (Postfix, from userid 40100)
	id 2E80F3807C; Fri, 22 Jul 2005 15:54:49 +0800 (KRAST)
To: 317622-done@bugs.debian.org
Subject: Re: Bug#317622: xserver-xfree86: X uses
 /root/bak_XF86/XF86Config-4_0 -- seriously..
From: Eugene Konev <ejka@imfi.kspu.ru>
Organization: The negative side of the core...
X-PGP-RSA-Key: 0x2D124C15
Date: Fri, 22 Jul 2005 15:54:49 +0800
In-Reply-To: <[🔎] 20050710074854.71917.qmail@web60115.mail.yahoo.com> (jagginess@yahoo.ca's
 message of "Sun, 10 Jul 2005 03:48:54 -0400 (EDT)")
Message-ID: <523y87zjmwm.fsf@imfi.kspu.ru>
User-Agent: Gnus/5.1007 (Gnus v5.10.7) Emacs/21.4 (gnu/linux)
References: <[🔎] 20050710074854.71917.qmail@web60115.mail.yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Delivered-To: 317622-done@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level: 
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
	autolearn=no version=2.60-bugs.debian.org_2005_01_02


Ok. According to the code, X can only read XF86Config from root's $HOME
and this behavior is _intended_ and _documented_ (see man
XF86Config). It definitely can't use /root/bak_XF86/XF86Config-4_0.

If you are able to reproduce reading /root/bak_XF86/XF86Config-4_0,
please reopen this bug and attach contents /var/log/XFree86.0.log to
your report.



Reply to: