Summary: | x11-wm/awesome-3.2.1-r3 x11-libs/pango-1.24.2: crash on window title set | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Khumba <bog> |
Component: | Current packages | Assignee: | Alex Alexander (RETIRED) <wired> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | auke, leio |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
URL: | http://osdev.org/phpBB2 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
Gdb backtrace of awesome's coredump.
Output of startx. My make.conf. |
Description
Khumba
2009-05-30 18:55:11 UTC
Created attachment 193000 [details]
Gdb backtrace of awesome's coredump.
Created attachment 193001 [details]
Output of startx.
Created attachment 193003 [details]
My make.conf.
Looks like non-ascii characters in title is what triggers the problem, since both your test cases use special characters (• bullet for first, » double angle for second) -- which fits with the complaint about wide characters you got before crash. Thanks for the report, assigning to maintainer. Please try to set utf-8 locale to LANG environment variable before start awesome. For example, LANG=en_US.UTF-8. cf. http://www.mail-archive.com/awesome@naquadah.org/msg01112.html Yes, I hadn't created an /etc/env.d/02local. Setting LANG=en_US.UTF-8 in there fixed the problem for me. Thanks! Is it right for Pango to be crashing though? Confirmed. It is the same with awesome 3.3 and 3.2.* worked before, it is an other package that broke them Takuto's solution did not fix the problem for me. I'm using a number of masked X packages on ~amd64. (In reply to comment #8) > Takuto's solution did not fix the problem for me. I'm using a number of masked > X packages on ~amd64. > please try these commands. $ echo $LANG $ echo $LC_ALL $ locale $ LANG=en_US.UTF-8 LC_ALL=en_US.UTF-8 awesome and could you test this patch? http://git.naquadah.org/?p=awesome.git;a=commit;h=9c8efee9bf06ac731454d293e269d5c909c8175b LANG=en.US-UTF-8, but LC_ALL= (ie empty) (both in the terminal and in locale's output) the patch didn't help, nor did setting LC_ALL to en.US-UTF-8. I will try and make a backtrace soon. sheesh, I should get one of those books on GDB, i'm really struggling with it. anyway, rebuilt awesome with USE=debug, and although it depends on which planets line up, it seems like the problem is in property.c:168, which is an initialization call to xcb (and in some of my tests, xcb was indeed clearly doing stuff with uninitialized pointers). I suspect xcb is the cause of issues, here, since I haven't updated pango nor awesome since the problems began. awesome-3.3.1 in cvs. perhaps, its fixed the pango issue. This is what works for me: echo "es_ES.UTF-8 UTF-8" >> /etc/locale.gen locale-gen echo "LANG="es_ES.UTF-8" >> /etc/env.d/02locale reboot (with env-update, source /etc/profile and restart of xdm don't work, so finally I reboot the computer and works. I don't understand why) Only for curiosity, if you want to see the text that are causing the crash, you can edit /usr/share/awesome/lib/awful/util.lua in line 98, change: function escape(text) return text and text:gsub("['&<>\"]", xml_entity_names) or nil end by function escape(text) os.execute("echo '" .. text .. "' >> /tmp/aw.log") return text and text:gsub("['&<>\"]", xml_entity_names) or nil end When it crash again, you can see the text that causes the crash in the last line of /tmp/aw.log. In my case I can't access to gmail page in spanish, it tries to display: Gmail: correo electr?nico de Google - Mozilla Firefox instead of: Gmail: correo electrónico de Google - Mozilla Firefox pango-1.24.2 was crashing instead of logging a critical warning (which should get fixed in the API consumer - awesome - too still) due to a packaging bug that disabled the safeguards against bad API usage. pango-1.24.4 and later packages shouldn't crash on markup_text being NULL, but log a critical warning instead, which should be fixed from awesome's end probably, but at least not crashing. This works OK here (with properly set locale) in latest awesome. Please re-open if you still have issues after setting up your locale. |