[plasmashell] [Bug 357105] Applications can't detect system tray

[agilob via KDE Bugzilla]

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

agilob  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |INVALID
 Status|NEEDSINFO   |RESOLVED

--- Comment #5 from agilob  ---
I found the problem. After the upgrade some background services were disabled
(system settings->startup and shutdown -> background services). Bluetooth,
device manager, status notifier manager were disabled. Enabling SNM fixed my
issue...

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

[ksmserver] [Bug 357140] New: Can't terminate KDE session if it's been open for a long time

[Fibonacci via KDE Bugzilla]

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

Bug ID: 357140
   Summary: Can't terminate KDE session if it's been open for a
long time
   Product: ksmserver
   Version: 5.4.2
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: l.lu...@kde.org
  Reporter: fibonacci.pro...@gmail.com

After a KDE session has been running for a long time (it's not always the same
time, but the longer it is, the higher the chance this bug will appear), trying
to logout, reboot or shutdown from the menu results in absolutely nothing
happening – not even the usual dialog asking me to confirm logging out.

Running qdbus org.kde.ksmserver /KSMServer logout 0 0 0 only prints the
following:
Cannot find '.logout' in object /KSMServer at org.kde.ksmserver

The only way to log out at this point is to either shut down or reboot the
computer from the command line (i.e. reboot/poweroff commands)

Strangely, both logging out from the menu or running the aforementioned command
work fine most of the time right after I've logged in.

Reproducible: Sometimes

Steps to Reproduce:
1. Open a KDE session
2. Leave it running for a long time
3. Try to logout

Actual Results:  
Nothing

Expected Results:  
The KDE session terminates

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

[ark] [Bug 357134] Ark is unable to open RAR archives after update to 15.12

[Elvis Angelaccio via KDE Bugzilla]

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

--- Comment #1 from Elvis Angelaccio  ---
(In reply to Ongun Kanat from comment #0)
> Ark 15.12 cannot open specific RAR archives that 15.08 can open. I have two
> files that I'm sure they are not broken (I can open both of them in Ark
> 15.08 and WinRAR).
> 
> In the first file Ark 15.12 shows the file names in the brand new comment
> section but contents of the archive are not displayed. I can extract its
> contents via Dolphin's right click menu.
> You can access the file from here: https://goo.gl/ZQCEux
> The screenshot for it: https://goo.gl/yZDCKH
> It works on Ark 15.08: https://goo.gl/iW3Djq
> 
This is a known issue that will be fixed in Ark 15.12.1. As a temporary
workaround, please remove the spaces from the archive's filename. Then Ark
15.12 will be able to open the archive again.

> In the other one Ark 15.12 completely denies opening the file. In the
> version 15.08, Ark asks for a file type for this file if I select RAR It
> opens and shows me the contents correctly (The ask option has removed but
> this is another bug report). I can also extract it using Ark 15.08.
> At the moment I don't have a fast connection but I will upload the file soon
> (~200MiB)
> The screenshot of the error: https://goo.gl/xnli7V
> The option window in Ark 15.08: https://goo.gl/s7mjeI
> And It also works on Ark 15.08: https://goo.gl/537Fi8
> 
> Reproducible: Always
> 
> Steps to Reproduce:
> Open a specific RAR archive.
> 
> Actual Results:  
> Files are not shown or Ark 15.12 denies opening the file
> 
> Expected Results:  
> Ark opens and contents are correctly shown

Please update your archlinux Ark package to version 15.12.0-2, that should make
Ark able to open RAR archives again. If this update does not fix it, please
tell me.

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

[plasmashell] [Bug 357141] New: kdeinit5 crashes on waking up in fedora22

[via KDE Bugzilla]

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

Bug ID: 357141
   Summary: kdeinit5 crashes on waking up in fedora22
   Product: plasmashell
   Version: master
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: nikita.rogat...@infotecs.ru
CC: bhus...@gmail.com, plasma-b...@kde.org

call trace i've got:

Application: kdeinit5 (kdeinit5), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f8e5aa0b840 (LWP 15591))]

Thread 7 (Thread 0x7f8e3bbab700 (LWP 15594)):
#0  0x7f8e577782fd in poll () at /lib64/libc.so.6
#1  0x7f8e56957182 in _xcb_conn_wait () at /lib64/libxcb.so.1
#2  0x7f8e56958c77 in xcb_wait_for_event () at /lib64/libxcb.so.1
#3  0x7f8e3dd3bda9 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5
#4  0x7f8e583853ce in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#5  0x7f8e56dbf555 in start_thread () at /lib64/libpthread.so.0
#6  0x7f8e57783b9d in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7f8e30271700 (LWP 15596)):
#0  0x7f8e577782fd in poll () at /lib64/libc.so.6
#1  0x7f8e55bf3dbc in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7f8e55bf4142 in g_main_loop_run () at /lib64/libglib-2.0.so.0
#3  0x7f8e30b8f696 in gdbus_shared_thread_func () at /lib64/libgio-2.0.so.0
#4  0x7f8e55c1b0a5 in g_thread_proxy () at /lib64/libglib-2.0.so.0
#5  0x7f8e56dbf555 in start_thread () at /lib64/libpthread.so.0
#6  0x7f8e57783b9d in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7f8e23093700 (LWP 15598)):
#0  0x7f8e55c38ec9 in g_mutex_lock () at /lib64/libglib-2.0.so.0
#1  0x7f8e55bf2d60 in g_main_context_acquire () at /lib64/libglib-2.0.so.0
#2  0x7f8e55bf3c75 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#3  0x7f8e55bf3ecc in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#4  0x7f8e585bcf0b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#5  0x7f8e58563f0a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#6  0x7f8e58380424 in QThread::exec() () at /lib64/libQt5Core.so.5
#7  0x7f8e583853ce in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7f8e56dbf555 in start_thread () at /lib64/libpthread.so.0
#9  0x7f8e57783b9d in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f8e21e82700 (LWP 15602)):
#0  0x7f8e55c38ec9 in g_mutex_lock () at /lib64/libglib-2.0.so.0
#1  0x7f8e55bf380c in g_main_context_check () at /lib64/libglib-2.0.so.0
#2  0x7f8e55bf3d60 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#3  0x7f8e55bf3ecc in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#4  0x7f8e585bcf0b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#5  0x7f8e58563f0a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#6  0x7f8e58380424 in QThread::exec() () at /lib64/libQt5Core.so.5
#7  0x7f8e3397b397 in KCupsConnection::run() () at /lib64/libkcupslib.so
#8  0x7f8e583853ce in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#9  0x7f8e56dbf555 in start_thread () at /lib64/libpthread.so.0
#10 0x7f8e57783b9d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f8e21681700 (LWP 15603)):
#0  0x7f8e5779163f in __libc_enable_asynccancel () at /lib64/libc.so.6
#1  0x7f8e577782f2 in poll () at /lib64/libc.so.6
#2  0x7f8e55bf3dbc in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#3  0x7f8e55bf3ecc in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#4  0x7f8e585bcf0b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#5  0x7f8e58563f0a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#6  0x7f8e58380424 in QThread::exec() () at /lib64/libQt5Core.so.5
#7  0x7f8e583853ce in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7f8e56dbf555 in start_thread () at /lib64/libpthread.so.0
#9  0x7f8e57783b9d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f8e1aa84700 (LWP 15762)):
#0  0x7f8e57773fad in read () at /lib64/libc.so.6
#1  0x7f8e55c37b00 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0
#2  0x7f8e55bf38b4 in g_main_context_check () at /lib64/libglib-2.0.so.0
#3  0x7f8e55bf3d60 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#4  0x7f8e55bf3ecc in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#5  0x7f8e585bcf0b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#6  0x7f8e58563f0a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#7  0x7f8e58380424 in QThread::exec() () at /lib64/libQt5Core.so.5
#8  0x7f8e583853ce in 

[kontact] [Bug 351686] After using Knotes, Kontakt crashes after reopening following to riduction to icon

[via KDE Bugzilla]

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

--- Comment #2 from staka...@freenet.de ---
Created attachment 96294
  --> https://bugs.kde.org/attachment.cgi?id=96294=edit
New crash information added by DrKonqi

kontact (4.14.9) on KDE Platform 4.14.9 using Qt 4.8.6

- What I was doing when the application crashed:
signing a mail with a "cryptokey"

- Unusual behavior I noticed:
closing kontakt after sending it crashed. 
I attached this because I think it could be interesting if connected to the use
of crytohardware with email sending. 
Sorry if this should be redundant. 

Cryptografic hardware was Cryptokey 1.2 (look at www.nitrokey.com for further
details).

-- Backtrace (Reduced):
#11 0x7f0c29419d84 in operator-> (this=) at
/usr/src/debug/kdepim-4.14.9/mailcommon/kernel/mailkernel.cpp:58
#12 MailCommon::Kernel::self () at
/usr/src/debug/kdepim-4.14.9/mailcommon/kernel/mailkernel.cpp:75
#13 0x7f0c29461ec0 in MailCommon::FolderCollection::writeConfig
(this=this@entry=0x1950050) at
/usr/src/debug/kdepim-4.14.9/mailcommon/folder/foldercollection.cpp:218
#14 0x7f0c294626c2 in MailCommon::FolderCollection::~FolderCollection
(this=0x1950050, __in_chrg=) at
/usr/src/debug/kdepim-4.14.9/mailcommon/folder/foldercollection.cpp:84
#15 0x7f0c29462739 in MailCommon::FolderCollection::~FolderCollection
(this=0x1950050, __in_chrg=) at
/usr/src/debug/kdepim-4.14.9/mailcommon/folder/foldercollection.cpp:86

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

[kontact] [Bug 351686] After using Knotes, Kontakt crashes after reopening following to riduction to icon

[via KDE Bugzilla]

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

staka...@freenet.de changed:

   What|Removed |Added

 CC||staka...@freenet.de

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

[plasmashell] [Bug 354244] Logout/Shutdown etc. dialog buttons are placed in unexpected order

[Gregor Mi via KDE Bugzilla]

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

Gregor Mi  changed:

   What|Removed |Added

 CC||thomas.luebk...@gmail.com

--- Comment #3 from Gregor Mi  ---
I added Thomas from VDG. I think it is good to clear this topic early before
the current order really burns in; as more and more people are going to use
Plasma 5 instead of 4.

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

[kdenlive] [Bug 357054] Undoing quick razor clip cut actions freezes Kdenlive

[via KDE Bugzilla]

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

qubo...@gmail.com changed:

   What|Removed |Added

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

--- Comment #4 from qubo...@gmail.com ---
Fortunately, I can't reproduce any of the issues any more. Thanks!

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

[frameworks-knotifications] [Bug 357141] kdeinit5 crashes on waking up in fedora22

[Kai Uwe Broulik via KDE Bugzilla]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

Product|plasmashell |frameworks-knotifications
  Component|general |general
 CC||k...@privat.broulik.de,
   ||kdelibs-b...@kde.org
   Target Milestone|1.0 |---
Version|master  |unspecified
   Assignee|k...@davidedmundson.co.uk|mklape...@kde.org

--- Comment #1 from Kai Uwe Broulik  ---
Someone was spawning a notification as a passive popup and when it closed it
crashed. Can you see a notification (a Plasma style notification, no DrKonqi)?

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

[blogilo] [Bug 350267] Blogilo crashed when I opened it the first time.

[Grishin via KDE Bugzilla]

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

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

blogilo (1.1) on KDE Platform 4.14.2 using Qt 4.8.6

- What I was doing when the application crashed:

В принципе, то же самое, что и в предыдущих ошибках. 
Первый запуск программы привёл к её немедленному завершению без объяснения
причин.

