[frameworks-kimageformats] [Bug 397040] New: crash when save a QImage to the eps format file

[zccrs]

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

Bug ID: 397040
   Summary: crash when save a QImage to the eps format file
   Product: frameworks-kimageformats
   Version: unspecified
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: alex.me...@kde.org
  Reporter: zc...@live.com
CC: kdelibs-b...@kde.org
  Target Milestone: ---

#include 
#include 

int main()
{
QImage image(100, 100, QImage::Format_ARGB32);

qDebug() << image.save("/tmp/test.eps", "eps");

return 0;
}


Crash at: QPrinterPrivate::init
Output: QPrinter: Must construct a QCoreApplication before a QPrinter

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

[okular] [Bug 397039] When a PDF file is saved using file > save as, the file path in file > properties is not updated

[Kishore Gopalakrishnan]

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

Kishore Gopalakrishnan  changed:

   What|Removed |Added

Summary|When a PDF file is saved|When a PDF file is saved
   |using file> save as, the|using file > save as, the
   |file path in file > |file path in file >
   |proerties is not updated|properties is not updated

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

[okular] [Bug 397039] New: When a PDF file is saved using file> save as, the file path in file > proerties is not updated

[Kishore Gopalakrishnan]

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

Bug ID: 397039
   Summary: When a PDF file is saved using file> save as, the file
path in file > proerties is not updated
   Product: okular
   Version: 1.4.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: kishor...@gmail.com
  Target Milestone: ---

Steps to reproduce:
1. Settings > configure okular 
2. Uncheck 'display document title...' if it is checked.
3. Select 'display full file path' when not displaying document title.
4. Open a PDF file.
5. File > Save as; save it somewhere else under a different name in a different
location
6. Note that the window title changes, indicating that okular is showing the
file in the new location.
7. Go to File > Properties.
8. Look at the value of 'file path'.

Observed results:
The file path shown in the properties dialogue is the old path, but the new
path is shown in the window title. Reloading the file by pressing 'F5' updates
the path in File > Properties to the new location.

Expected results:
The new path and filename should be shown both in the window title and the
Properties dialogue.

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

[latte-dock] [Bug 397038] New: Latte setting window is a bit wide after some recent commit

[bugzilla_noreply]

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

Bug ID: 397038
   Summary: Latte setting window is a bit wide after some recent
commit
   Product: latte-dock
   Version: git (master)
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: application
  Assignee: mvourla...@gmail.com
  Reporter: tr...@yandex.com
  Target Milestone: ---

Please see the pictures below:

Before: https://i.imgur.com/XYYuAGO.png
After: https://i.imgur.com/ZybH9H9.png

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

[plasmashell] [Bug 397037] Software Updates icon on the system tray doesn't change when I change the desktop theme

[bugzilla_noreply]

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

--- Comment #2 from tr...@yandex.com ---
Created attachment 114247
  --> https://bugs.kde.org/attachment.cgi?id=114247=edit
Pic2

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

[plasmashell] [Bug 397037] Software Updates icon on the system tray doesn't change when I change the desktop theme

[bugzilla_noreply]

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

--- Comment #1 from tr...@yandex.com ---
Created attachment 114246
  --> https://bugs.kde.org/attachment.cgi?id=114246=edit
Pic1

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

[plasmashell] [Bug 397037] New: Software Updates icon on the system tray doesn't change when I change the desktop theme

[bugzilla_noreply]

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

Bug ID: 397037
   Summary: Software Updates icon on the system tray doesn't
change when I change the desktop theme
   Product: plasmashell
   Version: 5.13.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: tr...@yandex.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Steps to reproduce:

1. Use the Breeze Dark desktop theme, Breeze icon theme.
2. Change the desktop theme to
[Adapta-KDE](https://github.com/PapirusDevelopmentTeam/adapta-kde)
3. Result: the Software Updates icon on the system tray doesn't change to the
icon provided by the Adapta desktop theme, it still uses the icon provided by
the Breeze icon theme. (Pic1)

Expected result:

It changes to the right icon provided by the Adapta desktop theme.
(If I restart plasmashell, the icon will change to the right one) (Pic2)

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

[latte-dock] [Bug 397036] New: Is there any way to change the desktop widget background transparency?

[bugzilla_noreply]

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

Bug ID: 397036
   Summary: Is there any way to change the desktop widget
background transparency?
   Product: latte-dock
   Version: git (master)
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: application
  Assignee: mvourla...@gmail.com
  Reporter: tr...@yandex.com
  Target Milestone: ---

I really like the Latte's ability to change the panel/dock background
transparency and their blur effect, apply to any desktop theme. That's very
nice.

But currently, from Latte there is no way to change the desktop widget
background transparency, something like what the BreezeAlphaBlack Control
widget can do (but it only applies to the BreezeAlphaBlack desktop theme).

So what do you think about adding this feature?

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

[krita] [Bug 369475] Resizing the Krita window hangs for about 10-20 seconds after a long period of not resizing the window

[Phoenix Enero]

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

--- Comment #5 from Phoenix Enero  ---
Hi, sorry for lack of responses.

I have not encountered this bug in my work for the past several months. I think
the version 4 update fixed it in general.

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

[amarok] [Bug 397035] New: Amarok 2.x syncronization target is always offline

[Anderson Medeiros Gomes]

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

Bug ID: 397035
   Summary: Amarok 2.x syncronization target is always offline
   Product: amarok
   Version: 2.9.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Tools/Statistics Synchronization
  Assignee: amarok-bugs-d...@kde.org
  Reporter: amg1...@gmail.com
CC: ma...@laitl.cz
  Target Milestone: kf5

Dear Amarok developers,

I am currently unable to configure synchronization of ratings and play count
information embedded in my MP3 files with an external MariaDB database. I tried
to execute the following steps:

* From the main window, I navigated to "Settings => Configure Amarok =>
Metadata => Statistics Synchronization";
* I clicked at the "Add" button and added a new synchronization target of type
"Amarok 2.x" and database type "external";
* I clicked at the "Synchronize" button, selected the collections I wanted to
synchronize, selected all information fields and clicked "Next";

On the "Synchronize Statistics" window, I can see a list of tracks from the
local collection, however I am not able to see a list of tracks from my
external database. In addition, on the "Configure" window, I see the message
"This collection is currently offline" when I hover the mouse over the
synchronization target I created.

When launching Amarok from a console window by using the command line "amarok
--debug --nofork", I am able to see the following messages:

-

amarok: END__: void Amarok2ConfigDialog::updateButtons() [Took: 0s] 
QSqlDatabase: MYSQL driver not loaded
QSqlDatabase: available drivers: QIBASE QSQLITE QMYSQL3 QMYSQL QPSQL7 QPSQL
amarok: BEGIN: void Amarok2ConfigDialog::updateButtons() 

-

Additional troubleshooting of my issue has made me believe that in the source
file src/importers/amarok/AmarokProvider.cpp:38 [1], the argument "MYSQL" is
expected to be "QMYSQL", instead. That is because the
ImporterSqlConnection:ImporterSqlConnection constructor, which is declared in
src/importers/ImporterSqlConnection.cpp:32 [2], seems to pass the "MYSQL"
string unmodified to QSqlDatabase::addDatabase [3] constructor.

Please, could you verify if my diagnostic makes sense?

-

[1]
https://github.com/KDE/amarok/blob/453aa79e03fc512abcca5b2109a2aecce6dab314/src/importers/amarok/AmarokProvider.cpp#L38
[2]
https://github.com/KDE/amarok/blob/453aa79e03fc512abcca5b2109a2aecce6dab314/src/importers/ImporterSqlConnection.cpp#L32
[3] http://doc.qt.io/archives/qt-4.8/qsqldatabase.html#addDatabase-2

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

[kpat] [Bug 397034] New: completed piles fail to fall and left a space between completed piles

[gary]

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

Bug ID: 397034
   Summary: completed piles fail to fall and left a space between
completed piles
   Product: kpat
   Version: 3.6
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: co...@kde.org
  Reporter: la.bu...@gmail.com
CC: kde-games-b...@kde.org
  Target Milestone: ---

Application: kpat (3.6)

Qt Version: 5.6.2
Frameworks Version: 5.32.0
Operating System: Linux 4.4.138-59-default x86_64
Distribution: "openSUSE Leap 42.3"

-- Information about the crash:
- What I was doing when the application crashed:
after 4th completed pile fell i still had a space between 2nd and 3rd pile when
i moved cursor spider crashed

-- Backtrace:
Application: KPatience (kpat), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f3217779780 (LWP 26121))]

Thread 3 (Thread 0x7f31fb1ef700 (LWP 26124)):
#0  0x7f321313630d in poll () from /lib64/libc.so.6
#1  0x7f320e912314 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f320e91242c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f3213d3f1ab in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#4  0x7f3213cecbfb in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#5  0x7f3213b27f5a in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x7f320fb61295 in ?? () from /usr/lib64/libQt5DBus.so.5
#7  0x7f3213b2ca29 in ?? () from /usr/lib64/libQt5Core.so.5
#8  0x7f320f046724 in start_thread () from /lib64/libpthread.so.0
#9  0x7f321313ee8d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f32035d1700 (LWP 26123)):
#0  0x7f321313630d in poll () from /lib64/libc.so.6
#1  0x7f320cf613c2 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7f320cf62faf in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7f3205b2c0d9 in ?? () from /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f3213b2ca29 in ?? () from /usr/lib64/libQt5Core.so.5
#5  0x7f320f046724 in start_thread () from /lib64/libpthread.so.0
#6  0x7f321313ee8d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f3217779780 (LWP 26121)):
[KCrash Handler]
#6  0x0045ac49 in ?? ()
#7  0x7f3213d18de3 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib64/libQt5Core.so.5
#8  0x7f3213d18de3 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib64/libQt5Core.so.5
#9  0x7f3213d18de3 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib64/libQt5Core.so.5
#10 0x7f3213d25dd2 in QTimer::timerEvent(QTimerEvent*) () from
/usr/lib64/libQt5Core.so.5
#11 0x7f3213d19bf4 in QObject::event(QEvent*) () from
/usr/lib64/libQt5Core.so.5
#12 0x7f32150a828c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib64/libQt5Widgets.so.5
#13 0x7f32150ac8ea in QApplication::notify(QObject*, QEvent*) () from
/usr/lib64/libQt5Widgets.so.5
#14 0x7f3213ceebe5 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib64/libQt5Core.so.5
#15 0x7f3213d3eafe in QTimerInfoList::activateTimers() () from
/usr/lib64/libQt5Core.so.5
#16 0x7f3213d3eec1 in ?? () from /usr/lib64/libQt5Core.so.5
#17 0x7f320e912134 in g_main_context_dispatch () from
/usr/lib64/libglib-2.0.so.0
#18 0x7f320e912388 in ?? () from /usr/lib64/libglib-2.0.so.0
#19 0x7f320e91242c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#20 0x7f3213d3f18c in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#21 0x7f3213cecbfb in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#22 0x7f3213cf4ae6 in QCoreApplication::exec() () from
/usr/lib64/libQt5Core.so.5
#23 0x0041efaf in ?? ()
#24 0x7f3213072725 in __libc_start_main () from /lib64/libc.so.6
#25 0x0041f849 in _start ()

