[kmymoney] [Bug 469431] Need better way to handle changes in stock price quote source

[Brendan]

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

Brendan  changed:

   What|Removed |Added

 CC||k...@coupe7.com

--- Comment #48 from Brendan  ---
As a user for almost 20 years I find this comment pretty insulting to the
developers and the users.

"kmm is not for the masses, it is an experimental tool with no visible
development, non existent documentation and "mail lists"."

Go find a version from 20 years ago and tell me there has been no visible
development. I'm extremely glad that's not what I was told before I started
using KMM. I have found the developers to be very helpful when I run into
issues and Thomas has gone way above and beyond helping track down online
banking issues for me over the years.

While development has essentially stopped on 5.1 for a while now, that's
because the focus is on the master version, which you are welcome to run. Of
course, it's not released so it's actually experimental to some degree.

The Yahoo issue has been a problem, but blaming the KMM team make little sense.
It would be nice to find the perfect solution, but sometimes that's in the eye
of the beholder. I have no problem editing the Yahoo settings when there is a
problem. Tracking down the latest settings is usually as easy as asking on the
mailing list if you don't find it there already. I also compile KMM weekly
(when things were changing) so updating through the code works for me but
releases are pretty rare so that's not a great option for everyone. Maybe a
simple link on the  "Update Stock and Currency" window to a web page that has
the latest settings for online quotes would help. Maybe a link to the KMM
Online Quote Settings page in the same window would also help, but I'm not sure
that's possible with the existing code.

For now, I hope they focus on releasing the master and then maybe some wishlist
items can get in their queue.

They say you get what you pay for but I think KMM is an example where we get a
lot more than we pay for.

I suggest you either offer helpful suggestions and deal with what we have or
find some other program to track you finances. Or better yet, join the
development team and make some visible improvements.

Brendan Coupe

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

[kmymoney] [Bug 475674] New: Create a Lock File when running KMyMoney

[Brendan]

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

Bug ID: 475674
   Summary: Create a Lock File when running KMyMoney
Classification: Applications
   Product: kmymoney
   Version: git (master)
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: kmymoney-de...@kde.org
  Reporter: 3...@coupe7.com
  Target Milestone: ---

I use KMM on multiple systems. My data file is shared between my various Linux
systems and several backup servers via Synthing.

When I forget to close KMM before opening it on a different system, I can end
up with 2 versions of the KMM data file.

I have created a workaround with a script that starts KMM (kmymoney.sh). It
checks to see if there is a lock file present at the designated path. If the
lock file is present, I use Zenity to display a message that file is already
open on a different system and I display the name of the system where KMM is
already running.

If the lock file is not present, I create the lock file which has the same name
as the KMM data file that I am trying to open plus .lock. The lock file has the
name of the host that is running KMM. Synthing syncs this file to my backup
systems and any system that is online immediately. If I put a system to sleep
without closing KMM, the lock file is still present. If I then wake up or boot
up a different system, it will receive the lock file and prevent me from
running KMM with the same data file.

It would be ideal if KMM handled all of this internally. By default i think the
lock file should be stored in the same path as the data file but it might make
sense to make it configurable. The home directory would not work for my setup
since I do not sync my entire home directory with Syncthing.

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

[plasmashell] [Bug 466917] New: CPU Temperature in Fahrenheit

[Brendan]

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

Bug ID: 466917
   Summary: CPU Temperature in Fahrenheit
Classification: Plasma
   Product: plasmashell
   Version: master
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: System Monitor
  Assignee: plasma-b...@kde.org
  Reporter: bren...@bdwy.app
CC: ahiems...@heimr.nl, notm...@gmail.com
  Target Milestone: 1.0

Would love it if I had the option to display the CPU temperature in Fahrenheit
instead of Celsius in the "Total CPU Use" widget.

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

[Powerdevil] [Bug 465987] New: Power Module (power devil or whatever) won't start at all with latest plasma.

[Brendan Rankin]

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

Bug ID: 465987
   Summary: Power Module (power devil or whatever) won't start at
all with latest plasma.
Classification: Plasma
   Product: Powerdevil
   Version: 5.27.0
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: brendan.ran...@gmail.com
CC: m...@ratijas.tk
  Target Milestone: ---

Application: org_kde_powerdevil (5.27.0)

Qt Version: 5.15.8
Frameworks Version: 5.103.0
Operating System: Linux 6.1.11-200.fc37.x86_64 x86_64
Windowing System: X11
Distribution: Fedora Linux 37 (Workstation Edition)
DrKonqi: 5.27.0 [KCrashBackend]

-- Information about the crash:
The relevant stack trace/dump is attached. I haven't done anything different or
special compared to what I used to do in the previous revision. The only
"unique" thing that I'm doing is logging in remotely via x2go to a "x" plasma
session.

Thx much!

Brendan

The crash can be reproduced every time.

-- Backtrace:
Application: KDE Power Management System (org_kde_powerdevil), signal: Aborted

[KCrash Handler]
#4  0x7fb002eafe5c in __pthread_kill_implementation () at /lib64/libc.so.6
#5  0x7fb002e5fa76 in raise () at /lib64/libc.so.6
#6  0x7fb002e497fc in abort () at /lib64/libc.so.6
#7  0x7fb0030d7e80 in __gnu_debug::_Safe_sequence_base::_M_get_mutex() ()
at /lib64/libstdc++.so.6
#8  0x7fafe96c3d37 in  () at /lib64/libKF5ScreenDpms.so.8
#9  0x7fb0042b436f in PowerDevil::ActionPool::init(PowerDevil::Core*) () at
/lib64/libpowerdevilcore.so.2
#10 0x7fb0042bbded in PowerDevil::Core::onBackendReady() () at
/lib64/libpowerdevilcore.so.2
#11 0x7fb0036d0e96 in void doActivate(QObject*, int, void**) () at
/lib64/libQt5Core.so.5
#12 0x7fafea56eada in PowerDevilUPowerBackend::initWithBrightness(bool) ()
at /usr/lib64/qt5/plugins/kf5/powerdevil/powerdevilupowerbackend.so
#13 0x7fb0036d0e96 in void doActivate(QObject*, int, void**) () at
/lib64/libQt5Core.so.5
#14 0x7fafea565fd3 in
PowerDevilUPowerBackend::brightnessSupportQueried(bool) () at
/usr/lib64/qt5/plugins/kf5/powerdevil/powerdevilupowerbackend.so
#15 0x7fb0036d0e96 in void doActivate(QObject*, int, void**) () at
/lib64/libQt5Core.so.5
#16 0x7fb0041333d9 in KJob::result(KJob*, KJob::QPrivateSignal) () at
/lib64/libKF5CoreAddons.so.5
#17 0x7fb004138e3b in KJob::finishJob(bool) () at
/lib64/libKF5CoreAddons.so.5
#18 0x7fb0036d0e96 in void doActivate(QObject*, int, void**) () at
/lib64/libQt5Core.so.5
#19 0x7faff002a863 in KAuth::DBusHelperProxy::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) [clone .part.0] () at
/usr/lib64/qt5/plugins/kauth/helper/kauth_helper_plugin.so
#20 0x7faff002af41 in
KAuth::DBusHelperProxy::qt_metacall(QMetaObject::Call, int, void**) () at
/usr/lib64/qt5/plugins/kauth/helper/kauth_helper_plugin.so
#21 0x7fb0040670bb in QDBusConnectionPrivate::deliverCall(QObject*, int,
QDBusMessage const&, QVector const&, int) () at /lib64/libQt5DBus.so.5
#22 0x7fb0036c8134 in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5
#23 0x7fb00369d4e8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /lib64/libQt5Core.so.5
#24 0x7fb0036a0854 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /lib64/libQt5Core.so.5
#25 0x7fb0036eeb07 in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () at /lib64/libQt5Core.so.5
#26 0x7fb002119cbf in g_main_context_dispatch () at /lib64/libglib-2.0.so.0
#27 0x7fb00216f598 in g_main_context_iterate.constprop () at
/lib64/libglib-2.0.so.0
#28 0x7fb002116f40 in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#29 0x7fb0036ee5fa in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#30 0x7fb00369bf3a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#31 0x7fb0036a4002 in QCoreApplication::exec() () at /lib64/libQt5Core.so.5
#32 0x564847437a45 in main ()
[Inferior 1 (process 1069144) detached]

Reported using DrKonqi

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

[kdf] [Bug 81227] Wrong amount of free space reported for FAT32 partitions

[Brendan]

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

--- Comment #7 from Brendan  ---
As I stated in 2009 and 2018, I don't have the environment to test this
anymore. Could you stop asking?

On 23/12/22 11:28, Justin Zobel wrote:
> https://bugs.kde.org/show_bug.cgi?id=81227
> 
> Justin Zobel  changed:
> 
> What|Removed |Added
> 
>   Status|REPORTED|NEEDSINFO
>   Resolution|--- |WAITINGFORINFO
> 
> --- Comment #6 from Justin Zobel  ---
> Thank you for reporting this issue in KDE software. As it has been a while
> since this issue was reported, can we please ask you to see if you can
> reproduce the issue with a recent software version?
> 
> If you can reproduce the issue, please change the status to "REPORTED" when
> replying. Thank you!
>

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

[kmymoney] [Bug 400465] Imported transactions are not matched against reconciled transactions

[Brendan]

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

Brendan <3...@coupe7.com> changed:

   What|Removed |Added

 CC||3...@coupe7.com

--- Comment #6 from Brendan <3...@coupe7.com> ---
Thomas changed this several years ago when I ran into a problem with KMM not
being able to detect duplicate transactions. He added a second method to detect
duplicates. You can find the setting in both the manual OFX import file
selector and in the direct connect setup for an account.

The setting is called "Method to detect duplicate transactions during import".
There are 2 options, "OFX FITID" and "KMyMoney Hash". The KMM hash fixed my
import problem when the bank did not sent the same FITID each time you
downloaded a transaction.

This is not an immediate fix since switching this setting to KMM Hash will
result in none of the transactions matching the previous transactions since
they used FITID. 

It's also not perfect, I still get duplicate transactions from one bank where
the transactions don't always match. I can limit the extent of the problem by
limiting the date range of the download so I haven't dug in to figure out what
is going wrong.

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

[krita] [Bug 461309] Fuzzy Dab ignores curves calculation mode, appears to just use multiply.

[Brendan]

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

Brendan  changed:

   What|Removed |Added

  Component|Brush Engine/Shape  |Brush engines

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

[krita] [Bug 461309] New: Fuzzy Dab ignores curves calculation mode, appears to just use multiply.

