[kdenlive] [Bug 364837] High CPU usage when kdenlive window is on top

2016-10-08 Thread BobSCA via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364837

--- Comment #16 from BobSCA  ---
Wegwerf, I am not familiar with Qt and don't know if there has been a Qt
upgrade. Is there something specific you would like me to check?

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


[kdenlive] [Bug 364837] High CPU usage when kdenlive window is on top

2016-10-08 Thread BobSCA via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364837

--- Comment #13 from BobSCA  ---
I did an upgrade from the kdenlive-master ppa and found there was no change in
CPU usage.

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


[kmymoney4] [Bug 343484] Transactions created with no payee/receiver after OFX import when payee has default account

2016-09-02 Thread BobSCA via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=343484

BobSCA  changed:

   What|Removed |Added

Summary|Transactions created with   |Transactions created with
   |no payee/receiver after OFX |no payee/receiver after OFX
   |import when payer has   |import when payee has
   |default account |default account

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


[kmymoney4] [Bug 343484] Transactions created with no payee/receiver after OFX import when payer has default account

2016-09-02 Thread BobSCA via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=343484

--- Comment #3 from BobSCA  ---
(In reply to BobSCA from comment #1)
> Version 4.7.1
Still present in 4.8.0.

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


[kmymoney4] [Bug 343484] Transactions created with no payee/receiver after OFX import when payer has default account

2016-09-02 Thread BobSCA via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=343484

BobSCA  changed:

   What|Removed |Added

Version|4.7.1   |4.8.0

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


[kmymoney4] [Bug 368159] New: Report Transactions by Payee omits transactions lacking category

2016-09-02 Thread BobSCA via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=368159

Bug ID: 368159
   Summary: Report Transactions by Payee omits transactions
lacking category
   Product: kmymoney4
   Version: 4.8.0
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kmymoney-de...@kde.org
  Reporter: bobs_spa...@cox.net

Reports with "Organize: By Payee" option omits transactions which do not
specify a category, including all transactions which specify an account in the
Category/Account field.

Reproducible: Always

Steps to Reproduce:
1. Create a transaction which specifies either an account or null in the
Category/Account field.
2. Create a report with "Organize: By Payee".


Actual Results:  
Specified transaction is not shown in report.

Expected Results:  
Specified transaction is shown in report.

1. Perhaps the required fix is to add a "Include transactions without a
category" option on the Report Configuration | Categories tab.

2. Oddly, if "Organize: By Accounts" is selected, then the specified
transactions are displayed.

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


[kdenlive] [Bug 364837] High CPU usage when kdenlive window is on top

2016-08-02 Thread BobSCA via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364837

--- Comment #10 from BobSCA  ---
I just did an upgrade from the kdenlive-master ppa and found that I still have
the problem. 

I'm not sure if the above commit into the Applications/16.08 branch is
currently merged and compiled on that ppa. Version shows as 16.11.70.

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


[kdenlive] [Bug 364837] High CPU usage when kdenlive window is on top

2016-07-03 Thread BobSCA via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364837

--- Comment #3 from BobSCA  ---
Thanks for your response, Jean-Baptiste. I tried resizing the bin from very
narrow to full window width, and even turned off the bin display and every
other windows shown in the View menu. CPU usage remains unchanged.

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


[kdenlive] [Bug 364837] New: High CPU usage when kdenlive window is on top

2016-06-27 Thread BobSCA via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364837

Bug ID: 364837
   Summary: High CPU usage when kdenlive window is on top
   Product: kdenlive
   Version: 15.12.2
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: bobs_spa...@cox.net

When kdenlive is the top window and idle, high CPU utilization occurs as
follows:
compiz:100% 
Xorg: 25%.
kdenlive: 15%

Observed on kdenlive 15.12.3 and 16.07.70.
Opening any dialog in kdenlive, e.g. "New" or "Open" dialogs, drops CPU usage
to normal values while those dialogs remain open.

Reproducible: Always

Steps to Reproduce:
1. Start kdenlive.
2. Start "top" in a terminal window.
3. Position the two windows so that both can be seen, with kdenlive having the
focus.

Actual Results:  
High CPU utilization as described above.

Expected Results:  
Normal idle CPU utilization (typically no task >5%).

Running on a Windows 8.1 host in a Ubuntu VirtualBox VM with 3D acceleration
disabled.

If 3D acceleration is enabled in the VM, then CPU usage is reduced to:
compiz: 17%
Xorg: 12%
kdenlive: 15%

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


[kdenlive] [Bug 364833] Crash when adding .wtv (Windows Media Center) clip.

2016-06-27 Thread BobSCA via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364833

--- Comment #1 from BobSCA  ---
Correction: task FFplay mentioned above should be ffmpeg.

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


[kdenlive] [Bug 364833] New: Crash when adding .wtv (Windows Media Center) clip.

2016-06-27 Thread BobSCA via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364833

Bug ID: 364833
   Summary: Crash when adding .wtv (Windows Media Center) clip.
   Product: kdenlive
   Version: 16.04.0
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: bobs_spa...@cox.net

Attempting to add a video clip from Windows Media Center (.wtv) causes a crash. 

I've tested with two different files - a 1 hour and a 1 minute file. Both files
play OK in both FFplay and melt. They also load instantly and play fine in
kdenlive 0.9.6.

The following results are for Kdenlive version 16.07.70 (not a choice in above
dropdown).

1 minute file: Causes an immediate crash. Dump shown below.

1 hour file: Causes the screen to go gray, with some pretty scary noises like
I've never heard coming from the hard drive. It's a loud continuous vibration
at roughly 20 Hz. Even after I close the greyed-out kdenlive window, the
kdenlive and FFplay tasks continue to run and the hard drive noise continues.
Killing the FFplay task also kills the kdenlive task and stops the hard drive
noise.

In kdenlive 15.12.3, loading these files fails for a different (?) reason –
they create many (infinite?) clips in the project bin with repeated "Multi
Stream Clip" dialogs, taking about 1 minute to load each iteration with lots of
grey-screen time in between.

Reproducible: Always

Steps to Reproduce:
1. Load a .wfv file created by Windows Media Player. Sample file available at
https://dl.dropboxusercontent.com/u/52261998/kdenlive_crash_1.wtv.
2.
3.

Actual Results:  
Crash.

Expected Results:  
Not crash.

GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.04) 7.11.1
Copyright (C) 2016 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-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 kdenlive...Reading symbols from
/usr/lib/debug/.build-id/ac/8d7adb99369c4947dcc2683e0da41b9ae94b6e.debug...done.
done.
(gdb) run
Starting program: /usr/bin/kdenlive 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe2ed9700 (LWP 3060)]
[New Thread 0x7fffd9518700 (LWP 3061)]
[New Thread 0x7fffd8d00700 (LWP 3062)]
[New Thread 0x7fffd3fff700 (LWP 3063)]
[New Thread 0x7fffd3359700 (LWP 3065)]
[New Thread 0x7fffd2b58700 (LWP 3066)]
[Thread 0x7fffd2b58700 (LWP 3066) exited]
[New Thread 0x7fffd2b58700 (LWP 3067)]
[New Thread 0x7fffa2c43700 (LWP 3068)]
[New Thread 0x7fffa2442700 (LWP 3069)]
[New Thread 0x7fffa1a09700 (LWP 3070)]
[New Thread 0x7fffa0a08700 (LWP 3071)]
[New Thread 0x7fff9bfff700 (LWP 3072)]
"This is an untested development version. Always backup your data"
Removing cache at "/home/bob/.cache/kdenlive-thumbs.kcache"
[New Thread 0x7fff9a461700 (LWP 3075)]
[Thread 0x7fff9a461700 (LWP 3075) exited]
[New Thread 0x7fff9a461700 (LWP 3077)]
WARNING: bool Phonon::FactoryPrivate::createBackend() phonon backend plugin
could not be loaded
WARNING: bool Phonon::FactoryPrivate::createBackend() phonon backend plugin
could not be loaded
WARNING: bool Phonon::FactoryPrivate::createBackend() phonon backend plugin
could not be loaded
WARNING: bool Phonon::FactoryPrivate::createBackend() phonon backend plugin
could not be loaded
WARNING: Phonon::createPath: Cannot connect  Phonon::MediaObject ( no
objectName ) to  Phonon::AudioOutput ( no objectName ).
WARNING: bool Phonon::FactoryPrivate::createBackend() phonon backend plugin
could not be loaded
WARNING: bool Phonon::FactoryPrivate::createBackend() phonon backend plugin
could not be loaded
OpenGL vendor:  "VMware, Inc."
OpenGL renderer:  "Gallium 0.4 on llvmpipe (LLVM 3.8, 128 bits)"
OpenGL Threaded:  false
OpenGL ARG_SYNC:  true
OpenGL OpenGLES:  false
[New Thread 0x7fff9956d700 (LWP 3078)]
[New Thread 0x7fff98d6c700 (LWP 3079)]
OpenGL vendor:  "VMware, Inc."
OpenGL renderer:  "Gallium 0.4 on llvmpipe (LLVM 3.8, 128 bits)"
OpenGL Threaded:  false
OpenGL ARG_SYNC:  true
OpenGL OpenGLES:  false
[New Thread 0x7fff8fffe700 (LWP 3080)]
[New Thread 0x7fff8f7fd700 (LWP 3081)]
[New Thread 0x7fff8effc700 (LWP 3082)]
QXcbConnection: XCB error: 8 (BadMatch), sequence: 576, resource id: 62914576,
major code: 154 (Unknown), minor code: 11
KServiceTypeTrader: serviceType "ThumbCreator" not found

[kmymoney4] [Bug 362263] OFX import transactions inherit split from preexisting transaction

2016-04-25 Thread BobSCA via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362263

--- Comment #2 from BobSCA  ---
I found that one can workaround this for any particular payee by specify the
"No Matching" option for the payee. Of course that precludes automatically
setting the account during the import too.

Note that the inherited splits included not only the accounts specified in the
split, but the exact dollar amounts which were not at all related to the dollar
amount of the imported splits. The split information therefore made no sense,
and it's hard to imagine that anyone would want such a feature.

It's pretty annoying to import hundreds of transactions before realizing that
many of them have nonsensical splits defined and must all be manually
corrected.

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


[kmymoney4] [Bug 362263] New: OFX import transactions inherit split from preexisting transaction

2016-04-25 Thread BobSCA via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362263

Bug ID: 362263
   Summary: OFX import transactions inherit split from preexisting
transaction
   Product: kmymoney4
   Version: 4.7.2
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kmymoney-de...@kde.org
  Reporter: bobs_spa...@cox.net

Did an OFX import. The result was that apparently every imported deposit was
assigned the split details from a preexisting transaction which had payer =
"Deposit".

Reproducible: Always

Steps to Reproduce:
1. Create deposit transaction with payer = "Deposit" and which contains a
split.
2. Do OFX import.

Actual Results:  
All imported imported transactions with payer "Deposit" inherit the split
details from the pre-existing deposit.

Expected Results:  
Imported transactions should be not inherit split info.

If name of preexisting condition is changed from "Deposit" then the issue does
not occur.

Imported OFX deposit transactions were of the following format:

  CREDIT
  2016022912.000
  0.33
  [VALUE REDACTED]
  Deposit 0.050% %% Apy Earned 
  Deposit 0.050% %% Apy Earned  0.05% 02/01/16 To 02/29/16 %%


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