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

[Huon via KDE Bugzilla]

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

Huon  changed:

   What|Removed |Added

 CC||huo...@gmail.com

--- Comment #7 from Huon  ---
Unchecking "Ask the window manager to perform the animation" (in Configure ->
Window) seems to have fixed this for me. FWIW I got the dodgy focus seemingly
randomly, about 30% of the time. I did/do not have "Focus Follows Mouse" turned
on.

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

[ktorrent] [Bug 360855] Unable to restart torrents after stopping them all

[Valentin via KDE Bugzilla]

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

--- Comment #1 from Valentin  ---
I managed to restart everything through the Suspend Torrents action in the
Torrents menu.

Now while I feel a bit dumb, there are many confusing features that led to
this, among which:
- The system tray icon disappears after the torrents got suspended
- The icon on the torrents was the "stop" one, no the "pause" one
- The Start / Stop / Start All / Stop All actions, although alternatively
enabled / disabled, had no effect and gave no feedback
- It is not possible to disable "Suspend Torrents" through the torrents'
context menus
- The Suspend Torrents button in the toolbar was hidden

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

[plasmashell] [Bug 361030] Show window title in Icon-Only Task Manager Tooltips

[Sudhir Khanger via KDE Bugzilla]

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

--- Comment #1 from Sudhir Khanger  ---
Created attachment 98108
  --> https://bugs.kde.org/attachment.cgi?id=98108=edit
screenshot of grouped window preview

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

[plasmashell] [Bug 361030] New: Show window title in Icon-Only Task Manager Tooltips

[Sudhir Khanger via KDE Bugzilla]

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

Bug ID: 361030
   Summary: Show window title in Icon-Only Task Manager Tooltips
   Product: plasmashell
   Version: 5.5.5
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Icons-only Task Manager
  Assignee: h...@kde.org
  Reporter: sud...@sudhirkhanger.com
CC: plasma-b...@kde.org

Icon-Only Task Manager tooltips show grouped windows without a title on mouse
hover. It would be great if they were to show window title to easily
distinguish between them.

Reproducible: Always


Actual Results:  
Grouped window preview is shown without window title in Icon-Only Task Manager
tooltip

Expected Results:  
Window title should be shown when previewing more than one window in the
Icon-Only Task Manager tooltip

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

[plasma-nm] [Bug 346118] Plasmashell crash when disconnecting/reconnecting my WiFi connection after changing MTU

[Ben Klopfenstein via KDE Bugzilla]

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

Ben Klopfenstein  changed:

   What|Removed |Added

 CC|benk...@gmail.com   |

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

[plasmashell] [Bug 315488] icon-only task manager groups chrome/chromium web apps with chrome/chromium

[Sudhir Khanger via KDE Bugzilla]

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

--- Comment #28 from Sudhir Khanger  ---
Just wanted to say that even at the cost of showing identical icons and no way
of distinguishing among windows I would really like to see grouping disabled
similar to task manager. First open preview and then pick a window really takes
a toll on fastly moving among windows. People can make their choice even if it
is not the best option.

PS:- Is there a Chrome bug filed so this gets fixed eventually? I will read
this thread over, to my best understanding, and file one if it is not.

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

[Powerdevil] [Bug 337674] kded5 is eating CPU

[Christoph Feck via KDE Bugzilla]

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

--- Comment #88 from Christoph Feck  ---
Please check which kded module is responsible. You can disable them in the
SystemSettings Service Manager.

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

[gwenview] [Bug 361029] view ordering by name mismatch

[MuStArt via KDE Bugzilla]

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

MuStArt  changed:

   What|Removed |Added

 CC||must...@gmail.com

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

[gwenview] [Bug 361029] New: view ordering by name mismatch

[MuStArt via KDE Bugzilla]

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

Bug ID: 361029
   Summary: view ordering by name mismatch
   Product: gwenview
   Version: Other (add details in bug description)
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: must...@gmail.com
CC: myr...@kde.org

There are only 3 orber by possibilities: file name, date and size.
My photo files looks like 13c12A_d9594 tanitlak_1M.jpg , 13c13G_e3754_1m.jpg ,
10126Pecs_d5560.jpg , 10130Pecs_d5599.jpg when browse them by name!
How on Earth could be this? In Krusader, file name ordering by name is good
anyway.
GwenView v2.8.5 (KDE: 4.8.5) 

Reproducible: Always

Steps to Reproduce:
1. open jpg file with Gwenview
2. browse them with Order by: File name


Actual Results:  
Always occurs, only this 4 files in directory as the given names stand in a
mixed way mentioned above.

Expected Results:  
10126*,10130*,13c12*,13c13*

It would be good idea adding more sorting options, like other file manager
programs, e.g. natural, alphanumerical as numbers, or shooting exif date as
well.

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

[kmymoney4] [Bug 361021] CSV importer: The transaction has missing assignment of...

[allan via KDE Bugzilla]

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

--- Comment #8 from allan  ---
(In reply to NSLW from comment #0)
> Buy transactions imported by CSV importer always have missing assignment

It's not correct to say that they '...always have missing assignment'  it is
only under certain conditions.

> (see attachment).
> 
> Reproducible: Always
> 
> Steps to Reproduce:
> 1. file->import csv
> 2. choose investment
> 3. create new profile
> 4. open "test file.csv" and assign columns to values (see attachment)
> 5. FieldDelimiter to comma
> 6. TextDelimiter to double quotes
> 7. DecimalSymbol to comma
> 8. ImportCSV
> 
> Actual Results:  
> In ledger:
> All buy operations have missing assignment
> On home page:
> Balance for banking and investment account are equal.
> 
> Expected Results:  
> In ledger:
> All operations should have assignment
> On home page:
> Balance for banking and investment account should be equal only in special
> cases. Correct difference in balance is shown in attachment.
> 
> To get good balance without the need of patching one has to double click
> every operation in ledger and press enter button. Upon completion column
> value will have exact same values as column from patched KMM.

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

[kmymoney4] [Bug 361021] CSV importer: The transaction has missing assignment of...

[allan via KDE Bugzilla]

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

--- Comment #7 from allan  ---
(In reply to Jack from comment #5)
> Without looking at the details, I believe this is not a problem with the CSV
> importer, but with any KMM import of an investment transaction which
> requires a brokerage account for transfer of funds.

That's not exactly true.  I've just done a QIF import of a Buy transaction, as
a test, and that correctly identified the checking account to be used.

There is also another issue, with fees sometimes getting the wrong sign, which
I identified in https://bugs.kde.org/show_bug.cgi?id=360129.  I think the patch
in this current bug may be related.

>  (I have it with OFX
> import.) The issue is that when KMM imports an investment transaction, it
> does not specify the brokerage account, so the missing assignment refers to
> the amount which would go to that account.  When you edit the transaction,
> KMM automatically enters the brokerage account, so the error disappears.

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

[ark] [Bug 361028] New: Zip archives opening like Nan

[Tarlis via KDE Bugzilla]

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

Bug ID: 361028
   Summary: Zip archives opening like Nan
   Product: ark
   Version: 2.19
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: elvis.angelac...@kdemail.net
  Reporter: nighttar...@gmail.com
CC: rak...@freebsd.org, rthoms...@gmail.com

Application: ark (2.19)
KDE Platform Version: 4.14.13
Qt Version: 4.8.6
Operating System: Linux 4.5.0-040500-generic x86_64
Distribution: Ubuntu 14.04.4 LTS

-- Information about the crash:
Zip archives opening like Nan

The crash can be reproduced every time.

-- Backtrace:
Application: Ark (ark), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f1fa40d97c0 (LWP 20541))]

Thread 2 (Thread 0x7f1f8e883700 (LWP 20547)):
#0  0x7f1f9dd6c61a in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f1f9dd6c9a9 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f1f9dd2ae9d in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f1f9dd2b0ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f1fa18477be in QEventDispatcherGlib::processEvents
(this=0x7f1f8800e7a0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#5  0x7f1fa18190af in QEventLoop::processEvents
(this=this@entry=0x7f1f8e882de0, flags=...) at kernel/qeventloop.cpp:149
#6  0x7f1fa18193a5 in QEventLoop::exec (this=this@entry=0x7f1f8e882de0,
flags=...) at kernel/qeventloop.cpp:204
#7  0x7f1fa1715c5f in QThread::exec (this=this@entry=0x21e6ad0) at
thread/qthread.cpp:537
#8  0x7f1fa17fa823 in QInotifyFileSystemWatcherEngine::run (this=0x21e6ad0)
at io/qfilesystemwatcher_inotify.cpp:265
#9  0x7f1fa171832f in QThreadPrivate::start (arg=0x21e6ad0) at
thread/qthread_unix.cpp:349
#10 0x7f1f9e20a182 in start_thread (arg=0x7f1f8e883700) at
pthread_create.c:312
#11 0x7f1fa10ce47d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7f1fa40d97c0 (LWP 20541)):
[KCrash Handler]
#5  0x7f1fa30077b0 in KXMLGUIFactory::removeClient(KXMLGUIClient*) () from
/usr/lib/libkdeui.so.5
#6  0x7f1f92116e64 in Ark::Part::~Part (this=0x2262f10,
__in_chrg=, __vtt_parm=) at
../../part/part.cpp:141
#7  0x7f1f92116ef9 in Ark::Part::~Part (this=0x2262f10,
__in_chrg=, __vtt_parm=) at
../../part/part.cpp:146
#8  0x7f1fa37fa541 in KParts::Part::slotWidgetDestroyed() () from
/usr/lib/libkparts.so.4
#9  0x7f1fa182e87a in QMetaObject::activate (sender=sender@entry=0x2265160,
m=m@entry=0x7f1fa1b7bc40 ,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffea2341770)
at kernel/qobject.cpp:3539
#10 0x7f1fa182f27f in QObject::destroyed (this=this@entry=0x2265160,
_t1=_t1@entry=0x2265160) at .moc/release-shared/moc_qobject.cpp:148
#11 0x7f1fa1833193 in QObject::~QObject (this=0x2265160,
__in_chrg=) at kernel/qobject.cpp:843
#12 0x7f1fa2253ddc in QWidget::~QWidget (this=0x2265160,
__in_chrg=) at kernel/qwidget.cpp:1554
#13 0x7f1fa264ba49 in QSplitter::~QSplitter (this=0x2265160,
__in_chrg=) at widgets/qsplitter.cpp:1056
#14 0x7f1fa1831168 in QObjectPrivate::deleteChildren
(this=this@entry=0x2254260) at kernel/qobject.cpp:1907
#15 0x7f1fa2253d47 in QWidget::~QWidget (this=0x22536f0,
__in_chrg=) at kernel/qwidget.cpp:1679
#16 0x7f1fa2ff9ab9 in KVBox::~KVBox() () from /usr/lib/libkdeui.so.5
#17 0x7f1fa1831168 in QObjectPrivate::deleteChildren
(this=this@entry=0x22546a0) at kernel/qobject.cpp:1907
#18 0x7f1fa2253d47 in QWidget::~QWidget (this=0x2206c00,
__in_chrg=) at kernel/qwidget.cpp:1679
#19 0x7f1f92120f64 in ~ArkViewer (this=0x2206c00, __in_chrg=) at ../../part/arkviewer.cpp:56
#20 ArkViewer::~ArkViewer (this=0x2206c00, __in_chrg=) at
../../part/arkviewer.cpp:58
#21 0x7f1fa1831168 in QObjectPrivate::deleteChildren
(this=this@entry=0x1e145f0) at kernel/qobject.cpp:1907
#22 0x7f1fa2253d47 in QWidget::~QWidget (this=0x1ffdef0,
__in_chrg=) at kernel/qwidget.cpp:1679
#23 0x7f1fa264ba49 in QSplitter::~QSplitter (this=0x1ffdef0,
__in_chrg=) at widgets/qsplitter.cpp:1056
#24 0x7f1fa37fa046 in KParts::Part::~Part() () from /usr/lib/libkparts.so.4
#25 0x7f1f92116ea4 in Ark::Part::~Part (this=0x1fe18b0,
__in_chrg=, __vtt_parm=) at
../../part/part.cpp:139
#26 0x7f1f92116ef9 in Ark::Part::~Part (this=0x1fe18b0,
__in_chrg=, __vtt_parm=) at
../../part/part.cpp:146
#27 0x0040dc5f in MainWindow::~MainWindow (this=this@entry=0x1ef5080,
__in_chrg=, __vtt_parm=) at
../../app/mainwindow.cpp:72
#28 0x0040dd09 in MainWindow::~MainWindow (this=0x1ef5080,
__in_chrg=, __vtt_parm=) at
../../app/mainwindow.cpp:74
#29 0x7f1fa1832c58 in QObject::event (this=this@entry=0x1ef5080,

[kdeplasma-addons] [Bug 360120] Show Desktop Applet corrupts panel when added to it (spacing issues)

