from:"G"

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

--- Comment #1 from Raphaël G.  ---
Installed version:
amarok-2.9.75-2.mga9
amarok-debuginfo-2.9.75-2.mga9
amarok-debugsource-2.9.75-2.mga9
amarok-utils-2.9.75-2.mga9
lib64amarokcore1-2.9.75-2.mga9
lib64amaroklib1-2.9.75-2.mga9
lib64amarokpud1-2.9.75-2.mga9
lib64amarokshared1-2.9.75-2.mga9
lib64amarok-sqlcollection1-2.9.75-2.mga9
lib64amarok-transcoding1-2.9.75-2.mga9

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

[amarok] [Bug 481384] New: Amarok crash while searching

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

Bug ID: 481384
   Summary: Amarok crash while searching
Classification: Applications
   Product: amarok
   Version: unspecified
  Platform: Mageia RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: amarok-bugs-d...@kde.org
  Reporter: k...@rapsys.eu
  Target Milestone: kf5

SUMMARY
I search for a string like 'a b c d e f g h i j k l ...' or others but with
this one it fails each time.

After adding my collection, with multiple duplicated file and a directory
failing import (modification date 31 dec 1969).

Amarok crash

STEPS TO REPRODUCE
1.  Import lot of directories with a directory modified the 31 dec 1969 and
multiple duplicates
2.  Search for some song title or string earlier
3.  Crash

OBSERVED RESULT
Crash

EXPECTED RESULT
Should not crash

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Calling appendChild() on a null node does nothing.

Thread 1 "amarok" received signal SIGSEGV, Segmentation fault.
0x7783d0d0 in CollectionTreeItem::row() const () from
/lib64/libamaroklib.so.1
(gdb) bt
#0  0x7783d0d0 in CollectionTreeItem::row() const () at
/lib64/libamaroklib.so.1
#1  0x77842380 in
CollectionTreeItemModelBase::itemIndex(CollectionTreeItem*) const () at
/lib64/libamaroklib.so.1
#2  0x77842400 in CollectionTreeItemModelBase::parent(QModelIndex
const&) const () at /lib64/libamaroklib.so.1
#3  0x76274799 in QModelIndex::parent() const (this=0x11e9790) at
../../include/QtCore/../../src/corelib/itemmodels/qabstractitemmodel.h:443
#4  QSortFilterProxyModelPrivate::_q_sourceDataChanged(QModelIndex const&,
QModelIndex const&, QVector const&)
 (this=0xdcf670, source_top_left=,
source_bottom_right=, roles=...) at
itemmodels/qsortfilterproxymodel.cpp:1433
#5  0x762d3f84 in doActivate(QObject*, int, void**)
(sender=0xaeda30, signal_index=3, argv=0x7fffd2f0) at
kernel/qobject.cpp:3931
#6  0x762cd55f in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**)
(sender=, m=m@entry=0x76570680
,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fffd2f0)
at kernel/qobject.cpp:3979
#7  0x7623d3ec in QAbstractItemModel::dataChanged(QModelIndex const&,
QModelIndex const&, QVector const&) (this=, _t1=, _t2=, _t3=)
at .moc/moc_qabstractitemmodel.cpp:557
#8  0x7784625a in
CollectionTreeItemModelBase::tracksLoaded(AmarokSharedPointer
const&, QModelIndex const&, QList > const&) ()
at /lib64/libamaroklib.so.1
#9  0x762c8d40 in QObject::event(QEvent*) (this=0xaeda30,
e=0x7fff9c002210) at kernel/qobject.cpp:1347
#10 0x76f6240e in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0xaeda30, e=0x7fff9c002210) at
kernel/qapplication.cpp:3637
#11 0x7629e888 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0xaeda30, event=0x7fff9c002210) at kernel/qcoreapplication.cpp:1064
#12 0x762a15b9 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) (receiver=0x0, event_type=0, data=0x446e30) at
kernel/qcoreapplication.cpp:1821
#13 0x762f3b03 in postEventSourceDispatch(GSource*, GSourceFunc,
gpointer) (s=0x53f9f0) at kernel/qeventdispatcher_glib.cpp:277
#14 0x71a4c689 in g_main_dispatch (context=0x7fffe4000ee0) at
../glib/gmain.c:3460
#15 g_main_context_dispatch (context=context@entry=0x7fffe4000ee0) at
../glib/gmain.c:4200
#16 0x71a4ca18 in g_main_context_iterate
(context=context@entry=0x7fffe4000ee0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4276
#17 0x71a4ca9c in g_main_context_iteration (context=0x7fffe4000ee0,
may_block=1) at ../glib/gmain.c:4343
#18 0x762f31f6 in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x54b220, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#19 0x7629d46b in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fffd720, flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
#20 0x762a4fe6 in QCoreApplication::exec() () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#21 0x7673034c in QGuiApplication::exec() () at
kernel/qguiapplication.cpp:1870
#22 0x76f62385 in QApplication::exec() () at
kernel/qapplication.cpp:2829
#23 0x00407fd7 in main(int, char**) (argc=,
argv=) at
/usr/src/debug/amarok-2.9.75-2.mga9.x86_64/src/main.cpp:389

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

[amarok] [Bug 426807] Out of range changedate prevents importing music folder

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

--- Comment #5 from Raphaël G.  ---
Same bug as https://bugs.kde.org/show_bug.cgi?id=405241 too, which was
invalidly closed as invalid.

Amarok should support out of timestamp range creation/modification dates.

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

[amarok] [Bug 426807] Out of range changedate prevents importing music folder

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

Raphaël G.  changed:

   What|Removed |Added

 CC||k...@rapsys.eu
 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

--- Comment #4 from Raphaël G.  ---
SUMMARY
I set amarok to use my mariadb server at localhost.

I get a sql error in the /var/lib/mysql/sql_error.log when amarok update the
collection:
2024-02-15 22:14:22 amarok[amarok] @ localhost [] ERROR 1264: Out of range
value for column 'changedate' at row 1 : INSERT INTO
directories(deviceid,changedate,dir) VALUES
(1,4294963696,'home//Musique/')

STEPS TO REPRODUCE
1.  Create directory with such timestamps
2.  Update collection
3.  See error in sql error log

FIX SUGGESTION
Change changedate from int(11) to datetime ?

OBSERVED RESULT
ERROR 1264: Out of range value for column 'changedate' at row 1 : INSERT INTO
directories(deviceid,changedate,dir) VALUES
(1,4294963696,'home//Musique/')

EXPECTED RESULT
No error

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
LC_ALL=C l -ldh '/home//Musique/':
drwxr-xr-x 1   3.8K Dec 31  1969

LC_ALL=C stat '/home//Musique/'
  File: /home//Musique/
  Size: 3872Blocks: 0  IO Block: 4096   directory
Device: 0,39Inode: 270513  Links: 1
Access: (0755/drwxr-xr-x)  Uid: ( /  )   Gid: ( /  )
Access: 2024-02-15 21:54:41.937300905 +
Modify: 1969-12-31 23:00:00.0 +
Change: 2024-01-12 18:40:54.232067829 +
 Birth: 2024-01-12 16:40:52.050847188 +

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

[plasmashell] [Bug 481197] When the panel is hidden, a thin blue line is always visible

2024-02-13 Thread Tobias G.

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

--- Comment #5 from Tobias G.  ---
(In reply to Marco Martin from comment #4)
> 
> *** This bug has been marked as a duplicate of bug 480434 ***

Is this really a duplicate?
The other bug has a different description 

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

[plasmashell] [Bug 481197] When the panel is hidden, a thin blue line is always visible

2024-02-12 Thread Tobias G.

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

--- Comment #3 from Tobias G.  ---
(In reply to fanzhuyifan from comment #1)
> There is an effect that only activates when your cursor is near the edge. It
> is called screen edge in window management - desktop effects.
> 
> However based on the screenshot the issue you are encountering might be
> different. Could you verify if you still see this after turning off this
> effect?
> 
> Thanks!

I can also confirm that the issue still exist after turning off aforementioned
feature.
Good that I'm not the only one, my screen is scaled by 150%

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

[plasmashell] [Bug 481197] New: When the panel is hidden, a thin blue line is always visible

2024-02-10 Thread Tobias G.

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

Bug ID: 481197
   Summary: When the panel is hidden, a thin blue line is always
visible
Classification: Plasma
   Product: plasmashell
   Version: master
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Panel
  Assignee: plasma-b...@kde.org
  Reporter: tobi.goerg...@gmail.com
CC: niccolo.venera...@gmail.com
  Target Milestone: 1.0

Created attachment 165737
  --> https://bugs.kde.org/attachment.cgi?id=165737=edit
Screenshot showing blue line

SUMMARY
I have a floating panel and set it to dodge windows, which works fine. However,
when the panel is hidden, a thin blue line is visible at the bottom of the
screen where the panel is located (see screenshot)
If this behavior is wanted, is there an option to turn this off?


STEPS TO REPRODUCE
1. Set panel to floating
2. Set panel to dodge windows
3. Open fullscreen content

OBSERVED RESULT
There's a blue line at the screen edge where the panel is

EXPECTED RESULT
There is no indicator at to where the panel is

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20240206
KDE Plasma Version: 6.0.80
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.1
Kernel Version: 6.7.2-1-default (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 7840U w/ Radeon 780M Graphics
Memory: 30.5 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: Framework
Product Name: Laptop 13 (AMD Ryzen 7040Series)
System Version: A7

ADDITIONAL INFORMATION
See Image

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

[kwin] [Bug 481095] New: After logout, I sometimes have visual glitches

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

Bug ID: 481095
   Summary: After logout, I sometimes have visual glitches
Classification: Plasma
   Product: kwin
   Version: git master
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: compositing
  Assignee: kwin-bugs-n...@kde.org
  Reporter: tobi.goerg...@gmail.com
  Target Milestone: ---

SUMMARY
See video. After logout, I sometimes get weird lines and artifacts when
elements get redrawn

STEPS TO REPRODUCE
1. logout
2. observe
3. 

OBSERVED RESULT
visual artifacts and glitches

EXPECTED RESULT
no visual artifacts and glitches

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20240206
KDE Plasma Version: 6.0.80
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.1
Kernel Version: 6.7.2-1-default (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 7840U w/ Radeon 780M Graphics
Memory: 30.5 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: Framework
Product Name: Laptop 13 (AMD Ryzen 7040Series)
System Version: A7

ADDITIONAL INFORMATION
I made a video: https://www.youtube.com/watch?v=XMRkRcZUhKw

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

[systemsettings] [Bug 481094] New: No kwin scripts are shown to install

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

Bug ID: 481094
   Summary: No kwin scripts are shown to install
Classification: Applications
   Product: systemsettings
   Version: master
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm_kwinscripts
  Assignee: kwin-bugs-n...@kde.org
  Reporter: tobi.goerg...@gmail.com
CC: alexander.loh...@gmx.de, plasma-b...@kde.org
  Target Milestone: ---

SUMMARY
I can't install any kwin scripts as the dialog doesn't find any


STEPS TO REPRODUCE
1. go to kwin script's settings page
2. search for new scripts online using the inbuilt dialog
3. observe

OBSERVED RESULT
No scripts can be found

EXPECTED RESULT
The dalog shows the available scripts

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20240206
KDE Plasma Version: 6.0.80
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.1
Kernel Version: 6.7.2-1-default (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 7840U w/ Radeon 780M Graphics
Memory: 30.5 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: Framework
Product Name: Laptop 13 (AMD Ryzen 7040Series)
System Version: A7

ADDITIONAL INFORMATION
I made a video: https://www.youtube.com/watch?v=pR98oMgRbGw

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

[kwin] [Bug 481093] New: When switching the theme, it happens piece by piece and not smoothly

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

Bug ID: 481093
   Summary: When switching the theme, it happens piece by piece
and not smoothly
Classification: Plasma
   Product: kwin
   Version: git master
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: compositing
  Assignee: kwin-bugs-n...@kde.org
  Reporter: tobi.goerg...@gmail.com
  Target Milestone: ---

SUMMARY
When switching the theme of Plasma, it's done in a choppy way and there's no
smooth transition


STEPS TO REPRODUCE
1. start settings
2. switch to other theme
3. observe

OBSERVED RESULT
The theme is switched in "multiple steps"

EXPECTED RESULT
The theme should be switched in one go and be smoothly animated

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20240206
KDE Plasma Version: 6.0.80
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.1
Kernel Version: 6.7.2-1-default (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 7840U w/ Radeon 780M Graphics
Memory: 30.5 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: Framework
Product Name: Laptop 13 (AMD Ryzen 7040Series)
System Version: A7

ADDITIONAL INFORMATION
I made a video: https://www.youtube.com/watch?v=vHSgbiYwEqE

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

[Discover] [Bug 481092] New: Discover doesn't list/show packagekit applications

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

Bug ID: 481092
   Summary: Discover doesn't list/show packagekit applications
Classification: Applications
   Product: Discover
   Version: master
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: PackageKit
  Assignee: plasma-b...@kde.org
  Reporter: tobi.goerg...@gmail.com
CC: aleix...@kde.org
  Target Milestone: ---

SUMMARY
When searching for an application, only flatpaks are shown, even though the
packagekit backend is also installed and updates work fine


STEPS TO REPRODUCE
1. open discover
2. search for application
3. only find flatpak

OBSERVED RESULT
only the flatpak version of applications is found

EXPECTED RESULT
packagekit applications are shown as well

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20240206
KDE Plasma Version: 6.0.80
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.1
Kernel Version: 6.7.2-1-default (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 7840U w/ Radeon 780M Graphics
Memory: 30.5 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: Framework
Product Name: Laptop 13 (AMD Ryzen 7040Series)
System Version: A7

ADDITIONAL INFORMATION
I made a video: https://www.youtube.com/watch?v=H6Ma2bD-jOE

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

[Discover] [Bug 481091] New: Discover doesn't show application on the start page even though packagekit is installed and updates/remove software works

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

Bug ID: 481091
   Summary: Discover doesn't show application on the start page
even though packagekit is installed and updates/remove
software works
Classification: Applications
   Product: Discover
   Version: master
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: plasma-b...@kde.org
  Reporter: tobi.goerg...@gmail.com
CC: aleix...@kde.org
  Target Milestone: ---

SUMMARY
The start page of discover doesn't show any applications. 


STEPS TO REPRODUCE
1. start discover
2. wait
3. see error message

OBSERVED RESULT
I get an hint to check the internet connection

EXPECTED RESULT
Discover shows applications

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20240206
KDE Plasma Version: 6.0.80
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.1
Kernel Version: 6.7.2-1-default (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 7840U w/ Radeon 780M Graphics
Memory: 30.5 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: Framework
Product Name: Laptop 13 (AMD Ryzen 7040Series)
System Version: A7

ADDITIONAL INFORMATION
I made a video: https://www.youtube.com/watch?v=dLGUt6wYkJs

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

[partitionmanager] [Bug 481087] Partiton manager asks two times for password

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

Tobias G.  changed:

   What|Removed |Added

   Platform|Other   |openSUSE

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

[partitionmanager] [Bug 481087] New: Partiton manager asks two times for password

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

Bug ID: 481087
   Summary: Partiton manager asks two times for password
Classification: Applications
   Product: partitionmanager
   Version: Git
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: andr...@stikonas.eu
  Reporter: tobi.goerg...@gmail.com
  Target Milestone: ---

SUMMARY
When opened, the partition manager asks two times for the password, which is
also acting weird with the fingerprint sensor. When dismissing the second one,
one gets asked again


STEPS TO REPRODUCE
1. open partiton manager
2. enter first password
3. enter second password

OBSERVED RESULT
the user is asked two times for a password

EXPECTED RESULT
the user is only asked once (OR even better: only asked when a privileged
action is to be done) 

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20240206
KDE Plasma Version: 6.0.80
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.1
Kernel Version: 6.7.2-1-default (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 7840U w/ Radeon 780M Graphics
Memory: 30.5 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: Framework
Product Name: Laptop 13 (AMD Ryzen 7040Series)
System Version: A7

ADDITIONAL INFORMATION
I made a video: https://www.youtube.com/watch?v=uYOuUi1NAyQ

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

[kscreenlocker] [Bug 481086] New: Fingerprint unlock of screen locker only works after initial failure

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

Bug ID: 481086
   Summary: Fingerprint unlock of screen locker only works after
initial failure
Classification: Plasma
   Product: kscreenlocker
   Version: git-master
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: tobi.goerg...@gmail.com
  Target Milestone: ---

SUMMARY
See video. Often, the fingerprint wouldn't be registered until I enter the
wrong password once, only then it accepts the fingerprint


STEPS TO REPRODUCE
1.  set up fingerprint
2.  lock screen
3. try to unlock using fingerprint reader

OBSERVED RESULT
Screen doesn't unlock

EXPECTED RESULT
Screen should unlock

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20240206
KDE Plasma Version: 6.0.80
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.1
Kernel Version: 6.7.2-1-default (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 7840U w/ Radeon 780M Graphics
Memory: 30.5 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: Framework
Product Name: Laptop 13 (AMD Ryzen 7040Series)
System Version: A7

ADDITIONAL INFORMATION
I made a video: https://www.youtube.com/watch?v=KmxRadbhnzI

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

[kdeplasma-addons] [Bug 481085] New: Battery widget in panel doessn't save "show percent" setting

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

Bug ID: 481085
   Summary: Battery widget in panel doessn't save "show percent"
setting
Classification: Plasma
   Product: kdeplasma-addons
   Version: git-master
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: plasma-b...@kde.org
  Reporter: tobi.goerg...@gmail.com
  Target Milestone: ---

SUMMARY
The battery widget in the panel has a setting to show the percent in the panel
on the symbol. However, after a reboot the percentage is not shown anymore.


STEPS TO REPRODUCE
1.  activate "show battery percent" in battery/power widget
2. reboot
3. observe

OBSERVED RESULT
battery percent is not shown anymore

EXPECTED RESULT
battery percent should still be shown

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20240206
KDE Plasma Version: 6.0.80
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.1
Kernel Version: 6.7.2-1-default (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 7840U w/ Radeon 780M Graphics
Memory: 30.5 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: Framework
Product Name: Laptop 13 (AMD Ryzen 7040Series)
System Version: A7

ADDITIONAL INFORMATION

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

[kde] [Bug 478684] New: Kalendar Crash after install

2023-12-18 Thread Kevin G

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

Bug ID: 478684
   Summary: Kalendar Crash after install
Classification: I don't know
   Product: kde
   Version: unspecified
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: krg...@kevingarand.com
  Target Milestone: ---

Application: kalendar (22.12.3)

Qt Version: 5.15.8
Frameworks Version: 5.103.0
Operating System: Linux 6.1.0-15-amd64 x86_64
Windowing System: X11
Distribution: Debian GNU/Linux 12 (bookworm)
DrKonqi: 5.27.5 [KCrashBackend]

-- Information about the crash:
Constant Crash when trying to open.  Tried 3 times, app starts, but then
crashes.

The crash can be reproduced every time.

-- Backtrace:
Application: Kalendar (kalendar), signal: Segmentation fault

[KCrash Handler]
#4  0x7faab3abb760 in KCalendarCore::Calendar::isLoading() const () from
/lib/x86_64-linux-gnu/libKF5CalendarCore.so.5abi2
#5  0x55f1ac30827c in ?? ()
#6  0x7faab1c57f4f in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7faab1c5bd6a in QTimer::timeout(QTimer::QPrivateSignal) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7faab1c4c50d in QObject::event(QEvent*) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7faab28a2fae in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#10 0x7faab1c206f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7faab1c77c31 in QTimerInfoList::activateTimers() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x7faab1c784fc in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x7faaaf4d97a9 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#14 0x7faaaf4d9a38 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#15 0x7faaaf4d9acc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#16 0x7faab1c78836 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x7faab1c1f17b in
QEventLoop::exec(QFlags) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x7faab1c272d6 in QCoreApplication::exec() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#19 0x55f1ac2b6341 in ?? ()
#20 0x7faab157b1ca in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#21 0x7faab157b285 in __libc_start_main () from
/lib/x86_64-linux-gnu/libc.so.6
#22 0x55f1ac2b70c1 in ?? ()
[Inferior 1 (process 4364) detached]

Reported using DrKonqi
This report was filed against 'kde' because the product 'kalendar' could not be
located in Bugzilla. Add it to drkonqi's mappings file!

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

[konsole] [Bug 478354] New: Konsole crashed with huge rsync log output

2023-12-10 Thread Joerg G.

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

Bug ID: 478354
   Summary: Konsole crashed with huge rsync log output
Classification: Applications
   Product: konsole
   Version: 23.08.4
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: kde.b...@wurzelbenutzer.de
  Target Milestone: ---

Application: konsole (23.08.4)

Qt Version: 5.15.11
Frameworks Version: 5.112.0
Operating System: Linux 6.6.5-arch1-1 x86_64
Windowing System: X11
Distribution: Arch Linux
DrKonqi: 5.27.10 [KCrashBackend]

-- Information about the crash:
Running rsync in one tab switching tabs crashed Konsole

The crash can be reproduced sometimes.

-- Backtrace:
Application: Konsole (konsole), signal: Segmentation fault

[KCrash Handler]
#4  0x7ff7207d30ac in Konsole::Screen::copyFromHistory(Konsole::Character*,
int, int) const () at /usr/lib/libkonsoleprivate.so.1
#5  0x7ff7207d3599 in Konsole::Screen::getImage(Konsole::Character*, int,
int, int) const () at /usr/lib/libkonsoleprivate.so.1
#6  0x7ff7207dc72a in Konsole::ScreenWindow::getImage() () at
/usr/lib/libkonsoleprivate.so.1
#7  0x7ff7208375ec in Konsole::TerminalDisplay::updateImage() () at
/usr/lib/libkonsoleprivate.so.1
#8  0x7ff71f2d1097 in  () at /usr/lib/libQt5Core.so.5
#9  0x7ff720065193 in QAbstractSlider::valueChanged(int) () at
/usr/lib/libQt5Widgets.so.5
#10 0x7ff720066ccd in QAbstractSlider::setValue(int) () at
/usr/lib/libQt5Widgets.so.5
#11 0x7ff72006896a in  () at /usr/lib/libQt5Widgets.so.5
#12 0x7ff720111801 in QScrollBar::wheelEvent(QWheelEvent*) () at
/usr/lib/libQt5Widgets.so.5
#13 0x7ff71ffaf331 in QWidget::event(QEvent*) () at
/usr/lib/libQt5Widgets.so.5
#14 0x7ff72083974f in Konsole::TerminalDisplay::wheelEvent(QWheelEvent*) ()
at /usr/lib/libkonsoleprivate.so.1
#15 0x7ff71ffaf331 in QWidget::event(QEvent*) () at
/usr/lib/libQt5Widgets.so.5
#16 0x7ff71ff788ff in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#17 0x7ff71ff7e824 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib/libQt5Widgets.so.5
#18 0x7ff71f29c168 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#19 0x7ff71ffcfbb6 in  () at /usr/lib/libQt5Widgets.so.5
#20 0x7ff71ff788ff in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#21 0x7ff71f29c168 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#22 0x7ff71f745299 in
QGuiApplicationPrivate::processWheelEvent(QWindowSystemInterfacePrivate::WheelEvent*)
() at /usr/lib/libQt5Gui.so.5
#23 0x7ff71f72a6f5 in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
() at /usr/lib/libQt5Gui.so.5
#24 0x7ff718d08570 in  () at /usr/lib/libQt5XcbQpa.so.5
#25 0x7ff71d43af69 in  () at /usr/lib/libglib-2.0.so.0
#26 0x7ff71d499367 in  () at /usr/lib/libglib-2.0.so.0
#27 0x7ff71d439162 in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#28 0x7ff71f2eaf7c in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#29 0x7ff71f29ae74 in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#30 0x7ff71f29c313 in QCoreApplication::exec() () at
/usr/lib/libQt5Core.so.5
#31 0x55bb323dbb15 in  ()
#32 0x7ff71ea45cd0 in  () at /usr/lib/libc.so.6
#33 0x7ff71ea45d8a in __libc_start_main () at /usr/lib/libc.so.6
#34 0x55bb323dc3a5 in  ()
[Inferior 1 (process 2714) detached]

Reported using DrKonqi

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

[krita] [Bug 478341] Errors trying to run "Hello World" in Scripter Debugger

2023-12-10 Thread Martin G.

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

--- Comment #2 from Martin G.  ---
Created attachment 164063
  --> https://bugs.kde.org/attachment.cgi?id=164063=edit
KritaSystemInformation.txt

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

[krita] [Bug 478341] Errors trying to run "Hello World" in Scripter Debugger

2023-12-10 Thread Martin G.

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

--- Comment #1 from Martin G.  ---
Created attachment 164062
  --> https://bugs.kde.org/attachment.cgi?id=164062=edit
KritaUsageLog.txt

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

[krita] [Bug 478341] New: Errors trying to run "Hello World" in Scripter Debugger

2023-12-10 Thread Martin G.

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

Bug ID: 478341
   Summary: Errors trying to run "Hello World" in Scripter
Debugger
Classification: Applications
   Product: krita
   Version: unspecified
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Scripting
  Assignee: krita-bugs-n...@kde.org
  Reporter: gecko...@gmx.de
  Target Milestone: ---

Krita 5.2.2 (can't select this version in the bugtracker), Windows 10 64 Bit

This simple script runs fine when pressing the "Run" button.

print("Hello World")

But pressing the "Debug" button instead results in two error dialogs popping
up.



Dialog 1

Script error - Krita

An exception occurred while running the script.

TypeError: cannot pickle 'ScripterExtension' object

TypeError
Python 3.10.7: C:\Program Files\Krita (x64)\bin\krita.exe
Sun Dec 10 09:52:45 2023

A problem occurred in a Python script.  Here is the sequence of
function calls leading up to the error, in the order they occurred.

 C:\Program Files\Krita
(x64)\share\krita\pykrita\scripter\ui_scripter\actions\debugaction\debugaction.py
in debug(self=)
   33 if self.scripter.uicontroller.invokeAction('save'):
   34 self.scripter.uicontroller.setActiveWidget(i18n('Debugger'))
   35
self.scripter.debugcontroller.start(self.scripter.documentcontroller.activeDocument)
   36 widget =
self.scripter.uicontroller.findTabWidget(i18n('Debugger'))
   37 widget.startDebugger()
self = 
self.scripter = 
self.scripter.debugcontroller = 
self.scripter.debugcontroller.start = >
self.scripter.documentcontroller =

self.scripter.documentcontroller.activeDocument =


 C:\Program Files\Krita (x64)\share\krita\pykrita\scripter\debugcontroller.py
in start(self=,
document=)
   23 self.setCmd(compile(document.data, document.filePath, "exec"))
   24 self._debugger = debugger.Debugger(self.scripter, self._cmd)
   25 self._debugger.debugprocess.start()
   26 loop = asyncio.get_event_loop()
   27 loop.run_until_complete(self._debugger.start())
self = 
self._debugger = 
self._debugger.debugprocess = 
self._debugger.debugprocess.start = >

 C:\Program Files\Krita (x64)\multiprocessing\process.py in start(self=)


 C:\Program Files\Krita (x64)\multiprocessing\context.py in
_Popen(process_obj=)


 C:\Program Files\Krita (x64)\multiprocessing\context.py in
_Popen(process_obj=)


 C:\Program Files\Krita (x64)\multiprocessing\popen_spawn_win32.py in
__init__(self=,
process_obj=)


 C:\Program Files\Krita (x64)\multiprocessing\reduction.py in dump(obj=, file=<_io.BufferedWriter name=3>,
protocol=None)

TypeError: cannot pickle 'ScripterExtension' object
__cause__ = None
__class__ = 
__context__ = None
__delattr__ = 
__dict__ = {}
__dir__ = 
__doc__ = 'Inappropriate argument type.'
__eq__ = 
__format__ = 
__ge__ = 
__getattribute__ = 
__gt__ = 
__hash__ = 
__init__ = 
__init_subclass__ = 
__le__ = 
__lt__ = 
__ne__ = 
__new__ = 
__reduce__ = 
__reduce_ex__ = 
__repr__ = 
__setattr__ = 
__setstate__ = 
__sizeof__ = 
__str__ = 
__subclasshook__ = 
__suppress_context__ = False
__traceback__ = 
args = ("cannot pickle 'ScripterExtension' object",)
with_traceback = 

The above is a description of an error in a Python program.  Here is
the original traceback:

Traceback (most recent call last):
  File "C:\Program Files\Krita
(x64)\share\krita\pykrita\scripter\ui_scripter\actions\debugaction\debugaction.py",
line 35, in debug
   
self.scripter.debugcontroller.start(self.scripter.documentcontroller.activeDocument)
  File "C:\Program Files\Krita
(x64)\share\krita\pykrita\scripter\debugcontroller.py", line 25, in start
self._debugger.debugprocess.start()
  File "multiprocessing\process.py", line 121, in start
  File "multiprocessing\context.py", line 224, in _Popen
  File "multiprocessing\context.py", line 336, in _Popen
  File "multiprocessing\popen_spawn_win32.py", line 93, in __init__
  File "multiprocessing\reduction.py", line 60, in dump
TypeError: cannot pickle 'ScripterExtension' object



Dialog 2

---
Krita
---
krita: Unknown options: c, multiprocessing-fork.

---
OK   
---

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

[plasmashell] [Bug 477300] No "Add to Favorites" option in search results in kickoff

2023-11-20 Thread Andreas G

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

Andreas G  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Andreas G  ---


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

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

[plasmashell] [Bug 476719] "Add to Favorites" menu item missing in context menu of search result delegates

2023-11-20 Thread Andreas G

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

Andreas G  changed:

   What|Removed |Added

 CC||uri...@posteo.de

--- Comment #1 from Andreas G  ---
*** Bug 477300 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 477300] New: No "Add to Favorites" option in search results in kickoff

2023-11-20 Thread Andreas G

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

Bug ID: 477300
   Summary: No "Add to Favorites" option in search results in
kickoff
Classification: Plasma
   Product: plasmashell
   Version: master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Application Launcher (Kickoff)
  Assignee: plasma-b...@kde.org
  Reporter: uri...@posteo.de
CC: mikel5...@gmail.com, noaha...@gmail.com
  Target Milestone: 1.0

Created attachment 163326
  --> https://bugs.kde.org/attachment.cgi?id=163326=edit
context menu in kickoff search vs. browsing

"Add to Favorites" option doesn't appear in the context menu of an application
in search results. 

STEPS TO REPRODUCE

See attached video.

SOFTWARE/OS VERSIONS

Operating System: Fedora Linux 39
KDE Plasma Version: 5.81.0
KDE Frameworks Version: 5.245.0
Qt Version: 6.6.0
Kernel Version: 6.5.11-300.fc39.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-7700HQ CPU @ 2.80GHz
Memory: 15.5 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 630

ADDITIONAL INFORMATION

Plasma 6 built with kdesrc-build

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

[plasmashell] [Bug 477138] Application Launcher slow and laggy when Discover not installed

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

Andreas G  changed:

   What|Removed |Added

 CC||uri...@posteo.de

--- Comment #7 from Andreas G  ---
That was fast,
Thanks a lot

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

[kwin] [Bug 477242] Kwin on host duplicates Displays when guest VM is using Intel GVT-g

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

--- Comment #2 from Andreas G  ---
Created attachment 163298
  --> https://bugs.kde.org/attachment.cgi?id=163298=edit
kwin keeps on adding displays while the VM is running

This video shows that it doesn't just happen during VM boot, but also when
opening a running VM and sometimes just randomly.

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

[kwin] [Bug 477242] Kwin on host duplicates Displays when guest VM is using Intel GVT-g

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

--- Comment #1 from Andreas G  ---
Created attachment 163297
  --> https://bugs.kde.org/attachment.cgi?id=163297=edit
Starting a VM utilizing GVTg on a Plasma 6 Host

Here the uevents are shown and KWin adding a duplicate display on Windows guest
VM boot.

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

[kwin] [Bug 477242] Kwin on host duplicates Displays when guest VM is using Intel GVT-g

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

Andreas G  changed:

   What|Removed |Added

Summary|Kwin duplicates Displays|Kwin on host duplicates
   |when VM is using Intel  |Displays when guest VM is
   |GVT-g   |using Intel GVT-g

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

[kwin] [Bug 477242] New: Kwin duplicates Displays when VM is using Intel GVT-g

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

Bug ID: 477242
   Summary: Kwin duplicates Displays when VM is using Intel GVT-g
Classification: Plasma
   Product: kwin
   Version: master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: platform-drm
  Assignee: kwin-bugs-n...@kde.org
  Reporter: uri...@posteo.de
  Target Milestone: ---

SUMMARY

GVTg can be used on some Intel CPUs to provide vGPUs for virtual machines.
Whenever a virtual machine is using a vGPU, the intel driver i915 triggers an
"add" uevent for "/dev/dri/card0" (the integrated intel gpu).
Every single time such an uevent happens, kwin on KF6 adds another duplicate
display.

On current KF5 (5.27.9), the behaviour is different: It causes kwin to freeze
with the warnings:
Nov 19 14:38:35 fedora.gatas kwin_wayland[21784]: kwin_core: Failed to open
/dev/dri/card0 device (Device already taken)
Nov 19 14:38:35 fedora.gatas kwin_wayland[21784]: kwin_wayland_drm: failed to
open drm device at "/dev/dri/card0"

STEPS TO REPRODUCE
1. buy Intel 5th to 10th gen CPU
2. use Plasma 6 via kdesrc-build
3. setup a virtual machine using GVTg
https://wiki.archlinux.org/title/Intel_GVT-g (what form of output you choose
doesn't matter)
4. start VM (again doesn't matter how, if it's "virsh start DomainName" and you
never look at it, it also happens)

OBSERVED RESULT

Flashing and scale change and new monitors keep getting added in the display
settings causing worse and worse performance.

EXPECTED RESULT

Not having a dozen duplicate displays.

SOFTWARE/OS VERSIONS

Operating System: Fedora Linux 39
KDE Plasma Version: 5.81.0
KDE Frameworks Version: 5.245.0
Qt Version: 6.6.0
Kernel Version: 6.5.11-300.fc39.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-7700HQ CPU @ 2.80GHz
Memory: 15.5 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 630

ADDITIONAL INFORMATION

This is not an issue when using xorg or when using an older kwin_wayland KF5.
But i do not remember the last working version. I just have it in my memory
that i used wayland a few months ago in Fedora 38 and the same VM setup did
work.

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

[kscreenlocker] [Bug 469687] Screen does not shut off when sleep inhibitor lock is created and released

2023-11-18 Thread Eric G

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

--- Comment #2 from Eric G  ---
I'm now unable to reproduce on:
Operating System: Gentoo Linux 2.14
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.11
Kernel Version: 6.1.53-gentoo-r1 (64 bit)
Graphics Platform: Wayland

I recommend closing.  I'm not sure if something was up streamed which would
affect behavior here. So I will leave it to someone with more experience with
this project to tag resolution.  Thank you.

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

[dolphin] [Bug 475357] Regression in Dolphin 23.08.1 - Expandable folders in Details view mode broken

2023-10-14 Thread Shay G

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

Shay G  changed:

   What|Removed |Added

 CC||govers...@gmail.com

--- Comment #2 from Shay G  ---
I have something similar but I don't use LUKS.

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

[Spectacle] [Bug 462860] Rectangle capture modes have wrong GUI sizing and positioning with fractional scaling

2023-09-26 Thread Marco G

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

Marco G  changed:

   What|Removed |Added

 CC||mg.sola...@gmail.com

--- Comment #59 from Marco G  ---
23.08.1-0xneon+22.04+jammy+release+build21

Happens to me on all scales >100%.
Dual Monitor Setup:

```
➤ xrdb -query
*customization: -color
Xcursor.size:   36
Xcursor.theme:  Sweet-cursors
Xft.antialias:  1
Xft.dpi:144
Xft.hinting:1
Xft.hintstyle:  hintslight
Xft.rgba:   none

➤ xdpyinfo | grep dots
resolution:144x144 dots per inch

➤ xrandr | grep -w connected
eDP-1 connected 2880x1800+0+180 (normal left inverted right x axis y axis)
302mm x 188mm
DP-1-1 connected primary 3840x2160+2880+0 (normal left inverted right x axis y
axis) 697mm x 392mm
```

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

[KScreen] [Bug 471475] 3 screen configuration doesn't "write".

2023-06-26 Thread Kevin G

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

Kevin "G"  changed:

   What|Removed |Added

 CC||krg...@kevingarand.com

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

[KScreen] [Bug 471475] New: 3 screen configuration doesn't "write".

2023-06-26 Thread Kevin G

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

Bug ID: 471475
Summary: 3 screen configuration doesn't "write".
Classification: Plasma
Product: KScreen
Version: git-stable-Plasma/5.27
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: common
Assignee: kscreen-bugs-n...@kde.org
Reporter: krg...@kevingarand.com
Target Milestone: ---

SUMMARY
I love Plasma, but no matter the distro, when I setup my 3 screens and
configure them how I like them, I choose "apply" and go to move to another
setting, Plasma then asks "do you wish to keep this setting" even though I have
already chosen apply. I choose yes, and then a simple reboot the configuration
isn't saved or "written". It simply goes back to default, which isn't how i
want them, obv.Please fix!! I humbly (not a programmer) appreciate
anyone's help in advance.
***
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
***

STEPS TO REPRODUCE
1. Either Live or install Plasma, go to configure display
2. Set displays as you want them, I have 3, and choose Apply. Go to another
setting, it will ask you "Do you wish to keep this setting" you choose yes and
reboot.
3. Displays goes back to default, as if when Apply was chosen, something
didn't write the config.

OBSERVED RESULT

EXPECTED RESULT

SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma: Does this in every distro, Fedora, KUbuntu, Debian-KDE,
OpenSuse.
(available in About System)
KDE Plasma Version: pretty much all since 5.25 or before.
KDE Frameworks Version:
Qt Version:

ADDITIONAL INFORMATION

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

[kdenlive] [Bug 470070] Resizing handles missing (Transform)

2023-05-20 Thread G Froehle

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

--- Comment #1 from G Froehle  ---
Created attachment 159157
  --> https://bugs.kde.org/attachment.cgi?id=159157=edit
Handles in Transform window

Upgraded to 23.04.1.  Sorry, did not know there was an upgrade.
The handles are now there, and they can resize the window, but the whole window
cannot be moved (click and drag) to reposition.

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

[kdenlive] [Bug 470070] New: Resizing handles missing (Transform)

2023-05-20 Thread G Froehle

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

Bug ID: 470070
   Summary: Resizing handles missing (Transform)
Classification: Applications
   Product: kdenlive
   Version: 22.12.3
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Effects & Transitions
  Assignee: j...@kdenlive.org
  Reporter: gvfroe...@hotmail.com
  Target Milestone: ---

Created attachment 159156
  --> https://bugs.kde.org/attachment.cgi?id=159156=edit
missing handles in Transfor effect

The resizing handles are missing in the Project Monitor frame when using
Transform effect.
Apologies if I am not clear.  This is a new program for me.  I appreciate your
gift!
Win 10, etc.

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

[kscreenlocker] [Bug 469687] New: Screen does not shut off when sleep inhibitor lock is created and released

2023-05-12 Thread Eric G

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

Bug ID: 469687
   Summary: Screen does not shut off when sleep inhibitor lock is
created and released
Classification: Plasma
   Product: kscreenlocker
   Version: 5.27.4
  Platform: Gentoo Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: ericgh...@gmail.com
  Target Milestone: ---

If a sleep inhibitor lock is repeatedly created and released during the
duration of the "Screen Energy Saving" switch off period, the screen will never
switch off on inactivity.  I believe this is unintended behavior based on the
similar Bug 464119;  screen switch off and sleep should not be correlated.

***

STEPS TO REPRODUCE
1. Set the "Screen Energy Saving" to switch off after 1 minute in Power Devil
2. Run the below script as root:
```
#!/bin/bash

if (( $EUID != 0 )); then
  echo "Must run as root"
  exit 1
fi

trap exit 1 SIGINT

while true; do
  systemd-inhibit --what="sleep" --who="test" --why="test" --mode="block" sleep
5
done
```

OBSERVED RESULT
Screen will not switch off after 1 minute of inactivity.


EXPECTED RESULT
Screen should switch off after 1 minute of inactivity.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma:  Gentoo (up to date stable branch 5-10-2023)
KDE Plasma Version: 5.27.4 
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.9

ADDITIONAL INFORMATION
Similar behavior was observed on Debian 12, in this case the screen shut off
momentarily and seconds later switched back on without any human interaction. 

Linux Version: Debian 12
KDE Plasma Version: 5.27.2
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8

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

[okular] [Bug 468332] Change the highlight shape from oval with rounded edges to rectangular with straight edges

2023-04-27 Thread I-G-1-1

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

--- Comment #3 from I-G-1-1  ---
(In reply to Albert Astals Cid from comment #1)
> We're going to need that file

as asked added the PDF file

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

[okular] [Bug 468332] Change the highlight shape from oval with rounded edges to rectangular with straight edges

2023-04-14 Thread I-G-1-1

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

I-G-1-1  changed:

   What|Removed |Added

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

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

[okular] [Bug 468332] Change the highlight shape from oval with rounded edges to rectangular with straight edges

2023-04-10 Thread I-G-1-1

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

--- Comment #2 from I-G-1-1  ---
Created attachment 158004
  --> https://bugs.kde.org/attachment.cgi?id=158004=edit
PDF file

as asked added the PDF file

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

[okular] [Bug 468332] New: Change the highlight shape from oval with rounded edges to rectangular with straight edges

2023-04-09 Thread I-G-1-1

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

Bug ID: 468332
   Summary: Change the highlight shape from oval with rounded
edges to rectangular with straight edges
Classification: Applications
   Product: okular
   Version: 22.12.1
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: PDF backend
  Assignee: okular-de...@kde.org
  Reporter: k6948732...@outlook.com
  Target Milestone: ---

Created attachment 157977
  --> https://bugs.kde.org/attachment.cgi?id=157977=edit
Observed and Expected Result

STEPS TO REPRODUCE
1. Open a PDF with annotations and highlights

OBSERVED RESULT
The highlights are rendered as oval shape with rounded edges. 
It's very confusing when studying if there are highlights of different color
side by side.

EXPECTED RESULT
The highlights are rendered as rectangular with straight edges. See attachment

SOFTWARE/OS VERSIONS
Windows: Windows10

ADDITIONAL INFORMATION

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

[kwayland-integration] [Bug 461910] Implement minimize to tray

2023-04-02 Thread Andreas G.

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

Andreas G.  changed:

   What|Removed |Added

 CC||m-...@andig.net

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

[dolphin] [Bug 467176] New: Systemd-homed users can't share folders

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

Bug ID: 467176
   Summary: Systemd-homed users can't share folders
Classification: Applications
   Product: dolphin
   Version: 22.12.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: tobi.goerg...@gmail.com
CC: kfm-de...@kde.org
  Target Milestone: ---

SUMMARY
When being logged in as systemd-homed user, one is not able to share folders.
While the tab appears in the properties window of a folder, the window remains
empty and doesn't show any information.
The terminal logs the following error:
PermissionsHelper::reload() failed: current user is null
qrc:/org.kde.filesharing.samba/qml/main.qml:39: TypeError: Cannot read property
'inSamba' of null

When using a non-systemd-homed user, it works as expected.

STEPS TO REPRODUCE
1.  create systemd-homed user
2. log in with it
3. try to share a folder with dolphin

OBSERVED RESULT
The share tab is empty

EXPECTED RESULT
the share tab offers options to share the folder

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Should additional information be required, I'd be happy to provide them :)

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

[kwin] [Bug 467145] New: Offline updates are not directly installed when selecting shutdown, but on next boot

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

Bug ID: 467145
   Summary: Offline updates are not directly installed when
selecting shutdown, but on next boot
Classification: Plasma
   Product: kwin
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: tobi.goerg...@gmail.com
  Target Milestone: ---

SUMMARY
Currently, when selecting shutdown with offline updates pending, the system
shuts down without installing the updates and the updates are just installed
during next boot.
Instead, when selecting shutdown and offline updates pending, the system should
reboot to install the updates and then shutdown. This way, the system is
actually usable when booting it the next time instead of sitting in front of an
update screen and not being able to do anything productive and getting as angry
on Linux for updating in the worst possible moment as on Windows.

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

[Discover] [Bug 435845] Option to shut down/restart without applying pending offline updates

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

Tobias G.  changed:

   What|Removed |Added

 CC||tobi.goerg...@gmail.com

--- Comment #8 from Tobias G.  ---
Is there any progress on this?
I really hate offline updates in KDE currently, because every simple reboot
instantly prevents me from using my computer for updates to install that were
not that important to me in this moment.
Having an option to let the user choose is, at least for me, vital.
This is the very reason I don't use offline updates currently with KDE and
can't recommend enabling them.

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

[kwin] [Bug 467142] New: Show open application when trying to close a session

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

Bug ID: 467142
   Summary: Show open application when trying to close a session
Classification: Plasma
   Product: kwin
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: tobi.goerg...@gmail.com
  Target Milestone: ---

SUMMARY
Currently, when hitting shutdown/reboot/logout in Plasma, the session is simply
quitted, no matter what applications are currently running/what their state is.
This might lead to users losing unsaved work or long shutdown times (to the
maximum defined by systems), due to applications not wanting to quit.
This problem could be solved by showing a list of still open applications after
pressing shutdown etc. and, in the best case, the user should be prominently
warned if an application reports an unsaved state.
Plasma should remain active for as long as this list is visible or a timer is
running out (e.g. 60 seconds), shutting down/rebooting anyway.
The user should have the option to cancel the shutdown or shutdown anyway.
In this phase, Plasma could already try to close open applications so the list
gets smaller and only really blocking/important applications remain.
All applications with an unsaved state should be shown and the issue should be
obvious (e.g. with a subtitle stating that there's unsaved work)
Other Desktop Environments already support this and this feature could have
prevented me from unintentionally losing edited files.
The system monitor already supports showing a list of applications, so
detecting them and distinguishing them from other processes seems to be
possible.
In a KDE manner, this feature could be made optional and not enforced to users.

Is this a useful feature?
What do others think about this?

If wanted, I could add a wireframe to visualize what I mean.

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

[krita] [Bug 465503] New: Extended Display creating problem in pointer identification

2023-02-27 Thread nishant . g

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

Bug ID: 465503
   Summary: Extended Display creating problem in pointer
identification
Classification: Applications
   Product: krita
   Version: 5.1.5
  Platform: Compiled Sources
OS: All
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Tools/Freehand
  Assignee: krita-bugs-n...@kde.org
  Reporter: nishan...@mahindraholidays.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
***


STEPS TO REPRODUCE
1. Freehand tool selected
2. Pen stylus used for input
3. Output is offset from the pointer location by considerable margin

OBSERVED RESULT
Output of any tool not in position of pointer, on using pen-stylus for input

EXPECTED RESULT
Output should be on same location as input pointer location

SOFTWARE/OS VERSIONS
Windows: 11
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

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

[digikam] [Bug 464220] New: Showfoto not exporting properly coded export videos. Use to convert time lapse images to videos. Last version to work was 6.4

2023-01-12 Thread Alan G

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

Bug ID: 464220
   Summary: Showfoto not exporting properly coded export videos.
Use to convert time lapse images to videos.  Last
version to work was 6.4
Classification: Applications
   Product: digikam
   Version: 7.8.0
  Platform: Kubuntu
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Showfoto-Usability
  Assignee: digikam-bugs-n...@kde.org
  Reporter: ranger...@twc.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
***


STEPS TO REPRODUCE
1. load up a series of TL images
2. Configure for desired output: BlueRay (1080p) usually
3. Review exported video 

OBSERVED RESULT
output file of 705 x 540 resolution

EXPECTED RESULT
1920 x 1080p

SOFTWARE/OS VERSIONS

Operating System: Kubuntu 22.04
KDE Plasma Version: 5.24.7
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3
Kernel Version: 5.15.0-58-generic (64-bit)
Graphics Platform: X11
Processors: 4 Ã— AMD Phenom(tm) II X4 B50 Processor
Memory: 15.6 GiB of RAM
Graphics Processor: AMD CEDAR

ADDITIONAL INFORMATION

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

[lattedock] [Bug 463466] New: Listed dependency libwayland-client++0 will not install - Build throws could not find QTWaylandScanner_EXECUTABLE error

2022-12-25 Thread G M Slater

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

Bug ID: 463466
   Summary: Listed dependency libwayland-client++0 will not
install - Build throws could not find
QTWaylandScanner_EXECUTABLE error
Classification: Plasma
   Product: lattedock
   Version: git (master)
  Platform: Kubuntu
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: application
  Assignee: mvourla...@gmail.com
  Reporter: gm.slater.m...@gmail.com
  Target Milestone: ---

SUMMARY
Latest git version will not build/install. Missing dependency listed as
required in Installation.md -  libwayland-client++0. Build process also shows
error Could NOT find QtWaylandScanner (missing: QtWaylandScanner_EXECUTABLE)

STEPS TO REPRODUCE
1. Clone latest git master
2. Run command shown in Installation.md to install all dependencies
3. Run install.sh script

OBSERVED RESULT
Running command shown in Installation.md to install all dependencies results in
the following error:
Package libwayland-client++0 is not available, but is referred to by another
package.
This may mean that the package is missing, has been obsoleted, or is available
only through another source.
However the following packages replace it: libwayland-client++1. (Note: I have
that version installed).

Running install.sh script results in the following error: Could NOT find
QtWaylandScanner (missing: QtWaylandScanner_EXECUTABLE)


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Ubuntu Studio 22.10
(available in About System)
KDE Plasma Version: 5.26.4
KDE Frameworks Version: 5.100.0
Qt Version: 5.15.6

ADDITIONAL INFORMATION
All dependencies are installed except for the missing/obsolete
libwayland-client++0 (libwayland-client++1 is installed)

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

[kdelibs] [Bug 194609] [Indic] Indic hunspell dictionary not default for Indic locale with kwrite, kate

2022-12-21 Thread G Karunakar

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

G Karunakar  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME

--- Comment #7 from G Karunakar  ---
(In reply to Justin Zobel from comment #6)
> Thank you for reporting this issue 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 issue with a recent software version?
> 
> If you can reproduce the issue, please change the status to "REPORTED" when
> replying. Thank you!

With the latest version (KDE on Debian), it was working fine. With user
language set to Hindi, spellcheck (using hunspell hindi) defaulted to Hindi.
I will check on Kubuntu also.

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

[plasmashell] [Bug 438092] Some Hindi words are not displaying in a proper format.

2022-12-21 Thread G Karunakar

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

G Karunakar  changed:

   What|Removed |Added

 CC||karuna...@indlinux.org

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

[konsole] [Bug 451716] Hindi font display issues: halant cut too short, horizontal line break

2022-12-21 Thread G Karunakar

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

G Karunakar  changed:

   What|Removed |Added

 CC||karuna...@indlinux.org

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

[kscreenlocker] [Bug 462617] New: Laptop doesn't go into hibernation if in standby for a long time

2022-12-03 Thread Tobias G.

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

Bug ID: 462617
   Summary: Laptop doesn't go into hibernation if in standby for a
long time
Classification: Plasma
   Product: kscreenlocker
   Version: 5.26.4
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: tobi.goerg...@gmail.com
  Target Milestone: ---

SUMMARY
Hey there, 
I use Plasma on a Laptop and selected that it should go into hibernation mode
after being in standby mode for a while. 
While going into hibernation directly, this option doesn't work. The laptop
never goes to actual hibernation, but always stays in standby consuming battery
constantly. 
There is also no error message, indicating why it doesn't work (if it was ever
triggered) 
(error messages for failing hibernation would in general be great, rarely I
manually want to go into hibernation and it doesn't work (probably full swap
file)) 
And what exactly is "a while"? :D


STEPS TO REPRODUCE
1. Activate go into deepleep after a while setting
2. Put your device into standby
3. Observe after "a while" that it hasn't gone into hibernation

OBSERVED RESULT
Device stays in standby mode

EXPECTED RESULT
Device goes to hibernation mode

SOFTWARE/OS VERSIONS
Manjaro Linux stable

ADDITIONAL INFORMATION
Should any additional information be required, I'd be happy to provide them. :)

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

[kwin] [Bug 461615] Workspace only in top left corner with rotated display

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

--- Comment #2 from Tobias G.  ---
Created attachment 153604
  --> https://bugs.kde.org/attachment.cgi?id=153604=edit
broken setup

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

[kwin] [Bug 461615] Workspace only in top left corner with rotated display

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

--- Comment #1 from Tobias G.  ---
Created attachment 153603
  --> https://bugs.kde.org/attachment.cgi?id=153603=edit
correct setup

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

[kwin] [Bug 461615] Workspace only in top left corner with rotated display

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

Tobias G.  changed:

   What|Removed |Added

Version|5.24.5  |5.26.2

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

[kwin] [Bug 461615] New: Workspace only in top left corner with rotated display

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

Bug ID: 461615
   Summary: Workspace only in top left corner with rotated display
Classification: Plasma
   Product: kwin
   Version: 5.24.5
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: multi-screen
  Assignee: kwin-bugs-n...@kde.org
  Reporter: tobi.goerg...@gmail.com
  Target Milestone: ---

SUMMARY
Hey there,

since the update to Plasma 5.26.2, I sometimes can't interact (after
reboot/waking from sleep) with my system as the workspace is only shown in the
top left corner of my main screen that I can't interact with (neither in the
top left nor where the elements should actually be on the screen) (I attached
pictures of what it looks like and what my setup should be).
When it happens, it completely disables the rotated screen.
Sometimes I can "fix" it by hitting ctrl+alt+F2 and ctrl+alt+F1 again, then
it's at least shown correctly on one screen.
Enabling and rotating the disabled screen breaks it again, until the timer runs
up asking for confirmation of the setup (btw. thanks for adding it).
I can, however, mostly make it work again by first activating the screen and
confirming it and then rotating it.
Should any additional information be required, I'd be happy to help :)


STEPS TO REPRODUCE
1. have rotated screen
2. reboot
3. observe

OBSERVED RESULT
the rotated display is turned off and the workspace shown in one corner

EXPECTED RESULT
The rotated screen is turned on and confirgured correctly

SOFTWARE/OS VERSIONS
Betriebssystem: Manjaro Linux
KDE-Plasma-Version: 5.26.2
KDE-Frameworks-Version: 5.99.0
Qt-Version: 5.15.6
Kernel-Version: 5.15.75-xanmod1-1.1-lts (64-bit)
Grafik-Plattform: X11
Prozessoren: 8 × Intel® Core™ i7-6700K CPU @ 4.00GHz
Speicher: 23,4 GiB Arbeitsspeicher
Grafikprozessor: NVIDIA GeForce GTX 1080/PCIe/SSE2
ADDITIONAL INFORMATION

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

[kscreenlocker] [Bug 433495] Lock screen greeter fails to visually update when system is woken up while connected to TV via receiver

2022-11-06 Thread Tobias G.

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

--- Comment #6 from Tobias G.  ---
Sorry for the late reply,

this issue seems to be fixed now :)
Should it ever happen again, I'll reopen this bug report

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

[frameworks-qqc2-desktop-style] [Bug 451232] Broken font rendering in wayland

2022-11-06 Thread Tobias G.

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

--- Comment #7 from Tobias G.  ---
Hey there,

I tested a few things and I noticed that all my text looks broken, when I
disable font smoothing (disabling anti-aliasing).
Might it be that it's not applied everywhere for some reason on my system?

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

[Skanpage] [Bug 461359] New: black-and-white / monochrome mode missing

2022-11-03 Thread M G Berberich

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

Bug ID: 461359
   Summary: black-and-white / monochrome mode missing
Classification: Applications
   Product: Skanpage
   Version: unspecified
  Platform: Debian testing
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: a.stipp...@gmx.net
  Reporter: k...@oss.m-berberich.de
  Target Milestone: ---

I build skanpage from git, version is “skanpage 22.11.70”
( 22.11.70 is not in the version-list on bugs.kde.org)

The tools misses a option for creating black and white (2-color/monochrom)
scans. This saves a lot of disk-space and is sufficient for most non-colored
document. There are scanner that do not support monochrom output and sane has
the policy to not add functionality in the backends, but leave this for
frontends. So providing a monochrom option in skanpage is the  correct place.

In my example, I got for a 1-page A4 pdf:

skanpage grayscale: 9,1M
black-and-white converted: 232K

At first attempt a simple threshold at 50% would be O.K.

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

[kwin] [Bug 461302] New: kwin_x11 - Missing symbol drmModeFormatModifierBlobIterNext

2022-11-01 Thread Tom G

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

Bug ID: 461302
   Summary: kwin_x11 - Missing symbol
drmModeFormatModifierBlobIterNext
Classification: Plasma
   Product: kwin
   Version: 5.26.0
  Platform: Debian testing
OS: Linux
Status: REPORTED
  Severity: critical
  Priority: NOR
 Component: platform-x11-standalone
  Assignee: kwin-bugs-n...@kde.org
  Reporter: t...@nc.rr.com
  Target Milestone: ---

SUMMARY
~$ kwin_x11 --replace
kwin_x11: symbol lookup error: /lib/x86_64-linux-gnu/libkwin.so.5: undefined
symbol: drmModeFormatModifierBlobIterNext

STEPS TO REPRODUCE
1.  kwin --replace
2. 
3. 

OBSERVED RESULT
kwin_x11: symbol lookup error: /lib/x86_64-linux-gnu/libkwin.so.5: undefined
symbol: drmModeFormatModifierBlobIterNext

EXPECTED RESULT
expect to kill existing kwin_x11 and start a new instance

SOFTWARE/OS VERSIONS
Operating System: Debian GNU/Linux - Debian 11 - $ uname -a
Linux wallet 6.0.0-2-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.0.5-1 (2022-10-28)
x86_64 GNU/Linux
KDE Plasma Version: 5.26.0
KDE Frameworks Version: 5.98.0
Qt Version: 5.15.6
Kernel Version: 6.0.0-2-amd64 (64-bit)
Graphics Platform: X11
Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor
Memory: 62.8 GiB of RAM
Graphics Processor: AMD Radeon RX Vega
Manufacturer: Micro-Star International Co., Ltd.
Product Name: MS-7C35
System Version: 2.0

ADDITIONAL INFORMATION

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

[valgrind] [Bug 458845] The L field for the dcbf and sync instruction should be 3 bits in ISA 3.1

2022-09-07 Thread Shivaprasad G

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

Shivaprasad G  changed:

   What|Removed |Added

 CC||shivaprasadb...@gmail.com

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

[Powerdevil] [Bug 432694] Suspend-then-hibernate not working as expected

2022-08-18 Thread Robert G. Siebeck

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

Robert G. Siebeck  changed:

   What|Removed |Added

 CC||kde.bugzilla.2...@r123.de

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

[plasma-integration] [Bug 456256] New: FileDialog does not honor QFileDialog::HideNameFilterDetails

2022-07-02 Thread M G Berberich

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

Bug ID: 456256
   Summary: FileDialog does not honor
QFileDialog::HideNameFilterDetails
   Product: plasma-integration
   Version: git-stable-Plasma/5.24
  Platform: Debian testing
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: k...@oss.m-berberich.de
  Target Milestone: ---

Created attachment 150343
  --> https://bugs.kde.org/attachment.cgi?id=150343=edit
KDE-File-Dialog not showing filters after description

SUMMARY

The KDE file-dialog that replaces the QFileDialog on non-KDE applications does
not honor the QFileDialog::HideNameFilterDetails flag of QFileDialog. 
The QFileDialog can show the filters in parentheses behind the description,
p.e. “STL Mesh (*.stl)”
The KDE file dialog never shows the filter.

The transformation of the filters from QT to KDE syntax is done in
/src/platformtheme/kdeplatformfiledialoghelper.cpp:qt2KdeFilter()

Always show the filter can be done by editing this function

str << it->mid(ob + 1, (cb - ob) - 1) << '|' << it->mid(0, ob) << "
(" << it->mid(ob + 1, (cb - ob) - 1) << ")";

but I think the correct way to do this would be either to have a
QFileDialog::HideNameFilterDetails functionality in the kde filedialog and
interface it or let KDEPlatformFileDialogHelper append the filter to the
description, depending on QFileDialog::HideNameFilterDetails

STEPS TO REPRODUCE
1. Start a non-KDE_application like FreeCAD
2. Try to save something (p.e. export a object)
3. See that filters are not shown in the drop-down-box

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

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

[Akonadi] [Bug 454948] Akonadi server will not start on fresh install; yields "unknown error"

2022-06-07 Thread Andreas G.

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

Andreas G.  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 CC||m-...@andig.net
 Ever confirmed|0   |1

--- Comment #1 from Andreas G.  ---
Same issue after updating Arch Linux today. Same program versions as you.
Downgrading to the previous version of mariadb made Akonadi usable again. 

Packages that were downgraded:
mariadb-10.7.4-1
mariadb-clients-10.7.4-1
mariadb-libs-10.7.4-1

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

[kwin] [Bug 454871] New: (SDDM) Login screen doesn't save rotation of screen

2022-06-05 Thread Tobias G.

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

Bug ID: 454871
   Summary: (SDDM) Login screen doesn't save rotation of screen
   Product: kwin
   Version: 5.24.5
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: tobi.goerg...@gmail.com
  Target Milestone: ---

SUMMARY
Hey there,
I've tried in the past few hours to make SDDM save the rotation of my screens,
as one is rotated by 90°. But unfortunately, SDDM just doesn't want to do that.
I've tried to synchronize the settings in wayland and X11, but the log in
screen always has the wrong orientation.
Am I missing something?

PS: I couldn't find SDDM as module to open this bug, so I opened it here, I
hope that's OK.

STEPS TO REPRODUCE
1. rotate display by 90°
2. sync settings with login screen
3. log out

OBSERVED RESULT
SDDM is not rotated by 90°

EXPECTED RESULT
SDDM should be rotated by 90°

SOFTWARE/OS VERSIONS
Operating System: Manjaro Linux
KDE Plasma Version: 5.24.5
KDE Frameworks Version: 5.94.0
Qt Version: 5.15.4
Kernel Version: 5.17.9-1-MANJARO (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-6700K CPU @ 4.00GHz
Memory: 23.4 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1080/PCIe/SSE2

ADDITIONAL INFORMATION

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

[kwin] [Bug 454630] Add support for System76 scheduler

2022-06-03 Thread Tobias G.

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

--- Comment #2 from Tobias G.  ---
(In reply to David Edmundson from comment #1)
> This is out of scope

Are you sure?
I don't really know what would have to be done, but there is a kwin script that
does exactly that.
AFAIK, KWin "just" has to tell the scheduler which window is curently focussed
to increase it's niceness.
The script can be found here: https://store.kde.org/p/1789957

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

[kscreenlocker] [Bug 454627] Add support for face unlock

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

--- Comment #2 from Tobias G.  ---
(In reply to Phos from comment #1)
> Hey Tobias, you might want to check out Howdy
> https://github.com/Boltgolt/howdy

Hi, thank you, I already heard of Howdy. :)
Unfortunately, it doesn't have a graphical interface for setup, requires manual
configuration and users have to search for it manually.
It would be way more convenient if KDE included this natively.

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

[kwin] [Bug 454642] New: automatically hidden panel inaccessible using touch screen

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

Bug ID: 454642
   Summary: automatically hidden panel inaccessible using touch
screen
   Product: kwin
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: tobi.goerg...@gmail.com
  Target Milestone: ---

SUMMARY
Hey guys,
whenever I set a plasma/latte panel or dock to auto hide, the dock is not
accessible anymore using the touchscreen. Moving with the finger to the edge
doesn't make the panel appear.
This happens with the default plasma panels or panels/docks added using Latte. 


STEPS TO REPRODUCE
1. add panel to workspace
2. set panel to auto-hide
3. try to make it visible using touch screen

OBSERVED RESULT
panel stays hidden

EXPECTED RESULT
panel should appear

SOFTWARE/OS VERSIONS
Operating System: Manjaro Linux
KDE Plasma Version: 5.24.5
KDE Frameworks Version: 5.94.0
Qt Version: 5.15.4
Kernel Version: 5.17.9-1-MANJARO (64-bit)
Graphics Platform: Wayland
Processors: 6 × AMD Ryzen 5 4500U with Radeon Graphics
Memory: 7.2 GiB of RAM
Graphics Processor: AMD RENOIR

ADDITIONAL INFORMATION

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

[lattedock] [Bug 454641] New: "Edit dock/panel" button unreliable in wayland session

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

Bug ID: 454641
   Summary: "Edit dock/panel" button unreliable in wayland session
   Product: lattedock
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: application
  Assignee: mvourla...@gmail.com
  Reporter: tobi.goerg...@gmail.com
  Target Milestone: ---

SUMMARY
Hey guys,
in a wayland session, the "Edit dock/panel" button works very unreliable.
Either, the blue background is shown for a short time, but then disappears and
I have to open it again or the menu opens for half a second and latte crashes
or it just opens normally.
This doesn't happen in X11


STEPS TO REPRODUCE
1. start latte
2. right click on dock
3. hit "Edit dock/panel" button

OBSERVED RESULT
the menu is not always shown, but latte crashes or the menu is closed after
half a second

EXPECTED RESULT
the menu opens and waits for input

SOFTWARE/OS VERSIONS
Operating System: Manjaro Linux
KDE Plasma Version: 5.24.5
KDE Frameworks Version: 5.94.0
Qt Version: 5.15.4
Kernel Version: 5.17.9-1-MANJARO (64-bit)
Graphics Platform: Wayland
Processors: 6 × AMD Ryzen 5 4500U with Radeon Graphics
Memory: 7.2 GiB of RAM
Graphics Processor: AMD RENOIR

ADDITIONAL INFORMATION

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

[lattedock] [Bug 454640] New: Unable to use context menu when app preview is enabled on wayland

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

Bug ID: 454640
   Summary: Unable to use context menu when app preview is enabled
on wayland
   Product: lattedock
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: application
  Assignee: mvourla...@gmail.com
  Reporter: tobi.goerg...@gmail.com
  Target Milestone: ---

SUMMARY
Hey guys,
on wayland, I'm unable to use the context menu if prior to that the preview
window is shown (by hovering over an opened application). The context menu is
opened with a right click, as soon as one moves out of the preview window, not
only the preview is closed, but also the context menu, making it
tricky/impossible to use it in that case.


STEPS TO REPRODUCE
1. start wayland session and latte
2. enable window preview on hover
3. right click on opened app
4. try to access context menu

OBSERVED RESULT
the context menu is closed with the preview

EXPECTED RESULT
the preview is closed, but the context menu stays open

SOFTWARE/OS VERSIONS
Operating System: Manjaro Linux
KDE Plasma Version: 5.24.5
KDE Frameworks Version: 5.94.0
Qt Version: 5.15.4
Kernel Version: 5.17.9-1-MANJARO (64-bit)
Graphics Platform: Wayland
Processors: 6 × AMD Ryzen 5 4500U with Radeon Graphics
Memory: 7.2 GiB of RAM
Graphics Processor: AMD RENOIR

ADDITIONAL INFORMATION

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

[kwin] [Bug 454632] New: Add energy modes to energy applet

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

Bug ID: 454632
   Summary: Add energy modes to energy applet
   Product: kwin
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: tobi.goerg...@gmail.com
  Target Milestone: ---

SUMMARY
Hey guys,
it would be nice if the energy applet showed the option to change the system's
behavior, e.g. a battery saving mode, underclocking CPU/GPU and reducing the
display brightness, a balanced mode (normal) and a performance mode with more
aggressive clocking.
This would give the users the opportunity to decide on their own, whether they
prefer battery life or performance, based on the current situation.

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

[plasmashell] [Bug 454631] New: Add context menu to run application using dGPU

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

Bug ID: 454631
   Summary: Add context menu to run application using dGPU
   Product: plasmashell
   Version: master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: tobi.goerg...@gmail.com
CC: k...@davidedmundson.co.uk
  Target Milestone: 1.0

SUMMARY
Hey there,
it would be nice if KDE Plasma showed a menu entry in the context menu for
applications to run them using a dGPU on systems, where it is supported.

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

[kwin] [Bug 454630] New: Add support for System76 scheduler

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

Bug ID: 454630
   Summary: Add support for System76 scheduler
   Product: kwin
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: tobi.goerg...@gmail.com
  Target Milestone: ---

SUMMARY
Hey guys,
System76 developed a scheduler with better responsiveness for their system.
It would be great if KDE Plasma also supported the scheduler out of the box, to
deliver the best experience.
The repo can be found here:
https://github.com/pop-os/system76-scheduler

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

[kwin] [Bug 454629] New: System hangs in Plymouth splash screen

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

Bug ID: 454629
   Summary: System hangs in Plymouth splash screen
   Product: kwin
   Version: 5.24.4
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: tobi.goerg...@gmail.com
  Target Milestone: ---

SUMMARY
Hey guys,
sometimes (1/3 times), when starting my system, I never see Plasma, but
instead, the plymouth splash screen is shown endlessly spinning. Nothing
happens then, I can prevent that by hitting an F key early, then Plasma is
starting reliably.
I haven't tested it with Plasma 5.24.5 yet, but it happened on 5.24.4.
It also just happened with wayland sessions so far.


STEPS TO REPRODUCE
1. boot system into wayland session
2. observe plymouth

OBSERVED RESULT
plymouth is shown endlessly

EXPECTED RESULT
plymouth is terminated and Plasma is shown

SOFTWARE/OS VERSIONS
Operating System: Manjaro Linux
KDE Plasma Version: 5.24.5
KDE Frameworks Version: 5.94.0
Qt Version: 5.15.4
Kernel Version: 5.17.9-1-MANJARO (64-bit)
Graphics Platform: Wayland
Processors: 6 × AMD Ryzen 5 4500U with Radeon Graphics
Memory: 7.2 GiB of RAM
Graphics Processor: AMD RENOIR

ADDITIONAL INFORMATION

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

[kdeplasma-addons] [Bug 454628] New: Add option to hide session options

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

Bug ID: 454628
   Summary: Add option to hide session options
   Product: kdeplasma-addons
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: Application Dashboard
  Assignee: plasma-b...@kde.org
  Reporter: tobi.goerg...@gmail.com
  Target Milestone: ---

SUMMARY
Hey there,
It would be nice if the application dashboard had an option to hide the session
menu (with poweroff, reboot, etc.).
Currently, this is not possible.

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

[kscreenlocker] [Bug 454627] New: Add support for face unlock

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

Bug ID: 454627
   Summary: Add support for face unlock
   Product: kscreenlocker
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: kcheckpass
  Assignee: plasma-b...@kde.org
  Reporter: tobi.goerg...@gmail.com
CC: bhus...@gmail.com
  Target Milestone: ---

SUMMARY
Hey there,

it would be nice if Plasma supported unlocking the screen/logging in using face
unlock, similar to how fingerprint unlock works.
This could either only work with infrared-cams or with "Normal" cams as well,
though they might not be as secure.
Executing root commands should also be possible using it.

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

[kwin] [Bug 454626] New: screen turns on again when switching to hibernation