-- Backtrace (Reduced):
#6  BilboBlog::url (this=0x0) at ../../../blogilo/src/bilboblog.cpp:127
#7  0x00453ef4 in BilboBrowser::setHtml (this=0x2972e20, title=...,
content=...) at ../../../blogilo/src/composer/bilbobrowser.cpp:112
#8  0x0042fbd0 in PostEntry::slotSyncEditors (this=0x1f90560, index=2)
at ../../../blogilo/src/postentry.cpp:215
#9  0x0045cdb3 in PostEntry::qt_static_metacall (_o=,
_id=, _a=, _c=) at
moc_postentry.cpp:96
[...]
#11 0x7f4cb665d01e in QTabWidget::currentChanged
(this=this@entry=0x1fe86c0, _t1=_t1@entry=2) at
.moc/release-shared/moc_qtabwidget.cpp:213

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

[blogilo] [Bug 350267] Blogilo crashed when I opened it the first time.

[Grishin via KDE Bugzilla]

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

Grishin  changed:

   What|Removed |Added

 CC||w201...@ya.ru

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

[plasmashell] [Bug 354244] Logout/Shutdown etc. dialog buttons are placed in unexpected order

[Thomas Lübking via KDE Bugzilla]

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

Thomas Lübking  changed:

   What|Removed |Added

 CC||colo...@autistici.org

--- Comment #4 from Thomas Lübking  ---
wrong Thomas ;-P

But I can provide the information that in general the button order is
controlled by QStyle::SH_DialogButtonLayout, providing
QDialogButtonBox::ButtonLayout being one of
QDialogButtonBox::WinLayout
QDialogButtonBox::MacLayout
QDialogButtonBox::KdeLayout
QDialogButtonBox::GnomeLayout

I'd say that *any* dialog should follow that (ie. in doubt copy the logic from
QDialogButtonBox) - you implicitly click wrong buttons (for a while) after
changing the order.

Cancel/Ok is a typical OSX/Gnome layout while KDE largely copied the Windows
layout patterns (Ok/Cancel)

---

On a personal note, the windows layout is rubbish.

The buttons are on the right side of buttonboxes (right aligned) and the OSX
theory is that of a ltr culture walking top-left -> bottom-right (that's why
the close button is on the top left and cancel buttons are on the left - you
"go back to where thou camest" while the ok/apply/accept buttons ideally appear
on the bottom right (signing the changes)

tl;dr - the buttons should seriously be consistent (changing that pattern makes
you click the wrong button easily, I notice that when changing the stylehint)
but the default KDE layout is the wrong one ;-P

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

[Spectacle] [Bug 357142] New: "Save & Exit" is a UX pessimization

[Szczepan Hołyszewski via KDE Bugzilla]

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

Bug ID: 357142
   Summary: "Save & Exit" is a UX pessimization
   Product: Spectacle
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: m...@baloneygeek.com
  Reporter: rula...@wp.pl

When you neither ask the user where to save the screenshot nor tell them where
you saved it, then the correct therm is "lost", not "saved".

Please don't be goddamn Firefox. Please *do ask* the user where to save the
file, or *at the very least* post a system notification telling the user where
the file was saved. Not even knowing the *filename*, searching for that saved
screenshot (without success!) took me so long that the time spent posting this
bug report is negligible in comparison.

Reproducible: Always

Steps to Reproduce:
1. Make a screenshot with Spectacle
2. Use "Save & Exit"


Actual Results:  
Spectacle *loses* the screenshot someplace only it knows about, and exits
immediately.

Expected Results:  
Spectacle should *save* the screenshot in either specifiable or immediately
made-known location.

I expected "Save & Exit" to differ from "Save As..." *only* by sparing me the
extra click to exit Spectacle, *not* by substituting the semantics of "lose"
for that of "save".

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

[khotkeys] [Bug 352073] "http://ksnapshot/" is opened in web browser if KSnapshot is not installed

[Boudhayan Gupta via KDE Bugzilla]

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

--- Comment #3 from Boudhayan Gupta  ---
If you uninstall KSnapshot, your ~/.config/khotkeysrc still includes references
to ksnapshot, which makes it open as an URL in your browser. Removing it should
fix things.

Spectacle does ship its own khotkeysrc file which is installed into
${CMAKE_DATA_DIR}/khotkeys. It ships as part of the Spectacle package, so
without installing it you won't get the new definition files.

I can't close this bug, but I think an appropriate resolution would be INVALID.

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

[Spectacle] [Bug 357142] "Save & Exit" is a UX pessimization

[Boudhayan Gupta via KDE Bugzilla]

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

Boudhayan Gupta  changed:

   What|Removed |Added

 Resolution|--- |LATER
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Boudhayan Gupta  ---
If you've seen the drop down menu that appears when you click the arrow beside
Save & Exit, you'll see an option "Configure Save Options" that allows you to
set the location and filename pattern. This  is documented in the handbook.

That said, no one actually reads the handbook, so I'll resolve this by popping
up a notification when the Save & Exit button is used, and changing the tooltip
to point users to the Configure Save Options dialog.

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

[Spectacle] [Bug 357142] "Save & Exit" is a UX pessimization

[Boudhayan Gupta via KDE Bugzilla]

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

Boudhayan Gupta  changed:

   What|Removed |Added

 Status|RESOLVED|VERIFIED
 Resolution|LATER   |REMIND

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

[kontact] [Bug 357139] New: Kontact crashed when choosing "configure completion" in kmail composer

[Christian Trippe via KDE Bugzilla]

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

Bug ID: 357139
   Summary: Kontact crashed when choosing "configure completion"
in kmail composer
   Product: kontact
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: christiande...@web.de

Application: kontact (5.1)

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

-- Information about the crash:
1.)Open kontact with kmail included.
2.) Open the kmail composer
3.) RIght click in the address field
4.) Choose "configure completion" (guessed from German "Vervollständigung
einrichten ..."
5.) kontact crashes (sometimes but not always)

The crash can be reproduced sometimes.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fe54ccb9800 (LWP 7990))]

Thread 25 (Thread 0x7fe52edb3700 (LWP 7991)):
#0  0x7fe549900c1d in poll () from /lib64/libc.so.6
#1  0x7fe5430a3422 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7fe5430a500f in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7fe530f02c29 in QXcbEventReader::run (this=0xfe8420) at
qxcbconnection.cpp:1214
#4  0x7fe54a20e55f in QThreadPrivate::start (arg=0xfe8420) at
thread/qthread_unix.cpp:331
#5  0x7fe542c800a4 in start_thread () from /lib64/libpthread.so.0
#6  0x7fe54990904d in clone () from /lib64/libc.so.6

Thread 24 (Thread 0x7fe5275ef700 (LWP 7992)):
#0  0x7fe542c8405f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fe5474644a3 in ?? () from /usr/lib64/libQt5WebKit.so.5
#2  0x7fe5474644c9 in ?? () from /usr/lib64/libQt5WebKit.so.5
#3  0x7fe542c800a4 in start_thread () from /lib64/libpthread.so.0
#4  0x7fe54990904d in clone () from /lib64/libc.so.6