Possible duplicates by query: bug 395984, bug 395983, bug 395982, bug 395624,
bug 389064.

Reported using DrKonqi

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

[kwin] [Bug 397032] [Wayland] Some task switcher visualizations should appear on the center of the screen but instead they appear on the top left

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

 CC||k...@davidedmundson.co.uk
 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

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


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

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

[kwin] [Bug 386304] [Wayland] Several task switchers are not centered on screen

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

 CC||jfeb...@gmail.com

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

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

[plasmashell] [Bug 397019] Wrong ISO file icon display on Folder View widgets

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

  Component|Widget Explorer |Folder
 Status|UNCONFIRMED |NEEDSINFO
 CC||k...@davidedmundson.co.uk,
   ||plasma-b...@kde.org
 Resolution|--- |WAITINGFORINFO
Summary|[Kubuntu 18.04] wrong ISO   |Wrong ISO file icon display
   |file icon display on Folder |on Folder View widgets
   |View widgets|
   Assignee|plasma-b...@kde.org |h...@kde.org

--- Comment #1 from David Edmundson  ---
Please state the Plasma version. You can find it in kinfocenter. I don't know
what different downstreams have.

Are these icons correct in dolphin?

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

[valgrind] [Bug 396290] [PATCH] Possible tool - allocfail

[Roger Light]

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

Roger Light  changed:

   What|Removed |Added

 Attachment #114229|0   |1
is obsolete||
 CC||ro...@atchoo.org

--- Comment #16 from Roger Light  ---
Created attachment 114245
  --> https://bugs.kde.org/attachment.cgi?id=114245=edit
Updated patch with UInt fix, plus others

This addresses the points in comments 13 and 14.

The reason for the crash is now obvious, I hadn't spotted it because it only
manifests on stripped binaries, or if --show-below-main is set.

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

[valgrind] [Bug 396290] [PATCH] Possible tool - allocfail

[Roger Light]

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

--- Comment #15 from Roger Light  ---
Thanks for the comments and review.

I think adding greater capability for controlling where and when failures
occur, and adding syscall support could turn this into a really useful tool. I
don't think that should take away from there already is though.

How about renaming to "failcheck" for example, and rewriting a load of the text
to make it clear the tool is about failure checking in general and at the
moment considers heap allocation failures, then expanding the scope once you
are happy with everything as it stands.

Ivo, I'm annoyed I missed the whitespace, I do pay attention to that sort of
thing. For af_instrument, you just mean the 4 spaces indentation instead of 3,
nothing to do with the function arguments?

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

[drkonqi] [Bug 397030] drkonqi - version 5.13.4 - can not compile it because of a problem with backtraceparsertest

[Christoph Feck]

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

--- Comment #3 from Christoph Feck  ---
Are you using an out-of-source build?

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

[konsole] [Bug 396006] Can't attach tabs unless single process mode is used

[Thaodan]

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

--- Comment #5 from Thaodan  ---
>Works for me without using single process mode. Can you verify that switching 
>>that setting (and only that setting) on and off triggers and fixes the bug?
Yes I tried that and thats exactly what happens.

>If you start 2 different konsole separately, you can not move tabs between 
>them >regardless of the 'single' settings.

>So I'm not sure what the reporter is trying to do.
Thats I exactly what I reported.
I had not single mode enabled and move tabs between two windows.
With single mode it works.

A better hint to that would be great, even if this is intended.

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

[plasmashell] [Bug 397017] Activate grouped windows from alternative activities isnt working for taskmanager

[Michail Vourlakos]

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

Michail Vourlakos  changed:

   What|Removed |Added

 CC||mvourla...@gmail.com

--- Comment #1 from Michail Vourlakos  ---
Ok, this is happening also with plasma taskmanagers so I suppose this is
something upstream and not Latte.

How to reproduce for plasma icon-only taskmanager:

1. Add an icon-only plasma taskmanager
2. Disable "Show only tasks from current activity"
3. open two windows of same app in Activity A
4. Switch to Activity B and try to click the grouped windows from Activity A,
it doesnt do anything

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

[kwin] [Bug 397032] New: [Wayland] Some task switcher visualizations should appear on the center of the screen but instead they appear on the top left

[Josep Febrer]

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

Bug ID: 397032
   Summary: [Wayland] Some task switcher visualizations should
appear on the center of the screen but instead they
appear on the top left
   Product: kwin
   Version: git master
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: jfeb...@gmail.com
  Target Milestone: ---

Created attachment 114244
  --> https://bugs.kde.org/attachment.cgi?id=114244=edit
Large Icon task switch visualization appearing on the top left of the screen

On a Plasma Wayland session some task switcher visualizations they should
appear on the center of the screen, but they appear on the top left of the
screen.
The affected visualizations are: Small Icons, Informative, Text Only, Large
Icons, Compact and Thumbnails.
On a Plasma Xorg session they appear on the center of the screen as intended.
I'm running a current Debian GNU/Linux sid system, with Qt 5.11.1 and today
builds of kwayland, kwin, plasma-workspace and plasma-desktop.

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

[plasmashell] [Bug 397017] Activate grouped windows from alternative activities isnt working for taskmanager

[Michail Vourlakos]

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

Michail Vourlakos  changed:

   What|Removed |Added

 CC||plasma-b...@kde.org
Product|latte-dock  |plasmashell
   Assignee|mvourla...@gmail.com|h...@kde.org
Version|git (master)|5.13.3
  Component|plasmoid|Task Manager
   Target Milestone|--- |1.0

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

[choqok] [Bug 397031] New: Twitter: opening conversation/thread results in 401

[Thaodan]

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

Bug ID: 397031
   Summary: Twitter: opening conversation/thread results in 401
   Product: choqok
   Version: Git
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Twitter
  Assignee: mehrdad.mom...@gmail.com
  Reporter: theodorstormgr...@gmail.com
CC: scarp...@kde.org
  Target Milestone: ---

Created attachment 114243
  --> https://bugs.kde.org/attachment.cgi?id=114243=edit
mitmproxy dump

When I try to open a conversation I get:
org.kde.choqok.twitterapi: Error: "Could not authenticate you."
org.kde.choqok.twitterapi: Fetching post: Server Error: "Could not authenticate
you."


This results in only the first (or final) post being shown.

I logged the event with mitmproxy and attached it here.

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

[valgrind] [Bug 385707] memcheck-amd64-linux crashing

[Daniel Gutson]

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

--- Comment #5 from Daniel Gutson  ---
Thanks Philippe. We will retry with the conditions you suggest and will write
the results here.

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

[Akonadi] [Bug 396980] akonadi_imap_resource segfaults [due to ImapQuotaAttribute in libakonadi-singlefileresource.so]

[Christophe Giboudeaux]

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

Christophe Giboudeaux  changed:

   What|Removed |Added

 CC|kdepim-b...@kde.org |

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

[Akonadi] [Bug 396980] akonadi_imap_resource segfaults [due to ImapQuotaAttribute in libakonadi-singlefileresource.so]

[Christophe Giboudeaux]

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

Christophe Giboudeaux  changed:

   What|Removed |Added

   Assignee|broeks...@kde.org   |kdepim-b...@kde.org

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

[drkonqi] [Bug 397030] drkonqi - version 5.13.4 - can not compile it because of a problem with backtraceparsertest

[shevegen]

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

--- Comment #2 from shevegen  ---
Well another try; guess this can not be edited once posted, sorry. :)

  Operating System:   GNU/Linux
  Os Bit Type:x86_64
  CPU Model:  AMD A8-7600 Radeon R7, 10 Compute Cores 4C+6G,  cores
  CFLAGS in use:  -O2 -fPIC -fno-strict-overflow -Wno-error
  Screen Resolution:  1920x1080
  Gcc Version:8.2.0
  Glibc Version:  2.26
  Kernel Version: 4.14.12

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

[drkonqi] [Bug 397030] drkonqi - version 5.13.4 - can not compile it because of a problem with backtraceparsertest

[shevegen]

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

--- Comment #1 from shevegen  ---
Oops - sorry for the weird line breaks, guess there were ' ' characters that I
did not see in the textfield (I just copy/pasted it from the output of a
terminal script; will look for stray ' ' and less of them next time when
pasting here into a textfield).

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

[kwin] [Bug 397029] [Wayland] Some windows or dialogs don't appear below a top panel

[Josep Febrer]

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

--- Comment #3 from Josep Febrer  ---
Created attachment 114242
  --> https://bugs.kde.org/attachment.cgi?id=114242=edit
Yakuake window where it should appeear

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

[kwin] [Bug 397029] [Wayland] Some windows or dialogs don't appear below a top panel

[Josep Febrer]

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

--- Comment #1 from Josep Febrer  ---
Created attachment 114240
  --> https://bugs.kde.org/attachment.cgi?id=114240=edit
KRunner dialog where it should appear

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

[drkonqi] [Bug 397030] New: drkonqi - version 5.13.4 - can not compile it because of a problem with backtraceparsertest

[shevegen]

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

Bug ID: 397030
   Summary: drkonqi - version 5.13.4 - can not compile it because
of a problem with backtraceparsertest
   Product: drkonqi
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: sheve...@gmail.com
  Target Milestone: ---

[ 13%] Built target drkonqi_backtrace_parser
[ 14%] Automatic MOC for target drkonqi
[ 14%] Built target drkonqi_autogen
[ 73%] Built target drkonqi
[ 75%] Automatic MOC for target crashtest
[ 75%] Built target crashtest_autogen
[ 78%] Built target crashtest
[ 80%] Automatic MOC for target backtraceparsertest_manual
[ 80%] Built target backtraceparsertest_manual_autogen
[ 85%] Built target backtraceparsertest_manual
[ 86%] Automatic MOC for target backtraceparsertest
[ 86%] Built target backtraceparsertest_autogen
[ 88%] Linking CXX executable ../../../bin/backtraceparsertest
failed to create symbolic link 'backtraceparsertest_data' because existing path
cannot be removed: Is a directory
make[2]: ***
[src/tests/backtraceparsertest/CMakeFiles/backtraceparsertest.dir/build.make:116:
bin/backtraceparsertest] Fehler 1
make[2]: *** Datei ,,bin/backtraceparsertest" wird gelöscht
make[1]: *** [CMakeFiles/Makefile2:619:
src/tests/backtraceparsertest/CMakeFiles/backtraceparsertest.dir/all] Fehler 2
make: *** [Makefile:141: all] Fehler 2

^

fails to compile for me at the "Linking CXX executable". Not sure why it can
not link it. Most of the other kde-plasma things compile fine for me by the
way, in the 5.13.4 branch.

I guess the error may happen at the symlink part - weird that it wants to 
remove a directory.

PS: This should be filed under compile-related problem perhaps, but this
option was not available in the bug tracker.

If my environment is important, I copy/paste it next:


  Operating System:GNU/Linux
  Os Bit Type: x86_64   
  CPU Model:   AMD A8-7600 Radeon R7, 10 Compute Cores
4C+6G,  cores
  CFLAGS in use:   -O2 -fPIC -fno-strict-overflow -Wno-error
  Gcc Version: 8.2.0
  Glibc Version:   2.26 
  Kernel Version:  4.14.12  


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

[valgrind] [Bug 396290] [PATCH] Possible tool - allocfail

[Ivo Raisr]

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

--- Comment #14 from Ivo Raisr  ---
The current exp-allocfail crashes badly on my Ubuntu 18.04 box.
When running './vg-in-place --tool=exp-allocfail /bin/date', it crashes at
af_main.c:119.
That's because i is equal to an equivalent of '-1' (4294967295).

You need to fix the code at af_main.c:96
-   UInt i;
+   Int i;


With this fix in place, I was able to play with ordinary Linux/UNIX standalone
programs.
Will try to do 'make dist' and check if everything works ok tomorrow.

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

[kaffeine] [Bug 397028] New: Exit Problems in main window after TV program change

[bugzilla_noreply]

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

Bug ID: 397028
   Summary: Exit Problems in main window after TV program change
   Product: kaffeine
   Version: 2.0.15
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: mchehab+sams...@kernel.org
  Reporter: simonboett...@googlemail.com
  Target Milestone: ---

If I click on the main window exit button (this little "x" or hitting ALT+F4)
after some videos are played, the main window disappears together with its big
taskbar icon but the small kaffeine icon in the notification area is still
visible. Before using kaffeine again I have to kill the dead kaffeine task. No
problem when the program is terminated with File->Quit or if I haven't played
any videos (video file or tv).

Example output of gdb when kaffeine is in "ghost" mode (the numbers are
changing):
-
Attaching to program: /usr/bin/kaffeine, process 6134
[New LWP 6144]
[New LWP 6145]
[New LWP 6146]
[New LWP 6147]
[New LWP 6148]
[New LWP 6149]
[New LWP 6509]
[New LWP 6689]
[New LWP 6690]
[New LWP 6691]
[New LWP 6710]
[New LWP 6711]
[New LWP 6717]
[New LWP 6718]
[New LWP 6719]
[New LWP 6720]
[New LWP 6721]
[New LWP 6722]
[New LWP 6723]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
0x7efef08964cd in __pthread_timedjoin_ex () from /usr/lib/libpthread.so.0
-

I am using cinnamon 3.8.8-1, kio 5.48.0-1, vlc 3.0.3-2, libxss 1.2.2-3  on Arch
Linux.

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

[KBibTeX] [Bug 397027] Sciencedirect search broken

[Volker Fröhlich]

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

--- Comment #2 from Volker Fröhlich  ---
https://github.com/JabRef/jabref/issues/1258 for reference

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

[valgrind] [Bug 396290] [PATCH] Possible tool - allocfail

[Ivo Raisr]

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

--- Comment #13 from Ivo Raisr  ---
(In reply to roger.light from comment #8)
> Created attachment 114229 [details]
> Updated patch with fixes and text callstacks.

Looks quite good. There are just few nits:
- Please remove trailing whitespace you introduced (a few occurrences).
For example 'git am' gives the list.
- Please have a space between 'while' and the condition.
- Please do better job with fixed size buffers (for example in
write_callstack_line).
  Some times ago, Florian underwent a painful exercise auditing all fixed size
buffers.
- You can use C99 constructs.
- Description for command line option --callstack-file deserves a better
wording.
- Description for command line option --show-fail-traces should be probably
renamed to --show-failed-traces (or simply --show-failed). The sentence should
start with capital letter anyway.
- Fix indentation of function af_instrument.

I will post my findings about using tool in a separate reply.

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

[KBibTeX] [Bug 397027] Sciencedirect search broken

[Volker Fröhlich]

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

--- Comment #1 from Volker Fröhlich  ---
https://dev.elsevier.com/user/login -- Maybe using their proper API is more
useful though.

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

[KBibTeX] [Bug 397027] New: Sciencedirect search broken

[Volker Fröhlich]

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

Bug ID: 397027
   Summary: Sciencedirect search broken
   Product: KBibTeX
   Version: 0.7
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Network/online search
  Assignee: fisc...@unix-ag.uni-kl.de
  Reporter: volke...@gmx.at
  Target Milestone: ---

Searching sciencedirect doesn't work, most likely because of changes on their
website. At first I thought that changing everything to https might be enough,
but unfortunately the search form changed too. 

kbibtex(29247) OnlineSearchAbstract::handleErrors: Search using "ScienceDirect"
failed (error code 301 ( "Protocol "" is unknown" ), HTTP code 0 : "" )

As far as I could see, nothing has changed in this area recently, so it's most
likely broken in 0.8 too.

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

[kwin] [Bug 396585] Kwin Options dialog (Wayland) not responding

[Panos]

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

--- Comment #5 from Panos  ---
Fedora Linux 28

[panos@deimos ~]$ gdb -ex=r --args kcmshell5 kwindecoration kwinactions
kwinfocus kwinmoving kwinadvanced kwinrules kwincompositing kwineffects
kwintabbox kwinscreenedges kwinscripts
GNU gdb (GDB) Fedora 8.1-25.fc28
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from kcmshell5...Reading symbols from
/usr/lib/debug/usr/bin/kcmshell5-5.13.3-2.fc28.x86_64.debug...done.
done.
Starting program: /usr/bin/kcmshell5 kwindecoration kwinactions kwinfocus
kwinmoving kwinadvanced kwinrules kwincompositing kwineffects kwintabbox
kwinscreenedges kwinscripts
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7fffd6790700 (LWP 3865)]
[New Thread 0x7fffcd589700 (LWP 3867)]
Calling KPluginInfo::property("X-KDE-PluginInfo-Name") is deprecated, use
KPluginInfo::pluginName() in
"/usr/lib64/qt5/plugins/org.kde.kdecoration2/breezedecoration.so" instead.
file:///usr/share/kwin/kcm_kwindecoration/Previews.qml:36: ReferenceError:
savedIndex is not defined
file:///usr/share/kwin/kcm_kwindecoration/Buttons.qml:143: ReferenceError:
iconLabel is not defined
[New Thread 0x7fffc16b6700 (LWP 3869)]
org.kde.kcoreaddons: Expected JSON property "X-KWin-Border-Activate" to be a
single string. but it is a bool
org.kde.kcoreaddons: Expected JSON property "X-KWin-Exclude-Listing" to be a
single string. but it is a bool
file:///usr/share/kwin/kcm_kwindecoration/Previews.qml:36: ReferenceError:
savedIndex is not defined
Calling KPluginInfo::property("X-KDE-PluginInfo-Name") is deprecated, use
KPluginInfo::pluginName() in
"/usr/lib64/qt5/plugins/org.kde.kdecoration2/breezedecoration.so" instead.
file:///usr/share/kwin/kcm_kwindecoration/Buttons.qml:143: ReferenceError:
iconLabel is not defined
[New Thread 0x7fffba351700 (LWP 3870)]
Calling KPluginInfo::property("X-KDE-PluginInfo-Name") is deprecated, use
KPluginInfo::pluginName() in
"/usr/lib64/qt5/plugins/org.kde.kdecoration2/breezedecoration.so" instead.
[New Thread 0x7fffb6146700 (LWP 3871)]
Module 'org.kde.kwin.decoration' does not contain a module identifier directive
- it cannot be protected from external registrations.
wl_display@1: error 0: invalid object 84
The Wayland connection experienced a fatal error (Μη έγκυρη παράμετρος)
[Thread 0x7fffb6146700 (LWP 3871) exited]
[Thread 0x7fffd6790700 (LWP 3865) exited]
[Thread 0x7fffc16b6700 (LWP 3869) exited]
[Thread 0x7fffcd589700 (LWP 3867) exited]
[Thread 0x7fffe582d940 (LWP 3854) exited]
[Inferior 1 (process 3854) exited with code 01]
(gdb) 

(again without kwindecoration it's working properly)

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

[plasmashell] [Bug 355258] plasmashell is preventing systemd automount shares from idle unmounting

[Maciej Stanczew]

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

Maciej Stanczew  changed:

   What|Removed |Added

 CC||maciej.stancze...@gmail.com

--- Comment #22 from Maciej Stanczew  ---
I experience a similar issue. I have three NFS mounts in fstab, with option
"x-systemd.automount" set (so they should only be mounted when something tries
accessing corresponding directories). After system boot none of the three
shares is mounted, but then when one is mounted on demand, plasmashell triggers
the mount of other two shares:

Jul 31 22:41:05 hostname systemd[1]: n-media.automount: Got automount request
for /n/media, triggered by 669 (mpd)
Jul 31 22:41:05 hostname systemd[1]: Mounting /n/media...
Jul 31 22:41:05 hostname systemd[1]: Mounted /n/media.
Jul 31 22:41:05 hostname systemd[1]: n-pacman.automount: Got automount request
for /n/pacman, triggered by 518 (plasmashell)
Jul 31 22:41:05 hostname systemd[1]: Mounting /n/pacman...
Jul 31 22:41:05 hostname systemd[1]: Mounted /n/pacman.
Jul 31 22:41:05 hostname systemd[1]: n-backup.automount: Got automount request
for /n/backup, triggered by 518 (plasmashell)
Jul 31 22:41:05 hostname systemd[1]: Mounting /n/backup...
Jul 31 22:41:05 hostname systemd[1]: Mounted /n/backup.

As in original description, it's not possible to unmount any of the shares:

Jul 31 22:44:14 hostname systemd[1]: Unmounting /n/backup...
Jul 31 22:44:14 hostname systemd[1]: n-backup.automount: Got automount request
for /n/backup, triggered by 518 (plasmashell)
Jul 31 22:44:14 hostname systemd[1]: Mounting /n/backup...
Jul 31 22:44:15 hostname systemd[1]: Mounted /n/backup.

This only happens with Device Notifier applet active -- without it, everything
works correctly.

The patch from comment #15 fixes both of above issues -- plasmashell no longer
triggers any unwanted mounts in those scenarios.

Regarding simultaneous unmount (as described in comment #16): manually running
umount with multiple targets always works (all shares are properly unmounted).
It's only when doing this from systemd that sometimes shares are remounted by
plasmashell:

# systemctl stop n-backup.mount n-media.mount n-pacman.mount
Job for n-media.mount canceled.

Jul 31 23:02:53 hostname systemd[1]: Unmounting /n/backup...
Jul 31 23:02:53 hostname systemd[1]: Unmounting /n/media...
Jul 31 23:02:53 hostname systemd[1]: Unmounting /n/pacman...
Jul 31 23:02:53 hostname systemd[1]: n-media.automount: Got automount request
for /n/media, triggered by 508 (plasmashell)
Jul 31 23:02:53 hostname systemd[1]: Unmounted /n/backup.
Jul 31 23:02:53 hostname systemd[1]: Mounting /n/media...
Jul 31 23:02:53 hostname systemd[1]: Unmounted /n/pacman.
Jul 31 23:02:53 hostname systemd[1]: Mounted /n/media.

Still, could the patch from comment #15 be merged regardless of this remaining
issue? In my case the patch only improves the behavior, as it eliminates almost
all of unwanted mounts (leaving only a specific corner-case that is
simultaneous unmounting).

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

[valgrind] [Bug 396290] [PATCH] Possible tool - allocfail

[Philippe Waroquiers]

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

--- Comment #12 from Philippe Waroquiers  ---
((In reply to Philippe Waroquiers from comment #11)
> Yes, I agree that having a way to exercise the error recovery/handling
> patch of an application is a very good thing to do.
Remove 'patch of' in the above :)

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

[valgrind] [Bug 396290] [PATCH] Possible tool - allocfail

[Philippe Waroquiers]

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

--- Comment #11 from Philippe Waroquiers  ---
Yes, I agree that having a way to exercise the error recovery/handling
patch of an application is a very good thing to do.

IMO, it is very late now to add this, even as an exp tool.
A.o. we better discuss the desired functionality somewhat more
(e.g. to make a more general/flexible way to make various things fail
in a single 'framework/tool').

For big/huge applications, we might need a lot more control about
e.g. when to start failing (maybe something like what is available
in callgrind:   let the tool start doing something once a call to a function
has been detected, or once a certain stacktrace has been detected
etc ...

In summary: the tool as it is now is too minimal and too 'young'.

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

[valgrind] [Bug 396290] [PATCH] Possible tool - allocfail

[Ivo Raisr]

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

--- Comment #10 from Ivo Raisr  ---
(In reply to Philippe Waroquiers from comment #9)
> I am wondering also how much difficult it would be to somewhat more
> generalise the tool.
> 
> For example, we might want to make similar tests to check failing syscalls.

Injecting failures in general is a very good topic. However given the imminent
Valgrind release, we should decide if this exp-tool can make it for 3.14 in its
current shape (and with some regtests available) or not. This decision
eventually drives the scope...

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

[kmymoney] [Bug 397026] New: No icon in the panel on xfce

[antoine]

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

Bug ID: 397026
   Summary: No icon in the panel on xfce
   Product: kmymoney
   Version: 5.0.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kmymoney-de...@kde.org
  Reporter: toitoine...@laposte.net
  Target Milestone: ---

Created attachment 114238
  --> https://bugs.kde.org/attachment.cgi?id=114238=edit
no icon int xfce panel

Hi,

I noticed that the icon of kmymoney does not appear on the xfce panel (see
attachment)

to reproduced the bug
1> start kmy
2> look at the panel

xubuntu 18.04
antoine@Frankenstein:~$ apt show kmymoney
Package: kmymoney
Version: 5.0.1-2
Priority: optional
Section: universe/kde
Origin: Ubuntu
Maintainer: Ubuntu Developers 
Original-Maint

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

[kmymoney] [Bug 397026] No icon in the panel on xfce

[antoine]

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

antoine  changed:

   What|Removed |Added

   Platform|Other   |Ubuntu Packages

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

[kmymoney] [Bug 397024] Wrong date choice when a schedule transaction is recognised

[antoine]

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

antoine  changed:

   What|Removed |Added

   Platform|Other   |Ubuntu Packages

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

[kmymoney] [Bug 397022] kmy do not recognise my schedule transaction when I import a qif file

[antoine]

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

antoine  changed:

   What|Removed |Added

   Platform|Other   |Ubuntu Packages

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

[kmymoney] [Bug 397025] Kmymoney version in help menu, splash screen and apt are different

[antoine]

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

antoine  changed:

   What|Removed |Added

   Platform|Other   |Ubuntu Packages

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

[kmymoney] [Bug 397025] New: Kmymoney version in help menu, splash screen and apt are different

[antoine]

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

Bug ID: 397025
   Summary: Kmymoney version in help menu, splash screen and apt
are different
   Product: kmymoney
   Version: 5.0.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kmymoney-de...@kde.org
  Reporter: toitoine...@laposte.net
  Target Milestone: ---

Hi,

I noticed that the kmymoney version are not consistent on xubuntu 18.04

Splash screen > 5.0.0
Help Menu > 5.0.0
apt > 5.0.1-2

to reproduce the bug
1> install kmy in *ubuntu
2> start kmy 
3> look at the splash screen and help menu
4> compare to apt information

antoine@Frankenstein:~$ apt show kmymoney
Package: kmymoney
Version: 5.0.1-2
Priority: optional
Section: universe/kde
Origin: Ubuntu
Maintainer: Ubuntu Developers 
Original-Maintainer: Debian KDE Extras Team


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

[kmymoney] [Bug 397024] New: Wrong date choice when a schedule transaction is recognised

[antoine]

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

Bug ID: 397024
   Summary: Wrong date choice when a schedule transaction is
recognised
   Product: kmymoney
   Version: 5.0.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kmymoney-de...@kde.org
  Reporter: toitoine...@laposte.net
  Target Milestone: ---

Hi,

I noticed some changes since I moved from kmy 4.6 to 5.0, especially when I
import transaction from a qif file.
As usual, kmy recognises a transaction , then it offers me the possibility to
accept or not this recognition

First, when I refuse a recognition, kmy stop to look at the other transactions
in the .qif for another recognition

Second, once in the ledger, I can valid a transaction recognition, when the
date of real transaction (imported) and the schedule transaction are different,
the validation of the recognition set the date of the transaction equals to the
date of the scheduled transaction, not the real, this behavior is not logical
in my opinion

xubuntu 18.04
antoine@Frankenstein:~$ apt show kmymoney
Package: kmymoney
Version: 5.0.1-2
Priority: optional
Section: universe/kde
Origin: Ubuntu
Maintainer: Ubuntu Developers 
Original-Maintainer: Debian KDE Extras Team


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

[kmymoney] [Bug 397023] New: Default color of imported transaction in the ledger

[antoine]

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

Bug ID: 397023
   Summary: Default color of imported transaction in the ledger
   Product: kmymoney
   Version: 5.0.1
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kmymoney-de...@kde.org
  Reporter: toitoine...@laposte.net
  Target Milestone: ---

Hi,

in kmy 5.0, the default color of imported transactions in the ledger is now
"dark brown" and it is really difficult to see the text
I had to change this in the preferences but I think that this color is not a
good choice for a default choice

To reproduce the bug:
1> open a file in kmy
2> import transaction with a qif file
3> look at the ledger

xubuntu 18.04
antoine@Frankenstein:~$ apt show kmymoney
Package: kmymoney
Version: 5.0.1-2
Priority: optional
Section: universe/kde
Origin: Ubuntu
Maintainer: Ubuntu Developers 
Original-Maintainer: Debian KDE Extras Team


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

[kmymoney] [Bug 397022] New: kmy do not recognise my schedule transaction when I import a qif file

[antoine]

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

Bug ID: 397022
   Summary: kmy do not recognise my schedule transaction when I
import a qif file
   Product: kmymoney
   Version: 5.0.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: importer
  Assignee: kmymoney-de...@kde.org
  Reporter: toitoine...@laposte.net
  Target Milestone: ---

Hi,

I switch from ubuntu 16.04/kmymoney 4.6 to xubuntu18.04/kmymoney5.0 in may and
I think that this new version has some bugs

I import all my transactions into kmy every month from my bank
I have about 10 schedule transaction every month and I feel that the
transactions recognition is not as efficient as it was before

I don't know how to give more details about this situation


antoine@Frankenstein:~$ apt show kmymoney
Package: kmymoney
Version: 5.0.1-2
Priority: optional
Section: universe/kde
Origin: Ubuntu
Maintainer: Ubuntu Developers 
Original-Maintainer: Debian KDE Extras Team


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

[kmymoney] [Bug 397021] New: Net worth does not appear

[antoine]

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

Bug ID: 397021
   Summary: Net worth does not appear
   Product: kmymoney
   Version: 5.0.1
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kmymoney-de...@kde.org
  Reporter: toitoine...@laposte.net
  Target Milestone: ---

Created attachment 114237
  --> https://bugs.kde.org/attachment.cgi?id=114237=edit
net worth does not appear

Hi,

I am using kmy 5.0.1 on xubuntu 18.04.
I noticed that net worth does not appear on the  accounts, institutions,
categories views. (see attachment)

antoine@Frankenstein:~$ apt show kmymoney
Package: kmymoney
Version: 5.0.1-2
Priority: optional
Section: universe/kde
Origin: Ubuntu
Maintainer: Ubuntu Developers 
Original-Maintainer: Debian KDE Extras Team


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

[kmymoney] [Bug 397020] New: Opening dates in "all dates" plot

[antoine]

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

Bug ID: 397020
   Summary: Opening dates in "all dates" plot
   Product: kmymoney
   Version: 5.0.1
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: reports
  Assignee: kmymoney-de...@kde.org
  Reporter: toitoine...@laposte.net
  Target Milestone: ---

Created attachment 114236
  --> https://bugs.kde.org/attachment.cgi?id=114236=edit
opening date graph

Hi,

I am running kmy 5.0.1 on xubuntu 18.04 and I think I found a small bug in kmy.

When I plot graph with the on "all date" interval, it works but there is the
opening balance plotted at the beginning and in my opinion, it is not the right
behavior. (see attachment)

To reproduce the bug :
1> open a file with kmy
2> in the report view, choose a report and plot it on a "all date" interval

antoine@Frankenstein:~$ apt show kmymoney
Package: kmymoney
Version: 5.0.1-2
Priority: optional
Section: universe/kde

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

[digikam] [Bug 91562] Change order of pictures in the virtual album manually

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 Resolution|--- |FIXED
   Version Fixed In||6.0.0
  Latest Commit||https://commits.kde.org/dig
   ||ikam/ff2415c06095c98a439f88
   ||6002bb6df824c12db9
 Status|CONFIRMED   |RESOLVED

--- Comment #41 from Maik Qualmann  ---
Git commit ff2415c06095c98a439f886002bb6df824c12db9 by Maik Qualmann.
Committed on 31/07/2018 at 20:11.
Pushed by mqualmann into branch 'master'.

use CoreDbOperationGroup
FIXED-IN: 6.0.0

M  +2-1NEWS
M  +7-1core/app/items/digikamimageview.cpp

https://commits.kde.org/digikam/ff2415c06095c98a439f886002bb6df824c12db9

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

[plasmashell] [Bug 397019] New: [Kubuntu 18.04] wrong ISO file icon display on Folder View widgets

[bugzilla_noreply]

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

Bug ID: 397019
   Summary: [Kubuntu 18.04] wrong ISO file icon display on Folder
View widgets
   Product: plasmashell
   Version: master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Widget Explorer
  Assignee: plasma-b...@kde.org
  Reporter: delt...@free.fr
  Target Milestone: 1.0

Created attachment 114235
  --> https://bugs.kde.org/attachment.cgi?id=114235=edit
Desktop Screenshot

Hi,

In Kubuntu 18.04, from live USB key or after fresh install, there is a problem
with Folder View widgets.

If you add a Folder View widgets on the desktop, and try to display a folder
with ISO files, default ISO file icon not always display, depending of type of
ISO files.

In attachement, you can see the bug with 3 type of .ISO extension files :
- icon is the good ISO icon for Linux ISO files.
- icon is TXT icon for gparted ISO file.
- there is non icon for MS Windows ISO files.

You can easyly test this issue with live USB key of Kubuntu 18.04.

Regards,

Sam.

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

[valgrind] [Bug 396290] [PATCH] Possible tool - allocfail

[Philippe Waroquiers]

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

--- Comment #9 from Philippe Waroquiers  ---
I am wondering also how much difficult it would be to somewhat more
generalise the tool.

For example, we might want to make similar tests to check failing syscalls.

A part of the tool can then be re-used (e.g. storing/loading the
stack traces etc ...).

We then would need some more command line options to control what
to make fail.

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

[digikam] [Bug 91562] Change order of pictures in the virtual album manually

[Maik Qualmann]

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

--- Comment #40 from Maik Qualmann  ---
Git commit c6e92a02cfeebc86b60faad9442e780a7342abbf by Maik Qualmann.
Committed on 31/07/2018 at 19:46.
Pushed by mqualmann into branch 'master'.

fix and optimize manual sorting

M  +21   -13   core/app/items/digikamimageview.cpp
M  +0-2core/libs/database/coredb/coredb.cpp
M  +14   -2core/libs/database/item/imageinfo.cpp
M  +1-1core/libs/database/item/imageinfo.h
M  +1-1core/libs/database/item/imageinfodata.h

https://commits.kde.org/digikam/c6e92a02cfeebc86b60faad9442e780a7342abbf

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

[skrooge] [Bug 397018] New: Cannot open file - password requested

[Chris Prior]

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

Bug ID: 397018
   Summary: Cannot open file - password requested
   Product: skrooge
   Version: unspecified
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: guillaume.deb...@gmail.com
  Reporter: cmpr...@gmail.com
CC: steph...@mankowski.fr
  Target Milestone: ---

I have skrooge 2.13.0, qt 5.9.6 (but skrooge says built against 5.9.4), kde
frameworks 5.46.0

I use 2 databases - one opens perfectly. The other, that was last saved on 22
June (before the qt 5.9.6 update) requests a password to open the file. I do
not remember setting a password for this file. I have tried to open the backup
(from the same date) and also a previous version of the file last saved in Feb
2018. None of these will open. Is there any way of attempting to recover these
files?

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

[latte-dock] [Bug 397017] New: Activities and application groups in latte-dock

[bugzilla_noreply]

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

Bug ID: 397017
   Summary: Activities and application groups in latte-dock
   Product: latte-dock
   Version: git (master)
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: plasmoid
  Assignee: mvourla...@gmail.com
  Reporter: dalto...@routenetwork.net
  Target Milestone: ---

When using multiple activities and you have “Show only tasks from the current
activity” unchecked and “Group tasks of the same application” checked nothing
happens when you click on a group if it is not in the current activity. If it
is a single instance, it switches to the activity and activates the window.
When it is multiple instances it does nothing apparent.

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

[kde] [Bug 397016] Dolphin doesn't ask for root password when creating links of files

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

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

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


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

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

[frameworks-kio] [Bug 179678] KIO needs PolicyKit-kde integration

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||david.cortes.rivera@gmail.c
   ||om

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

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

[kde] [Bug 397016] New: Dolphin doesn't ask for root password when creating links of files

[David]

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

Bug ID: 397016
   Summary: Dolphin doesn't ask for root password when creating
links of files
   Product: kde
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: david.cortes.riv...@gmail.com
  Target Milestone: ---

When trying to create a symlink between folders that require root access,
Dolphin would not ask for the root password before performing the operation -
instead, it will simply fail due to lack of permissions.

Steps to reproduce:
* Open two folders in which the user doesn't have write permissions (e.g.
/usr/lib/chromium-browser/ and /opt/google/chrome/).
* Drag and drop some file from one of the folders above to the other.
* When it asks what to do with it, select "Link here".

Expected behavior:
* Should ask for root password and create a link.

Actual behavior:
* Fails due to permissions

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

[khelpcenter] [Bug 397015] khelpcenter will not install for Marble handbook Refer bug 313266

[Luigi Toscano]

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

--- Comment #2 from Luigi Toscano  ---
The other bug is unrelated, and the logs that you pasted there, which should
have been pasted here, shows that you have a mix of repositories from different
versions of Mageia which are probably causing also other issues.

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

[khelpcenter] [Bug 397015] khelpcenter will not install for Marble handbook Refer bug 313266

[Luigi Toscano]

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

Luigi Toscano  changed:

   What|Removed |Added

 CC||luigi.tosc...@tiscali.it
 Resolution|UPSTREAM|DOWNSTREAM

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

[khelpcenter] [Bug 397015] khelpcenter will not install for Marble handbook Refer bug 313266

[Yuri Chornoivan]

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

Yuri Chornoivan  changed:

   What|Removed |Added

 Resolution|--- |UPSTREAM
 CC||yurc...@ukr.net
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Yuri Chornoivan  ---
It is a packaging issue that should be reported here:

https://bugs.mageia.org/

Thanks for your patience and sorry for inconveniences. KDE developers cannot do
much in this case.

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

[kile] [Bug 313266] Can't find Kile Handbook; error says "Could not launch the KDE Help Center: Could not find service 'khelpcenter'."

[Luigi Toscano]

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

Luigi Toscano  changed:

   What|Removed |Added

 CC||luigi.tosc...@tiscali.it

--- Comment #4 from Luigi Toscano  ---
(In reply to Chris from comment #3)
> This is not Ubuntu specific.  I installed Marble from the Mageia 6 Control
> Center.  Then the Kwallet warning came up on passwords, but Marble activated
> anyway. Checked No and started using it. Clicking on the Help > Marble
> Virtual Globe Handbook got me the same error. Maybe not installed at all. 
> Check MCC.  Bingo.  So, install it.  And got this;
> 

This was indeed Ubuntu specific, and it referred anyway to an old version of
khelpcenter (Qt4 based, now it's Qt 5).

The log that you show is also about a problem with the repositories of your
distribution.

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

[dolphin] [Bug 377663] Dolphin crashes when trying to open built-in terminal properties.

[Fisiu]

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

Fisiu  changed:

   What|Removed |Added

 CC||fisi...@gmail.com
 Resolution|BACKTRACE   |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #3 from Fisiu  ---
It seems dolphin doesn't crash anymore with built-in terminal.

Confirmed with version 18.04.3 using:
Qt: 5.11.1
KDE Frameworks: 5.48.0

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

[khelpcenter] [Bug 397015] New: khelpcenter will not install for Marble handbook Refer bug 313266

[Chris]

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

Bug ID: 397015
   Summary: khelpcenter will not install for Marble handbook
Refer bug 313266
   Product: khelpcenter
   Version: unspecified
  Platform: Mageia RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kde-doc-engl...@kde.org
  Reporter: krakke...@gmail.com
  Target Milestone: ---

Created attachment 114234
  --> https://bugs.kde.org/attachment.cgi?id=114234=edit
Mageia 6 Control Center Software installation dialog.

I mistakenly added a comment on a bug under an installation of Kile.  Bug
number 313266.  The attachment shows detail for khelpcenter on my laptop.  The
orange arrows say it is installed but the bug is still there.

I included the MCC error message on non-installation and an lspcidrake -v

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

[kile] [Bug 313266] Can't find Kile Handbook; error says "Could not launch the KDE Help Center: Could not find service 'khelpcenter'."

[Chris]

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

Chris  changed:

   What|Removed |Added

 CC||krakke...@gmail.com

--- Comment #3 from Chris  ---
This is not Ubuntu specific.  I installed Marble from the Mageia 6 Control
Center.  Then the Kwallet warning came up on passwords, but Marble activated
anyway. Checked No and started using it. Clicking on the Help > Marble Virtual
Globe Handbook got me the same error. Maybe not installed at all.  Check MCC. 
Bingo.  So, install it.  And got this;

1 installation transactions failed

There was a problem during the installation:

file /usr/share/icons/hicolor/128x128/apps/akonadi.png from install of
oxygen-icon-theme-1:4.14.3-3.mga5.noarch conflicts with file from package
akonadi-1:17.12.2-1.mga6.x86_64

file /usr/share/icons/hicolor/16x16/apps/akonadi.png from install of
oxygen-icon-theme-1:4.14.3-3.mga5.noarch conflicts with file from package
akonadi-1:17.12.2-1.mga6.x86_64

file /usr/share/icons/hicolor/32x32/apps/akonadi.png from install of
oxygen-icon-theme-1:4.14.3-3.mga5.noarch conflicts with file from package
akonadi-1:17.12.2-1.mga6.x86_64

file /usr/share/icons/hicolor/48x48/apps/akonadi.png from install of
oxygen-icon-theme-1:4.14.3-3.mga5.noarch conflicts with file from package
akonadi-1:17.12.2-1.mga6.x86_64

More detail;
[root@localhost Marble]# lspcidrake -v
snd_hda_intel   : Intel Corporation|7 Series/C216 Chipset Family High
Definition Audio Controller [MULTIMEDIA_AUDIO_DEV] (vendor:8086 device:1e20
subv:17aa subd:3977) (rev: 04)
alx : Qualcomm Atheros|AR8162 Fast Ethernet [NETWORK_ETHERNET]
(vendor:1969 device:1090 subv:17aa subd:3979) (rev: 10)
mei_me  : Intel Corporation|7 Series/C216 Chipset Family MEI Controller
#1 [COMMUNICATION_OTHER] (vendor:8086 device:1e3a subv:17aa subd:3977) (rev:
04)
ath9k   : Qualcomm Atheros|AR9485 Wireless Network Adapter
[NETWORK_OTHER] (vendor:168c device:0032 subv:17aa subd:3218) (rev: 01)
lpc_ich : Intel Corporation|HM76 Express Chipset LPC Controller
[BRIDGE_ISA] (vendor:8086 device:1e59 subv:17aa subd:3977) (rev: 04)
shpchp  : Intel Corporation|7 Series/C216 Chipset Family PCI Express
Root Port 1 [BRIDGE_PCI] (vendor:8086 device:1e10) (rev: c4)
unknown : Intel Corporation|7 Series Chipset Family 6-port SATA
Controller [AHCI mode] [STORAGE_SATA] (vendor:8086 device:1e03 subv:17aa
subd:3977) (rev: 04)
xhci_pci: Intel Corporation|7 Series/C210 Series Chipset Family USB
xHCI Host Controller [SERIAL_USB] (vendor:8086 device:1e31 subv:17aa subd:3977)
(rev: 04)
Card:Intel 810 and later: Intel Corporation|2nd Generation Core Processor
Family Integrated Graphics Controller [DISPLAY_VGA] (vendor:8086 device:0116
subv:17aa subd:3977) (rev: 09)
ehci_pci: Intel Corporation|7 Series/C216 Chipset Family USB Enhanced
Host Controller #1 [SERIAL_USB] (vendor:8086 device:1e26 subv:17aa subd:3977)
(rev: 04)
ehci_pci: Intel Corporation|7 Series/C216 Chipset Family USB Enhanced
Host Controller #2 [SERIAL_USB] (vendor:8086 device:1e2d subv:17aa subd:3977)
(rev: 04)
shpchp  : Intel Corporation|7 Series/C210 Series Chipset Family PCI
Express Root Port 2 [BRIDGE_PCI] (vendor:8086 device:1e12) (rev: c4)
unknown : Intel Corporation|2nd Generation Core Processor Family DRAM
Controller [BRIDGE_HOST] (vendor:8086 device:0104 subv:17aa subd:3977) (rev:
09)
i2c_i801: Intel Corporation|7 Series/C216 Chipset Family SMBus
Controller [SERIAL_SMBUS] (vendor:8086 device:1e22 subv:17aa subd:3977) (rev:
04)
hub : Linux 4.14.50-desktop-2.mga6 ehci_hcd|EHCI Host Controller
[Hub|Unused|Full speed (or root) hub] (vendor:1d6b device:0002)
hub : Intel Corp.|Integrated Rate Matching Hub [Hub|Unused|Full
speed (or root) hub] (vendor:8087 device:0024)
hub : VIA Labs, Inc. |USB2.0 Hub 
[Hub|Unused|Full speed (or root) hub] (vendor:2109 device:2811)
hub : VIA Labs, Inc. |USB2.0 Hub 
[Hub|Unused|Full speed (or root) hub] (vendor:2109 device:2811)
usb_storage : Seagate |Expansion [Mass Storage|SCSI|Bulk-Only] (vendor:0bc2
device:2312)
usb_storage : Seagate |Expansion [Mass Storage|SCSI|Bulk-Only] (vendor:0bc2
device:2312)
unknown : Canon|CanoScan (vendor:04a9 device:2220)
unknown : MediaTek|Lenovo (vendor:17ef device:789a)
btusb   : Atheros Communications|Bluetooth USB Host Controller
[Wireless|Radio Frequency|Bluetooth] (vendor:0cf3 device:3004)
rtsx_usb: Generic|USB2.0-CRW (vendor:0bda device:0129)
hub : Linux 4.14.50-desktop-2.mga6 ehci_hcd|EHCI Host Controller
[Hub|Unused|Full speed (or root) hub] (vendor:1d6b device:0002)
hub : Intel Corp.|Integrated Rate Matching Hub [Hub|Unused|Full
speed (or root) hub] (vendor:8087 device:0024)
hub : Linux 

[digikam] [Bug 397001] The "maximise" button is missing in decoration of the geolocation editor window

[Milan Knížek]

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

Milan Knížek  changed:

   What|Removed |Added

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

--- Comment #3 from Milan Knížek  ---
That guy had a problem with Cinnamon, which may not be the same as standard
GNOME.

I have gnome-tweaks installed, disabled "attach modal dialogs" (so that the
dialog window moves separately from the parent window), enabled Maximise and
Minimise buttons for the title bar already.

That said, Tweaks do not seem to offer a solution for me.

You are right, that GNOME treats Geolocation Editor as a dialog window (in
Alt+Tab switcher, I can see both digikam and editor as a single icon).
Right-clicking on Editor's title bar shows both Maximise and Minimise greyed
out (disabled), double click does not maximise the window. Note that the window
has a title bar and the close button.

I searched a bit more, but no resolution yet. This one suggests that Mac OS
might deal with modal windows similarly like GNOME does:
https://musescore.org/en/node/56931

P.S. Re-opening the bug if you do not mind.

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

[kde] [Bug 211416] Optimise kde performance on nfs

[Rex Dieter]

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

Rex Dieter  changed:

   What|Removed |Added

 CC|rdie...@gmail.com   |

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

[kde] [Bug 211416] Optimise kde performance on nfs

[Murz]

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

--- Comment #22 from Murz  ---
And here
http://people.skolelinux.org/pere/blog/Why_the_KDE_menu_is_slow_when__usr__is_NFS_mounted___and_a_workaround.html
is article with more detailed description of problem.

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

[KScreen] [Bug 395714] Display switch shows no icons

[Frederik Gladhorn]

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

--- Comment #1 from Frederik Gladhorn  ---
https://phabricator.kde.org/D14514 fixes this

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

[kde] [Bug 211416] Optimise kde performance on nfs

[Murz]

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

--- Comment #21 from Murz  ---
Lubos Dolezel, does workaround with symlinking missed icons, described in
https://bugs.kde.org/show_bug.cgi?id=211416#c16 increase login performance in
KDE5 on NFS share?

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

[KScreen] [Bug 395714] Display switch shows no icons

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org

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

[kdebugsettings] [Bug 396959] Adding support for also having the (known to be used) identifier in the database

[Laurent Montel]

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

--- Comment #5 from Laurent Montel  ---
categories file is not autogenerated.
I don't have idea how to make support in old kdebugsettings version.

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

[frameworks-kcoreaddons] [Bug 397008] KFormat::formatDuration returns different results with ms large

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

   Keywords||junior-jobs
 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #1 from Christoph Feck  ---
Currently uses qRound, which returns int, but either should use qRound64 (and
double instead of qreal), or just use int arithmetic for rounding, e.g. ((x +
50) / 100) * 100 will round to multiple of 100.

https://cgit.kde.org/kcoreaddons.git/tree/src/lib/util/kformatprivate.cpp#n332

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

[plasmashell] [Bug 349289] Crash in Plotter::render

[Kai Uwe Broulik]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

 CC||achrisl...@gmail.com

--- Comment #26 from Kai Uwe Broulik  ---
*** Bug 397013 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 397013] plasma crashed when added new monitors

[Kai Uwe Broulik]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

 CC||k...@privat.broulik.de
 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Kai Uwe Broulik  ---


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

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

[konsole] [Bug 397014] New: Konsole crashed when switching tabs

[Alex Fiestas]

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

Bug ID: 397014
   Summary: Konsole crashed when switching tabs
   Product: konsole
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: afies...@kde.org
  Target Milestone: ---

Application: konsole (18.11.70)
 (Compiled from sources)
Qt Version: 5.11.1
Frameworks Version: 5.48.0
Operating System: Linux 4.17.10-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

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

I was switching tabs using the shortcuts and after a few hours using konsole it
crashed.

This has happened before.

The crash can be reproduced sometimes.

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

Thread 3 (Thread 0x7f8b5b9e5700 (LWP 7296)):
#0  0x7f8b77683ffc in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f8b606c1124 in ?? () from /usr/lib/dri/i965_dri.so
#2  0x7f8b606c0e18 in ?? () from /usr/lib/dri/i965_dri.so
#3  0x7f8b7767e075 in start_thread () from /usr/lib/libpthread.so.0
#4  0x7f8b7905553f in clone () from /usr/lib/libc.so.6

Thread 2 (Thread 0x7f8b63534700 (LWP 7295)):
#0  0x7f8b7904afa6 in ppoll () from /usr/lib/libc.so.6
#1  0x7f8b79f09e19 in qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7f8b5c00f988)
at /home/afiestas/Projects/qt5/qtbase/src/corelib/kernel/qcore_unix.cpp:133
#2  qt_safe_poll (fds=0x7f8b5c00f988, nfds=nfds@entry=1,
timeout_ts=timeout_ts@entry=0x0) at
/home/afiestas/Projects/qt5/qtbase/src/corelib/kernel/qcore_unix.cpp:133
#3  0x7f8b79f0b289 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at ../../include/QtCore/../../../../qtbase/src/corelib/tools/qarraydata.h:209
#4  0x7f8b79ebab9b in
QEventLoop::exec(QFlags) () at
../../include/QtCore/../../../../qtbase/src/corelib/global/qflags.h:140
#5  0x7f8b79d09ae6 in QThread::exec() () at
../../include/QtCore/../../../../qtbase/src/corelib/global/qflags.h:120
#6  0x7f8b7ba5ba25 in QDBusConnectionManager::run (this=0x7f8b7bcd3d60
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
/home/afiestas/Projects/qt5/qtbase/src/dbus/qdbusconnection.cpp:178
#7  0x7f8b79d136b7 in QThreadPrivate::start(void*) () at
/home/afiestas/Projects/qt5/qtbase/src/corelib/thread/qthread_unix.cpp:367
#8  0x7f8b7767e075 in start_thread () from /usr/lib/libpthread.so.0
#9  0x7f8b7905553f in clone () from /usr/lib/libc.so.6

Thread 1 (Thread 0x7f8b810c3840 (LWP 7292)):
[KCrash Handler]
#6  0x7f8b809e7112 in std::__atomic_base::load
(__m=std::memory_order_relaxed, this=0x51) at
/usr/include/c++/8.1.1/bits/atomic_base.h:390
#7  QAtomicOps::load (_q_value=...) at
/opt/qt5/include/QtCore/qatomic_cxx11.h:227
#8  QBasicAtomicInteger::load (this=0x51) at
/opt/qt5/include/QtCore/qbasicatomic.h:103
#9  QtPrivate::RefCount::isShared (this=0x51) at
/opt/qt5/include/QtCore/qrefcount.h:101
#10 QVector::isDetached (this=0x5600597a52c8) at
/opt/qt5/include/QtCore/qvector.h:106
#11 QVector::detach (this=0x5600597a52c8) at
/opt/qt5/include/QtCore/qvector.h:383
#12 QVector::data (this=0x5600597a52c8) at
/opt/qt5/include/QtCore/qvector.h:127
#13 Konsole::Screen::copyLineToStream (this=this@entry=0x5600597dcfa0,
line=line@entry=40, start=0, count=172, count@entry=-1,
decoder=decoder@entry=0x7ffe9dd62b70, appendNewLine=appendNewLine@entry=true,
options=...) at /home/afiestas/Projects/kde5/source/konsole/src/Screen.cpp:1346
#14 0x7f8b809e74e1 in Konsole::Screen::writeToStream
(this=this@entry=0x5600597dcfa0, decoder=decoder@entry=0x7ffe9dd62b70,
startIndex=startIndex@entry=3677, endIndex=endIndex@entry=15530, options=...)
at /home/afiestas/Projects/kde5/source/konsole/src/Screen.cpp:1270
#15 0x7f8b809e89c2 in Konsole::Screen::text (this=0x5600597dcfa0,
startIndex=3677, endIndex=15530, options=...) at
/home/afiestas/Projects/kde5/source/konsole/src/Screen.cpp:1226
#16 0x7f8b809e8a66 in Konsole::Screen::selectedText (this=,
options=..., options@entry=...) at
/home/afiestas/Projects/kde5/source/konsole/src/Screen.cpp:1207
#17 0x7f8b809b5f9d in Konsole::Emulation::checkSelectedText
(this=0x5600597dc660) at /opt/qt5/include/QtCore/qflags.h:120
#18 0x7f8b79ee54d0 in QtPrivate::QSlotObjectBase::call (a=0x7ffe9dd62cf0,
r=0x5600597dc660, this=0x560059882d10) at
../../include/QtCore/../../../../qtbase/src/corelib/kernel/qobjectdefs_impl.h:376
#19 QMetaObject::activate(QObject*, int, int, void**) () at
/home/afiestas/Projects/qt5/qtbase/src/corelib/kernel/qobject.cpp:3754
#20 0x7f8b79ee5997 in QMetaObject::activate (sender=,
m=m@entry=0x7f8b80c86a40 ,

