[plasma-systemmonitor] [Bug 461361] GPU Information for Dedicated NVIDIA GPU not showing on widget or plasma system monitor application.

[Neil]

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

Neil  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 CC||cont...@neillambert.com
 Resolution|FIXED   |---

--- Comment #7 from Neil  ---
this issue seems to be back with latest nvidia driver 535.54.03

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

[plasma-systemmonitor] [Bug 429159] Horizontal Bars: No scaling

[Neil]

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

Neil  changed:

   What|Removed |Added

 CC||cont...@neillambert.com
 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

--- Comment #6 from Neil  ---
Google has brought me here... I see the same and can confirm. My sensors have
high and critical but no max, so I understand the conundrum. 

"We are working on some new sensor setup that should fix this for certain
sensors"

For what it's worth *pie chart* allows for a manual data range. Could be a
great addition to horizontal bars: let the user fix it!

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

[kwin] [Bug 429319] New: Task switcher with options "stacking order" + "one window per app" not behaving nicely

[Neil]

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

Bug ID: 429319
   Summary: Task switcher with options "stacking order" + "one
window per app" not behaving nicely
   Product: kwin
   Version: 5.20.3
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: cont...@neillambert.com
  Target Milestone: ---

SUMMARY

There was something unexpected going on when I was aiming for a certain result
from the task switcher.

"If Only one window per application is selected then only the last used
instance of an application is contained in the list. Switching to other
instances is possible only via the panel then."
https://docs.kde.org/trunk5/en/kde-workspace/kcontrol/kwintabbox/index.html

When sort order is "Recently used" this works correctly

When sort order is "Stacking order" this does not work as expected

When sort order is "Stacking order": a PREVIOUSLY used instance of the
application is contained in the list.

Why this matters:
- Alt+Tab to walk through applications (as if groups)
- Alt+` to walk through instances of the current application

Alt+Tab should then not display a different window of the current application,
only Alt+` should.

STEPS TO REPRODUCE
1. Under System Settings > Window Management > Task Switcher
2. Sort order: choose "stacking order"
3. Check "only one window per application"
4. Open 2 chrome windows
5. Open 2 terminal windows
6. Open 2 firefox windows
7. Make sure each window has something recognizable 

OBSERVED RESULT
The Alt+Tab list shows all 3 applications, but not the last used.

What is displayed is the bottom of the stack.

And, when Alt+` is used, the next time you press Alt+Tab you see the other
window of the current application (which should definitely not happen).

EXPECTED RESULT
With "one window per application" Alt-Tab should never switch to another window
of the same application.
Alt-Tab should just cycle the top of the stack
Alt-` should bring stuff up from underneath

SOFTWARE/OS VERSIONS
Linux: Arch 5.9.8-zen1-1-zen
KDE Plasma Version: 5.20.3
KDE Frameworks Version: 5.75.0
Qt Version: 5.15.1

ADDITIONAL INFORMATION

I hope this was clear enough :-)

I understand why this is happening, but "stacking order" + "one window per app"
together should work differently i.e.: it should work like in the docs: "If
Only one window per application is selected then only the last used instance of
an application is contained in the list."

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

[kmymoney] [Bug 473223] New: Data lost on kmymoney-master-2001-macos-clang-x86_64.dmg upgrade

[Neil]

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

Bug ID: 473223
   Summary: Data lost on
kmymoney-master-2001-macos-clang-x86_64.dmg upgrade
Classification: Applications
   Product: kmymoney
   Version: unspecified
  Platform: macOS (DMG)
OS: macOS
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: kmymoney-de...@kde.org
  Reporter: nral...@pm.me
  Target Milestone: ---

SUMMARY
***
Using kmymoney-5.1-1802-macos-clang-x86_64.dmg - Can open .kmy files created on
Linux (kmymoney v5.0.8 ) with 21720 transactions. Problem with unusable Home
screen. Googled solution suggested that nightly version solved the Home
problem.
Installed kmymoney-master-2001-macos-clang-x86_64.dmg. Home screen works but
Data newer than 2016 was missing. File Information shows only 14811
transactions






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. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


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

ADDITIONAL INFORMATION

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

[kmymoney] [Bug 473223] Data lost on kmymoney-master-2001-macos-clang-x86_64.dmg upgrade

[Neil]

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

--- Comment #2 from Neil  ---
(In reply to Thomas Baumgart from comment #1)
> Could be related to the content of your data. What does KMyMoney print to
> the console when started from the command line? Anything suspicious? What is
> the output of the following command run on the command line (replace
> "your-data-file-name.kmy" with your actual filename:
> 
> zcat your-data-file-name.kmy | grep 'TRANSACTION>' | wc -l
> 
> It should be the number of transactions plus the number of schedules shown
> in the File information dialog.

Reply from Neil Ralph:
1) Not sure if I should be using 'reply' or 'Add Comment'
2) could not get zcat to complete:
neilralph@Neils-MBP ~ % zcat 9gwengood4.kmy | grep 'TRANSACTION>' | wc -l
zcat: can't stat: 9gwengood4.kmy (9gwengood4.kmy.Z): No such file or directory
   0
neilralph@Neils-MBP ~ % pwd
/Users/neilralph
neilralph@Neils-MBP ~ % ls
9gwengood4.kmy  Library
ApplicationsMovies
Applications (Parallels)Music
BBDownloads Nextcloud
Desktop Parallels
Documents   Pictures
Downloads   Public

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

[kmymoney] [Bug 473223] Data lost on kmymoney-master-2001-macos-clang-x86_64.dmg upgrade

[Neil]

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

