[extra-cmake-modules] [Bug 375195] Pass -fno-operator-names when supported breaks build of several packages

[Kevin Funk]

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

--- Comment #8 from Kevin Funk  ---
Is there a problem you're trying to fix or is this just a theoretical concern?

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

[kwin] [Bug 379803] Kwin crashed when switching screens

[EssL]

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

--- Comment #2 from EssL  ---
yep

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

[frameworks-kio] [Bug 355258] plasmashell is preventing systemd automount shares from idle unmounting

[Joseph Yasi]

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

--- Comment #11 from Joseph Yasi  ---
I tracked the stat call down to KMountPoint::List::findByPath which is called
by KDiskFreeSpaceInfo again. That is being called by Device Notifier. When
systemd times out and unmounts my automounts, Device Notifier gets an event and
rescans the mounts. This triggers all of my automounts to remount when it stats
them.

KMountPoint::List:findByPath calls
QFileInfo fileinfo(path);
const QString realname = fileinfo.exists()

The fileinfo.exists() ends up calling stat on the mount point which retriggers
the mount. This causes my automounts to constantly remount after they timeout.
Is there a way to turn off the free space feature for Device Notifier?

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

[kmail2] [Bug 379791] Confusing Account Wizard dialog

[Laurent Montel]

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

Laurent Montel  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||mon...@kde.org
 Resolution|--- |FIXED

--- Comment #5 from Laurent Montel  ---
For sure we don't have it in new version.

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

[kdenlive] [Bug 379836] New: Kdenlive always crashes on exit (Kdenlive 17.04.1 on Neon w/ Latest Nvidia Drivers)

[Pranav Sharma]

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

Bug ID: 379836
   Summary: Kdenlive always crashes on exit (Kdenlive 17.04.1 on
Neon w/ Latest Nvidia Drivers)
   Product: kdenlive
   Version: 17.04.1
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: pranav.sharma@gmail.com
  Target Milestone: ---

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

Application: kdenlive (17.04.1)

Qt Version: 5.7.1
Frameworks Version: 5.33.0
Operating System: Linux 4.8.0-51-generic x86_64
Distribution: KDE neon User Edition 5.9

-- Information about the crash:
- What I was doing when the application crashed:
I just exit Kdenlive and while the program exits, it seems to crash as it is
exiting.

I am running KDE neon with an Nvidia GPU and latest nvidia drivers.

The crash can be reproduced every time.

-- Backtrace:
Application: Kdenlive (kdenlive), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f0cf50958c0 (LWP 32300))]

Thread 18 (Thread 0x7f0c82529700 (LWP 32648)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f0cc59538ae in ?? () from
/usr/lib/x86_64-linux-gnu/libavcodec-ffmpeg.so.56
#2  0x7f0ced1c46ba in start_thread (arg=0x7f0c82529700) at
pthread_create.c:333
#3  0x7f0ceeb6b82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 17 (Thread 0x7f0c82d2a700 (LWP 32647)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f0cc59538ae in ?? () from
/usr/lib/x86_64-linux-gnu/libavcodec-ffmpeg.so.56
#2  0x7f0ced1c46ba in start_thread (arg=0x7f0c82d2a700) at
pthread_create.c:333
#3  0x7f0ceeb6b82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 16 (Thread 0x7f0c8352b700 (LWP 32646)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f0cc59538ae in ?? () from
/usr/lib/x86_64-linux-gnu/libavcodec-ffmpeg.so.56
#2  0x7f0ced1c46ba in start_thread (arg=0x7f0c8352b700) at
pthread_create.c:333
#3  0x7f0ceeb6b82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 15 (Thread 0x7f0c83d2c700 (LWP 32645)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f0cc59538ae in ?? () from
/usr/lib/x86_64-linux-gnu/libavcodec-ffmpeg.so.56
#2  0x7f0ced1c46ba in start_thread (arg=0x7f0c83d2c700) at
pthread_create.c:333
#3  0x7f0ceeb6b82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 14 (Thread 0x7f0c9e079700 (LWP 32644)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f0cc59538ae in ?? () from
/usr/lib/x86_64-linux-gnu/libavcodec-ffmpeg.so.56
#2  0x7f0ced1c46ba in start_thread (arg=0x7f0c9e079700) at
pthread_create.c:333
#3  0x7f0ceeb6b82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 13 (Thread 0x7f0caed62700 (LWP 32643)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f0cc59538ae in ?? () from
/usr/lib/x86_64-linux-gnu/libavcodec-ffmpeg.so.56
#2  0x7f0ced1c46ba in start_thread (arg=0x7f0caed62700) at
pthread_create.c:333
#3  0x7f0ceeb6b82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 12 (Thread 0x7f0c81d28700 (LWP 32642)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f0cc59538ae in ?? () from
/usr/lib/x86_64-linux-gnu/libavcodec-ffmpeg.so.56
#2  0x7f0ced1c46ba in start_thread (arg=0x7f0c81d28700) at
pthread_create.c:333
#3  0x7f0ceeb6b82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 11 (Thread 0x7f0c81527700 (LWP 32641)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f0cc59538ae in ?? () from
/usr/lib/x86_64-linux-gnu/libavcodec-ffmpeg.so.56
#2  0x7f0ced1c46ba in start_thread (arg=0x7f0c81527700) at
pthread_create.c:333
#3  0x7f0ceeb6b82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 10 (Thread 0x7f0c80d26700 (LWP 32640)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f0cc59538ae in ?? () from
/usr/lib/x86_64-linux-gnu/libavcodec-ffmpeg.so.56
#2  0x7f0ced1c46ba in start_thread (arg=0x7f0c80d26700) at
pthread_create.c:333
#3  0x7f0ceeb6b82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 9 (Thread 0x7f0c9c98e700 (LWP 32320)):
#0  0x7f0ceeb5fb5d in poll () at ..

[kscreenlocker] [Bug 379796] kscreenlocker/ksmserver-logout-greeter crashing repeatedly in Neon after recent update

[Martin Flöser]

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

Martin Flöser  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |UPSTREAM

--- Comment #3 from Martin Flöser  ---
Driver bug.

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

[kdenlive] [Bug 379837] New: Kdenlive always crashes on exit (Kdenlive 17.04.1 on Neon w/ Latest Nvidia Drivers)

[Pranav Sharma]

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

Bug ID: 379837
   Summary: Kdenlive always crashes on exit (Kdenlive 17.04.1 on
Neon w/ Latest Nvidia Drivers)
   Product: kdenlive
   Version: 17.04.1
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: pranav.sharma@gmail.com
  Target Milestone: ---

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

Application: kdenlive (17.04.1)

Qt Version: 5.7.1
Frameworks Version: 5.33.0
Operating System: Linux 4.8.0-51-generic x86_64
Distribution: KDE neon User Edition 5.9

-- Information about the crash:
- What I was doing when the application crashed:
I just exit Kdenlive and while the program exits, it seems to crash as it is
exiting.

I am running KDE neon with an Nvidia GPU and latest nvidia drivers.

The crash can be reproduced every time.

-- Backtrace:
Application: Kdenlive (kdenlive), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f0cf50958c0 (LWP 32300))]

