[kwin] [Bug 356128] Equivalent to "ShowDesktopIsMinimizeAll=true" is missing in plasma 5

[Thomas Lübking via KDE Bugzilla]

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

Thomas Lübking  changed:

   What|Removed |Added

   Severity|normal  |wishlist

--- Comment #1 from Thomas Lübking  ---
Since I asked you to file your thoughts about the minimize all script as
bug/wish, it's maybe required to clarify some things first.

* Show Desktop is the implementation of a NETWM spec, it's not gonna be removed
and not gonna turn into a kindly provided alternative.
* The purpose of Show Desktop is that: show the desktop for (intermediate)
interaction with it.
   It is especiallly NOT a concept to "unclutter" the desktop
* Your description fully supports my personal assumption that the demand for
the minimize all feature is mostly driven by carrying over some bad habits from
MS Windows. Unix desktops always had virtual desktops to organize the
workspace, there never was a need to minimize windows to "unclutter" things.

So on your plea:
> implement the equivalent of SDIMA=true in plasma 5
This needs to be discussed in this bug (notably on what was intended w/ the
original -hidden- feature and what and whether it is reasonable to accomplish
VDs)

> make it the default tool for de-cluttering the desktop
Not gonna happen.

> put a corresponding widget/button right beside the K-menu-button as the 
> default setting 
Wrong component (=> plasmashell) and the discussion about the default layout
needs to take place with the HIG group.

> if you must: keep "Show desktop" as an alternative
Already explained.

>  (I bet: few would miss it)
Please stick closely to the problem. If this turns into a flamewar, the bug
will be closed w/o resolution.

--

That said, let's check on the deviations of the script from now on (I'll note
them with the next post)

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

[systemsettings] [Bug 336089] Font preview - rendering problem

[Al via KDE Bugzilla]

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

Al  changed:

   What|Removed |Added

 CC||ahw...@verizon.net

--- Comment #23 from Al  ---
I am seeing the same as well, including the observation in comment #18.
Fedora 22 and 23 both display the problem, 22 is using NVIDIA 340 driver, 23 is
using nouveau.
Also my F22 and F23 virtual box machines have no problem at all.
All systems are current updates against the base and updates repositories, no
testing repo's.

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

[cantor] [Bug 356103] New: Python 3 backend is not functional

[Antonis G . via KDE Bugzilla]

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

Bug ID: 356103
   Summary: Python 3 backend is not functional
   Product: cantor
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: alexanderrie...@gmail.com
  Reporter: gaanto...@civil.auth.gr

When evaluating entries, the status bar says "Calculating..." but reults are
never returned. New variables don't show up in the Variable Manager.

Reproducible: Always

Steps to Reproduce:
Do something simple as "a = 1"



Cantor version 0.6

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

[telepathy] [Bug 355714] kdetalk - register new user button does not actually send a XMPP reg request

[Henning Hu via KDE Bugzilla]

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

Henning Hu  changed:

   What|Removed |Added

  Flags||kpeople+

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

[kdevplatform] [Bug 356016] Closing tabs hides/unhides left dock

[Kevin Funk via KDE Bugzilla]

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

Kevin Funk  changed:

   What|Removed |Added

  Latest Commit|http://commits.kde.org/kdev |http://commits.kde.org/kdev
   |platform/5e1af74f5038b6e39b |platform/7d8b19d95c2f586581
   |d959781e76df05d4e19479  |b6b0d073e862693b7e1333

--- Comment #3 from Kevin Funk  ---
Git commit 7d8b19d95c2f586581b6b0d073e862693b7e1333 by Kevin Funk.
Committed on 29/11/2015 at 14:23.
Pushed by kfunk into branch 'master'.

Dont hide/restore docks on double-click with RMB

M  +23   -1sublime/container.cpp

http://commits.kde.org/kdevplatform/7d8b19d95c2f586581b6b0d073e862693b7e1333

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

[kwin] [Bug 344326] Black or corrupted screen on resume from suspend

[Bas van Schaik via KDE Bugzilla]

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

Bas van Schaik  changed:

   What|Removed |Added

 CC|b...@tuxes.nl|

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

[plasmashell] [Bug 355985] user scrripts nolonger run correctly

[Treeve Jelbert via KDE Bugzilla]

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

Treeve Jelbert  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED

--- Comment #6 from Treeve Jelbert  ---
I moved the scripts from ~/.config/autostart to .config/plaswm-workspace/env

It now works correctly

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

[plasmashell] [Bug 355985] user scrripts nolonger run correctly

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |INVALID

--- Comment #7 from David Edmundson  ---
Ah, yes.

anything in "pre-startup" are run in a blocking way that sources any env
changes
anything in "startup" are forked into the background by ksmserver (and
therefore env changes dont' sync)

It's been like that since 4.x. AFAIK.

but I guess it's not super clear in the docs.

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

[kwin] [Bug 356107] New: Taskbar disappear when switched to fullscreen in a VNC session

[Jonathan via KDE Bugzilla]

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

Bug ID: 356107
   Summary: Taskbar disappear when switched to fullscreen in a VNC
session
   Product: kwin
   Version: 5.4.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: jbar...@gmail.com

Application: kwin_x11 (5.4.3)

Qt Version: 5.5.1
Operating System: Linux 4.1.13-1-MANJARO x86_64
Distribution: "Manjaro Linux"

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

Just connected to my remote machine using vncviewer

- Unusual behavior I noticed:

Plasma desktop crashes and no taskbar nor background image

- Custom settings of the application:

Just a startkde & in ~/.vnc/xstartup

The crash can be reproduced every time.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f3e179cd840 (LWP 1436))]

Thread 5 (Thread 0x7f3df698f700 (LWP 1461)):
#0  0x7f3e171efe23 in select () from /usr/lib/libc.so.6
#1  0x7f3e151bda2f in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timespec const*) () from /usr/lib/libQt5Core.so.5
#2  0x7f3e151bf507 in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () from /usr/lib/libQt5Core.so.5
#3  0x7f3e151bfa0e in
QEventDispatcherUNIX::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7f3e1516937a in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7f3e14f859c4 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7f3e0f439c85 in ?? () from /usr/lib/libQt5Qml.so.5
#7  0x7f3e14f8a96e in ?? () from /usr/lib/libQt5Core.so.5
#8  0x7f3e174b94a4 in start_thread () from /usr/lib/libpthread.so.0
#9  0x7f3e171f713d in clone () from /usr/lib/libc.so.6

Thread 4 (Thread 0x7f3df515d700 (LWP 1473)):
#0  0x7f3e174bf07f in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f3e13edf5e4 in ?? () from /usr/lib/libQt5Script.so.5
#2  0x7f3e13edf629 in ?? () from /usr/lib/libQt5Script.so.5
#3  0x7f3e174b94a4 in start_thread () from /usr/lib/libpthread.so.0
#4  0x7f3e171f713d in clone () from /usr/lib/libc.so.6

Thread 3 (Thread 0x7f3df75ef700 (LWP 1859)):
#0  0x7f3e174bf07f in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f3d64680b33 in ?? () from /usr/lib/xorg/modules/dri/swrast_dri.so
#2  0x7f3d64680997 in ?? () from /usr/lib/xorg/modules/dri/swrast_dri.so
#3  0x7f3e174b94a4 in start_thread () from /usr/lib/libpthread.so.0
#4  0x7f3e171f713d in clone () from /usr/lib/libc.so.6

Thread 2 (Thread 0x7f3df596e700 (LWP 1860)):
#0  0x7f3e174bf07f in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f3d64680b33 in ?? () from /usr/lib/xorg/modules/dri/swrast_dri.so
#2  0x7f3d64680997 in ?? () from /usr/lib/xorg/modules/dri/swrast_dri.so
#3  0x7f3e174b94a4 in start_thread () from /usr/lib/libpthread.so.0
#4  0x7f3e171f713d in clone () from /usr/lib/libc.so.6

