tde-devels

devels@trinitydesktop.org

3 participants
3808 discussions

X Error: BadWindow
by Darrell Anderson 20 Sep '10

20 Sep '10

X Error: BadWindow (invalid Window parameter) X Error: BadAccess (attempt to access private resource denied) For as long as I can remember, anybody using KDE has seen these superfluous messages in their xsession log. The messages are annoying. FWIW, occasionally I start Xfce for some oddball testing and I don't see the messages. I'm guessing the problem is unique to legacy KDE code. Is there something specific in the KDE/Trinity code that causes X to respond with those messages? You have impressed me many times with your ability to patch the old sloppy KDE code. I think if you could solve this problem you would add one dandy looking feather to your cap! Darrell

1 0

First Trinity 3.5.12 Usability Test
by Darrell Anderson 20 Sep '10

20 Sep '10

My first usability test of Trinity was in a virtual machine. Trinity loaded just fine --- but ignored all of my previous ~/.kde profile settings. Hey! What? :) Not to mention the evil bouncing mouse cursor! Okay, I can solve that irritant when I build the package. What happened with my desktop? First clue: Trinity is using ~/.kde3 rather than ~/.kde. Yet my $KDEHOME environment variable is set to ~/.kde. Hmm. Where is this being ignored or overridden? Yes, I can rename ~/.kde to ~/.kde3. But I should not have to. Trinity should honor my $KDEHOME variable. First suspect: /usr/bin/startkde. I have some proposed patches for startkde, but that can wait for another thread. Nope. Not the culprit because I exited KDE, restored my ~/.kde profile, renamed the new startkde, and restored my old startkde. When I started X, Trinity again created ~/.kde3 and ignored my ~/.kde profile and $KDEHOME variable.. What is hard-coded to create and use ~/.kde3? A .desktop file somewhere? Been a looooong time since I wandered around with the KDE startup sequence. Second, there are folder icons on the desktop for every directory in the root level. They are not device icons and I don't know how to disable that effect. I also have lost my previous desktop icons. Third, something is starting the HP system tray. I remember that being an annoyance three or four years ago, but I don't remember how to stop that. There is a file in /etc/xdg/autostart, but there is one in my office system too and the tray does not start there. Fourth, There are messages in xsession-errors that seem to indicate something accessing samba, a service I don't have started in the virtual machine. Fifth, the Klipper tray icon is huge and does not display completely in the tray --- the top and bottom of the icon are missing. I don't seem to find anything in kcontrol/icons. Sixth, the color of my konsole changed from black to white. I realize some of the problems might be cause by using a 3.5.10 profile, but then again perhaps not. I'm suffering a bit from new culture shock. 3.5.12 is not 3.5.10. I did not expect so many configuration changes, however. :) If I have to start with a new profile and rebuild the profile I have been using for several years I am likely to become manic depressive. Suddenly I feel very tired!

3 19

libpng warnings
by Darrell Anderson 20 Sep '10

20 Sep '10

Open the Configure Panel dialog box. Select the Appearance option. The following (.xsession-errors) messages appear immediately. libpng warning: Ignoring gAMA chunk with gamma=0 libpng warning: Ignoring attempt to set negative chromaticity value libpng warning: Ignoring attempt to set cHRM RGB triangle with zero area Repeatable with an existing 3.5.10 or new Trinity profile. The messages probably are generated by libpng, but only happens when opening Appearances. I thought the problem was related to using button backgrounds, but selecting "Default" causes the messages too. I checked and see the error messages in 3.5.10 too. Thus, some legacy code is causing these messages in Trinity. Based on the context of the messages I suspect something in the Trinity/KDE code is not accessing the libpng libraries correctly. Darrell

1 0

Toolbar grabber handle artifacts
by Darrell Anderson 19 Sep '10

19 Sep '10

