[lattedock] [Bug 450986] new pinned launcher appears on all unique tasks

2022-03-04 Thread Michail Vourlakos
https://bugs.kde.org/show_bug.cgi?id=450986

--- Comment #4 from Michail Vourlakos  ---
Some feedback why this occurs in master version. So idea why it also breaks for
stable v0.10.7 . I will try to fix it for git version. Git version currently
supports Clones of docks and panels in order to support dock OnAllScreens and
OnAllSecondaryScreens. So the applets groupid needs to be updated in order to
take into account the clones infrastructure. Probably applet.groupId needs to
become in the form OriginalViewId#applets_position

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

[lattedock] [Bug 450986] new pinned launcher appears on all unique tasks

2022-03-04 Thread Michail Vourlakos
https://bugs.kde.org/show_bug.cgi?id=450986

Michail Vourlakos  changed:

   What|Removed |Added

Summary|[wayland] - new pinned  |new pinned launcher appears
   |launcher appears on all |on all unique tasks
   |unique tasks|

--- Comment #3 from Michail Vourlakos  ---
Some feedback why this occurs in master version. So idea why it also breaks

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

[lattedock] [Bug 450986] [wayland] - new pinned launcher appears on all unique tasks

2022-03-04 Thread Michail Vourlakos
https://bugs.kde.org/show_bug.cgi?id=450986

Michail Vourlakos  changed:

   What|Removed |Added

Version|0.10.7  |git (master)

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

[lattedock] [Bug 450986] [wayland] - new pinned launcher appears on all unique tasks

2022-03-04 Thread Michail Vourlakos
https://bugs.kde.org/show_bug.cgi?id=450986

Michail Vourlakos  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

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

[kde-cli-tools] [Bug 429408] kde-open5 changes case of argument

2022-03-04 Thread Egon Willighagen
https://bugs.kde.org/show_bug.cgi?id=429408

Egon Willighagen  changed:

   What|Removed |Added

 CC||egon.willigha...@gmail.com

--- Comment #3 from Egon Willighagen  ---
I got here via this StackOverflow workaround for a problem where Slack does not
open all workspaces. The SO flow suggests the same upper/lower rewrite by KDE
as a suspect. Here is some data from my machine just now (for privacy I use
fake codes, like WORKSPACEID, xxx, , and zzz, of course with upper/lower
casing exact):

/bin/sh /usr/bin/xdg-open
slack://WORKSPACEID/magic-login///magic-login/zzz-z-z
kde-open5
slack://WORKSPACEID/magic-login///magic-login/zzz-z-z
/usr/lib/slack/slack --enable-crashpad
slack://workspaceid/magic-login///magic-login/zzz-z-z

I hope you trust my translation of my observation, but I can confirm that
WORKSPACEID goed into kde-open5 as upper case, but is converted to lower case
when passed to the `/usr/lib/slack/slack` application. And Slack seems to be
case sensitive as suggested in the SO post: if I upper case back the
WORKSPACEID in the `/usr/lib/slack/slack` call, then it opens properly.

* Slack 4.23.0
* kde-open5/kioclient 5.20.5

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

[Discover] [Bug 451077] Discover fails on minor updates in kde neon

2022-03-04 Thread Christian Hartmann
https://bugs.kde.org/show_bug.cgi?id=451077

--- Comment #3 from Christian Hartmann  ---
apparently
$ sudo dpkg --configure -a
fixed it

and likely 
$ sudo dpkg-reconfigure libc6
would also do the job

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

[umbrello] [Bug 369464] Data type with modifiers are space sensitive

2022-03-04 Thread Oliver Kellogg
https://bugs.kde.org/show_bug.cgi?id=369464

Oliver Kellogg  changed:

   What|Removed |Added

   Version Fixed In||2.33.80 (KDE releases
   ||22.03.80)
 Resolution|--- |FIXED
  Latest Commit||https://invent.kde.org/sdk/
   ||umbrello/commit/999d6338f4c
   ||4baec178626fb3bff175e2bac79
   ||06
 Status|ASSIGNED|RESOLVED

--- Comment #1 from Oliver Kellogg  ---
Git commit 999d6338f4c4baec178626fb3bff175e2bac7906 by Oliver Kellogg.
Committed on 05/03/2022 at 07:09.
Pushed by okellogg into branch 'master'.

Fix "Data type with modifiers are space sensitive"

umbrello/model_utils.{h,cpp}
- New function normalize(QString type) removes interspersed spaces from
  given type name where possible: Between word and non word, between non
  word and word, between non word and non word.  Space between word and
  word is left intact to preserve names such as "unsigned long long".
- In function findUMLObject:
  - On assigning to name apply normalize() to inName.
  - As a peripheral change, fix bug number in #ifdef TRY_BUGFIX_120862.

umbrello/codeimport/kdevcppparser/cpptree2uml.cpp
- In function typeOfDeclaration for-loop over ptrOpList, on assigning to
  `text' remove spaces from ptrOpList.at(i)->text() as done in loop over
  declarator->arrayDimensionList().

umbrello/dialogs/dialog_utils.cpp
- In function askName apply Model_Utils::normalize() on returned name.

umbrello/dialogs/widgets/umldatatypewidget.cpp
- In functions applyAttribute, applyEntityAttribute, applyOperation,
  applyParameter, on assigning to typeName apply Model_Utils::normalize
  on m_editField->currentText().

umbrello/umldoc.cpp
- In function findDatatype apply Model_Utils::normalize() to name before
  processing.
FIXED-IN:2.33.80 (KDE releases 22.03.80)

M  +4-2umbrello/codeimport/kdevcppparser/cpptree2uml.cpp
M  +4-3umbrello/dialogs/dialog_utils.cpp
M  +6-5umbrello/dialogs/widgets/umldatatypewidget.cpp
M  +32   -2umbrello/model_utils.cpp
M  +2-0umbrello/model_utils.h
M  +1-0umbrello/umldoc.cpp

https://invent.kde.org/sdk/umbrello/commit/999d6338f4c4baec178626fb3bff175e2bac7906

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

[Akonadi] [Bug 449024] Unable to fetch google calendar events

2022-03-04 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=449024

--- Comment #41 from siauder...@hotmail.com ---
Thank you for fixing it! It works now, I just updated on Kubuntu!

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

[rkward] [Bug 450479] Cannot start the software: R engine has died, The backend process failed to start with exit code 6.

2022-03-04 Thread Thomas Friedrichsmeier
https://bugs.kde.org/show_bug.cgi?id=450479

--- Comment #4 from Thomas Friedrichsmeier  
---
Meanwhile I managed to get our MacOS builds back online, but I now believe the
problem is not actually related to the version of R, but to changes in the
codesigning. If you have a few minutes to spare, could you download and test
this new build:
https://binary-factory.kde.org/view/MacOS/job/RKWard_Nightly_macos/lastSuccessfulBuild/artifact/rkward-master-992-macos-64-clang.dmg
?

It will _not_ fix the problem, but it should give some additional info on the
cause of the problem. Could you copy and post that?

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

[umbrello] [Bug 369464] Data type with modifiers are space sensitive

2022-03-04 Thread Oliver Kellogg
https://bugs.kde.org/show_bug.cgi?id=369464

Oliver Kellogg  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|ASSIGNED
 CC||okellogg@users.sourceforge.
   ||net

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

[kdeconnect] [Bug 451154] KDE connect does not discover PC and Android (each other) if the connection is Mobile Hotspot Tethering started from Android and Windows laptop connected to it.

2022-03-04 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=451154

darkphoenix...@protonmail.com changed:

   What|Removed |Added

Summary|KDE connect does not|KDE connect does not
   |discove PC and Android  |discover PC and Android
   |(each other) if the |(each other) if the
   |connection is Mobile|connection is Mobile
   |Hotspot Tethering started   |Hotspot Tethering started
   |from Android and Windows|from Android and Windows
   |laptop connected to it. |laptop connected to it.

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

[kdeconnect] [Bug 451154] New: KDE connect does not discove PC and Android (each other) if the connection is Mobile Hotspot Tethering started from Android and Windows laptop connected to it.

2022-03-04 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=451154

Bug ID: 451154
   Summary: KDE connect does not discove PC and Android (each
other) if the connection is Mobile Hotspot Tethering
started from Android and Windows laptop connected to
it.
   Product: kdeconnect
   Version: unspecified
  Platform: Android
OS: Android 11.x
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: android-application
  Assignee: albertv...@gmail.com
  Reporter: darkphoenix...@protonmail.com
  Target Milestone: ---

SUMMARY
***
It works perfectly if there is a Wifi but i don't have wifi and i use mobile
hotspot to share my intenet to my laptop.
With Android custom rom, the ip address keep changing and cannot be set to
static for hotspot. Hostname also don't work.
I tried two android device one with custom rom and one with moto stock rom both
on Android 11. The Android device and Windows PC are able to discover each
other if Hotspot is started from Third device ( android device acting as a wifi
router).
I use syncthing and my android device and windows pc are able to discover each
other.

It would be very good if support for discovering Windows PC and Android device
using Hotspot tethering can be added.

Also if i manually add ipv4 address of my hotspot to KDE connect android app.
pc-discovers each other but as my ip keep changing with each hotspot session.
its not possible to use this method.

Also, i tried using Two Android device connected to each other using Hospot
tethering started by one device- the result- they were discovering each other.
***


STEPS TO REPRODUCE
1. Start Hotspot from Android Device.
2. Connect windows pc to that hotspot using wifi.
3. Start KDE connect on both device.

OBSERVED RESULT

Device not discovering each other until manually ip address is added to the
android kde connect app.

EXPECTED RESULT

Device automatically abe to discover each other.

SOFTWARE/OS VERSIONS
Windows: 21H2 ( build 19044.1526)
KDE connect windows version : latest from MS Store ( 21.1200.818.0
publisher-KDE e,V.)
Android version : 1.19.1 from Fdroid

PS: I tried to reproduce same with my third android devie running and the same
thing happed- not discovering each other.

Also the hostname is in top left of Find device in windows kde connect app
right ?
i tried adding it in Add device by IP in KDE connect android app, eg-
DESKTOP-QT7AATI but still not discovering each other.

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

[digikam] [Bug 451153] Incomplete Mariadb PrivCheck delete causes digiKam fail to start.

2022-03-04 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=451153

caulier.gil...@gmail.com changed:

   What|Removed |Added

 CC||caulier.gil...@gmail.com
Summary|Incomplete PrivCheck delete |Incomplete Mariadb
   |causes Digikam to fail  |PrivCheck delete causes
   ||digiKam fail to start.

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

[digikam] [Bug 451153] New: Incomplete PrivCheck delete causes Digikam to fail

2022-03-04 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=451153

Bug ID: 451153
   Summary: Incomplete PrivCheck delete causes Digikam to fail
   Product: digikam
   Version: 7.6.0
  Platform: Mint (Ubuntu based)
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Database-Mysql
  Assignee: digikam-bugs-n...@kde.org
  Reporter: bugskde...@goland.org
  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. Not completely sure since the state described below shouldn't have happened,
I can only assume that the DROP TABLE in PrivCheck got into a bad state?
2. 
3. 

OBSERVED RESULT
Starting Digikam causes the error:
You have insufficient privileges on the database.
Following privileges are not assigned to you:
   CREATE TABLE
Check your privileges on the database and restart digikam.

EXPECTED RESULT
Program works fine

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

ADDITIONAL INFORMATION
At some point Maria DB entered a state where .mysql.digikam/db_data/digikam
contained a PrivCheck.idb file but no PrivCheck.frm file. Once Maria DB got
into this state the PrivCheck table creation fails because it can't create a
table under those circumstances. In the end the only fix I could find was to
manually delete the PrivCheck.idb file from the file system.

I have no expertise with mariadb but the docs imply that it isn't possible to
issue a CREATE TABLE and a DROP TABLE in the same transaction. But perhaps it
would be possible to put in code that when PrivCheck fails, checks the table
directory to see if this state has been entered and deletes the PrivCheck.idb
file and tries again? Just a thought.

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

[amarok] [Bug 450500] Amarok boosts audio to the maximum, with manual track changes

2022-03-04 Thread Edar José Blanco Rodríguez
https://bugs.kde.org/show_bug.cgi?id=450500

--- Comment #7 from Edar José Blanco Rodríguez  ---
(In reply to Edar José Blanco Rodríguez from comment #6)
> El error ocurre al intentar cambiar una pista de manera manual, si solo sigo
> la reproducion de la lista, y cambia de manera automatica, nada sucede si el
> volumen esta en 80% se mantiene asi, pero si es cabiada la pista manualmente
> el volumen regresa a 100%, esto comenzo a suceder cuando actualize desde KDE
> 5.23 a 5.24, my phonon backend hasn't changed
> 
> > Which phonon backend do you use?
> 
> phonon-qt5-gstreamer

My mistake, I wrote in Spanish

The error occurs when trying to change a track manually, if I just follow the
playback of the list, and it changes automatically, nothing happens if the
volume is at 80% it stays that way, but if the track is changed manually the
volume returns at 100%, this started to happen when I upgraded from KDE 5.23 to
5.24, my phonon backend hasn't changed

> Which phonon backend do you use?

 phonon-qt5-gstreamer

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

[amarok] [Bug 450500] Amarok boosts audio to the maximum, with manual track changes

2022-03-04 Thread Edar José Blanco Rodríguez
https://bugs.kde.org/show_bug.cgi?id=450500

Edar José Blanco Rodríguez  changed:

   What|Removed |Added

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

--- Comment #6 from Edar José Blanco Rodríguez  ---
El error ocurre al intentar cambiar una pista de manera manual, si solo sigo la
reproducion de la lista, y cambia de manera automatica, nada sucede si el
volumen esta en 80% se mantiene asi, pero si es cabiada la pista manualmente el
volumen regresa a 100%, esto comenzo a suceder cuando actualize desde KDE 5.23
a 5.24, my phonon backend hasn't changed

> Which phonon backend do you use?

phonon-qt5-gstreamer

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

[kwin] [Bug 447705] Flickering in Wayland session when returning from standby

2022-03-04 Thread mjeff
https://bugs.kde.org/show_bug.cgi?id=447705

mjeff  changed:

   What|Removed |Added

 CC||fe...@fegul.com

--- Comment #14 from mjeff  ---
Same issue on my end (Intel Iris xe graphics on an i7-1185G7)

There are also issues where, when resuming a session, unlocking the desktop,
etc. my laptop screen is suddenly activated (even when it is closed) and the
wallpaper on my 4k screen shrinks to fill just 1/4 of the screen (like when you
snap a window to the upper right of a screen)

I have to reopen my laptop lid, close it again, change my main screen
resolution briefly and then set it back to 4k, and then it works fine again (I
have to follow these steps every time)

I see the following entries in my logs in regards to the flickering:
3/5/22 8:58 AM  xdg-desktop-portal-kde  xdp-kde-background: GetAppState called:
no parameters
3/5/22 8:59 AM  xdg-desktop-portal-kde  xdp-kde-background: GetAppState called:
no parameters
3/5/22 8:59 AM  xdg-desktop-portal-kde  xdp-kde-background: GetAppState called:
no parameters

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

[plasmashell] [Bug 441730] Panel does not remain hidden in multi-monitor setups.

2022-03-04 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=441730

lnx...@westlot.net changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |NOT A BUG

--- Comment #5 from lnx...@westlot.net ---
This seems to be some possible ridicule issue with my config files or
something, so I'm changing this to resolved, not a bug.

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

[plasmashell] [Bug 450506] panel freezes plasmashell on wayland crashes

2022-03-04 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=450506

--- Comment #4 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

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

[okular] [Bug 449448] Pre-render the subsequent page, and speed-up the large PDF rendering (even the text PDFs are too slow at the moment)

2022-03-04 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=449448

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

--- Comment #10 from Bug Janitor Service  ---
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!

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

[amarok] [Bug 450500] Amarok boosts audio to the maximum, with manual track changes

2022-03-04 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=450500

--- Comment #5 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

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

[dolphin] [Bug 450477] when going to search and hit enter then it not showing results but showing Invalid protocol.

2022-03-04 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=450477

--- Comment #2 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

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

[kwin] [Bug 450451] kwin_wayland randomly crashed

2022-03-04 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=450451

--- Comment #2 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

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

[lattedock] [Bug 450194] Latte dock crashed on opening browser and some webapps

2022-03-04 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=450194

--- Comment #2 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

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

[plasmashell] [Bug 441730] Panel does not remain hidden in multi-monitor setups.

2022-03-04 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=441730

--- Comment #4 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

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

[kdeconnect] [Bug 449719] KDE Connect crashes when opening a message

2022-03-04 Thread Simon Redman
https://bugs.kde.org/show_bug.cgi?id=449719

--- Comment #5 from Simon Redman  ---
(In reply to Nathan from comment #4)
> Looks like no one is even reading these bug reports

I read every bug report which is assigned to me and I'm sorry you get the
impression that bug reports don't get read. I have an old house and a taxing
job, so I don't have time or energy to act on most of them.

The problem described in this bug looks like it might be pretty simple. In
ConversationModel::createRowFromMessage, it seems to be trying to take the
.first() of the list of message address and failing, presumably because the
list is empty. I don't know why a conversation would exist with no addresses
(that's probably the more interesting thing to investigate), but a quick fix
would be to just have the app check that there is at least one entry before
trying to take the first.

Since I can't reproduce this, it's hard for me to work on, but if someone who
can reproduce wants to try I'd be happy to support them.

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

[kdeconnect] [Bug 449719] KDE Connect crashes when opening a message

2022-03-04 Thread Nathan
https://bugs.kde.org/show_bug.cgi?id=449719

--- Comment #4 from Nathan <2gd4...@gmail.com> ---
Looks like no one is even reading these bug reports

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

[kdev-python] [Bug 451152] New: Custom PYTHONPATH not getting set

2022-03-04 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=451152

Bug ID: 451152
   Summary: Custom PYTHONPATH not getting set
   Product: kdev-python
   Version: 5.6.1
  Platform: Appimage
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: m...@svenbrauch.de
  Reporter: garli...@outlook.com
CC: m...@svenbrauch.de
  Target Milestone: ---

SUMMARY
***
If a custom Environment profile is created with a custom PYTHONPATH and the
environment gets used in the Launcher, the PYTHONPATH will not get set.
***


STEPS TO REPRODUCE
1. Go to Settings -> Configure KDevelop
2. Click on 'Environment'
3. Click the + (plus) button to create a new profile.
4. Name the profile 'Python_Test'
5. Add a Variable to the environment called PYTHONPATH
6. Set the value of the variable to a real custom path, for example:
/home/myname/custom/module
To specify more than one path, delimit the paths with a colon (:). For example
/home/path1:/home/path2

7. Click OK to exit the configure window
8. Click on the 'Run' menu and click 'Configure Launches'
9. Add a new launch by clicking the '+Add' button.
10. Set the Environment option to the environment we made in step 4
(Python_Test)
11. Click OK to save the Launch Configuration
12. Click the 'Run' menu -> 'Current Launch Configuration' sub-menu, and choose
the Launcher that we made in step 9.
12. Run a Python script using the Launch Configuration that was just made. The
PYTHONPATH variable will not get set.

OBSERVED RESULT
PYTHONPATH variable is not set from the Environment that is configured.

EXPECTED RESULT
PYTHONPATH=/the/path/i_chose:/second/path

SOFTWARE/OS VERSIONS
Linux: Ubuntu MATE 20.04.4 LTS

ADDITIONAL INFORMATION
It only seems to affect the AppImage version of KDevelop (v5.6.1). I tried
using the Ubuntu package distribution version of KDevelop (v5.5.0) and the
Environment variable set PYTHONPATH just fine.

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

[okular] [Bug 451149] Support opening wide images as a single page in double page mode

2022-03-04 Thread Alastor Tenebris
https://bugs.kde.org/show_bug.cgi?id=451149

Alastor Tenebris  changed:

   What|Removed |Added

 CC||livingnightmare@thelivingni
   ||ghtmare.xyz

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

[okular] [Bug 451149] New: Support opening wide images as a single page in double page mode

2022-03-04 Thread Alastor Tenebris
https://bugs.kde.org/show_bug.cgi?id=451149

Bug ID: 451149
   Summary: Support opening wide images as a single page in double
page mode
   Product: okular
   Version: 21.12.2
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: Comicbook backend
  Assignee: okular-de...@kde.org
  Reporter: livingnightm...@thelivingnightmare.xyz
  Target Milestone: ---

Created attachment 147286
  --> https://bugs.kde.org/attachment.cgi?id=147286=edit
Screenshot

SUMMARY

When reading comics/manga, sometimes the artist will create a two page spread.
When digitally distributed, works may choose to combine a two page spread as a
single image. Currently, if Okular encounters one such image in double page
mode, it as expected, displays both in double page mode leading to cases like
the attached screenshot.

STEPS TO REPRODUCE
1. Open comic with wide image
2. Enable double page mode

OBSERVED RESULT
The wide image is displayed next to the previous/next image

EXPECTED RESULT
The wide image is displayed on its own page

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 35
(available in About System)
KDE Plasma Version: 5.24.2
KDE Frameworks Version: 5.91.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION

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

[kwin] [Bug 444468] Sometimes a context menu won't go away even after it's program is closed.

2022-03-04 Thread Satyam
https://bugs.kde.org/show_bug.cgi?id=68

--- Comment #4 from Satyam  ---
(In reply to dexter from comment #3)
> Created attachment 147285 [details]
> screen as I wrote this bug

Restarting kwin is the least painful way out I've found:

killall kwin_x11 && kwin_x11 &

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

[Falkon] [Bug 450526] Page loader in tab never stops loading even if the website is completely loaded

2022-03-04 Thread IronTom
https://bugs.kde.org/show_bug.cgi?id=450526

IronTom  changed:

   What|Removed |Added

Version|unspecified |3.2.0
   Platform|Neon Packages   |Mint (Ubuntu based)

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

[plasma-systemmonitor] [Bug 451148] New: plasma-systemmonitor crashes at KSysGuard::Processes::getProcess

2022-03-04 Thread Fushan Wen
https://bugs.kde.org/show_bug.cgi?id=451148

Bug ID: 451148
   Summary: plasma-systemmonitor crashes at
KSysGuard::Processes::getProcess
   Product: plasma-systemmonitor
   Version: master
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: ksysguard-b...@kde.org
  Reporter: qydwhotm...@gmail.com
CC: ahiems...@heimr.nl, plasma-b...@kde.org
  Target Milestone: ---

SUMMARY
plasma-systemmonitor crashes after the summary interface is shown.


STEPS TO REPRODUCE
1. Open plasma-systemmonitor
2. Crash

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Application: plasma-systemmonitor (5.24.80)

Qt Version: 5.15.2
Frameworks Version: 5.92.0
Operating System: Linux 5.16.11-1-default x86_64
Windowing System: X11
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.24.80 [KCrashBackend]

-- Information about the crash:


The crash can be reproduced sometimes.

-- Backtrace:
Application: System Monitor (plasma-systemmonitor), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = 0x0}
[KCrash Handler]
#6  0x7faed403c556 in QHash::value
(akey=: 3063, this=) at /usr/include/qt5/QtCore/qhash.h:656
#7  KSysGuard::Processes::getProcess (this=0x0, pid=3063) at
/usr/src/debug/libksysguard5-5.24.80git.20220228T165743~1b36ab8c-ku.14.1.x86_64/processcore/processes.cpp:109
#8  0x7faed404c329 in KSysGuard::ProcessDataProvider::getProcess
(this=0x55fdc694f000, pid=3063) at
/usr/src/debug/libksysguard5-5.24.80git.20220228T165743~1b36ab8c-ku.14.1.x86_64/processcore/process_data_provider.cpp:44
#9  0x7faed68e0866 in operator() (__closure=) at
/usr/src/debug/libksysguard5-5.24.80git.20220228T165743~1b36ab8c-ku.14.1.x86_64/processcore/plugins/network/network.cpp:79
#10 QtPrivate::FunctorCall, QtPrivate::List<>, void,
NetworkPlugin::NetworkPlugin(QObject*, const QVariantList&):: >::call
(arg=, f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:146
#11 QtPrivate::Functor, 0>::call, void> (arg=, f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:256
#12 QtPrivate::QFunctorSlotObject, 0, QtPrivate::List<>, void>::impl(int,
QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=0x55fdc694a160, r=, a=,
ret=) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:443
#13 0x7faf2e5a8503 in QtPrivate::QSlotObjectBase::call (a=0x7fffe50704b0,
r=0x55fdc694f000, this=0x55fdc694a160) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#14 doActivate (sender=0x55fdc6949f10, signal_index=15,
argv=0x7fffe50704b0) at kernel/qobject.cpp:3886
#15 0x7faf2e5a19cf in QMetaObject::activate (sender=,
m=m@entry=0x7faf2e8456e0 ,
local_signal_index=local_signal_index@entry=6, argv=argv@entry=0x7fffe50704b0)
at kernel/qobject.cpp:3946
#16 0x7faf2e4dd34d in QProcess::readyReadStandardOutput (this=, _t1=...) at .moc/moc_qprocess.cpp:367
#17 0x7faf2e4e2add in QProcessPrivate::tryReadFromChannel
(this=0x55fdc6949f30, channel=0x55fdc694a040) at io/qprocess.cpp:1073
#18 0x7faf2e4e3015 in QProcessPrivate::_q_canReadStandardError
(this=) at io/qprocess.cpp:1092
#19 QProcess::qt_static_metacall (_o=, _c=,
_id=, _a=0x7fffe5070650) at .moc/moc_qprocess.cpp:210
#20 0x7faf2e5a8538 in doActivate (sender=0x55fdc6b012d0,
signal_index=3, argv=0x7fffe5070650) at kernel/qobject.cpp:3898
#21 0x7faf2e5a19cf in QMetaObject::activate
(sender=sender@entry=0x55fdc6b012d0, m=m@entry=0x7faf2e847ac0
,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fffe5070650)
at kernel/qobject.cpp:3946
#22 0x7faf2e5ab8df in QSocketNotifier::activated
(this=this@entry=0x55fdc6b012d0, _t1=..., _t2=, _t3=...) at
.moc/moc_qsocketnotifier.cpp:178
#23 0x7faf2e5ac0db in QSocketNotifier::event (this=0x55fdc6b012d0,
e=0x7fffe5070770) at kernel/qsocketnotifier.cpp:302
#24 0x7faf2f661a7f in QApplicationPrivate::notify_helper (this=, receiver=0x55fdc6b012d0, e=0x7fffe5070770) at
kernel/qapplication.cpp:3632
#25 0x7faf2e571e3a in QCoreApplication::notifyInternal2
(receiver=0x55fdc6b012d0, event=0x7fffe5070770) at
kernel/qcoreapplication.cpp:1064
#26 0x7faf2e5c9f3d in socketNotifierSourceDispatch
(source=source@entry=0x55fdc5515730) at kernel/qeventdispatcher_glib.cpp:107
#27 0x7faf2c966e22 in g_main_dispatch (context=0x7faf24005010) at
../glib/gmain.c:3381
#28 g_main_context_dispatch (context=0x7faf24005010) at ../glib/gmain.c:4099
#29 0x7faf2c9671b8 in g_main_context_iterate
(context=context@entry=0x7faf24005010, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4175
#30 0x7faf2c96726f in g_main_context_iteration (context=0x7faf24005010,
may_block=1) at ../glib/gmain.c:4240
#31 0x7faf2e5c9384 in QEventDispatcherGlib::processEvents
(this=0x55fdc5521e90, flags=...) at 

[kwin] [Bug 444468] Sometimes a context menu won't go away even after it's program is closed.

2022-03-04 Thread dexter
https://bugs.kde.org/show_bug.cgi?id=68

--- Comment #3 from dexter  ---
Created attachment 147285
  --> https://bugs.kde.org/attachment.cgi?id=147285=edit
screen as I wrote this bug

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

[kwin] [Bug 444468] Sometimes a context menu won't go away even after it's program is closed.

2022-03-04 Thread dexter
https://bugs.kde.org/show_bug.cgi?id=68

dexter  changed:

   What|Removed |Added

 CC||dex.m...@gmail.com

--- Comment #2 from dexter  ---
I'm seeing this now in Fedora F35 & previously, in all applications randomly
plasma version 5.24.2
frameworks 5.91
Qt 5.15.2
X11
kernel 5.16.12

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

[plasmashell] [Bug 451147] New: Crashes when returning from sleep

2022-03-04 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=451147

Bug ID: 451147
   Summary: Crashes when returning from sleep
   Product: plasmashell
   Version: 5.24.2
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: stephen.wet...@hotmail.com
CC: k...@davidedmundson.co.uk
  Target Milestone: 1.0

Application: plasmashell (5.24.2)

Qt Version: 5.15.2
Frameworks Version: 5.91.0
Operating System: Linux 5.16.11-1-default x86_64
Windowing System: X11
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.24.2 [KCrashBackend]

-- Information about the crash:
- What I was doing when the application crashed:

I have two monitors conected to a motherboard with Ryzen 5700G integrated
graphics via HDMI and DP.  Every since upgrading to KDE 5.24 KDE crashes
whenever I return to my computer after the monitors have turned off.

The crash can be reproduced every time.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = 0x0}
[KCrash Handler]
#6  QScreen::geometry (this=0x0) at kernel/qscreen.cpp:413
#7  0x55746adcdc0f in PanelView::geometryByDistance
(this=this@entry=0x55746d3c1ae0, distance=0) at
/usr/src/debug/plasma5-workspace-5.24.2-1.1.x86_64/shell/panelview.cpp:478
#8  0x55746add2d22 in PanelView::resizeEvent (this=0x55746d3c1ae0,
ev=0x7fff28d0e8b0) at
/usr/src/debug/plasma5-workspace-5.24.2-1.1.x86_64/shell/panelview.cpp:788
#9  0x7fe89ad12645 in QWindow::event (this=0x55746d3c1ae0, ev=) at kernel/qwindow.cpp:2438
#10 0x7fe89b646a7f in QApplicationPrivate::notify_helper (this=, receiver=0x55746d3c1ae0, e=0x7fff28d0e8b0) at
kernel/qapplication.cpp:3632
#11 0x7fe89a8a9e3a in QCoreApplication::notifyInternal2
(receiver=0x55746d3c1ae0, event=0x7fff28d0e8b0) at
kernel/qcoreapplication.cpp:1064
#12 0x7fe89ad07a48 in QGuiApplicationPrivate::processExposeEvent
(e=0x55746cd55e40) at kernel/qguiapplication.cpp:3247
#13 0x7fe89acdc85c in QWindowSystemInterface::sendWindowSystemEvents
(flags=flags@entry=...) at kernel/qwindowsysteminterface.cpp:1169
#14 0x7fe895d73e0a in xcbSourceDispatch
(source=source@entry=0x55746c17e0f0) at qxcbeventdispatcher.cpp:105
#15 0x7fe898c09e22 in g_main_dispatch (context=0x7fe890005010) at
../glib/gmain.c:3381
#16 g_main_context_dispatch (context=0x7fe890005010) at ../glib/gmain.c:4099
#17 0x7fe898c0a1b8 in g_main_context_iterate
(context=context@entry=0x7fe890005010, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4175
#18 0x7fe898c0a26f in g_main_context_iteration (context=0x7fe890005010,
may_block=1) at ../glib/gmain.c:4240
#19 0x7fe89a901384 in QEventDispatcherGlib::processEvents
(this=0x55746c188320, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#20 0x7fe89a8a883b in QEventLoop::exec (this=this@entry=0x7fff28d0eb20,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
#21 0x7fe89a8b0b10 in QCoreApplication::exec () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#22 0x7fe89acfa25c in QGuiApplication::exec () at
kernel/qguiapplication.cpp:1867
#23 0x7fe89b6469f5 in QApplication::exec () at kernel/qapplication.cpp:2824
#24 0x55746adb969a in main (argc=, argv=) at
/usr/src/debug/plasma5-workspace-5.24.2-1.1.x86_64/shell/main.cpp:238
[Inferior 1 (process 15539) detached]

The reporter indicates this bug may be a duplicate of or related to bug 450296.

Possible duplicates by query: bug 450296, bug 449845, bug 445362, bug 421895,
bug 421700.

Reported using DrKonqi

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

[systemsettings] [Bug 451146] New: Wacom CTE-450 not load and crash manual configuration

2022-03-04 Thread Roberto Reis
https://bugs.kde.org/show_bug.cgi?id=451146

Bug ID: 451146
   Summary: Wacom CTE-450 not load and crash manual configuration
   Product: systemsettings
   Version: 5.24.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm_tablet
  Assignee: plasma-b...@kde.org
  Reporter: roberto.santos.r...@gmail.com
CC: aleix...@kde.org
  Target Milestone: ---

SUMMARY
***
If try to install the linuxwacom driver or not, the system crash and close.
If install manual, can't save, but when click between options of kind of tablet
 the window close.
The save or save all not working and can't use the most famous tablet device on
system for work with design and photography

***


STEPS TO REPRODUCE
1. open system panel and devices > tablet >register one
2. choice the options and try to save (not realy save anything)
3. when alternate the options of touch sensor section, the software close too. 

There are two bugs

OBSERVED RESULT
close window, not save options and can't use device for work
EXPECTED RESULT
Save option with a name and minimal use the device with buttons and sense touch
/ press

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Regata 21.0.34
(available in About System)
KDE Plasma Version: 5.x.x
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

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

[plasmashell] [Bug 451141] Kickoff menu not disappearing on clicking elsewhere

2022-03-04 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=451141

Patrick Silva  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 CC||bugsefor...@gmx.com
 Resolution|--- |DUPLICATE

--- Comment #1 from Patrick Silva  ---


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

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

[plasmashell] [Bug 443774] [Wayland] Kicker is not dismissed when I click outside it while a submenu is open

2022-03-04 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=443774

Patrick Silva  changed:

   What|Removed |Added

 CC||frontle...@gmail.com

--- Comment #5 from Patrick Silva  ---
*** Bug 451141 has been marked as a duplicate of this bug. ***

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

[okular] [Bug 451059] Okular freezes for up to 10 seconds when loading a document or switching windows

2022-03-04 Thread Albert Astals Cid
https://bugs.kde.org/show_bug.cgi?id=451059

--- Comment #6 from Albert Astals Cid  ---
But if it happens just by switching virtual desktops, it has nothing to do with
dbus?

dbus is not involved in that scenario that i can see

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

[Akonadi] [Bug 435721] Select appointments from Office 365 not showing in Korganizer

2022-03-04 Thread Radovan Skolnik
https://bugs.kde.org/show_bug.cgi?id=435721

--- Comment #3 from Radovan Skolnik  ---
(In reply to gasmelt+kde from comment #0)
> SUMMARY
> Approximately one month ago I first observed that not all calendar
> appointments from my Office 365 calendar were showing up in my Korganizer.
> Appointments created by me do show up fine. Furthermore the missing
> appointments are do not show on the summary pane in Kontact either, but do
> show up in Kmail in the "Events on this day" portion.
> 
> STEPS TO REPRODUCE
> 1. Configure the Office 365 account through the wizard
> 2. Create an appointment via the web calendar on
> https://outlook.office.com/calendar/
> 3. Invite the new Office 365 account to a meeting from a different account
> 4. Accept the invite from the web calendar
> 5. Observe the differences between both events in Korganizer
> 
> OBSERVED RESULT
> - Appointments created by me in the web calendar show up in Korganizer
> - Appointments I am invited to by others do not show up in Korganizer,
> Kontact summary, but do show up in Kmail in the "Events on this day" portion
> 
> EXPECTED RESULT
> Both self-created appointments and calendar invites should show up in the
> Calendar pane in Kontact / Korganizer.
> 
> SOFTWARE/OS VERSIONS
> Windows: N/A
> macOS: N/A
> Linux/KDE Plasma: OpenSUSE Tumbleweed (kernel version 5.11.11-1-default)
> (available in About System)
> KDE Plasma Version: 5.21.3
> KDE Frameworks Version: 5.80.0
> Qt Version: 5.15.2
> 
> ADDITIONAL INFORMATION
> Deleting the account from Kontact entirely and re-registering it did not
> resolve the issue. In the meantime a new version of the KDE PIM suite has
> also been released which I hoped would solve the issue automatically, but it
> hasn't yet.

Also: the events are shown in Akonadi Console just fine. But not in calendar.

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

[Akonadi] [Bug 435721] Select appointments from Office 365 not showing in Korganizer

2022-03-04 Thread Radovan Skolnik
https://bugs.kde.org/show_bug.cgi?id=435721

Radovan Skolnik  changed:

   What|Removed |Added

 CC||rado...@skolnik.info

--- Comment #2 from Radovan Skolnik  ---
(In reply to gasmelt+kde from comment #0)
> SUMMARY
> Approximately one month ago I first observed that not all calendar
> appointments from my Office 365 calendar were showing up in my Korganizer.
> Appointments created by me do show up fine. Furthermore the missing
> appointments are do not show on the summary pane in Kontact either, but do
> show up in Kmail in the "Events on this day" portion.
> 
> STEPS TO REPRODUCE
> 1. Configure the Office 365 account through the wizard
> 2. Create an appointment via the web calendar on
> https://outlook.office.com/calendar/
> 3. Invite the new Office 365 account to a meeting from a different account
> 4. Accept the invite from the web calendar
> 5. Observe the differences between both events in Korganizer
> 
> OBSERVED RESULT
> - Appointments created by me in the web calendar show up in Korganizer
> - Appointments I am invited to by others do not show up in Korganizer,
> Kontact summary, but do show up in Kmail in the "Events on this day" portion
> 
> EXPECTED RESULT
> Both self-created appointments and calendar invites should show up in the
> Calendar pane in Kontact / Korganizer.
> 
> SOFTWARE/OS VERSIONS
> Windows: N/A
> macOS: N/A
> Linux/KDE Plasma: OpenSUSE Tumbleweed (kernel version 5.11.11-1-default)
> (available in About System)
> KDE Plasma Version: 5.21.3
> KDE Frameworks Version: 5.80.0
> Qt Version: 5.15.2
> 
> ADDITIONAL INFORMATION
> Deleting the account from Kontact entirely and re-registering it did not
> resolve the issue. In the meantime a new version of the KDE PIM suite has
> also been released which I hoped would solve the issue automatically, but it
> hasn't yet.

The same here. Kubuntu 21.10. Kontact 5.19.13 KDE 5.91.10 Seems also the
calendar is read only in Kontact/Korganizer but is writeable through DavMail.

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

[kalzium] [Bug 415736] Isotope table: Zoom to the mouse pointer position

2022-03-04 Thread Albert Astals Cid
https://bugs.kde.org/show_bug.cgi?id=415736

Albert Astals Cid  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
  Latest Commit||https://invent.kde.org/educ
   ||ation/kalzium/commit/3f3920
   ||80116c0e591dc777d5cdab0f4db
   ||5f6de6e
 Resolution|--- |FIXED

--- Comment #1 from Albert Astals Cid  ---
Git commit 3f392080116c0e591dc777d5cdab0f4db5f6de6e by Albert Astals Cid, on
behalf of Malte Jürgens.
Committed on 04/03/2022 at 23:07.
Pushed by aacid into branch 'master'.

Improve the Isotope Table

- Zoom to mouse instead of to the center
- Make the zoom slider logarithmic
- Use the actual zoom scroll delta value (Previously zooming broke on a laptop
touchpad without that)
- Make the rectangle in the top right preview more visible
- Show Isotope dialog on double click

M  +3-3src/isotopetable/isotopedialog.ui
M  +4-2src/isotopetable/isotopeguideview.cpp
M  +11   -0src/isotopetable/isotopeitem.cpp
M  +1-0src/isotopetable/isotopeitem.h
M  +3-2src/isotopetable/isotopetabledialog.cpp
M  +12   -15   src/isotopetable/isotopeview.cpp

https://invent.kde.org/education/kalzium/commit/3f392080116c0e591dc777d5cdab0f4db5f6de6e

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

[frameworks-kio] [Bug 448859] KEmailClientLaucherJob can't lauch Thunderbird with env variable in Exec

2022-03-04 Thread David Faure
https://bugs.kde.org/show_bug.cgi?id=448859

--- Comment #6 from David Faure  ---
Yes this ends up in /bin/sh. I thought any shell command was valid for an Exec
line.
Thanks for the pointer to the spec, that's instructive. Sometimes we
voluntarily support more things than the spec, but it's probably not a great
idea (creates compat problems when people test something in KDE and assume
it'll work everywhere)

I just found desktop files that say

Exec=env WINEPREFIX="/home/dfaure/.wine" wine start /ProgIDOpen giffile %f

Isn't this a solution to this problem? I.e. change step 1 to prepend "env"
before the env var?

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

[dolphin] [Bug 451145] New: Icon alignment method is inconsistent

2022-03-04 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=451145

Bug ID: 451145
   Summary: Icon alignment method is inconsistent
   Product: dolphin
   Version: 21.12.3
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: doncb...@gmail.com
CC: kfm-de...@kde.org
  Target Milestone: ---

Created attachment 147284
  --> https://bugs.kde.org/attachment.cgi?id=147284=edit
The tab icons on the right are higher than those under "Places"

SUMMARY

While making an icon theme I noticed that the way icons are aligned with text
in tabs is different from how they are aligned in the places pane. This results
in an odd effect where icons in the tabs are 'floating away'.


STEPS TO REPRODUCE
1. Open Places pane and select 16px icons
2. Open more than one tab

OBSERVED RESULT
Tab icons are higher than Places entry icons, relative to the text.

EXPECTED RESULT
The alignment of the icons with text should be consistent.

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

[frameworks-kcalendarcore] [Bug 451115] Plasmashell frequently crashes

2022-03-04 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=451115

--- Comment #4 from m.w...@web.de ---
I have to correct myself, the crashes still occur, but less less frequent
without the clock applet. The difference with the remaining crashes: Dr. Konqui
does not kick in, so may be it is a different bug.

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

[dolphin] [Bug 450813] "Dolphin" crashes when dragging a file to the top of the Places-Panel

2022-03-04 Thread snx
https://bugs.kde.org/show_bug.cgi?id=450813

snx  changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
  Latest Commit||https://invent.kde.org/fram
   ||eworks/kio/commit/386629579
   ||4d9201c4b4269e0cd5006ed01d6
   ||b8af
 Resolution|--- |FIXED

--- Comment #4 from snx  ---
Git commit 3866295794d9201c4b4269e0cd5006ed01d6b8af by snooxx .
Committed on 02/03/2022 at 17:21.
Pushed by broulik into branch 'master'.

KFilePlacesView: Fix crash when dragging over topmost section header

b5de820a78 fixed incorrect highlighting of the section header label
during drag operations over the first place of a section in clients
setting `m_dropOnPlace`, e.g. Dolphin. This was effective for all except
the topmost section header, where it would cause a crash (independent of
the state of `m_dropOnPlace`).

In `KFilePlacesViewDelegate::previousVisibleIndex` access to `model`
fails, because the `index` determined via `indexAt` of `m_dropRect` in
`KFilePlacesView::paintEvent` is invalid when dragging towards the
topmost section header label. This is because `m_dropRect.topLeft()` can
extend above the entry's `visualRect`, i.e. it covers the places items
below as well as above the separator, of which the latter does not exist
for the first entry.

By remembering the index belonging to `m_dropRect` in `m_dropIndex`
instead of reconstructing it, we can guarantee it to be valid.
Related: bug 450966

Test Plan:

No more crash when dragging places or folders over topmost section
header label in places view in `kdialog --getsaveurl` as well as
`dolphin`. Other functionality related to dragging places around
(including existing bugs) is unaffected and the behavior of the original
fix remains.

M  +7-5src/filewidgets/kfileplacesview.cpp

https://invent.kde.org/frameworks/kio/commit/3866295794d9201c4b4269e0cd5006ed01d6b8af

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

[dolphin] [Bug 450966] Dolphin crashes when dragging image from Gwenview over the details view

2022-03-04 Thread snx
https://bugs.kde.org/show_bug.cgi?id=450966

--- Comment #5 from snx  ---
Git commit fc95fed526f59b70ea93c5e81680ffd0dec05c61 by snooxx .
Committed on 03/03/2022 at 09:06.
Pushed by broulik into branch 'master'.

KFilePlacesView: Fix potential crash in `previousVisibleIndex`

The previous commit fixed a crash in
`KFilePlacesViewDelegate::previousVisibleIndex`, where access to `model`
failed due to an invalid index.

In addition to the previous commit already fixing the crash, unrelated
potential crashes in the future can be avoided by checking for an
invalid `index` in `previousVisibleIndex`. The existing logic of
`indexIsSectionHeader` is kept intact, since now an invalid `index` will
lead to comparing two empty strings, i.e. it will not be considered a
section header as required by the rest of the code.

This fix alone would already solve the crash without any side effects,
still introducing `m_dropIndex` seemed less brittle.
Related: bug 450813

Test Plan:

Functionality related to dragging places around (including existing
bugs) is unaffected.

M  +1-1src/filewidgets/kfileplacesview.cpp

https://invent.kde.org/frameworks/kio/commit/fc95fed526f59b70ea93c5e81680ffd0dec05c61

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

[dolphin] [Bug 450813] "Dolphin" crashes when dragging a file to the top of the Places-Panel

2022-03-04 Thread snx
https://bugs.kde.org/show_bug.cgi?id=450813

--- Comment #3 from snx  ---
Git commit fc95fed526f59b70ea93c5e81680ffd0dec05c61 by snooxx .
Committed on 03/03/2022 at 09:06.
Pushed by broulik into branch 'master'.

KFilePlacesView: Fix potential crash in `previousVisibleIndex`

The previous commit fixed a crash in
`KFilePlacesViewDelegate::previousVisibleIndex`, where access to `model`
failed due to an invalid index.

In addition to the previous commit already fixing the crash, unrelated
potential crashes in the future can be avoided by checking for an
invalid `index` in `previousVisibleIndex`. The existing logic of
`indexIsSectionHeader` is kept intact, since now an invalid `index` will
lead to comparing two empty strings, i.e. it will not be considered a
section header as required by the rest of the code.

This fix alone would already solve the crash without any side effects,
still introducing `m_dropIndex` seemed less brittle.
Related: bug 450966

Test Plan:

Functionality related to dragging places around (including existing
bugs) is unaffected.

M  +1-1src/filewidgets/kfileplacesview.cpp

https://invent.kde.org/frameworks/kio/commit/fc95fed526f59b70ea93c5e81680ffd0dec05c61

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

[dolphin] [Bug 450966] Dolphin crashes when dragging image from Gwenview over the details view

2022-03-04 Thread snx
https://bugs.kde.org/show_bug.cgi?id=450966

snx  changed:

   What|Removed |Added

  Latest Commit||https://invent.kde.org/fram
   ||eworks/kio/commit/386629579
   ||4d9201c4b4269e0cd5006ed01d6
   ||b8af
 Resolution|--- |FIXED
 Status|ASSIGNED|RESOLVED

--- Comment #4 from snx  ---
Git commit 3866295794d9201c4b4269e0cd5006ed01d6b8af by snooxx .
Committed on 02/03/2022 at 17:21.
Pushed by broulik into branch 'master'.

KFilePlacesView: Fix crash when dragging over topmost section header

b5de820a78 fixed incorrect highlighting of the section header label
during drag operations over the first place of a section in clients
setting `m_dropOnPlace`, e.g. Dolphin. This was effective for all except
the topmost section header, where it would cause a crash (independent of
the state of `m_dropOnPlace`).

In `KFilePlacesViewDelegate::previousVisibleIndex` access to `model`
fails, because the `index` determined via `indexAt` of `m_dropRect` in
`KFilePlacesView::paintEvent` is invalid when dragging towards the
topmost section header label. This is because `m_dropRect.topLeft()` can
extend above the entry's `visualRect`, i.e. it covers the places items
below as well as above the separator, of which the latter does not exist
for the first entry.

By remembering the index belonging to `m_dropRect` in `m_dropIndex`
instead of reconstructing it, we can guarantee it to be valid.
Related: bug 450813

Test Plan:

No more crash when dragging places or folders over topmost section
header label in places view in `kdialog --getsaveurl` as well as
`dolphin`. Other functionality related to dragging places around
(including existing bugs) is unaffected and the behavior of the original
fix remains.

M  +7-5src/filewidgets/kfileplacesview.cpp

https://invent.kde.org/frameworks/kio/commit/3866295794d9201c4b4269e0cd5006ed01d6b8af

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

[lattedock] [Bug 450986] [wayland] - new pinned launcher appears on all unique tasks

2022-03-04 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=450986

--- Comment #2 from ryu.ketsu...@outlook.com ---
(In reply to Michail Vourlakos from comment #1)
> do you stlll have that issue with master version? is it possible to test
> master version?

I just cloned from the Github repo and compiled, so I'm on master. It still
happens

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

[kwin] [Bug 450940] [Wayland] Full desktop freezes with GTK+ apps

2022-03-04 Thread Iván Ávalos
https://bugs.kde.org/show_bug.cgi?id=450940

Iván Ávalos  changed:

   What|Removed |Added

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

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

[plasmashell] [Bug 451141] Kickoff menu not disappearing on clicking elsewhere

2022-03-04 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=451141

frontle...@gmail.com changed:

   What|Removed |Added

  Flags||version_5_applied+,
   ||Wayland+, X11-

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

[frameworks-baloo] [Bug 402154] Baloo reindexes everything after every reboot

2022-03-04 Thread Lukas Ba.
https://bugs.kde.org/show_bug.cgi?id=402154

Lukas Ba.  changed:

   What|Removed |Added

 CC||k...@web.de

--- Comment #40 from Lukas Ba.  ---
My baloo index file is 32GiB large right now, more than any other folder on my
file system, and my file system is filled up by 100%, my PC crashed during an
update and doesn't boot anymore because there is no linux kernel. Thanks baloo.

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

[frameworks-solid] [Bug 451105] UI regression when mounting LUKS-encrypted disks caused by 5d2b5180fc4d1737f12cbbaba12884dbae832823

2022-03-04 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=451105

Nate Graham  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED
  Latest Commit||https://invent.kde.org/fram
   ||eworks/solid/commit/1d7cced
   ||a76bd3a1c2c4060d7c215ff6cba
   ||e64769

--- Comment #2 from Nate Graham  ---
Git commit 1d7cceda76bd3a1c2c4060d7c215ff6cbae64769 by Nate Graham.
Committed on 04/03/2022 at 18:50.
Pushed by ngraham into branch 'master'.

Revert "Don’t create a full Solid::Device to check encryption"

This reverts commit 5d2b5180fc4d1737f12cbbaba12884dbae832823.

This commit regressed mounting LUKS volumes; we will have to find a
better way.
Related: bug 398908

M  +2-3src/solid/devices/backends/udisks2/udisksstorageaccess.cpp

https://invent.kde.org/frameworks/solid/commit/1d7cceda76bd3a1c2c4060d7c215ff6cbae64769

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

[frameworks-solid] [Bug 398908] Dolphin uses up huge amounts of memory over time

2022-03-04 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=398908

--- Comment #126 from Nate Graham  ---
Git commit 1d7cceda76bd3a1c2c4060d7c215ff6cbae64769 by Nate Graham.
Committed on 04/03/2022 at 18:50.
Pushed by ngraham into branch 'master'.

Revert "Don’t create a full Solid::Device to check encryption"

This reverts commit 5d2b5180fc4d1737f12cbbaba12884dbae832823.

This commit regressed mounting LUKS volumes; we will have to find a
better way.
Related: bug 451105

M  +2-3src/solid/devices/backends/udisks2/udisksstorageaccess.cpp

https://invent.kde.org/frameworks/solid/commit/1d7cceda76bd3a1c2c4060d7c215ff6cbae64769

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

[valgrind] [Bug 451144] New: getting unhandled instruction: 0xEC51 0x0F1E ==22488== valgrind: Unrecognised instruction at address 0xcf667. ==22488== at 0xCF666: _armv7_neon_probe when running valgr

2022-03-04 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=451144

Bug ID: 451144
   Summary: getting unhandled instruction: 0xEC51 0x0F1E ==22488==
valgrind: Unrecognised instruction at address 0xcf667.
==22488==at 0xCF666: _armv7_neon_probe when
running valgrind
   Product: valgrind
   Version: 3.18.1
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: memcheck
  Assignee: jsew...@acm.org
  Reporter: mark.huber...@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
***


STEPS TO REPRODUCE
1. I crosscompiled a C program with this compiler
https://developer.arm.com/-/media/Files/downloads/gnu-a/8.3-2019.03/binrel/gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabihf.tar.xz?revision=e09a1c45-0ed3-4a8e-b06b-db3978fd8d56=en=93EDB8B3A812B893373B490B90BBB28FD2E3
on my Ubuntu machine 20.04. 
2. I then copied the program onto a Beaglebone black machine where I run the
program. details on the BBB: 
$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:Debian GNU/Linux 10 (buster)
Release:10
Codename:   buster

$ uname -a
Linux my-hostname 4.19.94-ti-r42 #1buster SMP PREEMPT Tue Mar 31 19:38:29 UTC
2020 armv7l GNU/Linux

3. I run valgrind like so: valgrind ./myprog

OBSERVED RESULT

unhandled instruction: 0xEC51 0x0F1E ==22488== valgrind: Unrecognised
instruction at address 0xcf667. ==22488==at 0xCF666: _armv7_neon_probe


EXPECTED RESULT

full valgrind report 


SOFTWARE/OS VERSIONS
my host os (where I compile the project): 

$ uname -a
Linux ubuntu 5.13.0-30-generic #33~20.04.1-Ubuntu SMP Mon Feb 7 14:25:10 UTC
2022 x86_64 x86_64 x86_64 GNU/Linux

$  lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04.3 LTS
Release:20.04
Codename:   focal

The Beaglebone Black (where I run the valgrind and the program): 

$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:Debian GNU/Linux 10 (buster)
Release:10
Codename:   buster

$ uname -a
Linux my-hostname 4.19.94-ti-r42 #1buster SMP PREEMPT Tue Mar 31 19:38:29 UTC
2020 armv7l GNU/Linux

ADDITIONAL INFORMATION
I did the same steps with gdb as in this bug report
https://bugzilla.redhat.com/show_bug.cgi?id=1495320#c2 and got to the exact
same conclusions

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

[dolphin] [Bug 450318] Right click context menu on "Places" does not offer to "lock" panel again

2022-03-04 Thread postix
https://bugs.kde.org/show_bug.cgi?id=450318

postix  changed:

   What|Removed |Added

  Latest Commit||https://invent.kde.org/syst
   ||em/dolphin/-/commit/1c5b6d4
   ||d1042877863801e3c0b683e8a9c
   ||41be18
 CC||n...@kde.org

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

[dolphin] [Bug 450318] Right click context menu on "Places" does not offer to "lock" panel again

2022-03-04 Thread postix
https://bugs.kde.org/show_bug.cgi?id=450318

--- Comment #2 from postix  ---
(In reply to Kai Uwe Broulik from comment #1)
> Fixed by
> https://invent.kde.org/system/dolphin/-/commit/
> 1c5b6d4d1042877863801e3c0b683e8a9c41be18

Thanks Kai! Fixed in 21.12.3?

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

[lattedock] [Bug 451093] Some fullscreen application makes latte-dock crash/non responsive

2022-03-04 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=451093

--- Comment #7 from szilprogramm...@gmail.com ---
A. lspci | grep VGA ->  VGA compatible controller: Intel Corporation HD
Graphics 630 (rev 04)
B. AUR (latte-dock-git)
C.  According to pacman: r5865.f1472db6-1

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

[kio-extras] [Bug 447507] No thumbnails for .kra in dolphin

2022-03-04 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=447507

--- Comment #4 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/network/kio-extras/-/merge_requests/144

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

[kdevelop] [Bug 451143] New: Kdevelop flatpak package: libclang.so.12 missing, no syntax highlighting

2022-03-04 Thread Alexander
https://bugs.kde.org/show_bug.cgi?id=451143

Bug ID: 451143
   Summary: Kdevelop flatpak package: libclang.so.12 missing, no
syntax highlighting
   Product: kdevelop
   Version: 5.7.211203
  Platform: Flatpak
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Language Support: CPP (Clang-based)
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: monk_of_darkn...@mail.ru
  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
***
Hello. I'm using latest flatpak kdevelop package on kubuntu 20.04 with latest
updates. I'm having problem with absent syntax highlighting on a C++ project.
General code tools like find uses and refactoring are also unavailable.
Background parser progress bar shows, moves to 100% and fades.

If you launch kdevelop flatpak package from terminal you will see an error
like:
kdevplatform.shell: Can't load plugin "kdevclangsupport" because a factory to
load the plugin could not be obtained: Cannot load library
/app/lib/plugins/kdevplatform/35/kdevclangsupport.so: (libclang.so.12: cannot
open shared object file: No such file or directory)

Juding by locate (updatedb performed beforehand), libclang.so.12 is nowhere to
be found in flatpak directories. I've manually installed llvm12 through apt but
it does not change anything.

Thanks.

STEPS TO REPRODUCE
1. Install kdevelop from flatpak on Kubuntu 20.04 or 21.10
2. Open any c++ project
3. Syntax highlighting and code warnings, errors and other things (find uses,
refactor) are not available. 

OBSERVED RESULT
libclang.so.12 is not present, kdevelop fails to load kdevclangsupport plugin
and fails to provide syntax highlighting and other features.

EXPECTED RESULT
libclang.so.12 should probably be installed with kdevelop or in its
dependencies.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Kubuntu 20.04, Plasma 5.18.8
(available in About System)
KDE Plasma Version: 5.18.8
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8

ADDITIONAL INFORMATION

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

[konsole] [Bug 451142] New: Removing an Umlaut (ä,ö,ü) enables one to remove parts of the shell prompt

2022-03-04 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=451142

Bug ID: 451142
   Summary: Removing an Umlaut (ä,ö,ü) enables one to remove parts
of the shell prompt
   Product: konsole
   Version: 21.12.2
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: keyboard
  Assignee: konsole-de...@kde.org
  Reporter: henri.innd...@tutanota.com
  Target Milestone: ---

Created attachment 147283
  --> https://bugs.kde.org/attachment.cgi?id=147283=edit
Example result

SUMMARY
After entering a text containing an Umlaut (ä,ö,ü), one is able to delete one
more character per Umlaut than should be allowed, i. e. one is able to delete
part of the shell prompt ([user@pc ~]$ ).


STEPS TO REPRODUCE
1. Enter several Umlaute.
2. Hit backspace until you can't delete anymore characters.

OBSERVED RESULT
E. g. for 4 Umlaute, one can delete the "~]$" from the shell prompt.

EXPECTED RESULT
Not being able to remove more characters than I typed (I assume this has
something to do with the encoding of an Umlaut needing two Unicode characters).

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Manjaro Linux (4.19.230-1-MANJARO) (64-bit)
(available in About System)
KDE Plasma Version: 5.24.2
KDE Frameworks Version: 5.91.0
Qt Version: 5.15.2
Graphics Platform: X11

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

[plasma-nm] [Bug 451139] Since fixed bug 399973, Network manager does not automatically reconnect to known network after reset

2022-03-04 Thread NIk
https://bugs.kde.org/show_bug.cgi?id=451139

--- Comment #1 from NIk  ---
More info: In the moment of the reset of the connection, it seems that another
connection is being created by NM (enp3s0), whereas my normal connection is
"Kabelgebunden" (meaning wired).
Upon finished restart of the router (or if you put the network plug back in),
it stays connected to this new non functional enp3s0 thing, whatever that is,
saying it has "limited connectivity". The actually working wired connection
gets ignored. 
If I connect manually to said wired connection, the enp3s0 thing disappears.

This is all very weird, here is a screenshot of mentioned state:
https://imgur.com/a/W9bvObB

Lets not needlessly fiddle around with all NM/network-related things, its too
important :)

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

[lattedock] [Bug 451093] Some fullscreen application makes latte-dock crash/non responsive

2022-03-04 Thread Michail Vourlakos
https://bugs.kde.org/show_bug.cgi?id=451093

--- Comment #6 from Michail Vourlakos  ---
(In reply to szilprogramming from comment #5)
> Unfournately I can't find an open source application that produce this
> issue, but these steps my help:
> 0. Make sure that the compositor is running
> 1. Check the "Allow applications to block compositing" in System Settings -
> Compositor
> 2. Run "qdbus org.kde.KWin /Compositor suspend" or press Alt+Shift+F12
> (2.5. Sometimes you have to click once in the latte-dock panel)
> 3. It's completely freezes
> (Running qdbus org.kde.KWin /Compositor resume or pressing Alt-Shift-F12
> doesn't help)
> 
> Fix:
> 1. Kill the latte-dock process
> 2. Resume the compositor
> 3. Run latte-dock

Nope, this is not the case in my system? I switch between no compositing and
compositing mode regularly in my system with no issues.

A. What is your graphics driver?
B. How did you install Latte?
C. What is your Latte version?

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

[plasmashell] [Bug 451141] New: Kickoff menu not disappearing on clicking elsewhere

2022-03-04 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=451141

Bug ID: 451141
   Summary: Kickoff menu not disappearing on clicking elsewhere
   Product: plasmashell
   Version: 5.24.2
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Application Menu (Kicker)
  Assignee: plasma-b...@kde.org
  Reporter: frontle...@gmail.com
  Target Milestone: 1.0

SUMMARY
***
When I click on Kicker, it pops up the application groups (as expected). At
this stage, if I click on any place outside Kicker, it disappears (again as
expected). If I pause my mouse pointer on any one of the groups, it opens the
list of installed applications (as expected) and at this stage, if I quickly
move my pointer and click on any place outside Kicker, it disappears (again as
expected).
But if I open the list of installed applications, point my pointer on any one
of the installed applications but do not click on it (or do not move my pointer
over and out of the list of applications quick enough) and then move the
pointer away from Kicker and click on any place outside, the Kicker menu stays
put and does not disappear. It stays put wherever or on whichever window I
click on. If I bring the pointer back to Kicker on a different application
group then the list of installed applications disappears and reveals a new list
of installed applications. If at this stage I quickly move my pointer and click
on any place outside Kicker then the list of applications disappear but Kicker
itself stays put and does not disappear until I click on the Kicker icon on the
panel. 

The observed behaviour happens only for Kicker but not for Kickoff. Also, the
problem happens in Wayland session but not in x11.
***


STEPS TO REPRODUCE
1. Click on Kicker and open the menu.
2. Move pointer to any program group and open the list of (installed) programs. 
3. Hover on the entry for any application for a second but DO NOT click on it.
4. Click anywhere outside the menu say on another windows or the desktop.
OBSERVED RESULT
Kicker menu stays put and does not disappear.

EXPECTED RESULT
Kicker should disappear.

SOFTWARE/OS VERSIONS
Windows: NA
macOS: NA
Linux/KDE Plasma: Arch Linux Kernel: 5.16-arch-2 (64-bit)
(available in About System)
KDE Plasma Version: 5.24.2
KDE Frameworks Version: 5.91.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
Graphics Platform: Wayland
NB: The problem happens in Wayland session but not in x11.

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

[print-manager] [Bug 426652] Orientation option is set to 0 and causes error message in Status Message queue for CUPS

2022-03-04 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=426652

virusma...@gmail.com changed:

   What|Removed |Added

 CC||virusma...@gmail.com

--- Comment #1 from virusma...@gmail.com ---
Had the same problem with HP LaserJet Enterprise 700 color MFP M775 today.
Had to set orientation to Landscape and back to Portrait. Was printing from
Okular.

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

[krfb] [Bug 451140] krfb fails to start from menu with error: Unknown option 'icon'

2022-03-04 Thread Rex Dieter
https://bugs.kde.org/show_bug.cgi?id=451140

Rex Dieter  changed:

   What|Removed |Added

Summary|krfb fails to start from|krfb fails to start from
   |menu with eror: Unknown |menu with error: Unknown
   |option 'icon'   |option 'icon'

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

[krfb] [Bug 451140] New: krfb fails to start from menu with eror: Unknown option 'icon'

2022-03-04 Thread Rex Dieter
https://bugs.kde.org/show_bug.cgi?id=451140

Bug ID: 451140
   Summary: krfb fails to start from menu with eror: Unknown
option 'icon'
   Product: krfb
   Version: 21.12.2
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: grundleb...@googlemail.com
  Reporter: rdie...@gmail.com
  Target Milestone: ---

Fails to start via menu, journal reports error:
krfb: Unknown option 'icon'.

I'm guessing due to use of %i in org.kde.krfb.desktop:
Exec=krfb -qwindowtitle %c %i

Dropping %i makes startup work correctly

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

[krfb] [Bug 413476] Wayland/Pipewire segfault on connection

2022-03-04 Thread Rex Dieter
https://bugs.kde.org/show_bug.cgi?id=413476

Rex Dieter  changed:

   What|Removed |Added

 CC||rdie...@gmail.com

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

[dolphin] [Bug 450318] Right click context menu on "Places" does not offer to "lock" panel again

2022-03-04 Thread Kai Uwe Broulik
https://bugs.kde.org/show_bug.cgi?id=450318

Kai Uwe Broulik  changed:

   What|Removed |Added

 CC||k...@privat.broulik.de
 Status|REPORTED|RESOLVED
 Resolution|--- |FIXED

--- Comment #1 from Kai Uwe Broulik  ---
Fixed by
https://invent.kde.org/system/dolphin/-/commit/1c5b6d4d1042877863801e3c0b683e8a9c41be18

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

[krfb] [Bug 433890] can not share desktop under wayland, only got a black screen

2022-03-04 Thread Rex Dieter
https://bugs.kde.org/show_bug.cgi?id=433890

Rex Dieter  changed:

   What|Removed |Added

 CC||rdie...@gmail.com

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

[krfb] [Bug 451086] Cannot connect to KRFB desktop running on Fedora 36 KDE.

2022-03-04 Thread Rex Dieter
https://bugs.kde.org/show_bug.cgi?id=451086

Rex Dieter  changed:

   What|Removed |Added

 CC||rdie...@gmail.com

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

[Breeze] [Bug 421677] Scrolling on tab bar also scrolls page content, if it's scrollable

2022-03-04 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=421677

Nate Graham  changed:

   What|Removed |Added

URL||https://bugreports.qt.io/br
   ||owse/QTBUG-101467

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

[plasma-nm] [Bug 451139] New: Since fixed bug 399973, Network manager does not automatically reconnect to known network after reset

2022-03-04 Thread NIk
https://bugs.kde.org/show_bug.cgi?id=451139

Bug ID: 451139
   Summary: Since fixed bug 399973, Network manager does not
automatically reconnect to known network after reset
   Product: plasma-nm
   Version: 5.24.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jgrul...@redhat.com
  Reporter: nik.kaise...@googlemail.com
  Target Milestone: ---

Created attachment 147282
  --> https://bugs.kde.org/attachment.cgi?id=147282=edit
NM applet showing wrong "last connected" time

SUMMARY
Since 5.24.2 including this commit
https://invent.kde.org/plasma/plasma-nm/-/commit/622f53da6184dc90d5834a9e75fb1cb1c3af5986,
Network Manager does not reconnect to my known, wired network connection, if it
is being reset from the outside (for example a router reset). 
It did automatically reconnect in 5.24.1 and .0. The connection is set to
"connect autmatically". I do not have any other connections saved/available in
NM. 


STEPS TO REPRODUCE
1. Connect to (wired) network, for example a router
2. Cut the power on the router and plug it back in
3. After router has booted up, observe NM is not reconnecting automatically

OBSERVED RESULT
NM is not reconnecting automatically

EXPECTED RESULT
NM should reconnect automatically, if the network is saved and known


Operating System: openSUSE Tumbleweed 20220302
KDE Plasma Version: 5.24.2
KDE Frameworks Version: 5.91.0
Qt Version: 5.15.2
Kernel Version: 5.16.11-1-default (64-bit)
Graphics Platform: X11
Processors: 12 × 11th Gen Intel® Core™ i5-11600K @ 3.90GHz
Memory: 31.2 GiB of RAM
Graphics Processor: Mesa Intel® Graphics

ADDITIONAL INFORMATION
Included picture shows the state after the router has been restarted and is
booted up. NM shows my connection as "used last two hours ago" which isnt true,
its rather 2 minutes. Maybe this is part of the bug. If I click connect it does
connect normally.

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

[Breeze] [Bug 443437] Make it optional to deepen the shadow for the active window

2022-03-04 Thread Jan Blackquill
https://bugs.kde.org/show_bug.cgi?id=443437

Jan Blackquill  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |INTENTIONAL
 CC||uhh...@gmail.com

--- Comment #9 from Jan Blackquill  ---
Consensus from our designers seems to be that we don't want this as an option,
so I'm marking as RESOLVED INTENTIONAL for now.

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

[Breeze] [Bug 418904] Offer a user-adjustable padding/margin setting for widgets that have internal padding

2022-03-04 Thread Jan Blackquill
https://bugs.kde.org/show_bug.cgi?id=418904

Jan Blackquill  changed:

   What|Removed |Added

 CC||uhh...@gmail.com
 Resolution|--- |INTENTIONAL
 Status|CONFIRMED   |RESOLVED

--- Comment #6 from Jan Blackquill  ---
Consensus from our designers seems to be that we don't want this as an option,
so I'm marking as RESOLVED INTENTIONAL for now.

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

[Breeze] [Bug 421677] Scrolling on tab bar also scrolls page content, if it's scrollable

2022-03-04 Thread Jan Blackquill
https://bugs.kde.org/show_bug.cgi?id=421677

Jan Blackquill  changed:

   What|Removed |Added

 Resolution|--- |UPSTREAM
 CC||uhh...@gmail.com
 Status|CONFIRMED   |RESOLVED

--- Comment #2 from Jan Blackquill  ---
This is an upstream Qt bug; see https://bugreports.qt.io/browse/QTBUG-101467.

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

[lattedock] [Bug 451093] Some fullscreen application makes latte-dock crash/non responsive

2022-03-04 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=451093

--- Comment #5 from szilprogramm...@gmail.com ---
Unfournately I can't find an open source application that produce this issue,
but these steps my help:
0. Make sure that the compositor is running
1. Check the "Allow applications to block compositing" in System Settings -
Compositor
2. Run "qdbus org.kde.KWin /Compositor suspend" or press Alt+Shift+F12
(2.5. Sometimes you have to click once in the latte-dock panel)
3. It's completely freezes
(Running qdbus org.kde.KWin /Compositor resume or pressing Alt-Shift-F12
doesn't help)

Fix:
1. Kill the latte-dock process
2. Resume the compositor
3. Run latte-dock

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

[dolphin] [Bug 450966] Dolphin crashes when dragging image from Gwenview over the details view

2022-03-04 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=450966

--- Comment #3 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/frameworks/kio/-/merge_requests/779

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

[dolphin] [Bug 450966] Dolphin crashes when dragging image from Gwenview over the details view

2022-03-04 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=450966

Bug Janitor Service  changed:

   What|Removed |Added

 Status|REPORTED|ASSIGNED
 Ever confirmed|0   |1

--- Comment #2 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/frameworks/kio/-/merge_requests/779

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

[dolphin] [Bug 450813] "Dolphin" crashes when dragging a file to the top of the Places-Panel

2022-03-04 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=450813

--- Comment #2 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/frameworks/kio/-/merge_requests/779

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

[dolphin] [Bug 450813] "Dolphin" crashes when dragging a file to the top of the Places-Panel

2022-03-04 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=450813

Bug Janitor Service  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|ASSIGNED

--- Comment #1 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/frameworks/kio/-/merge_requests/779

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

[tellico] [Bug 451138] New: Supporting importing Data Crow XML

2022-03-04 Thread Robby Stephenson
https://bugs.kde.org/show_bug.cgi?id=451138

Bug ID: 451138
   Summary: Supporting importing Data Crow XML
   Product: tellico
   Version: unspecified
  Platform: Other
OS: Other
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: ro...@periapsis.org
  Reporter: ro...@periapsis.org
  Target Milestone: ---

Data Crow is able to export into an XML format. GCstar currently supports
importing that format. 
http://forums.gcstar.org/viewtopic.php?id=18359
https://gitlab.com/Kerenoc/GCstar/-/blob/Test/gcstar/lib/gcstar/GCImport/GCImportDataCrow.pm

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

[Discover] [Bug 426270] Error transferrring https://odrs.gnome.org/1.0/reviews/api/fetch - server replied: BAD REQUEST

2022-03-04 Thread B Negri
https://bugs.kde.org/show_bug.cgi?id=426270

--- Comment #7 from B Negri  ---
Created attachment 147281
  --> https://bugs.kde.org/attachment.cgi?id=147281=edit
Not being able to install because of the bug

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

[kwin] [Bug 451136] wobbly windows bug

2022-03-04 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=451136

barsnet...@gmail.com changed:

   What|Removed |Added

Summary|effects bug |wobbly windows bug

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

[kwin] [Bug 451136] effects bug

2022-03-04 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=451136

--- Comment #2 from barsnet...@gmail.com ---
Created attachment 147280
  --> https://bugs.kde.org/attachment.cgi?id=147280=edit
wobbly windows bug

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

[kwin] [Bug 451136] effects bug

2022-03-04 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=451136

--- Comment #1 from barsnet...@gmail.com ---
Created attachment 147279
  --> https://bugs.kde.org/attachment.cgi?id=147279=edit
wobbly windows bug

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

[Breeze] [Bug 442628] Breeze Dark: menubar and toolbar background not switching colours for inactive/active windows

2022-03-04 Thread Oliver Freyermuth
https://bugs.kde.org/show_bug.cgi?id=442628

--- Comment #14 from Oliver Freyermuth  ---
Wow, thanks for catching this! This made my day, or maybe even my week :-). I
can confirm disabling side borders (or all borders) fixes this issue, I was
unaware enabling the tiny borders (which I did many Plasma versions ago) would
have such an effect 
Now my only remaining issue with the new design is #435905, but that's a
different bug. 

Thanks!

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

[frameworks-networkmanager-qt] [Bug 451137] connection.interface-name: 'New wireguard connection': interface name contains an invalid character

2022-03-04 Thread Artyom
https://bugs.kde.org/show_bug.cgi?id=451137

--- Comment #1 from Artyom  ---
Created attachment 147278
  --> https://bugs.kde.org/attachment.cgi?id=147278=edit
default name

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

[frameworks-networkmanager-qt] [Bug 451137] New: connection.interface-name: 'New wireguard connection': interface name contains an invalid character

2022-03-04 Thread Artyom
https://bugs.kde.org/show_bug.cgi?id=451137

Bug ID: 451137
   Summary: connection.interface-name: 'New wireguard connection':
interface name contains an invalid character
   Product: frameworks-networkmanager-qt
   Version: 5.91.0
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jgrul...@redhat.com
  Reporter: bugs.kde@rop.cx
CC: lamar...@kde.org, lukas.ti...@merlin.cz
  Target Milestone: ---

Created attachment 147277
  --> https://bugs.kde.org/attachment.cgi?id=147277=edit
the error

SUMMARY
connection.interface-name: 'New wireguard connection': interface name contains
an invalid character


STEPS TO REPRODUCE
1. create wireguard connection, do not change the name (default is "New
wireguard connection")
2. save

OBSERVED RESULT
connection is not added

EXPECTED RESULT
connection is not added

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: cpe:/o:opensuse:tumbleweed:20220302
KDE Plasma Version: 5.24.2
KDE Frameworks Version: 5.91
Qt Version: 5.15.2

ADDITIONAL INFORMATION
do not create an interface with the same name?

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

[kwin] [Bug 451136] New: effects bug

2022-03-04 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=451136

Bug ID: 451136
   Summary: effects bug
   Product: kwin
   Version: 5.24.2
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: effects-various
  Assignee: kwin-bugs-n...@kde.org
  Reporter: barsnet...@gmail.com
  Target Milestone: ---

STEPS TO REPRODUCE
1. Open systemsettings
2. Go to effects
3. enable wobbly windows
4. go to wobbly windows settings and enable advanced mode
5. set settings:
stiffness - 50
drag - 100
move factor - 25
6. move window

RESULT:
wobbly windows bug (video)

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: arch/debian based, ubuntu based, arch based (all)
KDE Plasma Version: 5.24.2/*
KDE Frameworks Version: 5.91.0/*
Qt Version: 5.12.2/*
Session: X11
LoginManager: sddm/*
gpu: amd/*

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

[kwin] [Bug 311919] Aurorae doesn't honor text shadow and halo settings

2022-03-04 Thread Chaz Rittich
https://bugs.kde.org/show_bug.cgi?id=311919

Chaz Rittich  changed:

   What|Removed |Added

Version|4.9.4   |5.24.2
   Platform|Ubuntu Packages |Archlinux Packages
 CC||chaz9...@gmail.com

--- Comment #11 from Chaz Rittich  ---
Kwin's text halo effect is broken and doesn't render even when enabled in
themerc.
Here's what the effect is supposed to look like
https://store.kde.org/p/1002683/ and in modern releases the text halo doesn't
appear and instead you just get text on a transparent background. This creates
problems with legacy theme or even maybe some newer themes that wish to have a
transparent titlebar and not sacrifice on title quality. This bug is
reproducible by the following the instructions in the above posts.

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

[Breeze] [Bug 442628] Breeze Dark: menubar and toolbar background not switching colours for inactive/active windows

2022-03-04 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=442628

Nate Graham  changed:

   What|Removed |Added

 Resolution|--- |INTENTIONAL
 Status|REPORTED|RESOLVED

--- Comment #13 from Nate Graham  ---
Indeed.

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

[Breeze] [Bug 442628] Breeze Dark: menubar and toolbar background not switching colours for inactive/active windows

2022-03-04 Thread Jan Blackquill
https://bugs.kde.org/show_bug.cgi?id=442628

Jan Blackquill  changed:

   What|Removed |Added

 CC||uhh...@gmail.com

--- Comment #12 from Jan Blackquill  ---
It looks like you have the side window borders enabled; the new style only
applies when the borders option in the Window Decorations KCM is set to "No
Borders" or "No Side Borders"

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

[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade

2022-03-04 Thread Zach White
https://bugs.kde.org/show_bug.cgi?id=414559

--- Comment #23 from Zach White  ---
I tried to dig into this problem a little bit and here is what I was able to
observe. I still have not figured out how I can either fix or workaround the
issue.

The first surprising observation is that `sudo udevadm monitor` does not
register any output at all at times I would expect it to. For example, there is
no output when I run `udevadm trigger -s input` but there is output when I run
`sudo udevadm trigger -s input`. This is what I see running that:

https://gist.github.com/skullydazed/6a0703258dc9f0a231cebc0395174228

When I unplug and plugin my mouse here is what udevadm shows:

https://gist.github.com/skullydazed/855393941da35627e15870b313224b7d

Now, here's where things get interesting. I grabbed a second mouse and plugged
it in (a Logitech TrackMan Marble.) When I did this my first mouse (Logitech MX
Ergo) kept the correct settings but the new mouse had incorrect settings. More
interestingly, when I went into System Settings -> Input Devices -> Mouse and
changed a setting both mice adopted the correct settings.

Steps to reproduce with any 2 mice:

1. Have first mouse plugged in, second mouse unplugged.
2. Go to System Settings -> Input Devices -> Mouse, check "Invert scroll
direction", click "Apply".
3. Verify that moving the scroll wheel away from you scrolls a window down.
4. Plug in second mouse
5. Observe that first mouse scrolls down when the wheel is scrolled away from
you while second mouse scrolls down when the wheel is scrolled towards you.
6. In the mouse settings window check (or uncheck) "Press left and right
buttons together", then click Apply.
7. Observe that both mice scroll identically

I believe this bug is classified incorrectly. Based on my observations it seems
that the problem is that USB plug events are configuring devices with the
default settings rather than the user's settings.

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

[lattedock] [Bug 451093] Some fullscreen application makes latte-dock crash/non responsive

2022-03-04 Thread Michail Vourlakos
https://bugs.kde.org/show_bug.cgi?id=451093

Michail Vourlakos  changed:

   What|Removed |Added

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

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

[lattedock] [Bug 451093] Some fullscreen application makes latte-dock crash/non responsive

2022-03-04 Thread Michail Vourlakos
https://bugs.kde.org/show_bug.cgi?id=451093

--- Comment #4 from Michail Vourlakos  ---
(In reply to szilprogramming from comment #3)
> 1. Yes, I had issues from other applications, but I can't remember any open
> source.
> 2. Disabling compositor effected latte-dock the same way as described
> before, so I disabled "Allow applications to block compositing" thats solved
> the issue. I experimented further more and for me it's seems like disabling
> compositor while latte-dock is active breaks it.
> 
> In conclusion applications blocking compositor makes Latte non responsive

Can you provide me a well known open source app/game in order to install in my
system to test things? There isba big chance of course that this is Qt bug, not
Latte

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

[konsole] [Bug 451135] New: Background flickers occasionally

2022-03-04 Thread twoexem
https://bugs.kde.org/show_bug.cgi?id=451135

Bug ID: 451135
   Summary: Background flickers occasionally
   Product: konsole
   Version: 21.12.3
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: fridolin@web.de
  Target Milestone: ---

SUMMARY
***
The blurred transparent background flickers occasionally when another Window is
behind it.
Video of the bug: https://twoexem.com/bug.mp4
***


STEPS TO REPRODUCE
1. Open Konsole
2. Enable background transparency
3. With luck, the background will start flickering

OBSERVED RESULT
Background flicker

EXPECTED RESULT
No background flicker

SOFTWARE/OS VERSIONS
Linux: Arch Linux
KDE Plasma Version: 5.24.2
KDE Frameworks Version: 5.91.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
Graphics platform: X11

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

[lattedock] [Bug 451093] Some fullscreen application makes latte-dock crash/non responsive

2022-03-04 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=451093

--- Comment #3 from szilprogramm...@gmail.com ---
1. Yes, I had issues from other applications, but I can't remember any open
source.
2. Disabling compositor effected latte-dock the same way as described before,
so I disabled "Allow applications to block compositing" thats solved the issue.
I experimented further more and for me it's seems like disabling compositor
while latte-dock is active breaks it.

In conclusion applications blocking compositor makes Latte non responsive

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

  1   2   3   >