openSUSE KDE 3 January 2018

kde3@lists.opensuse.org

3 participants
6 discussions

[opensuse-kde3] Missing writing accents
by Helga Fischer 09 Jul '18

09 Jul '18

Hello List, how can I get back the ability writing accents on my KDE3-desktop? My System is openSUSE 13.1 with KDE3 (3.5.10 release 262) from inofficial Suse-repos. I'm using the keyboard layout with dead keys. Under KDE4 all applications can work with accents. Under KDE3 there is no application writing accents. Writing accents is active (kcontrol). Any hints (or is this behaviour a bug)?. Thanks, Helga -- ## Technik: [http://de.opensuse.org] ## Privat: [http://www.eschkitai.de] -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde3+owner(a)opensuse.org

4 18

[opensuse-kde3] "failed" display-manager service works as expected
by Felix Miata 10 Feb '18

10 Feb '18

# journalctl -u display-manager -- Logs begin at Mon 2016-11-28 04:06:57 EST, end at Wed 2018-01-31 04:15:02 EST. -- Jun 30 23:06:36 kdm[12087]: :0[12087]: pam_unix(xdm-np:session): session opened for user ##### by (uid=0) -- Reboot -- Jul 19 07:02:19 systemd[1]: Starting X Display Manager... Jul 19 07:02:19 display-manager[1647]: /etc/vconsole.conf available Jul 19 07:02:19 display-manager[1647]: KEYMAP: us Jul 19 07:02:19 display-manager[1647]: Command: localectl set-keymap us Jul 19 07:02:19 display-manager[1647]: I: Using systemd /usr/share/systemd/kbd-model-map mapping Jul 19 07:02:19 display-manager[1647]: Starting service kdm..done Jul 19 07:02:19 systemd[1]: PID file /var/run/displaymanager.pid not readable (yet?) after start. Jul 19 07:02:20 kdm_config[1672]: Multiple occurrences of key 'AllowRootLogin' in section [X-*-Core] of /opt/kde3/share/config/kdm/kdmrc Jul 19 07:02:20 kdm_config[1672]: Multiple occurrences of key 'ShowUsers' in section [X-*-Greeter] of /opt/kde3/share/config/kdm/kdmrc Jul 19 07:02:20 kdm_config[1672]: Multiple occurrences of key 'UseTheme' in section [X-*-Greeter] of /opt/kde3/share/config/kdm/kdmrc Jul 19 07:03:47 kdm[1691]: :0[1691]: pam_unix(xdm-np:session): session opened for user #### by (uid=0) Jul 19 07:03:49 systemd[1]: display-manager.service start operation timed out. Terminating. Jul 19 07:03:49 systemd[1]: Failed to start X Display Manager. Jul 19 07:03:49 systemd[1]: Unit display-manager.service entered failed state. ... -- Reboot -- Jan 30 23:04:00 systemd[1]: Starting X Display Manager... Jan 30 23:04:02 display-manager[1770]: /etc/vconsole.conf available Jan 30 23:04:02 display-manager[1770]: KEYMAP: us Jan 30 23:04:02 display-manager[1770]: Command: localectl set-keymap us Jan 30 23:04:03 display-manager[1770]: I: Using systemd /usr/share/systemd/kbd-model-map mapping Jan 30 23:04:03 display-manager[1770]: Starting service kdm..done Jan 30 23:04:03 systemd[1]: display-manager.service: PID file /var/run/displaymanager.pid not readable (yet?) after start: No such file or directory Jan 30 23:04:03 kdm_config[1816]: Multiple occurrences of key 'AllowRootLogin' in section [X-*-Core] of /opt/kde3/share/config/kdm/kdmrc Jan 30 23:04:03 kdm_config[1816]: Multiple occurrences of key 'ShowUsers' in section [X-*-Greeter] of /opt/kde3/share/config/kdm/kdmrc Jan 30 23:04:03 kdm_config[1816]: Multiple occurrences of key 'UseTheme' in section [X-*-Greeter] of /opt/kde3/share/config/kdm/kdmrc Jan 30 23:05:04 kdm[1825]: :0[1825]: pam_unix(xdm-np:session): session opened for user ##### by (uid=0) Jan 30 23:05:30 systemd[1]: display-manager.service: Start operation timed out. Terminating. Jan 30 23:05:30 systemd[1]: Failed to start X Display Manager. Jan 30 23:05:30 systemd[1]: display-manager.service: Unit entered failed state. Jan 30 23:05:30 systemd[1]: display-manager.service: Failed with result 'timeout'. I see no evidence of KDM failure using the PC. I'm typing this in a KDE3 session started from KDM3. Why are these putative systemd failure messages in the journal? -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (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(a)opensuse.org To contact the owner, e-mail: opensuse-kde3+owner(a)opensuse.org

2 7

[opensuse-kde3] BUG in KDE3 ? (Oups !)
by Patrick Serru 08 Feb '18

08 Feb '18

