[akregator] [Bug 381683] Akregator crash when starting

[Nikita Malyshev]

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

--- Comment #3 from Nikita Malyshev  ---
Created attachment 107507
  --> https://bugs.kde.org/attachment.cgi?id=107507=edit
New crash information added by DrKonqi

akregator (5.6.1) using Qt 5.9.1

- What I was doing when the application crashed:

Nothing. Just installed it as normal app and trying to run.

-- Backtrace (Reduced):
#9  0x7f1eb77bc20a in qobject_cast
(object=0x28032c0) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:514
#10 Akregator::FrameManager::saveProperties (this=0x25f1d90, config=...) at
/workspace/build/src/frame/framemanager.cpp:278
#11 0x7f1e8c0b3c3f in Akregator::MainWidget::saveProperties
(this=, config=...) at /workspace/build/src/mainwidget.cpp:1227
#12 0x7f1e8c0ac7bd in Akregator::Part::saveCrashProperties (this=0x2587470)
at /workspace/build/src/akregator_part.cpp:779
#13 0x7f1e8c0ac835 in Akregator::Part::slotAutoSave (this=)
at /workspace/build/src/akregator_part.cpp:784

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

[akregator] [Bug 381683] Akregator crash when starting

[Nikita Malyshev]

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

Nikita Malyshev  changed:

   What|Removed |Added

 CC||niklan...@gmail.com

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

[kscreenlocker] [Bug 383981] kscreenlocker_greet segfaults with latest nvidia 384-69

[Martin Flöser]

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

Martin Flöser  changed:

   What|Removed |Added

 Resolution|--- |BACKTRACE
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #3 from Martin Flöser  ---
Please add a backtrace.

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

[kholidays] [Bug 383971] KHolidays: public holidays for Mauritius

[Laurent Montel]

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

Laurent Montel  changed:

   What|Removed |Added

 CC||mon...@kde.org

--- Comment #1 from Laurent Montel  ---
could you create a real patch please ?
more easy to verify improvement.

diff -up   &>~/diff_patch.diff


Thanks

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

[kinfocenter] [Bug 382128] wayland: kinfocenter still crashing when clicking on "Graphical information -> OpenGL"

[S . Vaidyanathan]

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

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

kinfocenter (5.10.4) using Qt 5.7.1

- What I was doing when the application crashed:

Select "OpenGL" Under Graphics section in KinfoCenter while running on Wayland
under Fedora26 (KDE).

-- Backtrace (Reduced):
#6  0x7f5fe682c9b9 in wl_map_insert_at () from
/lib64/libwayland-client.so.0
#7  0x7f5fe6828afe in wl_proxy_destroy () from
/lib64/libwayland-client.so.0
#8  0x7f5fe3e005c5 in KWayland::Client::Registry::release() () from
/lib64/libKF5WaylandClient.so.5
#9  0x7f5fe3e005ec in KWayland::Client::Registry::~Registry() () from
/lib64/libKF5WaylandClient.so.5
#10 0x7f5fe3e00679 in KWayland::Client::Registry::~Registry() () from
/lib64/libKF5WaylandClient.so.5

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

[kinfocenter] [Bug 382128] wayland: kinfocenter still crashing when clicking on "Graphical information -> OpenGL"

[S . Vaidyanathan]

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

S.Vaidyanathan  changed:

   What|Removed |Added

 CC||sva...@gmail.com

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

[plasmashell] [Bug 366062] Icons for Electron apps are too large in the System Tray

[varlesh]

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

--- Comment #16 from varlesh  ---
Any news? Now Plasma 5.10.5 and this not fixed

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

[k3b] [Bug 383835] Crash after closing audio project

[Leslie Zhai]

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

--- Comment #13 from Leslie Zhai  ---
Git commit 3cbe1f53c5e79864d4594879402297db902da703 by Leslie Zhai.
Committed on 25/08/2017 at 03:31.
Pushed by lesliezhai into branch 'master'.

Remove dead assignment private variable.

M  +1-2src/projects/k3bprojectplugindialog.cpp
M  +0-1src/projects/k3bprojectplugindialog.h

https://commits.kde.org/k3b/3cbe1f53c5e79864d4594879402297db902da703

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

[k3b] [Bug 383835] Crash after closing audio project

[Leslie Zhai]

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

--- Comment #12 from Leslie Zhai  ---
> //m_plugin(plugin)

yes, ProjectPlugin* m_plugin   is Dead assignment
http://www.leetcode.cn/2016/11/analyzing-code-for-kde-qt-open-source-components.html#k3b
 it never be used after assginment during constructor.


diff --git a/src/projects/k3bprojectplugindialog.cpp
b/src/projects/k3bprojectplugindialog.cpp
index 994424f..84841f6 100644
--- a/src/projects/k3bprojectplugindialog.cpp
+++ b/src/projects/k3bprojectplugindialog.cpp
@@ -25,8 +25,7 @@ K3b::ProjectPluginDialog::ProjectPluginDialog(
K3b::ProjectPlugin* plugin, K3b::
 QString(),
 START_BUTTON|CANCEL_BUTTON,
 START_BUTTON,
-plugin->metaObject()->className() ),
-  m_plugin(plugin)
+plugin->metaObject()->className() )
 {
 m_pluginGui = plugin->createGUI( doc, this );
 Q_ASSERT( m_pluginGui );
diff --git a/src/projects/k3bprojectplugindialog.h
b/src/projects/k3bprojectplugindialog.h
index 8a085c5..a799703 100644
--- a/src/projects/k3bprojectplugindialog.h
+++ b/src/projects/k3bprojectplugindialog.h
@@ -36,7 +36,6 @@ namespace K3b {
 void loadSettings( const KConfigGroup& config );

 private:
-ProjectPlugin* m_plugin;
 ProjectPluginGUIBase* m_pluginGui;
 };
 }


but I argue that it might not the root cause...

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

[k3b] [Bug 383835] Crash after closing audio project

[Mark]

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

--- Comment #11 from Mark  ---
Solved! maybe

The problem seems involved between k3b and kfilemetadata. So seemed to me there
might be some kind of name collision. grepped the k3b source and found clues. 
Now, this works for me (tried a number of times) but I don't know what other
problems it would cause. 

src/projects/k3bprojectplugindialog.cpp:22

K3b::ProjectPluginDialog::ProjectPluginDialog( K3b::ProjectPlugin* plugin,
K3b::Doc* doc, QWidget* parent )
: K3b::InteractionDialog( parent,
QString(),
QString(),
START_BUTTON|CANCEL_BUTTON,
START_BUTTON,
plugin->metaObject()->className() )
  //m_plugin(plugin)
{
m_pluginGui = plugin->createGUI( doc, this );

m_plugin is a name also used in kfilemetadata.

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

[konqueror] [Bug 382976] Clicking on OTD file does not open Libreoffice

[Emmett Culley]

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

--- Comment #2 from Emmett Culley  ---
Yes, uninstalling krusader fixed the problem.

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

[k3b] [Bug 383931] DVD extraction fails

[Leslie Zhai]

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

--- Comment #10 from Leslie Zhai  ---
> Does Leslie Zhai's recommendation of using kdenlive instead work at all?

yes, kdenlive is better choice than transcode, kdenlive use up-to-date libAV,
but transcode use very old library, and my wife prefer to use kdenlive :)

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

[dolphin] [Bug 383985] New: 'create new' disabled in context menu

[bugzilla_noreply]

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

Bug ID: 383985
   Summary: 'create new' disabled in context menu
   Product: dolphin
   Version: 17.08.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: ras...@gmail.com
CC: elvis.angelac...@kde.org
  Target Milestone: ---

When in a folder where the user does not have write permission, the 'create
new' option in the context menu is disabled. 

- Open another folder where the user has write permission in a new tab
- Switch to the new tab
- Open the context menu. The 'create new' option remains disabled.

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

[plasmashell] [Bug 379994] KDE freeze for 2-3 Minutes due to network disconnect while cifs mount

[Dennis Knorr]

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

--- Comment #11 from Dennis Knorr  ---
Hey, working late :)

For the file dialog patch: Yeah, giving us the patch would be very nice! At
least we can play around with it and see, if there's any cases we can test for.
How long would a proper real fix take? Just out of curiosity :-D

As for the symlink on the desktop, that might work perhaps, i have to ask my
colleagues tomorrow and write at the weekend a response.

We appreciate your work very much!

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

[k3b] [Bug 383835] Crash after closing audio project

[Leslie Zhai]

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

--- Comment #10 from Leslie Zhai  ---
> This edit makes a workaround:
> Extractor::~Extractor()
> {
> //delete d->m_plugin;

Memory leak...

> d->m_plugin = NULL;
> delete d;
> }
> 
> I only use k3b to burn audio so is it possible to make depending on
> kfilemetadata optional? I presume taglib would be enough.

Welcome patch!

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

[plasmashell] [Bug 379994] KDE freeze for 2-3 Minutes due to network disconnect while cifs mount

[David Edmundson]

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

--- Comment #10 from David Edmundson  ---
As for the file dialog, I can give you a patch right now that will work at the
expense of removing the blue progress bars underneath the mount points showing
how much disk is used.

I can't merge that like that as it's clearly just removing a feature, but for
you it might be worth the hit.

Fixing that properly I think is doable.

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

[plasmashell] [Bug 379994] KDE freeze for 2-3 Minutes due to network disconnect while cifs mount

[David Edmundson]

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

--- Comment #9 from David Edmundson  ---
I don't think I can easily fix the case of a symlink on the desktop.
*BUT* I can fix something that is identical to the end user.

Instead of creating a symlink create a .desktop file with the contents:

[Desktop Entry]
Type=Link
URL[$e]=file:///mnt/server

This (currently) does still freezes when disconnected, but that one is nice and
fixable.

Would that work for you?

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

[kscreenlocker] [Bug 383981] kscreenlocker_greet segfaults with latest nvidia 384-69

[bugzilla_noreply]

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

n3on.samu...@gmail.com changed:

   What|Removed |Added

 CC||n3on.samu...@gmail.com

--- Comment #2 from n3on.samu...@gmail.com ---
Im also experiencing this issue.

Just updated plasma today

kde plasma: 5.10.5
frameworks: 5.37.0
qt version: 5.9.1
kernel: 4.10.0-32
nvidia: 384-69

USER@NERO:~$ /usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet --testing
--immediateLock --graceTime 5000 --ksldfd 50
QSocketNotifier: Invalid socket 50 and type 'Read', disabling...
org.kde.kcoreaddons: Failed to establish shared memory mapping, will fallback
to private memory -- memory usage will increase 
No metadata file in the package, expected it at: "/home/USER/Pictures/" 
No metadata file in the package, expected it at: "/home/USER/Pictures/"
No metadata file in the package, expected it at: "/home/USER/Pictures/"
No metadata file in the package, expected it at: "/home/USER/Pictures/"
No metadata file in the package, expected it at: "/home/USER/Pictures/"
No metadata file in the package, expected it at: "/home/USER/Pictures/"
No metadata file in the package, expected it at: "/home/USER/Pictures/"
No metadata file in the package, expected it at: "/home/USER/Pictures/"
No metadata file in the package, expected it at: "/home/USER/Pictures/"
Locked at 1503622294
No metadata file in the package, expected it at: "/home/USER/Pictures/"
No metadata file in the package, expected it at: "/home/USER/Pictures/"
No metadata file in the package, expected it at: "/home/USER/Pictures/"
No metadata file in the package, expected it at: "/home/USER/Pictures/"
No metadata file in the package, expected it at: "/home/USER/Pictures/"
No metadata file in the package, expected it at: "/home/USER/Pictures/"
org.kde.kcoreaddons: Failed to establish shared memory mapping, will fallback
to private memory -- memory usage will increase
UdevQt: unable to create udev monitor connection
WARNING: Cannot find style "org.kde.desktop" - fallback:
"/usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Styles/Base"
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = kscreenlocker_greet path =
/usr/lib/x86_64-linux-gnu/libexec pid = 27650
KCrash: Arguments: /usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet
--testing --immediateLock --graceTime 5000 --ksldfd 50 
Segmentation fault

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

[dolphin] [Bug 383984] New: Switching to breadcrumb mode when pressing F6/Ctrl+L/Esc

[bugzilla_noreply]

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

Bug ID: 383984
   Summary: Switching to breadcrumb mode when pressing
F6/Ctrl+L/Esc
   Product: dolphin
   Version: 17.08.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: bars: location
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: ras...@gmail.com
  Target Milestone: ---

Pressing F6 or Ctrl+L to focus on the location bar should set it to editable
rather than toggling between editable and breadcrumb. If the config option
'editable location bar' is used, pressing F6 causes it to change to breadcrumb
mode so I have to press F6 a second time before I can type a new location. Also
pressing Esc when it has focus should not cause it to change to breadcrumb
mode.

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

[plasmashell] [Bug 381525] Crash in QQmlBinding::getPropertyData

[Frederick Zhang]

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

Frederick Zhang  changed:

   What|Removed |Added

 CC|frederick...@gmail.com  |

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

[plasmashell] [Bug 381525] Crash in QQmlBinding::getPropertyData

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

 CC||accounts-...@hinsenveld.net

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

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

[plasmashell] [Bug 383983] SPDIF audio output plus spotify crashes plasma

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

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

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


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

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

[plasmashell] [Bug 383983] New: SPDIF audio output plus spotify crashes plasma

[bugzilla_noreply]

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

Bug ID: 383983
   Summary: SPDIF audio output plus spotify crashes plasma
   Product: plasmashell
   Version: 5.10.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: accounts-...@hinsenveld.net
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.10.4)

Qt Version: 5.9.1
Frameworks Version: 5.37.0
Operating System: Linux 4.12.8-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed:
Recently switched to SPDIF digital output for audio. Now when I start the
computer and play audio for the first time (using spotify), plasma momentarily
crashes. There are no audio glitches, it continues playing. Plasma also
restarts almost immediately. Afterwards no crashes happen until I restart the
computer.
- Custom settings of the application:
SPDIF audio output using the inbuild realtek intel sound system of the
motherboard.
No modifications were made to the pulseaudio config files, so audio quality is
still 16bits and 44.1kHz. I run arch linux.

The crash can be reproduced sometimes.

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

Thread 13 (Thread 0x7f002c849700 (LWP 1044)):
#0  0x7f0118e411ad in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f0119c735ec in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f011da27ae8 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7f011da27f4a in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f0119c7215b in  () at /usr/lib/libQt5Core.so.5
#5  0x7f0118e3b049 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f0119585f0f in clone () at /usr/lib/libc.so.6

Thread 12 (Thread 0x7f001b7a0700 (LWP 1035)):
#0  0x7f011957be9d in poll () at /usr/lib/libc.so.6
#1  0x7f0113e9cc09 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f0113e9cd1c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f0119eb0084 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f0119e53ffb in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f0119c6d40e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f011cdf21d5 in  () at /usr/lib/libQt5Qml.so.5
#7  0x7f0119c7215b in  () at /usr/lib/libQt5Core.so.5
#8  0x7f0118e3b049 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f0119585f0f in clone () at /usr/lib/libc.so.6

Thread 11 (Thread 0x7f002ee22700 (LWP 1030)):
#0  0x7f0118e411ad in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f0119c735ec in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f011da27ae8 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7f011da27f4a in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f0119c7215b in  () at /usr/lib/libQt5Core.so.5
#5  0x7f0118e3b049 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f0119585f0f in clone () at /usr/lib/libc.so.6

Thread 10 (Thread 0x7f0034857700 (LWP 919)):
#0  0x7f0118e411ad in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f0119c735ec in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f011da27ae8 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7f011da27f4a in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f0119c7215b in  () at /usr/lib/libQt5Core.so.5
#5  0x7f0118e3b049 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f0119585f0f in clone () at /usr/lib/libc.so.6

Thread 9 (Thread 0x7f0035058700 (LWP 892)):
#0  0x7f0113ee1a69 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0
#1  0x7f0113e9cbef in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f0113e9cd1c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f0119eb0084 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f0119e53ffb in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f0119c6d40e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f00366dc18a in KCupsConnection::run() () at /usr/lib/libkcupslib.so
#7  0x7f0119c7215b in  () at /usr/lib/libQt5Core.so.5
#8  0x7f0118e3b049 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f0119585f0f in clone () at /usr/lib/libc.so.6

Thread 8 (Thread 0x7f003d312700 (LWP 826)):
#0  0x7f0113e9c69f in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#1  0x7f0113e9cbb0 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f0113e9cd1c in g_main_context_iteration () at

[konversation] [Bug 383982] New: Add GPU option to sysinfo script - PATCH

[richardlm]

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

Bug ID: 383982
   Summary: Add GPU option to sysinfo script - PATCH
   Product: konversation
   Version: 1.7.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: konversation-de...@kde.org
  Reporter: richard.l...@gmail.com
  Target Milestone: ---

Created attachment 107505
  --> https://bugs.kde.org/attachment.cgi?id=107505=edit
sysinfo with added $gpu

As requested on #konversation Fuchs kindly provided an solution, see script in
attachment.

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

[konversation] [Bug 383801] inputline adds # to every channel string when joining making local joins impossible

[Eli MacKenzie]

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

Eli MacKenzie  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
  Latest Commit||https://commits.kde.org/kon
   ||versation/72de2027f3d3e7a0c
   ||48aef6acd666e04fc0b19b1
 Resolution|--- |FIXED

--- Comment #1 from Eli MacKenzie  ---
Git commit 72de2027f3d3e7a0c48aef6acd666e04fc0b19b1 by Eli MacKenzie.
Committed on 24/08/2017 at 23:13.
Pushed by argonel into branch '1.7'.

Fix prefix-addressed message handling

Messages sent to all channel operators or other mode-prefixed classes of
channel members could use flags that conflict with channel prefix flags.
This tries harder to ensure that the actual channel prefix is found.

M  +1-0ChangeLog
M  +1-1src/commit.h
M  +19   -15   src/irc/server.cpp
M  +5-2src/irc/server.h

https://commits.kde.org/konversation/72de2027f3d3e7a0c48aef6acd666e04fc0b19b1

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

[plasmashell] [Bug 382793] QuiteRss news notification hangs plasmashell

[Aleksey Kontsevich]

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

--- Comment #9 from Aleksey Kontsevich  ---
Reproducible for KDE Plasma 5.10.5 in openSUSE Tumbleweed as well.

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

[kscreenlocker] [Bug 383981] kscreenlocker_greet segfaults with latest nvidia 384-69

[Paulo Dias]

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

--- Comment #1 from Paulo Dias  ---
kde: 5.10.5
frameworks: 5.37.0
qt: 5.7.1
kernel: 4.12.5
nvidia: 384-69

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

[kscreenlocker] [Bug 383981] kscreenlocker_greet segfaults with latest nvidia 384-69

[Paulo Dias]

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

Paulo Dias  changed:

   What|Removed |Added

 CC||paulo.miguel.d...@gmail.com

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

[kscreenlocker] [Bug 383981] New: kscreenlocker_greet segfaults with latest nvidia 384-69

[Paulo Dias]

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

Bug ID: 383981
   Summary: kscreenlocker_greet segfaults with latest nvidia
384-69
   Product: kscreenlocker
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: greeter
  Assignee: plasma-b...@kde.org
  Reporter: paulo.miguel.d...@gmail.com
CC: bhus...@gmail.com, mgraess...@kde.org
  Target Milestone: ---

apparently something changed with the opengl implementation,
kscreenlocker_greet segfault while trying to secure the screen. if i use
embedded intel, it works as advertised.

groo@kerberos:~$ /usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet
--testing --immediateLock --graceTime 5000 --ksldfd 50
QSocketNotifier: Invalid socket 50 and type 'Read', disabling...
org.kde.kcoreaddons: Failed to establish shared memory mapping, will fallback
to private memory -- memory usage will increase 
file:///usr/share/plasma/wallpapers/org.kde.slideshow/contents/ui/main.qml:147:
TypeError: Property 'setAction' of object
ScreenLocker::WallpaperIntegration(0x21229c1590) is not a function  
Locked at 1503615880
No file found for ".xml" , even though update-mime-info said it would exist.
Either it was just removed, or the directory doesn't have executable
permission... ("/usr/share/mime")   
No file found for ".xml" , even though update-mime-info said it would exist.
Either it was just removed, or the directory doesn't have executable
permission... ("/usr/share/mime")   
org.kde.kcoreaddons: Failed to establish shared memory mapping, will fallback
to private memory -- memory usage will increase 
UdevQt: unable to create udev monitor connection
WARNING: Cannot find style "org.kde.desktop" - fallback:
"/usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Styles/Base"
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)  
No metadata file in the package, expected it at: "/usr/share/backgrounds/"  
No metadata file in the package, expected it at: "/usr/share/backgrounds/"  
No metadata file in the package, expected it at: "/usr/share/backgrounds/"  
QOpenGLFramebufferObject: Unsupported framebuffer format.   
QOpenGLFramebufferObject: Framebuffer incomplete, missing attachment.   
KCrash: crashing... crashRecursionCounter = 2   
KCrash: Application Name = kscreenlocker_greet path =
/usr/lib/x86_64-linux-gnu/libexec pid = 5931
KCrash: Arguments: /usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet
--testing --immediateLock --graceTime 5000 --ksldfd 50 

the screenlock then shows the screenlock is broken msg, use loginctl
unlock-session

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

[okular] [Bug 360603] Markdown (.md) support

[Albert Astals Cid]

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

Albert Astals Cid  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/oku
   ||lar/4931385777ce9fa55c8b52f
   ||5009603b2b6d58d7f
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Albert Astals Cid  ---
Git commit 4931385777ce9fa55c8b52f5009603b2b6d58d7f by Albert Astals Cid, on
behalf of Julian Wolff.
Committed on 24/08/2017 at 23:05.
Pushed by aacid into branch 'master'.

add markdown support

Summary:
Adds support for Markdown documents

Test Plan: Open a Markdown (.md) document in Okular

Reviewers: #okular, aacid

Reviewed By: #okular, aacid

Subscribers: michaelweghorn, aacid

Tags: #okular

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

A  +36   -0cmake/modules/FindDiscount.cmake
M  +11   -0generators/CMakeLists.txt
A  +22   -0generators/markdown/CMakeLists.txt
A  +2-0generators/markdown/Messages.sh
A  +177  -0generators/markdown/converter.cpp [License: GPL (v2+)]
A  +47   -0generators/markdown/converter.h [License: GPL (v2+)]
A  +19   -0generators/markdown/debug_md.h [License: GPL (v2+)]
A  +37   -0generators/markdown/generator_md.cpp [License: GPL (v2+)]
A  +27   -0generators/markdown/generator_md.h [License: GPL (v2+)]
A  +26   -0generators/markdown/libokularGenerator_md.json
A  +13   -0generators/markdown/okularApplication_md.desktop
A  +7-0generators/markdown/okularMd.desktop
A  +14   -0generators/markdown/org.kde.mobile.okular_md.desktop
A  +13   -0generators/markdown/org.kde.okular-md.metainfo.xml
M  +1-0okular.categories

https://commits.kde.org/okular/4931385777ce9fa55c8b52f5009603b2b6d58d7f

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

[okular] [Bug 383980] Okular crashes when latex updates synctex

[Eugene Shalygin]

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

--- Comment #1 from Eugene Shalygin  ---
Okular does not crash when I recompile the same .tex source with synctex
disabled.

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

[okular] [Bug 383980] New: Okular crashes when latex updates synctex

[Eugene Shalygin]

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

Bug ID: 383980
   Summary: Okular crashes when latex updates synctex
   Product: okular
   Version: 1.3.70
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: eugene.shalygin+bugzilla@gmail.com
  Target Milestone: ---

Application: okular (1.3.70)
 (Compiled from sources)
Qt Version: 5.9.1
Frameworks Version: 5.37.0
Operating System: Linux 4.12.8-gentoo x86_64
Distribution: "Gentoo Base System release 2.4.1"

-- Information about the crash:
- What I was doing when the application crashed:
When Okular views a PDF file which is beeing updated by lualatex with synctex
enabled, Okular crashes during latex run.

The crash can be reproduced every time.

-- Backtrace:
Application: Okular (okular), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f7004fdcd80 (LWP 13051))]

Thread 3 (Thread 0x7f6fe5f66700 (LWP 13053)):
#0  0x7f70002ff29d in poll () from /lib64/libc.so.6
#1  0x7f6ff9b50a19 in g_main_context_iterate.isra () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f6ff9b50b2c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f700118a22b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#4  0x7f70011377ea in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#5  0x7f7000f8efda in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x7f70050a5629 in QDBusConnectionManager::run() () from
/usr/lib64/libQt5DBus.so.5
#7  0x7f7000f93302 in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#8  0x7f6fff2a3617 in start_thread () from /lib64/libpthread.so.0
#9  0x7f700030a69f in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f6ff27bd700 (LWP 13052)):
#0  0x7f70002ff29d in poll () from /lib64/libc.so.6
#1  0x7f6ffda0a60f in _xcb_conn_wait () from /usr/lib64/libxcb.so.1
#2  0x7f6ffda128c9 in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7f6ff44ebcd9 in QXcbEventReader::run() () from
/usr/lib64/libQt5XcbQpa.so.5
#4  0x7f7000f93302 in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#5  0x7f6fff2a3617 in start_thread () from /lib64/libpthread.so.0
#6  0x7f700030a69f in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f7004fdcd80 (LWP 13051)):
[KCrash Handler]
#6  0x0aca1020 in ?? ()
#7  0x7f6fe45647d5 in _synctex_free_leaf () from
/usr/lib64/libOkular5Core.so.7
#8  0x7f6fe45647d5 in _synctex_free_leaf () from
/usr/lib64/libOkular5Core.so.7
#9  0x7f6fe45647d5 in _synctex_free_leaf () from
/usr/lib64/libOkular5Core.so.7
#10 0x7f6fe45647d5 in _synctex_free_leaf () from
/usr/lib64/libOkular5Core.so.7
#11 0x7f6fe45647d5 in _synctex_free_leaf () from
/usr/lib64/libOkular5Core.so.7
#12 0x7f6fe45647d5 in _synctex_free_leaf () from
/usr/lib64/libOkular5Core.so.7
#13 0x7f6fe45647d5 in _synctex_free_leaf () from
/usr/lib64/libOkular5Core.so.7
#14 0x7f6fe45647d5 in _synctex_free_leaf () from
/usr/lib64/libOkular5Core.so.7
#15 0x7f6fe45647d5 in _synctex_free_leaf () from
/usr/lib64/libOkular5Core.so.7
#16 0x7f6fe45647d5 in _synctex_free_leaf () from
/usr/lib64/libOkular5Core.so.7
#17 0x7f6fe45647d5 in _synctex_free_leaf () from
/usr/lib64/libOkular5Core.so.7
#18 0x7f6fe45647d5 in _synctex_free_leaf () from
/usr/lib64/libOkular5Core.so.7
#19 0x7f6fe45647d5 in _synctex_free_leaf () from
/usr/lib64/libOkular5Core.so.7
#20 0x7f6fe45647d5 in _synctex_free_leaf () from
/usr/lib64/libOkular5Core.so.7
#21 0x7f6fe45647d5 in _synctex_free_leaf () from
/usr/lib64/libOkular5Core.so.7
#22 0x7f6fe45647d5 in _synctex_free_leaf () from
/usr/lib64/libOkular5Core.so.7
#23 0x7f6fe4564700 in _synctex_free_node () from
/usr/lib64/libOkular5Core.so.7
#24 0x7f6fe456469a in _synctex_free_node () from
/usr/lib64/libOkular5Core.so.7
#25 0x7f6fe456469a in _synctex_free_node () from
/usr/lib64/libOkular5Core.so.7
#26 0x7f6fe456469a in _synctex_free_node () from
/usr/lib64/libOkular5Core.so.7
#27 0x7f6fe456469a in _synctex_free_node () from
/usr/lib64/libOkular5Core.so.7
#28 0x7f6fe456469a in _synctex_free_node () from
/usr/lib64/libOkular5Core.so.7
#29 0x7f6fe456469a in _synctex_free_node () from
/usr/lib64/libOkular5Core.so.7
#30 0x7f6fe456469a in _synctex_free_node () from
/usr/lib64/libOkular5Core.so.7
#31 0x7f6fe456469a in _synctex_free_node () from
/usr/lib64/libOkular5Core.so.7
#32 0x7f6fe456469a in _synctex_free_node () from
/usr/lib64/libOkular5Core.so.7
#33 0x7f6fe456469a in _synctex_free_node () from
/usr/lib64/libOkular5Core.so.7
#34 0x7f6fe456469a in _synctex_free_node () from
/usr/lib64/libOkular5Core.so.7

[kstars] [Bug 383979] New: KStars can't find NGC6992

[Jean-Claude]

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

Bug ID: 383979
   Summary: KStars can't find NGC6992
   Product: kstars
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mutla...@ikarustech.com
  Reporter: jcjes...@free.fr
  Target Milestone: ---

I typed NGC6992 in the Find dialog, then Details...> Center in Map + Center in
Telescope.
Nothing happened during about one minute.
Then the scope slewed crazy to the ground .
I repeated this bug several times after restarting KStars.
Same thing if I type NGC6960.
Then I typed Deneb in the Find dialog : same thing. The scope went crazy.
Then I typed a second time Deneb and the scope slewed to the right place.

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

[kstars] [Bug 383978] New: KStars can't find NGC6992

[Jean-Claude]

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

Bug ID: 383978
   Summary: KStars can't find NGC6992
   Product: kstars
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mutla...@ikarustech.com
  Reporter: jcjes...@free.fr
  Target Milestone: ---

I typed NGC6992 in the Find dialog, then Details...> Center in Map + Center in
Telescope.
Nothing happened during about one minute.
Then the scope slewed crazy to the ground .
I repeated this bug several times after restarting KStars.
Same thing if I type NGC6960.
Then I typed Deneb in the Find dialog : same thing. The scope went crazy.
Then I typed a second time Deneb and the scope slewed to the right place.

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

[telepathy] [Bug 383964] Going online on Instant Messaging Widget crashes plasma

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

   Assignee|k...@davidedmundson.co.uk|kde-telepathy-b...@kde.org
Version|5.10.4  |unspecified
  Component|general |general
   Target Milestone|1.0 |Future
Product|plasmashell |telepathy

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

[plasmashell] [Bug 383968] Plasma crashes after the screensafer

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

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

--- Comment #1 from David Edmundson  ---
Crash is fixed in newer Qt.

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

[konqueror] [Bug 383071] Konqueror isn't able to open URLs on startup

[Christoph Feck]

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

--- Comment #1 from Christoph Feck  ---
Does it depend on the used web engine type? You can Konqueror to use KHTML,
WebKit, or WebEngine, if the required packages are installed.

Using WebKit mode, it works here with Konqueror from master branch.

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

[konqueror] [Bug 382976] Clicking on OTD file does not open Libreoffice

[Christoph Feck]

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

--- Comment #1 from Christoph Feck  ---
> Is it possible karc is the problem?

Probably. Please check if uninstalling Krusader helps to resolve the issue.

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

[plasmashell] [Bug 382728] Multiple icons bugs in SystemTray

[Aleksey Kontsevich]

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

--- Comment #13 from Aleksey Kontsevich  ---
Hmmm... icons looks very nice in openSUSE. Icons do not disappear. Seems some
Neon or Kubuntu bug. Have not checked with riot however.

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

[kmymoney4] [Bug 383977] New: In Accounts view, do not change expand/collapse state after editing an account

[Jack]

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

Bug ID: 383977
   Summary: In Accounts view, do not change expand/collapse state
after editing an account
   Product: kmymoney4
   Version: git (master)
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: kmymoney-de...@kde.org
  Reporter: ostrof...@users.sourceforge.net
  Target Milestone: ---

The Accounts View defaults to displaying fully expanded.  If I collapse all
accounts (to not show equities, for example) and then edit an account (to
change it's name) when I OK the edit, the list is fully expanded again.  This
is very annoying, since I only want to see the account names, not all the
equities (yes this is for investment accounts.)  I do not want to disable
showing the equities, since I do generally want to see them, but if I am (for
example) making systemic changes to account names (such as to include partial
account number in the name) I have several edits to do, and it is very
inconvenient to have to reset the expand/collapse after every edit.

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

[kwin] [Bug 382393] Hot Corners Fail On Multiple Monitors

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |INVALID

--- Comment #4 from Christoph Feck  ---
No response, changing status. If you have new information, please add a
comment.

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

[kwin] [Bug 381796] crash kwin_wayland when changing the keyboard layout

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 Resolution|BACKTRACE   |INVALID
 Status|NEEDSINFO   |RESOLVED

--- Comment #4 from Christoph Feck  ---
No response, changing status. If you have new information, please add a
comment.

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

[konsole] [Bug 383976] New: newer vim outputs $q q on konsole (broken xterm-256color compatibility)

[Albert Astals Cid]

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

Bug ID: 383976
   Summary: newer vim outputs $q q on konsole (broken
xterm-256color compatibility)
   Product: konsole
   Version: 17.08.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: emulation
  Assignee: konsole-de...@kde.org
  Reporter: aa...@kde.org
  Target Milestone: ---

According to https://github.com/vim/vim/issues/2008#issuecomment-324476312

This is the usual problem of setting 'term' to "xterm", while the terminal is
not actually xterm compatible. You have to set 'term' to the right value.

So either we change the 
 echo $TERM
  xterm-256color

or ideally we make it xterm compatible

I can try having a look at what needs fixing, but a pointer would be welcome :)

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

[krita] [Bug 383975] Vector Creation Bug with Grid

[bugzilla_noreply]

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

--- Comment #1 from reptilli...@live.com ---
Oh yeah, forgot to mention that the grid spacing must be 1 px, 1 px
subdivision, and in rectangle form. Basically, a pixel grid.

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

[kdenlive] [Bug 383914] Segfault in QSGRenderThread immediately upon startup

[The Lightning Stalker]

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

--- Comment #3 from The Lightning Stalker  ---
(In reply to Christoph Feck from comment #1)
> Please ask for help in a forum of your distribution with correct OpenGL
> driver installation.

Ok so I got it working.  I had to purge all my libqt* and did a post-autoremove
just for good measure, which also happened to remove kdenlive itself, then
reinstalled kdenlive.  I suspect it may have had something to do with qt4 and 5
not playing nice with one another.  The OpenGL driver is part of the NVIDIA
packages, so it most likely had nothing to do with that.

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

[krita] [Bug 383975] New: Vector Creation Bug with Grid

[bugzilla_noreply]

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

Bug ID: 383975
   Summary: Vector Creation Bug with Grid
   Product: krita
   Version: 4.0 pre-alpha
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Vector Objects and Tools
  Assignee: krita-bugs-n...@kde.org
  Reporter: reptilli...@live.com
  Target Milestone: ---

On Krita 4.0.0 Pre-Alpha and Windows 10 x64, it appears that if you enable snap
to grid, and create a vector layer, and then create a square, you'll note that
the created vector square shifts the point to 1 pixel right, and down.

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

[k3b] [Bug 383835] Crash after closing audio project

[Mark]

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

--- Comment #9 from Mark  ---
This edit makes a workaround:
Extractor::~Extractor()
{
//delete d->m_plugin;
d->m_plugin = NULL;
delete d;
}

Removing /opt/kf5/lib/plugins/kf5/kfilemetadata/*extractor.so also fixes the
issue. So it would seem the problem is with my installation of kfilemetadata.
Problem is, every other thing that depends on kfilemetadata works correctly -
baloo, digikam, kdenlive. I just built Tellico and ran the test suite, all
good.

I only use k3b to burn audio so is it possible to make depending on
kfilemetadata optional? I presume taglib would be enough.

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

[dolphin] [Bug 383942] Application: Dolphin (kdeinit5), signal: Aborted

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

   Severity|normal  |crash

--- Comment #2 from Christoph Feck  ---
A valgrind log would help to understand if the the memory corruption is caused
by the nvidia driver or KDE code.

For more information, please see
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_with_Valgrind

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

[systemsettings] [Bug 370628] Allow to chose fractional font sizes

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||ene...@gmail.com

--- Comment #3 from Christoph Feck  ---
*** Bug 383938 has been marked as a duplicate of this bug. ***

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

[systemsettings] [Bug 383938] It should be possible to adjust plasma font size with decimal precision

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #1 from Christoph Feck  ---


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

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

[plasmashell] [Bug 381000] [Regression] High CPU when background is set to slideshow

[Mircea Kitsune]

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

--- Comment #115 from Mircea Kitsune  ---
openSUSE Tumbleweed reverted the guilty commit about 3 weeks ago. I can only
say it's solved the problem for me.

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

[ring-kde] [Bug 383974] New: The account own "contact" is sometime visible in the timeline

[Emmanuel Lepage Vallée]

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

Bug ID: 383974
   Summary: The account own "contact" is sometime visible in the
timeline
   Product: ring-kde
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: elv1...@gmail.com
  Reporter: elv1...@gmail.com
  Target Milestone: ---

If the user account own profile/contact/avatar creates more than a single
ContactMethod entry (for example, by trying to call itself for some absurd
reasons), it will create a "black hole" in the PhoneDirectoryModel. That
duplicated ContactMethod should have the "isSelf" state, but doesn't. It means
it can then vacuum history elements into itself instead of the real peer. The
database is no longer consistent and the models view are wrong.

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

[kdevelop] [Bug 383973] New: JavaScript parser confused by missing optional semicolon

[Jonathan Verner]

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

Bug ID: 383973
   Summary: JavaScript parser confused by missing optional
semicolon
   Product: kdevelop
   Version: 5.1.1
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: Language Support: QML/JavaScript
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: jonathan.ver...@gmail.com
  Target Milestone: ---

Kdevelop's Javascript parser is confused by (seemingly valid) code like this:

`
while(true) {
 if(false){break}
}
`

Complaining that there is a syntax error

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

[ring-kde] [Bug 383972] New: The peerstimeline proxy order is unstable/racy

[Emmanuel Lepage Vallée]

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

Bug ID: 383972
   Summary: The peerstimeline proxy order is unstable/racy
   Product: ring-kde
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: elv1...@gmail.com
  Reporter: elv1...@gmail.com
  Target Milestone: ---

The peerstimelinemodel used by the left pane is prone to race conditions when
the applications load. The individual peer timeline too (not to be confused
with the peerS timeline).

This is caused by the deduplication algorithm and seems to have regressed with
all the recent memory managment changes that affected the loading order. The
race did exist before, but as the loading order was different, it was unlikely
(but as stree tests showed, not impossible). With the current HEAD commit,
there is about a 50/50 chance of being wrong.

This is in itself good news, as it shows the loading is a bit saner. However it
has to be fixed as it renders the app unusable. The items that should be at the
top can only be accessed using the search feature.

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

[kmail2] [Bug 358430] Consecutive quotes make message extremely long, which in turn makes KMail freeze when replying.

[Vincenzo Reale]

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

Vincenzo Reale  changed:

   What|Removed |Added

 CC||smart2...@baslug.org

--- Comment #3 from Vincenzo Reale  ---
I can confirm it. 
Exchanging some messages, the body becomes too long and the composer freezes
all the time.
The same behavior is still present on KMail 5.6 on Archlinux, Plasma 5.10.5,
KDE Frameworks 5.37 and KDE Applications 17.08.

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

[okular] [Bug 383943] HiDPI: Rendering glitches near the page boundaries

[Henrik Fehlauer]

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

Henrik Fehlauer  changed:

   What|Removed |Added

Summary|Rendering glitches near the |HiDPI: Rendering glitches
   |page boundaries |near the page boundaries
 CC||rk...@lab12.net
 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #1 from Henrik Fehlauer  ---
To reproduce, set QT_SCREEN_SCALE_FACTORS=2 (I guess this context is missing
here ;). For a nice and flickery animation of the artifacts, try changing the
window width.

Tested with Qt 5.9.1.

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

[k3b] [Bug 383931] DVD extraction fails

[Dr . Chapatin]

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

--- Comment #9 from Dr. Chapatin  ---
I forgot to say that this problem happens on two comnputers running the same
distro.

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

[k3b] [Bug 383931] DVD extraction fails

[Dr . Chapatin]

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

--- Comment #8 from Dr. Chapatin  ---
Created attachment 107504
  --> https://bugs.kde.org/attachment.cgi?id=107504=edit
debug info

Thank you again Jim.

These two dvds are musical videos/concert, debug info in my attachment.

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

[kholidays] [Bug 383971] New: KHolidays: public holidays for Mauritius

[Nadim Attari]

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

Bug ID: 383971
   Summary: KHolidays: public holidays for Mauritius
   Product: kholidays
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: nadim.att...@gmail.com
  Target Milestone: ---

Created attachment 107503
  --> https://bugs.kde.org/attachment.cgi?id=107503=edit
KDE PIM/KHolidays/File for Mauritius

Request to include public holidays for Mauritius

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

[libkgapi] [Bug 383970] New: libkgapi ignores proxy settings (yet again)

[Renan Teston Inácio]

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

Bug ID: 383970
   Summary: libkgapi ignores proxy settings (yet again)
   Product: libkgapi
   Version: GIT
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: dvra...@kde.org
  Reporter: zerocaro...@gmail.com
  Target Milestone: ---

This is a regression(?) from Bug 339727, which was fixed on the LibKGAPI/2.2
branch but never released. The branch, however, when merged into master got the
fix reverted (commit 64493078).

This affects Bug 343039.

I am running libkf5gapicore5 version 5.3.1-0ubuntu1~ubuntu17.04~ppa2 (from
Kubuntu Backports PPA).

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

[k3b] [Bug 383931] DVD extraction fails

[Jim]

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

--- Comment #7 from Jim  ---
Are the other two discs some popular movie that I may have a copy of on which
to test?  If so, what are they?  Can you attach k3b output for at least one of
the other two discs?

Thanks,
--Jim

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

[kate] [Bug 368130] Vi-mode search box disappears if used again while the search box is still open

[Simon Yuan]

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

Simon Yuan  changed:

   What|Removed |Added

Version|17.04.0 |17.08.0

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

[k3b] [Bug 383931] DVD extraction fails

[Dr . Chapatin]

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

--- Comment #6 from Dr. Chapatin  ---
My mistake. Handbrake fails at 44%.
The file generated by ConvertXtoVideo Ultimate freezes at ~27min, the same
freeze hapeens when I play the disc.
Ok, I think the original files burmed on this disc were corrupted.

I tested the others two discs on Antergos: I can rip both using handbrake, but
K3b fails to rip them.

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

[krita] [Bug 382557] [WACOM] Unexpected multiple clicks using intuos tablet

[Xzu]

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

Xzu  changed:

   What|Removed |Added

 CC||xzuruk...@free.fr

--- Comment #2 from Xzu  ---
Personally, I don't got this with 3.2.0 app image and intuos3 A4.

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

[krita] [Bug 383969] New: Make brush color darker/lighter issue

[Xzu]

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

Bug ID: 383969
   Summary: Make brush color darker/lighter issue
   Product: krita
   Version: 3.2.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Brush engine
  Assignee: krita-bugs-n...@kde.org
  Reporter: xzuruk...@free.fr
  Target Milestone: ---

Hi, apologizes for this amazing soft!!

I use the app image from official web site. 
When I use "Make brush color darker/lighter" all is ok, except if I go to real
black or white: then I can just go to black and white and I can't get back to
my original color.

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

[plasmashell] [Bug 383968] New: Plasma crashes after the screensafer

[Christian Pubanz]

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

Bug ID: 383968
   Summary: Plasma crashes after the screensafer
   Product: plasmashell
   Version: 5.5.5
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: pub...@arcor.de
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.5.5)

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

-- Information about the crash:
- What I was doing when the application crashed:
My Laptop switched to screensafer, so when I exit screensafer and i working
continued Plasma 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 0x7f9bf02557c0 (LWP 4506))]

Thread 8 (Thread 0x7f9b2cfaa700 (LWP 4619)):
#0  0x7f9be9752bfd in poll () from /lib64/libc.so.6
#1  0x7f9be5e2fe64 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f9be5e2ff7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f9bea07fd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#4  0x7f9bea026d53 in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#5  0x7f9be9e4861a in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x7f9b2e5f6cf7 in KCupsConnection::run() () from
/usr/lib64/libkcupslib.so
#7  0x7f9be9e4d32f in ?? () from /usr/lib64/libQt5Core.so.5
#8  0x7f9be8f5c0a4 in start_thread () from /lib64/libpthread.so.0
#9  0x7f9be975b02d in clone () from /lib64/libc.so.6

Thread 7 (Thread 0x7f9b3734b700 (LWP 4539)):
#0  0x7f9be974eccd in read () from /lib64/libc.so.6
#1  0x7f9be5e70b60 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f9be5e2f999 in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f9be5e2fdf8 in ?? () from /usr/lib64/libglib-2.0.so.0
#4  0x7f9be5e2ff7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#5  0x7f9bea07fd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#6  0x7f9bea026d53 in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#7  0x7f9be9e4861a in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#8  0x7f9bedcf8282 in ?? () from /usr/lib64/libQt5Quick.so.5
#9  0x7f9be9e4d32f in ?? () from /usr/lib64/libQt5Core.so.5
#10 0x7f9be8f5c0a4 in start_thread () from /lib64/libpthread.so.0
#11 0x7f9be975b02d in clone () from /lib64/libc.so.6

Thread 6 (Thread 0x7f9bbe9c1700 (LWP 4527)):
#0  0x7f9be8f6003f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f9bef92b86b in ?? () from /usr/lib64/libQt5Script.so.5
#2  0x7f9bef92b899 in ?? () from /usr/lib64/libQt5Script.so.5
#3  0x7f9be8f5c0a4 in start_thread () from /lib64/libpthread.so.0
#4  0x7f9be975b02d in clone () from /lib64/libc.so.6

Thread 5 (Thread 0x7f9bb700 (LWP 4526)):
#0  0x7f9be5e2f010 in g_main_context_release () from
/usr/lib64/libglib-2.0.so.0
#1  0x7f9be5e2fe0e in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f9be5e2ff7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f9bea07fd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#4  0x7f9bea026d53 in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#5  0x7f9be9e4861a in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x7f9bed15ce18 in ?? () from /usr/lib64/libQt5Qml.so.5
#7  0x7f9be9e4d32f in ?? () from /usr/lib64/libQt5Core.so.5
#8  0x7f9be8f5c0a4 in start_thread () from /lib64/libpthread.so.0
#9  0x7f9be975b02d in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7f9bc5b32700 (LWP 4525)):
#0  0x7f9be9752bfd in poll () from /lib64/libc.so.6
#1  0x7f9be5e2fe64 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f9be5e2ff7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f9bea07fd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#4  0x7f9bea026d53 in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#5  0x7f9be9e4861a in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x7f9bed15ce18 in ?? () from /usr/lib64/libQt5Qml.so.5
#7  0x7f9be9e4d32f in ?? () from /usr/lib64/libQt5Core.so.5
#8  0x7f9be8f5c0a4 in start_thread () from /lib64/libpthread.so.0
#9  0x7f9be975b02d in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7f9bd2fc1700 (LWP 4519)):
#0  0x7f9be9752bfd in poll () from /lib64/libc.so.6
#1  0x7f9be5e2fe64 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f9be5e2ff7c in g_main_context_iteration 

[krita] [Bug 383967] Scary output (crash?) after closing krita.

[wolthera]

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

--- Comment #1 from wolthera  ---
And.. a proper backtrace?

Application: Krita (krita), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f818eeca8c0 (LWP 27744))]

Thread 4 (Thread 0x7f8158262700 (LWP 27755)):
#0  0x7f819e76f30d in nanosleep () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f819f2dc2ad in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f819f0b2d18 in QThread::msleep(unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f819c72642a in KisTileDataSwapper::run (this=0x7f819cbf6b00
<(anonymous namespace)::Q_QGS_s_instance::innerFunction()::holder+64>) at
/home/wolthera/krita/src/libs/image/tiles3/swap/kis_tile_data_swapper.cpp:97
#4  0x7f819f0b3989 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f8198ef16ba in start_thread (arg=0x7f8158262700) at
pthread_create.c:333
#6  0x7f819e7aa3dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f818133c700 (LWP 27749)):
#0  0x7f819e79e70d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f81978f738c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f81978f749c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f819f2dc94b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f819f2857ca in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f819f0aecd4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f819911cb75 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x7f819f0b3989 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f8198ef16ba in start_thread (arg=0x7f818133c700) at
pthread_create.c:333
#9  0x7f819e7aa3dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f818ca50700 (LWP 27745)):
#0  0x7f819e79e70d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f819ce53c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f819ce558d7 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f818ed98329 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x7f819f0b3989 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f8198ef16ba in start_thread (arg=0x7f818ca50700) at
pthread_create.c:333
#6  0x7f819e7aa3dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f818eeca8c0 (LWP 27744)):
[KCrash Handler]
#6  0x7f819e6d8428 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
#7  0x7f819e6da02a in __GI_abort () at abort.c:89
#8  0x7f819e71a7ea in __libc_message (do_abort=do_abort@entry=2,
fmt=fmt@entry=0x7f819e833e98 "*** Error in `%s': %s: 0x%s ***\n") at
../sysdeps/posix/libc_fatal.c:175
#9  0x7f819e72337a in malloc_printerr (ar_ptr=,
ptr=, str=0x7f819e830c6f "free(): invalid pointer", action=3) at
malloc.c:5006
#10 _int_free (av=, p=, have_lock=0) at
malloc.c:3867
#11 0x7f819e72753c in __GI___libc_free (mem=) at
malloc.c:2968
#12 0x7f819f2b1703 in QObjectPrivate::deleteChildren() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x7f819fc2c234 in QWidget::~QWidget() () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#14 0x7f81a04045a1 in KMainWindow::~KMainWindow (this=0x1bd9ffd0,
__in_chrg=) at
/home/wolthera/krita/src/libs/widgetutils/xmlgui/kmainwindow.cpp:349
#15 0x7f81a0e0cc9a in KisMainWindow::~KisMainWindow (this=0x1bd9ffd0,
__in_chrg=, __vtt_parm=) at
/home/wolthera/krita/src/libs/ui/KisMainWindow.cpp:490
#16 0x7f81a0e0cd39 in KisMainWindow::~KisMainWindow (this=0x1bd9ffd0,
__in_chrg=, __vtt_parm=) at
/home/wolthera/krita/src/libs/ui/KisMainWindow.cpp:523
#17 0x7f819f2b4c90 in QObject::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x7f819fc30d33 in QWidget::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#19 0x7f819fd221cb in QMainWindow::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#20 0x7f81a04064f7 in KMainWindow::event (this=this@entry=0x1bd9ffd0,
ev=ev@entry=0x26880c70) at
/home/wolthera/krita/src/libs/widgetutils/xmlgui/kmainwindow.cpp:780
#21 0x7f81a043e919 in KXmlGuiWindow::event (this=0x1bd9ffd0, ev=0x26880c70)
at /home/wolthera/krita/src/libs/widgetutils/xmlgui/kxmlguiwindow.cpp:125
#22 0x7f819fbef3fc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#23 0x7f819fbf6e07 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#24 0x7f81a0dda507 in KisApplication::notify (this=,
receiver=0x1bd9ffd0, event=0x26880c70) at
/home/wolthera/krita/src/libs/ui/KisApplication.cpp:556

[akregator] [Bug 199232] Database not saved until quitting

[Patrick]

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

--- Comment #8 from Patrick  ---
Regarding my previous comment, I lost a lot of articles after an uptime of
about 10 days and a crash of Akregator during startup (after a reboot). I've
been monitoring the archived feeds since then, but they seem to be saved
correctly after each fetch.

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

[kdenlive] [Bug 383914] Segfault in QSGRenderThread immediately upon startup

[The Lightning Stalker]

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

--- Comment #2 from The Lightning Stalker  ---
(In reply to Christoph Feck from comment #1)
> Please ask for help in a forum of your distribution with correct OpenGL
> driver installation.

A more recent version of the nvidia driver is installed.  There is an even
newer one I will try updating and see if it works.

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

[systemsettings] [Bug 383962] The Num Block key status isn't remembered between sessions

[Thomas H]

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

Thomas H  changed:

   What|Removed |Added

 CC||iamtomhan...@gmail.com

--- Comment #2 from Thomas H  ---
I found some discussion of this and a temporary workaround on this thread:
https://forum.kde.org/viewtopic.php?f=289=133089

Add a "Numlock=on" string inside /etc/sddm.conf

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

[digikam] [Bug 383912] AppImage crashes when started in terminal with 'debug' option

[bugzilla_noreply]

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

--- Comment #11 from caulier.gil...@gmail.com ---
Well, Marcel recommend to catch C++ exception to handle all problems report by
Exiv2.

Of course we can disabling this behavior now.

Gilles

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

[kwin] [Bug 383966] Missing QPlatformIntegration::queryKeyboardModifiers() implementation

[Martin Flöser]

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

Martin Flöser  changed:

   What|Removed |Added

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

--- Comment #2 from Martin Flöser  ---
I'm sorry, but this is out of scope for KWin. This is functionality which needs
to be added in QtWayland.

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

[kwin] [Bug 383965] Kwin crashes while debugging an opengl app in qtcreator

[Martin Flöser]

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

Martin Flöser  changed:

   What|Removed |Added

 Resolution|--- |BACKTRACE
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #1 from Martin Flöser  ---
As with all Arch backtraces: it's lacking debug symbols, thus we cannot see
where it crashes and there is nothing we can do to investigate. Please complain
to Arch for not providing debug symbols.

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

[krita] [Bug 383967] New: Scary output (crash?) after closing krita.

[wolthera]

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

Bug ID: 383967
   Summary: Scary output (crash?) after closing krita.
   Product: krita
   Version: git master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Animation
  Assignee: krita-bugs-n...@kde.org
  Reporter: griffinval...@gmail.com
  Target Milestone: ---

I had just attempted to render an animation, which failed so I closed krita...
clsoing went fine, but this showed up ni the terminal...

*** Error in `krita': free(): invalid pointer: 0x7ffdd5a698a0 ***
=== Backtrace: =
/lib/x86_64-linux-gnu/libc.so.6(+0x777e5)[0x7fcd91a257e5]
/lib/x86_64-linux-gnu/libc.so.6(+0x8037a)[0x7fcd91a2e37a]
/lib/x86_64-linux-gnu/libc.so.6(cfree+0x4c)[0x7fcd91a3253c]
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5(_ZN14QObjectPrivate14deleteChildrenEv+0x63)[0x7fcd925bc703]
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5(_ZN7QWidgetD1Ev+0x384)[0x7fcd92f37234]
/home/wolthera/krita/inst/lib/x86_64-linux-gnu/libkritawidgetutils.so.16(_ZN11KMainWindowD1Ev+0xe1)[0x7fcd9370f5a1]
/home/wolthera/krita/inst/lib/x86_64-linux-gnu/libkritaui.so.16(_ZN13KisMainWindowD1Ev+0x1aa)[0x7fcd94117c9a]
/home/wolthera/krita/inst/lib/x86_64-linux-gnu/libkritaui.so.16(_ZN13KisMainWindowD0Ev+0x9)[0x7fcd94117d39]
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5(_ZN7QObject5eventEP6QEvent+0x120)[0x7fcd925bfc90]
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5(_ZN7QWidget5eventEP6QEvent+0x853)[0x7fcd92f3bd33]
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5(_ZN11QMainWindow5eventEP6QEvent+0x16b)[0x7fcd9302d1cb]
/home/wolthera/krita/inst/lib/x86_64-linux-gnu/libkritawidgetutils.so.16(_ZN11KMainWindow5eventEP6QEvent+0x57)[0x7fcd937114f7]
/home/wolthera/krita/inst/lib/x86_64-linux-gnu/libkritawidgetutils.so.16(_ZN13KXmlGuiWindow5eventEP6QEvent+0x29)[0x7fcd93749919]
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5(_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent+0x9c)[0x7fcd92efa3fc]
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5(_ZN12QApplication6notifyEP7QObjectP6QEvent+0x257)[0x7fcd92f01e07]
/home/wolthera/krita/inst/lib/x86_64-linux-gnu/libkritaui.so.16(_ZN14KisApplication6notifyEP7QObjectP6QEvent+0x27)[0x7fcd940e5507]
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5(_ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent+0x108)[0x7fcd92592798]
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x2db)[0x7fcd92594f7b]
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5(+0x2d8323)[0x7fcd925e8323]
/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x2a7)[0x7fcd8ac02197]
/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4a3f0)[0x7fcd8ac023f0]
/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c)[0x7fcd8ac0249c]
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x5f)[0x7fcd925e792f]
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0xfa)[0x7fcd925907ca]
/home/wolthera/krita/inst/lib/x86_64-linux-gnu/kritaplugins/kritavideoexport.so(+0xdca8)[0x7fcd64ae2ca8]
/home/wolthera/krita/inst/lib/x86_64-linux-gnu/kritaplugins/kritavideoexport.so(_ZN10VideoSaver6encodeERK7QString18KisPinnedSharedPtrI26KisPropertiesConfigurationE+0xc4a)[0x7fcd64ae011a]
/home/wolthera/krita/inst/lib/x86_64-linux-gnu/kritaplugins/kritavideoexport.so(+0x967c)[0x7fcd64ade67c]
/home/wolthera/krita/inst/lib/x86_64-linux-gnu/kritaplugins/kritaanimationrenderer.so(+0xc0b9)[0x7fcd4aafd0b9]
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5(_ZN11QMetaObject8activateEP7QObjectiiPPv+0x679)[0x7fcd925bec19]
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5(_ZN7QAction9triggeredEb+0x42)[0x7fcd92ef3f22]
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5(_ZN7QAction8activateENS_11ActionEventE+0x110)[0x7fcd92ef6630]
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5(+0x2b23ea)[0x7fcd930523ea]
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5(+0x2b9826)[0x7fcd93059826]
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5(_ZN5QMenu17mouseReleaseEventEP11QMouseEvent+0x1d0)[0x7fcd9305a7c0]
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5(_ZN7QWidget5eventEP6QEvent+0x1f8)[0x7fcd92f3b6d8]
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5(_ZN5QMenu5eventEP6QEvent+0xa3)[0x7fcd9305cc73]
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5(_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent+0x9c)[0x7fcd92efa3fc]
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5(_ZN12QApplication6notifyEP7QObjectP6QEvent+0xe7b)[0x7fcd92f02a2b]
/home/wolthera/krita/inst/lib/x86_64-linux-gnu/libkritaui.so.16(_ZN14KisApplication6notifyEP7QObjectP6QEvent+0x27)[0x7fcd940e5507]
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5(_ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent+0x108)[0x7fcd92592798]

[kwin] [Bug 374881] Lags when resizing Qt4 windows on Wayland

[Martin Flöser]

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

Martin Flöser  changed:

   What|Removed |Added

URL||https://phabricator.kde.org
   ||/D7524
  Flags||ReviewRequest+

--- Comment #5 from Martin Flöser  ---
Workaround at: https://phabricator.kde.org/D7524

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

[peruse] [Bug 381491] Copyright inconsistencies

[clivej]

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

--- Comment #4 from clivej  ---
Will you make a new release with this commit included?

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

[krdc] [Bug 383870] KRDC cannot connect to VNC server with RFB version 3.8

[Urs Wolfer]

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

Urs Wolfer  changed:

   What|Removed |Added

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

--- Comment #1 from Urs Wolfer  ---
Yes, this should be reported against libvncserver. Please post the link here
after reporting it.

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

[kwin] [Bug 383966] Missing QPlatformIntegration::queryKeyboardModifiers() implementation

[Elvis Angelaccio]

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

--- Comment #1 from Elvis Angelaccio  ---
For some context, see comments in https://phabricator.kde.org/D7519

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

[kwin] [Bug 383966] New: Missing QPlatformIntegration::queryKeyboardModifiers() implementation

[Elvis Angelaccio]

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

Bug ID: 383966
   Summary: Missing QPlatformIntegration::queryKeyboardModifiers()
implementation
   Product: kwin
   Version: 5.10.4
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: platform-wayland
  Assignee: kwin-bugs-n...@kde.org
  Reporter: elvis.angelac...@kde.org
  Target Milestone: ---

QGuiApplication::queryKeyboardModifiers() (which calls
QPlatformIntegration::queryKeyboardModifiers()) does not work on wayland (or
better, the default implementation, which just call
QGuiApplication::keyboardModifiers(), gets called).

Not sure if the re-implementation should be done by the kwin QPA (as it also
doesn't work with weston), but I can't find an equivalent of QXcbIntegration in
qtwayland.

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

[kwin] [Bug 383965] New: Kwin crashes while debugging an opengl app in qtcreator

[Artur K .]

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

Bug ID: 383965
   Summary: Kwin crashes while debugging an opengl app in
qtcreator
   Product: kwin
   Version: 5.10.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: nemer...@gmail.com
  Target Milestone: ---

Application: kwin_x11 (5.10.4)

Qt Version: 5.9.1
Frameworks Version: 5.37.0
Operating System: Linux 4.12.8-2-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
Attempted to 'kill' debugged application after it crashed. Switched window to
the application - kwin crashed as a result.

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

Thread 6 (Thread 0x7f3ea8938700 (LWP 855)):
#0  0x7f3f64f841ad in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f3f691bc5ec in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f3f64171ae8 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7f3f64171f4a in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f3f691bb15b in  () at /usr/lib/libQt5Core.so.5
#5  0x7f3f64f7e049 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f3f6bdedf0f in clone () at /usr/lib/libc.so.6

Thread 5 (Thread 0x7f3eb8eeb700 (LWP 748)):
#0  0x7f3f6bde3f76 in ppoll () at /usr/lib/libc.so.6
#1  0x7f3f693f4ba3 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2  0x7f3f693f633f in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7f3f6939cffb in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7f3f691b640e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7f3f63a7f1d5 in  () at /usr/lib/libQt5Qml.so.5
#6  0x7f3f691bb15b in  () at /usr/lib/libQt5Core.so.5
#7  0x7f3f64f7e049 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f3f6bdedf0f in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7f3f3bfff700 (LWP 663)):
#0  0x7f3f64f841ad in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f3f68313b04 in  () at /usr/lib/libQt5Script.so.5
#2  0x7f3f68313b49 in  () at /usr/lib/libQt5Script.so.5
#3  0x7f3f64f7e049 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f3f6bdedf0f in clone () at /usr/lib/libc.so.6

Thread 3 (Thread 0x7f3f498fe700 (LWP 655)):
#0  0x7f3f6bde3f76 in ppoll () at /usr/lib/libc.so.6
#1  0x7f3f693f4ba3 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2  0x7f3f693f633f in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7f3f6939cffb in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7f3f691b640e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7f3f63a7f1d5 in  () at /usr/lib/libQt5Qml.so.5
#6  0x7f3f691bb15b in  () at /usr/lib/libQt5Core.so.5
#7  0x7f3f64f7e049 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f3f6bdedf0f in clone () at /usr/lib/libc.so.6

Thread 2 (Thread 0x7f3f4bfff700 (LWP 619)):
#0  0x7f3f6bde3f76 in ppoll () at /usr/lib/libc.so.6
#1  0x7f3f693f4ba3 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2  0x7f3f693f633f in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7f3f6939cffb in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7f3f691b640e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7f3f62c22396 in  () at /usr/lib/libQt5DBus.so.5
#6  0x7f3f691bb15b in  () at /usr/lib/libQt5Core.so.5
#7  0x7f3f64f7e049 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f3f6bdedf0f in clone () at /usr/lib/libc.so.6

Thread 1 (Thread 0x7f3f6c424840 (LWP 591)):
[KCrash Handler]
#5  0x0050 in  ()
#6  0x7f3f6b8c893d in KWin::Workspace::constrainedStackingOrder() () at
/usr/lib/libkwin.so.5
#7  0x7f3f6b8c9721 in KWin::Workspace::updateStackingOrder(bool) () at
/usr/lib/libkwin.so.5
#8  0x7f3f6b8c9ac1 in KWin::Workspace::blockStackingUpdates(bool) () at
/usr/lib/libkwin.so.5
#9  0x7f3f6b870294 in KWin::Client::destroyClient() () at
/usr/lib/libkwin.so.5
#10 0x7f3f6b8d9bff in
KWin::Client::unmapNotifyEvent(xcb_unmap_notify_event_t*) () at
/usr/lib/libkwin.so.5
#11 0x7f3f6b8dd904 in KWin::Client::windowEvent(xcb_generic_event_t*) () at
/usr/lib/libkwin.so.5
#12 0x7f3f6b8ded60 in KWin::Workspace::workspaceEvent(xcb_generic_event_t*)
() at /usr/lib/libkwin.so.5
#13 0x7f3f6939ba1f in
QAbstractEventDispatcher::filterNativeEvent(QByteArray const&, void*, long*) ()
at 

[plasmashell] [Bug 383964] Going online on Instant Messaging Widget crashes plasma

[Bertoche]

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

--- Comment #1 from Bertoche  ---
Created attachment 107502
  --> https://bugs.kde.org/attachment.cgi?id=107502=edit
instant-messaging-toaster

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

[plasmashell] [Bug 383964] New: Going online on Instant Messaging Widget crashes plasma

[Bertoche]

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

Bug ID: 383964
   Summary: Going online on Instant Messaging Widget crashes
plasma
   Product: plasmashell
   Version: 5.10.4
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: raphly...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.10.4)

Qt Version: 5.9.1
Frameworks Version: 5.36.0
Operating System: Linux 4.7.4-2.g6a5bbb1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:
I had just gone offline and then logged in again trying to update the contact
list.
I logged in clicking on a "Go Online" button on the toaster that appears after
clicking on the instant messaging icon. I'll attach a screenshot.
It's been crashing every time I do that. It also crashes while logging in
through other ways, though less consistently so. I'll attach another traceback
if there's any changes on it.
Plasma shell panels go away for a few seconds and then get back running without
furter issues; KDE and Plasma instant messaging features work as if nothing
ever happened.

I've found a bunch of correlations between the stacks of some of the threads
here and the ones at 348653, which is quite similar:
#0 read() at Thread 16 at 348653 <-> Thread 11 here
#0 poll() at Thread 15 at 348653 <->> Thread 4 here
#0 g_mutex_unlock at Thread 14 at 348653 <-> Thread 5 here, if
g_main_context_prepare ≃ g_main_context_check
#0 g_mutex_unlock at Thread 35 at 348653 <-> Thread 6 here, if
g_main_context_prepare ≃ g_main_context_check
#0 pthread_cond_wait at Thread 27,36  <-> Threads 14, 15 here

- Custom settings of the application:
I've got a bunch of widgets running, though not too many. I'm currenlty logged
in to g66gle account.

The crash can be reproduced every time.

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

Thread 15 (Thread 0x7f9fe2cab700 (LWP 28758)):
#0  0x7fa0b43465dd in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fa0b517a04b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7fa0b8ee1958 in QSGRenderThread::processEventsAndWaitForMore() () at
/usr/lib64/libQt5Quick.so.5
#3  0x7fa0b8ee1d8a in QSGRenderThread::run() () at
/usr/lib64/libQt5Quick.so.5
#4  0x7fa0b5178d2e in QThreadPrivate::start(void*) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fa0b43404d7 in start_thread () at /lib64/libpthread.so.0
#6  0x7fa0b4a86b2f in clone () at /lib64/libc.so.6

Thread 14 (Thread 0x7f9fd0c27700 (LWP 28357)):
#0  0x7fa0b43465dd in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fa0b517a04b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7fa0b8ee1958 in QSGRenderThread::processEventsAndWaitForMore() () at
/usr/lib64/libQt5Quick.so.5
#3  0x7fa0b8ee1d8a in QSGRenderThread::run() () at
/usr/lib64/libQt5Quick.so.5
#4  0x7fa0b5178d2e in QThreadPrivate::start(void*) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fa0b43404d7 in start_thread () at /lib64/libpthread.so.0
#6  0x7fa0b4a86b2f in clone () at /lib64/libc.so.6

Thread 13 (Thread 0x7f9fdf368700 (LWP 27980)):
#0  0x7fa0b43465dd in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fa0b517a04b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7fa0b8ee1958 in QSGRenderThread::processEventsAndWaitForMore() () at
/usr/lib64/libQt5Quick.so.5
#3  0x7fa0b8ee1d8a in QSGRenderThread::run() () at
/usr/lib64/libQt5Quick.so.5
#4  0x7fa0b5178d2e in QThreadPrivate::start(void*) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fa0b43404d7 in start_thread () at /lib64/libpthread.so.0
#6  0x7fa0b4a86b2f in clone () at /lib64/libc.so.6

Thread 12 (Thread 0x7f9fe08a4700 (LWP 27977)):
#0  0x7fa0b43465dd in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fa0b517a04b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7fa0b8ee1958 in QSGRenderThread::processEventsAndWaitForMore() () at
/usr/lib64/libQt5Quick.so.5
#3  0x7fa0b8ee1d8a in QSGRenderThread::run() () at
/usr/lib64/libQt5Quick.so.5
#4  0x7fa0b5178d2e in QThreadPrivate::start(void*) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fa0b43404d7 in start_thread () at /lib64/libpthread.so.0
#6  0x7fa0b4a86b2f in clone () at /lib64/libc.so.6

Thread 11 (Thread 0x7f9fe34ac700 (LWP 27973)):
#0  0x7fa0b4a78efd in read () at /lib64/libc.so.6
#1  0x7fa0afa3b840 in  () at 

[frameworks-baloo] [Bug 383961] Application launcher searches don't show compressed files

[Alberto Salvia Novella]

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

Alberto Salvia Novella  changed:

   What|Removed |Added

   Keywords||usability

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

[frameworks-baloo] [Bug 383961] Application launcher searches don't show compressed files

[Alberto Salvia Novella]

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

Alberto Salvia Novella  changed:

   What|Removed |Added

 CC||es204904...@gmail.com

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

[k3b] [Bug 383931] DVD extraction fails

[Dr . Chapatin]

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

--- Comment #5 from Dr. Chapatin  ---
Created attachment 107501
  --> https://bugs.kde.org/attachment.cgi?id=107501=edit
nero disc speed

Thanks Leslie and Jim.

My system is Antergos, my mencoder is 37916-2 from Arch repositories.
I tested three discs on K3b, all dvd video, and always I get the same fail.
I tried rip one of the discs with handbrake, but rip process failed at 27%.
I tried rip the same disc using handbrake on windows 7 installed on the same
hardware: failed at 27% too.
Again in windows 7 I ran a disc surface test with nero disc speed: no problem
found (see the screenshot).
I tried rip the same disc on windows 7 using ConvertXtoVideo Ultimate software:
whole disc was ripped without any problem.

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

[systemsettings] [Bug 383962] The Num Block key status isn't remembered between sessions

[Alberto Salvia Novella]

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

Alberto Salvia Novella  changed:

   What|Removed |Added

 CC||es204904...@gmail.com

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

[systemsettings] [Bug 373646] NUMLOCK configuration not taken into account

[Alberto Salvia Novella]

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

Alberto Salvia Novella  changed:

   What|Removed |Added

 Depends on||383962


Referenced Bugs:

https://bugs.kde.org/show_bug.cgi?id=383962
[Bug 383962] The Num Block key status isn't remembered between sessions
-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 383962] The Num Block key status isn't remembered between sessions

[Alberto Salvia Novella]

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

Alberto Salvia Novella  changed:

   What|Removed |Added

   Keywords||usability
 Blocks||368063, 373646


Referenced Bugs:

https://bugs.kde.org/show_bug.cgi?id=368063
[Bug 368063] NumLock not turned on
https://bugs.kde.org/show_bug.cgi?id=373646
[Bug 373646] NUMLOCK configuration not taken into account
-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 368063] NumLock not turned on

[Alberto Salvia Novella]

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

Alberto Salvia Novella  changed:

   What|Removed |Added

 Depends on||383962


Referenced Bugs:

https://bugs.kde.org/show_bug.cgi?id=383962
[Bug 383962] The Num Block key status isn't remembered between sessions
-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 383912] AppImage crashes when started in terminal with 'debug' option

[Simon]

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

--- Comment #10 from Simon  ---
On OpenSUSE you use the AppImage as well?

And you can debug without having to press a button for every mp4 file, just use
the workaround I gave in comment #8.

I am however curious about the reason why "catch throw" is activated
automatically in AppImage (@Gilles).

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

[systemsettings] [Bug 373646] NUMLOCK configuration not taken into account

[Alberto Salvia Novella]

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

--- Comment #3 from Alberto Salvia Novella  ---
Related bug: The Num Block key status isn't remembered between sessions:
(https://bugs.kde.org/show_bug.cgi?id=383962)

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

[systemsettings] [Bug 368063] NumLock not turned on

[Alberto Salvia Novella]

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

--- Comment #3 from Alberto Salvia Novella  ---
Related bug: The Num Block key status isn't remembered between sessions:
(https://bugs.kde.org/show_bug.cgi?id=383962)

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

[systemsettings] [Bug 383962] The Num Block key status isn't remembered between sessions

[Alberto Salvia Novella]

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

--- Comment #1 from Alberto Salvia Novella  ---
Related bugs:
- NumLock doesn't follow BIOS setting
(https://bugs.kde.org/show_bug.cgi?id=368063)
- Numblock doesn't follow settings
(https://bugs.kde.org/show_bug.cgi?id=373646)

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

[frameworks-baloo] [Bug 383961] Application launcher searches don't show compressed files

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

Product|plasmashell |frameworks-baloo
   Target Milestone|1.0 |---
  Component|Application Launcher|general
   |(Kickoff)   |
   Assignee|k...@davidedmundson.co.uk|pinak.ah...@gmail.com
Version|5.10.4  |unspecified

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

[kate] [Bug 383963] New: Kate is not opening current folder when it's remote (KIO, sftp)

[Charles]

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

Bug ID: 383963
   Summary: Kate is not opening current folder when it's remote
(KIO, sftp)
   Product: kate
   Version: 17.04.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: application
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: charles.vej...@yale.edu
  Target Milestone: ---

Hi,

When I open a remote folder in Kate (sftp://) and open some file from there, it
works. If I click to open a file again then the dialog open my local home and
not the remote folder.

Reproducible: Always

Steps to Reproduce:
1) Open remote file with Kate
2) Try to open a second file.

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

[kaffeine] [Bug 374693] kaffeine does not tune into some dvb-s channels

[bugzilla_noreply]

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

--- Comment #42 from julius...@gmail.com ---
i tested with the latest kaffeine and can confirm that this bug is solved.
Since this is a general feature, it also affects other programs. Does it make
sense to mention this at other places? for instance, the same thing affects
w_scan, where i could not find the higher voltage option yet.

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

[systemsettings] [Bug 383962] The Num Block key status isn't remembered between sessions

[Alberto Salvia Novella]

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

Alberto Salvia Novella  changed:

   What|Removed |Added

   Platform|Other   |Manjaro

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

[systemsettings] [Bug 383962] New: The Num Block key status isn't remembered between sessions

[Alberto Salvia Novella]

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

Bug ID: 383962
   Summary: The Num Block key status isn't remembered between
sessions
   Product: systemsettings
   Version: 5.10.4
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: kcm_keyboard
  Assignee: unassigned-b...@kde.org
  Reporter: es204904...@gmail.com
  Target Milestone: ---

HOW TO REPRODUCE:
1. Turn the num block key on.
2. Reboot and log in again.

RESULT:
- The key is off, where it should be as in the last session.
- This small think forces you to think if the num block is turned on every time
you use the numerical keyboard. Due to its frequency it's quite annoying.

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

[plasmashell] [Bug 383583] Display scale is not applied consistently to mouse pointer

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

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

--- Comment #2 from David Edmundson  ---
Fixed in wayland. 
Can't feasibly fix in X.

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

[frameworks-kcoreaddons] [Bug 361426] Crash in KIconLoaderPrivate::findCachedPixmapWithPath and KSharedDataCache

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

 CC||nougu...@orange.fr

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

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