[kstars] [Bug 397010] Context menu hides after ~1 second in some cases (e.g. on objects below horizon)

[Christian Dersch]

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

--- Comment #1 from Christian Dersch  ---
Using reverted patch for Fedora downstream packaging until we have better
solution:
https://src.fedoraproject.org/rpms/kstars/blob/master/f/kstars-undo-a852d0c6edced5263a00361368222e8f3ed96eba.patch

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

[Discover] [Bug 397003] Big memory allocation if no backend is available

[Aleix Pol]

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

--- Comment #1 from Aleix Pol  ---
You seem to be loading the plugins on the system, not the ones you just
installed.

Also if you could do a heaptrack run that would maybe help detect where you're
hitting the OOM? I've never seen it before.

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

[systemsettings] [Bug 349673] kcm_fontinst: Backend crashes on systemwide fonts installations

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

   Version Fixed In||5.14.0

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

[plasmashell] [Bug 397013] New: plasma crashed when added new monitors

[Chris Long]

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

Bug ID: 397013
   Summary: plasma crashed when added new monitors
   Product: plasmashell
   Version: 5.8.9
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: achrisl...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.9)

Qt Version: 5.6.1
Frameworks Version: 5.36.0
Operating System: Linux 4.13.0-43-generic x86_64
Distribution: Ubuntu 16.04.5 LTS

