Hi,
I just want to install TDE to my minimal installation of OpenSUSE 12.2. I installed minimal OpenSUSE without X however, I installed minimal X and Trinity but, when I edited the /etc/sysconfig/displaymanager to kdm and windowmanger to startkde it didn't start. Hence, when I looked at /opt/trinity/bin/ inside I saw kdm and startkde.
If someone installed TDE to OpenSUSE 12.2, will tell me to steps after installing and configuring minimal OpenSUSE? Sincerely,
Eren
On Mon, Nov 26, 2012 at 1:59 PM, Eren erenogrul@gmail.com wrote:
Hi,
I just want to install TDE to my minimal installation of OpenSUSE 12.2. I installed minimal OpenSUSE without X however, I installed minimal X and Trinity but, when I edited the /etc/sysconfig/displaymanager to kdm and windowmanger to startkde it didn't start. Hence, when I looked at /opt/trinity/bin/ inside I saw kdm and startkde.
If someone installed TDE to OpenSUSE 12.2, will tell me to steps after installing and configuring minimal OpenSUSE? Sincerely,
Eren
Hi,
I did install TDE on 12.2 - following the instructions found on the trinity site - but not on a minimal install. So I'd guess you are missing something. Maybe you could try to install KDE 3 first, then TDE?
Thierry
On 2012-11-26 14:59 (GMT+0200) Eren composed:
I just want to install TDE to my minimal installation of OpenSUSE 12.2. I installed minimal OpenSUSE without X however, I installed minimal X and Trinity but, when I edited the /etc/sysconfig/displaymanager to kdm and windowmanger to startkde it didn't start.
What exactly did happen when you tried?
Hence, when I looked at /opt/trinity/bin/ inside I saw kdm and startkde.
If someone installed TDE to OpenSUSE 12.2, will tell me to steps after installing and configuring minimal OpenSUSE?
I've not yet tried TDE on OS, but will once I've found instructions to get it using zypper. My usual OS installation method is from minimal X to KDE3 via zypper.
Le 26/11/2012 22:04, Felix Miata a écrit :
On 2012-11-26 14:59 (GMT+0200) Eren composed:
I just want to install TDE to my minimal installation of OpenSUSE 12.2. I installed minimal OpenSUSE without X however, I installed minimal X and Trinity but, when I edited the /etc/sysconfig/displaymanager to kdm and windowmanger to startkde it didn't start.
What exactly did happen when you tried?
Hence, when I looked at /opt/trinity/bin/ inside I saw kdm and startkde.
If someone installed TDE to OpenSUSE 12.2, will tell me to steps after installing and configuring minimal OpenSUSE?
I've not yet tried TDE on OS, but will once I've found instructions to get it using zypper. My usual OS installation method is from minimal X to KDE3 via zypper.
Hello, I've just tried a virtual machine installed with "minimal X"; Then I installed "trinity-tdebase" (to have a minimal TDE environment).
Then configure DISPLAYMANAGER with full path to kdm.
DISPLAYMANAGER="/opt/trinity/bin/kdm"
it works as expected.
Francois
Le lundi 26 novembre 2012, François ANDRIOT a écrit :
Le 26/11/2012 22:04, Felix Miata a écrit :
On 2012-11-26 14:59 (GMT+0200) Eren composed:
I just want to install TDE to my minimal installation of OpenSUSE 12.2. I installed minimal OpenSUSE without X however, I installed minimal X and Trinity but, when I edited the /etc/sysconfig/displaymanager to kdm
and
windowmanger to startkde it didn't start.
What exactly did happen when you tried?
Hence, when I looked at /opt/trinity/bin/ inside I saw kdm and
startkde.
If someone installed TDE to OpenSUSE 12.2, will tell me to steps after installing and configuring minimal OpenSUSE?
I've not yet tried TDE on OS, but will once I've found instructions to get it using zypper. My usual OS installation method is from minimal X to KDE3 via zypper.
Hello, I've just tried a virtual machine installed with "minimal X"; Then I installed "trinity-tdebase" (to have a minimal TDE environment).
Then configure DISPLAYMANAGER with full path to kdm.
DISPLAYMANAGER="/opt/trinity/bin/kdm"
it works as expected.
Francois
--------------------------------------------------------------------- Hi all,
I have not successfully installed neither Suse 12.2, nor Fedora 17 nor Ubuntu with TDE. Everything worked fine at 1024x768 but not 1380x1024. I think that I saw a "TDE live CD" functioning in 1380x1024, but which one (?), I also saw my screen saying that the frequencies were out of range. I unsuccessfully tryed some X related commands found in Ubuntu web site. That is, I still dont have a clean TDE installation. Can you see this type of X problem by testing on a virtual machine?
Thank you for all, Patrick
Le 27/11/2012 00:36, Patrick Serru a écrit :
Le lundi 26 novembre 2012, François ANDRIOT a écrit :
Le 26/11/2012 22:04, Felix Miata a écrit :
On 2012-11-26 14:59 (GMT+0200) Eren composed:
I just want to install TDE to my minimal installation of OpenSUSE 12.2. I installed minimal OpenSUSE without X however, I installed minimal X and Trinity but, when I edited the /etc/sysconfig/displaymanager to kdm
and
windowmanger to startkde it didn't start.
What exactly did happen when you tried?
Hence, when I looked at /opt/trinity/bin/ inside I saw kdm and
startkde.
If someone installed TDE to OpenSUSE 12.2, will tell me to steps after installing and configuring minimal OpenSUSE?
I've not yet tried TDE on OS, but will once I've found instructions to get it using zypper. My usual OS installation method is from minimal X to KDE3 via zypper.
Hello, I've just tried a virtual machine installed with "minimal X"; Then I installed "trinity-tdebase" (to have a minimal TDE environment).
Then configure DISPLAYMANAGER with full path to kdm.
DISPLAYMANAGER="/opt/trinity/bin/kdm"
it works as expected.
Francois
Hi all, I have not successfully installed neither Suse 12.2, nor Fedora 17nor Ubuntu with TDE. Everything worked fine at 1024x768 but not 1380x1024. I think that I saw a "TDE live CD" functioning in 1380x1024, but which one (?), I also saw my screen saying that the frequencies were out of range. I unsuccessfully tryed some X related commands found in Ubuntu web site. That is, I still dont have a clean TDE installation. Can you see this type of X problem by testing on a virtual machine?
Thank you for all,Patrick
Hello, the resolution problem is not related to Trinity (or any other desktop environment). At startup, the Xorg server queries the monitor to get all supported resolutions. Then, it sets the display to the maximum supported resolution. Then, you can only switch between maximum and lower resolution from inside Trinity. (you can never use an higner resolution) If 1280x1024 is not available, it means that, for some reason, the autodetection fails. You should inspect your /var/log/Xorg.0.log file to check where it happens.
I remember I had an old Hyundai Q17 monitor (17" LCD) which had a firmware bug, it reported 1024x768 as maximum supported resolution, whereas it supported 1280x1024. To get 1280x1024, I had to force 1280x1024 resolution in /etc/X11/xorg.conf file.
Check if your distribution has a configuration utility that allows to force the resolution, then use it. E.g, In Mageia control center, I must choose "Generic 1280x1024 Flat panel" (instead of auto-detect), then set resolution to "1280x1024" (instead of auto-detect).
Francois
On 2012-11-26 18:36 (GMT-0500) Patrick Serru composed:
I have not successfully installed neither Suse 12.2, nor Fedora 17nor Ubuntu with TDE. Everything worked fine at 1024x768 but not 1380x1024. I think that I saw a "TDE live CD" functioning in 1380x1024, but which one
1380x1024 is not a standard mode. Probably the video driver is rejecting it as no match to the display's EDID report.
What is your output from 'lspci | grep VGA'?
If you've repeated a typo, and what you're after is actually 1280x1024, and your display actually supports 1280x1024, then there are several things you can try, some of which François ANDRIOT wrote about.
When there is no provided configuration utility to build you an xorg.conf file easily, you nevertheless can build one manually. Try using http://fm.no-ip.com/Share/xorg.conf-minimal-force-DPI as a starter, but with the DisplaySize line commented out if you don't wish to force DPI. If it fails initially, try adding the following to 'Section "Monitor"':
HorizSync 28-91 VertRefresh 55-76
If you have access to the specifications for your display, substitute the values it provides for the above.
In openSUSE (as well as various other distros) instead of putting all configs in xorg.conf, you may find it easier to use the smaller files in /etc/X11/xorg.conf.d/ as alluded to in http://fm.no-ip.com/Share/xorg.conf-minimal-force-DPI.
Something he also did not mention that could possibly help is putting the video mode desired on the kernel cmdline, e.g. video=1280x1024@75 or video=1280x1024@60.
(?), I also saw my screen saying that the frequencies were out of range. I unsuccessfully tryed some X related commands found in Ubuntu web site. That is, I still dont have a clean TDE installation.
As François ANDRIOT wrote, your problem isn't specific to TDE. If you put your Xorg.0.log file where readers can see it without wrapping (e.g. pastebin), then someone may spot your specific problem. Likely you're using the VESA driver and your BIOS fails to include 1280x1024. VESA is a fallback you don't want to be using normally.
Le mardi 27 novembre 2012, Felix Miata a écrit :
On 2012-11-26 18:36 (GMT-0500) Patrick Serru composed:
I have not successfully installed neither Suse 12.2, nor Fedora17 nor Ubuntu with TDE. Everything worked fine at 1024x768 but not 1380x1024. I think that I saw a "TDE live CD" functioning in 1380x1024, but which one
1380x1024 is not a standard mode. Probably the video driver is rejecting it as no match to the display's EDID report.
What is your output from 'lspci | grep VGA'?
If you've repeated a typo, and what you're after is actually 1280x1024, and your display actually supports 1280x1024, then there are several things you can try, some of which François ANDRIOT wrote about.
When there is no provided configuration utility to build you an xorg.conf file easily, you nevertheless can build one manually. Try using http://fm.no-ip.com/Share/xorg.conf-minimal-force-DPI as a starter, but with the DisplaySize line commented out if you don't wish to force DPI. If it fails initially, try adding the following to 'Section "Monitor"':
HorizSync 28-91 VertRefresh 55-76
If you have access to the specifications for your display, substitute the values it provides for the above.
In openSUSE (as well as various other distros) instead of putting all configs in xorg.conf, you may find it easier to use the smaller files in /etc/X11/xorg.conf.d/ as alluded to in http://fm.no-ip.com/Share/xorg.conf-minimal-force-DPI.
Something he also did not mention that could possibly help is putting the video mode desired on the kernel cmdline, e.g. video=1280x1024@75 or video=1280x1024@60.
(?), I also saw my screen saying that the frequencies were out of range. I unsuccessfully tryed some X related commands found in Ubuntu web site. That is, I still dont have a clean TDE installation.
As François ANDRIOT wrote, your problem isn't specific to TDE. If you put your Xorg.0.log file where readers can see it without wrapping (e.g. pastebin), then someone may spot your specific problem. Likely you're using the VESA driver and your BIOS fails to include 1280x1024. VESA is a fallback you don't want to be using normally. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
--------------------------------------------------------------------- Hi all,
Sorry about that: first, I disturbed the thread, and second I wrote 1380 instead of 1280!
I know that my problem is not related to TDE. I just wanted to point out that testing on virtual system is not necesseraly complete testing. Anyway, I stopped trying distributions. Even if I would be able to fix my display problem by my-self, whichever distribution, that was not the case in a relatively short time, I prefer things that install as for a "lambda" user.
Thanks for all, Patrick
On 2012-11-27 13:39 (GMT-0500) Patrick Serru composed:
I prefer things that install as for a "lambda" user.
I think everybody has that preference. It's just that developers don't have *your* particular hardware combination to test on, and when the required hardware data is missing or broken, as apparently must be the case for your display's EDID, there's little that can be done unless you participate in the development process and report the problems you encounter before the product is released.
Hi Felix,
Thank you for your answer.
Le mardi 27 novembre 2012, Felix Miata a écrit :
I think everybody has that preference.
In the "Developer of free things" side of my life, I have always been enthusiastic to user feedback, positive or negative. A feedback was exeptional, before Internet. A guy pointing (politely) a problem is a godsend for the developer.
It's just that developers don't have *your* particular hardware combination to test on…
Is 1280x1024 pixels screen such an exceptionnel format?
…, and when the required hardware data is missing or broken, as apparently must be the case for your display's EDID,…
My display (Fujisu-Siemens FUS T17-2) works well, and its Extended display identification data (EDID) too, but I did not espacialy check that last point. And some recent distributions did configure X correctly for its use.
Anyone who wants to wear the hat of developer should accept comments on the mistakes made by his team or group to which he belongs. Saying "my screens work," or "I do not have this configuration", etc. is not suitable because everyone feels bad: the user feels stupid, and conscientious developer knows he has failed. That said, the group concerned is the XOrg team? I'm not sure.
Faced with the difficulties of installing the most recent distributions, I got to thinking that the tests were done on virtual machines, and thus, the developers were not seeing the problems. The ATI driver? But I am using this machine, this graphic card and this screen with this ancient OSS 11.1!
I'm sorry if I'm uncomfortable.
Cheers, Patrick
On 2012-11-27 20:46 (GMT-0500) Patrick Serru composed:
It's just that developers don't have *your* particular hardware combination to test on…
Is 1280x1024 pixels screen such an exceptionnel format?
It's probably the most common native resolution currently. But, was the Scaleoview T17-2 you're looking at perfect when it left the factory? Is it still perfect?
…, and when the required hardware data is missing or broken, as apparently must be the case for your display's EDID,…
My display (Fujisu-Siemens FUS T17-2) works well, and its Extended display identification data (EDID) too, but I did not espacialy check that last point. And some recent distributions did configure X correctly for its use.
But will they today? That something worked is not proof that it works.
Faced with the difficulties of installing the most recentdistributions, I got to thinking that the tests were done on virtual machines, and thus, the developers were not seeing the problems. The ATI driver? But I am using this machine, this graphic card and this screen with this ancient OSS 11.1!
IIRC, automatic X configuration was rather young at the time of, and likely not implemented in, openSUSE 11.1. The 11.1 I just booted even has a /etc/X11/XF86Config as a soft link from xorg.conf! The in place backup of its original xorg.conf is timestamped April 2007. What happens when you restart X in 11.1 after removing xorg.conf?
When I try X in 11.1 with xorg.conf removed, Xorg.0.log ends with fatal server error \ cannot run in framebuffer mode, even after having correctly identified the gfxchip as Radeon. After restoring xorg.conf, X starts in 1600x1200 according to specification in the xorg.conf file.
Most modern distros have automagic X configuration that works in most cases, but not all. Until one tries manual configuration or other hardware, there's no practical way to be sure a particular failure is not some previously unobserved hardware fault. I have found in *every* case tried personally, absent known driver or X bugs applicable to the hardware used, that basic automagic X configuration failure can be worked around through manual configuration. Trying a less than 1Kbyte http://fm.no-ip.com/Share/xorg.conf-minimal-EDID-workaround as a shortcut to manual configuration from scratch is a pretty simple thing to try. It doesn't take much in most cases to work around apparent EDID-related automagic failure.
Le mardi 27 novembre 2012, Felix Miata a écrit :
On 2012-11-27 20:46 (GMT-0500) Patrick Serru composed:
It's just that developers don't have *your* particular hardware combination to test on…
Is 1280x1024 pixels screen such an exceptionnel format?
It's probably the most common native resolution currently. But, was the Scaleoview T17-2 you're looking at perfect when it left the factory? Is it still perfect?
…, and when the required hardware data is missing or broken, as apparently must be the case for your display's EDID,…
My display (Fujisu-Siemens FUS T17-2) works well, and its Extended display identification data (EDID) too, but I did not espacialy check that last point. And some recent distributions did configure X correctly for its use.
But will they today? That something worked is not proof that it works.
Faced with the difficulties of installing the most recentdistributions, I got to thinking that the tests were done on virtual machines, and thus, the developers were not seeing the problems. The ATI driver? But I am using this machine, this graphic card and this screen with this ancient OSS 11.1!
IIRC, automatic X configuration was rather young at the time of, and likely not implemented in, openSUSE 11.1. The 11.1 I just booted even has a /etc/X11/XF86Config as a soft link from xorg.conf! The in place backup of its original xorg.conf is timestamped April 2007. What happens when you restart X in 11.1 after removing xorg.conf?
When I try X in 11.1 with xorg.conf removed, Xorg.0.log ends with fatal server error \ cannot run in framebuffer mode, even after having correctly identified the gfxchip as Radeon. After restoring xorg.conf, X starts in 1600x1200 according to specification in the xorg.conf file.
Most modern distros have automagic X configuration that works in most cases, but not all. Until one tries manual configuration or other hardware, there's no practical way to be sure a particular failure is not some previously unobserved hardware fault. I have found in *every* case tried personally, absent known driver or X bugs applicable to the hardware used, that basic automagic X configuration failure can be worked around through manual configuration. Trying a less than 1Kbyte http://fm.no-ip.com/Share/xorg.conf-minimal-EDID-workaround as a shortcut to manual configuration from scratch is a pretty simple thing to try. It doesn't take much in most cases to work around apparent EDID-related automagic failure. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
--------------------------------------------------------------------- Hi all, hi Felix,
Thank you for your response.
From inside KDE:
kdesu konqueror /etc/X11/ renaming /etc/X11/XF86Config to /etc/X11/~XF86Config On a root console (F4): /etc/X11 # sax2 SaX: Checking update status for radeon driver SaX: initialization already done SaX: call [ sax2 -r ] if your system has changed !
SaX: startup SaX: X-Server: :0.0 -> grant SaX: importing current configuration...
This worked an a root window showing proposing ATI RV350 AP card, FUS LCD Monitor, at 1280x1024 (SXGA) - 24 bit X Acceleration activated --------------------------------------------
Leaving KDE3, Login as "root" in tty1 and executing sax2 is working well. But with such a reserved of files, this is not surprising: /etc/X11/xorg.conf /etc/X11/xorg.conf.bak /etc/X11/xorg.conf.saxsave and my change /etc/X11/~XF86Config /etc/X11/xorg.conf.md5
-------------------------------------------- So: I did not cut the wings of X. But I understand that if I do, X will no longer work. There is not only X that no longer works when its configuration file is missing!
What can I say? The screen works quite well, for a user like me. As I am not manufacturer, I do not have the means to quickly fully test the screen. I will not study the specifications of the "Extended display identification" and its use on X side, to check my screen. But at a moment of my tests, I typed a command that gave me what should have been included in some equivalent of XOrg.conf. I dont know if the following command to enable this resolution worked because the system (Ubuntu) did not restart ("Ctrl D to continue"). A recent distributions tested these last ~30 days has shown in 1280x1024. I think I saw it from a TDE live CD after "normal user level" adjustment (from desktop contextual menu, I think).
Felix, thank you again, but you can simply forget the component of that thread corresponding to my difficulties. I am no longer interrested by OpenSuse. But I would restart Ubuntu or Fedora tests if there is someone here that could really help me, more than the Ubuntu inline help did it.
Cheers, Patrick
On 2012-11-29 21:54 (GMT-0500) Patrick Serru composed:
Felix, thank you again, but you can simply forget the component ofthat thread corresponding to my difficulties. I am no longer interrested by OpenSuse. But I would restart Ubuntu or Fedora tests if there is someone here that could really help me, more than the Ubuntu inline help did it.
I lost track of what precipitated your inability to run openSUSE on your display's native 1280x1024, but if you're after getting a Fedora or *buntu release from a similar point in time as when the openSUSE release you tried was released, prepare yourself for the likelihood that you'll encounter the same trouble. What openSUSE, Fedora and *buntu are mostly are packagers, not developers. Releases of different distros at similar points in time are unlikely to have very different Xorg versions packaged in them, along with the same bugs. If you get lucky and don't get the same failure, fine for you, but be careful what you expect. You may well wind up needing the exact same workaround in others as I suggested for openSUSE: using config file(s) to override failing automagic.
Your unfortunate experience is not uncommon, regardless of distro. Inexplicable failure is the nature of automagic. Developers are human. Hardware is fallible.
Le jeudi 29 novembre 2012, Felix Miata a écrit :
On 2012-11-29 21:54 (GMT-0500) Patrick Serru composed:
... Your unfortunate experience is not uncommon, regardless of distro. Inexplicable failure is the nature of automagic. Developers are human. Hardware is fallible.
--------------------------------------------------------------------- Great to read that! :-)
I installed and used almost normally kubuntu 10.10-trinity-enterprise (downloaded 26/08/2011). Someone on this list could tell me if after re-installing this kubuntu 10.10, I could upgrade TDE to 3.5.13 and / or even to kubuntu 12.10? This would suit me perfectly, finally!
Otherwise, would you suggest me to subscribe to an XWindow helping list, if any?
Cheers Patrick
On 2012-11-29 23:10 (GMT-0500) Patrick Serru composed:
I installed and used almost normally kubuntu 10.10-trinity-enterprise(downloaded 26/08/2011). Someone on this list could tell me if after re-installing this kubuntu 10.10, I could upgrade TDE to 3.5.13 and / or even to kubuntu 12.10? This would suit me perfectly, finally!
I doubt anyone could predict viability of any particular DE over another. If you can get any DE to work in X, then TDE should be no problem if there is a version published for that release.
If you want to know if you should expect 12.10 to work, boot its live media and see what happens. If it works, then a 12.10 installation should work too.
As for getting from 10.10 to 12.10, be sure to follow the published instructions. Normally an upgrade to each intermediate version is the only way to expect to avoid a mess, and X certainly might break along the way. A clean install might be easier, especially if you already have /home on a separate filesystem.
Otherwise, would you suggest me to subscribe to an XWindow helpinglist, if any?
The Trinity list is short of ideal for discussing generic X trouble like yours. Instead, try either http://lists.x.org/mailman/listinfo/xorg or whatever list may be dedicated to X on your distro of choice.
On 2012-11-26 22:44 (GMT+0100) François ANDRIOT composed:
Le 26/11/2012 22:04, Felix Miata a écrit :
If someone installed TDE to OpenSUSE 12.2, will tell me to steps after installing and configuring minimal OpenSUSE?
I've not yet tried TDE on OS, but will once I've found instructions to get it using zypper. My usual OS installation method is from minimal X to KDE3 via zypper.
I've just tried a virtual machine installed with "minimal X";
I had already minimal installed to Intel/Radeon hardware and added KDE3 on a test machine.
Then I installed "trinity-tdebase" (to have a minimal TDE environment).
Did this.
Then configure DISPLAYMANAGER with full path to kdm.
DISPLAYMANAGER="/opt/trinity/bin/kdm"
Did this.
it works as expected.
Not here, though I don't recall if I ever got KDM login manager to work. No login manager appears on runlevel 5 boot. Startx does work, but NAICT, I'm seeing KDE3, not TDE.
xorg/x11 installed package list: http://fm.no-ip.com/Tmp/SUSE/122/xpkg-big31-os112.txt
kde/trinity installed package list: http://fm.no-ip.com/Tmp/SUSE/122/tdepkg-big31-os122.txt
Xorg.0.log: http://fm.no-ip.com/Tmp/Linux/Xorg/xorg.0.log-big31-os122.txt
.xsession-errors: http://fm.no-ip.com/Tmp/Linux/Xorg/xsession-errors-big31-os122.txt
Le 27/11/2012 02:30, Felix Miata a écrit :
On 2012-11-26 22:44 (GMT+0100) François ANDRIOT composed:
Le 26/11/2012 22:04, Felix Miata a écrit :
If someone installed TDE to OpenSUSE 12.2, will tell me to steps after installing and configuring minimal OpenSUSE?
I've not yet tried TDE on OS, but will once I've found instructions to get it using zypper. My usual OS installation method is from minimal X to KDE3 via zypper.
I've just tried a virtual machine installed with "minimal X";
I had already minimal installed to Intel/Radeon hardware and added KDE3 on a test machine.
Then I installed "trinity-tdebase" (to have a minimal TDE environment).
Did this.
Then configure DISPLAYMANAGER with full path to kdm.
DISPLAYMANAGER="/opt/trinity/bin/kdm"
Did this.
it works as expected.
Not here, though I don't recall if I ever got KDM login manager to work. No login manager appears on runlevel 5 boot. Startx does work, but NAICT, I'm seeing KDE3, not TDE.
xorg/x11 installed package list: http://fm.no-ip.com/Tmp/SUSE/122/xpkg-big31-os112.txt
kde/trinity installed package list: http://fm.no-ip.com/Tmp/SUSE/122/tdepkg-big31-os122.txt
Xorg.0.log: http://fm.no-ip.com/Tmp/Linux/Xorg/xorg.0.log-big31-os122.txt
.xsession-errors: http://fm.no-ip.com/Tmp/Linux/Xorg/xsession-errors-big31-os122.txt
Sorry I read the thread too fast, in fact I was answering to "Eren". My instructions are still valid if you don't install KDE3. I will look why it fails when KDE3 is installed, but I'm pretty sure I will find a shitty kde3-related script (in /etc/profile.d/ I guess), which hardcodes environment variables to force the use of KDE3, and prevent Trinity to start.
Francois
On Mon, Nov 26, 2012 at 10:04 PM, Felix Miata mrmazda@earthlink.net wrote:
I've not yet tried TDE on OS, but will once I've found instructions to get it using zypper. My usual OS installation method is from minimal X to KDE3 via zypper.
Here are the instructions I found (and used) to install via zypper (although I did a standard install with KDE 4 as I may wish to run some KDE apps, even if I don't like the desktop):
1. Configure the supplementary PACKMAN repository Instructions: http://packman.links2linux.org/
2. Configure the ZYPPER repository (as root user) For OpenSUSE? 12.2 (v3.5.13.1) zypper ar -t YUM -G http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity/rpm/opensuse12.2/... -i) trinity zypper ar -t YUM -G http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity/rpm/opensuse12.2/... trinity-noarch zypper refresh
3. Install the Trinity desktop environment
zypper install trinity-desktop
After that I logged out, then in changing the session to TDE, that's all
Thierry
Greetings,
On Mon, Nov 26, 2012 at 10:04 PM, Felix Miata mrmazda@earthlink.net wrote:
I've not yet tried TDE on OS, but will once I've found instructions to get it using zypper. My usual OS installation method is from minimal X to KDE3 via zypper.
Here are the instructions I found (and used) to install via zypper (although I did a standard install with KDE 4 as I may wish to run some KDE apps, even if I don't like the desktop):
First of all, thanks for your answers. However, I saw mostly installation of yours were Minimal X + Trinity or you installed OpenSUSE with default desktop (KDE 4) then installed Trinity. Also, I think minimal installation without X causes some permission problems or something else to prevent opening kdm. Hence, when you did a minimal X installation, your system has tones of unnecessary packages like some ncurses applications of yast and with dependencies, bootsplash etc etc (for me of course).
- Configure the supplementary PACKMAN repository
Instructions: http://packman.links2linux.org/
- Configure the ZYPPER repository (as root user)
For OpenSUSE? 12.2 (v3.5.13.1) zypper ar -t YUM -G http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity/rpm/opensuse12.2/... -i) trinity zypper ar -t YUM -G http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity/rpm/opensuse12.2/... trinity-noarch zypper refresh
- Install the Trinity desktop environment
zypper install trinity-desktop
After that I logged out, then in changing the session to TDE, that's all
Thierry
Besides, I tried minimal OpenSUSE install + simple Xorg server + Trinity, still Trinity and kdm not starting. Hence, I looked at logs and there's no error about kdm or anything related with Trinity. After all, I think I'm going to choose Minimal X + Trinity installation and I'll inform you what I achieved..
Thanks for your answers. If someone will try minimal without X then install Xorg and try to install and run Trinity and in the end success to run, let me know. Sincerely,
Eren
Le 27/11/2012 17:09, Eren a écrit :
Greetings,
On Mon, Nov 26, 2012 at 10:04 PM, Felix Miata mrmazda@earthlink.net wrote:
I've not yet tried TDE on OS, but will once I've found instructions to get it using zypper. My usual OS installation method is from minimal X to KDE3 via zypper.
Here are the instructions I found (and used) to install via zypper (although I did a standard install with KDE 4 as I may wish to run some KDE apps, even if I don't like the desktop):
First of all, thanks for your answers. However, I saw mostly installation of yours were Minimal X + Trinity or you installed OpenSUSE with default desktop (KDE 4) then installed Trinity. Also, I think minimal installation without X causes some permission problems or something else to prevent opening kdm. Hence, when you did a minimal X installation, your system has tones of unnecessary packages like some ncurses applications of yast and with dependencies, bootsplash etc etc (for me of course).
- Configure the supplementary PACKMAN repository
Instructions: http://packman.links2linux.org/
- Configure the ZYPPER repository (as root user)
For OpenSUSE? 12.2 (v3.5.13.1) zypper ar -t YUM -G http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity/rpm/opensuse12.2/...
-i) trinity zypper ar -t YUM -G http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity/rpm/opensuse12.2/...
trinity-noarch zypper refresh
- Install the Trinity desktop environment
zypper install trinity-desktop
After that I logged out, then in changing the session to TDE, that's all
Thierry
Besides, I tried minimal OpenSUSE install + simple Xorg server + Trinity, still Trinity and kdm not starting. Hence, I looked at logs and there's no error about kdm or anything related with Trinity. After all, I think I'm going to choose Minimal X + Trinity installation and I'll inform you what I achieved..
Thanks for your answers. If someone will try minimal without X then install Xorg and try to install and run Trinity and in the end success to run, let me know. Sincerely,
Eren
OK I've done the following steps and I confirm it works:
Install opensuse (i586 in my case) with very minimal installation.
Configure networking, configure repositories.
Install minimal xorg with: zypper install xorg-x11-server
Install minimal TDE with: zypper install trinity-tdebase
Install iceauth (required for dcopserver): zypper install iceauth (dependency will be added in next TDE build for opensuse)
Configure DISPLAYMANAGER=/opt/trinity/bin/kdm in /etc/sysconfig/displaymanager
Fix missing 'Xsession' file (file exists but not in expected folder): ln -s /etc/X11/xdm/Xsession /etc/X11/Xsession (will be fixed in next TDE build for opensuse)
Set default runlevel to 5 in systemd. rm -f /etc/systemd/system/default.target ln -s /lib/systemd/system/runlevel5.target /etc/systemd/system/default.target
And reboot. It works, tested in virtual machine again.
Francois
On 2012-11-27 21:42 (GMT+0100) François ANDRIOT composed:
OK I've done the following steps and I confirm it works:
Install opensuse (i586 in my case) with very minimal installation.
Configure networking, configure repositories.
Install minimal xorg with: zypper install xorg-x11-server
done
Install minimal TDE with: zypper install trinity-tdebase
done
Install iceauth (required for dcopserver): zypper install iceauth (dependency will be added in next TDE build for opensuse)
done
Configure DISPLAYMANAGER=/opt/trinity/bin/kdm in /etc/sysconfig/displaymanager
done
Fix missing 'Xsession' file (file exists but not in expected folder): ln -s /etc/X11/xdm/Xsession /etc/X11/Xsession (will be fixed in next TDE build for opensuse)
done
Set default runlevel to 5 in systemd. rm -f /etc/systemd/system/default.target ln -s /lib/systemd/system/runlevel5.target /etc/systemd/system/default.target
systemd in 12.2 is an non-mandatory/broken/incomplete openSUSE misfeature. I have sysvinit-init installed instead, with id:5:initdefault: in /etc/inittab.
And reboot. It works, tested in virtual machine again.
Here on real hardware X starts to start (busy cursor and non-black background appear briefly), then exits to tty login prompt. Does trinity-tdm create a log file anywhere? I wonder if https://bugzilla.novell.com/show_bug.cgi?id=783862 is related?
Le 27/11/2012 23:16, Felix Miata a écrit :
It works, tested in virtual machine again.
Here on real hardware X starts to start (busy cursor and non-black background appear briefly), then exits to tty login prompt. Does trinity-tdm create a log file anywhere? I wonder if https://bugzilla.novell.com/show_bug.cgi?id=783862 is related?
Look at /var/log/kdm.log if it exists. Alas it does not contain many information on my test virtual machine ...
You can try /opt/trinity/bin/kdm --help to see options. There is a --nodaemon and a --debug which could help you find out what is happening.
Francois
On 2012-11-27 17:32 (GMT-0500) Francois Andriot composed:
Felix Miata composed:
Here on real hardware X starts to start (busy cursor and non-black Does trinity-tdm create a log file anywhere? I wonder if https://bugzilla.novell.com/show_bug.cgi?id=783862 is related?
Look at /var/log/kdm.log if it exists.
Problem seems apparent, but not why present: http://fm.no-ip.com/Tmp/SUSE/122/kdm-log-big31-122-tde.txt
You can try /opt/trinity/bin/kdm --help to see options. There is a --nodaemon and a --debug which could help you find out what is happening.
On 2012-11-27 18:08 (GMT-0500) Felix Miata composed:
Problem seems apparent, but not why present: http://fm.no-ip.com/Tmp/SUSE/122/kdm-log-big31-122-tde.txt
I did some fiddling that produced various other error messages. All today's logs are at: http://fm.no-ip.com/Tmp/SUSE/122/
Le 28/11/2012 00:41, Felix Miata a écrit :
On 2012-11-27 18:08 (GMT-0500) Felix Miata composed:
Problem seems apparent, but not why present: http://fm.no-ip.com/Tmp/SUSE/122/kdm-log-big31-122-tde.txt
I did some fiddling that produced various other error messages. All today's logs are at: http://fm.no-ip.com/Tmp/SUSE/122/
Hello, what is the result of the command: ldd /opt/trinity/bin/kdm
(you may need to install this command if not present)
Francois
On 2012-11-28 07:05 (GMT+0100) Francois Andriot composed:
Felix Miata composed:
Problem seems apparent, but not why present: http://fm.no-ip.com/Tmp/SUSE/122/kdm-log-big31-122-tde.txt
I did some fiddling that produced various other error messages. All today's logs are at: http://fm.no-ip.com/Tmp/SUSE/122/
Hello, what is the result of the command: ldd /opt/trinity/bin/kdm
linux-vdso.so.1 (0x00007fff9077c000) libX11.so.6 => /usr/lib64/libX11.so.6 (0x00007f29cd2e0000) libXau.so.6 => /usr/lib64/libXau.so.6 (0x00007f29cd0dc000) libdbus-tqt-1.so.0 => /opt/trinity/lib64/libdbus-tqt-1.so.0 (0x00007f29cceca000) libdbus-1.so.3 => /lib64/libdbus-1.so.3 (0x00007f29ccc84000) libcrypt.so.1 => /lib64/libcrypt.so.1 (0x00007f29cca49000) libpam.so.0 => /lib64/libpam.so.0 (0x00007f29cc83b000) libdl.so.2 => /lib64/libdl.so.2 (0x00007f29cc637000) libXdmcp.so.6 => /usr/lib64/libXdmcp.so.6 (0x00007f29cc431000) libc.so.6 => /lib64/libc.so.6 (0x00007f29cc08c000) libxcb.so.1 => /usr/lib64/libxcb.so.1 (0x00007f29cbe6c000) libtqt.so.4 => /opt/trinity/lib64/libtqt.so.4 (0x00007f29cbc69000) libqt-mt.so.3 => /usr/lib64/libqt-mt.so.3 (0x00007f29cb261000) libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007f29caf5a000) libm.so.6 => /lib64/libm.so.6 (0x00007f29cac63000) libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f29caa4c000) libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f29ca830000) librt.so.1 => /lib64/librt.so.1 (0x00007f29ca628000) libaudit.so.1 => /lib64/libaudit.so.1 (0x00007f29ca410000) /lib64/ld-linux-x86-64.so.2 (0x00007f29cd61c000) libpng14.so.14 => /usr/lib64/libpng14.so.14 (0x00007f29ca1e7000) libz.so.1 => /lib64/libz.so.1 (0x00007f29c9fd1000) libXi.so.6 => /usr/lib64/libXi.so.6 (0x00007f29c9dc1000) libXrender.so.1 => /usr/lib64/libXrender.so.1 (0x00007f29c9bb7000) libXrandr.so.2 => /usr/lib64/libXrandr.so.2 (0x00007f29c99ae000) libXcursor.so.1 => /usr/lib64/libXcursor.so.1 (0x00007f29c97a2000) libXinerama.so.1 => /usr/lib64/libXinerama.so.1 (0x00007f29c959f000) libXft.so.2 => /usr/lib64/libXft.so.2 (0x00007f29c9389000) libfreetype.so.6 => /usr/lib64/libfreetype.so.6 (0x00007f29c90fc000) libfontconfig.so.1 => /usr/lib64/libfontconfig.so.1 (0x00007f29c8ec5000) libXext.so.6 => /usr/lib64/libXext.so.6 (0x00007f29c8cb3000) libSM.so.6 => /usr/lib64/libSM.so.6 (0x00007f29c8aab000) libICE.so.6 => /usr/lib64/libICE.so.6 (0x00007f29c888f000) libXfixes.so.3 => /usr/lib64/libXfixes.so.3 (0x00007f29c8689000) libexpat.so.1 => /usr/lib64/libexpat.so.1 (0x00007f29c845f000) libuuid.so.1 => /usr/lib64/libuuid.so.1 (0x00007f29c825a000)
Le 28/11/2012 07:29, Felix Miata a écrit :
On 2012-11-28 07:05 (GMT+0100) Francois Andriot composed:
Felix Miata composed:
Problem seems apparent, but not why present: http://fm.no-ip.com/Tmp/SUSE/122/kdm-log-big31-122-tde.txt
I did some fiddling that produced various other error messages. All today's logs are at: http://fm.no-ip.com/Tmp/SUSE/122/
Hello, what is the result of the command: ldd /opt/trinity/bin/kdm
[snip]
Hello, I've just retried my own procedure on an x86_64 opensuse virtual machine, and I confirm it works (at first I was using i586) ... KDM starts, I have no missing symbol.
Symbol ZN20KSMModalDialogHeaderC1EP7QWidget is defined in /opt/trinity/lib64/libkdeui.so.4.2.0 , which is part of "tdelibs" package.
What did you do differently from the procedure ? You said you use sysvinit instead of systemd, have you installed other software at the same time ? I suspect (never really tried) that TDE 3.5.13 cannot co-exist with KDE3, have you installed KDE3 ? Maybe TDE's kdm is trying to use KDE3's libraries, and that cannot work at all...
Some hints: - run "/sbin/ldconfig" then try again . - check that you have no LD_LIBRARY_PATH defined in your environment variables - check that there is no KDE3 related stuff in /etc/ld.so.conf, /etc/ld.so.conf.d/*.conf, and /etc/profile.d/*.sh
Please give me your "rpm -qa" output ...
Francois
On 2012-11-28 19:43 (GMT+0100) Francois Andriot composed:
Felix Miata composed:
On 2012-11-28 07:05 (GMT+0100) Francois Andriot composed:
Felix Miata composed:
Problem seems apparent, but not why present: http://fm.no-ip.com/Tmp/SUSE/122/kdm-log-big31-122-tde.txt
I did some fiddling that produced various other error messages. All today's logs are at: http://fm.no-ip.com/Tmp/SUSE/122/
Hello, what is the result of the command: ldd /opt/trinity/bin/kdm
Symbol ZN20KSMModalDialogHeaderC1EP7QWidget is defined in /opt/trinity/lib64/libkdeui.so.4.2.0 , which is part of "tdelibs" package.
What did you do differently from the procedure?
from upthread: http://trinity-users.pearsoncomputing.net/?0::4066
"> I've just tried a virtual machine installed with "minimal X";
I had already minimal installed to Intel/Radeon hardware and added KDE3"
I guess what we're really working on here is how to replace KDE3 with TDE.
You said you use sysvinit instead of systemd, have you installed other software at the same time ?
Other than Firefox & SeaMonkey, nothing I recall. I have more than 30 multiboot systems, and this has been my first openSUSE TDE try. Before I've only used TED on *buntu, and very little of that because of my distaste for *buntu's Debian foundation and *buntu tweaking.
I suspect (never really tried) that TDE 3.5.13 cannot co-exist with KDE3, have you installed KDE3 ? Maybe TDE's kdm is trying to use KDE3's libraries, and that cannot work at all...
also from: http://trinity-users.pearsoncomputing.net/?0::4066 http://fm.no-ip.com/Tmp/SUSE/122/tdepkg-big31-os122.txt http://fm.no-ip.com/Tmp/SUSE/122/xpkg-big31-os112.txt
Some hints:
- run "/sbin/ldconfig" then try again .
Didn't help.
- check that you have no LD_LIBRARY_PATH defined in your environment
variables
# set | grep LIBR #
- check that there is no KDE3 related stuff in /etc/ld.so.conf,
It contains only: /usr/local/lib64 /usr/local/lib include /etc/ld.so.conf.d/*.conf
/etc/ld.so.conf.d/*.conf, and /etc/profile.d/*.sh
In /etc/profile.d/, 'll | grep kd' produces null.
/etc/ld.so.conf.d/ # ll -rw-r--r-- 1 root root 30 Jul 23 17:31 arts.conf -rw-r--r-- 1 root root 24 Jul 16 12:47 glamor.conf -rw-r--r-- 1 root root 272 Jul 16 10:51 graphviz.conf -rw-r--r-- 1 root root 30 Sep 27 06:11 kdelibs3.conf -rw-r--r-- 1 root root 19 Sep 29 08:54 trinity.conf
'mv kdelibs3.conf kdelibs3-conf' or kdelibs3-cfg and reboot didn't help, nor did rerunning ldconfig after the rename and another reboot.
Please give me your "rpm -qa" output ...
http://fm.no-ip.com/Tmp/SUSE/122/allpkg-big31-os122.txt 44k
Does every KDE3 package in the openSUSE catalog have a TDE replacement? If so, then all of kde*3* probably needs to be zypper rm'd, and the KDE:KDE3 repo rr'd. As of now there remain 21 such packages:
http://fm.no-ip.com/Tmp/SUSE/122/kde3remain-big21-os122.txt
Le 28/11/2012 20:58, Felix Miata a écrit :
from upthread: http://trinity-users.pearsoncomputing.net/?0::4066
"> I've just tried a virtual machine installed with "minimal X";
I had already minimal installed to Intel/Radeon hardware and added KDE3"
I guess what we're really working on here is how to replace KDE3 with TDE.
You said you use sysvinit instead of systemd, have you installed other software at the same time ?
Other than Firefox & SeaMonkey, nothing I recall. I have more than 30 multiboot systems, and this has been my first openSUSE TDE try. Before I've only used TED on *buntu, and very little of that because of my distaste for *buntu's Debian foundation and *buntu tweaking.
I suspect (never really tried) that TDE 3.5.13 cannot co-exist with KDE3, have you installed KDE3 ? Maybe TDE's kdm is trying to use KDE3's libraries, and that cannot work at all...
also from: http://trinity-users.pearsoncomputing.net/?0::4066 http://fm.no-ip.com/Tmp/SUSE/122/tdepkg-big31-os122.txt http://fm.no-ip.com/Tmp/SUSE/122/xpkg-big31-os112.txt
Some hints:
- run "/sbin/ldconfig" then try again .
Didn't help.
- check that you have no LD_LIBRARY_PATH defined in your environment
variables
# set | grep LIBR #
- check that there is no KDE3 related stuff in /etc/ld.so.conf,
It contains only: /usr/local/lib64 /usr/local/lib include /etc/ld.so.conf.d/*.conf
/etc/ld.so.conf.d/*.conf, and /etc/profile.d/*.sh
In /etc/profile.d/, 'll | grep kd' produces null.
/etc/ld.so.conf.d/ # ll -rw-r--r-- 1 root root 30 Jul 23 17:31 arts.conf -rw-r--r-- 1 root root 24 Jul 16 12:47 glamor.conf -rw-r--r-- 1 root root 272 Jul 16 10:51 graphviz.conf -rw-r--r-- 1 root root 30 Sep 27 06:11 kdelibs3.conf -rw-r--r-- 1 root root 19 Sep 29 08:54 trinity.conf
'mv kdelibs3.conf kdelibs3-conf' or kdelibs3-cfg and reboot didn't help, nor did rerunning ldconfig after the rename and another reboot.
Please give me your "rpm -qa" output ...
http://fm.no-ip.com/Tmp/SUSE/122/allpkg-big31-os122.txt 44k
Does every KDE3 package in the openSUSE catalog have a TDE replacement? If so, then all of kde*3* probably needs to be zypper rm'd, and the KDE:KDE3 repo rr'd. As of now there remain 21 such packages:
http://fm.no-ip.com/Tmp/SUSE/122/kde3remain-big21-os122.txt
What does the 'kdelibs3.conf' file contain ? I bet it contains "/opt/kde3/lib64" ...
From what I see in your packages, everything you installed from KDE3 exist in TDE (except some Suse-specific artwork packages).
Before uninstalling KDE3, you can try a last (dirty) trick: mv /opt/kde3 /opt/kde3.old ldconfig
then restart kdm again (or reboot).
Francois
On 2012-11-28 14:58 (GMT-0500) Felix Miata composed:
On 2012-11-28 19:43 (GMT+0100) Francois Andriot composed:
- check that there is no KDE3 related stuff in /etc/ld.so.conf,
It contains only: /usr/local/lib64 /usr/local/lib include /etc/ld.so.conf.d/*.conf
/etc/ld.so.conf.d/*.conf, and /etc/profile.d/*.sh
In /etc/profile.d/, 'll | grep kd' produces null.
/etc/ld.so.conf.d/ # ll -rw-r--r-- 1 root root 30 Jul 23 17:31 arts.conf -rw-r--r-- 1 root root 24 Jul 16 12:47 glamor.conf -rw-r--r-- 1 root root 272 Jul 16 10:51 graphviz.conf -rw-r--r-- 1 root root 30 Sep 27 06:11 kdelibs3.conf -rw-r--r-- 1 root root 19 Sep 29 08:54 trinity.conf
'mv kdelibs3.conf kdelibs3-conf' or kdelibs3-cfg and reboot didn't help, nor did rerunning ldconfig after the rename and another reboot.
This time I just deleted it.
Please give me your "rpm -qa" output ...
Does every KDE3 package in the openSUSE catalog have a TDE replacement? If so, then all of kde*3* probably needs to be zypper rm'd, and the KDE:KDE3 repo rr'd. As of now there remain 21 such packages:
I removed all remaining *kde*3* except the following:
kde-susetranslations-12.1-14.1.1.noarch kde3-gtk-qt-engine-0.8svn20071009-58.2.x86_64 kdeartwork3-3.5.10-92.2.x86_64 kdebase3-SuSE-branding-openSUSE-11.3-72.1.x86_64
and rebooted into TDE greeter. It would have been nice if it had offered to import settings from ~/.kde, but it seems to be working OK.
GTK styles & fonts produces nothing to do (kcontrol startup panel content) in kcontrol. Keyboard retains the same inane 660msec default delay as KDE always has. cf. https://bugs.kde.org/show_bug.cgi?id=279201
On 2012-11-28 21:26 (GMT+0100) François ANDRIOT composed:
What does the 'kdelibs3.conf' file contain ? I bet it contains "/opt/kde3/lib64" ...
Too late to look now. I think:
/usr/local/lib64 /usr/local/lib include /etc/ld.so.conf.d/*.conf
is what was in it.
From what I see in your packages, everything you installed from KDE3 exist in TDE (except some Suse-specific artwork packages).
Before uninstalling KDE3, you can try a last (dirty) trick: mv /opt/kde3 /opt/kde3.old ldconfig
then restart kdm again (or reboot).
Too late, but thanks a lot! :-)
Le 28/11/2012 21:59, Felix Miata a écrit :
I removed all remaining *kde*3* except the following:
kde-susetranslations-12.1-14.1.1.noarch kde3-gtk-qt-engine-0.8svn20071009-58.2.x86_64 kdeartwork3-3.5.10-92.2.x86_64 kdebase3-SuSE-branding-openSUSE-11.3-72.1.x86_64and rebooted into TDE greeter. It would have been nice if it had offered to import settings from ~/.kde, but it seems to be working OK.
OK this is what I thought. KDE3 conflicts with TDE. Until we find a trick, we cannot use both on the same computer.
You can remove "kdeartwork3" and install "trinity-tdeartwork". You can remove "kde3-gtk-qt-engine" and install "trinity-qt-engine".
About the 2 other packages, I don't know if they are specific to Suse, specific to KDE3, or both. But they are not needed (and not even used) by Trinity, so they are useless to you. You'd better remove them to avoid other strange side-effects.
GTK styles & fonts produces nothing to do (kcontrol startup panel content) in kcontrol.
If you have the "kde3-gtk-qt-engine" installed but not "trinity-gtk-qt-engine", it cannot work correctly.
Keyboard retains the same inane 660msec default delay as KDE always has. cf. https://bugs.kde.org/show_bug.cgi?id=279201
Nice find. It could be a Trinity enhancement, you should fill a bug report for it.
On 2012-11-28 21:26 (GMT+0100) François ANDRIOT composed:
What does the 'kdelibs3.conf' file contain ? I bet it contains "/opt/kde3/lib64" ...
Too late to look now. I think:
/usr/local/lib64 /usr/local/lib include /etc/ld.so.conf.d/*.confis what was in it.
Finally I've just installed KDE3 in my virtual machine which already had TDE, and I confirm that I have the exact same missing symbol as you have. FYI, the file /etc/ld.so.conf.d/kdelibs3.conf contains /opt/kde3/lib64 and /opt/kde3/lib . Since "kdelibs3.conf" comes before "trinity.conf" in alphabetical order, the kde3 libraries take precedence over Trinity libraries.
From what I see in your packages, everything you installed from KDE3 exist in TDE (except some Suse-specific artwork packages).
Before uninstalling KDE3, you can try a last (dirty) trick: mv /opt/kde3 /opt/kde3.old ldconfig
then restart kdm again (or reboot).
Too late, but thanks a lot! :-)
I'm glad it finally works for you :-) I hope you will enjoy Trinity.
Francois
On 2012-11-28 22:28 (GMT+0100) François ANDRIOT composed:
Felix Miata composed:
I removed all remaining *kde*3* except the following:
kde-susetranslations-12.1-14.1.1.noarch kde3-gtk-qt-engine-0.8svn20071009-58.2.x86_64 kdeartwork3-3.5.10-92.2.x86_64 kdebase3-SuSE-branding-openSUSE-11.3-72.1.x86_64
and rebooted into TDE greeter. It would have been nice if it had offered to import settings from ~/.kde, but it seems to be working OK.
OK this is what I thought. KDE3 conflicts with TDE. Until we find a trick, we cannot use both on the same computer.
I'm having a hard time imagining a need for both, as long as equivalent packages (that I use ;-) ) remain available on TDE for all available on KDE3.
You can remove "kdeartwork3" and install "trinity-tdeartwork".
Yikes! Adding this one pulled in 11 others.
You can remove "kde3-gtk-qt-engine" and install "trinity-qt-engine".
"No provider of 'trinity-qt-engine' found (but trinity-gtk-qt-engine is now installed).
About the 2 other packages, I don't know if they are specific to Suse, specific to KDE3, or both. But they are not needed (and not even used) by Trinity, so they are useless to you. You'd better remove them to avoid other strange side-effects.
They're gone now.
Keyboard retains the same inane 660msec default delay as KDE always has. cf. https://bugs.kde.org/show_bug.cgi?id=279201
Nice find. It could be a Trinity enhancement, you should fill a bug report for it.
http://bugs.trinitydesktop.org/bugzilla/bugzilla/bugzilla/bugzilla/show_bug....
I'm glad it finally works for you :-)
Not completely yet.
1-Init 3 from runlevel 5 fails to stop kdm, same as with KDE3 in 12.2. rcxdm stop and /etc/init.d/xdm stop don't stop it either.
2-startx instead of TDE starts icewm. Comments in /etc/sysconfig/windowmanager fail to say to make TDE the DEFAULT_WM it needs to be set to tde.
3-cnf starttde produces nothing. cnf startkde produces no hits in /opt/trinity/* or from TDE repo.
I hope you will enjoy Trinity.
I can't imagine it not. KDE3 is weak on maintenance resources. KDE4 is hopeless: https://bugs.kde.org/show_bug.cgi?id=158556 https://bugs.kde.org/show_bug.cgi?id=283366 https://bugs.kde.org/show_bug.cgi?id=297217 https://bugs.kde.org/show_bug.cgi?id=297219
This exercise was on my backup box to the system I run 24/7, trying to figure out whether an upgrade from 11.4 to 12.2 is doable. The bonus upgrade to TDE I hope will end the nonsense that updated KDE3 packages are inexplicably added to the mirrors practically every day.
In the meantime, I have at least a half dozen 12.2 systems, at least half of which have KDE3 instead of KDE4. Over time I'll probably convert at least 3 to TDE, but the next step will be a fresh minimal X with TDE on a box whose HD died week before last, which is waiting for me to put in the new one UPS brought me today.
Le 29/11/2012 02:06, Felix Miata a écrit :
On 2012-11-28 22:28 (GMT+0100) François ANDRIOT composed:
You can remove "kdeartwork3" and install "trinity-tdeartwork".
Yikes! Adding this one pulled in 11 others.
The TDE packaging is more "fine grained" than KDE3 packaging. The single "kdeartwork3" package is equivalent to the 11 Trinity packages. So you can selectively uninstall any program you don't want, without uninstalling everything from a package family.
You can remove "kde3-gtk-qt-engine" and install "trinity-qt-engine".
"No provider of 'trinity-qt-engine' found (but trinity-gtk-qt-engine is now installed).
Of course I mispelled it :) The package is trinity-gtk-qt-engine, as you found .
Not completely yet.
1-Init 3 from runlevel 5 fails to stop kdm, same as with KDE3 in 12.2. rcxdm stop and /etc/init.d/xdm stop don't stop it either.
Ok, I've found that openSUSE use specific configuration files to find which DM to use. Save the attached file as /usr/lib/X11/displaymanagers/tdm . Then set "DISPLAYMANAGER=tdm" in /etc/sysconfig/displaymanager
Then, edit file /opt/trinity/share/config/kdm/kdmrc Activate and set variable: PidFile=/var/run/tdm.pid
Now starting and shutting down TDM with openSUSE scripts should work.
I will make these changes to the next package release.
Alas, when stopping TDM, it looks like other processes forked by TDM (tsak ...) are not stopped...
2-startx instead of TDE starts icewm. Comments in /etc/sysconfig/windowmanager fail to say to make TDE the DEFAULT_WM it needs to be set to tde.
It looks like the comments are hardcoded in a template in an openSUSE package: /var/adm/fillup-templates/sysconfig.windowmanager You should fill a bug report on openSUSE bugtracker asking to add 'tde' to the list. (they are likely to refuse, since we are not upstream, and kde3 is absent too)
3-cnf starttde produces nothing. cnf startkde produces no hits in /opt/trinity/* or from TDE repo.
Mmm I have no clue about this. Maybe it's because the Trinity repository is in YUM format ...
I hope you will enjoy Trinity.
I can't imagine it not. KDE3 is weak on maintenance resources. KDE4 is hopeless: https://bugs.kde.org/show_bug.cgi?id=158556 https://bugs.kde.org/show_bug.cgi?id=283366 https://bugs.kde.org/show_bug.cgi?id=297217 https://bugs.kde.org/show_bug.cgi?id=297219
This exercise was on my backup box to the system I run 24/7, trying to figure out whether an upgrade from 11.4 to 12.2 is doable. The bonus upgrade to TDE I hope will end the nonsense that updated KDE3 packages are inexplicably added to the mirrors practically every day.
In the meantime, I have at least a half dozen 12.2 systems, at least half of which have KDE3 instead of KDE4. Over time I'll probably convert at least 3 to TDE, but the next step will be a fresh minimal X with TDE on a box whose HD died week before last, which is waiting for me to put in the new one UPS brought me today.
Good luck with that, it's nice to see people (willing to) use TDE in a larger scale than a single home computer :-)
Francois
On 2012-11-29 22:21 (GMT+0100) François ANDRIOT composed:
Felix Miata composed:
2-startx instead of TDE starts icewm. Comments in /etc/sysconfig/windowmanager fail to say to make TDE the DEFAULT_WM it needs to be set to tde.
It looks like the comments are hardcoded in a template in an openSUSE package: /var/adm/fillup-templates/sysconfig.windowmanager You should fill a bug report on openSUSE bugtracker asking to add 'tde' to the list. (they are likely to refuse, since we are not upstream, and kde3 is absent too)
Before there was KDE4 in openSUSE there was only KDE. For several releases, both were installation options. KDE4 did not, and still hasn't, fully replaced KDE3, though only 4 is offered by the GUI installer in recent releases. KDE3 was always called kde in the openSUSE filesystem and scripts, and still is, which is why no (IIRC) config file comments make mention of any kde3.
3-cnf starttde produces nothing. cnf startkde produces no hits in /opt/trinity/* or from TDE repo.
Mmm I have no clue about this. Maybe it's because the Trinity repository is in YUM format ...
Reasons for the original query: Which is it? What package provides it? Where does it live?
Le 29/11/2012 22:45, Felix Miata a écrit :
Reasons for the original query: Which is it? What package provides it? Where does it live?
Hello, in case you are still looking for it:
The script is: /opt/trinity/bin/startkde It is provided by package: trinity-ksmserver
Francois
Greetings,
I tried Francois's installation method and it worked. Thanks a lot for your helps.
Sincerely,
Eren
-
Eren -
Felix Miata -
Francois Andriot -
François ANDRIOT
-
Patrick Serru -
Thierry de Coulon