Hi,

may I attach a similar (and most probably already asked...) question here?

Is there a general rule what to do with publicly accessible reports that are 
duplicates of already known, not publicly accessible ones. In most cases the 
not publicly accessible original will remain private.

I'm not questioning this policy in general, but are exceptions possible? Like 
"If there are more than <whatever> publicly accessible duplicates, let's make 
the original one public as well so people can actually know what's going on".

Precisely, in this case it's about the problem of not being able to mount 
floppies from within GNOME. The error message is "Method "Mount" with signature 
"ssas" on interface "org.freedesktop.Hal.Device.Volume" doesn't exist".

I guess that this is known as #164327. There is a publicly accessible duplicate 
#175590 and many similar, related but not-quite-duplicate ones:

#152078 (same error message, but reported to and fixed in KDE, not GNOME)
#159589 (private, duplicate of the above)
#164488 (another duplicate, for KDE)
#152542 (yet another one, for KDE)
#154652 (yet another one, for KDE
#155574 (the last one I found, again for KDE)

Specifically I'd like to know:

- Is it known that this problem is fixed for KDE, but still present in GNOME 
(the publicly accessible #175590 doesn't say anything about the desktop 
environment explicitly),

- Where is the origin of the problem, in a GNOME library (like it was in 
kdebase3 for KDE) or in hal/dbus itself,

- Is it a problem in a setup script or config file that I can fix myself or 
does fixing this problem require a recompiled <whatever> package,

- Can I forget about it (aka. "don't use floppies") or are there plans to fix 
this for SL 10.1.

Andreas Hanke
-- 


Bis zu 70% Ihrer Onlinekosten sparen: GMX SmartSurfer!
      Kostenlos downloaden: http://www.gmx.net/de/go/smartsurfer
    

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to