tde-devels

devels@trinitydesktop.org

3 participants
3808 discussions

dbus-1-tqt ObjectManager
by deloptes 23 Sep '17

23 Sep '17

Hi, I am sorry if ask similar question again. My question is how can I get access to all object paths as shown below, when calling qdbus. How can I get the name of the object path? thanks in advance I have written a test.cpp (attached) file which produces following output TQT_DBusMessage::ReplyMessage Type : 2 TQT_DBusData::Map : 16 Name1 : Map Size1 : 1 Name2 : Map Size2 : 4 Name3 : Map key : org.bluez.Device1 Size3 : 13 Name3 : Map key : org.bluez.MediaControl1 Size3 : 1 Name3 : Map key : org.freedesktop.DBus.Introspectable Size3 : 0 Name3 : Map key : org.freedesktop.DBus.Properties Size3 : 0 Now, when I run qdbus --literal --system org.bluez / org.freedesktop.DBus.ObjectManager.GetManagedObjects [Argument: a{oa{sa{sv}}} { [ObjectPath: /org/bluez] = [ Argument: a{sa{sv}} {"org.freedesktop.DBus.Introspectable" = [Argument: a{sv} {}], "org.bluez.AgentManager1" = [Argument: a{sv} {}], "org.bluez.ProfileManager1" = [Argument: a{sv} {}], "org.bluez.HealthManager1" = [Argument: a{sv} {}]}], [ObjectPath: /org/bluez/hci0] = [Argument: a{sa{sv}} {"org.freedesktop.DBus.Introspectable" = [Argument: a{sv} {}], "org.bluez.Adapter1" = [Argument: a{sv} {"Address" = [Variant(QString): "00:10:60:D1:0F:5C"], "Name" = [Variant(QString): "fujitsu"], "Alias" = [Variant(QString): "fujitsu"], "Class" = [Variant(uint): 0], "Powered" = [Variant(bool): false], "Discoverable" = [Variant(bool): false], "DiscoverableTimeout" = [Variant(uint): 180], "Pairable" = [Variant(bool): true], "PairableTimeout" = [Variant(uint): 0], "Discovering" = [Variant(bool): false], "UUIDs" = [Variant(QStringList): {"00001112-0000-1000-8000-00805f9b34fb", "00001801-0000-1000-8000-00805f9b34fb", "0000110e-0000-1000-8000-00805f9b34fb", "00001106-0000-1000-8000-00805f9b34fb", "00001800-0000-1000-8000-00805f9b34fb", "00001105-0000-1000-8000-00805f9b34fb", "00001200-0000-1000-8000-00805f9b34fb", "0000110c-0000-1000-8000-00805f9b34fb", "00001104-0000-1000-8000-00805f9b34fb", "0000110b-0000-1000-8000-00805f9b34fb", "0000110a-0000-1000-8000-00805f9b34fb", "00005005-0000-1000-8000-0002ee000001", "00001133-0000-1000-8000-00805f9b34fb", "0000112f-0000-1000-8000-00805f9b34fb", "00001132-0000-1000-8000-00805f9b34fb"}], "Modalias" = [Variant(QString): "usb:v1D6Bp0246d052B"]}], "org.freedesktop.DBus.Properties" = [Argument: a{sv} {}], "org.bluez.GattManager1" = [Argument: a{sv} {}], "org.bluez.Media1" = [Argument: a{sv} {}], "org.bluez.NetworkServer1" = [Argument: a{sv} {}] }], [ObjectPath: /org/bluez/hci0/dev_XX_XX_XX_XX_XX_XX] = [Argument: a{sa{sv}} {"org.freedesktop.DBus.Introspectable" = [Argument: a{sv} {}], {"org.bluez.Device1" = [Argument: a{sv} {"Address" = [Variant(QString): "XX:XX:XX:XX:XX:XX"], "Name" = [Variant(QString): "Mobile Phone"], "Alias" = [Variant(QString): "Mobile Phone"], "Class" = [Variant(uint): 5898764], "Icon" = [Variant(QString): "phone"], "Paired" = [Variant(bool): true], "Trusted" = [Variant(bool): true], "Blocked" = [Variant(bool): false], "LegacyPairing" = [Variant(bool): false], "Connected" = [Variant(bool): false], "UUIDs" = [Variant(QStringList): {"00000002-0000-1000-8000-0002ee000002", "00001103-0000-1000-8000-00805f9b34fb", "00001105-0000-1000-8000-00805f9b34fb", "00001106-0000-1000-8000-00805f9b34fb", "0000110a-0000-1000-8000-00805f9b34fb", "0000110c-0000-1000-8000-00805f9b34fb", "0000110e-0000-1000-8000-00805f9b34fb", "00001112-0000-1000-8000-00805f9b34fb", "0000111f-0000-1000-8000-00805f9b34fb", "0000112f-0000-1000-8000-00805f9b34fb", "00001132-0000-1000-8000-00805f9b34fb", "00005005-0000-1000-8000-0002ee000001", "00005601-0000-1000-8000-0002ee000001"}], "Adapter" = [Variant: [ObjectPath: /org/bluez/hci0]], "ServicesResolved" = [Variant(bool): false] } ], "org.freedesktop.DBus.Properties" = [Argument: a{sv} {}], "org.bluez.MediaControl1" = [Argument: a{sv} {"Connected" = [Variant(bool): false]}] } }] }]

