[plasmashell] [Bug 469648] New: Gap left between cascading submenus
https://bugs.kde.org/show_bug.cgi?id=469648 Bug ID: 469648 Summary: Gap left between cascading submenus Classification: Plasma Product: plasmashell Version: 5.27.4 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Menu (Kicker) Assignee: plasma-b...@kde.org Reporter: banderson19...@san.rr.com Target Milestone: 1.0 Created attachment 158876 --> https://bugs.kde.org/attachment.cgi?id=158876=edit Screenshot showing gap between 2nd and 3rd menus SUMMARY *** There is sometimes a gap left between succeeding levels of cascading menus such that the cursor has to be moved across it quickly or the submenu is closed. *** STEPS TO REPRODUCE 1. Create a three level menu in the Application Menu widget. In my case I have Multimedia->Media Editor->[applications] 2. Move the cursor onto desired submenu entry (in my case Multimedia->Media Editor) 3. When the submenu appears notice that there is a gap between the second level menu and the third. 4. Move the cursor slowly towards the new submenu and when it hits the gap, the menu disappears. OBSERVED RESULT If you are too slow, the menu you want disappears EXPECTED RESULT The cursor should move smoothly onto the submenu no matter how slow you move the cursor. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed version 20230509. Kernel 6.3.1-1 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION A screenshot is attached. The most obvious place to see the gap is where the edge of the highlighted entry in the first menu can be seen between the second menu and the third menu. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 461655] "extract timeline zone" does not effects subtitles
https://bugs.kde.org/show_bug.cgi?id=461655 Bruce Anderson changed: What|Removed |Added CC||banderson19...@san.rr.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 453453] New: IPv6 Address field not populated on existing WireGuard entries
https://bugs.kde.org/show_bug.cgi?id=453453 Bug ID: 453453 Summary: IPv6 Address field not populated on existing WireGuard entries Product: plasma-nm Version: 5.24.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: editor Assignee: jgrul...@redhat.com Reporter: banderson19...@san.rr.com Target Milestone: --- SUMMARY *** Opening an existing WireGuard connection which has an IPv6 method set to "Manual" and and address specified, no entries are populated in the Address table on the IPv6 tab of the editor. This makes it impossible to modify the connection because the "Apply" button never becomes active. *** STEPS TO REPRODUCE 1. Create a WireGuard connection which includes a Manually supplied IPv6 address and save it. 2. Exit the configuration applet and start it again. 3. Go to the newly created WireGuard connection. OBSERVED RESULT Look at the IPv6 tab and verify that the previously entered address is not in the table. This also prevents saving any changes due without putting the IPv6 address back in because the entry is not valid. EXPECTED RESULT The IPv6 tab should have the previously entered address in the table. Should be able to save any changes without reentering the address. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSuse tumbleweed KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION This works on a very old version (5.16.0) but this isn't something that I try to do very often so I don't know when it might have failed between then and now. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421303] No network icon in system drawer under certain conditions
https://bugs.kde.org/show_bug.cgi?id=421303 Bruce Anderson changed: What|Removed |Added Status|REPORTED|RESOLVED CC||banderson19...@san.rr.com Resolution|--- |DUPLICATE --- Comment #3 from Bruce Anderson --- *** This bug has been marked as a duplicate of bug 420983 *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 420983] Missing system tray icon if WireGuard connection made before applet startup
https://bugs.kde.org/show_bug.cgi?id=420983 Bruce Anderson changed: What|Removed |Added CC||simone.za...@protonmail.com --- Comment #3 from Bruce Anderson --- *** Bug 421303 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 420983] New: Missing system tray icon if WireGuard connection made before applet startup
https://bugs.kde.org/show_bug.cgi?id=420983 Bug ID: 420983 Summary: Missing system tray icon if WireGuard connection made before applet startup Product: plasma-nm Version: 5.18.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: banderson19...@san.rr.com Reporter: banderson19...@san.rr.com CC: jgrul...@redhat.com Target Milestone: --- SUMMARY No icon appears in the system tray if a configured WireGuard connection has started prior to start of the applet. STEPS TO REPRODUCE 1. Configure a wired connection for autostart 2. Configure a WireGuard connection for autostart 3. Reboot system and login OBSERVED RESULT No network icon in the system tray EXPECTED RESULT The standard wired connection icon with the padlock addition should be in the system tray SOFTWARE/OS VERSIONS Linux/KDE Plasma: linux 5.6.2 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.
[plasma-nm] [Bug 414464] wireguard: default name not allowed, no ipv6 in "allowed ip" text box, validate input before user clicks ok
https://bugs.kde.org/show_bug.cgi?id=414464 --- Comment #1 from Bruce Anderson --- (In reply to daniel-other+kdebug from comment #0) > SUMMARY > - default name contains spaces and thus results in cancellation when > adding new VPN entry. (if name not changed) The default name will be changed to not include spaces. > > - entering a ipv6 ip in allowed ip text box leads to cancellation of > editing the entry when trying to apply it, but ipv6 ip is a legal option in > wireguard (for example 0.0.0.0, ::/0) I am unable to reproduce this problem, in fact I have used IPv6 in the Allowed IPs in all the tests I have done. I notice that in the example given, there is not a CIDR mask given on the IPv4 part though. It should actually be: "0.0.0.0/0, ::/0" so this might be the problem. What is showing when you enter this string in the Allowed IPs field? That field has an integrity check on it which should set the background color to an error color (on mine it shows red but that is theme dependent) and the OK button should be grayed out. So when you create a new WireGuard connection, you should see several fields (Private Key in the initial window and Public Key and Allowed IPs in the Peers window) should be highlighted with the error background and Save (or OK on the Peer window) should be grayed out and as you enter a correct value, the error background should go away and when all checked fields are good, the Save button should become active. Is this what you are seeing? > > - don't cancel the entry when illegal inputs are made, but rather block > user from applying the change. > Unfortunately the software architecture of plasma-nm with WireGuard being added after the rest of the interface was implemented, made this a whole lot easier for the data fields on the WireGuard Interface tab than the other tabs so that was what got implemented. A solution for the other entries (including the connection name field) is being explored. > SOFTWARE/OS VERSIONS > Linux/KDE Plasma: Arch Linux > KDE Plasma Version: 5.17.3 > KDE Frameworks Version: 5.64.0 > Qt Version: 5.13.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376277] Right clicking on a system tray icon causes keeps focus on the icon even if user has moved elsewhere
https://bugs.kde.org/show_bug.cgi?id=376277 Bruce Anderson changed: What|Removed |Added CC||banderson19...@san.rr.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 405666] Wireguard: Endpoint only allows IP addresses - not hostnames/DNS names
https://bugs.kde.org/show_bug.cgi?id=405666 Bruce Anderson changed: What|Removed |Added Resolution|--- |FIXED Assignee|jgrul...@redhat.com |banderson19...@san.rr.com Status|REPORTED|RESOLVED --- Comment #1 from Bruce Anderson --- Although not specifically mentioned there, this items was included in the fix for Bug 403548 (plasma-nm Wireguard: endpoint UI should be reworked). It has been completed and will be included in an upcoming release. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 405566] Wireguard support incomplete
https://bugs.kde.org/show_bug.cgi?id=405566 Bruce Anderson changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Assignee|jgrul...@redhat.com |banderson19...@san.rr.com --- Comment #1 from Bruce Anderson --- These items were included in the fixes for Bug 403546 (Redundant plasma-nm wireguard DNS entry in connection editor) and Bug 403548 (plasma-nm Wireguard: endpoint UI should be reworked). Both have been completed and will be included in an upcoming release. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 405501] plasma-nm is not compatible with NetworkManager 1.16's native WireGuard support
https://bugs.kde.org/show_bug.cgi?id=405501 Bruce Anderson changed: What|Removed |Added Assignee|jgrul...@redhat.com |banderson19...@san.rr.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 405501] plasma-nm is not compatible with NetworkManager 1.16's native WireGuard support
https://bugs.kde.org/show_bug.cgi?id=405501 Bruce Anderson changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Bruce Anderson --- This is going to take a while to fix because the configuration data for WireGuard connections has totally changed starting in the new version of NetworkManager. As a sidenote it appears that nm-connection-editor has not been updated to handle the change either. In the meantime to make it so the WireGuard connections do not automatically start on login you can issue: nmcli connection modify connection.autoconnect no Then to start and stop the connection unfortunately it appears you will need to use: nmcli connection because at least for me, the WireGuard connections don't show up on the popup menu to be connected using the plasma-nm interface. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 403547] plasma-nm Wireguard: redundant options offered in the Advanced configuration
https://bugs.kde.org/show_bug.cgi?id=403547 --- Comment #1 from Bruce Anderson --- The one additional parameter which is not related to the wg-quick tool directly but to the underlying wg device driver itself is FwMark which appears to be unique to the WireGuard interface and doesn't seem to have any corresponding entry method on any of the other screens. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 403347] Wireguard connection with Table=off kills internet
https://bugs.kde.org/show_bug.cgi?id=403347
--- Comment #4 from Bruce Anderson ---
(In reply to Rokas Kupstys from comment #3)
> `nmcli connection up wg21` also kills internet access. Think it is issue
> with networkmanager-wireguard plugin?
Yes, I suspect it is. As an explanation why, the nm-plasma app is really just a
user interface that sits on top of Network Manager (including
networkmanager-wireguard) which does all the actual work of interacting with
the OS networking layer.
>From looking at the output, I'm not sure that it is the "Table = off" itself
that is the problem. I know that in NetworkManager, the "PostUp" and "PreDown"
are not handled quite the same way that they are handled in wg-quick so it
*may* there that the problem lies.
There are a few things I can suggest you try.
1) Try adding only one of the routes and see what happens. I know this isn't
what you want to do but it might give another data point for debugging.
2) If 1) works, you might be able to put both of the 'ip route add ...'
commands into a shell script and put that as the PostUp command.
3) (and this is how I add extra routes although not with Table = off): look
into the use of NetworkManager's dispatcher scripts. Reading the NetworkManager
man page will give you details about this. Personally, I created the file
/etc/NetworkManager/dispatcher.d/vpn-static-links which contains:
=
#! /bin/bash
DEVICE="$1"
COMMAND="$2"
if test ${COMMAND} == "vpn-up" ; then
/bin/ip route add 107.16.144.70 via 192.168.1.1 dev eth0
/bin/ip route add 166.16.100.1 via 192.168.1.1 dev eth0
fi
==
Personally I think the third method is preferable to using the WireGuard PostUp
and PreDown configs because as long as you are using NetworkManager, it handles
things in a common way independent of the VPN protocol used. That way if I
connect through an openVPN link or through a WireGuard link it will add the two
routes either way.
--
You are receiving this mail because:
You are watching all bug changes.
[plasma-nm] [Bug 403347] Wireguard connection with Table=off kills internet
https://bugs.kde.org/show_bug.cgi?id=403347 --- Comment #2 from Bruce Anderson --- (In reply to Rokas Kupstys from comment #0) > I have wireguard connection with Table=off and some custom routes. Importing > this connection and connecting to it through plasma's network manager applet > kills internet connection. Connecting to very same connection through > `wg-quick up wg21` works as intended. > Could you please try running (from the command line): nmcli connection up wg21 and see if whether it works like wg-quick or fails like the plasma applet? Thanks. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 397572] Add support for the Wireguard plugin
https://bugs.kde.org/show_bug.cgi?id=397572 --- Comment #3 from Bruce Anderson --- I will open a review in phabricator as soon as I finish reading the documentation to figure out how to use it. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 397572] Add support for the Wireguard plugin
https://bugs.kde.org/show_bug.cgi?id=397572 Bruce Anderson changed: What|Removed |Added CC||banderson19...@san.rr.com --- Comment #1 from Bruce Anderson --- I have a nearly completed version of this at https://github.com/Druco/plasma-nm-wireguard. I have been using it for a couple of weeks in opensuse tumbleweed while I added some bells and whistles. Currently the repository is only the new vpn/wireguard directory rather than a full clone of plasma-nm but I should be ready to do a clone, fold in the new code, and do a pull request in the next few days if the devs are interested in adding this. Please let me know if there is interest for this and I will generate a pull request. -- You are receiving this mail because: You are watching all bug changes.
[tellico] [Bug 378331] tellico crashes on save with images in data file
https://bugs.kde.org/show_bug.cgi?id=378331 --- Comment #2 from Bruce Anderson <banderson19...@san.rr.com> --- Unfortunately Tumbleweed does not have the debug packages for tellico so no help there. The steps I used to recreate the problem were: 1) Load the data file 2) Add a new item 3) Select "Configure Tellico" from the "Settings" menu Note: Image Storage Options is set to "Store images in common application directory" even though the images were previously stored in the data file. 4) Check the "Store images in data file" box and click Apply. 5) A dialog box pops up saying something like, some of the images are not stored in data file, do you want to save and I clicked Yes At this point the file starts saving and continues to completion (i.e. shows 100% in the progress bar) at which point the application crashes. Restarting the application, all of the items are present including the item added in step 2. Going into the configure dialog, it is back set to "Store images in common application directory". In hopes of getting some additional debug information, I downloaded the source and compiled it and tried the same set of steps and fortunately or unfortunately, I'm not sure which, it did not crash this time. Also starting the Tumbleweed supplied application, the confituration now shows "Store images in data file" and saving the file works fine without crashing (although I didn't need to change the image storage location because it was already set to what I wanted). My suspicion is that the crash occurs while saving the changed configuration file but I don't have any proof of this. It's probably not significant but I have the environment variables KDEHOME, XDG_CONFIG_HOME, and XDG_DATA_HOME all set to non-default directories. The good news in this is that the problem does not appear to be in the code as compiling from source works just fine so it must be a problem with the Tumbleweed compilation. And from my point of view, now that the storage location is set to what I want it to be, even the Tumbleweed version works fine so I don't have to stick with source version and can continue getting updates. Thanks, Bruce Anderson On 04/08/2017 05:52 PM, Robby Stephenson wrote: > https://bugs.kde.org/show_bug.cgi?id=378331 > > --- Comment #1 from Robby Stephenson <ro...@periapsis.org> --- > I'm having trouble re-producing this. Does it crash right after you change the > setting or after closing the config dialog and saving the data file? > > Do you know if Tumbleweed has debug packages for including the backtrace from > Tellico? Right now, the backtrace just shows a few items from the underlying > KDE and Qt libraries, which makes it hard to tell where in Tellico the crash > is > occurring > -- You are receiving this mail because: You are watching all bug changes.
[tellico] [Bug 378331] New: tellico crashes on save with images in data file
https://bugs.kde.org/show_bug.cgi?id=378331 Bug ID: 378331 Summary: tellico crashes on save with images in data file Product: tellico Version: 3.0.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: ro...@periapsis.org Reporter: banderson19...@san.rr.com Target Milestone: --- Application: tellico (3.0.2) Qt Version: 5.7.1 Frameworks Version: 5.32.0 Operating System: Linux 4.9.16-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I set the "Image Storage Options" to "Store images in data file" and saved. File completes saving but then the application crashes. The data file has 3027 entries and almost all have images associated with them. On restarting the application, the storage option is set back to "Store images in common application directory". The crash can be reproduced every time. -- Backtrace: Application: Tellico (tellico), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0ad86eee00 (LWP 4496))] Thread 3 (Thread 0x7f0ab3a03700 (LWP 4498)): #0 0x7f0acee377bd in poll () at /lib64/libc.so.6 #1 0x7f0ac7b42a86 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f0ac7b42b9c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f0acfa6d18b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f0acfa16aea in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f0acf844813 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f0ad2bfd385 in () at /usr/lib64/libQt5DBus.so.5 #7 0x7f0acf8494c8 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f0acb71e537 in start_thread () at /lib64/libpthread.so.0 #9 0x7f0acee4104f in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f0aba802700 (LWP 4497)): #0 0x7f0acee377bd in poll () at /lib64/libc.so.6 #1 0x7f0ac9f3c3e0 in () at /usr/lib64/libxcb.so.1 #2 0x7f0ac9f3e179 in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7f0abcb28889 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f0acf8494c8 in () at /usr/lib64/libQt5Core.so.5 #5 0x7f0acb71e537 in start_thread () at /lib64/libpthread.so.0 #6 0x7f0acee4104f in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f0ad86eee00 (LWP 4496)): [KCrash Handler] #6 0x7f0ad0efd234 in KPageDialog::button(QDialogButtonBox::StandardButton) const () at /usr/lib64/libKF5WidgetsAddons.so.5 #7 0x0048a886 in () #8 0x00513645 in () #9 0x7f0acfa44709 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5 #10 0x7f0ad07ef722 in QAbstractButton::clicked(bool) () at /usr/lib64/libQt5Widgets.so.5 #11 0x7f0ad07ef974 in () at /usr/lib64/libQt5Widgets.so.5 #12 0x7f0ad07f0d67 in () at /usr/lib64/libQt5Widgets.so.5 #13 0x7f0ad07f0f44 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () at /usr/lib64/libQt5Widgets.so.5 #14 0x7f0ad074e588 in QWidget::event(QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #15 0x7f0ad0706eac in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #16 0x7f0ad070f51d in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #17 0x7f0acfa18b00 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #18 0x7f0ad070dbcd in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () at /usr/lib64/libQt5Widgets.so.5 #19 0x7f0ad0768c06 in () at /usr/lib64/libQt5Widgets.so.5 #20 0x7f0ad076b613 in () at /usr/lib64/libQt5Widgets.so.5 #21 0x7f0ad0706eac in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #22 0x7f0ad070e661 in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #23 0x7f0acfa18b00 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #24 0x7f0acff65c43 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () at /usr/lib64/libQt5Gui.so.5 #25 0x7f0acff677c5 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () at /usr/lib64/libQt5Gui.so.5 #26 0x7f0acff4575b in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () at /usr/lib64/libQt5Gui.so.5 #27 0x7f0abcb5f210 in () at /usr/lib64/libQt5XcbQpa.so.5 #28 0x7f0ac7b42887 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #29 0x7f0ac7b42af0 in () at /usr/lib64/libglib-2.0.so.0 #30 0x7f0ac7b42b9c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #31 0x7f0acfa6d16f in
