With the nightly packages, systemsettings crashes here. I can't seem to generate a proper stack trace however. Is there a -dbg package I can install to let it create a proper stack trace?
Best regards, Julius
With the nightly packages, systemsettings crashes here. I can't seem to generate a proper stack trace however. Is there a -dbg package I can install to let it create a proper stack trace?
Best regards, Julius
System settings? Do you mean kcontrol, or something else entirely?
Tim
Timothy Pearson wrote:
With the nightly packages, systemsettings crashes here. I can't seem to generate a proper stack trace however. Is there a -dbg package I can install to let it create a proper stack trace?
Best regards, Julius
System settings? Do you mean kcontrol, or something else entirely?
kcontrol works (although it misses a lot of panels), I mean the special Kubuntu version of systemsettings with the overview layout: /opt/trinity/bin/systemsettings This one crashes.
Julius
Timothy Pearson wrote:
With the nightly packages, systemsettings crashes here. I can't seem to generate a proper stack trace however. Is there a -dbg package I can install to let it create a proper stack trace?
Best regards, Julius
System settings? Do you mean kcontrol, or something else entirely?
kcontrol works (although it misses a lot of panels), I mean the special Kubuntu version of systemsettings with the overview layout: /opt/trinity/bin/systemsettings This one crashes.
Julius
There is no debug package for that application; you would need to compile and install it yourself.
Tim
With the nightly packages, systemsettings crashes here. I can't seem to generate a proper stack trace however. Is there a -dbg package I can install to let it create a proper stack trace?
System settings? Do you mean kcontrol, or something else entirely?
kcontrol works (although it misses a lot of panels), I mean the special Kubuntu version of systemsettings with the overview layout: /opt/trinity/bin/systemsettings This one crashes.
Tim, Julius,
I don't have systemsettings installed on my Slackware system. I always assumed that was an Ubuntu-only package. Is that a bad presumption? Will that package install on Slackware? Where can I learn more about this package? What does this package provide that the normal kcontrol does not?
Because of my presumption I never tested that package with the XDG updates. :-(
During my testing I am aware of several dialogs with missing icons in the left-side icon list of modules. You might recall our conversations in this list with me trying to find hidden hard-coded references (bug report 892 has some of those conversations). Konqueror and the panel come to mind, although there were two or three others that displayed this behavior. Julius' description of systemsettings sounds exactly the same.
The key to restoring missing icons is two-fold: 1) updating source code references to a "kde-*.desktop" file and 2) updating profile *desktop references of X-KDE -> X-TDE and KDE; -> TDE;.
The changes in starttde are supposed to remedy the latter problems, but I will not pretend to be all-knowing and presume I know about all glitches caused by the XDG compliance updates. :-) . I suspect those starttde changes are working okay, but perhaps I missed one or two. Likely systemsettings has its own rc file and because I never tested, I would never have added updating snippets in starttde.
Some of the keyboard problems reported could be related. I don't know. Julius:
* Search the $TDEHOME profilerc file for occurrences of "kde-".
* Search the khotkeysrc for occurrences of "kde-".
* If systemsettings has its own rc file, then search that too for "kde-".
Please temporarily rename your $TDEHOME to force creating a new profile and then look for the same anomalies. During my testing I did that many times to test these many XDG updates. None should exist with a new profile, but I suspect anything related to systemsettings will be broken in a new profile.
Some quick good news: A quick grep of the systemsettings sources reveals a slew of kde-*.desktop references:
grep -rn kde-[a-zA-Z0-9]*.desktop applications/systemsettings
Likely I need to update some of those. One of the quirks I discovered when I tested these updates was that not all such references need to be updated to tde-*.desktop. Blindly converting all such references caused its own set of unique breakage.
Therefore I need a help to fix: I need screen grabs of what the systemsettings dialog looks like when functioning correctly and when broken. Would one of you post such screen grabs?
I will try to build and install systemsettings.
I will be able to patch as soon as I can compare a good image to the current building image.
Thank you both for your patience and testing!
Darrell
Darrell Anderson wrote:
I don't have systemsettings installed on my Slackware system. I always assumed that was an Ubuntu-only package. Is that a bad presumption? Will that package install on Slackware? Where can I learn more about this package? What does this package provide that the normal kcontrol does not?
Yes it's Kubuntu's revised configuration panel. It was never upstreamed back into KDE 3 as far as I'm aware. I would expect it to work fine on any none-Ubuntu system however.
Because of my presumption I never tested that package with the XDG updates. :-(
During my testing I am aware of several dialogs with missing icons in the left-side icon list of modules. You might recall our conversations in this list with me trying to find hidden hard-coded references (bug report 892 has some of those conversations). Konqueror and the panel come to mind, although there were two or three others that displayed this behavior. Julius' description of systemsettings sounds exactly the same.
The key to restoring missing icons is two-fold: 1) updating source code references to a "kde-*.desktop" file and 2) updating profile *desktop references of X-KDE -> X-TDE and KDE; -> TDE;.
The changes in starttde are supposed to remedy the latter problems, but I will not pretend to be all-knowing and presume I know about all glitches caused by the XDG compliance updates. :-) . I suspect those starttde changes are working okay, but perhaps I missed one or two. Likely systemsettings has its own rc file and because I never tested, I would never have added updating snippets in starttde.
Some of the keyboard problems reported could be related. I don't know. Julius:
Search the $TDEHOME profilerc file for occurrences of "kde-".
Search the khotkeysrc for occurrences of "kde-".
If systemsettings has its own rc file, then search that too for "kde-".
I'll be sure to keep a back-up of my profile and analyze it for more instances of the KDE string.
Please temporarily rename your $TDEHOME to force creating a new profile and then look for the same anomalies. During my testing I did that many times to test these many XDG updates. None should exist with a new profile, but I suspect anything related to systemsettings will be broken in a new profile.
I'll test it with a new user if I have a moment, but also see my comment in the migration bug. It seems the cause behind my issues was indeed a failed migration. Also see my comment in the migration bug about that.
Some quick good news: A quick grep of the systemsettings sources reveals a slew of kde-*.desktop references:
grep -rn kde-[a-zA-Z0-9]*.desktop applications/systemsettings
Likely I need to update some of those. One of the quirks I discovered when I tested these updates was that not all such references need to be updated to tde-*.desktop. Blindly converting all such references caused its own set of unique breakage.
Therefore I need a help to fix: I need screen grabs of what the systemsettings dialog looks like when functioning correctly and when broken. Would one of you post such screen grabs?
Here is an older screenshot: http://www.dedoimedo.com/images/computers/kubuntu_system_settings.jpg
It shouldn't look much different from that.
Best regards, Julius
Yes it's Kubuntu's revised configuration panel. It was never upstreamed back into KDE 3 as far as I'm aware. I would expect it to work fine on any none-Ubuntu system however.
I successfully built the package on Slackware but the app refuses to run. I submitted a backtrace here on the list. If Tim does not respond today I'll open a bug report.
I'll be sure to keep a back-up of my profile and analyze it for more instances of the KDE string.
I read your comments in bug report 892. I will respond there about your unique situation.
I'll test it with a new user if I have a moment, but also see my comment in the migration bug. It seems the cause behind my issues was indeed a failed migration. Also see my comment in the migration bug about that.
The cause of failure is a sym linked profile directory. With the XDG updates that no longer will succeed and you need two distinct profile directories.
Here is an older screenshot: http://www.dedoimedo.com/images/computers/kubuntu_system_settings.jpg
Thanks. As I can't yet get systemsettings to run, does that app allow changing the view to classic tree view?
Regarding whether tde-systemsettings needs patching, probably not, now that I understand your unique situation. I likely will patch anyway for file name conformance. Additionally, two of the desktop files in tde-systemsettings are the same as those provided in tdebase and they should be like-for-like or renamed to prevent overwriting.
tde-systemsettings does not appear anywhere in the TDE menu. How do Kubuntu users normally access systemsettings?
Darrell
Darrell Anderson wrote:
Here is an older screenshot: http://www.dedoimedo.com/images/computers/kubuntu_system_settings.jpg
Thanks. As I can't yet get systemsettings to run, does that app allow changing the view to classic tree view?
No. kcontrol is also available though (although not through the menu).
Regarding whether tde-systemsettings needs patching, probably not, now that I understand your unique situation. I likely will patch anyway for file name conformance. Additionally, two of the desktop files in tde-systemsettings are the same as those provided in tdebase and they should be like-for-like or renamed to prevent overwriting.
tde-systemsettings does not appear anywhere in the TDE menu. How do Kubuntu users normally access systemsettings?
In Kubuntu (and also now with Trinity) it appears in the menu like you see here: https://help.ubuntu.com/community/SCIM/Kubuntu?action=AttachFile&do=get&...
KDE3 on Ubuntu always had a few specific differences from vanilla KDE3 for Kubuntu. It seems Tim kept this separation for Trinity.
Best regards, Julius
In Kubuntu (and also now with Trinity) it appears in the menu like you see here: https://help.ubuntu.com/community/SCIM/Kubuntu?action=AttachFile&do=get&...
Okay. I see. Yes, the app appears in the top level of my menu --- at the bottom. I simply was not seeing the new entry. :-)
Still crashes. :-)
Darrell
In Kubuntu (and also now with Trinity) it appears in the menu like you see here: https://help.ubuntu.com/community/SCIM/Kubuntu?action=AttachFile&do=get&...
Okay. I see. Yes, the app appears in the top level of my menu --- at the bottom. I simply was not seeing the new entry. :-)
Still crashes. :-)
Darrell
Crash fixed in GIT hash 2348e07.
Tim
Crash fixed in GIT hash 2348e07.
Okay, thanks!
Should this app function on non-Ubuntu systems?
I patched and rebuilt. The app is empty of anything. Just a dialog with a toolbar. No icons.
Darrell
Crash fixed in GIT hash 2348e07.
Okay, thanks!
Should this app function on non-Ubuntu systems?
I patched and rebuilt. The app is empty of anything. Just a dialog with a toolbar. No icons.
Darrell
As of right now I don't think it does anything. It is sitting in the tree for legacy reasons, and will continue to do so in case we decide to have two "views" to access kcontrol modules from.
Tim
On 15 June 2012 16:01, Timothy Pearson kb9vqf@pearsoncomputing.net wrote:
Crash fixed in GIT hash 2348e07.
Okay, thanks!
Should this app function on non-Ubuntu systems?
I patched and rebuilt. The app is empty of anything. Just a dialog with a toolbar. No icons.
Darrell
As of right now I don't think it does anything. It is sitting in the tree for legacy reasons, and will continue to do so in case we decide to have two "views" to access kcontrol modules from.
Tim
What if that display view was added to Kcontol, so it had the capability to display in 2 different styles (much like microsoft XP's two styles for control panel), and remove systemsettings altogether?
Just an idea Calvin
As of right now I don't think it does anything. It is sitting in the tree for legacy reasons, and will continue to do so in case we decide to have two "views" to access kcontrol modules from.
What if that display view was added to Kcontol, so it had the capability to display in 2 different styles (much like microsoft XP's two styles for control panel), and remove systemsettings altogether?
Just an idea
Are you volunteering? :-)
The KDE4 system settings (nee kcontrol) has the option to display both the classic mode and icon view mode.
From what I have seen thus far in tde-systemsettings, everything is duplicated from kcontrol except the view mode. Possibly there is an extra module or two (I have to look again). If we migrated the icon view mode to kcontrol then likely we could remove tde-systemsettings from the source tree.
Another option is grabbing the top-level *.desktop file from tde-systemsettings and use that to launch kcontrol. KDE3 works that way. That is, tde-systemsettings adds a "System Settings" menu option at the top level of the TDE menu. Similar to the "Settings" menu that displays all the kcontrol modules but with no submenu. KDE3 added "Control Center" to the top level menu. Actually, I sort of miss that KDE3 method when using Trinity. Perhaps a long time ago in a galaxy far away I manually added "Control Center" to the top level....
Darrell
Timothy Pearson wrote:
Crash fixed in GIT hash 2348e07.
Okay, thanks!
Should this app function on non-Ubuntu systems?
I patched and rebuilt. The app is empty of anything. Just a dialog with a toolbar. No icons.
Darrell
As of right now I don't think it does anything. It is sitting in the tree for legacy reasons, and will continue to do so in case we decide to have two "views" to access kcontrol modules from.
That would be a regression. In the past Trinity versions it ran fine. Running either systemsettings or kcontrol will bring up a different view (on Ubuntu).
Julius
Timothy Pearson wrote:
Crash fixed in GIT hash 2348e07.
Okay, thanks!
Should this app function on non-Ubuntu systems?
I patched and rebuilt. The app is empty of anything. Just a dialog with a toolbar. No icons.
Darrell
As of right now I don't think it does anything. It is sitting in the tree for legacy reasons, and will continue to do so in case we decide to have two "views" to access kcontrol modules from.
That would be a regression. In the past Trinity versions it ran fine. Running either systemsettings or kcontrol will bring up a different view (on Ubuntu).
Julius
There is a discussion on either this list or the bugtracker on the confusion that two control centers was causing, especially considering that one of them (systemsettings) was more limited than the other, and we eventually decided to remove/deactivate systemsettings until it could be brought up to the same functional level as kcontrol.
Tim
Timothy Pearson wrote:
Crash fixed in GIT hash 2348e07.
Okay, thanks!
Should this app function on non-Ubuntu systems?
I patched and rebuilt. The app is empty of anything. Just a dialog with a toolbar. No icons.
Darrell
As of right now I don't think it does anything. It is sitting in the tree for legacy reasons, and will continue to do so in case we decide to have two "views" to access kcontrol modules from.
That would be a regression. In the past Trinity versions it ran fine. Running either systemsettings or kcontrol will bring up a different view (on Ubuntu).
Julius
There is a discussion on either this list or the bugtracker on the confusion that two control centers was causing, especially considering that one of them (systemsettings) was more limited than the other, and we eventually decided to remove/deactivate systemsettings until it could be brought up to the same functional level as kcontrol.
Tim
Disregard this; the discussion was in reference to kinfocenter and I got the two applications confused somehow.
This IS a regression and should be fixed, probably related to Bug 892.
Tim
As of right now I don't think it does anything. It is sitting in the tree for legacy reasons, and will continue to do so in case we decide to have two "views" to access kcontrol modules from.
That would be a regression. In the past Trinity versions it ran fine. Running either systemsettings or kcontrol will bring up a different view (on Ubuntu).
Yes, at the moment I am presuming the tde-systemsettings failures I see are related to the XDG updates.
I'm working on that, as well as some robustness to starttde to catch update failures. I'll be posting those updates to bug report 892 and asking you to help test. :-)
Darrell
Thanks. As I can't yet get systemsettings to run, does
that app allow changing the view to classic tree view?
No. kcontrol is also available though (although not through the menu).
tde-systemsettings has been patched. Please test!
Darrell
-
Calvin Morrison -
Darrell Anderson -
Julius Schwartzenberg -
Timothy Pearson