[systemsettings] [Bug 424090] New: Add emoji font selection

[kmi]

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

Bug ID: 424090
   Summary: Add emoji font selection
   Product: systemsettings
   Version: unspecified
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm_fonts
  Assignee: plasma-b...@kde.org
  Reporter: kamika...@gmail.com
  Target Milestone: ---

Similar to Sans Serief, Monospace, etc font selection, there should be a picker
for choosing the emoji font.

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

[krita] [Bug 423630] [Steam] Create Start Menu icon

[kmi]

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

--- Comment #5 from kmi  ---
(In reply to Boudewijn Rempt from comment #4)
> Actually, apparently you can enable whether an application has a start menu
> entry in steam's settings?

Nope, only a desktop icon that links to steam://rungameid/280680 (which also
means that Steam will launch first, ie. the startup time is horrible even with
an SSD).

Quite frankly, I'm puzzled that a relatively minor request that would help
people who paid for Krita would be so controversial.

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

[krita] [Bug 423630] [Steam] Create Start Menu icon

[kmi]

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

--- Comment #3 from kmi  ---
(In reply to Boudewijn Rempt from comment #2)
> I don't think that this is krita's job

Krita does this job in the non-paid installer. All I ask is a little feature
parity: An icon in the Start Menu.

The checkbox was just an idea. The exact method is not really relevant.

> and I have never seen any application
> on Windows that handles its start menu integration like that.

Usually games require Steam to run because of DRM. Luckily, Krita is different
but as it is now, one has to manually navigate to "C:\Program Files
(x86)\Steam\steamapps\common\Krita\krita\bin".

Windows does not allow apps without a .lnk file in
"%appdata%\Microsoft\Windows\Start Menu\Programs"  to Pin To Start.

I don't think my workflow is super weird in that I group productivity apps
together in my Start Menu.

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

[krita] [Bug 423630] New: [Steam] Create Start Menu icon

[kmi]

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

Bug ID: 423630
   Summary: [Steam] Create Start Menu icon
   Product: krita
   Version: unspecified
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: krita-bugs-n...@kde.org
  Reporter: kamika...@web.de
  Target Milestone: ---

Since Krita from Steam runs just fine without Steam running and Steam is at
most only capable to create an icon on the desktop, Krita from Steam should
have an option to create a Start Menu icon.

Under Windows that would be a link in "%appdata%\Microsoft\Windows\Start
Menu\Programs" to "C:\Program Files
(x86)\Steam\steamapps\common\Krita\krita\bin\krita.exe" (or wherever the Steam
library is).

Not sure what the best way under Linux would be.

I suggest a checkbox in Settings > General that adds or removes the shortcut.

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

[Breeze] [Bug 422551] Window decoration corner radius does not respect scale factor

[kmi]

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

kmi  changed:

   What|Removed |Added

 CC||kamika...@web.de

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

[kwin] [Bug 422549] Default window sizes not scaled with scale factor

[kmi]

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

kmi  changed:

   What|Removed |Added

 CC||kamika...@web.de

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

[kwin] [Bug 422548] Cursors do not respect scale factor on X11

[kmi]

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

kmi  changed:

   What|Removed |Added

 CC||kamika...@web.de

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

[kwin] [Bug 422547] Small Icons, Large Icons, and Thumbnails task switchers do not respect scale factor on X11

[kmi]

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

kmi  changed:

   What|Removed |Added

 CC||kamika...@web.de

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

[plasmashell] [Bug 356446] plasmashell does not respect QT_DEVICE_PIXEL_RATIO on X

[kmi]

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

kmi  changed:

   What|Removed |Added

 CC||kamika...@web.de

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

[plasmashell] [Bug 422552] Auto-detect appropriate scale factor for the easy cases (e.g. 4k screen) on X11

[kmi]

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

kmi  changed:

   What|Removed |Added

 CC||kamika...@web.de

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

[Breeze] [Bug 419045] Inconsistencies in behavior when left clicking on toolbar

[kmi]

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

kmi  changed:

   What|Removed |Added

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

--- Comment #2 from kmi  ---
Oh, you've meant clicking and holding the mouse button on a toolbar button. I
see. You're totally right.

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

[Breeze] [Bug 419045] Inconsistencies in behavior when left clicking on toolbar

[kmi]

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

kmi  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 CC||kamika...@web.de
 Resolution|--- |NOT A BUG

--- Comment #1 from kmi  ---
I can equally move a window from empty space in KWrite, KSysGuard, Dolphin, and
Okular.

Using KF 5.67 and Qt 5.14.1.

I'm closing the report. Please reopen, should I have misunderstood.

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

[plasmashell] [Bug 417282] Set 24h in System Settings, got 12h in lockscreen

[kmi]

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

kmi  changed:

   What|Removed |Added

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

--- Comment #8 from kmi  ---
There is absolutely no difference whether I also set Detailed Settings to the
time format or not.

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

[krename] [Bug 418112] HiDPI rendering problems

[kmi]

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

kmi  changed:

   What|Removed |Added

   Assignee|heire...@exherbo.org|i...@guoyunhe.me

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

[krename] [Bug 418112] New: HiDPI rendering problems

[kmi]

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

Bug ID: 418112
   Summary: HiDPI rendering problems
   Product: krename
   Version: 5.0.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: heire...@exherbo.org
  Reporter: kamika...@web.de
  Target Milestone: ---

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

SUMMARY

KRename's GUI is not HiDPI enabled. See attached screenshot for details.

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

[akregator] [Bug 116482] metakit: akregator crashes at startup

[kmi]

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

kmi  changed:

   What|Removed |Added

 Resolution|FIXED   |---
 Ever confirmed|1   |0
 CC||kamika...@web.de
   Platform|Kubuntu Packages|unspecified
 Status|RESOLVED|REPORTED

--- Comment #282 from kmi  ---
Hardly any commits in
https://github.com/KDE/akregator/commits/master/plugins/mk4storage over a few
years.

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

[frameworks-kirigami] [Bug 417694] New: Disabled "Invert scroll direction" with touchpad, still inverted

[kmi]

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

Bug ID: 417694
   Summary: Disabled "Invert scroll direction" with touchpad,
still inverted
   Product: frameworks-kirigami
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: notm...@gmail.com
  Reporter: kamika...@web.de
  Target Milestone: Not decided

SUMMARY


STEPS TO REPRODUCE
1. Disable "Invert scroll direction" in System Settings

OBSERVED RESULT
QtQuick-using Views such as System Setting's side bar still scroll in the
inverted/"natural"/wrong direction. Dolphin/Firefox/… and everything else
appears to be fine.

EXPECTED RESULT
Respect scrolling direction.

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.18.0
KDE Frameworks Version: 5.66
Qt Version: 5.14.1

ADDITIONAL INFORMATION
Using Wayland on openSUSE TW.

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

[plasmashell] [Bug 417282] Set 24h in System Settings, got 12h in lockscreen

[kmi]

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

kmi  changed:

   What|Removed |Added

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

--- Comment #3 from kmi  ---
(In reply to David Edmundson from comment #2)
> Please include output of "env"

COLORFGBG=0;15
COLORTERM=truecolor
DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-oZbq4VeoIv,guid=424e2aaa65f7bcd418823cd15e404459
DESKTOP_SESSION=plasmawayland
DISPLAY=:0
GDK_BACKEND=x11
GDMSESSION=plasmawayland
GDM_LANG=en_US.UTF-8
GS_LIB=/home/user/.fonts
GTK2_RC_FILES=/etc/gtk-2.0/gtkrc:/home/user/.gtkrc-2.0:/home/user/.config/gtkrc-2.0
GTK_RC_FILES=/etc/gtk/gtkrc:/home/user/.gtkrc:/home/user/.config/gtkrc
HOME=/home/user
KDE_FULL_SESSION=true
KDE_SESSION_UID=1000
KDE_SESSION_VERSION=5
KONSOLE_DBUS_SERVICE=:1.24
KONSOLE_DBUS_SESSION=/Sessions/1
KONSOLE_VERSION=191201
LANG=de_DE.UTF-8
LANGUAGE=en_US
LOGNAME=user
PATH=/home/user/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin
PLASMA_USE_QT_SCALING=1
PROFILEHOME=
PWD=/home/user
QT_AUTO_SCREEN_SCALE_FACTOR=0
QT_WAYLAND_FORCE_DPI=96
SESSION_MANAGER=local/user-linux:@/tmp/.ICE-unix/2260,unix/user-linux:/tmp/.ICE-unix/2260
SHELL=/usr/bin/fish
SHELL_SESSION_ID=7e313f33a4184f67847dcc9012f816ff
SHLVL=1
TERM=xterm-256color
USER=user
USERNAME=user
WAYLAND_DISPLAY=wayland-0
WINDOWID=0
X11LAYOUT=de
X11MODEL=pc105
X11OPTIONS=terminate:ctrl_alt_bksp
XAUTHLOCALHOSTNAME=user-linux
XAUTHORITY=/run/user/1000/xauth_YLOPHk
XCURSOR_SIZE=36
XCURSOR_THEME=breeze_cursors
XDG_CURRENT_DESKTOP=KDE
XDG_DATA_DIRS=/home/user/.local/share/flatpak/exports/share/:/var/lib/flatpak/exports/share/:/usr/local/share/:/usr/share/
XDG_RUNTIME_DIR=/run/user/1000
XDG_SEAT=seat0
XDG_SESSION_CLASS=user
XDG_SESSION_DESKTOP=plasmawayland
XDG_SESSION_ID=1
XDG_SESSION_TYPE=wayland
XDG_VTNR=2

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

[plasmashell] [Bug 417282] Set 24h in System Settings, got 12h in lockscreen

[kmi]

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

--- Comment #1 from kmi  ---
Created attachment 125754
  --> https://bugs.kde.org/attachment.cgi?id=125754=edit
Photo of lockscreen

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

[plasmashell] [Bug 417282] New: Set 24h in System Settings, got 12h in lockscreen

[kmi]

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

Bug ID: 417282
   Summary: Set 24h in System Settings, got 12h in lockscreen
   Product: plasmashell
   Version: 5.17.90
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Lock/logout
  Assignee: plasma-b...@kde.org
  Reporter: kamika...@web.de
  Target Milestone: 1.0

Created attachment 125753
  --> https://bugs.kde.org/attachment.cgi?id=125753=edit
Screenshot of System Settings

SUMMARY

Set 24h in System Settings, got 12h in lockscreen.

STEPS TO REPRODUCE
1. Set the time format in System Settings to a 24h one
2. Lock the screen

OBSERVED RESULT

8:35 PM

EXPECTED RESULT

20:35

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.17.90
KDE Frameworks Version: 5.66.0
Qt Version: 5.14.1

ADDITIONAL INFORMATION

System language is set to US English.

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

[systemsettings] [Bug 380980] Font names with spaces (in font meta-data) are not processed correctly.

[kmi]

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

kmi  changed:

   What|Removed |Added

 Ever confirmed|0   |1
  Component|kcm_style   |kcm_fonts
 CC||kamika...@web.de
 Status|REPORTED|CONFIRMED

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

[plasmashell] [Bug 379635] popmenu at desktop doesn't disappear when lost focus.

[kmi]

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

kmi  changed:

   What|Removed |Added

 CC||kamika...@web.de

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

[frameworks-baloo] [Bug 389848] baloo_file crashes in mdb_put() in LMDB

[kmi]

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

--- Comment #128 from kmi  ---
I've got the crash recently but a "balooctl purge" command to rebuild the index
fixed it for me. Seems like Baloo doesn't like it when there's some data
corrupted or so.

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

[Powerdevil] [Bug 414872] Crash when unplugging second monitor under Wayland

[kmi]

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

kmi  changed:

   What|Removed |Added

Summary|Crash when unplugging   |Crash when unplugging
   |second monitor  |second monitor under
   ||Wayland

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

[Powerdevil] [Bug 414872] New: Crash when unplugging second monitor

[kmi]

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

Bug ID: 414872
   Summary: Crash when unplugging second monitor
   Product: Powerdevil
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: kamika...@web.de
  Target Milestone: ---

Application: org_kde_powerdevil (2.0.0)

Qt Version: 5.13.1
Frameworks Version: 5.64.0
Operating System: Linux 5.3.12-1-default x86_64
Distribution: "openSUSE Tumbleweed"

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

I was using an external screen with my notebook. Unplugging it caused the
crash.

The crash can be reproduced sometimes.

-- Backtrace:
Application: KDE Power Management System (org_kde_powerdevil), signal:
Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fd0d4dd1800 (LWP 2299))]

Thread 6 (Thread 0x7fd0c3fff700 (LWP 2357)):
#0  0x7fd0d72a1bdf in poll () from /lib64/libc.so.6
#1  0x7fd0d5e1427e in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7fd0d5e1439f in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7fd0d784398b in QEventDispatcherGlib::processEvents
(this=0x7fd0b8000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7fd0d77ec0cb in QEventLoop::exec (this=this@entry=0x7fd0c3ffeda0,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:140
#5  0x7fd0d7624021 in QThread::exec (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:120
#6  0x7fd0d76251a2 in QThreadPrivate::start (arg=0x55b701e340c0) at
thread/qthread_unix.cpp:360
#7  0x7fd0d6903f2a in start_thread () from /lib64/libpthread.so.0
#8  0x7fd0d72ac4af in clone () from /lib64/libc.so.6

Thread 5 (Thread 0x7fd0d0fe5700 (LWP 2356)):
#0  0x7fd0d72a1bdf in poll () from /lib64/libc.so.6
#1  0x7fd0d5e1427e in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7fd0d5e1439f in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7fd0d784398b in QEventDispatcherGlib::processEvents
(this=0x7fd0bc000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7fd0d77ec0cb in QEventLoop::exec (this=this@entry=0x7fd0d0fe4da0,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:140
#5  0x7fd0d7624021 in QThread::exec (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:120
#6  0x7fd0d76251a2 in QThreadPrivate::start (arg=0x55b701e1e360) at
thread/qthread_unix.cpp:360
#7  0x7fd0d6903f2a in start_thread () from /lib64/libpthread.so.0
#8  0x7fd0d72ac4af in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7fd0d1abd700 (LWP 2314)):
#0  0x7fd0d72a1bdf in poll () from /lib64/libc.so.6
#1  0x7fd0d5e1427e in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7fd0d5e145e3 in g_main_loop_run () from /usr/lib64/libglib-2.0.so.0
#3  0x7fd0d24919c6 in ?? () from /usr/lib64/libgio-2.0.so.0
#4  0x7fd0d5e3d11e in ?? () from /usr/lib64/libglib-2.0.so.0
#5  0x7fd0d6903f2a in start_thread () from /lib64/libpthread.so.0
#6  0x7fd0d72ac4af in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7fd0d22be700 (LWP 2313)):
#0  0x7fd0d72a1bdf in poll () from /lib64/libc.so.6
#1  0x7fd0d5e1427e in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7fd0d5e1439f in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7fd0d5e143f1 in ?? () from /usr/lib64/libglib-2.0.so.0
#4  0x7fd0d5e3d11e in ?? () from /usr/lib64/libglib-2.0.so.0
#5  0x7fd0d6903f2a in start_thread () from /lib64/libpthread.so.0
#6  0x7fd0d72ac4af in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7fd0d2e11700 (LWP 2310)):
#0  0x7fd0d5e10f12 in ?? () from /usr/lib64/libglib-2.0.so.0
#1  0x7fd0d5e12564 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7fd0d5e13743 in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#3  0x7fd0d5e141ab in ?? () from /usr/lib64/libglib-2.0.so.0
#4  0x7fd0d5e1439f in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#5  0x7fd0d784398b in QEventDispatcherGlib::processEvents
(this=0x7fd0cc000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#6  0x7fd0d77ec0cb in QEventLoop::exec (this=this@entry=0x7fd0d2e10d70,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:140
#7  0x7fd0d7624021 in QThread::exec (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:120
#8  0x7fd0d7acc4f6 in ?? () from /usr/lib64/libQt5DBus.so.5
#9  0x7fd0d76251a2 in QThreadPrivate::start (arg=0x7fd0d7b4ed80) at
thread/qthread_unix.cpp:360
#10 0x7fd0d6903f2a in start_thread () from /lib64/libpthread.so.0
#11 0x7fd0d72ac4af in clone () from /lib64/libc.so.6

[kmail2] [Bug 284172] Kmail does not correctly recognize some IMAP-Inbox-Folders

[kmi]

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

kmi  changed:

   What|Removed |Added

 CC||cyg...@tutanota.com

--- Comment #28 from kmi  ---
*** Bug 343825 has been marked as a duplicate of this bug. ***

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

[kmail2] [Bug 343825] KMail does not pull IMAP inbox mail

[kmi]

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

kmi  changed:

   What|Removed |Added

 Resolution|UNMAINTAINED|DUPLICATE
 CC||kamika...@web.de

--- Comment #7 from kmi  ---


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

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

[frameworks-baloo] [Bug 389848] baloo_file crashes in mdb_put() in LMDB

[kmi]

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

kmi  changed:

   What|Removed |Added

 CC||kamika...@web.de

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

[frameworks-baloo] [Bug 413485] New: Crash when downloading files

[kmi]

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

Bug ID: 413485
   Summary: Crash when downloading files
   Product: frameworks-baloo
   Version: 5.63.0
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: Baloo File Daemon
  Assignee: stefan.bru...@rwth-aachen.de
  Reporter: kamika...@web.de
  Target Milestone: ---

Application: baloo_file_extractor (5.63.0)

Qt Version: 5.13.1
Frameworks Version: 5.63.0
Operating System: Linux 5.3.6-1-default x86_64
Distribution: "openSUSE Tumbleweed"

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

I was downloading some audio files. The crash occured when the downloads were
still in progress.

-- Backtrace:
Application: Baloo File Extractor (baloo_file_extractor), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f8b16a27800 (LWP 17124))]

Thread 3 (Thread 0x7f8b0700 (LWP 17126)):
#0  0x7f8b16f345a4 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0
#1  0x7f8b16ee92a3 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f8b16ee93cf in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f8b1834e99b in QEventDispatcherGlib::processEvents
(this=0x7f8b08000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f8b182f70db in QEventLoop::exec (this=this@entry=0x7f8b0fffed70,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:140
#5  0x7f8b1812f021 in QThread::exec (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:120
#6  0x7f8b193694f6 in ?? () from /usr/lib64/libQt5DBus.so.5
#7  0x7f8b181301a2 in QThreadPrivate::start (arg=0x7f8b193ebd80) at
thread/qthread_unix.cpp:360
#8  0x7f8b17845f2a in start_thread () from /lib64/libpthread.so.0
#9  0x7f8b17db74af in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f8b149c4700 (LWP 17125)):
#0  0x7f8b17dacbdf in poll () from /lib64/libc.so.6
#1  0x7f8b16e87742 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7f8b16e883fa in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7f8b14bd9f90 in ?? () from /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f8b181301a2 in QThreadPrivate::start (arg=0x55b7893408b0) at
thread/qthread_unix.cpp:360
#5  0x7f8b17845f2a in start_thread () from /lib64/libpthread.so.0
#6  0x7f8b17db74af in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f8b16a27800 (LWP 17124)):
[KCrash Handler]
#6  0x7f8b17cf40d1 in raise () from /lib64/libc.so.6
#7  0x7f8b17cdd55d in abort () from /lib64/libc.so.6
#8  0x7f8b17a086f3 in mdb_assert_fail (env=0x55b7893f0090,
expr_txt=expr_txt@entry=0x7f8b17a0a04c "mp->mp_pgno != pgno",
func=func@entry=0x7f8b17a0a988 <__func__.7286> "mdb_page_touch",
line=line@entry=2433, file=0x7f8b17a0a010 "mdb.c") at mdb.c:1542
#9  0x7f8b179fea1a in mdb_page_touch (mc=mc@entry=0x7ffc80e99120) at
mdb.c:2441
#10 0x7f8b179fef38 in mdb_page_search (mc=mc@entry=0x7ffc80e99120,
key=0x55b7893f02e0, flags=flags@entry=1) at mdb.c:5657
#11 0x7f8b17a004a1 in mdb_cursor_touch (mc=mc@entry=0x7ffc80e99600) at
mdb.c:6515
#12 0x7f8b17a035f5 in mdb_cursor_put (mc=mc@entry=0x7ffc80e99600,
key=key@entry=0x7ffc80e999f0, data=data@entry=0x7ffc80e99a00,
flags=flags@entry=0) at mdb.c:6657
#13 0x7f8b17a0644b in mdb_put (txn=0x55b7893f04d0, dbi=4,
key=key@entry=0x7ffc80e999f0, data=data@entry=0x7ffc80e99a00,
flags=flags@entry=0) at mdb.c:9022
#14 0x7f8b19417991 in Baloo::DocumentDB::put
(this=this@entry=0x7ffc80e99b20, docId=,
docId@entry=436339939647487488, list=...) at
/usr/src/debug/baloo5-5.63.0-1.1.x86_64/src/engine/documentdb.cpp:79
#15 0x7f8b1944a0d0 in Baloo::WriteTransaction::replaceDocument
(this=0x55b7893f0010, doc=..., operations=operations@entry=...) at
/usr/src/debug/baloo5-5.63.0-1.1.x86_64/src/engine/writetransaction.cpp:210
#16 0x7f8b1943b372 in Baloo::Transaction::replaceDocument
(this=0x55b7893f2960, doc=..., operations=...) at
/usr/src/debug/baloo5-5.63.0-1.1.x86_64/src/engine/transaction.cpp:293
#17 0x55b78848baa5 in ?? ()
#18 0x55b78848d56b in ?? ()
#19 0x7f8b18330382 in QtPrivate::QSlotObjectBase::call (a=0x7ffc80e99fa0,
r=, this=) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394
#20 QSingleShotTimer::timerEvent (this=0x55b7893f01e0) at kernel/qtimer.cpp:318
#21 0x7f8b18323e85 in QObject::event (this=0x55b7893f01e0, e=) at kernel/qobject.cpp:1282
#22 0x7f8b18d2ac62 in QApplicationPrivate::notify_helper
(this=this@entry=0x55b789318140, receiver=receiver@entry=0x55b7893f01e0,
e=e@entry=0x7ffc80e9a2c0) at kernel/qapplication.cpp:3703
#23 0x7f8b18d341e0 in QApplication::notify (this=0x7ffc80e9a5a0,
receiver=0x55b7893f01e0, e=0x7ffc80e9a2c0) at kernel/qapplication.cpp:3449
#24 0x7f8b182f8572 in 

[kde-windows] [Bug 276857] KDE applications should use the standard Windows fonts

[kmi]

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

--- Comment #4 from kmi  ---
(In reply to Jack from comment #3)
> I'm curious about WHAT specifically is unmaintained to justify closing this.

Anything Qt4-related.

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

[kde-windows] [Bug 413232] Oxygen icons instead of Breeze in app store

[kmi]

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

--- Comment #4 from kmi  ---
The application icons are currently Oxygen and that's wrong – neither fitting
style guidelines of any Win version since Win8 nor being the "currently
actively maintained icon set" as you wrote yourself.

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

[kde-windows] [Bug 413232] Oxygen icons instead of Breeze in app store

[kmi]

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

--- Comment #2 from kmi  ---
(In reply to Christoph Cullmann from comment #1)
> What does this bug mean?
> That we shall use Oxygen?

The bug is that Oxygen is currently being used. I reported a bug, not a wish.

You yourself linked https://www.microsoft.com/store/apps/9N41MSQ1WNM8 ,
https://www.microsoft.com/store/apps/9NWMW7BB59HW , and
https://www.microsoft.com/store/apps/9PPRZ2QHLXTG in a Reddit post. Never
looked at the actual site or tried to launch those apps under Windows?

> breeze is the currently actively maintained icon set and is
> more in style with what Win10 has as icons anyways.

Exactly. Even more baffling then that you use Oxygen instead of Breeze.

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

[kde-windows] [Bug 413232] New: Oxygen icons instead of Breeze in app store

[kmi]

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

Bug ID: 413232
   Summary: Oxygen icons instead of Breeze in app store
   Product: kde-windows
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kde-wind...@kde.org
  Reporter: kamika...@web.de
  Target Milestone: ---

Windows ports use Breeze

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

[kde-windows] [Bug 317622] git master branch (kde-4.10) should be updated

[kmi]

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

kmi  changed:

   What|Removed |Added

 CC||kamika...@web.de
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

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

[kde-windows] [Bug 340289] in kde-4.13 for windows, emerge qt fails build

[kmi]

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

kmi  changed:

   What|Removed |Added

 Resolution|--- |UNMAINTAINED
 CC||kamika...@web.de
 Status|REPORTED|RESOLVED

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

[kde-windows] [Bug 276857] KDE applications should use the standard Windows fonts

[kmi]

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

kmi  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 CC||kamika...@web.de
 Resolution|--- |UNMAINTAINED

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

[kde-windows] [Bug 318820] emerge git branch kde-4.10 brocken

[kmi]

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

kmi  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 CC||kamika...@web.de
 Resolution|--- |UNMAINTAINED

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

[kde-windows] [Bug 338318] kdesettings-example.bat missing from kde-4.13

[kmi]

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

kmi  changed:

   What|Removed |Added

 Resolution|--- |UNMAINTAINED
 CC||kamika...@web.de
 Status|REPORTED|RESOLVED

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

[kde-windows] [Bug 338319] kde-4.13 build fails on win32-mscv2013 due to old qt

[kmi]

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

kmi  changed:

   What|Removed |Added

 CC||kamika...@web.de
 Status|REPORTED|RESOLVED
 Resolution|--- |UNMAINTAINED

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

[kmail2] [Bug 396282] Segmentation fault on loading mail in Wayland

[kmi]

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

kmi  changed:

   What|Removed |Added

 CC||kl...@free.fr

--- Comment #1 from kmi  ---
*** Bug 396780 has been marked as a duplicate of this bug. ***

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

[kmail2] [Bug 396780] Crash at startup on Wayland

[kmi]

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

kmi  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|REPORTED|RESOLVED
 CC||kamika...@web.de

--- Comment #1 from kmi  ---


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

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

[kmail2] [Bug 409679] Kmail crash when open through a mailto link

[kmi]

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

--- Comment #1 from kmi  ---
Created attachment 122452
  --> https://bugs.kde.org/attachment.cgi?id=122452=edit
New crash information added by DrKonqi

kmail (5.12.0) using Qt 5.13.0

- What I was doing when the application crashed:

I clicked on a mailto: link in Firefox.

- Custom settings of the application:

openSUSE Tumbleweed in a Plasma Wayland session.

-- Backtrace (Reduced):
#6  0x7f89eee18c48 in
QWebEnginePagePrivate::bindPageAndWidget(QWebEnginePage*,
QtWebEngineCore::RenderWidgetHostViewQtDelegateWidget*) () from
/usr/lib64/libQt5WebEngineWidgets.so.5
#7  0x7f89eee0879a in
QtWebEngineCore::RenderWidgetHostViewQtDelegateWidget::~RenderWidgetHostViewQtDelegateWidget()
() from /usr/lib64/libQt5WebEngineWidgets.so.5
#8  0x7f89eee087f9 in
QtWebEngineCore::RenderWidgetHostViewQtDelegateWidget::~RenderWidgetHostViewQtDelegateWidget()
() from /usr/lib64/libQt5WebEngineWidgets.so.5
#9  0x7f89e7ab0bcd in
QtWebEngineCore::RenderWidgetHostViewQt::~RenderWidgetHostViewQt() () from
/usr/lib64/libQt5WebEngineCore.so.5
#10 0x7f89e7ab0cc2 in
QtWebEngineCore::RenderWidgetHostViewQt::~RenderWidgetHostViewQt() () from
/usr/lib64/libQt5WebEngineCore.so.5

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

[kmail2] [Bug 409679] Kmail crash when open through a mailto link

[kmi]

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

kmi  changed:

   What|Removed |Added

 CC||kamika...@web.de

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

[yakuake] [Bug 407726] Button icons blurry on HiDPI

[kmi]

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

kmi  changed:

   What|Removed |Added

 Resolution|DUPLICATE   |---
 Status|RESOLVED|REOPENED

--- Comment #6 from kmi  ---
Not a dupe. The other bug is about the title bar buttons (those have been
fixed). This is about OK/Cancel buttons in preferences.

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

[yakuake] [Bug 407726] Button icons blurry on HiDPI

[kmi]

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

--- Comment #5 from kmi  ---
(In reply to Nate Graham from comment #2)

> Let me know if you need a hand with anything.

You could merge https://phabricator.kde.org/D19237 if nobody else does.

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

[yakuake] [Bug 407726] Button icons blurry on HiDPI

[kmi]

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

--- Comment #3 from kmi  ---
(In reply to Nate Graham from comment #2)

> Let me know if you need a hand with anything.

Move Yakuake to GitLab, so I can have a nice web-based editor than to fight
with Git for a single line. :p

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

[yakuake] [Bug 407726] Button icons blurry on HiDPI

[kmi]

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

kmi  changed:

   What|Removed |Added

   Assignee|h...@kde.org|n...@kde.org

--- Comment #1 from kmi  ---
I hope assigning this bug to Nate is OK. He's done much HiDPI work as far as I
can see.

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

[yakuake] [Bug 407726] New: Button icons blurry on HiDPI

[kmi]

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

Bug ID: 407726
   Summary: Button icons blurry on HiDPI
   Product: yakuake
   Version: 3.0.5
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: h...@kde.org
  Reporter: kamika...@web.de
  Target Milestone: ---

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

Both the title bar buttons as well as OK/Cancel buttons in preferences are
blurry on HiDPI.

See attached screenshot.

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

[plasmashell] [Bug 407722] New: Hitting a global shortcut crashes parts of Plasma

[kmi]

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

Bug ID: 407722
   Summary: Hitting a global shortcut crashes parts of Plasma
   Product: plasmashell
   Version: 5.15.90
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: generic-crash
  Assignee: plasma-b...@kde.org
  Reporter: kamika...@web.de
  Target Milestone: 1.0

SUMMARY

Shortly after launching Plasma 5.16 beta, some part of Plasma either crashes or
hangs. Hitting shortcuts like Ctrl+Esc or PrintScr seems to trigger that issue
sooner.

User-visible problems so far are: KSNI systray icons vanish, Ctrl+Esc,
PrintScr, etc. no longer work.

There's no crash error message. I tried running plasmashell from terminal an on
occasion I get

QQuickItem::stackAfter: Cannot stack
StatusNotifierItem_QMLTYPE_288(0x55766e4bd070, parent=0x55766d6e8400,
geometry=0,0 0x0) after StatusNotifierItem_QMLTYPE_288(0x55766dd3f790), which
must be a sibling

after a while.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: openSUSE Tumbleweed, x64, all updates as of 19 May 2019.
(available in About System)
KDE Plasma Version: 5.15.90
KDE Frameworks Version: 5.57.0
Qt Version: 5.12.3

ADDITIONAL INFORMATION

X11 session

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

[www.kde.org] [Bug 406756] Update KDE Apps 19.04 announcement to link to Flathub as well

[kmi]

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

--- Comment #9 from kmi  ---
(In reply to Jonathan Riddell from comment #8)
> I look forward to you helping out with future announcements

Fix this one first.

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

[www.kde.org] [Bug 406756] Update KDE Apps 19.04 announcement to link to Flathub as well

[kmi]

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

--- Comment #7 from kmi  ---
(In reply to Jonathan Riddell from comment #6)


> Neither me nor the users who will install this software will know how to
> search through github for whatever is needed.

You're unable to look up e.g.
https://github.com/flathub/org.kde.okular/commits/master ? Seriously?
Well, you've got the info now. Correct your mistake, please.


> It is now too late to include it as the announcement was written over a week
> ago and has been translated and published.

No, it's not too late.


> Note the proprietary nature of the store is largely irrelevant

https://manifesto.kde.org/ happens do disagree with you.


> I am unaware of the licence or development model of flathub.

And yet you claim to care for Snap and Flatpak equally?
Flathub is 100% Free Software, therefore 100% aligned with KDE ideals.
It should get prioritized treatment over any proprietary alternative.

The announcement links to https://snapcraft.io/search?q=kde. Linking
https://flathub.org/apps/search/org.kde as well is the very least KDE should
do.

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

[www.kde.org] [Bug 406756] Update KDE Apps 19.04 announcement to link to Flathub as well

[kmi]

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

--- Comment #5 from kmi  ---
(In reply to Jonathan Riddell from comment #4)
> There's no version numers on he flathub packages so it's unclear if they are 
> updated or not.

Commits on Github are very clear on that.

Closed as intentional. This was you chance to disprove that you're giving
preferential treatment to Canonical's proprietary store. You didn't take you
chance. Says enough…

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

[www.kde.org] [Bug 406756] Update KDE Apps 19.04 announcement to link to Flathub as well

[kmi]

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

--- Comment #2 from kmi  ---
So what. The Snap box links to https://snapcraft.io/search?q=kde

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

[www.kde.org] [Bug 406756] New: Update KDE Apps 19.04 announcement to link to Flathub as well

[kmi]

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

Bug ID: 406756
   Summary: Update KDE Apps 19.04 announcement to link to Flathub
as well
   Product: www.kde.org
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kde-...@kde.org
  Reporter: kamika...@web.de
  Target Milestone: ---

KDE Applications 19.04 announcement only links to Canonical's proprietary Snap
Store despite the fact that 19.04 applications are also available from Flathub.

https://www.flathub.org/assets/themes/flathub/flathub-logo-toolbar.svg is the
necessary graphic.

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

[plasmashell] [Bug 405237] Crash after waking up from suspend

[kmi]

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

--- Comment #5 from kmi  ---
(In reply to Christoph Feck from comment #4)
> Could be related to bug 403971.

I also have use a wallpaper slideshow but not at an 0h0m0s interval.

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

[plasmashell] [Bug 405237] New: Crash after waking up from suspend

[kmi]

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

Bug ID: 405237
   Summary: Crash after waking up from suspend
   Product: plasmashell
   Version: 5.15.2
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: kamika...@web.de
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.15.2)

Qt Version: 5.12.0
Frameworks Version: 5.55.0
Operating System: Linux 4.20.12-1-default x86_64
Distribution: "openSUSE Tumbleweed"

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

I woke up the notebook with the power cord connected.

Doesn't happen regularly.

OS: openSUSE TW, x64, Intel graphics

The crash can be reproduced sometimes.

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

Thread 26 (Thread 0x7fce6a7fd700 (LWP 32138)):
#0  0x7fceec1f7ad9 in poll () at /lib64/libc.so.6
#1  0x7fcecefe00f1 in  () at /usr/lib64/libpulse.so.0
#2  0x7fcecefd1920 in pa_mainloop_poll () at /usr/lib64/libpulse.so.0
#3  0x7fcecefd1f6e in pa_mainloop_iterate () at /usr/lib64/libpulse.so.0
#4  0x7fcecefd2020 in pa_mainloop_run () at /usr/lib64/libpulse.so.0
#5  0x7fcecefe0039 in  () at /usr/lib64/libpulse.so.0
#6  0x7fceceef3e28 in  () at /usr/lib64/pulseaudio/libpulsecommon-12.2.so
#7  0x7fceeba48fab in start_thread () at /lib64/libpthread.so.0
#8  0x7fceec20269f in clone () at /lib64/libc.so.6

Thread 25 (Thread 0x7fce6b7fe700 (LWP 3895)):
#0  0x7fceeba4f03c in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fceec528613 in QWaitConditionPrivate::wait(QDeadlineTimer)
(deadline=..., this=0x5642a1717360) at thread/qwaitcondition_unix.cpp:146
#2  0x7fceec528613 in QWaitCondition::wait(QMutex*, QDeadlineTimer)
(this=, mutex=0x5642a2a38e30, deadline=...) at
thread/qwaitcondition_unix.cpp:225
#3  0x7fceec5286f9 in QWaitCondition::wait(QMutex*, unsigned long)
(this=0x5642a2e15868, mutex=0x5642a2a38e30, time=) at
../../include/QtCore/../../src/corelib/kernel/qdeadlinetimer.h:68
#4  0x7fcece6a2800 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7fcece6a6538 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#6  0x7fcece6a190d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#7  0x7fcece6a6592 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#8  0x7fcece6a190d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#9  0x7fcece6a6592 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#10 0x7fcece6a190d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#11 0x7fcece6a6592 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#12 0x7fcece6a190d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#13 0x7fcece6a6592 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#14 0x7fcece6a190d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#15 0x7fcece6a6592 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#16 0x7fcece6a190d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#17 0x7fcece6a6592 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#18 0x7fcece6a190d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#19 0x7fcece6a6592 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#20 0x7fcece6a190d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#21 0x7fcece6a6592 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#22 0x7fcece6a190d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#23 0x7fcece6a6592 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#24 0x7fcece6a190d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#25 0x7fcece6a6592 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#26 0x7fcece6a190d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#27 0x7fcece6a6592 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#28 0x7fcece6a190d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#29 0x7fcece6a6592 in  () at 

[Akonadi] [Bug 230199] Bookmarks via Akonadi should make use of Mozilla's Weave

[kmi]

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

kmi  changed:

   What|Removed |Added

 CC|kamika...@web.de|

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

[Akonadi] [Bug 388196] akonadi_control crash after login

[kmi]

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

--- Comment #3 from kmi  ---
(In reply to Daniel Vrátil from comment #2)
> Something weird in your setup. Can you check that all files in
> ~/.local/share/akonadi are owned by your user and writable?

As far as I can see, all files are owned by me and RW and even if they weren't,
shouldn't there be a PolKit prompt asking me to fix permissions for me instead
of crashing? 樂

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

[Akonadi] [Bug 388196] akonadi_control crash after login

[kmi]

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

kmi  changed:

   What|Removed |Added

 CC||kamika...@web.de

--- Comment #1 from kmi  ---
Apparently the same bug for me:

Application: akonadi_control (akonadi_control), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fb67e747800 (LWP 2636))]

Thread 3 (Thread 0x7fb66e7b7700 (LWP 2639)):
#0  0x7ffea83fc9d9 in ?? ()
#1  0x7ffea83fcbdc in clock_gettime ()
#2  0x7fb67d799876 in clock_gettime () from /lib64/libc.so.6
#3  0x7fb67dea59e1 in qt_clock_gettime (ts=0x7fb66e7b6ab0, clock=1) at
kernel/qelapsedtimer_unix.cpp:175
#4  do_gettime (frac=, sec=) at
kernel/qelapsedtimer_unix.cpp:166
#5  qt_gettime () at kernel/qelapsedtimer_unix.cpp:175
#6  0x7fb67dea4219 in QTimerInfoList::updateCurrentTime
(this=this@entry=0x7fb668004cf0) at kernel/qtimerinfo_unix.cpp:91
#7  0x7fb67dea4815 in QTimerInfoList::timerWait (this=0x7fb668004cf0,
tm=...) at kernel/qtimerinfo_unix.cpp:388
#8  0x7fb67dea5e3e in timerSourcePrepareHelper (timeout=0x7fb66e7b6b94,
src=) at kernel/qeventdispatcher_glib.cpp:161
#9  timerSourcePrepare (source=, timeout=0x7fb66e7b6b94) at
kernel/qeventdispatcher_glib.cpp:165
#10 0x7fb67bc9b739 in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#11 0x7fb67bc9c13b in ?? () from /usr/lib64/libglib-2.0.so.0
#12 0x7fb67bc9c32c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#13 0x7fb67dea60bb in QEventDispatcherGlib::processEvents
(this=0x7fb668000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#14 0x7fb67de5309b in QEventLoop::exec (this=this@entry=0x7fb66e7b6d70,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:140
#15 0x7fb67dca1e96 in QThread::exec (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:120
#16 0x7fb67e79a545 in ?? () from /usr/lib64/libQt5DBus.so.5
#17 0x7fb67dcaba67 in QThreadPrivate::start (arg=0x7fb67e814d60) at
thread/qthread_unix.cpp:367
#18 0x7fb67d479554 in start_thread () from /lib64/libpthread.so.0
#19 0x7fb67d78bccf in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7fb677144700 (LWP 2638)):
#0  0x7fb67d7812c9 in poll () from /lib64/libc.so.6
#1  0x7fb67b5becc7 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7fb67b5c08ea in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7fb6783216d9 in QXcbEventReader::run (this=0x5586eb30c9c0) at
qxcbconnection.h:409
#4  0x7fb67dcaba67 in QThreadPrivate::start (arg=0x5586eb30c9c0) at
thread/qthread_unix.cpp:367
#5  0x7fb67d479554 in start_thread () from /lib64/libpthread.so.0
#6  0x7fb67d78bccf in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7fb67e747800 (LWP 2636)):
[KCrash Handler]
#6  0x7fb67d6c908b in raise () from /lib64/libc.so.6
#7  0x7fb67d6b24e9 in abort () from /lib64/libc.so.6
#8  0x7fb67dc6a9ad in qt_message_fatal (context=..., message=...) at global/qlogging.cpp:1842
#9  QMessageLogger::fatal (this=this@entry=0x7ffea83f7c30,
msg=msg@entry=0x5586eae89518 "Cannot remove old log file '%s': %s") at
global/qlogging.cpp:880
#10 0x5586eae58cfd in akInit (appName=...) at
/usr/include/qt5/QtCore/qarraydata.h:206
#11 0x5586eae7ba62 in AkApplicationBase::init
(this=this@entry=0x7ffea83f7dd0) at /usr/include/qt5/QtCore/qstring.h:823
#12 0x5586eae58f68 in AkApplicationImpl::AkApplicationImpl
(loggingCategory=..., argv=0x7ffea83f7f38, argc=@0x7ffea83f7d4c: 1,
this=0x7ffea83f7dd0) at /usr/include/qt5/QtCore/qscopedpointer.h:52
#13 main (argc=, argv=0x7ffea83f7f38) at
/usr/src/debug/akonadi-server-18.08.1-1.1.x86_64/src/akonadicontrol/main.cpp:55
[Inferior 1 (process 2636) detached]

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

[marble] [Bug 397379] New: Download Region: Crash when changing zoom level

[kmi]

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

Bug ID: 397379
   Summary: Download Region: Crash when changing zoom level
   Product: marble
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: marble-b...@kde.org
  Reporter: kamika...@web.de
  Target Milestone: ---

Application: marble (2.2.20 (2.3 development version))

Qt Version: 5.11.1
Frameworks Version: 5.48.0
Operating System: Linux 4.17.12-1-default x86_64
Distribution: "openSUSE Tumbleweed"

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

Try to download a map region.

Change zoom level.

- Custom settings of the application:

VectorOSM maps

[Filler text because Dr Konqui insists on a minimum length.]

The crash can be reproduced every time.

-- Backtrace:
Application: Marble Virtual Globe (marble), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fc96e976940 (LWP 4252))]

Thread 8 (Thread 0x7fc8ee537700 (LWP 4264)):
#0  0x7fc9636708c8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fc96a57ceac in QWaitConditionPrivate::wait_relative(unsigned long)
(time=3, this=0x5571aec5acf0) at thread/qwaitcondition_unix.cpp:133
#2  0x7fc96a57ceac in QWaitConditionPrivate::wait(unsigned long)
(time=3, this=0x5571aec5acf0) at thread/qwaitcondition_unix.cpp:141
#3  0x7fc96a57ceac in QWaitCondition::wait(QMutex*, unsigned long)
(this=, mutex=0x5571ae1b8570, time=3) at
thread/qwaitcondition_unix.cpp:215
#4  0x7fc96a57532e in QThreadPoolThread::run() (this=0x5571ae926a90) at
../../include/QtCore/../../src/corelib/thread/qmutex.h:240
#5  0x7fc96a57c8ec in QThreadPrivate::start(void*) (arg=0x5571ae926a90) at
thread/qthread_unix.cpp:367
#6  0x7fc96366a554 in start_thread () at /lib64/libpthread.so.0
#7  0x7fc969c49ccf in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7fc8ed535700 (LWP 4262)):
#0  0x7fc9636708c8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fc96a57ceac in QWaitConditionPrivate::wait_relative(unsigned long)
(time=3, this=0x7fc8e4005850) at thread/qwaitcondition_unix.cpp:133
#2  0x7fc96a57ceac in QWaitConditionPrivate::wait(unsigned long)
(time=3, this=0x7fc8e4005850) at thread/qwaitcondition_unix.cpp:141
#3  0x7fc96a57ceac in QWaitCondition::wait(QMutex*, unsigned long)
(this=, mutex=0x5571ae0d2e70, time=3) at
thread/qwaitcondition_unix.cpp:215
#4  0x7fc96a57532e in QThreadPoolThread::run() (this=0x7fc8e4005650) at
../../include/QtCore/../../src/corelib/thread/qmutex.h:240
#5  0x7fc96a57c8ec in QThreadPrivate::start(void*) (arg=0x7fc8e4005650) at
thread/qthread_unix.cpp:367
#6  0x7fc96366a554 in start_thread () at /lib64/libpthread.so.0
#7  0x7fc969c49ccf in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7fc8edd36700 (LWP 4261)):
#0  0x7fc9636708c8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fc96a57ceac in QWaitConditionPrivate::wait_relative(unsigned long)
(time=3, this=0x7fc8e0005740) at thread/qwaitcondition_unix.cpp:133
#2  0x7fc96a57ceac in QWaitConditionPrivate::wait(unsigned long)
(time=3, this=0x7fc8e0005740) at thread/qwaitcondition_unix.cpp:141
#3  0x7fc96a57ceac in QWaitCondition::wait(QMutex*, unsigned long)
(this=, mutex=0x5571ae0d2e70, time=3) at
thread/qwaitcondition_unix.cpp:215
#4  0x7fc96a57532e in QThreadPoolThread::run() (this=0x7fc8e00054e0) at
../../include/QtCore/../../src/corelib/thread/qmutex.h:240
#5  0x7fc96a57c8ec in QThreadPrivate::start(void*) (arg=0x7fc8e00054e0) at
thread/qthread_unix.cpp:367
#6  0x7fc96366a554 in start_thread () at /lib64/libpthread.so.0
#7  0x7fc969c49ccf in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7fc8ef539700 (LWP 4258)):
#0  0x7fc9636704dc in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fc8f00807fb in  () at /usr/lib64/dri/i965_dri.so
#2  0x7fc8f0080527 in  () at /usr/lib64/dri/i965_dri.so
#3  0x7fc96366a554 in start_thread () at /lib64/libpthread.so.0
#4  0x7fc969c49ccf in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7fc949129700 (LWP 4257)):
#0  0x7fc96085d216 in  () at /usr/lib64/libglib-2.0.so.0
#1  0x7fc96085f733 in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#2  0x7fc9608601fb in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7fc9608603ec in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7fc96a764b3b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fc93c000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7fc96a714b3b in
QEventLoop::exec(QFlags) (this=0x7fc949128c80,
flags=...) at 

[frameworks-kio] [Bug 189482] Add a rename option in the open/save file dialog

[kmi]

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

kmi <kamika...@web.de> changed:

   What|Removed |Added

 CC||kamika...@web.de

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

[ksysguard] [Bug 393066] New: No Swap partition but Swap graph present

[kmi]

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

Bug ID: 393066
   Summary: No Swap partition but Swap graph present
   Product: ksysguard
   Version: 5.12.4
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: ksysguard
  Assignee: ksysguard-b...@kde.org
  Reporter: kamika...@web.de
  Target Milestone: ---

Apparently previously fixed in Plasma 4 (Bug 245762), it has returned in Plasma
5:

I have no Swap partition but a Swap graph is shown anyways (always at zero).

Expected behaviour: Don't show that graph at all.

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

[plasmashell] [Bug 392523] Run apps on dedicated GPU

[kmi]

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

kmi <kamika...@web.de> changed:

   What|Removed |Added

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

--- Comment #2 from kmi <kamika...@web.de> ---
(In reply to David Edmundson from comment #1)

> It should be implemented.

You're right. There are three problems though:

1. is that the context menu entry is not even there most of the time (details
below)

2. in cases where it's there, it's a bit hard to discover (hidden behind an
"Advanced" button in the third tab of a properties window)

3. The setting is not remembered.

> The UI is in right click -> edit application   this way your preference
> persists rather than having to right click every time.

Icon-only Task Manager: Only "Unpin" and "Settings".

Frequent Apps in Dashboard: "Forget" and "Add to Favorites".

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

[plasmashell] [Bug 392523] New: Run apps on dedicated GPU

[kmi]

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

Bug ID: 392523
   Summary: Run apps on dedicated GPU
   Product: plasmashell
   Version: master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: kamika...@web.de
CC: plasma-b...@kde.org
  Target Milestone: 1.0

If a second GPU is present, the context menu of an application's icon should
display the option to run it using the dedicated GPU. If possible, it should be
a generic feature that works across all application launchers – K menu, panel,
desktop icons.

switcheroo-control  is a D-Bus
service to check the availability of a second GPU.

The same feature in Gnome

required only 51 lines of code.

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

[drkonqi] [Bug 392115] New: Crash while diagnosing another crash

[kmi]

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

Bug ID: 392115
   Summary: Crash while diagnosing another crash
   Product: drkonqi
   Version: 5.12.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: kamika...@web.de
  Target Milestone: ---

Application: drkonqi (drkonqi), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f250563b440 (LWP 11529))]

Thread 3 (Thread 0x7f24ea012700 (LWP 11535)):
#0  0x7f2500c25179 in poll () from /lib64/libc.so.6
#1  0x7f24fcaca429 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f24fcaca53c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f2501563a2b in QEventDispatcherGlib::processEvents
(this=0x7f24e4000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f250150a95a in QEventLoop::exec (this=this@entry=0x7f24ea011d90,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7f2501331baa in QThread::exec (this=) at
thread/qthread.cpp:522
#6  0x7f2502bdaa35 in ?? () from /usr/lib64/libQt5DBus.so.5
#7  0x7f2501336ba0 in QThreadPrivate::start (arg=0x7f2502e4ad60) at
thread/qthread_unix.cpp:376
#8  0x7f24ff0c259b in start_thread () from /lib64/libpthread.so.0
#9  0x7f2500c2fa1f in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f24f3618700 (LWP 11531)):
#0  0x7f2500c25179 in poll () from /lib64/libc.so.6
#1  0x7f24fbd47387 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7f24fbd48faa in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7f24f65e50a9 in QXcbEventReader::run (this=0x5556dde481c0) at
qxcbconnection.cpp:1370
#4  0x7f2501336ba0 in QThreadPrivate::start (arg=0x5556dde481c0) at
thread/qthread_unix.cpp:376
#5  0x7f24ff0c259b in start_thread () from /lib64/libpthread.so.0
#6  0x7f2500c2fa1f in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f250563b440 (LWP 11529)):
[KCrash Handler]
#6  BacktraceLine::type (this=) at
/usr/src/debug/drkonqi5-5.12.3-1.1.x86_64/src/parser/backtraceline.h:59
#7  GdbHighlighter::highlightBlock (this=this@entry=0x5556de4abdb0, text=...)
at /usr/src/debug/drkonqi5-5.12.3-1.1.x86_64/src/gdbhighlighter.cpp:80
#8  0x7f2501be79e8 in QSyntaxHighlighterPrivate::reformatBlock
(this=this@entry=0x5556de38c720, block=...) at text/qsyntaxhighlighter.cpp:203
#9  0x7f2501be7b80 in QSyntaxHighlighterPrivate::reformatBlocks
(this=0x5556de38c720, from=, charsRemoved=,
charsAdded=15) at text/qsyntaxhighlighter.cpp:184
#10 0x7f250153a26a in QMetaObject::activate
(sender=sender@entry=0x5556de08def0, signalOffset=,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffc43e72590)
at kernel/qobject.cpp:3766
#11 0x7f250153a977 in QMetaObject::activate
(sender=sender@entry=0x5556de08def0, m=m@entry=0x7f2502115d00
,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffc43e72590)
at kernel/qobject.cpp:3628
#12 0x7f2501e35bea in QTextDocument::contentsChange
(this=this@entry=0x5556de08def0, _t1=, _t2=,
_t3=) at .moc/moc_qtextdocument.cpp:383
#13 0x7f2501ba66a1 in QTextDocumentPrivate::finishEdit
(this=0x5556de105a90) at text/qtextdocument_p.cpp:1217
#14 0x7f2501ba68dc in QTextDocumentPrivate::endEditBlock (this=) at text/qtextdocument_p.cpp:1201
#15 0x7f2501bd2874 in QTextCursor::endEditBlock
(this=this@entry=0x7ffc43e72638) at text/qtextcursor.cpp:2510
#16 0x7f250245f93c in QWidgetTextControlPrivate::append
(this=0x5556de105930, text=..., format=format@entry=Qt::AutoText) at
widgets/qwidgettextcontrol.cpp:3136
#17 0x7f250245f9ae in QWidgetTextControl::append (this=,
text=...) at widgets/qwidgettextcontrol.cpp:3142
#18 0x7f250244a059 in QTextEdit::append (this=, text=...) at
widgets/qtextedit.cpp:2624
#19 0x5556dc9a12e0 in BacktraceWidget::backtraceNewLine (this=, line=...) at
/usr/src/debug/drkonqi5-5.12.3-1.1.x86_64/src/backtracewidget.cpp:316
#20 0x7f250153a36c in QtPrivate::QSlotObjectBase::call (a=0x7ffc43e72800,
r=0x5556de087c90, this=0x5556de08bd00) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:378
#21 QMetaObject::activate (sender=sender@entry=0x5556ddf99e30,
signalOffset=, local_signal_index=local_signal_index@entry=1,
argv=argv@entry=0x7ffc43e72800) at kernel/qobject.cpp:3749
#22 0x7f250153a977 in QMetaObject::activate
(sender=sender@entry=0x5556ddf99e30, m=m@entry=0x5556dcc235c0
,
local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffc43e72800)
at kernel/qobject.cpp:3628
#23 0x5556dc9edde5 in BacktraceGenerator::newLine
(this=this@entry=0x5556ddf99e30, _t1=...) at
/usr/src/debug/drkonqi5-5.12.3-1.1.x86_64/build/src/drkonqi_autogen/EWIEGA46WW/moc_backtracegenerator.cpp:201
#24 0x5556dc9a54da in BacktraceGenerator::slotReadInput

[drkonqi] [Bug 392114] New: No bug report address, can't report DrKonqi crashes

[kmi]

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

Bug ID: 392114
   Summary: No bug report address, can't report DrKonqi crashes
   Product: drkonqi
   Version: 5.12.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: kamika...@web.de
  Target Milestone: ---

#344404 says it's fixed but I just had DrKonqi 5.12.3 crash and get the same
error.

openSUSE TW, lastest updates as of 21 March 2018.

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

[plasma-nm] [Bug 352326] Plasma nm applet keeps spinning even after wifi network is connected

[kmi]

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

--- Comment #76 from kmi <kamika...@web.de> ---
If Plasma-NM cannot do anything to prevent that a totally unrelated widget
affects how Plasma-NM works, IMO the bug's component should be changed to
Plasma or whatever is responsible for separating Plasna widgets from each other
instead of closing the bug.

So is it a Plasma Desktop bug that Weather affects Plasma-NM? Plasma Framework?

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

[Akonadi] [Bug 387926] Release version 17.12: Sending a mail with SMTP fails with: org.kde.pim.ksmtp: Socket error: 1

[kmi]

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

kmi <kamika...@web.de> changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1
 CC||kamika...@web.de
Version|unspecified |5.7.0

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

[Akonadi] [Bug 387926] Release version 17.12: Sending a mail with SMTP fails with: org.kde.pim.ksmtp: Socket error: 1

