tde-devels

devels@trinitydesktop.org

11 participants
3800 discussions

[trinity-devel] schizoid greeter window on dual display setup
by Felix Miata 16 Jan '19

16 Jan '19

I do a lot of mix and match with displays and PCs. The one I have now booted to Sid has 2560x1440 and 2560x1080 displays on an old ATI dual DisplayPort PCIe card. I have the larger configured as primary and the smaller as upper via an xrandr script in /etc/X11/Xsession.d/. 14.0.6dev's first greeter appearance after booting is on the upper/smaller display, but moves to the lower/larger display on logging out. I'd rather it always be on the larger. Is this something configurable? If so, where & how? Is this something worth or needing a bug report? -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/

1 0

Fwd: [britney]: Do you use --control-files or the "legacy package layout" in your derivative?
by Mike Bird 30 Dec '18

30 Dec '18

FWIW I don't know if this impacts the way that debs are built for TDE. --Mike ---------- Forwarded Message ---------- Subject: [britney]: Do you use --control-files or the "legacy package layout" in your derivative? Date: Sun December 30 2018, 11:13:00 From: Niels Thykier <niels(a)thykier.net> To: Raphaël Hertzog <hertzog(a)debian.org>, Matthias Klumpp <mak(a)debian.org>, Iain Lane <laney(a)debian.org> CC: "debian-release" <debian-release(a)lists.debian.org>, "debian-derivatives" <debian-derivatives(a)lists.debian.org> Hi, I am writing to you, because I know that you are (or have been) involved in setting up or maintaining a britney instance for a Debian derivative. If you are no longer involving please let me know who to contact instead (where applicable). We are considering to deprecate the "legacy package layout" and remove the "--control-files" option. 1) Debian no longer uses these two features in our production runs at all and now instead simply point britney at the metadata of a standard mirror. 2) The "--control-files" option has not being updated and currently generates incomplete Sources files for the target suite. We have no test cases to safe guard against that. As it is not a feature we use, it is unlikely to appear there. 3) The "legacy package layout" is currently used for tests and is unlikely to disappear immediately. However, if a better layout for test cases appear, we may migrate to it and remove the old code. How can I tell if I use these features? ======================================= Check your britney command line. If it includes "--control-files" then you are using both features (as "--control-files" only works with the "legacy package layout". Otherwise, check your britney configuration. If the path set for the "TESTING" configuration points to a standard APT mirror (with a Release file) you are unaffected by this mail. If it instead points to a file directory with some "Packages_X" files and a "Sources" file, you are using what I refer to as the "legacy package layout". You can also check the output with -v for a line like [1]. This determine if britney actually believes it is working with a standard mirror layout. If you use "--control-files": ============================= If you use "--control-files", then you can probably discard it. If you rely on the updated target suite, please consider reusing whatever tooling you use to generate your source suite data to also generate the target suite. This ensures you have a sane full data set for both source suite(s) and target suites. If you use the legacy package layout: ===================================== If feasible, consider migrating to using a standard mirror layout (e.g. if you have a local mirror on the machine running britney). This also enables you to remove the "ARCHITECTURES" and "COMPONENTS" fields from your configuration file as britney simply reads those from the Release file of the target suite. If the mirror format it not an option, please let me know about your use case to see if there is a better alternative. Other bits while we are in contact. :) ====================================== Improving britney: ------------------ We are accepting contributions to britney via salsa.debian.org[2] in form of Merge Requests and bug reports via the BTS as usual (with or without patches). Merge Requests are preferred over patches in the BTS as we have configured salsa to run our test suite for britney along with our code coverage report at [3]. More (technical) details can be found in our docs for contribution[4]. Request for info about your britney sources/configs/setups: ------------------------------------------------- We would very much like an updated list of links to your britney sources (e.g. forks/clones), configurations and setups. Our aim is to get a better understanding of what is out there and how you use britney. If you use britney to process data generated by other tools than the ones in use by Debian (like dak), it might be good to mention that as well. Please send this info to debian-release(a)lists.debian.org. Thanks, ~Niels [1] I: [...] - Found a Release file in testing - using that for defaults (Exact format depends on which version you are using) [2] https://salsa.debian.org/release-team/britney2 [3] https://release-team.pages.debian.net/britney2/coverage/ [4] https://release-team.pages.debian.net/britney2/docs/contributing-to-britney… -------------------------------------------------------

1 0

Does anyone use patchwork?
by Slávek Banko 20 Dec '18

20 Dec '18

Hi all, as part of updates and migrations that Tim made on the primary server, there was a question as to whether someone is using patchwork service https://patchwork.trinitydesktop.org/ ? Or can this service be droped? I remind that TDE Gitea Workspace (TGW) now serves as the best source code collaboration tool for us. See: https://mirror.git.trinitydesktop.org/gitea/ https://wiki.trinitydesktop.org/TDE_Gitea_Workspace Cheers -- Slávek

1 0

FreeBSD 12 :-)
by Dr. Nikolaus Klepp 17 Dec '18

17 Dec '18

Hi all! I just wanted to let you know how TDE works on just-released FreeBSD 12: Basicly everything works as expected, there are just 4 small problems. - For 2 of them I've added bugs + fixes to the bugtracker. - The 3rd is the test "tdeio/kmimetypetest" from "tdelibs", which still fails but mimetipes work after "make install". - the 4rd is again a definition "#define ksize_t socklen_t", but I still have to find where that comes from. So I'm quite pleased :-) Nik -- Please do not email me anything that you are not comfortable also sharing with the NSA, CIA ...

