[kwin] [Bug 351116] Titlebar font should be editable from WM settings

[Tsu Jan via KDE Bugzilla]

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

--- Comment #14 from Tsu Jan  ---
@Martin Gräßlin

I understand your reasoning. It was why I said "Technical problems aside,...";
just wanted to show the problem from another perspective.

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

[kwin] [Bug 351116] Titlebar font should be editable from WM settings

[Tsu Jan via KDE Bugzilla]

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

Tsu Jan  changed:

   What|Removed |Added

 CC||tsujan2...@gmail.com

--- Comment #12 from Tsu Jan  ---
Technical problems aside, since kwin works well outside KDE too, it's logical
to expect a separate titlebar font setting for it.

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

[plasmashell] [Bug 365014] All windows hide on repeating desktop click

[Tsu Jan via KDE Bugzilla]

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

--- Comment #40 from Tsu Jan  ---
I confirm that this bug is fixed in Plasma-5.8.1. Thanks!

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

[krita] [Bug 368716] "Edit Brush Settings" doesn't open.

[jan via KDE Bugzilla]

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

--- Comment #5 from jan  ---
I have managed to get "snap" Krita 3.0.1 running on Gnome 3 on Ubuntu. With the
"snap" Krita version I have no problems with "Edit Brush Settings" or F5.

So with "Appimage" "Edit Brush Settings" doesn't work, with "snap" version
3.0.1 (git 7c6cf9c) all works fine. This is on Gnome 3.

"just for your information"

Jan

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

[krita] [Bug 368716] "Edit Brush Settings" doesn't open.

[jan via KDE Bugzilla]

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

--- Comment #3 from jan  ---
I use 'Gnome 3' 3.18.1.2-1ubuntu1.16.04.2

Linux 4.4.0-36-generic #55-Ubuntu SMP Thu Aug 11 18:01:55 UTC 2016 x86_64
x86_64 x86_64 GNU/Linux.

I noticed that all works fine with Unity and Enlightenment 0.21
On Gnome 3 all works but the mentioned "Edit Brush Settings" and F5. Pity that
Gnome 3 fails on me here as it is far out my favourite.

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

[krita] [Bug 368716] New: "Edit Brush Settings" doesn't open.

[jan via KDE Bugzilla]

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

Bug ID: 368716
   Summary: "Edit Brush Settings" doesn't open.
   Product: krita
   Version: 3.0.1
  Platform: Appimage
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: Brush engine
  Assignee: krita-bugs-n...@kde.org
  Reporter: jan.br...@gmail.com

"Edit Brush Settings" doesn't open if pressing F5 nor by clicking on icon on
toolbar. It stays closed.

Reproducible: Always

Steps to Reproduce:
1. Click on "Edit Brush Settings"
2. Press F5
3.

Actual Results:  
Brush editor stays closed.

Expected Results:  
Brush editor should open for brush adjustments.

Appimage 3.0.1 used, brush editor doesn't open . 
The PPA 2.9 version does work correct, brush editor opens.

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

[plasmashell] [Bug 365014] All windows hide on repeating desktop click

[Tsu Jan via KDE Bugzilla]

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

--- Comment #38 from Tsu Jan  ---
> There seem to be additional changes

OK! That's what I wanted to know. Thank you!

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

[plasmashell] [Bug 365014] All windows hide on repeating desktop click

[Tsu Jan via KDE Bugzilla]

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

--- Comment #36 from Tsu Jan  ---
> I can confirm it works with master

So, other commits are also essential to fixing this bug? Which ones? I ask
because this bug, together with bug #360219, has made a painful experience out
of Plasma for months.

> No need to change the status.

 Martin Gräßlin said in https://bugs.kde.org/show_bug.cgi?id=365014#c33, "We
want to have it tested properly before shipping it to the users." I told the
result of my test.

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

[plasmashell] [Bug 360219] Right Click opens files

[Tsu Jan via KDE Bugzilla]

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

Tsu Jan  changed:

   What|Removed |Added

 CC||tsujan2...@gmail.com

--- Comment #31 from Tsu Jan  ---
For me, both on a desktop computer with nvidia and on a laptop with Intel, the
only way of right clicking an item on the desktop without opening it is holding
the right mouse button for 1-2 seconds (Manjaro Testing with
plasma-workspace-5.7.4).

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

[plasmashell] [Bug 365014] All windows hide on repeating desktop click

[Tsu Jan via KDE Bugzilla]

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

Tsu Jan  changed:

   What|Removed |Added

 CC||tsujan2...@gmail.com

--- Comment #34 from Tsu Jan  ---
Unfortunately, the commit
https://quickgit.kde.org/?p=plasma-workspace.git=commit=30b7e3f2423b07b372daffbe09e420ba1ef59ced
has no effect here. After compiling plasma-workspace-5.7.4 with it, I still can
reproduce the issue easily (on Manjaro Testing).

Please change the status!

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

[gwenview] [Bug 368439] New: crash if I start a *.png

[jan via KDE Bugzilla]

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

Bug ID: 368439
   Summary: crash if I start a *.png
   Product: gwenview
   Version: Other (add details in bug description)
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: importer
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: j.kla...@operamail.com
CC: myr...@kde.org

afer starting a *.png I can read:
No such object path '/modules/kdeconnect/devices/df5f239b28dbbe1d/sftp'
but the start war korrect
My Kubuntu ist version 5.5.5; QT 5.5.1; Kernel 4.4.0-34-generic; CPU i3-4100M;
workspace 5,7 GiB

when only starting gwenview (without PNG) it starts without an error

Reproducible: Always

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

[kate] [Bug 354482] scrolling quickly with the mouse wheel jumps and can even scroll backwards

[Tsu Jan via KDE Bugzilla]

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

--- Comment #9 from Tsu Jan  ---
I'm almost sure that this bug is about
https://bugreports.qt.io/browse/QTBUG-49294

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

[kwin] [Bug 344326] Black or corrupted screen on resume from suspend

[Tsu Jan via KDE Bugzilla]

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

--- Comment #113 from Tsu Jan  ---
Shouldn't the title be changed to "Black or corrupted screen on resume from
suspend with nVidia"? I had this issue with nVidia but never with Intel.

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

[Breeze] [Bug 361192] File managers use wrong breeze icons size.

[Tsu Jan via KDE Bugzilla]

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

--- Comment #4 from Tsu Jan  ---
You could close this report. See https://codereview.qt-project.org/#/c/159800/

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

[Breeze] [Bug 361192] File managers use wrong breeze icons size.

[Tsu Jan via KDE Bugzilla]

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

--- Comment #2 from Tsu Jan  ---
Wrong address! Sorry, the bug is in qiconloader.cpp -> directoryMatchesSize().

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

[Breeze] [Bug 361192] File managers use wrong breeze icons size.

[Tsu Jan via KDE Bugzilla]

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

Tsu Jan  changed:

   What|Removed |Added

 CC||tsujan2...@gmail.com

--- Comment #1 from Tsu Jan  ---
This is a Qt bug (in qiconloader.cpp -> directorySizeDistance()).

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

[Akonadi] [Bug 361485] New: crash on initial start with mysql 5.7 on ubuntu 16.04

[Jan via KDE Bugzilla]

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

Bug ID: 361485
   Summary: crash on initial start with mysql 5.7 on ubuntu 16.04
   Product: Akonadi
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: server
  Assignee: kdepim-b...@kde.org
  Reporter: malte.ge...@googlemail.com

On a clean installation of kubuntu 16.04 akonadi won't start.
The initial creation of the mysql database fails.

Reproducible: Always

Steps to Reproduce:
1. Clean install of kubuntu 16.04 beta release
2. Start akonadi from the cli using 'akonadictl start'

Actual Results:  
initial start fails
akonadi is not usable at all

Expected Results:  
initial start of akonadi and be able to set up ressources

janmalte@ubuntu:~$ akonadictl start
Starting Akonadi Server...
   done.
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
search paths:  ("/home/janmalte/.composer/vendor/bin", "/home/janmalte/.bin",
"/usr/local/sbin", "/usr/local/bin", "/usr/sbin", "/usr/bin", "/sbin", "/bin",
"/usr/games", "/usr/local/games", "/opt/bin", "/usr/sbin", "/usr/local/sbin",
"/usr/local/libexec", "/usr/libexec", "/opt/mysql/libexec",
"/opt/local/lib/mysql5/bin", "/opt/mysql/sbin")
Found mysql_install_db:  "/usr/bin/mysql_install_db"
Found mysqlcheck:  "/usr/bin/mysqlcheck"
mysql_install_db: [ERROR] unknown option '--force'
2016-04-07 08:51:57 [ERROR]   Unrecognized options
Database process exited unexpectedly during initial connection!
executable: "/usr/sbin/mysqld-akonadi"
arguments: ("--defaults-file=/home/janmalte/.local/share/akonadi/mysql.conf",
"--datadir=/home/janmalte/.local/share/akonadi/db_data/",
"--socket=/tmp/akonadi-janmalte.ddv6eY/mysql.socket")
stdout: ""
stderr: ""
exit code: 1
process error: "Unknown error"
terminating service threads
terminating connection threads
stopping db process
mysqladmin: connect to server at 'localhost' failed
error: 'Can't connect to local MySQL server through socket
'/tmp/akonadi-janmalte.ddv6eY/mysql.socket' (2)'
Check that mysqld is running and that the socket:
'/tmp/akonadi-janmalte.ddv6eY/mysql.socket' exists!
Failed to remove Unix socket
Failed to remove runtime connection config file
Application 'akonadiserver' exited normally...

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

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

