> > 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
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.
https://bugs.debian.org/cgi-bi
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 this a
On 18/02/14 02:52 PM, Frank McCormick wrote:
On 18/02/14 02:39 PM, Paul Cartwright wrote:
On 02/18/2014 02:02 PM, Sven Joachim wrote:
No, but please file a bug against libgtop2-7 or the source package
libgtop2. For the reference, the message is in sysdeps/linux/open.c in
the libgtop2 source co
On 18/02/14 02:39 PM, Paul Cartwright wrote:
On 02/18/2014 02:02 PM, Sven Joachim wrote:
No, but please file a bug against libgtop2-7 or the source package
libgtop2. For the reference, the message is in sysdeps/linux/open.c in
the libgtop2 source code:
Fwd: Bug#739444: glibtop: Non-standard ut
On 02/18/2014 02:02 PM, Sven Joachim wrote:
> No, but please file a bug against libgtop2-7 or the source package
> libgtop2. For the reference, the message is in sysdeps/linux/open.c in
> the libgtop2 source code:
Fwd: Bug#739444: glibtop: Non-standard uts for running kernel:
Package: libgtop2-7
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 a
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
On 02/21/2011 09:16 PM, Dave Witbrodt wrote:
>
> I've been plagued by this one for over a year. The Debian BTS has a bug
> report for it already, and in comment 35 there I listed similar reports
> on other bug tracking systems:
>
thanks for the update!
>
> I'm hoping that the upcoming libgtk ve
On 02/21/2011 05:36 PM, Michelle Konzack wrote:
Hello Paul Cartwright,
Am 2011-02-21 16:01:58, hacktest Du folgendes herunter:
$ grep 'XID collision, trouble ahead' .xsession-errors | wc
275772 1930404 18116684
wow, ya got me beat:)
$ grep 'XID collision, trouble ahead' .xsession-errors | wc
On 02/21/2011 05:36 PM, Michelle Konzack wrote:
> I think I have to write some bug reports since there are three programs
> DOSing the .xsession-errors. 680 MByte in 3 days is inacceptable.
>
> However, if I stay as usualy one month and longer online my partition
> will crash...
yes, I delete
Hello Paul Cartwright,
Am 2011-02-21 16:01:58, hacktest Du folgendes herunter:
> > $ grep 'XID collision, trouble ahead' .xsession-errors | wc
> > 275772 1930404 18116684
> wow, ya got me beat:)
> $ grep 'XID collision, trouble ahead' .xsession-errors | wc
> 137884 965188 9100344
>
> I was goo
On 02/21/2011 03:47 PM, Ron Johnson wrote:
> > (firefox-bin:15563): Gdk-WARNING **: XID collision, trouble ahead
> >
> > is it my configuration, or a major gtk issue?
>
> a) They are warnings, not errors.
> b) They are *stupendously* common.
>
> $ grep 'XID collision, trouble ahead' .xsession-error
On 02/21/2011 02:26 PM, Paul Cartwright wrote:
I have lots& lots of these errors:
in .xsession-errors:
(firefox-bin:15563): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:15563): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:15563): Gdk-WARNING **: XID collision, trouble
On Thursday 20 May 2010 23:38:42 T o n g wrote:
> On Wed, 19 May 2010 11:33:02 -0500, Boyd Stephen Smith Jr. wrote:
> >> I took a look, the reason and cure is very simple -- having X to trunk
> >> it each time when started
> >> (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=287876) whereas
> >>
On Wed, 19 May 2010 11:33:02 -0500, Boyd Stephen Smith Jr. wrote:
>> I took a look, the reason and cure is very simple -- having X to trunk
>> it each time when started
>> (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=287876) whereas
>> currently, my ~/.xsession-errors kept logs back to stone
On 2010-05-19 19:19 +0200, d.sastre.med...@gmail.com wrote:
> FWIW, I don't have that problem, although /etc/X11/Xsession says:
>
> exec >>"$ERRFILE" 2>&1 (despite the solution proposed in¹)
> echo "$PROGNAME: X session started for $LOGNAME at $(date)"
>
> and the contents of it are, unsurprisingl
T o n g wrote:
Hi,
I am astonished to find out that my ~/.xsession-errors grows to a
humongous 640M! My wife's is nearly 400M as well. This is way way too
big.
I took a look, the reason and cure is very simple -- having X to trunk it
each time when started
(http://bugs.debian.org/cgi-bin/b
On Wed, May 19, 2010 at 06:45:04PM +0200, Sven Joachim wrote:
> On 2010-05-19 18:18 +0200, T o n g wrote:
>
> > I am astonished to find out that my ~/.xsession-errors grows to a
> > humongous 640M! My wife's is nearly 400M as well. This is way way too
> > big.
> >
> > I took a look, the reason
On 2010-05-19 18:18 +0200, T o n g wrote:
> I am astonished to find out that my ~/.xsession-errors grows to a
> humongous 640M! My wife's is nearly 400M as well. This is way way too
> big.
>
> I took a look, the reason and cure is very simple -- having X to trunk it
> each time when started
>
On Wednesday 19 May 2010 11:18:57 T o n g wrote:
> I am astonished to find out that my ~/.xsession-errors grows to a
> humongous 640M! My wife's is nearly 400M as well. This is way way too
> big.
>
> I took a look, the reason and cure is very simple -- having X to trunk it
> each time when started
On 15:44 Thu 15 Oct , Jan Willem Stumpel wrote:
I think I had this problem many years ago. I dont remember if it was in my old
redhat days or after I moved to debian in ?2003 or so. I remember I had a 50G
or 100G .xsession-errors file or
something like that.
The solution is simple. You must
Jan Willem Stumpel wrote at 2009-10-15 08:44 -0500:
> On my machine the file ~/.xsession-errors grows and grows without
> limits. I have to remove it regularly before it takes over my
> whole disk; this has been the case for years. Last time I removed
> it was September 21; now it is again already
Hugo Vanwoerkom wrote:
Hugo Vanwoerkom wrote:
Hi,
I get a lot of:
error 182 request 157 minor 8 serial 773
where 'serial'keeps climbing.
Anybody knows what it means?
Its meaning is still a mystery. But they show up after issuing:
xcompmgr -c -f
I've filed a bug:
http://bugs.debian.or
Hugo Vanwoerkom wrote:
Hi,
I get a lot of:
error 182 request 157 minor 8 serial 773
where 'serial'keeps climbing.
Anybody knows what it means?
Its meaning is still a mystery. But they show up after issuing:
xcompmgr -c -f
Hugo
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subje
Hi Raju,
On 6/7/08, Kamaraju S Kusumanchi <[EMAIL PROTECTED]> wrote:
> Manon Metten wrote:
>
> > The only problem I have lately is Firefox 2.0.0.14 crashing regularly.
> > Everything else is running fine.
>
> No. The opcode errors do not correspond to the firefox crashes. The best way
> to trac
Hi Raju,
On 6/13/08, Kamaraju S Kusumanchi <[EMAIL PROTECTED]> wrote:
> > So I removed '/usr/share/fonts/X11/Type1' and the errors where gone.
>
> Which errors? Did it get rid of the opcode errors or did it get rid of "bad
> font path element" errors?
To my surprise I'm back to where I've star
Manon Metten wrote:
> Hi Michelle,
>
> On 6/8/08, Michelle Konzack <[EMAIL PROTECTED]> wrote:
>> Hi Manon,
>>
>> Am 2008-06-07 02:16:31, schrieb Manon Metten:
>>
>> > On 6/6/08, Michelle Konzack <[EMAIL PROTECTED]> wrote:
>> > > > xset: bad font path element (#71), possible causes are:
>> > >
Hi Michelle,
On 6/8/08, Michelle Konzack <[EMAIL PROTECTED]> wrote:
> Hi Manon,
>
> Am 2008-06-07 02:16:31, schrieb Manon Metten:
>
> > On 6/6/08, Michelle Konzack <[EMAIL PROTECTED]> wrote:
> > > > xset: bad font path element (#71), possible causes are:
> > > > Directory does not exist o
Hi Manon,
Am 2008-06-07 02:16:31, schrieb Manon Metten:
> On 6/6/08, Michelle Konzack <[EMAIL PROTECTED]> wrote:
> > > xset: bad font path element (#71), possible causes are:
> > > Directory does not exist or has wrong permissions
> > > Directory missing fonts.dir
> > > Incorrect f
Hi again,
Am 2008-06-05 19:05:55, schrieb Manon Metten:
> QFont::setPointSize: Point size <= 0 (-3)
OK, there is a program which try to set an FontSize of "-3" which can
not exist. We can try to locate it with:
grep 'attempt to access private resource denied' /usr/bin/*
grep --recursiv
Hi Raju
On 6/7/08, Kamaraju S Kusumanchi <[EMAIL PROTECTED]> wrote:
> Manon Metten wrote:
>
> >
> > The only problem I have lately is Firefox 2.0.0.14 crashing regularly.
> > Everything else is running fine.
>
>
> No. The opcode errors do not correspond to the firefox crashes. The best way
> t
Manon Metten wrote:
>
> The only problem I have lately is Firefox 2.0.0.14 crashing regularly.
> Everything else is running fine.
No. The opcode errors do not correspond to the firefox crashes. The best way
to track down the iceweasel crashes is to disable all the add-ons and start
iceweasel in
Hi Michelle,
On 6/6/08, Michelle Konzack <[EMAIL PROTECTED]> wrote:
> > xset: bad font path element (#71), possible causes are:
> > Directory does not exist or has wrong permissions
> > Directory missing fonts.dir
> > Incorrect font server address or syntax
>
>
> Can you show us t
Hi Manon,
Am 2008-06-05 19:05:55, schrieb Manon Metten:
> xset: bad font path element (#71), possible causes are:
> Directory does not exist or has wrong permissions
> Directory missing fonts.dir
> Incorrect font server address or syntax
Can you show us the output of
xset q
ple
Hi Raju,
> Are you running KDE by any chance? I have the same errors in
> my .xsesssion-errors as well. I have a feeling that it is due to some badly
> written KDE app.
Yes, I'm running KDE (using etch: Linux debian 2.6.18-6-686 #1).
I forgot to mention.
The only problem I have lately is Fir
Manon Metten wrote:
> X Error: BadAccess (attempt to access private resource denied) 10
> Major opcode: 2
> Minor opcode: 0
> Resource id: 0x1ec
> X Error: BadAccess (attempt to access private resource denied) 10
> Major opcode: 2
> Minor opcode: 0
> Resource id: 0x1ec
>
On Thursday 05 June 2008 13:05, Manon Metten wrote:
> Hi,
>
> Today I noticed this '.xsession-errors' file in my home dir. It's
> telling me following:
[ Errors elided]
The .xsession-errors file is written as part of the normal
start-up sequence, so its mere presence is not automatically
a prob
[ Charset ISO-8859-1 converted... ]
> On Tue, May 20, 2008 at 10:48 PM, jamie <[EMAIL PROTECTED]> wrote:
> > Hi
> >
> > I wanted to ask a question about the file ".xsession-errors", namely its
> > contents.
> >
> > Inside this file in my home directory is see this:
> >
> > X Error: BadWindow (inval
On Tue, May 20, 2008 at 10:48 PM, jamie <[EMAIL PROTECTED]> wrote:
> Hi
>
> I wanted to ask a question about the file ".xsession-errors", namely its
> contents.
>
> Inside this file in my home directory is see this:
>
> X Error: BadWindow (invalid Window parameter) 3
> Major opcode: 19
>Minor
On Tue November 20 2007, s. keeling wrote:
> Dump kde? Figure out where the installer failed you? Is any of that
> at all interesting in your position? I'd just ignore it and
> concentrate on what I can't do with my apps. Once that's solved, the
> errors should stop. No, those errors are not w
On Nov 19, 2007 4:51 AM, Paul Cartwright <[EMAIL PROTECTED]> wrote:
> not sure what all this means, should I be worried?
>
> $ tail -50 .xsession-errors
> kbuildsycoca: WARNING: '/usr/share/applications/banshee.desktop' specifies
> undefined mimetype/servicetype 'audio/x-mpeg-3'
kbuildsycoca alwa
Paul Cartwright <[EMAIL PROTECTED]>:
> not sure what all this means, should I be worried?
>
> $ tail -50 .xsession-errors
> kbuildsycoca: WARNING: '/usr/share/applications/banshee.desktop' specifies
> undefined mimetype/servicetype 'audio/x-mpeg-3'
> [snip]
> kbuildsycoca: WARNING: 'Graphic
I found a nice discussion of this issue on a ubuntu forum.
https://bugs.launchpad.net/ubuntu/dapper/+source/xinit/+bug/60448
they discuss various approaches to handling the problem.
They point out that gdm wipes out the log on restart.
I am not running gdm, i start X with startx,
that is why s
On Wed, 19 Jul 100 [EMAIL PROTECTED] wrote:
> Hi there:
>
> My problem is I can't get into X mode, aparently 'cause of an
> authorization issue.
>
> My .xsessionerror file has these lines:
> ===
> xrdb: Can't open display ':0'
>
On Mon, 24 Mar 1997 20:18:07 + (GMT), "R.M. Hinkley" <[EMAIL PROTECTED]>
said:
>
> I wonder if anyone can help, I get the following in .xsession-errors
>
> xrdb: cannot run '/lib/cpp -traditional -Dlinux -D__i386__
> -D_POSIX_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE -DX_LOCALE [...]
I don't kno
46 matches
Mail list logo
