[kmines] [Bug 356811] Kmines number indicators are incorrect.

[Frederik Schwarzer via KDE Bugzilla]

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

Frederik Schwarzer  changed:

   What|Removed |Added

 CC||schwar...@kde.org

--- Comment #1 from Frederik Schwarzer  ---
Hi,
please attach the image to the bug report directly.

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

[plasma-nm] [Bug 356772] "connect" does not work for mobile broadband connection

[Jan Grulich via KDE Bugzilla]

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

--- Comment #4 from Jan Grulich  ---
Created attachment 96140
  --> https://bugs.kde.org/attachment.cgi?id=96140&action=edit
Patch allowing to unlock PIN2 and other lock types

Are you able to test this patch?

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

[kscreenlocker] [Bug 354811] kscreenlocker_greet crashes if using compiz instead of kwin

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #11 from Martin Gräßlin  ---
Workaround patch: https://git.reviewboard.kde.org/r/126397/

I don't have Compiz in my distribution, I cannot verify whether it works. If
you could compile the patch and test whether it solves the problem, it would be
appreciated.

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

[plasmashell] [Bug 356461] Notification Settings wrong default display for notifications and notifaction position.

[Artur O . via KDE Bugzilla]

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

--- Comment #24 from Artur O.  ---
(In reply to Raghavendra kamath from comment #23)
> For me setting the custom location in notification solves thew problem and
> this setting now persists after reboot unlike earlier. I am on arch and can
> say this now works as intended

This bug report is about the default position not custom position.

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

[plasma-nm] [Bug 354782] [RFE] locking down some functions

[Jan Grulich via KDE Bugzilla]

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

--- Comment #4 from Jan Grulich  ---
Of course it's easy to get info whether some hardware is enabled or present,
but what if someone would like to configure a wifi connection for a future
usage or pre-configure mobile connection when he has time and don't want to be
bothered with this once he plugs in required device? I know, this is really
stupid and probably not a common case, but we shouldn't restrict our users on
our assumption that they won't probably use it. If you are willing to create a
patch/solution allowing to simply configure this then I'm more then happy to
review it and include it in plasma-nm, but my free time is limited and I don't
want to spend it on such specific feature.

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

[plasma-nm] [Bug 342007] Active connections disappear from the list of connections when the bridged connection is disconnected while the VPN connection is active

[Jan Grulich via KDE Bugzilla]

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

--- Comment #6 from Jan Grulich  ---
Is the situation different with Plasma 5?

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

[bugs.kde.org] [Bug 356793] Crash reporting system is missing

[Ben Cooksley via KDE Bugzilla]

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

Ben Cooksley  changed:

   What|Removed |Added

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

--- Comment #1 from Ben Cooksley  ---
Bugs in the crash reporting system (which runs on your local computer at least)
should be reported under the product "drkonqi".

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

[yakuake] [Bug 341330] Active terminal doesn't always gain focus correctly after opening the window

[Phil Schaf via KDE Bugzilla]

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

Phil Schaf  changed:

   What|Removed |Added

 CC||flying-sh...@web.de

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

[yakuake] [Bug 354646] [heisenbug] Focus missing in tabs after unknown actions

[Phil Schaf via KDE Bugzilla]

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

Phil Schaf  changed:

   What|Removed |Added

 CC||flying-sh...@web.de

--- Comment #1 from Phil Schaf  ---
duplicate of bug 341330, i guess

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

[plasma-nm] [Bug 341122] Error message "failed to rescan"

[Jan Grulich via KDE Bugzilla]

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

--- Comment #5 from Jan Grulich  ---
Git commit 1d0905abafb51fcc956bdc32fdb0be7673608c89 by Jan Grulich.
Committed on 17/12/2015 at 08:27.
Pushed by grulich into branch 'master'.

Disable notification about failed re-scan by default

Let's be less annoying for users who are not patient and who press
the scan button while already scanning.

M  +1-1kded/networkmanagement.notifyrc

http://commits.kde.org/plasma-nm/1d0905abafb51fcc956bdc32fdb0be7673608c89

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

[plasma-nm] [Bug 342007] Active connections disappear from the list of connections when the bridged connection is disconnected while the VPN connection is active

[via KDE Bugzilla]

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

--- Comment #7 from aux...@gmail.com ---
With Plasma 5.5.1 and NetworkManager 1.0.6, it is impossible to reconnect to
the bridge after disconnection without restarting NetworkManager, therefore I'm
unable to test for this problem.

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

[plasmashell] [Bug 356461] Notification Settings wrong default display for notifications and notifaction position.

[via KDE Bugzilla]

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

--- Comment #25 from aux...@gmail.com ---
I still have the problem with the incorrect placement of the notifications even
after forcing them to display on the lower right corner of the desktop (by the
way, I had already done this before and refreshed the setting). Most
notifications now appear on the right, but the ones from the nm plasmoid mostly
appear on the left.

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

[frameworks-kidletime] [Bug 328987] Power saving should not trigger if joystick is in use

[Afief Halumi via KDE Bugzilla]

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

--- Comment #9 from Afief Halumi  ---
Would donating a gamepad to a developer help or is this issue too far out of
scope for KIdleTime? The input-devices in systemsettings seems to be aware of
of the joysticks and be able to get their events, so perhaps it is dealt with
in another part of KDE already.

Out of curiosity, is this X specific or will this affect Wayland as well? (i.e.
will this bug solve itself as soon as the Wayland transition is complete?)

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

[plasma-nm] [Bug 342007] Active connections disappear from the list of connections when the bridged connection is disconnected while the VPN connection is active

[Jan Grulich via KDE Bugzilla]

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

--- Comment #8 from Jan Grulich  ---
Does it work using nmcli? Anyway, we just filtered out "interprise" devices
like bridge, bond etc. which are not that common on desktops so those
connection types won't be shown in the applet anymore (for Plasma 5.6). You
should be still able to configure them in our editor, however preferred way is
to use nmcli as I'm not sure they have ever worked perfectly in plasma-nm.

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

[frameworks-kservice] [Bug 353203] 20 seconds delay on kde login with kservice 5.14.3

[OlafLostViking via KDE Bugzilla]

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

--- Comment #44 from OlafLostViking  ---
I can not confirm that completely. While it seems to be true that the login is
faster (but no guarantees for now ;-) ), a lot of autostarted programs (be it
by explicit autostart or by session restoration) now take this time to finally
start up. The desktop/plasmashell is (partly?) there and seems to be useable,
but a lot of the programs are just starting much later (and in case of programs
showing dialogs, pop up all together - like a restored kontact with open mails
or the CopyAgent from copy.com).

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

[kscreenlocker] [Bug 354811] kscreenlocker_greet crashes if using compiz instead of kwin

[Mikhail Khvoinitsky via KDE Bugzilla]

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

--- Comment #12 from Mikhail Khvoinitsky  
---
(In reply to Martin Gräßlin from comment #11)
> Workaround patch: https://git.reviewboard.kde.org/r/126397/
> 
> I don't have Compiz in my distribution, I cannot verify whether it works. If
> you could compile the patch and test whether it solves the problem, it would
> be appreciated.

It solves the problem, thank you.
Which version of frameworks will be this patch released in?

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

[plasma-nm] [Bug 342007] Active connections disappear from the list of connections when the bridged connection is disconnected while the VPN connection is active

[via KDE Bugzilla]

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

--- Comment #9 from aux...@gmail.com ---
This must be a bug in NetworkManager: if I disconnect the bridge, even with
nmcli, it loses its interfaces (brctl showstp br0 is empty) and NetworkManager
cannot connect to the network. Sometimes even restarting NetworkManager does
not fix this and I must delete br0 first, then restart NM.

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

[kscreenlocker] [Bug 354811] kscreenlocker_greet crashes if using compiz instead of kwin

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #13 from Martin Gräßlin  ---
> It solves the problem, thank you.

Thanks for testing

> Which version of frameworks will be this patch released in?

will go into the next.

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

[frameworks-kidletime] [Bug 328987] Power saving should not trigger if joystick is in use

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #10 from Martin Gräßlin  ---
> Would donating a gamepad to a developer help or is this issue too far out of 
> scope for KIdleTime?

I have a gamepad for my playstation. Need to try whether it works at all on
linux.

> Out of curiosity, is this X specific or will this affect Wayland as well?

I don't know yet. But actually that's the part I want to test with the gamepad.
If it's fixed on Wayland it's unlikely that we will get support for it in
KIdleTime on X11. If it works in neither, I will look into what could be a
solution for KIdleTime. It might mess with the functionality a lot, so no
promise that it can be fixed.

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

[okular] [Bug 173896] Sent-to menu entry or send-via-email menu-entry

[Rok via KDE Bugzilla]

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

Rok  changed:

   What|Removed |Added

 CC||r...@kanardia.eu

--- Comment #20 from Rok  ---
The developers should (sometimes) listen to the public.

This feature is in now-days really as common as saving file to the disk. This
is true for all applications which can open any file. In fact the proper
integration of KDE enables simple and consistent implementation of SHARE
function.

If I look into the future it is more important than SaveAs. From user
perspective (tablet users) this enables to save file not only disk but also on
different -internet media.

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

[plasma-nm] [Bug 342007] Active connections disappear from the list of connections when the bridged connection is disconnected while the VPN connection is active

[Jan Grulich via KDE Bugzilla]

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

Jan Grulich  changed:

   What|Removed |Added

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

--- Comment #10 from Jan Grulich  ---
Ok, thanks for the information. I'm going to close this bug now as there is
nothing we can fix in plasma-nm and support for bridge connections was dropped
in the upcoming major version of plasma-nm.

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

[plasmashell] [Bug 356494] System tray volume icon appear in the wrong place

[Nick Cross via KDE Bugzilla]

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

Nick Cross  changed:

   What|Removed |Added

 CC||k...@goots.org

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

[kphotoalbum] [Bug 356809] Adding a new category is not saved

[Tobias Leupold via KDE Bugzilla]

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

Tobias Leupold  changed:

   What|Removed |Added

 CC||tobias.leup...@web.de

--- Comment #1 from Tobias Leupold  ---
"It looks like the bottom of the panel is below the bottom of the screen."
sounds fishy. Could you please post a screenshot? I don't think this is a KPA
bug, but rather some problem with the window manager and/or theme, so that the
"Save"/"Apply changes"/"Cancel" buttons are simply not shown/accessible. We do
have those ;-)

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

[kdelibs] [Bug 355275] kdelibs upgrade - Kopete crashes after closing a window

[Honza Tvrznik via KDE Bugzilla]

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

Honza Tvrznik  changed:

   What|Removed |Added

 CC||flate...@atlas.cz

--- Comment #42 from Honza Tvrznik  ---
For me this problem is not fixed. Kopete still crashes every time when I close
chat window. I have latest kdelibs version (4.14.15-1)

Distro: Arch Linux
KF5 Version: 5.17.0
Plasma version: 5.5.1
KDE Aplications version: 15.12.0

Crash:
Application: Kopete (kopete), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fe2f4e9f840 (LWP 4252))]

Thread 3 (Thread 0x7fe2d3950700 (LWP 4273)):
#0  0x7fe2f18d in poll () from /usr/lib/libc.so.6
#1  0x7fe2ec2d1fbc in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7fe2ec2d20cc in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7fe2f28e2856 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQtCore.so.4
#4  0x7fe2f28b0dc1 in
QEventLoop::processEvents(QFlags) () from
/usr/lib/libQtCore.so.4
#5  0x7fe2f28b1135 in
QEventLoop::exec(QFlags) () from
/usr/lib/libQtCore.so.4
#6  0x7fe2dad22053 in QCA::SyncThread::run() () from /usr/lib/libqca.so.2
#7  0x7fe2f27a214c in ?? () from /usr/lib/libQtCore.so.4
#8  0x7fe2ee2494a4 in start_thread () from /usr/lib/libpthread.so.0
#9  0x7fe2f111a13d in clone () from /usr/lib/libc.so.6

Thread 2 (Thread 0x7fe2d314f700 (LWP 4274)):
#0  0x7fe2f18d in poll () from /usr/lib/libc.so.6
#1  0x7fe2ec2d1fbc in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7fe2ec2d20cc in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7fe2f28e2856 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQtCore.so.4
#4  0x7fe2f28b0dc1 in
QEventLoop::processEvents(QFlags) () from
/usr/lib/libQtCore.so.4
#5  0x7fe2f28b1135 in
QEventLoop::exec(QFlags) () from
/usr/lib/libQtCore.so.4
#6  0x7fe2f279f859 in QThread::exec() () from /usr/lib/libQtCore.so.4
#7  0x7fe2db16413a in ?? () from /usr/lib/kde4/kopete_jabber.so
#8  0x7fe2f27a214c in ?? () from /usr/lib/libQtCore.so.4
#9  0x7fe2ee2494a4 in start_thread () from /usr/lib/libpthread.so.0
#10 0x7fe2f111a13d in clone () from /usr/lib/libc.so.6

Thread 1 (Thread 0x7fe2f4e9f840 (LWP 4252)):
[KCrash Handler]
#6  0x in ?? ()
#7  0x7fe2f28c7a75 in QObject::disconnect(QObject const*, char const*,
QObject const*, char const*) () from /usr/lib/libQtCore.so.4
#8  0x7fe2eb06c4a9 in KParts::PartManager::~PartManager() () from
/usr/lib/libkparts.so.4
#9  0x7fe2eb06c679 in KParts::PartManager::~PartManager() () from
/usr/lib/libkparts.so.4
#10 0x7fe2f28ca8b1 in QObjectPrivate::deleteChildren() () from
/usr/lib/libQtCore.so.4
#11 0x7fe2f28ccf54 in QObject::~QObject() () from /usr/lib/libQtCore.so.4
#12 0x7fe2eb065f7e in KParts::Part::~Part() () from /usr/lib/libkparts.so.4
#13 0x7fe2dc802a6d in KHTMLPart::~KHTMLPart() () from
/usr/lib/libkhtml.so.5
#14 0x7fe2dd011d27 in ChatMessagePart::~ChatMessagePart() () from
/usr/lib/libkopetechatwindow_shared.so.1
#15 0x7fe2dd011e79 in ChatMessagePart::~ChatMessagePart() () from
/usr/lib/libkopetechatwindow_shared.so.1
#16 0x7fe2f28cc3d8 in QObject::event(QEvent*) () from
/usr/lib/libQtCore.so.4
#17 0x7fe2f195939c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQtGui.so.4
#18 0x7fe2f19601f6 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/libQtGui.so.4
#19 0x7fe2f33658aa in KApplication::notify(QObject*, QEvent*) () from
/usr/lib/libkdeui.so.5
#20 0x7fe2f28b254d in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib/libQtCore.so.4
#21 0x7fe2f28b59d6 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib/libQtCore.so.4
#22 0x7fe2f28e26e3 in ?? () from /usr/lib/libQtCore.so.4
#23 0x7fe2ec2d1dc7 in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#24 0x7fe2ec2d2020 in ?? () from /usr/lib/libglib-2.0.so.0
#25 0x7fe2ec2d20cc in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#26 0x7fe2f28e2834 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQtCore.so.4
#27 0x7fe2f1a023f6 in ?? () from /usr/lib/libQtGui.so.4
#28 0x7fe2f28b0dc1 in
QEventLoop::processEvents(QFlags) () from
/usr/lib/libQtCore.so.4
#29 0x7fe2f28b1135 in
QEventLoop::exec(QFlags) () from
/usr/lib/libQtCore.so.4
#30 0x7fe2f28b6ad9 in QCoreApplication::exec() () from
/usr/lib/libQtCore.so.4
#31 0x00414175 in ?? ()
#32 0x7fe2f1051610 in __libc_start_main () from /usr/lib/libc.so.6
#33 0x00414959 in _start ()

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

[kde] [Bug 356819] New: Trying to reopen previous bug - (sorry I need a howto). KDE desktop multiscreen doesn't work again.

[PhillB via KDE Bugzilla]

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

Bug ID: 356819
   Summary: Trying to reopen previous bug - (sorry I need a
howto). KDE desktop multiscreen doesn't work again.
   Product: kde
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: phi...@webwombat.com.au

Either Screen go black or the desktop from the right screen sometimes goes to
the left screen or vice-versa while the other screen is black. Desktop fail to
start on black screen. The black screen will display windows fine.

Sometimes lots of crashes reported on startup now.

Was working OK.

Two computers with the same issue here.

Logging in, then logging out several times (like 3 to 6 times) eventually seems
to make it work. Then everything works perfectly until the next login.

If the computer crashes for any reason then it takes longer (more fiddling
about) to get it going again.

Fedora 23 now. All updates.

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

[kate] [Bug 356820] New: Open Filename in Kate causes crash

[John Barnes via KDE Bugzilla]

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

Bug ID: 356820
   Summary: Open Filename in Kate causes crash
   Product: kate
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: jrbarne...@gmail.com

Application: kate (15.08.1)

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

-- Information about the crash:
Click File --> Open. 
This happens on most occasions. Sometimes the open file dialogue opens
successfully, but usually get the segmentation fault error

The crash can be reproduced every time.

-- Backtrace:
Application: Kate (kate), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fecbeba2900 (LWP 2808))]

Thread 2 (Thread 0x7fec9f8d0700 (LWP 2814)):
#0  0x7fecb74c6ffd in poll () at /lib64/libc.so.6
#1  0x7fecb43db272 in _xcb_conn_wait () at /lib64/libxcb.so.1
#2  0x7fecb43dcee7 in xcb_wait_for_event () at /lib64/libxcb.so.1
#3  0x7feca229cda9 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5
#4  0x7fecb80cf3ce in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#5  0x7fecb568b60a in start_thread () at /lib64/libpthread.so.0
#6  0x7fecb74d2a9d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7fecbeba2900 (LWP 2808)):
[KCrash Handler]
#5  0x7feca22b3f08 in QXcbWindow::setParent(QPlatformWindow const*) () at
/lib64/libQt5XcbQpa.so.5
#6  0x7fecb914d8bb in QWindow::setParent(QWindow*) () at
/lib64/libQt5Gui.so.5
#7  0x7fecb99285d5 in QWidgetPrivate::setParent_sys(QWidget*,
QFlags) () at /lib64/libQt5Widgets.so.5
#8  0x7fecb9933fda in QWidget::setParent(QWidget*, QFlags)
() at /lib64/libQt5Widgets.so.5
#9  0x7fecb99350cc in QWidget::setParent(QWidget*) () at
/lib64/libQt5Widgets.so.5
#10 0x7fecb9a1b11c in QDialogButtonBox::addButton(QAbstractButton*,
QDialogButtonBox::ButtonRole) () at /lib64/libQt5Widgets.so.5
#11 0x7fec9eaa0e59 in KDEPlatformFileDialog::KDEPlatformFileDialog() () at
/usr/lib64/qt5/plugins/platformthemes/KDEPlatformTheme.so
#12 0x7fec9eaa1282 in
KDEPlatformFileDialogHelper::KDEPlatformFileDialogHelper() () at
/usr/lib64/qt5/plugins/platformthemes/KDEPlatformTheme.so
#13 0x7fec9ea942fa in
KdePlatformTheme::createPlatformDialogHelper(QPlatformTheme::DialogType) const
() at /usr/lib64/qt5/plugins/platformthemes/KDEPlatformTheme.so
#14 0x7fecb9aea1b5 in QDialogPrivate::platformHelper() const () at
/lib64/libQt5Widgets.so.5
#15 0x7fecb9afd958 in QFileDialogPrivate::init(QUrl const&, QString const&,
QString const&) () at /lib64/libQt5Widgets.so.5
#16 0x7fecb9afdc76 in QFileDialog::QFileDialog(QFileDialogArgs const&) ()
at /lib64/libQt5Widgets.so.5
#17 0x7fecb9afe22e in QFileDialog::getOpenFileUrls(QWidget*, QString
const&, QUrl const&, QString const&, QString*, QFlags,
QStringList const&) () at /lib64/libQt5Widgets.so.5
#18 0x7fecbe848918 in KateViewManager::slotDocumentOpen() () at
/lib64/libkdeinit5_kate.so
#19 0x7fecbe882695 in KateViewManager::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) () at /lib64/libkdeinit5_kate.so
#20 0x7fecb82df2ea in QMetaObject::activate(QObject*, int, int, void**) ()
at /lib64/libQt5Core.so.5
#21 0x7fecb98e67d2 in QAction::triggered(bool) () at
/lib64/libQt5Widgets.so.5
#22 0x7fecb98e8c58 in QAction::activate(QAction::ActionEvent) () at
/lib64/libQt5Widgets.so.5
#23 0x7fecb98e95af in QAction::event(QEvent*) () at
/lib64/libQt5Widgets.so.5
#24 0x7fecb98f041c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib64/libQt5Widgets.so.5
#25 0x7fecb98f58e6 in QApplication::notify(QObject*, QEvent*) () at
/lib64/libQt5Widgets.so.5
#26 0x7fecb82b077b in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /lib64/libQt5Core.so.5
#27 0x7fecb916f018 in QShortcutMap::dispatchEvent(QKeyEvent*) () at
/lib64/libQt5Gui.so.5
#28 0x7fecb916f151 in QShortcutMap::tryShortcutEvent(QObject*, QKeyEvent*)
() at /lib64/libQt5Gui.so.5
#29 0x7fecb9143a8a in
QGuiApplicationPrivate::processKeyEvent(QWindowSystemInterfacePrivate::KeyEvent*)
() at /lib64/libQt5Gui.so.5
#30 0x7fecb9148b95 in
QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*)
() at /lib64/libQt5Gui.so.5
#31 0x7fecb912c958 in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
() at /lib64/libQt5Gui.so.5
#32 0x7feca22ce0a0 in userEventSourceDispatch(_GSource*, int (*)(void*),
void*) () at /lib64/libQt5XcbQpa.so.5
#33 0x7fecb387be3a in g_main_context_dispatch () at /lib64/libglib-2.0.so.0
#34 0x7fecb387c1d0 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#35 0x7fecb

