[lokalize] [Bug 346784] Drag and drop of text keeps original text in place

[Simon Depiets]

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

Simon Depiets  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|ASSIGNED|RESOLVED

--- Comment #3 from Simon Depiets  ---
Fixed in 
https://phabricator.kde.org/D14177

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

[lokalize] [Bug 389285] Delete all translated strings

[Simon Depiets]

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

Simon Depiets  changed:

   What|Removed |Added

   Assignee|sha...@ukr.net  |sdepi...@gmail.com
 CC||sdepi...@gmail.com
 Ever confirmed|0   |1
 Status|UNCONFIRMED |ASSIGNED

--- Comment #2 from Simon Depiets  ---
You don't always have the .pot file, this can be useful.

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

[KScreen] [Bug 356864] Plasma cannot adapt to VM host window

[bugzilla_noreply]

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

--- Comment #46 from ccrompho_w...@hotmail.com ---
Hi,

Some more information since apparently the situation changed.
Whonix have been updated to 14. so the plasmashell have been integrated into a
debian stretch version. 
It's a fresh installation from whonix with the default VM.
The graphic card is QXL, the graphic server is spice. 
Since the starting resolution is 1024*768 , I've tried to changed it to
1440*900 but apparently your kscreen_backend doesn't like it. 
I got, on the next login/reboot, a segmentation fault at 10 ip 7f6eec42d568
sp 07ffcec4bdb60 error 4 in KSC_XRandR.so[7f6eec413000+23000]

I didn't test all the resolution yet but I guess some of them are buggy as
well. So you might look into that and test your kscreen_backend thoroughly
before put this bug as fixed. 

uname -a: 4.9.0.7-amd64 debian 4.9.110-3+deb9u1
kscreen: 4:5.8.5-2
libxrandr2: 2:1.5.1-1
plasma-framework: 5.20.0-2
plasma-desktop: 4:5.8.6-1

Tell me if you need something else...

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

[KScreen] [Bug 356864] Plasma cannot adapt to VM host window

[bugzilla_noreply]

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

ccrompho_w...@hotmail.com changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|FIXED   |---
 CC||ccrompho_w...@hotmail.com

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

[kde] [Bug 397259] New: Plasma Crashes after Clicking on Hamburger Menu on Panel

[Edward Reiss]

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

Bug ID: 397259
   Summary: Plasma Crashes after Clicking on Hamburger Menu on
Panel
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: ebre...@fastmail.com
  Target Milestone: ---

Application: plasmashell (5.13.4)

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

-- Information about the crash:
- What I was doing when the application crashed:
 I clicked on the Hamburger menu button on the panel. This happens after I
click twice on the menu.

The crash can be reproduced every time.

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

Thread 16 (Thread 0x7fcc04c06700 (LWP 3652)):
#0  0x7fccd69ff2c9 in poll () at /lib64/libc.so.6
#1  0x7fccd08f12c6 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fccd08f13ec in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fccd730cb3b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fcbf80c87c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7fccd72bcb3b in
QEventLoop::exec(QFlags) (this=0x7fcc04c05d20,
flags=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140
#5  0x7fccd711b326 in QThread::exec() (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:120
#6  0x7fccdabcab55 in QQmlThreadPrivate::run() (this=0x559f539fcb80) at
/usr/src/debug/libqt5-qtdeclarative-5.11.1-1.2.x86_64/src/qml/qml/ftw/qqmlthread.cpp:148
#7  0x7fccd71248ec in QThreadPrivate::start(void*) (arg=0x559f539fcb80) at
thread/qthread_unix.cpp:367
#8  0x7fccd62b4554 in start_thread () at /lib64/libpthread.so.0
#9  0x7fccd6a09ccf in clone () at /lib64/libc.so.6

Thread 15 (Thread 0x7fcbb700 (LWP 3535)):
#0  0x7fccd62ba4dc in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fccd7124fab in QWaitConditionPrivate::wait(unsigned long)
(time=18446744073709551615, this=0x7fcbcc0438b0) at
thread/qwaitcondition_unix.cpp:143
#2  0x7fccd7124fab in QWaitCondition::wait(QMutex*, unsigned long)
(this=, mutex=0x559f5cbed1f0, time=18446744073709551615) at
thread/qwaitcondition_unix.cpp:215
#3  0x7fccdb0d2139 in QSGRenderThreadEventQueue::takeEvent(bool)
(wait=true, this=0x559f5cbed1e8) at
/usr/src/debug/libqt5-qtdeclarative-5.11.1-1.2.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:245
#4  0x7fccdb0d2139 in QSGRenderThread::processEventsAndWaitForMore()
(this=this@entry=0x559f5cbed170) at
/usr/src/debug/libqt5-qtdeclarative-5.11.1-1.2.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:709
#5  0x7fccdb0d236a in QSGRenderThread::run() (this=0x559f5cbed170) at
/usr/src/debug/libqt5-qtdeclarative-5.11.1-1.2.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:738
#6  0x7fccd71248ec in QThreadPrivate::start(void*) (arg=0x559f5cbed170) at
thread/qthread_unix.cpp:367
#7  0x7fccd62b4554 in start_thread () at /lib64/libpthread.so.0
#8  0x7fccd6a09ccf in clone () at /lib64/libc.so.6

Thread 14 (Thread 0x7fcbe5c1f700 (LWP 3534)):
#0  0x7fccd69ff2c9 in poll () at /lib64/libc.so.6
#1  0x7fccce2859b1 in  () at /usr/lib64/libpulse.so.0
#2  0x7fccce2771e0 in pa_mainloop_poll () at /usr/lib64/libpulse.so.0
#3  0x7fccce27782e in pa_mainloop_iterate () at /usr/lib64/libpulse.so.0
#4  0x7fccce2778e0 in pa_mainloop_run () at /usr/lib64/libpulse.so.0
#5  0x7fccce2858f9 in  () at /usr/lib64/libpulse.so.0
#6  0x7f487658 in  () at /usr/lib64/pulseaudio/libpulsecommon-12.2.so
#7  0x7fccd62b4554 in start_thread () at /lib64/libpthread.so.0
#8  0x7fccd6a09ccf in clone () at /lib64/libc.so.6

Thread 13 (Thread 0x7fcbbf7fe700 (LWP 3211)):
#0  0x7fccd62ba4dc in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fccd7124fab in QWaitConditionPrivate::wait(unsigned long)
(time=18446744073709551615, this=0x559f5badad30) at
thread/qwaitcondition_unix.cpp:143
#2  0x7fccd7124fab in QWaitCondition::wait(QMutex*, unsigned long)
(this=, mutex=0x559f589bdc00, time=18446744073709551615) at
thread/qwaitcondition_unix.cpp:215
#3  0x7fccdb0d2139 in QSGRenderThreadEventQueue::takeEvent(bool)
(wait=true, this=0x559f589bdbf8) at
/usr/src/debug/libqt5-qtdeclarative-5.11.1-1.2.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:245
#4  0x7fccdb0d2139 in QSGRenderThread::processEventsAndWaitForMore()
(this=this@entry=0x559f589bdb80) at
/usr/src/debug/libqt5-qtdeclarative-5.11.1-1.2.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:709
#5  0x7fccdb0d236a in QSGRend

[krita] [Bug 397258] New: when rendering the animation, I get cut

[bugzilla_noreply]

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

Bug ID: 397258
   Summary: when rendering the animation, I get cut
   Product: krita
   Version: 4.0.2
  Platform: PCLinuxOS
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: Animation
  Assignee: krita-bugs-n...@kde.org
  Reporter: paulinamateus2...@gmail.com
  Target Milestone: ---

When I use the program, everything works correctly until I see the video
animation, it is cut and fails to play, I tried in formats like mkv, mp4 or ogg

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

[Discover] [Bug 397257] New: Two entries for Adapta, neither can be removed

[Buck Shockley]

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

Bug ID: 397257
   Summary: Two entries for Adapta, neither can be removed
   Product: Discover
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: KNewStuff Backend
  Assignee: aleix...@kde.org
  Reporter: darkwingbuc...@gmail.com
CC: lei...@leinir.dk
  Target Milestone: ---

Created attachment 114369
  --> https://bugs.kde.org/attachment.cgi?id=114369&action=edit
Screenshot of Installed list

I have two entries for Adapta KDE in my Discover Installed listing but it
doesn't do anything when I try to remove them. The program cannot be closed and
there are no entries for them in System Settings.

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

[frameworks-kwayland] [Bug 373907] Implement Wayland Primary Selection Protocol (middle-click paste)

[Gaël de Chalendar]

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

Gaël de Chalendar (aka Kleag)  changed:

   What|Removed |Added

 CC||kl...@free.fr

--- Comment #15 from Gaël de Chalendar (aka Kleag)  ---
Apart from a kmail crash at startup, this is the only thing that will keep me
away from Wayland at this time.
This is probably the basic feature that makes my desktop so much more usable
than other ones.

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

[valgrind] [Bug 397256] New: Valgrind 3.13.0 fails with simple executable which was compiled with swift 3.1.1 on arm32

[Tabor Kelly]

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

Bug ID: 397256
   Summary: Valgrind 3.13.0 fails with simple executable which was
compiled with swift 3.1.1 on arm32
   Product: valgrind
   Version: 3.13.0
  Platform: Debian stable
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: taborke...@gmail.com
  Target Milestone: ---

Created attachment 114368
  --> https://bugs.kde.org/attachment.cgi?id=114368&action=edit
Simple swift project, plus logs

I am running Debian Stretch (9/stable) on an arm32 device. I am using a ported
version of the Swift 3.1.1 compiler which William Dillon provides:
http://www.housedillon.com/other/swift-3.1.1.tgz

I simply unpacked swift-3.1.1.tgz in /opt/swift-3.1.1:
which swift
/opt/swift-3.1.1/usr/bin/swift

I have compiled the Valgrind 3.13.0 release and also install it in my /opt:
which valgrind
/opt/valgrind-3.13.0/bin/valgrind

I have attached a simple swift project, barely more complicated than "Hello
World" which runs fine by itself but fails under valgrind. It includes a log of
compiling and running successfully (swift_build_and_run.log) as well as a log
of valgrind failing (valgrind_failure.log).

Please let me know if there is any other information that I can provide.

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

[frameworks-baloo] [Bug 397255] New: Baloo crashes at a gust of wind and has horrible error handling.

[Logan Rathbone]

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

Bug ID: 397255
   Summary: Baloo crashes at a gust of wind and has horrible error
handling.
   Product: frameworks-baloo
   Version: 5.48.0
  Platform: Slackware Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: Baloo File Daemon
  Assignee: baloo-bugs-n...@kde.org
  Reporter: popro...@gmail.com
  Target Milestone: ---

It's difficult for me to really report this issue as a singular crash within
Baloo. After suffering so many random crashes that are unrecoverable unless the
index is deleted and rebuilt from scratch, I have decided to report this as a
singular bug.

Baloo crashes often, for a variety of reasons, and has very poor error
handling.

The primary issue is *not* the mere fact that Baloo crashes. Almost all
programs are bound to crash from time to time. The issue is, Baloo fails
silently and seems to have virtually no recovery mechanism whatsoever.

On 5.47.0 about two weeks ago, my database at ~/.local/share/baloo/index became
corrupt, which resulted in baloo leaking memory until my 8 GB of RAM were all
eaten up, and the kernel had to kill it with OOM killer.

On 5.48.0, everything was working swimmingly for about a week and a half. Then,
I printed an email from Seamonkey Mail to PDF. Baloo's attempt to index this
file inexplicably caused Baloo to crash, and my index again became corrupt.

This time, thankfully, there is no memory leak, but even after logging out,
killing baloo_file (which had to be done manually since the process was still
running after logout [see, eg, https://bugs.kde.org/show_bug.cgi?id=391253]),
removing ~/.local/share/baloo/index-lock, removing the offending file, and
restarting Plasma5, baloo has now become extremely crashy and unstable.

Now, introducing any file into $HOME causes a crash. Even running "touch foo"
in my $HOME causes a crash.

At any rate, these issues sound very, very difficult to debug. Just pointing
your browser to https://bugs.kde.org/buglist.cgi?quicksearch=baloo is extremely
overwhelming. Rather than trying to bandage these bugs one by one, would it not
make more sense to build more user-friendly error handling into Baloo? Is it
absolutely impossible to repair a baloo database without doing a full rebuild?
Perhaps upon crash due to a corrupt DB, baloo could auto-repair itself?

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

[kate] [Bug 385520] Kate's tabs don't respect the theme and look like they came from Adwaita

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||tcanabr...@kde.org

--- Comment #11 from Nate Graham  ---
(In reply to k3bBug from comment #10)
> Why is it that the default tab bar can not be multirow?
There are other bugs tracking changes to tab behavior. This bug is purely about
visual appearance.

Thanks for the history, Dominik. To be clear, this bug is not proposing any
behavioral changes at all. Personally I don't have a problem with the overflow
behavior. This bug is only tracking a proposal to make the tabs' visual
appearance match the rest of Qt and KDE software. In theory, the only
implementation detail it proposes to change is to use a QTabBar instead of a
custom widget, and of course to port the features so no current functionality
is lost.

I was kind of hoping that Tomaz Canabrava would stumble on this and volunteer
once he gets finished with his Konsole tab bar re-work. He seems to like
hacking on tab bars. :)

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

[plasmashell] [Bug 397251] Unable change desktop or lockscreen wallpapers

[acidrums4]

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

acidrums4  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |INVALID

--- Comment #6 from acidrums4  ---
(In reply to David Edmundson from comment #5)
> > kpluginindex.json
> 
> try either deleting this or running sudo kpackagetool5 --generate-index -g

It did it! Thank you so much :)

> And if you can read gentoo packaging to see if the emerge is calling
> something like that last line explicitly that would be much appreciated.
> It's not from any KDE code.

Well, I just did:

grep -r kpackagetools5 /usr/portage
grep -r kpackagetools5 /var/lib/layman/kde
grep -r kpluginindex.json /usr/portage
grep -r kpluginindex.json /var/lib/layman/kde

and all of them returned nothing. Not sure if that's what you meant but I guess
it didn't came from any KDE ebuild but rather from an plasma widget I got from
the store quite time ago.

However, than you so much for your help. Leaving this as invalid, as I could
finally confirm this wasn't related to upstream.

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

[kipiplugins] [Bug 389794] "Print Images" always greyed out when opening "Plugins" menu the first time

[Henrik Fehlauer]

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

Henrik Fehlauer  changed:

   What|Removed |Added

Product|gwenview|kipiplugins
  Component|general |general
   Assignee|gwenview-bugs-n...@kde.org  |imaging-bugs-n...@kde.org
Version|18.04.3 |5.8.0
 CC||rk...@lab12.net

--- Comment #4 from Henrik Fehlauer  ---
Let's move this bug to kipi-plugins for now, since Gwenview has no special
handling for specific plugins, and for other plugins it's working fine (why,
though?). It might very well be an old problem which only surfaced due to
1fc7d86dbc94.

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

[plasmashell] [Bug 397251] Unable change desktop or lockscreen wallpapers

[David Edmundson]

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

--- Comment #5 from David Edmundson  ---
> kpluginindex.json

try either deleting this


or running 

sudo kpackagetool5 --generate-index -g



And if you can read gentoo packaging to see if the emerge is calling something
like that last line explicitly that would be much appreciated. It's not from
any KDE code.

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

[plasma-browser-integration] [Bug 397254] New: No widgets at all, as if it wasn't installed

[bugzilla_noreply]

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

Bug ID: 397254
   Summary: No widgets at all, as if it wasn't installed
   Product: plasma-browser-integration
   Version: unspecified
  Platform: Manjaro
OS: Linux
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: general
  Assignee: k...@privat.broulik.de
  Reporter: albytt...@protonmail.com
  Target Milestone: ---

All of the required packages are installed yet they provide almost no
functionality. I have both the plugins for Chromium and Firefox, and the
plasma-browser-integration package. I can search for browser tabs for both
Chromium and Firefox in KRunner, but that's about it. There are no widgets for
the browsers' media players or notifications about downloads.

I've restarted my computer several times, and reinstalled the browsers, their
plugins, and the plasma-browser-integration package several times as well, to
no avail.

Versions:
Kernel 4.17.12-1.1
Manjaro 17.1.11
KDE Plasma 5.13.4
Chromium 68.0.3440.84 
Firefox 61.0.1-1
plasma-browser-integration 5.13.4-1

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

[kdenlive] [Bug 397253] New: Opening error when double click project file

[bugzilla_noreply]

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

Bug ID: 397253
   Summary: Opening error when double click project file
   Product: kdenlive
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: kav3man1...@gmail.com
  Target Milestone: ---

I get an error when i double click to open the project file withing the project
folder:

Cannot open the project file,
Do you want to open backup file?

If I open the backup file i loose part of my progress but if I don't open the
backup file kdenlive open to a blank project.

by going to File/Open Recent the project open without any errors.

I am running it in Lubuntu 16.04 LTS 

Kdenlive Version 15.12.3

Using:
KDE Frameworks 5.18.0
Qt 5.5.1 (built against 5.5.1)
The xcb windowing system

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

[kate] [Bug 385520] Kate's tabs don't respect the theme and look like they came from Adwaita

[k3bBug]

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

--- Comment #10 from k3bBug  ---
Why is it that the default tab bar can not be multirow?

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

[plasmashell] [Bug 397251] Unable change desktop or lockscreen wallpapers

[acidrums4]

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

--- Comment #4 from acidrums4  ---
(In reply to David Edmundson from comment #1)
> Please include:
>  - a screenshot
>  - ls of /usr/share/plasma/wallpapers

Thank you so much for your quick answer. Here's the ls output:

ls -alLh /usr/share/plasma/wallpapers
total 40K
drwxr-xr-x  6 root root  124 ago  7 16:46 .
drwxr-xr-x 11 root root 4,0K may 12  2017 ..
-rw-r--r--  1 root root  33K nov  4  2017 kpluginindex.json
drwxr-xr-x  3 root root  101 ago  7 07:02 org.kde.color
drwxr-xr-x  4 root root   87 ago  7 07:02 org.kde.image
drwxr-xr-x  3 root root   64 jul 14 07:02 org.kde.plasma.worldmap
drwxr-xr-x  3 root root   64 ago  7 07:02 org.kde.slideshow

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

[plasmashell] [Bug 397251] Unable change desktop or lockscreen wallpapers

[acidrums4]

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

--- Comment #3 from acidrums4  ---
Created attachment 114367
  --> https://bugs.kde.org/attachment.cgi?id=114367&action=edit
Screenshot from Settings->Desktop behavior->Lockscreen->Visual

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

[plasmashell] [Bug 397251] Unable change desktop or lockscreen wallpapers

[acidrums4]

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

--- Comment #2 from acidrums4  ---
Created attachment 114366
  --> https://bugs.kde.org/attachment.cgi?id=114366&action=edit
Screenshot from right-click->Desktop settings->Desktop wallpaper

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

[kdeplasma-addons] [Bug 355322] The keyboard shortcut to the Application Dashboard doesn't work after KDE startup

[Xavion]

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

Xavion  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #7 from Xavion  ---
No, it seems to have been fixed.  I haven't seen it for a while.

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

[plasmashell] [Bug 397251] Unable change desktop or lockscreen wallpapers

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|UNCONFIRMED |NEEDSINFO
 CC||k...@davidedmundson.co.uk

--- Comment #1 from David Edmundson  ---
Please include:
 - a screenshot
 - ls of /usr/share/plasma/wallpapers

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

[valgrind] [Bug 385409] s390x: z13 vector integer instructions not implemented

[Vadim Barkov]

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

--- Comment #46 from Vadim Barkov  ---
Since the issue is solved, is it ready to merge? Or additional testing is
needed?

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

[valgrind] [Bug 385409] s390x: z13 vector integer instructions not implemented

[Vadim Barkov]

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

--- Comment #45 from Vadim Barkov  ---
(In reply to Julian Seward from comment #44)

The new VFENE implementation has no problems. I just want to point you that in
my opinion the memchecks' "Conditional jump or move depends on uninitialised
value(s)" error for "VFENEZB %v0, %v0, %v0" instruction (which is used in
inline ) can be considered as correct error (from some point of view it is not
false positive).

Let's assume that we have a vector register %v0:
0xaa11223344556677, 0x8800 -- the contents of %v0
"?" sign means that that bytes are uninitialized/undefined for some reason
(e.g. 
 because of "vector load with length" VLL instruction)

We have "VFENEZBS %v0, %v0, %v0" instruction in code. It searchs for the zero
byte in %v0, writes the index of zero byte in byte 7 of %v0 and upgrades
condition code (CC, used for branches)
The result of execution is:
0x009, 0x -- the new contents of %v0

On the one hand this result is memcheck clean (there is issues like
"Conditional jump or move depends on uninitialised value(s)") because the CPU
works using this algorithm:

int index;
for(index = 0; index < 16; index++) {
   if(v0[index] == 0)
  break;
}
return index;

But on the other hand the S390x specification ("z/Archtecture. Principles of
Operation", SA22-7832-10) says that VFENE with ZS flag set (if mnemonic of
operation contains the letter "Z") reads all bytes of second operand (in our
example from %v0). So we get situation when instruction reads uninitialized
bytes.
Is the result of this instruction detemined in the terms of valgrind's
terminology? That's my question.

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

[kdenlive] [Bug 379490] Crop, Scale and Tilt effect not working [video example included]

[Adam Spiers]

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

Adam Spiers  changed:

   What|Removed |Added

 CC||kde-b...@adamspiers.org

--- Comment #6 from Adam Spiers  ---
I see this too.  Is there any reason why it can't have usable default values?

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

[plasma-nm] [Bug 397252] Network manager asks for WIFI password after resume from sleep

[bugzilla_noreply]

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

alex...@gmx.net changed:

   What|Removed |Added

 CC||alex...@gmx.net

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

[plasma-nm] [Bug 397252] New: Network manager asks for WIFI password after resume from sleep

[bugzilla_noreply]

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

Bug ID: 397252
   Summary: Network manager asks for WIFI password after resume
from sleep
   Product: plasma-nm
   Version: 5.12.6
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jgrul...@redhat.com
  Reporter: alex...@gmx.net
  Target Milestone: ---

After resuming from sleep, i.e. the laptop was closed, the network manager does
not reconnect automatically but asks again for the WIFI password. 

However, it is not needed to enter it again as is still enough to select the
relevant network in the network manager to reconnect.

(Ubuntu 18.04.1 LTS, 4.17.13 mainline kernel, iwlwifi driver)

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

[plasmashell] [Bug 397251] New: Unable change desktop or lockscreen wallpapers

[acidrums4]

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

Bug ID: 397251
   Summary: Unable change desktop or lockscreen wallpapers
   Product: plasmashell
   Version: 5.13.3
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Image Wallpaper
  Assignee: notm...@gmail.com
  Reporter: acidrums4+st...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

(Reporting as a bug as I got no help on forums).

>From 5.12 onwards, every time I right-click on the desktop or try to change
lockscreen wallpaper, the"Wallpaper type" (or what is says in english)
selection widget has no options.

I tried creating a whole new user on my system, but from there the thing is the
same.

Expected results: Being able to select "static image", "color" and etc (and
being able to select an image when selecting "static image") when changing
lockscreen and desktop wallpapers.

Still I can change desktop wallpaper by dragging an image file from Dolphin.
Alas I don't know if there's a similar workaround for changing the lock screen
wallpaper.

The output of plasmashell can be found here (there are some weird things there,
but I don't know if they're relevant to this): https://pastebin.com/w2rcTadT

OS: Gentoo amd64
Plasma 5.13 & Frameworks 5.48 from the KDE overlay.

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

[plasmashell] [Bug 397206] Kicker: submenus are too wide after opening Recent Documents containing long filename

[Albert Astals Cid]

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

--- Comment #6 from Albert Astals Cid  ---
(In reply to Eike Hein from comment #5)
> Maybe we misunderstood each other somehow (or I misunderstood). Do you have
> time to write the alternate patch?

I'll make some time during Akademy (next week)

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

[frameworks-baloo] [Bug 396218] Crash on log-in

[Brett Keller]

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

--- Comment #2 from Brett Keller  ---
Created attachment 114363
  --> https://bugs.kde.org/attachment.cgi?id=114363&action=edit
New crash information added by DrKonqi

baloo_file (5.44.0) using Qt 5.9.5

- What I was doing when the application crashed:

Noticed this just after untarring a file via Dolphin's context menu, but this
was not long after login, so it may have simply been triggered by login.

-- Backtrace (Reduced):
#6  __memmove_avx_unaligned_erms () at
../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:370
#7  0x7f4dbd4d7973 in memcpy (__len=2050, __src=,
__dest=) at
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:34
#8  Baloo::PostingCodec::decode (this=this@entry=0x7f4db3377a77, arr=...) at
./src/codecs/postingcodec.cpp:42
#9  0x7f4dbd4c93e4 in Baloo::PostingDB::get
(this=this@entry=0x7f4db3377b60, term=...) at ./src/engine/postingdb.cpp:100
#10 0x7f4dbd4d5060 in Baloo::WriteTransaction::commit (this=0x7f4dac035160)
at ./src/engine/writetransaction.cpp:259

--- Comment #3 from Brett Keller  ---
Created attachment 114365
  --> https://bugs.kde.org/attachment.cgi?id=114365&action=edit
New crash information added by DrKonqi

baloo_file (5.44.0) using Qt 5.9.5

- What I was doing when the application crashed:

Noticed this just after untarring a file via Dolphin's context menu, but this
was not long after login, so it may have simply been triggered by login.

-- Backtrace (Reduced):
#6  __memmove_avx_unaligned_erms () at
../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:370
#7  0x7f4dbd4d7973 in memcpy (__len=2050, __src=,
__dest=) at
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:34
#8  Baloo::PostingCodec::decode (this=this@entry=0x7f4db3377a77, arr=...) at
./src/codecs/postingcodec.cpp:42
#9  0x7f4dbd4c93e4 in Baloo::PostingDB::get
(this=this@entry=0x7f4db3377b60, term=...) at ./src/engine/postingdb.cpp:100
#10 0x7f4dbd4d5060 in Baloo::WriteTransaction::commit (this=0x7f4dac035160)
at ./src/engine/writetransaction.cpp:259

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

[frameworks-baloo] [Bug 396218] Crash on log-in

[Brett Keller]

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

--- Comment #2 from Brett Keller  ---
Created attachment 114363
  --> https://bugs.kde.org/attachment.cgi?id=114363&action=edit
New crash information added by DrKonqi

baloo_file (5.44.0) using Qt 5.9.5

- What I was doing when the application crashed:

Noticed this just after untarring a file via Dolphin's context menu, but this
was not long after login, so it may have simply been triggered by login.

-- Backtrace (Reduced):
#6  __memmove_avx_unaligned_erms () at
../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:370
#7  0x7f4dbd4d7973 in memcpy (__len=2050, __src=,
__dest=) at
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:34
#8  Baloo::PostingCodec::decode (this=this@entry=0x7f4db3377a77, arr=...) at
./src/codecs/postingcodec.cpp:42
#9  0x7f4dbd4c93e4 in Baloo::PostingDB::get
(this=this@entry=0x7f4db3377b60, term=...) at ./src/engine/postingdb.cpp:100
#10 0x7f4dbd4d5060 in Baloo::WriteTransaction::commit (this=0x7f4dac035160)
at ./src/engine/writetransaction.cpp:259

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

[frameworks-baloo] [Bug 396218] Crash on log-in

[Brett Keller]

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

Brett Keller  changed:

   What|Removed |Added

 CC||blkel...@comcast.net

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

[kdenlive] [Bug 397250] All slowmotion effects in project lost upon saving

[Dominik Leiner]

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

--- Comment #1 from Dominik Leiner  ---
I should add that the project (throughout many file versions) showed an alert
about clip problems when loading, although the list of problems was void.

The system I run kdenlive on is an Ubuntu 16.04.

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

[kdenlive] [Bug 397250] New: All slowmotion effects in project lost upon saving

[Dominik Leiner]

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

Bug ID: 397250
   Summary: All slowmotion effects in project lost upon saving
   Product: kdenlive
   Version: 18.04.1
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: Effects & Transitions
  Assignee: vpi...@kde.org
  Reporter: m...@dominik-leiner.de
  Target Milestone: ---

I am working in a kdenlive project with lots of clips, and many of them have a
"Speed" effect, often 300 to 1000%.

This worked fine for a while, but after a few hours of cutting and shifting
clips, and adding and removing clips, I had all but few clips marked and
shifted. Then kdenlive crashed, which is not very uncommon. When opening the
last saved version, kdenlive told me that invalid transitions were removed. The
reason for them getting invalid was that *all* "Speed" (slowmotion) effects
were lost, which changed the clip duration, and caused overlaps.

I already had this issue in the previous AppImage (17.x) in a different
project. Unfortunately, it again appeared in 18.04.1 now. My gut feeling is
that it happens when moving a large number of clips on the timeline, but I was
unable to deliberately trigger the bug so far.

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

[frameworks-kio] [Bug 374048] Feature Request: add octal format to file permissions.

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org
 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

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

[kwin] [Bug 396546] Mouse remote control causes KDE Plasma (Wayland) to Crash

[DevPre24]

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

DevPre24  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #6 from DevPre24  ---
On Kde Plasma 5.13.4 it's not an issue anymore. The remote keyboard still
doesn't work though.

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

[kate] [Bug 385520] Kate's tabs don't respect the theme and look like they came from Adwaita

[Dominik Haumann]

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

--- Comment #9 from Dominik Haumann  ---
@Nate: I will give some background here.

Traditionally, Kate did not have tabs for over 15 years. The reason was always
that tabs do not scale: It is not uncommon that users have many many files open
(say >50), navigating between files then will simply not work anymore.
Therefore, Kate always only had the so called "Documents" list as sidebar,
which displays all opened files in a list view or tree view.

Over time, some developers (including me) added some tab bar plugins, which
could be enabled. There was a simple tab bar that more looked like an embedded
toolbar. Then there was the multiline tab bar (by me), and I think even more.
You can read about some of them here:
https://kate-editor.org/2011/04/25/kates-tab-bar-plugins/

For Kate 5, we decided to follow the users' request and added a tabbar by
default. However, we decided that this tabbar should be tightly integrated with
the quick open feature (CTRL+ALT+O). The idea was to show as many tabs as
possible, and tell the user how many documents do not fit anymore into the
tabbar. These documents can then be quickly accessed via CTRL+ALT+O.

Many users seem to like how this works right now. Maybe many also don't. Fact
is: You will always find some who don't and have a loud voice.

In this case: I can see that the tabbar is different, because it has absolutely
nothing to do with a tabbar of e.g. console, dolphin, ... It works different by
design.

Now of course it may very well be that we completely borked things, and we
simply did a bad job (which is most likely the case). But let me put it like
this: Changing this to simple tabs like Dolphin won't cut it. Before changing
this, this needs to be very well designed in the workflow. Compare with Visual
Studio, compare with all the other text editors out there. Compare with
extensions for Visual Studio. You will find 10+ different implementations, all
having their strength and weaknesses.

If our only weakness right now is the visual appearance and possibly a slightly
different behavior, then maybe it's not the worst solution.

PS: I currently do not have plans to change the current implementation. But of
course, patches are welcome.

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

[plasmashell] [Bug 397152] [wayland] - Support Window Previews

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |MOVED
 CC||k...@davidedmundson.co.uk

--- Comment #3 from David Edmundson  ---
We have new feature tracking on phabricator.

I appreciate that it's really confusing for us to have things in two places,
but it's worse to have the same data in both.

https://phabricator.kde.org/T9233

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

[systemdgenie] [Bug 397249] New: Ability to add/edit and remove timers

[clivejo]

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

Bug ID: 397249
   Summary: Ability to add/edit and remove timers
   Product: systemdgenie
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: rthoms...@gmail.com
  Reporter: cliv...@protonmail.com
  Target Milestone: ---

Would it be possible to offer a GUI to add, edit and remove timers via the
program?

Also, could you make an official release of this software?  It doesn't seem to
have made it out of download.kde.org/unstable

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

[krfb] [Bug 397248] Tray icon not used form Plasma theme

[varlesh]

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

--- Comment #1 from varlesh  ---
Created attachment 114362
  --> https://bugs.kde.org/attachment.cgi?id=114362&action=edit
preview bug

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

[krfb] [Bug 397248] New: Tray icon not used form Plasma theme

[varlesh]

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

Bug ID: 397248
   Summary: Tray icon not used form Plasma theme
   Product: krfb
   Version: unspecified
  Platform: Manjaro
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: grundleb...@googlemail.com
  Reporter: varl...@gmail.com
  Target Milestone: ---

All KDE applications used icons for tray from plasma theme. But KRFB not...
it's spoil style with monochrome icons on tray.
After add file krfb.svg on plasma theme with ID's:
- krfb
- 22-22-krfb
KRFB used system icon from system icon theme, but not from plasma theme.

https://github.com/PapirusDevelopmentTeam/adapta-kde/issues/73

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

[krita] [Bug 394974] Layer converted filter mask causes Krita crash most of the time.

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |INVALID

--- Comment #20 from Boudewijn Rempt  ---
I'm sorry, but I'm going to close this report. You're not clear on what your
system is, you're not clear on the description of what's going on, with what
we've got we cannot reproduce, and you're using an older version of Krita.

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

[krita] [Bug 394974] Layer converted filter mask causes Krita crash most of the time.

[Andras]

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

--- Comment #19 from Andras  ---
(In reply to Boudewijn Rempt from comment #18)
> Could it be that there was a problem with your old hardware?

That CPU is 1.5 years old only and it still works well on other MB and it'd be
crazy if Krita would be useless with 6th gen i3 CPU however yes, it could be
related to how Krita moreover my System is handling hardwares because there are
no more crash with 7th gen i7 CPU so far.

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

[valgrind] [Bug 385409] s390x: z13 vector integer instructions not implemented

[Julian Seward]

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

--- Comment #44 from Julian Seward  ---
(In reply to Vadim Barkov from comment #43)

> What do you think about it?

Honestly, I do not understand.  You need to explain much more clearly:

* what these instructions actually do

* what your implementation strategy is

* what the problem cases are

I have the impression from comment 34 that vfenezbs %v0, %v0, %v0 finds
the index of the first zero in the operand and writes that somewhere in
the result register.  (But why do they all have to to be v0 ?).  We have
solved such problems in the past for amd64 and so it would help if you
could relate your work to the amd64 implementation.

For amd64, we generate the sequence

  t1 = CmpEQ8x16(vec, zero-vector)
  t2 = pmovmskb(t1), which moves one bit from each lane into t2
  t3 = count-leading-zeroes(t2)

Because the count-leading-zeroes operation can be done in a way in
which the result is defined even if there are undefined bits to the
right of the leftmost 1 bit, this means that the resulting t3 value
will be defined if the input vector consisted of defined non-zero
bytes terminated by a defined-zero, even if the bytes after that
are undefined.

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

[systemsettings] [Bug 254560] Associate application as the default for all of its known compatible mimetypes

[Karl Ove Hufthammer]

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

Karl Ove Hufthammer  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1
 CC||k...@huftis.org

--- Comment #4 from Karl Ove Hufthammer  ---
Windows actually has a nice UI for this feature. Example screenshot:

https://filestore.community.support.microsoft.com/api/images/29fc882f-a9e4-40fc-9dcf-65ad6be91492

Perhaps worth using as inspiration?

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

[krusader] [Bug 397133] Krusader in root-mode don't start

[Alex Bikadorov]

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

Alex Bikadorov  changed:

   What|Removed |Added

 CC||alex.bikado...@kdemail.net
 Resolution|--- |INVALID
 Status|UNCONFIRMED |RESOLVED

--- Comment #4 from Alex Bikadorov  ---
It seems that kdesu is not working on your system in general.
This may be an issue with Mint or your installation but is not related to
Krusader.

About the workaround - specially for other people reading this ticket: Manually
removing or replacing binaries belonging to a distro package IS NOT
RECOMMENDED. You should avoid that!

I'm curious, are you the same guy asking here:
https://forum.ubuntuusers.de/topic/kdesudo-kdesu-missing/ ?

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

[gwenview] [Bug 389794] "Print Images" always greyed out when opening "Plugins" menu the first time

[Peter Mühlenpfordt]

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

--- Comment #3 from Peter Mühlenpfordt  ---
This was the commit where setEnabled() got lost on plugin init: 
https://cgit.kde.org/kipi-plugins.git/commit/?id=1fc7d86dbc94cb343b3c39b9dfda4d49a07f71e0
I'm not sure what the intention of this change was and if this should be fixed
in the plugin code or in Gwenview (and maybe digiKam).

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

[krita] [Bug 397247] Krita crashes upon drawing a text box.

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Resolution|--- |INVALID
 Status|UNCONFIRMED |RESOLVED
 CC||b...@valdyas.org

--- Comment #1 from Boudewijn Rempt  ---
I'm sorry, but that looks a flatpak packaging problem where some parts aren't
updated correctly. It's certianly not a problem in Krita's code :-(

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

[krita] [Bug 397247] New: Krita crashes upon drawing a text box.

[Rene Antonaccio]

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

Bug ID: 397247
   Summary: Krita crashes upon drawing a text box.
   Product: krita
   Version: 4.1.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Tool/Text
  Assignee: krita-bugs-n...@kde.org
  Reporter: rene.antonac...@grr.la
  Target Milestone: ---

As described above. Krita installation used is 4.1.1 stable available through
Flatpak. OS is a debian-based Subgraph OS. This is the log emitted at the
event:

```
Aug 07 14:30:10 subgraph org.kde.krita.desktop[9337]:
QMetaObject::indexOfSignal: signal selectionChanged() from
KoSelectedShapesProxy redefined in KisSelectedShapesProxy
Aug 07 14:30:10 subgraph org.kde.krita.desktop[9337]:
QMetaObject::indexOfSignal: signal selectionChanged() from
KoSelectedShapesProxy redefined in KisSelectedShapesProxy
Aug 07 14:30:16 subgraph org.kde.krita.desktop[9337]: convertFromSvg. text:
"Lorem ipsum dolor sit amet, consectetur adipiscing elit." styles:
"\n \n  text {\n   font-family:'Noto Sans';\n   font-size:72 ;  
text-anchor:start;\n  }\n\n" bounds: QRectF(201.265,341.849
1220.37x469.599) ppi: 72
Aug 07 14:30:16 subgraph org.kde.krita.desktop[9337]:
QMetaObject::indexOfSignal: signal selectionChanged() from
KoSelectedShapesProxy redefined in KisSelectedShapesProxy
Aug 07 14:30:16 subgraph org.kde.krita.desktop[9337]:
QMetaObject::indexOfSignal: signal selectionContentChanged() from
KoSelectedShapesProxy redefined in KisSelectedShapesProxy
Aug 07 14:30:16 subgraph org.kde.krita.desktop[9337]: ASSERT failure in
QVector::operator[]: "index out of range", file
../../include/QtCore/../../src/corelib/tools/qvector.h, line 432
```

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

[Discover] [Bug 397246] New: Crash of discover

[Ivan]

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

Bug ID: 397246
   Summary: Crash of discover
   Product: Discover
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: ivan9...@protonmail.com
  Target Milestone: ---

Application: plasma-discover (5.13.4)

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

-- Information about the crash:
- What I was doing when the application crashed:
I was typing the name of the program in the search engine, and it closed
suddenly. I only had the firefox and dolphin browser

The crash can be reproduced sometimes.

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

Thread 7 (Thread 0x7f146fdf3700 (LWP 10881)):
#0  0x7f14ac21f407 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f14ac221cea in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f14ac222330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f14ac22249c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f14b22030bb in QEventDispatcherGlib::processEvents
(this=0x7f14680008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7f14b21aa5ba in QEventLoop::exec (this=this@entry=0x7f146fdf2cf0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:214
#6  0x7f14b1fdf5e4 in QThread::exec (this=) at
thread/qthread.cpp:525
#7  0x7f14b1fea727 in QThreadPrivate::start (arg=0x16e7460) at
thread/qthread_unix.cpp:367
#8  0x7f14ae0876ba in start_thread (arg=0x7f146fdf3700) at
pthread_create.c:333
#9  0x7f14b15ee41d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7f147da15700 (LWP 10877)):
#0  0x7f14ac266a94 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f14ac3d in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f14ac22249c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f14b22030bb in QEventDispatcherGlib::processEvents
(this=0x7f1478c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f14b21aa5ba in QEventLoop::exec (this=this@entry=0x7f147da14cf0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:214
#5  0x7f14b1fdf5e4 in QThread::exec (this=) at
thread/qthread.cpp:525
#6  0x7f14b1fea727 in QThreadPrivate::start (arg=0x2b98e80) at
thread/qthread_unix.cpp:367
#7  0x7f14ae0876ba in start_thread (arg=0x7f147da15700) at
pthread_create.c:333
#8  0x7f14b15ee41d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7f147f810700 (LWP 10874)):
#0  0x7f14ac266a94 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f14ac221bf9 in g_main_context_query () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f14ac222307 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f14ac22249c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f14b22030bb in QEventDispatcherGlib::processEvents
(this=0x7f14780008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7f14b21aa5ba in QEventLoop::exec (this=this@entry=0x7f147f80fcf0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:214
#6  0x7f14b1fdf5e4 in QThread::exec (this=) at
thread/qthread.cpp:525
#7  0x7f14b1fea727 in QThreadPrivate::start (arg=0x1a3fad0) at
thread/qthread_unix.cpp:367
#8  0x7f14ae0876ba in start_thread (arg=0x7f147f810700) at
pthread_create.c:333
#9  0x7f14b15ee41d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7f148948b700 (LWP 10873)):
#0  0x7f14ac266a79 in g_mutex_lock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f14ac221929 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f14acbb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f14ac22249c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f14b22030bb in QEventDispatcherGlib::processEvents
(this=0x7f14840008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7f14b21aa5ba in QEventLoop::exec (this=this@entry=0x7f148948ac80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:214
#6  0x7f14b1fdf5e4 in QThread::exec (this=) at
thread/qthread.cpp:525
#7  0x7f14b542cf86 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#8  0x7f14b1fea727 in QThreadPrivate::start (arg=0x19a43f0) at
thread/qthread_unix.cpp:367
#9  0x7f14ae0876ba in start_thread (arg=0x

[kscreenlocker] [Bug 347772] kscreenlocker_greet using 100% cpu on plasma 5

[Martin Flöser]

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

--- Comment #26 from Martin Flöser  ---
(In reply to Gianni from comment #25)
> Created attachment 114342 [details]
> qdbus org.kde.KWin /KWin supportInformation macmini mid 2007

You are using xrender compositing. This could indicate that your OpenGL drivers
are broken. That would explain the high cpu usage.

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

[systemsettings] [Bug 254560] Associate application as the default for all of its known compatible mimetypes

[Øystein Steffensen-Alværvik]

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

--- Comment #3 from Øystein Steffensen-Alværvik  ---
*** Bug 396930 has been marked as a duplicate of this bug. ***

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

[systemsettings] [Bug 396930] Option to lock the order of preferred applications for all mimetypes

[Øystein Steffensen-Alværvik]

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

Øystein Steffensen-Alværvik  changed:

   What|Removed |Added

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

--- Comment #5 from Øystein Steffensen-Alværvik  ---
So after some thought, this is more or less the same as WISH 254560.

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

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

[valgrind] [Bug 385409] s390x: z13 vector integer instructions not implemented

[Vadim Barkov]

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

--- Comment #43 from Vadim Barkov  ---
Generally speaking I think that warning in inline strlen is correct because the
VFENE specification says:

If ZS (zero search) flag is set, then each element in the second operand is
compared for equality with zero.

So, if we have this instruction:

vfenezbs %v0, %v0, %v0

then all bytes of %v0 (second operand) are read in all cases (if the needed
element found or not)

So, if some bytes of %v0 are uninitialized for some reason, then the resulting
condition code of VFENEZBS instruction is undefined.

Anyway, the  VFENE implementation is rewritten because in general case (when
the second and third operand are different) the third operand is not read
fully.

What do you think about it?

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

[valgrind] [Bug 385409] s390x: z13 vector integer instructions not implemented

[Vadim Barkov]

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

--- Comment #42 from Vadim Barkov  ---
Good news! I've solved the strlen inlining issue.

The old VFENE implementation used the dirty helper, which marked second and
third argument fully read (16 bytes). This is semantically wrong because this
instruction reads its arguments byte by byte until needed element will be found
(or all bytes are read).

The new implementation is correct from this perspective.

Now I am going to review other string instructions to this bug and fix them
too.

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

[valgrind] [Bug 385409] s390x: z13 vector integer instructions not implemented

[Vadim Barkov]

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

Vadim Barkov  changed:

   What|Removed |Added

 Attachment #114334|0   |1
is obsolete||

--- Comment #41 from Vadim Barkov  ---
Created attachment 114361
  --> https://bugs.kde.org/attachment.cgi?id=114361&action=edit
New VFENE Implementation

Fixed the strlen issue via new VFENE implementation

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

[ksysguard] [Bug 152608] Tray and taskbar icon should show cpu usage

[Gregor Mi]

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

--- Comment #8 from Gregor Mi  ---
Created attachment 114360
  --> https://bugs.kde.org/attachment.cgi?id=114360&action=edit
Example of system tray where 3 icons are enabled

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

[ksysguard] [Bug 152608] Tray and taskbar icon should show cpu usage

[Gregor Mi]

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

--- Comment #7 from Gregor Mi  ---
Created attachment 114359
  --> https://bugs.kde.org/attachment.cgi?id=114359&action=edit
Menu in main application to select which tray icons should be shown

I have attached an example of how this is done in Process Hacker (Free software
process monitor and debugging tool for Windows:
https://processhacker.sourceforge.io/):

1) "Menu in main application to select which tray icons should be shown"

2) "Example of system tray where 3 icons are enabled". The tray icons have
black background by default an show a log graph of recent activity (e.g. CPU
usage, Disk IO, network activity)

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

[plasmashell] [Bug 396441] Icons turn into black figures

[David]

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

--- Comment #4 from David  ---
(In reply to David from comment #2)
> (In reply to Roman Gilg from comment #1)
> > Happens on Wayland as well?
> > 
> > What icons all? For example in task manager, launcher/menu, desktop?
> 
> No idea if it happens on wayland, and don't have the necessary setup to try
> it either, sorry. Happens with all icons in the task manager and system
> tray. Not sure about desktop ones as I haven't really checked, but will try
> to provide more info when it happens again.

Had the bug happen again now and it seems that the icons are replaced with
slices of some terminal window. This time, I had a konsole window open with
colored text on it, and the icons seem to each take a bit of it.

It affects: taskbar icons, system tray, panel widgets.
The icons in the application launcher are all black instead of having pieces of
the konsole window like the others.
After a while, it also affects desktop icon and desktop widgets - for example,
the notes widgets has a piece of the konsole terminal in the background with
the text that I wrote as notes over it.

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

[kmymoney] [Bug 396831] 5.0 Version - Crashes when importing OFX/QFX File Using Firefox

[bugzilla_noreply]

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

--- Comment #5 from bren...@coupeware.com ---
Yes I am running the master from a couple of days ago.

This is the same system that does not recognize encrypted files.

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

[plasmashell] [Bug 396441] Icons turn into black figures

[David]

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

--- Comment #3 from David  ---
Created attachment 114358
  --> https://bugs.kde.org/attachment.cgi?id=114358&action=edit
bug in action

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

[kmymoney] [Bug 397245] New: Cannot set date format properly in KMyMoney 5

[bugzilla_noreply]

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

Bug ID: 397245
   Summary: Cannot set date format properly in KMyMoney 5
   Product: kmymoney
   Version: 5.0.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kmymoney-de...@kde.org
  Reporter: schoenes-...@web.de
  Target Milestone: ---

Created attachment 114357
  --> https://bugs.kde.org/attachment.cgi?id=114357&action=edit
Output from System Profiler

Running Lubuntu 18.04.1 LTS .  My preferred system language is US English, my
preferred date format is -MM-DD.  Closest locale combination thereof is
en_DK which I have set in Language Support (as can be seen from the System
Profiler output attached).

Before I changed the Regional Formats from German to English (Denmark),
KMyMoney showed a date format of dd.mm.yy which I did not like.  After having
changed it to the current setting, both PCManFM and Thunar file managers show
the desired date format of -mm-dd .  However, KMyMoney has decided to show
dd/mm/ which is better than before but still not the desired format.

Please advise.

- nothing follows-

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

[kdenlive] [Bug 397244] New: [Flatpak] Kdenlive wont start on propietary Nvidia drivers

[Neousr]

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

Bug ID: 397244
   Summary: [Flatpak] Kdenlive wont start on propietary Nvidia
drivers
   Product: kdenlive
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Installation
  Assignee: vpi...@kde.org
  Reporter: neo...@protonmail.com
  Target Milestone: ---

Neon User Edition 5.13.4

Nvidia 390.77

Steps to Reproduce:

1. Install Kdenlive from discover using the flathub source.
2. Launch the program.

Launching the Kdenlive flatpak on terminal will output:

libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
Could not initialize GLX

The program will not load. On Open source drivers it works with out problems.

To make the flatpak open "flatpak update" needs to be run on a terminal so it
will download and install the packaged drivers on flathub. After that the
program will launch.

Just reporting after trying another flatpaked KDE software that rely on Opengl
and wont launch. No further testing was made than opening and closing the
program.

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

[Discover] [Bug 397243] New: Discover 5.13.4 freezes permanently when launched after a recent crash

[Øystein Steffensen-Alværvik]

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

Bug ID: 397243
   Summary: Discover 5.13.4 freezes permanently when launched
after a recent crash
   Product: Discover
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: yst...@posteo.net
  Target Milestone: ---

Discover on my computer is in a seemingly unrecoverable state of freeze/hang
after being launched; i.e. every time I launch Discover it freezes. Rebooting
doesn't help. 
This started to happen after Discover crashed while I was configuring a Snap.
After choosing 'Relaunch application', Discover would freeze. A re-login fixed
this once, but after reproducing the crash a second time the freeze is always
there.


Backtrace of the freeze:

GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word".
(gdb) handle SIG33 pass nostop noprint
SignalStop  Print   Pass to program Description
SIG33 NoNo  Yes Real-time event 33
(gdb) set pagination 0
(gdb) attach 11718
Attaching to process 11718
[New LWP 11719]
[New LWP 11720]
[New LWP 11721]
[New LWP 11722]
[New LWP 11723]
[New LWP 11724]
[New LWP 11725]
[New LWP 11731]
[New LWP 11733]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7fb894ff22dd in write () at ../sysdeps/unix/syscall-template.S:84
84  ../sysdeps/unix/syscall-template.S: No such file or directory.
(gdb) bact[Kktrace full
#0  0x7fb894ff22dd in write () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fb894f73bff in _IO_new_file_write (f=0x7fb8952c0540
<_IO_2_1_stderr_>, data=0x4493fca0, n=112) at fileops.c:1263
count = 
to_do = 112
#2  0x7fb894f7438a in _IO_new_file_xsputn (to_do=112, data=0x4493fca0
"\n(process:11718): GLib-CRITICAL **: g_byte_array_remove_range: assertion
'index_ + length <= array->len' failed\n", fp=0x7fb8952c0540 <_IO_2_1_stderr_>)
at fileops.c:518
count = 
block_size = 
do_write = 112
s = 0x4493fca0 "\n(process:11718): GLib-CRITICAL **:
g_byte_array_remove_range: assertion 'index_ + length <= array->len' failed\n"
to_do = 112
must_flush = 
count = 
n = 112
data = 
f = 0x7fb8952c0540 <_IO_2_1_stderr_>
s = 
to_do = 112
#3  0x7fb894f7438a in _IO_new_file_xsputn (f=0x7fb8952c0540
<_IO_2_1_stderr_>, data=, n=112) at fileops.c:1342
block_size = 
do_write = 112
s = 0x4493fca0 "\n(process:11718): GLib-CRITICAL **:
g_byte_array_remove_range: assertion 'index_ + length <= array->len' failed\n"
to_do = 112
must_flush = 
count = 
n = 112
data = 
f = 0x7fb8952c0540 <_IO_2_1_stderr_>
s = 
to_do = 112
#4  0x7fb894f690c8 in __GI__IO_fputs (str=str@entry=0x4493fca0
"\n(process:11718): GLib-CRITICAL **: g_byte_array_remove_range: assertion
'index_ + length <= array->len' failed\n", fp=fp@entry=0x7fb8952c0540
<_IO_2_1_stderr_>) at iofputs.c:38
_IO_acquire_lock_file = 0x7fb8952c0540 <_IO_2_1_stderr_>
len = 112
result = -1
#5  0x7fb88fc3c41f in g_log_default_handler (string=0x4493fca0
"\n(process:11718): GLib-CRITICAL **: g_byte_array_remove_range: assertion
'index_ + length <= array->len' failed\n", stream=0x7fb8952c0540
<_IO_2_1_stderr_>) at
/build/glib2.0-b4FPyK/glib2.0-2.48.2/./glib/gmessages.c:367
level_prefix = "CRITICAL
**\000\270\177\000\000\060\361\367\224\270\177\000\000\360\364\367\224\270\177\000\000
\301\261\222\377\177\000\000`\301\261\222\377\177\000\000\000\000\000\000\000\000\000\000`\301",

string = 0x4493fca0 "\n(process:11718): GLib-CRITICAL **:
g_byte_array_remove_range: assertion 'index_ + length <= array->len' failed\n"
gstring = 0x74fcae0
stream = 0x7fb8952c0540 <_IO_2_1_stderr_>
domains = 
#6  0x7fb88fc3c41f in g_log_default_handler
(log_domain=log_domain@entry=0x7fb88fc7d7ee "GLib",
log_level=log_level@entry=G_LOG_LEVEL_CRITICAL,
message=message@entry=0x4492dc00 "g_byte_array_remove_range: assertion 'i

[Discover] [Bug 397192] Discover crashes on close when I use "Manage " feature with an app from AUR

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/dis
   ||cover/2155003d054e75d173307
   ||360c81fea41890b590f
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Aleix Pol  ---
Git commit 2155003d054e75d173307360c81fea41890b590f by Aleix Pol.
Committed on 07/08/2018 at 16:02.
Pushed by apol into branch 'Plasma/5.12'.

PK: wait until we have fetched the packages that dont' come from appstream

M  +3-3discover/DiscoverObject.cpp
M  +2-2libdiscover/backends/PackageKitBackend/PackageKitBackend.cpp

https://commits.kde.org/discover/2155003d054e75d173307360c81fea41890b590f

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

[kio] [Bug 266141] KTar class have broken UTF-8 support for multibyte characters (longlink)

[Ibragimov Rinat]

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

--- Comment #3 from Ibragimov Rinat  ---
(In reply to Julian Schraner from comment #1)

I've tested it against version of karchive from git repository, and still found
the issue reproducible. In the process, I've added
https://phabricator.kde.org/D14674 with the patch. Could you take a look?

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

[krita] [Bug 397231] Unable to move/close certain dockers

[bugzilla_noreply]

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

buffaloba...@earthlink.net changed:

   What|Removed |Added

 CC||buffaloba...@earthlink.net

--- Comment #2 from buffaloba...@earthlink.net ---
Oh, well that was simple. I still can't move them around though, there isn't
even a place that I can grab on to them.

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

[kmymoney] [Bug 397024] Wrong date choice when a schedule transaction is recognised

[antoine]

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

--- Comment #8 from antoine  ---
Hi, 

Yes, with the sample file, the "Supprimer la mise correspondance" (Unmatch)
button also does not appear on my computer.

When I click the "Correspond" (Match) button, transaction are unmatched...

What is funny is that the "Correspond" button tooltip is "Supprimer la mise en
correspondance"

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

[krusader] [Bug 397133] Krusader in root-mode don't start

[Hanisch]

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

--- Comment #3 from Hanisch  ---
The problem is solved with following Workaround:

sudo rm /usr/lib/i386-linux-gnu/libexec/kf5/kdesu
sudo ln -s /usr/bin/kdesudo /usr/lib/i386-linux-gnu/libexec/kf5/kdesu

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

[digikam] [Bug 382362] Locale database mismatch between Windows and Linux

[Eric Schultz]

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

Eric Schultz  changed:

   What|Removed |Added

 CC||schultz...@gmail.com

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

[kate] [Bug 385520] Kate's tabs don't respect the theme and look like they came from Adwaita

[bugzilla_noreply]

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

adr.fant...@gmail.com changed:

   What|Removed |Added

 CC||adr.fant...@gmail.com

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

[Touchpad-KCM] [Bug 395722] touchpad settings are wrong after resuming from suspend

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

   Priority|HI  |VHI

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

[frameworks-baloo] [Bug 397242] New: Baloo gets confused when a file is renamed over existing one

[Alexander Meshcheryakov]

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

Bug ID: 397242
   Summary: Baloo gets confused when a file is renamed over
existing one
   Product: frameworks-baloo
   Version: 5.48.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: Baloo File Daemon
  Assignee: baloo-bugs-n...@kde.org
  Reporter: alexander@gmail.com
  Target Milestone: ---

Here is an example script to reproduce (has to be runned inside baloo indexed
directory):

```
NAME=$(pwgen -N1); CONTENT=$(pwgen -N1)
echo "$CONTENT" > "${NAME}"_1.txt
echo "$CONTENT" > "${NAME}"_2.txt
sleep 5
baloosearch "${CONTENT}"
echo
mv -v "${NAME}"_1.txt "${NAME}"_2.txt
sleep 5
baloosearch "${CONTENT}"
```

The first baloosearch as expected finds files "${NAME}"_1.txt and
"${NAME}"_2.txt

But the second invocation (after "${NAME}"_1.txt is renamed to "${NAME}"_2.txt)
finds "${NAME}"_2.txt twice!!!


I believe this is the reason why a get tons of duplicates of zim notes in
search results. Zim desktop wiki for robustness saves its notes in file
$NOTE.txt.zim-new~ and then moves this file over $NOTE.txt.

Also this obviously leads to unreasonably large index file etc etc

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

[krusader] [Bug 397133] Krusader in root-mode don't start

[Hanisch]

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

--- Comment #2 from Hanisch  ---
The problem is identical with Krusader 2.6.0 and 2.7.0

VM-linuxmint:~$ /usr/lib/i386-linux-gnu/libexec/kf5/kdesu krusader
kdesud daemon not found.
org.kde.kdesu: Daemon not safe (not sgid), not using it.

What mean 'kdesud daemon'?

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

[kstars] [Bug 397227] PHD2 stopped guiding not recognized

[Wolfgang Reissenberger]

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

--- Comment #2 from Wolfgang Reissenberger  ---
Tested it on commit 9c7bebf8421ce49194ebed7ecdaa426ac143032d. Looks good!

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

[plasmashell] [Bug 397240] Ability to close/remove non-visible system widget

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org

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

[plasmashell] [Bug 397235] Ability to close/remove all instances of system widget using the Widget Explorer

[bugzilla_noreply]

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

boaz.do...@gmail.com changed:

   What|Removed |Added

Summary|Ability to close/remove all |Ability to close/remove all
   |instances of system widget  |instances of system widget
   |from Widget Explorer|using the Widget Explorer

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

[plasmashell] [Bug 397235] Ability to close/remove all instances of system widget from Widget Explorer

[Christoph Feck]

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

--- Comment #15 from Christoph Feck  ---
Please change the title to not read "remove from Widget explorer", because
everyone will be confused. Additionally, just replying "yes" to comment #1
would have helped to understand what you want to do.

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

[kmymoney] [Bug 397241] Cannot write .kmy file from Lubuntu 18.04.1 LTS to Windows 10-based network share

[bugzilla_noreply]

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

schoenes-...@web.de changed:

   What|Removed |Added

 CC|schoenes-...@web.de |

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

[kmymoney] [Bug 397241] Cannot write .kmy file from Lubuntu 18.04.1 LTS to Windows 10-based network share

[bugzilla_noreply]

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

schoenes-...@web.de changed:

   What|Removed |Added

 CC||schoenes-...@web.de

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

[kmymoney] [Bug 397241] New: Cannot write .kmy file from Lubuntu 18.04.1 LTS to Windows 10-based network share

[bugzilla_noreply]

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

Bug ID: 397241
   Summary: Cannot write .kmy file from Lubuntu 18.04.1 LTS to
Windows 10-based network share
   Product: kmymoney
   Version: 5.0.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: kmymoney-de...@kde.org
  Reporter: schoenes-...@web.de
  Target Milestone: ---

Created attachment 114356
  --> https://bugs.kde.org/attachment.cgi?id=114356&action=edit
Screenshots

Just updated LUBUNTU from 17.10 to 18.04.1 LTS .  Much to my surprise, KMYMONEY
(language set to German, reports version 5.0.0 in Help|About although starting
splash shows a big "4" in the right-hand side area) opens my .kmy file from the
previous version without problem on my Windows share named
smb://dg-server/norbert/Programme/KMyMoney/norbert.kmy, shows all entries,
etc., but trying to save the modified file, an error is given as follows:

FEHLER - kmymoney
Änderungen können nicht in
„/run/user/1000/gvfs/smb-share:server=dg-server,share=norbert/Programme/KMyMoney/norbert.kmy“
geschrieben werden

The critical part of that is - exiting KMyMoney WITHOUT saving leaves an EMPTY
.kmy file with all entries gone!

Writing the .kmy file to the local file system works fine.

Note that other programs (e.g., LibreOffice 6.0) read from and write to that
same very share without any issues.

- nothing follows -

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

[plasmashell] [Bug 397240] Ability to close/remove non-visible system widget

[bugzilla_noreply]

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

boaz.do...@gmail.com changed:

   What|Removed |Added

Summary|Ability to remove   |Ability to close/remove
   |non-visible system widget   |non-visible system widget

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

[plasmashell] [Bug 397235] Ability to close/remove all instances of system widget from Widget Explorer

[bugzilla_noreply]

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

boaz.do...@gmail.com changed:

   What|Removed |Added

Summary|Ability to remove widget|Ability to close/remove all
   |from Widget Explorer|instances of system widget
   ||from Widget Explorer

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

[plasmashell] [Bug 397235] Ability to remove widget from Widget Explorer

[bugzilla_noreply]

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

--- Comment #14 from boaz.do...@gmail.com ---
I am sorry if the image confusing.

Nate, thanks for your detailed replies.

I am looking for a way to close/remove all instances of a widget.

How about to show "Close/remove all instances" icon instead of "Uninstall
widget", for system widgets that can't be uninstalled?

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

[plasmashell] [Bug 397235] Ability to remove widget from Widget Explorer

[Nate Graham]

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

--- Comment #13 from Nate Graham  ---
The image you linked to shows uninstallation.

Removing all open instances of a widget not not the same as uninstallation.
Think of it like programs: if a program is open, you can CLOSE it to make it
stop running, but leave it available on your computer. If you UNINSTALL the
program, it will be removed from the computer entirely and you will not be able
to open it again.

If you just want to close/remove all instances of a widget, you don't need to
uninstall it.

Are you looking for a way to close/remove all instances of a widget? Or are you
trying to uninstall widgets such that they are no longer available on your
computer?

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

[plasmashell] [Bug 397240] Ability to remove non-visible system widget

[bugzilla_noreply]

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

--- Comment #1 from boaz.do...@gmail.com ---
Just to clarify - I am talking about been able to remove visible and invisible
instances of the widget from my desktop (not deleting packages, etc.).

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

[Discover] [Bug 397037] Software Updates icon on the system tray doesn't change when I change the desktop theme

[Kai Uwe Broulik]

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

--- Comment #8 from Kai Uwe Broulik  ---
The icon is only in Breeze icons (and Oxygen) but not in the Plasma theme,
maybe this causes it not to update.

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

[plasmashell] [Bug 397235] Ability to remove widget from Widget Explorer

[bugzilla_noreply]

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

--- Comment #12 from boaz.do...@gmail.com ---
(In reply to Nate Graham from comment #11)
> Boaz, are you using the word "uninstall" to mean "remove visible and
> invisible instances of the widget from my desktop?" I think you may be
> confusing the developers, because everyone thinks you're asking for an
> ability to delete widgets that are shipped with Plasma off of your whole
> computer, which is not possible.
> 
> Can you clarify what it is you want to do?

Nate, I think it's clear from my several comments and the linked image, that I
am talking about "remove visible and invisible instances of the widget from my
desktop".

Reopening this bug will be appreciated.

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

[konsole] [Bug 359810] Konsole doesn't start with nVidia powermizer set to run slow

[bugzilla_noreply]

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

--- Comment #2 from mgol...@mitchgolden.com ---
I have not seen this for a while.

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

[plasmashell] [Bug 397235] Ability to remove widget from Widget Explorer

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org

--- Comment #11 from Nate Graham  ---
Boaz, are you using the word "uninstall" to mean "remove visible and invisible
instances of the widget from my desktop?" I think you may be confusing the
developers, because everyone thinks you're asking for an ability to delete
widgets that are shipped with Plasma off of your whole computer, which is not
possible.

Can you clarify what it is you want to do?

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

[Discover] [Bug 397037] Software Updates icon on the system tray doesn't change when I change the desktop theme

[Aleix Pol]

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

--- Comment #7 from Aleix Pol  ---
It's: update-* (update-none, update-high, etc).

So it's just not supposed to change?

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

[Discover] [Bug 396968] Discover sometimes silently fails to download package

[Aleix Pol]

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

--- Comment #1 from Aleix Pol  ---
Do you know which backend that was? (source? which is your default source?)

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

[systemsettings] [Bug 393061] Focus not transferred properly to child windows in sidebar view

[Ivo C]

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

--- Comment #3 from Ivo C  ---
Created attachment 114355
  --> https://bugs.kde.org/attachment.cgi?id=114355&action=edit
video demonstration

Unfortunately, I am unable to test with the master branch, but my system has
since been updated to newer versions and it still occurs at random very often
but not always. I don't use any kind of special focus prevention rules: the
policy is "click to focus", low stealing prevention and click raises active
window is enabled.

I have added an attachment video to demonstrate this odd issue if it wasn't
clear what is happening on my end. Here, it doesn't happen the first time, but
does the second and I try to show the effects. When I click on the child
window, it starts behaving normally.

Plasma: 5.13.3
KDE frameworks: 5.48.0
Qt: 5.10.1

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

[systemsettings] [Bug 397220] Thumbnails/previews in systemsettings gone

[Kai Uwe Broulik]

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

--- Comment #2 from Kai Uwe Broulik  ---
Git commit 94c6f3152188d15e84019c4aafcc7835b7f42b12 by Kai Uwe Broulik.
Committed on 07/08/2018 at 13:03.
Pushed by broulik into branch 'master'.

[KCM GridDelegate] Use layer effect only on OpenGL backend

QtGraphicalEffects only works then, otherwise we render no thumbnail whatsoever

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

M  +2-2src/qmlcontrols/kcmcontrols/qml/GridDelegate.qml

https://commits.kde.org/kdeclarative/94c6f3152188d15e84019c4aafcc7835b7f42b12

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

[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.

[Castro B]

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

Castro B  changed:

   What|Removed |Added

 CC||castro8583benn...@gmx.com

--- Comment #280 from Castro B  ---
(In reply to wraithmonk from comment #279)
> (In reply to undecidable from comment #277)
> > A sad day.
> > After using Kubuntu / KDE since 2007 (11 years),
> > and being an annual contributor to both the KDE and Kubuntu projects,
> >  at 18.04 I have moved to Xubuntu.
> >  
> >  One reason  alone:  different wallpaper per virtual desktop.
> >  I spend ~14 hours a day at my desktop 
> > and my desktop environment (see comment 192) is a fundamental part of my
> > intellectual day.
> >   
> >   I do definitely miss the beauty and power of KDE
> >   and the transition has really been a pain
> >   (though I took some kde tools - okular, kate, clementine, gwenview, kdiff3
> > etc with me).
> >   
> >  But I don't miss being forced to work the way someone else wants me to 
> > work.
> 
> Nor do I. I've switched to using Trinity DE. TDE is a fork of KDE 3.5 & you
> can
> have different wallpapers on different desktops, as well as having the usual
> KDE tools & sounds etc. TDE is available for Debian, Ubuntu, Fedora, etc.

Does this also available to windows or higher version of windows? Thanks

Carlo B.
https://amsterdamdiary.com/

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

[plasmashell] [Bug 397235] Ability to remove widget from Widget Explorer

[bugzilla_noreply]

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

boaz.do...@gmail.com changed:

   What|Removed |Added

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

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

[plasmashell] [Bug 397240] Ability to remove non-visible system widget

[bugzilla_noreply]

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

boaz.do...@gmail.com changed:

   What|Removed |Added

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

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

[plasmashell] [Bug 397240] New: Ability to remove non-visible system widget

[bugzilla_noreply]

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

Bug ID: 397240
   Summary: Ability to remove non-visible system widget
   Product: plasmashell
   Version: 5.12.6
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: boaz.do...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

If for any reason, a widget non-visible on the desktop [1], it looks like there
is no way to uninstall (installed/added via Widget Explorer or Add Panel
option) system widget (like Digital Clock), beside removing system packages
(with depends on pretty much half of KDE/Plasma) or editing system files.

Kubuntu 18.04.1 64bit
KDE Plasma 5.12.6

[1]: A real example of this situation
https://www.kubuntuforums.net/showthread.php/74165-Default-panel-disappeared

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

[Akonadi] [Bug 397239] New: crash when searching with kmail

[Martin Koller]

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

Bug ID: 397239
   Summary: crash when searching with kmail
   Product: Akonadi
   Version: GIT (master)
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: server
  Assignee: kdepim-b...@kde.org
  Reporter: kol...@aon.at
  Target Milestone: ---

Application: akonadiserver (5.8.90)

Qt Version: 5.11.1
Frameworks Version: 5.48.0
Operating System: Linux 4.4.138-59-default x86_64
Distribution: "openSUSE Leap 42.3"

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

I opened the "find messages" dialog from kmail, selected "Search in all
folders", "Match all of the following" (default), "Complete Message" and
entered my search string and hit "Search", then I got the crash report
assistant tellig me akonadi crashed and kmail opens a dialog showing
"Cannot get search result. Cannot connect to the Akonadi service."

-- Backtrace:
Application: Akonadi Server (akonadiserver), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f048a6c8900 (LWP 25381))]

Thread 33 (Thread 0x7f0451ffb700 (LWP 2164)):
#0  0x7f0486e694a8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0


Thread 9 (Thread 0x7f04767fc700 (LWP 25461)):
[KCrash Handler]
#6  0x7f0487fe4f67 in raise () from /lib64/libc.so.6
#7  0x7f0487fe633a in abort () from /lib64/libc.so.6
#8  0x00643f8e in akMessageHandler (type=QtFatalMsg, context=...,
msg=...) at /home/KDE5/source/kde/pim/akonadi/src/shared/akdebug.cpp:177
#9  0x00646094 in (anonymous namespace)::RemoteLogger::dbusLogger
(type=QtFatalMsg, ctx=..., msg=...) at
/home/KDE5/source/kde/pim/akonadi/src/shared/akremotelog.cpp:178
#10 0x7f04759f4a24 in (anonymous namespace)::RemoteLogger::dbusLogger
(type=QtFatalMsg, ctx=..., msg=...) at
/home/KDE5/source/kde/pim/akonadi/src/shared/akremotelog.cpp:178
#11 0x7f0488c969bf in qt_message_print (message=..., context=...,
msgType=QtFatalMsg) at global/qlogging.cpp:1793
#12 qt_message(QtMsgType, const QMessageLogContext &, const char *, typedef
__va_list_tag __va_list_tag *) (msgType=msgType@entry=QtFatalMsg, context=...,
msg=msg@entry=0x7f0488f10788 "ASSERT: \"%s\" in file %s, line %d",
ap=ap@entry=0x7f04767fa318) at global/qlogging.cpp:365
#13 0x7f0488c7ff04 in QMessageLogger::fatal
(this=this@entry=0x7f04767fa3f0, msg=msg@entry=0x7f0488f10788 "ASSERT: \"%s\"
in file %s, line %d") at global/qlogging.cpp:877
#14 0x7f0488c7f576 in qt_assert (assertion=, file=, line=) at global/qglobal.cpp:3188
#15 0x0042da12 in Akonadi::Server::Connection::self () at
/home/KDE5/source/kde/pim/akonadi/src/server/connection.cpp:82
#16 0x005b086b in
Akonadi::Server::NotificationCollector::completeNotification
(this=0x7f04608d2af0, changeMsg=...) at
/home/KDE5/source/kde/pim/akonadi/src/server/storage/notificationcollector.cpp:545
#17 0x005b026f in
Akonadi::Server::NotificationCollector::dispatchNotification
(this=0x7f04608d2af0, msg=...) at
/home/KDE5/source/kde/pim/akonadi/src/server/storage/notificationcollector.cpp:580
#18 0x005acb1b in
Akonadi::Server::NotificationCollector::itemNotification (this=0x7f04608d2af0,
op=Akonadi::Protocol::ItemChangeNotification::Unlink, items=...,
collection=..., collectionDest=..., resource=..., parts=..., addedFlags=...,
removedFlags=..., addedTags=..., removedTags=..., addedRelations=...,
removedRelations=...) at
/home/KDE5/source/kde/pim/akonadi/src/server/storage/notificationcollector.cpp:373
#19 0x005ad719 in Akonadi::Server::NotificationCollector::itemsUnlinked
(this=0x7f04608d2af0, items=..., collection=...) at
/home/KDE5/source/kde/pim/akonadi/src/server/storage/notificationcollector.cpp:132
#20 0x004bda51 in Akonadi::Server::SearchManager::updateSearchImpl
(this=0x1fb8b80, collection=...) at
/home/KDE5/source/kde/pim/akonadi/src/server/search/searchmanager.cpp:374
#21 0x004bfb07 in
Akonadi::Server::SearchManager::updateSearch(Akonadi::Server::Collection
const&)::$_9::operator()() const (this=0x7f03f81740a0) at
/home/KDE5/source/kde/pim/akonadi/src/server/search/searchmanager.cpp:269
#22 0x004bfac9 in QtPrivate::FunctorCall,
QtPrivate::List<>, void,
Akonadi::Server::SearchManager::updateSearch(Akonadi::Server::Collection
const&)::$_9>::call(Akonadi::Server::SearchManager::updateSearch(Akonadi::Server::Collection
const&)::$_9&, void**) (f=..., arg=0x7f040f7fc530) at
/usr/include/qt5/QtCore/qobjectdefs_impl.h:128
#23 0x004bfaa1 in
QtPrivate::Functor::call,
void>(Akonadi::Server::SearchManager::updateSearch(Akonadi::Server::Collection
const&)::$_9&, void*, void**) (f=..., arg=0x7f040f7fc530) at
/usr/include/qt5/QtCore/qobjectdefs_impl.h:238
#24 0x004bf9dd in
QtPrivate::QFunctorSlotObject, void>::impl(int,
QtPrivate::QSlotObje

[frameworks-kimageformats] [Bug 397040] crash when save a QImage to the eps format file

[Friedrich W . H . Kossebau]

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

Friedrich W. H. Kossebau  changed:

   What|Removed |Added

 CC||kosse...@kde.org

--- Comment #5 from Friedrich W. H. Kossebau  ---
(In reply to Pino Toscano from comment #4)
> (In reply to zccrs from comment #3)
> > Created attachment 114347 [details]
> > This is a stack list
> 
> This shows that the issue is not in the EPS handler, which is called for
> some reasons during the application destruction.

"Some reason" might be the interesting part here though. Seems that the
clipboard wants to rescue the current content the application has set on the
clipboard, instead of deleting it together with the process ending, and tries
to pass it to the X clipboard manager, which might be by design.

Now it just happens that from all the possible QImageIO plugins which can write
it picks the EPS one. Which would be a rather bad pick in general, but it seems
QInternalMimeData::hasFormatHelper() simply picks whatever is first in the
list.

And as the EPS plugin has not been written to be run at this destruction stage,
things are flawed.

Not sure if the result of QImageIOPlugin::capabilities() is cached, or queried
dynamically. But if queried dynamically, there should be a check here to deny
any abilities if there is no QCoreApplication, as of course doing so in the
actual read/write handlers would be too late.

At least by a quick look following the call chain from 
https://code.woboq.org/qt5/qtbase/src/gui/kernel/qdnd.cpp.html#293 to
https://code.woboq.org/qt5/qtbase/src/gui/image/qimagereaderwriterhelpers.cpp.html#119
hints the list of qimageio plugins is always dynamically queried here.

So while still curious why the EPS handler is picked here, being prepared for
this situation seems not a useless thing to do.

> The problem is the deepin stuff, including its usage of an internal part of
> Qt (the Qt5XcbQpa library). Try the test case of comment 2 without any
> deepin stuff installed.

Though most of the stacktrace looks fine, a call stack which would just happen
with normal QGuiApplication destruction as well, which only deletes the
platform integration plugin in the ~QGuiApplicationPrivate destructor.

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