1 0

Problem with starting arduino ide
by MLR 01 Dec '18

01 Dec '18

Hi, I have ubuntu 18.4 with trinity R14.0.5. If I want to start the arduino ide from arduino.cc (download and extract arduino-1.8.7-linux64.tar.xz) there comes the splash-screen for one second and it crashes with this message: ~/arduino-1.8.7$ ./arduino Picked up JAVA_TOOL_OPTIONS: TQSettings::sync: failed to open '/etc/tqt3/tqt_plugins_3.5rc.tmp' for writing What I have to install or change? Thank you very much for the great Desktop.

3 8

TDE Gitea Workspace was updated to Gitea 1.6.x
by Slávek Banko 24 Nov '18

24 Nov '18

The Trinity Desktop Environment (TDE) development team is pleased to announce that the TDE Gitea Workspace (TGW) collaboration tool has been updated to the Gitea 1.6.x series. This new release of Gitea brings some interesting things, such as the Code Review and Approval and Issue Dependencies. For a detailed description, see the Gitea 1.6.0 announcement: https://blog.gitea.io/2018/11/gitea-1.6.0-is-released/ TDE core developers are already using TGW on a daily basis and they hope more and more users and contributors will join them soon. Read more about TGW and how to use it on the wiki https://wiki.trinitydesktop.org/TDE_Gitea_Workspace and access the workspace at https://mirror.git.trinitydesktop.org/gitea .

1 0

Questions regarding build fails on debian
by deloptes 23 Nov '18

23 Nov '18

Hi, I have seen many changes recently in the tools cmake or automake and I tried to rebuild my TDE repository over the weekend. tdelibs-trinity failed because it needs libpkcs11-helper1-dev which depends on libssl1.0-dev other packages however depend on libssl-dev like: kasablanca-trinity tdeaddons-trinity tqca-tls tdebase If I change the control file to libssl-dev | libssl1.0-dev it all works. What can we do about that? Perhaps you have better insight in the difference between two packages. I also can't build couple of packages like kplayer or krecipes for example ./.libs/libkplayernoinst.a(libkplayernoinst_la.all_cpp.o) (.data.rel.ro+0x1048): undefined reference to `static_QUType_ptr' ./.libs/libkplayernoinst.a(libkplayernoinst_la.all_cpp.o) (.data.rel.ro+0x1068): undefined reference to `static_QUType_ptr' What can I do about that? thanks regards

3 9

pixmap memory leak
by Ilya Dogolazky 20 Nov '18

20 Nov '18

Hello ! On my freshly (2 month ago or so) installed trinity desktop (4:14.0.5-0debian9.0.0+0) memory usage of Xorg process grows all the time, it's now 66 of available 170 GB virtual memory after 1 day running and in two or three days the system will kill Xorg because the virtual memory will end. Otherwise it works fine. Here is the output of "xrestop" saying that most of the memory is used by KDE Desktop: res-base Wins GCs Fnts Pxms Misc Pxm mem Other Total PID Identifier 1e00000 42 31 0 1654 1674 92369288K 40K 92369329K 77215 KDE Desktop (and yes, I don't know why it shows 92G which is more than 66G reported by htop for Xorg process) Is there any known workaround for this? Please set Cc: to my address, because otherwise gmail tends to lose some e-mails from TDE lists, thanks!

1 0

Does anyone know how to contact Tim?
by Slávek Banko 10 Nov '18

10 Nov '18

Hi all, we all know that Tim is usually very busy and it's hard to get in touch with him. For everyday work on the project, this is not a major problem. However, there are tasks for which Tim's hands are necessary. For example, uploading ISO images for Ubuntu 18.04 with TDE 14.0.5 into the official mirror system, adding Ubuntu 18.10 (Cosmic) to QuickBuild, creating GIT repositories for next applications, changes to web pages, etc. The problem is, there has been no way to contact Tim for the past 1.5 months. There is no reaction to mails - neither in mailing lists nor in direct contact. At Trinity IRC rooms Tim is not present. Every attempt to contact Tim over the Internet is unsuccessful. Please, is there anyone in the mailing list who can get in touch with Tim? Is there, for example, someone who has personal contact with Tim and can tell him that there are some tasks for which he is needed? Cheers -- Slávek

1 0

very wide konsole ( > 223 columns) + mouse events (machine: debian stable)
by Ilya Dogolazky 18 Oct '18

18 Oct '18

Hello ! I'm forwarding here a message I previously sent to trinity-users list. I think it should be consider as a bug in "konsole", if there is no way to report a column number higher than 223. ---------- Forwarded message --------- On a wide display my konsole window has more than 223 columns. So all the mouse events (clicks and mouse wheel scrolling) with column coordinate bigger than 223 are getting corrupted. As a result VIM receives wrong mouse event coordinates. This is not a VIM specific problem, because VIM works fine in xterm window on the same machine (with the same settings as usual). I compiled a testing ncurses application from here https://stackoverflow.com/questions/47256750 It reports corrupted coordinates if running in xterm with TERM=xterm but it reports right values when running in xterm with TERM=xterm-1006 (exactly as it is intended to work). Alas in konsole this application either reports corrupted coordinates with TERM=xterm or doesn't recognize mouse events at all with TERM=xterm-1006 Maybe someone knows how to get mouse events reported properly ? Cheers, Ilya D.

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels