[plasma-nm] [Bug 448576] No F5 protocol support in plasma-nm-openconnect
https://bugs.kde.org/show_bug.cgi?id=448576 George Seaton changed: What|Removed |Added Platform|RedHat RPMs |unspecified -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 448576] New: No F5 protocol support in plasma-nm-openconnect
https://bugs.kde.org/show_bug.cgi?id=448576 Bug ID: 448576 Summary: No F5 protocol support in plasma-nm-openconnect Product: plasma-nm Version: unspecified Platform: RedHat RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: jgrul...@redhat.com Reporter: george.sea...@iinet.net.au Target Milestone: --- SUMMARY Request for feature. plasma-nm-openconnect widget/plasmoid doesn't appear to support openconnect protocol f5 (BigIP f5). Can this be added. STEPS TO REPRODUCE 1. open plasma-nm widget, no openconnect F5 protocol available to use 2. 3. OBSERVED RESULT no openconnect F5 protocol available EXPECTED RESULT f5 protocol available SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION manually created config in /etc/NetworkManager/system-connections/ appears to work in widget so long as no changes are attempted otherwise the f5 protocol is overwritten in the config -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 370972] Scanned image is bad
https://bugs.kde.org/show_bug.cgi?id=370972 --- Comment #32 from George Seaton --- Removing the Skanliterc in SL7 fixes the broken colour image for me in SL7 (RHEL7). If I then restart skanlite then I get the broken colour image preview again. Looks like it has to be deleted every time. The skanlite rpm packages are being supplied by the epel repository skanlite.x86_641.1-8.el7 @epel Regards, George -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 370972] Scanned image is bad
https://bugs.kde.org/show_bug.cgi?id=370972 George Seaton <george.sea...@iinet.net.au> changed: What|Removed |Added CC||george.sea...@iinet.net.au --- Comment #13 from George Seaton <george.sea...@iinet.net.au> --- I have seen the same issue on Scientific Linux 7 and Fedora 27. The strange thing about this issue is that for me it works OK just after a clean install. If I go back after a few weeks skanlite then gives me the corrupted image. If I use simple-scan the scanning works as expected. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 364619] New: kcm_grub2 editor stopped working in Fedora 24
https://bugs.kde.org/show_bug.cgi?id=364619 Bug ID: 364619 Summary: kcm_grub2 editor stopped working in Fedora 24 Product: systemsettings Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: george.sea...@inbox.com Application: kcmshell4 (4.14.19) KDE Platform Version: 4.14.20 Qt Version: 4.8.7 Operating System: Linux 4.5.7-300.fc24.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: trying to start kcm_grub2 grub2 editor in Fedora 24 - Unusual behavior I noticed: On initial startup utility window opens but is completely blank. seems to be dbus errors The crash can be reproduced every time. -- Backtrace: Application: KDE Control Module (kcmshell4), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [KCrash Handler] #6 0x7f95e5ae76f5 in raise () at /lib64/libc.so.6 #7 0x7f95e5ae92fa in abort () at /lib64/libc.so.6 #8 0x7f95e28c0d04 in _dbus_abort () at /lib64/libdbus-1.so.3 #9 0x7f95e28b773c in () at /lib64/libdbus-1.so.3 #10 0x7f95e28a7c82 in dbus_message_new_method_call () at /lib64/libdbus-1.so.3 #11 0x7f95e7df22c8 in QDBusMessagePrivate::toDBusMessage(QDBusMessage const&, QFlags, QDBusError*) () at /lib64/libQtDBus.so.4 #12 0x7f95e7ded8ba in QDBusConnectionPrivate::sendWithReply(QDBusMessage const&, int, int) () at /lib64/libQtDBus.so.4 #13 0x7f95e7defbd7 in QDBusConnectionPrivate::findMetaObject(QString const&, QString const&, QString const&, QDBusError&) () at /lib64/libQtDBus.so.4 #14 0x7f95e7dfcc4b in QDBusInterfacePrivate::QDBusInterfacePrivate(QString const&, QString const&, QString const&, QDBusConnection const&) () at /lib64/libQtDBus.so.4 #15 0x7f95e7dfcd95 in QDBusInterface::QDBusInterface(QString const&, QString const&, QString const&, QDBusConnection const&, QObject*) () at /lib64/libQtDBus.so.4 #16 0x7f95e8eb7047 in KCMShell::isRunning() () at /lib64/libkdeinit4_kcmshell4.so #17 0x7f95e8eb890f in kdemain () at /lib64/libkdeinit4_kcmshell4.so #18 0x7f95e5ad3731 in __libc_start_main () at /lib64/libc.so.6 #19 0x55e1fe6dc8e9 in _start () Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