Thread 23 (Thread 0x7fe4e2d0b700 (LWP 7993)):
#0  postEventSourcePrepare (s=0x7fe4dc0012d0, timeout=0x7fe4e2d0ac14) at
kernel/qeventdispatcher_glib.cpp:248
#1  0x7fe5424624ad in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#2  0x7fe542462d80 in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x7fe542462f7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#4  0x7fe54a43fa5b in QEventDispatcherGlib::processEvents
(this=0x7fe4dc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7fe54a3e6a63 in QEventLoop::exec (this=this@entry=0x7fe4e2d0add0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7fe54a20984a in QThread::exec (this=) at
thread/qthread.cpp:503
#7  0x7fe54a20e55f in QThreadPrivate::start (arg=0x11796b0) at
thread/qthread_unix.cpp:331
#8  0x7fe542c800a4 in start_thread () from /lib64/libpthread.so.0
#9  0x7fe54990904d in clone () from /lib64/libc.so.6

Thread 22 (Thread 0x7fe4dbfff700 (LWP 7994)):
#0  0x7fe542c8405f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fe5471704cd in ?? () from /usr/lib64/libQt5WebKit.so.5
#2  0x7fe547492da1 in ?? () from /usr/lib64/libQt5WebKit.so.5
#3  0x7fe542c800a4 in start_thread () from /lib64/libpthread.so.0
#4  0x7fe54990904d in clone () from /lib64/libc.so.6

Thread 21 (Thread 0x7fe4db7fe700 (LWP 7995)):
#0  0x7fe542c8405f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fe5471714a3 in ?? () from /usr/lib64/libQt5WebKit.so.5
#2  0x7fe547492da1 in ?? () from /usr/lib64/libQt5WebKit.so.5
#3  0x7fe542c800a4 in start_thread () from /lib64/libpthread.so.0
#4  0x7fe54990904d in clone () from /lib64/libc.so.6

Thread 20 (Thread 0x7fe4ca4f4700 (LWP 7996)):
#0  0x7fe549900c1d in poll () from /lib64/libc.so.6
#1  0x7fe542462e64 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7fe542462f7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7fe54a43fa5b in QEventDispatcherGlib::processEvents
(this=0x7fe4c40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7fe54a3e6a63 in QEventLoop::exec (this=this@entry=0x7fe4ca4f3dd0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7fe54a20984a in QThread::exec (this=) at
thread/qthread.cpp:503
#6  0x7fe54a20e55f in QThreadPrivate::start (arg=0x15cc760) at
thread/qthread_unix.cpp:331
#7  0x7fe542c800a4 in start_thread () from /lib64/libpthread.so.0
#8  0x7fe54990904d in clone () from /lib64/libc.so.6

Thread 19 (Thread 0x7fe4c9cf3700 (LWP 7997)):
#0  0x7fe5424a4d14 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0
#1  0x7fe5424628e9 in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#2  0x7fe542462df8 in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x7fe542462f7c in g_main_context_iteration 

[plasmashell] [Bug 357143] New: Logout/Shutdown/Reboot panel can lose focus and then ESC key does not work

[Gregor Mi via KDE Bugzilla]

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

Bug ID: 357143
   Summary: Logout/Shutdown/Reboot panel can lose focus and then
ESC key does not work
   Product: plasmashell
   Version: 5.5.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: codestr...@posteo.org
CC: bhus...@gmail.com, plasma-b...@kde.org

Reproduce:
1. Hit Ctrl+Alt+Esc to show logout panel
2. Accidentally click with the mouse somewhere else
3. Hit ESC to close the panel

Actual: The ESC key works on the window which is currently focued

Expected: The ESC key closes the Logout panel

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

[gcompris] [Bug 357144] New: In the chess activity against Tux, the "redo" button does not work well when is pressed multiple times very quickly

[via KDE Bugzilla]

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

Bug ID: 357144
   Summary: In the chess activity against Tux, the "redo" button
does not work well when is pressed multiple times very
quickly
   Product: gcompris
   Version: unspecified
  Platform: Ubuntu Packages
   URL: https://youtu.be/GCgbet-gfSA
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: bruno.coud...@gcompris.net
  Reporter: stefan.to...@cti.pub.ro

When i play against Tux, after i redo some moves very quickly, the game rules
change:
- a message is shown: "invalid, your king may be in check" but it is not true
- white has done 2 moves instead of one
- i do not play with white -> i am switched to blacks
- the pieces no longer moves as they should (in the link on Youtube: 00:54 -
[1];  1:16 - [2])
   [1]  https://youtu.be/GCgbet-gfSA?t=54s
   [2]  https://youtu.be/GCgbet-gfSA?t=1m16s
- after black is checked (1:28 - [3]), i move the king, white does not make any
move and i can move again
   [3]  https://youtu.be/GCgbet-gfSA?t=1m28s

Reproducible: Always

Steps to Reproduce:
1. Start Chess against Tux
2. Make 4-5 moves
3. Undo all moves
4. Redo very quickly all the moves

Actual Results:  
The game does not work properly anymore.

Expected Results:  
Redo the moves without any problems to their original position.

I got this bug on my Android and managed to replicate it on Ubuntu 15.10.
I attached a link to a Youtube video where i replicate this bug.

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

[plasmashell] [Bug 357146] New: Sporadic lost window decoration --> coredump

[jan neumann via KDE Bugzilla]

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

Bug ID: 357146
   Summary: Sporadic lost window decoration --> coredump
   Product: plasmashell
   Version: 5.5.1
  Platform: Other
   URL: https://forum.manjaro.org/index.php?topic=29248.0
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: Look & Feel package
  Assignee: plasma-b...@kde.org
  Reporter: neum...@gmail.com
CC: plasma-b...@kde.org

Some users complain about aforesaid issue. check forum site for more
information (logs etc.). thank you

Reproducible: Didn't try


Actual Results:  
coredump

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

[plasmashell] [Bug 357147] New: Two different system settings windows could be confusing

[Gregor Mi via KDE Bugzilla]

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

Bug ID: 357147
   Summary: Two different system settings windows could be
confusing
   Product: plasmashell
   Version: 5.5.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: codestr...@posteo.org
CC: bhus...@gmail.com, plasma-b...@kde.org

Reproduce: 
1. Open Kicker -> Settings -> System Settings
2. Open Kicker -> Settings -> Configure Desktop
=> See screenshot http://susepaste.org/images/77256862.png (and attachment)

Acutal:
There are two windows both titled with "System settings" but they contain
different icons and groupings.

Expected:
There is only one consistent settings window.

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

[plasmashell] [Bug 357147] Two different system settings windows could be confusing

[Gregor Mi via KDE Bugzilla]

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

--- Comment #1 from Gregor Mi  ---
Created attachment 96295
  --> https://bugs.kde.org/attachment.cgi?id=96295=edit
two system settings window

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

[kdenlive] [Bug 357151] New: Crashes when trying to render

[HERVE MOENS via KDE Bugzilla]

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

Bug ID: 357151
   Summary: Crashes when trying to render
   Product: kdenlive
   Version: unspecified
  Platform: Archlinux Packages
   URL: https://www.youtube.com/watch?v=BvIS07NAlp0=yo
utu.be
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: herve.mo...@skynet.be

Version 15.07.0 (rev. v15.03.97-301-g9308597)
Using
KDE Frameworks 5.17.0
Qt 5.5.1 (built against 5.5.1)
The xcb windowing system

Reproducible: Always

Steps to Reproduce:
1.Add a clip (whatever it is)
2.Render


Actual Results:  
Kdenlive crashes and shuts down

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

[frameworks-kio] [Bug 352073] "http://ksnapshot/" is opened in web browser if KSnapshot is not installed

[Thomas Lübking via KDE Bugzilla]

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

Thomas Lübking  changed:

   What|Removed |Added

Product|khotkeys|frameworks-kio
 CC||kdelibs-b...@kde.org,
   ||thomas.luebk...@gmail.com
  Component|general |general
Version|5.4.0   |unspecified
   Assignee|k...@michael-jansen.biz  |fa...@kde.org

--- Comment #4 from Thomas Lübking  ---
We'd probably need some kind of kconf_update script to remove the ksnapshot
bits when installing spectacle (though it's still possible to have both) - or
in khotkeys (shipping default actions with khotkeys was probably a mistake ...
15 years ago ;-)

At least there's no ksnapshot (printscreen) default action anymore.

-> *Maybe* krun should not interpret "random_binary" as protocol/url.
Asking kio group.

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

[kde] [Bug 357154] New: Error description

[Reinhard Auner via KDE Bugzilla]

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

Bug ID: 357154
   Summary: Error description
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: reinhardau...@gmx.at

Application: apper-pk-session (0.9.1)
KDE Platform Version: 4.14.9
Qt Version: 4.8.6
Operating System: Linux 3.16.7-29-desktop x86_64
Distribution: "openSUSE 13.2 (Harlequin) (x86_64)"

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

I had running: Firefox 43.0, Amarok 2.8.0, KDE 4.14.9, openSUSE version
3.16.7-29-desktop from the openSUSE- main repository; I was installing various
debuginfo-packages from the openSUSE webpage.

-- Backtrace:
Application: Apper (apper-pk-session), signal: Bus error
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#5  0x7f7e5f688d99 in pthread_mutex_timedlock () at /lib64/libpthread.so.0
#6  0x7f7e63250bfc in  () at /usr/lib64/libkdecore.so.5
#7  0x7f7e6324faf2 in KSharedDataCache::find(QString const&, QByteArray*)
const () at /usr/lib64/libkdecore.so.5
#8  0x7f7e641d0d5e in  () at /usr/lib64/libkdeui.so.5
#9  0x7f7e641d1096 in KIconLoader::loadIcon(QString const&,
KIconLoader::Group, int, int, QStringList const&, QString*, bool) const () at
/usr/lib64/libkdeui.so.5
#10 0x7f7e6418e73f in KMessageBox::createKMessageBox(KDialog*,
QMessageBox::Icon, QString const&, QStringList const&, QString const&, bool*,
QFlags, QString const&) () at /usr/lib64/libkdeui.so.5
#11 0x7f7e6418f298 in KMessageBox::detailedSorryWId(unsigned long, QString
const&, QString const&, QString const&, QFlags) () at
/usr/lib64/libkdeui.so.5
#12 0x7f7e6418f387 in KMessageBox::detailedSorry(QWidget*, QString const&,
QString const&, QString const&, QFlags) () at
/usr/lib64/libkdeui.so.5
#13 0x7f7e6352d76b in PkTransaction::showSorry(QString const&, QString
const&, QString const&) (this=this@entry=0x120c2e0, title=..., description=...,
details=...) at /usr/src/debug/apper-0.9.1/libapper/PkTransaction.cpp:786
#14 0x7f7e6352da11 in
PkTransaction::slotErrorCode(PackageKit::Transaction::Error, QString const&)
(this=0x120c2e0, error=PackageKit::Transaction::ErrorInternalError,
details=...) at /usr/src/debug/apper-0.9.1/libapper/PkTransaction.cpp:275
#15 0x7f7e62a551fa in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () at /usr/lib64/libQtCore.so.4
#16 0x7f7e63dbd90a in
PackageKit::Transaction::errorCode(PackageKit::Transaction::Error, QString
const&) () at /usr/lib64/libpackagekitqt4.so.0
#17 0x7f7e63dc0374 in PackageKit::TransactionPrivate::errorCode(unsigned
int, QString const&) () at /usr/lib64/libpackagekitqt4.so.0
#18 0x7f7e63dbcb9a in  () at /usr/lib64/libpackagekitqt4.so.0
#19 0x7f7e62a551fa in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () at /usr/lib64/libQtCore.so.4
#20 0x7f7e63dca110 in
OrgFreedesktopPackageKitTransactionInterface::ErrorCode(unsigned int, QString
const&) () at /usr/lib64/libpackagekitqt4.so.0
#21 0x7f7e63dc86ba in  () at /usr/lib64/libpackagekitqt4.so.0
#22 0x7f7e63dc9d66 in
OrgFreedesktopPackageKitTransactionInterface::qt_metacall(QMetaObject::Call,
int, void**) () at /usr/lib64/libpackagekitqt4.so.0
#23 0x7f7e62dd3d4d in  () at /usr/lib64/libQtDBus.so.4
#24 0x7f7e62a5959e in QObject::event(QEvent*) () at
/usr/lib64/libQtCore.so.4
#25 0x7f7e61dd376c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQtGui.so.4
#26 0x7f7e61dd9cad in QApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQtGui.so.4
#27 0x7f7e6421ae0a in KApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libkdeui.so.5
#28 0x7f7e62a412ad in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /usr/lib64/libQtCore.so.4
#29 0x7f7e62a4457d in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib64/libQtCore.so.4
#30 0x7f7e62a6e8fe in  () at /usr/lib64/libQtCore.so.4
#31 0x7f7e5e1b1a04 in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#32 0x7f7e5e1b1c48 in  () at /usr/lib64/libglib-2.0.so.0
#33 0x7f7e5e1b1cec in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#34 0x7f7e62a6e0be in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQtCore.so.4
#35 0x7f7e61e70676 in  () at /usr/lib64/libQtGui.so.4
#36 0x7f7e62a3fe6f in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/libQtCore.so.4
#37 0x7f7e62a40165 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQtCore.so.4
#38 0x7f7e62a455b9 in QCoreApplication::exec() () at
/usr/lib64/libQtCore.so.4
#39 0x0040cdcc in main(int, char**) (argc=1, argv=0x7ffee97b6ec8) at

[plasmashell] [Bug 356470] Plasmashell 5.5 segfaults on shutdown (like 5.3)

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/plas
   ||ma-workspace/e8c6426ac12c14
   ||be68a68b9492274140c28f3285
 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #9 from David Edmundson  ---
Git commit e8c6426ac12c14be68a68b9492274140c28f3285 by David Edmundson.
Committed on 25/12/2015 at 18:16.
Pushed by davidedmundson into branch 'Plasma/5.5'.

Guard against applet failing to load in systemtray task

If an applet fails to load properly m_applet will be null which is a
valid state to be in when we destruct the plasmoid task object.
REVIEW: 126497

M  +3-1applets/systemtray/plugin/protocols/plasmoid/plasmoidtask.cpp

http://commits.kde.org/plasma-workspace/e8c6426ac12c14be68a68b9492274140c28f3285

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

[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar

[AnAkkk via KDE Bugzilla]

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

AnAkkk  changed:

   What|Removed |Added

Summary|plasmashell uses 100% CPU   |plasmashell uses 100% CPU
   |when octopi-notifier shows  |when there is an animation
   |that updates are available  |in the task bar

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

[krita] [Bug 356824] When zooming in, canvas does not render.

[David via KDE Bugzilla]

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

--- Comment #4 from David  ---
Apparently it's a windows 10 thing. I reverted back to windows 7 and it
works perfectly.

On Thu, Dec 17, 2015 at 10:27 AM, Boudewijn Rempt via KDE Bugzilla <
bugzilla_nore...@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=356824
>
> --- Comment #3 from Boudewijn Rempt  ---
> Hm, if it also happens when opengl is switched off, it cannot be a display
> driver issue. But I still haven't seen anything like this... You don't have
> transform masks or something like that in your test images?
>
> --
> You are receiving this mail because:
> You reported the bug.
>

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

[kdenlive] [Bug 356407] Custom Kdenlive install (DCMAKE_INSTALL_PREFIX): "View" menu can't show/hide tabs

[via KDE Bugzilla]

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

qubo...@gmail.com changed:

   What|Removed |Added

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

--- Comment #4 from qubo...@gmail.com ---
This has been resolved as of
https://quickgit.kde.org/?p=kdenlive.git=commit=8904948c2e170e382df0cd85710187dd0a8cdbe5

There appear to be related issues:
1. Wrong icons used
2. If breeze is installed system-wide, switching theme can cause crash

but i'll report separate tickets once I can properly describe them.

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

[kdenlive] [Bug 357111] Segfault if I set the name of a track and then click away without hitting enter

[Mark Long via KDE Bugzilla]

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

--- Comment #2 from Mark Long  ---
Fair enough. I was unaware that I was using an older build. I will update and
see if I can repro.

Thanks for looking at this and for the work that you are doing on an excellent
bit of software. Much appreciated.

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

[kmail2] [Bug 333611] error on decoding PGP-encoded messages

[Andre Heinecke via KDE Bugzilla]

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

--- Comment #17 from Andre Heinecke  ---
(In reply to Sandro Knauß from comment #15)
> @Andre thanks for the fast response. I now also have a bugfix for this bug.

> But I just get it right - from outside I can't differ if it is encrypted or
> only a encoded signature, because both use PGP MESSAGES header?

Yes.

> So there is no way to select the "correct" job for it. Is it recommended to 
> use
> verifyOpaqueJob in any case?

Sorry I have not designed this API. As I see it you can use either,
verifyOpaque (if it also decrypts) might produce nicer results as the general
decryptverify job but as far as I know it should be Ok to use both.

> Should we first ask gnupgp what kind of packets
> are inside the message?

Parsing the output of list-packets you mean? I don't think this is sensible to
do in KMail. Werner Koch will add API for this in GpgME in the next months
because we need to Answer the question "Hey GnuPG, what should we do with this
data" to better support file extensions (where it's often .asc or .gpg) for
various data formats this could then also be used in this case.

> @Andrew: You sent me a sample mail in private - is it okay if i publish it
> as testcase in the code? Because I can't read cryrillic, I can't deside if
> there are any sensible/private informations.

You can generate such a mail if you just do "echo foo | gpg2 -as" on the
command line and copy & paste this into a mail.

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

[amarok] [Bug 357112] Amarok

[Reinhard Auner via KDE Bugzilla]

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

--- Comment #2 from Reinhard Auner  ---
   Hello, dear Myriam, I am really sorry, but I am not able to reproduce
   this bug, but what I am currently doing is to install all the
   debuginfo-packages of my openSUSE in order to be able to produce more
   detailed and helpful reports for you develpoers in the future, ok?
   yours, Reinhard Auner * Gesendet:* Freitag, 25. Dezember 2015 um 16:36
   Uhr
   *Von:* "Myriam Schweingruber via KDE Bugzilla"
   
   *An:* reinhardau...@gmx.at
   *Betreff:* [amarok] [Bug 357112]
Amarokhttps://bugs.kde.org/show_bug.cgi?id=357112

   Myriam Schweingruber  changed:

   What |Removed |Added
   
   Resolution|--- |BACKTRACE
   Status|UNCONFIRMED |NEEDSINFO

   --- Comment #1 from Myriam Schweingruber  ---
   Unfortunately your backtrace has no debugging symbols, which makes it
   rather
   useless. Please install debugging symbols and provide a new backtrace,
   as well
   as exact steps on how to reproduce this crash.
   See also
  
https://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

   --
   You are receiving this mail because:
   You reported the bug.

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

[kdenlive] [Bug 357155] Deleting any video/audio track causes kdenlive to crash with a segmentation fault

[Anton Eliasson via KDE Bugzilla]

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

--- Comment #1 from Anton Eliasson  ---
Created attachment 96297
  --> https://bugs.kde.org/attachment.cgi?id=96297=edit
stack trace

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

[systemsettings] [Bug 356265] File associations app crashes

[Artur Puzio via KDE Bugzilla]

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

Artur Puzio  changed:

   What|Removed |Added

 CC||cytade...@op.pl

--- Comment #1 from Artur Puzio  ---
You said you changed or deleted the association of ".desktop" files and this
may triggered the crashing. Does this problem affect only the systemsettings
app or does it affect some other apps?
Please try repairing the association of ".desktop" files, to check if it fixes
it.

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

[Touchpad-KCM] [Bug 349545] Disable touchpad when mouse is plugged in, never re-enables when mouse is unplugged

[Weng Xuetian via KDE Bugzilla]

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

Weng Xuetian  changed:

   What|Removed |Added

 CC||wen...@gmail.com

--- Comment #2 from Weng Xuetian  ---
(In reply to Rex Dieter from comment #1)
> I tested and verified this behavior using both libinput and synaptics
> backends.

I have a review that may fix this bug:
https://git.reviewboard.kde.org/r/126513/

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

[gcompris] [Bug 357144] In Chess against Tux, the "redo" button does not work well

[via KDE Bugzilla]

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

stefan.to...@cti.pub.ro changed:

   What|Removed |Added

Summary|In the chess activity   |In Chess against Tux, the
   |against Tux, the "redo" |"redo" button does not work
   |button does not work well   |well
   |when is pressed multiple|
   |times very quickly  |

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

[telepathy] [Bug 354130] Telepathy can't connect to a Jabber account anymore

[via KDE Bugzilla]

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

andreas.sturmlech...@gmail.com changed:

   What|Removed |Added

 CC||andreas.sturmlechner@gmail.
   ||com

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

[kde] [Bug 357154] Error description

[Reinhard Auner via KDE Bugzilla]

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

Reinhard Auner  changed:

   What|Removed |Added

   Platform|unspecified |openSUSE RPMs

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

[plasmashell] [Bug 356790] Containment-controls theme elements in panel resizing mode are mixed up

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/plas
   ||ma-desktop/426a24c051d18787
   ||5abc0e373cdc252f151b1d21
 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #4 from David Edmundson  ---
Git commit 426a24c051d187875abc0e373cdc252f151b1d21 by David Edmundson.
Committed on 25/12/2015 at 18:14.
Pushed by davidedmundson into branch 'Plasma/5.5'.

Use the right graphics for min and max sliders

We never noticed on Breeze because they look the same.
REVIEW: 126498

M  +2-2   
desktoppackage/contents/configuration/panelconfiguration/Ruler.qml

http://commits.kde.org/plasma-desktop/426a24c051d187875abc0e373cdc252f151b1d21

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

[krita] [Bug 356592] crash when menu "settings -> configure krita" (win64)

[jimbo1qaz via KDE Bugzilla]

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

--- Comment #7 from jimbo1qaz  ---
pretty sure my opengl drivers are hosed.

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

[i18n] [Bug 356961] KWin rules, "Block compositing" is claimed to be translated as "Compositing by blocks"

[Sebastien Renard via KDE Bugzilla]

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

Sebastien Renard  changed:

   What|Removed |Added

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

--- Comment #1 from Sebastien Renard  ---
SVN commit 1448184 by renard:

Fix compositing translation


 M  +6 -5  kde-workspace/kcmkwincompositing.po  
 M  +5 -4  kde-workspace/kcmkwinrules.po  
 M  +4 -4  kde-workspace/kwin.po  
 M  +5 -5  www/www_www.po  


WebSVN link: http://websvn.kde.org/?view=rev=1448184

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

[plasmashell] [Bug 357147] Two different system settings windows could be confusing

[Kai Uwe Broulik via KDE Bugzilla]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 CC||k...@privat.broulik.de
 Resolution|--- |WAITINGFORINFO

--- Comment #2 from Kai Uwe Broulik  ---
The left one looks like the 4.x systemsettings and the right is the corret
systemsettings5. Did you recently upgrade to Plasma 5 with a Plasma 4 installed
already? I only have one systemsettings.

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

[kmail2] [Bug 357150] New: KMail crash on opening

[Rodney Baker via KDE Bugzilla]

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

Bug ID: 357150
   Summary: KMail crash on opening
   Product: kmail2
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: rodney.ba...@iinet.net.au

Application: kmail (4.14.9)
KDE Platform Version: 4.14.9
Qt Version: 4.8.6
Operating System: Linux 4.3.3-2.gdb72752-default x86_64
Distribution: "openSUSE 13.2 (Harlequin) (x86_64)"

-- Information about the crash:
KMail had hung while emptying the Trash folders on 2 IMAP accounts. It appeared
to close normally via File-Quit but crashed with the attached
segfault/backtrace when I next attempted to start it (about 30 mins later).

The crash can be reproduced sometimes.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f77ab517840 (LWP 12666))]

Thread 5 (Thread 0x7f7784b4b700 (LWP 12671)):
#0  0x7f77a669705f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f779bd94686 in WTF::TCMalloc_PageHeap::scavengerThread() () at
/usr/lib64/libQtWebKit.so.4
#2  0x7f779bd946b9 in  () at /usr/lib64/libQtWebKit.so.4
#3  0x7f77a66930a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f77a889208d in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f777f998700 (LWP 12672)):
#0  0x7f77a669705f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f779bb06e7d in JSC::BlockAllocator::blockFreeingThreadMain() () at
/usr/lib64/libQtWebKit.so.4
#2  0x7f779bdbc1e6 in WTF::wtfThreadEntryPoint(void*) () at
/usr/lib64/libQtWebKit.so.4
#3  0x7f77a66930a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f77a889208d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f777eb87700 (LWP 12673)):
#0  0x7f77a06028e9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0
#1  0x7f77a05c0299 in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f77a05c0b03 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f77a05c0cec in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f77a9ee40de in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQtCore.so.4
#5  0x7f77a9eb5e6f in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/libQtCore.so.4
#6  0x7f77a9eb6165 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQtCore.so.4
#7  0x7f77a9db30bf in QThread::exec() () at /usr/lib64/libQtCore.so.4
#8  0x7f77a9db579f in  () at /usr/lib64/libQtCore.so.4
#9  0x7f77a66930a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7f77a889208d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f777d0fc700 (LWP 12676)):
#0  0x7f77a669985a in __lll_unlock_wake () at /lib64/libpthread.so.0
#1  0x7f77a66965d9 in _L_unlock_554 () at /lib64/libpthread.so.0
#2  0x7f77a6696516 in __pthread_mutex_unlock_usercnt () at
/lib64/libpthread.so.0
#3  0x7f7793f3af45 in  () at /usr/lib64/libGL.so.1
#4  0x7f7793f40608 in  () at /usr/lib64/libGL.so.1
#5  0x7f779147a102 in  () at /usr/lib64/tls/libnvidia-tls.so.358.16
#6  0x7f77a0601750 in  () at /usr/lib64/libglib-2.0.so.0
#7  0x7f77a05c0714 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#8  0x7f77a05c0b7b in  () at /usr/lib64/libglib-2.0.so.0
#9  0x7f77a05c0cec in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#10 0x7f77a9ee40de in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQtCore.so.4
#11 0x7f77a9eb5e6f in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/libQtCore.so.4
#12 0x7f77a9eb6165 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQtCore.so.4
#13 0x7f77a9db30bf in QThread::exec() () at /usr/lib64/libQtCore.so.4
#14 0x7f77a9e97783 in  () at /usr/lib64/libQtCore.so.4
#15 0x7f77a9db579f in  () at /usr/lib64/libQtCore.so.4
#16 0x7f77a66930a4 in start_thread () at /lib64/libpthread.so.0
#17 0x7f77a889208d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f77ab517840 (LWP 12666)):
[KCrash Handler]
#6  0x7f77a9df8c88 in QString::operator==(QString const&) const () at
/usr/lib64/libQtCore.so.4
#7  0x7f77ab0cee5c in KStatusNotifierItem::setToolTipSubTitle(QString
const&) (this=0x1fbbb00, subTitle=...) at
/usr/src/debug/kdelibs-4.14.9/kdeui/notifications/kstatusnotifieritem.cpp:419
#8  0x7f77aa2d703e in  () at /usr/lib64/libkmailprivate.so.4
#9  0x7f77aa2d6f1d in  () at /usr/lib64/libkmailprivate.so.4
#10 0x7f77aa2d71f6 in  () at /usr/lib64/libkmailprivate.so.4
#11 0x7f77aa2dfea5 in KMKernel::toggleSystemTray() () at
/usr/lib64/libkmailprivate.so.4
#12 0x7f77aa30cd8f in KMMainWidget::readConfig() () at
/usr/lib64/libkmailprivate.so.4
#13 0x7f77aa31cab1 in 

[systemsettings] [Bug 357118] Can't switch graphics drivers

[Artur Puzio via KDE Bugzilla]

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

Artur Puzio  changed:

   What|Removed |Added

 CC||cytade...@op.pl