[Tsu Jan via KDE Bugzilla]

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

--- Comment #16 from Tsu Jan  ---
@Wulf
I think this bug has never been fixed because it occurs once a year, being
related to daylight saving time.

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

[rkward] [Bug 360350] enhanced context menu for objects

[Jan via KDE Bugzilla]

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

--- Comment #4 from Jan  ---
(In reply to Thomas Friedrichsmeier from comment #3)

Thank you for your reply. I'm delighted about your interest.

> I am slightly surprised by your choice of example actions, though: E.g. 
> dimensions (rows / columns) is already visible from the tool-tip, when 
> hovering the mouse over an object.

You're right. Sometimes "nrow" and "length" return different results so a quick
check via context menu would be useful (for me). Same with "names" and
"colnames".

> Also, the existing "View" action is meant to serve a somewhat similar purpose

"View" isn't a good choice for an overview of large objects. Clicking at the
tab "print(x)" shows "Fetching information. Please wait." for up to a minute.
The command "head" give results much faster.

> I am wondering: Would it make more sense to allow (the same / different?) 
> custom areas in the "View" window, in addition to / instead of your 
> suggestion?

This is another possibility.
Sometimes the first tab of the "View" window "summary(x)" also needs some time
to be ready (for large objects). So the first tab should have only a limited
amount of information.

Example:
first tab: various
ncol: ...
nrow: ...
length: ...
(Please both nrow and length)
names: ...
colnames: ...
(Please both names and colnames)

second tab: head(x)

third tab: tail(x)

(or head(x) and tail(x) combined in one tab)

fourth tab: summary(x)

fifth tab: print(x)

sixth tab: str(x)

Regards

Jan

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

[kmymoney4] [Bug 352954] Report: Transactions by Reconciliation Status does not correctly honor selected state in config

[Jan via KDE Bugzilla]

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

Jan  changed:

   What|Removed |Added

 CC||jan_cec...@verizon.net

--- Comment #2 from Jan  ---
I cannot reproduce this problem.  In KMM 4.6.4, the report looks correct.  Note
that the date range of the Customized Report needs to be set to include 2015
transactions or the report is trivial.  Also note that the report was
customized to only include reconciled transactions.  Please check and, if
confirmed, close this bug.

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

[plasmashell] [Bug 344123] Colorize entry background based on icon color

[Jan via KDE Bugzilla]

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

Jan  changed:

   What|Removed |Added

 CC||cyanmyst...@gmx.net

--- Comment #4 from Jan  ---
There is a problem here. The current background colors indicates the window
status (focused, not focused, minimized, not running). There aren't any other
indicators anymore, so like these small triangles before.

In which case should the background have the the icon-specific-color?

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

[kmymoney4] [Bug 359739] New: Incorrect label for New Investment entry

[Jan via KDE Bugzilla]

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

Bug ID: 359739
   Summary: Incorrect label for New Investment entry
   Product: kmymoney4
   Version: 4.6.6
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kmymoney-de...@kde.org
  Reporter: jan_cec...@verizon.net

My investments all use "Total for all shares" as Price Entry method. When
entering a new buy, I do get the number of shares and the total price fields in
the data entry pane. However, when I duplicate an existing buy in order to edit
it (e.g. to enter a recurring 401K investment where the total price is always
the same, but the number of shares changes), now this field is called
Price/share. Yet, I still need to enter the total price here and not the price
per share for the data entry to be correct. This problem does not exist in the
old KMM version: it shows the total price instead of price per share as soon as
you edit the transaction.

The same problem is present when duplicating a Reinvest Dividend transaction: 
Price per share is displayed, while the field should be called Price or Total
price.

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

[kmymoney4] [Bug 359659] Wrong payee matching for new payees during OFX import

[Jan via KDE Bugzilla]

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

--- Comment #9 from Jan  ---
Before I upgrade, I just wanted to add this:

1.  I ran KMM from the console:  it prints matching info in the terminal. 
Every time a match is found, two false matches are listed and one or zero
correct matches.  If there is a third match, the result is always good; if
there isn't, it's always wrong.

2. If I disallow matching for these two incorrectly matching payees, or change
it to "Match on name," everything works.  The original matching settings for
these two payees was "Match on a name listed below", but the list was empty
(not even blanks) and all options in the list [add, remove, up, down] were
grayed out.

3. When I then reset the original matching (match on name listed below), I
could no longer reproduce the problem, even if the prints in the terminal still
included both payees in all matches found.  The difference is that now a new
payee was created, as expected.

So, swapping payees that match on an empty list back and forth to either no
match or match on name solves the problem.  Matching on an empty list always
leads to a match detection, but not always to an incorrect result.  Before
changing the matching, an incorrect match was generated; after a
back-and-forth, a new payee was created.

Is this explained by the 4.7.2 change?  If so, please close the bug.  Thanks!

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

[kmymoney4] [Bug 249363] "Map to Online Account" cannot distinguish different accounts properly

[Jan via KDE Bugzilla]

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

--- Comment #14 from Jan  ---
I think I see the problem.  We were both working for the same employer (I quit
in the mean time but still have the 401K account).  The wizard showed only one
account with a number.  It turns out this is the employer account number, not
the individual's account number.

So, KMM seems to think there is only one account because there is only one
number.  Is it possible to make it see both accounts?

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

[kmymoney4] [Bug 243534] QIF import of a stock not yet defined in the account results in Add shares transaction assigned to investment account

[Jan via KDE Bugzilla]

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

--- Comment #4 from Jan  ---
I think you can close this.  Since it's so long ago, I doubt I can ever
reproduce it.  Thanks.

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

[kmymoney4] [Bug 249363] "Map to Online Account" cannot distinguish different accounts properly

[Jan via KDE Bugzilla]

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

--- Comment #13 from Jan  ---
Would the existence of a pin procedure be consistent with the fact that I can
import operations for one account, even if they are loaded to the wrong ledger?

The Fidelity FAQ mentions that only a password is needed to access the account
download service, the same as the interactive logon password.

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

[kmymoney4] [Bug 359659] Wrong payee matching for new payees during OFX import

[Jan via KDE Bugzilla]

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

--- Comment #5 from Jan  ---
Also, I did not have this problem with KMM 1.05.  It appeared the day I
switched to KMM 4.6

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

[kmymoney4] [Bug 359659] Wrong payee matching for new payees during OFX import

[Jan via KDE Bugzilla]

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

--- Comment #4 from Jan  ---
Allan: No.  I do not have a " " Payee, and the payee to which it matches all
unknown (new) payees are "IBERIA" in one kmm file and "SUNOCO 0498589   
WORCESTERM" in another kmm file.  Also, this is OFX, not CSV, although I
would not be surprised both use the same matching code.

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

[kmymoney4] [Bug 359659] Wrong payee matching for new payees during OFX import

[Jan via KDE Bugzilla]

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

--- Comment #3 from Jan  ---
Jack:  Yes, I did think of that.  *All* new payees are matched to the same
existing one.  That would require a universal wildcard expression in the
payee's matching tab.  There is nothing at all.  I tried checking "No matching"
to see if it makes a difference.  It just matched with another wrong payee.

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

[kmymoney4] [Bug 347848] Cannot add a fee entry-only anymore for an investment

[Jan via KDE Bugzilla]

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

--- Comment #2 from Jan  ---
I mean, your request looks artificial.  If a fee is not associated with a
dividend or interest payment, it should not be entered as such.  If the fee is
directly associated with a particular investment, perhaps what you want is a
new Activity category, sort of like a negative interest, called "Custody fee",
for instance.  Custody fees normally are "per line", i.e. not directly
associated with an individual investment, but with the number of investments
and therefore should form an independent expense category.  But if you have a
case where such a fee is directly related to an investment other than through a
Buy, Sell, Interest, or Dividend, then a new Activity would be justified.

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

[kmymoney4] [Bug 347848] Cannot add a fee entry-only anymore for an investment

[Jan via KDE Bugzilla]

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

Jan  changed:

   What|Removed |Added

 CC||jan_cec...@verizon.net

--- Comment #1 from Jan  ---
I suppose the fee has to be paid from the associated brokerage account, since
investment accounts don't have cash.  You can enter a withdrawal in the
brokerage account, payable to your bank, and assigned to the desired expense
category.

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

[kmymoney4] [Bug 249363] "Map to Online Account" cannot distinguish different accounts properly

[Jan via KDE Bugzilla]

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

--- Comment #11 from Jan  ---
Right, but I'd expect to see a difference between the two.  I noticed my wife's
account had an account number 1 assigned and mine a  2 [edit account,
institution tab).  That's not what I saw in the list.
As recommended, I unmapped both accounts and then remapped mine:  again only
one account was listed.  Number shown was 09876.  Map succeeded.  When I
updated my account, I again get the invalid user ID or password error.  Here is
the full error text:
"Unable to import '/tmp/kde-jan/kmymoneypd6365.tmp' using the OFX importer
plugin.  The plugin returned the following error: SONRS: Signon invalid (Code
15500):  The use cannot signon because he or she entered an invalid user ID or
password. (Error occurred logging in)..." etc.  This time, my password was not
invalidated.  That is, I connected to the provider's site in a browser without
having to reset the password.  The tmp file mentioned contained a similar error
message in html format.  I tried everything twice to make sure I did not
accidentally enter a wrong password.

Next, I remapped my wife's account.  Again only one choice in the wizard. 
Again, the transactions were added to my account.

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

[kmymoney4] [Bug 238454] Improve UI responsiveness while running unresponsive online quotes

[Jan via KDE Bugzilla]

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

--- Comment #19 from Jan  ---
You probably overlooked something.  I waited for way more than 30 seconds.  It
hangs indefinitely.  I no longer use Finance::Quote, and have not had the
problem anymore.  I also switched to KMM 4.6.4.
If you are interested, I can update Finance::Quote and try again, if you intend
to continue support for Finance::Quote.

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

[kmymoney4] [Bug 249363] "Map to Online Account" cannot distinguish different accounts properly

[Jan via KDE Bugzilla]

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

--- Comment #9 from Jan  ---
Bug still present.

1. When I update my wife's account, it puts her transactions in my account.

2. When I update my account, it says the password is not valid.

3. When I unmap and remap my account, it invalidates my password with the
provider.  I can no longer use the company's interactive website and have to
reset my password first.  After this is done, I can remap my KMM account, but
the result is the same:  password invalid - see #2.

It looks like my comment #4 is still accurate:  the wizzard only lists one
account.  I unmapped my account and mapped it again:  had only one choice.  I
unmapped my wife's account; remapped it and had only one (the same) choice. 
There are two different accounts with the same institution; only one can be
mapped, but it maps to the wrong KMM account.  The other maps to the wrong
online account and fails at login.

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

[kmymoney4] [Bug 330226] Incorrect Net Worth report when adding/removing shares

[Jan via KDE Bugzilla]

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

--- Comment #5 from Jan  ---

I have revisited this and could not find anything wrong in KMM 4.6.4.  Thanks.

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

[kmymoney4] [Bug 359641] New: Inconsistent date in price table

[Jan via KDE Bugzilla]

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

Bug ID: 359641
   Summary: Inconsistent date in price table
   Product: kmymoney4
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kmymoney-de...@kde.org
  Reporter: jan_cec...@verizon.net

A price entered in the price table automatically through the creation of an
investment transaction is not changed when the date of the corresponding
transaction is changed, causing an incorrect price entry.

Reproducible: Always

Steps to Reproduce:
1. Enter a transaction in an investment account
2. Check that a new price was added in the price table
3. Change the date of the transaction
4. Verify that the price table was not corrected accordingly.

Actual Results:  
The price table contains a [transaction] price with incorrect date

Expected Results:  
The price table is updated consistently with the corresponding transaction

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

[kate] [Bug 354482] scrolling quickly with the mouse wheel jumps and can even scroll backwards

[Tsu Jan via KDE Bugzilla]

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

--- Comment #5 from Tsu Jan  ---
I forgot to confirm what Denis said: this is a Qt5 bug and not specific to Kate
or KDE. However, it is specific to Linux.

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

[kate] [Bug 354482] scrolling quickly with the mouse wheel jumps and can even scroll backwards

[Tsu Jan via KDE Bugzilla]

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

Tsu Jan  changed:

   What|Removed |Added

 CC||tsujan2...@gmail.com

--- Comment #4 from Tsu Jan  ---
I encountered this erratic and annoying behavior since Qt-5.3. In
https://bugreports.qt.io/browse/QTBUG-38274, they say it's fixed but it isn't.
As far as I know, the problem is in the first QWheelEvent after the enter
event.

I think a clean Qt bug report is needed. Otherwise, it might not be fixed soon.

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

[kopete] [Bug 358744] New: Kopete crashes on closing message tab

[Jan via KDE Bugzilla]

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

Bug ID: 358744
   Summary: Kopete crashes on closing message tab
   Product: kopete
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kopete-bugs-n...@kde.org
  Reporter: malte.ge...@googlemail.com

Application: kopete (1.7.3)
KDE Platform Version: 4.14.15
Qt Version: 4.8.6
Operating System: Linux 4.2.0-25-generic x86_64
Distribution: Ubuntu 15.10

-- Information about the crash:
- What I was doing when the application crashed:
Kopete is crashing if i close a message tab.
It is also crashing on quitting kopete with the main window menu item "Quit"

The crash can be reproduced every time.

-- Backtrace:
Application: Kopete (kopete), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f5d83eb7840 (LWP 2656))]

Thread 4 (Thread 0x7f5d6c06a700 (LWP 2660)):
#0  0x7f5d7b632884 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f5d7b5eda59 in g_main_context_query () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f5d7b5ee167 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f5d7b5ee2fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f5d8194620e in QEventDispatcherGlib::processEvents
(this=0x7f5d640008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#5  0x7f5d819140d1 in QEventLoop::processEvents
(this=this@entry=0x7f5d6c069d40, flags=...) at kernel/qeventloop.cpp:149
#6  0x7f5d81914445 in QEventLoop::exec (this=this@entry=0x7f5d6c069d40,
flags=...) at kernel/qeventloop.cpp:204
#7  0x7f5d818034f9 in QThread::exec (this=this@entry=0x10bf060) at
thread/qthread.cpp:538
#8  0x7f5d818f4133 in QInotifyFileSystemWatcherEngine::run (this=0x10bf060)
at io/qfilesystemwatcher_inotify.cpp:265
#9  0x7f5d81805d1c in QThreadPrivate::start (arg=0x10bf060) at
thread/qthread_unix.cpp:349
#10 0x7f5d7beda6aa in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#11 0x7f5d801d1eed in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 3 (Thread 0x7f5d62039700 (LWP 2667)):
#0  0x7fffaf1aeb6d in clock_gettime ()
#1  0x7f5d801e038d in clock_gettime () from /lib/x86_64-linux-gnu/libc.so.6
#2  0x7f5d81860565 in do_gettime (frac=, sec=) at tools/qelapsedtimer_unix.cpp:127
#3  qt_gettime () at tools/qelapsedtimer_unix.cpp:144
#4  0x7f5d819470a5 in QTimerInfoList::updateCurrentTime
(this=0x7f5d54002ce0) at kernel/qeventdispatcher_unix.cpp:354
#5  QTimerInfoList::timerWait (this=0x7f5d54002ce0, tm=...) at
kernel/qeventdispatcher_unix.cpp:460
#6  0x7f5d819458dc in timerSourcePrepareHelper (src=,
timeout=0x7f5d62038b14) at kernel/qeventdispatcher_glib.cpp:143
#7  0x7f5d7b5ed77d in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x7f5d7b5ee11b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x7f5d7b5ee2fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x7f5d8194620e in QEventDispatcherGlib::processEvents
(this=0x7f5d540008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#11 0x7f5d819140d1 in QEventLoop::processEvents
(this=this@entry=0x7f5d62038ce0, flags=...) at kernel/qeventloop.cpp:149
#12 0x7f5d81914445 in QEventLoop::exec (this=this@entry=0x7f5d62038ce0,
flags=...) at kernel/qeventloop.cpp:204
#13 0x7f5d818034f9 in QThread::exec (this=) at
thread/qthread.cpp:538
#14 0x7f5d6851cb2a in ?? () from /usr/lib/kde4/kopete_jabber.so
#15 0x7f5d81805d1c in QThreadPrivate::start (arg=0x13c4d40) at
thread/qthread_unix.cpp:349
#16 0x7f5d7beda6aa in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#17 0x7f5d801d1eed in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 2 (Thread 0x7f5d58ebc700 (LWP 8955)):
#0  0x7f5d801c249d in read () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x7f5d7b6314e0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f5d7b5edcd4 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f5d7b5ee190 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f5d7b5ee2fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f5d8194620e in QEventDispatcherGlib::processEvents
(this=0x7f5d480008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#6  0x7f5d819140d1 in QEventLoop::processEvents
(this=this@entry=0x7f5d58ebbd40, flags=...) at kernel/qeventloop.cpp:149
#7  0x7f5d81914445 in QEventLoop::exec (this=this@entry=0x7f5d58ebbd40,
flags=...) at kernel/qeventloop.cpp:204
#8  0x7f5d818034f9 in QThread::exec (this=this@entry=0x273ac50) at
thread/qthread.cpp:538
#9  0x7f5d818f4133 in 

[Akonadi] [Bug 354056] Deleted emails stay, but greyed out

[Jan via KDE Bugzilla]

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

--- Comment #17 from Jan  ---
This is still present:
Akonadi 5.0.51
kmail2 5.0.3

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

[konsole] [Bug 350651] Konsole has scrolling artifacts if HiDPI screen with scaling in Qt

[Tsu Jan via KDE Bugzilla]

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

--- Comment #5 from Tsu Jan  ---
A part of the issue: https://bugreports.qt.io/browse/QTBUG-48116

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

[kexi] [Bug 356888] Kexi crashes at the attempt to create a table row.

[Jan via KDE Bugzilla]

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

--- Comment #3 from Jan  ---
Created attachment 96200
  --> https://bugs.kde.org/attachment.cgi?id=96200=edit
The Database file.

Thanks for the quick response. Sorry I forgot to deliver more information. This
is the relevant database.

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

[systemsettings] [Bug 356876] New: Online Accounts crashing on "configure"

[Jan via KDE Bugzilla]

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

Bug ID: 356876
   Summary: Online Accounts crashing on "configure"
   Product: systemsettings
   Version: 5.4.1
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: goeb...@gmail.com

Application: systemsettings5 (5.4.1)

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

-- Information about the crash:
- What I was doing when the application crashed:
Open system settings.
click online accounts.
add google account
click on the google account on the left
click configure.
crash.