[Kai Uwe Broulik via KDE Bugzilla]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

   Version Fixed In||5.6.1
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #6 from Kai Uwe Broulik  ---
Fixed by
https://quickgit.kde.org/?p=kdeplasma-addons.git=commit=e164ae7c02f5579e02d26842bee6a4a450e01871

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

[kdeplasma-addons] [Bug 360120] Show Desktop Applet corrupts panel when added to it (spacing issues)

[Marius Cirsta via KDE Bugzilla]

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

Marius Cirsta  changed:

   What|Removed |Added

 CC||k...@privat.broulik.de

--- Comment #5 from Marius Cirsta  ---
 Kai sorry for adding you here like this but I was thinking that maybe you'd
have an idea on this since you've done some work on "show desktop".
 Thanks.

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

[kdeplasma-addons] [Bug 360120] Show Desktop Applet corrupts panel when added to it (spacing issues)

[Marius Cirsta via KDE Bugzilla]

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

Marius Cirsta  changed:

   What|Removed |Added

 CC||marius_...@yahoo.com
 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #4 from Marius Cirsta  ---
 Happens to me too. Using qt 5.6 and kdeplasma-addons 5.6

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

[systemsettings] [Bug 361027] New: Al cambiar estilo de ventana a uno descargado la aplicación colapsó.

[Mauricio J . Adonis C . via KDE Bugzilla]

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

Bug ID: 361027
   Summary: Al cambiar estilo de ventana a uno descargado la
aplicación colapsó.
   Product: systemsettings
   Version: 5.4.1
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: mike.alfa.2...@gmail.com

Application: systemsettings5 (5.4.1)

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

-- Information about the crash:
Intenté cambiar el estilo de ventana a uno que había descargado desde el centro
oficial de descarga de estos archivos

-- Backtrace:
Application: Preferencias del sistema (systemsettings5), signal: Segmentation
fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
[Current thread is 1 (Thread 0x7f1080e79800 (LWP 22614))]

Thread 5 (Thread 0x7f106daf1700 (LWP 22615)):
#0  0x7f107d5bd88d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f107b29bbd2 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f107b29d74f in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f10708faa39 in QXcbEventReader::run (this=0xff0e90) at
qxcbconnection.cpp:1105
#4  0x7f107dcbc2be in QThreadPrivate::start (arg=0xff0e90) at
thread/qthread_unix.cpp:337
#5  0x7f107aa116aa in start_thread (arg=0x7f106daf1700) at
pthread_create.c:333
#6  0x7f107d5c8e9d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7f105e945700 (LWP 22620)):
#0  0x7f107a530869 in g_mutex_lock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f107a4eb789 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f107a4ec11b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f107a4ec2fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f107def329b in QEventDispatcherGlib::processEvents
(this=0x7f10580008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7f107de9975a in QEventLoop::exec (this=this@entry=0x7f105e944da0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7f107dcb73d4 in QThread::exec (this=) at
thread/qthread.cpp:503
#7  0x7f107c61ef85 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7f107dcbc2be in QThreadPrivate::start (arg=0x146d9a0) at
thread/qthread_unix.cpp:337
#9  0x7f107aa116aa in start_thread (arg=0x7f105e945700) at
pthread_create.c:333
#10 0x7f107d5c8e9d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f1056da1700 (LWP 22621)):
#0  0x7d2ac947 in ?? ()
#1  0x7d2acc75 in clock_gettime ()
#2  0x7f107d5d733d in __GI___clock_gettime (clock_id=,
tp=tp@entry=0x7f1056da0b10) at ../sysdeps/unix/clock_gettime.c:115
#3  0x7f107dd6d3a6 in qt_clock_gettime (ts=0x7f1056da0b10, clock=) at tools/qelapsedtimer_unix.cpp:105
#4  do_gettime (frac=, sec=) at
tools/qelapsedtimer_unix.cpp:161
#5  qt_gettime () at tools/qelapsedtimer_unix.cpp:170
#6  0x7f107def0d29 in QTimerInfoList::updateCurrentTime
(this=this@entry=0x7f1050002cd0) at kernel/qtimerinfo_unix.cpp:84
#7  0x7f107def1295 in QTimerInfoList::timerWait (this=0x7f1050002cd0,
tm=...) at kernel/qtimerinfo_unix.cpp:379
#8  0x7f107def267e in timerSourcePrepareHelper (timeout=0x7f1056da0be4,
src=) at kernel/qeventdispatcher_glib.cpp:127
#9  timerSourcePrepare (source=, timeout=0x7f1056da0be4) at
kernel/qeventdispatcher_glib.cpp:160
#10 0x7f107a4eb77d in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x7f107a4ec11b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x7f107a4ec2fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#13 0x7f107def329b in QEventDispatcherGlib::processEvents
(this=0x7f1058c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#14 0x7f107de9975a in QEventLoop::exec (this=this@entry=0x7f1056da0da0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#15 0x7f107dcb73d4 in QThread::exec (this=) at
thread/qthread.cpp:503
#16 0x7f107c61ef85 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#17 0x7f107dcbc2be in QThreadPrivate::start (arg=0x1975ad0) at
thread/qthread_unix.cpp:337
#18 0x7f107aa116aa in start_thread (arg=0x7f1056da1700) at
pthread_create.c:333
#19 0x7f107d5c8e9d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f1054a59700 (LWP 22624)):
[KCrash Handler]
#6  0x7f107e379b4e in KConfig::name() const () from
/usr/lib/x86_64-linux-gnu/libKF5ConfigCore.so.5
#7  0x7f107e398805 in KSharedConfig::openConfig(QString const&,
QFlags, 

[Breeze] [Bug 356940] kalarm crash on start up

[Olivier Trichet via KDE Bugzilla]

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

Olivier Trichet  changed:

   What|Removed |Added

 CC||n...@nivalis.org

--- Comment #2 from Olivier Trichet  ---
Created attachment 98107
  --> https://bugs.kde.org/attachment.cgi?id=98107=edit
Testcase

This testcase reproduces this crash (encountered with another application).
Tested with :
   - Qt 5.5.1 (Debian package)
   - Breeze 5.4.3 (Debian package) and git revision f4032a191f5e

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

[Powerdevil] [Bug 361022] Laptop goes to sleep when closing lid even with an external display connected

[Ovidiu D . Niţan via KDE Bugzilla]

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

Ovidiu D. Niţan  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |UNCONFIRMED

--- Comment #2 from Ovidiu D. Niţan  ---
No, it doesn't

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

[cantor] [Bug 359918] Licensing issues

[Filipe Saraiva via KDE Bugzilla]

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

Filipe Saraiva  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
   Platform|Debian unstable |Compiled Sources
 Ever confirmed|0   |1

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

[Powerdevil] [Bug 337674] kded5 is eating CPU

[Trioxin via KDE Bugzilla]

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

Trioxin  changed:

   What|Removed |Added

 CC||tomash...@protonmail.com

--- Comment #87 from Trioxin  ---
Not verified fixed for me. kded5 is killing my CPU at a constant 25%.

Kubuntu 15.10
Plasma: 5.4.2
QT: 5.4.2

Debug info: http://hastebin.com/uqoriyuhoq.avrasm

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

[dolphin] [Bug 356098] feauture request: move *.slave-socket files to tmp folder...

[Florian Röhrer via KDE Bugzilla]

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

Florian Röhrer  changed:

   What|Removed |Added

 CC||florian.roeh...@gmx.net

--- Comment #1 from Florian Röhrer  ---
That would be really nice as those files are really annoying me

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

[kdeplasma-addons] [Bug 361025] New: Using notification.createNotification({"timeout": 2000}) instead of {"expireTimeout": ...}

[Chris Holland via KDE Bugzilla]

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

Bug ID: 361025
   Summary: Using notification.createNotification({"timeout":
2000}) instead of {"expireTimeout": ...}
   Product: kdeplasma-addons
   Version: 5.5.4
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: timer
  Assignee: plasma-b...@kde.org
  Reporter: zrenf...@gmail.com

The notification remains in the systray until the user dismisses it. It does
hide, but a (1) stays in the systray until you deal with it.

The timer applet currently uses the "timeout" key:
https://github.com/KDE/kdeplasma-addons/blob/master/applets/timer/package/contents/ui/main.qml#L76

When currently, the datasource notification.createNotification only supports
"expireTimeout":
https://github.com/KDE/plasma-workspace/blob/master/dataengines/notifications/notifications.operations#L29

It looks like it changed from "timeout" to "expireTimeout" here:
https://github.com/KDE/plasma-workspace/commit/a12bb76502952749c069b9ab70ac61ee1353079b#diff-236026257e1c90327fc3db97f089c673L23

I tested using "expireTimeout" in my own applet, and the notification dismisses
properly.

Reproducible: Always

Steps to Reproduce:
Start a timer, wait for it to finish, notification appears.

Actual Results:  
Notification hides, but stays in systray history until manually dismissed.

Expected Results:  
Should just disappear.

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

[plasmashell] [Bug 350994] Opened trash folder

[Alexander Potashev via KDE Bugzilla]

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

Alexander Potashev  changed:

   What|Removed |Added

 CC||aspotas...@gmail.com

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

[kwin] [Bug 361018] kwin crashes

[Thomas Lübking via KDE Bugzilla]

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

Thomas Lübking  changed:

   What|Removed |Added

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

--- Comment #1 from Thomas Lübking  ---
mpv suspends the compositor, that deletes the QML driven buttons in the desktop
grid (present windows close button might be affected likewise) and that has
somehow a bad teardown order.

No idea whether to blame QtQuick, MESA or the particular driver - looks a bit
like dri2_dpy or dri2_dpy->core (in
https://cgit.freedesktop.org/cgit/?url=mesa/mesa/tree/src/egl/drivers/dri2/egl_dri2.c)
are 0x0 or dangeling?

=> woraround is to either adda rule that forces MPV to *not* suspend the
compositor (but you'll likely get segfaults on doing that by shortcut as well)
or disable the buttons for the desktop grid and present windows effects.

Chances to check what's going on in egl/drivers/dri2/egl_dri2.c (printf the
pointer positions or similar - ideally it's just a nullptr deref)?

Another possible workaouround in KWin might be to take the buttonviews out of
moc's child/parent related and attempt to deleteLater them - but that's sick.

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

[Breeze] [Bug 359913] Firefox extension XPI files have no icon

[andreas via KDE Bugzilla]

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

--- Comment #5 from andreas  ---
thanks for your help Piotr Kloc

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

[Breeze] [Bug 359913] Firefox extension XPI files have no icon

[andreas via KDE Bugzilla]

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

andreas  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/bree
   ||ze-icons/467556d006dc44b8d4
   ||c0374779132ca715df4149
 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #4 from andreas  ---
Git commit 467556d006dc44b8d4c0374779132ca715df4149 by andreas kainz.
Committed on 26/03/2016 at 21:36.
Pushed by andreask into branch 'master'.

add xpi support for firefox addons

A  +1-0icons-dark/mimetypes/16/application-x-xpinstall.svg
A  +1-0icons-dark/mimetypes/22/application-x-xpinstall.svg
A  +1-0icons-dark/mimetypes/32/application-x-xpinstall.svg
A  +1-0icons-dark/mimetypes/64/application-x-xpinstall.svg
A  +1-0icons/mimetypes/16/application-x-xpinstall.svg
A  +1-0icons/mimetypes/22/application-x-xpinstall.svg
A  +1-0icons/mimetypes/32/application-x-xpinstall.svg
A  +1-0icons/mimetypes/64/application-x-xpinstall.svg

http://commits.kde.org/breeze-icons/467556d006dc44b8d4c0374779132ca715df4149

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

[kwin] [Bug 358369] Plasma crashed after opening an HTML5 video in Chrome

[Thomas Lübking via KDE Bugzilla]

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

Thomas Lübking  changed:

   What|Removed |Added

 CC||pier_andr...@yahoo.it

--- Comment #16 from Thomas Lübking  ---
*** Bug 361023 has been marked as a duplicate of this bug. ***

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

[kwin] [Bug 361023] kwin crashes when I paste someting in kwrite

[Thomas Lübking via KDE Bugzilla]

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

Thomas Lübking  changed:

   What|Removed |Added

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

--- Comment #1 from Thomas Lübking  ---
Use the breeze decoration.

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

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

[plasma-nm] [Bug 346118] Plasmashell crash when disconnecting/reconnecting my WiFi connection after changing MTU

[via KDE Bugzilla]

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

hello.titties...@googlemail.com changed:

   What|Removed |Added

 CC|hello.titties123@googlemail |
   |.com|

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

[plasma-nm] [Bug 346118] Plasmashell crash when disconnecting/reconnecting my WiFi connection after changing MTU

[Jacek Pawlyta via KDE Bugzilla]

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

--- Comment #76 from Jacek Pawlyta  ---
I see the bug again too  qt 5.6.0, kf 5.20.0, plasma 5.5.5 Fedora23

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

[plasma-nm] [Bug 346118] Plasmashell crash when disconnecting/reconnecting my WiFi connection after changing MTU

[Jacek Pawlyta via KDE Bugzilla]

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

--- Comment #75 from Jacek Pawlyta  ---
I see the bug again too  qt 5.6.0, kf 5.20.0, plasma 5.5.5 Fedora23

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

[kmymoney4] [Bug 360938] Scheduled transactions entered in credit card (liability) have random descriptions populated

[Jack via KDE Bugzilla]

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

Jack  changed:

   What|Removed |Added

 CC||ostroffjh@users.sourceforge
   ||.net

--- Comment #7 from Jack  ---
Aside from doing more backups :-) the first thing I would do is to see if it
also crashes using a file instead of a database.  If it works with a file, but
crashes with the database, that helps focus where to look for the problem.  You
might also try testing with a newly created (and thus essentially empty) file
and database.  That would show whether the crash has anything to do with your
data or not.

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

[konqueror] [Bug 361024] New: Konqueror crashed when trying to open Google redirect link

[via KDE Bugzilla]

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

Bug ID: 361024
   Summary: Konqueror crashed when trying to open Google redirect
link
   Product: konqueror
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: konq-b...@kde.org
  Reporter: m...@nightrealms.com

Application: konqueror (4.14.17)
KDE Platform Version: 4.14.18
Qt Version: 4.8.7
Operating System: Linux 4.4.5-300.fc23.x86_64 x86_64
Distribution: "Fedora release 23 (Twenty Three)"

-- Information about the crash:
>From the command line I entered "konqueror
'https://www.google.com/url?sa=t=j==s=web=1=rja=8=0ahUKEwi5vYSund_LAhVW0mMKHdmrD4kQFggdMAA=http%3A%2F%2Ftvtropes.org%2Fpmwiki%2Fpmwiki.php%2FMain%2FHaveIMentionedIAmHeterosexualToday=AFQjCNH6KR-uIF0VA9sCR80hObp5cBGo6g=3yd8ivWLQDszUyoQFTfw3w'",
and it immediately crashed.

-- Backtrace:
Application: Konqueror (konqueror), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#6  0x7f4a25086370 in khtml::HTMLTokenizer::scriptHandler() () at
/lib64/libkhtml.so.5
#7  0x7f4a25087eb1 in
khtml::HTMLTokenizer::parseRawContent(khtml::TokenizerString&) () at
/lib64/libkhtml.so.5
#8  0x7f4a25089b55 in
khtml::HTMLTokenizer::parseTag(khtml::TokenizerString&) () at
/lib64/libkhtml.so.5
#9  0x7f4a2508a493 in khtml::HTMLTokenizer::write(khtml::TokenizerString
const&, bool) () at /lib64/libkhtml.so.5
#10 0x7f4a2502672c in DOM::DocumentImpl::write(QString const&) () at
/lib64/libkhtml.so.5
#11 0x7f4a252036c0 in KJS::HTMLDocFunction::callAsFunction(KJS::ExecState*,
KJS::JSObject*, KJS::List const&) () at /lib64/libkhtml.so.5
#12 0x7f4a248b2de7 in KJS::Machine::runBlock(KJS::ExecState*,
WTF::Vector const&, KJS::ExecState*) () at
/lib64/libkjs.so.4
#13 0x7f4a248948a0 in KJS::FunctionImp::callAsFunction(KJS::ExecState*,
KJS::JSObject*, KJS::List const&) () at /lib64/libkjs.so.4
#14 0x7f4a248b2de7 in KJS::Machine::runBlock(KJS::ExecState*,
WTF::Vector const&, KJS::ExecState*) () at
/lib64/libkjs.so.4
#15 0x7f4a248948a0 in KJS::FunctionImp::callAsFunction(KJS::ExecState*,
KJS::JSObject*, KJS::List const&) () at /lib64/libkjs.so.4
#16 0x7f4a248b2de7 in KJS::Machine::runBlock(KJS::ExecState*,
WTF::Vector const&, KJS::ExecState*) () at
/lib64/libkjs.so.4
#17 0x7f4a248948a0 in KJS::FunctionImp::callAsFunction(KJS::ExecState*,
KJS::JSObject*, KJS::List const&) () at /lib64/libkjs.so.4
#18 0x7f4a252308b1 in KJS::ScheduledAction::execute(KJS::Window*) () at
/lib64/libkhtml.so.5
#19 0x7f4a25230b2c in KJS::WindowQObject::timerEvent(QTimerEvent*) () at
/lib64/libkhtml.so.5
#20 0x7f4a40d8d6c3 in QObject::event(QEvent*) () at /lib64/libQtCore.so.4
#21 0x7f4a3fbfd93c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib64/libQtGui.so.4
#22 0x7f4a3fc04796 in QApplication::notify(QObject*, QEvent*) () at
/lib64/libQtGui.so.4
#23 0x7f4a41a8760a in KApplication::notify(QObject*, QEvent*) () at
/lib64/libkdeui.so.5
#24 0x7f4a40d738bd in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /lib64/libQtCore.so.4
#25 0x7f4a40da6330 in QTimerInfoList::activateTimers() () at
/lib64/libQtCore.so.4
#26 0x7f4a40da34a1 in timerSourceDispatch(_GSource*, int (*)(void*), void*)
() at /lib64/libQtCore.so.4
#27 0x7f4a39f4ae3a in g_main_context_dispatch () at /lib64/libglib-2.0.so.0
#28 0x7f4a39f4b1d0 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#29 0x7f4a39f4b27c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#30 0x7f4a40da3e5e in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQtCore.so.4
#31 0x7f4a3fca6436 in
QGuiEventDispatcherGlib::processEvents(QFlags)
() at /lib64/libQtGui.so.4
#32 0x7f4a40d72131 in
QEventLoop::processEvents(QFlags) () at
/lib64/libQtCore.so.4
#33 0x7f4a40d724a5 in
QEventLoop::exec(QFlags) () at
/lib64/libQtCore.so.4
#34 0x7f4a40d78039 in QCoreApplication::exec() () at /lib64/libQtCore.so.4
#35 0x7f4a435d48bf in kdemain () at /lib64/libkdeinit4_konqueror.so
#36 0x7f4a3de1b580 in __libc_start_main () at /lib64/libc.so.6
#37 0x5587f23239a9 in _start ()

The reporter indicates this bug may be a duplicate of or related to bug 360960.

Possible duplicates by query: bug 360960.

Reported using DrKonqi

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

[kwin] [Bug 361023] New: kwin crashes when I paste someting in kwrite

[pier andre via KDE Bugzilla]

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

Bug ID: 361023
   Summary: kwin crashes when I paste someting in kwrite
   Product: kwin
   Version: 5.6.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: pier_andr...@yahoo.it

Application: kwin_x11 (5.6.0)

Qt Version: 5.6.0
Frameworks Version: 5.20.0
Operating System: Linux 4.1.15-8-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
I was pasting text in a kwrite document and  plasma crashed
sorry I cannot give more informations than these

The crash can be reproduced sometimes.

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

Thread 7 (Thread 0x7ffa1b336700 (LWP 29731)):
#0  0x7ffa35da1bbd in poll () at /lib64/libc.so.6
#1  0x7ffa336d9422 in  () at /usr/lib64/libxcb.so.1
#2  0x7ffa336db00f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7ffa1c20c979 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7ffa3399d079 in  () at /usr/lib64/libQt5Core.so.5
#5  0x7ffa353c10a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7ffa35da9fed in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7ffa196c5700 (LWP 29732)):
#0  0x7ffa35da3253 in select () at /lib64/libc.so.6
#1  0x7ffa33baa8e9 in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timespec const*) () at /usr/lib64/libQt5Core.so.5
#2  0x7ffa33bac1b5 in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () at /usr/lib64/libQt5Core.so.5
#3  0x7ffa33bac5f7 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7ffa33b5c04b in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7ffa339985da in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7ffa2c9ed095 in  () at /usr/lib64/libQt5DBus.so.5
#7  0x7ffa3399d079 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7ffa353c10a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7ffa35da9fed in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7ffa12bcf700 (LWP 29749)):
#0  0x7ffa35da3253 in select () at /lib64/libc.so.6
#1  0x7ffa33baa8e9 in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timespec const*) () at /usr/lib64/libQt5Core.so.5
#2  0x7ffa33bac1b5 in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () at /usr/lib64/libQt5Core.so.5
#3  0x7ffa33bac5f7 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7ffa33b5c04b in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7ffa339985da in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7ffa2da664d8 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7ffa3399d079 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7ffa353c10a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7ffa35da9fed in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7ffa07ab3700 (LWP 29750)):
#0  0x7ffa35da3253 in select () at /lib64/libc.so.6
#1  0x7ffa33baa8e9 in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timespec const*) () at /usr/lib64/libQt5Core.so.5
#2  0x7ffa33bac1b5 in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () at /usr/lib64/libQt5Core.so.5
#3  0x7ffa33bac5f7 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7ffa33b5c04b in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7ffa339985da in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7ffa2da664d8 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7ffa3399d079 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7ffa353c10a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7ffa35da9fed in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7ffa04964700 (LWP 29753)):
#0  0x7ffa353c503f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7ffa3291697b in  () at /usr/lib64/libQt5Script.so.5
#2  0x7ffa329169a9 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7ffa353c10a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7ffa35da9fed in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7ffa0617f700 (LWP 30014)):
#0  0x7ffa353c503f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7ffa3399dceb in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7ffa2e13a7eb in  () at /usr/lib64/libQt5Quick.so.5
#3  0x7ffa2e13ac95 in  () at /usr/lib64/libQt5Quick.so.5
#4  0x7ffa3399d079 in  () at /usr/lib64/libQt5Core.so.5
#5  0x7ffa353c10a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7ffa35da9fed in clone () at /lib64/libc.so.6

[Akonadi] [Bug 334569] KOrganizer not syncing properly with modified repeated events in google calendar

[via KDE Bugzilla]

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

--- Comment #4 from kai.stra...@gmx.de ---
Confirmed

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

[kmymoney4] [Bug 360938] Scheduled transactions entered in credit card (liability) have random descriptions populated

[via KDE Bugzilla]

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

--- Comment #6 from lp.allar...@gmail.com ---
Well.. I added the PPA you suggested and upgraded KMM to 4.7.2.  First thing I
noticed, it crashes hard when I perform a consistency check.  I am storing my
data on a MySQL backend, with about 7800 transactions (been using KMM since
2008).

Can it corrupt my data (I do have backups but I dont want to jeopardize my data
either)?

What I could gather from the crash (happens every time, with all accounts).  I
have tried with another account which is almost empty and still it crashes.

Application: KMyMoney (kmymoney), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fb6d8a8f7c0 (LWP 26966))]