--- Comment #3 from Artur Puzio  ---
As you have written: the updates fixed the problem. So the problem with
switching the driver was fixed in an new version of something and doesn't need
fixing.
You also said that the updates should be pulled immediately after starting the
fresh installation for the first time. This problem is a future request
concerning a piece of software from Ubuntu. Please file a bug raport on their
bug tracker: https://bugs.launchpad.net/ubuntu/ and mark the bug here as
"RESOLVED: DOWNSTREAM"

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

[systemsettings] [Bug 353413] New keyboard shortcuts aren't active until you toggle them off and on, even after restart

[Artur Puzio via KDE Bugzilla]

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

Artur Puzio  changed:

   What|Removed |Added

 CC||cytade...@op.pl

--- Comment #2 from Artur Puzio  ---
After several tries I wasn't able to reproduce it on version 5.5.1 on Gentoo.
Everything seams to work fine. Could you try updating systemsettings and
checking then?

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

[konsole] [Bug 357152] New: Segmentation fault

[Argenis Balcazar via KDE Bugzilla]

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

Bug ID: 357152
   Summary: Segmentation fault
   Product: konsole
   Version: 15.08.0
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: emulation
  Assignee: konsole-de...@kde.org
  Reporter: argenisbalca...@gmail.com

Application: konsole (konsole), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6  0x7f25807141b3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x7f258070a5dd in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#8  0x7f258070ac79 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#9  0x7f25806ff2ed in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#10 0x7f25806ff399 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#11 0x7f2580049f52 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#12 0x7f2580049fa5 in exit () from /lib/x86_64-linux-gnu/libc.so.6
#13 0x7f2580034877 in __libc_start_main () from
/lib/x86_64-linux-gnu/libc.so.6
#14 0x00400749 in _start ()

Ejecutable: konsole PID: 2974 Señal: Segmentation fault (11) Hora: 25/12/15
12:39:35

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

[kdenlive] [Bug 357153] New: Increasing "Video quality" number in render panel actually reduces quality + increases compression

[Kubuntiac via KDE Bugzilla]

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

Bug ID: 357153
   Summary: Increasing "Video quality" number in render panel
actually reduces quality + increases compression
   Product: kdenlive
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: Video Display & Export
  Assignee: j...@kdenlive.org
  Reporter: user...@xymail.info

When using at least some output codecs, increasing the "video quality" number
actually does the reverse, instead ramping up compression (and lowering video
quality).

Reproducible: Always

Steps to Reproduce:
1. Place a sample video clip on the timeline
2. Choose render > MP4 > H265 HEVC and render
3. Increase the "video quality" number and render again

Actual Results:  
Video quality is degraded, and the file size decreases

Expected Results:  
Video quality increases along with the file size

While this is fairly simple, it still managed to take quite a lot of time out
of my day, as I experimented with different codecs and higher and higher
quality settings to try and improve the quality, before I realized it was doing
the opposite of what was expected.

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

[systemsettings] [Bug 355711] System Settings crashed during exit processing.

[Artur Puzio via KDE Bugzilla]

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

Artur Puzio  changed:

   What|Removed |Added

 CC||cytade...@op.pl

--- Comment #9 from Artur Puzio  ---
bug 356771 suggests that the problem is still in version 5.5.1. In this version
I'm also able to reproduce it.

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

[ksmserver] [Bug 357140] Can't terminate KDE session if it's been open for a long time

[Artur Puzio via KDE Bugzilla]

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

Artur Puzio  changed:

   What|Removed |Added

 CC||cytade...@op.pl

--- Comment #1 from Artur Puzio  ---
What do you mean by long time? Few hours, days or weeks?
Also this bug seams to be similar to bug 283879.

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

[systemsettings] [Bug 356771] System settings always crashes on closing

[Artur Puzio via KDE Bugzilla]

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

Artur Puzio  changed:

   What|Removed |Added

 CC||cytade...@op.pl

--- Comment #1 from Artur Puzio  ---
I tried changing several different setting and closing systemsettings after
hitting apply. I haven't encountered any crashes. I'm running version 5.5.1 on
Gentoo.
Also this bug seams to be a duplicate of bug 355711, that isn't marked as
resolved.

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

[kdenlive] [Bug 357155] Deleting any video/audio track causes kdenlive to crash with a segmentation fault

[Anton Eliasson via KDE Bugzilla]

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

--- Comment #2 from Anton Eliasson  ---
Also tested in an empty DV/DVD PAL project with the same result.

Desktop environment is Unity. Until I installed kdenlive I didn't have many KDE
packages installed, so I could possibly be missing some.

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

[systemsettings] [Bug 354179] File associations cannot be changed if already defined in $XDG_CONFIG_HOME/mimeapps.list

[Colin via KDE Bugzilla]

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

Colin  changed:

   What|Removed |Added

 CC||colinnkee...@gmail.com

--- Comment #6 from Colin  ---
Why is this still "UNCONFIRMED". It's clearly confirmed and a major issue for
the Plasma Desktop.

This table in the Arch Wiki will help the developers to solve this problem:

https://wiki.archlinux.org/index.php/Default_applications#MIME_types_and_desktop_entries

It shows the order of paths that are searched to find mimeapps.list. From this
table, it is obvious that the defaults set by Plasma Desktop should ideally be
stored in

$HOME/.config/$desktop-mimeapps.list

Or, at least in

$HOME/.config/mimeapps.list

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

[kdenlive] [Bug 357111] Segfault if I set the name of a track and then click away without hitting enter

[via KDE Bugzilla]

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

qubo...@gmail.com changed:

   What|Removed |Added

 CC||qubo...@gmail.com

--- Comment #1 from qubo...@gmail.com ---
I can not reproduce this in latest git.
kdenlive-git 15.12.0.r6759.5103ea6-1
mlt-git r4154.v0.9.2.376.g9e04d46-1

Video: https://youtu.be/F_Ah7aaC8mg

As stated on https://userbase.kde.org/Kdenlive/Manual/BugReporting , old
versions are not receiving support. It might be unfortunate to users who can't
or don't want to upgrade to the latest Kdenlive version but is unavoidable and
understandable considering the development team size.

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

[kdenlive] [Bug 357151] Crashes when trying to render

[HERVE MOENS via KDE Bugzilla]

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

--- Comment #1 from HERVE MOENS  ---
Created attachment 96296
  --> https://bugs.kde.org/attachment.cgi?id=96296=edit
Bugtrack

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

[trojita] [Bug 356437] Notifications through QToolTIp::showText appear on all desktops

[Jan Kundrát via KDE Bugzilla]

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

Jan Kundrát  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/troj
   ||ita/9b24073a05071a7145a4f92
   ||e4c781073481bb3c6
 Status|CONFIRMED   |RESOLVED

--- Comment #4 from Jan Kundrát  ---
Git commit 9b24073a05071a7145a4f92e4c781073481bb3c6 by Jan Kundrát, on behalf
of Thomas Lübking.
Committed on 16/12/2015 at 16:49.
Pushed by gerrit into branch 'master'.

only show status tooltip if the window is active

in addition, uconditionally set the tooltip to the message, so
it can be inspected anytime.
Change-Id: Ied9562741c390fbc8ffb560dd8ea481a185bd381

M  +3-1src/Gui/Window.cpp

http://commits.kde.org/trojita/9b24073a05071a7145a4f92e4c781073481bb3c6

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

[kdenlive] [Bug 357155] New: Deleting any video/audio track causes kdenlive to crash with a segmentation fault

[Anton Eliasson via KDE Bugzilla]

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

Bug ID: 357155
   Summary: Deleting any video/audio track causes kdenlive to
crash with a segmentation fault
   Product: kdenlive
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: kdeb...@antoneliasson.se

See summary and steps to reproduce.

Reproducible: Always

Steps to Reproduce:
1. Start kdenlive.
2. In the empty default project (in my case HD 1080p 29.97 fps), right click
any video or audio track and select delete.
3. Confirm in the popup.
4. kdenlive crashes.



Using version 4:15.12.0-0ubuntu0~sunab~vivid1 from sunab's PPA. OS is Ubuntu
15.04 64-bit.

Attaching stacktrace from gdb. The segfault is at

0x7561ab6c in mlt_service_connect_producer () from /usr/lib/libmlt.so.6

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

[systemsettings] [Bug 356771] System settings always crashes on closing

[Artur Puzio via KDE Bugzilla]

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

--- Comment #2 from Artur Puzio  ---
After reading comments on bug 355711 and changing to "Classic Tree View" mode
I'm also experiencing the problem.
Because bug 355711 isn't resolved, please mark this bug as "RESOLVED: DUPLICATE
of bug 355711". I commented on bug 355711 with information that in version
5.5.1 the problem is still present.

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

[systemsettings] [Bug 356337] Error

[Artur Puzio via KDE Bugzilla]

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

Artur Puzio  changed:

   What|Removed |Added

 CC||cytade...@op.pl

--- Comment #1 from Artur Puzio  ---
Please describe precisely when exactly the crash happened.

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

[systemsettings] [Bug 355711] System Settings crashed during exit processing.

[via KDE Bugzilla]

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

wulf.richa...@gmx.de changed:

   What|Removed |Added

 CC||wulf.richa...@gmx.de

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

[Breeze] [Bug 347524] Qt Creator Options crashed in Breeze theme

[Gunther Piez via KDE Bugzilla]

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

Gunther Piez  changed:

   What|Removed |Added

 CC||gp...@web.de

--- Comment #33 from Gunther Piez  ---
Still crashes in breeze-5.5.2. I have a similar crash with similar backtraces
if oxygen is active. Workaround: remove breeze.so and oxygen.so from 
/usr/lib64/qt5/plugins/styles ;-)
Has the additional benefit of getting rid of "the void
QWindowPrivate::setTopLevelScreen(QScreen*, bool) ( QScreen(0x69dd30) ):
Attempt to set a screen on a child window." spam qtcreator spits out if started
with breeze/oxygen.

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

[digikam] [Bug 357149] New: digikam crashes while writing Exif metadata

[via KDE Bugzilla]

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

Bug ID: 357149
   Summary: digikam crashes while writing Exif metadata
   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: rav...@gmx.at

Application: digikam (4.12.0)
KDE Platform Version: 4.14.13
Qt Version: 4.8.6
Operating System: Linux 4.2.0-22-generic x86_64
Distribution: Ubuntu 15.10

-- Information about the crash:
- What I was doing when the application crashed:
1) I changed the Exif  Timestamp of an image
2) Digikam crashed
3) I  tried it again (and again) with the same result.

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