Thread 18 (Thread 0x7f0c82529700 (LWP 32648)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f0cc59538ae in ?? () from
/usr/lib/x86_64-linux-gnu/libavcodec-ffmpeg.so.56
#2  0x7f0ced1c46ba in start_thread (arg=0x7f0c82529700) at
pthread_create.c:333
#3  0x7f0ceeb6b82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 17 (Thread 0x7f0c82d2a700 (LWP 32647)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f0cc59538ae in ?? () from
/usr/lib/x86_64-linux-gnu/libavcodec-ffmpeg.so.56
#2  0x7f0ced1c46ba in start_thread (arg=0x7f0c82d2a700) at
pthread_create.c:333
#3  0x7f0ceeb6b82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 16 (Thread 0x7f0c8352b700 (LWP 32646)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f0cc59538ae in ?? () from
/usr/lib/x86_64-linux-gnu/libavcodec-ffmpeg.so.56
#2  0x7f0ced1c46ba in start_thread (arg=0x7f0c8352b700) at
pthread_create.c:333
#3  0x7f0ceeb6b82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 15 (Thread 0x7f0c83d2c700 (LWP 32645)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f0cc59538ae in ?? () from
/usr/lib/x86_64-linux-gnu/libavcodec-ffmpeg.so.56
#2  0x7f0ced1c46ba in start_thread (arg=0x7f0c83d2c700) at
pthread_create.c:333
#3  0x7f0ceeb6b82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 14 (Thread 0x7f0c9e079700 (LWP 32644)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f0cc59538ae in ?? () from
/usr/lib/x86_64-linux-gnu/libavcodec-ffmpeg.so.56
#2  0x7f0ced1c46ba in start_thread (arg=0x7f0c9e079700) at
pthread_create.c:333
#3  0x7f0ceeb6b82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 13 (Thread 0x7f0caed62700 (LWP 32643)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f0cc59538ae in ?? () from
/usr/lib/x86_64-linux-gnu/libavcodec-ffmpeg.so.56
#2  0x7f0ced1c46ba in start_thread (arg=0x7f0caed62700) at
pthread_create.c:333
#3  0x7f0ceeb6b82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 12 (Thread 0x7f0c81d28700 (LWP 32642)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f0cc59538ae in ?? () from
/usr/lib/x86_64-linux-gnu/libavcodec-ffmpeg.so.56
#2  0x7f0ced1c46ba in start_thread (arg=0x7f0c81d28700) at
pthread_create.c:333
#3  0x7f0ceeb6b82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 11 (Thread 0x7f0c81527700 (LWP 32641)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f0cc59538ae in ?? () from
/usr/lib/x86_64-linux-gnu/libavcodec-ffmpeg.so.56
#2  0x7f0ced1c46ba in start_thread (arg=0x7f0c81527700) at
pthread_create.c:333
#3  0x7f0ceeb6b82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 10 (Thread 0x7f0c80d26700 (LWP 32640)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f0cc59538ae in ?? () from
/usr/lib/x86_64-linux-gnu/libavcodec-ffmpeg.so.56
#2  0x7f0ced1c46ba in start_thread (arg=0x7f0c80d26700) at
pthread_create.c:333
#3  0x7f0ceeb6b82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 9 (Thread 0x7f0c9c98e700 (LWP 32320)):
#0  0x7f0ceeb5fb5d in poll () at ..

[kcalc] [Bug 379821] Exponent button (x*10y) only works with numbers entered immediately previously

[Burkhard Lueck]

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

Burkhard Lueck  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1
 CC||lu...@hube-lueck.de

--- Comment #1 from Burkhard Lueck  ---
confirmed in master build from sources

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

[frameworks-kdbusaddons] [Bug 379830] All kde binaries crash in QDBusConnectionPrivate::closeConnection() when exiting without opening a window

[Rex Dieter]

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

--- Comment #1 from Rex Dieter  ---
May be a regression in a recent qt5-qtbase update,
https://bodhi.fedoraproject.org/updates/FEDORA-2017-41124b7b1d

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

[frameworks-kdbusaddons] [Bug 379830] All kde binaries crash in QDBusConnectionPrivate::closeConnection() when exiting without opening a window

[Rex Dieter]

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

Rex Dieter  changed:

   What|Removed |Added

 CC||rdie...@math.unl.edu

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

[kmail2] [Bug 379791] Confusing Account Wizard dialog

[Martin]

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

Martin  changed:

   What|Removed |Added

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

--- Comment #4 from Martin  ---
Version of kmail is 5.2.3.

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

[frameworks-kio] [Bug 355258] plasmashell is preventing systemd automount shares from idle unmounting

[Joseph Yasi]

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

--- Comment #10 from Joseph Yasi  ---
I can confirm that Device Notifier is the culprit this time. I attached strace
to plasmashell and see stat("/mediastorage/mediastorage" after every auto
umount. I removed Device Notifier from the system tray, and no longer see this.
I see a read of mounts around the same time, so it looks like it's reading
through my mounts and doing a stat. This is problematic for automounts. I will
try to pin down where Device Notifier is doing this.

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

[frameworks-kio] [Bug 355258] plasmashell is preventing systemd automount shares from idle unmounting

[Joseph Yasi]

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

--- Comment #9 from Joseph Yasi  ---
This bug has reappeared for me. I had worked around it by patching
KDiskFreeSpaceInfo to not call stat on "probablySlow" mount points.

However, this has recently started happening again with that patch installed. I
don't know what is calling stat on my automounts now, but plasmashell 5.9.4 on
Ubuntu Zesty is causing my systemd automounts to remount shortly after they
timeout and autounmount:
May 14 22:07:34 fishasshole systemd[1]: Unmounting
/mediastorage/mediastorage...
-- Subject: Unit mediastorage-mediastorage.mount has begun shutting down
-- Unit mediastorage-mediastorage.mount has begun shutting down.
May 14 22:07:34 fishasshole systemd[1]: Unmounted /mediastorage/mediastorage.
-- Subject: Unit mediastorage-mediastorage.mount has finished shutting down
-- Unit mediastorage-mediastorage.mount has finished shutting down.
May 14 22:07:34 fishasshole systemd[1]: mediastorage-mediastorage.automount:
Got automount request for /mediastorage/mediastorage, triggered by 18881
(plasmashell)
May 14 22:07:34 fishasshole systemd[1]: Mounting /mediastorage/mediastorage...
-- Subject: Unit mediastorage-mediastorage.mount has begun start-up
-- Unit mediastorage-mediastorage.mount has begun starting up.
May 14 22:07:34 fishasshole systemd[1]: Mounted /mediastorage/mediastorage.
-- Subject: Unit mediastorage-mediastorage.mount has finished start-up
-- Unit mediastorage-mediastorage.mount has finished starting up.

I will try to trace why it is stating those mount points.

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

[gwenview] [Bug 379823] Message to cut and delete when opening image

[Xanadu]

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

Xanadu  changed:

   What|Removed |Added

 CC||b210...@mvrht.net

--- Comment #1 from Xanadu  ---
Created attachment 105540
  --> https://bugs.kde.org/attachment.cgi?id=105540&action=edit
Screen capture image.

I can confirm that this started happening to me after a big update on the 14
May 2017. OS Linux Mint 18.0 KDE updated from Plasma version 5.8.5 to 5.8.6.

The error happens when clicking on png or jpg in the Home folder or when
selecting them from "Recent Documents" listed in the Application Menu.

Screenshot enclosed.

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

[okular] [Bug 379835] New: okular crashes on scrolling

[bugzilla_noreply]

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

Bug ID: 379835
   Summary: okular crashes on scrolling
   Product: okular
   Version: 0.25.0
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: edikedikedike...@gmail.com
  Target Milestone: ---

Application: okular (0.25.0)
KDE Platform Version: 4.14.22
Qt Version: 4.8.7
Operating System: Linux 4.4.0-75-generic x86_64
Distribution: Linux Mint 18.1 Serena

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

I was scrolling the book, pdf, nothing else. Crashes at random places of the
book after somewhat 3 sec of scrolling down

The crash can be reproduced every time.

-- Backtrace:
Application: Okular (okular), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f286a4bf900 (LWP 11738))]

