[opensuse] Beagle crashes hard my machine. Removing beagle impedes nautilus from running.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, As is known, the combination of having a root filesystem formatted as reiserfs will hard lock the machine as soon as Beagle runs (Bug 448007). Therefore I removed all related to Beagle. But now Nautilus refuses to run: cer@minas-morgul:~> nautilus nautilus: error while loading shared libraries: libbeagle.so.1: cannot open shared object file: No such file or directory - -- Cheers / Saludos, Carlos E. R. (from 11.1-ex-factory) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAklOsT8ACgkQU92UU+smfQUmTgCffhf5Zo2J3lqBuTsWtCb8B0lG 3acAn1zitGo3RKu6xaksYeTyqORObHxh =yCH7 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Carlos E. R. wrote:
Hi,
As is known, the combination of having a root filesystem formatted as reiserfs will hard lock the machine as soon as Beagle runs (Bug 448007). Therefore I removed all related to Beagle.
But now Nautilus refuses to run:
cer@minas-morgul:~> nautilus nautilus: error while loading shared libraries: libbeagle.so.1: cannot open shared object file: No such file or directory
Let libbeagle* installed - just remove the daemon package called beagle. Beagle is the daemon to run and libbeagle is linked in apps that connect to the daemon, Andreas - -- Andreas Jaeger, Director Platform / openSUSE, aj@suse.de SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFJTrWCOJpWPMJyoSYRAs6vAJ0dmnb2+sIcjMlGgNz2CW1am67qmACgg7FQ 07pOAFRyRJ2J61yQtRzBBCQ= =DlMv -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Andreas Jaeger wrote:
Let libbeagle* installed - just remove the daemon package called beagle.
Beagle is the daemon to run and libbeagle is linked in apps that connect to the daemon,
Thanks, it appears to work :-) - -- Cheers / Saludos, Carlos E. R. (from 11.1-ex-factory) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAklOvQwACgkQU92UU+smfQUzegCeO35mhWRYCCJ1gh10BW8a2q0G EC8AnjOoNHxumUJnmv2yD0Ca2WUyjHI0 =FCyY -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 21 December 2008, Carlos E. R. wrote:
Hi,
Hi,
As is known, the combination of having a root filesystem formatted as reiserfs will hard lock the machine as soon as Beagle runs (Bug 448007). Therefore I removed all related to Beagle.
Running 2.6.27.7-9-default , with beagle on a reiserfs root with ACLs and heavy disk IO, I haven't had any hard locks since it was released.
But now Nautilus refuses to run:
cer@minas-morgul:~> nautilus nautilus: error while loading shared libraries: libbeagle.so.1: cannot open shared object file: No such file or directory
-- Cheers / Saludos,
Carlos E. R. (from 11.1-ex-factory)
Kind regards -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2008-12-22 at 19:25 +0200, auxsvr@gmail.com wrote:
Running 2.6.27.7-9-default , with beagle on a reiserfs root with ACLs and heavy disk IO, I haven't had any hard locks since it was released.
And that's the problem they are having about solving it: some people bump into this every day, some never. It could be a pattern beagle finds. Do you use kde or gnome? - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAklP50sACgkQtTMYHG2NR9UX6ACdF2VS5g/xPnUagQgHzcUPaNdY qj8An3QJOs7dODd9+RL6F3x53GlPS6TJ =fOEg -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 22 December 2008, Carlos E. R. wrote:
On Monday, 2008-12-22 at 19:25 +0200, auxsvr@gmail.com wrote:
Running 2.6.27.7-9-default , with beagle on a reiserfs root with ACLs and heavy disk IO, I haven't had any hard locks since it was released.
And that's the problem they are having about solving it: some people bump into this every day, some never. It could be a pattern beagle finds.
Do you use kde or gnome?
KDE 4. Do you know the bugzilla number for the initial report? I had a problem similar to the one you describe when 11 was released, a patch fixed it some months later.
-- Cheers, Carlos E. R.
Kind regards -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2008-12-22 at 22:28 +0200, auxsvr@gmail.com wrote:
Do you use kde or gnome?
KDE 4.
Me gnome.
Do you know the bugzilla number for the initial report? I had a problem similar to the one you describe when 11 was released, a patch fixed it some months later.
No... I don't think I have it. I searched on the bug names in my list and I don't see that one looking for reiser or beagle. I heard of it and I waited till it was solved before I upgraded. But as my factory install at the time did not show the symptoms, I couldn't report on it. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAklP+q8ACgkQtTMYHG2NR9V36gCZAYhEzY9WuM5fmGmBMVr3YJgX Rs8AoIAlVmMCyys0RYaFv5AU+xDs2UwF =nMVW -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 22 December 2008, Carlos E. R. wrote:
No... I don't think I have it. I searched on the bug names in my list and I don't see that one looking for reiser or beagle. I heard of it and I waited till it was solved before I upgraded. But as my factory install at the time did not show the symptoms, I couldn't report on it.
I just had 3 system hangs (SysRq-B works, SysRq-S doesn't) in succession, right after KDE (and beagle) starts. Killing beagle right after KDE started the fourth time prevented the hang, so it must be the same issue as yours. I notice a pattern here that might be relevant: every time I'm using a vanilla kernel, which I compile myself and has reiserfs in the kernel, I get "ReiserFS: sda2: warning: Invalid hash for xattr (user.Beagle) associated with [101 45992 0x0 SD]" messages for various files in the system log. These error messages never appear when I use the opensuse kernel, this has been the case since 10.3, if I remember correctly. The hangs started right after I booted with the vanilla kernel. Do you have a bug # to add this information?
-- Cheers, Carlos E. R.
Happy new year everybody, Peter -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2009-01-03 at 12:43 +0200, auxsvr@gmail.com wrote:
On Monday 22 December 2008, Carlos E. R. wrote:
No... I don't think I have it. I searched on the bug names in my list and I don't see that one looking for reiser or beagle. I heard of it and I waited till it was solved before I upgraded. But as my factory install at the time did not show the symptoms, I couldn't report on it.
I just had 3 system hangs (SysRq-B works, SysRq-S doesn't) in succession, right after KDE (and beagle) starts. Killing beagle right after KDE started the fourth time prevented the hang, so it must be the same issue as yours. I notice a pattern here that might be relevant: every time I'm using a vanilla kernel, which I compile myself and has reiserfs in the kernel, I get "ReiserFS: sda2: warning: Invalid hash for xattr (user.Beagle) associated with [101 45992 0x0 SD]" messages for various files in the system log. These error messages never appear when I use the opensuse kernel, this has been the case since 10.3, if I remember correctly. The hangs started right after I booted with the vanilla kernel.
Do you have a bug # to add this information?
Yes, please, do! :-)) Bug 448007, at Novell. <https://bugzilla.novell.com/show_bug.cgi?id=448007> There has not been any movement since Dec 22 in this bug, so we need people reporting this so that they invest resources in solving it. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAklfU3gACgkQtTMYHG2NR9X0kACZATtkK8lFbB3cUYqEQO3vHkkU Gp4Anieg60ZyvhEJ8tTyD3mCyEpXmEiX =w0b9 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 03 January 2009 13:00:54 Carlos E. R. wrote:
On Saturday, 2009-01-03 at 12:43 +0200, auxsvr@gmail.com wrote:
On Monday 22 December 2008, Carlos E. R. wrote:
No... I don't think I have it. I searched on the bug names in my list and I don't see that one looking for reiser or beagle. I heard of it and I waited till it was solved before I upgraded. But as my factory install at the time did not show the symptoms, I couldn't report on it.
I just had 3 system hangs (SysRq-B works, SysRq-S doesn't) in succession, right after KDE (and beagle) starts. Killing beagle right after KDE started the fourth time prevented the hang, so it must be the same issue as yours. I notice a pattern here that might be relevant: every time I'm using a vanilla kernel, which I compile myself and has reiserfs in the kernel, I get "ReiserFS: sda2: warning: Invalid hash for xattr (user.Beagle) associated with [101 45992 0x0 SD]" messages for various files in the system log. These error messages never appear when I use the opensuse kernel, this has been the case since 10.3, if I remember correctly. The hangs started right after I booted with the vanilla kernel.
Do you have a bug # to add this information?
Yes, please, do! :-))
Bug 448007, at Novell. <https://bugzilla.novell.com/show_bug.cgi?id=448007>
There has not been any movement since Dec 22 in this bug, so we need people reporting this so that they invest resources in solving it.
Carlos, many people are at Christmas vacation, so no surprise that you don't see a reaction. I expect some activity next week again... Happy New Year, Andreas -- Andreas Jaeger, Director Platform / openSUSE, aj@suse.de SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2009-01-04 at 10:50 +0100, Andreas Jaeger wrote:
There has not been any movement since Dec 22 in this bug, so we need people reporting this so that they invest resources in solving it.
Carlos, many people are at Christmas vacation, so no surprise that you don't see a reaction. I expect some activity next week again...
I thought so... - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAklhEiUACgkQtTMYHG2NR9X1DACfWzQz6RmTeaEYL83st9mnHvv9 lckAn11qrp8g+skbMsu17Wt/Ttk4jXlV =WmvF -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (4)
-
Andreas Jaeger -
auxsvr＠gmail.com -
Carlos E. R. -
Carlos E. R.