| Summary: | TDM does not start properly on boot | ||
|---|---|---|---|
| Product: | TDE | Reporter: | ad503trinity |
| Component: | system | Assignee: | Timothy Pearson <kb9vqf> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | CC: | ad503trinity, bugwatch, michele.calgaro |
| Priority: | P5 | ||
| Version: | R14.1.x [Trinity] | ||
| Hardware: | amd64 | ||
| OS: | Linux | ||
| Compiler Version: | TDE Version String: | ||
| Application Version: | Application Name: | ||
If it worked before you updated the kernel and not after doing that, I don't think it is a problem in tdm, otherwise it would have shown up even before that. Also I would expect tdm to fail even after you restart the service manually if the problem was within tdm. IMO the problem is somewhere before tdm is started, although I can't say where. (In reply to Michele Calgaro from comment #1) > If it worked before you updated the kernel and not after doing that, I don't > think it is a problem in tdm, otherwise it would have shown up even before > that. Also I would expect tdm to fail even after you restart the service > manually if the problem was within tdm. > IMO the problem is somewhere before tdm is started, although I can't say > where. Thanks for the update. It did not fully work before upgrading as it did not recognize the non-native resolutions or rotation ability on my monitor. I will check back with the team at Q4OS on this. Thanks. I am updating this to state that I attempted to install and set as default lightdm, and the system booted without issue. So indeed, that would indicate to me that the problem is with the Trinity desktop manager causing it not to behave the same with the automatic (systemd) startup as it does with a manual start. Thanks for the info. Still sounds weird though. Any more info that could help? Someone had just suggested I try changing back from lightdm to tdm. Once I did that, everything started working properly. At this time, I am not having any issues, so it's hard to say where the issue was. Thanks for following up. So what should we do with this bug report? Close it off? It does not seem there is enough info to point to a specific TDE issue... The bug can be closed for now. Thanks! ok, closing for the time being. Reopen if we can find more specific info pointing to a TDE problem |
On the latest Q4OS distribution of Linux, after upgrading the Linux kernel, I was booted into a command line, and prior to the login prompt saw several "Failed to open display ." messages. If I enter the commands to start and stop TDM ("sudo systemctl stop tdm.service" and "sudo systemctl start tdm.service"), the Trinity desktop immediately loads without issue. I have verified the xorg.conf file remains the same before and after. Prior to upgrading the kernel, I did not have this issue on login. However, the system was not able to detect any of the monitor's supported non-native resolutions or rotation. Once I restart TDM from the command line, it does. It seems from this that there may have always been some issue relating to the display. I use integrated graphics from the Intel i5-9600K CPU and do not have a discrete graphics card. In the kernel upgrade, I verified all the firmware was updated and installed. Because it works properly upon stopping and restarting tdm, I was informed this was likely a Trinity issue and not a Q4OS (Debian) issue. I have searched high and low and been unable to encounter any information to shed light on the same problem. Let me know if you need any more information, or if there are any additional steps I need to follow.