from:"jeremy"

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

Bug ID: 483181
   Summary: Exit edit mode does not exit when panel settings are
closed
Classification: Plasma
   Product: plasmashell
   Version: 6.0.1
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Desktop Containment
  Assignee: plasma-b...@kde.org
  Reporter: jeremypl...@gmail.com
CC: notm...@gmail.com
  Target Milestone: 1.0

Created attachment 166919
  --> https://bugs.kde.org/attachment.cgi?id=166919=edit
Exit edit mode not exiting when panel settings closed

SUMMARY

Right clicking the taskbar panel while in edit mode and the panel settings is
closed, then clicking "Exit Edit Mode" does not actually exit. Instead, it
opens back the panel settings.

STEPS TO REPRODUCE
1. Enter Edit Mode
2. Close the panel settings (by clicking the desktop)
2. Right click the taskbar
3. Click "Exit Edit Mode"

OBSERVED RESULT

The panel settings window opens.

EXPECTED RESULT

Edit mode exits.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version:  6.0.1
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2

ADDITIONAL INFORMATION

This seems similar to this bug: https://bugs.kde.org/show_bug.cgi?id=476970

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

[plasmashell] [Bug 483175] Hovering between active window icons inconsistently showing window previews

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

--- Comment #1 from Jeremy Plsek  ---
Created attachment 166918
  --> https://bugs.kde.org/attachment.cgi?id=166918=edit
This video shows it kind of working as expected, but still odd behavior

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

[plasmashell] [Bug 483175] New: Hovering between active window icons inconsistently showing window previews

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

Bug ID: 483175
   Summary: Hovering between active window icons inconsistently
showing window previews
Classification: Plasma
   Product: plasmashell
   Version: 6.0.1
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Task Manager and Icons-Only Task Manager
  Assignee: plasma-b...@kde.org
  Reporter: jeremypl...@gmail.com
CC: qydwhotm...@gmail.com
  Target Milestone: 1.0

Created attachment 166917
  --> https://bugs.kde.org/attachment.cgi?id=166917=edit
Hover not showing window previews going between apps instantly

SUMMARY

When hovering over active windows, the window preview *sometimes* "follows" the
mouse, showing a "swipe" animation as it goes between active windows. Or it
doesn't work at all.

So it sometimes takes a bit longer to show a window preview when hovering
between apps.

STEPS TO REPRODUCE
1. Have at least two active app windows open beside eachother in the icon only
task manager.
2. Hover over one application and wait for the window preview to show
3. Now move your mouse to the other application

OBSERVED RESULT

The window preview closes, and it takes some time for the new window preview to
show.

Or it sometimes shows a "swipe" animation, but then the window preview closes,
before showing up again some time later.

EXPECTED RESULT

The window preview should be instant when hovering between multiple active
applications once the preview shows up the first time.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 6.0.1
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2

ADDITIONAL INFORMATION

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

[systemsettings] [Bug 483171] New: Titlebar and Frame Actions dropdown width inconsistency on wide window

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

Bug ID: 483171
   Summary: Titlebar and Frame Actions dropdown width
inconsistency on wide window
Classification: Applications
   Product: systemsettings
   Version: 6.0.1
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: kcm_kwinoptions
  Assignee: kwin-bugs-n...@kde.org
  Reporter: jeremypl...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: ---

Created attachment 166916
  --> https://bugs.kde.org/attachment.cgi?id=166916=edit
Dropdown width inconsistent

SUMMARY

The width of the dropdown section for "Titlebar and Frame Actions" "Active"
grows in size as the window gets wider.

STEPS TO REPRODUCE
1. Make the window large enough for the dropdown widths to grow in size.

OBSERVED RESULT

Width of dropdowns in "Active" section inconsistent with "Inactive" section in
wide window size.

EXPECTED RESULT

Width of dropdowns in "Active" section consistent with "Inactive" section in
wide window size.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 6.0.1
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2

ADDITIONAL INFORMATION

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

[systemsettings] [Bug 483169] New: Custom shortcut keys do not stay to the right edge of the window

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

Bug ID: 483169
   Summary: Custom shortcut keys do not stay to the right edge of
the window
Classification: Applications
   Product: systemsettings
   Version: 6.0.1
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: kcm_keys
  Assignee: plasma-b...@kde.org
  Reporter: jeremypl...@gmail.com
CC: k...@david-redondo.de
  Target Milestone: ---

Created attachment 166914
  --> https://bugs.kde.org/attachment.cgi?id=166914=edit
Button gap

SUMMARY

Custom shortcut keys do not stay to the right edge of the window.

STEPS TO REPRODUCE
1. Add a custom shortcut key for an application/action

OBSERVED RESULT

The button displaying the shortcut is several pixels off the right edge of the
window instead of staying sticky. The gap also grows larger as the window gets
wider.

EXPECTED RESULT

The buttons stay to the right edge of the window like the "Add custom shortcut"
button.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 6.0.1
KDE Frameworks Version: 6.0.0
Qt Version: 6.2.2

ADDITIONAL INFORMATION

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

[systemsettings] [Bug 483167] New: Checkbox hover effect should match other checkboxes in monitor graphic

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

Bug ID: 483167
   Summary: Checkbox hover effect should match other checkboxes in
monitor graphic
Classification: Applications
   Product: systemsettings
   Version: 6.0.1
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: kcm_kwinscreenedges
  Assignee: kwin-bugs-n...@kde.org
  Reporter: jeremypl...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: ---

Created attachment 166907
  --> https://bugs.kde.org/attachment.cgi?id=166907=edit
Current checkbox behavior

SUMMARY

This is mainly regarding consistency, that when hovering over the checkbox, I
think it should have an outline similar to other checkboxes instead of going
transparent.

STEPS TO REPRODUCE
1. Hover over a checkbox in the monitor graphic

OBSERVED RESULT

The checkbox becomes transparent (when unselected) or the background becomes
transparent (when selected)

EXPECTED RESULT

The checkbox background stays visible, and has an outline like other
checkboxes.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 6.0.1
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2

ADDITIONAL INFORMATION

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

[systemsettings] [Bug 482696] Game Controller setting blocks UI before loading the page

2024-03-07 Thread Jeremy Whiting

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

Jeremy Whiting  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

--- Comment #1 from Jeremy Whiting  ---
https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/2095 has a
temporary fix that makes the GUI look responsive even though it's taking a
couple of seconds to do the SDL_Init. A better solution will be to do all SDL
operations in a background thread. I'll look into that next.

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

[plasma-integration] [Bug 481998] New: problème shutdown plasma 6

2024-02-28 Thread baldin jeremy

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

Bug ID: 481998
   Summary: problème shutdown plasma 6
Classification: Plasma
   Product: plasma-integration
   Version: master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: baldin.jer...@orange.fr
  Target Milestone: ---

Impossible d’arrêter ou redémarrer le système a partir du lanceur d'application
ni en mode console. Seul la veille semble fonctionner.

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

[neon] [Bug 481938] Unable to leave session via Desktop menu on Plasma 6.0.0

2024-02-28 Thread baldin jeremy

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

baldin jeremy  changed:

   What|Removed |Added

 CC||baldin.jer...@orange.fr
  Component|Packages User Edition   |general

--- Comment #16 from baldin jeremy  ---
impossible d’arrêter ou redémarrer le système a partir du menu Seul la mise en
veille fonctionne après la mise a jour vers plasma

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

[okular] [Bug 480901] "Configure Okular" window under "Settings" menu is slow to open

2024-02-06 Thread Jeremy Whiting

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

--- Comment #3 from Jeremy Whiting  ---
That looks like spd_list_voices is taking a while. I'm willing to bet money
they have speech-dispatcher configured to use espeak or espeak-ng which in some
recent versions of speech-dispatcher give a way longer list than it should.
Setting it up with espeak-ng here on arch and running spd-say -L to give the
list of voices on the command line takes a couple of seconds and gives a list
of 13363 different voices... (because it's including all locales and some
mbrola variants, etc.)

Unfortunately there's not really a gui to configure speech-dispatcher yet.
Users that hit this can edit their configuration files in
~/.config/speech-dispatcher/speechd.conf to disable espeak and other
problematic synthesizers that have this issue. Or alternatively run spd-conf
and choose a default synthesizer such as flite or festival or pico that each
only have a few voices.

Alternatively I'll take a look and see if we can avoid that call in okular
until the user asks for the Accessibility page maybe, though that would slow
down switching to that page from other pages.

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

[Skanpage] [Bug 469270] Skanpage crashes when trying to do OCR if tesseract is not installed

2023-10-22 Thread Jeremy Cook

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

Jeremy Cook  changed:

   What|Removed |Added

 CC||jeremycook...@gmail.com

--- Comment #3 from Jeremy Cook  ---
This also crashes Skanpage on Debian 12 Bookworm when using "Export PDF." The
"Enable optical character recognition (OCR)" option was checked by default (I
did not check it) and no languages were listed (not even English). I had
installed Skanpage via Discover from the Debian repo. I had not installed
tesseract-ocr.

Next I apt installed tesseract-ocr, exited and restarted Skanpage. When I
clicked Export PDF the Enable OCR option was checked like before but "American
English [eng]" also appeared with an unchecked checkbox beside it. I left
"American English [eng]" unchecked and "Enable optical character recognition
(OCR)" checked, and was able to generate a PDF without the crash.

I also tried "Save All" instead of "Export PDF" before installing
tesseract-ocr, and that worked without crashing. It presumably makes no attempt
at OCR.

Operating System: Debian GNU/Linux 12
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Kernel Version: 6.1.0-13-amd64 (64-bit)
Graphics Platform: Wayland

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

[kmymoney] [Bug 475841] New: payees with different case not recognized until asking

2023-10-19 Thread Jeremy Whiting

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

