After the upgrade to 1.12.10, claws-mail locks up at start without completing drawing the window; app is not useable in this state.
Additionally, thunar has sometimes problems rendering it's icons, can be solved by scrolling or refresh.
Neither problem existed before and downgrading cairo to 1.12.8 fixes it for me.
Steps to Reproduce:
1. emerge =cairo-1.12.10
for me it's major, thus setting severity to it.
> for me it's major,...
Anyway, check bug 454108.
Same here with thunar. But claws-mail works fine for me.
(In reply to comment #1)
> > for me it's major,...
> Anyway, check bug 454108.
Seen that, doesn't solve anything for me.
Can you try to run the applications with `strace -f` and attach the resulting logs?
It might be it is not an I/O related problem, in which case you can run them with gdb and have the relevant packages compiled with debug symbols, once they hang interrupt them (CTRL+C) and inspect the backtrace by typing backtrace.
I think this is could be a duplicate of bug 454108.
Created attachment 337110 [details]
strace -f claws-mail
As requested, here is a gzipped strace-f of claws-mail. ^C didn't work, so had to kill it from another terminal.
If you also need something for thunar, let me know. It's not unusable bad right now, but I'll notice.
First interesting thing would be which of the issues still exist with 1.12.10-r1
claws doesn't render it's interface and locks up to an unusable state, can only be force killed.
thunar still has problems rendering some document icons, to be specific, it seems like only thumbnail icons (i.e. from office-docs) are affected, not general purpose icons like for .mp3 or .png.
Please provide a screenshot of thunar image corruption with 1.12.10-r1 (and from 1.12.10 if it is any different)
Created attachment 337124 [details]
thunar rendering issues
screenshot of thunar as requested, filenames redacted
Taking back my comment from above, affecting definetly more icon types.
Restarting thunar sometimes affects other icons and the ones currently not rendered correctly are fine, I don't see a pattern.
I confirm the problems reported in thunar with cairo-1.12.10. Downgrading to 1.12.8 solves the problems.
I first suspected this to be a problem with the graphics card drivers (r600 git, mesa git, linux-3.7.3). Maybe cairo-1.12.10 now uses hardware acceleration for rendering some stuff which cairo-1.12.8 didn't.
(In reply to comment #13)
> I first suspected this to be a problem with the graphics card drivers (r600
> git, mesa git, linux-3.7.3). Maybe cairo-1.12.10 now uses hardware
> acceleration for rendering some stuff which cairo-1.12.8 didn't.
Dunno, but could be, thus: gentoo-sources-3.7.3, nvidia-drivers-313.18
It doesn't happen on a r600 with CAYMAN chip and kernel-3.6.11.
I stand corrected. It happens with r600 on CAYMAN too.
https://bugs.gentoo.org/show_bug.cgi?id=454468 fixed the corruption in thunar, but claws still doesn't work, thus still forced to mask >1.12.8
Does it still exist with 1.12.12?
(In reply to comment #18)
> Does it still exist with 1.12.12?
Yes, problem still there.
Currently in the process of running `emerge -e claws-mail`, doubt that will help, though.
(In reply to comment #19)
> (In reply to comment #18)
> > Does it still exist with 1.12.12?
> Yes, problem still there.
> Currently in the process of running `emerge -e claws-mail`, doubt that will
> help, though.
Okay, seems like it's time to file a bug upstream at bugs.freedesktop.org.
(In reply to comment #20)
> Okay, seems like it's time to file a bug upstream at bugs.freedesktop.org.
Would I need to do that or can some @Gentoo-dev do that? Not really motivated to create and monitor yet another account :/
Regarding the `emerge -e claws-mail` run, as expected, it didn't help, neither does pulling and building the latest CVS snapshot of claws.
Upstream says that a gdb backtrace of claws would be useful.
Created attachment 338156 [details]
Hope I've done that right:
- recompiled with -O1 and taking care of the other flags in your linked guide
- `gdb /usr/bin/claws-mail`
- set logging file foo
- set logging on
- ^C (since nothing else was doable with claws)
- thread apply all bt full
If that's the wrong way or I also need to compile every dep with debug-stuff, please tell me/give detailed info.
(In reply to comment #23)
> Created attachment 338156 [details]
> gdb backtrace
> Hope I've done that right:
> - recompiled with -O1 and taking care of the other flags in your linked guide
> - `gdb /usr/bin/claws-mail`
> - set logging file foo
> - set logging on
> - run
> - ^C (since nothing else was doable with claws)
> - thread apply all bt full
> - quit
> If that's the wrong way or I also need to compile every dep with
> debug-stuff, please tell me/give detailed info.
Yeah, we probably need debug symbols.
The best way to do this is to add
and add -g or -ggdb to your CFLAGS and then remerge
gtk+:2 glib pango cairo gobject-introspection claws-mail
Then the backtrace should have a lot more information.
Created attachment 338180 [details]
Same procedure as above, except for the changes and rebuilds you suggest.
OT, wondering if I'm the only ~amd64 user of claws :p
I needed to make a complete new install of the whole system, back on ~amd64 now and copied over my .claws-mail, it's working again.
So I'm guessing, some dep was broken but not listed to be rebuilt or something. Anyway, fixed for me, thus closing, sry for the inconvenience.