On Tue, 06 Dec 2011 20:39:26 +0100, Sven Joachim wrote:
> On 2011-12-06 10:50 +0100, Shaun wrote:
>
>> On 05/12/2011 22:25, Sven Joachim wrote:
>>> For gnome-shell you need a 3D OpenGL driver, and in wheezy the nouveau
>>> 3D drivers are not installed by default yet. This has been changed¹
>>> i
On 2011-12-06 10:50 +0100, Shaun wrote:
> On 05/12/2011 22:25, Sven Joachim wrote:
>> For gnome-shell you need a 3D OpenGL driver, and in wheezy the nouveau
>> 3D drivers are not installed by default yet. This has been changed¹ in
>> unstable already, however.
>
> Is there a way to test this?
$
On 05/12/2011 22:25, Sven Joachim wrote:
> For gnome-shell you need a 3D OpenGL driver, and in wheezy the nouveau
> 3D drivers are not installed by default yet. This has been changed¹ in
> unstable already, however.
Is there a way to test this? Is glxgears enough to tell if a suitable 3D
OpenGL d
On 2011-12-05 22:31 +0100, rudu wrote:
> Le 05/12/2011 20:25, Andrei Popescu a écrit :
>> On Lu, 05 dec 11, 19:31:47, rudu wrote:
>>> Hello,
>>> After my last upgrade& reboot, my wheezy refused to fire up gdm3/kdm.
>>> All I have is a black console offering a login.
>>> I saw that nvidia was upgr
Le 05/12/2011 20:25, Andrei Popescu a écrit :
On Lu, 05 dec 11, 19:31:47, rudu wrote:
Hello,
After my last upgrade& reboot, my wheezy refused to fire up gdm3/kdm.
All I have is a black console offering a login.
I saw that nvidia was upgraded to a 290 something version so I
removed all the nvidi
On Lu, 05 dec 11, 19:31:47, rudu wrote:
> Hello,
> After my last upgrade & reboot, my wheezy refused to fire up gdm3/kdm.
> All I have is a black console offering a login.
> I saw that nvidia was upgraded to a 290 something version so I
> removed all the nvidia* packages to let nouveau take its pla
Hello,
After my last upgrade & reboot, my wheezy refused to fire up gdm3/kdm.
All I have is a black console offering a login.
I saw that nvidia was upgraded to a 290 something version so I removed
all the nvidia* packages to let nouveau take its place.
That changed nothing.
Here is some info abo
On 2010-10-26 05:05 +0200, Brian Sammon wrote:
>> As I explained in that bug report, it's an incompatibility between the
>> Squeeze kernel and Lenny userland. Unfortunately, there is no way to
>> express this in package conflicts to ensure that it does not occur on
>> partial upgrades.
>
> Okay,
On Lu, 25 oct 10, 23:05:56, Brian Sammon wrote:
> I don't think I have a custom kernel/udev/boot configuration. Is this
> problem
> going to happen to everyone who tries to run squeeze on an Inspiron 8500?
> Everyone who tries to run squeeze on a nvidia system?
But you are not running squeeze
> As I explained in that bug report, it's an incompatibility between the
> Squeeze kernel and Lenny userland. Unfortunately, there is no way to
> express this in package conflicts to ensure that it does not occur on
> partial upgrades.
Okay, so I'm clear:
You're saying the Lenny xserver-xorg-vide
On 2010-10-24 21:17 +0200, Brian Sammon wrote:
> I entered a bug that upgrading udev from lenny to unstable breaks X. (It
> also
> breaks with the squeeze version of udev )
> ( http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600551 )
>
> The bug was closed without any changes to the package, o
On Du, 24 oct 10, 15:17:50, Brian Sammon wrote:
> I entered a bug that upgrading udev from lenny to unstable breaks X. (It
> also
> breaks with the squeeze version of udev )
> ( http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600551 )
>
> The bug was closed without any changes to the package,
I entered a bug that upgrading udev from lenny to unstable breaks X. (It also
breaks with the squeeze version of udev )
( http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600551 )
The bug was closed without any changes to the package, or any other package.
While I've found a workaround, I'm con
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)
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) Failed to load module "pcida
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
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 looking kernel messages in the logs. I have included both
errors below, along wit
Perfect. Replaced the USB mouse with a old serial mouse. Thanks for
the tip, I was stuck.
--
Dan Hunt Saint Brieux Saskatchewan Canada
Dan R. Hunt wrote:
I installed Sarge on a HP Evectra.
http://images.google.ca/images?q=evectra
When I did this I used a Logitech USB / Optical Wheel Mouse.
Took the little fellow downstairs and changed the mouse to a Logitech
two button serial mouse, D-shaped 9 pin.
Been running:
dpkg-reconfigu
I installed Sarge on a HP Evectra.
http://images.google.ca/images?q=evectra
When I did this I used a Logitech USB / Optical Wheel Mouse.
Took the little fellow downstairs and changed the mouse to a Logitech
two button serial mouse, D-shaped 9 pin.
Been running:
dpkg-reconfigure xserver-xfree86 to
> 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
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
configuration. I did that and nothing changed.
Someone Suggested that I boot knoppix and copy
On Wed, Oct 22, 2003 at 07:33:22AM -0500, Kent West wrote:
> Robert William Hutton wrote:
>
> >Hi,
> >
> >Last night's update in unstable has killed my xserver. I'd normally be
> >able to work out what's going on, but nothing is showing up in my logs.
> >The symptoms of the problem are also diffe
Robert William Hutton wrote:
Hi,
Last night's update in unstable has killed my xserver. I'd normally be
able to work out what's going on, but nothing is showing up in my logs.
The symptoms of the problem are also different than the usual ones:
- The X server starts, I get the grey background, an
Hi,
Last night's update in unstable has killed my xserver. I'd normally be
able to work out what's going on, but nothing is showing up in my logs.
The symptoms of the problem are also different than the usual ones:
- The X server starts, I get the grey background, and the cross, which
is the d
dave mallery wrote:
> the only custom drivers i can find on the matrox site have to be compiled
> from source along with X and under a 2.4 kernel.
>
> is that the only way to get em??
There are binaries available. Depending on the model of card you have and/or
whether you want improved 3D you ma
dave mallery declaimed:
> On Fri, 5 Apr 2002, Paul Mackinney wrote:
>
> > Simon Hepburn declaimed:
> > > 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 el
On Fri, 5 Apr 2002, Paul Mackinney wrote:
> Simon Hepburn declaimed:
> > 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?
Simon Hepburn declaimed:
> 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
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
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. The problem
lines in /var/log/XFree86.0.log are
Symbol fbPictureInit from module /usr/X11R6/lib/modules/drivers/mga_drv.o\
is unresolved!
Symbol XAA_888_plus_PICT_a8_to
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
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 a similar
problem, but no solutions posted; henc
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
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!
- soumitri
This is a pre-release version of XFree86, and is not supported in any
way. Bugs may be reported to XFree
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
Hi,
I'm running potato on a laptop with a ATI Mobility M 4.
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.
Am I the only one experiencing this
I'll attach the /var/log/XFree86.log.
What I make from it i
--- "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
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 group I'll start with some simple info to see if there's anything
known or ob
"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
Hello list...
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 ?
Thanks alot.
Dominique
David Purton writes:
> On Fri, 27 Apr 2001 [EMAIL PROTECTED] wrote:
>
> >Hi all,
> >Yesterday I upgrade an intel box to the lastest release of
> > woody. Suddenly gdm ceases to work. Launching
> > /etc/init.d/gdm start
> >
> > nothing happens, except that the message
> >
On Fri, 27 Apr 2001 [EMAIL PROTECTED] wrote:
>Hi all,
>Yesterday I upgrade an intel box to the lastest release of
> woody. Suddenly gdm ceases to work. Launching
> /etc/init.d/gdm start
>
> nothing happens, except that the message
>
> Starting gdm appears
>
> Switching to the vt
Hi all,
Yesterday I upgrade an intel box to the lastest release of
woody. Suddenly gdm ceases to work. Launching
/etc/init.d/gdm start
nothing happens, except that the message
Starting gdm appears
Switching to the vt7, I see just a x cursor. Launching "ps aux" I see
that gdm is ind
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
EMAIL PROTECTED]
-]Sent: maandag 26 maart 2001 10:23
-]To: debian-user@lists.debian.org
-]Subject: X Broken After Upgrade
-]
-]
-]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 (r
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
the cursor menu won't appear when I press the mouse button. So I can't
do anything except move th
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
After the upgrade I get a series of:
var: allowed_users, value: rootonly.
var: nice_value, value: .
var: allowed_users, value: rootonly.
var: nice_value, value: .
var: allowed_users, value: rootonly.
var: nice_value, value: .
var: allowed_users, value: rootonly.
var: nice_value, value: .
var: allo
"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
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 has suspicious ownership, aborting.
_X11TransSocketUNIXConnect: Can't connect: er
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).
--
+-
Anyone else is experiencing this problem? Here are the messages that X
gives me at startup
_FontTransSocketUNIXConnect: Can't connect: errno = 2
failed to set default font path
'/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/75dpi/:unscaled,/usr/X11R6/lib/X11/fonts/100dpi/:unscaled,/usr/
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 c
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
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 slink or did I
do something wrong/not install some
80 matches
Mail list logo
