Interesting!

How did you install tdm, via tdm-trinity or via some other package?

I have run into the missing theme myself, but usually only when installing tdm-trinity manually.  This should be able to be fixed now that TDM can use a distrc file for overrides; I will see what I can do about it.

The high CPU and inability to type have me more concerned however.  I am currently running another nightly build set to rule out a binary problem, however if these issues persist I will need to investigate further.

I followed the regular Ubuntu installation instructions, just with the nightly repositories instead, so I installed tdm as part of the sudo apt-get install kubuntu-default-settings-trinity kubuntu-desktop-trinity command.

The not being able to type problem also happens when running within KVM/QEMU btw.

The incorrect theme path should be fixed in tde-packaging GIT hash 1935fb8.

I am waiting for the latest nightly build set, and will test the other kdm problems once it has been built.

As of today (2013-04-23), do the latest "nightlies" contain the patch referenced in comment 3?

Julius, as the original reporter, any chance of you testing this soon?

The nightly builds should contain all needed tdm and base library updates at this point.  Please re-test and let me know if the problems reported are still present.

Thanks!

Hi everyone!
I've just installed Ubuntu 13.04 on my Asus EEE 2g surf and just as Julius, I've added the nightlies repos and did the install exactly like it's said in the Ubuntu installation method and me too, when I boot, I get to the ''The default theme path does not exist and TDM gives this error:
Cannot open theme file /opt/trinity/share/apps/kdm/themes/kubuntu-
trinity'' message and if I click on ''OK'', the dialog close and nothing happens after...

If I log in another console, I see the ''tdm_greet'' eating 93% of the CPU...

Can I provide some debug infos for you? If yes, how?

I installed it on May 03, 2013 at +-7:00pm, New York/Montreal time zone

Thanks!
-Alexandre

(In reply to comment #7)
> Hi everyone!
> I've just installed Ubuntu 13.04 on my Asus EEE 2g surf and just as Julius,
> I've added the nightlies repos and did the install exactly like it's said in
> the Ubuntu installation method and me too, when I boot, I get to the ''The
> default theme path does not exist and TDM gives this error:
> Cannot open theme file /opt/trinity/share/apps/kdm/themes/kubuntu-
> trinity'' message and if I click on ''OK'', the dialog close and nothing
> happens after...
> 
> If I log in another console, I see the ''tdm_greet'' eating 93% of the CPU...
> 
> Can I provide some debug infos for you? If yes, how?
> 
> I installed it on May 03, 2013 at +-7:00pm, New York/Montreal time zone
> 
> Thanks!
> -Alexandre

Yes, that would be of help!

First, install the tdebase-trinity-dbg and gdb packages.  Then, while tdm_greet is using high CPU, log in to a terminal and type "gdb --pid `pidof tdm_greet`".  Once gdb has started, type "bt <enter>" and attach the output to this bug report along with your tdmrc and tdmdistrc files (the last one may or may not be present on your system).

Thanks!

Tim

Created attachment 1206 [details]
Debug info

Here is the debug info!
Is there a way to tranfer the debug output to a file, instead of taking a photo of the screen like a fool? That's what I did :)
-Alexandre

When all of the debugging symbol packages are correctly installed, a crash will be intercepted by the Trinity crash handler and a dialog will appear. One of the options in the crash handler dialog is to copy the debugging symbol output.

OK, I see that you are using the themed greeter.  Let me switch my test box to the themed greeter to see if I can reproduce the hang.

Thank you for the additional information!(In reply to comment #9)
> Created attachment 1206 [details]
> Debug info

OK, I see that you are using the themed greeter.  Let me switch my test box to the themed greeter to see if I can reproduce the hang.

Thank you for the additional information!

(In reply to comment #11)
> When all of the debugging symbol packages are correctly installed, a crash will
> be intercepted by the Trinity crash handler and a dialog will appear. One of
> the options in the crash handler dialog is to copy the debugging symbol output.

This only works if tdm_greet actually crashes, unfortunately.  In this case, gdb is being used to break into an already running, although hung, program, in an effort to figure out why the program has hung.  While I know that gdb can be scripted in such a way as to dump a backtrace to a file, I do not know how to do this off the top of my head.

I do see an issue with the themed greeter in that the username/password entry boxes are not able to be changed with mouse or keyboard.  This might be related to the switch to Qt3/TQt3 glib event loop support which occurred in December 2012; the themed greeter may not have received sufficient testing as compared to the normal unthemed greeter.

For the Ubuntu packages, the themed greeter is the default I guess?

Tim,

I haven't changed it to the themed greeter, since this bug happened at the first time I wanted to boot with TDE R14. It is the default setting.

I haven't tested it yet, but would it work if I switch TDM to the unthemed greeter? The only way I had to actually use R14 is by switching back to the default DM of Ubuntu.

I don't know yet if the problem is with Ubuntu, TDE or me, but the performance of R14 on Ubuntu is very poor if I compare it to PCLinuxOS with 3.5.13.1. I guess that the base system of Ubuntu is bigger than the base of PCLOS. Yet I also have to admit that my first-gen Asus EEE is far from being a Ferrari...

(In reply to comment #16)
> I don't know yet if the problem is with Ubuntu, TDE or me, but the performance
> of R14 on Ubuntu is very poor if I compare it to PCLinuxOS with 3.5.13.1. I
> guess that the base system of Ubuntu is bigger than the base of PCLOS. Yet I
> also have to admit that my first-gen Asus EEE is far from being a Ferrari...

Regarding performance, the only real way to narrow this down is to install a version of Ubuntu that can support TDE 3.5.13.1, test it, then reinstall that same Ubuntu version and test with TDE R14.0.0.  I cannot think of any changes in TDE that would cause performance regressions of a large enough magnitude to be noticeable by the end user, so I am inclined to blame Ubuntu itself until shown evidence to the contrary.

(In reply to comment #16)
> Tim,
> 
> I haven't changed it to the themed greeter, since this bug happened at the
> first time I wanted to boot with TDE R14. It is the default setting.
> 
> I haven't tested it yet, but would it work if I switch TDM to the unthemed
> greeter? The only way I had to actually use R14 is by switching back to the
> default DM of Ubuntu.

Forgot to answer this, sorry.  Yes, TDM will work with the unthemed greeter; it receives daily testing and is pretty much guaranteed to keep working at all times as a result.

(In reply to comment #17)
> (In reply to comment #16)
> > I don't know yet if the problem is with Ubuntu, TDE or me, but the performance
> > of R14 on Ubuntu is very poor if I compare it to PCLinuxOS with 3.5.13.1. I
> > guess that the base system of Ubuntu is bigger than the base of PCLOS. Yet I
> > also have to admit that my first-gen Asus EEE is far from being a Ferrari...
> 
> Regarding performance, the only real way to narrow this down is to install a
> version of Ubuntu that can support TDE 3.5.13.1, test it, then reinstall that
> same Ubuntu version and test with TDE R14.0.0.  I cannot think of any changes
> in TDE that would cause performance regressions of a large enough magnitude to
> be noticeable by the end user, so I am inclined to blame Ubuntu itself until
> shown evidence to the contrary.

Yes, that's what I was thinking too... TDE couldn't change enough to make the computer much slower. It's not the first time I've seen both Ubuntu and Debian having poor performance in comparison with PCLinuxOS, but this time, I can even go as far as saying that TDE R14 on Ubuntu 13.04 is not faster than KDE 4.10 on PCLinuxOS 2013 on this little computer. It is for testing purpose only, not really usable. 

If I launch ''top'' on Konsole, just after boot time:
PCLinuxOS 2013 - 3.5.13.1: 421mb ram used - 260mb cached
Ubuntu 13.04 - R14: 487mb ram used - 299mb cached

-Alexandre

The original focus of this bug report (a TDM hang when the themed greeter theme is not available) should be resolved in GIT hash 9aa01ee.

Any performance regressions from 3.5.13.x --> R14.0.0 (when tested on identical hardware with an identical distribution, version, and architecture) should be reported in a new bug report.

I am leaving this report open until I can verify that the Kubuntu-specific TDM theme functions normally.

Created attachment 1263 [details]
Debug info, from R14 on Ubuntu 13.04 on May 11, 2013

Doesn't work for me!

Tagging dependency on Bug 1508 as all current data points to some kind of race condition.

Nice!

I'll need to wipe my Ubuntu with R14 nightlies install in max. 2 weeks to go back to PCLinuxOS TDE. Is there some parts of Trinity that needs specifically more testing?

-Alexandre

(In reply to comment #24)
> Nice!
> 
> I'll need to wipe my Ubuntu with R14 nightlies install in max. 2 weeks to go
> back to PCLinuxOS TDE. Is there some parts of Trinity that needs specifically
> more testing?
> 
> -Alexandre

Any of the crash bug reports. ;-)  Hopefully I'll have this fixed before 2 weeks so that you can confirm a fix...

Hi!
On Ubuntu 13.04 with R14 nightlies of May 15,2013, I still see the ''Cannot open theme file /opt/trinity/share/apps/kdm/themes/kubuntu-
trinity'' dialog, but when I click on ''ok'' to close the window, instead of doing nothing as it did, now it launch the TDE crash handler. In the second tab of the TDE crash handler, it loads debug info, but it never stops, so I can't give the info. If I go in another terminal session, I can see that drkonqui uses 95% of the CPU

-Alexandre

With the nightlies of May 18, 2013 on Ubuntu 13.04, it works partly as it should:
I still get the ''Cannot
open theme file /opt/trinity/share/apps/kdm/themes/kubuntu-
trinity'' dialog, but when I click on ''ok'' to close the window, it launch the classic greeter. Should the theme file, or a ''fallback'' theme be provided by default, to avoid this?

Thanks!
-Alexandre

(In reply to comment #27)
> With the nightlies of May 18, 2013 on Ubuntu 13.04, it works partly as it
> should:
> I still get the ''Cannot
> open theme file /opt/trinity/share/apps/kdm/themes/kubuntu-
> trinity'' dialog, but when I click on ''ok'' to close the window, it launch the
> classic greeter. Should the theme file, or a ''fallback'' theme be provided by
> default, to avoid this?
> 
> Thanks!
> -Alexandre

OK, it looks like the default theme files still contain invalid paths, however the fact that tdm_greet is no longer crashing or hanging is a major step forward.

The fallback to the classic greeter is correct and will likely not be changed.

(In reply to comment #28)
> (In reply to comment #27)
> > With the nightlies of May 18, 2013 on Ubuntu 13.04, it works partly as it
> > should:
> > I still get the ''Cannot
> > open theme file /opt/trinity/share/apps/kdm/themes/kubuntu-
> > trinity'' dialog, but when I click on ''ok'' to close the window, it launch the
> > classic greeter. Should the theme file, or a ''fallback'' theme be provided by
> > default, to avoid this?
> > 
> > Thanks!
> > -Alexandre
> 
> OK, it looks like the default theme files still contain invalid paths, however
> the fact that tdm_greet is no longer crashing or hanging is a major step
> forward.
> 
> The fallback to the classic greeter is correct and will likely not be changed.

I cannot replicate this problem any longer.  Can you confirm that, after installing TDE via "sudo apt-get install kubuntu-default-settings-trinity kubuntu-desktop-trinity", this bug is resolved?

Thanks!

With the R14 nightlies of May 23 on Ubuntu 13.04, it has exactly the same behavior as in my previous message.

I have not used the command you wrote, but I fully updated my system with synaptic. It should do exactly the same thing, except maybe for some config files that are probably kept, instead of being replaced with brand new ones.

At least it is useable like that. Still I think that a KDM theme should be provided by default. Or maybe kdm could switch automatically to the classic greeter without annoying the user with an error dialog in this case?

I will wipe probably tomorrow my Asus EEE to reinstall PCLinuxOS TDE, because R14 on Ubuntu is unbearably slow on this computer. Kded and ksmserver and kicker are still the 3 big CPU eaters!

Thank you for your hard work on TDE!
-Alexandre

If the old tdmrc file was kept, then the original invalid greeter path would be kept along with it.  You would need to use the TDM theme control center module (or edit tdmrc manually) to reset it.  I will look a bit further into the issue just to make sure I have not accidentally overlooked something, however. :-)

Does the /opt/trinity/share/apps/kdm/themes/kubuntu-trinity directory exist on your system?

The only reservation I have in removing the error message is that it could end up confusing the end user in a frustrating manner.  Say the end user installs a theme that cannot be loaded for some reason; on reboot, the user sees the default greeter theme and assumes the settings simply did not take.  In my experience this can be the most frustrating type of problem to track down; when the developers didn't bother to include a simple error message that would highlight the true source of the problem and thereby potentially shave days off of a troubleshooting attempt.

Hi!
No, this folder doesn't exist. I have installed TDE by following the instructions for installing it on Ubuntu Raring, but with the R14 repos found here:
http://www.trinitydesktop.org/wiki/bin/view/Developers/NightlyBuilds

By looking at it, I understood the problem: the package tdmtheme-trinity is not installed by default! It is not installed on my system. This is probably where is the problem. I don't have time right now to install it and to test it, but it should work right away.

I understand your point of view on removing the error message, but in the case that tdmtheme-trinity is not installed, I guess that we could go without this error message? The users who prefers to use the classic greeter shouldn't have to click on this error message everytime they turn on their computer... Or tdmtheme-trinity could be installed by default with TDE.

Thank you!
-Alexandre

I'm going to close this report as the original problem was dealt with some time ago with the introduction of the tdmdistrc file.  In a nutshell, installing only tdm-trinity will install an initial tdmrc file that has theming disabled, thus not displaying the irritating error message described above.  Installing any of the *default-settings-trinity packages will install the associated tdm theme files along with a tdmdistrc file, which will override the tdmrc file and enable the newly-installed default tdm theme.

As stated above, the error message is important for those users who change their tdm themes (if they run into a broken/uninstalled theme), and will not be removed from the tdm source.

Bad news!

I've just reinstalled Ubuntu 13.10 and TDE R14 on my Asus EEE this morning, and TDM doesn't start. I have to use lightdm.

I'll try to give some debug infos in the next few days.
-Alexandre

Created attachment 1748 [details]
TDM debug info, Dec 26, 2013

On a fresh install of TDE on Ubuntu 13.10, on a Asus EEE X101CH, TDM never starts.
By logging in another console, I could get debug info. Here is the picture I got.

Tell me if I can provide more info about it!

Merry Christmas!
-Alexandre

Looks ugly! Unfortunately, I am unable to confirm on two Slackware 14.0 systems. One of which is my HTPC that uses auto-login. My packages are built as of last night from git.

Hi,

This bug is important, and will need attention. With TDE R14 of January 9, 2014 on Ubuntu 13.10, it is still there and I need to switch back to lightdm to be able to login.

-Alexandre

>This bug is important, and will need attention.
This bug is listed in our R14 etherpad check list. :)

(In reply to comment #37)
> Hi,
> 
> This bug is important, and will need attention. With TDE R14 of January 9, 2014
> on Ubuntu 13.10, it is still there and I need to switch back to lightdm to be
> able to login.
> 
> -Alexandre

I still cannot replicate this.  The crash dump indicates that the system call "time(&now)" is failing, which makes no sense!

Can you do the following on the system that is showing the problem:
1.) Make sure that valgrind and tdebase-trinity-dbg are installed
2.) Log in to a VT console as root, and stop TDM.
3.) Remove the TDM log file (/var/log/tdm.log)
4.) Run tdm with the following command: /opt/trinity/bin/tdm -debug 1024
5.) Wait for TDM to crash, then copy the /var/log/tdm.log file to a safe location
6.) Log in and attach the /var/log/tdm.log file to this report

Thanks!

Created attachment 1874 [details]
TDM error log, Jan 19, 2014

Hi!

Still on Ubuntu 13.10 (32 bit) and R14.

I removed the tdm.log file, switched back to tdm and rebooted the computer.
As it did the previous times, it stays at the Ubuntu boot time splash logo

So I hitted Ctrl+Alt+F2, logged myself and after I found the PID of tdm, I killed the process.

Then, I started ''sudo /opt/trinity/bin/tdm -debug 1024''
X started quickly, but after that, it stays at the clock animated cursor for 3-4 minutes. Then, the rest of tdm eventually appeared and I've been able to login normally.

At logout, it took a lot of time too to get to the full tdm.

-Alexandre

(In reply to comment #40)
> Created attachment 1874 [details]
> TDM error log, Jan 19, 2014
> 
> Hi!
> 
> Still on Ubuntu 13.10 (32 bit) and R14.
> 
> I removed the tdm.log file, switched back to tdm and rebooted the computer.
> As it did the previous times, it stays at the Ubuntu boot time splash logo
> 
> So I hitted Ctrl+Alt+F2, logged myself and after I found the PID of tdm, I
> killed the process.
> 
> Then, I started ''sudo /opt/trinity/bin/tdm -debug 1024''
> X started quickly, but after that, it stays at the clock animated cursor for
> 3-4 minutes. Then, the rest of tdm eventually appeared and I've been able to
> login normally.
> 
> At logout, it took a lot of time too to get to the full tdm.
> 
> -Alexandre

Interesting.  The log file doesn't show anything glaringly obvious.  Can you try the same process, but without the -debug 1024 flag to verify that starting tdm manually from the command line still causes tdm to crash?

Thanks!

No, starting tdm manually doesn't cause it to crash.
Without the debug, it is not as slow.

The problem is still why doesn't it work when starting with the system.

Was it on Ubuntu 13.10 32bit that you tested the issue?

-ALexandre

>At logout, it took a lot of time too to get to the full tdm.
I don't want in interrupt this conversation or muddy the waters. The only system here where I use a graphical login and TDM is my HTPC. On that system I notice logout is always several seconds longer than my other run level 3 (command line) login machines. Not minutes, just seconds longer, but noticeable.

(In reply to comment #42)
> No, starting tdm manually doesn't cause it to crash.
> Without the debug, it is not as slow.

OK, great!

> The problem is still why doesn't it work when starting with the system.

If you kill the crashed tdm process, then issue 'stop tdm-trinity' and 'start tdm-trinity' from the terminal, does tdm then start properly?  If it does, then tdm may be starting too early on certain Upstart-based systems.

Do you use Plymouth?  I am pretty sure you do from your mention of the splash screen, but I need to make sure.

> Was it on Ubuntu 13.10 32bit that you tested the issue?

I have tested it on this platform in the past with no crash found.  I can set up another test VM and try again.

Thanks!

Tim

(In reply to comment #44)
> (In reply to comment #42)
> > No, starting tdm manually doesn't cause it to crash.
> > Without the debug, it is not as slow.
> 
> OK, great!
> 
> > The problem is still why doesn't it work when starting with the system.
> 
> If you kill the crashed tdm process, then issue 'stop tdm-trinity' and 'start
> tdm-trinity' from the terminal, does tdm then start properly?  If it does, then
> tdm may be starting too early on certain Upstart-based systems.
> 
If I kill it and do 'sudo stop tdm-trinity', it does nothing since it is already off, but if I reboot, switch to another VT and issue 'stop tdm-trinity' and 'start tdm-trinity', tdm starts as it should.

> Do you use Plymouth?  I am pretty sure you do from your mention of the splash
> screen, but I need to make sure.
> 
Yes, it uses Plymouth (Chrysler, Dodge :) ). My test machine is based on regular Ubuntu (not kubuntu, lubuntu), with R14 installed on top of it, with the system set to use  tdm instead of lightdm.

> > Was it on Ubuntu 13.10 32bit that you tested the issue?
> 
> I have tested it on this platform in the past with no crash found.  I can set
> up another test VM and try again.
> 
It all depends of how far was that past, but I can confirm this bug on 2 different computers.
 
> Thanks!
> 
> Tim

Tell me if I can provide more info!
-Alexandre

I still can't get this to crash in VirtualBox using Ubuntu Saucy i386.

I know one of the machines you are observing the crash on is an EEE, what is the make/model of the other one?

Thanks!

(In reply to comment #46)
> I still can't get this to crash in VirtualBox using Ubuntu Saucy i386.
> 
> I know one of the machines you are observing the crash on is an EEE, what is
> the make/model of the other one?
> 
> Thanks!


The 2 test machines are Asus EEE.
The first one is my old first gen Asus EEE 2G surf, which has perfect support for all of its hardware on Linux since at least the 5 last years.

The second one is my new (probably last gen...) Asus EEE X101CH. Support is good, except for the video card (GMA500 Poulsbo). It can only work in 2D, without graphic acceleration on Linux and the frame rate is really horrible when using Unity or TDE composition manager. On PCLinuxOS, it can only work in VESA...

I know that when I bough the computer, but netbooks aren't sold anymore. These were real computers, but smaller. Industry replaced it with Chromebook crap...

Here is how the support for this video card is described:
http://www.phoronix.com/scan.php?page=news_item&px=MTMyODA

-Alexandre

Created attachment 1877 [details]
Make sure Plymouth is stopped before starting TDM (i.e. the same way KDM for KDE4 starts)

Since this appears to be a bad interaction between Plymouth and TDM (still not able to replicate it here, but I trust you ;-)), I have updated the /etc/init/tdm-trinity.conf with the latest changes from Ubuntu's KDM startup file.  Please apply the attached patch to your /etc/init/tdm-trinity.conf file and see if it stops the crash.

Thanks!

(In reply to comment #48)
> Created attachment 1877 [details]
> Make sure Plymouth is stopped before starting TDM (i.e. the same way KDM for
> KDE4 starts)
> 
> Since this appears to be a bad interaction between Plymouth and TDM (still not
> able to replicate it here, but I trust you ;-)), I have updated the
> /etc/init/tdm-trinity.conf with the latest changes from Ubuntu's KDM startup
> file.  Please apply the attached patch to your /etc/init/tdm-trinity.conf file
> and see if it stops the crash.
> 
> Thanks!


Yes! It works!
I rebooted 3 times to see if it is reliable, and it's good.

Good work!
-Alexandre

(In reply to comment #49)
> (In reply to comment #48)
> > Created attachment 1877 [details] [details]
> > Make sure Plymouth is stopped before starting TDM (i.e. the same way KDM for
> > KDE4 starts)
> > 
> > Since this appears to be a bad interaction between Plymouth and TDM (still not
> > able to replicate it here, but I trust you ;-)), I have updated the
> > /etc/init/tdm-trinity.conf with the latest changes from Ubuntu's KDM startup
> > file.  Please apply the attached patch to your /etc/init/tdm-trinity.conf file
> > and see if it stops the crash.
> > 
> > Thanks!
> 
> 
> Yes! It works!
> I rebooted 3 times to see if it is reliable, and it's good.
> 
> Good work!
> -Alexandre

Pushed to tde-packaging GIT in hash 0d32890.

Thanks for testing!

Tim