tde-devels

devels@trinitydesktop.org

3 participants
3770 discussions

by Darrell Anderson

I built and installed polkit-tqt and polkit-agent-tde. The polkit-agent-tde agent launches fine and can be seen in the process list. Yet I am unable to launch pkexec. Just hangs. No issues with polkit-agent-kde. Where to debug? Thanks.

2 hours, 24 minutes

xdg-desktop-portal-tde

by Darrell Anderson

Are there are any build prerequisites for the xdg-desktop-portal-tde package other than tdelibs|tdebase? Are any run-time environment variables needed? Thanks.

2 hours, 30 minutes

TDE build order and requirements

by Darrell Anderson

I'm trying to create a TDE build environment. I'm using my old notes and the wiki. https://wiki.trinitydesktop.org/How_to_Build_TDE_Core_Modules#Suggested_Bui… I recognize the information because I was (mostly) the original author. :) But I've been out of sync with the process for some years and I am finding some information incorrect or obsolete. For example, python-tqt was renamed to pytqt and python-trinity renamed to pytde. I also am uncertain of the correct build order these days. I know you folks are busy, but would a seasoned developer please review the page and update? Would be a nice help to us folks with lots of brain fog. ) Thanks! :)

2 hours, 54 minutes

TDE and polkit

by Darrell Anderson

I updated my system from 14.1.2 to 14.1.3. I no longer could launch non TDE tools as root using pkexec. Testing in the command line indicates some kind of polkit issue. I tested the same in KDE and had no problems. I noticed in KDE there is a polkit-kde-authentication-agent-1 process running. No such process in TDE, but I don't recall anything like that in previous versions of TDE. Kind of implies something in 14.1.3 changed to expect a polkit agent. On a whim I created a $TDEHOME/Autostart desktop file to launch the KDE polkit agent. I then could again launch non TDE tools as root with pkexec. Did something related change between 14.1.2 and 14.1.3? Digging further into this indicates there has for a while been a polkit-tqt and polkit-agent-tde package. I never had these packages installed and never had an issue until 14.1.3. Are these two packages now required in TDE? A simple executive summary would be a help. Thanks. :)

7 hours, 18 minutes

Update for atavistic beginners link in the KDE3/TDE Tutorials page

by David C Rankin

All, Dead pages come back to life sometimes... The TDE wiki at https://wiki.trinitydesktop.org/KDE3_Tutorials lists the original link as dead for: Development/Tutorials/KDE3/Qt Designer and KDevelop 3.0 for Beginners It has been resurrected under: https://techbase.kde.org/Development/Tutorials/KDE3/Qt_Designer_and_KDevelo… I just happened to run across it and I thought I would pass it along. It appears a bunch of the KDE3 docs are in mediawiki form (not that they were all that complete at the time). Anyway, there may be one or two more that are helpful from those listed at: https://techbase.kde.org/Category:KDE3 Keep up the good work! -- David C. Rankin, J.D.,P.E.

6 days, 17 hours

kicker misplaced after xrandr display position alteration

by Felix Miata

On most boots, I have 2 or 3 displays connected out of 4 normally available. It is unusual when more than one are same resolution as others. The only matched pair are 1680x1050. Most commonly it is 2560x1440 or 1920x1200 as primary, and 1680x1050 as other, or 2560x1440 as primary, and 1920x1200 and 1680x1050 as other. I keep an xrandr miniscript, in e.g. in Debian and *buntu /etc/X11/Xsession.d/, for the purpose of having the positions and primary as I usually want them with the particular PC involved, as among the PCs, available GPU outputs vary in number and type. On any given boot, I may either connect them differently, or want different positions than usual. Bug?: I cannot remember a time when the behavior was any better than now. When I run xrandr to make a change that should result in Kicker moving to a different display, it generally gets the resulting position wrong, sometimes above the (expected) bottom, sometimes misplaced horizontally. The only case I remember that it gets it right is if the change moves primary below another display instead of horizontally. Occurrance just observed resulted from: xrandr --output HDMI-1 --primary --output DVI-I-1 --right-of HDMI-1 This shifted side-by-side's primary as desired from 1680x1050 display to 1920x1200 display. Kicker moved from smaller display to larger, correctly positioned vertically, but off by 1680px horizontally to the right, thus mostly invisible. Only fix to this I've found without opening arandr or KControl (both of which I rarely open for such a purpose) is to alter the script, log out, and log back in. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata

1 week, 3 days

Slackware build environment

by Darrell Anderson

I want to restore my old days of having a full Slackware TDE build environment. To my knowledge there is no full scale build tools for Slackware. I remember when I did this years ago I had some complex build scripts and environment variables to decide whether to build official releases from tarballs or from git. How are you folks supporting both environments? Complex build scripts? Separate but similar build scripts? Anything else to recommend before I venture down this road and likely go nuts? P.S. I have seen the wiki. My eyes still hurt -- been away from this kind of thinking too long. Thanks.

1 week, 4 days

DCOP fails to maximize a Konsole window

by J Leslie Turriff

In a particular script, I'd like to maximize the Konsole window, and DCOP seems like the way to do this, but though the DCOP interface for Konsole provides a maximize() function, it doesn't seem to do anything. Using KDCOP I found in Konsole-16415 => konsole-mainwindow#1, void maximize(), but it doesn't seem to do anything. Entering the equivalent command in Konsole, | @15:30:39 leslie@pinto | wd=~ | $ dcop --user leslie --session .DCOPserver_pinto__0 konsole-16415 konsole-mainwindow#1 maximize | rc=0 completes successfully, but the window does not become maximized. Is this DCOP function's purpose not what it seems, or perhaps I have found a bug? Leslie -- Platform: Linux Distribution: openSUSE Leap 15.6 - x86_64 Desktop Environment: Trinity Qt: 3.5.0 TDE: R14.1.3 tde-config: 1.0

3 weeks, 1 day

tdepowersave dcop interface not working

by deloptes

Hi, does someone know why tdepowersave is not working with dcop or kdcop I am trying to change the scheme via dcop but get false and no change $ dcop tdepowersave tdepowersaveIface currentScheme Powersave $ dcop tdepowersave tdepowersaveIface do_setScheme Presentation false $ dcop tdepowersave tdepowersaveIface currentScheme Powersave but it is possible to change the scheme via the applet in the taskbar thanks -- FCD6 3719 0FFB F1BF 38EA 4727 5348 5F1F DCFE BCB0

3 weeks, 2 days

Cannot talk to TDE Launcher #224 in TDE 14.1.3.

by Alec Destry

About a week ago, I reported this bug in TDE 14.1.3 at https://mirror.git.trinitydesktop.org/gitea/TDE/tde/issues/224 but, so far, nothing has happened. Is that where bugs should be reported?

3 weeks, 4 days

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels