Bug Day coming up! 23 August 2011 at 1400 EDT. Time to get Trinity into tip-top shape!
Join us in #trinity-desktop-meeting on Freenode (webchat.freenode.net) to help with bugs and get help with any outstanding issues, live!
If you don't already have an account on btd, you should probably create one. URL: bugs.trinitydesktop.org
And last but not least, we need all the help we can get :)
* On 2011 16 Aug 22:06 -0500, Robert Xu wrote:
Bug Day coming up! 23 August 2011 at 1400 EDT. Time to get Trinity into tip-top shape!
Join us in #trinity-desktop-meeting on Freenode (webchat.freenode.net) to help with bugs and get help with any outstanding issues, live!
If you don't already have an account on btd, you should probably create one. URL: bugs.trinitydesktop.org
And last but not least, we need all the help we can get :)
I imagine this requires using the SVN version of Trinity? Right now I am using Squeeze 3.5.12 packages on Debian Squeeze and Wheezy. What are the build requirements/dependencies?
- Nate >>
On Tue, Aug 16, 2011 at 23:52, Nate Bargmann n0nb@n0nb.us wrote:
- On 2011 16 Aug 22:06 -0500, Robert Xu wrote:
Bug Day coming up! 23 August 2011 at 1400 EDT. Time to get Trinity into tip-top shape!
Join us in #trinity-desktop-meeting on Freenode (webchat.freenode.net) to help with bugs and get help with any outstanding issues, live!
If you don't already have an account on btd, you should probably create one. URL: bugs.trinitydesktop.org
And last but not least, we need all the help we can get :)
I imagine this requires using the SVN version of Trinity? Right now I am using Squeeze 3.5.12 packages on Debian Squeeze and Wheezy. What are the build requirements/dependencies?
No, you can use 3.5.12 and still help :) We want to know what's still outstanding. I'll also be there to try to confirm any bugs that might be brought up from previous versions to see if they still exist in nightlies.
I most likely cannot be around this Saturday so I'll list my observations here.
There is a thread from last week where we tried to determine why two instances of WiCD are appearing in the system tray each time TDE is started. I tried moving /etc/xdg/autostart/wicd-tray.desktop out of the way and then no WiCD system tray instances were run. After moving it back TDE once again starts two instances. I did not observe this behavior in XFCE 4.8 which I was running previous to installing TDE.
I was a bit stymied attempting tocustomize KDM from kControl. No matter what I tried, Debian More Orbit Blue was shown. I finally had to comment out the Theme line (as I recall) to allow my changes to be seen. If a default them is chosen, mention should probably be made in kcontrol that the system theme setting overrided changes made in kcontrol's KDM module.
Desktop icons. I don't use too many but the few I have are set to be lined up vertically, directories first, and locked in place. Plugging in a flash drive results in its icon being placed in a new vertical row not exactly lined up with the existing icons. I would prefer it to be placed at the bottom of the existing icon list on the desktop. It seems as though that was the behavior up to 3.5.10, as I recall.
I am using Xscreensaver rather than kscreensaver. There are some issues with screen locking that occur after lid close and resume from suspend. I have things configured so that the screen is locked on lid close and when I reopen the lid I get the Xscreensaver password dialog. I also have the screen set to be locked upon resume and then I first get a TDE password dialog followed immediately by the Xscreensaver password dialog! I use Xscreensaver only for the reason that its savers are more varied and it changes savers at a configurable interval. If Kscreensaver would change savers at a regular interval rather than at each saver start in Random mode, I could drop Xscreensaver.
No real show stoppers here, just a few minor annoyances. :-) Overall, I give the project an A++ rating for keeping a great desktop environment moving forward.
- Nate >>
In addition, in Kcontrol under Power Control|Laptop Battery, each tab offers the following advice, "Your computer seems to have a partial ACPI installation. ACPI was probably enabled, but some of the sub-options were not - you need to enable at least 'AC Adaptor' and 'Control Method Battery' and then rebuild your kernel."
So far as I know, the ACPI packages are current and I'm not missing dependencies. Could this be a simple error looking for specific package names? I am using stock Debian kernel packages on both Squeeze and Wheezy and see the message in each installation.
- Nate >>
-
Nate Bargmann -
Robert Xu