Bug ID: 475841
Summary: payees with different case not recognized until asking
Classification: Applications
Product: kmymoney
Version: git (master)
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: ux-ui
Assignee: kmymoney-de...@kde.org
Reporter: jpwhit...@kde.org
Target Milestone: ---

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
If you enter a new transaction, but type the payee with slightly different case
a popup asks if you want to add a new payee (but already has any existing
payee's case in the question). If you click Yes, it adds a new payee with [1]
at the end of the name.

STEPS TO REPRODUCE
1. Enter a transaction with an existing payee with one letter case changed.
I.e. bank instead of Bank
2. Watch when the gui asks if you want to add "Bank" as a new payee.
3. Click Yes

OBSERVED RESULT
"Bank [1]" added to the list of payees.

EXPECTED RESULT
Either or both of:
1. Bank payee left alone, no new payee added.
2. bank corrected to Bank and no question about payee asked.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Archlinux
(available in About System)
KDE Plasma Version: Plasma6 built from git
KDE Frameworks Version: KF5 from arch packages, 5.110.0-1 currently
Qt Version: 5.15.11-1 from arch packages.

ADDITIONAL INFORMATION

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

[filelight] [Bug 144948] [wish] Correctly count hardlinks in Filelight

2023-09-27 Thread Jeremy Whiting

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

Jeremy Whiting  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 CC||jpwhit...@kde.org
 Resolution|--- |FIXED

--- Comment #10 from Jeremy Whiting  ---
Fixed in January here:
https://invent.kde.org/utilities/filelight/commit/7356cc3bc8164073e161820c32321ec8bf5b52c4
so was in Gear 23.04 and newer.

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

[filelight] [Bug 406030] hard links multiply counted in usage totals

2023-09-27 Thread Jeremy Whiting

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

--- Comment #4 from Jeremy Whiting  ---
Yep, good point. I'll update that one also. One moment.

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

[dolphin] [Bug 474512] kio 5.110.1-1 causes dolphin to crash when overwriting files with copy/paste

2023-09-13 Thread Jeremy

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

Jeremy  changed:

   What|Removed |Added

Summary|kio 5.110.1-1 causes|kio 5.110.1-1 causes
   |dolphin to crash when   |dolphin to crash when
   |overwriting files with copy |overwriting files with
   ||copy/paste

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

[dolphin] [Bug 474512] New: kio 5.110.1-1 causes dolphin to crash when overwriting files with copy

2023-09-13 Thread Jeremy

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

Bug ID: 474512
   Summary: kio 5.110.1-1 causes dolphin to crash when overwriting
files with copy
Classification: Applications
   Product: dolphin
   Version: 23.08.0
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: bluishhumil...@duck.com
CC: kfm-de...@kde.org
  Target Milestone: ---

SUMMARY
***

When copying identically named files from one directory to another, choosing
the "overwrite" option causes Dolphin to crash.

Downgrading kio from 5.110.0-1 to 5.109.0-2 resolves the issue.

***


STEPS TO REPRODUCE
1.  mkdir test1 test2
2.  touch test1/file{1..9}.txt test2/file{1..9}.txt
3.  In Dolphin, copy the nine files out of test1 and paste to test2
4.  When prompted to overwrite, rename, or skip, choose overwrite.

OBSERVED RESULT
Dolphin reliably dumps core. Downgrading kio from 5.110.0-1 to 5.109.0-2
resolves the issue.

EXPECTED RESULT
The expected result would be the application succeeds in overwriting the files
without crashing.

SOFTWARE/OS VERSIONS

Linux/KDE Plasma:
(available in About System)
KDE Plasma Version: 5.27.8-1
KDE Frameworks Version: 5.110.0-1
Qt Version: I'm not sure what this means, I hope this helps:
pacman -Q | grep qt
appstream-qt 0.16.3-1
layer-shell-qt 5.27.8-1
libdbusmenu-qt5 0.9.3+16.04.20160218-6
modemmanager-qt 5.110.0-1
networkmanager-qt 5.110.0-1
phonon-qt5 4.11.1-3
phonon-qt5-gstreamer 4.10.0-4
polkit-qt5 0.114.0-1
poppler-qt5 23.08.0-1
python-pyqt6 6.5.2-1
python-pyqt6-sip 13.5.2-1
python-pyqt6-webengine 6.5.0-2
python-sphinxcontrib-qthelp 1.0.6-1
qca-qt5 2.3.7-1
qt5-base 5.15.10+kde+r155-1
qt5-declarative 5.15.10+kde+r31-1
qt5-graphicaleffects 5.15.10-1
qt5-location 5.15.10+kde+r4-2
qt5-multimedia 5.15.10+kde+r3-1
qt5-quickcontrols 5.15.10-1
qt5-quickcontrols2 5.15.10+kde+r6-1
qt5-sensors 5.15.10-1
qt5-speech 5.15.10+kde+r1-1
qt5-svg 5.15.10+kde+r8-1
qt5-tools 5.15.10+kde+r3-2
qt5-translations 5.15.10-1
qt5-wayland 5.15.10+kde+r57-1
qt5-webchannel 5.15.10+kde+r3-1
qt5-webengine 5.15.15-1
qt5-x11extras 5.15.10-1
qt6-base 6.5.2-1
qt6-declarative 6.5.2-2
qt6-imageformats 6.5.2-1
qt6-positioning 6.5.2-1
qt6-svg 6.5.2-1
qt6-translations 6.5.2-1
qt6-webchannel 6.5.2-1
qt6-webengine 6.5.2-3
qtermwidget 1.3.0-2

ADDITIONAL INFORMATION

Here is the stack trace. Apologies, it is just from the journal so it doesn't
have debug symbols.

Sep 13 21:20:56 nuc dolphin[68032]: kf.kio.workers.file: copy()
QUrl("file:///home/jeremy/test1/file1.txt") to
QUrl("file:///home/jeremy/test2/file1.txt") mode= 420
Sep 13 21:20:56 nuc kernel: KIO::WorkerThre[68132]: segfault at 8 ip
7f559156c154 sp 7f55656188a8 error 4 in
libKF5KIOCore.so.5.110.0[7f55914dc000+db000] likely on CPU 11 (core 3, socket
0)
Sep 13 21:20:56 nuc kernel: Code: f8 48 8b 4a 10 48 89 0f 8b 11 83 c2 01 83 fa
01 77 04 c3 0f 1f 00 f0 83 01 01 c3 90 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e
fa <48> 8b 56 08 48 89 f8 48 8b 4a 18 48 89 0f 8b 11 83 c2 01 83 fa 01
Sep 13 21:20:56 nuc systemd[1]: Started Process Core Dump (PID 68411/UID 0).
Sep 13 21:20:56 nuc systemd-coredump[68412]: [] Process 68032 (dolphin) of
user 1000 dumped core.

 Stack trace of thread 68132:
 #0  0x7f559156c154
_ZNK11KMountPoint9mountTypeEv (libKF5KIOCore.so.5 + 0xd9154)
 #1  0x7f555ea1687d n/a
(kio_file.so + 0x1287d)
 #2  0x7f55915198db
_ZN3KIO9SlaveBase8dispatchEiRK10QByteArray (libKF5KIOCore.so.5 + 0x868db)
 #3  0x7f559151220e
_ZN3KIO9SlaveBase12dispatchLoopEv (libKF5KIOCore.so.5 + 0x7f20e)
 #4  0x7f5591592e87 n/a
(libKF5KIOCore.so.5 + 0xffe87)
 #5  0x7f558f6f35da n/a
(libQt5Core.so.5 + 0xf35da)
 #6  0x7f558ee8c9eb n/a
(libc.so.6 + 0x8c9eb)
 #7  0x7f558ef10dfc n/a
(libc.so.6 + 0x110dfc)

 Stack trace of thread 68034:
 #0  0x7f558ef0359f __poll
(libc.so.6 + 0x10359f)
 #1  0x7f558cf22d9d n/a
(libQt5WaylandClient.so.5 + 0x72d9d)
 #2  0x7f558f6f35da n/a
(libQt5Core.so.5 + 0xf35da)
 #3  0x7f558ee8c9eb n/a
(libc.so.6 + 0x8c9eb)
 #4  0x7f558ef10dfc n/a
(libc.so.6 + 0x110dfc)

[kmymoney] [Bug 473223] Data lost on kmymoney-master-2001-macos-clang-x86_64.dmg upgrade

2023-08-11 Thread Jeremy Whiting

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

Jeremy Whiting  changed:

   What|Removed |Added

 CC||jpwhit...@kde.org

--- Comment #8 from Jeremy Whiting  ---
On MacOS usually the .app contents aren't added to your PATH variable. So to
run you'll have to do something like
/Applications/KMyMoney.app/Contents/MacOS/kmymoney  I
haven't tried kmymoney on mac lately, not sure what the path is but adjust
accordingly.

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

[kwin] [Bug 468530] 1-2 seconds of video lag with DisplayLink DL-195 GPU (udl driver)

2023-04-15 Thread Jeremy Rand

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

--- Comment #1 from Jeremy Rand  ---
Forgot to mention that both the AST2500 display and the DL-195 display are
running at 1920x1080 resolution, in case that matters for reproducing it.

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

[kwin] [Bug 468530] New: 1-2 seconds of video lag with DisplayLink DL-195 GPU (udl driver)

2023-04-15 Thread Jeremy Rand

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

Bug ID: 468530
   Summary: 1-2 seconds of video lag with DisplayLink DL-195 GPU
(udl driver)
Classification: Plasma
   Product: kwin
   Version: 5.27.4
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: jeremyr...@danwin1210.de
  Target Milestone: ---

SUMMARY

My machine (POWER9 ppc64le, DD2.3 stepping) has two GPU's: an integrated ASPEED
AST2500 (ast Linux driver), and an external SIIG JU-DV0112-S1 (DisplayLink
DL-195 chipset, udl Linux driver, connected via USB). Both are unaccelerated,
so 3D operations use LLVMpipe. The AST2500 seems to perform fine with Plasma
(no perceptible lag), but the DL-195 exhibits nontrivial video lag (~1-2
seconds) with Plasma. Both GPU's perform fine (no perceptible lag) with GNOME
Classic, so I'm reasonably confident that this is not a hardware or kernel
issue.

STEPS TO REPRODUCE

1. Plug in a DL-195 USB GPU.
2. Configure Plasma to use the DL-195 GPU to extend the desktop to the right.
3. Drag a large window between the main display and the DL-195 display, back
and forth, as fast as feasible with the mouse, for around 15 seconds.
4. Release the window while it's on the main display.

OBSERVED RESULT

The main display will show the window no longer moving immediately, but the
DL-195 display will continue to show the window moving back and forth for
around 1-2 more seconds, i.e. the video is lagging on the DL-195 display.

EXPECTED RESULT

Both displays should show the window no longer moving immediately, i.e. no
perceptible lag.

SOFTWARE/OS VERSIONS

Operating System: Fedora Linux 38
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8
Kernel Version: 6.3.0-0.rc5.20230407gitf2afccfefe7b.46.fc39.ppc64le (64-bit)
Graphics Platform: Wayland
Processors: 144 × POWER9, altivec supported
Memory: 14.8 GiB of RAM
Graphics Processor: llvmpipe
Product Name: T2P9S01 REV 1.01

ADDITIONAL INFORMATION

Happy to provide more details on request.

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

[KScreen] [Bug 466208] Display arrangement is lost after reboot when using "Extend" button in KScreen widget

2023-04-15 Thread Jeremy Rand

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

Jeremy Rand  changed:

   What|Removed |Added

 CC||jeremyr...@danwin1210.de

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

[kde-cli-tools] [Bug 429408] kde-open5 changes case of argument

2023-03-08 Thread Jeremy W. Murphy

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

Jeremy W. Murphy  changed:

   What|Removed |Added

 CC||jeremy.william.murphy@gmail
   ||.com

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

[krita] [Bug 455998] tried using the rectangle selection tool . ibut instead it preformed a line tool

2023-01-26 Thread jeremy

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

--- Comment #2 from jeremy  ---
 hi thanks for responding. 
i use mouse or 

XP-Pen Artist10 10.1
 to select tools only. i dont use keyboard shortcuts. 



On Thursday, January 26, 2023 at 07:53:53 AM CST, wolthera
 wrote:  

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

wolthera  changed:

          What    |Removed                    |Added

                CC|                            |griffinval...@gmail.com
        Resolution|---                        |WAITINGFORINFO
            Status|REPORTED                    |NEEDSINFO

--- Comment #1 from wolthera  ---
Hey,

I cannot reproduce with the Krita Version: 5.2.0-prealpha (git 5c98a72)
Appimage with Qt 5.15.7

How are you selecting the different tools? Are you using keyboard shortcuts?

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

[filelight] [Bug 406030] hard links multiply counted in usage totals

2023-01-17 Thread Jeremy Whiting

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

Jeremy Whiting  changed:

   What|Removed |Added

   Version Fixed In||23.03
 CC||jpwhit...@kde.org

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

[filelight] [Bug 406030] hard links multiply counted in usage totals

2023-01-17 Thread Jeremy Whiting

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

Jeremy Whiting  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|ASSIGNED|RESOLVED
  Latest Commit||https://invent.kde.org/util
   ||ities/filelight/commit/7356
   ||cc3bc8164073e161820c32321ec
   ||8bf5b52c4

--- Comment #2 from Jeremy Whiting  ---
Git commit 7356cc3bc8164073e161820c32321ec8bf5b52c4 by Jeremy Whiting.
Committed on 17/01/2023 at 17:50.
Pushed by whiting into branch 'master'.

Don't double count hard link files.
On posix file systems, if the number of links for a file is >1
add it to a set the first time we count it and never count it again.
Fixes double counting files that aren't taking twice as much space.

M  +4-0autotests/directoryIteratorTest.cpp
M  +2-2autotests/localListerTest.cpp
M  +1-0src/directoryEntry.h
M  +1-1src/localLister.cpp
M  +13   -0src/posixWalker.cpp
M  +4-0src/posixWalker.h

https://invent.kde.org/utilities/filelight/commit/7356cc3bc8164073e161820c32321ec8bf5b52c4

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

[digikam] [Bug 462744] Will Digikam run on Apple M1 or M2 chips?

2022-12-07 Thread Jeremy Whiting

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

Jeremy Whiting  changed:

   What|Removed |Added

 CC||jpwhit...@kde.org

--- Comment #1 from Jeremy Whiting  ---
Created attachment 154395
  --> https://bugs.kde.org/attachment.cgi?id=154395=edit
Already works

Just tested the latest x86_64 pkg from
https://download.kde.org/stable/digikam/7.9.0/ works like a charm here on an m1
mac mini thanks to rosetta. Should work fine.

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

[frameworks-kdoctools] [Bug 461139] New: Item is somehow getting linked to KStars qml type from other documentation

2022-10-28 Thread Jeremy Whiting

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

Bug ID: 461139
   Summary: Item is somehow getting linked to KStars qml type from
other documentation
Classification: Frameworks and Libraries
   Product: frameworks-kdoctools
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kde-doc-engl...@kde.org
  Reporter: jpwhit...@kde.org
CC: kdelibs-b...@kde.org
  Target Milestone: ---

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

I noticed when I was checking what KStatusNotifierItem does and how it works
today that
https://api.kde.org/frameworks/knotifications/html/classKStatusNotifierItem.html#details
is linking to a KStars Item class even though it's not a class, but a QML type.
Then also noticed on https://lxr.kde.org/ident?v=kf5-qt5&_i=Item many things
link to it, but shouldn't. Is there some way to filter out these generic things
(or would it be better to rename the KStars qml "Item" to KStarsItem or
something to clear it up?

STEPS TO REPRODUCE
1.  Read the docs
2.  Notice stuff is linking to kstars Item that shouldn't be
3. 

OBSERVED RESULT


EXPECTED RESULT


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

ADDITIONAL INFORMATION

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

[dolphin] [Bug 458472] New: Tab appears to selects wrong file when re-ordered

2022-08-29 Thread Jeremy

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

Bug ID: 458472
   Summary: Tab appears to selects wrong file when re-ordered
   Product: dolphin
   Version: 22.08.0
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: borgman.jer...@pm.me
CC: kfm-de...@kde.org
  Target Milestone: ---

Created attachment 151684
  --> https://bugs.kde.org/attachment.cgi?id=151684=edit
glitch

SUMMARY
When the file names are sorted by name and you re-name a file and "tab" to the
next file, the re-ordering of the list appears to select the wrong file. The
attached gif may help better than the steps to reproduce. 


STEPS TO REPRODUCE
1. Create a set of files (1.txt, 2.txt  5.txt) 
2. Set view to "detailed"
3. Sort files by name
4. Start renaming the files from 1.txt to a.txt
5. Hit tab to go to the next file
6. See that the wrong file is selected

OBSERVED RESULT
I see that it initially selects "2.txt" but then after the files are re-ordered
"3.txt" is selected and will be renamed

EXPECTED RESULT
I expect 2.txt to be selected since that was the next in the list when I hit
tab. 

Operating System: EndeavourOS
KDE Plasma Version: 5.25.4
KDE Frameworks Version: 5.97.0
Qt Version: 5.15.5
Kernel Version: 5.15.63-1-lts (64-bit)
Graphics Platform: X11
Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: AMD Radeon RX 6800 XT
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: X570 AORUS ULTRA
System Version: -CF

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

[krita] [Bug 455998] New: tried using the rectangle selection tool . ibut instead it preformed a line tool

2022-06-26 Thread jeremy

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

Bug ID: 455998
   Summary: tried using the rectangle selection tool . ibut
instead it preformed a line tool
   Product: krita
   Version: 5.0.5
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Tools/Selection
  Assignee: krita-bugs-n...@kde.org
  Reporter: koons...@yahoo.com
  Target Milestone: ---

Created attachment 150178
  --> https://bugs.kde.org/attachment.cgi?id=150178=edit
screen shot of krita . cannot save original file . not responding.

SUMMARY
designing an abacus on krita. using line tools brush tools and selection tools
 i flaten image.

 doesnt happen with free hand selection tool . or oval selection tool for me. 
just rectangle tool.
 when using rectangle selection tool it is  replacing it with line tool.
 i canot Undo that line tool .
 i flatten image i undo redo. i try cutting and. i cant even brush over it.
happened 3 times now in a row.

use draw tools to make lines. use brush tool to make circles ( like beadS)
make a  retangle selection tool. - if its reproduced you should see same color
of line tool used
. not selection tool 
happened 3 times now. in a row.
I canno

STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT
rectangle selection tool doesnt work instead getting line tool that i cant
erase ,brush over  ,or flatten.


EXPECTED RESULT
use retangle selection tool to select an area .


SOFTWARE/OS VERSIONS
Windows: 10 latest patched. same with nvidia drivers. 
intel i 7 4790k processor

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

[Craft] [Bug 454506] Dbus fails to build on arm64 macOS (Apple sillicon / M1 hardware)

2022-06-12 Thread Jeremy Whiting

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

Jeremy Whiting  changed:

   What|Removed |Added

 CC||jpwhit...@kde.org

--- Comment #2 from Jeremy Whiting  ---
>ld: warning: ignoring file /Users/javier/CraftRoot/lib/libexpat.dylib, 
>building for macOS-arm64 but attempting to link with file built for 
>macOS-x86_64


that's the key, it's trying to build a x86_64 build but trying to link to arm
libraries. It seems the craft ini file change to arm isn't taking effect in
this case. Since it's built with cmake the key is to add
https://cmake.org/cmake/help/latest/variable/CMAKE_OSX_ARCHITECTURES.html
somehow. Maybe cmake is already setting this (or craft is using cmake to set
that) but that's the key.

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

[kmymoney] [Bug 454821] Unexpected application crash when trying to save the changes of a new transaction

2022-06-03 Thread Jeremy Whiting

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

--- Comment #2 from Jeremy Whiting  ---
https://lists.gnupg.org/pipermail/gnutls-help/2022-May/004744.html has some
details also. Seems they released gnutls 3.7.6 to mitigate this regression in
3.7.5.

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

[kmymoney] [Bug 454821] Unexpected application crash when trying to save the changes of a new transaction

2022-06-03 Thread Jeremy Whiting

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

Jeremy Whiting  changed:

   What|Removed |Added

 CC||jpwhit...@kde.org
 Status|REPORTED|RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Jeremy Whiting  ---
This is another duplicate of https://bugs.kde.org/show_bug.cgi?id=453857 See
that bug for details, but basically it's a regression in gnutls 3.7.5. Either
downgrade to gnutls 3.7.4 or ask your distribution to patch gnutls with the
patch mentioned on that bug.

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

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

[kmymoney] [Bug 453857] malloc() aborts during save

2022-06-03 Thread Jeremy Whiting

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

Jeremy Whiting  changed:

   What|Removed |Added

 CC||diorte...@gmail.com

--- Comment #14 from Jeremy Whiting  ---
*** Bug 454821 has been marked as a duplicate of this bug. ***

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

[kmymoney] [Bug 453857] malloc() aborts during save

2022-05-27 Thread Jeremy Whiting

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

Jeremy Whiting  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=454485

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

[kmymoney] [Bug 454485] KMyMoney crashed when opening a ledger

2022-05-27 Thread Jeremy Whiting

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

Jeremy Whiting  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=453857

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

[kmymoney] [Bug 454485] KMyMoney crashed when opening a ledger

2022-05-27 Thread Jeremy Whiting

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

Jeremy Whiting  changed:

   What|Removed |Added

 CC||jpwhit...@kde.org

--- Comment #2 from Jeremy Whiting  ---
Yep, another crash from the gnutls regression. Either downgrade your gnutls to
any version before 3.7.5 which introduced the regression or get a fix in
opensuse 3.7.5 like this one in arch:
https://github.com/archlinux/svntogit-packages/commit/cf4d5e8c600e32251eeacbd08c67f78bd4a3adb3
gnutls 3.7.6 will have the same fix, but won't release until July afaict.

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

[kmymoney] [Bug 454399] kmymoney crashes upon opening

2022-05-26 Thread Jeremy Whiting

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

--- Comment #5 from Jeremy Whiting  ---
Yeah, since it's a regression in gnutls you either need to downgrade that back
from 3.7.5 to 3.7.4 or get opensuse to add the previously mentioned patch to
their 3.7.5 package in a new revision.

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

[kmymoney] [Bug 454399] kmymoney crashes upon opening

2022-05-25 Thread Jeremy Whiting

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

--- Comment #2 from Jeremy Whiting  ---
https://github.com/archlinux/svntogit-packages/commit/cf4d5e8c600e32251eeacbd08c67f78bd4a3adb3
has the patched arch changes in 3.7.5-2 that opensuse and other distros may
want to add to their patches.

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

[kmymoney] [Bug 454399] kmymoney crashes upon opening

2022-05-25 Thread Jeremy Whiting

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

Jeremy Whiting  changed:

   What|Removed |Added

 CC||jpwhit...@kde.org

--- Comment #1 from Jeremy Whiting  ---
Looks like another gnutls caused one. that gnutls_zero_free in the stack trace
points to it. Try downgrading gnutls to 3.7.4 if possible and see if that still
crashes.

BTW, from reading https://gitlab.com/gnutls/gnutls/-/milestones/35#tab-issues I
think the fix in 3.7.6 wont come out until July so it may be useful to see if
opensuse will add the patch here:
https://gitlab.com/gnutls/gnutls/-/merge_requests/1592 to gnutls 3.7.5 in the
mean time.

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

[kmymoney] [Bug 453857] malloc() aborts during save

2022-05-25 Thread Jeremy Whiting

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

Jeremy Whiting  changed:

   What|Removed |Added

 CC||jpwhit...@kde.org

--- Comment #9 from Jeremy Whiting  ---
Yeah, it's only programs that use gmp for multi precision math and also use
gnutls 3.7.5. A fix has been merged for 3.7.6 but not sure when that will be
released. Downgrading gnutls back to 3.7.4 will fix it. We may be able to get
the patch into a new gnutls 3.7.5 package (I've got the same here on arch,
which works well) to get around it until 3.7.6 is released.

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

[kdevelop] [Bug 448152] Building with Xcode fails `ld: malformed 64-bit a.b.c.d.e version number: 5.7.211201`

2022-05-18 Thread Jeremy W. Murphy

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

Jeremy W. Murphy  changed:

   What|Removed |Added

   Version Fixed In||5.8.220402
 Status|REPORTED|RESOLVED
  Latest Commit||https://invent.kde.org/kdev
   ||elop/kdevelop/commit/7d0289
   ||5fd0ef22fb93c4f2a5fc3fe5dfc
   ||7aba4cb
 Resolution|--- |FIXED

--- Comment #3 from Jeremy W. Murphy  ---
Git commit 7d02895fd0ef22fb93c4f2a5fc3fe5dfc7aba4cb by Jeremy W. Murphy.
Committed on 17/05/2022 at 07:44.
Pushed by igorkushnir into branch 'release/22.04'.

On Apple, use project version format compatible with Apple linker
FIXED-IN: 5.8.220402

Using PROJECT here makes sure that it is never out of sync with the ecm
setup in kdevplatform. However, I'm pretty sure that the 'micro' (fourth)
version level is ignored.

M  +12   -1CMakeLists.txt

https://invent.kde.org/kdevelop/kdevelop/commit/7d02895fd0ef22fb93c4f2a5fc3fe5dfc7aba4cb

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

[kmymoney] [Bug 453896] When saving a new transaction Kmymoney crashes each time without saving

2022-05-17 Thread Jeremy Whiting

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

--- Comment #8 from Jeremy Whiting  ---
Problem found. It's because gnutls 3.7.5 is doing this:

commit 41c9c845a342359327403431050d3458246896af
Author: Tobias Heider 
Date:   Mon Mar 14 16:17:28 2022 +0100

Use custom allocators for GMP to make sure temporary secrets
from cryptographic operations in nettle are deleted safely.

Signed-off-by: Tobias Heider 

Which sets the realloc and free functions, but not the malloc one...

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

[kmymoney] [Bug 453896] When saving a new transaction Kmymoney crashes each time without saving

2022-05-17 Thread Jeremy Whiting

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

--- Comment #7 from Jeremy Whiting  ---
Ok, spent too long debugging and trying to get alkvaluetest to pass. Then at
one point noticed the freefunc from mp_get_memory_functions() in alkvalue.cpp
was the same as gnutls_free_zero So I checked pacman.log and yep, recently
upgraded from gnutls 3.7.4-3 to 3.7.5. Downgraded back to 3.7.4-3 and
alkvaluetest passes now... Seems something in gnutls arch package (or upstream
in 3.7.5) broke alkimia. Will look into what could have caused that tomorrow.
In the mean time downgrading gnutls seems to get kmm running again. Saving now
working here, phew.

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

[kmymoney] [Bug 453896] When saving a new transaction Kmymoney crashes each time without saving

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

--- Comment #6 from Jeremy Whiting  ---
Today's testing is pointing to libalkimia. So I got that from git, built it and
kmm crashes in the same way with it as it does with latest libalkimia from arch
packages.

More interestingly I also get this segfault when I run make test in
alkimia/build

Application: alkquoteitemtest (alkquoteitemtest), signal: Aborted

[KCrash Handler]
#4  0x7f3c3848c36c in  () at /usr/lib/libc.so.6
#5  0x7f3c3843c838 in raise () at /usr/lib/libc.so.6
#6  0x7f3c38426535 in abort () at /usr/lib/libc.so.6
#7  0x7f3c3848045e in  () at /usr/lib/libc.so.6
#8  0x7f3c384960cc in  () at /usr/lib/libc.so.6
#9  0x7f3c3849804a in  () at /usr/lib/libc.so.6
#10 0x7f3c3849a8f3 in free () at /usr/lib/libc.so.6
#11 0x7f3c42a3acd6 in __gmp_doprnt () at /usr/lib/libgmp.so.10
#12 0x7f3c42a3c62d in __gmp_vasprintf () at /usr/lib/libgmp.so.10
#13 0x7f3c42a3a2c5 in __gmp_asprintf () at /usr/lib/libgmp.so.10
#14 0x7f3c42b13a22 in mpqToString(mpq_class const&) (val=...) at
/home/jeremy/data/devel/kde/src/extragear/office/alkimia/src/alkvalue.cpp:39
#15 0x7f3c42b14dec in AlkValue::toString() const (this=0x564bbd6af3d0) at
/home/jeremy/data/devel/kde/src/extragear/office/alkimia/src/alkvalue.cpp:239
#16 0x564bbcba2da2 in operator<<(QDBusArgument&, AlkQuoteItem const&)
(argument=..., item=...) at
/home/jeremy/data/devel/kde/src/extragear/office/alkimia/src/alkquoteitem.cpp:192
#17 0x564bbcba0bb8 in AlkQuoteItemTest::qDbusArgument()
(this=0x7fff3f6a0e60) at
/home/jeremy/data/devel/kde/src/extragear/office/alkimia/autotests/alkquoteitemtest.cpp:160
#18 0x564bbcb9c86d in AlkQuoteItemTest::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) (_o=0x7fff3f6a0e60,
_c=QMetaObject::InvokeMetaMethod, _id=5, _a=0x7fff3f6a07b0) at
/home/jeremy/data/devel/kde/src/extragear/office/alkimia/build/autotests/alkquoteitemtest_autogen/EWIEGA46WW/moc_alkquoteitemtest.cpp:93
#19 0x7f3c38be74fe in QMetaMethod::invoke(QObject*, Qt::ConnectionType,
QGenericReturnArgument, QGenericArgument, QGenericArgument, QGenericArgument,
QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument,
QGenericArgument, QGenericArgument, QGenericArgument) const () at
/usr/lib/libQt5Core.so.5
#20 0x7f3c42a75a5c in QTest::qRun() () at /usr/lib/libQt5Test.so.5
#21 0x7f3c42a76c31 in QTest::qExec(QObject*, int, char**) () at
/usr/lib/libQt5Test.so.5
#22 0x564bbcb9f130 in main(int, char**) (argc=1, argv=0x7fff3f6a0fa8) at
/home/jeremy/data/devel/kde/src/extragear/office/alkimia/autotests/alkquoteitemtest.cpp:14
[Inferior 1 (process 1112390) detached]

Which looks like the same backtrace. AlkValue::toString() in some of the others
from kmm itself. Seeing if I can find the cause in alkimia.

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

[kmymoney] [Bug 453896] When saving a new transaction Kmymoney crashes each time without saving

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

--- Comment #5 from Jeremy Whiting  ---
Hmm, going back to an earlier glibc changes the assertion, but it's still an
assertion inside new() operator:
This is from going back to glibc 2.35-3 arch package. Looking into the stdc++
library instead now.

malloc(): unaligned tcache chunk detected

Thread 1 "kmymoney" received signal SIGABRT, Aborted.
0x7576834c in __pthread_kill_implementation () from /usr/lib/libc.so.6
(gdb) bt
#0  0x7576834c in __pthread_kill_implementation () at
/usr/lib/libc.so.6
#1  0x7571b4b8 in raise () at /usr/lib/libc.so.6
#2  0x75705534 in abort () at /usr/lib/libc.so.6
#3  0x7575c397 in __libc_message () at /usr/lib/libc.so.6
#4  0x7577233c in  () at /usr/lib/libc.so.6
#5  0x757768cc in  () at /usr/lib/libc.so.6
#6  0x75a9237d in operator new(unsigned long) (sz=sz@entry=8) at
/usr/src/debug/gcc/libstdc++-v3/libsupc++/new_op.cc:50
#7  0x77a5d218 in
MyMoneyKeyValueContainer::MyMoneyKeyValueContainer(MyMoneyKeyValueContainer
const&) (this=this@entry=0x5df15e50, other=...)
at
/home/jeremy/data/devel/kde/src/extragear/office/kmymoney/kmymoney/mymoney/mymoneykeyvaluecontainer.cpp:29
#8  0x77a68455 in
MyMoneyTransaction::MyMoneyTransaction(MyMoneyTransaction const&)
(this=this@entry=0x5df15e40, other=...)
    at
