.xsession-errors
Manon Metten
Today I noticed this '.xsession-errors' file in my home dir. It's
telling me following:
Xsession: X session started for manon at Thu Jun 5 18:10:00 CEST 2008
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
startkde: Starting up...
kbuildsycoca running...
QFont::setPointSize: Point size <= 0 (-3)
X Error: BadAccess (attempt to access private resource denied) 10
Major opcode: 2
Minor opcode: 0
Resource id: 0x1e0000c
X Error: BadAccess (attempt to access private resource denied) 10
Major opcode: 2
Minor opcode: 0
Resource id: 0x1e0000c
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 19
Minor opcode: 0
Resource id: 0x1e006de
Can anyone please tell me how I can eliminate or correct these errors?
Greetings and thanks in advance,
Manon Metten
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Andrew Reid
> 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 problem.
My experience is that X errors are notoriously hard to
diagnose, so unless you're seeing some pathology independently
of the error report, I'd ignore them.
-- A.
--
Andrew Reid / rei...@bellatlantic.net
Kamaraju S Kusumanchi
> X Error: BadAccess (attempt to access private resource denied) 10
> Major opcode: 2
> Minor opcode: 0
> Resource id: 0x1e0000c
> X Error: BadAccess (attempt to access private resource denied) 10
> Major opcode: 2
> Minor opcode: 0
> Resource id: 0x1e0000c
> X Error: BadWindow (invalid Window parameter) 3
> Major opcode: 19
> Minor opcode: 0
> Resource id: 0x1e006de
>
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.
> Can anyone please tell me how I can eliminate or correct these errors?
No idea! But I am interested in knowing the answer as well.
thanks
raju
--
Kamaraju S Kusumanchi
http://www.people.cornell.edu/pages/kk288/
http://malayamaarutham.blogspot.com/
Manon Metten
<snip>
> 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 Firefox 2.0.0.14 crashing regularly.
Everything else is running fine.
Greetings, Manon.
Michelle Konzack
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
please, then I can tell you where the error is.
Thanks, Greetings and nice Day
Michelle Konzack
Systemadministrator
24V Electronic Engineer
Tamay Dogan Network
Debian GNU/Linux Consultant
--
Linux-User #280138 with the Linux Counter, http://counter.li.org/
##################### Debian GNU/Linux Consultant #####################
Michelle Konzack Apt. 917 ICQ #328449886
+49/177/9351947 50, rue de Soultz MSN LinuxMichi
+33/6/61925193 67100 Strasbourg/France IRC #Debian (irc.icq.com)
Manon Metten
On 6/6/08, Michelle Konzack <linux4m...@tamay-dogan.net> 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 the output of
>
> xset q
Here's the output:
Keyboard Control:
auto repeat: on key click percent: 0 LED mask: 00000002
auto repeat delay: 250 repeat rate: 25
auto repeating keys: 00ffffffdffffbbf
fadfffdfffdfe5ef
ffffffffffffffff
ffffffffffffffff
bell percent: 50 bell pitch: 400 bell duration: 100
Pointer Control:
acceleration: 20/10 threshold: 4
Screen Saver:
prefer blanking: no allow exposures: yes
timeout: 310 cycle: 600
Colors:
default colormap: 0x20 BlackPixel: 0 WhitePixel: 16777215
Font Path:
/usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi:unscaled,/usr/share/fonts/X11/75dpi:unscaled,/usr/share/fonts/X11/Type1,/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType,/usr/local/share/fonts
Bug Mode: compatibility mode is disabled
DPMS (Energy Star):
Standby: 600 Suspend: 1200 Off: 3600
DPMS is Enabled
Monitor is On
Thanks in advance, Manon.
Kamaraju S Kusumanchi
>
> 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 a safe mode using "iceweasel -safe-mode". Another thing to
look for are the flash packages installed on the system. FWIW, I am running
Debian Etch, iceweasel 2.0.0.14 and it does not crash at all!
hth
raju
--
Kamaraju S Kusumanchi
http://www.people.cornell.edu/pages/kk288/
http://malayamaarutham.blogspot.com/
Manon Metten
On 6/7/08, Kamaraju S Kusumanchi <kama...@bluebottle.com> 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 track down the iceweasel crashes is to disable all the add-ons and start
> iceweasel in a safe mode using "iceweasel -safe-mode". Another thing to
> look for are the flash packages installed on the system. FWIW, I am running
> Debian Etch, iceweasel 2.0.0.14 and it does not crash at all!
Thanks for the tip.
I was using Firefox (not Iceweasel) with flashplayer r115. I installed
the newest version (r124) to see if that was the problem. If not, I'll
disabling add-ons and try safe-mode.
Greetings, Manon.
Michelle Konzack
Am 2008-06-07 02:16:31, schrieb Manon Metten:
> On 6/6/08, Michelle Konzack <linux4m...@tamay-dogan.net> 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
> Font Path:
> /usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi:unscaled,/usr/
share/fonts/X11/75dpi:unscaled,/usr/share/fonts/X11/Type1,/var/lib/defo
ma/x-ttcidfont-conf.d/dirs/TrueType,/usr/local/share/fonts
^^^^^^^^^^^^^^^^^^^^^^^
Maybe you should remove this directory since I can not imagine you have
it. I have several installations from Woody, Sarge, Etch, Lenny and Sid
and there is not a singel installation, where this directory exist.
So removing this directory from the FontPath will eliminate the above
four Error lines.
Michelle Konzack
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 --recursive 'setPointSize' /etc/*
> X Error: BadAccess (attempt to access private resource denied) 10
> Major opcode: 2
> Minor opcode: 0
> Resource id: 0x1e0000c
> X Error: BadAccess (attempt to access private resource denied) 10
> Major opcode: 2
> Minor opcode: 0
> Resource id: 0x1e0000c
> X Error: BadWindow (invalid Window parameter) 3
> Major opcode: 19
> Minor opcode: 0
> Resource id: 0x1e006de
>
> Can anyone please tell me how I can eliminate or correct these errors?
Maybe we get the program which try to set the wrong FontSize.
Manon Metten
On 6/8/08, Michelle Konzack <linux4m...@tamay-dogan.net> wrote:
> Hi Manon,
>
> Am 2008-06-07 02:16:31, schrieb Manon Metten:
>
> > On 6/6/08, Michelle Konzack <linux4m...@tamay-dogan.net> 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
>
>
> > Font Path:
> > /usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi:unscaled,/usr/
> share/fonts/X11/75dpi:unscaled,/usr/share/fonts/X11/Type1,/var/lib/defo
> ma/x-ttcidfont-conf.d/dirs/TrueType,/usr/local/share/fonts
>
> ^^^^^^^^^^^^^^^^^^^^^^^
> Maybe you should remove this directory since I can not imagine you have
> it. I have several installations from Woody, Sarge, Etch, Lenny and Sid
> and there is not a singel installation, where this directory exist.
>
> So removing this directory from the FontPath will eliminate the above
> four Error lines.
I checked all these dirs:
drwxr-xr-x 2 root root /usr/share/fonts/X11/misc
drwxr-xr-x 2 root root /usr/share/fonts/X11/100dpi
drwxr-xr-x 2 root root /usr/share/fonts/X11/75dpi
drwxr-xr-x 2 root root /usr/share/fonts/X11/Type1
drwxr-xr-x 2 root root /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType
drwxrwsr-x 2 root staff /usr/local/share/fonts
All but /usr/share/fonts/X11/Type1 have a 'fonts.dir' file in it.
/usr/share/fonts/X11/misc
/usr/share/fonts/X11/100dpi
/usr/share/fonts/X11/75dpi
contain lots of *.pcf.gz files
/usr/share/fonts/X11/Type1
contains '*.pfb' softlinks to '../../type1/gsfonts/' which does not exist
/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType
contains softlinks to '/usr/share/fonts/truetype'
/usr/local/share/fonts
contains a softlink to '/usr/share/fonts/X11/encodings/encodings.dir'
and a custom installed font
So I removed '/usr/share/fonts/X11/Type1' and the errors where gone.
Thank you very much for the help.
Greetings, Manon.
Kamaraju S Kusumanchi
> Hi Michelle,
>
> On 6/8/08, Michelle Konzack <linux4m...@tamay-dogan.net> wrote:
>> Hi Manon,
>>
>> Am 2008-06-07 02:16:31, schrieb Manon Metten:
>>
>> > On 6/6/08, Michelle Konzack <linux4m...@tamay-dogan.net> 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
>>
>>
>> > Font Path:
>> > /usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi:unscaled,/usr/
>> share/fonts/X11/75dpi:unscaled,/usr/share/fonts/X11/Type1,/var/lib/defo
>> ma/x-ttcidfont-conf.d/dirs/TrueType,/usr/local/share/fonts
>>
>> ^^^^^^^^^^^^^^^^^^^^^^^
>> Maybe you should remove this directory since I can not imagine you have
>> it. I have several installations from Woody, Sarge, Etch, Lenny and Sid
>> and there is not a singel installation, where this directory exist.
>>
>> So removing this directory from the FontPath will eliminate the above
>> four Error lines.
>
>
> 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?
--
Kamaraju S Kusumanchi
http://www.people.cornell.edu/pages/kk288/
http://malayamaarutham.blogspot.com/
Manon Metten
On 6/13/08, Kamaraju S Kusumanchi <kama...@bluebottle.com> 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 started from.
Yesterday I renamed '/usr/share/fonts/X11/Type1', to
'/usr/share/fonts/X11/Type1-old', then deleted '~/.xsession-errors',
logged out and back in to KDE, just to find an empty .xsession-errors
file (well, almost empty, apart from the line telling me when my
xsession started). So I thought the problem was solved.
Today I noticed that the .xsession-errors file was like the one I
started this thread with. So I deleted
'/usr/share/fonts/X11/Type1-old', deleted '~/.xsession-errors', logged
out and back in to KDE and got a fresh .xsession-errors file, same as
where I started with.
In the end the errors are still there, only I've lost
'/usr/share/fonts/X11/Type1'.
Greetings, Manon.