-- Information about the crash:
- What I was doing when the application crashed:
I used the Displays system settings panel to enable and position external
monitors for my laptop after docking it. Normally it remembers, but maybe
because I rebooted while away from my desk it did not this time. Once I clicked
"Apply", the external monitors started displaying and for a second it all
seemed ok. But then plasma crashed.

I tried adding and removing monitors and changing the primary display but could
not reproduce the crash.

The crash does not seem to be reproducible.

-- Backtrace:
Application: Plasma (plasmashell), 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 0x7fe7ed29b900 (LWP 10367))]

Thread 23 (Thread 0x7fe7293fe700 (LWP 15209)):
[KCrash Handler]
#6  0x0018 in ?? ()
#7  0x7fe734b36ce9 in Plotter::render (this=0x2846450) at
/build/kdeclarative-gkCJW7/kdeclarative-5.36.0/src/qmlcontrols/kquickcontrolsaddons/plotter.cpp:648
#8  0x7fe7e8220c24 in QtPrivate::QSlotObjectBase::call (a=0x7fe7293fdad0,
r=0x2846450, this=) at
../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124
#9  QMetaObject::activate (sender=sender@entry=0xa959e0,
signalOffset=, local_signal_index=local_signal_index@entry=6,
argv=argv@entry=0x0) at kernel/qobject.cpp:3715
#10 0x7fe7e82211b7 in QMetaObject::activate (sender=sender@entry=0xa959e0,
m=m@entry=0x7fe7eb560040 ,
local_signal_index=local_signal_index@entry=6, argv=argv@entry=0x0) at
kernel/qobject.cpp:3595
#11 0x7fe7eb32b933 in QQuickWindow::beforeRendering
(this=this@entry=0xa959e0) at .moc/moc_qquickwindow.cpp:488
#12 0x7fe7eb32fdee in QQuickWindowPrivate::renderSceneGraph
(this=this@entry=0x5162a70, size=...) at items/qquickwindow.cpp:406
#13 0x7fe7eb301c9a in QSGRenderThread::syncAndRender
(this=this@entry=0xaa09b0) at scenegraph/qsgthreadedrenderloop.cpp:623
#14 0x7fe7eb30723c in QSGRenderThread::run (this=0xaa09b0) at
scenegraph/qsgthreadedrenderloop.cpp:704
#15 0x7fe7e801f808 in QThreadPrivate::start (arg=0xaa09b0) at
thread/qthread_unix.cpp:341
#16 0x7fe7e71036ba in start_thread (arg=0x7fe7293fe700) at
pthread_create.c:333
#17 0x7fe7e792d41d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 22 (Thread 0x7fe71ebfe700 (LWP 15208)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fe7e80206bb in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x1004ad0) at
thread/qwaitcondition_unix.cpp:136
#2  QWaitCondition::wait (this=this@entry=0xffb378, mutex=mutex@entry=0xffb370,
time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208
#3  0x7fe7eb306a8d in QSGRenderThreadEventQueue::takeEvent (wait=true,
this=0xffb368) at scenegraph/qsgthreadedrenderloop.cpp:236
#4  QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0xffb2f0) at
scenegraph/qsgthreadedrenderloop.cpp:684
#5  0x7fe7eb307365 in QSGRenderThread::run (this=0xffb2f0) at
scenegraph/qsgthreadedrenderloop.cpp:713
#6  0x7fe7e801f808 in QThreadPrivate::start (arg=0xffb2f0) at
thread/qthread_unix.cpp:341
#7  0x7fe7e71036ba in start_thread (arg=0x7fe71ebfe700) at
pthread_create.c:333
#8  0x7fe7e792d41d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 21 (Thread 0x7fe732e38700 (LWP 15207)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fe7e80206bb in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0xdfeb90) at
thread/qwaitcondition_unix.cpp:136
#2  QWaitCondition::wait (this=this@entry=0x630bd98,
mutex=mutex@entry=0x630bd90, time=time@entry=18446744073709551615) at
thread/qwaitcondition_unix.cpp:208
#3  0x7fe7eb306a8d in QSGRenderThreadEventQueue::takeEvent (wait=true,
this=0x630bd88) at scenegraph/qsgthreadedrenderloop.cpp:236
#4  QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x630bd10) at
scenegraph/qsgthreadedrenderloop.cpp:684
#5  0x7fe7eb307365 in QSGRenderThread::run (this=0x630bd10) at
scenegraph/qsgthreadedrenderloop.cpp:713
#6  

