tde-devels

devels@trinitydesktop.org

2 participants
3755 discussions

by Darrell Anderson

I have always been suspect of all the cmake conversions as being incomplete. Some obvious examples include tdemultimedia and tdewebdev. Conversions were started but never completed. Other examples include amarok (bug reports 818, 1917). Last night I noticed a directory in tdepim that does not compile because no CMakeLists.txt file was created during the cmake conversion. There are other cmake issues, such as no cmake macro was written for converting man page docbook files to man pages. The automake packages still compile fine but the cmake converted packages no longer build the man pages. (Bug report 1830.) I don't know how we should audit the cmake conversion process. Possibly one way is search the source tree in the known conversions for Makefile.am and look for a coexisting CMakeLists.txt. That does not mean the conversion is complete but would expose certain incomplete conversions as I discovered last night in tdepim. We need a way to audit cmake conversions. Any ideas? Darrell

10 years, 12 months

Re: [trinity-devel] Latest Build broke ALSA sound (play works - aplay screaches)

by Darrell Anderson

>> This is getting stranger: >> >> Darrell, you were correct, aplay will play .wav files just >fine. I rebuilt >> both arts and tdemultimedia - no change. From the command line, >both 'play' and >> 'aplay' work fine, but TDE will not play any sound. I open >kcontrol -> Sound >> System -> [Test Sound] and I get nothing. I click the litte |> >next to any sound >> event file - same result, no sound. >> >> Checking .xsession-errors, each time I try playing the a >sound, I get the >> following: >> >> unix_connect: can't connect to server >> (unix:/tmp/tdesocket-david/localhost.localdomain-02d0-52f9c6b6) >> unable to connect to sound server >> unix_connect: can't connect to server >> (unix:/tmp/tdesocket-david/localhost.localdomain-02d0-52f9c6b6) >> unable to connect to sound server >> unix_connect: can't connect to server >> (unix:/tmp/tdesocket-david/localhost.localdomain-02d0-52f9c6b6) >> unable to connect to sound server >> unix_connect: can't connect to server >> (unix:/tmp/tdesocket-david/localhost.localdomain-02d0-52f9c6b6) >> unable to connect to sound server >> [tdeinit] Got EXEC_NEW 'artsd' from launcher. >> [tdeinit] artsd is executable. Launching. >> unix_connect: can't connect to server >> (unix:/tmp/tdesocket-david/localhost.localdomain-02d0-52f9c6b6) >> unable to connect to sound server >> [artsd] There are already artsd objects registered, looking if >they are active... >> unix_connect: can't connect to server >> (unix:/tmp/tdesocket-david/localhost.localdomain-02d0-52f9c6b6) >> unable to connect to sound server >> [artsd] ... cleaned 5 unused mcop global references. >> >> server status: running, will suspend in 6 s >> real-time status: no real-time support >> server buffer time: 53.288 ms >> buffer size multiplier: 1 >> minimum stream buffer time: 53.288 ms >> auto suspend time: 7 s >> audio method: alsa >> sampling rate: 44100 >> channels: 2 >> sample size: 16 bits >> duplex: half >> device: default >> fragments: 10 >> fragment size: 940 >> [tdeinit] Got EXT_EXEC 'knotify' from launcher. >> artsd: symbol lookup error: /opt/trinity/lib/libarts_xine.so.0: >undefined >> symbol: ao_new_port >> [tdeinit] Got EXEC_NEW '/opt/trinity/bin/artsd' from socket. >> [tdeinit] /opt/trinity/bin/artsd is executable. Launching. >> [artsd] There are already artsd objects registered, looking if >they are active... >> unix_connect: can't connect to server >> (unix:/tmp/tdesocket-david/localhost.localdomain-02e1-52f9c6c6) >> [artsd] ... cleaned 5 unused mcop global references. >> >> Checking /tmp/tdesocket-david/localhost.localdomain-02d0- >52f9c6b6, it is there >> and easily accessible, so I don't know what that unix_connect >error is all >> about. The bottom line, something is active very differently >with this set of >> package regarding sound. Let me know if you have any other >thoughts. We'll look >> at this more later. >> > >Just so it is clear. After update from the packages built on 1/29 >to packages >built on 2/8, sound event notifications no longer work in TDE. >Using play or >aplay from the command line in konsole, both WORK FINE: > >02:37 valhalla:~> aplay >/opt/trinity/share/sounds/KDE_Window_Open.wav >Playing WAVE '/opt/trinity/share/sounds/KDE_Window_Open.wav' : >Signed 16 bit >Little Endian, Rate 22050 Hz, Stereo >02:37 valhalla:~> play /opt/trinity/share/sounds/KDE_Startup_1.ogg > >/opt/trinity/share/sounds/KDE_Startup_1.ogg: > > File Size: 124k Bit Rate: 125k > Encoding: Vorbis > Channels: 2 @ 16-bit >Samplerate: 44100Hz >Replaygain: off > Duration: 00:00:07.95 > >In:100% 00:00:07.95 [00:00:00.00] Out:382k [ | ] >Hd:0.1 Clip:3 >play WARN rate: rate clipped 2 samples; decrease volume? >play WARN dither: dither clipped 1 samples; decrease volume? >Done. > > However, as soon as any sound event in TDE is triggered (such as >on shade), I >get the following dumped into the .xsession-errors file: > >unix_connect: can't connect to server >(unix:/tmp/tdesocket-david/localhost.localdomain-04ac-52f9cdd8) >(The previous message was repeated 2 times.) >unix_connect: can't connect to server >(unix:/tmp/tdesocket-david/localhost.localdomain-04e5-52f9cde2) >[tdeinit] Got EXEC_NEW '/opt/trinity/bin/artsd' from socket. >[tdeinit] /opt/trinity/bin/artsd is executable. Launching. >[artsd] There are already artsd objects registered, looking if >they are active... >[artsd] ... cleaned 5 unused mcop global references. > >/opt/trinity/bin/artsd: symbol lookup error: >/opt/trinity/lib/libarts_xine.so.0: >undefined symbol: ao_new_port >unix_connect: can't connect to server >(unix:/tmp/tdesocket-david/localhost.localdomain-04e5-52f9cde2) >(The previous message was repeated 1 times.) >unix_connect: can't connect to server >(unix:/tmp/tdesocket-david/localhost.localdomain-05c9-52f9e0cf) >[tdeinit] Got EXEC_NEW '/opt/trinity/bin/artsd' from socket. >[tdeinit] /opt/trinity/bin/artsd is executable. Launching. >[artsd] There are already artsd objects registered, looking if >they are active... >[artsd] ... cleaned 5 unused mcop global references. > >/opt/trinity/bin/artsd: symbol lookup error: >/opt/trinity/lib/libarts_xine.so.0: >undefined symbol: ao_new_port > > So where is TDE trying to make the call for the sound event >resulting in the >unix_connect error? Yeah, Linux is ready for the desktop.... You have tested sound with the aplay and play commands, which validates your hardware and alsa. Start an alternate desktop to at least isolate the problem to only Trinity. I don't know about the above messages, but seems arts is not starting or is not loading completely. Another idea is permissions. I quite often log into my desktop as root to test permissions issues. Not tdesu, actually logging in as root. I don't prescribe to any aspect of the anti-root religion and logging in as root is a quick way to determine whether a problem is permissions related. Also try with a fresh profile. I have a couple of testing accounts I use to try various things without touching my normal accounts. With the testing accounts often I 'mv ~/.trinity ~/.trinity.bak' and then start Trinity. That creates a new ~/.trinity profile directory. When I finish testing I 'rm ~/.trinity' and then 'mv ~/.trinity.bak ~/.trinity'. With a fresh profile directory you should hear the stupid login sound file if arts is loading correctly. This at least narrows the issue to your profile or Trinity in general. When I have arts issues I delete the tdesycoca cache files, ~/.mcop, and all the Trinity socket and temporary files. This is a big reason I don't use graphical logins. I can exit X and be back to the command line without worrying that the login manager and X are still running. Provides an easy way to debug and delete files. I also just now remembered there is an arts config file. Once upon a time in the KDE3 days that file caused problems with one of the options, but I no longer remember the details. Anyway, try renaming ~/.trinity/share/config/kcmartsrc. And yeah, the tdemultimedia conversion to cmake never was completed. Darrell

