[kmail2] [Bug 372850] New: KMail crashes on startup

2016-11-23 Thread Peter Grobarcik
https://bugs.kde.org/show_bug.cgi?id=372850

Bug ID: 372850
   Summary: KMail crashes on startup
   Product: kmail2
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: coder.peter.grobar...@gmail.com
  Target Milestone: ---

Application: kmail (5.3.3 (QtWebEngine))

Qt Version: 5.7.0
Frameworks Version: 5.29.0
Operating System: Linux 4.4.0-47-generic x86_64
Distribution: KDE neon Developer Edition

-- Information about the crash:
I just booted up after an update. The update crpled kdepim. None action taken
yet.

-- Backtrace:
Application: KMail (kmail), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fe1805cfa00 (LWP 6210))]

Thread 3 (Thread 0x7fe17575f700 (LWP 6213)):
#0  0x7fe1b0a6d81e in timerSourcePrepareHelper (timeout=0x7fe17575e9f4,
src=) at kernel/qeventdispatcher_glib.cpp:133
#1  timerSourcePrepare (source=, timeout=0x7fe17575e9f4) at
kernel/qeventdispatcher_glib.cpp:165
#2  0x7fe1a4eba92d in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fe1a4ebb2cb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fe1a4ebb4ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fe1b0a6e23b in QEventDispatcherGlib::processEvents
(this=0x7fe1680008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#6  0x7fe1b0a18cea in QEventLoop::exec (this=this@entry=0x7fe17575ebc0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:210
#7  0x7fe1b083dfb4 in QThread::exec (this=) at
thread/qthread.cpp:507
#8  0x7fe1b0842b98 in QThreadPrivate::start (arg=0x29a2ad0) at
thread/qthread_unix.cpp:344
#9  0x7fe1a6a0070a in start_thread (arg=0x7fe17575f700) at
pthread_create.c:333
#10 0x7fe1aff3982d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7fe176970700 (LWP 6212)):
#0  0x7fe1aff2db5d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fe1a4ebb39c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fe1a4ebb4ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fe1b0a6e23b in QEventDispatcherGlib::processEvents
(this=0x7fe178c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7fe1b0a18cea in QEventLoop::exec (this=this@entry=0x7fe17696fb90,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:210
#5  0x7fe1b083dfb4 in QThread::exec (this=this@entry=0x7fe1b2b66d60
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread.cpp:507
#6  0x7fe1b2af27a5 in QDBusConnectionManager::run (this=0x7fe1b2b66d60
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:196
#7  0x7fe1b0842b98 in QThreadPrivate::start (arg=0x7fe1b2b66d60 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:344
#8  0x7fe1a6a0070a in start_thread (arg=0x7fe176970700) at
pthread_create.c:333
#9  0x7fe1aff3982d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7fe1805cfa00 (LWP 6210)):
[KCrash Handler]
#6  0x7fe1afe68428 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
#7  0x7fe1afe6a02a in __GI_abort () at abort.c:89
#8  0x7fe1afeaa7ea in __libc_message (do_abort=2,
fmt=fmt@entry=0x7fe1affc32e0 "*** Error in `%s': %s: 0x%s ***\n") at
../sysdeps/posix/libc_fatal.c:175
#9  0x7fe1afeb481e in malloc_printerr (ar_ptr=0x7fe1b01f6b20 ,
ptr=0x29d7ce0, str=0x7fe1affc0142 "malloc(): memory corruption",
action=) at malloc.c:5004
#10 _int_malloc (av=av@entry=0x7fe1b01f6b20 ,
bytes=bytes@entry=1162) at malloc.c:3472
#11 0x7fe1afeb65d4 in __GI___libc_malloc (bytes=bytes@entry=1162) at
malloc.c:2911
#12 0x7fe1b0843e32 in QArrayData::allocate (objectSize=objectSize@entry=2,
alignment=alignment@entry=8, capacity=capacity@entry=569,
options=options@entry=...) at tools/qarraydata.cpp:114
#13 0x7fe1b08cdbe8 in QTypedArrayData::allocate
(options=..., capacity=569) at
../../include/QtCore/../../src/corelib/tools/qarraydata.h:222
#14 QString::fromLatin1_helper (str=str@entry=0x7fe1b0ae44e0 
"ZzzzArabCyrlDsrtGuruHansHantLatnMongTfngArmnBengCherDevaEthiGeorGrekGujrHebrJpanKhmrKndaKoreLaooMlymMymrOryaTamlTeluThaaThaiTibtSinhSyrcYiiiVaiiAvstBaliBamuBatkBopoBrahBugiBuhdCansCariCakmChamCoptCprt"...,
size=size@entry=568) at tools/qstring.cpp:4654
#15 0x7fe1b08a4bf1 in QString::fromLatin1 (str=,
size=568) at ../../include/QtCore/../../src/corelib/tools/qstring.h:538
#16 qt_splitLocaleName (name=..., lang=..., script=..., cntry=...) at
tools/qlocale.cpp:434
#17 0x7fe1b08eaab3 in QSystemLocale::query (this=,
type=, in=...) at 

[konsole] [Bug 371599] Konsole crashed with multiple Konsole / tabs

2016-11-26 Thread Peter Wu
https://bugs.kde.org/show_bug.cgi?id=371599

--- Comment #2 from Peter Wu <pe...@lekensteyn.nl> ---
Possibly related to bug 372401 (and duplicates).

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

[pimsettingexporter] [Bug 372598] New: PIM Setting Exporter not backing up all Local Folders

2016-11-17 Thread Peter XP
https://bugs.kde.org/show_bug.cgi?id=372598

Bug ID: 372598
   Summary: PIM Setting Exporter not backing up all Local Folders
   Product: pimsettingexporter
   Version: unspecified
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mon...@kde.org
  Reporter: p.wibber...@btinternet.com
  Target Milestone: ---

Created attachment 102280
  --> https://bugs.kde.org/attachment.cgi?id=102280=edit
Screenshot of Kmail, showing the Local Folders and of Ark, showing the mail.zip
contents

PIM Setting Exporter 4.14.2

'Tools'-'Export Kmail Data'-'Back Up Data' successfully creates a zip file. 
However, the mail.zip file contained with the back up zip file appears to
contain only some of the Local Folders (see attachment).  I cannot see any
obvious property to distinguish the folders that get backed up from the ones
that don't.  

Thank you and regards

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

[pimsettingexporter] [Bug 372598] PIM Setting Exporter not backing up all Local Folders

2016-11-17 Thread Peter XP
https://bugs.kde.org/show_bug.cgi?id=372598

--- Comment #1 from Peter XP <p.wibber...@btinternet.com> ---
Linux Mint 17.3
Qt 4.8.6
KDE Development Platform 4.14.2
PIM Setting Exporter 4.14.2

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

[Spectacle] [Bug 367907] spectacle segfault

2016-11-12 Thread Peter Wu
https://bugs.kde.org/show_bug.cgi?id=367907

--- Comment #6 from Peter Wu <pe...@lekensteyn.nl> ---
Can you configure coredumps such that a backtrace can be obtained? It is really
difficult to investigate this otherwise.

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

[plasmashell] [Bug 371992] New: Plasma 5 crashed

2016-11-02 Thread Peter Ullinger
https://bugs.kde.org/show_bug.cgi?id=371992

Bug ID: 371992
   Summary: Plasma 5 crashed
   Product: plasmashell
   Version: 5.8.2
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: peter.ullin...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.2)

Qt Version: 5.7.0
Frameworks Version: 5.27.0
Operating System: Linux 4.4.27-2-MANJARO x86_64
Distribution: "Manjaro Linux"

-- Information about the crash:
- Custom settings of the application:
I was tinkering with the new Now Dock from the KDE Store as a plasmoid when
Plasma crashed.

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

Thread 20 (Thread 0x7fb44af73700 (LWP 20513)):
#0  0x7fb547f7610f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fb548e61c2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fb48f73e1c0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7fb48f742988 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7fb48f73d263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7fb48f7429e2 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#6  0x7fb48f73d263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#7  0x7fb48f7429e2 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#8  0x7fb48f73d263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#9  0x7fb48f7401f9 in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#10 0x7fb548e60d78 in  () at /usr/lib/libQt5Core.so.5
#11 0x7fb547f70454 in start_thread () at /usr/lib/libpthread.so.0
#12 0x7fb5487767df in clone () at /usr/lib/libc.so.6

Thread 19 (Thread 0x7fb44b774700 (LWP 20512)):
#0  0x7fb547f7610f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fb548e61c2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fb48f73e1c0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7fb48f742988 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7fb48f73d263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7fb48f7429e2 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#6  0x7fb48f73d263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#7  0x7fb48f7401f9 in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#8  0x7fb548e60d78 in  () at /usr/lib/libQt5Core.so.5
#9  0x7fb547f70454 in start_thread () at /usr/lib/libpthread.so.0
#10 0x7fb5487767df in clone () at /usr/lib/libc.so.6

Thread 18 (Thread 0x7fb44bf75700 (LWP 20511)):
#0  0x7fb547f7610f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fb548e61c2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fb48f73e1c0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7fb48f742988 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7fb48f73d263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7fb48f7429e2 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#6  0x7fb48f73d263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#7  0x7fb48f7429e2 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#8  0x7fb48f73d263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#9  0x7fb48f7401f9 in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#10 0x7fb548e60d78 in  () at /usr/lib/libQt5Core.so.5
#11 0x7fb547f70454 in start_thread () at /usr/lib/libpthread.so.0
#12 0x7fb5487767df in clone () at /usr/lib/libc.so.6

Thread 17 (Thread 0x7fb44c776700 (LWP 20510)):
#0  0x7fb547f7610f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fb548e61c2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fb48f73e1c0 in

[konversation] [Bug 370637] Crash exiting Konversation

2016-10-30 Thread Peter Simonsson
https://bugs.kde.org/show_bug.cgi?id=370637

Peter Simonsson <peter.simons...@gmail.com> changed:

   What|Removed |Added

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

--- Comment #1 from Peter Simonsson <peter.simons...@gmail.com> ---


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

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

[konversation] [Bug 364899] konversation5 crashes on exit

2016-10-30 Thread Peter Simonsson
https://bugs.kde.org/show_bug.cgi?id=364899

Peter Simonsson <peter.simons...@gmail.com> changed:

   What|Removed |Added

 CC||luke-jr+kdeb...@utopios.org

--- Comment #6 from Peter Simonsson <peter.simons...@gmail.com> ---
*** Bug 370637 has been marked as a duplicate of this bug. ***

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

[Spectacle] [Bug 371843] selection rectangle can be too tiny which causes it to become buggy

2016-11-02 Thread Peter Wu
https://bugs.kde.org/show_bug.cgi?id=371843

Peter Wu <pe...@lekensteyn.nl> changed:

   What|Removed |Added

 CC||pe...@lekensteyn.nl
 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #1 from Peter Wu <pe...@lekensteyn.nl> ---
The resize handles are deliberately not shown when the box becomes too small.

Not being able to resize vertically is a bit odd, I can confirm this: create a
small rectangle, resize is to make it much wider. Observe that vertical
resizing does not work however.

Workaround: just create a new selection (this is what I normally do when I
accidentally create a too small selection).

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

[Spectacle] [Bug 371768] Screenshot of "Window under cursor" of plasma applet show other part of the desktop

2016-11-02 Thread Peter Wu
https://bugs.kde.org/show_bug.cgi?id=371768

Peter Wu <pe...@lekensteyn.nl> changed:

   What|Removed |Added

 CC||pe...@lekensteyn.nl

--- Comment #1 from Peter Wu <pe...@lekensteyn.nl> ---
It is probably working as intended. Your "Window" is not really a new window,
but a "window" part of the Plasma desktop. The "Window under cursor" option
shows all windows belonging to the application.

Ticking the "Pop-up" only box might help, but in some cases it would capture
only menus for example.

Just to be sure, can you try to reproduce your issue with the latest git
version?
git://anongit.kde.org/spectacle.git

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

[kwordquiz] [Bug 371711] New: Save file problem

2016-10-26 Thread Peter Mueller
https://bugs.kde.org/show_bug.cgi?id=371711

Bug ID: 371711
   Summary: Save file problem
   Product: kwordquiz
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: pe...@peterandlinda.com
  Reporter: elektrotechnik2...@outlook.com
  Target Milestone: ---

"Unknown file type" when saving a file. Occurs after Ubuntu update to LTE 16.

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

[konversation] [Bug 372493] right click to ignore does not work

2016-11-26 Thread Peter Simonsson
https://bugs.kde.org/show_bug.cgi?id=372493

Peter Simonsson <peter.simons...@gmail.com> changed:

   What|Removed |Added

 CC||peter.simons...@gmail.com

--- Comment #1 from Peter Simonsson <peter.simons...@gmail.com> ---
Hmm, I'm unable to reproduce this on master, does this happen for all nicks?

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

[konversation] [Bug 354263] It moves to different area on desktop every time I click on it in system tray

2016-11-26 Thread Peter Simonsson
https://bugs.kde.org/show_bug.cgi?id=354263

Peter Simonsson <peter.simons...@gmail.com> changed:

   What|Removed |Added

 CC||peter.simons...@gmail.com

--- Comment #1 from Peter Simonsson <peter.simons...@gmail.com> ---
Can't reproduce it here, which desktop are you using?

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

[kwin] [Bug 373412] New: Kwin crash at login

2016-12-07 Thread Peter Fodrek
https://bugs.kde.org/show_bug.cgi?id=373412

Bug ID: 373412
   Summary: Kwin crash at login
   Product: kwin
   Version: 5.8.4
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: peter.fod...@stuba.sk
  Target Milestone: ---

Application: kwin_x11 (5.8.4)

Qt Version: 5.7.0
Frameworks Version: 5.28.0
Operating System: Linux 4.8.12-1-default x86_64
Distribution: "openSUSE Tumbleweed"

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

- Unusual behavior I noticed:

after upgrade to Opensuse KDE 16.11.90 crash of akonmadi at stop after long run
and mysql not shutdown correctly

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

Thread 5 (Thread 0x7f5db3fff700 (LWP 2551)):
#0  0x7f5dcdbff10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f5dd0f2e834 in  () at /usr/lib64/libQt5Script.so.5
#2  0x7f5dd0f2e879 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7f5dca556754 in  () at /usr/lib64/libGL.so.1
#4  0x7f5dcdbf9454 in start_thread () at /lib64/libpthread.so.0
#5  0x7f5dd48fc39f in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f5da3fff700 (LWP 2300)):
[KCrash Handler]
#6  0x7f5dd1e89119 in QDir::fromNativeSeparators(QString const&) () at
/usr/lib64/libQt5Core.so.5
#7  0x7f5dd1e9bf21 in QFileInfo::QFileInfo(QString const&) () at
/usr/lib64/libQt5Core.so.5
#8  0x7f5dd1f080ee in  () at /usr/lib64/libQt5Core.so.5
#9  0x7f5dd1f092b2 in  () at /usr/lib64/libQt5Core.so.5
#10 0x7f5dd1ea6706 in QLockFile::tryLock(int) () at
/usr/lib64/libQt5Core.so.5
#11 0x7f5dd3cb32c9 in  () at /usr/lib64/libKF5ConfigCore.so.5
#12 0x7f5dd3c9d0b0 in KConfig::sync() () at
/usr/lib64/libKF5ConfigCore.so.5
#13 0x7f5db28e5bf5 in  () at
/usr/lib64/qt5/plugins/org.kde.kwin.platforms/KWinX11Platform.so
#14 0x7f5dd1fa221e in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#15 0x7f5dd1fae828 in QTimer::timerEvent(QTimerEvent*) () at
/usr/lib64/libQt5Core.so.5
#16 0x7f5dd1fa2d13 in QObject::event(QEvent*) () at
/usr/lib64/libQt5Core.so.5
#17 0x7f5dd2c6b92c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQt5Widgets.so.5
#18 0x7f5dd2c730e1 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#19 0x7f5dd1f76200 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib64/libQt5Core.so.5
#20 0x7f5dd1fc971e in QTimerInfoList::activateTimers() () at
/usr/lib64/libQt5Core.so.5
#21 0x7f5dd1fc7688 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#22 0x7f5dd1f741ea in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#23 0x7f5dd1da28b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#24 0x7f5dd1da7558 in  () at /usr/lib64/libQt5Core.so.5
#25 0x7f5dca556754 in  () at /usr/lib64/libGL.so.1
#26 0x7f5dcdbf9454 in start_thread () at /lib64/libpthread.so.0
#27 0x7f5dd48fc39f in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f5db13d1700 (LWP 2299)):
#0  0x7fff821e5b12 in clock_gettime ()
#1  0x7f5dd4909246 in clock_gettime () at /lib64/libc.so.6
#2  0x7f5dd1e4c6e1 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f5dd1fc8419 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7f5dd1fc89c5 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f5dd1fc7704 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#6  0x7f5dd1f741ea in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#7  0x7f5dd1da28b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8  0x7f5dcc72aa75 in  () at /usr/lib64/libQt5Qml.so.5
#9  0x7f5dd1da7558 in  () at /usr/lib64/libQt5Core.so.5
#10 0x7f5dca556754 in  () at /usr/lib64/libGL.so.1
#11 0x7f5dcdbf9454 in start_thread () at /lib64/libpthread.so.0
#12 0x7f5dd48fc39f in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f5dbb9df700 (LWP 2223)):
#0  0x7f5dd48f368d in poll () at /lib64/libc.so.6
#1  0x7f5dc932c876 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f5dc932c98c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f5dd1fca77f in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f5dd1f741ea in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f5dd1da28b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f5dcb9033e5 in  () at /usr/lib64/libQt5DBus.so.5
#7  0x7f5dd1da7558 in  () at /usr/lib64/libQt5Core.so.5

[konsole] [Bug 373567] New: RHE: Add profile in bookmarks

2016-12-12 Thread Peter Tselios
https://bugs.kde.org/show_bug.cgi?id=373567

Bug ID: 373567
   Summary: RHE: Add profile in bookmarks
   Product: konsole
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: bookmark
  Assignee: konsole-de...@kde.org
  Reporter: s91...@yahoo.gr
  Target Milestone: ---

Currently the Bookmarks in Konsole are usefull, although they need some some as
another user already suggested. 
However, one the most annoying things for me with konsole is the fact that I
need to manually change the profile everytime I use bookmarks. 
So,my suggestion is to add a drop-down menu with currently set profiles and
associate one of them with the bookmark.

I hope that this change is not a difficult one and it go in production soon.

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

[Spectacle] [Bug 362061] Use popular shortcuts for Spectacle for sake of consistency with other environments

2016-12-06 Thread Peter Wu
https://bugs.kde.org/show_bug.cgi?id=362061

--- Comment #8 from Peter Wu <pe...@lekensteyn.nl> ---
There were no changes made to Spectacle. I think these are handled by KWin, but
not sure.

If you are going to implement this, you probably have to interface with DBus
(see dbus/org.kde.Spectacle.xml for the interface).

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

[krita] [Bug 373651] New: No web links work from within Krita 3.1.0

2016-12-14 Thread Peter Bowmar
https://bugs.kde.org/show_bug.cgi?id=373651

Bug ID: 373651
   Summary: No web links work from within Krita 3.1.0
   Product: krita
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: pbow...@yahoo.com
  Target Milestone: ---

Clicking any link in the Splash startup screen or from the Help menu
(including, ironically, the Launch Bug Report Wizard) results in an error in
the shell:

This application failed to start because it could not find or load the Qt
platform plugin "xcb"
in "".

Reinstalling the application may fix this problem.
/usr/bin/xdg-open: line 524:  5245 Aborted
kde-open${KDE_SESSION_VERSION} "$1"

This is using the .appimage directly on OpenSUSE 42.1 KDE desktop.

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

[korganizer] [Bug 317656] Korganizer alert reminders are not reliable (they're lost after logout)

2016-12-16 Thread Peter Gückel
https://bugs.kde.org/show_bug.cgi?id=317656

Peter Gückel <pguec...@gmail.com> changed:

   What|Removed |Added

 CC|pguec...@gmail.com  |

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

[marble] [Bug 373750] New: KDE Marble (Installed from openSUSE standard) breaks down when trying to import bookmarks from a previous installed Marble

2016-12-17 Thread Peter Jespersen
https://bugs.kde.org/show_bug.cgi?id=373750

Bug ID: 373750
   Summary: KDE Marble (Installed from openSUSE standard) breaks
down when trying to import bookmarks from a previous
installed Marble
   Product: marble
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: marble-b...@kde.org
  Reporter: flywh...@illogical.dk
  Target Milestone: ---

Application: marble (2.0.2 (stable release))

Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.4.36-8-default x86_64
Distribution: "openSUSE Leap 42.2"

-- Information about the crash:
- What I was doing when the application crashed: Trying to import bookmarks
from a previous installed Marble, using the import function in bookmarks
handling.

- Custom settings of the application:OSM as maps, otherwise I just installed
the damn thing five minutes ago, so its default settings.

The crash can be reproduced every time.

-- Backtrace:
Application: Marble virtuel globus (marble), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7ff201f128c0 (LWP 18277))]

Thread 12 (Thread 0x7ff164f3c700 (LWP 18399)):
#0  0x7ff1f4ff80af in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7ff1f77d493b in  () at /usr/lib64/libQt5Script.so.5
#2  0x7ff1f77d4969 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7ff1f4ff3734 in start_thread () at /lib64/libpthread.so.0
#4  0x7ff1f8033d3d in clone () at /lib64/libc.so.6

Thread 11 (Thread 0x7ff1677fe700 (LWP 18300)):
#0  0x7ff1f802751d in read () at /lib64/libc.so.6
#1  0x7ff1f47bd670 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7ff1f477ce49 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7ff1f477d2a8 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7ff1f477d42c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7ff1f8e4b32b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#6  0x7ff1f8df8fdb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#7  0x7ff1f8c33f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8  0x7ff1f8c389e9 in  () at /usr/lib64/libQt5Core.so.5
#9  0x7ff1f4ff3734 in start_thread () at /lib64/libpthread.so.0
#10 0x7ff1f8033d3d in clone () at /lib64/libc.so.6

Thread 10 (Thread 0x7ff16e977700 (LWP 18286)):
#0  0x7ff1f4ff80af in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7ff181d8b533 in  () at /usr/lib64/dri/radeonsi_dri.so
#2  0x7ff181d8ad57 in  () at /usr/lib64/dri/radeonsi_dri.so
#3  0x7ff1f4ff3734 in start_thread () at /lib64/libpthread.so.0
#4  0x7ff1f8033d3d in clone () at /lib64/libc.so.6

Thread 9 (Thread 0x7ff182ffd700 (LWP 18285)):
#0  0x7ff1f4ff80af in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7ff1feeff6e3 in  () at /usr/lib64/libQt5WebKit.so.5
#2  0x7ff1ff221341 in  () at /usr/lib64/libQt5WebKit.so.5
#3  0x7ff1f4ff3734 in start_thread () at /lib64/libpthread.so.0
#4  0x7ff1f8033d3d in clone () at /lib64/libc.so.6

Thread 8 (Thread 0x7ff1837fe700 (LWP 18284)):
#0  0x7ff1f4ff80af in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7ff1feeff6e3 in  () at /usr/lib64/libQt5WebKit.so.5
#2  0x7ff1ff221341 in  () at /usr/lib64/libQt5WebKit.so.5
#3  0x7ff1f4ff3734 in start_thread () at /lib64/libpthread.so.0
#4  0x7ff1f8033d3d in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7ff183fff700 (LWP 18283)):
#0  0x7ff1f4ff80af in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7ff1feeff6e3 in  () at /usr/lib64/libQt5WebKit.so.5
#2  0x7ff1ff221341 in  () at /usr/lib64/libQt5WebKit.so.5
#3  0x7ff1f4ff3734 in start_thread () at /lib64/libpthread.so.0
#4  0x7ff1f8033d3d in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7ff1889ad700 (LWP 18282)):
#0  0x7ff1f4ff80af in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7ff1feefe70d in  () at /usr/lib64/libQt5WebKit.so.5
#2  0x7ff1ff221341 in  () at /usr/lib64/libQt5WebKit.so.5
#3  0x7ff1f4ff3734 in start_thread () at /lib64/libpthread.so.0
#4  0x7ff1f8033d3d in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7ff1c96c3700 (LWP 18281)):
#0  0x7ff1f4ff80af in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7ff1ff1f2873 in  () at /usr/lib64/libQt5WebKit.so.5
#2  0x7ff1ff1f2899 in  () at /usr/lib64/libQt5WebKit.so.5
#3  0x7ff1f4ff3734 in start_thread () at /lib64/libpthread.so.0
#4  0x7ff1f8033d3d in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7ff1deb9d700 (LWP 18280)):
#0  0x7ff1f47be7d4 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0
#1  

[konsole] [Bug 373440] konsole --new-tab opens window instead

2016-12-17 Thread Peter Wu
https://bugs.kde.org/show_bug.cgi?id=373440

Peter Wu <pe...@lekensteyn.nl> changed:

   What|Removed |Added

 CC||pe...@lekensteyn.nl
 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #2 from Peter Wu <pe...@lekensteyn.nl> ---
Confirmed with konsole 16.12.0 on Arch Linux.

Possibly related issue: previously a tab could be dragged between windows. Now
it will only allow rearrangement within one window, or creation of a new
window.

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

[konsole] [Bug 373716] Closebutton should be on each tab - not on the right side of the window

2016-12-17 Thread Peter Wu
https://bugs.kde.org/show_bug.cgi?id=373716

Peter Wu <pe...@lekensteyn.nl> changed:

   What|Removed |Added

 CC||pe...@lekensteyn.nl
   Severity|normal  |wishlist

--- Comment #1 from Peter Wu <pe...@lekensteyn.nl> ---
Konsole does not have a close button for a tab, you can right-click it and
chose "Close Tab".

(For consistency with other apps like Kate, I guess that it is better to show
the close button on the right though.)

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

[trojita] [Bug 374819] When dragging a collapsed thread, all messages in the thread should be moved

2017-01-13 Thread Peter Mattern
https://bugs.kde.org/show_bug.cgi?id=374819

Peter Mattern <pmatt...@arcor.de> changed:

   What|Removed |Added

 CC||pmatt...@arcor.de

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

[kwin] [Bug 375023] New: Kwin chrashed when Auth-Window opens

2017-01-13 Thread Peter Wendel
https://bugs.kde.org/show_bug.cgi?id=375023

Bug ID: 375023
   Summary: Kwin chrashed when Auth-Window opens
   Product: kwin
   Version: 5.8.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: p...@thefan1968.de
  Target Milestone: ---

Application: kwin_x11 (5.8.3)

Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.4.36-8-default x86_64
Distribution: "openSUSE Leap 42.2"

-- Information about the crash:
- What I was doing when the application crashed:
I opened SuseImageWriter, selected an image to write and clicked "write"

