[systemsettings] [Bug 483115] Lost hotkey assignment and reappearing deleted hotkey entries in KDE 6

[Nelson]

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

--- Comment #3 from Nelson  ---
(In reply to Nicolas Fella from comment #1)
> Can you please attach your .config/kglobalshortcutsrc?

Certainly. I have added it as an attachment now.

I noticed that when I set the Dolphin shortcut, an entry gets added to this
file with the hotkey; but upon restart, it's no longer there.

I also didn't see any reference in it to the extra entries I cannot get rid of.

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

[systemsettings] [Bug 483115] Lost hotkey assignment and reappearing deleted hotkey entries in KDE 6

[Nelson]

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

--- Comment #2 from Nelson  ---
Created attachment 167492
  --> https://bugs.kde.org/attachment.cgi?id=167492=edit
kglobalshortcutsrc config file

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

[neon] [Bug 482305] Cannot install Kjots in KDE 6, dependency issue

[Nelson]

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

--- Comment #6 from Nelson  ---
(In reply to Jonathan Riddell from comment #5)
> Could Zanshin or KNotes be a recommended replacement?

I was not aware of Zanshin's existence. It looks interesting, but that's more
of a task program. KNotes, however, is closer to what I need and, for some
reason, picked up my existing KJots notes, which I thought were lost forever.
Good suggestion. Thanks!

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

[dolphin] [Bug 481506] [X11, qt 6.7 beta 3 ] Open Terminal Here in Dolphin crashes konsole

[Nelson]

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

--- Comment #6 from Nelson  ---
(In reply to Bernhard Rosenkränzer from comment #5)
> This is caused by KTerminalLauncherJob launching konsole with an empty
> environment (causing the DISPLAY variable to go missing, causing the
> connection to the X server to fail).
> It has already been fixed in git (and in OpenMandriva packages).
> https://invent.kde.org/frameworks/kio/-/commit/
> 6e7775d315f389df0a440ed62b842ce83dc9a27e

That's good. But excuse me, I'm not a technical user: what does it mean it's
fixed in git? I hear there's a KDE 6.0.1 out already with some fixes, but on
Neon, the distro I use, it's not yet available, for example. Can we know when
the fixes will be released on any given distro?

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

[neon] [Bug 482305] Cannot install Kjots in KDE 6, dependency issue

[Nelson]

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

--- Comment #4 from Nelson  ---
(In reply to Jonathan Riddell from comment #3)
> KJots has no currently working released version unfortunately.
> 
> We should make a dummy override package in Neon and remove it from
> apps.kde.org

Does this mean Kjots is abandoned? If so, any replacement recommendations?

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

[kwin] [Bug 483282] Firefox picture-in-picture video lags while self-closing notifications are shown

[Nelson]

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

--- Comment #2 from Nelson  ---
(In reply to Nate Graham from comment #1)
> I can't reproduce this on Wayland. Can you?

I cannot.
On Wayland, the PIP video does not suffer any slowdown when a notification is
visible.
It seems it only happens on X11.

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

[systemsettings] [Bug 483115] Lost hotkey assignment and reappearing deleted hotkey entries in KDE 6

[Nelson]

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

Nelson  changed:

   What|Removed |Added

 CC||dubh...@yandex.com

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

[kwin] [Bug 483282] Firefox picture-in-picture video lags while self-closing notifications are shown

[Nelson]

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

Nelson  changed:

   What|Removed |Added

 CC||dubh...@yandex.com

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

[kwin] [Bug 483282] New: Firefox picture-in-picture video lags while self-closing notifications are shown

[Nelson]

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

Bug ID: 483282
   Summary: Firefox picture-in-picture video lags while
self-closing notifications are shown
Classification: Plasma
   Product: kwin
   Version: 6.0.0
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: dubh...@yandex.com
  Target Milestone: ---

SUMMARY
When a Firefox picture-in-picture window is open and a timed notification comes
on screen, the video is affected by terrible lag until the notification is gone
or manually closed.

Not sure if this is even a KDE thing or a Firefox thing (but I don't see the
problem on Firefox for Windows). Tested in LibreWolf too and it's the same.

It's reproducible every time (version 5.27 too).

STEPS TO REPRODUCE
1. Have a video playing in picture-in-picture mode in Firefox.
2. Wait for a notification to appear (KTeaTime notifications work every time to
trigger this issue; but only the timed one when the tea is ready; not the one
when the timer starts)

OBSERVED RESULT
While the temporary notification is visible, the video will lag a lot. Once the
notification automatically closes, playback will continue normally. It will
happen again on the next notification.

EXPECTED RESULT
Notifications do not affect video playback.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Neon
KDE Plasma Version: 6.0.0
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Using X11

ADDITIONAL INFORMATION
NVIDIA card, proprietary drivers; AMD CPU.
Notifications set to bottom right corner, if it matters. Single monitor.
Using standalone notifications widget in the taskbar instead of the entry in
the system tray, which is deactivated.
This issue is 100% reproducible every single time and I have experienced it for
as long as I can remember.
Apologies if this does not belong here; but I assumed it's worth a shot.

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

[systemsettings] [Bug 483115] New: Lost hotkey assignment and reappearing deleted hotkey entries in KDE 6

[Nelson]

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

Bug ID: 483115
   Summary: Lost hotkey assignment and reappearing deleted hotkey
entries in KDE 6
Classification: Applications
   Product: systemsettings
   Version: 6.0.0
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm_keys
  Assignee: plasma-b...@kde.org
  Reporter: dubh...@yandex.com
CC: k...@david-redondo.de
  Target Milestone: ---

Created attachment 166877
  --> https://bugs.kde.org/attachment.cgi?id=166877=edit
Partial view of the hotkey assignment screen in system settings

SUMMARY
In the hotkey assignment part of system settings, I had a shortcut to open
Dolphin (Meta+E) which stopped working in the new KDE version. If I re-assign
it, it works; but after rebooting, the shortcut is lost.

Similarly, I had installed Waydroid to try it out and a lot of entries of its
programs appeared in the hotkey section. I have uninstalled it now, but the
hotkey entries remain. I can delete the entries from the list by pressing the
trash can button next to them, but after restarting, they are back.

STEPS TO REPRODUCE
1. Set shortcut and/or remove leftover entries
2. Reboot

OBSERVED RESULT
Shortcut is gone and entries are back.

EXPECTED RESULT
Shortcut remains assigned and entries remain deleted.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Neon
KDE Plasma Version: 6.0.0
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Using X11

ADDITIONAL INFORMATION
Not sure if these two problems are related but since both involve setting
something in the hotkey screen, which is then lost upon restart, I'm reporting
them together.

I have attached an image showing the hotkeys section with all the entries added
from using Waydroid; and the Dolphin entry with no shortcut set.

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

[Powerdevil] [Bug 481308] screen locker black with cursor on X11

[Nelson]

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

--- Comment #36 from Nelson  ---
(In reply to Luke from comment #33)
> (In reply to Bug Janitor Service from comment #31)
> > A possibly relevant merge request was started @
> > https://invent.kde.org/plasma/powerdevil/-/merge_requests/332
> 
> Following the logic of this merge request, I was able to fix the problem on
> my PC by:
> - enabling automatic screen turn-off;
> - setting a long-enough LockGrace period.
> In my case, LockGrace has to be at least 15 seconds; as soon as it’s set
> lower, the unintentional screen turn-off happens again.

Can confirm that this setting works. At 15 seconds or more the expected
behavior comes back, seeing the lock screen and the screen does not turn off
either when locking nor unlocking. Thanks!

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

[plasmashell] [Bug 482339] Tasks Show on incorrect screen after monitor reconnected

[Bradley Nelson]

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

Bradley Nelson  changed:

   What|Removed |Added

Summary|Tasks Show on incorrect |Tasks Show on incorrect
   |screen after sleep  |screen after monitor
   ||reconnected

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

[plasmashell] [Bug 482339] Tasks Show on incorrect screen after sleep

[Bradley Nelson]

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

--- Comment #16 from Bradley Nelson  ---
STEPS TO REPRODUCE
1. Configure multiple monitors 
2. Add a panel with a task bar to each monitor
3. set task bar to only show tasks from current screen.
4. Open Settings and Disable a monitor
5. Reenable

OBSERVED RESULT
The panel on the left most screen shows all tasks. Tasks are still shown on
other screens but can't be left clicked to activate the application or right
click for more options.

EXPECTED RESULT
Tasks are only shown when on that screen and can be clicked to activate.

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

[plasmashell] [Bug 482339] Tasks Show on incorrect screen after sleep

[Bradley Nelson]

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

--- Comment #15 from Bradley Nelson  ---
(In reply to qlum from comment #13)
> I am unsure if this is the same bug, but I have observed the following
> behavior when using the option to only show tasks on the current screen:
> Whenever a monitor disconnect or gets connected, the task manager on one
> screen may end up showing tasks of all monitors.
> I suspect this is the problem the OP is encountering when waking up from
> sleep, somewhere along the way a screen gets disconnected and reconnected.
> 
> Another related case where this fails, is when moving panels between
> monitors.
> If you move a panel with a task manager showing only tasks from one screen
> to a different monitor, it will still show tasks from the monitor it was on
> before.
> So if the panel was first on monitor 1 and is switched around with the panel
> on monitor 2, the panel on monitor 2 will show the tasks on monitor 1 and
> vise versa. 
> 
> I have confirmed at least the first case on 2 systems, I think these issues
> when I switched to the plasma 6 beta, but never got around confirming /
> reporting them.

This does appear to the the case. I can reproduce it by disconnecting a monitor
and reconnecting it. Task manager also behave strangely when moving a panel to
a different monitor.

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

[kscreenlocker] [Bug 481308] screen locker blank-with-cursor [xorg]

[Nelson]

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

--- Comment #24 from Nelson  ---
(In reply to Jakob Petsovits from comment #20)
> So, quick recap:
> 
> - It's not specific to any GPU vendor. We have all three of Intel, AMD and
> Nvidia reported.
> - It's not specific to having monitors or laptop displays.
> - It's not specific to Arch Linux, as KDE neon also gets a mention.
> 
> With such a wide range of scenarios covered, it feels like reproducing this
> should be straightforward except for me it's not. If any other KDE developer
> experiences this on their system, please get in touch. 
> 
> Thanks everyone for chiming in with system configurations. Just to make
> sure, the trick from the corresponding (now fixed) Wayland bug doesn't help
> here, where you press Esc twice to make the display come back? (once to hide
> the screen locker and properly turn off the screen, the second time to bring
> it back)

For me, all that does is shut down the monitor again, so I have to move the
cursor for it to wake up again and eventually get the blank screen.
Also doesn't seem to do anything once I unlock the screen and get another blank
(desktop) screen where the monitor shuts down. Meta key eventually does brink
the screen back, though (~10-15 seconds later).

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

[dolphin] [Bug 481506] [X11, qt 6.7 beta 3 ] Open Terminal Here in Dolphin crashes konsole

[Nelson]

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

Nelson  changed:

   What|Removed |Added

 CC||dubh...@yandex.com

--- Comment #3 from Nelson  ---
(In reply to pmargeti34 from comment #2)
> ~ ▶ export QT_DEBUG_PLUGINS=1
> ~ ▶ dolphin
> Detected locale "C" with character encoding "ANSI_X3.4-1968", which is not
> UTF-8.
> Qt depends on a UTF-8 locale, and has switched to "C.UTF-8" instead.
> If this causes problems, reconfigure your locale. See the locale(1) manual
> for more information.
> qt.qpa.xcb: could not connect to display 
> qt.qpa.plugin: From 6.5.0, xcb-cursor0 or libxcb-cursor0 is needed to load
> the Qt xcb platform plugin.
> qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though
> it was found.
> This application failed to start because no Qt platform plugin could be
> initialized. Reinstalling the application may fix this problem.
> 
> Available platform plugins are: eglfs, linuxfb, minimal, minimalegl,
> offscreen, vkkhrdisplay, vnc, xcb, wayland-egl, wayland.

Got the same problem with the same output. KDE Neon 6.0.0. X11.

I use a button on the Dolphin panel to open terminals in the current directory.
Found the bug when that button no longer did anything.
I assume it's the exact same as using the context menu.

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

[dolphin] [Bug 481952] On X11, panels are hidden after minimizing Dolphin window

[Nelson]

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

Nelson  changed:

   What|Removed |Added

 CC||dubh...@yandex.com

--- Comment #13 from Nelson  ---
I confirm to having the same issue. Under KDE Neon 6.0.0, X11, NVIDIA card (if
it helps).
This bug was driving me crazy by how random it seemed, as I didn't realize it
was caused by minimizing Dolphin.
Now I can reproduce it every time.

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

[plasmashell] [Bug 482339] Tasks Show on left most screen as well as the correct screen but and only be clicked on on the left most screen

[Bradley Nelson]

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

--- Comment #4 from Bradley Nelson  ---
Restarting plasmashell fixes it until the next sleep

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

[plasmashell] [Bug 482339] Tasks Show on left most screen as well as the correct screen but and only be clicked on on the left most screen

[Bradley Nelson]

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

Bradley Nelson  changed:

   What|Removed |Added

 Attachment #166373|0   |1
is obsolete||

--- Comment #3 from Bradley Nelson  ---
Created attachment 166375
  --> https://bugs.kde.org/attachment.cgi?id=166375=edit
Display Config

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

[plasmashell] [Bug 482339] Tasks Show on left most screen as well as the correct screen but and only be clicked on on the left most screen

[Bradley Nelson]

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

Bradley Nelson  changed:

   What|Removed |Added

 Attachment #166372|0   |1
is obsolete||

--- Comment #2 from Bradley Nelson  ---
Created attachment 166374
  --> https://bugs.kde.org/attachment.cgi?id=166374=edit
Screenshot with some notes

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

[plasmashell] [Bug 482339] Tasks Show on left most screen as well as the correct screen but and only be clicked on on the left most screen

[Bradley Nelson]

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

--- Comment #1 from Bradley Nelson  ---
Created attachment 166373
  --> https://bugs.kde.org/attachment.cgi?id=166373=edit
Display Config

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

[plasmashell] [Bug 482339] New: Tasks Show on left most screen as well as the correct screen but and only be clicked on on the left most screen

[Bradley Nelson]

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

Bug ID: 482339
   Summary: Tasks Show on left most screen as well as the correct
screen but and only be clicked on on the left most
screen
Classification: Plasma
   Product: plasmashell
   Version: 6.0.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Task Manager and Icons-Only Task Manager
  Assignee: plasma-b...@kde.org
  Reporter: bradleynelson...@gmail.com
CC: qydwhotm...@gmail.com
  Target Milestone: 1.0

Created attachment 166372
  --> https://bugs.kde.org/attachment.cgi?id=166372=edit
Screenshot with some notes

SUMMARY

Tasks show on the wrong screen as well as the expected screen but can't be
click on the correct screen


STEPS TO REPRODUCE
1. Configure multiple monitors 
2. Add a panel with a task bar to each monitor
3. set task bar to only show tasks from current screen.
4. wait for session go to sleep
5. Wake it up

OBSERVED RESULT
The panel on the left most screen shows all tasks. Tasks are still shown on
other screens but can't be left clicked to activate the application or right
click for more options.

EXPECTED RESULT
Tasks are only shown when on that screen and can be clicked to activate.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Nixos Unstable
(available in About System)
KDE Plasma Version: 6.0.0
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2



ADDITIONAL INFORMATION

Copy Details from about system
Operating System: NixOS 24.05
KDE Plasma Version: 6.0.0
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.6.18 (64-bit)
Graphics Platform: Wayland
Processors: 20 × 12th Gen Intel® Core™ i7-12700KF
Memory: 31.2 GiB of RAM
Graphics Processor: AMD Radeon RX 6650 XT


Display configuration
Three Screens with the center one being set to primary

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

[kjots] [Bug 482305] Cannot install Kjots in KDE 6, dependency issue

[Nelson]

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

Nelson  changed:

   What|Removed |Added

 CC||dubh...@yandex.com

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

[kjots] [Bug 482305] New: Cannot install Kjots in KDE 6, dependency issue

[Nelson]

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

Bug ID: 482305
   Summary: Cannot install Kjots in KDE 6, dependency issue
Classification: Applications
   Product: kjots
   Version: 5.1.0
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: igor.pobo...@gmail.com
  Reporter: dubh...@yandex.com
  Target Milestone: ---

SUMMARY
On both a brand new KDE Neon installation and an updated KDE 5 to KDE 6 system,
Kjots cannot be installed due to a dependency problem.
Looks to me like Kjots is still looking for a KDE 5 package which may no longer
be available.

STEPS TO REPRODUCE
1. On KDE Neon, "sudo apt install kjots"

OBSERVED RESULT
---
(...)
Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) libkf5pimtextedit5abi3:amd64 < none -> 21.12.3-0ubuntu1 @un
puN Ib >
Broken libkf5pimtextedit5abi3:amd64 Depends on libkf5pimtextedit-data:amd64 <
none | 24.02.0-0xneon+22.04+jammy+release+build41 @un uH > (= 21.12.3-0ubuntu1)
  Considering libkf5pimtextedit-data:amd64 0 as a solution to
libkf5pimtextedit5abi3:amd64 0
  Re-Instated libqt6keychain1:amd64
  Re-Instated kf6-ktextaddons:amd64
  Re-Instated kpim6-kpimtextedit:amd64
  Re-Instated libkf5pimtextedit-data:amd64
(...)
The following packages have unmet dependencies:
libkf5pimtextedit5abi3 : Depends: libkf5pimtextedit-data (= 21.12.3-0ubuntu1)
---

EXPECTED RESULT
Kjots would install and open normally.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE Neon
KDE Plasma Version: 6.0.0
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2

ADDITIONAL INFORMATION
On the Neon system that was updated, Kjots was already installed but would no
longer open. The only feedback was available when trying to open it through the
terminal, but I did not take note of what it was before removing Kjots and
trying to re-install it.

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

[kscreenlocker] [Bug 482054] Monitor sleep and black screen on screen lock and after unlocking on X11

[Nelson]

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

--- Comment #3 from Nelson  ---
(In reply to pmargeti34 from comment #2)
> 
> *** This bug has been marked as a duplicate of bug 481308 ***

For what it's worth, I see one difference with the bug this has been marked a
duplicate of, and that's that the other user's monitor does not seem to go into
sleep mode when locking nor unlocking.

That might be related to the monitor, but it wasn't the observed behavior when
locking the screen up to 5.27. I would just see the lock screen.

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

[kscreenlocker] [Bug 482054] New: Monitor sleep and black screen on screen lock and after unlocking on X11

[Nelson]

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

Bug ID: 482054
   Summary: Monitor sleep and black screen on screen lock and
after unlocking on X11
Classification: Plasma
   Product: kscreenlocker
   Version: unspecified
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: dubh...@yandex.com
  Target Milestone: ---

SUMMARY
After updating to KDE 6, when I lock the screen, either manually with the
hotkey or letting it happen after the set time, the monitor goes into sleep
mode. If I move the mouse, the monitor wakes up and I can see the cursor on a
black screen. The controls are there and the cursor changes to the text cursor
where the password field is supposed to be. 

Entering the password unlocks the screen, but the monitor again goes into sleep
mode. After moving the cursor, it wakes up and I'm on a black screen on the
desktop where the cursor changes upon hovering over windows and such, as if
everything is there, but anything that's not the mouse cursor is black. 

It seems pressing some keys affects this issue, as pressing meta on the lock
screen makes the image come back after ~5-10 seconds.
Same with unlocking, where triggering the overview feature or pressing meta,
which opens the menu, bring the image back. These workarounds, however, don't
prevent the monitor from going into sleep mode when lock is triggered or
unlocked, as mentioned above.

STEPS TO REPRODUCE
1. Let the screen lock itself or do it manually with the hotkey
2. Move the cursor or press a key to wake up the monitor

OBSERVED RESULT
The monitor goes into sleep mode instead of showing the lock screen.
After waking up, there's a black screen with only the cursor visible.
Upon unlocking, monitor sleeps again and wakes up to black, unlocked screen.

EXPECTED RESULT
Monitor does not sleep when locking the screen.
Can see lock screen.
Monitor does not sleep after unlocking.
Can see desktop right away.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Neon
KDE Plasma Version: 6.0.0
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2

ADDITIONAL INFORMATION
I tested this on Wayland and it does not happen.
This did not happen on KDE 5.27 on X11 either.
Disabling and re-enabling compositing with alt+shift+F12 does return the screen
to normal immediately, but after ~10 seconds, there's a fading-from-black
effect as if the screen had been black just the same.
Moving the cursor to a corner to trigger overview does bring the image back,
but it's promptly taken away, and only remains after a few tries (probably
while the ~10 seconds are elapsing).

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

[konsole] [Bug 476378] New: Konsole Layouts

[Nelson Fonseca]

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

Bug ID: 476378
   Summary: Konsole Layouts
Classification: Applications
   Product: konsole
   Version: unspecified
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: split-view
  Assignee: konsole-de...@kde.org
  Reporter: nelsin...@gmail.com
  Target Milestone: ---

SUMMARY
How to create Konsole Layouts including details to connect directly to a
server, for example, it could be something similar to the following .json file,
but reaching the server prompt already connected. In other words, getting
connected to a server directly once is used the Konsole Layout?

# Sample:
{
"Orientation": "Horizontal",
"Widgets": [
{
"SessionRestoreId": 0,
"commandline": "ssh nelson@server1"
},
{
"Orientation": "Vertical",
"Widgets": [
    {
"SessionRestoreId": 0,
"commandline": "ssh nelson@server2"
    },
{
"SessionRestoreId": 0,
"commandline": "ssh nelson@server3"
},
{
"SessionRestoreId": 0,
"commandline": "ssh nelson@server4"
}
]
}
]
}


STEPS TO REPRODUCE
1. Keys: Alt + F2.
2. Command: konsole --layout sample_layout.json.
3. SSH Server and Password prompt.

OBSERVED RESULT
Split view of the Konsole according to the layout only, but not servers
reached.

EXPECTED RESULT
Split view of the Konsole but also reaching the SSH servers prompt.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma:  Arch Linux + KDE Plasma
KDE Plasma Version: 5.27.9
KDE Frameworks Version: 5.111.0
Qt Version: 5.15.11
Konsole Version: 23.08.2
Date: Oct-31-2023

ADDITIONAL INFORMATION
I think it is already working as designed like it is now, but it would be a
really great enhancement, especially for being able to create Konsole Layouts
and getting connected to the servers directly. A very good example of this
could be what I can do on a Windows OS tool that is called SuperPuTTY where I
am able to reach the servers prompt by using a .xml layout file.

To many thanks, for the support. Please keep up doing the great things for KDE
Plasma and Plasma Mobile!

Kind regards,
Nelson Fonseca

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

[systemsettings] [Bug 464285] system setting crash viewing firewalld connections

[Arron David Nelson]

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

Arron David Nelson  changed:

   What|Removed |Added

Version|5.26.5  |5.27.9

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

[systemsettings] [Bug 464285] system setting crash viewing firewalld connections

[Arron David Nelson]

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

Arron David Nelson  changed:

   What|Removed |Added

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

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

[systemsettings] [Bug 464285] system setting crash viewing firewalld connections

[Arron David Nelson]

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

--- Comment #4 from Arron David Nelson  ---
Created attachment 162748
  --> https://bugs.kde.org/attachment.cgi?id=162748=edit
New crash information added by DrKonqi

systemsettings (5.27.9) using Qt 5.15.11

In "system settings"->"Firewall"->"View Connections" it crashes after about a
minute of it processing.

-- Backtrace (Reduced):
#6  QString::size() const (this=, this=) at
../../include/QtCore/../../src/corelib/text/qstring.h:277
#7  (anonymous namespace)::splitString(QString const&,
QChar const*, Qt::SplitBehavior, Qt::CaseSensitivity, int) (source=...,
sep=0x7ffc92a8bc4e, behavior=..., cs=Qt::CaseSensitive, separatorSize=1) at
text/qstring.cpp:7822
#8  0x7fc971b71911 in QString::split(QChar, QFlags,
Qt::CaseSensitivity) const (this=, sep=..., behavior=...,
behavior@entry=..., cs=cs@entry=Qt::CaseSensitive) at text/qstring.cpp:7933
#9  0x7fc96a22d1b2 in NetstatHelper::parseSSOutput(QByteArray const&)
(this=0x555ab8274bd0, netstatOutput=...) at
/usr/src/debug/plasma-firewall/plasma-firewall-5.27.9/kcm/backends/netstat/netstathelper.cpp:148
#10 NetstatHelper::stepExecuteFinished(int) (this=0x555ab8274bd0,
exitCode=) at
/usr/src/debug/plasma-firewall/plasma-firewall-5.27.9/kcm/backends/netstat/netstathelper.cpp:82

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

[systemsettings] [Bug 464285] system setting crash viewing firewalld connections

[Arron David Nelson]

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

Arron David Nelson  changed:

   What|Removed |Added

 CC||nelsonar...@outlook.com

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

[plasmashell] [Bug 412923] Global Menu on Latte panel on one activity = no menu at all on another activity

[Nelson]

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

Nelson  changed:

   What|Removed |Added

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

--- Comment #2 from Nelson  ---
(In reply to Nate Graham from comment #1)
> Hello and thank you again for the bug report! Unfortunately we were not able
> to address it yet, nor even manage to reproduce the issue ourselves. Can we
> ask you to please check if this issue is still happening with Plasma 5.27?
> 
> If it is, please change the status to REPORTED. Thanks a lot!

Good day. I have just tested it again on KDE Neon with Plasma 5.27 and indeed
it still happens.
I had forgotten about it, but I followed my own instructions and was able to
reproduce the issue.
I also tried pressing CTRL+M on programs like Dolphin to see if that makes the
menu show up; but it does not.

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

[plasmashell] [Bug 471642] Severe memory leak in 5.27.5 with Wayland

[lacresha nelson]

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

lacresha nelson  changed:

   What|Removed |Added

 CC||lacreshanelson1...@gmail.co
   ||m
 Attachment #159983|image/png   |text/plain
  mime type||
 Attachment #159983|0   |1
is obsolete||
 Attachment #159983|0   |1
   is patch||

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

[amarok] [Bug 397184] Amarok corrupts ogg files

[lacresha nelson]

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

lacresha nelson  changed:

   What|Removed |Added

 CC||lacreshanelson1...@gmail.co
   ||m

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

[Elisa] [Bug 468987] Elisa scan not picking up files from NTFS partition

[Kris Nelson]

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

Kris Nelson  changed:

   What|Removed |Added

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

--- Comment #4 from Kris Nelson  ---
Found out that I should have switched the status back to "reported" along with
my last reply, so doing that now.

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

[Elisa] [Bug 468987] Elisa scan not picking up files from NTFS partition

[Kris Nelson]

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

--- Comment #3 from Kris Nelson  ---
Created attachment 158468
  --> https://bugs.kde.org/attachment.cgi?id=158468=edit
Successful scan after changing to "scan the filesystem directly"

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

[Elisa] [Bug 468987] Elisa scan not picking up files from NTFS partition

[Kris Nelson]

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

--- Comment #2 from Kris Nelson  ---
(In reply to Nate Graham from comment #1)
> If you switch to the "Scan the filesystem directly" indexer and restart
> Elisa, does it find your music files?

Just tested that, and yes it did find everything expected from the Music folder
(attached screenshot confirmation - "elisa - scan the filesystem directly
result.png").

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

[telepathy] [Bug 354130] Telepathy can't connect to a Jabber account anymore

[Nelson Fonseca]

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

Nelson Fonseca  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|RESOLVED|REOPENED
 Resolution|WORKSFORME  |---
 CC||nelsin...@gmail.com

--- Comment #37 from Nelson Fonseca  ---
Hi There,

The error persists even with the last version recently updated. The following
details of my Arch Linux version and the telepathy packages that I have
installed:

Operating System: Arch Linux 
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.105.0
Qt Version: 5.15.9
Kernel Version: 6.2.11-arch1-1 (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5-2400 CPU @ 3.10GHz
Memory: 31.3 GiB of RAM
Graphics Processor: AMD BARTS
Manufacturer: Apple Inc.
Product Name: iMac12,2
System Version: 1.0

❯ yay -Qs telepathy
local/telepathy-accounts-signon 2.1-3
local/telepathy-farstream 0.6.2-7
local/telepathy-gabble 0.18.4-4 (telepathy)
local/telepathy-glib 0.24.2-2
local/telepathy-haze 0.8.1-1 (telepathy)
local/telepathy-idle 0.2.2-1 (telepathy)
local/telepathy-kde-accounts-kcm 22.12.3-1 (kde-applications kde-network
telepathy-kde)
local/telepathy-kde-approver 22.12.3-1 (kde-applications kde-network
telepathy-kde)
local/telepathy-kde-auth-handler 22.12.3-1 (kde-applications kde-network
telepathy-kde)
local/telepathy-kde-call-ui 22.12.3-1 (kde-applications kde-network
telepathy-kde)
local/telepathy-kde-common-internals 22.12.3-1 (kde-applications kde-network
telepathy-kde)
local/telepathy-kde-contact-list 22.12.3-1 (kde-applications kde-network
telepathy-kde)
local/telepathy-kde-contact-runner 22.12.3-1 (kde-applications kde-network
telepathy-kde)
local/telepathy-kde-desktop-applets 22.12.3-1 (kde-applications kde-network
telepathy-kde)
local/telepathy-kde-filetransfer-handler 22.12.3-1 (kde-applications
kde-network telepathy-kde)
local/telepathy-kde-integration-module 22.12.3-1 (kde-applications kde-network
telepathy-kde)
local/telepathy-kde-send-file 22.12.3-1 (kde-applications kde-network
telepathy-kde)
local/telepathy-kde-text-ui 22.12.3-1 (kde-applications kde-network
telepathy-kde)
local/telepathy-logger 0.8.2-5
local/telepathy-logger-qt 17.09.0-1
local/telepathy-mission-control 5.16.6-2
local/telepathy-morse 0.1.0-3
local/telepathy-qt 0.9.8-2
local/telepathy-salut 0.8.1-7 (telepathy)

ERRORS:
- There was a problem while trying to connect nelsin...@kdetalk.net - An
unknown error was encountered (org.freedesktop.DBus.Error.Failed), please
report this
- There was a problem while trying to connect google8 - An unknown error was
encountered (org.freedesktop.DBus.Error.Failed), please report this

KSystemlog:
4/16/23 12:39 PMplasmashell ktp-common-internals: Current presence
changed: "offline" ""
4/16/23 12:39 PMplasmashell ktp-common-internals: Requested
presence changed: "available" ""
4/16/23 12:39 PMplasmashell ktp-common-internals: Presence
changing: true
4/16/23 12:39 PMplasmashell ktp-common-internals: Account
"gabble/jabber/google_2dim_8" enabled: true
4/16/23 12:39 PMplasmashell ktp-common-internals: Account
"gabble/jabber/ktp_2dkde_2dtalk_2dim_7" enabled: true
4/16/23 12:39 PMplasmashell ktp-models: Creating a new Account from
account: Tp::Account(0x5557b508a8c0)
4/16/23 12:39 PMplasmashell ktp-models: Account not already in
model. Create new Account from account: Tp::Account(0x5557b508a8c0)
4/16/23 12:39 PMplasmashell ktp-models: Creating a new Account from
account: Tp::Account(0x5557b834d690)
4/16/23 12:39 PMplasmashell ktp-models: Account not already in
model. Create new Account from account: Tp::Account(0x5557b834d690)


Thanks a lot for the support!

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

[Falkon] [Bug 467653] New: Falkon crashes when opening the file picker

[Nelson]

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

Bug ID: 467653
   Summary: Falkon crashes when opening the file picker
Classification: Applications
   Product: Falkon
   Version: 22.12.3
  Platform: Neon
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: now...@gmail.com
  Reporter: dubh...@yandex.com
  Target Milestone: ---

Application: falkon (22.12.3)

Qt Version: 5.15.8
Frameworks Version: 5.104.0
Operating System: Linux 5.19.0-35-generic x86_64
Windowing System: X11
Distribution: KDE neon 5.27
DrKonqi: 5.27.3 [KCrashBackend]

-- Information about the crash:
Selecting the menu option to open a file crashes the program. Seems to be
related to the file picker, as the crash also happens when trying to open or
save a file on Okular, Gwenview, Kate and Krita, among others.

The crash can be reproduced every time.

-- Backtrace:
Application: Falkon (falkon), signal: Aborted

[KCrash Handler]
#4  __pthread_kill_implementation (no_tid=0, signo=6, threadid=139899944692032)
at ./nptl/pthread_kill.c:44
#5  __pthread_kill_internal (signo=6, threadid=139899944692032) at
./nptl/pthread_kill.c:78
#6  __GI___pthread_kill (threadid=139899944692032, signo=signo@entry=6) at
./nptl/pthread_kill.c:89
#7  0x7f3d09e42476 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#8  0x7f3d09e287f3 in __GI_abort () at ./stdlib/abort.c:79
#9  0x7f3d0a2a2bbe in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6
#10 0x7f3d0a2ae24c in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6
#11 0x7f3d0a2ae2b7 in std::terminate() () from
/lib/x86_64-linux-gnu/libstdc++.so.6
#12 0x7f3d0a2ae518 in __cxa_throw () from
/lib/x86_64-linux-gnu/libstdc++.so.6
#13 0x7f3d0a690f85 in qBadAlloc () at global/qglobal.cpp:3371
#14 0x7f3d0a6969a3 in QString::reallocData (this=this@entry=0x7ffee8964578,
alloc=1073742055, grow=grow@entry=false) at text/qstring.cpp:2367
#15 0x7f3d0a83894e in QString::reserve (asize=1073742054,
this=0x7ffee8964578) at
../../include/QtCore/../../src/corelib/text/qstring.h:1316
#16 QConfFileSettingsPrivate::readIniSection (section=..., data=...,
settingsMap=, codec=) at io/qsettings.cpp:1760
#17 0x7f3d0a838be4 in QConfFileSettingsPrivate::ensureAllSectionsParsed
(this=this@entry=0x560ef8d001a0, confFile=confFile@entry=0x560ef8d00290) at
io/qsettings.cpp:1915
#18 0x7f3d0a83ae96 in QConfFileSettingsPrivate::children
(spec=QSettingsPrivate::ChildGroups, prefix=..., this=0x560ef8d001a0) at
io/qsettings.cpp:1318
#19 QSettings::childGroups (this=this@entry=0x7ffee8964750) at
io/qsettings.cpp:3232
#20 0x7f3d0af91c4a in QFileDialogPrivate::restoreFromSettings
(this=this@entry=0x560ef5120ae0) at dialogs/qfiledialog.cpp:2951
#21 0x7f3d0af93bb7 in QFileDialogPrivate::init (this=0x560ef5120ae0,
args=...) at dialogs/qfiledialog.cpp:3060
#22 0x7f3d0af94b71 in QFileDialog::QFileDialog (this=0x7ffee89648f0,
args=...) at dialogs/qfiledialog.cpp:393
#23 0x7f3d0af94c36 in QFileDialog::getOpenFileUrl
(parent=parent@entry=0x560ef724b6c0, caption=..., dir=..., filter=...,
selectedFilter=selectedFilter@entry=0x0, options=..., supportedSchemes=...) at
dialogs/qfiledialog.cpp:2262
#24 0x7f3d0af94f06 in QFileDialog::getOpenFileName
(parent=parent@entry=0x560ef724b6c0, caption=..., dir=..., filter=...,
selectedFilter=selectedFilter@entry=0x0, options=...) at
dialogs/qfiledialog.cpp:2213
#25 0x7f3d0b6a42df in QzTools::getOpenFileName (name=...,
parent=parent@entry=0x560ef724b6c0, caption=..., dir=..., filter=...,
selectedFilter=0x0, options=...) at ./src/lib/tools/qztools.cpp:672
#26 0x7f3d0b5379aa in BrowserWindow::openFile (this=0x560ef724b6c0) at
./src/lib/app/browserwindow.cpp:1161
#27 0x7f3d0a8c74ab in QMetaMethod::invoke (this=,
object=0x560ef724b6c0, connectionType=Qt::DirectConnection, returnValue=...,
val0=..., val1=..., val2=..., val3=..., val4=..., val5=..., val6=..., val7=...,
val8=..., val9=...) at kernel/qmetaobject.cpp:2310
#28 0x7f3d0a8cc656 in QMetaObject::invokeMethod (obj=0x560ef724b6c0,
member=0x7f3d0b6f7b62 "openFile", type=type@entry=Qt::AutoConnection, ret=...,
val0=..., val1=..., val2=..., val3=..., val4=..., val5=..., val6=..., val7=...,
val8=..., val9=...) at kernel/qmetaobject.cpp:1522
#29 0x7f3d0b54c4f4 in QMetaObject::invokeMethod (val9=..., val8=...,
val7=..., val6=..., val5=..., val4=..., val3=..., val2=..., val1=..., val0=...,
member=, obj=) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs.h:460
#30 MainMenu::callSlot (this=, slot=) at
./src/lib/app/mainmenu.cpp:670
#31 0x7f3d0a8f4108 in doActivate (sender=0x560ef777c760,
signal_index=4, argv=0x7ffee8965370) at kernel/qobject.cpp:3935
#32 0x7f3d0a8ed177 in QMetaObject::activate
(sender=sender@entry=0x560ef777c760, m=m@entry=0x7f3d0b295d40
, local_signal_index=local_signal_index@entry=1,

[Elisa] [Bug 458090] Elisa start problem

[Nelson Fonseca]

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

Nelson Fonseca  changed:

   What|Removed |Added

 CC||nelsin...@gmail.com

--- Comment #5 from Nelson Fonseca  ---
Hi all,

I do have the same issue on my Arch Linux. How was it resolved?

Thanks a lot!

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

[Discover] [Bug 464684] Discover crashes on close

[Katie Marie Nelson]

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

--- Comment #64 from Katie Marie Nelson  ---
katie@Node-11:~$ sudo -i
[sudo] password for katie:
root@Node-11:~# gdb plasma-discover 6103
GNU gdb (Ubuntu 12.1-0ubuntu1~22.04) 12.1
Copyright (C) 2022 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
"/root/plasma-discover": not in executable format: file format not 
recognized
Attaching to process 6103
[New LWP 6104]
[New LWP 6105]
[New LWP 6107]
[New LWP 6113]
[New LWP 6114]
[New LWP 6116]
[New LWP 6126]
[New LWP 6127]
[New LWP 6130]
[New LWP 6131]
[New LWP 6152]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7fa58144cd7fin __GI___poll(fds=0x55f5c18f2770, nfds=5, 
timeout=324) at ../sysdeps/unix/sysv/linux/poll.c:29
29  ../sysdeps/unix/sysv/linux/poll.c: No such file or directory.
(gdb) backtrace
#0 0x7fa58144cd7fin __GI___poll(fds=0x55f5c18f2770, nfds=5, 
timeout=324) at ../sysdeps/unix/sysv/linux/poll.c:29
#1 0x7fa58038a666in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x7fa580e3in g_main_context_iteration() at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x7fa581a990b8in 
QEventDispatcherGlib::processEvents(QFlags)() 
at /lib/x86_64-linux-gnu/libQt5Core.so.5
#4 0x7fa581a3e75bin 
QEventLoop::exec(QFlags)() at 
/lib/x86_64-linux-gnu/libQt5Core.so.5
#5 0x7fa581a46cf4in QCoreApplication::exec()() at 
/lib/x86_64-linux-gnu/libQt5Core.so.5
#6 0x55f5bef98838in  ()
#7 0x7fa58135dd90in 
__libc_start_call_main(main=main@entry=0x55f5bef97f40, 
argc=argc@entry=3, argv=argv@entry=0x7ffc2651bf18) at 
../sysdeps/nptl/libc_start_call_main.h:58
#8 0x7fa58135de40in __libc_start_main_impl
 (main=0x55f5bef97f40, argc=3, argv=0x7ffc2651bf18, init=, fini=, rtld_fini=, 
stack_end=0x7ffc2651bf08) at ../csu/libc-start.c:392
#9 0x55f5bef99275in  ()
(gdb) exit
A debugging session is active.

    Inferior 1 [process 6103] will be detached.

