Kmail crash: "Could not create collection outbox, resourceId 15"
Hi, I just got a kmail crash out of the blue with a message "Could not create collection outbox, resourceId 15" I updated a few weeks back to Debian 12, but apart from that I am not aware of any updates. I tried to run akonadictl fsck and got a similar result [...] org.kde.pim.akonadiserver: Error during insertion into table "CollectionTable" "Duplicate entry '8-outbox' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Der Befehl konnte nicht ausgeführt werden" org.kde.pim.akonadiserver: Failed to append Collection "outbox" in resource "akonadi_maildir_resource_0" org.kde.pim.akonadicore: Failed SpecialCollectionsRequestJob::slotResult "Could not create collection outbox, resourceId 15" org.kde.pim.akonadiserver: Error while handling command CreateCollection on connection akonadi_maildispatcher_agent (0x555c6ad0ccc0) org.kde.pim.maildispatcher: Failed to get outbox folder. Giving up. org.kde.pim.akonadicore: Failed CollectionCreateJob. "Could not create collection outbox, resourceId 15" I am wondering if https://userbase.kde.org/KMail/ FAQs_Hints_and_Tips#Clean_start_after_a_failed_migration is still the correct way to fix this. Unfortunately, this implies to configure all the accounts, identities, folders etc. again. I am wondering why resetting the cached imap etc. data requires to reset all user configuration data as well. Many thanks Rainer signature.asc Description: This is a digitally signed message part.
Re: Postpone update
Am Donnerstag, 13. April 2023, 08:24:15 CEST schrieb Rainer Dorsch: > Am Mittwoch, 12. April 2023, 22:26:14 CEST schrieb Johannes Zarl-Zierl: > > Am Mittwoch, 12. April 2023, 13:18:46 CEST schrieb Martin Steigerwald: > > > 2) Krunner segfaults, thus neither Alt-Space and in case still configure > > > Alt-F2 will work. > > > > > > There may be other issues. > > > > For the record: nheko is also segfaulting... > > > > Cheers, > > > > Johannes > > digikam segfaults after the upgrade from bullseye to bookworm. I opened a > bug report > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034310 > > Since it is not proven for me that it is the same issue and it helps to warn > others who are using apt-listbugs. After reading more details on debian-qt-kde IRC I understand that the qtbase5 issue only affects sid, 5.15.8+dfsg-3 in bookworm is not affected. That means the digikam issue is unrelated. Rainer -- Rainer Dorsch http://bokomoko.de/
Re: Postpone update
Am Mittwoch, 12. April 2023, 22:26:14 CEST schrieb Johannes Zarl-Zierl: > Am Mittwoch, 12. April 2023, 13:18:46 CEST schrieb Martin Steigerwald: > > 2) Krunner segfaults, thus neither Alt-Space and in case still configure > > Alt-F2 will work. > > > > There may be other issues. > > For the record: nheko is also segfaulting... > > Cheers, > Johannes digikam segfaults after the upgrade from bullseye to bookworm. I opened a bug report https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034310 Since it is not proven for me that it is the same issue and it helps to warn others who are using apt-listbugs. Thanks Rainer -- Rainer Dorsch http://bokomoko.de/
Re: Cut and Paste looses formatting when copying from one table to another table
Hi Rene, many thanks for the super fast reply. Am Sonntag, 26. Februar 2023, 13:30:05 CET schrieb Rene Engelhard: > Hi, > > Am 26.02.23 um 12:02 schrieb Rainer Dorsch: > > The issue does not occur on a Manjaro Stable system with Libreoffice 7.5.0 > > Maybe fixed in 7.5.0? I did some more testing. I think it is a KDE Plasma related issue (therefore copying debian-kde): -> If I disable in the clipboard settings: Sync content of clipboard and current selection (translation of "Inhalt von Zwischenablage und aktueller Auswahl angleichen"), I don't get the empty selection anymore, when switching to a new librecalc tab and pasting (a copy from previously selected content on another librecalc tab) works without loosing any formatting. -> If I deliberately copy something else in between and revert back to the previous selection in the clipboard history, I have the issue again. => Seems to be a bug in the plasma clipboard history of Debian bullseye. It seems formatting gets lost in the history. Probably not worth debugging for bullseye anymore, since bookworm gets released soon. I hope the bug is fixed in Plasma in bookworm though. > > The systems don't share the home directory though. Is the are a way to > > make > > libreoffice ignoring all user settings? > > You can start with safe mode.. Thanks, tried this first, but does not change anything. > > Any hint what could be wrong is welcome. > > See above, it can just be a upstream bug. You can try with > bookworm/sid+experimental in a VM? Or wait until there will be 7.5.x in > bookworm-backports (yes, explicitely NOT bullseye-backports). > > > Too bad there was never really a chance to get 7.5.x into bookworm > given the freeze schedule. > > /7.5.0 might have worked if one was really courageos but then we'd have > a serious problem on any bigger surprise. Usually .0s are not really > good anyway, .1 woul bd a given and that really misses the deadline > completely) I think that was an excellent choice for Debian stable. Manjaro stable ships updates for major packages (like KDE plasma, browsers, libreoffice, etc.) roughly every month, which are entirely different boundary conditions. Thanks Rainer > > Regards, > > > Rene -- Rainer Dorsch http://bokomoko.de/
Re: Locale Issue in bullseye
Hi Boris,
very useful reply, many thanks.
Am Sonntag, 3. Januar 2021, 22:52:20 CET schrieb Boris Pek:
> Hi,
>
> > I installed a new bullseye system. I added some accounts and changed the
> > locale (regional settings) to German. Worked well for
> >
> > - System settings
> > - Application starter menu
> > - Non-KDE Applications (e.g. firefox and libreoffice)
> >
> > Did not work for
> > - control panel
> > - all KDE Applications, e.g.
> > -- kate
> > -- kmail
> > -- konsole
> > -- ...
> >
> > Is this a bug or did I miss something?
> >
> > Any advice or hint is welcome.
>
> Please show output of commands:
>
> $ locale
> $ locale -a
antonia@aura:~$ locale
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
LANG=de_DE.UTF-8
LANGUAGE=de:en_US
LC_CTYPE="de_DE.UTF-8"
LC_NUMERIC="de_DE.UTF-8"
LC_TIME="de_DE.UTF-8"
LC_COLLATE="de_DE.UTF-8"
LC_MONETARY="de_DE.UTF-8"
LC_MESSAGES="de_DE.UTF-8"
LC_PAPER="de_DE.UTF-8"
LC_NAME="de_DE.UTF-8"
LC_ADDRESS="de_DE.UTF-8"
LC_TELEPHONE="de_DE.UTF-8"
LC_MEASUREMENT="de_DE.UTF-8"
LC_IDENTIFICATION="de_DE.UTF-8"
LC_ALL=
antonia@aura:~$ locale -a
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_COLLATE to default locale: No such file or directory
C
C.UTF-8
POSIX
en_US.utf8
antonia@aura:~$
I did run
root@aura:~# dpkg-reconfigure locales
Generating locales (this might take a while)...
de_DE.UTF-8... done
en_US.UTF-8... done
Generation complete.
*** update-locale: Warning: LANGUAGE ("en_US:en") is not compatible with LANG
(de_DE.UTF-8). Disabling it.
root@aura:~#
to add de_DE.utf8
root@aura:~# locale -a
C
C.UTF-8
de_DE.utf8
en_US.utf8
POSIX
root@aura:~#
> Have you tried to install special meta-packages task-german-desktop and
> task-german-kde-desktop?
No, but task-german-kde-desktop did not add anything anymore
root@aura:/etc# apt-get install task-german-kde-desktop
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
task-german-kde-desktop
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/884 B of archives.
After this operation, 6,144 B of additional disk space will be used.
Selecting previously unselected package task-german-kde-desktop.
(Reading database ... 175044 files and directories currently installed.)
Preparing to unpack .../task-german-kde-desktop_3.61_all.deb ...
Unpacking task-german-kde-desktop (3.61) ...
Setting up task-german-kde-desktop (3.61) ...
root@aura:/etc#
I think adding the locale de_DE.UTF-8 has fixed the issue. Is it expected that
KDE applications are more sensitive to this than other applications?
Does anybody know the definition of the LANGUAGE variable? Or what does
LANGUAGE=de:en_US
mean?
Thanks again
Rainer
--
Rainer Dorsch
http://bokomoko.de/
Locale Issue in bullseye
Hi, I installed a new bullseye system. I added some accounts and changed the locale (regional settings) to German. Worked well for - System settings - Application starter menu - Non-KDE Applications (e.g. firefox and libreoffice) Did not work for - control panel - all KDE Applications, e.g. -- kate -- kmail -- konsole -- ... Is this a bug or did I miss something? Any advice or hint is welcome. Thanks Rainer -- Rainer Dorsch http://bokomoko.de/
Re: KF5 5.75 timeline
Am Mittwoch, 28. Oktober 2020, 00:06:41 CET schrieb Borden Rhodes: > On Tue, 27 Oct 2020 at 15:30, Sandro Knauß wrote: > Thank you for your response > > > I don't understand what you try to do. > > This is what I'm trying to do: > https://invent.kde.org/frameworks/syntax-highlighting/-/issues/3 > Upstream says that I need 5.75, but perhaps the features are available > in the 5.74 just uploaded to testing? Hi Borden, you could also try Norbert's packages until 5.75 is in the Debian repo: https://www.preining.info/blog/2020/10/kde-plasma-status-update-2020-10-12/ He writes that KDE Frameworks 5.75 is included. Rainer -- Rainer Dorsch http://bokomoko.de/
Get rid of deleted data in akonadi cache
Hi, does anybody know if there is a way to get rid of deleted data in the akonadi cache on a buster system? I thought $ akonadictl vacuum $ akonadictl fsck does that, but it does not seem so. I see many outputs like Found unreferenced external file: /home/rd/.local/share/akonadi/file_db_data/ 13/470913_r0 but no space is freed on the filesystem and in a second run, the same outputs appear again. akonadictl fsck also prints Moved 6027 unreferenced files to lost+found. What that means is a complete miracle for me, I thought lost+found is for disk partitions, find also was not successful $ find ~/.local/share/akonadi -name lost+found $ Do I need to write a script which parses the output of fsck and delete the files with the script? Or does that not work either for some reason? Many thanks Rainer -- Rainer Dorsch http://bokomoko.de/
Re: window manager crash
Am Dienstag, 4. August 2020, 15:25:16 CEST schrieb Thom Castermans: > Hi Rainer, > > It sounds to me like it might be kwin that crashed, rather than > Plasma. You can restart that with `DISPLAY=:0 kwin --replace` from any > VTT. > > > I can start new apps using the (former) K-menu, > > If you mean the Application Launcher, then that means you can run > commands from there too. Either Luca's suggestions or `kwin --replace` > (does not need the DISPLAY) hopefully work for you. Many thanks. The situation re-occured and I DISPLAY=:1 kwin --replace worked (it was the second session not the first one). But then the next issue I hit was: "Could not start ksmserver. Check your installation." Any idea how to recover from this would be welcome. Thanks Rainer -- Rainer Dorsch http://bokomoko.de/
Re: Problem switching users from plasma under lightdm
Am Mittwoch, 12. August 2020, 22:31:13 CEST schrieb Shai Berger: > Hi, > > On Wed, 12 Aug 2020 13:47:16 -0300 > > Lisandro Damián Nicanor Pérez Meyer wrote: > > I am currently using > > > > qdbus --system org.freedesktop.DisplayManager > > /org/freedesktop/DisplayManager/Seat0 > > org.freedesktop.DisplayManager.Seat.SwitchToGreeter > > > > to open new users' sessions. > > I can confirm that this works. Hi Shai, if you are brave, another test could be upgrading to Norbert's newer packages https://www.preining.info/blog/2020/07/kde-plasma-status-update-2020-07-04/ This would show if it is an issue which is fixed in a newer plasma version and it could make it easier to motivate upstream to look into that. I would expect that at least by uninstalling the packages and reinstalling of the Debian repo would bring you back to the Debian packages, but I have not tried that. Rainer -- Rainer Dorsch http://bokomoko.de/
Re: window manager crash
Am Dienstag, 4. August 2020, 14:50:45 CEST schrieb Rainer Dorsch: > Am Dienstag, 4. August 2020, 10:30:19 CEST schrieb luca.pedrielli: > > alt+F2(krunner) is working? > > > > if yes maybe you can try with > > > > $ kquitapp5 plasmashell > > > > $ kstart5 plasmashell > > > > and restart plasma > > Thanks, Luca. But no, alt+F2 does not work :-/ > Any idea if I can get plasmashell started on a virtual (text) console? Connecting to the X server is probably the difficult part (?) Thanks Rainer -- Rainer Dorsch http://bokomoko.de/
Re: window manager crash
Am Dienstag, 4. August 2020, 10:30:19 CEST schrieb luca.pedrielli: > alt+F2(krunner) is working? > > if yes maybe you can try with > > $ kquitapp5 plasmashell > > $ kstart5 plasmashell > > and restart plasma Thanks, Luca. But no, alt+F2 does not work :-/ Rainer -- Rainer Dorsch http://bokomoko.de/
window manager crash
Hi, I have for one user on a Debian 10 system an issue which looks like a window manager crash. I.e. one application (e.g. kmail) is full screen w/o window decoration. I can start new apps using the (former) K-menu, they also start immediately fullscreen. It is particularly likely to happen after a switch user Can anybody advise on how to debug this? Or as a workaround to restart the window manager. It seems also the keyboard is dead e.g. no input possible into a console on that session (though swtiching to another VTT is still possible (Alt+Ctrl+Fx). If it is too hard to debug, is there a good way to reset all KDE configurations for a user? Is mv .kde .kde.old mv .local .local.old mv .config .config.old sufficient? Any ideas on less drastic measures are welcome :-) Thanks Rainer -- Rainer Dorsch http://bokomoko.de/
Re: Status of Plasma 5.18/5.19?
Hi Pino, thanks for sharing your concerns. But can you elaborate somewhat more on a few things? Am Dienstag, 7. Juli 2020, 16:57:23 CEST schrieb Pino Toscano: [...] > It is definitely not nice to see that all the work & efforts in many > years are happily thrown down the loo by Why do you think that something is thrown away by Norbert (or anybody else) providing recent Debian packages for KDE? > - publicity stunts What are you referring to? For me Norbert's blog entries read reasonably neutral (?) or are you referring to other blogs? > - binary-only repos because "one person [not anymore working in the > team] said something bad to me, so it's all team fault" Are you referring to Norbert's repos? Picking a random one https://download.opensuse.org/repositories/home:/npreining:/debian-kde:/ plasma519/Debian_Testing/ I find source packages in there. Not sure if apt-get can handle the directory structure though. > - blogs filled with untrue facts and on the borderline of insults Can you list the major facts which you consider untrue? > How does an "open mind" motivate you to work on this? I'll tell you: > it does not. > > Maybe a better solution would be to just give up with this -- after > all, users have the super-duper-and-excellent-quality repos, right? It seems you are insulted by Norbert (or anybody else) providing uptodate KDE releases and some users who have a need for new releases using them. For me it seems there are packages from the Debian KDE team which are high quality, but often somewhat outdated. Then there are Norbert's packages which are uptodate but likely(?) lower quality. It would be surprising if one person would be able to just provide better packages in all aspects. Unfortunately, at least so far, nobody had a solution which resulted in packages which were both high quality packages and contained very recent KDE releases. If that solution is found Norbert's packages are obsolete until then for me they seem to fill a gap. > Deepily unmotivated, Can you elaborate why you are demotivated by Norbert providing packages he compiled of latest KDE releases? How does it affect your packaging work? Thanks Rainer -- Rainer Dorsch http://bokomoko.de/
Re: Status of Plasma 5.18/5.19?
Am Sonntag, 5. Juli 2020, 15:48:55 CEST schrieb Norbert Preining: > Hi Dietz, > > > Would you mind announcing relevant changes from your side (changed repos, > > discontinued development and so on) also oh debian-kde? > > I don't think this is welcome here, since also on the IRC channel I was > told not to advertise my repositories. > Since this is already speculation, can anybody who has concerns with announcements or user reports of Norbert's super uptodate KDE packages for Debian here on the list share them? I hope with an open minded and solution oriented discussion they can be addressed and resolved.... Thanks Rainer -- Rainer Dorsch http://bokomoko.de/
Re: Status of Plasma 5.18/5.19?
Hi Jeremy, there is good news, Norbert's continues to provide KDE packages e.g. for 5.19.2 , see https://www.preining.info/blog/2020/06/kde-plasma-5-19-2-for-debian/ Be aware I have not used them, all my desktop systems are on stable and as I try to avoid to have third party repos as much as possible for reasons for trust and stability. I am not sure which topic of https://wiki.debian.org/DontBreakDebian Marco is referring to, I am sure he understands that Norbert's packages are built and meant for Debian sid/bullseye, so none of the criteria for FrankenDebian applies: > Repositories that can create a FrankenDebian if used with Debian Stable: > - Debian testing release (currently bullseye) > - Debian unstable release (also known as sid) > - Ubuntu, Mint or other derivative repositories are not compatible with Debian! > - Ubuntu PPAs Norbert is a very experienced DD. I would not be too worried of breaking Debian with Norbert's packages as long as you follow Norbert's blog https://www.preining.info/blog/ and remember you are on testing or unstable anyways, if you use his packages. I am glad that he closes the gap that there is usually a delay between KDE releases and official Debian packages for them. I consider his packages as value add, since I am sure there are Debian users which need a recent KDE release (and if it is just to do a quick test in a VM for bugs fixed, new features,) @Marco: Do you have any evidence that anybody broke his system, because he used Norbert's builds? Thanks Rainer Am Sonntag, 28. Juni 2020, 09:03:53 CEST schrieb Marco Valli: > In data domenica 28 giugno 2020 02:08:48 CEST, Jeremy Potter ha scritto: > > Norbert Preining (who is > > controversial for some reason?) had created a third-party repository with > > Plasma 5.18. > > https://www.preining.info/blog/2020/06/waste-of-resources-bye-bye-debian-kde > -team/ > > ps don't break Debian! > https://wiki.debian.org/DontBreakDebian > > regards -- Rainer Dorsch http://bokomoko.de/
KDE Apps 20.04 (and Plasma) for Debian
Hi, just wondering, if anybody tried Norbert's repo for sid and bullseye with - KDE frameworks, currently version 5.69 - Plasma packages, currently 5.18.4.1 - KDE Apps, currently 20.04 https://www.preining.info/blog/2020/04/kde-apps-20-04-for-debian/ I think, any feedback would be useful. Thanks Rainer -- Rainer Dorsch http://bokomoko.de/
Re: Screen energy saving turning on and off and (fixed)
gt; But I haven't found similar comments on the net. And it is not really > > hinting to any course of action. > > > > And again, I haven't been able to associate any traces of the > > malfunctioning with any logs: nothing specific seems to be recorded in > > the logs when the screen is flashing like a Christmas tree. > > > > I'm using rsyslogd and > > SYSTEMD_LESS=FRXMK journalctl -xa > > seems to show me everything there is. > > I haven't seen anything relevant in > > /var/log/Xorg.0.log > > > > Worth mentioning: I put the pc to sleep with: (the screen that is [*]) > > xset dpms 10 10 10; sleep 10; xset dpms force off > > Then "C-l" > > Then after entering my password: > > xset dpms 1800 2700 3600 > > > > But I don't thing it really influences the flashing effect; only the > > frequency of the flashing. > > > > Again, 9 times out of 10, it doesn't flash at all be behaves itself, like > > a > > good pc. > > > > [*] I cannot put the PC to sleep, nor suspend... I can, but it's > > complicated, and I don't think it works well. > > Because to restart the laptop, I'll have to make some event. But the lid > > is > > closed. So I'd have to manipulate the lid, but then kde will see that as a > > dual screen configuration, and it will freak out, and I will loose all my > > screen settings. > > > > When I restart the PC, I have to make a special dance: > > Open the lid; Press power button; > > Wait for grub screen... > > Then, at that moment, and that moment only, > > close the lid! > > Can you imagine the hassle. > > > > There must be much better solutions that I missed; only, I haven't found > > them yet. -- Rainer Dorsch http://bokomoko.de/
News from KDE PIM in September-October 2019
Hi, interesting read, seems some quite nice features are coming into KDEPIM, I am really looking forward to KDE Itinerary and DKIM support: https://ervin.ipsquad.net/blog/2019/11/05/news-from-kde-pim-in-september-october-2019/ Thanks Rainer -- Rainer Dorsch http://bokomoko.de/
Re: KDE Frameworks 5.61 coming
Hi Martin, your reporting to the list is useful for me, I like it. :-) Many thanks Rainer Am Dienstag, 10. September 2019, 10:44:03 CEST schrieb Martin Steigerwald: > Hi Sandro. > > Sandro Knauß - 10.09.19, 10:30:32 CEST: > > > As usual check apt dist-upgrade output carefully for any package > > > removals and wait till the upload is complete. > > > > Please read the update messages more carefully. Frameworks is uploaded > > to experimental, so nobody should install it by accident. And nobody > > should install new version from experimental by default, because > > experimental is often used, to coordinate new version, like handling > > stuff, that hits the NEW queue. > > I am sorry, in my excitement of something new coming, I missed that. > > Will read more carefully next time. > > And anyway: it is always good to watch out then doing apt dist-upgrade, > so my notices may be redundant. So may just skip notices like that > completely in the future. > > Best, -- Rainer Dorsch http://bokomoko.de/
Idle Detection
Hi, can anybody tell how Plasma determines that it is idle to put the system e.g. in suspend? I see sometimes the idle detection does not work anymore. A reboot fixes it.. One candidate is a stale vlc process, but it seems there are others. I am looking for a way which to find out what is the reason for the system to believe that it is not idle. Thanks Rainer -- Rainer Dorsch http://bokomoko.de/
Re: Akonadiserver use too much memory after upgrade to Buster
Hi Abba, I just checked here, I have around 30 MB usage per akonadiserver process. But I upgraded the system here quite some time back to buster. I remember that I also had some issues to get to a "stable state" again. Here are my notes I took back then...: akonadi: Manually start, stop, restart: -- https://userbase.kde.org/Akonadi/de#Wo_sind_meine_Daten_jetzt_abgelegt.3F akonadictl start akonadictl stop akonadictl restart Reducing size of .local/share/akonadi/file_db_data: --- https://bugs.kde.org/show_bug.cgi?id=282160 - comment 16: akonadictl vacuum akonadictl fsck Just make it clear: vacuum compresses the mysql database (not related to files_db_data). fsck find the files from that directory that are not referenced anymore from the database, and moves it to the ~/.local/share/akonadi/file_lost+found/ folder. From ~/.local/share/akonadi/file_lost+found the files need to be deleted manually. Clean akonadi configuration to fix KMail: - https://wiki.archlinux.org/index.php/ KDE#Clean_akonadi_configuration_to_fix_KMail First, make sure that KMail is not running. Then backup configuration: $ cp -a ~/.local/share/akonadi ~/.local/share/akonadi-old $ cp -a ~/.config/akonadi ~/.config/akonadi-old Start SystemSettings > Personal and remove all the resources. Go back to Dolphin and remove the original ~/.local/share/akonadi and ~/.config/akonadi - the copies you made ensure that you can back-track if necessary. Now go back to the System Settings page and carefully add the necessary resources. You should see the resource reading in your mail folders. Then start Kontact/KMail to see if it work properly. Resetting akonadi: -- https://docs.kde.org/stable/en/kdepim/kmail/clean-start-after-a-failed-migration.html Hope that helps Rainer Am Freitag, 19. Juli 2019, 11:29:41 CEST schrieb Abba Soungui YOUNOUSS: > Here is the screenshot taken this morning, we are already at 2G of memory > usage : https://cloud.soungui.cm/s/MSX2tMo7FrGAdPr > > -- > > Le jeudi 18 juillet 2019, 21:41:17 WAT Abba Soungui YOUNOUSS a écrit : > Hi, > > I just check with KSysguard: https://cloud.soungui.net/s/PmP84bxMB5WySfw. > > Right now, it's low because I restarted the services few minutes ago. By the > way, i'll will try to run fcsk and vacuum to see if it make things better. > > -- > > > Le jeudi 18 juillet 2019, 17:42:43 WAT Rainer Dorsch a écrit : > Hi Abba, > > can you show how you measure memory usage? > > Thanks > Rainer > > Am Mittwoch, 17. Juli 2019, 14:15:34 CEST schrieb Abba Soungui YOUNOUSS: > > Good morning, > > > > I have 2 computers which were running Stretch and have been upgraded to > > Buster recently. On both of them, I noticed an increase of memory usage > > (3-4 G) for the process akonadiserver. The only workaround that I've found > > till there, is to restart the service with akonadictl restart. It allow me > > to work peacefully for about a hour. > > > > Am I the only one? Is there an action needed after upgrade to Buster. -- Rainer Dorsch http://bokomoko.de/
Re: Akonadiserver use too much memory after upgrade to Buster
Hi Abba, can you show how you measure memory usage? Thanks Rainer Am Mittwoch, 17. Juli 2019, 14:15:34 CEST schrieb Abba Soungui YOUNOUSS: > Good morning, > > I have 2 computers which were running Stretch and have been upgraded to > Buster recently. On both of them, I noticed an increase of memory usage > (3-4 G) for the process akonadiserver. The only workaround that I've found > till there, is to restart the service with akonadictl restart. It allow me > to work peacefully for about a hour. > > Am I the only one? Is there an action needed after upgrade to Buster. -- Rainer Dorsch http://bokomoko.de/
Re: Gimp Print Dialogue almost unusable in Plasma/Buster
Hi Shai, many thanks for your reply. Am Samstag, 1. Juni 2019, 11:58:44 CEST schrieb Shai Berger: > On Sat, 01 Jun 2019 10:22:02 +0200 > > Rainer Dorsch wrote: > > Hi, > > > > since a few weeks the print dialogue of gimp has almost unreadable > > tabs (for all but the selected tab), an example is shown here > > > > http://netcup.bokomoko.de/~rd/Debian/gimp-print-dialogue-in-plasma.png > > > > I tried various settings in the Application Settings->GNOME > > Applications (GTK) but I do not see an impact and in particular the > > default settings do not help... > > Works fine for me, using the English interface. Try playing with the > Gtk-2 theme selection (I normally use Raleigh, but I checked with the > Adwaita-dark that you seem to have there and the tabs were still > clearly readable). No, I had Breeze, if I change to Adwaita-dark or HighContrast all tabs are readable :-) Yesterday, I think, I did not yet have this selection. In installed appmenu- gtk3-module, not sure if that helped to make larger selection available. To enhance usability, is there a way to make this the default setting? Thanks again, Rainer -- Rainer Dorsch http://bokomoko.de/
Gimp Print Dialogue almost unusable in Plasma/Buster
Hi, since a few weeks the print dialogue of gimp has almost unreadable tabs (for all but the selected tab), an example is shown here http://netcup.bokomoko.de/~rd/Debian/gimp-print-dialogue-in-plasma.png I tried various settings in the Application Settings->GNOME Applications (GTK) but I do not see an impact and in particular the default settings do not help... Any idea what might go wrong here (or confirmation that this is the same in other buster installations) is welcome :-) Thanks Rainer -- Rainer Dorsch http://bokomoko.de/
Re: Akonadi does not start for new users in buster
Am Montag, 4. Februar 2019, 16:34:51 CET schrieb Sandro Knauß: > Hey, > > > Can anybody check if that is the same on other buster systems? > > At least there are two different bugs with first start: > One with mariadb > (they moved my_print_defaults from mariadb-server-core -> mariadb-server), > so we need mariadb-server for initially start. This is reported: > https://bugs.debian.org/910902 > > the workaround: > * install mariadb-server > * replace the dump script with a symlink: > > rm /usr/sbin/mysqld-akonadi > ln -s /usr/sbin/mysqld /usr/sbin/mysqld-akonadi > > And than there is mysql, that is not happy about the current apparmor > profile: https://bugs.kde.org/show_bug.cgi?id=399346#c10 > > But I don't want to open the apparmor profile that much, so I someone with > more knowlege about apparmor can look into this. That'll be great. > > This mysql bug is not reported right now, it was only reported against kde > neon. And mysql is not default db anyways in Debian. > > hefee Thanks, hefee :-) # apt-get install mariadb-server and as new user (before starting akonadi) mkdir -p ~/.local/share/akonadi/db_data/ (I have not tried w/o this) worked around the problem for me. Since both is described in #910902, it seems there is no need to open another bugreport. Rainer -- Rainer Dorsch http://bokomoko.de/
Akonadi does not start for new users in buster
Hello, I observer on my buster system here, that akonadi does not start for new users (i.e. fresh added through adduser). It works well for existing users. Kmail says something along the lines Akonadi service for the personal information management does not work properly. [Translated back from German, for the original screenshot in German see http://scw.bokomoko.de/~rd/akonadi-issue.png ] For reference I add the output of an akonadi self-test here: http://scw.bokomoko.de/~rd/akonadi-selftest-report-20190203.txt Can anybody check if that is the same on other buster systems? The check is simple: - Run adduser testuser - Login as testuser - Start kmail If that is not only on my system, I think that would qualify for a release critical bugbut I want to avoid that I am missing something stupid and I do not want create unnecessary work for the Debian KDE team, which is doing a great job in having a recent KDE in buster :-) Thanks Rainer -- Rainer Dorsch http://bokomoko.de/
Re: Akregator in KDEPIM 18.08 crashes very often
Hi, it seems there is a fix for this issue available https://bugs.kde.org/show_bug.cgi?id=371511 which will be included in the next upstream release. Regards Rainer Am Samstag, 13. Oktober 2018, 20:58:29 CET schrieb szmas...@googlemail.com: > Hello Martin, > > in my case (debian testing) Akregator was working fine up to 4th > Oktober (4:17.12.3-1). > Upgrade to 4:18.08.1-1 versions (on 8th Oktober) of the libkf5* > libraries causes Akregator to crash (all the time by start). > By now I use archive from 4th Oktober and reverted all the attached > packages (rollback_2018_10_08.txt) to get Akregator working again. > In my opinion it drops down to the following libraries: > > libkf5contacts5:amd64=4:17.12.3-1 > libkf5contacts-data:all=4:17.12.3-1 > libkf5grantleetheme-plugins:amd64=17.12.3-1 > libkf5grantleetheme5:amd64=17.12.3-1 > libkf5mime5abi1:amd64=17.12.3-2 > libkf5mime-data:all=17.12.3-2 > libkf5imap5:amd64=17.12.3-2 > libkf5kontactinterface5:amd64=17.12.3-1 > libkf5kontactinterface-data:all=17.12.3-1 > libkf5mbox5:amd64=17.12.3-1 > libkf5calendarutils5:amd64=4:17.12.3-1 > libkf5tnef5:amd64=4:17.12.3-1 > > All the libraries (versions) above work for me fine (no Akregator > startup crash). > > Greetings > Peter > > On 2018-10-12 11:14, Martin Steigerwald wrote: > > Martin Steigerwald - 10.10.18, 23:29: > >> Often when clicking on a link. > >> > >> I had three or four crashes in just five minutes. > >> > >> Depending on scheduling my time I may investigate further in the next > >> days and if I can gather enough information, I file a bug report. > >> > >> I believe the issue to be Webengine integration related, but I need to > >> install the necessary debug packages to generate a useful backtrace. > > > > I bet it is this: > > > > Debian#910500: libqt5quick5: Sefault in applications using > > QWebEngineView > > https://bugs.debian.org/910500 > > > > Debian#910317: QtWebEngine in unstable is constantly crashing > > https://bugs.debian.org/910317 > > > > Unstable is affected. Testing should be safe due to bug severity. > > > > Downgrading just libqt5quick5 to just 5.11.1-5 as mentioned in 910500 > > does not fix the crashes in Akregator on my system. > > > > No time for further tests right now. > > > > Thanks, -- Rainer Dorsch http://bokomoko.de/
Re: KMail does not show the full header anymore
Am Donnerstag, 15. November 2018, 07:48:50 CET schrieb Pino Toscano: > In data giovedì 15 novembre 2018 07:37:36 CET, Rainer Dorsch ha scritto: > > I cannot find a way anymore to display the full mail header in kmail 5.9.1 > > (buster). Previously, View->Heades had various entries to select "Full > > header" or similar allowed to display the full header. Now there is only > > "KMail5.2" left. Can anybody tell if the way to display the full header > > changed or if that functionality was dropped? > > Is kdepim-addons installed? If not, install it, and restart kmail. Thanks, Pino for your reply. That improves the situation somewhat, now I can choose between three headers - KMail 5.2 - Short - Decorative or I can download new designs ...but displaying the full header is still not there (and also not in the list of downloadable designs). Are you able to display the full header? Thanks Rainer -- Rainer Dorsch http://bokomoko.de/
KMail does not show the full header anymore
Hi, I cannot find a way anymore to display the full mail header in kmail 5.9.1 (buster). Previously, View->Heades had various entries to select "Full header" or similar allowed to display the full header. Now there is only "KMail5.2" left. Can anybody tell if the way to display the full header changed or if that functionality was dropped? Thanks Rainer -- Rainer Dorsch http://bokomoko.de/
Re: Akregator in KDEPIM 18.08 crashes very often
Am Donnerstag, 11. Oktober 2018, 22:12:20 CEST schrieb Johannes Zarl-Zierl: > Am Mittwoch, 10. Oktober 2018, 23:29:08 CEST schrieb Martin Steigerwald: > > Hi! > > > > Often when clicking on a link. > > > > I had three or four crashes in just five minutes. > > Do you use nouveau by any chance? Just guessing, but this sounds like this > bug: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886428 > I see fequent crashes in akregator (not kmail) as well, but use an Intel GPU: [ 1998.383] (II) modeset(0): glamor X acceleration enabled on Mesa DRI Intel(R) UHD Graphics 630 (Coffeelake 3x8 GT2) Rainer -- Rainer Dorsch http://bokomoko.de/
Re: Hanging plasmashell
On Donnerstag, 31. Mai 2018 09:44:45 CEST Martin Steigerwald wrote: > Rainer Dorsch - 30.05.18, 23:20: > > On Mittwoch, 30. Mai 2018 13:38:43 CEST Miguel A. Vallejo wrote: > > > The problem is so annoying and frequent I moved (temporarily?) to > > > stable just to get work done. > > > > In this case testing would have been enough, the bug is marked > > critical, xorg- server 1.20 will not enter testing before this issue > > is addressed ;-) Also apt-listbugs is your friend when running > > testing... > > apt-listbugs does not trigger at all here. > > It happily just installed xserver-xorg-core anyway. Maybe because the bug > marked as critical is against src:xserver-xorg. I´d think it would affect > all of its binary packages then, but maybe apt-listbugs does not get this. > > I made the following similarly to how apt-listbugs does it: > > %:/etc/apt/preferences.d> cat xorg > Explaination: #900333 xserver-xorg-core: flickering, black screen and > modeset driver error: flip queue failed: Cannot allocate memory > Explaination: #900352 new xorg-server version causes a random freezes in > plasmashell Explaination: #900145 plasma-workspace: plasmashell freezes > every few times it appears Explaination: #900149 xserver-xorg: plasmashell > freezes after upgrade xserver-xorg Package: xserver-xorg-core > Pin: version 2:1.19.6-1 > Pin-Priority: 3 > So far testing does a good job: rd@b370:~$ rmadison xserver-xorg-core|cut -f 1-2 -d '|' xserver-xorg-core | 2:1.12.4-6+deb7u6 xserver-xorg-core | 2:1.16.4-1 xserver-xorg-core | 2:1.16.4-1+deb8u2 xserver-xorg-core | 2:1.19.1-4 xserver-xorg-core | 2:1.19.2-1+deb9u2 xserver-xorg-core | 2:1.19.6-1 xserver-xorg-core | 2:1.20.0-2 rd@b370:~$ and as far as I understand #900316 holds it back. https://tracker.debian.org/pkg/xorg-server rd@b370:~$ rmadison xserver-xorg-core xserver-xorg-core | 2:1.12.4-6+deb7u6 | oldoldstable | amd64, armel, armhf, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, s390x, sparc xserver-xorg-core | 2:1.16.4-1| oldstable-kfreebsd | kfreebsd-amd64, kfreebsd-i386 xserver-xorg-core | 2:1.16.4-1+deb8u2 | oldstable | amd64, arm64, armel, armhf, i386, mips, mipsel, powerpc, ppc64el, s390x xserver-xorg-core | 2:1.19.1-4| unstable | kfreebsd-amd64, kfreebsd-i386 xserver-xorg-core | 2:1.19.2-1+deb9u2 | stable | amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x xserver-xorg-core | 2:1.19.6-1| testing| amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x xserver-xorg-core | 2:1.20.0-2| unstable | amd64, arm64, armel, armhf, hurd-i386, i386, mips, mips64el, mipsel, powerpc, ppc64el, s390x rd@b370:~$ Certainly, testing relies on some users running unstable, otherwise testing would not work. I did not want to imply that apt-listbugs would have helped you here, I just gave it a recommendation for a tool which helped me sometimes in the past (certainly not always). Kind regards Rainer -- Rainer Dorsch http://bokomoko.de/
Re: Hanging plasmashell
On Mittwoch, 30. Mai 2018 13:38:43 CEST Miguel A. Vallejo wrote: > The problem is so annoying and frequent I moved (temporarily?) to stable > just to get work done. In this case testing would have been enough, the bug is marked critical, xorg- server 1.20 will not enter testing before this issue is addressed ;-) Also apt-listbugs is your friend when running testing... Rainer -- Rainer Dorsch http://bokomoko.de/
Re: Akonadi does not start
Hi hefee, thanks for your suggestions. I already deleted ~/.local/share/akonadi and ~/.config/akonadi I have probably now some stale data lying around, e.g. rd@b370:~/.config$ ls -l akonadi_* -rw--- 1 rd users70 Apr 14 2017 akonadi_akonotes_resource_0rc -rw--- 1 rd users56 Apr 14 2017 akonadi_akonotes_resource_3rc -rw--- 1 rd rd 200 Mai 14 08:41 akonadi_contactrc -rw--- 1 rd rd 241 Mai 14 21:27 akonadi_davgroupware_resource_0rc -rw--- 1 rd rd 253 Mai 14 21:27 akonadi_davgroupware_resource_1rc -rw--- 1 rd rd 239 Mai 14 21:28 akonadi_davgroupware_resource_2rc -rw--- 1 rd rd 260 Jun 10 2017 akonadi_davgroupware_resource_78rc -rw--- 1 rd rd 246 Jun 11 2017 akonadi_davgroupware_resource_81rc -rw--- 1 rd rd 260 Jun 11 2017 akonadi_davgroupware_resource_82rc -rw--- 1 rd rd 254 Jan 17 20:19 akonadi_davgroupware_resource_83rc -rw--- 1 rd users96 Apr 14 2017 akonadi_ical_resource_4rc -rw--- 1 rd rd 78 Mai 6 06:29 akonadi_ical_resource_5rc -rw--- 1 rd rd 306 Mai 14 23:51 akonadi_imap_resource_0rc -rw--- 1 rd rd26978 Jun 6 2017 akonadi_imap_resource_14rc -rw--- 1 rd users 324 Apr 14 2017 akonadi_imap_resource_5rc -rw--- 1 rd users 273 Apr 14 2017 akonadi_imap_resource_6rc -rw--- 1 rd rd 85 Mai 19 11:16 akonadi_indexing_agentrc -rw--- 1 rd users 133 Apr 14 2017 akonadi_kalarm_resource_0rc -rw--- 1 rd users 136 Apr 14 2017 akonadi_kalarm_resource_1rc -rw--- 1 rd users 137 Apr 14 2017 akonadi_kalarm_resource_2rc -rw--- 1 rd rd 130 Mai 4 2017 akonadi_kalarm_resource_3rc -rw--- 1 rd rd 133 Mai 4 2017 akonadi_kalarm_resource_4rc -rw--- 1 rd rd 134 Mai 4 2017 akonadi_kalarm_resource_5rc -rw--- 1 rd rd 74 Mai 14 21:17 akonadi_maildir_resource_0rc -rw--- 1 rd users74 Apr 14 2017 akonadi_maildir_resource_1rc -rw--- 1 rd rd 101 Mai 14 23:40 akonadi_maildispatcher_agent.notifyrc -rw--- 1 rd users 266 Apr 14 2017 akonadi_mailfilter_agentrc -rw--- 1 rd users 109 Apr 14 2017 akonadi_newmailnotifier_agentrc -rw--- 1 rd users 180 Apr 14 2017 akonadi_notes_agentrc -rw--- 1 rd rd 47 Mär 5 21:31 akonadi_sendlater_agent.notifyrc -rw--- 1 rd users 431 Apr 14 2017 akonadi_sendlater_agentrc -rw--- 1 rd users82 Apr 14 2017 akonadi_vcard_resource_10rc -rw--- 1 rd users79 Apr 14 2017 akonadi_vcard_resource_11rc -rw--- 1 rd users81 Apr 14 2017 akonadi_vcard_resource_12rc -rw--- 1 rd users73 Apr 14 2017 akonadi_vcard_resource_13rc -rw--- 1 rd users88 Apr 14 2017 akonadi_vcard_resource_14rc -rw--- 1 rd users81 Apr 14 2017 akonadi_vcard_resource_15rc -rw--- 1 rd users82 Apr 14 2017 akonadi_vcard_resource_16rc -rw--- 1 rd users 207 Apr 14 2017 akonadi_vcard_resource_3rc -rw--- 1 rd users 207 Apr 14 2017 akonadi_vcard_resource_4rc -rw--- 1 rd users83 Apr 14 2017 akonadi_vcard_resource_6rc -rw--- 1 rd users 115 Apr 14 2017 akonadi_vcard_resource_7rc -rw--- 1 rd users87 Apr 14 2017 akonadi_vcard_resource_9rc rd@b370:~/.config$ but the size does not hurt. Thanks again Rainer Am Samstag, 19. Mai 2018, 21:03:22 CEST schrieb Sandro Knauß: > Hey, > > it may be an issue with AppArmor - some people had issues with that. > > well the best would be to try to start the mysql db by hand and see if mysql > itself complains about the data: > > /usr/sbin/mysqld --defaults-file=~/.local/share/akonadi/mysql.conf > --datadir=~/.local/share/akonadi/db_data/ --socket=/tmp/test-mysql.socket -- > pid-file=/tmp/test-mysql.pid > > than you can connect to the database via to execute staements and test if it > is running: > > mysql --defaults-file=~/.local/share/akonadi/mysql.conf --socket=/tmp/test- > mysql.socket > > to stop mysql run: > mysqladmin --defaults-file=~/.local/share/akonadi/mysql.conf --socket=/tmp/ > test-mysql.socket shutdown > > hefee > > On Montag, 14. Mai 2018 09:28:37 CEST m...@bokomoko.de wrote: > > Hi, > > > > I just discovered another issue after running buster (copying the home > > directories from a stretch installation): > > > > For one account akonadi does not work properly, there seems to be a mysql > > issue: > > > > org.kde.pim.akonadiserver: DATABASE ERROR: > > org.kde.pim.akonadiserver: Error code: "2013" > > org.kde.pim.akonadiserver: DB error: "Lost connection to MySQL server > > during query" org.kde.pim.akonadiserver: Error text: "Lost connection to > > MySQL server during query QMYSQL3: Unable to execute statement" > > > > Full log is here: > > > > https://scw.bokomoko.de/~rd/akonadi.log > > > > It is surprising though that akonadi works on other accounts which are > > also > > configured to use the mysql driver :-/ > > > > Any input is welcome. -- Rainer Dorsch http://bokomoko.de/
Re: Switch User Broken
Hi, this seems to cause the issue https://bugs.gentoo.org/644718#c0 that is supposed to be the fix https://github.com/sddm/sddm/pull/1010/files but I have not yet validated it. Rainer -- Rainer Dorsch http://bokomoko.de/
Switch User Broken
Hello, it seems that in the a current buster installation, the switch user feature (i.e. run a parallel session for a second or a third user) is broken. Can anybody confirm this? Then I would open a bugreport... Thanks Rainer
kdepim over socks
Hi, for KDE4 in jessie "tsocks kdeinit4" made akonadi/kdepim using the socks server as defined in /etc/tsocks.conf. For KDE5 this does not seem to work anymore (also tsocks kdeinit5 does not solve the problem). Can anybody tell if something else needs to be done? Thanks Rainer
Run script after resume from suspend
Hi, I would like to run xmodmap ~/.Xmodmap after resuming from suspend. Is there a hook which is called after resume from suspend in KDE? Thanks Rainer -- Rainer Dorsch http://bokomoko.de/
Plasma mobile using Wayland on imx6
Might be of interest for some people here: Puri.sm is running Plasma mobile using Wayland on imx6 (ARM SoC) using Debian Testing: https://puri.sm/posts/running-plasma-mobile-on-an-imx6-test-board/ Rainer -- Rainer Dorsch http://bokomoko.de/
Re: libreoffice-kde package qt4 -> qt5
I just came accross https://eang.it/libreoffice-conference-2017/ At least active works seems to be ongoing... Rainer -- Rainer Dorsch http://bokomoko.de/
Bug#863844: kwalletmanager: Migration does not work and restarts at every login
Package: kwalletmanager Version: 4:16.08.3-1 Severity: important Dear Maintainer, since upgrading from Jessie to Stretch, the migration assistant starts at every login, but kwalletmanager does never see the old passwords. I assume the migration assistant crashes silently. I am happy to provide additional debug information, please specify what would help to better understand the failure. I classify the Severity as important since I do not know how many users will be affected by this bug, once Stretch is released. Thanks Rainer -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (500, 'testing'), (300, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages kwalletmanager depends on: ii kio 5.28.0-2 ii libc6 2.24-10 ii libkf5archive5 5.28.0-2 ii libkf5auth5 5.28.0-2 ii libkf5codecs5 5.28.0-1+b2 ii libkf5configcore5 5.28.0-2 ii libkf5configwidgets55.28.0-2 ii libkf5coreaddons5 5.28.0-2 ii libkf5dbusaddons5 5.28.0-1 ii libkf5i18n5 5.28.0-2 ii libkf5iconthemes5 5.28.0-2 ii libkf5itemviews55.28.0-1 ii libkf5jobwidgets5 5.28.0-2 ii libkf5kdelibs4support5 5.28.0-1 ii libkf5kiocore5 5.28.0-2 ii libkf5notifications55.28.0-1 ii libkf5service-bin 5.28.0-1 ii libkf5service5 5.28.0-1 ii libkf5textwidgets5 5.28.0-1 ii libkf5wallet-bin5.28.0-3 ii libkf5wallet5 5.28.0-3 ii libkf5widgetsaddons55.28.0-3 ii libkf5xmlgui5 5.28.0-1 ii libqt5core5a5.7.1+dfsg-3+b1 ii libqt5dbus5 5.7.1+dfsg-3+b1 ii libqt5gui5 5.7.1+dfsg-3+b1 ii libqt5widgets5 5.7.1+dfsg-3+b1 ii libqt5xml5 5.7.1+dfsg-3+b1 ii libstdc++6 6.3.0-18 Versions of packages kwalletmanager recommends: ii kde-runtime 4:16.08.3-2 kwalletmanager suggests no packages. -- no debconf information
Bug#843525: Goes away with amd64
Hi, I just wanted to confirm that this problem goes away immediately, if I run from an amd64 installation instead of an i386 installation (same home directory). Rainer -- Rainer Dorsch http://bokomoko.de/
Re: Upgrade from Jessie to Stretch
Quick update: This works flawless on an amd64 system, i.e. the issue shows only on i386 (and potentially other 32 bit systems). Rainer Am Freitag, 14. April 2017, 16:05:55 CEST schrieb Rainer Dorsch: > 3) kaddressbook crashes when started > > This is the trace I have seen: > > Application: KAddressBook (kaddressbook), signal: Segmentation fault > Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1". > [Current thread is 1 (Thread 0xacf4fac0 (LWP 5027))] > > Thread 9 (Thread 0xa7d0bb40 (LWP 5040)): > #0 0xb76fecf9 in __kernel_vsyscall () > #1 0xb5c35b0f in poll () at ../sysdeps/unix/syscall-template.S:84 > #2 0xb3a8c180 in poll (__timeout=-1, __nfds=1, __fds=0x81c80de8) at /usr/ > include/i386-linux-gnu/bits/poll2.h:46 > #3 0xb3a8c180 in g_poll (fds=0x81c80de8, nfds=1, timeout=-1) at ././glib/ > gpoll.c:124 > #4 0xb3a7c71c in g_main_context_poll (priority=, n_fds=1, > fds=0x81c80de8, timeout=, context=0x81c4e1b8) at ././glib/ > gmain.c:4228 > #5 0xb3a7c71c in g_main_context_iterate (context=context@entry=0x81c4e1b8, > block=block@entry=1, dispatch=dispatch@entry=1, self=) at > ././ glib/gmain.c:3924 > #6 0xb3a7c854 in g_main_context_iteration (context=0x81c4e1b8, > may_block=1) at ././glib/gmain.c:3990 > #7 0xb61674b4 in > QEventDispatcherGlib::processEvents(QFlags) > () at /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 > #8 0xb610b83d in QEventLoop::exec(QFlags) > () at /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 > #9 0xb5f34e95 in QThread::exec() () at /usr/lib/i386-linux-gnu/sse2/ > libQt5Core.so.5 > #10 0xb5f34f78 in QThread::run() () at /usr/lib/i386-linux-gnu/sse2/ > libQt5Core.so.5 > #11 0xb5f3a32a in () at /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 > #12 0xb419e2aa in start_thread (arg=0xa7d0bb40) at pthread_create.c:333 > #13 0xb5c3fa0e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:113 > > Thread 8 (Thread 0xa850cb40 (LWP 5038)): > #0 0xb76fecf9 in __kernel_vsyscall () > #1 0xb5c2ebcf in read () at ../sysdeps/unix/syscall-template.S:84 > #2 0xb3ac26b5 in read (__nbytes=16, __buf=0xa850bfbc, __fd= out>) at /usr/include/i386-linux-gnu/bits/unistd.h:44 > #3 0xb3ac26b5 in g_wakeup_acknowledge (wakeup=0xab6157b0) at ././glib/ > gwakeup.c:210 > #4 0xb3a7c189 in g_main_context_check (context=0xac202e00, > max_priority=2147483647, fds=0xac200fe8, n_fds=1) at ././glib/gmain.c:3707 > #5 0xb3a7c6b1 in g_main_context_iterate (context=context@entry=0xac202e00, > block=block@entry=1, dispatch=dispatch@entry=1, self=) at > ././ glib/gmain.c:3926 > #6 0xb3a7c854 in g_main_context_iteration (context=0xac202e00, > may_block=1) at ././glib/gmain.c:3990 > #7 0xb61674b4 in > QEventDispatcherGlib::processEvents(QFlags) > () at /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 > #8 0xb610b83d in QEventLoop::exec(QFlags) > () at /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 > #9 0xb5f34e95 in QThread::exec() () at /usr/lib/i386-linux-gnu/sse2/ > libQt5Core.so.5 > #10 0xb5f34f78 in QThread::run() () at /usr/lib/i386-linux-gnu/sse2/ > libQt5Core.so.5 > #11 0xb5f3a32a in () at /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 > #12 0xb419e2aa in start_thread (arg=0xa850cb40) at pthread_create.c:333 > #13 0xb5c3fa0e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:113 > > Thread 7 (Thread 0xa8fc1b40 (LWP 5036)): > #0 0xb3a7bc1d in g_main_context_prepare (context=0xab613e98, > priority=0xa8fc1074) at ././glib/gmain.c:3574 > #1 0xb3a7c624 in g_main_context_iterate (context=context@entry=0xab613e98, > block=block@entry=1, dispatch=dispatch@entry=1, self=) at > ././ glib/gmain.c:3909 > #2 0xb3a7c854 in g_main_context_iteration (context=0xab613e98, > may_block=1) at ././glib/gmain.c:3990 > #3 0xb61674b4 in > QEventDispatcherGlib::processEvents(QFlags) > () at /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 > #4 0xb610b83d in QEventLoop::exec(QFlags) > () at /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 > #5 0xb5f34e95 in QThread::exec() () at /usr/lib/i386-linux-gnu/sse2/ > libQt5Core.so.5 > #6 0xb5f34f78 in QThread::run() () at /usr/lib/i386-linux-gnu/sse2/ > libQt5Core.so.5 > #7 0xb5f3a32a in () at /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 > #8 0xb419e2aa in start_thread (arg=0xa8fc1b40) at pthread_create.c:333 > #9 0xb5c3fa0e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:113 > > Thread 6 (Thread 0xa99b3b40 (LWP 5034)): > #0 0xb3a7bb64 in g_main_context_prepare (context=0xaa203cf0, > priority=0xa99b3074) at ././glib/gmain.c:3513 > #1 0xb3a7c624 in g_main_context_iterate (context=context@entry=0xaa203cf0, > block=block@entry=1, dispatch=dispatch@entry=1, self=) at > ././ glib/gmain.c:3909 > #2 0xb3a7c854 in g_main_context_iteration (context=0xaa20
Bug#843525: Problem now gone for new user, but reappears when adding owncloud addressbook
Hi, just noticed that after the changes (mariadb instead of mysql and reinstalling akonadi-backend-mysql) kaddressbook and akonadiconsole work for a new user again. But when adding an owncloud addressbook (DAV resource), it crashes as well with the same stack trace: Thread 1 (Thread 0xacfe1ac0 (LWP 10870)): [KCrash Handler] #7 0xb5093166 in Akonadi::Tag::isValid() const () at /usr/lib/i386-linux-gnu/ libKF5AkonadiCore.so.5 #8 0xb514024a in Akonadi::TagModel::data(QModelIndex const&, int) const () at /usr/lib/i386-linux-gnu/libKF5AkonadiCore.so.5 #9 0xb76a1779 in () at /usr/lib/i386-linux-gnu/libkaddressbookprivate.so.5 #10 0xb61ce34e in QMetaObject::activate(QObject*, int, int, void**) () at / usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #11 0xb61ce85d in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () at /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #12 0xb624c741 in QAbstractItemModel::rowsInserted(QModelIndex const&, int, int, QAbstractItemModel::QPrivateSignal) () at /usr/lib/i386-linux-gnu/sse2/ libQt5Core.so.5 #13 0xb61422c9 in QAbstractItemModel::endInsertRows() () at /usr/lib/i386- linux-gnu/sse2/libQt5Core.so.5 #14 0xb51424ce in () at /usr/lib/i386-linux-gnu/libKF5AkonadiCore.so.5 #15 0xb5142c5a in () at /usr/lib/i386-linux-gnu/libKF5AkonadiCore.so.5 #16 0xb513f550 in () at /usr/lib/i386-linux-gnu/libKF5AkonadiCore.so.5 #17 0xb61cdfdb in QMetaObject::activate(QObject*, int, int, void**) () at / usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #18 0xb61ce85d in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () at /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #19 0xb50ec861 in Akonadi::TagFetchJob::tagsReceived(QVector const&) () at /usr/lib/i386-linux-gnu/libKF5AkonadiCore.so.5 #20 0xb50ee64a in () at /usr/lib/i386-linux-gnu/libKF5AkonadiCore.so.5 #21 0xb50ce036 in () at /usr/lib/i386-linux-gnu/libKF5AkonadiCore.so.5 #22 0xb50cef9b in () at /usr/lib/i386-linux-gnu/libKF5AkonadiCore.so.5 #23 0xb61cb0e0 in QMetaCallEvent::placeMetaCall(QObject*) () at /usr/lib/i386- linux-gnu/sse2/libQt5Core.so.5 #24 0xb61cee33 in QObject::event(QEvent*) () at /usr/lib/i386-linux-gnu/sse2/ libQt5Core.so.5 #25 0xb6a6f17a in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/i386-linux-gnu/libQt5Widgets.so.5 #26 0xb6a7703c in QApplication::notify(QObject*, QEvent*) () at /usr/lib/i386- linux-gnu/libQt5Widgets.so.5 #27 0xb619fc5d in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at / usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #28 0xb61a2647 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #29 0xb61a2a87 in QCoreApplication::sendPostedEvents(QObject*, int) () at / usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #30 0xb61f90a3 in () at /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #31 0xb3b0e4e9 in g_main_dispatch (context=0xac202a00) at ././glib/gmain.c: 3203 #32 0xb3b0e4e9 in g_main_context_dispatch (context=0xac202a00) at ././glib/ gmain.c:3856 #33 0xb3b0e789 in g_main_context_iterate (context=context@entry=0xac202a00, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ././ glib/gmain.c:3929 #34 0xb3b0e854 in g_main_context_iteration (context=0xac202a00, may_block=1) at ././glib/gmain.c:3990 #35 0xb61f9493 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #36 0xaccedd81 in () at /usr/lib/i386-linux-gnu/libQt5XcbQpa.so.5 #37 0xb619d83d in QEventLoop::exec(QFlags) () at /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #38 0xb61a699f in QCoreApplication::exec() () at /usr/lib/i386-linux-gnu/sse2/ libQt5Core.so.5 #39 0xb64d9aa1 in QGuiApplication::exec() () at /usr/lib/i386-linux-gnu/sse2/ libQt5Gui.so.5 #40 0xb6a6f0d4 in QApplication::exec() () at /usr/lib/i386-linux-gnu/ libQt5Widgets.so.5 #41 0x80042743 in () #42 0xb5c02276 in __libc_start_main (main=0x800423f0, argc=1, argv=0xbf9f4bc4, init=0x80043f60 <__libc_csu_init>, fini=0x80043fc0 <__libc_csu_fini>, rtld_fini=0xb779a8b0 <_dl_fini>, stack_end=0xbf9f4bbc) at ../csu/libc-start.c: 291 #43 0x800428dd in _start () Rainer -- Rainer Dorsch http://bokomoko.de/
Bug#843525: Purging and reinstalling akonadi-backend-mysql
For me purging and reinstalling akonadi-backend-mysql also did not fix the problem :-/ Rainer -- Rainer Dorsch http://bokomoko.de/
Bug#843525: mariadb-server-core-10.1 does not help either
Hi, installing mariadb-server-core-10.1 did not resolve the problem either... mariadb-server-core-10.1: Installiert: 10.1.22-3 Installationskandidat: 10.1.22-3 Versionstabelle: *** 10.1.22-3 500 500 http://ftp-stud.fht-esslingen.de/debian stretch/main i386 Packages 300 http://ftp-stud.fht-esslingen.de/debian sid/main i386 Packages 100 /var/lib/dpkg/status rd@blackbox:~$ apt-cache policy mysql-server mysql-server mysql-server-5.7 mysql-server-core-5.7 rd@blackbox:~$ apt-cache policy mysql-server mysql-server: Installiert: (keine) Installationskandidat: 5.7.17-1 Versionstabelle: 5.7.17-1 300 300 http://ftp-stud.fht-esslingen.de/debian sid/main i386 Packages 300 http://ftp-stud.fht-esslingen.de/debian sid/main amd64 Packages rd@blackbox:~$ apt-cache policy mysql-server-core-5.7 mysql-server-core-5.7: Installiert: (keine) Installationskandidat: 5.7.17-1 Versionstabelle: 5.7.17-1 300 300 http://ftp-stud.fht-esslingen.de/debian sid/main i386 Packages rd@blackbox:~$ -- Rainer Dorsch http://bokomoko.de/
Bug#860366: okular: Okular crashes when opening some documents
Package: okular Version: 4:16.08.2-1+b1 Severity: normal Dear Maintainer, when I try to open http://scw.bokomoko.de/~rd/fdbaut/2013-08-28-Uebersichtsplan.pdf with okular, it crashes. Evince opens on the same system the document without any problems. Thanks Rainer -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (500, 'testing'), (300, 'unstable'), (250, 'experimental') Architecture: i386 (i686) Foreign Architectures: amd64 Kernel: Linux 4.9.0-2-686-pae (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages okular depends on: ii kde-runtime 4:16.08.3-2 ii libc6 2.24-9 ii libfreetype62.6.3-3.1 ii libgcc1 1:6.3.0-12 ii libjpeg62-turbo 1:1.5.1-2 ii libkdecore5 4:4.14.26-1 ii libkdeui5 4:4.14.26-1 ii libkexiv2-114:15.04.3-1 ii libkio5 4:4.14.26-1 ii libkparts4 4:4.14.26-1 ii libkprintutils4 4:4.14.26-1 ii libkpty44:4.14.26-1 ii libokularcore7 4:16.08.2-1+b1 ii libphonon4 4:4.9.0-4 ii libpoppler-qt4-40.48.0-2 ii libqca2 2.1.1-4+b2 ii libqimageblitz4 1:0.0.6-4+b2 ii libqmobipocket1 4:16.08.0-1 ii libqt4-dbus 4:4.8.7+dfsg-11 ii libqt4-declarative 4:4.8.7+dfsg-11 ii libqt4-svg 4:4.8.7+dfsg-11 ii libqt4-xml 4:4.8.7+dfsg-11 ii libqtcore4 4:4.8.7+dfsg-11 ii libqtgui4 4:4.8.7+dfsg-11 ii libsolid4 4:4.14.26-1 ii libspectre1 0.2.8-1 ii libstdc++6 6.3.0-12 ii phonon 4:4.9.0-4 ii zlib1g 1:1.2.8.dfsg-5 Versions of packages okular recommends: ii cups-bsd 2.2.1-8 Versions of packages okular suggests: ii ghostscript9.20~dfsg-3 pn jovie ii okular-extra-backends 4:16.08.2-1+b1 ii poppler-data 0.4.7-8 ii texlive-binaries 2016.20160513.41080.dfsg-2 ii unrar 1:5.3.2-1 -- no debconf information
Bug#843525: kaddressbook: Same issue after upgrading from jessie to stretch
Package: kaddressbook
Version: 4:16.04.3-3
Followup-For: Bug #843525
Dear Maxy,
I think I hit the same issue on my system after upgrading from jessie
to stretch, before following the procedure above I give you a chance
to review, maybe it helps to find out what needs to be done to help
other jessie users who have not yet upgraded:
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
akonadiprivate_log: search paths: ("/usr/local/bin", "/usr/bin", "/bin",
"/usr/local/games", "/usr/games", "/usr/sbin", "/usr/local/sbin",
"/usr/local/libexec", "/usr/libexec", "/opt/mysql/libexec",
"/opt/local/lib/mysql5/bin", "/opt/mysql/sbin")
Found mysql_install_db: "/usr/bin/mysql_install_db"
Found mysqlcheck: "/usr/bin/mysqlcheck"
Using mysqld: "/usr/sbin/mysqld-akonadi"
mysqld reports version 5.5.54 (Oracle MySQL)
Executing: "/usr/sbin/mysqld-akonadi"
"--defaults-file=/home/test/.local/share/akonadi/mysql.conf
--datadir=/home/test/.local/share/akonadi/db_data/
--socket=/tmp/akonadi-test.7MgEGb/mysql.socket"
akonadicore_log: Socket error occurred: "QLocalSocket::connectToServer: Invalid
name"
akonadicore_log: Socket error occurred: "QLocalSocket::connectToServer: Invalid
name"
org.kde.akonadi.ETM: GEN true false true
org.kde.akonadi.ETM: collection: QVector()
Executing: "/usr/bin/mysqlcheck"
"--defaults-file=/home/test/.local/share/akonadi/mysql.conf --check-upgrade
--auto-repair --socket=/tmp/akonadi-test.7MgEGb/mysql.socket akonadi"
akonadi.collectiontableOK
akonadi.mimetypetable OK
akonadi.resourcetable OK
akonadi.schemaversiontable OK
MySQL version OK (required "5.1" , available "5.5" )
Database "akonadi" opened using driver "QMYSQL"
DbInitializer::run()
checking table "SchemaVersionTable"
checking table "ResourceTable"
checking table "CollectionTable"
checking table "MimeTypeTable"
checking table "PimItemTable"
"CREATE TABLE PimItemTable (id BIGINT NOT NULL AUTO_INCREMENT PRIMARY KEY, rev
INTEGER NOT NULL DEFAULT 0, remoteId VARBINARY(255), remoteRevision
VARBINARY(255), gid VARBINARY(255), collectionId BIGINT, mimeTypeId BIGINT,
datetime TIMESTAMP DEFAULT CURRENT_TIMESTAMP, atime TIMESTAMP DEFAULT
CURRENT_TIMESTAMP, dirty BOOL, size BIGINT NOT NULL DEFAULT 0, FOREIGN KEY
(collectionId) REFERENCES CollectionTable(id) ON UPDATE CASCADE ON DELETE
CASCADE, FOREIGN KEY (mimeTypeId) REFERENCES MimeTypeTable(id) ON UPDATE
CASCADE ON DELETE RESTRICT) COLLATE=utf8_general_ci DEFAULT CHARSET=utf8"
"\nSql error: Incorrect table definition; there can be only one TIMESTAMP
column with CURRENT_TIMESTAMP in DEFAULT or ON UPDATE clause QMYSQL: Unable to
execute query\nQuery: CREATE TABLE PimItemTable (id BIGINT NOT NULL
AUTO_INCREMENT PRIMARY KEY, rev INTEGER NOT NULL DEFAULT 0, remoteId
VARBINARY(255), remoteRevision VARBINARY(255), gid VARBINARY(255), collectionId
BIGINT, mimeTypeId BIGINT, datetime TIMESTAMP DEFAULT CURRENT_TIMESTAMP, atime
TIMESTAMP DEFAULT CURRENT_TIMESTAMP, dirty BOOL, size BIGINT NOT NULL DEFAULT
0, FOREIGN KEY (collectionId) REFERENCES CollectionTable(id) ON UPDATE CASCADE
ON DELETE CASCADE, FOREIGN KEY (mimeTypeId) REFERENCES MimeTypeTable(id) ON
UPDATE CASCADE ON DELETE RESTRICT) COLLATE=utf8_general_ci DEFAULT
CHARSET=utf8"
Unable to initialize database.
terminating service threads
terminating connection threads
stopping db process
Application 'akonadiserver' exited normally...
akonadicore_log: "Unknown error."
akonadicore_log: Job error: "Unknown error." for collection: QVector()
State of akonadi-backend-mysql:
blackbox:~# apt-cache policy akonadi-backend-mysql
akonadi-backend-mysql:
Installiert: 4:16.04.3-4
Installationskandidat: 4:16.04.3-4
Versionstabelle:
*** 4:16.04.3-4 500
500 http://ftp-stud.fht-esslingen.de/debian stretch/main i386 Packages
500 http://ftp-stud.fht-esslingen.de/debian stretch/main amd64 Packages
300 http://ftp-stud.fht-esslingen.de/debian sid/main i386 Packages
300 http://ftp-stud.fht-esslingen.de/debian sid/main amd64 Packages
100 /var/lib/dpkg/status
1.13.0-2+deb8u2 500
500 http://ftp-stud.fht-esslingen.de/debian jessie/main i386 Packages
500 http://ftp-stud.fht-esslingen.de/debian jessie/main amd64 Packages
1.13.0-2+deb8u1 500
500 http://snapshot.debian.org/archive/debian/20160901T042215Z
jessie/main i386 Packages
500 http://snapshot.debian.org/archive/debian/20160901T042215Z
jessie/main amd64 Packages
blackbox:~#
One reason could be that mysql was not updated properly
blackbox:~# apt-cache policy mysql-server-core-5.5
mysql-server-core-5.5:
Installiert: 5.5.54-0+deb8u1
Installationskandidat: 5.5.54-0+deb8u1
Versionstabelle:
*** 5.5.54-0+deb8u1 450
450 http://ftp-stud.fht-esslingen.de/debian
jessie-proposed-updates/main i386 Packages
Bug#830128: Might be related to KDE bug 365982
https://bugs.kde.org/show_bug.cgi?id=365982 -- Rainer Dorsch http://bokomoko.de/
Bug#830128: akonadiconsole: Same behavior after upgrade from jessie to stretch
Package: akonadiconsole Version: 4:16.04.3-3 Followup-For: Bug #830128 Dear maintainer, after upgrading from jessie to stretch I can neither start akonadiconsole nor kaddressbook, everything else seems to work ok (at least what I have seen so far): rd@blackbox:~/tmp.nobackup$ kaddressbook org.kde.akonadi.ETM: GEN true false true org.kde.akonadi.ETM: collection: QVector() KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = kaddressbook path = /usr/bin pid = 24465 KCrash: Arguments: /usr/bin/kaddressbook KCrash: Attempting to start /usr/lib/i386-linux-gnu/libexec/drkonqi from kdeinit sock_file=/run/user/2809/kdeinit5__0 [1]+ Stopped kaddressbook rd@blackbox:~/tmp.nobackup$ akonadiconsole org.kde.akonadi.ETM: GEN true true true org.kde.akonadi.ETM: collection: QVector() org.kde.akonadi.ETM: GEN true false true org.kde.akonadi.ETM: collection: QVector() org.kde.akonadi.ETM: GEN true false true org.kde.akonadi.ETM: collection: QVector() org.kde.akonadi.ETM: GEN true false true org.kde.akonadi.ETM: collection: QVector() org.kde.akonadi.ETM: Subtree: 7936 QSet(7940, 7937, 7936, 7939, 7938) org.kde.akonadi.ETM: Subtree: 1417 QSet(1417) org.kde.akonadi.ETM: Subtree: 6847 QSet(6847, 6849, 6848, 7928, 7927) org.kde.akonadi.ETM: Subtree: 9 QSet(3535, 2120, 9) org.kde.akonadi.ETM: Subtree: 5672 QSet(5672) org.kde.akonadi.ETM: Subtree: 5 QSet(5) org.kde.akonadi.ETM: Subtree: 4 QSet(4) org.kde.akonadi.ETM: Subtree: 1 QSet(7941, 7942, 1, 1359) org.kde.akonadi.ETM: Subtree: 3455 QSet(3455, 3456, 3465, 3466) org.kde.akonadi.ETM: Subtree: 3 QSet(3) org.kde.akonadi.ETM: Subtree: 3724 QSet(3724, 6841, 7929, 7930) org.kde.akonadi.ETM: Subtree: 6805 QSet(6805) org.kde.akonadi.ETM: Subtree: 3449 QSet(3449) org.kde.akonadi.ETM: Subtree: 6804 QSet(6804) org.kde.akonadi.ETM: Subtree: 6807 QSet(6807) org.kde.akonadi.ETM: Subtree: 7908 QSet(7910, 7923, 7924, 7909, 7908, 7911) org.kde.akonadi.ETM: Subtree: 6806 QSet(6806) org.kde.akonadi.ETM: Subtree: 6801 QSet(6801) org.kde.akonadi.ETM: Subtree: 3635 QSet(3635) org.kde.akonadi.ETM: Subtree: 6947 QSet(7388, 7391, 7390, 7385, 7384, 7387, 7386, 7381, 7380, 7383, 7382, 7377, 7376, 7379, 7378, 7405, 7404, 7407, 7406, 7401, 7400, 7403, 7402, 7397, 7396, 7399, 7398, 7393, 7392, 7395, 7394, 7421, 7420, 7423, 7422, 7417, 7416, 7419, 7418, 7413, 7412, 7415, 7414, 7409, 7408, 7411, 7410, 7309, 7308, 7311, 7310, 7305, 7304, 7307, 7306, 7301, 7300, 7303, 7302, 7297, 7296, 7299, 7298, 7325, 7324, 7327, 7326, 7321, 7320, 7323, 7322, 7317, 7316, 7319, 7318, 7313, 7312, 7315, 7314, 7341, 7340, 7343, 7342, 7337, 7336, 7339, 7338, 7333, 7332, 7335, 7334, 7329, 7328, 7331, 7330, 7357, 7356, 7359, 7358, 7353, 7352, 7355, 7354, 7349, 7348, 7351, 7350, 7345, 7344, 7347, 7346, 7245, 7244, 7247, 7246, 7241, 7240, 7243, 7242, 7237, 7236, 7239, 7238, 7233, 7232, 7235, 7234, 7261, 7260, 7263, 7262, 7257, 7256, 7259, 7258, 7253, 7252, 7255, 7254, 7249, 7248, 7251, 7250, 7277, 7276, 7279, 7278, 7273, 7272, 7275, 7274, 7269, 7268, 7271, 7270, 7265, 7264, 7267, 7266, 7293, 7292, 7295, 7294, 7289, 7288, 7291, 7290, 7285, 7284, 7287, 7286, 7281, 7280, 7283, 7282, 7181, 7180, 7183, 7182, 7177, 7176, 7179, 7178, 7173, 7172, 7175, 7174, 7169, 7168, 7171, 7170, 7197, 7196, 7199, 7198, 7193, 7192, 7195, 7194, 7189, 7188, 7191, 7190, 7185, 7184, 7187, 7186, 7213, 7212, 7215, 7214, 7209, 7208, 7211, 7210, 7205, 7204, 7207, 7206, 7201, 7200, 7203, 7202, 7229, 7228, 7231, 7230, 7225, 7224, 7227, 7226, 7221, 7220, 7223, 7222, 7217, 7216, 7219, 7218, 7117, 7116, 7119, 7118, 7113, 7112, 7115, 7114, 7109, 7108, 7111, 7110, 7105, 7104, 7107, 7106, 7133, 7132, 7135, 7134, 7129, 7128, 7131, 7130, 7125, 7124, 7127, 7126, 7121, 7120, 7123, 7122, 7149, 7148, 7151, 7150, 7145, 7144, 7147, 7146, 7141, 7140, 7143, 7142, 7137, 7136, 7139, 7138, 7165, 7164, 7167, 7166, 7161, 7160, 7163, 7162, 7157, 7156, 7159, 7158, 7153, 7152, 7155, 7154, 7053, 7052, 7055, 7054, 7049, 7048, 7051, 7050, 7045, 7044, 7047, 7046, 7041, 7040, 7043, 7042, 7069, 7068, 7071, 7070, 7065, 7064, 7067, 7066, 7061, 7060, 7063, 7062, 7057, 7056, 7059, 7058, 7085, 7084, 7087, 7086, 7081, 7080, 7083, 7082, 7077, 7076, 7079, 7078, 7073, 7072, 7075, 7074, 7101, 7100, 7103, 7102, 7097, 7096, 7099, 7098, 7093, 7092, 7095, 7094, 7089, 7088, 7091, 7090, 6989, 6988, 6991, 6990, 6985, 6984, 6987, 6986, 6981, 6980, 6983, 6982, 6977, 6976, 6979, 6978, 7005, 7004, 7007, 7006, 7001, 7000, 7003, 7002, 6997, 6996, 6999, 6998, 6993, 6992, 6995, 6994, 7021, 7020, 7023, 7022, 7017, 7016, 7019, 7018, 7013, 7012, 7015, 7014, 7009, 7008, 7011, 7010, 7037, 7036, 7039, 7038, 7033, 7032, 7035, 7034, 7029, 7028, 7031, 7030, 7025, 7024, 7027, 7026, 6957, 6956, 6959, 6958, 6953, 6952, 6955, 6954, 6949, 6948, 6951, 6950, 6947, 6973, 6972, 6975, 6974, 6969, 6968, 6971, 6970, 6965, 6964, 6967, 6966, 6961, 6960, 6963, 6962, 7898, 7892, 7891, 7917, 7916, 7919, 7918, 7915, 7914, 7907, 7921, 7920, 7922, 7821, 7820, 7823, 7822, 7817, 7816,
Re: Upgrade from Jessie to Stretch
) > at ././glib/gmain.c:3990 > #35 0xb6167493 in > QEventDispatcherGlib::processEvents(QFlags) > () at /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 > #36 0xacc54d81 in () at /usr/lib/i386-linux-gnu/libQt5XcbQpa.so.5 > #37 0xb610b83d in QEventLoop::exec(QFlags) () > at /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 > #38 0xb611499f in QCoreApplication::exec() () at > /usr/lib/i386-linux-gnu/sse2/ libQt5Core.so.5 > #39 0xb6447aa1 in QGuiApplication::exec() () at > /usr/lib/i386-linux-gnu/sse2/ libQt5Gui.so.5 > #40 0xb69dd0d4 in QApplication::exec() () at /usr/lib/i386-linux-gnu/ > libQt5Widgets.so.5 > #41 0x800cd743 in () > #42 0xb5b70276 in __libc_start_main (main=0x800cd3f0, argc=1, > argv=0xbffb8234, init=0x800cef60 <__libc_csu_init>, fini=0x800cefc0 > <__libc_csu_fini>, rtld_fini=0xb770f8b0 <_dl_fini>, stack_end=0xbffb822c) > at ../csu/libc-start.c: 291 > #43 0x800cd8dd in _start () > > Many thanks, > Rainer -- Rainer Dorsch http://bokomoko.de/
Upgrade from Jessie to Stretch
./sysdeps/unix/syscall-template.S:84 #2 0xb37e81dd in () at /usr/lib/i386-linux-gnu/libxcb.so.1 #3 0xb37ea553 in xcb_wait_for_event () at /usr/lib/i386-linux-gnu/libxcb.so.1 #4 0xacc1a853 in () at /usr/lib/i386-linux-gnu/libQt5XcbQpa.so.5 #5 0xb5f3a32a in () at /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #6 0xb419e2aa in start_thread (arg=0xacb26b40) at pthread_create.c:333 #7 0xb5c3fa0e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:113 Thread 1 (Thread 0xacf4fac0 (LWP 5027)): [KCrash Handler] #7 0xb5001166 in Akonadi::Tag::isValid() const () at /usr/lib/i386-linux-gnu/ libKF5AkonadiCore.so.5 #8 0xb50ae24a in Akonadi::TagModel::data(QModelIndex const&, int) const () at /usr/lib/i386-linux-gnu/libKF5AkonadiCore.so.5 #9 0xb760f779 in () at /usr/lib/i386-linux-gnu/libkaddressbookprivate.so.5 #10 0xb613c34e in QMetaObject::activate(QObject*, int, int, void**) () at / usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #11 0xb613c85d in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () at /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #12 0xb61ba741 in QAbstractItemModel::rowsInserted(QModelIndex const&, int, int, QAbstractItemModel::QPrivateSignal) () at /usr/lib/i386-linux-gnu/sse2/ libQt5Core.so.5 #13 0xb60b02c9 in QAbstractItemModel::endInsertRows() () at /usr/lib/i386- linux-gnu/sse2/libQt5Core.so.5 #14 0xb50b04ce in () at /usr/lib/i386-linux-gnu/libKF5AkonadiCore.so.5 #15 0xb50b0c5a in () at /usr/lib/i386-linux-gnu/libKF5AkonadiCore.so.5 #16 0xb50ad550 in () at /usr/lib/i386-linux-gnu/libKF5AkonadiCore.so.5 #17 0xb613bfdb in QMetaObject::activate(QObject*, int, int, void**) () at / usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #18 0xb613c85d in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () at /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #19 0xb505a861 in Akonadi::TagFetchJob::tagsReceived(QVector const&) () at /usr/lib/i386-linux-gnu/libKF5AkonadiCore.so.5 #20 0xb505c64a in () at /usr/lib/i386-linux-gnu/libKF5AkonadiCore.so.5 #21 0xb503c036 in () at /usr/lib/i386-linux-gnu/libKF5AkonadiCore.so.5 #22 0xb503cf9b in () at /usr/lib/i386-linux-gnu/libKF5AkonadiCore.so.5 #23 0xb61390e0 in QMetaCallEvent::placeMetaCall(QObject*) () at /usr/lib/i386- linux-gnu/sse2/libQt5Core.so.5 #24 0xb613ce33 in QObject::event(QEvent*) () at /usr/lib/i386-linux-gnu/sse2/ libQt5Core.so.5 #25 0xb69dd17a in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/i386-linux-gnu/libQt5Widgets.so.5 #26 0xb69e503c in QApplication::notify(QObject*, QEvent*) () at /usr/lib/i386- linux-gnu/libQt5Widgets.so.5 #27 0xb610dc5d in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at / usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #28 0xb6110647 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #29 0xb6110a87 in QCoreApplication::sendPostedEvents(QObject*, int) () at / usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #30 0xb61670a3 in () at /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #31 0xb3a7c4e9 in g_main_dispatch (context=0xac202a00) at ././glib/gmain.c: 3203 #32 0xb3a7c4e9 in g_main_context_dispatch (context=0xac202a00) at ././glib/ gmain.c:3856 #33 0xb3a7c789 in g_main_context_iterate (context=context@entry=0xac202a00, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ././ glib/gmain.c:3929 #34 0xb3a7c854 in g_main_context_iteration (context=0xac202a00, may_block=1) at ././glib/gmain.c:3990 #35 0xb6167493 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #36 0xacc54d81 in () at /usr/lib/i386-linux-gnu/libQt5XcbQpa.so.5 #37 0xb610b83d in QEventLoop::exec(QFlags) () at /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #38 0xb611499f in QCoreApplication::exec() () at /usr/lib/i386-linux-gnu/sse2/ libQt5Core.so.5 #39 0xb6447aa1 in QGuiApplication::exec() () at /usr/lib/i386-linux-gnu/sse2/ libQt5Gui.so.5 #40 0xb69dd0d4 in QApplication::exec() () at /usr/lib/i386-linux-gnu/ libQt5Widgets.so.5 #41 0x800cd743 in () #42 0xb5b70276 in __libc_start_main (main=0x800cd3f0, argc=1, argv=0xbffb8234, init=0x800cef60 <__libc_csu_init>, fini=0x800cefc0 <__libc_csu_fini>, rtld_fini=0xb770f8b0 <_dl_fini>, stack_end=0xbffb822c) at ../csu/libc-start.c: 291 #43 0x800cd8dd in _start () Many thanks, Rainer -- Rainer Dorsch http://bokomoko.de/
Re: Lost KMail Folders/outbox
Hi Markus,
thanks for your response.
On Saturday 04 February 2017 20:37:54 Markus Raab wrote:
> Hi,
>
> Rainer Dorsch wrote:
> > it seems that I lost the folder Kmail Folders/outbox (in the Kmail Folder
> > view). I seems I have a message stuck in the outbox and now all messages
> > are queing behind this message, i.e. sending mail with this kmail
> > installation does not work anymore :-(
> >
> > Akonadi console shows me that I have 14 messages queued in KMail
> > Folders/outbox.
> >
> > In Akonadi console I still see Kmail Folders/outbox in the Browser.
> >
> > Any insight how to recover this installation is very welcome.
>
> I had a similar issue with an out-going mail stucked for a very long time.
> (on a Debian Jessie box) The stucked mail was not shown in the outbox.
>
> For me, in the options -> configure kmail ("KMail einrichten") -> "Zugänge"
> -> sending mails ("Versand"), sending mails in the outbox ("Nachrichten im
> Postausgang senden:") changing to 'always when fetching mails' ("Bei allen
> Abholvorgängen") at least gets rid of stucked mails when I fetch mails the
> next time. (The english texts are guessed, I do not want to restart with
> other locales. Shouldn't be too hard to find.)
>
> Hope that helps.
I had that option already enabled ("Send messages in outbox folder: On All Mail
Checks").
What at the end helped me was the Arch wiki (which is a wonderful source of
information):
https://wiki.archlinux.org/index.php/KDE#Clean_akonadi_configuration_to_fix_KMail
I did not strictly follow, but after backing up the akonadi directories, I
opened
SystemSettings > Personal
and deleted the KMail Folder resource, which contained my outbox.
After that I restartarted akonadi and reopened kmail. My outbox was back in
another resource and I can send mail again.
Kind regards
Rainer
--
Rainer Dorsch
http://bokomoko.de/
Re: Lost KMail Folders/outbox
Hi Martin, Am Donnerstag, 2. Februar 2017, 23:01:20 schrieb Martin Steigerwald: > Am Donnerstag, 2. Februar 2017, 21:46:06 CET schrieb Rainer Dorsch: > > it seems that I lost the folder Kmail Folders/outbox (in the Kmail Folder > > view). I seems I have a message stuck in the outbox and now all messages > > are queing behind this message, i.e. sending mail with this kmail > > installation does not work anymore :-( > > > > Akonadi console shows me that I have 14 messages queued in KMail > > Folders/outbox. > > > > In Akonadi console I still see Kmail Folders/outbox in the Browser. > > > > Any insight how to recover this installation is very welcome. > > You mail lacks a lot of necessary information. It demonstrates exactly how > not to ask for help on a volunteer based mailing list. I am happy to share everything I know, I was hoping that somebody has seen something like this before. I was hoping for a specific log request... > Does not work anymore is by far not specific enough to say anything about > your issue. What does happen *exactly*? I press the send button and that's it. There is no log entry on the SMTP server. > No guess work, no speculations, > what do you *actually* observe? I still see the message arriving in akonadi console: AkonadiConsole Browser Widget (0xb39d8458) 1686 OK UID FETCH completed Archive Mail Kernel ETM (0xb17c3b98) 20128 STATUS 3541 (MESSAGES UNSEEN SIZE) Archive Mail Kernel ETM (0xb17c3b98) * STATUS "KMail Folders/outbox" (MESSAGES 1 UNSEEN 1 SIZE 2902) Archive Mail Kernel ETM (0xb17c3b98) 20128 OK STATUS completed MailFilter Kernel ETM (0x9b801bb0) 20125 STATUS 3541 (MESSAGES UNSEEN SIZE) akonadi_maildispatcher_agent (0x8c18668) 92 STATUS 3541 (MESSAGES UNSEEN SIZE) MailFilter Kernel ETM (0x9b801bb0) * STATUS "KMail Folders/outbox" (MESSAGES 1 UNSEEN 1 SIZE 2902) MailFilter Kernel ETM (0x9b801bb0) 20125 OK STATUS completed akonadi_maildispatcher_agent (0x8c18668) * STATUS "KMail Folders/outbox" (MESSAGES 1 UNSEEN 1 SIZE 2902) akonadi_maildispatcher_agent (0x8c18668) 92 OK STATUS completed akonadi_maildispatcher_agent (0x8c18668) 93 LIST 3541 0 (ENABLED TRUE) () akonadi_maildispatcher_agent (0x8c18668) * 3541 1282 (NAME "outbox" MIMETYPE (inode/directory) REMOTEID "" REMOTEREVISION "" RESOURCE "akonadi_mixedmaildir_resource_1" VIRTUAL 0 CACHEPOLICY (INHERIT true INTERVAL -1 CACHETIMEOUT 1 SYNCONDEMAND true LOCALPARTS (ENVELOPE)) ENABLED TRUE DISPLAY DEFAULT SYNC DEFAULT INDEX DEFAULT SpecialCollectionAttribute "outbox" ENTITYDISPLAY "(\"outbox\" \"mail-folder-outbox\" \"\" ())" AccessRights "a") akonadi_maildispatcher_agent (0x8c18668) 93 OK List completed AkonadiConsole Browser Widget (0xb39d8458) 1687 STATUS 3541 (MESSAGES UNSEEN SIZE) AkonadiConsole Browser Widget (0xb39d8458) * STATUS "KMail Folders/outbox" (MESSAGES 1 UNSEEN 1 SIZE 2902) AkonadiConsole Browser Widget (0xb39d8458) 1687 OK STATUS completed KMail Kernel ETM (0x8b80630) 1714 STATUS 3541 (MESSAGES UNSEEN SIZE) KMail Kernel ETM (0x8b80630) * STATUS "KMail Folders/outbox" (MESSAGES 1 UNSEEN 1 SIZE 2902) KMail Kernel ETM (0x8b80630) 1714 OK STATUS completed kmail2-411416715 (0x99e6f1b8) 3387 STATUS 3541 (MESSAGES UNSEEN SIZE) kmail2-411416715 (0x99e6f1b8) * STATUS "KMail Folders/outbox" (MESSAGES 1 UNSEEN 1 SIZE 2902) kmail2-411416715 (0x99e6f1b8) 3387 OK STATUS completed kmail2-411416715 (0x99e6f1b8) 3388 LIST 3541 0 (ENABLED TRUE) () kmail2-411416715 (0x99e6f1b8) * 3541 1282 (NAME "outbox" MIMETYPE (inode/directory) REMOTEID "" REMOTEREVISION "" RESOURCE "akonadi_mixedmaildir_resource_1" VIRTUAL 0 CACHEPOLICY (INHERIT true INTERVAL -1 CACHETIMEOUT 1 SYNCONDEMAND true LOCALPARTS (ENVELOPE)) ENABLED TRUE DISPLAY DEFAULT SYNC DEFAULT INDEX DEFAULT SpecialCollectionAttribute "outbox" ENTITYDISPLAY "(\"outbox\" \"mail-folder-outbox\" \"\" ())" AccessRights "a") kmail2-411416715 (0x99e6f1b8) 3388 OK List completed But I see no attempt from akonadi to hand over the message to the configured SMTP server. > Are there any error messages? Nothing more that I listed. > What does > mean "you lost the folder KMail Folders/outbox" exactly? While the KMail Folders/outbox it still visible in akonadi console, it is not visible anymore in KMail. This happened quite some time back, and is probably not the root cause of the issue, it just makes it hard to spot that an email gets not send, since there is no feedback at all to the user that the emails are not sent. If the outbox still would be there, the user can see that there are unsent emails in the outbox. > > Also I suggest kdepim-users upstream mailing list for things like this. I certainly can copy upstream, but since it is a stable installation I was expect that upstream does not care anymore, whereas here there might be quite a few users of Debian stable. Thanks Rainer -- Rainer Dorsch
Lost KMail Folders/outbox
Hello, it seems that I lost the folder Kmail Folders/outbox (in the Kmail Folder view). I seems I have a message stuck in the outbox and now all messages are queing behind this message, i.e. sending mail with this kmail installation does not work anymore :-( Akonadi console shows me that I have 14 messages queued in KMail Folders/outbox. In Akonadi console I still see Kmail Folders/outbox in the Browser. Any insight how to recover this installation is very welcome. Many thanks Rainer
Re: Lost mail, etc.
Hi Martin, On Monday 30 January 2017 12:46:59 Martin Steigerwald wrote: > > I have a lot of data in > > > > ~/.local/share/akonadi/file_db_data > > > > If this directory is pretty much empty, then your mail is probably gone. If > > that directory is still huge, there seems to be some data left, not sure > > how you recover the content though (it seems to be one file per mail, you > > could open it with less or an other pager or editor). > > Sorry, thats dangerous half-knowledge. > > While it could be that something is in there, that Akonadi didn´t save > elsewhere (yet), Akonadi is still mostly a cache. The real mail data is > elsewhere. I am sorry that I spread my half-knowledge... and many thanks for adding your explanation. Is there a way to control the size of this cache? Mine seems to be huge rd@blackbox:~/.local/share/akonadi/file_db_data$ du -sh . 12G . rd@blackbox:~/.local/share/akonadi/file_db_data$ and I would not mind reducing it to a lower single digit GB number. Many thanks Rainer -- Rainer Dorsch http://bokomoko.de/
Re: Lost mail, etc.
Hi Ed, I assume you use an POP3 Mailserver. Consider moving to an IMAP based setup to avoid these kind of issues in future. I have a lot of data in ~/.local/share/akonadi/file_db_data If this directory is pretty much empty, then your mail is probably gone. If that directory is still huge, there seems to be some data left, not sure how you recover the content though (it seems to be one file per mail, you could open it with less or an other pager or editor). Good luck Rainer On Sunday 29 January 2017 16:57:11 Ed Jabbour wrote: > I somehow lost the use of kmail - couldn't send, couldn't download and > lost my custom folders. I fooled around, reinstalled kmail, etc. Now, I can > send and download, but no folders and no saved mail. From a backup, I > restored ~/.kde/share/apps/kmail/mail/inbox, where the folders and mail > were. However, kmail still has no mail and no folders other than the > default ones. It's kmail 4.14.1. Any advice, pointers, etc. appreciated. > -- Rainer Dorsch http://bokomoko.de/
Re: Searching in dolphin
On Friday 06 January 2017 08:08:14 David McPearson wrote: > > On 2017-01-05 22:15, Brad Rogers wrote: > > On Thu, 05 Jan 2017 21:02:00 +0100 > > solitone <solit...@mail.com> wrote: > > > > Hello solitone, > > > >> What package is needed in order to use the search functionality in > >> Dolphin? At the moment I get an"invalid protocol" error. > > > > Nothing: > > > > Run System Settings, then go to Workspace -> Search -> File Search and > > turn *off* Enable File Search. That is, untick/uncheck it. Now apply, > > and then the Find file function will work in Dolphin. > > Hi Guys, > > Same error here on Debian Jessie/KDE 4.14.2/Dolphin 4.14.1. When I run > System Settings I do not see an option "Search option" > > According to the System Setting Manual there should be a "Desktop > Search" module under System Settings > Workspace Appearance and Behavior > - but it is not there. I assume this is what is meant by "File Search" > above. Am I correct? > > Any hints/instructions about how to get Dolphin's Find to work (given > the above)? > > Please note I turned file indexing off when I first installed Jessie. I can at least confirm that desktop search works for me in Jessie, my dataset is about 60 GB in about half a million files. There is "Desktop Search" and "Desktop Search Advanced" in "System Settings". In "Desktop Search Advanced" I specified which paths to exclude and which to include in the desktop search. I have enabled "Desktop search" and "File indexer" There is one glitch I noticed: dolphin searches from the current working directory. If the current working directory is a symbolic link, the search does not find anything. It seems baloo stores the physical paths and is not able to map symbolic paths to physical paths. I hope that helps... Rainer -- Rainer Dorsch http://bokomoko.de/
Re: Upcoming KDEPIM changes in unstable (KMail, Kontact, KOrganizer, etc)
On Sunday 03 July 2016 11:49:42 David Goodenough wrote: > On Saturday 02 July 2016 21:46:48 Lisandro Damián Nicanor Pérez Meyer wrote: > > Currently the latest version of kdepim is available in experimental. > > According to our limited tests it's working way better than kdepim 4.14 > > (more stable, more performant, less bugs). However migrating from one to > > the other is not a trivial process (distribution wise, hopefully not for > > our users). > > > > If you are still reading, please check the full text in [link]. > > > > [link] > > <http://perezmeyer.blogspot.com.ar/2016/07/upcoming-kdepim-changes-in-unst > > a > > ble.html> > > > > Happy hacking! > > Is there a migration guide so that we know what to expect (and when to > panic)? Yes, that would be useful. Maybe on a wiki page, which could be updated by developers and advanced users... E.g. is akonadi supposed to be migrated? Are mailbox (e.g. imap) settings preserved? Rainer -- Rainer Dorsch http://bokomoko.de/
Re: KDE4 in Stretch?
On Wednesday 01 June 2016 21:13:04 Andrej Kacian wrote: > On Wed, 01 Jun 2016 20:39:23 +0200 > > Martin Steigerwald <mar...@lichtvoll.de> wrote: > > I hope that Qt 5.6.1 also will fix more things than it breaks. Then maybe > > one of the last things I am quite annoyed with, that is multiscreen > > handling will work robustly, but I think it already got better with > > kscreen 5.22. > That's interesting, multiscreen handling is one of the areas where KDE5 > works without any issues for me - or at least I am not aware of > anything wrong. :) > > Perhaps my setup is just too simple (two screens next to each other). There seem to be quite some known problems in multiscreen handling, but for 5.7 sebas announces many fixes http://vizzzion.org/blog/2016/05/multiscreen-in-plasma-5-7-and-beyond/ Rainer -- Rainer Dorsch http://bokomoko.de/
Re: kde framework 5.21
On Friday 15 April 2016 12:03:27 Maximiliano Curia wrote: > I'm currently working on reducing it, by building most of the packages > automatically, it still needs several improvements but, it's getting there. That sounds excellent, I am really looking forward to see this automatic package creation in action. Many, many thanks for that great work Rainer -- Rainer Dorsch http://bokomoko.de/
Re: KDE Plasma 5.6 in Debian unstable / testing?
HI Hillel, I am not involved in packaging, but I see 5.5.4 in experimental (but have not yet tested it): rd@nanette:~$ rmadison plasma-desktop debian: plasma-desktop | 4:4.4.5-7+squeeze1 | squeeze | amd64, armel, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc plasma-desktop | 4:4.8.4-6 | wheezy | amd64, armel, armhf, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, s390x, sparc plasma-desktop | 4:4.11.13-2| jessie-kfreebsd | kfreebsd-amd64, kfreebsd-i386 plasma-desktop | 4:4.11.13-2| jessie | amd64, arm64, armel, armhf, i386, mips, mipsel, powerpc, ppc64el, s390x plasma-desktop | 4:5.4.3-1 | stretch | source, amd64, arm64, armel, armhf, i386, mips, mipsel, powerpc, ppc64el, s390x plasma-desktop | 4:5.4.3-1 | sid | source, amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, powerpc, ppc64el, s390x plasma-desktop | 4:5.5.4-1 | experimental| source, amd64 new: rd@nanette:~$ Rainer Am Dienstag, 29. März 2016, 00:32:00 schrieb Hillel Lubman: > Hi. > > Do you have any plans to package recently released KDE Plasma 5.6 in Debian? > And what is the delay in general (5.5.x was skipped altogether). It it some > compatibility issue or something else, or may there are some Qt blockers? > > Thanks, > Hillel Lubman.
The specified camera is not supported.
Hi,
in the latest Debian stable release (8.2) I get an error message when
connecting my camera and when I use the "Available devices" system tray icon
to "Download photos with digikam":
The specified camera
("/org/kde/solid/udev/sys/devices/pci:00/:00:0b.1/usb1/1-4/1-4:1.0")
is not supported.
Surprisingly, it works flawless, when I use inside digikam the Import->Cameras-
>USB PTP Camera Class or even Import->Cameras->Canon Inc. Canon Digital camera
(auto-detected)
lsusb reveals the camera on usb bus 1, device 006. The error message seems to
imply that for whatever reason digikam tries to open device number 4 on bus 1.
rd@Silberkiste:~$ lsusb
Bus 001 Device 006: ID 04a9:322c Canon, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 04b8:0103 Seiko Epson Corp. GT-6600U [Perfection 610]
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
rd@Silberkiste:~$
Any idea how to fix the system tray entry would be very welcome.
Rainer
Re: kdepim/akonadi for jessie-backports
On Saturday 28 November 2015 14:38:09 Sandro Knauß wrote: > Unfortunatelly 4.14 branch is closed, so I'm currently > backporting all patches from our branches to master in kdepim. And since we have no stable-backports, for Debian 4.14 was even earlier closed :-/ Rainer -- Rainer Dorsch http://bokomoko.de/
[OT] KDEPIM KF5 status and test plan
Hi everybody, somewhat off-topic, since not Debian specific, but maybe somebody who here is interested to help in testing the DAV interface for KDEPIM upsteam: http://www.aegiap.eu/kdeblog/2015/06/kdepim-kf5-status-and-test-plan/ Rainer -- Rainer Dorsch http://bokomoko.de/
Re: Newer KDEPIM for Jessie
Hi, On Wednesday 13 May 2015 09:31:57 Lisandro Damián Nicanor Pérez Meyer wrote: I might try to build 4.14.7 packages for Jessie myself. I've been following the discussion for a while, and my understanding is that supplying 4.14.7 packages with jessie-backports would block the backports on KDE4, while someone might want to get KDE5 into it, which would then be impossible. Right. are there any cons of having 4.14.7 in one of the next point releases and KDE5 via backports for jessie? I understand that in general new upstream releases are not supposed to pushed in in point releases. In this case it makes perfect sense for me though and there are other examples which do it as well, e.g. chromium pushes even bigger changes into point releases rd@blackbox:~$ rmadison chromium|grep jessie|grep amd64 chromium | 41.0.2272.118-1| jessie | amd64, i386 chromium | 42.0.2311.135-1~deb8u1 | jessie-p-u | amd64, i386 chromium | 42.0.2311.135-1~deb8u1 | jessie-security | amd64, i386 rd@blackbox:~$ Rainer -- Rainer Dorsch Lärchenstr. 6 72135 Dettenhausen 07157/734133
[Offtopic] KDEPIM Sprint Report
Hi, this is somewhat offtopic, but there might be people interested in the future of KDEPIM on the list http://www.dvratil.cz/2015/04/what-happened-in-toulouse/ Kind regards Rainer -- Rainer Dorsch http://bokomoko.de/ -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/102099653.iictmfSN1f@blackbox
Re: Newer KDEPIM for Jessie
Hi Martin, thanks for sharing your positive experience. I agree, getting these kind of KDEPIM fixes through backports would be a great enhancement for Jessie KDE users. Do you compile to /opt or do you build proper Debian packages of the upstream akonadi and kdepim? Though having the backports path after the Jessie release open for additional fixes (or security updates?) would mean that no newer packages can go into sid. If somebody would spend the work to provide patches for Jessie, would there be a way to continuously update the packages in the Debian infrastructure? Or would that only work with an external repo? Thanks again Rainer On Thursday 26 March 2015 13:06:40 Martin Steigerwald wrote: Hi! I think it would be good to have a newer KDEPIM + Akonadi into Jessie. Why? The current akonadi 1.13 master branch together with kdepim, kdepimlibs, kdepim-runtime from 4.14 branches (as of 4.14.6/7) here runs better than *ever* before, including my most annoying bug [Akonadi] [Bug 343114] gets stuck on one request that times out, kmail and akonadiconsole do not display any mail payloads anymore, stuck waiting https://bugs.kde.org/show_bug.cgi?id=343114 gone for good as well. For the first time in years (!) I didn´t have to restart either Akonadi or KMail just to keep it running with *both* my private huge POP3 and smaller IMAP and my huge work IMAP setup with crappy IMAP server (Exchange) for a week or so (okay, with using the work IMAP for as most as long as a work day without logout/login). That said, I have no idea whatsoever what commit may contain the fix. But as the mentioned branches are for fixes anyway, they shouldn´t contain any major breakage. I didn´t see any regression at all so far, and I think I use quite a subset of KDEPIM functionality. Also due to the MySQL performance improvements, the load on the machine is way lower. Not perfect yet, but *much* better. Compared with current akonadi 1.13 and kdepim 4.14.2 versions currently in sid, this is a *huge* improvement. I personally will just self-compile things until newer stuff is available via unstable and experimental. But for all the users of KDEPIM in stable it would be highly beneficial to have the newer versions in the archive. And yes, I know, likely the only way at this late stage would be to retrofit them via backports. I think for the experience of the stable users it would be highly beneficial. Thanks, -- Rainer Dorsch http://bokomoko.de/
Re: KDEPIM issues (was: Re: Bugs bugs bugs)
On Sunday 22 February 2015 16:13:10 Martin Steigerwald wrote: What could work quite well, and thats why I think for Munich it could work, would be to have some decent (!) IMAP server like Dovecot (not Exchange!) together with KMail. I have this setup here and indeed dovecot-imap, akonadi and kmail work nicely together for me. All are Debian jessie boxes. Rainer -- Rainer Dorsch http://bokomoko.de/ -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1799689.gj3HT5iYvv@blackbox
outbox disappeared
Hi, I discovered that my outbox (holding unsent messages) disappeared and thought it has something todo with my user configuration and checked with kdepim-users: http://lists.kde.org/?l=kdepim-usersm=142031569006557w=2 But I now saw the same issue for a second issue. Does anybody else have a missing outbox folder on a Debian (jessie) system? Thanks, Rainer -- Rainer Dorsch http://bokomoko.de/ -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5102654.TaVzZANcgZ@blackbox
Cannot add DAV groupware resource to kaddressbook
Hi,
I tried to add a DAV groupware resource on kaddressbook on a jessie system,
but it silently failed: all dialogs worked ok, but addressbook does not show
in kaddressbook.
Investigating .xsession-errors shows a DATABASE ERROR:
akonadi_davgroupware_resource_8(1960)/kio (KIOJob)
KIO::TransferJob::slotFinished:
KUrl(https://r...@home.bokomoko.de/owncloud/remote.php/caldav/calendars/rd/;)
akonadi_davgroupware_resource_8(1960)/kio (Scheduler)
KIO::SchedulerPrivate::jobFinished: KIO::DavJob(0x94c5658)
KIO::Slave(0x9895a78)
akonadi_davgroupware_resource_8(1960)/kio (Scheduler)
KIO::SchedulerPrivate::jobFinished: Updating ioslaves with new internal
metadata information
akonadi_davgroupware_resource_8(1960)/kio (Scheduler)
KIO::SchedulerPrivate::jobFinished: Updated configuration of https ioslave,
pid= 1964
akonadi_davgroupware_resource_8(1960)/kio (Scheduler)
KIO::SchedulerPrivate::jobFinished: Updated configuration of https ioslave,
pid= 1964
akonadi_davgroupware_resource_8(1960)/kio (Scheduler)
KIO::SchedulerPrivate::updateInternalMetaData: KIO::DavJob(0x94c5658)
QMap(({internal~currenthost}cached-www-auth, true)
({internal~currenthost}www-auth-challenge, Basic realm=ownCloud)
({internal~currenthost}www-auth-realm, ownCloud))
DATABASE ERROR:
Error code: 1062
DB error: Duplicate entry '1031-5' for key 'PRIMARY'
Error text: Duplicate entry '1031-5' for key 'PRIMARY' QMYSQL3: Unable to
execute statement
Query: INSERT INTO CollectionMimeTypeRelation (Collection_id, MimeType_id)
VALUES (:0, :1)
Error during adding a record to table CollectionMimeTypeRelation Duplicate
entry '1031-5' for key 'PRIMARY' QMYSQL3: Unable to execute statement
I upgraded this system from wheezy, but I did that also with others before. I
am not sure, what makes this system different from the others.
Any idea is welcome.
Many thanks,
Rainer
--
To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/1877589.Z3jpeZN7dr@omjuta
Re: Authenticity check failures in konqueror
On Tuesday 28 October 2014 15:22:11 Allan Sandfeld Jensen wrote: On Sunday 26 October 2014, Martin Steigerwald wrote: Am Sonntag, 26. Oktober 2014, 11:44:27 schrieb Rainer Dorsch: Hello, Hello Rainer, I see a lot of authenticity check failures when using Konqueror. Do I have a bad config or do other people see that as well (and have given up using konqueror)? I see this as well, for example with any side that access fbstatic.com (or so) seems some static Facebook content server. I never see this when accessing the same site with Iceweasel. I tried Qupzilla as Konqueror seems to have more and more issues with websites, but while it works quite nice I also have some issues with it: - It doesn´t handle man:/ls and things like Konqueror - It opens new sites in new tabs. I use activities and it opens just one window and opens new site I load with Alt-F2 someurl into new tab on a Qupzilla window even when it is on a different activity. I´d love to see Konqueror getting some developer love :). For me currently all browsers have their pitfalls. Chromium had the API key error stuff (no sorted I think), and its non standard GUI controls, Iceweasel… well on some sites I can´t open dynamic menus, but might be some extension. And Qupzilla see above, and Konqueror… well… with WebKit engine no zoom keys in Akregator and with khtml… hmmm… display errors on quote some webpages. This is caused by Debian using the Mozilla certificate store as their own. The Mozilla certificate store is only meant for Mozilla and the NSS library, and doesn't work with OpenSSL like Qt uses. Thanks for your reply, Allan. Is there a bug report for this issue? Thanks again, Rainer -- Rainer Dorsch http://bokomoko.de/ -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/3038738.Jo7ArExy1X@blackbox
Authenticity check failures in konqueror
Hello, I see a lot of authenticity check failures when using Konqueror. Do I have a bad config or do other people see that as well (and have given up using konqueror)? Thanks, Rainer -- Rainer Dorsch http://bokomoko.de/ -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1563709.HtBZgdzvF7@blackbox
Re: pm-suspend and KDE sleep
Hi Rubin, On Wednesday 23 July 2014 11:27:00 Rubin Abdi wrote: Rainer Dorsch wrote on 2014-07-21 13:10: For me this solved my problem (replace the ExecStart script with whatever you need): blackbox:~# cat /etc/systemd/system/root-resume.service ... I did a dist-upgrade a few days ago and it seems like my on sleep/wake scripts sitting in /etc/pm/sleep.d/ are now no longer being hit. By reading your previous post, should I assume now that /etc/systemd/system/root-resume.service is the new proper way of going about this from this point forward with systemd? Yes, as far as I understand. See the archlinux wiki for some background information: https://wiki.archlinux.org/index.php/Power_Management Rainer -- Rainer Dorsch http://bokomoko.de/ -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1895888.mu8fnA03ED@blackbox
Re: pm-suspend and KDE sleep
On Tuesday 15 July 2014 15:04:43 Rubin Abdi wrote: Rainer Dorsch wrote on 2014-07-15 14:48: On #kde irc somebody mentioned that KDE is not using pm-utils anymore, but upower instead. upower 0.9.23-2+b2 Does suspend/resume work or are the hook scripts in /etc/pm/config.d/ really executed? The act of suspend/resume, and hibernation all work for me. I have nothing sitting in /etc/pm/config.d, but plenty of stuff in /etc/pm/sleep.d. The scripts that I have which cause things to happen on sleep I know are working just fine. However now that I'm thinking about it I have a feeling some of the on resume events haven't been happening as of late. I wont be able to test until later tonight to be sure. Does upower scrape up scripts from elsewhere in etc? For me this solved my problem (replace the ExecStart script with whatever you need): blackbox:~# cat /etc/systemd/system/root-resume.service [Unit] Description=Local system resume actions After=suspend.target [Service] Type=simple ExecStart=/etc/init.d/hdparm restart [Install] WantedBy=suspend.target blackbox:~# systemctl enable root-resume As often the execellent Arch Linux documentation describes the solution: https://wiki.archlinux.org/index.php/Power_management#Sleep_hooks -- Rainer Dorsch http://bokomoko.de/ -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/7616971.3vbkjyem0J@blackbox
Re: pm-suspend and KDE sleep
Hi Diederik,
On Monday 14 July 2014 23:39:01 Diederik de Haas wrote:
On Monday 14 July 2014 22:01:03 Rainer Dorsch wrote:
my scripts in the /etc/pm/sleep.d are not executed anymore when running
KDE
sleep. When running pm-suspend from the cmd line the problem is not there.
Does anybody know if KDE does not use pm-utils anymore for suspend and
resume for some reason?
I've reinstalled pm-utils, but I still don't have any scripts in /etc/pm/* .
Do you know how you got them?
I created the script manually. The scripts which come with pm-utils are in
/usr/lib/pm-utils/
Hibernate does not work at all on my machine anymore.
Have your swap partitions changed? If yes please check
blackbox:~# cat /etc/initramfs-tools/conf.d/resume
# RESUME=/dev/sdb2
RESUME=/dev/disk/by-uuid/cfac727c-78d3-4c20-8e08-1a599d42a117
blackbox:~#
and
blackbox:~# cat /etc/uswsusp.conf
# /etc/uswsusp.conf(8) -- Configuration file for s2disk/s2both
resume device = /dev/disk/by-uuid/cfac727c-78d3-4c20-8e08-1a599d42a117
compress = y
early writeout = y
image size = 974180433
RSA key file = /etc/uswsusp.key
shutdown method = platform
blackbox:~#
After making changes run
# update-initramfs -u
Suspend does work when using the free nouveau drivers, but not properly
with the proprietary nvidia drivers (from the nvidia-driver package).
With the nvidia drivers my desktop isn't painted correctly anymore and all I
can do is press ('blindly') Alt+F5 - Alt+l - 3x arrow up - Enter
(Ctl+Alt+Backspace seems to work too) to log out at which point I can log
back in again (and then it works).
Fortunately I have only one nvidia system left, their linux support has been
poor.
So all I'm really saying is that hibernate and suspend don't work properly
on my KDE system (haven't tried another DE, no plans either) and haven't
for (quite) some time.
I'm using Sid.
In the past KDE suspend used pm-utils, but right now that seems not to be the
case anymore
Rainer
--
Rainer Dorsch
http://bokomoko.de/
--
To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/1594763.1aiFF4xUcU@blackbox
Re: pm-suspend and KDE sleep
On Tuesday 15 July 2014 14:28:13 Rubin Abdi wrote: Rainer Dorsch wrote on 2014-07-14 13:01: my scripts in the /etc/pm/sleep.d are not executed anymore when running KDE sleep. When running pm-suspend from the cmd line the problem is not there. Does anybody know if KDE does not use pm-utils anymore for suspend and resume for some reason? What version of things are you running? Works for me on a ThinkPad X220 with Sid dist-upgraded sometime early last week. On #kde irc somebody mentioned that KDE is not using pm-utils anymore, but upower instead. Does suspend/resume work or are the hook scripts in /etc/pm/config.d/ really executed? suspend/resume works here as well. My only issue is the my harddisks do not spin down anymore after a resume. Before I have done that through a resume hook. Linux lines 3.15.0-custom-01 #2 SMP Thu Jun 12 21:07:23 CDT 2014 x86_64 GNU/Linux plasma-desktop 4:4.11.9-1 pm-utils1.4.1-14 I have a very similar setup: rd@blackbox:~$ uname -a Linux blackbox 3.13-1-686-pae #1 SMP Debian 3.13.10-1 (2014-04-15) i686 GNU/Linux rd@blackbox:~$ apt-cache policy pm-utils pm-utils: Installiert: 1.4.1-15 Installationskandidat: 1.4.1-15 Versionstabelle: *** 1.4.1-15 0 300 http://ftp-stud.fht-esslingen.de/debian/ sid/main i386 Packages 100 /var/lib/dpkg/status 1.4.1-14 0 600 http://ftp-stud.fht-esslingen.de/debian/ jessie/main i386 Packages 1.4.1-9 0 500 http://ftp-stud.fht-esslingen.de/debian/ wheezy/main i386 Packages rd@blackbox:~$ apt-cache policy plasma-desktop plasma-desktop: Installiert: 4:4.11.9-1 Installationskandidat: 4:4.11.9-1 Versionstabelle: *** 4:4.11.9-1 0 600 http://ftp-stud.fht-esslingen.de/debian/ jessie/main i386 Packages 300 http://ftp-stud.fht-esslingen.de/debian/ sid/main i386 Packages 100 /var/lib/dpkg/status 4:4.8.4-6 0 500 http://ftp-stud.fht-esslingen.de/debian/ wheezy/main i386 Packages rd@blackbox:~$ -- Rainer Dorsch http://bokomoko.de/ -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/2494364.jhq1SntE9K@blackbox
pm-suspend and KDE sleep
Hello, my scripts in the /etc/pm/sleep.d are not executed anymore when running KDE sleep. When running pm-suspend from the cmd line the problem is not there. Does anybody know if KDE does not use pm-utils anymore for suspend and resume for some reason? Thanks, Rainer -- Rainer Dorsch http://bokomoko.de/ -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/8741454.WRKOEbaJYj@blackbox
Kopete accounts offline after suspend/resume cycle
Hello, since a few months my kopete accounts are offline after resume from suspend. After the initial start of kopete they are still automatically online. Does anybody have an idea how to fix the auto-offline issue? Thanks, Rainer -- Rainer Dorsch http://bokomoko.de/ -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/6790268.MQcuJRk81l@blackbox
Fwd: Re: Fwd: Re: [kdepim-users] akonadi_imap_resource segfaults
Hi, are there any projections, when 4.13 will hit experimental? Thanks, Rainer Original-Nachricht Return-path:rdor...@web.de Envelope-to:r...@bokomoko.de Delivery-date: Tue, 13 May 2014 09:29:49 +0200 Received: from mout.web.de ([212.227.15.3]) by bokomoko.de with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from rdor...@web.de) id 1Wk79l-00042o-B7 for r...@bokomoko.de; Tue, 13 May 2014 09:29:49 +0200 Received: from [213.165.67.104] ([213.165.67.104]) by mx-ha.web.de (mxweb006) with ESMTP (Nemesis) id 0Lb4C9-1XCK9z2rvN-00kepv for r...@bokomoko.de; Tue, 13 May 2014 09:29:39 +0200 Received: from mx1.redhat.com ([209.132.183.28]) by mx-ha.web.de (mxweb006) with ESMTP (Nemesis) id 0McDDz-1WTpK92h2l-00Jawf for rdor...@web.de; Tue, 13 May 2014 09:29:38 +0200 Received: from int-mx13.intmail.prod.int.phx2.redhat.com (int-mx13.intmail.prod.int.phx2.redhat.com [10.5.11.26]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id s4D7Tb4u008479 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for rdor...@web.de; Tue, 13 May 2014 03:29:37 -0400 Received: from thor.localnet (dhcp-24-135.brq.redhat.com [10.34.24.135]) by int-mx13.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id s4D7TZoT016327 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for rdor...@web.de; Tue, 13 May 2014 03:29:36 -0400 From: Daniel Vrátil dvra...@redhat.com To: Rainer Dorsch rdor...@web.de Date: Tue, 13 May 2014 09:29:34 +0200 Message-ID: 25932218.k6rcLBx4Cf@thor Organization: Red Hat User-Agent: KMail/4.14 pre (Linux/3.14.2-200.fc20.x86_64; KDE/4.13.60; x86_64; git-73f4c4f; 2014-05-07) In-Reply-To:537116a6.30...@web.de References: 53601ea2.40...@bokomoko.de 537116a6.30...@web.de MIME-Version: 1.0 Content-Type: multipart/signed; boundary=nextPart1501013.ZerHIZtkPi; micalg=pgp-sha1; protocol=application/pgp-signature X-Scanned-By: MIMEDefang 2.68 on 10.5.11.26 X-SA-Exim-Connect-IP: 212.227.15.3 X-SA-Exim-Mail-From:rdor...@web.de X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on bokomoko.de X-Spam-Level: X-Spam-Status: No, score=-2.4 required=5.2 tests=FREEMAIL_FROM, RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD,T_FRT_CONTACT autolearn=ham version=3.3.1 Subject:Re: Fwd: Re: [kdepim-users] akonadi_imap_resource segfaults X-SA-Exim-Version: 4.2.1 (built Mon, 22 Mar 2010 06:51:10 +) X-SA-Exim-Scanned: Yes (on bokomoko.de) Hi, there were extensive changes in the IMAP resource in KDE 4.13, so unfortunately the 4.12 crashes have lower priority for us right now. If would be great if you could test with 4.13, see whether you can reproduce the crash there too. Dan On Monday 12 of May 2014 20:44:54 you wrote: Daniel, is there any chance that somebody will look at my bug report in the next weeks? https://bugs.kde.org/show_bug.cgi?id=334098 If not, I will recreate the account, which probably makes the issue go away. Thanks, Rainer Original-Nachricht Return-path:kdepim-users-boun...@kde.org Envelope-to:m...@bokomoko.de Delivery-date: Tue, 29 Apr 2014 23:51:19 +0200 Received: from postbox.kde.org ([46.4.96.248]) by bokomoko.de with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from kdepim-users-boun...@kde.org) id 1WfFvn-0001P2-8L for m...@bokomoko.de; Tue, 29 Apr 2014 23:51:19 +0200 Received: from postbox.kde.org (localhost [IPv6:::1]) by postbox.kde.org (Postfix) with ESMTP id 027FFB37323; Tue, 29 Apr 2014 21:51:10 + (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kde.org; s=default; t=1398808274; bh=0PdjQ/L7IfIMv3QgKqIdyjRx6Ns7K5uiruoi0DodZhM=; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To: Subject:List-Id:List-Unsubscribe:List-Post:List-Help: List-Subscribe:Content-Transfer-Encoding:Content-Type:Sender; b=CV 9PdVEu+OuPqiDRg5wrAbAPPeUrIUmzMNLvaurU2JHQNBcNBbfufivJXXH7pjaTZk85r w6MK2a9r8omgapkodhHqlwVfuJ67xk9RXXrWbgUWW50C4hjbU+J2MG+RufgS8BiH+Oy vT5xAbCCz9JP/GDob8ezr3ZsNL/vTSgG8YU= X-Original-To: kdepim-us...@kde.org Delivered-To: kdepim-us...@localhost.kde.org Received: from bokomoko.de (ns.km21811-02.keymachine.de [87.118.104.111]) by postbox.kde.org (Postfix) with ESMTP id C1FF2B37303 for kdepim-us...@kde.org; Tue, 29 Apr 2014 21:50:37 + (UTC) Received: from p57b4975d.dip0.t-ipconnect.de ([87.180.151.93] helo=[192.168.178.20]) by bokomoko.de with esmtpsa (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from m...@bokomoko.de) id 1WfFv6-0001NZ-RB for kdepim-us...@kde.org; Tue, 29 Apr 2014 23:50:37 +0200 Message-ID: 53601ea2.40...@bokomoko.de Date: Tue, 29 Apr 2014 23:50:26 +0200 From: Rainer Dorsch m...@bokomoko.de User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Icedove/24.4.0 MIME-Version: 1.0 To: kdepim-us...@kde.org References: 535ebb4e.5060...@bokomoko.de 2201994.R9EknOY7Cs@odin
Re: akonadi_imap_resource segfaults
I opened a bug report https://bugs.kde.org/show_bug.cgi?id=334098 Rainer Am 24.04.2014 21:03, schrieb Rainer Dorsch: Hello, I get a segfault on my system with akonadi_imap_resource. I do not remember that I did anything particular change in akonadi, kmail, or my IMAP server, recently. I have not yet tried to setup a new imap account. I would be happy to provide debug information on this issue, if it helps to make akonadi more robust, otherwise I just try to setup a new imap account. I developer information I get in the KDE Crash Handler (do I need to install additional -dbg packages or run with KDE_DEBUG?): Application: bokomoko of type IMAP E-Mail Server (akonadi_imap_resource), signal: Segmentation fault Using host libthread_db library /lib/i386-linux- gnu/i686/cmov/libthread_db.so.1. [Current thread is 1 (Thread 0xb49da740 (LWP 16105))] Thread 2 (Thread 0xb1c5ab40 (LWP 16903)): #0 g_mutex_get_impl (mutex=0xb13004e0) at /build/glib2.0-54cgmj/glib2.0-2.40.0/./glib/gthread-posix.c:119 #1 0xb54dd558 in g_mutex_unlock (mutex=mutex@entry=0xb13004e0) at /build/glib2.0-54cgmj/glib2.0-2.40.0/./glib/gthread-posix.c:228 #2 0xb5497eef in g_main_context_check (context=context@entry=0xb13004e0, max_priority=2147483647, fds=fds@entry=0xb102dce0, n_fds=n_fds@entry=1) at /build/glib2.0-54cgmj/glib2.0-2.40.0/./glib/gmain.c:3642 #3 0xb54984aa in g_main_context_iterate (context=context@entry=0xb13004e0, block=block@entry=1, dispatch=dispatch@entry=1, self=optimized out) at /build/glib2.0-54cgmj/glib2.0-2.40.0/./glib/gmain.c:3731 #4 0xb5498658 in g_main_context_iteration (context=0xb13004e0, may_block=1) at /build/glib2.0-54cgmj/glib2.0-2.40.0/./glib/gmain.c:3795 #5 0xb733777f in QEventDispatcherGlib::processEvents (this=0xb1300468, flags=...) at kernel/qeventdispatcher_glib.cpp:427 #6 0xb7306503 in QEventLoop::processEvents (this=this@entry=0xb1c5a288, flags=...) at kernel/qeventloop.cpp:149 #7 0xb7306829 in QEventLoop::exec (this=this@entry=0xb1c5a288, flags=...) at kernel/qeventloop.cpp:204 #8 0xb71f241d in QThread::exec (this=this@entry=0xa0104d8) at thread/qthread.cpp:537 #9 0xb71f256b in QThread::run (this=0xa0104d8) at thread/qthread.cpp:604 #10 0xb71f4daf in QThreadPrivate::start (arg=0xa0104d8) at thread/qthread_unix.cpp:349 #11 0xb55cded9 in start_thread (arg=0xb1c5ab40) at pthread_create.c:312 #12 0xb577726e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:129 Thread 1 (Thread 0xb49da740 (LWP 16105)): [KCrash Handler] #7 0x0808d59e in ?? () #8 0x0808dbd3 in ?? () #9 0xb731cd55 in QMetaObject::activate (sender=sender@entry=0x9fd5f00, m=m@entry=0xb5bf44ac KJob::staticMetaObject, local_signal_index=local_signal_index@entry=3, argv=argv@entry=0xbfd67a28) at kernel/qobject.cpp:3539 #10 0xb5a4f675 in KJob::result (this=this@entry=0x9fd5f00, _t1=_t1@entry=0x9fd5f00) at ./kjob.moc:207 #11 0xb5a4f6c2 in KJob::emitResult (this=0x9fd5f00) at ../../kdecore/jobs/kjob.cpp:318 #12 0xb653c42e in KIMAP::Job::handleErrorReplies(KIMAP::Message const) () from /usr/lib/libkimap.so.4 #13 0xb6561989 in KIMAP::SearchJob::handleResponse(KIMAP::Message const) () from /usr/lib/libkimap.so.4 #14 0xb65552f6 in KIMAP::SessionPrivate::responseReceived(KIMAP::Message const) () from /usr/lib/libkimap.so.4 #15 0xb6557d6b in ?? () from /usr/lib/libkimap.so.4 #16 0xb73194ea in QMetaCallEvent::placeMetaCall (this=0xb1040d30, object=0xa066308) at kernel/qobject.cpp:524 #17 0xb73213bb in QObject::event (this=0xa066308, e=0xb1040d30) at kernel/qobject.cpp:1194 #18 0xb68128a4 in QApplicationPrivate::notify_helper (this=0x9ed8b40, receiver=0xa066308, e=0xb1040d30) at kernel/qapplication.cpp:4567 #19 0xb68193a3 in QApplication::notify (this=0xbfd68274, receiver=receiver@entry=0xa066308, e=e@entry=0xb1040d30) at kernel/qapplication.cpp:4353 #20 0xb5de7074 in KApplication::notify (this=0xbfd68274, receiver=0xa066308, event=0xb1040d30) at ../../kdeui/kernel/kapplication.cpp:311 #21 0xb7307b4a in QCoreApplication::notifyInternal (this=0xbfd68274, receiver=receiver@entry=0xa066308, event=event@entry=0xb1040d30) at kernel/qcoreapplication.cpp:953 #22 0xb730b405 in sendEvent (event=0xb1040d30, receiver=0xa066308) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #23 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x9ea3280) at kernel/qcoreapplication.cpp:1577 #24 0xb730b92c in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1470 #25 0xb7337f8e in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236 #26 postEventSourceDispatch (s=s@entry=0x9ec5330) at kernel/qeventdispatcher_glib.cpp:280 #27 0xb5498313 in g_main_dispatch (context=0x9ed8c50, context@entry=0x9ec5330) at /build/glib2.0-54cgmj/glib2.0-2.40.0/./glib/gmain.c:3064 #28 g_main_context_dispatch (context=context@entry=0x9ed8c50) at /build/glib2.0-54cgmj/glib2.0-2.40.0/./glib
akonadi_imap_resource segfaults
=0x9ed8c50, block=block@entry=1, dispatch=dispatch@entry=1, self=optimized out) at /build/glib2.0-54cgmj/glib2.0-2.40.0/./glib/gmain.c:3734 #30 0xb5498658 in g_main_context_iteration (context=0x9ed8c50, may_block=1) at /build/glib2.0-54cgmj/glib2.0-2.40.0/./glib/gmain.c:3795 #31 0xb733775f in QEventDispatcherGlib::processEvents (this=this@entry=0x9ea3dc8, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #32 0xb68c3dde in QGuiEventDispatcherGlib::processEvents (this=0x9ea3dc8, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #33 0xb7306503 in QEventLoop::processEvents (this=this@entry=0xbfd681e8, flags=...) at kernel/qeventloop.cpp:149 #34 0xb7306829 in QEventLoop::exec (this=this@entry=0xbfd681e8, flags=...) at kernel/qeventloop.cpp:204 #35 0xb730c61e in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1225 #36 0xb6810d34 in QApplication::exec () at kernel/qapplication.cpp:3828 #37 0xb763f158 in Akonadi::ResourceBase::init(Akonadi::ResourceBase*) () from /usr/lib/libakonadi-kde.so.4 #38 0x0806347d in _start () Thanks, Rainer -- Rainer Dorsch http://bokomoko.de/ -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/2104177.CLW12OMrjI@blackbox
Re: kmix has weired output device
On Sunday 23 March 2014 15:00:46 Lisandro Damián Nicanor Pérez Meyer wrote: On Sunday 23 March 2014 15:41:14 Rainer Dorsch wrote: Hello, when klick on the kmix icon in the systray, I get which looks ok at first glance. Muting the USB Headset does not work though. Checking carefully reveals that above the USB headset playback device is a mono device. If I open the Mixer with the botton above, I get the USB headset stereo device. Muting that works nicely (but seems to be completely unrelated to the mono device). Does anybody know, why the USB headset mono device gets displayed in the first place? Many thanks, Rainer Sounds like you have pulseaudio running. Yes, that is correct. But is that not supposed to work? What should I use instead? Thanks, Rainer -- Rainer Dorsch http://bokomoko.de/ -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1455714.G3vLfH0d7m@blackbox
Is Search Messages in IMAP Mailbox Broken for Everybody?
Hello, I am just curious if Search Messages in IMAP Mailboxes is broken for all kmail users due to https://bugs.kde.org/show_bug.cgi?id=281227 or if it is working for most of the users and only few are affected by SQL query errors: akonadi_nepomuk_feeder(32182) ItemQueue::fetchJobResult: Not all items were fetched: 0 100 akonadi_nepomuk_feeder(32182) ItemQueue::fetchJobResult: Not all items were fetched: 90 100 Error during executing query INSERT INTO CollectionTable (remoteId, name, parentId, resourceId, queryString, queryLanguage, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6) : Duplicate entry '1-Last Search' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement Many thanks, Rainer -- Rainer Dorsch http://bokomoko.de/ -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2749753.hsncAMG4eg@blackbox
Re: What happened to rekonq?
On Tuesday 03 December 2013 22:30:56 Rainer Dorsch wrote: On Tuesday 03 December 2013 22:25:51 Rainer Dorsch wrote: I build my own version of rekonq and 2.4.0 is the most stable version I every had. I just copied to debian dir for building, i.e. I did not really put work into it. I forgot the link, if somebody wants to make us of it: http://bokomoko.de/~rd/rekonq_2.4.0-1_i386.deb (I know it is a very minor contribution, compared to what some of you do). I build the new upstream release: http://bokomoko.de/~rd/rekonq/rekonq_2.4.2-1_i386.deb Note, this does not address the unmaintained qtwebkit issue discussed before. Rainer -- Rainer Dorsch http://bokomoko.de/ -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1656118.ITSoE7DMrQ@blackbox
Re: What happened to rekonq?
On Sunday 19 January 2014 19:13:39 Martin Steigerwald wrote: Am Sonntag, 19. Januar 2014, 16:06:26 schrieb Rainer Dorsch: On Tuesday 03 December 2013 22:30:56 Rainer Dorsch wrote: On Tuesday 03 December 2013 22:25:51 Rainer Dorsch wrote: I build my own version of rekonq and 2.4.0 is the most stable version I every had. I just copied to debian dir for building, i.e. I did not really put work into it. I forgot the link, if somebody wants to make us of it: http://bokomoko.de/~rd/rekonq_2.4.0-1_i386.deb (I know it is a very minor contribution, compared to what some of you do). I build the new upstream release: http://bokomoko.de/~rd/rekonq/rekonq_2.4.2-1_i386.deb Note, this does not address the unmaintained qtwebkit issue discussed before. Thanks. Please share your source package as well. I want to build it for 64-Bit. Aside from that with copyleft licenses its always good to upload the sources as well. I just rebuilt with the debian dir from the last Debian rekonq package the upstream sources. For completeness I uploaded everything to http://bokomoko.de/~rd/rekonq/2.4.2 Rainer -- Rainer Dorsch http://bokomoko.de/ -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1975593.ioIlDFv9Xy@blackbox
Re: Login failed, server replied: A000003 NO Maximum number of connections from user+IP exceeded ( mail_max_userip_connections )
On Tuesday 12 November 2013 22:40:00 Martin Steigerwald wrote: Am Dienstag, 12. November 2013, 22:21:17 schrieb Rainer Dorsch: On Sunday 10 November 2013 14:10:56 Martin Steigerwald wrote: Am Sonntag, 10. November 2013, 13:58:49 schrieben Sie: Am Sonntag 10.11.2013, 11:20:33 schrieb Martin Steigerwald: Note that it may not be actually a crashing resource, maybe just lots of new connections, would be nice if you can find out whether you akonadi imap resource gets restarted all the time (changing PID quickly) or its just new connection attempt as I could prove. Wouldn't there be a popup notification for crashed akonadi resources? I specifically remember one time when there were no popups but something akonadi-related kept downloading a couple hundred KB/s from my university's mail server. Re-starting akonadi didn't fix this, but stopping it ended the download. (And no, that wasn't a huge email/amount of emails being downloaded. In fact, there were no new emails.) OTOH, I've also frequently had the resource crashed notification spam fill up my screen in 4.10, but haven't seen it in a while. I am not sure. As described in bug report I saw a hint that akinadi pop resources crashed. But I don´t know how often. Maybe its just reconnection attempts. watch -n1 ps aux | grep akonadi may give information about how PIDs change... I didn´t do this back then and just watched port numbers changes with the netstat example I provided in bug report. Hi Martin, I just hit the problem again. PIDs are stable and I get lots of login failed messages. Restarting dovecot cures the problem. On the server side, I get lots of entries like this: Nov 12 22:16:49 bokomoko dovecot: imap-login: Login: user=user, method=PLAIN, rip=87.180.155.148, lip=aaa.bbb.ccc.ddd, TLS Nov 12 22:16:49 bokomoko dovecot: imap-login: Disconnected (no auth attempts): rip=87.180.155.148, lip=aaa.bbb.ccc.ddd, TLS: Disconnected Thats good information to add to bug report. Somewhere I read a hint it might be related to some TLS/SSL negotiation issue. Maybe it was in one of the the two bug reports. I checked my server settings last week and changed in /etc/dovecot/dovecot.conf 575c575 #mail_max_userip_connections = 10 --- mail_max_userip_connections = 30 The problem did not reappear since then. Is akonadi opening more parallel connections now? Is that expected? Rainer PS: If others have similar issues on virtual servers: watch out for the numfile limit on the server, this limits the number you can specify. -- Rainer Dorsch Lärchenstr. 6 D-72135 Dettenhausen 07157-734133 email: rdor...@web.de jabber: rdor...@jabber.org GPG Fingerprint: 5E6C 4AF9 363C 97A6 F820 C2E6 8CE0 5F33 07F3 EDC0 Full GPG key: http://pgp.mit.edu/ signature.asc Description: This is a digitally signed message part.
Re: What happened to rekonq?
On Monday 02 December 2013 21:33:50 Sune Vuorela wrote: On 2013-12-02, Martin Steigerwald mar...@lichtvoll.de wrote: What is the oppinion of the Debian Qt/KDE team on this? I don't think the Debian Qt/KDE team has a opinion. Debian Qt/KDE team maintains QtWebkit, and the kpart-webkit besides khtml. I also maintain Arora. I have no plans to work on rekonq but I also don't have any plans to work on it. Felix was looking at taking over Rekonq but his conclusion was as the bug says. I build my own version of rekonq and 2.4.0 is the most stable version I every had. I just copied to debian dir for building, i.e. I did not really put work into it. The author of rekonq recommends the latest qtwebkit release. People reported, in this 40 days since rekonq 2.3.0 release, a lot of crash bugs that can be fixed just upgrading from QtWebKit 2.3.0 to QtWebKit 2.3.1. http://adjamblog.wordpress.com/2013/06/23/rekonq-2-3-1/ It is sad, that we have in sid only an outdated release rd@blackbox:~/SW.nobackup$ apt-cache policy libqtwebkit4 libqtwebkit4: Installiert: 2.2.1-7 Installationskandidat: 2.2.1-7 Versionstabelle: *** 2.2.1-7 0 600 http://ftp-stud.fht-esslingen.de/debian/ jessie/main i386 Packages 300 http://ftp-stud.fht-esslingen.de/debian/ sid/main i386 Packages 100 /var/lib/dpkg/status 2.2.1-5 0 500 http://ftp-stud.fht-esslingen.de/debian/ wheezy/main i386 Packages rd@blackbox:~/SW.nobackup$ *and* there is with Jose a volunteer who would want to work on qtwebkit. I keep hoping that you bring enough (non-technical skills) to get your dispute resolved...with a better result for Debian. Kind regards Rainer -- Rainer Dorsch http://bokomoko.de/ -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4563618.sWVI1cEK9F@blackbox
Re: What happened to rekonq?
On Tuesday 03 December 2013 22:25:51 Rainer Dorsch wrote: I build my own version of rekonq and 2.4.0 is the most stable version I every had. I just copied to debian dir for building, i.e. I did not really put work into it. I forgot the link, if somebody wants to make us of it: http://bokomoko.de/~rd/rekonq_2.4.0-1_i386.deb (I know it is a very minor contribution, compared to what some of you do). Rainer -- Rainer Dorsch http://bokomoko.de/ -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/15951264.3qCFJOLpTg@blackbox
Kmail address completion from addressbook
Hello, kmail address completion from my addressbook does not work anymore. I can though select every address through the select button. I see my addressbooks in the Kmail Settings for Composer in the completion order dialog. Does address completion from addressbook work for you? If yes, do you have any idea, what I could check to get it working again? Thanks, Rainer -- Rainer Dorsch http://bokomoko.de/ -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2833491.390rceBOAK@blackbox
Re: Login failed, server replied: A000003 NO Maximum number of connections from user+IP exceeded ( mail_max_userip_connections )
On Tuesday 12 November 2013 22:40:00 Martin Steigerwald wrote: Thats good information to add to bug report. Somewhere I read a hint it might be related to some TLS/SSL negotiation issue. Maybe it was in one of the the two bug reports. Another data point: typically the problem occurs right after loginusually not when getting out of suspend. Rainer -- Rainer Dorsch http://bokomoko.de/ -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2287699.vI38A1iXS7@blackbox
Re: Login failed, server replied: A000003 NO Maximum number of connections from user+IP exceeded ( mail_max_userip_connections )
On Sunday 10 November 2013 14:10:56 Martin Steigerwald wrote: Am Sonntag, 10. November 2013, 13:58:49 schrieben Sie: Am Sonntag 10.11.2013, 11:20:33 schrieb Martin Steigerwald: Note that it may not be actually a crashing resource, maybe just lots of new connections, would be nice if you can find out whether you akonadi imap resource gets restarted all the time (changing PID quickly) or its just new connection attempt as I could prove. Wouldn't there be a popup notification for crashed akonadi resources? I specifically remember one time when there were no popups but something akonadi-related kept downloading a couple hundred KB/s from my university's mail server. Re-starting akonadi didn't fix this, but stopping it ended the download. (And no, that wasn't a huge email/amount of emails being downloaded. In fact, there were no new emails.) OTOH, I've also frequently had the resource crashed notification spam fill up my screen in 4.10, but haven't seen it in a while. I am not sure. As described in bug report I saw a hint that akinadi pop resources crashed. But I don´t know how often. Maybe its just reconnection attempts. watch -n1 ps aux | grep akonadi may give information about how PIDs change... I didn´t do this back then and just watched port numbers changes with the netstat example I provided in bug report. Hi Martin, I just hit the problem again. PIDs are stable and I get lots of login failed messages. Restarting dovecot cures the problem. On the server side, I get lots of entries like this: Nov 12 22:16:49 bokomoko dovecot: imap-login: Login: user=user, method=PLAIN, rip=87.180.155.148, lip=aaa.bbb.ccc.ddd, TLS Nov 12 22:16:49 bokomoko dovecot: imap-login: Disconnected (no auth attempts): rip=87.180.155.148, lip=aaa.bbb.ccc.ddd, TLS: Disconnected Nov 12 22:16:49 bokomoko dovecot: IMAP(user): Disconnected: Logged out bytes=53/709 Nov 12 22:16:50 bokomoko dovecot: imap-login: Disconnected (no auth attempts): rip=87.180.155.148, lip=aaa.bbb.ccc.ddd, TLS: Disconnected Nov 12 22:16:50 bokomoko dovecot: imap-login: Login: user=user, method=PLAIN, rip=87.180.155.148, lip=aaa.bbb.ccc.ddd, TLS Nov 12 22:16:50 bokomoko dovecot: imap-login: Disconnected (no auth attempts): rip=87.180.155.148, lip=aaa.bbb.ccc.ddd, TLS: Disconnected Nov 12 22:16:50 bokomoko dovecot: IMAP(user): Disconnected: Logged out bytes=53/709 Nov 12 22:16:50 bokomoko dovecot: imap-login: Disconnected (no auth attempts): rip=87.180.155.148, lip=aaa.bbb.ccc.ddd, TLS: Disconnected Nov 12 22:16:50 bokomoko dovecot: imap-login: Login: user=user, method=PLAIN, rip=87.180.155.148, lip=aaa.bbb.ccc.ddd, TLS Nov 12 22:16:51 bokomoko dovecot: imap-login: Disconnected (no auth attempts): rip=87.180.155.148, lip=aaa.bbb.ccc.ddd, TLS: Disconnected Nov 12 22:16:51 bokomoko dovecot: IMAP(user): Disconnected: Logged out bytes=53/709 Nov 12 22:16:51 bokomoko dovecot: imap-login: Disconnected (no auth attempts): rip=87.180.155.148, lip=aaa.bbb.ccc.ddd, TLS: Disconnected Nov 12 22:16:51 bokomoko dovecot: imap-login: Disconnected (no auth attempts): rip=87.180.155.148, lip=aaa.bbb.ccc.ddd, TLS: Disconnected Nov 12 22:16:51 bokomoko dovecot: imap-login: Login: user=user, method=PLAIN, rip=87.180.155.148, lip=aaa.bbb.ccc.ddd, TLS Nov 12 22:16:51 bokomoko dovecot: imap-login: Disconnected (no auth attempts): rip=87.180.155.148, lip=aaa.bbb.ccc.ddd, TLS: Disconnected Nov 12 22:16:51 bokomoko dovecot: IMAP(user): Disconnected: Logged out bytes=53/709 Nov 12 22:16:52 bokomoko dovecot: imap-login: Disconnected (no auth attempts): rip=87.180.155.148, lip=aaa.bbb.ccc.ddd, TLS: Disconnected Nov 12 22:16:52 bokomoko dovecot: imap-login: Login: user=user, method=PLAIN, rip=87.180.155.148, lip=aaa.bbb.ccc.ddd, TLS Nov 12 22:16:52 bokomoko dovecot: imap-login: Disconnected (no auth attempts): rip=87.180.155.148, lip=aaa.bbb.ccc.ddd, TLS: Disconnected Nov 12 22:16:52 bokomoko dovecot: IMAP(user): Disconnected: Logged out bytes=53/709 Nov 12 22:16:52 bokomoko dovecot: imap-login: Disconnected (no auth attempts): rip=87.180.155.148, lip=aaa.bbb.ccc.ddd, TLS: Disconnected Nov 12 22:16:52 bokomoko dovecot: imap-login: Disconnected (no auth attempts): rip=87.180.155.148, lip=aaa.bbb.ccc.ddd, TLS: Disconnected Nov 12 22:16:52 bokomoko dovecot: imap-login: Login: user=user, method=PLAIN, rip=87.180.155.148, lip=aaa.bbb.ccc.ddd, TLS Nov 12 22:16:53 bokomoko dovecot: imap-login: Disconnected (no auth attempts): rip=87.180.155.148, lip=aaa.bbb.ccc.ddd, TLS: Disconnected Rainer -- Rainer Dorsch http://bokomoko.de/ -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1805447.HVslCLAI0d@blackbox
Re: Login failed, server replied: A000003 NO Maximum number of connections from user+IP exceeded ( mail_max_userip_connections )
On Sunday 10 November 2013 11:20:33 Martin Steigerwald wrote: Am Donnerstag, 7. November 2013, 11:41:13 schrieb Reinhold Rumberger: Am Mittwoch 06.11.2013, 23:24:58 schrieb Rainer Dorsch: Hello, after upgrading from 4.10.5 to 4.11.2, I regularly get from kmail2 this message: The server for account boko refused the supplied username and password. Do you want to go to the settings, have another attempt at logging in, or do nothing? Login failed, server replied: A03 NO Maximum number of connections from user+IP exceeded ( mail_max_userip_connections ) Restarting dovecot on the server side fixes the problem. Does akonadi/kmail have some connection leaks, i.e. is opening but not properly closing connections? Shortly after I switched to KMail2, my university account was disabled with a comment from the admin that my mail client was spamming connections (some hundreds per second). Since then I don't trust KMail2 with my university email anymore, so I don't know whether this still happens. Interesting. I have seen something similar and am now using Icedove at work due to that: I was tempted to do the same, if the issue becomes too painful. But currently it happens rarely. Bug 322199 - akonadi_imap spams perdition log when two clients are active and gets restarted all the time https://bugs.kde.org/322199 I enabled logging on the server side (dovecot from squeeze). Related to that: Bug 322200 - limit restarts of crashing resources https://bugs.kde.org/show_bug.cgi?id=322200 Please give feedback to the bug report above. So far devs may the thinking it just happens for me. I offered to provide information, if solicited to tell what they need. Also I subscribed to the issues. Note that it may not be actually a crashing resource, maybe just lots of new connections, would be nice if you can find out whether you akonadi imap resource gets restarted all the time (changing PID quickly) or its just new connection attempt as I could prove. Can you provide a string to grep for? I am reluctant to try this on our infrastructure again, since it almost ate our IMAP proxy server by spamming it so badly that log filled up available disk space. I have no problem here to test somewhat as long as it does not become too painful or lose data... Rainer -- Rainer Dorsch Lärchenstr. 6 D-72135 Dettenhausen 07157-734133 email: rdor...@web.de jabber: rdor...@jabber.org GPG Fingerprint: 5E6C 4AF9 363C 97A6 F820 C2E6 8CE0 5F33 07F3 EDC0 Full GPG key: http://pgp.mit.edu/ signature.asc Description: This is a digitally signed message part.
Can not get search result. Unable to create persistent search
Hello, when I start issuing a Find messages, enter a search expression and then start search, I get an error message, saying Can not get search result. Unable to create persistent search Does anybody know what that is? That is nothing new, I did not use search before, because nepomuk indexing was too slow. Many thanks, Rainer -- Rainer Dorsch http://bokomoko.de/ -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/3167989.6zmp0xICmZ@blackbox
Re: Plasma Desktop Shell crashes after upgrade to 4.11.2
On Tuesday 05 November 2013 23:42:08 Lisandro Damián Nicanor Pérez Meyer wrote: On Sunday 03 November 2013 21:59:51 Rainer Dorsch wrote: Hello, I upgraded to 4.11.2 today. Right after login I see a plasma desktop shell crash: http://pastebin.kde.org/p5g9moosq When I start with a test user from a clean account (i.e. no .kde directory) I do not see the crash, i.e. it is likely to have something todo with my .kde directory. Cleaning up my plasma configuration fixed the problem $ kquitapp plasma-desktop $ sleep 20s $ mkdir -p $HOME/plasma-config/ $ mv $(kde4-config --localprefix)/share/config/plasma-desktop* $HOME/plasma- config/ If anybody is interested in my plasma-config, please let me know. Do you have an image slideshow on your plasma desktop? No, at least not intentionally. Rainer -- Rainer Dorsch http://bokomoko.de/ -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2280853.58mBIAaYF2@blackbox
Re: kdm Configuration
Maximilliano, thank you for your response, that was very helpful. Am Mittwoch 30 Oktober 2013, 13:13:38 schrieb Maximiliano Curia: Rainer Dorsch m...@bokomoko.de wrote: I am trying to configure kdm to show a user list. But no matter what I do, I cannot get rid of the default debian theme without the user list. I added: root@Silberkiste:~# cat /etc/default/kdm.d/90_local LogoArea=Clock UseTheme=false UserList=true Those values are not supported by the script that updates the kdmrc file (check /etc/init.d/kdm script). I'll say you should avoid using /etc/default/kdm.d/* and modify /etc/kde4/kdmrc directly. With tracing kdm, I managed to get the settings I need. It would have been much more intuitive, if I /etc/default/kdm.d would overwrite all fields in kdmrc and not only a subset (which seem to have also a different uppercase/lowercase convention(?)). Here are the notes I took, in case they are useful for somebody else: List All Users on Login Screen == Disabling the theme is required to show user list rd@Silberkiste:/etc/kde4/kdm$ diff kdmrc.orig kdmrc 328c328,329 LogoArea=Logo --- # LogoArea=Logo LogoArea=Clock 378a380 UserList=true rd@Silberkiste:/etc/kde4/kdm$ diff backgroundrc.orig backgroundrc 16c16 Wallpaper=stripes.png --- Wallpaper=/usr/share/wallpapers/joy/contents/images/1920x1080.png rd@Silberkiste:/etc/kde4/kdm$ cat /etc/default/kdm.d/90_local USETHEME=false rd@Silberkiste:/etc/kde4/kdm$ Disabling USETHEME in kdmrc would be overwritten by /etc/default/kdm.d/10_desktop-base Thanks, Rainer -- Rainer Dorsch -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201311021205.39886...@bokomoko.de
kdm Configuration
Hello, I am trying to configure kdm to show a user list. But no matter what I do, I cannot get rid of the default debian theme without the user list. I added: root@Silberkiste:~# cat /etc/default/kdm.d/90_local LogoArea=Clock UseTheme=false UserList=true root@Silberkiste:~# And this should be the last configuration executed root@Silberkiste:~# ls -l /etc/default/kdm.d/ insgesamt 8 -rw-r--r-- 1 root root 123 Aug 23 2012 10_desktop-base -rw-r--r-- 1 root root 51 Okt 5 12:31 90_local root@Silberkiste:~# Is there a way I can check what is the full configuration kdm sees out of the various configuration files in the system (and ideally where the individual parts come from)? Many thanks, Rainer -- Rainer Dorsch -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201310051240.55799...@bokomoko.de
Bug#712458: kmail: About Dialog crashes KMail
Package: kmail Version: 4:4.10.4-1 Severity: normal Dear Maintainer, * What led up to the situation? Opening Help - About KMail * What exactly did you do (or not do) that was effective (or ineffective)? Right after starting KMail * What was the outcome of this action? KMail crashes When starting from cmd line, I get QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. Hspell: can't open /usr/share/hspell/hebrew.wgz.sizes. rd@blackbox:~/Disk/SW.backup/n900$ Plugin paths: (/usr/lib/i386-linux-gnu/qt4/plugins, /home/rd/.kde/lib/, /usr/lib/) Trying to load Attica plugin: /usr/lib/i386-linux-gnu/qt4/plugins/attica_kde.so Trying to load Attica plugin: /home/rd/.kde/lib//attica_kde.so Trying to load Attica plugin: /usr/lib//attica_kde.so Using Attica with KDE support *** KMail got signal 11 (Exiting) *** Dead letters dumped. KCrash: Application 'kmail' crashing... KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit sock_file=/home/rd/.kde/socket-blackbox/kdeinit4__0 * What outcome did you expect instead? 4.10.4 :-) -- System Information: Debian Release: 7.1 APT prefers stable APT policy: (500, 'stable'), (400, 'testing'), (300, 'unstable'), (250, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages kmail depends on: ii kde-runtime 4:4.10.4-1 ii kdepim-runtime4:4.10.4-1 ii kdepimlibs-kio-plugins4:4.10.4-1 ii libakonadi-contact4 4:4.10.4-1 ii libakonadi-kde4 4:4.10.4-1 ii libakonadi-kmime4 4:4.10.4-1 ii libakonadiprotocolinternals1 1.9.2-2 ii libc6 2.17-3 ii libcalendarsupport4 4:4.10.4-1 ii libgcc1 1:4.7.2-5 ii libgpgme++2 4:4.10.2-2 ii libincidenceeditorsng44:4.10.4-1 ii libkabc4 4:4.10.4-1 ii libkcalcore4 4:4.10.4-1 ii libkcalutils4 4:4.10.4-1 ii libkcmutils4 4:4.10.4-1 ii libkdecore5 4:4.10.4-1 ii libkdepim44:4.10.4-1 ii libkdeui5 4:4.10.4-1 ii libkio5 4:4.10.4-1 ii libkleo4 4:4.10.4-1 ii libkmime4 4:4.10.4-1 ii libknotifyconfig4 4:4.10.4-1 ii libkontactinterface4 4:4.10.4-1 ii libkparts44:4.10.4-1 ii libkpgp4 4:4.10.4-1 ii libkpimidentities44:4.10.4-1 ii libkpimtextedit4 4:4.10.4-1 ii libkpimutils4 4:4.10.4-1 ii libkprintutils4 4:4.10.4-1 ii libksieveui4 4:4.10.4-1 ii libktnef4 4:4.10.4-1 ii libmailcommon44:4.10.4-1 ii libmailimporter4 4:4.10.4-1 ii libmailtransport4 4:4.10.4-1 ii libmessagecomposer4 4:4.10.4-1 ii libmessagecore4 4:4.10.4-1 ii libmessagelist4 4:4.10.4-1 ii libmessageviewer4 4:4.10.4-1 ii libnepomukcore4 4:4.10.4-1 ii libpimcommon4 4:4.10.4-1 ii libqt4-dbus 4:4.8.4+dfsg-4 ii libqt4-network4:4.8.4+dfsg-4 ii libqt4-xml4:4.8.4+dfsg-4 ii libqtcore44:4.8.4+dfsg-4 ii libqtgui4 4:4.8.4+dfsg-4 ii libqtwebkit4 2.2.1-5 ii libsolid4 4:4.10.4-1 ii libsoprano4 2.9.2+dfsg.1-1 ii libstdc++64.7.2-5 ii libtemplateparser44:4.10.4-1 ii perl 5.14.2-21 Versions of packages kmail recommends: ii gnupg-agent 2.0.19-2 ii gnupg22.0.19-2 ii pinentry-gtk2 [pinentry-x11] 0.8.1-1 ii pinentry-qt4 [pinentry-x11] 0.8.1-1 Versions of packages kmail suggests: pn clamav | f-prot-installernone ii kaddressbook 4:4.10.4-1 ii kleopatra4:4.10.4-1 ii procmail 3.22-20 pn spamassassin | bogofilter | annoyance-filter | spambayes | bsfi none -- no debconf information -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130616074356.6681.69411.reportbug@localhost.localdomain
Bug#712476: virtuoso-opensource-6.1: virtuoso-t uses almost 100% CPU over 100 minutes now
Package: virtuoso-opensource-6.1 Version: 6.1.6+dfsg-2 Severity: normal Dear Maintainer, * What led up to the situation? Started file indexing in desktop search * What exactly did you do (or not do) that was effective (or ineffective)? see above * What was the outcome of this action? virtuoso-t uses almost 100% CPU over a long period of time. In the beginning I saw nepomukindexer with very high load in parallel (almost 100% as well). Now I see nepomukservices with a load of roughly 5%. If that is the expected behaviour for some time, I can live with that, but I rather thing virtuoso-t/nepomuk got stuck. * What outcome did you expect instead? CPU load reduction after a a few minutes or at least a way to see the progress which has been made. I am disabling desktop search again, but I am happy to provide more data if needed. -- System Information: Debian Release: 7.1 APT prefers stable APT policy: (500, 'stable'), (400, 'testing'), (300, 'unstable'), (250, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages virtuoso-opensource-6.1 depends on: ii debconf [debconf-2.0] 1.5.49 ii dpkg1.16.10 ii libc6 2.17-3 ii libexpat1 2.1.0-1 ii libgomp14.7.2-5 ii libmagickcore5 8:6.7.7.10-5 ii libmagickwand5 8:6.7.7.10-5 ii libpcre31:8.30-5 ii libvirtodbc06.1.6+dfsg-2 ii libwbxml2-0 0.10.7-1 ii multiarch-support 2.13-38 ii virtuoso-opensource-6.1-bin 6.1.6+dfsg-2 ii virtuoso-opensource-6.1-common 6.1.6+dfsg-2 virtuoso-opensource-6.1 recommends no packages. virtuoso-opensource-6.1 suggests no packages. -- debconf information: virtuoso-opensource-6.1/db-server-port: virtuoso-opensource-6.1/register-odbc-dsn: true virtuoso-opensource/primary-server: virtuoso-opensource-6.1 virtuoso-opensource-6.1/password-mismatch: virtuoso-opensource-6.1/note-disabled: virtuoso-opensource-6.1/http-server-port: 8890 virtuoso-opensource-6.1/error-setting-password: virtuoso-opensource-6.1/check-remove-databases: false -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130616095352.18561.49635.reportbug@localhost.localdomain
Re: Creating Activities does not work anymore
Diane, thanks for your reply. On Sunday 14 April 2013 10:39:51 Diane Trout wrote: Painter not active sounds like its trying to render something and failing for some reason. So some guesses of what to try : Under system settings. configure desktop effects, advanced, could you try some different compositing type / qt graphics system settings? Mine is set to Compositing Type: opengl Qt Graphics System: raster same here. You might need something different. I'm not sure but It might be worth turning off some of desktop effects and trying as well. I do not turn them on. Also it's probably worth checking to make sure kactivitymanagerd is running. ps auxw | grep kactivitymanager Hmmno, that is missing: blackbox:/etc# apt-cache policy libkactivities-bin libkactivities-bin: Installiert: (keine) Installationskandidat: 4:4.8.4-1 Versionstabelle: 4:4.10.2-1 0 200 http://ftp-stud.fht-esslingen.de/debian/ experimental/main i386 Packages 4:4.9.5-0r0 0 100 http://qt-kde.debian.net/debian/ experimental-snapshots/main i386 Packages 4:4.8.4-1 0 500 http://ftp-stud.fht-esslingen.de/debian/ wheezy/main i386 Packages 300 http://ftp-stud.fht-esslingen.de/debian/ sid/main i386 Packages blackbox:/etc# blackbox:/etc# apt-cache policy kde-full kde-full: Installiert: 5:78 Installationskandidat: 5:78 Versionstabelle: *** 5:78 0 200 http://ftp-stud.fht-esslingen.de/debian/ experimental/main i386 Packages 100 /var/lib/dpkg/status 5:78~pre2 0 100 http://qt-kde.debian.net/debian/ experimental-snapshots/main i386 Packages 5:77+deb7u1 0 300 http://ftp-stud.fht-esslingen.de/debian/ sid/main i386 Packages 5:77 0 500 http://ftp-stud.fht-esslingen.de/debian/ wheezy/main i386 Packages blackbox:/etc# Is it expected that I can have kde-full but miss the kactivitymanager? Thanks, Rainer On Sunday, April 14, 2013 10:16:47 Rainer Dorsch wrote: Hi Diane, that is exactly, what I do, except that the Looked at empty desktop does not happen. Here are the .xsession-errors which showed up during this process...quite a number of them, but I do not really understand what they mean. ActivityManager::focusInEvent() ControllerWindow::resizeEvent QSize(-1, -1) QPainter::begin: Paint device returned engine == 0, type: 2 QPainter::setCompositionMode: Painter not active QPainter::end: Painter not active, aborted QPainter::begin: Paint device returned engine == 0, type: 2 QPainter::setCompositionMode: Painter not active QPainter::end: Painter not active, aborted QPainter::begin: Paint device returned engine == 0, type: 2 QPainter::setCompositionMode: Painter not active -- Rainer Dorsch http://bokomoko.de/ -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2322353.jPsgu7lxbF@blackbox