Thread 8 (Thread 0x7fec517c9700 (LWP 5264)):
#0  0x7fec6f7ae8dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7fec5b96b12c in ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
#2  0x7fec6ccc56aa in start_thread (arg=0x7fec517c9700) at
pthread_create.c:333
#3  0x7fec6f7b9eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 7 (Thread 0x7fec4b907700 (LWP 5265)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fec70314286 in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x18a4950) at
thread/qwaitcondition_unix.cpp:86
#2  QWaitCondition::wait (this=this@entry=0x18a4890,
mutex=mutex@entry=0x18a4888, time=time@entry=18446744073709551615) at
thread/qwaitcondition_unix.cpp:158
#3  0x005fffb4 in Digikam::ScanController::run (this=0x18412b0) at
/build/digikam-131Z2v/digikam-4.12.0/core/app/database/scancontroller.cpp:725
#4  0x7fec70313d1c in QThreadPrivate::start (arg=0x18412b0) at
thread/qthread_unix.cpp:349
#5  0x7fec6ccc56aa in start_thread (arg=0x7fec4b907700) at
pthread_create.c:333
#6  0x7fec6f7b9eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7fec4b106700 (LWP 5266)):
#0  0x7fec6f7ae8dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7fec692601ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fec692602fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fec7045420e in QEventDispatcherGlib::processEvents
(this=0x7fec3c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#4  0x7fec704220d1 in QEventLoop::processEvents
(this=this@entry=0x7fec4b105a40, flags=...) at kernel/qeventloop.cpp:149
#5  0x7fec70422445 in QEventLoop::exec (this=this@entry=0x7fec4b105a40,
flags=...) at kernel/qeventloop.cpp:204
#6  0x7fec703114f9 in QThread::exec (this=this@entry=0x18c7020) at
thread/qthread.cpp:538
#7  0x7fec70402133 in QInotifyFileSystemWatcherEngine::run (this=0x18c7020)
at io/qfilesystemwatcher_inotify.cpp:265
#8  0x7fec70313d1c in QThreadPrivate::start (arg=0x18c7020) at
thread/qthread_unix.cpp:349
#9  0x7fec6ccc56aa in start_thread (arg=0x7fec4b106700) at
pthread_create.c:333
#10 0x7fec6f7b9eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7fec4a905700 (LWP 5269)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fec70314286 in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x18ec5b0) at
thread/qwaitcondition_unix.cpp:86
#2  QWaitCondition::wait (this=this@entry=0x1aa84e0,
mutex=mutex@entry=0x1aa84d8, time=time@entry=18446744073709551615) at
thread/qwaitcondition_unix.cpp:158
#3  0x7fec74691f02 in Digikam::ParkingThread::run (this=0x1aa84c0) at
/build/digikam-131Z2v/digikam-4.12.0/core/libs/threads/threadmanager.cpp:119
#4  0x7fec70313d1c in QThreadPrivate::start (arg=0x1aa84c0) at
thread/qthread_unix.cpp:349
#5  0x7fec6ccc56aa in start_thread (arg=0x7fec4a905700) at
pthread_create.c:333
#6  0x7fec6f7b9eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7febcdb66700 (LWP 5317)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fec70314286 in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x46de720) at
thread/qwaitcondition_unix.cpp:86
#2  QWaitCondition::wait (this=this@entry=0x471a530,
mutex=mutex@entry=0x471a528, time=time@entry=18446744073709551615) at
thread/qwaitcondition_unix.cpp:158
#3  0x7febdc7117f8 in KIPIPlugins::KPRawThumbThread::run (this=0x46ddd90)
at
/build/digikam-131Z2v/digikam-4.12.0/extra/kipi-plugins/common/libkipiplugins/tools/kprawthumbthread.cpp:108
#4  0x7fec70313d1c in QThreadPrivate::start (arg=0x46ddd90) at
thread/qthread_unix.cpp:349
#5  0x7fec6ccc56aa in 

[i18n] [Bug 356961] KWin rules, "Block compositing" is claimed to be translated as "Compositing by blocks"

[Sebastien Renard via KDE Bugzilla]

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

Sebastien Renard  changed:

   What|Removed |Added

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

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

[konsole] [Bug 347008] Konsole does not start, process list shows several konsole instances as "defunct".

[via KDE Bugzilla]

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

lampus.la...@gmail.com changed:

   What|Removed |Added

 CC||lampus.la...@gmail.com

--- Comment #1 from lampus.la...@gmail.com ---
Software versions:
Linux Distr.: Arch Linux
Konsole version 15.12.0
KDE Frameworks 5.17.0
Qt 5.5.1

$ pacman -Qi konsole | grep Version
Version: 15.12.0-1

$ pacman -Qi plasma-desktop | grep Version
Version: 5.5.2-1

Steps to reproduce:
1. Start new konsole from K-menu or Run Command dialog.
2. Close all tabs
3. Try to start konsole again

Actual Results: Launch feedback occurs, no window is opened, no error messages
displayed. Effectively, nothing seems to happen. Expected Results: Konsole
should start normally.

Expected Results: Konsole should start normally.

$ ps aux | grep konsole
lampus3647  1.7  1.3 468744 52548 ?Sl   17:43   0:00
/usr/bin/konsole
lampus3657  0.4  0.9 320428 39588 ?S17:43   0:00
/usr/bin/konsole
lampus3658  0.0  0.0  0 0 ?Z17:43   0:00 [konsole]

lampus3665  0.0  0.0  11972  2300 pts/1R+   17:43   0:00 grep konsole

Sometimes crash occured:
Application: Konsole (konsole), signal: Aborted
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[KCrash Handler]
#5  0x7f7f925865f8 in raise () from /usr/lib/libc.so.6
#6  0x7f7f92587a7a in abort () from /usr/lib/libc.so.6
#7  0x7f7f925c505a in __libc_message () from /usr/lib/libc.so.6
#8  0x7f7f925ca9a6 in malloc_printerr () from /usr/lib/libc.so.6
#9  0x7f7f925cb18e in _int_free () from /usr/lib/libc.so.6
#10 0x7f7f8f106c4c in QMetaCallEvent::~QMetaCallEvent() () from
/usr/lib/libQt5Core.so.5
#11 0x7f7f8f106c99 in QMetaCallEvent::~QMetaCallEvent() () from
/usr/lib/libQt5Core.so.5
#12 0x7f7f8f0dd707 in QCoreApplication::removePostedEvents(QObject*, int)
() from /usr/lib/libQt5Core.so.5
#13 0x7f7f8f108a22 in QObjectPrivate::~QObjectPrivate() () from
/usr/lib/libQt5Core.so.5
#14 0x7f7f8f108b49 in QObjectPrivate::~QObjectPrivate() () from
/usr/lib/libQt5Core.so.5
#15 0x7f7f8f111618 in QObject::~QObject() () from /usr/lib/libQt5Core.so.5
#16 0x7f7f7f513409 in QXcbConnection::~QXcbConnection() () from
/usr/lib/libQt5XcbQpa.so.5
#17 0x7f7f7f514ea6 in QXcbIntegration::~QXcbIntegration() () from
/usr/lib/libQt5XcbQpa.so.5
#18 0x7f7f7f514fb9 in QXcbIntegration::~QXcbIntegration() () from
/usr/lib/libQt5XcbQpa.so.5
#19 0x7f7f8f411d43 in QGuiApplicationPrivate::~QGuiApplicationPrivate() ()
from /usr/lib/libQt5Gui.so.5
#20 0x7f7f8f9c8a09 in QApplicationPrivate::~QApplicationPrivate() () from
/usr/lib/libQt5Widgets.so.5
#21 0x7f7f8f111618 in QObject::~QObject() () from /usr/lib/libQt5Core.so.5
#22 0x7f7f8f9ca7f9 in QApplication::~QApplication() () from
/usr/lib/libQt5Widgets.so.5
#23 0x7f7f929212e8 in kdemain () from /usr/lib/libkdeinit5_konsole.so
#24 0x7f7f92573610 in __libc_start_main () from /usr/lib/libc.so.6
#25 0x00400779 in _start ()

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

[digikam] [Bug 354364] Crash of DNG converter

[via KDE Bugzilla]

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

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

   What|Removed |Added

 CC||rav...@gmx.at

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

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

[digikam] [Bug 357149] digikam crashes while writing Exif metadata

[via KDE Bugzilla]

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

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

   What|Removed |Added

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

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


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

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

[plasma4] [Bug 341184] 'Left Mouse Click' doesn't work / function with Plasma Widgets

[PGillespie via KDE Bugzilla]

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

--- Comment #12 from PGillespie  ---
This has been posted for a while. 

Not trying to be provocative or in-your-face, but am I correct in thinking this
is pretty much a "Won't Fix" bug? KDE 4 is yesterday's news and ARM is a niche
of a niche. My little ARMHF CPU was so ill-suited to Linux that I altogether
quit using it.

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

[systemsettings] [Bug 357145] New: 使用 系统设置/硬件/输入设备/触摸板 时， 系统设置程序自己关闭

[via KDE Bugzilla]

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

Bug ID: 357145
   Summary: 使用  系统设置/硬件/输入设备/触摸板 时， 系统设置程序自己关闭
   Product: systemsettings
   Version: 5.4.1
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: abo...@21cn.com

Application: systemsettings5 (5.4.1)

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:
用鼠标左键按住 “拖拽我”，拖拽的第二次时，系统设置程序自己关闭。 
但再次使用 系统设置程序， 重复相同的做，却很正常

-- Backtrace:
Application: 系统设置 (systemsettings5), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f4c8eb34780 (LWP 9719))]

Thread 6 (Thread 0x7f4c7c5c0700 (LWP 9720)):
#0  0x7f4c8a8c0c1d in poll () at /lib64/libc.so.6
#1  0x7f4c876a5422 in  () at /usr/lib64/libxcb.so.1
#2  0x7f4c876a700f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7f4c7e914c29 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f4c8afb755f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f4c86e300a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7f4c8a8c904d in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7f4c6cfa3700 (LWP 9721)):
#0  0x7f4c86e3405f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f4c6d1177eb in  () at /usr/lib64/libQt5Script.so.5
#2  0x7f4c6d117819 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7f4c86e300a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f4c8a8c904d in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f4bdcd41700 (LWP 9736)):
#0  0x7f4c8a8c0c1d in poll () at /lib64/libc.so.6
#1  0x7f4c86913e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f4c8691419a in g_main_loop_run () at /usr/lib64/libglib-2.0.so.0
#3  0x7f4be1fbc426 in  () at /usr/lib64/libgio-2.0.so.0
#4  0x7f4c86938f65 in  () at /usr/lib64/libglib-2.0.so.0
#5  0x7f4c86e300a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7f4c8a8c904d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f4bd6078700 (LWP 10023)):
#0  0x7f4c86939409 in g_thread_self () at /usr/lib64/libglib-2.0.so.0
#1  0x7f4c86912ecc in g_main_context_acquire () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f4c86913d25 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f4c86913f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f4c8b1e8a5b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7f4c8b18fa63 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7f4c8afb284a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7f4c895435f8 in  () at /usr/lib64/libQt5Qml.so.5
#8  0x7f4c8afb755f in  () at /usr/lib64/libQt5Core.so.5
#9  0x7f4c86e300a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7f4c8a8c904d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f4bd707a700 (LWP 10035)):
#0  0x7f4c86955cf0 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0
#1  0x7f4c869136a1 in g_main_context_query () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f4c86913dcf in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f4c86913f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f4c8b1e8a5b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7f4c8b18fa63 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7f4c8afb284a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7f4c895435f8 in  () at /usr/lib64/libQt5Qml.so.5
#8  0x7f4c8afb755f in  () at /usr/lib64/libQt5Core.so.5
#9  0x7f4c86e300a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7f4c8a8c904d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f4c8eb34780 (LWP 9719)):
[KCrash Handler]
#6  0x7f4c8c86308b in QStandardItemModel::mimeData(QList
const&) const () at /usr/lib64/libQt5Gui.so.5
#7  0x7f4c8cf1ec69 in  () at /usr/lib64/libQt5Widgets.so.5
#8  0x7f4c8cf1e65f in QListView::startDrag(QFlags) () at
/usr/lib64/libQt5Widgets.so.5
#9  0x7f4c8cf00adf in QAbstractItemView::mouseMoveEvent(QMouseEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#10 0x7f4c8cf1e1c4 in QListView::mouseMoveEvent(QMouseEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#11 0x7f4c8ccebfe8 in QWidget::event(QEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#12 0x7f4c8cde64de in QFrame::event(QEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#13 0x7f4c8cf014cb in QAbstractItemView::viewportEvent(QEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#14 0x7f4c8b191de3 in
QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () at
/usr/lib64/libQt5Core.so.5
#15 0x7f4c8ccabe6c in 

[krita] [Bug 356592] crash when menu "settings -> configure krita" (win64)

[Boudewijn Rempt via KDE Bugzilla]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |INVALID

