Message: previous - next
Month: March 2011

Re: [trinity-devel] Bugs, bugs, bugs

From: Darrell Anderson <humanreadable@...>
Date: Fri, 4 Mar 2011 19:17:38 -0800 (PST)
Here is a list of bugzilla reports I believe are unique to Trinity and not inherited from KDE3.

268, 'Headers Present But Cannot Be Compiled' Warning Messages When Compiling
288, kdelibs icon bug
289, KInfoCenter Not Purged from Desktop and Still Contains Two Modules
290, Libcarddav: Cannot build in Slackware 12.2
291, DCOPReply messages in xsession-error log
292, TQTinterface Build Bugs
294, KControl Zeroconf Service Discovery Module
296, New Trinity Profile Error Messages
299, Samba: Something in Trinity Tries to Access Samba Config Files
306, Desktop Device Icon Arrangement
320, Branding Issues
335, Konqueror Icon Activation Effect
339, Duplicating upstream efforts
343, Update Outdated Kaffeine
346, Building amarok refuses to support mp4 tag writing
346, Building amarok refuses to support mp4 tag writing
350, Source tarball permissions are goofy
363, ktorrent is not the most recent version
385, Unmounted removable device icons do not appear on the desktop
387, Kicker/Panel Clock Font Display Looks Weird
388, KDESU Dialog Box Behavior
389, Activation Effects
390, Akregator Fails to Fetch Feeds Without KRB5 Installed
392, Desktop Device Icon Placement
393, Incorrect kdesu Behavior When Opening Kate
394, Problems with DCOP After Using kdesu

Here is a list of bugzilla reports I believe were inherited from KDE3.

230, Amarok Keyboard Shortcuts Do Not Work Correctly
242, Akregator forces external browser to front
244, Kate: Restore ability to specify the number of files in the Most Recently Used list
251, Kicker/panel has no configuration option to stop scrolling among apps
252, Panel handle pointers (the black arrow heads) are too large.
257, Ark: Disabling the warning message associated with opening files in an external viewer.
258, ksmserver: Logout confirmation fadeaway is too slow with older hardware
259, kompare does not always terminate properly, leaving the process running
261, kompare default 'Compare Files or Folders' dialog box behavior is flawed
270, KFileDialog: Provide an option to disable tooltip popups when hovering over long file names
293, Kde-config Incorrectly Creates a Profile Folder in the System root directory
297, Numerous "X Error: BadWindow" and "X Error: BadAccess" Messages
298, Libpng Warning Messages
300, Scroll Bar Width
301, Kompare does not maintain a correct mru list
302, Akgregator does not provide a keyboard shortcut or menu option to select and delete all feeds.
303, Safely Unmount does not always remove the icon from the desktop
304, KAlarm does not accept date changes to existing reoccurring actions
305, Akregator provides no configuration option to ignore favicons
336, ksystemlog bugs and enhancements
347, Amarok Sym Links Incorrect
348, kdebindings man pages split into two locations
353, KOffice will not build with GraphicsMagick 1.3.12 or 1.2.10 installed
386, Show Desktop behavior
427, NumLock light does not reflect actual state

This list is incomplete. I did not peruse the entire bugzilla. I browsed the reports I filed and some of those that affect me but filed by others.

Because of the efforts to move to cmake, possibly 29 of the reports I filed could be closed after the transition to cmake proves successful. That is approximately 6.5% of the 451 reports on file. I have not listed any of those reports.

Bear in mind the KDE3 sources used to start the Trinity Project were from Kubuntu. The sources were not the generic sources directly from the upstream KDE repository. In other words, the first Trinity sources contained 'buntu patches that the generic version did not. Slackware used the unpatched generic sources from the upstream KDE repository. Therefore people familiar only with 'buntu might never have seen the problems reported in the bugzilla because they presume KDE has "always worked that way" when that is not the case. An example is the kdesu behavior. Because the 'buntu developers only support sudo, the kdesu tool is broken on a non 'buntu system.

I hope this helps. :)


--- On Fri, 3/4/11, Ilya Chernykh <neptunia@...> wrote:

> From: Ilya Chernykh <neptunia@...>
> Subject: Re: [trinity-devel] Bugs, bugs, bugs
> To: trinity-devel@...
> Date: Friday, March 4, 2011, 1:21 PM
> On Friday 04 March 2011 21:20:12
> Darrell Anderson wrote:
> > When are bugs going to receive attention?
> >
> > I don't eat my own dog food. Despite some
> enhancements, I continue using
> > KDE 3.5.10 rather than Trinity 3.5.12.
> >
> > I expended a lot of energy last autumn packaging
> Trinity 3.5.12 for
> > Slackware 12.2. My personal schedule prevented further
> packaging efforts,
> > but now that I again have some time, I am not
> motivated to package for
> > recent releases. Why? There are many usability bugs
> that render Trinity
> > frustrating. Many of which do not exist in KDE
> 3.5.10.
> Do you have a list of bugs that were introduced in Trinity
> and were not 
> present in KDE 3.5.10?
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: trinity-devel-unsubscribe@...
> For additional commands, e-mail: trinity-devel-help@...
> Read list messsages on the Web archive:
> Please remember not to top-post: