[dolphin] [Bug 483436] Incorrect display of file icons (thumbnails)
https://bugs.kde.org/show_bug.cgi?id=483436 --- Comment #1 from bluelupo --- Distribution : KDE neon 6.0 Kernel : 6.5.0-25-generic SystemD: systemd 249 (249.11-0ubuntu3.12) Plasma : 6.0.2 Qt : 6.6.2-1xneon Kwin X11 : 6.0.2 Kwin Wayland : 6.0.2 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 483436] New: Incorrect display of file icons (thumbnails)
https://bugs.kde.org/show_bug.cgi?id=483436 Bug ID: 483436 Summary: Incorrect display of file icons (thumbnails) Classification: Applications Product: dolphin Version: 24.02.0 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: view-engine: details mode Assignee: dolphin-bugs-n...@kde.org Reporter: i...@sinweb.de CC: kfm-de...@kde.org Target Milestone: --- Created attachment 167095 --> https://bugs.kde.org/attachment.cgi?id=167095=edit Screenshot of folder view from dolphin SUMMARY *** The thumbnails are not displayed correctly in the Dolphin file manager (see attachment file). The user “michael” is in the following groups: $ id -a michael uid=1000(michael) gid=1000(michael) Gruppen=1000(michael),4(adm),20(dialout),24(cdrom),27(sudo),29(audio),30(dip),44(video),46(plugdev),50(staff),100(users),113(netdev),116(lpadmin),117(scanner),125(sambashare),129(vboxusers),5001(music),5002(photo),131(kvm),998(adbusers),997(docker) In the screenshot you can see that the file “Z” belongs to the user root and the group “photo” has write permissions (permission 660). I can also change this because the user “michael” is in the “photo” group. Unfortunately, the lock symbol for the file “Z” is then displayed in Dolphin, which is definitely wrong. This error did not occur under Plasma5 and the thumbnails were displayed correctly, i.e. without the lock symbol. As soon as the file permissions are 660 (see screenshot), the display in Dolphin is incorrect, as the user’s group permissions are presumably not taken into account. *** STEPS TO REPRODUCE 1. start dolphin 2. look at the details mode OBSERVED RESULT lock symbol is displayed despite write access to the file EXPECTED RESULT correct display of thumbnails/icons if write permissions on the file allow it (group and user permissions) SOFTWARE/OS VERSIONS Distribution : KDE neon 6.0 Kernel : 6.5.0-25-generic SystemD: systemd 249 (249.11-0ubuntu3.12) Plasma : 6.0.0 Qt : 5.15.12 Kwin X11 : 6.0.2 Kwin Wayland : 6.0.2 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 462099] Autostart of a shell script does not work anymore since the upgrade to 22.04
https://bugs.kde.org/show_bug.cgi?id=462099 --- Comment #16 from bluelupo --- Hello Nate, no xbindkeys does not run in the process list. $ ps -ef|grep -i xbindkeys michael 81968164 0 07:18 pts/100:00:00 grep --color=auto -i xbindkeys $ systemctl status --user app-xbindkeys@autostart.service ○ app-xbindkeys@autostart.service - xbindkeys Loaded: loaded (/etc/xdg/autostart/xbindkeys.desktop; generated) Active: inactive (dead) since Thu 2022-12-15 06:51:53 CET; 32min ago Docs: man:systemd-xdg-autostart-generator(8) Process: 3110 ExecStart=/usr/bin/xbindkeys_autostart (code=exited, status=0/SUCCESS) Main PID: 3110 (code=exited, status=0/SUCCESS) CPU: 28ms Dez 15 06:51:53 neonlight systemd[2514]: Starting xbindkeys... Dez 15 06:51:53 neonlight systemd[2514]: Started xbindkeys. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 462099] Autostart of a shell script does not work anymore since the upgrade to 22.04
https://bugs.kde.org/show_bug.cgi?id=462099 --- Comment #14 from bluelupo --- $ systemctl cat --user app-xbindkeys@autostart.service # /run/user/1000/systemd/generator.late/app-xbindkeys@autostart.service # Automatically generated by systemd-xdg-autostart-generator [Unit] Documentation=man:systemd-xdg-autostart-generator(8) SourcePath=/etc/xdg/autostart/xbindkeys.desktop PartOf=graphical-session.target Description=xbindkeys After=graphical-session.target [Service] Type=exec ExecStart=:/usr/bin/xbindkeys_autostart Restart=no TimeoutSec=5s Slice=app.slice -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 462099] Autostart of a shell script does not work anymore since the upgrade to 22.04
https://bugs.kde.org/show_bug.cgi?id=462099 --- Comment #13 from bluelupo --- Output of the command $ systemctl status --user app-xbindkeys@autostart.service ○ app-xbindkeys@autostart.service - xbindkeys Loaded: loaded (/etc/xdg/autostart/xbindkeys.desktop; generated) Active: inactive (dead) since Tue 2022-12-13 06:57:21 CET; 2h 49min ago Docs: man:systemd-xdg-autostart-generator(8) Process: 3105 ExecStart=/usr/bin/xbindkeys_autostart (code=exited, status=0/SUCCESS) Main PID: 3105 (code=exited, status=0/SUCCESS) CPU: 31ms Dez 13 06:57:20 neonlight systemd[2614]: Starting xbindkeys... Dez 13 06:57:20 neonlight systemd[2614]: Started xbindkeys. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 462099] Autostart of a shell script does not work anymore since the upgrade to 22.04
https://bugs.kde.org/show_bug.cgi?id=462099 --- Comment #11 from bluelupo --- Hi thenujan, there is no autostart unit $ systemctl status --user start_xbindkeys.sh Unit start_xbindkeys.sh.service could not be found. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 462099] Autostart of a shell script does not work anymore since the upgrade to 22.04
https://bugs.kde.org/show_bug.cgi?id=462099 --- Comment #7 from bluelupo --- The command line command they mentioned solved the problem. The start_xbindkeys autostart script is now executed when the KDE desktop is started. Thus the additional key bindings for the mouse are initiated in the script start_xbindkeys . I still have one question, what exactly does the command do? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 462099] Autostart of a shell script does not work anymore since the upgrade to 22.04
https://bugs.kde.org/show_bug.cgi?id=462099 --- Comment #5 from bluelupo --- the shellccript is executable, I already paid attention to that. -rwx-- 1 michael michael 24 Feb 10 2015 /home/michael/userscripts/start_xbindkeys -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 462099] Autostart of a shell script does not work anymore since the upgrade to 22.04
https://bugs.kde.org/show_bug.cgi?id=462099 --- Comment #3 from bluelupo --- Created attachment 154160 --> https://bugs.kde.org/attachment.cgi?id=154160=edit Autostart shellscript Here is my shellscript in the file attachment -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 462099] Autostart of a shell script does not work anymore since the upgrade to 22.04
https://bugs.kde.org/show_bug.cgi?id=462099 --- Comment #1 from bluelupo --- Created attachment 153927 --> https://bugs.kde.org/attachment.cgi?id=153927=edit Screentshot Autostart script in the systemsettings -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 462099] New: Autostart of a shell script does not work anymore since the upgrade to 22.04
https://bugs.kde.org/show_bug.cgi?id=462099 Bug ID: 462099 Summary: Autostart of a shell script does not work anymore since the upgrade to 22.04 Classification: I don't know Product: kde Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: i...@sinweb.de Target Milestone: --- SUMMARY *** A short self-made bashscript that starts xbindkeys unfortunately does not work anymore since the update to KDE Neon 22.04. Running the bashscript manually in the console after starting the desktop works without problems. My Script: #!/bin/bash nohup xbindkeys #EOF *** Distributor ID: Neon Description: KDE neon 5.26 Release: 22.04 Codename: jammy STEPS TO REPRODUCE 1. start from KDE, OBSERVED RESULT no process of xbindkeys running EXPECTED RESULT An xbindkeys should be visible in the process list SOFTWARE/OS VERSIONS Distribution: KDE neon 5.26 Kernel : 5.15.0-53-generic Plasma : 5.26.3 Qt : 5.15.7 KF : 5.100.0 Kwin: 5.18.7 ADDITIONAL INFORMATION The shell script for the autostart of xbindkeys was correctly included or created by me in the system settings under the item Start and Shutdown, subitem Autostart. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 365959] Addressbook is not usable via Owncloud-Ressource
https://bugs.kde.org/show_bug.cgi?id=365959 --- Comment #10 from bluelupo --- The error that occurred at that time no longer occurs now. The error report can be closed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 388349] Activity partially unusable
https://bugs.kde.org/show_bug.cgi?id=388349 --- Comment #2 from bluelupo --- Hi Nate, you close the bugreport. The error does not occur in the current version. regars Michael Am Montag, 15. März 2021, 17:21:00 CET schrieben Sie: > https://bugs.kde.org/show_bug.cgi?id=388349 > > Nate Graham changed: > >What|Removed |Added > > Assignee|notm...@gmail.com |k...@davidedmundson.co.uk > Component|Desktop Containment |general > CC||n...@kde.org > Resolution|--- |WAITINGFORINFO > Status|REPORTED|NEEDSINFO > > --- Comment #1 from Nate Graham --- > Sorry nobody looked at this sooner. :( Is it still happening in Plasma 5.21? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 400543] console crashes unexpectedly
https://bugs.kde.org/show_bug.cgi?id=400543 bluelupo changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #2 from bluelupo --- Thanks for the message. The error no longer occurs and the bug report can be marked as solved. $ apt cache policy konsole konsole: Installiert: 4:20.08.3-0xneon+20.04+focal+build9 Installationskandidat: 4:20.08.3-0xneon+20.04+focal+build9 regards Michael -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 405778] KDEconnect can not connect to the desktop
https://bugs.kde.org/show_bug.cgi?id=405778 --- Comment #7 from bluelupo --- Hi Justin, you can be marked as resolved. The error no longer occurs. Thanks Michael -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 405778] KDEconnect can not connect to the desktop
https://bugs.kde.org/show_bug.cgi?id=405778 --- Comment #2 from bluelupo --- Hi Erik, I have the latest version from the F-Droid Appstore installed. This is version 1.12 (11200, 2019-03-10). Version 1.12.6 is already available on the Google Playstore, but I can not access it because I do not use goggle apps on my smartphone. Do you know when version 1.12.6 will be available in F-Droid? Greetings Michael -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 405778] New: KDEconnect can not connect to the desktop
https://bugs.kde.org/show_bug.cgi?id=405778 Bug ID: 405778 Summary: KDEconnect can not connect to the desktop Product: kdeconnect Version: 1.3.3 Platform: Neon Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: i...@bluelupo.net Target Milestone: --- SUMMARY When I access my smartphone (Oneplus 3T) via KDEconnect in the file manager Dolphin, the following error message appears in German: "The drive can not be unmounted. The error message is: File system of the device can not be integrated." STEPS TO REPRODUCE 1. Click on the mobile device on the left in the "Devices" window in the file manager 2. Error message as described above in the file window 3. Always reproducible OBSERVED RESULT No access to the file system of the Android device EXPECTED RESULT Access to the file system of the Android device SOFTWARE/OS VERSIONS KDEconnect : 1.3.3-0xneon+18.04+bionic+build10 Kernel : 4.18.0-16-generic Plasma : 5.15.3.2 Qt : 5.12.0 KF : 5.56.1 Distribution: KDE Neon Useredition ADDITIONAL INFORMATION Mobil device Hardware : Oneplus 3T Mobil device OS : LineageOS 16.0 Mobil KDEconnect version: 1.12 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 400178] KDEConnect fails to open remote phone directory as it says protocol died unexpectedly
https://bugs.kde.org/show_bug.cgi?id=400178 --- Comment #74 from bluelupo --- Problem solved with the new kdeconnect version 1.3.3 in KDE Neon. Thanks guys! -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 400543] New: console crashes unexpectedly
https://bugs.kde.org/show_bug.cgi?id=400543 Bug ID: 400543 Summary: console crashes unexpectedly Product: konsole Version: 18.08.2 Platform: Neon Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: i...@bluelupo.net Target Milestone: --- SUMMARY When calling a "MultiTab" console using a config file, the console crashes reproducibly. Content of the config file with the calls for the console: $ cat /home/michael/multi-console.config title: Log rsnapshot_bluesky;; command: tail -n 40 -f /var/log/rsnapshot_bluesky;; profile: Shell title: Log rsnapshot_neonlight;; command: tail -n 40 -f /var/log/rsnapshot_neonlight;; profile: Shell title: Log rsnapshot_raven;; command: tail -n 40 -f /var/log/rsnapshot_raven;; profile: Shell title: Log rsnapshot_tuxy;; command: tail -n 40 -f /var/log/rsnapshot_tuxy;;profile: Shell I started this with the following command from the console: $ konsole --tabs-from-file /home/michael/multi-konsole.config -e true KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = konsole path = /usr/bin pid = 31674 KCrash: Arguments: /usr/bin/konsole --tabs-from-file /home/michael/multi-konsole.config -e true KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 STEPS TO REPRODUCE I can reproduce the crash of the console at any time OBSERVED RESULT Crash the console with the issues listed above. EXPECTED RESULT Start the console with the number of tabs as defined in the config file /home/michael/multi-konsole.config. SOFTWARE VERSIONS Distribution: KDE neon User Edition 5.14 Kernel : 4.15.0-38-generic Plasma : 5.14.2 Qt : 5.11.2 KF : 5.51.0 konsole : Installed: 4:18.08.2-0xneon+18.04+bionic+build11 Candidate: 4:18.08.2-0xneon+18.04+bionic+build11 Version table: *** 4:18.08.2-0xneon+18.04+bionic+build11 500 500 http://archive.neon.kde.org/user bionic/main amd64 Packages 100 /var/lib/dpkg/status ADDITIONAL INFORMATION If further system information is needed I can list it here. regards Michael -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 400178] KDEConnect fails to open remote phone directory as it says protocol died unexpectedly
https://bugs.kde.org/show_bug.cgi?id=400178 --- Comment #13 from bluelupo --- I have the same problems with kdeconnect see the bug report I opened under https://bugs.kde.org/show_bug.cgi?id=399943 I have verified this with two KDE Neon installations, both show the same error behavior. regards Michael -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 399943] New: kdeconnect quits unexpectedly
https://bugs.kde.org/show_bug.cgi?id=399943 Bug ID: 399943 Summary: kdeconnect quits unexpectedly Product: kdeconnect Version: 1.3.1 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: plasmoid Assignee: albertv...@gmail.com Reporter: i...@bluelupo.net Target Milestone: --- Created attachment 115710 --> https://bugs.kde.org/attachment.cgi?id=115710=edit Dialogbox Screenshot If you want to access the smartphone with kdeconnect from the control panel or from the file manager Dolphin, a dialog box opens with the error message: --- The process for the Protocol kdeconnect: // 637813d43352f8c8 was quit unexpectedly. --- I can reproduce the error at any time. Thus, it is no longer possible to access the smartphone from the KDE desktop. Distribution: KDE neon User Edition 5.14 Kernel : 4.15.0-36-generic Plasma : 5.14.0 Qt : 5.11.1 KF : 5.51.0 Kwin: 5.14.0 Akonadi : 5.9.2 Kmail : 5.9.2 What can I do to prevent the error from occurring? regards Michael -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 395133] cannot treat [edit] adresses
https://bugs.kde.org/show_bug.cgi?id=395133 bluelupo changed: What|Removed |Added CC||i...@bluelupo.net --- Comment #5 from bluelupo --- Hi all, I have the same problems with the address book under KDE Neon here. I can not edit an address entry as Nextcloud resource nor an entry in a local address book. System information Linux Distribution: KDE Neon Kernel: 4.13.0-45-generic Version of Plasma: 5.13.3 Versions of Kaddressbook: # dpkg -l|grep kaddressbook ii kaddressbook 4:18.04.3-0xneon+16.04+xenial+build46amd64address book and contact data manager ii libkf5kaddressbookgrantlee5:amd64 4:18.04.3-0xneon+16.04+xenial+build37amd64follow up reminder library ii libkf5kaddressbookimportexport5:amd64 4:18.04.3-0xneon+16.04+xenial+build37amd64 Addressbook import export library Greetings Bluelupo -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 396722] New: Kontact crashes since the update to the plasma version 5.13.3
https://bugs.kde.org/show_bug.cgi?id=396722 Bug ID: 396722 Summary: Kontact crashes since the update to the plasma version 5.13.3 Product: kontact Version: 5.8.2 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: summary Assignee: kdepim-b...@kde.org Reporter: i...@bluelupo.net Target Milestone: --- Hi maintainer, Since today's (2018-07-21) update (apt-get update && apt-get dist-upgrade) to the plasma version 5.13.3, in which two packages related to Kontact have been updated, Kontact crashes on startup. This I have tested physical hardware, as well as in a virtual machine (kvm) with a KDE Neon installation. Until the update of the system I had no problems with Kontact. My system data: System: KDE Neon Useredition Kernel: 4.15.0-29-generic kontact packages on my system $ dpkg -l|grep kontact ii kontact 4:18.04.2-0neon+16.04+xenial+build50 amd64integrated application for personal information management ii libkf5kontactinterface-data 18.04.3-0xneon+16.04+xenial+build42 all Kontact interface library - data files ii libkf5kontactinterface5:amd64 18.04.3-0xneon+16.04+xenial+build42 amd64Kontact interface library If you still need data from my system please let me know. Greetings Bluelupo -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 388349] New: Activity partially unusable
https://bugs.kde.org/show_bug.cgi?id=388349 Bug ID: 388349 Summary: Activity partially unusable Product: kactivitymanagerd Version: 5.11.4 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: ivan.cu...@kde.org Reporter: i...@bluelupo.net CC: plasma-b...@kde.org Target Milestone: --- Dear Maintainer, In my KDE Neon system, the following error occurs in connection with three scheduled activities. I log in to the KDE desktop and it appears the default activity, then I switch to one of the two other existing activities with the activity bar (in german "Aktivitätenleiste") mini-program, I can not start the desktop icons stored there on this activity. It seems like this activity is "frozen", the other two activities are working correctly. Unfortunately, this error is not always reproducible and does not occur every time you log in to the KDE desktop. If further information is needed I can adjust this here. My system: # inxi -v3 System:Host: neonlight Kernel: 4.11.0-14-generic x86_64 (64 bit gcc: 5.4.0) Desktop: N/A Distro: neon 16.04 xenial Machine: Mobo: Intel model: DH77DF v: AAG40293-300 serial: BTDF21VL Bios: Intel v: KCH7710H.86A.0095.2012.0608.1754 date: 06/08/2012 CPU: Quad core Intel Core i7-3770S (-HT-MCP-) cache: 8192 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 24743 clock speeds: max: 3900 MHz 1: 1613 MHz 2: 1755 MHz 3: 1629 MHz 4: 1662 MHz 5: 1599 MHz 6: 1606 MHz 7: 1609 MHz 8: 1602 MHz Graphics: Card: Intel Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller bus-ID: 00:02.0 Display Server: X.org 1.19.3 drivers: (unloaded: fbdev,vesa) tty size: 128x53 Advanced Data: N/A for root Network: Card: Intel 82579V Gigabit Network Connection driver: e1000e v: 3.2.6-k port: f080 bus-ID: 00:19.0 IF: eno1 state: up speed: 1000 Mbps duplex: full mac: e0:cb:4e:8b:b2:f1 Drives:HDD Total Size: 1000.2GB (35.3% used) ID-1: model: Samsung_SSD_850 ID-2: model: WDC_WD5000BPKT Info: Processes: 295 Uptime: 30 min Memory: 2297.7/15945.0MB Init: systemd runlevel: 5 Gcc sys: 5.4.0 Client: Shell (bash 4.3.481) inxi: 2.2.35 regards Michael -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 379911] No mail accounts (IMAP) can be created or configured anymore
https://bugs.kde.org/show_bug.cgi?id=379911 --- Comment #10 from bluelupo <i...@bluelupo.net> --- Thanks the problem is solved. The IMAP account can be edited again or create a new one. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 379911] No mail accounts (IMAP) can be created or configured anymore
https://bugs.kde.org/show_bug.cgi?id=379911 --- Comment #5 from bluelupo <i...@bluelupo.net> --- Hi Alex, Thanks for the info on the 17.04.2 release where the error is fixed ;-) Michael -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 379911] No mail accounts (IMAP) can be created or configured anymore
https://bugs.kde.org/show_bug.cgi?id=379911 --- Comment #3 from bluelupo <i...@bluelupo.net> --- Hi Alex, a question yet, in which version exactly is the error in KDE Neon then fixed? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 379911] No mail accounts (IMAP) can be created or configured anymore
https://bugs.kde.org/show_bug.cgi?id=379911 --- Comment #1 from bluelupo <i...@bluelupo.net> --- additional info: The error is identical and reproducible in several Neon installations. Two virtual systems and one installation on real hardware are affected. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 379911] New: No mail accounts (IMAP) can be created or configured anymore
https://bugs.kde.org/show_bug.cgi?id=379911
Bug ID: 379911
Summary: No mail accounts (IMAP) can be created or configured
anymore
Product: kmail2
Version: unspecified
Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: NOR
Component: config dialog
Assignee: kdepim-b...@kde.org
Reporter: i...@bluelupo.net
Target Milestone: ---
Dear maintainer,
Since the update on 17.04 (KDE Neon Useredition) no new IMAP accounts can be
added. The existing IMAP accounts can not be configured via the "Bearbeiten"
(in german) button. The Setup dialog no longer appears. The error can be
reproduced at any time.
Versions:
Linux: KDE Neon Useredition
Kernel: 4.8.0-30-generic
Plasma: plasma-workspace 4:5.9.5.1-0neon+16.04+build75
Kmail: kmail 4:17.04.1-0neon+16.04+build20
Kontact: kontact 4:17.04.1-0neon+16.04+build18
Akonadi:
$ dpkg -l|egrep ^'(ii akonadi)'|awk '{print $1,$2,$3}'
ii akonadi-backend-mysql 4:17.04.1-0neon+16.04+build29
ii akonadi-contacts-data 4:17.04.1-0neon+16.04+build22
ii akonadi-mime-data 4:17.04.1-0neon+16.04+build18
ii akonadi-server 4:17.04.1-0neon+16.04+build29
ii akonadiconsole 4:17.04.1-0neon+16.04+build12
$ cat /etc/lsb-release
DISTRIB_ID=neon
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="KDE neon User Edition 5.9"
If you still need information from my system, please ask.
regards
Michael
--
You are receiving this mail because:
You are watching all bug changes.
[kactivitymanagerd] [Bug 371150] Black screen is when more than one type of activity is applied
https://bugs.kde.org/show_bug.cgi?id=371150 --- Comment #12 from bluelupo <i...@bluelupo.net> --- Hi Ivan, To 1.) kdebugdialog5 I have installed. Afterwards as user started and the indicated packages "plasma" and "libplasma" activated by checkbox. To 2.) I have pulled the ActivityPager on the bar, nothing has happened. No black screen, to 3.) You mean probably start the plasma shell from a terminal. I did that (before a kill on the plasmashell process) and the screen was briefly black. Then again in the terminal the Plasmashell started, it was everything as before. The ActivityPager was still in the bar and all activities were accessible by mouse. I now have the original error probably no more. It could be the Debian Unstable, however, newer plasma packages have fixed the error. -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 371150] Black screen is when more than one type of activity is applied
https://bugs.kde.org/show_bug.cgi?id=371150 --- Comment #10 from bluelupo <i...@bluelupo.net> --- Here is the output from "plasmashell" ;-) $ plasmashell file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Panel.qml:83: TypeError: Cannot read property 'Layout' of null Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) Could not resolve property : radialGradient4857 Could not resolve property : radialGradient4857 Could not resolve property : radialGradient4857 file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Button.qml:96: TypeError: Cannot read property of null file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Button.qml:96: TypeError: Cannot read property of null file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Button.qml:96: TypeError: Cannot read property of null file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Button.qml:96: TypeError: Cannot read property of null file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/main.qml:78:27: Unable to assign [undefined] to QStringList file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/main.qml:37: TypeError: Cannot read property 'DateTime' of undefined file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/DigitalClock.qml:443:5: QML Text: Cannot anchor to a null item. Notifications service registered file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Button.qml:96: TypeError: Cannot read property of null Plasma Shell startup completed file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Button.qml:96: TypeError: Cannot read property of null -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 371150] Black screen is when more than one type of activity is applied
https://bugs.kde.org/show_bug.cgi?id=371150 --- Comment #7 from bluelupo <i...@bluelupo.net> --- Here is the output: $ ps -ef|grep plasmashell michael 2294 2272 4 18:21 ?00:00:05 plasmashell --shut-up $ kill 2294 $ plasmashell --shut-up file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Panel.qml:83: TypeError: Cannot read property 'Layout' of null Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) Could not resolve property : radialGradient4857 Could not resolve property : radialGradient4857 Could not resolve property : radialGradient4857 file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Button.qml:96: TypeError: Cannot read property of null file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Button.qml:96: TypeError: Cannot read property of null file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Button.qml:96: TypeError: Cannot read property of null file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Button.qml:96: TypeError: Cannot read property of null file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/main.qml:78:27: Unable to assign [undefined] to QStringList file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/main.qml:37: TypeError: Cannot read property 'DateTime' of undefined file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/DigitalClock.qml:443:5: QML Text: Cannot anchor to a null item. Notifications service registered file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Button.qml:96: TypeError: Cannot read property of null Plasma Shell startup completed file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Button.qml:96: TypeError: Cannot read property of null file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Button.qml:96: TypeError: Cannot read property of null QXcbConnection: XCB error: 2 (BadValue), sequence: 1926, resource id: 83886082, major code: 142 (Unknown), minor code: 3 -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 371150] Black screen is when more than one type of activity is applied
https://bugs.kde.org/show_bug.cgi?id=371150 --- Comment #5 from bluelupo <i...@bluelupo.net> --- Hi Ivan, Thank you for your quick response. Now the KDE desktop temporarily changed to English to find the correct identifiers. "Aktivitätenüberwachung" is in english the "Activity Pager" ;-) The "Activity Pager" is installed by default and has nothing to do with my used Linux distribution siduction. Here the output from the command: $ grep plugin ~/.config/plasma-org.kde.plasma.desktop-appletsrc | sort -u plugin=org.kde.desktopcontainment plugin=org.kde.panel plugin=org.kde.plasma.clipboard plugin=org.kde.plasma.devicenotifier plugin=org.kde.plasma.digitalclock plugin=org.kde.plasma.kickoff plugin=org.kde.plasma.notifications plugin=org.kde.plasma.pager plugin=org.kde.plasma.private.systemtray plugin=org.kde.plasma.systemtray plugin=org.kde.plasma.taskmanager plugin=org.kde.plasma.volume wallpaperplugin=org.kde.image I hope now the error report becomes clearer and understandable to you ;-) greetings Michael -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 371150] Black screen is when more than one type of activity is applied
https://bugs.kde.org/show_bug.cgi?id=371150 --- Comment #3 from bluelupo <i...@bluelupo.net> --- Hi Ivan, let me explain ;-) Rightclick on the desktop, then in the context menu "Add Miniprogramme" (in German: Miniprogramme hinzufügen), then the Miniprogramme "Activity monitoring" (in German: Aktivitätenüberwachung) to the control bar pull by mouse. At this point, the desktop becomes black. Sorry for my insufficient English. I hope I have now expressed myself clearly. greetings Michael -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 371150] Black screen is when more than one type of activity is applied
https://bugs.kde.org/show_bug.cgi?id=371150 --- Comment #1 from bluelupo <i...@bluelupo.net> --- More Information: The error only occurs if the Miniprogramms activity monitoring is placed in the window bar or on the desktop background with more than one created activity. In this action, the screen becomes black and you can not get out of this state. In addition, it seems despite a "black screen" that the KDE desktop running in the background still, because after a few minutes of the "Black Sreen" the dialog box of the screen lock. If you do not touch the mini-program "Activity monitoring" you do not have problems with several created activities. -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 371150] Black screen is when more than one type of activity is applied
https://bugs.kde.org/show_bug.cgi?id=371150 bluelupo <i...@bluelupo.net> changed: What|Removed |Added Summary|Black screen is when more |Black screen is when more |than one type applied |than one type of activity ||is applied -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 371150] New: Black screen is when more than one type applied
https://bugs.kde.org/show_bug.cgi?id=371150 Bug ID: 371150 Summary: Black screen is when more than one type applied Product: kactivitymanagerd Version: 5.8.0 Platform: Debian unstable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: ivan.cu...@kde.org Reporter: i...@bluelupo.net CC: plasma-b...@kde.org Hi, If more than one activity is created, the screen remains black after the KDE splash screen (KDE logo). Deletes in the $HOME of the user the directories .config, .kde and .local is a login possible again but of course you have an initial desktop. As soon as you create an additional activity, the error reappears. The error occurs reproducibly whether the installation runs in a virtual machine or on real hardware. Reproducible: Always Steps to Reproduce: Create a second activity Actual Results: Can not login to the KDE desktop My system (Siduction) has current packages from Debian Unstable. Kernel version: 4.8.2-towo.1-siduction-amd64 I would like to provide additional information about my installation as long as it is needed. What can be done against this error? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 370301] Auto grouping of any program windows does not work
https://bugs.kde.org/show_bug.cgi?id=370301 --- Comment #3 from bluelupo <i...@bluelupo.net> --- If you need more information about my system, I would like to post it here. regards Michael Singer -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 370301] Auto grouping of any program windows does not work
https://bugs.kde.org/show_bug.cgi?id=370301 --- Comment #2 from bluelupo <i...@bluelupo.net> --- Created attachment 101489 --> https://bugs.kde.org/attachment.cgi?id=101489=edit systemsettings dialog -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 370301] Auto grouping of any program windows does not work
https://bugs.kde.org/show_bug.cgi?id=370301 --- Comment #1 from bluelupo <i...@bluelupo.net> --- Created attachment 101488 --> https://bugs.kde.org/attachment.cgi?id=101488=edit systemsettings dialog -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 370301] New: Auto grouping of any program windows does not work
https://bugs.kde.org/show_bug.cgi?id=370301 Bug ID: 370301 Summary: Auto grouping of any program windows does not work Product: kwin Version: unspecified Platform: Debian unstable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: rules Assignee: kwin-bugs-n...@kde.org Reporter: i...@bluelupo.net Hi Maintainer, If I create a rule for the autogrouping of any program (such as kwrite) and save it through the "systemettings / window management / window rules" they have no effect. Different instances of the same program are always displayed in a separate window and not in an additional tab (as you would expect). The rules that have been created are shown in the attached screenshot. Reproducible: Always Steps to Reproduce: reproducible at any time Actual Results: These types of window rules can be created but do not work. Kernel: 4.8.0 Distribution: Siduction (based on Debian SID) # dpkg -l|egrep '(kwin|systemsettings|plasma)' ii kde-plasma-desktop5:91 amd64KDE Plasma Desktop and minimal set of applications ii kdeplasma-addons-data 4:5.7.4-1 all locale files for kdeplasma-addons ii kwin-addons 4:5.7.4-1 amd64additional desktop and window switchers for KWin ii kwin-common 4:5.7.4-1 amd64KDE window manager, common files ii kwin-data 4:5.7.4-1 all KDE window manager data files ii kwin-style-breeze 4:5.7.4-1 amd64KWin Breeze Style ii kwin-x11 4:5.7.4-1 amd64KDE window manager, X11 version ii libkdeclarative5 4:4.14.23-1 amd64declarative library for plasma ii libkf5plasma5:amd64 5.26.0-2 amd64Plasma Runtime components ii libkf5plasmaquick5:amd64 5.26.0-2 amd64Plasma Runtime components ii libkwin4-effect-builtins1 4:5.7.4-1 amd64KDE window manager effect builtins library ii libkwineffects8 4:5.7.4-1 amd64KDE window manager effects library ii libkwinglutils8 4:5.7.4-1 amd64KDE window manager gl utils library ii libkwinxrenderutils8 4:5.7.4-1 amd64KDE window manager render utils library ii libplasma-geolocation-interface5 4:5.7.4-1 amd64Plasma Workspace for KF5 library ii libplasma34:4.14.23-1 amd64Plasma Library for the KDE Platform ii plasma-dataengines-addons 4:5.7.4-1 amd64additional data engines for Plasma ii plasma-desktop4:5.7.4-2 amd64Tools and widgets for the desktop ii plasma-desktop-data 4:5.7.4-2 all Tools and widgets for the desktop data files ii plasma-framework 5.26.0-2 amd64Plasma Runtime components ii plasma-integration5.7.4-1 amd64Qt Platform Theme integration plugins for KDE Plasma ii plasma-pa 5.7.4-1 amd64Plasma 5 Volume controller ii plasma-runners-addons 4:5.7.4-1 amd64additional runners for Plasma 5 and Krunner ii plasma-scriptengine-javascript4:16.08.0-1 amd64JavaScript script engine for Plasma ii plasma-wallpapers-addons 4:5.7.4-1 amd64additional wallpaper plugins for Plasma 5 ii plasma-widgets-addons 4:5.7.4-1 amd64additional widgets for Plasma 5 ii plasma-workspace 4:5.7.4-1 amd64Plasma Workspace for KF5 ii qml-module-org-kde-kwindowsystem:amd645.26.0-1 amd64provides integration of QML and KDE frameworks - kwindowsystem ii systemsettings4:5.7.4-1
[kactivitymanagerd] [Bug 369145] kactivitymanagerd and kdeconnectd crashed on logout of KDE
https://bugs.kde.org/show_bug.cgi?id=369145 --- Comment #1 from bluelupo <i...@bluelupo.net> --- If you have information of my system need I can provide it to you. -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 369145] New: kactivitymanagerd and kdeconnectd crashed on logout of KDE
https://bugs.kde.org/show_bug.cgi?id=369145 Bug ID: 369145 Summary: kactivitymanagerd and kdeconnectd crashed on logout of KDE Product: kactivitymanagerd Version: unspecified Platform: Debian unstable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: ivan.cu...@kde.org Reporter: i...@bluelupo.net CC: plasma-b...@kde.org Dear Maintainer, When finishing a KDE session will be displayed in the journal core dumps caused by kactivitymanage and kdeconnectd. The problem is reproducible at any time. Below is an excerpt of the systemd Journal: BEGIN-- Sep 21 09:16:50 bluesky systemd-coredump[6794]: Process 4949 (kdeconnectd) of user 1000 dumped core. Stack trace of thread 4951: #0 0x7f6391a177af _ZN7QObject10disconnectEPKS_PKcS1_S3_ (libQt5Core.so.5) #1 0x7f6390a4b430 n/a (libQt5DBus.so.5) #2 0x7f6390a38632 n/a (libQt5DBus.so.5) #3 0x7f639180ed78 n/a (libQt5Core.so.5) #4 0x7f638e2d2464 start_thread (libpthread.so.0) #5 0x7f639112a97f __clone (libc.so.6) Stack trace of thread 4949: #0 0x7f638e2d818f pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x7f639180fc3b _ZN14QWaitCondition4waitEP6QMutexm (libQt5Core.so.5) #2 0x7f639180e91e _ZN7QThread4waitEm (libQt5Core.so.5) #3 0x7f6390a38396 n/a (libQt5DBus.so.5) #4 0x7f6390a38429 n/a (libQt5DBus.so.5) #5 0x7f6391077920 n/a (libc.so.6) #6 0x7f639107797a exit (libc.so.6) #7 0x7f6380fb9533 _ZN14QXcbConnection16processXcbEventsEv (libQt5XcbQpa.so.5) #8 0x7f6391a14729 _ZN7QObject5eventEP6QEvent (libQt5Core.so.5) #9 0x7f6392322bec _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5) #10 0x7f639232808f _ZN12QApplication6notifyEP7QObjectP6QEvent (libQt5Widgets.so.5) #11 0x7f63919e6450 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5) #12 0x7f63919e83cc _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt5Core.so.5) #13 0x7f6391a3c0f3 n/a (libQt5Core.so.5) #14 0x7f638ddaf7d7 g_main_context_dispatch (libglib-2.0.so.0) #15 0x7f638ddafa40 n/a (libglib-2.0.so.0) #16 0x7f638ddafaec g_main_context_iteration (libglib-2.0.so.0) #17 0x7f6391a3c4ff _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5) #18 0x7f63919e419a _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5) #19 0x7f63919ec99c _ZN16QCoreApplication4execEv (libQt5Core.so.5) #20 0x0040263f main (kdeconnectd) #21 0x7f63910622b1 __libc_start_main (libc.so.6) #22 0x004026a9 _start (kdeconnectd) Stack trace of thread 4952: #0 0x7f639112150d __poll (libc.so.6) #1 0x7f638ddaf9d6 n/a (libglib-2.0.so.0) #2 0x7f638ddafaec g_main_context_iteration (libglib-2.0.so.0) #3 0x7f6391a3c4ff _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5) #4 0x7f63919e419a _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5) #5 0x7f6391809e53 _ZN7QThread4execEv (libQt5Core.so.5) #6 0x7f639180ed78 n/a (libQt5Core.so.5) #7 0x7f638e2d2464 start_thread (libpthread.so.0) #8 0x7f639112a97f __clone (libc.so.6) Sep 21 09:16:51 bluesky systemd-coredump[6796]: Process 4636 (kactivitymanage) of user 1000 dumped core. Stack trace of thread 4636: #0 0x7f9754111471 _ZN12QSqlDatabase5closeEv (libQt5Sql.so.5) #1 0x7f9754113ae9 _ZN12QSqlDatabaseD1Ev (libQt5Sql.so.5) #2 0x7f97541167dd n/a (libQt5Sql.so.5) #3 0x7f976fefa139 _ZN9QHashData11free_helperEPFvPNS_4NodeEE (libQt5Core.so.5) #4 0x7f9754c7 n/a (libQt5Sql.so.5) #5 0x7f976f702920 n/a (libc.so.6) #6 0x7f976f70297a exit (libc.so.6) #7 0x7f976521a533 _ZN14QXcbConnection16processXcbEventsEv (libQt5XcbQpa.so.5) #8 0x7f977009f729 _ZN7QObject5eventEP6QEvent (libQt5Core.so.5) #9 0x7f9770912bec _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5) #10 0x7f977091808f _ZN12QApplication6notifyEP7QObjectP6QEvent (libQt5Widgets.so.5) #11 0x7f9770071450 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5) #12 0x7f97700733cc _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt5Core.so.5) #13 0x7f97700c70f3 n/a (libQt5Core.so.5) #14 0x7f976e29f7d7 g_main_context_dispatch (libglib-2.0.so.0) #15 0x7f976e29fa40 n/a (libglib-2.0.so.0) #16 0x7f976e29faec g_main_context_iteration (libglib-2.0.so.0) #17 0x7f97700c74ff _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5) #18 0x7f977006f19a _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5) #19 0x7f977007799c _ZN16QCoreApplication4execEv
[Akonadi] [Bug 365959] Addressbook is not usable via Owncloud-Ressource
https://bugs.kde.org/show_bug.cgi?id=365959 --- Comment #8 from bluelupo <i...@bluelupo.net> --- Unfortunately, the setting in Config File found no improvement in the error situation. The address book is included when creating the DAV groupware resource but no content can be seen. My akonadi_davgroupware_resource_6rc: --- [ConfigDialog] Size=852,570 [General] defaultUsername=michael displayName=Owncloud Kontakte michael remoteUrls=$default$|CardDav|https://xx.yy.zz/remote.php/dav/ settingsVersion=3 [UrlConfigurationDialog] Size=352,496 --- What can I do? regards Michael -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 365959] Addressbook is not usable via Owncloud-Ressource
https://bugs.kde.org/show_bug.cgi?id=365959 --- Comment #6 from bluelupo <i...@bluelupo.net> --- Hi Laurent, thanks for this info. Can I fix the problem yourself? If yes how? I am instructed that the access works to the address from the ownCloud. regards Michael -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 365959] Addressbook is not usable via Owncloud-Ressource
https://bugs.kde.org/show_bug.cgi?id=365959 --- Comment #4 from bluelupo <i...@bluelupo.net> --- Hi Laurent, OwnCloud is running at my provider in the version 9.0.0. In version 13.0-8 (Debian Unstable) from Akonadi server everything ran without problems. regards Michael -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 365959] Addressbook is not usable via Owncloud-Ressource
https://bugs.kde.org/show_bug.cgi?id=365959 bluelupo <i...@bluelupo.net> changed: What|Removed |Added Summary|Addressbook is not usable |Addressbook is not usable ||via Owncloud-Ressource -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 365959] Addressbook is not usable
https://bugs.kde.org/show_bug.cgi?id=365959
--- Comment #2 from bluelupo <i...@bluelupo.net> ---
Here's logging output when you start contact from a console:
$ kontact
org.kde.akonadi.ETM: GEN true false false
org.kde.akonadi.ETM: collection: QVector()
org.kde.akonadi.ETM:
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()
"Tag 'a' is not defined in message {<__kuit_internal_top__>For more information
about using Akregator, check the For more information
about using Akregator, check the http://www.kde.org/dotkdeorg.rdf;
"https://www.linux.com/rss/feeds.php;
"http://planetkde.org/rss20.xml;
"http://pim.planetkde.org/rss20.xml;
"http://www.kde.org/dot/kde-apps-content.rdf;
"http://www.kde.org/kde-look-content.rdf;
"http://planetkde.org/pt-br/rss20.xml;
"http://planet.kde-espana.org/atom.xml;
"https://fr.planetkde.org/rss20.xml;
"http://planet.debian.org/rss20.xml;
"http://www.debian.org/News/news;
"http://planet.ubuntu.com/rss20.xml;
"http://feeds.feedburner.com/ubuntu-fridge;
"http://www.kubuntu.org/news/feed;
"http://wire.kubuntu.org/?feed=rss2;
org.kde.akonadi.ETM: GEN true false true
org.kde.akonadi.ETM: collection: QVector()
org.kde.akonadi.ETM: Subtree: 34 QSet(34, 35)
org.kde.akonadi.ETM: collection: "akonadi_davgroupware_resource_2"
org.kde.akonadi.ETM: collection:
"https://xyz.de/remote.php/dav/addressbooks/users/michael/kontakte/;
org.kde.akonadi.ETM: Fetch job took 15 msec
org.kde.akonadi.ETM: was collection fetch job: collections: 2
org.kde.akonadi.ETM: first fetched collection:
"akonadi_davgroupware_resource_2"
org.kde.akonadi.ETM: Fetch job took 2 msec
org.kde.akonadi.ETM: was item fetch job: items: 0
org.kde.akonadi.ETM: Fetch job took 10 msec
org.kde.akonadi.ETM: was item fetch job: items: 0
It is only the integrated Address Book (CardDAV ownCloud resource) watch
without content, although it contains more than 100 entries.
--
You are receiving this mail because:
You are watching all bug changes.
[Akonadi] [Bug 365959] Addressbook is not usable
https://bugs.kde.org/show_bug.cgi?id=365959 --- Comment #1 from bluelupo <i...@bluelupo.net> --- Requires your logfiles Akonadi, if so, which? -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 365959] New: Addressbook is not usable
https://bugs.kde.org/show_bug.cgi?id=365959 Bug ID: 365959 Summary: Addressbook is not usable Product: Akonadi Version: 16.04 Platform: Debian unstable OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: Contacts resource Assignee: to...@kde.org Reporter: i...@bluelupo.net CC: kdepim-b...@kde.org, vkra...@kde.org Dear Maintainer, An integrated CardDAV resource (ownCloud instance) shows the address of any contacts. The resource could be integrated without error and the address is also displayed, but unfortunately are all available records not visible. By contrast, a CalDAV resource of the same ownCloud instance is displayed properly in the calendar and it is also applied Schedules visible. What can I do that the contacts again? If additional information is needed? Regards Michael Singer Reproducible: Always Steps to Reproduce: always reproducible Actual Results: no indication of contacts records -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 362435] Description change to .desktop file via KPropertiesDialog not saved
https://bugs.kde.org/show_bug.cgi?id=362435 --- Comment #12 from bluelupo <i...@bluelupo.net> --- They are more information on reported errors? If the error is already corrected possibly in a KDE version? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362435] Characteristics of desktop icons are not adopted
https://bugs.kde.org/show_bug.cgi?id=362435 --- Comment #9 from bluelupo <i...@bluelupo.net> --- Created attachment 98704 --> https://bugs.kde.org/attachment.cgi?id=98704=edit Screenshot_06.png Screenshots for the bug report -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362435] Characteristics of desktop icons are not adopted
https://bugs.kde.org/show_bug.cgi?id=362435 --- Comment #8 from bluelupo <i...@bluelupo.net> --- Created attachment 98703 --> https://bugs.kde.org/attachment.cgi?id=98703=edit Screenshot_05.png Screenshots for the bug report -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362435] Characteristics of desktop icons are not adopted
https://bugs.kde.org/show_bug.cgi?id=362435 --- Comment #7 from bluelupo <i...@bluelupo.net> --- Created attachment 98702 --> https://bugs.kde.org/attachment.cgi?id=98702=edit Screenshot_04.png Screenshots for the bug report -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362435] Characteristics of desktop icons are not adopted
https://bugs.kde.org/show_bug.cgi?id=362435 --- Comment #6 from bluelupo <i...@bluelupo.net> --- Created attachment 98701 --> https://bugs.kde.org/attachment.cgi?id=98701=edit Screenshot_03.png Screenshots for the bug report -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362435] Characteristics of desktop icons are not adopted
https://bugs.kde.org/show_bug.cgi?id=362435 --- Comment #5 from bluelupo <i...@bluelupo.net> --- Created attachment 98700 --> https://bugs.kde.org/attachment.cgi?id=98700=edit Screenshot_02.png Screenshots for the bug report -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362435] Characteristics of desktop icons are not adopted
https://bugs.kde.org/show_bug.cgi?id=362435 --- Comment #4 from bluelupo <i...@bluelupo.net> --- Created attachment 98699 --> https://bugs.kde.org/attachment.cgi?id=98699=edit Screenshot_01.png Screenshots for the bug report -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362435] Characteristics of desktop icons are not adopted
https://bugs.kde.org/show_bug.cgi?id=362435
--- Comment #3 from bluelupo <i...@bluelupo.net> ---
Hi Eike,
I have attached a few screenshots for detailed analysis. First, I have a new
icon for the calculator on desktop kcalc applied (Screenshot_01.png).
Then called the Properties dialog from the just created desktop icon
(Screenshot_02.png). With another screenshot (Screenshot_03.png) I will show
you config Kcalc.desktop it.
Now I lead changes in the properties dialog by as shown in the next screenshot
(Screenshot_04.png). The description field ("Ein Rechner") and the comment
field ("Test") I have added amendments. Then press the OK button to save.
Now again the Properties dialog or opened with the editor Kcalc.desktop (see
File Screenshot_05.png and Screenshot_06.png). You see that here no amendments
were adopted. Also, the time stamp of Kcalc.desktop file has not changed.
What is wrong?
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 362435] Characteristics of desktop icons are not adopted
https://bugs.kde.org/show_bug.cgi?id=362435
--- Comment #1 from bluelupo <i...@bluelupo.net> ---
Some data:
$ uname -a
Linux snowcat 4.5.2-towo.1-siduction-amd64 #1 SMP PREEMPT siduction 4.5-7
(2016-04-20) x86_64 GNU/Linux
$ dpkg -l | grep -i plasma | awk '{print $1,$2,$3}'
ii breeze 4:5.4.3-1
ii breeze-cursor-theme 4:5.4.3-1
ii breeze-icon-theme 4:5.4.3-1
ii kde-plasma-desktop 5:90
ii kde-standard 5:90
ii kdeconnect 0.9g-1
ii kdeplasma-addons-data 4:5.4.3-1
ii libkdeclarative5 4:4.14.14-1+b2
ii libkf5plasma5:amd64 5.16.0-1
ii libkf5plasmaquick5:amd64 5.16.0-1
ii libkworkspace5-5 4:5.4.3-2
ii libplasma-geolocation-interface5 4:5.4.3-2
ii libplasma3 4:4.14.14-1+b2
ii libtaskmanager5 4:5.4.3-2
ii libweather-ion7 4:5.4.3-2
ii plasma-dataengines-addons 4:5.4.3-1
ii plasma-desktop 4:5.4.3-1
ii plasma-desktop-data 4:5.4.3-1
ii plasma-framework 5.16.0-1
ii plasma-nm 4:5.4.3-1
ii plasma-pa 5.4.3-1
ii plasma-runners-addons 4:5.4.3-1
ii plasma-scriptengine-javascript 4:15.08.3-1+b1
ii plasma-systray-legacy 0~git20151104-ded1538-2
ii plasma-wallpapers-addons 4:5.4.3-1
ii plasma-widget-folderview 4:15.08.3-1
ii plasma-widgets-addons 4:5.4.3-1
ii plasma-workspace 4:5.4.3-2
--
You are receiving this mail because:
You are watching all bug changes.
[konsole] [Bug 360433] New: konsole crashes when the window is closed
https://bugs.kde.org/show_bug.cgi?id=360433 Bug ID: 360433 Summary: konsole crashes when the window is closed Product: konsole Version: 15.12.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: i...@bluelupo.net The KDE console crashes reproducibly when they stopped using the menu or by pressing CTRL-D. So you can console not leave without a crash. Here the trace report: Application: Konsole (konsole), signal: Floating point exception Using host libthread_db library "/usr/lib/libthread_db.so.1". [KCrash Handler] #5 0x7f312c4eec19 in pthread_barrier_destroy () from /usr/lib/libpthread.so.0 #6 0x7f311d74196f in ?? () from /usr/lib/xorg/modules/dri/swrast_dri.so #7 0x7f311d74d441 in ?? () from /usr/lib/xorg/modules/dri/swrast_dri.so #8 0x7f311d3ec54f in ?? () from /usr/lib/xorg/modules/dri/swrast_dri.so #9 0x7f311d3ec5f5 in ?? () from /usr/lib/xorg/modules/dri/swrast_dri.so #10 0x7f311d3eaa2f in ?? () from /usr/lib/xorg/modules/dri/swrast_dri.so #11 0x7f312b467522 in ?? () from /usr/lib/libGL.so.1 #12 0x7f312b443506 in ?? () from /usr/lib/libGL.so.1 #13 0x7f312b443589 in ?? () from /usr/lib/libGL.so.1 #14 0x7f312b4436de in ?? () from /usr/lib/libGL.so.1 #15 0x7f312e096c52 in XCloseDisplay () from /usr/lib/libX11.so.6 #16 0x7f3120e0edd6 in QXcbConnection::~QXcbConnection() () from /usr/lib/libQt5XcbQpa.so.5 #17 0x7f3120e0f139 in QXcbConnection::~QXcbConnection() () from /usr/lib/libQt5XcbQpa.so.5 #18 0x7f3120e10bd6 in QXcbIntegration::~QXcbIntegration() () from /usr/lib/libQt5XcbQpa.so.5 #19 0x7f3120e10ce9 in QXcbIntegration::~QXcbIntegration() () from /usr/lib/libQt5XcbQpa.so.5 #20 0x7f3130fb7983 in QGuiApplicationPrivate::~QGuiApplicationPrivate() () from /usr/lib/libQt5Gui.so.5 #21 0x7f313156e029 in QApplicationPrivate::~QApplicationPrivate() () from /usr/lib/libQt5Widgets.so.5 #22 0x7f3130cb7408 in QObject::~QObject() () from /usr/lib/libQt5Core.so.5 #23 0x7f313156fe19 in QApplication::~QApplication() () from /usr/lib/libQt5Widgets.so.5 #24 0x7f31344c7468 in kdemain () from /usr/lib/libkdeinit5_konsole.so #25 0x7f313411c710 in __libc_start_main () from /usr/lib/libc.so.6 #26 0x00400779 in _start () Konsole version: 15.12.2-1 Kernel version: 4.4.5-1-MANJARO Linux Distribution: Manjaro (unstable) Reproducible: Always Steps to Reproduce: 1. start konsole 2. close konsole 3. crash If I can still more are required on the system that still choose to be happy here. -- You are receiving this mail because: You are watching all bug changes.
