<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "http://bugs.gentoo.org/bugzilla.dtd">

<bugzilla version="2.22.7"
          urlbase="http://bugs.gentoo.org/"
          maintainer="bugzilla@gentoo.org"
>

    <bug>
          <bug_id>21297</bug_id>
          
          <creation_ts>2003-05-19 18:14 0000</creation_ts>
          <short_desc>System Monitor of gnome-applets won&apos;t load after emerging new libgtop-2.0.2</short_desc>
          <delta_ts>2003-05-22 18:57:57 0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>Gentoo Linux</product>
          <component>GNOME</component>
          <version>unspecified</version>
          <rep_platform>x86</rep_platform>
          <op_sys>Linux</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          
          <priority>P2</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>1.4</target_milestone>
          
          
          
          <everconfirmed>1</everconfirmed>
          <reporter>wmilkowski@gazeta.pl</reporter>
          <assigned_to>gnome@gentoo.org</assigned_to>
          

      

      
          <long_desc isprivate="0">
            <who>wmilkowski@gazeta.pl</who>
            <bug_when>2003-05-19 18:14:25 0000</bug_when>
            <thetext>I emerged new libgtop during system update (and only this single ebuild).
When I try to load system monitor GNOME displays following error:
&apos;The panel encountered a problem while loading &quot;OAFIID:GNOME_MultiLoadApplet&quot;
Details: Child process did not give an error message, unknown failure occurred
Do you want to delete the applet from your configuration?&apos;

I emerged earlier version 2.0.1 but problem hasn&apos;t been solved. It still crashes.

Reproducible: Always
Steps to Reproduce:
Probably only emerge libgtop-2.0.2, and then try to run system monitor as applet
in GNOME Panel.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>foser@gentoo.org</who>
            <bug_when>2003-05-19 18:35:02 0000</bug_when>
            <thetext>yes a problem i noticed as well, libgtop creates a wrongly versioned .so similar to what gal does.

One solution is to rebuild the applets.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>wmilkowski@gazeta.pl</who>
            <bug_when>2003-05-19 18:56:16 0000</bug_when>
            <thetext>Yes, I rebuild them, but it didn&apos;t change anyting... Did you meen that I should do 
this against previous version of libgtop? </thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>foser@gentoo.org</who>
            <bug_when>2003-05-19 19:11:15 0000</bug_when>
            <thetext>no it should work just fine against any version.

remove libgtop and try again, the fact that even when you downgraded libgtop you still had the problem suggest that you still missed something because the link should&apos;ve been reinstalled.

This could be a completely different problem, but i at this time very much doubt it.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>wmilkowski@gazeta.pl</who>
            <bug_when>2003-05-20 18:22:23 0000</bug_when>
            <thetext>OK it works now.

Thanks a lot.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>foser@gentoo.org</who>
            <bug_when>2003-05-20 18:35:49 0000</bug_when>
            <thetext>still needs to be fixed properly though.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>foser@gentoo.org</who>
            <bug_when>2003-05-22 18:57:57 0000</bug_when>
            <thetext>i&apos;ve added a 202-r1 with a so versioning fix that should fix the initial problem, you might have to rebuild again because you rebuild against the bad 2.0.2 .

</thetext>
          </long_desc>
      
    </bug>

</bugzilla>