KDE4 observations
Hi, having installed KDE4 from experimental this weekend I noticed two major problems: - some components cause insane amounts of wakeups (about 100++/s) which result in a power consumtion about 1.5 time the consumption if the latest kde3 packages from unstable. - regardless of eye candy options, maximizing windows takes about 3-5s, during which th system is completely unresponsive. (needlessly to say that I switched back to kde3 within an hour or so ;-) The machine is a Lenovo Z61m with an ATI Radeon Mobility X1400. I use the lastest fglrx driver. regards, Dietz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: KDE4 observations
Hi, thanks for the tip regarding the radeon driver, I'll give it a try the next days. Regarding the wakeups, I'm quite sure that some of the kde guys simply forgot how to use the "timeout" parameter for a select() or poll(). Should be no big deal to figure out ;-). regards, Dietz Karthik Ramgopal: > Hi, The slow window drawing problem may be linked to fglrx. Your > chipset is supported by the open source radeon driver (xf86-video-ati). > Just pull in Xorg, mesa, and xf86-video-ati from experimental. Edit the > xorg.conf to make it use "radeon" as the Driver, and enable EXA. The > slow window drawing problem should go away. As for the power consumption > issue, Im clueless. > > Regards, > Karthik > > On Mon, Sep 22, 2008 at 6:54 PM, Dietz Proepper <[EMAIL PROTECTED]>wrote: > > Hi, > > > > having installed KDE4 from experimental this weekend I noticed two > > major problems: > > - some components cause insane amounts of wakeups (about 100++/s) > > which result in a power consumtion about 1.5 time the consumption if > > the latest kde3 packages from unstable. > > - regardless of eye candy options, maximizing windows takes about > > 3-5s, during which th system is completely unresponsive. > > > > (needlessly to say that I switched back to kde3 within an hour or so > > ;-) > > > > The machine is a Lenovo Z61m with an ATI Radeon Mobility X1400. I use > > the lastest fglrx driver. > > > > regards, > >Dietz > > > > > > -- > > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > > with a subject of "unsubscribe". Trouble? Contact > > [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
KDEPIM 17.08, korgac
Hello, I upgraded to the latest kdepim version from experimental yesterday and it seems to work quite nicely. And so many beloved glitches are gone :-). Even email search seems to work again. Many, many thanks to our great maintainers! Just one issue: korgac seems not to produce reminders anymore. Any idea? Kindest regards Dietz -- Name the puppet master signature.asc Description: This is a digitally signed message part.
Re: KMail 17.08.3 mail composer always initially in rich text mode
Hi, Am Mittwoch, 27. Dezember 2017, 14:51:13 CET schrieb Martin Steigerwald: > Since some time of using KMail 17.08.3 (not with 17.08.0) I have it that > the KMail mail composing editor always starts in rich text mode. I can confirm that one. > I certainly did not tell it to do so. I checked the global settings and > its disabled there. I did not even find the place in global setting (I assume, you mean Composer/Global Settings) to disable that behaviour. Regards, Dietz -- Name the puppet master signature.asc Description: This is a digitally signed message part.
Re: Qt transition about to start
Hi, Am Mittwoch, 25. Juli 2018, 13:32:53 CEST schrieb Lisandro Damián Nicanor Pérez Meyer: > We are about to start the Qt 5.11.1 transition, so as usual beware when > updating your packages. Nice stuff :-), but I noticed a little anormality. Since the update, kontact seems to spawn a konqueror instance. Is that intended? Kindest regards, Dietz signature.asc Description: This is a digitally signed message part.
Re: preparation of KDE PIM 18.08 started in experimental
Hi Sandro Am Mittwoch, 19. September 2018, 00:03:45 CEST schrieb Sandro Knauß: > Why it takes so long till a kdepim version is ready? Well there is not > enough manpower doing the packaging. Additionally I was busy with other > stuff outside the computer the last weeks to make the version ready and I > needed to wait for the ftp masters to approve the library renaming. > Currently I hope that I can request the transition of kdepim 18.08 within > that month. I missed a file move and need another review of the ftp > masters. I am also not happy that it takes that long, but kdepim is not the > easy part to package... No need to apologise in any way! Your work is really appreciated, keep it goin' ! (And kdepim is a really big beast to hunt. ;-) ) signature.asc Description: This is a digitally signed message part.
Screensaver activation b0rken?
Hi, since the latest qt update in unstable (5.11.2), automatic screen saver activation does no longer work here. Manual activation is still fine. Regards, Dietz signature.asc Description: This is a digitally signed message part.
digiKam 6.0.0
Hi, a humble question - digiKam 6.0.0 is out some weeks now. Are there plans to package it? Kindest regards, Dietz signature.asc Description: This is a digitally signed message part.
Re: digiKam 6.0.0
Am Freitag, 1. März 2019, 11:57:41 CET schrieb Andrey Rahmatullin: > On Fri, Mar 01, 2019 at 11:33:08AM +0100, Dietz Proepper wrote: > > Hi, > > > > a humble question - digiKam 6.0.0 is out some weeks now. Are there plans > > to > > package it? > > We are currently frozen, by the way. Oops. Thx, I missed that. Regards Dietz signature.asc Description: This is a digitally signed message part.
Kmail crashes
Hi all, since two or three weeks, I have a strange problem with kmail (unstable). If I copy one message between two folders (imap) several times, kmail (or, more exactly kontact) crashes with a SIGSEGV. This seems to happen mainly with gpg encrypted mails. After restarting kmail, when I look at the folder the message got copied in again a SIGSEGV. The only way I can access the folder again is to delete and recreate the imap account (which is a little cumbersome). I can see the SIGSEGV message only if I start from a command line, not the kde crash handler. Does anyone else see this problem? And why do I not get that "your app crashed" window? Regards, Dietz signature.asc Description: This is a digitally signed message part.
Re: baloo, son of nepomuk
Am Freitag, 30. August 2019, 23:08:19 CEST schrieb Luigi Toscano: > bw ha scritto: > > Just did an upgrade from stretch, baloo is now doing the same thing > > nepomuk did back in the day. On logout, baloo_file process remains, so > > restarting the xserver causes duplicates, thus hanging up the > > baloo_file_extractor, and eating memory and cpu until crash... > > > quick and dirty workaround: > I can either disable it from systemsettings with a click, or at least ensure > that it only indexes the file names and not the contents. How do you do the latter? Regards Dietz signature.asc Description: This is a digitally signed message part.
Re: baloo, son of nepomuk
Am Sonntag, 1. September 2019, 12:54:50 CEST schrieb Luigi Toscano: > Dietz Proepper ha scritto: > > Am Freitag, 30. August 2019, 23:08:19 CEST schrieb Luigi Toscano: > >> bw ha scritto: > >>> Just did an upgrade from stretch, baloo is now doing the same thing > >>> nepomuk did back in the day. On logout, baloo_file process remains, so > >>> restarting the xserver causes duplicates, thus hanging up the > >>> baloo_file_extractor, and eating memory and cpu until crash... > >> > >>> quick and dirty workaround: > >> I can either disable it from systemsettings with a click, or at least > >> ensure that it only indexes the file names and not the contents. > > > > How do you do the latter? > > > >From the same systemsettings panel (Workspace->Search). There are only two > > options: > - "Enable File Search" > - "Also index file content" oO(must visit my optican ;-)) Thx alot! signature.asc Description: This is a digitally signed message part.
Re: KDE PIM 19.08.3 in unstable
Hi Sandro, Am Samstag, 30. November 2019, 23:09:10 CET schrieb Sandro Knauß: > Hey, > > I started to upload KDE PIM 19.08.3 to unstable. > > It is known, that following applications need to get rebuilt against KDEPIM > 19.08: > > kmymoney > kio-gdrive > kjots > kraft > zanshin > kgpg > > Like always, give the whole thing some days before upgrading. The current > state of the transition is covered here: > https://release.debian.org/transitions/html/kdepim-19.08.html Perfect timing - will make a nice sunday afternoon diversion. And thanks for all your work! Kindest regards, Dietz signature.asc Description: This is a digitally signed message part.
Re: KDE PIM 19.08.3 in unstable
Am Sonntag, 1. Dezember 2019, 14:57:58 CET schrieb Dietz Proepper: > Hi Sandro, > > Am Samstag, 30. November 2019, 23:09:10 CET schrieb Sandro Knauß: > > Hey, > > > > I started to upload KDE PIM 19.08.3 to unstable. [...] > Perfect timing - will make a nice sunday afternoon diversion. > > And thanks for all your work! And it seems to work fine out-of-the-box. For kgpg, using the version from experimental seems to work, too. And several very annoying bugs are gone. Once again - veeery nice work, buddy. signature.asc Description: This is a digitally signed message part.
Massive problems with kmail/akonadi
Hi, since some time, I encounter massive problems with kmail: - akonadi crashes every couple of hours. - moving mail between folders is b0rken badly (see https://bugs.kde.org/show_bug.cgi?id=418184) Changing db backends did not help, recreating accounts, too. Has anyone similar problems? Am I missing something completely? (Or has KDE PIM reached it's end of useability? ;-) ) Kindest regards, Dietz signature.asc Description: This is a digitally signed message part.
Re: Massive problems with kmail/akonadi
Am Montag, 23. März 2020, 08:59:22 CET schrieb Martin Steigerwald: > Dietz Proepper - 23.03.20, 08:40:06 CET: > > since some time, I encounter massive problems with kmail: > > - akonadi crashes every couple of hours. > > - moving mail between folders is b0rken badly > > > > (see https://bugs.kde.org/show_bug.cgi?id=418184) > > > > Changing db backends did not help, recreating accounts, too. > > > > Has anyone similar problems? Am I missing something completely? > > (Or has KDE PIM reached it's end of useability? ;-) ) > > No such problems with KMail/KDEPIM/Akonadi from Debian Sid currently > (19.08). Ack. I forgot to mention, version is from sid. Ah, the problems in the kde bug mainly happen with encrypted mails. oO(Did I mention this?) > But also had no such problems with KMail/KDEPIM/Akonadi from Debian 10 > as it was in Sid before. > > I did have some Akonadi crashes which may have been related to incorrect > AppArmor rules. Meanwhile I disabled AppArmor for akonadi-server since I > still saw frequent AppArmor access denial messages in log. I believe > there is Debian a bug report about it. Ack. Will take a look. > You may also consider to ask on kdepim-users KDE mailinglist for help. Good idea, thx. Kindest Regards, Dietz signature.asc Description: This is a digitally signed message part.
Re: Massive problems with kmail/akonadi
Am Montag, 23. März 2020, 22:20:37 CET schrieb Allan Sandfeld Jensen: > On Monday, 23 March 2020 08:40:06 CET Dietz Proepper wrote: > > Hi, > > > > since some time, I encounter massive problems with kmail: > > - akonadi crashes every couple of hours. > > - moving mail between folders is b0rken badly > > > > (see https://bugs.kde.org/show_bug.cgi?id=418184) > > > > Changing db backends did not help, recreating accounts, too. > > > > Has anyone similar problems? Am I missing something completely? > > (Or has KDE PIM reached it's end of useability? ;-) ) > > I haven't seen the crashes in a while, but two years ago it was hit and > miss, and sometimes you need to skip certain versions that were crashy.. I > only see crashes when the networks disappears or when logging off, and I do > that rarely, but I guess if you logout a lot track crashed on exit it can > look rather bad still. Yes, it's a laptop and gets suspended and moved between networks quite often. The frequent crash stuff started around Jan and got worse lately. > Moving emails between folders mostly just duplicates emails or keep marking > read emails unread and stupid stuff like that. At least it never corrupts > anything. Funnily it only seems to happen with pgp encrypted mails involved. More exactly, if I move messages one-by-one, everything is fine. If I move a bunch of messages, with at least one encrypted mail beyond them, things start getting funny. And if I move to a temp folder first and from there to the real target, the 2nd move seems to "heal" the mixups. Weird issue. Alas, perhaps I should extend my bug report and move to kdepim-users soon with that stuff ... Kindest regards, Dietz signature.asc Description: This is a digitally signed message part.
Headset and audio profiles
Good morning, I think, that this is more of a pulseaudio problem, but perhaps someone has got an idea. I have a bluetooth headset, supporting High Fidelity Playback (A2DP profile) and Headset Head Unit (HSP/HFP profile). Now, every time I connect it, the A2DP profile gets chosen, which does not support the headset's microphone. I can easily switch to HSP/HFP by means of the sound control applet, but is there a way to set HSP/HFP as a default? (I already spent an afternoon on that, but all recipes I found did not work.) Kindest regards, Dietz signature.asc Description: This is a digitally signed message part.
Re: Headset and audio profiles
Good morning, HSP/HFP works very well here. I just have to switch from A2DP manually. The behaviour changed somewhen late summer last year. Kindest regards, Dietz Am Mittwoch, 25. März 2020, 13:39:26 CET schrieb Raúl Sánchez Siles: > Hi: > > Not really answering the OP, but last time I looked into this latest bluez > didn't support HSP/HFP properly. bluez did on v4, but not on v5. I'll be > gladly surprised if HFP works now. signature.asc Description: This is a digitally signed message part.
Re: Massive problems with kmail/akonadi
Am Montag, 23. März 2020, 08:59:22 CET schrieb Martin Steigerwald: > Dietz Proepper - 23.03.20, 08:40:06 CET: [kmail problems] > > No such problems with KMail/KDEPIM/Akonadi from Debian Sid currently > (19.08). > > But also had no such problems with KMail/KDEPIM/Akonadi from Debian 10 > as it was in Sid before. > > I did have some Akonadi crashes which may have been related to incorrect > AppArmor rules. Meanwhile I disabled AppArmor for akonadi-server since I > still saw frequent AppArmor access denial messages in log. I believe > there is Debian a bug report about it. Crazy shit - on 24.3. I disabled AppArmor for akonadi. Since then: *no* crashing akonadi (which makes sense to me "somehow"). But my "move email" issues seem to be gone, too! (I did not test in depth, but had no issues the last days.) I'll observe that some more time (and hopefully can do some real tests on it), but has anyone of the wizards here even a remote glimpse, how AppArmor could trigger this kind of error?! Or is it some kind of Schroedinger Error (you look at it in depth and it goes away)? ;-) dazed & confused Dietz signature.asc Description: This is a digitally signed message part.
Re: Status of Plasma 5.18/5.19?
Hi Norbert, and I have to confess - looks like a really, really decent piece of work you did. Quite a pity, that there seem to be differences on using what you have been producing. Would you mind announcing relevant changes from your side (changed repos, discontinued development and so on) also oh debian-kde? Kindest regards, Dietz Am Sonntag, 28. Juni 2020, 10:14:21 CEST schrieb Norbert Preining: > Hi Jeremy, > > It is now 5.19.2 (and frameworks 5.71), see here > https://www.preining.info/blog/2020/06/kde-plasma-5-19-2-for-debian/ > thanks to the upload of Qt 5.14 to unstable. > > Feel free to try it out but report bugs to me and **not** the Debian BTS. > > And don't break Debian :-D > > Best > > Norbert signature.asc Description: This is a digitally signed message part.
Re: Digikam and 4:21
Am Freitag, 27. August 2021, 17:13:26 CEST schrieb Martin Steigerwald: > MERLIN Philippe - 27.08.21, 16:36:01 CEST: > > the update from Kde 4:20 to 4:21 removes the digikam > > software, > > in my case blocks the installation of this new version. > > My question is the following: is there a foreseeable date > > of an update of digikam compatible with the 4:21? > > Norbert requested a binNMU, i.e. a rebuilt, see bug #992948. > > Once the release team gets to it and the builds are through it should be > installable again. > > Just wait a bit more. Simply rebuilding digikam against 21.08.0 on their own for those who can not wait is more a time consuming than a difficult task ;-). signature.asc Description: This is a digitally signed message part.
Re: Digikam and 4:21
Am Freitag, 27. August 2021, 17:13:26 CEST schrieb Martin Steigerwald: > MERLIN Philippe - 27.08.21, 16:36:01 CEST: > > the update from Kde 4:20 to 4:21 removes the digikam > > software, > > in my case blocks the installation of this new version. > > My question is the following: is there a foreseeable date > > of an update of digikam compatible with the 4:21? > > Norbert requested a binNMU, i.e. a rebuilt, see bug #992948. > > Once the release team gets to it and the builds are through it should be > installable again. > > Just wait a bit more. Simply rebuilding digikam against 21.08.0 on their own for those who can not wait is more a time consuming than a difficult task ;-). signature.asc Description: This is a digitally signed message part.
Re: KDEPIM 21.08: blank settings window in KMail
Am Mittwoch, 25. August 2021, 09:50:16 CEST schrieb Martin Steigerwald: > Hi. > > KDEPIM upgrade to 21.08 in Debian Unstable should be possible, unless > you rely on Digikam. digikam-private-libs still needs a rebuilt. > > Did anyone update? Do you also see a blank settings window in KMail? As a quick workaround, if I use kmail from within Kontact, I can access all kmail settings via the Kontact setup dialog. signature.asc Description: This is a digitally signed message part.
Re: KDEPIM 21.08: blank settings window in KMail
Am Samstag, 28. August 2021, 16:36:52 CEST schrieb Martin Steigerwald: > Dietz Proepper - 28.08.21, 14:31:45 CEST: > > Am Mittwoch, 25. August 2021, 09:50:16 CEST schrieb Martin > > Steigerwald: > > > Hi. > > > > > > KDEPIM upgrade to 21.08 in Debian Unstable should be possible, > > > unless > > > you rely on Digikam. digikam-private-libs still needs a rebuilt. > > > > > > Did anyone update? Do you also see a blank settings window in KMail? > > > > As a quick workaround, if I use kmail from within Kontact, I can > > access all kmail settings via the Kontact setup dialog. > > Thanks, that is a really nice work-around. I did not think of trying > this! I found it out by accident ;-). signature.asc Description: This is a digitally signed message part.
Re: Digikam and 4:21
Am Freitag, 27. August 2021, 16:36:01 CEST schrieb MERLIN Philippe: > Hello, > the update from Kde 4:20 to 4:21 removes the digikam > software, > in my case blocks the installation of this new version. > My question is the following: is there a foreseeable date > of an update of digikam compatible with the 4:21? > Philippe Merlin FYI: New digikam packages just showed up some hours ago. signature.asc Description: This is a digitally signed message part.
Re: Future of "his" packages in Debian
Am Donnerstag, 20. Januar 2022, 19:17:23 CET schrieb Marco Valli:
> > by Norbert Preining · 2022/01/14
> >
> > After having been (again) demoted (blah)
> > based on flimsy arguments, I have been forced to rethink the level
> > of contribution I want to do for Debian. Blah blah blah blah
> > After about 20 years in Debian, blah blah blah
> > blah
> > KDE/Plasma, frameworks, Gears, and related packages:
>
> Admittedly, this guy doesn't have much faith in the the Debian/Kde team. 😆
> Regards
The way you are citing Norbert's blog post[1] ('"his" packages', "blah blah",
references to the source) sounds a little funny. And I'd expect such more from
a 10 year old that from an adult person.
Even more, given the fact that Norbert was the guy who seemingly was the main
driving force for converting debian-kde from an unstable, outdated mess to
something which is a pleasure to use around two years ago, I am even more
surprised.
My impression is, that some people with very, very tiny and limited minds
drive off those who do not lament on every bullshit and just get stuff done.
This is a rather sad developement for Debian.
I have been using Debian since 1998, but start wondering whether it really
makes sense to support a band of politicans much further.
Kindest regards,
Dietz
[1] https://www.preining.info/blog/2022/01/future-of-my-packages-in-debian/
signature.asc
Description: This is a digitally signed message part.
Re: Future of "his" packages in Debian
Am Freitag, 21. Januar 2022, 01:11:44 CET schrieb Johannes Zarl-Zierl: > > I never had any issues with Norbert. > > Full ACK. +1. And also not with Marco, as far as I remember. Which comes with little relevance, as we did not have much contact before. > Let's always keep discussions civil and in good faith... Well, but jftr, let's not forget who started this thread and in which way. At the very least, citing the source of ones comments is quite basic IMNSHO. Kindest regards, Dietz signature.asc Description: This is a digitally signed message part.
Re: Future of KDE packages in Debian
You: > It is sad to see what is happening from within Debian to Debian, but I > see myself not in a position to do much about it. I second that. Kindest regards, Dietz signature.asc Description: This is a digitally signed message part.
Re: No battery in tray, battery widget says "no batteries"
Good morning, Am Freitag, 4. Februar 2022, 19:40:14 CET schrieb Marc Haber: > Hi, > > on my notebook, a Thinkpad X260 running Debian unstable, the battery > widget has vanished from the tray. The "Battery and Brightness" widget > added to the panel shows a battery with a red cross, hovering gives the > message "No Batteries available". > > tlp-stat --battery sees both batteries just fine. > > Is this a bug in current KDE, or am I probably missing some packages to > find out? Where does the battery try icon look for battery states? What does "upower -d" say? Iirc, powerdevil queries upower(d) by means of some dbus magic to obtain the battery stats. Regards, Dietz signature.asc Description: This is a digitally signed message part.
Re: No battery in tray, battery widget says "no batteries"
Am Montag, 7. Februar 2022, 19:57:19 CET schrieb Marc Haber: > On Mon, Feb 07, 2022 at 11:25:35AM +0100, Dietz Proepper wrote: > > What does "upower -d" say? Iirc, powerdevil queries upower(d) by means of > > some dbus magic to obtain the battery stats. > > That looks good: > s[1/5041]mh@drop:~ $ upower -d > Device: /org/freedesktop/UPower/devices/line_power_AC [...] Sorry, then I don't know any further. Regards, Dietz signature.asc Description: This is a digitally signed message part.
Korgac vanished
Hi, as of 22.04, kdepim seems no longer to contain korgac (event reminder), see https://kde.org/announcements/changelogs/gear/22.04.1/ and the unstable packages contain no korgac anymore. But the replacement (kalendaracrc) seems not to be packaged currently. Are there plans for doing so? Kindest regards, Dietz signature.asc Description: This is a digitally signed message part.
Re: Korgac vanished
Am Donnerstag, 30. Juni 2022, 10:03:26 CEST schrieb Matthieu Gallien: > Hello, > > On jeudi 30 juin 2022 09:33:44 CEST Dietz Proepper wrote: > > Hi, > > > > as of 22.04, kdepim seems no longer to contain korgac (event reminder), > > see > > https://kde.org/announcements/changelogs/gear/22.04.1/ and the unstable > > packages contain no korgac anymore. > > > > But the replacement (kalendaracrc) seems not to be packaged currently. Are > > there plans for doing so? > > It is already packaged and in package libkf5akonadicalendar-bin. Ah, thx alot. Of course, searching for kalendarac*rc* yielded no result. Kindest regards, Dietz signature.asc Description: This is a digitally signed message part.
digikam
Hi, since the update to the kde version from unstable some days ago digikam is no longer installable. Are there plans underway to fix that? (Simply rebuilding from source failed due to some compilation error.) Kindest regards, Dietz signature.asc Description: This is a digitally signed message part.
Re: Any chance of getting the fix for autocompletion or kmail addresses failure into Debian?
Am Donnerstag, 25. August 2022, 01:09:48 CEST schrieb Patrick Franz: > Hej David, > > Am Montag, 22. August 2022, 15:11:22 CEST schrieb David Goodenough: > > https://bugs.kde.org/show_bug.cgi?id=458042[1] > > > > It would appear that there is a fix, and this is a regression > > from the previous release. It would be nice not to have to > > wait for the next full release. > > I have started packaging KDE PIM 22.08 and hope to finish it in a couple > of days. Just have a little patience. Seems that they are reachin' unstable right now. Thx alot for the good work, man! Kindest regards, Dietz signature.asc Description: This is a digitally signed message part.
Re: Many thanks for KDEPIM 22.08!
Am Samstag, 10. September 2022, 21:24:00 CEST schrieb Martin Steigerwald: > Hi! > > Many thanks for KDEPIM 22.08 packages. > > Still need to wait a bit here with dist-upgrade, but I bet it will be > soon enough! Just updated, seems to work like a charm :-). Kindest regards, Dietz signature.asc Description: This is a digitally signed message part.
Global search in kmail b0rken?
Hi, it seems, that the global search in kmail (Extras/Search message) from unstable is broken atm (at least for me). If I try to search for something, no results are returned. Even a regexp search with ".*" for "all messages" and "all folders" does not yield any results. Does anyone also observe this? Kindest regards, Dietz signature.asc Description: This is a digitally signed message part.
Re: Global search in kmail b0rken?
Am Freitag, 7. Oktober 2022, 11:55:29 CET schrieb Dietz Proepper: > Hi, > > it seems, that the global search in kmail (Extras/Search message) from > unstable is broken atm (at least for me). And with that shiny new kdepim 22.08.2 everything works again :-) Thx alot! Dietz signature.asc Description: This is a digitally signed message part.
Re: Plasma with Wayland: No ssh-agent started automatically?
Am Dienstag, 14. Februar 2023, 23:07:52 CET schrieb Martin Steigerwald: > Martin Steigerwald - 14.02.23, 22:27:16 CET: > > Do I really need to start ssh-agent by hand with Plasma (Wayland) > > session type? > > Never mind. I tried some weeks back and it seemed that there *was* a ssh-agent running, but some processes had SSH_AGENT.* set and some not. For reasons I did not investigate further, it seemed to depend on how child processes were spawned. > That is not the only issue. Kick off menu with scaling 150% spanning the > whole 1920x1080 laptop screen and artifacts while typing in Konsole are > other issues with Wayland. Multi screen setups, esp. with different scaling factors seem to have issues, too. And any scaling factor different from 100% led to blurring, even in text. > That still does not appear to be ready for me. > > Maybe some day. I have a recurring event "Test Wayland & KDE" every December ;-). Regards, Dietz signature.asc Description: This is a digitally signed message part.
Re: network managed applet not seeing connections after suspend
Am Montag, 14. August 2023, 13:46:52 CEST schrieb Marc Haber: > I am running KDE on an X260. Since the latest updates, after suspending > the machine, network-manager doesn't connect the network again and the > taskbar applet says "no connections found". Logging out of the Plasma > session and logging in again fixes the issue until next suspend. > > Is anybody else seeing this behavior and has already debugged? No, but the audio applet exposes funny behaviour here, too (audio sinks are displayed multiple times after resume or if I reconnect the dock, at least sometimes). Restarting plasmashell only (killall plasmashell; plasmashell&) fixes at least that issue until next suspend/resume cycle (for me). Regards, Dietz signature.asc Description: This is a digitally signed message part.
Re: network managed applet not seeing connections after suspend
Am Sonntag, 20. August 2023, 10:44:19 CEST schrieb Marc Haber: > On Sat, Aug 19, 2023 at 04:01:15PM +0200, Dietz Proepper wrote: > > No, but the audio applet exposes funny behaviour here, too (audio sinks > > are > > displayed multiple times after resume or if I reconnect the dock, at least > > sometimes). > > > > Restarting plasmashell only (killall plasmashell; plasmashell&) fixes at > > least that issue until next suspend/resume cycle (for me). > > Restarting plasmashell doesn't help here. Ok, then that smells not like a kde problem to me. > The nm applet seems to > reconnect and shows the available connections, but clicking on one > immediately yields a toast "Connection (name) deactivated" without even > trying to conect. I didn't know that behavior before. Anything interesting in /var/log/syslog? The other thing I'd try first is to play a little with nmctl so you can narrow down who might be the culprit. What kind of network btw? WLAN? Mobile? Regards, Dietz signature.asc Description: This is a digitally signed message part.
Re: network managed applet not seeing connections after suspend
Am Montag, 21. August 2023, 19:16:36 CEST schrieb Marc Haber: > On Sun, Aug 20, 2023 at 11:58:48AM +0200, Dietz Proepper wrote: > > Am Sonntag, 20. August 2023, 10:44:19 CEST schrieb Marc Haber: > > > Restarting plasmashell doesn't help here. > > > > Ok, then that smells not like a kde problem to me. > > It does to me. At least on a WPA Perosnalnetwork, I can connect using > nmtui alright. This smells to me like the nm applet not talking > properly to NetworkManager (which got updated on 09 Aug 2023, current > version being 1.44.0-1). Will try a downgrade tomorrow. Ack. [Logfile] > > Note the "Activation: (wifi) access point 'Zugschlus_Netgear' has > security, but secrets are required." and "no secrets: No agents were > available for this request." In my understanding, the agent in question > would be a KDE component since the secret was entered in the nm applet. That makes sense. > Now, where does nm applet store the secrets? KDEWallet iirc. signature.asc Description: This is a digitally signed message part.
Re: Upgrade to KDE 3.2: X resolution, Kwifimanager,
David Bishop: > On Tuesday 24 February 2004 12:04 pm, Joan Roig Amorós wrote: > > - I can not find Kwifimanager anywhere (and I swear, I installed it! > > ;-). > > An apt-cache search for kwifi brings back nothing. Where did you get This is strange. I can see kwifimanager, but it's broken, anyway. The reason seems to be that first kwifimanager depends on some old libiw, which means it won't compile withot modification. The second reason semms to be that kdenetwork-3.2.0/debian/kwifimanager.install contains only the documentation... Dietz
Re: Upgrade to KDE 3.2: X resolution, Kwifimanager,
Chris Cheney: > On Tue, Feb 24, 2004 at 10:03:01PM +0100, Dietz Proepper wrote: > > This is strange. I can see kwifimanager, but it's broken, anyway. The > > reason seems to be that first kwifimanager depends on some old libiw, > > which means it won't compile withot modification. The second reason > > semms to be that kdenetwork-3.2.0/debian/kwifimanager.install contains > > only the documentation... > > Yes, kwifimanager in 3.2 and BRANCH was broken the last time I compiled > the debs. It does use the current libiw api. I went ahead and included Hmm, is 26 current or 27? > the deb anyway since it needed an override that usually takes an extra > week. Hopefully kwifimanager will be fixed in time for the 3.2.1 > release. Bringing it to compile againt the current libiw in unstable requires a minimal fix. If you're interested, I can make a patch from my changes (plz. include your preferred patch format;). Dietz
Re: half duplex
larinia: > I saw the half duplex message in the /var/log/syslog. I am not sure if > the cat-5 cable is the network cable(Sorry, I am a newbie), if it is, It is. > then it is connecting to a hub, which is then connect to a wireless > bridge. That's the point. A hub can only give you a half duplex connection as opposed to a switch. For an explanation see [1]. But it should not matter in your setup cause the wireless bridge will be the bottleneck anyway. [1] i.e. http://www.duxcw.com/faq/network/hubsw.htm -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: half duplex
larinia: > ehm, thank you all very much, I will try to connect my laptop directly > with the modem and see if there is any difference. You need another cable (or a rather intelligent nic or modem;) for this. > Does half duplex make the network traffic slower? It does. But as I already said, this should not matter in your situation, because that bridge (or modem or whatever) will be the bottleneck. Therefore, simply leave it as it is. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: half duplex
You: > On Fri, Jul 29, 2005 at 10:13:41PM +0100, Lei Yu wrote: > > I think the hub does support full duplex. It is netgear dual speed hub > > model DS104. > > The hub is telling your eth0 that it doesn't - only half duplex (HD), > at 100 Mbits or 10 Mbits. To find out if it actually does FD, you can > try forcing full duplex temporarily with "mii-tool -F 100baseTx-FD > eth0". Watch the output from "ifconfig eth0" to see if the Errors or > Collisions start going wild, which will indicate that the hub doesn't do > full duplex. Sorry to say this again - if it's a HUB it will never - never - never support FD. Hubs generally only support HD links due to their design. Switchs can and normally do support FD. But this does not matter normally, the slowdown is acceptable, at least for SOHO and smaller kinds of setups. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
kwallet, konqueror and password
Hi, I have a little question regarding kwallet and konqueror. If I enter passwords in konqueror, it asks me, wether I'd like to store them via kwallet. Now, I request, not to store passwords for a website. Now, how can I revert that decision? Or, more exactly, where does konqueror store that information (not the encrypted password/username!) thx alot, Dietz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kwallet, konqueror and password
I wrote: > Hi, > > I have a little question regarding kwallet and konqueror. > > If I enter passwords in konqueror, it asks me, wether I'd like to store > them via kwallet. Now, I request, not to store passwords for a website. > > Now, how can I revert that decision? Or, more exactly, where does > konqueror store that information (not the encrypted password/username!) Found it on my own ;-). It's in .kde/share/apps/khtml/formcompletions just if someone were curious... Dietz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Dead keys not working in KDE
Michael Schuerig: > I'm trying to get dead keys to work in KDE (all the latest unstable > packages, incl. xserver-xorg), but don't have any success. When I type > followed by 'e', the first key stroke inserts nothing, the > second inserts a plain 'e'. '`', '^', '~' are inserted immediately. Might be #362112... Did you install xkb-data? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: problems printing with cups 1.2
Hi, Ross Boylan: > I can't get printing working from KDE since upgrading to cups 1.2. If you can reproduce the problem with lp too and get a "Bad Request" error message then take a look at bug #374009. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [OT]Re: Multi-tasking
Raúl Sánchez Siles: > Here is something I have always liked to asks but I hadn't had the > chance. The problem is that on my job PC, I use reiser over a LVM over a > SATA disk. When I have some disk intensive tasks/intervals, my system > turns not as responsive as I wish and as I think should be. One part of the problem is crappy PC hardware :-\. Most certainly, the SATA tranfers block the PCI bus and use up parts of your memory bandwidth while transfering data, which is a bad thing. The other part (even with non-crap) - you're putting heavy load on your disk subsystem from one process. Now, if another process tries to do disk i/o, the heavy load from the other process slows it down. > In this situation, I have tried doing top on a konsole, and I find > that the field "wa" in the above part of the top report, in the middle > of "id" and "hi" raises to 80-90%. I don't know what exactly this field > means, but I bet for cpu-wait state as it is the case in disk I/O. It's the amount of time, your systems spends waiting for i/o requests to finish, and its quite normal to have 90%+ i/o wait while you're doing disk i/o. In an ideal world, the disk operation should not influence the rest of the system too much (apart from slowing down other disk i/o.) > All of this guessing yields me to the conclusion that I'm sometimes > wasting up to 90% of cpu time waiting or just doing nothing, I can't If you're not typing very, very fast (or run some seti stuff in the background all the time), your system spends nearly 100% of it's time doing nothing ;-).
Re: problems starting kde
I assume you're using unstable... George Adamides: > Hello > I am following the instructions from a paper to install and start KDE. I > managed to install it and now I am trying to make it work...When I type > startkde I get the following message > > :~# startkde > > xsetroot: unable to open display '' > xset: unable to open display "" > xsetroot: unable to open display '' > DCOPServer : slotShutdown() -> waiting for clients to disconnect. > DCOPServer : slotExit() -> exit. > startkde: Starting up... > startkde: Running kpersonalizer... > DCOP: register 'anonymous-19155' -> number of clients is now 1 > DCOP: unregister 'anonymous-19155' > kwin: cannot connect to X server > kpersonalizer: cannot connect to X server > kpersonalizer: cannot connect to X server Calling startkde in that way will fail. Normally, startx will call it for you. > So then it says somewhere that if I get the above message I should type startx and run startkde from .xinitrc, .xsession or .Xclients. First of all I cannot find any of those files. Why is that? You don't need them ;-). Normally. > And whats more when I run startx I get the following: > :~# startx > > Using authority file /root/.Xauthority > Writing authority file /root/.Xauthority > Using authority file /root/.Xauthority > Writing authority file /root/.Xauthority > /usr/X11R6/lib/X11/xinit/xserverrc: line 2: /usr/bin/X11/X: No such file > or directory /usr/X11R6/lib/X11/xinit/xserverrc: line 2: exec: > /usr/bin/X11/X: cannot execute: No such file or directory giving up. > xinit: No such file or directory (errno 2): unable to connect to X > server xinit: No such process (errno 3): Server error. > > > Can someone please explain to me what am I doing wrong and how to fix > this problem? That looks like your X11 installation is flawed. Have you installed xserver-org (that's the package that hould pull all the stuff necessary for X11)? Dietz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Shortcuts in kmail
Hi, I'm trying to set some shortcuts for kmail. I can set them up, and they work. Now the problem: If I restart kmail, they're gone. Any idea? regards, Dietz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kmail won't work with satellite provider....
Charlie: > Have just subscribed to this list and using Icedove to post. > Using Debian Etch/Lenny > Have just been connected to satellite internet provider Clearnet who > have some Linux capable techs on their staff, but have not been able to > resolve a problem with Kmail 1.9.5 [using KDE 3.5.7] in Debian testing. These techs should train themselves regarding smtp ;-). > If I attempt to send an email to myself, the test of the satellite > provider [smtp], or anyone else using Kmail 1.9.5 [using KDE 3.5.7], > with the new email address after setting the accounts up, I get an error > message:- > > Sending failed: > Message sending failed since the following recipients were rejected by > the server: > [EMAIL PROTECTED] (The server responded: "relaying mail to > clearmail.com.au is not allowed") This indicates that you could connect to the mail server but he rejected your mail for some reason. Therefore you should check this out with your email provider. > I have no problem sending through the old dialup provider and have used > Kmail for years. This is a new twist. I'd assume that your satellite provider is blacklisted somewhere. Dietz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kmail won't work with satellite provider....
Charlie: > Dietz Proepper wrote: > > Charlie: > >> Have just subscribed to this list and using Icedove to post. > >> Using Debian Etch/Lenny > >> Have just been connected to satellite internet provider Clearnet who > >> have some Linux capable techs on their staff, but have not been able > >> to resolve a problem with Kmail 1.9.5 [using KDE 3.5.7] in Debian > >> testing. > > > > These techs should train themselves regarding smtp ;-). > > Interesting, they sent me a message through kmail from their end, and I > received it, but couldn't reply to it. Sending and receiving email can be two completely different beasts. BTW, how (by which protocols) do you receive and send your mail? > >> Sending failed: > >> Message sending failed since the following recipients were rejected > >> by the server: > >> [EMAIL PROTECTED] (The server responded: "relaying mail to > >> clearmail.com.au is not allowed") > > > > This indicates that you could connect to the mail server but he > > rejected your mail for some reason. Therefore you should check this > > out with your email provider. > > The provider couldn't discover why this should happen from my end. They The email provider (as opposed to the access (satellite) provider)? They should at least see something in their log files. > > I'd assume that your satellite provider is blacklisted somewhere. > > > > Dietz > > Interesting as well? Icedove isn't blacklisted through that provider? > Kmail is? > > You may well be right, but why kmail and not Icedove? Eh, you mean, icedove works and kmail fails? I must have overead that in your first mail. If they are configured the same way, this might indicate some glitch on kmail's side. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kdesendfax
Rainer Dorsch: > Hello, > > I found in the KDE Control Center in the debian KDE packages a reference > to ksendfax (as one installed printer). I did not find a Debian package > for ksendfax, only sources. I am wondering, if ksendfax is superseded by > another package, since > - the last maintainance release was in 2002 > - Debian does not package it The fax sender application is kdeprintfax, which can be found in the kdeprint package. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