--- Comment #8 from Boudewijn Rempt  ---
Okay -- I'm afraid there isn't much I can do then.

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

[konqueror] [Bug 357156] New: GitHub branch/tag switcher doesn't show any branches/tags

[Robin Green via KDE Bugzilla]

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

Bug ID: 357156
   Summary: GitHub branch/tag switcher doesn't show any
branches/tags
   Product: konqueror
   Version: 4.14.3
  Platform: Fedora RPMs
   URL: https://github.com/leksah/leksah#building-on-linux
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: konq-b...@kde.org
  Reporter: gree...@greenrd.org

The dropdown branch list on Github is truncated and shows 0 entries.

Reproducible: Always

Steps to Reproduce:
1. Go to URL above 
2. Click on the "Branch: master" button

Actual Results:  
An HTML popup appears with a textbox and two tabs, one called "branches" and
the other called "tags", but in both tabs, no branches or tags are visible.

Expected Results:  
Branches such as 0.12 should be visible (as I can see in Firefox).

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

[marble] [Bug 357157] Marble crashes while trying to open .osm files using the open file icon in Edit Maps Panel.

[sutirtha via KDE Bugzilla]

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

--- Comment #1 from sutirtha  ---
Created attachment 96299
  --> https://bugs.kde.org/attachment.cgi?id=96299=edit
the .osm file that causes the  crash

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

[kwin] [Bug 357116] Using a window rule to turn off compositing causes flickering windows when compositing is turned back on

[Thomas Lübking via KDE Bugzilla]

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

--- Comment #9 from Thomas Lübking  ---
(In reply to AnAkkk from comment #8)

> xkill has no effect on it, it's still here.

Err, what?
It would then probably belong to a crashed (and stopped) process?
ps ax | grep T

> > ... "glxgears", sorry :-)
> Just tried, I don't have issues 2) and 3) with glxgears.

What about fullscreen glxgears (you can turn it fullscreen using  the Alt+F3
menu and in doubt close it by Alt+F4 w/o unfullscreening it before)

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

[frameworks-kglobalaccel] [Bug 353926] Global shortcuts using wrong layout

[Holger via KDE Bugzilla]

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

--- Comment #6 from Holger  ---
I was pointed here by Thomas Lübking:
https://forum.kde.org/viewtopic.php?f=289=130179=348185#p348185

In my case, the wrong mappings are tied to passwordless autologin on boot (as
I'm using harddrive encryption and typing one password is enough for my taste.)
That is, can someone reproduce wrong global shortcut mappings, after explicitly
logging out, selecting his account and logging in again?

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

[kdesrc-build] [Bug 357162] Hardcoded reference to inexistent URL

[Raphael Kubo da Costa via KDE Bugzilla]

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

Raphael Kubo da Costa  changed:

   What|Removed |Added

   Assignee|neund...@kde.org|mp...@kde.org
Product|buildsystem |kdesrc-build
  Component|KDE4 (cmake)|general

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

[konsole] [Bug 345403] "Terminal Size" setting in profile ignored

[Philip Smith via KDE Bugzilla]

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

Philip Smith  changed:

   What|Removed |Added

 CC||p...@mssl.ucl.ac.uk

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

[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar

[AnAkkk via KDE Bugzilla]

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

AnAkkk  changed:

   What|Removed |Added

Version|5.5.0   |5.5.2

--- Comment #1 from AnAkkk  ---
This is actually not specific to octopi-notifier. I just had a connection issue
and the network applet kept trying to connect, which also displayed the
"connection" animation in the task bar, and I had exactly the same issue. My
computer was very laggy (the mouse would "jump" on the screen) and plasmashell
CPU usage was increasing.

Stopping the connection would fix the issue (plasmashell CPU usage would go
back to 0%) and trying to connect again would bring the issue back again.
For octopi, when there is an update, it changes the icon in the task bar and
it's animated as well.

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

[plasmashell] [Bug 357147] Two different system settings windows could be confusing

[Kai Uwe Broulik via KDE Bugzilla]

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

--- Comment #4 from Kai Uwe Broulik  ---
If you have 4.x apps that spawn a systemsettings entry, they won't be
accessible in the 5 systemsettings. This was most prominent with KDE PIM, which
now has a 5 release now, however.

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

[kdenlive] [Bug 357155] Deleting any video/audio track causes kdenlive to crash with a segmentation fault

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

Jean-Baptiste Mardelle  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/kden
   ||live/d38f09b584a2ab0d793b64
   ||b7fd013e6a2ab82769

--- Comment #3 from Jean-Baptiste Mardelle  ---
Git commit d38f09b584a2ab0d793b64b7fd013e6a2ab82769 by Jean-Baptiste Mardelle.
Committed on 25/12/2015 at 20:29.
Pushed by mardelle into branch 'Applications/15.12'.

Fix crash on add/delete track when frei0r cairoblend transition is not
available

M  +6-4src/renderer.cpp
M  +4-0src/timeline/customtrackview.cpp

http://commits.kde.org/kdenlive/d38f09b584a2ab0d793b64b7fd013e6a2ab82769

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

[ktorrent] [Bug 357160] New: KTorrent GUI freezes randlomly and stops torrent downloads

[Philip via KDE Bugzilla]

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

Bug ID: 357160
   Summary: KTorrent GUI freezes randlomly and stops torrent
downloads
   Product: ktorrent
   Version: 4.3.1
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: joris.guis...@gmail.com
  Reporter: phil.t...@gmail.com

Application: ktorrent (4.3.1)
KDE Platform Version: 4.14.13
Qt Version: 4.8.6
Operating System: Linux 4.2.0-22-generic x86_64
Distribution: Ubuntu 15.10

-- Information about the crash:
- What I was doing when the application crashed:
After starting the KTorrent application it works normally, but usually after
several seconds (generally less than a minute) freezes. Sometimes if I wait
long enough GUI unfreezes and all torrents restart which indicates that there
was no app activity while GUI was frozen. Same happens if I minimize KTorrent
to tray right after start - the information while hovering above tray icon is
not being updated and torrents are not being downloaded, also app doesn't
revert to window mode while frozen.

The crash can be reproduced every time.

-- Backtrace:
Application: KTorrent (ktorrent), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7efffbd97840 (LWP 1723))]

Thread 5 (Thread 0x7effdeffd700 (LWP 1733)):
#0  std::pair >::pair
(this=0x7effc826ddc0) at /usr/include/c++/5/bits/stl_pair.h:96
#1  __gnu_cxx::new_allocator >::construct (this=,
__val=..., __p=0x7effc826ddc0) at /usr/include/c++/5/ext/new_allocator.h:130
#2  std::_Rb_tree,
std::_Select1st >,
std::less, std::allocator > >::_M_construct_node (this=,
__x=..., __node=0x7effc826dda0) at /usr/include/c++/5/bits/stl_tree.h:502
#3  std::_Rb_tree,
std::_Select1st >,
std::less, std::allocator > >::_M_create_node (this=,
__x=...) at /usr/include/c++/5/bits/stl_tree.h:514
#4  std::_Rb_tree,
std::_Select1st >,
std::less, std::allocator > >::_Alloc_node::operator() > (this=,
__arg=...) at /usr/include/c++/5/bits/stl_tree.h:459
#5  std::_Rb_tree,
std::_Select1st >,
std::less, std::allocator > >::_M_insert_,
std::_Select1st >,
std::less, std::allocator > >::_Alloc_node> (__node_gen=, __v=..., __p=0x95ec60, __x=, this=0x95ec58) at
/usr/include/c++/5/bits/stl_tree.h:1509
#6  std::_Rb_tree,
std::_Select1st >,
std::less, std::allocator > >::_M_insert_unique_,
std::_Select1st >,
std::less, std::allocator > >::_Alloc_node> (__node_gen=, __v=..., __position=..., this=0x95ec58) at
/usr/include/c++/5/bits/stl_tree.h:1978
#7  std::_Rb_tree,
std::_Select1st >,
std::less, std::allocator > >::_M_insert_unique_ (__x=..., __pos=...,
this=0x95ec58) at /usr/include/c++/5/bits/stl_tree.h:984
#8  std::map >
>::insert (__x=..., __position=..., this=0x95ec58) at
/usr/include/c++/5/bits/stl_map.h:666
#9  std::map >
>::operator[] (__k=, this=0x95ec58) at
/usr/include/c++/5/bits/stl_map.h:487
#10 net::Poll::add (this=this@entry=0x95ec30, pc=...) at
../../src/net/poll.cpp:74
#11 0x7efffb917550 in net::DownloadThread::waitForSocketReady
(this=this@entry=0x95ec20) at ../../src/net/downloadthread.cpp:114
#12 0x7efffb917716 in net::DownloadThread::update (this=0x95ec20) at
../../src/net/downloadthread.cpp:48
#13 0x7efffb917919 in net::NetworkThread::run (this=0x95ec20) at
../../src/net/networkthread.cpp:48
#14 0x7efff877dd1c in QThreadPrivate::start (arg=0x95ec20) at
thread/qthread_unix.cpp:349
#15 0x7efff4aa56aa in start_thread (arg=0x7effdeffd700) at
pthread_create.c:333
#16 0x7efff7b9eeed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7effde7fc700 (LWP 1734)):
#0  syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1  0x7efff877c622 in _q_futex (val2=0, addr2=0x0, timeout=0x0, val=2,
op=0, addr=0x95ebf0) at thread/qmutex_unix.cpp:99
#2  QMutexPrivate::wait (this=this@entry=0x95ebf0, timeout=timeout@entry=-1) at
thread/qmutex_unix.cpp:113
#3  0x7efff8778a1d in QMutex::lock (this=) at
thread/qmutex.cpp:164
#4  0x7efffb915f39 in net::SocketMonitor::lock (this=) at
../../src/net/socketmonitor.cpp:108
#5  0x7efffb91706c in net::UploadThread::update (this=0x95f010) at
../../src/net/uploadthread.cpp:49
#6  0x7efffb917919 in net::NetworkThread::run (this=0x95f010) at
../../src/net/networkthread.cpp:48
#7  

[kwin] [Bug 357116] Using a window rule to turn off compositing causes flickering windows when compositing is turned back on

[AnAkkk via KDE Bugzilla]

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

