When I run kdebugdialog to enable a single option, the result is that kdebugdialog creates a user kdebugdialogrc file with every option enabled.
Seems to me that the resulting kdebugdialogrc file should be the same as the system default with the only difference being the single change.
Would somebody please confirm this behavior?
Darrell
The summer season (in the northern hemisphere), traditionally a time when many people shift paces to enjoy outdoor activities and traveling, begins to close. Despite this traditional change of pace the past three months, Trinity development continued at a methodical pace. From June 1 to August 31 there were 131 bug reports or enhancement requests resolved in the bug tracker (http://bugs.trinitydesktop.org/bugzilla/buglist.cgi?bug_status=RESOLVED&chf…), as well as issues resolved through discussion in the developer's mailing list.
During the past several months, many changes occurred in the upstream free/libre software world, such as changes to GCC, GLIBC, GLIB2, LIBPNG, FFMPEG, HAL, etc. Those changes occurred in rapid succession and close proximity. Resolving Trinity related issues has been challenging.
The Trinity development team kept pace. The online Patches web page shows the progress of resolving those challenges: http://www.trinitydesktop.org/patches/
As autumn knocks on the doors of life, Trinity development continues:
* The 3.5.13.1 SRU (Stable Release Update) is only a few patches away from being released with official tarballs.
* A slew of TDEHWLIB updates were committed to the GIT development branch. TDEHWLIB is the eventual Trinity hardware detection layer replacement for HAL, and is already able to fully replace HAL in most areas.
* Network-manager improvements were committed to the GIT development branch.
* Koffice, K3B, and Gwenview i18n sources were committed to the GIT development branch.
* The R14 development branch was overhauled with XDG compliance updates. Trinity is now a recognized XDG environment.
* Comprehensive branding overhaul.
The Trinity development team has adopted a "release when ready" approach but tentatively are focused on releasing R14.0.0 in the fall of 2012. Also, the previously mentioned LDAP/Kerberos tools remain available in the TDE bounty program, with more information available on the TDE RFE page (http://www.trinitydesktop.org/crfe/#finished).
The Trinity development team hopes you enjoyed your summer. Soon in the northern hemisphere the leaves will turn color and in the southern hemisphere, leaves will sprout. Please enjoy the seasonal changes and thank you for being a member of this community!
--The Trinity News Team
Slavek, All,
On my last 3.5.13-sru build, the input gesture pressing print-screen for
ksnapshot stopped working similar to what happened with R14. Please test the
latest 3.5.13-sru build and see if it still works for you. The entire issue
might be a simple 'k' 't' rename issue and 3.5.13-sru may have pulled in that
commit. I'll have more time this weekend to dig into it, but having confirmation
on if other see it as well will help :)
--
David C. Rankin, J.D.,P.E.
All,
A positive note. After the latest set of updates to Arch, tde 3513-sru
continues to run without issue. Fingers crossed that the last of the upstream
bombs have already been detonated...
--
David C. Rankin, J.D.,P.E.
Now that I have a Mounting tab I can see why we were not communicating fully in the previous thread. :-) I'm starting a new thread so we start on the same page.
With that dialog enabled, I now see you are using UUIDs in mediamanagerrc. I was unable to see that previously because without the underlying code being compiled that caused the missing Mounting tab, those features of TDEHW were not working. :-)
I don't know your TDEHW FIXME to-do list. So please accept my apology if I am covering topics you already know. :-)
* You already know about the problem of retaining the same icon label across different physical ports. Now that I have access to device-specific mounting options, I can see that mediamangerrc contains mounting options per UUID, but TDEHW remains confused about applying icon labels. From what I think I see after multiple insertions/removals of the same device across three different USB ports, TDEHW is assigning icon labels based upon device nodes rather than UUID. You mentioned in a previous post you saw the problem in the code, so I'll watch for a patch.
* Some features of the Mounting dialog are missing, which are reflected respectively in mediamanagerrc too. Here are some screenshots, the first set from a HAL system and the second set from TDEHW:
HAL:
http://humanreadable.nfshost.com/trinity/build_logs/mounting-dialog-floppy-…http://humanreadable.nfshost.com/trinity/build_logs/mounting-dialog-usb-hal…
TDEHW:
http://humanreadable.nfshost.com/trinity/build_logs/mounting-dialog-floppy-…http://humanreadable.nfshost.com/trinity/build_logs/mounting-dialog-usb-tde…
Missing features:
Generic Mount Options:
Quiet
Filesystem Specific Mount Options:
Flushed IO
Mount as user
Short names
Here is a mediamanagerrc set of HAL configurations:
[/org/freedesktop/Hal/devices/volume_uuid_4840_B9DA]
atime=false
flush=true --> Missing
mountpoint=/media/buffalo_1gb
quiet=false --> Missing
ro=false
shortname=lower --> Missing
sync=false
uid=true --> Missing
utf8=true
Here are the same UUID settings under TDEHW:
[4840-B9DA]
atime=false
automount=true
mountpoint=/media/buffalo_1gb
ro=false
sync=false
use_defaults=false
utf8=true
* Safely Remove does not work. That is, using that option will unmount the device but does not remove the icon from the desktop.
* Eject does not work with CDs/DVDs.
* Icon appearance times remain weird, some fast, some very slow.
* Does TDEHW poll floppy drives? The floppy Mounting dialog (Unmounted Floppy icon) has a check box to mount automatically, but the option does not yet seem implemented.
Darrell
I'm attempting to build 'tdenetwork' from the latest git source but it's
failing. The errors begin with;
tdenetwork/kopete/protocols/groupwise/libgroupwise/securestream.h:43:22:
error: QCA has not been declared
I've seen this mentioned in recent list history but from what I read, it
was apparently fixed. As mentioned in the posts I read, it builds
successfully with;
-DBUILD_KOPETE_PROTOCOL_GROUPWISE=OFF
-DBUILD_KOPETE_PROTOCOL_JABBER=OFF
but that is surely not the answer?
I have _fairly_ recently built this but not on x86_64. Anybody any pointers?
MIke.
--
Any question is easy if you know the answer!
Please share any Trinity related progress or news for the week of Aug. 25 to Sep. 1!
In addition to a bug tracker report, the information will be shared with the trinity-devel and trinity-users mail lists as well as the Trinity RSS feed.
In the hope of encouraging short term goals, I am going to include a section called "Bug Report Focus," which will be intended to help developers and testers focus on areas needing help. I'll include only three bug reports each week. That list will change as the bugs are resolved.
My proposed Bug Report Focus for the next week:
Bug report 1169 Build issue: koffice FTBFS with libwpd >= 0.9
Bug report 976 "My Documents" device is broken
Bug report 975 Apps do not honor/use the Documents location set in user-dirs.dirs
The proposed Bug Report Focus is subject to change based upon feedback received through this email.
I'll post the news release Tuesday.
Thank you!
Darrell
Darrell,
please, a few days ago I have added to TDE another localization package -
gwenview-i18n. Also contains some docbook documentations. Please can you
help with docbook modifications and branding issues?
Thank you
Slavek
--
Tim,
1. Does TDEHWLIB require pmount? Although available as a third-party package --- something similar to PPAs --- pmount is not a stock package in Slackware. Slackware 14.0 no longer supports HAL but supports udisks, udisks2, and upower.
2. If -DWITH_HAL=ON and -DWITH_TDEHWLIB=ON, does TDEHWLIB override during run-time? If yes, can TDEHWLIB be disabled at run-time, or only during compiling?
Darrell