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
(Filing KDE3 bugs hasn't produces any apparent results in a very long time.)
I went ahead and installed the newer libIlmImf-2_2-2* that was available, then
force installed kdebase3-kdm, and it seems to have no problem doing its job. I
use it with useTheme=no, so maybe that's why it works.
--
"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
All,
I did my monthly update to the latest master of FW5 (17.12) and Plasma
(5.12) and it continues to be horrendous. I don't know why I keep hoping that
desktop will become usable -- only to be repeatedly disappointed with each
latest and greatest version. Simple things don't work, the pager takes up 1/4
of the taskbar, there is no way to tell it to use 2-row that is a simply
mouse-click in KDE3, there is no way to control the damn clock and calendar
font size leaving it looking like an awkward blob of text at the lower-right
of the desktop, and on, and on, and on......
Which makes KDE3 and imperative for 15. Otherwise, it fluxbox, xfe,
galculator and geany (not a bad combo at all, but not KDE3, and no tabbed
konsole!)
It is time to raise our collective voices to the packagers of KDE3 and say
"We want to help! We will code for KDE3 on 15!" It is desperately needed,
especially for older laptops that don't have 4G and 4cores (and for all the
other reasons I've documented here and on the suse list)
Let us know what stumbling blocks there are to the build, show us where the
build service project is and we can help. Let's make this work for 15.
--
David C. Rankin, J.D.,P.E.
--
To unsubscribe, e-mail: opensuse-kde3+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-kde3+owner(a)opensuse.org
# 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
All,
This is truly a testament to the team approach and depth of thought that
went into the KDE3 desktop design. After more than a decade using KDE3, I am
still discovering little gems you wouldn't normally think about, but when you
see them implemented you think "You know, that was a damn good idea!"
Take today, clicking on my 'Konsole-Restore Sessions' menu item to run the
script to launch konsole and restore my 9 konsole tabas with ssh connections
established, I looked at the tip-window (the "Show Tips on Startup"). To my
surprise it was one I had not seen before. The tip widow is always captioned
Did you know?
... pressing Ctrl while pasting the selection with the middle mouse button
will append a carriage return after pasting the selection buffer?
Thinking... well yes, if I have a non-newline terminated command in the
select buffer, and I want to run it with the least possible disturbance to the
position of my left hand on the keyboard and right hand on the mouse, the most
efficient way to do that would be to utilize a control key available on the
left side of the keyboard...
It is that thoroughness that is totally missing in the latest incarnation of
KDE. From what I have observed, probably the result of KDE development being
fractured into many little camps with only 1, at most 2 people working on any
app and absolutely no level of overall desktop use efficiency coordination
between them.
You cannot go back and build this type of efficiency and good design into a
desktop after you port all the apps to your newest gotta-have widget library,
it is either something built into the design of the desktop from the
beginning, or it is lost forever.
That is why there will never be another desktop with the sheer use
efficiency that KDE3 has.
--
David C. Rankin, J.D.,P.E.
--
To unsubscribe, e-mail: opensuse-kde3+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-kde3+owner(a)opensuse.org
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