[plasmashell] [Bug 356821] New: Plasma shell crash after upgrade to openSUSE Leap 42.1

[Vadym Krevs via KDE Bugzilla]

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

Bug ID: 356821
   Summary: Plasma shell crash after upgrade to openSUSE Leap 42.1
   Product: plasmashell
   Version: 5.4.2
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: vkr...@yahoo.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.4.2)

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

-- Information about the crash:
- What I was doing when the application crashed:
Did a zypper dup upgrade to openSUSE Leap, rebooted, and attempted to login.
Plasmashell crashed.

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 0x7fc907857800 (LWP 2356))]

Thread 3 (Thread 0x7fc8efa57700 (LWP 2357)):
#0  0x7fc900dcac1d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7fc905cd0422 in  () at /usr/lib64/libxcb.so.1
#2  0x7fc905cd200f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7fc8f21d9c29 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7fc9014c155f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7fc9005d40a4 in start_thread (arg=0x7fc8efa57700) at
pthread_create.c:309
#6  0x7fc900dd304d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 2 (Thread 0x7fc8e7fff700 (LWP 2358)):
#0  0x7fc900dcac1d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7fc8fd4bbe64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fc8fd4bbf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fc9016f2a3c in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fc901699a63 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fc9014bc84a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fc90478c5f8 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7fc9014c155f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7fc9005d40a4 in start_thread (arg=0x7fc8e7fff700) at
pthread_create.c:309
#9  0x7fc900dd304d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7fc907857800 (LWP 2356)):
[KCrash Handler]
#6  0x7fc900d23187 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
#7  0x7fc900d24538 in __GI_abort () at abort.c:78
#8  0x7fc9014b077e in  () at /usr/lib64/libQt5Core.so.5
#9  0x7fc8f21f04c2 in QXcbWindow::create() () at
/usr/lib64/libQt5XcbQpa.so.5
#10 0x7fc8ee60a299 in  () at
/usr/lib64/qt5/plugins/xcbglintegrations/libqxcb-egl-integration.so
#11 0x7fc8f21dbb42 in QXcbIntegration::createPlatformWindow(QWindow*) const
() at /usr/lib64/libQt5XcbQpa.so.5
#12 0x7fc901bf29d5 in QWindowPrivate::create(bool) () at
/usr/lib64/libQt5Gui.so.5
#13 0x7fc901bf2c58 in QWindow::winId() const () at
/usr/lib64/libQt5Gui.so.5
#14 0x7fc90726544e in PlasmaQuick::Dialog::event(QEvent*) () at
/usr/lib64/libKF5PlasmaQuick.so.5
#15 0x7fc902a14e8c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQt5Widgets.so.5
#16 0x7fc902a19cd8 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#17 0x7fc90169bba5 in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /usr/lib64/libQt5Core.so.5
#18 0x7fc901bf2e42 in QWindow::setIcon(QIcon const&) () at
/usr/lib64/libQt5Gui.so.5
#19 0x7fc907264bf0 in PlasmaQuick::Dialog::Dialog(QQuickItem*) () at
/usr/lib64/libKF5PlasmaQuick.so.5
#20 0x7fc8e69bbee0 in  () at
/usr/lib64/qt5/qml/org/kde/plasma/core/libcorebindingsplugin.so
#21 0x7fc9047278a9 in QQmlType::create() const () at
/usr/lib64/libQt5Qml.so.5
#22 0x7fc9047860a4 in  () at /usr/lib64/libQt5Qml.so.5
#23 0x7fc9047867af in  () at /usr/lib64/libQt5Qml.so.5
#24 0x7fc904715fe7 in  () at /usr/lib64/libQt5Qml.so.5
#25 0x7fc90471684e in QQmlIncubationController::incubateFor(int) () at
/usr/lib64/libQt5Qml.so.5
#26 0x7fc90580b6dc in  () at /usr/lib64/libKF5Declarative.so.5
#27 0x7fc9047164e5 in QQmlEnginePrivate::incubate(QQmlIncubator&,
QQmlContextData*) () at /usr/lib64/libQt5Qml.so.5
#28 0x7fc904711e9c in QQmlComponent::create(QQmlIncubator&, QQmlContext*,
QQmlContext*) () at /usr/lib64/libQt5Qml.so.5
#29 0x7fc9057fad50 in
KDeclarative::QmlObject::completeInitialization(QHash
const&) () at /usr/lib64/libKF5Declarative.so.5
#30 0x7fc9057fadfc in  () at /usr/lib64/libKF5Declarative.so.5
#31 0x7fc9057fafb1 in  () at /usr/lib64/libKF5Declarative.so.5
#32 0x00465bdb in Osd::Osd(ShellCorona*) ()
#33 0x00458d46 in ShellCorona::ShellCorona(QObject*) ()
#34 0x00462099 in Shel

[drkonqi] [Bug 356822] New: Can not add similar issues

[sederic via KDE Bugzilla]

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

Bug ID: 356822
   Summary: Can not add similar issues
   Product: drkonqi
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: sebastian.end...@online.de

Sometimes I can't add similar issues to my issue, neither as the same issue
(append my new bug report as comment) nor as similar issue (link the issues).

Reproducible: Sometimes

Steps to Reproduce:
1. Fill in everything required field
2. Login to bugzilla in drkonqi
3. Select similar issues and click in "suggest as duplicate"

Actual Results:  
When clicking on "next" drkonqi complains that I didn't link any issues

Expected Results:  
drkonqi should link the issues I suggested as duplicate

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

[valgrind] [Bug 356823] New: Unsupported ARM instruction: stlex

[Роман Донченко via KDE Bugzilla]

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

Bug ID: 356823
   Summary: Unsupported ARM instruction: stlex
   Product: valgrind
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: vex
  Assignee: jsew...@acm.org
  Reporter: d...@corrigendum.ru

Note: this instruction is new to ARMv8.

Simple example:

$ cat test.c
int main() {
asm volatile("stlex r0, r1, [r2]");
}
$ gcc -marm -march=armv8-a test.c 
$ valgrind ./a.out
==28004== Memcheck, a memory error detector
==28004== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==28004== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==28004== Command: ./a.out
==28004== 
disInstr(arm): unhandled instruction: 0xE1820E91
 cond=14(0xE) 27:20=24(0x18) 4:4=1 3:0=1(0x1)
...


Reproducible: Always

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

[umbrello] [Bug 351525] Build failure

[Ralf Habacker via KDE Bugzilla]

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

Ralf Habacker  changed:

   What|Removed |Added

 Resolution|INVALID |---
 Ever confirmed|0   |1
 Status|RESOLVED|REOPENED

--- Comment #7 from Ralf Habacker  ---
After updating umbrello frameworks branch this issue is still present with
jenkis ci.
A local build with Qt 5.4 does not show this issue. 

I did a few tries to get the issue fixed

first http://commits.kde.org/umbrello/ce9c5fd6f0d018534fc3cb04f6391fe8959aff5d,
which shows on the next build an issue with Uml::Visibility::Enum, so I guessed
to fix the issues in a generic way by providing related top level toString()
functions here 
http://commits.kde.org/umbrello/132d4498dcc73b25f95045b8fa0d9daff22a3977.

But this fails too. Any idea how to fix ?

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

[yakuake] [Bug 354646] [heisenbug] Focus missing in tabs after unknown actions

[mva]

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

Vadim A. Misbakh-Soloviov (mva)  changed:

   What|Removed |Added

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

--- Comment #2 from Vadim A. Misbakh-Soloviov (mva)  ---
Yeah, looks like so.

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

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

[yakuake] [Bug 341330] Active terminal doesn't always gain focus correctly after opening the window

[mva]

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

Vadim A. Misbakh-Soloviov (mva)  changed:

   What|Removed |Added

 CC||k...@mva.name

--- Comment #6 from Vadim A. Misbakh-Soloviov (mva)  ---
*** Bug 354646 has been marked as a duplicate of this bug. ***

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

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

[David via KDE Bugzilla]

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

Bug ID: 356824
   Summary: When zooming in, canvas does not render.
   Product: krita
   Version: 2.9.9
  Platform: Other
   URL: http://i.imgur.com/Ny7I4ML.png
OS: MS Windows
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: usability
  Assignee: krita-bugs-n...@kde.org
  Reporter: diderotma...@gmail.com

While using the Intous 5 wacom tablet, after scrolling with the wacom wheel to
zoom in / out the canvas lags. It doesn't render the canvas' zoomed in state
until I either click something else on the desktop, or go over it with the
mouse cursor. 

Reproducible: Always

Steps to Reproduce:
1.Open new canvas with any size. 
2.Use wacom tablet wheel to zoom in/out

Actual Results:  
Unloaded/rendered canvas.

Expected Results:  
 Load/render the canvas as you're zooming in/out.

Computer Spec:
i7 4790k
16g Ram
SSD 120g
HD 1T
GTX 760 Nvidia 


This problem doesn't happen with other graphic applications (paint tool sai,
photoshop)

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

[kdevelop] [Bug 321939] Outputview does not support ANSI escape sequences (Clang warnings partially trunkated)

[Kevin Funk via KDE Bugzilla]

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

Kevin Funk  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/kdev
   ||platform/9991a24e3d543f0153
   ||80ce4f8c3d2dfca377aba4
   Version Fixed In||5.0
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #10 from Kevin Funk  ---
Git commit 9991a24e3d543f015380ce4f8c3d2dfca377aba4 by Kevin Funk.
Committed on 17/12/2015 at 11:58.
Pushed by kfunk into branch '5.0'.

OutputView: Filter ANSI sequences

Summary:
Hardcoding the filter function in the outputmodel for now.

Not making this a filter strategy on purpose, it doesn't fit into the
current architecture. Stripping ANSI sequences is merely a
QString->QString transformation, while the filtering strategies do a
QString->FilteredItem transformation.
Related: bug 113128
FIXED-IN: 5.0

Subscribers: apol, kdevelop-devel

Projects: #kdevelop

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

M  +15   -1outputview/outputmodel.cpp
M  +63   -0util/kdevstringhandler.cpp
M  +6-0util/kdevstringhandler.h
M  +19   -0util/tests/test_stringhandler.cpp
M  +2-0util/tests/test_stringhandler.h

http://commits.kde.org/kdevplatform/9991a24e3d543f015380ce4f8c3d2dfca377aba4

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

[kdevelop] [Bug 113128] use color codes in output messages

[Kevin Funk via KDE Bugzilla]

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

--- Comment #5 from Kevin Funk  ---
Git commit 9991a24e3d543f015380ce4f8c3d2dfca377aba4 by Kevin Funk.
Committed on 17/12/2015 at 11:58.
Pushed by kfunk into branch '5.0'.

OutputView: Filter ANSI sequences

Summary:
Hardcoding the filter function in the outputmodel for now.

Not making this a filter strategy on purpose, it doesn't fit into the
current architecture. Stripping ANSI sequences is merely a
QString->QString transformation, while the filtering strategies do a
QString->FilteredItem transformation.
Related: bug 321939
FIXED-IN: 5.0

Subscribers: apol, kdevelop-devel

Projects: #kdevelop

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

M  +15   -1outputview/outputmodel.cpp
M  +63   -0util/kdevstringhandler.cpp
M  +6-0util/kdevstringhandler.h
M  +19   -0util/tests/test_stringhandler.cpp
M  +2-0util/tests/test_stringhandler.h

http://commits.kde.org/kdevplatform/9991a24e3d543f015380ce4f8c3d2dfca377aba4

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

[kdenlive] [Bug 356151] Git master 2015-12-01 - Rendering project with embedded project files fails

[Evert Vorster via KDE Bugzilla]

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

Evert Vorster  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |REMIND

--- Comment #5 from Evert Vorster  ---
This is still an issue

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

[kdevelop] [Bug 350183] Support of $VARIABLE in environment settings

[Kevin Funk via KDE Bugzilla]

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

Kevin Funk  changed:

   What|Removed |Added

 CC||kf...@kde.org
 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED
   Keywords||junior-jobs

--- Comment #1 from Kevin Funk  ---
Definitely useful, I agree.

This should be relatively trivial to implement, wanna give it a try, Denis?

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

[kdevelop] [Bug 345043] Make it possible to select environment for the QMake builder process

[Kevin Funk via KDE Bugzilla]

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

Kevin Funk  changed:

   What|Removed |Added

   Keywords||junior-jobs

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

[kdevplatform] [Bug 356825] New: EnvironmentWidget: Support editing existing env

[Kevin Funk via KDE Bugzilla]

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

Bug ID: 356825
   Summary: EnvironmentWidget: Support editing existing env
   Product: kdevplatform
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: shell
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: kf...@kde.org

Right now there's just a batch mode for adding new entries.

In fact, this dialog should probably be turned into a "batch edit mode" dialog.

=> All existing key-value pairs should be inserted into the dialog, the user
can then freely modify them

Reproducible: Always

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

[kdevplatform] [Bug 356825] EnvironmentWidget: Support editing existing environment

[Kevin Funk via KDE Bugzilla]

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

Kevin Funk  changed:

   What|Removed |Added

Summary|EnvironmentWidget: Support  |EnvironmentWidget: Support
   |editing existing env|editing existing
   ||environment

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

[kdevplatform] [Bug 356825] EnvironmentWidget: Support editing existing environment

[Kevin Funk via KDE Bugzilla]

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

Kevin Funk  changed:

   What|Removed |Added

   Keywords||junior-jobs

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

[kdenlive] [Bug 351062] Git master 2015-08-07 - Massive memory leak on file loading.

[Evert Vorster via KDE Bugzilla]

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

Evert Vorster  changed:

   What|Removed |Added

 Resolution|--- |REMIND
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #3 from Evert Vorster  ---
I still hit this bug. 
It's a little worse for me now, as I run Kdenlive in a virtual machine on a
laptop, so I run out of memory a lot quicker. 

However, I was playing on a monster of a machine a little while ago that has
64Gb of RAM. I still managed to make Kdenlive crash because it ran out of
memory. 

I have a lot of 4K footage, and because it was taken with a GoPro, I end up
with several 3.7Gb files that I normally load sequentially. 

Unfortunately, Kdenlive does not release the memory of a loaded file, even when
the file is removed from the Project Bin. The only way to reclaim that memory
is to close the running instance of Kdenlive.

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

[kdevplatform] [Bug 356826] EnvironmentWidget: Support cloning existing environment

[Kevin Funk via KDE Bugzilla]

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

Kevin Funk  changed:

   What|Removed |Added

   Keywords||junior-jobs
 CC||kf...@kde.org

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

[kdevplatform] [Bug 356826] New: EnvironmentWidget: Support cloning existing environment

[Kevin Funk via KDE Bugzilla]

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

Bug ID: 356826
   Summary: EnvironmentWidget: Support cloning existing
environment
   Product: kdevplatform
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: shell
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: kf...@kde.org

Title says it all.

We should support cloning existing environments in the environment widget

Reproducible: Always

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

[frameworks-kidletime] [Bug 328987] Power saving should not trigger if joystick is in use

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #11 from Martin Gräßlin  ---
gamepad works, I see the events in the joystick kcm. Now the bad news: libinput
doesn't provide support for it, see [1]. Which means also on Wayland we don't
get the events into KIdleTime.

Now getting this into KIdleTime is tricky. We would need to add a second source
for checking idle and only consider the session as idle if both sources are
idle. Not an easy change. Even more we would need to move the monitoring of
joysticks into the applications, while monitoring of pointer/keyboard/touch is
inside the display server. All applications using KIdleTime would then get
woken up on each event. Not good. This needs serious thinking on how to
integrate it and will take time.

[1]
http://lists.freedesktop.org/archives/wayland-devel/2015-January/019462.html

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

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

[Boudewijn Rempt via KDE Bugzilla]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|UNCONFIRMED |NEEDSINFO
 CC||b...@valdyas.org

--- Comment #1 from Boudewijn Rempt  ---
Hi David,

This problem does not happen generally, as far as I know, so it must be
something peculiar to your system. * Does it also happen if you zoom in/out
with the mouse scrollwheel or the keyboard zoom shortcuts? 
* Do you have opengl enabled (and if so, is your driver the latest version?) 
* Does it also happen for you if you switch opengl on/off?

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

[kate] [Bug 356827] New: KWrite crashes when clicking "save as" on a blank file

[via KDE Bugzilla]

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

Bug ID: 356827
   Summary: KWrite crashes when clicking "save as" on a blank file
   Product: kate
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: kwrite
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: emele...@gmail.com

Application: kwrite (15.08.1)

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

-- Information about the crash:
- What I was doing when the application crashed:
Opened KWrite from the menu, wrote something, clicked "Save As", and KWrite
crashed

The crash can be reproduced every time.

-- Backtrace:
Application: KWrite (kwrite), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fb75a42e900 (LWP 2850))]

Thread 2 (Thread 0x7fb73b1e6700 (LWP 2851)):
#0  0x7fb753248ffd in poll () at /lib64/libc.so.6
#1  0x7fb74b886272 in _xcb_conn_wait () at /lib64/libxcb.so.1
#2  0x7fb74b887ee7 in xcb_wait_for_event () at /lib64/libxcb.so.1
#3  0x7fb73dbb2da9 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5
#4  0x7fb753e513ce in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#5  0x7fb750fa260a in start_thread () at /lib64/libpthread.so.0
#6  0x7fb753254a9d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7fb75a42e900 (LWP 2850)):
[KCrash Handler]
#5  0x7fb73dbc9f08 in QXcbWindow::setParent(QPlatformWindow const*) () at
/lib64/libQt5XcbQpa.so.5
#6  0x7fb754c388bb in QWindow::setParent(QWindow*) () at
/lib64/libQt5Gui.so.5
#7  0x7fb7554135d5 in QWidgetPrivate::setParent_sys(QWidget*,
QFlags) () at /lib64/libQt5Widgets.so.5
#8  0x7fb75541efda in QWidget::setParent(QWidget*, QFlags)
() at /lib64/libQt5Widgets.so.5
#9  0x7fb7554200cc in QWidget::setParent(QWidget*) () at
/lib64/libQt5Widgets.so.5
#10 0x7fb75550611c in QDialogButtonBox::addButton(QAbstractButton*,
QDialogButtonBox::ButtonRole) () at /lib64/libQt5Widgets.so.5
#11 0x7fb73a3b6e59 in KDEPlatformFileDialog::KDEPlatformFileDialog() () at
/usr/lib64/qt5/plugins/platformthemes/KDEPlatformTheme.so
#12 0x7fb73a3b7282 in
KDEPlatformFileDialogHelper::KDEPlatformFileDialogHelper() () at
/usr/lib64/qt5/plugins/platformthemes/KDEPlatformTheme.so
#13 0x7fb73a3aa2fa in
KdePlatformTheme::createPlatformDialogHelper(QPlatformTheme::DialogType) const
() at /usr/lib64/qt5/plugins/platformthemes/KDEPlatformTheme.so
#14 0x7fb7555d51b5 in QDialogPrivate::platformHelper() const () at
/lib64/libQt5Widgets.so.5
#15 0x7fb7555e8958 in QFileDialogPrivate::init(QUrl const&, QString const&,
QString const&) () at /lib64/libQt5Widgets.so.5
#16 0x7fb7555e8c76 in QFileDialog::QFileDialog(QFileDialogArgs const&) ()
at /lib64/libQt5Widgets.so.5
#17 0x7fb7555e974e in QFileDialog::getSaveFileUrl(QWidget*, QString const&,
QUrl const&, QString const&, QString*, QFlags, QStringList
const&) () at /lib64/libQt5Widgets.so.5
#18 0x7fb759b5dae3 in KTextEditor::DocumentPrivate::documentSaveAs() () at
/lib64/libKF5TextEditor.so.5
#19 0x7fb759d18c5e in
KTextEditor::DocumentPrivate::qt_static_metacall(QObject*, QMetaObject::Call,
int, void**) () at /lib64/libKF5TextEditor.so.5
#20 0x7fb7540612ea in QMetaObject::activate(QObject*, int, int, void**) ()
at /lib64/libQt5Core.so.5
#21 0x7fb7553d17d2 in QAction::triggered(bool) () at
/lib64/libQt5Widgets.so.5
#22 0x7fb7553d3c58 in QAction::activate(QAction::ActionEvent) () at
/lib64/libQt5Widgets.so.5
#23 0x7fb7554d9b80 in QAbstractButtonPrivate::click() () at
/lib64/libQt5Widgets.so.5
#24 0x7fb7554d9cb4 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) ()
at /lib64/libQt5Widgets.so.5
#25 0x7fb75559e96a in QToolButton::mouseReleaseEvent(QMouseEvent*) () at
/lib64/libQt5Widgets.so.5
#26 0x7fb75541e428 in QWidget::event(QEvent*) () at
/lib64/libQt5Widgets.so.5
#27 0x7fb75559ea49 in QToolButton::event(QEvent*) () at
/lib64/libQt5Widgets.so.5
#28 0x7fb7553db41c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib64/libQt5Widgets.so.5
#29 0x7fb7553e0fe9 in QApplication::notify(QObject*, QEvent*) () at
/lib64/libQt5Widgets.so.5
#30 0x7fb75403277b in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /lib64/libQt5Core.so.5
#31 0x7fb7553dfef2 in QApplicationPrivate::sendMouseEvent(QWidget*,
QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () at
/lib64/libQt5Widgets.so.5
#32 0x7fb75543898b in QWidgetWindow::handleMouseEvent(QMouseEvent*) () at
/lib64/libQt5Widgets.so.5
#33 0x7fb75543af4b in QWidgetWindow::event(QEvent*) () at
/lib64/libQt5Widgets.so.5
#34 0x7fb7553db41c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib64/libQt5Widgets.so.5
#35 0x0

[kdenlive] [Bug 355350] Online Resources/Freesound Download No Results

[Roger Morton via KDE Bugzilla]

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

--- Comment #7 from Roger Morton  ---
(In reply to qubodup from comment #6)
> Freesound seems to work. Thanks!
> 
> However, pressing a link (license for example) in the online resource
> interface appears to freeze the window and kdenlive.
> 
> [6874:6874:1207/005841:ERROR:sandbox_linux.cc(338)] InitializeSandbox()
> called with multiple threads in process gpu-process
> 
> Video: https://youtu.be/UQhi0qEYeHk

Can not reproduce this issue. Links open in whatever the system is set up for
reading html from.

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

[kscreenlocker] [Bug 356828] New: kscreenlocker_g crashes with SIGABRT, continually dumps core

[Robert Munteanu via KDE Bugzilla]

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

Bug ID: 356828
   Summary: kscreenlocker_g crashes with SIGABRT, continually
dumps core
   Product: kscreenlocker
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: robert.munte...@gmail.com
CC: bhus...@gmail.com, mgraess...@kde.org

Using plasma5-workspace-5.4.3-1.1.x86_64 on openSUSE Tumbleweed x86_64. When
trying to lock the screen the image freezes - no lock screen appears and I am
only able to move the mouse but not input anything.

Switching to another VT and running 'top' shows that I have 7-8 coredumpctl
processes running at the same time.

I'm running a W541 Lenovo Laptop using the Intel video card only - neither
nouveau nor the nvidia proprietary drivers are installed.

Reproducible: Always

Steps to Reproduce:
Try to lock the screen.



Here's a core dump summary from coredumpctl

   PID: 29049 (kscreenlocker_g)
   UID: 1000 (robert)
   GID: 100 (users)
Signal: 6 (ABRT)
 Timestamp: Thu 2015-12-17 14:21:36 EET (22min ago)
  Command Line: /usr/lib64/libexec/kscreenlocker_greet --immediateLock --ksldfd
52
Executable: /usr/lib64/libexec/kscreenlocker_greet
 Control Group: /user.slice/user-1000.slice/session-13.scope
  Unit: session-13.scope
 Slice: user-1000.slice
   Session: 13
 Owner UID: 1000 (robert)
   Boot ID: fa49e85f2ebf4f31b00f5e04300e9e6d
Machine ID: 87f0790206514af7a87d17a290547703
  Hostname: rombert.corp.adobe.com
  Coredump:
/var/lib/systemd/coredump/core.kscreenlocker_g.1000.fa49e85f2ebf4f31b00f5e04300e9e6d.29049.145035489600.xz
   Message: Process 29049 (kscreenlocker_g) of user 1000 dumped core.

The gdb backtrace shows

#0  0x7f3e830e8d38 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:55
#1  0x7f3e830ea18a in __GI_abort () at abort.c:78
#2  0x7f3e8387482e in qt_message_fatal (context=..., message=) at global/qlogging.cpp:1578
#3  QMessageLogger::fatal (this=this@entry=0x7fffa1142d60,
msg=msg@entry=0x7f3e72e093e8 "QXcbConnection: Could not connect to display %s")
at global/qlogging.cpp:781
#4  0x7f3e72d93ad0 in QXcbConnection::QXcbConnection (this=0x237a920,
nativeInterface=0x2374420, canGrabServer=,
defaultVisualId=, displayName=0x0) at qxcbconnection.cpp:511
#5  0x7f3e72d99125 in QXcbIntegration::QXcbIntegration (this=, parameters=..., argc=@0x7fffa11431fc: 4, argv=0x7fffa11434e8) at
qxcbintegration.cpp:177
#6  0x7f3e7306e4cd in QXcbIntegrationPlugin::create (this=,
system=..., parameters=..., argc=@0x7fffa11431fc: 4, argv=0x7fffa11434e8) at
qxcbmain.cpp:50
#7  0x7f3e83f8a1d2 in loadIntegration (argv=0x7fffa11434e8,
argc=@0x7fffa11431fc: 4, parameters=..., key=..., loader=0x7f3e845d4bf0
<_ZZN12_GLOBAL__N_112Q_QGS_loader13innerFunctionEvE6holder>) at
kernel/qplatformintegrationfactory.cpp:56
#8  QPlatformIntegrationFactory::create (platform=..., paramList=...,
argc=@0x7fffa11431fc: 4, argv=argv@entry=0x7fffa11434e8,
platformPluginPath=...) at kernel/qplatformintegrationfactory.cpp:73
#9  0x7f3e83f956d2 in init_platform (argv=0x7fffa11434e8, argc=, platformThemeName=..., platformPluginPath=..., pluginArgument=...) at
kernel/qguiapplication.cpp:1019
#10 QGuiApplicationPrivate::createPlatformIntegration (this=0x236c730) at
kernel/qguiapplication.cpp:1176
#11 0x7f3e83f965dd in QGuiApplicationPrivate::createEventDispatcher
(this=) at kernel/qguiapplication.cpp:1193
#12 0x7f3e83a5bfc6 in QCoreApplication::init
(this=this@entry=0x7fffa11432b0) at kernel/qcoreapplication.cpp:768
#13 0x7f3e83a5c026 in QCoreApplication::QCoreApplication
(this=0x7fffa11432b0, p=...) at kernel/qcoreapplication.cpp:689
#14 0x7f3e83f9811d in QGuiApplication::QGuiApplication
(this=0x7fffa11432b0, argc=@0x7fffa11431fc: 4, argv=0x7fffa11434e8,
flags=328961) at kernel/qguiapplication.cpp:558
#15 0x004136f5 in ScreenLocker::UnlockApp::UnlockApp
(this=0x7fffa11432b0, argc=, argv=) at
/usr/src/debug/plasma-workspace-5.4.3/ksmserver/screenlocker/greeter/greeterapp.cpp:80
#16 0x0040dd43 in main (argc=4, argv=0x7fffa11434e8) at
/usr/src/debug/plasma-workspace-5.4.3/ksmserver/screenlocker/greeter/main.cpp:58

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

[kate] [Bug 356829] New: kate processes keeps running after closing

[Alfredo via KDE Bugzilla]

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

Bug ID: 356829
   Summary: kate processes keeps running after closing
   Product: kate
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: sessions
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: in...@bibuweb.de

after closing kate the processes keeps running in the background.
Result is, when you closed your first session, kate doesn't open a second,
third, ... GUI session but opens backend sessions.
After login again with a new kwin session, all the kate session are restored to
the frontend.

Reproducible: Always

Steps to Reproduce:
1. open kate
2. close kate
3. ps -ef | grep kate
you will see the open kate session(s)



Kate
 Version 15.08.3
KDE Frameworks 5.17.0
Qt 5.5.0 (kompiliert gegen 5.5.0)
Das xcb Fenstersystem

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

[dolphin] [Bug 356830] New: Invalid location in location bar (button mode) when browsing FTP

[Max via KDE Bugzilla]

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

Bug ID: 356830
   Summary: Invalid location in location bar (button mode) when
browsing FTP
   Product: dolphin
   Version: 15.08.1
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: bars: location
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: thesource...@gmail.com

When I descend into directory tree of FTP server, all entries in location bar
after server name become the same and display the name of current folder, so if
I'm in myproject/images, location bar displays images / images. Pressing any of
those entries does nothing. This only happens in "button" mode of the bar. If I
click aside of location buttons to switch to string mode, than the location is
displayed properly.

Reproducible: Always

Steps to Reproduce:
1. Logon to any FTP server
2. Descend at least 2 directories down the tree
3.

Actual Results:  
All buttons on location bar display same names, clicking on them does nothing.

Expected Results:  
Buttons should properly display names of all folders in current tree branch,
clicking on the button should change directory.

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

[kate] [Bug 356827] KWrite crashes when clicking "save as" on a blank file

[Kåre Särs via KDE Bugzilla]

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

Kåre Särs  changed:

   What|Removed |Added

 CC||kare.s...@iki.fi
 Resolution|--- |WAITINGFORINFO
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #1 from Kåre Särs  ---
Are you by chance using Compiz as window manager? 

There seems to be a problem with Compiz and KDE applications at the moment:

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

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

[kate] [Bug 356820] Open Filename in Kate causes crash

[Kåre Särs via KDE Bugzilla]

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

Kåre Särs  changed:

   What|Removed |Added

 CC||kare.s...@iki.fi

--- Comment #1 from Kåre Särs  ---
Are you by chance using Compiz as window manager? 

There seems to be a problem with Compiz and KDE applications at the moment:

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

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

[kate] [Bug 356786] KWrite crashes attempting Open, from menu or toolbar.

[Kåre Särs via KDE Bugzilla]

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

Kåre Särs  changed:

   What|Removed |Added

 CC||kare.s...@iki.fi
 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #1 from Kåre Särs  ---
Are you by chance using Compiz as window manager? 

There seems to be a problem with Compiz and KDE applications at the moment:

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

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

[kate] [Bug 356735] Kate crashes on Open toolbar button click

[Kåre Särs via KDE Bugzilla]

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

Kåre Särs  changed:

   What|Removed |Added

 CC||kare.s...@iki.fi
 Resolution|--- |WAITINGFORINFO
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #2 from Kåre Särs  ---
Are you by chance using Compiz as window manager? 

There seems to be a problem with Compiz and KDE applications at the moment:

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

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

[kmines] [Bug 356811] Kmines number indicators are incorrect.

[Alex Zaballa via KDE Bugzilla]

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

--- Comment #2 from Alex Zaballa  ---
Created attachment 96141
  --> https://bugs.kde.org/attachment.cgi?id=96141&action=edit
Numbering bug visible in upper left quadrant.

Sorry about not attaching it directly. Here you go.

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

[kscreenlocker] [Bug 356828] kscreenlocker_g crashes with SIGABRT, continually dumps core

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #1 from Martin Gräßlin  ---
are all backtraces like that? Question is whether the first crash looks the
same, because
"QXcbConnection: Could not connect to display" doesn't make any sense. Why
should it not be able to connect to the XDisplay?

Unrelated to that: you should never get more than 4 crashers and afterwards an
error message should be shown telling you how to unlock the screen. On second
thought: that might be new in 5.5

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

[Spectacle] [Bug 356831] New: cannot send image to clipboard in background mode

[dantmnf via KDE Bugzilla]

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

Bug ID: 356831
   Summary: cannot send image to clipboard in background mode
   Product: Spectacle
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: m...@baloneygeek.com
  Reporter: dantmnf2+kdeb...@gmail.com

When I launch Spectacle with "--background --clipboard", it won't send the
captured image to clipboard, but save it to disk and send a notification.

Reproducible: Always

Steps to Reproduce:
1. open a terminal
2. launch `spectacle --background --clipboard --fullscreen`
3. check clipboard and default save directory of Spectacle

Actual Results:  
$ spectacle --background --clipboard --fullscreen
"Copied image to clipboard"
--
Desktop notification: A new screenshot was captured and saved to /blah/blah
--
Nothing happens to clipboard.

Expected Results:  
The captured image should be in clipboard.
Related notifications or nothing should be shown.

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

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

[David via KDE Bugzilla]

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

--- Comment #2 from David  ---
When I use the mouse alone it doesn't happen as bad. You can notice some
render delay but it's hardly noticeable. It happens mainly with my wacom.
Open GL is enabled.  Version 4.5. It still happens when I switch opengl
on/off.

This
email has been sent from a virus-free computer protected by Avast.
www.avast.com

<#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

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

> https://bugs.kde.org/show_bug.cgi?id=356824
>
> Boudewijn Rempt  changed:
>
>What|Removed |Added
>
> 
>  Resolution|--- |WAITINGFORINFO
>  Status|UNCONFIRMED |NEEDSINFO
>  CC||b...@valdyas.org
>
> --- Comment #1 from Boudewijn Rempt  ---
> Hi David,
>
> This problem does not happen generally, as far as I know, so it must be
> something peculiar to your system. * Does it also happen if you zoom in/out
> with the mouse scrollwheel or the keyboard zoom shortcuts?
> * Do you have opengl enabled (and if so, is your driver the latest
> version?)
> * Does it also happen for you if you switch opengl on/off?
>
> --
> You are receiving this mail because:
> You reported the bug.
>

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

[kscreenlocker] [Bug 356828] kscreenlocker_g crashes with SIGABRT, continually dumps core

[Robert Munteanu via KDE Bugzilla]

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

--- Comment #2 from Robert Munteanu  ---
> Question is whether the first crash looks the same

Yes, I just checked the first one for today and it has the same message.

> Unrelated to that: you should never get more than 4 crashers and afterwards 
> an error message should be shown telling you how to unlock the screen. On 
> second thought: that might be new in 5.5

It might be new in 5.5, I don't get this behaviour and I have > 50 dumps for
today

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

[okular] [Bug 173896] Sent-to menu entry or send-via-email menu-entry

[Rok via KDE Bugzilla]

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

--- Comment #21 from Rok  ---
I have an idea. Is it possible to implement KIO slave protocol for sending
mail? You will choose SaveAs in any application and forward this to kmail or
anything else...

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

[plasmashell] [Bug 356821] Plasma shell crash after upgrade to openSUSE Leap 42.1

[David Edmundson via KDE Bugzilla]

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

--- Comment #1 from David Edmundson  ---
It'll be your graphic drivers not being set up properly.

-- 
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||vkr...@yahoo.com

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

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

[plasmashell] [Bug 356821] Plasma shell crash after upgrade to openSUSE Leap 42.1

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

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

--- Comment #2 from David Edmundson  ---


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

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

[plasmashell] [Bug 353426] plasma disappears when using multiple monitors

[Phil Schaf via KDE Bugzilla]

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

Phil Schaf  changed:

   What|Removed |Added

 CC||flying-sh...@web.de

--- Comment #7 from Phil Schaf  ---
i have similar problems, although for me, it simply gets into a silly state
where maximized windows end up behind the panel.

i work around it by having "pkill plasmashell; plasmashell" in my KRunner
history

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

[kate] [Bug 356735] Kate crashes on Open toolbar button click

[Jason Elwell via KDE Bugzilla]

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

--- Comment #3 from Jason Elwell  ---
It looks like compiz is _not_ running, but kwin is running (see below).  I _do_
have the default Desktop Effects enabled.  Let me know if that answers your
question properly.  

Also, there were a ton of kf5-5.17 updates this morning.  I'd be happy to try
any work-arounds you might recommend.  

$ ps aux |grep -E 'compiz|kwin' |grep -v grep
user   2751  3.5  0.6 3166104 101660 ?  Sl   06:50   1:15 kwin_x11

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

[telepathy] [Bug 307990] Auto join jabber conference rooms

[Piotr Dobrogost via KDE Bugzilla]

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

Piotr Dobrogost  changed:

   What|Removed |Added

 CC||p...@bugs.kde.dobrogost.net

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

[telepathy] [Bug 307990] Auto join jabber conference rooms

[Piotr Dobrogost via KDE Bugzilla]

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

--- Comment #14 from Piotr Dobrogost  ---
It seems people had problem getting this feature in Kopete, too – Bug 65803 -
stay in a chat even when no window is open
(https://bugs.kde.org/show_bug.cgi?id=65803).

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

[kate] [Bug 356735] Kate crashes on Open toolbar button click

[Kåre Särs via KDE Bugzilla]

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

--- Comment #4 from Kåre Särs  ---
Can you install debug packages and produce a dump that has more info?

debug packages for: Kate, Frameworks integration (KDEPlatformTheme.so) and Qt

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

[plasma-nm] [Bug 353290] Applet incorrect active connections and broken dis/connect

[Jan Grulich via KDE Bugzilla]

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

Jan Grulich  changed:

   What|Removed |Added

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

--- Comment #3 from Jan Grulich  ---
Closing, there won't be any new release of plasma-nm for KDE 4. Switch please
to Plasma 5 and re-open this bug if your problem persists.

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

[plasma-nm] [Bug 335585] DSL connection does not work

[Jan Grulich via KDE Bugzilla]

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

Jan Grulich  changed:

   What|Removed |Added

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

--- Comment #14 from Jan Grulich  ---
Closing, there won't be any new release of plasma-nm for KDE 4. Switch please
to Plasma 5 and re-open this bug if your problem persists.

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

[plasma-nm] [Bug 333905] wpa key is not displayed

[Jan Grulich via KDE Bugzilla]

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

Jan Grulich  changed:

   What|Removed |Added

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

--- Comment #37 from Jan Grulich  ---
Closing, there won't be any new release of plasma-nm for KDE 4. Switch please
to Plasma 5 and re-open this bug if your problem persists.

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

[kdenlive] [Bug 355350] Online Resources/Freesound Download No Results

[via KDE Bugzilla]

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

qubo...@gmail.com changed:

   What|Removed |Added

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

--- Comment #8 from qubo...@gmail.com ---
you're right. my issue was unrelated to kdenlive. marking as fixed.

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

[digikam] [Bug 355831] MySQL Schema Improvements

[Richard Mortimer via KDE Bugzilla]

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

--- Comment #60 from Richard Mortimer  ---
Gilles,

Many thanks for the information and the testing feedback. I have not had much
time to look into this yet. 

A quick look at the schema does indicate that there is a missing UNIQUE clause
in the Tags table definition for MySQL. I do not think that is the full
solution but it will certainly stop duplicate entries reaching the database.

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

[kdenlive] [Bug 356803] Shortcut keys stop working in fullscreen

[Peter via KDE Bugzilla]

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

--- Comment #1 from Peter  ---
This was in 15.12

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

[plasmashell] [Bug 356832] New: Plasma crashed when I try to use settings for Activities

[Piotr Mierzwinski via KDE Bugzilla]

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

Bug ID: 356832
   Summary: Plasma crashed when I try to use settings for
Activities
   Product: plasmashell
   Version: 5.5.1
  Platform: Mageia RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: piotr.mierzwin...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.1)

Qt Version: 5.5.1
Operating System: Linux 4.3.2-desktop-2.mga6 x86_64
Distribution: "Mageia 6"

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

1. Right Mouse Button on desktop
2. Select Activities
3. In left edge I have only one scaled empty desktop. When I move mouse pointer
over it then I can see on bottom of it yellow/green bar
4. click settings icon localized on above bar
Plasma crashed

Plasma ver.5.1.1

The crash can be reproduced every time.

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

Thread 9 (Thread 0x7f7145d00700 (LWP 8983)):
#0  0x7f7154bdbdbd in poll () at /lib64/libc.so.6
#1  0x7f7158c64ac2 in _xcb_conn_wait () at /lib64/libxcb.so.1
#2  0x7f7158c66697 in xcb_wait_for_event () at /lib64/libxcb.so.1
#3  0x7f7147e27cc9 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5
#4  0x7f71552c601f in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#5  0x7f71543d865d in start_thread () at /lib64/libpthread.so.0
#6  0x7f7154be7bfd in clone () at /lib64/libc.so.6

Thread 8 (Thread 0x7f713f3ea700 (LWP 8991)):
#0  0x7f7151e43d03 in g_main_context_query () at /lib64/libglib-2.0.so.0
#1  0x7f7151e443af in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7f7151e4453c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7f71554e992b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7f715549380a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7f71552c11bc in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7f7157b4dcd5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5
#7  0x7f71552c601f in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7f71543d865d in start_thread () at /lib64/libpthread.so.0
#9  0x7f7154be7bfd in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7f7136b84700 (LWP 8998)):
#0  0x7f7151e87a99 in g_mutex_lock () at /lib64/libglib-2.0.so.0
#1  0x7f7151e435e4 in g_main_context_release () at /lib64/libglib-2.0.so.0
#2  0x7f7151e443ee in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#3  0x7f7151e4453c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#4  0x7f71554e992b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#5  0x7f715549380a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#6  0x7f71552c11bc in QThread::exec() () at /lib64/libQt5Core.so.5
#7  0x7f7157b4dcd5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5
#8  0x7f71552c601f in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#9  0x7f71543d865d in start_thread () at /lib64/libpthread.so.0
#10 0x7f7154be7bfd in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7f7135426700 (LWP 8999)):
#0  0x7f7154bd76dd in read () at /lib64/libc.so.6
#1  0x7f7151e867d0 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0
#2  0x7f7151e43f64 in g_main_context_check () at /lib64/libglib-2.0.so.0
#3  0x7f7151e443d8 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#4  0x7f7151e4453c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#5  0x7f71554e992b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#6  0x7f715549380a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#7  0x7f71552c11bc in QThread::exec() () at /lib64/libQt5Core.so.5
#8  0x7f7157b4dcd5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5
#9  0x7f71552c601f in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#10 0x7f71543d865d in start_thread () at /lib64/libpthread.so.0
#11 0x7f7154be7bfd in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7f712f3a7700 (LWP 9000)):
#0  0x7f71543ddc3f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f7159ee0fd4 in QTWTF::TCMalloc_PageHeap::scavengerThread() () at
/lib64/libQt5Script.so.5
#2  0x7f7159ee1019 in  () at /lib64/libQt5Script.so.5
#3  0x7f71543d865d in start_thread () at /lib64/libpthread.so.0
#4  0x7f7154be7bfd in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f712c833700 (LWP 9001)):
#0  0x7f7154bd76dd in read () at /lib64/libc.

[kate] [Bug 356735] Kate crashes on Open toolbar button click

[Jason Elwell via KDE Bugzilla]

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

--- Comment #5 from Jason Elwell  ---
Via drkonqi

Backtrace of the crash I experienced:

Application: Kate (kate), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
84T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[Current thread is 1 (Thread 0x7fa074459900 (LWP 29659))]

Thread 3 (Thread 0x7fa05513d700 (LWP 29660)):
#0  0x7fa06cd34ffd in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fa069c49272 in _xcb_conn_wait (__timeout=-1, __nfds=1,
__fds=0x7fa05513cbc0) at /usr/include/bits/poll2.h:46
#2  0x7fa069c49272 in _xcb_conn_wait (c=c@entry=0x5612ce8370e0,
cond=cond@entry=0x5612ce837120, vector=vector@entry=0x0, count=count@entry=0x0)
at xcb_conn.c:459
#3  0x7fa069c4aee7 in xcb_wait_for_event (c=0x5612ce8370e0) at xcb_in.c:693
#4  0x7fa057b09da9 in QXcbEventReader::run() (this=0x5612ce84a130) at
qxcbconnection.cpp:1254
#5  0x7fa06d93d3ce in QThreadPrivate::start(void*) (arg=0x5612ce84a130) at
thread/qthread_unix.cpp:331
#6  0x7fa06aef960a in start_thread (arg=0x7fa05513d700) at
pthread_create.c:334
#7  0x7fa06cd40a9d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7fa046f47700 (LWP 29661)):
#0  0x7fa06aefeb10 in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fa04a7fc2fa in radeon_drm_cs_emit_ioctl (mtx=0x5612cf00ab28,
cond=0x5612cf00ab50) at ../../../../../include/c11/threads_posix.h:154
#2  0x7fa04a7fc2fa in radeon_drm_cs_emit_ioctl (sema=0x5612cf00ab28) at
../../../../../src/gallium/auxiliary/os/os_thread.h:259
#3  0x7fa04a7fc2fa in radeon_drm_cs_emit_ioctl
(param=param@entry=0x5612cf00a7e0) at radeon_drm_winsys.c:644
#4  0x7fa04a7fba37 in impl_thrd_routine (p=) at
../../../../../include/c11/threads_posix.h:87
#5  0x7fa06aef960a in start_thread (arg=0x7fa046f47700) at
pthread_create.c:334
#6  0x7fa06cd40a9d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7fa074459900 (LWP 29659)):
[KCrash Handler]
#5  0x7fa057b20f08 in QXcbWindow::setParent(QPlatformWindow const*)
(this=0x5612cf3c5840, parent=0x0) at qxcbwindow.cpp:1499
#6  0x7fa06e9be8bb in QWindow::setParent(QWindow*) (this=0x5612cf3d7340,
parent=parent@entry=0x5612cf3bb790) at kernel/qwindow.cpp:614
#7  0x7fa06f1995d5 in QWidgetPrivate::setParent_sys(QWidget*,
QFlags) (this=this@entry=0x5612cf65f2b0,
newparent=newparent@entry=0x5612cf8269c0, f=...) at kernel/qwidget.cpp:10543
#8  0x7fa06f1a4fda in QWidget::setParent(QWidget*, QFlags)
(this=this@entry=0x5612cf335ab0, parent=parent@entry=0x5612cf8269c0, f=...) at
kernel/qwidget.cpp:10398
#9  0x7fa06f1a60cc in QWidget::setParent(QWidget*)
(this=this@entry=0x5612cf335ab0, parent=parent@entry=0x5612cf8269c0) at
kernel/qwidget.cpp:10334
#10 0x7fa06f28c11c in QDialogButtonBox::addButton(QAbstractButton*,
QDialogButtonBox::ButtonRole) (this=0x5612cf8269c0, button=0x5612cf335ab0,
role=QDialogButtonBox::AcceptRole) at widgets/qdialogbuttonbox.cpp:761
#11 0x7fa05430cde9 in KDEPlatformFileDialog::KDEPlatformFileDialog() () at
/usr/lib64/qt5/plugins/platformthemes/KDEPlatformTheme.so
#12 0x7fa05430d212 in
KDEPlatformFileDialogHelper::KDEPlatformFileDialogHelper() () at
/usr/lib64/qt5/plugins/platformthemes/KDEPlatformTheme.so
#13 0x7fa05430035a in
KdePlatformTheme::createPlatformDialogHelper(QPlatformTheme::DialogType) const
() at /usr/lib64/qt5/plugins/platformthemes/KDEPlatformTheme.so
#14 0x7fa06f35b1b5 in QDialogPrivate::platformHelper() const
(this=this@entry=0x5612cf6596e0) at dialogs/qdialog.cpp:94
#15 0x7fa06f36e958 in QFileDialogPrivate::init(QUrl const&, QString const&,
QString const&) (this=0x5612cf6596e0) at dialogs/qfiledialog_p.h:112
#16 0x7fa06f36e958 in QFileDialogPrivate::init(QUrl const&, QString const&,
QString const&) (this=0x5612cf6596e0, directory=..., nameFilter=...,
caption=...) at dialogs/qfiledialog.cpp:2771
#17 0x7fa06f36ec76 in QFileDialog::QFileDialog(QFileDialogArgs const&)
(this=0x7ffe07428130, args=...) at dialogs/qfiledialog.cpp:379
#18 0x7fa06f36f22e in QFileDialog::getOpenFileUrls(QWidget*, QString
const&, QUrl const&, QString const&, QString*, QFlags,
QStringList const&) (parent=0x5612ceb3c010, caption=..., dir=..., filter=...,
selectedFilter=0x0, options=..., supportedSchemes=...) at
dialogs/qfiledialog.cpp:2243
#19 0x7fa0740e6898 in KateViewManager::slotDocumentOpen() () at
/lib64/libkdeinit5_kate.so
#20 0x7fa0741205f5 in KateViewManager::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) () at /lib64/libkdeinit5_kate.so
#21 0x7fa06db4d2ea in QMetaObject::activate(QObject*, int, int, void**)
(sender=sender@entry=0x5612cec89080, signalOffset=,
local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffe07428460)
at kernel/qobject.cpp:3713
#22 0x7fa06db4dae7 in QMetaObject::activate(QObject*, QMetaObject const*,

[plasmashell] [Bug 350060] Device notification and use

[Christian González via KDE Bugzilla]

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

Christian González  changed:

   What|Removed |Added

 CC||chgonzal...@gmail.com

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

[kscreenlocker] [Bug 356828] kscreenlocker_g crashes with SIGABRT, continually dumps core

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #3 from Martin Gräßlin  ---
> It might be new in 5.5, I don't get this behaviour and I have > 50 dumps for 
> today

sorry about that :-( Positive: it shows that the investment in ensuring that
doesn't happen was worth the effort.

Could you please try to manually start 
/usr/lib64/libexec/kscreenlocker_greet --testing

The question for me is whether that will also abort.

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

[plasma-nm] [Bug 350188] When trying to connect via plasma-nm to a openconnect - connection, the dialog starts flickering until i hit enter -> then crash

[Jan Grulich via KDE Bugzilla]

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

--- Comment #4 from Jan Grulich  ---
Is this still reproducible with latest Plasma 5.5.1 release? Having this
version is important as there are most recent Openconnect fixes.

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

[kscreenlocker] [Bug 356828] kscreenlocker_g crashes with SIGABRT, continually dumps core

[Robert Munteanu via KDE Bugzilla]

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

--- Comment #4 from Robert Munteanu  ---
(In reply to Martin Gräßlin from comment #3)
> > It might be new in 5.5, I don't get this behaviour and I have > 50 dumps 
> > for today
> 
> sorry about that :-( Positive: it shows that the investment in ensuring that
> doesn't happen was worth the effort.
> 
> Could you please try to manually start 
> /usr/lib64/libexec/kscreenlocker_greet --testing
> 
> The question for me is whether that will also abort.

I will try do that. However I need to wait for the crash to happen again, and
then I'll only be able to run this from another VT.

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

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

[Martin Gräßlin via KDE Bugzilla]

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

Bug ID: 356833
   Summary: Ctrl+C doesn't work on Wayland
   Product: konsole
   Version: master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: keyboard
  Assignee: konsole-de...@kde.org
  Reporter: mgraess...@kde.org

All ctrl + key shortcuts do not work when running under Wayland.

Reproducible: Always

Steps to Reproduce:
1. Start a Wayland compositor (kwin_wayland or Weston)
2. Run konsole --platform wayland
3. start an application in konsole
4. Try to use Ctrl+c

Actual Results:  
c printed into terminal window

Expected Results:  
application terminates

-- 
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

[Bhushan Shah via KDE Bugzilla]

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

Bhushan Shah  changed:

   What|Removed |Added

 CC||mgraess...@kde.org

--- Comment #3 from Bhushan Shah  ---
*** Bug 356833 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

[Bhushan Shah via KDE Bugzilla]

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

Bhushan Shah  changed:

   What|Removed |Added

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

--- Comment #1 from Bhushan Shah  ---


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

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

[kate] [Bug 354494] Project plugin does not load Git repos anymore

[Mathieu Jobin via KDE Bugzilla]

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

Mathieu Jobin  changed:

   What|Removed |Added

 CC||opensou...@somekool.net

--- Comment #5 from Mathieu Jobin  ---
I'm not sure when this patch should have been deployed. I have this bug for a
while now, on both Kubuntu and ArchLinux

I am still experiencing this issue as of kate 15.08.3-3

I have everything upgraded to the latest available, 5.17 and 5.5.1 and 15.08.3

thanks

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

[kwin] [Bug 353983] Turning off compositing breaks Plasma panel rendering

[Christian González via KDE Bugzilla]

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

Christian González  changed:

   What|Removed |Added

 CC||chgonzal...@gmail.com

-- 
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.

[Joost VandeVondele via KDE Bugzilla]

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

--- Comment #3 from Joost VandeVondele  ---
just happened again, but it is really rare. (this is a 12 core server running
valgrind +-12h a day... and this seems to happen every +- 10 days). Is any of
the suggestions mentioned above possible without runtime overhead and excessive
IO ?

==25277== Memcheck, a memory error detector
==25277== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==25277== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==25277== Command:
/data/schuetto/auto_regtesting/regtests/cp2k/exe/local_valgrind/cp2k.pdbg
Pa.inp
==25277== 
blockSane: fail -- redzone-hi

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

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

[plasma-pa] [Bug 355129] Can't change PA sink in plasma-pa volume controller

[Christian González via KDE Bugzilla]

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

Christian González  changed:

   What|Removed |Added

 CC||chgonzal...@gmail.com

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

[plasmashell] [Bug 353962] initial login, systray applets odd, all enabled, cannot configure

[Christian González via KDE Bugzilla]

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

Christian González  changed:

   What|Removed |Added

 CC||chgonzal...@gmail.com

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

[kate] [Bug 356615] Projects plugin 15.08.3: file context menu only shows two items (git items missing)

[Mathieu Jobin via KDE Bugzilla]

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

Mathieu Jobin  changed:

   What|Removed |Added

 CC||opensou...@somekool.net

--- Comment #1 from Mathieu Jobin  ---
does it list project files from the git repos for you ?

this problem might be related to this other item

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

which has been closed, but it is not fixed for me.

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

[kate] [Bug 355827] Kate Project not loading project tree

[Mathieu Jobin via KDE Bugzilla]

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

Mathieu Jobin  changed:

   What|Removed |Added

 CC||opensou...@somekool.net

--- Comment #3 from Mathieu Jobin  ---
15.12 ? oh, thanks, looking forward to it ...

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

[kate] [Bug 354494] Project plugin does not load Git repos anymore

[Mathieu Jobin via KDE Bugzilla]

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

--- Comment #6 from Mathieu Jobin  ---
as per this bug, this should be shipped as part of 15.12 release

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

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

[kscreenlocker] [Bug 356828] kscreenlocker_g crashes with SIGABRT, continually dumps core

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #5 from Martin Gräßlin  ---
No need to wait for the crash to happen again. Just run it from a konsole in
your X session.

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

[kscreenlocker] [Bug 356828] kscreenlocker_g crashes with SIGABRT, continually dumps core

[Robert Munteanu via KDE Bugzilla]

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

--- Comment #6 from Robert Munteanu  ---
(In reply to Martin Gräßlin from comment #5)
> No need to wait for the crash to happen again. Just run it from a konsole in
> your X session.

Yes, it worked. However, locking the screen also worked fine after the last
restart.

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

[plasmashell] [Bug 356834] New: Systray popup has fixed size and can't show more than 8 items

[Christian González via KDE Bugzilla]

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

Bug ID: 356834
   Summary: Systray popup has fixed size and can't show more than
8 items
   Product: plasmashell
   Version: 5.4.3
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: System Tray
  Assignee: plasma-b...@kde.org
  Reporter: chgonzal...@gmail.com

Currently systray popup has a fixed size (can't be resized). If the number of
hidden items in systray is greater than 8, all the items over the 8th aren't
show in the popup and can't be accessed.

Reproducible: Always

Steps to Reproduce:
1. Open systray config dialog.
2. Set 8 or more plasmoids or apps to "hidden".
3. Open systray popup.

Actual Results:  
All items over the 8th are not visible.

Expected Results:  
Either the popup is resized to show all items or a scroll apperas in the popup.

I've discovered this problem after almost 1 hour trying to make plasma-nm to
show on the systray popup. Finally I've realized than the icon always was there
but can't be accessed until I remove other items from the popup. So this bug
can potentially leave people confused about essential parts of the desktop
(networking, bluetooth, removable devices, etc.).

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

[systemsettings] [Bug 356835] New: System settings crash after changing style to Oxygen

[via KDE Bugzilla]

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

Bug ID: 356835
   Summary: System settings crash after changing style to Oxygen
   Product: systemsettings
   Version: 5.5.1
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: opensuse.lietuviu.ka...@gmail.com

Application: systemsettings5 (5.5.1)

Qt Version: 5.5.0
Operating System: Linux 4.1.13-5-default x86_64
Distribution (Platform): openSUSE RPMs

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

System settings crash after changing style to Oxygen. But before that I did
various other changes in appearence in System settings

-- Backtrace:
Application: Sistemos nustatymai (systemsettings5), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fb917873780 (LWP 3367))]

Thread 5 (Thread 0x7fb8ea910700 (LWP 3472)):
#0  0x7fb90f5f11c5 in g_source_iter_next (iter=iter@entry=0x7fb8ea90fdd0,
source=source@entry=0x7fb8ea90fdc8) at gmain.c:894
#1  0x7fb90f5f383f in g_main_context_check
(context=context@entry=0x3c00750, max_priority=2147483647,
fds=fds@entry=0x7fb8e40010c0, n_fds=n_fds@entry=1) at gmain.c:3629
#2  0x7fb90f5f3df8 in g_main_context_iterate (context=0x3c00750,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
gmain.c:3805
#3  0x7fb90f5f419a in g_main_loop_run (loop=0x3c006e0) at gmain.c:4002
#4  0x7fb8eb44c426 in gdbus_shared_thread_func (user_data=0x3c00720) at
gdbusprivate.c:274
#5  0x7fb90f618f65 in g_thread_proxy (data=0x3c01c50) at gthread.c:764
#6  0x7fb90fb100a4 in start_thread () from /lib64/libpthread.so.0
#7  0x7fb9135b504d in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7fb8e95ff700 (LWP 3769)):
#0  g_mutex_unlock (mutex=0x7fb8dc000990) at gthread-posix.c:1348
#1  0x7fb90f5f3d1d in g_main_context_iterate
(context=context@entry=0x7fb8dc000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3756
#2  0x7fb90f5f3f7c in g_main_context_iteration (context=0x7fb8dc000990,
may_block=1) at gmain.c:3869
#3  0x7fb913ed4a5b in QEventDispatcherGlib::processEvents
(this=0x7fb8dc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7fb913e7ba63 in QEventLoop::exec (this=this@entry=0x7fb8e95fee30,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7fb913c9e84a in QThread::exec (this=this@entry=0x3d087a0) at
thread/qthread.cpp:503
#6  0x7fb9122295f8 in QQmlThreadPrivate::run (this=0x3d087a0) at
/usr/src/debug/qtdeclarative-opensource-src-5.5.0/src/qml/qml/ftw/qqmlthread.cpp:141
#7  0x7fb913ca355f in QThreadPrivate::start (arg=0x3d087a0) at
thread/qthread_unix.cpp:331
#8  0x7fb90fb100a4 in start_thread () from /lib64/libpthread.so.0
#9  0x7fb9135b504d in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7fb8e0f77700 (LWP 3787)):
#0  g_wakeup_acknowledge (wakeup=0x7fb8dc002780) at gwakeup.c:211
#1  0x7fb90f5f3999 in g_main_context_check
(context=context@entry=0x7fb8d8000990, max_priority=2147483647,
fds=fds@entry=0x7fb8d8003270, n_fds=n_fds@entry=1) at gmain.c:3600
#2  0x7fb90f5f3df8 in g_main_context_iterate
(context=context@entry=0x7fb8d8000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3805
#3  0x7fb90f5f3f7c in g_main_context_iteration (context=0x7fb8d8000990,
may_block=1) at gmain.c:3869
#4  0x7fb913ed4a5b in QEventDispatcherGlib::processEvents
(this=0x7fb8d80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7fb913e7ba63 in QEventLoop::exec (this=this@entry=0x7fb8e0f76e30,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7fb913c9e84a in QThread::exec (this=this@entry=0x4fc3c80) at
thread/qthread.cpp:503
#7  0x7fb9122295f8 in QQmlThreadPrivate::run (this=0x4fc3c80) at
/usr/src/debug/qtdeclarative-opensource-src-5.5.0/src/qml/qml/ftw/qqmlthread.cpp:141
#8  0x7fb913ca355f in QThreadPrivate::start (arg=0x4fc3c80) at
thread/qthread_unix.cpp:331
#9  0x7fb90fb100a4 in start_thread () from /lib64/libpthread.so.0
#10 0x7fb9135b504d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7fb8d77ff700 (LWP 3796)):
#0  0x7fb9135acc1d in poll () from /lib64/libc.so.6
#1  0x7fb90f5f3e64 in g_main_context_poll (priority=2147483647, n_fds=1,
fds=0x7fb8d0002c70, timeout=-1, context=0x7fb8d990) at gmain.c:4103
#2  g_main_context_iterate (context=context@entry=0x7fb8d990,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
gmain.c:3803
#3  0x7fb90f5f3f7c in g_main_context_iteration (context=0x7fb8d990,
may_block=1) at gmain.c:3869
#4  0x7fb913ed4a5b in QEventDispatcherGlib::processEvents
(this=0x7fb8d8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7fb913e7ba63 in QEventLoop::

[konsole] [Bug 356836] New: Change of default profile is not saved in configuration file

[Piotr Mierzwinski via KDE Bugzilla]

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

Bug ID: 356836
   Summary: Change of default profile is not saved in
configuration file
   Product: konsole
   Version: master
  Platform: Mageia RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: history
  Assignee: konsole-de...@kde.org
  Reporter: piotr.mierzwin...@gmail.com

I've prepared couple of profiles and all are located in ~/.local/share/konsole
mc.profile
root mc.profile
shell.profile

On begin default is built profile: "Profile 1", so in configuration file
("~/.config/konsolerc") I have on begin following content:
[Desktop Entry]
DefaultProfile=Profile 1.profile

[Favorite Profiles]
Favorites=root mc.profile,shell.profile,mc.profile

Using "Manage profiles" option I changed default profile to "shell". I
restarted konsole and I got profile same as I very first time run konsole. When
I check configuration file here I can't see  any changes. OK. I change again
and default profile let be "mc". Again after restart of konsole I get very
first default profile, and configuration file is the same.



Reproducible: Always


Actual Results:  
Changed default profile is not saved in configuration file.

Expected Results:  
Newly selected default profile should be saved in configuration file.

This is refers to version: 15.11.80 (unavailable in this form).
KFrameworks 5.17.0. Plasma 5.5.1. Qt-5.5.1
Packages are coming from Mageia 6 Cauldron.

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

[plasmashell] [Bug 356834] Systray popup has fixed size and can't show more than 8 items

[Christian González via KDE Bugzilla]

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

--- Comment #1 from Christian González  ---
Created attachment 96143
  --> https://bugs.kde.org/attachment.cgi?id=96143&action=edit
Plasma5 systray popup with more than 8 items (the 9th can barely be accessed,
the 10th can't be accessed at all)

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

[konsole] [Bug 356723] Incomplete window updates after updating to Plasma 5.5.0

[Stefan Becker via KDE Bugzilla]

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

--- Comment #2 from Stefan Becker  ---
It seems that the running konsole process gets confused. When the windows from
the original konsole process start to show the window update problem then a new
konsole process started with

   $ konsole --separate

does *not* show the problem. I.e. I now have on my desktop konsole windows with
broken scrolling and konsole windows that work fine.

As an update to the original description: try scrolling up & down of a konsole
that has many lines in the scroll buffer: you will see updates on the top 2-3
lines and lowest 2-3 lines, but the middle part stays at is is.

BTW: my konsole profile has "Fixed size scrollback" with 1000 lines enabled.

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

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

[Boudewijn Rempt via KDE Bugzilla]

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

--- Comment #3 from Boudewijn Rempt  ---
Hm, if it also happens when opengl is switched off, it cannot be a display
driver issue. But I still haven't seen anything like this... You don't have
transform masks or something like that in your test images?

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