Thread 4 (Thread 0x7f285244f700 (LWP 15633)):
[KCrash Handler]
#6  0x7f2867590428 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
#7  0x7f286759202a in __GI_abort () at abort.c:89
#8  0x7f2852a2b789 in GfxPatchMeshShading::parse(GfxResources*, int, Dict*,
Stream*, OutputDev*, GfxState*) () from
/usr/lib/x86_64-linux-gnu/libpoppler.so.58
#9  0x7f2852a2cbdb in GfxShading::parse(GfxResources*, Object*, OutputDev*,
GfxState*) () from /usr/lib/x86_64-linux-gnu/libpoppler.so.58
#10 0x7f28529fb83d in GfxResources::lookupShading(char*, OutputDev*,
GfxState*) () from /usr/lib/x86_64-linux-gnu/libpoppler.so.58
#11 0x7f2852a0586f in Gfx::opShFill(Object*, int) () from
/usr/lib/x86_64-linux-gnu/libpoppler.so.58
#12 0x7f2852a0697e in Gfx::go(bool) () from
/usr/lib/x86_64-linux-gnu/libpoppler.so.58
#13 0x7f2852a06e20 in Gfx::display(Object*, bool) () from
/usr/lib/x86_64-linux-gnu/libpoppler.so.58
#14 0x7f2852a4cf45 in Page::displaySlice(OutputDev*, double, double, int,
bool, bool, int, int, int, int, bool, bool (*)(void*), void*, bool (*)(Annot*,
void*), void*, bool) () from /usr/lib/x86_64-linux-gnu/libpoppler.so.58
#15 0x7f2852da6726 in Poppler::Page::textList(Poppler::Page::Rotation)
const () from /usr/lib/x86_64-linux-gnu/libpoppler-qt4.so.4
#16 0x7f2852ffbff3 in ?? () from /usr/lib/kde4/okularGenerator_poppler.so
#17 0x7f285876a012 in ?? () from /usr/lib/libokularcore.so.7
#18 0x7f2868a15e3c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#19 0x7f286480c6ba in start_thread (arg=0x7f285244f700) at
pthread_create.c:333
#20 0x7f286766182d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f284bfff700 (LWP 15632)):
#0  syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1  0x7f2868a14672 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#2  0x7f2868a10925 in QMutex::lockInternal() () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#3  0x7f2852ffd0e7 in ?? () from /usr/lib/kde4/okularGenerator_poppler.so
#4  0x7f285876a713 in ?? () from /usr/lib/libokularcore.so.7
#5  0x7f2868a15e3c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#6  0x7f286480c6ba in start_thread (arg=0x7f284bfff700) at
pthread_create.c:333
#7  0x7f286766182d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f2851c4e700 (LWP 11744)):
#0  0x7f2867655b5d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f2863cd338c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f2863cd349c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f2868b5623e in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#4  0x7f2868b2413f in
QEventLoop::processEvents(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#5  0x7f2868b244a5 in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#6  0x7f2868a13549 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#7  0x7f2868b041d3 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#8  0x7f2868a15e3c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#9  0x7f286480c6ba in start_thread (arg=0x7f2851c4e700) at
pthread_create.c:333
#10 0x7f286766182d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f286a4bf900 (LWP 11738)):
#0  0x7f286765169d in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f2863d166f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f2863cd2e74 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f2863cd3330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f2863cd349c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f2868b

[plasmashell] [Bug 373749] Left/right arrow keys switch to one direction in RTL

[Hamid]

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

Hamid  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|FIXED   |---

--- Comment #6 from Hamid  ---
Hello,

Left/right key is Ok but up/down/escape only move to the left page (or probably
right if the KDE interface language is LTR) as if you are sending a left
keystroke. Up/down should move focus to the upper or lower item and escape
should presumably close the launcher.

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

[kaffeine] [Bug 379834] 2.0.9 build error with frameworks ( ki18n ) >= 5.34.0

[Gabriel C]

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

Gabriel C  changed:

   What|Removed |Added

 CC||nix.or@gmail.com

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

[kaffeine] [Bug 379834] New: 2.0.9 build error with frameworks ( ki18n ) >= 5.34.0

[Gabriel C]

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

Bug ID: 379834
   Summary: 2.0.9 build error with frameworks ( ki18n ) >= 5.34.0
   Product: kaffeine
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mchehab+...@kernel.org
  Reporter: nix.or@gmail.com
  Target Milestone: ---

Hello,

notice the following build error while rebuilding kde applications against 
frameworks 5.34.0:

CMake Error at /usr/lib64/cmake/KF5I18n/KF5I18NMacros.cmake:106
(add_custom_target):
  add_custom_target cannot create target
  "pofiles-10d72210d417e16d8cd0ab35f9f8f3bf" because another target with the
  same name already exists.  The existing target is a custom target created
  in source directory "/var/tmp/fst/src/kaffeine-2.0.9".  See documentation
  for policy CMP0002 for more details.
Call Stack (most recent call first):
  CMakeLists.txt:111 (ki18n_install)

I used follwing patch to workaround this issue :
https://github.com/frugalware/kde5/commit/6fc8b4d7a7e7a7f2660c039aa7983b2b64ade5b9#diff-045e678ab2c445442c4c7fb71ae7a573

Regards

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

[digikam] [Bug 379833] New: Sidecar files are not being created for some files

[wildcowboy]

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

Bug ID: 379833
   Summary: Sidecar files are not being created for some files
   Product: digikam
   Version: 5.5.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Metadata-Sidecar
  Assignee: digikam-de...@kde.org
  Reporter: aegor...@gmail.com
  Target Milestone: ---

I just added many video files (mp4) to a folder in digiKam collection and
noticed that xmp sidecar was created for only one file.

If I for example add geolocation to the file that has xmp I get no GUI error
and GPS coordinates being added to the sidecar.
Here is the output of the terminal:
---
digikam.geoiface: "setting backend googlemaps"
digikam.geoiface: "ROADMAP"
digikam.geoiface: located data: 
QUrl("file:///usr/share/digikam/geoiface/backend-googlemaps.html")
digikam.geoiface: Maps Loading Progress:  10 %
digikam.geoiface: "ASSERT: isReady() -
/home/abuild/rpmbuild/BUILD/digikam-5.5.0/core/utilities/geolocation/geoiface/backends/backendgooglemaps.cpp:402"
digikam.geoiface: Maps Loading Progress:  50 %
digikam.geoiface: 
digikam.general: 0 1
digikam.geoiface: 
digikam.general: 1 2
digikam.geoiface: Maps Loading Progress:  100 %
digikam.geoiface: Map Loading Completed:  true
digikam.geoiface: "ROADMAP"
digikam.geoiface: "backend googlemaps is ready!"
digikam.geoiface: "googlemaps:8"
digikam.geoiface: 8
digikam.geoiface: QVariant(QPersistentModelIndex,
QModelIndex(0,0,0x0,Digikam::GPSImageModel(0x4033410))) QSize(32, 58)
digikam.geoiface: QVariant(QPersistentModelIndex,
QModelIndex(1,0,0x0,Digikam::GPSImageModel(0x4033410))) QSize(32, 58)
digikam.geoiface: 
digikam.geoiface: 
digikam.geoiface: 
digikam.geoiface: "ASSERT: currentBounds.first.lat() <
currentBounds.second.lat() -
/home/abuild/rpmbuild/BUILD/digikam-5.5.0/core/utilities/geolocation/geoiface/abstractmarkertiler.cpp:256"
digikam.geoiface: "ASSERT: currentBounds.first.lon() <
currentBounds.second.lon() -
/home/abuild/rpmbuild/BUILD/digikam-5.5.0/core/utilities/geolocation/geoiface/abstractmarkertiler.cpp:257"
digikam.geoiface: "level 4: 0 non empty tiles sorted into 0 clusters (0
searched)"
digikam.geoiface: start updateclusters
digikam.geoiface: end updateclusters
digikam.metaengine: Cannot load metadata from file   (Error # 11 : 
/mnt/data/FamilyPictures/2016/2016-10/20161023_191434_x264.mp4: The file
contains data of an unknown image type
digikam.geoiface: 
digikam.metaengine: MetaEngine::metadataWritingMode 3
digikam.metaengine: Will write Metadata to file
"/mnt/data/FamilyPictures/2016/2016-10/20161023_191434_x264.mp4"
digikam.metaengine: Cannot save metadata to image using Exiv2   (Error # 11 : 
/mnt/data/FamilyPictures/2016/2016-10/20161023_191434_x264.mp4: The file
contains data of an unknown image type
digikam.metaengine: Metadata for file "20161023_191434_x264.mp4" written to
file.
digikam.metaengine: Will write XMP sidecar for file "20161023_191434_x264.mp4"
digikam.metaengine: wroteComment:  false
digikam.metaengine: wroteEXIF:  true
digikam.metaengine: wroteIPTC:  true
digikam.metaengine: wroteXMP:  true
digikam.metaengine: Metadata for file "20161023_191434_x264.mp4" written to XMP
sidecar.
digikam.geoiface: 
digikam.general: 0 1
digikam.geoiface: "ASSERT: currentBounds.first.lat() <
currentBounds.second.lat() -
/home/abuild/rpmbuild/BUILD/digikam-5.5.0/core/utilities/geolocation/geoiface/abstractmarkertiler.cpp:256"
digikam.geoiface: "ASSERT: currentBounds.first.lon() <
currentBounds.second.lon() -
/home/abuild/rpmbuild/BUILD/digikam-5.5.0/core/utilities/geolocation/geoiface/abstractmarkertiler.cpp:257"
digikam.geoiface: "level 4: 0 non empty tiles sorted into 0 clusters (0
searched)"
digikam.geoiface: start updateclusters
digikam.geoiface: end updateclusters
---

If I try to add geolocation to another file from this folder I get the error
"Failed to open file" after pressing "Save". No sidecar being created.
Here is the output of the terminal:
---
digikam.geoiface: "setting backend googlemaps"
digikam.geoiface: "ROADMAP"
digikam.geoiface: located data: 
QUrl("file:///usr/share/digikam/geoiface/backend-googlemaps.html")
digikam.geoiface: Maps Loading Progress:  10 %
digikam.metaengine: Cannot load metadata from file   (Error # 11 : 
/mnt/data/FamilyPictures/2016/2016-10/20161015_093414_x264.mp4: The file
contains data of an unknown image type
digikam.metaengine: Cannot load metadata from file   (Error # 11 : 
/mnt/data/FamilyPictures/2016/2016-10/20161015_093414_x264.mp4: The file
contains data of an unknown image type
digikam.geoiface: "ASSERT: isReady() -
/home/abuild/rpmbuild/BUILD/digikam-5.5.0/core/utilities/geolocation/geoiface/backends/backendgooglemaps.cpp:402"
digikam.geoiface: Maps Loading Progress:  50 %
digikam.geoiface: 
digikam.general: 1 2
digikam.general: 0 1
digikam.geoiface: Maps Loading Progress:  100 %
digikam.

[dolphin] [Bug 375813] DrKonqi can't report error because address is missing

[bugzilla_noreply]

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

p...@alicious.com changed:

   What|Removed |Added

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

--- Comment #5 from p...@alicious.com ---
It's more weird: on crash now (attempting to open from the device pop-up menu
in the kde tray on Kubuntu) the "report" button is again greyed out. There is
no longer a duplicate entry as there was in my previous report; if I load
dolphin in the normal way and send a sigabrt then I do get an active "report"
button, so it seems it's situational as to whether dolphin (or is that drkonqi)
can get the address or not.

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

[valgrind] [Bug 374963] increase valgrind's load address to prevent mmap failure

[Ivo Raisr]

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

Ivo Raisr  changed:

   What|Removed |Added

   Assignee|jsew...@acm.org |iv...@ivosh.net
 Status|CONFIRMED   |ASSIGNED

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

[Discover] [Bug 379784] Duplicate desktop file

[Antonio Rojas]

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

Antonio Rojas  changed:

   What|Removed |Added

   Version Fixed In||5.10
 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/dis
   ||cover/13d96d15a177132b6d360
   ||7a7f389a60cb7d615af
 Status|CONFIRMED   |RESOLVED

--- Comment #2 from Antonio Rojas  ---
Git commit 13d96d15a177132b6d3607a7f389a60cb7d615af by Antonio Rojas.
Committed on 14/05/2017 at 21:25.
Pushed by arojas into branch 'Plasma/5.10'.

Fix duplicate Discover entry on the Application Menu

Differential Revision: https://phabricator.kde.org/D5850
FIXED-IN: 5.10

M  +1-0   
libdiscover/backends/FlatpakBackend/org.kde.discover-flatpak.desktop

https://commits.kde.org/discover/13d96d15a177132b6d3607a7f389a60cb7d615af

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

[krita] [Bug 379832] New: [HUION H420] tablet cursor offset

[Fuyukine]

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

Bug ID: 379832
   Summary: [HUION H420] tablet cursor offset
   Product: krita
   Version: 3.1.3-rc
  Platform: unspecified
OS: MS Windows
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: tablet support
  Assignee: krita-bugs-n...@kde.org
  Reporter: sennanekor...@gmail.com
  Target Milestone: ---

There is a horziontal cursor offset apparent while using Krita 3.1.3 with the
H420 Huion tablet. I have a one display setup. The offset is only apparent in
Krita 3.1.3 and not in other IMP's such as GIMP and MANGA STUDIO.

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

[minuet] [Bug 379831] New: Could not find a suitable SoundController plugin

[SP]

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

Bug ID: 379831
   Summary: Could not find a suitable SoundController plugin
   Product: minuet
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: general
  Assignee: sandroandr...@kde.org
  Reporter: scp.stj...@gmail.com
  Target Milestone: ---

I have built and installed Minuet from github source. (I presume it is version
0.2 though this is not reported from the command line.)  The program installs
flawlessy as it reports that I have all the requirements.  The program does not
start if it is run from the GUI.  If I run it from a terminal it reports,
"Could not find a suitable SoundController plugin!"  I see that the following
are installed:
/usr/include/minuet/interfaces/isoundcontroller.h
/usr/lib64/plugins/minuet/minuetfluidsynthsoundcontroller.so

My environment:
KDE Plasma 5.9.5
KDE Frameworks 5.33.0
Qt 5.7.1
Kernel: 4.10.14-200.fc25.x86_64

Any advice or help appreciated

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

[frameworks-kdbusaddons] [Bug 379830] New: All kde binaries crash in QDBusConnectionPrivate::closeConnection() when exiting without opening a window

[bugzilla_noreply]

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

Bug ID: 379830
   Summary: All kde binaries crash in
QDBusConnectionPrivate::closeConnection() when exiting
without opening a window
   Product: frameworks-kdbusaddons
   Version: 5.33.0
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: fa...@kde.org
  Reporter: ber...@codewiz.org
CC: kdelibs-b...@kde.org
  Target Milestone: ---

I noticed this today, but it may have been going since the release of
kdeframeworks 5.33.

On my system, pretty much every KDE 5 binary segfaults on exit, *unless* it has
opened its main window. For instance, if I run systemsettings once and then
close the window, it exits cleanly. If I run it a second time while the first
one is still open, this second instance crashes in
QDBusConnectionPrivate::closeConnection().

KDE command line binaries crash just after printing their help text. Tested
with kdesu, kde-open5 and kcmshell5. The latter crashes on exit only if it
exits without opening the kcm window. Also noteworthy is that kcmshell4 never
crashes.


Here's a gdb session from kcmshell5:

$ gdb kcmshell5  
GNU gdb (GDB) Fedora 7.12.1-48.fc25
Copyright (C) 2017 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-redhat-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"...
set scheduler-locking on
Reading symbols from kcmshell5...Reading symbols from
/home/bernie/src/bernie/mandelwow/kcmshell5...(no debugging symbols
found)...done.
(no debugging symbols found)...done.
Missing separate debuginfos, use: dnf debuginfo-install
kde-cli-tools-5.9.5-1.fc25.x86_64
(gdb) c
The program is not being run.
(gdb) r
Starting program: /usr/bin/kcmshell5 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7fffe40cc700 (LWP 30617)]
[New Thread 0x7fffdbd56700 (LWP 30618)]
Usage: /usr/bin/kcmshell5 [options] module
A tool to start single system settings modules

Options:
  -v, --version  Displays version information.
  -h, --help Displays this help.
  --author   Show author information.
  --license  Show license information.
  --desktopfile   The base file name of the desktop entry for this
 application.
  --list List all possible modules
  --lang   Specify a particular language
  --silent   Do not display main window
  --args  Arguments for the module
  --icon   Use a specific icon for the window
  --caption Use a specific caption for the window

Arguments:
  module Configuration module to open

Thread 3 "QDBusConnection" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffdbd56700 (LWP 30618)]
0x75404f8d in QObject::disconnect(QObject const*, char const*, QObject
const*, char const*) () from /lib64/libQt5Core.so.5
(gdb) bt
#0  0x75404f8d in QObject::disconnect(QObject const*, char const*,
QObject const*, char const*) () at /lib64/libQt5Core.so.5
#1  0x77f22fb0 in QDBusConnectionPrivate::closeConnection() () at
/lib64/libQt5DBus.so.5
#2  0x77f0f852 in QDBusConnectionManager::run() () at
/lib64/libQt5DBus.so.5
#3  0x7523a9ca in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#4  0x729cd6ca in start_thread () at /lib64/libpthread.so.0
#5  0x7462df7f in clone () at /lib64/libc.so.6

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