When the window for root-legitimation opens, kwin chrashes

The crash can be reproduced every time.

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

Thread 6 (Thread 0x7f976631e700 (LWP 3508)):
#0  0x7f97884c9b03 in select () at /lib64/libc.so.6
#1  0x7f9785b85849 in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timespec const*) () at /usr/lib64/libQt5Core.so.5
#2  0x7f9785b870c3 in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () at /usr/lib64/libQt5Core.so.5
#3  0x7f9785b87527 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f9785b36fdb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f9785971f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f978050b9b8 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7f97859769e9 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f9788797734 in start_thread () at /lib64/libpthread.so.0
#9  0x7f97884d0d3d in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7f9757fff700 (LWP 2790)):
#0  0x7f978879c0af in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f9784afa93b in  () at /usr/lib64/libQt5Script.so.5
#2  0x7f9784afa969 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7f9788797734 in start_thread () at /lib64/libpthread.so.0
#4  0x7f97884d0d3d in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f97654be700 (LWP 2769)):
#0  0x7f9785b871f9 in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () at /usr/lib64/libQt5Core.so.5
#1  0x7f9785b87527 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#2  0x7f9785b36fdb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#3  0x7f9785971f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#4  0x7f978050b9b8 in  () at /usr/lib64/libQt5Qml.so.5
#5  0x7f97859769e9 in  () at /usr/lib64/libQt5Core.so.5
#6  0x7f9788797734 in start_thread () at /lib64/libpthread.so.0
#7  0x7f97884d0d3d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f9767966700 (LWP 2735)):
#0  0x7f97884c9b03 in select () at /lib64/libc.so.6
#1  0x7f9785b85849 in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timespec const*) () at /usr/lib64/libQt5Core.so.5
#2  0x7f9785b870c3 in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () at /usr/lib64/libQt5Core.so.5
#3  0x7f9785b87527 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f9785b36fdb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f9785971f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f977f6de1d5 in  () at /usr/lib64/libQt5DBus.so.5
#7  0x7f97859769e9 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f9788797734 in start_thread () at /lib64/libpthread.so.0
#9  0x7f97884d0d3d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f976dbee700 (LWP 2727)):
#0  0x7f97884c849d in poll () at /lib64/libc.so.6
#1  0x7f978764a3e2 in  () at /usr/lib64/libxcb.so.1
#2  0x7f978764bfcf in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7f976ece8839 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f97859769e9 in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f9788797734 in start_thread () at /lib64/libpthread.so.0
#6  0x7f97884d0d3d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f9788d69940 (LWP 2676)):
[KCrash Handler]
#6  0x7f97804f7dd0 in QQmlBinding::write(QQmlPropertyData const&,
QV4::Value const&, bool, QFlags) () at
/usr/lib64/libQt5Qml.so.5
#7  0x7f97804f924a in
QQmlBinding::update(QFlags) () at
/usr/lib64/libQt5Qml.so.5
#8  0x7f97805022f6 in  () at /usr/lib64/libQt5Qml.so.5
#9  0x7f978049093b in QQmlComponentPrivate::complete(QQmlEnginePrivate*,
QQmlComponentPrivate::ConstructionState*) () at /usr/lib64/libQt5Qml.so.5
#10 0x7f97804909f7 in QQmlComponentPrivate::completeCreate() () at
/usr/lib64/libQt5Qml.so.5
#11 0x7f9780490880 in QQmlComponent::create(QQmlContext*) () at
/usr/lib64/libQt5Qml.so.5
#12 

[kwin] [Bug 375038] New: kwin crashes when imagewriter needs legitimation

2017-01-14 Thread Peter Wendel
https://bugs.kde.org/show_bug.cgi?id=375038

Bug ID: 375038
   Summary: kwin crashes when imagewriter needs legitimation
   Product: kwin
   Version: 5.8.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: p...@thefan1968.de
  Target Milestone: ---

Application: kwin_x11 (5.8.3)

Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.4.36-8-default x86_64
Distribution: "openSUSE Leap 42.2"

-- Information about the crash:
- What I was doing when the application crashed:
I selected an image and clicked to write it to sd-card.
Imagewriter needs root legitimation and kwin chrashes.

The crash can be reproduced every time.

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

Thread 6 (Thread 0x7f926113f700 (LWP 14563)):
#0  0x7f9285fceb03 in select () at /lib64/libc.so.6
#1  0x7f928368a849 in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timespec const*) () at /usr/lib64/libQt5Core.so.5
#2  0x7f928368c0c3 in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () at /usr/lib64/libQt5Core.so.5
#3  0x7f928368c527 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f928363bfdb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f9283476f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f927e0109b8 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7f928347b9e9 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f928629c734 in start_thread () at /lib64/libpthread.so.0
#9  0x7f9285fd5d3d in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7f9261eda700 (LWP 4334)):
#0  0x7f92862a10af in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f92825ff93b in  () at /usr/lib64/libQt5Script.so.5
#2  0x7f92825ff969 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7f928629c734 in start_thread () at /lib64/libpthread.so.0
#4  0x7f9285fd5d3d in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f9262fc3700 (LWP 4326)):
#0  0x7f9285fceb03 in select () at /lib64/libc.so.6
#1  0x7f928368a849 in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timespec const*) () at /usr/lib64/libQt5Core.so.5
#2  0x7f928368c0c3 in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () at /usr/lib64/libQt5Core.so.5
#3  0x7f928368c527 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f928363bfdb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f9283476f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f927e0109b8 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7f928347b9e9 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f928629c734 in start_thread () at /lib64/libpthread.so.0
#9  0x7f9285fd5d3d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f9269543700 (LWP 4295)):
#0  0x7f9285fceb03 in select () at /lib64/libc.so.6
#1  0x7f928368a849 in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timespec const*) () at /usr/lib64/libQt5Core.so.5
#2  0x7f928368c0c3 in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () at /usr/lib64/libQt5Core.so.5
#3  0x7f928368c527 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f928363bfdb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f9283476f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f927d1e31d5 in  () at /usr/lib64/libQt5DBus.so.5
#7  0x7f928347b9e9 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f928629c734 in start_thread () at /lib64/libpthread.so.0
#9  0x7f9285fd5d3d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f926b6f3700 (LWP 4290)):
#0  0x7f9285fcd49d in poll () at /lib64/libc.so.6
#1  0x7f928514f3e2 in  () at /usr/lib64/libxcb.so.1
#2  0x7f9285150fcf in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7f926c7ed839 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f928347b9e9 in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f928629c734 in start_thread () at /lib64/libpthread.so.0
#6  0x7f9285fd5d3d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f928686f940 (LWP 4275)):
[KCrash Handler]
#6  0x7f927dffcdd0 in QQmlBinding::write(QQmlPropertyData const&,
QV4::Value const&, bool, QFlags) () at
/usr/lib64/libQt5Qml.so.5
#7  0x7f927dffe24a in
QQmlBinding::update(QFlags) () at
/usr/lib64/libQt5Qml.so.5
#8  0x7f927e0072f6 in  () at /usr/lib64/libQt5Qml.so.5
#9  0x7f927df9593b in QQmlComponentPrivate::complete(QQmlEnginePrivate*,
QQmlComponentPrivate::ConstructionState*) () at /usr/lib64/libQt5Qml.so.5
#10 0x7f927df959f7 in 

[kdialog] [Bug 369216] kdialog path parsing regression

2017-01-12 Thread Peter Petrov
https://bugs.kde.org/show_bug.cgi?id=369216

--- Comment #8 from Peter Petrov <onest...@gmail.com> ---
In which user-facing release is this fix expected to be included? Apparently
it's not part of the just released 16.12.1.

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

[kdialog] [Bug 369216] kdialog path parsing regression

2017-01-12 Thread Peter Petrov
https://bugs.kde.org/show_bug.cgi?id=369216

--- Comment #10 from Peter Petrov <onest...@gmail.com> ---
Right, sorry for the noise. Didn't notice the fix was in kio (frameworks)
instead of kdialog (applications).

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

[plasmashell] [Bug 373209] New: Plasma sometimes crashes after suspend/hibernate

2016-12-03 Thread Peter Kreussel
https://bugs.kde.org/show_bug.cgi?id=373209

Bug ID: 373209
   Summary: Plasma sometimes crashes after suspend/hibernate
   Product: plasmashell
   Version: 5.8.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: pri...@peter-kreussel.de
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.4)

Qt Version: 5.7.0
Frameworks Version: 5.28.0
Operating System: Linux 4.8.11-1-ARCH x86_64
Distribution: "Arch Linux"

-- Information about the crash:
What I was doing when the application crashed:
- returning from hibernate (that's what the backtrace belongs to)
- or from suspend
Plasma crashes and restarts. Not every time, about every 6th or 7th resume from
powersave mode or so.

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 0x7fe5d22a4800 (LWP 1374))]

Thread 24 (Thread 0x7fe4bbb6f700 (LWP 3708)):
#0  0x7fe5cb1e810f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fe5cc0d3c2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fe5d003c395 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7fe5d003cc8a in  () at /usr/lib/libQt5Quick.so.5
#4  0x7fe5cc0d2d78 in  () at /usr/lib/libQt5Core.so.5
#5  0x7fe5cb1e2454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fe5cb9e87df in clone () at /usr/lib/libc.so.6

Thread 23 (Thread 0x7fe4b788d700 (LWP 3704)):
#0  0x7fe5cb1e810f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fe5cc0d3c2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fe5d003c395 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7fe5d003cc8a in  () at /usr/lib/libQt5Quick.so.5
#4  0x7fe5cc0d2d78 in  () at /usr/lib/libQt5Core.so.5
#5  0x7fe5cb1e2454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fe5cb9e87df in clone () at /usr/lib/libc.so.6

Thread 22 (Thread 0x7fe4b829b700 (LWP 3329)):
#0  0x7fe5cb1e810f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fe5cc0d3c2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fe5d003c395 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7fe5d003cc8a in  () at /usr/lib/libQt5Quick.so.5
#4  0x7fe5cc0d2d78 in  () at /usr/lib/libQt5Core.so.5
#5  0x7fe5cb1e2454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fe5cb9e87df in clone () at /usr/lib/libc.so.6

Thread 21 (Thread 0x7fe4b9d0d700 (LWP 3273)):
#0  0x7fe5cb1e810f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fe5cc0d3c2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fe5d003c395 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7fe5d003cc8a in  () at /usr/lib/libQt5Quick.so.5
#4  0x7fe5cc0d2d78 in  () at /usr/lib/libQt5Core.so.5
#5  0x7fe5cb1e2454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fe5cb9e87df in clone () at /usr/lib/libc.so.6

Thread 20 (Thread 0x7fe4b8d0b700 (LWP 3249)):
#0  0x7fe5cb1e810f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fe5cc0d3c2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fe5d003c395 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7fe5d003cc8a in  () at /usr/lib/libQt5Quick.so.5
#4  0x7fe5cc0d2d78 in  () at /usr/lib/libQt5Core.so.5
#5  0x7fe5cb1e2454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fe5cb9e87df in clone () at /usr/lib/libc.so.6

Thread 19 (Thread 0x7fe4b4a3d700 (LWP 3170)):
#0  0x7fe5cb1e810f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fe5cc0d3c2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fe5d003c395 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7fe5d003cc8a in  () at /usr/lib/libQt5Quick.so.5
#4  0x7fe5cc0d2d78 in  () at /usr/lib/libQt5Core.so.5
#5  0x7fe5cb1e2454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fe5cb9e87df in clone () at /usr/lib/libc.so.6

Thread 18 (Thread 0x7fe4ab7fd700 (LWP 2826)):
#0  0x7fe5cb1e810f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fe5cc0d3c2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fe5d003c395 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7fe5d003cc8a in  () at /usr/lib/libQt5Quick.so.5
#4  0x7fe5cc0d2d78 in  () at /usr/lib/libQt5Core.so.5
#5  0x7fe5cb1e2454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fe5cb9e87df

[digikam] [Bug 367970] Allow copyof EXIF, IPTC and XMP from one to another image

2016-12-01 Thread Hans-Peter
https://bugs.kde.org/show_bug.cgi?id=367970

--- Comment #3 from Hans-Peter <hans...@web.de> ---
(In reply to b3nmore from comment #2)
> (In reply to caulier.gilles from comment #1)
> > 
> > *** This bug has been marked as a duplicate of bug 155384 ***
> 
> Not sure why this is a duplicate. Bug 155384 seems to be a request for
> general enhancement, which may or may not be implemented at some point. This
> bug is more like a regression, because exif, iptc and xmp import was already
> possible with digikam <5 and no replacement exist like in the bqm (or I have
> not found it ;)).

Thats correct, its a feature which has been lost during 5.x development, not an
old bug.

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

[plasma-nm] [Bug 374262] wireless connection drops frequently

2017-01-02 Thread Peter Roots
https://bugs.kde.org/show_bug.cgi?id=374262

--- Comment #4 from Peter Roots <peterro...@gmail.com> ---
(In reply to Jan Grulich from comment #3)
> Unfortunately this is definitely a problem somewhere in the underlying
> software (either driver issue or a bug in NetworkManager). I would start
> with opening a bug report for NetworkManager where they can help you more
> than me.
> 
> NM bugzilla:
> https://bugzilla.gnome.org/page.cgi?id=browse.html=NetworkManager

Thank you, I will do that

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

[krunner] [Bug 374541] New: Krunner segfaulting after selecting result + pressing Enter

2017-01-04 Thread Peter Kreussel
https://bugs.kde.org/show_bug.cgi?id=374541

Bug ID: 374541
   Summary: Krunner segfaulting after selecting result + pressing
Enter
   Product: krunner
   Version: 5.8.5
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@privat.broulik.de
  Reporter: pri...@peter-kreussel.de
  Target Milestone: ---

Application: krunner (5.8.5)

Qt Version: 5.7.1
Frameworks Version: 5.29.0
Operating System: Linux 4.8.13-1-ARCH x86_64
Distribution: "Arch Linux"

-- Information about the crash:
- What I was doing when the application crashed:
--opening Krunner with Alt+Space
--typing "kwr"
--selecting result "KWrite", pressing Enter

I am using Nvidia 375.26. 
This has been happening for quite a while (= different versions of
plasma-framwork on Arch Linux). Not very often, but Krunner does not restart,
which makes this a bit of a bother.

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

Thread 21 (Thread 0x7f328d7fa700 (LWP 20189)):
#0  0x7f32f38a510f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f32f63edbab in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f32d44381c0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7f32d443c988 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7f32d4437263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7f32d443c9e2 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#6  0x7f32d4437263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#7  0x7f32d443a1f9 in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#8  0x7f32f63eccf8 in  () at /usr/lib/libQt5Core.so.5
#9  0x7f32f389f454 in start_thread () at /usr/lib/libpthread.so.0
#10 0x7f32f5d027df in clone () at /usr/lib/libc.so.6

Thread 20 (Thread 0x7f328dffb700 (LWP 20188)):
#0  0x7f32f38a510f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f32f63edbab in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f32d44381c0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7f32d443c988 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7f32d4437263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7f32d443a1f9 in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#6  0x7f32f63eccf8 in  () at /usr/lib/libQt5Core.so.5
#7  0x7f32f389f454 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f32f5d027df in clone () at /usr/lib/libc.so.6

Thread 19 (Thread 0x7f328e7fc700 (LWP 20187)):
#0  0x7f32f38a510f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f32f63edbab in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f32d44381c0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7f32d443c988 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7f32d4437263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7f32d443c9e2 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#6  0x7f32d4437263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#7  0x7f32d443a1f9 in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#8  0x7f32f63eccf8 in  () at /usr/lib/libQt5Core.so.5
#9  0x7f32f389f454 in start_thread () at /usr/lib/libpthread.so.0
#10 0x7f32f5d027df in clone () at /usr/lib/libc.so.6

Thread 18 (Thread 0x7f328effd700 (LWP 20186)):
#0  0x7f32f38a510f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f32f63edbab in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f32d44381c0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7f32d443c988 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7f32d4437263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7f32d443a1f9 in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5

[kmail2] [Bug 321024] KMail does not show event invitations sent by Outlook

2017-01-09 Thread Peter Hatina
https://bugs.kde.org/show_bug.cgi?id=321024

Peter Hatina <phat...@gmail.com> changed:

   What|Removed |Added

 CC||phat...@gmail.com

--- Comment #12 from Peter Hatina <phat...@gmail.com> ---
(In reply to Denis Kurz from comment #11)
> Just as announced in my last comment, I close this bug. If you encounter it
> again in a recent version (at least 5.0 aka 15.08), please open a new one
> unless it already exists. Thank you for all your input.

I can't see Outlook invitations in KMail 5.2.3, using 
KDE Frameworks 5.28.0 and Qt 5.6.1

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

[amarok] [Bug 374283] New: Icons Missing

2016-12-29 Thread Peter Mulller
https://bugs.kde.org/show_bug.cgi?id=374283

Bug ID: 374283
   Summary: Icons Missing
   Product: amarok
   Version: 2.8.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: amarok-bugs-d...@kde.org
  Reporter: peter_mull...@yahoo.de
  Target Milestone: 2.9

Amarok 2.8.0-39.1 built Mo 26 Dez 2016 22:49:06 CET

The follwoing icons are missing: 
Previous Track, Play/Pause, Stop, Next Track 
in the file browser: back, forward, go up, home, refresh
in the help menue: Amarok Handbook, Report bug, Switch application Language

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

[amarok] [Bug 374284] New: Icons Missing

2016-12-29 Thread Peter Mulller
https://bugs.kde.org/show_bug.cgi?id=374284

Bug ID: 374284
   Summary: Icons Missing
   Product: amarok
   Version: 2.8.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: amarok-bugs-d...@kde.org
  Reporter: peter_mull...@yahoo.de
  Target Milestone: 2.9

Amarok 2.8.0-39.1 built Mo 26 Dez 2016 22:49:06 CET

The follwoing icons are missing: 
Previous Track, Play/Pause, Stop, Next Track 
in the file browser: back, forward, go up, home, refresh
in the help menue: Amarok Handbook, Report bug, Switch application Language

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

[amarok] [Bug 374283] Icons Missing

2016-12-29 Thread Peter Mulller
https://bugs.kde.org/show_bug.cgi?id=374283

Peter Mulller <peter_mull...@yahoo.de> changed:

   What|Removed |Added

 CC||peter_mull...@yahoo.de

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

[konversation] [Bug 374252] Aplying IRC-Color whithout changing the color settings results in a string "%C01" in the chat input field

2017-01-01 Thread Peter Simonsson
https://bugs.kde.org/show_bug.cgi?id=374252

Peter Simonsson <peter.simons...@gmail.com> changed:

   What|Removed |Added

 CC||peter.simons...@gmail.com

--- Comment #1 from Peter Simonsson <peter.simons...@gmail.com> ---
Yes... don't see the problem with that as that is what is set in the dialog by
default. What did you expect to happen?

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

[konversation] [Bug 374264] Konversation 1.6.2 reports Version 1.6-branch #4910 in Help About Konversation Version

2017-01-01 Thread Peter Simonsson
https://bugs.kde.org/show_bug.cgi?id=374264

Peter Simonsson <peter.simons...@gmail.com> changed:

   What|Removed |Added

 CC||peter.simons...@gmail.com

--- Comment #3 from Peter Simonsson <peter.simons...@gmail.com> ---
Hmm are you sure those packages are built from the 1.6.2 release source
packages and not just from the 1.6 branch? It's only the release source
packages that will report 1.6.2 as the version.

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

[kdialog] [Bug 369216] kdialog path parsing regression

2016-12-20 Thread Peter Petrov
https://bugs.kde.org/show_bug.cgi?id=369216

Peter Petrov <onest...@gmail.com> changed:

   What|Removed |Added

 CC||onest...@gmail.com

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

[konsole] [Bug 373991] New: Konsonle does not honour "Use current Window size on next Startup"

2016-12-21 Thread Peter Tselios
https://bugs.kde.org/show_bug.cgi?id=373991

Bug ID: 373991
   Summary: Konsonle does not honour "Use current Window size on
next Startup"
   Product: konsole
   Version: 16.08.2
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: s91...@yahoo.gr
  Target Milestone: ---

I have enabled the under subject option in my Konsole. However, when I start
konsole again, the previous size is not honoured. It looks like it's not saved. 

If I deselect it and set a fixed size for the profiles, those settings are
honoured though.

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

[plasma-nm] [Bug 374262] New: wireless connection drops frequently

2016-12-28 Thread Peter Roots
https://bugs.kde.org/show_bug.cgi?id=374262

Bug ID: 374262
   Summary: wireless connection drops frequently
   Product: plasma-nm
   Version: 5.5.5
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: editor
  Assignee: lu...@kde.org
  Reporter: peterro...@gmail.com
CC: jgrul...@redhat.com
  Target Milestone: ---

not really sure if plasma applet or underlying network manager or something
else but on wireless I frequently loose connection. Other devices on the
network don't drop connection and neither does this laptop when running Windows
10
Using realtek RTL8821AE on 5GHz but also have had this when using 2.4GHz

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

[plasma-nm] [Bug 374262] wireless connection drops frequently

2016-12-28 Thread Peter Roots
https://bugs.kde.org/show_bug.cgi?id=374262

--- Comment #1 from Peter Roots <peterro...@gmail.com> ---
sometimes drops within a few minutes of logging on, other times may run for an
hour or so. Sometimes will eventually reconnect but mostly have to disconnect
and reconnect to AP. Sometimes forced to turn off wireless and back on again
before it works. occasionally the only way to get network is to reboot.
sometimes after reconnecting the connection remains for sometime, other times
it drops almost immediately again
I have tried with both 2.4GHz and 5GHz connections remembered and when one
drops the other tries to start but found suggestion that this can cause a
problem when wireless flaps between the two so have tried with just one or the
other set up. Problem exists on both.
have tried this
sudo add-apt-repository ppa:hanipouspilot/rtlwifi
sudo apt update
sudo apt install rtlwifi-new-dkms
but ended up with no wireless connectivity at all
I am using Kubuntu 16.4 and have had the issue for months. Keep hoping an
update will fix but nothing as yet. kernel is 4.4.0-57-generic

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

[plasma-nm] [Bug 374262] wireless connection drops frequently

2016-12-28 Thread Peter Roots
https://bugs.kde.org/show_bug.cgi?id=374262

Peter Roots <peterro...@gmail.com> changed:

   What|Removed |Added

   Platform|Other   |Ubuntu Packages

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

[plasma-nm] [Bug 374262] wireless connection drops frequently

2016-12-28 Thread Peter Roots
https://bugs.kde.org/show_bug.cgi?id=374262

--- Comment #2 from Peter Roots <peterro...@gmail.com> ---
oh and not confined to my home wifi either, reproducible on others too

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

[plasmashell] [Bug 374138] New: Start shell script with desktop icon

2016-12-25 Thread Peter Stolz
https://bugs.kde.org/show_bug.cgi?id=374138

Bug ID: 374138
   Summary: Start shell script with desktop icon
   Product: plasmashell
   Version: 5.8.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Desktop Containment
  Assignee: se...@kde.org
  Reporter: p.stol...@gmail.com
  Target Milestone: 1.0

Created attachment 102986
  --> https://bugs.kde.org/attachment.cgi?id=102986=edit
Screeshot with desktop icon configuration

It is not possible to start a shell script with a desktop icon:
No terminal is starting and no user interacts (password input) are possible.

In earlier KDE Version like 5.4 this works (see attachment)

Peter

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

[plasmashell] [Bug 374138] Start shell script with desktop icon

2016-12-25 Thread Peter Stolz
https://bugs.kde.org/show_bug.cgi?id=374138

--- Comment #1 from Peter Stolz <p.stol...@gmail.com> ---
It seems to be caused by Bug 366793 Regression in Konsole's handling of command
line parameters

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

[kdialog] [Bug 373721] Chrome's kdialog always opens the default path

2016-12-19 Thread Peter Petrov
https://bugs.kde.org/show_bug.cgi?id=373721

Peter Petrov <onest...@gmail.com> changed:

   What|Removed |Added

 CC||onest...@gmail.com

--- Comment #1 from Peter Petrov <onest...@gmail.com> ---
Confirming, also on Arch Linux after updating to kdialog 16.12.0-1.

Not sure that "default folder" is accurate though. In my case ~/Downloads is
specified as the default save folder in Chrome, but the Save dialog always
opens in ~/Documents.

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

[valgrind] [Bug 377966] disInstr(arm64): unhandled instruction 0xD50B7425 (dc zva,)

2017-03-23 Thread Peter Maydell
https://bugs.kde.org/show_bug.cgi?id=377966

Peter Maydell <peter.mayd...@linaro.org> changed:

   What|Removed |Added

 CC||peter.mayd...@linaro.org

--- Comment #2 from Peter Maydell <peter.mayd...@linaro.org> ---
You can read the DCZID_EL0 register, which will tell you both (a) whether it's
permitted to use DC ZVA and (b) the size of the cache line affected. A
big.Little system will always report the same cache line size for this purpose
regardless of core -- it would be impossible to use DC ZVA reliably otherwise.
(There is at least one SoC with a system integration bug where it reports
different values on different cores, but the fix for this is at the Linux
kernel level where the kernel can check for such errata and set the register up
to trap so the kernel can fix up the reported values.)

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

[konsole] [Bug 372991] Terminal gets stuck on interrupting a program that is outputting, preventing further output from being shown

2017-03-26 Thread Peter Wu
https://bugs.kde.org/show_bug.cgi?id=372991

--- Comment #17 from Peter Wu <pe...@lekensteyn.nl> ---
Created attachment 104751
  --> https://bugs.kde.org/attachment.cgi?id=104751=edit
smaller kernel config that is able to boot archiso

(In reply to Martin Sandsmark from comment #15)
> Well, it wasn't that commit, managed to reproduce it with that reverted.

What about testing the previous commit? Simply reverting might not work as
there can be other patches that cause this issue.

> Running an arch install pretty similar to your setup but with virtualbox.
> Also made an unholy mess of shell scripts that seems to trigger it more
> consistently, only problem is that it takes forever to build the kernel (I'm
> too lazy to modify the config to trim it down).

I am attaching a kernel config from which I based my test kernels (the kernel
config I used for bisection got lost). It also has ACPI debugging features
enabled (remainder of some other bughunt), you could disable that if you want.
What do you use for "quickly" triggering the issue? Something automated would
be awesome :)

(In reply to Martin Sandsmark from comment #16)
> also, I'm not sure if I'm somehow triggering this bug instead sometimes (or
> if these are related): https://bugs.kde.org/show_bug.cgi?id=230184

It looks unrelated, that seems to be an issue with firing the timer, the issue
in this bug is caused by a watcher that is removed.

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

[konsole] [Bug 372991] Terminal gets stuck on interrupting a program that is outputting, preventing further output from being shown

2017-03-26 Thread Peter Wu
https://bugs.kde.org/show_bug.cgi?id=372991

--- Comment #14 from Peter Wu <pe...@lekensteyn.nl> ---
(In reply to Martin Sandsmark from comment #13)
> Are you sure that 4.1 was okay?

Not sure if it was okay, but I wasn't able to reproduce the issue. The
difficult/annoying thing is that some versions easily trigger the problem while
others only show up after trying for some time.

> There is only a single commit to any relevant tty code that I can spot
> between v4.1.1 and v4.1.10-89-g5eb491ba5d06:
> https://www.spinics.net/lists/stable-commits/msg47515.html
> (3b19e032295647b7be2aa3be62510db4aaeda759).

which first ended up in v4.1.5 as ba3961ad681981dc74fcd519b8f98be8bc3ac381

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

[konversation] [Bug 374690] Already running Konversation app invoked as handler for irc:// links does not enter channel from link

2017-03-30 Thread Peter Simonsson
https://bugs.kde.org/show_bug.cgi?id=374690

Peter Simonsson <peter.simons...@gmail.com> changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 CC||peter.simons...@gmail.com
 Ever confirmed|0   |1

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

[konversation] [Bug 371534] mouse wheel and cursor acts differently in scrollong thru the channel list

2017-03-30 Thread Peter Simonsson
https://bugs.kde.org/show_bug.cgi?id=371534

Peter Simonsson <peter.simons...@gmail.com> changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED
 CC||peter.simons...@gmail.com

--- Comment #1 from Peter Simonsson <peter.simons...@gmail.com> ---
In 1.7 both keys and mouse wheel circles around.

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

[konversation] [Bug 374690] Already running Konversation app invoked as handler for irc:// links does not enter channel from link

2017-03-30 Thread Peter Simonsson
https://bugs.kde.org/show_bug.cgi?id=374690

Peter Simonsson <peter.simons...@gmail.com> changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED
  Latest Commit||https://commits.kde.org/kon
   ||versation/2605c61fcaec65f22
   ||23a8ad91c39005f09047642

--- Comment #1 from Peter Simonsson <peter.simons...@gmail.com> ---
Git commit 2605c61fcaec65f2223a8ad91c39005f09047642 by Peter Simonsson.
Committed on 30/03/2017 at 15:46.
Pushed by psn into branch '1.7'.

Use correct argument for the url

M  +2-2src/application.cpp

https://commits.kde.org/konversation/2605c61fcaec65f2223a8ad91c39005f09047642

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

[valgrind] [Bug 377966] disInstr(arm64): unhandled instruction 0xD50B7425 (dc zva,)

2017-03-23 Thread Peter Maydell
https://bugs.kde.org/show_bug.cgi?id=377966

--- Comment #4 from Peter Maydell <peter.mayd...@linaro.org> ---
Good point -- there's no inherent reason why valgrind would need to use the
same cache line size that the host is using for DC ZVA. You can just pick an
arbitrary value as long as you're consistent with the value of DCZID_EL0 you
report to the guest.

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

[konversation] [Bug 373243] Ignore feature seems to do nothing at all

2017-03-29 Thread Peter Simonsson
https://bugs.kde.org/show_bug.cgi?id=373243

Peter Simonsson <peter.simons...@gmail.com> changed:

   What|Removed |Added

 CC||peter.simons...@gmail.com
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WONTFIX

--- Comment #1 from Peter Simonsson <peter.simons...@gmail.com> ---
The ignore feature only works on the hostmask at the moment. Please open a
feature request and describe what you need and we'll see what we can do.

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

[kwin] [Bug 377804] New: Kwin chrashes on opening Authentication-Window in imagewriter

2017-03-19 Thread Peter Wendel
https://bugs.kde.org/show_bug.cgi?id=377804

Bug ID: 377804
   Summary: Kwin chrashes on opening Authentication-Window in
imagewriter
   Product: kwin
   Version: 5.8.6
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: p...@thefan1968.de
  Target Milestone: ---

Application: kwin_x11 (5.8.6)

Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.4.49-16-default x86_64
Distribution: "openSUSE Leap 42.2"

-- Information about the crash:
- What I was doing when the application crashed:
Copied an OS-image to SD-card. Root-Pasword was required.
The window opened and kwin chrashes on the main monitor, where the program is
displayed. Got a black square in up left corner, where normally a KDE-menu is
displayed.
This black square now shows details from main taskbar. It shows informations
from the rightmost program in the taskbar which is at the moment clipboard.

The crash can be reproduced every time.

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

Thread 6 (Thread 0x7fa5ef5ec700 (LWP 6960)):
#0  0x7ffc07d68ada in clock_gettime ()
#1  0x7fa611b93806 in clock_gettime () at /lib64/libc.so.6
#2  0x7fa60f0cf826 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7fa60f235989 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7fa60f235f05 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fa60f23558a in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#6  0x7fa60f1e4fdb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#7  0x7fa60f01ff1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8  0x7fa609bb99c8 in  () at /usr/lib64/libQt5Qml.so.5
#9  0x7fa60f0249e9 in  () at /usr/lib64/libQt5Core.so.5
#10 0x7fa611e4d734 in start_thread () at /lib64/libpthread.so.0
#11 0x7fa611b86d3d in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7fa5edb4b700 (LWP 4716)):
#0  0x7fa611e520af in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fa60e1a893b in  () at /usr/lib64/libQt5Script.so.5
#2  0x7fa60e1a8969 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7fa611e4d734 in start_thread () at /lib64/libpthread.so.0
#4  0x7fa611b86d3d in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7fa5eeb4c700 (LWP 4713)):
#0  0x7fa611b7fb03 in select () at /lib64/libc.so.6
#1  0x7fa60f233849 in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timespec const*) () at /usr/lib64/libQt5Core.so.5
#2  0x7fa60f2350c3 in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () at /usr/lib64/libQt5Core.so.5
#3  0x7fa60f235527 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fa60f1e4fdb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fa60f01ff1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fa609bb99c8 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7fa60f0249e9 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7fa611e4d734 in start_thread () at /lib64/libpthread.so.0
#9  0x7fa611b86d3d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7fa5f50dc700 (LWP 4682)):
#0  0x7fa611b7fb03 in select () at /lib64/libc.so.6
#1  0x7fa60f233849 in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timespec const*) () at /usr/lib64/libQt5Core.so.5
#2  0x7fa60f2350c3 in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () at /usr/lib64/libQt5Core.so.5
#3  0x7fa60f235527 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fa60f1e4fdb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fa60f01ff1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fa608d8c1d5 in  () at /usr/lib64/libQt5DBus.so.5
#7  0x7fa60f0249e9 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7fa611e4d734 in start_thread () at /lib64/libpthread.so.0
#9  0x7fa611b86d3d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7fa5f728c700 (LWP 4666)):
#0  0x7fa611b7e49d in poll () at /lib64/libc.so.6
#1  0x7fa610cf83e2 in  () at /usr/lib64/libxcb.so.1
#2  0x7fa610cf9fcf in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7fa5f8386839 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7fa60f0249e9 in  () at /usr/lib64/libQt5Core.so.5
#5  0x7fa611e4d734 in start_thread () at /lib64/libpthread.so.0
#6  0x7fa611b86d3d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7fa61241e940 (LWP 4623)):
[KCrash Handler]
#6  0x7fa609ba5de0 in QQmlBinding::write(QQmlPropertyData const&,
QV4::Value const&, bool, QFlags) 

[konversation] [Bug 375086] Bundled /media script only shows DBus message about the script not being translated

2017-04-02 Thread Peter Simonsson
https://bugs.kde.org/show_bug.cgi?id=375086

Peter Simonsson <peter.simons...@gmail.com> changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/kon
   ||versation/46ef74b8485311af4
   ||6969f4dd789d0e60b45a7d8

--- Comment #2 from Peter Simonsson <peter.simons...@gmail.com> ---
Git commit 46ef74b8485311af46969f4dd789d0e60b45a7d8 by Peter Simonsson.
Committed on 02/04/2017 at 08:47.
Pushed by psn into branch '1.7'.

Use qtpaths to find locale paths instead of kde4-config

M  +2-2data/scripting_support/python/konversation/i18n.py

https://commits.kde.org/konversation/46ef74b8485311af46969f4dd789d0e60b45a7d8

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

[plasmashell] [Bug 378609] New: Plasma shell crash

2017-04-10 Thread Peter Sutta
https://bugs.kde.org/show_bug.cgi?id=378609

Bug ID: 378609
   Summary: Plasma shell crash
   Product: plasmashell
   Version: 5.5.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: peter.sutta...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.5.5)

Qt Version: 5.5.1
Operating System: Linux 4.6.0-040600rc7-generic x86_64
Distribution: Ubuntu 16.04.2 LTS

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

I connect VPN via KDE network manager. Plasma shell crashes immediately.

The crash can be reproduced every time.

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

Thread 8 (Thread 0x7f392b0f6700 (LWP 2168)):
#0  0x7f39e9381372 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f39e938149c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f39ecf187eb in QEventDispatcherGlib::processEvents
(this=0x7f39240008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#3  0x7f39ecebfb4a in QEventLoop::exec (this=this@entry=0x7f392b0f5cc0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#4  0x7f39eccdc834 in QThread::exec (this=) at
thread/qthread.cpp:503
#5  0x7f392d5d47d7 in KCupsConnection::run() () from
/usr/lib/x86_64-linux-gnu/libkcupslib.so
#6  0x7f39ecce17be in QThreadPrivate::start (arg=0x333e370) at
thread/qthread_unix.cpp:331
#7  0x7f39ebdce6ba in start_thread (arg=0x7f392b0f6700) at
pthread_create.c:333
#8  0x7f39ec5f782d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 7 (Thread 0x7f393bfff700 (LWP 1905)):
#0  __GI___tls_get_addr (ti=0x7f39ed10c788) at dl-tls.c:829
#1  0x7f39ecce0702 in get_thread_data () at thread/qthread_unix.cpp:181
#2  QThreadData::current (createIfNecessary=createIfNecessary@entry=true) at
thread/qthread_unix.cpp:212
#3  0x7f39ecf17d4a in postEventSourcePrepare (s=0x7f39340012d0,
timeout=0x7f393bffead4) at kernel/qeventdispatcher_glib.cpp:247
#4  0x7f39e938091d in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f39e93812bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7f39e938149c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7f39ecf187eb in QEventDispatcherGlib::processEvents
(this=0x7f39340008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#8  0x7f39ecebfb4a in QEventLoop::exec (this=this@entry=0x7f393bffec90,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#9  0x7f39eccdc834 in QThread::exec (this=this@entry=0x10d18b0) at
thread/qthread.cpp:503
#10 0x7f39eff0aed6 in QQuickPixmapReader::run (this=0x10d18b0) at
util/qquickpixmapcache.cpp:817
#11 0x7f39ecce17be in QThreadPrivate::start (arg=0x10d18b0) at
thread/qthread_unix.cpp:331
#12 0x7f39ebdce6ba in start_thread (arg=0x7f393bfff700) at
pthread_create.c:333
#13 0x7f39ec5f782d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7f39c3bef700 (LWP 1858)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f39f1929bd4 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#2  0x7f39f1929c19 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#3  0x7f39ebdce6ba in start_thread (arg=0x7f39c3bef700) at
pthread_create.c:333
#4  0x7f39ec5f782d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7f39c954b700 (LWP 1855)):
#0  0x7f39ec5ebb5d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f39e938138c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f39e938149c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f39ecf187eb in QEventDispatcherGlib::processEvents
(this=0x7f39bc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7f39ecebfb4a in QEventLoop::exec (this=this@entry=0x7f39c954ace0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f39eccdc834 in QThread::exec (this=this@entry=0xcc31d0) at
thread/qthread.cpp:503
#6  0x7f39ef5843c5 in QQmlThreadPrivate::run (this=0xcc31d0) at
qml/ftw/qqmlthread.cpp:141
#7  0x7f39ecce17be in QThreadPrivate::start (arg=0xcc31d0) at
thread/qthread_unix.cpp:331
#8  0x7f39ebdce6ba in start_thread (arg=0x7f39c954b700) at
pthread_create.c:333
#9  0x7f39ec5f782d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7f39cb307700 (LWP 1852)):
#0  0x7f39ec5e769d in read () at 

[digikam] [Bug 378804] New: lensfun uses only one core, pls. parallize

2017-04-15 Thread Hans-Peter
https://bugs.kde.org/show_bug.cgi?id=378804

Bug ID: 378804
   Summary: lensfun uses only one core, pls. parallize
   Product: digikam
   Version: 5.5.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: ImageEditor-Tool-LensDistortion
  Assignee: digikam-de...@kde.org
  Reporter: hans...@web.de
  Target Milestone: ---

i noticed that automatic lens correction (currently DK 5.5) is very slow and
uses only one CPU core. When doing this in Gimp (lensfun-plugin), its way
faster and uses all cores.

This is in Manjaro on a Core-i5

So please enable all cores (port to QtConcurrent).

Thanks

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

[konversation] [Bug 356917] Can Konversation support server-time

2017-04-20 Thread Peter Simonsson
https://bugs.kde.org/show_bug.cgi?id=356917

Peter Simonsson <peter.simons...@gmail.com> changed:

   What|Removed |Added

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

--- Comment #3 from Peter Simonsson <peter.simons...@gmail.com> ---
And now it's fixed...
See commit 8dcacb72d56c642feff3c3007f44b6739f914811

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

[konversation] [Bug 378882] symbols in nickname not handled well "`"

2017-04-22 Thread Peter Simonsson
https://bugs.kde.org/show_bug.cgi?id=378882

Peter Simonsson <peter.simons...@gmail.com> changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/kon
   ||versation/d960726c6b7e45a9a
   ||b82743220c4d42198067b58
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Peter Simonsson <peter.simons...@gmail.com> ---
Git commit d960726c6b7e45a9ab82743220c4d42198067b58 by Peter Simonsson.
Committed on 22/04/2017 at 08:43.
Pushed by psn into branch '1.7'.

Fix handling of ` when clicking nicks

QUrl::toString doesn't decode ` correctly so add a hack to workaround

M  +2-0src/viewer/ircview.cpp

https://commits.kde.org/konversation/d960726c6b7e45a9ab82743220c4d42198067b58

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

[konversation] [Bug 379028] Settings "Highlight List" doesn't enable "Apply"

2017-04-22 Thread Peter Simonsson
https://bugs.kde.org/show_bug.cgi?id=379028

Peter Simonsson <peter.simons...@gmail.com> changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/kon
   ||versation/4721367d02c957ce8
   ||fdde0df9063d09673189fcd
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Peter Simonsson <peter.simons...@gmail.com> ---
Git commit 4721367d02c957ce8fdde0df9063d09673189fcd by Peter Simonsson.
Committed on 22/04/2017 at 07:35.
Pushed by psn into branch '1.7'.

Fix modified handling in the highlight treewidget

The highlight config didn't emit the modified signal when items
were moved or modified in the treewidget.

M  +1-0src/CMakeLists.txt
M  +2-0src/config/highlight_config.cpp
M  +11   -6src/config/highlight_configui.ui
A  +27   -0src/config/highlighttreewidget.cpp [License: GPL (v2+)]
A  +31   -0src/config/highlighttreewidget.h [License: GPL (v2+)]

https://commits.kde.org/konversation/4721367d02c957ce8fdde0df9063d09673189fcd

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

[frameworks-kwayland] [Bug 373907] Implement Wayland Primary Selection Protocol (middle-click paste)

2017-04-23 Thread Peter Schmidt
https://bugs.kde.org/show_bug.cgi?id=373907

Peter Schmidt <zicrons...@yahoo.com> changed:

   What|Removed |Added

 CC||zicrons...@yahoo.com

--- Comment #2 from Peter Schmidt <zicrons...@yahoo.com> ---
I too desire this feature.  This doesn't appear to be completely broken,
though.  I noticed any text I select (regardless of source) will
middle-click-paste in Xwayland programs.  In other words, I can select text
from a Wayland-native program and middle-click-paste in a Xwayland program, but
not in another Wayland-native program.

At the very least, I would like it if there was an implementation not backward
compatible with Xwayland.  Something is better than nothing.

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

[valgrind] [Bug 377420] Valgrind is missing an armv7 instruction

2017-03-09 Thread Peter Maydell
https://bugs.kde.org/show_bug.cgi?id=377420

Peter Maydell <peter.mayd...@linaro.org> changed:

   What|Removed |Added

 CC||peter.mayd...@linaro.org

--- Comment #1 from Peter Maydell <peter.mayd...@linaro.org> ---
Looks like the same as bug 344082 to me (insn is reading CNTVCT).

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

[valgrind] [Bug 377420] Valgrind is missing an armv7 instruction

2017-03-09 Thread Peter Maydell
https://bugs.kde.org/show_bug.cgi?id=377420

--- Comment #2 from Peter Maydell <peter.mayd...@linaro.org> ---
Doh, I meant bug 344802...

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

[kontact] [Bug 377381] New: Kontact crashes three times after system lost power and restarted during kontact closing

2017-03-08 Thread Peter Fodrek
https://bugs.kde.org/show_bug.cgi?id=377381

Bug ID: 377381
   Summary: Kontact crashes three times after system lost power
and restarted during kontact closing
   Product: kontact
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: peter.fod...@stuba.sk
  Target Milestone: ---

Application: kontact (5.4.2)

Qt Version: 5.7.1
Frameworks Version: 5.31.0
Operating System: Linux 4.8.14-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:
computer was restarted because of power lost.
Then I started  kontact after login.
Kontact crashes in mail and  kontact  newsgroup reader,as wel three
consecuitive times at least

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

Thread 28 (Thread 0x7f4c47f89700 (LWP 4397)):
#0  0x7ffd83dfbb12 in clock_gettime ()
#1  0x7f4d60d8d216 in clock_gettime () at /lib64/libc.so.6
#2  0x7f4d6172f771 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f4d618abe09 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7f4d618ac3b5 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f4d618ad75e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7f4d5a953d7d in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7f4d5a9547bb in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7f4d5a9549ac in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7f4d618ae18b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7f4d61857aea in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7f4d61685813 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7f4d6168a4c8 in  () at /usr/lib64/libQt5Core.so.5
#13 0x7f4d5cc17454 in start_thread () at /lib64/libpthread.so.0
#14 0x7f4d60d8037f in clone () at /lib64/libc.so.6

Thread 27 (Thread 0x7f4c45001700 (LWP 4383)):
#0  0x7f4d5cc1d10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f4d53af5609 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7f4d53af5c49 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#3  0x7f4d53af5e00 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#4  0x7f4d53af299c in  () at /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7f4d5cc17454 in start_thread () at /lib64/libpthread.so.0
#6  0x7f4d60d8037f in clone () at /lib64/libc.so.6

Thread 26 (Thread 0x7f4c45b02700 (LWP 4381)):
#0  0x7f4d5cc1d10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f4d53af5609 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7f4d53af5c49 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#3  0x7f4d53af5e00 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#4  0x7f4d53af299c in  () at /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7f4d5cc17454 in start_thread () at /lib64/libpthread.so.0
#6  0x7f4d60d8037f in clone () at /lib64/libc.so.6

Thread 25 (Thread 0x7f4c4878a700 (LWP 4346)):
#0  0x7ffd83dfbb12 in clock_gettime ()
#1  0x7f4d60d8d216 in clock_gettime () at /lib64/libc.so.6
#2  0x7f4d6172f771 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f4d618abe09 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7f4d618ac3b5 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f4d618ad9f4 in  () at /usr/lib64/libQt5Core.so.5
#6  0x7f4d5a953d7d in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7f4d5a9547bb in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7f4d5a9549ac in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7f4d618ae18b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7f4d61857aea in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7f4d61685813 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7f4d6168a4c8 in  () at /usr/lib64/libQt5Core.so.5
#13 0x7f4d5cc17454 in start_thread () at /lib64/libpthread.so.0
#14 0x7f4d60d8037f in clone () at /lib64/libc.so.6

Thread 24 (Thread 0x7f4c52fb5700 (LWP 4330)):
#0  0x7ffd83dfbb12 in clock_gettime ()
#1  0x7f4d60d8d216 in clock_gettime () at /lib64/libc.so.6
#2  0x7f4d6172f771 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f4d618abe09 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7f4d618ac3b5 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f4d618ad75e in  () at /usr/lib64/libQt5Core.so.5
#6  

[Akonadi] [Bug 345211] mails in ~/.local/share/local-mail don't show up any more

2017-03-13 Thread Peter Erdelyi
https://bugs.kde.org/show_bug.cgi?id=345211

--- Comment #5 from Peter Erdelyi <p.erde...@gmx.de> ---
Some of the updated packages and their versions:

kmail-16.12.2-1.fc25.x86_64
kf5-akonadi-server-16.12.2-1.fc25.x86_64
pim-storage-service-manager-16.12.2-1.fc25.x86_64

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

[Akonadi] [Bug 345211] mails in ~/.local/share/local-mail don't show up any more

2017-03-13 Thread Peter Erdelyi
https://bugs.kde.org/show_bug.cgi?id=345211

Peter Erdelyi <p.erde...@gmx.de> changed:

   What|Removed |Added

 CC||p.erde...@gmx.de

--- Comment #4 from Peter Erdelyi <p.erde...@gmx.de> ---
I use Fedora 25 and have updated my system also on 27.02.2017. KMail,
KMail-libs but also akonadi and pim packages were included. My subfolders have
disappeared after the update. They are still stored in .local/share/local-mail
folders, but can not be imported. Not as plaintext, not as archive file.

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

[konsole] [Bug 372991] Terminal gets stuck on interrupting a program that is outputting, preventing further output from being shown

2017-03-04 Thread Peter Wu
https://bugs.kde.org/show_bug.cgi?id=372991

--- Comment #11 from Peter Wu <pe...@lekensteyn.nl> ---
Looks like a race condition. Reproduced in QEMU 2.8.0 with Arch Linux and
Konsole 16.12.2 with plasma-desktop 5.9.3 (and also openbox). Cannot reproduce
with just one CPU (need -smp 2 or more). Command to start QEMU:

qemu-system-x86_64 -M pc,accel=kvm -m 2G -vga qxl -net user -net
nic,model=virtio -drive if=virtio,file=plasma.qcow2 -initrd initrd.img -kernel
arch/x86/boot/bzImage -append "rw root=/dev/vda1" -smp 4

A normal user was created with autologin (agetty --autologin). In openbox
(where no background activity exists), it was necessary to run "while lsdo
:;done" in a separate xterm process (which would display just the directory "x"
in the home directory on an 8GB ext4 filesystem).

Tested kernels (BAD = got hang, OK = could not reproduce hang within a few
minutes):
BAD v4.9.11
BAD v4.10.1
BAD v4.1.38
OK v3.12.70 (Note: to update display, had to switch between QEMU monitor and
back)
OK v3.18.48
OK v4.0.9 (needed "ln -s compiler-gcc5.h ../include/linux/compiler-gcc6.h" to
fix GCC6 build)
BAD v4.1.38 (yes, still bad, just to be sure)
BAD v4.1.15
OK v4.1.1 (could not reproduce)
OK v4.1.7-44-g49b85054a83d (git bisect starts)
BAD v4.1.13-91-g8d0fe5721d27
[OK v4.1.10-89-g5eb491ba5d06 (actually, this is also BAD! see below)]
BAD v4.1.12-7-g4508582e6a83
[OK v4.1.10-174-gc1d40e01ad8c (actually, this is also BAD! see below)]
BAD v4.1.11-13-g7b61554c25cb
BAD v4.1.10-195-g614ea4ea2c3f (hmm, I suspect that this commit is bad)
BAD v4.1.10-194-ga0533fb8cf60 (wait, I can still reproduce? did not expect
that, bisect probably wrong)
BAD v4.1.10-184-g0cf68c236f11
BAD v4.1.10-179-g249af812dcf3
BAD v4.1.10-174-gc1d40e01ad8c (not good, bad! Can also reproduce issue)
BAD v4.1.10-89-g5eb491ba5d06 (finally got hang after trying for 5 minutes)
OK v4.1.1 (can still not reproduce after 8 minutes)
[v4.1.10-89-g5eb491ba5d06 (can still not reproduce after 6 minutes)]
[BAD v4.1.10-194-ga0533fb8cf60 (can still reproduce after 2 minutes)]

Gave up after 2-3 hours of trying... The first known bad version is
v4.1.10-89-g5eb491ba5d06. The first *possibly* good version is
v4.1.7-44-g49b85054a83d, but a quick scan through the commits (keywords, "tty",
"console", "lock") does not yield suspicuous commits.

I think I'll just try to patch this without knowing the root cause.

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

[konsole] [Bug 372991] Terminal gets stuck on interrupting a program that is outputting, preventing further output from being shown

2017-03-04 Thread Peter Wu
https://bugs.kde.org/show_bug.cgi?id=372991

--- Comment #12 from Peter Wu <pe...@lekensteyn.nl> ---
Proposed patch: https://git.reviewboard.kde.org/r/129984/

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

[akregator] [Bug 116482] metakit: akregator crashes at startup

2017-08-01 Thread Peter Gückel
https://bugs.kde.org/show_bug.cgi?id=116482

Peter Gückel <pguec...@gmail.com> changed:

   What|Removed |Added

 CC|pguec...@gmail.com  |

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

[konsole] [Bug 355421] Konsole crashed on login

2017-08-03 Thread Peter Westlake
https://bugs.kde.org/show_bug.cgi?id=355421

--- Comment #14 from Peter Westlake <peter.westl...@pobox.com> ---
I'm not able to retest this now, sorry.

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

[konsole] [Bug 381901] New: Corsor position is 3 spaces offset (3 blanks before cursor)

2017-07-02 Thread peter flexer
https://bugs.kde.org/show_bug.cgi?id=381901

Bug ID: 381901
   Summary: Corsor position is 3 spaces offset (3 blanks before
cursor)
   Product: konsole
   Version: 15.12.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: bgkd.x.lok...@mamber.net
  Target Milestone: ---

Created attachment 106411
  --> https://bugs.kde.org/attachment.cgi?id=106411=edit
when moving the cursor three ticks left

My Cursor does not point to end of text but 3 spaces more right.

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

[konsole] [Bug 381901] Corsor position is spaces offset (0 at x=0, 6 at x=5 etc blanks before cursor)

2017-07-02 Thread peter flexer
https://bugs.kde.org/show_bug.cgi?id=381901

peter flexer <bgkd.x.lok...@mamber.net> changed:

   What|Removed |Added

Summary|Corsor position is 3 spaces |Corsor position is spaces
   |offset (3 blanks before |offset (0 at x=0, 6 at x=5
   |cursor) |etc blanks before cursor)

--- Comment #1 from peter flexer <bgkd.x.lok...@mamber.net> ---
The offest ist 0 at position 0 in a line. with every x+1 the offset is +1, so
my cursors trails a black "snake" that getting longer the more away the cursor
is from position 0.

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

[valgrind] [Bug 381556] arm64: Handle feature registers access on 4.11 Linux kernel or later

2017-07-06 Thread Peter Maydell
https://bugs.kde.org/show_bug.cgi?id=381556

Peter Maydell <peter.mayd...@linaro.org> changed:

   What|Removed |Added

 CC||peter.mayd...@linaro.org

--- Comment #3 from Peter Maydell <peter.mayd...@linaro.org> ---
I believe there's a plan in the works to add a docs patch to the kernel for the
hwcap bit meanings, but in the meantime the kernel code for them is here:
http://elixir.free-electrons.com/linux/latest/source/arch/arm64/kernel/cpufeature.c#L886

and it basically defines each HWCAP in terms of what the values in the relevant
fields of the architectural ID registers (ID_AA64*) need to be -- you can look
those up in the ARM ARM to find their meanings. The only one not in that table
I think is HWCAP_CPUID, which is the "support emulation of access to CPU ID
feature registers" bit.

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

[minuet] [Bug 379272] Unable to compile minuet on NixOS

2017-04-26 Thread Peter Hoeg
https://bugs.kde.org/show_bug.cgi?id=379272

Peter Hoeg <peterh...@gmail.com> changed:

   What|Removed |Added

Summary|Unable to compile on NixOS  |Unable to compile minuet on
   ||NixOS

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

[minuet] [Bug 379272] New: Unable to compile on NixOS

2017-04-26 Thread Peter Hoeg
https://bugs.kde.org/show_bug.cgi?id=379272

Bug ID: 379272
   Summary: Unable to compile on NixOS
   Product: minuet
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: sandroandr...@kde.org
  Reporter: peterh...@gmail.com
  Target Milestone: ---

Created attachment 105214
  --> https://bugs.kde.org/attachment.cgi?id=105214=edit
CMakeOutput.log

I'm trying to package minuet for NixOS but the linking stage fails:

[ 94%] Building CXX object
src/app/CMakeFiles/minuet.dir/exercisecontroller.cpp.o
[ 96%] Building CXX object src/app/CMakeFiles/minuet.dir/qrc_qml.cpp.o
[ 96%] Built target minuetfluidsynthsoundcontroller
[ 98%] Building CXX object src/app/CMakeFiles/minuet.dir/minuet_automoc.cpp.o
[100%] Linking CXX executable minuet
/nix/store/ykpcyj4f8mpjb0hjagrnnbxh0c7m3m3n-qtquickcontrols2-5.8.0/lib/libQt5QuickTemplates2.so.5:(*IND*+0x0):
multiple definition of `_end'
/nix/store/ykpcyj4f8mpjb0hjagrnnbxh0c7m3m3n-qtquickcontrols2-5.8.0/lib/libQt5QuickTemplates2.so.5:(*IND*+0x0):
multiple definition of `_edata'
/nix/store/ykpcyj4f8mpjb0hjagrnnbxh0c7m3m3n-qtquickcontrols2-5.8.0/lib/libQt5QuickTemplates2.so.5:(*IND*+0x0):
multiple definition of `__bss_start'
collect2: error: ld returned 1 exit status
make[2]: *** [src/app/CMakeFiles/minuet.dir/build.make:296: src/app/minuet]
Error 1
make[1]: *** [CMakeFiles/Makefile2:1466: src/app/CMakeFiles/minuet.dir/all]
Error 2
make: *** [Makefile:128: all] Error 2

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

[konversation] [Bug 379195] Konversation can't handle IDN urls

2017-04-25 Thread Peter Simonsson
https://bugs.kde.org/show_bug.cgi?id=379195

Peter Simonsson <peter.simons...@gmail.com> changed:

   What|Removed |Added

 Resolution|--- |INVALID
 Status|CONFIRMED   |RESOLVED

--- Comment #2 from Peter Simonsson <peter.simons...@gmail.com> ---
Seems it's some form of phishing protection in QUrl that kicks in as other
punycode urls works fine. For example http://xn--6kry05bl4a.no works fine. So
I'll close this one as phishing isn't really a good usecase. ;)

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

[konversation] [Bug 379195] Konversation can't handle IDN urls

2017-04-25 Thread Peter Simonsson
https://bugs.kde.org/show_bug.cgi?id=379195

Peter Simonsson <peter.simons...@gmail.com> changed:

   What|Removed |Added

 Ever confirmed|0   |1
 CC||peter.simons...@gmail.com
 Status|UNCONFIRMED |CONFIRMED

--- Comment #1 from Peter Simonsson <peter.simons...@gmail.com> ---
So far it seems the problem is QUrl::toEncoded() not returning the punycoded
url

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

[krita] [Bug 383911] New: (Cmd Z) Undo stops some other shortcuts from functioning.

2017-08-23 Thread Peter Traylor
https://bugs.kde.org/show_bug.cgi?id=383911

Bug ID: 383911
   Summary: (Cmd Z) Undo stops some other shortcuts from
functioning.
   Product: krita
   Version: 3.2.0
  Platform: Mac OS X Disk Images
OS: OS X
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: pe...@traylorpark.com
  Target Milestone: ---

When pressing (Cmd Z) Undo, the shortcuts for Eye Dropper (Cmd) and Pan (Space)
become inoperable. (Other keys could potentially be effected as well)

To "fix" this, clicking on the internal window of the file restores
functionality.

If "multiple document mode" is set to Windowed, this bug appears more often.
In Tabbed mode, it is less consistently reproducible. 

Behavior was also observed in version 3.1.4

2011 MacBook Air
MacOS 10.12.6
Intel HD Graphics 3000
1.7 GHz Intel Core i5

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

[akregator] [Bug 379496] New: akregator crashes on startup

2017-05-03 Thread Peter Gückel
https://bugs.kde.org/show_bug.cgi?id=379496

Bug ID: 379496
   Summary: akregator crashes on startup
   Product: akregator
   Version: 5.4.3
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: pguec...@gmail.com
  Target Milestone: ---

Application: akregator (5.4.3)

Qt Version: 5.7.1
Frameworks Version: 5.33.0
Operating System: Linux 4.11.0-1.fc26.x86_64 x86_64
Distribution: "Fedora release 26 (Twenty Six)"

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

I clicked the icon in the launcher and the application crashed. This has been
going on for about a week, likely since plasma 5.9.5-2 on fedora 26 alpha was
in the repo.

The crash can be reproduced every time.

-- Backtrace:
Application: Akregator (akregator), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f04fc5ba600 (LWP 2164))]

Thread 19 (Thread 0x7f047a526700 (LWP 2196)):
#0  0x7f05156737db in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f0509c66534 in QTWTF::TCMalloc_PageHeap::scavengerThread() () from
/lib64/libQt5Script.so.5
#2  0x7f0509c66579 in QTWTF::TCMalloc_PageHeap::runScavengerThread(void*)
() from /lib64/libQt5Script.so.5
#3  0x7f051566d36d in start_thread () from /lib64/libpthread.so.0
#4  0x7f051ee86e0f in clone () from /lib64/libc.so.6

Thread 18 (Thread 0x7f04a57fa700 (LWP 2191)):
#0  0x7f051ee7641d in read () from /lib64/libc.so.6
#1  0x7f050eb0e1e0 in g_wakeup_acknowledge () from /lib64/libglib-2.0.so.0
#2  0x7f050eaca038 in g_main_context_check () from /lib64/libglib-2.0.so.0
#3  0x7f050eaca4d0 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#4  0x7f050eaca63c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#5  0x7f051fc96d0b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#6  0x7f051fc46b8a in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#7  0x7f051fa9befa in QThread::exec() () from /lib64/libQt5Core.so.5
#8  0x7f051faa01ee in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#9  0x7f051566d36d in start_thread () from /lib64/libpthread.so.0
#10 0x7f051ee86e0f in clone () from /lib64/libc.so.6

Thread 17 (Thread 0x7f04a6ffd700 (LWP 2188)):
#0  0x7f05156737db in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f0518a82bb5 in
base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*)
() from /lib64/libQt5WebEngineCore.so.5
#2  0x7f0518a83009 in base::SequencedWorkerPool::Worker::Run() () from
/lib64/libQt5WebEngineCore.so.5
#3  0x7f0518a831b1 in base::SimpleThread::ThreadMain() () from
/lib64/libQt5WebEngineCore.so.5
#4  0x7f0518a7fdeb in base::(anonymous namespace)::ThreadFunc(void*) ()
from /lib64/libQt5WebEngineCore.so.5
#5  0x7f051566d36d in start_thread () from /lib64/libpthread.so.0
#6  0x7f051ee86e0f in clone () from /lib64/libc.so.6

Thread 16 (Thread 0x7f04a77fe700 (LWP 2187)):
#0  0x7f051ee7641d in read () from /lib64/libc.so.6
#1  0x7f05023f40b1 in pa_read () from
/usr/lib64/pulseaudio/libpulsecommon-10.0.so
#2  0x7f050dd8111e in pa_mainloop_prepare () from /lib64/libpulse.so.0
#3  0x7f050dd81b90 in pa_mainloop_iterate () from /lib64/libpulse.so.0
#4  0x7f050dd81c50 in pa_mainloop_run () from /lib64/libpulse.so.0
#5  0x7f050dd8fab9 in thread () from /lib64/libpulse.so.0
#6  0x7f0502423078 in internal_thread_func () from
/usr/lib64/pulseaudio/libpulsecommon-10.0.so
#7  0x7f051566d36d in start_thread () from /lib64/libpthread.so.0
#8  0x7f051ee86e0f in clone () from /lib64/libc.so.6

Thread 15 (Thread 0x7f04a7fff700 (LWP 2186)):
#0  0x7f0515673cda in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f0518a78be2 in base::ConditionVariable::TimedWait(base::TimeDelta
const&) () from /lib64/libQt5WebEngineCore.so.5
#2  0x7f0518a79412 in base::WaitableEvent::TimedWait(base::TimeDelta
const&) () from /lib64/libQt5WebEngineCore.so.5
#3  0x7f0518a5b00b in
base::MessagePumpDefault::Run(base::MessagePump::Delegate*) () from
/lib64/libQt5WebEngineCore.so.5
#4  0x7f0518a6d908 in base::RunLoop::Run() () from
/lib64/libQt5WebEngineCore.so.5
#5  0x7f0518a834b5 in base::Thread::Run(base::MessageLoop*) () from
/lib64/libQt5WebEngineCore.so.5
#6  0x7f0518a83774 in base::Thread::ThreadMain() () from
/lib64/libQt5WebEngineCore.so.5
#7  0x7f0518a7fdeb in base::(anonymous namespace)::ThreadFunc(void*) ()
from /lib64/libQt5WebEngineCore.so.5
#8  0x7f051566d36d in start_thread () from /lib64/libpthread.so.0
#9  0x7f051ee86e0f in clone () from /lib64/libc.so.6

Thread 14 (Thread 

[konsole] [Bug 380997] New: "Reverse scroll direction" ignored on awake

2017-06-08 Thread Peter Traylor
https://bugs.kde.org/show_bug.cgi?id=380997

Bug ID: 380997
   Summary: "Reverse scroll direction" ignored on awake
   Product: konsole
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: pe...@traylorpark.com
  Target Milestone: ---

When desktop comes out sleep, "reverse scroll direction" is ignored. Must
restart application for reverse scrolling to be accepted.

KDE Neon 5.10
Dual monitor setup

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

[konsole] [Bug 380997] "Reverse scroll direction" ignored on awake

2017-06-08 Thread Peter Traylor
https://bugs.kde.org/show_bug.cgi?id=380997

Peter Traylor <pe...@traylorpark.com> changed:

   What|Removed |Added

Version|unspecified |17.04.0

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

[konsole] [Bug 380998] New: Konsole transparency broken on bootup.

2017-06-08 Thread Peter Traylor
https://bugs.kde.org/show_bug.cgi?id=380998

Bug ID: 380998
   Summary: Konsole transparency broken on bootup.
   Product: konsole
   Version: 17.04.0
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: pe...@traylorpark.com
  Target Milestone: ---

Konsole transparency is broken (opaque) when resuming session (KDE
automatically launches Konsole) after starting up computer.

Must restart application for correct transparency.

KDE Neon 5.10
Dual monitor setup

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

[konsole] [Bug 380997] "Reverse scroll direction" ignored on awake

2017-06-08 Thread Peter Traylor
https://bugs.kde.org/show_bug.cgi?id=380997

Peter Traylor <pe...@traylorpark.com> changed:

   What|Removed |Added

 CC||pe...@traylorpark.com

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

[konsole] [Bug 380998] Konsole transparency broken on bootup.

2017-06-19 Thread Peter Traylor
https://bugs.kde.org/show_bug.cgi?id=380998

Peter Traylor <pe...@traylorpark.com> changed:

   What|Removed |Added

 CC||pe...@traylorpark.com

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

[pimsettingexporter] [Bug 372598] PIM Setting Exporter not backing up all Local Folders

2017-05-26 Thread Peter XP
https://bugs.kde.org/show_bug.cgi?id=372598

--- Comment #3 from Peter XP <p.wibber...@btinternet.com> ---
Laurent, 

I can't verify that at the moment.  The problem has come about because I am
wanting to transfer my emails from Mint 17.3 KDE to Mint 18.1 KDE, so I'm not
sure I can check whether I can replicate the problem, until I've transferred
the emails that I can't transfer!

What I have noticed is that the folders that PIMSettingsExporter sees are the
ones that are visible in .local/share/local-mails.  However, I seem to have a
lot of folders that are visible from within Kmail but don't show up in
.local/share/local-mails.  (I'm not sure whether these are all folders that
were imported from a previous installation, but I don't think so.) 

And just so as I'm completely snookered, I find that I cannot archive a lot of
the folders as I get the message, "Failed to archive the folder ''.
Downloading a message in folder '' failed." (NB There are plenty
of folders that aren't visible in .local/share/local-mails which do archive OK,
so I don't think the problems are linked.  

Any thoughts you may have on a way to proceed will be most gratefully received!

Regards

Peter

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

[konsole] [Bug 372991] Terminal gets stuck on interrupting a program that is outputting, preventing further output from being shown

2017-05-21 Thread Peter Wu
https://bugs.kde.org/show_bug.cgi?id=372991

Peter Wu <pe...@lekensteyn.nl> changed:

   What|Removed |Added

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

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

[konsole] [Bug 175283] Pressing ^C freezer term.

2017-05-21 Thread Peter Wu
https://bugs.kde.org/show_bug.cgi?id=175283

Peter Wu <pe...@lekensteyn.nl> changed:

   What|Removed |Added

 CC||pe...@lekensteyn.nl
   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=372991

--- Comment #3 from Peter Wu <pe...@lekensteyn.nl> ---
This issue was mentioned in commit
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=77dae6134440420bac334581a3ccee94cee1c054

"tty: pty: Fix ldisc flush after userspace become aware of the data already"

A recent incarnation of this issue could be bug 372991.

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

[konsole] [Bug 372991] Terminal gets stuck on interrupting a program that is outputting, preventing further output from being shown

2017-05-21 Thread Peter Wu
https://bugs.kde.org/show_bug.cgi?id=372991

--- Comment #19 from Peter Wu <pe...@lekensteyn.nl> ---
This bug is possibly resolved in the Linux kernel with this commit:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=77dae6134440420bac334581a3ccee94cee1c054

This change (v4.11-rc2-16-g77dae6134440) has been backported as:
v4.11.1-99-g34e01f920739
v4.10.16-82-g58d479441029
v4.9.28-70-g89c91ea37581
v4.4.68-46-g9bd2cc56a089

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

[basket] [Bug 380837] New: Crash when moving grouped notes

2017-06-04 Thread Peter Gruenbeck
https://bugs.kde.org/show_bug.cgi?id=380837

Bug ID: 380837
   Summary: Crash when moving grouped notes
   Product: basket
   Version: 2.0-git
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: kel...@ieee.org
  Reporter: pe...@automatingbusiness.com
  Target Milestone: ---

Created attachment 105917
  --> https://bugs.kde.org/attachment.cgi?id=105917=edit
Syslog around time of crash

Took a lot of notes (video transcript with time marks) and grouped them in a 2
panel layout.  Moving the grouped notes from the right side to left side panel,
had some trouble with paste placement inserting groups within groups
(collapsed) rather than between groups where the cursor appears.  After 5 or 6
attempts to correct it, Basket crashed losing all data on the page.

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

[plasmashell] [Bug 380522] New: Plasma crasched by systemstart

2017-06-03 Thread Peter G
https://bugs.kde.org/show_bug.cgi?id=380522

Bug ID: 380522
   Summary: Plasma crasched by systemstart
   Product: plasmashell
   Version: 5.5.5
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: partis...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.5.5)
 (Compiled from sources)
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: i have only startet the
computer and the only what i see was the error box plasma is crasht in 6
inentical threads.
This error comes in the last 3 times when i probing the computer starting.

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

Thread 7 (Thread 0x7f3bc700 (LWP 2037)):
#0  0x7f3c8904cbfd in poll () at /lib64/libc.so.6
#1  0x7f3c85729e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f3c85729f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f3c89979d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f3c89920d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f3c8974261a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f3c8d5f2282 in  () at /usr/lib64/libQt5Quick.so.5
#7  0x7f3c8974732f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f3c888560a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7f3c8905502d in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7f3c5bbd7700 (LWP 2034)):
#0  0x7f3c8885a03f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f3c8f22586b in  () at /usr/lib64/libQt5Script.so.5
#2  0x7f3c8f225899 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7f3c888560a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f3c8905502d in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7f3c615c4700 (LWP 2033)):
#0  0x7f3c89048ccd in read () at /lib64/libc.so.6
#1  0x7f3c811d4073 in  () at /usr/lib64/tls/libnvidia-tls.so.375.39
#2  0x7f3c8576ab60 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f3c8572 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f3c85729df8 in  () at /usr/lib64/libglib-2.0.so.0
#5  0x7f3c85729f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#6  0x7f3c89979d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#7  0x7f3c89920d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#8  0x7f3c8974261a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#9  0x7f3c8ca56e18 in  () at /usr/lib64/libQt5Qml.so.5
#10 0x7f3c8974732f in  () at /usr/lib64/libQt5Core.so.5
#11 0x7f3c888560a4 in start_thread () at /lib64/libpthread.so.0
#12 0x7f3c8905502d in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f3c62d6f700 (LWP 2032)):
#0  0x7f3c8904cbfd in poll () at /lib64/libc.so.6
#1  0x7f3c85729e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f3c85729f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f3c89979d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f3c89920d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f3c8974261a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f3c8ca56e18 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7f3c8974732f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f3c888560a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7f3c8905502d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f3c6e8cb700 (LWP 2031)):
#0  0x7f3c8904cbfd in poll () at /lib64/libc.so.6
#1  0x7f3c85729e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f3c85729f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f3c89979d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f3c89920d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f3c8974261a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f3c8ca56e18 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7f3c8974732f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f3c888560a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7f3c8905502d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f3c78981700 (LWP 2022)):
#0  0x7f3c8904cbfd in poll () at /lib64/libc.so.6
#1  0x7f3c8dfa0422 in  () at /usr/lib64/libxcb.so.1
#2  0x7f3c8dfa200f in xcb_wait_for_event () at 

[yakuake] [Bug 381351] Multi HiDPI screens invalid placement

2017-06-18 Thread Peter Marshall
https://bugs.kde.org/show_bug.cgi?id=381351

--- Comment #1 from Peter Marshall <p...@goteck.co.uk> ---
Sorry - mistake in code:

QRect MainWindow::getDesktopGeometry()
{
QRect screenGeometry =
QApplication::desktop()->availableGeometry(getScreen());
return screenGeometry;
}

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

[yakuake] [Bug 381351] New: Multi HiDPI screens invalid placement

2017-06-18 Thread Peter Marshall
https://bugs.kde.org/show_bug.cgi?id=381351

Bug ID: 381351
   Summary: Multi HiDPI screens invalid placement
   Product: yakuake
   Version: Git (Frameworks 5)
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: h...@kde.org
  Reporter: p...@goteck.co.uk
  Target Milestone: ---

On my setup with two hidpi monitors (2560x1440 and 3840x2160) and a window
scaling factor of 1.3, the yakuake window would not have the correct
coordinates on the larger screen.

Changing the MainWindow::getDesktopGeometry() code to just this fixes the issue
for me:

QRect MainWindow::getDesktopGeometry()
{
QRect screenGeometry =
QApplication::desktop()->availableGeometry(getScreen());
return screenGeometry();
}

It works with full screen etc. It removes a lot of code relating to struts - it
seems that that code doesn't work in my multi-monitor scenario.

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

[yakuake] [Bug 381351] Multi HiDPI screens invalid placement

2017-06-18 Thread Peter Marshall
https://bugs.kde.org/show_bug.cgi?id=381351

--- Comment #2 from Peter Marshall <p...@goteck.co.uk> ---
System is X11 based KDE, running OpenSUSE Tumbleweed.

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

[konversation] [Bug 378854] Konversation crashes randomly

2017-06-10 Thread Peter Simonsson
https://bugs.kde.org/show_bug.cgi?id=378854

Peter Simonsson <peter.simons...@gmail.com> changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
  Latest Commit||https://commits.kde.org/kon
   ||versation/783dc0f595ecf90e3
   ||7225a57da0ffa2c030a470d
 Resolution|--- |FIXED

--- Comment #3 from Peter Simonsson <peter.simons...@gmail.com> ---
Git commit 783dc0f595ecf90e37225a57da0ffa2c030a470d by Peter Simonsson.
Committed on 10/06/2017 at 18:41.
Pushed by psn into branch '1.7'.

Fix crash in join handling in inputfilter

Make sure to check size of parameter list for extended join.

M  +6-13   src/irc/inputfilter.cpp

https://commits.kde.org/konversation/783dc0f595ecf90e37225a57da0ffa2c030a470d

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

[konversation] [Bug 381066] Konversation crashes with a segmentation fault

2017-06-13 Thread Peter Simonsson
https://bugs.kde.org/show_bug.cgi?id=381066

Peter Simonsson <peter.simons...@gmail.com> changed:

   What|Removed |Added

 CC||peter.simons...@gmail.com

--- Comment #2 from Peter Simonsson <peter.simons...@gmail.com> ---
(In reply to Tore Havn from comment #1)
> Same problem happens for me.
> 
> Application: Konversation 1.7.2
> Qt version: 5.7.1
> Frameworks version: 5.35.0
> Kernel version: 4.4.0-79-generic x86_64
> Distribution: KDE neon 5.10
> 
> Description:
> This has actually been happening for a few months, but I had mostly decided
> to blame my filesystem (btrfs), which was experiencing problems in general.
> Those have been fixed, and the problem persists.
> 
> I have configured it to automatically connect to multiple servers and
> channels at startup (5 servers and ~20 channels). I usually leave my
> computer on during the night, and every morning Konversation has segfaulted.
> Restarting it would only help for about an hour or so before segfaulting
> again.
> 
> I recently emptied all my old irc logs and this seems to have made
> Konversation last a few hours more, but this morning it had once again
> segfaulted.
> 
> The program is usually segfaults while it is minimized or I'm sleeping, so
> no user action is taken to make it happen. There's no pattern in usage
> before it segfaults, as far as I can tell.
> 
> Thread 1 (Thread 0x7f6856bff8c0 (LWP 4719)):
> [KCrash Handler]
> #6  0x7f68628ec19f in std::__atomic_base::load
> (__m=std::memory_order_relaxed, this=) at
> /usr/include/c++/5/bits/atomic_base.h:396
> #7  QAtomicOps::load (_q_value=...) at
> ../../include/QtCore/../../src/corelib/arch/qatomic_cxx11.h:227
> #8  QBasicAtomicInteger::load (this=) at
> ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:99
> #9  QtPrivate::RefCount::ref (this=) at
> ../../include/QtCore/../../src/corelib/tools/qrefcount.h:55
> #10 QString::operator= (this=this@entry=0x7ffd70b1a270, other=...) at
> tools/qstring.cpp:1814
> #11 0x005124af in InputFilter::parseClientCommand
> (this=this@entry=0x3124810, prefix=..., command=..., parameterList=...,
> messageTags=...) at /workspace/build/src/irc/inputfilter.cpp:584
> #12 0x0051d8f8 in InputFilter::parseLine (this=this@entry=0x3124810,
> line=...) at /workspace/build/src/irc/inputfilter.cpp:127
> #13 0x004c9a64 in Server::processIncomingData (this=0x3124700) at

This isn't the same bug... This should have been fixed already see bug 378854.

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

[konqueror] [Bug 355849] Konqueror Freezes KDE Session When Opening Hyperlink In New Tab

2017-05-04 Thread Peter Gückel
https://bugs.kde.org/show_bug.cgi?id=355849

Peter Gückel <pguec...@gmail.com> changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |INVALID

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

[kaddressbook] [Bug 364678] kaddressbook does not sync contacts

2017-05-04 Thread Peter Gückel
https://bugs.kde.org/show_bug.cgi?id=364678

Peter Gückel <pguec...@gmail.com> changed:

   What|Removed |Added

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

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

[knode] [Bug 363410] knode doesn't respect X-Archive:encrypt in the header

2017-05-04 Thread Peter Gückel
https://bugs.kde.org/show_bug.cgi?id=363410

Peter Gückel <pguec...@gmail.com> changed:

   What|Removed |Added

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

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

[digikam] [Bug 384976] New: Missing menu items

2017-09-22 Thread Hans-Peter
https://bugs.kde.org/show_bug.cgi?id=384976

Bug ID: 384976
   Summary: Missing menu items
   Product: digikam
   Version: 5.7.0
  Platform: Manjaro
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Usability-Menus
  Assignee: digikam-bugs-n...@kde.org
  Reporter: hans...@web.de
  Target Milestone: ---

Several menu items are missing in the drop-down menus: send email, create html
gallery, print. Those actions can be configured for the tool bar and they work
as expected, so they are there.

Command line shows (amongst the usual other messages):
...
kipi.library: Plugin  "KMLExport"  (generic name:  "KMLExport" ) is in the
ignore list from host application
kipi.library: Plugin  "Bilder senden"  (generic name:  "SendImages" ) is in the
ignore list from host application
kipi.library: Plugin  "Bilder drucken"  (generic name:  "Print images" ) is in
the ignore list from host application
...

Modul Configuration shows 15 Kipi modules (kipi-plugins 5.7, libkipi 5.2), but
the functions mentioned above are not listed there.

HP

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

[digikam] [Bug 384976] Missing menu items

2017-09-23 Thread Hans-Peter
https://bugs.kde.org/show_bug.cgi?id=384976

Hans-Peter <hans...@web.de> changed:

   What|Removed |Added

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

--- Comment #5 from Hans-Peter <hans...@web.de> ---
Thanks, this works.

HP

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

<    2   3   4   5   6   7   8   9   10   11   >