[kdebugsettings] [Bug 396959] Adding support for also having the (known to be used) identifier in the database

[Friedrich W . H . Kossebau]

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

--- Comment #4 from Friedrich W. H. Kossebau  ---
(In reply to Laurent Montel from comment #3)
> (In reply to Friedrich W. H. Kossebau from comment #2)
> > How backward compatible is this notations to older versions of
> > kdebugsettings?
> 
> If we use new notation with old kdebugsettings you will see "IDENTIFIER
> [foo;bar]" in description.
> 
> For sure it(s not supported.
> 
> > 
> > Challenge:
> > e.g. with KDevelop (thus not released in sync with "KDE Applications") how
> > can we know whether to install .catagories files with this notation?

So one would have to extend the buildsystem to set a flag whether to generate
those additional data or not. And decide the default based on what parsing the
output of "kdebugsettings -v" for version tag delivers. Any better
idea/recommendation?

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

[marble] [Bug 378885] Marble crashes sometime when using the vector map theme

[bugzilla_noreply]

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

--- Comment #9 from 2012g...@web.de ---
Created attachment 114231
  --> https://bugs.kde.org/attachment.cgi?id=114231=edit
New crash information added by DrKonqi

marble (2.2.20 (2.3 development version)) using Qt 5.11.1

- What I was doing when the application crashed:

Zooming while using the OSM vector theme.

-- Backtrace (Reduced):
#6  0x7f7f9790710b in QPixmap::size() const () at /usr/lib64/libQt5Gui.so.5
#7  0x7f7f9abc6808 in Marble::VisiblePlacemark::symbolRect() const
(this=this@entry=0x561c6df6ff20) at
/usr/src/debug/marble-18.04.3-1.1.x86_64/src/lib/marble/VisiblePlacemark.cpp:171
#8  0x7f7f9abc83c3 in Marble::PlacemarkLayout::hasPlacemarkAt(QPoint
const&) (this=0x561c6459bbf8, pos=...) at
/usr/include/qt5/QtCore/qarraydata.h:143
#9  0x7f7f9aadebf9 in Marble::PlacemarkLayer::hasPlacemarkAt(QPoint const&)
(this=, pos=...) at
/usr/src/debug/marble-18.04.3-1.1.x86_64/src/lib/marble/layers/PlacemarkLayer.cpp:218
#10 0x7f7f9ab176da in Marble::MarbleMap::hasFeatureAt(QPoint const&) const
(this=0x561c64573280, position=...) at
/usr/src/debug/marble-18.04.3-1.1.x86_64/src/lib/marble/MarbleMap.cpp:483

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

[marble] [Bug 378885] Marble crashes sometime when using the vector map theme

[bugzilla_noreply]

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

--- Comment #9 from 2012g...@web.de ---
Created attachment 114231
  --> https://bugs.kde.org/attachment.cgi?id=114231=edit
New crash information added by DrKonqi

marble (2.2.20 (2.3 development version)) using Qt 5.11.1

- What I was doing when the application crashed:

Zooming while using the OSM vector theme.

-- Backtrace (Reduced):
#6  0x7f7f9790710b in QPixmap::size() const () at /usr/lib64/libQt5Gui.so.5
#7  0x7f7f9abc6808 in Marble::VisiblePlacemark::symbolRect() const
(this=this@entry=0x561c6df6ff20) at
/usr/src/debug/marble-18.04.3-1.1.x86_64/src/lib/marble/VisiblePlacemark.cpp:171
#8  0x7f7f9abc83c3 in Marble::PlacemarkLayout::hasPlacemarkAt(QPoint
const&) (this=0x561c6459bbf8, pos=...) at
/usr/include/qt5/QtCore/qarraydata.h:143
#9  0x7f7f9aadebf9 in Marble::PlacemarkLayer::hasPlacemarkAt(QPoint const&)
(this=, pos=...) at
/usr/src/debug/marble-18.04.3-1.1.x86_64/src/lib/marble/layers/PlacemarkLayer.cpp:218
#10 0x7f7f9ab176da in Marble::MarbleMap::hasFeatureAt(QPoint const&) const
(this=0x561c64573280, position=...) at
/usr/src/debug/marble-18.04.3-1.1.x86_64/src/lib/marble/MarbleMap.cpp:483

--- Comment #10 from 2012g...@web.de ---
Created attachment 114232
  --> https://bugs.kde.org/attachment.cgi?id=114232=edit
New crash information added by DrKonqi

marble (2.2.20 (2.3 development version)) using Qt 5.11.1

- What I was doing when the application crashed:

Zooming while using the OSM vector theme.

-- Backtrace (Reduced):
#6  0x7f7f9790710b in QPixmap::size() const () at /usr/lib64/libQt5Gui.so.5
#7  0x7f7f9abc6808 in Marble::VisiblePlacemark::symbolRect() const
(this=this@entry=0x561c6df6ff20) at
/usr/src/debug/marble-18.04.3-1.1.x86_64/src/lib/marble/VisiblePlacemark.cpp:171
#8  0x7f7f9abc83c3 in Marble::PlacemarkLayout::hasPlacemarkAt(QPoint
const&) (this=0x561c6459bbf8, pos=...) at
/usr/include/qt5/QtCore/qarraydata.h:143
#9  0x7f7f9aadebf9 in Marble::PlacemarkLayer::hasPlacemarkAt(QPoint const&)
(this=, pos=...) at
/usr/src/debug/marble-18.04.3-1.1.x86_64/src/lib/marble/layers/PlacemarkLayer.cpp:218
#10 0x7f7f9ab176da in Marble::MarbleMap::hasFeatureAt(QPoint const&) const
(this=0x561c64573280, position=...) at
/usr/src/debug/marble-18.04.3-1.1.x86_64/src/lib/marble/MarbleMap.cpp:483

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

