tde-devels September 2022

devels@trinitydesktop.org

12 participants
9 discussions

[debian] Error - Kicker; Malformed URL system:/

by Felix Miata

4:14.0.13~pre26-0debian12.0.0+3~a Bookworm I have multiple installations doing this when attempting to bring up context menu from desktop RMB click, which fails. I then LMB click on menu starter as alternate method to log out, and this triggers the $SUBJECT window on first click. Subsequent click on menu starter produces no response unless I first dismiss the error window. -- 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

2 years, 1 month

4:14.0.13~pre26-0debian12.0.0+3~a GPU hanging on Bookworm

by Felix Miata

.xsession-errors tail: [FIXME] UNCLASSIFIED DEVICE name: wakeup1 type: (null) subsystem: wakeup driver: (null) [Node Path: (null)] [Syspath: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:0f/wakeup/wakeup1] [(null):(null)] [FIXME] UNCLASSIFIED DEVICE name: wakeup2 type: (null) subsystem: wakeup driver: (null) [Node Path: (null)] [Syspath: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:10/wakeup/wakeup2] [(null):(null)] [FIXME] UNCLASSIFIED DEVICE name: wakeup11 type: (null) subsystem: wakeup driver: (null) [Node Path: (null)] [Syspath: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/wakeup/wakeup11] [(null):(null)] [FIXME] UNCLASSIFIED DEVICE name: wakeup13 type: (null) subsystem: wakeup driver: button [Node Path: (null)] [Syspath: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/wakeup/wakeup13] [(null):(null)] [FIXME] UNCLASSIFIED DEVICE name: wakeup17 type: (null) subsystem: wakeup driver: uhci_hcd [Node Path: (null)] [Syspath: /sys/devices/pci0000:00/0000:00:1a.0/wakeup/wakeup17] [8086:2834] [FIXME] UNCLASSIFIED DEVICE name: wakeup18 type: (null) subsystem: wakeup driver: uhci_hcd [Node Path: (null)] [Syspath: /sys/devices/pci0000:00/0000:00:1a.1/wakeup/wakeup18] [8086:2835] [FIXME] UNCLASSIFIED DEVICE name: wakeup22 type: (null) subsystem: wakeup driver: ehci-pci [Node Path: (null)] [Syspath: /sys/devices/pci0000:00/0000:00:1a.7/wakeup/wakeup22] [8086:283a] [FIXME] UNCLASSIFIED DEVICE name: hdaudioC0D0 type: (null) subsystem: hdaudio driver: snd_hda_codec_analog [Node Path: (null)] [Syspath: /sys/devices/pci0000:00/0000:00:1b.0/hdaudioC0D0] [8086:284b] [FIXME] UNCLASSIFIED DEVICE name: wakeup23 type: (null) subsystem: wakeup driver: tg3 [Node Path: (null)] [Syspath: /sys/devices/pci0000:00/0000:00:1c.4/0000:02:00.0/wakeup/wakeup23] [14e4:167a] [FIXME] UNCLASSIFIED DEVICE name: wakeup19 type: (null) subsystem: wakeup driver: uhci_hcd [Node Path: (null)] [Syspath: /sys/devices/pci0000:00/0000:00:1d.0/wakeup/wakeup19] [8086:2830] [FIXME] UNCLASSIFIED DEVICE name: wakeup20 type: (null) subsystem: wakeup driver: uhci_hcd [Node Path: (null)] [Syspath: /sys/devices/pci0000:00/0000:00:1d.1/wakeup/wakeup20] [8086:2831] [FIXME] UNCLASSIFIED DEVICE name: wakeup21 type: (null) subsystem: wakeup driver: uhci_hcd [Node Path: (null)] [Syspath: /sys/devices/pci0000:00/0000:00:1d.2/wakeup/wakeup21] [8086:2832] [FIXME] UNCLASSIFIED DEVICE name: wakeup24 type: (null) subsystem: wakeup driver: ehci-pci [Node Path: (null)] [Syspath: /sys/devices/pci0000:00/0000:00:1d.7/wakeup/wakeup24] [8086:2836] [FIXME] UNCLASSIFIED DEVICE name: cmos_nvram0 type: (null) subsystem: nvmem driver: (null) [Node Path: (null)] [Syspath: /sys/devices/pnp0/00:01/cmos_nvram0] [(null):(null)] [FIXME] UNCLASSIFIED DEVICE name: wakeup16 type: (null) subsystem: wakeup driver: alarmtimer [Node Path: (null)] [Syspath: /sys/devices/pnp0/00:01/rtc/rtc0/alarmtimer.0.auto/wakeup/wakeup16] [(null):(null)] [FIXME] UNCLASSIFIED DEVICE name: wakeup15 type: (null) subsystem: wakeup driver: rtc_cmos [Node Path: (null)] [Syspath: /sys/devices/pnp0/00:01/wakeup/wakeup15] [(null):(null)] [FIXME] UNCLASSIFIED DEVICE name: wakeup14 type: (null) subsystem: wakeup driver: i8042 kbd [Node Path: (null)] [Syspath: /sys/devices/pnp0/00:02/wakeup/wakeup14] [(null):(null)] [FIXME] UNCLASSIFIED DEVICE name: mc type: (null) subsystem: edac driver: (null) [Node Path: (null)] [Syspath: /sys/devices/system/edac/mc] [(null):(null)] Connection failure: Connection refused pa_context_connect() failed: Connection refused [2022/09/23 20:15:01.728] [konsole] [1006] WARNING: Unable to use /opt/trinity/share/apps/konsole/screen.desktop [2022/09/23 20:15:23.001] klipper: Fatal IO error: client killed [2022/09/23 20:15:23.001] ktip: Fatal IO error: client killed [2022/09/23 20:15:23.004] khelpcenter: Fatal IO error: client killed [2022/09/23 20:15:23.004] kicker: Fatal IO error: client killed [2022/09/23 20:15:23.006] konsole: Fatal IO error: client killed [2022/09/23 20:15:23.007] tderandrtray: Fatal IO error: client killed [2022/09/23 20:15:23.008] kdesktop: Fatal IO error: client killed [2022/09/23 20:15:23.017] twin: Fatal IO error: client killed [2022/09/23 20:15:23.019] [tdeio (TDEIOConnection)] [1051] ERROR: Header read failed, errno=104 (pid 1051 process "it] help /tmp/tdesocket-root/tdelauncherahjy22.sl") [2022/09/23 20:15:23.019] [tdeio (TDEIOConnection)] [1051] ERROR: Header has invalid size (-1) (pid 1051 process "it] help /tmp/tdesocket-root/tdelauncherahjy22.sl") [2022/09/23 20:15:23.019] knotify: Fatal IO error: client killed [2022/09/23 20:15:23.021] kmix: Fatal IO error: client killed [2022/09/23 20:15:23.024] [KSMServer] Fatal IO error: client killed [2022/09/23 20:15:23.025] [tdeinit] Fatal IO error: client killed [2022/09/23 20:15:23.025] [tdeinit] sending SIGHUP to children. [2022/09/23 20:15:23.028] kded: Fatal IO error: client killed [2022/09/23 20:15:23.033] [tdeinit] sending SIGTERM to children. [2022/09/23 20:15:23.033] [tdeinit] Exit. [tdelauncher] Exiting on signal 15 [2022/09/23 20:15:23.035] tdelauncher: Fatal IO error: client killed Session starts, mostly finishes painting desktop, Kicker, Konsole & Release Notes window, then blinks once or thrice, then greeter returns. The following shows up in /var/log/Xorg.0.log.old tail: [ 522.736] (II) modeset(0): Modeline "1680x1050"x0.0 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz e) [ 522.739] (EE) [ 522.739] (EE) Backtrace: [ 522.739] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x555beac49bf9] [ 522.740] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x40) [0x7f45e123daf0] [ 522.741] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (pthread_key_delete+0x15c) [0x7f45e128983c] [ 522.742] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (raise+0x12) [0x7f45e123da52] [ 522.743] (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (abort+0xcf) [0x7f45e1228469] [ 522.744] (EE) unw_get_proc_name failed: no unwind info found [-10] [ 522.744] (EE) 5: /usr/lib/x86_64-linux-gnu/dri/crocus_dri.so (?+0x0) [0x7f45df29e089] [ 522.744] (EE) 6: /usr/lib/x86_64-linux-gnu/dri/crocus_dri.so (nouveau_drm_screen_create+0x6bd469) [0x7f45e01bbd19] [ 522.745] (EE) 7: /usr/lib/x86_64-linux-gnu/dri/crocus_dri.so (__driDriverGetExtensions_d3d12+0xc4f30) [0x7f45df36fd70] [ 522.746] (EE) 8: /usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x14c) [0x7f45e0dddc5c] [ 522.747] (EE) unw_get_proc_name failed: no unwind info found [-10] [ 522.747] (EE) 9: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7f45e0e170b3] [ 522.747] (EE) 10: /usr/lib/xorg/Xorg (BlockHandler+0xad) [0x555beaadb0dd] [ 522.747] (EE) 11: /usr/lib/xorg/Xorg (WaitForSomething+0x153) [0x555beac43573] [ 522.747] (EE) 12: /usr/lib/xorg/Xorg (SendErrorToClient+0x113) [0x555beaad6463] [ 522.747] (EE) 13: /usr/lib/xorg/Xorg (InitFonts+0x3bc) [0x555beaada6bc] [ 522.748] (EE) 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x8a) [0x7f45e122920a] [ 522.749] (EE) 15: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x7c) [0x7f45e12292bc] [ 522.749] (EE) 16: /usr/lib/xorg/Xorg (_start+0x2a) [0x555beaac3b6a] [ 522.749] (EE) [ 522.749] (EE) Fatal server error: [ 522.749] (EE) Caught signal 6 (Aborted). Server aborting Sometimes it takes a very short while before the errant behavior begins. The following I was able to capture in such a session: # xdriinfo Screen 0: crocus # pinxi -C --vs pinxi 3.3.21-17 (2022-09-21) CPU: Info: dual core model: Intel Core2 6700 bits: 64 type: MCP cache: L2: 4 MiB Speed (MHz): avg: 2658 min/max: N/A cores: 1: 2658 2: 2658 # pinxi -GSaz System: Kernel: 5.19.0-1-amd64 arch: x86_64 bits: 64 compiler: gcc v: 11.3.0 parameters: ro root=LABEL=13debian ipv6.disable=1 net.ifnames=0 plymouth.enable=0 noresume mitigations=auto consoleblank=0 vga=791 video=1440x900@60 5 Desktop: Trinity v: R14.0.13 tk: Qt v: 3.5.0 info: kicker wm: Twin v: 3.0 vt: 7 dm: 1: TDM 2: XDM Distro: Debian GNU/Linux bookworm/sid Graphics: Device-1: Intel 82Q963/Q965 Integrated Graphics vendor: Dell driver: i915 v: kernel arch: Gen-4 process: Intel 65n built: 2006-07 ports: active: DVI-D-1,VGA-1 empty: none bus-ID: 00:02.0 chip-ID: 8086:2992 class-ID: 0300 Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: modesetting alternate: fbdev,vesa dri: crocus gpu: i915 display-ID: :0 screens: 1 Screen-1: 0 s-res: 3600x1200 s-dpi: 120 s-size: 762x254mm (30.00x10.00") s-diag: 803mm (31.62") Monitor-1: DVI-D-1 pos: primary,left model: NEC EA243WM serial: <filter> built: 2011 res: 1920x1200 hz: 60 dpi: 94 gamma: 1.2 size: 519x324mm (20.43x12.76") diag: 612mm (24.1") ratio: 16:10 modes: max: 1920x1200 min: 640x480 Monitor-2: VGA-1 pos: right model: Dell P2213 serial: <filter> built: 2012 res: 1680x1050 hz: 60 dpi: 90 gamma: 1.2 size: 473x296mm (18.62x11.65") diag: 558mm (22") ratio: 16:10 modes: max: 1680x1050 min: 720x400 OpenGL: renderer: Mesa Intel 965Q (BW) v: 2.1 Mesa 22.2.0-rc3 direct render: Yes Same thing happens even with only the DVI display connected. It does not happen using an IceWM session. If I force use of the intel DDX display driver instead of the modesetting DIX, then the problem is not exhibited. Same PC runs Plasma on Tumbleweed and KDE3 on Leap 15.4 with no similar issues and modesetting DIX. This behavior was first experienced last June, but it wasn not booted since until upgrading Bookworm today via apt-get full-upgrade. It also doesn't matter whether i965 or crocus is used for dri. Current boot journal: https://paste.debian.net/1254833/ How can we tell whether this drm GPU hang is a TDE issue, or a Bookworm issue, or both? -- 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

2 years, 1 month

[mageia] 0% of 0 completed, ETA = --:--:--, speed = 0

by Felix Miata

0% of 0 completed, ETA = --:--:--, speed = 0 0% of 0 completed, ETA = --:--:--, speed = 0 0% of 0 completed, ETA = --:--:--, speed = 0 0% of 0 completed, ETA = --:--:--, speed = 0 0% of 0 completed, ETA = --:--:--, speed = 0 ... is how most trinity packages are shown being processed for installation, in contrast to packages from mageia's own mirrored repos, which result in numbers in place of the dashes and zeros, and few or no blank lines in between. This is for sure in cauldron (9 to be), and I think also in 8, and it has been this way too long to remember. Indeed I always forget to do this in an X session in order to capture more detail without losing it off top of tty screen, inaccessible since the demise of kernel's scrollback 2 years ago. Is there a repo for Cauldron? There's talk of version freeze for v9 coming up before long. So far I've been using 8's TDE in Cauldron, usually without serious issues. -- 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

2 years, 2 months

[rpm][TW] nothing provides libFLAC8

by Felix Miata

2 years, 2 months

[suse][TW] nothing provides 'libjasper.so.4

by Felix Miata

# zypper install trinity-desktop ... Problem: nothing provides 'libjasper.so.4()(64bit)' needed by the to be installed trinity-tdelibs-14.0.11-1.osstw.x86_64 Solution 1: do not install trinity-desktop-14.0.11-1.osstw.noarch Solution 2: break trinity-tdelibs-14.0.11-1.osstw.x86_64 by ignoring some of its dependencies libjasper4-2.0.33-2.1.x86_64.rpm has been replaced by libjasper6-3.0.0-1.1.x86_64.rpm -- 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

