[opensuse-factory] Thunderbird and Firefox not working, Dolphin and stopping via KDE-menu very slow
Hi, After a fresh install of RC1 (and emptying .kde and .kde4) firefox and thunderbird are not working. Both show (process:4432): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed when started from the command line. There are several posts (also very recent ones) on various ml's about this error message for FF and TB, but none on opensuse (and none with a solution which works for me). After first start of FF, the FF-window appears, with the entries on the main menu, but without the corresponding icons. Starting it a second - or third, fourth etc.) the icons appear also, and a subwindow which lists the sessions that could not be opened (which is all sessions). No input is taken from mouse or keyboard, and also closing the window does not work (intil KDE kicks in). Also - but maybe not related - some applications are very, very slow starting up. For example to start dolphin it takes 75 secs. To restart or shutdown from the KDE menu it takes 2 minutes for the little stop-menu to appear, and another 75 secs before the real shutdown is started after choosing restart or shutdown. Shutdown as root from a terminal has it's normal speed. What can be going on here? regards, Jogchum -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wed, 2013-10-30 at 21:25 +0100, Jogchum Reitsma wrote:
Hi,
After a fresh install of RC1 (and emptying .kde and .kde4) firefox and thunderbird are not working. Both show
(process:4432): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
This is https://bugzilla.mozilla.org/show_bug.cgi?id=672671
Whereas it's annoying, it is not known to cause any crashes or
malfunction.
Not helpful, I know, but it should be indicative to not focus on this
specific occurrence.
Dominique
--
Dimstar / Dominique Leuenberger
On Wed, 2013-10-30 at 21:34 +0100, Dimstar / Dominique Leuenberger wrote:
On Wed, 2013-10-30 at 21:25 +0100, Jogchum Reitsma wrote:
Hi,
After a fresh install of RC1 (and emptying .kde and .kde4) firefox and thunderbird are not working. Both show
(process:4432): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
This is https://bugzilla.mozilla.org/show_bug.cgi?id=672671 Whereas it's annoying, it is not known to cause any crashes or malfunction.
Correction.. it should have been
https://bugzilla.mozilla.org/show_bug.cgi?id=833117
--
Dimstar / Dominique Leuenberger
op 30-10-13 21:35, Dimstar / Dominique Leuenberger schreef:
On Wed, 2013-10-30 at 21:34 +0100, Dimstar / Dominique Leuenberger wrote:
On Wed, 2013-10-30 at 21:25 +0100, Jogchum Reitsma wrote:
Hi,
After a fresh install of RC1 (and emptying .kde and .kde4) firefox and thunderbird are not working. Both show
(process:4432): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed This is https://bugzilla.mozilla.org/show_bug.cgi?id=672671 Whereas it's annoying, it is not known to cause any crashes or malfunction. Correction.. it should have been https://bugzilla.mozilla.org/show_bug.cgi?id=833117
Well, I call it more than annoying, for both FF and TB refuse to do anything besides opening the main window. The workaround on https://bugzilla.mozilla.org/show_bug.cgi?id=833117(namely to start with env variable G_SLICE=always-malloc) does not change a thing in my case. And, AFAICS I'm not the only one (though, as stated, I didn't see postings with opensuseas os) Jogchum -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 30/10/13 22:31, Jogchum Reitsma wrote:
op 30-10-13 21:35, Dimstar / Dominique Leuenberger schreef:
On Wed, 2013-10-30 at 21:34 +0100, Dimstar / Dominique Leuenberger wrote:
On Wed, 2013-10-30 at 21:25 +0100, Jogchum Reitsma wrote:
Hi,
After a fresh install of RC1 (and emptying .kde and .kde4) firefox and thunderbird are not working. Both show
(process:4432): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed This is https://bugzilla.mozilla.org/show_bug.cgi?id=672671 Whereas it's annoying, it is not known to cause any crashes or malfunction. Correction.. it should have been https://bugzilla.mozilla.org/show_bug.cgi?id=833117
Well, I call it more than annoying, for both FF and TB refuse to do anything besides opening the main window. The workaround on https://bugzilla.mozilla.org/show_bug.cgi?id=833117(namely to start with env variable G_SLICE=always-malloc) does not change a thing in my case.
And, AFAICS I'm not the only one (though, as stated, I didn't see postings with opensuseas os)
Jogchum I installed RC1 on my wife's (and my own) computer and FF and TB both behave as they have done in past years: working perfectly.
When you state, "After a fresh install of RC1 (and emptying .kde and .kde4)", what do you mean by "emptying .kde and .kde4"? When you do a clean, fresh, install .kde4 is created afresh anyway so you don't have to "empty" anything. BC -- Using openSUSE 13.1, KDE 4.11.2 & kernel 3.11.6-3 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 OC 2GB DDR5 GPU -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2013-10-31 at 00:50 -0000, Basil Chupin wrote:
When you state, "After a fresh install of RC1 (and emptying .kde and .kde4)", what do you mean by "emptying .kde and .kde4"? When you do a clean, fresh, install .kde4 is created afresh anyway so you don't have to "empty" anything.
Unless it is a fresh install with an old home. It is reused, not formatted. Many people call that "fresh install" to diferentiate from "upgrade". Jogchum, try a new user. - -- Cheers, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlJyI1cACgkQtTMYHG2NR9XqMgCeKGCBYpYfkIQHt0FWuQXWrRSl lKMAn0fuyLGkM2m9Re7Y6g1ezZJT8Q+3 =Y7m8 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
op 31-10-13 10:31, Carlos E. R. schreef:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Thursday, 2013-10-31 at 00:50 -0000, Basil Chupin wrote:
When you state, "After a fresh install of RC1 (and emptying .kde and .kde4)", what do you mean by "emptying .kde and .kde4"? When you do a clean, fresh, install .kde4 is created afresh anyway so you don't have to "empty" anything.
Unless it is a fresh install with an old home. It is reused, not formatted. Many people call that "fresh install" to diferentiate from "upgrade".
Jogchum, try a new user.
- -- Cheers, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux)
iEYEARECAAYFAlJyI1cACgkQtTMYHG2NR9XqMgCeKGCBYpYfkIQHt0FWuQXWrRSl lKMAn0fuyLGkM2m9Re7Y6g1ezZJT8Q+3 =Y7m8 -----END PGP SIGNATURE----- It is indeed a fresh install - with new formatted root and boot - with an old home. After all, that's the condition my production system will be upgraded, so that's what I want to test.
I tried another, existing user, and created a totally new one: both with the same results. The only difference is that with the new user dolphin does not take 75, but 25 seconds to start. The rest of the behaviour is the same. Jogchum -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
op 31-10-13 10:31, Carlos E. R. schreef:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Thursday, 2013-10-31 at 00:50 -0000, Basil Chupin wrote:
When you state, "After a fresh install of RC1 (and emptying .kde and .kde4)", what do you mean by "emptying .kde and .kde4"? When you do a clean, fresh, install .kde4 is created afresh anyway so you don't have to "empty" anything.
Unless it is a fresh install with an old home. It is reused, not formatted. Many people call that "fresh install" to diferentiate from "upgrade".
Jogchum, try a new user.
- -- Cheers, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux)
iEYEARECAAYFAlJyI1cACgkQtTMYHG2NR9XqMgCeKGCBYpYfkIQHt0FWuQXWrRSl lKMAn0fuyLGkM2m9Re7Y6g1ezZJT8Q+3 =Y7m8 -----END PGP SIGNATURE----- A few days have gone since my last reply. As it is, 13.1 RC1 is unusable for production for me. Is it usefull to enter a bugreport against RC1, or is it wiser to upgrade to RC2 and see what happens?
regards, Jogchum -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hello, Am Sonntag, 3. November 2013 schrieb Jogchum Reitsma:
A few days have gone since my last reply. As it is, 13.1 RC1 is unusable for production for me. Is it usefull to enter a bugreport against RC1, or is it wiser to upgrade to RC2 and see what happens?
Bugreports against RC2 are of course better. OTOH, getting a bugreport as fast as possible is is also an important goal - the goldmaster deadline is very near. If you can upgrade to RC2 quickly, do it. Otherwise a bugreport against RC1 is also OK IMHO - and better than no bugreport at all. (Worst thing that can happen is that you get a reply saying it's already fixed ;-) Regards, Christian Boltz -- Why should I read the fucking manual? I know how to fuck! -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
op 03-11-13 20:54, Christian Boltz schreef:
Hello,
Am Sonntag, 3. November 2013 schrieb Jogchum Reitsma:
A few days have gone since my last reply. As it is, 13.1 RC1 is unusable for production for me. Is it usefull to enter a bugreport against RC1, or is it wiser to upgrade to RC2 and see what happens? Bugreports against RC2 are of course better. OTOH, getting a bugreport as fast as possible is is also an important goal - the goldmaster deadline is very near.
If you can upgrade to RC2 quickly, do it.
Otherwise a bugreport against RC1 is also OK IMHO - and better than no bugreport at all. (Worst thing that can happen is that you get a reply saying it's already fixed ;-)
Regards,
Christian Boltz
Upgrading to RC2 didn't change a thing, entered bug 848883 Regards, Jogchum -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
op 03-11-13 20:54, Christian Boltz schreef:
Hello,
Am Sonntag, 3. November 2013 schrieb Jogchum Reitsma:
A few days have gone since my last reply. As it is, 13.1 RC1 is unusable for production for me. Is it usefull to enter a bugreport against RC1, or is it wiser to upgrade to RC2 and see what happens? Bugreports against RC2 are of course better. OTOH, getting a bugreport as fast as possible is is also an important goal - the goldmaster deadline is very near.
If you can upgrade to RC2 quickly, do it.
Otherwise a bugreport against RC1 is also OK IMHO - and better than no bugreport at all. (Worst thing that can happen is that you get a reply saying it's already fixed ;-)
Regards,
Christian Boltz Hmm - how about getting no reaction at all? For me, this bug is a showstopper. Thunderbird and Firefox are completely unusable, Dolphin and more almost unusable because of their slowness.
regards, Jogchum -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2013-11-09 08:41 (GMT+0100) Jogchum Reitsma composed:
Hmm - how about getting no reaction at all? For me, this bug is a showstopper. Thunderbird and Firefox are completely unusable, Dolphin and more almost unusable because of their slowness.
Have you tried booting the old kernel stanza to see if it makes a difference? None of my systems have slowed down by upgrading beyond RC1, but I've only done mine via zypper dup, and have only ever opened Dolphin once, and not on one of my own systems. Maybe what's wrong is hardware is failing. Have you tried reseating RAM, running memtest, checking for bad caps[1], or anything else hardware related? [1] http://en.wikipedia.org/wiki/Capacitor_plague -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
op 09-11-13 09:03, Felix Miata schreef:
On 2013-11-09 08:41 (GMT+0100) Jogchum Reitsma composed:
Hmm - how about getting no reaction at all? For me, this bug is a showstopper. Thunderbird and Firefox are completely unusable, Dolphin and more almost unusable because of their slowness.
Have you tried booting the old kernel stanza to see if it makes a difference? None of my systems have slowed down by upgrading beyond RC1, but I've only done mine via zypper dup, and have only ever opened Dolphin once, and not on one of my own systems. Maybe what's wrong is hardware is failing. Have you tried reseating RAM, running memtest, checking for bad caps[1], or anything else hardware related?
[1] http://en.wikipedia.org/wiki/Capacitor_plague I'm not sure if I understand correctly what you mean by ¨booting the old kernel stanza" - you mean 12.3?
12.3 runs without problems on the same system as 13.1RC2, the only difference being 13.1 residing on another disk, with it's own home partition on that same disk. So hardware trouble seems unlikely. Apart from that, the motherboard is from Gigabyte, who gives special attention to its capacitors, so I doubt that is an issue here. Since I seem to be the only one with this problem, it could well be some peculiarity on my side, but what, and how to determine that? I lack sufficient expertise to find that out on my own. Of course I can upgrade to GM and then to final when these arrive, and see what happens. But upgrading from RC1 to RC2 didn't help. Thanks! regards, Jogchum -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2013-11-09 11:53 (GMT+0100) Jogchum Reitsma composed:
I'm not sure if I understand correctly what you mean by ¨booting the old kernel stanza" - you mean 12.3?
Recent openSUSE versions have multiversion enabled by default for kernel. That means RC2 installations running 3.11.6 that reached RC2 via zypper or YaST upgrade from RC1 should still have 3.11.3 installed.
the motherboard is from Gigabyte, who gives special attention to its capacitors, so I doubt that is an issue here.
Power supplies use capacitors too.
Of course I can upgrade to GM and then to final when these arrive, and see what happens. But upgrading from RC1 to RC2 didn't help.
Are updates being held back pending official release announcement? If not, try checking for updates and upgrading when you find any involving KDE and/or Xorg. Did you have the same trouble when you tried M4 or earlier or Beta? Have you checked to see if the Xorg driver used is made for your gfxchip rather than a generic FBDEV or VESA? Is swap being touched more than nominally? Have you checked top to see if some/what process is gobbling resources? Have you tried hdparm to see if HD is running full speed? Do you have older installation media still? If so, try removing current TB & FF and installing the older versions. If not, or in addition, try running the binaries from mozilla.org instead. Does Dolphin have the same KHTML vs. WebKit engine option that Konq has? If so, try switching to the other. You could try installing RC2 again, but starting minimal, and adding packages until an addition causes recreation of your problem, if that ever happens. You could try global bling disable to see if it helps. Put somewhere in /etc/X11/xorg.conf* the following: Section "Extensions" Option "Composite" "Disable" EndSection Try shutting down nepomuk. I do it out of habit by putting these files in ~/.kde4/share/config/ before ever starting a new KDE user the first time: # nepomukserverrc: [$Version] update_info=nepomukstrigiservice-migrate.upd:nepomukstrigiservice-migrate [Basic Settings] Start Nepomuk=false [main Settings] Storage Dir[$e]=$HOME/.kde4/share/apps/nepomuk/repository/main/ Used Soprano Backend=null rebuilt index for type indexing=false [Service-nepomukstrigiservice] autostart=false # nepomukstrigirc: [General] exclude filters=autom4te,*.rcore,CTestTestfile.cmake,*.o,*.omf,.hg,*.m4,*.orig,moc_*.cpp,conftest,.xsession-errors*,CMakeTmpQmake,*.tmp,po,.svn,.histfile.*,lzo,.bzr,.git,litmain.sh,cmake_install.cmake,CMakeFiles,*.pc,*.nvram,*.elc,*.la,CMakeCache.txt,confdefs.h,*.gmo,*.csproj,*.rej,config.status,lost+found,confstat,*.pyc,_darcs,CVS,*.part,libtool,*.aux,*.po,CMakeTmp,Makefile.am,*.lo,*.loT,*~,*.moc,*.vm*,*.class,core-dumps exclude filters version=2 folders[$e]=$HOME/tmp/null index hidden folders=false index newly mounted=false -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
op 09-11-13 12:37, Felix Miata schreef:
Are updates being held back pending official release announcement? If not, try checking for updates and upgrading when you find any involving KDE and/or Xorg.
Did you have the same trouble when you tried M4 or earlier or Beta?
Have you checked to see if the Xorg driver used is made for your gfxchip rather than a generic FBDEV or VESA?
Is swap being touched more than nominally?
Have you checked top to see if some/what process is gobbling resources?
Have you tried hdparm to see if HD is running full speed?
Do you have older installation media still? If so, try removing current TB & FF and installing the older versions. If not, or in addition, try running the binaries from mozilla.org instead.
Does Dolphin have the same KHTML vs. WebKit engine option that Konq has? If so, try switching to the other.
You could try installing RC2 again, but starting minimal, and adding packages until an addition causes recreation of your problem, if that ever happens.
You could try global bling disable to see if it helps. Put somewhere in /etc/X11/xorg.conf* the following:
Section "Extensions" Option "Composite" "Disable" EndSection
Try shutting down nepomuk. I do it out of habit by putting these files in ~/.kde4/share/config/ before ever starting a new KDE user the first time:
# nepomukserverrc: [$Version] update_info=nepomukstrigiservice-migrate.upd:nepomukstrigiservice-migrate
[Basic Settings] Start Nepomuk=false
[main Settings] Storage Dir[$e]=$HOME/.kde4/share/apps/nepomuk/repository/main/ Used Soprano Backend=null rebuilt index for type indexing=false
[Service-nepomukstrigiservice] autostart=false
# nepomukstrigirc: [General] exclude filters=autom4te,*.rcore,CTestTestfile.cmake,*.o,*.omf,.hg,*.m4,*.orig,moc_*.cpp,conftest,.xsession-errors*,CMakeTmpQmake,*.tmp,po,.svn,.histfile.*,lzo,.bzr,.git,litmain.sh,cmake_install.cmake,CMakeFiles,*.pc,*.nvram,*.elc,*.la,CMakeCache.txt,confdefs.h,*.gmo,*.csproj,*.rej,config.status,lost+found,confstat,*.pyc,_darcs,CVS,*.part,libtool,*.aux,*.po,CMakeTmp,Makefile.am,*.lo,*.loT,*~,*.moc,*.vm*,*.class,core-dumps exclude filters version=2 folders[$e]=$HOME/tmp/null index hidden folders=false index newly mounted=false
Hi, I tried all this, no result. Repartitioned the disk, including formatting the /home, downloaded and installed RC2 again: no result. While I didn't check all applications, some observations I have made: - yast functions as expected, at it's normal speed - libreoffice functions OK, but when opening or saving a document, the dialog windows take some time to appear, and after closing them (which itself goes at normal speed), it also takes a while before the main libreoffice is responding to input. Once it does, normal responsiveness is back. - gkrellm, gimp, inkscape show the firefox/thunderbird behavior - they do so even if started in icewm environment. All testing took a lot of sparse free time, that's why it sometimes takes some time before I react here. My next try would be to install 12.3 on that same disk, see what happens. (But, it had 12.3 in it's beta stages, this disk being my experiment environment). But maybe (well, probably...) someone on this list has better ideas. regards, Jogchum -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
op 15-11-13 21:13, Jogchum Reitsma schreef:
My next try would be to install 12.3 on that same disk, see what happens. (But, it had 12.3 in it's beta stages, this disk being my experiment environment).
First, installed fglrx, but that gave no change. Installed 12.3 on that disk, everything perfect. Upgraded to 13.1 RC2, no problems. So decided to upgrade my ' production' -system (except for the disk on the same hardware): mixed results: - Firefox and Thunderbird behave as expected - dolphin takes more than a minute to start, but from than on reacts normally - the 'leave' -options take almost two minutes to pop up - sound working in Yast, not in kde (window ' Geluidsinstellingen' ('Sound configuration') in kmix takes several minutes to appear, show some hardware items. but gives no test sound at either of them - vlc, when started from command line, gives it's name and version, stays alive as a process, (and cannot be stopped even with kill -9 as root) but gives no window - kdenlive, when started from command line, complains about missing libDeckLinkAPI.so, then says "QCoreApplication::postEvent: Unexpected null receiver", and stays mutt. gkrellm works, so I can see there' s no disk/CPU activity while waiting. /var/log/messages gives no errors or warnings related to this. There's even more, but too much to elaborate on now. All in all, 13.1 is the worst Suse distro in this house so far (since about 6.0)... regards, Jogchum (PS: since 13.1 is not factory anymore, should this discussion be held elsewhere?) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hello, Am Samstag, 9. November 2013 schrieb Jogchum Reitsma:
12.3 runs without problems on the same system as 13.1RC2, the only difference being 13.1 residing on another disk, with it's own home partition on that same disk. So hardware trouble seems unlikely.
I remember more than one harddisk that still seemed to work, but was terribly slow because it had errors. Can you check the harddisk with badblocks? Regards, Christian Boltz -- Ein Admin ist wie ein Tierpfleger er muss mir eNTen Pinguinen und Daemonen (ähm habe ich irgendwie noch in keinem Zoo gesehen) umgehen können, eNTen sind aber besonders gefährlich und unberechenbar, beim Putzen sollte man da schon aufpassen das man sich keinen Wurm einfängt[........] [D. Aubry] -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
op 09-11-13 13:27, Christian Boltz schreef:
Hello,
Am Samstag, 9. November 2013 schrieb Jogchum Reitsma:
12.3 runs without problems on the same system as 13.1RC2, the only difference being 13.1 residing on another disk, with it's own home partition on that same disk. So hardware trouble seems unlikely. I remember more than one harddisk that still seemed to work, but was terribly slow because it had errors.
Can you check the harddisk with badblocks?
Regards,
Christian Boltz Christian,
Checked all four file systems on the disk, zero errors. I will go through Felix's suggestions partly tonight, partly tomorrow evening. Thanks. Jogchum -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2013-10-30 13:25, Jogchum Reitsma wrote:
Hi,
After a fresh install of RC1 (and emptying .kde and .kde4) firefox and thunderbird are not working. Both show
(process:4432): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
I've been getting ugly messages out of glib since April or so... It's a feature to dump them to the users terminal instead of a log. Mine were a bit different, but seeing such things all the time, and you begin to stop paying attention to them: (Terminal:31033): GLib-WARNING **: (gerror.c:390):g_error_new_valist:
runtime check failed: (domain != 0) Failed to connect to session manager: Failed to connect to the session manager: SESSION_MANAGER environment variable not defined
These are at least two warnings / errors:
(Terminal:31033): GLib-WARNING **: (gerror.c:390):g_error_new_valist: runtime check failed: (domain != 0)
The caller does not specify an error Domain. Whereas this used to be silently ignored earlier, it now gives a warning (commit in glib in question): https://git.gnome.org/browse/glib/commit/glib/gerror.c?id=6d9f874330ee27ea09...
When programs spout stuff like this on a regular basis you learn to ignore it -- which is very likely NOT the best thing for users to learn to ignore. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 16/11/13 04:08, Linda Walsh wrote:
On 2013-10-30 13:25, Jogchum Reitsma wrote:
Hi,
After a fresh install of RC1 (and emptying .kde and .kde4) firefox and thunderbird are not working. Both show
(process:4432): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
I've been getting ugly messages out of glib since April or so... It's a
feature to dump them to the users terminal instead of a log.
Mine were a bit different, but seeing such things all the time, and you begin to stop paying attention to them:
(Terminal:31033): GLib-WARNING **: (gerror.c:390):g_error_new_valist:
runtime check failed: (domain != 0) Failed to connect to session manager: Failed to connect to the session manager: SESSION_MANAGER environment variable not defined
These are at least two warnings / errors:
(Terminal:31033): GLib-WARNING **: (gerror.c:390):g_error_new_valist: runtime check failed: (domain != 0)
The caller does not specify an error Domain. Whereas this used to be silently ignored earlier, it now gives a warning (commit in glib in question): https://git.gnome.org/browse/glib/commit/glib/gerror.c?id=6d9f874330ee27ea09...
When programs spout stuff like this on a regular basis you learn to ignore it -- which is very likely NOT the best thing for users to learn to ignore.
I ignored it as noise but I got the following reply from codeweavers.com - I asked for support on a python problem installing Crossover Office, instead they picked on this and ignored the python errors that were causing the install to fail. Needless to say all it did was to get rid of the GLIB WARNING message. ------------------------------------------------------------------------------------------------------------------------------- Hello, You are hitting a bug with the oxygen-gtk theme. It's easy to work around. For CrossOver's installation, change the "Widget Style" to anything besides "oxygen-gtk". You'll find this setting within your system settings (I don't have OpenSuse 13.1 handy at this moment, apologies for the fumbling). It should be under "Application Appearance", "GTK+ Appearance", "Widget Style". Once you've made that change, again try to install the .bin installer and CrossOver should install successfully. ---------------------------------------------------------------------------------------------------------------- Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
op 16-11-13 07:56, Sid Boyce schreef:
On 16/11/13 04:08, Linda Walsh wrote:
On 2013-10-30 13:25, Jogchum Reitsma wrote:
Hi,
After a fresh install of RC1 (and emptying .kde and .kde4) firefox and thunderbird are not working. Both show
(process:4432): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
I've been getting ugly messages out of glib since April or so... It's a
feature to dump them to the users terminal instead of a log.
Mine were a bit different, but seeing such things all the time, and you begin to stop paying attention to them:
(Terminal:31033): GLib-WARNING **: (gerror.c:390):g_error_new_valist:
runtime check failed: (domain != 0) Failed to connect to session manager: Failed to connect to the session manager: SESSION_MANAGER environment variable not defined
These are at least two warnings / errors:
(Terminal:31033): GLib-WARNING **: (gerror.c:390):g_error_new_valist: runtime check failed: (domain != 0)
The caller does not specify an error Domain. Whereas this used to be silently ignored earlier, it now gives a warning (commit in glib in question): https://git.gnome.org/browse/glib/commit/glib/gerror.c?id=6d9f874330ee27ea09...
When programs spout stuff like this on a regular basis you learn to ignore it -- which is very likely NOT the best thing for users to learn to ignore.
I ignored it as noise but I got the following reply from codeweavers.com - I asked for support on a python problem installing Crossover Office, instead they picked on this and ignored the python errors that were causing the install to fail. Needless to say all it did was to get rid of the GLIB WARNING message. -------------------------------------------------------------------------------------------------------------------------------
Hello,
You are hitting a bug with the oxygen-gtk theme. It's easy to work around. For CrossOver's installation, change the "Widget Style" to anything besides "oxygen-gtk".
You'll find this setting within your system settings (I don't have OpenSuse 13.1 handy at this moment, apologies for the fumbling). It should be under "Application Appearance", "GTK+ Appearance", "Widget Style".
Once you've made that change, again try to install the .bin installer and CrossOver should install successfully. ----------------------------------------------------------------------------------------------------------------
Regards Sid.
Hi Sid, While this may solve Linda's problem, it doesn't solve mine - the problems described in the original post are still there after changing the widget style. Well, you didn't propose as a solution for these problems, but I decided to check it anyhow. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 16/11/13 15:40, Jogchum Reitsma wrote:
op 16-11-13 07:56, Sid Boyce schreef:
On 16/11/13 04:08, Linda Walsh wrote:
On 2013-10-30 13:25, Jogchum Reitsma wrote:
Hi,
After a fresh install of RC1 (and emptying .kde and .kde4) firefox and thunderbird are not working. Both show
(process:4432): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
I've been getting ugly messages out of glib since April or so... It's a
feature to dump them to the users terminal instead of a log.
Mine were a bit different, but seeing such things all the time, and you begin to stop paying attention to them:
(Terminal:31033): GLib-WARNING **: (gerror.c:390):g_error_new_valist:
runtime check failed: (domain != 0) Failed to connect to session manager: Failed to connect to the session manager: SESSION_MANAGER environment variable not defined
These are at least two warnings / errors:
(Terminal:31033): GLib-WARNING **: (gerror.c:390):g_error_new_valist: runtime check failed: (domain != 0)
The caller does not specify an error Domain. Whereas this used to be silently ignored earlier, it now gives a warning (commit in glib in question): https://git.gnome.org/browse/glib/commit/glib/gerror.c?id=6d9f874330ee27ea09...
When programs spout stuff like this on a regular basis you learn to ignore it -- which is very likely NOT the best thing for users to learn to ignore.
I ignored it as noise but I got the following reply from codeweavers.com - I asked for support on a python problem installing Crossover Office, instead they picked on this and ignored the python errors that were causing the install to fail. Needless to say all it did was to get rid of the GLIB WARNING message. -------------------------------------------------------------------------------------------------------------------------------
Hello,
You are hitting a bug with the oxygen-gtk theme. It's easy to work around. For CrossOver's installation, change the "Widget Style" to anything besides "oxygen-gtk".
You'll find this setting within your system settings (I don't have OpenSuse 13.1 handy at this moment, apologies for the fumbling). It should be under "Application Appearance", "GTK+ Appearance", "Widget Style".
Once you've made that change, again try to install the .bin installer and CrossOver should install successfully. ----------------------------------------------------------------------------------------------------------------
Regards Sid.
Hi Sid,
While this may solve Linda's problem, it doesn't solve mine - the problems described in the original post are still there after changing the widget style. Well, you didn't propose as a solution for these problems, but I decided to check it anyhow. I changed GTK Theme to Raleigh and it stopped those messages appearing for all applications. Regards Sid.
-- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Saturday 2013-11-16 17:52, Sid Boyce wrote:
I changed GTK Theme to Raleigh and it stopped those messages appearing for all applications.
So your particular GTK theme (possibly with a dedicated engine/compiled program) has not been ported. Or to put it in a different way, GTK changed its semantics once again :/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (9)
-
Basil Chupin -
Carlos E. R. -
Christian Boltz -
Dimstar / Dominique Leuenberger -
Felix Miata -
Jan Engelhardt -
Jogchum Reitsma -
Linda Walsh -
Sid Boyce