Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#18947 - lxterminal seqfault after gnome 2.28 -> 2.30 upgrade
Attached to Project:
Community Packages
Opened by J. Scott Heppler (shep) - Saturday, 03 April 2010, 15:11 GMT
Last edited by Ionut Biru (wonder) - Saturday, 03 April 2010, 20:44 GMT
Opened by J. Scott Heppler (shep) - Saturday, 03 April 2010, 15:11 GMT
Last edited by Ionut Biru (wonder) - Saturday, 03 April 2010, 20:44 GMT
|
DetailsDescription:lxterminal segfault
Additional info:Occurred after massive upgrade gnome 2.28 -> 2.30 Reinstall of lxterminal and cairo did not resolve Another occurences noted in forums: http://bbs.archlinux.org/viewtopic.php?id=94403 Googling did not reveal any upstream errors xterm and vte still work * package version(s) [jsh@Bear ~]$ pacman -Q | grep lxterminal lxterminal 0.1.7-1 [jsh@Bear ~]$ pacman -Q | grep cairo cairo 1.8.10-1 pycairo 1.8.8-1 * config and/or log files etc. [jsh@Bear ~]$ lxterminal Segmentation fault dmesg: lxterminal[2180]: segfault at 0 ip 00007fccec1bf93b sp 00007fff391f57e0 error 4 in libcairo.so.2.10800.10[7fccec17f000+78000] Steps to reproduce:Do a standard upgrade and start lxterminal |
This task depends upon
Closed by Ionut Biru (wonder)
Saturday, 03 April 2010, 20:44 GMT
Reason for closing: Fixed
Additional comments about closing: using vte-0.24.0-2
Saturday, 03 April 2010, 20:44 GMT
Reason for closing: Fixed
Additional comments about closing: using vte-0.24.0-2
I'll post in the forums for input from the i686 architecture users.