[Breeze] [Bug 379790] MDI SubWindows are frozen (non-responsive) with Breeze and Oxygen

[Hugo Pereira Da Costa]

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

Hugo Pereira Da Costa  changed:

   What|Removed |Added

   Priority|NOR |VLO

--- Comment #6 from Hugo Pereira Da Costa  ---
Thanks for posting the ui file
I can reproduce all the freezes you describe. Will investigate.
Raising as high priority

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

[kscreenlocker] [Bug 379796] kscreenlocker/ksmserver-logout-greeter crashing repeatedly in Neon after recent update

[NiO]

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

--- Comment #2 from NiO  ---
Seems you were right, thanks. Updated Nvidia driver fixed it

I had just installed system updates and greeter/screen lock suddenly started
crashing.  It is fixed now, feel free to close

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

[frameworks-baloo] [Bug 379739] insane baloo_file (and plasmashell) 256 GB virtual memory size

[skierpage]

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

--- Comment #2 from skierpage  ---
(In reply to Rex Dieter from comment #1)
> fyi, the VIRT table of memory you reference is not a good metric.  RES+SHR
> is a better measure of real usage.

Sure. But it's not free to maintain mapping for 1/4 Terabyte of VM. And if the
cause of the enormous virtual size is the wrong huge size for baloo/index,
something seems wrong in how Baloo accesses this file.

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

[korganizer] [Bug 379813] Korganizer and Kaddressbook doesnt sync anymore using Webdav

[bernd]

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

bernd  changed:

   What|Removed |Added

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

--- Comment #1 from bernd  ---
KDE Frameworks 5 has been updated to 5.34.0 - That solves the problem

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

[krita] [Bug 379829] Krita display unresponsive

[bugzilla_noreply]

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

toastzombi...@gmail.com changed:

   What|Removed |Added

   Keywords||usability

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

[krita] [Bug 379829] New: Krita display unresponsive

[bugzilla_noreply]

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

Bug ID: 379829
   Summary: Krita display unresponsive
   Product: krita
   Version: 3.1.3-rc
  Platform: Windows CE
OS: Windows CE
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: toastzombi...@gmail.com
  Target Milestone: ---

When trying to work on any document, new or opened, the brush, zoom or any
action except the warp around feature is unresponsive. Any brush stroke I try
to make doesn't show up or any movement around the canvas. The display catches
up if I hit the warp around key (W), but otherwise I can't see anything I'm
doing. I've tried restarting the program, my computer, and reinstalling the
software, but there's no change. There was a recent Windows 10 update and
that's the only thing I can think of that's breaking Krita.

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

[kdenlive] [Bug 379828] Unable to render after updating codecs. 'freeze -p' not allowed

[James A . Jaworski]

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

James A. Jaworski  changed:

   What|Removed |Added

 CC||jimj_...@yahoo.ca

--- Comment #1 from James A. Jaworski  ---
Created attachment 105539
  --> https://bugs.kde.org/attachment.cgi?id=105539&action=edit
Yumex-DNF screenshot updating codecs

Yumex-DNF screenshot updating codecs:

x265, ffmpeg, gstreamer1-plugins-bad,

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

[kdenlive] [Bug 379611] I cant capture video from my webcam

[James A . Jaworski]

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

James A. Jaworski  changed:

   What|Removed |Added

 CC||jimj_...@yahoo.ca

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

[kdenlive] [Bug 379828] New: Unable to render after updating codecs. 'freeze -p' not allowed

[James A . Jaworski]

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

Bug ID: 379828
   Summary: Unable to render after updating codecs. 'freeze -p'
not allowed
   Product: kdenlive
   Version: 16.12.3
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: Video Display & Export
  Assignee: j...@kdenlive.org
  Reporter: jimj_...@yahoo.ca
  Target Milestone: ---

After using 'yumex-dnf' or Software Centre in Fedora to update
gstreamer1-plugins-bad, ffmpeg, h264 codecs, I can no longer Render to File.
Kdenlive halts rendering immediately after start and displays the following
error message in the status window:

Rendering of /home/lilzebra/kdenlive/projects/untitled.mp4 crashed

Unknown flag: 'p'; Usage: freeze [-cdfvVg] [file | +type ...] -c Write output
on stdout, don't remove original. -d If given, melting is done instead. -g Use
"greedy" parsing (1.5% worse, 40% faster). -f Forces output file to be
generated, even if one already exists, and even if no space is saved by
freezeing. -i Image mode. -t Text mode. -v Write freezing statistics. -vv means
"draw progress indicator". -V Write version and compilation options.

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

[plasmashell] [Bug 378698] Icons became too large

[bugzilla_noreply]

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

--- Comment #11 from n...@mail.ticket-please.ga ---
and that goddamn gap on the right discribed in
https://bugs.kde.org/show_bug.cgi?id=378700 (seems that devs ignoring that bug)

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

[kwin] [Bug 379819] [Wayland] QT UI element overflow in systemsettings Display section

[Martin Flöser]

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

Martin Flöser  changed:

   What|Removed |Added

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

--- Comment #1 from Martin Flöser  ---


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

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

[KScreen] [Bug 365864] Display layout preview renders off-window in Display Configuration using Wayland

[Martin Flöser]

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

Martin Flöser  changed:

   What|Removed |Added

 CC||rajdeepna...@gmail.com

--- Comment #14 from Martin Flöser  ---
*** Bug 379819 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 378698] Icons became too large

[bugzilla_noreply]

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

--- Comment #10 from n...@mail.ticket-please.ga ---
Created attachment 105538
  --> https://bugs.kde.org/attachment.cgi?id=105538&action=edit
screen2

and for flash device before clicking for actions

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

[kwin] [Bug 344326] Buffer objects (VBO, FBO) need remapping after suspend/vt switch with NVIDIA

[Martin Flöser]

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

Martin Flöser  changed:

   What|Removed |Added

 CC||jonespanic...@gmail.com

--- Comment #160 from Martin Flöser  ---
*** Bug 379814 has been marked as a duplicate of this bug. ***

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

[kwin] [Bug 379814] Black Screen on Resuming from Suspend to RAM with Nvidia Proprietary Driver

[Martin Flöser]

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

Martin Flöser  changed:

   What|Removed |Added

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

--- Comment #1 from Martin Flöser  ---


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

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

[plasmashell] [Bug 378698] Icons became too large

[bugzilla_noreply]

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

n...@mail.ticket-please.ga changed:

   What|Removed |Added

 CC||n...@mail.ticket-please.ga

--- Comment #9 from n...@mail.ticket-please.ga ---
Created attachment 105537
  --> https://bugs.kde.org/attachment.cgi?id=105537&action=edit
screen

There is also too big icon for gwenview

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

[kwin] [Bug 379803] Kwin crashed when switching screens

[Martin Flöser]

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

--- Comment #1 from Martin Flöser  ---
NVIDIA graphics?

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

[kdeconnect] [Bug 368438] KDE Connect does not communicate while running in background on phone

[Matt Whitlock]

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

--- Comment #19 from Matt Whitlock  ---
(In reply to Theresa from comment #18)
> Alas my phone (Oneplus One) only has Android 6.

FYI, LineageOS 14.1 (Android 7.1) is available for the OnePlus One. LineageOS
is the successor to CyanogenOS (which, if I'm not mistaken, is what the OnePlus
One runs out of the box).

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

[dolphin] [Bug 379827] New: Dolphin crashed moving files to a NTFS partition

[Iván R .]

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

Bug ID: 379827
   Summary: Dolphin crashed moving files to a NTFS partition
   Product: dolphin
   Version: 17.04.0
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: ivan.rinco...@gmail.com
  Target Milestone: ---

Application: dolphin (17.04.0)

Qt Version: 5.7.1
Frameworks Version: 5.33.0
Operating System: Linux 4.8.0-51-generic x86_64
Distribution: KDE neon User Edition 5.9

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

File in /home/user (Ext4) > move to > /media/user/folder (NTFS) with Dolphin >
access denied to /home/file.ex message > Retry > The file /home/user//file.ex
does not exist message > Cancel > Crash

NTFS partition parameters in fstab:
UUID=DCDA0B17DA0AED98 /media/ivan/Acer ntfsdefaults,umask=007,gid=46 0 
 0

The crash can be reproduced every time.

-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f91d4a568c0 (LWP 31556))]

Thread 4 (Thread 0x7f91c2d3e700 (LWP 31562)):
#0  0x7f91e7757b5d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f91dc4bf38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f91dc4bf49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f91e24e775b in QEventDispatcherGlib::processEvents
(this=0x7f91bc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f91e24920ba in QEventLoop::exec (this=this@entry=0x7f91c2d3dd00,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7f91e22c1f64 in QThread::exec (this=) at
thread/qthread.cpp:507
#6  0x7f91e22c6b48 in QThreadPrivate::start (arg=0x28f0fd0) at
thread/qthread_unix.cpp:368
#7  0x7f91de7c86ba in start_thread (arg=0x7f91c2d3e700) at
pthread_create.c:333
#8  0x7f91e776382d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f91cbfff700 (LWP 31560)):
#0  __libc_enable_asynccancel () at
../sysdeps/unix/sysv/linux/x86_64/cancellation.S:65
#1  0x7f91e7757b52 in poll () at ../sysdeps/unix/syscall-template.S:84
#2  0x7f91dc4bf38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f91dc4bf49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f91e24e775b in QEventDispatcherGlib::processEvents
(this=0x7f91c40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7f91e24920ba in QEventLoop::exec (this=this@entry=0x7f91cbffecd0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#6  0x7f91e22c1f64 in QThread::exec (this=) at
thread/qthread.cpp:507
#7  0x7f91e7e47735 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#8  0x7f91e22c6b48 in QThreadPrivate::start (arg=0x7f91e7ebbd60) at
thread/qthread_unix.cpp:368
#9  0x7f91de7c86ba in start_thread (arg=0x7f91cbfff700) at
pthread_create.c:333
#10 0x7f91e776382d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f91d1ecb700 (LWP 31559)):
#0  0x7f91e7757b5d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f91db7c0c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f91db7c28d7 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f91d4423d79 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x7f91e22c6b48 in QThreadPrivate::start (arg=0x23649a0) at
thread/qthread_unix.cpp:368
#5  0x7f91de7c86ba in start_thread (arg=0x7f91d1ecb700) at
pthread_create.c:333
#6  0x7f91e776382d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f91d4a568c0 (LWP 31556)):
[KCrash Handler]
#6  0x7f91e24c5fee in QObjectPrivate::setParent_helper (this=0x18fb9e1,
o=o@entry=0x0) at kernel/qobject.cpp:1978
#7  0x7f91e24c6b79 in QObject::setParent (this=,
parent=parent@entry=0x0) at kernel/qobject.cpp:1957
#8  0x7f91e378aa32 in KCompositeJob::removeSubjob (this=,
job=0x2c28930) at /workspace/build/src/lib/jobs/kcompositejob.cpp:71
#9  0x7f91e57f26f4 in KIO::CopyJobPrivate::slotResultErrorCopyingFiles
(this=this@entry=0x2c02b50, job=job@entry=0x2c28930) at
/workspace/build/src/core/copyjob.cpp:1445
#10 0x7f91e57f2d84 in KIO::CopyJobPrivate::slotResultCopyingFiles
(this=this@entry=0x2c02b50, job=job@entry=0x2c28930) at
/workspace/build/src/core/copyjob.cpp:1313
#11 0x7f91e57f4d57 in KIO::CopyJob::slotResult (this=0x2c092f0,
job=0x2c28930) at /workspace/build/src/core/copyjob.cpp:2114
#12 0x7f91e24bee89 in QMetaObject::activate (sender=sender@entry=0x2c28930,
signalOffset=, local_signal_index=local_signal_index@entry=3,
argv=argv@entry=0x7fff25f37b80) at k

[kio-extras] [Bug 376344] cant write to smb shares which has write access

[Sergey]

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

Sergey  changed:

   What|Removed |Added

 CC||rion...@gmail.com

--- Comment #22 from Sergey  ---
Just faced the same bug, but workaround from @tempel.julian does not work well.
I finally have write access to my Windows share (requires auth) but if I create
with dolphin a subdirectory I can't open it. It requires authentication again
but this time the same login/password do not work anymore.

Another glitch. If I don't use *:* for auth but just smb://host/share and login
via popup dialog, then I create a subdirctory in cifs mounted directory for the
same share,  I can open the new subdirectory with Dolphin, but again no write
access inside. But if I write a few files from console (the same mounted cifs)
to the subdirectory I magically obtain the write access from Dolphin.

I also tested with "mount cifs" and it works in all circumstances where dolphin
fails.

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

[plasmashell] [Bug 378700] There is gap on the right of every invoked tray icon

[bugzilla_noreply]

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

n...@mail.ticket-please.ga changed:

   What|Removed |Added

 CC||n...@mail.ticket-please.ga

--- Comment #2 from n...@mail.ticket-please.ga ---
bump! just booted with neon dev unstable which is going with KF 5.35 and gap is
still there.

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

[kdeconnect] [Bug 368438] KDE Connect does not communicate while running in background on phone

[Theresa]

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

--- Comment #18 from Theresa  ---
I can confirm that the problem is fixed with Android 7.x
Alas my phone (Oneplus One) only has Android 6.
Is there any chance of fixing this also for Android 6 devices?

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

[plasmashell] [Bug 379826] New: Plasma Crash after closing firefox window - segmentation fault

[Thomas]

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

Bug ID: 379826
   Summary: Plasma Crash after closing firefox window -
segmentation fault
   Product: plasmashell
   Version: 5.9.5
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: tho...@elsensohn.ch
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.9.5)

Qt Version: 5.8.0
Frameworks Version: 5.33.0
Operating System: Linux 4.10.13-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed:
I tried to close ocular window and closed the firefox window. Then I tried to
close the other window but was already crashed. Restored after some seconds.

- Unusual behavior I noticed:
The menubar was wrong.

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 0x7f300d93f800 (LWP 721))]

Thread 19 (Thread 0x7eeef7fff700 (LWP 7132)):
#0  0x7f30065a2756 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f30076e858b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f30076e14d3 in QSemaphore::acquire(int) () at
/usr/lib/libQt5Core.so.5
#3  0x7eeefd65c37c in  () at
/usr/lib/qt/plugins/texttospeech/libqttexttospeech_flite.so
#4  0x7f30076e76d8 in  () at /usr/lib/libQt5Core.so.5
#5  0x7f300659c2e7 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f3006ffa54f in clone () at /usr/lib/libc.so.6

Thread 18 (Thread 0x7f2f14e12700 (LWP 1976)):
#0  0x7f3007914f21 in QTimerInfoList::repairTimersIfNeeded() () at
/usr/lib/libQt5Core.so.5
#1  0x7f3007914fb3 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib/libQt5Core.so.5
#2  0x7f300791666e in  () at /usr/lib/libQt5Core.so.5
#3  0x7f3001dc6e8d in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#4  0x7f3001dc78db in  () at /usr/lib/libglib-2.0.so.0
#5  0x7f3001dc7acc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#6  0x7f300791709b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#7  0x7f30078c08ca in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#8  0x7f30076e2a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#9  0x7f300a81b025 in  () at /usr/lib/libQt5Qml.so.5
#10 0x7f30076e76d8 in  () at /usr/lib/libQt5Core.so.5
#11 0x7f300659c2e7 in start_thread () at /usr/lib/libpthread.so.0
#12 0x7f3006ffa54f in clone () at /usr/lib/libc.so.6

Thread 17 (Thread 0x7f2f164b1700 (LWP 1295)):
#0  0x7f3001dc6d38 in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#1  0x7f3001dc78db in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f3001dc7acc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f300791709b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f30078c08ca in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f30076e2a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f30076e76d8 in  () at /usr/lib/libQt5Core.so.5
#7  0x7f300659c2e7 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f3006ffa54f in clone () at /usr/lib/libc.so.6

Thread 16 (Thread 0x7f2f16ffd700 (LWP 1225)):
#0  0x7f30065a2756 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f30076e858b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f2f4f0d81d0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7f2f4f0dc9d8 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7f2f4f0d7263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7f2f4f0dca32 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#6  0x7f2f4f0d7263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#7  0x7f2f4f0dca32 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#8  0x7f2f4f0d7263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#9  0x7f2f4f0da249 in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#10 0x7f30076e76d8 in  () at /usr/lib/libQt5Core.so.5
#11 0x7f300659c2e7 in start_thread () at /usr/lib/libpthread.so.0
#12 0x7f3006ffa54f in clone () at /usr/lib/libc.so.6

Thread 15 (Thread 0x7f2f177fe700 (LWP 1224)):
#0  0x7f30065a2756 in pthread_cond_wait@@GLIBC_2.3.2 () at

[digikam] [Bug 379825] Conversion of DNG files to DNG with metadata loss - maybe add warning

[bugzilla_noreply]

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

vas...@gmx.net changed:

   What|Removed |Added

   Severity|normal  |wishlist

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

[digikam] [Bug 379825] New: Conversion of DNG files to DNG with metadata loss - maybe add warning

[bugzilla_noreply]

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

Bug ID: 379825
   Summary: Conversion of DNG files to DNG with metadata loss -
maybe add warning
   Product: digikam
   Version: 5.5.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Import
  Assignee: digikam-de...@kde.org
  Reporter: vas...@gmx.net
  Target Milestone: ---

I own a Pentax camera which is capable of producing DNG-Files. Unfortunately i
had left the "convert raw files to dng"-option enabled when importing which
converted all my DNG files to DNG files but deleting Makernotes in the process
so that all the new DNGs now have missing lens information.
I think a warning when trying to convert from DNG to DNG would be a good idea
(maybe mentioning the possible loss of metadata) as this took me quite some
time to track down (at first i thought that the camera did no longer encode the
lens used, then i realised that the information was there in the jpeg files but
not the dng ones and finally i realised that i had left the conversion option
enabled).

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

[systemsettings] [Bug 379824] New: Crash after closing settings

[DecentM]

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

Bug ID: 379824
   Summary: Crash after closing settings
   Product: systemsettings
   Version: 5.9.5
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: barnaba...@gmail.com
  Target Milestone: ---

Application: systemsettings5 (5.9.5)

Qt Version: 5.8.0
Frameworks Version: 5.33.0
Operating System: Linux 4.10.15-1-MANJARO x86_64
Distribution: "Manjaro Linux"

-- Information about the crash:
- What I was doing when the application crashed:
I just closed the system settings after turning desktop compositing on

- Unusual behavior I noticed:
Logging in fresh after installing the latest updates, Kwin crashed, disabling
compositing. After enabling it back and closing the settings app, this crash
happened.

-- Backtrace:
Application: Rendszerbeállítások (systemsettings5), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fa78784b500 (LWP 1933))]

Thread 3 (Thread 0x7fa758bc8700 (LWP 1984)):
#0  0x7fa77d6ac1c9 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0
#1  0x7fa77d66699b in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fa77d666acc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7fa783e9d09b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7fa783e468ca in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7fa783c68a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7fa781f65025 in  () at /usr/lib/libQt5Qml.so.5
#7  0x7fa783c6d6d8 in  () at /usr/lib/libQt5Core.so.5
#8  0x7fa77f5ae2e7 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7fa78358054f in clone () at /usr/lib/libc.so.6

Thread 2 (Thread 0x7fa76c1f0700 (LWP 1936)):
#0  0x7fa78357667d in poll () at /usr/lib/libc.so.6
#1  0x7fa77d6669b6 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fa77d666acc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7fa783e9d09b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7fa783e468ca in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7fa783c68a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7fa7847b4125 in  () at /usr/lib/libQt5DBus.so.5
#7  0x7fa783c6d6d8 in  () at /usr/lib/libQt5Core.so.5
#8  0x7fa77f5ae2e7 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7fa78358054f in clone () at /usr/lib/libc.so.6

Thread 1 (Thread 0x7fa78784b500 (LWP 1933)):
[KCrash Handler]
#6  0x09841400 in  ()
#7  0x7fa76f06eba6 in  () at /usr/lib/libKF5Notifications.so.5
#8  0x7fa76f06ec39 in  () at /usr/lib/libKF5Notifications.so.5
#9  0x7fa783e72441 in QObjectPrivate::deleteChildren() () at
/usr/lib/libQt5Core.so.5
#10 0x7fa783e7bd9f in QObject::~QObject() () at /usr/lib/libQt5Core.so.5
#11 0x7fa76f040ea9 in  () at /usr/lib/libKF5Notifications.so.5
#12 0x7fa7834ca6c0 in __run_exit_handlers () at /usr/lib/libc.so.6
#13 0x7fa7834ca71a in  () at /usr/lib/libc.so.6
#14 0x7fa7834b4518 in __libc_start_main () at /usr/lib/libc.so.6
#15 0x0040c33a in _start ()

Reported using DrKonqi

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

[qca] [Bug 379810] qca compilation fails with openssl 1.1

[Rex Dieter]

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

Rex Dieter  changed:

   What|Removed |Added

 CC||rdie...@math.unl.edu

--- Comment #1 from Rex Dieter  ---
That's ok, Qt5 itself doesn't support openssl 1.1 yet either, which is an
important prerequisite.

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

[gwenview] [Bug 379823] New: Message to cut and delete when opening image

[jose caynan]

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

Bug ID: 379823
   Summary: Message to cut and delete when opening image
   Product: gwenview
   Version: unspecified
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: caynannu...@gmail.com
CC: myr...@kde.org
  Target Milestone: ---

After updating my system LinuxMint 18.1 x64 KDE: 4.14.22,  kde4-config:
1.0,kde4-config: 1.0

 Every time I click on an image a message appears saying "there is a command to
