FS#40658 - [libxcursor] mixx crashes after a while, as well as other programs

Attached to Project: Arch Linux
Opened by farid (osc) - Tuesday, 03 June 2014, 15:02 GMT
Last edited by Jan de Groot (JGC) - Wednesday, 18 June 2014, 11:28 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Andreas Radke (AndyRTR)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 26
Private No

Details

Description:
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff288b0ff in __GI__IO_file_doallocate () from /usr/lib/libc.so.6
(gdb) backtrace
#0 0x00007ffff288b0ff in __GI__IO_file_doallocate () from /usr/lib/libc.so.6
#1 0x00007ffff2898060 in __GI__IO_doallocbuf () from /usr/lib/libc.so.6
#2 0x00007ffff28972ec in __GI__IO_file_underflow () from /usr/lib/libc.so.6
#3 0x00007ffff28980ae in __GI__IO_default_uflow () from /usr/lib/libc.so.6
#4 0x00007ffff288cc2a in __GI__IO_getline_info () from /usr/lib/libc.so.6
#5 0x00007ffff288bab3 in fgets () from /usr/lib/libc.so.6
#6 0x00007fffe8ed5570 in ?? () from /usr/lib/libXcursor.so.1
#7 0x00007fffe8ed59f2 in ?? () from /usr/lib/libXcursor.so.1
#8 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#9 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#10 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#11 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#12 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#13 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#14 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#15 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#16 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#17 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#18 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#19 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#20 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#21 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#22 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#23 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#24 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#25 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#26 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#27 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#28 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#29 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#30 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#31 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#32 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#33 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#34 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#35 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#36 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#37 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#38 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#39 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
---Type <return> to continue, or q <return> to quit---
#40 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#41 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#42 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#43 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#44 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#45 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#46 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#47 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#48 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#49 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#50 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#51 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#52 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#53 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#54 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#55 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#56 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#57 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#58 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#59 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#60 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#61 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#62 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#63 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#64 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#65 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#66 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#67 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#68 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#69 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#70 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#71 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#72 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#73 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#74 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#75 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#76 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#77 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#78 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#79 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
---Type <return> to continue, or q <return> to quit---
#80 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#81 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#82 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#83 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#84 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#85 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#86 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#87 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#88 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#89 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#90 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#91 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#92 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#93 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#94 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#95 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#96 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#97 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#98 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#99 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#100 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#101 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#102 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#103 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#104 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#105 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#106 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#107 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#108 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#109 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#110 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#111 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#112 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#113 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#114 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#115 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#116 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#117 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#118 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#119 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
---Type <return> to continue, or q <return> to quit---
#120 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#121 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#122 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#123 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#124 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#125 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#126 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#127 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#128 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#129 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#130 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#131 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#132 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#133 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#134 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#135 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#136 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#137 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#138 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#139 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#140 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#141 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#142 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#143 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#144 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#145 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#146 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#147 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#148 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#149 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#150 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#151 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#152 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#153 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#154 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#155 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#156 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#157 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#158 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
#159 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1
---Type <return> to continue, or q <return> to quit---
#160 0x00007fffe8ed5a52 in ?? () from /usr/lib/libXcursor.so.1


Additional info:
* package version(s)
mixxx 1.11.0-2

* config and/or log files etc.


Steps to reproduce:
just open and wait
This task depends upon

Closed by  Jan de Groot (JGC)
Wednesday, 18 June 2014, 11:28 GMT
Reason for closing:  Won't fix
Additional comments about closing:  Symlink issue caused by user, not something we should fix.
Comment by Doug Newgard (Scimmia) - Tuesday, 03 June 2014, 15:13 GMT
What version of libxcursor? We just had someone on the forum report that 1.1.14-2 is causing segfaults in a number of programs.
Comment by farid (osc) - Tuesday, 03 June 2014, 15:15 GMT
libxcursor 1.1.14-2

after todays update a lot of programs started crashing.