10 years, 12 months

Re: [trinity-devel] Latest Build broke ALSA sound (play works - aplay screaches)

by Darrell Anderson

> It sounded great. So checking, play is provided by sox 14.4.1-4. >That begs the >question, Why does play work fine but aplay fail? I believe aplay does not support ogg and only supports wav. Don't ask --- I don't know why. Darrell

10 years, 12 months

Latest Build broke ALSA sound (play works - aplay screaches)

by David C. Rankin

All, I just installed all of the packages from the 2/8 - 2/10 build. The initial display of khelpcenter worked fine, but I noticed that I had no sound. After fighting with sound in the first set of packages, I was surprised that sound would just quit working in the latest set. I then opened konsole and tried: 21:52 valhalla:~> aplay /opt/trinity/share/sounds/KDE_Startup_1.ogg Playing raw data '/opt/trinity/share/sounds/KDE_Startup_1.ogg' : Unsigned 8 bit, Rate 8000 Hz, Mono I got a horrible screaching sound from speakers. I then tried: 21:52 valhalla:~> play /opt/trinity/share/sounds/KDE_Startup_1.ogg /opt/trinity/share/sounds/KDE_Startup_1.ogg: File Size: 124k Bit Rate: 125k Encoding: Vorbis Channels: 2 @ 16-bit Samplerate: 44100Hz Replaygain: off Duration: 00:00:07.95 In:100% 00:00:07.95 [00:00:00.00] Out:382k [ | ] Hd:0.1 Clip:4 play WARN rate: rate clipped 2 samples; decrease volume? play WARN dither: dither clipped 2 samples; decrease volume? Done. It sounded great. So checking, play is provided by sox 14.4.1-4. That begs the question, Why does play work fine but aplay fail? Suggestions? -- David C. Rankin, J.D.,P.E.

