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
Hi!
I am about to install openSUSE 12.1 on a laptop. I want to use it mainly
(or entirely) with the KDE3 desktop but I still want to be able to run
KDE4 applications under KDE3. In the past, I have done this with openSUSE
11.3 and 11.4. During installation of 11.3 and 11.4, I selected KDE4 as
the default desktop. Then I added the KDE:KDE3 repository and installed
all the packages to properly run KDE3 following more or less the
recommendations given here:
HOW-TO: KDE 3.5 on 11.4
This has worked perfectly and I was even able to use the oxygen theme in
KDE3. For example, okular and vlc came with the nice oxygen theme even
when running under KDE3.
My question is: Is this procedure going to work also with openSUSE 12.1 or
is there anything in particular I have to pay attention to?
Thanks!
Gianluca
--
To unsubscribe, e-mail: opensuse-kde3+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-kde3+owner(a)opensuse.org
Hi KDE3 fans,
Some time ago I started a new implementation for NM client (my version will
be integrated into kcontrol). A screenshot attached. I hope I will have some
spare time to finish it someday.
--
Serghei
-------- Original Message --------
Subject: [opensuse] Re: [opensuse-kde3] 13.1 kde3 build is not removing all
calls to HAL
Date: Sat, 30 Aug 2014 19:38:28 -0500
From: David C. Rankin <drankinatty(a)suddenlinkmail.com>
Organization: Rankin Law Firm, PLLC
To: suse <opensuse(a)opensuse.org>
On 08/30/2014 05:52 PM, Felix Miata wrote:
>
>> NAICT, all KDE3's own virtues remain in the fork, plus the fork gets the
> fixes required to work with the evolving foundations, such as systemd and the
> myriad of changes systemd has caused to X.
>
> What changes related to systemd support Trinity has that KDE3 in openSUSE does not?
None -- that is where I'm stuck with Arch. TDE has the same manpower problems we
do here. Here is the relevant bug (I filed it)
http://bugs.pearsoncomputing.net/show_bug.cgi?id=1998
>
> In fact Ubuntu (for which Trinity is developed) migrated to systemd the last of
> all major
> distributions. So Tribnity migrated to systemd after openSUSE's KDE3 did.
>
If there were advantages to moving to TDE, I'd be the first to say -- Migrate to
TDE, but after building TDE for 3 years and running kde3/opensuse for the same
time, there just are not any huge driving reasons for changing, and it just
complicates application development with the Qt/TQt name changes.
T
--
David C. Rankin, J.D.,P.E.
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
--
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
Ilya,
The kneworkmanager app started to run-away with 100% of CPU again. Checking
.xsession-errors, I found the following:
KNotify::playTimeout
jack_client_new: deprecated
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
akode: Guessed format: wav
KNotify::playTimeout
libpng warning: iCCP: known incorrect sRGB profile
1409156905331 addons.update-checker WARN Update manifest for
{989e9382-d540-4189-88d1-fc54a949a387} did not contain an updates property
1409156905507 addons.update-checker WARN Update manifest for
susefox(a)opensuse.org did not contain an updates property
1409156905531 addons.update-checker WARN Update manifest for
{586bd060-22d6-11de-8c30-0800200c9a66} did not contain an updates property
1409156905840 addons.update-checker WARN Update manifest for
{972ce4c6-7e08-4474-a285-3208198ce6fd} did not contain an updates property
Xlib: extension "XFree86-Misc" missing on display ":0".
X Error: BadAccess (attempt to access private resource denied) 10
Major opcode: 2
Minor opcode: 0
Resource id: 0x3600011
sh: hal-find-by-property: command not found
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
WARNING: DCOPReply<>: cast to 'QStringList' error
WARNING: DCOPReply<>: cast to 'QString' error
Something is still making calls to `hal-find-by-property`. If suse kde3 is
build NOHAL, then there is something that needs fixing.
Also, as asked numerous times, where are bugs supposed to be reported? I have
reported a half-dozen or so here to the list, but I really feel they need to go
to some tracker associated with whoever is building kde3 for opensuse. These
little things need fixing before they accumulate too badly.
--
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
-------- Original Message --------
Subject: [opensuse] Re: [opensuse-kde3] 13.1 kde3 build is not removing all
calls to HAL
Date: Sat, 30 Aug 2014 18:41:11 -0500
From: David C. Rankin <drankinatty(a)suddenlinkmail.com>
Organization: Rankin Law Firm, PLLC
To: suse <opensuse(a)opensuse.org>
On 08/29/2014 03:06 PM, Serghei Amelian wrote:
> On Friday 29 August 2014 23:01:19 Kyrill Detinov wrote:
>> Kyrill, I currently have no spare time and do not use nertworkmanager
>> anyway,
>> but Serghei Amelian has a fixed version of knetworkmanager-kde3? compatible
>> with the current networkmanager (although some patches from our version may
>> require porting there).
>
> Some time ago I started to implement a new knetworkmanager, but unfortunately
> I have no time to continue it. Maybe sometime... :)
>
Serghei,
If you made any headway, do you still have a copy of any patches you developed?
I'll take the current knetworkmanager source and develop a patch for the new
systemd network interface naming schemes. But when I have one -- who do I submit
it to for building/testing?? Ilya, Kyrill, you?
--
David C. Rankin, J.D.,P.E.
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
--
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
-------- Original Message --------
Subject: [opensuse] Re: [opensuse-kde3] 13.1 kde3 build is not removing all
calls to HAL
Date: Sat, 30 Aug 2014 18:31:52 -0500
From: David C. Rankin <drankinatty(a)suddenlinkmail.com>
Organization: Rankin Law Firm, PLLC
To: suse <opensuse(a)opensuse.org>
On 08/29/2014 12:31 PM, Kyrill Detinov wrote:
>
> On Thu, 28 Aug 2014 15:21:52 -0500 David C. Rankin wrote:
>
>> Also, as asked numerous times, where are bugs supposed to be
>> reported? I have reported a half-dozen or so here to the list, but I
>> really feel they need to go to some tracker associated with whoever
>> is building kde3 for opensuse. These little things need fixing before
>> they accumulate too badly.
>
> I'm very sorry to say, David…
> It seems, we (openSUSE) can't keep KDE3 in working state without
> "fresh blood" (if anybody still cares).
>
Kyrill,
I CARE!!! Please tell point me to a link for building KDE3 on openSuSE and
I'm happy to give it a shot. I do not have an opensuse build environment for
kde3 so I'm hoping that it can be done through build service somehow. I build
TDE for Archlinux, so I'm familiar with the kde3 codebase, the only challenge
for opensuse/kde3 is the how/where to setup a project to do it. I would really
rather avoid downloading all srpms and attempting to reconstruct the build
environment here -- so what is the best way to do this?
--
David C. Rankin, J.D.,P.E.
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
--
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
This message is forwarded from Serghei Amelian.
The message is empty in my client, Claws Mail.
Something goes wrong.
I've got:
Subject: Re: [opensuse-kde3] 13.1 kde3 build is not removing all calls to HAL
From: Kyrill Detinov <anixx***(a)*****.com>
To: <opensuse-kde3(a)*********.org>
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
> From: Kyrill Detinov <anixx***@
That's wrong.
Probably addressed to Ilya.
And
--
WBR
Kyrill
Ilya,
I had a runaway knetworkmanager pegging the cpu at 100% constantly. I don't
know what caused it to race, but it almost melted my laptop down. Here is a
screenshot of the 'top' output:
http://www.3111skyline.com/dl/bugs/openSuSE/131/kde3/KNetworkMgr-100cpu.jpg
I suspect this is related to the new interface renaming (ath -> wlp) that
causes networkmanager to not see the actual network connection. (that is why the
systray icon stays the green globe instead of turning into the bar-graph showing
connection)
Let me know what else you would like to see.
--
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
All,
Every so often knotify will crash. (sample kcrash attached). When this occurs
all systems sounds stop. I still get the beep and I can still play sound files,
but all desktop sounds (shade/unshade, minimize, etc..) stop. How can I restart
knotify (or whatever crashed) to recover desktop sounds without having to
shutdown and restart kde?
--
David C. Rankin, J.D.,P.E.