openSUSE KDE August 2017

kde@lists.opensuse.org

18 participants
11 discussions

[opensuse-kde] Temporary migration to Kmail3 as work around
by stakanov 25 Sep '17

25 Sep '17

This is not a polemic post but driven by sheer necessity. Having Leap 42.3 and given the current situation of Kontact/kmail I have to find a temporary workaround to avoid the use of akonadi (given the daily or hourly crashes, compromised indexes, filter failure, and at the end as it seems even overheat shutdowns due to zombie processes and spontaneous system crashes. I thought at Kmail3 (that was the only program that never made me loose a mail. a) is it possible to migrate my mail from Kmail5 to Kmail3? What format would I choose for archival in order to be able to import them into kmail3. Thank you. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

2 3

[opensuse-kde] Return of old bugs : kscreen spamming logs
by Bruno Friedmann 27 Aug '17

27 Aug '17

On my TW plasma 5.10x I'm seeing again the same flow of message from kscreen as reported, fixed long ago https://bugs.kde.org/show_bug.cgi?id=361688 I've made stats, I got 2684 message log since midnight (where there around 4 times changes events like monitor going to sleep and so) I have the var echo $QT_LOGGING_RULES kscreen.*=false exported in my bashrc, so I move that to system instead of my user ? If someone has a clue about how can I shut up those messages Aug 27 14:46:41 org.kde.KScreen[1975]: kscreen.xrandr: XRandROutput 547 update Aug 27 14:46:41 org.kde.KScreen[1975]: kscreen.xrandr: m_connected: 0 Aug 27 14:46:41 org.kde.KScreen[1975]: kscreen.xrandr: m_crtc QObject(0x0) Aug 27 14:46:41 org.kde.KScreen[1975]: kscreen.xrandr: CRTC: 0 Aug 27 14:46:41 org.kde.KScreen[1975]: kscreen.xrandr: MODE: 0 Aug 27 14:46:41 org.kde.KScreen[1975]: kscreen.xrandr: Connection: 0 Aug 27 14:46:41 org.kde.KScreen[1975]: kscreen.xrandr: Primary: false Aug 27 14:46:41 org.kde.KScreen[1975]: kscreen.xrandr: Output 547 : connected = true , enabled = false Aug 27 14:46:41 org.kde.KScreen[1975]: kscreen.xrandr: XRandROutput 550 update Aug 27 14:46:41 org.kde.KScreen[1975]: kscreen.xrandr: m_connected: 0 Aug 27 14:46:41 org.kde.KScreen[1975]: kscreen.xrandr: m_crtc XRandRCrtc(0x1c36c80fb0) Aug 27 14:46:41 org.kde.KScreen[1975]: kscreen.xrandr: CRTC: 538 Aug 27 14:46:41 org.kde.KScreen[1975]: kscreen.xrandr: MODE: 551 Aug 27 14:46:41 org.kde.KScreen[1975]: kscreen.xrandr: Connection: 0 Aug 27 14:46:41 org.kde.KScreen[1975]: kscreen.xrandr: Primary: true Aug 27 14:46:41 org.kde.KScreen[1975]: kscreen.xrandr: Output 550 : connected = true , enabled = true Aug 27 14:46:41 org.kde.KScreen[1975]: kscreen.xrandr: XRandROutput 547 update Aug 27 14:46:41 org.kde.KScreen[1975]: kscreen.xrandr: m_connected: 0 Aug 27 14:46:41 org.kde.KScreen[1975]: kscreen.xrandr: m_crtc QObject(0x0) Aug 27 14:46:41 org.kde.KScreen[1975]: kscreen.xrandr: CRTC: 0 Aug 27 14:46:41 org.kde.KScreen[1975]: kscreen.xrandr: MODE: 0 Aug 27 14:46:41 org.kde.KScreen[1975]: kscreen.xrandr: Connection: 0 Aug 27 14:46:41 org.kde.KScreen[1975]: kscreen.xrandr: Primary: false Aug 27 14:46:41 org.kde.KScreen[1975]: kscreen.xrandr: Output 547 : connected = true , enabled = false Aug 27 14:46:41 org.kde.KScreen[1975]: kscreen.xrandr: XRandROutput 550 update Aug 27 14:46:41 org.kde.KScreen[1975]: kscreen.xrandr: m_connected: 0 Aug 27 14:46:41 org.kde.KScreen[1975]: kscreen.xrandr: m_crtc XRandRCrtc(0x1c36c80fb0) Aug 27 14:46:41 org.kde.KScreen[1975]: kscreen.xrandr: CRTC: 538 Aug 27 14:46:41 org.kde.KScreen[1975]: kscreen.xrandr: MODE: 551 Aug 27 14:46:41 org.kde.KScreen[1975]: kscreen.xrandr: Connection: 0 Aug 27 14:46:41 org.kde.KScreen[1975]: kscreen.xrandr: Primary: true Aug 27 14:46:41 org.kde.KScreen[1975]: kscreen.xrandr: Output 550 : connected = true , enabled = true Aug 27 14:46:42 org.kde.KScreen[1975]: kscreen.xrandr: Emitting configChanged() thanks. -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

1 0

[opensuse-kde] RFC: Dropping (for real) KTP from Applications 17.12
by Luca Beltrame 24 Aug '17

24 Aug '17

NOTE: this mail comes from a downstream (distributor / integrator) point of view. Feel free to correct possible errors. Also please try to keep both lists in CC. Hello, a recent message[1] to the release-team mailing list suggested that KDE Telepathy is de facto dead, due to lack of maintenance with the exception of infrequent contributions. Now, the problem seems also to affect the upstream Telepathy project, which is mostly dormant. Recently, a component used by KTP (the Qt bindings for Telepathy) broke with CMake 3.9 (and a fix or a release is not in sight; there has been no significant activity since 2015). At this point, with many parts of the stack that are likely bitrotting, and even a mostly dead upstream, it is the time to wonder whether KTP should be still part of Applications. It was suggested to keep it if it didn't break, but as I mentioned, some dependencies *are* already broken. Therefore, I would suggest for it to be dropped from the next Applications release (17.12). For what it's worth, it's being already dropped from openSUSE Tumbleweed (and the future stable versions as well), unless, of course, the impasse can be solved, but IMO it would just move the line to the next breakage (which is going to happen, sooner or later), [1] https://mail.kde.org/pipermail/release-team/2017-August/010494.html -- Luca Beltrame - KDE Forums team GPG key ID: A29D259B

3 2

[opensuse-kde] KWallet PAM integration in TW
by Fabian Vogt 22 Aug '17

22 Aug '17

Hi, it was a much requested feature to have some better integration of the KWallet PAM module into the system. Until now, it was necessary to add the module manually to the configuration files in /etc/pam.d. To improve the situation, kwallet-pam got some necessary fixes (already upstream in master and backported to 5.10.4) and pam-config gained support for the pam_kwallet5.so module. With the upcoming release of Plasma, 5.10.5, the pam_kwallet package will automatically activate itself when installed. This however means that you *must* remove any manual edits of the PAM configuration beforehand! Otherwise the pam module will be included multiple times during the authentication process, which may work fine in most cases, but can also break the authentication process, resulting in the total inability to login graphically. Please report any bugs or other issues you find. Note that this only applies to Tumbleweed. Cheers, Fabian -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

2 3

[opensuse-kde] Custom patterns for "New File" in plasma
by Efrem Novak 19 Aug '17

19 Aug '17

Hello. Does anyone know how to add custom templates (.ods file for example) to "Create New" in right-click-menu in plasma? Google says that I should place my files in ~/.local/share/templates and /usr/share/templates, but seems like it doesn't work. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

2 2

[opensuse-kde] Strange behavior of akonadictl in Tumbleweed
by Freek de Kruijf 15 Aug '17

15 Aug '17

Since yesterday after the latest update, but I am not sure it has been introduced by the update, I now have a good working KMail with 6 accounts to IMAP servers. Yesterday I had one of these account which was busy to synchronize the wastebasket, but did not finish. I decided to run "akonadictl fsck" and "akonadictl vacuum". The first process finished normal, but the second one did not, even after quite a while waiting. So I aborted that process using ^C. I deleted the account which did not finish the synchronization and created it again. Now I have KMail which seems to be OK. However currently both the above commands give no output at all. I can use "akonadictl stop" and "akonadictl start" even while KMail is active without ill effects. Still these two commands do not seem to do anything. Using another linux account, these commands do give the expected output. Any ideas? -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

3 3

[opensuse-kde] kmail troubling behaviour
by C. Brouerius van Nidek 15 Aug '17

15 Aug '17

After having troubles with the setup I was using daily for over a year I decided to start a new user. Everything wordked out well except kmail. After the initial setup I could not make new folders. After several trialruns I finaly got some new subfolders who were sticking in place. Lookong into the /.local/share directory I discovered that my mail was not found in akonadi_maildir_resource_0 but found its place in the old kind of /.local-mail.directory. I ran akonadictl fsck and got the feeling that also there was no real information about my mail setup. See for yourself. How to get a functioning kmail? ------------------------------------ > akonadictl fsck Looking for resources in the DB not matching a configured resource... Looking for collections not belonging to a valid resource... Checking collection tree consistency... Looking for items not belonging to a valid collection... Looking for item parts not belonging to a valid item... Looking for item flags not belonging to a valid item... Looking for overlapping external parts... Verifying external parts... Found 0 external files. Found 0 external parts. Found no unreferenced external files. Checking size treshold changes... Found 0 parts to be moved to external files Found 0 parts to be moved to database Looking for dirty objects... Collection "Search" (id: 1) has no RID. Found 1 collections without RID. Found 0 items without RID. Found 0 dirty items. Looking for rid-duplicates not matching the content mime-type of the parent collection Checking Birthdays & Anniversaries Checking Local Folders Checking Notes Checking Personal Contacts Checking Search Checking akonadi_ical_resource_0 Checking commics Checking drafts Checking inbox Checking outbox Checking rotzooi??? Checking sent-mail Checking suse Checking susekde Checking suseot Checking templates Checking trash Migrating parts to new cache hierarchy... Consistency check done. ---------------- -- opensuse:tumbleweed:20170810 Qt: 5.9.1 KDE Frameworks: 5.36.0 kf5-config: 1.0 KDE Plasma: 5.10.4 plasmashell 5.10.4 Kernel: 4.11.8-2-default Linux User 183145 working on a Pentium IV . -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

1 0

[opensuse-kde] No Shutdown/reboot Option in Plasma 5.10.4 on latest Tumbleweed
by Stefan Kunze 14 Aug '17

14 Aug '17

Just noticed since yesterday that Plasma does not have a shutdown or reboot option in the Application menu anymore . I only see Lock Logoff Switch User Standby Suspend/Hibernate ( in German Ruhezustand) not sure which is meant To get a Shutdown or Reboot Option without using the terminal I need to log off from the session to go to the Login Manager Screen Question: Was this an intentional design decision ? Or is it a Bug? Thx Stefan -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

4 3

[opensuse-kde] Troubles with a user: KDE presents "dump core" by several processes and X gives strange messages.
by stakanov 11 Aug '17

11 Aug '17

I do not know if a) this is x related b) kde related c) if I should raise a bug? So, I am getting in journalctl -r the following for the 1002 user (called entropia). -- Logs begin at gio 2017-07-27 16:58:32 CEST, end at gio 2017-08-10 10:44:38 CEST. -- ago 10 10:44:38 roadrunner org.kde.kwalletd5[3836]: Migration agent stop. ago 10 10:44:38 roadrunner org.kde.kwalletd5[3836]: old wallets were already migrated ago 10 10:44:38 roadrunner org.kde.kwalletd5[3836]: Migration agent starting... ago 10 10:44:37 roadrunner org.kde.kwalletd5[3836]: The key was found. ago 10 10:44:37 roadrunner org.kde.kwalletd5[3836]: This wallet was encrypted using GPG key with ID "3444252C6A7D1687" ago 10 10:44:28 roadrunner org.kde.kwalletd5[3836]: Wallet new enough, using new hash ago 10 10:44:28 roadrunner org.kde.kwalletd5[3836]: Setting useNewHash to true ago 10 10:44:27 roadrunner org.kde.kwalletd5[3836]: openAsync for ":1.51" ago 10 10:44:27 roadrunner org.kde.kwalletd5[3836]: kwalletd5 started ago 10 10:44:23 roadrunner obexd[4016]: OBEX daemon 5.41 ago 10 10:44:21 roadrunner checkproc[3825]: checkproc: can not get session id for process 3617! ago 10 10:44:21 roadrunner sddm-helper[3784]: Adding cookie to "/home/ entropia/.Xauthority" ago 10 10:44:21 roadrunner systemd[3777]: Startup finished in 21ms. ago 10 10:44:21 roadrunner systemd[3777]: Reached target Default. ago 10 10:44:21 roadrunner systemd[3777]: Reached target Basic System. ago 10 10:44:21 roadrunner systemd[3777]: Reached target Paths. ago 10 10:44:21 roadrunner systemd[3777]: Reached target Timers. ago 10 10:44:21 roadrunner systemd[3777]: Reached target Sockets. ago 10 10:44:08 roadrunner systemd[3560]: pam_unix(systemd-user:session): session closed for user entropia ago 10 10:44:08 roadrunner systemd[3558]: Received SIGRTMIN+24 from PID 3721 (kill). ago 10 10:44:08 roadrunner systemd[3558]: Stopped target Timers. ago 10 10:44:08 roadrunner systemd[3558]: Stopped target Sockets. ago 10 10:44:08 roadrunner systemd[3558]: Stopped target Paths. ago 10 10:44:08 roadrunner systemd[3558]: Stopped target Basic System. ago 10 10:44:08 roadrunner systemd[3558]: Stopped target Default. ago 10 10:44:08 roadrunner systemd[3558]: Starting Exit the Session... ago 10 10:44:08 roadrunner systemd[3558]: Reached target Shutdown. ago 10 10:44:06 roadrunner org.kde.KScreen[3616]: after 196 requests (196 known processed) with 0 events remaining. ago 10 10:44:06 roadrunner org.kde.KScreen[3616]: XIO: fatal IO error 3 (Nessun processo corrisponde) on X server ":2" ago 10 10:44:06 roadrunner org.kde.KScreen[3616]: The X11 connection broke: I/ O error (code 1) ago 10 10:44:05 roadrunner org.kde.kglobalaccel[3616]: The X11 connection broke (error 1). Did the X11 server die? ago 10 10:44:05 roadrunner org.kde.KScreen[3616]: Qt: couldn't get core keyboard device info ago 10 10:44:05 roadrunner org.kde.KScreen[3616]: Qt: failed to retrieve the virtual modifier map from XKB ago 10 10:44:04 roadrunner checkproc[3605]: checkproc: can not get session id for process 3843! ago 10 10:44:04 roadrunner sddm-helper[3564]: Adding cookie to "/home/ entropia/.Xauthority" A part of these problems with this strange process 3843 (how can I find whose process was this, I get the complain only after that the process is gone). ps u 3617 USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND entropia@roadrunner:~> sudo ps u 3617 [sudo] password di root: USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND Any suggestions to find out? I also get the following for this user: Process 4639 (kontact) of user 1002 dumped core. Process 3913 (kded5) of user 1002 dumped core. ago 09 22:17:02 roadrunner systemd-coredump[17629]: Process 17620 (drkonqi) of user 1002 dumped core. ago 09 22:17:02 roadrunner systemd-coredump[17632]: Process 17628 (klauncher) of user 1002 dumped core. Kded5 and launcher give often these coredumps. When this user is open, the temperature of the system rises sometimes from a normal 50-70 C to 99 to 100 C with occasional emergency shutdown. The system also crashes with all users to a black screen and subsequent shutdown in an irregular way. What is seen as a relation is: suspend to ram or powersafe and restart triggers these crashes especially if entropia has kontact running. Although it is a quite violent crash (all users gone in one second) no apparent failure is commented in journalctl when it happens (as it seems. But maybe it is the coredump?). Again a typical expert of journalctl when it happens: ago 06 22:43:09 roadrunner systemd-coredump[12084]: Process 3005 (kded5) of user 1002 dumped core. ago 06 22:42:59 roadrunner systemd-coredump[12093]: Process 12085 (klauncher) of user 1002 dumped core. ago 06 22:42:59 roadrunner systemd-coredump[12083]: Process 12081 (drkonqi) of user 1002 dumped core. ago 06 22:42:56 roadrunner org.kde.kuiserver[2964]: The X11 connection broke (error 1). Did the X11 server die? ago 06 22:42:56 roadrunner org.kde.kwalletd5[2964]: The X11 connection broke (error 1). Did the X11 server die? ago 06 22:42:56 roadrunner org.gtk.vfs.Daemon[2964]: A connection to the bus can't be made ago 06 22:42:56 roadrunner org.gtk.vfs.Daemon[2964]: A connection to the bus can't be made ago 06 22:42:56 roadrunner org.gtk.vfs.Daemon[2964]: A connection to the bus can't be made ago 06 22:42:56 roadrunner org.kde.kglobalaccel[2964]: The X11 connection broke (error 1). Did the X11 server die? ago 06 22:42:56 roadrunner org.kde.KScreen[2964]: The X11 connection broke (error 1). Did the X11 server die? ago 06 22:42:56 roadrunner org.kde.kdeconnect[2964]: The X11 connection broke (error 1). Did the X11 server die? ago 06 22:42:56 roadrunner org.gtk.vfs.Daemon[2964]: A connection to the bus can't be made ago 06 22:42:53 roadrunner org.kde.kdeconnect[2964]: kdeconnect.core: Broadcasting identity packet ago 06 22:42:53 roadrunner org.kde.kdeconnect[2964]: kdeconnect.core: KdeConnect daemon started ago 06 22:42:53 roadrunner org.kde.kdeconnect[2964]: kdeconnect.core: onStart ago 06 22:42:53 roadrunner org.kde.kdeconnect[2964]: kdeconnect.core: KdeConnect daemon starting ago 06 22:42:52 roadrunner org.kde.kwalletd5[2964]: slotServiceOwnerChanged ":1.58" , ":1.58" , "" ago 06 22:42:52 roadrunner org.kde.kwalletd5[2964]: slotServiceOwnerChanged ":1.57" , ":1.57" , "" Open to any hint or suggestion to get the system stable again. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

3 5

[opensuse-kde] KMail keeps changing theme of the list of the messages
by Vojtěch Zeisek 10 Aug '17

10 Aug '17

Since about a week, KMail 5.5.3 (Tumbleweed) keeps when starting changing theme of the message list to "Intelligent" (default). I must change it manually (View | Message list | Theme) to "Classic", which I set long time ago and keep it as required. Anyone else having same problem? How to tell KMail not to change my choice? -- Vojtěch Zeisek Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux https://www.opensuse.org/ https://trapa.cz/

2 1

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

openSUSE KDE August 2017