both cut and delete the image", when I ignore the message nothing happens to
the file.

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

[ktouchpadenabler] [Bug 379785] palm rejection

[Albert Astals Cid]

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

Albert Astals Cid  changed:

   What|Removed |Added

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

--- Comment #1 from Albert Astals Cid  ---
only think that ktouchpadenabler is listen to the touchpad enable key on your
laptop and enable/disable it.

Anything else is out of scope.

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

[Breeze] [Bug 379790] MDI SubWindows are frozen (non-responsive) with Breeze and Oxygen

[Tim E . Real]

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

--- Comment #5 from Tim E. Real  ---
Wow! When the attached UI file is opened, it is not only the
 MDI sub windows that are affected - it is the ENTIRE QMainWindow
 containing the QMDIArea.
In fact, I am unable to even move the window around in Qt5Designer !
I can place items on the form, but I cannot select anything afterwards.
The rest of Qt5Designer is OK, of course.

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

[dolphin] [Bug 379314] Crash when restoring activity

[Jaime Torres]

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

Jaime Torres  changed:

   What|Removed |Added

 CC||jtam...@gmail.com

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

[dolphin] [Bug 379314] Crash when restoring activity

[Jaime Torres]

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

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

dolphin (17.04.0) using Qt 5.7.1

- What I was doing when the application crashed:

Just logged in and restoring the previous session.

-- Backtrace (Reduced):
#6  DolphinViewContainer::setActive (this=0x0, active=active@entry=true) at
/usr/src/debug/dolphin-17.04.0/src/dolphinviewcontainer.cpp:208
#7  0x7f1c48bd2b72 in DolphinTabPage::restoreState (this=0x2daced0,
state=...) at /usr/src/debug/dolphin-17.04.0/src/dolphintabpage.cpp:239
#8  0x7f1c48bd4b35 in DolphinTabWidget::readProperties (this=0x268abd0,
group=...) at /usr/src/debug/dolphin-17.04.0/src/dolphintabwidget.cpp:90
#9  0x7f1c461224a0 in KMainWindow::readPropertiesInternal(KConfig*, int) ()
from /usr/lib64/libKF5XmlGui.so.5
#10 0x7f1c46122502 in KMainWindow::restore(int, bool) () from
/usr/lib64/libKF5XmlGui.so.5

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

[frameworks-plasma] [Bug 355410] Scroll speed of QML scroll area is too slow with the xf86-input-libinput driver

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com

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

[plasmashell] [Bug 366451] "display scaling" on hidpi screen results in poor font quality

[rindeal]

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

--- Comment #17 from Jan Chren (rindeal)  
---
Created attachment 105535
  --> https://bugs.kde.org/attachment.cgi?id=105535&action=edit
logout overlay; scaling=1.5

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

[Breeze] [Bug 379790] MDI SubWindows are frozen (non-responsive) with Breeze and Oxygen

[Tim E . Real]

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

--- Comment #4 from Tim E. Real  ---
Wow. I never tried saving/re-opening a test-case UI file before.
This fresh suse installation is on Breeze by default.
So the attached UI file's MDI sub windows are frozen even without
 previewing the form. They are frozen right in the Qt5Designer editor !
Qt Version 5.7.1

As mentioned, also observed on KUbuntu 6.0.4 LTS, worse it happens even 
 without setting any stylesheet on the QMDIArea. (The supplied UI file
 has a stylesheet set on the QMDIArea.)
Also observed on another, older PC running same KUbuntu 6.0.4 LTS.
Others in our group have also reported the problem.

Only commonality I can think of, at least in my setup, is the 
 Nouveau nVidia drivers. But I think I tried an ATI card at one point.

Everything is fine if the attached UI file is opened in Qt4Designer!
Indeed, our Qt app was fine in Qt4 (and Qt3, Qt2, Qt1, he he.)

Thanks.

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

[plasmashell] [Bug 366451] "display scaling" on hidpi screen results in poor font quality

[rindeal]

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

Jan Chren (rindeal)  changed:

   What|Removed |Added

 CC||dev.rindeal+bugs.kde.org@gm
   ||ail.com

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

[systemsettings] [Bug 379822] New: Multimedia icon confusing for new users

[bugzilla_noreply]

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

Bug ID: 379822
   Summary: Multimedia icon confusing for new users
   Product: systemsettings
   Version: 5.9.5
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: ber...@codewiz.org
  Target Milestone: ---

Warning, UX bug. Feel free to close as WONTFIX if you disagree.

I recently observed a new KDE user browse through the main Systemsettings
window in search for the sound configuration KCM. This user missed the
Multimedia icon because:

1) "This icon looks like a monitor, but I wanted to configure sound so I was
looking for a speaker"

2) No mental association between Sound / Audio the abstract concept of
Multimedia

3) Multimedia appears way down in the window


Here are some (personal) ideas to give better cues to the user:

1) Split the Sound kcm and promote it to a top-level entry in the
systemsettings main window

2) Change the Multimedia icon to look more distinct from a display, possibly
including a speaker logo (either alone, or besides a film, a "play button" or a
clapperboard).

3) Rename Multimedia to "Sound and Video"

4) Move the Hardware group up, at least before Network and possibly also before
Personalization

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

[kcalc] [Bug 379821] Exponent button (x*10y) only works with numbers entered immediately previously

[Jonathan Cottrill]

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

Jonathan Cottrill  changed:

   What|Removed |Added

 CC||kde-bugzilla@jonathancottri
   ||ll.net

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

[kcalc] [Bug 379821] New: Exponent button (x*10y) only works with numbers entered immediately previously

[Jonathan Cottrill]

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

Bug ID: 379821
   Summary: Exponent button (x*10y) only works with numbers
entered immediately previously
   Product: kcalc
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: ete...@alum.rit.edu
  Reporter: kde-bugzi...@jonathancottrill.net
  Target Milestone: ---

KCalc version 17.04.0, with KDE Frameworks 5.32.0 and Qt 5.7.1.

If you enter a number with the keyboard or application buttons, the Exponent
(x*10y) button works appropriately; example:

1. Enter 2 in KCalc
2. Press x*10y button
3. Observer 2e0 in display

However, if the current number was not entered immediately previously, it is
"lost" (treated as zero).

Issue #1: Pasted value

1. Copy single character 2 to clipboard
2. Paste into KCalc
3. Press x*10y button
4. Observe result is 0e0, *NOT* 2e0, as expected

Issue #2: Result of prior calculation (perhaps arguable, as other calculators
treat this case in different ways)

1. Add 1 and 1
2. Observe result is 2
3. Press x*10y button
4. Observe result is 0e0, *NOT* 2e0, as expected

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

[Breeze] [Bug 379790] MDI SubWindows are frozen (non-responsive) with Breeze and Oxygen

[Tim E . Real]

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

--- Comment #3 from Tim E. Real  ---
Created attachment 105534
  --> https://bugs.kde.org/attachment.cgi?id=105534&action=edit
Frozen MDI test UI file 1

Open in Qt5Designer or Creator. The MDI sub windows are frozen
 in Breeze or Oxygen.

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

[Akonadi] [Bug 379548] IMAP resource crashes on configure operation

[Luca Giambonini]

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

--- Comment #9 from Luca Giambonini  ---
For me is fixed with:
https://cgit.kde.org/kdepim-runtime.git/patch/?id=e8b131fe179f474af9de12f1289ea70cd99e90e4

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

[KScreen] [Bug 379770] Scaled UI settings will prevent access to rescale UI or apply

[bugzilla_noreply]

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

--- Comment #4 from jey.and@gmail.com ---
Created attachment 105533
  --> https://bugs.kde.org/attachment.cgi?id=105533&action=edit
Screenshot of display cut-off

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

[kde] [Bug 379820] KDE File chooser items names shown in multiple lines when sort isn't set to 'by name'

[DeMus]

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

--- Comment #2 from DeMus  ---
P.s.
KDE Plasma 5.9.5
KDE Frameworks 5.33.0
Qt version 5.8.0

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

[kde] [Bug 379820] KDE File chooser items names shown in multiple lines when sort isn't set to 'by name'

[DeMus]

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

DeMus  changed:

   What|Removed |Added

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

--- Comment #1 from DeMus  ---
Same thing as what pmarget...@gmail.com writes happens to me in my Manjaro
17.01 KDE. Only when the sort key is set to "name" things are okay, if not file
and folder names are chopped after second character.

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

[Akonadi] [Bug 379548] IMAP resource crashes on configure operation

[Sebastian Kuhne]

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

Sebastian Kuhne  changed:

   What|Removed |Added

 CC||sebastiankuhne1@googlemail.
   ||com

--- Comment #8 from Sebastian Kuhne  ---
I am on openSUSE Tumbleweed (latest update), with KDE applications 17.04. I am
facing the same issue. Once generated an IMAP resource in KDE's Kontact it
can't be configured properly. The same happens using aconadiconsole (Agents -->
IMAP resource --> Configure --> Configure Natively) - no window opens for
configuration. The IMAP resource; however, is a standard Google mail account.

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

[k3b] [Bug 379448] There is no information

[Cristian Aravena Romero]

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

--- Comment #20 from Cristian Aravena Romero  ---
== New packages for ubuntu [0]zesty & ubuntu [0]artful ==
[0] https://bugs.launchpad.net/bugs/1689641
[1] https://bugs.launchpad.net/bugs/1690595

"Good idea, it doesn't hurt to be ahead of the game for once... The packages
for artful have been build and published.

Cheers,
 Rok"

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

[konqueror] [Bug 203119] keyboard shortcuts: user defined shortcuts are vanishing (are auto deleted)

[kranthi]

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

kranthi  changed:

   What|Removed |Added

 CC||kranthi.t2...@gmail.com

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

[gwenview] [Bug 202414] allow to hide status bar and toolbar

[Valerio Pilo]

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

--- Comment #20 from Valerio Pilo  ---
I've submitted https://phabricator.kde.org/D5854 (to fix the statusbar
persistence) and https://phabricator.kde.org/D5855 (to add the toolbar menu
entry).

I've used standard KDE Actions, so they will end up in the Settings menu like
in all other apps. Perhaps we should move the Sidebar menu entry there as well,
for the sake of consistency.

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

[kde] [Bug 379820] KDE File chooser items names shown in multiple lines when sort isn't set to 'by name'

[bugzilla_noreply]

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

pmarget...@gmail.com changed:

   What|Removed |Added

Summary|KDE File chooser items  |KDE File chooser items
   |shown in multiple lines |names shown in multiple
   |when sort isn't set to 'by  |lines when sort isn't set
   |name'   |to 'by name'

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

[Akonadi] [Bug 379548] IMAP resource crashes on configure operation

[Luca Giambonini]

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

Luca Giambonini  changed:

   What|Removed |Added

 CC||luc...@bluewin.ch

--- Comment #7 from Luca Giambonini  ---
Created attachment 105532
  --> https://bugs.kde.org/attachment.cgi?id=105532&action=edit