Quit anyway? (y or n) n
Not confirmed.
(gdb) continue
Continuing.
Couldn't get registers: No such process.
(gdb) [Thread 0x7fa52d3fa640 (LWP 6152) exited]
[Thread 0x7fa52ebfd640 (LWP 6131) exited]
[Thread 0x7fa52f3fe640 (LWP 6130) exited]
[Thread 0x7fa5377fe640 (LWP 6127) exited]
[Thread 0x7fa537fff640 (LWP 6126) exited]
[Thread 0x7fa55dffb640 (LWP 6116) exited]
[Thread 0x7fa55effd640 (LWP 6114) exited]
[Thread 0x7fa55f7fe640 (LWP 6113) exited]
[Thread 0x7fa578aff640 (LWP 6107) exited]
[Thread 0x7fa57ac42640 (LWP 6105) exited]
[Thread 0x7fa57bb9b640 (LWP 6104) exited]

Program terminated with signal SIGKILL, Killed.
The program no longer exists.
Quit
(gdb)


On 1/26/23 03:36, Katie Nelson wrote:
> ed 2023-01-25 06:42:34 CST  8642 1000 1000 SIGSEGV present 
>  /usr/bin/plasma-discover

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

[Discover] [Bug 464684] Discover crashes on close

[Katie Marie Nelson]

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

--- Comment #63 from Katie Marie Nelson  ---
katie@Node-11:~$ coredumpctl
TIME  PID  UID  GID SIG COREFILE EXE 
    SIZE
Wed 2023-01-25 02:42:41 CST 68104 1000 1000 SIGSEGV present 
  /usr/bin/plasma-discover  13.9M
Wed 2023-01-25 03:07:13 CST  4843 1000 1000 SIGSEGV present 
  /usr/libexec/xdg-desktop-portal  434.3K
Wed 2023-01-25 06:42:34 CST  8642 1000 1000 SIGSEGV present 
  /usr/bin/plasma-discover  29.8M
Wed 2023-01-25 08:17:38 CST 17966 1000 1000 SIGSEGV present 
  /usr/lib/virtualbox/VirtualBoxVM  12.1M
Wed 2023-01-25 08:29:26 CST  4586 1000 1000 SIGSEGV present 
  /usr/libexec/xdg-desktop-portal  421.7K
Wed 2023-01-25 09:48:46 CST 27481 1000 1000 SIGABRT present 
  /usr/lib/x86_64-linux-gnu/libexec/drkonqi    615.8K
Wed 2023-01-25 09:48:47 CST  4651 1000 1000 SIGSEGV present 
  /usr/lib/x86_64-linux-gnu/libexec/xdg-desktop-portal-kde   6.9M
Wed 2023-01-25 09:54:07 CST 29458 1000 1000 SIGSEGV present 
  /usr/bin/conky   791.7K
Wed 2023-01-25 09:57:35 CST 30940 1000 1000 SIGSEGV present 
  /usr/bin/conky   764.6K
Wed 2023-01-25 09:57:49 CST 30991 1000 1000 SIGSEGV present 
  /usr/bin/conky   766.0K
Wed 2023-01-25 09:58:36 CST 31154 1000 1000 SIGABRT present 
  /usr/bin/conky   672.5K
Wed 2023-01-25 09:58:40 CST 31168 1000 1000 SIGABRT present 
  /usr/bin/conky   683.4K
Wed 2023-01-25 09:58:42 CST 31182 1000 1000 SIGABRT present 
  /usr/bin/conky   683.6K
Wed 2023-01-25 09:58:45 CST 31196 1000 1000 SIGABRT present 
  /usr/bin/conky   675.0K
Wed 2023-01-25 09:58:48 CST 31210 1000 1000 SIGABRT present 
  /usr/bin/conky   675.6K
Wed 2023-01-25 09:58:59 CST 31262 1000 1000 SIGABRT present 
  /usr/bin/conky   681.6K
Wed 2023-01-25 09:59:03 CST 31276 1000 1000 SIGABRT present 
  /usr/bin/conky   682.4K
Wed 2023-01-25 10:01:25 CST 32026 1000 1000 SIGABRT present 
  /usr/bin/conky   732.1K
Wed 2023-01-25 10:01:48 CST 32062 1000 1000 SIGABRT present 
  /usr/bin/conky   743.6K
Wed 2023-01-25 10:01:58 CST 32094 1000 1000 SIGABRT present 
  /usr/bin/conky   739.6K
Wed 2023-01-25 10:02:04 CST 32125 1000 1000 SIGABRT present 
  /usr/bin/conky   722.9K
Wed 2023-01-25 10:02:08 CST 32153 1000 1000 SIGABRT present 
  /usr/bin/conky   723.2K
Wed 2023-01-25 10:02:18 CST 32209 1000 1000 SIGABRT present 
  /usr/bin/conky   733.3K
Wed 2023-01-25 10:02:29 CST 32245 1000 1000 SIGABRT present 
  /usr/bin/conky   732.4K
Wed 2023-01-25 10:34:26 CST 39931 1000 1000 SIGABRT present 
  /usr/bin/conky   682.2K
Wed 2023-01-25 10:35:39 CST 40026 1000 1000 SIGSEGV present 
  /usr/bin/conky   765.4K
Wed 2023-01-25 13:01:26 CST  8257 1000 1000 SIGSEGV present 
  /usr/bin/conky   783.5K
Wed 2023-01-25 19:59:46 CST  4517 1000 1000 SIGSEGV present 
  /usr/libexec/xdg-desktop-portal  441.1K
Thu 2023-01-26 03:30:26 CST 11669 1000 1000 SIGSEGV present 
  /usr/bin/plasma-discover  29.3M
katie@Node-11:~$ coredumpctl gdb 11669
   PID: 11669(plasma-discover)
   UID: 1000 (katie)
   GID: 1000 (katie)
    Signal: 11 (SEGV)
 Timestamp: Thu 2023-01-26 03:30:25 CST (3min 35s ago)
  Command Line: /usr/bin/plasma-discover --mode update
    Executable: /usr/bin/plasma-discover
Control Group: 
/user.slice/user-1000.slice/user@1000.service/app.slice/app-org.kde.discover-aea30f19db344212af0120249d8f8b4e.scope
  Unit: user@1000.service
 User Unit: app-org.kde.discover-aea30f19db344212af0120249d8f8b4e.scope
 Slice: user-1000.slice
 Owner UID: 1000 (katie)
   Boot ID: 4e43bc43f5684cc3be02961b326b768f
    Machine ID: 870004348a19485188bee6d65dcbe47b
  Hostname: Node-11
   Storage: 
/var/lib/systemd/coredump/core.plasma-discover.1000.4e43bc43f5684cc3be02961b326b768f.11669.167472542500.zst
 
(present)
 Disk Size: 29.3M
   Message: Process 11669 (plasma-discover) of user 1000 dumped core.

    Found module 
/usr/lib/x86_64-linux-gnu/libkrb5support.so.0.1 (deleted

[Discover] [Bug 464684] Discover crashes on close

[Katie Marie Nelson]

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

--- Comment #62 from Katie Marie Nelson  ---
I need specific instructions to get a backtrace. I can't replicate this 
using the gnome debugger tool.
I did get that installed though. This only happens when the system tray 
notifier shows updates available.
It doesn't matter whether I click the tray icon or go into the start 
menu to launch discover. After installing
all updates and then closing discover is when this happens. If I had 
specific instructions before I closed
the app??

On 1/25/23 10:53, Nate Graham wrote:
> https://bugs.kde.org/show_bug.cgi?id=464684
>
> --- Comment #61 from Nate Graham  ---
> I'm afraid attaching all these images is not super helpful. If you're having
> trouble getting a backtrace for the crash, I would recommend asking for help 
> in
> a Kubuntu-specific venue.
>

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

[Discover] [Bug 464684] Discover crashes on close

[Katie Marie Nelson]

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

--- Comment #54 from Katie Marie Nelson  ---
Created attachment 155619
  --> https://bugs.kde.org/attachment.cgi?id=155619=edit
xR7KhXip6CXEKtgE.png

--- Comment #55 from Katie Marie Nelson  ---
Created attachment 155620
  --> https://bugs.kde.org/attachment.cgi?id=155620=edit
JetFe0sgblN6Rr0e.png

--- Comment #56 from Katie Marie Nelson  ---
Created attachment 155621
  --> https://bugs.kde.org/attachment.cgi?id=155621=edit
p0MC0l0qh0yty31j.png

--- Comment #57 from Katie Marie Nelson  ---
Created attachment 155622
  --> https://bugs.kde.org/attachment.cgi?id=155622=edit
MO4R0TbpvkwLmVeb.png

--- Comment #58 from Katie Marie Nelson  ---
Created attachment 155623
  --> https://bugs.kde.org/attachment.cgi?id=155623=edit
00s375iPLaw0IyvD.png

--- Comment #59 from Katie Marie Nelson  ---
Created attachment 155624
  --> https://bugs.kde.org/attachment.cgi?id=155624=edit
Nssx8FqNRLwY8pVN.png

--- Comment #60 from Katie Marie Nelson  ---
Created attachment 155625
  --> https://bugs.kde.org/attachment.cgi?id=155625=edit
p0gNUz0hbufPpAM0.png

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

[Discover] [Bug 464684] Discover crashes on close

[Katie Marie Nelson]

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

--- Comment #53 from Katie Marie Nelson  ---
katie@Node-11:~$ gdb plasma-discover 61305
GNU gdb (Ubuntu 12.1-0ubuntu1~22.04) 12.1
Copyright (C) 2022 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from plasma-discover...
(No debugging symbols found in plasma-discover)
Attaching to program: /usr/bin/plasma-discover, process 61305
ptrace: No such process.
/home/katie/61305: No such file or directory.
(gdb) start
Function "main" not defined.
Make breakpoint pending on future shared library load? (y or [n]) y
Temporary breakpoint 1 (-qualified main) pending.
Starting program: /usr/bin/plasma-discover
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7015d640 (LWP 61530)]
[New Thread 0x7fffef204640 (LWP 61531)]
[New Thread 0x7fffed0ff640 (LWP 61533)]
qrc:/qml/DiscoverWindow.qml:116:19: QML Shortcut: Shortcut: Only binding 
to one of multiple key bindings associated with 15. Use 'sequences: [ 
 ]' to bind to all of them.
[New Thread 0x7fffdb09a640 (LWP 61534)]
[New Thread 0x7fffda899640 (LWP 61535)]
[New Thread 0x7fffda098640 (LWP 61536)]
[New Thread 0x7fffd9897640 (LWP 61537)]
qrc:/qml/DiscoverPage.qml:42:37: QML Shortcut: Shortcut: Only binding to 
one of multiple key bindings associated with 15. Use 'sequences: [  
]' to bind to all of them.
[New Thread 0x7fffd8e7f640 (LWP 61538)]
[New Thread 0x7fffc3fff640 (LWP 61540)]
[New Thread 0x7fffc37fe640 (LWP 61541)]
[New Thread 0x7fffc2ffd640 (LWP 61542)]
[New Thread 0x7fffc27fc640 (LWP 61543)]
adding empty sources model QStandardItemModel(0x56287810)
[New Thread 0x7fffc1ffb640 (LWP 61544)]
[Detaching after fork from child process 61545]
org.kde.plasma.libdiscover: Couldn't find a category for  "fwupd-backend"
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/PrivateActionToolButton.qml:75:5:
 