/home/jeremy/data/devel/kde/src/extragear/office/kmymoney/kmymoney/mymoney/mymoneytransaction.cpp:44
#9  0x77aecbc8 in
QList::node_construct(QList::Node*,
MyMoneyTransaction const&) (this=0x7fffd0e0, t=..., n=0x5df158a8)
at /usr/include/qt/QtCore/qlist.h:465
#10 QList::append(MyMoneyTransaction const&)
(this=this@entry=0x7fffd0e0, t=...) at /usr/include/qt/QtCore/qlist.h:634
#11 0x77ae4425 in
JournalModel::transactionList(QList&,
MyMoneyTransactionFilter&) const (this=0x55c36880, list=..., filter=...)
at /usr/include/qt/QtCore/qsharedpointer_impl.h:301
#12 0x77a28de0 in
MyMoneyFile::transactionList(QList&,
MyMoneyTransactionFilter&) const (this=, list=..., filter=...)
at
/home/jeremy/data/devel/kde/src/extragear/office/kmymoney/kmymoney/mymoney/mymoneyfile.cpp:2031
#13 0x7fff8ab8a528 in MyMoneyStorageXML::writeTransactions(QDomElement&)
(this=0x58c05ba0, transactions=...)
at
/home/jeremy/data/devel/kde/src/extragear/office/kmymoney/kmymoney/plugins/xml/mymoneystoragexml.cpp:1851
#14 0x7fff8ab7ef60 in MyMoneyStorageXML::writeFile(QIODevice*,
MyMoneyFile*) (this=this@entry=0x58c05ba0, qf=qf@entry=0x5df03a00,
file=)
at
/home/jeremy/data/devel/kde/src/extragear/office/kmymoney/kmymoney/plugins/xml/mymoneystoragexml.cpp:1623
#15 0x7fff8ab75947 in XMLStorage::saveToLocalFile(QString const&,
IMyMoneyOperationsFormat*, bool, QString const&)
 (this=0x562394f0, localFile=..., pWriter=0x58c05ba0,
plaintext=, keyList=...) at
/home/jeremy/data/devel/kde/src/extragear/office/kmymoney/kmymoney/plugins/xml/xmlstorage.cpp:512

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

[kmymoney] [Bug 453896] When saving a new transaction Kmymoney crashes each time without saving

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

--- Comment #4 from Jeremy Whiting  ---
Since it's in new/malloc in all cases, I'm wondering if this upgrade to glibc
on the 14th here broke things:

[2022-05-14T09:40:34-0600] [ALPM] upgraded glibc (2.35-4 -> 2.35-5)

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

[kmymoney] [Bug 453896] When saving a new transaction Kmymoney crashes each time without saving

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

--- Comment #3 from Jeremy Whiting  ---
Here's the backtrace when using locally built master branch from git:

Thread 1 "kmymoney" received signal SIGSEGV, Segmentation fault.
0x757735b0 in _int_malloc (av=av@entry=0x758d6bc0 ,
bytes=bytes@entry=48) at malloc.c:3937
3937  bck->fd = bin;
(gdb) bt
#0  0x757735b0 in _int_malloc (av=av@entry=0x758d6bc0 ,
bytes=bytes@entry=48) at malloc.c:3937
#1  0x75774358 in __GI___libc_malloc (bytes=bytes@entry=48) at
malloc.c:3329
#2  0x75a9337d in operator new(unsigned long) (sz=sz@entry=48) at
/usr/src/debug/gcc/libstdc++-v3/libsupc++/new_op.cc:50
#3  0x75e3ec43 in QHashData::detach_helper(void (*)(QHashData::Node*,
void*), void (*)(QHashData::Node*), int, int)
 (this=, node_duplicate=node_duplicate@entry=0x75679c50
::duplicateNode(QHashData::Node*, void*)>,
node_delete=node_delete@entry=0x75679920 ::deleteNode2(QHashData::Node*)>, nodeSize=nodeSize@entry=32,
nodeAlign=nodeAlign@entry=8) at tools/qhash.cpp:503
#4  0x7567b760 in QHash::detach_helper()
(this=this@entry=0x5891c198) at
../../include/QtCore/../../src/corelib/tools/qhash.h:631
#5  0x7567b927 in QHash::detach()
(this=) at
../../include/QtCore/../../src/corelib/tools/qhash.h:291
#6  QMultiHash::insert(QString const&,
QDomNodePrivate* const&) (this=0x5891c198, akey=...,
avalue=@0x7fffcee8: 0x5e32ea00)
at ../../include/QtCore/../../src/corelib/tools/qhash.h:1124
#7  0x7566ee11 in
QDomNamedNodeMapPrivate::setNamedItem(QDomNodePrivate*) (this=0x5891c190,
arg=) at dom/qdom.cpp:2611
#8  0x7fff8ab7ddb8 in
MyMoneyXmlContentHandler::writeKeyValueContainer(MyMoneyKeyValueContainer
const&, QDomDocument&, QDomElement&) (container=, document=...,
parent=...)
at
/home/jeremy/data/devel/kde/src/extragear/office/kmymoney/kmymoney/plugins/xml/mymoneystoragexml.cpp:531
#9  0x7fff8ab896f9 in MyMoneyXmlContentHandler::writeAccount(MyMoneyAccount
const&, QDomDocument&, QDomElement&) (account=..., document=..., parent=...)
at
/home/jeremy/data/devel/kde/src/extragear/office/kmymoney/kmymoney/plugins/xml/mymoneystoragexml.cpp:874
#10 0x7fff8ab89e2c in MyMoneyStorageXML::writeAccount(QDomElement&,
MyMoneyAccount const&) (p=, account=..., this=0x5836a510)
at
/home/jeremy/data/devel/kde/src/extragear/office/kmymoney/kmymoney/plugins/xml/mymoneystoragexml.cpp:1841
#11 MyMoneyStorageXML::writeAccounts(QDomElement&) (this=0x5836a510,
accounts=...) at
/home/jeremy/data/devel/kde/src/extragear/office/kmymoney/kmymoney/plugins/xml/mymoneystoragexml.cpp:1835
#12 0x7fff8ab81f03 in MyMoneyStorageXML::writeFile(QIODevice*,
MyMoneyFile*) (this=this@entry=0x5836a510, qf=qf@entry=0x564a8040,
file=)
at
/home/jeremy/data/devel/kde/src/extragear/office/kmymoney/kmymoney/plugins/xml/mymoneystoragexml.cpp:1619
#13 0x7fff8ab78947 in XMLStorage::saveToLocalFile(QString const&,
IMyMoneyOperationsFormat*, bool, QString const&)

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