journalctl crash log with debug symbols

backstrace journal -f with debug symbols

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

[kde] [Bug 379820] New: KDE File chooser items shown in multiple lines when sort isn't set to 'by name'

[bugzilla_noreply]

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

Bug ID: 379820
   Summary: KDE File chooser items shown in multiple lines when
sort isn't set to 'by name'
   Product: kde
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: pmarget...@gmail.com
  Target Milestone: ---

Created attachment 105531
  --> https://bugs.kde.org/attachment.cgi?id=105531&action=edit
Sorting is set do 'by date' and 'descending' is enabled. Folder names are
chopped up into multiple lines.

KDE File chooser (open or save as dialogues) items shown in multiple lines when
sort isn't set to 'by name'.
Using sort 'by type', 'by date', 'by size' results in content being chopped up
into multiple rows. Icon size must be set to something other than smallest to
reproduce this bug.
More details and a discussion on this bug can be found here:
https://forum.manjaro.org/t/kde-open-save-dialogue-bug-item-names-multi-lined/23706

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

[krusader] [Bug 321863] Krusader crasher during synchronization of directory with tons of sub-dirs

[Alex Bikadorov]

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

Alex Bikadorov  changed:

   What|Removed |Added

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

--- Comment #3 from Alex Bikadorov  ---
Was the "Compare by content" setting checked? If so, does it crash when
unchecked?

(I know this is an old report.)

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

[akregator] [Bug 338908] KISS feed sync (brainstorming)

[James Cain]

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

James Cain  changed:

   What|Removed |Added

 CC||dequ...@mykolab.com

--- Comment #1 from James Cain  ---
I agree that akregator needs a syncing-service, but I'd rather see it built-in.
In other words, not using a 3rd party service. It would just need a back-end
and a front-end, similar to how Quassel handles syncing for IRC. 

The back-end could be on a user's main PC, a server on the LAN, a Kodi or Plex
plugin, reside within OwnCloud, or via a hosted service like Digital Ocean or
maybe a service that KDE could provide. 

I could see potentially many great enterprise uses for this as well, such as
syncing Intranet news and information within a company or school, etc. If
anyone thinks this may have merit, I could spin-off a separate bug report.

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

[kwin] [Bug 379819] New: [Wayland] QT UI element overflow in systemsettings Display section

[Rajdeep Nanua]

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

Bug ID: 379819
   Summary: [Wayland] QT UI element overflow in systemsettings
Display section
   Product: kwin
   Version: 5.9.5
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: rajdeepna...@gmail.com
  Target Milestone: ---

Created attachment 105530
  --> https://bugs.kde.org/attachment.cgi?id=105530&action=edit
Overflown UI in systemsettings Display tab

Steps to reproduce:
1. Go to systemsettings -> Display and Monitor -> Displays
2. Resize the window to the smallest size possible
3. Scroll down. 

The Display layout section will overflow outside the application window, as
seen in attached screenshot. Also, moving the window around causes a trail of
overflown UI to appear, which I could not capture in a screenshot.

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

[kate] [Bug 379818] Kate, Kwrite seems to not apply acls rules

[jcdole]

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

jcdole  changed:

   What|Removed |Added

   Platform|Other   |openSUSE RPMs
   Severity|normal  |grave
Version|unspecified |16.08

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

[kate] [Bug 379818] New: Kate, Kwrite seems to not apply acls rules

[jcdole]

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

Bug ID: 379818
   Summary: Kate, Kwrite seems to not apply acls rules
   Product: kate
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: jcd...@free.fr
  Target Milestone: ---

Created attachment 105529
  --> https://bugs.kde.org/attachment.cgi?id=105529&action=edit
screenshots of acl command and other.

Initial conditions :
- OS : Leap 42.2
- Kernel : 4.4.62-18.6-default - x86_64
- File system : ext4 and xfs
UUID=857c3295-5944-4593-82e2-bb90dede4312 / ext4  noatime,acl,user_xattr   1 1
UUID=6173a3df-4407-427c-b01a-c2d664471fc8 /data3_dwnld_pub  xfs  defaults  1 2
- ACL : 2.2.52-8.55
- KDE : Frameworks 5.26.0 - Qt 5.6.1 (built against 5.6.1)
- KATE : Version 16.08.2 

Goal : In folders defined as "PUBLIC" for users in group "publicuser', any
users can do anythings but cannot delete objects they do not own.

1st Step : Creation of initial group, user and folders
Create group publicuser
Create user publicuser (no login user), user_test1, user_test2
Add publicuser, user_test1, user_test2 to group publicuser
Create a new folder : 
   mkdir -p /d_pub_folder
   chown   publicuser:publicuser /d_pub_folder 
Create sub-folder for each regular user
   mkdir -p /d_pub_folder/user_test1
   chown user_test1:publicuser /d_pub_folder/user_test1   
   mkdir -p /d_pub_folder/user_test2
   chown user_test2:publicuser /d_pub_folder/user_test2
Set properties on new folders
   chmod -R 770 /d_pub_folder
   chmod -R g+s /d_pub_folder
   chmod -R +t  /d_pub_folder
Set ACL on new folders
   #set user to rwx, group to ---, group publicuser to rwx,other to ---
   setfacl -R -m u::rwx,g::---,g:publicuser:rwx,o:---  /d_pub_folder
   #set default : user to rwx, group to ---, group publicuser to rwx,other to
---
   setfacl -R -d -m u::rwx,g::---,g:publicuser:rwx,o:---  /d_pub_folder

2nd Step : Files creation
Create new files owned by each user in their respective folder  
   su to user_test1
   echo "Create by user_test1 in user_test1's folder" >
/d_pub_folder/user_test1/testfile_1.txt
   su to user_test2
   echo "Create by user_test2 in user_test2's folder" >
/d_pub_folder/user_test2/testfile_2.txt
Create new files own by user_test2 in user_test2's folder  
   echo "Create by user_test2 in user_test1's folder" >
/d_pub_folder/user_test1/testfile_4.txt

3rd Step : ACL Check from a "public" folder /d_pub_folder/
1°) OK : any user can create a file in it's own folder
2°) OK : any user can create a file in folder owned by others
3°) OK : any user can modify a file they owned in folder owned by others
4°) OK : any user cannot delete a file they do not owned any where
5°) OK : any user can modify a file they do not owned using vi in a terminal
emulator (Konsole)

What does not work
USING KATE or KWRITE
6°) FAILED : any user cannot modify a file they do not owned. Write is denied

Any help is welcome.

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

[kio-extras] [Bug 379817] New: Behaviour change: JPEG image preview scaled to widget size

[Alex Bikadorov]

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

Bug ID: 379817
   Summary: Behaviour change: JPEG image preview scaled to widget
size
   Product: kio-extras
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: default
  Assignee: plasma-de...@kde.org
  Reporter: alex.bikado...@kdemail.net
  Target Milestone: ---

Created attachment 105528
  --> https://bugs.kde.org/attachment.cgi?id=105528&action=edit
Dolphin JPEG image preview

Preview images in KImageFilePreview for JPEG files are always scaled to the
widget size - no matter how how small the jpeg is. PNGs are not scaled. Dolphin
and Krusader are affected. See screenshot.

I tracked it down to thumbnail/jpegcreator and its maybe caused by
https://git.reviewboard.kde.org/r/129851/

Version:
KDE Frameworks 5.33.0
kio-extras 17.04.0

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

[kmail2] [Bug 379816] New: Cannot edit IMAP resources after upgrade to 5.5.0

[Guo Yunhe]

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

Bug ID: 379816
   Summary: Cannot edit IMAP resources after upgrade to 5.5.0
   Product: kmail2
   Version: 5.5.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: guoyunhebr...@gmail.com
  Target Milestone: ---

I have two Gmail accounts in KMail. After upgrading to 5.5.0 today, I was asked
to provide Google account passwords. I did. After that, I found that I cannot
edit IMAP resources in KMail Settings. When I click the modify button, it said
"the resource is broken" and IMAP status is "cannot start".

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

[okular] [Bug 379815] New: random crash when changing system audio volume with media keys

[Keziolio]

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

Bug ID: 379815
   Summary: random crash when changing system audio volume with
media keys
   Product: okular
   Version: 1.1.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: keziolio...@gmail.com
  Target Milestone: ---

Okular crashed randomly when increasing the volume with the keyboard media
keys, I was not able to reproduce

Arch linux with kde-unstable, okular 1.1.1, everything is up to date


mag 14 16:24:05 desktop systemd-coredump[9116]: Process 15413 (okular) of user
1000 dumped core.

Stack trace of thread 15413:
#0  0x7f879a206a10 raise (libc.so.6)
#1  0x7f879a20813a abort (libc.so.6)
#2  0x7f87856a7212 pa_fdsem_post (libpulsecommon-10.0.so)
#3  0x7f87856bf2ea pa_srbchannel_write (libpulsecommon-10.0.so)
#4  0x7f87856bd4fd n/a (libpulsecommon-10.0.so)
#5  0x7f87856be668 n/a (libpulsecommon-10.0.so)
#6  0x7f87856be989 n/a (libpulsecommon-10.0.so)
#7  0x7f87856bf20a n/a (libpulsecommon-10.0.so)
#8  0x7f8785b07f36 n/a (libpulse-mainloop-glib.so.0)
#9  0x7f87950097b7 g_main_context_dispatch (libglib-2.0.so.0)
#10 0x7f8795009a20 n/a (libglib-2.0.so.0)
#11 0x7f8795009acc g_main_context_iteration (libglib-2.0.so.0)
#12 0x7f879abdc07f
_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE
(libQt5Core.so.5)
#13 0x7f879ab858ca _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE
(libQt5Core.so.5)
#14 0x7f879ab8de14 _ZN16QCoreApplication4execEv (libQt5Core.so.5)
#15 0x0040b97d n/a (okular)
#16 0x7f879a1f3511 __libc_start_main (libc.so.6)
#17 0x0040d24a _start (okular)

Stack trace of thread 15415:
#0  0x7f879a2b567d poll (libc.so.6)
#1  0x7f87950099b6 n/a (libglib-2.0.so.0)
#2  0x7f8795009acc g_main_context_iteration (libglib-2.0.so.0)
#3  0x7f879abdc07f
_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE
(libQt5Core.so.5)
#4  0x7f879ab858ca _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE
(libQt5Core.so.5)
#5  0x7f879a9a7a73 _ZN7QThread4execEv (libQt5Core.so.5)
#6  0x7f879aff1125 n/a (libQt5DBus.so.5)
#7  0x7f879a9ac6d8 n/a (libQt5Core.so.5)
#8  0x7f8796f512e7 start_thread (libpthread.so.0)
#9  0x7f879a2bf54f __clone (libc.so.6)

Stack trace of thread 15418:
#0  0x7f8796f57756 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1  0x7f87796070cb n/a (radeonsi_dri.so)
#2  0x7f8779606df7 n/a (radeonsi_dri.so)
#3  0x7f8796f512e7 start_thread (libpthread.so.0)
#4  0x7f879a2bf54f __clone (libc.so.6)