Hello all, I have a problem difficult to specify. I made a backup of my home directory yesterday. Today, after a few hours of operation, the processor started heating. This is not the first time this has happened (known solution!). A launch of ksysguard allows me to see that "systemd-coredum" uses 100% of the resources and renews itself permanently. Then, I kill X, and things calm down. When I log in as kde3 root, there is no problem. But every time I log in as a user: thermal runaway. Once restored my personal directory from yesterday, NO MORE PROBLEM. After the last restoration of my personal directory, I went back to where I was, considering the incident as closed. All of today's work was concentrated in a repertoire. So, I copied this directory as root, out of X and with the help of rsync, and then, again thermal runaway once the kde3 user cession re-opened:! For information, yesterday's repertoire (on which I worked) was 15.4 MB (16,164,103) and after today's work it was 50.1 MB (52,510,297). The system partition is 58.9 GB and is 87% occupied. I am conviced that a deamond like ksysguardd is invloved, but i'm really not sure. If you have an idea on how to find where it comes from, tell me, please. Thank you for the attention you paid to this mail. Patrick Serru Edit: < NO MORE PROBLEM > in stead of < MORE PROBLEM > -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde3+owner(a)opensuse.org

3 4

[opensuse-kde3] BUG in KDE3 ?
by Patrick Serru 26 Jan '18

26 Jan '18

Hello all, I have a problem difficult to specify. I made a backup of my home directory yesterday. Today, after a few hours of operation, the processor started heating. This is not the first time this has happened (known solution!). A launch of ksysguard allows me to see that "systemd-coredum" uses 100% of the resources and renews itself permanently. Then, I kill X, and things calm down. When I log in as kde3 root, there is no problem. But every time I log in as a user: thermal runaway. Once restored my personal directory from yesterday, MORE PROBLEM. After the last restoration of my personal directory, I went back to where I was, considering the incident as closed. All of today's work was concentrated in a repertoire. So, I copied this directory as root, out of X and with the help of rsync, and then, again thermal runaway once the kde3 user cession re-opened:! For information, yesterday's repertoire (on which I worked) was 15.4 MB (16,164,103) and after today's work it was 50.1 MB (52,510,297). The system partition is 58.9 GB and is 87% occupied. I am conviced that a deamond like ksysguardd is invloved, but i'm really not sure. If you have an idea on how to find where it comes from, tell me, please. Thank you for the attention you paid to this mail. Patrick Serru -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde3+owner(a)opensuse.org

1 0

[opensuse-kde3] K3B fubar (redo)
by Felix Miata 22 Jan '18

22 Jan '18

Trying to copy a DVDR-produced DVD using K3B on this 42.3/KDE3 system causes the CPU to peg and K3B to freeze. It also exhausts free RAM. I have to exit the KDE session to normalize the desktop. If I only want to burn an existing .iso to DVD, then K3B works as expected. A month or more ago, K3B always worked as expected. So I tried to use a different 42.3/KDE3 PC to see if it would work, and K3B complains about MAD not being installed. When I try to install kdemultimedia3-mad, zypper complains nothing provides mad. On this system, there is no current "mad" available, only as you can see here: i | libmad0 | package | 0.15.1b-4.1 | x86_64 | (System Packages) v | libmad0 | package | 0.15.1b-2.1 | x86_64 | Update I don't know why the current libmad0 is shown as an older version than that installed. About mad, I filed a bug: https://bugzilla.opensuse.org/show_bug.cgi?id=1076935 I gave up enabling mad on the other PC and tried with K3B to copy the DVD, which should have nothing to do with mad anyway. It too pegs the CPU and writes 0 bytes to the tmp file. On the first attempt, I did Ctrl-Alt-F3 first to run top. On return to KDE3, K3B had disappeared. On the second attempt, after several minutes of 0 progress K3B simply disappeared. Third try I logged in as root to run K3B with same failing result. On the 4th try with a different DVD made with a different recorder, the K3B crash aborted the KDE3 session as Xorg process was killed due to RAM exhaustion. Does K3B DVD copying work for anyone here who has 42.3 fully updated? -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (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(a)opensuse.org To contact the owner, e-mail: opensuse-kde3+owner(a)opensuse.org

1 0

[opensuse-kde3] K3B fubar
by Felix Miata 22 Jan '18

22 Jan '18

Trying to copy a DVDR-produced DVD using K3B on this 42.3/KDE3 system causes the CPU to peg and K3B to freeze. I have to exit the KDE session to normalize the desktop. If I only want to burn an existing .iso to DVD, then K3B works as expected. A month or more ago, K3B always worked as expected. So I tried to use a different 42.3/KDE3 PC to see if it would work, and K3B complains about MAD not being installed. When I try to install kdemultimedia3-mad, zypper complains nothing provides mad. On this system, there is no current "mad" available, only as you can see here: i | libmad0 | package | 0.15.1b-4.1 | x86_64 | (System Packages) v | libmad0 | package | 0.15.1b-2.1 | x86_64 | Update I don't know why the current libmad0 is shown as an older version than that installed. About mad, I filed a bug: https://bugzilla.opensuse.org/show_bug.cgi?id=1076935 I gave up enabling mad on the other PC and tried with K3B to copy the DVD, which should have nothing to do with mad anyway. It too pegs the CPU and writes 0 bytes to the tmp file. On the first attempt, I did Ctrl-Alt-F3 first to run top. On return to KDE3, K3B had disappeared. On the second attempt, after several minutes of 0 progress K3B simply disappeared. Third try I logged in as root to run K3B with same failing result. On the 4th try with a different DVD made with a different recorder, the K3B crash aborted the KDE3 session. Does K3B DVD copying work for anyone here who has 42.3 fully updated? -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (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(a)opensuse.org To contact the owner, e-mail: opensuse-kde3+owner(a)opensuse.org

1 0

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

openSUSE KDE 3 January 2018