[kactivitymanagerd] [Bug 371150] Black screen is when more than one type of activity is applied

[bluelupo via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=371150

--- Comment #12 from bluelupo  ---
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

[bluelupo via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=371150

--- Comment #10 from bluelupo  ---
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

[bluelupo via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=371150

--- Comment #7 from bluelupo  ---
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

[bluelupo via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=371150

--- Comment #5 from bluelupo  ---
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

[bluelupo via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=371150

--- Comment #3 from bluelupo  ---
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

[bluelupo via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=371150

--- Comment #1 from bluelupo  ---
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

[bluelupo via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=371150

bluelupo  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

[bluelupo via KDE Bugzilla]

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

[bluelupo via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=370301

--- Comment #3 from bluelupo  ---
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

[bluelupo via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=370301

--- Comment #2 from bluelupo  ---
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

[bluelupo via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=370301

--- Comment #1 from bluelupo  ---
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

[bluelupo via KDE Bugzilla]

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

[bluelupo via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=369145

--- Comment #1 from bluelupo  ---
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

[bluelupo via KDE Bugzilla]

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

[bluelupo via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365959

--- Comment #8 from bluelupo  ---
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

[bluelupo via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365959

--- Comment #6 from bluelupo  ---
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

[bluelupo via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365959

--- Comment #4 from bluelupo  ---
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

[bluelupo via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365959

bluelupo  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

[bluelupo via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365959

--- Comment #2 from bluelupo  ---
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

[bluelupo via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365959

--- Comment #1 from bluelupo  ---
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

[bluelupo via KDE Bugzilla]

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

[bluelupo via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362435

--- Comment #12 from bluelupo  ---
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

[bluelupo via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362435

--- Comment #9 from bluelupo  ---
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

[bluelupo via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362435

--- Comment #8 from bluelupo  ---
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

[bluelupo via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362435

--- Comment #7 from bluelupo  ---
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

[bluelupo via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362435

--- Comment #6 from bluelupo  ---
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

[bluelupo via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362435

--- Comment #5 from bluelupo  ---
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

[bluelupo via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362435

--- Comment #4 from bluelupo  ---
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

[bluelupo via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362435

--- Comment #3 from bluelupo  ---
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

[bluelupo via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362435

--- Comment #1 from bluelupo  ---
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

[bluelupo via KDE Bugzilla]

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.