| View previous topic :: View next topic |
| Author |
Message |
paraw
Apprentice
Joined: 07 Jan 2005
Posts: 163
Location: Coventry (UK)
|
 Posted: Wed Jul 17, 2024 8:10 am Post subject: tuxedo-control-center-bin fails to start |
 |
|
Hi all, as per the thread title, the Tuxedo control center fails to start on my laptop. When I try to launch it, all I get is
| Code: | | Trace/breakpoint trap |
Similarly, in dmesg, I get a single line saying
| Code: | | [ 22.942709] traps: tuxedo-control-[3409] trap int3 ip:5615fe7b2abc sp:7ffc77e14a50 error:0 in tuxedo-control-center[5615fb089000+6462000] |
This happens with all three versions available in portage (2.1.8, 2.0.8-r1 and 2.0.2). Also, it happens with both versions of tuxedo-drivers available in portage (4.5.0 and 3.2.14).
I have no idea how to go about debugging this problem, also because I can't really get any info as to what causes it. I think, but I'm not really sure, that it started when I upgraded the kernel to the 6.6 tree. Any help will be greatly appreciated. |
|
| Back to top |
|
 |
paraw
Apprentice
Joined: 07 Jan 2005
Posts: 163
Location: Coventry (UK)
|
| Posted: Wed Jul 17, 2024 2:46 pm Post subject: |
|
|
OK, after testing with many different kernel versions, I can say it is not a kernel problem.
Anyway, can anyone explain me what the error means? I have no idea, and if at least I figured that out, maybe I could try something... |
|
| Back to top |
|
|
Hu
Administrator
Joined: 06 Mar 2007
Posts: 22364
|
| Posted: Wed Jul 17, 2024 3:06 pm Post subject: |
|
|
| It means the program hit a debugger trap. These should never happen. What do you see if you run it under gdb and print a backtrace? Note that as this appears to be a prebuilt package (but still GPL-3? weird), you may not get much, if the original builder did not include debug symbols. |
|
| Back to top |
|
|
paraw
Apprentice
Joined: 07 Jan 2005
Posts: 163
Location: Coventry (UK)
|
| Posted: Wed Jul 17, 2024 3:33 pm Post subject: |
|
|
| Code: | Reading symbols from tuxedo-control-center...
(No debugging symbols found in tuxedo-control-center)
(gdb) run
Starting program: /usr/bin/tuxedo-control-center
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib64/libthread_db.so.1".
[New Thread 0x7ffff43ff6c0 (LWP 17411)]
[Detaching after fork from child process 17412]
[Detaching after fork from child process 17413]
[Detaching after fork from child process 17414]
[New Thread 0x7ffff3bfe6c0 (LWP 17417)]
[New Thread 0x7ffff33fd6c0 (LWP 17418)]
[New Thread 0x7ffff2bfc6c0 (LWP 17419)]
[New Thread 0x7ffff1bfa6c0 (LWP 17420)]
[New Thread 0x7ffff23fb6c0 (LWP 17421)]
[New Thread 0x7ffff0bf86c0 (LWP 17423)]
[New Thread 0x7ffff13f96c0 (LWP 17422)]
[New Thread 0x7ffff03f76c0 (LWP 17424)]
[New Thread 0x7fffefbf66c0 (LWP 17425)]
[New Thread 0x7fffef3f56c0 (LWP 17426)]
[New Thread 0x7fffeebf46c0 (LWP 17427)]
[New Thread 0x7ffff7fb96c0 (LWP 17428)]
[New Thread 0x7fffee3f36c0 (LWP 17429)]
[New Thread 0x7fffedbf26c0 (LWP 17430)]
[New Thread 0x7fffed3f16c0 (LWP 17431)]
[New Thread 0x7fffecbf06c0 (LWP 17432)]
[New Thread 0x7fffec3ef6c0 (LWP 17433)]
[New Thread 0x7fffebbee6c0 (LWP 17434)]
[New Thread 0x7fffeb3ed6c0 (LWP 17435)]
[New Thread 0x7ffff54be6c0 (LWP 17436)]
[New Thread 0x7fffe9dfe6c0 (LWP 17437)]
[New Thread 0x7fffea5ff6c0 (LWP 17438)]
[New Thread 0x7fffe95fd6c0 (LWP 17439)]
[New Thread 0x7fffe8dfc6c0 (LWP 17440)]
[New Thread 0x7fffe7bff6c0 (LWP 17441)]
[New Thread 0x7fffe73fe6c0 (LWP 17442)]
[New Thread 0x7fffe6bfd6c0 (LWP 17443)]
Thread 1 "tuxedo-control-" received signal SIGTRAP, Trace/breakpoint trap.
0x000055555a763abc in ?? ()
(gdb) bt
#0 0x000055555a763abc in ?? ()
#1 0x00007fffffffce50 in ?? ()
#2 0x00003304059ab230 in ?? ()
#3 0x00007fffffffce40 in ?? ()
#4 0x000055555a7506ae in ?? ()
#5 0x00003304059ab230 in ?? ()
#6 0x00007fffffffce50 in ?? ()
#7 0x00007fffffffce70 in ?? ()
#8 0x000055555a7510c7 in ?? ()
#9 0x0000019000000000 in ?? ()
#10 0x00007fffffffcf48 in ?? ()
#11 0x000033040590c3e0 in ?? ()
#12 0x00007fffffffcf90 in ?? ()
#13 0x00007fffffffce90 in ?? ()
#14 0x000055555a750f9e in ?? ()
#15 0x0000019000000000 in ?? ()
#16 0xaaaaaaaaaaaaaaaa in ?? ()
#17 0x00007fffffffcf80 in ?? ()
#18 0x000055555a8efbd4 in ?? ()
#19 0xbd91d6e72fb2dc00 in ?? ()
#20 0x0000000000000000 in ?? () |
which does not look promising. The annoying thing is that it used to work well, and I only realized today it had stopped working. There seems to be no bug open about it in bugzilla. Also, I'm afraid I wouldn't have much information to provide if I were to open one... |
|
| Back to top |
|
|
Hu
Administrator
Joined: 06 Mar 2007
Posts: 22364
|
| Posted: Wed Jul 17, 2024 3:51 pm Post subject: |
|
|
| It looks like the first step will be to get proper debug symbols. As I noted above, this is unfortunately a prebuilt package, so it is not as simple as re-emerging it. However, since the license is stated as GPL-3, source should be available. Perhaps the prebuilt was picked because this package is very difficult to build. |
|
| Back to top |
|
|
paraw
Apprentice
Joined: 07 Jan 2005
Posts: 163
Location: Coventry (UK)
|
| Posted: Wed Jul 17, 2024 3:52 pm Post subject: |
|
|
| It's one of those electron builds... I can try to build it from source locally and see where that leads me. |
|
| Back to top |
|
|
Hu
Administrator
Joined: 06 Mar 2007
Posts: 22364
|
| Posted: Wed Jul 17, 2024 4:13 pm Post subject: |
|
|
| If Electron is involved, then I would pursue other options first. Does it print any messages before crashing? Can you make it more verbose? |
|
| Back to top |
|
|
paraw
Apprentice
Joined: 07 Jan 2005
Posts: 163
Location: Coventry (UK)
|
| Posted: Wed Jul 17, 2024 5:39 pm Post subject: |
|
|
So, I couldn't get any info at all before the crash, so I got the source code and started checking it out. To make a long story short, it first spits out a truckload of complaints about package versions being no longer supported and/or deprecated, with functionality moved elsewhere, and then it refuses to build in node.js, giving a certain error. I traced that error to the fact that it has a hard dependency on legacy openssl libraries. Upon passing the openssl-legacy-provider option to node.js it finished the build, but then it crashes with
| Code: | | /home/paraw/tuxedo-control-center/node_modules/electron/dist/electron exited with signal SIGTRAP |
Note that if I just run electron by itself, with node_modules/electron/dist/electron, after the initial help text I get pretty much the same error:
| Code: | Electron 13.6.9 - Build cross platform desktop apps with JavaScript, HTML, and CSS
Usage: electron [options] [path]
A path to an Electron app may be specified. It must be one of the following:
- index.js file.
- Folder containing a package.json file.
- Folder containing an index.js file.
- .html/.htm file.
- http://, https://, or file:// URL.
Options:
-i, --interactive Open a REPL to the main process.
-r, --require Module to preload (option can be repeated).
-v, --version Print the version.
-a, --abi Print the Node ABI version.
Trace/breakpoint trap |
At this point, this seems to be an electron problem, but I have no idea what is causing it, considering that, up to some time ago, it was working just fine. Amongst the outdated packages the project requests, there is electron version 13.6.9, which may be too old a version and maybe conflict with some updated system component.
I don't know whether I should contact the devs upstream and, in this case, what to tell them, literally... |
|
| Back to top |
|
|
Hu
Administrator
Joined: 06 Mar 2007
Posts: 22364
|
| Posted: Wed Jul 17, 2024 6:08 pm Post subject: |
|
|
| If it crashes just trying to show its own usage message, perhaps it is broken enough that you can reproduce the crash in a "supported" Linux distribution. If so, then you could file a report that "On a cleanly installed Fedora NN, this tool crashes." That is both easier for them to test (they can just grab a Fedora install CD), and harder for them to refute as being that you did something "weird" with the Gentoo environment. In this regard, you are even better off if it crashes on a virtual machine booted from a Fedora LiveCD. |
|
| Back to top |
|
|
NichtDerHans
Apprentice
Joined: 27 Jan 2023
Posts: 173
|
| Posted: Thu Jul 18, 2024 4:35 pm Post subject: |
|
|
It works for me
TUXEDO Book XP14 Gen12 with 11th Gen Intel i7-1165G7
Kernel 6.9.9 / but works with 6.6.32
Wayland
Plasma 6
the new Intel XE Gpu driver / but tcc works also with the i915 driver
app-laptop/tuxedo-drivers
app-laptop/tuxedo-control-center-bin
| Code: |
emerge -1 app-laptop/tuxedo-drivers
emerge -1 app-laptop/tuxedo-control-center-bin
modprobe tuxedo_io
modprobe tuxedo_keyboard
modprobe clevo_acpi
modprobe clevo_wmi
rc-service tccd start
|
The new Intel XE driver prevents the GPU frequency from being displayed in tcc. But with i915 everything works (for me). But the tcc is really badly programmed bloatware. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