Thread 2 (Thread 0x7fb6b51bf700 (LWP 26970)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238
#1  0x7fb6d3cb67f4 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#2  0x7fb6d3caa0fa in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#3  0x7fb6d3cb632f in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#4  0x7fb6ce5a4182 in start_thread (arg=0x7fb6b51bf700) at
pthread_create.c:312
#5  0x7fb6d2c9047d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7fb6d8a8f7c0 (LWP 26966)):
[KCrash Handler]
#5  0x7fb6d3cf99eb in QString::operator==(QString const&) const () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#6  0x7fb6d841c243 in MyMoneyFile::consistencyCheck() () from
/usr/lib/libkmm_mymoney.so.4
#7  0x00465996 in _start ()

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

[Powerdevil] [Bug 361022] Laptop goes to sleep when closing lid even with an external display connected

[Kai Uwe Broulik via KDE Bugzilla]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

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

--- Comment #1 from Kai Uwe Broulik  ---
Does battery monitor show "your computer is configured not to suspend when
closing the lid because an external monitor is connected" ?

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

[kmymoney4] [Bug 360712] kmymoney (4.6.4): crash at the end of aqbanking importer of a diba datafile

[JS via KDE Bugzilla]

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

JS  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #5 from JS  ---
After several trials and the information from linuxwiki how to configure
aqbanking, the hbci connection works now very well !!  So i have to say many
thanks for the tip. From my side the problem is solved

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

[Powerdevil] [Bug 361022] New: Laptop goes to sleep when closing lid even with an external display connected

[Ovidiu D . Niţan via KDE Bugzilla]

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

Bug ID: 361022
   Summary: Laptop goes to sleep when closing lid even with an
external display connected
   Product: Powerdevil
   Version: 5.5.5
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-de...@kde.org
  Reporter: nitanovi...@gmail.com

If I connect an external display and I close the laptop's lid the system is
going to sleep even if the option "Even when an external monitor is connected"
is unchecked in the Power Management settings. I changed "When laptop lid is
closed" to "Do nothing" to check if KDE's power management is inhibiting
systemd's power management and it worked as expected.

My current display configuration is http://i.imgur.com/tsVgEU1.png

Reproducible: Always

Steps to Reproduce:
1. Set the system to not enter sleep mode in Power Management when an external
monitor is connected
2. Close the laptop's lid


Actual Results:  
The system is going to sleep

Expected Results:  
The system should not go to sleep

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

[kmymoney4] [Bug 361021] CSV importer: The transaction has missing assignment of...

[NSLW via KDE Bugzilla]

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

--- Comment #6 from NSLW  ---
(In reply to Jack from comment #5)
> Without looking at the details, I believe this is not a problem with the CSV
> importer, but with any KMM import of an investment transaction which
> requires a brokerage account for transfer of funds.  (I have it with OFX
> import.) The issue is that when KMM imports an investment transaction, it
> does not specify the brokerage account, so the missing assignment refers to
> the amount which would go to that account.  When you edit the transaction,
> KMM automatically enters the brokerage account, so the error disappears.

It makes no sense for me that sell operations are properly assigned and buy
operation not. Which error do you refer to Jack?

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

[kmymoney4] [Bug 361021] CSV importer: The transaction has missing assignment of...

[Jack via KDE Bugzilla]

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

--- Comment #5 from Jack  ---
Without looking at the details, I believe this is not a problem with the CSV
importer, but with any KMM import of an investment transaction which requires a
brokerage account for transfer of funds.  (I have it with OFX import.) The
issue is that when KMM imports an investment transaction, it does not specify
the brokerage account, so the missing assignment refers to the amount which
would go to that account.  When you edit the transaction, KMM automatically
enters the brokerage account, so the error disappears.

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

[kmymoney4] [Bug 361021] CSV importer: The transaction has missing assignment of...

[NSLW via KDE Bugzilla]

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

--- Comment #4 from NSLW  ---
Created attachment 98106
  --> https://bugs.kde.org/attachment.cgi?id=98106=edit
[PATCH] Add fee for buy and sell operation in the right way

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

[kmymoney4] [Bug 361021] CSV importer: The transaction has missing assignment of...

[NSLW via KDE Bugzilla]

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

--- Comment #3 from NSLW  ---
Created attachment 98105
  --> https://bugs.kde.org/attachment.cgi?id=98105=edit
Problem description

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

[kmymoney4] [Bug 361021] CSV importer: The transaction has missing assignment of...

[NSLW via KDE Bugzilla]

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

--- Comment #2 from NSLW  ---
Created attachment 98104
  --> https://bugs.kde.org/attachment.cgi?id=98104=edit
Column Assignment for CSV file

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

[kmymoney4] [Bug 361021] CSV importer: The transaction has missing assignment of...

[NSLW via KDE Bugzilla]

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

--- Comment #1 from NSLW  ---
Created attachment 98103
  --> https://bugs.kde.org/attachment.cgi?id=98103=edit
CSV Test File

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

[kmymoney4] [Bug 361021] New: CSV importer: The transaction has missing assignment of...

[NSLW via KDE Bugzilla]

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

Bug ID: 361021
   Summary: CSV importer: The transaction has missing assignment
of...
   Product: kmymoney4
   Version: git master
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: csvimporter
  Assignee: kmymoney-de...@kde.org
  Reporter: lukasz.wojnilow...@gmail.com

Buy transactions imported by CSV importer always have missing assignment (see
attachment).

Reproducible: Always

Steps to Reproduce:
1. file->import csv
2. choose investment
3. create new profile
4. open "test file.csv" and assign columns to values (see attachment)
5. FieldDelimiter to comma
6. TextDelimiter to double quotes
7. DecimalSymbol to comma
8. ImportCSV

Actual Results:  
In ledger:
All buy operations have missing assignment
On home page:
Balance for banking and investment account are equal.

Expected Results:  
In ledger:
All operations should have assignment
On home page:
Balance for banking and investment account should be equal only in special
cases. Correct difference in balance is shown in attachment.

To get good balance without the need of patching one has to double click every
operation in ledger and press enter button. Upon completion column value will
have exact same values as column from patched KMM.

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

[plasma4] [Bug 324164] Folderview icon has the wrong image when put in a panel.

[via KDE Bugzilla]

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

ltwilliam...@gmail.com changed:

   What|Removed |Added

 CC|ltwilliam...@gmail.com  |

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

[krita] [Bug 359931] performance decrease compared to stable release

[via KDE Bugzilla]

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

--- Comment #7 from kde...@tuta.io ---
(In reply to wolthera from comment #6)
> are you using the hsy selector? because then that's expected(the hsy
> selector is now linearised giving it true luminance).

It doesn't matter which color model type or color space I use.
The only thing which seems to make a difference is restarting with opengl
disabled, which isn't worth it for such a minor issue.
It affects the Advanced Color Selector, Small Color Selector and Artistic Color
Selector.
Only encountered the problem on 3.0.

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

[krunner] [Bug 361020] New: Krunner crash upon entering command.

[Ken Aaker via KDE Bugzilla]

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

Bug ID: 361020
   Summary: Krunner crash upon entering command.
   Product: krunner
   Version: 5.5.5
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: m...@vhanda.in
  Reporter: kenaa...@gmail.com

Application: krunner (5.5.5)

Qt Version: 5.5.1
Operating System: Linux 4.3.3-4-default x86_64
Distribution: "openSUSE Tumbleweed (20160117) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:Freshly logged in, hit Alt-F2,
entered openscad, pressed enter. Crashed, never launching openscad.  Sometimes
it crashes part way through typing any command name.

The crash can be reproduced sometimes.

-- Backtrace:
Application: krunner (krunner), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
QMutexLocker::unlock (this=) at
../../src/corelib/thread/qmutex.h:138
[Current thread is 1 (Thread 0x7ffb5327a8c0 (LWP 3081))]

Thread 20 (Thread 0x7ffb3cf85700 (LWP 3090)):
#0  0x7ffb4ef3f43d in poll () at /lib64/libc.so.6
#1  0x7ffb4e439432 in  () at /usr/lib64/libxcb.so.1
#2  0x7ffb4e43b007 in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7ffb3f740dd9 in QXcbEventReader::run() (this=0x18e0800) at
qxcbconnection.cpp:1229
#4  0x7ffb4f63790f in QThreadPrivate::start(void*) (arg=0x18e0800) at
thread/qthread_unix.cpp:331
#5  0x7ffb4cfbd454 in start_thread () at /lib64/libpthread.so.0
#6  0x7ffb4ef47d8d in clone () at /lib64/libc.so.6

Thread 19 (Thread 0x7ffb30bbd700 (LWP 3097)):
#0  0x7ffb4ef3f43d in poll () at /lib64/libc.so.6
#1  0x7ffb4c40a294 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7ffb4c40a39c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7ffb4f85c4db in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7ffb2c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7ffb4f8065ca in
QEventLoop::exec(QFlags)
(this=this@entry=0x7ffb30bbccf0, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#5  0x7ffb4f632adc in QThread::exec() (this=) at
thread/qthread.cpp:503
#6  0x7ffb51f1b7b5 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7ffb4f63790f in QThreadPrivate::start(void*) (arg=0x1b1bf80) at
thread/qthread_unix.cpp:331
#8  0x7ffb4cfbd454 in start_thread () at /lib64/libpthread.so.0
#9  0x7ffb4ef47d8d in clone () at /lib64/libc.so.6

Thread 18 (Thread 0x7ffb2673d700 (LWP 13727)):
#0  0x7ffb4cfc302f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7ffb4f638a7b in QWaitCondition::wait(QMutex*, unsigned long)
(time=18446744073709551615, this=0x22955e0) at
thread/qwaitcondition_unix.cpp:136
#2  0x7ffb4f638a7b in QWaitCondition::wait(QMutex*, unsigned long)
(this=, mutex=0x2295580, time=18446744073709551615) at
thread/qwaitcondition_unix.cpp:208
#3  0x7ffb523db1de in  () at /usr/lib64/libQt5Quick.so.5
#4  0x7ffb523dba23 in  () at /usr/lib64/libQt5Quick.so.5
#5  0x7ffb4f63790f in QThreadPrivate::start(void*) (arg=0x2295500) at
thread/qthread_unix.cpp:331
#6  0x7ffb4cfbd454 in start_thread () at /lib64/libpthread.so.0
#7  0x7ffb4ef47d8d in clone () at /lib64/libc.so.6

Thread 17 (Thread 0x7ffb1aead700 (LWP 13728)):
#0  0x7ffb4cfc302f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7ffb4f638a7b in QWaitCondition::wait(QMutex*, unsigned long)
(time=18446744073709551615, this=0x234b240) at
thread/qwaitcondition_unix.cpp:136
#2  0x7ffb4f638a7b in QWaitCondition::wait(QMutex*, unsigned long)
(this=, mutex=0x1d188f0, time=18446744073709551615) at
thread/qwaitcondition_unix.cpp:208
#3  0x7ffb28fd9de7 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5
#4  0x7ffb28fddd48 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7ffb28fd9009 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#6  0x7ffb28fddd92 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#7  0x7ffb28fd9009 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#8  0x7ffb28fdbdd3 in ThreadWeaver::Thread::run() () at
/usr/lib64/libKF5ThreadWeaver.so.5
#9  0x7ffb4f63790f in QThreadPrivate::start(void*) (arg=0x2302f10) at
thread/qthread_unix.cpp:331
#10 0x7ffb4cfbd454 in start_thread () at /lib64/libpthread.so.0
#11 0x7ffb4ef47d8d in clone () at /lib64/libc.so.6

Thread 16 (Thread 0x7ffb126ac700 (LWP 13729)):
#0  0x7ffb4cfc302f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7ffb4f638a7b in QWaitCondition::wait(QMutex*, unsigned long)
(time=18446744073709551615, this=0x234b240) at

[amarok] [Bug 329166] Amarok volume is often reset to 100% when changing tracks

[noric via KDE Bugzilla]

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

--- Comment #12 from noric  ---
One minor annoiance of GStreamer backend. It looks like with it Amarok can't
play short tracks (few seconds) of a playlist. If you play a single short track
alone, it works. If you play a playlist, Amarok will skip every short track.

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

[Breeze] [Bug 359913] Firefox extension XPI files have no icon

[Piotr Kloc via KDE Bugzilla]

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

Piotr Kloc  changed:

   What|Removed |Added

 CC||pepk...@gmail.com

--- Comment #3 from Piotr Kloc  ---
If Breeze gets .xpi icon then we will be one of the few that has it.
I've tried few icon sets (Breeze, Adwaita, GNOME, Oxygen) and only Numix has
it.

Below is output from pacman -Ql numix-icon-theme | grep xpi

numix-icon-theme
/usr/share/icons/Numix/16/mimetypes/application-x-xpinstall.svg
numix-icon-theme
/usr/share/icons/Numix/16/mimetypes/gnome-mime-image-x-xpixmap.svg
numix-icon-theme /usr/share/icons/Numix/16/mimetypes/image-x-xpixmap.svg
numix-icon-theme /usr/share/icons/Numix/16/status/krb-expiring-ticket.svg
numix-icon-theme
/usr/share/icons/Numix/22/mimetypes/application-x-xpinstall.svg
numix-icon-theme
/usr/share/icons/Numix/22/mimetypes/gnome-mime-image-x-xpixmap.svg
numix-icon-theme /usr/share/icons/Numix/22/mimetypes/image-x-xpixmap.svg
numix-icon-theme /usr/share/icons/Numix/22/status/krb-expiring-ticket.svg
numix-icon-theme
/usr/share/icons/Numix/24/mimetypes/application-x-xpinstall.svg
numix-icon-theme
/usr/share/icons/Numix/24/mimetypes/gnome-mime-image-x-xpixmap.svg
numix-icon-theme /usr/share/icons/Numix/24/mimetypes/image-x-xpixmap.svg
numix-icon-theme /usr/share/icons/Numix/24/status/krb-expiring-ticket.svg
numix-icon-theme
/usr/share/icons/Numix/32/mimetypes/application-x-xpinstall.svg
numix-icon-theme
/usr/share/icons/Numix/32/mimetypes/gnome-mime-image-x-xpixmap.svg
numix-icon-theme /usr/share/icons/Numix/32/mimetypes/image-x-xpixmap.svg
numix-icon-theme
/usr/share/icons/Numix/48/mimetypes/application-x-xpinstall.svg
numix-icon-theme
/usr/share/icons/Numix/48/mimetypes/gnome-mime-image-x-xpixmap.svg
numix-icon-theme /usr/share/icons/Numix/48/mimetypes/image-x-xpixmap.svg
numix-icon-theme
/usr/share/icons/Numix/64/mimetypes/application-x-xpinstall.svg
numix-icon-theme
/usr/share/icons/Numix/64/mimetypes/gnome-mime-image-x-xpixmap.svg
numix-icon-theme /usr/share/icons/Numix/64/mimetypes/image-x-xpixmap.svg

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

[kmymoney4] [Bug 361004] CSV Importer doesn't read DecimalSymbol stored in csvimporterrc

[allan via KDE Bugzilla]

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

allan  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #5 from allan  ---
Well spotted!  Now, why did I do that?

I'll come back to this later.

Allan

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

[kmymoney4] [Bug 360938] Scheduled transactions entered in credit card (liability) have random descriptions populated

[allan via KDE Bugzilla]

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

--- Comment #5 from allan  ---
On 26/03/16 15:55, via KDE Bugzilla wrote:
> https://bugs.kde.org/show_bug.cgi?id=360938
>
> --- Comment #4 from lp.allar...@gmail.com ---
> I am not off to a good start.  First I downloaded the sources of 4.7.2 then
> followed the instructions of the README.cmake file which mentions that I 
> should
> run "sudo apt-get build-dep kmymoney" since I am on ubuntu (mint)..  The 
> output
> was
>
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> E: Unable to find a source package for kmymoney
>
> Then I tried to manually start the cmake compilation process and got :
>
> CMake Error at CMakeLists.txt:72 (find_package):
>By not providing "FindQGpgme.cmake" in CMAKE_MODULE_PATH this project has
>asked CMake to find a package configuration file provided by "QGpgme", but
>CMake did not find one.
>
>Could not find a package configuration file provided by "QGpgme" with any
>of the following names:
>
>  QGpgmeConfig.cmake
>  qgpgme-config.cmake
>
>Add the installation prefix of "QGpgme" to CMAKE_PREFIX_PATH or set
>"QGpgme_DIR" to a directory containing one of the above files.  If "QGpgme"
>provides a separate development package or SDK, be sure it has been
>installed.
> -- Configuring incomplete, errors occurred!
>
> I am not sure how to proceed since I am not using KDE as my DE and I am not
> developing apps for KDE..
>

KMyMoney is a KDE application, and to compile from source you would need 
to have a number of dependencies, "QGpgme" included.

However, if you are not familiar with KDE application development, it 
might be better for you to locate the Claydoh PPA, and you should find a 
recent KMyMoney release there.

Allan

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

[bugs.kde.org] [Bug 359603] Incorrect and useless From header in emails generated by KDE Bugzilla

[Pali Rohár via KDE Bugzilla]

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

--- Comment #34 from Pali Rohár  ---
On Saturday 26 March 2016 19:13:24 Nicolás Alvarez via KDE Bugzilla 
wrote:
> https://bugs.kde.org/show_bug.cgi?id=359603
> 
> --- Comment #33 from Nicolás Alvarez  ---
> (In reply to Pali Rohár from comment #32)
> 
> > 2) If such anti-spam protection drops more than 30% of non-spam
> > emails then it is not only useless but must be avoided because it
> > drop regular non-spam messages. Same as sending all emails to
> > /dev/null. It is absolute anti-spam protection but totally
> > useless.
> 
> Yup, I agree.
> 
> But it's not our fault. Go complain to Yahoo and to the inventors of
> DMARC. We can't fix it, we can only apply workarounds to ensure our
> mail reaches our users.

Ok, here is my proposed solution for this problem:

Detect if provider of email receiver enforce DMARC and if not, do not 
mangle from/sender headers. Ideally add option to bugzilla account 
configuration to enable/disable mangling from/sender headers.

This could fix problem when yahoo (and others) drop emails from kde 
bugzilla and also allow other non-yahoo (and non-etc...) users to 
receive normal emails as before.

Nicolás, what do you think about it?

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

[kmymoney4] [Bug 360435] CSV Importer doesn't recognize security if its symbol isn't lower case

[allan via KDE Bugzilla]

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

--- Comment #9 from allan  ---
(In reply to NSLW from comment #8)
> (In reply to allan from comment #7)
> > I did fix this a while ago, following
> > https://bugs.kde.org/show_bug.cgi?id=352789, but somehow things got
> > side-tracked, and it was not committed.
> > 
> > The proposed patch looks, good, but I would make one change, in
> > "
> > securityName = m_wizDlg->m_csvDialog->ui->tableWidget->item(row,
> > detail)->text().toUpper().trimmed();"
> > 
> > I would propose removing the '.toUpper()', allowing the user's
> > value/preference to be maintained.
> 
> That seems reasonable. Do you need me to send you another patch?

No, thanks.  I think we have enough.

Allan

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

[krita] [Bug 359931] performance decrease compared to stable release

[wolthera via KDE Bugzilla]

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

--- Comment #6 from wolthera  ---
are you using the hsy selector? because then that's expected(the hsy selector
is now linearised giving it true luminance).

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

[plasmashell] [Bug 361019] New: Plasma Crashes at Random Times

[Robert M via KDE Bugzilla]

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

Bug ID: 361019
   Summary: Plasma Crashes at Random Times
   Product: plasmashell
   Version: 5.5.5
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: calend...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.5)

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

-- Information about the crash:
- What I was doing when the application crashed:
Watching a Youtube video. Plasma seems to crash at random times, and I can't
duplictae it.

The crash does not seem to be reproducible.

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

Thread 14 (Thread 0x7f8e5bfed700 (LWP 1843)):
#0  0x7f8e6a6f2bbd in poll () at /lib64/libc.so.6
#1  0x7f8e6f691422 in  () at /usr/lib64/libxcb.so.1
#2  0x7f8e6f69300f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7f8e5e7a63c9 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f8e6adf132f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f8e69eee0a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7f8e6a6fafed in clone () at /lib64/libc.so.6

Thread 13 (Thread 0x7f8e58f35700 (LWP 1912)):
#0  0x7f8e6a6eec8d in read () at /lib64/libc.so.6
#1  0x7f8e66daab60 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f8e66d6 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f8e66d69df8 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7f8e66d69f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7f8e6b023d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#6  0x7f8e6afcad53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#7  0x7f8e6adec61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8  0x7f8e6e136df8 in  () at /usr/lib64/libQt5Qml.so.5
#9  0x7f8e6adf132f in  () at /usr/lib64/libQt5Core.so.5
#10 0x7f8e69eee0a4 in start_thread () at /lib64/libpthread.so.0
#11 0x7f8e6a6fafed in clone () at /lib64/libc.so.6

Thread 12 (Thread 0x7f8e45005700 (LWP 1973)):
#0  0x7f8e66dabcf9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0
#1  0x7f8e66d69387 in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f8e66d69d80 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f8e66d69f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f8e6b023d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7f8e6afcad53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7f8e6adec61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7f8e6e136df8 in  () at /usr/lib64/libQt5Qml.so.5
#8  0x7f8e6adf132f in  () at /usr/lib64/libQt5Core.so.5
#9  0x7f8e69eee0a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7f8e6a6fafed in clone () at /lib64/libc.so.6

Thread 11 (Thread 0x7f8e3f7b5700 (LWP 1979)):
#0  0x7f8e6a6f2bbd in poll () at /lib64/libc.so.6
#1  0x7f8e66d69e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f8e66d69f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f8e6b023d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f8e6afcad53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f8e6adec61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f8e6e136df8 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7f8e6adf132f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f8e69eee0a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7f8e6a6fafed in clone () at /lib64/libc.so.6

Thread 10 (Thread 0x7f8e3de35700 (LWP 1991)):
#0  0x7f8e69ef203f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f8e7092986b in  () at /usr/lib64/libQt5Script.so.5
#2  0x7f8e70929899 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7f8e69eee0a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f8e6a6fafed in clone () at /lib64/libc.so.6

Thread 9 (Thread 0x7f8db6845700 (LWP 2002)):
#0  0x7f8e6a6eec8d in read () at /lib64/libc.so.6
#1  0x7f8e66daab60 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f8e66d6 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f8e66d69df8 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7f8e66d69f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7f8e6b023d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#6  0x7f8e6afcad53 in
QEventLoop::exec(QFlags) () at

[bugs.kde.org] [Bug 359603] Incorrect and useless From header in emails generated by KDE Bugzilla

[Nicolás Alvarez via KDE Bugzilla]

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

--- Comment #33 from Nicolás Alvarez  ---
(In reply to Pali Rohár from comment #32)
> 2) If such anti-spam protection drops more than 30% of non-spam emails
> then it is not only useless but must be avoided because it drop regular
> non-spam messages. Same as sending all emails to /dev/null. It is
> absolute anti-spam protection but totally useless.

Yup, I agree.

But it's not our fault. Go complain to Yahoo and to the inventors of DMARC. We
can't fix it, we can only apply workarounds to ensure our mail reaches our
users.

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

[digikam] [Bug 354364] Crash of DNG converter

[Thomas Käfer via KDE Bugzilla]

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

--- Comment #18 from Thomas Käfer  ---
haha okey so that was a catastrophic experience ;) while digikam 4.12 managed
to corrupt a single picture of my album while crashing, digikam 4.14 managed to
corrupt around 20 of the total ~50 pictures in the album (selected all of them
before using the adjust date/timestamp kipi plugin) But don't worry for me I
have backups ;)

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

[kwin] [Bug 361018] New: kwin crashes

[Vincent-Xavier JUMEL via KDE Bugzilla]

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

Bug ID: 361018
   Summary: kwin crashes
   Product: kwin
   Version: 5.6.0
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: endymion+...@thetys-retz.net

Application: kwin_x11 (5.6.0)
 (Compiled from sources)
Qt Version: 5.5.1
Frameworks Version: 5.20.0
Operating System: Linux 4.5.0-gentoo x86_64
Distribution: "Gentoo Base System release 2.2"

-- Information about the crash:
- Most of the time, launching mpv 0.16.0 makes kwin to crash.
mpv is compiled from source, and I'm using EGL backend.

The crash can be reproduced sometimes.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
pthread_cond_wait () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
[Current thread is 1 (Thread 0x7fda60863840 (LWP 1420))]

Thread 8 (Thread 0x7fda5fd0a700 (LWP 1429)):
#0  0x7fda76bf4c8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fda75007b12 in poll (__timeout=-1, __nfds=1, __fds=0x7fda5fd09c80)
at /usr/include/bits/poll2.h:46
#2  _xcb_conn_wait (c=c@entry=0x638910, cond=cond@entry=0x638950,
vector=vector@entry=0x0, count=count@entry=0x0) at
/var/tmp/portage/x11-libs/libxcb-1.11.1/work/libxcb-1.11.1/src/xcb_conn.c:459
#3  0x7fda750098d7 in xcb_wait_for_event (c=0x638910) at
/var/tmp/portage/x11-libs/libxcb-1.11.1/work/libxcb-1.11.1/src/xcb_in.c:693
#4  0x7fda605b4ce9 in QXcbEventReader::run (this=0x64b8f0) at
qxcbconnection.cpp:1229
#5  0x7fda752c1812 in QThreadPrivate::start (arg=0x64b8f0) at
thread/qthread_unix.cpp:331
#6  0x7fda76eba5c6 in start_thread (arg=0x7fda5fd0a700) at
pthread_create.c:334
#7  0x7fda76bfe0cd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 7 (Thread 0x7fda54c86700 (LWP 1430)):
#0  pthread_cond_wait () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fda5e948a8b in cnd_wait (mtx=0x68d990, cond=0x68d9b8) at
/var/tmp/portage/media-libs/mesa-11.1.2-r1/work/mesa-11.1.2/include/c11/threads_posix.h:159
#2  pipe_semaphore_wait (sema=0x68d990) at
/var/tmp/portage/media-libs/mesa-11.1.2-r1/work/mesa-11.1.2/src/gallium/auxiliary/os/os_thread.h:259
#3  radeon_drm_cs_emit_ioctl (param=param@entry=0x68d640) at
/var/tmp/portage/media-libs/mesa-11.1.2-r1/work/mesa-11.1.2/src/gallium/winsys/radeon/drm/radeon_drm_winsys.c:653
#4  0x7fda5e9481b7 in impl_thrd_routine (p=) at
/var/tmp/portage/media-libs/mesa-11.1.2-r1/work/mesa-11.1.2/include/c11/threads_posix.h:87
#5  0x7fda76eba5c6 in start_thread (arg=0x7fda54c86700) at
pthread_create.c:334
#6  0x7fda76bfe0cd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7fda51f03700 (LWP 1449)):
#0  0x7fda76bf6bc3 in select () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fda754b49af in qt_safe_select (nfds=18,
fdread=fdread@entry=0x7fda44000a78, fdwrite=fdwrite@entry=0x7fda44000d08,
fdexcept=fdexcept@entry=0x7fda44000f98, orig_timeout=orig_timeout@entry=0x0) at
kernel/qcore_unix.cpp:75
#2  0x7fda754b5f93 in QEventDispatcherUNIX::select (timeout=0x0,
exceptfds=0x7fda44000f98, writefds=0x7fda44000d08, readfds=0x7fda44000a78,
nfds=, this=0x7fda440008c0) at
kernel/qeventdispatcher_unix.cpp:320
#3  QEventDispatcherUNIXPrivate::doSelect (this=this@entry=0x7fda440008e0,
flags=..., flags@entry=..., timeout=timeout@entry=0x0) at
kernel/qeventdispatcher_unix.cpp:196
#4  0x7fda754b64be in QEventDispatcherUNIX::processEvents
(this=0x7fda440008c0, flags=...) at kernel/qeventdispatcher_unix.cpp:607
#5  0x7fda75468fea in QEventLoop::exec (this=this@entry=0x7fda51f02d60,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7fda752bd076 in QThread::exec (this=this@entry=0x8f25b0) at
thread/qthread.cpp:503
#7  0x7fda6f92d645 in QQmlThreadPrivate::run (this=0x8f25b0) at
qml/ftw/qqmlthread.cpp:141
#8  0x7fda752c1812 in QThreadPrivate::start (arg=0x8f25b0) at
thread/qthread_unix.cpp:331
#9  0x7fda76eba5c6 in start_thread (arg=0x7fda51f03700) at
pthread_create.c:334
#10 0x7fda76bfe0cd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7fda4affd700 (LWP 1469)):
#0  pthread_cond_wait () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fda74437e64 in QTWTF::TCMalloc_PageHeap::scavengerThread
(this=0x7fda74523a20 ) at
../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359
#2  0x7fda74437ea9 in QTWTF::TCMalloc_PageHeap::runScavengerThread
(context=) at
../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464
#3  0x7fda76eba5c6 in start_thread (arg=0x7fda4affd700) at
pthread_create.c:334
#4  0x7fda76bfe0cd in clone () at

[kontact] [Bug 358967] Crash going into my inbox

[Darin McBride via KDE Bugzilla]

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

--- Comment #1 from Darin McBride  ---
Created attachment 98101
  --> https://bugs.kde.org/attachment.cgi?id=98101=edit
New crash information added by DrKonqi

kontact (4.14.10) on KDE Platform 4.14.18 using Qt 4.8.6

- What I was doing when the application crashed:

I was scrolling up to my latest inbox in gmail (IMAP).  Not sure what that
message is that is causing problems, if I go to the web gmail, the latest
message has "

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

[kontact] [Bug 358967] Crash going into my inbox

[Darin McBride via KDE Bugzilla]

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

Darin McBride  changed:

   What|Removed |Added

 CC||tankta...@gmail.com

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

[kmymoney4] [Bug 360435] CSV Importer doesn't recognize security if its symbol isn't lower case

[NSLW via KDE Bugzilla]

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

--- Comment #8 from NSLW  ---
(In reply to allan from comment #7)
> I did fix this a while ago, following
> https://bugs.kde.org/show_bug.cgi?id=352789, but somehow things got
> side-tracked, and it was not committed.
> 
> The proposed patch looks, good, but I would make one change, in
> "
> securityName = m_wizDlg->m_csvDialog->ui->tableWidget->item(row,
> detail)->text().toUpper().trimmed();"
> 
> I would propose removing the '.toUpper()', allowing the user's
> value/preference to be maintained.

That seems reasonable. Do you need me to send you another patch?

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

[plasmashell] [Bug 356609] Add options to prefer window icon over application icon

[Jordan Anderson via KDE Bugzilla]

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

--- Comment #3 from Jordan Anderson  ---
(In reply to kde from comment #2)
> Created attachment 98068 [details]
> Patch to revert to the desired behavior
> 
> For anyone willing to build from source, this patch applies against
> plasma-workspace (5.6.0, may work with others) to revert to the desired
> behavior of not using launcher icons.  There is no configurability: this
> unconditionally uses the window's icon, which is the correct behavior as far
> as I'm concerned.

Thanks! Patched and working as intended on Archlinux (with testing repos
enabled as 5.6.0 is still there).

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

[kaffeine] [Bug 361017] New: DVB-T video freeze after startup if desentrelace is activated

[via KDE Bugzilla]

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

Bug ID: 361017
   Summary: DVB-T video freeze after startup if desentrelace is
activated
   Product: kaffeine
   Version: 1.2.2 1.2.2
  Platform: Debian stable
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: christophpfis...@gmail.com
  Reporter: jeanlo...@delatte.org

The bug appear when read->video->desentrelace is activated and playing
correctly DVB-T.
After closing application, on the first restart the bug appear; kaffeine crash
or freeze the video but i hear the sound on this case.
At second restart, every things run normaly.
If i desactivate desentrelacing, this bug do not appear and kaffein restart and
play DVD-T pretty well.



Reproducible: Always

Steps to Reproduce:
1. start kaffeine
2. activate desentrelacing, play DVB-T channel
3. close kaffeine
4. restrart kaffeine

Actual Results:  
Crash or freeze video


i don't find any trace...
Coud be interesting to have a flag to activate log in ~/kaffeine.log

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

[digikam] [Bug 354364] Crash of DNG converter

[Thomas Käfer via KDE Bugzilla]

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

--- Comment #17 from Thomas Käfer  ---
okey, thanks for the info! would getting digikam 4.14 to run on my system help?
as in does it already contain the fix for this bug?

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

[ksnapshot] [Bug 361016] New: Quicken support number 1877-200-2151 Quicken pro tech support phone number

[suraj shrestha via KDE Bugzilla]

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

Bug ID: 361016
   Summary: Quicken support number 1877-200-2151 Quicken pro tech
support phone number
   Product: ksnapshot
   Version: unspecified
  Platform: Other
   URL: http://yahoo.com
OS: other
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: ase...@kde.org
  Reporter: apollo.vampi...@yahoo.com

Quicken support number 1877-200-2151 Quicken pro tech support phone number
Quicken support number ..))1877-200-2151((~~ Quicken pro tech support phone
number Witty ! 1-877-200-2151~Quicken pro tech support phone number,
Quicken pro customer support phone number,Witty@@!! 1-877-200-2151~Quicken pro
tech support phone number, Quicken pro customer support phone number, TECH
1-877-200-2151Quicken phone number, Quicken pro tech support phone number,
Quicken customer service number, usa, canada QB.s)) +1-877-200-2151(( Quicken
pro technical support phone number Quicken helpline number USA,Quicken help
phone number USA Quicken helpdesk number, Quicken support help number, Quicken
support help number ~Help Usa@ +1-877-200-2151…((( Quicken pro support phone
number… ~Help Usa@ +1-877-200-2151…((( Quicken payroll support phone number…
~Help Usa@ +1-877-200-2151…((( Quicken support phone number… ~Help Usa@
+1-877-200-2151…((( Quicken support number… ~Help Usa@ +1-877-200-2151…(((
Quicken help desk phone number… ~Help Usa@ +1-877-200-2151…((( Quicken pro help
desk phone number… ~Help Usa@ +1-877-200-2151…((( Quicken payroll help desk
phone number… Contents [hide] 1 ::~Help Usa@ +1-877-200-2151…((( Quicken tech
support phone number… 2 ::~Help Usa@ +1-877-200-2151…((( Quicken tech support
number… 3 ::~Help Usa@ +1-877-200-2151…((( Quicken customer support number… 4
Intuit Help… 1-877-200-2151Quicken tech support phone number , Quicken
technical support phone number 5 Intuit Help… 1-877-200-2151Quicken pro tech
support phone number , Quicken pro technical support phone number 6 Intuit
Help… 1-877-200-2151Quicken payroll tech support phone number , Quicken payroll
technical support phone number ~Help Usa@ +1-877-200-2151…((( Quicken tech
support phone number…[edit] ~Help Usa@ +1-877-200-2151…((( Quicken tech support
number…[edit] == ~Help Usa@ +1-877-200-2151…((( Quicken pro tech support phone
number..==. ~Help Usa@ +1-877-200-2151…((( Quicken payroll tech support phone
number…[edit] ~Help Usa@ +1-877-200-2151…((( Quicken pro tech support
number…[edit] 1-877-200-2151Quicken phone number, Quicken pro tech support
phone number, Quicken customer service number, usa, canada Quicken Customer
Support Number, Quicken Service Help Number, Quicken Error Support Number,
Quicken Customer Service Number, Quicken customer service phone number, Quicken
tech support number USA/CANADA, Quicken help phone number, Quicken online
support phone number USA/CANADA, Quicken support phone number, Quicken Customer
care number, Quicken Customer Care Phone Number, Quicken Support Contact Phone
Number 1877-200-2151 Quicken Customer Technical Support Number 1877-200-2151
Quicken Customer Technical Support Number 1877-200-2151 Quicken Customer
Technical Support Number 1877-200-2151 Quicken Customer Technical Support
Number 1877-200-2151 Quicken Customer Technical Support Number 1877-200-2151
Quicken Customer Technical Support Number 1877-200-2151 Quicken Customer
Technical Support Number 1877-200-2151 Quicken Customer Technical Support
Number Help @ 1877-200-2151 Quicken help desk number here. HELPLINE Quicken
Tech support number +1-877-200-2151,Quicken tech support phone number, Quicken
technical support phone number USA/CANADA, +1-877-200-2151 Quicken help desk
number Support HELPLINE Quicken Tech support number USA/CANADA ,Quicken help
desk phone number, ==+1-877-200-2151== Quicken Customer care phone number
CANADA +1-877-200-2151Quicken tech support number Quicken help desk phone
number Quicken tech support number +1-877-200-2151. Quicken Tech Support Number
Quicken Tech Support Number @(+1-877-200-2151)Quicken Tech Support Phone Number
videos online solution for all USA/CANADA clients. For any help of query call
1-877-200-2151to get all Quicken account solution. @@Call, 1-877-200-2151for
all type help by Quicken tech support phone number, Quicken Tech Support Phone
Number, Quicken Help Desk Phone Number, ==+1-877-200-2151== Quicken tech
support number, Quicken technical support phone number, 1877-200-2151 @@@
Quicken phone number USA/CANADA, Quicken technical support number, Quicken
support phone number, Quicken technical support, Quicken Customer Service Phone
Number, +1-877-200-2151 Quicken Customer Service Number, Quicken Customer
Support Phone Number, Quicken Customer Support Number, Quicken Customer
Service Helpline Number, Quicken Customer Care Number, Quicken support team
phone number, +1-877-200-2151 Quicken 

[plasmashell] [Bug 361015] New: Plasma has crashed message after resume from standby

[Ludo via KDE Bugzilla]

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

Bug ID: 361015
   Summary: Plasma has crashed message after resume from standby
   Product: plasmashell
   Version: 5.5.5
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: ludo.aelbrecht+...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.5)

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

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

I had put the laptop in standby mode. After resuming, Plasma had crashed. The
brightness level of my screen was also all the way down (could almost not see
the laptop was turned on again).

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

Thread 23 (Thread 0x7f66f3fff700 (LWP 3798)):
#0  0x7f6712ef2fdd in poll () at /lib64/libc.so.6
#1  0x7f670e41616c in g_main_context_iterate (priority=2147483647, n_fds=1,
fds=0x7f66ec003070, timeout=, context=0x7f66ec000990) at
gmain.c:4135
#2  0x7f670e41616c in g_main_context_iterate
(context=context@entry=0x7f66ec000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3835
#3  0x7f670e41627c in g_main_context_iteration (context=0x7f66ec000990,
may_block=may_block@entry=1) at gmain.c:3901
#4  0x7f6713d32ecb in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f66ec0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7f6713cd9eca in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f66f3ffec60, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#6  0x7f6713af6434 in QThread::exec() (this=) at
thread/qthread.cpp:503
#7  0x7f6717e449b5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5
#8  0x7f6713afb3de in QThreadPrivate::start(void*) (arg=0x55d50ce689e0) at
thread/qthread_unix.cpp:331
#9  0x7f671223660a in start_thread (arg=0x7f66f3fff700) at
pthread_create.c:334
#10 0x7f6712efea4d in clone () at /lib64/libc.so.6

Thread 22 (Thread 0x7f66eafe6700 (LWP 3820)):
#0  0x7f6712ef2fdd in poll () at /lib64/libc.so.6
#1  0x7f670e41616c in g_main_context_iterate (priority=2147483647, n_fds=1,
fds=0x7f66e4002e70, timeout=, context=0x7f66e4000990) at
gmain.c:4135
#2  0x7f670e41616c in g_main_context_iterate
(context=context@entry=0x7f66e4000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3835
#3  0x7f670e41627c in g_main_context_iteration (context=0x7f66e4000990,
may_block=may_block@entry=1) at gmain.c:3901
#4  0x7f6713d32ecb in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f66e40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7f6713cd9eca in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f66eafe5c60, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#6  0x7f6713af6434 in QThread::exec() (this=) at
thread/qthread.cpp:503
#7  0x7f6717e449b5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5
#8  0x7f6713afb3de in QThreadPrivate::start(void*) (arg=0x55d50d13af50) at
thread/qthread_unix.cpp:331
#9  0x7f671223660a in start_thread (arg=0x7f66eafe6700) at
pthread_create.c:334
#10 0x7f6712efea4d in clone () at /lib64/libc.so.6

Thread 21 (Thread 0x7f66e9766700 (LWP 3831)):
#0  0x7f6712ef2fdd in poll () at /lib64/libc.so.6
#1  0x7f670e41616c in g_main_context_iterate (priority=2147483647, n_fds=1,
fds=0x7f66dc003070, timeout=, context=0x7f66dc000990) at
gmain.c:4135
#2  0x7f670e41616c in g_main_context_iterate
(context=context@entry=0x7f66dc000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3835
#3  0x7f670e41627c in g_main_context_iteration (context=0x7f66dc000990,
may_block=may_block@entry=1) at gmain.c:3901
#4  0x7f6713d32ecb in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f66dc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7f6713cd9eca in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f66e9765c60, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#6  0x7f6713af6434 in QThread::exec() (this=) at
thread/qthread.cpp:503
#7  0x7f6717e449b5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5
#8  0x7f6713afb3de in QThreadPrivate::start(void*) (arg=0x55d50d20abf0) at
thread/qthread_unix.cpp:331
#9  0x7f671223660a in start_thread (arg=0x7f66e9766700) at
pthread_create.c:334
#10 0x7f6712efea4d in clone () at /lib64/libc.so.6

Thread 20 (Thread 0x7f66e3df7700 (LWP 3948)):
#0  0x7f671223bb10 in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  

[frameworks-karchive] [Bug 89051] Kzip: Want Kzip to convert filename charsets in archives & patch

[OGINO Tomonori via KDE Bugzilla]

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

--- Comment #8 from OGINO Tomonori  ---
No.  Formerly, The information of the filename encoding is NOT present in the
ZIP file format.

The information of the OS that the zip file made by is present in the "version
made by" ZIP file header.The filename encoding , in most case, is determined
with "version made by" and User Language by a historical reasons. 

See also
https://marcosc.com/2008/12/zip-files-and-encoding-i-hate-you/ 


But nowadays,  UTF-8 international file name storage was introduced in
APPNOTE.TXT version  6.3.0, 2006-09-29. 
http://www.digitalpreservation.gov/formats/fdd/fdd000354.shtml
What can we do?

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

[kmymoney4] [Bug 360938] Scheduled transactions entered in credit card (liability) have random descriptions populated

[via KDE Bugzilla]

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

--- Comment #4 from lp.allar...@gmail.com ---
I am not off to a good start.  First I downloaded the sources of 4.7.2 then
followed the instructions of the README.cmake file which mentions that I should
run "sudo apt-get build-dep kmymoney" since I am on ubuntu (mint)..  The output
was

Reading package lists... Done
Building dependency tree   
Reading state information... Done
E: Unable to find a source package for kmymoney

Then I tried to manually start the cmake compilation process and got :

CMake Error at CMakeLists.txt:72 (find_package):
  By not providing "FindQGpgme.cmake" in CMAKE_MODULE_PATH this project has
  asked CMake to find a package configuration file provided by "QGpgme", but
  CMake did not find one.

  Could not find a package configuration file provided by "QGpgme" with any
  of the following names:

QGpgmeConfig.cmake
qgpgme-config.cmake

  Add the installation prefix of "QGpgme" to CMAKE_PREFIX_PATH or set
  "QGpgme_DIR" to a directory containing one of the above files.  If "QGpgme"
  provides a separate development package or SDK, be sure it has been
  installed.
-- Configuring incomplete, errors occurred!

I am not sure how to proceed since I am not using KDE as my DE and I am not
developing apps for KDE..

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

[plasmashell] [Bug 355463] xembedsniproxy always crash when login

[Daniel Schulte via KDE Bugzilla]

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

Daniel Schulte  changed:

   What|Removed |Added

 CC||trilader+kdeb...@gmail.com

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

[calligracommon] [Bug 359511] Changing line spacing removes text formatting.

[Camilla Boemann via KDE Bugzilla]

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

Camilla Boemann  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED
  Latest Commit||http://commits.kde.org/call
   ||igra/5b12c6efa4ea89f956c5da
   ||20984d6816f0e6a9e1

--- Comment #4 from Camilla Boemann  ---
Git commit 5b12c6efa4ea89f956c5da20984d6816f0e6a9e1 by C. Boemann.
Committed on 26/03/2016 at 13:12.
Pushed by boemann into branch 'master'.

Make sure the direct formatting dialog doesn't overwrite
blockcharformats and fragment formats with a complete new format, but
rather just apply changes.

M  +0-1libs/text/KoTextEditor_format.cpp
M  +7-5libs/text/commands/ParagraphFormattingCommand.cpp
M  +3-3plugins/textshape/dialogs/CharacterGeneral.cpp
M  +1-1plugins/textshape/dialogs/CharacterGeneral.h
M  +71   -103  plugins/textshape/dialogs/CharacterHighlighting.cpp
M  +4-9plugins/textshape/dialogs/CharacterHighlighting.h
M  +1-1plugins/textshape/dialogs/FontDia.cpp
M  +1-1plugins/textshape/dialogs/ParagraphBulletsNumbers.cpp
M  +1-1plugins/textshape/dialogs/ParagraphBulletsNumbers.h
M  +1-1plugins/textshape/dialogs/ParagraphDecorations.cpp
M  +1-1plugins/textshape/dialogs/ParagraphDecorations.h
M  +5-5plugins/textshape/dialogs/ParagraphDropCaps.cpp
M  +1-1plugins/textshape/dialogs/ParagraphDropCaps.h
M  +7-7plugins/textshape/dialogs/ParagraphGeneral.cpp
M  +1-1plugins/textshape/dialogs/ParagraphGeneral.h
M  +7-7plugins/textshape/dialogs/ParagraphIndentSpacing.cpp
M  +1-1plugins/textshape/dialogs/ParagraphIndentSpacing.h
M  +6-6plugins/textshape/dialogs/ParagraphLayout.cpp
M  +1-1plugins/textshape/dialogs/ParagraphLayout.h
M  +1-1plugins/textshape/dialogs/ParagraphSettingsDialog.cpp
M  +4-4plugins/textshape/dialogs/StyleManager.cpp

http://commits.kde.org/calligra/5b12c6efa4ea89f956c5da20984d6816f0e6a9e1

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

[calligrawords] [Bug 359700] Additional table is inserted after reopening document

[Camilla Boemann via KDE Bugzilla]

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

Camilla Boemann  changed:

   What|Removed |Added

   Version Fixed In||3.0
 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/call
   ||igra/e2ef9c43498165466cbec5
   ||2509b834e026539fc5
 Status|CONFIRMED   |RESOLVED

--- Comment #4 from Camilla Boemann  ---
Git commit e2ef9c43498165466cbec52509b834e026539fc5 by C. Boemann.
Committed on 26/03/2016 at 13:23.
Pushed by boemann into branch 'master'.

Make sure we save nested tables correctly - ToC or hiddenByTable would make us
skip the table, only to save
it in the next block messing everything up.
Unfortunately we still have a bug loding nested tables as we don't seem to hide
the hiddenparagraph of an inner table
FIXED-IN: 3.0

M  +10   -9libs/text/opendocument/KoTextWriter_p.cpp

http://commits.kde.org/calligra/e2ef9c43498165466cbec52509b834e026539fc5

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

[digikam] [Bug 354364] Crash of DNG converter

[via KDE Bugzilla]

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

--- Comment #16 from caulier.gil...@gmail.com ---
The Time Adjust tool is not yet re-integrated in digiKam 5.0.0 after Qt5 port
of application. It still in todo list. Please, be patient, we plan to do it
before final release...

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

[digikam] [Bug 354364] Crash of DNG converter

[Thomas Käfer via KDE Bugzilla]

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

Thomas Käfer  changed:

   What|Removed |Added

 CC||kaef...@gmail.com

--- Comment #15 from Thomas Käfer  ---
I've experienced this bug in digikam 4.12 in the same way Yasin Zähringer
described.

So I've followed the guide at https://www.digikam.org/download?q=download/GIT
to get the latest digikam since this bug entry says "RESOLVED DOWNSTREAM" I
thought that should fix it.

But now I have the problem that in this new version the menu entry that allowed
for mass time stamp manipulation is gone. Or maybe moved? Please help.

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

[plasmashell] [Bug 356800] Add ability to configure how applications are shown on the desktop mouse actions application launcher

[Michael Tunnell via KDE Bugzilla]

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

Michael Tunnell  changed:

   What|Removed |Added

 CC||m...@michaeltunnell.com

--- Comment #1 from Michael Tunnell  ---
This is a bug in Plasma 5 I'm affected by as well, the usability is essentially
lost entirely for me so I simply don't use it anymore.

I just checked it in Plasma 4.14.x and this is not an issue . . . while it is
not configurable in 4.14.x either, it defaults to application Name instead of
Description. Name being the default is logical functionality so I wouldn't
consider it a bug in that scenario. -
http://michaeltunnell.com/images/linux/kde/mouse-action-menu-plasma-4.png

In Plasma 5, the description is used instead and since there are no options to
configure this feature in Desktop Settings > Mouse Actions or System Settings
it makes the desktop application launcher difficult to use.
http://michaeltunnell.com/images/linux/kde/plasma-5.5-mouse-action-launcher-menu-bug.jpg

I'd prefer to have the ability to choose how the items are displayed in the
same way that the Plasma Widgets have but I'd be satisfied personally if the
default setting was Application Name.

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

[frameworks-ktexteditor] [Bug 361014] New: Completion widget flickert and not resize it width after abortCompletion

[Anthony via KDE Bugzilla]

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

Bug ID: 361014
   Summary: Completion widget flickert and not resize it width
after abortCompletion
   Product: frameworks-ktexteditor
   Version: 5.20.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: bvb...@abv.bg

Type in katecomplationwidget.cpp 'm_viewb' and type backspace => completion is
aborted and it has a flickert widget, type one more time backspace and width of
completion widget is not correct calculated.

Reproducible: Always

Steps to Reproduce:
1. Type a word who has a completion widget
2. Type backspace few times
3. Completions widget width after abortCompletion is incorrect

Actual Results:  
https://i.imgur.com/iUrg2V4.png

Expected Results:  
I prefer to hasen't flickert, it's not too difficult 
But width of completion widget *must* be correct

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

[frameworks-ktexteditor] [Bug 360688] Cursor may be invisible at the end of line

[Dominik Haumann via KDE Bugzilla]

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

--- Comment #1 from Dominik Haumann  ---
Side note: the width of the cursor is larger in overwrite mode (full character)

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

[krita] [Bug 361011] Undo issue? (Ubuntu 14.04 Unity - Krita 3.0 Pre-alpha 3 AppImage)

[mvowada via KDE Bugzilla]

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

--- Comment #3 from mvowada  ---
Sorry, I meant the opposite in description:

Actual Results: undo "create new guide" and undo "lock/unlock guide"
Expected Results: undo only "create new guide"

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

[frameworks-ktexteditor] [Bug 335079] Invisible underscore charactere

[Dominik Haumann via KDE Bugzilla]

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

--- Comment #14 from Dominik Haumann  ---
Yes, a "line spacing" option would probably work (but may be visually ugly).

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

[plasmashell] [Bug 355922] Icon and tooltip say "charging" when on battery

[via KDE Bugzilla]

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

--- Comment #7 from vanboxem.ru...@gmail.com ---
I just verified this behaviour: go to hibernate plugged in, pull out adapter,
resume, "ac adapter" state remains plugged in, and therefore icon remains on
charging. The extra state you added doesn't solve this though.

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

[kmymoney4] [Bug 360747] CSV Importer detects more columns than are assigned

[allan via KDE Bugzilla]

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

allan  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

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

[kmymoney4] [Bug 360747] CSV Importer detects more columns than are assigned

[allan via KDE Bugzilla]

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

allan  changed:

   What|Removed |Added

  Attachment #97981|[PATCH] Use parseLine() to  |[PATCH] CSV Importer
description|determine most likely   |detects more columns than
   |fieldDelimiter  |are assigned

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

[plasmashell] [Bug 356908] popup does not factor in auto-hiding panel

[Kai Uwe Broulik via KDE Bugzilla]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

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

[plasmashell] [Bug 355922] Icon and tooltip say "charging" when on battery

[Kai Uwe Broulik via KDE Bugzilla]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED
  Latest Commit||http://commits.kde.org/plas
   ||ma-workspace/93daaf4c504ee2
   ||da91b5bbfc9502d0244105bd18
   Version Fixed In||5.7.0

--- Comment #6 from Kai Uwe Broulik  ---
Git commit 93daaf4c504ee2da91b5bbfc9502d0244105bd18 by Kai Uwe Broulik.
Committed on 26/03/2016 at 14:04.
Pushed by broulik into branch 'master'.

[Battery Monitor] Add a "plugged in but not charging" state for the tooltip

The tooltip would only take into account the AC adapter state and say the
battery is being charged although it isn't. This adds a "Plugged in"
state when the AC is plugged in but the battery is not charging.
FIXED-IN: 5.7.0

M  +6-1applets/batterymonitor/package/contents/ui/batterymonitor.qml

http://commits.kde.org/plasma-workspace/93daaf4c504ee2da91b5bbfc9502d0244105bd18

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

[krita] [Bug 361011] Undo issue? (Ubuntu 14.04 Unity - Krita 3.0 Pre-alpha 3 AppImage)

[mvowada via KDE Bugzilla]

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

--- Comment #2 from mvowada  ---
Thanks! :)

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

[plasmashell] [Bug 355922] Icon and tooltip say "charging" when on battery

[Kai Uwe Broulik via KDE Bugzilla]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

 Status|NEEDSINFO   |CONFIRMED
 Resolution|WAITINGFORINFO  |---
 Ever confirmed|0   |1

--- Comment #5 from Kai Uwe Broulik  ---
Ok, I found the cause. It just checks whether the AC is plugged in, not the
battery state.

The icon should reflect the AC state but the tooltip should perhaps have a
"plugged in but not charging" state.

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

[plasmashell] [Bug 355922] Icon and tooltip say "charging" when on battery

[Kai Uwe Broulik via KDE Bugzilla]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #4 from Kai Uwe Broulik  ---
Ok, thanks. Can you run plasmaengineexplorer (part of Plasma SDK) and see in
the "powermanagement" what the "State" says in "Battery" (not Battery0) ?

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

[krita] [Bug 361011] Undo issue? (Ubuntu 14.04 Unity - Krita 3.0 Pre-alpha 3 AppImage)

[Boudewijn Rempt via KDE Bugzilla]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1
 CC||b...@valdyas.org

--- Comment #1 from Boudewijn Rempt  ---
Hi Mvowada! 

Haven't seen you for quite some time, and really missed you :-). And, yes, I
can confirm the issue. Something is really weird here. Though I'm actually not
sure that the lock button state should go into the undo stack, I see that the
Show guides check is also affected.

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

[krita] [Bug 349484] Multiple masks not refreshed on canvas - (Possibly related to Bug 345612)

[mvowada via KDE Bugzilla]

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

mvowada  changed:

   What|Removed |Added

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

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

[krita] [Bug 361012] New: Undo only actions, not user settings?

[mvowada via KDE Bugzilla]

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

Bug ID: 361012
   Summary: Undo only actions, not user settings?
   Product: krita
   Version: 3.0 Alpha
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: usability
  Assignee: krita-bugs-n...@kde.org
  Reporter: freebo...@tiscali.it

Personal view, however I think it'd be better if undo/redo commands couldn't
affect user settings, only operations. (Ubuntu 14.04 Unity - Krita 3.0
Pre-alpha 3 AppImage)

Reproducible: Always

Steps to Reproduce:
1. Lock/Unlock guide
2. Undo

Actual Results:  
undo "Lock/Unlock guide"

Expected Results:  
nothing (or undo the last operation)

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

[krita] [Bug 361011] New: Undo issue? (Ubuntu 14.04 Unity - Krita 3.0 Pre-alpha 3 AppImage)

[mvowada via KDE Bugzilla]

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

Bug ID: 361011
   Summary: Undo issue? (Ubuntu 14.04 Unity - Krita 3.0 Pre-alpha
3 AppImage)
   Product: krita
   Version: 3.0 Alpha
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: usability
  Assignee: krita-bugs-n...@kde.org
  Reporter: freebo...@tiscali.it

Not sure if it's expected (Ubuntu 14.04 Unity - Krita 3.0 Pre-alpha 3
AppImage):

Reproducible: Always

Steps to Reproduce:
1. lock/unlock guide
2. create new guide
3. undo (CTRL+Z)

Actual Results:  
undo only "create new guide"

Expected Results:  
undo "create new guide" and undo "lock/unlock guide"

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

[kphotoalbum] [Bug 360977] Autocomplete in annotation dialog fails with some category names

[Andreas Schleth via KDE Bugzilla]

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

--- Comment #7 from Andreas Schleth  ---
OK, You caught me (again!) with not investigating the options closely enough...
  Thanks!

I tried and succeeded.  It even works, when I change the default and then, in
another session, open a different database.

Maybe it would be easiest to change the default and leave it at that.  
However, as this seems to be one of the central KPA settings
(~/.kde4/share/config/kphotoalbum.rc ??), this default will only work as such
for new users or people who clean up their rc-files.  [On the other hand: I did
not find this setting in the rc-files...(??)]

Right now: "Works for me. ™" 

Let's add some explanation (found by means of experimental informatics):
- Match tags from the first character:  
regex: /^search_string/
search a left justified string
This is, how autocomplete works in the most natural way.

- Match tags from word boundaries: 
regex: /\Wsearch_string.*\W/ 
search a string left justified at any word boundary - cannot search across word
boundaries
If you need to find last names.

- Match tags anywhere: 
regex: /search_string/
search any string anywhere
This is most useful for people who use the input field knowingly as a search
field.

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

[plasmashell] [Bug 355922] Icon and tooltip say "charging" when on battery

[via KDE Bugzilla]

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

vanboxem.ru...@gmail.com changed:

   What|Removed |Added

 CC||vanboxem.ru...@gmail.com

--- Comment #3 from vanboxem.ru...@gmail.com ---
I can confirm on Arch Linux, KDE Frameworks 5.19, Qt 5.5.1.

Output of upower -d:

Device: /org/freedesktop/UPower/devices/line_power_ADP1 
  native-path:  ADP1
  power supply: yes 
  updated:  do 24 mrt 2016 15:13:02 CET (170446 seconds ago)
  has history:  no  
  has statistics:   no  
  line-power
warning-level:   none   
online:  yes
icon-name:  'ac-adapter-symbolic'   

Device: /org/freedesktop/UPower/devices/battery_BAT1
  native-path:  BAT1
  vendor:   Sony Corporation
  power supply: yes 
  updated:  za 26 mrt 2016 14:33:46 CET (2 seconds ago) 
  has history:  yes 
  has statistics:   yes 
  battery   
present: yes
rechargeable:yes
state:   discharging
warning-level:   none   
energy:  17,76 Wh   
energy-empty:0 Wh   
energy-full: 32,64 Wh   
energy-full-design:  59,5 Wh
energy-rate: 17,444 W   
voltage: 10,978 V   
time to empty:   1,0 hours  
percentage:  54%
capacity:54,8571%   
technology:  lithium-ion
icon-name:  'battery-good-symbolic' 
  History (charge): 
1458999226  54,000  discharging 
  History (rate):   
1458999226  17,444  discharging 

Device: /org/freedesktop/UPower/devices/DisplayDevice
  power supply: yes
  updated:  za 26 mrt 2016 14:33:46 CET (2 seconds ago)
  has history:  no
  has statistics:   no
  battery
present: yes
state:   discharging
warning-level:   none
energy:  17,76 Wh
energy-full: 32,64 Wh
energy-rate: 17,444 W
time to empty:   1,0 hours
percentage:  54%
icon-name:  'battery-good-symbolic'

Daemon:
  daemon-version:  0.99.4
  on-battery:  no
  lid-is-closed:   no
  lid-is-present:  yes
  critical-action: HybridSleep

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

[korgac] [Bug 250729] korganizer fires remainder event every minute

[Wulf via KDE Bugzilla]

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

--- Comment #17 from Wulf  ---
@Tsu Jan
I think you are right, because reminders stopped at 3 am.

But then there is a bug in the calculation of the beginning of DST for Europe.
It's the last Sunday in march 1 am UTC, not Saturday!

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

[krita] [Bug 349484] Multiple masks not refreshed on canvas - (Possibly related to Bug 345612)

[mvowada via KDE Bugzilla]

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

mvowada  changed:

   What|Removed |Added

  Attachment #93287|0   |1
is obsolete||

--- Comment #3 from mvowada  ---
Created attachment 98100
  --> https://bugs.kde.org/attachment.cgi?id=98100=edit
Krita 3.0 Alpha - Trasparency bug video example

Hi Boudewijn,
Unfortunately I can still reproduce the bug here (video in attachment).
I've checked with Krita 3.0 Pre-alpha 3 AppImage.

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

[krita] [Bug 359931] performance decrease compared to stable release

[via KDE Bugzilla]

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

--- Comment #5 from kde...@tuta.io ---
I think I made a mistake when I submitted the bug.
Sorry for causing confusion, but when I selected openSUSE RPM as platform I
actually meant I'm having these issues with the Krita appimages and Krita
master compiled from source on openSUSE Tumbleweed, not with any openSUSE Krita
package.

I built them with Vc.
However, I just made a new build from master and I can't reproduce these issues
anymore.
I still experienced the "sluggish brush that gets worse with smaller brush
size"  issue mentioned on the recent appimage release (third), so I assume
whatever caused it was fixed between then and now.

Advanced Color Selector is now the only thing that is slower on any version of
3.0 I tried, but I guess this was unrelated and doesn't fall under the topic of
general performance issue anymore.

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

[krita] [Bug 348097] Predefined brush tip changes after resizing, if you have a tag selected for brush tips in brush editor and use a brush with a brush tip which is not in the selected tag

[via KDE Bugzilla]

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

--- Comment #12 from trueki...@gmail.com ---
I agree that even this simple workaround partial solution would be a good idea.
Without selecting this "all" tag every time I start krita I can't even resize
my brushes with predefined tips. Even though using tags will still be flawed
(as it is now) but at least there won't be a problem right from the start of
the program :)

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

[kmymoney4] [Bug 360435] CSV Importer doesn't recognize security if its symbol isn't lower case

[allan via KDE Bugzilla]

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

allan  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #7 from allan  ---
I did fix this a while ago, following
https://bugs.kde.org/show_bug.cgi?id=352789, but somehow things got
side-tracked, and it was not committed.

The proposed patch looks, good, but I would make one change, in
"
securityName = m_wizDlg->m_csvDialog->ui->tableWidget->item(row,
detail)->text().toUpper().trimmed();"

I would propose removing the '.toUpper()', allowing the user's value/preference
to be maintained.

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

[ark] [Bug 335716] Incorrect displaying file names in .zip cp2151

[Alexander Potashev via KDE Bugzilla]

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

--- Comment #18 from Alexander Potashev  ---
Fixed in p7zip 15.14. Thanks for the notification!

=
aspotashev@cell ~ $ /usr/bin/7z l -slt
/home/aspotashev/Downloads/cyrilic_bug.zip

7-Zip [64] 15.14 : Copyright (c) 1999-2015 Igor Pavlov : 2015-12-31
p7zip Version 15.14 (locale=ru_RU.UTF-8,Utf16=on,HugeFiles=on,64 bits,2 CPUs
Intel(R) Celeron(R) CPU B800 @ 1.50GHz (206A7),ASM)

Scanning the drive for archives:
1 file, 390 bytes (1 KiB)

Listing archive: /home/aspotashev/Downloads/cyrilic_bug.zip

--
Path = /home/aspotashev/Downloads/cyrilic_bug.zip
Type = zip
Physical Size = 390

--
Path = папка
Folder = +
Size = 0
Packed Size = 0
Modified = 2014-08-18 14:52:37
Created = 2014-08-18 14:52:23
Accessed = 2014-08-18 14:52:37
Attributes = D
Encrypted = -
Comment = 
CRC = 
Method = Store
Host OS = FAT
Version = 10

Path = папка/файл.txt
Folder = -
Size = 0
Packed Size = 0
Modified = 2014-08-18 14:52:34
Created = 2014-08-18 14:52:34
Accessed = 2014-08-18 14:52:34
Attributes = A
Encrypted = -
Comment = 
CRC = 
Method = Store
Host OS = FAT
Version = 10

aspotashev@cell ~ $ /usr/bin/7z l -slt
/home/aspotashev/Downloads/cyrilic_bug.rar

7-Zip [64] 15.14 : Copyright (c) 1999-2015 Igor Pavlov : 2015-12-31
p7zip Version 15.14 (locale=ru_RU.UTF-8,Utf16=on,HugeFiles=on,64 bits,2 CPUs
Intel(R) Celeron(R) CPU B800 @ 1.50GHz (206A7),ASM)

Scanning the drive for archives:
1 file, 136 bytes (1 KiB)

Listing archive: /home/aspotashev/Downloads/cyrilic_bug.rar

--
Path = /home/aspotashev/Downloads/cyrilic_bug.rar
Type = Rar
Physical Size = 136
Solid = -
Blocks = 2
Multivolume = -
Volumes = 1

--
Path = папка/файл.txt
Folder = -
Size = 0
Packed Size = 0
Modified = 2014-08-18 14:52:34
Created = 
Accessed = 
Attributes = A
Encrypted = -
Solid = -
Commented = -
Split Before = -
Split After = -
CRC = 
Host OS = Win32
Method = m0:17
Version = 29

Path = папка
Folder = +
Size = 0
Packed Size = 0
Modified = 2014-08-18 14:52:37
Created = 
Accessed = 
Attributes = D
Encrypted = -
Solid = -
Commented = -
Split Before = -
Split After = -
CRC = 
Host OS = Win32
Method = m0
Version = 20

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