QML Binding: Binding loop detected for property "value"
[New Thread 0x7fffc1029640 (LWP 61547)]
[New Thread 0x7fffabfff640 (LWP 61548)]
[New Thread 0x7fff9640 (LWP 61552)]
[New Thread 0x7fff9f7fe640 (LWP 61553)]
fwupd: Device not supported: UEFI dbx No releases found: Device only 
supports version upgrades
fwupd: Device not supported: UEFI dbx
[New Thread 0x7fff9effd640 (LWP 61556)]
[New Thread 0x7fff9e7fc640 (LWP 61557)]
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:200:9:
 
QML MouseArea: Binding loop detected for property "implicitHeight"
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:200:9:
 
QML MouseArea: Binding loop detected for property "implicitHeight"
[Thread 0x7fff9e7fc640 (LWP 61557) exited]
[New Thread 0x7fff9e7fc640 (LWP 61561)]
[Thread 0x7fffc2ffd640 (LWP 61542) exited]
[Thread 0x7fff9effd640 (LWP 61556) exited]
qrc:/qml/DiscoverPage.qml:42:37: QML Shortcut: Shortcut: Only binding to 
one of multiple key bindings associated with 15. Use 'sequences: [  
]' to bind to all of them.
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/PlaceholderMessage.qml:239:5:
 
QML Heading: Binding loop detected for property "verticalAlignment"
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/PlaceholderMessage.qml:239:5:
 
QML Heading: Binding loop detected for property "verticalAlignment"
Qt Quick Layouts: Detected recursive rearrange. Aborting after two 
iterations.
Qt Quick Layouts: Detected recursive rearrange. Aborting after two 
iterations.
Qt Quick Layouts: Detected recursive rearrange. Aborting after two 
iterations.
Qt Quick Layouts: Detected recursive rearrange. Aborting after two 
iterations.
[New Thread 0x7fff9effd640 (LWP 61572)]
[Thread 0x7fffd9897640 (LWP 61537) exited]
[Thread 0x7fffda899640 (LWP 61535) exited]
[Thread 0x7fffdb09a640 (LWP 61534) exited]
[Thread 0x7fffda098640 (LWP 61536) exited]
[Thread 0x7fffd8e7f640 (LWP 61538) exited]
[New Thread 0x7fffd8e7f640 (LWP 61579)]
[New Thread 0x7fffda098640 (LWP 61580)]
[New Thread 0x7fffd9897640 (LWP 61581)]
[New Thread 0x7fffdb09a640 (LWP 61582)]
[New Thread 0x7fffc2ffd640 (LWP 61583)]
[Thread 0x7fffc1ffb640 (LWP 61544) exited]
org.kde.plasma.libdiscover: last stream isn

[Discover] [Bug 464684] Discover crashes on close

[Katie Marie Nelson]

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

--- Comment #46 from Katie Marie Nelson  ---
Created attachment 155611
  --> https://bugs.kde.org/attachment.cgi?id=155611=edit
xR7KhXip6CXEKtgE.png

--- Comment #47 from Katie Marie Nelson  ---
Created attachment 155612
  --> https://bugs.kde.org/attachment.cgi?id=155612=edit
JetFe0sgblN6Rr0e.png

--- Comment #48 from Katie Marie Nelson  ---
Created attachment 155613
  --> https://bugs.kde.org/attachment.cgi?id=155613=edit
p0MC0l0qh0yty31j.png

--- Comment #49 from Katie Marie Nelson  ---
Created attachment 155614
  --> https://bugs.kde.org/attachment.cgi?id=155614=edit
MO4R0TbpvkwLmVeb.png

--- Comment #50 from Katie Marie Nelson  ---
Created attachment 155615
  --> https://bugs.kde.org/attachment.cgi?id=155615=edit
00s375iPLaw0IyvD.png

--- Comment #51 from Katie Marie Nelson  ---
Created attachment 155616
  --> https://bugs.kde.org/attachment.cgi?id=155616=edit
Nssx8FqNRLwY8pVN.png

--- Comment #52 from Katie Marie Nelson  ---
Created attachment 155617
  --> https://bugs.kde.org/attachment.cgi?id=155617=edit
p0gNUz0hbufPpAM0.png

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

[Discover] [Bug 464684] Discover crashes on close

[Katie Marie Nelson]

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

--- Comment #45 from Katie Marie Nelson  ---
On 1/25/23 01:27, Katie Nelson wrote:
>
>
> I got gdb installed...but I'm not sure I'm running the commands correctly.
>
> On 1/25/23 01:09, Katie Nelson wrote:
>>
>> katie@Node-11:~$ sudo -i
>> [sudo] password for katie:
>> root@Node-11:~# echo "deb http://ddebs.ubuntu.com $(lsb_release -cs) 
>> main restricted universe multiverse
>> > deb http://ddebs.ubuntu.com $(lsb_release -cs)-updates main 
>> restricted universe multiverse
>> > deb http://ddebs.ubuntu.com $(lsb_release -cs)-proposed main 
>> restricted universe multiverse" | \
>> > sudo tee -a /etc/apt/sources.list.d/ddebs.list
>> deb http://ddebs.ubuntu.com jammy main restricted universe multiverse
>> deb http://ddebs.ubuntu.com jammy-updates main restricted universe 
>> multiverse
>> deb http://ddebs.ubuntu.com jammy-proposed main restricted universe 
>> multiverse
>> root@Node-11:~# sudo apt install ubuntu-dbgsym-keyring
>> Reading package lists... Done
>> Building dependency tree... Done
>> Reading state information... Done
>> The following NEW packages will be installed:
>>  ubuntu-dbgsym-keyring
>> 0 upgraded, 1 newly installed, 0 to remove and 5 not upgraded.
>> Need to get 6,876 B of archives.
>> After this operation, 23.6 kB of additional disk space will be used.
>> Get:1 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 
>> ubuntu-dbgsym-keyring all 2021.03.26 [6,876 B]
>> Fetched 6,876 B in 0s (17.5 kB/s)
>> Selecting previously unselected package ubuntu-dbgsym-keyring.
>> (Reading database ... 414488 files and directories currently installed.)
>> Preparing to unpack .../ubuntu-dbgsym-keyring_2021.03.26_all.deb ...
>> Unpacking ubuntu-dbgsym-keyring (2021.03.26) ...
>> Setting up ubuntu-dbgsym-keyring (2021.03.26) ...
>> W: Target Packages (main/binary-amd64/Packages) is configured 
>> multiple times in /etc/apt/sources.list.d/google-earth-pro.list:3 and 
>> /etc/apt/sources.list.d/google.list:1
>> W: Target Packages (main/binary-all/Packages) is configured multiple 
>> times in /etc/apt/sources.list.d/google-earth-pro.list:3 and 
>> /etc/apt/sources.list.d/google.list:1
>> W: Target Translations (main/i18n/Translation-en_US) is configured 
>> multiple times in /etc/apt/sources.list.d/google-earth-pro.list:3 and 
>> /etc/apt/sources.list.d/google.list:1
>> W: Target Translations (main/i18n/Translation-en) is configured 
>> multiple times in /etc/apt/sources.list.d/google-earth-pro.list:3 and 
>> /etc/apt/sources.list.d/google.list:1
>> W: Target DEP-11 (main/dep11/Components-amd64.yml) is configured 
>> multiple times in /etc/apt/sources.list.d/google-earth-pro.list:3 and 
>> /etc/apt/sources.list.d/google.list:1
>> W: Target DEP-11 (main/dep11/Components-all.yml) is configured 
>> multiple times in /etc/apt/sources.list.d/google-earth-pro.list:3 and 
>> /etc/apt/sources.list.d/google.list:1
>> W: Target DEP-11-icons-small (main/dep11/icons-48x48.tar) is 
>> configured multiple times in 
>> /etc/apt/sources.list.d/google-earth-pro.list:3 and 
>> /etc/apt/sources.list.d/google.list:1
>> W: Target DEP-11-icons (main/dep11/icons-64x64.tar) is configured 
>> multiple times in /etc/apt/sources.list.d/google-earth-pro.list:3 and 
>> /etc/apt/sources.list.d/google.list:1
>> W: Target DEP-11-icons-hidpi (main/dep11/icons-64...@2.tar) is 
>> configured multiple times in 
>> /etc/apt/sources.list.d/google-earth-pro.list:3 and 
>> /etc/apt/sources.list.d/google.list:1
>> W: Target DEP-11-icons-large (main/dep11/icons-128x128.tar) is 
>> configured multiple times in 
>> /etc/apt/sources.list.d/google-earth-pro.list:3 and 
>> /etc/apt/sources.list.d/google.list:1
>> W: Target Contents-deb (main/Contents-amd64) is configured multiple 
>> times in /etc/apt/sources.list.d/google-earth-pro.list:3 and 
>> /etc/apt/sources.list.d/google.list:1
>> W: Target Contents-deb (main/Contents-all) is configured multiple 
>> times in /etc/apt/sources.list.d/google-earth-pro.list:3 and 
>> /etc/apt/sources.list.d/google.list:1
>> W: Target CNF (main/cnf/Commands-amd64) is configured multiple times 
>> in /etc/apt/sources.list.d/google-earth-pro.list:3 and 
>> /etc/apt/sources.list.d/google.list:1
>> W: Target CNF (main/cnf/Commands-all) is configured multiple times in 
>> /etc/apt/sources.list.d/google-earth-pro.list:3 and 
>> /etc/apt/sources.list.d/google.list:1
>> root@Node-11:~# sudo apt update
>> Hit:1 http://us.archive.ubuntu.com/ubuntu jammy InRelease
>> H

[Discover] [Bug 464684] Discover crashes on close

[Katie Marie Nelson]

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

--- Comment #39 from Katie Marie Nelson  ---
Created attachment 155604
  --> https://bugs.kde.org/attachment.cgi?id=155604=edit
JetFe0sgblN6Rr0e.png

--- Comment #40 from Katie Marie Nelson  ---
Created attachment 155605
  --> https://bugs.kde.org/attachment.cgi?id=155605=edit
p0MC0l0qh0yty31j.png

--- Comment #41 from Katie Marie Nelson  ---
Created attachment 155606
  --> https://bugs.kde.org/attachment.cgi?id=155606=edit
MO4R0TbpvkwLmVeb.png

--- Comment #42 from Katie Marie Nelson  ---
Created attachment 155607
  --> https://bugs.kde.org/attachment.cgi?id=155607=edit
00s375iPLaw0IyvD.png

--- Comment #43 from Katie Marie Nelson  ---
Created attachment 155608
  --> https://bugs.kde.org/attachment.cgi?id=155608=edit
Nssx8FqNRLwY8pVN.png

--- Comment #44 from Katie Marie Nelson  ---
Created attachment 155609
  --> https://bugs.kde.org/attachment.cgi?id=155609=edit
p0gNUz0hbufPpAM0.png

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

[Discover] [Bug 464684] Discover crashes on close

[Katie Marie Nelson]

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

--- Comment #38 from Katie Marie Nelson  ---
I got gdb installed...but I'm not sure I'm running the commands correctly.

On 1/25/23 01:09, Katie Nelson wrote:
>
> katie@Node-11:~$ sudo -i
> [sudo] password for katie:
> root@Node-11:~# echo "deb http://ddebs.ubuntu.com $(lsb_release -cs) 
> main restricted universe multiverse
> > deb http://ddebs.ubuntu.com $(lsb_release -cs)-updates main 
> restricted universe multiverse
> > deb http://ddebs.ubuntu.com $(lsb_release -cs)-proposed main 
> restricted universe multiverse" | \
> > sudo tee -a /etc/apt/sources.list.d/ddebs.list
> deb http://ddebs.ubuntu.com jammy main restricted universe multiverse
> deb http://ddebs.ubuntu.com jammy-updates main restricted universe 
> multiverse
> deb http://ddebs.ubuntu.com jammy-proposed main restricted universe 
> multiverse
> root@Node-11:~# sudo apt install ubuntu-dbgsym-keyring
> Reading package lists... Done
> Building dependency tree... Done
> Reading state information... Done
> The following NEW packages will be installed:
>  ubuntu-dbgsym-keyring
> 0 upgraded, 1 newly installed, 0 to remove and 5 not upgraded.
> Need to get 6,876 B of archives.
> After this operation, 23.6 kB of additional disk space will be used.
> Get:1 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 
> ubuntu-dbgsym-keyring all 2021.03.26 [6,876 B]
> Fetched 6,876 B in 0s (17.5 kB/s)
> Selecting previously unselected package ubuntu-dbgsym-keyring.
> (Reading database ... 414488 files and directories currently installed.)
> Preparing to unpack .../ubuntu-dbgsym-keyring_2021.03.26_all.deb ...
> Unpacking ubuntu-dbgsym-keyring (2021.03.26) ...
> Setting up ubuntu-dbgsym-keyring (2021.03.26) ...
> W: Target Packages (main/binary-amd64/Packages) is configured multiple 
> times in /etc/apt/sources.list.d/google-earth-pro.list:3 and 
> /etc/apt/sources.list.d/google.list:1
> W: Target Packages (main/binary-all/Packages) is configured multiple 
> times in /etc/apt/sources.list.d/google-earth-pro.list:3 and 
> /etc/apt/sources.list.d/google.list:1
> W: Target Translations (main/i18n/Translation-en_US) is configured 
> multiple times in /etc/apt/sources.list.d/google-earth-pro.list:3 and 
> /etc/apt/sources.list.d/google.list:1
> W: Target Translations (main/i18n/Translation-en) is configured 
> multiple times in /etc/apt/sources.list.d/google-earth-pro.list:3 and 
> /etc/apt/sources.list.d/google.list:1
> W: Target DEP-11 (main/dep11/Components-amd64.yml) is configured 
> multiple times in /etc/apt/sources.list.d/google-earth-pro.list:3 and 
> /etc/apt/sources.list.d/google.list:1
> W: Target DEP-11 (main/dep11/Components-all.yml) is configured 
> multiple times in /etc/apt/sources.list.d/google-earth-pro.list:3 and 
> /etc/apt/sources.list.d/google.list:1
> W: Target DEP-11-icons-small (main/dep11/icons-48x48.tar) is 
> configured multiple times in 
> /etc/apt/sources.list.d/google-earth-pro.list:3 and 
> /etc/apt/sources.list.d/google.list:1
> W: Target DEP-11-icons (main/dep11/icons-64x64.tar) is configured 
> multiple times in /etc/apt/sources.list.d/google-earth-pro.list:3 and 
> /etc/apt/sources.list.d/google.list:1
> W: Target DEP-11-icons-hidpi (main/dep11/icons-64...@2.tar) is 
> configured multiple times in 
> /etc/apt/sources.list.d/google-earth-pro.list:3 and 
> /etc/apt/sources.list.d/google.list:1
> W: Target DEP-11-icons-large (main/dep11/icons-128x128.tar) is 
> configured multiple times in 
> /etc/apt/sources.list.d/google-earth-pro.list:3 and 
> /etc/apt/sources.list.d/google.list:1
> W: Target Contents-deb (main/Contents-amd64) is configured multiple 
> times in /etc/apt/sources.list.d/google-earth-pro.list:3 and 
> /etc/apt/sources.list.d/google.list:1
> W: Target Contents-deb (main/Contents-all) is configured multiple 
> times in /etc/apt/sources.list.d/google-earth-pro.list:3 and 
> /etc/apt/sources.list.d/google.list:1
> W: Target CNF (main/cnf/Commands-amd64) is configured multiple times 
> in /etc/apt/sources.list.d/google-earth-pro.list:3 and 
> /etc/apt/sources.list.d/google.list:1
> W: Target CNF (main/cnf/Commands-all) is configured multiple times in 
> /etc/apt/sources.list.d/google-earth-pro.list:3 and 
> /etc/apt/sources.list.d/google.list:1
> root@Node-11:~# sudo apt update
> Hit:1 http://us.archive.ubuntu.com/ubuntu jammy InRelease
> Hit:2 http://dl.google.com/linux/earth/deb stable InRelease
> Get:3 http://us.archive.ubuntu.com/ubuntu jammy-updates InRelease [114 
> kB]
> Get:4 http://security.ubuntu.com/ubuntu jammy-security InRelease [110 kB]
> Hit:5 https://downloads.plex.tv/repo/deb public InRelease
> Hit:6 https://www.kismetwireless.net/repos/apt/release/jammy jammy 
> InRelease
> Get:7 h

[Discover] [Bug 464684] Discover crashes on close

[Katie Marie Nelson]

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

--- Comment #32 from Katie Marie Nelson  ---
katie@Node-11:~$ sudo -i
[sudo] password for katie:
root@Node-11:~# echo "deb http://ddebs.ubuntu.com $(lsb_release -cs) 
main restricted universe multiverse
 > deb http://ddebs.ubuntu.com $(lsb_release -cs)-updates main 
restricted universe multiverse
 > deb http://ddebs.ubuntu.com $(lsb_release -cs)-proposed main 
restricted universe multiverse" | \
 > sudo tee -a /etc/apt/sources.list.d/ddebs.list
deb http://ddebs.ubuntu.com jammy main restricted universe multiverse
deb http://ddebs.ubuntu.com jammy-updates main restricted universe 
multiverse
deb http://ddebs.ubuntu.com jammy-proposed main restricted universe 
multiverse
root@Node-11:~# sudo apt install ubuntu-dbgsym-keyring
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
  ubuntu-dbgsym-keyring
0 upgraded, 1 newly installed, 0 to remove and 5 not upgraded.
Need to get 6,876 B of archives.
After this operation, 23.6 kB of additional disk space will be used.
Get:1 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 
ubuntu-dbgsym-keyring all 2021.03.26 [6,876 B]
Fetched 6,876 B in 0s (17.5 kB/s)
Selecting previously unselected package ubuntu-dbgsym-keyring.
(Reading database ... 414488 files and directories currently installed.)
Preparing to unpack .../ubuntu-dbgsym-keyring_2021.03.26_all.deb ...
Unpacking ubuntu-dbgsym-keyring (2021.03.26) ...
Setting up ubuntu-dbgsym-keyring (2021.03.26) ...
W: Target Packages (main/binary-amd64/Packages) is configured multiple 
times in /etc/apt/sources.list.d/google-earth-pro.list:3 and 
/etc/apt/sources.list.d/google.list:1
W: Target Packages (main/binary-all/Packages) is configured multiple 
times in /etc/apt/sources.list.d/google-earth-pro.list:3 and 
/etc/apt/sources.list.d/google.list:1
W: Target Translations (main/i18n/Translation-en_US) is configured 
multiple times in /etc/apt/sources.list.d/google-earth-pro.list:3 and 
/etc/apt/sources.list.d/google.list:1
W: Target Translations (main/i18n/Translation-en) is configured multiple 
times in /etc/apt/sources.list.d/google-earth-pro.list:3 and 
/etc/apt/sources.list.d/google.list:1
W: Target DEP-11 (main/dep11/Components-amd64.yml) is configured 
multiple times in /etc/apt/sources.list.d/google-earth-pro.list:3 and 
/etc/apt/sources.list.d/google.list:1
W: Target DEP-11 (main/dep11/Components-all.yml) is configured multiple 
times in /etc/apt/sources.list.d/google-earth-pro.list:3 and 
/etc/apt/sources.list.d/google.list:1
W: Target DEP-11-icons-small (main/dep11/icons-48x48.tar) is configured 
multiple times in /etc/apt/sources.list.d/google-earth-pro.list:3 and 
/etc/apt/sources.list.d/google.list:1
W: Target DEP-11-icons (main/dep11/icons-64x64.tar) is configured 
multiple times in /etc/apt/sources.list.d/google-earth-pro.list:3 and 
/etc/apt/sources.list.d/google.list:1
W: Target DEP-11-icons-hidpi (main/dep11/icons-64...@2.tar) is 
configured multiple times in 
/etc/apt/sources.list.d/google-earth-pro.list:3 and 
/etc/apt/sources.list.d/google.list:1
W: Target DEP-11-icons-large (main/dep11/icons-128x128.tar) is 
configured multiple times in 
/etc/apt/sources.list.d/google-earth-pro.list:3 and 
/etc/apt/sources.list.d/google.list:1
W: Target Contents-deb (main/Contents-amd64) is configured multiple 
times in /etc/apt/sources.list.d/google-earth-pro.list:3 and 
/etc/apt/sources.list.d/google.list:1
W: Target Contents-deb (main/Contents-all) is configured multiple times 
in /etc/apt/sources.list.d/google-earth-pro.list:3 and 
/etc/apt/sources.list.d/google.list:1
W: Target CNF (main/cnf/Commands-amd64) is configured multiple times in 
/etc/apt/sources.list.d/google-earth-pro.list:3 and 
/etc/apt/sources.list.d/google.list:1
W: Target CNF (main/cnf/Commands-all) is configured multiple times in 
/etc/apt/sources.list.d/google-earth-pro.list:3 and 
/etc/apt/sources.list.d/google.list:1
root@Node-11:~# sudo apt update
Hit:1 http://us.archive.ubuntu.com/ubuntu jammy InRelease
Hit:2 http://dl.google.com/linux/earth/deb stable InRelease
Get:3 http://us.archive.ubuntu.com/ubuntu jammy-updates InRelease [114 kB]
Get:4 http://security.ubuntu.com/ubuntu jammy-security InRelease [110 kB]
Hit:5 https://downloads.plex.tv/repo/deb public InRelease
Hit:6 https://www.kismetwireless.net/repos/apt/release/jammy jammy 
InRelease
Get:7 http://us.archive.ubuntu.com/ubuntu jammy-backports InRelease 
[99.8 kB]
Ign:8 http://ddebs.ubuntu.com jammy InRelease
Ign:9 http://ddebs.ubuntu.com jammy-updates InRelease
Hit:10 https://ppa.launchpadcontent.net/cubic-wizard/release/ubuntu 
jammy InRelease
Get:11 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 
Packages [413 kB]
Get:12 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages [834 kB]
Ign:13 http://ddebs.ubuntu.com jammy-proposed InRelease
Get:14 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd

[Discover] [Bug 464684] Discover crashes on close

[Katie Marie Nelson]

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

--- Comment #26 from Katie Marie Nelson  ---
On 1/25/23 01:03, Katie Nelson wrote:
>
>
> working on it..their info works.
>
> On 1/25/23 00:58, Katie Nelson wrote:
>>
>> It looks like a small mistake on that page but people like me are 
>> willing to help ...but get quickly discouraged when we see error 
>> messages in konsole 'oh no! Please don't crash my os!'
>>
>> On 1/25/23 00:56, Katie Nelson wrote:
>>>
>>> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl
>>>
>>>
>>> https://wiki.ubuntu.com/Debug%20Symbol%20Packages
>>>
>>>
>>>
>>> Somebody needs to update the info on that kde community page.
>>>
>>> On 1/25/23 00:47, Katie Nelson wrote:
>>>>
>>>>
>>>>
>>>> The info is not correct or something.
>>>>
>>>> On 1/24/23 12:51, Nate Graham wrote:
>>>>> https://bugs.kde.org/show_bug.cgi?id=464684
>>>>>
>>>>> Nate Graham  changed:
>>>>>
>>>>> What|Removed |Added
>>>>> 
>>>>>   Resolution|--- |BACKTRACE
>>>>>   CC||n...@kde.org
>>>>>   Status|REPORTED|NEEDSINFO
>>>>>
>>>>> --- Comment #10 from Nate Graham  ---
>>>>> Sounds like Discover did in fact crash, but it crashed on closing, so the 
>>>>> net
>>>>> effect was the same.
>>>>>
>>>>> Can you get a backtrace of the crash? See
>>>>> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl
>>>>>

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

[Discover] [Bug 464684] Discover crashes on close

[Katie Marie Nelson]

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

--- Comment #21 from Katie Marie Nelson  ---
working on it..their info works.

On 1/25/23 00:58, Katie Nelson wrote:
>
> It looks like a small mistake on that page but people like me are 
> willing to help ...but get quickly discouraged when we see error 
> messages in konsole 'oh no! Please don't crash my os!'
>
> On 1/25/23 00:56, Katie Nelson wrote:
>>
>> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl
>>
>>
>> https://wiki.ubuntu.com/Debug%20Symbol%20Packages
>>
>>
>>
>> Somebody needs to update the info on that kde community page.
>>
>> On 1/25/23 00:47, Katie Nelson wrote:
>>>
>>>
>>>
>>> The info is not correct or something.
>>>
>>> On 1/24/23 12:51, Nate Graham wrote:
>>>> https://bugs.kde.org/show_bug.cgi?id=464684
>>>>
>>>> Nate Graham  changed:
>>>>
>>>> What|Removed |Added
>>>> 
>>>>   Resolution|--- |BACKTRACE
>>>>   CC||n...@kde.org
>>>>   Status|REPORTED|NEEDSINFO
>>>>
>>>> --- Comment #10 from Nate Graham  ---
>>>> Sounds like Discover did in fact crash, but it crashed on closing, so the 
>>>> net
>>>> effect was the same.
>>>>
>>>> Can you get a backtrace of the crash? See
>>>> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl
>>>>

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

[Discover] [Bug 464684] Discover crashes on close

[Katie Marie Nelson]

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

--- Comment #18 from Katie Marie Nelson  ---
Created attachment 155582
  --> https://bugs.kde.org/attachment.cgi?id=155582=edit
00s375iPLaw0IyvD.png

--- Comment #19 from Katie Marie Nelson  ---
Created attachment 155583
  --> https://bugs.kde.org/attachment.cgi?id=155583=edit
Nssx8FqNRLwY8pVN.png

--- Comment #20 from Katie Marie Nelson  ---
Created attachment 155584
  --> https://bugs.kde.org/attachment.cgi?id=155584=edit
p0gNUz0hbufPpAM0.png

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

[Discover] [Bug 464684] Discover crashes on close

[Katie Marie Nelson]

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

--- Comment #17 from Katie Marie Nelson  ---
It looks like a small mistake on that page but people like me are 
willing to help ...but get quickly discouraged when we see error 
messages in konsole 'oh no! Please don't crash my os!'

On 1/25/23 00:56, Katie Nelson wrote:
>
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl
>
>
> https://wiki.ubuntu.com/Debug%20Symbol%20Packages
>
>
>
> Somebody needs to update the info on that kde community page.
>
> On 1/25/23 00:47, Katie Nelson wrote:
>>
>>
>>
>> The info is not correct or something.
>>
>> On 1/24/23 12:51, Nate Graham wrote:
>>> https://bugs.kde.org/show_bug.cgi?id=464684
>>>
>>> Nate Graham  changed:
>>>
>>> What|Removed |Added
>>> 
>>>   Resolution|--- |BACKTRACE
>>>   CC||n...@kde.org
>>>   Status|REPORTED|NEEDSINFO
>>>
>>> --- Comment #10 from Nate Graham  ---
>>> Sounds like Discover did in fact crash, but it crashed on closing, so the 
>>> net
>>> effect was the same.
>>>
>>> Can you get a backtrace of the crash? See
>>> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl
>>>

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

[Discover] [Bug 464684] Discover crashes on close

[Katie Marie Nelson]

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

--- Comment #13 from Katie Marie Nelson  ---
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl


https://wiki.ubuntu.com/Debug%20Symbol%20Packages



Somebody needs to update the info on that kde community page.

On 1/25/23 00:47, Katie Nelson wrote:
>
>
>
> The info is not correct or something.
>
> On 1/24/23 12:51, Nate Graham wrote:
>> https://bugs.kde.org/show_bug.cgi?id=464684
>>
>> Nate Graham  changed:
>>
>> What|Removed |Added
>> 
>>   Resolution|--- |BACKTRACE
>>   CC||n...@kde.org
>>   Status|REPORTED|NEEDSINFO
>>
>> --- Comment #10 from Nate Graham  ---
>> Sounds like Discover did in fact crash, but it crashed on closing, so the net
>> effect was the same.
>>
>> Can you get a backtrace of the crash? See
>> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl
>>

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

[Discover] [Bug 464684] Discover crashes on close

[Katie Marie Nelson]

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

--- Comment #12 from Katie Marie Nelson  ---
Created attachment 155576
  --> https://bugs.kde.org/attachment.cgi?id=155576=edit
p0gNUz0hbufPpAM0.png

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

[Discover] [Bug 464684] Discover crashes on close

[Katie Marie Nelson]

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

--- Comment #11 from Katie Marie Nelson  ---
The info is not correct or something.

On 1/24/23 12:51, Nate Graham wrote:
> https://bugs.kde.org/show_bug.cgi?id=464684
>
> Nate Graham  changed:
>
> What|Removed |Added
> 
>   Resolution|--- |BACKTRACE
>   CC||n...@kde.org
>   Status|REPORTED|NEEDSINFO
>
> --- Comment #10 from Nate Graham  ---
> Sounds like Discover did in fact crash, but it crashed on closing, so the net
> effect was the same.
>
> Can you get a backtrace of the crash? See
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl
>

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

[Discover] [Bug 464684] False positive

[Katie Marie Nelson]

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

--- Comment #9 from Katie Marie Nelson  ---
Just for testing purposes I removed all entries for my yubikey. The yubikey is
not the problem.

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

[Discover] [Bug 464684] False positive

[Katie Marie Nelson]

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

--- Comment #8 from Katie Marie Nelson  ---
After updating this morning 10:33 am 1/24/23 ...now firefox is doing the same
thing after closing normallysystem tray notification "We're sorry firefox
has closed unexpectedly.."

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

[Discover] [Bug 464684] False positive

[Katie Marie Nelson]

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

--- Comment #7 from Katie Marie Nelson  ---
commented out all entries for the yubikey in login, sudo-i, sudo, su and an
update showed after rebooting. I installed all updates and closed discover and
it did the same thing with Dr Konjia false positive saying that discover
closed unexpectedly.

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

[Discover] [Bug 464684] False positive

[Katie Marie Nelson]

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

--- Comment #6 from Katie Marie Nelson  ---
/etc/pam.d/sudo
-
#%PAM-1.0

# Set up user limits from /etc/security/limits.conf.
sessionrequired   pam_limits.so

sessionrequired   pam_env.so readenv=1 user_readenv=0
sessionrequired   pam_env.so readenv=1 envfile=/etc/default/locale
user_readenv=0

@include common-auth
auth   requiredpam_u2f.so cue
@include common-account
@include common-session-noninteractive

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

[Discover] [Bug 464684] False positive

[Katie Marie Nelson]

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

--- Comment #5 from Katie Marie Nelson  ---
/etc/pam.d/login
--
#
# The PAM configuration file for the Shadow `login' service
#

# Enforce a minimal delay in case of failure (in microseconds).
# (Replaces the `FAIL_DELAY' setting from login.defs)
# Note that other modules may require another minimal delay. (for example,
# to disable any delay, you should add the nodelay option to pam_unix)
auth   optional   pam_faildelay.so  delay=300

# Outputs an issue file prior to each login prompt (Replaces the
# ISSUE_FILE option from login.defs). Uncomment for use
# auth   required   pam_issue.so issue=/etc/issue

# Disallows other than root logins when /etc/nologin exists
# (Replaces the `NOLOGINS_FILE' option from login.defs)
auth   requisite  pam_nologin.so

# SELinux needs to be the first session rule. This ensures that any
# lingering context has been cleared. Without this it is possible
# that a module could execute code in the wrong domain.
# When the module is present, "required" would be sufficient (When SELinux
# is disabled, this returns success.)
session [success=ok ignore=ignore module_unknown=ignore default=bad]
pam_selinux.so close

# Sets the loginuid process attribute
sessionrequired pam_loginuid.so

# Prints the message of the day upon successful login.
# (Replaces the `MOTD_FILE' option in login.defs)
# This includes a dynamically generated part from /run/motd.dynamic
# and a static (admin-editable) part from /etc/motd.
sessionoptional   pam_motd.so motd=/run/motd.dynamic
sessionoptional   pam_motd.so noupdate

# SELinux needs to intervene at login time to ensure that the process
# starts in the proper default security context. Only sessions which are
# intended to run in the user's context should be run after this.
# pam_selinux.so changes the SELinux context of the used TTY and configures
# SELinux in order to transition to the user context with the next execve()
# call.
session [success=ok ignore=ignore module_unknown=ignore default=bad]
pam_selinux.so open
# When the module is present, "required" would be sufficient (When SELinux
# is disabled, this returns success.)

# This module parses environment configuration file(s)
# and also allows you to use an extended config
# file /etc/security/pam_env.conf.
# 
# parsing /etc/environment needs "readenv=1"
session   required   pam_env.so readenv=1
# locale variables are also kept into /etc/default/locale in etch
# reading this file *in addition to /etc/environment* does not hurt
session   required   pam_env.so readenv=1 envfile=/etc/default/locale

# Standard Un*x authentication.
@include common-auth
auth  requiredpam_u2f.so
# This allows certain extra groups to be granted to a user
# based on things like time of day, tty, service, and user.
# Please edit /etc/security/group.conf to fit your needs
# (Replaces the `CONSOLE_GROUPS' option in login.defs)
auth   optional   pam_group.so

# Uncomment and edit /etc/security/time.conf if you need to set
# time restraint on logins.
# (Replaces the `PORTTIME_CHECKS_ENAB' option from login.defs
# as well as /etc/porttime)
# accountrequisite  pam_time.so

# Uncomment and edit /etc/security/access.conf if you need to
# set access limits.
# (Replaces /etc/login.access file)
# account  required   pam_access.so

# Sets up user limits according to /etc/security/limits.conf
# (Replaces the use of /etc/limits in old login)
sessionrequired   pam_limits.so

# Prints the last login info upon successful login
# (Replaces the `LASTLOG_ENAB' option from login.defs)
sessionoptional   pam_lastlog.so

# Prints the status of the user's mailbox upon successful login
# (Replaces the `MAIL_CHECK_ENAB' option from login.defs). 
#
# This also defines the MAIL environment variable
# However, userdel also needs MAIL_DIR and MAIL_FILE variables
# in /etc/login.defs to make sure that removing a user 
# also removes the user's mail spool file.
# See comments in /etc/login.defs
sessionoptional   pam_mail.so standard

# Create a new session keyring.
sessionoptional   pam_keyinit.so force revoke

# Standard Un*x account and session
@include common-account
@include common-session
@include common-password

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

[Discover] [Bug 464684] False positive

[Katie Marie Nelson]

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

--- Comment #4 from Katie Marie Nelson  ---
/etc/pam.d/polkit-1
---
#%PAM-1.0

@include common-auth
auth required pam_u2f.so
@include common-account
@include common-password
session   required   pam_env.so readenv=1 user_readenv=0
session   required   pam_env.so readenv=1 envfile=/etc/default/locale
user_readenv=0
@include common-session-noninteractive

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

[Discover] [Bug 464684] False positive

[Katie Marie Nelson]

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

--- Comment #3 from Katie Marie Nelson  ---
/etc/pam.d/sudo-i
-
#%PAM-1.0

# Set up user limits from /etc/security/limits.conf.
sessionrequired   pam_limits.so

sessionrequired   pam_env.so readenv=1 user_readenv=0
sessionrequired   pam_env.so readenv=1 envfile=/etc/default/locale
user_readenv=0

@include common-auth
auth required pam_u2f.so cue
@include common-account
@include common-session

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

[Discover] [Bug 464684] False positive

[Katie Marie Nelson]

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

--- Comment #2 from Katie Marie Nelson  ---
Results of the Analyzed Crash Details

This report does not contain enough information for the developers, so the
automated bug reporting process is not enabled for this crash.

Contents of the report

Application: plasma-discover (5.24.7)

Qt Version: 5.15.3
Frameworks Version: 5.98.0
Operating System: Linux 5.15.0-58-generic x86_64
Windowing System: X11
Distribution: Ubuntu 22.04.1 LTS
DrKonqi: 5.24.5 [KCrashBackend]

-- Information about the crash:


The crash can be reproduced every time.

-- Backtrace:
A useful backtrace could not be generated

Report to https://bugs.kde.org/

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

[Discover] [Bug 464684] False positive

[Katie Marie Nelson]

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

--- Comment #1 from Katie Marie Nelson  ---
Executable: plasma-discover PID: 16119 Signal: Segmentation fault (11) Time:
1/23/23 10:17:26 PM CST

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

[Discover] [Bug 464684] New: False positive

[Katie Marie Nelson]

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

Bug ID: 464684
   Summary: False positive
Classification: Applications
   Product: Discover
   Version: 5.24.7
  Platform: Kubuntu
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: discover
  Assignee: plasma-b...@kde.org
  Reporter: bradfordl71...@gmail.com
CC: aleix...@kde.org
  Target Milestone: ---

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
When closing Discover, a tray icon appears saying that Discover closed
unexpectedly.

STEPS TO REPRODUCE
1. Click button appy all updates
2. enter password and press yubikey
3. close discover after udating

OBSERVED RESULT
When closing a false positive system tray notificaiton appears saying Discover
closed unexpectedly.

EXPECTED RESULT


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

ADDITIONAL INFORMATION
All applicable files were sudo nano edited except user login to require my
yubkey nano 5 for 2 factor authentication.

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

[kstars] [Bug 432437] Fails to connect to ZWO CCD followed by Indi crashes

[Nelson Salez]

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

Nelson Salez  changed:

   What|Removed |Added

 Resolution|FIXED   |---
 Status|NEEDSINFO   |REPORTED

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

[kstars] [Bug 432437] Fails to connect to ZWO CCD followed by Indi crashes

[Nelson Salez]

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

Nelson Salez  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED

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

[kstars] [Bug 432437] Fails to connect to ZWO CCD followed by Indi crashes

[Nelson Salez]

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

--- Comment #3 from Nelson Salez  ---
Tested with Kstars 3.6.1.  After a couple of rounds of testing, no anomalies
occurred.  Everything worked as expected.

Thanks for the fix.

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

[plasmashell] [Bug 451839] New: Plasma Crashed

[Nelson]

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

Bug ID: 451839
   Summary: Plasma Crashed
   Product: plasmashell
   Version: 5.24.3
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: nmadn...@gmail.com
CC: k...@davidedmundson.co.uk
  Target Milestone: 1.0

Application: plasmashell (5.24.3)

Qt Version: 5.15.3
Frameworks Version: 5.92.0
Operating System: Linux 5.13.0-37-generic x86_64
Windowing System: X11
Distribution: KDE neon User - 5.24
DrKonqi: 5.24.3 [KCrashBackend]

-- Information about the crash:
- What I was doing when the application crashed:
I was running a update in the terminal as it starting installing Plasma crashe
KDE-Neon

The reporter is unsure if this crash is reproducible.

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

[New LWP 1471]
[New LWP 1569]
[New LWP 1607]
[New LWP 1634]
[New LWP 1641]
[New LWP 1674]
[New LWP 1679]
[New LWP 1699]
[New LWP 1793]
[New LWP 1794]
[New LWP 3213]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
futex_wait_cancelable (private=, expected=0,
futex_word=0x563b47fa37b4) at ../sysdeps/nptl/futex-internal.h:183
__preamble__
[Current thread is 1 (Thread 0x7febcb0d69c0 (LWP 1453))]

Thread 12 (Thread 0x7feb76ffe700 (LWP 3213)):
#0  0x7febcef8a9cf in __GI___poll (fds=0x7feb6c000fb0, nfds=3, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7feb9e9621d6 in ?? () from /lib/x86_64-linux-gnu/libpulse.so.0
#2  0x7feb9e953841 in pa_mainloop_poll () from
/lib/x86_64-linux-gnu/libpulse.so.0
#3  0x7feb9e953ec3 in pa_mainloop_iterate () from
/lib/x86_64-linux-gnu/libpulse.so.0
#4  0x7feb9e953f70 in pa_mainloop_run () from
/lib/x86_64-linux-gnu/libpulse.so.0
#5  0x7feb9e96211d in ?? () from /lib/x86_64-linux-gnu/libpulse.so.0
#6  0x7feb9e8fe72c in ?? () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so
#7  0x7febcecae609 in start_thread (arg=) at
pthread_create.c:477
#8  0x7febcef97163 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 11 (Thread 0x7febacdca700 (LWP 1794)):
#0  futex_wait_cancelable (private=, expected=0,
futex_word=0x563b49c20574) at ../sysdeps/nptl/futex-internal.h:183
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x563b49c20520,
cond=0x563b49c20548) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x563b49c20548, mutex=0x563b49c20520) at
pthread_cond_wait.c:638
#3  0x7febcf32068b in QWaitConditionPrivate::wait (deadline=...,
this=0x563b49c20520) at thread/qwaitcondition_unix.cpp:146
#4  QWaitCondition::wait (this=this@entry=0x563b490415a8,
mutex=mutex@entry=0x563b490415a0, deadline=...) at
thread/qwaitcondition_unix.cpp:225
#5  0x7febd0fa0074 in QSGRenderThreadEventQueue::takeEvent (wait=true,
this=0x563b49041598) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qdeadlinetimer.h:68
#6  QSGRenderThread::processEventsAndWaitForMore
(this=this@entry=0x563b49041500) at scenegraph/qsgthreadedrenderloop.cpp:936
#7  0x7febd0fa04e9 in QSGRenderThread::run (this=0x563b49041500) at
scenegraph/qsgthreadedrenderloop.cpp:1053
#8  0x7febcf31a623 in QThreadPrivate::start (arg=0x563b49041500) at
thread/qthread_unix.cpp:331
#9  0x7febcecae609 in start_thread (arg=) at
pthread_create.c:477
#10 0x7febcef97163 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 10 (Thread 0x7febad5cb700 (LWP 1793)):
[KCrash Handler]
#4  0x7febd0f51f5e in QSGOpaqueTextureMaterialShader::updateState
(this=0x7feba4080790, state=..., newEffect=, oldEffect=0x0) at
scenegraph/util/qsgtexturematerial.cpp:112
#5  0x7febd0f353d9 in QSGBatchRenderer::Renderer::renderMergedBatch
(this=0x7feba4005410, batch=0x7feba400d460) at
../../include/QtQuick/5.15.3/QtQuick/private/../../../../../src/quick/scenegraph/coreapi/qsgrenderer_p.h:197
#6  0x7febd0f3af8d in QSGBatchRenderer::Renderer::renderBatches
(this=this@entry=0x7feba4005410) at
scenegraph/coreapi/qsgbatchrenderer.cpp:4025
#7  0x7febd0f3b67a in QSGBatchRenderer::Renderer::render (this=) at scenegraph/coreapi/qsgbatchrenderer.cpp:4337
#8  0x7febd0f1f614 in QSGRenderer::renderScene (bindable=...,
this=0x7feba4005410) at scenegraph/coreapi/qsgrenderer.cpp:264
#9  QSGRenderer::renderScene (this=0x7feba4005410, bindable=...) at
scenegraph/coreapi/qsgrenderer.cpp:220
#10 0x7febd0f1fae3 in QSGRenderer::renderScene (this=,
fboId=) at scenegraph/coreapi/qsgrenderer.cpp:212
#11 0x7febd0f8e4d7 in QSGDefaultRenderContext::renderNextFrame
(this=0x563b4875ead0, renderer=0x7feba4005410, fboId=) at
scenegraph/qsgdefaultrendercontext.cpp:228
#12 0x7febd0ffc189 in QQuickWindowPrivate::renderSceneGraph
(this=this@entry=0x563b4859e1b0, size=..., 

[systemsettings] [Bug 449774] global theme, application style, plasma style (same type error)

[Katie Marie Nelson]

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

--- Comment #27 from Katie Marie Nelson  ---
Look I'm not going to bother! I explained to you in vivid detail and 
even took pictures at your request. I also provided additional clues to 
what else might have caused the issue. Delete the issue or do what ever.

On 2/10/22 11:15, Nate Graham wrote:
> https://bugs.kde.org/show_bug.cgi?id=449774
>
> --- Comment #26 from Nate Graham  ---
> I am still having a hard time understanding the issue. Can you please answer
> one question at a time and not also provide a ton of other information or a
> narration of what you're doing? And please don't quote every reply as it 
> causes
> each comment to be huge.
>
> Can you please write a simple step-by-step description of how you can 
> reproduce
> the problem? No need to start all the way back with "I installed such-and-such
> OS"; that part is implicit. :) Just start with what app you launched.
>

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

[systemsettings] [Bug 449774] global theme, application style, plasma style (same type error)

[Katie Marie Nelson]

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

--- Comment #25 from Katie Marie Nelson  ---
Unless you have any further questions, I'm going to leave you alone. 
Sorry if this was not organized enough and if I spammed you too much. I 
have used Kubuntu and only Kubuntu on desktop and laptop since 2008 and 
I have never seen that error the entire time.

On 2/8/22 20:26, Katie Nelson wrote:
> The usb 3.0 on the front panel is connected to this sata controller:
> https://www.amazon.com/gp/product/B09C4FDDBC/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8=1
>  
>
> I have been noticing pcio messages or acpi or something like that 
> ...it flashes so fast before booting kubuntu...but it usually loads 
> anyways and all drives work ok.
>
> On 2/8/22 20:22, Katie Nelson wrote:
>> I might also add that it was a high speed usb 3.0 PNY pendrive. The 
>> install and everything went fast but the first 2 installs I did not 
>> get that prompt to remove the installation media.
>>
>> On 2/8/22 20:18, Katie Nelson wrote:
>>> After installing 21.10 appearance subcategories work ok.
>>> I did not test downloading yet.
>>> Tray icon indicates updates available.
>>> Now updating.
>>> Updates complete via discover.
>>> Turning off screen edge effects
>>> system settings/workspace behavior/screen edges:Left top, Left 
>>> Middle: No actionapply...closing settings
>>> testing appearance subcategories again:works!!
>>> launching discover:
>>> installing:
>>> gparted partition editor
>>> grub customizer
>>> htop
>>> gnome disks
>>> cpu-x
>>> psensor
>>> ksysguard
>>> bleachbit as root
>>> network tools
>>> q4wine
>>> gsmartcontrol
>>> xsensors
>>> apper
>>> wine
>>> smplayer
>>> playitslowly
>>> simplescreenrecorder
>>> handbrake
>>> kaffeine
>>> kodi
>>> acidrip dvd ripper
>>> kmplayer
>>> brasereo
>>> k3b
>>> burner
>>> iso master
>>> audacity
>>> asunder cd ripper
>>> qmmp
>>> winff
>>> media info
>>> easy tag
>>> flowblade
>>> openshot video editor
>>> filezilla
>>> uget
>>> kget
>>> linssid
>>> gimp
>>> inkscape
>>> dia
>>> screenshot
>>> steam installer
>>> lutris
>>> qjoypad
>>> antimicrox
>>> clamtk
>>> keepassxc
>>> 
>>> Done installing rebooting
>>> Desktop loaded
>>> re-testing appearance settings...works!!!restoring folders and data 
>>> from backup
>>> re-tesing...works!!
>>> ==
>>>
>>> One thing that comes to mind is during the kubuntu setup it took a 
>>> really long time. This time it prompted me "please remove 
>>> installation media and press enter". The last 2 times I did not get 
>>> that prompt. After clicking the button "restart now" it went to a 
>>> kubuntu screen flashing blue around the word kubuntu then to a black 
>>> screen with a "_" at the top. It looked like a command prompt. It 
>>> did nothing. I waited and waited but nothing happened for about 10 
>>> minutes so I removed the pen drive and powered off the machine.
>>>
>>> On 2/8/22 17:55, Nate Graham wrote:
>>>> https://bugs.kde.org/show_bug.cgi?id=449774
>>>>
>>>> --- Comment #10 from Nate Graham  ---
>>>> OK, can you run system settings as a normal user (no sudo, no root) 
>>>> and then
>>>> describe exactly what you do and also attach a screenshot that 
>>>> shows the error?
>>>> No need for debug logs or backtraces right now; we can get to those 
>>>> later.
>>>> Thanks!
>>>>

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

[systemsettings] [Bug 449774] global theme, application style, plasma style (same type error)

[Katie Marie Nelson]

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

--- Comment #24 from Katie Marie Nelson  ---
The usb 3.0 on the front panel is connected to this sata controller:
https://www.amazon.com/gp/product/B09C4FDDBC/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8=1
I have been noticing pcio messages or acpi or something like that ...it 
flashes so fast before booting kubuntu...but it usually loads anyways 
and all drives work ok.

On 2/8/22 20:22, Katie Nelson wrote:
> I might also add that it was a high speed usb 3.0 PNY pendrive. The 
> install and everything went fast but the first 2 installs I did not 
> get that prompt to remove the installation media.
>
> On 2/8/22 20:18, Katie Nelson wrote:
>> After installing 21.10 appearance subcategories work ok.
>> I did not test downloading yet.
>> Tray icon indicates updates available.
>> Now updating.
>> Updates complete via discover.
>> Turning off screen edge effects
>> system settings/workspace behavior/screen edges:Left top, Left 
>> Middle: No actionapply...closing settings
>> testing appearance subcategories again:works!!
>> launching discover:
>> installing:
>> gparted partition editor
>> grub customizer
>> htop
>> gnome disks
>> cpu-x
>> psensor
>> ksysguard
>> bleachbit as root
>> network tools
>> q4wine
>> gsmartcontrol
>> xsensors
>> apper
>> wine
>> smplayer
>> playitslowly
>> simplescreenrecorder
>> handbrake
>> kaffeine
>> kodi
>> acidrip dvd ripper
>> kmplayer
>> brasereo
>> k3b
>> burner
>> iso master
>> audacity
>> asunder cd ripper
>> qmmp
>> winff
>> media info
>> easy tag
>> flowblade
>> openshot video editor
>> filezilla
>> uget
>> kget
>> linssid
>> gimp
>> inkscape
>> dia
>> screenshot
>> steam installer
>> lutris
>> qjoypad
>> antimicrox
>> clamtk
>> keepassxc
>> 
>> Done installing rebooting
>> Desktop loaded
>> re-testing appearance settings...works!!!restoring folders and data 
>> from backup
>> re-tesing...works!!
>> ==
>>
>> One thing that comes to mind is during the kubuntu setup it took a 
>> really long time. This time it prompted me "please remove 
>> installation media and press enter". The last 2 times I did not get 
>> that prompt. After clicking the button "restart now" it went to a 
>> kubuntu screen flashing blue around the word kubuntu then to a black 
>> screen with a "_" at the top. It looked like a command prompt. It did 
>> nothing. I waited and waited but nothing happened for about 10 
>> minutes so I removed the pen drive and powered off the machine.
>>
>> On 2/8/22 17:55, Nate Graham wrote:
>>> https://bugs.kde.org/show_bug.cgi?id=449774
>>>
>>> --- Comment #10 from Nate Graham  ---
>>> OK, can you run system settings as a normal user (no sudo, no root) 
>>> and then
>>> describe exactly what you do and also attach a screenshot that shows 
>>> the error?
>>> No need for debug logs or backtraces right now; we can get to those 
>>> later.
>>> Thanks!
>>>

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

[systemsettings] [Bug 449774] global theme, application style, plasma style (same type error)

[Katie Marie Nelson]

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

--- Comment #23 from Katie Marie Nelson  ---
I might also add that it was a high speed usb 3.0 PNY pendrive. The 
install and everything went fast but the first 2 installs I did not get 
that prompt to remove the installation media.

On 2/8/22 20:18, Katie Nelson wrote:
> After installing 21.10 appearance subcategories work ok.
> I did not test downloading yet.
> Tray icon indicates updates available.
> Now updating.
> Updates complete via discover.
> Turning off screen edge effects
> system settings/workspace behavior/screen edges:Left top, Left Middle: 
> No actionapply...closing settings
> testing appearance subcategories again:works!!
> launching discover:
> installing:
> gparted partition editor
> grub customizer
> htop
> gnome disks
> cpu-x
> psensor
> ksysguard
> bleachbit as root
> network tools
> q4wine
> gsmartcontrol
> xsensors
> apper
> wine
> smplayer
> playitslowly
> simplescreenrecorder
> handbrake
> kaffeine
> kodi
> acidrip dvd ripper
> kmplayer
> brasereo
> k3b
> burner
> iso master
> audacity
> asunder cd ripper
> qmmp
> winff
> media info
> easy tag
> flowblade
> openshot video editor
> filezilla
> uget
> kget
> linssid
> gimp
> inkscape
> dia
> screenshot
> steam installer
> lutris
> qjoypad
> antimicrox
> clamtk
> keepassxc
> 
> Done installing rebooting
> Desktop loaded
> re-testing appearance settings...works!!!restoring folders and data 
> from backup
> re-tesing...works!!
> ==
>
> One thing that comes to mind is during the kubuntu setup it took a 
> really long time. This time it prompted me "please remove installation 
> media and press enter". The last 2 times I did not get that prompt. 
> After clicking the button "restart now" it went to a kubuntu screen 
> flashing blue around the word kubuntu then to a black screen with a 
> "_" at the top. It looked like a command prompt. It did nothing. I 
> waited and waited but nothing happened for about 10 minutes so I 
> removed the pen drive and powered off the machine.
>
> On 2/8/22 17:55, Nate Graham wrote:
>> https://bugs.kde.org/show_bug.cgi?id=449774
>>
>> --- Comment #10 from Nate Graham  ---
>> OK, can you run system settings as a normal user (no sudo, no root) 
>> and then
>> describe exactly what you do and also attach a screenshot that shows 
>> the error?
>> No need for debug logs or backtraces right now; we can get to those 
>> later.
>> Thanks!
>>

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

[systemsettings] [Bug 449774] global theme, application style, plasma style (same type error)

[Katie Marie Nelson]

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

--- Comment #22 from Katie Marie Nelson  ---
After installing 21.10 appearance subcategories work ok.
I did not test downloading yet.
Tray icon indicates updates available.
Now updating.
Updates complete via discover.
Turning off screen edge effects
system settings/workspace behavior/screen edges:Left top, Left Middle: 
No actionapply...closing settings
testing appearance subcategories again:works!!
launching discover:
installing:
gparted partition editor
grub customizer
htop
gnome disks
cpu-x
psensor
ksysguard
bleachbit as root
network tools
q4wine
gsmartcontrol
xsensors
apper
wine
smplayer
playitslowly
simplescreenrecorder
handbrake
kaffeine
kodi
acidrip dvd ripper
kmplayer
brasereo
k3b
burner
iso master
audacity
asunder cd ripper
qmmp
winff
media info
easy tag
flowblade
openshot video editor
filezilla
uget
kget
linssid
gimp
inkscape
dia
screenshot
steam installer
lutris
qjoypad
antimicrox
clamtk
keepassxc

Done installing rebooting
Desktop loaded
re-testing appearance settings...works!!!restoring folders and data from 
backup
re-tesing...works!!
==

One thing that comes to mind is during the kubuntu setup it took a 
really long time. This time it prompted me "please remove installation 
media and press enter". The last 2 times I did not get that prompt. 
After clicking the button "restart now" it went to a kubuntu screen 
flashing blue around the word kubuntu then to a black screen with a "_" 
at the top. It looked like a command prompt. It did nothing. I waited 
and waited but nothing happened for about 10 minutes so I removed the 
pen drive and powered off the machine.

On 2/8/22 17:55, Nate Graham wrote:
> https://bugs.kde.org/show_bug.cgi?id=449774
>
> --- Comment #10 from Nate Graham  ---
> OK, can you run system settings as a normal user (no sudo, no root) and then
> describe exactly what you do and also attach a screenshot that shows the 
> error?
> No need for debug logs or backtraces right now; we can get to those later.
> Thanks!
>

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

[systemsettings] [Bug 449774] global theme, application style, plasma style (same type error)

[Katie Marie Nelson]

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

--- Comment #16 from Katie Marie Nelson  ---
These folders were manually created:




I am backing data up now to do a re-install  and see if I can replicate 
the error and get
some screenshots and possibly debug data.

On 2/8/22 18:32, Katie Nelson wrote:
>
> In 21.10, There are 2 methods to get to the settings. (1) The default 
> panel right next to the Kubuntu start menu icon is system settings.
>
>
> (2) Clicking the start menu icon opens up the menu and has a right 
> pane on it with system settings.
>
>
> Then from system settings, I click appearance at the top.
>
>
> As stated I can't replicate the error on this os partition without 
> re-installing. The problem was
> resolved by manually creating folders inside the .local folder and by 
> manually downloading themes etc and pushing the buttons in appearance 
> sub categories to install them.
>
>
> On 2/8/22 18:19, Katie Nelson wrote:
>> I can't on this operating system 21.10 because the error is gone 
>> after manually installing customizations as I said in my comments. I 
>> would have to switch over to the other partition with lts version on 
>> it. It will be later tonight but I will do so.
>>
>> I simply accessed them as normal in both operating systems the lts 
>> version of kubuntu and the non lts version. They were both fresh 
>> installs via downloading the iso from website and using belana etcher 
>> to write them to a usb 3.0 pen drive. I tried both before update and 
>> after on both versions and it did the same thing.
>>
>> On 2/8/22 17:55, Nate Graham wrote:
>>> https://bugs.kde.org/show_bug.cgi?id=449774
>>>
>>> --- Comment #10 from Nate Graham  ---
>>> OK, can you run system settings as a normal user (no sudo, no root) 
>>> and then
>>> describe exactly what you do and also attach a screenshot that shows 
>>> the error?
>>> No need for debug logs or backtraces right now; we can get to those 
>>> later.
>>> Thanks!
>>>

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

[systemsettings] [Bug 449774] global theme, application style, plasma style (same type error)

[Katie Marie Nelson]

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

--- Comment #12 from Katie Marie Nelson  ---
In 21.10, There are 2 methods to get to the settings. (1) The default 
panel right next to the Kubuntu start menu icon is system settings.


(2) Clicking the start menu icon opens up the menu and has a right pane 
on it with system settings.


Then from system settings, I click appearance at the top.


As stated I can't replicate the error on this os partition without 
re-installing. The problem was
resolved by manually creating folders inside the .local folder and by 
manually downloading themes etc and pushing the buttons in appearance 
sub categories to install them.


On 2/8/22 18:19, Katie Nelson wrote:
> I can't on this operating system 21.10 because the error is gone after 
> manually installing customizations as I said in my comments. I would 
> have to switch over to the other partition with lts version on it. It 
> will be later tonight but I will do  so.
>
> I simply accessed them as normal in both operating systems the lts 
> version of kubuntu and the non lts version. They were both fresh 
> installs via downloading the iso from website and using belana etcher 
> to write them to a usb 3.0 pen drive. I tried both before update and 
> after on both versions and it did the same thing.
>
> On 2/8/22 17:55, Nate Graham wrote:
>> https://bugs.kde.org/show_bug.cgi?id=449774
>>
>> --- Comment #10 from Nate Graham  ---
>> OK, can you run system settings as a normal user (no sudo, no root) 
>> and then
>> describe exactly what you do and also attach a screenshot that shows 
>> the error?
>> No need for debug logs or backtraces right now; we can get to those 
>> later.
>> Thanks!
>>

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

[systemsettings] [Bug 449774] global theme, application style, plasma style (same type error)

[Katie Marie Nelson]

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

--- Comment #13 from Katie Marie Nelson  ---
Created attachment 146462
  --> https://bugs.kde.org/attachment.cgi?id=146462=edit
1tk3cwi26P20EHWV.png

--- Comment #14 from Katie Marie Nelson  ---
Created attachment 146463
  --> https://bugs.kde.org/attachment.cgi?id=146463=edit
D1GFRvkVwInXaFKY.png

--- Comment #15 from Katie Marie Nelson  ---
Created attachment 146464
  --> https://bugs.kde.org/attachment.cgi?id=146464=edit
L5Jr05mdCO4TyISw.png

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

[systemsettings] [Bug 449774] global theme, application style, plasma style (same type error)

[Katie Marie Nelson]

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

--- Comment #11 from Katie Marie Nelson  ---
I can't on this operating system 21.10 because the error is gone after 
manually installing customizations as I said in my comments. I would 
have to switch over to the other partition with lts version on it. It 
will be later tonight but I will do  so.

I simply accessed them as normal in both operating systems the lts 
version of kubuntu and the non lts version. They were both fresh 
installs via downloading the iso from website and using belana etcher to 
write them to a usb 3.0 pen drive. I tried both before update and after 
on both versions and it did the same thing.

On 2/8/22 17:55, Nate Graham wrote:
> https://bugs.kde.org/show_bug.cgi?id=449774
>
> --- Comment #10 from Nate Graham  ---
> OK, can you run system settings as a normal user (no sudo, no root) and then
> describe exactly what you do and also attach a screenshot that shows the 
> error?
> No need for debug logs or backtraces right now; we can get to those later.
> Thanks!
>

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

[systemsettings] [Bug 449774] global theme, application style, plasma style (same type error)

[Katie Marie Nelson]

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

--- Comment #9 from Katie Marie Nelson  ---
Yes. I got root in terminal just in case I needed super user privileges. 
The debugging is new to me. It still does that without root. I'm telling 
you it's in both of latest builds. I had an old usb 2.0 drive with an 
earlier kubuntu lts 20.04 build on it and it does not have that issue.

On 2/8/22 11:16, Nate Graham wrote:
> https://bugs.kde.org/show_bug.cgi?id=449774
>
> Nate Graham  changed:
>
> What|Removed |Added
> 
>   CC||n...@kde.org
>   Resolution|--- |WAITINGFORINFO
>   Status|REPORTED|NEEDSINFO
>
> --- Comment #8 from Nate Graham  ---
> Why are you running systemsettings with sudo? That is not a good idea at all. 
> I
> would strongly recommend not doing that. Many of the errors in the debug
> logging you're provided are directly caused by doing that.
>
> Does the issue reproduce if you don't run systemsettings with sudo?
>

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

[systemsettings] [Bug 449774] global theme, application style, plasma style (same type error)

[Katie Marie Nelson]

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

--- Comment #7 from Katie Marie Nelson  ---
Icon file manually downloaded from kde store and went to settings...icons and
install file...afterwords it works!!! Before doing this it did not!! A lot of
the other Appearance sub categories I either installed by copying to .local or
using the button to install file.

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

[systemsettings] [Bug 449774] global theme, application style, plasma style (same type error)

[Katie Marie Nelson]

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

--- Comment #6 from Katie Marie Nelson  ---
Icons.."all categories are missing" shows spinning circle

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

[systemsettings] [Bug 449774] global theme, application style, plasma style (same type error)

[Katie Marie Nelson]

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

--- Comment #5 from Katie Marie Nelson  ---
I had been downloading themes etc manually and most of them went into the
.local folder. Is it possible that it's because these folders were not there? I
had to manually create these folders in .local and everyone of them that I've
added a folder for seems to be working now.

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

[systemsettings] [Bug 449774] global theme, application style, plasma style (same type error)

[Katie Marie Nelson]

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

--- Comment #4 from Katie Marie Nelson  ---
Tested at 7:01 am 2/8/2022. It is now fixed on Kubuntu 21.10.

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

[systemsettings] [Bug 449774] global theme, application style, plasma style (same type error)

[Katie Marie Nelson]

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

--- Comment #3 from Katie Marie Nelson  ---
Just booted into Kubuntu 20.04. These are fresh iso images and I did verify the
checksums from the built in properties dialog. Both distros 20.04 and 21.10 are
experiencing the same issues.

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

[systemsettings] [Bug 449774] global theme, application style, plasma style (same type error)

[Katie Marie Nelson]

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

--- Comment #2 from Katie Marie Nelson  ---
I had the same problem and thought maybe a re-install would fix this issue. It
did not. This was a fresh install of Kubuntu 21.10. As soon as I got all
updates, I went straight to settings to see if the issue was fixed. I got the
same errors.

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

[systemsettings] [Bug 449774] global theme, application style, plasma style (same type error)

[Katie Marie Nelson]

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

--- Comment #1 from Katie Marie Nelson  ---
katie@Node-10:~$ sudo -i
[sudo] password for katie: 
root@Node-10:~# gdb systemsettings5
GNU gdb (Ubuntu 11.1-0ubuntu2) 11.1
Copyright (C) 2021 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from systemsettings5...
(No debugging symbols found in systemsettings5)
(gdb) (gdb) run
Undefined command: "".  Try "help".
(gdb) run
Starting program: /usr/bin/systemsettings5 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x71104640 (LWP 76643)]
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
[New Thread 0x708ef640 (LWP 76644)]
[Detaching after fork from child process 76645]
[New Thread 0x7fffea109640 (LWP 76650)]
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
[New Thread 0x7fffde58a640 (LWP 76651)]
kf.kirigami: Warning: Theme implementations should use
Kirigami.BasicThemeDefinition for its root item
kf.kirigami: Failed to find a Kirigami platform plugin
kf.kirigami: Units.devicePixelRatio is deprecated (since 5.86 ): This returns 1
when using Qt HiDPI scaling.
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/Page.qml:448:
TypeError: Cannot read property 'globalToolBar' of null
[New Thread 0x7fffdcea3640 (LWP 76652)]
kf.kirigami: Failed to find a Kirigami platform plugin
kf.activitiesstats: KActivities: Database is not open: 
"kactivities_db_resources_140737246034304_readonly"
"/root/.local/share/kactivitymanagerd/resources/database" QSqlError("14",
"Error opening database", "unable to open database file")
QSqlDatabasePrivate::database: unable to open database: "unable to open
database file Error opening database"
kf.activitiesstats: KActivities: Database is not open: 
"kactivities_db_resources_140737246034304_readonly"
"/root/.local/share/kactivitymanagerd/resources/database" QSqlError("14",
"Error opening database", "unable to open database file")
kf.activitiesstats: KActivities ERROR: There is no database. This probably
means that you do not have the Activity Manager running, or that something else
is broken on your system. Recent documents and alike will not work!
QSqlDatabasePrivate::database: unable to open database: "unable to open
database file Error opening database"
kf.activitiesstats: KActivities: Database is not open: 
"kactivities_db_resources_140737246034304_readonly"
"/root/.local/share/kactivitymanagerd/resources/database" QSqlError("14",
"Error opening database", "unable to open database file")
QSqlDatabasePrivate::database: unable to open database: "unable to open
database file Error opening database"
kf.activitiesstats: KActivities: Database is not open: 
"kactivities_db_resources_140737246034304_readonly"
"/root/.local/share/kactivitymanagerd/resources/database" QSqlError("14",
"Error opening database", "unable to open database file")
kf.activitiesstats: KActivities ERROR: There is no database. This probably
means that you do not have the Activity Manager running, or that something else
is broken on your system. Recent documents and alike will not work!
[Detaching after fork from child process 76656]
[Detaching after fork from child process 76657]
[New Thread 0x7fffcf9f9640 (LWP 76658)]
kf.kirigami: Failed to find a Kirigami platform plugin
QQmlEngine::setContextForObject(): Object already has a QQmlContext
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/Page.qml:448:
TypeError: Cannot read property 'globalToolBar' of null
[Thread 0x7fffcf9f9640 (LWP 76658) exited]
[New Thread 0x7fffcf9f9640 (LWP 76676)]
kf.kirigami: Failed to find a Kirigami platform plugin
kf.kirigami: Units.devicePixelRatio is deprecated (since 5.86 ): This returns 1
when using Qt HiDPI scaling.
kf.kirigami: Previous message repeats 77 times.
QQmlEngine::setContextForObject(): Object already has a QQmlContext
file:///usr

[systemsettings] [Bug 449774] New: global theme, application style, plasma style (same type error)

[Katie Marie Nelson]

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

Bug ID: 449774
   Summary: global theme, application style, plasma style (same
type error)
   Product: systemsettings
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: Quick Settings
  Assignee: plasma-b...@kde.org
  Reporter: bradfordl71...@gmail.com
  Target Milestone: ---