Comment by Doug Newgard (Scimmia) - Tuesday, 03 June 2014, 15:19 GMT Comment by cfr (cfr42) - Tuesday, 03 June 2014, 17:08 GMT
Is there any chance this is related to the crashes in Kile and Kate (https://bbs.archlinux.org/viewtopic.php?id=182319)? Only I don't see libxcursor actually listed in the output from the seg faults in that case. But for me, at least, the crashes started after upgrading libxcursor etc. (Which might mean that I'm experiencing a different problem from the OP in that thread who updated last week.)
Comment by Jonas Platte (jP_wanN) - Tuesday, 03 June 2014, 17:54 GMT
This was a nasty bug... I was able to work around it by downgrading libxcursor from 1.1.14-2 to 1.1.14-1 as mentioned in the forum.

I can confirm the following programs crashed: chromium (startup), pidgin (when writing in a chat window), lxterminal (startup), skype (after the first seconds of usage)
Comment by farid (osc) - Tuesday, 03 June 2014, 18:22 GMT
basically all the programs that i use... wont start or keep crashing. :/

i cant downgrade since i had removed my cache. hope this gets fixed soon.
Comment by Doug Newgard (Scimmia) - Tuesday, 03 June 2014, 19:03 GMT
Old version can be found here for those that need it:
ftp://seblu.net/archlinux/arm/packages/l/libxcursor/
Comment by Doug Newgard (Scimmia) - Tuesday, 03 June 2014, 19:09 GMT
@cfr, downgrade libxcursor and see. If it fixes it, let us know so we can close your other bug report.
Comment by farid (osc) - Tuesday, 03 June 2014, 19:44 GMT
downgrading fixes the issues
Comment by Andreas Radke (AndyRTR) - Tuesday, 03 June 2014, 20:25 GMT
Do you have the new optdepends "gnome-themes-standard" installed? Maybe it's not actually optional though Fedora does it the same.
Comment by John Ledbetter (ledbettj) - Tuesday, 03 June 2014, 22:17 GMT
I also saw the same crash in xfce4-terminal (among others) with gnome-themes-standard installed. Downgrading libxcursor fixed the issues.
Comment by cfr (cfr42) - Wednesday, 04 June 2014, 02:45 GMT
@Doug Newgard I downgraded libxcursor and it doesn't help with the Kile crashes. That problem unfortunately appears to be independent. (But downgrading libxcursor has stopped Firefox crashing.)
Comment by Allan McRae (Allan) - Wednesday, 04 June 2014, 10:56 GMT
What architecture? I am not having issues on x86_64.
Comment by Marko Biškup (helidium) - Wednesday, 04 June 2014, 12:13 GMT
I am also having segfaults caused by libxcursor, downgrading fixes the issue! It affects google-chrome and xfce4-terminal amongst other...

I am running 64 bit arch.
Comment by Jonas Platte (jP_wanN) - Wednesday, 04 June 2014, 14:19 GMT
I have a x86_64 system too. Intel Haswell, no seperate graphics... If that matters.
Comment by cfr (cfr42) - Wednesday, 04 June 2014, 14:23 GMT
x86_64. No separate graphics.
Comment by Jan de Groot (JGC) - Wednesday, 04 June 2014, 15:00 GMT
Does removing /usr/share/icons/default/index.theme fix the problem?
Comment by Jonas Platte (jP_wanN) - Wednesday, 04 June 2014, 15:12 GMT
JGC: It does! and it doesn't seem to break anything else.
Comment by farid (osc) - Wednesday, 04 June 2014, 15:31 GMT
[edit]

i just updated and didnt remove anything and firefox worked fine.

others programs like mixxx and clementine kept crashing. going to remove and test.

cheers
Comment by Marko Biškup (helidium) - Wednesday, 04 June 2014, 16:43 GMT
Removing index.theme seems to work for me too.

Thank you,
Comment by Eugene R. Miller (the7erm) - Thursday, 05 June 2014, 07:19 GMT
I moved ~/.icons to ~/.icons.bak and some things started working, but after loading a few programs like keepassx it kept crashing. Reverted back to 14-1 and everything is working again.

I also noticed that systemd's cpu usage goes off the charts when 14-2 is installed. Something that's scaring me is my laptop is starting to feel warm to the touch since this last round of updates, and this never happens. Usually I don't notice it.

Comment by satorik (satorik) - Thursday, 05 June 2014, 08:38 GMT
Okay... I registered just to post this. I hope it helps.

I have experienced the same bug. I compiled libxcursor with the debug symbols.

This is the traceback. It appears that the cursor when a mouseover event over a horizontal split (in this case: split_h) cannot be found and is ultimately to blame for this particular segfault. There is no such cursor in the directory of the theme (/usr/share/icons/Adwaita/cursors).

So maybe the new inherit theme which was introduced in the index.theme is to blame.

The result is a segfault (vlc is the application with which the segfault occurs).

Good luck!
Comment by Jan de Groot (JGC) - Thursday, 05 June 2014, 09:30 GMT
Looks like infinite inherits recursion, reported here in 2005 and still valid:
https://bugs.freedesktop.org/show_bug.cgi?id=3603

Don't know why Fedora doesn't hit this though.

Every theme has a fallback to the default theme. Libxcursor 1.1.14-2 adds a fallback to Adwaita for the default theme, meaning that if some theme is missing a cursor, it will take the fallback from Adwaita. This fixes bugs with some applications that crash or have undefined behaviour when a cursor doesn't exist in the theme (this is what happens with mutter/gnome-shell with custom themes which aren't complete).

What happens here is that a cursor is requested which isn't in Adwaita. Libxcursor will fallback to the default theme, which has a fallback to Adwaita, which doesn't have the cursor, so it goes to default again. What we created here is a circular inheritance when a requested cursor doesn't exist in Adwaita.

Libxcursor will just recurse until stack overflows. This is why CPU usage is higher than before and why it crashes inside glibc. I'll have a look at the upstream patch later tonight, probably it will get a recursion depth limit and a special case where a fallback from default to some other theme will not recurse back into the default theme.
Comment by satorik (satorik) - Thursday, 05 June 2014, 09:49 GMT
Jan, I think you are correct. I was also thinking something along these lines wrt to the issue.

Regarding the CPU usage, I have noticed that journald also hits high cpu as it writes to the journal upon a segfault (this is just an observation). Unfortunately, I downgraded so I can provide further data only if really neaded.

Eitherway, a default cursor theme (outside the recursive theme enumeration suggested in the patch) looks sensible to me. Or even simpler: just a default theme with libxcursor that covers all bases.

Thanks for supporting the package.
Comment by Thiago Perrotta (thiagowfx) - Friday, 06 June 2014, 02:20 GMT
Hi, I'm using the 1.1.14-2 version but I'm not experiencing any of the problems / crashes mentioned here. Anything I could do to reproduce it?
I'm not using the Adwaita theme.
Comment by satorik (satorik) - Friday, 06 June 2014, 06:51 GMT
Thiago,

I think Jan said it best:

> What happens here is that a cursor is requested which isn't in Adwaita. Libxcursor will fallback to the default theme, which has a fallback to Adwaita, which doesn't have the cursor, so it goes to default again. What we created here is a circular inheritance when a requested cursor doesn't exist in Adwaita.

> Libxcursor will just recurse until stack overflows

So I would surmise that if you don't have any other theme but Adwaita installed and open an application that requests (in my case) a pointer icon, which is not present in the Adwaita theme, the bug should be reproduced. Otherwise it is lurking somewhere else :-)

I also think that the bug should be reproducible for any theme variation or set of themes which do not enumerate exhaustively the resource in question. It is just so that the probability of unsuccessful enumeration decreases over the set of shared resources of all installed themes.
Comment by Marcus Radisch (amarradi) - Friday, 06 June 2014, 10:18 GMT
Hello,

i've also the problem that some programs crashed. Here are my Ticket https://bugs.archlinux.org/task/40730.
I traced some programs and added into the Ticket.

Marcus
Comment by Thiago Perrotta (thiagowfx) - Friday, 06 June 2014, 15:15 GMT
satorik,

Thanks for pointing me to Jan's explanation. I think I've read it too quickly before, but now it makes sense. I'm using Numix-ArchBlue with the Human (from Ubuntu, available in the aur) cursor theme.
Comment by Marcus Radisch (amarradi) - Friday, 06 June 2014, 15:31 GMT
Now i have a stupid question.
Uses every desktop this library? Can i work on an other desktop. I need my notebook to work the next days.

Greetings Marcus
Comment by Thiago Perrotta (thiagowfx) - Friday, 06 June 2014, 15:34 GMT
Marcus, try installing the two themes I mentioned in my previous post, then apply them with lxappearance, just to see if your desktop will crash. I believe only the Human cursor theme is necessary -- probably the GTK theme has nothing to do with the cursor one.
Comment by Marcus Radisch (amarradi) - Friday, 06 June 2014, 15:57 GMT
Thanks Thiago, this workaround works in my case
Comment by Andre (Learning) - Saturday, 07 June 2014, 00:06 GMT
it's all related to this..
Perl updated to 5.20

2014-06-04

Perl 5.20, as any other new perl version, requires all modules that are not purely perl code to be rebuilt. We did that for all packages in our repos.

The last couple major updates printed an error message when trying to load modules built against the wrong version, 5.20 seems to cause segfaults. Please make sure to rebuild all custom installed CPAN modules and binaries that link to libperl.so. """"<<< + extra stuff that is not linked well like libxcursor etc that is all now turning out Segmentation fault errors""
add testing for faster fix access or check/list before update on what it is depended on that way you can plan ahead if you should update(work around it) & won't get hit by unspected errors ;)

Refer to my post on arch-dev-public for a script that helps to find those packages.
Comment by Doug Newgard (Scimmia) - Saturday, 07 June 2014, 03:26 GMT
No, Learning, it has nothing to do with that at all.
Comment by Eugenio M. Vigo (emvigo) - Saturday, 07 June 2014, 18:19 GMT
After days ignoring the 1.1.14-2 update, I've applied it today. I have no misbehavior to report yet. I'm using KDE in a x86_64 system, *without* gnome-themes-standard installed, and using oxygen-gtk for GTK+ apps (both GTK+2 and GTK+3). I've tried using Kate, Firefox, etc. and everything works as should or so it seems. I hope these data may be of help for you, guys.
Comment by Eugene R. Miller (the7erm) - Sunday, 08 June 2014, 03:49 GMT
I'm running XFCE if that helps, but I tried running gnome3, and that also had issues with nothing starting.

The only program that was even remotely stable was firefox and xterm

xfce-terminal crashed
whisker's menu crashed
terminator crashed
skype crashed
pidgin crashed

I don't think I have any kde/qt programs installed beyond kid3.

Is this bug happening only to people who don't have KDE installed?
Comment by Giovanni Santini (ItachiSan) - Sunday, 08 June 2014, 09:50 GMT
I can confirm that downgrading the package to the previous version (in ARM) makes Chromium working.
If using last version, Chromium crashes every time.
Edit:
Seems also that Steam started working again. Yuppie :D
Comment by Philip Sequeira (qmega) - Sunday, 08 June 2014, 16:18 GMT
> Is this bug happening only to people who don't have KDE installed?

No, I have a lot of KDE stuff installed and I'm still affected. In fact, KWin is one of the things that crashes for me with libxcursor 1.1.14-2 installed.
Comment by Petre (petre) - Monday, 09 June 2014, 12:44 GMT
downgraded for now...
Comment by Jan de Groot (JGC) - Tuesday, 10 June 2014, 14:50 GMT
I've been studying these backtraces a bit, but what's really weird here:

open("/usr/share/icons/default/index.theme", O_RDONLY) = 62
read(62, "[Icon Theme]\nInherits=Adwaita\n", 4096) = 30
...
open("/usr/share/icons/Adwaita/index.theme", O_RDONLY) = 62
read(62, "[Icon Theme]\nInherits=Adwaita\n", 4096) = 30


I've also been studying the sources a bit, libxcursor will not go into loop unless tricked. Code is as following:

- lookup file from theme
- if no icon, lookup file from default theme

Inside lookup function:
- if no icon, look in inherits. This never traverses "default"
- if not in inherits, return NULL.

People who are affected have symlinked /usr/share/icons/Adwaita to /usr/share/icons/default. The Adwaita icon theme doesn't have a theme index file, so by upgrading to the new xcursor, this placed a nice index.theme file into /usr/share/icons/Adwaita, referencing itself.

This is simply a user error, this is not a packaging bug or library bug.
Comment by Philip Sequeira (qmega) - Tuesday, 10 June 2014, 17:08 GMT
> People who are affected have symlinked /usr/share/icons/Adwaita to /usr/share/icons/default.

Yep, I had done that. Removing the symlink before upgrading fixes the problem for me. I feel pretty stupid now...
Comment by Guillermo Luis Exposito (glexposito) - Tuesday, 10 June 2014, 17:39 GMT
Hi All, Thanks for your help!
So, we should remove the symlink /usr/share/icons/default to fix the issue. Right?
Comment by Giovanni Santini (ItachiSan) - Tuesday, 10 June 2014, 18:00 GMT
Exactly, it worked for me.
I think it should be somewhere also on the Wiki for the noobs like me :P
Comment by Doug Newgard (Scimmia) - Tuesday, 10 June 2014, 18:04 GMT
No, I believe JGC is saying that you need to remove the /usr/share/icons/Adwaita symlink that you put there. Creating a symlink like that behind pacman's back can cause problems.

Wait, that doesn't make sense, either, but that what "symlinked /usr/share/icons/Adwaita to /usr/share/icons/default" seems to say.
Comment by Guillermo Luis Exposito (glexposito) - Tuesday, 10 June 2014, 18:11 GMT
I am truly sorry. I am a little confused. I understood that we should remove the soft link from /usr/share/icons/Adwaita to /usr/share/icons/default.
To clarify even more, I mean "sudo rm /usr/share/icons/default" and after that we should perform the upgrade. Am I right?
Comment by Philip Sequeira (qmega) - Tuesday, 10 June 2014, 19:00 GMT
> No, I believe JGC is saying that you need to remove the /usr/share/icons/Adwaita symlink that you put there. Creating a symlink like that behind pacman's back can cause problems.
> Wait, that doesn't make sense, either, but that what "symlinked /usr/share/icons/Adwaita to /usr/share/icons/default" seems to say.

Other way around. He gave them in the order you'd give them to ln -s, but it's the second argument (default) that points to the first (Adwaita).

> To clarify even more, I mean "sudo rm /usr/share/icons/default" and after that we should perform the upgrade. Am I right?

Yes.
Comment by Eugene R. Miller (the7erm) - Tuesday, 10 June 2014, 19:40 GMT
I don't think I added the sym link. I appears I have one for default.kde4 in there as well.

I can confirm (at least on my system) `sudo rm /usr/share/icons/default` appears to have worked.

Loading...