[kmi]

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

kmi <kamika...@web.de> changed:

   What|Removed |Added

 CC||tro...@free.fr

--- Comment #3 from kmi <kamika...@web.de> ---
*** Bug 388005 has been marked as a duplicate of this bug. ***

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

[kmail2] [Bug 388005] Impossible to send emails : "Connection to server interrupted".

[kmi]

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

kmi <kamika...@web.de> changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #2 from kmi <kamika...@web.de> ---


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

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

[kmail2] [Bug 388005] Impossible to send emails : "Connection to server interrupted".

[kmi]

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

kmi <kamika...@web.de> changed:

   What|Removed |Added

 CC||kamika...@web.de
Summary|Impossible to send emails : |Impossible to send emails :
   |"Connection to serveur  |"Connection to server
   |interrupted".   |interrupted".

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

[frameworks-frameworkintegration] [Bug 383708] Duplicate launcher icons under Gnome

[kmi]

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

kmi <kamika...@web.de> changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #3 from kmi <kamika...@web.de> ---
(In reply to David Edmundson from comment #1)
> Is that gnome wayland or X?

Both.

> Can you also check with dolphin. 
> I imagine they're doing .desktop name to ID mapping; which means every app
> moving to the newer org.kde.kmail "standard" naming. 
> 
> I know dolphin will be correct.

Same bug with Dolphin.

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

[marble] [Bug 384330] New: Main window has fixed size under Gnome – can't maximize

[kmi]

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

Bug ID: 384330
   Summary: Main window has fixed size under Gnome – can't
maximize
   Product: marble
   Version: 2.1 (KDE Applications 16.12)
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: marble-b...@kde.org
  Reporter: kamika...@web.de
  Target Milestone: ---

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

Main window has fixed size under Gnome – can't maximize.

See screenshot.

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

[frameworks-frameworkintegration] [Bug 383709] New: Systray icons under Gnome only expose XEmbed, not KSNI

[kmi]

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

Bug ID: 383709
   Summary: Systray icons under Gnome only expose XEmbed, not KSNI
   Product: frameworks-frameworkintegration
   Version: 5.36.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdelibs-b...@kde.org
  Reporter: kamika...@web.de
  Target Milestone: ---

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

KDE applications only use XEmbed-based systray icons under Gnome, whether
https://extensions.gnome.org/extension/615/appindicator-support/ is installed
or not.
Currently that's only a minor inconvenience (visual inconsistency, two context
menus can be open at the same time – see attached screenshot) but it gets
worse:
The upcoming Gnome version (3.26) will completely remove support for XEmbed
systray icons, therefore the above mentioned Gnome extension will be the last
remaining way to properly use non-Gnome applications with systray icons under
Gnome.

