from:"C."

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

Gabriel C  changed:

   What|Removed |Added

   Severity|wishlist|normal
 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED
 CC||nix.or@gmail.com

--- Comment #1 from Gabriel C  ---
Well there is not even a notice by cmake about system-config-printer being
needed

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

[print-manager] [Bug 320326] print-manager looking for org.fedoraproject.Config.Printing

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

Gabriel C  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Ever confirmed|0   |1
 Resolution|INVALID |---
 CC||nix.or@gmail.com

--- Comment #8 from Gabriel C  ---
I can't see how this bug is invalid. Users and Distros are not reading your
blogs. Please be nice and add s-cp as runtime depend  to print-managers build
system so everyone knows what s-c-p is about. thx

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

[ksnapshot] [Bug 371744] screen capture doesn't display the actual screen

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

Gabriel C  changed:

   What|Removed |Added

 CC||nix.or@gmail.com

--- Comment #1 from Gabriel C  ---
Ksnapshot is replaced by spectacle. Please try spectacle first.

Regards

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

[gwenview] [Bug 371733] Gwenview crashings when trying to open videos

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

Gabriel C  changed:

   What|Removed |Added

 CC||nix.or@gmail.com
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Gabriel C  ---


*** This bug has been marked as a duplicate of bug 335111 ***

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

[phonon-backend-vlc] [Bug 335111] vlc crashes phonon by mixing qt4 and qt5

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

Gabriel C  changed:

   What|Removed |Added

 CC||grglsn...@gmail.com

--- Comment #89 from Gabriel C  ---
*** Bug 371733 has been marked as a duplicate of this bug. ***

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

[kwin] [Bug 449982] New: Gradient effect applied to left and right window borders

2022-02-10 Thread Blaise C.

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

Bug ID: 449982
   Summary: Gradient effect applied to left and right window
borders
   Product: kwin
   Version: 5.24.0
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: aurorae
  Assignee: kwin-bugs-n...@kde.org
  Reporter: scribe.awo...@gmail.com
  Target Milestone: ---

Created attachment 146562
  --> https://bugs.kde.org/attachment.cgi?id=146562&action=edit
A screenshot of the graphical bug on display.

SUMMARY
When using many Aurorae themes, a vertical gradient is applied to the left and
right window borders. This is most apparent on VinceLiuice's Graphite theme and
its derivatives due to the thick, contrasting outlines it uses, though this is
also present in other themes, like eliverlara's Nordic theme. Notably this
seems to happen in themes where the bottom corners have a different shape than
the top corners.

Some observations across different themes:
- When the border size is set to normal or larger, both the left and right
borders are affected on Graphite and Graphite-Round
- When the size is set to Tiny, neither side border is affected on the round
variations on Graphite, but the right border is still affected on normal
Graphite

STEPS TO REPRODUCE
1. Apply certain Aurorae themes (most apparent with VinceLiuice's Graphite
themes, but also subtly present on eliverlara's Nordic theme)
2. Open Qt program.

OBSERVED RESULT
The side window decorations have a gradient effect applied to them

EXPECTED RESULT
The side window decorations should look identical to how they look in the .svg
file.

SOFTWARE/OS VERSIONS
Linux: openSUSE Tumbleweed 20220207
(available in About System)
KDE Plasma Version: 5.24.0 
KDE Frameworks Version: 5.90.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
Screen resolution is 1366x768.

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

[Bluedevil] [Bug 449178] KCM and Applet no longer show paired devices after turning bluetooth off and on again; have to restart plasmashell or leave/return to the KCM

2022-02-15 Thread Mathias C.

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

Mathias C.  changed:

   What|Removed |Added

 CC||mathias.cilibe...@gmail.com

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

[plasmashell] [Bug 353975] Black screen on second display (no wallpaper, can't get a context menu on right-click)

2022-05-29 Thread gene c

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

--- Comment #170 from gene c  ---
Hi @Nate:
Results of testing with Archlinux 5.24.90 from kde-unstable repo.

Good:
 - Both monitor desktops continue to work after idle and wake cycle (yay) which
means the major bug is fixed. 

Bad (ish):
 - After idle/resume all windows are pushed to 1 of the 2 monitors.  This has
one usb-c and one hdmi - so feels like timing issue to me
 - Tons of messages logged to journal 
   - plasmashell[xxx]: IPDL protocol error: Handler returned error code!
 plasmashell[xxx]###!!! [Parent][DispatchAsyncMessage] 
Error: PClientManager::Msg_ExpectFutureClientSource Processing
error: message was deserialized, but the handler returned false
(indicating failure)

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

[plasmashell] [Bug 353975] Black screen on second display (no wallpaper, can't get a context menu on right-click)

2022-05-29 Thread gene c

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

--- Comment #171 from gene c  ---
Per my last test - this is wayland desktop started by sddm running wayland. So
no Xorg involved anywhere.

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

[plasmashell] [Bug 353975] Black screen on second display (no wallpaper, can't get a context menu on right-click)

2022-05-30 Thread gene c

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

--- Comment #173 from gene c  ---
I can regularly crash plasmashell by simply editing (1 of the 2)  panel and
adding (or trying to add) applications from kmenu - not convinced this wasn't
commonplace in released version though. 

I did this as after updating to 5.24.90 all customized panel settings were
lost. i gave up after multiple tries,  added default panel and use quick
launcher now - which at least don't crash and vanish :)

This is beta and bugs are expected.

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

[plasmashell] [Bug 455538] New: Option to keep floating panels -floating- when windows are maximized

2022-06-18 Thread Damian C

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

Bug ID: 455538
   Summary: Option to keep floating panels -floating- when windows
are maximized
   Product: plasmashell
   Version: 5.25.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: Panel
  Assignee: plasma-b...@kde.org
  Reporter: dcalv...@gmail.com
CC: niccolo.venera...@gmail.com
  Target Milestone: 1.0

Created attachment 149885
  --> https://bugs.kde.org/attachment.cgi?id=149885&action=edit
example of the "desired" result but with a non maximized window

SUMMARY
***
Normally when using a floating panel, maximizing a window and having the
floating panel become a "normal" (ie, non floating) panel makes sense as it
would look ugly and incoherent with the maximized window.

However I'm using the "Maximized Window Gap" Kwin Script, and with it my
maximized windows have a gap around them, and when these windows are not
maximized (but taking the same space as the maximized window) it looks like
both the window and the panel are floating over the background and to me it
looks quite cool.

However when I maximize any window while using the kwin script and the floating
panel, the panel acts as it was designed to and becomes "non floating", thus
breaking the look of both elements (the window, and the panel) floating.

I know this is probably quite a niche scenario, but I'd love to have such
option.
Something similar but not quite the same has been requested under bug #454950.

It will make more sense with the screenshot, which shows more or less an
example of the "desired" result but with a non maximized window, which doesn't
look quite exactly right as I basically had to set the window size manually to
more or less match what it looks like when maximized with the kwin script
enable, but it will surely illustrate the point.

***


STEPS TO REPRODUCE
1. Enable Floating Panel.
2. Be using Kwin Script "Maximized Window Gap"
3. Maximize a window.

OBSERVED RESULT
The floating panel becomes a "normal" panel and docks to the bottom of the
screen.

EXPECTED RESULT
That the floating panel remains floating the same as if there was no maximized
window.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.25.0
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.4
Kernel Version: 5.18.3-zen1-1-zen (64-bit)
Graphics Platform: X11
Processors: 12 × Intel® Core™ i7-8700K CPU @ 3.70GHz
Memory: 15.5 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2

ADDITIONAL INFORMATION

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

[systemsettings] [Bug 465631] New: Opening Window Decorations crashes System Setttings

2023-02-12 Thread Ben C

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

Bug ID: 465631
   Summary: Opening Window Decorations crashes System Setttings
Classification: Applications
   Product: systemsettings
   Version: 5.26.5
  Platform: Kubuntu
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: coppr...@gmail.com
  Target Milestone: ---

Application: systemsettings (5.26.5)

Qt Version: 5.15.8
Frameworks Version: 5.102.0
Operating System: Linux 6.1.9-060109-generic x86_64
Windowing System: X11
Distribution: Ubuntu Lunar Lobster (development branch)
DrKonqi: 5.26.5 [KCrashBackend]

-- Information about the crash:
Happened even if I tired it immediately after a reboot.

The crash can be reproduced every time.

-- Backtrace:
Application: System Settings (systemsettings), signal: Segmentation fault

[KCrash Handler]
#4  0x7f5373b0a198 in QVariant::toMap() const () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f535541d4fd in KDecoration2::Decoration::Decoration(QObject*,
QList const&) () from /lib/x86_64-linux-gnu/libkdecorations2.so.5
#6  0x7f53553b53fd in ?? () from
/usr/lib/x86_64-linux-gnu/qt5/plugins/org.kde.kdecoration2/breezedecoration.so
#7  0x7f53745b2373 in KPluginFactory::create(char const*, QWidget*,
QObject*, QList const&, QString const&) () from
/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5
#8  0x7f53553f313d in ?? () from
/usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kwin/private/kdecoration/libkdecorationprivatedeclarative.so
#9  0x7f53553f33eb in ?? () from
/usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kwin/private/kdecoration/libkdecorationprivatedeclarative.so
#10 0x7f5371700ab3 in
QQmlObjectCreator::finalize(QQmlInstantiationInterrupt&) () from
/lib/x86_64-linux-gnu/libQt5Qml.so.5
#11 0x7f5371695fd2 in
QQmlIncubatorPrivate::incubate(QQmlInstantiationInterrupt&) () from
/lib/x86_64-linux-gnu/libQt5Qml.so.5
#12 0x7f5371696475 in QQmlEnginePrivate::incubate(QQmlIncubator&,
QQmlContextData*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
#13 0x7f5370f5dbff in ?? () from /lib/x86_64-linux-gnu/libQt5QmlModels.so.5
#14 0x7f5371d26c74 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#15 0x7f5371d188c5 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#16 0x7f5371d25463 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#17 0x7f5371d2cae8 in QQuickItemView::componentComplete() () from
/lib/x86_64-linux-gnu/libQt5Quick.so.5
#18 0x7f5371700ab3 in
QQmlObjectCreator::finalize(QQmlInstantiationInterrupt&) () from
/lib/x86_64-linux-gnu/libQt5Qml.so.5
#19 0x7f5371695fd2 in
QQmlIncubatorPrivate::incubate(QQmlInstantiationInterrupt&) () from
/lib/x86_64-linux-gnu/libQt5Qml.so.5
#20 0x7f5371696475 in QQmlEnginePrivate::incubate(QQmlIncubator&,
QQmlContextData*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
#21 0x7f537168fc38 in QQmlComponent::create(QQmlIncubator&, QQmlContext*,
QQmlContext*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
#22 0x7f53729444fb in
KDeclarative::QmlObject::completeInitialization(QHash
const&) () from /lib/x86_64-linux-gnu/libKF5Declarative.so.5
#23 0x7f537217c32d in KQuickAddons::ConfigModule::mainUi() () from
/lib/x86_64-linux-gnu/libKF5QuickAddons.so.5
#24 0x7f53745152df in KCModuleLoader::loadModule(KPluginMetaData const&,
QWidget*, QList const&) () from
/lib/x86_64-linux-gnu/libKF5KCMUtils.so.5
#25 0x7f53745186ad in ?? () from /lib/x86_64-linux-gnu/libKF5KCMUtils.so.5
#26 0x7f5374518cd8 in KCModuleProxy::realModule() const () from
/lib/x86_64-linux-gnu/libKF5KCMUtils.so.5
#27 0x7f537520d2e8 in ModuleView::updatePageIconHeader(KPageWidgetItem*) ()
from /lib/x86_64-linux-gnu/libsystemsettingsview.so.3
#28 0x7f537520e6aa in ModuleView::addModule(MenuItem*, QStringList const&)
() from /lib/x86_64-linux-gnu/libsystemsettingsview.so.3
#29 0x7f535d56dcb5 in ?? () from
/usr/lib/x86_64-linux-gnu/qt5/plugins/systemsettingsview/systemsettings_sidebar_mode.so
#30 0x7f535d5703ad in ?? () from
/usr/lib/x86_64-linux-gnu/qt5/plugins/systemsettingsview/systemsettings_sidebar_mode.so
#31 0x7f535d570fdb in ?? () from
/usr/lib/x86_64-linux-gnu/qt5/plugins/systemsettingsview/systemsettings_sidebar_mode.so
#32 0x7f53716d0433 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
#33 0x7f53715a9901 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
#34 0x7f53715ab7e0 in QV4::QObjectMethod::callInternal(QV4::Value const*,
QV4::Value const*, int) const () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
#35 0x7f53715c88ad in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
#36 0x7f53715cc027 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
#37 0x7f537155d4a6 in QV4::Function::call(QV4::Value const*, QV4::Value
const*, int, QV4::ExecutionContext const*) () from
/lib/x86_64-linux-gnu/libQt5Qml.

[systemsettings] [Bug 465631] Opening Window Decorations crashes System Setttings

2023-02-13 Thread Ben C

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

--- Comment #2 from Ben C  ---
Thanks for the heads up and analysis! I’ll have a look and sort it out. Much
appreciated!

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

[plasmashell] [Bug 458038] On X11, widgets still inappropriately move after login after panel appears

2023-02-21 Thread Damian C

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

--- Comment #21 from Damian C  ---
Confirmed, the issue is no longer happening. Thank you!

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

[KScreen] [Bug 466434] New: Monitor frequently fails to go to sleep and corruption occurs after it attempts to or is shut off.

2023-02-25 Thread C Schell

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

Bug ID: 466434
   Summary: Monitor frequently fails to go to sleep and corruption
occurs after it attempts to or is shut off.
Classification: Plasma
   Product: KScreen
   Version: 5.27.1
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: common
  Assignee: kscreen-bugs-n...@kde.org
  Reporter: kdeb...@schells.com
  Target Milestone: ---

Created attachment 156733
  --> https://bugs.kde.org/attachment.cgi?id=156733&action=edit
journalctl output when the bug occurs

SUMMARY

On 5.27.0 I had the kded5 crashes after the monitor went to sleep or was
manually powered off.

After upgrade to 5.27.1 while that no longer happens, now there is another
problem with random behavior after the monitor attempts to go to sleep or is
powered off.  On my normal account when typically the monitor should go to
sleep instead the monitor wakes back up but most of my desktop icons are
missing, sometimes terminal output is messed up, etc.

For the general problem though I'll discuss what happens with a brand new
account with entirely default configuration.

STEPS TO REPRODUCE
1.   Create a new account
2.   Let the screen timeout.  (Either the default 10 minutes or do "xset dpms 5
6 7" to speed things up
3.   At first everything is fine.  Monitor goes to sleep.
4.   Open a konsole and run "sudo journalctl -f"
5.   Let the monitor try to go to sleep again, it won't.  (Usually, sometimes
I've had to move back to the konsole that I ran xset in, or do something to
start the bug.)

OBSERVED RESULT
The monitor will not go to sleep and instead just before it should the desktop
will wake back up.  There may be corruption of open apps and the Desktop.

The journalctl fills with lines from kscreen like in the attachment.  This
journalctl output does not occur when the monitor goes to sleep and wakes back
up correctly.

EXPECTED RESULT
The monitor should go to sleep.  When the session is resumed the desktop and
all applications should be as they were before the monitor went to sleep.   The
logs should not fill with information about the screen after every sleep/wake
cycle.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma:  Opensuse Tumbleweed
KDE Plasma Version: 5.27.1
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8

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

[KScreen] [Bug 466434] Monitor frequently fails to go to sleep and corruption occurs after it attempts to or is shut off.

2023-02-28 Thread C Schell

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

C Schell  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |NOT A BUG

--- Comment #1 from C Schell  ---
This seems to be a hardware (firmware) issue.  It only happens with one monitor
and only when connected via HDMI.

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

[Discover] [Bug 448551] Could not open appstream://org.kde.kate.desktop

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

--- Comment #8 from Martin C.  ---
Hi all,

Today I've got the same error (Fedora Silverblue 36 Kinoite) when trying to
install Kalendar:
/*
Could not open appstream://org.kde.kalendar because it was not found in any
available software repositories. Please report this issue to the packagers of
your distribution.
*/

If I go ahead and hit the Report this issue button it sends me to RedHat's
Bugzilla -- should I open a ticket there too and link both issues?

Thanks!

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

[Discover] [Bug 448551] Could not open appstream://org.kde.kate.desktop

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

Martin C.  changed:

   What|Removed |Added

Version|5.23.4  |5.25.4

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

[Discover] [Bug 448551] Could not open appstream://org.kde.kate.desktop

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

--- Comment #9 from Martin C.  ---
Bumped the KDE Plasma version reported in my original issue to 5.25.4

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

[Discover] [Bug 448551] Could not open appstream://org.kde.kate.desktop

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

--- Comment #10 from Martin C.  ---
(In reply to Timothée Ravier from comment #7)
> (In reply to thenujan from comment #6)
> > trying to install any app from apps.kde.org results in this error 
> > 
> > OS manjaro 
> > plasma version 5.23.5
> > kde frameworks version 5.90
> 
> This is not the same bug. This one is only for the rpm-ostree backend.
> Please file a new one.

I could try packaging Kate and Kalendar for Flatpak to contribute back to your
awesome work guys; could you point me to any documentation that describes how
to do so for KDE applications?

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

[kmines] [Bug 406749] Minesweeper Crashes

2022-09-21 Thread James C

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

--- Comment #2 from James C  ---
 It's been so long I can't tell.I don't currently have kmines installed on the
current version of fedora.

On Tuesday, September 20, 2022 at 08:42:19 PM MST, Justin Zobel
 wrote:  

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

Justin Zobel  changed:

          What    |Removed                    |Added

        Resolution|---                        |WAITINGFORINFO
            Status|REPORTED                    |NEEDSINFO

--- Comment #1 from Justin Zobel  ---
Thank you for reporting this crash in KDE software. As it has been a while
since this issue was reported, can we please ask you to see if you can
reproduce the crash with a recent software version?

If you can reproduce the issue, please change the status to "CONFIRMED" when
replying. Thank you!

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

[plasmashell] [Bug 435715] Plasma crashes in SystemTrayContainer::internalSystrayChanged() on start

2022-09-22 Thread gene c

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

gene c  changed:

   What|Removed |Added

 CC|gj...@sapience.com  |

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

[kontact] [Bug 438345] Contents load as Blank Page in Wayland - Kmail and Akregator

2023-04-11 Thread Damian C

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

--- Comment #10 from Damian C  ---
(In reply to Adam Borsos from comment #9)
> QTWEBENGINE_CHROMIUM_FLAGS="--disable-gpu-compositing" works me as a
> workaround, so the issue seems to be HW accel related
> 
> (Operating System: Gentoo Linux 2.13
> KDE Plasma Version: 5.27.4
> KDE Frameworks Version: 5.104.0
> Qt Version: 5.15.8
> Kernel Version: 6.1.19-gentoo-x86_64 (64-bit)
> Graphics Platform: Wayland
> Processors: 12 × AMD Ryzen 5 5600G with Radeon Graphics
> Memory: 31.2 GiB of RAM
> Graphics Processor: NVIDIA GeForce RTX 3070 Ti/PCIe/SSE2)

This works for me as well! Also works for the news feed.

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

[kmail2] [Bug 460687] "Forward To" option missing from Filter Actions

2023-04-15 Thread Damian C

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

Damian C  changed:

   What|Removed |Added

 CC||dcalv...@gmail.com

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

[plasmashell] [Bug 450062] Plasma 5.25 + Wayland: When disconnecting 2nd monitor, icon positions get reset

2023-04-18 Thread C. Kimna

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

C. Kimna  changed:

   What|Removed |Added

 CC||ki...@gmx.de
Version|5.27.0  |5.27.4
   Platform|Other   |Neon
 Status|RESOLVED|REOPENED
 Resolution|FIXED   |---

--- Comment #14 from C. Kimna  ---
Same here, since some months. After switching signal input from monitor and
back to KDE
all icons positions are reset. On Wayland AND xorg.

kscreen-console monitor displays while switching to other signal:
Priorities changed: QMap()
qt.qpa.wayland: Creating a fake screen in order for Qt not to crash


I've tested disabling kscreen, but the same issue here.

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

[plasmashell] [Bug 450062] Plasma 5.25 + Wayland: When disconnecting 2nd monitor, icon positions get reset

2023-04-18 Thread C. Kimna

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

--- Comment #15 from C. Kimna  ---
Plasma version 5.27.4 KDE Neon

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

[plasmashell] [Bug 468665] New: Plasma 5.27.4: Desktop icon positions get reset after changing monitor signal or reconnecting cable

2023-04-18 Thread C. Kimna

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

Bug ID: 468665
   Summary: Plasma 5.27.4: Desktop icon positions get reset after
changing monitor signal or reconnecting cable
Classification: Plasma
   Product: plasmashell
   Version: 5.27.4
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Folder
  Assignee: plasma-b...@kde.org
  Reporter: ki...@gmx.de
CC: h...@kde.org
  Target Milestone: 1.0

SUMMARY
Situation: Monitor with multi-signal input. After switching back to KDE the
icon positions on
desktop have been reset. Same issue after disconnecting monitor cable.


STEPS TO REPRODUCE
1. switch to another signal on monitor or plug off the monitor cable.
2. switch back to signal to KDE or replug the cable


OBSERVED RESULT
Desktop icons get reset to default positions (populating the top of the screen)

EXPECTED RESULT
Desktop icons hold their positions.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Neon 5.27
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.105.0
Qt Version: 5.15.8
Kernel Version: 5.15.0-69-generic 64-Bit


ADDITIONAL INFORMATION
Wayland: issue is persisting after removing kscreen.
Xorg: issue is gone after removing kscreen.

"kscreen-console monitor" displays while switching to other signal:
Priorities changed: QMap()
qt.qpa.wayland: Creating a fake screen in order for Qt not to crash

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

[neon] [Bug 433896] snap version outdated

2023-04-21 Thread C. Sonnleitner

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

C. Sonnleitner  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #3 from C. Sonnleitner  ---
I moved away from snap. But it looks like the snap version of okular has been
updated to multiple newer version.

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

[kwin] [Bug 450327] Night Color Has No Effect on KDE Wayland with NVIDIA

2023-04-23 Thread Damian C

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

Damian C  changed:

   What|Removed |Added

 CC||dcalv...@gmail.com

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

[kwin] [Bug 450327] Night Color Has No Effect on KDE Wayland with NVIDIA

2023-04-23 Thread Damian C

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

--- Comment #5 from Damian C  ---
I want to add that with the Night Color feature enabled, each time the
"kwin_wayland_drm: Failed to create gamma blob! Invalid argument" message shows
on the logs, the screen freezes (one of them, the other two won't), and it can
completely freeze the kwin session.

3 monitors: One Display Port, one HDMI and one DVI.

Operating System: Arch Linux 
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.105.0
Qt Version: 5.15.9
Kernel Version: 6.2.12-zen1-1-zen (64-bit)
Graphics Platform: Wayland
Processors: 12 × Intel® Core™ i7-8700K CPU @ 3.70GHz
Memory: 15.6 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2

Nvidia Drivers: 530.41.03-1

Workaround has been to disable this feature completely.

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

[kwin] [Bug 468895] New: Desktop freezes when Night Color feature kicks in running Wayland with NVIDIA proprietary drivers.

2023-04-24 Thread Damian C

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

Bug ID: 468895
   Summary: Desktop freezes when Night Color feature kicks in
running Wayland with NVIDIA proprietary drivers.
Classification: Plasma
   Product: kwin
   Version: 5.27.4
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: dcalv...@gmail.com
  Target Milestone: ---

SUMMARY
***
With the Night Color feature enabled, running Wayland with NVIDIA proprietary
drivers, one or more monitors freezes momentarily. If left unattended the whole
kwin session freezes on all monitors.

On the logs, the message : "kwin_wayland_drm: Failed to create gamma blob!
Invalid argument" can be seen at each time the desktop freezes.

After a few seconds it will unfreeze and let you continue for maybe a minute
more before going at it again, I'm guessing it is the Night Color feature
attempting to start again.



***


STEPS TO REPRODUCE
1. Be running a Kwin Wayland session using Nvidia proprietary drivers.
2. Have the Night Color feature enabled.
3. At the time the Night Color feature is supposed to kick in, the issue is
observed.

OBSERVED RESULT
One or more monitors freezes momentarily. If left unattended the whole kwin
session freezes on all monitors.

EXPECTED RESULT
Night Color works as expected.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.105.0
Qt Version: 5.15.9
Kernel Version: 6.2.12-zen1-1-zen (64-bit)
Graphics Platform: Wayland
Processors: 12 × Intel® Core™ i7-8700K CPU @ 3.70GHz
Memory: 15.6 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2

Nvidia Drivers: 530.41.03-1


ADDITIONAL INFORMATION

3 monitors: One Display Port, one HDMI and one DVI.

It seems to favor freezing the DVI monitor first, but the rest will follow
soon.

To avoid this issue and continue to have a working system through the night
hours, the workaround has been to disable Night Color completely.

Seems related to #450327.

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

[kwin] [Bug 468895] Desktop freezes when Night Color feature kicks in running Wayland with NVIDIA proprietary drivers.

2023-04-24 Thread Damian C

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

Damian C  changed:

   What|Removed |Added

 CC||dcalv...@gmail.com

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

[kwin] [Bug 450327] Night Color Has No Effect on KDE Wayland with NVIDIA

2023-04-24 Thread Damian C

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

--- Comment #7 from Damian C  ---
(In reply to Zamundaaa from comment #6)
> Please create a separate bug report for the freeze

Done, https://bugs.kde.org/show_bug.cgi?id=468895

Thank you,

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

[plasmashell] [Bug 469434] Romanian variant Sun Type 6/7 does not show correctly

2023-05-20 Thread Silviu C.

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

--- Comment #8 from Silviu C.  ---
Today I was testing things with an X11 session. The bug does not happen. I
switched to Wayland and there it was again.

Will attach screenshot.

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

[plasmashell] [Bug 469434] Romanian variant Sun Type 6/7 does not show correctly

2023-05-20 Thread Silviu C.

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

--- Comment #9 from Silviu C.  ---
Created attachment 159127
  --> https://bugs.kde.org/attachment.cgi?id=159127&action=edit
Screenshot showing the problem not manifesting on X11

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

[yakuake] [Bug 470651] New: Can't paste text into a terminal because Yakuek doesn't honors the universal key combination Ctrl+Shift+v

2023-06-04 Thread Martin C.

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

Bug ID: 470651
   Summary: Can't paste text into a terminal because Yakuek
doesn't honors the universal key combination
Ctrl+Shift+v
Classification: Applications
   Product: yakuake
   Version: 23.04.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: h...@kde.org
  Reporter: martincigorr...@gmail.com
  Target Milestone: ---

SUMMARY
***
The option to map a key combination to copy/paste text in the terminal is
missing.
***


STEPS TO REPRODUCE
1. Press Ctrl+Shift+v to try to paste text, as you would do in Konsole (and
basically pretty much every other terminal emulator in the world)
2. Get greeted by a warning message letting you know that the universal
combination is not registered, so you have to head down to the shortcuts
section to fix that

OBSERVED RESULT
There's no such option to map the the `paste` command

EXPECTED RESULT
Pressing the universal key combination would paste the clipboard's text into
the terminal.

SOFTWARE/OS VERSIONS 
Linux/KDE Plasma: Fedora Kinoite 38
(available in About System)
KDE Plasma Version:  5.27.5
KDE Frameworks Version: 5.106.0
Qt Version: 5.15.9

ADDITIONAL INFORMATION

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

[yakuake] [Bug 470651] Can't paste text into a terminal because Yakuake doesn't honors the universal key combination Ctrl+Shift+v

2023-06-04 Thread Martin C.

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

Martin C.  changed:

   What|Removed |Added

Summary|Can't paste text into a |Can't paste text into a
   |terminal because Yakuek |terminal because Yakuake
   |doesn't honors the  |doesn't honors the
   |universal key combination   |universal key combination
   |Ctrl+Shift+v|Ctrl+Shift+v

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

[yakuake] [Bug 470651] Can't paste text into a terminal pane because Yakuake doesn't honors the universal key combination Ctrl+Shift+v

2023-06-04 Thread Martin C.

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

Martin C.  changed:

   What|Removed |Added

Summary|Can't paste text into a |Can't paste text into a
   |terminal because Yakuake|terminal pane because
   |doesn't honors the  |Yakuake doesn't honors the
   |universal key combination   |universal key combination
   |Ctrl+Shift+v|Ctrl+Shift+v

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

[yakuake] [Bug 470651] Can't paste text into a terminal pane because Yakuake doesn't honors the universal key combination Ctrl+Shift+v

2023-06-06 Thread Martin C.

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

Martin C.  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #2 from Martin C.  ---
Hi Justin 👋,

Thank you so much for your prompt reply.

"Is Yakuake installed as a Flatpak or overlayed onto the ostree image?"
- No, I couldn't find a Yakuake Flatpak - I checked both Flathub and KDEApps
(https://userbase.kde.org/Tutorials/Flatpak) -, so I overlayed it.

After checking your comment, I removed the overlayed package without touching
the configuration files, then re-installed it, and now it is working as you
describe (as expected!).

I should have taken a screenshot of the error message when it popped up before
uninstalling Yakuake the first time; I'll make sure to do so next time if I see
it again.

Thanks again!
-Martín

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

[yakuake] [Bug 470651] Can't paste text into a terminal pane because Yakuake doesn't honors the universal key combination Ctrl+Shift+v

2023-06-12 Thread Martin C.

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

--- Comment #3 from Martin C.  ---
Created attachment 159618
  --> https://bugs.kde.org/attachment.cgi?id=159618&action=edit
Yakuake shortcut error message

"Ambiguous shortcut detected" notice is shown when trying to paste text on the
pane created with the shortcut [ Ctrl+Shift+8 ]

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

[yakuake] [Bug 470651] Can't paste text into a terminal pane because Yakuake doesn't honors the universal key combination Ctrl+Shift+v

2023-06-12 Thread Martin C.

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

Martin C.  changed:

   What|Removed |Added

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

--- Comment #4 from Martin C.  ---
Hi all,

It turned out I wasn't crazy after all (at least not that crazy); I hit this
issue again today, check the attached screenshot.

The interesting thing here is that this issue only occurs when trying to paste
text on a pane created with the shortcut Ctrl+Shift+8, which I use a lot in
Konsole to create dynamic panes (with 0 and 9 it works well).

I understand that there might be something else going on here because when
creating a pane using Ctrl+Shift+8 I also can't switch to/from it using Ctrl +
Tab.

Yakuake version is: `yakuake 23.04.2`
Reproducibility: always

Thanks

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

[krita] [Bug 471046] New: Bug in the brush stroke after using Mirror Screen Vertically; Brush duplicated, on the other side of the screen.

2023-06-14 Thread L. C.

compressed_ETC2_RGBA8_texture" 
 "GL_EXT_sRGB" 
 "GL_KHR_parallel_shader_compile" 
 "GL_CHROMIUM_bind_uniform_location" 
 "GL_EXT_instanced_arrays" 
 "GL_NV_framebuffer_blit" 
 "GL_OES_surfaceless_context" 
 "GL_OES_texture_half_float_linear" 
 "GL_CHROMIUM_lose_context" 
 "GL_ANGLE_translated_shader_source" 
 "GL_ANGLE_texture_compression_dxt5" 
 "GL_EXT_draw_buffers" 
 "GL_ANGLE_texture_compression_dxt3" 
 "GL_EXT_texture_type_2_10_10_10_REV" 
 "" 
 "GL_OES_vertex_array_object" 
 "GL_EXT_unpack_subimage" 
 "GL_NV_pack_subimage" 
 "GL_EXT_draw_buffers_indexed" 
 "GL_EXT_float_blend" 
 "GL_EXT_texture_compression_rgtc" 
 "GL_NV_fence" 
 "GL_ANGLE_get_serialized_context_string" 
 "GL_OES_compressed_EAC_RG11_signed_texture" 
 "GL_OVR_multiview2" 
 "GL_EXT_texture_compression_bptc" 
 "GL_ANGLE_provoking_vertex" 
 "GL_CHROMIUM_bind_generates_resource" 
 "GL_AMD_performance_monitor" 
 "GL_OES_mapbuffer" 
 "GL_ANGLE_texture_multisample" 
 "GL_EXT_blend_minmax" 
 "GL_ANGLE_pack_reverse_row_order" 
 "GL_ANGLE_multi_draw" 
 "GL_WEBGL_video_texture" 
 "GL_ANGLE_program_cache_control" 
 "GL_OES_packed_depth_stencil" 
 "GL_OES_rgb8_rgba8" 
 "GL_OVR_multiview" 
 "GL_ANGLE_memory_size" 
 "GL_ANGLE_framebuffer_multisample" 
 "GL_EXT_color_buffer_float" 
 "GL_ANGLE_robust_client_memory" 
 "GL_EXT_multi_draw_indirect" 
 "GL_KHR_debug" 
 "GL_OES_texture_half_float" 
 "GL_EXT_disjoint_timer_query" 
 "GL_OES_fbo_render_mipmap" 
 "GL_OES_standard_derivatives" 
 "GL_OES_depth32" 
 "GL_EXT_texture_rg" 
 "GL_EXT_frag_depth" 
 "GL_ANGLE_instanced_arrays" 
 "GL_OES_EGL_image" 
 "GL_OES_EGL_image_external" 
 "GL_OES_compressed_EAC_R11_unsigned_texture" 
 "GL_EXT_discard_framebuffer" 
 "GL_OES_texture_float" 

QPA OpenGL Detection Info 
  supportsDesktopGL: true 
  supportsAngleD3D11: true 
  isQtPreferAngle: true 

useBufferInvalidation (config option): false


Hardware Information

  GPU Acceleration: auto
  Memory: 6107 Mb
  Number of Cores: 8
  Swap Location: C:/Users/PC/AppData/Local/Temp
  Built for: sse2
  Base instruction set: sse2
  Supported instruction sets: sse4.2 sse4.1 ssse3 sse3 sse2 

Current Settings

  Current Swap Location: C:/Users/PC/AppData/Local/Temp
  Current Swap Location writable: true
  Undo Enabled: true
  Undo Stack Limit: 200
  Use OpenGL: true
  Use OpenGL Texture Buffer: true
  Disable Vector Optimizations: false
  Disable AVX Optimizations: false
  Canvas State: OPENGL_SUCCESS
  Autosave Interval: 420
  Use Backup Files: true
  Number of Backups Kept: 1
  Backup File Suffix: ~
  Backup Location: Same Folder as the File
  Backup Location writable: false
  Resource Location: C:/Users/PC/AppData/Roaming/krita
  Use Win8 Pointer Input: false
  Use RightMiddleTabletButton Workaround: false
  Levels of Detail Enabled: false
  Use Zip64: false


Loaded Python Plugins
colorspace
comics_project_management_tools
documenttools
exportlayers
filtermanager
lastdocumentsdocker
plugin_importer
quick_settings_docker
scripter
tenbrushes
tenscripts


Display Information
Number of screens: 1
Screen: 0
Name: \\.\DISPLAY1
Depth: 32
Scale: 1
Physical DPI49.6621
Logical DPI96
Physical Size: 697, 392
Position: 0, 0
Resolution in pixels: 1360x768
Manufacturer: 
Model: 
Refresh Rate: 60


-

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

[kwin] [Bug 468895] Desktop freezes when Night Color feature kicks in running Wayland with NVIDIA proprietary drivers.

2023-04-28 Thread Damian C

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

--- Comment #2 from Damian C  ---
Created attachment 158525
  --> https://bugs.kde.org/attachment.cgi?id=158525&action=edit
drm_info1

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

[plasmashell] [Bug 469175] New: Panel with taskbar freezes visually but remains operational

2023-04-30 Thread Damian C

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

Bug ID: 469175
   Summary: Panel with taskbar freezes visually but remains
operational
Classification: Plasma
   Product: plasmashell
   Version: 5.27.4
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Panel
  Assignee: plasma-b...@kde.org
  Reporter: dcalv...@gmail.com
CC: niccolo.venera...@gmail.com
  Target Milestone: 1.0

SUMMARY
Default panel with taskbar and clock freezes visually at some point during
operation.
The panel can still be interacted with but it won't update any information, the
time on the digital clock remains as it was when it stopped working, and
taskbar icons that would update some information (such as the new email counter
within the kmail icon) will not update.


STEPS TO REPRODUCE
1.  Boot and login normally.
2. Use the system normally and at some point some panel will stop responding,
normally the main display one, but not exclusively.

OBSERVED RESULT
Panel stops visually updating, and becomes "frozen", but interaction is still
possible, so I'd call it "functional".

EXPECTED RESULT
Panel doesn't freeze visually at all.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.105.0
Qt Version: 5.15.9
Kernel Version: 6.2.13-zen-1-zen (64-bit)
Graphics Platform: Wayland
Processors: 12 × Intel® Core™ i7-8700K CPU @ 3.70GHz
Memory: 15.6 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2

ADDITIONAL INFORMATION
It can be brought back to a working state by right clicking the panel, entering
edit mode and changing some visual aspect of it, such as the height.

It does not happen on all panels simultaneously, it seems to affect a single
display, though not necessarily the same one every time.

It may have happened around the time I opened a game running with Proton, but
unsure at this point.

Even more strange, during the "frozen" period, if one clicks on the pinned
taskbar icon for "System Settings" it opens some windows that existed at some
point on a different activity. 
Even stranger is the fact that this activity no longer exists as I deleted it
from the activities menu, but during this issue, clicking on this icon brings
back the apps that I had open back then, which were a browser and a konsole
window.
This strange behavior ceases when the workaround of changing the panels height
is applied.

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

[plasmashell] [Bug 469175] Panel with taskbar freezes visually but remains operational

2023-04-30 Thread Damian C

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

Damian C  changed:

   What|Removed |Added

 CC||dcalv...@gmail.com

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

[Skanpage] [Bug 469270] New: Skanpage crashes when trying to do OCR if tesseract is not installed

2023-05-02 Thread Silviu C.

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

Bug ID: 469270
Summary: Skanpage crashes when trying to do OCR if tesseract is
not installed
Classification: Applications
Product: Skanpage
Version: 23.04.0
Platform: openSUSE
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: a.stipp...@gmx.net
Reporter: silvi...@gmail.com
Target Milestone: ---

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
Skanpage crashes if OCR is selected when saving the file but tesseract-ocr is
not actually installed.

STEPS TO REPRODUCE
1. start Skanpage
2. scan something with text
3. when saving the PDF either leave the option to add OCR checked or check it

OBSERVED RESULT

Skanpage crashes.

EXPECTED RESULT

Skanpage test whether tesseract is actually usable. If it's not, grey out the
OCR option and inform user they don't have it installed on the system

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20230501
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.105.0
Qt Version: 5.15.9
Kernel Version: 6.2.12-1-default (64-bit)
Graphics Platform: Wayland
Processors: 6 × Intel® Core™ i5-9600K CPU @ 3.70GHz
Memory: 31,1 GiB of RAM
Graphics Processor: AMD Radeon RX 6600 XT
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: Z390 GAMING X

ADDITIONAL INFORMATION

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

[Skanpage] [Bug 469270] Skanpage crashes when trying to do OCR if tesseract is not installed

2023-05-02 Thread Silviu C.

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

--- Comment #2 from Silviu C.  ---
(In reply to Nate Graham from comment #1)
> Tesseract is required for OCR; if it's not installed, it won't work. But if
> the OCR controls are appearing anyway despite Tesseract not being installed,
> that sounds like a bug in the app, as it shouldn't be happening. I just
> tested this by removing the `tesseract-devel package` and rebuilding the
> app, and I correctly don't see the OCR controls.
> 
> Maybe the reverse is not working, and it fails to hide them at runtime if
> compiled with Tesseract support included but the package isn't actually
> installed on the user's machine. Unfortunately I can't easily test this as
> my distro (Fedora KDE) makes Tesseract a mandatory package and it can't be
> removed at runtime.

I believe this is what is happening. Skanpage is compiled with tesseract
support but tesseract is not installed.

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

[kwin] [Bug 468895] Desktop freezes when Night Color feature kicks in running Wayland with NVIDIA proprietary drivers.

2023-05-03 Thread Damian C

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

--- Comment #4 from Damian C  ---
Created attachment 158675
  --> https://bugs.kde.org/attachment.cgi?id=158675&action=edit
journalctl

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

[kwin] [Bug 468895] Desktop freezes when Night Color feature kicks in running Wayland with NVIDIA proprietary drivers.

2023-05-03 Thread Damian C

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

--- Comment #5 from Damian C  ---
(In reply to Zamundaaa from comment #3)
> There's still no GAMMA_LUT property, so I'm not sure how night color would
> be related. Can you attach your full KWin log? So
> > journalctl --user-unit plasma-kwin_wayland --boot 0
> after causing the issue again

Attached!
I don't expect Night Color to work since the property is not there, but it
seems to cause the issue when it attempts to kick in.
And the only way to stop it from happening so far is to disable Night Color.

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

[plasmashell] [Bug 469434] New: Romanian variant Sun Type 6/7 does not show correctly

2023-05-06 Thread Silviu C.

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

Bug ID: 469434
   Summary: Romanian variant Sun Type 6/7 does not show correctly
Classification: Plasma
   Product: plasmashell
   Version: 5.27.4
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Keyboard Layout
  Assignee: plasma-b...@kde.org
  Reporter: silvi...@gmail.com
CC: butir...@gmail.com
  Target Milestone: 1.0

Created attachment 158745
  --> https://bugs.kde.org/attachment.cgi?id=158745&action=edit
Screenshot showing the issue

SUMMARY



STEPS TO REPRODUCE
1.  Go to System Settings - >  Input Devices -> Kayboard -> Layouts
2.  Add Romanian variant Sun Type 6/7 - which is basically the same as what
Microsoft calls Romanian Programmers
3. Click "Apply"

OBSERVED RESULT

 The Keyboard layout switcher calls is English US (see attached screenshot)

EXPECTED RESULT

Show entry as  "Romanian ( Sun Type 6/7)"

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20230505
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.105.0
Qt Version: 5.15.9
Kernel Version: 6.3.1-1-default (64-bit)
Graphics Platform: Wayland
Processors: 6 × Intel® Core™ i5-9600K CPU @ 3.70GHz
Memory: 31,1 GiB of RAM
Graphics Processor: AMD Radeon RX 6600 XT
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: Z390 GAMING X

ADDITIONAL INFORMATION

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

[plasmashell] [Bug 469434] Romanian variant Sun Type 6/7 does not show correctly

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

--- Comment #2 from Silviu C.  ---
(In reply to Andrey from comment #1)
> Is "variant Sun Type 6/7" essential here?

Honestly, I would be happy if it said just  "Romanian". I've no clue why it
thinks it's "English (US)". I tried with other languages with variants but it
displayed those fine.

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

[plasmashell] [Bug 469434] Romanian variant Sun Type 6/7 does not show correctly

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

--- Comment #4 from Silviu C.  ---
(In reply to Andrey from comment #3)
> I mean, if you skip variant Sun Type 6/7, does it show Romanian right?

I added the "Romanian (Windows)" layout and it shows fine.

Adding screenshot...

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

[plasmashell] [Bug 469434] Romanian variant Sun Type 6/7 does not show correctly

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

--- Comment #5 from Silviu C.  ---
Created attachment 158747
  --> https://bugs.kde.org/attachment.cgi?id=158747&action=edit
Screenshot with Romanian (Windows) layout added

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

[plasmashell] [Bug 469434] Romanian variant Sun Type 6/7 does not show correctly

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

--- Comment #7 from Silviu C.  ---
(In reply to Andrey from comment #6)
> Thanks, what is the actual layout? Is it Romanian or English still?

If I select the Romanian layout that is shown as "English" the actual keyboard
layout changes correctly and I can use the <> key to type characters
like âășțî etc.

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

[kdeconnect] [Bug 417787] sshfs key exchange methods deprecated

2023-05-08 Thread Philip C

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

Philip C  changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution|--- |FIXED
 CC||cliabh...@gmail.com

--- Comment #8 from Philip C  ---
As per discussion in the Telegram group and on the linked merge request
https://invent.kde.org/network/kdeconnect-kde/-/merge_requests/239, this was
fixed sometime in 2020. Please make a new bug if you see this appear again.

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

[systemsettings] [Bug 469730] New: Night color shifting does not start at the correct time or end at the correct time

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

Bug ID: 469730
   Summary: Night color shifting does not start at the correct
time or end at the correct time
Classification: Applications
   Product: systemsettings
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm_nightcolor
  Assignee: plasma-b...@kde.org
  Reporter: silvi...@gmail.com
CC: kwin-bugs-n...@kde.org
  Target Milestone: ---

Created attachment 158929
  --> https://bugs.kde.org/attachment.cgi?id=158929&action=edit
Screenshot illustrating the problem

SUMMARY

Night color shifting does not start at the correct time or end at the correct
time .


STEPS TO REPRODUCE
1.  Go to System settings ->  Display and monitor - > Night colour
2.  At the option "Switching times:" select "Sunset and sunrise at current
location"
3.  Check that the geolocation is correct and that the proposed times for
changing the colour temperature are correct (or just suited to what you'd like
to happen).
4.  Set the desired colour temperature.
5. Click on the "Apply button"

OBSERVED RESULT

The colour does not begin changing at the correct time despite what the taskbar
applet shows.

The next morning you may also find that despite it being way past the hour when
night colour should have shifted back to daylight colour, your desktop will
still have a red tint and the applet will show that night colour is still
active

EXPECTED RESULT

Color shifting should begin and apply correctly at the advertised times

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20230512
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.105.0
Qt Version: 5.15.9
Kernel Version: 6.3.1-2-default (64-bit)
Graphics Platform: Wayland
Processors: 6 × Intel® Core™ i5-9600K CPU @ 3.70GHz
Memory: 31,1 GiB of RAM
Graphics Processor: AMD Radeon RX 6600 XT
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: Z390 GAMING X

ADDITIONAL INFORMATION

Attached screenshot that shows the functionality problem minus the red tint.

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

[systemsettings] [Bug 469730] Night color shifting does not start at the correct time or end at the correct time

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

Silviu C.  changed:

   What|Removed |Added

   Platform|Other   |openSUSE
Version|unspecified |5.27.5

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

[Powerdevil] [Bug 469732] New: Mouse battery percentage is not shown correctly - Logitech G603

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

Bug ID: 469732
   Summary: Mouse battery percentage is not shown correctly -
Logitech G603
Classification: Plasma
   Product: Powerdevil
   Version: 5.27.5
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: silvi...@gmail.com
CC: m...@ratijas.tk, natalie_clar...@yahoo.de
  Target Milestone: ---

Created attachment 158931
  --> https://bugs.kde.org/attachment.cgi?id=158931&action=edit
Screenshot illustrating the problem 1

SUMMARY

Energy -Info Centre and taskbar energy / battery power applet do not show the
battery percentage correctly


STEPS TO REPRODUCE
1.  Click on the "battery" icon on the taskbar 

OBSERVED RESULT

The battery percentage of the mouse is shown incorrectly as 0%

EXPECTED RESULT

It should show the actual reported percentage.

SOFTWARE/OS VERSIONS

Operating System: openSUSE Tumbleweed 20230512
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.105.0
Qt Version: 5.15.9
Kernel Version: 6.3.1-2-default (64-bit)
Graphics Platform: Wayland
Processors: 6 × Intel® Core™ i5-9600K CPU @ 3.70GHz
Memory: 31,1 GiB of RAM
Graphics Processor: AMD Radeon RX 6600 XT
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: Z390 GAMING X

ADDITIONAL INFORMATION

In Gnome's power settings the percentage is shown correctly.

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

[Powerdevil] [Bug 469732] Mouse battery percentage is not shown correctly - Logitech G603

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

--- Comment #1 from Silviu C.  ---
Created attachment 158932
  --> https://bugs.kde.org/attachment.cgi?id=158932&action=edit
Screenshot illustrating the problem 2

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

[Powerdevil] [Bug 469732] Mouse battery percentage is not shown correctly - Logitech G603