[Keyboard status applet] [Bug 396578] keyboard shortcut

[Christoph Feck]

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

--- Comment #2 from Christoph Feck  ---
If you can provide the information requested in comment #1, please add it.

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

[konsole] [Bug 396960] Feature Request: ability to set Konsole tab background color using escape codes (like can already be done for the terminal background color)

[Egmont Koblinger]

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

Egmont Koblinger  changed:

   What|Removed |Added

 CC||egm...@gmail.com

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

[Discover] [Bug 396991] History feature

[Nate Graham]

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

--- Comment #2 from Nate Graham  ---
That's currently true, but un-actionable information can still be useful--not
only for troubleshooting, but also just making the user feel more informed and
in control.

Also, an Update History page would support and be a prerequisite for the
potential future features of error recovery and/or package/app version
rollbacks.

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

[frameworks-kxmlgui] [Bug 395988] KMainWindow saves invalid window/widget state under Qt 5.11.1

[David Faure]

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

--- Comment #24 from David Faure  ---
Git commit 814f0db2a1ae5b15bf91909ce80a5d6792f9aeed by David Faure.
Committed on 31/07/2018 at 13:46.
Pushed by dfaure into branch 'Applications/18.08'.

Port to setAutoSaveSettings so that saving happens before hiding.

Summary:
See d35a882895 in kxmlgui for more complete explanation.
Related: bug 396339

Test Plan: kmail ; Alt+F4 ; kmail -> now the statusbar and toolbar are visible
again

Reviewers: ngraham, elvisangelaccio, broulik, cfeck, mlaurent

Reviewed By: mlaurent

Subscribers: kde-pim

Tags: #kde_pim

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

M  +1-5src/kmmainwin.cpp

https://commits.kde.org/kmail/814f0db2a1ae5b15bf91909ce80a5d6792f9aeed

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

[kmail2] [Bug 396339] [Kmail] Main and status toolbars options not remembered

[David Faure]

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

David Faure  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REOPENED|RESOLVED
  Latest Commit||https://commits.kde.org/kma
   ||il/814f0db2a1ae5b15bf91909c
   ||e80a5d6792f9aeed

--- Comment #5 from David Faure  ---
Git commit 814f0db2a1ae5b15bf91909ce80a5d6792f9aeed by David Faure.
Committed on 31/07/2018 at 13:46.
Pushed by dfaure into branch 'Applications/18.08'.

Port to setAutoSaveSettings so that saving happens before hiding.

Summary:
See d35a882895 in kxmlgui for more complete explanation.
Related: bug 395988

Test Plan: kmail ; Alt+F4 ; kmail -> now the statusbar and toolbar are visible
again

Reviewers: ngraham, elvisangelaccio, broulik, cfeck, mlaurent

Reviewed By: mlaurent

Subscribers: kde-pim

Tags: #kde_pim

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

M  +1-5src/kmmainwin.cpp

https://commits.kde.org/kmail/814f0db2a1ae5b15bf91909ce80a5d6792f9aeed

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

[krita] [Bug 365478] Eraser switch size lag

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED
 Status|NEEDSINFO   |RESOLVED

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

[valgrind] [Bug 385409] s390x: z13 vector integer instructions not implemented

[Andreas Arnez]

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

--- Comment #22 from Andreas Arnez  ---
Created attachment 114230
  --> https://bugs.kde.org/attachment.cgi?id=114230=edit
Fix strict aliasing violation

This fix applies to Vadim's new version.  It also undoes the change from
UChar[6] to ULong, because that change was unnecessary and I prefer the
original approach.  (A 6-byte character array seems more appropriate for
representing an s390x instruction, and the original approach avoids pointer
conversions.)

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

[valgrind] [Bug 397012] New: glibc ld.so uses arch_prctl on i386

[Mark Wielaard]

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

Bug ID: 397012
   Summary: glibc ld.so uses arch_prctl on i386
   Product: valgrind
   Version: 3.14 SVN
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: m...@klomp.org
  Target Milestone: ---

arch_prctl used to be amd64 only. But since linux 4.12 it is also implemented
or i386. And since glibc 2.28 (not yet released) it will be used to see if the
cpu/kernel provides CET support.

See also https://bugs.kde.org/show_bug.cgi?id=396887

To prevent seeing:

WARNING: unhandled x86-linux syscall: 384
You may be able to write your own handler.
Read the file README_MISSING_SYSCALL_OR_IOCTL.
Nevertheless we consider this a bug.  Please report
it at http://valgrind.org/support/bug_reports.html.

on every program run under valgrind I just made it ENOSYS on Fedora:

diff --git a/coregrind/m_syswrap/syswrap-x86-linux.c
b/coregrind/m_syswrap/syswrap-x86-linux.c
index bec145a..11bb13d 100644
--- a/coregrind/m_syswrap/syswrap-x86-linux.c
+++ b/coregrind/m_syswrap/syswrap-x86-linux.c
@@ -1604,7 +1604,10 @@ static SyscallTableEntry syscall_table[] = {
LINX_(__NR_sendmsg,   sys_sendmsg),  // 370
LINXY(__NR_recvfrom,  sys_recvfrom), // 371
LINXY(__NR_recvmsg,   sys_recvmsg),  // 372
-   LINX_(__NR_shutdown,  sys_shutdown)  // 373
+   LINX_(__NR_shutdown,  sys_shutdown), // 373
+
+   /* Explicitly not supported on i386 yet. */
+   GENX_(__NR_arch_prctl,sys_ni_syscall)// 384
 };

 SyscallTableEntry* ML_(get_linux_syscall_entry) ( UInt sysno )

This is fine for glibc/ld.so usage since any failure indicates no CET support.

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

[krita] [Bug 365478] Eraser switch size lag

[Zafio]

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

--- Comment #6 from Zafio  ---
(In reply to Julian Schraner from comment #5)

Hi Julian, this one is fixed!

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

[kmail2] [Bug 397011] Add Followup Reminder doesn't create reminder correctly

[Sander van Grieken]

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

Sander van Grieken  changed:

   What|Removed |Added

Summary|Add Followup Reminder   |Add Followup Reminder
   |doesn't create reminder |doesn't create reminder
   ||correctly

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

[kmail2] [Bug 397011] New: Add Followup Reminder doesn't create reminder

[Sander van Grieken]

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

Bug ID: 397011
   Summary: Add Followup Reminder doesn't create reminder
   Product: kmail2
   Version: unspecified
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: UI
  Assignee: kdepim-b...@kde.org
  Reporter: san...@outrightsolutions.nl
  Target Milestone: ---

Using 17.12.3-1 from Debian Buster.

When I rightclick on an email (the main message view), there's an option Add
Followup Reminder. Clicking that, there's a dialog with a date field and a
calendar dropdown. When I set a date and choose a calendar, the reminder is
created as a ToDo item.

When I go to the ToDo section in Kontact, and I open the reminder, there is no
Due date set, and the reminder section is greyed out.

I would expect a Due date to be checked (at 0:00 time), and the reminder
section not greyed out.

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

[kstars] [Bug 397010] New: Context menu hides after ~1 second in some cases (e.g. on objects below horizon)

[Christian Dersch]

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

Bug ID: 397010
   Summary: Context menu hides after ~1 second in some cases (e.g.
on objects below horizon)
   Product: kstars
   Version: 2.9.7
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: mutla...@ikarustech.com
  Reporter: lupi...@mailbox.org
  Target Milestone: ---

When right clicking on an object to get the popup/context menu for that object,
it just closes after ~1 second in some cases, e.g. when object is below
horizon. 

Tested on Fedora 28 with Qt 5.10.1 and KF5 5.48, also known on Arch Linux and
Fedora Rawhide (Qt 5.11.1 and KF5 5.48).

To reproduce you can use a current Fedora Rawhide Astronomy live build
(https://koji.fedoraproject.org/koji/taskinfo?taskID=28714105), just start
KStars and right click on object below horizon. 

Further investigation shows that this has been introduced with
https://cgit.kde.org/kstars.git/commit/?id=a852d0c6edced5263a00361368222e8f3ed96eba

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

[Akonadi] [Bug 396980] akonadi_imap_resource segfaults [due to ImapQuotaAttribute in libakonadi-singlefileresource.so]

[Christoph Feck]

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

--- Comment #4 from Christoph Feck  ---
For help see https://community.kde.org/Get_Involved/development

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

[Rocs] [Bug 397009] qml-module-qtqml-statemachine is not in dependency

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #1 from Christoph Feck  ---
Reported as bug 396222.

The bug tracker for Kubuntu is Launchpad.

https://launchpad.net/ubuntu/+search?text=rocs

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