[korganizer] [Bug 398173] month view font can be resized, but items are still small
https://bugs.kde.org/show_bug.cgi?id=398173 Alan Porter changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Alan Porter --- I don't even use korganizer any more... but trying it out today, it looks a little better than what's in the screenshots I attached back in 2018, but still a little squooshed if you make the font size a little on the large size. If no one else has complained, I can't see much reason in digging around to "fix" this one any more than it's already "fixed". Thanks for checking back in. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 450410] when you turn on the next track, the volume is reset to maximum sound.
https://bugs.kde.org/show_bug.cgi?id=450410 --- Comment #7 from Porter --- (In reply to Nate Graham from comment #6) > Are we talking about the *system* volume resetting when the track changes, > or the volume that's set within Elisa itself? > > Cannot reproduce with PipeWire and WirePlumber on Fedora 35. The volume set within Elisa. View the attachments for reference. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 450410] when you turn on the next track, the volume is reset to maximum sound.
https://bugs.kde.org/show_bug.cgi?id=450410 --- Comment #3 from Porter --- (In reply to Porter from comment #2) > (In reply to Porter from comment #1) > > Created attachment 147153 [details] > > Screen capture > > > > I can reproduce this. > > > > SOFTWARE/OS VERSIONS > > KDE Plasma Version: 5.24.2 > > KDE Frameworks Version: 5.91.0 > > Qt Version: 5.15.2 > > I've found a temporary fix to set the volume without the volume changing to > maximum when a new track is played, but if you change the volume without > reopening Elisa, you'll experience this bug. > > TEMPORARY FIX > Open Elisa, change the volume, reopen Elisa, the volume will remain as that > volume when a new track is played. Actually, this temporary fix results in another bug. When a new track is played, it plays at maximum volume, but the volume slider doesn't update to maximum. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 450410] when you turn on the next track, the volume is reset to maximum sound.
https://bugs.kde.org/show_bug.cgi?id=450410 Porter changed: What|Removed |Added CC||t4h454445n...@protonmail.co ||m --- Comment #2 from Porter --- (In reply to Porter from comment #1) > Created attachment 147153 [details] > Screen capture > > I can reproduce this. > > SOFTWARE/OS VERSIONS > KDE Plasma Version: 5.24.2 > KDE Frameworks Version: 5.91.0 > Qt Version: 5.15.2 I've found a temporary fix to set the volume without the volume changing to maximum when a new track is played, but if you change the volume without reopening Elisa, you'll experience this bug. TEMPORARY FIX Open Elisa, change the volume, reopen Elisa, the volume will remain as that volume when a new track is played. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 450410] when you turn on the next track, the volume is reset to maximum sound.
https://bugs.kde.org/show_bug.cgi?id=450410 Porter changed: What|Removed |Added CC|t4h454445n...@protonmail.co | |m | -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 450410] when you turn on the next track, the volume is reset to maximum sound.
https://bugs.kde.org/show_bug.cgi?id=450410 Porter changed: What|Removed |Added CC||t4h454445n...@protonmail.co ||m --- Comment #1 from Porter --- Created attachment 147153 --> https://bugs.kde.org/attachment.cgi?id=147153=edit Screen capture I can reproduce this. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[bomber] [Bug 443627] New: Will Cash App Refund Money If Scammed? What are tips for solutions?
https://bugs.kde.org/show_bug.cgi?id=443627 Bug ID: 443627 Summary: Will Cash App Refund Money If Scammed? What are tips for solutions? Product: bomber Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: harryporter2...@gmail.com CC: kde-games-b...@kde.org Target Milestone: --- People using the Cash app are struggling with queries such as Will Cash App Refund Money If Scammed. They should be attentive if any unknown Element approaches them and instructs them to invest in profits. Cash app never Suggests their users for such aspect, so before, taking any action, they must Once contact the cash app service team to find out the facts. https://www.contactmail-support.com/blog/will-cash-app-refund-money-if-scammed/ -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 398173] month view font can be resized, but items are still small
https://bugs.kde.org/show_bug.cgi?id=398173 --- Comment #1 from Alan Porter --- Created attachment 114751 --> https://bugs.kde.org/attachment.cgi?id=114751=edit month view with larger font, ovals do not resize to fit text -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 398173] New: month view font can be resized, but items are still small
https://bugs.kde.org/show_bug.cgi?id=398173 Bug ID: 398173 Summary: month view font can be resized, but items are still small Product: korganizer Version: 5.7.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: monthview Assignee: kdepim-b...@kde.org Reporter: kde-bugs-2...@kr4jb.net Target Milestone: --- Created attachment 114750 --> https://bugs.kde.org/attachment.cgi?id=114750=edit month view with very small font, ovals sized OK Korganizer's month view shows items within a day stacked up in little rounded rectangles or "ovals". I'm pretty sure you call them something else. The settings screen allows you to change the font size used for events listed in these ovals, but the ovals themselves do not resize to accommodate the fonts. In order for the text within the ovals to not be clipped or crowded, I have to use a tiny font, like 8pt or 9pt. But I'd like to use something more like 16pt. If I try to use a 16pt font, the display is all crowded. The ovals themselves need to be thicker if the font size is larger. Or perhaps there should be a setting to change the size of the ovals. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 380822] New: Sporadic crashes when drag a file via breadcrumb navigation
https://bugs.kde.org/show_bug.cgi?id=380822 Bug ID: 380822 Summary: Sporadic crashes when drag a file via breadcrumb navigation Product: dolphin Version: 16.08.3 Platform: Debian stable OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: porterni...@gmx.de Target Milestone: --- Application: dolphin (16.08.3) Qt Version: 5.7.1 Frameworks Version: 5.28.0 Operating System: Linux 4.9.0-3-amd64 x86_64 Distribution: Debian GNU/Linux 9.0 (stretch) -- Information about the crash: - What I was doing when the application crashed: When sorting files, I often move one or more to a parent or sibling directory using the breadcrumb navigation (dropdown arrows for sibling directories). In some cases, Dolphin crashes, making me lose my session and interrupting ongoing file move operations.. The crash can be reproduced sometimes. -- Backtrace: Application: Dolphin (dolphin), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6a2aa03940 (LWP 1620))] Thread 5 (Thread 0x7f6a031c1700 (LWP 1738)): #0 0x7fffd8301b12 in clock_gettime () #1 0x7f6a2a2347d6 in clock_gettime () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x7f6a249b1091 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f6a24b2dce9 in QTimerInfoList::updateCurrentTime() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f6a24b2e295 in QTimerInfoList::timerWait(timespec&) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f6a24b2f63e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f6a1f0aaedd in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f6a1f0ab91b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7f6a1f0abb0c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7f6a24b3006b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f6a24ad99ca in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f6a249070f3 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f6a2490bda8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f6a29d25494 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #14 0x7f6a2a22793f in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 4 (Thread 0x7f6a04d5a700 (LWP 1695)): #0 0x7f6a29d2b15f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f6a0cfb975b in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #2 0x7f6a0cfb9487 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #3 0x7f6a29d25494 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #4 0x7f6a2a22793f in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 3 (Thread 0x7f6a0eba9700 (LWP 1629)): #0 0x7f6a2a21a55d in read () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f6a1f0efd40 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f6a1f0ab4be in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6a1f0ab994 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f6a1f0abb0c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f6a24b3006b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f6a24ad99ca in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f6a249070f3 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f6a2aaf26d5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #9 0x7f6a2490bda8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f6a29d25494 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #11 0x7f6a2a22793f in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 2 (Thread 0x7f6a14814700 (LWP 1627)): #0 0x7f6a2a21e4ed in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f6a1e7e7150 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f6a1e7e8ee9 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f6a1653db69 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f6a2490bda8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f6a29d25494 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #6 0x7f6a2a22793f in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 1 (Thread 0x7f6a2aa03940 (LWP 1620)): [KCrash Handler] #6 0x7f6a2a171fcf in raise () from /lib/x86_64-linux-gnu/libc.so.6 #7 0x7f6a2a1733fa in abort () from
[krita] [Bug 367625] New: Krita crashed after clicking new file
https://bugs.kde.org/show_bug.cgi?id=367625 Bug ID: 367625 Summary: Krita crashed after clicking new file Product: krita Version: 2.9.7 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: dertpor...@gmail.com Application: krita (2.9.7) KDE Platform Version: 4.14.16 Qt Version: 4.8.7 Operating System: Linux 4.4.0-21-lowlatency x86_64 Distribution: Ubuntu 16.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: Opened Krita, then clicked new, after that went into setting to customize the application but didn't save the settings because of crash -- Backtrace: Application: Krita (krita), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2cb3897900 (LWP 23132))] Thread 5 (Thread 0x7f2c737fe700 (LWP 23280)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225 #1 0x7f2cb160b384 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #2 0x7f2cb15fdfe7 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #3 0x7f2cb160ae3c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #4 0x7f2cab8786fa in start_thread (arg=0x7f2c737fe700) at pthread_create.c:333 #5 0x7f2cb0d35b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7f2c6327f700 (LWP 23279)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225 #1 0x7f2cb160b384 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #2 0x7f2cb15fdfe7 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #3 0x7f2cb160ae3c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #4 0x7f2cab8786fa in start_thread (arg=0x7f2c6327f700) at pthread_create.c:333 #5 0x7f2cb0d35b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f2c8c5ec700 (LWP 23168)): #0 0x7f2cb0d29e8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f2cab39139c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f2cab3914ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f2cb174b2ce in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #4 0x7f2cb171918f in QEventLoop::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #5 0x7f2cb17194f5 in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x7f2cb1608549 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x7f2cb16f9223 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #8 0x7f2cb160ae3c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #9 0x7f2cab8786fa in start_thread (arg=0x7f2c8c5ec700) at pthread_create.c:333 #10 0x7f2cb0d35b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f2c73fff700 (LWP 23167)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f2cb160b3a6 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #2 0x7f2cb26499ac in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #3 0x7f2cb160ae3c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #4 0x7f2cab8786fa in start_thread (arg=0x7f2c73fff700) at pthread_create.c:333 #5 0x7f2cb0d35b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f2cb3897900 (LWP 23132)): [KCrash Handler] #6 0x7f2cb0c64418 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 #7 0x7f2cb0c6601a in __GI_abort () at abort.c:89 #8 0x7f2cb15fff15 in qt_message_output(QtMsgType, char const*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #9 0x7f2cb1600371 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #10 0x7f2cb1600c91 in qFatal(char const*, ...) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #11 0x7f2cadd985f7 in KoToolManager::instance() () from /usr/lib/libflake.so.14 #12 0x7f2cb2f72728 in KisNodeShape::~KisNodeShape() () from /usr/lib/libkritaui.so.14 #13 0x7f2cb2f72859 in KisNodeShape::~KisNodeShape() () from /usr/lib/libkritaui.so.14 #14 0x7f2cb2f724bb in KisNodeShapesGraph::removeNode(KisSharedPtr) () from /usr/lib/libkritaui.so.14 #15 0x7f2cb2f73443 in KisShapeController::~KisShapeController() () from /usr/lib/libkritaui.so.14 #16 0x7f2cb2f73559 in KisShapeController::~KisShapeController() () from /usr/lib/libkritaui.so.14 #17 0x7f2cb3203ed6 in
