[Falkon] [Bug 398354] Sometimes when I switch tabs, the browser window does not refresh

[David Rosca]

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

--- Comment #1 from David Rosca  ---
Does it also happen without compositing window manager?

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

[digikam] [Bug 398387] New: Ability to step through video frame by frame

[bugzilla_noreply]

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

Bug ID: 398387
   Summary: Ability to step through video frame by frame
   Product: digikam
   Version: 6.0.0
  Platform: Appimage
OS: All
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: Preview-Video
  Assignee: digikam-bugs-n...@kde.org
  Reporter: tungau...@yahoo.com
  Target Milestone: ---

Implement a button or shortcut to step through video frames in the Preview
window.
Something similar to the "s" command from ffplay.
Thank you!

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

[digikam] [Bug 398386] New: Allow video frame to be saved as picture

[bugzilla_noreply]

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

Bug ID: 398386
   Summary: Allow video frame to be saved as picture
   Product: digikam
   Version: 6.0.0
  Platform: Appimage
OS: All
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: Preview-Video
  Assignee: digikam-bugs-n...@kde.org
  Reporter: tungau...@yahoo.com
  Target Milestone: ---

>From the Video Preview window to have the option to save the current frame as a
picture in a given album.

Thanks for such a great piece of software.

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

[kpat] [Bug 392946] Hi-DPI cards too small to use.

[TonyP]

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

--- Comment #3 from TonyP  ---
(In reply to Albert Astals Cid from comment #2)
> There's no attached screenshot?

Not sure how a screenshot would help. Imagine a playing surface. Imagine cards
that are too tiny to read whats on them. It looks like that.

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

[plasmashell] [Bug 398117] plasmashell huge memory usage with flooding notifications

[GSC]

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

--- Comment #6 from GSC  ---
It' s just that simple text only electron notification sent like:

let myNotification = new Notification('Title', {
body: 'Lorem Ipsum Dolor Sit Amet'
  })

  myNotification.onclick = () => {
console.log('Notification clicked')
  }

A single program would send a error notification every 3 seconds. But I have a
bunch of them monitoring many programs on servers. In rare cases I left the
computer for a long time and things went wrong I would see this. I would try
disabling notification history, I feel it would help. The ability to set a
history size would be better.

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

[plasma-nm] [Bug 398385] New: wi-fi connection loss while awaiking from the sleep mode

[Leo]

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

Bug ID: 398385
   Summary: wi-fi connection loss while awaiking from the sleep
mode
   Product: plasma-nm
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: editor
  Assignee: jgrul...@redhat.com
  Reporter: leo.wire...@gmail.com
  Target Milestone: ---

After awaiking from the sleep mode, system doesn't make any attempts to
reconnectto wi-fi. Unplugging wi-fi' USB cable and plugging it back required
every time to establish lost connection. No other way to initiate the
reconnection.

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

[frameworks-baloo] [Bug 375370] Unable to remove a folder from excludeFolders list

[S . Christian Collins]

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

--- Comment #7 from S. Christian Collins  ---
Bug still present in KDE neon based on Ubuntu 18.04.1 (Plasma 5.13.5,
Frameworks 5.49.0, Qt 5.11.1, Kernel 4.15.0-33-generic, 64-bit).

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

[kdevelop] [Bug 398056] Icons are too small (4k resolution display)

[Andrew Crouthamel]

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

--- Comment #24 from Andrew Crouthamel  ---
(In reply to Fabian Vogt from comment #19)
> (In reply to Friedrich W. H. Kossebau from comment #15)
> > (In reply to Christoph Feck from comment #13)
> > > What exactly is the difference between Qt::AA_UseHighDpiPixmaps and
> > > Qt::AA_EnableHighDpiScaling, and should both be enabled for proper HiDPI
> > > support? Most applications I see only set the former property.
> > 
> > Good question.
> > Not exactly sure, but I would bet both should be set for really good looking
> > UI currently for our legacy-based applications like KDevelop, which rely on
> > code done around low-dpi pixel sizes (think icon sizes referring to 16, 32
> > or 64 pixels per dimension), as still relied on in all(?) the QtWidget-based
> > KDE Frameworks modules.
> > From what I understood by reading the docs, Qt::AA_EnableHighDpiScaling
> > cares for scaling any QPainter commands and other pixel-based geometries.
> > While Qt::AA_UseHighDpiPixmaps makes sure that pixmaps which are rendered
> > for the unscaled pixel sizes are internally prepared for the real pixels
> > sizes when rendered in the end onto the real display.
> > But we indeed should consult some experts, not putting my hand here close to
> > any fire.
> > 
> > (Adding fvogt as potential expoert to cc: list)
> > Fabian, can you tell more?
> 
> It's complicated.
> 
> QPainter etc. scale all the time, but by default the devicePixelRatio is 1 so
> it has no effect (except on OS X). All AA_EnableHighDpiScaling does is set
> the
> devicePixelRatio according to the DPI of the monitor the application is on.
> 
> On Plasma on X11, where AA_EnableHighDpiScaling has no effect at all as it's
> overwritten using environment variables (QT_AUTO_SCREEN_SCALE_FACTOR and
> QT_SCREEN_SCALE_FACTORS).
> 
> AA_UseHighDpiPixmaps is important as it allows QPixmap with a
> devicePixelRatio
> of > 1.
> 
> So your guess is correct, both is the best option here.
> 
> > (In reply to Saverio from comment #9)
> > > Oh, ok. Sorry, I didn't understand xD
> > > So, I'll wait other possible solutions, thanks anyway :)
> > 
> > Saverio, as Kevin asked and linked, please test the Nigthly build of the
> > Windows version created after my commit. My fix was done as blind fix, just
> > done based on documentation and given it did not break things for me on my
> > lowdpi system :)

Should we start submitting patches to include both lines on all apps? Or is
there a list of "legacy" apps I could tackle?

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

[kdevelop] [Bug 398056] Icons are too small (4k resolution display)

[Andrew Crouthamel]

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

Andrew Crouthamel  changed:

   What|Removed |Added

 CC||andrew.crouthamel@kdemail.n
   ||et

--- Comment #23 from Andrew Crouthamel  ---
(In reply to Fabian Vogt from comment #19)
> (In reply to Friedrich W. H. Kossebau from comment #15)
> > (In reply to Christoph Feck from comment #13)
> > > What exactly is the difference between Qt::AA_UseHighDpiPixmaps and
> > > Qt::AA_EnableHighDpiScaling, and should both be enabled for proper HiDPI
> > > support? Most applications I see only set the former property.
> > 
> > Good question.
> > Not exactly sure, but I would bet both should be set for really good looking
> > UI currently for our legacy-based applications like KDevelop, which rely on
> > code done around low-dpi pixel sizes (think icon sizes referring to 16, 32
> > or 64 pixels per dimension), as still relied on in all(?) the QtWidget-based
> > KDE Frameworks modules.
> > From what I understood by reading the docs, Qt::AA_EnableHighDpiScaling
> > cares for scaling any QPainter commands and other pixel-based geometries.
> > While Qt::AA_UseHighDpiPixmaps makes sure that pixmaps which are rendered
> > for the unscaled pixel sizes are internally prepared for the real pixels
> > sizes when rendered in the end onto the real display.
> > But we indeed should consult some experts, not putting my hand here close to
> > any fire.
> > 
> > (Adding fvogt as potential expoert to cc: list)
> > Fabian, can you tell more?
> 
> It's complicated.
> 
> QPainter etc. scale all the time, but by default the devicePixelRatio is 1 so
> it has no effect (except on OS X). All AA_EnableHighDpiScaling does is set
> the
> devicePixelRatio according to the DPI of the monitor the application is on.
> 
> On Plasma on X11, where AA_EnableHighDpiScaling has no effect at all as it's
> overwritten using environment variables (QT_AUTO_SCREEN_SCALE_FACTOR and
> QT_SCREEN_SCALE_FACTORS).
> 
> AA_UseHighDpiPixmaps is important as it allows QPixmap with a
> devicePixelRatio
> of > 1.
> 
> So your guess is correct, both is the best option here.
> 
> > (In reply to Saverio from comment #9)
> > > Oh, ok. Sorry, I didn't understand xD
> > > So, I'll wait other possible solutions, thanks anyway :)
> > 
> > Saverio, as Kevin asked and linked, please test the Nigthly build of the
> > Windows version created after my commit. My fix was done as blind fix, just
> > done based on documentation and given it did not break things for me on my
> > lowdpi system :)

Should we start submitting patches to include both lines on all apps? Or is
there a list of "legacy" apps I could tackle?

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

[kate] [Bug 371001] Kate opens new window rather than tab if on different virtual desktop

[Andrew Crouthamel]

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

--- Comment #2 from Andrew Crouthamel  ---
Hi there! I'm a bug triager from the KDE Bugsquad.

I tested this on Kate 18.08 and was able to confirm the behavior you reported.
Developers, is this expected behavior now?

KDE Plasma Version: 5.13.4
KDE Frameworks Version: 5.49.0
Qt Version: 5.11.1

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

[LabPlot2] [Bug 398342] ProjectImportTest segfaults while loading Excel file

[awilfox]

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

--- Comment #2 from A. Wilcox (awilfox)  ---
awilcox on gwyn [pts/15 Sat 8 1:57] labplot-2.5.0:
tests/import_export/project/projectimporttest
* Start testing of ProjectImportTest *
Config: Using QtTest library 5.9.6, Qt 5.9.6 (power64-big_endian-lp64 shared
(dynamic) debug build; by GCC 6.4.0)
PASS   : ProjectImportTest::initTestCase()
QDEBUG : ProjectImportTest::testOrigin01() "Starting the import of
/usr/src/packages/user/labplot/src/labplot-2.5.0/tests/import_export/project/data/origin8_test_tree_import.opj"
OriginProjectParser::load()

= Received signal, dumping stack ==
GNU gdb (GDB) 8.2
Copyright (C) 2018 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 "powerpc64-foxkit-linux-musl".
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".
Attaching to process 25556
[New LWP 25557]
[New LWP 25558]
__cp_end () at src/thread/powerpc64/syscall_cp.s:32
(gdb) 
Thread 3 (LWP 25558):
#0  __cp_end () at src/thread/powerpc64/syscall_cp.s:32
No locals.
#1  0x3fffbd7642e4 in __syscall_cp_c (nr=128, u=2, v=70367527851920, w=0,
x=0, y=0, z=0) at src/thread/pthread_cancel.c:35
self = 
r = 
st = 0
#2  0x3fffbd7630d8 in __syscall_cp (nr=, u=,
v=, w=, x=, y=,
z=)
at src/thread/__syscall_cp.c:20
No locals.
#3  0x3fffbd7631f4 in __timedwait_cp (addr=0x3fffb7805804, val=, clk=, at=, priv=128) at
src/thread/__timedwait.c:31
r = 
to = {tv_sec = 299, tv_nsec = 99168}
top = 
#4  0x3fffbd70d028 in __pthread_cond_timedwait (c=0x3fffb99a4c28,
m=0x3fffb99a4c00, ts=0x3fffb78058d8) at src/thread/pthread_cond_timedwait.c:105
node = {prev = 0x0, next = 0x0, state = 0, barrier = 2, notify = 0x0}
e = 
seq = 2
clock = 1
cs = 0
shared = 0
oldstate = 
tmp = 
fut = 0x3fffb7805804
#5  0x3fffbb4816f8 in QWaitConditionPrivate::wait_relative (time=30,
this=0x3fffb99a4c00) at thread/qwaitcondition_unix.cpp:133
ti = {tv_sec = 5797241, tv_nsec = 374265993}
ti = 
#6  QWaitConditionPrivate::wait (time=30, this=0x3fffb99a4c00) at
thread/qwaitcondition_unix.cpp:141
code = 
code = 
#7  QWaitCondition::wait (this=, mutex=0x3fffb99a49f8,
time=30) at thread/qwaitcondition_unix.cpp:215
__PRETTY_FUNCTION__ = "bool QWaitCondition::wait(QMutex*, long unsigned
int)"
returnValue = 
#8  0x3fffbd6234d0 in QTest::WatchDog::run (this=0x3fffb99a49e0) at
qtestcase.cpp:988
t = 
locker = {val = 70367563106809}
__PRETTY_FUNCTION__ = "virtual void QTest::WatchDog::run()"
#9  0x3fffbb480c88 in QThreadPrivate::start (arg=0x3fffb99a49e0) at
thread/qthread_unix.cpp:368
__cb = {__f = 0x3fffbb47f04c , __x =
0x3fffb99a49e0, __next = 0x0}
thr = 0x3fffb99a49e0
data = 
#10 0x3fffbd76483c in start (p=0x3fffb7805a88) at
src/thread/pthread_create.c:147
self = 0x3fffb7805a88
#11 0x3fffbd7705a8 in __clone () at src/thread/powerpc64/clone.s:43
No locals.

Thread 2 (LWP 25557):
#0  __cp_end () at src/thread/powerpc64/syscall_cp.s:32
No locals.
#1  0x3fffbd764374 in __syscall_cp_c (nr=167, u=-1, v=0, w=0, x=0, y=0,
z=0) at src/thread/pthread_cancel.c:35
self = 
r = 
st = 0
#2  0x3fffbd7630d8 in __syscall_cp (nr=, u=,
v=, w=, x=, y=,
z=)
at src/thread/__syscall_cp.c:20
No locals.
#3  0x3fffbd7520b4 in poll (fds=, n=,
timeout=) at src/select/poll.c:10
No locals.
#4  0x3fffb9bec6e0 in _xcb_conn_wait (c=0x12d29bec0, cond=,
vector=0x0, count=0x0) at xcb_conn.c:479
ret = 
fd = {fd = 3, events = 1, revents = 0}
#5  0x3fffb9bef074 in xcb_wait_for_event (c=) at
xcb_in.c:697
ret = 0x0
#6  0x3fffb7bb9a98 in QXcbEventReader::run (this=0x3fffbd607a60) at
qxcbconnection.cpp:1330
event = 0x0
#7  0x3fffbb480c88 in QThreadPrivate::start (arg=0x3fffbd607a60) at
thread/qthread_unix.cpp:368
__cb = {__f = 0x3fffbb47f04c , __x =
0x3fffbd607a60, __next = 0x0}
thr = 0x3fffbd607a60
data = 
#8  0x3fffbd76483c in start (p=0x3fffb786ea88) at
src/thread/pthread_create.c:147
self = 0x3fffb786ea88
#9  0x3fffbd7705a8 in __clone () at src/thread/powerpc64/clone.s:43
No locals.

Thread 1 (LWP 25556):
#0  __cp_end () at src/thread/powerpc64/syscall_cp.s:32
No locals.
#1  0x3fffbd764374 in 

[Breeze] [Bug 382264] Black buttons unreadable on the black logout screen

[DeMus]

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

DeMus  changed:

   What|Removed |Added

 CC||jan.muss...@gmail.com

--- Comment #13 from DeMus  ---
Okay, so now there is a text file which should cure things. That is wonderful,
but what to do with it?
Where do I place it, how do I name it, should I run it once, every time I boot,
will it be read by the system. How does this work?
Sorry, but not every Linux user is an expert in these things.
Thank you.

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

[frameworks-kcmutils] [Bug 389585] Window is too small when KCMs are opened standalone (e.g. using `kcmshell5), and contents get cut off

[Andrew Crouthamel]

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

--- Comment #41 from Andrew Crouthamel  ---
I'd love to help, but this is honestly outside of my capabilities at the
moment. I'd be glad to work with someone and test though.

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

[kate] [Bug 398384] New: Recording activities doing in editor and applying them on text

[Piotr Mierzwinski]

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

Bug ID: 398384
   Summary: Recording activities doing in editor and applying them
on text
   Product: kate
   Version: 18.08.1
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: piotr.mierzwin...@gmail.com
  Target Milestone: ---

Would be nice to have possibility to record activities doing in editor and
apply them on text.
I mean special button triggering recording, second for stoping it and next for
apply on text. Last one would just run recorded macro to apply all recorded
activities on selected text or to all text to the end of file.

Such function is present in one of the most popular editor on Windows system. I
mean Notepad++.

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

[kate] [Bug 363765] Allow “Tab key inserts tab character” as tab key action

[Andrew Crouthamel]

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

Andrew Crouthamel  changed:

   What|Removed |Added

 CC||andrew.crouthamel@kdemail.n
   ||et
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #3 from Andrew Crouthamel  ---
Hi there from the Bugsquad!

This appears to have been fixed at some point between the last comment and the
latest version. I tested this with Kate 18.08 and there is now a "Tabulators"
option in the same area where you can select "Spaces".

Selecting "Tabulators" and using the Tab key successfully entered tab
characters, designated with a tiny >> icon.

Please let us know if you continue to have this issue. Thank you!

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

[kate] [Bug 398062] [Suggestion] Does kate have a function to automatically switch the syntax?

[Andrew Crouthamel]

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

Andrew Crouthamel  changed:

   What|Removed |Added

 CC||andrew.crouthamel@kdemail.n
   ||et
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #1 from Andrew Crouthamel  ---
Hi there from the Bugsquad!

I am not experiencing this bahavior. Kate does automatically select syntax
highlighting types based on file extension, including .zshrc. I tested this on
Kate 18.08 today successfully with a test.zshrc file I populated with an
example template. Please let us know if you continue to have this issue.

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

[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling

[Mark Jacobson]

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

Mark Jacobson  changed:

   What|Removed |Added

 CC||jacobsons...@gmail.com

--- Comment #51 from Mark Jacobson  ---
I can confirm this bug is still present as well. 

Gentoo using 4.18.6 kernel
Konsole 18.04.3
Desktop is at 4k

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

[kdeplasma-addons] [Bug 398383] New: Change font size to match that of Digital Clock

[Andrew Crouthamel]

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

Bug ID: 398383
   Summary: Change font size to match that of Digital Clock
   Product: kdeplasma-addons
   Version: 5.13.4
  Platform: Manjaro
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: weather
  Assignee: kosse...@kde.org
  Reporter: andrew.croutha...@kdemail.net
CC: plasma-b...@kde.org
  Target Milestone: ---

It would be great from a consistency standpoint if the temperature shown on the
panel were the same font size as Digital Clock. Or allow changing the font
size. I have the clock and weather next to each other on the panel so it's
pretty noticeable.

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

[frameworks-ktexteditor] [Bug 382075] Solarized light color schema is outdated or uses wrong colors

[Andrew Crouthamel]

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

Andrew Crouthamel  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/kte
   ||xteditor/d67dd570336e995ea4
   ||a7f2fbfcd47d05ad3a0eae
 Status|CONFIRMED   |RESOLVED

--- Comment #6 from Andrew Crouthamel  ---
Git commit d67dd570336e995ea4a7f2fbfcd47d05ad3a0eae by Andrew Crouthamel.
Committed on 07/09/2018 at 23:25.
Pushed by acrouthamel into branch 'master'.

Fix Solarized Light and Dark color schemes

Summary:
Solarized Light contrast was low. Upon investigation it was determined much of
the color scheme did not follow Solarized base 16 colors or rules. Color scheme
for both Dark and Light variants were adjusted to match the latest Solarized
color scheme release palette and [[
https://ethanschoonover.com/solarized/#usage-development | color interaction
rules ]]. Color schemes were also matched closely to the [[
https://github.com/altercation/vim-colors-solarized/blob/master/colors/solarized.vim
| Vim color scheme ]] created by the original Solarized author.

This is my first "frameworks" patch, so please let me know if I missed
anything.

This has also been added to KSyntaxHighlighting in D15340.

Solarized Light Before:
{F6241106}
Solarized Light After:
{F6241107}
Solarized Dark Before:
{F6241108}
Solarized Dark After:
{F6241109}

Test Plan: Open Kate with new rc files and inspect the Color settings. Open a
CPP file to review syntax highlighting.

Reviewers: #kate, #ktexteditor, #framework_syntax_highlighting, dhaumann

Reviewed By: #kate, #ktexteditor, #framework_syntax_highlighting, dhaumann

Subscribers: dhaumann, kwrite-devel, kde-frameworks-devel

Tags: #kate, #frameworks, #ktexteditor

Differential Revision: https://phabricator.kde.org/D15337

M  +9-9src/data/kateschemarc
M  +56   -38   src/data/katesyntaxhighlightingrc

https://commits.kde.org/ktexteditor/d67dd570336e995ea4a7f2fbfcd47d05ad3a0eae

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

[dolphin] [Bug 398382] New: Dolphin crashes when attempting to send file(s) to trash

[Gary Lindquist]

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

Bug ID: 398382
   Summary: Dolphin crashes when attempting to send file(s) to
trash
   Product: dolphin
   Version: 17.04.2
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: gdlvml...@gmail.com
CC: elvis.angelac...@kde.org
  Target Milestone: ---

Application: dolphin (17.04.2)

Qt Version: 5.6.2
Frameworks Version: 5.32.0
Operating System: Linux 4.4.143-65-default x86_64
Distribution: "openSUSE Leap 42.3"

-- Information about the crash:
- What I was doing when the application crashed:
Attempted to send 2 pdf files to trash first time; second time sent 1 pdf file
to trash.  Crashed both times.

- Unusual behavior I noticed:
Just before the attempt the KDE window manager crashed (desktop was black and
only thing showing was some knotes.  Rebooted the machine and then attempted
the deletion.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fde76f34900 (LWP 5560))]

Thread 5 (Thread 0x7fde46e80700 (LWP 5692)):
#0  0x7fde767fe30d in poll () at /lib64/libc.so.6
#1  0x7fde6bae6081 in  () at /usr/lib64/libpulse.so.0
#2  0x7fde6bad774c in pa_mainloop_poll () at /usr/lib64/libpulse.so.0
#3  0x7fde6bad7dbe in pa_mainloop_iterate () at /usr/lib64/libpulse.so.0
#4  0x7fde6bad7e70 in pa_mainloop_run () at /usr/lib64/libpulse.so.0
#5  0x7fde6bae5fe6 in  () at /usr/lib64/libpulse.so.0
#6  0x7fde677923f8 in  () at /usr/lib64/pulseaudio/libpulsecommon-9.0.so
#7  0x7fde6bf1f724 in start_thread () at /lib64/libpthread.so.0
#8  0x7fde76806e8d in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7fde4e75a700 (LWP 5563)):
#0  0x7fde767fa33d in read () at /lib64/libc.so.6
#1  0x7fde6b3d8750 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fde6b397e49 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fde6b3982a8 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7fde6b39842c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7fde70afb1ab in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#6  0x7fde70aa8bfb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#7  0x7fde708e3f5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8  0x7fde708e8a29 in  () at /usr/lib64/libQt5Core.so.5
#9  0x7fde6bf1f724 in start_thread () at /lib64/libpthread.so.0
#10 0x7fde76806e8d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7fde5d768700 (LWP 5562)):
#0  0x7fde767fe30d in poll () at /lib64/libc.so.6
#1  0x7fde6b398314 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fde6b39842c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fde70afb1ab in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fde70aa8bfb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fde708e3f5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fde70f0f295 in  () at /usr/lib64/libQt5DBus.so.5
#7  0x7fde708e8a29 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7fde6bf1f724 in start_thread () at /lib64/libpthread.so.0
#9  0x7fde76806e8d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7fde5f32f700 (LWP 5561)):
#0  0x7fde767fe30d in poll () at /lib64/libc.so.6
#1  0x7fde68f183c2 in  () at /usr/lib64/libxcb.so.1
#2  0x7fde68f19faf in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7fde6188a0d9 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7fde708e8a29 in  () at /usr/lib64/libQt5Core.so.5
#5  0x7fde6bf1f724 in start_thread () at /lib64/libpthread.so.0
#6  0x7fde76806e8d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7fde76f34900 (LWP 5560)):
[KCrash Handler]
#6  0x7fde45b692a7 in  () at
/usr/lib64/qt5/plugins/phonon4qt5_backend/phonon_gstreamer.so
#7  0x7fde45b694d2 in  () at
/usr/lib64/qt5/plugins/phonon4qt5_backend/phonon_gstreamer.so
#8  0x7fde45b6ae43 in  () at
/usr/lib64/qt5/plugins/phonon4qt5_backend/phonon_gstreamer.so
#9  0x7fde45b6ba24 in  () at
/usr/lib64/qt5/plugins/phonon4qt5_backend/phonon_gstreamer.so
#10 0x7fde45b6e6d1 in  () at
/usr/lib64/qt5/plugins/phonon4qt5_backend/phonon_gstreamer.so
#11 0x7fde70ad47d1 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#12 0x7fde45b7476f in  () at
/usr/lib64/qt5/plugins/phonon4qt5_backend/phonon_gstreamer.so
#13 0x7fde45b76cf4 in  () at
/usr/lib64/qt5/plugins/phonon4qt5_backend/phonon_gstreamer.so
#14 0x7fde6b66f760 in g_cclosure_marshal_VOID__BOXEDv () at
/usr/lib64/libgobject-2.0.so.0
#15 

[kwin] [Bug 398340] VirtualBOX, VMware Player - hot corners don't work, hot edges work as intended

[Tomasz Feliksiak]

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

--- Comment #2 from Tomasz Feliksiak  ---
(In reply to Martin Flöser from comment #1)
> Please try to grab the mouse in the virtual machine. The seamless mouse
> integration might destroy the feature.

You're absolutely right.
In VirtualBOX turning OFF mouse integration fixes hot corners (it's even
possible to add shortcut to this operation). I didn't find that option in
VMware Player (free version).

In both VirtualBOX and VMware Player after connecting USB mouse to virtual
machine (and in the same time disconnecting from host) fixes hot corners too. I
didn't spend much time on this but getting back mouse to host for me was
possible only after shutting off guest. Maybe there is some other way.

Nonetheless is that the right way to go? Shouldn't hot corners work like hot
edges do? If someone switch from host to guest as often as me, switching mouse
from guest to host is so much problem it's absolutely pointless to use hot
corners (of course I can live without them but that's not the way to fix bugs).

Of course I'm interested how hot corners differ from hot edges in this
situation and I will be gratefull for explanation. For now I still consider
this as a bug.

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

[kdeconnect] [Bug 394993] In recent beta version of kdeconncet android app, fails to send files from device to computer

[Nicolas Fella]

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

--- Comment #15 from Nicolas Fella  ---
(In reply to Albert Vaca from comment #14)
> Fixed a problem that could have been the cause of this:
> 1d1fdf8ef5c26a22672a68eaa94581ba30ef6dbf
> 
> Could you test the master branch version and tell me if you are still having
> trouble?

To be clear, he's talking about the master branch of the desktop side

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

[kdeconnect] [Bug 394993] In recent beta version of kdeconncet android app, fails to send files from device to computer

[Albert Vaca]

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

Albert Vaca  changed:

   What|Removed |Added

 Status|CONFIRMED   |NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #14 from Albert Vaca  ---
Fixed a problem that could have been the cause of this:
1d1fdf8ef5c26a22672a68eaa94581ba30ef6dbf

Could you test the master branch version and tell me if you are still having
trouble?

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

[Falkon] [Bug 397579] Dictionary Conversion no longer working

[Marco Parillo]

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

Marco Parillo  changed:

   What|Removed |Added

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

--- Comment #2 from Marco Parillo  ---
Upstream Bug Report:
https://bugreports.qt.io/browse/QTBUG-70034

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

[dolphin] [Bug 398309] Use icon or the word 'Edit' instead of 'Change' for editing tags and comments

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org

--- Comment #1 from Nate Graham  ---
Here, have a patch: https://phabricator.kde.org/D15332

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

[okular] [Bug 398334] Okular crashes while un/re highlighting PDF file

[Albert Astals Cid]

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

Albert Astals Cid  changed:

   What|Removed |Added

 CC||aa...@kde.org

--- Comment #3 from Albert Astals Cid  ---
This didn't really add much. 

I guess you may need to type backtrace after the crash to get more info.

Also if you can please run okular through valgrind, please do so and attach it?

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

[neon] [Bug 398381] New: installation of python3-distupgrade (1:18.04.25+p16.04+git20180906.1227) is broken

[bugzilla_noreply]

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

Bug ID: 398381
   Summary: installation of python3-distupgrade
(1:18.04.25+p16.04+git20180906.1227) is broken
   Product: neon
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: Packages Dev Edition [stable]
  Assignee: neon-b...@kde.org
  Reporter: thierrybl...@msn.com
CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org
  Target Milestone: ---

Hi,
while installing python3-distupgrade (1:18.04.25+p16.04+git20180906.1227), I
got following error (that broke packages installation and configuration) :
E: Sub-process /usr/bin/dpkg returned an error code (1)
Impossible d'effectuer l'opération demandée sur le paquet. Essai de
récupération :
Paramétrage de python3-distupgrade (1:18.04.25+p16.04+git20180906.1227) ...
  File "/usr/lib/python3/dist-packages/DistUpgrade/DistUpgradeViewKDE.py", line
744
if not run_apport() || not apport_ran:
 ^
SyntaxError: invalid syntax



To fix this bug, I edited the file
/usr/lib/python3/dist-packages/DistUpgrade/DistUpgradeViewKDE.py and replaced
at line 744

if not run_apport() || not apport_ran:
by 
if not run_apport() or not apport_ran:

and had to run afterwards:
sudo dpkg-reconfigure --force python3-distupgrade ubuntu-release-upgrader-core
ubuntu-release-upgrader-qt distro-release-notifier


Hope it helps to fix this bug ;)

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

[kdeconnect] [Bug 336043] SFTP: Should be able to browse external SD cards via SFTP too

[Andras]

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

Andras  changed:

   What|Removed |Added

 CC||andrasszerencs...@gmail.com

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

[okular] [Bug 398334] Okular crashes while un/re highlighting PDF file

[T . Zack Crawford]

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

--- Comment #2 from T. Zack Crawford  ---
(In reply to T. Zack Crawford from comment #1)
> I reinstalled okular and glibc in debug mode such that I could get the full
> backtrace and now the bug is not reproducible...

The crash started happening again. Managed to extract a trace using the gnu
debugger per the instructions at
https://wiki.archlinux.org/index.php/Debug_-_Getting_Traces

Trace 
Starting program: /usr/bin/okular --verbose
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7fffed767700 (LWP 8371)]
[Thread 0x7034b800 (LWP 8367) exited]
[Inferior 1 (process 8367) exited with code 01]
Starting program: /usr/bin/okular --verbose
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7fffed767700 (LWP 8374)]
[Thread 0x7034b800 (LWP 8372) exited]
[Inferior 1 (process 8372) exited with code 01]
Starting program: /usr/bin/okular 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7fffed767700 (LWP 8387)]
[New Thread 0x7fffe6aa1700 (LWP 8390)]
[New Thread 0x7fffdb198700 (LWP 8391)]
[New Thread 0x7fffda856700 (LWP 8392)]
[New Thread 0x7fffda055700 (LWP 8393)]
[New Thread 0x7fffd9854700 (LWP 8394)]
[New Thread 0x7fffd9053700 (LWP 8395)]
[New Thread 0x7fffd8852700 (LWP 8396)]
[New Thread 0x7fffc3fff700 (LWP 8397)]
[New Thread 0x7fffc2cda700 (LWP 8400)]
[Thread 0x7fffc2cda700 (LWP 8400) exited]
[New Thread 0x7fffc2cda700 (LWP 8412)]
[New Thread 0x7fffb7fff700 (LWP 8413)]
[Thread 0x7fffc2cda700 (LWP 8412) exited]
[Thread 0x7fffb7fff700 (LWP 8413) exited]
[New Thread 0x7fffb7fff700 (LWP 8414)]
[New Thread 0x7fffc2cda700 (LWP 8415)]
[Thread 0x7fffb7fff700 (LWP 8414) exited]
[New Thread 0x7fffb7fff700 (LWP 8416)]
[Thread 0x7fffc2cda700 (LWP 8415) exited]
[New Thread 0x7fffb7fff700 (LWP 8417)]
[Thread 0x7fffb7fff700 (LWP 8416) exited]
[Thread 0x7fffb7fff700 (LWP 8417) exited]
[New Thread 0x7fffb7fff700 (LWP 8418)]
[New Thread 0x7fffc2cda700 (LWP 8419)]
[Thread 0x7fffb7fff700 (LWP 8418) exited]
[New Thread 0x7fffb7fff700 (LWP 8420)]
[Thread 0x7fffc2cda700 (LWP 8419) exited]
[New Thread 0x7fffc2cda700 (LWP 8421)]
[Thread 0x7fffb7fff700 (LWP 8420) exited]
[New Thread 0x7fffb7fff700 (LWP 8422)]
[Thread 0x7fffc2cda700 (LWP 8421) exited]
[New Thread 0x7fffc2cda700 (LWP 8423)]
[New Thread 0x7fffb77fe700 (LWP 8424)]
[Thread 0x7fffb7fff700 (LWP 8422) exited]
[Thread 0x7fffc2cda700 (LWP 8423) exited]
[New Thread 0x7fffb77fe700 (LWP 8425)]
[Thread 0x7fffb77fe700 (LWP 8424) exited]
[New Thread 0x7fffc2cda700 (LWP 8426)]
[Thread 0x7fffb77fe700 (LWP 8425) exited]
[Thread 0x7fffc2cda700 (LWP 8426) exited]
[New Thread 0x7fffc2cda700 (LWP 8427)]
[Thread 0x7fffc2cda700 (LWP 8427) exited]
[New Thread 0x7fffc2cda700 (LWP 8428)]
[Thread 0x7fffc2cda700 (LWP 8428) exited]
[New Thread 0x7fffc2cda700 (LWP 8429)]
[Thread 0x7fffc2cda700 (LWP 8429) exited]
[New Thread 0x7fffc2cda700 (LWP 8430)]
[New Thread 0x7fffb77fe700 (LWP 8431)]
[Thread 0x7fffc2cda700 (LWP 8430) exited]
[Thread 0x7fffb77fe700 (LWP 8431) exited]
[New Thread 0x7fffb77fe700 (LWP 8432)]
[Thread 0x7fffb77fe700 (LWP 8432) exited]
[New Thread 0x7fffb77fe700 (LWP 8433)]
[New Thread 0x7fffc2cda700 (LWP 8434)]
[Thread 0x7fffb77fe700 (LWP 8433) exited]
[Thread 0x7fffc2cda700 (LWP 8434) exited]
[New Thread 0x7fffc2cda700 (LWP 8435)]
[New Thread 0x7fffb77fe700 (LWP 8436)]
[New Thread 0x7fffc2cda700 (LWP 8437)]
[Thread 0x7fffc2cda700 (LWP 8435) exited]
[Thread 0x7fffb77fe700 (LWP 8436) exited]
[New Thread 0x7fffb77fe700 (LWP 8438)]
[Thread 0x7fffc2cda700 (LWP 8437) exited]
[Thread 0x7fffb77fe700 (LWP 8438) exited]
[New Thread 0x7fffb77fe700 (LWP 8439)]
[Thread 0x7fffb77fe700 (LWP 8439) exited]
[New Thread 0x7fffb77fe700 (LWP 8440)]
[Thread 0x7fffb77fe700 (LWP 8440) exited]
[New Thread 0x7fffb77fe700 (LWP 8441)]
[New Thread 0x7fffb77fe700 (LWP 8442)]
[Thread 0x7fffb77fe700 (LWP 8441) exited]
[Thread 0x7fffb77fe700 (LWP 8442) exited]
[New Thread 0x7fffb77fe700 (LWP 8443)]
[New Thread 0x7fffb77fe700 (LWP 8444)]
[Thread 0x7fffb77fe700 (LWP 8443) exited]
[Thread 0x7fffb77fe700 (LWP 8444) exited]
[New Thread 0x7fffb77fe700 (LWP 8446)]
[Thread 0x7fffb77fe700 (LWP 8446) exited]
[New Thread 0x7fffb77fe700 (LWP 8447)]

Thread 1 "okular" received signal SIGSEGV, Segmentation fault.
0x7fffec69df6b in Okular::ObjectRect::distanceSqr
(this=this@entry=0x55c6a2a0, 
x=x@entry=0.52796803652968038, y=y@entry=0.717892903787549,
xScale=xScale@entry=1752, 
yScale=yScale@entry=2297) at
/usr/src/debug/okular-18.08.1/core/annotations.h:693
693 /usr/src/debug/okular-18.08.1/core/annotations.h: No such file or
directory.

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

[krita] [Bug 398380] Krita won't handle big files with a lot of layers

[Andras]

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

Andras  changed:

   What|Removed |Added

 CC||andrasszerencs...@gmail.com

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

[krita] [Bug 398380] New: Krita won't handle big files with a lot of layers

[Andras]

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

Bug ID: 398380
   Summary: Krita won't handle big files with a lot of layers
   Product: krita
   Version: 4.1.1
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: General
  Assignee: krita-bugs-n...@kde.org
  Reporter: andrasszerencs...@gmail.com
  Target Milestone: ---

Application: krita (4.1.1)

Qt Version: 5.11.1
Frameworks Version: 5.49.0
Operating System: Linux 4.15.0-33-generic x86_64
Distribution: KDE neon User Edition 5.13

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

There were two files open in Krita, each of them more then 2GB with a lot of
layer. Simple I was working on different layers on the first file and tried to
save it and right after I pressed CTRL+s, I closed the second file then it's
crashed. Anyway, I don't thing there was any specific issue here related what
was I doing. It's clear Krita is unstable with more then one big file with a
lot of layers.
Basically I'd reopen this bug report:
https://bugs.kde.org/show_bug.cgi?id=394974
Obviously I'll not open it since it's closed by me after my lot of uploading
and involvement wasn't appreciated and I was childishly threatened. For me,
it's clear, somehow Krita contribution is not for bug reports what can't be
solved fast and easily.
So this is still an awkward situation because I still have a not so simple not
so clear issue with Krita. I report this issue only because I have still hope
in Krita. It's a basic thing when your work is lost by a software, you would
report it to developers, wouldn't you?

The crash can be reproduced sometimes.

-- Backtrace:
Application: Krita (krita), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fcec2488940 (LWP 23496))]

Thread 5 (Thread 0x7fce7a134700 (LWP 23515)):
#0  0x7fcebe86c74d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fceb6c6c38c in g_main_context_poll (priority=2147483647, n_fds=1,
fds=0x7fce700033b0, timeout=, context=0x7fce7990) at
/build/glib2.0-b4FPyK/glib2.0-2.48.2/./glib/gmain.c:4135
#2  g_main_context_iterate (context=context@entry=0x7fce7990,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
/build/glib2.0-b4FPyK/glib2.0-2.48.2/./glib/gmain.c:3835
#3  0x7fceb6c6c49c in g_main_context_iteration (context=0x7fce7990,
may_block=may_block@entry=1) at
/build/glib2.0-b4FPyK/glib2.0-2.48.2/./glib/gmain.c:3901
#4  0x7fcebf39a0bb in QEventDispatcherGlib::processEvents
(this=0x7fce78c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7fcebf3415ba in QEventLoop::exec (this=this@entry=0x7fce7a133c00,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:214
#6  0x7fcebf1765e4 in QThread::exec (this=) at
thread/qthread.cpp:525
#7  0x7fce9ee17f86 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#8  0x7fcebf181727 in QThreadPrivate::start (arg=0xc9c2df0) at
thread/qthread_unix.cpp:367
#9  0x7fceb83106ba in start_thread (arg=0x7fce7a134700) at
pthread_create.c:333
#10 0x7fcebe87841d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7fce83b0f700 (LWP 23514)):
#0  0x7fcebe86827d in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fceb6caf6f0 in read (__nbytes=16, __buf=0x7fce83b0ea40,
__fd=) at /usr/include/x86_64-linux-gnu/bits/unistd.h:44
#2  g_wakeup_acknowledge (wakeup=0x7fce940025b0) at
/build/glib2.0-b4FPyK/glib2.0-2.48.2/./glib/gwakeup.c:210
#3  0x7fceb6c6be74 in g_main_context_check
(context=context@entry=0x7fce7c000990, max_priority=2147483647,
fds=fds@entry=0x7fce7c004870, n_fds=n_fds@entry=1) at
/build/glib2.0-b4FPyK/glib2.0-2.48.2/./glib/gmain.c:3632
#4  0x7fceb6c6c330 in g_main_context_iterate
(context=context@entry=0x7fce7c000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-b4FPyK/glib2.0-2.48.2/./glib/gmain.c:3837
#5  0x7fceb6c6c49c in g_main_context_iteration (context=0x7fce7c000990,
may_block=may_block@entry=1) at
/build/glib2.0-b4FPyK/glib2.0-2.48.2/./glib/gmain.c:3901
#6  0x7fcebf39a0bb in QEventDispatcherGlib::processEvents
(this=0x7fce7c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#7  0x7fcebf3415ba in QEventLoop::exec (this=this@entry=0x7fce83b0ec50,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:214
#8  0x7fcebf1765e4 in QThread::exec (this=) at
thread/qthread.cpp:525
#9  0x7fce9e98e195 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#10 0x7fcebf181727 in QThreadPrivate::start (arg=0xc87ea30) at
thread/qthread_unix.cpp:367
#11 0x7fceb83106ba in start_thread (arg=0x7fce83b0f700) at
pthread_create.c:333
#12 0x7fcebe87841d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 

[dolphin] [Bug 398316] Time to move files into another tab is pretty long

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WONTFIX
 Status|NEEDSINFO   |RESOLVED

--- Comment #3 from Nate Graham  ---
Well, these are different user interfaces with different needs. Tabs in an app
such as Dolphin generally have a delay when for dragged-and-dropped files are
passed over them to prevent accidental tab activation, which can be very
annoying and require you to redo the operation. Kickoff has no such issues,
since the tabs never receive drag-and-dropped files. So there is no need for a
delay there.

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

[dolphin] [Bug 398316] Time to move files into another tab is pretty long

[Matthias]

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

--- Comment #2 from Matthias  ---
Yeah. So long as it is. According to the recent fix in Kicker, this is too
long, right?

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

[digikam] [Bug 398377] Rename jpg and related dng file keeping the same base name

[bugzilla_noreply]

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

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

   What|Removed |Added

Summary|Rename fpg and related dng  |Rename jpg and related dng
   |file keeping the same base  |file keeping the same base
   |name|name
 CC||caulier.gil...@gmail.com

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

[digikam] [Bug 398376] UI problems making face management very hard

[bugzilla_noreply]

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

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

   What|Removed |Added

  Component|Faces-Maintenance   |Faces-Workflow
 CC||caulier.gil...@gmail.com

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

[LabPlot2] [Bug 398342] ProjectImportTest segfaults while loading Excel file

[Alexander Semke]

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

--- Comment #1 from Alexander Semke  ---
Can you please do a debug build and execute the tests again?

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

[dolphin] [Bug 398379] New: Emptying the trash can doesn't change its icon.

[Parimal Prasoon]

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

Bug ID: 398379
   Summary: Emptying the trash can doesn't change its icon.
   Product: dolphin
   Version: 18.04.2
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: parimalpraso...@gmail.com
CC: elvis.angelac...@kde.org
  Target Milestone: ---

I am using Kubuntu 18.04 LTS release, and the default plasma 5 theme for icons.
The icon is blue when trash is empty, goes to red when something goes in trash,
and stays red even after I empty the trash ( although sometimes it goes back to
the default blue colour). Don't know how to reproduce the bug.

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

[systemsettings] [Bug 398368] "Could not find the program kcmshell4" error when I try to start Audio CD kcm via apps launcher

[Antonio Rojas]

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

Antonio Rojas  changed:

   What|Removed |Added

   Version Fixed In||18.08.2

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

[systemsettings] [Bug 398368] "Could not find the program kcmshell4" error when I try to start Audio CD kcm via apps launcher

[Antonio Rojas]

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

Antonio Rojas  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
  Latest Commit||https://commits.kde.org/aud
   ||iocd-kio/9aa606bbc4c9012eb1
   ||f09fbc8c7db4194a81f18a
 Resolution|--- |FIXED

--- Comment #2 from Antonio Rojas  ---
Git commit 9aa606bbc4c9012eb1f09fbc8c7db4194a81f18a by Antonio Rojas.
Committed on 07/09/2018 at 20:05.
Pushed by arojas into branch 'Applications/18.08'.

Use the right version of kcmshell

Differential Revision: https://phabricator.kde.org/D15336

M  +1-1kcmaudiocd/audiocd.desktop

https://commits.kde.org/audiocd-kio/9aa606bbc4c9012eb1f09fbc8c7db4194a81f18a

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

[krunner] [Bug 398378] New: Allow to set krunner window position

[bugzilla_noreply]

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

Bug ID: 398378
   Summary: Allow to set krunner window position
   Product: krunner
   Version: 5.13.5
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: k...@privat.broulik.de
  Reporter: fabi...@keemail.me
  Target Milestone: ---

Hello!

Today a friend of mine showed me macOS's krunner equivalent (Spotlight maybe?),
which is nicely positioned in the center of the screen. I thought that the
current krunner position, the top of the screen, is not very attractive as it's
uncomfortable to raise your sight, especially when using a desktop computer,
and the bar is pretty tiny for my 1080p, 24" monitor. What do you think about
positioning krunner window in the center, and make it bigger? OR maybe we
should allow users to place it wherever they like?

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

[Discover] [Bug 396149] Kolourpaint icon does not respect the active theme

[Nate Graham]

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

--- Comment #7 from Nate Graham  ---
The fix was made to AppStream, and made it into the 0.7.4 release last month.
Your distro is responsible for providing that to you.

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

[Discover] [Bug 396149] Kolourpaint icon does not respect the active theme

[PK]

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

--- Comment #6 from PK  ---
I am already on plasma 5.13.5 and applications 18.08.1 but only very rarely the
KolourPaint icon is the one I would like to see. Most of the time it is still
the wrong one. As it is in the attachment I added to this bug report.

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

[digikam] [Bug 398377] New: Rename fpg and related dng file keeping the same base name

[Reiner Nix]

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

Bug ID: 398377
   Summary: Rename fpg and related dng file keeping the same base
name
   Product: digikam
   Version: 5.9.0
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: AdvancedRename
  Assignee: digikam-bugs-n...@kde.org
  Reporter: reiner@web.de
  Target Milestone: ---

Hi,

When I have created two files with the same image, one in jpg and the other in
png format, the cameray will store them with the same name, e.g. K_3_1243.JPG
and K_3_1243.DNG.

I am using the rename tool with a pattern "[date:-MM-dd]_###[1]". 
I like to rename these files while keeping the same base name, e.g.
2018-09-01_001.JPG and 2018-09-01_001.DNG.

Best regards
Reiner

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

[digikam] [Bug 398376] New: UI problems making face management very hard

[Reiner Nix]

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

Bug ID: 398376
   Summary: UI problems making face management very hard
   Product: digikam
   Version: 5.9.0
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Faces-Maintenance
  Assignee: digikam-bugs-n...@kde.org
  Reporter: reiner@web.de
  Target Milestone: ---

Created attachment 114836
  --> https://bugs.kde.org/attachment.cgi?id=114836=edit
Choosing a caption using the drop down box in the full image view

The face detection and management is a big step forward and I like it.
I like to give some feedback about my experiences with the hope that an
improvement is also useful for many other digikam users.

Using the face detection, digikam has some problems making face management very
hard. 

The issues are related to the label / caption hierarchy. For correctness to my
setup, I am using german  but I guess this should not really matter. Here a
snippet of the hierarchy I have setup:

Stichwörter (the root)
 |-- Lebewesen
 | |-- Personen und Haustiere
 |   |-- Familie
 |   | |-- Anne
 |   | |-- Reiner
 |   |
 |   |-- Freunde
 |   | |-- Mueller
 |   | | |-- Maria
 |   | | |-- Michel
...
 |-- Personen // created by Digikam as default place for face recognition

Before face detection was available I had already manually labelled many images
with face tags. Of cource face tags means that I have had created a label
(caption) subtree, see "Personen und Haustiere". 
For the face detection another subtree below "Personen" is automatically
introduced which caused problems.

Problems:
1) When running face detection on an image which was previously labelled at
whole, the caption cannot be choosen to be re-assigned particulary fro whe
image to the face. Moreover it is not possible to choose it (maybe because it
is already assigned to the image?). I think that should be possible because
this caption is related to the person no matter where it is attached to the
image or to the designated face in the same image. And the face detection
mechanism cannot be configured to ignore this album forever (which would be a
work-around only).

2) It is not possible that I can manually configure my subtree in the captions
named "Personen und Haustiere" to be used for the face detection.
Moving to the automatic created "Personen" top-level subtree is not my wish
because of using another system and it would place much work to me.

3) Due to the difference between the preset top-level tree of captions, some
captions below "Personen und Lebewesen" and some below "Personen" are used.
I. e. creating new captions during the management will be placed below
"Personen" while choosing old ones use those below "Personen und Lebewesen".
This leads to a mess. For me all, new and old, captions should be below
"Personen und Lebewesen".

4) After the face recognition was done and I do the assignment using a known
caption with the drop-down combo box as supported in the full image view. As
the hierarchy of captions is huge by high number of captions and deep hierarchy
the displayed combo box is too small - even I am working using a 4k display,
which provides much more space. Please have a look to the attached screenshoot.

5) Using the dialog to run the face detection only within a subset of all
albums, will display a combo box for the albums. But it is not possible to
reset the previous made selection with a single action. Instead I have manually
to run through the whole hierarchie of almbums and try to find which one was
selected in the previous run. 
A suggestion would be to have a list of all albums on the left side and the
choosen albums are displayed on the right side. For example, this concept is
used for example when configuring the buttons in a KDE menu bar.

6) Any face detected need to be assigned to a caption. But what is the best way
to remember that a face is to be ignored? For example my family and me did
visit a historic metal mine on holidays. My family was part of a larger visitor
group. Thus on some images there were quite more faces detected than I am
familar with and for which I like to provide captions.

7) Regression error: with the current release (5.9.0) the face detection does
not correctly work on the choosen album. Instead quite more albums will be
used. Of course the check mark "Gesamte Almbumsammlung" (All Albums) has been
not checked. In my previous digikam release (5.6.0) this was working as
expected.


Best regards,
Reiner

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

[dolphin] [Bug 398375] New: Problem moving a file in split view

[bugzilla_noreply]

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

Bug ID: 398375
   Summary: Problem moving a file in split view
   Product: dolphin
   Version: 18.04.3
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: split view
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: 16f8...@gmail.com
  Target Milestone: ---

Created attachment 114835
  --> https://bugs.kde.org/attachment.cgi?id=114835=edit
the video show the problem described in the description

There is a problem if I move a file from one folder to another in split view
(the problem seems to show only with the view in detail mode).
How you can see in the video if I move the file it may happen that the name of
the file I was moving is written in another file of the folder. As a
consequence after I have moved the file I get two different files with the same
name, one -the original- in the first folder and another different but with the
same name of the first, in the second folder.

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

[frameworks-ktexteditor] [Bug 382075] Solarized light color schema is outdated or uses wrong colors

[Andrew Crouthamel]

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

--- Comment #5 from Andrew Crouthamel  ---
(In reply to Michael D from comment #4)
> Thanks for taking the time to fix this!

Michael, you can check it out here as it goes through code review:
https://phabricator.kde.org/D15337

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

[okular] [Bug 398334] Okular crashes while un/re highlighting PDF file

[T . Zack Crawford]

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

--- Comment #1 from T. Zack Crawford  ---
I reinstalled okular and glibc in debug mode such that I could get the full
backtrace and now the bug is not reproducible...

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

[latte-dock] [Bug 398374] New: Latte dock goes into edit-ish mode when game take full screen.

[Andy Great]

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

Bug ID: 398374
   Summary: Latte dock goes into edit-ish  mode when game take
full screen.
   Product: latte-dock
   Version: 0.8.0
  Platform: Manjaro
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: application
  Assignee: mvourla...@gmail.com
  Reporter: andythe_gr...@pm.me
  Target Milestone: ---

Created attachment 114834
  --> https://bugs.kde.org/attachment.cgi?id=114834=edit
Screenshot of edit-ish like mode when fullscreen game was launch.

Manjaro KDE stable 
Latte dock 0.8.0-1

1. Setting>Display>Compositor> tick "Allow application to block compositing"
2. Launch any full screen steam game.
3. Switch workspace
4. If mouse is placed over the dock, it work fine.
5. If mouse is not placed over the dock, it become like the screenshot
attachment.

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

[kate] [Bug 398289] Set "Open Terminal" by default to F4

[Matthias]

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

--- Comment #5 from Matthias  ---
Then also think about another keybinding for Ctrl+Shift+V?

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

[Discover] [Bug 398373] New: Estoy intentando actualizar

[Javier Curbelo]

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

Bug ID: 398373
   Summary: Estoy intentando actualizar
   Product: Discover
   Version: 5.13.5
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: ajc...@telefonica.net
  Target Milestone: ---

Application: plasma-discover (5.13.5)

Qt Version: 5.11.1
Frameworks Version: 5.50.0
Operating System: Linux 4.15.0-33-generic x86_64
Distribution: KDE neon User Edition 5.13

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

Yo estaba intentando actualizar kde neon, primero desde la version user 16.04 a
la version gitstable, para luego intentar actualizar a la version 18.04.

Las imagenes 18.04 de finales de agosto funcionaban bien pero las nuevas del 6
de septiembre el instalador se estropea cuando empieza a instalar el sistema.
Esto me pasa con las versiones user edition y developer edition gitstable. Por
eso he tenido que instalar la version 16.04 que es la unica que funciona.

Gracias.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Discover (plasma-discover), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fa18353a8c0 (LWP 1646))]

Thread 7 (Thread 0x7fa143d96700 (LWP 1654)):
#0  0x7fa17e7e874d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fa17942738c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fa17942749c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fa17f4090bb in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fa17f3b05ba in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fa17f1e55e4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fa17f1f0727 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fa17b28c6ba in start_thread (arg=0x7fa143d96700) at
pthread_create.c:333
#8  0x7fa17e7f441d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7fa1494be700 (LWP 1653)):
#0  0x7fa17e7e874d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fa17942738c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fa17942749c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fa17f4090bb in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fa17f3b05ba in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fa17f1e55e4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fa17f1f0727 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fa17b28c6ba in start_thread (arg=0x7fa1494be700) at
pthread_create.c:333
#8  0x7fa17e7f441d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7fa1521a1700 (LWP 1652)):
#0  0x7fa17e7e427d in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fa17946a6f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fa179426e74 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fa179427330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fa17942749c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fa17f4090bb in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fa17f3b05ba in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fa17f1e55e4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fa182635f86 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#9  0x7fa17f1f0727 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7fa17b28c6ba in start_thread (arg=0x7fa1521a1700) at
pthread_create.c:333
#11 0x7fa17e7f441d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7fa153681700 (LWP 1651)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fa158e4e70b in ?? () from
/usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
#2  0x7fa158e4e427 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
#3  0x7fa17b28c6ba in start_thread (arg=0x7fa153681700) at
pthread_create.c:333
#4  0x7fa17e7f441d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7fa1675ef700 (LWP 1650)):
#0  0x7fa17946ba79 in g_mutex_lock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fa179426dcc in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fa179427330 in 

[kmymoney] [Bug 393752] Budgeted vs. Actual report: Budgeted values broken if ticks selected to Bi-Monthly, Quarterly or Yearly

[Thomas Baumgart]

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

Thomas Baumgart  changed:

   What|Removed |Added

   Version Fixed In||5.0.2
  Latest Commit||https://commits.kde.org/kmy
   ||money/90c714c693edb88467fe7
   ||0dcd97277a18dc8e47b
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #10 from Thomas Baumgart  ---
Git commit 90c714c693edb88467fe70dcd97277a18dc8e47b by Thomas Baumgart.
Committed on 07/09/2018 at 17:28.
Pushed by tbaumgart into branch '5.0'.

Fix Bi-Monthly, Quarterly or Yearly budget reports
FIXED-IN: 5.0.2

M  +1-1kmymoney/plugins/views/reports/core/pivottable.cpp

https://commits.kde.org/kmymoney/90c714c693edb88467fe70dcd97277a18dc8e47b

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

[policykit-kde-agent-1] [Bug 398367] Authentication dialog does not accept password of admin user on root-locked Ubuntu-based system

[spm2011]

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

--- Comment #1 from spm2011  ---
Created attachment 114833
  --> https://bugs.kde.org/attachment.cgi?id=114833=edit
Authentication fails on admin password

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

[plasmashell] [Bug 398369] 2 external monitors not possible, screen goes haywire [Picture]

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #2 from Nate Graham  ---
That imgur link is broken. Please attach the image to the bug report using the
"Add an attachment" link. Also please attach the image of it working on Linux
mint. Finally, also attach the xorg paste as a file, rather than a link to an
external site. See
https://community.kde.org/Get_Involved/Bug_Reporting#Screenshots_and_screen_recordings

Thanks!

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

[plasmashell] [Bug 398369] 2 external monitors not possible, screen goes haywire [Picture]

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

   Assignee|notm...@gmail.com   |aleix...@kde.org
  Component|Desktop Dashboard   |Multi-screen support
 CC||n...@kde.org,
   ||plasma-b...@kde.org

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

[systemsettings] [Bug 398368] "Could not find the program kcmshell4" error when I try to start Audio CD kcm via apps launcher

[Antonio Rojas]

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

Antonio Rojas  changed:

   What|Removed |Added

 CC||aro...@archlinux.org
 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #1 from Antonio Rojas  ---
https://phabricator.kde.org/D15336

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

[neon] [Bug 398372] [Bionic] The handling of the left-click on the system tray becomes wrong after some time.

[Alexander]

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

Alexander  changed:

   What|Removed |Added

Summary|[Bionic] The handling of|[Bionic] The handling of
   |the left-click on the   |the left-click on the
   |system tray become wrong|system tray becomes wrong
   |after some time.|after some time.

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

[plasmashell] [Bug 398369] 2 external monitors not possible, screen goes haywire [Picture]

[Salang]

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

--- Comment #1 from Salang  ---
This is the Xorg.0.conf log after I rebooted with both plugged in:
https://bpaste.net/show/ac2462ea434d

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

[kwallet-pam] [Bug 375236] kwallet-pam doesn't work in conjunction with dm-crypt-encrypted /home which gets unlocked with pam_mount

[spm2011]

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

spm2011  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=383115

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

[neon] [Bug 383115] With encrypted and _not_ already mounted $HOME: kwallet (and ssh-agent) not opened automatically on login. (With already mounted home it works.)

[spm2011]

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

spm2011  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=375236

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

[neon] [Bug 398372] New: [Bionic] The handling of the left-click on the system tray become wrong after some time.

[Alexander]

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

Bug ID: 398372
   Summary: [Bionic] The handling of the left-click on the system
tray become wrong after some time.
   Product: neon
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Live/Install images
  Assignee: neon-b...@kde.org
  Reporter: kos...@koshka.ddns.net
CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org
  Target Milestone: ---

I can describe the problem only as an example.
After reboot system tray works as it should. I can left-click once on each icon
to open network or sound control. The proper icon in tray is highlighted after
such click.

For example I listen to music using deadbeef player and often change music
volume using tray icon. Left click on tray's sound icon, move slider, click
icon (or desktop) again to close widget.

After a few tens of such adjustments I notice that tray icon doesn't respond on
the first click. Now I need two clicks to open sound settings.
On this stage sound settings looks normal but power manager looses battery
charge indicator. To see the battery charge indicator, the battery icon must be
clicked 3 times.
But still, tray is usable unless I click "triangle" icon which opens "status
and notifications".
After that each click (sometimes double, sometimes single) on such tray icons
as "battery", "network", "clipboard", "sound" opens "status and notifications"
widget. The whole tray is highlighted with blue line.

But!
- clock widget, keyboard layout icon and third-party icons such as thunderbird,
goldendict work properly. 
- right-click works properly. I can open "configure networks", "configure power
saving" etc
- I can unlock widgets and open "system tray settings" which show absolutely
empty "Entries" page. 

I couldn't find any workaround or the way to restart only the system tray.

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

[kmymoney] [Bug 398371] New: The width of the rows increase instead of font

[bugzilla_noreply]

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

Bug ID: 398371
   Summary: The width of the rows increase instead of font
   Product: kmymoney
   Version: 4.8.2
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kmymoney-de...@kde.org
  Reporter: esmpast...@gmail.com
  Target Milestone: ---

When increasing fonts, only the width of the row increases, font stays the same

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

[kdesu] [Bug 377528] KDE su Run as root Window Hangs Entering Admin Password in Standard User Session

[spm2011]

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

spm2011  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=398367

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

[policykit-kde-agent-1] [Bug 398367] Authentication dialog does not accept password of admin user on root-locked Ubuntu-based system

[spm2011]

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

spm2011  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=377528

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

[krita] [Bug 398370] New: [Krita Animation] Onion layers are overridden with initial key frame

[BlackHand]

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

Bug ID: 398370
   Summary: [Krita Animation] Onion layers are overridden with
initial key frame
   Product: krita
   Version: 4.1.0
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Animation
  Assignee: krita-bugs-n...@kde.org
  Reporter: c.blackh...@yahoo.com
  Target Milestone: ---

Hi Team,

When creating an animation, the 1st key frame is the only frame visible on
playback and rendering.
It doesn't matter if you create from duplicate or insert blank frame.
Once you alter the subsequent frames you can even see the variation in color of
the onion layers and all edits, then upon playback it's a still image of the
original key frame with no animation.
Rendering to gif is problematic as well (I will open a separate ticket for
this).
I was able to get my first animation to operate properly, however, upon
reopening the same file and adding more frames, the added frames don't animate.
Please let me know what extra info you need and I am happy to provide.

-BH

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

[plasmashell] [Bug 398369] New: 2 external monitors not possible, screen goes haywire [Picture]

[Salang]

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

Bug ID: 398369
   Summary: 2 external monitors not possible, screen goes haywire
[Picture]
   Product: plasmashell
   Version: master
  Platform: Manjaro
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Desktop Dashboard
  Assignee: notm...@gmail.com
  Reporter: salan...@gmail.com
  Target Milestone: 1.0

https://i.imgur.com/tjqPC9

This always worked fine in Linux Mint with XFCE - I'm trying to get all 3
monitors to work on Manjaro KDE. 2 monitors works, 3 doesn't

I had the same problem with Mint KDE. It worked fine with Mint Cinnamon and
Mint XFCE

It's a USB-c => 2 HDMI dongle

 As soon as I plugout 1 of the HDMI cables, the other screen shows fine... only
when 2 are hooked up, it goes like that

It's an INTEL HD graphics card

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

[systemsettings] [Bug 398368] New: "Could not find the program kcmshell4" error when I try to start Audio CD kcm via apps launcher

[Dr . Chapatin]

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

Bug ID: 398368
   Summary: "Could not find the program kcmshell4" error when I
try to start Audio CD kcm via apps launcher
   Product: systemsettings
   Version: 5.13.5
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: kcm_audiocd
  Assignee: b...@meyerhome.net
  Reporter: bugsefor...@gmx.com
  Target Milestone: ---

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

Search for "audio cd" in the apps laucher and try to open it.
Screenshot shows the result.

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

[kiofuse] [Bug 75324] Integrate KIO Slaves into file system using FUSE gateway

[bugzilla_noreply]

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

gszymas...@short.pl changed:

   What|Removed |Added

 CC||gszymas...@short.pl

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

[Akonadi] [Bug 398282] Akonadi crashes frequently since upgrade to 5.9.0

[Frits Spieker]

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

--- Comment #3 from Frits Spieker  ---
Hi. Updated PC today and so far (knock on wood) it seems indeed to be fixed. So
far can consider as resolved indeed.

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

[policykit-kde-agent-1] [Bug 398367] New: Authentication dialog does not accept password of admin user on root-locked Ubuntu-based system

[spm2011]

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

Bug ID: 398367
   Summary: Authentication dialog does not accept password of
admin user on root-locked Ubuntu-based system
   Product: policykit-kde-agent-1
   Version: 5.13.5
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: polkit-kde-authentication-agent-1
  Assignee: jrez...@redhat.com
  Reporter: spammonster2...@hotmail.com
CC: neon-b...@kde.org
  Target Milestone: ---

Neon user edition
polkit-kde-agent-1/xenial,now 4:5.13.5-0xneon+16.04+xenial+build64 amd64

To reproduce:
  - In a limited user account session, open software updates in discover.
  - Click "Update All"
  - Enter password of admin/sudo user

Expected:

Dialog takes the admin/sudo user password to unlock privileges.


Actual:

Dialog asks "Password for root:", shows Authentication failure when the admin
user password is entered. This won't work on Ubuntu because the root user is
locked by default.


This bug makes updating through discover software updates impossible on KDE
Neon (in a standard user session).

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

[plasmashell] [Bug 398362] Unreliable behavior of control buttons

[avlas]

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

--- Comment #5 from avlas  ---
(In reply to avlas from comment #2)
> Oops I'm very sorry, I have submitted all these bugs to the wrong target.
> Now that you say, I'm sure I use plasmashell Global Menu (using KDE neon
> User Edition 18.04 with plasma 5.13.5).
> 
> Regarding the specifics of this bug, Libreoffice menues work fine other than
> this reported issue, as far as I can tell (which surprised me as previous
> attempts with LO, and also firefox failed at large).
> 
> Unfortunately, I am not aware of any other application with control buttons
> in the menu to test if this is or not specific of Libreoffice. If you would
> know of an application, I am willing to test, assumed it is easy to
> install/uninstall in my system.

I could test checkboxes in Chromium and Firefox and they seem to work as
expected. So this may be sth about LO, indeed.

But what I find most intriguing, actually don't understand, is why LO control
buttons work as expected in the server side decoration menu button.

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

[plasmashell] [Bug 398362] Unreliable behavior of control buttons

[avlas]

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

--- Comment #4 from avlas  ---
(In reply to avlas from comment #3)

> I wrongly reported other 2 bugs to appmenu as well (398357 and 398361) that
> remain to be moved to plasmashell global menu. But while I find plasmashell
> as an option, global menu submenu is not present.

Done (found out that the option appears after trying to save the changes)

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

[plasmashell] [Bug 398361] Moving across menues sometimes breaks (e.g., when an empty menu is encountered)

[avlas]

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

avlas  changed:

   What|Removed |Added

 CC||plasma-b...@kde.org
Product|kded-appmenu|plasmashell
Version|5.9.3   |5.13.5
   Assignee|plasma-b...@kde.org |k...@privat.broulik.de
   Target Milestone|--- |1.0
  Component|top menubar |Global Menu

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

[plasmashell] [Bug 398357] Different menues appear one by one with a latency in between

[avlas]

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

avlas  changed:

   What|Removed |Added

   Target Milestone|--- |1.0
   Assignee|plasma-b...@kde.org |k...@privat.broulik.de
  Component|top menubar |Global Menu
Product|kded-appmenu|plasmashell
Version|5.9.3   |5.13.5
 CC||plasma-b...@kde.org
   Platform|Other   |Neon Packages

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

[systemsettings] [Bug 398366] New: Failure of treasure box download caused by network failure

[xuthus]

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

Bug ID: 398366
   Summary: Failure of treasure box download caused by network
failure
   Product: systemsettings
   Version: 5.13.4
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: xuth...@qq.com
  Target Milestone: ---

Application: systemsettings5 (5.13.4)

Qt Version: 5.10.1
Frameworks Version: 5.48.0
Operating System: Linux 4.16.3-301.fc28.x86_64 x86_64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
当我在配置fedora-kde5的主题时候,我发现如果我的当前网络缓慢,导致的百宝箱里面的小物件下载失败,假如我退出设置界面后再一次打开系统设置,会导致系统设置界面崩溃

When I was configuring the theme of fedora-kde5, I found that if my current
network slowed down, resulting in a failure to download small objects in the
treasure box, if I quit the settings interface and open the system settings
again, it would cause the system settings interface to crash.

The crash can be reproduced every time.

-- Backtrace:
Application: 系统设置 (systemsettings5), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fbf07f19940 (LWP 3134))]

Thread 5 (Thread 0x7fbed5219700 (LWP 3157)):
#0  0x7fbf146803e9 in poll () from /lib64/libc.so.6
#1  0x7fbf0cf2abe6 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#2  0x7fbf0cf2ad10 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7fbf1554cc2b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#4  0x7fbf154fb12b in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#5  0x7fbf153499c6 in QThread::exec() () from /lib64/libQt5Core.so.5
#6  0x7fbf193403a9 in QQmlThreadPrivate::run() () from
/lib64/libQt5Qml.so.5
#7  0x7fbf1534e11d in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#8  0x7fbf1271e594 in start_thread () from /lib64/libpthread.so.0
#9  0x7fbf1468ae6f in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7fbedda67700 (LWP 3146)):
#0  0x7fbf1467be54 in read () from /lib64/libc.so.6
#1  0x7fbf0cf70070 in g_wakeup_acknowledge () from /lib64/libglib-2.0.so.0
#2  0x7fbf0cf2a6db in g_main_context_check () from /lib64/libglib-2.0.so.0
#3  0x7fbf0cf2ab90 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#4  0x7fbf0cf2ad10 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#5  0x7fbf1554cc2b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#6  0x7fbf154fb12b in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#7  0x7fbf153499c6 in QThread::exec() () from /lib64/libQt5Core.so.5
#8  0x7fbf193403a9 in QQmlThreadPrivate::run() () from
/lib64/libQt5Qml.so.5
#9  0x7fbf1534e11d in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#10 0x7fbf1271e594 in start_thread () from /lib64/libpthread.so.0
#11 0x7fbf1468ae6f in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7fbee5466700 (LWP 3145)):
#0  0x7fbf146803e9 in poll () from /lib64/libc.so.6
#1  0x7fbf0cf2abe6 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#2  0x7fbf0cf2ad10 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7fbf1554cc2b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#4  0x7fbf154fb12b in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#5  0x7fbf153499c6 in QThread::exec() () from /lib64/libQt5Core.so.5
#6  0x7fbf193403a9 in QQmlThreadPrivate::run() () from
/lib64/libQt5Qml.so.5
#7  0x7fbf1534e11d in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#8  0x7fbf1271e594 in start_thread () from /lib64/libpthread.so.0
#9  0x7fbf1468ae6f in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7fbef2ea5700 (LWP 3143)):
#0  0x7fbf1467be54 in read () from /lib64/libc.so.6
#1  0x7fbf0cf70070 in g_wakeup_acknowledge () from /lib64/libglib-2.0.so.0
#2  0x7fbf0cf2a6db in g_main_context_check () from /lib64/libglib-2.0.so.0
#3  0x7fbf0cf2ab90 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#4  0x7fbf0cf2ad10 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#5  0x7fbf1554cc2b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#6  0x7fbf154fb12b in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#7  0x7fbf153499c6 in QThread::exec() () from /lib64/libQt5Core.so.5
#8  0x7fbf15783299 in QDBusConnectionManager::run() () from
/lib64/libQt5DBus.so.5
#9  0x7fbf1534e11d in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#10 0x7fbf1271e594 in start_thread () from /lib64/libpthread.so.0
#11 0x7fbf1468ae6f in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7fbf07f19940 (LWP 

[plasmashell] [Bug 397912] ALT key menu activation priority (top menubar vs. kwin button)

[avlas]

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

avlas  changed:

   What|Removed |Added

   Platform|Other   |Neon Packages
 CC||plasma-b...@kde.org
Version|5.9.3   |5.13.5
Product|kded-appmenu|plasmashell
  Component|menu popup  |Global Menu
   Target Milestone|--- |1.0
   Assignee|plasma-b...@kde.org |k...@privat.broulik.de

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

[plasma-nm] [Bug 398363] Network manager loses credentials info

[bugzilla_noreply]

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

--- Comment #6 from marcin.ba...@gmail.com ---
This often happens when I switching wired cable in my laptop. I have to work
with multiple wired networks.

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

[konsole] [Bug 396435] emoji rendering broken

[Mariusz Glebocki]

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

--- Comment #12 from Mariusz Glebocki  ---
I can finish it on the weekend, and publish next week.
Sorry for huge delay.

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

[plasma-nm] [Bug 398363] Network manager loses credentials info

[bugzilla_noreply]

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

--- Comment #5 from marcin.ba...@gmail.com ---
Created attachment 114831
  --> https://bugs.kde.org/attachment.cgi?id=114831=edit
Plasma logs

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

[plasma-nm] [Bug 398363] Network manager loses credentials info

[bugzilla_noreply]

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

--- Comment #4 from marcin.ba...@gmail.com ---
Created attachment 114830
  --> https://bugs.kde.org/attachment.cgi?id=114830=edit
connections_wrong_selections

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

[plasma-nm] [Bug 398363] Network manager loses credentials info

[bugzilla_noreply]

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

--- Comment #3 from marcin.ba...@gmail.com ---
When applet crashes I've noticed that sometimes details of selected connection
are from different connection (connections_wrong_selections atachment)

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

[plasmashell] [Bug 398360] last menu entries remain accessible and functional when no window is under focus

[avlas]

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

avlas  changed:

   What|Removed |Added

Version|5.9.3   |5.13.5

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

[plasmashell] [Bug 398362] Unreliable behavior of control buttons

[avlas]

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

avlas  changed:

   What|Removed |Added

Version|5.9.3   |5.13.5

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

[plasmashell] [Bug 398362] Unreliable behavior of control buttons

[avlas]

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

--- Comment #3 from avlas  ---
(In reply to Kai Uwe Broulik from comment #1)
> Also, kded-appmenu top menubar is deprecated and not used in Plasma 5, the
> component responsible for that is plasmashell Global Menu

I wrongly reported other 2 bugs to appmenu as well (398357 and 398361) that
remain to be moved to plasmashell global menu. But while I find plasmashell as
an option, global menu submenu is not present.

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

[kwalletmanager] [Bug 395234] kdewallet (kf5-kwallet 5.46.0) does nopt accept password after logout from session and relogin

[avlas]

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

--- Comment #9 from avlas  ---
(In reply to avlas from comment #3)
> Further testing. The problem is not app specific. The bug is present once
> any application different of kwalletmanager is using kwallet.
> 
> I'm going to check now if there is a way to manually disconnect applications
> using kwallet from the terminal, so I can create an script to do so at
> logout, as a workaround...

Mmm, unfortunately this seems unreliable to say the least. Most of the times it
doesn't workaround the issue. I hope this bug gets some attention as it makes
impossible to restart a session when using kwallet, one needs to always reboot,
which is a bit annoying.

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

[plasmashell] [Bug 398364] New: After Game O A.D.

[Frank68]

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

Bug ID: 398364
   Summary: After Game O A.D.
   Product: plasmashell
   Version: 5.13.4
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: frankschind...@t-online.de
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.13.4)

Qt Version: 5.11.1
Frameworks Version: 5.49.0
Operating System: Linux 4.17.0-9-generic x86_64
Distribution: Ubuntu Cosmic Cuttlefish (development branch)

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

Change from Game to desktop. Game endet. After Wayland crashed.

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

Thread 15 (Thread 0x7fa6c4ef9700 (LWP 4377)):
#0  futex_wait_cancelable (private=, expected=0,
futex_word=0x562135e5e3b4) at ../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x562135e5e360,
cond=0x562135e5e388) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x562135e5e388, mutex=0x562135e5e360) at
pthread_cond_wait.c:655
#3  0x7fa784d2c43b in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fa786966279 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#5  0x7fa7869664da in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#6  0x7fa784d2bc87 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fa784894164 in start_thread (arg=) at
pthread_create.c:486
#8  0x7fa784a0fdef in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 14 (Thread 0x7fa6c5ffb700 (LWP 3350)):
#0  futex_wait_cancelable (private=, expected=0,
futex_word=0x56213616d434) at ../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x56213616d3e0,
cond=0x56213616d408) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x56213616d408, mutex=0x56213616d3e0) at
pthread_cond_wait.c:655
#3  0x7fa784d2c43b in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fa786966279 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#5  0x7fa7869664da in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#6  0x7fa784d2bc87 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fa784894164 in start_thread (arg=) at
pthread_create.c:486
#8  0x7fa784a0fdef in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 13 (Thread 0x7fa6c67fc700 (LWP 3349)):
#0  futex_wait_cancelable (private=, expected=0,
futex_word=0x562134e6bb34) at ../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x562134e6bae0,
cond=0x562134e6bb08) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x562134e6bb08, mutex=0x562134e6bae0) at
pthread_cond_wait.c:655
#3  0x7fa784d2c43b in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fa786966279 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#5  0x7fa7869664da in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#6  0x7fa784d2bc87 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fa784894164 in start_thread (arg=) at
pthread_create.c:486
#8  0x7fa784a0fdef in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 12 (Thread 0x7fa6c77fe700 (LWP 3309)):
#0  futex_wait_cancelable (private=, expected=0,
futex_word=0x562135d9eac0) at ../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x562135d9ea70,
cond=0x562135d9ea98) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x562135d9ea98, mutex=0x562135d9ea70) at
pthread_cond_wait.c:655
#3  0x7fa784d2c43b in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fa786966279 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#5  0x7fa7869664da in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#6  0x7fa784d2bc87 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fa784894164 in start_thread (arg=) at
pthread_create.c:486
#8  0x7fa784a0fdef in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 11 (Thread 0x7fa6c7fff700 (LWP 3289)):
#0  futex_wait_cancelable (private=, expected=0,
futex_word=0x562135a214b4) at ../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x562135a21460,
cond=0x562135a21488) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x562135a21488, 

[frameworks-kcmutils] [Bug 389585] Window is too small when KCMs are opened standalone (e.g. using `kcmshell5), and contents get cut off

[Nate Graham]

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

--- Comment #40 from Nate Graham  ---
(In reply to Dr. Chapatin from comment #36)
> Created attachment 114815 [details]
> Network kcm on neon dev unstable. Hidden buttons on bottom.

Looks like this particular issue is caused by
https://bugreports.qt.io/browse/QTBUG-3459, as Valeriy indicates.

I'd prefer to go the route of fixing it in Qt rather than working around it
locally (though that's an option too, if worse comes to worst).


So it seems that we have three angles of attack:

1. Fix individual KCMs that don't give us proper SizeHints, now that kcmshell
*pays attention to sizeHints. Bugseforuns, since you're carefully tracking the
issues here, would you like to un-dupe the bugs for individual KCMs that still
need adjustment and add appropriate comments?

2. Fix or work around https://bugreports.qt.io/browse/QTBUG-3459 so that KCMs
sizeHints are actually properly respected on short screens. Valeriy, would you
be interested in tackling that?

3. Fix the issue with the fix for this bug not working for HiDPI. Andrew, since
you have a HiDPI screen, would you like to investigate this part?

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

[plasmashell] [Bug 398362] Unreliable behavior of control buttons

[avlas]

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

--- Comment #2 from avlas  ---
Oops I'm very sorry, I have submitted all these bugs to the wrong target. Now
that you say, I'm sure I use plasmashell Global Menu (using KDE neon User
Edition 18.04 with plasma 5.13.5).

Regarding the specifics of this bug, Libreoffice menues work fine other than
this reported issue, as far as I can tell (which surprised me as previous
attempts with LO, and also firefox failed at large).

Unfortunately, I am not aware of any other application with control buttons in
the menu to test if this is or not specific of Libreoffice. If you would know
of an application, I am willing to test, assumed it is easy to
install/uninstall in my system.

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

[frameworks-kcmutils] [Bug 389585] Window is too small when KCMs are opened standalone (e.g. using `kcmshell5), and contents get cut off

[bugzilla_noreply]

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

--- Comment #39 from tr...@yandex.com ---
(In reply to Dr. Chapatin from comment #36)
> Created attachment 114815 [details]
> Network kcm on neon dev unstable. Hidden buttons on bottom.

Confirm this.

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

[plasma-nm] [Bug 398363] Network manager loses credentials info

[bugzilla_noreply]

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

--- Comment #2 from marcin.ba...@gmail.com ---
Created attachment 114829
  --> https://bugs.kde.org/attachment.cgi?id=114829=edit
Connection info after restart services

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

[plasma-nm] [Bug 398363] Network manager loses credentials info

[bugzilla_noreply]

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

--- Comment #1 from marcin.ba...@gmail.com ---
Created attachment 114828
  --> https://bugs.kde.org/attachment.cgi?id=114828=edit
Edit connections window

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

[plasmashell] [Bug 398362] Unreliable behavior of control buttons

[Kai Uwe Broulik]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

 CC||k...@privat.broulik.de,
   ||plasma-b...@kde.org
Product|kded-appmenu|plasmashell
   Target Milestone|--- |1.0
   Assignee|plasma-b...@kde.org |k...@privat.broulik.de
  Component|top menubar |Global Menu

--- Comment #1 from Kai Uwe Broulik  ---
Are you really using Plasma 5.9.3? I recall LibreOffice's own global menu
implementation to be quite buggy and unreliable.

Also, kded-appmenu top menubar is deprecated and not used in Plasma 5, the
component responsible for that is plasmashell Global Menu

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

[plasma-nm] [Bug 398363] New: Network manager loses credentials info

[bugzilla_noreply]

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

Bug ID: 398363
   Summary: Network manager loses credentials info
   Product: plasma-nm
   Version: 5.13.5
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: applet
  Assignee: jgrul...@redhat.com
  Reporter: marcin.ba...@gmail.com
  Target Milestone: ---

Created attachment 114827
  --> https://bugs.kde.org/attachment.cgi?id=114827=edit
Edit connection with empty fields

Sometimes plasma-nm loses all connection info.
When I click "connect" to WiFi network a window with empty fields is displayed
(edit-wifi.png attachment), but when I click on "Edit connections" some fields
are filed (connections.png attachment) without password.
For other WiFi connections(with password only) plasma-nm asks for password but
is not able to connect.
All passwords are stored in kwallet.
I can't connect to other wired networks too. Click on "connect" does nothing.

Plasma network manager loses all connection info and passwords.

Command:
$sudo systemctl restart network NetworkManager
or restart of computer sometimes resolves the problem
(connection_info_after_restart_services.png attachment)

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

[kded-appmenu] [Bug 398362] New: Unreliable behavior of control buttons

[avlas]

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

Bug ID: 398362
   Summary: Unreliable behavior of control buttons
   Product: kded-appmenu
   Version: 5.9.3
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: top menubar
  Assignee: plasma-b...@kde.org
  Reporter: jsar...@gmail.com
  Target Milestone: ---

When these items are pressed in the top menubar, function is not affected,
however their appearance is unreliable: several conflicting radiobuttons
checked at once, checkboxes that appear the opposite of current configuration,
etc.

This only happens in the top menubar and was tested with checkboxes and
radiobuttons in Libreoffice "Visualize" menu.

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

[plasmashell] [Bug 394476] Can't edit applications that are installed through flatpak

[Dr . Chapatin]

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

Dr. Chapatin  changed:

   What|Removed |Added

 CC||bugsefor...@gmx.com

--- Comment #1 from Dr. Chapatin  ---
Created attachment 114826
  --> https://bugs.kde.org/attachment.cgi?id=114826=edit
screenshot

Same bug on Arch Linux, plasma 5.13.5.

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

[kded-appmenu] [Bug 398361] New: Moving across menues sometimes breaks (e.g., when an empty menu is encountered)

[avlas]

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

Bug ID: 398361
   Summary: Moving across menues sometimes breaks (e.g., when an
empty menu is encountered)
   Product: kded-appmenu
   Version: 5.9.3
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: top menubar
  Assignee: plasma-b...@kde.org
  Reporter: jsar...@gmail.com
  Target Milestone: ---

This happens only in the top menubar. Tested in Kate's "Bookmarks" and
Konqueror's "Tools" menues.

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

[plasmashell] [Bug 393401] Kickoff favorites should update with "Show applications by name"

[Dr . Chapatin]

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

Dr. Chapatin  changed:

   What|Removed |Added

 CC||bugsefor...@gmx.com

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

[plasmashell] [Bug 398360] last menu entries remain accessible and functional when no window is under focus

[Kai Uwe Broulik]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

   Target Milestone|--- |1.0
   Assignee|plasma-b...@kde.org |k...@privat.broulik.de
  Component|top menubar |Global Menu
Product|kded-appmenu|plasmashell
 CC||k...@privat.broulik.de,
   ||plasma-b...@kde.org

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

[kded-appmenu] [Bug 398360] New: last menu entries remain accessible and functional when no window is under focus

[avlas]

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

Bug ID: 398360
   Summary: last menu entries remain accessible and functional
when no window is under focus
   Product: kded-appmenu
   Version: 5.9.3
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: top menubar
  Assignee: plasma-b...@kde.org
  Reporter: jsar...@gmail.com
  Target Milestone: ---

I think that the menues should be gone from the top menubar when the window is
not under focus (i.e., the focus is on plasma's desktop). This should be
straightforward to fix by checking if the window is active.

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

[plasmashell] [Bug 398359] App entry is not updated correctly when "name" and/or "description" fields are edited in "Edit application..." window

[Kai Uwe Broulik]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

 CC||k...@privat.broulik.de

--- Comment #1 from Kai Uwe Broulik  ---
Likely same root cause as Bug 393401

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

[frameworks-ktexteditor] [Bug 382075] Solarized light color schema is outdated or uses wrong colors

[Michael D]

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

--- Comment #4 from Michael D  ---
Thanks for taking the time to fix this!

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