[marble] [Bug 378727] New: Crash when clicking Play a Tour of Popular Places

[bugzilla_noreply]

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

Bug ID: 378727
   Summary: Crash when clicking Play a Tour of Popular Places
   Product: marble
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: marble-b...@kde.org
  Reporter: cleit...@sfu.ca
  Target Milestone: ---

Application: marble (1.12.20 (1.13 development version))

Qt Version: 5.5.1
Operating System: Linux 4.4.0-72-generic x86_64
Distribution: Ubuntu 16.04.2 LTS

-- Information about the crash:
- What I was doing when the application crashed:
Clicked on the link that says Play a tour of popular places. Nothing appeared;
immediately crashed.

-- Backtrace:
Application: Marble Virtual Globe (marble), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fadb47f58c0 (LWP 2553))]

Thread 9 (Thread 0x7fad397fa700 (LWP 3626)):
#0  0x7fadbe673a94 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fadbe62e910 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fadbe62f2bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fadbe62f49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fadc5bd97eb in QEventDispatcherGlib::processEvents
(this=0x7fad180ef3c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7fadc5b80b4a in QEventLoop::exec (this=this@entry=0x7fad397f9d00,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7fadc599d834 in QThread::exec (this=) at
thread/qthread.cpp:503
#7  0x7fadc59a27be in QThreadPrivate::start (arg=0x2877300) at
thread/qthread_unix.cpp:331
#8  0x7fadbf6276ba in start_thread (arg=0x7fad397fa700) at
pthread_create.c:333
#9  0x7fadc50a282d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 8 (Thread 0x7fad53fff700 (LWP 2560)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fadc38a5aa3 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7fadc3bc6541 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7fadbf6276ba in start_thread (arg=0x7fad53fff700) at
pthread_create.c:333
#4  0x7fadc50a282d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 7 (Thread 0x7fad58c81700 (LWP 2559)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fadc38a5aa3 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7fadc3bc6541 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7fadbf6276ba in start_thread (arg=0x7fad58c81700) at
pthread_create.c:333
#4  0x7fadc50a282d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7fad59482700 (LWP 2558)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fadc38a5aa3 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7fadc3bc6541 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7fadbf6276ba in start_thread (arg=0x7fad59482700) at
pthread_create.c:333
#4  0x7fadc50a282d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7fad59c83700 (LWP 2557)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fadc38a4a74 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7fadc3bc6541 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7fadbf6276ba in start_thread (arg=0x7fad59c83700) at
pthread_create.c:333
#4  0x7fadc50a282d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7fad9a592700 (LWP 2556)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fadc3b9688b in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7fadc3b968c9 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7fadbf6276ba in start_thread (arg=0x7fad9a592700) at
pthread_create.c:333
#4  0x7fadc50a282d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7fada98e6700 (LWP 2555)):
#0  0x7fadc5096b5d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fadbe62f38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fadbe62f49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fadc5bd97eb in QEventDispatcherGlib::processEvents
(this=0x7fada40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7fadc5b80b4a in QEventLoop::exec (this=this@entry=0x7fada98e5d00,
flags=..., flags@entry=...) at 

[kalarm] [Bug 378722] Remove System Settings email address options

[Burkhard Lueck]

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

Burkhard Lueck  changed:

   What|Removed |Added

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

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

[kgpg] [Bug 373910] kgpg crash when changing key trust

[Dietmar]

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

Dietmar  changed:

   What|Removed |Added

 CC||dcze...@gmx.de

--- Comment #4 from Dietmar  ---
the bug is still present in openSuse Tumbleweed 16.12.3-1.1

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

[frameworks-baloo] [Bug 378726] baloosearch doesn't return the expected result

[Munzir Taha Obeid]

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

Munzir Taha Obeid  changed:

   What|Removed |Added

 CC||munzirt...@gmail.com

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

[frameworks-baloo] [Bug 378726] New: baloosearch doesn't return the expected result

[Munzir Taha Obeid]

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

Bug ID: 378726
   Summary: baloosearch doesn't return the expected result
   Product: frameworks-baloo
   Version: 5.32.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: pinak.ah...@gmail.com
  Reporter: munzirt...@gmail.com
  Target Milestone: ---

Though the file is indexed, baloo doesn't return the expected result!

> cat baloo_bug_378690 
hello_baloo
> balooctl status baloo_bug_378690 
File: /home/arch/baloo_bug_378690
Basic Indexing: Done
Content Indexing: Done
> baloosearch hello_baloo
Elapsed: 0.130105 msecs

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

[plasmashell] [Bug 377050] Plasmashell crashes whenever I close VLC

[Rex Dieter]

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

Rex Dieter  changed:

   What|Removed |Added

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

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

[dolphin] [Bug 378701] Option to disable frames with shadows on selected directories

[bugzilla_noreply]

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

--- Comment #3 from andre.cbar...@yahoo.com ---
Never mind, disabled protection plugins on my browser and registered.

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

[dolphin] [Bug 378701] Option to disable frames with shadows on selected directories

[bugzilla_noreply]

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

--- Comment #2 from andre.cbar...@yahoo.com ---
I could not figure out how to register to post, if you may give me some hint it
would be awesome.

André

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

[digikam] [Bug 378724] digikam - Direct crash when rotate left is choosed

[bugzilla_noreply]

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

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

   What|Removed |Added

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

--- Comment #1 from caulier.gil...@gmail.com ---


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

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

[digikam] [Bug 376429] Crash on rotate

[bugzilla_noreply]

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

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

   What|Removed |Added

 CC||kauf_d...@mailbox.org

--- Comment #2 from caulier.gil...@gmail.com ---
*** Bug 378724 has been marked as a duplicate of this bug. ***

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

[kwin] [Bug 378663] KWin won't draw Aurorae themes

[Mircea Kitsune]

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

--- Comment #7 from Mircea Kitsune  ---
The first part of the above comment is incorrect, please ignore it! For some
reason an old version I wrote up got posted here, before I did an additional
test and modified it. Updated statement:

First of all, I attempted to log in with the following environment variables
exported at system level, which I did by adding them to my ~/.profile:

export LIBGL_ALWAYS_SOFTWARE=1
export LIBGL_DEBUG=verbose

This has indeed fixed the issue, and caused KWin to render window decorations
again! However certain desktop effects would not work, such as blur.

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

[kwin] [Bug 378663] KWin won't draw Aurorae themes

[Mircea Kitsune]

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

--- Comment #6 from Mircea Kitsune  ---
Created attachment 105000
  --> https://bugs.kde.org/attachment.cgi?id=105000=edit
kwin_x11.txt

First of all, I attempted to log in with the following environment variables
exported at system level, which I did by adding them to my ~/.profile file:

LIBGL_ALWAYS_SOFTWARE=1
LIBGL_DEBUG=verbose

This has not affected the problem in any way: The issue occurred just like
before and KWin would render no window decorations.

While testing this however, I uncovered a strange side effect: If I kill
kwin_x11 then start the process back up while the system is running, the
problem goes away and the window elements show again, however I can no longer
enable desktop effects until I log out and in again. KDE doesn't complain about
anything in their regard, but pressing "alt + shift + f12" or trying to enable
them from the Desktop Settings menu does nothing.

Lastly I've attached the log generated by running kwin_x11 from bash. There
seem to be numerous complaints regarding all of the window elements, as well as
a message about a module identifier directive not being protected from external
registrations.

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

[Discover] [Bug 378615] [proposa] add and manage ppa archives from discover

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

 Resolution|--- |WONTFIX
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Aleix Pol  ---
That's out of scope for Discover and PackageKit. That's why we add a shortcut
to use the native tools, such as software-properties for Ubuntu. We expect
users to use that.

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

[Discover] [Bug 378339] Crash on remove chars in search text box

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #1 from Aleix Pol  ---
Addressed by https://phabricator.kde.org/D5408

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

[Discover] [Bug 378261] Discover upgrades list zero bytes

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

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

--- Comment #1 from Aleix Pol  ---
Fixed in on all stable releases.

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

[Discover] [Bug 377895] Window sizes < 1201 pixels wide obscure the ability to go back to the app list

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

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

--- Comment #2 from Aleix Pol  ---
Fixed in master, will have a button for that on 5.10.

Thanks for reporting and helping make it happen!

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

[frameworks-khtml] [Bug 377490] build failure with qt-5.9

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/kht
   ||ml/2d9c893adef9ba22a6357b01
   ||c51ca9983fbba5a9
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #3 from Aleix Pol  ---
Git commit 2d9c893adef9ba22a6357b01c51ca9983fbba5a9 by Aleix Pol.
Committed on 13/04/2017 at 01:02.
Pushed by apol into branch 'master'.

Fix build with Qt 5.9

Summary:
Otherwise we get the following error:
/home/apol/devel/frameworks/khtml/src/khtml_factory.h:31: Error: Plugin
Metadata file "" could not be opened: file to open is a directory

Arguably it's something to fix upstream, but also having `FILE ""` doesn't add
much either.

Test Plan: Now it compiles, tests pass, khelpcenter runs.

Reviewers: #frameworks, kfunk

Reviewed By: kfunk

Subscribers: mpyne, ltoscano, #frameworks

Tags: #frameworks

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

M  +1-1src/khtml_factory.h

https://commits.kde.org/khtml/2d9c893adef9ba22a6357b01c51ca9983fbba5a9

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

[plasmashell] [Bug 378683] org.kde.plasma.systemtray configKeys not accessible via plasma script api

[Bernard Gray]

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

--- Comment #2 from Bernard Gray  ---
Hi David, 
Thank you so much - that's really helpful!

I've hit one more (hopefully related) snag - so I've got the correct
containment now, I can manipulate the widgets that appear in the systemtray,
but I'm now having difficult setting the [Auto|Hidden|Shown] immutability(?)
configKey on a per widget/applet level.

To clarify, at the SystemTray level the applets can be set to appear or not
appear (this is what you've given me access to already) -
At an applet level, they can be set to Appear in the main tray (Shown), Appear
in the popup dialog when you click on the SystemTray arrow (Hidden), or work it
out for themselves (Auto).

I believe the key for this setting is "immutability", but I can't seem to find
how to access this key now - code snippet:

===
panel = panels()['0'];
for (var j in panel.widgetIds) {
var widget = panel.widgetById(panel.widgetIds[j]);
sysTrayId = widget.readConfig("SystrayContainmentId", -1);
if (sysTrayId > 0) {
var containment = desktopById(sysTrayId);
containment.currentConfigGroup = ["General"];
print(containment.configKeys);
print(containment.widgetIds);
for (var w in containment.widgetIds) {
var cwidget = containment.widgetById(containment.widgetIds[w]);
print(cwidget.type);
print(cwidget.configGroups);
print(cwidget.configKeys);
}
}
}


cwidget.configGroups and cwidget.configKeys are empty - even after manually
setting some different immutability's on various systray widgets - can I be so
bold as to ask for another pointer on how to get into these settings?

Thanks -

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

[korganizer] [Bug 378725] New: korganizer crashes when changing fonts in to-do list

[Jim Stewart]

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

Bug ID: 378725
   Summary: korganizer crashes when changing fonts in to-do list
   Product: korganizer
   Version: 5.4.3
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: korganizer-de...@kde.org
  Reporter: jstew...@celerox.net
  Target Milestone: ---

Application: korganizer (5.4.3)

Qt Version: 5.7.1
Frameworks Version: 5.33.0
Operating System: Linux 4.4.0-72-lowlatency x86_64
Distribution: KDE neon User Edition 5.9

-- Information about the crash:
- What I was doing when the application crashed:
changing the fonts on the second line of a to-do list. The first line has a
large font and the next line was to have a smaller font with a different type
face. 
This consistently crashes the application 

- Custom settings of the application:
To do list is being editing in "enhanced edit mode" with all the fancy edit
tools :o)  and on a separate monitor from the main Korganizer window

The crash can be reproduced every time.

-- Backtrace:
Application: KOrganizer (korganizer), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f1f8d8759c0 (LWP 8961))]

Thread 4 (Thread 0x7f1f81ead700 (LWP 8969)):
#0  0x7f1fbc12b69d in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f1fb26686f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f1fb2624e74 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f1fb2625330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f1fb262549c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f1fbcc6575b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f1fbcc100ba in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f1fbca3ff64 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f1fbca44b48 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f1fb439a6ba in start_thread (arg=0x7f1f81ead700) at
pthread_create.c:333
#10 0x7f1fbc13b82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f1f826ae700 (LWP 8967)):
#0  0x7f1fbcc638c9 in QTimerInfoList::repairTimersIfNeeded() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#1  0x7f1fbcc63953 in QTimerInfoList::timerWait(timespec&) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f1fbcc64d0e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f1fb262491d in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f1fb26252bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f1fb262549c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7f1fbcc6575b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f1fbcc100ba in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f1fbca3ff64 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f1fbca44b48 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7f1fb439a6ba in start_thread (arg=0x7f1f826ae700) at
pthread_create.c:333
#11 0x7f1fbc13b82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f1f838bf700 (LWP 8966)):
#0  0x7f1fbc12fb5d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f1fb262538c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f1fb262549c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f1fbcc6575b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f1fbcc100ba in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f1fbca3ff64 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f1fc01d9735 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x7f1fbca44b48 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f1fb439a6ba in start_thread (arg=0x7f1f838bf700) at
pthread_create.c:333
#9  0x7f1fbc13b82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f1f8d8759c0 (LWP 8961)):
[KCrash Handler]
#6  0x7f1fbd974f5f in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#7  0x7f1f8d4f8c26 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#8  0x7f1fbd9b3fe0 in QListView::selectionChanged(QItemSelection const&,
QItemSelection const&) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#9  0x7f1fbd98e591 in ?? () from