--- Comment #12 from AnAkkk  ---
(In reply to Thomas Lübking from comment #11)
> Do you have positive knowledge on the relation, ie. does killing plasmashell
> remove the window?

No, you're right, it doesn't actually remove the window. But I thought this was
plasmashell, since it's at the place of the desktop "movable menu".

> Errr... stupid question: did you optirun glxgears?

No, but now I did, no difference :/

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

[kipiplugins] [Bug 320308] "Failed to upload photo into Flickr" every time after first use

[Bill Prout via KDE Bugzilla]

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

Bill Prout  changed:

   What|Removed |Added

 CC||okicha...@gmail.com

--- Comment #13 from Bill Prout  ---
On Version 4.14.0, I'm getting the "failed" error trying to export to flickr.
After some experimenting, I found that it will upload only if I check (on the
Upload Options tab) either "Send original file (no resizing)"  or "Resize
photos before uploading".  
No checks gives the failed message.
Cheers

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

[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar

[AnAkkk via KDE Bugzilla]

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

AnAkkk  changed:

   What|Removed |Added

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

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

[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar

[AnAkkk via KDE Bugzilla]

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

--- Comment #2 from AnAkkk  ---
I added two issues which seem related. Maybe
https://bugs.kde.org/show_bug.cgi?id=351923 is also related?

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

[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar

[AnAkkk via KDE Bugzilla]

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

AnAkkk  changed:

   What|Removed |Added

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

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

[plasma-nm] [Bug 357099] Stuck at connecting animation [regression]

[AnAkkk via KDE Bugzilla]

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

AnAkkk  changed:

   What|Removed |Added

 CC||anakin...@gmail.com

--- Comment #4 from AnAkkk  ---
I think I had the same problem here (high CPU usage):
https://bugs.kde.org/show_bug.cgi?id=356479

This is not only specific to the network applet, but any animation on the task
bar is actually causing this CPU usage issue apparently.

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

[kdenlive] [Bug 357153] Increasing "Video quality" number in render panel actually reduces quality + increases compression

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

Jean-Baptiste Mardelle  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #1 from Jean-Baptiste Mardelle  ---
Yes, the "less is better" logic comes from FFmpeg, where several quality
parameter use a scale where 0 is the best possible quality and higher numbers
degrade the quality.

I totally agree that this is highly counter-intuitive.

We plan to redesign the rendering widget to provide better defaults and a
cleaner interface, and this issue should be handled by the redesign.

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

[kdelibs] [Bug 183458] Numpad (keypad) keys not mapped correctly when setting Global Shortcuts

[Holger via KDE Bugzilla]

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

Holger  changed:

   What|Removed |Added

 CC||h.kl...@gmx.de

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

[kdelibs] [Bug 309193] Keyboard shortcuts doesn't work if non-english keyboard layout is set before english one

[Holy via KDE Bugzilla]

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

--- Comment #57 from Holy  ---
This fixed the problem for me (from
https://forum.kde.org/viewtopic.php?f=289=130179=348185#p348027 ):

pkill kglobalaccel5
kglobalaccel5 &

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

[ksmserver] [Bug 357140] Can't terminate KDE session if it's been open for a long time

[Fibonacci via KDE Bugzilla]

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

--- Comment #3 from Fibonacci  ---
Also, I don't think it's the same as bug 283879, since my qdbus command
actually does generate some output.

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

[plasmashell] [Bug 357038] Add this date style: lun. 21 déc. 21:50

[Sudhir Khanger via KDE Bugzilla]

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

Sudhir Khanger  changed:

   What|Removed |Added

 CC||sud...@sudhirkhanger.com

--- Comment #1 from Sudhir Khanger  ---
My suggestions are as follows.

* Only use 3 letters for weekday and month.
* Ability to disable year. There is not a whole lot of benefit in showing a
number that changes only once a year.

Saturday 26 December 2015 is way too long. There is no much benefit. It would
save precious horizontal space if we only show first 3 letters of week day and
month.

Thank you.

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

[plasma4] [Bug 312919] high CPU usage for copying notification

[AnAkkk via KDE Bugzilla]

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

AnAkkk  changed:

   What|Removed |Added

 CC||anakin...@gmail.com

--- Comment #8 from AnAkkk  ---
Seems like this is the same as:
https://bugs.kde.org/show_bug.cgi?id=356479
https://bugs.kde.org/show_bug.cgi?id=357099

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

[krazy] [Bug 357008] Stats graphic wrong

[Frederik Schwarzer via KDE Bugzilla]

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

Frederik Schwarzer  changed:

   What|Removed |Added

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

--- Comment #2 from Frederik Schwarzer  ---
This was fixed today. Thanks. :)

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

[kdenlive] [Bug 357155] Deleting any video/audio track causes kdenlive to crash with a segmentation fault

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

--- Comment #4 from Jean-Baptiste Mardelle  ---
Thanks for your report. The crash happens because an item from the frei0r
package is missing. I just fixed the crash in git. As a workaround, try
installing the "frei0r-plugins" package, it should solve your problem.

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

[kdenlive] [Bug 356162] .mxf (mpeg2) footage clips are not added completely

[Rhizomatic Nomad via KDE Bugzilla]

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

--- Comment #6 from Rhizomatic Nomad  ---
I didn't manage to install the git version of FFmpeg, but tried it in Arch
Linux with the ffmpeg 1:2.8.4-1, build on 20th December. The error/bug sadly
still remains.

In the Kdenlive forum a user suggested to convert the files with "ffmpeg -i
1080i_25fps_footage.mxf -c copy x.mkv" which works as a workaround.

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

[kwin] [Bug 357116] Using a window rule to turn off compositing causes flickering windows when compositing is turned back on

[AnAkkk via KDE Bugzilla]

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

--- Comment #10 from AnAkkk  ---
(In reply to Thomas Lübking from comment #9)
> It would then probably belong to a crashed (and stopped) process?
> ps ax | grep T

No, nothing. xkill probably doesn't work because there is no PID attached to
the window (doesn't it rely on the PID that is showed by xprop?)
.Anyway, why would it belong to a crashed process, since we know it belongs to
plasmashell?

> What about fullscreen glxgears (you can turn it fullscreen using  the Alt+F3
> menu and in doubt close it by Alt+F4 w/o unfullscreening it before)

Tried, that doesn't trigger the issue either.

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

[plasmashell] [Bug 357165] New: Hangout Configure

[Luca via KDE Bugzilla]

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

Bug ID: 357165
   Summary: Hangout Configure
   Product: plasmashell
   Version: 5.4.2
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: lucagiovagnoli...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.4.2)

Qt Version: 5.4.2
Operating System: Linux 4.2.0-22-generic x86_64
Distribution: Ubuntu 15.10

-- Information about the crash:
Plasma crashing every time I hit Configure after adding Hangoutss

The crash can be reproduced every time.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7ffa93914800 (LWP 4846))]

Thread 11 (Thread 0x7ffa7ef6b700 (LWP 4848)):
#0  0x7ffa8e0bb8dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7ffa92102bd2 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7ffa9210474f in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7ffa812b5a39 in ?? () from
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so
#4  0x7ffa8e7ae2be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7ffa8d89d6aa in start_thread (arg=0x7ffa7ef6b700) at
pthread_create.c:333
#6  0x7ffa8e0c6eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 10 (Thread 0x7ffa7c938700 (LWP 4869)):
#0  0x7ffa8e0bb8dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7ffa8ae681ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7ffa8ae682fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7ffa8e9e529b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7ffa8e98b75a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7ffa8e7a93d4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7ffa90fd1f85 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7ffa8e7ae2be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7ffa8d89d6aa in start_thread (arg=0x7ffa7c938700) at
pthread_create.c:333
#9  0x7ffa8e0c6eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 9 (Thread 0x7ffa6d51e700 (LWP 4877)):
#0  0x7ffa8e0bb8dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7ffa8ae681ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7ffa8ae682fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7ffa8e9e529b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7ffa8e98b75a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7ffa8e7a93d4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7ffa90fd1f85 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7ffa8e7ae2be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7ffa8d89d6aa in start_thread (arg=0x7ffa6d51e700) at
pthread_create.c:333
#9  0x7ffa8e0c6eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 8 (Thread 0x7ffa66c4c700 (LWP 4881)):
#0  0x7ffa8aeac884 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7ffa8ae68306 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7ffa8e9e529b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7ffa8e98b75a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7ffa8e7a93d4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7ffa90fd1f85 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#6  0x7ffa8e7ae2be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7ffa8d89d6aa in start_thread (arg=0x7ffa66c4c700) at
pthread_create.c:333
#8  0x7ffa8e0c6eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 7 (Thread 0x7ffa65309700 (LWP 4903)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7ffa9335d114 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#2  0x7ffa9335d159 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#3  0x7ffa8d89d6aa in start_thread (arg=0x7ffa65309700) at
pthread_create.c:333
#4  0x7ffa8e0c6eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7ff9d7fff700 (LWP 5018)):
#0  0x7ffa938d48c0 in __GI___tls_get_addr (ti=0x7ffa8ebc2718) at
dl-tls.c:830
#1  0x7ffa8e7ad202 in ?? 

[plasmashell] [Bug 356899] Desktop Settings are not saved and loads default settings on reboot/startup.

[Frank Sandefur via KDE Bugzilla]

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

Frank Sandefur  changed:

   What|Removed |Added

 CC||fsande...@mchsi.com

--- Comment #11 from Frank Sandefur  ---
I am having the same issue on Kubuntu 15.10.  However, my trouble began when I
configured a second monitor to my system. 

It is worth noting that my hardware configuration has not changed, and worked
flawlessly under Kubuntu 14.04LTS (Plasm 4.8.6 I think).  

On reboot I come to a blank screen, drivers and resolution appear to be
correct. a Right-click to open Folder View Settings reveals it has reverted to
Desktop Layout with no wallpaper selected. Selecting Folder view and a
wallpaper restores everything, except that all my icons have reverted to
default sizes and are lined up across the top of the screen, rather than the
smaller sizes and arrangement I'd manually set up.

My system is:  Kubuntu 15.10, KDE Plasma version 5.4.2, Qt version 5.4.2,
Kernel version 4.2.0-22-generic, 64-bit.
4 x Intel Core I5-3470 CPU @3.20 GHz, 7.7 GiB Ram, Nvidia 2Gb GT640

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

[krita] [Bug 357166] New: two finger zoom gesture stopped functioning, making convenient zooming impossible

[Christian via KDE Bugzilla]

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

Bug ID: 357166
   Summary: two finger zoom gesture stopped functioning, making
convenient zooming impossible
   Product: krita
   Version: 2.9.10
  Platform: MS Windows
   URL: https://bugs.kde.org/show_bug.cgi?id=356959
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: usability
  Assignee: krita-bugs-n...@kde.org
  Reporter: christianbcla...@gmail.com

The two finger zoom capability was working until a day ago. I have attempted
restarts and have uninstalled and reinstalled Krita 2.9.10.
The touch screen is still functionable for tools and the two finger function
can pan the canvas sideways, up and down.

Reproducible: Always

Steps to Reproduce:
1.Open Canvas.
2.Try to zoom with gesture
3.

Actual Results:  
Does not zoom in or out of canvas

Expected Results:  
Zoom in and out of canvas to allow for finite movement

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

[buildsystem] [Bug 357162] New: Hardcoded reference to inexistent URL

[Andreas Koenig via KDE Bugzilla]

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

Bug ID: 357162
   Summary: Hardcoded reference to inexistent URL
   Product: buildsystem
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: KDE4 (cmake)
  Assignee: neund...@kde.org
  Reporter: andreas.koenig.7os6v...@franz.ak.mind.de

Not sure whether the website or the module needs fixing, they are not in sync.
The module displays after a "repository" error a URL but that URL gives a 404.

% git remote -v|grep fetch
origin  git://anongit.kde.org/kdesrc-build (fetch)
% git describe
v15.12-3-gbbb1a6d
% git grep kdesrc-build.kde.org/documentation/kde-modules-and-selection.html
|cat
modules/ksb/Application.pm:http://kdesrc-build.kde.org/documentation/kde-modules-and-selection.html#module-sets
% HEAD kdesrc-build.kde.org/documentation/kde-modules-and-selection.html|head
-2
404 Not Found
Connection: close



Reproducible: Always

Steps to Reproduce:
1. goto the referenced webpage
2.
3.

Actual Results:  
404

Expected Results:  
a web page

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

[Spectacle] [Bug 357120] Remember rectangular region when retaking screenshot

[Albert via KDE Bugzilla]

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

Albert  changed:

   What|Removed |Added

 CC||kdebug-specta...@yahoo.com

--- Comment #1 from Albert  ---
I second this request.  I'm back on ksnapshot for this specific feature.  On
the announcement for spectacle replacing ksnapshot it was very specific, " In
addition to what you could do with KSnapshot..." so I was disappointed to find
this feature, and the save as feature both missing.
https://bugs.kde.org/show_bug.cgi?id=354046

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

[plasmashell] [Bug 356470] Plasmashell 5.5 segfaults on shutdown (like 5.3)

[Sudhir Khanger via KDE Bugzilla]

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

Sudhir Khanger  changed:

   What|Removed |Added

 CC||sud...@sudhirkhanger.com

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