Mailinglist Archive: opensuse (2441 mails)

["Carlos E. R." <robin1.listas@xxxxxxxxxx>]

The Wednesday 2005-06-01 at 18:24 +0200, Anders Johansson wrote:

> On Wednesday 01 June 2005 11:43, Carlos E. R. wrote:
> > That's not it. Remember that I have renamed the susewatcher binary to
> > /opt/kde3/bin/DAMMsusewatcher, there is no way it can start. It doesn't
> > exist.
> 
> It's suseplugger, not susewatcher, that monitors for new hardware. susewatcher 
> monitors for updates, and I suspect you no longer see the suse logo icon in 
> the systray

That doesn't matter; remember, again, I said that I renamed both to:

  /opt/kde3/bin/DAMMsuseplugger
  /opt/kde3/bin/DAMMsusewatcher

   I posted that data on this same thread 36 hours ago. I see you did not 
   read what I said before answering.

There is no way any of them can be started, unless hardlinked somewhere, 
or using a library somewhere. The binaries are unreachable.

However, new users are prompted with "new hardware found". It's got to be 
something else.

-- 
Cheers,
       Carlos Robinson