[kmymoney] [Bug 453896] When saving a new transaction Kmymoney crashes each time without saving

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

--- Comment #2 from Jeremy Whiting  ---
kmymoney: malloc.c:2617: sysmalloc: Assertion `(old_top == initial_top (av) &&
old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_inuse
(old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)' failed.

Thread 1 "kmymoney" received signal SIGABRT, Aborted.
__pthread_kill_implementation (threadid=, signo=signo@entry=6,
no_tid=no_tid@entry=0) at pthread_kill.c:44
44return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO
(ret) : 0;
(gdb) up
#1  0x7585f3d3 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78
78return __pthread_kill_implementation (threadid, signo, 0);
(gdb) up
#2  0x7580f838 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
26int ret = __pthread_kill (__pthread_self (), sig);
(gdb) up
#3  0x757f9535 in __GI_abort () at abort.c:79
79raise (SIGABRT);
(gdb) up
#4  0x7586928d in __malloc_assert (
assertion=assertion@entry=0x75994628 "(old_top == initial_top (av) &&
old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_inuse
(old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)",
file=file@entry=0x7598f27e "malloc.c", line=line@entry=2617,
function=function@entry=0x75994e98 <__PRETTY_FUNCTION__.8> "sysmalloc") at
malloc.c:307
307   abort ();
(gdb) up
#5  0x7586bc62 in sysmalloc (nb=nb@entry=112,
av=av@entry=0x759cfbc0 ) at malloc.c:2617
2617  assert ((old_top == initial_top (av) && old_size == 0) ||
(gdb) up
#6  0x7586ca5a in _int_malloc (av=av@entry=0x759cfbc0 ,
bytes=bytes@entry=104) at malloc.c:4407
4407  void *p = sysmalloc (nb, av);
(gdb) up
#7  0x7586d358 in __GI___libc_malloc (bytes=bytes@entry=104) at
malloc.c:3329
3329  victim = _int_malloc (ar_ptr, bytes);
(gdb) up
#8  0x75b8e37d in operator new (sz=sz@entry=104) at
/usr/src/debug/gcc/libstdc++-v3/libsupc++/new_op.cc:50
50  /usr/src/debug/gcc/libstdc++-v3/libsupc++/new_op.cc: Directory not
empty.
(gdb) up
#9  0x7731ac4b in QDomElementPrivate::setAttribute (newValue=...,
aname=..., this=0x5d10f020) at dom/qdom.cpp:3960
3960n = new QDomAttrPrivate(ownerDocument(), this, aname);
(gdb) list
3955
3956void QDomElementPrivate::setAttribute(const QString& aname, const
QString& newValue)
3957{
3958QDomNodePrivate* n = m_attr->namedItem(aname);
3959if (!n) {
3960n = new QDomAttrPrivate(ownerDocument(), this, aname);
3961n->setNodeValue(newValue);
3962
3963// Referencing is done by the map, so we set the reference
counter back
3964// to 0 here. This is ok since we created the QDomAttrPrivate.


Seems like an assertion in new -> malloc here. Not sure why though...

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

[kmymoney] [Bug 453896] When saving a new transaction Kmymoney crashes each time without saving

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

Jeremy Whiting  changed:

   What|Removed |Added

 CC||jpwhit...@kde.org

--- Comment #1 from Jeremy Whiting  ---
I'm getting the same with both arch kmymoney and kmymoney built from git here.
(Both using archlinux libalkimia 8.1.1-1 from archlinux package). I thought it
was a flaw in my .kmy file, but a few days old backup has the same problem. I
suspect a bug in libalkimia since the backtrace points at that.

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

[kdevelop] [Bug 448152] Building with Xcode fails `ld: malformed 64-bit a.b.c.d.e version number: 5.7.211201`

2022-04-07 Thread Jeremy W. Murphy

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

--- Comment #2 from Jeremy W. Murphy  ---
I opened a PR: https://invent.kde.org/kdevelop/kdevelop/-/merge_requests/343

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

[kdevelop] [Bug 448152] Building with Xcode fails `ld: malformed 64-bit a.b.c.d.e version number: 5.7.211201`

2022-03-01 Thread Jeremy W. Murphy

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

--- Comment #1 from Jeremy W. Murphy  ---
I assume this is the explanation?
https://www.sicpers.info/2013/03/how-to-version-a-mach-o-library/
Using git revision as the minor version?

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

[kdevelop] [Bug 448245] Crash immediately on startup (Mac M1 Monterey)

2022-03-01 Thread Jeremy W. Murphy

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

--- Comment #1 from Jeremy W. Murphy  ---
I want to add that other KDE applications (KATE, Okteta, Okular) run fine, so
it's not a general problem with KDE applications in MacOS homebrew.

Btw, sorry about the huge description -- in hindsight, I should have put the
MacOS crash report into an attachment.

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

[yakuake] [Bug 383555] Yakuake doesn't show on Screen2 when I'm working on two monitors.

2022-02-16 Thread Jeremy Whiting

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

--- Comment #24 from Jeremy Whiting  ---
And rebooted a moment ago, panel still on the bottom of laptop display (on the
left of screen on the right) but this time yakuake doesn't appear on second
display :( So doesn't seem related to panel placement afterall, just got lucky
last boot to have working yakuake.

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

[yakuake] [Bug 383555] Yakuake doesn't show on Screen2 when I'm working on two monitors.

2022-02-14 Thread Jeremy Whiting

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

--- Comment #23 from Jeremy Whiting  ---
So as a test I moved my panel from being on the left side of my left display to
the bottom of my left display. That didn't help, yakuake still refused to show
on the right display. But then I rebooted. Now yakuake is happily working on
either display again. Not sure if it's related or I just got lucky this time to
not hit the broken state this time around...

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

[yakuake] [Bug 383555] Yakuake doesn't show on Screen2 when I'm working on two monitors.

2022-02-14 Thread Jeremy Whiting

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

Jeremy Whiting  changed:

   What|Removed |Added

 CC||jpwhit...@kde.org

--- Comment #21 from Jeremy Whiting  ---
Here it sometimes works as expected and other times will only appear if the
focus is on the laptop screen. Not on the external display. Changing which
display is "primary" doesn't matter here. when in the broken state it will only
ever appear on the laptop display.

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

[kompare] [Bug 356197] Files with other encoding than utf-8 are not displayed correctly, also encoding-option is defect

2022-02-09 Thread Jeremy Whiting

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

Jeremy Whiting  changed:

   What|Removed |Added

 CC||jpwhit...@kde.org

--- Comment #2 from Jeremy Whiting  ---
Of course. Patches are always welcome.

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

[kdevelop] [Bug 448152] Building with Xcode fails `ld: malformed 64-bit a.b.c.d.e version number: 5.7.211201`

2022-01-17 Thread Jeremy W. Murphy

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

Jeremy W. Murphy  changed:

   What|Removed |Added

 CC||jeremy.william.murphy@gmail
   ||.com

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

[kdevelop] [Bug 448245] New: Crash immediately on startup (Mac M1 Monterey)

2022-01-10 Thread Jeremy W. Murphy

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

Bug ID: 448245
   Summary: Crash immediately on startup (Mac M1 Monterey)
   Product: kdevelop
   Version: 5.6.2
  Platform: Homebrew (macOS)
OS: macOS
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: jeremy.william.mur...@gmail.com
  Target Milestone: ---

SUMMARY

Crash on startup, no window appears.

Issue on homebrew website:
https://invent.kde.org/packaging/homebrew-kde/-/issues/41

STEPS TO REPRODUCE
1.  Start application (there is only one icon in MacOS homebrew installation)

OBSERVED RESULT

Crash.

EXPECTED RESULT

Application runs.

ADDITIONAL INFORMATION

-
Translated Report (Full Report Below)
-

Process:   kdevelop [64249]
Path:  /opt/homebrew/*/kdevelop.app/Contents/MacOS/kdevelop
Identifier:org.kde.KDevelop
Version:   5.6 (5.6)
Code Type: ARM-64 (Native)
Parent Process:launchd [1]
User ID:   779951123

Date/Time: 2022-01-11 16:38:07.0242 +1100
OS Version:macOS 12.1 (21C52)
Report Version:12
Anonymous UUID:D7C1E617-3607-BDAB-65FB-96F5A6842509

Sleep/Wake UUID:   06B11828-1581-4CC8-905B-B53852FC61B3

Time Awake Since Boot: 230 seconds
Time Since Wake:   635133 seconds

System Integrity Protection: enabled

Crashed Thread:0  Dispatch queue: com.apple.main-thread

Exception Type:EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:   KERN_INVALID_ADDRESS at 0x0008
Exception Codes:   0x0001, 0x0008
Exception Note:EXC_CORPSE_NOTIFY

Termination Reason:Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process:   exc handler [64249]

VM Region Info: 0x8 is not in any region.  Bytes before following region:
4298113016
  REGION TYPESTART - END [ VSIZE] PRT/MAX
SHRMOD  REGION DETAIL
  UNUSED SPACE AT START
--->  
  __TEXT  10030-10032[  128K] r-x/r-x
SM=COW  ...acOS/kdevelop

Thread 0 Crashed::  Dispatch queue: com.apple.main-thread
0   QtDBus 0x102f9a630
QDBusAbstractInterface::callWithArgumentList(QDBus::CallMode, QString const&,
QList const&) + 52
1   QtDBus 0x102f7da50
QDBusConnectionInterface::registeredServiceNames() const + 84
2   QtDBus 0x102f7da50
QDBusConnectionInterface::registeredServiceNames() const + 84
3   kdevgdb.so 0x11731293c
KDevMI::MIDebuggerPlugin::setupDBus() + 72
4   kdevgdb.so 0x117312260
KDevMI::MIDebuggerPlugin::MIDebuggerPlugin(QString const&, QString const&,
QObject*) + 160
5   kdevgdb.so 0x1172e98bc
KDevMI::GDB::CppDebuggerPlugin::CppDebuggerPlugin(QObject*, QList
const&) + 104
6   kdevgdb.so 0x1172eafa8 QObject*
KPluginFactory::createInstance(QWidget*, QObject*, QList const&) + 60
7   libKF5CoreAddons.5.89.0.dylib  0x103109c30
KPluginFactory::create(char const*, QWidget*, QObject*, QList const&,
QString const&) + 564
8   libKDevPlatformShell.5.6.2.dylib   0x10072db90
KDevelop::PluginController::loadPluginInternal(QString const&) + 4420
9   libKDevPlatformShell.5.6.2.dylib   0x10072f370
KDevelop::PluginController::initialize() + 2856
10  libKDevPlatformShell.5.6.2.dylib   0x10073a534
KDevelop::CorePrivate::initialize(KDevelop::Core::Setup, QString const&) + 3704
11  libKDevPlatformShell.5.6.2.dylib   0x10073b1f0
KDevelop::Core::initialize(KDevelop::Core::Setup, QString const&) + 280
12  kdevelop   0x10031a404 main + 44400
13  dyld   0x1003850f4 start + 520

Thread 1:
0   libsystem_pthread.dylib0x1b9100010 start_wqthread + 0

Thread 2:
0   libsystem_pthread.dylib0x1b9100010 start_wqthread + 0

Thread 3:
0   libsystem_pthread.dylib0x1b9100010 start_wqthread + 0

Thread 4:: QDBusConnectionManager
0   libsystem_kernel.dylib 0x1b90d1ad0 poll + 8
1   QtCore 0x104d82f04
qt_safe_poll(pollfd*, unsigned int, timespec const*) + 436
2   QtCore 0x104d84724
QEventDispatcherUNIX::processEvents(QFlags) +
976
3   QtCore 0x104d21a08
QEventLoop::exec(QFlags) + 524
4   QtCore 0x104b70188 QThread::exec() +
136
5   QtDBus 0x102f7a428 0x102f74000 + 25640
6   QtCore 0x104b71120 0x104b5 +

[plasmashell] [Bug 443443] New: Plasma crashes sometimes when I try to set/change a widget, like the Memory Usage widget.

2021-10-07 Thread Jeremy

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

Bug ID: 443443
   Summary: Plasma crashes sometimes when I try to set/change a
widget, like the Memory Usage widget.
   Product: plasmashell
   Version: master
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: System Monitor
  Assignee: plasma-b...@kde.org
  Reporter: jeremytbax...@pm.me
CC: ahiems...@heimr.nl, notm...@gmail.com
  Target Milestone: 1.0

SUMMARY
Plasma crashes sometimes when I try to set a new widget, like the Memory Usage
widget.

STEPS TO REPRODUCE
1. Make a Memory Usage widget on a panel
2. If it was my computer, it has already crashed and when I try again it works.
real 2. right click the sensor and click Configure system monitor sensor... now
configure it and change it a bit, like the type of sensor from pie to
horizontal or something
3. Crash! My top panel (my only panel) disappears and Firefox acts normal until
like 5-10 seconds later when it appears back, normal. Dr Konqi appears and says
something crashed unexpectedly.

OBSERVED RESULT
Crashes and panels disappear for 5-10 seconds.

EXPECTED RESULT
Well I expect it to not crash (not sure if its my pc but plasma shouldn't be
this buggy). I like KDE and I think it's very cool and I don't actually think
its this buggy but yeah i'm not sure

SOFTWARE/OS VERSIONS
Windows: we don't do that here
macOS: nor do we do macos
Linux/KDE Plasma: Linux Kubuntu 5.11.0-37-generic
(available in About System)
KDE Plasma Version: 5.21.4
KDE Frameworks Version: 5.80.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION

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

[marble] [Bug 443376] New: urbanareas geodata polygon inconsistent rendering relative to land

2021-10-05 Thread Jeremy W. Murphy

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

Bug ID: 443376
   Summary: urbanareas geodata polygon inconsistent rendering
relative to land
   Product: marble
   Version: unspecified
  Platform: Compiled Sources
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: marble-b...@kde.org
  Reporter: jeremy.william.mur...@gmail.com
  Target Milestone: ---

SUMMARY

The Urban Areas geodata layer, specified in Atlas and Plain themes, renders
some cities above the ground layer, but some cities below it.

STEPS TO REPRODUCE
1. Use the Plain theme.
2. Zoom in and look for large cities with obviously missing polygons.


OBSERVED RESULT

Some cities do not have visible polygons for their urban area.
Some large coastal cities have their hidden polygon partially visible if it
extends out beyond the land polygon.

EXPECTED RESULT

All cities have visible polygons for their urban area, above the land polygon.

I have tested on Windows and Linux/KDE.

SOFTWARE/OS VERSIONS

Windows: 10.0.19041
Marble: 2.2.0 stable, 0.27.0 stable (installed from binary)
Qt Version: 5.8.0

Linux/KDE Plasma: Gentoo Linux
Marble: 2.2.20 (2.3 development), 21.04 (built from source)
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.2


ADDITIONAL INFORMATION

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

[plasmashell] [Bug 417852] Date in vertical panels is too big until panel is manually resized

2021-08-16 Thread Jeremy Plsek

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

Jeremy Plsek  changed:

   What|Removed |Added

 CC|jeremypl...@gmail.com   |

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

[kmymoney] [Bug 440018] Home Screen Showing Closed Accounts

2021-07-18 Thread Jeremy Whiting

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

Jeremy Whiting  changed:

   What|Removed |Added

 CC||jpwhit...@kde.org

--- Comment #1 from Jeremy Whiting  ---
Settings -> Configure KMyMoney (Or maybe apple -> Settings on mac?) -> General
Page -> Filter Tab has a "Do not show closed accounts" checkbox. Should do the
trick.

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

[kmymoney] [Bug 439819] Issue with changing credit card limits

2021-07-17 Thread Jeremy Whiting

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

Jeremy Whiting  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

--- Comment #6 from Jeremy Whiting  ---
Ok, found a solution. Using approach B. MR coming shortly.

I found the windows currency format setting. Nowhere in settings app of course,
but in Control Panel -> Clock & Region -> Change Date Time & Number Formats ->
Additional settings... -> Currency tab there's a place to select how negative
currencies should show. The way kmm gets it from setlocale and localeconv works
perfectly with that to decide how negative numbers appear on home in KMM.

https://invent.kde.org/office/kmymoney/-/merge_requests/108 <-- MR here.

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

[kmymoney] [Bug 439819] Issue with changing credit card limits

2021-07-17 Thread Jeremy Whiting

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

--- Comment #5 from Jeremy Whiting  ---
Thomas, thanks for the DebugView hint. That's a very useful tool. After a bit
of wrangling with craft on windows I think I found the problem. I'm just not
yet sure what the proper fix is. Here's what I found.

The locale settings from c++ lconv are saying for negative values use 0 :
Currency symbol and quantity surrounded by parentheses. (which equates to
eMyMoney::Money::ParensAround in KMM. That's fine all negative values on
windows have () around them, while on linux here they have - in front instead.
But because of that the AmountEditValidator marks (5000.00) as invalid and
changes it immediately to "" when loading an existing kmy file with credit
limits that are negative values.

So one of the following I guess is needed.
A) Make AmountEditValidator not derive from QDoubleValidator but instead be a
custom type that understands all the different notations in MyMoneyMoney
formatMoney
B) Only use the system eMyMoney::Money::signPosition in the html views, but not
when setting text in an AmountEdit

I can get a patch ready with either approach, just wasn't sure which made more
sense. Or maybe something completely different would be better?

In fiddling with this I also found I can't find a place to set how I want
negative values to appear in KMM on windows. Maybe it needs to be a new setting
at least on windows where the system locale's aren't editable? (Or maybe they
are editable, but I haven't yet found where?)

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

[kmymoney] [Bug 439819] Issue with changing credit card limits

2021-07-14 Thread Jeremy Whiting

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

Jeremy Whiting  changed:

   What|Removed |Added

 CC||jpwhit...@kde.org

--- Comment #3 from Jeremy Whiting  ---
This is exactly the same issue I hit. My old kmymoney file from 4.x times,
using all year with 5.0.x or 5.1.0 worked fine. Then recently installed 5.1.1
on windows and saw this same behavior. Credit card "Limits" tab doesn't show
values for cards that I have set limits for them on previous builds.

In trying to debug I added some qDebug() lines around AmountEdit, but realized
on windows those don't go anywhere since it's a gui app. So tried on linux and
linux build of kmymoney master branch doesn't have this bug somehow.

I tried installing the latest nightly for windows, but still hit the same
issue.

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

[kmymoney] [Bug 437757] Add ability to enter splits when scheduling a payment

2021-05-27 Thread Jeremy Whiting

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

Jeremy Whiting  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED

--- Comment #3 from Jeremy Whiting  ---
Awesome. Closing.

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

[kmymoney] [Bug 437757] Add ability to enter splits when scheduling a payment

2021-05-27 Thread Jeremy Whiting

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

Jeremy Whiting  changed:

   What|Removed |Added

 CC||jpwhit...@kde.org

--- Comment #1 from Jeremy Whiting  ---
I think that's already possible. At least I'm able to here on a 6 month old
build by clicking the button to the right of the dropdown "Transfer to:" Just
to the left of "Next due date:" label. Clicking that opens the split editor and
allows adding whatever splits are needed.

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

[gwenview] [Bug 436168] Segfault when optimized SVG file created in Inkscape is loaded either directly or in folder view

2021-04-25 Thread Jeremy Nuttall

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

Jeremy Nuttall  changed:

   What|Removed |Added

 CC||jer...@jeremy-nuttall.com

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

[gwenview] [Bug 436168] Segfault when optimized SVG file created in Inkscape is loaded either directly or in folder view

2021-04-25 Thread Jeremy Nuttall

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

--- Comment #1 from Jeremy Nuttall  ---
Power cycling has no effect.

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

[gwenview] [Bug 436168] New: Segfault when optimized SVG file created in Inkscape is loaded either directly or in folder view

2021-04-25 Thread Jeremy Nuttall

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

Bug ID: 436168
   Summary: Segfault when optimized SVG file created in Inkscape
is loaded either directly or in folder view
   Product: gwenview
   Version: 21.04.0
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: jer...@jeremy-nuttall.com
  Target Milestone: ---

Created attachment 137906
  --> https://bugs.kde.org/attachment.cgi?id=137906=edit
svg

SUMMARY


STEPS TO REPRODUCE
1. Download SVG data from attachment
2. Navigate to save directory in gwenview or open file directly

OBSERVED RESULT
segfault


EXPECTED RESULT
SVG viewing


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch 5.11.16-arch1-1 x86_64
KDE Plasma Version: 5.21.4-1
KDE Frameworks Version: 5.81.0-1
Qt Version: 5.15.2+kde+r180-1

ADDITIONAL INFORMATION
Will power cycle later to be sure it's not an OS-side problem

-- Backtrace:
Application: Gwenview (gwenview), signal: Segmentation fault

[KCrash Handler]
#4  0x7f62d8479a88 in fffi4u4 () from /usr/lib/libcfitsio.so.9
#5  0x7f62d847b1a5 in ?? () from /usr/lib/libcfitsio.so.9
#6  0x7f62d847b76b in ffgpvuj () from /usr/lib/libcfitsio.so.9
#7  0x7f62d84517d1 in ffgpv () from /usr/lib/libcfitsio.so.9
#8  0x7f62db00876a in ?? () from /usr/lib/libgwenviewlib.so.5
#9  0x7f62daffe6c9 in ?? () from /usr/lib/libgwenviewlib.so.5
#10 0x7f62d9b2370c in ?? () from /usr/lib/libQt5Gui.so.5
#11 0x7f62d9b24be4 in ?? () from /usr/lib/libQt5Gui.so.5
#12 0x7f62d9b2579c in QImageReader::canRead() const () from
/usr/lib/libQt5Gui.so.5
#13 0x7f62dafda4f9 in ?? () from /usr/lib/libgwenviewlib.so.5
#14 0x7f62dafdae07 in ?? () from /usr/lib/libgwenviewlib.so.5
#15 0x7f62d931707f in ?? () from /usr/lib/libQt5Core.so.5
#16 0x7f62d76fe299 in start_thread () from /usr/lib/libpthread.so.0
#17 0x7f62d8f9e053 in clone () from /usr/lib/libc.so.6

Thread 9 (Thread 0x7f6287fff640 (LWP 359770) "Gwenview::Thumb"):
#1  0x7f62d7704260 in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#2  0x7f62d931d244 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from
/usr/lib/libQt5Core.so.5
#3  0x7f62dafdaf62 in ?? () from /usr/lib/libgwenviewlib.so.5
#4  0x7f62d931707f in ?? () from /usr/lib/libQt5Core.so.5
#5  0x7f62d76fe299 in start_thread () from /usr/lib/libpthread.so.0
#6  0x7f62d8f9e053 in clone () from /usr/lib/libc.so.6

Thread 8 (Thread 0x7f62a65a0640 (LWP 359757) "gwenvie:disk$3"):
#1  0x7f62d7704260 in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#2  0x7f62b9a65a1c in ?? () from /usr/lib/dri/iris_dri.so
#3  0x7f62b9a5f668 in ?? () from /usr/lib/dri/iris_dri.so
#4  0x7f62d76fe299 in start_thread () from /usr/lib/libpthread.so.0
#5  0x7f62d8f9e053 in clone () from /usr/lib/libc.so.6

Thread 7 (Thread 0x7f62b8910640 (LWP 359756) "gwenvie:disk$2"):
#1  0x7f62d7704260 in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#2  0x7f62b9a65a1c in ?? () from /usr/lib/dri/iris_dri.so
#3  0x7f62b9a5f668 in ?? () from /usr/lib/dri/iris_dri.so
#4  0x7f62d76fe299 in start_thread () from /usr/lib/libpthread.so.0
#5  0x7f62d8f9e053 in clone () from /usr/lib/libc.so.6

Thread 6 (Thread 0x7f62b9111640 (LWP 359755) "gwenvie:disk$1"):
#1  0x7f62d7704260 in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#2  0x7f62b9a65a1c in ?? () from /usr/lib/dri/iris_dri.so
#3  0x7f62b9a5f668 in ?? () from /usr/lib/dri/iris_dri.so
#4  0x7f62d76fe299 in start_thread () from /usr/lib/libpthread.so.0
#5  0x7f62d8f9e053 in clone () from /usr/lib/libc.so.6

Thread 5 (Thread 0x7f62b9912640 (LWP 359754) "gwenvie:disk$0"):
#1  0x7f62d7704260 in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#2  0x7f62b9a65a1c in ?? () from /usr/lib/dri/iris_dri.so
#3  0x7f62b9a5f668 in ?? () from /usr/lib/dri/iris_dri.so
#4  0x7f62d76fe299 in start_thread () from /usr/lib/libpthread.so.0
#5  0x7f62d8f9e053 in clone () from /usr/lib/libc.so.6

Thread 4 (Thread 0x7f62c9d80640 (LWP 359752) "gwenview"):
#1  0x7f62d418d524 in ?? () from /usr/lib/libusbmuxd-2.0.so.6
#2  0x7f62d418e8a9 in ?? () from /usr/lib/libusbmuxd-2.0.so.6
#3  0x7f62d76fe299 in start_thread () from /usr/lib/libpthread.so.0
#4  0x7f62d8f9e053 in clone () from /usr/lib/libc.so.6

Thread 3 (Thread 0x7f62d2257640 (LWP 359750) "QDBusConnection"):
#1  0x7f62d6e2545d in g_main_context_check () from
/usr/lib/libglib-2.0.so.0
#2  0x7f62d6e78a8b in ?? () from /usr/lib/libglib-2.0.so.0
#3  0x7f62d6e22781 in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#4  0x7f62d95581ac in
QEvent

[krita] [Bug 423204] New: Crash in KoShape::parent

2020-06-18 Thread Jeremy Rose

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

Bug ID: 423204
   Summary: Crash in KoShape::parent
   Product: krita
   Version: 4.2.8
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: krita-bugs-n...@kde.org
  Reporter: norna...@nornagon.net
  Target Milestone: ---

Created attachment 129509
  --> https://bugs.kde.org/attachment.cgi?id=129509=edit
Full crash report

SUMMARY
Null dereference in KoShape::parent

STEPS TO REPRODUCE
I don't have reliable repro steps, but this happened when I toggled a layer to
be invisible.

OBSERVED RESULT

Crash with SIGSEGV at address 0x0090

Truncated stack trace (full report attached):
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libkritaflake.18.dylib  0x00011166b598 KoShape::parent()
const + 8
1   libkritaui.18.dylib 0x00010fc3dbae
KisNodeShape::editabilityChanged() + 478
2   org.qt-project.QtCore   0x000113383112
QObject::event(QEvent*) + 770
3   org.qt-project.QtWidgets0x00011217c110
QApplicationPrivate::notify_helper(QObject*, QEvent*) + 272
4   org.qt-project.QtWidgets0x00011217d4c5
QApplication::notify(QObject*, QEvent*) + 581
5   libkritaui.18.dylib 0x00010ff18ada
KisApplication::notify(QObject*, QEvent*) + 26


SOFTWARE/OS VERSIONS
macOS: 10.14.6

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

[krita] [Bug 422982] Segfault in KisNodeProgressProxy::setRange

2020-06-14 Thread Jeremy Rose

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

--- Comment #2 from Jeremy Rose  ---
Fantastic, thanks! Sorry for the noise, I searched for the top of the stack
trace and didn't find anything. Glad to hear it's fixed :)


On Sun, Jun 14, 2020 at 10:33 AM Boudewijn Rempt 
wrote:

> https://bugs.kde.org/show_bug.cgi?id=422982
>
> Boudewijn Rempt  changed:
>
>What|Removed |Added
>
> 
>  CC||b...@valdyas.org
>  Status|REPORTED|RESOLVED
>  Resolution|--- |FIXED
>
> --- Comment #1 from Boudewijn Rempt  ---
> Ah, this was fixed for 4.3.0 -- second beta now available, final release
> this
> week.
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[krita] [Bug 422982] New: Segfault in KisNodeProgressProxy::setRange

2020-06-14 Thread Jeremy Rose

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

Bug ID: 422982
   Summary: Segfault in KisNodeProgressProxy::setRange
   Product: krita
   Version: 4.2.8
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: krita-bugs-n...@kde.org
  Reporter: norna...@nornagon.net
  Target Milestone: ---

Created attachment 129359
  --> https://bugs.kde.org/attachment.cgi?id=129359=edit
Full crash report

SUMMARY
Program crashed while painting.

STEPS TO REPRODUCE
I can't reproduce this, but in case one of these seems relevant: I was messing
with filter layers on a clone layer, outline selection and clearing (w/
Delete), while undoing.


SOFTWARE/OS VERSIONS
macOS: 10.14.6

ADDITIONAL INFORMATION

Here's the stack trace (the full crash report is attached):

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libkritaimage.18.dylib  0x00010ff43a3a
KisNodeProgressProxy::setRange(int, int) + 42
1   libkritawidgetutils.18.dylib0x0001109310e8
KoProgressUpdater::updateUi() + 712
2   org.qt-project.QtCore   0x00011213ef55
QMetaObject::activate(QObject*, int, int, void**) + 1765
3   org.qt-project.QtCore   0x000112146bf2
QTimer::timerEvent(QTimerEvent*) + 98
4   org.qt-project.QtCore   0x000112137e78
QObject::event(QEvent*) + 104
5   org.qt-project.QtWidgets0x000110f2c110
QApplicationPrivate::notify_helper(QObject*, QEvent*) + 272
6   org.qt-project.QtWidgets0x000110f2d4c5
QApplication::notify(QObject*, QEvent*) + 581
7   libkritaui.18.dylib 0x00010ecc9ada
KisApplication::notify(QObject*, QEvent*) + 26
8   org.qt-project.QtCore   0x00011210f384
QCoreApplication::notifyInternal2(QObject*, QEvent*) + 212
9   org.qt-project.QtCore   0x000112166bf2
QTimerInfoList::activateTimers() + 930
10  libqcocoa.dylib 0x00011496b062 0x114937000 + 213090
11  com.apple.CoreFoundation0x7fff4253bd17
__CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
12  com.apple.CoreFoundation0x7fff4253bcbd __CFRunLoopDoSource0
+ 108
13  com.apple.CoreFoundation0x7fff4251f6d3
__CFRunLoopDoSources0 + 283
14  com.apple.CoreFoundation0x7fff4251ec45 __CFRunLoopRun +
1189
15  com.apple.CoreFoundation0x7fff4251e54e CFRunLoopRunSpecific
+ 455
16  com.apple.HIToolbox 0x7fff4177d1ab
RunCurrentEventLoopInMode + 292
17  com.apple.HIToolbox 0x7fff4177cded
ReceiveNextEventCommon + 355
18  com.apple.HIToolbox 0x7fff4177cc76
_BlockUntilNextEventMatchingListInModeWithFilter + 64
19  com.apple.AppKit0x7fff3fb1477d _DPSNextEvent + 1135
20  com.apple.AppKit0x7fff3fb1346b
-[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:]
+ 1361
21  com.apple.AppKit0x7fff3fb0d588 -[NSApplication run]
+ 699
22  libqcocoa.dylib 0x00011496be68 0x114937000 + 216680
23  org.qt-project.QtCore   0x00011210aacf
QEventLoop::exec(QFlags) + 431
24  org.qt-project.QtCore   0x00011210f9d2
QCoreApplication::exec() + 130
25  org.krita   0x00010d9924e6 main + 10806
26  libdyld.dylib   0x7fff6e4873d5 start + 1

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

[marble] [Bug 411140] Example MarbleWidget will not exit when closed

2020-06-09 Thread Jeremy Harding

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

--- Comment #2 from Jeremy Harding  ---
Can be fixed by adding 

m_mapWidget->setAttribute(Qt::WA_DeleteOnClose);

to the example.

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

[xdg-desktop-portal-kde] [Bug 422508] New: Portal File Dialog is launched behind main app GUI

2020-06-05 Thread Jeremy Palmer

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

Bug ID: 422508
   Summary: Portal File Dialog is launched behind main app GUI
   Product: xdg-desktop-portal-kde
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jgrul...@redhat.com
  Reporter: jpal...@linz.govt.nz
  Target Milestone: ---

SUMMARY

When opening a system file dialog in a flatpak QT application (QGIS) the dialog
is launched behind the main app window. This has been observed on Ubuntu 18.04. 

See original issue https://github.com/flathub/org.qgis.qgis/issues/11

STEPS TO REPRODUCE
1. sudo add-apt-repository ppa:alexlarsson/flatpak
2. sudo apt update && sudo apt install flatpak
3. flatpak install --from 
https://flathub.org/repo/appstream/org.qgis.qgis.flatpakref
4. flatpak run org.qgis.qgis
5. In QGIS app menu select Project->Open

OBSERVED RESULT

Notification message is raised 'Portal "Choose a QGIS Project File to Open" is
ready', but the file open dialog is launch in background in separate window. 


EXPECTED RESULT

SOFTWARE/OS VERSIONS
Linux: Ubuntu 18.04.4 LTS
Qt Version: 5.14.2

ADDITIONAL INFORMATION

using ppa:alexlarsson/flatpak

$ sudo apt-get install xdg-desktop-portal xdg-desktop-portal-gtk
xdg-desktop-portal-kde flatpak
Reading package lists... Done
Building dependency tree   
Reading state information... Done
xdg-desktop-portal-kde is already the newest version (5.12.7-0ubuntu0.1).
flatpak is already the newest version (1.7.2-flatpak2~bionic).
xdg-desktop-portal is already the newest version (1.7.1-flatpak2~bionic).
xdg-desktop-portal-gtk is already the newest version (1.7.1-flatpak1~bionic).
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.

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

[korganizer] [Bug 421215] editing category colors crashes korganizer

2020-05-30 Thread Jeremy Potter

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

--- Comment #3 from Jeremy Potter  ---
Application: korganizer (5.14.1 (20.04.0))

Qt Version: 5.13.2
Frameworks Version: 5.70.0
Operating System: Linux 5.6.13-153.current x86_64
Windowing system: X11
Distribution: Solus 4.1 Fortitude

-- Information about the crash:
Same as everybody else.

-- Backtrace:
Application: KOrganizer (korganizer), signal: Segmentation fault
[KCrash Handler]
#4  0x7f794830b8cf in ?? () from /usr/lib/libQt5Core.so.5
#5  0x7f794830655d in QAbstractItemModelPrivate::itemsMoved(QModelIndex
const&, int, int, QModelIndex const&, int, Qt::Orientation) () from
/usr/lib/libQt5Core.so.5
#6  0x7f7948308b18 in QAbstractItemModel::endMoveRows() () from
/usr/lib/libQt5Core.so.5
#7  0x7f794724fafa in ?? () from /usr/lib/libKF5AkonadiCore.so.5
#8  0x7f794724cdb3 in ?? () from /usr/lib/libKF5AkonadiCore.so.5
#9  0x7f7948387168 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/libQt5Core.so.5
#10 0x7f7947155e25 in Akonadi::Monitor::tagChanged(Akonadi::Tag const&) ()
from /usr/lib/libKF5AkonadiCore.so.5
#11 0x7f794716204f in
Akonadi::MonitorPrivate::emitTagNotification(Akonadi::Protocol::TagChangeNotification
const&, Akonadi::Tag const&) () from /usr/lib/libKF5AkonadiCore.so.5
#12 0x7f79471655de in
Akonadi::MonitorPrivate::emitNotification(QSharedPointer
const&) () from /usr/lib/libKF5AkonadiCore.so.5
#13 0x7f7947167a0c in Akonadi::MonitorPrivate::dispatchNotifications() ()
from /usr/lib/libKF5AkonadiCore.so.5
#14 0x7f7947167bb5 in
Akonadi::MonitorPrivate::slotNotify(QSharedPointer
const&) () from /usr/lib/libKF5AkonadiCore.so.5
#15 0x7f794716804b in Akonadi::MonitorPrivate::handleCommands() () from
/usr/lib/libKF5AkonadiCore.so.5
#16 0x7f7947156e23 in ?? () from /usr/lib/libKF5AkonadiCore.so.5
#17 0x7f7948387b7a in QObject::event(QEvent*) () from
/usr/lib/libQt5Core.so.5
#18 0x7f7948dc0382 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQt5Widgets.so.5
#19 0x7f7948dc98c0 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#20 0x7f794835c202 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/libQt5Core.so.5
#21 0x7f794835ee98 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib/libQt5Core.so.5
#22 0x7f79483b2fe3 in ?? () from /usr/lib/libQt5Core.so.5
#23 0x7f7943c92e3d in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#24 0x7f7943c930c0 in ?? () from /usr/lib/libglib-2.0.so.0
#25 0x7f7943c9314f in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#26 0x7f79483b2621 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#27 0x7f794835ad6b in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#28 0x7f79483629d2 in QCoreApplication::exec() () from
/usr/lib/libQt5Core.so.5
#29 0x004091d7 in ?? ()
#30 0x7f7947ce00d3 in __libc_start_main () from /usr/lib/haswell/libc.so.6
#31 0x0040935e in ?? ()
[Inferior 1 (process 57990) detached]

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

[korganizer] [Bug 421215] editing category colors crashes korganizer

2020-05-30 Thread Jeremy Potter

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

Jeremy Potter  changed:

   What|Removed |Added

 CC||k...@stormdesign.us

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

[plasmashell] [Bug 349004] UI for activity switching provides poor feedback

2020-05-23 Thread Jeremy Potter

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

--- Comment #5 from Jeremy Potter  ---
IMO the activity switcher should be shown in all cases for a brief amount of
time just so that the user knows what activity they've switched to. Switching
activities is not something you do often so when you do switch activities it
would be nice to have some kind of feedback.

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

[plasmashell] [Bug 349004] UI for activity switching provides poor feedback

2020-05-23 Thread Jeremy Potter

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

Jeremy Potter  changed:

   What|Removed |Added

 CC||k...@stormdesign.us

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

[okular] [Bug 421670] Okular hangs when printing pages specified in "Print range -> Pages"

2020-05-17 Thread Jeremy Lorelli

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

--- Comment #3 from Jeremy Lorelli  ---
Thanks for the replies :)

I just tested it and, yes, it does max out CPU usage and eventually adds the
job to the print queue after about 15 minutes. Wasn't able to get it to
actually print, but that might just be an issue with my printer.

When testing a small document (~30 pages), I was able to print individual pages
using the "Pages: " input. When using the "print to pdf" option though, the
entire PDF is saved.

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

[okular] [Bug 421670] Okular hangs when printing pages specified in "Print range -> Pages"

2020-05-17 Thread Jeremy Lorelli

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

Jeremy Lorelli  changed:

   What|Removed |Added

Summary|Okular hangs when printing  |Okular hangs when printing
   |pages specified in the  |pages specified in "Print
   |"Print range -> Pages"  |range -> Pages"
   |input box   |

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

[okular] [Bug 421670] New: Okular hangs when printing pages specified in the "Print range -> Pages" input box

2020-05-17 Thread Jeremy Lorelli

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

Bug ID: 421670
   Summary: Okular hangs when printing pages specified in the
"Print range -> Pages" input box
   Product: okular
   Version: 1.10.1
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: printing
  Assignee: okular-de...@kde.org
  Reporter: jeremy.lorelli.1...@gmail.com
  Target Milestone: ---

Created attachment 128537
  --> https://bugs.kde.org/attachment.cgi?id=128537=edit
Example of input that causes Okular to hang.

SUMMARY
Okular hangs when printing a specific page specified using the Pages box in the
Print dialog.

STEPS TO REPRODUCE
1. File->Print
2. Click Options, then Copies tab
3. Enter pages in the box named "Pages" in the "Print Range" section
4. Click Print

OBSERVED RESULT
Okular hangs and needs to be killed.

EXPECTED RESULT
Okular should print the pages specified in there. I've tested the other Print
ranges and they all seem to work fine. 

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.6.7-1-MANJARO
KDE Plasma Version: 5.18.4
KDE Frameworks Version: 5.69.0
Qt Version: 5.14.2

ADDITIONAL INFORMATION
I'm not sure when this issue first appeared, as it's the first time I've tried
to print individual pages like that.

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

[kdevelop] [Bug 419520] Build tool view does not parse warnings and errors using clang-cl (on Windows)

2020-04-01 Thread Jeremy W. Murphy

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

--- Comment #1 from Jeremy W. Murphy  ---
Also, link errors, e.g.:

NodeValueChangeEventLogger.obj : error LNK2019: unresolved external symbol
"private: static struct NodeValueChangeEventLoggerElement::NodeValueEvents
const * const NodeValueChangeEventLoggerElement::NODES_VALUE_EVENTS"
(?NODES_VALUE_EVENTS@NodeValueChangeEventLoggerElement@@0QBUNodeValueEvents@1@B)
referenced in function "private: void __thiscall
NodeValueChangeEventLoggerElement::InitialiseNodesEvents(void)"
(?InitialiseNodesEvents@NodeValueChangeEventLoggerElement@@AAEXXZ)

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

[kdevelop] [Bug 419520] New: Build tool view does not parse warnings and errors using clang-cl (on Windows)

2020-04-01 Thread Jeremy W. Murphy

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

Bug ID: 419520
   Summary: Build tool view does not parse warnings and errors
using clang-cl (on Windows)
   Product: kdevelop
   Version: 5.5.0
  Platform: MS Windows
OS: MS Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Output Views
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: jeremy.william.mur...@gmail.com
  Target Milestone: ---

SUMMARY

Warnings and errors are not highlighted orange and red respectively, although
the preceding "In file..." lines do get highlighted blue.

An example warning line is:

Application/Infrastructure/DataManager/Include/EnumeratedItem.hpp(15,10):
warning: non-portable path to file '"Application.h"'; specified path differs in
case from file name on disk [-Wnonportable-include-path]

STEPS TO REPRODUCE
1. Use clang-cl on Windows
2. Build some code that generates warnings/errors

OBSERVED RESULT

Warnings and errors are not highlighted.

EXPECTED RESULT

Warnings and errors are highlighted.

SOFTWARE/OS VERSIONS
Windows: Server 2016 Standard
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 5.67.0
Qt Version: 

ADDITIONAL INFORMATION

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

[khangman] [Bug 392493] Default language is not American English when running on Ubuntu 18.04 Bionic Beaver

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

Jeremy Whiting  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED
  Latest Commit||https://commits.kde.org/kha
   ||ngman/b9eb2808a6079de6f6f78
   ||43d1c267f13da23e4d3

--- Comment #1 from Jeremy Whiting  ---
Git commit b9eb2808a6079de6f6f7843d1c267f13da23e4d3 by Jeremy Whiting.
Committed on 03/03/2020 at 02:17.
Pushed by whiting into branch 'master'.

Fix KHangMan default language.
Somehow default language was set to "userLanguage" which was supposed
to be based on locale, but isn't when compiled by kcfg, it's a static
string, so just set the default back to en to be back to previous
behavior.
TODO: Actually use the user's locale to set the default language.

M  +4-4src/khangman.kcfg

https://commits.kde.org/khangman/b9eb2808a6079de6f6f7843d1c267f13da23e4d3

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

[khangman] [Bug 362193] Problems in Localization with German Umlauts ('ä', 'ö', and 'ü') and 'ß'

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

Jeremy Whiting  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/kha
   ||ngman/c757fb327dd1841d2f079
   ||3851bb86ff4ab695fc4
 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #2 from Jeremy Whiting  ---
Git commit c757fb327dd1841d2f0793851bb86ff4ab695fc4 by Jeremy Whiting.
Committed on 03/03/2020 at 02:01.
Pushed by whiting into branch 'master'.

Convert all letters to upper case to compare.
Since special characters for each language in khangman language.txt
files are lower case, but we show upper case in the gui special
characters were not properly getting marked as disabled or being
marked green or red when clicked. To fix always compare
upper case version of letters.
Note: if I changed letter button letter property to modelData.toUpperCase
some German characters were shown incorrectly in the gui, so show the
modelData with capitalization font, but compare toUpperCase() behind
the scenes.

M  +3-2src/qml/GamePage.qml

https://commits.kde.org/khangman/c757fb327dd1841d2f0793851bb86ff4ab695fc4

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

[khangman] [Bug 344834] installs khangman-harmattan icons even when not building harmattan version

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

Jeremy Whiting  changed:

   What|Removed |Added

 CC||jpwhit...@kde.org
 Status|REPORTED|NEEDSINFO
 Resolution|--- |FIXED

--- Comment #1 from Jeremy Whiting  ---
Harald, I don't see any harmattan icons in the git repository anymore. Is this
still an issue? or was it accidentally fixed when the qml gui was introduced
and the icons got cleaned up and simplified?

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

[khangman] [Bug 348735] Game crashes immediately after launch.

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

Jeremy Whiting  changed:

   What|Removed |Added

 CC||jpwhit...@kde.org
 Resolution|--- |WORKSFORME
 Status|REPORTED|RESOLVED

--- Comment #2 from Jeremy Whiting  ---
Closing for lack of feedback, reopen if you still hit it and can provide a
stack trace from the crash report window.

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

[khangman] [Bug 386855] Cannot change theme when on pause

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

Jeremy Whiting  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
  Latest Commit||https://commits.kde.org/kha
   ||ngman/24883a2dae9d44186b8cf
   ||b7b23b28b1e5b1987b3
 Resolution|--- |FIXED

--- Comment #1 from Jeremy Whiting  ---
Git commit 24883a2dae9d44186b8cfb7b23b28b1e5b1987b3 by Jeremy Whiting.
Committed on 03/03/2020 at 01:29.
Pushed by whiting into branch 'master'.

Move theme selection button from bottom to top toolbar.
Move the theme selection button to the top toolbar so it is
usable while the game is paused or before starting.

M  +11   -11   src/qml/GamePage.qml

https://commits.kde.org/khangman/24883a2dae9d44186b8cfb7b23b28b1e5b1987b3

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

[khangman] [Bug 362256] Change theme name "Notes" to "Notes theme"