trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: September 2010

Re: [trinity-devel] Network status indicator errors

From: Darrell Anderson <humanreadable@...>
Date: Mon, 20 Sep 2010 11:22:57 -0700 (PDT)
> > The following errors appear in
> the xsession logs:
> >
> > QObject::connect: No such signal
> MediaImpl::warning(const QString&)
> > QObject::connect:  (sender
> name:   'unnamed')
> > QObject::connect:  (receiver name: 'unnamed')
> > QObject::connect: No such signal
> >
> ConnectionManager::statusChanged(QString,NetworkStatus::EnumStatus)
> > QObject::connect:  (sender
> name:   'connection_manager')
> > QObject::connect:  (receiver name:
> 'networkstatusindicator')
> > QObject::connect: No such signal
> >
> ConnectionManager::statusChanged(QString,NetworkStatus::EnumStatus)
> > QObject::connect:  (sender
> name:   'connection_manager')
> > QObject::connect:  (receiver name:
> 'networkstatusindicator')

Updated kdelibs and kdebase to svn 1177573. Messages do not appear! :)

> Also, I think I have fixed the XDG autostart problem, and

No HPLIP messages appear and no $HOME/hplip directory is created. Good job!

> the Konqueror
> toolbar issue is also fixed.  In other words, barring
> a major crashing
> issue or functionality problem the code should be very
> close to finalized
> for 3.5.12!

I think we are indeed getting close. :)

I am posting some additional items to the list as I continue testing. None are fatal but I think if corrected add polish and professionalism.

I can hardly believe how much work has been done to get Trinity installable on Slackware. I am grateful to have gotten this far. Thank you!

Yet I still have much to do in that respect: building and testing non-core packages and libraries, testing the build scripts with post 12.2 releases, and most important, actually installing Trinity on my office machine (and not a virtual machine) to begin real-world daily testing. That latter is always a huge step of faith. Gulp!