2 years, 2 months

Re mail.com Security Notice: Deactivation of TLS 1.0, TLS 1.1 and unencrypted access

by J Leslie Turriff

I suppose that this is the same thing that happened with gmail.com, yes? Leslie -- Operating System: Linux Distribution: openSUSE Leap 15.4 x86_64 Desktop Environment: Trinity Qt: 3.5.0 TDE: R14.0.12 tde-config: 1.0

2 years, 2 months

Mailman web interface changed?

by Mike Bird

I can no longer see a held message by clicking on the blue link for it on the held messages page. I've tried both Firefox and Chromium. There appear to be other minor cosmetic changes so I'm guessing an upgrade happened? --Mike

2 years, 2 months

Make Kwallet behave ?

by J Leslie Turriff

Hi, I ran across this on the OpenSuSE user list. It's also a problem for me at login time; I've been starting Kmail and Konqueror manually because of it. Will the suggestion using systemd, listed at the end, work in Trinity also? TIA, Leslie ---------- Forwarded Message ---------- > Subject: Re: Make Kwallet behave ? > Date: 2022-08-28, 06:43:19 > From: Adam Mizerski <adam(a)mizerski.pl> > To: users(a)lists.opensuse.org > > W dniu 28.08.2022 o 07:19, Nicolas Kovacs pisze: > > Hi, > > > > I've been a KDE user since version 2.x on Slackware more than 20 years > > ago. I really like it for my daily work, but some details are a bit of a > > PITA. Kwallet is one of them. > > > > Here's a few scenarios that happen erratically on my Tumbleweed > > installations. > > > > 1. KDE starts, Kwallet pops up immediately and leaves me about ten > > seconds to type in my very long GPG password. In the background, > > applications that need a password to connect (like OwnCloud) fail and > > have to be restarted. > > > > 2. KDE starts, Wi-Fi tries to connect but fails, OwnCloud asks me for > > the connection password, and after about a minute or so, Kwallet decides > > to pop up too late to the show. > > > > 3. KDE starts, Kwallet pops up, I type in my password fast enough, Wi-Fi > > connects but OwnCloud asks me for the connection password even though > > Kwallet has been opened successfully. > > > > Any idea how I can make Kwallet behave ? > > > > Cheers from the sunny South of France, > > > > Niki > > > > I have the same problem. > > I just had an idea, but it needs some experimenting to check whether it > would work. Recently KDE introduced managing it's services with systemd > [1]. Systemd allows to extend units using "foo.service.d" directories > [2]. Maybe it would be possible to inject a dependency between kwallet > and nextcloud? > > In my case it looks like this: > - kwallet runs under "dbus-:1.2-org.kde.kwalletd5@0.service" > - nextcloud runs under > "app-com.nextcloud.desktopclient.nextcloud-<random_id>.scope". > - both units are "a transient unit file, created programmatically via > the systemd API. Do not edit." > > You can see all systemd units (they form a tree) using "systemctl --user > status". > > I'll try to do some experiments with it. > > [1] https://blog.davidedmundson.co.uk/blog/plasma-and-the-systemd-startup/ > [2] "man systemd.unit" or > https://www.freedesktop.org/software/systemd/man/systemd.unit.html > > Unfortunately it's not a solution, but for the record: > https://github.com/nextcloud/desktop/issues/1011 ------------------------------------------------------- -- Operating System: Linux Distribution: openSUSE Leap 15.4 x86_64 Desktop Environment: Trinity Qt: 3.5.0 TDE: R14.0.12 tde-config: 1.0