Stack trace of thread 15414:
#0  0x7f879a2b567d poll (libc.so.6)
#1  0x7f8797d048e0 n/a (libxcb.so.1)
#2  0x7f8797d06679 xcb_wait_for_event (libxcb.so.1)
#3  0x7f878f642239 n/a (libQt5XcbQpa.so.5)
#4  0x7f879a9ac6d8 n/a (libQt5Core.so.5)
#5  0x7f8796f512e7 start_thread (libpthread.so.0)
#6  0x7f879a2bf54f __clone (libc.so.6)

Stack trace of thread 15416:
#0  0x7f8796f57756 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1  0x7f87796070cb n/a (radeonsi_dri.so)
#2  0x7f8779606df7 n/a (radeonsi_dri.so)
#3  0x7f8796f512e7 start_thread (libpthread.so.0)
#4  0x7f879a2bf54f __clone (libc.so.6)

Stack trace of thread 15419:
#0  0x7f8796f57756 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1  0x7f87796070cb n/a (radeonsi_dri.so)
#2  0x7f8779606df7 n/a (radeonsi_dri.so)
#3  0x7f8796f512e7 start_thread (libpthread.so.0)
#4  0x7f879a2bf54f __clone (libc.so.6)

Stack trace of thread 15417:
#0  0x7f8796f57756 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1  0x7f87796070cb n/a (radeonsi_dri.so)
#2  0x7f8779606df7 n/a (radeonsi_dri.so)
#3  0x7f8796f512e7 start_thread (libpthread.so.0)
#4  0x7f879a2bf54f __clone (libc.so.6)

Stack trace of thread 15420:
#0  0x7f8796f57756 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1  0x7f87796070cb n/a (radeonsi_dri.so)
#2  0x7f8779606df7 n/a (radeonsi_dri.so)
#3  0x7f8796f512e7 start_thread (libpthread.so.0)
#4  0x7f879a2bf54f __clone (libc.so.6)

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

[kmail2] [Bug 379791] Confusing Account Wizard dialog

[Burkhard Lueck]

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

Burkhard Lueck  changed:

   What|Removed |Added

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

--- Comment #3 from Burkhard Lueck  ---
You did not provide your version of KMail (kmail -v).
Anyway master and stable version have a different dialog, therefore your report
is invalid

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

[valgrind] [Bug 371503] disInstr(arm64): unhandled instruction 0xF89F0000 (prfum)

[Julian Seward]

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

Julian Seward  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #3 from Julian Seward  ---
Fixed, vex r3369.

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

[kmail2] [Bug 379805] Kmail ne s'ouvre pas erreur Akoni

[Daniel]

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

--- Comment #3 from Daniel  ---
Ré BonjourLe bouton "Détail" ne réagit pas j'ai oublié de le mentionner dans ma
réponse.Cordialement D. AUQUIER 


Envoyé depuis mon appareil Samsung

 Message d'origine 
De : Laurent Montel  
Date : 2017/05/14  14:32  (GMT+01:00) 
À : hcolsou...@gmail.com 
Objet : [kmail2] [Bug 379805] Kmail ne s'ouvre pas erreur Akoni 

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

Laurent Montel  changed:

   What    |Removed |Added

 CC|    |mon...@kde.org

--- Comment #1 from Laurent Montel  ---
Hello
In french "Salut, les bugs reports se font en anglais par défaut mais comme je
suis français ça va" :)
Le bouton détail de donne des infos ?
Est ce que tu as des erreurs en console ? Est ce que Akonadi est bien installé
sur ta machine ?"

I ask more info about errors.

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

[kwin] [Bug 379814] New: Black Screen on Resuming from Suspend to RAM with Nvidia Proprietary Driver

[bugzilla_noreply]

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

Bug ID: 379814
   Summary: Black Screen on Resuming from Suspend to RAM with
Nvidia Proprietary Driver
   Product: kwin
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: jonespanic...@gmail.com
  Target Milestone: ---

I get a black screen on resuming from suspend to RAM. This happens every single
time, but only when using Nvidia proprietary driver.

Cannot go to tty with Ctrl-Alt-Fn keys. Nothing works. Just black screen. Not
even mouse pointer.


I am not sure if this is to be fixed by Nvidia guys or KDE.

-Linux Mint 18.1 KDE version, Nvidia 930MX graphics, driver used Nvidia
375/378/381.

OpenGL vendor string:   NVIDIA Corporation
OpenGL renderer string: GeForce 930MX/PCIe/SSE2
OpenGL version string:  3.1.0 NVIDIA 381.22
OpenGL shading language version string: 1.40 NVIDIA via Cg compiler
Driver: NVIDIA
Driver version: 381.22
GPU class:  Unknown
OpenGL version: 3.1
GLSL version:   1.40
X server version:   1.18.4
Linux kernel version:   4.4
Requires strict binding:no
GLSL shaders:   yes
Texture NPOT support:   yes
Virtual Machine:no

I'm fed up of this issue, I can give you any diagnostic info needed, just let
me know what is needed...

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

[frameworks-kio] [Bug 356791] KDE Applications won't show contents of nfs mount (automount)

[Geert Janssens]

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

Geert Janssens  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|UNCONFIRMED |RESOLVED

--- Comment #6 from Geert Janssens  ---
I have resolved this issue by exporting directories outside of the /home
directory on the server.

It seems like there is some security feature interfering with exporting
directories under /home. I never was able to figure out whether this is
something in nfs or selinux or whatever.

So works for me now.

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

[kwallet-pam] [Bug 356785] kwallet4 still asks for password although pam-kwallet should open both kwallet4 and kwallet5

[Geert Janssens]

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

Geert Janssens  changed:

   What|Removed |Added

 Resolution|--- |UNMAINTAINED
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Geert Janssens  ---
Now that most of the applications I use have switched to kf5, I no longer have
a use case to test this. And since no other users have confirmed this, I'll
just close this bug again. I'm hesitating on the resolution reason as none
really fit the bill. I'll choose "Unmaintained". If that's a wrong choice, feel
free to correct it.

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

[digikam] [Bug 379751] I18N_ARGUMENT_MISSING in Edit Metadata

[bugzilla_noreply]

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

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

   What|Removed |Added

 CC||caulier.gil...@gmail.com

--- Comment #3 from caulier.gil...@gmail.com ---
no. It's just a translation format problem...

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

[kmail2] [Bug 379805] Kmail ne s'ouvre pas erreur Akoni

[Daniel]

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

--- Comment #2 from Daniel  ---
Bonjour

Merci pour prendre un peu de temps pour me répondre.

C'est justement ce que je me pose comme question.

Je viens juste de faire démarrer thunderbird et ainsi j'ai pu voir le mail.

Que dois-je faire pour remonter les messages d'erreur?

D. Auquier

je viens de commencer à installer Ubuntu*Mate après avoir lu pas mal de 
pages d'info je fais le grand saut vers ce nouvel univers afin d'oublier 
Microsoft et ses bugs de virus.

Merci d'avance pour l'aide.

Cordialement.

AD



Le 14/05/2017 à 14:32, Laurent Montel a écrit :
> https://bugs.kde.org/show_bug.cgi?id=379805
>
> Laurent Montel  changed:
>
> What|Removed |Added
> 
>   CC||mon...@kde.org
>
> --- Comment #1 from Laurent Montel  ---
> Hello
> In french "Salut, les bugs reports se font en anglais par défaut mais comme je
> suis français ça va" :)
> Le bouton détail de donne des infos ?
> Est ce que tu as des erreurs en console ? Est ce que Akonadi est bien installé
> sur ta machine ?"
>
> I ask more info about errors.
>

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

[krusader] [Bug 321098] Preview configuration

[Alex Bikadorov]

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

Alex Bikadorov  changed:

   What|Removed |Added

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

--- Comment #1 from Alex Bikadorov  ---


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

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

[krusader] [Bug 329307] Can not configure built-in previewer to display .jpg files over 5 Mb

[Alex Bikadorov]

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

Alex Bikadorov  changed:

   What|Removed |Added

 CC||m...@pensaro.net

--- Comment #3 from Alex Bikadorov  ---
*** Bug 321098 has been marked as a duplicate of this bug. ***

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

[krusader] [Bug 329307] Can not configure built-in previewer to display .jpg files over 5 Mb

[Alex Bikadorov]

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

Alex Bikadorov  changed:

   What|Removed |Added

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

--- Comment #2 from Alex Bikadorov  ---
Maximum file size was removed in KDE Frameworks/KIO, see
https://phabricator.kde.org/D4552.

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

[krusader] [Bug 329307] Can not configure built-in previewer to display .jpg files over 5 Mb

[Alex Bikadorov]

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

Alex Bikadorov  changed:

   What|Removed |Added

 CC||zal...@volny.cz

--- Comment #1 from Alex Bikadorov  ---
*** Bug 353312 has been marked as a duplicate of this bug. ***

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

[krusader] [Bug 353312] Image thumbnails (jpeg) missing for files bigger than 3 MB

[Alex Bikadorov]

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

Alex Bikadorov  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #3 from Alex Bikadorov  ---


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

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

[korganizer] [Bug 379813] New: Korganizer and Kaddressbook doesnt sync anymore using Webdav

[bernd]

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

Bug ID: 379813
   Summary: Korganizer and Kaddressbook doesnt sync anymore using
Webdav
   Product: korganizer
   Version: 5.5.1
  Platform: PCLinuxOS
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: groupware
  Assignee: kdepim-b...@kde.org
  Reporter: berndwet...@mailbox.org
  Target Milestone: ---

Since the update to the 17.04 Version, Addressbook and Korganizer are not
synced anymore. The 17.04 Update installed a new package "kdav" (17.04..).
Since that time it is still possible to set up a new calendar in "DAV-
Groupware Resources". After adding required user information and collecting the
resources, Events are not displayed in Korganizer, and Contacts are not
displayed in Kaddressbook.

It you have already setup your account before the upgrade, everything is
visible but it is not syncing anymore with a webdav server.

I am collecting email, Contacts and Events from my provider mailbox.org.
Collecting Emails is not affected.

Bernd

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

[kmail2] [Bug 379791] Confusing Account Wizard dialog

[Martin]

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

--- Comment #2 from Martin  ---
Created attachment 105526
  --> https://bugs.kde.org/attachment.cgi?id=105526&action=edit
Screenshot

I mean this dialog. There is a "Postfach erstellen" button, which is annoying.
It would be better to remove this button.
And in addition hide button "Finish" for this step. It makes no sense to show
this disabled button here.
The UI of KDE programs are sometimes overloaded.

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

[digikam] [Bug 379751] I18N_ARGUMENT_MISSING in Edit Metadata

[philippe weyland]

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

--- Comment #2 from philippe weyland  ---
Is the window title issue linked to the fact I'm not able to save the changes ?

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