[Brendan]

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

Bug ID: 461309
   Summary: Fuzzy Dab ignores curves calculation mode, appears to
just use multiply.
Classification: Applications
   Product: krita
   Version: 5.0.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Brush Engine/Shape
  Assignee: krita-bugs-n...@kde.org
  Reporter: abc...@yahoo.com
  Target Milestone: ---

SUMMARY

STEPS TO REPRODUCE
1. Select Basic-5 Size brush
2. Enable Fuzzy Dab on Size
3. Change curves calculation mode to Maximum
4. Draw a line with the mouse (which always registers as 100% pressure)

OBSERVED RESULT

Brush size changes randomly per dab

EXPECTED RESULT

Every dab should be at 100% size.

SOFTWARE/OS VERSIONS

Krita

 Version: 5.0.2
 Languages: en_US, en
 Hidpi: true

Qt

  Version (compiled): 5.12.12
  Version (loaded): 5.12.12

OS Information

  Build ABI: x86_64-little_endian-lp64
  Build CPU: x86_64
  CPU: x86_64
  Kernel Type: linux
  Kernel Version: 5.8.0-50-generic
  Pretty Productname: Ubuntu 20.04.2 LTS
  Product Type: ubuntu
  Product Version: 20.04
  Desktop: LXDE

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

[krita] [Bug 407380] Softness sensor does nothing when using a predefined brush tip

[Brendan]

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

--- Comment #8 from Brendan  ---
Any movement on this? I recently tested the Softness setting on an Auto brush,
not a predefined one, and I still can't tell the difference.

1) Select the brush Ink-1 Precision
2) draw a stroke at the default 10% softness
3) change the softness to 100%, draw another stroke.

I couldn't see a lick of difference between the two, no matter what other brush
elements I changed.

This was on Krita 5.0.2 on Lubuntu from the x86_64 appimage.

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

[kmymoney] [Bug 460131] Make it possible/easier to open account's web site to download transactions

[Brendan]

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

--- Comment #3 from Brendan <3...@coupe7.com> ---
I'm not sure I have any banks where it is possible (or at least obvious) to get
the ofx file directly from a URL. If it was, seems like a way to simulate
direct connect so why save the file, just import it.

How does KMM handle an ofx file with multiple accounts in it (your Merrill
Lynch accounts)? I've never tried it.

Every bank that I currently download ofx files from manually seems to do things
their own way. I have more than one account at some of the banks and have
always downloaded them separately. At a credit union, matching is a disaster so
I'm always filtering by date to minimize duplicates.

It's for this reason, I'm proposing a way to import all saved ofx files along
with any remaining direct connect accounts (or separately, if that's
preferred). I assume it will take a fair amount of work to save the files
manually but if that can be simplified, that would be even better. I'm not
concerned about links to the banks in KMM, I always have one Firefox window
open with all of my banks in tabs so getting to the web page is not an issue.

I'm imaging this as an update to the OXF Importer plugin, but I'm not sure how
involved that would be. Maybe a new plugin, which would be a simplified version
of the OFX Importer. I could see it starting out basic and improving with
experience.

I currently have 6 or 7 accounts where I download the ofx file once a month and
have to manually import the file to KMM. Now I've added my Chase credit card,
Which I will probably import 4 to 6 times a month, basically doubling the
number of times I have to go File, Import, OXF, and select the file. Automating
just this part would be very helpful.

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

[kmymoney] [Bug 460131] Make it possible/easier to open account's web site to download transactions

[Brendan]

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

Brendan <3...@coupe7.com> changed:

   What|Removed |Added

 CC||3...@coupe7.com

--- Comment #1 from Brendan <3...@coupe7.com> ---
I think this would help but I have another suggestion, which would make it
easier to import OFX files downloaded from multiple banks. The number of manual
imports is increasing, thank Chase.

Currently you save the ofx or qfx file somewhere on your system. Then you have
to import each saved ofx/qfx file one by one. As the number of accounts that
require manual selection increases this becomes a bigger burden.

It would be nice if the process could be included as part of the "Update
account" and "Update all accounts" process. This could be done a couple of
different ways. A global path where the ofx/qfx files are saved could be set
and then all existing ofx/qfx files are imported when you run "Update all
accounts". Another option would be to define the path and file name for each
ofx/qfx file for each account. This would allow you to update one account with
the latest ofx/qfx file or update them all along with accounts that are still
available directly from the bank via KMM ofx import.

I can make this a new wishlist item if this makes sense.

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

[www.kde.org] [Bug 451486] md5sums of krita-5.0.2.dmg in https://download.kde.org/stable/krita/5.0.2/md5sum.txt is wrong

[Brendan]

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

--- Comment #11 from Brendan  ---
Thanks for that. 

So, these checksums (being autogenerated by server) verify whether the version
on the server is the same as the version downloaded.  Chain of trust from
developer to user is assured by GPG signature from Krita.org?  

Where is the public key?

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

[www.kde.org] [Bug 451486] md5sums of krita-5.0.2.dmg in https://download.kde.org/stable/krita/5.0.2/md5sum.txt is wrong

[Brendan]

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

--- Comment #5 from Brendan  ---
Looks like something wrong at my end? Tried today, downloaded fine. 
That said, I don't see sha256sum hashes published anywhere.

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

[www.kde.org] [Bug 451486] md5sums of krita-5.0.2.dmg in https://download.kde.org/stable/krita/5.0.2/md5sum.txt is wrong

[Brendan]

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

Brendan  changed:

   What|Removed |Added

 CC||bunf2014@apps.opensourcelaw
   ||.biz

--- Comment #3 from Brendan  ---
I have just downloaded the Krita 5.0.5 appimage 4 times. Each of the binaries
differs. None match the md5sum in the md5sum file.
Is it possible that the server is adding some header information?

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

[kmymoney] [Bug 376514] Encrpyption option not available

[Brendan]

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

Brendan <3...@coupe7.com> changed:

   What|Removed |Added

 CC||3...@coupe7.com

--- Comment #6 from Brendan <3...@coupe7.com> ---
Since Fedora 35 is ten versions newer and I have never had a problem with
encryption in Fedora, since long before Fedora 25,, I say close this bug.

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

[kmymoney] [Bug 450016] Attempting KMyMoney 5.0.8 "Currencies" Maintenance, Application Crash

[Brendan]

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

Brendan <3...@coupe7.com> changed:

   What|Removed |Added

 CC||3...@coupe7.com

--- Comment #6 from Brendan <3...@coupe7.com> ---
I created build scripts for KMM that I have shared here before. You are welcome
to try them.

You cat get them here:

https://drive.google.com/drive/folders/1sfo2HgzaCCSb3d7pjl3To50yoQT5BaXM?usp=sharing

Let me know if you have any questions.

Brendan

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

[plasma-systemmonitor] [Bug 437089] On Wayland, Windows that were closed when maximized will open in the maximized position, but not the maximized state

[Brendan William]

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

Brendan William  changed:

   What|Removed |Added

 CC||bt.will...@outlook.com

--- Comment #18 from Brendan William  ---
I have trouble believing this is something that needs to be resolved by
individual apps. This effects various native Wayland applications, particularly
Qt ones. I have experienced this with Dolphin, Konsole, MultiMC 5, Kate,
Kalendar, System Settings, Discover, and several others, and also with VS Code
running with relevant launch flags to use Ozone platform under Wayland.

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

[extra-cmake-modules] [Bug 443532] New: [PATCH] kde_package_app_templates makes tarballs non-reproducible with GNU tar.

[Brendan]

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

Bug ID: 443532
   Summary: [PATCH] kde_package_app_templates makes tarballs
non-reproducible with GNU tar.
   Product: extra-cmake-modules
   Version: 5.86.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: ecm-bugs-n...@kde.org
  Reporter: m...@brendan.scot
  Target Milestone: ---

Created attachment 142288
  --> https://bugs.kde.org/attachment.cgi?id=142288=edit
Patch to make kde_package_app_templates reproducible.

SUMMARY
kde_package_app_templates embeds timestamps and GID's in tarballs with GNU tar. 

The attached patch fixes this in all the cases I observed.
Timestamp embedding should be fixed my the use of --mtime
GID, UID should be set to 0 with --owner=0 --group=0

STEPS TO REPRODUCE
1. Build any of the packages with templates such as below in Guix, or in some
build environment where the root GID can differ.
 - kio
 - akonadi
 - plasma-framework
 - krunner
 - kparts
 - ktexteditor
 - kirigami

OBSERVED RESULT
diffoscope output from building kio:


│ │ │ │   ---
/gnu/store/j83x88sa4967i4yndf6r7zwm2vz3xvnp-kio-5.86.0/share/kdevappwizard/templates/ioslave.tar.bz2
│ │ │ ├── +++
/gnu/store/j83x88sa4967i4yndf6r7zwm2vz3xvnp-kio-5.86.0-check/share/kdevappwizard/templates/ioslave.tar.bz2
│ │ │ │ ├── ioslave.tar
│ │ │ │ │ ├── file list
│ │ │ │ │ │ @@ -1,16 +1,16 @@
│ │ │ │ │ │ -drwxr-xr-x   0  99930 2021-10-08
19:25:03.199470 ./
│ │ │ │ │ │ --rw-r--r--   0  9993  651 1970-01-01
00:00:01.00 ./CMakeLists.txt
│ │ │ │ │ │ -drwxr-xr-x   0  99930 1970-01-01
00:00:01.00 ./LICENSES/
│ │ │ │ │ │ --rw-r--r--   0  999325906 1970-01-01
00:00:01.00 ./LICENSES/LGPL-2.1-or-later.txt
│ │ │ │ │ │ --rwxr-xr-x   0  9993  121 1970-01-01
00:00:01.00 ./Messages.sh
│ │ │ │ │ │ --rw-r--r--   0  9993 1498 1970-01-01
00:00:01.00 ./README.md
│ │ │ │ │ │ --rwxr-xr-x   0  9993  487 1970-01-01
00:00:01.00 ./install.sh
│ │ │ │ │ │ --rw-r--r--   0  9993   65 1970-01-01
00:00:01.00 ./ioslave.kdevtemplate
│ │ │ │ │ │ -drwxr-xr-x   0  99930 1970-01-01
00:00:01.00 ./src/
│ │ │ │ │ │ --rw-r--r--   0  9993 4630 1970-01-01
00:00:01.00 ./src/%{APPNAMELC}.cpp
│ │ │ │ │ │ --rw-r--r--   0  9993  636 1970-01-01
00:00:01.00 ./src/%{APPNAMELC}.h
│ │ │ │ │ │ --rw-r--r--   0  9993  905 1970-01-01
00:00:01.00 ./src/CMakeLists.txt
│ │ │ │ │ │ --rw-r--r--   0  9993 2025 1970-01-01
00:00:01.00 ./src/mydatasystem.cpp
│ │ │ │ │ │ --rw-r--r--   0  9993 1252 1970-01-01
00:00:01.00 ./src/mydatasystem.h
│ │ │ │ │ │ --rw-r--r--   0  9993  415 1970-01-01
00:00:01.00 ./src/myproto.json
│ │ │ │ │ │ --rwxr-xr-x   0  9993  138 1970-01-01
00:00:01.00 ./uninstall.sh
│ │ │ │ │ │ +drwxr-xr-x   0  99730 2021-10-09
02:23:54.861213 ./
│ │ │ │ │ │ +-rw-r--r--   0  9973  651 1970-01-01
00:00:01.00 ./CMakeLists.txt
│ │ │ │ │ │ +drwxr-xr-x   0  99730 1970-01-01
00:00:01.00 ./LICENSES/
│ │ │ │ │ │ +-rw-r--r--   0  997325906 1970-01-01
00:00:01.00 ./LICENSES/LGPL-2.1-or-later.txt
│ │ │ │ │ │ +-rwxr-xr-x   0  9973  121 1970-01-01
00:00:01.00 ./Messages.sh
│ │ │ │ │ │ +-rw-r--r--   0  9973 1498 1970-01-01
00:00:01.00 ./README.md
│ │ │ │ │ │ +-rwxr-xr-x   0  9973  487 1970-01-01
00:00:01.00 ./install.sh
│ │ │ │ │ │ +-rw-r--r--   0  9973   65 1970-01-01
00:00:01.00 ./ioslave.kdevtemplate
│ │ │ │ │ │ +drwxr-xr-x   0  99730 1970-01-01
00:00:01.00 ./src/
│ │ │ │ │ │ +-rw-r--r--   0  9973 4630 1970-01-01
00:00:01.00 ./src/%{APPNAMELC}.cpp
│ │ │ │ │ │ +-rw-r--r--   0  9973  636 1970-01-01
00:00:01.00 ./src/%{APPNAMELC}.h
│ │ │ │ │ │ +-rw-r--r--   0  9973  905 1970-01-01
00:00:01.00 ./src/CMakeLists.txt
│ │ │ │ │ │ +-rw-r--r--   0  9973 2025 1970-01-01
00:00:01.00 ./src/mydatasystem.cpp
│ │ │ │ │ │ +-rw-r--r--   0  9973 1252 1970-01-01
00:00:01.00 ./src/mydatasystem.h
│ │ │ │ │ │ +-rw-r--r--   0  9973  415 1970-01-01
00:00:01.00 ./src/myproto.json
│ │ │ │ │ │ +-rwxr-xr-x   0  9973  138 1970-01-01
00:00:01.00 ./uninstall.sh
│ │ │ │ ├── stat {}
│ │ │ │ │ @@ -1,8 +1,8 @@
│ │ │ │ │  
│ │ │ │ │ -  Size: 13047Blocks: 32 IO Block: 4096   regular
file
│ │ │ │ │ -Links: 3
│ │ │ │ │ +  Size: 13069Blocks: 32 IO Block: 4096   regular
file
│ │ │ │ │ +Links: 1
│ │ │ │ │  Access: 

[frameworks-kdav] [Bug 442935] New: Inconsistent test failure in test kdav-davcollectionsmultifetchjobtest

[Brendan]

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

Bug ID: 442935
   Summary: Inconsistent test failure in test
kdav-davcollectionsmultifetchjobtest
   Product: frameworks-kdav
   Version: 5.86.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdelibs-b...@kde.org
  Reporter: m...@brendan.scot
  Target Milestone: ---

I'm updating KDE software for the Guix GNU/Linux distribution. Currently I'm
building kdav and roughly 1/4 times the kdav-davcollectionsmultifetchjobtest
testfails. 

STEPS TO REPRODUCE
I'm updating KDE software in the Guix GNU/Linux distribution, so reproducing
the result would involve installing Guix, and running something like:

git clone -b wip-kde-updates-kgpg-bug https://notabug.org/Brendan/guix.git
cd guix
guix environment guix
./bootstrap
./configure --localstatedir=/var
make -j
./pre-inst-env guix build kdav
./pre-inst-env guix build --no-grafts --check --rounds=5

OBSERVED RESULT
4/6 Test #4: kdav-davcollectionsmultifetchjobtest ...***Failed0.03 sec
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to
'/tmp/guix-build-kdav-5.86.0.drv-0/runtime-nixbld'
* Start testing of DavCollectionsMultiFetchJobTest *
Config: Using QtTest library 5.15.2, Qt 5.15.2 (x86_64-little_endian-lp64
shared (dynamic) release build; by GCC 7.5.0), unknown unknown
PASS   : DavCollectionsMultiFetchJobTest::initTestCase()
QWARN  : DavCollectionsMultiFetchJobTest::runSuccessfullTest() QStandardPaths:
XDG_RUNTIME_DIR not set, defaulting to
'/tmp/guix-build-kdav-5.86.0.drv-0/runtime-nixbld'
QWARN  : DavCollectionsMultiFetchJobTest::runSuccessfullTest() QStandardPaths:
XDG_RUNTIME_DIR not set, defaulting to
'/tmp/guix-build-kdav-5.86.0.drv-0/runtime-nixbld'
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to
'/tmp/guix-build-kdav-5.86.0.drv-0/runtime-nixbld'
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to
'/tmp/guix-build-kdav-5.86.0.drv-0/runtime-nixbld'
QDEBUG : DavCollectionsMultiFetchJobTest::runSuccessfullTest() Read client
request "PROPFIND /carddav HTTP/1.1\r\n"
QDEBUG : DavCollectionsMultiFetchJobTest::runSuccessfullTest() Read client
request "PROPFIND /caldav HTTP/1.1\r\n"
QDEBUG : DavCollectionsMultiFetchJobTest::runSuccessfullTest() Read client
request "PROPFIND /carddav/dfaure%40example.com/ HTTP/1.1\r\n"
QDEBUG : DavCollectionsMultiFetchJobTest::runSuccessfullTest() Read client
request "PROPFIND /caldav/dfaure%40example.com/ HTTP/1.1\r\n"
FAIL!  : DavCollectionsMultiFetchJobTest::runSuccessfullTest() Compared values
are not the same
   Actual   (calendar.displayName())  : "My Address Book"
   Expected (QStringLiteral("Test1 User")): "Test1 User"
   Loc:
[/tmp/guix-build-kdav-5.86.0.drv-0/kdav-5.86.0/autotests/davcollectionsmultifetchjobtest.cpp(56)]
QDEBUG : DavCollectionsMultiFetchJobTest::shouldFailOnError() Read client
request "PROPFIND /caldav HTTP/1.1\r\n"
QDEBUG : DavCollectionsMultiFetchJobTest::shouldFailOnError() Read client
request "PROPFIND /does_not_exist HTTP/1.1\r\n"
QDEBUG : DavCollectionsMultiFetchJobTest::shouldFailOnError() Read client
request "PROPFIND /caldav/dfaure%40example.com/ HTTP/1.1\r\n"
PASS   : DavCollectionsMultiFetchJobTest::shouldFailOnError()
PASS   : DavCollectionsMultiFetchJobTest::cleanupTestCase()
Totals: 3 passed, 1 failed, 0 skipped, 0 blacklisted, 21ms
* Finished testing of DavCollectionsMultiFetchJobTest *


EXPECTED RESULT
The test passes.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: GNU Guix.
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 5.86.0 
Qt Version: 5.12.5

ADDITIONAL INFORMATION

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

[frameworks-sonnet] [Bug 442931] New: Build is not reproducible

[Brendan]

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

Bug ID: 442931
   Summary: Build is not reproducible
   Product: frameworks-sonnet
   Version: 5.86.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: martin.sandsm...@kde.org
  Reporter: m...@brendan.scot
CC: kdelibs-b...@kde.org
  Target Milestone: ---

Created attachment 141895
  --> https://bugs.kde.org/attachment.cgi?id=141895=edit
diffoscope output.

I am packaging sonnet for the Guix GNU/Linux distribution. packages in Guix are
all build in a clean isolated environment. Repeatedly building sonnet results
in a differing libKF5SonnetCore.so.5.86.0. This also occurs for sonnet 5.70

STEPS TO REPRODUCE
1. guix build sonnet --no-grafts
2. guix build sonnet --no-grafts --check --keep-failed

OBSERVED RESULT
See attached diffoscope output. There is quite a large part of the binary that
differs. I'm not really sure how it occurs. Please ask if you need any more
info.

EXPECTED RESULT
The builds should be identical. See  https://reproducible-builds.org/

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma:  Guix
(available in About System)
KDE Plasma Version: 21.08.1
KDE Frameworks Version: 5.86.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
Just ask if you need any more information.

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

[kgpg] [Bug 442886] New: Inconsistent test failure in test kgpg-import.

[Brendan]

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

Bug ID: 442886
   Summary: Inconsistent test failure in test kgpg-import.
   Product: kgpg
   Version: 21.08.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@opensource.sf-tec.de
  Reporter: m...@brendan.scot
  Target Milestone: ---

STEPS TO REPRODUCE
I'm updating KDE software in the Guix GNU/Linux distribution, so reproducing
the result would involve installing Guix, and running something like:

git clone -b wip-kde-updates-kgpg-bug https://notabug.org/Brendan/guix.git
cd guix
guix environment guix
./bootstrap
./configure --localstatedir=/var
make -j
./pre-inst-env guix build kgpg

OBSERVED RESULT