[digikam] [Bug 378724] New: digikam - Direct crash when rotate left is choosed

[bugzilla_noreply]

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

Bug ID: 378724
   Summary: digikam - Direct crash when rotate left is choosed
   Product: digikam
   Version: 4.12.0
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: digikam-de...@kde.org
  Reporter: kauf_d...@mailbox.org
  Target Milestone: ---

Application: digikam (4.12.0)
KDE Platform Version: 4.14.16
Qt Version: 4.8.7
Operating System: Linux 4.4.0-36-generic i686
Distribution: Ubuntu 16.04.2 LTS

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

When I opened digikam, I choosed a folder in the left panel. Then opened one
folder in which were some pics with wrong rotation. So I was in the foto viewer
and at one foto and then clicked at the symbol to rotate left. Then digikam
crashed.
When I try to reproduce it, digikamt is crashing everytime directly after that
step.
So I typed #gdb digikam into the console, but could not get digikam startet.
after the crash the debug window is opening and so i am here now.

I don't have deeper debug knowledge so I can't tell if the crashing is related
to the bug report called "Crash on rotate" which was closed by Gilles, because
of external program crash.

So I will apreciate it, when someone with deeper knowledge kann analyze the bug
and get the info out, if the fault is internal or of an external program.

Thanks to you/ them
Sapuani Teclada

The crash can be reproduced every time.

-- Backtrace:
Application: digiKam (digikam), signal: Segmentation fault
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0xacca79c0 (LWP 4280))]

Thread 6 (Thread 0x9f8acb40 (LWP 4298)):
[KCrash Handler]
#7  0xb3b2d8be in ?? () from /usr/lib/i386-linux-gnu/libjpeg.so.8
#8  0xb6fd01dc in do_rot_270 (dst_coef_arrays=0xb4182f90 , src_coef_arrays=0xa2d085c, y_crop_offset=195134048,
x_crop_offset=3020237506, dstinfo=0x9f8ab1cc, srcinfo=0x9f8ab378) at
/build/digikam-Gcg5vj/digikam-4.12.0/core/libs/jpegutils/libjpeg-84/transupp.c:486
#9  jtransform_execute_transform (srcinfo=0x9f8ab378, dstinfo=0x9f8ab1cc,
src_coef_arrays=0xa2d085c, info=0x9f8aaf38) at
/build/digikam-Gcg5vj/digikam-4.12.0/core/libs/jpegutils/libjpeg-84/transupp.c:1463
#10 0xb6fc8685 in Digikam::JPEGUtils::JpegRotator::performJpegTransform
(this=0x9f8ab880, action=KExiv2Iface::RotationMatrix::Rotate270, src=...,
dest=...) at
/build/digikam-Gcg5vj/digikam-4.12.0/core/libs/jpegutils/jpegutils.cpp:656
#11 0xb6fcc610 in Digikam::JPEGUtils::JpegRotator::exifTransform
(this=0x9f8ab880, matrix=...) at
/build/digikam-Gcg5vj/digikam-4.12.0/core/libs/jpegutils/jpegutils.cpp:414
#12 0xb6fce1db in Digikam::JPEGUtils::JpegRotator::exifTransform
(this=0x9f8ab880, action=KExiv2Iface::RotationMatrix::Rotate270) at
/build/digikam-Gcg5vj/digikam-4.12.0/core/libs/jpegutils/jpegutils.cpp:366
#13 0x0827c894 in Digikam::FileActionMngrFileWorker::transform (this=0x9037190,
infos=..., action=7) at
/build/digikam-Gcg5vj/digikam-4.12.0/core/app/fileaction/fileworkeriface.cpp:218
#14 0x0827ad66 in Digikam::FileWorkerInterface::qt_static_metacall
(_o=0x9037190, _c=QMetaObject::InvokeMetaMethod, _id=5, _a=0xa9f35b8) at
/build/digikam-Gcg5vj/digikam-4.12.0/obj-i686-linux-gnu/core/app/fileworkeriface.moc:68
#15 0xb4761cca in QMetaCallEvent::placeMetaCall (this=0x96d8b90,
object=0x9037190) at kernel/qobject.cpp:524
#16 0xb4769ea1 in QObject::event (this=0x9037190, e=0x96d8b90) at
kernel/qobject.cpp:1222
#17 0xb70383aa in Digikam::WorkerObject::event (this=0x9037190, e=0x96d8b90) at
/build/digikam-Gcg5vj/digikam-4.12.0/core/libs/threads/workerobject.cpp:160
#18 0xb4d9f64a in QApplicationPrivate::notify_helper (this=0x8c20540,
receiver=0x9037190, e=0x96d8b90) at kernel/qapplication.cpp:4570
#19 0xb4da6951 in QApplication::notify (this=0xbff27fb4, receiver=0x9037190,
e=0x96d8b90) at kernel/qapplication.cpp:4356
#20 0xb595f71c in KApplication::notify (this=0xbff27fb4, receiver=0x9037190,
event=0x96d8b90) at
/build/kde4libs-nQJkRJ/kde4libs-4.14.16/kdeui/kernel/kapplication.cpp:311
#21 0xb474e57a in QCoreApplication::notifyInternal (this=0xbff27fb4,
receiver=0x9037190, event=0x96d8b90) at kernel/qcoreapplication.cpp:955
#22 0xb4752266 in QCoreApplication::sendEvent (event=0x96d8b90,
receiver=0x9037190) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#23 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0,
data=0x9d4f1e0) at kernel/qcoreapplication.cpp:1579
#24 0xb4752595 in QCoreApplication::sendPostedEvents (receiver=0x0,
event_type=0) at kernel/qcoreapplication.cpp:1472
#25 0xb4780f91 in QCoreApplication::sendPostedEvents () at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236
#26 postEventSourceDispatch (s=0x9d5a400) at
kernel/qeventdispatcher_glib.cpp:300
#27 

[kdenlive] [Bug 356493] "Save Layout As" menu option in menu bar redundant? Suggest removing "Save Layout As" sub-menu text

[Ashark]

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

--- Comment #5 from Ashark  ---
By the way, this bug is screenshoted in features page in main site:
https://kdenlive.org/features/

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

[kdenlive] [Bug 356493] "Save Layout As" menu option in menu bar redundant? Suggest removing "Save Layout As" sub-menu text

[Ashark]

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

--- Comment #4 from Ashark  ---
Hello, Jesse.
Github is a read only mirror of KDE repositories. See this page:
https://community.kde.org/Infrastructure/Github_Mirror

But I saw your patch, and I think my is more "optimised".
On line 69 you keep i18n("%1", layoutName)); to send a string.
However, in this case i18n will just return %1 and then replace it with
layoutName and after that this string could be used by setText.
In my patch, I just give layoutName to setText:
saveActions[j]->setText(layoutName);

I suggest you to add [patch provided] to the title of this bug report and then
it will be easy for team to spot and apply this patch.

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

[dolphin] [Bug 378723] New: Dolphin crashes while logging out.

[Tony]

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

Bug ID: 378723
   Summary: Dolphin crashes while logging out.
   Product: dolphin
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: jodr...@live.com
  Target Milestone: ---

As the title says. Have a dolphin instance running then log out. You'll get a
crash window instead of dolphin ending cleanly.

Here is the trace i managed to get:

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 0x7fd00bbff8c0 (LWP 14132))]

Thread 3 (Thread 0x7fcfe4ff5700 (LWP 14139)):
#0  0x7fd00b5f9b5d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fd0001e938c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fd0001e949c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fd00632675b in QEventDispatcherGlib::processEvents
(this=0x7fcfd80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7fd0062d10ba in QEventLoop::exec (this=this@entry=0x7fcfe4ff4d00,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7fd006100f64 in QThread::exec (this=) at
thread/qthread.cpp:507
#6  0x7fd006105b48 in QThreadPrivate::start (arg=0x2605290) at
thread/qthread_unix.cpp:368
#7  0x7fd00253e6ba in start_thread (arg=0x7fcfe4ff5700) at
pthread_create.c:333
#8  0x7fd00b60582d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7fcfe57f6700 (LWP 14138)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x7fcfec77ae44 in ?? () from /usr/lib/nvidia-378/libGLX_nvidia.so.0
#2  0x7fcfe65c2394 in ?? () from
/usr/lib/nvidia-378/libnvidia-glcore.so.378.13
#3  0x7fcfec77a12c in ?? () from /usr/lib/nvidia-378/libGLX_nvidia.so.0
#4  0x7fd00253e6ba in start_thread (arg=0x7fcfe57f6700) at
pthread_create.c:333
#5  0x7fd00b60582d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7fd00bbff8c0 (LWP 14132)):
[KCrash Handler]
#6  std::__atomic_base::compare_exchange_strong (__m2=, __m1=std::memory_order_acquire, __p2=,
__p1=@0x7ffef8903f88: 0x0, this=0x20) at
/usr/include/c++/5/bits/atomic_base.h:752
#7  std::atomic::compare_exchange_strong
(__m=std::memory_order_acquire, __p2=, __p1=@0x7ffef8903f88:
0x0, this=0x20) at /usr/include/c++/5/atomic:475
#8  QAtomicOps::testAndSetAcquire
(currentValue=, newValue=, expectedValue=0x0,
_q_value=...) at
../../include/QtCore/../../src/corelib/arch/qatomic_cxx11.h:290
#9  QBasicAtomicPointer::testAndSetAcquire (currentValue=, newValue=, expectedValue=0x0, this=0x20) at
../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:259
#10 QBasicMutex::fastTryLock (current=, this=0x20) at
thread/qmutex.h:89
#11 QMutex::lock (this=this@entry=0x20) at thread/qmutex.cpp:225
#12 0x7fd00bce49af in QMutexLocker::QMutexLocker (m=0x20, this=) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:137
#13 QDBusConnectionManager::busConnection (this=0x0,
type=type@entry=QDBusConnection::SessionBus) at qdbusconnection.cpp:109
#14 0x7fd00bce5a5a in QDBusConnection::sessionBus () at
qdbusconnection.cpp:1177
#15 0x7fcff515198d in QtCurve::Style::disconnectDBus (this=0x250b040) at
/workspace/build/qt5/style/qtcurve.cpp:702
#16 0x7fcff518db56 in QtCurve::runAllCleanups () at
/workspace/build/qt5/style/qtcurve_plugin.cpp:86
#17 QtCurve::StylePlugin::~StylePlugin (this=0x200f510, __in_chrg=) at /workspace/build/qt5/style/qtcurve_plugin.cpp:167
#18 0x7fcff518db89 in QtCurve::StylePlugin::~StylePlugin (this=0x200f510,
__in_chrg=) at /workspace/build/qt5/style/qtcurve_plugin.cpp:170
#19 0x7fd0062c8189 in QLibraryPrivate::unload (this=this@entry=0x1ff30f0,
flag=flag@entry=QLibraryPrivate::UnloadSys) at plugin/qlibrary.cpp:562
#20 0x7fd0062be1a2 in QFactoryLoaderPrivate::~QFactoryLoaderPrivate
(this=0x1ff2e00, __in_chrg=) at plugin/qfactoryloader.cpp:86
#21 0x7fd0062be2c9 in QFactoryLoaderPrivate::~QFactoryLoaderPrivate
(this=0x1ff2e00, __in_chrg=) at plugin/qfactoryloader.cpp:89
#22 0x7fd00630585c in QScopedPointerDeleter::cleanup
(pointer=) at
../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:60
#23 QScopedPointer::~QScopedPointer (this=0x7fd0070bccc8 <(anonymous
namespace)::Q_QGS_loader::innerFunction()::holder+8>, __in_chrg=) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:107
#24 QObject::~QObject (this=, __in_chrg=) at
kernel/qobject.cpp:900
#25 0x7fd0062bd73a in QFactoryLoader::~QFactoryLoader (this=0x7fd0070bccc0
<(anonymous 

[kalarm] [Bug 378722] New: Remove System Settings email address options

[David Jarvie]

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

Bug ID: 378722
   Summary: Remove System Settings email address options
   Product: kalarm
   Version: 2.11.10
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: djar...@kde.org
  Reporter: djar...@kde.org
  Target Milestone: ---

KF5 system settings doesn't have an email address setting any more, so these
options should be removed from KAlarm.

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

[kalarm] [Bug 378431] Saving Text reminders very buggy

[David Jarvie]

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

--- Comment #2 from David Jarvie  ---
I've tried setting an alarm for 90 hours from now, but it is scheduled for the
correct time (3 days 18 hours ahead). I can't make it go wrong.

Can you try creating a new alarm with "time from now 90:00" again, and if it
also shows the wrong time after saving it, open the alarm for editing and look
at what it now shows in the "time from now" value. Does it show "90:00" (or
slightly less in case a minute has passed)? (Note that the value displayed in
"time from now" is calculated afresh from the scheduled time stored for the
alarm - the alarm time is not saved as a "time from now" value - so this should
test for consistency.)

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

[krita] [Bug 378721] New: Cannot paint in canvas

[bugzilla_noreply]

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

Bug ID: 378721
   Summary: Cannot paint in canvas
   Product: krita
   Version: 3.1.2
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: Brush engine
  Assignee: krita-bugs-n...@kde.org
  Reporter: thomasaza...@gmail.com
  Target Milestone: ---

My cursor is frozen within the canvas.  This is the same result for all of my
files and new files. I cannot paint at all.  I cannot paint with the mouse or
the pen. I am using Windows 10.  I have tried the following:
1. restarting computer
2. ensuring windows is fully up to date and then restarting
3. uninstalling, restarting, and reinstalling Krita

Thank you!

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

[krita] [Bug 378706] [WACOM] Eraser not switching to eraser.

[Bryan McWhirt]

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

--- Comment #2 from Bryan McWhirt  ---
(In reply to Boudewijn Rempt from comment #1)
> That was fixed in 3.1.3 beta.

I've just learned of Krita so forgive me if this is a dumb question, but is the
beta publicly available? I looked around on the website and saw no place to
download the beta.

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

[kdenlive] [Bug 371762] git master - Project Monitor isn't playing to end of timeline. Stops a second or two before end [video example included]

[Jesse]

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

--- Comment #2 from Jesse  ---
I tested to see if it was an MLT issue by opening a Terminal and playing a
9-second video clip I rendered "melt ./untitled.webm", and the video played all
the way through, smoothly. Going back into Kdenlive and pressing SPACEBAR or
pressing the play button, once the timeline position cursor gets a second or
two from the end of the project, it skips immediately to the end.

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

[kdenlive] [Bug 371762] git master - Project Monitor isn't playing to end of timeline. Stops a second or two before end [video example included]

[Jesse]

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

Jesse  changed:

   What|Removed |Added

   Severity|normal  |major

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

[kdenlive] [Bug 375967] git master - Project Monitor skipping to end of Timeline when seconds away from the end.

[Jesse]

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

Jesse  changed:

   What|Removed |Added

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

--- Comment #2 from Jesse  ---
I made a duplicate bug by accident of this (Bug #371762), but it has more
updated data, so I'll continue this, there. Closing bug.

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

[plasmashell] [Bug 377050] Plasmashell crashes whenever I close VLC

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #11 from David Edmundson  ---
Found it!

Interestingly nothing to do with media controller.

If system tray adds an Applet which is incredibly broken (such as missing
metadta) it will still get created. 
For some reason that I don't know yet Containmnet::createApplet isn't returning
null

ContainmentInterface guards against an invalid graphic object when an applet is
added forward.

However, nothing really bad happens.
So .. we then add a media player, and then later delete it:

We then get into this code in the system tray:

void SystemTray::cleanupTask(const QString )
{
foreach (Plasma::Applet *applet, applets()) {
if (!applet->pluginMetaData().isValid() || task ==
applet->pluginMetaData().pluginId()) {
applet->deleteLater();


So when we try and clean up VLC we end up also cleaning our broken applet.
(whatever that is)

This then gets removed.

ContainmentInterface doesn't guard against the graphics object on applet
removal, and we get our cras.


So 3 bits of code, and they're all bad.

Containment::createApplet : should be failing properly

ContainmentInterface::appletAdded / appletRemoved: should be consistent with
guards. I don't think there should be any. It's a bad habbit to just blindly
guard pointers that should be there. It would have made diagnosing this a
million times faster.

SystemTray::cleanupTask : why is it checking applet metadata now???

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

[kdenlive] [Bug 356493] "Save Layout As" menu option in menu bar redundant? Suggest removing "Save Layout As" sub-menu text

[Jesse]

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

--- Comment #3 from Jesse  ---
Thanks for submitting that patch, Ashark. I'd actually performed that commit on
my forked github repo, but I guess that I didn't know the whole steps to submit
the patch for review. :) Still so much to learn! Hoping to hear back from the
Kdenlive team -- would love to say I'd committed to the project beyond bug
testing.

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

[krita] [Bug 378720] New: crashes when drawing on canvas

[kyain]

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

Bug ID: 378720
   Summary: crashes when drawing on canvas
   Product: krita
   Version: 3.1.1
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: kal...@gmail.com
  Target Milestone: ---

when i open my krita it seems to work normally but then once i press anywhere
on the screen with the pen it closes immediately. even if the krita tab is not
on screen. im using a huion tablet on windows 7

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

[krita] [Bug 378719] New: crashes when drawing on canvas

[kyain]

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

Bug ID: 378719
   Summary: crashes when drawing on canvas
   Product: krita
   Version: 3.1.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: kal...@gmail.com
  Target Milestone: ---

when i open my krita it seems to work normally but then once i press anywhere
on the screen with the pen it closes immediately. even if the krita tab is not
on screen. im using a huion tablet on windows 7

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

[kdenlive] [Bug 371762] git master - Project Monitor isn't playing to end of timeline. Stops a second or two before end [video example included]

[Jesse]

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

--- Comment #1 from Jesse  ---
Test this on a fresh install of Ubuntu GNOME 17.04 x64, GNOME 3.24.0, and this
bug still occurred.

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

[Akonadi] [Bug 245218] akonadi uses a lot of hard disk space Platform Version 4.5.60 (KDE 4.5.60 (KDE 4.6 >= 20100627)) "release 3"

[Matija Šuklje]

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

--- Comment #12 from Matija Šuklje  ---
(In reply to Martin Steigerwald from comment #11)
> Matija, did you read the previous comments and especially the hint to bug
> #341884?

I did. That’s how I managed to work around it.

> You are using an *ancient* version of KDEPIM and Akonadi that is not
> maintained anymore. Additionally the issue is likely already fixed. Please
> switch to at least KDEPIM/Akonadi 16.04 or 16.08, preferably 16.12. If you
> still have these issues with any of these versions, please open a new bug
> report.

Mageia’s stable is still and carrying that version of KDE(PIM) and Akonadi. I’m
anxiously waiting for Mageia 6 to finally come out in the next (hopefully)
weeks – and with it the Plasma 5 (LTS)!

I’m optimistic that I won’t stumble upon this bug again, but if I do, I’ll open
a new bug, as instructed. Thanks :)

> Closing as unmaintained. Thanks, Martin

Sounds OK to me.

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

[Spectacle] [Bug 378718] New: Yakuake drop-down terminal presenting Spectacle bindings to not work

[Kamil]

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

Bug ID: 378718
   Summary: Yakuake drop-down terminal presenting Spectacle
bindings to not work
   Product: Spectacle
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: General
  Assignee: m...@baloneygeek.com
  Reporter: redredempt...@protonmail.com
  Target Milestone: ---

Created attachment 104999
  --> https://bugs.kde.org/attachment.cgi?id=104999=edit
The bug itself

What exactly happens:

If Yakuake is not set to keep window open when it loses focus attempting to
take a screenshot of yakuake window via the rectangular region capture mode
causes Spectacle's bindings (`Enter` to take a screenshot & `ESC` to quit) to
not work.

The only way to take a screenshot when the bugs is present is double-clicking.

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

[Spectacle] [Bug 378685] Improve the contrast of the slection '+' cursor - can hardly see it.

[Derek]

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

--- Comment #2 from Derek  ---
(In reply to Boudhayan Gupta from comment #1)
> Save button arrow > Preferences > Light Background for Rectangular Region

That helps. Thank you.

I think i'll raise another wishlist: put Preferences somewhere other than "Save
As" (!!)  :) Honestly - i looked for preferences. Note i looked under the
Handbook in Help which doesn't appear to mention this.

Do i close this or someone else?

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

[plasmashell] [Bug 345563] Assert in QGLXContext::init when OpenGL drivers are not installed

[Stephan Manzek]

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

Stephan Manzek  changed:

   What|Removed |Added

 CC|man...@gmail.com|

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

[Akonadi] [Bug 245218] akonadi uses a lot of hard disk space Platform Version 4.5.60 (KDE 4.5.60 (KDE 4.6 >= 20100627)) "release 3"

[Martin Steigerwald]

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

Martin Steigerwald  changed:

   What|Removed |Added

 CC||mar...@lichtvoll.de
 Resolution|--- |UNMAINTAINED
 Status|REOPENED|RESOLVED

--- Comment #11 from Martin Steigerwald  ---
Matija, thank you for your comment.

Matija, did you read the previous comments and especially the hint to bug
#341884?

You are using an *ancient* version of KDEPIM and Akonadi that is not maintained
anymore. Additionally the issue is likely already fixed. Please switch to at
least KDEPIM/Akonadi 16.04 or 16.08, preferably 16.12. If you still have these
issues with any of these versions, please open a new bug report.

Closing as unmaintained. Thanks, Martin

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

[dolphin] [Bug 378717] New: Dolphin crash when browsing files on a mounted ISO

[Max]

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

Bug ID: 378717
   Summary: Dolphin crash when browsing files on a mounted ISO
   Product: dolphin
   Version: 15.12.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: mzele...@hotmail.com
  Target Milestone: ---

Application: dolphin (15.12.3)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-72-generic x86_64
Distribution: Ubuntu 16.04.2 LTS

-- Information about the crash:
- I was attempting to select a file for copy on a mounted ISO
- Running Kubuntu as guest in VMware Workstation 12

-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
__lll_lock_wait () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:135
[Current thread is 1 (Thread 0x7f0afdd058c0 (LWP 8160))]

Thread 4 (Thread 0x7f09a7b58700 (LWP 8185)):
[KCrash Handler]
#6  QBasicAtomicOps<8>::testAndSetRelaxed (currentValue=, newValue=0x1, expectedValue=0x0, _q_value=@0x81: ) at ../../include/QtCore/../../src/corelib/arch/qatomic_x86.h:259
#7  QGenericAtomicOps >::testAndSetAcquire (currentValue=, newValue=,
expectedValue=0x0, _q_value=@0x81: ) at
../../include/QtCore/../../src/corelib/thread/qgenericatomic.h:166
#8  QBasicAtomicPointer::testAndSetAcquire (currentValue=, newValue=, expectedValue=0x0, this=this@entry=0x81) at
../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:276
#9  QBasicMutex::fastTryLock (current=,
this=this@entry=0x81) at thread/qmutex.h:82
#10 QMutex::lock (this=this@entry=0x81) at thread/qmutex.cpp:212
#11 0x7f0b0b6f191b in QMutexLocker::QMutexLocker (m=0x81, this=) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:128
#12 QThreadPrivate::finish (arg=arg@entry=0x12fe410) at
thread/qthread_unix.cpp:343
#13 0x7f0b0b6f27df in __pthread_cleanup_class::~__pthread_cleanup_class
(this=, __in_chrg=) at
/usr/include/pthread.h:561
#14 QThreadPrivate::start (arg=0x12fe410) at thread/qthread_unix.cpp:290
#15 0x7f0b07ea06ba in start_thread (arg=0x7f09a7b58700) at
pthread_create.c:333
#16 0x7f0b10b2c82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f0aed1d4700 (LWP 8164)):
#0  0x7f0b10b20b5d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f0b0731438c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f0b0731449c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f0b0b9297eb in QEventDispatcherGlib::processEvents
(this=0x7f0ae80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7f0b0b8d0b4a in QEventLoop::exec (this=this@entry=0x7f0aed1d3d00,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f0b0b6ed834 in QThread::exec (this=) at
thread/qthread.cpp:503
#6  0x7f0b0b6f27be in QThreadPrivate::start (arg=0x10ead00) at
thread/qthread_unix.cpp:331
#7  0x7f0b07ea06ba in start_thread (arg=0x7f0aed1d4700) at
pthread_create.c:333
#8  0x7f0b10b2c82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f0afb607700 (LWP 8161)):
#0  0x7f0b10b2d79d in recvmsg () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f0b052aadd7 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f0b052a8ed1 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f0b052aa8d7 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#4  0x7f0afd959629 in QXcbEventReader::run (this=0xcfde00) at
qxcbconnection.cpp:1253
#5  0x7f0b0b6f27be in QThreadPrivate::start (arg=0xcfde00) at
thread/qthread_unix.cpp:331
#6  0x7f0b07ea06ba in start_thread (arg=0x7f0afb607700) at
pthread_create.c:333
#7  0x7f0b10b2c82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f0afdd058c0 (LWP 8160)):
#0  __lll_lock_wait () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:135
#1  0x7f0b07ea2dbd in __GI___pthread_mutex_lock (mutex=0xcf16f8) at
../nptl/pthread_mutex_lock.c:80
#2  0x7f0b052a964c in xcb_send_request64 () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f0b052a9969 in xcb_send_request () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#4  0x7f0b052b01e3 in xcb_query_pointer () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#5  0x7f0afd97b39f in QXcbCursor::queryPointer (c=0xceff40,
rootWin=rootWin@entry=0x0, pos=pos@entry=0x7fffbd751670,
keybMask=keybMask@entry=0x0) at qxcbcursor.cpp:617
#6  0x7f0afd97b468 in QXcbCursor::pos (this=0xd0dde0) at qxcbcursor.cpp:639
#7  0x7f0b0be2ff88 in QCursor::pos (screen=) at
kernel/qcursor.cpp:182
#8  0x7f0b0be30061 in QCursor::pos () at kernel/qcursor.cpp:206
#9  0x7f0b0c554961 in 

[krita] [Bug 376405] Saturation value in HSV adjustment isn't restored

[RKS]

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

RKS  changed:

   What|Removed |Added

 CC||rks...@gmail.com

--- Comment #2 from RKS  ---
Created attachment 104998
  --> https://bugs.kde.org/attachment.cgi?id=104998=edit
Fix for incorrect restoration of saturation slider

In the UI file (wdg_hsv_adjustment.ui), the minimum value for saturationSpinBox
was not set, and hence was taken as default 0, and the minimum value for
saturationSlider was set to 0.

I added them and now it seems to work fine.

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

[kdenlive] [Bug 378716] Crashes on video playback

[Kirill Shustov]

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

--- Comment #1 from Kirill Shustov  ---
On next clip import crashes again

[swscaler @ 0x7f2b3756e340] Warning: data is not aligned! This can lead to a
speedloss
GL error 0x502 at effect_chain.cpp:1877
Aborted (core dumped)

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

[kdenlive] [Bug 378716] New: Crashes on video playback

[Kirill Shustov]

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

Bug ID: 378716
   Summary: Crashes on video playback
   Product: kdenlive
   Version: 16.12.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Video Display & Export
  Assignee: j...@kdenlive.org
  Reporter: kirill.sus...@gmail.com
  Target Milestone: ---

App crashes on video playback  with key-frame rotation -900. 
As side affect negative angled  does not rotate video

in console I see follow log, project is broken after crash and crashes on every
start up.


[swscaler @ 0x7fd318bc1440] Warning: data is not aligned! This can lead to a
speedloss
***
FOUND GUIDES:  0 
**
GL error 0x502 at ycbcr_input.cpp:63
Aborted (core dumped)

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

[okular] [Bug 378449] Fall back to PDF when file type cannot be inferred from extension

[Damian Nowak]

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

--- Comment #4 from Damian Nowak  ---
$ okular 

Or via Dolphin - right click, open as, choose Okular.

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

[clazy] [Bug 378677] returning-void-expression false positive

[bugzilla_noreply]

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

--- Comment #3 from oktal3...@gmail.com ---
I'm sorry, I jumped to a conclusion and gave you faulty information without
first checking it thoroughly for myself. The false positive occurs when the
function is constexpr and the return type is dependent on a template parameter.

template 
constexpr T test3()
{
return {}; // OK (bug #378677)
}

I have confirmed that _this_ testcase does exhibit the bug on my system, which
is the pre-built Windows binary.

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

[okular] [Bug 378473] Medieval Sharp font does not print bold correctly

[bugzilla_noreply]

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

--- Comment #8 from phoeni...@gmail.com ---
However, now I can. I have probably made a mistake first time I have tried.

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

[okular] [Bug 378473] Medieval Sharp font does not print bold correctly

[bugzilla_noreply]

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

--- Comment #7 from phoeni...@gmail.com ---
Interesting, I was not able to reproduce it by printing to file when I have
tried.

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

[krusader] [Bug 373976] krusader and krusader root icons are not open in wayland.

[Andrius Štikonas]

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

Andrius Štikonas  changed:

   What|Removed |Added

   Version Fixed In||2.6.1
  Latest Commit||e396c209073d830dcb0d2e9eb7f
   ||ab16f36fbbd8d
 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #7 from Andrius Štikonas  ---
Git commit e396c209073d830dcb0d2e9eb7fab16f36fbbd8d by Andrius Štikonas.
Committed on 12/04/2017 at 21:45.
Pushed by stikonas into branch 'master'.

Set a path to desktop file.

M  +1  krusader/main.cpp

https://commits.kde.org/krusader/e396c209073d830dcb0d2e9eb7fab16f36fbbd8d

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

[gwenview] [Bug 364805] Gwenview fails to open images with russian letters in path - Invalid url QUrl("") or file or path does not exist

[Luigi Toscano]

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

Luigi Toscano  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 CC||luigi.tosc...@tiscali.it
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #15 from Luigi Toscano  ---
(In reply to Wadlax from comment #14)
> Error was specific to my locale settings.
>  
> I had line  LC_ALL=""   in file  /etc/env.d/02locale
> 
> Can anyone affected check this file?

So basically now you have LC_ALL="ru_RU.UTF-8", or something like that, and
gwenview works as it is?

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

[okular] [Bug 378473] Medieval Sharp font does not print bold correctly

[Oliver Sander]

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

--- Comment #6 from Oliver Sander  ---
The problem goes away when using the patch from

  https://git.reviewboard.kde.org/r/130055/

which avoids the intermediate conversion to postscript in a few cases.

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

[krusader] [Bug 373976] krusader and krusader root icons are not open in wayland.

[Andrius Štikonas]

https://bugs.kde.org/show_bug.cgi?id=373976
Bug 373976 depends on bug 378612, which changed state.

Bug 378612 Summary: Many applications show generic wayland icon in taskbar
https://bugs.kde.org/show_bug.cgi?id=378612

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution|--- |INVALID

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

[frameworks-kcoreaddons] [Bug 378612] Many applications show generic wayland icon in taskbar

[Andrius Štikonas]

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

Andrius Štikonas  changed:

   What|Removed |Added

 Resolution|--- |INVALID
 Status|REOPENED|RESOLVED

--- Comment #5 from Andrius Štikonas  ---
Ok, so I guess what happened is that application developers were not aware that
setting organizationDomain is not enough and it does not change desktop file
path. A consensus was to add explicit setDesktopFilePath.

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

[kdevelop] [Bug 378651] Kdev-python + Vi Input Mode and CPU load

[Sven Brauch]

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

Sven Brauch  changed:

   What|Removed |Added

 CC||m...@svenbrauch.de

--- Comment #3 from Sven Brauch  ---
The VI mode sounds like a random correlation to me. I don't see how that could
have anything to do with it.

Can you attach the debugger to KDevelop when it uses too much CPU, and then
interrupt it (Ctrl+C) and post the output of "thread apply all bt"?

Also, are you sure it's not just the background parser doing something and will
eventually finish after a few seconds ...?

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

[okular] [Bug 378449] Fall back to PDF when file type cannot be inferred from extension

[Albert Astals Cid]

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

--- Comment #3 from Albert Astals Cid  ---
How are you opening the file?

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

[kdevelop] [Bug 376084] Crash on code parsing

[Kevin Funk]

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

Kevin Funk  changed:

   What|Removed |Added

 Resolution|--- |UPSTREAM
 Status|CONFIRMED   |RESOLVED

--- Comment #4 from Kevin Funk  ---
Unfixable in KDevelop, I think. Reported upstream:
  https://bugs.llvm.org/show_bug.cgi?id=32643

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

[Akonadi] [Bug 245218] akonadi uses a lot of hard disk space Platform Version 4.5.60 (KDE 4.5.60 (KDE 4.6 >= 20100627)) "release 3"

[Matija Šuklje]

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

--- Comment #10 from Matija Šuklje  ---
> My ~/.local/share/akonadi/file_db_data takes up around 86 GiB, which even
> though I have a 5 GiB IMAP inbox, is not *nearly* close to what it should be.

And sure enough, after cleaning it up with fdupes, the folder now takes only
around 6 GiB of space.

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

[okular] [Bug 378473] Medieval Sharp font does not print bold correctly

[Oliver Sander]

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

--- Comment #5 from Oliver Sander  ---
Created attachment 104997
  --> https://bugs.kde.org/attachment.cgi?id=104997=edit
Screenshot of sample file printed to pdf

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

[okular] [Bug 378473] Medieval Sharp font does not print bold correctly

[Oliver Sander]

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

Oliver Sander  changed:

   What|Removed |Added

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

--- Comment #4 from Oliver Sander  ---
I can reproduce this by simply printing to pdf; see attached file.

This is with the current git master on today's Debian testing.

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

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

[Roberto]

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

--- Comment #246 from Roberto  ---
I'm not sure if this is going to be useful at all, but I actually used
activities and desktops combined, so I really lost functionality when all
desktops became equal.

I am a Data Analyst, and I usually create a separate activity for each project
I'm working on, plus a couple of general ones (communication, entertainment,
etc.). For the project-related ones, I usually have one desktop where I code,
one where I view graphics, one where I run background process and I used to
have different backgrounds and widgets for each of these. They were all
related, but definitely different for each desktop. The background was nice,
but the different widgets were really important, and those are gone.

I don't have the skills to help fix this problem, but I'd really appreciate to
have the functionality available in KDE 14 back. The workarounds suggested
don't match my use case.

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

[kmail2] [Bug 353620] distribution list is resolved by comma in name

[Eugen Albiker]

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

Eugen Albiker  changed:

   What|Removed |Added

   Version Fixed In||Kmail 5.2.3

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

[krita] [Bug 378715] New: Cant change or load shortcut schemes

[Fer]

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

Bug ID: 378715
   Summary: Cant change or load shortcut schemes
   Product: krita
   Version: 3.1.2
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: usability
  Assignee: krita-bugs-n...@kde.org
  Reporter: ferdinandu...@gmail.com
  Target Milestone: ---

The program wont acknowledge any changes to the shortcut layout, even when
loading one of the preset schemes. Tried using the table_pro scheme so I could
create new frames when animating (using Alt+N). Instead I only get this window:
"The key sequence 'Alt+N' is ambiguous. Use 'Configure Shortcuts'
from the 'Settings' menu to solve the ambiguity.
No action will be triggered."

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

[krita] [Bug 378714] New: Cant change or load shortcut schemes

[Fer]

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

Bug ID: 378714
   Summary: Cant change or load shortcut schemes
   Product: krita
   Version: 3.1.2
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: usability
  Assignee: krita-bugs-n...@kde.org
  Reporter: ferdinandu...@gmail.com
  Target Milestone: ---

The program wont acknowledge any changes to the shortcut layout, even when
loading one of the preset schemes. Tried using the table_pro scheme so I could
create new frames when animating (using Alt+N). Instead I only get this window:
"The key sequence 'Alt+N' is ambiguous. Use 'Configure Shortcuts'
from the 'Settings' menu to solve the ambiguity.
No action will be triggered."

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

[plasmashell] [Bug 378713] New: Plasma crashes after suspend

[Serge Pavlyuk]

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

Bug ID: 378713
   Summary: Plasma crashes after suspend
   Product: plasmashell
   Version: 5.9.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: flo...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.9.4)

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

-- Information about the crash:
After suspend and login, plasma sotimes crashes and restores.
KWin reports that video driver was restarted, and i'm catching a few freezes.
Some times opengl effects are disabled after suspend.
In some cases plasma reports about crash.

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 0x7fbf489d8800 (LWP 712))]

Thread 44 (Thread 0x7f7dcd837700 (LWP 8587)):
#0  0x7fbf4162cca6 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fbf1e5f3e44 in  () at /usr/lib/libGLX_nvidia.so.0
#2  0x7fbf1d143394 in  () at /usr/lib/libnvidia-glcore.so.378.13
#3  0x7fbf1e5f312c in  () at /usr/lib/libGLX_nvidia.so.0
#4  0x7fbf416262e7 in start_thread () at /usr/lib/libpthread.so.0
#5  0x7fbf4208454f in clone () at /usr/lib/libc.so.6

Thread 43 (Thread 0x7f7dce038700 (LWP 8586)):
#0  0x7fbf4162c756 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fbf4277258b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fbf464c9665 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7fbf464c9f72 in  () at /usr/lib/libQt5Quick.so.5
#4  0x7fbf427716d8 in  () at /usr/lib/libQt5Core.so.5
#5  0x7fbf416262e7 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fbf4208454f in clone () at /usr/lib/libc.so.6

Thread 42 (Thread 0x7f7dce839700 (LWP 8583)):
#0  0x7fbf4162cca6 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fbf1e5f3e44 in  () at /usr/lib/libGLX_nvidia.so.0
#2  0x7fbf1d143394 in  () at /usr/lib/libnvidia-glcore.so.378.13
#3  0x7fbf1e5f312c in  () at /usr/lib/libGLX_nvidia.so.0
#4  0x7fbf416262e7 in start_thread () at /usr/lib/libpthread.so.0
#5  0x7fbf4208454f in clone () at /usr/lib/libc.so.6

Thread 41 (Thread 0x7f7de8bad700 (LWP 8582)):
#0  0x7fbf4162c756 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fbf4277258b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fbf464c9665 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7fbf464c9f72 in  () at /usr/lib/libQt5Quick.so.5
#4  0x7fbf427716d8 in  () at /usr/lib/libQt5Core.so.5
#5  0x7fbf416262e7 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fbf4208454f in clone () at /usr/lib/libc.so.6

Thread 40 (Thread 0x7f7de9be2700 (LWP 5372)):
#0  0x7fbf4162cca6 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fbf1e5f3e44 in  () at /usr/lib/libGLX_nvidia.so.0
#2  0x7fbf1d143394 in  () at /usr/lib/libnvidia-glcore.so.378.13
#3  0x7fbf1e5f312c in  () at /usr/lib/libGLX_nvidia.so.0
#4  0x7fbf416262e7 in start_thread () at /usr/lib/libpthread.so.0
#5  0x7fbf4208454f in clone () at /usr/lib/libc.so.6

Thread 39 (Thread 0x7f7dea3e3700 (LWP 5371)):
#0  0x7fbf4162c756 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fbf4277258b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fbf464c9665 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7fbf464c9f72 in  () at /usr/lib/libQt5Quick.so.5
#4  0x7fbf427716d8 in  () at /usr/lib/libQt5Core.so.5
#5  0x7fbf416262e7 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fbf4208454f in clone () at /usr/lib/libc.so.6

Thread 38 (Thread 0x7f7deafe4700 (LWP 2966)):
#0  0x7fbf4162cca6 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fbf1e5f3e44 in  () at /usr/lib/libGLX_nvidia.so.0
#2  0x7fbf1d143394 in  () at /usr/lib/libnvidia-glcore.so.378.13
#3  0x7fbf1e5f312c in  () at /usr/lib/libGLX_nvidia.so.0
#4  0x7fbf416262e7 in start_thread () at /usr/lib/libpthread.so.0
#5  0x7fbf4208454f in clone () at /usr/lib/libc.so.6

Thread 37 (Thread 0x7fbe024d8700 (LWP 2965)):
#0  0x7fbf4162c756 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fbf4277258b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fbf464c9665 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7fbf464c9f72 in  () 

[kmymoney] [Bug 378649] KMyMoney crashed while saving reports. Now cannot open KMyMoney .kmy file - "unable" to parse

[CraigH]

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

--- Comment #5 from CraigH  ---
Thank you for your prompt response.

I look forward to upgrading to Version 5 when it is available for Linux
Mint.

Best regards
Craig H

On 13/04/2017 12:48 am, "NSLW"  wrote:

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

NSLW  changed:

   What|Removed |Added

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

--- Comment #4 from NSLW  ---
(In reply to CraigH from comment #3)
> Created attachment 104976 [details]
> attachment-9374-0.html
>
> Hi Luka
>
> No backup "myFile.kmy.1~" file found.
> I did not have "number of backups to keep" set (was 0).
> Have recovered from a manual backup I made 3 hours previously, so don't
> need to send you my .kmy file
> My Current Version is 4.6.6-2 which is the only version in the repository
> for Linux Mint 18.1. Not sure I want to try and install 4.8 from another
> source.
>
> In Reports, the "convert values to base currencies" does not work
properly.
> Although I have updated the currencies and the window shows updated as at
> today's date USD>NZ $1.4370, that rate is not used in reports.
> The rate used in reports is  USD>NZ $1.2193.
> I can report in USD but would prefer to have all reports in local currency
> NZ $.
> Should I log a bug for this issue?
>
> Thank you for your prompt response.
>
> Craig H


I cannot reproduce your problem, no test file provided, and you use old
version
of KMM, so closing.
Don't report any bug report with currencies, because your problem is already
known and should work in 5.0.

--
You are receiving this mail because:
You reported the bug.
You are on the CC list for the bug.

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

[kwin] [Bug 378663] KWin won't draw Aurorae themes

[Mircea Kitsune]

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

--- Comment #5 from Mircea Kitsune  ---
An important note: The exact same bug is also happening on my mother's
computer! It also has the latest packages of openSUSE Tumbleweed, as well as an
AMD card. However hers is a much older model, and likely not RadeonSI (possibly
R600). This means it might be a general Radeon issue.

This is what lspci says on her machine:

VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV635 [Radeon
HD 3650/3750/4570/4580]

For that matter, this is what lspci says on mine:

VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO
[Radeon R7 370 / R9 270/370 OEM] (rev 81)

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

[kmail2] [Bug 362608] Default colours unusable on dark theme

[Denis Kurz]

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

--- Comment #8 from Denis Kurz  ---
(In reply to Salvo "LtWorf" Tomaselli from comment #7)
> It's an issue that takes 1 minute to reproduce, you didn't bother to try and
> then you close it when someone randomly comments something completely
> unrelated.

Why would anyone care to investigate a bug that was dismissed by the maintainer
if the reporter doesn't even care to defend the report? You didn't do so for 8
months, yet you blame me to take an action you didn't speak up against?

Which is the latest version you experienced this with? Can you share a
screenshot? My current setup makes it rather hard to even attempt to reproduce.

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

[krita] [Bug 378681] Krita occasionally save documents with resized layers

[Dmitry Kazakov]

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

--- Comment #11 from Dmitry Kazakov  ---
Git commit d71f0019e01266bd6b77638fcc37007937b40474 by Dmitry Kazakov.
Committed on 12/04/2017 at 15:20.
Pushed by dkazakov into branch 'krita/3.1'.

Add a warning dialog that the user is saving possibly corrupted image
Related: bug 361883

M  +12   -1libs/ui/KisMainWindow.cpp
M  +6-1libs/ui/dialogs/kis_delayed_save_dialog.cpp
M  +7-0libs/ui/dialogs/kis_delayed_save_dialog.h

https://commits.kde.org/krita/d71f0019e01266bd6b77638fcc37007937b40474

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

[krita] [Bug 378681] Krita occasionally save documents with resized layers

[Dmitry Kazakov]

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

--- Comment #10 from Dmitry Kazakov  ---
Git commit af9a7841964830f8752e1887d9d5b79658ade4ce by Dmitry Kazakov.
Committed on 12/04/2017 at 15:20.
Pushed by dkazakov into branch 'krita/3.1'.

Lock the image while saving

It is not enough to just disable cloning of the image,
locking should also be recovered.
Related: bug 361883

M  +55   -52   libs/ui/KisDocument.cpp

https://commits.kde.org/krita/af9a7841964830f8752e1887d9d5b79658ade4ce

--- Comment #11 from Dmitry Kazakov  ---
Git commit d71f0019e01266bd6b77638fcc37007937b40474 by Dmitry Kazakov.
Committed on 12/04/2017 at 15:20.
Pushed by dkazakov into branch 'krita/3.1'.

Add a warning dialog that the user is saving possibly corrupted image
Related: bug 361883

M  +12   -1libs/ui/KisMainWindow.cpp
M  +6-1libs/ui/dialogs/kis_delayed_save_dialog.cpp
M  +7-0libs/ui/dialogs/kis_delayed_save_dialog.h

https://commits.kde.org/krita/d71f0019e01266bd6b77638fcc37007937b40474

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

[krita] [Bug 378681] Krita occasionally save documents with resized layers

[Dmitry Kazakov]

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

--- Comment #10 from Dmitry Kazakov  ---
Git commit af9a7841964830f8752e1887d9d5b79658ade4ce by Dmitry Kazakov.
Committed on 12/04/2017 at 15:20.
Pushed by dkazakov into branch 'krita/3.1'.

Lock the image while saving

It is not enough to just disable cloning of the image,
locking should also be recovered.
Related: bug 361883

M  +55   -52   libs/ui/KisDocument.cpp

https://commits.kde.org/krita/af9a7841964830f8752e1887d9d5b79658ade4ce

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

[krita] [Bug 361883] many layer Auto scale smaller to top left size.

[Dmitry Kazakov]

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

Dmitry Kazakov  changed:

   What|Removed |Added

  Latest Commit|http://commits.kde.org/krit |https://commits.kde.org/kri
   |a/d5c39fbd21f3eed41a4675ed0 |ta/af9a7841964830f8752e1887
   |1ec5f9be38e4c57 |d9d5b79658ade4ce
 Resolution|--- |FIXED
 Status|REOPENED|RESOLVED

--- Comment #10 from Dmitry Kazakov  ---
Git commit d71f0019e01266bd6b77638fcc37007937b40474 by Dmitry Kazakov.
Committed on 12/04/2017 at 15:20.
Pushed by dkazakov into branch 'krita/3.1'.

Add a warning dialog that the user is saving possibly corrupted image
Related: bug 378681

M  +12   -1libs/ui/KisMainWindow.cpp
M  +6-1libs/ui/dialogs/kis_delayed_save_dialog.cpp
M  +7-0libs/ui/dialogs/kis_delayed_save_dialog.h

https://commits.kde.org/krita/d71f0019e01266bd6b77638fcc37007937b40474

--- Comment #11 from Dmitry Kazakov  ---
Git commit af9a7841964830f8752e1887d9d5b79658ade4ce by Dmitry Kazakov.
Committed on 12/04/2017 at 15:20.
Pushed by dkazakov into branch 'krita/3.1'.

Lock the image while saving

It is not enough to just disable cloning of the image,
locking should also be recovered.
Related: bug 378681

M  +55   -52   libs/ui/KisDocument.cpp

https://commits.kde.org/krita/af9a7841964830f8752e1887d9d5b79658ade4ce

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

[krita] [Bug 361883] many layer Auto scale smaller to top left size.

[Dmitry Kazakov]

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

Dmitry Kazakov  changed:

   What|Removed |Added

  Latest Commit|http://commits.kde.org/krit |https://commits.kde.org/kri
   |a/d5c39fbd21f3eed41a4675ed0 |ta/af9a7841964830f8752e1887
   |1ec5f9be38e4c57 |d9d5b79658ade4ce
 Resolution|--- |FIXED
 Status|REOPENED|RESOLVED

--- Comment #10 from Dmitry Kazakov  ---
Git commit d71f0019e01266bd6b77638fcc37007937b40474 by Dmitry Kazakov.
Committed on 12/04/2017 at 15:20.
Pushed by dkazakov into branch 'krita/3.1'.

Add a warning dialog that the user is saving possibly corrupted image
Related: bug 378681

M  +12   -1libs/ui/KisMainWindow.cpp
M  +6-1libs/ui/dialogs/kis_delayed_save_dialog.cpp
M  +7-0libs/ui/dialogs/kis_delayed_save_dialog.h

https://commits.kde.org/krita/d71f0019e01266bd6b77638fcc37007937b40474

--- Comment #11 from Dmitry Kazakov  ---
Git commit af9a7841964830f8752e1887d9d5b79658ade4ce by Dmitry Kazakov.
Committed on 12/04/2017 at 15:20.
Pushed by dkazakov into branch 'krita/3.1'.

Lock the image while saving

It is not enough to just disable cloning of the image,
locking should also be recovered.
Related: bug 378681

M  +55   -52   libs/ui/KisDocument.cpp

https://commits.kde.org/krita/af9a7841964830f8752e1887d9d5b79658ade4ce

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

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

[John Andersen]

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

--- Comment #245 from John Andersen  ---
Instead of posting yet more rambling rants and recipes for trying to make
activities work for this (most of which are unnecessarily complex and eliminate
other uses of activities) I encourage all to look into Post 212:
It simply works:

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

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

[krita] [Bug 378712] New: Lag

[maxi . mayrhofer800]

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

Bug ID: 378712
   Summary: Lag
   Product: krita
   Version: 3.1.2
  Platform: Windows CE
OS: Windows CE
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Brush engine
  Assignee: krita-bugs-n...@kde.org
  Reporter: maxi.mayrhofer...@gmail.com
  Target Milestone: ---

Lag

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

[plasma-nm] [Bug 377473] Plasma-nm doesn't store connection passwords encrypted anymore

[Theresa]

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

--- Comment #6 from Theresa  ---
Hi Jan,

unfortunately this is not the case as Kwallet is running:

tm1913 1  0 21:27 ?00:00:00 /usr/bin/kwalletd5
tm2253 1  0 21:27 ?00:00:00 /usr/bin/kwalletd5 --pam-login
15 18
tm2463  2355  0 21:27 ?00:00:00 /usr/bin/kwalletmanager5
-session 10e065726500014888287600034130029_1492025218_888983

Also, I was asked by KWallet if I wanted to allow the access from
NetworkManager

However, doing a tail on /var/log/syslog shows the following
Apr 12 21:29:44 herex NetworkManager[927]:   [1492025384.5414] device
(wlp58s0): No agents were available for this request.
Apr 12 21:29:44 herex NetworkManager[927]:   [1492025384.5415] device
(wlp58s0): state change: need-auth -> failed (reason 'no-secrets') [60 120 7]
Apr 12 21:29:44 herex NetworkManager[927]:   [1492025384.5420] device
(wlp58s0): Activation: failed for connection 'Wifi'
Apr 12 21:29:44 herex NetworkManager[927]:   [1492025384.5426] device
(wlp58s0): state change: failed -> disconnected (reason 'none') [120 30 0]
Apr 12 21:29:44 herex kernel: [  137.607891] IPv6: ADDRCONF(NETDEV_UP):
wlp58s0: link is not ready
Apr 12 21:29:55 herex NetworkManager[927]:   [1492025395.7890] device
(wlp58s0): Activation: starting connection 'Wifi'
(79a71c8c-a898-4012-b631-7f14d00bc068)
Apr 12 21:29:55 herex NetworkManager[927]:   [1492025395.7891] audit:
op="connection-activate" uuid="79a71c8c-a898-4012-b631-7f14d00bc068"
name="Wifi" pid=2410 uid=1001 result="success"
Apr 12 21:29:55 herex NetworkManager[927]:   [1492025395.7892] device
(wlp58s0): state change: disconnected -> prepare (reason 'none') [30 40 0]
Apr 12 21:29:55 herex NetworkManager[927]:   [1492025395.7896] device
(wlp58s0): state change: prepare -> config (reason 'none') [40 50 0]
Apr 12 21:29:55 herex NetworkManager[927]:   [1492025395.7898] device
(wlp58s0): Activation: (wifi) access point 'Wifi' has security, but secrets are
required.
Apr 12 21:29:55 herex NetworkManager[927]:   [1492025395.7898] device
(wlp58s0): state change: config -> need-auth (reason 'none') [50 60 0]
Apr 12 21:31:55 herex NetworkManager[927]:   [1492025515.8085] device
(wlp58s0): No agents were available for this request.
Apr 12 21:31:55 herex NetworkManager[927]:   [1492025515.8085] device
(wlp58s0): state change: need-auth -> failed (reason 'no-secrets') [60 120 7]
Apr 12 21:31:55 herex NetworkManager[927]:   [1492025515.8089] device
(wlp58s0): Activation: failed for connection 'Wifi'
Apr 12 21:31:55 herex kernel: [  268.880993] IPv6: ADDRCONF(NETDEV_UP):
wlp58s0: link is not ready
Apr 12 21:31:55 herex NetworkManager[927]:   [1492025515.8095] device
(wlp58s0): state change: failed -> disconnected (reason 'none') [120 30 0]

plasma-nm keeps saying "Waiting for authorization".

Unencrypted passwords workbut what's the point, right?

Is there any other way how we could troubleshoot this?

cheers,
theresa

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

[Akonadi] [Bug 245218] akonadi uses a lot of hard disk space Platform Version 4.5.60 (KDE 4.5.60 (KDE 4.6 >= 20100627)) "release 3"

[Matija Šuklje]

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

Matija Šuklje  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|RESOLVED|REOPENED
 Resolution|WORKSFORME  |---
 CC||mat...@suklje.name

--- Comment #9 from Matija Šuklje  ---
I just bumped into this bug on Mageia 5:

Akonadi 1.13.0
Qt: 4.8.6
KMail: 4.14.5


My ~/.local/share/akonadi/file_db_data takes up around 86 GiB, which even
though I have a 5 GiB IMAP inbox, is not *nearly* close to what it should be.

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

[krita] [Bug 378706] [WACOM] Eraser not switching to eraser.

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

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

--- Comment #1 from Boudewijn Rempt  ---
That was fixed in 3.1.3 beta.

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

[ksmserver] [Bug 356013] kdeinit crashed when using menu

[Gilberto Caetano de Andrade]

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

Gilberto Caetano de Andrade  changed:

   What|Removed |Added

 CC||gilbert...@gmail.com

--- Comment #1 from Gilberto Caetano de Andrade  ---
I can confirm this behavior. This happens periodically when selecting any icon
on the favorite - mainly Kmymoney:

Application: kdeinit5 (kdeinit5), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#4  0x7f6354b330c7 in raise () at /lib64/libc.so.6
#5  0x7f6354b34478 in abort () at /lib64/libc.so.6
#6  0x7f6354b70784 in  () at /lib64/libc.so.6
#7  0x7f6354b76026 in malloc_printerr () at /lib64/libc.so.6
#8  0x7f6354b76d53 in _int_free () at /lib64/libc.so.6
#9  0x7f6355eff026 in xcb_disconnect () at /usr/lib64/libxcb.so.1
#10 0x7f634cfccbd5 in  () at /usr/lib64/libkdeinit5_klauncher.so
#11 0x7f634cfccc55 in  () at /usr/lib64/libkdeinit5_klauncher.so
#12 0x7f634cfd9215 in  () at /usr/lib64/libkdeinit5_klauncher.so
#13 0x7f635515ccc6 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#14 0x7f63551de8ee in QSocketNotifier::activated(int,
QSocketNotifier::QPrivateSignal) () at /usr/lib64/libQt5Core.so.5
#15 0x7f6355169a89 in QSocketNotifier::event(QEvent*) () at
/usr/lib64/libQt5Core.so.5
#16 0x7f635512d18d in QCoreApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQt5Core.so.5
#17 0x7f635512ce95 in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /usr/lib64/libQt5Core.so.5
#18 0x7f6355181743 in QEventDispatcherUNIX::activateSocketNotifiers() () at
/usr/lib64/libQt5Core.so.5
#19 0x7f6355181beb in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () at /usr/lib64/libQt5Core.so.5
#20 0x7f6355181f3b in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#21 0x7f6348feb33d in  () at /usr/lib64/libQt5XcbQpa.so.5
#22 0x7f635512ad53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#23 0x7f63551328f6 in QCoreApplication::exec() () at
/usr/lib64/libQt5Core.so.5
#24 0x7f634cfd6a1a in kdemain () at /usr/lib64/libkdeinit5_klauncher.so
#25 0x004086fc in _start ()

# cat /etc/os-release 
NAME="openSUSE Leap"
VERSION="42.1"
VERSION_ID="42.1"
PRETTY_NAME="openSUSE Leap 42.1 (x86_64)"
ID=opensuse
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:opensuse:42.1"
BUG_REPORT_URL="https://bugs.opensuse.org;
HOME_URL="https://opensuse.org/;
ID_LIKE="suse"

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

[plasmashell] [Bug 378711] New: [Wayland] Qt and Gtk applications have two different copy stacks

[Germano Massullo]

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

Bug ID: 378711
   Summary: [Wayland] Qt and Gtk applications have two different
copy stacks
   Product: plasmashell
   Version: 5.9.4
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: generic-wayland
  Assignee: plasma-b...@kde.org
  Reporter: germano.massu...@gmail.com
  Target Milestone: 1.0

Qt and Gtk applications have two different copy & paste stacks.
During everyday computer usage, you happen to copy and paste various strings of
text. Now for example let's assume that if I paste into Konsole, I will get
"hello" text. And now let's paste into Firefox or another Gtk application: I
will get "how are you" instead of "hello".

In Klipper (I don't remember if it is the correct name), I do not see "how are
you" (the Gtk related paste)

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

[frameworks-kio] [Bug 350810] file open dialog freezes when browsing to /dev

[Thomas Eschenbacher]

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

--- Comment #4 from Thomas Eschenbacher  ---
I can confirm that the original bug seems to be fixed.

Only the display is wrong, the texts of the items are all positioned
overlapping over the preview symbols, which makes the dialog look ugly and the
texts unreadable.

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

[plasmashell] [Bug 378693] Activities are listed with a black background although wallpaper is set

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

   Target Milestone|--- |1.0
 CC||plasma-b...@kde.org
  Component|activities  |Activity Switcher
Product|kwin|plasmashell
   Assignee|kwin-bugs-n...@kde.org  |ivan.cu...@kde.org

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

[kwin] [Bug 347490] Crash when opening dialog windows (KWin::Workspace::desktopPresenceChanged)

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

 CC||lashk...@landau.ac.ru

--- Comment #13 from Martin Gräßlin  ---
*** Bug 378691 has been marked as a duplicate of this bug. ***

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

[kwin] [Bug 378691] Crash while importing phone calls via Wammu.

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

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

--- Comment #1 from Martin Gräßlin  ---


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

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

[plasmashell] [Bug 375860] Crash in QTXML Patterns parsing

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

Summary|Plasma Shell crash  |Crash in QTXML Patterns
   ||parsing

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

[kwin] [Bug 378688] Broken reflections in coverswitch on multi screen

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

  Component|multihead   |effects-tabbox
Summary|Glitch on alt-tab with  |Broken reflections in
   |multimonitor setup with |coverswitch on multi screen
   |different screen sizes  |

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

[plasmashell] [Bug 378660] Plasma crashes during regular usage

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

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

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


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

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

[plasmashell] [Bug 375860] Plasma Shell crash

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

 CC||bp1...@gmail.com

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

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

[frameworks-kio] [Bug 378546] KIOExec Error

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

Version|5.9.4   |unspecified
Product|plasmashell |frameworks-kio
  Component|general |general
   Assignee|k...@davidedmundson.co.uk|fa...@kde.org
   Target Milestone|1.0 |---
 CC||kdelibs-b...@kde.org

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

[kwin] [Bug 378710] New: OpenGL visual glitches for task switcher, desktop grid and window tiling.

[Szymon Łągiewka]

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

Bug ID: 378710
   Summary: OpenGL visual glitches for task switcher, desktop grid
and window tiling.
   Product: kwin
   Version: 5.9.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: compositing
  Assignee: kwin-bugs-n...@kde.org
  Reporter: bugs-...@lagiewka.pl
  Target Milestone: ---

For some time now (before 5.9.4 at least, update did not change anything) there
are some glitches that I (and turns out not only me
https://www.reddit.com/r/kde/comments/5zij0p/a_visual_glitch_in_the_task_switcher/)
have found inf Task Switcher, Desktop Grid effect and when a window is being
dragged for tiling into a specific area.

This happens when OpenGL 2.0/3.1 was selected. When I tried XRender (as the
reddit entry suggests) and everything works as it used to. That's why I'm
submitting the bug against KWin.

Screenshots: http://imgur.com/a/udzyD

For Task Switcher:
Task switching looks like on the screenshots 1 and 3. Expected behaviour is to
have background and selection on the switcher visible. 

For Desktop Grid:
The buttons (or at least their space) for adjusting the number of virtual
desktops is covered with a corner of a desktop. It can be seen on screenshot
number 2. 'Browse' text is from full screen Spotify window. Sometimes there is
a top panel with a part of the screen visible (so upper-left corner).

For window tiling:
When a window is dragged to an edge of the screen (no matter which,
top/right/left) the area that is going to be covered with resized window should
be painted (i.e. take the left half of the screen, upper-left quarter etc.).
This does not happen and the only effect is shown on the last screenshot from
the gallery.

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

[plasmashell] [Bug 378708] [Wayland] Konversation crash

[Germano Massullo]

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

--- Comment #1 from Germano Massullo  ---
Created attachment 104995
  --> https://bugs.kde.org/attachment.cgi?id=104995=edit
WAYLAND_DEBUG=1 konversation |& tee output.out

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

[dolphin] [Bug 378701] Option to disable frames with shadows on selected directories

[Elvis Angelaccio]

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

Elvis Angelaccio  changed:

   What|Removed |Added

 CC||elvis.angelac...@kde.org

--- Comment #1 from Elvis Angelaccio  ---
Please submit the patch here:
https://phabricator.kde.org/differential/diff/create/

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

[konsole] [Bug 343539] "Draw intense colors in bold font" not respected with a fresh installation

[Roberto Benfatto]

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

--- Comment #19 from Roberto Benfatto  ---
I followed Mike's qt bug report and as he suggested, I tried to look in
kdeglobals. I took an old KDE5 installation where this bug does not appear, I
updated it to the latest arch release. Then, confirming that it indeed works if
I don't touch anything, I changed the monospace font in the system settings,
then I compared the new kdeglobals file with the old one. I attached the diff,
as you can see all fonts where changed to a new format in the configuration
file, and that is the thing that breaks everything.
To double check, I restored the old kdeglobals file and bold fonts started
working again.

I think that the problem resides exactly there, as if konsole and other
programs (I suppose a lot of programs are affected by this) cannot apply a
different font style if one is explicitly specified in kdeglobals.
So, if this is the case, that's not a konsole only bug.

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

[konsole] [Bug 343539] "Draw intense colors in bold font" not respected with a fresh installation

[Roberto Benfatto]

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

--- Comment #18 from Roberto Benfatto  ---
Created attachment 104994
  --> https://bugs.kde.org/attachment.cgi?id=104994=edit
Difference between kdeglobals before and after font change

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

[okular] [Bug 378449] Fall back to PDF when file type cannot be inferred from extension

[Damian Nowak]

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

--- Comment #2 from Damian Nowak  ---
Okular 1.0.3, Arch Linux.

Filename "ViewPdfBills.aspx" -> error
Rename to "whatever.pdf" -> opens fine

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

[okular] [Bug 378473] Medieval Sharp font does not print bold correctly

[bugzilla_noreply]

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

--- Comment #3 from phoeni...@gmail.com ---
Testing PDF: http://fenikso.cz/Linux/test-okular.pdf
Photo of print: http://fenikso.cz/Linux/test-okular.jpg

I was not able to reproduce it on Canon printer (not sure about the specific
type) we have at work.
I am able to reproduce it on Samsung ML-2950.

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

[plasmashell] [Bug 378709] New: [Wayland] keyboard numlock status not always being recognized

[Germano Massullo]

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

Bug ID: 378709
   Summary: [Wayland] keyboard numlock status not always being
recognized
   Product: plasmashell
   Version: 5.9.4
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: generic-wayland
  Assignee: plasma-b...@kde.org
  Reporter: germano.massu...@gmail.com
  Target Milestone: 1.0

Plasma sometimes does not recognize keyboard numlock status, so instead of
writing numbers, it will act as if numlock is disabled.
To trigger it try enabling and disabling many times numlock

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

[plasmashell] [Bug 378708] New: [Wayland] Konversation crash

[Germano Massullo]

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

Bug ID: 378708
   Summary: [Wayland] Konversation crash
   Product: plasmashell
   Version: 5.9.4
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: generic-wayland
  Assignee: plasma-b...@kde.org
  Reporter: germano.massu...@gmail.com
  Target Milestone: 1.0

Konversation 1.6.2 crashes on Wayland.
Video driver: amdgpu


$ gdb konversation
GNU gdb (GDB) Fedora 7.12.1-47.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"...
Reading symbols from konversation...Reading symbols from
/usr/lib/debug/usr/bin/konversation.debug...done.
done.
(gdb) run
Starting program: /usr/bin/konversation 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
QObject::connect: invalid null parameter
[New Thread 0x7fffdaabc700 (LWP 23080)]
[New Thread 0x7fffd96a5700 (LWP 23081)]
[New Thread 0x7fffd1216700 (LWP 23083)]
[New Thread 0x7fffd0810700 (LWP 23084)]
[New Thread 0x7fffc947c700 (LWP 23085)]
[New Thread 0x7fffc8c7b700 (LWP 23086)]
[New Thread 0x7fffc847a700 (LWP 23087)]
[New Thread 0x7fffc45a9700 (LWP 23088)]
[New Thread 0x7fffc3b59700 (LWP 23089)]
[New Thread 0x7fffc3356700 (LWP 23090)]
[New Thread 0x7fffc2b55700 (LWP 23091)]
[New Thread 0x7fffc2354700 (LWP 23092)]


[Thread 0x7fffc3356700 (LWP 23090) exited]
[Thread 0x7fffc2354700 (LWP 23092) exited]
[Thread 0x7fffc3b59700 (LWP 23089) exited]
[Thread 0x7fffc45a9700 (LWP 23088) exited]
[Thread 0x7fffc2b55700 (LWP 23091) exited]
sonnet.core: No language dictionaries for the language: "it"
The Wayland connection broke. Did the Wayland compositor die?

Thread 2 "QDBusConnection" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffdaabc700 (LWP 23080)]
0x71b79f8d in QObject::disconnect (sender=0x7fffcc004ed0,
signal=signal@entry=0x0, receiver=receiver@entry=0x7fffd4011cc0,
method=method@entry=0x0) at kernel/qobject.cpp:2956
2956const QMetaObject *smeta = sender->metaObject();
(gdb) thread apply all backtrace

Thread 8 (Thread 0x7fffc847a700 (LWP 23087)):
#0  0x7fffef984460 in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fffd26d4c5b in cnd_wait (mtx=0x5607aa78, cond=0x5607aaa0) at
../../../include/c11/threads_posix.h:159
#2  0x7fffd26d4c5b in util_queue_thread_func
(input=input@entry=0x55f620b0) at util/u_queue.c:76
#3  0x7fffd26d4ab7 in impl_thrd_routine (p=) at
../../../include/c11/threads_posix.h:87
#4  0x7fffef97e6ca in start_thread (arg=0x7fffc847a700) at
pthread_create.c:333
#5  0x70da0f7f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 7 (Thread 0x7fffc8c7b700 (LWP 23086)):
#0  0x7fffef984460 in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fffd26d4c5b in cnd_wait (mtx=0x5607aa78, cond=0x5607aaa0) at
../../../include/c11/threads_posix.h:159
#2  0x7fffd26d4c5b in util_queue_thread_func
(input=input@entry=0x55f620b0) at util/u_queue.c:76
#3  0x7fffd26d4ab7 in impl_thrd_routine (p=) at
../../../include/c11/threads_posix.h:87
#4  0x7fffef97e6ca in start_thread (arg=0x7fffc8c7b700) at
pthread_create.c:333
#5  0x70da0f7f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 6 (Thread 0x7fffc947c700 (LWP 23085)):
#0  0x7fffef984460 in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fffd26d4c5b in cnd_wait (mtx=0x5607aa78, cond=0x5607aaa0) at
../../../include/c11/threads_posix.h:159
#2  0x7fffd26d4c5b in util_queue_thread_func
(input=input@entry=0x55f620b0) at util/u_queue.c:76
#3  0x7fffd26d4ab7 in impl_thrd_routine (p=) at
../../../include/c11/threads_posix.h:87
#4  0x7fffef97e6ca in start_thread (arg=0x7fffc947c700) at
pthread_create.c:333
#5  0x70da0f7f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 5 (Thread 0x7fffd0810700 (LWP 23084)):
#0  0x7fffef984460 in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fffd26d4c5b in cnd_wait (mtx=0x5607aa78, 

[drkonqi] [Bug 361198] crash while submit another bug because KDE wallet is off

[RJ]

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

RJ  changed:

   What|Removed |Added

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

--- Comment #2 from RJ  ---
https://bugs.kde.org/show_bug.cgi?id=361196

(In reply to Wolfgang Bauer from comment #6)
> Thanks for confirming!
> 
> I'll close it as duplicate then.
> 
> The backtrace shows exactly the same code lines inside kwallet, in
> particular KWallet::Wallet::isOpen (name=...) at
> /usr/src/debug/kwallet-5.20.0/src/api/KWallet/kwallet.cpp:366...
> That's exactly what the fix for bug#358260 touches:
> https://cgit.kde.org/kwallet.git/commit/
> ?id=48ec969bcf36fde17de027576859c98bae609c73
> 
> *** This bug has been marked as a duplicate of bug 358260 ***

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

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

[frameworks-kwallet] [Bug 358260] Drkonqi crashed during bugreport filling process

[RJ]

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

--- Comment #9 from RJ  ---
*** Bug 361198 has been marked as a duplicate of this bug. ***

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

[extra-cmake-modules] [Bug 375392] KConfig 5.30 and 5.31 do not compile with Macports/XCode under MacOS

[bugzilla_noreply]

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

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

   What|Removed |Added

   Version Fixed In||5.33.0
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED
Version|unspecified |5.30.0

--- Comment #9 from caulier.gil...@gmail.com ---
With KF5 5.33, now all is compilable under MAcOS through Macports.

Gilles Caulier

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