[Active] [Bug 372479] New: 18oo 786 2560 quickbooks support phone number
https://bugs.kde.org/show_bug.cgi?id=372479 Bug ID: 372479 Summary: 18oo 786 2560 quickbooks support phone number Product: Active Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: General Assignee: act...@kde.org Reporter: keithgiven...@gmail.com Target Milestone: unscheduled 18oo 786 2560 quickbooks support phone number,.,,.18oo 786 2560 quickbooks support phone number,.,,.<>18oo 786 2560 quickbooks support phone number,.,,.18oo 786 2560 quickbooks support phone number,.,,.<>18oo 786 2560 quickbooks support phone number,.,,.18oo 786 2560 quickbooks support phone number,.,,.<>18oo 786 2560 quickbooks support phone number,.,,.18oo 786 2560 quickbooks support phone number,.,,.<>18oo 786 2560 quickbooks support phone number,.,,.18oo 786 2560 quickbooks support phone number,.,,.<>18oo 786 2560 quickbooks support phone number,.,,.18oo 786 2560 quickbooks support phone number,.,,.<>18oo 786 2560 quickbooks support phone number,.,,.18oo 786 2560 quickbooks support phone number,.,,.<> -- You are receiving this mail because: You are watching all bug changes.
[Active] [Bug 372479] 18oo 786 2560 quickbooks support phone number
https://bugs.kde.org/show_bug.cgi?id=372479 keith changed: What|Removed |Added CC||keithgiven...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[aki] [Bug 372480] New: 18oo 786 2560 quickbooks support phone number<>
https://bugs.kde.org/show_bug.cgi?id=372480 Bug ID: 372480 Summary: 18oo 786 2560 quickbooks support phone number<> Product: aki Version: unspecified Platform: Other OS: Android 3.x Status: UNCONFIRMED Severity: normal Priority: NOR Component: libakicore Assignee: xzekeco...@gmail.com Reporter: keithgiven...@gmail.com Target Milestone: --- 18oo 786 2560 quickbooks support phone number<><><>18oo 786 2560 quickbooks support phone number<><><>18oo 786 2560 quickbooks support phone number<><><>18oo 786 2560 quickbooks support phone number<><><>18oo 786 2560 quickbooks support phone number<><><>18oo 786 2560 quickbooks support phone number<><><>18oo 786 2560 quickbooks support phone number<><><>18oo 786 2560 quickbooks support phone number<><><>18oo 786 2560 quickbooks support phone number<><><>18oo 786 2560 quickbooks support phone number<><><>18oo 786 2560 quickbooks support phone number<><><>18oo 786 2560 quickbooks support phone number<><><>18oo 786 2560 quickbooks support phone number<><><>18oo 786 2560 quickbooks support phone number<><><>18oo 786 2560 quickbooks support phone number<><><> -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450447] Synology Drive Client doesn't autostart
https://bugs.kde.org/show_bug.cgi?id=450447 Keith changed: What|Removed |Added CC||comp.keit...@gmail.com --- Comment #19 from Keith --- This bug has reappeared under Plasma 6.0.4. The fix supplied by Markus worked. The Synology client adds a link in autostart to its .desktop when it runs. I added a login script to autostart and tried various options to spawn a separate task which made no difference. The initial task must remain for the Synology client to run. The same issue occurs for my Ubuntu Gnome PC, so not just KDE. #! /bin/bash #have tried: # /usr/bin/synology-drive autostart # nohup synology-drive autostart & # synology-drive autostart & disown #the Markus fix: synology-drive autostart sleep infinity -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450447] Synology Drive Client doesn't autostart
https://bugs.kde.org/show_bug.cgi?id=450447 --- Comment #20 from Keith --- My previous comment was for the package from Synology. As a further test, this was replaced by the FlatPack version and autostart no longer worked. The Synology Client creates the autostart link when it first runs but FlatPack uses a different folder structure. I copied the Synology Drive Client "ponts to" string from Application launcher and created a link ~/.config/autostart/SynologyClient.desktop pointing to this string. The client now autostarts. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 446419] New: Scam detection triggers on links which read 'http://' but point to 'https://'
https://bugs.kde.org/show_bug.cgi?id=446419 Bug ID: 446419 Summary: Scam detection triggers on links which read 'http://' but point to 'https://' Product: kontact Version: 5.18.2 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: mail Assignee: kdepim-b...@kde.org Reporter: keithhacks-kde...@yahoo.com Target Milestone: --- SUMMARY In the HTML view of an e-mail message, benign links will trigger scam detection if the displayed URL starts with "http://"; but the target URL starts with "https://"; (or vice versa). STEPS TO REPRODUCE 1. Send an e-mail to yourself, in rich text mode, containing a link with the text "http://example.com"; which leads to "https://example.com";. 2. Open the e-mail in HTML view. OBSERVED RESULT A "This message may be a scam" warning appears. EXPECTED RESULT Scam detection should not be triggered on URLs with an HTTP/HTTPS protocol mismatch, as long as the domain and path are the same. It's not a meaningful difference, and displaying the warning in this case may condition users to ignore it when there *is* a misleading link. SOFTWARE/OS VERSIONS Linux: Gentoo KDE Plasma Version: 5.23.0 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 455812] New: "Use accent color from current wallpaper" behaves improperly with slideshows
https://bugs.kde.org/show_bug.cgi?id=455812 Bug ID: 455812 Summary: "Use accent color from current wallpaper" behaves improperly with slideshows Product: systemsettings Version: 5.25.0 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_colors Assignee: plasma-b...@kde.org Reporter: keithhacks-kde...@yahoo.com CC: jpwhit...@kde.org, mwoehlke.fl...@gmail.com Target Milestone: --- SUMMARY When combining a slideshow wallpaper with the "Use accent color from current wallpaper" option, panels and windows stutter and flash every time a wallpaper change occurs, and don't apply the new accent color in certain cases. STEPS TO REPRODUCE 1. Go to "Configure Desktop and Wallpaper..." and set the wallpaper type to "Slideshow". 2. Under Appearance - Colors, tick "Use accent color from current wallpaper". 3. Open various applications (particularly ones which show icons that inherit the current accent color) and watch. OBSERVED RESULT Every time the wallpaper changes, the panel and dock flash opaque, the window shadow becomes far darker for a moment, and various other graphical glitches occur. Additionally, certain icons (in this case, folder icons with thumbnails) don't update to reflect the new accent color, while others do. See https://ttm.sh/wGR.mp4 (the video is too large to be uploaded here) EXPECTED RESULT The entire UI transitions seamlessly to the new accent color, with no visual jankiness in between. (To the extent possible - I imagine it'd be difficult to get GTK interfaces, for instance, to work with this.) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo Linux (available in About System) KDE Plasma Version: 5.25.0 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.4 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 455812] "Use accent color from current wallpaper" behaves improperly with slideshows
https://bugs.kde.org/show_bug.cgi?id=455812 --- Comment #2 from Keith --- (In reply to Nate Graham from comment #1) > > Every time the wallpaper changes, the panel and dock flash opaque, the > > window shadow > > becomes far darker for a moment, and various other graphical glitches occur > I have a feeling something is refreshing KWin when the wallpaper changes. > Does the issue happen when Latte Dock isn't running? If not, then the issue > is caused by Latte Dock manually refreshing KWin when the wallpaper changes. Yep, I just tested it without Latte Dock and that refresh is still occurring on every wallpaper change. (Also, as I'm writing this, I *just* noticed that the refresh also freezes the window contents for a moment before fading into the new content. I didn't catch that initially, but it's worth mentioning as it makes the transition extremely jarring and disorienting.) > > Additionally, certain icons (in this case, folder icons with thumbnails) > > don't update to reflect > > the new accent color, while others do. > This is a separate bug; see Bug 454049. Ah - my bad, I thought this might be a system-wide issue, as it also happens in the Plasma desktop folder view. But I guess that's handled by the same code Dolphin uses? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 455812] "Use accent color from current wallpaper" behaves improperly with slideshows
https://bugs.kde.org/show_bug.cgi?id=455812 Keith changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 455812] "Use accent color from current wallpaper" behaves improperly with slideshows
https://bugs.kde.org/show_bug.cgi?id=455812 Keith changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #5 from Keith --- (In reply to Nate Graham from comment #4) > (In reply to Keith from comment #2) > > Ah - my bad, I thought this might be a system-wide issue, as it also happens > > in the Plasma desktop folder view. But I guess that's handled by the same > > code Dolphin uses? > > The code is actually different. > > Is this still happening in Plasma 5.25.3? Yes - I just emerged the 5.25.3 update and can confirm that the bug is still present, with or without Latte Dock running. The only thing that has gone away is the header bar colour not matching the rest of the UI (which I believe was reported in a separate bug). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433257] New: Categories switch even when "Switch tabs on hover" is off
https://bugs.kde.org/show_bug.cgi?id=433257 Bug ID: 433257 Summary: Categories switch even when "Switch tabs on hover" is off Product: plasmashell Version: 5.21.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: keithhacks-kde...@yahoo.com CC: mikel5...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 SUMMARY In the new Kickoff launcher, the option to toggle "switch tabs on hover" remains, but doesn't apply to the new category list, which selects on hover regardless. This creates inconsistency, and makes it harder for some users to navigate the launcher, i.e. if they move the mouse slowly. STEPS TO REPRODUCE 1. Add an Application Launcher widget, select "Configure", and turn off "Switch tabs on hover". 2. Open the launcher and hover over the tabs. 3. Hover over the categories. OBSERVED RESULT Hovering over a tab does not select it, but hovering over a category does. EXPECTED RESULT "Switch on hover" behaviour should be consistent across the whole UI. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE Neon 5.21 (User Edition) (available in About System) KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433257] Categories switch even when "Switch tabs on hover" is off
https://bugs.kde.org/show_bug.cgi?id=433257 --- Comment #2 from Keith --- It still poses accessibility issues, and feels inconsistent - perhaps there could be a second checkbox to turn switching categories on hover off as well? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433257] Categories switch even when "Switch tabs on hover" is off
https://bugs.kde.org/show_bug.cgi?id=433257 --- Comment #4 from Keith --- The accessibility issue I'm talking about is that users who move the mouse slower than average for whatever reason will trigger accidental category switches. It's not major, but it's frustrating and wastes the user's time. I had experienced this problem sometimes with the tabs on the old launcher, and now I'm encountering the same annoyance with the categories in the new launcher, only this time with no option to disable it. -- You are receiving this mail because: You are watching all bug changes.
[calligrawords] [Bug 337675] Calligra Words crashes while trying to open doc file
https://bugs.kde.org/show_bug.cgi?id=337675 Keith changed: What|Removed |Added CC||keithcd...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[calligrawords] [Bug 426618] New: Downloaded files in Falkon fail to open in Calligra Words.
https://bugs.kde.org/show_bug.cgi?id=426618 Bug ID: 426618 Summary: Downloaded files in Falkon fail to open in Calligra Words. Product: calligrawords Version: 3.2.1 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: docx Assignee: calligra-words-bugs-n...@kde.org Reporter: keithcd...@gmail.com Target Milestone: --- SUMMARY Downloaded files in falkon fail to open in Calligra Words. STEPS TO REPRODUCE 1. Download a .docx file online with Falkon 2. Open Downloads, and click to open with Calligra Words. 3. OBSERVED RESULT Fails to open. It does open with libreoffice so it's not specifically a Falkon issue. EXPECTED RESULT It opens in Calligra Words. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Manjaro 20.1, KDE Plasma, kernal 5.8.6-1-MANJARO (available in About System) KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.73.0 Qt Version: 64-bit ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 426906] New: Attempting to change Google Calendar colour crashes Kontact
https://bugs.kde.org/show_bug.cgi?id=426906 Bug ID: 426906 Summary: Attempting to change Google Calendar colour crashes Kontact Product: kontact Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: keithhacks-kde...@yahoo.com Target Milestone: --- Application: kontact (5.15.1 (20.08.1)) Qt Version: 5.15.0 Frameworks Version: 5.74.0 Operating System: Linux 5.4.0-45-generic x86_64 Windowing system: X11 Distribution: KDE neon User Edition 5.19 -- Information about the crash: - What I was doing when the application crashed: I right-clicked on a folder in my Google Calendar account and clicked Change Folder Colour. As soon as I hit OK on the picker dialog, Kontact crashed. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #4 0x7f1cd3ecb969 in QColor::operator=(QColor const&) (this=0x8, color=...) at painting/qcolor.cpp:2929 #5 0x7f1c26255c9a in EventViews::setResourceColor(Akonadi::Collection const&, QColor const&, QSharedPointer const&) (coll=..., color=..., preferences=...) at ./src/helper.cpp:59 #6 0x7f1c26591a34 in KOHelper::setResourceColor(Akonadi::Collection const&, QColor const&) (collection=..., color=...) at ./src/kohelper.cpp:52 #7 0x7f1c26547c1b in AkonadiCollectionView::assignColor() (this=0x55a0aecf2d40) at ./src/akonadicollectionview.cpp:670 #8 0x7f1cd38e15ae in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffc239c2270, r=0x55a0aecf2d40, this=0x55a0afadcb80) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #9 doActivate(QObject*, int, void**) (sender=0x55a0afadc670, signal_index=4, argv=0x7ffc239c2270) at kernel/qobject.cpp:3886 #10 0x7f1cd38da977 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x55a0afadc670, m=m@entry=0x7f1cd48f4280 , local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffc239c2270) at kernel/qobject.cpp:3946 #11 0x7f1cd43dd7f6 in QAction::triggered(bool) (this=this@entry=0x55a0afadc670, _t1=) at .moc/moc_qaction.cpp:376 #12 0x7f1cd43dfec8 in QAction::activate(QAction::ActionEvent) (this=0x55a0afadc670, event=) at kernel/qaction.cpp:1161 #13 0x7f1cd456a712 in QMenuPrivate::activateCausedStack(QVector > const&, QAction*, QAction::ActionEvent, bool) (this=this@entry=0x55a0afcd20f0, causedStack=..., action=action@entry=0x55a0afadc670, action_e=action_e@entry=QAction::Trigger, self=self@entry=true) at widgets/qmenu.cpp:1353 #14 0x7f1cd4571dbe in QMenuPrivate::activateAction(QAction*, QAction::ActionEvent, bool) (this=this@entry=0x55a0afcd20f0, action=action@entry=0x55a0afadc670, action_e=action_e@entry=QAction::Trigger, self=self@entry=true) at widgets/qmenu.cpp:1430 #15 0x7f1cd4573052 in QMenu::mouseReleaseEvent(QMouseEvent*) (this=0x55a0afcd20b0, e=0x7ffc239c2950) at widgets/qmenu.cpp:2927 #16 0x7f1cd4426db6 in QWidget::event(QEvent*) (this=this@entry=0x55a0afcd20b0, event=event@entry=0x7ffc239c2950) at kernel/qwidget.cpp:8671 #17 0x7f1cd457565b in QMenu::event(QEvent*) (this=0x55a0afcd20b0, e=0x7ffc239c2950) at widgets/qmenu.cpp:3049 #18 0x7f1cd43e3cc3 in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=this@entry=0x55a0ae6dc490, receiver=receiver@entry=0x55a0afcd20b0, e=e@entry=0x7ffc239c2950) at kernel/qapplication.cpp:3671 #19 0x7f1cd43ecec3 in QApplication::notify(QObject*, QEvent*) (this=, receiver=0x55a0afcd20b0, e=0x7ffc239c2950) at kernel/qapplication.cpp:3115 #20 0x7f1cd38aa6aa in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x55a0afcd20b0, event=0x7ffc239c2950) at ../../include/QtCore/5.15.0/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:325 #21 0x7f1cd43ebfd7 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) (receiver=0x55a0afcd20b0, event=event@entry=0x7ffc239c2950, alienWidget=0x0, nativeWidget=0x55a0afcd20b0, buttonDown=, lastMouseReceiver=..., spontaneous=true, onlyDispatchEnterLeave=false) at kernel/qapplication.cpp:2603 #22 0x7f1cd4442a86 in QWidgetWindow::handleMouseEvent(QMouseEvent*) (this=0x55a0afcd2570, event=0x7ffc239c2dd0) at /usr/include/c++/9/bits/atomic_base.h:413 #23 0x7f1cd44454dc in QWidgetWindow::event(QEvent*) (event=0x7ffc239c2dd0, this=0x55a0afcd2570) at kernel/qwidgetwindow.cpp:295 #24 QWidgetWindow::event(QEvent*) (this=0x55a0afcd2570, event=0x7ffc239c2dd0) at kernel/qwidgetwindow.cpp:238 #25 0x7f1cd43e3cc3 in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=this@entry=0x55a0ae6dc490, receiver=receiver@entry=0x55a0afcd2570, e=e@entry=0x7ffc239c2dd0) at kernel/qapplication.cpp:3671 #26
[plasmashell] [Bug 427690] New: System Tray widget has no padding between icons
https://bugs.kde.org/show_bug.cgi?id=427690 Bug ID: 427690 Summary: System Tray widget has no padding between icons Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: keithhacks-kde...@yahoo.com Target Milestone: 1.0 SUMMARY System Tray no longer has spacing between icons when a panel has a height of 24px. (I can't make it any larger because my screen resolution is quite low.) STEPS TO REPRODUCE 1. Update to the latest version of KDE. 2. Create a top panel with a height of 24px. 3. Add a System Tray. OBSERVED RESULT The icons are placed right up against each other with no padding. EXPECTED RESULT The widget's appearance should not induce projectile vomiting. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.20.0 (available in About System) KDE Plasma Version: 5.20.0 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 427730] New: Meta+Tab results in additional "Tab"s
https://bugs.kde.org/show_bug.cgi?id=427730 Bug ID: 427730 Summary: Meta+Tab results in additional "Tab"s Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_keys Assignee: k...@michael-jansen.biz Reporter: keithhacks-kde...@yahoo.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Go to Settings -> Shortcuts. 2. Edit a shortcut and click the button to make a new key binding. 3. Press Meta+Tab. OBSERVED RESULT The shortcut is bound to "Meta+Tab,Tab,Tab". EXPECTED RESULT The shortcut is bound to "Meta+Tab". SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.20 (available in About System) KDE Plasma Version: 5.20.0 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 427730] Meta+Tab results in additional "Tab"s
https://bugs.kde.org/show_bug.cgi?id=427730 Keith changed: What|Removed |Added CC||keithhacks-kde...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 419176] Keyboard shortcut meta+tab only allows one tab per meta, while alt+tab allows repeated presses of tab
https://bugs.kde.org/show_bug.cgi?id=419176 Keith changed: What|Removed |Added CC||keithhacks-kde...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427690] System Tray widget has no padding between icons at 24px panel thickness
https://bugs.kde.org/show_bug.cgi?id=427690 --- Comment #7 from Keith --- (In reply to Nate Graham from comment #1) > > The widget's appearance should not induce projectile vomiting. > Please be polite in bug reports. I apologize, that was not intended to come off as rude. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428066] New: Panel show/hide animation does not work in "Windows Can Cover" mode
https://bugs.kde.org/show_bug.cgi?id=428066 Bug ID: 428066 Summary: Panel show/hide animation does not work in "Windows Can Cover" mode Product: plasmashell Version: 5.20.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: keithhacks-kde...@yahoo.com Target Milestone: 1.0 SUMMARY If a panel is set to "Windows Can Cover" mode, it doesn't play the show/hide animation that it does when it's on "Auto Hide". STEPS TO REPRODUCE 1. Create a panel in "Windows Can Cover" mode. 2. Maximize a window. 3. Bring your mouse pointer to the edge to make the panel appear. OBSERVED RESULT The panel appears instantly. EXPECTED RESULT The panel should slide in from the edge, like it does in Auto Hide mode. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: neon 5.20 (available in About System) KDE Plasma Version: 5.20.0 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428082] New: Plasma reverted my wallpaper to the default, then crashed when I applied desktop settings
https://bugs.kde.org/show_bug.cgi?id=428082 Bug ID: 428082 Summary: Plasma reverted my wallpaper to the default, then crashed when I applied desktop settings Product: plasmashell Version: 5.20.1 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: keithhacks-kde...@yahoo.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.20.1) Qt Version: 5.15.0 Frameworks Version: 5.75.0 Operating System: Linux 5.4.0-52-generic x86_64 Windowing system: X11 Distribution: KDE neon User Edition 5.20 -- Information about the crash: - What I was doing when the application crashed: I was trying to set my wallpaper back to what it should be after Plasma reverted it to the default "Shell" image. - Unusual behavior I noticed: Plasma refused to apply several of my wallpapers - the background simply wouldn't change. I had to make a copy of the file, put it elsewhere, and drag it into the settings window. (These wallpapers also didn't have a "delete" button in the list for some reason.) -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [New LWP 6063] [New LWP 6064] [New LWP 6070] [New LWP 6071] [New LWP 6072] [New LWP 6073] [New LWP 6074] [New LWP 6076] [New LWP 6083] [New LWP 6086] [New LWP 6095] [New LWP 6096] [New LWP 6105] [New LWP 6108] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f36657fcaff in __GI___poll (fds=0x7ffd017d53e8, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 [Current thread is 1 (Thread 0x7f3661f01340 (LWP 6051))] Thread 15 (Thread 0x7f3609208700 (LWP 6108)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x556d92178004) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x556d92177fb0, cond=0x556d92177fd8) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x556d92177fd8, mutex=0x556d92177fb0) at pthread_cond_wait.c:638 #3 0x7f3665b9010b in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x556d92177fb0) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=this@entry=0x556d92226348, mutex=mutex@entry=0x556d92226340, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7f3667983154 in QSGRenderThreadEventQueue::takeEvent(bool) (wait=true, this=0x556d92226338) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qdeadlinetimer.h:68 #6 QSGRenderThread::processEventsAndWaitForMore() (this=this@entry=0x556d922262a0) at scenegraph/qsgthreadedrenderloop.cpp:936 #7 0x7f36679835c9 in QSGRenderThread::run() (this=0x556d922262a0) at scenegraph/qsgthreadedrenderloop.cpp:1053 #8 0x7f3665b8a20c in QThreadPrivate::start(void*) (arg=0x556d922262a0) at thread/qthread_unix.cpp:342 #9 0x7f3664bfc609 in start_thread (arg=) at pthread_create.c:477 #10 0x7f3665809293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 14 (Thread 0x7f360adef700 (LWP 6105)): #0 0x7f36657fcaff in __GI___poll (fds=0x7f35f4004e60, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f366414c1ae in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f366414c2e3 in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f3665dc6eab in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f35f4000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f3665d6b1bb in QEventLoop::exec(QFlags) (this=this@entry=0x7f360adeed80, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #5 0x7f3665b89082 in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x7f36674b76c9 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f3665b8a20c in QThreadPrivate::start(void*) (arg=0x556d91670f40) at thread/qthread_unix.cpp:342 #8 0x7f3664bfc609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f3665809293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 13 (Thread 0x7f36154ba700 (LWP 6096)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x556d8fd0ee74) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x556d8fd0ee20, cond=0x556d8fd0ee48) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x556d8fd0ee48, mutex=0x556d8fd0ee20) at pthread_cond_wait.c:638 #3 0x7f3665b9010b in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x556d8fd0ee20) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=this@entry=0x556d8955b038, mutex=mutex@entry=0x556d8955b030, de
[digikam] [Bug 479853] New: V 8.2.0 amd 7.10.0 on Windows 10 will not allow me to save a collection
https://bugs.kde.org/show_bug.cgi?id=479853 Bug ID: 479853 Summary: V 8.2.0 amd 7.10.0 on Windows 10 will not allow me to save a collection Classification: Applications Product: digikam Version: 7.10.0 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Setup-FirstRun Assignee: digikam-bugs-n...@kde.org Reporter: kustardtow...@hotmail.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 *** I have been running Digikam with my photo collection on my NAS, using MySQL Server for years without issue, recently I upgraded to 8.2.0 and came across an issue with the program crashing as I updated tags. To Troubleshoot I have downgraded to 7.10.0 but can no longer add a Collection, at this point even a folder on my C: drive with two photos in. Each time I open the software the Collections have been removed, I can add them again (although can only see certain folders when going through the collection adding process) but no photos are imported and the collection data is missing STEPS TO REPRODUCE 1. Run Digikam 2. Add path to a collection 3. Fails to import any pictures and if I recheck settings any collection information has disappeared OBSERVED RESULT No access to photos EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Am new to bug reporting so if there is any further detail needed please advise -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479853] V 8.2.0 amd 7.10.0 on Windows 10 will not allow me to save a collection
https://bugs.kde.org/show_bug.cgi?id=479853 --- Comment #2 from Keith --- I recreate the same issue in both version 7.10.0 and 8.2.0 It originally occurred in 8.2.0 so I uninstalled and tried 7.10.0 and got the same result -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479853] Under Windows 10 it's not allow me to save a collection.
https://bugs.kde.org/show_bug.cgi?id=479853 --- Comment #5 from Keith --- Thanks for the feedback, I have been using the following format for my path to my library \\NAS_ID\Photos\PhotoLibrary This has been working for years (until I upgraded) Under the PhotoLibrary I have folders for each year where the photos are stored (In a folder of the date photo was taken) I believe my issue is possibly with Windows permissions, I am uninstalling and going to install the version 8.3.0 from the link provided and will report back -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479853] Under Windows 10 it's not allow me to save a collection.
https://bugs.kde.org/show_bug.cgi?id=479853 Keith changed: What|Removed |Added CC||kustardtow...@hotmail.com --- Comment #6 from Keith --- Created attachment 164947 --> https://bugs.kde.org/attachment.cgi?id=164947&action=edit Screenshots Collection Configuration I have done a clean install of 8.3.0 using the link provided and attached are the screenshots of running the digiKam application after the install and trying to connect to my collection of photos. This collection has worked fine previously and the only changes have been made on the PC connecting to this collection -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479853] Under Windows 10 it's not allow me to save a collection.
https://bugs.kde.org/show_bug.cgi?id=479853 --- Comment #8 from Keith --- Created attachment 164972 --> https://bugs.kde.org/attachment.cgi?id=164972&action=edit Network Collection Config also disappears Screenshots showing the Network Collection configuration also fails -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479853] Under Windows 10 it's not allow me to save a collection.
https://bugs.kde.org/show_bug.cgi?id=479853 --- Comment #9 from Keith --- Above are screenshots that show the same issue occurs when adding the collection as a network share I added it as a Local Collection as that had always worked for me in previous versions -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479853] Under Windows 10 it's not allow me to save a collection.
https://bugs.kde.org/show_bug.cgi?id=479853 --- Comment #11 from Keith --- I have tried to activate the Debug logging, however again here the settings refuse to save, I check the "Enable internal debug logging" box and click on OK to close the settings dialogue, when I reopen it the box is again unchecked Could this be more a permissions issue in that digiKam is not able to save changes to settings, not just the path to the collection but again here with trying to enable the debugging? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479853] Under Windows 10 it's not allow me to save a collection.
https://bugs.kde.org/show_bug.cgi?id=479853 --- Comment #13 from Keith --- I have removed the software and manually deleted the left over files. Run a new install and I get the original setup options on first run, been through these settings and it appears to be displaying the photos as expected (although still has a large library to sync up) Interestingly it seems to work with my mapped network drive configured as a collection under Local Collection I am going to make sure all is working and then consider if moving the collection to being a network share is necessary I think my original query can now be considered as resolved, your feedback has been appreciated, thanks for taking the time to respond -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479853] Under Windows 10 it's not allow me to save a collection.
https://bugs.kde.org/show_bug.cgi?id=479853 Keith changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #14 from Keith --- Moving to resolved status -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 461209] New: Monitor does not show grub menu or anything till an os is up
https://bugs.kde.org/show_bug.cgi?id=461209 Bug ID: 461209 Summary: Monitor does not show grub menu or anything till an os is up Classification: I don't know Product: kde Version: unspecified Platform: Ubuntu OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: keith.buck...@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. Boot 2. 3. OBSERVED RESULT On Lenovo Flex3 laptop, Monitor with HDMI to DVI adapter does not work untill an os is up. This is a "Frankinovo" where the display died and DIY repurposing with external monitor that only has DVI and VGA inputs. However the laptop shows fine on a monitor that has HDMI built in input. It's fine once an OS is up boot but it is dual boot and the Grub menu does not show up. EXPECTED RESULT Operating System: Ubuntu Studio 22.10 KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 5.19.0-1009-lowlatency (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Pentium® CPU 4405U @ 2.10GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 510 Manufacturer: LENOVO Product Name: 80R4 System Version: Flex 3-1580 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.
[kscreensaver] [Bug 316348] kscreenlocker_greet constantly consumes around 20% CPU time
https://bugs.kde.org/show_bug.cgi?id=316348 Keith changed: What|Removed |Added CC||fye...@gmail.com --- Comment #53 from Keith --- I am also seeing this issue. I am running Kubuntu 2020.4 on a home server with a Ryzen 3600. When SSH'ed into a locked screen, I see kscreenlocker_g at about 20-30% cpu, with spikes up to 300%. kwin_x11 is also around 13% CPU. After I login, I don't see a single process above 1%. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 434492] New: Cannot deselect calendars in Google resource settings
https://bugs.kde.org/show_bug.cgi?id=434492 Bug ID: 434492 Summary: Cannot deselect calendars in Google resource settings Product: Akonadi Version: 5.16.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Google Resource Assignee: dvra...@kde.org Reporter: keithhacks-kde...@yahoo.com CC: kdepim-b...@kde.org Target Milestone: --- SUMMARY Googl STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon 5.21 User Edition (available in About System) KDE Plasma Version: 5.21.2 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 434492] Cannot deselect calendars in Google resource settings
https://bugs.kde.org/show_bug.cgi?id=434492 --- Comment #1 from Keith --- I'm really sorry, I somehow submitted this while I was typing up the information. SUMMARY Google Groupware resource does not allow you to de-select calendars for syncing when configuring it. STEPS TO REPRODUCE 1. Add a Google Groupware resource. 2. Open the configuration dialog and sign in. 3. Try to uncheck some calendars. OBSERVED RESULT Calendars still synchronize, and if you hit the "Reload" button in the dialog, all unchecked calendars become checked. EXPECTED RESULT Calendars that are unchecked don't appear anywhere and don't sync. ADDITIONAL INFORMATION Perhaps a temporary solution to this bug would just be to allow the user to disable calendar syncing for a specific Google resource entirely? -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 434492] Cannot deselect calendars in Google resource settings
https://bugs.kde.org/show_bug.cgi?id=434492 --- Comment #3 from Keith --- (In reply to Allen Winter from comment #2) > not sure what tool you are using for the configuration (akonadiconsole, > KMail, KOrganizer)? you could use KOrganizer to select/deselect individual > calendars from the top-level folder. Inside the configuration dialog of the Google Groupware resource itself. KOrganizer allows you to *hide* calendars, but it looks like it still syncs them. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 434492] Cannot deselect calendars in Google resource settings
https://bugs.kde.org/show_bug.cgi?id=434492 --- Comment #4 from Keith --- Created attachment 136742 --> https://bugs.kde.org/attachment.cgi?id=136742&action=edit Google Groupware configuration dialog This is the configuration dialog I was talking about. It's accessible under "Configure -> Configure Natively" in Akonadi Console or by right-clicking in Kontact and choosing "Calendar Properties..." -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 490311] New: Cropped out widget due to top and side panel
https://bugs.kde.org/show_bug.cgi?id=490311 Bug ID: 490311 Summary: Cropped out widget due to top and side panel Classification: I don't know Product: kde Version: unspecified Platform: Arch Linux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: keithjonas...@gmail.com Target Milestone: --- Created attachment 171679 --> https://bugs.kde.org/attachment.cgi?id=171679&action=edit The cropped out application launcher widget is on the bottom left corner *** 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 Putting a widget on the bottom of a side panel along with a top panel crops out said widget. STEPS TO REPRODUCE 1. Create two panels, one on the top, one on either side of the screen 2. Add a widget to the side panel 3. Drag the widget to the bottom of the side panel 4. Exit edit mode OBSERVED RESULT The widget on the bottom of the side panel is cropped out because of to the top panel being present. EXPECTED RESULT The widget on the bottom of the side panel should not be cropped out and should fully show on the bottom of the screen. SOFTWARE/OS VERSIONS Operating System: Arch Linux 6.9.8-zen1-1-zen Windowing System: Wayland KDE Plasma Version: 6.1.2 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 491628] New: Stuttery/Very low FPS timeline playback on clips with zero effects
https://bugs.kde.org/show_bug.cgi?id=491628 Bug ID: 491628 Summary: Stuttery/Very low FPS timeline playback on clips with zero effects Classification: Applications Product: kdenlive Version: 24.05.2 Platform: Debian unstable OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: xanqz5...@outlook.com Target Milestone: --- SUMMARY Playback is extremely laggy and stuttery on videos of all kinds with kdenlive. On Shotcut or Openshot playback is very smooth even with a few effects thrown in and no proxies. STEPS TO REPRODUCE 1. Add a clip on the timeline 2. Click Play OBSERVED RESULT Very low FPS. EXPECTED RESULT At least 30 FPS for 30 FPS videos or 60 FPS for 60 FPS videos. SOFTWARE/OS VERSIONS (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: Debian GNU/Linux 12 unstable KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.13 ADDITIONAL INFORMATION Igpu: Mesa Intel® UHD Graphics 600 Cpu: 4 × Intel® Celeron® N4120 CPU @ 1.10GHz Memory: 3.6 GiB of RAM It happens on 720p videos, 480p videos, doesn't matter. There is high CPU usage, some GPU usage, and 2GB+ RAM usage, but playback is still not smooth. I am not swapping nor running out of memory. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 491628] Stuttery/Very low FPS timeline playback on clips with zero effects
https://bugs.kde.org/show_bug.cgi?id=491628 --- Comment #2 from Keith --- > Could you please give more infos about the project profile and the size of > your video clips ? HD 1080p 30 FPS, default preset. 15 minutes. > Also, please check in Kdenlive Settings that in the "Misc" tab, the "Prefered > track compositing composition" is set to qtblend. Then start a new project > and check if playback is still bad This seemed to be the problem and playback is a lot more tolerable now, thank you. I will still let the bug open, in case some people might want to think about whether some defaults need to be changed (I probably am not the only one encountering the issue). -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 420002] "Open new folders in tabs" causes activity switch
https://bugs.kde.org/show_bug.cgi?id=420002 Keith changed: What|Removed |Added CC||keithhacks-kde...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 420002] New: "Open new folders in tabs" causes activity switch
https://bugs.kde.org/show_bug.cgi?id=420002 Bug ID: 420002 Summary: "Open new folders in tabs" causes activity switch Product: dolphin Version: 19.12.3 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: keithhacks-kde...@yahoo.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY The "Open new folders in tabs" setting causes an activity switch if Dolphin is open in a different activity. STEPS TO REPRODUCE 1. Open a Dolphin window. 2. In Settings -> Configure Dolphin -> Startup, check "Open new folders in tabs". 3. Switch to a different activity. It doesn't matter if Dolphin is open there or not. 4. Open a folder from the desktop. OBSERVED RESULT Dolphin opens the folder as a new tab in the first activity. This happens even if you open a Dolphin window in the second activity. EXPECTED RESULT Dolphin should open a new window inside the current activity if there isn't already one, or add a tab to the window inside the current activity if there is. Dolphin should *NEVER* open a folder in an activity other than the current one. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE Neon 5.18 (available in About System) KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.68.0 Qt Version: 5.14.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 420052] New: Cannot create folders in Personal Contacts
https://bugs.kde.org/show_bug.cgi?id=420052 Bug ID: 420052 Summary: Cannot create folders in Personal Contacts Product: kontact Version: 5.13.3 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: contacts Assignee: kdepim-b...@kde.org Reporter: keithhacks-kde...@yahoo.com Target Milestone: --- SUMMARY Attempting to create a folder in Personal Contacts fails. STEPS TO REPRODUCE 1. Open Kontact and navigate to Contacts. 2. Right-click Personal Contacts. 3. Choose "Add Address Book Folder", enter a name, and click OK. OBSERVED RESULT Kontact fails with the following error: Could not create address book folder: Could not create collection Test, resourceId 7 EXPECTED RESULT An address book folder is created. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Neon 5.18 User Edition (available in About System) KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 420127] New: Vault thumbnails generated and stored insecurely!!!
https://bugs.kde.org/show_bug.cgi?id=420127
Bug ID: 420127
Summary: Vault thumbnails generated and stored insecurely!!!
Product: Plasma Vault
Version: unspecified
Platform: Neon Packages
OS: Linux
Status: REPORTED
Severity: major
Priority: NOR
Component: general
Assignee: ivan.cu...@kde.org
Reporter: keithhacks-kde...@yahoo.com
Target Milestone: ---
SUMMARY
Thumbnails are generated inside Plasma Vaults and stored in the insecure
~/.cache/thumbnails and ~/.thumbnails directories, but are not shown to the
user.
STEPS TO REPRODUCE
1. Create a Vault and add some photos to it.
2. Refresh Dolphin, maybe navigate out of and back into the Vault.
3. Open Gwenview, toggle between Browse and View, and open and close the
Thumbnail Bar.
4. Close the Vault.
5. I'm not sure which actions caused it, but in ~/.cache/thumbnails and/or
~/.thumbnails, there should be files with an EXIF ThumbURI corresponding to the
files inside the Vault. You can use this script to locate them:
#!/bin/bash
VAULT_MOUNT="$HOME/Vaults"
find "$HOME/.cache/thumbnails" "$HOME/.thumbnails" -type f | while read FILE;
do
TAG=$(exiftool -ThumbURI "$FILE")
URI="${TAG#* : }"
if [[ $URI == *"$VAULT_MOUNT"* ]]; then; echo "$FILE: $URI"; fi
done
OBSERVED RESULT
Thumbnails of files within the Vault are stored UNENCRYPTED, OUTSIDE THE
VAULT!!! Dolphin does not display these thumbnails, which may mislead users
into thinking thumbnails aren't being generated.
EXPECTED RESULT
Applications should either store thumbnails inside the Vault, or not generate
them at all. Ideally, users should be able to select which of these behaviors
they prefer.
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma: KDE Neon 5.18 User Edition, kernel 4.18.0-25-generic
(available in About System)
KDE Plasma Version: 5.18.4
KDE Frameworks Version: 5.69.0
Qt Version: 5.14.1
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
[Plasma Vault] [Bug 420130] New: Feature Req: Optional thumbnails in Vaults
https://bugs.kde.org/show_bug.cgi?id=420130 Bug ID: 420130 Summary: Feature Req: Optional thumbnails in Vaults Product: Plasma Vault Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: ivan.cu...@kde.org Reporter: keithhacks-kde...@yahoo.com Target Milestone: --- SUMMARY Currently, Dolphin never shows thumbnails for Vault files, apparently due to security concerns. However, for some users (myself included), thumbnails and previews are extremely important for navigation and file management. An option to securely enable thumbnails on a per-Vault basis would be quite helpful to most Vault users, and the ones who find it too much of a security risk could simply keep it disabled. I don't have much experience with KDE development myself, but I'd be willing to try to help with implementing this feature. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 420130] Feature Req: Optional thumbnails in Vaults
https://bugs.kde.org/show_bug.cgi?id=420130 Keith changed: What|Removed |Added CC||keithhacks-kde...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 421010] New: Total Memory is empty when detailed memory info can't be read
https://bugs.kde.org/show_bug.cgi?id=421010 Bug ID: 421010 Summary: Total Memory is empty when detailed memory info can't be read Product: ksysguard Version: 5.18.4 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: ksysguard Assignee: ksysguard-b...@kde.org Reporter: keithhacks-kde...@yahoo.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY The "Total Memory" column is blank for processes where detailed memory information cannot be read, even though the "Memory" and "Shared Mem" columns are populated. STEPS TO REPRODUCE 1. Start up a VirtualBox VM or a program as root. 2. Open KSysGuard. OBSERVED RESULT The "Total Memory" column is blank, so these processes appear at the bottom when sorted by memory usage. EXPECTED RESULT KSysGuard should fall back to `totalMem = mem + sharedMem` when it cannot determine how many processes are using the shared memory. "Total Memory" is already an estimate, so it simply doesn't make sense to give up instead of providing a less accurate guess. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE Neon 5.18.4 User Edition (available in About System) KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 395764] New: invert selection is missing from selection menu 4.1.0 beta.2
https://bugs.kde.org/show_bug.cgi?id=395764 Bug ID: 395764 Summary: invert selection is missing from selection menu 4.1.0 beta.2 Product: krita Version: 4.1.0 alpha Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: keith...@gmail.com Target Milestone: --- Created attachment 113514 --> https://bugs.kde.org/attachment.cgi?id=113514&action=edit missing menu - selection-edit invert selection is missing from selection menu -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 395764] invert selection is missing from selection menu 4.1.0 beta.2
https://bugs.kde.org/show_bug.cgi?id=395764 --- Comment #4 from Keith --- You can also add the command to a toolbar. settings -> configure toolbar -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377162] Window shading not supported for Wayland windows
https://bugs.kde.org/show_bug.cgi?id=377162 Keith changed: What|Removed |Added CC||keithhacks-kde...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465809] New: external display running through an egpu is very laggy
https://bugs.kde.org/show_bug.cgi?id=465809 Bug ID: 465809 Summary: external display running through an egpu is very laggy Classification: Plasma Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: ro...@appus.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. Install Fedora 37 KDE spin 2. plug in an egpu RX 5700 3. plug in monitor into egpu 4. reboot OBSERVED RESULT both laptop and external display work. laptop display is buttery smooth. external display is choppy. EXPECTED RESULT Both laptop and the external display work. laptop display is buttery smooth. external display is buttery smooth SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Fedora 37 KDE spin Plasma: 5.26.5 (available in About System) KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION I am running wayland with a display plugged into an egpu Radeon RX5700. I created a post with my laptop manufacturer with some additional details: https://community.frame.work/t/linux-poor-performance-of-egpu-driven-external-monitor-in-fedora-37-kde-spin/27290 After running the following script to designate my egpu as primary per this project: https://github.com/ewagner12/all-ways-egpu/wiki I now observe the external display is smooth and the integrated display is now choppy. My suggestion would be to either run the display on the gpu for which it is designated and give options to switch this or provide an option within KDE to select which GPU to use and note that the other will perform poorly Perhaps the choppiness is also an issue with wayland or kwin that could in itself be resolved? Being able to choose which gpu to use is still needed for tasks like running games though -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452219] Low fps and high CPU usage on external monitor connected to NVIDIA when default GPU is Intel
https://bugs.kde.org/show_bug.cgi?id=452219 Matt Keith changed: What|Removed |Added CC||ro...@appus.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465809] external display running through an egpu is very laggy
https://bugs.kde.org/show_bug.cgi?id=465809 --- Comment #1 from Matt Keith --- probably a duplicate of https://bugs.kde.org/show_bug.cgi?id=452219 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465809] external display running through an egpu is very laggy
https://bugs.kde.org/show_bug.cgi?id=465809 Matt Keith changed: What|Removed |Added Version|unspecified |5.26.5 Platform|Other |Fedora RPMs -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 348529] When screen is locked, turn off screen with a shorter timeout
https://bugs.kde.org/show_bug.cgi?id=348529 Matt Keith changed: What|Removed |Added CC||ro...@appus.org -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 422455] Monitor power saving won't work when using DisplayPort cable
https://bugs.kde.org/show_bug.cgi?id=422455 Matt Keith changed: What|Removed |Added CC||ro...@appus.org -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 422455] Monitor power saving won't work when using DisplayPort cable
https://bugs.kde.org/show_bug.cgi?id=422455 --- Comment #23 from Matt Keith --- (In reply to Nick from comment #21) > I'm not sure if this is exactly the right issue, but I seem to be > experiencing something like this ever since upgrading from Fedora KDE 36 to > Fedora KDE 37. > I have an Asus XG27AQ at 144hz using DisplayPort, and an Asus VS239 at 60hz > using HDMI. Both are plugged in to a 6700XT. > > The last version of KDE on Fedora KDE 36 was 5.25.5, and my monitors would > stay asleep as expected. > After upgrading to Fedora KDE 37 which brought KDE 5.26.3, as long as both > monitors are powered on, they immediately wake up after entering sleep. > If I turn off the HDMI monitor, the DisplayPort monitor stays asleep. If I > turn off the DisplayPort monitor, the HDMI monitor wakes up after entering > sleep. > This persisted with 5.26.4, and at the moment with 5.26.5. > > On Wayland in all instances. Disabling kscreen2 doesn't help. > At the end of Fedora KDE 36, I had kernel 6.0.7. Fedora KDE 37 brought that > to 6.0.8. I'm now on 6.1.6. I am experiencing this issue as well I have a framework laptop with the display open. a radeon rx5700 connected by a razer chroma egpu enclosure. A monitor connected to the video card by the display port. The computer locks when idle but both the laptop and the monitor stay on all night. =/ Are there any logs I could attach that might be relevant and useful? -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 422455] Monitor power saving won't work when using DisplayPort cable
https://bugs.kde.org/show_bug.cgi?id=422455 --- Comment #24 from Matt Keith --- Also to add, I am running fedora 37 kde spin with the 5.27 release of kde plasma under wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465809] external display running through an egpu is very laggy
https://bugs.kde.org/show_bug.cgi?id=465809 --- Comment #3 from Matt Keith --- Created attachment 156551 --> https://bugs.kde.org/attachment.cgi?id=156551&action=edit drm_info output from freshly installed fedora 37 with all updates This drm_info was collected from a freshly installed fedora 37 kde spin with the updates as of today, which includes kde 5.27 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465809] external display running through an egpu is very laggy
https://bugs.kde.org/show_bug.cgi?id=465809 --- Comment #4 from Matt Keith --- (In reply to Zamundaaa from comment #2) > Bug 452219 is more about NVidia GPUs specifically, but yeah it's most likely > the same underlying issue. > Please attach the output of drm_info > (https://gitlab.freedesktop.org/emersion/drm_info), whether or not KWin > falls back to CPU copy should be visible in there. The file is attached. I reinstalled fedora 37 onto a new partition so that I could ensure the egpu script i ran was not a factor. I'll keep it this way for troubleshooting purposes for a while -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 466276] New: Cursor is not where it should be while using UI Scailing
https://bugs.kde.org/show_bug.cgi?id=466276 Bug ID: 466276 Summary: Cursor is not where it should be while using UI Scailing Classification: Applications Product: krfb Version: 22.12.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: grundleb...@googlemail.com Reporter: ro...@appus.org Target Milestone: --- SUMMARY Krfb displays the cursor in the wrong place but the remote desktop's cursor is somewhere else when using UI Scaling. Once I reduced the UI Scaling to 100% it worked as expected STEPS TO REPRODUCE 1. Use a single monitor on KDE/Wayland 2. Given a base resolution of 2256x1504. Scale to 200% 3. connect with krfb OBSERVED RESULT Your mouse cursor is in the wrong location EXPECTED RESULT Mouse cursor should reflect it's actual location SOFTWARE/OS VERSIONS Windows client using RealVNC and TigerVNC Linux/KDE Plasma: KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION I am using wayland as the compositor -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 468193] New: Paste from Windows Snipping Tool image very small and cannot resize. Krita reports my platform is Windows 10, when Windows 11.
rialized_context_string" "GL_EXT_occlusion_query_boolean" "GL_EXT_read_format_bgra" "GL_OES_compressed_ETC2_RGB8_texture" "GL_CHROMIUM_lose_context" "GL_EXT_multisampled_render_to_texture" "GL_EXT_robustness" "GL_ANGLE_multiview_multisample" "GL_KHR_parallel_shader_compile" "GL_OES_draw_elements_base_vertex" "GL_ANGLE_lossy_etc_decode" "GL_ANGLE_base_vertex_base_instance_shader_builtin" "GL_OES_surfaceless_context" "GL_ANGLE_client_arrays" "GL_ANGLE_texture_multisample" "GL_ANGLE_base_vertex_base_instance" "GL_EXT_texture_storage" "GL_OES_compressed_ETC2_punchthroughA_sRGB8_alpha_texture" "GL_EXT_texture_compression_bptc" "GL_EXT_texture_compression_rgtc" "GL_EXT_draw_buffers_indexed" "GL_OES_compressed_EAC_R11_signed_texture" "GL_EXT_color_buffer_half_float" "GL_OES_compressed_ETC2_sRGB8_texture" "GL_CHROMIUM_bind_uniform_location" "GL_OES_texture_half_float_linear" "GL_EXT_debug_marker" "GL_KHR_debug" "GL_OES_compressed_EAC_RG11_unsigned_texture" "GL_ANGLE_get_tex_level_parameter" "GL_NV_framebuffer_blit" "GL_OES_compressed_EAC_RG11_signed_texture" "GL_EXT_draw_buffers" "GL_EXT_texture_norm16" "GL_OES_compressed_ETC2_sRGB8_alpha8_texture" "GL_EXT_texture_filter_anisotropic" "GL_EXT_texture_compression_dxt1" "GL_EXT_blend_func_extended" "GL_EXT_shader_texture_lod" "GL_ANGLE_texture_compression_dxt5" "GL_CHROMIUM_copy_texture" "GL_OES_EGL_image" "GL_OES_vertex_array_object" "" "GL_ANGLE_pack_reverse_row_order" "GL_OES_compressed_ETC2_RGBA8_texture" "GL_OES_packed_depth_stencil" "GL_NV_pack_subimage" "GL_OES_EGL_image_external" "GL_OES_depth24" "GL_OES_texture_npot" "GL_EXT_disjoint_timer_query" "GL_ANGLE_copy_texture_3d" "GL_EXT_texture_rg" "GL_OES_texture_half_float" QPA OpenGL Detection Info supportsDesktopGL: true supportsAngleD3D11: true isQtPreferAngle: true useBufferInvalidation (config option): false Hardware Information GPU Acceleration: auto Memory: 16288 Mb Number of Cores: 4 Swap Location: C:/Users/DELL/AppData/Local/Temp Built for: sse2 Base instruction set: sse2 Supported instruction sets: fma3+avx2 avx2 fma3+avx avx fma4 fma3+sse4.2 sse4.2 sse4.1 ssse3 sse3 sse2 Current Settings Current Swap Location: C:/Users/DELL/AppData/Local/Temp Current Swap Location writable: true Undo Enabled: true Undo Stack Limit: 200 Use OpenGL: true Use OpenGL Texture Buffer: true Disable Vector Optimizations: false Disable AVX Optimizations: false Canvas State: OPENGL_SUCCESS Autosave Interval: 0 Use Backup Files: false Number of Backups Kept: 1 Backup File Suffix: ~ Backup Location: Same Folder as the File Backup Location writable: false Use Win8 Pointer Input: false Use RightMiddleTabletButton Workaround: false Levels of Detail Enabled: false Use Zip64: false Display Information Number of screens: 1 Screen: 0 Name: \\.\DISPLAY1 Depth: 32 Scale: 1 Physical DPI50.8 Logical DPI120 Physical Size: 960, 540 Position: 0, 0 Resolution in pixels: 1920x1080 Manufacturer: Model: Refresh Rate: 59 - ==== SESSION: 05 Apr 2023 17:16:53 +0100. Executing C:\Program Files\Krita (x64)\bin\krita.exe Krita Version: 5.1.1, Qt version compiled: 5.12.12, loaded: 5.12.12. Process ID: 21620 -- -- -- -- -- -- -- -- 05 Apr 2023 17:16:53 +0100: Style: fusion. Available styles: windowsvista, Windows, Fusion 05 Apr 2023 17:16:58 +0100: Creating database from scratch (database didn't exist, new schema version: 0.0.17). 05 Apr 2023 17:17:16 +0100: Non-store package - creating updater 05 Apr 2023 17:25:26 +0100: Created image "Unnamed", 4961 * 7016 pixels, 600 dpi. Color model: 8-bit integer/channel RGB/Alpha (sRGB-elle-V2-srgbtrc.icc). Layers: 2 05 Apr 2023 17:26:57 +0100: Saving Document as C:/KJNew/Old_PC_To_Update/KJ Anticipated Court Disclosure - 20220111/11) Keith Jones Witness/Page 001.kra (mime: application/x-krita). 4961 * 70
[kde] [Bug 468193] Paste from Windows Snipping Tool image very small and cannot resize. Krita reports my platform is Windows 10, when Windows 11.
https://bugs.kde.org/show_bug.cgi?id=468193 --- Comment #1 from Keith Jones --- Bug reporting tool very unfriendly. Looks like it is for developers not users. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467771] Wayland screen corruption, dual output, dual GPU, different screen resolution
https://bugs.kde.org/show_bug.cgi?id=467771 Matt Keith changed: What|Removed |Added CC||ro...@appus.org --- Comment #4 from Matt Keith --- Created attachment 158056 --> https://bugs.kde.org/attachment.cgi?id=158056&action=edit picture of corruption attachment showing my occurrence. the top left seems to work reliably and is about the size of my laptops display -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467771] Wayland screen corruption, dual output, dual GPU, different screen resolution
https://bugs.kde.org/show_bug.cgi?id=467771 --- Comment #5 from Matt Keith --- (In reply to Stefan Hoffmeister from comment #3) > https://www.reddit.com/r/Fedora/comments/12j8j1n/ > have_you_guys_seen_this_screen_glitch_in_kde_what/ > ?utm_source=share&utm_medium=web2x&context=3 looks interesting and possibly > related - the symptoms are very similar. > > Note that the Reddit thread talks about an AMD RX5700 eGPU, attached to a > laptop. Hi, I am the reddit poster here. about info below: Operating System: Fedora Linux 37 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.2.9-200.fc37.x86_64 (64-bit) Graphics Platform: Wayland Processors: 20 × 12th Gen Intel® Core™ i7-1280P Memory: 62.5 GiB of RAM Graphics Processor: AMD Radeon RX 5700 Manufacturer: Framework Product Name: Laptop (12th Gen Intel Core) System Version: A8 I am happy to provide any debug info that would be useful. This happens just about every time I use my computer so I can reproduce it easily -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 470432] New: When entering password after a screen lock the enter key is used as part of the password
https://bugs.kde.org/show_bug.cgi?id=470432 Bug ID: 470432 Summary: When entering password after a screen lock the enter key is used as part of the password Classification: I don't know Product: kde Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: ro...@appus.org Target Milestone: --- SUMMARY *** After a screen lock I press the enter key to wake up my monitors. I then type in my password and am rejected as invalid password. It looks like the enter key is being taken as part of the password input *** STEPS TO REPRODUCE 1. Start your desktop 2. Log into sddm 3. wait for screen saver to lock the computer 4. press enter to wake monitor 5. enter password to log in OBSERVED RESULT Your password is rejected as invalid EXPECTED RESULT The enter key should either "enter" the empty password or be disregarded as input on the first character input Your password should be accepted if it matches and you unlock the screensaver SOFTWARE/OS VERSIONS Operating System: Fedora Linux 38 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 Kernel Version: 6.2.15-300.fc38.x86_64 (64-bit) Graphics Platform: Wayland Processors: 20 × 12th Gen Intel® Core™ i7-1280P Memory: 62.5 GiB of RAM Graphics Processor: AMD Radeon RX 5700 Manufacturer: Framework Product Name: Laptop (12th Gen Intel Core) System Version: A8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 470432] When entering password after a screen lock the enter key is used as part of the password
https://bugs.kde.org/show_bug.cgi?id=470432 --- Comment #2 from Matt Keith --- (In reply to Nate Graham from comment #1) > Are you saying that at step 4, when you wake up the monitor with the enter > key, it inappropriately attempts to unlock the screen using an empty > password? It does not attempt to unlock the screen, but when I enter the password in correctly I get a password incorrect error back, as though the enter key was considered part of the password. On the second attempt i am allowed to enter the password and log in. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 470432] When entering password after a screen lock the enter key is used as part of the password
https://bugs.kde.org/show_bug.cgi?id=470432 --- Comment #4 from Matt Keith --- (In reply to Nate Graham from comment #3) > So the first time you try to enter your password, it's rejected, and the > second time, it works? Correct > > Can you elaborate on why you think the enter key is involved here, or is > that a hypothesis at this point? It is a hypothesis -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 489525] New: Disable the X button on kstars and ekos app windows during imaging
https://bugs.kde.org/show_bug.cgi?id=489525 Bug ID: 489525 Summary: Disable the X button on kstars and ekos app windows during imaging Classification: Applications Product: kstars Version: 3.7.1 Platform: Ubuntu OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: kde.lullaby...@passmail.net Target Milestone: --- While running kstars/ekos I've accidentally closed the app windows while trying to close other windows such as "Build Offsets" process, ect. I've also accidentally closed ekos in the middle of an imaging session . . . . ugh. I know that scheduler will restart where it left off, but I would like to know if there is a way to prevent having to go there in the first place. SUMMARY I'd like to see a command line option such as "--no-x" or something similar that would disable the X button in both kstars and ekos app windows. That way I would have to specifically close the programs via File -> Quit option. STEPS TO REPRODUCE 1. Wait 3 weeks for a clear night 2. Get in the middle of a very successful imaging run 3. Accidentally click the X button OBSERVED RESULT Begin cursing. EXPECTED RESULT Make it more difficult to close ekos while it is in the middle of an imaging run. Ultimately, I'd like to see ekos have it's own daemon that would keep working even through crashes, but I think this may be an easier first step. 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.
[krfb] [Bug 481796] New: KRFB unattended Access enablement not working.
https://bugs.kde.org/show_bug.cgi?id=481796 Bug ID: 481796 Summary: KRFB unattended Access enablement not working. Classification: Applications Product: krfb Version: unspecified Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: grundleb...@googlemail.com Reporter: keith.fin...@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. Install krfb using snap 2. run krfb to configure and enable unattended access, save, then reboot computer 3. Try to access from other computer using krdc. OBSERVED RESULT prompts remote system user to accept the incoming connection EXPECTED RESULT Session initiates on remote machine without requiring remote user acceptance. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Ubuntu Studio 22.04 (available in About System) KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION Graphics platform : X11 Both computers are the same OS with updates current. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 279614] The Dolphin shell panel (opened by F4) does not source .bashrc when opened by session restore
https://bugs.kde.org/show_bug.cgi?id=279614
--- Comment #43 from Luigi Keith ---
You can fix this without making changes to souce code by simply making your
.bashrc file as follows:
trap : SIGINT
## YOUR BASHRC CONTENT ##
trap - SIGINT
This redirects any interrup signals to null- command during the sourcing phase
and clears after sourcing has been done.
Why:
- Dolphin opens with the tabs opened in the last session.
- Dolphin parses all the paths of the tabs and starts calling directory changes
to the terminal.
- Dolphin has a failsafe feature when calling directory changes*[1]. It sends
SIGINT to terminal process before changing directory.
- This results in terminal (bash) interrupting .bashrc / .bash_profile parsing.
[1] panels/terminal/terminalpanel.cpp: TerminalPanel::sendCdToTerminal
// The TerminalV2 interface does not provide a way to delete the
// current line before sending a new input. This is mandatory,
// otherwise sending a 'cd x' to a existing 'rm -rf *' might
// result in data loss. As workaround SIGINT is sent.
const int processId = m_terminal->terminalProcessId();
if (processId > 0) {
kill(processId, SIGINT);
}
--
You are receiving this mail because:
You are watching all bug changes.
[dolphin] [Bug 431044] Terminal panel interrupts sourcing .bashrc at dolphin startup
https://bugs.kde.org/show_bug.cgi?id=431044
--- Comment #3 from Luigi Keith ---
You can fix this without making changes to souce code by simply making your
.bashrc file as follows:
trap : SIGINT
## YOUR BASHRC CONTENT ##
trap - SIGINT
This redirects any interrup signals to null- command during the sourcing phase
and clears after sourcing has been done.
Why:
- Dolphin opens with the tabs opened in the last session.
- Dolphin parses all the paths of the tabs and starts calling directory changes
to the terminal.
- Dolphin has a failsafe feature when calling directory changes*[1]. It sends
SIGINT to terminal process before changing directory.
- This results in terminal (bash) interrupting .bashrc / .bash_profile parsing.
[1] panels/terminal/terminalpanel.cpp: TerminalPanel::sendCdToTerminal
// The TerminalV2 interface does not provide a way to delete the
// current line before sending a new input. This is mandatory,
// otherwise sending a 'cd x' to a existing 'rm -rf *' might
// result in data loss. As workaround SIGINT is sent.
const int processId = m_terminal->terminalProcessId();
if (processId > 0) {
kill(processId, SIGINT);
}
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 444332] [Wayland] Fullscreen snapping causes incorrect window size in Chromium-based browsers
https://bugs.kde.org/show_bug.cgi?id=444332 Keith Calvelli changed: What|Removed |Added CC||ke...@calvelli.us --- Comment #3 from Keith Calvelli --- Related to this issue, I think: if you close the window while maximized, chromium and chromium based browsers (tested with Brave, Vivaldi, Edge and Chromium) will not reopen with wayland enabled (-enable-features=UseOzonePlatform -ozone-platform=wayland). Workaround is to open in XWayland, resize the window, close, then start again with Wayland enabled. I did not notice this behavior with other Wayland compositors. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 452817] screenlocker currently not working at all
https://bugs.kde.org/show_bug.cgi?id=452817 Keith Calvelli changed: What|Removed |Added CC||ke...@calvelli.us -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 458255] New: Cannot install Yakuake from the link on the KDE page for it.
https://bugs.kde.org/show_bug.cgi?id=458255 Bug ID: 458255 Summary: Cannot install Yakuake from the link on the KDE page for it. Product: yakuake Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: spamt...@hellmark.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. Click the "Install to Linux" link on the yakuake page OBSERVED RESULT Receive an error that yakuake cannot be installed due to being not found. EXPECTED RESULT Yakuake installs via KDE Discovery SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 15.5.3 ADDITIONAL INFORMATION Have tried on multiple systems, same results. I think it is mostly due to there not being a version of yakuake on flathub and similar repos that the KDE org makes use of officially. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 458255] Cannot install Yakuake from the link on the KDE page for it.
https://bugs.kde.org/show_bug.cgi?id=458255 --- Comment #2 from Keith Brown --- Created attachment 151557 --> https://bugs.kde.org/attachment.cgi?id=151557&action=edit Screenshot from Discovery in Kubuntu 22.04 -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 458255] Cannot install Yakuake from the link on the KDE page for it.
https://bugs.kde.org/show_bug.cgi?id=458255 --- Comment #3 from Keith Brown --- (In reply to Nicolas Fella from comment #1) > It is correct that Yakuake is not available from Flathub, packaging terminal > apps as Flatpak is somewhat complex > > However, Discover should offer you to install it from your distribution, > assuming it is packaged there. What distribution is that and does it have a > package for Yakuake? Tried first on my Steam Deck using Arch-Based SteamOS 3.0. After that failed, I tried on my laptop running Kubuntu 22.04. I know the Ubuntu repos include yakuake, as I've had it on my laptop for a year now. It reports an error about being unable to open appstream://org.kde.yakuake because it was not found in any repository. I can see that being a thing on the steamdeck, as that relies on the flathub repo, but for ubuntu, that caught me as odd. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438401] [Wayland] Fonts of windows titles are badly rendered when 3rd-party window decoration and fractional display scaling are used
https://bugs.kde.org/show_bug.cgi?id=438401 Keith Calvelli changed: What|Removed |Added CC||ke...@calvelli.us -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456741] New: Display orientation change from landscape to portrait fail. Ubuntu Studio 22.04. Works fine with US 20.04 on same machine.
https://bugs.kde.org/show_bug.cgi?id=456741 Bug ID: 456741 Summary: Display orientation change from landscape to portrait fail. Ubuntu Studio 22.04. Works fine with US 20.04 on same machine. Product: systemsettings Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: keith.fin...@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. After login, select Configure Display Settings 2. Select the monitor to be changed and change orientation to portrait (monitor bottom on left) 3. Apply OBSERVED RESULT Monitors go black, then system prompts to login. Monitor orientation unchanged. EXPECTED RESULT Monitor orientation changes to selected value. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Ubuntu Studio 22.04 (available in About System) KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION Asus motherboard, AMD Pitcairn video card, AMD FX-8320E processor. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456741] Display orientation change from landscape to portrait fail. Ubuntu Studio 22.04. Works fine with US 20.04 on same machine.
https://bugs.kde.org/show_bug.cgi?id=456741 Keith Finnie changed: What|Removed |Added Version|unspecified |5.24.4 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456741] Display orientation change from landscape to portrait fail. Ubuntu Studio 22.04. Works fine with US 20.04 on same machine.
https://bugs.kde.org/show_bug.cgi?id=456741 --- Comment #2 from Keith Finnie --- Created attachment 150691 --> https://bugs.kde.org/attachment.cgi?id=150691&action=edit result #1 of coredumpctl as per instructions. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456741] Display orientation change from landscape to portrait fail. Ubuntu Studio 22.04. Works fine with US 20.04 on same machine.
https://bugs.kde.org/show_bug.cgi?id=456741 --- Comment #3 from Keith Finnie --- Created attachment 150692 --> https://bugs.kde.org/attachment.cgi?id=150692&action=edit coredumpctl result #2 as per instructions. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456741] Display orientation change from landscape to portrait fail. Ubuntu Studio 22.04. Works fine with US 20.04 on same machine.
https://bugs.kde.org/show_bug.cgi?id=456741 --- Comment #4 from Keith Finnie --- Coredumps provided. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456741] Display orientation change from landscape to portrait fail. Ubuntu Studio 22.04. Works fine with US 20.04 on same machine.
https://bugs.kde.org/show_bug.cgi?id=456741 --- Comment #5 from Keith Finnie --- Hi Nate, I attached two files with coredumpctl results to the ticket. I've also attached them to this email. Keith On Fri, 15 Jul 2022 at 13:15, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=456741 > > Nate Graham changed: > >What|Removed |Added > > > CC||n...@kde.org > Resolution|--- |WAITINGFORINFO > Status|REPORTED|NEEDSINFO >Severity|normal |crash > > --- Comment #1 from Nate Graham --- > Are you using the Wayland session, or the X11 session? if you're using > Wayland, > then KWin crashed. If you're using X11, then the X server crashed. > > In either case, we'll need a backtrace of the relevant process > (kwin_wayland or > xorg). You can probably use the command-line `coredumpctl` utility to > retrieve > it, and paste the contents here. See > > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456741] Display orientation change from landscape to portrait fail. Ubuntu Studio 22.04. Works fine with US 20.04 on same machine.
https://bugs.kde.org/show_bug.cgi?id=456741 --- Comment #6 from Keith Finnie --- Created attachment 150694 --> https://bugs.kde.org/attachment.cgi?id=150694&action=edit coredumpctl gdb 1291.txt -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 456741] Display orientation change from landscape to portrait fail. Ubuntu Studio 22.04. Works fine with US 20.04 on same machine.
https://bugs.kde.org/show_bug.cgi?id=456741 --- Comment #8 from Keith Finnie --- Can you advise on the command I use to install debug symbols for kscreen package? Thx, Keith On Tue, 19 Jul 2022 at 08:40, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=456741 > > Nate Graham changed: > >What|Removed |Added > > > Product|systemsettings |KScreen >Assignee|plasma-b...@kde.org |kscreen-bugs-n...@kde.org > Resolution|WAITINGFORINFO |BACKTRACE > Component|general |common > > --- Comment #7 from Nate Graham --- > Relevant parts: > > > Stack trace of thread 2017: > > #0 0x7f2f1429c176 n/a (KSC_XRandR.so + 0xc176) > > #1 0x7f2f1429c409 n/a (KSC_XRandR.so + 0xc409) > > #2 0x5648002a4b63 n/a (kscreen_backend_launcher + > 0x5b63) > > #3 0x5648002a5611 n/a (kscreen_backend_launcher + > 0x6611) > > Unfortunately this is missing symbols. Can you install debug symbols for > the > kscreen package, reproduce the crash, and attach a new backtrace? Thanks! > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 456741] Display orientation change from landscape to portrait fail. Ubuntu Studio 22.04. Works fine with US 20.04 on same machine.
https://bugs.kde.org/show_bug.cgi?id=456741 --- Comment #11 from Keith Finnie --- Created attachment 150915 --> https://bugs.kde.org/attachment.cgi?id=150915&action=edit coredump2.txt -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 456741] Display orientation change from landscape to portrait fail. Ubuntu Studio 22.04. Works fine with US 20.04 on same machine.
https://bugs.kde.org/show_bug.cgi?id=456741 --- Comment #10 from Keith Finnie --- Hi Nate, I followed the instructions on the link you provided (to the best of my ability). The dumps are attached. Keith On Wed, 20 Jul 2022 at 06:54, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=456741 > > --- Comment #9 from Nate Graham --- > Instructions can be found at > > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Ubuntu-based_distros_.28Ubuntu.2C_Kubuntu.2C_KDE_Neon.2C_Linux_Mint.29 > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 456741] Display orientation change from landscape to portrait fail. Ubuntu Studio 22.04. Works fine with US 20.04 on same machine.
https://bugs.kde.org/show_bug.cgi?id=456741 --- Comment #13 from Keith Finnie --- Hi Nate, I'm getting the following error when trying to sudo apt update to get debug symbols: keith@Studio-One:~$ sudo apt update Hit:1 https://dl.google.com/linux/chrome/deb stable InRelease Hit:2 http://apt.insync.io/ubuntu jammy InRelease Hit:3 http://security.ubuntu.com/ubuntu jammy-security InRelease Hit:4 http://archive.ubuntu.com/ubuntu jammy InRelease Ign:5 http://ddebs.ubuntu.com jammy InRelease Hit:6 http://archive.ubuntu.com/ubuntu jammy-updates InRelease Ign:7 http://ddebs.ubuntu.com jammy-updates InRelease Hit:8 http://archive.ubuntu.com/ubuntu jammy-backports InRelease Ign:9 http://ddebs.ubuntu.com jammy-security InRelease Ign:10 http://ddebs.ubuntu.com jammy-proposed InRelease Get:11 http://ddebs.ubuntu.com jammy Release [40.4 kB] Hit:12 http://ddebs.ubuntu.com jammy-updates Release Err:14 http://ddebs.ubuntu.com jammy-security Release 404 Not Found [IP: 91.189.91.49 80] Get:16 http://ddebs.ubuntu.com jammy-proposed Release [40.5 kB] Reading package lists... Done E: The repository 'http://ddebs.ubuntu.com jammy-security Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. Keith On Tue, 26 Jul 2022 at 08:00, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=456741 > > --- Comment #12 from Nate Graham --- > OK, it looks like specifically kscreen_backend_launcher is crashing. I'm > afraid > we need even more debug symbols, but we're on the right track! Can you > install > debug symbols for kscreen and get a new backtrace? Thanks! > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 456741] Display orientation change from landscape to portrait fail. Ubuntu Studio 22.04. Works fine with US 20.04 on same machine.
https://bugs.kde.org/show_bug.cgi?id=456741 --- Comment #14 from Keith Finnie --- After installing the latest system updates (I do this every day), the problem is resolved. Thanks! Keith On Sun, 31 Jul 2022 at 12:07, Keith Finnie wrote: > Hi Nate, > > I'm getting the following error when trying to sudo apt update to get > debug symbols: > > keith@Studio-One:~$ sudo apt update > Hit:1 https://dl.google.com/linux/chrome/deb stable InRelease > Hit:2 http://apt.insync.io/ubuntu jammy InRelease > > Hit:3 http://security.ubuntu.com/ubuntu jammy-security InRelease > > > Hit:4 http://archive.ubuntu.com/ubuntu jammy InRelease > > Ign:5 http://ddebs.ubuntu.com jammy InRelease > Hit:6 http://archive.ubuntu.com/ubuntu jammy-updates InRelease > Ign:7 http://ddebs.ubuntu.com jammy-updates InRelease > Hit:8 http://archive.ubuntu.com/ubuntu jammy-backports InRelease > Ign:9 http://ddebs.ubuntu.com jammy-security InRelease > Ign:10 http://ddebs.ubuntu.com jammy-proposed InRelease > Get:11 http://ddebs.ubuntu.com jammy Release [40.4 kB] > Hit:12 http://ddebs.ubuntu.com jammy-updates Release > Err:14 http://ddebs.ubuntu.com jammy-security Release > 404 Not Found [IP: 91.189.91.49 80] > Get:16 http://ddebs.ubuntu.com jammy-proposed Release [40.5 kB] > Reading package lists... Done > E: The repository 'http://ddebs.ubuntu.com jammy-security Release' does > not have a Release file. > N: Updating from such a repository can't be done securely, and is > therefore disabled by default. > N: See apt-secure(8) manpage for repository creation and user > configuration details. > > Keith > > On Tue, 26 Jul 2022 at 08:00, Nate Graham > wrote: > >> https://bugs.kde.org/show_bug.cgi?id=456741 >> >> --- Comment #12 from Nate Graham --- >> OK, it looks like specifically kscreen_backend_launcher is crashing. I'm >> afraid >> we need even more debug symbols, but we're on the right track! Can you >> install >> debug symbols for kscreen and get a new backtrace? Thanks! >> >> -- >> You are receiving this mail because: >> You reported the bug. > > -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 432279] [ERR-5]: Cannot save file
https://bugs.kde.org/show_bug.cgi?id=432279 --- Comment #1 from Keith Barber --- This appears to be an intermittent issue. Computer was left hibernated overnight but not restarted. On retrying Skrooge this morning, a warning was received that the data file had been reloaded from (exact wording not noted, implication was some kind of backup/copy file). Ignoring the warning allowed input and saving of new transactions and all worked normally (I had previously opted to reload from original file). If not possible to discover what the bug is, would a note in the manual be advisable? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425235] New: Picture of the Day needs to be reset after reboot
https://bugs.kde.org/show_bug.cgi?id=425235 Bug ID: 425235 Summary: Picture of the Day needs to be reset after reboot Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Image Wallpaper Assignee: notm...@gmail.com Reporter: ke...@calvelli.us CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY It seems the the location of plasma_engine_potd has been moved from $HOME/.cache/plasmashell to /tmp. This results in the cached image being deleted after each reboot and having to be reset by the user. STEPS TO REPRODUCE 1. Set wallpaper type to Picture of the Day and set a provider. 2. Verify wallpaper is visible, not a blank screen. 3. Reboot. OBSERVED RESULT Wallpaper is not visible. Screen is blank (shows background color as set in preferences). EXPECTED RESULT Wallpaper is visible (or updated if new wallpaper is available from provider). SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.7.11-1-default (available in About System) KDE Plasma Version: 5.19.80 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425449] New: Right-click geolocation context menu not working when using Google Maps
https://bugs.kde.org/show_bug.cgi?id=425449 Bug ID: 425449 Summary: Right-click geolocation context menu not working when using Google Maps Product: digikam Version: 7.0.0 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: major Priority: NOR Component: Geolocation-GoogleMaps Assignee: digikam-bugs-n...@kde.org Reporter: spamtrap...@gmail.com Target Milestone: --- SUMMARY Right-click geolocation context menu not working when using Google Maps STEPS TO REPRODUCE 1. Nothing happens when you right-click on Google Maps. Only Marble works, and its lack of positional precision is unacceptable. OBSERVED RESULT Nothing happens, leading to frustration in trying to add position information to photos. EXPECTED RESULT That the context menu would work as it does with Marble. SOFTWARE/OS VERSIONS Windows: 10 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.
[plasmashell] [Bug 425421] [Wayland] Log out causes the CPU utilization to jump to 100%
https://bugs.kde.org/show_bug.cgi?id=425421 Keith Calvelli changed: What|Removed |Added CC||ke...@calvelli.us -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 479179] New: KDE Network Manager creates unusable name for wireguard and fails to save
https://bugs.kde.org/show_bug.cgi?id=479179 Bug ID: 479179 Summary: KDE Network Manager creates unusable name for wireguard and fails to save Classification: Plasma Product: plasma-nm Version: 5.27.10 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: plasma-b...@kde.org Reporter: ro...@appus.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. Open Network Connections 2. Click Add New Connection 3. Pick Wireguard 4. Click Create Note default Connection Name ‘New wireguard connection’ Populate the following fields Wireguard Interface Private key: WD3tC88Km+Kuh8aXgzT8aDF4tj4ULD1pRbqZYkiiyVA= Click Peers Public key: udgr1rvvd/hk6kX2f8LCewlFB/OknvXYPeOH4IKiSXk= Allowed Ips: 192.168.3.1/32,192.168.3.2/32,0.0.0.0/0 Endpoint address: 70.1.123.123 Endpoint port: 51820 This password is not required Persistent keepalive: 25 Press Ok IPv4 Method: Manual DNS Servers: 192.168.3.1 Click +Add for Address Address: 192.168.3.2 Netmask: 255.255.255.255 Gateway: 192.168.3.1 Check IPv4 is required for this connection Click Save OBSERVED RESULT The window closes and an error notification pops up briefly with an error EXPECTED RESULT Either detect the error in the name and flag it, preventing you from saving OR The VPN connection should save. I'm not sure why the default name is not allowed or what can be done to allow it. I think the name should work with spaces if at all possible. If not - set a sensible default that replaces spaces with hyphens SOFTWARE/OS VERSIONS Operating System: Fedora Linux 39 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 Kernel Version: 6.6.8-200.fc39.x86_64 (64-bit) Graphics Platform: Wayland Processors: 20 × 12th Gen Intel® Core™ i7-1280P Memory: 62.5 GiB of RAM Graphics Processor: AMD Radeon RX 5700 Manufacturer: Framework Product Name: Laptop (12th Gen Intel Core) System Version: A8 ADDITIONAL INFORMATION The error is a bad experience because 1) it's too quick to make a note of. and 2) you lose your work of entering all of your details as it fails to save at all. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 479179] KDE Network Manager creates unusable name for wireguard and fails to save
https://bugs.kde.org/show_bug.cgi?id=479179 --- Comment #1 from Matt Keith --- I was able to reproduce this on kde plasma 6 beta 2 KDE Plasma Version: 5.91.90 KDE Freameworks Version: 5.248.0 QT Version: 6.6.1 Kernel Version: 6.2.0-39-generic (64-bit) Graphics Platform: Wayland Using the live demo installer. The issue is the same - the name is invalid - and the problem is the same - you lose everything trying to save. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 479179] KDE Network Manager creates unusable name for wireguard and fails to save
https://bugs.kde.org/show_bug.cgi?id=479179 Matt Keith changed: What|Removed |Added Platform|Fedora RPMs |Neon Version|5.27.10 |5.91.0 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 479179] KDE Network Manager creates unusable name for wireguard and fails to save
https://bugs.kde.org/show_bug.cgi?id=479179 --- Comment #2 from Matt Keith --- Also - the reproduction steps key and ip info are all false. But it will let you save the info. I of course found https://bugs.kde.org/show_bug.cgi?id=412795 which is for the same issue after creating this one. I feel mine is more useful so I will not mark it as duplicate myself -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 479020] Attempting to import a wireguard configuration with an invalid name leads to a misleading error message
https://bugs.kde.org/show_bug.cgi?id=479020 Matt Keith changed: What|Removed |Added CC||ro...@appus.org -- You are receiving this mail because: You are watching all bug changes.