I tried with and without the "google hangouts" option.

Also:
It doesn´t seem to import any of my account stuff, no mail in kmail.
I am not sure if that is a bug, i remember to read that it should integrate
nicely.

Else:
Running Ubuntu15.10, upgrade from 15.04, KDE got upgraded from an earlier
version (earlier plasma5 version) too.

The crash can be reproduced every time.

-- Backtrace:
Application: System Settings (systemsettings5), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f1ec796a800 (LWP 14028))]

Thread 4 (Thread 0x7f1eb489a700 (LWP 14029)):
#0  0x7f1ec41078dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f1ec1e17bd2 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f1ec1e1974f in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f1eb7633a39 in QXcbEventReader::run (this=0x2061890) at
qxcbconnection.cpp:1105
#4  0x7f1ec47fa2be in QThreadPrivate::start (arg=0x2061890) at
thread/qthread_unix.cpp:337
#5  0x7f1ec15a26aa in start_thread (arg=0x7f1eb489a700) at
pthread_create.c:333
#6  0x7f1ec4112eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f1ea5a91700 (LWP 14032)):
#0  0x7f1ec410349d in read () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f1ec10c64e0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f1ec1082cd4 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f1ec1083190 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f1ec10832fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f1ec1083339 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7f1ec10a9965 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7f1ec15a26aa in start_thread (arg=0x7f1ea5a91700) at
pthread_create.c:333
#8  0x7f1ec4112eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f1ea5290700 (LWP 14033)):
#0  0x7f1ec41078dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f1ec10831ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f1ec1083572 in g_main_loop_run () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f1ea5f9a4c6 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#4  0x7f1ec10a9965 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f1ec15a26aa in start_thread (arg=0x7f1ea5290700) at
pthread_create.c:333
#6  0x7f1ec4112eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f1ec796a800 (LWP 14028)):
[KCrash Handler]
#6  0x7f1e9e4799f8 in ?? () from
/usr/lib/x86_64-linux-gnu/qt5/plugins/kaccounts/ui/ktpaccountskcm_plugin_kaccounts.so
#7  0x7f1ec4a0a617 in QtPrivate::QSlotObjectBase::call (a=0x7fff93970a40,
r=0x2321b50, this=) at
../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124
#8  QMetaObject::activate (sender=0x2321b50, signalOffset=,
local_signal_index=, argv=) at
kernel/qobject.cpp:3702
#9  0x7f1e9e4799b8 in ?? () from
/usr/lib/x86_64-linux-gnu/qt5/plugins/kaccounts/ui/ktpaccountskcm_plugin_kaccounts.so
#10 0x7f1ec4a0a617 in QtPrivate::QSlotObjectBase::call (a=0x7fff93970c20,
r=0x25c6b70, this=) at
../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124
#11 QMetaObject::activate (sender=sender@entry=0x25c6b70,
signalOffset=, local_signal_index=local_signal_index@entry=2,
argv=argv@entry=0x7fff93970c20) at kernel/qobject.cpp:3702
#12 0x7f1ec4a0af87 in QMetaObject::activate (sender=sender@entry=0x25c6b70,
m=m@entry=0x7f1ec6374620 ,
local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7fff93970c20)
at kernel/qobject.cpp:3582
#13 0x7f1ec61eefe2 in QAbstractButton::clicked (this=this@entry=0x25c6b70,
_t1=false) at .moc/moc_qabstractbutton.cpp:298
#14 0x7f1ec5f55914 in QAbstractButtonPrivate::emitClicked (this=0x2461e60)
at widgets/qabstractbutton.cpp:534
#15 0x7f1ec5f56df9 in QAbstractButtonPrivate::click (this=0x2461e60) at
widgets/qabstractbutton.cpp:527
#16 0x7f1ec5f56f74 in 

[kexi] [Bug 356888] Kexi crashes at the attempt to create a table row.

[Jan via KDE Bugzilla]

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

Jan  changed:

   What|Removed |Added

  Component|General |Tables

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

[kexi] [Bug 356888] New: Kexi crashes at the attempt to create a table row.

[Jan via KDE Bugzilla]

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

Bug ID: 356888
   Summary: Kexi crashes at the attempt to create a table row.
   Product: kexi
   Version: 2.9.10
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: General
  Assignee: kexi-b...@kde.org
  Reporter: cyanmyst...@gmx.net
CC: a...@piggz.co.uk, in...@fables.co.za

Application: kexi (2.9.10)
KDE Platform Version: 4.14.14
Qt Version: 4.8.7
Operating System: Linux 4.2.5-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
This Bug appeared on the third table I made in the Design view. I changed to
the Data view and wanted to fill the table with data.

- What I was doing when the application crashed:
 The Crash is reproducible either when clicking the +-symbol  on the upper left
side of the list or when clicking on the +-symbol on the lower border.

- Unusual behavior I noticed:
As the screenshot shows the list isn't initialized correctly.

I can reproduce the crash every time I reload the database file. If I delete
the table and recreate it it leads to the same problem.

-- Backtrace:
Application: Kexi (kexi), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[KCrash Handler]
#6  0x7f2aabbf90c5 in KexiTableScrollArea::keyPressEvent(QKeyEvent*) ()
from /usr/lib/libkexidatatable.so.14
#7  0x7f2ad31b56b3 in QWidget::event(QEvent*) () from
/usr/lib/libQtGui.so.4
#8  0x7f2ad357a7ee in QFrame::event(QEvent*) () from /usr/lib/libQtGui.so.4
#9  0x7f2ad360019b in QAbstractScrollArea::event(QEvent*) () from
/usr/lib/libQtGui.so.4
#10 0x7f2aabbf9ed7 in KexiTableScrollArea::event(QEvent*) () from
/usr/lib/libkexidatatable.so.14
#11 0x7f2ad315e39c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQtGui.so.4
#12 0x7f2ad3166543 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/libQtGui.so.4
#13 0x7f2ad0c3e8aa in KApplication::notify(QObject*, QEvent*) () from
/usr/lib/libkdeui.so.5
#14 0x7f2ad2bf054d in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib/libQtCore.so.4
#15 0x7f2ad3204493 in ?? () from /usr/lib/libQtGui.so.4
#16 0x7f2ad32049a2 in ?? () from /usr/lib/libQtGui.so.4
#17 0x7f2ad31de6d6 in QApplication::x11ProcessEvent(_XEvent*) () from
/usr/lib/libQtGui.so.4
#18 0x7f2ad3207322 in ?? () from /usr/lib/libQtGui.so.4
#19 0x7f2acec2cdc7 in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#20 0x7f2acec2d020 in ?? () from /usr/lib/libglib-2.0.so.0
#21 0x7f2acec2d0cc in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#22 0x7f2ad2c20834 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQtCore.so.4
#23 0x7f2ad32073f6 in ?? () from /usr/lib/libQtGui.so.4
#24 0x7f2ad2beedc1 in
QEventLoop::processEvents(QFlags) () from
/usr/lib/libQtCore.so.4
#25 0x7f2ad2bef135 in
QEventLoop::exec(QFlags) () from
/usr/lib/libQtCore.so.4
#26 0x7f2ad2bf4ad9 in QCoreApplication::exec() () from
/usr/lib/libQtCore.so.4
#27 0x00400979 in ?? ()
#28 0x7f2ad26d0610 in __libc_start_main () from /usr/lib/libc.so.6
#29 0x004009e9 in _start ()

Reported using DrKonqi

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

[kexi] [Bug 356888] Kexi crashes at the attempt to create a table row.

[Jan via KDE Bugzilla]

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

--- Comment #1 from Jan  ---
Created attachment 96196
  --> https://bugs.kde.org/attachment.cgi?id=96196=edit
Before crash. List interface seems to be broken.

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

[kmail2] [Bug 355093] Crash if I click on new mail

[Jan via KDE Bugzilla]

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

Jan  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

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

[plasmashell] [Bug 354928] Minimized task cannot be told apart from a not running launcher

[Jan via KDE Bugzilla]

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

--- Comment #22 from Jan  ---
Never mind, the update to 5.5.1 fixed it for me.

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

[plasmashell] [Bug 354928] Minimized task cannot be told apart from a not running launcher

[Jan via KDE Bugzilla]

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

Jan  changed:

   What|Removed |Added

 CC||medhe...@web.de

--- Comment #21 from Jan  ---
Well, for me this bug is still present in 5.5. Neither light nor dark theme
make minimized apps distinguishable even after clearing the .cache folder.

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