10 years, 12 months

Patch to add trash can configuration dialog to set storage limits

by Darrell Anderson

I found a 3.5.9 patch to add a trash can dialog to set trash storage limitations. The dialog would look like this: http://tokoe-kde.blogspot.com/2008/08/size-limits-for-trash.html The patch did get submitted in the KDE bugzilla but never got merged into 3.5.x. I converted the patch to TQt3 and added an option to populate the konqueror configuration dialog with a trash icon that should show the same dialog. The patch fails to build for me: /dev/shm/tdebase/tdeioslave/trash/ktrashpropsdlgplugin.cpp:226: undefined reference to `TrashImpl::trashDirectories() const' /dev/shm/tdebase/tdeioslave/trash/ktrashpropsdlgplugin.cpp:141: undefined reference to `TrashImpl::trashDirectories() const' /dev/shm/tdebase/tdeioslave/trash/ktrashpropsdlgplugin.cpp:61: undefined reference to `TrashImpl::TrashImpl()' /dev/shm/tdebase/tdeioslave/trash/ktrashpropsdlgplugin.cpp:62: undefined reference to `TrashImpl::init()' If you are interested then I have attached the patch to bug report 1923. Darrell

10 years, 12 months

Re: [trinity-devel] undefined symbols in all builds

by Darrell Anderson

>Ok, I have the ultimate solution. > >Because 'cppeditor' utilizes many parts of the 'editor', it seems >useful >(perhaps only possible), leave visible 'everything' from the >editor. Drop previous patches and try only this attached. I rebuilt tqt3 and tdebase and my build logs and error log are again quiet. Thank you. Is this something I have to run all the time or will this be pushed to git? Darrell

10 years, 12 months

Re: [trinity-devel] undefined symbols in all builds