2 years, 2 months

UI design review?

by bobsmith432＠tutanota.com

Hey, just wanna start off by saying I love Trinity Desktop, easy to use and fast on a Pentium 4 with little than a gigabyte of RAM, that's what good coding runs like :D I was reading https://www.trinitydesktop.org/development.php and noticed one of the listed things that Trinity needed assistance in was UI design review. What exactly needs to be reviewed in the terms of UI design? I know people like to say Trinity looks outdated, and although that is kind of true, the Breeze theme from Q4OS modernizes it quite a bit and that could be used as a basis for an optional "modernized" theme. (maybe during setup give the user the choice between the new modern theme and the classic themes) I own a 16:10 ThinkPad, folding tablet laptop, modern curved 1080p monitor and a 5:4 monitor so it's pretty safe to say I could test all sorts of UI designs and layouts functionality-wise, but design wise I'll go ahead and say I'm a bit younger and I still think the KDE 2.x theme looks great, but I'll be open to test and use any sort of theme if it helps. I don't code but I am pretty fluent in just generally knowing what good UI/UX looks and functions like (although I am a bit biased towards the old Windows UI) and can test many different things on new and old hardware, so if help isn't needed there but somewhere else please let me know and I'd be glad to help! - bobsmith

2 years, 2 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels September 2022