[konsole] [Bug 482481] New: Konsole forces full hinting (hintfull) despite both fontconfig and KDE settings
https://bugs.kde.org/show_bug.cgi?id=482481 Bug ID: 482481 Summary: Konsole forces full hinting (hintfull) despite both fontconfig and KDE settings Classification: Applications Product: konsole Version: 24.02.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: font Assignee: konsole-de...@kde.org Reporter: borisb@gmail.com Target Milestone: --- SUMMARY I upgraded to KDE 6 today and found that Konsole now renders terminal fonts with full hinting. This looks awful with some fonts. The rest of the OS (even Konsole's own Appearance window) is respecting my global fontconfig (/usr/share/local.conf) and KDE System Settings -> Fonts, both of which set the font hinting to Slight. STEPS TO REPRODUCE 1. Make sure your system configuration is set to slight hinting. 2. Start Konsole and go to "Edit Current Profile" -> "Appearance" -> "Select Font". OBSERVED RESULT Observe live the difference between font rendering in the Appearance preview sample and the actual terminal font behind it. Bold fonts with higher sizes show more difference. Not all fonts are affected the same. EXPECTED RESULT Konsole should follow the system settings and fontconfig for font hinting. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.8-arch1-1 (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION Globally turning on autohinting makes it somewhat better (as in at least the rendering is the same as for the rest of the system) but is not a solution. However it does indicate that not _all_ settings are overridden by Konsole. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478851] "Task manager" mode: Pinned icons should be replaced by opened programs
https://bugs.kde.org/show_bug.cgi?id=478851 --- Comment #11 from Boris Gonzalez --- (In reply to ezh from comment #10) > What is the point of having it separate by default why one want that > behavior? And with a very hidden and not clear checkbox? > > I am sure it should be defaulted to "not separate". I agree with ezh, last time I saw the behaviour of using "keep launchers separate" was with those small icons you could pin in windows xp -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 480658] New: cursor escaping to another screen when only 1 was selected
https://bugs.kde.org/show_bug.cgi?id=480658 Bug ID: 480658 Summary: cursor escaping to another screen when only 1 was selected Classification: Applications Product: systemsettings Version: 5.93.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_tablet Assignee: plasma-b...@kde.org Reporter: borgon...@gmail.com CC: aleix...@kde.org Target Milestone: --- Created attachment 165426 --> https://bugs.kde.org/attachment.cgi?id=165426=edit video of the issue 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. set screens in vertical alignment in wayland 2. set drawing tablet to only move in top screen 3. set area as "fit output in tablet" 3. move pen around the bottom of the tablet OBSERVED RESULT cursor shows on an area of the bottom screen EXPECTED RESULT cursor gets clipped to the bottom of the top screen as in x11 SOFTWARE/OS VERSIONS Linux/KDE Plasma: plasma6 RC2 (available in About System) KDE Plasma Version: 5.93.0 KDE Frameworks Version: 5.249.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION wayland drawing tablet doesnt match the ratio of the screen set as active -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 480656] New: Pin elements not working as intended in plasma6 RC2
https://bugs.kde.org/show_bug.cgi?id=480656 Bug ID: 480656 Summary: Pin elements not working as intended in plasma6 RC2 Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: borgon...@gmail.com Target Milestone: --- Created attachment 165425 --> https://bugs.kde.org/attachment.cgi?id=165425=edit classic task manager, dolphin pinned and opened but double icon showing 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 plasma6 RC2 2. right click on task manager, show alternatives 3. change only icons task manager to "task manager (classic taskbar icons and text)" 4. click on any of the pin elements 5. double icon displayed on task manager 6. click again on the same pin element 7. another window opens as if middle click OBSERVED RESULT doble icon entry for the same element click not selecting and showing the corresponding window but instead opens new window EXPECTED RESULT should work as kde5 SOFTWARE/OS VERSIONS Linux/KDE Plasma: Plasma6 RC2 (available in About System) KDE Plasma Version: 5.93.0 KDE Frameworks Version: 5.249.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION wayland double monitor -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 479541] Orientation (rotation) option on drawing tablet settings not available
https://bugs.kde.org/show_bug.cgi?id=479541 --- Comment #8 from Boris Gonzalez --- (In reply to Joshua Goins from comment #6) > This may be fixed upstream by > https://gitlab.freedesktop.org/libinput/libinput/-/commit/ > 11a7de7640e2f461719c3aa5b88648fba4931f92, will see once reporter comes back > with more info what happened in the end? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 479541] Orientation (rotation) option on drawing tablet settings not available
https://bugs.kde.org/show_bug.cgi?id=479541 --- Comment #7 from Boris Gonzalez --- Created attachment 164848 --> https://bugs.kde.org/attachment.cgi?id=164848=edit evtest for the HUION huion tablet pen added the output of evtest for the HUION huion tablet pen -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 479541] Orientation (rotation) option on drawing tablet settings not available
https://bugs.kde.org/show_bug.cgi?id=479541 --- Comment #2 from Boris Gonzalez --- Created attachment 164756 --> https://bugs.kde.org/attachment.cgi?id=164756=edit libinput list-devices added output of "libinput list-devices" -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 479541] New: Orientation (rotation) option on drawing tablet settings not available
https://bugs.kde.org/show_bug.cgi?id=479541 Bug ID: 479541 Summary: Orientation (rotation) option on drawing tablet settings not available Classification: Plasma Product: wacomtablet Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jazzv...@gmail.com Reporter: borgon...@gmail.com Target Milestone: --- Created attachment 164753 --> https://bugs.kde.org/attachment.cgi?id=164753=edit screenshot SUMMARY *** Orientation (rotation) option on drawing tablet settings not available *** STEPS TO REPRODUCE 1. connect tablet to computer 2. open drawing tablet settings OBSERVED RESULT Option to rotate drawing tablet is grey and cant be changed EXPECTED RESULT Option to rotate drawing tablet is available and tablet input can be rotated SOFTWARE/OS VERSIONS Linux/KDE Plasma: neon-unstable-20240104-1507.iso (available in About System) KDE Plasma Version: KDE PLASMA 6 BETA ADDITIONAL INFORMATION usb screenless drawing tablet problem has been present since drawing tablets started being supported in plasma 5 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfigwidgets] [Bug 460868] Kate slow to open if networked document in "open recent" list not available
https://bugs.kde.org/show_bug.cgi?id=460868 Boris Egorov changed: What|Removed |Added CC||ego...@linux.com --- Comment #8 from Boris Egorov --- Nice fix. Now your recent items will not disappear when the drive (with location of recent item) is not mounted. I've seen this history loss a few times and I wanted to fix it. But it is already done now. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461503] New: Drag and drop not working on Wayland with maximized windows
https://bugs.kde.org/show_bug.cgi?id=461503 Bug ID: 461503 Summary: Drag and drop not working on Wayland with maximized windows Classification: Plasma Product: kwin Version: 5.26.2 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: borgon...@gmail.com Target Milestone: --- SUMMARY Drag and drop doesnt work on wayland if the taskbar is set to autohide when draging files from a maximized window STEPS TO REPRODUCE 1. Login into a wayland plasma session 2. Move the task bar (panel) to the left side 3. Set the task bar visibility to "auto hide" 4. Drag a file from a maximized window 5. Drop it on another window OBSERVED RESULT The task bar remains hidden when the mouse cursor with the dragged file is touching the left side of the screen, making it impossible to select a destination window except the original one EXPECTED RESULT Just like in X11, drag and drop between two maximized windows or applications, drag a file, you put mouse on the left side, task bar comes up, you hover the cursor on the taskbar for a second over the window you want, the window you want comes up you, drop your file there SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.0.7 (available in About System) KDE Plasma Version: 6.26.2 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.7 ADDITIONAL INFORMATION no -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 451337] New: "Cross-channel adjustment curves" not available on Shortcuts settings
https://bugs.kde.org/show_bug.cgi?id=451337 Bug ID: 451337 Summary: "Cross-channel adjustment curves" not available on Shortcuts settings Product: krita Version: 5.0.2 Platform: Appimage OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Shortcuts and Canvas Input Settings Assignee: krita-bugs-n...@kde.org Reporter: borgon...@gmail.com Target Milestone: --- Created attachment 147411 --> https://bugs.kde.org/attachment.cgi?id=147411=edit screenshot krita shortcut settings Filter "Cross-channel adjustment curves" does not appear on the list of actions in the shortcut section of krita settings, due to that is not possible to assign a short cut to it. Not to be confused with "Color adjustments curves" ⚠️ "Cross-channel adjustment curves" can be found in: Filters -> Adjust -> Cross-channel adjustment curves STEPS TO REPRODUCE 1. Settings -> Configure Krita -> Shortcuts 2. Search or try to find "Cross-channel adjustment curves" OBSERVED RESULT "Cross-channel color adjustment" does not appear in the list as an action that a hotkey can be assigned EXPECTED RESULT is possible to assign a shortcut to "Cross-channel adjustment curves" SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 36 KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION none -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 419867] Unable to use scrollwheel on desktop to change Virtual Desktop
https://bugs.kde.org/show_bug.cgi?id=419867 --- Comment #57 from Dr. Boris Neubert --- I have a current KUbuntu 21.10. I just added a new user for testing purposes with default settings. Then added 4 desktops in a row. It does not switch desktops when scrolling with the mouse wheel. Turning from folder view to desktop view makes the mouse wheel work. So it was easy to reproduce for me. Only thing I can think off what could make a difference is the screen resolution: 3840x2160 60 Hz on a Samsung U28D590 connected via DisplayPort. I volunteer to demonstrate it in a screen sharing session if that would help. My time zone is UTC+1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 419867] Unable to use scrollwheel on desktop to change Virtual Desktop
https://bugs.kde.org/show_bug.cgi?id=419867 --- Comment #45 from Dr. Boris Neubert --- 1. Plasma 5.22.5 2. 4 desktops in 1 row 3. yes 4. there are about 15 icons, desktop not scrollable I have a tool bar at the left edge of the screen, in the middle, height approx. one fifth. Mouse-wheel scrolling works in the area the width of the toolbar that is not covered by the tool bar -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 441527] New: Plasma crash after login
https://bugs.kde.org/show_bug.cgi?id=441527 Bug ID: 441527 Summary: Plasma crash after login Product: plasmashell Version: 5.22.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: bo...@bori.org CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.22.4) Qt Version: 5.15.2 Frameworks Version: 5.85.0 Operating System: Linux 5.13.12-1-default x86_64 Windowing System: X11 Drkonqi Version: 5.22.4 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I had just logged in after a reboot - Custom settings of the application: Panel on top. Extra panel on second screen and analog clock widget on second screen. I think it started after I tried wayland once (it didn't happen on wayland). This now happens regularly on xorg. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [KCrash Handler] #4 0x7f1bed079834 in DBusMenuImporter::menu() const (this=0x0) at /usr/src/debug/plasma5-workspace-5.22.4-614.8.x86_64/libdbusmenuqt/dbusmenuimporter.cpp:333 #5 0x7f1bed069506 in operator() (menu=0x563bd5cd60d0, __closure=0x563bd5df2390) at /usr/src/debug/plasma5-workspace-5.22.4-614.8.x86_64/dataengines/statusnotifieritem/statusnotifieritemsource.cpp:388 #6 QtPrivate::FunctorCall, QtPrivate::List, void, StatusNotifierItemSource::refreshCallback(QDBusPendingCallWatcher*):: >::call (arg=, f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:146 #7 QtPrivate::Functor, 1>::call, void> (arg=, f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:256 #8 QtPrivate::QFunctorSlotObject, 1, QtPrivate::List, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=0x563bd5df2380, r=, a=, ret=) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:443 #9 0x7f1c5c7edfd3 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7fffc8e8a230, r=0x563bd3aa1140, this=0x563bd5df2380) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #10 doActivate(QObject*, int, void**) (sender=0x563bd2aee8f0, signal_index=3, argv=0x7fffc8e8a230) at kernel/qobject.cpp:3886 #11 0x7f1c5c7e749f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x563bd2aee8f0, m=, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fffc8e8a230) at kernel/qobject.cpp:3946 #12 0x7f1bed07ca72 in DBusMenuImporter::menuUpdated(QMenu*) (_t1=0x563bd5cd60d0, this=) at /usr/src/debug/plasma5-workspace-5.22.4-614.8.x86_64/build/libdbusmenuqt/dbusmenuqt_autogen/include/moc_dbusmenuimporter.cpp:212 #13 DBusMenuImporter::slotGetLayoutFinished(QDBusPendingCallWatcher*) (this=, watcher=) at /usr/src/debug/plasma5-workspace-5.22.4-614.8.x86_64/libdbusmenuqt/dbusmenuimporter.cpp:461 #14 0x7f1c5c7edfd3 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7fffc8e8a370, r=0x563bd2aee8f0, this=0x563bd2abd3a0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #15 doActivate(QObject*, int, void**) (sender=0x563bd3adacb0, signal_index=3, argv=0x7fffc8e8a370) at kernel/qobject.cpp:3886 #16 0x7f1c5c7e749f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=, m=m@entry=0x7f1c5d2535c0 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fffc8e8a370) at kernel/qobject.cpp:3946 #17 0x7f1c5d233fff in QDBusPendingCallWatcher::finished(QDBusPendingCallWatcher*) (this=, _t1=) at .moc/moc_qdbuspendingcall.cpp:158 #18 0x7f1c5c7e3f7e in QObject::event(QEvent*) (this=0x563bd3adacb0, e=0x7f1c48086410) at kernel/qobject.cpp:1314 #19 0x7f1c5d549a7f in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x563bd3adacb0, e=0x7f1c48086410) at kernel/qapplication.cpp:3632 #20 0x7f1c5c7b798a in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x563bd3adacb0, event=0x7f1c48086410) at kernel/qcoreapplication.cpp:1064 #21 0x7f1c5c7ba9d7 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (receiver=0x0, event_type=0, data=0x563bd209c0c0) at kernel/qcoreapplication.cpp:1821 #22 0x7f1c5c80f7e3 in postEventSourceDispatch(GSource*, GSourceFunc, gpointer) (s=s@entry=0x563bd21f01e0) at kernel/qeventdispatcher_glib.cpp:277 #23 0x7f1c5aad880f in g_main_dispatch (context=0x7f1c50005000) at ../glib/gmain.c:3337 #24 g_main_context_dispatch (context=0x7f1c50005000) at ../glib/gmain.c:4055 #25 0x7f1c5aad8b98 in g_main_context_iterate (context=context@entry=0x7f1c50005000, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4131 #26 0x7f1c5aad8c4f in g_main_context_iteration (context=0x7f1c50005000, may_block=1) at
[plasmashell] [Bug 419867] Bouncing when changing virtual desktop through touchpad or mouse wheel scroll when there are only two virtual desktops and navigation wrap is on
https://bugs.kde.org/show_bug.cgi?id=419867 --- Comment #35 from Dr. Boris Neubert --- The issue is still present in 5.21.4 with 3, 4 or 5 desktops and no matter if wrap around is turned on or off. With a sidebar that does not cover the entire edge of the virtual desktop, scrolling the mouse wheel in the area that is not covered by the sidebar works. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 440046] Unable to execute kirigami-based applications because of a symbol lookup error
https://bugs.kde.org/show_bug.cgi?id=440046 Boris Petrov changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Boris Petrov --- The issue was fixed by deleting the file reported in the error. Sorry for the noise... -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 440047] Unable to execute kirigami-based applications because of a symbol lookup error
https://bugs.kde.org/show_bug.cgi?id=440047 Boris Petrov changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Boris Petrov --- It turns out that deleting the file reported in the error solves the issue. Sorry for the noise... -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 440047] New: Unable to execute kirigami-based applications because of a symbol lookup error
https://bugs.kde.org/show_bug.cgi?id=440047 Bug ID: 440047 Summary: Unable to execute kirigami-based applications because of a symbol lookup error Product: frameworks-kirigami Version: Master Platform: Compiled Sources OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: boris.v.pet...@protonmail.com Target Milestone: Not decided SUMMARY After successfully building kclock and its dependencies (with kdesrc-build), I can't get it to run. I am now also unable to launch other kirigami-based applications I built previously like kweather or audiotube. STEPS TO REPRODUCE 1. Build any kirigami-based application, including its dependencies For example: kdesrc-build kclock --include-dependencies 2. Source prefix.sh For example: source ~/kde/build/kdereview/kclock/prefix.sh 3. Execute the program that was just built For example: kclock OBSERVED RESULT I get the following error: kclock: symbol lookup error: /home/borisp/dev/kde/usr/lib/plugins/kf5/kirigami/org.kde.desktop.so: undefined symbol: _ZNK11KIconLoader16hasCustomPaletteEv EXPECTED RESULT The application (in this case kclock) should launch normally. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.13.1-3 (available in About System) KDE Plasma Version: 5.22.3 KDE Frameworks Version: Master Qt Version: 5.15 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 440046] New: Unable to execute kirigami-based applications because of a symbol lookup error
https://bugs.kde.org/show_bug.cgi?id=440046 Bug ID: 440046 Summary: Unable to execute kirigami-based applications because of a symbol lookup error Product: frameworks-kirigami Version: Master Platform: Compiled Sources OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: boris.v.pet...@protonmail.com Target Milestone: Not decided SUMMARY After successfully building kclock and its dependencies (with kdesrc-build), I can't execute it. After that building, I am also unable to launch other kirigami-based applications I built previously like kweather or audiotube. STEPS TO REPRODUCE 1. Build any kirigami-based application, including its dependencies For example: kdesrc-build kclock --include-dependencies 2. Source prefix.sh For example: source ~/kde/build/kdereview/kclock/prefix.sh 3. Execute the program that was just built For example: kclock OBSERVED RESULT I get the following error: kclock: symbol lookup error: /home/borisp/dev/kde/usr/lib/plugins/kf5/kirigami/org.kde.desktop.so: undefined symbol: _ZNK11KIconLoader16hasCustomPaletteEv EXPECTED RESULT The application (in this case kclock) should launch normally. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.13.1-3 (available in About System) KDE Plasma Version: 5.22.3 KDE Frameworks Version: Master Qt Version: 5.15 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 433254] plasma network-manager fails to connect to PAN GP vpn
https://bugs.kde.org/show_bug.cgi?id=433254 --- Comment #5 from Boris --- Anyone knows how to raise bug priority or escalate it? New Plasma software versions are coming but this trifling bug is still hanging not resolved and drags on from version to version. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 433254] plasma network-manager fails to connect to PAN GP vpn
https://bugs.kde.org/show_bug.cgi?id=433254 --- Comment #4 from Boris --- (In reply to Daniel Morales Salas from comment #3) > Hello, I can confirm the same bug under Kubuntu 21.04, fresh install. After > applying the Andrei workaround I can confirm that now under network manager > applet protocol is gp but if I try to connect using the applet, dialog box > does not offer any option to set the username and password so I cannot use > the applet to connect to the global protect vpn. Can I put username and > password in > "/etc/NetworkManager/system-connections/[connection-name].nmconnection" at > least? how? > > Thanks! I don't have this. After specifying gp as protocol in .nmconnection file it works as it should asking creds and so on. Did you change anything else in .nmconnection file in addition to "protocol" line? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 432955] enabling WYTIWYG comments
https://bugs.kde.org/show_bug.cgi?id=432955 Boris Petrov changed: What|Removed |Added CC||boris.v.petrov@protonmail.c ||om --- Comment #1 from Boris Petrov --- Hi, I can't try this on Windows but on my Linux installation (same version of Kate though), there is the section Indentation in the Tools' menu which determines (I think because it works on my side, but I'm not sure) whether characters are automatically inserted or not. Could you try to set it to None and see if characters are still inserted ? If this solves it, I guess this bug can be closed. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 433254] plasma network-manager fails to connect to PAN GP vpn
https://bugs.kde.org/show_bug.cgi?id=433254 --- Comment #2 from Boris --- (In reply to Andrei Slavoiu from comment #1) > Confirming. I had my PAN GP configured and working fine for several months. > Today, after changing the gateway for an experiment, I couldn't get it to > work with either the new or old gateway. Turns out saving the configuration > changed the protocol from PAN GP to Pulse and it was impossible to change it > back to PAN GP from the UI, it kept being changed to Pulse when saving the > config. > > Workaround: stop NetworkManager service and manually edit the connection > file, in the section [vpn] replace line "protocol=pulse" with "protocol=gp", > start the NetworkManager service back. As long a plasma-nm is only used to > connect/disconnect from VPN everithing is fine. > > Linux: 5.11.2 > KDE Plasma Version: 5.21.2 > KDE Frameworks Version: 5.79.0 > Qt Version: 5.15.2 > NetworkNamager version: 1.28.0 > openconnect version: 8.10 Great catch, Andrei! In turn I confirm that your workaround works - editing "/etc/NetworkManager/system-connections/[connection-name].nmconnection" makes it work as it should. Dear developers, please fix it. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 433254] plasma network-manager fails to connect to PAN GP vpn
https://bugs.kde.org/show_bug.cgi?id=433254 Boris changed: What|Removed |Added CC||boris.zuba...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 433254] New: plasma network-manager fails to connect to PAN GP vpn
https://bugs.kde.org/show_bug.cgi?id=433254 Bug ID: 433254 Summary: plasma network-manager fails to connect to PAN GP vpn Product: plasma-nm Version: 5.21.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: jgrul...@redhat.com Reporter: boris.zuba...@gmail.com Target Milestone: --- SUMMARY After recent KDE update ability to connect to PAN GP from NM applet in Plasma is lost. Command line openconnect app works flawlessly. NetworkManager-openconnect and plasma-nm5-openconnect packages are installed. STEPS TO REPRODUCE 1. Open Network Connections configuration of NM applet. 2. Press "+" for adding new connection and choose "PAN Global Protect", press "Create". "New connection (vpn)" window appears. 3. Type in vpn gate address, press "Save", close "Connections" window. 4. Go to tray, press NM applet's icon, choose newly created vpn connection and poress "Connect". Login screen appears. 5. Enter creds, press login button - no connection appears with 404 error in log. 6. Go back to NM applet in tray, choose vpn connection, right click on it and press "Configure". See that "Pulse Secure" is being chosen in protocol field instead of "PAN Global Protect". OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 431635] Strange behavior with text selection in some rare PDF files
https://bugs.kde.org/show_bug.cgi?id=431635 Boris Petrov changed: What|Removed |Added Summary|Wrong text selection for|Strange behavior with text |documents made with LaTeX |selection in some rare PDF ||files -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 431635] Wrong text selection for documents made with LaTeX
https://bugs.kde.org/show_bug.cgi?id=431635 --- Comment #5 from Boris Petrov --- You are right, the PDF is really strange. This issue is one of many I encounter while selecting text in this document whereas before it, I've never stumbled upon anything like that. I don't know how it was made, but the funny thing is that I have received two different PDFs from two different persons with the same issues. Might it be related to the fact that the two of them were transferred through Moodle (this being the other common thing between the two in addition to LaTeX)? I don't know, I'm just curious how these things come to happen. All in all, as you said, it's not really an issue with Okular. I'll change the title. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 431635] Wrong text selection for documents made with LaTeX
https://bugs.kde.org/show_bug.cgi?id=431635 Boris Petrov changed: What|Removed |Added Summary|Wrong text selection for|Wrong text selection for |uncommon characters |documents made with LaTeX -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 431635] Wrong text selection for uncommon characters
https://bugs.kde.org/show_bug.cgi?id=431635 --- Comment #3 from Boris Petrov --- I did some tests and apparently it's only happening when the PDF was made with LaTeX. The same characters in LaTeX documents having problems with Okular don't have any issue if they are found in, for instance, a document made with LibreOffice. Therefore, I guess it's not an issue with Okular but rather with LaTeX. I don't know if something can be done on Okular's side, so I'll leave it open for the time being but feel free to close it if nothing can be done. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 431635] Wrong text selection for uncommon characters
https://bugs.kde.org/show_bug.cgi?id=431635 --- Comment #2 from Boris Petrov --- Oops, just saw a few typos in my initial report, too bad I can't edit it... Sorry for that. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 431635] Wrong text selection for uncommon characters
https://bugs.kde.org/show_bug.cgi?id=431635 --- Comment #1 from Boris Petrov --- Created attachment 134888 --> https://bugs.kde.org/attachment.cgi?id=134888=edit Pdf containing uncommon characters -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 431635] New: Wrong text selection for uncommon characters
https://bugs.kde.org/show_bug.cgi?id=431635 Bug ID: 431635 Summary: Wrong text selection for uncommon characters Product: okular Version: 20.12.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: boris.v.pet...@protonmail.com Target Milestone: --- Created attachment 134886 --> https://bugs.kde.org/attachment.cgi?id=134886=edit Video showing the bug SUMMARY STEPS TO REPRODUCE 1. Open any pdf (tested with two) containing uncommon characters (see attachments) 2. Try to select the said characters with the text selection tool OBSERVED RESULT The selection tool selects more than just the character, somehow selecting the line below as well. This can be seen when trying to copy the selection (in Kate for instance). It not only copies the character but also the line below it (if there is one, else it copies only the selected text, as expected). I thought it might be an issue with the pdf but trying the same thing with Firefox's pdf reader doesn't give me this behavior so it has something to do with Okular. EXPECTED RESULT The selection tool should behave the same way with those uncommon characters. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro 20.2 (available in About System) KDE Plasma Version: KDE Plasma 5.20.4 KDE Frameworks Version: 5.77 Qt Version: 5.15 ADDITIONAL INFORMATION I noticed that when trying to read with Okular a txt file with those characters in it, Okular fails to do it. Maybe something to do with the encoding? Also not related to the bug, but just want to thank every contributor to Okular, it really is an amazing tool! -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 413751] Open links in LSP tooltips
https://bugs.kde.org/show_bug.cgi?id=413751 Boris Egorov changed: What|Removed |Added CC||ego...@linux.com --- Comment #3 from Boris Egorov --- Created attachment 134839 --> https://bugs.kde.org/attachment.cgi?id=134839=edit Tooltip example I've made a screenshot with mentioned tooltip. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 389052] Desired connections run away just before clicking the "connect" button or entering password
https://bugs.kde.org/show_bug.cgi?id=389052 --- Comment #16 from Boris --- (In reply to Boris from comment #15) > Created attachment 134313 [details] > attachment-30706-0.html > > Waiting didn't work for me, they kept jumping around. So yes, no internet > means unusable in my case. > > Sent from my mobile > > On Thu, 24 Dec 2020, 17:44 Nate Graham, wrote: > > > https://bugs.kde.org/show_bug.cgi?id=389052 > > > > --- Comment #14 from Nate Graham --- > > I agree that it's an annoying issue that needs to be fixed, but "makes > > Kubuntu > > totally unusable" strikes me as a slight exaggeration given that the > > workaround > > is to simply wait a few seconds first. :) > > > > -- > > You are receiving this mail because: > > You voted for the bug. > > You are on the CC list for the bug. I don't know if this helps, but this issue does not occur when I switch to kde on my opensuse desktop where the network was already configured before installing kde. (It does happen when I boot from the kubuntu live usb on the same system.) -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 389052] Desired connections run away just before clicking the "connect" button or entering password
https://bugs.kde.org/show_bug.cgi?id=389052 --- Comment #15 from Boris --- Waiting didn't work for me, they kept jumping around. So yes, no internet means unusable in my case. Sent from my mobile On Thu, 24 Dec 2020, 17:44 Nate Graham, wrote: > https://bugs.kde.org/show_bug.cgi?id=389052 > > --- Comment #14 from Nate Graham --- > I agree that it's an annoying issue that needs to be fixed, but "makes > Kubuntu > totally unusable" strikes me as a slight exaggeration given that the > workaround > is to simply wait a few seconds first. :) > > -- > You are receiving this mail because: > You voted for the bug. > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 389052] Desired connections run away just before clicking the "connect" button or entering password
https://bugs.kde.org/show_bug.cgi?id=389052 Boris changed: What|Removed |Added CC||bo...@bori.org --- Comment #13 from Boris --- I have the same issue (without VPN, just Wi-Fi) on Kubuntu 20.10. Is there a way (apart from voting) to change the priority of this issue? I'm really surprised this has been hanging here for almost 3 years. This makes Kubuntu totally unusable for my girlfriend and I'd guess for everyone else who relies on WiFi. It also really limits the options to find a good looking distro for newbies when KDE is not an option. (Troubleshooting and finding a workaround is not an option when trying to convince someone to switch from Windows to Linux. Internet has to work on first boot.) -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 368434] Kontact crash when filing through eMail
https://bugs.kde.org/show_bug.cgi?id=368434 --- Comment #9 from Boris Bigott --- This problem has long "gone away". It is so long ago that I do not remember what fixed it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 419867] Bouncing when changing virtual desktop through touchpad or mouse wheel scroll (broken with Folder View, works with Desktop view)
https://bugs.kde.org/show_bug.cgi?id=419867 Dr. Boris Neubert changed: What|Removed |Added CC||b...@4nv.de -- You are receiving this mail because: You are watching all bug changes.
[kteatime] [Bug 421155] When adding an autostart entry for kteatimes multiple instances are started
https://bugs.kde.org/show_bug.cgi?id=421155 Boris Bigott changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #3 from Boris Bigott --- Removing the autostart entry seems to fix the issue because kteatime is restored with the session. I don't know why I added the autostart entry in the first place. Maybe the session was not restored in one of my previous setups. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 423658] New: Change of color when adding a fully transparent PNG over a color clip
https://bugs.kde.org/show_bug.cgi?id=423658 Bug ID: 423658 Summary: Change of color when adding a fully transparent PNG over a color clip Product: kdenlive Version: 20.04.1 Platform: Appimage OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: dalbo...@gmail.com Target Milestone: --- Created attachment 129764 --> https://bugs.kde.org/attachment.cgi?id=129764=edit Description of the bug: incorrect colors when layering color clips with transparent PNGs STEPS TO REPRODUCE 1. Create a Kdenlive project with two video tracks 2. Bottom track: a full red #ff "color clip" 3. Top track: a fully transparent PNG (e.g., created in Gimp). Note: in the attached series of screenshots, "circle.png" is fully transparent, except for the opaque white circle in the middle. OBSERVED RESULT The output color (as seen in the project monitor or the rendered H264 video) is not the same, depending on whether there's the transparent PNG on top. More precisely, the output color is #ff18000 without the transparent PNG, and #ff0001 with the transparent PNG. See attached image, the problem should be pretty clear. EXPECTED RESULT The color should not change (to avoid visible flicker) when adding a fully transparent PNG on top. Also, the color should be exactly #ff, which it never is with or without the transparent PNG. Adding the transparent PNG makes it in fact "more correct", but still not perfectly correct. DETAILS AND DISCUSSION The project has the following video settings: Video Settings Frame size: 1920 x 1080 (16:9) Frame rate: 23,976 fps Pixel Aspect Ratio: 1 Color Space: ITU-R 709 Interlaced: no My expectation is that when creating a #ff color clip, the "#ff" should be interpreted as a full red in the ITU-R 709 color space (which is by the way the same chromacity as a full red in sRGB). Therefore, I don't understand why the color clip is rendered as #ff18000 instead of #ff. It seems as if there is some color space conversion happening which doesn't seem to make sense to me. When adding the transparent PNG on top, it seems to behave as if the color clip is now interpreted in the correct color space, and thus give the correct result (besides the "1" in #ff0001, which I assume is some sort of rounding error) Note that if instead of a "#ff color clip", I use a PNG filled with a #ff color, I get #ff0001 as output, both with or without a transparent PNG layered on top. Therefore, we have the four following behaviors: A: #ff color clip (output = #ff1800) B: #ff color clip + fully transparent PNG (output = #ff001) B: #ff PNG (output = #ff001) B: #ff PNG + fully transparent PNG (output = #ff001) Finally, note that if I render the video as a PNG image sequence (instead of either an H-264 encoded video, or the Project Monitor's preview), then I do get the correct #ff output in all four situations described above. SOFTWARE/OS VERSIONS Kubuntu 18.04 Kdenlive Version 20.04.1 (Official AppImage) KDE Frameworks 5.68.0 Qt 5.14.1 (built against 5.14.1) The xcb windowing system -- You are receiving this mail because: You are watching all bug changes.
[KAccounts] [Bug 422857] New: Empty dialog when adding a new account
https://bugs.kde.org/show_bug.cgi?id=422857 Bug ID: 422857 Summary: Empty dialog when adding a new account Product: KAccounts Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: kde-telepathy-b...@kde.org Reporter: joskicbori...@gmail.com Target Milestone: --- Created attachment 129250 --> https://bugs.kde.org/attachment.cgi?id=129250=edit Screenshot showing the empty modal SUMMARY STEPS TO REPRODUCE 1. Open Online Accounts 2. Click Add New Account 3. There is no option to add a new account. OBSERVED RESULT There are on inputs or other options to add a online account. EXPECTED RESULT There should be some inputs..like email, provider etc SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.13.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 421822] 'Scroll Page Up'/'Scroll Page Down' actions do not scroll by pages
https://bugs.kde.org/show_bug.cgi?id=421822 Boris changed: What|Removed |Added CC||durako...@gmail.com --- Comment #7 from Boris --- I have the same issue on Arch Linux. I have to downgrade to version 19.12.3. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421749] Plasma desktop crashes when choosing to configure the thermal monitor widget
https://bugs.kde.org/show_bug.cgi?id=421749 Boris changed: What|Removed |Added CC||a...@mtlr.one -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 418674] New: Kontact crashes everytime "Configure Kontact" is pressed
https://bugs.kde.org/show_bug.cgi?id=418674 Bug ID: 418674 Summary: Kontact crashes everytime "Configure Kontact" is pressed Product: kontact Version: unspecified Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: boris.zuba...@gmail.com Target Milestone: --- SUMMARY Kontact crashes everytime "Configure Kontact" is pressed STEPS TO REPRODUCE 1. Run Kontact 2. Open Settings menu 3. Press Configure Kontact OBSERVED RESULT Application immediately crashes with "Report Bug/Restart App" popup EXPECTED RESULT Opened configuration window SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 19.10 Eoan (available in About System) KDE Plasma Version: 5.18.2 KDE Frameworks Version: 5.67.0 Qt Version: 5.12.4 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 418673] New: Kmail hides messages on pressing Del in message list
https://bugs.kde.org/show_bug.cgi?id=418673 Bug ID: 418673 Summary: Kmail hides messages on pressing Del in message list Product: kmail2 Version: unspecified Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: message list Assignee: kdepim-b...@kde.org Reporter: boris.zuba...@gmail.com Target Milestone: --- SUMMARY Kmail hides other messages on pressing Del (or Move to Trash) on single message in message list STEPS TO REPRODUCE 1. Select message among others 2. Press Del to put it in Trash 3. All other messages become hidden. Need to change folder and return back to have the the rest of messages visible again. OBSERVED RESULT Messages become invisible after pressing Del on one of them EXPECTED RESULT Deleted message disappears from list, the rest is still visible. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 19.10 Eoan (available in About System) KDE Plasma Version: 5.18.2 KDE Frameworks Version: 5.67.0 Qt Version: 5.12.4 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 387345] Background image is reset when screen was turned off
https://bugs.kde.org/show_bug.cgi?id=387345 --- Comment #3 from Dr. Boris Neubert --- I stopped using activities a while ago. Thus, I just added an activity for testing purposes right now and tried to reproduce the issue. I cannot observe the issue in KDE Plasma 5.16.5 with KDE Frameworks 5.62.0. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 408063] Rendering corruption in items
https://bugs.kde.org/show_bug.cgi?id=408063 --- Comment #3 from Boris Jang --- (In reply to Boris Jang from comment #2) > (In reply to Michail Vourlakos from comment #1) > > Upstream Nvidia issue, is fixed both for Latte and plasma with Qt 5.13, KDE > > frameworks 5.58 > > It's fixed for the desktop for me since 5.13, but the dock is still showing > the graphical artefacts. My bad, didn't check my version number. Sorry about that! -- You are receiving this mail because: You are watching all bug changes.
[calligrasheets] [Bug 309352] separately selected rows incorrectly deleted
https://bugs.kde.org/show_bug.cgi?id=309352 Boris Ribalkin changed: What|Removed |Added Status|NEEDSINFO |RESOLVED --- Comment #2 from Boris Ribalkin --- I am not really using calligra anymore as LibreOffice works great for me :) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 395056] Video thumbnails in timeline display incorrect frames when using speed effect (or when clip's fps different from project's fps)
https://bugs.kde.org/show_bug.cgi?id=395056 --- Comment #4 from Boris Dalstein --- Created attachment 113093 --> https://bugs.kde.org/attachment.cgi?id=113093=edit Correct video thumbnails when zoomed-out -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 395056] Video thumbnails in timeline display incorrect frames when using speed effect (or when clip's fps different from project's fps)
https://bugs.kde.org/show_bug.cgi?id=395056 --- Comment #3 from Boris Dalstein --- Created attachment 113092 --> https://bugs.kde.org/attachment.cgi?id=113092=edit Incorrect video thumbnails when zoomed-in -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 395056] Video thumbnails in timeline display incorrect frames when using speed effect (or when clip's fps different from project's fps)
https://bugs.kde.org/show_bug.cgi?id=395056 --- Comment #2 from Boris Dalstein --- (and sorry for the first message, it seems I hit "submit" in the middle of writing the bug report, please delete if someone has admin rights to do so) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 395056] Video thumbnails in timeline display incorrect frames when using speed effect (or when clip's fps different from project's fps)
https://bugs.kde.org/show_bug.cgi?id=395056 Boris Dalstein changed: What|Removed |Added Platform|Other |Kubuntu Packages Summary|Video thumbnails in |Video thumbnails in |timeline display incorrect |timeline display incorrect |frames when using speed |frames when using speed |effect (or when clipclip|effect (or when clip's fps |with different fps than |different from project's |project |fps) Version|unspecified |17.12.3 --- Comment #1 from Boris Dalstein --- The video thumbnails in the timeline (the ones that appear for all frames when zooming in, not the first/last thumbnails which seem to be okay) seem to ignore the 'speed' effect. That is, when speed=200%, it seems to display frame X/2 (w.r.t the beginning of the input non-cut clip) when the desired behaviour is to display frame X. See attachments showing: 1. When zoomed in, the "first" thumbnail is correct, but the "middle" and "last" thumbnails are incorrect 2. When zoomed out, all thumbnails (=first+last thumbnails) are correct This bug also seems to occur when the FPS of the input clip (e.g. 24fps) is different from the FPS of the project (e.g., 25 fps). I know this is bad practice to mix FPS and it's better to first convert the input clips to the target FPS before importing them, but still, the bug should not occur. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 395056] New: Video thumbnails in timeline display incorrect frames when using speed effect (or when clipclip with different fps than project
https://bugs.kde.org/show_bug.cgi?id=395056 Bug ID: 395056 Summary: Video thumbnails in timeline display incorrect frames when using speed effect (or when clipclip with different fps than project Product: kdenlive Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: dalbo...@gmail.com Target Milestone: --- When zooming the timeline, it displays every individual video frame as a thumbnail -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 387128] Memory leak in plasmashell with persistent notifications
https://bugs.kde.org/show_bug.cgi?id=387128 Boris Pek <tehnic...@yandex.ru> changed: What|Removed |Added CC||tehnic...@yandex.ru -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 387345] Background image is reset when screen was turned off
https://bugs.kde.org/show_bug.cgi?id=387345 --- Comment #1 from Dr. Boris Neubert <b...@4nv.de> --- Additional information: Changing the background image after that does not survive changing activities. Switching to one activity and then back shows the stock KDE background image again. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 387345] Background image is reset when screen was turned off
https://bugs.kde.org/show_bug.cgi?id=387345 Dr. Boris Neubert <b...@4nv.de> changed: What|Removed |Added CC||b...@4nv.de Platform|Other |Ubuntu Packages -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 387345] New: Background image is reset when screen was turned off
https://bugs.kde.org/show_bug.cgi?id=387345 Bug ID: 387345 Summary: Background image is reset when screen was turned off Product: plasmashell Version: 5.10.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Desktop Containment Assignee: se...@kde.org Reporter: b...@4nv.de CC: plasma-b...@kde.org Target Milestone: 1.0 This is KDE Plasma Version 5.10.5 with KDE Frameworks Version 5.38.0 on KUbuntu 17.10 with Kernel 4.8.0-46-generic. I have observed the issue for one or two years. Screen is 4k HDMI. Desktop is set to folder view (desktop folder) with custom background images per activity. Turning off (power down) the screen and turning it on again resets the background image to the stock KDE image. -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 266313] Desktop Background Image is reset when changing monitors
https://bugs.kde.org/show_bug.cgi?id=266313 Dr. Boris Neubert <b...@4nv.de> changed: What|Removed |Added CC||b...@4nv.de -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 378546] KIOExec Error
https://bugs.kde.org/show_bug.cgi?id=378546 Boris Kheyfets <kheyfbo...@gmail.com> changed: What|Removed |Added CC||kheyfbo...@gmail.com --- Comment #1 from Boris Kheyfets <kheyfbo...@gmail.com> --- On a clean install of Kubuntu 17.04 I don't have this bug. However, on another machine I had it in 16.10 and the bug is there after upgrade to 17.04 as well. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 377852] KDevelop crashing when repeating ('.') last 'o'/'O' command in Vi Mode.
https://bugs.kde.org/show_bug.cgi?id=377852 Boris Egorov <ego...@linux.com> changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED CC||ego...@linux.com --- Comment #1 from Boris Egorov <ego...@linux.com> --- It is KTextEditor issue, Kate crashes for me too. Exact keystrokes I press on a new document: "o" "Esc" "O" "Esc" "." Application: Kate (kate), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f74430ef180 (LWP 3481))] Thread 3 (Thread 0x7f7435c9f700 (LWP 3483)): #0 0x7f744fa3dbed in read () at /lib64/libc.so.6 #1 0x7f7448e6a4d0 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0 #2 0x7f7448e25c83 in g_main_context_check () at /lib64/libglib-2.0.so.0 #3 0x7f7448e26104 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #4 0x7f7448e2627c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #5 0x7f74508486eb in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7f74507f968a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #7 0x7f74506565e3 in QThread::exec() () at /lib64/libQt5Core.so.5 #8 0x7f7450a53739 in QDBusConnectionManager::run() () at /lib64/libQt5DBus.so.5 #9 0x7f745065a9ca in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #10 0x7f744de6e6ca in start_thread () at /lib64/libpthread.so.0 #11 0x7f744fa4df7f in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f743e5c1700 (LWP 3482)): #0 0x7f744fa4201d in poll () at /lib64/libc.so.6 #1 0x7f744cb9bd10 in _xcb_conn_wait () at /lib64/libxcb.so.1 #2 0x7f744cb9daa9 in xcb_wait_for_event () at /lib64/libxcb.so.1 #3 0x7f7442e62d69 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5 #4 0x7f745065a9ca in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #5 0x7f744de6e6ca in start_thread () at /lib64/libpthread.so.0 #6 0x7f744fa4df7f in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f74430ef180 (LWP 3481)): [KCrash Handler] #6 0x7f7451154ee0 in QTextLayout::lineCount() const () at /lib64/libQt5Gui.so.5 #7 0x7f7454f353d9 in KateLineLayout::viewLineCount() const (this=) at /usr/src/debug/ktexteditor-5.33.0/src/render/katelinelayout.cpp:178 #8 0x7f7454f29716 in KateRenderer::paintTextLineBackground(QPainter&, QExplicitlySharedDataPointer, int, int, int) (this=this@entry=0x55b2b79de6c0, paint=..., layout=..., currentViewLine=-1, xStart=xStart@entry=0, xEnd=xEnd@entry=1164) at /usr/src/debug/ktexteditor-5.33.0/src/render/katerenderer.cpp:224 #9 0x7f7454f2dbd7 in KateRenderer::paintTextLineBackground(QPainter&, QExplicitlySharedDataPointer, int, int, int) (xEnd=1164, xStart=0, currentViewLine=, layout=..., paint=..., this=0x55b2b79de6c0) at /usr/src/debug/ktexteditor-5.33.0/src/render/katerenderer.cpp:181 #10 0x7f7454f2dbd7 in KateRenderer::paintTextLine(QPainter&, QExplicitlySharedDataPointer, int, int, KTextEditor::Cursor const*, QFlags) (this=0x55b2b79de6c0, paint=..., range=..., xStart=xStart@entry=0, xEnd=xEnd@entry=1164, cursor=cursor@entry=0x7ffef4f90730, flags=...) at /usr/src/debug/ktexteditor-5.33.0/src/render/katerenderer.cpp:559 #11 0x7f7454f79299 in KateViewInternal::paintEvent(QPaintEvent*) (this=0x55b2b7c341b0, e=0x7ffef4f90a80) at /usr/src/debug/ktexteditor-5.33.0/src/view/kateviewinternal.cpp:2996 #12 0x7f74515dd7c0 in QWidget::event(QEvent*) () at /lib64/libQt5Widgets.so.5 #13 0x7f7451595ecc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #14 0x7f745159d671 in QApplication::notify(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #15 0x7f74507fa6fa in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #16 0x7f74515d647a in QWidgetPrivate::sendPaintEvent(QRegion const&) () at /lib64/libQt5Widgets.so.5 #17 0x7f74515d6af3 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () at /lib64/libQt5Widgets.so.5 #18 0x7f74515d782d in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList<QObject*> const&, int, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () at /lib64/libQt5Widgets.so.5 #19 0x7f74515d771a in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList<QObject*> const&, int, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () at /lib64/libQt5Widgets.so.5 #20 0x7f74515d771a in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList<QObject*> const&, int,
[kdevelop] [Bug 376084] Crash on code parsing
https://bugs.kde.org/show_bug.cgi?id=376084
Boris Egorov <ego...@linux.com> changed:
What|Removed |Added
CC||ego...@linux.com
--- Comment #2 from Boris Egorov <ego...@linux.com> ---
I've made a backtrace with Clang debugging symbols, hope it will help. I wanted
to dig a bit further, but gdb hangs completely.
--
template using crash = struct : public virtual T {}
(gdb) bt
#0 0x7fffb084d5da in
clang::ASTContext::getASTRecordLayout(clang::RecordDecl const*) const
(this=0x7fff3c0c1e20, D=D@entry=0x0)
at /usr/src/debug/cfe-3.9.1.src/lib/AST/RecordLayoutBuilder.cpp:2929
#1 0x7fffb084dcc4 in (anonymous
namespace)::EmptySubobjectMap::ComputeEmptySubobjectSizes (this=0x7fff8affacf0)
at /usr/src/debug/cfe-3.9.1.src/lib/AST/RecordLayoutBuilder.cpp:192
#2 0x7fffb084dcc4 in (anonymous
namespace)::EmptySubobjectMap::EmptySubobjectMap (Class=0x7fff3c1504f0,
Context=..., this=0x7fff8affacf0)
at /usr/src/debug/cfe-3.9.1.src/lib/AST/RecordLayoutBuilder.cpp:171
#3 0x7fffb084dcc4 in
clang::ASTContext::getASTRecordLayout(clang::RecordDecl const*) const
(this=this@entry=0x7fff3c0c1e20, D=,
D@entry=0x7fff3c1504f0) at
/usr/src/debug/cfe-3.9.1.src/lib/AST/RecordLayoutBuilder.cpp:2965
#4 0x7fffb06f7c02 in clang::ASTContext::getTypeInfoImpl(clang::Type
const*) const (this=this@entry=0x7fff3c0c1e20, T=0x7fff3c150590)
at /usr/src/debug/cfe-3.9.1.src/lib/AST/ASTContext.cpp:1769
#5 0x7fffb06eed0c in clang::ASTContext::getTypeInfo(clang::Type const*)
const (this=this@entry=0x7fff3c0c1e20, T=,
T@entry=0x7fff3c150590) at
/usr/src/debug/cfe-3.9.1.src/lib/AST/ASTContext.cpp:1513
#6 0x7fffb06eef85 in clang::ASTContext::getTypeInfoInChars(clang::Type
const*) const (this=0x7fff3c0c1e20, T=0x7fff3c150590)
at /usr/src/debug/cfe-3.9.1.src/lib/AST/ASTContext.cpp:1489
#7 0x7fffb06ef030 in
clang::ASTContext::getTypeInfoInChars(clang::QualType) const
(this=this@entry=0x7fff3c0c1e20, T=...)
at /usr/src/debug/cfe-3.9.1.src/lib/AST/ASTContext.cpp:1496
#8 0x7fffb06ef0b9 in
clang::ASTContext::getTypeSizeInChars(clang::QualType) const
(this=this@entry=0x7fff3c0c1e20, T=..., T@entry=...)
at /usr/src/debug/cfe-3.9.1.src/lib/AST/ASTContext.cpp:1870
#9 0x7fffb0b7804b in clang_Type_getSizeOf(CXType) (T=...) at
/usr/src/debug/cfe-3.9.1.src/tools/libclang/CXType.cpp:769
#10 0x7fffb0df92fb in (anonymous
namespace)::Visitor::setDeclData<(CXCursorKind)2>(CXCursor,
KDevelop::ClassDeclaration*) const (this=this@entry=0x7fff8affc710, cursor=...,
decl=decl@entry=0x7fff8000d4a0) at
/usr/src/debug/kdevelop-5.1.0/languages/clang/duchain/builder.cpp:1044
#11 0x7fffb0e144cc in (anonymous
namespace)::Visitor::createDeclarationCommon<(CXCursorKind)2,
KDevelop::ClassDeclaration> (id=..., cursor=..., this=0x7fff8affc710) at
/usr/src/debug/kdevelop-5.1.0/languages/clang/duchain/builder.cpp:396
#12 0x7fffb0e144cc in (anonymous
namespace)::Visitor::createDeclaration<(CXCursorKind)2,
KDevelop::ClassDeclaration> (context=0x7fff8000ea80, id=..., cursor=...,
this=0x7fff8affc710) at
/usr/src/debug/kdevelop-5.1.0/languages/clang/duchain/builder.cpp:407
#13 0x7fffb0e144cc in (anonymous
namespace)::Visitor::buildDeclaration<(CXCursorKind)2,
KDevelop::ClassDeclaration, true> (cursor=..., this=0x7fff8affc710) at
/usr/src/debug/kdevelop-5.1.0/languages/clang/duchain/builder.cpp:1144
#14 0x7fffb0e144cc in (anonymous
namespace)::Visitor::dispatchCursor<(CXCursorKind)2, (Decision)1, (Decision)0>
(parent=..., cursor=..., this=0x7fff8affc710) at
/usr/src/debug/kdevelop-5.1.0/languages/clang/duchain/builder.cpp:907
#15 0x7fffb0e144cc in (anonymous
namespace)::Visitor::dispatchCursor<(CXCursorKind)2, (Decision)1,
(Decision)2>(CXCursor, CXCursor) (this=this@entry=0x7fff8affc710, cursor=...,
parent=...) at
/usr/src/debug/kdevelop-5.1.0/languages/clang/duchain/builder.cpp:881
#16 0x7fffb0e1629c in (anonymous
namespace)::Visitor::dispatchCursor<(CXCursorKind)2> (parent=..., cursor=...,
this=0x7fff8affc710)
at /usr/src/debug/kdevelop-5.1.0/languages/clang/duchain/builder.cpp:869
#17 0x7fffb0e1629c in (anonymous namespace)::visitCursor(CXCursor,
CXCursor, CXClientData) (cursor=..., parent=..., data=0x7fff8affc710)
at /usr/src/debug/kdevelop-5.1.0/languages/clang/duchain/builder.cpp:1452
#18 0x7fffb0b48fd5 in clang::cxcursor::CursorVisitor::Visit(CXCursor, bool)
(this=this@entry=0x7fff8affc4a0, Cursor=...,
CheckedRegionOfInterest=CheckedRegionOfInterest@entry=true) at
/usr/src/debug/cfe-3.9.1.src/tools/libclang/CIndex.cpp:208
#19 0x7fffb0b4c9bd in
clang::cxcursor::CursorVisitor::handleDeclForVisitation(clang::Decl const*)
(this=this@entry=0x7fff8affc4a0, D=0x7fff3c1504f0)
at /usr/src/debug/cfe-3.9.1.src/tools/libclang/CIndex.cpp:665
#20 0x7fffb0b4ca
[ktorrent] [Bug 359903] ktorrent sequential download UI wishlist
https://bugs.kde.org/show_bug.cgi?id=359903 Boris Radulov <bobbyradul...@gmail.com> changed: What|Removed |Added CC||bobbyradul...@gmail.com --- Comment #2 from Boris Radulov <bobbyradul...@gmail.com> --- Has this been resolved? If not I'll try to implement such a feature -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 373254] New: Gwenview crashed while browsing smb share
https://bugs.kde.org/show_bug.cgi?id=373254 Bug ID: 373254 Summary: Gwenview crashed while browsing smb share Product: gwenview Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: bu.kde_...@mail.unckel.net CC: myr...@kde.org Target Milestone: --- Application: gwenview (16.08.2) Qt Version: 5.7.0 Frameworks Version: 5.27.0 Operating System: Linux 4.8.10-300.fc25.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: I was browsing a smb share. At that moment only folders were visible, no pictures in that directory. No other program was open. -- Backtrace: Application: Gwenview (gwenview), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7faca370ee80 (LWP 3791))] Thread 3 (Thread 0x7fac936a1700 (LWP 3793)): #0 0x7facb1ad0a9b in QMutex::lock() () from /lib64/libQt5Core.so.5 #1 0x7facb1cc5c4f in postEventSourcePrepare(_GSource*, int*) () from /lib64/libQt5Core.so.5 #2 0x7faca9bda699 in g_main_context_prepare () from /lib64/libglib-2.0.so.0 #3 0x7faca9bdb07b in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #4 0x7faca9bdb26c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #5 0x7facb1cc5d8b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7facb1c770ba in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #7 0x7facb1ad4643 in QThread::exec() () from /lib64/libQt5Core.so.5 #8 0x7facb237b7a9 in QDBusConnectionManager::run() () from /lib64/libQt5DBus.so.5 #9 0x7facb1ad8a1a in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #10 0x7facaf8e56ca in start_thread () from /lib64/libpthread.so.0 #11 0x7facb0ecbf6f in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fac98c22700 (LWP 3792)): #0 0x7facb0ec000d in poll () from /lib64/libc.so.6 #1 0x7facae6e5d10 in _xcb_conn_wait () from /lib64/libxcb.so.1 #2 0x7facae6e7aa9 in xcb_wait_for_event () from /lib64/libxcb.so.1 #3 0x7fac9ca8fa19 in QXcbEventReader::run() () from /lib64/libQt5XcbQpa.so.5 #4 0x7facb1ad8a1a in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #5 0x7facaf8e56ca in start_thread () from /lib64/libpthread.so.0 #6 0x7facb0ecbf6f in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7faca370ee80 (LWP 3791)): [KCrash Handler] #6 0x7facb1fc4d7d in QCursorData::~QCursorData() () from /lib64/libQt5Gui.so.5 #7 0x7facb1fc4e8f in QCursor::~QCursor() () from /lib64/libQt5Gui.so.5 #8 0x7facb30df647 in QWidget::setCursor(QCursor const&) () from /lib64/libQt5Widgets.so.5 #9 0x7facb8fb5835 in Gwenview::PreviewItemDelegate::eventFilter(QObject*, QEvent*) () from /lib64/libgwenviewlib.so.5 #10 0x7facb1c77f12 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #11 0x7facb30a2945 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #12 0x7facb30ab82f in QApplication::notify(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #13 0x7facb1c7812a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #14 0x7facb30a965d in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () from /lib64/libQt5Widgets.so.5 #15 0x7facb3103dd0 in QWidgetWindow::handleMouseEvent(QMouseEvent*) () from /lib64/libQt5Widgets.so.5 #16 0x7facb3106603 in QWidgetWindow::event(QEvent*) () from /lib64/libQt5Widgets.so.5 #17 0x7facb30a296c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #18 0x7facb30aa111 in QApplication::notify(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #19 0x7facb1c7812a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #20 0x7facb1fb6e73 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /lib64/libQt5Gui.so.5 #21 0x7facb1fb8925 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () from /lib64/libQt5Gui.so.5 #22 0x7facb1f997cb in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /lib64/libQt5Gui.so.5 #23 0x7fac9cac5c60 in userEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5XcbQpa.so.5 #24 0x7faca9bdae42 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #25 0x7faca9bdb1c0 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #26 0x7faca9bdb26c in
[kde] [Bug 372971] New: Unusably small scroll steps in various places incl. settings, add widget and dolphin's places sidebar
https://bugs.kde.org/show_bug.cgi?id=372971 Bug ID: 372971 Summary: Unusably small scroll steps in various places incl. settings, add widget and dolphin's places sidebar Product: kde Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: k...@borisovo.cz Target Milestone: --- So, I encountered this both on Fedora that I tried and Open Suse which I'm trying now. In places including but not limited to dolophin's places sidebar, panel's add widget menu and desktop effects settings. The scroll step is less than one line and is not affected by changing scroll step in mouse settings, while this setting does affect scroll speed in for example web browser or even dolphin's main panel. Video included: https://www.youtube.com/watch?v=n2BDi_-AaH8 Problem was discussed also here but only related to dolphin: ttps://bugs.kde.org/show_bug.cgi?id=342839 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 342839] Scrolling steps much too small in folders and places panels
https://bugs.kde.org/show_bug.cgi?id=342839 Boris <k...@borisovo.cz> changed: What|Removed |Added CC||k...@borisovo.cz -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 371825] Places->Network doesn't lead to anywhere
https://bugs.kde.org/show_bug.cgi?id=371825 --- Comment #2 from Boris <k...@borisovo.cz> --- Update: workaround: This problem can be fixed by installing plasma-workspace -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 371825] Places->Network doesn't lead to anywhere
https://bugs.kde.org/show_bug.cgi?id=371825 --- Comment #1 from Boris <k...@borisovo.cz> --- Update: This problem doesn't exist in Dolphin4 on same system -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 371825] New: Places->Network doesn't lead to anywhere
https://bugs.kde.org/show_bug.cgi?id=371825 Bug ID: 371825 Summary: Places->Network doesn't lead to anywhere Product: dolphin Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: panels: folders Assignee: dolphin-bugs-n...@kde.org Reporter: k...@borisovo.cz Target Milestone: --- User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:49.0) Gecko/20100101 Firefox/49.0 Build Identifier: 16.04.3 So, I'm on xubuntu 16.10 and I installed dolphin from repository. Clicking Network in Places side panel results in no action, location doesn't change from current dirrectory. If I right click it and select open in new panel, it brings up blank remote:/ location. I still can see network shares in other browsers (thunar and nemo) normally. Reproducible: Always Steps to Reproduce: 1. On xubuntu 16.10 2. open Dolphin 3.Click Network in left panel Alternatively to 3.: right click Network in Places menu and choose open in new tab Actual Results: No change, or blank remote:/ location shows up in new panel Expected Results: There should be local network samba shares visile like it is in other browsers on same machine. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 371822] New: "Open terminal here" doesn't work without Konsole installed
https://bugs.kde.org/show_bug.cgi?id=371822 Bug ID: 371822 Summary: "Open terminal here" doesn't work without Konsole installed Product: dolphin Version: unspecified Platform: Other URL: http://i.imgur.com/9SyoG1l.png OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: panels: terminal Assignee: dolphin-bugs-n...@kde.org Reporter: k...@borisovo.cz Target Milestone: --- User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:49.0) Gecko/20100101 Firefox/49.0 Build Identifier: Version 16.04.3 On xubuntu Konsole is not installed by default, so after I install Dolphin but not Konsole (it took me very long time to find out it's needed) F4 shows plain grey panel where terminal would be (That's the included picture) and shift+F4 doesn't do anything at all. Right click menu is also missing the "Open terminal here" option. Installing Konsole fixes all this, but there are problems with this: I had no idea that's needed, it doesn't give you any error message and there should be option to choose what terminal to use and it doesn't respect preferred terminal setting in xubuntu. Reproducible: Always Steps to Reproduce: 1. Uninstall Konsole if installed 2. kill Dolphin 3. start Dolphin again 4. In any folder press either F4 of shift+F4 Actual Results: F4 gives you the result visible in the included picture, shift+F4 or "Open terminal" in tools menu doesn't do anything, "open terminal here" is missing from right click menu in folder. Expected Results: Two options: Dolphin should open terminal that is set as preferred application in xubuntu settings or Konsole should be dependency. This happenned on freshly installed xubuntu 16.10, but I think it could happen on any system that lets you install dolphin without konsole. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 367966] Auto bracket on if statements not indenting properly
https://bugs.kde.org/show_bug.cgi?id=367966 Boris Egorov <ego...@linux.com> changed: What|Removed |Added CC||ego...@linux.com --- Comment #2 from Boris Egorov <ego...@linux.com> --- Yeah, it is annoying. Reproduces on Kate too, so I guess it should be moved to ktexteditor bugs. -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 365205] New: Plasma crash and restarts when move Steam app window from one desktop to another by dragging app icon in taskbar to another desktop icon
https://bugs.kde.org/show_bug.cgi?id=365205 Bug ID: 365205 Summary: Plasma crash and restarts when move Steam app window from one desktop to another by dragging app icon in taskbar to another desktop icon Product: plasma4 Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: speakingf...@gmail.com Application: plasma-desktop (4.11.20) KDE Platform Version: 4.14.9 Qt Version: 4.8.6 Operating System: Linux 3.16.7-35-desktop x86_64 Distribution: "openSUSE 13.2 (Harlequin) (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Move Steam app window from one desktop to another by dragging app icon in taskbar to another desktop icon - Custom settings of the application: Steam app window The crash can be reproduced sometimes. -- Backtrace: Application: Оболочка Plasma (plasma-desktop), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f334bb98780 (LWP 1768))] Thread 15 (Thread 0x7f331f10b700 (LWP 1769)): #0 0x7f334a46b03f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f333caa98cb in () at /usr/lib64/libQtScript.so.4 #2 0x7f333caa9909 in () at /usr/lib64/libQtScript.so.4 #3 0x7f334a4670a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f33491d3cbd in clone () at /lib64/libc.so.6 Thread 14 (Thread 0x7f328700 (LWP 1773)): #0 0x7f33491cb88d in poll () at /lib64/libc.so.6 #1 0x7f33462debe4 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f33462decec in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f334a82c0de in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #4 0x7f334a7fde6f in QEventLoop::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #5 0x7f334a7fe165 in QEventLoop::exec(QFlags) () at /usr/lib64/libQtCore.so.4 #6 0x7f334a6fb0bf in QThread::exec() () at /usr/lib64/libQtCore.so.4 #7 0x7f334a7df783 in () at /usr/lib64/libQtCore.so.4 #8 0x7f334a6fd79f in () at /usr/lib64/libQtCore.so.4 #9 0x7f334a4670a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7f33491d3cbd in clone () at /lib64/libc.so.6 Thread 13 (Thread 0x7f332b189700 (LWP 3127)): #0 0x7f334a46b03f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f334a6fdc86 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQtCore.so.4 #2 0x7f333bd006fc in () at /usr/lib64/libthreadweaver.so.4 #3 0x7f333bd03193 in () at /usr/lib64/libthreadweaver.so.4 #4 0x7f333bd031ac in () at /usr/lib64/libthreadweaver.so.4 #5 0x7f333bd031ac in () at /usr/lib64/libthreadweaver.so.4 #6 0x7f333bd031ac in () at /usr/lib64/libthreadweaver.so.4 #7 0x7f333bd031ac in () at /usr/lib64/libthreadweaver.so.4 #8 0x7f333bd01eaf in ThreadWeaver::Thread::run() () at /usr/lib64/libthreadweaver.so.4 #9 0x7f334a6fd79f in () at /usr/lib64/libQtCore.so.4 #10 0x7f334a4670a4 in start_thread () at /lib64/libpthread.so.0 #11 0x7f33491d3cbd in clone () at /lib64/libc.so.6 Thread 12 (Thread 0x7f327b9dc700 (LWP 3128)): #0 0x7f334a46b03f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f334a6fdc86 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQtCore.so.4 #2 0x7f333bd006fc in () at /usr/lib64/libthreadweaver.so.4 #3 0x7f333bd03193 in () at /usr/lib64/libthreadweaver.so.4 #4 0x7f333bd031ac in () at /usr/lib64/libthreadweaver.so.4 #5 0x7f333bd01eaf in ThreadWeaver::Thread::run() () at /usr/lib64/libthreadweaver.so.4 #6 0x7f334a6fd79f in () at /usr/lib64/libQtCore.so.4 #7 0x7f334a4670a4 in start_thread () at /lib64/libpthread.so.0 #8 0x7f33491d3cbd in clone () at /lib64/libc.so.6 Thread 11 (Thread 0x7f327b1db700 (LWP 3129)): #0 0x7f334a46b03f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f334a6fdc86 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQtCore.so.4 #2 0x7f333bd006fc in () at /usr/lib64/libthreadweaver.so.4 #3 0x7f333bd03193 in () at /usr/lib64/libthreadweaver.so.4 #4 0x7f333bd031ac in () at /usr/lib64/libthreadweaver.so.4 #5 0x7f333bd031ac in () at /usr/lib64/libthreadweaver.so.4 #6 0x7f333bd031ac in () at /usr/lib64/libthreadweaver.so.4 #7 0x7f333bd031ac in () at /usr/lib64/libthreadweaver.so.4 #8 0x7f333bd01eaf in ThreadWeaver::Thread::run() () at /usr/lib64/libthreadweaver.so.4 #9 0x7f334a6fd79f in () at /usr/lib64/libQtCore.so.4 #10 0x7f334a4670a4 in start_thread () at /lib64/libpthread.so.0 #11 0x7f33491d3cbd in clone () at
[kmail2] [Bug 360963] Select identity and "From" automatically on reply in dependence of the answered mail.
https://bugs.kde.org/show_bug.cgi?id=360963 Boris <bugs-kde-joog3eizaec9x...@wcht.de> changed: What|Removed |Added CC||bugs-kde-joog3eizaec9xoo3@w ||cht.de -- You are receiving this mail because: You are watching all bug changes.
[QtCurve] [Bug 362908] New: New stable release (or git tag)
https://bugs.kde.org/show_bug.cgi?id=362908 Bug ID: 362908 Summary: New stable release (or git tag) Product: QtCurve Version: git Platform: Debian testing OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: yyc1...@gmail.com Reporter: tehnic...@yandex.ru CC: h...@kde.org Last stable release was long time ago. Very long time ago... Could you make a major or minor release of QtCurve in foreseeable future? I believe that its time has come. QtCurve 1.8.18-246-g0cd6aae worked really well during long time. At least in Debian testing and unstable. Ubuntu users have not complained as well. It is a pity that bug #362907 is suddenly appeared. But it might be fixed or last commits might be reverted. Last stable release of QtCurve was done at GitHub, before project has been moved to KDE infrastructure. Where QtCurve tarballs would be placed when git tag will be done? Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[QtCurve] [Bug 362907] New: kwin_x11 crashes in QtCurve::Style::disconnectDBus()
https://bugs.kde.org/show_bug.cgi?id=362907
Bug ID: 362907
Summary: kwin_x11 crashes in QtCurve::Style::disconnectDBus()
Product: QtCurve
Version: git
Platform: Debian testing
URL: https://bugs.debian.org/823674
OS: Linux
Status: UNCONFIRMED
Severity: crash
Priority: NOR
Component: qt5
Assignee: yyc1...@gmail.com
Reporter: tehnic...@yandex.ru
CC: h...@kde.org
After updating QtCurve from 1.8.18+git20160112-0cd6aae (1.8.18-247-gd126bd5) to
1.8.18+git20160320-3d8622c (1.8.18-251-g3d8622c) users report about multiple
kwin_x11 crashes at KDE startup.
Typical backtrace looks like this:
Program received signal SIGSEGV, Segmentation fault.
0xb52fdb78 in QDBusConnection::QDBusConnection(QDBusConnection const&) ()
from /usr/lib/i386-linux-gnu/libQt5DBus.so.5
(gdb) bt full
#0 0xb52fdb78 in QDBusConnection::QDBusConnection(QDBusConnection const&) ()
from /usr/lib/i386-linux-gnu/libQt5DBus.so.5
No symbol table info available.
#1 0xb53008f4 in QDBusConnection::sessionBus() ()
from /usr/lib/i386-linux-gnu/libQt5DBus.so.5
No symbol table info available.
#2 0xb0a9d11a in QtCurve::Style::disconnectDBus (this=0x809f690)
at ../../../qt5/style/qtcurve.cpp:694
cb =
bus = {static staticMetaObject = {d = {superdata = 0x0, stringdata =
0xb5356e20,
data = 0xb5356ce0, static_metacall = 0x0, relatedMetaObjects =
0x0,
extradata = 0x0}}, d = 0x8062238}
#3 0xb0a9d429 in QtCurve::Style::::operator()(void *)
(data=,
__closure=) at ../../../qt5/style/qtcurve.cpp:663
No locals.
#4 0xb0ae2678 in QtCurve::runAllCleanups () at
../../../qt5/style/qtcurve_plugin.cpp:86
func =
data =
#5 0xb0ae2884 in QtCurve::StylePlugin::~StylePlugin (this=0x809c310,
__in_chrg=) at ../../../qt5/style/qtcurve_plugin.cpp:167
No locals.
#6 0xb0ae28ca in QtCurve::StylePlugin::~StylePlugin (this=0x809c310,
__in_chrg=) at ../../../qt5/style/qtcurve_plugin.cpp:170
No locals.
#7 0xb6b198b5 in ?? () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
No symbol table info available.
#8 0xb6b11c54 in ?? () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
No symbol table info available.
#9 0xb6b11e5a in ?? () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
No symbol table info available.
#10 0xb6b5cf3c in QObject::~QObject() () from
/usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
No symbol table info available.
#11 0xb6b10e33 in QFactoryLoader::~QFactoryLoader() ()
from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
No symbol table info available.
#12 0xb747beb8 in ?? () from /usr/lib/i386-linux-gnu/libQt5Widgets.so.5
No symbol table info available.
#13 0xb7dfa933 in __run_exit_handlers (status=1, listp=0xb7f803dc
<__exit_funcs>,
run_list_atexit=true) at exit.c:82
atfct =
onfct =
cxafct =
#14 0xb7dfa98f in __GI_exit (status=1) at exit.c:104
No locals.
#15 0xb7f86e39 in ?? () from /usr/lib/i386-linux-gnu/libkdeinit5_kwin_x11.so
No symbol table info available.
---Type to continue, or q to quit---
#16 0xb6b551d0 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
No symbol table info available.
#17 0xb6b55aad in QMetaObject::activate(QObject*, QMetaObject const*, int,
void**) ()
from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
No symbol table info available.
#18 0xb7a8e3e2 in KSelectionOwner::failedToClaimOwnership() ()
from /usr/lib/i386-linux-gnu/libKF5WindowSystem.so.5
No symbol table info available.
#19 0xb7a79319 in KSelectionOwner::claim(bool, bool) ()
from /usr/lib/i386-linux-gnu/libKF5WindowSystem.so.5
No symbol table info available.
#20 0xb7f87aab in ?? () from /usr/lib/i386-linux-gnu/libkdeinit5_kwin_x11.so
No symbol table info available.
#21 0xb7b91ff4 in KWin::Application::start() () from
/usr/lib/i386-linux-gnu/libkwin.so.5
No symbol table info available.
#22 0xb7f885ac in kdemain () from
/usr/lib/i386-linux-gnu/libkdeinit5_kwin_x11.so
No symbol table info available.
#23 0x08048607 in main ()
No symbol table info available.
Another example:
https://bugs.debian.org/823674
Reproducible: Always
Steps to Reproduce:
1. Login to KDE Plasma 5.
2. kwin_x11 crashes.
3. Close crash dialog window.
4. kwin_x11 crashes again.
5. Close crash dialog window.
6. kwin_x11 crashes again.
7. ...
Actual Results:
Despite this annoying crash dialog all programs works like expected. Or I have
missed something...
Expected Results:
QtCurve should work as earlier after this code refactoring.
System: up to date Debian testing or unstable
Libraries: Qt -- 5.5.1, KF5 -- 5.16.0, kwin-x11 -- 5.4.3
--
You are receiving this mail because:
You are watching all bug changes.
[kate] [Bug 360797] Kate crashing opening binary file
https://bugs.kde.org/show_bug.cgi?id=360797 Boris Egorov <ego...@linux.com> changed: What|Removed |Added CC||ego...@linux.com Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #2 from Boris Egorov <ego...@linux.com> --- I can reproduce it. Looks like a problem in kcodecs. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 235862] [VI Mode] Range operations in vi-input mode don't work
https://bugs.kde.org/show_bug.cgi?id=235862 Boris Egorov <ego...@linux.com> changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||http://commits.kde.org/ktex ||teditor/0ea97afbeddb19f598b ||ab98e01f31869852bdf62 Status|UNCONFIRMED |RESOLVED --- Comment #5 from Boris Egorov <ego...@linux.com> --- Git commit 0ea97afbeddb19f598bab98e01f31869852bdf62 by Boris Egorov. Committed on 12/02/2016 at 02:12. Pushed by egorov into branch 'master'. Add tests for #235862, just to make sure it is fixed REVIEW: 127045 M +4-0autotests/src/vimode/modes.cpp http://commits.kde.org/ktexteditor/0ea97afbeddb19f598bab98e01f31869852bdf62 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 343329] Remote files open up empty
https://bugs.kde.org/show_bug.cgi?id=343329 Boris Egorov <ego...@linux.com> changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #14 from Boris Egorov <ego...@linux.com> --- This bug appears to be fixed. Feel free to reopen this bug if you notice such behavior. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 348073] WISH: Implement a system tray plasmoid with XEmbed support
https://bugs.kde.org/show_bug.cgi?id=348073 Boris Pek <tehnic...@yandex.ru> changed: What|Removed |Added CC||tehnic...@yandex.ru --- Comment #7 from Boris Pek <tehnic...@yandex.ru> --- Hi there, xembed-sni-proxy is in plasma-workspace [1] since October, so this bug report might be closed. [1] https://quickgit.kde.org/?p=plasma-workspace.git=tree=xembed-sni-proxy -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 357341] kate .gnupg/secring.gpg crashes kate
https://bugs.kde.org/show_bug.cgi?id=357341
Boris Egorov <ego...@linux.com> changed:
What|Removed |Added
Status|UNCONFIRMED |CONFIRMED
Ever confirmed|0 |1
CC||ego...@linux.com
--- Comment #1 from Boris Egorov <ego...@linux.com> ---
I can reproduce it. It looks like the problem is in kcodecs.
UnicodeGroupProber::HandleData has this code:
if (4 >= aBuf[1] && aBuf[1] >= 0 && isprint(aBuf[0])) {
where isprint is a macro:
enum {
// non-relevant
CTYPE_PRINT = 1 << 6,
// non-relevant
};
#define ctype_test(c, t) ((ctype_data[(unsigned short)c] & t) != 0)
#define isprint(c) ctype_test((c), CTYPE_PRINT)
And sometimes aBuf contains negative values. So we got an out-of-bounds index
for ctype_data array: c is negative in "(unsigned short)c".
I don't know what to do with this, but I think it is a kcodecs bug.
--
You are receiving this mail because:
You are watching all bug changes.
[kate] [Bug 357341] kate .gnupg/secring.gpg crashes kate
https://bugs.kde.org/show_bug.cgi?id=357341 --- Comment #2 from Boris Egorov <ego...@linux.com> --- Created attachment 96479 --> https://bugs.kde.org/attachment.cgi?id=96479=edit gdb backtrace with additional info -- You are receiving this mail because: You are watching all bug changes.
