[dolphin] [Bug 487002] Text disappears
https://bugs.kde.org/show_bug.cgi?id=487002 --- Comment #1 from Dave --- Latest nightly build downloaded from https://cdn.kde.org/ci-builds/system/dolphin/master/windows/ Build date 8/5/24 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 487002] New: Text disappears
https://bugs.kde.org/show_bug.cgi?id=487002 Bug ID: 487002 Summary: Text disappears Classification: Applications Product: dolphin Version: unspecified Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: dave.burbi...@catch.com.au CC: kfm-de...@kde.org Target Milestone: --- Created attachment 169468 --> https://bugs.kde.org/attachment.cgi?id=169468=edit Part of screen so you can see it SUMMARY I am running Windows 11 with a dark theme. The the view pane (white background) showing files & folders the text is white. It can be read if a select a file or folder. One the hamburger menu text is dark grey on black - hard to read but not impossible STEPS TO REPRODUCE 1. Start Dolphin 2. 3. OBSERVED RESULT Can't read text EXPECTED RESULT Should be able to read text. Ideally the background should be black SOFTWARE/OS VERSIONS Windows: I'm at work - so this computer (Win 11) macOS: n/a Linux/KDE Plasma: Runs fine at home (Arch Linux) ADDITIONAL INFORMATION If there is an option to swap to a dark theme, it is going to be difficult to find due to this bug -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446654] Feature Request: mirror a panel on all monitors
https://bugs.kde.org/show_bug.cgi?id=446654 Dave Vasilevsky changed: What|Removed |Added CC||d...@vasilevsky.ca -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412588] feature to duplicate a panel or save a panels config
https://bugs.kde.org/show_bug.cgi?id=412588 Dave Vasilevsky changed: What|Removed |Added CC||d...@vasilevsky.ca -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 471462] Hard-to-see colors in black-on-white color scheme
https://bugs.kde.org/show_bug.cgi?id=471462 --- Comment #1 from Dave Vasilevsky --- The Gnome palettes here tend to look much nicer on light backgrounds: https://gitlab.gnome.org/GNOME/gnome-terminal/-/blob/master/src/terminal-profile-editor.cc?ref_type=heads#L196 . At least in the sense that they're actually readable! It also helps that Gnome allows choosing the overall "scheme" (background/foreground colors) and "palette" (set of colors) independently. It doesn't look like there's a Konsole black-on-white scheme update in a decade, so it's not unreasonable to think it's due for an update: https://invent.kde.org/utilities/konsole/-/blob/master/data/color-schemes/BlackOnWhite.colorscheme?ref_type=heads Another option might be adding a new scheme you like to the KDE Store (which is free): https://store.kde.org/browse?cat=462=rating Or you could pick an existing scheme from there. Unforunately few of the currently available schemes are light-colored, and tbh I find them mostly pretty weird. But some, like 'Github Light' are quite nice: https://store.kde.org/p/1574065/ -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 471462] Hard-to-see colors in black-on-white color scheme
https://bugs.kde.org/show_bug.cgi?id=471462 Dave Vasilevsky changed: What|Removed |Added CC||d...@vasilevsky.ca -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 485180] KCalc doesnt launch by pressing XF86Calculator button
https://bugs.kde.org/show_bug.cgi?id=485180 --- Comment #1 from Dave --- Created attachment 168247 --> https://bugs.kde.org/attachment.cgi?id=168247=edit Picture of keyboard Numpad with dedicated Calculator button -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 485180] New: KCalc doesnt launch by pressing XF86Calculator button
https://bugs.kde.org/show_bug.cgi?id=485180 Bug ID: 485180 Summary: KCalc doesnt launch by pressing XF86Calculator button Classification: Frameworks and Libraries Product: frameworks-kglobalaccel Version: 6.0.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: davesy...@gmail.com Target Milestone: --- Created attachment 168246 --> https://bugs.kde.org/attachment.cgi?id=168246=edit Output of xev command after pressing calculator and +/- button *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY My Dell Lattitude keyboad has a Calculator and +/- button. Botton buttons are detected as XF6Calculator and F9 in xev command. Please see attached screenshot of xev. Issues: 1. KCalc doesnot launch by pressing XF86Calculator button. (It works fine whenever I use Gnome and launches gnome-calculator on same laptop) 2. +/- button should not be registered as F9 3. XF86calulator button is not register in systemsettings>Keyboard>Shortcuts so it cannot be assigened to any app. STEPS TO REPRODUCE 1. On UK layout keyboard with dedicated Calulator button (picture attached), press the the Calculator button OBSERVED RESULT Nothing happens. EXPECTED RESULT kcalc should launch, SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE Neon (available in About System) KDE Plasma Version: 6 KDE Frameworks Version: 6 Qt Version: 6.6.2 ADDITIONAL INFORMATION (KDE 5 also had the same issue) -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 484691] KDE Plasma 6 after updates Discover will not open. Used "apt update" still broken, restarted, then shut down, still broken.
https://bugs.kde.org/show_bug.cgi?id=484691 --- Comment #2 from Dave --- Thank you for the update. This ticket can be closed. The next day everything was working again. I have no idea what changed. Thank you again for the follow up. On Mon, Apr 1, 2024 at 10:01 PM Harald Sitter wrote: > https://bugs.kde.org/show_bug.cgi?id=484691 > > Harald Sitter changed: > >What|Removed |Added > > > CC||sit...@kde.org > Resolution|--- |BACKTRACE > Status|REPORTED|NEEDSINFO > > --- Comment #1 from Harald Sitter --- > If you're reporting a crash, attach a backtrace with debug symbols; see > > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 484691] New: KDE Plasma 6 after updates Discover will not open. Used "apt update" still broken, restarted, then shut down, still broken.
https://bugs.kde.org/show_bug.cgi?id=484691 Bug ID: 484691 Summary: KDE Plasma 6 after updates Discover will not open. Used "apt update" still broken, restarted, then shut down, still broken. Classification: Applications Product: Discover Version: 6.0.3 Platform: Neon OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: ddevans...@gmail.com CC: aleix...@kde.org Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY I tried to do backtrace but could understand instructions. steps I took in terminal did not work. Bug reporting too complicated for me. The Discover app attempts to start but does not. STEPS TO REPRODUCE 1. install KDE plasma 6 2. run sudo apt update 3. click on Discover app button in every location of KDE Plasma desktop and click on them OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version:6 KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482757] Crash / Segfault on Shift+window drag
https://bugs.kde.org/show_bug.cgi?id=482757 dave@hal9000 changed: What|Removed |Added CC||ffcru...@gmail.com --- Comment #1 from dave@hal9000 --- Also experiencing the exact same issue. System info: Operating System: EndeavourOS KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.8-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 24 × AMD Ryzen 9 7900X 12-Core Processor Memory: 30.5 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 Manufacturer: ASUS -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 439736] Can't drag and drop tracks from context view/albums
https://bugs.kde.org/show_bug.cgi?id=439736 --- Comment #7 from Dave --- Yes that's the functionality, and I can confirm that it works. The problem turned out to be a misconfiguration on my system: Amarok was picking up shared libraries left over from from an older installation. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 439736] Can't drag and drop tracks from context view/albums
https://bugs.kde.org/show_bug.cgi?id=439736 --- Comment #5 from Dave --- This version I have is self-compiled (Gentoo) from the git master branch downloaded today from invent.kde.org. I can't find a 'head' branch. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 439736] Can't drag and drop tracks from context view/albums
https://bugs.kde.org/show_bug.cgi?id=439736 --- Comment #2 from Dave --- This still doesn't work in Amarok 2.9.71using KDE Frameworks 5.115.0 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 479374] New: Unable to create account using initial account creator or add account
https://bugs.kde.org/show_bug.cgi?id=479374 Bug ID: 479374 Summary: Unable to create account using initial account creator or add account Classification: Applications Product: kontact Version: GIT (master) Platform: Neon OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: mail Assignee: kdepim-b...@kde.org Reporter: davm...@davmor2.co.uk Target Milestone: --- Created attachment 164657 --> https://bugs.kde.org/attachment.cgi?id=164657=edit page I'm stuck on SUMMARY In Kontact 5.240.90 rc1 (24.01.90) I am unable to get past the attached screenshots page in the account creation STEPS TO REPRODUCE 1. On initial setup and on add account after 2. I am unable to get past this screen 3. Try an create an Imap/SMTP account OBSERVED RESULT I get to the create account page and it refuses to go any further leaving me without an account EXPECTED RESULT I expect the create account button to take me onto the next part of the setup normally encryption SOFTWARE/OS VERSIONS Linux/KDE Plasma: Neon Unstable plasma 6 (available in About System) KDE Plasma Version: 5.91.90 KDE Frameworks Version: 5.248.0 Qt Version: 6.6.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479046] New: RFE: Showfoto rename
https://bugs.kde.org/show_bug.cgi?id=479046 Bug ID: 479046 Summary: RFE: Showfoto rename Classification: Applications Product: digikam Version: 8.2.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Showfoto-Core Assignee: digikam-bugs-n...@kde.org Reporter: gilbertd+...@treblig.org Target Milestone: --- SUMMARY In digikam I can rename photos (with f2 in most places); I don't seem to be able to showfoto, but think it would be useful. In my case I've got a directory of photos gathered with an external scanner app (rather than my camera that I'd use digikam for), and I want to go and rename them to say what they are rather than the raw scanner-date-sequence.jpg; so I was using showfoto to page through them, but don't see an obvious rename. STEPS TO REPRODUCE 1. 2. 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.
[k3b] [Bug 478589] New: MPEG_PICTURE_CODE case
https://bugs.kde.org/show_bug.cgi?id=478589 Bug ID: 478589 Summary: MPEG_PICTURE_CODE case Classification: Applications Product: k3b Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Video CD project Assignee: k...@kde.org Reporter: gilbertd+...@treblig.org CC: ch...@ckvsoft.at, mich...@jabster.pl, tr...@kde.org Target Milestone: --- SUMMARY Spotted during build by the compiler: k3b/libk3b/projects/videocd/mpeginfo/k3bmpeginfo.cpp:307:5: warning: case label value exceeds maximum value for type [-Wswitch-outside-range] 307 | case MPEG_PICTURE_CODE: | ^~~~ it's got a point, the switch is on 'mark' which is a 'byte' and k3bmpeginfo.h defines: #define MPEG_PICTURE_CODE((ulong) 0x0100) No idea what it's actually trying to do. STEPS TO REPRODUCE 1. 2. 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.
[k3b] [Bug 253768] Error when trying to open the filetype options while ripping audio CD.
https://bugs.kde.org/show_bug.cgi?id=253768 Dave Gilbert changed: What|Removed |Added CC||gilbertd+...@treblig.org --- Comment #15 from Dave Gilbert --- Hi Albert, Yeh that fix fixes this for me - thanks! (Note I suspect it's not the same as the original bug; they got a good real error, where as what Julius reported in comment 8 and that I also saw was no error in the dialog which seems to be the odd fallthrough KCModuleLoader) -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 442092] allow infinite time before password is required to unlock after auto-locking
https://bugs.kde.org/show_bug.cgi?id=442092 Dave Kaye changed: What|Removed |Added CC||d...@linuxmail.org --- Comment #2 from Dave Kaye --- I want to have a screen saving program similar to KDE4 which was lost in an upgrade to KDE5. That would mean slide show capability with no password required upon return to normal screen activity. I have been following the discussions on gitlab about kscreenlocker as well as general internet interest on this subject. I have modified less than 10 lines of code and achieved a reasonable program. My system is: KDE Plasma Version 5.18.5 KDE Frameworks Version 5.71.0 Qt Version 5.12.7 Linux Distribution openSUSE Leap 15.2 Within the kscreenlocker program, I modified 3 files changing only a couple of lines per file: -- in the file kcm/kcm.ui I changed the lock grace spinbox property specialValueText from "Immediately" to "Forever", and the minimum value from 0 to -1. This results in the line "Allow unlocking without password for:" spinbox display to change from "Immediately, 1 second, 2 seconds ..." to "Forever, 0 seconds, 1 second, 2 seconds...". This would make sense to the user, as 0 seconds and immediately are equivalent. The selection of Forever will give a time value of -1 which is invisible to the user. No other modifications to the user interface are needed. (I did change the step value to 1 from 10, a matter of personal preference and ease of usage - but not necessary.) -- in the file kcfg/kscreenlockersettings.kcfg I updated the minimum value from 0 to -1. This makes it consistent with the ui modification. -- in the file ksldapp.cpp within the configure subroutine I added one condition to the lock grace setup if statement. This checked for a lock request and grace time of -1 seconds. If found, it set the variable m_lockGrace to -1. The variable m_lockGrace with a value of -1 already exists in the code and causes the system not to require a password when exiting a locked condition. It appears to be active throughout the code, however on my system I can only test with the XOrg screen control. The diff file for the changes is as follows: --- ksldapp.cpp +++ ksldapp.cpp @@ -341,7 +341,10 @@ // timeout stored in minutes m_idleId = KIdleTime::instance()->addIdleTimeout(timeout*1000*60); } -if (KScreenSaverSettings::lock()) { +if (KScreenSaverSettings::lock() && (KScreenSaverSettings::lockGrace() == -1)) { + // lockGrace is forever, flag grace time to last forever + m_lockGrace = -1; +} else if (KScreenSaverSettings::lock()) { // lockGrace is stored in seconds m_lockGrace = KScreenSaverSettings::lockGrace() * 1000; } else { --- kcm/kcm.ui +++ kcm/kcm.ui @@ -76,8 +76,11 @@ - Immediately + Forever + + -1 + 300 --- kcfg/kscreenlockersettings.kcfg +++ kcfg/kscreenlockersettings.kcfg @@ -23,7 +23,7 @@ 5 - 0 + -1 300 The user will setup the screen locker with the slide show or other lock screen appearance and their normal lock screen settings. In the variable labeled "Allow unlocking without password for:" the user will select "Forever" to setup the system as a no password needed screen saver. I believe this is easier to do than using a huge grace time value. It also does not require a special check button or similar constuct to indicate a screen saver verses a screen locker. The program interface flow appears to be readily understandable. The program also acts as a password required screen locker, ignoring the grace time settings, if it is activated by the hot key sequence. This is in existing code. It will allow a rapid screen lock if such action is needed. This is a demonstration/idea code only. I do not have KDE6 and multiple screen types to check the modifications for the newest release and make a MR. In going from my version of KDE5 to KDE6 it appears that the codes are the same (line numbers slightly different) - only the ui file has been changed to a qml file. It may be possible to make a quick test KDE6 version and see if it is worth consideration for inclusion in the kscreenlocker program. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 476478] New: Kontact Crashes when trying to view Identities
https://bugs.kde.org/show_bug.cgi?id=476478 Bug ID: 476478 Summary: Kontact Crashes when trying to view Identities Classification: Applications Product: kontact Version: unspecified Platform: Archlinux OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: dave.conn...@gmail.com Target Milestone: --- Application: kontact (5.24.2 (23.08.2)) Qt Version: 5.15.11 Frameworks Version: 5.111.0 Operating System: Linux 6.5.9-arch2-1 x86_64 Windowing System: X11 Distribution: "Arch Linux" DrKonqi: 5.27.9 [KCrashBackend] -- Information about the crash: I have been dealing with issues relating to changing settings in my kmail. I tried to change the domain that is used in one of my identities. I tried sending an email from kmail after changing these settings, but my emails were being denied by Google due to DKIM (different issue). I noticed on the return to sender, that the domain still hadn't changed to what I had set in the Kontact settings. I deleted some emails from my outbox from the GUI, however Kmail then crashed. I tried cleaning the folders manually after following instructions from this bug report. https://bugs.kde.org/show_bug.cgi?id=339214#c24 I got it working after restarting my computer, however now I occasionally get crashes in the Kontact settings menu, especially when trying to view the Identities. Sometimes it doesn't crash, and the Identities page is just blank. Sometimes the Identities page seems to work after restarting the application. The crash can be reproduced sometimes. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #4 0x7f44dc35f4e8 in KCModuleProxy::isChanged() const () at /usr/lib/libKF5KCMUtils.so.5 #5 0x7f44dc63e35e in () at /usr/lib/libkontactprivate.so.5 #6 0x7f44db0d1097 in () at /usr/lib/libQt5Core.so.5 #7 0x7f44da790b69 in KPageDialog::currentPageChanged(KPageWidgetItem*, KPageWidgetItem*) () at /usr/lib/libKF5WidgetsAddons.so.5 #8 0x7f44db0d1097 in () at /usr/lib/libQt5Core.so.5 #9 0x7f44da799489 in KPageWidget::currentPageChanged(KPageWidgetItem*, KPageWidgetItem*) () at /usr/lib/libKF5WidgetsAddons.so.5 #10 0x7f44db0d1097 in () at /usr/lib/libQt5Core.so.5 #11 0x7f44da79930c in KPageView::currentPageChanged(QModelIndex const&, QModelIndex const&) () at /usr/lib/libKF5WidgetsAddons.so.5 #12 0x7f44da79d965 in () at /usr/lib/libKF5WidgetsAddons.so.5 #13 0x7f44db0d1097 in () at /usr/lib/libQt5Core.so.5 #14 0x7f44db0688cc in QItemSelectionModel::selectionChanged(QItemSelection const&, QItemSelection const&) () at /usr/lib/libQt5Core.so.5 #15 0x7f44db06c400 in QItemSelectionModel::emitSelectionChanged(QItemSelection const&, QItemSelection const&) () at /usr/lib/libQt5Core.so.5 #16 0x7f44db06665f in QItemSelectionModel::select(QItemSelection const&, QFlags) () at /usr/lib/libQt5Core.so.5 #17 0x7f44dc059ba5 in QTreeViewPrivate::select(QModelIndex const&, QModelIndex const&, QFlags) () at /usr/lib/libQt5Widgets.so.5 #18 0x7f44dc04dfc2 in QTreeView::setSelection(QRect const&, QFlags) () at /usr/lib/libQt5Widgets.so.5 #19 0x7f44dbfde0f6 in QAbstractItemView::mousePressEvent(QMouseEvent*) () at /usr/lib/libQt5Widgets.so.5 #20 0x7f44dbdaf4e9 in QWidget::event(QEvent*) () at /usr/lib/libQt5Widgets.so.5 #21 0x7f44dbe5d9d3 in QFrame::event(QEvent*) () at /usr/lib/libQt5Widgets.so.5 #22 0x7f44db099142 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #23 0x7f44dbd788ef in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #24 0x7f44dbd7ddaf in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #25 0x7f44db09c168 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #26 0x7f44dbd7c0ea in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () at /usr/lib/libQt5Widgets.so.5 #27 0x7f44dbdcce85 in () at /usr/lib/libQt5Widgets.so.5 #28 0x7f44dbdcebd7 in () at /usr/lib/libQt5Widgets.so.5 #29 0x7f44dbd788ff in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #30 0x7f44db09c168 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #31 0x7f44db54194c in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () at /usr/lib/libQt5Gui.so.5 #32 0x7f44db52a6e5 in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () at /usr/lib/libQt5Gui.so.5 #33 0x7f44bc52f5e0 in () at /usr/lib/libQt5XcbQpa.so.5 #34 0x7f44d1d0df69 in () at /usr/lib/libglib-2.0.so.0 #35 0x7f44d1d6c327 in () at
[krusader] [Bug 472119] New: Viewing or editing a .txt file results in certain words being formatted in bold, different colors, etc
https://bugs.kde.org/show_bug.cgi?id=472119 Bug ID: 472119 Summary: Viewing or editing a .txt file results in certain words being formatted in bold, different colors, etc Classification: Applications Product: krusader Version: 2.7.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: krviewer Assignee: krusader-bugs-n...@kde.org Reporter: dkol...@comcast.net CC: krusader-bugs-n...@kde.org Target Milestone: --- SUMMARY *** Viewing or editing a .txt file results in certain words being formatted in bold, different colors, etc *** STEPS TO REPRODUCE 1. Highlight .txt file 2. Press or 3. File opens in view or edit mode OBSERVED RESULT Certain words are in bold, quotations are colored, other words are colored EXPECTED RESULT Plain text file with no added features!! Must select Tools-Mode-Normal or Tools-Highlighting-None to remove extra formatting. NEED to set one of those to the default. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 22.04.2 LTS Krusader Version: 2.7.2 KDE Frameworks Version: 5.29.0 Qt Version: Version 5.15.3 (built against 5.15.3) ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 449106] Discrete graphics card not detected for dual-DPU setup with no /sys/kernel/debug/vgaswitcheroo/switch file on disk
https://bugs.kde.org/show_bug.cgi?id=449106 --- Comment #11 from Dave Vasilevsky --- Nate Graham do you think you could help me find someone to review? -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 470884] New: Elisa player can't play playlist radio streams (.pls, .m3u)
https://bugs.kde.org/show_bug.cgi?id=470884 Bug ID: 470884 Summary: Elisa player can't play playlist radio streams (.pls, .m3u) Classification: Applications Product: Elisa Version: 23.04.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: sunny.bed7...@fastmail.com Target Milestone: --- SUMMARY Several internet radio stations offer a playlist file as the resource used to tune to their stream. These are unusable in Elisa at the moment. Streams that I have confirmed work with Elisa come in the form of MPEG ADTS > checking the file format of a stream saved to disk $ curl -o out 'https://radiointernet.co:7000' $ file out out: MPEG ADTS, layer III, v1, 32 kbps, 44.1 kHz, JntStereo Streams that do not work with Elisa are playlists $ curl -o airout 'http://airspectrum.cdnstream1.com:8114/1648_128.m3u' $ file airout airout: ASCII text, with CRLF line terminators >airout content http://airspectrum.cdnstream1.com:8114/1648_128 $ curl -o pls 'http://79.98.108.170:8117/listen.pls?sid=1' $ file pls pls: PLS playlist, ASCII text >pls content [playlist] NumberOfEntries=1 File1=http://79.98.108.170:8117/stream Title1=Extreme Deep House Radio Length1=-1 Version=2% If you manually add the url of the internal playlist entry, now you can play that radio station. STEPS TO REPRODUCE 1. Add the following radio stations to Elisa: http://airspectrum.cdnstream1.com:8114/1648_128.m3u http://79.98.108.170:8117/listen.pls?sid=1 https://radiointernet.co:7000 2. Play each added radio station.play in Elisa. OBSERVED RESULT Elisa should not be able to play the first two radio stations. The last radio station should work fine. If you extract the real audio streams out of the playlists, you should be able to stream them with Elisa. EXPECTED RESULT Elisa plays all of the most common radio stream formats (playlist or pure audio stream) out of the box. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 37 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 470816] New: Display not configurable.
https://bugs.kde.org/show_bug.cgi?id=470816 Bug ID: 470816 Summary: Display not configurable. Classification: Applications Product: krusader Version: 2.7.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: krviewer Assignee: krusader-bugs-n...@kde.org Reporter: dkol...@comcast.net CC: krusader-bugs-n...@kde.org Target Milestone: --- Created attachment 159556 --> https://bugs.kde.org/attachment.cgi?id=159556=edit Song lyrics with the word "for" in bold, quoted text in red. 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 *** STEPS TO REPRODUCE 1. Click F3 to View a .txt file 2. Click F4 to Edit a .txt file OBSERVED RESULT Mode NOT set to "Normal", Highlighting NOT set to "None"... Certain words are now bold, quotes are highlighted in red, etc EXPECTED RESULT A PLAIN txt file, with NO highlighting or special effects. SOFTWARE/OS VERSIONS Linux/KDE Plasma: ??? (available in About System) KDE Plasma Version: ??? KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION Running Ubuntu 22.04.2 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 449106] Discrete graphics card not detected for dual-DPU setup with no /sys/kernel/debug/vgaswitcheroo/switch file on disk
https://bugs.kde.org/show_bug.cgi?id=449106 Dave Vasilevsky changed: What|Removed |Added CC||d...@vasilevsky.ca --- Comment #8 from Dave Vasilevsky --- It looks like gnome checks this by asking switcheroo-control over dbus[0], and switcheroo-control reads the cards from udev[1]. Then for launching with the selected GPU, it uses environment variables chosen by switcheroo-control[2], rather than just setting DRI_PRIME like KDE does. [0] https://github.com/GNOME/gnome-shell/blob/dec26b7da2ee61641eac8909d0fc2a9f8985216d/js/ui/appMenu.js#L163 [1] https://gitlab.freedesktop.org/hadess/switcheroo-control/-/blob/master/src/switcheroo-control.c [2] https://github.com/GNOME/gnome-shell/blob/dec26b7da2ee61641eac8909d0fc2a9f8985216d/src/shell-app.c#L1342 On my Intel/Nvidia box I can see that switcheroo-control's dbus service can indeed see my GPUs, as well as how to select each one: $ gdbus call --system --dest net.hadess.SwitcherooControl --object-path /net/hadess/SwitcherooControl --method org.freedesktop.DBus.Properties.Get net.hadess.SwitcherooControl HasDualGpu (,) $ gdbus call --system --dest net.hadess.SwitcherooControl --object-path /net/hadess/SwitcherooControl --method org.freedesktop.DBus.Properties.Get net.hadess.SwitcherooControl GPUs (<[{'Name': <'NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q]'>, 'Environment': <['__GLX_VENDOR_LIBRARY_NAME', 'nvidia', '__NV_PRIME_RENDER_OFFLOAD', '1']>, 'Default': }, {'Name': <'Intel® UHD Graphics 630'>, 'Environment': <['DRI_PRIME', 'pci-_00_02_0']>, 'Default': }]>,) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467092] Some desktop icons disappear on wake-up from sleep and only re-appear when plasmashell is restarted ("Creating a fake screen in order for Qt not to crash")
https://bugs.kde.org/show_bug.cgi?id=467092 Dave changed: What|Removed |Added CC||sunny.bed7...@fastmail.com -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 377231] Color of track not modifyable
https://bugs.kde.org/show_bug.cgi?id=377231 --- Comment #16 from Dave Gilbert --- and I can't trigger any more valgrindisms. Looks good! -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 377231] Color of track not modifyable
https://bugs.kde.org/show_bug.cgi?id=377231 --- Comment #15 from Dave Gilbert --- Yeh I think that's nailed the 'cancel' problem. -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 377231] Color of track not modifyable
https://bugs.kde.org/show_bug.cgi?id=377231 --- Comment #13 from Dave Gilbert --- Hi Torsten, Thanks for the fixes! I'm using the track from: https://michaelminn.net/tutorials/google-gpx/Track_2016-08-22_200130.gpx Note one thing I'm seeing is that: void EditPlacemarkDialog::restoreInitial( int result ) if ( d->m_placemark->coordinate().latitude( GeoDataCoordinates::Degree ) != d->m_initialCoords.latitude( GeoDataCoordinates::Degree ) || d->m_placemark->coordinate().longitude( GeoDataCoordinates::Degree ) != d->m_initialCoords.longitude( GeoDataCoordinates::Degree ) ) { is triggering, a bit of debug gave me: EditPlacemarkDialog::restoreInitial: initial: 47.4937/-117.578 current: 47.4937/-117.578 so I'm wondering if this is an FP rounding disagreement that's causing that restore. -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 377231] Color of track not modifyable
https://bugs.kde.org/show_bug.cgi?id=377231 --- Comment #11 from Dave Gilbert --- playing with the tick and stuff I managed to trigger valgrind: ==15894== Invalid read of size 8 ==15894==at 0x49C99F8: Marble::GeoDataObject::parent() (GeoDataObject.cpp:67) ==15894==by 0x4B69F7D: Marble::GeoDataTreeModel::parent(QModelIndex const&) const (GeoDataTreeModel.cpp:434) ==15894==by 0x4B7390D: QModelIndex::parent() const (qabstractitemmodel.h:443) ==15894==by 0x4B70384: Marble::KDescendantsProxyModel::mapFromSource(QModelIndex const&) const (kdescendantsproxymodel.cpp:417) ==15894==by 0x4B7177F: Marble::KDescendantsProxyModelPrivate::sourceRowsAboutToBeRemoved(QModelIndex const&, int, int) (kdescendantsproxymodel.cpp:661) ==15894==by 0x4B734CE: Marble::KDescendantsProxyModel::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (moc_kdescendantsproxymodel.cpp:118) ==15894==by 0xF9C27D7: void doActivate(QObject*, int, void**) (qobject.cpp:3935) ==15894==by 0xF93C399: QAbstractItemModel::rowsAboutToBeRemoved(QModelIndex const&, int, int, QAbstractItemModel::QPrivateSignal) (moc_qabstractitemmodel.cpp:599) ==15894==by 0xF944A9B: QAbstractItemModel::beginRemoveRows(QModelIndex const&, int, int) (qabstractitemmodel.cpp:2818) ==15894==by 0x4B6B9E7: Marble::GeoDataTreeModel::removeFeature(Marble::GeoDataContainer*, int) (GeoDataTreeModel.cpp:738) ==15894==by 0x4B6BB37: Marble::GeoDataTreeModel::removeFeature(Marble::GeoDataFeature*) (GeoDataTreeModel.cpp:765) ==15894==by 0x4B6BB80: Marble::GeoDataTreeModel::updateFeature(Marble::GeoDataFeature*) (GeoDataTreeModel.cpp:779) ==15894== Address 0x23dd2340 is 16 bytes inside a block of size 32 free'd ==15894==at 0x4844669: operator delete(void*) (vg_replace_malloc.c:935) ==15894==by 0x49C34FD: Marble::GeoDataMultiGeometry::~GeoDataMultiGeometry() (GeoDataMultiGeometry.cpp:36) ==15894==by 0x49B26C7: Marble::GeoDataPlacemark::setGeometry(Marble::GeoDataGeometry*) (GeoDataPlacemark.cpp:282) ==15894==by 0x49B2663: Marble::GeoDataPlacemark::setCoordinate(Marble::GeoDataCoordinates const&) (GeoDataPlacemark.cpp:276) ==15894==by 0x4C24922: Marble::EditPlacemarkDialog::restoreInitial(int) (EditPlacemarkDialog.cpp:484) ==15894==by 0x4C24EAA: Marble::EditPlacemarkDialog::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (moc_EditPlacemarkDialog.cpp:153) ==15894==by 0xF9C27D7: void doActivate(QObject*, int, void**) (qobject.cpp:3935) ==15894==by 0xED6439F: QDialog::finished(int) (moc_qdialog.cpp:230) ==15894==by 0xF9C27D7: void doActivate(QObject*, int, void**) (qobject.cpp:3935) ==15894==by 0xECF3B27: QDialogButtonBoxPrivate::_q_handleButtonClicked() (qdialogbuttonbox.cpp:882) ==15894==by 0xF9C27D7: void doActivate(QObject*, int, void**) (qobject.cpp:3935) ==15894==by 0xEC42B83: QAbstractButton::clicked(bool) (moc_qabstractbutton.cpp:308) ==15894== Block was alloc'd at ==15894==at 0x4841FF5: operator new(unsigned long) (vg_replace_malloc.c:434) ==15894==by 0x352FC2E2: ??? (in /opt/lib64/marble/plugins/GpxPlugin.so) ==15894==by 0x4A114EA: Marble::GeoParser::parseDocument() (GeoParser.cpp:139) ==15894==by 0x4A115B9: Marble::GeoParser::parseDocument() (GeoParser.cpp:166) ==15894==by 0x4A10D2E: Marble::GeoParser::read(QIODevice*) (GeoParser.cpp:79) ==15894==by 0x352F839B: ??? (in /opt/lib64/marble/plugins/GpxPlugin.so) ==15894==by 0x4CAC7C9: Marble::ParsingTask::run() (RunnerTask.cpp:90) ==15894==by 0xF7D275F: QThreadPoolThread::run() (qthreadpool.cpp:100) ==15894==by 0xF7CF56C: operator() (qthread_unix.cpp:350) ==15894==by 0xF7CF56C: terminate_on_exception > (qthread_unix.cpp:287) ==15894==by 0xF7CF56C: QThreadPrivate::start(void*) (qthread_unix.cpp:310) ==15894==by 0x10035C56: start_thread (pthread_create.c:444) ==15894==by 0x100BB973: clone (clone.S:100) -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 377231] Color of track not modifyable
https://bugs.kde.org/show_bug.cgi?id=377231 --- Comment #10 from Dave Gilbert --- Thanks; that OK case has gone. There's stil something odd going on, I tend to fully open the section of the tree, so I see: v Track... Document v time Placemark 0 1 vMultiGeometry Track and then play with the ticks and bringing the dialog up. Sometimes I see that there's a change where the 'MultiGeometry' and 'track' entries disappear when I turn the tick off and back; sometimes the track itself isn't displayed again. and on a really bad day, I just triggered the cancel crash again: (gdb) bt full #0 __cxxabiv1::__dynamic_cast(void const*, __cxxabiv1::__class_type_info const*, __cxxabiv1::__class_type_info const*, ptrdiff_t) (src_ptr=0x7fff30013a50, src_type=0x77e21168 , dst_type=0x77e1fac8 , src2dst=0) at ../../../../libstdc++-v3/libsupc++/dyncast.cc:57 vtable = 0x7ff8cff23bc3 prefix = 0x7ff8cff23bb3 whole_ptr = whole_type = result = {dst_ptr = 0x179df50, whole2dst = 3964353270, whole2src = 32767, dst2src = 805330464, whole_details = 32767} whole_vtable = whole_prefix = #1 0x779164b9 in Marble::GeoDataTreeModel::rowCount(QModelIndex const&) const (this=0xb05740, parent=...) at /discs/more/git/marble/src/lib/marble/GeoDataTreeModel.cpp:136 container = 0x0 parentItem = 0x7fff30013a50 #2 0x7fffeca63d78 in QAbstractItemModel::hasIndex(int, int, QModelIndex const&) const (this=0xb05740, row=0, column=0, parent=...) at itemmodels/qabstractitemmodel.cpp:1784 #3 0x77917cda in Marble::GeoDataTreeModel::index(int, int, QModelIndex const&) const (this=0xb05740, row=0, column=0, parent=...) at /discs/more/git/marble/src/lib/marble/GeoDataTreeModel.cpp:371 parentItem = 0x7fffec4b682b <__cxxabiv1::__vmi_class_type_info::__do_dyncast(long, __cxxabiv1::__class_type_info::__sub_kind, __cxxabiv1::__class_type_info const*, void const*, __cxxabiv1::__class_type_info const*, void const*, __cxxabiv1::__class_type_info::__dyncast_result&) const+635> childItem = 0x77e20210 #4 0x7fffeca8b7d1 in QSortFilterProxyModelPrivate::proxy_to_source(QModelIndex const&) const (this=this@entry=0x179df50, proxy_index=) at itemmodels/qsortfilterproxymodel.cpp:576 it = {i = } m = source_row = source_col = #5 0x7fffeca8bc55 in QSortFilterProxyModel::mapToSource(QModelIndex const&) const (proxyIndex=, this=) at itemmodels/qsortfilterproxymodel.cpp:3171 d = 0x179df50 d = 0x179df50 source_index = {r = -1, c = -1, i = 0, m = 0x0} #6 QSortFilterProxyModel::flags(QModelIndex const&) const (this=, index=) at itemmodels/qsortfilterproxymodel.cpp:2548 --Type for more, q to quit, c to continue without paging-- d = 0x179df50 source_index = {r = -1, c = -1, i = 0, m = 0x0} #7 0x7fffeca73820 in QModelIndex::flags() const (this=0x1a79420) at ../../include/QtCore/../../src/corelib/itemmodels/qabstractitemmodel.h:463 #8 QItemSelection::contains(QModelIndex const&) const (this=this@entry=0x179e5a0, index=...) at itemmodels/qitemselectionmodel.cpp:496 #9 0x7fffeca73f2f in QItemSelectionModel::isSelected(QModelIndex const&) const (this=, index=...) at itemmodels/qitemselectionmodel.cpp:1460 d = 0x179e530 selected = false it = {i = 0x7fffecb88c50 } #10 0x7fffedaa8dab in QTreeView::drawBranches(QPainter*, QRect const&, QModelIndex const&) const (this=0x18d7060, painter=0x7fffc1b8, rect=, index=...) at itemviews/qtreeview.cpp:1834 d = 0x179b740 reverse = false indent = 20 outer = 0 viewItem = @0x1a79420: {index = {r = 0, c = 0, i = 34955584, m = 0x16ad1c0}, parentItem = 6, expanded = 0, spanning = 0, hasChildren = 0, hasMoreSiblings = 0, total = 0, level = 3, height = 17} level = 3 primitive = {x1 = 80, y1 = 119, x2 = , y2 = } parent = {r = , c = , i = , m = } current = {r = 0, c = 0, i = 34060896, m = 0x16ad1c0} ancestor = {r = 0, c = 0, i = 32675840, m = 0x16ad1c0} opt = { = {version = 4, type = 10, state = {i = 65537}, direction = Qt::LeftToRight, rect = {x1 = 0, y1 = 0, x2 = -1, y2 = -1}, fontMetrics = {d = {d = 0x9a7e40}}, palette = {d = 0x99b0d0, {data = {current_group = 0, resolve_mask = 0}, for_faster_swapping_dont_use = 0}}, styleObject = 0x18d7060}, displayAlignment = {i = 129}, decorationAlignment = {i = 132}, textElideMode = Qt::ElideLeft, decorationPosition = QStyleOptionViewItem::Left, decorationSize = {wd = 16, ht = 16}, font = {d = {d = 0x9a7e40}, resolve_mask = 0}, showDecorationSelected = true, features = {i = 0}, locale = {d = {d = 0x2199e70}}, widget = 0x18d7060, index = {r = -1, c = -1, i = 0, m = 0x0}, checkState = Qt::Unchecked, icon = {d = 0x0}, text = {d = 0x7fffecb88160 }, viewItemPosition = Q
[marble] [Bug 377231] Color of track not modifyable
https://bugs.kde.org/show_bug.cgi?id=377231 --- Comment #7 from Dave Gilbert --- actually hmm.. I think there are more around here as well. I'm fairly sure I had a cancel crash again after a bit of poking around. I also can crash sometimes unticking the track as well; #0 0x79e8 in Marble::GeoDataObject::parent() (this=0x20) at /discs/more/git/marble/src/lib/marble/geodata/data/GeoDataObject.cpp:67 #1 0x77917fbb in Marble::GeoDataTreeModel::parent(QModelIndex const&) const (this=0xb05ec0, index=...) at /discs/more/git/marble/src/lib/marble/GeoDataTreeModel.cpp:440 #2 0x779218fe in QModelIndex::parent() const (this=0x7fffb610) at /usr/include/qt5/QtCore/qabstractitemmodel.h:443 #3 0x7791e375 in Marble::KDescendantsProxyModel::mapFromSource(QModelIndex const&) const (this=0xb05ed8, sourceIndex=...) at /discs/more/git/marble/src/lib/marble/kdescendantsproxymodel.cpp:417 #4 0x7791f770 in Marble::KDescendantsProxyModelPrivate::sourceRowsAboutToBeRemoved(QModelIndex const&, int, int) (this=0xa0e130, parent=..., start=0, end=0) at /discs/more/git/marble/src/lib/marble/kdescendantsproxymodel.cpp:661 #5 0x779214bf in Marble::KDescendantsProxyModel::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=0xb05ed8, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0x7fffb920) at /discs/more/git/marble/build/src/lib/marble/marblewidget_autogen/include/moc_kdescendantsproxymodel.cpp:118 #6 0x7fffecae87d8 in doActivate(QObject*, int, void**) (sender=0xb05ec0, signal_index=14, argv=0x7fffb920) at kernel/qobject.cpp:3935 #7 0x7fffecae34d7 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0xb05ec0, m=m@entry=0x7fffecd64900 , local_signal_index=local_signal_index@entry=11, argv=argv@entry=0x7fffb920) at kernel/qobject.cpp:3983 #8 0x7fffeca6239a in QAbstractItemModel::rowsAboutToBeRemoved(QModelIndex const&, int, int, QAbstractItemModel::QPrivateSignal) (this=this@entry=0xb05ec0, _t1=..., _t2=, _t2@entry=0, _t3=, _t3@entry=0, _t4=...) at .moc/moc_qabstractitemmodel.cpp:599 #9 0x7fffeca6aa9c in QAbstractItemModel::beginRemoveRows(QModelIndex const&, int, int) (this=0xb05ec0, parent=..., first=0, last=0) at itemmodels/qabstractitemmodel.cpp:2818 #10 0x779199d8 in Marble::GeoDataTreeModel::removeFeature(Marble::GeoDataContainer*, int) (this=0xb05ec0, parent=0x7fff34004738, row=0) at /discs/more/git/marble/src/lib/marble/GeoDataTreeModel.cpp:738 #11 0x77919b28 in Marble::GeoDataTreeModel::removeFeature(Marble::GeoDataFeature*) (this=0xb05ec0, feature=0x7fff34005c40) at /discs/more/git/marble/src/lib/marble/GeoDataTreeModel.cpp:765 #12 0x77919b71 in Marble::GeoDataTreeModel::updateFeature(Marble::GeoDataFeature*) (this=0xb05ec0, feature=0x7fff34005c40) at /discs/more/git/marble/src/lib/marble/GeoDataTreeModel.cpp:779 #13 0x779184f7 in Marble::GeoDataTreeModel::setData(QModelIndex const&, QVariant const&, int) (this=0xb05ec0, index=..., value=..., role=10) at /discs/more/git/marble/src/lib/marble/GeoDataTreeModel.cpp:521 #14 0x7fffeca8b8c9 in QSortFilterProxyModel::setData(QModelIndex const&, QVariant const&, int) (this=this@entry=0x1685aa0, index=..., value=..., role=role@entry=10) at itemmodels/qsortfilterproxymodel.cpp:2306 #15 0x7fffeda62ab4 in QStyledItemDelegate::editorEvent(QEvent*, QAbstractItemModel*, QStyleOptionViewItem const&, QModelIndex const&) (this=0x1778120, event=, model=0x1685aa0, option=, index=...) at itemviews/qstyleditemdelegate.cpp:635 #16 0x7fffeda384f6 in QAbstractItemViewPrivate::sendDelegateEvent(QModelIndex const&, QEvent*) const (this=this@entry=0x18ad810, index=..., event=event@entry=0x7fffc610) at itemviews/qabstractitemview.cpp:4463 #17 0x7fffeda3e14d in QAbstractItemView::edit(QModelIndex const&, QAbstractItemView::EditTrigger, QEvent*) (this=this@entry=0x18b5e80, index=..., trigger=trigger@entry=QAbstractItemView::SelectedClicked, event=event@entry=0x7fffc610) at itemviews/qabstractitemview.cpp:2683 #18 0x7fffeda38902 in QAbstractItemView::mouseReleaseEvent(QMouseEvent*) (this=0x18b5e80, event=0x7fffc610) at itemviews/qabstractitemview.cpp:1930 #19 0x7fffed7f3688 in QWidget::event(QEvent*) (this=this@entry=0x18b5e80, event=event@entry=0x7fffc610) at kernel/qwidget.cpp:9045 #20 0x7fffed8a4ae7 in QFrame::event(QEvent*) (this=0x18b5e80, e=0x7fffc610) at widgets/qframe.cpp:550 #21 0x7fffecab3af6 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) (receiver=receiver@entry=0x18b60c0, event=event@entry=0x7fffc610) at kernel/qcoreapplication.cpp:1190 -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 377231] Color of track not modifyable
https://bugs.kde.org/show_bug.cgi?id=377231 Dave Gilbert changed: What|Removed |Added CC||gilbertd+...@treblig.org --- Comment #6 from Dave Gilbert --- Nice; I'd agree the crash on 'cancel' on that dialog is gone. However, I can still crash it clicking OK: (Current git 419079e2f65b8357500cc3fd8a6425361404e95e ) #0 0x77878dc1 in Marble::OsmTagEditorWidget::placemarkData() const (this=0x0) at /discs/more/git/marble/src/lib/marble/osm/OsmTagEditorWidget.cpp:71 Note (this=0x0) #1 0x779d1641 in Marble::EditPlacemarkDialog::updateTextAnnotation() (this=0x1f5caa0) at /discs/more/git/marble/src/lib/marble/EditPlacemarkDialog.cpp:340 339 else { 340 const OsmPlacemarkData osmData = d->m_osmTagEditorWidget->placemarkData(); (gdb) p d->m_osmTagEditorWidget $4 = (Marble::OsmTagEditorWidget *) 0x0 341 const GeoDataPlacemark::GeoDataVisualCategory category = StyleBuilder::determineVisualCategory(osmData); #2 0x779d2d0c in Marble::EditPlacemarkDialog::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=0x1f5caa0, _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0x7fffaf80) at /discs/more/git/marble/build/src/lib/marble/marblewidget_autogen/include/moc_EditPlacemarkDialog.cpp:144 #3 0x7fffecae87d8 in doActivate(QObject*, int, void**) (sender=0x1f5caa0, signal_index=8, argv=0x7fffaf80) at kernel/qobject.cpp:3935 #4 0x7fffecae34d7 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x1f5caa0, m=m@entry=0x7fffedce38c0 , local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at kernel/qobject.cpp:3983 #5 0x7fffed9cb3d7 in QDialog::accepted() (this=this@entry=0x1f5caa0) at .moc/moc_qdialog.cpp:236 #6 0x7fffed9cb8c8 in QDialogPrivate::finalize(int, int) (this=, resultCode=1, dialogCode=) at dialogs/qdialog.cpp:176 #7 0x779d1dbb in Marble::EditPlacemarkDialog::checkFields() (this=0x1f5caa0) at /discs/more/git/marble/src/lib/marble/EditPlacemarkDialog.cpp:374 #8 0x779d2cfb in Marble::EditPlacemarkDialog::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=0x1f5caa0, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0x7fffb1a0) at /discs/more/git/marble/build/src/lib/marble/marblewidget_autogen/include/moc_EditPlacemarkDialog.cpp:143 #9 0x7fffecae87d8 in doActivate(QObject*, int, void**) (sender=0x2133400, signal_index=7, argv=0x7fffb1a0) at kernel/qobject.cpp:3935 #10 0x7fffecae34d7 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x2133400, m=m@entry=0x7fffedcd3680 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3983 #11 0x7fffed8a9b14 in QAbstractButton::pressed() (this=this@entry=0x2133400) at .moc/moc_qabstractbutton.cpp:295 #12 0x7fffed8a9f02 in QAbstractButtonPrivate::emitPressed() (this=0x1f50e20) at widgets/qabstractbutton.cpp:438 #13 0x7fffed8aa895 in QAbstractButton::mousePressEvent(QMouseEvent*) (this=0x2133400, e=0x7fffb750) at widgets/qabstractbutton.cpp:1017 #14 0x7fffed7f3688 in QWidget::event(QEvent*) (this=0x2133400, event=0x7fffb750) at kernel/qwidget.cpp:9045 #15 0x7fffed7aeb75 in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=this@entry=0x4e9e50, receiver=receiver@entry=0x2133400, e=e@entry=0x7fffb750) at kernel/qapplication.cpp:3640 #16 0x7fffed7b7456 in QApplication::notify(QObject*, QEvent*) (this=, receiver=0x2133400, e=0x7fffb750) at kernel/qapplication.cpp:3084 #17 0x7fffecab3d48 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x2133400, event=0x7fffb750) at kernel/qcoreapplication.cpp:1064 #18 0x7fffecab3f82 in QCoreApplication::sendSpontaneousEvent(QObject*, QEvent*) (receiver=, event=) at kernel/qcoreapplication.cpp:1474 #19 0x7fffed7b56a4 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) (receiver=receiver@entry=0x2133400, event=event@entry=0x7fffb750, alienWidget=, nativeWidget=0x1f5caa0, buttonDown=buttonDown@entry=0x7fffedd06330 , lastMouseReceiver=..., spontaneous=true, onlyDispatchEnterLeave=false) at kernel/qapplication.cpp:2622 #20 0x7fffed80d1a9 in QWidgetWindow::handleMouseEvent(QMouseEvent*) (this=this@entry=0x23efa50, event=event@entry=0x7fffba30) at kernel/qwidgetwindow.cpp:684 #21 0x7fffed81072f in QWidgetWindow::event(QEvent*) (this=0x23efa50, event=0x7fffba30) at kernel/qwidgetwindow.cpp:300 #22 0x7fffed7aeb75 in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x23efa50, e=0x7fffba30) at kernel/qapplication.cpp:3640 #23 0x7fffecab3d48 in QCoreApplication::notifyInternal2(QOb
[Elisa] [Bug 467265] Improvement: Current trackinfo not displayed when using a radio station
https://bugs.kde.org/show_bug.cgi?id=467265 Dave changed: What|Removed |Added CC||sunny.bed7...@fastmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmplot] [Bug 426025] kmplot crashed with any implicit functions include tangent
https://bugs.kde.org/show_bug.cgi?id=426025 --- Comment #11 from Dave Gilbert --- I've just created: https://invent.kde.org/education/kmplot/-/merge_requests/13 for this. It seems to clear the crash; I'm not 100% sure I understand all the details of that function though - but I think I'm just fixing it's list manipulation. (Note there are other problems with this program; like the fact that it refreshes the graph as you type and the smallest typo, or it refreshing as you type part of the equation can mean it takes minutes locking up X in that function to do the graph plotting) -- You are receiving this mail because: You are watching all bug changes.
[kmplot] [Bug 426025] kmplot crashed with any implicit functions include tangent
https://bugs.kde.org/show_bug.cgi?id=426025 --- Comment #9 from Dave Gilbert --- Unfortunately QMutableListIterator doesn't cope with growing the list either; so it needs a larger rework. -- You are receiving this mail because: You are watching all bug changes.
[kmplot] [Bug 426025] kmplot crashed with any implicit functions include tangent
https://bugs.kde.org/show_bug.cgi?id=426025 --- Comment #8 from Dave Gilbert --- Hmm the QMutableListIterator didn't work and I've not figured out why yet; the valgrind I'm looking at is: ==39870== Invalid read of size 8 ==39870==at 0x1DEF2D01: UnknownInlinedFun (qlist.h:153) ==39870==by 0x1DEF2D01: UnknownInlinedFun (qlist.h:313) ==39870==by 0x1DEF2D01: View::drawImplicit(Function*, QPainter*) (view.cpp:1168) ==39870==by 0x1DEF997D: View::draw(QPaintDevice*, View::PlotMedium) [clone .part.0] (view.cpp:363) ==39870==by 0x1DEE62D4: UnknownInlinedFun (view.cpp:2637) ==39870==by 0x1DEE62D4: View::drawPlot() (view.cpp:2636) ==39870==by 0x1DED4129: FunctionEditor::saveImplicit() (functioneditor.cpp:639) ==39870==by 0x5E5DE95: call (qobjectdefs_impl.h:398) ==39870==by 0x5E5DE95: void doActivate(QObject*, int, void**) (qobject.cpp:3923) ==39870==by 0x5E6121D: QTimer::timeout(QTimer::QPrivateSignal) (moc_qtimer.cpp:205) ==39870==by 0x5E54FC4: QObject::event(QEvent*) (qobject.cpp:1369) ==39870==by 0x4FA2D61: QApplicationPrivate::notify_helper(QObject*, QEvent*) (qapplication.cpp:3640) ==39870==by 0x5E2A4E7: QCoreApplication::notifyInternal2(QObject*, QEvent*) (qcoreapplication.cpp:1064) ==39870==by 0x5E7A980: QTimerInfoList::activateTimers() (qtimerinfo_unix.cpp:643) ==39870==by 0x5E7B25B: timerSourceDispatch(_GSource*, int (*)(void*), void*) (qeventdispatcher_glib.cpp:183) ==39870==by 0x78C2C7E: UnknownInlinedFun (gmain.c:3454) ==39870==by 0x78C2C7E: g_main_context_dispatch (gmain.c:4172) ==39870== Address 0x2d53d948 is 40 bytes inside a block of size 120 free'd ==39870==at 0x48486AF: realloc (vg_replace_malloc.c:1451) ==39870==by 0x5CB2156: QListData::realloc_grow(int) (qlist.cpp:170) ==39870==by 0x5CB2201: QListData::append(int) (qlist.cpp:196) ==39870==by 0x1DEF507C: UnknownInlinedFun (qlist.h:632) ==39870==by 0x1DEF507C: QList::append(QPointF const&) (qlist.h:620) ==39870==by 0x1DEEC03F: UnknownInlinedFun (qlist.h:402) ==39870==by 0x1DEEC03F: View::drawImplicitInSquare(Plot const&, QPainter*, double, double, QFlags, QList*) (view.cpp:1358) ==39870==by 0x1DEF33D5: View::drawImplicit(Function*, QPainter*) (view.cpp:1199) ==39870==by 0x1DEF997D: View::draw(QPaintDevice*, View::PlotMedium) [clone .part.0] (view.cpp:363) ==39870==by 0x1DEE62D4: UnknownInlinedFun (view.cpp:2637) ==39870==by 0x1DEE62D4: View::drawPlot() (view.cpp:2636) ==39870==by 0x1DED4129: FunctionEditor::saveImplicit() (functioneditor.cpp:639) ==39870==by 0x5E5DE95: call (qobjectdefs_impl.h:398) ==39870==by 0x5E5DE95: void doActivate(QObject*, int, void**) (qobject.cpp:3923) ==39870==by 0x5E6121D: QTimer::timeout(QTimer::QPrivateSignal) (moc_qtimer.cpp:205) ==39870==by 0x5E54FC4: QObject::event(QEvent*) (qobject.cpp:1369) ==39870== Block was alloc'd at ==39870==at 0x484386F: malloc (vg_replace_malloc.c:393) ==39870==by 0x5CB207F: QListData::detach(int) (qlist.cpp:137) ==39870==by 0x1DEF3D0E: UnknownInlinedFun (qlist.h:833) ==39870==by 0x1DEF3D0E: UnknownInlinedFun (qlist.h:613) ==39870==by 0x1DEF3D0E: UnknownInlinedFun (qmap.h:1028) ==39870==by 0x1DEF3D0E: View::drawImplicit(Function*, QPainter*) (view.cpp:1166) ==39870==by 0x1DEF997D: View::draw(QPaintDevice*, View::PlotMedium) [clone .part.0] (view.cpp:363) ==39870==by 0x1DEE62D4: UnknownInlinedFun (view.cpp:2637) ==39870==by 0x1DEE62D4: View::drawPlot() (view.cpp:2636) ==39870==by 0x1DED4129: FunctionEditor::saveImplicit() (functioneditor.cpp:639) ==39870==by 0x5E5DE95: call (qobjectdefs_impl.h:398) ==39870==by 0x5E5DE95: void doActivate(QObject*, int, void**) (qobject.cpp:3923) ==39870==by 0x5E6121D: QTimer::timeout(QTimer::QPrivateSignal) (moc_qtimer.cpp:205) ==39870==by 0x5E54FC4: QObject::event(QEvent*) (qobject.cpp:1369) ==39870==by 0x4FA2D61: QApplicationPrivate::notify_helper(QObject*, QEvent*) (qapplication.cpp:3640) ==39870==by 0x5E2A4E7: QCoreApplication::notifyInternal2(QObject*, QEvent*) (qcoreapplication.cpp:1064) ==39870==by 0x5E7A980: QTimerInfoList::activateTimers() (qtimerinfo_unix.cpp:643) ==39870== -- You are receiving this mail because: You are watching all bug changes.
[kmplot] [Bug 426025] kmplot crashed with any implicit functions include tangent
https://bugs.kde.org/show_bug.cgi?id=426025 --- Comment #7 from Dave Gilbert --- I think I kind of understand what's going on, but not 100% and hmm. void View::drawImplicit(Function *function, QPainter *painter) { QList singular; ... for (const QPointF : qAsConst(singular)) { ... for (double t : qAsConst(roots)) { double x = point.x() + epsilon * lcos(t); double y = point.y() + epsilon * lsin(t); drawImplicitInSquare(plot, painter, x, y, {}, ); } so, 'singular' - which I think is a list being walked in the outer for, gets modified by 'drawImplicitInSquare' in a corner case - which I think is the fact tan is not-contiguous. I think turning that loop into a QMutableListIterator might work. -- You are receiving this mail because: You are watching all bug changes.
[kmplot] [Bug 435186] KmPlot crashes when trying to plot an implicit function
https://bugs.kde.org/show_bug.cgi?id=435186 Dave Gilbert changed: What|Removed |Added CC||gilbertd+...@treblig.org --- Comment #2 from Dave Gilbert --- This looks the same as 426025 to me -- You are receiving this mail because: You are watching all bug changes.
[kmplot] [Bug 426025] kmplot crashed with any implicit functions include tangent
https://bugs.kde.org/show_bug.cgi?id=426025 Dave Gilbert changed: What|Removed |Added CC||gilbertd+...@treblig.org --- Comment #6 from Dave Gilbert --- still happens on current head ( a89ed5ddfea2ac96cfdce2bc4d1b49f268065edd ) - that pointer value is obviously complete garbage: #0 0x7fffdd0d6e1d in Parser::number(double) (value=Python Exception : Cannot access memory at address 0x34003600360031 looks like someone is writing ascii where a pointer should be. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 466425] Okular crashes when opening a faulty file
https://bugs.kde.org/show_bug.cgi?id=466425 --- Comment #7 from Dave Gilbert --- This seems to be fixed by the set of fixes in: https://github.com/captn3m0/ebook-tools referenced from: https://sourceforge.net/p/ebook-tools/bugs/10/ heck, this library is old; it seems worth taking those fixes somehow, not sure how. Anyway, erm what do we do with this Okular bug? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 466425] Okular crashes when opening a faulty file
https://bugs.kde.org/show_bug.cgi?id=466425 --- Comment #6 from Dave Gilbert --- The 'einfo' program that uses the same library crashes in the same way, so I'm guessing it's the library. [dg@dalek build]$ gdb /usr/bin/einfo (gdb) r -p ~/bugs/okular-466425-epubcrash/faulty_file.epub ... Program received signal SIGSEGV, Segmentation fault. __strcmp_avx2 () at ../sysdeps/x86_64/multiarch/strcmp-avx2.S:287 287 CMP_R1_S2_ymm (%ymm0, (%rsi), %ymm2, %ymm1) (gdb) where #0 __strcmp_avx2 () at ../sysdeps/x86_64/multiarch/strcmp-avx2.S:287 #1 0x77f94068 in FindNode (List=0xf9a0, Data=Data@entry=0x7fffdc40) at /usr/src/debug/ebook-tools-0.2.2-23.fc37.x86_64/src/libepub/linklist.c:116 #2 0x77f94239 in _opf_manifest_get_by_id (opf=, id=) at /usr/src/debug/ebook-tools-0.2.2-23.fc37.x86_64/src/libepub/opf.c:767 #3 0x77f9428e in _get_spine_it_url (it=it@entry=0xfc40) at /usr/src/debug/ebook-tools-0.2.2-23.fc37.x86_64/src/libepub/epub.c:258 #4 0x77f94322 in epub_it_get_curr (it=0xfc40) at /usr/src/debug/ebook-tools-0.2.2-23.fc37.x86_64/src/libepub/epub.c:343 #5 0x5357 in main (argc=, argv=0x7fffde28) at /usr/src/debug/ebook-tools-0.2.2-23.fc37.x86_64/src/tools/einfo.c:122 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 466425] Okular crashes when opening a faulty file
https://bugs.kde.org/show_bug.cgi?id=466425 Dave Gilbert changed: What|Removed |Added CC||gilbertd+...@treblig.org --- Comment #5 from Dave Gilbert --- #0 __strcmp_avx2 () at ../sysdeps/x86_64/multiarch/strcmp-avx2.S:287 #1 0x7fffd02f5068 in FindNode (List=0x10f4490, Data=Data@entry=0x7fffbe30) at /usr/src/debug/ebook-tools-0.2.2-23.fc37.x86_64/src/libepub/linklist.c:116 Compare = #2 0x7fffd02f5239 in _opf_manifest_get_by_id (opf=, id=) at /usr/src/debug/ebook-tools-0.2.2-23.fc37.x86_64/src/libepub/opf.c:767 data = {nspace = 0x7fffbe50 "", modules = 0xfed0 , id = 0x0, href = 0x0, type = 0x0, fallback = 0x7fffe0c90526 "UH\211\345H\203\354@H\211}\330H\211uЉU\314f\017\357\300\017)E\340f\017\326E\360H\213E\320H\211\307\350\353,", fbStyle = 0x0} #3 0x7fffd02f528e in _get_spine_it_url (it=it@entry=0x10f4350) at /usr/src/debug/ebook-tools-0.2.2-23.fc37.x86_64/src/libepub/epub.c:258 tmp = data = 0x10ea070 #4 0x7fffd02f5322 in epub_it_get_curr (it=0x10f4350) at /usr/src/debug/ebook-tools-0.2.2-23.fc37.x86_64/src/libepub/epub.c:343 #5 0x7fffd232478a in Epub::Converter::convert(QString const&) (this=0x10d1450, fileName=...) at /discs/more/git/okular/generators/epub/converter.cpp:360 newDocument = 0x10d5530 _cursor = 0x10d6420 it = 0x10f4350 firstPage = false movieAnnots = {d = 0x75f6d240 } soundActions = {d = 0x75f6d240 } orig = {d = 0x9558c0, {data = {current_group = 0, resolve_mask = 1965951}, for_faster_swapping_dont_use = 31455216}} p = {d = 0x10c9580, {data = {current_group = 0, resolve_mask = 1965951}, for_faster_swapping_dont_use = 31455216}} videoSize = {wd = 320, ht = 240} __PRETTY_FUNCTION__ = "virtual QTextDocument* Epub::Converter::convert(const QString&)" tit = 0xff hit = {c = {{d = 0x10d28c8, e = 0x10d28c8}}, i = {i = 0x77fd85a2 <_dl_fixup+258>}, n = {i = 0x5}} #6 0x7fffe0d2478a in Okular::TextDocumentConverter::convertWithPassword(QString const&, QString const&) (this=0x10d1450, fileName=...) at /discs/more/git/okular/core/textdocumentgenerator.cpp:52 doc = 0x10d6cb0 #7 0x7fffe0d25890 in Okular::TextDocumentGenerator::loadDocumentWithPassword(QString const&, QVector&, QString const&) (this=0x10d6cb0, fileName=..., pagesVector=..., password=...) at /discs/more/git/okular/core/textdocumentgenerator.cpp:288 d = 0x98c0c0 openResult = Okular::Document::OpenSuccess linkInfos = {> = {}, {p = {static shared_null = {ref = {atomic = {_q_value = std::atomic = { -1 }}}, alloc = 0, begin = 0, end = 0, array = {0x0}}, d = 0x7fffc860}, d = 0x7fffc860}} annotationInfos = {> = {}, {p = {static shared_null = {ref = {atomic = {_q_value = std::atomic = { -1 }}}, alloc = 0, begin = 0, end = 0, array = {0x0}}, d = 0x7fffc858}, d = 0x7fffc858}} size = {wd = 566784540, ht = 1080302727} objects = {d = 0x7fffc9c0} annots = {d = 0x10c97e0} #8 0x7fffe0cc659e in Okular::DocumentPrivate::openDocumentInternal(KPluginMetaData const&, bool, QString const&, QByteArray const&, QString const&) (this=0x7465c0, offer=..., isstdin=false, docFile=..., filedata=..., password=...) at /discs/more/git/okular/core/document.cpp:943 propName = {d = 0x10d0c60} genIt = {i = 0x10da870} errorToOpenErrorConnection = {d_ptr = 0x10d1720} window = 0xe58a70 dpi = {wd = 157.06280193236714, ht = 160.89149560117301} __PRETTY_FUNCTION__ = "Okular::Document::OpenResult Okular::DocumentPrivate::openDocumentInternal(const KPluginMetaData&, bool, const QString&, const QByteArray&, const QString&)" openResult = Okular::Document::OpenError #9 0x7fffe0cd00c7 in Okular::Document::openDocument(QString const&, QUrl const&, QMimeType const&, QString const&) (this=0x7e08e0, docFile=..., url=..., _mime=..., password=...) at /discs/more/git/okular/core/document.cpp:2461 db = {d = 0x7616b380 <(anonymous namespace)::Q_QGS_staticQMimeDatabase::innerFunction()::holder>} mime = {d = {d = 0x10d1150}} filedata = {d = 0x75f6d240 } fd = -1 triedMimeFromFileContent = false __PRETTY_FUNCTION__ = "Okular::Document::OpenResult Okular::Document::openDocument(const QString&, const QUrl&, const QMimeType&, const QString&)" fromFileDescriptor = false offer = {m_metaData = {dead = 0x0, o = {d = 0xac9dd0}}, m_fileName = {d = 0xa89bc0}, d = {d = 0xab5720}} openResult = (Okular::Document::OpenError | Okular::Document::Op
[kate] [Bug 468413] New: Can not turn off text highlighting
https://bugs.kde.org/show_bug.cgi?id=468413 Bug ID: 468413 Summary: Can not turn off text highlighting Classification: Applications Product: kate Version: 22.12.3 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: dkol...@comcast.net 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 *** STEPS TO REPRODUCE 1. Open file with song lyrics (format is .txt or .pro) 2. File opens OBSERVED RESULT Any time the word "for" exists, it is made bold. EXPECTED RESULT NO bold text! I have set the Highlighting to NONE in the Tools menu, but when opening files, it always highlights the word "for" Enuf to drive one nuts. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 22.04.2 LTS (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Also have major problems with Krusader, keyboard action conflicts... related? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 468037] Form: 2 of the tick boxes don't work (UK IHT 400)
https://bugs.kde.org/show_bug.cgi?id=468037 --- Comment #3 from Dave Gilbert --- Yeh, not too sure what's going on here. 44 and 45 look like all the others to me in the raw PDF - although I can't say I fully understand the syntax yet; they both have an '/Off' and '/Yes' in the /N and /D sections. 48a and 48b (objects 2416/2417) both do it differently with the buttons in children, and have 4 children, two 'No/Off' pairs and two 'Off/Yes' pairs - which doesn't make any sense to me since they only seem to have tow buttons each. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 468036] Form: NaN in form total (UK IHT 411)
https://bugs.kde.org/show_bug.cgi?id=468036 Dave Gilbert changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #4 from Dave Gilbert --- OK, fix incoming; it's just that we're missing a definition of valueAsString -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 468036] Form: NaN in form total (UK IHT 411)
https://bugs.kde.org/show_bug.cgi?id=468036 --- Comment #3 from Dave Gilbert --- I'm seeing a few scripts that run, the two that produce NaN are: -- //set values in boxes to variable\r\nvar tot = this.getField(\"Grand_Total_stock_1\");\r\nvar tot1 = Number(this.getField(\"Total_1\").valueAsString);\r\nvar tot2 = Number(this.getField(\"Total_2\").valueAsString);\r\nvar tot3 = Number(this.getField(\"Total_3\").valueAsString);\r\nvar tot4 = Number(this.getField(\"Total_4\").valueAsString);\r\nvar tot5 = Number(this.getField(\"Total_5\").valueAsString);\r\nvar tot6 = Number(this.getField(\"Total_6\").valueAsString);\r\nvar tot7 = Number(this.getField(\"Total_7\").valueAsString);\r\n\r\n//set an array of above variables\r\nvar arrTotal =[tot1, tot2, tot3, tot4, tot5, tot6, tot7];\r\n\r\n//loop through variables to add\r\nvar result = 0;\r\nfor (i=0; i < arrTotal.length; i++)\r\n{\r\nresult += arrTotal[i]\r\n };\r\n\r\n//place total of array loop in total box\r\ntot.value = result;\r\n\r\n//if(tot.value == 0){\r\n//tot.value = \"\";\r\n//};\r\n //set values in boxes to variable var tot = this.getField(\"Grand_Total_stock_1\"); var tot1 = Number(this.getField(\"Total_1\").valueAsString); var tot2 = Number(this.getField(\"Total_2\").valueAsString); var tot3 = Number(this.getField(\"Total_3\").valueAsString); var tot4 = Number(this.getField(\"Total_4\").valueAsString); var tot5 = Number(this.getField(\"Total_5\").valueAsString); var tot6 = Number(this.getField(\"Total_6\").valueAsString); var tot7 = Number(this.getField(\"Total_7\").valueAsString); //set an array of above variables var arrTotal =[tot1, tot2, tot3, tot4, tot5, tot6, tot7]; //loop through variables to add var result = 0; for (i=0; i < arrTotal.length; i++) { result += arrTotal[i] }; //place total of array loop in total box tot.value = result; //if(tot.value == 0){ //tot.value = \"\"; //}; -- //set values in boxes to variable\r\nvar totStk = this.getField(\"Grand_total_stock_2\");\r\nvar totStk1 = Number(this.getField(\"Total_stock_1\").valueAsString);\r\nvar totStk2 = Number(this.getField(\"Total_stock_2\").valueAsString);\r\nvar totStk3 = Number(this.getField(\"Total_stock_3\").valueAsString);\r\nvar totStk4 = Number(this.getField(\"Total_stock_4\").valueAsString);\r\nvar totStk5 = Number(this.getField(\"Total_stock_5\").valueAsString);\r\nvar totStk6 = Number(this.getField(\"Total_stock_6\").valueAsString);\r\nvar totStk7 = Number(this.getField(\"Total_stock_7\").valueAsString);\r\nvar totStk8 = Number(this.getField(\"Total_stock_8\").valueAsString);\r\nvar totStk9 = Number(this.getField(\"Total_stock_9\").valueAsString);\r\nvar totStk10 = Number(this.getField(\"Total_stock_10\").valueAsString);\r\nvar totStk11 = Number(this.getField(\"Total_stock_11\").valueAsString);\r\nvar totStk12 = Number(this.getField(\"Total_stock_12\").valueAsString);\r\nvar totStk13 = Number(this.getField(\"Total_stock_13\").valueAsString);\r\nvar totStk14 = Number(this.getField(\"Total_stock_14\").valueAsString);\r\n\r\n//set an array of above variables\r\nvar arrTotalStk =[totStk1, totStk2, totStk3, totStk4, totStk5, totStk6, totStk7, totStk8, totStk9, totStk10, totStk11, totStk12, totStk13, totStk14];\r\n\r\n//loop through variables to add\r\nvar resultStk = 0;\r\nfor (i=0; i < arrTotalStk.length; i++)\r\n{\r\nresultStk += arrTotalStk[i]\r\n}\r\n\r\n//place total of array loop in total box\r\ntotStk.value = resultStk;\r\n\r\n//if(totStk.value == 0){\r\n//totStk.value = \"\";\r\n//}; //set values in boxes to variable var totStk = this.getField(\"Grand_total_stock_2\"); var totStk1 = Number(this.getField(\"Total_stock_1\").valueAsString); var totStk2 = Number(this.getField(\"Total_stock_2\").valueAsString); var totStk3 = Number(this.getField(\"Total_stock_3\").valueAsString); var totStk4 = Number(this.getField(\"Total_stock_4\").valueAsString); var totStk5 = Number(this.getField(\"Total_stock_5\").valueAsString); var totStk6 = Number(this.getField(\"Total_stock_6\").valueAsString); var totStk7 = Number(this.getField(\"Total_stock_7\").valueAsString); var totStk8 = Number(this.getField(\"Total_stock_8\").valueAsString); var totStk9 = Number(this.getField(\"Total_stock_9\").valueAsString); var totStk10 = Number(this.getField(\"Total_stock_10\").valueAsString); var totStk11 = Number(this.getField(\"Total_stock_11\").valueAsString); var totStk12 = Numb
[krusader] [Bug 468101] There are two actions (Quit, Close Current Tab) that want to use the same shortcut (Esc).
https://bugs.kde.org/show_bug.cgi?id=468101 Dave Kolars changed: What|Removed |Added CC||dkol...@comcast.net -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 468101] New: There are two actions (Quit, Close Current Tab) that want to use the same shortcut (Esc).
https://bugs.kde.org/show_bug.cgi?id=468101 Bug ID: 468101 Summary: There are two actions (Quit, Close Current Tab) that want to use the same shortcut (Esc). Classification: Applications Product: krusader Version: 2.7.2 Platform: PCLinuxOS OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: shortcuts Assignee: krusader-bugs-n...@kde.org Reporter: dkol...@comcast.net CC: krusader-bugs-n...@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 *** STEPS TO REPRODUCE 1. Select a .txt (or .csv, .pdf, etc) file in a panel 2. Press F3 to view contents or F4 to edit OBSERVED RESULT 1. Error message appears 2. Closing error message allows file to open for viewing or editing EXPECTED RESULT File should open with no error message. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 4:5.24.4-0ubuntu1 (?) (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Deleting the shortcut from either of the conflicts does not solve the problem. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 468036] Form: NaN in form total (UK IHT 411)
https://bugs.kde.org/show_bug.cgi?id=468036 --- Comment #2 from Dave Gilbert --- For anyone desperately looking to work around this, Chromium doesn't NaN -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 468037] Form: 2 of the tick boxes don't work (UK IHT 400)
https://bugs.kde.org/show_bug.cgi?id=468037 --- Comment #1 from Dave Gilbert --- This *might* be a form bug; it's pretty consistent across Okular, evince and Chromium. (Chromium is slightly different, it gives the tick boxes a default of No which makes it easier to avoid) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 468037] New: Form: 2 of the tick boxes don't work (UK IHT 400)
https://bugs.kde.org/show_bug.cgi?id=468037 Bug ID: 468037 Summary: Form: 2 of the tick boxes don't work (UK IHT 400) Classification: Applications Product: okular Version: 22.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: gilbertd+...@treblig.org Target Milestone: --- Created attachment 157770 --> https://bugs.kde.org/attachment.cgi?id=157770=edit UK IHT 400 form SUMMARY In the UK form IHT 400 (included) there are many many tick boxes; most of them work fine, except 44 and 45, which instead change boxes 48a and 48b. https://www.gov.uk/government/publications/inheritance-tax-inheritance-tax-account-iht400 STEPS TO REPRODUCE 1. Click on the No/Yes boxes for 44 or 45 on page 6 OBSERVED RESULT The ticks appear in boxes 48a and 48b EXPECTED RESULT The ticks appear in the box you tick 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.
[okular] [Bug 468036] Form: NaN in form total (UK IHT 411)
https://bugs.kde.org/show_bug.cgi?id=468036 --- Comment #1 from Dave Gilbert --- Created attachment 157769 --> https://bugs.kde.org/attachment.cgi?id=157769=edit Verison of IHT411 with dummy £1 value filled in -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 468036] New: Form: NaN in form total (UK IHT 411)
https://bugs.kde.org/show_bug.cgi?id=468036 Bug ID: 468036 Summary: Form: NaN in form total (UK IHT 411) Classification: Applications Product: okular Version: 22.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: gilbertd+...@treblig.org Target Milestone: --- Created attachment 157768 --> https://bugs.kde.org/attachment.cgi?id=157768=edit Original IHT411 form unfilled SUMMARY The UK Gov form IHT411 (copy enclosed), has a pair of 'Totals' columns, while they correctly start out at £0.00, as soon as you enter any value they change into £NaN The forms come from: https://www.gov.uk/government/publications/inheritance-tax-listed-stocks-and-shares-iht411 STEPS TO REPRODUCE 1. Load the original form, see the 'Total value of stock at date of death' is £0.00 on both pages 2. Enter 1 into amount of stock held, and £1.00 in Market price at death OBSERVED RESULT Both 'total value of stock' columns display NaN EXPECTED RESULT The actual total of those columns 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.
[okular] [Bug 467852] Form: Numbers concatenated rather than summed (UK IHT407)
https://bugs.kde.org/show_bug.cgi?id=467852 --- Comment #1 from Dave Gilbert --- Created attachment 157631 --> https://bugs.kde.org/attachment.cgi?id=157631=edit IHT407 with dummy values filled as per the bug report -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 467852] New: Form: Numbers concatenated rather than summed (UK IHT407)
https://bugs.kde.org/show_bug.cgi?id=467852 Bug ID: 467852 Summary: Form: Numbers concatenated rather than summed (UK IHT407) Classification: Applications Product: okular Version: 22.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: gilbertd+...@treblig.org Target Milestone: --- Created attachment 157630 --> https://bugs.kde.org/attachment.cgi?id=157630=edit Original IHT407 form unfilled SUMMARY In the attached (government issued) form, the summation of fields is working as concatenation rather than summing the values. The original form is available: https://www.gov.uk/government/publications/inheritance-tax-household-and-personal-goods-iht407 I've attached: a) An original version b) A version with a value in the first entry in page 2 of £300, top row, and you can see the total field at the bottom has a load of 0's that correspond to each row adding an extra '0' to the result; this carries into the total on the next page STEPS TO REPRODUCE 1. Load the empty form 2. Enter a numeric value, e.g. 300, into the top right field on page 2 (Open market value, top row) 3. Enter another numeric value, e.g. 55 into the page 4 field 4, 'Total value of other' OBSERVED RESULT The total on page 2 is 300 The total on page 5 is something like 30055 EXPECTED RESULT £300 and £355 SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 37 (available in About System) KDE Plasma Version: 5.27.3 - but running under xfce KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION I've seen a non-reproducible crash on that form and other oddities, try tabbing around on page 2 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 466024] New: Export/Print shold be called Print/Export
https://bugs.kde.org/show_bug.cgi?id=466024 Bug ID: 466024 Summary: Export/Print shold be called Print/Export Classification: Applications Product: kate Version: 22.08.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: cliffor...@gmail.com Target Milestone: --- SUMMARY I find it an issue to hunt for the print (file) option all the time when my brain is looking for Print and not Export/Print. Please consider renaming the option to Print/Export or split them. It is frustrating to search for the option all the time! It is a two-step process to go to another window to select the print option. I know the letter 'E' comes before 'P' in the english alphabet, but printing is way more useful and used than the Export function. STEPS TO REPRODUCE 1. it's there all the time as an option 2. select export/print, then print OBSERVED RESULT 2 step works EXPECTED RESULT one step works SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 22.10 (available in About System) KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358277] Chrome apps assuming same icon from chrome browser, in Icon-Only Task Manager
https://bugs.kde.org/show_bug.cgi?id=358277 --- Comment #40 from Dave Morley --- Confirmed. Running chrome://flags searching for wayland and enabling the 2 flags and restart chrome, means that the app opens correctly. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 428765] Konsole custom profile not staying default
https://bugs.kde.org/show_bug.cgi?id=428765 Dave Brain changed: What|Removed |Added CC||k...@gregwalker.me.uk -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 464515] Plasma notification setting not honoured
https://bugs.kde.org/show_bug.cgi?id=464515 Dave Brain changed: What|Removed |Added CC||k...@gregwalker.me.uk -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 464515] New: Plasma notification setting not honoured
https://bugs.kde.org/show_bug.cgi?id=464515 Bug ID: 464515 Summary: Plasma notification setting not honoured Classification: Applications Product: Spectacle Version: 21.12.3 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: k...@gregwalker.me.uk CC: k...@david-redondo.de Target Milestone: --- SUMMARY ***l My notification pop-up timeout is set for 1second. Taking a screenshot with spectacle I expect the pop up to be removed after 1 second. The pop up stays for 5 seconds which is the default for the notification. reboot/restart of KDE/Plasma makes no difference *** STEPS TO REPRODUCE 1. Set notification timeout to any value . e.g. from the default of 5S to 1S 2. Take a screenshot with spectacle 3. Screen shot takes as expected 4. notification remains on screen for 5 seconds regardless of the time out set in notification settings OBSERVED RESULT notification remains on screen for 5 seconds regardless of the time out set in notification settings EXPECTED RESULT notification should stay on screen for the value input into the notification timeout. ie.e 1second SOFTWARE/OS VERSIONS Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-58-generic (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz Memory: 7.5 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 463672] Dragging to move files between windows only works once
https://bugs.kde.org/show_bug.cgi?id=463672 --- Comment #5 from Dave Lyon --- and btw, the behavior does not happen while moving within the same window, dragging to a subfolder etc.- only between two dolphin windows -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 463672] Dragging to move files between windows only works once
https://bugs.kde.org/show_bug.cgi?id=463672 Dave Lyon changed: What|Removed |Added CC||d...@tuxrocket.com Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #4 from Dave Lyon --- This is happening for me as well. I'm on Fedora 36 (plasma kde spin). This started relatively recently. I'm happy to provide any info you need. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 463671] MacOS Apple Silicon versions needed, only Intel available and it won't Rosetta
https://bugs.kde.org/show_bug.cgi?id=463671 --- Comment #1 from Dave Hamby --- Probably 2 problems here. Need to add option to build universal binaries to Mac build options. Second issue with the image itself. Perhaps damaged. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 463671] New: MacOS Apple Silicon versions needed, only Intel available and it won't Rosetta
https://bugs.kde.org/show_bug.cgi?id=463671 Bug ID: 463671 Summary: MacOS Apple Silicon versions needed, only Intel available and it won't Rosetta Classification: Applications Product: kdenlive Version: unspecified Platform: Other OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: Installation Assignee: j...@kdenlive.org Reporter: daveha...@protonmail.com 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 *** MacOS runtime loader is unable to verify the available Intel image authenticity. Suggests MacOS developer credentials are out of date or an outdated build system was used. STEPS TO REPRODUCE 1. Download KDENlive from the product website selecting Apple Intel version (No Apple Silicon version) 2. Drag to Applications 3. Attempt to launch in Finder or Spotlight https://download.kde.org/stable/kdenlive/22.12/macOS/kdenlive-22.12.0.dmg is NFG OBSERVED RESULT Launch failure as shown in the attachment window image EXPECTED RESULT Some Rosetta 2 chugging to M1 the image, it loads and starts, and KDENlive runs OK. SOFTWARE/OS VERSIONS Windows: macOS: Ventura 13.1 Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Apple Silicon M1 iMac KDENlive 22.12 Identified Developer Built 12/10/22 -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 184015] wrong 'ignore all' action on spell checker
https://bugs.kde.org/show_bug.cgi?id=184015 Dave Gilbert changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #5 from Dave Gilbert --- This is still failing for me on kopete-22.08.3-2.fc37.x86_64 kate-22.08.3-1.fc37.x86_64 Hitting the 'ignore all' button is copying the file into .hunspell_en_AG here. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 461726] The application list in the Plasma Firewall "Add rule" dialog is broken, nothing is shown
https://bugs.kde.org/show_bug.cgi?id=461726 Dave Morley changed: What|Removed |Added CC||davm...@davmor2.co.uk -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 462825] New: Rename tool combobox history not saving in version 7.90
https://bugs.kde.org/show_bug.cgi?id=462825 Bug ID: 462825 Summary: Rename tool combobox history not saving in version 7.90 Classification: Applications Product: digikam Version: 7.9.0 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: AdvancedRename-dialog Assignee: digikam-bugs-n...@kde.org Reporter: digikambugtrack...@helmet.anonaddy.com Target Milestone: --- Created attachment 154463 --> https://bugs.kde.org/attachment.cgi?id=154463=edit In screenshot _2 should appear in dropdown history as i previously renamed some files by appending _2 to the filename. SUMMARY *** Rename history is not saved in the dropdown combo box. I still show history from renames I did in version 7.8.0 however when I do new renames now, it is not saved in the history dropdown box for easy retrieval when I want to use the same rename template later. *** STEPS TO REPRODUCE 1. Select an image 2. Rename the image using the rename tool (F2) 3. Close the rename window 4. select and image 5. Rename using the image rename tool (F2) 6. Drop down the history dropdown to find the rename template you used in step 2 7. The history is not there for your rename from step 2, other rename history is there however, possibly from renames done in previous version of Digikam OBSERVED RESULT No rename history is saved and presented in the dropdown list EXPECTED RESULT Should be able to drop down the history dropdown box and recall previous renames used when renaming previous images. I believe that 20 rename history templates are supposed to be stored. SOFTWARE/OS VERSIONS Windows: 11 Pro 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.
[knights] [Bug 453178] Bad URL to register an acount at freechess.org
https://bugs.kde.org/show_bug.cgi?id=453178 Dave Kaye changed: What|Removed |Added CC||d...@linuxmail.org Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #3 from Dave Kaye --- Knights is programmed to send the user to the url http://freechess.org/Register/index.html when requesting a new account. The FreeChess website has changed from http to https. When the above url is recieved by the chess website, it sends a redirect response. Unfortunately it is malformed, and the redirect is to the url https://www.freechess.orgregister/index.html which does not exist. Correcting the issue at the website will correct this error. A note has been sent to supp...@freechess.org to inform them of the problem. A second method to correct this error is to change Knights ficsdialog.cpp from requesting http: to requesting https: by adding an "s" to the code. This is the correct url, and the malformed redirect url is never issued. This has been done in pull request labeled Commit 93002685. This change is awaiting acceptance by development team. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 462641] New: sempre più bug a caso
https://bugs.kde.org/show_bug.cgi?id=462641 Bug ID: 462641 Summary: sempre più bug a caso Classification: Applications Product: kdeconnect Version: 22.08.2 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: davefaganell...@protonmail.com Target Milestone: --- Application: kdeconnectd (22.08.2) (Compiled from sources) Qt Version: 5.15.6 Frameworks Version: 5.98.0 Operating System: Linux 5.19.0-26-generic x86_64 Windowing System: X11 Distribution: Ubuntu 22.10 DrKonqi: 5.25.5 [KCrashBackend] -- Information about the crash: non conosco bene cosa sia successo però a caso anche mentre faccio ricerche su internet mi vengono errori a caso The crash can be reproduced sometimes. -- Backtrace: Application: Demone di KDE Connect (kdeconnectd), signal: Segmentation fault [KCrash Handler] #4 0x7f0de06e45fe in QObjectPrivate::addConnection(int, QObjectPrivate::Connection*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f0de06e8d92 in QObjectPrivate::connectImpl(QObject const*, int, QObject const*, void**, QtPrivate::QSlotObjectBase*, Qt::ConnectionType, int const*, QMetaObject const*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f0de06e9205 in QObject::connectImpl(QObject const*, void**, QObject const*, void**, QtPrivate::QSlotObjectBase*, Qt::ConnectionType, int const*, QMetaObject const*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f0dd81f5496 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/kdeconnect/kdeconnect_notifications.so #8 0x7f0dd81f5e04 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/kdeconnect/kdeconnect_notifications.so #9 0x7f0de1dcce20 in Device::privateReceivedPacket(NetworkPacket const&) () from /lib/x86_64-linux-gnu/libkdeconnectcore.so.22 #10 0x7f0de06f36ff in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f0de1dbd921 in LanDeviceLink::dataReceived() () from /lib/x86_64-linux-gnu/libkdeconnectcore.so.22 #12 0x7f0de06f36ff in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f0de1db609d in SocketLineReader::dataReceived() () from /lib/x86_64-linux-gnu/libkdeconnectcore.so.22 #14 0x7f0de06f36ff in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f0ddff8dbc5 in ?? () from /lib/x86_64-linux-gnu/libQt5Network.so.5 #16 0x7f0de06f372c in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7f0ddff3cbe7 in ?? () from /lib/x86_64-linux-gnu/libQt5Network.so.5 #18 0x7f0ddff4f809 in ?? () from /lib/x86_64-linux-gnu/libQt5Network.so.5 #19 0x7f0de136bf32 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x7f0de06bae38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7f0de0715695 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7f0dded224f9 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #23 0x7f0dded77228 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #24 0x7f0dded1fcb0 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #25 0x7f0de0714aea in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x7f0de06b97cb in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x7f0de06c1c2a in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #28 0x5573acd950f6 in ?? () #29 0x7f0ddfc23510 in __libc_start_call_main (main=main@entry=0x5573acd94bf0, argc=argc@entry=1, argv=argv@entry=0x7fff1d365fb8) at ../sysdeps/nptl/libc_start_call_main.h:58 #30 0x7f0ddfc235c9 in __libc_start_main_impl (main=0x5573acd94bf0, argc=1, argv=0x7fff1d365fb8, init=, fini=, rtld_fini=, stack_end=0x7fff1d365fa8) at ../csu/libc-start.c:381 #31 0x5573acd95315 in _start () [Inferior 1 (process 1366) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 445862] konsole: unclean shutdown/broken session restore
https://bugs.kde.org/show_bug.cgi?id=445862 --- Comment #2 from Dave Flogeras --- I found a workaround, at least for my specific machine. It seems like on this machine, when I set up my konsole keyboard shortcut, I just assigned a key-combo to the shortcut under Session->Shortcuts->Custom Shortcuts->KMenuEdit->Konsole->Trigger. This shortcut I think is created by default. On other machines, I made a new custom group, then added a newly created shortcut by clicking edit->new->global shortcut->command/url and filling it in. What I notice is that if you go into /proc/`pidof ksmserver/fd and inspect the open files, starting console with the first shortcut does not seem to notify ksmserver of its presence, but using the "from scratch" shortcut seems to make a new socket to ksmserver for each konsole. I guess if konsole doesn't tell ksmserver about itself it cannot be queried for session management at logout. Not sure of the how or why, but it seems to fix/work around the issue here. I am also sure this used to work, and I only set the short cut up when I bought the laptop nearly three years ago. Hope it helps someone else get un-stuck. -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 461747] Crash after setting an account
https://bugs.kde.org/show_bug.cgi?id=461747 Dave Morley changed: What|Removed |Added CC||davm...@davmor2.co.uk --- Comment #3 from Dave Morley --- Created attachment 154055 --> https://bugs.kde.org/attachment.cgi?id=154055=edit Tokodon crash Confirmed I have the issue once the account is setup and the app has been closed once it will then not open again. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 338796] Blank the screen using Esc key while on the lock screen
https://bugs.kde.org/show_bug.cgi?id=338796 --- Comment #12 from Dave Gilbert --- Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456511] VLC and Firefox freeze / stop updating their window contents after being used for a while
https://bugs.kde.org/show_bug.cgi?id=456511 --- Comment #39 from Dave Lane --- (In reply to Dave Lane from comment #38) > AMD graphics card (Radeon RX 550) and am running kernel Oops - should be RX 5500 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456511] VLC and Firefox freeze / stop updating their window contents after being used for a while
https://bugs.kde.org/show_bug.cgi?id=456511 --- Comment #38 from Dave Lane --- Since installing 5.26 a few days ago, I have not seen the issue. I've got an AMD graphics card (Radeon RX 550) and am running kernel 5.19.14-051914-generic. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 427610] Konsole manages its own window position even when forcing KWin to manage window placement
https://bugs.kde.org/show_bug.cgi?id=427610 Dave changed: What|Removed |Added CC||d...@decent.cz -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 459834] Since the last update with Floating Panel enabled on Wayland Session the widget windows nolonger line up with their ICON
https://bugs.kde.org/show_bug.cgi?id=459834 --- Comment #2 from Dave Morley --- Created attachment 152506 --> https://bugs.kde.org/attachment.cgi?id=152506=edit Clipboard contents -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 459834] Since the last update with Floating Panel enabled on Wayland Session the widget windows nolonger line up with their ICON
https://bugs.kde.org/show_bug.cgi?id=459834 --- Comment #1 from Dave Morley --- Created attachment 152505 --> https://bugs.kde.org/attachment.cgi?id=152505=edit Panel options -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 459834] New: Since the last update with Floating Panel enabled on Wayland Session the widget windows nolonger line up with their ICON
https://bugs.kde.org/show_bug.cgi?id=459834 Bug ID: 459834 Summary: Since the last update with Floating Panel enabled on Wayland Session the widget windows nolonger line up with their ICON Classification: Plasma Product: plasmashell Version: 5.25.5 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: davm...@davmor2.co.uk CC: niccolo.venera...@gmail.com Target Milestone: 1.0 Created attachment 152504 --> https://bugs.kde.org/attachment.cgi?id=152504=edit Application Launcher open SUMMARY Set up a session to be wayland, set the panel to be floating in either expanded mode (full screen app open) or floating mode the widgets nolonger map to the icon that opened them STEPS TO REPRODUCE 1. Boot in to the desktop 2. Open the application launcher OBSERVED RESULT Widget opens in the middle of the panel EXPECTED RESULT Widget opens above the icon on the left of the panel SOFTWARE/OS VERSIONS Operating System: KDE neon 5.25 KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 5.15.0-48-generic (64-bit) Graphics Platform: Wayland Processors: 8 × AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx Memory: 9.7 GiB of RAM Graphics Processor: AMD Radeon™ Vega 10 Graphics Manufacturer: LENOVO Product Name: 81NC System Version: Lenovo IdeaPad S340-15API -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456511] VLC and Firefox freeze / stop updating their window contents after being used for a while
https://bugs.kde.org/show_bug.cgi?id=456511 --- Comment #11 from Dave Lane --- Oops - and I should say I'm running Plasma 5.25.4 and KDE Frameworks 5.97.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456511] VLC and Firefox freeze / stop updating their window contents after being used for a while
https://bugs.kde.org/show_bug.cgi?id=456511 Dave Lane changed: What|Removed |Added CC||d...@davelane.nz --- Comment #10 from Dave Lane --- I seem to be experiencing the same problem - have Firefox running with several windows, lots of tabs (hundreds) using the vertical "tree tabs" extension, and after a while, sometimes many hours, a FF windows starts flickering between two static frames - especially on, say, videos playing or video conference video (e.g. BigBlueButton) - and the refresh of all the FF windows stops updating unless I move/resize the window, and then it just redraws once before freezing again... Running KDE Neon 20.04 on an AMD CPU desktop machine (with X11 and AMD graphics, and 5.19.5 kernel). This problem has happened with other kernels. Haven't tried a non-plasma desktop for a while, so can't remember it happening on one, but I might be wrong. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 457028] Profiles are not saved correctly
https://bugs.kde.org/show_bug.cgi?id=457028 Dave changed: What|Removed |Added CC||fishnet37...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 458518] Some Google Calendar events are not displayed in KOrganizer or Kalendar; Events confirmed to exist in Akonadi Console
https://bugs.kde.org/show_bug.cgi?id=458518 --- Comment #5 from Dave Connett --- I found some bugs that look related, without knowing the root cause: I am not sure if they are they same bug. Here is a list: https://bugs.kde.org/show_bug.cgi?id=334569 https://bugs.kde.org/show_bug.cgi?id=366511 https://bugs.kde.org/show_bug.cgi?id=418811 https://bugs.kde.org/show_bug.cgi?id=447966 https://bugs.kde.org/show_bug.cgi?id=416660 https://bugs.kde.org/show_bug.cgi?id=415145 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 334569] KOrganizer not syncing properly with modified repeated events in google calendar
https://bugs.kde.org/show_bug.cgi?id=334569 Dave Connett changed: What|Removed |Added CC||dave.conn...@gmail.com --- Comment #18 from Dave Connett --- I found some bugs that look related, without knowing the root cause: I am not sure if they are they same bug. Here is a list: https://bugs.kde.org/show_bug.cgi?id=334569 https://bugs.kde.org/show_bug.cgi?id=366511 https://bugs.kde.org/show_bug.cgi?id=418811 https://bugs.kde.org/show_bug.cgi?id=447966 https://bugs.kde.org/show_bug.cgi?id=416660 https://bugs.kde.org/show_bug.cgi?id=415145 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 458518] Some Google Calendar events are not displayed in KOrganizer or Kalendar; Events confirmed to exist in Akonadi Console
https://bugs.kde.org/show_bug.cgi?id=458518 --- Comment #4 from Dave Connett --- (In reply to gjditchfield from comment #1) > Please use akonadiconsole to look at the undisplayed events. Are you listed > as an ATTENDEE? If so, this could be bug 436812. Based on a few tests, I don't think they are the same bug. Tests ran: 1. I created an event with only myself, not recurring -> It displayed 2. I had a friend create an event and send it to me, not recurring -> It displayed 3. I created an event with only myself, recurring every week -> Did not display 4. I changed RSVP to "Maybe" (previously a "Yes") to one of the recurring (daily) events already on my calendar that was previously not appearing -> The single event displayed 5. I replied as a "Maybe" to the recurring event referenced in test #4, but for the previous day -> Event #4 disappeared and this event displayed 6. I changed test #4 RSVP from "Maybe" back to "Yes" -> event referenced in test #5 disappeared, and event #4 displayed 7. I changed RSVP to all recurring events referenced in tests 4, 5, and 6 -> No change: event from test #4 is still the only one that displays in this series I have attached two files containing raw data from my Akonadi Console for two events: one that is displaying as expected, and one that is not. Here is the diff between to the two files: 6,7c6,7 < DTSTAMP:20220829T160523Z < X-KDE-LIBKGAPI-EventId:m79fsiqpfv5n18h6ikdpo737hr_20220829T16Z --- > DTSTAMP:20220830T133254Z > X-KDE-LIBKGAPI-EventId:1pqtfomf40achkvc4s831kdk8r 9,10c9,10 < UID:m79fsiqpfv5n18h6ikdpo737hr_r20220606t160...@google.com < LAST-MODIFIED:20220829T160523Z --- > UID:1pqtfomf40achkvc4s831kd...@google.com > LAST-MODIFIED:20220830T133254Z 12,13c12,13 < DTSTART;TZID=America/Detroit:20220829T12 < DTEND;TZID=America/Detroit:20220829T122500 --- > DTSTART;TZID=America/Detroit:20220829T11 > DTEND;TZID=America/Detroit:20220829T121500 It looks like it's something potentially related to event recurrence, though there are many other parameters I didn't control for. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 458518] Some Google Calendar events are not displayed in KOrganizer or Kalendar; Events confirmed to exist in Akonadi Console
https://bugs.kde.org/show_bug.cgi?id=458518 --- Comment #3 from Dave Connett --- Created attachment 151723 --> https://bugs.kde.org/attachment.cgi?id=151723=edit Raw Calendar Event Data from Akonadi Console of event not appearing -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 458518] Some Google Calendar events are not displayed in KOrganizer or Kalendar; Events confirmed to exist in Akonadi Console
https://bugs.kde.org/show_bug.cgi?id=458518 --- Comment #2 from Dave Connett --- Created attachment 151722 --> https://bugs.kde.org/attachment.cgi?id=151722=edit Raw Calendar Event Data from Akonodi Console of working event -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 458518] Some Google Calendar events are not displayed in KOrganizer or Kalendar; Events confirmed to exist in Akonadi Console
https://bugs.kde.org/show_bug.cgi?id=458518 Dave Connett changed: What|Removed |Added CC||dave.conn...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 458518] New: Some Google Calendar events are not displayed in KOrganizer or Kalendar; Events confirmed to exist in Akonadi Console
https://bugs.kde.org/show_bug.cgi?id=458518 Bug ID: 458518 Summary: Some Google Calendar events are not displayed in KOrganizer or Kalendar; Events confirmed to exist in Akonadi Console Product: kontact Version: 5.21.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: dave.conn...@gmail.com 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 *** STEPS TO REPRODUCE 1. Share Google Calendar From Account B to Account A 2. Add Calendar via Google Groupware to Kontact 3. Try to view Calendar Entries OBSERVED RESULT Some Calendar entries are missing EXPECTED RESULT All Calendar events should be visible Operating System: Arch Linux KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 Kernel Version: 5.19.4-arch1-1 (64-bit) Graphics Platform: X11 Processors: 32 × AMD Ryzen 9 5950X 16-Core Processor Memory: 125.0 GiB of RAM Graphics Processor: AMD Radeon RX 6900 XT Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7C34 System Version: 1.0 Log Snippets: ... Aug 30 13:36:33 aeonik kontact[2895017]: org.kde.pim.calendarview: AgendaView::calendarIncidenceChanged() Invalid agendaItem for incidence "4qa35nvs4eilk1mnhnlnnrj...@google.com" Aug 30 13:36:33 aeonik kontact[2895017]: org.kde.pim.calendarview: AgendaView::calendarIncidenceChanged() Invalid Aug 30 13:36:33 aeonik kontact[2895017]: org.kde.pim.calendarview: AgendaView::calendarIncidenceChanged() Invalid agendaItem for incidence "a547or2ad1f5p3smjvo9qom844_r20220608t161...@google.com" Aug 30 13:36:33 aeonik kontact[2895017]: org.kde.pim.calendarview: invalid incidence or item not found. QSharedPointer(0x55a7d3f7b0e0) Aug 30 13:36:33 aeonik kontact[2895017]: org.kde.pim.calendarview: invalid incidence or item not found. QSharedPointer(0x55a7d3f7b0e0) Aug 30 13:36:33 aeonik kontact[2895017]: org.kde.pim.calendarview: invalid incidence or item not found. QSharedPointer(0x55a7d3f7b0e0) Aug 30 13:36:33 aeonik kontact[2895017]: org.kde.pim.calendarview: AgendaView::calendarIncidenceChanged() Invalid agendaItem for incidence "6lm9ot4hssc3hv8cflt4kkq...@google.com" Aug 30 13:36:33 aeonik kontact[2895017]: org.kde.pim.calendarview: AgendaView::calendarIncidenceChanged() Invalid agendaItem for incidence "6lm9ot4hssc3hv8cflt4kkq...@google.com" ... I'd be happy to help Debug further, but I am not sure where to go for extra information. Akonadi Console shows the events have been downloaded properly. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457928] flat acceleration profile not honored after mouse unplugged and plugged in again
https://bugs.kde.org/show_bug.cgi?id=457928 Dave changed: What|Removed |Added CC||dav...@gmail.com --- Comment #3 from Dave --- I have the same experience with any of my mice. It's particularly annoying because one of them is a SteelSeries Aerox Wireless 3, which, in an effort to save weight, requires fairly frequent charging. Every time I unplug the dongle to use the cord to charge (and keep the mouse useful), or when I reverse this, I have this experience. It didn't always use to be this way - I first logged this downstream in may '22 (https://bugs.gentoo.org/842219) after it had been happening for about a week. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 435113] certain mouse settings resets after restart/resume from suspend/dock/undock
https://bugs.kde.org/show_bug.cgi?id=435113 Dave changed: What|Removed |Added CC||dav...@gmail.com --- Comment #112 from Dave --- I see this is fixed in 5.24.7 (and I'm still running 5.24.6-r2 on Gentoo), so I'm just adding this here as another test-case: unplugging and re-plugging a mouse does the same thing. I currently run a polling bash script to reset with xinput (`sudo udevadm trigger -s input` has no effect for me). This sounds minor, but unfortunately, my regular mouse is a SteelSeries Aerox 3 Wireless, which only has about 80 hours battery life when running full-tilt, so I have to disconnect/reconnect at least once (often a couple of times) per week to charge. However, I can also repro with my g305, simply unplugging the usb dongle and plugging back in again. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-karchive] [Bug 450597] Incorrect handling of zip files with data descriptors
https://bugs.kde.org/show_bug.cgi?id=450597 Dave changed: What|Removed |Added CC||sunny.bed7...@fastmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 457558] KMyMoney crashes immediately
https://bugs.kde.org/show_bug.cgi?id=457558 --- Comment #2 from Dave Bachmann --- False alarm. Works OK after a reboot tho it had failed multiple consecutive times prior to reboot. From: Jack Sent: Saturday, August 6, 2022 10:43 To: davebachm...@hotmail.com Subject: [kmymoney] [Bug 457558] KMyMoney crashes immediately https://bugs.kde.org/show_bug.cgi?id=457558 Jack changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Jack --- Have you upgraded any packages since last week? Does this crash happen every time you start KMyMoney? Can you start from console with "kmymoney -n" which does not open the data file. If it crashes, at least we know it is not because of your data. If it runs successfully, then try to open your data file. -- You are receiving this mail because: You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 457558] New: KMyMoney crashes immediately
https://bugs.kde.org/show_bug.cgi?id=457558 Bug ID: 457558 Summary: KMyMoney crashes immediately Product: kmymoney Version: 5.1.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: davebachm...@hotmail.com Target Milestone: --- Application: kmymoney (5.1.2) Qt Version: 5.15.2 Frameworks Version: 5.90.0 Operating System: Linux 5.14.21-150400.24.11-default x86_64 Windowing System: X11 Distribution: openSUSE Leap 15.4 DrKonqi: 5.24.4 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: Immediate crash after splash screen. Last used 1 week ago to add new brokerage account The crash can be reproduced every time. -- Backtrace: Application: KMyMoney (kmymoney), signal: Aborted [KCrash Handler] #4 0x7f7d23bcecdb in raise () from /lib64/libc.so.6 #5 0x7f7d23bd0375 in abort () from /lib64/libc.so.6 #6 0x7f7d24c7c56b in qt_message_fatal (context=..., message=...) at global/qlogging.cpp:1914 #7 QMessageLogger::fatal (this=this@entry=0x7ffe61b02940, msg=msg@entry=0x7f7d1b06ae85 "%s") at global/qlogging.cpp:893 #8 0x7f7d1b066edd in QQuickWidgetPrivate::handleContextCreationFailure (this=this@entry=0x562242cd7b80, format=...) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde43-150400.2.5.x86_64/src/quickwidgets/qquickwidget.cpp:885 #9 0x7f7d1b06722d in QQuickWidgetPrivate::createContext (this=this@entry=0x562242cd7b80) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde43-150400.2.5.x86_64/src/quickwidgets/qquickwidget.cpp:917 #10 0x7f7d1b0693be in QQuickWidget::resizeEvent (this=0x5622430a28a0, e=) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde43-150400.2.5.x86_64/src/quickwidgets/qquickwidget.cpp:1263 #11 0x7f7d2b0747d9 in QtWebEngineCore::RenderWidgetHostViewQtDelegateWidget::resizeEvent(QResizeEvent*) () from /usr/lib64/libQt5WebEngineWidgets.so.5 #12 0x7f7d26119dee in QWidget::event (this=this@entry=0x5622430a28a0, event=event@entry=0x7ffe61b02f00) at kernel/qwidget.cpp:8810 #13 0x7f7d1b06a16b in QQuickWidget::event (this=0x5622430a28a0, e=0x7ffe61b02f00) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde43-150400.2.5.x86_64/src/quickwidgets/qquickwidget.cpp:1573 #14 0x7f7d2b074af0 in QtWebEngineCore::RenderWidgetHostViewQtDelegateWidget::event(QEvent*) () from /usr/lib64/libQt5WebEngineWidgets.so.5 #15 0x7f7d260d93ac in QApplicationPrivate::notify_helper (this=this@entry=0x5622420dec10, receiver=receiver@entry=0x5622430a28a0, e=e@entry=0x7ffe61b02f00) at kernel/qapplication.cpp:3632 #16 0x7f7d260e01a0 in QApplication::notify (this=0x7ffe61b03990, receiver=0x5622430a28a0, e=0x7ffe61b02f00) at kernel/qapplication.cpp:3156 #17 0x7f7d24e9aac3 in QCoreApplication::notifyInternal2 (receiver=0x5622430a28a0, event=0x7ffe61b02f00) at kernel/qcoreapplication.cpp:1064 #18 0x7f7d24e9ac9e in QCoreApplication::sendEvent (receiver=receiver@entry=0x5622430a28a0, event=event@entry=0x7ffe61b02f00) at kernel/qcoreapplication.cpp:1462 #19 0x7f7d26111f46 in QWidgetPrivate::sendPendingMoveAndResizeEvents (this=this@entry=0x562242cd7b80, recursive=recursive@entry=false, disableUpdates=, disableUpdates@entry=false) at kernel/qwidget.cpp:7712 #20 0x7f7d26116503 in QWidgetPrivate::show_helper (this=0x562242cd7b80) at kernel/qwidget.cpp:7763 #21 0x7f7d2611632b in QWidgetPrivate::show_recursive (this=) at kernel/qwidget.cpp:7693 #22 0x7f7d26116440 in QWidgetPrivate::showChildren (this=this@entry=0x562242c61060, spontaneous=spontaneous@entry=false) at kernel/qwidget.cpp:8182 #23 0x7f7d2611651f in QWidgetPrivate::show_helper (this=this@entry=0x562242c61060) at kernel/qwidget.cpp:7769 #24 0x7f7d26119653 in QWidgetPrivate::setVisible (this=0x562242c61060, visible=) at kernel/qwidget.cpp:8112 #25 0x7f7d26118ce1 in QWidget::qt_static_metacall (_o=, _c=, _id=, _a=) at .moc/moc_qwidget.cpp:403 #26 0x7f7d24ececfb in QObject::event (this=this@entry=0x562242d5c740, e=e@entry=0x562242e6cc30) at kernel/qobject.cpp:1314 #27 0x7f7d26119ce3 in QWidget::event (this=0x562242d5c740, event=0x562242e6cc30) at kernel/qwidget.cpp:9081 #28 0x7f7d2b073459 in QWebEngineView::event(QEvent*) () from /usr/lib64/libQt5WebEngineWidgets.so.5 #29 0x7f7d260d93ac in QApplicationPrivate::notify_helper (this=this@entry=0x5622420dec10, receiver=receiver@entry=0x562242d5c740, e=e@entry=0x562242e6cc30) at kernel/qapplication.cpp:3632 #30 0x7f7d260e01a0 in QApplication::notify (this=0x7ffe61b03990, receiver=0x562242d5c740, e=0x562242e6cc30) at kernel/qapplication.cpp:3156 #31 0x7f7d24e9aac3 in QCoreApplication::notifyInternal2 (receiver=0x562242d5c740, event=0x562242e6cc30) at kernel/qcoreapplication.cpp:1064 #32 0x7f7d24e9ac9e in QCoreApplication::sendEvent
[Powerdevil] [Bug 456215] When booting on battery and plugging in power lead the brightness drops to minimum but only on the first time each boot
https://bugs.kde.org/show_bug.cgi?id=456215 --- Comment #9 from Dave Morley --- Hi Nate With the power options enabled for the screen brightness it still tries to dim but then comes back up to the correct brightness. There is a flash of the dimmed screen of about 1 second. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 456215] When booting on battery and plugging in power lead the brightness drops to minimum but only on the first time each boot
https://bugs.kde.org/show_bug.cgi?id=456215 --- Comment #8 from Dave Morley --- I'll give it a go when I am back home On 15 Jul 2022 22:22, Nate Graham wrote: https://bugs.kde.org/show_bug.cgi?id=456215 --- Comment #7 from Nate Graham --- Thanks. Does the issue go away if you check the checkbox for "Screen brightness" on the "On AC Power" and "On Battery" tabs? -- You are receiving this mail because: You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 456215] When booting on battery and plugging in power lead the brightness drops to minimum but only on the first time each boot
https://bugs.kde.org/show_bug.cgi?id=456215 --- Comment #6 from Dave Morley --- Created attachment 150631 --> https://bugs.kde.org/attachment.cgi?id=150631=edit With power plugged in -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 456215] When booting on battery and plugging in power lead the brightness drops to minimum but only on the first time each boot
https://bugs.kde.org/show_bug.cgi?id=456215 --- Comment #5 from Dave Morley --- Created attachment 150630 --> https://bugs.kde.org/attachment.cgi?id=150630=edit Battery settings -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 456215] When booting on battery and plugging in power lead the brightness drops to minimum but only on the first time each boot
https://bugs.kde.org/show_bug.cgi?id=456215 --- Comment #4 from Dave Morley --- Created attachment 150629 --> https://bugs.kde.org/attachment.cgi?id=150629=edit Power On Power Settings -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 456215] When booting on battery and plugging in power lead the brightness drops to minimum but only on the first time each boot
https://bugs.kde.org/show_bug.cgi?id=456215 --- Comment #3 from Dave Morley --- Sorry for the delay Attaching them now -- You are receiving this mail because: You are watching all bug changes.