[kio-extras] [Bug 394600] [KIO / sftp] copy to remote server with full disk fails silently

[Lukáš Karas]

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

--- Comment #3 from Lukáš Karas  ---
Ups. You are correct, i was using kioclient from KDE4 in console, sorry. I
mixed kioclient and scp commands in original post moreover...

Anyway, the same problem exists with kio 5:

cd /tmp/
mkdir ramdisk
sudo mount -t tmpfs - ramdisk -o size=1M
dd if=/dev/urandom of=bigfile bs=1M count=2

kioclient5 cp bigfile sftp://localhost/tmp/ramdisk

...
kf5.kio.core.copyjob: emit processedSize 1044480
kf5.kio.core.copyjob: d->state= 6
kf5.kio.core.copyjob: 0 files remaining
kf5.kio.core.copyjob: 
kf5.kio.core.copyjob: copyNextFile finished
kf5.kio.core.copyjob: KDirNotify'ing FilesAdded
QUrl("sftp://localhost/tmp/ramdisk;

echo $?
0

ls -alh ramdisk/* bigfile 
-rw-rw-r-- 1 karry karry 2.0M May 24 07:19 bigfile
-rw-rw-r-- 1 karry karry 1.0M May 24 07:23 ramdisk/bigfile.part

kioclient5 --version
kioclient 5.12.4

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

[plasmashell] [Bug 380311] No way to launch ssh-agent with interactivity under Wayland

[Roman Gilg]

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

Roman Gilg  changed:

   What|Removed |Added

 CC||subd...@gmail.com

--- Comment #3 from Roman Gilg  ---
What's your plan? To launch ssh-agent in Wayland on startup? What's your
solution now?

I'm looking into providing the same ssh-agent functionality in Wayland session
as in X. So I'm looking for info about it.

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

[okular] [Bug 394621] support strikethrough annotations

[Oliver Sander]

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

Oliver Sander  changed:

   What|Removed |Added

 CC||oliver.san...@tu-dresden.de

--- Comment #13 from Oliver Sander  ---
I justed tried, and I do indeed have the strikethrough option.

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

[calligrasheets] [Bug 394619] Help / handbook - does not exist. - calligrasheets

[Burkhard Lueck]

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

Burkhard Lueck  changed:

   What|Removed |Added

 CC||lu...@hube-lueck.de

--- Comment #1 from Burkhard Lueck  ---
using master build from sources and neon devedition unstable up to date with
Help -> Calligra Sheets Handbook KHelpcenter opens the Handbook properly.

You get your error message on docs.kde.org?

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

[digikam] [Bug 394590] Feature request: being able to filter on all metadatas fields

[bugzilla_noreply]

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

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

   What|Removed |Added

   Version Fixed In||6.0.0
 Resolution|INVALID |WORKSFORME
 CC||caulier.gil...@gmail.com

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

[Heaptrack] [Bug 394627] Unable to use with Mudlet

[Vadim Peretokin]

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

--- Comment #3 from Vadim Peretokin  ---
Mudlets backtrace is the following:

1   __lll_lock_wait  
lowlevellock.S   135 0x7fdd7848d10d 
2   __GI___pthread_mutex_lock
pthread_mutex_lock.c 78  0x7fdd78486023 
3   heaptrack_free 
   0x7fdd7bb02313 
4   free   
   0x7fdd7bb00e06 
5   debug_free(void *, const char *, int)  
   0x4e21b5   
6   operator delete(void *)
   0x4e225f   
7   QObject::~QObject()
   0x7fdd78be7858 
8   ?? 
   0x7fdd58267074 
9   QObjectPrivate::deleteChildren()   
   0x7fdd78bde19b 
10  QObject::~QObject()
   0x7fdd78be79cb 
11  ?? 
   0x7fdd58277e79 
12  ?? 
   0x7fdd5825714b 
13  QNetworkConfigurationManagerPrivate::updateConfigurations()
   0x7fdd7933143a 
14  QNetworkConfigurationManagerPrivate::initialize()  
   0x7fdd79331dae 
15  qNetworkConfigurationManagerPrivate()  
   0x7fdd7932bfdd 
16  QNetworkConfigurationManager::QNetworkConfigurationManager(QObject *)  
   0x7fdd7932c077 
17  QNetworkAccessManager::QNetworkAccessManager(QObject *)
   0x7fdd792ba096 
18  cTelnet::cTelnet(Host *)   
   0x582f6b   
19  Host::Host(int, QString const&, QString const&, QString const&, int)   
   0x69c520   
20  HostManager::addHost(QString, QString, QString, QString)   
   0x6ad33e   
...   


It looks like a deadlock.

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

[Heaptrack] [Bug 394627] Unable to use with Mudlet

[Vadim Peretokin]

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

--- Comment #2 from Vadim Peretokin  ---
Just running Mudlet is enough.

Heaptracks backtrace is not that interesting:

1  wait4 syscall-template.S 78  0x7fbfefa7d76a 
2  ??   0x560fe3ef58a0 
3  ??   0x560fe3ef709d 
4  ??   0x560fe3ef16d8 
5  ??   0x560fe3ef049e 
6  ??   0x560fe3ef049e 
7  ??   0x560fe3ef049e 
8  ??   0x560fe3ef766e 
9  ??   0x560fe3eee9de 
10 __libc_start_main libc-start.c   310 0x7fbfef9bab97 
11 ??   0x560fe3eeea4a

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

[Discover] [Bug 394642] New: Discovery crashes after initiating update

[Shahriyor]

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

Bug ID: 394642
   Summary: Discovery crashes after initiating update
   Product: Discover
   Version: 5.12.4
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: a.shahri...@gmail.com
  Target Milestone: ---

Application: plasma-discover (5.12.4)

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

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

I left my notebook on yesterday evening downloading FlightGear Flight Simulator
via Discover during the night. I came back at the morning discovering that
FlightGear wasn't downloaded, but 2 updates were available. I clicked on
updates tab and it crashed.

-- 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 0x7fa4d27def40 (LWP 5847))]

Thread 10 (Thread 0x7fa499942700 (LWP 5901)):
#0  0x7fa4cdec60b4 in __GI___libc_read (fd=30, buf=0x7fa499941b90,
nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27
#1  0x7fa4c87fd960 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fa4c87b8f27 in g_main_context_check () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fa4c87b93e0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fa4c87b954c in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fa4ce81890b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fa4ce7bd9ea in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fa4ce5dc22a in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fa4ce5e116d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7fa4ca6de6db in start_thread (arg=0x7fa499942700) at
pthread_create.c:463
#10 0x7fa4cded788f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 9 (Thread 0x7fa47da5d700 (LWP 5879)):
#0  0x7fa4cdec60b4 in __GI___libc_read (fd=62, buf=0x7fa47da5cb90,
nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27
#1  0x7fa4c87fd960 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fa4c87b8f27 in g_main_context_check () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fa4c87b93e0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fa4c87b954c in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fa4ce81890b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fa4ce7bd9ea in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fa4ce5dc22a in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fa4ce5e116d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7fa4ca6de6db in start_thread (arg=0x7fa47da5d700) at
pthread_create.c:463
#10 0x7fa4cded788f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 8 (Thread 0x7fa47e25e700 (LWP 5878)):
#0  0x7fa4c87fecf4 in g_mutex_unlock () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fa4c87b8988 in g_main_context_prepare () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fa4c87b936b in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fa4c87b954c in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fa4ce81890b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fa4ce7bd9ea in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fa4ce5dc22a in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fa4ce5e116d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fa4ca6de6db in start_thread (arg=0x7fa47e25e700) at
pthread_create.c:463
#9  0x7fa4cded788f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 7 (Thread 0x7fa48a2fc700 (LWP 5863)):
#0  syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1  0x7fa4adebb335 in ?? () from
/usr/lib/x86_64-linux-gnu/libGLX_nvidia.so.0
#2  0x7fa4adebafc3 in ?? () from
/usr/lib/x86_64-linux-gnu/libGLX_nvidia.so.0
#3  0x7fa4a735654c in ?? () from
/usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.390.48
#4  0x7fa4a724bced in ?? () from
/usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.390.48
#5  0x7fa4a7224dff in ?? () from
/usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.390.48
#6  0x7fa4a7224e33 in ?? () from

[basket] [Bug 394641] 1q2w3e4Rr

[jose manuel]

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

--- Comment #1 from jose manuel  ---
Comment on attachment 112842
  --> https://bugs.kde.org/attachment.cgi?id=112842
enviar informe de fallos

>
>  
>
>  
> uiAccess="false">
>  
>
>  
>  
>
>   version="6.0.0.0" processorArchitecture="x86" 
> publicKeyToken="6595b64144ccf1df" language="*">
>
>  
>

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

[kwin] [Bug 384091] Add a window placement mode that remembers prior window position

[Nate Graham]

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

--- Comment #11 from Nate Graham  ---
I couldn't get a blanket window rule to work. It worked for app windows, but
kept undesirably matching Plasma windows too, so I'd get Kicker and KRunner
appearing in the center of the screen. I struggled with it off and on for three
days before eventually giving up. Is this in fact possible?

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

[basket] [Bug 306820] Attempt to password-protect basket wipes data

[jose manuel]

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

jose manuel  changed:

   What|Removed |Added

 CC||jomabe...@gmail.com

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

[basket] [Bug 394641] New: 1q2w3e4Rr

[jose manuel]

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

Bug ID: 394641
   Summary: 1q2w3e4Rr
   Product: basket
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kel...@ieee.org
  Reporter: jomabe...@gmail.com
  Target Milestone: ---

Created attachment 112842
  --> https://bugs.kde.org/attachment.cgi?id=112842=edit
enviar informe de fallos

no me funciona el Manual de Blocs de notas Basqket

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

[elisa] [Bug 394259] Elisa has empty albums and artists folders

[Quiralta]

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

Quiralta  changed:

   What|Removed |Added

 CC||rjquira...@gmail.com

--- Comment #4 from Quiralta  ---
I notice this behavior happening without Elisa updating, thus I'm thinking
something in Plasma has changed that render Elisa album view empty?

Archlinux/Plasma here. same error reported in phabricator.

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

[elisa] [Bug 394259] Elisa has empty albums and artists folders

[Quiralta]

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

Quiralta  changed:

   What|Removed |Added

 CC||jaime.a.flo...@gmail.com

--- Comment #3 from Quiralta  ---
*** Bug 394427 has been marked as a duplicate of this bug. ***

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

[elisa] [Bug 394427] Albums seem to be empty

[Quiralta]

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

Quiralta  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||rjquira...@gmail.com
 Resolution|--- |DUPLICATE

--- Comment #1 from Quiralta  ---


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

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

[okular] [Bug 394621] support strikethrough annotations

[Kevin Burton]

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

--- Comment #12 from Kevin Burton  ---
Thx.. I'm going to post to the forum and see if other users have a similar
issue. I mean they literally don't show up on my machine so something here is
weird.

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

[kio-extras] [Bug 369520] FISH: directories are mistaken for files and vice-versa

[Emmett Culley]

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

--- Comment #2 from Emmett Culley  ---
After doing some more testing I found that this issue happens only on certain
servers. Connecting to any of the server on my LAN seems to work OK.

Also one remote server I've been using for a number of years works as expected.

One server I am having an issue is a CentOS VM in the cloud.  Could this be a
server ssh configuration issue, or possibly a firewall issue?  

I have no problem connectiny via ssh to that VM.

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

[kio-extras] [Bug 369520] FISH: directories are mistaken for files and vice-versa

[Emmett Culley]

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

Emmett Culley  changed:

   What|Removed |Added

 CC||lst_man...@webengineer.com

--- Comment #1 from Emmett Culley  ---
I have the same issue:

kio-extras-17.12.1-1.fc27.x86_64

In dolphin and konqueror if I enter on fish:://example.com/etc/fail2ban I can
see the fail2ban directory contents on example.com,  but if I click on action.d
I get a pop up that want to p=open the directory as a file.

Even adding /action.d to the contents of the location bar gets me a popup.

However, if I click on the expand carrot I can then see the contents of the
action.d directory, and can even open a file in there by clicking on a file
name.

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

[konsole] [Bug 394502] Mishandling of selecting of text

[Arfrever Frehtes Taifersar Arahesis]

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

Arfrever Frehtes Taifersar Arahesis  changed:

   What|Removed |Added

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

--- Comment #3 from Arfrever Frehtes Taifersar Arahesis 
 ---
Fixed most likely in commit f24aa818f97b6bebdcc4ce62c927994232b6f282.
https://cgit.kde.org/konsole.git/commit/?id=f24aa818f97b6bebdcc4ce62c927994232b6f282

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

[plasmashell] [Bug 394630] Plasma crash after qbittorrent exit or disable/enable widget

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

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

--- Comment #1 from David Edmundson  ---


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

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

[plasmashell] [Bug 383828] Crash in QV4::QObjectWrapper::getProperty

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

 CC||m...@abv.bg

--- Comment #47 from David Edmundson  ---
*** Bug 394630 has been marked as a duplicate of this bug. ***

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

[kwin] [Bug 377914] KWin prevents Application Launcher from opening when using focus stealing prevention

[Theo]

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

Theo  changed:

   What|Removed |Added

 Resolution|WONTFIX |---
 CC||alpha0...@yahoo.de
 Status|RESOLVED|REOPENED

--- Comment #32 from Theo  ---
This still isn't fixed in KWin 5.12.5 and it needs to be fixed. Call me an
idiot user, but I had this problem for months before I realized what caused the
problem, had my bug report finally ready to submit when I spotted this bug
under "Possible Duplicates". No amount of mental gymnastics ("technically" this
is not a bug) can justify leaving the user with this broken behavior as it is,
which is not even consistent: the activity management widget is not suppressed
by stealing prevention High, and once it is open, I can also open the
Application Menu and Weather Widget. A simple warning in the setting dialog
would actually be good enough for a fix. I have lost all hope for a well
working focus stealing prevention anyway.

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

[okular] [Bug 377688] No output to print for PDF since update to 1.0.3

[Ian Newton]

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

--- Comment #21 from Ian Newton  ---
Resolved the avahi-daemon failure as in
https://bugzilla.redhat.com/show_bug.cgi?id=1050201

"I had some stale files in /var/run/avahi-daemon, cleaning those out seems to
have fixed it"

However the Journal output to display print preview is now:

May 24 00:59:34 sabayonx86-64 okular[24434]: Settings::instance called after
the first use - ignoring
May 24 00:59:34 sabayonx86-64 okular[24434]: org.kde.okular.generators.spectre:
Generated image does not match wanted size: [0x0] vs requested [576x815]
May 24 00:59:34 sabayonx86-64 okular[24434]: QImage::scaled: Image is a null
image
May 24 00:59:35 sabayonx86-64 okular[24434]: org.kde.okular.generators.spectre:
Generated image does not match wanted size: [0x0] vs requested [565x799]
May 24 00:59:35 sabayonx86-64 okular[24434]: QImage::scaled: Image is a null
image
May 24 00:59:35 sabayonx86-64 okular[24434]: org.kde.okular.generators.spectre:
Generated image does not match wanted size: [0x0] vs requested [565x799]
May 24 00:59:35 sabayonx86-64 okular[24434]: QImage::scaled: Image is a null
image
May 24 00:59:35 sabayonx86-64 okular[24434]: org.kde.okular.generators.spectre:
Generated image does not match wanted size: [0x0] vs requested [80x113]
May 24 00:59:35 sabayonx86-64 okular[24434]: QImage::scaled: Image is a null
image

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

[kde] [Bug 394640] New: No real crash but error generated when closing window

[Manuel Malagon]

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

Bug ID: 394640
   Summary: No real crash but error generated when closing window
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: 3ld3rm4l4...@gmail.com
  Target Milestone: ---

Application: kdeinit5 (16.04.3)

Qt Version: 5.6.1
Frameworks Version: 5.36.0
Operating System: Linux 4.4.0-124-generic x86_64
Distribution: Linux Mint 18 Sarah

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

This generates sometimes when I simply close dolphin file manager after I have
finished working. Especifically I deleted a folder but I don't know if that has
to do something to it

The crash can be reproduced sometimes.

-- Backtrace:
Application: Dolphin (kdeinit5), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f7803f34780 (LWP 5871))]

Thread 3 (Thread 0x7f77e7060700 (LWP 5873)):
#0  __lll_lock_wait_private () at
../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:95
#1  0x7f78023b42bd in _int_free (av=0x7f77e820, p=0x7f77e80012f0,
have_lock=0) at malloc.c:3962
#2  0x7f78023b853c in __GI___libc_free (mem=) at
malloc.c:2968
#3  0x7f77ff067f06 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f77ff068099 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f77ffd75439 in __nptl_deallocate_tsd () at pthread_create.c:175
#6  0x7f77ffd76870 in __nptl_deallocate_tsd () at pthread_create.c:326
#7  start_thread (arg=0x7f77e7060700) at pthread_create.c:346
#8  0x7f780243b41d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f77ecc9f700 (LWP 5872)):
[KCrash Handler]
#6  0x7f7802369428 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
#7  0x7f780236b02a in __GI_abort () at abort.c:89
#8  0x7f78023ab7ea in __libc_message (do_abort=2,
fmt=fmt@entry=0x7f78024c4ed8 "*** Error in `%s': %s: 0x%s ***\n") at
../sysdeps/posix/libc_fatal.c:175
#9  0x7f78023b27c3 in malloc_printerr (ar_ptr=0x7f77e820,
ptr=0x7f77e80008b0, str=0x7f78024c1c92 "corrupted double-linked list",
action=) at malloc.c:5006
#10 malloc_consolidate (av=av@entry=0x7f77e820) at malloc.c:4175
#11 0x7f78023b5cde in _int_malloc (av=av@entry=0x7f77e820,
bytes=bytes@entry=2032) at malloc.c:3450
#12 0x7f78023b8dca in __libc_calloc (n=,
elem_size=) at malloc.c:3236
#13 0x7f77fe2cc3e3 in ?? () from
/usr/lib/nvidia-384/tls/libnvidia-tls.so.384.111
#14 0x7f77ff051771 in g_malloc0 () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#15 0x7f77ff0692bd in g_slice_free1 () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#16 0x7f77ffd75439 in __nptl_deallocate_tsd () at pthread_create.c:175
#17 0x7f77ffd76870 in __nptl_deallocate_tsd () at pthread_create.c:326
#18 start_thread (arg=0x7f77ecc9f700) at pthread_create.c:346
#19 0x7f780243b41d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f7803f34780 (LWP 5871)):
#0  0x7f77fe2cae15 in _nv014tls () from
/usr/lib/nvidia-384/tls/libnvidia-tls.so.384.111
#1  0x7f78005647cd in ?? () from /usr/lib/nvidia-384/libGL.so.1
#2  0x7f7800564bab in ?? () from /usr/lib/nvidia-384/libGL.so.1
#3  0x7f7800564c9a in ?? () from /usr/lib/nvidia-384/libGL.so.1
#4  0x7f78005aa4da in ?? () from /usr/lib/nvidia-384/libGL.so.1
#5  0x7f7803d69e05 in _dl_fini () at dl-fini.c:240
#6  0x7f780236dff8 in __run_exit_handlers (status=0, listp=0x7f78026f85f8
<__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:82
#7  0x7f780236e045 in __GI_exit (status=) at exit.c:104
#8  0x00408580 in ?? ()
#9  0x00409b39 in ?? ()
#10 0x0040a1d7 in ?? ()
#11 0x00404e74 in ?? ()
#12 0x7f7802354830 in __libc_start_main (main=0x404560, argc=5,
argv=0x7ffd7a321ef8, init=, fini=,
rtld_fini=, stack_end=0x7ffd7a321ee8) at ../csu/libc-start.c:291
#13 0x00405bd9 in _start ()

Possible duplicates by query: bug 392350, bug 387393, bug 381268.

Reported using DrKonqi

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

[partitionmanager] [Bug 394639] No option to view or set partition type (GU)ID

[Matthew Trescott]

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

--- Comment #2 from Matthew Trescott  ---
Nice to know, thanks.

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

[konsole] [Bug 394565] In Vt102Emulation snprintf truncation warnings while compiling

[Kurt Hindenburg]

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

Kurt Hindenburg  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/kon
   ||sole/847b72358d6c5371e7c811
   ||9c7081139112ced728
 Status|UNCONFIRMED |RESOLVED

--- Comment #3 from Kurt Hindenburg  ---
Git commit 847b72358d6c5371e7c8119c7081139112ced728 by Kurt Hindenburg, on
behalf of Mariusz Glebocki.
Committed on 23/05/2018 at 23:42.
Pushed by hindenburg into branch 'master'.

Silence -Wformat-truncation warnings

Summary:
Add a few bytes to a small arrays on stack in order to make compiler
happy. Those warnings are invalid in this context (as long as terminal
width and height are not larger than 8-digits-long number).

Test Plan:
* Build Konsole with GCC 8 and `-Wformat-truncation` flag

Expected result: no format-truncation warnings
Actual result: three format-truncation warnings appear

Reviewers: #konsole, hindenburg

Reviewed By: #konsole, hindenburg

Subscribers: hindenburg, konsole-devel, #konsole

Tags: #konsole

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

M  +2-2src/Vt102Emulation.cpp

https://commits.kde.org/konsole/847b72358d6c5371e7c8119c7081139112ced728

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

[systemsettings] [Bug 389318] menubar section in settings has been disappeared

[bugzilla_noreply]

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

mattcr...@mattcrews.com changed:

   What|Removed |Added

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

--- Comment #5 from mattcr...@mattcrews.com ---
This is a bad design then, because there is no way to disable this setting once
enabled.

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

[plasmashell] [Bug 394119] Panel should not stop auto-hiding even when a window wants attention

[Raf]

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

Raf  changed:

   What|Removed |Added

 CC||raf...@gmail.com

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

[partitionmanager] [Bug 394639] No option to view or set partition type (GU)ID

[Andrius Štikonas]

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

Andrius Štikonas  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #1 from Andrius Štikonas  ---
Yes, this is the long term plan, but some other things have to be completed
first.

Next version (4.0) will use sfdisk backend instead of libparted backend which
is necessary for this migration.

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

[plasmashell] [Bug 330356] Panel auto-hide stops working after using desktop for a while.

[Raf]

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

Raf  changed:

   What|Removed |Added

 CC||raf...@gmail.com

--- Comment #22 from Raf  ---
Hi, in my case panel auto-hide breaks after virtual desktop change or when I
open new app. On that panel I have the following widgets:
- icon only task manager,
- tasks monitor
- digital clock.

The one that breaks auto-hide of panel is task manager/switcher with enabled
option “show tasks only from current desktop”. When you disable this option
(task switcher shows all running apps from all desktops) panel auto-hide works
fine.

You can also fix it by moving the mouse on the panel and after that it hides
correctly. 

Maybe this is related with Bug 394119.

Os: Mint 18.3
Plasma: 5.8.9
KFrameworks: 5.36.0
QT version: 5.6.1

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

[partitionmanager] [Bug 394639] New: No option to view or set partition type (GU)ID

[Matthew Trescott]

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

Bug ID: 394639
   Summary: No option to view or set partition type (GU)ID
   Product: partitionmanager
   Version: 3.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: andr...@stikonas.eu
  Reporter: matthewtresc...@gmail.com
  Target Milestone: ---

When creating or editing a partition's properties, KDE Partition Manager does
not display MBR partition type IDs or GPT partition type GUIDs. I assume that
this probably gets determined for new partitions based on the various settings
(filesystem, "flags", etc.) but the flags don't represent a realistic picture
of the partition table. IMO,
- the flags section should disappear and be replaced with
a drop-down list that allows the user to choose the partition type
(https://en.wikipedia.org/wiki/Partition_type). Note that this applies to both
MBR and GPT; the only difference is that GPT uses long GUID codes and MBR uses
single-byte codes. This would be _in addition_ to the Filesystem drop-down.
- There should be a _separate_ checkbox that toggles the "bootable partition"
bit on GPT (search "Legacy BIOS bootable" on the Wikipedia GPT page for more
info) and the equivalent bit on MBR.

Reasoning:
- Checkboxes (as shown in the flags option) do not make sense when they are
mutually exclusive (because a partition can only be one partition type).
- The flags-based design makes it unclear what "boot" does, since it behaves
differently on GPT and MBR: on GPT, it does the same as "esp", which changes
the partition type GUID in the partition table to
C12A7328-F81F-11D2-BA4B-00A0C93EC93B. On MBR, I assume that it flips bit 7 in
byte offset 0 of the partition entry. But it's unclear whether it does the
equivalent operation on GPT, which, like MBR has a separate "bootable" bit in
addition to partition type GUID.
- The "flags" imply that partition tables have such a structure as "flags,"
which is not the case, at least for GPT and MBR.

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

[systemsettings] [Bug 389318] menubar section in settings has been disappeared

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||mattcr...@mattcrews.com

--- Comment #4 from Christoph Feck  ---
*** Bug 394636 has been marked as a duplicate of this bug. ***

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

[systemsettings] [Bug 394636] No setting to adjust Menubar Style

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #1 from Christoph Feck  ---


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

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

[digikam] [Bug 394590] Feature request: being able to filter on all metadatas fields

[Marc]

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

Marc  changed:

   What|Removed |Added

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

--- Comment #2 from Marc  ---
Hi Maik,

I didn't knew this advanced search form.
It seems that this feature request could be closed because it looks like I
could reach my expectations with this form.

regards

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

[plasma-nm] [Bug 394580] Wrong icon size on network manager applet

[Jonathan]

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

--- Comment #6 from Jonathan  ---
(In reply to TYY331 from comment #5)
> > thanks for response my ask.  Another question. This cache files will be
> > regenerated after delete them?
> 
> Every cache file by definition is regenerated if not found, Qt isn't the
> exception.

thanks... I will try

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

[kmail2] [Bug 393473] Weird "HTML-message" column

[Christophe Giboudeaux]

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

--- Comment #4 from Christophe Giboudeaux  ---
but in that case, it doesn't show the message warning about displaying external
references (tested with master)

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

[kmail2] [Bug 393473] Weird "HTML-message" column

[Christophe Giboudeaux]

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

--- Comment #3 from Christophe Giboudeaux  ---
If you can't click on it, it's because your message is html-only

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

[plasmashell] [Bug 394638] New: Plasma crashed by fast access to kicker

[bugzilla_noreply]

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

Bug ID: 394638
   Summary: Plasma crashed by fast access to kicker
   Product: plasmashell
   Version: 5.8.7
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: frank.hollenb...@online.de
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.7)

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

-- Information about the crash:
- What I was doing when the application crashed:
try to quit and halt the system. Then it hangs first, then it crashed. Plasma
starts again.

The crash does not seem to be reproducible.

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

Thread 17 (Thread 0x7f83071b9700 (LWP 22018)):
#0  0x7f84136df0ff in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f84145ce69b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f84184c855b in  () at /usr/lib64/libQt5Quick.so.5
#3  0x7f84184ca2d5 in  () at /usr/lib64/libQt5Quick.so.5
#4  0x7f84145cda29 in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f84136da724 in start_thread () at /lib64/libpthread.so.0
#6  0x7f8413edce8d in clone () at /lib64/libc.so.6

Thread 16 (Thread 0x7f82e2ffc700 (LWP 22009)):
#0  0x7f84136df0ff in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f84145ce69b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f84184c855b in  () at /usr/lib64/libQt5Quick.so.5
#3  0x7f84184ca2d5 in  () at /usr/lib64/libQt5Quick.so.5
#4  0x7f84145cda29 in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f84136da724 in start_thread () at /lib64/libpthread.so.0
#6  0x7f8413edce8d in clone () at /lib64/libc.so.6

Thread 15 (Thread 0x7f82e27fb700 (LWP 7509)):
#0  0x7f84136df0ff in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f84145ce69b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f84184c855b in  () at /usr/lib64/libQt5Quick.so.5
#3  0x7f84184ca2d5 in  () at /usr/lib64/libQt5Quick.so.5
#4  0x7f84145cda29 in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f84136da724 in start_thread () at /lib64/libpthread.so.0
#6  0x7f8413edce8d in clone () at /lib64/libc.so.6

Thread 14 (Thread 0x7f8304fa8700 (LWP 5015)):
#0  0x7f84136df0ff in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f84145ce69b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f84184c855b in  () at /usr/lib64/libQt5Quick.so.5
#3  0x7f84184ca2d5 in  () at /usr/lib64/libQt5Quick.so.5
#4  0x7f84145cda29 in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f84136da724 in start_thread () at /lib64/libpthread.so.0
#6  0x7f8413edce8d in clone () at /lib64/libc.so.6

Thread 13 (Thread 0x7f82e3ffe700 (LWP 4523)):
#0  0x7f84136df0ff in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f84145ce69b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f84184c855b in  () at /usr/lib64/libQt5Quick.so.5
#3  0x7f84184ca2d5 in  () at /usr/lib64/libQt5Quick.so.5
#4  0x7f84145cda29 in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f84136da724 in start_thread () at /lib64/libpthread.so.0
#6  0x7f8413edce8d in clone () at /lib64/libc.so.6

Thread 12 (Thread 0x7f832977d700 (LWP 4261)):
#0  0x7f84136df0ff in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f84145ce69b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f84184c855b in  () at /usr/lib64/libQt5Quick.so.5
#3  0x7f84184ca2d5 in  () at /usr/lib64/libQt5Quick.so.5
#4  0x7f84145cda29 in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f84136da724 in start_thread () at /lib64/libpthread.so.0
#6  0x7f8413edce8d in clone () at /lib64/libc.so.6

Thread 11 (Thread 0x7f832a091700 (LWP 4260)):
#0  0x7f84136df0ff in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f84145ce69b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f84184c855b in  () at /usr/lib64/libQt5Quick.so.5
#3  0x7f84184ca2d5 in  () at /usr/lib64/libQt5Quick.so.5
#4  0x7f84145cda29 in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f84136da724 in start_thread () at /lib64/libpthread.so.0
#6  0x7f8413edce8d in clone () at /lib64/libc.so.6

Thread 10 (Thread 0x7f833616c700 (LWP 3929)):
#0  0x7f84136df0ff in 

[plasma-nm] [Bug 394580] Wrong icon size on network manager applet

[TYY331]

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

--- Comment #5 from TYY331  ---
> thanks for response my ask.  Another question. This cache files will be
> regenerated after delete them?

Every cache file by definition is regenerated if not found, Qt isn't the
exception.

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

[frameworks-baloo] [Bug 394637] New: Using Double Commander (file manager)

[Sérgio Valente]

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

Bug ID: 394637
   Summary: Using Double Commander (file manager)
   Product: frameworks-baloo
   Version: 5.45.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: normal
  Priority: NOR
 Component: Baloo File Daemon
  Assignee: baloo-bugs-n...@kde.org
  Reporter: valente.ser...@gmail.com
  Target Milestone: ---

Application: baloo_file (5.45.0)

Qt Version: 5.9.4
Frameworks Version: 5.45.0
Operating System: Linux 4.16.9-lp150.2-default x86_64
Distribution: "openSUSE Leap 15.0"

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

Copying and pasteing a file using CTRL-C and CTRL-V on Double Commander (file
manager)

-- Backtrace:
Application: Baloo File Indexing Daemon (baloo_file), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7ff21f347100 (LWP 2822))]

Thread 3 (Thread 0x7fb213f5a700 (LWP 2997)):
#0  0x7ff21bdc9c24 in pthread_getspecific () from /lib64/libpthread.so.0
#1  0x7ff219471ce0 in g_thread_self () from /usr/lib64/libglib-2.0.so.0
#2  0x7ff21944a20d in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7ff21d9dac0b in QEventDispatcherGlib::processEvents
(this=0x55a611b68bc0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7ff21d98309a in QEventLoop::exec (this=this@entry=0x7fb213f59b80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x55a610c08dbd in Baloo::FileContentIndexer::run (this=0x55a611aea8a0)
at
/usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/file/filecontentindexer.cpp:73
#6  0x7ff21d7b4372 in QThreadPoolThread::run (this=0x55a611b21e40) at
thread/qthreadpool.cpp:99
#7  0x7ff21d7b70ce in QThreadPrivate::start (arg=0x55a611b21e40) at
thread/qthread_unix.cpp:368
#8  0x7ff21bdc2559 in start_thread () from /lib64/libpthread.so.0
#9  0x7ff21cd6b82f in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7ff214a6d700 (LWP 2827)):
#0  0x7ff21cd6108b in poll () from /lib64/libc.so.6
#1  0x7ff21944a109 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7ff21944a21c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7ff21d9dac0b in QEventDispatcherGlib::processEvents
(this=0x55a611ac85e0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7ff21d98309a in QEventLoop::exec (this=this@entry=0x7ff214a6cca0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7ff21d7b24da in QThread::exec (this=) at
thread/qthread.cpp:515
#6  0x7ff21ebf7985 in ?? () from /usr/lib64/libQt5DBus.so.5
#7  0x7ff21d7b70ce in QThreadPrivate::start (arg=0x7ff21ee67d60) at
thread/qthread_unix.cpp:368
#8  0x7ff21bdc2559 in start_thread () from /lib64/libpthread.so.0
#9  0x7ff21cd6b82f in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7ff21f347100 (LWP 2822)):
[KCrash Handler]
#6  0x7ff21cca90e0 in raise () from /lib64/libc.so.6
#7  0x7ff21ccaa6c1 in abort () from /lib64/libc.so.6
#8  0x7ff21aa6d922 in mdb_assert_fail (env=0x55a611ada160,
expr_txt=expr_txt@entry=0x7ff21aa6f3af "rc == 0",
func=func@entry=0x7ff21aa6fce8 <__func__.6935> "mdb_page_dirty",
line=line@entry=2071, file=0x7ff21aa6f390 "mdb.c") at mdb.c:1487
#9  0x7ff21aa62e05 in mdb_page_dirty (txn=0x55a611adb650, mp=) at mdb.c:2071
#10 0x7ff21aa63fea in mdb_page_alloc (num=num@entry=1,
mp=mp@entry=0x7ffe87e92468, mc=) at mdb.c:2252
#11 0x7ff21aa64259 in mdb_page_touch (mc=mc@entry=0x7ffe87e929a0) at
mdb.c:2370
#12 0x7ff21aa65d2f in mdb_cursor_touch (mc=mc@entry=0x7ffe87e929a0) at
mdb.c:6273
#13 0x7ff21aa68eee in mdb_cursor_put (mc=0x7ffe87e929a0,
key=0x7ffe87e92d70, data=0x7ffe87e92d80, flags=) at mdb.c:6407
#14 0x7ff21aa6b9ab in mdb_put (txn=0x55a611adb650, dbi=2,
key=key@entry=0x7ffe87e92d70, data=data@entry=0x7ffe87e92d80,
flags=flags@entry=0) at mdb.c:8765
#15 0x7ff21e341e5c in Baloo::PostingDB::put
(this=this@entry=0x7ffe87e92e60, term=..., list=...) at
/usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/engine/postingdb.cpp:78
#16 0x7ff21e34e5d0 in Baloo::WriteTransaction::commit (this=0x55a611b25fe0)
at
/usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/engine/writetransaction.cpp:289
#17 0x7ff21e3474c2 in Baloo::Transaction::commit
(this=this@entry=0x7ffe87e92f10) at
/usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/engine/transaction.cpp:262
#18 0x55a610c11bee in Baloo::MetadataMover::moveFileMetadata
(this=0x55a611ad9d00, from=..., to=...) at
/usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/file/metadatamover.cpp:58
#19 0x7ff21d9b214c in QtPrivate::QSlotObjectBase::call (a=0x7ffe87e93140,
r=0x7ffe87e936e0, this=0x55a611adc450) at
../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:101
#20 QMetaObject::activate (sender=sender@entry=0x55a611ade240,

[Falkon] [Bug 394494] support right-click on touchscreen

[Alexander Browne]

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

Alexander Browne  changed:

   What|Removed |Added

 CC||alexan...@elcste.com

--- Comment #1 from Alexander Browne  ---
FWIW, I tried Falkon on Kubuntu 18.04 (Falkon 3.0.0 with WebEngine 5.9.5) and a
Cosmic daily build (3.0.1; same WebEngine) on a laptop with a touchscreen, and
I was getting the context menu with a long press.

What version of Falkon and WebEngine are you trying?

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

[kwin] [Bug 394605] Thumbnail aside not working on opengl works on xrender

[xircon]

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

xircon  changed:

   What|Removed |Added

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

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

[kwin] [Bug 394605] Thumbnail aside not working on opengl works on xrender

[xircon]

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

--- Comment #3 from xircon  ---
Been at this all day, turning effects on/off.  Then I found it!

Scale method was set to accurate, crisp works, smooth works, accurate does not.

Apologies for wasting your time.  Will report back on Manjaro forum.

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

[plasma-nm] [Bug 394580] Wrong icon size on network manager applet

[Jonathan]

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

--- Comment #4 from Jonathan  ---
(In reply to TYY331 from comment #3)
> I can't reproduce the issue, all I did was to delete the cache files and
> folders associated with KDE in the ~.cache folder for example
> icon-cache.kcache but I really don't know what file did the trick.
> These kinds of problems are frequent when have big Plasma updates
> (5.11->5.12->5.13)
> Maybe it would be sensible to have these cache files removed when a plasma
> update is installed.

thanks for response my ask.  Another question. This cache files will be
regenerated after delete them?

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

[okular] [Bug 394623] Region highlight annotations

[Albert Astals Cid]

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

--- Comment #5 from Albert Astals Cid  ---
Then can you please open a new wishlist item saying you want rectangles?
Because this bug title said regions and region highlights are supported. I
understand rectangles are easier to control than regions, so that's a valid
feature request.

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

[okular] [Bug 394621] support strikethrough annotations

[Albert Astals Cid]

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

--- Comment #11 from Albert Astals Cid  ---
(In reply to Kevin Burton from comment #10)
> ok.. so then maybe this bug is more about the fact that , at least on 1
> machine, strike through isn't an option.

That's just not possible, see
https://cgit.kde.org/okular.git/tree/ui/annotationwidgets.cpp#n539
the four styles are added unconditionally.

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

[Heaptrack] [Bug 394631] tst_inject fails

[Heiko Becker]

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

--- Comment #4 from Heiko Becker  ---
It's actually caused by our build sandbox. If I build without it the test
passes. Sorry, should've checked that first. Guess this can be closed.

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

[okular] [Bug 394623] Region highlight annotations

[Kevin Burton]

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

--- Comment #4 from Kevin Burton  ---
OK.. I DO have polygon. Just not rectangle.

Rectangle is important:

1. they're easy resize.

2. I can resize just the left, right, top , or bottom, or I can pick the corner
to resize.  

3. Drawing a rectangle around a figure is a lot easier than drawing a polygon
to keep the sides even.

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

[okular] [Bug 394621] support strikethrough annotations

[Kevin Burton]

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

--- Comment #10 from Kevin Burton  ---
ok.. so then maybe this bug is more about the fact that , at least on 1
machine, strike through isn't an option.

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

[okular] [Bug 394621] support strikethrough annotations

[Albert Astals Cid]

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

--- Comment #9 from Albert Astals Cid  ---
(In reply to Kevin Burton from comment #5)
> Wow.. Fascinating.  Can you screenshot how you did that? or take a video?

https://www.youtube.com/watch?v=5BBwYbacTMQ

> I wonder if there some IFDEF issue here with poppler or something not having 
> support for those annotation types.

Annotations don't really depend on poppler, they are abstracted on the okular
core level, as you can see the video is on a txt file.

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

[kwin] [Bug 390247] Kwin crashes when clicking on application launcher

[bugzilla_noreply]

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

--- Comment #10 from jkrmnj...@gmail.com ---
(In reply to mikisid from comment #8)

> How you modified that extansion?

You can see the change I made here:
https://github.com/rliang/kwin-dynamic-virtual-desktops/commit/5608feb5de12a183012c812bc7cc2f8f963e33e2

I don't think the package online has been updated but if you install it from
Github it should work.

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

[okular] [Bug 394621] support strikethrough annotations

[Albert Astals Cid]

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

--- Comment #8 from Albert Astals Cid  ---
you commented on the wrong bug, this is about strikethrough.

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

[plasma-browser-integration] [Bug 394629] Plasma integration extension disappeared from Google Web Store

[Michał Dybczak]

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

--- Comment #5 from Michał Dybczak  ---
I still can't find it (I cleared the cache first) but I suspect that there is
some propagation time or something like that, will check tomorrow.

I assume that we will still need those extensions when Plasma 5.13 hits?

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

[kmail2] [Bug 393421] No ability to hide the HTML Message Status Bar

[Richard Gladman]

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

Richard Gladman  changed:

   What|Removed |Added

 CC||kde@the-systems-commonwealt
   ||h.net

--- Comment #19 from Richard Gladman  ---
Also affected by this bug. Please revert the removal of the setting
(https://phabricator.kde.org/R94:1c55919a64491bd5598cf9d8616e77b037edbf87)

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

[systemsettings] [Bug 394636] No setting to adjust Menubar Style

[bugzilla_noreply]

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

mattcr...@mattcrews.com changed:

   What|Removed |Added

 CC||mattcr...@mattcrews.com

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

[systemsettings] [Bug 394636] New: No setting to adjust Menubar Style

[bugzilla_noreply]

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

Bug ID: 394636
   Summary: No setting to adjust Menubar Style
   Product: systemsettings
   Version: 5.12.4
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: kcm_style
  Assignee: unassigned-b...@kde.org
  Reporter: mattcr...@mattcrews.com
  Target Milestone: ---

Created attachment 112841
  --> https://bugs.kde.org/attachment.cgi?id=112841=edit
Screenshot of Widget Style missing Menubar style settings

Under Setting -> Appearance -> Application Style -> Widget Style -> Fine
Tuning, the section for "Menubar style" is completely missing. This occured
after I enabled the global menu, and persisted even after the global menu was
disabled. There is no apparent way to re-enable this.

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

[kwin] [Bug 394605] Thumbnail aside not working on opengl works on xrender

[xircon]

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

--- Comment #2 from xircon  ---
```
 qdbus org.kde.KWin:
/
/0
/ColorCorrect
/ColorPicker
/Compositor
/Effects
/KWin
/Screenshot
/Scripting

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

[calligraflow] [Bug 394635] New: export png

[Arturo Pablo]

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

Bug ID: 394635
   Summary: export png
   Product: calligraflow
   Version: 2.9.11
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: opendocument
  Assignee: yue@mail.com
  Reporter: apabloroc...@gmail.com
  Target Milestone: ---

When i try to export a diagram from odg to png i have a error message, says in
spanish "no fue posible guardar "nombre archivo en png".

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

[plasma-browser-integration] [Bug 394629] Plasma integration extension disappeared from Google Web Store

[Kai Uwe Broulik]

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

--- Comment #4 from Kai Uwe Broulik  ---
Somehow it reset itself to "not listed", I made it public again now.

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

[Heaptrack] [Bug 394631] tst_inject fails

[Milian Wolff]

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

--- Comment #3 from Milian Wolff  ---
I've never heard of that distro. Does it do anything special when it comes to
compilation flags maybe?

Also, installation looks pretty complicated. Is there a live image one can boot
in a VM to debug this?

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

[digikam] [Bug 394434] installation problem mysql internal on mac os high sierra [patch]

[bugzilla_noreply]

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

--- Comment #62 from caulier.gil...@gmail.com ---
In time, these crashes appear just before to see the First Run assistant.

This one populate the Database page with runtime dependecies detected at
startup up.

It's fun to see these thread crashed without to crash the application.

Gilles Caulier

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

[digikam] [Bug 394434] installation problem mysql internal on mac os high sierra [patch]

[bugzilla_noreply]

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

--- Comment #61 from caulier.gil...@gmail.com ---
This is the resume of the 4 crashes which appear when i start digiKam from
Launchpad :

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libsystem_malloc.dylib  0x7fff783dc910 nano_force_unlock +
45
1   libsystem_malloc.dylib  0x7fff783db610 _malloc_fork_child +
284
2   libSystem.B.dylib   0x7fff75ec6afa
libSystem_atfork_child + 24
3   libsystem_c.dylib   0x7fff78280683 fork + 47
4   org.qt-project.QtCore   0x00010c30e5d1 0x10c185000 +
1611217
5   org.qt-project.QtCore   0x00010c30b34b 0x10c185000 +
1598283
6   org.qt-project.QtCore   0x00010c2bae0f 0x10c185000 +
1269263
7   libdigikamcore.6.0.0.dylib  0x000103ef71fd
Digikam::DBinaryIface::checkDir(QString const&) + 509
8   libdigikamcore.6.0.0.dylib  0x000103ef6e6f
Digikam::DBinaryIface::setup(QString const&) + 319
9   libdigikamgui.6.0.0.dylib   0x0001027e2b90
Digikam::MysqlInitBinary::MysqlInitBinary() + 400
10  libdigikamgui.6.0.0.dylib   0x0001027e2975
Digikam::MysqlInitBinary::MysqlInitBinary() + 21
11  libdigikamgui.6.0.0.dylib   0x0001027e2819
Digikam::DatabaseSettingsWidget::Private::Private() + 41
12  libdigikamgui.6.0.0.dylib   0x0001027d9ea5
Digikam::DatabaseSettingsWidget::Private::Private() + 21
13  libdigikamgui.6.0.0.dylib   0x0001027d9e03
Digikam::DatabaseSettingsWidget::DatabaseSettingsWidget(QWidget*) + 147
14  libdigikamgui.6.0.0.dylib   0x0001027ddc8d
Digikam::DatabaseSettingsWidget::DatabaseSettingsWidget(QWidget*) + 29
15  libdigikamgui.6.0.0.dylib   0x000102d41eae
Digikam::DatabasePage::DatabasePage(QWizard*) + 238
16  libdigikamgui.6.0.0.dylib   0x000102d4201d
Digikam::DatabasePage::DatabasePage(QWizard*) + 29
17  libdigikamgui.6.0.0.dylib   0x000102d3c956
Digikam::FirstRunDlg::FirstRunDlg(QWidget*) + 838
18  libdigikamgui.6.0.0.dylib   0x000102d3ce2d
Digikam::FirstRunDlg::FirstRunDlg(QWidget*) + 29
19  digikam 0x0001027b074a main + 7994
20  libdyld.dylib   0x7fff78221015 start + 1

---

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libsystem_malloc.dylib  0x7fff783dc910 nano_force_unlock +
45
1   libsystem_malloc.dylib  0x7fff783db610 _malloc_fork_child +
284
2   libSystem.B.dylib   0x7fff75ec6afa
libSystem_atfork_child + 24
3   libsystem_c.dylib   0x7fff78280683 fork + 47
4   org.qt-project.QtCore   0x00010c30e5d1 0x10c185000 +
1611217
5   org.qt-project.QtCore   0x00010c30b34b 0x10c185000 +
1598283
6   org.qt-project.QtCore   0x00010c2bae0f 0x10c185000 +
1269263
7   libdigikamcore.6.0.0.dylib  0x000103ef71fd
Digikam::DBinaryIface::checkDir(QString const&) + 509
8   libdigikamcore.6.0.0.dylib  0x000103ef6e6f
Digikam::DBinaryIface::setup(QString const&) + 319
9   libdigikamgui.6.0.0.dylib   0x0001027e2fb0
Digikam::MysqlServBinary::MysqlServBinary() + 400
10  libdigikamgui.6.0.0.dylib   0x0001027e2995
Digikam::MysqlServBinary::MysqlServBinary() + 21
11  libdigikamgui.6.0.0.dylib   0x0001027e282f
Digikam::DatabaseSettingsWidget::Private::Private() + 63
12  libdigikamgui.6.0.0.dylib   0x0001027d9ea5
Digikam::DatabaseSettingsWidget::Private::Private() + 21
13  libdigikamgui.6.0.0.dylib   0x0001027d9e03
Digikam::DatabaseSettingsWidget::DatabaseSettingsWidget(QWidget*) + 147
14  libdigikamgui.6.0.0.dylib   0x0001027ddc8d
Digikam::DatabaseSettingsWidget::DatabaseSettingsWidget(QWidget*) + 29
15  libdigikamgui.6.0.0.dylib   0x000102d41eae
Digikam::DatabasePage::DatabasePage(QWizard*) + 238
16  libdigikamgui.6.0.0.dylib   0x000102d4201d
Digikam::DatabasePage::DatabasePage(QWizard*) + 29
17  libdigikamgui.6.0.0.dylib   0x000102d3c956
Digikam::FirstRunDlg::FirstRunDlg(QWidget*) + 838
18  libdigikamgui.6.0.0.dylib   0x000102d3ce2d
Digikam::FirstRunDlg::FirstRunDlg(QWidget*) + 29
19  digikam 0x0001027b074a main + 7994
20  libdyld.dylib   0x7fff78221015 start + 1

-

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libsystem_malloc.dylib  0x7fff783dc910 nano_force_unlock +
45
1   libsystem_malloc.dylib  0x7fff783db610 _malloc_fork_child +
284
2   libSystem.B.dylib   0x7fff75ec6afa
libSystem_atfork_child + 24
3   libsystem_c.dylib   0x7fff78280683 fork + 47
4   org.qt-project.QtCore   0x00010c30e5d1 0x10c185000 +
1611217
5   org.qt-project.QtCore   

[plasma-browser-integration] [Bug 394629] Plasma integration extension disappeared from Google Web Store

[Kai Uwe Broulik]

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

--- Comment #3 from Kai Uwe Broulik  ---
https://chrome.google.com/webstore/detail/plasma-integration/cimiefiiaegbelhefglklhhakcgmhkai
Still there?
I have no idea why I cannot find it through the search

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

[Discover] [Bug 394634] New: Discover crashes (possibly after trying to install flash plugin)

[bugzilla_noreply]

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

Bug ID: 394634
   Summary: Discover crashes (possibly after trying to install
flash plugin)
   Product: Discover
   Version: 5.12.5
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: s1512...@sms.ed.ac.uk
  Target Milestone: ---

Application: plasma-discover (5.12.5)

Qt Version: 5.9.4
Frameworks Version: 5.44.0
Operating System: Linux 4.16.9-200.fc27.x86_64 x86_64
Distribution: "Fedora release 27 (Twenty Seven)"

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

I cannot use Discover at all. It crashes whenever I try to access any of the
tabs.

- Custom settings of the application:

I think it may be connected with my attempts to install the Flash plugin RPM
from adobe website. It seems like the program started crashing after I tried to
use it to install the repo.

The crash can be reproduced every time.

-- Backtrace:
Application: Discover (plasma-discover), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f1acaa938c0 (LWP 4060))]

Thread 15 (Thread 0x7f1a6a7fc700 (LWP 4122)):
#0  0x7f1ac45b7c6b in poll () from /lib64/libc.so.6
#1  0x7f1abdb9ee99 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#2  0x7f1abdb9efac in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7f1ac540dc4b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#4  0x7f1ac53bb96a in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#5  0x7f1ac520c8ca in QThread::exec() () from /lib64/libQt5Core.so.5
#6  0x7f1ac5210de2 in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#7  0x7f1ac22e950b in start_thread () from /lib64/libpthread.so.0
#8  0x7f1ac45c216f in clone () from /lib64/libc.so.6

Thread 14 (Thread 0x7f1a6bfff700 (LWP 4077)):
#0  0x7f1ac45b7c6b in poll () from /lib64/libc.so.6
#1  0x7f1abdb9ee99 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#2  0x7f1abdb9efac in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7f1abdb9eff1 in glib_worker_main () from /lib64/libglib-2.0.so.0
#4  0x7f1abdbc6486 in g_thread_proxy () from /lib64/libglib-2.0.so.0
#5  0x7f1ac22e950b in start_thread () from /lib64/libpthread.so.0
#6  0x7f1ac45c216f in clone () from /lib64/libc.so.6

Thread 13 (Thread 0x7f1a70be8700 (LWP 4076)):
#0  0x7f1ac22efb5b in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f1ac5211423 in QWaitCondition::wait(QMutex*, unsigned long) () from
/lib64/libQt5Core.so.5
#2  0x7f1ac520dda2 in QThreadPoolThread::run() () from
/lib64/libQt5Core.so.5
#3  0x7f1ac5210de2 in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#4  0x7f1ac22e950b in start_thread () from /lib64/libpthread.so.0
#5  0x7f1ac45c216f in clone () from /lib64/libc.so.6

Thread 12 (Thread 0x7f1a713e9700 (LWP 4075)):
#0  0x7f1ac22efb5b in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f1ac5211423 in QWaitCondition::wait(QMutex*, unsigned long) () from
/lib64/libQt5Core.so.5
#2  0x7f1ac520dda2 in QThreadPoolThread::run() () from
/lib64/libQt5Core.so.5
#3  0x7f1ac5210de2 in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#4  0x7f1ac22e950b in start_thread () from /lib64/libpthread.so.0
#5  0x7f1ac45c216f in clone () from /lib64/libc.so.6

Thread 11 (Thread 0x7f1a71bea700 (LWP 4074)):
#0  0x7f1ac22efb5b in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f1ac5211423 in QWaitCondition::wait(QMutex*, unsigned long) () from
/lib64/libQt5Core.so.5
#2  0x7f1ac520dda2 in QThreadPoolThread::run() () from
/lib64/libQt5Core.so.5
#3  0x7f1ac5210de2 in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#4  0x7f1ac22e950b in start_thread () from /lib64/libpthread.so.0
#5  0x7f1ac45c216f in clone () from /lib64/libc.so.6

Thread 10 (Thread 0x7f1a733eb700 (LWP 4071)):
#0  0x7f1ac45b7c6b in poll () from /lib64/libc.so.6
#1  0x7f1abdb9ee99 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#2  0x7f1abdb9efac in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7f1ac540dc4b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#4  0x7f1ac53bb96a in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#5  0x7f1ac520c8ca in QThread::exec() () from /lib64/libQt5Core.so.5
#6  0x7f1ac5210de2 in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#7  0x7f1ac22e950b in start_thread () from /lib64/libpthread.so.0
#8  0x7f1ac45c216f in clone () from /lib64/libc.so.6

[okular] [Bug 394621] support strikethrough annotations

[Kevin Burton]

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

--- Comment #7 from Kevin Burton  ---
OK.. I DO have polygon. Just not rectangle.

Rectangle is important:

1. they're easy resize.

2. I can resize just the left, right, top , or bottom, or I can pick the corner
to resize.  

3. Drawing a rectangle around a figure is a lot easier than drawing a polygon
to keep the sides even.

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

[okular] [Bug 394621] support strikethrough annotations

[Kevin Burton]

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

--- Comment #6 from Kevin Burton  ---
I wonder if there some IFDEF issue here with poppler or something not having
support for those annotation types.

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

[digikam] [Bug 394434] installation problem mysql internal on mac os high sierra [patch]

[bugzilla_noreply]

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

--- Comment #60 from caulier.gil...@gmail.com ---
Created attachment 112840
  --> https://bugs.kde.org/attachment.cgi?id=112840=edit
MacOS log files viewer with digiKam reports while starting from lauchpad

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

[okular] [Bug 394621] support strikethrough annotations

[Kevin Burton]

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

--- Comment #5 from Kevin Burton  ---
Wow.. Fascinating.  Can you screenshot how you did that? or take a video?

That's definitely not on my machine.  I don't even have 'strike out' as one of
the options in type when I edit an existing one.

I have TWO 'pop up note' options though. Which is weird.

Thanks for the help here!

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

[okular] [Bug 394623] Region highlight annotations

[Albert Astals Cid]

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

Albert Astals Cid  changed:

   What|Removed |Added

 Resolution|--- |INVALID
 CC||aa...@kde.org
 Status|UNCONFIRMED |RESOLVED

--- Comment #3 from Albert Astals Cid  ---
https://i.imgur.com/GXLEFOy.png

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

[digikam] [Bug 394434] installation problem mysql internal on mac os high sierra [patch]

[bugzilla_noreply]

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

--- Comment #59 from caulier.gil...@gmail.com ---
Testa, Maik,

Sorry for my late response. I'm not at home, and i'm busy until next Sunday.

I can confirm that i can reproduce the problem when i start digiKam directly
from OSX desktop icon. Running under OS console work perfectly.

And yes it sound like a wrong path somewhere. As we don't have any console
feedback under OSX in this case, it's difficult to investiguate.

There is a tool under OSX to show events and log from application. It's limited
but instructive. The tool is located in Launchpad/Others/Console (log). It's
not a terminal, it's a log files viewer very well done.

Gilles Caulier

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

[okular] [Bug 394621] support strikethrough annotations

[Albert Astals Cid]

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

--- Comment #4 from Albert Astals Cid  ---
Yes https://i.imgur.com/bR5hJW4.png

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

[Heaptrack] [Bug 394631] tst_inject fails

[Heiko Becker]

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

--- Comment #2 from Heiko Becker  ---
(In reply to Milian Wolff from comment #1)
> Qt isn't relevant here - heaptrack only uses Qt for the GUI.
> 
> What system is this? I.e. what distribution? What hardware platform? 32bit
> or 64bit?

Exherbo, x86_64, 64bit

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

[systemsettings] [Bug 394632] Options are missing when I switch sections available in system settings > workspace theme

[Antonio Rojas]

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

Antonio Rojas  changed:

   What|Removed |Added

 CC||aro...@archlinux.org

--- Comment #1 from Antonio Rojas  ---
For reference, the misleading "Error loading plugin" message is due to
https://bugs.kde.org/show_bug.cgi?id=348798 and is unrelated to this issue

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

[Heaptrack] [Bug 394627] Unable to use with Mudlet

[Milian Wolff]

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

--- Comment #1 from Milian Wolff  ---
Can you try to debug this and see what happens? I.e. attach a debugger when it
hangs and get me a full backtrace for all threads?

Otherwise, can you add information for me to reproduce this issue? Do I just
run mudlet? Do I need some parameters or input files?

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

[Heaptrack] [Bug 394631] tst_inject fails

[Milian Wolff]

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

--- Comment #1 from Milian Wolff  ---
Qt isn't relevant here - heaptrack only uses Qt for the GUI.

What system is this? I.e. what distribution? What hardware platform? 32bit or
64bit?

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

[okular] [Bug 383651] Custom/image stamp annotations are not saved into the PDF file in a way that can be printed or that other readers can see

[Kevin Burton]

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

--- Comment #24 from Kevin Burton  ---
I'll probably have to look and see if we can confirm that this is the problem. 

maybe a test app that generates all the annotation types ... 

I'm working on a separate project that can export the annotations as JSON from
PDF.js and make them machine readable.

I might be able to include the colors there so that we could have a unit test
or some way to verify that they work.  

poppler might already have some options for this.

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

[kontact] [Bug 394633] New: How to delete home directory using kontact

[bugzilla_noreply]

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

Bug ID: 394633
   Summary: How to delete home directory using kontact
   Product: kontact
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: contacts
  Assignee: to...@kde.org
  Reporter: au...@gangsto.cz
CC: kdepim-b...@kde.org
  Target Milestone: ---

So I deleted my entire home directory using kontact. Here's how:

I never used kontact before, but had .vcf files in ~/.local/share/contacts
synced with vdirsyncer from a carddav server.

This was before installing kontact and Akonadi.

Now I decided to use Kontact and carddav directly, so I don't need those
directories anymore, so I deleted them using the terminal and adjusted
vdirsyncer config to not sync those anymore.

I noticed the directories lingered in kontact, so i deleted it from the view
there as well, and i restarted kontact. It proceeded to explode with error
messages, and now my home directory was completely cleaned out.

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

[systemsettings] [Bug 394632] Options are missing when I switch sections available in system settings > workspace theme

[Colin J Thomson]

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

Colin J Thomson  changed:

   What|Removed |Added

 CC||colin.thom...@g6avk.co.uk

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

[okular] [Bug 394623] Region highlight annotations

[Kevin Burton]

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

--- Comment #2 from Kevin Burton  ---
Just updating.  


https://imgur.com/a/UR9w77J


I don't have those options.

This is running from the latest unstable build too via docker container so I'm
running the latest and greatest okular and they aren't available in either
version.

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

[okular] [Bug 394621] support strikethrough annotations

[Kevin Burton]

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

--- Comment #3 from Kevin Burton  ---
I wish I was wrong here but not on my 1.33 and not on unstable okular either.  

Here's what I have:


https://imgur.com/a/UR9w77J


Adding a new annotation shows less than the screenshot above.


Am I missing something?

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

[systemsettings] [Bug 394632] New: Options are missing when I switch sections available in system settings > workspace theme

[Dr . Chapatin]

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

Bug ID: 394632
   Summary: Options are missing when I switch sections available
in system settings > workspace theme
   Product: systemsettings
   Version: 5.12.90
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: bugsefor...@gmx.com
  Target Milestone: ---

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

open system settings, click "Configure" button on top, select "icon view" and
click "Ok" button
open "workspace theme", switch between the sections available on the left side
Watch my screencast please.

Already reported in Arch tracker
https://bugs.archlinux.org/task/58704

"No, this is not a packaging issue. The original upstream report was, but it
has now become a messy mixture of unrelated issues. The "Error loading plugin"
message is harmless and has been there forever. The actual error here is 
file:///usr/share/kpackage/kcms/kcm_lookandfeel/contents/ui/main.qml:198:26:
Unable to assign [undefined] to bool
file:///usr/share/kpackage/kcms/kcm_splashscreen/contents/ui/main.qml:41:
Error: Cannot assign [undefined] to int"

Currently I use plasma 5.13 beta + qt 5.11 rc2 + frameworks 5.46, but plasma
5.12.5 + qt 5.10.1 + frameworks 5.46 had the same problem.

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

[Heaptrack] [Bug 394631] New: tst_inject fails

[Heiko Becker]

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

Bug ID: 394631
   Summary: tst_inject fails
   Product: Heaptrack
   Version: 1.1.0
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: m...@milianw.de
  Reporter: heire...@exherbo.org
  Target Milestone: ---

Built with Qt 5.10.1

5: Test command:
/var/tmp/paludis/build/dev-util-heaptrack-1.1.0/work/build/tests/auto/tst_inject
5: Test timeout computed to be: 1000
5: 
5:
~~~
5: tst_inject is a Catch v1.2.1 host application.
5: Run with -? for options
5: 
5:
---
5: inject via dlopen
5:
---
5:
/var/tmp/paludis/build/dev-util-heaptrack-1.1.0/work/heaptrack-1.1.0/tests/auto/tst_inject.cpp:87
5:
...
5: 
5:
/var/tmp/paludis/build/dev-util-heaptrack-1.1.0/work/heaptrack-1.1.0/tests/auto/tst_inject.cpp:82:
FAILED:
5:   REQUIRE( contents.find("\n+") != std::string::npos )
5: with expansion:
5:   18446744073709551615 (0x)
5:   !=
5:   18446744073709551615 (0x)
5: 
5:
---
5: inject via libc
5:
---
5:
/var/tmp/paludis/build/dev-util-heaptrack-1.1.0/work/heaptrack-1.1.0/tests/auto/tst_inject.cpp:105
5:
...
5: 
5:
/var/tmp/paludis/build/dev-util-heaptrack-1.1.0/work/heaptrack-1.1.0/tests/auto/tst_inject.cpp:82:
FAILED:
5:   REQUIRE( contents.find("\n+") != std::string::npos )
5: with expansion:
5:   18446744073709551615 (0x)
5:   !=
5:   18446744073709551615 (0x)
5: 
5:
===
5: test cases:  2 |  0 passed | 2 failed
5: assertions: 21 | 19 passed | 2 failed
5: 
5/5 Test #5: tst_inject ...***Failed0.06 sec

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

[plasma-browser-integration] [Bug 394629] Plasma integration extension disappeared from Google Web Store

[Michał Dybczak]

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

--- Comment #2 from Michał Dybczak  ---
I'm not talking about the package. In order for Plasma integration to work we
need to install browser extensions as well. Unless they won't be needed
anymore? If that so, it's not clearly stated anymore and chrome extension is
deleted prematurely.

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

[plasma-browser-integration] [Bug 394629] Plasma integration extension disappeared from Google Web Store

[mthw0]

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

mthw0  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 CC||jari...@hotmail.com
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from mthw0  ---
(In reply to Michał Dybczak from comment #0)
> Not sure what happened but Plasma integration extension disappeared from
> Google Web Store.
> 
> My Chromium still has it installed and it works great (it worked always
> better then on Firefox although I noticed improvement lately on Firefox
> part) but it is not possible to find and install for new users. I've been
> searching the web for some information about it but so far nothing.
> 
> What happened? Is it just a temporary issue? Will it be back?
> 
> This is even stranger in face of incoming Plasma 5.13 where plasma
> integration is one of the flagship features.
> 
> I send the extension to one of my friends directly from my Chromium install
> and it works as expected for him. I also can't see any issues with it so why
> is it gone from Google Web Store?

Plasma browser integration will come in form of regular package (.deb/.rpm/?)
and will be installed as part of update to Plasma 5.13

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

[frameworks-kio] [Bug 76380] Trashing files on other partitions and disks that are mounted without UID=USERID, GID=USERGROUPID, FMASK=177, DMASK=077 copies them to the Trash directory on /

[Francesco Turco]

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

Francesco Turco  changed:

   What|Removed |Added

 CC||ftu...@fastmail.fm

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

[plasmashell] [Bug 394630] New: Plasma crash after qbittorrent exit or disable/enable widget

[Nick Stefanov]

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

Bug ID: 394630
   Summary: Plasma crash after qbittorrent exit or disable/enable
widget
   Product: plasmashell
   Version: 5.12.5
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: m...@abv.bg
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.12.5)

Qt Version: 5.10.1
Frameworks Version: 5.46.0
Operating System: Linux 4.16.10-1-ARCH x86_64
Distribution: "Arch Linux"

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

Sometimes (often) Plasma crashes on qbittorrent exit via right click->exit. It
often crashes too at widget change - enable or disable.

The crash can be reproduced sometimes.

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

Thread 13 (Thread 0x7ff50f1fe700 (LWP 16246)):
#0  0x7ff60b67fffc in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7ff60c4c8f9c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7ff6102cc5fa in  () at /usr/lib/libQt5Quick.so.5
#3  0x7ff6102cca84 in  () at /usr/lib/libQt5Quick.so.5
#4  0x7ff60c4c7abd in  () at /usr/lib/libQt5Core.so.5
#5  0x7ff60b67a075 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7ff60bdcb53f in clone () at /usr/lib/libc.so.6

Thread 12 (Thread 0x7ff52f5ef700 (LWP 9146)):
#0  0x7ff60b67fffc in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7ff60c4c8f9c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7ff6102cc5fa in  () at /usr/lib/libQt5Quick.so.5
#3  0x7ff6102cca84 in  () at /usr/lib/libQt5Quick.so.5
#4  0x7ff60c4c7abd in  () at /usr/lib/libQt5Core.so.5
#5  0x7ff60b67a075 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7ff60bdcb53f in clone () at /usr/lib/libc.so.6

Thread 11 (Thread 0x7ff52d357700 (LWP 3669)):
#0  0x7ff60b67fffc in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7ff60c4c8f9c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7ff6102cc5fa in  () at /usr/lib/libQt5Quick.so.5
#3  0x7ff6102cca84 in  () at /usr/lib/libQt5Quick.so.5
#4  0x7ff60c4c7abd in  () at /usr/lib/libQt5Core.so.5
#5  0x7ff60b67a075 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7ff60bdcb53f in clone () at /usr/lib/libc.so.6

Thread 10 (Thread 0x7ff535d12700 (LWP 1196)):
#0  0x7ff60b67fffc in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7ff60c4c8f9c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7ff6102cc5fa in  () at /usr/lib/libQt5Quick.so.5
#3  0x7ff6102cca84 in  () at /usr/lib/libQt5Quick.so.5
#4  0x7ff60c4c7abd in  () at /usr/lib/libQt5Core.so.5
#5  0x7ff60b67a075 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7ff60bdcb53f in clone () at /usr/lib/libc.so.6

Thread 9 (Thread 0x7ff537a51700 (LWP 1193)):
#0  0x7ff60bdc0ea9 in poll () at /usr/lib/libc.so.6
#1  0x7ff606613523 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7ff60661363e in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7ff60c711254 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7ff60c6b331b in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7ff60c4c271e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7ff60c4c7abd in  () at /usr/lib/libQt5Core.so.5
#7  0x7ff60b67a075 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7ff60bdcb53f in clone () at /usr/lib/libc.so.6

Thread 8 (Thread 0x7ff54015b700 (LWP 1192)):
#0  0x7ff60bdc0ea9 in poll () at /usr/lib/libc.so.6
#1  0x7ff606613523 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7ff60661363e in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7ff60c711254 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7ff60c6b331b in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7ff60c4c271e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7ff53c4d8b6a in  () at
/usr/lib/qt/qml/QtQuick/XmlListModel/libqmlxmllistmodelplugin.so
#7  0x7ff60c4c7abd in  () at /usr/lib/libQt5Core.so.5
#8  0x7ff60b67a075 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7ff60bdcb53f in clone () at /usr/lib/libc.so.6

Thread 7 (Thread 0x7ff55764d700 (LWP 1089)):
#0  0x7ff60b67fffc in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7ff60c4c8f9c in 

[frameworks-baloo] [Bug 393583] Baloo crashes on login

[mthw0]

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

mthw0  changed:

   What|Removed |Added

 CC||jari...@hotmail.com

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

[frameworks-baloo] [Bug 394404] baloo file indexer crashes after some runtime

[mthw0]

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

mthw0  changed:

   What|Removed |Added

 CC||jari...@hotmail.com
 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

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

[KScreen] [Bug 394609] External monitor pop-up doesn't work on wayland

[mthw0]

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

mthw0  changed:

   What|Removed |Added

 CC||jari...@hotmail.com

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

[okular] [Bug 383651] Custom/image stamp annotations are not saved into the PDF file in a way that can be printed or that other readers can see

[Nate Graham]

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

--- Comment #23 from Nate Graham  ---
I agree that we should focus on Poppler. If I'm reading
https://bugs.freedesktop.org/show_bug.cgi?id=23108#c21 correctly, patches were
merged that handled some annotation types, but not all of them. We should
probably focus on the remaining annotation types that still need default
Poppler appearance streams.

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

[plasma-browser-integration] [Bug 394629] New: Plasma integration extension disappeared from Google Web Store

[Michał Dybczak]

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

Bug ID: 394629
   Summary: Plasma integration extension disappeared from Google
Web Store
   Product: plasma-browser-integration
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Chrome
  Assignee: k...@privat.broulik.de
  Reporter: michal.dybc...@gmail.com
  Target Milestone: ---

Not sure what happened but Plasma integration extension disappeared from Google
Web Store.

My Chromium still has it installed and it works great (it worked always better
then on Firefox although I noticed improvement lately on Firefox part) but it
is not possible to find and install for new users. I've been searching the web
for some information about it but so far nothing.

What happened? Is it just a temporary issue? Will it be back?

This is even stranger in face of incoming Plasma 5.13 where plasma integration
is one of the flagship features.

I send the extension to one of my friends directly from my Chromium install and
it works as expected for him. I also can't see any issues with it so why is it
gone from Google Web Store?

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

[plasmashell] [Bug 393787] Icons only task manager gets confused between Native Steam app and Wine Steam

[Eike Hein]

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

--- Comment #18 from Eike Hein  ---
No problem, thanks for your bug report and the patience!

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

[okular] [Bug 394621] support strikethrough annotations

[Albert Astals Cid]

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

Albert Astals Cid  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||aa...@kde.org
 Resolution|--- |INVALID

--- Comment #2 from Albert Astals Cid  ---
This is supported since ages.

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

[kdenlive] [Bug 394275] Kdenlive crashes after the "Blur" effect is added to a track

[Wolfgang Bauer]

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

Wolfgang Bauer  changed:

   What|Removed |Added

 CC||wba...@tmo.at

--- Comment #2 from Wolfgang Bauer  ---
I can confirm that
https://cgit.kde.org/kdenlive.git/commit/?h=Applications/18.04=9b09dbb2b0de78d4eaf4011c8a462fdb3c6916b6
fixes the crashes here in openSUSE with libmlt 6.6.0+git20180502 (should be
close to 6.8.0 final).

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

[plasmashell] [Bug 393787] Icons only task manager gets confused between Native Steam app and Wine Steam

[Benjamin Xiao]

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

--- Comment #17 from Benjamin Xiao  ---
Wonderful! Looking forward to seeing these changes land in the next update.
Thanks again for your wonderful work.

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

[plasmashell] [Bug 393787] Icons only task manager gets confused between Native Steam app and Wine Steam

[Eike Hein]

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

--- Comment #16 from Eike Hein  ---
And the next part: https://phabricator.kde.org/D13073

Between the two, both Steam versions are now correctly mapped, pin well, etc.

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

[kmail2] [Bug 394628] New: Kontact 5.8.1 Reply to mail in HTML mode crashes KMail

[Axel Braun]

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

Bug ID: 394628
   Summary: Kontact 5.8.1 Reply to mail in HTML mode crashes KMail
   Product: kmail2
   Version: 5.7.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: composereditor-ng
  Assignee: mon...@kde.org
  Reporter: axel.br...@gmx.de
  Target Milestone: ---

Having 'Reply in HTML-mode' enabled causes kmail to crash:
docb@T520:~> kmail
Found only the dummy module in speech-dispatcher. No text to speech possible.
Install a tts module (e.g. espeak).
[0523/200333.211634:WARNING:stack_trace_posix.cc(648)] Failed to open file:
/home/docb/#536873062 (deleted)
  Error: Datei oder Verzeichnis nicht gefunden
QXcbConnection: XCB error: 8 (BadMatch), sequence: 2384, resource id:
132120663, major code: 130 (Unknown), minor code: 3
QXcbConnection: XCB error: 8 (BadMatch), sequence: 2387, resource id:
132120663, major code: 130 (Unknown), minor code: 3
QXcbConnection: XCB error: 8 (BadMatch), sequence: 2390, resource id:
132120663, major code: 130 (Unknown), minor code: 3
QXcbConnection: XCB error: 8 (BadMatch), sequence: 3234, resource id:
132120663, major code: 130 (Unknown), minor code: 3
QXcbConnection: XCB error: 8 (BadMatch), sequence: 3252, resource id:
132120663, major code: 130 (Unknown), minor code: 3
QXcbConnection: XCB error: 8 (BadMatch), sequence: 3256, resource id:
132120663, major code: 130 (Unknown), minor code: 3
org.kde.pim.messagecore: Adding image 0x55dcae378ac0
org.kde.pim.messagecore: Adding image 0x55dcb7c86710
org.kde.pim.messagecore: Adding image 0x55dcb5814930
org.kde.pim.templateparser: Adding 0x55dcae378ac0 as an embedded image
org.kde.pim.templateparser: Adding 0x55dcb7c86710 as an embedded image
org.kde.pim.templateparser: Adding 0x55dcb5814930 as an embedded image
Received signal 11 SEGV_MAPERR 
#0 0x7f15e55b5a86 
#1 0x7f15e41dd70a 
#2 0x7f15e55b5dfc 
#3 0x7f15fa6dba70 
#4 0x7f15fb6e8a14 QTextLine::height()
#5 0x7f15fb732ae5 
#6 0x7f15fb7372a5 
#7 0x7f15fb737729 
#8 0x7f15fb7378f8 QTextDocumentLayout::doLayout()
#9 0x7f15fb7389c3 QTextDocumentLayout::documentChanged()
#10 0x7f15fb71544a QTextDocumentPrivate::finishEdit()
#11 0x7f15fb73da34 QTextCursor::removeSelectedText()
#12 0x7f15f3b0433b KPIMTextEdit::RichTextComposerImages::loadImage()
#13 0x7f15f7ef761a MessageComposer::ComposerViewBase::collectImages()
#14 0x7f15f7ef7eb7 MessageComposer::ComposerViewBase::setMessage()
#15 0x7f15fd0387a7 
#16 0x7f15fd03f4db 
#17 0x7f15fd03fab1 
#18 0x7f15fcfada67 
#19 0x7f15fb0a936c QMetaObject::activate()
#20 0x7f15f7f4c482 MessageComposer::MessageFactoryNG::createReplyDone()
#21 0x7f15f7f308ce MessageComposer::MessageFactoryNG::slotCreateReplyDone()
#22 0x7f15fb0a936c QMetaObject::activate()
#23 0x7f15f7f4c533 
#24 0x7f15f7f35e21 
#25 0x7f15fb0a936c QMetaObject::activate()
#26 0x7f15f7823fdf TemplateParser::TemplateParserJob::parsingDone()
#27 0x7f15f77ff57b TemplateParser::TemplateParserJob::slotExtractInfoDone()
#28 0x7f15fb0a936c QMetaObject::activate()
#29 0x7f15f7823f82 
#30 0x7f15f781f5ef 
#31 0x7f15fb0a936c QMetaObject::activate()
#32 0x7f15f7823f0f 
#33 0x7f15f781ec56 
#34 0x7f15eaabb2e1 
#35 0x7f15e4269099 
#36 0x7f15e48d7cf8 
#37 0x7f15e48f164e 
#38 0x7f15e4a7a6c6 
#39 0x7f15e5ee65c3 
#40 0x7f15e563b842 
#41 0x7f15e55d2e98 
#42 0x7f15e55d3e78 
#43 0x7f15e55d42e3 
#44 0x7f15e4210a98 
#45 0x7f15fb0a9c0b QObject::event()
#46 0x7f15fbe0401c QApplicationPrivate::notify_helper()
#47 0x7f15fbe0b314 QApplication::notify()
#48 0x7f15fb07b148 QCoreApplication::notifyInternal2()
#49 0x7f15fb07db25 QCoreApplicationPrivate::sendPostedEvents()
#50 0x7f15fb0d3393 
#51 0x7f15ee0a7277 g_main_context_dispatch
#52 0x7f15ee0a74b0 
#53 0x7f15ee0a753c g_main_context_iteration
#54 0x7f15fb0d2a0f QEventDispatcherGlib::processEvents()
#55 0x7f15ceaed781 
#56 0x7f15fb07995a QEventLoop::exec()
#57 0x7f15fb082494 QCoreApplication::exec()
#58 0x55dcabf2dbcc 
#59 0x7f15fa6c6a87 __libc_start_main
#60 0x55dcabf2dcfa 
  r8: 0006  r9: 0018 r10: 55dcba449e0c r11:
55dcba449e30
 r12: 7ffcbd82dc00 r13: 7ffcbd82dd10 r14: 08e8 r15:
7ffcbd82dcf0
  di: 7ffcbd82dc00  si:   bp: 7ffcbd82dba0  bx:
55dcb9ee55a0
  dx:   ax:   cx: 005a  sp:
7ffcbd82dab8
  ip: 7f15fb6e8a14 efl: 00010246 cgf: 002b0033 erf:
0004
 trp: 000e msk:  cr2: 
[end of stack trace]
Calling _exit(1). Core file will not be generated.
docb@T520:~>

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

[okular] [Bug 394623] Region highlight annotations

[Burkhard Lueck]

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

Burkhard Lueck  changed:

   What|Removed |Added

 CC||lu...@hube-lueck.de

--- Comment #1 from Burkhard Lueck  ---
https://phabricator.kde.org/D13072

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

[kwin] [Bug 394605] Thumbnail aside not working on opengl works on xrender

[Martin Flöser]

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

--- Comment #1 from Martin Flöser  ---
I cannot reproduce. Works just fine here.

Can you please provide the output of:
qdbus org.kde.KWin /KWin supportInformation

when the problem is visible.

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

[kwin] [Bug 394603] Don't put minimized windows to the end of ALT-TAB stack in MRU mode

[Martin Flöser]

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

--- Comment #3 from Martin Flöser  ---
We don't add random options, I'm sorry.

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