Thread 1 (Thread 0x7f3e179cd840 (LWP 1436)):
[KCrash Handler]
#5  0x7f3e156f02c0 in QScreen::handle() const () from
/usr/lib/libQt5Gui.so.5
#6  0x7f3dfea69929 in QXcbIntegration::createPlatformWindow(QWindow*) const
() from /usr/lib/libQt5XcbQpa.so.5
#7  0x7f3e156d2234 in QWindowPrivate::create(bool) () from
/usr/lib/libQt5Gui.so.5
#8  0x7f3e156d2970 in QWindow::setVisible(bool) () from
/usr/lib/libQt5Gui.so.5
#9  0x7f3e0fcaca2b in QQuickWindowQmlImpl::qt_metacall(QMetaObject::Call,
int, void**) () from /usr/lib/libQt5Quick.so.5
#10 0x7f3e0f3b5c50 in QQmlPropertyPrivate::write(QObject*, QQmlPropertyData
const&, QVariant const&, QQmlContextData*,
QFlags) () from /usr/lib/libQt5Qml.so.5
#11 0x7f3e0f3b776b in QQmlPropertyPrivate::writeValueProperty(QObject*,
QQmlPropertyData const&, QVariant const&, QQmlContextData*,
QFlags) () from /usr/lib/libQt5Qml.so.5
#12 0x7f3e0f3b81bc in QQmlPropertyPrivate::writeBinding(QObject*,
QQmlPropertyData const&, QQmlContextData*, QQmlJavaScriptExpression*,
QV4::Value const&, bool, QFlags) () from
/usr/lib/libQt5Qml.so.5
#13 0x7f3e0f4260ef in
QQmlBinding::update(QFlags) () from
/usr/lib/libQt5Qml.so.5
#14 0x7f3e0f42651e in
QQmlBinding::expressionChanged(QQmlJavaScriptExpression*) () from
/usr/lib/libQt5Qml.so.5
#15 0x7f3e0f40245e in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*,
void**) () from /usr/lib/libQt5Qml.so.5
#16 0x7f3e0f3a4eec in QQmlData::signalEmitted(QAbstractDeclarativeData*,
QObject*, int, void**) () from /usr/lib/libQt5Qml.so.5
#17 0x7f3e15199a30 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/libQt5Core.so.5
#18 0x7f3e16d29a9e in ?? () from /usr/lib/libkwin.so.5
#19 

[plasmashell] [Bug 356108] New: plasma crash

[Germano Massullo via KDE Bugzilla]

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

Bug ID: 356108
   Summary: plasma crash
   Product: plasmashell
   Version: 5.4.3
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: germano.massu...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.4.3)

Qt Version: 5.5.1
Operating System: Linux 4.2.3-200.fc22.x86_64 x86_64
Distribution (Platform): Fedora RPMs

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

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

Thread 7 (Thread 0x7ff4f4118700 (LWP 22390)):
#0  0x0031014f72fd in poll () at /lib64/libc.so.6
#1  0x003105c0a182 in _xcb_conn_wait (__timeout=-1, __nfds=1,
__fds=0x7ff4f4117bc0) at /usr/include/bits/poll2.h:46
#2  0x003105c0a182 in _xcb_conn_wait (c=c@entry=0x9360a0,
cond=cond@entry=0x9360e0, vector=vector@entry=0x0, count=count@entry=0x0) at
xcb_conn.c:459
#3  0x003105c0bc77 in xcb_wait_for_event (c=0x9360a0) at xcb_in.c:648
#4  0x7ff4f4d28da9 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5
#5  0x00302f6a33ce in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#6  0x003101807555 in start_thread (arg=0x7ff4f4118700) at
pthread_create.c:333
#7  0x003101502b9d in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7ff4f148e700 (LWP 22394)):
#0  0x003104449d43 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#1  0x003104449ecc in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#2  0x00302f8daf0b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#3  0x00302f881f0a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#4  0x00302f69e424 in QThread::exec() () at /lib64/libQt5Core.so.5
#5  0x00303e8d9b45 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5
#6  0x00302f6a33ce in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#7  0x003101807555 in start_thread (arg=0x7ff4f148e700) at
pthread_create.c:333
#8  0x003101502b9d in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7ff4e9c14700 (LWP 22395)):
#0  0x0031014f72fd in poll () at /lib64/libc.so.6
#1  0x003104449dbc in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x003104449ecc in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x00302f8daf0b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x00302f881f0a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x00302f69e424 in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x00303e8d9b45 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5
#7  0x00302f6a33ce in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x003101807555 in start_thread (arg=0x7ff4e9c14700) at
pthread_create.c:333
#9  0x003101502b9d in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7ff4dfdc8700 (LWP 22400)):
#0  0x0031014f72fd in poll () at /lib64/libc.so.6
#1  0x003104449dbc in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x003104449ecc in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x00302f8daf0b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x00302f881f0a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x00302f69e424 in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x00303e8d9b45 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5
#7  0x00302f6a33ce in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x003101807555 in start_thread (arg=0x7ff4dfdc8700) at
pthread_create.c:333
#9  0x003101502b9d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7ff4de580700 (LWP 22401)):
#0  0x00310180c540 in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x003040385514 in QTWTF::TCMalloc_PageHeap::scavengerThread() () at
/lib64/libQt5Script.so.5
#2  0x003040385559 in  () at /lib64/libQt5Script.so.5
#3  0x003101807555 in start_thread (arg=0x7ff4de580700) at
pthread_create.c:333
#4  0x003101502b9d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7ff4d7677700 (LWP 22711)):
#0  0x0031014f2fad in read () at /lib64/libc.so.6
#1  0x7ff4fe501f45 in  () at
/usr/lib64/nvidia-340xx/tls/libnvidia-tls.so.340.93
#2  0x00310448db00 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0
#3  0x0031044498b4 in g_main_context_check () at /lib64/libglib-2.0.so.0
#4  0x003104449d60 in g_main_context_iterate.isra () at

[kwin] [Bug 352427] EGL compositing problems, update only every other bookmark item in Chrome and Launcher

[kamesh via KDE Bugzilla]

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

--- Comment #12 from kamesh  ---
Now created /etc/X11/xorg.conf.d/ and kept the file there. Removed it from
/usr/share/X11/xorg.conf.d/. Checked my Xorg.0.log. Link below. It shows
reference to DRI 3. The problem is still not solved. There seems to be
references to DRI 2 in my xorg.0.log file. I am not sure how to discern it. 

http://pastebin.com/cdDEgS80

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

[trojita] [Bug 332911] Offer autocomplete (or dropdown) for "Sent" folder choice

[Jan Kundrát via KDE Bugzilla]

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

Jan Kundrát  changed:

   What|Removed |Added

 CC||foster2cbran...@gmail.com

--- Comment #3 from Jan Kundrát  ---
*** Bug 356121 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 355858] digital clock does not display anything

[M G Berberich via KDE Bugzilla]

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

--- Comment #6 from M G Berberich  ---
That’s probably distribution dependent.
On Debian “dpkg-reconfigure tzdata” copies a file from /usr/share/zoneinfo/ to
/etc. In my case “/usr/share/zoneinfo/Europe/Berlin“ and “/etc/localtime” are
identical.

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

[kio] [Bug 326880] Dolphin is unable to utilize CoW feature of btrfs

[Edward O'Callaghan via KDE Bugzilla]

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

--- Comment #6 from Edward O'Callaghan  ---
kio could additionally support BTRFS's snapshot facilities too. aka. Apple^tm
Timemachine^{H. G. Wells} (sorry Jobs..)

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

[kate] [Bug 356118] word highlight selection plugin includes special character

[via KDE Bugzilla]

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

gillesgalip...@gmail.com changed:

   What|Removed |Added

 CC||gillesgalip...@gmail.com

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

[kde] [Bug 356119] New: Keyboard KDE control module configuration takes long time to start and crashes on close button

[via KDE Bugzilla]

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

Bug ID: 356119
   Summary: Keyboard KDE control module configuration takes long
time to start and crashes on close button
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: dusan.pet...@gmail.com

Application: kdeinit5 (5.4.2)

Qt Version: 5.5.0
Operating System: Linux 4.1.12-1-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
I have clicked the close button.
I have clicked the close button.
Bugtracker, are you happy with the lenght now?

The crash can be reproduced sometimes.

-- Backtrace:
Application: KDE Control Module (kdeinit5), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fb614245780 (LWP 25118))]

Thread 14 (Thread 0x7fb5fd1bf700 (LWP 25119)):
#0  0x7fb6125d7c1d in poll () at /lib64/libc.so.6
#1  0x7fb611add422 in  () at /usr/lib64/libxcb.so.1
#2  0x7fb611adf00f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7fb5ffb45c29 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7fb61294c55f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7fb60ff510a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7fb6125e004d in clone () at /lib64/libc.so.6

Thread 13 (Thread 0x7fb5f53dd700 (LWP 25178)):
[KCrash Handler]
#6  0x7fb61257323b in malloc_consolidate () at /lib64/libc.so.6
#7  0x7fb612574588 in _int_malloc () at /lib64/libc.so.6
#8  0x7fb6125770cc in calloc () at /lib64/libc.so.6
#9  0x7fb60e315279 in  () at /usr/lib64/tls/libnvidia-tls.so.352.55
#10 0x7fb60f29b4e9 in g_malloc0 () at /usr/lib64/libglib-2.0.so.0
#11 0x7fb60f267b6b in  () at /usr/lib64/libglib-2.0.so.0
#12 0x7fb60f2b17a9 in g_slice_free1 () at /usr/lib64/libglib-2.0.so.0
#13 0x7fb60ff50e62 in __nptl_deallocate_tsd () at /lib64/libpthread.so.0
#14 0x7fb60ff510b7 in start_thread () at /lib64/libpthread.so.0
#15 0x7fb6125e004d in clone () at /lib64/libc.so.6

Thread 12 (Thread 0x7fb5f4bdc700 (LWP 25179)):
#0  0x7fb6125dbfd9 in syscall () at /lib64/libc.so.6
#1  0x7fb6129458ac in QBasicMutex::lockInternal() () at
/usr/lib64/libQt5Core.so.5
#2  0x7fb61294d514 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#3  0x7fb612949716 in  () at /usr/lib64/libQt5Core.so.5
#4  0x7fb61294c55f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7fb60ff510a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7fb6125e004d in clone () at /lib64/libc.so.6

Thread 11 (Thread 0x7fb5f43db700 (LWP 25180)):
#0  0x7fb6125dbfd9 in syscall () at /lib64/libc.so.6
#1  0x7fb6129458ac in QBasicMutex::lockInternal() () at
/usr/lib64/libQt5Core.so.5
#2  0x7fb61294d514 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#3  0x7fb612949716 in  () at /usr/lib64/libQt5Core.so.5
#4  0x7fb61294c55f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7fb60ff510a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7fb6125e004d in clone () at /lib64/libc.so.6

Thread 10 (Thread 0x7fb5f3bda700 (LWP 25181)):
#0  0x7fb6125dbfd9 in syscall () at /lib64/libc.so.6
#1  0x7fb6129458ac in QBasicMutex::lockInternal() () at
/usr/lib64/libQt5Core.so.5
#2  0x7fb61294d514 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#3  0x7fb612949716 in  () at /usr/lib64/libQt5Core.so.5
#4  0x7fb61294c55f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7fb60ff510a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7fb6125e004d in clone () at /lib64/libc.so.6

Thread 9 (Thread 0x7fb5f33d9700 (LWP 25182)):
#0  0x7fb6125ec5cb in __lll_lock_wait_private () at /lib64/libc.so.6
#1  0x7fb6125788a9 in _L_lock_3741 () at /lib64/libc.so.6
#2  0x7fb612573b9b in _int_free () at /lib64/libc.so.6
#3  0x7fb60f2b0a26 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7fb60f2b0b92 in  () at /usr/lib64/libglib-2.0.so.0
#5  0x7fb60ff50e62 in __nptl_deallocate_tsd () at /lib64/libpthread.so.0
#6  0x7fb60ff510b7 in start_thread () at /lib64/libpthread.so.0
#7  0x7fb6125e004d in clone () at /lib64/libc.so.6

Thread 8 (Thread 0x7fb5f2bd8700 (LWP 25183)):
#0  0x7fb6125dbfd9 in syscall () at /lib64/libc.so.6
#1  0x7fb6129458ac in QBasicMutex::lockInternal() () at
/usr/lib64/libQt5Core.so.5
#2  0x7fb61294d514 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#3  0x7fb612949716 in  () at /usr/lib64/libQt5Core.so.5
#4  0x7fb61294c55f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7fb60ff510a4 in start_thread () at /lib64/libpthread.so.0
#6  

[plasmashell] [Bug 348792] KDE Plasma5 Pager does not adjust to the size of the panel in the vertical mode

[kamesh via KDE Bugzilla]

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

kamesh  changed:

   What|Removed |Added

 CC||antonis.tsiapalio...@kde.or
   ||g, bhus...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.
You are on the CC list for the bug.

[kate] [Bug 356118] word highlight selection plugin includes special character

[via KDE Bugzilla]

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

--- Comment #1 from gillesgalip...@gmail.com ---
This is seen with Kate 3.13.3 using KDE 4.13.3

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

[Breeze] [Bug 356037] Confusing indication of active tab (Konsole)

[Hugo Pereira Da Costa via KDE Bugzilla]

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

--- Comment #7 from Hugo Pereira Da Costa  ---
(In reply to kdde.rhn from comment #6)
> Created attachment 95811 [details]
> Tab focus indication that doesn't rely on tab content style
> 
> Clearlooks/Darklooks GTK.

Hi, 

thanks for the screenshot. 

My argument is that in the "similar" breeze screenshot, the active tab would be
as distinguishable as in these screenshot. (it is the one that is connected to
the tab content, and has the same color), without needing to add the top
coloured band. You agree ? 

The same is true when you have more than two tabs in konsole, and really the
problem is there only for the case that you mention: only two tabs, and no tab
content. I would find it a pitty to have to change the "default" look
everywhere (and adding what I'd consider clutter), just for this one case. I'd
rather rely on people getting "used to" how the active tab looks ...

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

[calligraplan] [Bug 356125] New: Indent of task makes Plan crash

[Felix Zesch via KDE Bugzilla]

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

Bug ID: 356125
   Summary: Indent of task makes Plan crash
   Product: calligraplan
   Version: 2.8.1
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kosse...@kde.org
  Reporter: xelzife...@web.de

Application: calligraplan (2.8.1)
KDE Platform Version: 4.14.2
Qt Version: 4.8.6
Operating System: Linux 4.2.0-18-generic x86_64
Distribution: Linux Mint 17.2 Rafaela

-- Information about the crash:
- What I was doing when the application crashed: I had three tasks with several
subtasks. I added a new task with ctrl-i below those tasks and then clicked
with the mouse on "indent". Application crashed then

-- Backtrace:
Application: Plan (calligraplan), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fb1052bb7c0 (LWP 3858))]

Thread 3 (Thread 0x7fb0e6394700 (LWP 3859)):
#0  0x7fb104c0d82d in read () at ../sysdeps/unix/syscall-template.S:81
#1  0x7fb0ffc10c10 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fb0ffbcfb14 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fb0ffbcff7b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fb0ffbd00ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fb1033267be in QEventDispatcherGlib::processEvents
(this=0x7fb0e8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#6  0x7fb1032f80af in QEventLoop::processEvents
(this=this@entry=0x7fb0e6393de0, flags=...) at kernel/qeventloop.cpp:149
#7  0x7fb1032f83a5 in QEventLoop::exec (this=this@entry=0x7fb0e6393de0,
flags=...) at kernel/qeventloop.cpp:204
#8  0x7fb1031f4c5f in QThread::exec (this=this@entry=0xf92cc0) at
thread/qthread.cpp:537
#9  0x7fb1032d9823 in QInotifyFileSystemWatcherEngine::run (this=0xf92cc0)
at io/qfilesystemwatcher_inotify.cpp:265
#10 0x7fb1031f732f in QThreadPrivate::start (arg=0xf92cc0) at
thread/qthread_unix.cpp:349
#11 0x7fb1000af182 in start_thread (arg=0x7fb0e6394700) at
pthread_create.c:312
#12 0x7fb104c1c47d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 2 (Thread 0x7fb0de84e700 (LWP 3878)):
#0  0x7fb104c0d82d in read () at ../sysdeps/unix/syscall-template.S:81
#1  0x7fb0ffc10c10 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fb0ffbcfb14 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fb0ffbcff7b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fb0ffbd00ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fb1033267be in QEventDispatcherGlib::processEvents
(this=0x7fb0d80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#6  0x7fb1032f80af in QEventLoop::processEvents
(this=this@entry=0x7fb0de84dde0, flags=...) at kernel/qeventloop.cpp:149
#7  0x7fb1032f83a5 in QEventLoop::exec (this=this@entry=0x7fb0de84dde0,
flags=...) at kernel/qeventloop.cpp:204
#8  0x7fb1031f4c5f in QThread::exec (this=this@entry=0x1cc8750) at
thread/qthread.cpp:537
#9  0x7fb1032d9823 in QInotifyFileSystemWatcherEngine::run (this=0x1cc8750)
at io/qfilesystemwatcher_inotify.cpp:265
#10 0x7fb1031f732f in QThreadPrivate::start (arg=0x1cc8750) at
thread/qthread_unix.cpp:349
#11 0x7fb1000af182 in start_thread (arg=0x7fb0de84e700) at
pthread_create.c:312
#12 0x7fb104c1c47d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7fb1052bb7c0 (LWP 3858)):
[KCrash Handler]
#6  deref (this=0x1a) at
../../include/QtCore/../../src/corelib/arch/qatomic_x86_64.h:133
#7  QPersistentModelIndex::~QPersistentModelIndex (this=0x7fb0d4005318,
__in_chrg=) at kernel/qabstractitemmodel.cpp:154
#8  0x7fb10426134d in ~QPair (this=0x7fb0d4005300, __in_chrg=) at ../../include/QtCore/../../src/corelib/tools/qpair.h:54
#9  node_destruct (this=, to=0x7fb0d4018b98,
from=0x7fb0d4018b88) at
../../include/QtCore/../../src/corelib/tools/qlist.h:431
#10 QList >::free
(data=0x7fb0d4018b70, this=) at
../../include/QtCore/../../src/corelib/tools/qlist.h:757
#11 0x7fb10426a828 in operator= (l=..., this=0x19459e8) at
../../include/QtCore/../../src/corelib/tools/qlist.h:443
#12 QList >::clear
(this=this@entry=0x19459e8) at
../../include/QtCore/../../src/corelib/tools/qlist.h:766
#13 0x7fb104263b30 in
QSortFilterProxyModelPrivate::_q_sourceLayoutAboutToBeChanged (this=0x19458d0)
at itemviews/qsortfilterproxymodel.cpp:1256
#14 0x7fb10330d87a in QMetaObject::activate (sender=sender@entry=0x193d0b0,
m=m@entry=0x7fb10365d6a0 ,
local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x0) at

[krecipes] [Bug 355995] can not open the program by the menu

[Albert Astals Cid via KDE Bugzilla]

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

--- Comment #9 from Albert Astals Cid  ---
Do you have a file named
 /usr/share/applications/kde4/krecipes.desktop
?

If so can you run 
   grep Exec /usr/share/applications/kde4/krecipes.desktop
and print its output?

If not you'll have to use your package manater to try to find the file and then
run the same grep command

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

[valgrind] [Bug 343306] OS X 10.10: UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option

[Daniel Trebbien via KDE Bugzilla]

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

--- Comment #5 from Daniel Trebbien  ---
(In reply to Rhys Kidd from comment #4)
> Daniel,
> That does sound like a separate bug report. Can you please create a new bug
> report with the details you've provided here.

Sure, I have created Bug 356122.

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

[digikam] [Bug 355831] MySQL Schema Improvements

[Richard Mortimer via KDE Bugzilla]

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

--- Comment #36 from Richard Mortimer  ---
Created attachment 95824
  --> https://bugs.kde.org/attachment.cgi?id=95824=edit
Standalone MySQL face recognition settings to FaceSettings table

Update face recognition MySQL support.

Use FaceSettings table to allow shared database in MySQL.
Use InnoDB engine to ensure that foreign key relationships are enforced.
Use foreign key between Identities and IdentityAttributes.

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

[digikam] [Bug 355831] MySQL Schema Improvements

[Richard Mortimer via KDE Bugzilla]

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

Richard Mortimer  changed:

   What|Removed |Added

  Attachment #95755|0   |1
is obsolete||

--- Comment #35 from Richard Mortimer  ---
Created attachment 95823
  --> https://bugs.kde.org/attachment.cgi?id=95823=edit
Standalone MySQL Thumbnail settings to ThumbSettings table

Move Thumbnail database Settings to ThumbSettings for MySQL

This allows the thumbnail and main image databases to be contained within the
same database.

Also ensure that thumbnail MySQL tables use the InnoDB storage engine and not
the older MyISAM engine.

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

[frameworks-kactivities] [Bug 355478] [abrt] kf5-kactivities: kactivitymanagerd killed by SIGSEGV

[Ivan Čukić via KDE Bugzilla]

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

Ivan Čukić  changed:

   What|Removed |Added

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

--- Comment #2 from Ivan Čukić  ---
This has been revamped. The crashes should not appear any more (at least, not
here ;) )

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

[plasmashell] [Bug 355625] Hotkey Switching of Activities Locks up Plasma

[Ivan Čukić via KDE Bugzilla]

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

--- Comment #2 from Ivan Čukić  ---
Hi Marina,

Thanks for reporting this.

This should be fixed in the next release of Plasma. At least a similar issue
has been resolved - QML in the activity switcher gets into an infinite loop
constantly trying to re-layout everything.

Just in case, can you test the following - when plasma starts, switch
activities using the mouse, and after that try to use meta+tab to switch again.

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

[amarok] [Bug 355972] Double-clicking a track in the playlist results in unexpected behaviour

[Trevor Parsons via KDE Bugzilla]

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

Trevor Parsons  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |INVALID
 Status|NEEDSINFO   |RESOLVED

--- Comment #4 from Trevor Parsons  ---
(In reply to Myriam Schweingruber from comment #3)
> Very weird, I don't see what could have been changed that causes this, there
> have been no changes in current git affecting the playlist or the playback.
> Could you try with a new user?

I should have tried the new user test before reporting this. It did the trick.

I've therefore removed/renamed the majority of the KDE and Plasma settings
files from my own user account and now have a refreshed desktop, in which
Amarok does not exhibit the reported problem behaviour.

For interest, I think this was also related to the fact that double-clicking on
a word in, for example, Konsole, would not result in the normal behaviour of
that word becoming selected, because this has also been resolved.

I suppose this kind of hard-to-identify problem is liable to happen after lots
of upgrades. Thanks for your help Myriam, and sorry for troubling you
unnecessarily!

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

[okular] [Bug 356127] "Save as" dialog for "Save copy as": path editing widget and list widget out of sync

[Thomas Fischer via KDE Bugzilla]

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

--- Comment #1 from Thomas Fischer  ---
When reporting this bug in KDE's Bugzilla, version 1.0.0 was not in the list of
available versions. This should be fixed as well.

I am using Okular 1.0.0 on KDE Frameworks 5.16.0 using Qt 5.5.1 on X11/xcb.

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

[kdenlive] [Bug 354778] Add G'MIC effects to Kdenlive

[Micah Pendleton via KDE Bugzilla]

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

Micah Pendleton  changed:

   What|Removed |Added

 CC||filmworl...@gmail.com

--- Comment #1 from Micah Pendleton  ---
I would LOVE to see G'mic implemented in Kdenlive!

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

[kdevelop] [Bug 354143] Unclear output when building cpp project using cmake

[Piotr Mierzwinski via KDE Bugzilla]

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

Piotr Mierzwinski  changed:

   What|Removed |Added

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

--- Comment #12 from Piotr Mierzwinski  ---
Sorry, but for me this is not fixed. I expected quite different output. I mean
output like this generated by KDevelop4 - attachment:
"qtcmd2_build_kdevelop4_output (pretty output generated by KDevelop4" or same
like is produced in terminal: attachment "kate_build_terminal_make_-j2". Other
are wrong. Thus such output where in almost every lines I get percentage
indicator. After this fix I get periodically percentage indicator. 
I made the tests with my project (qtcmd2) and with yours: kdevelop.
I tested building with 2, 4, and 8 jobs.

Before building I've checked only one plugin referring to build:
* Settings -> Plugins: "Build project by CMake"
In option "Loaded plugins" also there was visible "Building by make" despite in
"Configure plugins" is unchecked. The most likely one is dependent on the
second, so that's mean lack of consistency or minor bug.

* Project configuration:
Default cmake executable: /usr/bin/cmake
(but after pressing OK it has been reset to empty value - It doesn't matter
because cmake works)
Generator: Unix Makefile

Configure cmake settings:
QT_QMAKE_EXECUTABLE  /usr/bin/qmake-qt4

Configure Make settings:
- test1: "Number of simultaneous jobs:" 8
- test2: "Number of simultaneous jobs:" 4
- test3: "Number of simultaneous jobs:" 2

Make executable:  make
Active environment profile:  default

In kdevelop case percentage indicator appeared only with only following lines:
[  6%] Automatic moc for target test_gdb
[ 52%] Linking CXX executable debugeeqt

In my project
[ 37%] Scanning dependencies of target qtcmd2tarsubsystem
[ 61%] Linking CXX shared library 
When I built using 2 jobs then there wasn't no one percentage indicator
(despite there were "Scanning dependencies..." strings in output).

And if you check attachments you will see that not everyone matching (to above
template) lines have percentage indicator :/. So it means that this is randomly
:(. Second issue is that sometimes lines are starting with a capital letter and
sometimes not. Building in terminal I didn't notice it.

This test I've made on Kubuntu 15.10 with following tools:
# cmake --version
cmake version 3.2.2
# make --version
GNU Make 4.0
# gcc --version
gcc (Ubuntu 5.2.1-22ubuntu2) 5.2.1 20151010

On the end I built my project being in terminal - attachment:
"qtcmd2_build_j4_terminal_output". Thanks that I found where is the bug. It
turned out that percentage indicator is displayed with lines where should not
be displayed. There is in "Scanning dependencies" and should be for example in
"Building ...". There is in every place where should not be.

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

[kdevelop] [Bug 354143] Unclear output when building cpp project using cmake

[Piotr Mierzwinski via KDE Bugzilla]

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

--- Comment #16 from Piotr Mierzwinski  ---
Created attachment 95833
  --> https://bugs.kde.org/attachment.cgi?id=95833=edit
qtcmd2_build_j4_terminal_output

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

[plasmashell] [Bug 356135] New: Plasma crashes regularly with second monitor

[via KDE Bugzilla]

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

Bug ID: 356135
   Summary: Plasma crashes regularly with second monitor
   Product: plasmashell
   Version: 5.4.2
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: pearceb...@hotmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.4.2)

Qt Version: 5.5.0
Operating System: Linux 4.1.12-1-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
A television attached via HDMI as a second monitor had just been turned off.
- Unusual behavior I noticed:
The main desktop background regularly changes to the second monitor background,
especially following a suspend caused by the screen closing. Full windows
regularly go under the bottom task bar, though they work when the computer is
first turned on. The entire system of plasma stops working with regularity. 
- Custom settings of the application:
television hooked up to computer via HDMI, television is regularly used on a
differetnt input setting.

The crash can be reproduced sometimes.

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

Thread 18 (Thread 0x7ff767c01700 (LWP 14517)):
#0  0x7ff7762dec1d in poll () from /lib64/libc.so.6
#1  0x7ff77b245422 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7ff77b24700f in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7ff76a3b9c29 in ?? () from /usr/lib64/libQt5XcbQpa.so.5
#4  0x7ff7769dc55f in QThreadPrivate::start (arg=0x1e63420) at
thread/qthread_unix.cpp:331
#5  0x7ff775ada0a4 in start_thread () from /lib64/libpthread.so.0
#6  0x7ff7762e704d in clone () from /lib64/libc.so.6

Thread 17 (Thread 0x7ff764ba9700 (LWP 14561)):
#0  0x7ff7729afd14 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0
#1  0x7ff77296d8e9 in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#2  0x7ff77296ddf8 in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x7ff77296df7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#4  0x7ff776c0da5b in QEventDispatcherGlib::processEvents
(this=0x7ff7580008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7ff776bb4a63 in QEventLoop::exec (this=this@entry=0x7ff764ba8df0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7ff7769d784a in QThread::exec (this=this@entry=0x1f389b0) at
thread/qthread.cpp:503
#7  0x7ff779ce25f8 in QQmlThreadPrivate::run (this=0x1f389b0) at
/usr/src/debug/qtdeclarative-opensource-src-5.5.0/src/qml/qml/ftw/qqmlthread.cpp:141
#8  0x7ff7769dc55f in QThreadPrivate::start (arg=0x1f389b0) at
thread/qthread_unix.cpp:331
#9  0x7ff775ada0a4 in start_thread () from /lib64/libpthread.so.0
#10 0x7ff7762e704d in clone () from /lib64/libc.so.6

Thread 16 (Thread 0x7ff751099700 (LWP 14562)):
#0  0x7ff77296d7b5 in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#1  0x7ff77296ddf8 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7ff77296df7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7ff776c0da5b in QEventDispatcherGlib::processEvents
(this=0x7ff74c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7ff776bb4a63 in QEventLoop::exec (this=this@entry=0x7ff751098df0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7ff7769d784a in QThread::exec (this=this@entry=0x217b860) at
thread/qthread.cpp:503
#6  0x7ff779ce25f8 in QQmlThreadPrivate::run (this=0x217b860) at
/usr/src/debug/qtdeclarative-opensource-src-5.5.0/src/qml/qml/ftw/qqmlthread.cpp:141
#7  0x7ff7769dc55f in QThreadPrivate::start (arg=0x217b860) at
thread/qthread_unix.cpp:331
#8  0x7ff775ada0a4 in start_thread () from /lib64/libpthread.so.0
#9  0x7ff7762e704d in clone () from /lib64/libc.so.6

Thread 15 (Thread 0x7ff74b641700 (LWP 14565)):
#0  0x7ff7762dec1d in poll () from /lib64/libc.so.6
#1  0x7ff77296de64 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7ff77296df7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7ff776c0da5b in QEventDispatcherGlib::processEvents
(this=0x7ff7440008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7ff776bb4a63 in QEventLoop::exec (this=this@entry=0x7ff74b640df0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7ff7769d784a in QThread::exec (this=this@entry=0x232fe10) at
thread/qthread.cpp:503
#6  0x7ff779ce25f8 in QQmlThreadPrivate::run (this=0x232fe10) at
/usr/src/debug/qtdeclarative-opensource-src-5.5.0/src/qml/qml/ftw/qqmlthread.cpp:141
#7  

[kmymoney] [Bug 356137] New: update stock prices will not run

[Gorden via KDE Bugzilla]

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

Bug ID: 356137
   Summary: update stock prices will not  run
   Product: kmymoney
   Version: unspecified
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: kmymoney-de...@kde.org
  Reporter: ghfr...@gmail.com

Would not fetch prices

Reproducible: Always

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

[valgrind] [Bug 356138] New: vex amd64->IR unhandled instruction bytes 0x8F 0xEA 0x78 0x10 0xD2 0x6 0x6 0x0

[Andreas Boerner via KDE Bugzilla]

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

Bug ID: 356138
   Summary: vex amd64->IR unhandled instruction bytes 0x8F 0xEA
0x78 0x10 0xD2 0x6 0x6 0x0
   Product: valgrind
   Version: 3.10 SVN
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: memcheck
  Assignee: jsew...@acm.org
  Reporter: andreas.boer...@w84u.org

running my C++ program gives the following output:
vex amd64->IR: unhandled instruction bytes: 0x8F 0xEA 0x78 0x10 0xD2 0x6 0x6
0x0
vex amd64->IR:   REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR:   VEX=0 VEX.L=0 VEX.n=0x0 ESC=NONE
vex amd64->IR:   PFX.66=0 PFX.F2=0 PFX.F3=0
==18602== valgrind: Unrecognised instruction at address 0x527333.
==18602==at 0x527333:
COMPANY_NAMESPACE::DataPointerList2::PrepareRealloc(COMPANY_NAMESPACE::Operation&)
(DataPointerList2.cpp:280)
==18602==by 0x5289E4:
COMPANY_NAMESPACE::DataPointerList2::DirtyBufferInsert(unsigned int, unsigned
int const&) (DataPointerList2.cpp:668)
==18602==by 0x53D53E: (anonymous
namespace)::DataPointerTestCase_DirtyBuffers64_Test::TestBody()
(DataPointerListTest.cpp:687)
==18602==by 0x50ED12: void
testing::internal::HandleSehExceptionsInMethodIfSupported(testing::Test*, void (testing::Test::*)(), char const*) (in
/mnt/data/git/dataStruct/config/clang/bin/main)
==18602==by 0x503BC0: void
testing::internal::HandleExceptionsInMethodIfSupported(testing::Test*, void (testing::Test::*)(), char const*) (gtest.cc:2438)
==18602==by 0x4F51BA: testing::Test::Run() (gtest.cc:2474)
==18602==by 0x4F5C8D: testing::TestInfo::Run() (gtest.cc:2656)
==18602==by 0x4F63A6: testing::TestCase::Run() (gtest.cc:2774)
==18602==by 0x4FD76A: testing::internal::UnitTestImpl::RunAllTests()
(gtest.cc:4648)
==18602==by 0x50BB72: bool
testing::internal::HandleSehExceptionsInMethodIfSupported(testing::internal::UnitTestImpl*, bool
(testing::internal::UnitTestImpl::*)(), char const*) (in
/mnt/data/git/dataStruct/config/clang/bin/main)
==18602==by 0x505BF0: bool
testing::internal::HandleExceptionsInMethodIfSupported(testing::internal::UnitTestImpl*, bool
(testing::internal::UnitTestImpl::*)(), char const*) (gtest.cc:2438)
==18602==by 0x4FD424: testing::UnitTest::Run() (gtest.cc:4256)
==18602== Your program just tried to execute an instruction that Valgrind
==18602== did not recognise.  There are two possible reasons for this.
==18602== 1. Your program has a bug and erroneously jumped to a non-code
==18602==location.  If you are running Memcheck and you just saw a
==18602==warning about a bad jump, it's probably your program's fault.
==18602== 2. The instruction is legitimate but Valgrind doesn't handle it,
==18602==i.e. it's Valgrind's fault.  If you think this is the case or
==18602==you are not sure, please let us know and we'll try to fix it.
==18602== Either way, Valgrind will now raise a SIGILL signal which will
==18602== probably kill your program.
==18602== 
==18602== Process terminating with default action of signal 4 (SIGILL)
==18602==  Illegal opcode at address 0x527333
==18602==at 0x527333:
COMPANY_NAMESPACE::DataPointerList2::PrepareRealloc(COMPANY_NAMESPACE::Operation&)
(DataPointerList2.cpp:280)
==18602==by 0x5289E4:
COMPANY_NAMESPACE::DataPointerList2::DirtyBufferInsert(unsigned int, unsigned
int const&) (DataPointerList2.cpp:668)
==18602==by 0x53D53E: (anonymous
namespace)::DataPointerTestCase_DirtyBuffers64_Test::TestBody()
(DataPointerListTest.cpp:687)
==18602==by 0x50ED12: void
testing::internal::HandleSehExceptionsInMethodIfSupported(testing::Test*, void (testing::Test::*)(), char const*) (in
/mnt/data/git/dataStruct/config/clang/bin/main)
==18602==by 0x503BC0: void
testing::internal::HandleExceptionsInMethodIfSupported(testing::Test*, void (testing::Test::*)(), char const*) (gtest.cc:2438)
==18602==by 0x4F51BA: testing::Test::Run() (gtest.cc:2474)
==18602==by 0x4F5C8D: testing::TestInfo::Run() (gtest.cc:2656)
==18602==by 0x4F63A6: testing::TestCase::Run() (gtest.cc:2774)
==18602==by 0x4FD76A: testing::internal::UnitTestImpl::RunAllTests()
(gtest.cc:4648)
==18602==by 0x50BB72: bool
testing::internal::HandleSehExceptionsInMethodIfSupported(testing::internal::UnitTestImpl*, bool
(testing::internal::UnitTestImpl::*)(), char const*) (in
/mnt/data/git/dataStruct/config/clang/bin/main)
==18602==by 0x505BF0: bool
testing::internal::HandleExceptionsInMethodIfSupported(testing::internal::UnitTestImpl*, bool
(testing::internal::UnitTestImpl::*)(), char const*) (gtest.cc:2438)
==18602==by 0x4FD424: testing::UnitTest::Run() 

[kdevelop] [Bug 354143] Unclear output when building cpp project using cmake

[Piotr Mierzwinski via KDE Bugzilla]

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

--- Comment #13 from Piotr Mierzwinski  ---
kdevelop and kdevplatform cloned at 30/11/2015 (branch 5.0).

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

[kdevelop] [Bug 354143] Unclear output when building cpp project using cmake

[Piotr Mierzwinski via KDE Bugzilla]

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

--- Comment #14 from Piotr Mierzwinski  ---
Created attachment 95831
  --> https://bugs.kde.org/attachment.cgi?id=95831=edit
qtcmd_build (jobs: 2, 4, 8)

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

[kopete] [Bug 356130] Kopete crashes after closing any window

[Martin Walch via KDE Bugzilla]

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

Martin Walch  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 CC||walch.mar...@web.de
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Martin Walch  ---
Yes, this is pretty sure a duplicate of bug #355275. It is a known problem that
has yet to be fixed (there is no proper easy fix as Alex Merry stated in that
ticket).

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

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

[kopete] [Bug 355275] Kopete crashes after closing a window

[Martin Walch via KDE Bugzilla]

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

Martin Walch  changed:

   What|Removed |Added

 CC||donmar...@larkos.de

--- Comment #19 from Martin Walch  ---
*** Bug 356130 has been marked as a duplicate of this bug. ***

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

[systemsettings] [Bug 355671] Font Preview Panel not Rendering Correctly

[Joe via KDE Bugzilla]

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

--- Comment #3 from Joe  ---
I agree- 336089 looks like what I am experiencing.

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

[valgrind] [Bug 356138] vex amd64->IR unhandled instruction bytes 0x8F 0xEA 0x78 0x10 0xD2 0x6 0x6 0x0

[Andreas Boerner via KDE Bugzilla]

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

--- Comment #1 from Andreas Boerner  ---
PS: version selection box ends at 3.10 SVN.
It does not allow to select 3.11

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

[kleopatra] [Bug 356136] New: decrypt window opens off screen

[via KDE Bugzilla]

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

Bug ID: 356136
   Summary: decrypt window opens off screen
   Product: kleopatra
   Version: unspecified
  Platform: Other
OS: other
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: aheine...@intevation.de
  Reporter: jkort...@gmail.com
CC: kdepim-b...@kde.org, m...@kde.org

when i click clipboard to decrypt the new window opens up off screen, I cannot
move or use the window at all. 

Reproducible: Always

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

[ktimetracker] [Bug 269752] Auto track activities in KTimeTracker

[via KDE Bugzilla]

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

u...@pyngo.tom.ru changed:

   What|Removed |Added

 CC||u...@pyngo.tom.ru

--- Comment #25 from u...@pyngo.tom.ru ---
(In reply to Witold Sosnowski from comment #19)

> I believe this should not only be implemented for activities, but also
> tracking based on desktops could be removed from KTimeTracker.

I am using KTimeTracker with Unity. Please don't remove tracking based on
desktops!

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

[kmix] [Bug 356139] New: kmix stops responding to mouse clicks

[illumilore via KDE Bugzilla]

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

Bug ID: 356139
   Summary: kmix stops responding to mouse clicks
   Product: kmix
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: es...@kde.org
  Reporter: illumil...@gmail.com

In the system tray, when using kmix, it will stop responding to mouse clicks
and mouse wheel events when resuming from suspend.

Reproducible: Always

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

[kmail2] [Bug 354400] In Kmail 5.0.2 autocompletion only shows recent email addresses but not stored emails in Kaddressbook

[Clay Weber via KDE Bugzilla]

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

Clay Weber  changed:

   What|Removed |Added

 CC||c...@claydoh.com

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

[plasmashell] [Bug 356145] New: re-mapped "activate application launcher widget" shortcut not saved

[Moritz Bunkus via KDE Bugzilla]

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

Bug ID: 356145
   Summary: re-mapped "activate application launcher widget"
shortcut not saved
   Product: plasmashell
   Version: 5.4.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Application Menu (Kicker)
  Assignee: h...@kde.org
  Reporter: mor...@bunkus.org
CC: plasma-b...@kde.org

When I use systemsettings for changing the shortcut for Plasma's "activate
application launcher widget" from Alt+F1 to something else this works for the
current session only. At the end of the day I shut down KDE and the computer
normally via KDE's start menu. Next day when I log in again the shortcut has
been reset to Alt+F1.

All of my other changes to shortcuts are saved and restored correctly, e.g.
"manually invoke action on current clipboard" which I've re-mapped from
Ctrl+Alt+R to Meta+X.

Note that the Alt+F1 shortcut is listed as being a "custom" shortcut. The
"default" shortcut is supposed to be empty.

I've checked and made sure that all files in ~/.config belong to my current
user.


Reproducible: Always

Steps to Reproduce:
1. Change aforementioned shortcut
2. Log out of KDE (shut down the computer)
3. Log back in, open system settings and observe the shortcut's definition

Actual Results:  
Shortcut reverts to Alt+F1

Expected Results:  
Shortcut stays mapped to whatever I've chosen before

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

[kwin] [Bug 356144] New: KWin crashed when switching Tasks with +

[Leon via KDE Bugzilla]

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

Bug ID: 356144
   Summary: KWin crashed when switching Tasks with +
   Product: kwin
   Version: 5.4.2
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: l...@fairtragen.de

Application: kwin_x11 (5.4.2)

Qt Version: 5.4.2
Operating System: Linux 4.2.0-18-generic i686
Distribution: Ubuntu 15.10

-- Information about the crash:
- What I was doing when the application crashed:
I was using Konsole and wanted to switch to different program with the
+ and KWin crashed. 

This could be a duplicate of Bug 349174.

The crash can be reproduced sometimes.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0xb16757c0 (LWP 8635))]

Thread 4 (Thread 0xaefafb40 (LWP 8653)):
#0  0xb776e946 in __vdso_clock_gettime ()
#1  0xb7675740 in __GI___clock_gettime (clock_id=1, tp=0xaefaf064) at
../sysdeps/unix/clock_gettime.c:115
#2  0xb61cb378 in qt_clock_gettime (ts=0xaefaf064, clock=) at
tools/qelapsedtimer_unix.cpp:105
#3  do_gettime (frac=, sec=) at
tools/qelapsedtimer_unix.cpp:161
#4  qt_gettime () at tools/qelapsedtimer_unix.cpp:170
#5  0xb635b0a2 in QTimerInfoList::updateCurrentTime (this=0xae600af0) at
kernel/qtimerinfo_unix.cpp:84
#6  0xb635b5b4 in QTimerInfoList::timerWait (this=0xae600af0, tm=...) at
kernel/qtimerinfo_unix.cpp:379
#7  0xb635aba4 in QEventDispatcherUNIX::processEvents (this=0xae600468,
flags=...) at kernel/qeventdispatcher_unix.cpp:594
#8  0xb63002b3 in QEventLoop::processEvents (this=0xaefaf214, flags=...) at
kernel/qeventloop.cpp:128
#9  0xb6300702 in QEventLoop::exec (this=0xaefaf214, flags=...) at
kernel/qeventloop.cpp:204
#10 0xb612923d in QThread::exec (this=0x9bfa620) at thread/qthread.cpp:503
#11 0xb4f443bf in ?? () from /usr/lib/i386-linux-gnu/libQt5Qml.so.5
#12 0xb612e65b in QThreadPrivate::start (arg=0x9bfa620) at
thread/qthread_unix.cpp:337
#13 0xb725d1aa in start_thread (arg=0xaefafb40) at pthread_create.c:333
#14 0xb7667fde in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:122

Thread 3 (Thread 0xaddffb40 (LWP 8656)):
#0  0xb776ebe8 in __kernel_vsyscall ()
#1  0xb726225c in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:187
#2  0xb7674cf6 in __pthread_cond_wait (cond=0xb5dba8d0, mutex=0xb5dba8b8) at
forward.c:149
#3  0xb5c822fc in ?? () from /usr/lib/i386-linux-gnu/libQt5Script.so.5
#4  0xb5c8233c in ?? () from /usr/lib/i386-linux-gnu/libQt5Script.so.5
#5  0xb725d1aa in start_thread (arg=0xaddffb40) at pthread_create.c:333
#6  0xb7667fde in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:122

Thread 2 (Thread 0xafa3bb40 (LWP 8918)):
#0  0xb776e946 in __vdso_clock_gettime ()
#1  0xb7675740 in __GI___clock_gettime (clock_id=1, tp=0xafa3afb4) at
../sysdeps/unix/clock_gettime.c:115
#2  0xb61cb378 in qt_clock_gettime (ts=0xafa3afb4, clock=) at
tools/qelapsedtimer_unix.cpp:105
#3  do_gettime (frac=, sec=) at
tools/qelapsedtimer_unix.cpp:161
#4  qt_gettime () at tools/qelapsedtimer_unix.cpp:170
#5  0xb635b0a2 in QTimerInfoList::updateCurrentTime (this=0xaf100af0) at
kernel/qtimerinfo_unix.cpp:84
#6  0xb635a656 in QEventDispatcherUNIXPrivate::doSelect (this=0xaf100478,
flags=..., timeout=0x0) at kernel/qeventdispatcher_unix.cpp:171
#7  0xb635abd6 in QEventDispatcherUNIX::processEvents (this=0xaf100468,
flags=...) at kernel/qeventdispatcher_unix.cpp:607
#8  0xb63002b3 in QEventLoop::processEvents (this=0xafa3b214, flags=...) at
kernel/qeventloop.cpp:128
#9  0xb6300702 in QEventLoop::exec (this=0xafa3b214, flags=...) at
kernel/qeventloop.cpp:204
#10 0xb612923d in QThread::exec (this=0x9be4f18) at thread/qthread.cpp:503
#11 0xb4f443bf in ?? () from /usr/lib/i386-linux-gnu/libQt5Qml.so.5
#12 0xb612e65b in QThreadPrivate::start (arg=0x9be4f18) at
thread/qthread_unix.cpp:337
#13 0xb725d1aa in start_thread (arg=0xafa3bb40) at pthread_create.c:333
#14 0xb7667fde in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:122

Thread 1 (Thread 0xb16757c0 (LWP 8635)):
[KCrash Handler]
#7  0xb6641de4 in QScreen::handle (this=0x0) at kernel/qscreen.cpp:85
#8  0xb12ad681 in QXcbWindow::QXcbWindow (this=0xd3e7cd8, window=0xb5584a8) at
qxcbwindow.cpp:260
#9  0xb1298c65 in QXcbIntegration::createPlatformWindow (this=0x9a78ce8,
window=0xb5584a8) at qxcbintegration.cpp:194
#10 0xb661c885 in QWindowPrivate::create (this=0xb186ff0, recursive=false) at
kernel/qwindow.cpp:395
#11 0xb661caad in QWindow::create (this=0xb5584a8) at kernel/qwindow.cpp:546
#12 0xb661ccd9 in QWindow::winId (this=0xb5584a8) at kernel/qwindow.cpp:565
#13 0xa83e5723 in PlasmaQuick::DialogPrivate::updateInputShape (this=0xb39e118)
at ../../../src/plasmaquick/dialog.cpp:544
#14 

[kwin] [Bug 356144] KWin crashed when switching Tasks with +

[Thomas Lübking via KDE Bugzilla]

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

Thomas Lübking  changed:

   What|Removed |Added

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

--- Comment #1 from Thomas Lübking  ---
Yes, is. And is a bug in Qt. Hopefully to be fixed in Qt 5.6

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

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

[plasmashell] [Bug 355582] plasma crashes after disabling Laptop's screen

[Thekla Damaschke via KDE Bugzilla]

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

--- Comment #2 from Thekla Damaschke  ---
Created attachment 95834
  --> https://bugs.kde.org/attachment.cgi?id=95834=edit
New crash information added by DrKonqi

plasmashell (5.4.3) using Qt 5.5.1

- What I was doing when the application crashed:
I have a stationary with two screens. I was disabling the secondary display
from the Display Configuration app.
After Plasma recovering on the the primary screeen  the app doesnt show any
Monitor to adjust.

-- Backtrace (Reduced):
#5  0x7f54a90a255c in QXcbScreen::mapFromNative(QPoint const&) const ()
from /lib64/libQt5XcbQpa.so.5
#6  0x7f54a90aa9aa in
QXcbWindow::handleEnterNotifyEvent(xcb_enter_notify_event_t const*) () from
/lib64/libQt5XcbQpa.so.5
#7  0x7f54a9093afd in QXcbConnection::handleXcbEvent(xcb_generic_event_t*)
() from /lib64/libQt5XcbQpa.so.5
#8  0x7f54a9094433 in QXcbConnection::processXcbEvents() () from
/lib64/libQt5XcbQpa.so.5
#9  0x7f54bfc211b1 in QObject::event(QEvent*) () from
/lib64/libQt5Core.so.5

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

[dragonplayer] [Bug 356081] Dragon player crashes when trying to play a mp4 file from a smb share

[Arnold Greving via KDE Bugzilla]

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

--- Comment #2 from Arnold Greving  ---
The crash is reproduce-able.

I have the following phonon (AMD64) packages installed:
- phonon -> 4:4.8.3-0ubuntu2
- phonon-backend-gstreamer -> 4:4.8.2-0ubuntu1
- phonon-backend-gstreamer-common -> 4:4.8.2-0ubuntu1
- phonon4qt5-backend-gstreamer -> 4:4.8.2-0ubuntu1

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

[valgrind] [Bug 356112] New: mips: replace addi with addiu

[Vicente Olivert Riera via KDE Bugzilla]

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

Bug ID: 356112
   Summary: mips: replace addi with addiu
   Product: valgrind
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: vincent.ri...@imgtec.com

Created attachment 95815
  --> https://bugs.kde.org/attachment.cgi?id=95815=edit
mips: replace addi with addiu

ADDI instruction has been removed in R6 so let's use ADDIU instead.

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

[kwin] [Bug 356107] Taskbar disappear when switched to fullscreen in a VNC session

[Thomas Lübking via KDE Bugzilla]

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

Thomas Lübking  changed:

   What|Removed |Added

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

--- Comment #1 from Thomas Lübking  ---
every qt5 client is prone to crash on randr events, apparently hit at least
plasmashell and kwin.
hopefully fixed in qt 5.6

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

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

[kwin] [Bug 341497] Segfault in Qt since the (at least) the xcb screen backend cannot deal with "no screen" conditions

[Thomas Lübking via KDE Bugzilla]

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

Thomas Lübking  changed:

   What|Removed |Added

 CC||jbar...@gmail.com

--- Comment #47 from Thomas Lübking  ---
*** Bug 356107 has been marked as a duplicate of this bug. ***

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

[amarok] [Bug 356097] Connection to external MySQL database not recovered on resuming from sleep

[Myriam Schweingruber via KDE Bugzilla]

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

Myriam Schweingruber  changed:

   What|Removed |Added

 CC||ma...@laitl.cz,
   ||ralf-eng...@gmx.de
  Component|Collection Browser  |Collections/Local

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

[kwin] [Bug 344326] Black or corrupted screen on resume from suspend

[Ruslan Kabatsayev via KDE Bugzilla]

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

--- Comment #81 from Ruslan Kabatsayev  ---
(In reply to Rafael from comment #79)
> Another atypical issue I saw some time in the unlock screen is "crossed
> text", that's to say, the text  (and only the text) appeared  like if you
> put your eyes "crossed". I have some screenshot of this and will send here.

It might be bug 307003.

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

[ksnapshot] [Bug 356092] 12.04 LTS CD Save and other functions don; t work (e.g. Save As, Help: file a bug)

[Boudhayan Gupta via KDE Bugzilla]

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

Boudhayan Gupta  changed:

   What|Removed |Added

  Component|kscreengenie|general
   Assignee|m...@baloneygeek.com  |ase...@kde.org

--- Comment #1 from Boudhayan Gupta  ---
Reassigning as this is a problem with KSnapshot, not KScreenGenie/Spectacle.

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

[kwin] [Bug 344326] Black or corrupted screen on resume from suspend

[Rafael via KDE Bugzilla]

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

--- Comment #82 from Rafael  ---
Thank you Ruslan Kabatsayev , but it's not the same issue.  Mine only had
happened if login after wake up.  The 307003 bug seems to be subpixel rendering
related.
; )

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

[khotkeys] [Bug 340240] [wishlist] [ksnapshot] - a global hotkeys (winkey+prntscreen or a-like) in case system is broken to automatically take snapshot and save it in /home/ folder with default settin

[Thomas Lübking via KDE Bugzilla]

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

Thomas Lübking  changed:

   What|Removed |Added

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

--- Comment #5 from Thomas Lübking  ---
Then it shall be "fixed" ;-)

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

[kwin] [Bug 344326] Black or corrupted screen on resume from suspend

[anselmolsm]

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

Anselmo L. S. Melo (anselmolsm)  changed:

   What|Removed |Added

 CC|anselmo...@gmail.com|

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

[phonon-backend-gstreamer] [Bug 355823] Amarok crashes when I start it

[huangshun via KDE Bugzilla]

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

--- Comment #2 from huangshun <906639...@qq.com> ---
(In reply to Myriam Schweingruber from comment #1)
> There obviously is a problem with your Phonon backend, please check your
> installation and make sure you have no mixup of gstreamer 0.1 and gstreamer
> 1.x libraries, or a mixup between Qt4 and Qt5 parts.
> 
> FWIW: you need to install debugging symbols for Amarok, Phonon,
> phonon-backend-gstreamer and provide a new backtrace, yours is missing
> debugging symbols. Please see also
> https://techbase.kde.org/Development/Tutorials/Debugging/
> How_to_create_useful_crash_reports

Thanks for the tip. I will recheck and regenerate a backtrace.

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

[valgrind] [Bug 356044] Dwarf line info reader misinterprets is_stmt register

[Ivo Raisr via KDE Bugzilla]

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

--- Comment #4 from Ivo Raisr  ---
So I spotted the problem by a chance, because another redirected function got
used on Solaris/x86+amd64 (using gcc 4.8.2). However this is a generic problem
with location info on Linux as well.

Consider the following decoded "Line Number Statements" as displayed by
"readelf --debug-dump=rawline":
  (previous instructions were related to line 868)
  ...
  Set is_stmt to 1
  Special opcode 174: advance Address by 12 to 0x1c72 and Line by 1 to 869
  Advance PC by constant 17 to 0x1c83
  Special opcode 5: advance Address by 0 to 0x1c83 and Line by 0 to 869
  Extended opcode 4: set Discriminator to 1
  Set is_stmt to 0
  Special opcode 131: advance Address by 9 to 0x1c8c and Line by 0 to 869
  Extended opcode 4: set Discriminator to 2
  Special opcode 75: advance Address by 5 to 0x1c91 and Line by 0 to 869
  Extended opcode 4: set Discriminator to 1
  Special opcode 75: advance Address by 5 to 0x1c96 and Line by 0 to 869
  Extended opcode 4: set Discriminator to 2
  Copy
  Extended opcode 4: set Discriminator to 1
  Special opcode 131: advance Address by 9 to 0x1c9f and Line by 0 to 869
  Extended opcode 4: set Discriminator to 2
  Advance PC by constant 17 to 0x1cb0
  Special opcode 89: advance Address by 6 to 0x1cb6 and Line by 0 to 869
  Extended opcode 4: set Discriminator to 1
  Special opcode 159: advance Address by 11 to 0x1cc1 and Line by 0 to 869
  Extended opcode 4: set Discriminator to 2
  Special opcode 131: advance Address by 9 to 0x1cca and Line by 0 to 869
  Special opcode 131: advance Address by 9 to 0x1cd3 and Line by 0 to 869
  Extended opcode 4: set Discriminator to 3
  Special opcode 117: advance Address by 8 to 0x1cdb and Line by 0 to 869
  Extended opcode 4: set Discriminator to 1
  Advance PC by 88 to 0x1d33
  Special opcode 5: advance Address by 0 to 0x1d33 and Line by 0 to 869
  Extended opcode 4: set Discriminator to 2
  Advance PC by constant 17 to 0x1d44
  Special opcode 47: advance Address by 3 to 0x1d47 and Line by 0 to 869
  Advance PC by 12 to 0x1d53
  Extended opcode 1: End of Sequence

Line 869 corresponds to function _vgr10110ZU_VgSoSynsomalloc_memalign() - which
happens to be the last one in this compilation unit. Its size is 0xe1 (225)
bytes as confirmed by nm, readelf and also disassembly.

However current Valgrind functionality adds DiLoc entries only for addresses
where "is_stmt = 1", that is address range
0x1c72-0x1c83 (17 bytes). This is clearly wrong; address ranges for "is_stmt =
0" should be covered as well.

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

[konsole] [Bug 355760] Konsole process doesn't terminate when window is closed by the close button in the Titlebar.

[Rex Dieter via KDE Bugzilla]

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

Rex Dieter  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||rdie...@math.unl.edu
 Resolution|--- |DUPLICATE

--- Comment #4 from Rex Dieter  ---
Are you using nvidia driver?  If so, then it's likely a dup of bug #343803

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

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

[khotkeys] [Bug 340240] [wishlist] [ksnapshot] - a global hotkeys (winkey+prntscreen or a-like) in case system is broken to automatically take snapshot and save it in /home/ folder with default settin

[Thomas Lübking via KDE Bugzilla]

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

--- Comment #3 from Thomas Lübking  ---
Is spectacle already shipped w/ 5.5?

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