[Ubuntu-x-swat] [Bug 738526] Re: crash accessing font info with xfs in fontpath
Both upstream bug reports were fixed along time ago An 'Incomplete' bug report raised against Ubuntu 10.10 is of little use now as the last manual comment was made almost ten years ago. Will close as being fixed due to any comments suggesting that the bug is still extant in a currently supported release. ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/738526 Title: crash accessing font info with xfs in fontpath To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/738526/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 738526] Re: crash accessing font info with xfs in fontpath
** Changed in: xorg-server (Debian) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/738526 Title: crash accessing font info with xfs in fontpath To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/738526/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 738526] Re: crash accessing font info with xfs in fontpath
@Christopher M. Penalver Is xfs package available in trusty? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/738526 Title: crash accessing font info with xfs in fontpath To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/738526/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 738526] Re: crash accessing font info with xfs in fontpath
Ashley Yakeley, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If it remains an issue, could you please run the following command in the development release from a Terminal (Applications-Accessories-Terminal), as it will automatically gather and attach updated debug information to this report: apport-collect -p xorg-server REPLACE-WITH-BUG-NUMBER Please note, given you already have done this in a prior release, performing this on a release prior to Trusty would not be helpful. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs ** Changed in: xorg-server (Ubuntu) Importance: Medium = Low ** Changed in: xorg-server (Ubuntu) Status: Triaged = Incomplete -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/738526 Title: crash accessing font info with xfs in fontpath To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/738526/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 738526] Re: crash accessing font info with xfs in fontpath
According to the link: http://ubuntuforums.org/showthread.php?t=2183029 I commented out from /etc/X11/xorg.conf : #Section Files # FontPath unix/:7100 #EndSection to achieve a similar effect of uninstalling xfs This seems to be another successful workaround. (Unless xfs is manually called or something). -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/738526 Title: crash accessing font info with xfs in fontpath To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/738526/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 738526] Re: crash accessing font info with xfs in fontpath
Uninstalling xfs, for example by simply using Synaptic (search on 'xfs', and do 'Remove' (but not 'Remove Completely'), worked for me on Ubuntu 12.04 LTS all-up-to-date as of now. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/738526 Title: crash accessing font info with xfs in fontpath To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/738526/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 738526] Re: crash accessing font info with xfs in fontpath
@Timo, there have been a couple other bugs reported like this, where the workaround is to remove xfs. Should we just drop xfs from the archive? We don't need it for anything afaik? Please note that xfs can run over TCP. So this is roughly like having a crash in ssh, and asking if the fix would be to remove sshd. We run N (where N 1) Ubuntu instances here, and it makes life much, much easier to add fonts at a central server. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/738526 Title: crash accessing font info with xfs in fontpath To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/738526/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 738526] Re: crash accessing font info with xfs in fontpath
Launchpad has imported 12 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=31501.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.
On 2010-11-09T15:23:48+00:00 Jon TURNEY wrote:
Doing some investigation of this reported crash whilst using xserver
1.9.2 with xfs: http://cygwin.com/ml/cygwin-xfree/2010-11/msg8.html,
I'm able to reproduce this crash with the following sequence of actions:
X
xterm
xset fp+ tcp/myfontserver:7100
xlsfonts
Program received signal SIGSEGV, Segmentation fault.
[Switching to thread 4712.0x1220]
0x005b2e29 in doListFontsAndAliases (client=0x125fdc0, c=0x120fce8) at
dixfonts.c:611
611 fpe = c-fpe_list[c-current.current_fpe];
(gdb) p c
$1 = (LFclosurePtr) 0x120fce8
(gdb) p *c
$2 = {client = 0x120fce0, num_fpes = 18939104, fpe_list = 0x0, names = 0x0,
current = {
pattern = ▒W
a\002\000\000\000ed-medium-r-normal--24-230-75-75-c-240-jisx0208.1983-0\va▒\207\va\000\000\000\000▒▒
\0019\017\000\000\b\000\000\000\000\000\000\000|▒%a\000\000\000\000\001\000\000\000\001\000\000\000▒\207\va\220▒\va@▒\va\000\000\000\000\030▒
\001\t\017\000\000\t\000\000\000\024\004\000\000▒▒%a\000\000\000\000\000\000\000\000\001\000\000\000\020\231\va▒\227\va▒\207\va\000\000\000\000H▒
\001▒\016\000\000\v\000\000\000\024\004\000\000▒▒%a\000\000\000\000\000\000\000\000\001\000\000\000...,
patlen = 62, current_fpe = 5, max_names = 3, list_started = 0, private =
0x12df550},
saved = {
pattern =
*\000\000\000\001\000\000\000\020\231\va▒\227\va▒\207\va\000\000\000\000▒\001i\017\000\000\005\000\000\000\024\004\000\000|▒#a\000\000\000\000\000\000\000\000\001\000\000\000\020\231\va▒\227\va▒\207\va\000\000\000\000▒▒
\0019\017\000\000\b\000\000\000\000\000\000\000|▒%a\000\000\000\000\001\000\000\000\001\000\000\000▒\207\va\220▒\va@▒\va\000\000\000\000\030▒
\001\t\017\000\000\t\000\000\000\024\004\000\000▒▒%a\000\000\000\000\000\000\000\000\001\000\000\000\020\231\va▒\227\va▒\207\va\000\000\000\000H▒
\001▒\016\000\000\v\000\000\000\024\004\000\000▒▒%a\000\000\000\000\000\000\000\000\001\000\000\000...,
patlen = 1, current_fpe = 0, max_names = 65535, list_started = 1, private =
0x125fb10},
haveSaved = 1, savedName = 0x12df338
-jis-fixed-medium-r-normal--24-230-75-75-c-240-jisx0208.1983-0,
savedNameLen = 64}
(gdb)
On further investigation, the reason for the closure c being corrupt
seems to be related to the changes added in commit 3ab6cd31 to fix bug
#3040.
In doListFontsAndAliases(), if we get a Suspended result when the client
is already sleeping with the same closure (I don't really understand
enough what the code is doing to know if that's expected or not), then
the xinerama_sleep code frees() the closure c, so when it next wakes,
the closure c is being used after being freed.
Being a use after free bug possibly explains why the original reporter
is able to avoid the crash by changing the sequence of actions slightly.
The crash is not observed after reverting the noted commit, or with
xserver 1.8.2
Reply at: https://bugs.launchpad.net/xorg-server/+bug/738526/comments/0
On 2010-12-09T22:52:05+00:00 Jon TURNEY wrote:
See also https://bugzilla.redhat.com/show_bug.cgi?id=658587
Reply at: https://bugs.launchpad.net/xorg-server/+bug/738526/comments/1
On 2010-12-10T00:27:42+00:00 Jajones wrote:
Created attachment 40973
Possible fix
Haven't tested this thoroughly, as I'm not convinced early-out is really
the right way to handle Xinerama here, but I think this should fix the
crashes at least. Feel free to try it out.
Reply at: https://bugs.launchpad.net/xorg-server/+bug/738526/comments/2
On 2010-12-15T12:44:50+00:00 Colin-harrison wrote:
Hi,
It's not pretty, but James' patch fixes the crash for me.
Thanks,
Colin Harrison
Reply at: https://bugs.launchpad.net/xorg-server/+bug/738526/comments/3
On 2011-03-07T12:12:14+00:00 Julien Cristau wrote:
*** Bug 31675 has been marked as a duplicate of this bug. ***
Reply at: https://bugs.launchpad.net/xorg-server/+bug/738526/comments/4
On 2011-04-11T21:25:14+00:00 Jeremy Huddleston wrote:
James, have you sent this to xorg-devel for review / comment? I didn't
see it in a quick check of emails from you in December.
Reply at: https://bugs.launchpad.net/xorg-server/+bug/738526/comments/22
On 2011-04-27T08:09:38+00:00
[Ubuntu-x-swat] [Bug 738526] Re: crash accessing font info with xfs in fontpath
Bug #885813 is probably a dupe. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/738526 Title: crash accessing font info with xfs in fontpath To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/738526/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 738526] Re: crash accessing font info with xfs in fontpath
@Timo, there have been a couple other bugs reported like this, where the workaround is to remove xfs. Should we just drop xfs from the archive? We don't need it for anything afaik? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/738526 Title: crash accessing font info with xfs in fontpath To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/738526/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 738526] Re: crash accessing font info with xfs in fontpath
** Changed in: xorg-server Status: Unknown = Confirmed ** Changed in: xorg-server Importance: Unknown = Medium -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/738526 Title: crash accessing font info with xfs in fontpath ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 738526] Re: crash accessing font info with xfs in fontpath
** Changed in: xorg-server (Debian) Status: Unknown = Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/738526 Title: crash accessing font info with xfs in fontpath ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