I discovered how to create the problem. The artifact issue in the toolbar grabber handles appears when using certain widget styles (KControl, Appearance & Themes, Style). Several widget styles are affected: B3/KDE HighColor Classic KDE Classic Keramic Phase Rather than a grabber handle, the artifacts display text rather than a grabber handle. When I increase the konqueror tool bar icon size to 48 pts, I see the following text: olbar (Ko With Kedit I see the text: Toolbar (K With KLinkstatus: nksToolB With QuantaPlus: oolbar (Q With Shisen-Sho (game): lbar (Shis Hopefully those snippets of text provide a clue from where the text is derived. This problem affects all apps with toolbar grabber handles. Originally I discovered the problem with Konqueror, but I can duplicate in any app with toolbars: Kate, KEdit, Kompare, etc. The problem is universal. Originally I thought the problem was only with root and only with an existing kde profile. I can duplicate the problem with non-root users as well as in new Trinity profiles. I cannot replicate the behavior in 3.5.10. I hope this helps! Darrell

1 1

Building Trinity on BLFS - fixx11h.h
by Leandro Nini 19 Sep '10

19 Sep '10

Forgot to report another error: In file included from /opt/qt/include/tqimage.h:32:0, from /opt/trinity-3.5.12/include/kaboutdata.h:24, from main.cc:24, from libkdeinit_kdesktop_la.all_cc.cc:2: /opt/qt/include/qimage.h: In member function bool QImageTextKeyLang::operator<(const QImageTextKeyLang&) const: /opt/qt/include/qimage.h:61:61: warning: suggest parentheses around && within || In file included from main.cc:52:0, from libkdeinit_kdesktop_la.all_cc.cc:2: /usr/include/X11/extensions/Xrender.h: At global scope: /usr/include/X11/extensions/Xrender.h:75:5: error: reference to Bool is ambiguous /usr/include/X11/Xdefs.h:47:13: error: candidates are: typedef int Bool /opt/trinity-3.5.12/include/fixx11h.h:65:15: error: typedef X::XBool X::Bool /usr/include/X11/extensions/Xrender.h:75:5: error: Bool does not name a type /usr/include/X11/extensions/Xrender.h:80:5: error: reference to Bool is ambiguous /usr/include/X11/Xdefs.h:47:13: error: candidates are: typedef int Bool /opt/trinity-3.5.12/include/fixx11h.h:65:15: error: typedef X::XBool X::Bool /usr/include/X11/extensions/Xrender.h:80:5: error: Bool does not name a type /usr/include/X11/extensions/Xrender.h:203:1: error: reference to Bool is ambiguous /usr/include/X11/Xdefs.h:47:13: error: candidates are: typedef int Bool /opt/trinity-3.5.12/include/fixx11h.h:65:15: error: typedef X::XBool X::Bool /usr/include/X11/extensions/Xrender.h:203:1: error: Bool does not name a type /usr/include/X11/extensions/Xrender.h:213:1: error: reference to Bool is ambiguous /usr/include/X11/Xdefs.h:47:13: error: candidates are: typedef int Bool /opt/trinity-3.5.12/include/fixx11h.h:65:15: error: typedef X::XBool X::Bool /usr/include/X11/extensions/Xrender.h:213:1: error: Bool does not name a type In file included from libkdeinit_kdesktop_la.all_cc.cc:2:0: main.cc: In function int kdemain(int, char**): main.cc:220:67: error: XRenderQueryExtension was not declared in this scope In file included from /opt/trinity-3.5.12/include/kfileitem.h:31:0, from ../libkonq/konq_iconviewwidget.h:27, from kdiconview.h:23, from krootwm.cc:57, from libkdeinit_kdesktop_la.all_cc.cc:3: /opt/trinity-3.5.12/include/kfilemetainfo.h: At global scope: /opt/trinity-3.5.12/include/kfilemetainfo.h:1237:34: warning: type qualifiers ignored on function return type In file included from krootwm.cc:62:0, from libkdeinit_kdesktop_la.all_cc.cc:3: /opt/trinity-3.5.12/include/netwm.h:1145:5: error: reference to Bool is ambiguous /usr/include/X11/Xdefs.h:47:13: error: candidates are: typedef int Bool /opt/trinity-3.5.12/include/fixx11h.h:65:15: error: typedef X::XBool X::Bool /opt/trinity-3.5.12/include/netwm.h:1145:5: error: Bool does not name a type /opt/trinity-3.5.12/include/netwm.h:1172:32: error: reference to Bool is ambiguous /usr/include/X11/Xdefs.h:47:13: error: candidates are: typedef int Bool /opt/trinity-3.5.12/include/fixx11h.h:65:15: error: typedef X::XBool X::Bool /opt/trinity-3.5.12/include/netwm.h:1172:32: error: Bool has not been declared /opt/trinity-3.5.12/include/netwm.h:1267:26: error: reference to Bool is ambiguous /usr/include/X11/Xdefs.h:47:13: error: candidates are: typedef int Bool /opt/trinity-3.5.12/include/fixx11h.h:65:15: error: typedef X::XBool X::Bool /opt/trinity-3.5.12/include/netwm.h:1267:26: error: Bool has not been declared /opt/trinity-3.5.12/include/netwm.h:1457:99: error: reference to Bool is ambiguous /usr/include/X11/Xdefs.h:47:13: error: candidates are: typedef int Bool /opt/trinity-3.5.12/include/fixx11h.h:65:15: error: typedef X::XBool X::Bool /opt/trinity-3.5.12/include/netwm.h:1457:99: error: Bool has not been declared In file included from libkdeinit_kdesktop_la.all_cc.cc:3:0: krootwm.cc: In member function void KRootWm::initConfig(): krootwm.cc:248:10: warning: unused variable startup In file included from libkdeinit_kdesktop_la.all_cc.cc:5:0: kdiconview.cc: In member function void KDIconView::updateWorkArea(const QRect&): kdiconview.cc:1507:13: warning: unused variable dummy In file included from libkdeinit_kdesktop_la.all_cc.cc:8:0: bgmanager.cc: At global scope: bgmanager.cc:399:6: warning: unused parameter viewport make[3]: *** [libkdeinit_kdesktop_la.all_cc.lo] Errore 1 make[3]: Leaving directory `/usr/src/KDETrinity/20100918/kdebase-20100918/kdesktop' Fixed this by removing the fixx11h.h include from headers in the kdesktop directory, namely minicli_ui.ui and kdesktopapp.h, as recommended in the file itself: [...]put #include <fixx11h.h> in the .cpp file (not .h file!)[...] Regards, Leandro -- Caselle da 1GB, trasmetti allegati fino a 3GB e in piu' IMAP, POP3 e SMTP autenticato? GRATIS solo con Email.it: http://www.email.it/f Sponsor: Prova subito Emailpaghe, e' in prova gratuita sino al 31 dicembre 2010 e in pochi clik fai paghe e stipendi per la tua azienda! Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=10683&d=20100919

1 0

Resolved Trinity Issues as of SVN 1176785
by Darrell Anderson 18 Sep '10

18 Sep '10

* Kicker/panel does not exist. Resolved in SVN 1176785. * Trinity creates ~/.kde3 for cache, socket, and tmp directories, but only for root with an existing kde profile. Explicitly declaring KDEROOTHOME in startkde stops the problem. Resolved in SVN 1176545. * Klipper icon for root using existing an kde profile is larger than panel height. Resolved in SVN 1176545. * "Add applet" dialog box is too small. Resolved in SVN 1176785. * Splash, sidebar, and kpersonalizer branding. Resolved in SVN 1176545 and 1176785. * Panel icons flash and grow momentarily when selected. No disable mechanism. Resolved in SVN 1176545. Panel icons now have an option to disable. * "xset: bad font path element" nuisance message. Resolved in SVN 1176545. Good job! Darrell

1 0

Building koffice
by Darrell Anderson 18 Sep '10

18 Sep '10

This is a large package and build failures do not occur until well into the build process. Painfully slow. :) So let's move one step at a time. I would like to ignore previous koffice FTBFS reports. Start clean, now that the core packages all build and we have a known foundation and baseline. The first failure errors seem to be related to wv2, an MS Word import package. I'm still building packages on Slackware 12.2. That release came with wv2 0.2.3. Release 13.0 uses 0.2.3. The wv2 package was updated to 0.4.2 in Slackware 13.1. Unless there is no choice, I believe 12.2 and 13.0 users should not have to update the wv2 package to build or install koffice. Certainly that might be required, but I prefer to work from the thesis that Trinity KDE should build and install on previous KDE 3.5.10 distros without such tinkering. Previously we thought the failure was caused by an old version of wv2. Yet Lenny uses the same 0.2.3 version. Trinity koffice builds for that operating system. Thus we should proceed with the presumption the problem is not wv2 directly but the build process. As we have discovered the past several weeks, what builds on Debian does not always build on Slackware without some modifications. We don't know why but that is not important right now. :) When I build koffice on 12.2 with wv2 0.2.3 installed, the first fatal build errors I receive: document.cpp:393: error: 'const struct wvWare::Word97::BRC' has no member named 'cv' I'm no C++ programmer, but seems some constants are not being used correctly or as expected or are not being declared correctly. Note: Koffice builds successfully with no errors when wv2 is not installed. I suspect only a few people will be interested in that version. Most people want basic MS Word import functions. Log attached! Darrell

3 10

Wrong Konsole Settings
by Darrell Anderson 18 Sep '10

18 Sep '10

I'm using my existing 3.5.10 ~/.kde profile. I mentioned this quirk previously. When I start KDE 3.5.10, my konsole has a black background with tabs on the top. That is what I want. When I start Trinity KDE, my konsole has a white background with tabs on the bottom. Pretty good way to irritate new users migrating to Trinity from 3.5.10. :) I have seen this behavior before --- in Debian Lenny. I never traced the cause. I guess now I will. As the Trinity KDE sources were started from Debian Lenny rather than from the stock 3.5.10, I suspect Trinity is carrying some weird baggage from Debian Lenny. I do not believe any user configuration files are being changed. My reasoning is I can exit Trinity, log in two seconds later in 3.5.10, and konsole is black with tabs on top. I presume some *.desktop file somewhere defines the default konsole in Debian/Trinity as white background and tabs on bottom. I don't care for that default selection, but my user configuration should prevail. Why are the user configuration files being ignored for konsole? If I understand correctly: 1. Color schemes are controlled by schema files in /usr/share/apps/konsole. 2. The preferred user scheme is defined in ~/.kde/share/apps/konsole/shell.desktop. 3. If ~/.kde/share/apps/konsole/shell.desktop does not exist then the system default Konsole is used. 4. The default Konsole schema is defined in /usr/share/apps/konsole/linux.desktop and shell.desktop. 5. In both 3.5.10 and Trinity, the default schema in linux.desktop is Linux.schema. 6. Linux.schema is the same in both 3.5.10 and Trinity. 7. shell.desktop is the same in both 3.5.10 and Trinity. 8. I'm unsure how to read the schema files, but I think the background color in Linux.schema is black. At this point I'm lost as to why Trinity opens konsole with a white background and tabs on the bottom. Darrell

2 7

Re: [trinity-devel] The Default Trinity Desktop
by Timothy Pearson 18 Sep '10

18 Sep '10

> I temporarily renamed the ~/.kde directory so Trinity would create a new profile directory. > Beauty is always subjective, but I think Trinity should change some of the > old die-hard KDE defaults. As you mentioned previously, Trinity is now the > upstream source, not KDE. You now are the man. Be bold. Be different. :) I agree for the most part, but we must be careful not to be bold and different in the KDE4 style. ;-). Sometimes minor changes are OK in small quantities between releases, but usually large, sweeping changes will start alienating the types of users that are interested in this project. > So here are some thoughts about the default Trinity desktop. > 1. As you seem keen on changing references from KDE to Trinity, you might > want to consider a new splash image. Likewise for your side image in the K-Menu. Done. Thank goodness for the GIMP! > 2. I always found the KDE-Classic Icon Theme somewhat unpleasant. The Crystal SVG icon set is popular and cleaner. Agree; it looks like the default is already set to crystalsvg in the code though? > 3. I never understood the blind acceptance of four virtual desktops. Most > new users will appreciate two. Sorry; I don't agree here. I can't imagine life without four desktops (and I have two 21" screens per desktop)! While this usage case may be a bit extreme, this feature is still a major productivity enhancer compared to Window$/Mac, therefore I think it should be emphasized as much as possible. Also on a more practical note, IIRC other Linux DEs use four desktops by default. If you want to create a separate default for Slackware that could be done quite easily; I do that for the stock "cartoon" version of Kubuntu each release. > 4. With only two virtual desktops, the Small panel can be used as a default. Same with four; changed. > 5. Digital clocks are geeky. Just choose Plain as the default. Agree; changed. > 6. Change the default desktop icon text to non-shadowed, white. Not sure on this one; the non-shadowed icons blend in to certain desktop wallpapers and this may confuse users over time. Any thoughts from other list members? > 7. Get rid of the bouncing mouse cursor. :) Yeah, I mentioned that already. I'm making a not-so-subtle point. The thing is obnoxious. Stupid, > Dumb. Irritating. Annoying. Childish. Unprofessional. I greatly appreciate > any distro I test where the devs have changed the default mouse pointer to > Non Busy. And quite a few devs have done that too. Fully agree; I thought I already got rid of it though? > 8. None of the desktop device icons are enabled. You went through the effort to create many new useful icons, so why not add them and set enable > Device Icons as the default? Agree; changed. > 9. I don't understand the fetish and dumbing down with the default view in > Konqueror with icons. Set the default view to Tree View, and Show Hidden Files. Treat users like adults and not kids. :) Sorry, disagree. I like the intuitive icon view myself, and even by their name, hidden files are supposed to be hidden! ;-) I can see too many "oops, I just dragged and dropped my .<critical system file> who knows where and now I can't use my computer" type complaints cropping up. > 10. A bug: when I select the desktop Web Browser Device Icon, I receive an > error message: Unknown host default.browser. The message box has an OK button but the message box disappears by itself in about 1.5 seconds. Insufficient time to actually read without repeating the process a few times. Fixed. > 11. A bug: Selecting the My Documents Device Icon results in an error because the ~/Documents directory does not exist. I personally would get upset if any software created such a directory on my system. On the other > hand, I think when a person explicitly enables that device icon then such > a directory should get created. No, not quite. I think when a person enables that directory a pop-up should appear asking for the path to that > directory. The default would be ~/Documents, but the user can change the text in the popup text box. I don't consider that a feature request needing to be added after your feature freeze. I consider this behavior a > bug. Fixed; the shortcut now queries XDG for the documents directory path. > 12. I'm glad you selected to display both software names and descriptions > in the K-Menu. I always empathize with new users and they need both. Flip > a coin, but I prefer Description (Name) rather than Name (Description). My > belief is that most people are looking to solve a task and a description first helps toward that goal. Especially since so many developers have given their apps names that provide no clue to the apps purpose. The problem is that descriptions can change; e.g. become more descriptive. Change the first letter in the description and the user has to hunt through the entire list to find the same application again. > 13. So you added the option to use a Kickoff style K-Menu. Nice > programming touch. Really! You'll never see me use the Kickoff though. I'm > just too old to change some habits. :) > 14. Place the Exit/Lockout applet buttons on the default kicker. Many people use the buttons and they provide a familiar method to exit for new > users. Agree; changed. > 15. Trinity did not create a new ~/.kde3 directory, but honored $KDEHOME and created a new ~/.kde! > I hope this helps! Sure does! Update kdelibs and kdebase to SVN revision 1176514 or above, recompile both, and re-test everything. I believe I have repaired most of the bugs, including the Klipper icon (thanks to your latest message regarding applet mode, which allowed me to reproduce the bug here). Let me know if anything fishy shows up in testing, or if I forgot to address an issue! Thanks, Tim

4 9

HPLIP Mysteries
by Darrell Anderson 18 Sep '10

18 Sep '10

At this point I believe the reason I don't see those HPLIP messages when I start 3.5.10 is 3.5.10 is not fully xdg compliant. If I'm wrong then I have no other explanation why I never see those messages in 3.5.10. That I was seeing the messages in Trinity and not in 3.5.10 was a red herring. Yet Trinity is not fully compliant either. :( Test Results: In my 3.5.10 system, with my testing account, I removed the hplip.desktop file from ~/.config/autostart. I started 3.5.10 and there were no messages about HPLIP. I have a second KDEDIR directory. I purposely assigned 700 permissions to that directory to prevent any *.desktop files there from overriding KDE defaults. Again no HPLIP messages. Yet the service does not try to run in my 3.5.10 system. What did I do long ago in 3.5.10 to prevent HPLIP from starting? Maybe nothing? After much testing and web searching I started to wonder whether the original KDE 3.5.10 is broken with respect to xdg autostart requirements. Not a far stretch to believe since we have seen that 3.5.10 does not recognize or honor the ~/.config/autostart directory. Trinity is almost fully xdg compliant but not quite. I see the HPLIP messages because Trinity is correctly reading the contents of /etc/xdg/autostart. Is Trinity recognizing the ~/.config/autostart directory? Yes. In the past I used the ~/.config directory for non-KDE apps. Once in a while I run tests in Xfce. Xfce does honor the autostart directory. Trinity does too. I know this because when I start Trinity for the first time with no kde profile, a new profile gets created. My conky display starts. The only place Trinity can find that directive is the ~/.config/autostart directory. I'm concluding that Trinity honors the ~/.config/autostart directory. But does not recognize exceptions. When I run Trinity and I have the ~/.config/autostart/hplip-systray.desktop file set to Hidden=True, I still see the HPLIP messages in the log. This seems to be a bug with respect to full xdg autostart compliance. Initially I thought the Hidden=true directive in ~/.config/autostart/hplip.desktop only hides the tray icon and does not necessarily stop the service from trying to run. But that is not the effect I see in Xfce. When I set Hidden=False in the ~/.config/autostart/hplip-systray.desktop file, I see the same HPLIP messages in the log. When I set Hidden=True I no longer see the HPLIP messages. Thus the file in ~/.config/autostart fully controls whether the service in /etc/xdg/autostart actually starts. As another test, in 3.5.10, I copied the /etc/xdg/autostart/hplip-systray.desktop file to ~/.config/autostart. No related messages found in the log. I exited KDE and moved the file to ~/.kde/Autostart. I then saw the same messages in the log. SUMMARY: 3.5.10 is not fully xdg compliant and that is why I see no related messages. Trinity is mostly xdg compliant and that is why I see the messages in the log. Yet for some reason Trinity is not honoring the Hidden=True directive in the ~/.config/autostart/hplip-systray.desktop file and I still see the HPLIP messages when I should not. Xfce does this as expected. Perhaps the Xfce code might help with getting Trinity fully xdg compliant. I have the source code here. Tell me what to look for and I can forward appropriate snippets.

2 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels