| Summary: | R14 Tdm cannot start after a system upgrade from 3.5.13 kdm. | ||
|---|---|---|---|
| Product: | TDE | Reporter: | Martin Hodges <martinhodges479> |
| Component: | tdebase | Assignee: | Timothy Pearson <kb9vqf> |
| Status: | RESOLVED FIXED | ||
| Severity: | blocker | CC: | bugwatch, kb9vqf, martinhodges479, slavek.banko |
| Priority: | P5 | ||
| Version: | R14.0.0 [Trinity] | ||
| Hardware: | Other | ||
| OS: | Debian Wheezy | ||
| Compiler Version: | TDE Version String: | ||
| Application Version: | Application Name: | ||
|
Description
Martin Hodges
2013-05-29 05:46:02 CDT
This is strange. The Debian packaging system itself should be controlling system file installation (such as /etc/init.d/tdm-trinity), not the pre/post installation scripts. I may need to set up a 3.5.13.x VM and try upgrading to R14... Reproduced on another system upgrading from Squeeze. I wonder if this is connected to insserv threaded start up? The problem with replacing the service kdm-trinity to tde-trinity I solved in the commit dc647fd5 (tde-packaging / rename-meta). You can wait to rebuild package rename-meta and test it again? One of the elements that I found later was the presence of xdm, an earlier dependancy of kdm. xdm must be removed for tdm to start. Yes, insserv solves that at one time was active only one service offering the same type of activity => in this case, the X display manager. Therefore, it was necessary to remove former service kdm-trinity during upgrade from 3.5.x to R14. I close this bug report, because the transition from kdm-trinity to tdm-trinity was resolved in the updated packages ubuntu-rename-meta. |