[kdenlive] [Bug 356498] Several workflow and design improvement suggestions for timeline widget (video example included)

[Jesse via KDE Bugzilla]

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

--- Comment #2 from Jesse  ---
@wegerf, the vertical scrollbar makes perfect sense: scrolling down goes down,
scrolling up goes up. However, scrolling up in the Project Monitor window,
timecode field below the monitor, in the time numbers and zone field above the
timeline tracks all move the timeline forward; scrolling down moves them
backwards. Do you think that the horizontal scrollbar should do the opposite.
To me, it seems really incongruent with the rest of mouse scrolling operations
within the timeline  widget.

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

[umbrello] [Bug 358653] New: Umbrello crashed on close

[Ken Standard via KDE Bugzilla]

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

Bug ID: 358653
   Summary: Umbrello crashed on close
   Product: umbrello
   Version: 2.14.2 (KDE Applications 4.14.2)
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: umbrello-de...@kde.org
  Reporter: ad...@arrl.net

Application: umbrello (2.14.2)
KDE Platform Version: 4.14.2
Qt Version: 4.8.6
Operating System: Linux 4.2.0-18-generic i686
Distribution: Linux Mint 17.3 Rosa

-- Information about the crash:
Diagram save and clicked on close to leave the app.

-- Backtrace:
Application: Umbrello UML Modeller (umbrello), signal: Segmentation fault
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0xb4fc8b00 (LWP 12070))]

Thread 3 (Thread 0xad985b40 (LWP 12080)):
#0  0xb77d8cb0 in ?? ()
#1  0x0021 in ?? ()
#2  0x000b in ?? ()
#3  0x0021 in ?? ()
#4  0x in ?? ()

Thread 2 (Thread 0xacf2db40 (LWP 12081)):
#0  0xb77d8cb0 in ?? ()
#1  0xb5f6582b in ?? () from /usr/lib/i386-linux-gnu/libQtCore.so.4
#2  0xb5f658bd in ?? () from /usr/lib/i386-linux-gnu/libQtCore.so.4
#3  0xb532f9b3 in g_main_context_prepare () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#4  0xb53302df in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#5  0xb5330528 in g_main_context_iteration () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#6  0xb5f6595f in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/i386-linux-gnu/libQtCore.so.4
#7  0xb5f34823 in
QEventLoop::processEvents(QFlags) () from
/usr/lib/i386-linux-gnu/libQtCore.so.4
#8  0xb5f34b49 in QEventLoop::exec(QFlags) ()
from /usr/lib/i386-linux-gnu/libQtCore.so.4
#9  0xb5e2123d in QThread::exec() () from
/usr/lib/i386-linux-gnu/libQtCore.so.4
#10 0xb5f14c44 in ?? () from /usr/lib/i386-linux-gnu/libQtCore.so.4
#11 0xb5e23b6f in ?? () from /usr/lib/i386-linux-gnu/libQtCore.so.4
#12 0xb5456f70 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#13 0xb5bcbbee in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 1 (Thread 0xb4fc8b00 (LWP 12070)):
#0  0xb77d8cb0 in ?? ()
#1  0x in ?? ()

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

[umbrello] [Bug 358655] New: Umbrello does not import private class

[Ken Standard via KDE Bugzilla]

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

Bug ID: 358655
   Summary: Umbrello does not import private class
   Product: umbrello
   Version: 2.14.2 (KDE Applications 4.14.2)
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: umbrello-de...@kde.org
  Reporter: ad...@arrl.net

In a Qt 5.5.1 project, a private class is defined. It is referenced as a data
type for a private variable pointer:

myheader.hpp

private:
class MyPrivateClass;
MyPrivateClass *d_data;

myimplementation.cpp

class MyImplementation::MyPrivateClass
{
. . .
}

only the *d_data variable from the header is imported and not the private class
from the .cpp file.

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

[dolphin] [Bug 358657] New: Dolphin crash when in split pane mode

[wintonian via KDE Bugzilla]

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

Bug ID: 358657
   Summary: Dolphin crash when in split pane mode
   Product: dolphin
   Version: 15.12.1
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: bugzi...@wintonian.org.uk

Application: dolphin (15.12.1)

Qt Version: 5.5.1
Operating System: Linux 4.3.4-300.fc23.x86_64 x86_64
Distribution: "Fedora release 23 (Twenty Three)"

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

I clicked on "split" in the menu bar and then changed the directory of one of
the panes, using the "places" list.

-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f56f6c76940 (LWP 8135))]

Thread 4 (Thread 0x7f56d429a700 (LWP 8136)):
#0  0x7f56ee501fdd in poll () from /lib64/libc.so.6
#1  0x7f56e9ed5272 in _xcb_conn_wait () from /lib64/libxcb.so.1
#2  0x7f56e9ed6ee7 in xcb_wait_for_event () from /lib64/libxcb.so.1
#3  0x7f56d6dfbda9 in QXcbEventReader::run() () from
/lib64/libQt5XcbQpa.so.5
#4  0x7f56ef11e3de in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#5  0x7f56eb47a60a in start_thread () from /lib64/libpthread.so.0
#6  0x7f56ee50da4d in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7f56d129a700 (LWP 8152)):
#0  0x7f56ee4fdbcd in read () from /lib64/libc.so.6
#1  0x7f56e2c24f45 in ?? () from
/usr/lib64/nvidia-340xx/tls/libnvidia-tls.so.340.96
#2  0x7f56e9358390 in g_wakeup_acknowledge () from /lib64/libglib-2.0.so.0
#3  0x7f56e9314c64 in g_main_context_check () from /lib64/libglib-2.0.so.0
#4  0x7f56e9315110 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#5  0x7f56e931527c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#6  0x7f56ef355ecb in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#7  0x7f56ef2fceca in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#8  0x7f56ef119434 in QThread::exec() () from /lib64/libQt5Core.so.5
#9  0x7f56ef11e3de in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#10 0x7f56eb47a60a in start_thread () from /lib64/libpthread.so.0
#11 0x7f56ee50da4d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f56cb42a700 (LWP 8561)):
#0  0x7f56eb47feb9 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f56ef11f5a6 in QWaitCondition::wait(QMutex*, unsigned long) () from
/lib64/libQt5Core.so.5
#2  0x7f56ef11b063 in QThreadPoolThread::run() () from
/lib64/libQt5Core.so.5
#3  0x7f56ef11e3de in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#4  0x7f56eb47a60a in start_thread () from /lib64/libpthread.so.0
#5  0x7f56ee50da4d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f56f6c76940 (LWP 8135)):
[KCrash Handler]
#5  0x7f56ed69 in mdb_get () from /lib64/liblmdb.so.0.0.0
#6  0x7f56ed842c68 in Baloo::DocumentDataDB::get(unsigned long long) ()
from /lib64/libKF5BalooEngine.so.5
#7  0x7f56ed85ac2e in Baloo::Transaction::documentData(unsigned long long)
const () from /lib64/libKF5BalooEngine.so.5
#8  0x7f56f57346a9 in Baloo::File::load() () from /lib64/libKF5Baloo.so.5
#9  0x7f56f597c24e in Baloo::FileFetchJob::doStart() () from
/lib64/libKF5BalooWidgets.so.5
#10 0x7f56ef32f161 in QObject::event(QEvent*) () from
/lib64/libQt5Core.so.5
#11 0x7f56f06bf41c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib64/libQt5Widgets.so.5
#12 0x7f56f06c48e6 in QApplication::notify(QObject*, QEvent*) () from
/lib64/libQt5Widgets.so.5
#13 0x7f56ef2ff73b in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#14 0x7f56ef301b36 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /lib64/libQt5Core.so.5
#15 0x7f56ef355aa3 in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () from /lib64/libQt5Core.so.5
#16 0x7f56e9314e3a in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#17 0x7f56e93151d0 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#18 0x7f56e931527c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#19 0x7f56ef355eaf in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#20 0x7f56ef2fceca in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#21 0x7f56ef304fac in QCoreApplication::exec() () from
/lib64/libQt5Core.so.5
#22 0x7f56f68e2ef4 in kdemain () from /lib64/libkdeinit5_dolphin.so
#23 0x7f56ee42b580 in __libc_start_main () from /lib64/libc.so.6
#24 0x5643b03e0be9 in _start ()

Reported using DrKonqi

-- 
You are receiving 

[muon] [Bug 358659] New: Muon package manager does not close

[Lastique via KDE Bugzilla]

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

Bug ID: 358659
   Summary: Muon package manager does not close
   Product: muon
   Version: 5.4.3
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: muon
  Assignee: echidna...@kubuntu.org
  Reporter: andy...@mail.ru
CC: aleix...@kde.org, sit...@kde.org

The main package manager window does not close. Neither Alt+F4 nor the X button
in the window decoration close the application - it seem to simply ignore these
events. It does close if I select File->Quit. It also closes if I send SIGINT
to the process. No other applications on the machine exhibit this problem.

Reproducible: Always

Steps to Reproduce:
1. Start Muon package manager.
2. Try to close it by pressing Alt+F4 or the close window button in the window
decoration.


Actual Results:  
The application doesn't close.

Expected Results:  
The application should close.

The problem started to happen after a recent update. KDE is installed from
kubuntu-backports.

Kubuntu 15.10, x86_64.

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

[frameworks-knotifications] [Bug 356523] Hide/restore window from system tray cause change it position

[Thomas Lübking via KDE Bugzilla]

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

--- Comment #20 from Thomas Lübking  ---
Either the window was undecorated or the call to the wininfo was made before it
was decorated by the WM (in either case frameGeometry() and geometry() are
equal)

Why there's this complex code, also preserving the current desktop, is frankly
beyond me - QWidget::hide() withdraws the X drawable, but doesn't destroy it -
so properties like the VD and the geometry should be preserved; QWidget::hide()
/ QWidget::show() should™ really just work.

The only thing I could imagine is that the client code in addition nukes the
widget (destroying the drawable) and adds a new associate (w/o caring about
former properties) - however then also the X properties (KWinInfo geometry)
should be nonsense...

My uninformed suggestion was to explicitly store the position QWidget::pos()
like the virtual desktop and restore to that QPoint *shrug*

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

[plasmashell] [Bug 358624] Plasma Panel stays on disconnected Primary Output

[Malte S . Stretz via KDE Bugzilla]

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

--- Comment #3 from Malte S. Stretz  ---
Funnily, it looks like it magically fixed itself yesterday just when I pressed
the Submit button for this bug: Suddenly the panel appeared on my laptop
screen. Today I was at the office (where my extra screen is) and now I'm back
home again and the panel behaves exactly like it should.

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

[kdesvn] [Bug 358626] KDESVN crashes when trying to checkout a repo

[george via KDE Bugzilla]

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

--- Comment #2 from george  ---
(In reply to Christian Ehrlicher from comment #1)
> What url did you use? svn:// or http:// ?

file:///

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

[Akonadi] [Bug 358658] .desktop files of agents are read in the incorrect encoding

[Alexey Chernov via KDE Bugzilla]

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

--- Comment #1 from Alexey Chernov <4er...@gmail.com> ---
Created attachment 96876
  --> https://bugs.kde.org/attachment.cgi?id=96876=edit
Sample screenshot of the issue.

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

[plasmashell] [Bug 358654] New: Seeing Plasma crash messages when unlocking desktop

[via KDE Bugzilla]

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

Bug ID: 358654
   Summary: Seeing Plasma crash messages when unlocking desktop
   Product: plasmashell
   Version: 5.5.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: laff...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.3)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-1-default x86_64
Distribution: "openSUSE Tumbleweed (20160121) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
I unlocked the desktop (by entering login credentials) and got 2 messages that
Plasma had crashed. I can not say for sure that unlocking process ITSELF caused
the crash (perhaps it is caused by some background process that starts when the
desktop is locked), but every time I see these 2 crash messages, it is after I
unlock the desktop.

The crash can be reproduced sometimes.

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

Thread 12 (Thread 0x7efd6ee71700 (LWP 15042)):
#0  0x7efd7ee8424d in poll () from /lib64/libc.so.6
#1  0x7efd83d5a432 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7efd83d5c007 in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7efd70fc0e29 in ?? () from /usr/lib64/libQt5XcbQpa.so.5
#4  0x7efd7f57594f in QThreadPrivate::start (arg=0x224aa20) at
thread/qthread_unix.cpp:331
#5  0x7efd7e68b4a4 in start_thread () from /lib64/libpthread.so.0
#6  0x7efd7ee8cbdd in clone () from /lib64/libc.so.6

Thread 11 (Thread 0x7efd67fff700 (LWP 15043)):
#0  0x7efd7ee84239 in poll () from /lib64/libc.so.6
#1  0x7efd7b578264 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7efd7b57836c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7efd7f79a52b in QEventDispatcherGlib::processEvents
(this=0x7efd68c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7efd7f74463a in QEventLoop::exec (this=this@entry=0x7efd67ffecf0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7efd7f570b1c in QThread::exec (this=this@entry=0x231c710) at
thread/qthread.cpp:503
#6  0x7efd828409a5 in QQmlThreadPrivate::run (this=0x231c710) at
/usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/qml/ftw/qqmlthread.cpp:141
#7  0x7efd7f57594f in QThreadPrivate::start (arg=0x231c710) at
thread/qthread_unix.cpp:331
#8  0x7efd7e68b4a4 in start_thread () from /lib64/libpthread.so.0
#9  0x7efd7ee8cbdd in clone () from /lib64/libc.so.6

Thread 10 (Thread 0x7efd54f84700 (LWP 15050)):
#0  0x7efd7b577cd9 in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#1  0x7efd7b578208 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7efd7b57836c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7efd7f79a52b in QEventDispatcherGlib::processEvents
(this=0x7efd58c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7efd7f74463a in QEventLoop::exec (this=this@entry=0x7efd54f83cf0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7efd7f570b1c in QThread::exec (this=this@entry=0x254e8d0) at
thread/qthread.cpp:503
#6  0x7efd828409a5 in QQmlThreadPrivate::run (this=0x254e8d0) at
/usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/qml/ftw/qqmlthread.cpp:141
#7  0x7efd7f57594f in QThreadPrivate::start (arg=0x254e8d0) at
thread/qthread_unix.cpp:331
#8  0x7efd7e68b4a4 in start_thread () from /lib64/libpthread.so.0
#9  0x7efd7ee8cbdd in clone () from /lib64/libc.so.6

Thread 9 (Thread 0x7efd4f5c9700 (LWP 15051)):
#0  0x7efd7b5bb4b9 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0
#1  0x7efd7b577a91 in g_main_context_query () from
/usr/lib64/libglib-2.0.so.0
#2  0x7efd7b5781df in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x7efd7b57836c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#4  0x7efd7f79a52b in QEventDispatcherGlib::processEvents
(this=0x7efd480008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7efd7f74463a in QEventLoop::exec (this=this@entry=0x7efd4f5c8cf0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7efd7f570b1c in QThread::exec (this=this@entry=0x2683420) at
thread/qthread.cpp:503
#7  0x7efd828409a5 in QQmlThreadPrivate::run (this=0x2683420) at
/usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/qml/ftw/qqmlthread.cpp:141
#8  0x7efd7f57594f in QThreadPrivate::start (arg=0x2683420) at
thread/qthread_unix.cpp:331
#9  0x7efd7e68b4a4 in start_thread () from /lib64/libpthread.so.0
#10 0x7efd7ee8cbdd in clone () from /lib64/libc.so.6

Thread 8 (Thread 

[plasmashell] [Bug 358624] Plasma Panel stays on disconnected Primary Output

[Thomas Abraham via KDE Bugzilla]

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

--- Comment #4 from Thomas Abraham  ---
I'm sure: this issue will return as long the bug is not resolved. There are a
couple of open issues relating to this one

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

[Akonadi] [Bug 358658] .desktop files of agents are read in the incorrect encoding

[Alexey Chernov via KDE Bugzilla]

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

--- Comment #2 from Alexey Chernov <4er...@gmail.com> ---
Here's a review request link: https://git.reviewboard.kde.org/r/126911/

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

[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

[via KDE Bugzilla]

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

--- Comment #11 from cher...@aip.de ---
Thank you very much for the workaround.

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

[konsole] [Bug 357922] the remember position & size values are not honored in konsole

[boris64 via KDE Bugzilla]

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

boris64  changed:

   What|Removed |Added

 CC||bugs@boris64.net

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

[korganizer] [Bug 356463] Importing a calendar item pops up confusing/unclear UI

[via KDE Bugzilla]

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

i...@mhlavac.net changed:

   What|Removed |Added

 CC||i...@mhlavac.net

--- Comment #1 from i...@mhlavac.net ---
Created attachment 96874
  --> https://bugs.kde.org/attachment.cgi?id=96874=edit
Message with wrong actions

I was adding event in ics file to my calendar via korganizer and was met with
this message. Buttons didn't make any sense in context of the message itself.

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

[kdev-python] [Bug 358563] Possible infinite loop in UnsureType::toString()

[Sven Brauch via KDE Bugzilla]

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

Sven Brauch  changed:

   What|Removed |Added

   Severity|normal  |crash

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

[kdev-python] [Bug 358563] Possible infinite loop in UnsureType::toString()

[Sven Brauch via KDE Bugzilla]

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

--- Comment #3 from Sven Brauch  ---
Hmm. Can you post the backtrace? Also do you have example code which you edit
to trigger this bug?

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

[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

[Thomas Abraham via KDE Bugzilla]

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

Thomas Abraham  changed:

   What|Removed |Added

 CC||k...@thomas-abraham.com

--- Comment #10 from Thomas Abraham  ---
Found this workaround for my own to make a "hidden" panel visible again:

In $HOME/.config/plasma-org.kde.plasma.desktop-appletsrc there's a section
"[Containments][1]". There within the option  "lastScreen" often refers to the
wrong screen, i.e. "1" instead of "0".

When I change that option to "lastScreen=0"
before starting the KDE session the panel is visible again on my laptop screen
if it is the one and only available screen.

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

[plasmashell] [Bug 355466] Multihead: Panels from one monitor disappear and cannot be recovered if that monitor is disconnected

[Thomas Abraham via KDE Bugzilla]

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

Thomas Abraham  changed:

   What|Removed |Added

 CC||k...@thomas-abraham.com

--- Comment #3 from Thomas Abraham  ---
For the "less destructive" workaround, please, see #356225, comment 10.
plasma-org.kde.plasma.desktop-appletsrc:
-lastScreen=1
+lastScreen=0

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

[valgrind] [Bug 356457] valgrind: m_mallocfree.c:2042 (vgPlain_arena_free): Assertion 'blockSane(a, b)' failed.

[Philippe Waroquiers via KDE Bugzilla]

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

--- Comment #15 from Philippe Waroquiers  ---
(In reply to Joost VandeVondele from comment #14)
> Also no luck with --sanity-level=4 
> 
> The fact that it is not reproducible on command is indeed not simplifying
> this. I wonder if this could be related to something external to valgrind
> triggering this.
Yes, this bug is quite mysterious.

The only remaining thing to try that I see is to add 
   --vgdb-stop-at=valgrindabexit
to the valgrind args you use for your regression tests.
Then when the error happens, valgrind will wait for a gdb to connect using
gdb+vgdb.
You can then examine e.g. which library is being mmap-ed.
You might also use gdb to directly attach to valgrind and examine valgrind
internals.

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

[ksysguard] [Bug 358660] New: KSystemGuard crashed on closing

[Lastique via KDE Bugzilla]

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

Bug ID: 358660
   Summary: KSystemGuard crashed on closing
   Product: ksysguard
   Version: 5.5.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: ksysguard-b...@kde.org
  Reporter: andy...@mail.ru

Application: ksysguard (5.5.3)

Qt Version: 5.5.1
Operating System: Linux 4.2.0-25-generic x86_64
Distribution: Ubuntu 15.10

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

KSystemGuard application crashed when I closed it. The crash doesn't happen
every time, though.

-- Backtrace:
Application: System Monitor (ksysguard), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6  operator== (s1=..., s2=...) at tools/qstring.cpp:2553
#7  0x7fd766c0cbd7 in QLabel::setText (this=0x754550, text=...) at
widgets/qlabel.cpp:276
#8  0x7fd76a410239 in TopLevel::answerReceived (this=0x744020,
id=, answerList=...) at ../../gui/ksysguard.cpp:447
#9  0x7fd7696a8d11 in KSGRD::SensorAgent::processAnswer(char const*, int)
() from /usr/lib/x86_64-linux-gnu/libksgrd.so.7
#10 0x7fd7696b0620 in ?? () from /usr/lib/x86_64-linux-gnu/libksgrd.so.7
#11 0x7fd766200777 in QtPrivate::QSlotObjectBase::call (a=0x7fff4c3349e0,
r=0x841390, this=) at
../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124
#12 QMetaObject::activate (sender=sender@entry=0x83bc60,
signalOffset=, local_signal_index=local_signal_index@entry=5,
argv=argv@entry=0x0) at kernel/qobject.cpp:3698
#13 0x7fd7662010e7 in QMetaObject::activate (sender=sender@entry=0x83bc60,
m=m@entry=0x7fd766417360 ,
local_signal_index=local_signal_index@entry=5, argv=argv@entry=0x0) at
kernel/qobject.cpp:3578
#14 0x7fd7660ff1b3 in QProcess::readyReadStandardOutput
(this=this@entry=0x83bc60) at .moc/moc_qprocess.cpp:266
#15 0x7fd766107822 in QProcessPrivate::tryReadFromChannel (this=0x85f9f0,
channel=0x85fb20) at io/qprocess.cpp:966
#16 0x7fd766107ca0 in QProcessPrivate::_q_canReadStandardOutput
(this=) at io/qprocess.cpp:977
#17 QProcess::qt_static_metacall (_o=, _c=,
_id=, _a=0x7fff4c334be0) at .moc/moc_qprocess.cpp:133
#18 0x7fd7662008ea in QMetaObject::activate (sender=sender@entry=0x7e3eb0,
signalOffset=, local_signal_index=local_signal_index@entry=0,
argv=argv@entry=0x7fff4c334be0) at kernel/qobject.cpp:3713
#19 0x7fd7662010e7 in QMetaObject::activate (sender=sender@entry=0x7e3eb0,
m=m@entry=0x7fd76641b6e0 ,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fff4c334be0)
at kernel/qobject.cpp:3578
#20 0x7fd7662801fe in QSocketNotifier::activated (this=this@entry=0x7e3eb0,
_t1=12) at .moc/moc_qsocketnotifier.cpp:134
#21 0x7fd76620cd9b in QSocketNotifier::event (this=0x7e3eb0, e=) at kernel/qsocketnotifier.cpp:260
#22 0x7fd766ac69dc in QApplicationPrivate::notify_helper
(this=this@entry=0x6639e0, receiver=receiver@entry=0x7e3eb0,
e=e@entry=0x7fff4c334e50) at kernel/qapplication.cpp:3716
#23 0x7fd766acbea6 in QApplication::notify (this=0x7fff4c335170,
receiver=0x7e3eb0, e=0x7fff4c334e50) at kernel/qapplication.cpp:3499
#24 0x7fd7661d1d7b in QCoreApplication::notifyInternal
(this=0x7fff4c335170, receiver=0x7e3eb0, event=event@entry=0x7fff4c334e50) at
kernel/qcoreapplication.cpp:965
#25 0x7fd7662289bd in QCoreApplication::sendEvent (event=0x7fff4c334e50,
receiver=) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:224
#26 socketNotifierSourceDispatch (source=0x698d90) at
kernel/qeventdispatcher_glib.cpp:101
#27 0x7fd75ed14ff7 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#28 0x7fd75ed15250 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#29 0x7fd75ed152fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#30 0x7fd7662284ef in QEventDispatcherGlib::processEvents (this=0x698ee0,
flags=...) at kernel/qeventdispatcher_glib.cpp:418
#31 0x7fd7661cf50a in QEventLoop::exec (this=this@entry=0x7fff4c335060,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#32 0x7fd7661d75ec in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:1229
#33 0x7fd76650bd1c in QGuiApplication::exec () at
kernel/qguiapplication.cpp:1530
#34 0x7fd766ac2e15 in QApplication::exec () at kernel/qapplication.cpp:2976
#35 0x7fd76a411b5d in kdemain (argc=1, argv=) at
../../gui/ksysguard.cpp:594
#36 0x7fd769ff0a40 in __libc_start_main (main=0x400730 ,
argc=1, argv=0x7fff4c3352b8, init=, fini=,
rtld_fini=, stack_end=0x7fff4c3352a8) at libc-start.c:289
#37 0x00400769 in _start ()

Possible duplicates by query: bug 348751, bug 347662.

Reported using DrKonqi

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

[kdenlive] [Bug 358661] Merge Title Bars and Tabs? (design mock-ups included)

[Jesse via KDE Bugzilla]

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

--- Comment #1 from Jesse  ---
Created attachment 96877
  --> https://bugs.kde.org/attachment.cgi?id=96877=edit
Kdenlive current title bars and tabbed layout

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

[kdenlive] [Bug 358661] Merge Title Bars and Tabs? (design mock-ups included)

[Jesse via KDE Bugzilla]

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

--- Comment #2 from Jesse  ---
Created attachment 96878
  --> https://bugs.kde.org/attachment.cgi?id=96878=edit
Proposed improved "Title Tabs" (or whatever you want to call them)

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

[kdenlive] [Bug 358661] Merge Title Bars and Tabs? (design mock-ups included)

[Jesse via KDE Bugzilla]

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

Jesse  changed:

   What|Removed |Added

 CC||jesse.dub...@gmail.com

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

[kdenlive] [Bug 358661] New: Merge Title Bars and Tabs? (design mock-ups included)

[Jesse via KDE Bugzilla]

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

Bug ID: 358661
   Summary: Merge Title Bars and Tabs? (design mock-ups included)
   Product: kdenlive
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: Effects & Transitions
  Assignee: vpi...@kde.org
  Reporter: jesse.dub...@gmail.com

See attached images that will be included in this report. Consider merging the
Title Bars and Tabs? Benefits would be:

(1) Reduces redundancy when Title Bars are showing (currently the widget name
appears in the title bar and the widget tab. Combining these would condense it
into one, possibly confusing the user as to why there are two instances of the
name)
(2) Frees up screen real estate
(3) The "Show Title Bar" option in the View menu could be changed to "Show Tab
Details", which, when enabled, would simply add the Close and Diamond-looking
icon to the tab, placed to the right of the Title text.
(4) Generate more new user interest. Many of the video editors familiar with
Adobe Premiere, which is the 2nd most popular Industry editor, would find this
much more familiar. I also think this layout would be less ambiguous and more
comfortable for users.

Reproducible: Always

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

[Spectacle] [Bug 358652] New: Global shortcuts suggestions/wishes

[Gregor Mi via KDE Bugzilla]

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

Bug ID: 358652
   Summary: Global shortcuts suggestions/wishes
   Product: Spectacle
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: General
  Assignee: m...@baloneygeek.com
  Reporter: codestr...@posteo.org

In Global Keyboard Shortcuts -> KDE Daemon I identified three
screenshot-related shortcuts:

1) "Start Screenshot Tool" -> Starts spectacle with fullscreen shot already
being taken
2) "Take Active Window Screenshot" -> Takes active window screenshot and saves
the file to standard location
3) "Take Full Screen Screenshot" -> same as 2) but with a fullscreen screenshot

Wishes for improved workflow:
a) It would be nice to have a key that takes the active window screenshot but
also opens spectacle; e.g. to be able to use the export functions
b) It would be nice to have another keyboard shortcut that lets the user
immediately select a rectangular region and then show it in the spectacle
window for further processing.

Also nice would be if the above-mentioned shortcuts could be directly
configured in spectacle.

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

[kdepimlibs] [Bug 353326] Korganizer crashed when trying to add a new event.

[eric via KDE Bugzilla]

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

eric  changed:

   What|Removed |Added

 CC||pro...@gmx.net

--- Comment #4 from eric  ---
This still happens with korganizer and kaddresssbook, both version 15.12.1.
KDE-5.18
Qt-5.5.1

After importing new *.vcf files:
Korganizer crashes when trying to add a new event or after I click on the
'To-Do List' view; 
Kaddressbook crashes immediately after startup.

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

[kde] [Bug 358123] I can at the KDE screensaver or not adjust this setting does not exist.

[Olan via KDE Bugzilla]

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

--- Comment #1 from Olan  ---
Created attachment 96873
  --> https://bugs.kde.org/attachment.cgi?id=96873=edit
Kein Bildschirmschoner zu sehen ///  See No screensavers

I have now found the place where the screen saver was to come. At this point,
however, is nothing! Missing a package?
--
Ich habe jetzt die Stelle gefunden wo der Bildschirmschoner kommen sollte. An
dieser Stelle kommt aber nichts! Fehlt ein Paket?

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

[kleopatra] [Bug 340227] Unable to trust self-signed root certificate

[Briet via KDE Bugzilla]

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

Briet  changed:

   What|Removed |Added

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

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

[krunner] [Bug 353879] Crashes soon after KDE starts

[tom via KDE Bugzilla]

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

tom  changed:

   What|Removed |Added

 CC||tom...@gmail.com

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

[plasmashell] [Bug 358654] Seeing Plasma crash messages when unlocking desktop

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

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

--- Comment #1 from David Edmundson  ---
#10 0x7efd6492beaf in nouveau_pushbuf_data (push=push@entry=0x249d690,
bo=0x24cf7f0, offset=524240, length=96) at pushbuf.c:727

Crash is in your graphic driver. Please can you report the bug there.

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

[Akonadi] [Bug 358658] New: .desktop files of agents are read in the incorrect encoding

[Alexey Chernov via KDE Bugzilla]

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

Bug ID: 358658
   Summary: .desktop files of agents are read in the incorrect
encoding
   Product: Akonadi
   Version: GIT (master)
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: server
  Assignee: kdepim-b...@kde.org
  Reporter: 4er...@gmail.com

It turned out that .desktop files which hold settings of Akonadi agents are
read in the incorrect encoding which leads to broken strings in applications
(e.g. KMail or Akonadiconsole) when using localized version of KDE (see the
screenshots).

There's a fix for that, so the review request link is about to be applied.

Reproducible: Always

Steps to Reproduce:
1. Set some non-English locale in System settings.
2. Start e.g. Akonadiconsole.
3. Notice type string of agent summary.
4. Click "Add" button and notice descriptions of agents are with broken
symbols.

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

[kdenlive] [Bug 358661] Merge Title Bars and Tabs? (design mock-ups included)

[Jesse via KDE Bugzilla]

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

Jesse  changed:

   What|Removed |Added

  Component|Effects & Transitions   |User Interface

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

[plasmashell] [Bug 358102] New method to re-size and move widgets is not intuitive, as is discovering the configuration option.

[Clay Weber via KDE Bugzilla]

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

--- Comment #3 from Clay Weber  ---
(In reply to Martin Klapetek from comment #1)
> Thanks for the report
> 
> All applets should have the handle pop up on left-mouse button long-press.
> 
> Can you verify that is not the case?

Yes, long press with left mouse does work, but it may not be obvious to do so.
Updating to Plasma 5.5.4 seems to help here, as click-and-drag works easier,
much more like doing so from  within Dolphin. I can move most widgets by this,
without the log press. The handle does not pop up, though (As it is not
necessary in this case, I imagine).

However, the round analog clock  has no flat edge to grab, and unless you know
that you have to long-press, it is not obvious how to reposition it.

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

[kwin] [Bug 358664] New: On display configuration change some maximised windows are lost

[Mal Haak via KDE Bugzilla]

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

Bug ID: 358664
   Summary: On display configuration change some maximised windows
are lost
   Product: kwin
   Version: 5.5.1
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: insane...@gmail.com

I'm working on a lenovo laptop on a docking station.
When I have maximised windows that aren't Chrome or VirtualBox (Usually
Konsole, but also Kate) and I dock or undock causing my external monitor to be
attached/removed (thus changing my display setup) maximised windows get 'lost'

I can't see them on the task bar. I can see them as still running in top/ ps
aux . I can see them in the list via 'xwininfo -tree -root' however wmctrl -l
doesn't have them.

Reproducible: Always

Steps to Reproduce:
1.Maximise window
2.Dock/Undock laptop (or attach/detach monitor)
3.

Actual Results:  
Maximised windows are lost

Expected Results:  
Maximised windows are not lost

xwininfo -tree -root |grep konsole
grep: warning: GREP_OPTIONS is deprecated; please use an alias or script
 0x1a00096 "Konsole": ("konsole" "konsole")  356x199+330+60  +330+60
 0x1a00089 "() Somework — Konsole": ("konsole" "konsole")  1600x840+0+32 
+0+32
 0x1a00071 "performance : vim — Konsole": ("konsole" "konsole") 
1200x1888+1600+32  +1600+32
 0x1a00042 "Konsole": ("konsole" "konsole")  401x37+268+607  +268+607
 0x1a00031 "performance : zsh — Konsole": ("konsole" "konsole") 
1600x840+0+32  +0+32
   0x1a00090 "malcolm : zsh — Konsole": ("konsole" "konsole") 
1200x1888+0+0  +1600+32

~ ❯❯❯ wmctrl -l
0x0300040a -1 N/A Desktop — Plasma
0x030e -1 N/A Desktop — Plasma
0x01ec  0 mal-laptop.site Oracle VM VirtualBox Manager
0x0584  0 N/A Desktop — Dolphin
0x0501  0 mal-laptop.site Random web page - Google Chrome
0x03cc  0 mal-laptop.site Win7-1 [Running] - Oracle VM VirtualBox
0x050001bf  0 mal-laptop.site zabbix: Latest data [refreshed every 30 sec.] -
Google Chrome
0x03400019  0 N/A N/A
0x053e  0 mal-laptop.site Some other random webpage - Google Chrome
0x0540  0 mal-laptop.site Something else not important - Google Chrome
0x053f  0 mal-laptop.site 31.2. importlib – Convenience wrappers for
__import__() — Python 2.7.11 documentation - Google Chrome
0x0763  0 mal-laptop.site projectM
0x06a000c8  0 mal-laptop.site Rammstein - Ein Lied  ::  Amarok
0x0323 -1 N/A Plasma
0x050001d5 -1 mal-laptop.site Chat window A
0x050001d4 -1 mal-laptop.site Chat window B
0x01a00090  0 N/A malcolm : zsh — Konsole
0x01e00103  0 mal-laptop.site VirtualBox - Information

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

[akregator] [Bug 358663] New Feature: Enable interface to Owncloud News

[Daniel Lausevic via KDE Bugzilla]

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

--- Comment #2 from Daniel Lausevic  ---
Didn't see an existing request even after a cursory search. Sorry. Closing this
as it is a dupe.

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

[akregator] [Bug 358663] New Feature: Enable interface to Owncloud News

[Daniel Lausevic via KDE Bugzilla]

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

--- Comment #3 from Daniel Lausevic  ---
Didn't see an existing request even after a cursory search. Sorry. Closing this
as it is a dupe.

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

[akregator] [Bug 358663] New Feature: Enable interface to Owncloud News

[Daniel Lausevic via KDE Bugzilla]

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

--- Comment #4 from Daniel Lausevic  ---
.

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

[Baloo] [Bug 356298] Baloo crash - Baloo::File::load - mdb_dbi_open

[Riskable via KDE Bugzilla]

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

--- Comment #3 from Riskable  ---
I just want to add that I'm also experiencing this exact crash.  Happens quite
a lot, actually.  Quite annoying.  My stacktrace was almost identical so
there's no point in posting it.

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

[akregator] [Bug 358663] New: New Feature: Enable interface to Owncloud News

[Daniel Lausevic via KDE Bugzilla]

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

Bug ID: 358663
   Summary: New Feature: Enable interface to Owncloud News
   Product: akregator
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: feed parser
  Assignee: kdepim-b...@kde.org
  Reporter: calcman...@gmail.com

Please add a function whereby an owncloud server can be added to Akregator such
that feeds subscribed from the server will appear in akregator. Downloading and
reading feeds should mark the feeds read on the server to enable a snyc with
smartphone apps.

For reference, Android has an app which serves this purpose called 'ownCloud
News Reader.' 

Wishlist: 

1. Add connectivity/sync to owncloud news
2. Disable hostname verification for those of us who operate with a self signed
cert.
3. Allow for subscribing to new feeds within Akregator.
4. Allow folder creation/removal within Akregator.
5. Allow 'starring'

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

[kexi] [Bug 358662] Default "Smallest readable font" not used by Kexi

[Jarosław Staniek via KDE Bugzilla]

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

Jarosław Staniek  changed:

   What|Removed |Added

 Status|RESOLVED|CLOSED

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

[plasmashell] [Bug 349482] After resume from suspend, non-primary display in multi-screen setup is black

[jamese via KDE Bugzilla]

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

jamese  changed:

   What|Removed |Added

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

--- Comment #7 from jamese  ---
After reading https://bugs.kde.org/show_bug.cgi?id=353975 this appears to be
the same thing.

Since updating to Plasma 5.5 from Kubuntu Backports, Plasma crashes have all
but disappeared but I still have funky multi-screen support, possibly related
to other bugs, in KDE... Generally ending with unusable desktops and me having
to kill sddm and rm .local/share/kscreen/*, then signing in again.

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

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

[akregator] [Bug 358663] New Feature: Enable interface to Owncloud News

[Daniel Lausevic via KDE Bugzilla]

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

--- Comment #1 from Daniel Lausevic  ---
Thanks in advance

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

[plasmashell] [Bug 353975] Black screen on second display.

[jamese via KDE Bugzilla]

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

jamese  changed:

   What|Removed |Added

 CC||james.el...@gmail.com

--- Comment #12 from jamese  ---
*** Bug 349482 has been marked as a duplicate of this bug. ***

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

[konsole] [Bug 356833] Ctrl+C doesn't work on Wayland

[via KDE Bugzilla]

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

bluescreen_aven...@verizon.net changed:

   What|Removed |Added

 CC||bluescreen_avenger@verizon.
   ||net

--- Comment #2 from bluescreen_aven...@verizon.net ---
It seems this was an upstream issue fixed by 5.6
https://quickgit.kde.org/?p=qt%2Fqtwayland.git=commit=b0d02b3cfd39f6a8815cc07848ca865257cd2c9f

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

[konsole] [Bug 336638] Frameworks konsole doesn't send CTRL key to the Terminal under Wayland

[via KDE Bugzilla]

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

--- Comment #4 from bluescreen_aven...@verizon.net ---
This is resolved if you use qtwayland 5.6 it seems there was a patch there in
5.6 that fixed this

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

[kexi] [Bug 358662] New: Default "Smallest readable font" not used by Kexi

[Jarosław Staniek via KDE Bugzilla]

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

Bug ID: 358662
   Summary: Default "Smallest readable font" not used by Kexi
   Product: kexi
   Version: 2.9.10
  Platform: Other
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: kexi-b...@kde.org
  Reporter: stan...@kde.org
CC: a...@piggz.co.uk, in...@fables.co.za

Where appropriate, default "Smallest readable font" not used by Kexi. Also,
PropertyEditor/FontSize means pixel size, while typically it should be point
size.

Reproducible: Always

Steps to Reproduce:
1. Change "Smallest readable font"  in Plasma's system settings
2. Run Kexi
3. Changes are not present


Expected Results:  
"Smallest readable font" should be used.

Font size based on resolution is a risky choice, should be removed.

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

[kexi] [Bug 358662] Default "Smallest readable font" not used by Kexi

[Jarosław Staniek via KDE Bugzilla]

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

Jarosław Staniek  changed:

   What|Removed |Added

   Assignee|kexi-b...@kde.org   |stan...@kde.org
 Ever confirmed|0   |1
   Severity|normal  |minor
   Target Milestone|--- |2.9.11
 Status|UNCONFIRMED |ASSIGNED

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

[plasmashell] [Bug 356720] Panel displayed on wrong monitor on login

[jamese via KDE Bugzilla]

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

jamese  changed:

   What|Removed |Added

 CC||james.el...@gmail.com

--- Comment #2 from jamese  ---
I get a similar thing, quite often if I have a panel on my laptop screen and
one on the external monitor,  the laptop panel will migrate to the external
screen and sit over the external monitor panel.
If I remove the extra panel and subsequently use my laptop without external
screens, the laptop display has no panel any more and I have to add a new
Default Panel.

External screen is connected via Displayport as well -  I don't know if KDE
doesn't like Displayport connections, include MST, but my setup has regular,
daily issues with multiscreen support especially when switching  between
external + laptop -> laptop only -> external + laptop  (i.e desktop -> mobile
-> desktop usage pattern).

Using Kubuntu 15.10 + Plasma 5.5 backports

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

[kleopatra] [Bug 358666] New: Short dates are used everywhere in the UI

[via KDE Bugzilla]

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

Bug ID: 358666
   Summary: Short dates are used everywhere in the UI
   Product: kleopatra
   Version: 2.2.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: aheine...@intevation.de
  Reporter: kokotokos...@yopmail.fr
CC: kdepim-b...@kde.org, m...@kde.org

The user interface uses the short date format (e.g., Thu 28 Jan), which is
fairly useless if one is trying to ascertain, e.g., how long a certificate has
been valid or when it will expire.

Reproducible: Always

Steps to Reproduce:
1. Ensure at least one certificate has been imported
2. Open the certificate manager
3. Look at any dates, such as "Valid From" / "Valid Until" in the main pane,
but also under Certificate Details, and possibly other places.

Actual Results:  
Short dates are used, without the year.

Expected Results:  
I expect a full, unambiguous date. Either a full date according to locale (but
that's ambiguous thanks to Americans being weird like that), or perhaps better,
an ISO-8601 date, which is what my Enigmail does.

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

[kde] [Bug 358656] New: Recoverable kde crash on changing activity with several open windows

[Bruce Mayo via KDE Bugzilla]

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

Bug ID: 358656
   Summary: Recoverable kde crash on changing activity with
several open windows
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: progsplusd...@arcor.de

Application: plasma-desktop (4.12.2)
KDE Platform Version: 4.14.2
Qt Version: 4.8.2
Operating System: Linux 3.2.0-95-generic-pae i686
Distribution: Ubuntu 12.04.5 LTS

-- Information about the crash:
- What I was doing when the application crashed:
Changed activity, klicking on the activity manager icon (red-blue-green dots),
while 6 okular windows were open and mirrored separately in the task manager
panel, with "lock widgets" off. After the crash, only one okular icon appeared
in the task manager panel, but with a small triangle to indicate that the the 6
open files could be seen in a tool tip-type list when the mouse hovers over the
icon.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Plasma Desktop Shell (plasma-desktop), signal: Segmentation fault
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0xb1c4b740 (LWP 2347))]

Thread 4 (Thread 0xa3f17b40 (LWP 2355)):
#0  0xb7729428 in __kernel_vsyscall ()
#1  0xb288796b in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/i386-linux-gnu/libpthread.so.0
#2  0xb75e349c in pthread_cond_wait () from /lib/i386-linux-gnu/libc.so.6
#3  0xb37e0029 in ?? () from /usr/lib/i386-linux-gnu/libQtScript.so.4
#4  0xb37e006f in ?? () from /usr/lib/i386-linux-gnu/libQtScript.so.4
#5  0xb2883d4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#6  0xb75d5b8e in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 3 (Thread 0xa2027b40 (LWP 2360)):
#0  0xb7729428 in __kernel_vsyscall ()
#1  0xb75c7440 in poll () from /lib/i386-linux-gnu/libc.so.6
#2  0xb2788a3b in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb277b06e in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0xb277b1c1 in g_main_context_iteration () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#5  0xb5fb2de7 in QEventDispatcherGlib::processEvents (this=0xa1700468,
flags=...) at kernel/qeventdispatcher_glib.cpp:426
#6  0xb5f7e6ad in QEventLoop::processEvents (this=0xa2027240, flags=...) at
kernel/qeventloop.cpp:149
#7  0xb5f7e949 in QEventLoop::exec (this=0xa2027240, flags=...) at
kernel/qeventloop.cpp:204
#8  0xb5e67a1c in QThread::exec (this=0xa61fee8) at thread/qthread.cpp:501
#9  0xb5f5bcfd in QInotifyFileSystemWatcherEngine::run (this=0xa61fee8) at
io/qfilesystemwatcher_inotify.cpp:248
#10 0xb5e6aeb0 in QThreadPrivate::start (arg=0xa61fee8) at
thread/qthread_unix.cpp:307
#11 0xb2883d4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#12 0xb75d5b8e in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 2 (Thread 0x9fdaab40 (LWP 2363)):
#0  0xb7729428 in __kernel_vsyscall ()
#1  0xb75c7440 in poll () from /lib/i386-linux-gnu/libc.so.6
#2  0xb2788a3b in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb277b06e in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0xb277b1c1 in g_main_context_iteration () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#5  0xb5fb2de7 in QEventDispatcherGlib::processEvents (this=0x9f400468,
flags=...) at kernel/qeventdispatcher_glib.cpp:426
#6  0xb5f7e6ad in QEventLoop::processEvents (this=0x9fdaa240, flags=...) at
kernel/qeventloop.cpp:149
#7  0xb5f7e949 in QEventLoop::exec (this=0x9fdaa240, flags=...) at
kernel/qeventloop.cpp:204
#8  0xb5e67a1c in QThread::exec (this=0xa736f48) at thread/qthread.cpp:501
#9  0xb5f5bcfd in QInotifyFileSystemWatcherEngine::run (this=0xa736f48) at
io/qfilesystemwatcher_inotify.cpp:248
#10 0xb5e6aeb0 in QThreadPrivate::start (arg=0xa736f48) at
thread/qthread_unix.cpp:307
#11 0xb2883d4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#12 0xb75d5b8e in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 1 (Thread 0xb1c4b740 (LWP 2347)):
[KCrash Handler]
#7  0xb6b6507e in QDeclarativeItem::~QDeclarativeItem (this=0xc6370d0,
__in_chrg=) at graphicsitems/qdeclarativeitem.cpp:1668
#8  0xa3169980 in ?? () from
/usr/lib/kde4/imports/org/kde/plasma/core/libcorebindingsplugin.so
#9  0xa3155db0 in ?? () from
/usr/lib/kde4/imports/org/kde/plasma/core/libcorebindingsplugin.so
#10 0xb5f94203 in qDeleteInEventHandler (o=0xc6370d0) at
kernel/qobject.cpp:4277
#11 0xb5f9b1a8 in QObject::event (this=0xc6370d0, e=0xa4473c0) at
kernel/qobject.cpp:1176
#12 0xb6b5eae2 in QDeclarativeItem::event (this=0xc6370d0, ev=0xa4473c0) at
graphicsitems/qdeclarativeitem.cpp:3746
#13 0xb5469df4 in notify_helper (e=0xa4473c0, receiver=0xc6370d0,
this=0x99c23f0) at kernel/qapplication.cpp:4556
#14 QApplicationPrivate::notify_helper (this=0x99c23f0, 

[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

[Maciej Sitarz via KDE Bugzilla]

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

Maciej Sitarz  changed:

   What|Removed |Added

 CC||macieksit...@wp.pl

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

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

[Wladimir via KDE Bugzilla]

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

--- Comment #73 from Wladimir  ---
I did the same before reading this note, and now is working fine.

Thanks.

On 01/27/2016 05:33 PM, via KDE Bugzilla wrote:
> https://bugs.kde.org/show_bug.cgi?id=345563
>
> --- Comment #72 from gfletc...@eject.co.za ---
> Hi David,
>
> After a bit of time I uninstalled and reinstalled my NVidia driver and now the
> system works well.
>
> Thank you
>
> Sent from my iPad
>
>> On 27 Jan 2016, at 19:48, David Edmundson via KDE Bugzilla 
>>  wrote:
>>
>> https://bugs.kde.org/show_bug.cgi?id=345563
>>
>> David Edmundson  changed:
>>
>>What|Removed |Added
>> 
>>  CC||man...@gmail.com
>>
>> --- Comment #71 from David Edmundson  ---
>> *** Bug 358645 has been marked as a duplicate of this bug. ***
>>
>> -- 
>> You are receiving this mail because:
>> You are on the CC list for the bug.

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

[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

[Enrico Tagliavini via KDE Bugzilla]

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

Enrico Tagliavini  changed:

   What|Removed |Added

 CC||enrico.tagliav...@gmail.com

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

[plasmashell] [Bug 355953] Desktop on screens are switched on restart

[Enrico Tagliavini via KDE Bugzilla]

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

Enrico Tagliavini  changed:

   What|Removed |Added

 CC||enrico.tagliav...@gmail.com

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

[kwin] [Bug 344278] deco kcm segfault in KDecoration2::Decoration::update()

[via KDE Bugzilla]

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

a.skemb...@gmail.com changed:

   What|Removed |Added

 CC|a.skemb...@gmail.com|

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

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

[Pasi via KDE Bugzilla]

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

Pasi  changed:

   What|Removed |Added

 CC||kde.track.pasi...@xoxy.net

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

[plasmashell] [Bug 353975] Black screen on second display.

[Enrico Tagliavini via KDE Bugzilla]

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

Enrico Tagliavini  changed:

   What|Removed |Added

 CC||enrico.tagliav...@gmail.com

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

[plasmashell] [Bug 347637] When I unplug the HDMI output, my desktop gets a bigger resolution - Samsung R480

[Enrico Tagliavini via KDE Bugzilla]

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

Enrico Tagliavini  changed:

   What|Removed |Added

 CC||enrico.tagliav...@gmail.com

--- Comment #6 from Enrico Tagliavini  ---
For xrandr -q outputs see my comments on bug #310168 . Sorry copy and paste
doesn't work for some weird reason :(

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

[plasmashell] [Bug 358262] time dataEngine has empty Local source

[Martin Klapetek via KDE Bugzilla]

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

--- Comment #3 from Martin Klapetek  ---
Then it would appear you don't have the dataengine built/installed.

Can you confirm you have plasma_engine_time.so in QT_PLUGIN_PATH
and that you have /usr/share/kservices5/plasma-dataengine-time.desktop?

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

[krita] [Bug 352819] Brush icon in Edit Brush Setting is affected by zoom

[Boudewijn Rempt via KDE Bugzilla]

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

--- Comment #3 from Boudewijn Rempt  ---
I concur with Animtim. Maybe we should just no show the icon there anymore,
since  people usually edit the kpp icon in Krita itself?

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

[plasmashell] [Bug 358642] New: KDE crashing every reboot

[Wladimir via KDE Bugzilla]

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

Bug ID: 358642
   Summary: KDE crashing every reboot
   Product: plasmashell
   Version: 5.5.3
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: wlbe...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.3)

Qt Version: 5.5.1
Operating System: Linux 4.3.3-303.fc23.x86_64 x86_64
Distribution: "Fedora release 23 (Twenty Three)"

-- Information about the crash:
After update to kernel 4.3.301, KDE and Plasma crashing all the time.

The crash can be reproduced every time.

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

Thread 7 (Thread 0x7fac995be700 (LWP 2334)):
#0  0x7facb2a72fdd in poll () at /lib64/libc.so.6
#1  0x7facb8f2a272 in _xcb_conn_wait () at /lib64/libxcb.so.1
#2  0x7facb8f2bee7 in xcb_wait_for_event () at /lib64/libxcb.so.1
#3  0x7fac9bedcda9 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5
#4  0x7facb367b3de in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#5  0x7facb1db660a in start_thread () at /lib64/libpthread.so.0
#6  0x7facb2a7ea4d in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7fac92b6b700 (LWP 2339)):
#0  0x7facb2a8ccb2 in clock_gettime () at /lib64/libc.so.6
#1  0x7facb372b956 in qt_gettime() () at /lib64/libQt5Core.so.5
#2  0x7facb38b0949 in QTimerInfoList::updateCurrentTime() () at
/lib64/libQt5Core.so.5
#3  0x7facb38b0eb5 in QTimerInfoList::timerWait(timespec&) () at
/lib64/libQt5Core.so.5
#4  0x7facb38b22ae in timerSourcePrepare(_GSource*, int*) () at
/lib64/libQt5Core.so.5
#5  0x7facadee470d in g_main_context_prepare () at /lib64/libglib-2.0.so.0
#6  0x7facadee509b in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#7  0x7facadee527c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#8  0x7facb38b2ecb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#9  0x7facb3859eca in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#10 0x7facb3676434 in QThread::exec() () at /lib64/libQt5Core.so.5
#11 0x7facb79c1b45 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5
#12 0x7facb367b3de in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#13 0x7facb1db660a in start_thread () at /lib64/libpthread.so.0
#14 0x7facb2a7ea4d in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7fac8ad8d700 (LWP 2356)):
#0  0x7facadee2190 in g_source_iter_next () at /lib64/libglib-2.0.so.0
#1  0x7facadee4ada in g_main_context_check () at /lib64/libglib-2.0.so.0
#2  0x7facadee5110 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#3  0x7facadee527c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#4  0x7facb38b2ecb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#5  0x7facb3859eca in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#6  0x7facb3676434 in QThread::exec() () at /lib64/libQt5Core.so.5
#7  0x7facb79c1b45 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5
#8  0x7facb367b3de in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#9  0x7facb1db660a in start_thread () at /lib64/libpthread.so.0
#10 0x7facb2a7ea4d in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7fac8928d700 (LWP 2357)):
#0  0x7ffda23a6c8f in clock_gettime ()
#1  0x7facb2a8ccc6 in clock_gettime () at /lib64/libc.so.6
#2  0x7facb372b956 in qt_gettime() () at /lib64/libQt5Core.so.5
#3  0x7facb38b0949 in QTimerInfoList::updateCurrentTime() () at
/lib64/libQt5Core.so.5
#4  0x7facb38b0eb5 in QTimerInfoList::timerWait(timespec&) () at
/lib64/libQt5Core.so.5
#5  0x7facb38b22ae in timerSourcePrepare(_GSource*, int*) () at
/lib64/libQt5Core.so.5
#6  0x7facadee470d in g_main_context_prepare () at /lib64/libglib-2.0.so.0
#7  0x7facadee509b in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#8  0x7facadee527c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#9  0x7facb38b2ecb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#10 0x7facb3859eca in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#11 0x7facb3676434 in QThread::exec() () at /lib64/libQt5Core.so.5
#12 0x7facb79c1b45 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5
#13 0x7facb367b3de in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#14 0x7facb1db660a in start_thread () at /lib64/libpthread.so.0
#15 0x7facb2a7ea4d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7fac837b7700 (LWP 2358)):
#0  0x7facb1dbbb10 in 

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

[Bob Ewart via KDE Bugzilla]

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

Bob Ewart  changed:

   What|Removed |Added

 CC|jinni...@bobsown.net|

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

[krita] [Bug 352819] Brush icon in Edit Brush Setting is affected by zoom

[via KDE Bugzilla]

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

--- Comment #4 from anim...@gmail.com ---
I don't think we should remove it like that.
For now it is useful to:
-make a raw (temporary) icon from scratch to see the preset
-load an existing icon and make small edit on it to quickly get a good-looking
custom preset.

Unless we think a lot to design another way to achieve those two things, we
shouldn't remove this
(and I'm not sure we can do something really much better than what we have that
would be worth it... )

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

[plasmashell] [Bug 358640] Icons get scaled too small in task manager on certain panel heights

[Thomas Pfeiffer via KDE Bugzilla]

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

--- Comment #7 from Thomas Pfeiffer  ---
Is it possible for us to remove the task frame in the Breeze so this doesn't
happen anymore?
I know that the previous Breeze version needed that frame for the blue bar on
top, but as the current version doesn't have that anymore, could that be the
way to fix it?

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

[drkonqi] [Bug 354288] Crash Reporting Assistant gets error 32000 from bugzilla

[Jeff Trull via KDE Bugzilla]

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

Jeff Trull  changed:

   What|Removed |Added

 CC||jetr...@sbcglobal.net

--- Comment #1 from Jeff Trull  ---
This just happened to me as well.  Please mark as confirmed.

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

[plasmashell] [Bug 358639] crash

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

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

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


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

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

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

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

 CC||wlbe...@gmail.com

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

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

[plasmashell] [Bug 358642] KDE crashing every reboot

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

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

--- Comment #1 from David Edmundson  ---
Your Open GL drivers are missing

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

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

[kaffeine] [Bug 358644] New: Kaffeine 1.2.2 crasches on .wtv unexpected

[via KDE Bugzilla]

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

Bug ID: 358644
   Summary: Kaffeine 1.2.2 crasches on .wtv unexpected
   Product: kaffeine
   Version: 1.2.2
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: christophpfis...@gmail.com
  Reporter: fab...@t-online.de

Kaffeine plays .wtv files from wmc.
It crashes after some or more minutes.
it´s not reproducabel

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

[plasmashell] [Bug 352008] Crash in MPris Dataengine

[Johan Reitan via KDE Bugzilla]

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

--- Comment #7 from Johan Reitan  ---
Hi, sorry I forgot to follow up on this. Running dbus-monitor without any
arguments produced hundreds of thousands of output lines, so I attached the
output using a filter for mopidy. Please tell me if I can provide anything more
useful.

It is probably worth mentioning that I originally opened this issue over at
mopidy-mpris: https://github.com/mopidy/mopidy-mpris/issues/17.

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

[plasmashell] [Bug 358640] Icons get scaled too small in task manager on certain panel heights

[Eike Hein via KDE Bugzilla]

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

--- Comment #8 from Eike Hein  ---
You can do with the theme what you want, including have no frame. That's up to
the theme designers. I personally like the frame though and I think you're
trying to fix something that doesn't need fixing ...

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

[plasmashell] [Bug 352008] Crash in MPris Dataengine

[Johan Reitan via KDE Bugzilla]

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

--- Comment #6 from Johan Reitan  ---
Created attachment 96870
  --> https://bugs.kde.org/attachment.cgi?id=96870=edit
dbus-monitor output

Output of running:
$ dbus-monitor "sender='org.mpris.MediaPlayer2.mopidy'"
and starting mopidy.

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

[telepathy] [Bug 351785] Crash when clicking 'Configure...' button in Accounts settings

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

 CC||d...@ya.ru

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

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

[krita] [Bug 358643] New: Krita crash on creating new image

[Chris Hills via KDE Bugzilla]

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

Bug ID: 358643
   Summary: Krita crash on creating new image
   Product: krita
   Version: 2.9.10
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: c...@chaz6.com

Application: krita (2.9.10)
KDE Platform Version: 4.14.15
Qt Version: 4.8.7
Operating System: Linux 4.4.0-1-default x86_64
Distribution: "openSUSE Tumbleweed (20160121) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
I opened Krita after updating on Opensuse Tumbleweed for the first time and
tried to create a new image without changing any of the default settings. On
subsequent attempts Krita did not crash.

The crash does not seem to be reproducible.

-- Backtrace:
Application: Krita (krita), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fc43a29a900 (LWP 1949))]

Thread 5 (Thread 0x7fc40f0cb700 (LWP 1957)):
#0  0x7fc43266907f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fc437fb5754 in wait (time=18446744073709551615, this=0x42e71e0) at
thread/qwaitcondition_unix.cpp:86
#2  QWaitCondition::wait (this=, mutex=mutex@entry=0x42e7190,
time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:158
#3  0x7fc437fb15f3 in QSemaphore::acquire (this=this@entry=0x42e6eb0,
n=n@entry=1) at thread/qsemaphore.cpp:144
#4  0x7fc434e518be in KisTileDataPooler::waitForWork (this=0x42e6ea0) at
/usr/src/debug/calligra-2.9.10/krita/image/tiles3/kis_tile_data_pooler.cc:165
#5  0x7fc434e51c88 in KisTileDataPooler::run (this=0x42e6ea0) at
/usr/src/debug/calligra-2.9.10/krita/image/tiles3/kis_tile_data_pooler.cc:187
#6  0x7fc437fb523c in QThreadPrivate::start (arg=0x42e6ea0) at
thread/qthread_unix.cpp:352
#7  0x7fc4326634a4 in start_thread () from /lib64/libpthread.so.0
#8  0x7fc4376debdd in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7fc40e8ca700 (LWP 1958)):
#0  0x7fc43266907f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fc437fb5754 in wait (time=18446744073709551615, this=0x42e7590) at
thread/qwaitcondition_unix.cpp:86
#2  QWaitCondition::wait (this=, mutex=mutex@entry=0x42e7540,
time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:158
#3  0x7fc437fb19e3 in QSemaphore::tryAcquire (this=0x42e7250, n=n@entry=1,
timeout=timeout@entry=-1) at thread/qsemaphore.cpp:221
#4  0x7fc434e6d073 in KisTileDataSwapper::waitForWork
(this=this@entry=0x42e6ee0) at
/usr/src/debug/calligra-2.9.10/krita/image/tiles3/swap/kis_tile_data_swapper.cpp:86
#5  0x7fc434e6d2fa in KisTileDataSwapper::run (this=0x42e6ee0) at
/usr/src/debug/calligra-2.9.10/krita/image/tiles3/swap/kis_tile_data_swapper.cpp:92
#6  0x7fc437fb523c in QThreadPrivate::start (arg=0x42e6ee0) at
thread/qthread_unix.cpp:352
#7  0x7fc4326634a4 in start_thread () from /lib64/libpthread.so.0
#8  0x7fc4376debdd in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7fc40f8cc700 (LWP 1960)):
#0  0x7fc43266907f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fc437fb5754 in wait (time=18446744073709551615, this=0x480) at
thread/qwaitcondition_unix.cpp:86
#2  QWaitCondition::wait (this=this@entry=0x4aaa5e8,
mutex=mutex@entry=0x4aaa5e0, time=time@entry=18446744073709551615) at
thread/qwaitcondition_unix.cpp:158
#3  0x7fc438fc13ec in QFileInfoGatherer::run (this=0x4aaa5d0) at
dialogs/qfileinfogatherer.cpp:214
#4  0x7fc437fb523c in QThreadPrivate::start (arg=0x4aaa5d0) at
thread/qthread_unix.cpp:352
#5  0x7fc4326634a4 in start_thread () from /lib64/libpthread.so.0
#6  0x7fc4376debdd in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7fc419dcd700 (LWP 1961)):
#0  0x7fc4380cdb8c in QMetaObject::activate
(sender=sender@entry=0x7fc4140008f0, m=m@entry=0x7fc43841e460
,
local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at
kernel/qobject.cpp:3653
#1  0x7fc43811bd33 in QAbstractEventDispatcher::awake
(this=this@entry=0x7fc4140008f0) at
.moc/release-shared/moc_qabstracteventdispatcher.cpp:106
#2  0x7fc4380ec602 in QEventDispatcherUNIX::processEvents
(this=0x7fc4140008f0, flags=...) at kernel/qeventdispatcher_unix.cpp:922
#3  0x7fc4380b9411 in QEventLoop::processEvents
(this=this@entry=0x7fc419dccca0, flags=...) at kernel/qeventloop.cpp:149
#4  0x7fc4380b9725 in QEventLoop::exec (this=this@entry=0x7fc419dccca0,
flags=...) at kernel/qeventloop.cpp:204
#5  0x7fc437fb2a59 in QThread::exec (this=this@entry=0x4aaab80) at
thread/qthread.cpp:538
#6  0x7fc43809a4f3 in QInotifyFileSystemWatcherEngine::run (this=0x4aaab80)
at io/qfilesystemwatcher_inotify.cpp:265
#7  0x7fc437fb523c in QThreadPrivate::start 

[kdesvn] [Bug 358626] KDESVN crashes when trying to checkout a repo

[Christian Ehrlicher via KDE Bugzilla]

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

--- Comment #3 from Christian Ehrlicher  ---
Ok, that's the reason. I'll fix it asap.

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

[kdesvn] [Bug 358626] KDESVN crashes when trying to checkout a repo

[Christian Ehrlicher via KDE Bugzilla]

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

Christian Ehrlicher  changed:

   What|Removed |Added

 CC||ch.ehrlic...@gmx.de

--- Comment #1 from Christian Ehrlicher  ---
What url did you use? svn:// or http:// ?

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

[kwin] [Bug 358646] Rendering breaks if Triple Buffer detection gives NOT available

[Thomas Lübking via KDE Bugzilla]

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

--- Comment #2 from Thomas Lübking  ---
Sh*** I didn't look at the reporter ;-)

IIrc you actually mentioned that before (mailing list?) but don't recall on the
details.
Either way, it would be good to know whether this also occurs if you enforce
the non-blocking path (and what "completely broken" means itr)

Could it be rather related to
export KWIN_USE_BUFFER_AGE=0
?

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

[plasmashell] [Bug 358640] Icons get scaled too small in task manager on certain panel heights

[Eike Hein via KDE Bugzilla]

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

--- Comment #10 from Eike Hein  ---
Please note that I recently spent hours and hours and hours fixing the broken
Task Manager theme files and will revert any commits that regress it again.
Make sure changes are reviewed beforehand.

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

[krita] [Bug 344572] new image dialog default size slightly too large for 1024x768 display

[Alan Horkan via KDE Bugzilla]

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

--- Comment #4 from Alan Horkan  ---
Firstly thanks and I look forward to using Krita 3.1 and testing 3.0 if I have
time. Secondly and sorry to be a downer, I used to be more optimistic about
Open Source not repeating the same mistakes, but is there a code comment or
design note warning developers to ensure the dialog (or dialogs) continues to
work on smaller screens in the future? 

I don't expect to have the best experience, I only want to be included and for
it to be possible to run Krita on Netbooks or whatever other odd screen sizes
are out there.

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

[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

[Jeff Long via KDE Bugzilla]

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

Jeff Long  changed:

   What|Removed |Added

 CC||l...@ku.edu

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

[kwin] [Bug 358646] Rendering breaks if Triple Buffer detection gives NOT available

[Thomas Lübking via KDE Bugzilla]

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

--- Comment #1 from Thomas Lübking  ---
There's no fix - the detection is heuristic and can fail if swapping takes "too
long" for external reasons.

If the code falsely believes you'r e on blocked swapping, the timing
calculation is flawed (though please elaborate on "completely broken" - TB
detection may be rather a sympton than the cause!)

As workaround export KWIN_TRIPLE_BUFFER=1

~/.config/plasma-workspace/env/kwin_env.sh
 snip 
#!/bin/sh
export KWIN_TRIPLE_BUFFER=1
 /snip 

chmod +x ~/.config/plasma-workspace/env/kwin_env.sh

This will bypass the detection and get you into the non-blocking codepath
unconditionally.

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

[plasmashell] [Bug 358262] time dataEngine has empty Local source

[abulak via KDE Bugzilla]

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

--- Comment #4 from abulak  ---
Good guess!
I have plasma_engine_time.so and
/usr/share/kservices5/plasma-dataengine-time.desktop.
HOWEVER I don't have plasma_engine_time.so in QT_PLUGIN_PATH:
QT_PLUGIN_PATH points to /usr/lib64/kde4/plugins

kf5-config --qt-plugins points to /usr/lib64/qt5/plugins

so this should be added somewhere in /etc/env.d I guess??
Anyway it seems more a distribution problem than kde

Thanks!

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

[plasmashell] [Bug 358642] KDE crashing every reboot

[Wladimir via KDE Bugzilla]

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

--- Comment #2 from Wladimir  ---
Hi David !

After 4 or 5 boots everything was normal, it seems that akmod compiled 
nvidia driver after all these retries.

Thanks for your support.

Best  regards.


  On 01/27/2016 01:41 PM, David Edmundson via KDE Bugzilla wrote:
> https://bugs.kde.org/show_bug.cgi?id=358642
>
> David Edmundson  changed:
>
> What|Removed |Added
> 
>   Status|UNCONFIRMED |RESOLVED
>   Resolution|--- |DUPLICATE
>
> --- Comment #1 from David Edmundson  ---
> Your Open GL drivers are missing
>
> *** This bug has been marked as a duplicate of bug 345563 ***
>

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

[kwin] [Bug 358646] New: Rendering breaks if Triple Buffer detection gives NOT available

[Martin Gräßlin via KDE Bugzilla]

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

Bug ID: 358646
   Summary: Rendering breaks if Triple Buffer detection gives NOT
available
   Product: kwin
   Version: git master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: glx
  Assignee: kwin-bugs-n...@kde.org
  Reporter: mgraess...@kde.org
 Flags: Intel+

>From Time to time my KWin (Intel Ivybridge) reports:
Triple buffering detection: "NOT available"  - Mean block time: 1.25074 ms

>From that time on the rendering is completely broken and restarting the
compositor fixes it. The next triple buffer detection might work again. E.g.
the current session has:

KWin::SwapProfiler::end: Triple buffering detection: "Available"  - Mean block
time: 0.986466 ms

>From what I understand NOT available will call setBlocksForRetrace(true) and
changes the behavior.

I do not experience this behavior on Intel Sandybridge. The behavior is more
easily triggered when X has problems (plugging in my headset makes X input
handling freeze) or when KWin QML is loaded (long block?).

I'm interested fixing this but am not familiar enough with the swapping code.
Where to look at and how can I start KWin with going directly in the "broken"
code path?

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

[kwin] [Bug 356318] I can run wayland plasma session from terminal, not from sddm

[Hrvoje Senjan via KDE Bugzilla]

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

Hrvoje Senjan  changed:

   What|Removed |Added

 CC||hrvoje.sen...@gmail.com

--- Comment #11 from Hrvoje Senjan  ---
Will add the required qtwayland dep.
1) I only wonder which package is most logically correct.
2) Can upstream have find_package call for Qt5Wayland (mark as runtime)

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

[kwin] [Bug 358646] Rendering breaks if Triple Buffer detection gives NOT available

[Thomas Lübking via KDE Bugzilla]

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

--- Comment #3 from Thomas Lübking  ---
in addition,  export KWIN_TRIPLE_BUFFER=0 should kick you into the broken path.
If that triggers it, I assume the cause to be either
a) the reversed paint/sync/swap cycle which is required to measure the time we
spend on creating the frame (::endRenderingFrame) or
b) the recently added glXWaitGL() call in ::present() ("at least the nvidia
blob manages to swap async")

latter only in glxbackend.cpp, former also in eglonxbackend.cpp

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

[frameworks-knotifications] [Bug 356523] Hide/restore window from system tray cause change it position

[Martin Klapetek via KDE Bugzilla]

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

--- Comment #14 from Martin Klapetek  ---
> Any results here?

No.

@Thomas
> Actually™ you should not have to explicitly set the current geometry

I did some testing - if I remove this call completely, the placement is
fully random from what I can tell. if I simply replace
info.frameGeometry().topLeft()
with info.topLeft(), it still gets restored to a different position. Apparently
this is to some extent due to having QT_DEVICE_PIXEL_RATIO=2 as the
widget geometry is exactly half of what KWindowInfo reports, therefore
simply telling the QWidget to move to KWindowInfo geometry moves
it twice as much.

But not just that, I've tried something like

associatedWidget->move(info.geometry().topLeft().x() / 2,
info.geometry().topLeft().y() / 2);

but it would still restore it by some random pixels off.

What does, however, seems to restore it properly is this:

associatedWidget->windowHandle()->setX(info.geometry().topLeft().x()
/2);
associatedWidget->windowHandle()->setY(info.geometry().topLeft().y()
/2);

...where the "/2" should obviously be replaced by QT_DEVICE_PIXEL_RATIO.

But now tell me if this is a good and/or valid fix.

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

[plasmashell] [Bug 358262] time dataEngine has empty Local source

[Martin Klapetek via KDE Bugzilla]

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

Martin Klapetek  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |INVALID
 Status|NEEDSINFO   |RESOLVED

--- Comment #5 from Martin Klapetek  ---
Yep, this is certainly a local problem only :)

Unfortunately I'm not familiar with Gentoo so I cannot really
give you any advice on what would the best course of action
be, best is to probably contact your distro packagers.

I'll close it here then, thanks.

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

[plasmashell] [Bug 344879] memory leak in plasmashell - huge ram usage

[painless roaster via KDE Bugzilla]

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

--- Comment #119 from painless roaster  ---
valgrind detect memor leak (from 15minutes run) here:

==13702== 56,137,960 bytes in 32,858 blocks are definitely lost in loss record
62,663 of 62,663
==13702==at 0x4C28C50: malloc (in
/usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==13702==by 0x7496DFA:
QSGBatchRenderer::Renderer::map(QSGBatchRenderer::Buffer*, int, bool) (in
/usr/lib64/libQt5Quick.so.5.5.1)
==13702==by 0x7499074:
QSGBatchRenderer::Renderer::uploadBatch(QSGBatchRenderer::Batch*) (in
/usr/lib64/libQt5Quick.so.5.5.1)
==13702==by 0x74A4375: QSGBatchRenderer::Renderer::render() (in
/usr/lib64/libQt5Quick.so.5.5.1)
==13702==by 0x74B00AE: QSGRenderer::renderScene(QSGBindable const&) (in
/usr/lib64/libQt5Quick.so.5.5.1)
==13702==by 0x74B08FA: QSGRenderer::renderScene(unsigned int) (in
/usr/lib64/libQt5Quick.so.5.5.1)
==13702==by 0x74C0DDD: QSGRenderContext::renderNextFrame(QSGRenderer*,
unsigned int) (in /usr/lib64/libQt5Quick.so.5.5.1)
==13702==by 0x750ADCA: QQuickWindowPrivate::renderSceneGraph(QSize const&)
(in /usr/lib64/libQt5Quick.so.5.5.1)
==13702==by 0x74DB78A: ??? (in /usr/lib64/libQt5Quick.so.5.5.1)
==13702==by 0x74DC890: ??? (in /usr/lib64/libQt5Quick.so.5.5.1)
==13702==by 0xA9D041B: QApplicationPrivate::notify_helper(QObject*,
QEvent*) (in /usr/lib64/libQt5Widgets.so.5.5.1)
==13702==by 0xA9D58E5: QApplication::notify(QObject*, QEvent*) (in
/usr/lib64/libQt5Widgets.so.5.5.1)

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

[frameworks-knotifications] [Bug 356523] Hide/restore window from system tray cause change it position

[Thomas Lübking via KDE Bugzilla]

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

--- Comment #15 from Thomas Lübking  ---
What if you explicity
  associatedWidget->setAttribute(Qt::WA_Moved);

(the individual sets will likely cause this whereas the combined one will
figure it's no effective change and shortcut exit)

The QT_DEVICE_PIXEL_RATIO situation is kinda worrysome.
KWindowSystem deals with real pixels (and I doubt we can just change that, we
don't know the source of the calculation), so either this is the expected
behavior for toplevel widget actions or a bug in Qt (while it makes absolutely
sense for internal widgets, global positioning is usually driven by outside
values which do not related to the locals environment)

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

[plasmashell] [Bug 353752] Rigth click on task in taskmanager and click to other cause activate minized on prev

[Eike Hein via KDE Bugzilla]

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

Eike Hein  changed:

   What|Removed |Added

 Resolution|INVALID |DUPLICATE

--- Comment #5 from Eike Hein  ---


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

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

[plasmashell] [Bug 356018] Entries stay highlighted after closing context menu

[Eike Hein via KDE Bugzilla]

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

Eike Hein  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/plas
   ||ma-desktop/9e0a7e991dbfc862
   ||a72f21f4662e280aff8ab317
 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #2 from Eike Hein  ---
Git commit 9e0a7e991dbfc862a72f21f4662e280aff8ab317 by Eike Hein.
Committed on 27/01/2016 at 17:27.
Pushed by hein into branch 'Plasma/5.5'.

Fix entries staying highlighted after context menu closes.

MouseArea.containsMouse is set to true on press but never unset when
the item accepts hover events. This is unfortunate but documented
behavior so it can't be changed in Qt 5. If there's a leave before
the press, that means containsMouse ends up true even with the mouse
outside the item. So we unset the state ourselves.

M  +29   -2applets/taskmanager/package/contents/ui/Task.qml
M  +14   -0applets/taskmanager/plugin/backend.cpp
M  +3-0applets/taskmanager/plugin/backend.h

http://commits.kde.org/plasma-desktop/9e0a7e991dbfc862a72f21f4662e280aff8ab317

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

[plasmashell] [Bug 356018] Entries stay highlighted after closing context menu

[Eike Hein via KDE Bugzilla]

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

Eike Hein  changed:

   What|Removed |Added

 CC||bvb...@abv.bg

--- Comment #3 from Eike Hein  ---
*** Bug 353752 has been marked as a duplicate of this bug. ***

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

[frameworks-knotifications] [Bug 356523] Hide/restore window from system tray cause change it position

[Martin Klapetek via KDE Bugzilla]

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

--- Comment #16 from Martin Klapetek  ---
>   associatedWidget->setAttribute(Qt::WA_Moved);

Should just this be in or with some of the other lines? This standalone
puts it always to the bottom-left corner of my screen.

> KWindowSystem deals with real pixels

Yeah which means that the widget either needs to be move to real pixels
(ie. apply the device pixel ratio) or the window needs to be moved externally
by something else.

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

[KScreen] [Bug 356871] KScreen does not adapt to window size of QEMU/QXL/Spice VM window

[OlafLostViking via KDE Bugzilla]

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

--- Comment #1 from OlafLostViking  ---
I may add that with xrandr the resolution change is visible:

* before resizing the window
[olaflostviking@kessel ~]$ xrandr 
Screen 0: minimum 320 x 200, current 1280 x 720, maximum 8192 x 8192
Virtual-0 connected primary 1280x720+0+0 0mm x 0mm
   1280x720  59.86*+
   1920x1200 59.88  
   1920x1080 59.96  
   1600x1200 59.87  
   1680x1050 59.95  
   1400x1050 59.98  
   1280x1024 59.89  
   1440x900  59.89  
   1280x960  59.94  
   1280x854  59.89  
   1280x800  59.81  
   1152x768  59.78  
   1024x768  59.92  
   800x600   59.86  
   848x480   59.66  
   720x480   59.71  
   640x480   59.38  
Virtual-1 disconnected
Virtual-2 disconnected
Virtual-3 disconnected
[olaflostviking@kessel ~]$


* after resizing the window
[olaflostviking@kessel ~]$ xrandr 
Screen 0: minimum 320 x 200, current 1280 x 720, maximum 8192 x 8192
Virtual-0 connected primary 1280x720+0+0 0mm x 0mm
   1768x963  60.00 +
   1920x1200 59.88  
   1920x1080 59.96  
   1600x1200 59.87  
   1680x1050 59.95  
   1400x1050 59.98  
   1280x1024 59.89  
   1440x900  59.89  
   1280x960  59.94  
   1280x854  59.89  
   1280x800  59.81  
   1280x720  59.86* 
   1152x768  59.78  
   1024x768  59.92  
   800x600   59.86  
   848x480   59.66  
   720x480   59.71  
   640x480   59.38  
Virtual-1 disconnected
Virtual-2 disconnected
Virtual-3 disconnected
[olaflostviking@kessel ~]$

Here you can see you X correctly "thinks" the preferred resolution is 1768x963.

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

[kdenlive] [Bug 358648] New: Allow configurable columns in Project Bin

[Sam Muirhead via KDE Bugzilla]

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

Bug ID: 358648
   Summary: Allow configurable columns in Project Bin
   Product: kdenlive
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: s...@cameralibre.cc

I brought up this topic in the forum and TheDiveO helped refine it to this
idea: 

Basically the specific goal is to be able to show a 'Markers' column in the
Project Bin alongside (sub)clips, so that the user can very quickly scan the
Bin and find clips containing relevant quotes or material that they have noted
down in the form of markers.
(see the forum topic to understand how this fits into a workflow for a fast
initial rough cut: https://forum.kde.org/viewtopic.php?f=265=130736)
in this image you see the use of markers in the Timeline, however there's no
similar marker info in the bin:
http://www.cameralibre.cc/wp-content/uploads/kdenlive.png

To achieve that goal, and to allow people to adapt the Bin to their own needs,
we thought the best method would be to allow the columns in the Project Bin to
be configurable, like in Dolphin/Nautilus etc - you could choose to show or
hide Thumbnails/Clip Name/Description/Creation Time/Duration/Markers etc.

Reproducible: Always

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

[dolphin] [Bug 358649] New: Middle button on toolbar "GoUp" no longer functions

[Terry Barnaby via KDE Bugzilla]

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

Bug ID: 358649
   Summary: Middle button on toolbar "GoUp" no longer functions
   Product: dolphin
   Version: 15.12.1
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: te...@beam.ltd.uk

With the Kde 4 version of dolphin, clicking with the middle mouse button on the
"goup" toolbar icon resulted in a new tab being opened one level above the
current location. This very useful functionality is missing with the Kde 5
version of dolphin.

Reproducible: Always

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

[frameworks-knotifications] [Bug 356523] Hide/restore window from system tray cause change it position

[Thomas Lübking via KDE Bugzilla]

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

--- Comment #17 from Thomas Lübking  ---
This alone should do (and not even be required), but I guess there there's more
to it in the SNI case, like the widget being destroyed and recreated (so you've
not moved this widget at all, but just told the WM to believe so)

In the latter case you could either carry over the last position (and move it
in QWidget geometries, sth. like ie.

oldPosition = oldWidget->pos();

QWidget *newWidget = new QWidget;
newWidget->move(oldPosition);
newWidget->show();


---

"Something else™" cannot move the widget as eg. the WM doesn't know that this
window has been there before (or that it should restore that former geometry)

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

[plasmashell] [Bug 358647] New: Plasma crashes

[Dimitris via KDE Bugzilla]

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

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

Application: plasmashell (5.4.3)

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

-- Information about the crash:
- What I was doing when the application crashed:
Booting the system
- Unusual behavior I noticed:
System cannot boot with default settings
in recovery mode, system boots but no plasma

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

Thread 15 (Thread 0x7ff70cdb1700 (LWP 2197)):
#0  0x7ff71b4bec1d in poll () at /lib64/libc.so.6
#1  0x7ff720445422 in  () at /usr/lib64/libxcb.so.1
#2  0x7ff72044700f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7ff70f56a3c9 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7ff71bbbd32f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7ff71acba0a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7ff71b4c704d in clone () at /lib64/libc.so.6

Thread 14 (Thread 0x7ff6ffa41700 (LWP 2206)):
#0  0x7ff71acbe05f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7ff7064eda33 in  () at /usr/lib64/dri/swrast_dri.so
#2  0x7ff7064ed5a7 in  () at /usr/lib64/dri/swrast_dri.so
#3  0x7ff71acba0a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7ff71b4c704d in clone () at /lib64/libc.so.6

Thread 13 (Thread 0x7ff6ff240700 (LWP 2207)):
#0  0x7ff71acbe05f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7ff7064eda33 in  () at /usr/lib64/dri/swrast_dri.so
#2  0x7ff7064ed5a7 in  () at /usr/lib64/dri/swrast_dri.so
#3  0x7ff71acba0a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7ff71b4c704d in clone () at /lib64/libc.so.6

Thread 12 (Thread 0x7ff6fea3f700 (LWP 2208)):
#0  0x7ff71acbe05f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7ff7064eda33 in  () at /usr/lib64/dri/swrast_dri.so
#2  0x7ff7064ed5a7 in  () at /usr/lib64/dri/swrast_dri.so
#3  0x7ff71acba0a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7ff71b4c704d in clone () at /lib64/libc.so.6

Thread 11 (Thread 0x7ff6fe23e700 (LWP 2209)):
#0  0x7ff71acbe05f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7ff7064eda33 in  () at /usr/lib64/dri/swrast_dri.so
#2  0x7ff7064ed5a7 in  () at /usr/lib64/dri/swrast_dri.so
#3  0x7ff71acba0a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7ff71b4c704d in clone () at /lib64/libc.so.6

Thread 10 (Thread 0x7ff6fda3d700 (LWP 2210)):
#0  0x7ff71acbe05f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7ff7064eda33 in  () at /usr/lib64/dri/swrast_dri.so
#2  0x7ff7064ed5a7 in  () at /usr/lib64/dri/swrast_dri.so
#3  0x7ff71acba0a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7ff71b4c704d in clone () at /lib64/libc.so.6

Thread 9 (Thread 0x7ff6fd23c700 (LWP 2211)):
#0  0x7ff71acbe05f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7ff7064eda33 in  () at /usr/lib64/dri/swrast_dri.so
#2  0x7ff7064ed5a7 in  () at /usr/lib64/dri/swrast_dri.so
#3  0x7ff71acba0a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7ff71b4c704d in clone () at /lib64/libc.so.6

Thread 8 (Thread 0x7ff6fca3b700 (LWP 2212)):
#0  0x7ff71acbe05f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7ff7064eda33 in  () at /usr/lib64/dri/swrast_dri.so
#2  0x7ff7064ed5a7 in  () at /usr/lib64/dri/swrast_dri.so
#3  0x7ff71acba0a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7ff71b4c704d in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7ff6fc23a700 (LWP 2213)):
#0  0x7ff71acbe05f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7ff7064eda33 in  () at /usr/lib64/dri/swrast_dri.so
#2  0x7ff7064ed5a7 in  () at /usr/lib64/dri/swrast_dri.so
#3  0x7ff71acba0a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7ff71b4c704d in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7ff6f99e9700 (LWP 2223)):
#0  0x7ff717b77cf9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0
#1  0x7ff717b35f68 in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#2  0x7ff71bdefd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#3  0x7ff71bd96d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#4  0x7ff71bbb861a in QThread::exec()