1 0

R14.1.x new Kate session panel
by Michele Calgaro 15 Sep '17

15 Sep '17

Dear all, I have finally come around to push the new Kate session panel code to R14.1.x trunk. This adds a session panel to Kate to easy and enhance working with sessions. I have been using it for a couple of years, while slowly developing it. In future I envision more functionality added to it, although finding the time to develop that could be a serious challenge. Just three things to look out for: 1) the format of Kate's session files has changed, the new code will import all your session files and save them with some differences. So if you are just planning to test the new code to see how it works and then revert to an older version, it is recommended that you make a backup of your session files before you start and you restore them at the end of the process 2) with the new code, the "default" session is no longer hardcoded. You can rename it, delete it or do whatever you want. 3) a "read-only session" is a session where you can do whatever editing you want (and all the editing will be saved!). But when you close Kate or switch to another session, the session file will not be modified and the next time the session will open with the same GUI-state (same open files, same panel positions and so on...). If you run into any problem, just report to the ML or preferably open a bug report in bugszilla. Cheers Michele

1 0

where is dbus-1-tqt documented
by deloptes 13 Sep '17

13 Sep '17

Hi, perhaps I overlooked something, but I struggle to find information about dbus-1-tqt All my build produces is libdbus-1-tqt-dbgsym_14.1.0-0debian8.0.5+eko3_amd64.deb libdbus-1-tqt-dev-dbgsym_14.1.0-0debian8.0.5+eko3_amd64.deb libdbus-1-tqt-dev_14.1.0-0debian8.0.5+eko3_amd64.deb libdbus-1-tqt_14.1.0-0debian8.0.5+eko3_amd64.deb Thanks in advance regards

1 1

connectivity issues again
by deloptes 07 Sep '17

07 Sep '17

traceroute trinitydesktop.org traceroute to trinitydesktop.org (192.119.205.246), 30 hops max, 60 byte packets [...] 4 * * * 5 * * * 6 10gigabitethernet1-3.core1.vie1.he.net (193.203.0.185) 22.188 ms 21.474 ms 22.240 ms 7 100ge13-1.core1.par2.he.net (184.105.65.5) 44.981 ms 40.255 ms 41.082 ms 8 100ge14-1.core1.nyc4.he.net (184.105.81.77) 132.060 ms 127.530 ms 125.947 ms 9 100ge9-1.core2.chi1.he.net (184.105.223.161) 121.634 ms 114.500 ms 115.330 ms 10 mediacom-enterprise-business-as30036.100gigabitethernet13-2.core2.chi1.he.n… (184.105.17.74) 119.558 ms 116.528 ms 117.499 ms 11 po10.chgil001cr1.mchsi.com (68.66.73.121) 120.003 ms 119.684 ms 119.604 ms 12 hu5-0-0.fthil001er8.mchsi.com (68.66.73.141) 121.973 ms hu5-1-0.fthil001er8.mchsi.com (68.66.73.119) 121.949 ms 121.421 ms 13 * * * 14 * * * 15 * * *

2 2

Port of Breeze window decoration theme for TDE
by Alexandre Couture 04 Sep '17

04 Sep '17

Hi, I made a port of "Plasma 5 Breeze" window border for TDE. It works with the IceWM window decoration theme engine. To try it, uncompress the attached archive in this folder: /home/(your user name)/.trinity/share/apps/twin/icewm-themes/ Untick the "Use theme title text colors" options, and set your window title font to "Noto Sans 10" Have a great day! -Alexandre

3 2

pinentry-tqt
by deloptes 21 Aug '17

21 Aug '17

Hi I am not sure if someone is interested but I played with pinentry recently and produced a working executable from pinentry-0.8.3 (qt3 code ported to tqt) and a base of pinentry-0.9.7. I just can't do the packaging myself so that I may replace the existing pinentry-* with the one I modified, so that it satisfies all dependencies. I can provide the binary if someone wants to use it for now, but the question here is wouldn't it be better to get the code into the official pinentry project? and why is kleopatra-trinity* kmail-trinity* kmailcvt-trinity* kontact-trinity* tde-trinity* tdepim-trinity* dependant on pinentry-qt/qt4 ? Is it because pinentry-qt was previously qt3, but now qt5? It pulls in qt5 libraries which I want to avoid. regards

2 3

kgpg and key dates
by deloptes 06 Aug '17

06 Aug '17

I upgraded to stretch and testing 14.1 (DEV) Unfortunately when trying to send a gpg signed message today I realized that gpg is not working properly. I started from command line and saw message gpg2 migration successfull. I also see a file .gpg-v21-migrated When I start kgpg from command line it shows many line with invalid date. Gpg however lists all keys with properly displayed date. Kgpg does not display date or name assigned to key. I managed to find out that the date in the key is a unix timestamp, but in kgpg we have TQDate fromString with QT:ISODate, which forces fromString to split the string instead using it as unix time stamp. I did following to fix it if (ret.gpgkeyexpiration.isEmpty()) ret.gpgkeyexpiration=i18n("Unlimited"); else { TQDate date = TQDate::fromString(ret.gpgkeyexpiration, Qt::ISODate); if (!date.isValid()) { TQDateTime timestamp; timestamp.setTime_t(ret.gpgkeycreation.toInt()); date = timestamp.date(); } However I need to look into why the names are not shown properly. Perhaps we'll get a patch Can you confirm this? I created a Bug 2791 regards

1 4

trinitydesktop.org bugs.pearsoncomputing.net
by deloptes 02 Aug '17

02 Aug '17

Hi all, both domains are unreachable at the moment. Is it a local issue here or something gone wrong at the other end? PS: I wanted to upload improved patch to kgpg, but failed to get there. regards

2 3

Re: [trinity-devel] todo Wiki openSUSE installation update
by François Andriot 30 Jul '17

30 Jul '17

Le 30/07/2017 à 20:53, Felix Miata a écrit : > > There is at least one reason for high DPI users not to upgrade Leap past 42.1: > > GTK3 apps not honoring system-wide DPI settings nor KDE mouse cursor > https://bugzilla.opensuse.org/show_bug.cgi?id=1022830 > [GTK+ 3.18] UI text sizes no longer inherited from Linux system > https://bugzilla.mozilla.org/show_bug.cgi?id=1269274 > > The same reason applies to Stretch, all currently supported Fedoras, Ubuntu > 16.04 & up, Mint 18+, anything that includes unpatched gtk >3.16. > > Last night I did a final update on one 42.1 system and had to use the TDE 42.2 > repos to do it. I understand killing 13.1 & 13.2, but not 42.1 or 42.2. Hello, I did not know about this particular DPI problem ... I did not think that anyone using the 42.x serie would keep the 42.1 which is now EOL, that's why I removed the package. I left the 13.1 and 13.2 for users with old computers, and did not upgrade to 42. (also there is no more 32 bits architecture on 42.x) So, I've put back the 42.1 packages on the mirror, they will re-appear soon. François

1 0

[trinity-devel] todo Wiki openSUSE installation update
by Felix Miata 29 Jul '17

29 Jul '17

I can do the Wiki work, but how do I find out the actual current state, which releases actually have existing repos? Has one for 42.3 been built? Is 42.1 already gone? Surely 13.1 and 13.2 are gone, but how can one know for sure? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels