On Tue 24 Oct 2017 at 07:31:32 -0400, The Wanderer wrote:
> On 2017-10-24 at 01:40, Robert Arkiletian wrote:
>
> > On Mon, Oct 23, 2017 at 2:51 PM, The Wanderer wrote:
> >
> >> On 2017-10-23 at 16:21, Robert Arkiletian wrote:
> >>
> >>> Just tried this on a different box
On Tue, Oct 24, 2017 at 7:35 PM, Marc Shapiro wrote:
> On 10/24/2017 09:14 AM, David Wright wrote:
>>
>> On Tue 24 Oct 2017 at 08:29:50 (-0400), The Wanderer wrote:
>>>
>>> On 2017-10-24 at 08:15, Greg Wooledge wrote:
>>>
On Tue, Oct 24, 2017 at 07:31:32AM -0400, The
On 10/24/2017 09:14 AM, David Wright wrote:
On Tue 24 Oct 2017 at 08:29:50 (-0400), The Wanderer wrote:
On 2017-10-24 at 08:15, Greg Wooledge wrote:
On Tue, Oct 24, 2017 at 07:31:32AM -0400, The Wanderer wrote:
clear_console clears your console if this is possible. It looks in the
That
On 10/23/2017 10:40 PM, Robert Arkiletian wrote:
On Mon, Oct 23, 2017 at 2:51 PM, The Wanderer wrote:
On 2017-10-23 at 16:21, Robert Arkiletian wrote:
Just tried this on a different box running Fedora 25 (64) and it
works perfectly, no problem. So I think this is a
On Tue 24 Oct 2017 at 08:29:50 (-0400), The Wanderer wrote:
> On 2017-10-24 at 08:15, Greg Wooledge wrote:
>
> > On Tue, Oct 24, 2017 at 07:31:32AM -0400, The Wanderer wrote:
> >
> >>> clear_console clears your console if this is possible. It looks in the
> >
> >> That program is shipped as
On 2017-10-24 at 08:15, Greg Wooledge wrote:
> On Tue, Oct 24, 2017 at 07:31:32AM -0400, The Wanderer wrote:
>
>>> clear_console clears your console if this is possible. It looks in the
>
>> That program is shipped as part of bash, so it looks as if this might
>> actually be considered a bash
On Tue, Oct 24, 2017 at 07:31:32AM -0400, The Wanderer wrote:
> > clear_console clears your console if this is possible. It looks in the
> That program is shipped as part of bash, so it looks as if this might
> actually be considered a bash bug. I'd see about reporting it there, yes
> - either
On 2017-10-24 at 01:40, Robert Arkiletian wrote:
> On Mon, Oct 23, 2017 at 2:51 PM, The Wanderer wrote:
>
>> On 2017-10-23 at 16:21, Robert Arkiletian wrote:
>>
>>> Just tried this on a different box running Fedora 25 (64) and it
>>> works perfectly, no problem. So I think
On Mon, Oct 23, 2017 at 2:51 PM, The Wanderer wrote:
> On 2017-10-23 at 16:21, Robert Arkiletian wrote:
>
>> Just tried this on a different box running Fedora 25 (64) and it
>> works perfectly, no problem. So I think this is a Debian bug.
>> Although on Fedora I'm not
On 2017-10-23 at 16:21, Robert Arkiletian wrote:
> Just tried this on a different box running Fedora 25 (64) and it
> works perfectly, no problem. So I think this is a Debian bug.
> Although on Fedora I'm not starting the first X session with startx,
> I can start another X session on tty2 with
Just tried this on a different box running Fedora 25 (64) and it works
perfectly, no problem. So I think this is a Debian bug. Although on
Fedora I'm not starting the first X session with startx, I can start
another X session on tty2 with startx and switch to tty3, log in and
log out without
On Mon, Oct 23, 2017 at 9:32 AM, Brian wrote:
> On Sun 22 Oct 2017 at 09:45:08 -0700, Robert Arkiletian wrote:
>
>> More info. The crash does NOT occur if I log into and log out of the
>> root account on the second virtual terminal. Also here is journalctl
>> output
>
>
On Sun 22 Oct 2017 at 09:45:08 -0700, Robert Arkiletian wrote:
> More info. The crash does NOT occur if I log into and log out of the
> root account on the second virtual terminal. Also here is journalctl
> output
#858073?
--
Brian.
More info. The crash does NOT occur if I log into and log out of the
root account on the second virtual terminal. Also here is journalctl
output
Oct 22 09:33:10 up udev-acl.ck[4719]: g_slice_set_config: assertion
'sys_page_size == 0' failed
Oct 22 09:33:10 up login[3250]: pam_unix(login:session):
Ok got more detailed info on the crash. First some info
Debian Stretch 64 with Radeon Turks graphics card
Note: I'm running X without root priv. I just log into a virtual term
and run startx. The crash (of the first X session) specifically
happens (not when closing the second X session) but when
On Thu 19 Oct 2017 at 14:56:29 (-0700), Jimmy Johnson wrote:
> On 10/19/2017 01:01 PM, David Wright wrote:
> >On Thu 19 Oct 2017 at 08:35:55 (-0700), Jimmy Johnson wrote:
> >>On 10/18/2017 09:13 AM, Robert Arkiletian wrote:
> >>>Using Debian Stretch x86_64. I don't use a greeter like lightdm. I
>
On 10/19/2017 01:01 PM, David Wright wrote:
On Thu 19 Oct 2017 at 08:35:55 (-0700), Jimmy Johnson wrote:
On 10/18/2017 09:13 AM, Robert Arkiletian wrote:
Using Debian Stretch x86_64. I don't use a greeter like lightdm. I
just log in at the virtual terminal, then startx (xfce desktop). I
like
On Thu 19 Oct 2017 at 08:35:55 (-0700), Jimmy Johnson wrote:
> On 10/18/2017 09:13 AM, Robert Arkiletian wrote:
> >Using Debian Stretch x86_64. I don't use a greeter like lightdm. I
> >just log in at the virtual terminal, then startx (xfce desktop). I
> >like to use multiple accounts (running X)
On 10/18/2017 09:13 AM, Robert Arkiletian wrote:
Using Debian Stretch x86_64. I don't use a greeter like lightdm. I
just log in at the virtual terminal, then startx (xfce desktop). I
like to use multiple accounts (running X) at the same time on
different virtual terminals (eg. ctrl-alt-f1
On Thu, Oct 19, 2017 at 10:06:05AM +0200, Floris wrote:
> Maybe you can find more information in the log messages. /var/log/Xorg.x.log
> gives information about the X server. Or try journalctl to read all log
> messages.
The X log can either be in /var/log/Xorg.*.log or in
Op Wed, 18 Oct 2017 18:13:39 +0200 schreef Robert Arkiletian
:
Using Debian Stretch x86_64. I don't use a greeter like lightdm. I
just log in at the virtual terminal, then startx (xfce desktop). I
like to use multiple accounts (running X) at the same time on
different
Using Debian Stretch x86_64. I don't use a greeter like lightdm. I
just log in at the virtual terminal, then startx (xfce desktop). I
like to use multiple accounts (running X) at the same time on
different virtual terminals (eg. ctrl-alt-f1 ctrl-alt-f2)
All is fine until I exit (shutdown) one X
in
> jessie.
> In stretch, its screen was fubar as if an img with the wrong
> width was splashed to the graphic memory. Changing to lightdm looks
> better. However, X crashes after logging in.
>
> I tried reinstalling and reconfiguring a number of packages, to no avail.
>
. In stretch, its screen was fubar as if an img with the wrong
width was splashed to the graphic memory. Changing to lightdm looks
better. However, X crashes after logging in.
I tried reinstalling and reconfiguring a number of packages, to no avail.
I logged in on the tty and issued startx twice
Ed,
It seems somehow you do not have the kernel modesetting (KMS) module
loading during boot. https://wiki.debian.org/KernelModesetting
After you boot, check if the nouveau module has been loaded into the kernel
space. If not, add it to /etc/modules.
Hope this helps,
Antonio
On Wed, Oct 16,
Running testing, and using the nouveau driver for a GeForce 7150M / nForce 630M
GPU. X sporadically crashes to a black screen where things scroll by too fast
for me
to read. I’ve tried to examine kern.log and Xorg.0.log, as well as google
searches.
Xorg.0.log shows an error:
cat
Since installing the large upgrade earlier this week (which included the new
OS and xserver packages)
my x server crashes (and makes me log in again) after some undetermined
operation occurrs.
(I can cause this by starting VLC or emacs)
I am running Testing, with the nvidia driver installed, and
Hi
On Wed, Apr 13, 2011 at 17:40, S Scharf ss11...@gmail.com wrote:
I am running Testing, with the nvidia driver installed, and two screens with
xinerama ( a 30 and a 90 degree rotated 20)
First try the nv driver. And check /var/logs/X.0.log or something, if
it's an X error it should be there.
On 2011-04-13 16:40:38 GMT, S Scharf wrote:
Since installing the large upgrade earlier this week (which included the
new OS and xserver packages) my x server crashes ... I am running Testing ...
Any one know what to look for to diagnose this issue?
Unfortunately I do not, but you are not
On Apr 13, 1:50 pm, Nuno Magalhães nunomagalh...@eu.ipp.pt wrote:
Hi
On Wed, Apr 13, 2011 at 17:40, S Scharf ss11...@gmail.com wrote:
I am running Testing, with the nvidia driver installed, and two screens with
xinerama ( a 30 and a 90 degree rotated 20)
First try the nv driver. And check
2011/4/13 Nuno Magalhães nunomagalh...@eu.ipp.pt
Hi
On Wed, Apr 13, 2011 at 17:40, S Scharf ss11...@gmail.com wrote:
I am running Testing, with the nvidia driver installed, and two screens
with
xinerama ( a 30 and a 90 degree rotated 20)
First try the nv driver. And check
I have similar problem here!
I use testing with evdev, nvidia proprietary drivers, and multseat.
My system start, gdm are started too, but I couldn't log in because my
mouse and my kbd isn't work. I need to login by ssh and halt the
system.
I have another problem too: my system only start after
On Wed, 13 Apr 2011 16:28:02 -0300
Marcelo Laia marcelol...@gmail.com wrote:
I have another problem too: my system only start after a lots of
trying. The system crash after grub start and before udev populate the
/dev
Same problem here. After upgrading udev to version 167-1, every time
On Mon, Mar 24, 2008 at 08:43:26PM -0400, Hugh Lawson wrote:
I've been trying to install the nvidia driver. I managed to get it
working, but my solution is not entirely satisfactory, because it's
vulnerable to an update of the nvidia-glx-legacy package. I'll trace
through the problem, and
Owen Townend [EMAIL PROTECTED] writes:
Hugh wrote:
The init file /etc/init.d/nvidia-glx-legacy was causing the X crashes,
by fiddling with needed links and file locations in the libraries. I
fixed this by the following:
Owen wrote:
Are you using the legacy
drivers or are they simply
Andrei Popescu [EMAIL PROTECTED] writes:
As far as I know you are *not* supposed to have both, so you should
purge the package nvidia-glx-legacy. You might want to restore that file
first, otherwise dpkg will complain about a missing file.
Thanks Andrei,
I did dpkg --purge
Hugh Lawson wrote:
Since posting, I've done some more work.
nvidia-glx-legacy has been purged; now I have nvidia-glx.
AFAIK you don't need nvidia-glx if you are using the script from the
nvidia site. nvidia-glx is for the module in the repository.
Nevertheless, /etc/init.d/nvidia-glx
Wackojacko [EMAIL PROTECTED] writes:
Hugh Lawson wrote:
Since posting, I've done some more work.
nvidia-glx-legacy has been purged; now I have nvidia-glx.
Wacko wrote:
You are mixing the two methods of installing the the nvidia module.
1. Use the script from the nvidia site and nothing
. I did however
figure out what was causing the problem.
The init file /etc/init.d/nvidia-glx-legacy was causing the X crashes,
by fiddling with needed links and file locations in the libraries. I
fixed this by the following:
# cd /etc/init.d
# mv nvidia-glx-legacy XXnvidia-glx-legacy
How I
boot. I couldn't find any
documentation warning about this after much searching. I did however
figure out what was causing the problem.
The init file /etc/init.d/nvidia-glx-legacy was causing the X crashes,
by fiddling with needed links and file locations in the libraries. I
fixed
On Mon, Jan 29, 2007 at 05:45:21PM -0500, Normand wrote:
Since the last 2 weeks approximately, I'm experiencing crashes in
graphical display: I can move the mouse pointer but clicking on anything
Hi Normand,
Did this start from a particular time period (a week ago, or since 2
updates ago)?
Since the last 2 weeks approximately, I'm experiencing crashes in
graphical display: I can move the mouse pointer but clicking on anything
has no effect, or has a strange effect, e.g. clicking on an icon in the
toolbar will bring up a completely unrelated window. If I close X with
Hi,
I am having a problem with video replay on Linux, I am running testing
with 2.4.19. The problem is that when I attempt to run a video X crashes
and restarts, this occurs with GTV and xine. I attempted to delete the
.xine directory, and the xine bug report does not seem helpful
--- akintayo holder [EMAIL PROTECTED] wrote:
are a few error messages, but none that would explain why xine is
killing X, in fact it seems the other way around.
Try using another codec. From what I can tell from that, Xine hates it.
Are you using Xv, or Xshm ?
=
The Linux Weekend
On Tue, Mar 04, 2003 at 12:11:08PM +1100, Rob Weir wrote:
On Tue, Mar 04, 2003 at 12:35:12AM +0100, Miky J wrote:
[snip 904 lines]
Hmm, try comment out line in XF86Config-4 containing
LoadModule dri.
I hope that anyone else will know how to help you ...
OP: you do have a window
Here's the new log file i have, i only have two warnings but it doesn't work, i still don't understand why the system wants apm.Could this be because of the matrox drivers ? or because the system doesn't detect the matrox card nicely ?
Thanx
# lspci00:00.0 Host bridge: Advanced Micro Devices
On Tue, Mar 04, 2003 at 12:35:12AM +0100, Miky J wrote:
Here's the new log file i have, i only have two warnings but it doesn't work, i
still don't understand why the system wants apm.
Could this be because of the matrox drivers ? or because the system doesn't detect
the matrox card nicely
spare time.
i.a.uemlianin If I'm in X (Gnome) and I'm idle for a while (10
i.a.uemlianin mins?) X crashes.
I had a similar problem on my Satellite. It turned out that DPMS was
the culpret. My X would crash every 20 minutes precisely. This turns
out to be the exact value of the DPMS
Ivan Uemlianin wrote:
Dear All
I'm running Debian GNU/Linux 3.0 on an IBM Thinkpad A31p.
X is in VESA mode, as the Thinkpad has unsupported Radeon video.
If I'm in X (Gnome) and I'm idle for a while (10 mins?) X crashes.
The error messages seem to be to do with trying to run a screensaver
Dear All
I'm running Debian GNU/Linux 3.0 on an IBM Thinkpad A31p.
X is in VESA mode, as the Thinkpad has unsupported Radeon video.
If I'm in X (Gnome) and I'm idle for a while (10 mins?) X crashes. The
error messages seem to be to do with trying to run a screensaver. Now,
I have
I have Slink 2.1.
When I start X, either via XDM or via startx, switch to konsole, switch back
to X and in the same time move my mouse vigorously (or accidentaly) my X
crashes.
If I leave the mouse while switching to X for couple of seconds, everything is
alright.
I have ps/2 mouse
On Sat, Feb 12, 2000 at 03:48:58AM +0100, Marko Cehaja wrote:
I have Slink 2.1.
When I start X, either via XDM or via startx, switch to konsole, switch back
to X and in the same time move my mouse vigorously (or accidentaly) my X
crashes.
If I leave the mouse while switching to X
(or accidentaly) my X
crashes.
If I leave the mouse while switching to X for couple of seconds, everything
is
alright.
I have ps/2 mouse and it works fine. The crash comes when switching to X and
in the same time trying to move the mouse (which doesn't move on the screen
for couple of seconds
I'll try the upgrade. I had heard there was one on an ftp site (something like
ftp.mokole.com), but when I logged on there was a message that nothing would be
made available for download.
I tried the xf86config again last night, and set the mouse port to /dev/psaux.
That did the trick. But the
I have Debian 2.1. After installation the console works fine but X does not.
When I startx, I will get a teal screen at a very low resolution, with the
mouse pointing to the left. Then everything freezes. If I hit a key, I get a
beep. I must go to a virtual terminal to shutdown.
I have run
I have Debian 2.1. After installation the console works fine but X does not.
When I startx, I will get a teal screen at a very low resolution, with the
mouse pointing to the left. Then everything freezes. If I hit a key, I get a
beep. I must go to a virtual terminal to shutdown.
All other
Marko Loparic wrote:
Apparently X can't start my window manager (fvwm2) using startx. It quits
after showing the X screen for a second. Using xinit another window
manager is activated (I strange one, I can't tell what it is...)
The X messages shows no fatal errors, but the .xsession.errors
On 05-Feb-99 Marko Loparic wrote:
Hi,
Apparently X can't start my window manager (fvwm2) using startx. It quits
after showing the X screen for a second. Using xinit another window
manager is activated (I strange one, I can't tell what it is...)
The X messages shows no fatal errors, but
Hi,
Apparently X can't start my window manager (fvwm2) using startx. It quits
after showing the X screen for a second. Using xinit another window
manager is activated (I strange one, I can't tell what it is...)
The X messages shows no fatal errors, but the .xsession.errors says
something which
On Sun, 10 May 1998, Adam Keys wrote:
Kiyan Azarbar wrote:
Hi. I was wondering if anyone else had had this problem. It seems
really major. If I'm in console mode, then switch back to X with
alt-f7, and then move the mouse in anticipation of X showing up, it
very often crashes X. The
Hi. I was wondering if anyone else had had this problem. It seems
really major. If I'm in console mode, then switch back to X with
alt-f7, and then move the mouse in anticipation of X showing up, it
very often crashes X. The whole thing just comes down and xdm
restarts.
I've just
Hi. I was wondering if anyone else had had this problem. It seems
really major. If I'm in console mode, then switch back to X with
alt-f7, and then move the mouse in anticipation of X showing up, it
very often crashes X. The whole thing just comes down and xdm
restarts.
I don't know how else to
Kiyan Azarbar wrote:
Hi. I was wondering if anyone else had had this problem. It seems
really major. If I'm in console mode, then switch back to X with
alt-f7, and then move the mouse in anticipation of X showing up, it
very often crashes X. The whole thing just comes down and xdm
restarts.
Hi. I was wondering if anyone else had had this problem. It seems
really major. If I'm in console mode, then switch back to X with
alt-f7, and then move the mouse in anticipation of X showing up, it
very often crashes X. The whole thing just comes down and xdm
restarts.
I've just tried
Hi,
My X crashes quite often. It happens usually after I run netscape
communicator but I am not so sure that it's caused by that. Nothing
special is running usually, just few Xterms and when I try to switch
screens it just crashes and exits to bash prompt. I use afterstep window
manager. Does
Hi,
My X crashes quite often. It happens usually after I run netscape
communicator but I am not so sure that it's caused by that. Nothing
special is running usually, just few Xterms and when I try to switch
screens it just crashes and exits to bash prompt. I use afterstep window
manager
with 24bit 1280x1024 and SVGA server version 3.2A. The
exactly same things happened with the 3.2 server too.
Brian K Servis wrote:
Occasionally when I switch from a VC back to X(alt-f7) and try and use
the mouse immediately X crashes and exits.
I am using a Diamond Stealth 64 Trio64 w/2MB
Hi all,
Occasionally when I switch from a VC back to X(alt-f7) and try and use
the mouse immediately X crashes and exits. If I don't use the mouse
for a couple of seconds it does not crash. I am running xdm but have
had it happen when just starting X using xinit. I am running gpm on
the VC's
1280x1024 and SVGA server version 3.2A. The
exactly same things happened with the 3.2 server too.
My mouse is a cheap 3-button logitech model in ttyS0 (COM1) and I use gpm.
Brian K Servis wrote:
Occasionally when I switch from a VC back to X(alt-f7) and try and use
the mouse immediately X
69 matches
Mail list logo