Running tests...
/gnu/store/qixwn3dw6glj848hrr3h8fxm6s7wzxm3-cmake-minimal-3.16.5/bin/ctest
--force-new-ctest-process 
Test project /tmp/guix-build-kgpg-21.08.1.drv-0/build
  Start  1: kgpg-import
 1/11 Test  #1: kgpg-import ..***Failed6.14 sec
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to
'/tmp/guix-build-kgpg-21.08.1.drv-0/runtime-nixbld'
* Start testing of KGpgImportTest *
Config: Using QtTest library 5.15.2, Qt 5.15.2 (x86_64-little_endian-lp64
shared (dynamic) release build; by GCC 7.5.0), unknown unknown
PASS   : KGpgImportTest::initTestCase()
gpg: keybox
'/tmp/guix-build-kgpg-21.08.1.drv-0/kgpg-import-BoYZBL/.gnupg/pubring.kbx'
created
gpg: /tmp/guix-build-kgpg-21.08.1.drv-0/kgpg-import-BoYZBL/.gnupg/trustdb.gpg:
trustdb created
gpg: key BA7695F3C550DF14: public key "Test KGpg" imported
gpg: Total number processed: 1
gpg:   imported: 1
PASS   : KGpgImportTest::testImportTextKey()
gpg: keybox
'/tmp/guix-build-kgpg-21.08.1.drv-0/kgpg-import-BoYZBL/.gnupg/pubring.kbx'
created
gpg: /tmp/guix-build-kgpg-21.08.1.drv-0/kgpg-import-BoYZBL/.gnupg/trustdb.gpg:
trustdb created
gpg: key BA7695F3C550DF14: public key "Test KGpg" imported
gpg: can't connect to the agent: IPC connect call failed
gpg: Total number processed: 1
gpg:   imported: 1
FAIL!  : KGpgImportTest::testImportIdsAll() Compared values are not the same
   Actual   (result)  : 2
   Expected (static_cast(KGpgTransaction::TS_OK)): 0
   Loc:
[/tmp/guix-build-kgpg-21.08.1.drv-0/kgpg-21.08.1/tests/kgpgimport.cpp(83)]
gpg: keybox
'/tmp/guix-build-kgpg-21.08.1.drv-0/kgpg-import-BoYZBL/.gnupg/pubring.kbx'
created
gpg: /tmp/guix-build-kgpg-21.08.1.drv-0/kgpg-import-BoYZBL/.gnupg/trustdb.gpg:
trustdb created
[GNUPG:] KEY_CONSIDERED FBAF08DD7D9D0921C15DDA9FBA7695F3C550DF14 0
gpg: key BA7695F3C550DF14: public key "Test KGpg" imported
[GNUPG:] IMPORTED BA7695F3C550DF14 Test KGpg
[GNUPG:] IMPORT_OK 1 FBAF08DD7D9D0921C15DDA9FBA7695F3C550DF14
gpg: Total number processed: 1
gpg:   imported: 1
[GNUPG:] IMPORT_RES 1 0 1 0 0 0 0 0 0 0 0 0 0 0 0
QDEBUG : KGpgImportTest::testImportIdsUnchanged() Added Gpg key: 
"keys/kgpgtest_BA7695F3C550DF14_pub.asc"
gpg: key BA7695F3C550DF14: "Test KGpg" not changed
gpg: Total number processed: 1
gpg:  unchanged: 1
PASS   : KGpgImportTest::testImportIdsUnchanged()
gpg: keybox
'/tmp/guix-build-kgpg-21.08.1.drv-0/kgpg-import-BoYZBL/.gnupg/pubring.kbx'
created
gpg: /tmp/guix-build-kgpg-21.08.1.drv-0/kgpg-import-BoYZBL/.gnupg/trustdb.gpg:
trustdb created
gpg: key BA7695F3C550DF14: public key "Test KGpg" imported
gpg: Total number processed: 1
gpg:   imported: 1
PASS   : KGpgImportTest::testImportKeyFromFile()
gpg: keybox
'/tmp/guix-build-kgpg-21.08.1.drv-0/kgpg-import-BoYZBL/.gnupg/pubring.kbx'
created
gpg: /tmp/guix-build-kgpg-21.08.1.drv-0/kgpg-import-BoYZBL/.gnupg/trustdb.gpg:
trustdb created
gpg: key BA7695F3C550DF14: public key "Test KGpg" imported
gpg: Total number processed: 1
gpg:   imported: 1
gpg: Note: '--status-fd=1' is not considered an option
gpg: Note: '--import' is not considered an option
gpg: Note: '--allow-secret-key-import' is not considered an option
gpg: Note: '--command-fd=0' is not considered an option
gpg: key BA7695F3C550DF14: "Test KGpg" not changed
gpg: can't open '--status-fd=1': No such file or directory
gpg: can't open '--import': No such file or directory
gpg: can't open '--allow-secret-key-import': No such file or directory
gpg: can't open '--command-fd=0': No such file or directory
gpg: key BA7695F3C550DF14: "Test KGpg" not changed
gpg: Total number processed: 2
gpg:  unchanged: 2
QDEBUG : KGpgImportTest::testImportSameKeyTwice() MESSAGES:  ("[GNUPG:]
IMPORTED BA7695F3C550DF14 Test KGpg", "[GNUPG:] IMPORT_OK 1
FBAF08DD7D9D0921C15DDA9FBA7695F3C550DF14", "[GNUPG:] IMPORT_RES 1 0 1 0 0 0 0 0
0 0 0 0 0 0 0", "[GNUPG:] IMPORT_OK 0
FBAF08DD7D9D0921C15DDA9FBA7695F3C550DF14", "[GNUP

[krita] [Bug 425845] Duplication of default brush preset tags

[brendan]

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

brendan  changed:

   What|Removed |Added

  Alias||krita, docker

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

[krita] [Bug 425845] Duplication of default brush preset tags

[brendan]

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

brendan  changed:

   What|Removed |Added

Summary|Duplication of default tags |Duplication of default
   ||brush preset tags

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

[krita] [Bug 425845] Duplication of default tags

[brendan]

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

brendan  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

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

[krita] [Bug 425845] New: Duplication of default tags

[brendan]

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

Bug ID: 425845
   Summary: Duplication of default tags
   Product: krita
   Version: 4.3.0
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: Dockers
  Assignee: krita-bugs-n...@kde.org
  Reporter: waferl...@gmail.com
  Target Milestone: ---

Created attachment 131207
  --> https://bugs.kde.org/attachment.cgi?id=131207=edit
Usage log of this session

SUMMARY
When adding brushes to a custom tag group in the brush presets docker, the
default tags are duplicated: https://i.imgur.com/xvcj1q7.png
Restarting the program fixes the problem, until one decides to add to custom
tag groups again, in the brush presets docker.

STEPS TO REPRODUCE
1. Create a custom tag group in brush presets
2. Start adding brushes to that custom tag group
3. Default tags that are below the custom tag are duplicated, "My Favorites" is
duplicated the most.

OBSERVED RESULT
Adding brushes to a custom tag causes duplication of default tags.

EXPECTED RESULT
Default tags are not duplicated.

SOFTWARE/OS VERSIONS
Windows: 10 Home, Version 2004, Build 19041.450
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 5.12.8

ADDITIONAL INFORMATION
In-depth system information: https://pastebin.com/raw/A4UCrFzs

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

[krunner] [Bug 423566] Backspace can displace input text above the text box in some situations

[Brendan Early]

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

--- Comment #4 from Brendan Early  ---
Thanks, turns out I just already had krunner open. That patch works perfectly.

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

[krunner] [Bug 423566] Backspace can displace input text above the text box in some situations

[Brendan Early]

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

--- Comment #2 from Brendan Early  ---
I built and ran a version with the patch using kdesrc-build & kdesrc-run and
I'm still seeing this bug. That patch looks like it should work, is there
anything special I need to do to run the build?

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

[krunner] [Bug 423566] New: Backspace can displace input text above the text box in some situations

[Brendan Early]

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

Bug ID: 423566
   Summary: Backspace can displace input text above the text box
in some situations
   Product: krunner
   Version: 5.18.5
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@privat.broulik.de
  Reporter: m-...@evermiss.net
CC: plasma-b...@kde.org
  Target Milestone: ---

Created attachment 129712
  --> https://bugs.kde.org/attachment.cgi?id=129712=edit
Video of issue

SUMMARY

When using Backspace or Ctrl + Backspace, sometimes text will appear above the
input text box.

STEPS TO REPRODUCE
1. Open krunner
2. Type until autocomplete suggestions show
3. Press the down arrow on keyboard
4. Press backspace

OBSERVED RESULT

See attached video

EXPECTED RESULT

Word or character is deleted without text displacement.

SOFTWARE/OS VERSIONS
Operating System: Fedora 32
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.70.0
Qt Version: 5.14.2
Kernel Version: 5.6.19-300.fc32.x86_64
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-6700 CPU @ 3.40GHz
Memory: 15.6 GiB of RAM

ADDITIONAL INFORMATION
Resolution: 3840x2160
Scale: 150%

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

[okular] [Bug 423517] Text in enabled form fields becomes smaller when the window is made wider, and eventually disappears; but only with certain widget styles.

[Brendan Early]

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

--- Comment #10 from Brendan Early  ---
I'm just realizing that this is due to the zoom level changing when the window
is made wider.

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

[okular] [Bug 423517] Text in enabled form fields becomes smaller when the window is made wider, and eventually disappears; but only with certain widget styles.

[Brendan Early]

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

--- Comment #9 from Brendan Early  ---
(In reply to David Hurka from comment #8)
> I think what you write makes sense.

It makes sense that the text size should change along with the rest of the
document. I do not think it makes sense that the form text size becomes smaller
when the rest of the document becomes bigger.

> But I still believe this is an issue with the widget style you are using. Is
> “Arc” the widget style?

My widget style is Breeze, Arc is only set for window decorations. I still see
this with a version I built using kdesrc-build & kdesrc-run.

> Another interpretation is that Okular shoudn’t rely on the system widget
> style to render form fields. For the same reason as why I think text
> highlight background shouldn’t follow the system color scheme: Form fields
> are inside a WYSIWYG graphics area, which shouldn’t and mostly doesn’t
> follow system stuff, but should do what the document says.

+1

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

[okular] [Bug 423517] Unable to see text typed when filling forms

[Brendan Early]

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

--- Comment #7 from Brendan Early  ---
> I've never seen an application change text size depending on window width.

I feel a bit silly for writing this. I think the intended behaviour here should
be that the text size should be the same as the rendered form text.

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

[okular] [Bug 423517] Unable to see text typed when filling forms

[Brendan Early]

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

--- Comment #6 from Brendan Early  ---
Pretty much, though it doesn't disappear when using Breeze. I'm pretty sure
I've never seen an application change text size depending on window width.

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

[okular] [Bug 423517] Unable to see text typed when filling forms

[Brendan Early]

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

Brendan Early  changed:

   What|Removed |Added

 Attachment #129683|0   |1
is obsolete||

--- Comment #4 from Brendan Early  ---
Created attachment 129700
  --> https://bugs.kde.org/attachment.cgi?id=129700=edit
Form issue 2

It was under application style, I was using Arc via Kvantum. I am still seeing
differences when the window gets wider. I can see the text just fine, but when
I expand the window the text gets smaller.

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

[okular] [Bug 423517] Unable to see text typed when filling forms

[Brendan Early]

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

--- Comment #2 from Brendan Early  ---
(In reply to Albert Astals Cid from comment #1)
> Interesting, can't reproduce it.
> 
> Do you know which Qt style are you using?

No, where can I find that? I think I'm just using breeze.

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

[okular] [Bug 423517] Unable to see text typed when filling forms

[Brendan Early]

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

Brendan Early  changed:

   What|Removed |Added

 CC||m-...@evermiss.net

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

[okular] [Bug 423517] New: Unable to see text typed when filling forms

[Brendan Early]

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

Bug ID: 423517
   Summary: Unable to see text typed when filling forms
   Product: okular
   Version: 1.9.3
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: PDF backend
  Assignee: okular-de...@kde.org
  Reporter: m-...@evermiss.net
  Target Milestone: ---

Created attachment 129683
  --> https://bugs.kde.org/attachment.cgi?id=129683=edit
Form issue

SUMMARY

If the window is too wide when filling a PDF text form Okular will not display
typed text. When hiding form fields typed text is visible.

STEPS TO REPRODUCE
1. Open
https://wcjc.edu/Admissions/admissions-and-registration/AddressChangeADAv1.pdf
2. Maximize window
3. Attempt to fill form

OBSERVED RESULT

See attached video

EXPECTED RESULT

I should be able to see filled form text at all window sizes.

SOFTWARE/OS VERSIONS
Operating System: Fedora 32
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.70.0
Qt Version: 5.14.2
Kernel Version: 5.6.19-300.fc32.x86_64
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-6700 CPU @ 3.40GHz
Memory: 15.6 GiB of RAM


ADDITIONAL INFORMATION
Resolution: 3840x2160
Scale: 150%

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

[krita] [Bug 414638] New: transform tool near instantly crashes krita

[Brendan]

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

Bug ID: 414638
   Summary: transform tool near instantly crashes krita
   Product: krita
   Version: 4.2.8
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: Tools/Transform
  Assignee: krita-bugs-n...@kde.org
  Reporter: pineapplewitn...@gmail.com
  Target Milestone: ---

SUMMARY
when i press on the transorm tool or use ctrl+t, krita crashes. sometimes it
works fine for a minute or two before crashing, in one case crashing because i
switched from it to the brush tool.

STEPS TO REPRODUCE
1. open krita
2. open or create a canvas
3. use the transform tool

SOFTWARE/OS VERSIONS
Linux (x86_64) release 5.3.13-arch1-1

KRITA DID NOT CLOSE CORRECTLY

SESSION: 28 Nov 2019 13:49:07 -0600. Executing krita

WARNING: This file contains information about your system and the
images you have been working with.

If you have problems with Krita, the Krita developers might ask
you to share this file with them. The information in this file is
not shared automatically with the Krita developers in any way. You
can disable logging to this file in Krita's Configure Krita Dialog.

Please review the contents of this file before sharing this file with
anyone.

Krita

 Version: 4.2.8
 Languages: C
 Hidpi: true

Qt

  Version (compiled): 5.13.2
  Version (loaded): 5.13.2

OS Information

  Build ABI: x86_64-little_endian-lp64
  Build CPU: x86_64
  CPU: x86_64
  Kernel Type: linux
  Kernel Version: 5.3.13-arch1-1
  Pretty Productname: Arch Linux
  Product Type: arch
  Product Version: unknown

OpenGL Info

  Vendor:  "X.Org" 
  Renderer:  "Radeon RX 560 Series (POLARIS11, DRM 3.33.0, 5.3.13-arch1-1, LLVM
9.0.0)" 
  Version:  "4.5 (Compatibility Profile) Mesa 19.2.6" 
  Shading language:  "4.50" 
  Requested format:  QSurfaceFormat(version 3.0, options
QFlags(DeprecatedFunctions), depthBufferSize 24,
redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8,
stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer,
swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile 
QSurfaceFormat::CompatibilityProfile) 
  Current format:QSurfaceFormat(version 4.5, options
QFlags(DeprecatedFunctions), depthBufferSize 24,
redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8,
stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer,
swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile 
QSurfaceFormat::CompatibilityProfile) 
 Version: 4.5
 Supports deprecated functions true 
 is OpenGL ES: false 

QPA OpenGL Detection Info 
  supportsDesktopGL: true 
  supportsOpenGLES: true 
  isQtPreferOpenGLES: false 

Hardware Information

  GPU Acceleration: auto
  Memory: 7892 Mb
  Number of Cores: 4
  Swap Location: /tmp

Current Settings

Current Swap Location: /tmp
Undo Enabled: 1
Undo Stack Limit: 30
Use OpenGL: 1
Use OpenGL Texture Buffer: 1
Use AMD Vectorization Workaround: 0
Canvas State: OPENGL_SUCCESS
Autosave Interval: 900
Use Backup Files: 1
Number of Backups Kept: 1
Backup File Suffix: ~
Backup Location: Same Folder as the File
Use Win8 Pointer Input: 0
Use RightMiddleTabletButton Workaround: 0
Levels of Detail Enabled: 0
Use Zip64: 0


28 Nov 2019 13:49:24 -0600: CLOSING SESSION

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

[krita] [Bug 407380] Softness sensor does nothing when using a predefined brush tip

[Brendan]

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

Brendan  changed:

   What|Removed |Added

Summary|Softness sensor does|Softness sensor does
   |nothing |nothing when using a
   ||predefined brush tip

--- Comment #5 from Brendan  ---
Well I'll be damned, I'm not sure how I missed that.

Updating the bug report now.

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

[krita] [Bug 407380] Softness sensor does nothing

[Brendan]

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

--- Comment #2 from Brendan  ---
Nope.  Enabling pen settings then forcing the curve to 0% on both sides still
doesn't affect the pen softness.

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

[krita] [Bug 407380] New: Softness sensor does nothing

[Brendan]

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

Bug ID: 407380
   Summary: Softness sensor does nothing
   Product: krita
   Version: 4.1.5
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Brush engines
  Assignee: krita-bugs-n...@kde.org
  Reporter: abc...@yahoo.com
  Target Milestone: ---

STEPS TO REPRODUCE
1. Go to brush settings editor
2. Select any brush tip that has a hard edge
3. Enable Softness sensor
4. Deselect "enable pen settings" checkbox
5. Set softness to 100% if it isn't already

OBSERVED RESULT
Pen retains its hard edge regardless of what settings are selected with the
Softness sensor


EXPECTED RESULT
The pen tip should be at least a little bit blurred.

SOFTWARE/OS VERSIONS
Linux Appimage, 4.1.5 release.
Also tested in 4.2.0 nightly build 474, git hash c000999.  Bug exists there as
well.

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

[krita] [Bug 407380] Softness sensor does nothing

[Brendan]

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

Brendan  changed:

   What|Removed |Added

   Platform|Other   |Appimage

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

[krita] [Bug 407378] New: Krita segfaults when "Select Opaque" is used.

[Brendan]

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

Bug ID: 407378
   Summary: Krita segfaults when "Select Opaque" is used.
   Product: krita
   Version: nightly build (please specify the git hash!)
  Platform: Appimage
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Tools/Selection
  Assignee: krita-bugs-n...@kde.org
  Reporter: abc...@yahoo.com
  Target Milestone: ---

Linux Appimage nightly build #474, git hash c000999

STEPS TO REPRODUCE
1. Open a new file
2. Paint something on the top layer
3. Select -> Select Opaque -> any of the Select Opaque options (Replace),
(Add), (Subtract) or (Intersect).

OBSERVED RESULT
Krita crashes, closing itself completely.

ADDITIONAL INFORMATION

When opened from the console, the following text displays right before the
crash: 

SAFE ASSERT (krita): "allowAsChild(newNode)" in file
/home/appimage/workspace/Krita_Nightly_Appimage_Build/krita/libs/image/kis_node.cpp,
line 499
SAFE ASSERT (krita): "m_d->rootLayer->selectionMask()" in file
/home/appimage/workspace/Krita_Nightly_Appimage_Build/krita/libs/image/kis_image.cc,
line 487
Segmentation fault (core dumped)

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

[krita] [Bug 403576] Cannot edit transparency masks as greyscale images when using pixel brush with wash mode.

[Brendan]

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

--- Comment #9 from Brendan  ---
According to the guy in this video: 
https://www.youtube.com/watch?v=hLW6ulXZ9GM
in Krita 3.0.1 you could access the mask by holding "alt" and clicking on the
thumbnail.

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

[krita] [Bug 403576] Cannot edit transparency masks as greyscale images when using pixel brush with wash mode.

[Brendan]

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

--- Comment #8 from Brendan  ---
I'm pretty sure Wolthera is describing a different, albeit probably related
bug.  

My problem is that I cannot view any transparency mask without isolating the
layer first.  There is nowhere on the node that I can click to bring up the
greyscale image that represents the mask, and I'm pretty sure there should be.

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

[krita] [Bug 403576] Cannot edit transparency masks as greyscale images

[Brendan]

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

Brendan  changed:

   What|Removed |Added

 Resolution|NOT A BUG   |---
 Ever confirmed|0   |1
 Status|RESOLVED|REOPENED

--- Comment #2 from Brendan  ---
I can't do that either. When I click on the preview for the global selection
mask, the exact same problem occurs; I can paint to the mask but not see it in
greyscale. I thought they were similar enough to fall under the same bug, but I
can setup a separate bug if you think it won't just get closed as duplicate.

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

[krita] [Bug 403576] New: Cannot edit transparency masks as greyscale images

[Brendan]

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

Bug ID: 403576
   Summary: Cannot edit transparency masks as greyscale images
   Product: krita
   Version: 4.1.5
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: krita-bugs-n...@kde.org
  Reporter: abc...@yahoo.com
  Target Milestone: ---

SUMMARY

Cannot click the greyscale preview of a mask, just to the left of the mask
layer in the Layers docker, to bring up the mask as a greyscale image on the
main canvas.

STEPS TO REPRODUCE
1. Create a new file.
2. Create a new transparency mask.
3. Click on the BW preview box to the left of the transparency mask in the
layers docker.
4. Draw onto the canvas.

OBSERVED RESULT
The image remains blank.  When you mouseover the image preview of the
transparency mask, a preview of the scribble shows up.  So the mask is taking
the drawing, it's just not showing it on the canvas in any capacity.

EXPECTED RESULT
The transparency mask should show up as a greyscale image in the main canvas
window.

SOFTWARE/OS VERSIONS
Lubuntu 16.04.3 LTS
Krita Appimage 4.1.5

ADDITIONAL INFORMATION

https://www.youtube.com/watch?v=itW9wfPMyWc

In this video from about 3 years ago at around 0:30, the author (apparently)
just clicked on the small B preview box for a selection mask and it popped up
on screen. I'm using the Krita 4.1.5 appimage for Linux and I can't do that.
The closest I can get is isolating the layer and painting on it that way, but
that's very laggy for me (a known bug that was apparently fixed in 4.2) and
rather inconvenient if I want to rapidly switch between the mask and the
underlying image.

Isolating the layer works as a work-around, but doing so isn't very practical,
since sometimes I want to quickly switch between the greyscale mask and the
underlying image.  (Also, isolating a transparency mask has a really bad lag
bug, but that's already been reported and is apparently fixed in 4.2.)

Note that a Windows user independently confirmed the same bug with a windows
build of 4.1.5 at this url: 

https://www.reddit.com/r/krita/comments/ajafs2/question_is_it_possible_to_pull_up_a_mask_as_a/?st=jrbasnpb=bfc3ac91

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

[rust-qt-binding-generator] [Bug 403017] New: Qt-binding-generator "No such file or directory (os error 2)" on run

[Brendan Hansknecht]

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

Bug ID: 403017
   Summary: Qt-binding-generator "No such file or directory (os
error 2)" on run
   Product: rust-qt-binding-generator
   Version: unspecified
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: j...@vandenoever.info
  Reporter: brendan.hanskne...@gmail.com
  Target Milestone: ---

SUMMARY
I am not sure what is happening, but I seem unable to get
rust_qt_binding_generator to work. After I install it with cargo, I run it and
get "No such file or directory (os error 2)". I have tried it on the
binding.json in the readme and the one for the example and demo projects. All
of them give the same error for me.

STEPS TO REPRODUCE
1. cargo install rust_qt_binding_generator
2. create binding.json in README
3. rust_qt_binding_generator binding.json

OBSERVED RESULT
No such file or directory (os error 2)

EXPECTED RESULT
The binding files should get generated

SOFTWARE/OS VERSIONS
Linux: Manjaro 18
Qt Version: 5.12

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

[kdf] [Bug 81227] Wrong amount of free space reported for FAT32 partitions

[Brendan]

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

Brendan  changed:

   What|Removed |Added

 CC||bunf2014@apps.opensourcelaw
   ||.biz

--- Comment #5 from Brendan  ---
I do not have an environment that would allow me to test this any more. 
Sorry

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

[k3b] [Bug 399342] Target directory is always reset when ripping audio CDs.

[Brendan Howell]

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

Brendan Howell  changed:

   What|Removed |Added

Version|unspecified |18.08.1

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

[k3b] [Bug 399342] New: Target directory is always reset when ripping audio CDs.

[Brendan Howell]

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

Bug ID: 399342
   Summary: Target directory is always reset when ripping audio
CDs.
   Product: k3b
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Audio Project
  Assignee: k...@kde.org
  Reporter: brendan-...@howell-ersatz.com
CC: mich...@jabster.pl, tr...@kde.org
  Target Milestone: ---

SUMMARY
When ripping audio, the preferences for Codec, rate, etc. are all saved and
restored properly, but the target directory is always reset. I have to manually
type it in again for each CD I rip.

STEPS TO REPRODUCE
1. Insert an audio CD and click on "start ripping"
2. Change the target directory to "/home/foo/other_dir" and rip the CD
3. Upon completion, close the ripping window and start again with a new audio
CD.

OBSERVED RESULT
The target directory is reset to "/home/foo/Music"

EXPECTED RESULT
The target directory should be "/home/foo/other_dir"

SOFTWARE VERSIONS
(available in About System)
K3b Version: 18.08.1
KDE Plasma Version: ?
KDE Frameworks Version: 5.50.0
Qt Version: 5.11.1

ADDITIONAL INFORMATION
Thanks for your hard work!

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

[krita] [Bug 395194] New: undocked Dockers lost on orientation change (Wacom mobilestudio)

[Brendan]

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

Bug ID: 395194
   Summary: undocked Dockers lost on orientation change (Wacom
mobilestudio)
   Product: krita
   Version: git master
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Dockers
  Assignee: krita-bugs-n...@kde.org
  Reporter: bunf2...@apps.opensourcelaw.biz
  Target Milestone: ---

using git version 5345be7

I can't diagnose exactly what is happening, but undocked dockers disappear on
orientation change. 
Eg:
using a tablet 
start in landscape
open touch docker
make it undocked
change orientation (landscape-> portrait or vice versa)
docker disappears
change orientation again
docker reappears

The touch docker will disappear. 
Observations:
* when it disappears it can't be re-enabled through settings->dockers 
* can only be recovered by changing orientation back, docking it, then changing
orientation again

If there are multiple undocked dockers some, but not all, of them can survive
the orientation change.

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

[krita] [Bug 390184] Don't force Scripter window to stay on top

[Brendan]

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

--- Comment #5 from Brendan <bunf2...@apps.opensourcelaw.biz> ---
"Maybe we should make this an option though. "

Wouldn't hurt. Stay on top could just be stored like the geometry. Ie: if stay
on top set at close, then set self.setWindowFlags(QtCore.Qt.Tool |
QtCore.Qt.WindowStaysOnTopHint) otherwise don't.

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

[krita] [Bug 390184] Don't force Scripter window to stay on top

[Brendan]

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

--- Comment #2 from Brendan <bunf2...@apps.opensourcelaw.biz> ---
I am on a laptop. My scripter window is wide enough that it obscures the rest
of the krita window. It also means that if I switch applications - eg bash
shell - the scripter window and its output disappears. So to get it back I
first need to click the krita window, then click the scripter window to give it
focus.

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

[krita] [Bug 390184] New: Don't force Scripter window to stay on top

[Brendan]

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

Bug ID: 390184
   Summary: Don't force Scripter window to stay on top
   Product: krita
   Version: git master
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: Scripting
  Assignee: krita-bugs-n...@kde.org
  Reporter: bunf2...@apps.opensourcelaw.biz
  Target Milestone: ---

I am finding the auto-on-top of the scripter window a bit annoying. Could it
not be set, or could it be a setting? I would prefer the scripter window to
show up in the taskbar so I can switch to it that way or alt-tab to it.

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

[www.kde.org] [Bug 388846] Your download mirrors are bad for AU

[Brendan]

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

--- Comment #1 from Brendan <bunf2...@apps.opensourcelaw.biz> ---
So, that download failed with 2.7M received. 
For comparison I got the full ftp address from firefox then used it to navigate
the UK Mirror service and download from there. 
I am getting 110-190 kb/s now. My download time has gone from 6 hours to 6
minutes.

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

[www.kde.org] [Bug 388846] New: Your download mirrors are bad for AU

[Brendan]

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

Bug ID: 388846
   Summary: Your download mirrors are bad for AU
   Product: www.kde.org
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: kde-...@kde.org
  Reporter: bunf2...@apps.opensourcelaw.biz
  Target Milestone: ---

Your download mirrors for Australia seem to come from Japan which, while
geographically sort-of close-ish, has, frankly, terrible connectivity to
Australia. For example, I typically get from 1 to 4 kb/s. Atm I am downloading
Krita-4.0.0beta1. I get 1.3 kilobytes per second.  This is not the first time
this has happened. 

Could you at the very least provide a way to manually select a mirror to use.

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

[krita] [Bug 387701] Scripter cannot load files under Python 3.4

[Brendan]

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

--- Comment #2 from Brendan <bunf2...@apps.opensourcelaw.biz> ---
This has been implemented in the following code review request:
https://phabricator.kde.org/D9529

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

[krita] [Bug 387884] Scripter does not run edits unless saved

[Brendan]

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

--- Comment #3 from Brendan <bunf2...@apps.opensourcelaw.biz> ---
also in 9dd5c1a

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

[krita] [Bug 387884] Scripter does not run edits unless saved

[Brendan]

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

--- Comment #2 from Brendan <bunf2...@apps.opensourcelaw.biz> ---
This bug is present in commit 61a84e2 (15 Dec)
When you save a script it seems to uncouple the connection to
setDocumentModified - undo is available (press ctrl-Z!) but the signal is not
setting off setDocumentModified.

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

[krita] [Bug 387702] Permit Scripter to load scripts which don't have a main()

[Brendan]

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

Brendan <bunf2...@apps.opensourcelaw.biz> changed:

   What|Removed |Added

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

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

[krita] [Bug 387884] New: Scripter does not run edits unless saved

[Brendan]

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

Bug ID: 387884
   Summary: Scripter does not run edits unless saved
   Product: krita
   Version: 4.0 pre-alpha
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Scripting
  Assignee: krita-bugs-n...@kde.org
  Reporter: bunf2...@apps.opensourcelaw.biz
  Target Milestone: ---

If a scripter script has been saved, using the Run action causes scripter to
load and run the script from its associated file - even if there are unsaved
changes in the script window. 

To reproduce:
start scripter
file->new script 
print("hello")
file-> save (choose filename and save)
press Run/Ctrl-R:

==
hello

add to edit window:
print("world")
press Run/Ctrl-R:

==
hello


That is, "world" is not printed, despite being in the edit window. This is
because saving the document sets _activeDocument flag and that causes the
script to load directly from the file. 

There are different approaches to solving this
* add a dirty flag to the edit box and check that, put a dialog up to query
saving before running - or visual indicator that script has been changed or 
toolbar warning that running script from file
* automatically save edit window before running (or have this as an option in
settings)
* have separate actions save+run (... from the file) and run (...from the
editor window)
* have separate actions run from file, run from editor (manual saving)
* have a "run-from-file" mode which doesn't display the edit window - or makes
it read only?
* run only script in window
* some combination

I personally would like to be able to run scripts directly from the file - so
that I can use a different editor.

Wanted feedback on UI before diving into patching.

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

[krita] [Bug 387702] Permit Scripter to load scripts which don't have a main()

[Brendan]

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

--- Comment #6 from Brendan <bunf2...@apps.opensourcelaw.biz> ---
Have tried to create a diff:
https://phabricator.kde.org/D9317

Do I need to also git fork and commit? If I make further changes to the
runaction file how do I make sure the diffs are properly synced?

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

[krita] [Bug 387702] Permit Scripter to load scripts which don't have a main()

[Brendan]

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

--- Comment #4 from Brendan <bunf2...@apps.opensourcelaw.biz> ---
Turns out I already have an identity. Now I have a phabricator account.
So, next question - what's the process? I'm not a heavy git user.

I git clone the phabricator then make and commit changes then make pull
requests?

I plan on working on the scripts in my install directory then copying them to
the relevant git directory then git diffing them. Is that a problem?

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

[krita] [Bug 387702] Permit Scripter to load scripts which don't have a main()

[Brendan]

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

--- Comment #2 from Brendan <bunf2...@apps.opensourcelaw.biz> ---
Ok, thanks.
Not sure how I do that. 
So I set up an identity at kde, install arc, and then log in to phabricator?

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

[krita] [Bug 387701] Scripter cannot load files under Python 3.4

[Brendan]

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

--- Comment #1 from Brendan <bunf2...@apps.opensourcelaw.biz> ---
ps: git diffed patch!

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

[krita] [Bug 387702] New: Permit Scripter to load scripts which don't have a main()

[Brendan]

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

Bug ID: 387702
   Summary: Permit Scripter to load scripts which don't have a
main()
   Product: krita
   Version: 4.0 pre-alpha
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: Scripting
  Assignee: krita-bugs-n...@kde.org
  Reporter: bunf2...@apps.opensourcelaw.biz
  Target Milestone: ---

Created attachment 109254
  --> https://bugs.kde.org/attachment.cgi?id=109254=edit
Allow scripter to play main()-less scripts without complaining

If a script is typed into the scripter window interactively and saved, scripter
keeps a record of the file and automatically loads the script on the next run.
When you press play on this auto-loaded script the runner module tries to load
the module, then run it's main() method. However, an interactive script may not
have a main method.  Scripter should run main() if it's present, but fail
silently if it is not present. 

Patch attached.

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

[krita] [Bug 387701] New: Scripter cannot load files under Python 3.4

[Brendan]

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

Bug ID: 387701
   Summary: Scripter cannot load files under Python 3.4
   Product: krita
   Version: 4.0 pre-alpha
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Scripting
  Assignee: krita-bugs-n...@kde.org
  Reporter: bunf2...@apps.opensourcelaw.biz
  Target Milestone: ---

Created attachment 109253
  --> https://bugs.kde.org/attachment.cgi?id=109253=edit
Allow scripter to load files under Python 3.4

If you try to run a file from scripter it fails to load the file as a module
because it uses the new-in-3.5 method importlib.util.module_from_spec. 

I attach a patch to get this load working in Python 3.4.

This patch:
* adds a new file loader34.py, based on the equivalent bootstrap file from
Python 3.5; and
* some code to check for Python 3.4 and use the loader from loader34 to load
the module

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

[krita] [Bug 387611] New: Multitouch rotate, zoom-less pan

[Brendan]

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

Bug ID: 387611
   Summary: Multitouch rotate, zoom-less pan
   Product: krita
   Version: 3.3.2
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: Usability
  Assignee: krita-bugs-n...@kde.org
  Reporter: bunf2...@apps.opensourcelaw.biz
  Target Milestone: ---

Please add rotation to multitouch support.
Please support zoomless pan - to pan with multitouch requires two fingers. To
pan without zooming requires those fingers to maintain a constant distance.

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

[krita] [Bug 387433] Scripter plugin requires Python 3.5

[Brendan]

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

--- Comment #12 from Brendan <bunf2...@apps.opensourcelaw.biz> ---
(In reply to wolthera from comment #11)
> Hey Brendan, I managed to apply your patch. :)


Woohoo! The most recent one, with yield from I hope.

> One thing though: next time don't rename files, the rename had gotten into
> the patch. :(

Sorry. I was working from a tarball bc I wasn't sure how phabricator
worked/what fork had the most recent versions in it. 

There is another python 3.4 incompatibility in the way that scripter loads the
scripts (using module_from_spec) bug report to be filed soon. I'm proposing to
add a new file to deal with that rather than include compatibility code in
runner.py 

> How would you like to be known in the commit message?

(In reply to wolthera from comment #11)
> Hey Brendan, I managed to apply your patch. :)
> 
> One thing though: next time don't rename files, the rename had gotten into
> the patch. :(
> 
> How would you like to be known in the commit message?

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

[krita] [Bug 387566] New: Python scripting UI - submenus

[Brendan]

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

Bug ID: 387566
   Summary: Python scripting UI - submenus
   Product: krita
   Version: 4.0 pre-alpha
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: Scripting
  Assignee: krita-bugs-n...@kde.org
  Reporter: bunf2...@apps.opensourcelaw.biz
  Target Milestone: ---

Please provide a means to implement submenu items in the Python scripting menu.
At the moment it is already looking crowded.  See, eg, GIMP scripting, where
scripts use metadata to specify the menu/submenu structure that they will be
listed under. 

It may even make sense to permit Python scripts to appear under different menus
(eg File, Edit etc)

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

[krita] [Bug 387433] Scripter plugin requires Python 3.5

[Brendan]

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

Brendan <bunf2...@apps.opensourcelaw.biz> changed:

   What|Removed |Added

 Attachment #109129|0   |1
is obsolete||

--- Comment #9 from Brendan <bunf2...@apps.opensourcelaw.biz> ---
Created attachment 109137
  --> https://bugs.kde.org/attachment.cgi?id=109137=edit
Update to debugger.py in python scripter plugin to allow use under Python
versions prior to 3.5

yield causes errors, updated to use yield from

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

[krita] [Bug 387471] New: Scripter script fails if it cannot find previous file

[Brendan]

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

Bug ID: 387471
   Summary: Scripter script fails if it cannot find previous file
   Product: krita
   Version: 4.0 pre-alpha
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Scripting
  Assignee: krita-bugs-n...@kde.org
  Reporter: bunf2...@apps.opensourcelaw.biz
  Target Milestone: ---

If you save your script from the scripter text edit window it will keep a note
of the location and attempt to load it on next startup. If the file is moved or
deleted in the interim, file loading will fail and scripter will not
initialise.

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

[krita] [Bug 387470] New: Comments unreadable in scripter under default theme

[Brendan]

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

Bug ID: 387470
   Summary: Comments unreadable in scripter under default theme
   Product: krita
   Version: 4.0 pre-alpha
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: Scripting
  Assignee: krita-bugs-n...@kde.org
  Reporter: bunf2...@apps.opensourcelaw.biz
  Target Milestone: ---

Python hash comments:
# a comment
are rendered in a dark green against a dark grey in the default krita colour
scheme. The colours make the comments very difficult to read. 

Triple quote comments:
""" a comment"""
are only slightly better, being dark pink

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

[krita] [Bug 387433] Scripter plugin requires Python 3.5

[Brendan]

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

Brendan <bunf2...@apps.opensourcelaw.biz> changed:

   What|Removed |Added

 Attachment #109115|0   |1
is obsolete||

--- Comment #8 from Brendan <bunf2...@apps.opensourcelaw.biz> ---
Created attachment 109129
  --> https://bugs.kde.org/attachment.cgi?id=109129=edit
Update to debugger.py in python scripter plugin to allow use under Python
versions prior to 3.5

I have downloaded krita 4.0.0 alpha 2 tarball and worked from it. There is an
additional carriage return which has probably thrown off earlier patches.

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

[krita] [Bug 387468] New: Python cannot wrap Extension* objects

[Brendan]

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

Bug ID: 387468
   Summary: Python cannot wrap Extension* objects
   Product: krita
   Version: 4.0 pre-alpha
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Scripting
  Assignee: krita-bugs-n...@kde.org
  Reporter: bunf2...@apps.opensourcelaw.biz
  Target Milestone: ---

Open scripter
Type:
a = Application.extensions()

Press play.

Receive the error message:

unable to convert return value of Krita.extensions from 'QList' to
a Python object

Krita 4.0.0 alpha 2

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

[krita] [Bug 387433] Scripter plugin requires Python 3.5

[Brendan]

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

--- Comment #7 from Brendan <bunf2...@apps.opensourcelaw.biz> ---
(In reply to Boudewijn Rempt from comment #6)
> Tt would be easier to just change the original file and provide
> the output of "git diff"

Can you give me the link to the right git repository? I can never find the 4.0
version.

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

[krita] [Bug 387433] Scripter plugin requires Python 3.5

[Brendan]

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

Brendan <bunf2...@apps.opensourcelaw.biz> changed:

   What|Removed |Added

 Attachment #109114|0   |1
is obsolete||

--- Comment #5 from Brendan <bunf2...@apps.opensourcelaw.biz> ---
Created attachment 109115
  --> https://bugs.kde.org/attachment.cgi?id=109115=edit
Update to debugger.py in python scripter plugin to allow use under Python
versions prior to 3.5

Don't know what the story is with the earlier patch - stray carriage return
somewhere affecting the numbering?

~/krita/inst/share/krita/pykrita/scripter/debugger_scripter> diff -u
debugger.py debugger_new.py > debugger_python3.4b.patch
~/krita/inst/share/krita/pykrita/scripter/debugger_scripter> cp debugger.py
debugger_bak.py
~/krita/inst/share/krita/pykrita/scripter/debugger_scripter> patch <
debugger_python3.4b.patch 
patching file debugger.py
~/krita/inst/share/krita/pykrita/scripter/debugger_scripter> diff debugger.py
debugger_new.py 
~/krita/inst/share/krita/pykrita/scripter/debugger_scripter>

If this doesn't work, please point me to the phabricator (I can't find my way
around it) for debugger.py and I'll diff against that.

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

[krita] [Bug 387433] Scripter plugin requires Python 3.5

[Brendan]

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

--- Comment #4 from Brendan <bunf2...@apps.opensourcelaw.biz> ---
(In reply to Boudewijn Rempt from comment #3)
> Comment on attachment 109114 [details]
> Update to python scripter plugin to allow it to run under python 3.4
> 
> Um... It doesn't apply?

My patchy grasp of patching?
My version is 4.0.0-pre-alpha (git dd1c4cb)
I have also run diff in a separate directory, do I need to run it from the inst
directory and include the directory structure?

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

[krita] [Bug 387433] Scripter plugin requires Python 3.5

[Brendan]

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

--- Comment #2 from Brendan <bunf2...@apps.opensourcelaw.biz> ---
Created attachment 109114
  --> https://bugs.kde.org/attachment.cgi?id=109114=edit
Update to python scripter plugin to allow it to run under python 3.4

Patch attached.

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

[krita] [Bug 387433] New: Scripter plugin requires Python 3.5

[Brendan]

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

Bug ID: 387433
   Summary: Scripter plugin requires Python 3.5
   Product: krita
   Version: 4.0 pre-alpha
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Scripting
  Assignee: krita-bugs-n...@kde.org
  Reporter: bunf2...@apps.opensourcelaw.biz
  Target Milestone: ---

The scripter plugin requires Python 3.5 (uses async def/await). Python 3.5 is
not backwards compatible with Python 3.4 and aborts the scipter plugin during
krita startup on systems with earlier versions of Python 3. 

Python 3.5 is not available* for install on my distro (OpenSuSE Leap 42.3).
This plugin can be modified to run on earlier versions of Python 3 by using
@asyncio.coroutine/yield.  

File to change: 
inst/share/krita/pykrita/scripter/debugger_scripter/debugger.py
Diff:
>diff debugger.py debugger_new.py 
77c77,79
< async def display(self):
---
> 
> @asyncio.coroutine
> def display(self):
82c84
< await asyncio.sleep(0.3)
---
> yield asyncio.sleep(0.3)
89,90c91,93
< async def start(self):
< await self.display()
---
> @asyncio.coroutine
> def start(self):
> yield self.display()
92c95,96
< async def step(self):
---
> @asyncio.coroutine
> def step(self):
94c98
< await self.display()
---
> yield self.display()
96c100,101
< async def stop(self):
---
> @asyncio.coroutine
> def stop(self):
99c104
< await self.display()
---
> yield self.display()




* it can be installed, but it breaks a lot of other installed packages.

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

[krita] [Bug 386412] menu items not showing

[Brendan]

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

--- Comment #4 from Brendan <bunf2...@apps.opensourcelaw.biz> ---
>cd .local/share/krita/
hostname:~/.local/share/krita 
>find . | grep xmlgui
hostname:~/.local/share/krita 
>


Nope. Anywhere else?

Also, on my laptop, running OpenSuSE 42.2 the scripting submenu is not present
- there are no gaps in the menu entries, but there is no submenu listing
scripts.

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

[krita] [Bug 386412] menu items not showing

[Brendan]

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

--- Comment #2 from Brendan <bunf2...@apps.opensourcelaw.biz> ---
So where would it be?

>cd ~
hostname:~ 
>find . -iname "krita.xmlgui"
hostname:~
>find . -iname "*xmlgui"
hostname:~ 
>cd .local/
hostname:~/.local 
>find . -iname "krita.xmlgui"

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

[krita] [Bug 386412] New: menu items not showing

[Brendan]

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

Bug ID: 386412
   Summary: menu items not showing
   Product: krita
   Version: 4.0 pre-alpha
  Platform: Appimage
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: bunf2...@apps.opensourcelaw.biz
  Target Milestone: ---

Created attachment 108660
  --> https://bugs.kde.org/attachment.cgi?id=108660=edit
Some menus from Krita showing blank entries.

When I run ./krita-4.0.0-pre-alpha-x86_64.appimage on my system (OpenSuSE leap
42.3), many menu items are blank. The whole of the scripting submenu does not
show at all. 

Blank menu items seem to be connected to their associated code when clicked. 

Sample screenshot attached.

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

[krita] [Bug 381358] New: action.setToolTip doesn't seem to set any tooltip

[Brendan]

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

Bug ID: 381358
   Summary: action.setToolTip doesn't seem to set any tooltip
   Product: krita
   Version: 4.0 pre-alpha
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: Scipting
  Assignee: krita-bugs-n...@kde.org
  Reporter: bunf2...@apps.opensourcelaw.biz
  Target Milestone: ---

action.setToolTip doesn't seem to have any effect. 

Reproduce:
1. observe use of setToolTip in prepackaged tenbrushes script:
action.setToolTip("Assign ten brush presets to ten shortcuts.")

2. run krita

3. No tooltip pop up for action (ie menu item).

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

[krita] [Bug 381342] Please add a scripting component to the bug tracker

[Brendan]

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

Brendan <bunf2...@apps.opensourcelaw.biz> changed:

   What|Removed |Added

   Severity|normal  |wishlist

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

[krita] [Bug 381343] New: Application fails to close on scripting bug if main window closed first

[Brendan]

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

Bug ID: 381343
   Summary: Application fails to close on scripting bug if main
window closed first
   Product: krita
   Version: 4.0 pre-alpha
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: bunf2...@apps.opensourcelaw.biz
  Target Milestone: ---

If a script has an error Krita displays a dialog with a stack trace. If you
close the Krita window before closing the dialog, Krita doesn't return. 

To replicate:
run sample code below from scripting menu
when error dialog appears, click the close icon on the main Krita window
then click the close button or the close icon on the dialog window. 


Sample code:

import krita

class Tester(krita.Extension):
def __init__(self, parent):
super().__init__(parent)

def tester(self):
print("No object called ",  UNKNOWN_OBJECT)

def setup(self):
action = Application.createAction("Tester")
action.triggered.connect(self.tester)

Scripter.addExtension(Tester(Application))

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

[krita] [Bug 381342] New: Please add a scripting component to the bug tracker

[Brendan]

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

Bug ID: 381342
   Summary: Please add a scripting component to the bug tracker
   Product: krita
   Version: 4.0 pre-alpha
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: bunf2...@apps.opensourcelaw.biz
  Target Milestone: ---

Have a bug with scripting, think there'll be more. Suggest adding a scripting
component rather than putting them in general.

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

[kwin] [Bug 371883] New: Crash while using chrome

[Brendan Ingham]

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

Bug ID: 371883
   Summary: Crash while using chrome
   Product: kwin
   Version: 5.8.2
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: brendan.ingha...@gmail.com
  Target Milestone: ---

Application: kwin_x11 (5.8.2)

Qt Version: 5.7.0
Frameworks Version: 5.27.0
Operating System: Linux 4.8.4-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed:
switching tabs in Google Chrome, 
Should note that this is a Multi-monitor setup.
- Unusual behavior I noticed:
Kwin decided that chrome should be transparent, and stuck in the 'moving'
phase', had to move to a tty, and ran kwin_x11 --replace to solve the issue.

The crash does not seem to be reproducible.

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

Thread 4 (Thread 0x7f41a5d58700 (LWP 11667)):
#0  0x7f41c73f3551 in ppoll () at /usr/lib/libc.so.6
#1  0x7f41c4aa5ac9 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2  0x7f41c4aa73b8 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7f41c4a5423a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7f41c48770f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7f41bf3fd2d5 in  () at /usr/lib/libQt5Qml.so.5
#6  0x7f41c487bd78 in  () at /usr/lib/libQt5Core.so.5
#7  0x7f41c06a2454 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f41c73fc7df in clone () at /usr/lib/libc.so.6

Thread 3 (Thread 0x7f41a7fff700 (LWP 11657)):
#0  0x7f41c73f3551 in ppoll () at /usr/lib/libc.so.6
#1  0x7f41c4aa5ac9 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2  0x7f41c4aa73b8 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7f41c4a5423a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7f41c48770f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7f41be5c7e55 in  () at /usr/lib/libQt5DBus.so.5
#6  0x7f41c487bd78 in  () at /usr/lib/libQt5Core.so.5
#7  0x7f41c06a2454 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f41c73fc7df in clone () at /usr/lib/libc.so.6

Thread 2 (Thread 0x7f41adc13700 (LWP 11656)):
#0  0x7f41c73f348d in poll () at /usr/lib/libc.so.6
#1  0x7f41c65388e0 in  () at /usr/lib/libxcb.so.1
#2  0x7f41c653a679 in xcb_wait_for_event () at /usr/lib/libxcb.so.1
#3  0x7f41aeaeb449 in  () at /usr/lib/libQt5XcbQpa.so.5
#4  0x7f41c487bd78 in  () at /usr/lib/libQt5Core.so.5
#5  0x7f41c06a2454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f41c73fc7df in clone () at /usr/lib/libc.so.6

Thread 1 (Thread 0x7f41c79a6840 (LWP 11654)):
[KCrash Handler]
#6  0x7f4196ede7b5 in  () at /usr/lib/libnvidia-glcore.so.370.28
#7  0x7f41972d65c6 in  () at /usr/lib/libnvidia-glcore.so.370.28
#8  0x7f419740c8b6 in  () at /usr/lib/libnvidia-glcore.so.370.28
#9  0x7f4197087903 in  () at /usr/lib/libnvidia-glcore.so.370.28
#10 0x7f41970517e2 in  () at /usr/lib/libnvidia-glcore.so.370.28
#11 0x7f41c02423d1 in KWin::GLShader::link() () at
/usr/lib/libkwinglutils.so.9
#12 0x7f41c02491ef in
KWin::ShaderManager::generateCustomShader(QFlags, QByteArray
const&, QByteArray const&) () at /usr/lib/libkwinglutils.so.9
#13 0x7f41c0249312 in
KWin::ShaderManager::generateShader(QFlags) () at
/usr/lib/libkwinglutils.so.9
#14 0x7f41c02493bc in
KWin::ShaderManager::shader(QFlags) () at
/usr/lib/libkwinglutils.so.9
#15 0x7f41c02495ce in
KWin::ShaderManager::pushShader(QFlags) () at
/usr/lib/libkwinglutils.so.9
#16 0x7f41c6fab310 in  () at /usr/lib/libkwin.so.5
#17 0x7f41c6fab636 in KWin::SceneOpenGL::createScene(QObject*) () at
/usr/lib/libkwin.so.5
#18 0x7f41c6f821dc in KWin::Compositor::slotCompositingOptionsInitialized()
() at /usr/lib/libkwin.so.5
#19 0x7f41c6f82bd2 in KWin::Compositor::setup() () at /usr/lib/libkwin.so.5
#20 0x7f41c4a824b9 in QObject::event(QEvent*) () at
/usr/lib/libQt5Core.so.5
#21 0x7f41c5735e0c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#22 0x7f41c573d581 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib/libQt5Widgets.so.5
#23 0x7f41c4a55de0 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#24 0x7f41c4a5856d in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib/libQt5Core.so.5
#25 0x7f41c4aa71fa in

[krita] [Bug 370193] New: Save file didn't save work

[Brendan via KDE Bugzilla]

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

Bug ID: 370193
   Summary: Save file didn't save work
   Product: krita
   Version: 3.0
  Platform: Appimage
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: bunf2...@apps.opensourcelaw.biz

I opened up my file from yesterday to find that roughly an hour or so of work I
did yesterday wasn't saved. I thought I had saved it, so I checked the file's
timestamp. It was timestamped when I finished work (just after midnight), so I
don't know what happened there.  I was working on a saved "incremental
version".
Just renamed and opened the "~" file and my work is in there. 


Reproducible: Always

Steps to Reproduce:
1. I can't reproduce it. This is really just here in case someone else also has
the problem. 
2.
3.

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