by Darrell Anderson

>I am running multiple builds of tqt3 so you will be able to see >how >each build run results in a different 'undefined symbol' message. When building from git and no additional patching, I saw a slew of the following "undefined symbol" errors: ============================================ /dev/shm/tqt3/plugins/designer/libcppeditor.so: undefined symbol: _ZN6Editor11eventFilterEP8TQObjectP7TQEvent ============================================ This is what started the mess. With your proposed patch from earlier today, I then saw a slew of the following "undefined symbol" errors: ============================================ /dev/shm/tqt3/plugins/designer/libcppeditor.so: undefined symbol: _ZN6Editor13keyPressEventEP10TQKeyEvent ============================================ After seeing what you did in your patch --- while having no idea how any of this works, I looked at the previous build log and added another Q_EXPORT. The modified snippet added to your patch: ============================================ -void Editor::keyPressEvent( TQKeyEvent *e ) +Q_EXPORT void Editor::keyPressEvent( TQKeyEvent *e ) ============================================ With that updated patch, I see another new slew of "undefined symbol" errors: ============================================ /dev/shm/tqt3/plugins/designer/libcppeditor.so: undefined symbol: _ZN6Editor16doKeyboardActionEN10TQTextEdit14KeyboardActionE ============================================ So I continue this game and I add this snippet to the patch: ============================================ -void Editor::doKeyboardAction( KeyboardAction action ) +Q_EXPORT void Editor::doKeyboardAction( KeyboardAction action ) ============================================ With that updated patch, I see yet another slew of the following "undefined symbol" errors: ============================================ /dev/shm/tqt3/plugins/designer/libcppeditor.so: undefined symbol: _ZN6Editor16doChangeIntervalEv ============================================ According to how this game seems to play I should next do this: ============================================ -void Editor::doChangeInterval() +Q_EXPORT void Editor::doChangeInterval() ============================================ At this point I give up. Darrell

10 years, 12 months

Re: [trinity-devel] undefined symbols in all builds

by Darrell Anderson

>Search in the build-log 'cppeditor' in the context with linking. Here is a full build log: http://humanreadable.nfshost.com/misc/trinity-tqt3-pre_R14.0.0-i586- 14.1_32_git_3285_1-build.log Darrell

10 years, 12 months

Re: [trinity-devel] undefined symbols in all builds

by Darrell Anderson

>I'm going back to the beginning. > >I'm trying to find where is linked tqt3 plugin cppeditor - >elsewhere than >in tqt3, but I cannot find any place. Please, can you see where it >is linked in your builds? What do I look for? Darrell

10 years, 12 months

Re: [trinity-devel] undefined symbols in all builds

by Darrell Anderson

>You can be sure that I patch tested several times. > >Initial patch from François caused FTBFS (as you can find earlier >in the >mailing-list http://trinity-devel.pearsoncomputing.net/?0::11678 >). So I >worked on the patch longer time and tested on various versions of >Debian / Ubuntu distributions. Patch to solve the problem of >hidden-visibility was published on 20 January (see >http://bugs.pearsoncomputing.net/show_bug.cgi?id=1560#c111 ). In >testing I >tested building tdelibs, tdebase and tdevelop (which is the only >one who >used tqassistant). After all the testing I pushed patches on 2 >Feb. I'm sure you tested. You almost always do. All I'm saying is none of us were invited to test. If I had run the patches a week ago I would have discovered the messages immediately. The messages snuck past me for the past few days because I'm knee deep in working on the help handbooks and I'm not building fresh package sets as often. In the bug report you mention hidden visibility and shared versus static. In my tqt3 build script configuration I am using "-shared" and I have used that option from the beginning. I don't have any configuration option about visibility like other build script configurations. When I run configure --help I don't see any options related to visibility. Should I? My build log is filled with "- fvisibility=hidden -fvisibility-inlines-hidden." I am running multiple builds of tqt3 so you will be able to see how each build run results in a different 'undefined symbol' message. Darrell

10 years, 12 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels