tde-devels

devels@trinitydesktop.org

4 participants
3812 discussions

Re: [trinity-devel] qt3 API incompatiblity with qt3 programs
by Darrell Anderson 13 Sep '13

13 Sep '13

>What I need to do to run old qt3 programs on 3.5.13? >I need to make some kind of aufs chrooted environment. >Please, provide exact recipe of making it. In the Trinity source tree is a directory named experimental. There are some scripts there to convert KDE3 apps to TDE. Tim and Slavek are better qualified to explain how to use the scripts. We should have a wiki article. I don't know that pure Qt3 apps (rather than KDE3 apps) can be converted with those scripts. I presume the best approach is to install the original Qt3 in your chroot and build the app there. I haven't tinkered with that but as TQt3 normally is installed in /opt/trinity, there should be no conflicts installing the original Qt3 in /usr. I have no idea whether the original Qt3 will conflict with Qt4. Darrell

1 0

qt3 API incompatiblity with qt3 programs
by Aleksey Midenkov 13 Sep '13

13 Sep '13

What I need to do to run old qt3 programs on 3.5.13? I need to make some kind of aufs chrooted environment. Please, provide exact recipe of making it.

1 0

KOffice FTBFS on Jessie
by Slávek Banko 13 Sep '13

13 Sep '13

Hello all, Tim, I examined the problem FTBFS KOffice on Jessie. I have found the same problem also with other program from Jessie: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713270 Upon further searching, I found that the problem was caused by patch from reported bug #706181: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706181 When I tried to revert created symlinks, KOffice is built without problems. By the way, on Ubuntu 13.10 (Saucy) is KOffice built without any problems. -- Slavek

1 0

Re: [trinity-devel] (More) Possible bugs introduced from latest k->tde patches
by Darrell Anderson 07 Sep '13

07 Sep '13

>>Those errors aren't supposed to be something new or related with >>renaming... >>Before patch git hash 5354555 all messages passed to >>kd{Error,Warning} have >>gone nowhere but now they go to stderr by default. >>So, these is old errors, but previously masked. > >Okay, thanks, that explains why I now see the messages when >previously I did not. Commit 5354555 was pushed to git >sufficiently >close to the k->tde renaming patches. I would not have noticed >because I was not updating my local source tree during the period >I helped test the renaming patches with Slavek. I opened bug report 1655 to address any of the new, previously unseen error and warning messages. Darrell

1 0

Re: [trinity-devel] (tdesu) Possible bugs introduced from latest k->tde patches
by Darrell Anderson 07 Sep '13

07 Sep '13

>It does not matter if you use su or sudo. In tdelibs >CMakeLists.txt >DEFAULT_SUPER_USER_COMMAND is not set to a short name "su" or >"sudo", but the >name with the full path - ie. "/bin/su". And this is then the >reason for this >warning. I rebuilt tdelibs and tdebase with the proposed patches. I did not modify my configure options. The error message no longer appears. Please push the patches to git. :-) Thank you and good work! Darrell

1 0

Re: [trinity-devel] (More) Possible bugs introduced from latest k->tde patches
by Darrell Anderson 07 Sep '13

07 Sep '13

On Sat, 07 Sep 2013 07:37:23 -0500 "Slávek Banko" <slavek.banko(a)axis.cz> wrote: >On Saturday 07 of September 2013 08:20:12 Darrell Anderson wrote: >> * tdesu: WARNING: unknown super user command > >Test the super user command is a one tdelibs/tdesu/su.cpp a second >time in >tdebase/tdesu/sudlg.spp. Valid is considered "sudo" or "su". > >For tdebase is in tdebase/tdesu/CMakeLists.txt defined: > >if( WITH_SUDO_TDESU_BACKEND ) > set( DEFAULT_SUPER_USER_COMMAND sudo CACHE INTERNAL "" FORCE ) >else() > set( DEFAULT_SUPER_USER_COMMAND su CACHE INTERNAL "" FORCE ) >endif() > >For tdelibs is in tdelibs/CMakeLists.txt defined: > ># FIXME for unknown reason cmake cannot find su >#find_program( __PATH_SU su ) >set( __PATH_SU "/bin/su" ) > >if( __PATH_SU ) > set( DEFAULT_SUPER_USER_COMMAND ${__PATH_SU} ) >else( __PATH_SU ) > message( STATUS "WARNING: su was not found" ) >endif( __PATH_SU ) > ># FIXME for unknown reason cmake cannot find sudo ># find_program( __PATH_SUDO "sudo" ) >set( __PATH_SUDO "/usr/bin/sudo" ) >if( WITH_SUDO_TDESU_BACKEND ) > if( __PATH_SUDO ) > set( DEFAULT_SUPER_USER_COMMAND ${__PATH_SUDO} ) > else( __PATH_SUDO ) > message( FATAL_ERROR "sudo was chosen as tdesu backend, but >was not found >in path." ) > endif( __PATH_SUDO ) >endif( WITH_SUDO_TDESU_BACKEND ) > >In neither case does not test for the presence sudo. And in >tdelibs instead of >setting DEFAULT_SUPER_USER_COMMAND to su or sudo is used full path >to binary, >which is incorrect. > >Proposed patches attached. I build tdelibs and tdebase with WITH_SUDO_TDESU_BACKEND=OFF. The description for that option: "Use sudo as backend for tdesu (default is su)". I always presumed that option was for support for Ubuntu because that distro is hard-wired for sudo. sudo is well supported in Slackware, but the default is for users to use su. Hence my build option decisions. Seems I can trigger the "tdesu: WARNING: unknown super user command" message simply by running tdesu. A snippet from my xsession-error log: [tdeinit] Got EXT_EXEC 'tdesu' from launcher. [tdeinit] tdesu is executable. Launching with exec. [tdeinit] Got EXEC_NEW '/opt/trinity/bin/tdesud' from launcher. [tdeinit] /opt/trinity/bin/tdesud is executable. Launching with exec. tdesu: WARNING: unknown super user command tdesu: WARNING: unknown super user command Will the patches resolve the xsession-error messages with WITH_SUDO_TDESU_BACKEND=OFF? Darrell

2 1

Re: [trinity-devel] (More) Possible bugs introduced from latest k->tde patches
by Darrell Anderson 07 Sep '13

07 Sep '13

On Sat, 07 Sep 2013 02:47:38 -0500 "Fat-Zer" <fatzer2(a)gmail.com> wrote: >2013/9/7 Darrell Anderson <darrella(a)hushmail.com> > >> Additional xsession-error log messages that might be related to >the >> recent renaming (or they might be isolated bugs): >> >> * tdeio (KIOConnection): ERROR: Header read failed, errno=104 >> >> * tdeio (KIOConnection): ERROR: Header has invalid size (-1) >> >> * tdeio (KIOConnection): ERROR: Could not write data >> >> * tdeio (TDELauncher): ERROR: SlavePool: No communication with >> slave. >> >> * tdecore (TDEProcess): WARNING: _attachPty() 17 >> >> * tdecore (TDEProcess): WARNING: _attachPty() 13 >> >> * tdesu: WARNING: unknown super user command >> >> For consistency, should KIOConnection be renamed to >> TDEIOConnection? Looks like tdelibs is the only affected module, >> although there are some remaining remnant "KIO" usages in >tdelibs, >> tdepim, tdenetwork, tdebase, tdevelop, tdesdk, tde-i18n, >kshowmail, >> krusader, kdirstat, tdeio-apt, tork, digikam. >> >> Darrell >> > >Those errors aren't supposed to be something new or related with >renaming... >Before patch git hash 5354555 all messages passed to >kd{Error,Warning} have >gone nowhere but now they go to stderr by default. >So, these is old errors, but previously masked. Okay, thanks, that explains why I now see the messages when previously I did not. Commit 5354555 was pushed to git sufficiently close to the k->tde renaming patches. I would not have noticed because I was not updating my local source tree during the period I helped test the renaming patches with Slavek. That said, for consistency KIOConnection should be renamed to TDEIOConnection. Whether a WARNING or ERROR, the messages are caused by something not functioning correctly, especially the ERROR messages. I understand that commit 5354555 fixed a long standing problem of certain messages not being exposed but now that we have that fixed we must focus on why the messages are generated. As you shared, the messages were always being generated, which means a problem somewhere, despite the messages never being seen by anyone. At this point I now don't know whether the original three messages I posted are a result of the renaming or a result of commit 5354555 now making those messages available and the bugs actually have existed for a long time and nobody had any way to know. Darrell

1 0

opensync FTBFS on debian/testing and patch
by Michele Calgaro 07 Sep '13

07 Sep '13

opensync FTBFS on debian/testing. This is another dh_python -> dh_python2 bug. Proposed patch attached. Cheers Michele

2 1

Re: [trinity-devel] (More) Possible bugs introduced from latest k->tde patches
by Darrell Anderson 07 Sep '13

07 Sep '13

Additional xsession-error log messages that might be related to the recent renaming (or they might be isolated bugs): * tdeio (KIOConnection): ERROR: Header read failed, errno=104 * tdeio (KIOConnection): ERROR: Header has invalid size (-1) * tdeio (KIOConnection): ERROR: Could not write data * tdeio (TDELauncher): ERROR: SlavePool: No communication with slave. * tdecore (TDEProcess): WARNING: _attachPty() 17 * tdecore (TDEProcess): WARNING: _attachPty() 13 * tdesu: WARNING: unknown super user command For consistency, should KIOConnection be renamed to TDEIOConnection? Looks like tdelibs is the only affected module, although there are some remaining remnant "KIO" usages in tdelibs, tdepim, tdenetwork, tdebase, tdevelop, tdesdk, tde-i18n, kshowmail, krusader, kdirstat, tdeio-apt, tork, digikam. Darrell

3 2

Re: [trinity-devel] Possible bugs introduced from latest k->tde patches
by Darrell Anderson 06 Sep '13

06 Sep '13

>All, > >Hopefully these problems are easy to resolve and I don't have to >file formal bug reports. I don't recall seeing these error >messages >until after the recent k->tde renaming patches. There are no >related stability issues or crashes, but the messages indicate >various apps are failing to perform as intended. > >* tdepowersave: WARNING: Unknown error while acquire >org.freedesktop.Policy.Power interface > >* tdepowersave: WARNING: Couldn't request charge_level.unit for >udi: >/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:00/PNP0C09:0 >0 >/PNP0C0A:00/power_supply/BAT0/ > >* tdeio (tdeioslave): WARNING: Can't communicate with >kded_kpasswdserver! > >More than likely the messages are caused by inadvertent renaming >changes, or the renaming changes are correct but associated code >needs respective updating. If the errors can't be easily resolved >here in the list then I'll file official bug reports, all as >Blocker against the R14 release because if I'm seeing these errors > >then I suspect there are additional similar errors that other >users >are seeing. > >If you are using git with the latest patches then please review >your xsession-errors log for possible related error messages. The patch for tdepowersave is quite short but seems the commonality among the three error messages is authentication? Then again, I see the two tdepowersave error messages when logged in as root too. Therefore not an authentication problem per se, but likely a related renaming bug in the authinfo code? Darrell

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels