[opensuse-kde3] Oss 13.1 + KDE3
Hi All, Now that I know that my Amd FX mather borad is not damaged (a problem of disques posted earlyer), I dicided to try to reinstal Oss 13.1. I am happy because the X "nouveau" nvidia driver (or whatever Oss had installed is stable an I did not have any problem. Neither at the boot time nor at the X stating time. Nice, and thank a lot to the involved developpers! I just did the intallation today (2014-05-04). The problem is that the task bar is not compatible with th sound (as fare as I see). Whwn I restarted the sound system with help of yast, the task bar desapears. The noise made by the circuitry i well audible until kdm starts kde3. Pulseaudio is not installed. Can someone tell me, please, How could I diasable the task bar in KDE, waiting for an update (if my thinking is correct on the source of the sound problem) ? Thank you, and cheers. Patrick -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
What happens if you kill and restart kicker? Gianluca On Sun, 4 May 2014, Patrick Serru wrote:
Hi All,
Now that I know that my Amd FX mather borad is not damaged (a problem of disques posted earlyer), I dicided to try to reinstal Oss 13.1.
I am happy because the X "nouveau" nvidia driver (or whatever Oss had installed is stable an I did not have any problem. Neither at the boot time nor at the X stating time. Nice, and thank a lot to the involved developpers!
I just did the intallation today (2014-05-04). The problem is that the task bar is not compatible with th sound (as fare as I see). Whwn I restarted the sound system with help of yast, the task bar desapears. The noise made by the circuitry i well audible until kdm starts kde3. Pulseaudio is not installed. Can someone tell me, please, How could I diasable the task bar in KDE, waiting for an update (if my thinking is correct on the source of the sound problem) ?
Thank you, and cheers. Patrick -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
----------------------------------------------------- Gianluca Interlandi, PhD gianluca@u.washington.edu +1 (206) 685 4435 http://artemide.bioeng.washington.edu/ Research Scientist at the Department of Bioengineering at the University of Washington, Seattle WA U.S.A. ----------------------------------------------------- -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
Le dimanche 04 mai 2014, Gianluca Interlandi a écrit :
What happens if you kill and restart kicker?
Gianluca
On Sun, 4 May 2014, Patrick Serru wrote:
Hi All,
Now that I know that my Amd FX mather borad is not damaged (a problem of disques posted earlyer), I dicided to try to reinstal Oss 13.1.
I am happy because the X "nouveau" nvidia driver (or whatever Oss had installed is stable an I did not have any problem. Neither at the boot time nor at the X stating time. Nice, and thank a lot to the involved developpers!
I just did the intallation today (2014-05-04). The problem is that the task bar is not compatible with th sound (as fare as I see). Whwn I restarted the sound system with help of yast, the task bar desapears. The noise made by the circuitry i well audible until kdm starts kde3. Pulseaudio is not installed. Can someone tell me, please, How could I diasable the task bar in KDE, waiting for an update (if my thinking is correct on the source of the sound problem) ?
Thank you, and cheers. Patrick -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
----------------------------------------------------- Gianluca Interlandi, PhD gianluca@u.washington.edu +1 (206) 685 4435 http://artemide.bioeng.washington.edu/
Research Scientist at the Department of Bioengineering at the University of Washington, Seattle WA U.S.A. ----------------------------------------------------- Hi Gianluca,
Thank a lot for your response. I have been waiting too long to try ??? I just tryed now and X did not started properly after two boot. I use to start my actual Oss 12.2 in mode 3, login as root and then “init 5↵” to start the graphic system. If X starts in an other definition than 1280x1024, I press Ctrl+Alt+1 and type “init3 ; sleep 3 ; init 5↵” to restart X. I would say that most of the time, I dont need to restart X that way, but when X starts bad, I can repeat the last step up to 5 times before X starts in the correct definition. I installed Oss 13.1 the same way. But tonight, X started bad and I have not been able to recover tty0 pressing Ctrl+Alt+1. So, I did have the oportunity to kill “kicker”. Every thing was blocked and I am not sure Ctrl+Alt+Suppr worked but rather the power button of the PC did. I am ready to make other test if needed. Cheers Patrick -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
What I meant was to kill kicker, i.e., issue the command: ps aux | grep kicker | grep -v grep Then note the number in the second column <procID> (after your username) and kill it with: kill <procID> Sometimes you have to try with kill -9 <procID> Then restart it by typing "kicker" in the konsole. If you want to start X in init 3, starting with openSUSE 12.3 you have to change the permissions of /usr/bin/Xorg. You need to make sure that you have: $ ls -l /usr/bin/Xorg -rws--x--x 1 root root 2150176 Jul 15 2013 /usr/bin/Xorg Note the "rws". You need to set the SUID flag with (I believe): chmod u+s /usr/bin/Xorg but check on that. Gianluca On Thu, 15 May 2014, Patrick Serru wrote:
Le dimanche 04 mai 2014, Gianluca Interlandi a écrit :
What happens if you kill and restart kicker?
Gianluca
On Sun, 4 May 2014, Patrick Serru wrote:
Hi All,
Now that I know that my Amd FX mather borad is not damaged (a problem of disques posted earlyer), I dicided to try to reinstal Oss 13.1.
I am happy because the X "nouveau" nvidia driver (or whatever Oss had installed is stable an I did not have any problem. Neither at the boot time nor at the X stating time. Nice, and thank a lot to the involved developpers!
I just did the intallation today (2014-05-04). The problem is that the task bar is not compatible with th sound (as fare as I see). Whwn I restarted the sound system with help of yast, the task bar desapears. The noise made by the circuitry i well audible until kdm starts kde3. Pulseaudio is not installed. Can someone tell me, please, How could I diasable the task bar in KDE, waiting for an update (if my thinking is correct on the source of the sound problem) ?
Thank you, and cheers. Patrick -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
----------------------------------------------------- Gianluca Interlandi, PhD gianluca@u.washington.edu +1 (206) 685 4435 http://artemide.bioeng.washington.edu/
Research Scientist at the Department of Bioengineering at the University of Washington, Seattle WA U.S.A. ----------------------------------------------------- Hi Gianluca,
Thank a lot for your response. I have been waiting too long to try ??? I just tryed now and X did not started properly after two boot.
I use to start my actual Oss 12.2 in mode 3, login as root and then ?init 5?? to start the graphic system. If X starts in an other definition than 1280x1024, I press Ctrl+Alt+1 and type ?init3 ; sleep 3 ; init 5?? to restart X. I would say that most of the time, I dont need to restart X that way, but when X starts bad, I can repeat the last step up to 5 times before X starts in the correct definition.
I installed Oss 13.1 the same way. But tonight, X started bad and I have not been able to recover tty0 pressing Ctrl+Alt+1. So, I did have the oportunity to kill ?kicker?. Every thing was blocked and I am not sure Ctrl+Alt+Suppr worked but rather the power button of the PC did.
I am ready to make other test if needed.
Cheers Patrick -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
----------------------------------------------------- Gianluca Interlandi, PhD gianluca@u.washington.edu +1 (206) 685 4435 http://artemide.bioeng.washington.edu/ Research Scientist at the Department of Bioengineering at the University of Washington, Seattle WA U.S.A. -----------------------------------------------------
On 2014-05-15 20:15 (GMT-0700) Gianluca Interlandi composed:
If you want to start X in init 3, starting with openSUSE 12.3 you have to change the permissions of /usr/bin/Xorg. You need to make sure that you have:
$ ls -l /usr/bin/Xorg -rws--x--x 1 root root 2150176 Jul 15 2013 /usr/bin/Xorg
Note the "rws". You need to set the SUID flag with (I believe):
chmod u+s /usr/bin/Xorg
Or per /etc/permissions.local: chmod 4711 /usr/bin/Xorg -- "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/ -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
Le jeudi 15 mai 2014, vous avez écrit :
What I meant was to kill kicker, i.e., issue the command:
ps aux | grep kicker | grep -v grep
Then note the number in the second column <procID> (after your username) and kill it with:
kill <procID>
Sometimes you have to try with
kill -9 <procID>
Then restart it by typing "kicker" in the konsole.
If you want to start X in init 3, starting with openSUSE 12.3 you have to change the permissions of /usr/bin/Xorg. You need to make sure that you have:
$ ls -l /usr/bin/Xorg -rws--x--x 1 root root 2150176 Jul 15 2013 /usr/bin/Xorg
Note the "rws". You need to set the SUID flag with (I believe):
chmod u+s /usr/bin/Xorg
but check on that.
Gianluca
On Thu, 15 May 2014, Patrick Serru wrote:
Le dimanche 04 mai 2014, Gianluca Interlandi a écrit :
What happens if you kill and restart kicker?
Gianluca
On Sun, 4 May 2014, Patrick Serru wrote:
Hi All,
Now that I know that my Amd FX mather borad is not damaged (a problem of disques posted earlyer), I dicided to try to reinstal Oss 13.1.
I am happy because the X "nouveau" nvidia driver (or whatever Oss had installed is stable an I did not have any problem. Neither at the boot time nor at the X stating time. Nice, and thank a lot to the involved developpers!
I just did the intallation today (2014-05-04). The problem is that the task bar is not compatible with th sound (as fare as I see). Whwn I restarted the sound system with help of yast, the task bar desapears. The noise made by the circuitry i well audible until kdm starts kde3. Pulseaudio is not installed. Can someone tell me, please, How could I diasable the task bar in KDE, waiting for an update (if my thinking is correct on the source of the sound problem) ?
Thank you, and cheers. Patrick -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
----------------------------------------------------- Gianluca Interlandi, PhD gianluca@u.washington.edu +1 (206) 685 4435 http://artemide.bioeng.washington.edu/
Research Scientist at the Department of Bioengineering at the University of Washington, Seattle WA U.S.A. -----------------------------------------------------
Hi Gianluca,
Thank a lot for your response. I have been waiting too long to try ??? I just tryed now and X did not started properly after two boot.
I use to start my actual Oss 12.2 in mode 3, login as root and then ?init 5?? to start the graphic system. If X starts in an other definition than 1280x1024, I press Ctrl+Alt+1 and type ?init3 ; sleep 3 ; init 5?? to restart X. I would say that most of the time, I dont need to restart X that way, but when X starts bad, I can repeat the last step up to 5 times before X starts in the correct definition.
I installed Oss 13.1 the same way. But tonight, X started bad and I have not been able to recover tty0 pressing Ctrl+Alt+1. So, I did have the oportunity to kill ?kicker?. Every thing was blocked and I am not sure Ctrl+Alt+Suppr worked but rather the power button of the PC did.
I am ready to make other test if needed.
Cheers Patrick -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
Hi Gianluca, I know that my english is bad. I tryed to say that some weeks ago, Oss 13.1 was running up to starting KDE3 as user. But yesturday, no. To kill and restart "kicker" should not be a problem to me, but KDE3 must be started to do it (or am I confused ?). X did not start properly until the graphic login, like before. I write X but that is my interpretation, because I typed "init 5" from a TTY root login. Even worse: I was not able to get back into tty0 nor able to see some eventual error messages on an others texte screens (ie using Ctrl+Alt+F1 or Alt+→ or Alt+←). Could GRUB be involved in my difficulties to restart my Oss 13.1 ? ------------------------------------------------------------------ After installation of 13.1, 13.1 was booting correctly. The extended partition was marked to bee bootable. I have a Windows 7 on the disk. I dont use it, but as it was the only way to check the hardware of the moterboard… I tryed to boot Windows and the bootable flag moved to the Windows partition (I know why: it's my "fault"). Then I boot 13.1 an other way, but I wonder if ther is no relation between these recent difficulties with 13.1. The question could look creasy but as there is something looking like random error with display style memory dump ("DRM" I think, comming from BIOS) ? Looking like some gabage that could appear in memory while the mather board wakes up. Does KDM3 work properly ? ------------------------- I wonder if, during the last trying of KDE3, I did not follow the explanation on how to login with kdm3 (on http://en.opensuse.org/KDE3) ? Thak you, Patrick Serru -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
Hi Patrick, Sorry. It's hard to tell why your KDE3 installation stopped working. Are any other window managers, like lxde or even KDE4 working? Gianluca On Fri, 16 May 2014, Patrick Serru wrote:
Le jeudi 15 mai 2014, vous avez écrit :
What I meant was to kill kicker, i.e., issue the command:
ps aux | grep kicker | grep -v grep
Then note the number in the second column <procID> (after your username) and kill it with:
kill <procID>
Sometimes you have to try with
kill -9 <procID>
Then restart it by typing "kicker" in the konsole.
If you want to start X in init 3, starting with openSUSE 12.3 you have to change the permissions of /usr/bin/Xorg. You need to make sure that you have:
$ ls -l /usr/bin/Xorg -rws--x--x 1 root root 2150176 Jul 15 2013 /usr/bin/Xorg
Note the "rws". You need to set the SUID flag with (I believe):
chmod u+s /usr/bin/Xorg
but check on that.
Gianluca
On Thu, 15 May 2014, Patrick Serru wrote:
Le dimanche 04 mai 2014, Gianluca Interlandi a écrit :
What happens if you kill and restart kicker?
Gianluca
On Sun, 4 May 2014, Patrick Serru wrote:
Hi All,
Now that I know that my Amd FX mather borad is not damaged (a problem of disques posted earlyer), I dicided to try to reinstal Oss 13.1.
I am happy because the X "nouveau" nvidia driver (or whatever Oss had installed is stable an I did not have any problem. Neither at the boot time nor at the X stating time. Nice, and thank a lot to the involved developpers!
I just did the intallation today (2014-05-04). The problem is that the task bar is not compatible with th sound (as fare as I see). Whwn I restarted the sound system with help of yast, the task bar desapears. The noise made by the circuitry i well audible until kdm starts kde3. Pulseaudio is not installed. Can someone tell me, please, How could I diasable the task bar in KDE, waiting for an update (if my thinking is correct on the source of the sound problem) ?
Thank you, and cheers. Patrick -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
----------------------------------------------------- Gianluca Interlandi, PhD gianluca@u.washington.edu +1 (206) 685 4435 http://artemide.bioeng.washington.edu/
Research Scientist at the Department of Bioengineering at the University of Washington, Seattle WA U.S.A. -----------------------------------------------------
Hi Gianluca,
Thank a lot for your response. I have been waiting too long to try ??? I just tryed now and X did not started properly after two boot.
I use to start my actual Oss 12.2 in mode 3, login as root and then ?init 5?? to start the graphic system. If X starts in an other definition than 1280x1024, I press Ctrl+Alt+1 and type ?init3 ; sleep 3 ; init 5?? to restart X. I would say that most of the time, I dont need to restart X that way, but when X starts bad, I can repeat the last step up to 5 times before X starts in the correct definition.
I installed Oss 13.1 the same way. But tonight, X started bad and I have not been able to recover tty0 pressing Ctrl+Alt+1. So, I did have the oportunity to kill ?kicker?. Every thing was blocked and I am not sure Ctrl+Alt+Suppr worked but rather the power button of the PC did.
I am ready to make other test if needed.
Cheers Patrick -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
Hi Gianluca,
I know that my english is bad. I tryed to say that some weeks ago, Oss 13.1 was running up to starting KDE3 as user. But yesturday, no. To kill and restart "kicker" should not be a problem to me, but KDE3 must be started to do it (or am I confused ?).
X did not start properly until the graphic login, like before. I write X but that is my interpretation, because I typed "init 5" from a TTY root login. Even worse: I was not able to get back into tty0 nor able to see some eventual error messages on an others texte screens (ie using Ctrl+Alt+F1 or Alt+? or Alt+?).
Could GRUB be involved in my difficulties to restart my Oss 13.1 ? ------------------------------------------------------------------ After installation of 13.1, 13.1 was booting correctly. The extended partition was marked to bee bootable. I have a Windows 7 on the disk. I dont use it, but as it was the only way to check the hardware of the moterboard? I tryed to boot Windows and the bootable flag moved to the Windows partition (I know why: it's my "fault"). Then I boot 13.1 an other way, but I wonder if ther is no relation between these recent difficulties with 13.1. The question could look creasy but as there is something looking like random error with display style memory dump ("DRM" I think, comming from BIOS) ? Looking like some gabage that could appear in memory while the mather board wakes up.
Does KDM3 work properly ? ------------------------- I wonder if, during the last trying of KDE3, I did not follow the explanation on how to login with kdm3 (on http://en.opensuse.org/KDE3) ?
Thak you, Patrick Serru
----------------------------------------------------- Gianluca Interlandi, PhD gianluca@u.washington.edu +1 (206) 685 4435 http://artemide.bioeng.washington.edu/ Research Scientist at the Department of Bioengineering at the University of Washington, Seattle WA U.S.A. -----------------------------------------------------
participants (3)
-
Felix Miata -
Gianluca Interlandi -
Patrick Serru