By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 1528 - R14 Tdm cannot start after a system upgrade from 3.5.13 kdm.
Summary: R14 Tdm cannot start after a system upgrade from 3.5.13 kdm.
Status: RESOLVED FIXED
Alias: None
Product: TDE
Classification: Unclassified
Component: tdebase (show other bugs)
Version: R14.0.0 [Trinity]
Hardware: Other Debian Wheezy
: P5 blocker
Assignee: Timothy Pearson
URL:
Depends on:
Blocks:
 
Reported: 2013-05-29 05:46 CDT by Martin Hodges
Modified: 2013-11-05 13:36 CST (History)
4 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Hodges 2013-05-29 05:46:02 CDT 
Something is wrong with the package scripts as they do not install the /etc/init.d/tdm-trinity script. The file may be copied directly from the package (I use midnight commander which opens the packages directly).
Comment 1 Timothy Pearson 2013-06-08 02:17:46 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...
Comment 2 Martin Hodges 2013-06-17 02:41:42 CDT 
Reproduced on another system upgrading from Squeeze. I wonder if this is connected to insserv threaded start up?
Comment 3 Slávek Banko 2013-09-24 13:08:05 CDT 
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?
Comment 4 Martin Hodges 2013-09-25 14:55:43 CDT 
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.
Comment 5 Slávek Banko 2013-09-25 15:03:50 CDT 
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.
Comment 6 Slávek Banko 2013-11-05 13:36:05 CST 
I close this bug report, because the transition from kdm-trinity to tdm-trinity was resolved in the updated packages ubuntu-rename-meta.