--- Comment #4 from Neil  ---
(In reply to Jack from comment #3)
> Either way of replying to a bug works, but if you reply by email, please 
> remove all content, as your entire email becomes the next comment, which 
> gets very cluttered if you include the previous message.
> 
> Please post the result of "ls -l 9gwengood4*".   I can't tell if there 
> might be something strange with your filename or if zcat is doing 
> something strange.

neilralph@Neils-MBP ~ % ls -l 9gwengood4*
-rw-r--r--@ 1 neilralph  staff  967340 Aug  1 09:53 9gwengood4.kmy

I confirmed that I can open 9gwengood4.kmy with kmymoney.app (5.1.3)
I noticed that v 5.1.80 doesn't appear in the dropdown choices for the bug
report
I should also mention that, when opening with v5.1.80, kmymoney opens with a
dialog box asking for the currency type.
If I close the dialog without adding my currency (US Dollar) the program
crashes.
I never had issues with currency definition on previous upgrades (i have been
happily using kmymoney since 2008)

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

[kmymoney] [Bug 473223] Data lost on kmymoney-master-2001-macos-clang-x86_64.dmg upgrade

[Neil]

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

Neil  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
Version|git (master)|unspecified
 Status|NEEDSINFO   |REPORTED

--- Comment #7 from Neil  ---
(In reply to Thomas Baumgart from comment #6)
neilralph@Neils-MBP ~ % cp 9gwengood4.kmy 9gwengood4.kmy.Z
neilralph@Neils-MBP ~ % zcat 9gwengood4.kmy | grep 'TRANSACTION>' | wc -l
   21698
neilralph@Neils-MBP ~ % rm 9gwengood4.kmy.Z
neilralph@Neils-MBP ~ %

(In reply to Jack from comment #5)
I am unable to run kmm from command line - quessing a syntax or PATH issue:

neilralph@Neils-MBP ~ % kmymoney -n
zsh: command not found: kmymoney

(In General - I note that /Library/Preferences/ does not contain a file nor
directory for kmymoney)

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

[kmymoney] [Bug 473223] Data lost on kmymoney-master-2001-macos-clang-x86_64.dmg upgrade

[Neil]

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

--- Comment #9 from Neil  ---
Still trying to start from terminal - but in mean time - 
closing the currency dialog (which opens when starting kmymoney from Finder)
causes a crash with the following uncaught error:
Security 'USD' not found.
/Users/packaging/Craft/BinaryFactory/downloads/git/extragear/kmymoney/kmymoney/mymoney/mymoneyfile.cpp:3175

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

[kmymoney] [Bug 473223] Data lost on kmymoney-master-2001-macos-clang-x86_64.dmg upgrade

[Neil]

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

--- Comment #11 from Neil  ---
Okay - Starting from command line opens kmm - 
neilralph@Neils-MBP /Applications %
/Applications/kmymoney.app/Contents/MacOS/kmymoney -n
Terminal prints many items ending with:
Plugins: xmlstorage loaded
Template successfully opened from
"/Applications/kmymoney.app/Contents/Resources/checkprinting/check_template.html"

Everything is OK .. Then I open an existing file and the Currency Dialog opens
- 8 new lines show in Terminal:

2023-08-11 18:22:10.789 kmymoney[6110:382017] +[CATransaction synchronize]
called within transaction
Open file QUrl("file:///Users/neilralph/Nextcloud/Statements/9gwengood6.kmy")
Model for "I" loaded with 8 items in 0 ms
Model for "P" loaded with 1508 items in 8 ms
Start verifying account hierarchy
End verifying account hierarchy
Model for accounts loaded with 358 items in 3 ms
Model for "T" loaded with 33151 items in 84 ms

Upon adding US Dollar and closing the Dialog – Terminal displays many items not
found, ie:

"Account" "A000351" "BPFCU-CD-2747 6 month 12/9/23 " Security 'E72' not
found.
/Users/packaging/Craft/BinaryFactory/downloads/git/extragear/kmymoney/kmymoney/mymoney/mymoneyfile.cpp:3175
"Account" "A000352" "BPFCU-CD-6635 12 month 12/30/23" Security 'E73' not
found.
/Users/packaging/Craft/BinaryFactory/downloads/git/extragear/kmymoney/kmymoney/mymoney/mymoneyfile.cpp:3175

After listing the many "not found"s Terminal displays:

Start calculating balances: 33151 splits
End calculating balances
Processed home view section 8 in 72 ms
Processed home view section 1 in 5 ms
Processed home view section 2 in 4 ms
Processed home view section 3 in 3 ms
Processed home view section 4 in 0 ms
Processed home view section 5 in 7 ms
Processed home view section 6 in 170 ms
Processed home view section 7 in 0 ms
Processed home view section 10 in 5 ms

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

[kmymoney] [Bug 473223] Data lost on kmymoney-master-2001-macos-clang-x86_64.dmg upgrade

[Neil]

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

--- Comment #13 from Neil  ---
Reply to Comment 12
neilralph@Neils-MBP ~ % cp 9gwengood4.kmy 9gwengood4.kmy.Z
neilralph@Neils-MBP ~ % zcat 9gwengood4.kmy | tail -n 10
   
   
   
   
   
  
 
 
 

neilralph@Neils-MBP ~ % rm 9gwengood4.kmy.Z
neilralph@Neils-MBP ~ %

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

[kmymoney] [Bug 473223] Data lost on kmymoney-master-2001-macos-clang-x86_64.dmg upgrade

[Neil]

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

--- Comment #14 from Neil  ---
Comment14 (reply to Comment 12)
before installing v 5.1.8 I renamed kmymoney.app to kmymoney1dot3.app (in macos
Applications)
I can run that from command line:

neilralph@Neils-MBP ~ % /Applications/kmymoney1dot3.app/Contents/MacOS/kmymoney
 -n

KMM opens with no problem
I can then open my latest Linux save (9gwengood6) using within KMM,
which loads with no loss of data.
The File Info  indicates 21741 transactions

I wonder if upgrading from 5.1.3 to 5.1.8 is too great a leap – Should I try
5.1.4?

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

[kmymoney] [Bug 473223] Data lost on kmymoney-master-2001-macos-clang-x86_64.dmg upgrade

[Neil]

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

--- Comment #17 from Neil  ---
Thanks to all of you for your efforts - I began looking at the xml code, which
led me to think that problem might be my sloppy handling of securities as there
were 74 instances of currency="E**". At which point I thought to look how
the version upgrade handled a much smaller .kmy file (216kB) with no
securities.
This Linux .kmy has 4519 transactions with 9174 splits. Upon opening it from
5.1.80 the currency window came up. Upon choosing USD and closing the window
the Home Screen displayed the status of the accounts at the end of 2017.
File Information shows 173 transactions and 345 splits. Upon saving the file
size became 25kB. Transactions later than 2017 were lost. The console printout
did not indicate errors.

Printed Log Upon opening:

2023-08-12 14:41:42.746 kmymoney[8482:577400] +[CATransaction synchronize]
called within transaction
Open file
QUrl("file:///Users/neilralph/Downloads/kmymoney/RalphCenterportGood.kmy")
Model for "I" loaded with 7 items in 0 ms
Model for "P" loaded with 1030 items in 5 ms
Start verifying account hierarchy
End verifying account hierarchy
Model for accounts loaded with 179 items in 1 ms
Model for "T" loaded with 345 items in 0 ms

Printed Log Upon closing Currency Dialog:

Start calculating balances: 345 splits
End calculating balances
Processed home view section 8 in 1 ms
Processed home view section 1 in 0 ms
Processed home view section 2 in 0 ms
Processed home view section 3 in 1 ms
Processed home view section 4 in 0 ms
Processed home view section 5 in 2 ms
Processed home view section 6 in 58 ms
Processed home view section 7 in 0 ms
Processed home view section 10 in 0 ms
Plugins: budgetview unloaded
Plugins: checkprinting unloaded
Plugins: csvexporter unloaded
Plugins: csvimporter unloaded
Plugins: forecastview unloaded
Plugins: gncimporter unloaded
Plugins: icalendarexporter unloaded
Plugins: kbanking unplugged
Plugins: kbanking unloaded
Plugins: ofximporter unloaded
Plugins: onlinejoboutboxview unloaded
Plugins: qifexporter unloaded
Plugins: qifimporter unloaded
Plugins: reconciliation report unloaded
Plugins: reportsview unloaded
Plugins: sqlstorage unloaded
Plugins: xmlstorage unloaded

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

[kmymoney] [Bug 473223] Data lost on kmymoney-master-2001-macos-clang-x86_64.dmg upgrade

[Neil]

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

--- Comment #20 from Neil  ---
(In reply to Thomas Baumgart from comment #19)
neilralph@Neils-MBP kmymoney % zcat RCGcopy.kmy > RCGcopy.xml
neilralph@Neils-MBP kmymoney % grep -n '  
neilralph@Neils-MBP kmymoney % grep -n '  
neilralph@Neils-MBP kmymoney % 

Using Xcode on Mac:

Line 5902
  
  
   


   
  

Line 5896
 
  
   


   
  

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

[kmymoney] [Bug 473223] Data lost on kmymoney-master-2001-macos-clang-x86_64.dmg upgrade

[Neil]

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

--- Comment #21 from Neil  ---
While looking through the xml I wanted to test the assumption that the
transactions import sequentially in line# order – 
Transactions for payee P21 stopped after processing line 4870: (4 lost
before line 5902)

SSA TREAS is P21
finding “TREAS” gave 178 hits, 2/transaction
Line 3902:  12/31/15919/1   caught
Line 3908:  12/31/15383/1   caught
Line 4307:  2/3/2016919/1   caught  
Line 4313   2/3/2016383/1   caught  
Line 4550   3/3/2016919/1   caught  
Line 4556   3/3/2016383/1   caught  
Line 4864   4/1/2016919/1   caught  
Line 4870   4/1/2016383/1   caught  
Line 5230   5/3/2016919/1   missing
Line 5236   5/3/2016383/1   missing
Line 5632   6/3/2016919/1   missing 
Line 5638   6/3/2016383/1   missing

Transactions for payee P000463 stopped after processing line 4858, with two
lost before line 5902
Steve is P000463
388412/28/152000/1  caught
39681/1/16  2001/1  caught
42382/4/16  2001/1  caught
4520`   2/29/16 2000/1  caught
46643/9/16  2000/1  caught
48583/31/16 2000/1  caught
52665/4/16  2000/1  missing
57586/10/16 2000/1  missing

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

[kmymoney] [Bug 473223] Data lost on kmymoney-master-2001-macos-clang-x86_64.dmg upgrade

[Neil]

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

--- Comment #23 from Neil  ---
I am new at working with xml, and it looks like there are numerous issues with
my 2 KMM apps. I think I am going to stick with using 5.3.1 for now. I don't
have the time and skill set necessary for porting to nightly now. Do you
imagine that the upgrade issues will be tackled before 5.3.1 goes out of
support? Might there be an upgrade/conversion utility in the works? 
The Nightly 5.1.80 version looks good but I noticed a few little problems and
issues with it. Should I use a bug report to communicate them or mention the in
a email - if an email - to whom?
Thank you so much for your generosity and attention in helping me !- Neil

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

[kmymoney] [Bug 473223] Data lost on kmymoney-master-2001-macos-clang-x86_64.dmg upgrade

[Neil]

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

--- Comment #25 from Neil  ---
(In reply to Thomas Baumgart from comment #24)
I used xmllint and gedit to clean up the 9gwengood6a.xml file. There were
numerous instances "/00" in TRANSACTION memo fields.
How do I convert the .xml file to .kmy?

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

[kmymoney] [Bug 473223] Data lost on kmymoney-master-2001-macos-clang-x86_64.dmg upgrade

[Neil]

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

--- Comment #27 from Neil  ---
(In reply to Jack from comment #26)
The strings "/00" in the memo fields were found in credit card transactions
imported from .qfx files. When looked at in KMM these transactions all had
exactly 3 lines (not wrapped) in their memos .. I guess codes for new lines in
the qfx files may contribute

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

[kmymoney] [Bug 473477] New: Windowing Issus on Mac

[Neil]

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

Bug ID: 473477
   Summary: Windowing Issus on Mac
Classification: Applications
   Product: kmymoney
   Version: git (master)
  Platform: macOS (DMG)
OS: macOS
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kmymoney-de...@kde.org
  Reporter: nral...@pm.me
  Target Milestone: ---

SUMMARY
KMM opens in a window that is so large that, with the left edge aligned with
the left of the monitor, 1/3 of the KMM window extends beyond the right side of
the monitor. I can drag the window to see the rightmost third, which hides the
left third.
View>Enter Full Screen does not help: ie: In Full Screen, the right most fields
of Ledger Window are hidden (Status, Payment, Deposit, and Balance are
unavailable)

I think it is a KMM problem rather than an Mac problem as Libre Office
windowing is OK.

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

[kmymoney] [Bug 473223] Data lost on kmymoney-master-2001-macos-clang-x86_64.dmg upgrade

[Neil]

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

Neil  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED

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

[plasmashell] [Bug 456988] On X11, Panel autohide with "Keep Window Thumbnails = Always" leaves panel image always visible but non-interactive

[Neil]

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

Neil <1koyl...@duck.com> changed:

   What|Removed |Added

 CC||1koyl...@duck.com

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

[kinfocenter] [Bug 420573] New: system info crashes when energy info tab is clicked

[neil]

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

Bug ID: 420573
   Summary: system info crashes when energy info tab is clicked
   Product: kinfocenter
   Version: 5.12.8
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: hubn...@gmail.com
  Reporter: neilo2...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: ---

Application: kinfocenter (5.12.8)

Qt Version: 5.9.5
Frameworks Version: 5.44.0
Operating System: Linux 5.3.0-28-generic x86_64
Distribution: Ubuntu 18.04.4 LTS

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

pressed energy info tab when in info center
info center crashes every time

The crash can be reproduced every time.

-- Backtrace:
Application: Info Centre (kinfocenter), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7faf8cbb0c80 (LWP 27294))]

Thread 4 (Thread 0x7faf63f27700 (LWP 27301)):
#0  0x7faf83671629 in g_mutex_lock () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7faf8362b156 in g_main_context_dispatch () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7faf8362b650 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7faf8362b6dc in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7faf89ce38ab in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7faf89c8890a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7faf89aa723a in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7faf87d776f5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7faf89aac17d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7faf8555a6db in start_thread (arg=0x7faf63f27700) at
pthread_create.c:463
#10 0x7faf893a788f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 3 (Thread 0x7faf6e2cc700 (LWP 27297)):
#0  __lll_lock_wait () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:135
#1  0x7faf8555d098 in __GI___pthread_mutex_lock (mutex=0x7faf84f878a0) at
../nptl/pthread_mutex_lock.c:113
#2  0x7faf84d03ea0 in ?? () from /usr/lib/x86_64-linux-gnu/libGL.so.1
#3  0x7faf84d0742e in ?? () from /usr/lib/x86_64-linux-gnu/libGL.so.1
#4  0x7faf84d0782b in ?? () from /usr/lib/x86_64-linux-gnu/libGL.so.1
#5  0x7faf81e3afd0 in ?? () from
/usr/lib/x86_64-linux-gnu/tls/libnvidia-tls.so.340.107
#6  0x7faf836702b0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7faf8362b0b7 in g_main_context_check () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x7faf8362b570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x7faf8362b6dc in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x7faf89ce38ab in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7faf89c8890a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x7faf89aa723a in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x7faf873cfd45 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#14 0x7faf89aac17d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x7faf8555a6db in start_thread (arg=0x7faf6e2cc700) at
pthread_create.c:463
#16 0x7faf893a788f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7faf776b3700 (LWP 27296)):
#0  0x7faf8939abf9 in __GI___poll (fds=0x7faf776b2ca8, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7faf833c2747 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7faf833c436a in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7faf7a24e5e9 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x7faf89aac17d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7faf8555a6db in start_thread (arg=0x7faf776b3700) at
pthread_create.c:463
#6  0x7faf893a788f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7faf8cbb0c80 (LWP 27294)):
[KCrash Handler]
#6  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#7  0x7faf892c6801 in __GI_abort () at abort.c:79
#8  0x7faf89a96fb7 in QMessageLogger::fatal(char const*, ...) const () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7faf888f79f0 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5QuickWidgets.so.5
#10 0x7faf888f7d5a in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5QuickWidgets.so.5
#11 0x7faf888f9f8e in QQuickWidget::resizeEvent(QResizeEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5QuickWidgets.so.5
#12 0x7faf

[konsole] [Bug 380077] New: Konsole crash, possibly whilst switching tabs.

[Neil]

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

Bug ID: 380077
   Summary: Konsole crash, possibly whilst switching tabs.
   Product: konsole
   Version: 16.08.2
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: fnmur...@osier-farm.org.uk
  Target Milestone: ---

Application: konsole (16.08.2)

Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.4.62-18.6-default x86_64
Distribution: "openSUSE Leap 42.2"

-- Information about the crash:
I was happily running commands, switching between several tabs, when Poof. All
gone.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Konsole (konsole), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f9fe5d3f8c0 (LWP 29524))]

Thread 3 (Thread 0x7f9fca8ba700 (LWP 29526)):
#0  0x7f9fe567349d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f9fdd0b1314 in g_main_context_poll (priority=2147483647, n_fds=1,
fds=0x7f9fc4003020, timeout=-1, context=0x7f9fc4000990) at gmain.c:4135
#2  g_main_context_iterate (context=context@entry=0x7f9fc4000990,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
gmain.c:3835
#3  0x7f9fdd0b142c in g_main_context_iteration (context=0x7f9fc4000990,
may_block=1) at gmain.c:3901
#4  0x7f9fe1c8632b in QEventDispatcherGlib::processEvents
(this=0x7f9fc40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#5  0x7f9fe1c33fdb in QEventLoop::exec (this=this@entry=0x7f9fca8b9ce0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7f9fe1a6ef1a in QThread::exec (this=this@entry=0x7f9fe00a7ce0
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread.cpp:500
#7  0x7f9fdfe3f1d5 in QDBusConnectionManager::run (this=0x7f9fe00a7ce0
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:189
#8  0x7f9fe1a739e9 in QThreadPrivate::start (arg=0x7f9fe00a7ce0 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:341
#9  0x7f9fdd5ce744 in start_thread (arg=0x7f9fca8ba700) at
pthread_create.c:334
#10 0x7f9fe567bd3d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f9fd0c3e700 (LWP 29525)):
#0  0x7f9fe567349d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f9fdd9f13e2 in poll (__timeout=-1, __nfds=1, __fds=0x7f9fd0c3dc00)
at /usr/include/bits/poll2.h:46
#2  _xcb_conn_wait (c=c@entry=0x1b7bf40, cond=cond@entry=0x1b7bf80,
vector=vector@entry=0x0, count=count@entry=0x0) at xcb_conn.c:459
#3  0x7f9fdd9f2fcf in xcb_wait_for_event (c=0x1b7bf40) at xcb_in.c:693
#4  0x7f9fd3198839 in QXcbEventReader::run (this=0x1b86610) at
qxcbconnection.cpp:1325
#5  0x7f9fe1a739e9 in QThreadPrivate::start (arg=0x1b86610) at
thread/qthread_unix.cpp:341
#6  0x7f9fdd5ce744 in start_thread (arg=0x7f9fd0c3e700) at
pthread_create.c:334
#7  0x7f9fe567bd3d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f9fe5d3f8c0 (LWP 29524)):
[KCrash Handler]
#6  0x7f9fe1c3e3c7 in QMetaObject::cast (this=this@entry=0x7f9fe32bb9a0
, obj=obj@entry=0x86bfc01) at
kernel/qmetaobject.cpp:331
#7  0x7f9fe1c5e984 in qt_qFindChild_helper (parent=,
name=..., mo=..., options=..., options@entry=...) at kernel/qobject.cpp:1928
#8  0x7f9fe1c5e9f8 in qt_qFindChild_helper (parent=parent@entry=0x32518c0,
name=..., mo=..., options=..., options@entry=...) at kernel/qobject.cpp:1933
#9  0x7f9fe4c01004 in QObject::findChild (options=...,
aName=..., this=0x32518c0) at /usr/include/qt5/QtCore/qobject.h:153
#10 KXmlGuiWindow::applyMainWindowSettings (this=this@entry=0x32518c0,
config=...) at /usr/src/debug/kxmlgui-5.26.0/src/kxmlguiwindow.cpp:379
#11 0x7f9fe4c00fb1 in KXmlGuiWindow::finalizeGUI (this=0x32518c0) at
/usr/src/debug/kxmlgui-5.26.0/src/kxmlguiwindow.cpp:371
#12 0x7f9fe4bf1400 in KXMLGUIFactory::addClient (this=0x483fb90,
client=client@entry=0xf1ccc18) at
/usr/src/debug/kxmlgui-5.26.0/src/kxmlguifactory.cpp:275
#13 0x7f9fe59539f7 in Konsole::MainWindow::activeViewChanged
(this=0x32518c0, controller=0xf1ccbf0) at
/usr/src/debug/konsole-16.08.2/src/MainWindow.cpp:231
#14 0x7f9fe1c601c3 in QtPrivate::QSlotObjectBase::call (a=0x7fffbeb31e30,
r=0x32518c0, this=0x67c8320) at ../../src/corelib/kernel/qobject_impl.h:124
#15 QMetaObject::activate (sender=0x67bbea0, signalOffset=,
local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7fffbeb31e30)
at kernel/qobject.cpp:3715
#16 0x7f9fe1c60717 in QMetaObject::activate (sender=,
m=m@entry=0x7f9fe5589cc0 ,
local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7fffbeb31e30)
at kernel/qobject.cpp:3595
#17 0x7f9fe

[ktorrent] [Bug 383436] New: About dialog shows unsafe web address "www.ktorrent.org"

[neil]

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

Bug ID: 383436
   Summary: About dialog shows unsafe web address
"www.ktorrent.org"
   Product: ktorrent
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: joris.guis...@gmail.com
  Reporter: n...@neilhancock.co.uk
  Target Milestone: ---

Ktorrent about dialog links to a web site that appears to be squatted by a
chinese  operation.

Link should be to https://www.kde.org/applications/internet/ktorrent

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

[plasmashell] [Bug 382710] New: Crash on rearranging system tray entries...

[Neil]

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

Bug ID: 382710
   Summary: Crash on rearranging system tray entries...
   Product: plasmashell
   Version: 5.10.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: come_with_m...@protonmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.10.4)

Qt Version: 5.9.1
Frameworks Version: 5.36.0
Operating System: Linux 4.11.9-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed:
I was rearranging entries ( kept some entries in the SHOW mode like akregator
and weather while others in hidden mode like touchpad, clipboard and others).
Right after clicking on apply the plasma shell crashed...

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f32ccf89d80 (LWP 614))]

Thread 9 (Thread 0x7f3214a96700 (LWP 768)):
#0  0x7ffc13bde939 in  ()
#1  0x7ffc13bdebcb in clock_gettime ()
#2  0x7f32c65d1546 in clock_gettime () at /usr/lib/libc.so.6
#3  0x7f32c6eed972 in  () at /usr/lib/libQt5Core.so.5
#4  0x7f32c6eec10a in QTimerInfoList::updateCurrentTime() () at
/usr/lib/libQt5Core.so.5
#5  0x7f32c6eec6e6 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib/libQt5Core.so.5
#6  0x7f32c6eeddcf in  () at /usr/lib/libQt5Core.so.5
#7  0x7f32c1376148 in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#8  0x7f32c1376b3b in  () at /usr/lib/libglib-2.0.so.0
#9  0x7f32c1376d1c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#10 0x7f32c6eee084 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#11 0x7f32c6e91ffb in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#12 0x7f32c6cab40e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#13 0x7f32c6cb015b in  () at /usr/lib/libQt5Core.so.5
#14 0x7f32c5e77049 in start_thread () at /usr/lib/libpthread.so.0
#15 0x7f32c65c3f0f in clone () at /usr/lib/libc.so.6

Thread 8 (Thread 0x7f3216307700 (LWP 767)):
#0  0x7f32c137614e in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#1  0x7f32c1376b3b in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f32c1376d1c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f32c6eee084 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f32c6e91ffb in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f32c6cab40e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f32150a13c5 in  () at
/usr/lib/qt/qml/QtQuick/XmlListModel/libqmlxmllistmodelplugin.so
#7  0x7f32c6cb015b in  () at /usr/lib/libQt5Core.so.5
#8  0x7f32c5e77049 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f32c65c3f0f in clone () at /usr/lib/libc.so.6

Thread 7 (Thread 0x7f3216b12700 (LWP 763)):
#0  0x7f32c1376d17 in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#1  0x7f32c6eee084 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#2  0x7f32c6e91ffb in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#3  0x7f32c6cab40e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#4  0x7f32ca9ec8d6 in  () at /usr/lib/libQt5Quick.so.5
#5  0x7f32c6cb015b in  () at /usr/lib/libQt5Core.so.5
#6  0x7f32c5e77049 in start_thread () at /usr/lib/libpthread.so.0
#7  0x7f32c65c3f0f in clone () at /usr/lib/libc.so.6

Thread 6 (Thread 0x7f32a29a4700 (LWP 729)):
#0  0x7f32c5e7d1ad in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f32cc707b04 in  () at /usr/lib/libQt5Script.so.5
#2  0x7f32cc707b49 in  () at /usr/lib/libQt5Script.so.5
#3  0x7f32c5e77049 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f32c65c3f0f in clone () at /usr/lib/libc.so.6

Thread 5 (Thread 0x7f32acb33700 (LWP 716)):
#0  0x7f32c65b9e9d in poll () at /usr/lib/libc.so.6
#1  0x7f32c1376c09 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f32c1376d1c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f32c6eee084 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f32c6e91ffb in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f32c6cab40e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f32c9e341d5 in  () at /usr/lib/libQt5Qml.so.5
#7  0x7f32c6cb015b in  () at /usr/lib/libQt5Core.so.5
#8  0x7f32c5e77049 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f32c65c3f0f in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7f32aefbf700 (LWP 712)):
#0  0x7f32c13bba69 in g_m

[plasmashell] [Bug 455493] New: Wallpaper doesn't display preview when clicking on images

[Neil Padgett]

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

Bug ID: 455493
   Summary: Wallpaper doesn't display preview when clicking on
images
   Product: plasmashell
   Version: 5.25.0
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Image Wallpaper
  Assignee: plasma-b...@kde.org
  Reporter: neilpadgett...@gmail.com
CC: notm...@gmail.com, qydwhotm...@gmail.com
  Target Milestone: 1.0

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
***
Clicking wallpaper thumbnails in "Configure Desktop and Wallpaper" does not
show preview on the desktop. Have to click OK/Apply to see new wallpaper (just
like previous versions of Plasma).

STEPS TO REPRODUCE
1. Open "Configure Desktop and Wallpaper"
2. Click any thumbnail
3. Plasma 5.25 should then instantly preview that wallpaper on the Desktop

OBSERVED RESULT
Wallpaper does not update/preview.

EXPECTED RESULT
Wallpaper should update/preview on Desktop. Before clicking OK/Apply to accept
change.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: openSUSE Tumbleweed 20220614
(available in About System)
KDE Plasma Version: 5.25.0
KDE Frameworks Version: 5.94.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION

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

[partitionmanager] [Bug 459001] New: Asks for password twice

[Neil Padgett]

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

Bug ID: 459001
   Summary: Asks for password twice
   Product: partitionmanager
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: andr...@stikonas.eu
  Reporter: neilpadgett...@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
***
Partition asks for password twice.

STEPS TO REPRODUCE
1. Open
2. Input password
3. Asked again to input password

OBSERVED RESULT


EXPECTED RESULT
Should only require password once.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: openSUSE Tumbleweed
(available in About System)
KDE Plasma Version: 5.25.5
KDE Frameworks Version: 5.97.0
Qt Version: 5.15.5

ADDITIONAL INFORMATION

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

[digikam] [Bug 460124] New: Unable to acces existing collections

[Neil Baker]

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

Bug ID: 460124
   Summary: Unable to acces existing collections
Classification: Applications
   Product: digikam
   Version: 7.8.0
  Platform: Flatpak
OS: Linux
Status: REPORTED
  Severity: critical
  Priority: NOR
 Component: Setup-Collections
  Assignee: digikam-bugs-n...@kde.org
  Reporter: n...@sgns.co.uk
  Target Milestone: ---

SUMMARY
Version 7.8 does not access elements of my file system.
ie:/opt/
/Store/
STEPS TO REPRODUCE
1. Install flatpak.
2. Got to settings - collections -previous collections correctly listed, but
not accessed. 
3. 

OBSERVED RESULT
Digikam unusable

EXPECTED RESULT


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

ADDITIONAL INFORMATION

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

[kdeconnect] [Bug 477104] KDE Connect crashes after Bluetooth headphones power off (workaround: disable "System volume" plugin on desktop)

[Neil Hanlon]

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

Neil Hanlon  changed:

   What|Removed |Added

 CC||n...@shrug.pw

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

[kdeconnect] [Bug 477104] KDE Connect crashes after Bluetooth headphones power off (workaround: disable "System volume" plugin on desktop)

[Neil Hanlon]

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

--- Comment #24 from Neil Hanlon  ---
Created attachment 165978
  --> https://bugs.kde.org/attachment.cgi?id=165978&action=edit
New crash information added by DrKonqi

kdeconnectd (23.08.4) using Qt 5.15.11

Disconnected Sony WH1000XM4 and KDE connect crashed

-- Backtrace (Reduced):
#4  0x7f2a7647ce17 in PulseAudioQt::CardPrivate::update(pa_card_info
const*) () at /lib64/libKF5PulseAudioQt.so.3
#5  0x7f2a76427d9f in context_get_card_info_callback () at
/lib64/libpulse.so.0
#6  0x7f2a763c0588 in run_action () at
/usr/lib64/pulseaudio/libpulsecommon-16.1.so
#7  0x7f2a763c4b1c in pa_pdispatch_run () at
/usr/lib64/pulseaudio/libpulsecommon-16.1.so
#8  0x7f2a764161ab in pstream_packet_callback () at /lib64/libpulse.so.0

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

[plasmashell] [Bug 483621] New: Plasma Shell Crash

[Neil Chetty]

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

Bug ID: 483621
   Summary: Plasma Shell Crash
Classification: Plasma
   Product: plasmashell
   Version: 6.0.2
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: generic-crash
  Assignee: plasma-b...@kde.org
  Reporter: neilchetty4...@gmail.com
  Target Milestone: 1.0

Application: plasmashell (6.0.2)

Qt Version: 6.6.2
Frameworks Version: 6.0.0
Operating System: Linux 6.8.0-63.fc40.1.x86_64 x86_64
Windowing System: Wayland
Distribution: "Fedora Linux 40 (KDE Plasma Prerelease)"
DrKonqi: 6.0.2 [CoredumpBackend]

-- Information about the crash:
I rebooted my device, opened terminal and entered neofetch. Suddenly desktop
became black, and then it came back, but i got notification of plasma shell
crash
It happends randomly, and i have experienced this few times.

The crash can be reproduced sometimes.

-- Backtrace:
Application: plasmashell (plasmashell), signal: Segmentation fault


This GDB supports auto-downloading debuginfo from the following URLs:
  
Enable debuginfod for this session? (y or [n]) [answered N; input not from
terminal]
Debuginfod has been disabled.
To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit.
[New LWP 2046]
[New LWP 2378]
[New LWP 2399]
[New LWP 2527]
[New LWP 2534]
[New LWP 2395]
[New LWP 2398]
[New LWP 3179]
[New LWP 2192]
[New LWP 2535]
[New LWP 2394]
[New LWP 2526]
[New LWP 3175]
[New LWP 3014]
[New LWP 2191]
[New LWP 2087]
[New LWP 2157]
[New LWP 2079]
[New LWP 2525]
[New LWP 3191]
[New LWP 3171]
[New LWP 2528]
[New LWP 3015]
[New LWP 3183]
[New LWP 2606]
[New LWP 3177]
[New LWP 3016]
[New LWP 3185]
[New LWP 3144]
[New LWP 2532]
[New LWP 2530]
[New LWP 2088]
[New LWP 3176]
[New LWP 2112]
[New LWP 2110]
[New LWP 2098]
[New LWP 2634]
[New LWP 3172]
[New LWP 2407]
[New LWP 3182]
[New LWP 3018]
[New LWP 2531]
[New LWP 2396]
[New LWP 3174]
[New LWP 3145]
[New LWP 2529]
[New LWP 3148]
[New LWP 2524]
[New LWP 3184]
[New LWP 2406]
[New LWP 3189]
[New LWP 2533]
[New LWP 3188]
[New LWP 2635]
[New LWP 3433]
[New LWP 3075]
[New LWP 2111]
[New LWP 3190]
[New LWP 3146]
[New LWP 3435]
[New LWP 3017]
[New LWP 3170]
[New LWP 3431]
[New LWP 2109]
[New LWP 3173]
[New LWP 3178]
[New LWP 3432]
[New LWP 3181]
[New LWP 2097]
[New LWP 3147]
[New LWP 3434]
[New LWP 3187]
[New LWP 3180]
[New LWP 3186]
[New LWP 3192]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/bin/plasmashell --no-respawn'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7f4e122ab184 in __pthread_kill_implementation () from
/lib64/libc.so.6
[Current thread is 1 (Thread 0x7f4e0da26b00 (LWP 2046))]
Cannot QML trace cores :(
[Current thread is 1 (Thread 0x7f4e0da26b00 (LWP 2046))]

Thread 75 (Thread 0x7f4cf56006c0 (LWP 3192)):
#0  0x7f4e1231d73d in poll () from /lib64/libc.so.6
#1  0x7f4e11639244 in g_main_context_iterate_unlocked.isra () from
/lib64/libglib-2.0.so.0
#2  0x7f4e115d96e3 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7f4e12c66de3 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt6Core.so.6
#4  0x7f4e1299c053 in
QEventLoop::exec(QFlags) () from
/lib64/libQt6Core.so.6
#5  0x7f4e12aa9bdf in QThread::exec() () from /lib64/libQt6Core.so.6
#6  0x7f4e12b4562c in QThreadPrivate::start(void*) () from
/lib64/libQt6Core.so.6
#7  0x7f4e122a91f7 in start_thread () from /lib64/libc.so.6
#8  0x7f4e1232b3ac in clone3 () from /lib64/libc.so.6

Thread 74 (Thread 0x7f4d096006c0 (LWP 3186)):
#0  0x7f4e1231d73d in poll () from /lib64/libc.so.6
#1  0x7f4e11639244 in g_main_context_iterate_unlocked.isra () from
/lib64/libglib-2.0.so.0
#2  0x7f4e115d96e3 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7f4e12c66de3 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt6Core.so.6
#4  0x7f4e1299c053 in
QEventLoop::exec(QFlags) () from
/lib64/libQt6Core.so.6
#5  0x7f4e12aa9bdf in QThread::exec() () from /lib64/libQt6Core.so.6
#6  0x7f4e12b4562c in QThreadPrivate::start(void*) () from
/lib64/libQt6Core.so.6
#7  0x7f4e122a91f7 in start_thread () from /lib64/libc.so.6
#8  0x7f4e1232b3ac in clone3 () from /lib64/libc.so.6

Thread 73 (Thread 0x7f4d196006c0 (LWP 3180)):
#0  0x7f4e1231d73d in poll () from /lib64/libc.so.6
#1  0x7f4e11639244 in g_main_context_iterate_unlocked.isra () from
/lib64/libglib-2.0.so.0
#2  0x7f4e115d96e3 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7f4e12c66de3 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt6Core.so.6
#4  0x7f4e1299c053 in
QEventLoop::exec(QFlags) () from
/lib64/libQt6Core.so.6
#5  0x7f4e12aa9bdf in QThread::exec(

[plasmashell] [Bug 484052] New: KDE Plasma 6 Shell Crash | Fedora 40

[Neil Chetty]

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

Bug ID: 484052
   Summary: KDE Plasma 6 Shell Crash | Fedora 40
Classification: Plasma
   Product: plasmashell
   Version: 6.0.2
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: generic-crash
  Assignee: plasma-b...@kde.org
  Reporter: neilchetty4...@gmail.com
  Target Milestone: 1.0

Application: plasmashell (6.0.2)

Qt Version: 6.6.2
Frameworks Version: 6.0.0
Operating System: Linux 6.8.0-63.fc40.1.x86_64 x86_64
Windowing System: Wayland
Distribution: "Fedora Linux 40 (KDE Plasma Prerelease)"
DrKonqi: 6.0.2 [CoredumpBackend]

-- Information about the crash:
I was doing normal work, browsing and playing music. Suddenly task bar
reloaded, and i got notice of kde plasma shell crash. It is happening quite
offenly since when i installed fedora 40.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: plasmashell (plasmashell), signal: Segmentation fault


This GDB supports auto-downloading debuginfo from the following URLs:
  
Enable debuginfod for this session? (y or [n]) [answered N; input not from
terminal]
Debuginfod has been disabled.
To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit.
[New LWP 2034]
[New LWP 2439]
[New LWP 2085]
[New LWP 2670]
[New LWP 2453]
[New LWP 4279]
[New LWP 4282]
[New LWP 2457]
[New LWP 3292]
[New LWP 4272]
[New LWP 4296]
[New LWP 4299]
[New LWP 2456]
[New LWP 4857]
[New LWP 4289]
[New LWP 4290]
[New LWP 2452]
[New LWP 2451]
[New LWP 2782]
[New LWP 4284]
[New LWP 4278]
[New LWP 4288]
[New LWP 4280]
[New LWP 4583]
[New LWP 2084]
[New LWP 4627]
[New LWP 4876]
[New LWP 3078]
[New LWP 2154]
[New LWP 2079]
[New LWP 2074]
[New LWP 2075]
[New LWP 4274]
[New LWP 2087]
[New LWP 4291]
[New LWP 2065]
[New LWP 3076]
[New LWP 2789]
[New LWP 4879]
[New LWP 4293]
[New LWP 3080]
[New LWP 4276]
[New LWP 4286]
[New LWP 3296]
[New LWP 4281]
[New LWP 2086]
[New LWP 4297]
[New LWP 4277]
[New LWP 3294]
[New LWP 4587]
[New LWP 4294]
[New LWP 4285]
[New LWP 4859]
[New LWP 4298]
[New LWP 4283]
[New LWP 4287]
[New LWP 4871]
[New LWP 4629]
[New LWP 4864]
[New LWP 4877]
[New LWP 4631]
[New LWP 4585]
[New LWP 4292]
[New LWP 2078]
[New LWP 4874]
[New LWP 4858]
[New LWP 4866]
[New LWP 3077]
[New LWP 4295]
[New LWP 4273]
[New LWP 4868]
[New LWP 4878]
[New LWP 3079]
[New LWP 3293]
[New LWP 4275]
[New LWP 4584]
[New LWP 4872]
[New LWP 4628]
[New LWP 3295]
[New LWP 4586]
[New LWP 4875]
[New LWP 4630]
[New LWP 4865]
[New LWP 4867]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/bin/plasmashell --no-respawn'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7f0b8eaab184 in __pthread_kill_implementation () from
/lib64/libc.so.6
[Current thread is 1 (Thread 0x7f0b8a1fab00 (LWP 2034))]
Cannot QML trace cores :(
[Current thread is 1 (Thread 0x7f0b8a1fab00 (LWP 2034))]

Thread 84 (Thread 0x7f0afb4006c0 (LWP 4867)):
#0  0x7f0b8eaa5959 in __futex_abstimed_wait_common () from /lib64/libc.so.6
#1  0x7f0b8eaa8329 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libc.so.6
#2  0x7f0b71a9 in cnd_wait () from /usr/lib64/dri/iris_dri.so
#3  0x7f0b71a7b9ab in util_queue_thread_func () from
/usr/lib64/dri/iris_dri.so
#4  0x7f0b71a9dd0c in impl_thrd_routine () from /usr/lib64/dri/iris_dri.so
#5  0x7f0b8eaa91f7 in start_thread () from /lib64/libc.so.6
#6  0x7f0b8eb2b3ac in clone3 () from /lib64/libc.so.6

Thread 83 (Thread 0x7f0b1ea006c0 (LWP 4865)):
#0  0x7f0b8eaa5959 in __futex_abstimed_wait_common () from /lib64/libc.so.6
#1  0x7f0b8eaa8329 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libc.so.6
#2  0x7f0b71a9 in cnd_wait () from /usr/lib64/dri/iris_dri.so
#3  0x7f0b71a7b9ab in util_queue_thread_func () from
/usr/lib64/dri/iris_dri.so
#4  0x7f0b71a9dd0c in impl_thrd_routine () from /usr/lib64/dri/iris_dri.so
#5  0x7f0b8eaa91f7 in start_thread () from /lib64/libc.so.6
#6  0x7f0b8eb2b3ac in clone3 () from /lib64/libc.so.6

Thread 82 (Thread 0x7f0a6a0006c0 (LWP 4630)):
#0  0x7f0b8eaa5959 in __futex_abstimed_wait_common () from /lib64/libc.so.6
#1  0x7f0b8eaa8329 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libc.so.6
#2  0x7f0b71a9 in cnd_wait () from /usr/lib64/dri/iris_dri.so
#3  0x7f0b71a7b9ab in util_queue_thread_func () from
/usr/lib64/dri/iris_dri.so
#4  0x7f0b71a9dd0c in impl_thrd_routine () from /usr/lib64/dri/iris_dri.so
#5  0x7f0b8eaa91f7 in start_thread () from /lib64/libc.so.6
#6  0x7f0b8eb2b3ac in clone3 () from /lib64/libc.so.6

Thread 81 (Thread 0x7f0a74c006c0 (LWP 4875)):
#0  0x7f0b8eaa5959 in __futex_abstimed_wait_common () from /lib64/libc.so.6
#1  0x7f0b8eaa8692 in pthread_cond

[partitionmanager] [Bug 432704] New: Hang everytime at KDE Partition Manager startup after setting Active Backend to KDE Partition Manager Dummy Backend

[Neil Justice]

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

Bug ID: 432704
   Summary: Hang everytime at KDE Partition Manager startup after
setting Active Backend to KDE Partition Manager Dummy
Backend
   Product: partitionmanager
   Version: 4.2.0
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: andr...@stikonas.eu
  Reporter: njjust...@gmail.com
  Target Milestone: ---

Application: partitionmanager (4.2.0)

Qt Version: 5.15.2
Frameworks Version: 5.78.0
Operating System: Linux 5.10.13-200.fc33.x86_64 x86_64
Windowing system: X11
Distribution: Fedora 33 (KDE Plasma)

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

Launched KDE Partition Manager. The program loads with all blanks windows for
each GUI pane and then proceeds to rapidly flicker a blue rectangle around the
"Please select a device" window while displaying a spinning loading cursor
indefinitely. Clicking on menu items does nothing and only clicking the X works
to close the program with a crash.

- Custom settings of the application:

Before when KDE Partition Manager would load successfully I had not yet set
Active Backend to KDE Partition Manager Dummy Backend.

The crash can be reproduced every time.

-- Backtrace:
Application: KDE Partition Manager (partitionmanager), signal: Aborted

[KCrash Handler]
#4  0x7f0d4af069d5 in raise () from /lib64/libc.so.6
#5  0x7f0d4aeef8a4 in abort () from /lib64/libc.so.6
#6  0x7f0d4b32d48f in QMessageLogger::fatal(char const*, ...) const () from
/lib64/libQt5Core.so.5
#7  0x7f0d4b32dcfb in QThread::~QThread() [clone .cold] () from
/lib64/libQt5Core.so.5
#8  0x7f0d4caf6f47 in DeviceScanner::~DeviceScanner() () from
/lib64/libkpmcore.so.10
#9  0x7f0d4b52593a in QObjectPrivate::deleteChildren() () from
/lib64/libQt5Core.so.5
#10 0x7f0d4bfcf246 in QWidget::~QWidget() () from /lib64/libQt5Widgets.so.5
#11 0x56252967c5d4 in MainWindow::~MainWindow() ()
#12 0x7f0d4b525b21 in QObject::event(QEvent*) () from
/lib64/libQt5Core.so.5
#13 0x7f0d4ca74dbd in KXmlGuiWindow::event(QEvent*) () from
/lib64/libKF5XmlGui.so.5
#14 0x7f0d4bf92ec3 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib64/libQt5Widgets.so.5
#15 0x7f0d4b4fdbd8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#16 0x7f0d4b5008c7 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /lib64/libQt5Core.so.5
#17 0x7f0d4b54ac27 in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () from /lib64/libQt5Core.so.5
#18 0x7f0d49d79a5f in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#19 0x7f0d49dcba58 in g_main_context_iterate.constprop () from
/lib64/libglib-2.0.so.0
#20 0x7f0d49d76e33 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#21 0x7f0d4b54a6f3 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#22 0x7f0d4b4fc57b in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#23 0x7f0d4b5041b4 in QCoreApplication::exec() () from
/lib64/libQt5Core.so.5
#24 0x562529677d7f in main ()
[Inferior 1 (process 3558) detached]

Possible duplicates by query: bug 430799, bug 430393, bug 424911, bug 423951,
bug 423132.

Reported using DrKonqi

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

[partitionmanager] [Bug 432704] Hang everytime at KDE Partition Manager startup after setting Active Backend to KDE Partition Manager Dummy Backend

[Neil Justice]

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

--- Comment #1 from Neil Justice  ---
Created attachment 135540
  --> https://bugs.kde.org/attachment.cgi?id=135540&action=edit
KDE Partition Manager blank windows before crash after having previously set
Dummy Backend

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

[partitionmanager] [Bug 432704] Hang everytime at KDE Partition Manager startup after setting Active Backend to KDE Partition Manager Dummy Backend

[Neil Justice]

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

--- Comment #2 from Neil Justice  ---
Created attachment 135541
  --> https://bugs.kde.org/attachment.cgi?id=135541&action=edit
KDE Partition Manager Dr. Konqi crash dialog after clicking the X while KDE
Partition Manager is hanging at startup

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

[digikam] [Bug 431448] problem with Image Editor

[neil keane]

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

--- Comment #4 from neil keane  ---
Hi,

I'm sorry for the silence but as I said in my bug report we have Digikam 
installed on 2 almost identically configured Windows 10  pro 
workstations. The one I'm am sitting at right now and one installed at a 
friends apartment . Unfortunately because of Covid19 on the rampage here 
I don't have access to my friends workstation so I can't retrieve the 
debug information you requested. But the problem she has is that when 
she clicks any of


in the Digikam Editor nothing happens. Everything else works fine. On my 
workstation Digikam works flawlessly including Colour,Enhance and Transform.

The last thing I tried on her WS was to uninstall Digikam and clean the 
Windows10 register of all references to Digikam and then reinstall the 
program. But the problem prevailed. I tried the same procedure with the 
beta 7.2.0 release but to no avail.

In a few weeks we will be vaccinated against covid19 and I can recover 
the debug data you require.

Oh, one other very minor bug, if it has any relevance(?), is that the 
Digikam progam icon is not displayed on the Windows taskbar on her WS, 
instead a default icon is displayed.

sincerely,

neil keane


On 2021-02-21 05:33, Bug Janitor Service wrote:
> https://bugs.kde.org/show_bug.cgi?id=431448
>
> --- Comment #3 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.

[digikam] [Bug 431448] problem with Image Editor

[neil keane]

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

--- Comment #5 from neil keane  ---
Created attachment 136047
  --> https://bugs.kde.org/attachment.cgi?id=136047&action=edit
adhonglgpjfhaomn.png

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

[digikam] [Bug 431448] New: problem with Image Editor

[neil keane]

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

Bug ID: 431448
   Summary: problem with Image Editor
   Product: digikam
   Version: 7.2.0
  Platform: Other
OS: Microsoft Windows
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: ImageEditor
  Assignee: digikam-bugs-n...@kde.org
  Reporter: neil.ke...@hotmail.com
  Target Milestone: ---

Hi,
I´ve just started using Digikam and have it installed on two W10 machines with
version 20H2 (build 19042.685) of Windows 10 installed.
So far it works bug free on one machine but on the other the menu bar items
Color,Enhance,Decorate,Effects in the Image Editor don't respond when clicked.
I've googled the problem but have found any solution or even similar problems.

sincerely,
neil keane

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

[kate] [Bug 461630] New: When kwrite max tabs is set to 1 it should not be possible to edit multiple files

[Neil S]

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

Bug ID: 461630
   Summary: When kwrite max tabs is set to 1 it should not be
possible to edit multiple files
Classification: Applications
   Product: kate
   Version: 22.08.3
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kwrite
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: k...@moley.org.uk
  Target Milestone: ---

STEPS TO REPRODUCE
1. open a text file in kwrite (not kate)
2. settings -> configure -> behaviour -> set 'limit number of tabs' to '1' ->
ok
3. file -> new

OBSERVED RESULT
a new empty document is started in the same window and the old document
disappears. But is still open.

EXPECTED RESULT
With max tabs set to '1' I expect a new kwrite window to be opened.


SOFTWARE/OS VERSIONS
KDE neon 5.26
KDE Plasma Version: 5.26.2
KDE Frameworks Version: 5.99.2
Qt Version: 5.15.7

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

[kmix] [Bug 151297] KMix sliders should account for (output) gain

[Neil S]

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

Neil S  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |FIXED

--- Comment #2 from Neil S  ---
Fixed ages ago with a 'Raise maximum volume' checkbox. Thanks!

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

[kdeconnect] [Bug 481760] KDEconnect crashes on startup

[Neil Hanlon]

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

Neil Hanlon  changed:

   What|Removed |Added

 CC||n...@shrug.pw

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

[kdeconnect] [Bug 481760] KDEconnect crashes on startup

[Neil Hanlon]

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

--- Comment #8 from Neil Hanlon  ---
Created attachment 172303
  --> https://bugs.kde.org/attachment.cgi?id=172303&action=edit
New crash information added by DrKonqi

kdeconnectd (23.08.5) using Qt 5.15.9

New install of Rocky Linux 9.4 with KDE -- application runs but message appears
and app is not functioning fully.

-- Backtrace (Reduced):
#4  0x7f3afb900036 in KdeConnectConfig::deviceId() () from
/lib64/libkdeconnectcore.so.23
#5  0x7f3afb90362d in KdeConnectConfig::deviceInfo() () from
/lib64/libkdeconnectcore.so.23
#6  0x7f3afb8f00b5 in LanLinkProvider::broadcastToNetwork() () from
/lib64/libkdeconnectcore.so.23
#7  0x7f3afa2dbc69 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#8  0x7f3afa2d in QTimer::timeout(QTimer::QPrivateSignal) () from
/lib64/libQt5Core.so.5

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

[kde] [Bug 491486] New: KCalc behaves as if NumLock is off when launched from "Launch" button

[Neil Schelly]

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

Bug ID: 491486
   Summary: KCalc behaves as if NumLock is off when launched from
"Launch" button
Classification: I don't know
   Product: kde
   Version: unspecified
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: n...@schelly.net
  Target Milestone: ---

***
If you're not sure this is actually a bug, instead post about it at
https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

SUMMARY
I have a Microsoft Natural Ergonomic Keyboard 4000. It has buttons along the
top for shortcuts to various applications and functions. I use one of them as a
launcher for kcalc. When I assign a shortcut key to it, it is labelled "Launch
(1)" and it has a picture of a calculator on it.

When launching kcalc from one of the shortcut buttons, it will behave as if
NumLock is off until I either toggle it off then on or click out of the
application and back in. When launching kcalc from another shortcut, like
Ctrl-Alt-K for example, the number pad will work correctly right away.

If I launch kcalc from this button and press keys on the number pad, they will
behave as if NumLock is off. PgUp/PgDn in the number pad will highlight the
buttons in kcalc for C and AC in the application as if I were hitting the
normal PgUp/PgDn keys. The operand keys (/ * - +) all also highlight the
intended key in the application. Numbers will not type.

STEPS TO REPRODUCE
1. Assign a shortcut to launcing kcalc for the "Launch (1)" button on my
keyboard or any other shortcut button along the top of the keyboard.
2. Open kcalc with that shortcut key.

OBSERVED RESULT

1. Press numbers and operands in the number pad. Operands will press the
operand buttons in the kcalc window. Most numbers will be ignored. 9 will act
like PgUp and press the C button in the application (as if NumLock was off). 3
will act like PgDn and press the AC button in the application (as if NumLock
was off).
4. I can toggle NumLock off and on by pressing it twice, and then the number
pad will work as expected.
4 (alternate) I can also just click to another window and then back to kcalc,
and the number will work as expected.

EXPECTED RESULT

I expect kcalc to recognize the number pad presses as soon as it opens.

SOFTWARE/OS VERSIONS
Operating System: Debian GNU/Linux 12
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Kernel Version: 6.1.0-23-amd64 (64-bit)
Graphics Platform: offscreen
Processors: 16 × Intel® Core™ i9-9880H CPU @ 2.30GHz
Memory: 31.0 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 630

ADDITIONAL INFORMATION
* This behavior was new when I upgraded from Debian 11 Bullseye to Debian 12
Bookworm.
* I tried installing the Debian oldstable/11/Bullseye version of kcalc, and it
didn't make a difference. Both versions of kcalc exhibited the above behavior.
* I created shortcuts to kcalc with other built-in shortcut buttons, and I
still get the weird NumLock behavior.
* I created shortcuts to kcalc with "normal" keyboard keys, like Ctrl-Alt-K,
and it behaves as expected.
* I created shortcuts to other applications with the built-in shortcut buttons,
and the number pad works as expected right away in those programs.

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

[kde] [Bug 491486] KCalc behaves as if NumLock is off when launched from "Launch" button

[Neil Schelly]

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

Neil Schelly  changed:

   What|Removed |Added

 CC||n...@schelly.net

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

[konqueror] [Bug 220647] Poor mouse gesture interaction with dialog boxes

[Neil Skrypuch]

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

Neil Skrypuch  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED
 Status|NEEDSINFO   |RESOLVED

--- Comment #4 from Neil Skrypuch  ---
I'm pretty sure this was fixed at some point. I haven't seen it for a long
time.

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

[plasmashell] [Bug 415871] Maximize window on second monitor does not expand window to whole screen

[Neil Moore]

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

Neil Moore  changed:

   What|Removed |Added

 CC||dar13@gmail.com

--- Comment #8 from Neil Moore  ---
This looks similar to the issue I reported in
https://bugs.kde.org/show_bug.cgi?id=420263, but I don't see any pixel overlap
in your screenshot.

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

[plasmashell] [Bug 420263] Using "Screen edge" manipulator on panel puts some pixels of panel on other screens

[Neil Moore]

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

--- Comment #2 from Neil Moore  ---
Update:
After updating to Plasma 5.19.0, I have not seen this bug in Wayland sessions
(though I can't confirm if this is true of 5.18.5 or earlier as the Wayland
session was unusable in my setup before 5.19.0).

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

[plasmashell] [Bug 420263] Using "Screen edge" manipulator on panel puts some pixels of panel on other screens

[Neil Moore]

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

Neil Moore  changed:

   What|Removed |Added

Version|5.18.4  |5.19.0

--- Comment #3 from Neil Moore  ---
Can confirm this still occurs to me on the X11 session in Plasma 5.19.0

Software versions:
KDE Plasma: 5.19.0
KDE Frameworks: 5.70.0
Qt: 5.15.0
Kernel: 5.7.2-arch1-1

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

[plasmashell] [Bug 420263] New: Panel on non-primary screen influences 'top of screen' on primary screen

[Neil Moore]

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

Bug ID: 420263
   Summary: Panel on non-primary screen influences 'top of screen'
on primary screen
   Product: plasmashell
   Version: 5.18.4
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Multi-screen support
  Assignee: aleix...@kde.org
  Reporter: dar13@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Created attachment 127659
  --> https://bugs.kde.org/attachment.cgi?id=127659&action=edit
Screen layout that exhibits the problem

SUMMARY
I have a secondary screen with a panel on the top of the screen that is set to
'Always Visible' and windows cannot go on top or below.

For whatever reason, windows on my primary screen (physically to the left of
the secondary screen) act as if the panel is actually on the primary screen
instead of the secondary screen.

Not sure if related, but the 'Application Launcher' widget that's in the panel,
and its tooltip, opens on the primary screen as well. None of the other wigdets
on that panel open on the primary screen but correctly open/tooltip on the
secondary screen.

STEPS TO REPRODUCE
1. Make a panel on the top screen edge of a secondary screen that is 'Always
Visible' and windows cannot cover or go below
2. Have a window on the primary screen (I used 'System Settings')
3. Try to move the window to a portion of the screen that would be covered by
the panel (if it was on the primary screen)

OBSERVED RESULT
The window attempts to maximize, rather than move. If maximized the window
doesn't cover the entire screen, leaving a section of the wallpaper visible.

EXPECTED RESULT
The window can move there without maximizing.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
(available in About System)
KDE Plasma Version: 5.18.4
KDE Frameworks Version: 5.69.0
Qt Version: 5.14.2

ADDITIONAL INFORMATION
Not actually sure it's a plasmashell bug or KWin, please move as needed.

I'm also somewhat available to try out/make patches, assuming that I can figure
out building the relevant component.

I've attached a screenshot of my screen setup, notice the problematic panel on
the right screen at the top, and a maximized window on the primary screen that
doesn't quite cover the screen.

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

[systemsettings] [Bug 415364] Many touchpad settings are missing.

[Neil Rickert]

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

Neil Rickert  changed:

   What|Removed |Added

 CC||nwr10cst-os...@yahoo.com

--- Comment #2 from Neil Rickert  ---
This still seems a bug to me.

The setting that I am missing is "Disable touchpad when a mouse is plugged in".
 In all honesty, that setting is why I started using KDE.

And that worked for me with openSUSE Leap 15.0 and Leap 15.1 (both using Plasma
5.12.8 and the Libinput drivers).  But the setting is no longer available with
openSUSE Leap 15.2 Beta (using Plasma 5.18.0).  However, it still works if I
copy ".config/touchpadrc" from an earlier system.

I really hope that this setting isn't going away.  And I hope we can get back a
way of configuring it via system settings.

Here's a strange thing.  On one laptop, I see the old touchpad settings screen.
 That laptop was originally configured with openSUSE Leap 15.0, then upgraded. 
However, if I create a new user on that same computer, then I get the new
touchpad settings screen with some settings no longer visible.

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

[plasmashell] [Bug 420263] Panel on non-primary screen influences 'top of screen' on primary screen

[Neil Moore]

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

--- Comment #1 from Neil Moore  ---
I've revisited this and the issue is that whenever I drag the panel using the
"Screen Edge" manipulator, there's a little bit of the panel (a couple of
pixels maybe) on the screen to the left (if the panel is on the rightmost
screen, the leftover pixels are on the middle screen).

The panel has the "never be covered by windows" setting enabled, so now the
middle screen has a black bar.

I'll edit the title accordingly, and I'll look around later to see if this has
already been addressed somewhere else.

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

[plasmashell] [Bug 420263] Using "Screen edge" manipulator on panel puts some pixels of panel on other screens

[Neil Moore]

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

Neil Moore  changed:

   What|Removed |Added

Summary|Panel on non-primary screen |Using "Screen edge"
   |influences 'top of screen'  |manipulator on panel puts
   |on primary screen   |some pixels of panel on
   ||other screens

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

[kdeconnect] [Bug 417577] Remote Input not working with specific monitor arrangement

[Neil Moore]

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

Neil Moore  changed:

   What|Removed |Added

 CC||dar13@gmail.com

--- Comment #1 from Neil Moore  ---
I've run into this as well, there's an upstream Qt bug
(https://bugreports.qt.io/browse/QTBUG-55038) that KDEConnect runs into.

Presumably, the current work to use org.freedesktop.portal.RemoteDesktop as the
remote input backend will fix this entirely but that work isn't done yet.

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

[digikam] [Bug 393130] New: Tag manager now opens a separate window

[Neil Baker]

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

Bug ID: 393130
   Summary: Tag manager now opens a separate window
   Product: digikam
   Version: 5.5.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Tags-Manager
  Assignee: digikam-bugs-n...@kde.org
  Reporter: n...@sgns.co.uk
  Target Milestone: ---

This makes window management difficult.
I use a complex tag hierarchy and am therefore now looking for an alternative
to digikam.

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

[qaccessibilityclient] [Bug 375419] New: KDE accessibility dialogue appears at inappropriate times

[Neil Turton]

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

Bug ID: 375419
   Summary: KDE accessibility dialogue appears at inappropriate
times
   Product: qaccessibilityclient
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: gladh...@kde.org
  Reporter: 0neiltk@chiark.greenend.org.uk
  Target Milestone: ---

I can reproduce this problem with a guest session, so it isn't due to a
particularly strange configuration.

  1. Start a KDE session
  2. Open System settings and go to Desktop Behavior/Accessibility
  3. On the Activation Gestures tab, disable "Use gestures for activating
sticky keys and slow keys".
  4. Enable "Show a confirmation dialog whenever a keyboard accessibility
feature is toggled".
  5. Open an xterm (not konsole)
  6. Run this command to ring the terminal bell: perl -e 'print pack("C",7)'
  7. A dialogue appears reading 'Do you really want to activate "Slow keys",
"Bounce keys", and "Mouse keys"?'
  8. Select "Deactivate all AccessX features and gestures".
  9. Press the "No" button to close the dialog.
 10. Run the command to ring the terminal bell: perl -e 'print pack("C",7)'
 11. The dialogue appears again.

I would expect the system bell to be rung without generating a dialogue.

Step 6 can be replaced by pressing the backspace key or tab twice or a variety
of other actions which cause xterm to ring the bell.

A workaround for this bug is to disable the confirmation dialog which was
enabled in step 4.  I don't think there's any side-effect of the workaround.

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

[kwin] [Bug 389341] New: Kwin_X11 constantly restarting and not loading.

[Neil Brownlee]

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

Bug ID: 389341
   Summary: Kwin_X11 constantly restarting and not loading.
   Product: kwin
   Version: 5.11.95
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: n.brown...@pccsuk.com
  Target Milestone: ---

Application: kwin_x11 (5.11.95)

Qt Version: 5.9.1
Frameworks Version: 5.42.0
Operating System: Linux 4.13.0-30-generic x86_64
Distribution: Ubuntu 17.10

-- Information about the crash:
- What I was doing when the application crashed: I was trying to login!
Everytime I use KDE + Plasma - Kwin_X11 fails.

The crash can be reproduced every time.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fc9f47ac940 (LWP 3410))]

Thread 7 (Thread 0x7fc9ba4d2700 (LWP 3440)):
#0  0x7fc9ed141072 in futex_wait_cancelable (private=,
expected=0, futex_word=0x7fc9f070efb8) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7fc9ed141072 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x7fc9f070ef68, cond=0x7fc9f070ef90) at pthread_cond_wait.c:502
#2  0x7fc9ed141072 in __pthread_cond_wait (cond=0x7fc9f070ef90,
mutex=0x7fc9f070ef68) at pthread_cond_wait.c:655
#3  0x7fc9f041abd4 in  () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#4  0x7fc9f041ac19 in  () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#5  0x7fc9ed13a7fc in start_thread (arg=0x7fc9ba4d2700) at
pthread_create.c:465
#6  0x7fc9f413fb5f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 6 (Thread 0x7fc9bb9c2700 (LWP 3439)):
#0  0x7fc9f1522ad4 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#1  0x7fc9f14cae3a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7fc9f12ea3ca in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7fc9ebc24f45 in  () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#4  0x7fc9f12ef29d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fc9ed13a7fc in start_thread (arg=0x7fc9bb9c2700) at
pthread_create.c:465
#6  0x7fc9f413fb5f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 5 (Thread 0x7fc9bc2ba700 (LWP 3436)):
#0  0x7fc9ed141072 in futex_wait_cancelable (private=,
expected=0, futex_word=0x558e5b798230) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7fc9ed141072 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x558e5b7981e0, cond=0x558e5b798208) at pthread_cond_wait.c:502
#2  0x7fc9ed141072 in __pthread_cond_wait (cond=0x558e5b798208,
mutex=0x558e5b7981e0) at pthread_cond_wait.c:655
#3  0x7fc9c18e7d1b in  () at /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#4  0x7fc9c18e7a38 in  () at /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#5  0x7fc9ed13a7fc in start_thread (arg=0x7fc9bc2ba700) at
pthread_create.c:465
#6  0x7fc9f413fb5f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 4 (Thread 0x7fc9bcc02700 (LWP 3435)):
#0  0x7fc9ed141072 in futex_wait_cancelable (private=,
expected=0, futex_word=0x558e5bc072d8) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7fc9ed141072 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x558e5bc07288, cond=0x558e5bc072b0) at pthread_cond_wait.c:502
#2  0x7fc9ed141072 in __pthread_cond_wait (cond=0x558e5bc072b0,
mutex=0x558e5bc07288) at pthread_cond_wait.c:655
#3  0x7fc9c18e7d1b in  () at /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#4  0x7fc9c18e7a38 in  () at /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#5  0x7fc9ed13a7fc in start_thread (arg=0x7fc9bcc02700) at
pthread_create.c:465
#6  0x7fc9f413fb5f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 3 (Thread 0x7fc9d1401700 (LWP 3434)):
#0  0x7fc9f4133a4b in __GI_ppoll (fds=0x7fc9c8000d18, nfds=1,
timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39
#1  0x7fc9f1521151 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7fc9f152286e in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7fc9f14cae3a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fc9f12ea3ca in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fc9ebc24f45 in  () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#6  0x7fc9f12ef29d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fc9ed13a7fc in start_thread (arg=0x7fc9d1401700) at
pthread_create.c:465
#8  0x7fc9f413fb5f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7fc9d3952700 (LWP 3414)):
#0  

[kscreenlocker] [Bug 346741] bring back "auto-lock screen on login" option from KDM/Plasma 4

[Neil Sedger]

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

Neil Sedger  changed:

   What|Removed |Added

 CC||k...@moley.org.uk

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

[plasma-nm] [Bug 380797] New: Cannot set MTU of wired connection

[Neil Rickert]

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

Bug ID: 380797
   Summary: Cannot set  MTU of wired connection
   Product: plasma-nm
   Version: 5.10.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: applet
  Assignee: jgrul...@redhat.com
  Reporter: nwr10cst-os...@yahoo.com
  Target Milestone: ---

I attempted to set MTU for wired connection to 1472 (recommended for IPv6 via
6rd).

Note: this is also reported as Bug 1042542 for opensuse
(bugzilla.opensuse.org).

In the client, I made the change, then clicked "Okay" (or "Apply").  I expected
a connection definition file (probably "Wired connection 1") to be save in
"/etc/NetworkManager/system-connections" with the changed setting.  Instead,
nothing happened.  I rebooted, and the MTU was still 1500.

I also have Gnome desktop installed.  I tried using the Gnome NetworkManager
client, and changing the MTU there worked as expected (while logged into
Gnome).

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

[plasma-nm] [Bug 380797] Cannot set MTU of wired connection

[Neil Rickert]

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

--- Comment #2 from Neil Rickert  ---
I am seeing the problem on openSUSE Tumbleweed (plasma-nm 5.10.0 -- actually
called "plasma-nm5 there).

I am also seeing the problem on KaOS, with plasma-nm 5.9.5.1

With the way that openSUSE handles NM, there should have been a polkit window
that popped up when I tried to save the changes.  But there was no such polkit
popup.  Similarly, with KaOS, there was no polkit popup.

It's a while since I last used Fedora. But I seem to recall that it was more
generous with allowing network config changes, so perhaps it would not have
required a polkit query.

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

[plasmashell] [Bug 401558] New: Plasma crashes when changing the battery icon visibility

[Neil Turton]

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

Bug ID: 401558
   Summary: Plasma crashes when changing the battery icon
visibility
   Product: plasmashell
   Version: 5.12.6
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: 0neiltk@chiark.greenend.org.uk
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.12.6)

Qt Version: 5.9.5
Frameworks Version: 5.44.0
Operating System: Linux 4.15.0-39-generic x86_64
Distribution: Ubuntu 18.04.1 LTS

-- Information about the crash:
- To reproduce:
 1. Open system tray settings
 2. Select the "Entries" tab on the left
 3. Change the visiblity of "Battery and Brightness"
 4. Click "Okay".

At this point, the desktop background goes black and the panel at the top
disappears.  They both return to normal after a moment.

Effects of different visibility changes:
  "Auto" to "Shown": Crashes
  "Shown" to "Auto": Crashes
  "Hidden" to "Auto": No crash
  "Auto" to "Hidden": No crash
  "Hidden" to "Shown": Crashes
  "Shown" to "Hidden": Crashes

The cases which don't crash are the ones where the actual visibility of the
icon doesn't change.  At the time of testing, Auto means that the icon is
hidden.

Clicking the "Apply" button instead of "Okay" in step 4 occasionally causes a
crash, but only rarely.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fa7a21a4800 (LWP 5069))]

Thread 17 (Thread 0x7fa69d7fa700 (LWP 24093)):
#0  0x7fa79b02a9f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x55eff79681b0) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7fa79b02a9f3 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x55eff7968160, cond=0x55eff7968188) at pthread_cond_wait.c:502
#2  0x7fa79b02a9f3 in __pthread_cond_wait (cond=0x55eff7968188,
mutex=0x55eff7968160) at pthread_cond_wait.c:655
#3  0x7fa79bea459b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fa6e6277ad5 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#5  0x7fa6e627bba8 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#6  0x7fa6e6276c8d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#7  0x7fa6e627bc02 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#8  0x7fa6e6276c8d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#9  0x7fa6e6279a6b in ThreadWeaver::Thread::run() () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#10 0x7fa79bea316d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7fa79b0246db in start_thread (arg=0x7fa69d7fa700) at
pthread_create.c:463
#12 0x7fa79b79e88f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 16 (Thread 0x7fa69dffb700 (LWP 24092)):
#0  0x7fa79b02a9f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x55eff79681b0) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7fa79b02a9f3 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x55eff7968160, cond=0x55eff7968188) at pthread_cond_wait.c:502
#2  0x7fa79b02a9f3 in __pthread_cond_wait (cond=0x55eff7968188,
mutex=0x55eff7968160) at pthread_cond_wait.c:655
#3  0x7fa79bea459b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fa6e6277ad5 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#5  0x7fa6e627bba8 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#6  0x7fa6e6276c8d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#7  0x7fa6e627bc02 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#8  0x7fa6e6276c8d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#9  0x7fa6e627bc02 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#10 0x7fa6e6276c8d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#11 0x7fa6e627bc02 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#12 0x7fa6e6276c8d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#

[kde] [Bug 383260] New: Resolution changes leak across X sessions

[Neil Skrypuch]

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

Bug ID: 383260
   Summary: Resolution changes leak across X sessions
   Product: kde
   Version: unspecified
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: xinerama
  Assignee: l.lu...@kde.org
  Reporter: k...@skrypuch.com
  Target Milestone: ---

For context, I have a triple monitor setup (3840x2160 center monitor with a
1600x1200 monitor rotated 90 degrees clockwise to the left and the right of the
center monitor) all connected to a GTX 1080 Ti. In my xorg.conf is a static
metamode (Nvidia style) describing this setup so that it's setup properly even
if I'm not using KDE (SDDM, or a bare X session for example). This all works
great and I've done something similar for many many years.

Now, due to the fact that I normally have a lot of windows open and I don't
want them to be moved around or resized on me (as generally happens if the
resolution is changed) if I do actually want to run something in a different
resolution (mainly games, but also required for Gsync to work (as it only works
with a single active monitor)), then I will start a second X session (:1) and
switch *that* session's resolution, to guarantee that my primary X session (:0)
remains untouched.

Today, I executed the second X session as described above (switching center
monitor to 3840x2160 and the side monitors off via xrandr) and when I was done,
I returned to my primary X session and discovered that my resolution had been
changed (primary and right monitor were off, left monitor was the correct
resolution but no longer rotated). Frustrated, I killed that X session and and
let the static xorg.conf setup fix the resolution, which it did at the login
manager (SDDM). However, immediately after starting KDE, I was returned to the
broken resolution (left monitor not rotated, other two monitors off). At this
point the only way to fix the setup was to manually open nvidia-settings,
rotate my head 90 degrees and reenable the other two monitors and set the
monitor rotations correctly (using the kscreen equivalent probably would work
too - I didn't try, but ultimately not relevant). At this point, the correct
resolution will persist across KDE logins as expected (until of course one
tries to use a second X session again).

This issue is reproducible every time (with the same broken resolution on the
primary X session), regardless of the resolution change that actually happened
on the second X session. This started happening quite recently, no more than 6
months ago, but probably even less.

I'm not sure what specific component is at fault here, but I'm currently using
plasma-5.34.0 and plasma-meta-5.9.5. In the past 6 months, plasma-meta was
updated from 5.8.5 to 5.8.6 and then to 5.9.5, while plasma was updated from
5.29.0 to 5.34.0. I can provide further version details for other packages upon
request.

In short, it appears that KDE is:
a) listening for all resolution changes (across all X sessions, not just the
current X session nor just any X sessions with KDE running in them), and
b) attempting to update the resolution of a KDE session in response to a), and
c) failing badly at changing the resolution (probably because changing
resolution of a non-active X session is generally a no-no), and
d) saving the broken resolution settings and persisting them into the next
session, undoing the static xorg.conf config

I suspect the design intent here was to notice resolution changes in the
current KDE session (even when they happen via xrandr and not through a KDE
tool) and persist them across sessions (arguably a nice feature to have), but
this should not pick up resolution changes in other X sessions (especially
non-KDE X sessions).

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

[kde] [Bug 383260] Resolution changes leak across X sessions

[Neil Skrypuch]

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

Neil Skrypuch  changed:

   What|Removed |Added

 CC||k...@skrypuch.com

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

[kde] [Bug 383260] Resolution changes leak across X sessions

[Neil Skrypuch]

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

Neil Skrypuch  changed:

   What|Removed |Added

 Resolution|--- |UPSTREAM
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Neil Skrypuch  ---
Actually, upon further testing, two things become apparent:

1) It's not the resolution change that's triggering the issue, it's the VT
switch (to another X session... text mode is ok), and
2) updating from nvidia-drivers-384.47 to nvidia-drivers-384.59-r1 fixes the
issue.

It was likely an nvidia-drivers bump in the past couple months that broke it
(there were several in that time) in the first place, I just hadn't noticed
yet.

KDE automagically saving the active resolution and reapplying it at login time
is a new one on me, so I was initially barking up the wrong tree.

Sorry for the noise.

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

[plasma-nm] [Bug 380797] Cannot set MTU of wired connection

[Neil Rickert]

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

--- Comment #4 from Neil Rickert  ---
In openSUSE Tumbleweed, NetworkManager shows up as version 1.6.2.

On KaOS, where I also see this problem, NetworkManager appears to be version
1.8.0.

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

[plasma-nm] [Bug 380797] Cannot set MTU of wired connection

[Neil Rickert]

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

--- Comment #5 from Neil Rickert  ---
Tumbleweed upgrade plasma-nm to version 5.10.1 today.  So I decided to retest.

The problem is still there.  But I paid closer attention to what is happening.

When I start editing the Wired connect settings, I see "Okay", "Apply" and
"Cancel" buttons near the bottom of the screen.  But the "Apply" is grayed out,
so cannot be used.

When I change something (I tried changing the MTU from 1472 to 1471), the
"Apply" remains greyed out.  So the applet is not recognizing that there are
changes that need to be saved.

By contrast, if I edit a "WiFi" connection settings, then the change of MTU
from 1472 to 1471 (and then back to 1472) makes the Apply button active (not
grayed out).

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

[plasma-nm] [Bug 380797] Cannot set MTU of wired connection

[Neil Rickert]

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

--- Comment #7 from Neil Rickert  ---
>Could you please check whether this is not a duplicate of bug 378554?

Yes, it appears to be the same bug.

I set "allow auto-negotiation".  Then "Apply" was no longer grayed out.  I
changed the MTU to 1471 and clicked "Apply" (and was prompted for root
password).  Checking the connection file in
"/etc/NetworkManager/system-connection", the MTU information had changed to
1471.

I was then prompted for the "kdewallet" key.  I'm not sure what that is about,
since this is a wired connection.

I closed the connection editor.  Then I restarted it.  I could see that "allow
auto-negotiation" was still checked.  I changed the MTU back to 1472.  And that
caused "Apply" to no longer be grayed out.  And I was able to save those
changes.

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

[plasmashell] [Bug 375113] New: Plasmashell crashes when selecting a status widget with "Status and Notifications" open.

[Neil Turton]

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

Bug ID: 375113
   Summary: Plasmashell crashes when selecting a status widget
with "Status and Notifications" open.
   Product: plasmashell
   Version: 5.5.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: System Tray
  Assignee: plasma-b...@kde.org
  Reporter: 0neiltk@chiark.greenend.org.uk
  Target Milestone: 1.0

I can reliably crash plasmashell as follows:
  Make sure the touchpad is on the "Status & Notifications" panel.
  Select Touchpad settings.
  Assign a "Meta+Shift+T" as the shortcut for Touchpad.
  Press "Ok".
  Open the "Status & Notifications" panel.
  Press Meta+Shift+T to activate the Touchpad widget.
  The "Status & Notifications" panel closes and then plasmashell crashes.

Normally, Meta+Shift+T would open the "Status & Notifications" panel in order
to show the Touchpad widget.

The same procedure works with the "Notifications" widget, the "Device Notifier"
widget and the "Printers" widget.

I am using the Ubuntu package version "4:5.5.5.2-0ubuntu1".  The --version
option reports "plasmashell 5.5.5".

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

[plasma-nm] [Bug 359842] Shared connection asks for root password on every reconnect.

[Neil Rickert via KDE Bugzilla]

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

Neil Rickert  changed:

   What|Removed |Added

 CC||nrick...@ameritech.net

--- Comment #14 from Neil Rickert  ---
In my opinion, this should be reopened.  I won't reopen because of comment 8,
but I disagree with that comment.

Firstly, this is specifically a plasma 5 issue.  If the network connect is
setup in Gnome or XFCE or MATE or LXDE, then the problem does not arise.  If
"nm-applet" is used as network client and the connection is setup with that
client, the problem does not arise.  When I tried running nm-applet in Plasma
5, I could not access it, so nm-applet has to be run elsewhere.

Since it works with nm-applet (which is used in XFCE), then it cannot be a
polkit problem.  Rather, the plasma client does things differently and, in my
opinion, wrongly.

I have a blog post about this at:
https://nwrickert2.wordpress.com/2016/01/06/another-look-at-networkmanager-and-tumbleweed/

Responding to comment 4
>I think that "org.freedesktop.NetworkManager.settings.modify.system" = "auth" 
>is responsible for your problem.

Yes, that's possible.  But that's the wrong polkit rule.  The user is just
making a connection.  The user is not changing a system connection.  In my
opinion, it should instead use
"org.freedesktop.NetworkManager.network-control".  As far as I know, it is a
plasma issue to specify the appropriate rule.

When the user first changed the connection to be a system connection, then
"modify.system" was appropriate.  But just connecting to an existing system
connection does not modify the connection definition, so should be under the
more general "network-control".

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

[plasma-nm] [Bug 359842] Shared connection asks for root password on every reconnect.

[Neil Rickert via KDE Bugzilla]

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

--- Comment #18 from Neil Rickert  ---
Thanks for reopening.

I did not get any email for the recent comments.  I think my ISP may be
blocking KDE.org.  So I have now changed the email address that I am using. 
(The same problem happened with the opensuse bugzilla).

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