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 running Fedora 25 (64) a
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 Wanderer 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 Wanderer wrote:
clear_console clears your console if this is possible. It looks in the
That pro
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 Debian bug.
Although on Fed
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 part
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 bu
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 in
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 this is a Debian bug.
>
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 starting the first X session
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 st
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 issue.
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
>
> #858073?
>
Ah! thanks Bria
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 to
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) at
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 ctrl-a
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
~/.local/share/xorg/Xorg
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 virtual terminals (eg. ct
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 s
22 matches
Mail list logo
