[kwin] [Bug 461657] Night color does not deactivate when waking the computer up from sleep

2023-06-10 Thread hchain
https://bugs.kde.org/show_bug.cgi?id=461657

hchain  changed:

   What|Removed |Added

 CC||he...@henri-chain.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 439169] Autostart not working after changing my $XDG_CONFIG_HOME

2021-06-28 Thread hchain
https://bugs.kde.org/show_bug.cgi?id=439169

--- Comment #5 from hchain  ---
I think the only way to properly set XDG_CONFIG_HOME is through
/etc/security/pam_env.conf

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 438222] Task Manager doesn't update title of window under specific conditions

2021-06-10 Thread hchain
https://bugs.kde.org/show_bug.cgi?id=438222

hchain  changed:

   What|Removed |Added

 Status|CONFIRMED   |ASSIGNED

--- Comment #8 from hchain  ---
You're correct, the commit introduced a bug.

Fixed in https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/924

Now you should have the title work as expected, and also switching from any app
to the *playlist* window should mark audacious as the current focused task as
expected (this didn't work before).

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 436439] plasma-workspace 93f9ef030 broke my autostart scripts -- repeating the conversion

2021-05-04 Thread hchain
https://bugs.kde.org/show_bug.cgi?id=436439

--- Comment #3 from hchain  ---
Are you sure you didn't have autostart and autostart-scripts symlinked before ?
I don't see how whatever.desktop.desktop.desktop could happen otherwise
(autostart should only contain .desktop files, and autostart-scripts, which is
the only one looked at by the migration, should only contain scripts).

What's more, the migration does attempt to avoid running more than once, by
either deleting the autostart-scripts directory if it is empty after the
migration, or renaming it to old-autostart-scripts if there are still files
inside.

Could the renaming have failed on your machine ? perhaps due to a permission
issue ?

It looks to me like the multiple copies happened as a result of your trying to
fix the other issue (with the argv[0] being different since the move to
.desktop files)

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 433333] [systemd] Enabling systemdBoot breaks 'startkde'

2021-03-03 Thread hchain
https://bugs.kde.org/show_bug.cgi?id=43

hchain  changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
  Latest Commit||https://invent.kde.org/plas
   ||ma/plasma-workspace/commit/
   ||1c7e3064d88d13fb4a03aba41bd
   ||6d5ac7ca832e7
 Resolution|--- |FIXED

--- Comment #11 from hchain  ---
Git commit 1c7e3064d88d13fb4a03aba41bd6d5ac7ca832e7 by Henri Chain, on behalf
of David Edmundson.
Committed on 03/03/2021 at 14:41.
Pushed by davidedmundson into branch 'master'.

Fix query of StartPlasma::hasSystemdService

ListUnitByNames did not quite work as the author (me) expected. Whilst a
search for "adsfasf" yeilded an empty list a well-formed name like
"asdfasdf.service" would return a result to say that service was not
loaded.

This means our runtime detection of xdg-autostart-generator failed.

By using ListUnitFilesByPatterns we can filter on the status in the
query, meaning this code works again. We also can query the case of it
being available but explicitly disabled.

M  +3-3startkde/startplasma.cpp

https://invent.kde.org/plasma/plasma-workspace/commit/1c7e3064d88d13fb4a03aba41bd6d5ac7ca832e7

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 432364] [systemd] plasma-ksmserver.service blocks boot if ksplash is disabled

2021-02-17 Thread hchain
https://bugs.kde.org/show_bug.cgi?id=432364

hchain  changed:

   What|Removed |Added

  Latest Commit||https://invent.kde.org/plas
   ||ma/plasma-workspace/commit/
   ||e7e49916712d2d8efc65d7da172
   ||1eb1d31dc65d6
 Status|ASSIGNED|RESOLVED
 Resolution|--- |FIXED

--- Comment #6 from hchain  ---
Git commit e7e49916712d2d8efc65d7da1721eb1d31dc65d6 by Henri Chain, on behalf
of David Edmundson.
Committed on 17/02/2021 at 09:53.
Pushed by davidedmundson into branch 'master'.

Move ksmserver's ksplash notifying to ksmserver

Previously the call to ksplash was being emitted by plasma-session. This
isn't used in the systemd startup so it was introduced in a somewhat
messy script.

This script has an issue:

If ksplash is disabled the bus name won't be registered. Typically this
isn't an issue. However to avoid a race condition ksplash registers
itself as being DBus activatable, so that the dbus server holds
dispatching the message.

This combo means ksmserver our unit is considered as not running until
our script times out. This then defers other things in the chain that
depend on ksmserver.

Moving the call into the relevant piece of code into ksmserver unifies
things into a single path and gives us more control.

M  +0-2ksmserver/plasma-ksmserver.service.in
M  +7-0ksmserver/server.cpp
M  +0-1startkde/plasma-session/startup.cpp

https://invent.kde.org/plasma/plasma-workspace/commit/e7e49916712d2d8efc65d7da1721eb1d31dc65d6

-- 
You are receiving this mail because:
You are watching all bug changes.

[pimsettingexporter] [Bug 429895] PIM Data Exporter cannot import data in zip

2021-01-05 Thread hchain
https://bugs.kde.org/show_bug.cgi?id=429895

--- Comment #6 from hchain  ---
deleting exportdatatype.xml from the zip fixes the issue

-- 
You are receiving this mail because:
You are watching all bug changes.

[pimsettingexporter] [Bug 429895] PIM Data Exporter cannot import data in zip

2021-01-05 Thread hchain
https://bugs.kde.org/show_bug.cgi?id=429895

hchain  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

--- Comment #5 from hchain  ---
same here

-- 
You are receiving this mail because:
You are watching all bug changes.

[pimsettingexporter] [Bug 429895] PIM Data Exporter cannot import data in zip

2020-12-01 Thread hchain
https://bugs.kde.org/show_bug.cgi?id=429895

--- Comment #1 from hchain  ---
Created attachment 133773
  --> https://bugs.kde.org/attachment.cgi?id=133773=edit
zip contents

-- 
You are receiving this mail because:
You are watching all bug changes.

[pimsettingexporter] [Bug 429895] New: PIM Data Exporter cannot import data in zip

2020-12-01 Thread hchain
https://bugs.kde.org/show_bug.cgi?id=429895

Bug ID: 429895
   Summary: PIM Data Exporter cannot import data in zip
   Product: pimsettingexporter
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: mon...@kde.org
  Reporter: henri.ch...@enioka.com
  Target Milestone: ---

Created attachment 133772
  --> https://bugs.kde.org/attachment.cgi?id=133772=edit
empty selection

SUMMARY
PIM Data Exporter cannot import its own exports.

STEPS TO REPRODUCE
1. export settings to zip
2. try to import zip

OBSERVED RESULT
no data is shown in the "Select Type" dialog

EXPECTED RESULT
settings that were exported should be visible and selectable

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.13
KDE Frameworks Version: 5.76.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
The zip file looks correct and contains many files which can also be seen in
the "show archive information" window

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 426902] Unlock fails even with correct password

2020-11-28 Thread hchain
https://bugs.kde.org/show_bug.cgi?id=426902

hchain  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Resolution|DOWNSTREAM  |---
 Status|RESOLVED|REOPENED

--- Comment #13 from hchain  ---
I don't think this is it. It fails to unlock even on the first (correct)
attempt. Also I only get the issue with master, when I switch back to 5.20.3
the problem disappears. I'm also using Arch Linux however

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 426902] Unlock fails even with correct password

2020-10-21 Thread hchain
https://bugs.kde.org/show_bug.cgi?id=426902

--- Comment #10 from hchain  ---
Qt: Session management error: Could not open network socket
Locked at 1603268712
file:///usr/lib/qt/qml/QtQuick/Controls.2/ToolButton.qml: QML IconImage: Error
decoding: file:///usr/share/icons/breeze-dark/actions/22/edit-copy.svg:
Unsupported image format
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/VirtualKeyboard.qml:20:1:
module "QtQuick.VirtualKeyboard" is not installed
file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/osd/OsdItem.qml:50:9:
Unable to assign [undefined] to double
file:///usr/lib/qt/qml/org/kde/plasma/components.3/TextField.qml:36:
ReferenceError: textField is not defined
file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/VirtualKeyboard.qml:20:1:
module "QtQuick.VirtualKeyboard" is not installed
file:///usr/lib/qt/qml/org/kde/plasma/components.3/TextField.qml:36:
ReferenceError: textField is not defined
file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/osd/OsdItem.qml:50:9:
Unable to assign [undefined] to double
QXcbClipboard: SelectionRequest too old
QXcbClipboard: SelectionRequest too old
QXcbClipboard: SelectionRequest too old
QXcbClipboard: SelectionRequest too old
QXcbClipboard: SelectionRequest too old
QXcbClipboard: SelectionRequest too old
QXcbClipboard: SelectionRequest too old
QXcbClipboard: SelectionRequest too old
QXcbClipboard: SelectionRequest too old
QXcbClipboard: SelectionRequest too old
QXcbClipboard: SelectionRequest too old
QXcbClipboard: SelectionRequest too old
QXcbClipboard: SelectionRequest too old
QXcbClipboard: SelectionRequest too old
QXcbClipboard: SelectionRequest too old
QXcbClipboard: SelectionRequest too old
QXcbClipboard: SelectionRequest too old
QXcbClipboard: SelectionRequest too old
QXcbClipboard: SelectionRequest too old
QXcbClipboard: SelectionRequest too old
Authentication failure

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 426902] Unlock fails even with correct password

2020-10-21 Thread hchain
https://bugs.kde.org/show_bug.cgi?id=426902

hchain  changed:

   What|Removed |Added

 CC||henri.ch...@enioka.com

--- Comment #9 from hchain  ---
Reproduced (no virtual keyboard)

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kconfig] [Bug 425953] undefined reference to `KWindowConfig::allConnectedScreens()'

2020-09-02 Thread hchain
https://bugs.kde.org/show_bug.cgi?id=425953

hchain  changed:

   What|Removed |Added

 CC||henri.ch...@enioka.com

--- Comment #6 from hchain  ---
fix: https://invent.kde.org/frameworks/kconfig/-/merge_requests/22

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kconfig] [Bug 418146] kconfig_compiler with GenerateProperties creates uncompilable/wrong code

2020-02-25 Thread hchain
https://bugs.kde.org/show_bug.cgi?id=418146

hchain  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 CC||henri.ch...@enioka.com
 Status|REPORTED|RESOLVED

--- Comment #3 from hchain  ---
Closed by https://phabricator.kde.org/D27497

-- 
You are receiving this mail because:
You are watching all bug changes.