Only KDE applications are affected. "Pure" Qt applications are not. My
screenshot shows QuiteRSS (Qt) and KMail systray manus.

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

[frameworks-frameworkintegration] [Bug 383708] New: Duplicate launcher icons under Gnome

[kmi]

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

Bug ID: 383708
   Summary: Duplicate launcher icons under Gnome
   Product: frameworks-frameworkintegration
   Version: 5.36.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdelibs-b...@kde.org
  Reporter: kamika...@web.de
  Target Milestone: ---

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

After pinning a KDE application icon to the dock to serve as launcher, the
application spawns another icon when running.

How to:
* Launch Gnome
* Find a KDE application, e.g. KMail
* Right-click > Add to Favorites
* Launch that application

Result:
See attached screenshot

Only happens with KDE applications. "Pure" Qt applications are not affected.

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

[kdeconnect] [Bug 330536] Bluetooth device link

[kmi]

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

kmi <kamika...@web.de> changed:

   What|Removed |Added

 CC||kamika...@web.de

--- Comment #20 from kmi <kamika...@web.de> ---
(In reply to Saikrishna from comment #15)
> For the record, remote filesystem browsing will not work over the bluetooth
> backend because it uses SSHFS, which uses an IP network. It should be
> possible to implement FUSE in kdeconnect and transfer file information and
> payloads through kdeconnect itself.

I don't know if that's possible under Android but just for reference: Apple’s
Continuity negotiates things via Bluetooth LE but for actual file transfers
etc. is opens an Ad-hoc WiFi network.

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

[Breeze] [Bug 370425] No focus indicator on buttons with Breeze and Breeze dark GTK themes

[kmi]

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

kmi <kamika...@web.de> changed:

   What|Removed |Added

 Ever confirmed|0   |1
Version|5.8.0   |5.9.4
 CC||kamika...@web.de
 Status|UNCONFIRMED |CONFIRMED

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

[Breeze] [Bug 377008] Breeze scrollbar width with Firefox (version >= 52) broken (too wide)

[kmi]

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

kmi <kamika...@web.de> changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 CC||kamika...@web.de
 Ever confirmed|0   |1

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

[kdeconnect] [Bug 377319] New: Integrate PulseAudio volume control (e.g. Reverb)

[kmi]

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

Bug ID: 377319
   Summary: Integrate PulseAudio volume control (e.g. Reverb)
   Product: kdeconnect
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: android-application
  Assignee: albertv...@gmail.com
  Reporter: kamika...@web.de
  Target Milestone: ---

Would be cool if KDE Connect could set the volume not only for MPRIS media
players. There exists at least one FOSS project to implement a PulseAudio
mixer: https://github.com/goozler/reverb

If feasible, KDE Connect should implement that functionality (maybe by
importing aforementioned GPLed code).

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

[plasma4] [Bug 176872] Add 'MinimizeAll' widget ('Show Desktop' is not enough for everybody)

[kmi]

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

kmi <kamika...@web.de> changed:

   What|Removed |Added

 CC||kamika...@web.de
   Version Fixed In||5.8.0
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

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

[kwin] [Bug 341071] "menu button in title bar" does not work

[kmi]

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

kmi <kamika...@web.de> changed:

   What|Removed |Added

   Version Fixed In||5.9.0
 Resolution|WONTFIX |FIXED
 CC||kamika...@web.de

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

[kded-appmenu] [Bug 351813] Plasma 5 port missing

[kmi]

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

kmi <kamika...@web.de> changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
   Version Fixed In||5.9.0

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

[kded-appmenu] [Bug 326868] kde deamon crashed

[kmi]

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

kmi <kamika...@web.de> changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |UNMAINTAINED
 CC||kamika...@web.de

--- Comment #17 from kmi <kamika...@web.de> ---
This is for the old Plasma 4 implementation. Plasma 5.9 has a new
implementation of the menu bar.

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

[kded-appmenu] [Bug 329607] no activities submenu in right-click application menu

[kmi]

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

kmi <kamika...@web.de> changed:

   What|Removed |Added

 Resolution|--- |UNMAINTAINED
 Status|UNCONFIRMED |RESOLVED
 CC||kamika...@web.de

--- Comment #5 from kmi <kamika...@web.de> ---
This is for the old Plasma 4 implementation. Plasma 5.9 has a new
implementation of the menu bar.

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

[kded-appmenu] [Bug 325010] Firefox hang and kded crash with auto-hiding top menu

[kmi]

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

kmi <kamika...@web.de> changed:

   What|Removed |Added

 CC||kamika...@web.de
 Resolution|--- |UNMAINTAINED
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from kmi <kamika...@web.de> ---
This is for the old Plasma 4 implementation. Plasma 5.9 has a new
implementation of the menu bar.

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

[kded-appmenu] [Bug 333290] appmenu krunner plugin freezes when active window doesn't export dbus menus

[kmi]

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

kmi <kamika...@web.de> changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |UNMAINTAINED
 CC||kamika...@web.de

--- Comment #1 from kmi <kamika...@web.de> ---
This is for the old Plasma 4 implementation. Plasma 5.9 has a new
implementation of the menu bar.

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

[kded-appmenu] [Bug 331439] kde session hangs when konqueror/rekonq interacts with kcookiejar

[kmi]

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

kmi <kamika...@web.de> changed:

   What|Removed |Added

 Resolution|--- |UNMAINTAINED
 Status|UNCONFIRMED |RESOLVED
 CC||kamika...@web.de

--- Comment #9 from kmi <kamika...@web.de> ---
This is for the old Plasma 4 implementation. Plasma 5.9 has a new
implementation of the menu bar.

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

[kded-appmenu] [Bug 314979] AppMenu TopMenuBar positioned oddly

[kmi]

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

kmi <kamika...@web.de> changed:

   What|Removed |Added

 CC||kamika...@web.de
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |UNMAINTAINED

--- Comment #48 from kmi <kamika...@web.de> ---
This is for the old Plasma 4 implementation. Plasma 5.9 has a new
implementation of the menu bar.

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

[kde] [Bug 374808] Dependency on QtWebEngine might make KDE non-(free/libre)

[kmi]

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

kmi <kamika...@web.de> changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||kamika...@web.de
 Resolution|--- |INVALID

--- Comment #3 from kmi <kamika...@web.de> ---
Numerous Linux distributors reviewed the code base and came to the conclusion
that it's fully free software.

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

[plasmashell] [Bug 360388] [Trash widget] add a desktop view

[kmi]

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

kmi <kamika...@web.de> changed:

   What|Removed |Added

 CC||kamika...@web.de

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

[Spectacle] [Bug 373167] Plain Qt file picker instead of KDE's

[kmi]

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

kmi <kamika...@web.de> changed:

   What|Removed |Added

 CC||kamika...@web.de

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

[Spectacle] [Bug 373167] New: Plain Qt file picker instead of KDE's

[kmi]

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

Bug ID: 373167
   Summary: Plain Qt file picker instead of KDE's
   Product: Spectacle
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: m...@baloneygeek.com
  Reporter: kamika...@web.de
  Target Milestone: ---

For whatever reason Spectacle uses the plain Qt file picker when Saving As and
not KDE's native one. This happens only with Spectacle and no other KDE
application, so I doubt it's my fault.

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

[Breeze] [Bug 373148] New: No Breeze icon for Marble

[kmi]

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

Bug ID: 373148
   Summary: No Breeze icon for Marble
   Product: Breeze
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Icons
  Assignee: visual-des...@kde.org
  Reporter: kamika...@web.de
CC: kain...@gmail.com
  Target Milestone: ---

Marble still uses an Oxygen icon. The Breeze set does not ship an icon for
Marble.

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

[kwin] [Bug 371494] Support color temperature adjustments in Wayland (like Redshift in X11 or f.lux)

[kmi]

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

kmi <kamika...@web.de> changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED
 CC||kamika...@web.de

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

[Breeze] [Bug 370981] New: Can't enter LUKS password

[kmi via KDE Bugzilla]

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

Bug ID: 370981
   Summary: Can't enter LUKS password
   Product: Breeze
   Version: 5.8.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Plymouth
  Assignee: plasma-de...@kde.org
  Reporter: kamika...@web.de
CC: sit...@kde.org

I have a LUKS crypt setup. Using the Plymouth Breeze theme, no text input field
is shown. I have to hit ESC and enter the password in text mode.

Reproducible: Always

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

[plasmashell] [Bug 370490] Copyright violation in sddm theme

[kmi via KDE Bugzilla]

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

--- Comment #2 from kmi <kamika...@web.de> ---
Created attachment 101542
  --> https://bugs.kde.org/attachment.cgi?id=101542=edit
Free replacement

Here's a replacement with this guy:
https://commons.wikimedia.org/wiki/File:Giorgis.jpg

That photo is freely licensed, incl CC and LGPL, just include the attribution
somewhere (like the commit message).

PS: Next time use PNG for the preview image. An image that's mostly a flat
color compresses better that way.

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

[plasmashell] [Bug 370490] New: Copyright violation in sddm theme

[kmi via KDE Bugzilla]

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

Bug ID: 370490
   Summary: Copyright violation in sddm theme
   Product: plasmashell
   Version: master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: Theme - Breeze
  Assignee: visual-des...@kde.org
  Reporter: kamika...@web.de
CC: plasma-b...@kde.org

sddm-theme/face1.jpeg (sddm-theme/breeze.jpg in turn includes a thumbnail of
that) is a copyrighted photo of that guy:
http://how-i-met-your-mother.wikia.com/wiki/Ted_Mosby

Reproducible: Always



Expected Results:  
Remove it ASAP

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

[plasmashell] [Bug 365617] pinned chromium launcher disappears

[kmi via KDE Bugzilla]

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

kmi <kamika...@web.de> changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1
 CC||kamika...@web.de
Version|5.7.1   |5.8.0

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

[frameworks-baloo] [Bug 369476] New: "balooctl status" doesn't display the current file

[kmi via KDE Bugzilla]

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

Bug ID: 369476
   Summary: "balooctl status" doesn't display the current file
   Product: frameworks-baloo
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: balooctl
  Assignee: pinak.ah...@gmail.com
  Reporter: kamika...@web.de

The current output looks like this:

> balooctl status
Baloo File Indexer is running
Indexer state: Indexing file content
Indexed 33634 / 34200 files
Current size of index is 97,84 MiB


An additional line that shows which file exactly is currently being indexed,
would be great. Then I could report which files makes baloo_file_extractor go
nuts.

Reproducible: Always

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

[frameworks-baloo] [Bug 369470] New: Typo in balooshow -h

[kmi via KDE Bugzilla]

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

Bug ID: 369470
   Summary: Typo in balooshow -h
   Product: frameworks-baloo
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: pinak.ah...@gmail.com
  Reporter: kamika...@web.de

balooshow -h prints the line

-i Inode number of the fiel to show

That's "file" not "fiel".

Version 5.26 here.

Reproducible: Always

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