Summary: | x11-terms/terminal-0.4.8 sometimes looses GUI interface (Gtk-CRITICAL error) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Sergey S. Starikoff <Ikonta> |
Component: | Current packages | Assignee: | XFCE Team <xfce> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
URL: | https://bugzilla.xfce.org/show_bug.cgi?id=8370 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Sergey S. Starikoff
2012-01-23 07:15:26 UTC
Reported upstream. Link attached. This might sound "stupid", but please try: - With a new user, as in with empty home directory to exclude possibility of broken themes, gtkrc files, etc. - Try `emerge -eva x11-terms/terminal`, as in, rebuild the dependencies (deep) of terminal and then terminal itself. Then if the problem persists, it's worth to put some time into this ... not before. (In reply to comment #2) > This might sound "stupid", but please try: > > - With a new user, as in with empty home directory to exclude possibility of > broken themes, gtkrc files, etc. > > - Try `emerge -eva x11-terms/terminal`, as in, rebuild the dependencies (deep) > of terminal and then terminal itself. > > Then if the problem persists, it's worth to put some time into this ... not > before. It is not stupid. Thank you for remind. About checking for reproduceability with clean profile I'm not shure: the bug appears not so often (and is not user-willingly reproducable): I'm not shure, that it will be pissible to work in clean profile until it appears (or not). Anywhere, the issue only could be modified to the question of hadnling existing profiles. While reading logs I've find that this bug looks similiarly with #387117 (the difference is in that icecat unlike terminal don't becomes unavailable for window close command of window manager). The issue with terminal I've find first 12.01.2012 (after system update 11.01.2012). But the ussue with IceCat browser is much more old (at least several months). Now I'm rebuilding terminal with all dependencies (emerge -e x11-terms/terminal). It looks strange, that portage have find some packages to be newly installed: ... [ebuild N ] virtual/perl-File-Temp-0.220.0-r1 0 kB [ebuild N ] perl-core/version-0.940.0 103 kB [ebuild N ] perl-core/Perl-OSType-1.2.0 USE="-test" 12 kB [ebuild N ] perl-core/JSON-PP-2.272.0 41 kB [ebuild N ] perl-core/CPAN-Meta-YAML-0.4.0 29 kB [ebuild N ] virtual/perl-version-0.940.0 0 kB [ebuild N ] virtual/perl-JSON-PP-2.272.0 0 kB [ebuild N ] virtual/perl-CPAN-Meta-YAML-0.4.0 0 kB [ebuild N ] virtual/perl-Perl-OSType-1.2.0 0 kB [ebuild N ] perl-core/Module-Metadata-1.0.6 23 kB [ebuild N ] perl-core/Parse-CPAN-Meta-1.440.100 8 kB [ebuild N ] perl-core/Version-Requirements-0.101.20 15 kB [ebuild N ] virtual/perl-Parse-CPAN-Meta-1.440.100-r2 0 kB [ebuild N ] virtual/perl-Module-Metadata-1.0.6 0 kB [ebuild N ] virtual/perl-Version-Requirements-0.101.20-r2 0 kB [ebuild N ] perl-core/CPAN-Meta-2.112.621 75 kB [ebuild N ] virtual/perl-CPAN-Meta-2.112.621 0 kB ... (In reply to comment #2) > - Try `emerge -eva x11-terms/terminal`, as in, rebuild the dependencies (deep) > of terminal and then terminal itself. > Doing so seems to solve the issue, in about a week the bug doesn't appeared. (In reply to comment #4) > (In reply to comment #2) > > - Try `emerge -eva x11-terms/terminal`, as in, rebuild the dependencies (deep) > > of terminal and then terminal itself. > > > Doing so seems to solve the issue, in about a week the bug doesn't appeared. right, so let's just assume one of the dependencies was broken and rebuilding fixed it. in any case, it's impossible to trace it now :) closing (In reply to comment #5) > so let's just assume one of the dependencies was broken and rebuilding > fixed it. in any case, it's impossible to trace it now :) > It is so. But I think it's a time to point a question about exploring such issue. For future development. Because normally terminal was to be fixed by revdep-rebuild, nor emerge -e (In reply to comment #6) > (In reply to comment #5) > > so let's just assume one of the dependencies was broken and rebuilding > > fixed it. in any case, it's impossible to trace it now :) > > > It is so. > But I think it's a time to point a question about exploring such issue. For > future development. > Because normally terminal was to be fixed by revdep-rebuild, nor emerge -e umm, you are way overestimating the capabilities of revdep-rebuild... it's not a magic bullet ;-) |