On 4/17/06, Jan Schledermann <[EMAIL PROTECTED]> wrote:
> You should try to read the hundreds of posts, in this news
> group, covering this particular topic, over the past 2-3 days!
> Solutions and explanations havew been given to most of the
> problems arising from the sid/dist-upgrade problems pe
WireSpot wrote:
> I'm running unstable. I've done an apt-get update and an apt-get
> dist-upgrade yesterday and didn't restart the computer until today. When I
> was hit by this problem (I start with `startx` from console):
>
> (EE) Failed to load module "bitmap" (module does not exist, 0)
> (EE)
On Sun, Mar 05, 2006 at 09:25:09PM -0500, Jeffrey Nowakowski wrote:
> I'm using testing, with no packages from unstable. I'm also using
> gdm.
>
> First, while upgrading a bunch of packages yesterday I got an error
> upgrading the x11-common package. Second, after rebooting I get some
> nasty lo
> on Wed, Nov 19, 2003 at 10:57:41AM -0800, Mark Healey
> ([EMAIL PROTECTED]) wrote:
>> My X won't work with the default installation. When I boot it tries
>> to start it and after several attempts I get a message telling me to
>> look at the log followed by one asking if I want to try automatic
>
on Wed, Nov 19, 2003 at 10:57:41AM -0800, Mark Healey ([EMAIL PROTECTED]) wrote:
> My X won't work with the default installation. When I boot it tries
> to start it and after several attempts I get a message telling me to
> look at the log followed by one asking if I want to try automatic
> config
Paul Mackinney wrote:
> After apt-get dist-updating to the latest version of sid last night
> (approx 2002-04-03 23:00 PST), I can't start X-windows.
> Anyone else having problems? Should I report a bug?
Well, is this is a matrox bug or an X bug ? I would post to debian-x
initially, rather than
On Mon, Nov 12, 2001 at 01:44:24PM -0500, Timothy Webster wrote:
> This brings to mind a much bigger question.
> Package configuration tool that using debian dependences to construct
> config files. It would be nice to have general package configuration
> tool that could read rules from the deb pac
Mariusz:
Thanks, this corrected the problem. Now it seems that a bug-report
should be filed. But which package is at fault? xfonts-base was not a
package that got upgraded. So, an update from one of yesterday's
changes caused the fonts directories to get wiped. an
update-fonts-alias (as s
You have a copy choices. Edit XF86Config-4 and commnet out the font line
or better still get the required font.
This brings to mind a much bigger question.
Package configuration tool that using debian dependences to construct
config files. It would be nice to have general package configuration
to
On Monday 12 Nov 2001 6:35 pm, fea wrote:
> Fatal server error:
> could not open default font 'fixed'
>
> Any help appreciated.
Try update-fonts-alias as root in the misc fonts directory
(/usr/X11R6/lib/X11/fonts/misc). That worked for me (or I
think that was what fixed it -- I was thrashing a
On Mon, 2001-11-12 at 19:35, fea wrote:
> I currently use Debian/Sid/Unstable primarily in order to use
> KDE 2.2.x (yes I know I deserve this, but it is so hard to resist).
> Most of the time things are stable. However, an upgrade today
> broke X for me. I have seen a couple of other folks with
On Sun, Nov 11, 2001 at 09:16:47AM +0530, Soumitri P S wrote:
>
> hi..
> ran apt-get update/apt-get upgrade and ended up with a broken x.
> i cant start gdm. "/var/log/gdm/:0.log" attached.
> sorry if i missed the original thread, but can anyone help!
That's not gdm's log, it's X's log. And yo
On Fri, Nov 09, 2001 at 05:58:10PM +0100, M.J.P.Benschop wrote:
> I'm running potato on a laptop with a ATI Mobility M 4.
Good.
> I had a perfectly fine working X whith kde and everything.
> After I did an apt-get update/apt-get upgrade earlier this week
> X got broken.
> I'll attach the /var/log/X
--- "Michael P. Soulier" <[EMAIL PROTECTED]>
wrote:
> On Sun, Oct 07, 2001 at 05:17:25AM -0700, Charles
> Baker wrote:
> >
> > > Change /etc/X11/Xsession.d from
> > > exec "$REALSTARTUP"
> > > to
> > > exec $REATSTARTUP
> > >
> > > It's a fairly common problem :-)
> > >
> >
> > This is strange
On Sun, 2001-10-07 at 06:58, Steve Cooper wrote:
> On Sun, Oct 07, 2001 at 12:10:45AM -0400, Duncan Findlay decreed:
> [snip]
> > Change /etc/X11/Xsession.d from
> > exec "$REALSTARTUP"
> > to
> > exec $REATSTARTUP
> >
> > It's a fairly common problem :-)
> >
> > --
> > Duncan Findlay
> ---end q
On Sun, Oct 07, 2001 at 12:10:45AM -0400, Duncan Findlay decreed:
[snip]
> Change /etc/X11/Xsession.d from
> exec "$REALSTARTUP"
> to
> exec $REATSTARTUP
>
> It's a fairly common problem :-)
>
> --
> Duncan Findlay
---end quoted text---
Worked like a charm (deleting the quotes). Thanks!!
Stev
On Sun, Oct 07, 2001 at 05:17:25AM -0700, Charles Baker wrote:
>
> > Change /etc/X11/Xsession.d from
> > exec "$REALSTARTUP"
> > to
> > exec $REATSTARTUP
> >
> > It's a fairly common problem :-)
> >
>
> This is strange. I have $REALSTARTUP and my X comes up fine.
He meant $REALSTARTUP, w/o
--- Duncan Findlay <[EMAIL PROTECTED]> wrote:
> On Sat, Oct 06, 2001 at 08:55:03PM +, Steve
> Cooper wrote:
> > Hello all,
> >
> > Having done a backup, I thought I'd "go for it"
> and accept all the
> > recent unstable updates. I had held off for a
> couple of weeks.
> >
> > Now X won't st
On Sun, Oct 07, 2001 at 12:48:27AM -0400, Vinod Kurup wrote:
> On Sun, Oct 07, 2001 at 12:10:45AM -0400, Duncan Findlay wrote:
> > Change /etc/X11/Xsession.d from
> > exec "$REALSTARTUP"
> > to
> > exec $REATSTARTUP
> >
> > It's a fairly common problem :-)
> >
>
> I think this was a typo
>
On Sun, Oct 07, 2001 at 12:10:45AM -0400, Duncan Findlay wrote:
> Change /etc/X11/Xsession.d from
> exec "$REALSTARTUP"
> to
> exec $REATSTARTUP
>
> It's a fairly common problem :-)
>
I think this was a typo
Change /etc/X11/Xsession.d/99xfree86-common_start from
exec "$REALSTARTUP"
to
exec
On Sun, Oct 07, 2001 at 12:10:45AM -0400, Duncan Findlay wrote:
>
> Change /etc/X11/Xsession.d from
> exec "$REALSTARTUP"
> to
> exec $REATSTARTUP
How do you figure?
tigger:/etc/X11/Xsession.d# grep REALSTARTUP *
50xfree86-common_determine-startup:REALSTARTUP=$STARTUPFILE
50xfree86-c
On Sat, Oct 06, 2001 at 08:55:03PM +, Steve Cooper wrote:
> Hello all,
>
> Having done a backup, I thought I'd "go for it" and accept all the
> recent unstable updates. I had held off for a couple of weeks.
>
> Now X won't start. Before dumping logs and other information spewages
> on the g
"Dominique" == Dominique Deleris <[EMAIL PROTECTED]> writes:
Dominique> Having upgraded my woody box this evening, I am not able to
Dominique> run X anymore. It will complain that it does not find the
Dominique> 'fixed' font. Anyone having the same problem ? What can I
Dominique> do ?
I had the s
On Wed, May 09, 2001 at 11:43:52PM +0200, Dominique Deleris wrote:
> Having upgraded my woody box this evening, I am not able to run X
> anymore. It will complain that it does not find the 'fixed'
> font. Anyone having the same problem ? What can I do ?
Do you still have the xfonts-base package i
Erik Steffl wrote:
>
>well, that means that X works perfectly. what you're missing is a
>window manager.
>
So I am.
>you can do a lot more. for example switch to another console and run
>some X program with -display :0 and switch back to X.
>
That is so neat! Thanks for the -display :0 trick.
David Densmore wrote:
>
> I used Apt to upgrade from Slink to Potato, now X doesn't work.
> The X server will start, the background appears and the mouse cursor
> will move around the screen (running twm), but no xterm appears and
well, that means that X works perfectly. what you're missing is
You've probably accidently upgraded some part of X or even removed some part
of X
Try running XF86Setup again, run it from the console to be sure and make
sure to use a NEW config file (asked at startup)
Greetings,
Joris
-]-Original Message-
-]From: David Densmore [mailto:[EMAIL PROTECT
I though it went o.k., so I didn't look at that. Today's upgrade fixed
it, so I expect that was the problem.
Now if I can only figure out how to get 1024x768 with XFree86 (it works
with XF86_SVGA, i.e., 3.3.6)
Thanks, Bob
On Tue, Nov 21, 2000 at 03:41:31PM -0500, Juergen Fiedler wrote:
> Did th
Did the upgrade work OK? Did you get any errors while
xserver-xfree86 was configured? A partially configured
XFree86 could be troublesome, I guess.
Try 'dpkg --configure xserver-xfree86'. If you get an
error message, try
'ln -s /usr/bin/X11/XFree86 /etc/X11/X'. The postinstall
script of xfree86
This appears to be related to the new Xwrapper.config file, but I can't
seem to find any reference to the syntax of this file. It currently
shows:
allowed_users=rootonly
nice_value=-10
On the other hand Xserver specifies Console. changelog.Debian.gz talks
a bit about Xwrapper.config, but I'm too
"James D. Freels" <[EMAIL PROTECTED]> writes:
> The fix as recommended by several folks is to
>
> "rm -rf /tmp/.X11-unix"
>
> I trust this information is being passed on to the developers without
> a formal bug report.
It would be far better to submit a bug report, actually.
-- John
The fix as recommended by several folks is to
"rm -rf /tmp/.X11-unix"
I trust this information is being passed on to the developers without
a formal bug report.
Thanks to all for responding!!
--
/--\
|James D. Freels, P.E._i, Ph.
[EMAIL PROTECTED] wrote:
>In the recent potato update of the X packages from
>3.3.6-7 to 3.3.6-8, it caused it to quit working. I will
>file a bug report if not fixed right away.
You might try e.g. bug #66225.
(Executive summary: "removing /tmp/.X11-unix allowed it to run again".)
--
Colin Wa
A bunch of us got this. The answer that worked for me was to
cd /tmp
rm -rf .X*
startx
Worked great. There has been discussion on the list as to what
is broken so hopefully the maintainers know about it now.
Robert
Thus spake James D. Freels ([EMAIL PROTECTED]):
>
> In the recent potato u
On Mon, Jun 26, 2000 at 09:35:08AM -0400, James D. Freels wrote:
>
> In the recent potato update of the X packages from
> 3.3.6-7 to 3.3.6-8, it caused it to quit working. I will
> file a bug report if not fixed right away. The error
> messages on startup are:
>
> X: server socket directory ha
When I was playing with xfs, I never could get local unix sockets to
work vis-a-vis "/unix:7100". However, it worked using tcp as
"tcp/localhost:7100". xfs slows down the system though, so I went back
to direct path specification (don't use true type fonts).
--
+-
ded: 7 Nov 1998 20:59:25 -
> To: debian-user@lists.debian.org
> Subject: Re: X broken?
> From: [EMAIL PROTECTED] (Ole J. Tetlie)
> Date sent:07 Nov 1998 21:53:07 +0100
> Forwarded by: debian-use
Date forwarded: 7 Nov 1998 20:59:25 -
To: debian-user@lists.debian.org
Subject:Re: X broken?
From: [EMAIL PROTECTED] (Ole J. Tetlie)
Date sent: 07 Nov 1998 21:53:07 +0100
Forwarded by: debian-user
*-Vaibhav Goel <[EMAIL PROTECTED]>
|
| Hello;
|
| I updated my hamm to slink yesterday. Everything seems to work
| fine except for X. I get the following error, when I type
| startx -- -bpp 32
|
| _X11TransConnect: Cant connect: errno=111
|
| My question is, that is X broken in the current sli
On Sat, 7 Nov 1998, Vaibhav Goel wrote:
> I updated my hamm to slink yesterday. Everything seems to work
> fine except for X. I get the following error, when I type
> startx -- -bpp 32
>
> _X11TransConnect: Cant connect: errno=111
I have a feeling your real error is above that. Maybe fonts, m
40 matches
Mail list logo