SUMMARY
***
I have tried to follow all guidelines for submitting bug reports found here:
https://community.kde.org/Get_Involved/Issue_Reporting
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Kubuntu
I installed special packages etc but it did not create a backtrace.
***
katie@Node-10:~$ sudo -i
[sudo] password for katie: 
root@Node-10:~# gdb systemsettings5
GNU gdb (Ubuntu 11.1-0ubuntu2) 11.1
Copyright (C) 2021 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from systemsettings5...
(No debugging symbols found in systemsettings5)
(gdb) (gdb) run
Undefined command: "".  Try "help".
(gdb) run
Starting program: /usr/bin/systemsettings5 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x71104640 (LWP 76643)]
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
[New Thread 0x708ef640 (LWP 76644)]
[Detaching after fork from child process 76645]
[New Thread 0x7fffea109640 (LWP 76650)]
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
[New Thread 0x7fffde58a640 (LWP 76651)]
kf.kirigami: Warning: Theme implementations should use
Kirigami.BasicThemeDefinition for its root item
kf.kirigami: Failed to find a Kirigami platform plugin
kf.kirigami: Units.devicePixelRatio is deprecated (since 5.86 ): This returns 1
when using Qt HiDPI scaling.
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/Page.qml:448:
TypeError: Cannot read property 'globalToolBar' of null
[New Thread 0x7fffdcea3640 (LWP 76652)]
kf.kirigami: Failed to find a Kirigami platform plugin
kf.activitiesstats: KActivities: Database is not open: 
"kactivities_db_resources_140737246034304_readonly"
"/root/.local/share/kactivitymanagerd/resources/database" QSqlError("14",
"Error opening database", "unable to open database file")
QSqlDatabasePrivate::database: unable to open database: "unable to open
database file Error opening database"
kf.activitiesstats: KActivities: Database is not open: 
"kactivities_db_resources_140737246034304_readonly"
"/root/.local/share/kactivitymanagerd/resources/database" QSqlError("14",
"Error opening database", "unable to open database file")
kf.activitiesstats: KActivities ERROR: There is no database. This probably
means that you do not have the Activity Manager running, or that something else
is broken on your system. Recent documents and alike will not work!
QSqlDatabasePrivate::database: unable to open database: "unable to open
database file Error opening database"
kf.activitiesstats: KActivities: Database is not open: 
"kactivities_db_resources_140737246034304_readonly"
"/root/.local/share/kactivitymanagerd/resources/database" QSqlError("14",
"Error opening database", "unable to open database file")
QSqlDatabasePrivate::database: unable to open database: "unable to open
database file Error opening database"
kf.activitiesstats: KActivities: Database is not open: 
"kactivities_db_resources_140737246034304_readonly"
"/root/.local/share/kactivitymanagerd/resources/database" QSqlError("14",
"Error opening database", "unable to open database file")
kf.activitiesstats: KActivities ERROR: There is no database. This probably
means that you do not have the Activity Manager running, or that something else
is broken on your system. Recent documents and alike will not work!
[Detaching after fork from child process 76656]
[Detaching after fork from child process 76657]
[New Thread 0x7fffcf9f9640 (LWP 76658)]
kf.kirigami: Failed to find a Kirigami platform plugin
QQmlEngine::setContextForObject(): Object already has a QQmlContext

[Heaptrack] [Bug 431746] Heaptrack hangs indefinitely tracing the rust compiler

[Joshua Nelson]

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

--- Comment #13 from Joshua Nelson  ---
Created attachment 135919
  --> https://bugs.kde.org/attachment.cgi?id=135919=edit
strace of `rustc --version` (without going through the shim)

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

[Heaptrack] [Bug 431746] Heaptrack hangs indefinitely tracing the rust compiler

[Joshua Nelson]

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

--- Comment #12 from Joshua Nelson  ---
Milian,

The default rustc in path is just a shim, it's not important. Rustup uses it to
switch between the stable and nightly compilers. Heaptrack can run on it fine,
because it's only tracking the shim and not the compiler itself (the shim
spawns the compiler as a new process).

> Can you attach strace logs for running both versions, i.e. something like 
> `strace -e file -e process -f`

Here's an strace for the actual compiler:

$ strace -e file -e process -f
/home/joshua/.local/lib/rustup/toolchains/nightly-x86_64-unknown-linux-gnu/bin/rustc
--version
execve("/home/joshua/.local/lib/rustup/toolchains/nightly-x86_64-unknown-linux-gnu/bin/rustc",
["/home/joshua/.local/lib/rustup/t"..., "--version"], 0x7ffec9ecad90 /* 34 vars
*/) = 0
arch_prctl(ARCH_SET_FS, 0x7f5f5e98a4c0) = 0
rustc 1.52.0-nightly (0148b971c 2021-02-18)
exit_group(0)   = ?
+++ exited with 0 +++

I'll attach a full strace with all syscalls shown in just a second.

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

[Heaptrack] [Bug 431746] Heaptrack hangs indefinitely tracing the rust compiler

[Joshua Nelson]

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

--- Comment #10 from Joshua Nelson  ---
Hi Milian, is there anything more I can do to help debug this? Happy to collect
more info if you think it would be useful.

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

[kstars] [Bug 432437] New: Fails to connect to ZWO CCD followed by Indi crashes

[Nelson Salez]

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

Bug ID: 432437
   Summary: Fails to connect to ZWO CCD followed by Indi crashes
   Product: kstars
   Version: 3.5.1
  Platform: Other
OS: macOS
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mutla...@ikarustech.com
  Reporter: loconet...@icloud.com
  Target Milestone: ---

Created attachment 135380
  --> https://bugs.kde.org/attachment.cgi?id=135380=edit
kstars log file verbose mode

SUMMARY
All devices worked on v 3.5.0, NOT on v 3.5.1.  ZWO CCD for ASI120MM/Mini will
not connect, shortly after INDI crashes

STEPS TO REPRODUCE
1. Startup kstars, star ekos, connect to devices.  Mount and Sony DSLR connect
but not the ZWO.
2. Wait, shortly thereafter Indi crashes.


OBSERVED RESULT
ZWO device will not connect, Indi crashes.

EXPECTED RESULT
ZWO connects and INDI remains stable, up and running.

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

ADDITIONAL INFORMATION
Same devices worked perfectly in kstars 3.5.0

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

[Heaptrack] [Bug 431746] Heaptrack hangs indefinitely tracing the rust compiler

[Joshua Nelson]

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

--- Comment #9 from Joshua Nelson  ---
(In reply to Milian Wolff from comment #8)
> I see, interesting. is the shim doing anything special? maybe it's handling
> of execve/fork is messing up something in heaptrack. anyhow, a proper
> solution is probably going to mean adding the capability to track child
> processes somehow. that's a longstanding whish request which I sadly never
> got around to implement.

The hangs are not when running on the shim. If I bypass the shim and run on the
compiler directly (that's what `rustup which rustc` does), that's when it
hangs.

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

[Heaptrack] [Bug 431746] Heaptrack hangs indefinitely tracing the rust compiler

[Joshua Nelson]

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

--- Comment #7 from Joshua Nelson  ---
Right - `heaptrack` is just tracking the rustup shim for rustc, which is
not very helpful. It doesn't include any info about the compiler itself.

On Thu, Jan 21, 2021 at 2:09 PM Dániel Buga 
wrote:

> https://bugs.kde.org/show_bug.cgi?id=431746
>
> --- Comment #6 from Dániel Buga  ---
> Simply calling heaptrack to track rustc seems to work:
>
> ```
>  bin/heaptrack rustc --version
> heaptrack output will be written to
> "/home/dani/heaptrack/build/heaptrack.rustc.9925.gz"
> starting application, this might take some time...
> heaptrack debug(3) [9938:9938]@0 heaptrack_malloc(0x7fd450230320, 32)
> heaptrack debug(3) [9938:9938]@0 acquiring lock
> heaptrack debug(3) [9938:9938]@0 lock acquired
> heaptrack debug(3) [9938:9938]@0 releasing lock
> heaptrack debug(1) [9938:9938]@0 heaptrack_init(/tmp/heaptrack_fifo9925)
> heaptrack debug(3) [9938:9938]@0 acquiring lock
> heaptrack debug(3) [9938:9938]@0 lock acquired
> heaptrack debug(1) [9938:9938]@0 initializing: /tmp/heaptrack_fifo9925
> heaptrack debug(1) [9938:9938]@0 calling initBeforeCallback
> heaptrack debug(1) [9938:9938]@0 done calling initBeforeCallback
> heaptrack debug(1) [9938:9938]@0 doing once-only initialization
> heaptrack debug(2) [9938:9938]@0 will write to /tmp/heaptrack_fifo9925/0x3
>
> heaptrack debug(1) [9938:9938]@0 constructing LockedData
> heaptrack debug(1) [9938:9939]@0 timer thread started
> heaptrack debug(1) [9938:9938]@0 initialization done
> heaptrack debug(3) [9938:9938]@0 releasing lock
> heaptrack debug(3) [9938:9938]@0 heaptrack_malloc(0x55a52e3ec4d0, 72704)
> heaptrack debug(3) [9938:9938]@0 acquiring lock
> heaptrack debug(3) [9938:9938]@0 lock acquired
> heaptrack debug(1) [9938:9938]@0 updateModuleCache()
> heaptrack debug(2) [9938:9938]@0 dlopen_notify_callback: x 55a52d40f000
> ```
>
> But this hangs forever:
>
> bin/heaptrack $(rustup which rustc) --version
> heaptrack output will be written to
> "/home/dani/heaptrack/build/heaptrack.rustc.10419.gz"
> starting application, this might take some time...
> rustc 1.51.0-nightly (44e3daf5e 2020-12-31)
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[Heaptrack] [Bug 431746] Heaptrack hangs indefinitely tracing the rust compiler

[Joshua Nelson]

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

--- Comment #5 from Joshua Nelson  ---
Millian, thanks for getting back. Unfortunately, heaptrack has absolutely no
output on the Rust compiler. I confirmed it has logging for other programs:

```
> bin/heaptrack lsheaptrack output will be written to 
> "/home/joshua/heaptrack/build/heaptrack.ls.4864.gz"
starting application, this might take some time...
heaptrack debug(3) [4877:4877]@0 heaptrack_malloc(0x7f753d13a3a8, 32)
heaptrack debug(3) [4877:4877]@0 acquiring lock
...
```

but not on rustc:

```
> bin/heaptrack 
> /home/joshua/.local/lib/rustup/toolchains/nightly-x86_64-unknown-linux-gnu/bin/rustc
heaptrack output will be written to
"/home/joshua/heaptrack/build/heaptrack.rustc.4885.gz"
starting application, this might take some time...
Usage: rustc [OPTIONS] INPUT
... rest of the help options ...

^C
```

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

[k3b] [Bug 345392] crashed whilst burning .avi (video) files from own SDHC card

[Derek Nelson-Wills]

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

--- Comment #5 from Derek Nelson-Wills  ---
 I cannot confirm whether this matter has been addressed or resolved - it was
reported by me more than five years ago! It is now some time since I have used
K3b for DVD burning and Mint has now ceased using the KDE system.



I am now using Mint “Yuliana” release 20, with the “cinnamon” Gnome UI, so it
is impossible for me to run like-for-like testing or to try and replicate the
issue.



My apologies,

D. Nelson-Wills.








>   
> On Dec 17, 2020 at 5:33 am,  mailto:bugzilla_nore...@kde.org)> 
>  wrote:
>   
>   
>   
>   https://bugs.kde.org/show_bug.cgi?id=345392  Justin Zobel  
> mailto:justin.zo...@gmail.com)>  changed: What 
> |Removed |Added 
>  
> Resolution|--- |WAITINGFORINFO Status|REPORTED |NEEDSINFO --- Comment #4 from 
> Justin Zobel  mailto:justin.zo...@gmail.com)>  --- 
> Thank you for the crash report. As it has been a while since this was 
> reported, can you please test and confirm if this issue is still occurring or 
> if this bug report can be marked as resolved. I have set the bug status to 
> "needsinfo" pending your response, please change back to "reported" or 
> "resolved/worksforme" when you respond, thank you. -- You are receiving this 
> mail because: You reported the bug.  
>
>

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

[dolphin] [Bug 424229] Dolphin crashes when using SMB to reach NAS folder.

[Nelson]

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

Nelson  changed:

   What|Removed |Added

 CC||questorat7ac...@aol.com

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

[kmail2] [Bug 422151] New: Crash on attempting to open a 2GB mbox file

[Dave Nelson]

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

Bug ID: 422151
   Summary: Crash on attempting to open a 2GB mbox file
   Product: kmail2
   Version: 5.11.3
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: d...@dalek.zone
  Target Milestone: ---

Application: kmail (5.11.3)

Qt Version: 5.12.4
Frameworks Version: 5.62.0
Operating System: Linux 5.3.0-51-generic x86_64
Distribution: Ubuntu 19.10

-- Information about the crash:
- What I was doing when the application crashed: I double-clicked on a 2GB mbox
file from a Google takeaway download, on a computer with 4GB of RAM.

-- Backtrace:
Application: KMail (kmail), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fc27e5e3f00 (LWP 27494))]

Thread 7 (Thread 0x7fc2677fe700 (LWP 27780)):
#0  0x7fc290987f66 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fc2909889db in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fc290988be3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fc294210653 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fc2941b75cb in
QEventLoop::exec(QFlags) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fc293ff0a45 in QThread::exec() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fc293ff1c92 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fc2912e7669 in start_thread (arg=) at
pthread_create.c:479
#8  0x7fc293c76323 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 6 (Thread 0x7fc267fff700 (LWP 27767)):
#0  __GI___libc_read (nbytes=16, buf=0x7fc267ffe490, fd=12) at
../sysdeps/unix/sysv/linux/read.c:26
#1  __GI___libc_read (fd=12, buf=0x7fc267ffe490, nbytes=16) at
../sysdeps/unix/sysv/linux/read.c:24
#2  0x7fc2909d070f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fc2909885fe in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fc290988a52 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fc290988be3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7fc294210653 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fc2941b75cb in
QEventLoop::exec(QFlags) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fc293ff0a45 in QThread::exec() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7fc293ff1c92 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7fc2912e7669 in start_thread (arg=) at
pthread_create.c:479
#11 0x7fc293c76323 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 5 (Thread 0x7fc274861700 (LWP 27752)):
#0  0x7fc293c69c2f in __GI___poll (fds=0x7fc26c0025e0, nfds=1,
timeout=7536) at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7fc290988aae in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fc290988be3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fc294210653 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fc2941b75cb in
QEventLoop::exec(QFlags) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fc293ff0a45 in QThread::exec() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fc293ff1c92 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fc2912e7669 in start_thread (arg=) at
pthread_create.c:479
#8  0x7fc293c76323 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 4 (Thread 0x7fc275a72700 (LWP 27744)):
#0  0x7fc293c69c2f in __GI___poll (fds=0x55cc118f5830, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7fc290988aae in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fc290988be3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fc294210653 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fc2941b75cb in
QEventLoop::exec(QFlags) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fc293ff0a45 in QThread::exec() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fc293716efa in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x7fc293ff1c92 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fc2912e7669 in start_thread (arg=) at
pthread_create.c:479
#9  0x7fc293c76323 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 3 (Thread 0x7fc277338700 (LWP 27742)):
#0  futex_wait_cancelable (private=, expected=0,
futex_word=0x55cc114d2728) at ../sysdeps/unix/sysv/linux/futex-internal.h:80
#1  __pthread_cond_wait_common 

[plasmashell] [Bug 412923] New: Global Menu on Latte panel on one activity = no menu at all on another activity

[Nelson]

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

Bug ID: 412923
   Summary: Global Menu on Latte panel on one activity = no menu
at all on another activity
   Product: plasmashell
   Version: 5.16.5
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Global Menu
  Assignee: k...@privat.broulik.de
  Reporter: dubh...@yandex.com
CC: mvourla...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Created attachment 123173
  --> https://bugs.kde.org/attachment.cgi?id=123173=edit
Two screenshots of observed behavior from both activities

SUMMARY
I have set up two activities, using Latte panel/dock instead of Plasma panel.
In one activity, I use Global Menu on a Latte panel. In another activity, I use
no Global Menu. The activity with Global Menu works as expected; the activity
without it shows no menus altogether.

STEPS TO REPRODUCE
1. Install Latte dock/panel.
2. Set up a Latte panel, configure it so it's only on that activity.
3. Place the Global Menu applet on that panel.
4. Switch to another activity.
5. Open any program that normally has a menu.

OBSERVED RESULT
The program opened in the activity that has no Global Menu won't have its menu
on its own window. Instead, it will have no menu at all.

EXPECTED RESULT
The program opened in the activity with no Global Menu would have a menu on its
own window, like normally happens if one doesn't use Global Menu.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE neon 5.16, User Edition
KDE Plasma Version: 5.16.5
KDE Frameworks Version: 5.62.0
Qt Version: 5.13.1

ADDITIONAL INFORMATION
Also tested with Window AppMenu, which is a Global Menu applet made by Latte
Dock's creator. Same results as explained above.

I attached a screenshot. One side with the activity with Global Menu, showing
an application open, with an expected result. The other, in the other activity
that has no Global Menu, showing another instance of the same application, but
with no menu altogether.

The author of Latte Dock seems to think this issue is related to how Global
Menu works rather than something he can do with his Latte Dock program to fix
the behavior. Therefore, I ask here.

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