I've finally sorted it out. The problem is Debian bug 870126.
Work around it by manually adding:
sessionoptional pam_keyinit.so force revoke
to /etc/pam.d/nodm
On 2021-11-01, Lucio Crusca wrote:
> On Nov 1, 2021 I wrote:
>> (actually a Raspbian, but I assume it's no different
>
> I've now tried installing a clean Debian 11 with Nodm in a virtual
> machine and I face exactly the same problem, so we can safely exclude
> any Raspbian-specific problems.
On Nov 1, 2021 I wrote:
(actually a Raspbian, but I assume it's no different
I've now tried installing a clean Debian 11 with Nodm in a virtual
machine and I face exactly the same problem, so we can safely exclude
any Raspbian-specific problems.
`
automatically at system startup. The system is a Debian GNU/Linux 10
(actually a Raspbian, but I assume it's no different to this end) that
uses NoDM [1] to start Xorg. It automatically logs the unprivileged user
in and it runs the `$HOME/.xsession` startup script.
I have the following script
On Sun, Nov 1, 2020, 11:48 AM Teemu Likonen wrote:
> * 2020-11-01 11:09:50+01, Anders Andersson wrote:
>
> > On Mon, Oct 26, 2020 at 5:43 PM Teemu Likonen wrote:
> >> From my backups I found an ~/.xsession-errors file of size 111
> >> megabytes. Probably I
* 2020-11-01 11:09:50+01, Anders Andersson wrote:
> On Mon, Oct 26, 2020 at 5:43 PM Teemu Likonen wrote:
>> From my backups I found an ~/.xsession-errors file of size 111
>> megabytes. Probably I deleted the file at that point and it started
>> grow again.
>
> Amateur
On Mon, Oct 26, 2020 at 5:43 PM Teemu Likonen wrote:
>
> It seems that ~/.xsession-errors file can still grow to infinity in
> size. Sometimes it grows really fast. This is nothing new: we have all
> seen it and talked about it. What do you do to maintain this file?
>
> -
code that referenced
> > "xsession-errors" or "ERRFILE" or any logfile except
> > "~/.cache/lxsession/LXDE/run.log".
>
> The relevant code apparently exists in the greeter app (or whatever it's
> called) I use (lightdm):
>
> src/session.c
On 2020-10-28, David wrote:
>
> Yes, I don't feel that I found the full answer. Because I spent a while
> using https://codesearch.debian.net/ to examine the source code
> of lxsession but I was unable to find any code that referenced
> "xsession-errors" or "
On Tue 27 Oct 2020 at 07:53:01 (-0400), Greg Wooledge wrote:
> On Tue, Oct 27, 2020 at 11:28:12AM +1100, David wrote:
> > On Tue, 27 Oct 2020 at 10:56, David Wright wrote:
> > > fuser -v "$j"
> > > [ $? -ne 0 ] && gzip "$j&
, Tixy wrote:
> > > > > On Mon, 2020-10-26 at 18:35 +0200, Teemu Likonen wrote:
> > > > > > It seems that ~/.xsession-errors file can still grow to infinity in
> > > > > > size. Sometimes it grows really fast. This is nothing new: we have
> &
:35 +0200, Teemu Likonen wrote:
>
> > > > > It seems that ~/.xsession-errors file can still grow to infinity in
> > > > > size. Sometimes it grows really fast. This is nothing new: we have all
> > > > > seen it and talked about it. What do you do to maintain this f
On Mi, 28 oct 20, 15:28:37, David wrote:
> On Wed, 28 Oct 2020 at 00:45, Andrei POPESCU wrote:
>
> > On my system the file is rotated (renamed to .xsession-errors.old), on
> > every login as far as I can tell.
>
> > Didn't find (yet) what is doing this (using lightdm
On Wed, 28 Oct 2020 at 00:45, Andrei POPESCU wrote:
> On Ma, 27 oct 20, 07:55:00, Greg Wooledge wrote:
> > On Mon, Oct 26, 2020 at 11:07:37PM +, Tixy wrote:
> > > On Mon, 2020-10-26 at 18:35 +0200, Teemu Likonen wrote:
> > > > It seems that ~/.xsession-errors f
gt;> (Why doesn't Debian have this automatically?)
I simply (like someone else mentioned on the list) truncate the file
periodically (actually, once every minute) using a crontab with a task like
this:
* * * * * echo "Cleared on $(date) by $USER cron" >
/home//.xsessi
tance, such logrotate policy
> would be denied by SELinux.
> That, and inviting running-as-root logrotate to cleanup user files opens
> all kinds of trouble.
I'm using KDE Plasma desktop and my .xsession-errors grows quite fast.
I'll probably write some rotation system for the f
On Ma, 27 oct 20, 07:55:00, Greg Wooledge wrote:
> On Mon, Oct 26, 2020 at 11:07:37PM +, Tixy wrote:
> > On Mon, 2020-10-26 at 18:35 +0200, Teemu Likonen wrote:
> > > It seems that ~/.xsession-errors file can still grow to infinity in
> > > size. Sometimes it grows r
On Mon, Oct 26, 2020 at 11:07:37PM +, Tixy wrote:
> On Mon, 2020-10-26 at 18:35 +0200, Teemu Likonen wrote:
> > It seems that ~/.xsession-errors file can still grow to infinity in
> > size. Sometimes it grows really fast. This is nothing new: we have all
> > seen it and
On Tue, Oct 27, 2020 at 11:28:12AM +1100, David wrote:
> On Tue, 27 Oct 2020 at 10:56, David Wright wrote:
> > fuser -v "$j"
> > [ $? -ne 0 ] && gzip "$j" && mv -i "$j.gz" "$HOME/.monitors/xsession/"
>
> &
On Tue, 27 Oct 2020 at 10:56, David Wright wrote:
> fuser -v "$j"
> [ $? -ne 0 ] && gzip "$j" && mv -i "$j.gz" "$HOME/.monitors/xsession/"
[...]
> (Script improvements always appreciated.)
Hi, you might be interes
On Mon 26 Oct 2020 at 18:35:45 (+0200), Teemu Likonen wrote:
> It seems that ~/.xsession-errors file can still grow to infinity in
> size. Sometimes it grows really fast. This is nothing new: we have all
> seen it and talked about it. What do you do to maintain this file?
>
>
Tixy writes:
> I guess as I never hibernate my laptop and turn it off every day, it
> never gets to an annoying size.
I haven't rebooted my desktop for three months. ls -l .xsession-errors
shows 468223. I consider that trivial and ignore it.
--
John Hasler
jhas...@newsguy.com
Elmwood, WI USA
On Mon, 2020-10-26 at 18:35 +0200, Teemu Likonen wrote:
> It seems that ~/.xsession-errors file can still grow to infinity in
> size. Sometimes it grows really fast. This is nothing new: we have all
> seen it and talked about it. What do you do to maintain this file?
Don't do anyt
Teemu Likonen writes:
It seems that ~/.xsession-errors file can still grow to infinity in
size. Sometimes it grows really fast. This is nothing new: we have all
seen it and talked about it. What do you do to maintain this file?
Until now, I had not seen it as a problem. But it is quite large
n 2005-02-27. There are ideas about
/etc/X11/Xsession script too. Debian developers certainly can fix this
if they want.
--
/// Teemu Likonen - .-.. https://www.iki.fi/tlikonen/
// OpenPGP: 4E1055DC84E9DFF613D78557719D69D324539450
signature.asc
Description: PGP signature
On 2020-10-26 18:35 +0200, Teemu Likonen wrote:
> It seems that ~/.xsession-errors file can still grow to infinity in
> size. Sometimes it grows really fast. This is nothing new: we have all
> seen it and talked about it. What do you do to maintain this file?
>
> - Do you just
Hi.
On Mon, Oct 26, 2020 at 06:35:45PM +0200, Teemu Likonen wrote:
> It seems that ~/.xsession-errors file can still grow to infinity in
> size. Sometimes it grows really fast. This is nothing new: we have all
> seen it and talked about it. What do you do to maintain
It seems that ~/.xsession-errors file can still grow to infinity in
size. Sometimes it grows really fast. This is nothing new: we have all
seen it and talked about it. What do you do to maintain this file?
- Do you just delete it when you happen to notice it's too big?
- Do you configure
Hi there,
I found the following in the ~/.xsession-errors :
dbus-update-activation-environment: warning: error sending to systemd:
org.freedesktop.DBus.Error.Spawn.ChildExited: Process
org.freedesktop.systemd1 exited with status 1
I was trying to search the net but no luck. Any suggestions
On 2018-04-06 18:56, Greg Wooledge wrote:
> On Fri, Apr 06, 2018 at 06:45:20PM +0200, Mikhail Morfikov wrote:
>> Basically even the standard "exec ..." in the /etc/X11/Xsession file (with
>> changed $ERRFILE) works fine, but I have to "cat" the FIFO device
On Fri, Apr 06, 2018 at 06:45:20PM +0200, Mikhail Morfikov wrote:
> Basically even the standard "exec ..." in the /etc/X11/Xsession file (with
> changed $ERRFILE) works fine, but I have to "cat" the FIFO device first
> (without
> using systemd). The same w
On 2018-04-06 17:53, Greg Wooledge wrote:
> On Fri, Apr 06, 2018 at 05:48:35PM +0200, Mikhail Morfikov wrote:
>> If I set $ERRFILE to the FIFO device, processing of the script will be
>> stopped
>> in the point where "exec ..." appears (before sourcing the
>> /etc/X11/Xsession.d/
>> dir).
>
>
On 2018-04-06 18:29, Don Armstrong wrote:
> On Fri, 06 Apr 2018, Mikhail Morfikov wrote:
>> Basically, all messages returned by X-applications are redirected to the
>> ~/.xsession-errors file.
> [...]
>> Unfortunately, the ~/.xsession-errors file grows in size, and a
On Fri, 06 Apr 2018, Mikhail Morfikov wrote:
> Basically, all messages returned by X-applications are redirected to the
> ~/.xsession-errors file.
[...]
> Unfortunately, the ~/.xsession-errors file grows in size, and after a
> few hours it's around 20-30 MiB, and the content of th
On Fri, Apr 06, 2018 at 05:48:35PM +0200, Mikhail Morfikov wrote:
> If I set $ERRFILE to the FIFO device, processing of the script will be stopped
> in the point where "exec ..." appears (before sourcing the
> /etc/X11/Xsession.d/
> dir).
You need to run something in the background which opens
On 2018-04-06 15:48, to...@tuxteam.de wrote:
> On Fri, Apr 06, 2018 at 03:18:08PM +0200, Mikhail Morfikov wrote:
>> Basically, all messages returned by X-applications are redirected to the
>> ~/.xsession-errors file [...]
>
>> till a terminal with "cat" is st
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Apr 06, 2018 at 03:18:08PM +0200, Mikhail Morfikov wrote:
> Basically, all messages returned by X-applications are redirected to the
> ~/.xsession-errors file [...]
> till a terminal with "cat" is started inside of the
Basically, all messages returned by X-applications are redirected to the
~/.xsession-errors file. In some desktop environments this file is emptied with
each X session restart. At least that was the case of my Openbox + LightDM
setup. Now, I'm trying to migrate to KDE/Plasma5, and as a part
On Fri 24 Jun 2016 at 13:13:22 (-0700), Mike McClain wrote:
> I open several aps in .xsession, a couple of xterms, clock, iceweasel.
> The first in .xsession is an xterm I use for command line stuff.
> This xterm is seldom at any one pts but rather moves around. Is there
> a w
I open several aps in .xsession, a couple of xterms, clock, iceweasel.
The first in .xsession is an xterm I use for command line stuff.
This xterm is seldom at any one pts but rather moves around. Is there
a way to tell X to always open that xterm on /dev/pts/1?
Thanks,
Mike
--
During
Le Fri, 10 Jul 2015 06:30:02 +0200, Stéphane GARGOLY a écrit :
Moi, ce qui m'interpelle surtout, c'est de se retrouver avec un fichier
'.xsession-errors' de plus de... 200 Gio (soit plus de 200 000 Mio ou
encore plus de 200 000 000 kio). o_O
Je me demande comment cela est possible
On 10/07/2015 08:38, moi-meme wrote:
surtout que ce n'est pas une maladie du DD.
C'est la deuxième fois que cela se produit.
Juste par curiosité, tu peux publier un extrait ?
--
Fabien
--
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists
Pour
Le Fri, 10 Jul 2015 09:30:01 +0200, Fabien R a écrit :
C'est la deuxième fois que cela se produit.
Juste par curiosité, tu peux publier un extrait ?
--
tu le veux les 220G en totalité ? :-)
Non poubelle mais à la fin du fichier il disait en boucle qu'il ne
trouvait pas un fichier, je ne
pour éviter que le fichier explose ?
(limiter sa taille)
Moi, ce qui m'interpelle surtout, c'est de se retrouver avec un fichier
'.xsession-errors' de plus de... 200 Gio (soit plus de 200 000 Mio ou encore
plus de 200 000 000 kio). o_O
Je me demande comment cela est possible.
Cordialement et
un peu gros et ça ne laisse pas de place pour travailler :-(
Suite à petit problème X ça m'a tout bloqué.
Effacé le fichier : c'est reparti.
Mais comment faire pour éviter que le fichier explose ?
(limiter sa taille)
--
Lisez la FAQ de la liste avant de poser une question :
On Sat, Nov 08, 2014 at 04:17:21PM +, Brian wrote:
On Sat 08 Nov 2014 at 06:02:00 -1000, Joel Roth wrote:
Do you have a reference about .xinitrc vs. .xsession?
Lots. :). Fortunately, startx(1) has now been altered to read:
Note that in the Debian system, what many people
On Sat 08 Nov 2014 at 07:16:41 -1000, Joel Roth wrote:
On Sat, Nov 08, 2014 at 04:17:21PM +, Brian wrote:
On Sat 08 Nov 2014 at 06:02:00 -1000, Joel Roth wrote:
Do you have a reference about .xinitrc vs. .xsession?
Lots. :). Fortunately, startx(1) has now been altered to read
On Vi, 24 oct 14, 09:33:59, Raffaele Morelli wrote:
On 24/10/14 at 10:17am, Andrei POPESCU wrote:
On Jo, 23 oct 14, 19:38:15, John Conover wrote:
I use two WM, (xfce and fvwm.) Lightdm's Default Xsession is fvwm2.
How do I change lightdm's Default Xsession to xfce?
I prefer
Andrei POPESCU writes:
On Vi, 24 oct 14, 09:33:59, Raffaele Morelli wrote:
On 24/10/14 at 10:17am, Andrei POPESCU wrote:
On Jo, 23 oct 14, 19:38:15, John Conover wrote:
I use two WM, (xfce and fvwm.) Lightdm's Default Xsession is fvwm2.
How do I change lightdm's Default
On 25/10/14 22:11, John Conover wrote:
Andrei POPESCU writes:
On Vi, 24 oct 14, 09:33:59, Raffaele Morelli wrote:
On 24/10/14 at 10:17am, Andrei POPESCU wrote:
On Jo, 23 oct 14, 19:38:15, John Conover wrote:
I use two WM, (xfce and fvwm.) Lightdm's Default Xsession is fvwm2.
How do I
you have
both. Per user there is also ~/.dmrc.
In this particular case, the problem was an ~/.xinitrc, (linked to
~/.xsession, dated 1994!!! launching fvwm,) in the user's account. If
a .xinitrc/.xsession file exists, it is executed as Default Session
by lightdm, (regardless
On Jo, 23 oct 14, 19:38:15, John Conover wrote:
I use two WM, (xfce and fvwm.) Lightdm's Default Xsession is fvwm2.
How do I change lightdm's Default Xsession to xfce?
I prefer to do this at system level (i.e. will work for any DM):
update-alternatives --config x-session-manager
Kind
On 24/10/14 at 10:17am, Andrei POPESCU wrote:
On Jo, 23 oct 14, 19:38:15, John Conover wrote:
I use two WM, (xfce and fvwm.) Lightdm's Default Xsession is fvwm2.
How do I change lightdm's Default Xsession to xfce?
I prefer to do this at system level (i.e. will work for any DM
I use two WM, (xfce and fvwm.) Lightdm's Default Xsession is fvwm2.
How do I change lightdm's Default Xsession to xfce?
Thanks,
John
--
John Conover, cono...@rahul.net, http://www.johncon.com/
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject
On 24/10/14 13:38, John Conover wrote:
I use two WM, (xfce and fvwm.) Lightdm's Default Xsession is fvwm2.
How do I change lightdm's Default Xsession to xfce?
Thanks,
John
As root:-
/usr/lib/i386-linux-gnu/lightdm/lightdm-set-defaults -s xfce4-session
Ref:-
/usr/lib/i386
On 23/10/14 at 07:38pm, John Conover wrote:
I use two WM, (xfce and fvwm.) Lightdm's Default Xsession is fvwm2.
How do I change lightdm's Default Xsession to xfce?
Thanks,
John
--
John Conover, cono...@rahul.net, http://www.johncon.com/
--
To UNSUBSCRIBE, email
On 15/09/2014, Chen Wei weichen...@icloud.com wrote:
On Tue, Sep 09, 2014 at 03:29:04PM +0800, Bret Busby wrote:
.xsession-errors, which is currently sitting at about 740MB, and has
been growing in the last hour.
entries from before the current boot session) entries, so as to reduce
the file
On Mon, 15 Sep 2014 15:07:48 +0800
Bret Busby bret.bu...@gmail.com wrote:
On 15/09/2014, Chen Wei weichen...@icloud.com wrote:
On Tue, Sep 09, 2014 at 03:29:04PM +0800, Bret Busby wrote:
.xsession-errors, which is currently sitting at about 740MB, and
has been growing in the last hour
On Tue, Sep 09, 2014 at 03:29:04PM +0800, Bret Busby wrote:
.xsession-errors, which is currently sitting at about 740MB, and has
been growing in the last hour.
entries from before the current boot session) entries, so as to reduce
the file size to content that is necessary to retain
the file, then ran Empty Trash Can,
but, no disc space was freed, then, subsequently, I observed that a
new file had been created;
.xsession-errors.old
with a size of about 33kB, and so I overwrote that, as described
above, and that reduced its size to zero, but, I now do not have
the system
up in
the same state, you might see it in /proc/$(pidof Xorg)/fd (or it might
be
another process other than Xorg, or I might be wrong entirely)
if you have lsof installed, you can find out what processes are still
using the deleted file quite easily:
$ lsof |grep '\.xsession
have the system
up in
the same state, you might see it in /proc/$(pidof Xorg)/fd (or it might
be
another process other than Xorg, or I might be wrong entirely)
if you have lsof installed, you can find out what processes are still
using the deleted file quite easily:
$ lsof |grep '\.xsession
Bret Busby bret.bu...@gmail.com writes:
I note that, with that file that is being accessed by Nautilus,
assuming that the number 1169162 , is the size of the file, I have
tried, but, apparently, can not reduce that to zero, as that number
does not change, with my attempts.
On a side note:
Bret Busby bret.bu...@gmail.com writes:
So, I believe (unttil and unless, advised otherwise) that the
deleteing the file (which did not free up the disc space, in itself),
and then, renaming the xsystem-errors.old file, to xsystem-errors,
appears to have disappeared the problem, which, if I
Hello.
In trying to work out why my disk space gets progressively consumed so
that I repeatedly run out of disc space without any known reason, in
examining my hidden files in my home directory, I found the file
.xsession-errors, which is currently sitting at about 740MB, and has
been growing
that is necessary to retain for debugging?
xsession-errors should be re-created when a new session starts (see
/etc/X11/Xsession for the details). Long-running X session can produce
annoyingly large .xsession-errors indeed.
The solution to this problem comes in the form of logrotate:
$ cat /etc
On 09/09/14 at 03:29pm, Bret Busby wrote:
Hello.
In trying to work out why my disk space gets progressively consumed so
that I repeatedly run out of disc space without any known reason, in
examining my hidden files in my home directory, I found the file
.xsession-errors, which is currently
incantation is one answer:
tal% ls -alh .xsession-errors
-rw--- 1 chrisb chrisb 33K Sep 9 17:40 .xsession-errors
tal% : .xsession-errors
tal% ls -alh .xsession-errors
-rw--- 1 chrisb chrisb 0 Sep 9 21:25 .xsession-errors
--
If you're not careful, the newspapers will have you hating the people
such damage would occur by deleting it, but
the following incantation is one answer:
tal% ls -alh .xsession-errors
-rw--- 1 chrisb chrisb 33K Sep 9 17:40 .xsession-errors
tal% : .xsession-errors
tal% ls -alh .xsession-errors
-rw--- 1 chrisb chrisb 0 Sep 9 21:25 .xsession-errors
to the boot session, would occur.
I very much doubt that any such damage would occur by deleting it, but
the following incantation is one answer:
tal% ls -alh .xsession-errors
-rw--- 1 chrisb chrisb 33K Sep 9 17:40 .xsession-errors
tal% : .xsession-errors
tal% ls -alh .xsession-errors
-rw
On Wed 10 Sep 2014 at 01:24:24 +0800, Bret Busby wrote:
Just out of interest, top shows the system as having been up for 21
days, so, the xsession-errors file grew to 743MB, in 21 days. I saw,
at the top of that file, before I deleted it, reference to 21 August,
so, the file apparently, grows
On 10/09/2014, Brian a...@cityscape.co.uk wrote:
On Wed 10 Sep 2014 at 01:24:24 +0800, Bret Busby wrote:
Just out of interest, top shows the system as having been up for 21
days, so, the xsession-errors file grew to 743MB, in 21 days. I saw,
at the top of that file, before I deleted
On Wed, Sep 10, 2014 at 01:54:08AM +0800, Bret Busby wrote:
The file has (kind of) gone, now (it is no longer accessible, but,
appears to still exist, in the ether of the unknown; still taking up
disc space, whilst, in theory, non-existent),
A file continues to use up disk space until all open
, then, subsequently, I observed that a
new file had been created;
.xsession-errors.old
with a size of about 33kB, and so I overwrote that, as described
above, and that reduced its size to zero, but, I now do not have the
original file with which to do that, and, I have about 750MB of
missing
be
another process other than Xorg, or I might be wrong entirely)
if you have lsof installed, you can find out what processes are still
using the deleted file quite easily:
$ lsof |grep '\.xsession-errors'
might produce lines like
xterm 2237 busbyenator 1w REG 8,1 0 359981 /home/busbyenator
Hallo,
In het bestand .xsession-errors op mijn dikke, slome laptop staan veel
foutmeldingen die wijzen op configuratiefouten van gnome-session en
DBus, te beginnen met:
(gnome-settings-daemon:3923): color-plugin-WARNING **: failed to get
devices: Failed to GetDevices
I have been noticing this error in .xsession-errors file lately:
glibtop: Non-standard uts for running kernel:
release 3.12-1-686-pae=3.12.0 gives version code 199680
Can someone explain what's this about ? Should I be concerned?
Thanks
--
To UNSUBSCRIBE, email to debian-user-requ
On Tuesday, February 18, 2014 12:12:20 PM Frank McCormick wrote:
I have been noticing this error in .xsession-errors file lately:
glibtop: Non-standard uts for running kernel:
release 3.12-1-686-pae=3.12.0 gives version code 199680
Can someone explain what's this about ? Should I
On 2014-02-18 18:12 +0100, Frank McCormick wrote:
I have been noticing this error in .xsession-errors file lately:
glibtop: Non-standard uts for running kernel:
release 3.12-1-686-pae=3.12.0 gives version code 199680
Can someone explain what's this about ?
It's glibtop complaining about
Version: 2.28.5-2
Severity: normal
Dear Maintainer,
* What led up to the situation?
..xsession-errors entry:
glibtop: Non-standard uts for running kernel:
release 3.12-1-amd64=3.12.0 gives version code 199680
--
Paul Cartwright
Registered Linux User #367800 and new counter #561587
uts for running kernel:
Package: libgtop2-7
Version: 2.28.5-2
Severity: normal
Dear Maintainer,
* What led up to the situation?
..xsession-errors entry:
glibtop: Non-standard uts for running kernel:
release 3.12-1-amd64=3.12.0 gives version code 199680
I have a comment to the bug...re
code:
Fwd: Bug#739444: glibtop: Non-standard uts for running kernel:
Package: libgtop2-7
Version: 2.28.5-2
Severity: normal
Dear Maintainer,
* What led up to the situation?
..xsession-errors entry:
glibtop: Non-standard uts for running kernel:
release 3.12-1-amd64=3.12.0 gives version code
On 18/02/14 02:02 PM, Sven Joachim wrote:
On 2014-02-18 18:12 +0100, Frank McCormick wrote:
I have been noticing this error in .xsession-errors file lately:
glibtop: Non-standard uts for running kernel:
release 3.12-1-686-pae=3.12.0 gives version code 199680
Can someone explain what's
On Tue, 2014-02-18 at 11:19 -0600, y...@marupa.net wrote:
This is probably not the best advice but: If nothing slows
down/crashes/screws up data, then you can probably ignore it.
It's a good advice, it's only missing that people should do some
Internet research.
Bug#739444
Oops, by accident I posted a wrong link.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1392754630.2586.42.camel@archlinux
caras del cubo 3D
que se puede ver.
Despues desaparecio el menu, ya no sale. Despues de me quede sin
espacio siendo que el disco era de 1 thera y no encontraba la solucion
hasta que investigando llegue a que el archivo xsession-errors es el
que se llena rapido y ocupa todo el disco duro. Para trabjar
desaparecio el menu, ya no sale. Despues de me quede sin espacio
siendo que el disco era de 1 thera y no encontraba la solucion hasta que
investigando llegue a que el archivo xsession-errors es el que se llena
rapido y ocupa todo el disco duro. Para trabjar tuve que borrarlo en su
totalidad e hice un
On Fri 03 Jan 2014 at 16:28:05 +1100, Zenaan Harkness wrote:
On 12/13/13, Zenaan Harkness z...@freedbms.net wrote:
Clearly consolekit is started (logout, as well as reboot etc now
work), my keyboard shortcuts work etc.
This seems ideal - no per-user configuration, and it just works
On 1/3/14, Brian a...@cityscape.co.uk wrote:
On Fri 03 Jan 2014 at 16:28:05 +1100, Zenaan Harkness wrote:
On 12/13/13, Zenaan Harkness z...@freedbms.net wrote:
Clearly consolekit is started (logout, as well as reboot etc now
work), my keyboard shortcuts work etc.
This seems ideal - no
~/.xinitrc and ~/.xsession and I have no ~/.xsessionrc
.
So now things work as well as they did with ~/.xinitrc , but without
any ~/.x* files! This is good.
Clearly consolekit is started (logout, as well as reboot etc now
work), my keyboard shortcuts work etc.
This seems ideal - no per-user
On 2013-12-12 00:21:18 -0700, Bob Proulx wrote:
2.1 xdm graphical login manager (or gdm, or kdm, or lightdm, or other)
Runs /etc/X11/Xsession
Redirects output to .xsession-errors
[...]
Not for gdm3 3.5.2+. $XDG_CACHE_HOME/gdm/session.log is now used,
but this is currently a bit
On Mon 16 Dec 2013 at 17:17:01 +1300, Chris Bannister wrote:
On Sat, Dec 14, 2013 at 08:25:56PM +, Brian wrote:
Put
exec fvwm
after the xterm command in .xsession. This command does not complete and
.xsession doesn't close. You've summoned X, give it a chance to show off
On Sat, Dec 14, 2013 at 08:25:56PM +, Brian wrote:
Put
exec fvwm
after the xterm command in .xsession. This command does not complete and
.xsession doesn't close. You've summoned X, give it a chance to show off
what it can do :).
EXERCISE: You decide 'exec fvwm' is a splendid
On Thu, Dec 12, 2013 at 02:23:48PM +, Brian wrote:
On Thu 12 Dec 2013 at 00:21:18 -0700, Bob Proulx wrote:
The man page for Xsession documents ~/.xsessionrc and ~/.xsession. It
says that ~/.xsessionrc is only for setting variables and the
~/.xsession is for executing commands
On Sun, 15 Dec 2013 06:29:52 +1300 Chris Bannister sent:
I do remember this issue in the past, a google was not very helpful -
and may even have been misleading - e.g. suggesting that .xsessionrc
was the correct file to use. And since .xsession or .xinitrc didn't
work I must have assumed
. Remember that a script executes each line
sequentially and only moves on to the next line if the previous command
completes.
The xterm is put in the background; the command has completed. There is
no next line in .xsessionrc so /etc/X11/Xsession moves on from
40x11-common_xsessionrc to 50x11
is not
conducive to holding in my mind at the same time to answer this
question.
I have experimented with a couple combinations, but there are too many.
I have at the moment, startx working well, with .xinitrc and .xsession
both linking to the same file (bash script, with my exec ... line).
When I log
I wonder, in Debian does a path exist so that if a user wants to install a
g.u.i. environment without gdm and with startX so that they can run in
console mode by default and when they want to go g.u.i. they run startX to
do it and have orca start up after that automatically? If so, I'd like to
orca start up after that automatically? If so, I'd like to
learn how to do that.
Perhaps re-read this thread (and the other similar one) again in
detail. This is exactly what I'm doing. Or if you want simple answer:
create ~/.xinitrc or ~/.xsession and make the file look like mine (see
earlier
On Thu, 12 Dec 2013 00:28:54 -0700 Bob Proulx sent:
No it really should be ~/.xsession. This can be deduced by inspecting
the /etc/X11/Xsession.d/50x11-common_determine-startup file. Or see
the man page such as these snippets from it.
That's what I had for years but then something must have
1 - 100 of 682 matches
Mail list logo
