FS#17081 - [gtk2] seems to be broken after pacman update

Attached to Project: Arch Linux
Opened by Tobias Kieslich (tobias) - Monday, 09 November 2009, 18:36 GMT
Last edited by Jan de Groot (JGC) - Saturday, 21 November 2009, 16:32 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description: Updating my workbox this morning made every single gtk2 dependent application segfault


Additional info:
* package version(s) 2.18.3-2 x86_64
* config and/or log files etc.


Steps to reproduce: For me it was reopen my xfce4 desktop. After loging into openbox, firefox faild, pidgin failed, rox faild etc

Recompiling the updated package helped the case for me
This task depends upon

Closed by  Jan de Groot (JGC)
Saturday, 21 November 2009, 16:32 GMT
Reason for closing:  Works for me
Comment by Jan de Groot (JGC) - Tuesday, 10 November 2009, 08:18 GMT
Can you debug this a bit further? I can't reproduce the crashes.
Comment by Tobias Kieslich (tobias) - Tuesday, 10 November 2009, 16:55 GMT
Hi JGC,

yeah, I meant to come back to this bug last night. My home box(64bit) worked fine after the upgrade, it was just the box at work which had trouble. There are two things I can imagine happened:
- my package downloaded from the locke mirror was rotten (should have been caught by checksum)
- the ldconfig after the first pacman -Syu screwed up; that's a crapshoot dunno if that would result in segfaults
Anyway, I have the package still in the package cache and will try some playing around also get it to home try it there.

Oh, and since I'm the only one who encountered it, feel free to bring the severity down.
Comment by Tobias Kieslich (tobias) - Wednesday, 11 November 2009, 17:23 GMT
Okay I retried it. I reinstalled gtk2 from the mirrors and this time it worked. I have no clue what went wrong the first time. I even installed the package I downloaded in the first place and that worked as well. I have no clue what went wrong with the first update...

So, from my side that can be closed. I can't reproduce it, even with the very file involved in the first place. Maybe the pacman people have insight if something during an update can trigger such behaviour ....

Loading...