[kwin] [Bug 391322] Meta key randomly stops opening Plasma launcher menu
https://bugs.kde.org/show_bug.cgi?id=391322 --- Comment #85 from Andrés B.S. --- Hi Nate and Medin, I have experienced the same issue and adding back Alt+F1 seems to fix it. Had it happen on both Tumbleweed and Fedora. Interestingly, I had it happend after a few (~4) days of use, after adding it back it doesn't happen again. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 440330] Crash when opening PDF
https://bugs.kde.org/show_bug.cgi?id=440330 --- Comment #2 from Andrés B.S. --- Indeed, an iPhone 7 was plugged in (untrusted mode). The phone was being used to run Zoom, not much else, but it was drawing a lot of power. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440330] New: Crash when opening PDF
https://bugs.kde.org/show_bug.cgi?id=440330 Bug ID: 440330 Summary: Crash when opening PDF Product: plasmashell Version: 5.22.3 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: andresbs2...@protonmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.22.3) (Compiled from sources) Qt Version: 5.15.2 Frameworks Version: 5.84.0 Operating System: Linux 5.13.4-1-default x86_64 Windowing System: X11 Drkonqi Version: 5.22.3 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: In the middle of an exam, tried to open a PDF download from Firfox. No idea what happened, but this is the first time DrKonqui lets me report something lol It is not consistent, but it has happened to me a few times. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7fbcea253980 (LWP 4650))] [KCrash Handler] #6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49 #7 0x7fbcec6e5864 in __GI_abort () at abort.c:79 #8 0x7fbcec73eb17 in __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7fbcec84f826 "%s\n") at ../sysdeps/posix/libc_fatal.c:155 #9 0x7fbcec74673c in malloc_printerr (str=str@entry=0x7fbcec84da7f "free(): invalid pointer") at malloc.c:5626 #10 0x7fbcec747b0c in _int_free (av=, p=, have_lock=0) at malloc.c:4396 #11 0x7fbcec74b7f8 in __GI___libc_free (mem=) at malloc.c:3309 #12 0x7fbcec26ebe1 in idevice_free (device=0x7ffdde16fd50) at /usr/src/debug/libimobiledevice-1.3.0+git.20200910-1.5.x86_64/src/idevice.c:409 #13 0x7fbceed08d91 in operator() (__closure=) at /usr/src/debug/solid-5.84.0-2.1.x86_64/src/solid/devices/backends/imobile/imobiledevice.cpp:37 #14 QScopeGuard >::~QScopeGuard (this=, this=) at /usr/include/qt5/QtCore/qscopeguard.h:80 #15 Solid::Backends::IMobile::IMobileDevice::IMobileDevice(QString const&) (this=0x7ffdde16fbb0, udi=..., this=, udi=) at /usr/src/debug/solid-5.84.0-2.1.x86_64/src/solid/devices/backends/imobile/imobiledevice.cpp:72 #16 0x7fbceed0935b in Solid::Backends::IMobile::Manager::devicesFromQuery(QString const&, Solid::DeviceInterface::Type) (this=0x7ffdde16fbb0, parentUdi=..., type=Solid::DeviceInterface::PortableMediaPlayer) at /usr/src/debug/solid-5.84.0-2.1.x86_64/src/solid/devices/backends/imobile/imobilemanager.cpp:79 #17 0x7fbceecdd701 in Solid::Device::listFromQuery(Solid::Predicate const&, QString const&) (predicate=..., parentUdi=...) at /usr/src/debug/solid-5.84.0-2.1.x86_64/src/solid/devices/frontend/devicemanager.cpp:136 #18 0x7fbce790eea9 in KFilePlacesModel::Private::initDeviceList() (this=0x560b5dc5dea0) at /usr/src/debug/kio-5.84.0-1.2.x86_64/src/filewidgets/kfileplacesmodel.cpp:728 #19 operator() (__closure=) at /usr/src/debug/kio-5.84.0-1.2.x86_64/src/filewidgets/kfileplacesmodel.cpp:515 #20 QtPrivate::FunctorCall, QtPrivate::List<>, void, KFilePlacesModel::KFilePlacesModel(const QString&, QObject*):: >::call (arg=, f=) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:146 #21 QtPrivate::Functor, 0>::call, void> (arg=, f=) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:256 #22 QtPrivate::QFunctorSlotObject, 0, QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=, r=, a=, ret=) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:443 #23 0x7fbcecdaff5e in QObject::event(QEvent*) (this=0x560b5df834b0, e=0x560b5d63c690) at kernel/qobject.cpp:1314 #24 0x7fbcedb0fa7f in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x560b5df834b0, e=0x560b5d63c690) at kernel/qapplication.cpp:3632 #25 0x7fbcecd8396a in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x560b5df834b0, event=0x560b5d63c690) at kernel/qcoreapplication.cpp:1064 #26 0x7fbcecd869b7 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (receiver=0x0, event_type=0, data=0x560b595d50c0) at kernel/qcoreapplication.cpp:1821 #27 0x7fbcecddb7d3 in postEventSourceDispatch(GSource*, GSourceFunc, gpointer) (s=s@entry=0x560b59725aa0) at kernel/qeventdispatcher_glib.cpp:277 #28 0x7fbceb0a780f in g_main_dispatch (context=0x7fbce0005000) at ../glib/gmain.c:3337 #29 g_main_context_dispatch (context=0x7fbce0005000) at ../glib/gmain.c:4055 #30 0x7fbceb0a7b98 in g_main_context_iterate (context=context@entry=0x7fbce0005000, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4131 #31 0x7fbceb0a7c4f in g_main_context_iteration (context=0x7fbce0005000, may_block=1) at ../glib/gmain.c:4196 #32 0x7fbcecddae54 in
[kdeconnect] [Bug 436329] The clipboard sync may not work and users are not aware of why on Android > 10
https://bugs.kde.org/show_bug.cgi?id=436329 Andrés B.S. changed: What|Removed |Added Summary|The clipboard sync may not |The clipboard sync may not |work and users are not |work and users are not |aware of why|aware of why on Android > ||10 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 436329] The clipboard sync may not work and users are not aware of why
https://bugs.kde.org/show_bug.cgi?id=436329 Andrés B.S. changed: What|Removed |Added Summary|The clipboard sync may not |The clipboard sync may not |work and users are not |work and users are not |aware on why|aware of why -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 436329] New: The clipboard sync may not work and users are not aware on why
https://bugs.kde.org/show_bug.cgi?id=436329 Bug ID: 436329 Summary: The clipboard sync may not work and users are not aware on why Product: kdeconnect Version: unspecified Platform: Android OS: Android 11.x Status: REPORTED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: andresbs2...@protonmail.com Target Milestone: --- As shown in the Graphene OS FAQ: https://grapheneos.org/faq#clipboard Quote: "As of Android 10, only the configured default input method editor (your keyboard of choice) and the currently focused app can access the clipboard. Apps without focus cannot access the clipboard. This is a stricter restriction than preventing apps in the background from accessing it, since an app in the foreground or a foreground service cannot access it, only the foreground app that's currently focused. Clipboard managers need to be implemented by the keyboard chosen as the default by the user." There is no message printing a similar warning when the clipboard feature is enabled (note that it is enabled by default). I can confirm the behavior is as described above - the clipboard feature only works when the app is in focus (didn't try setting it as a default method). The KDE Connect app can still write into the clipboard (e.g. sync clipboard to the phone when copying text in the laptop). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 391322] Meta key randomly stops opening Plasma launcher menu
https://bugs.kde.org/show_bug.cgi?id=391322 --- Comment #63 from Andrés B.S. --- By chance, is this still an issue with Qt6? -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 436182] Merge KTimer, Kronometer, KAlarm and KTeaTime in one app, with a simple interface
https://bugs.kde.org/show_bug.cgi?id=436182 Andrés B.S. changed: What|Removed |Added CC||andresbs2...@protonmail.com --- Comment #3 from Andrés B.S. --- Created attachment 137961 --> https://bugs.kde.org/attachment.cgi?id=137961=edit Setting an alarm with KClock I like the idea of going all-in with KClock, I used it on my laptop when my smartphone broke, and I wasn't trusting my PinePhone with the alarms just yet. Bonus points for convergence because I didn't have to package KClock twice :D Works pretty good and honestly I thought it was the kind of program I'd expect bundled with Plasma out of the box. In my opinion, it is one of those things one usually does not need, but expect to be there when needed. Just one thing I don't like about KClock is the way to set the alarm time, the circular "selection" is tough to get right (especially if you have big fingers - not my case luckily), an alternative to input the time directly from the keyboard would be welcome. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 434408] Panel icon disappears after successful connection on 3G modem
https://bugs.kde.org/show_bug.cgi?id=434408 --- Comment #4 from Andrés B.S. --- Created attachment 136853 --> https://bugs.kde.org/attachment.cgi?id=136853=edit Icon appears while loading The icon appears while it is connecting so I think it is more likely to be option #2. At times, the network type changes from UMTS to HSUPA/HSDPA. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 434408] Panel icon disappears after successful connection on 3G modem
https://bugs.kde.org/show_bug.cgi?id=434408 --- Comment #2 from Andrés B.S. --- Both are set to Breeze Dark. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 434408] Panel icon disappears after successful connection on 3G modem
https://bugs.kde.org/show_bug.cgi?id=434408 Andrés B.S. changed: What|Removed |Added Summary|Panel icon disappears after |Panel icon disappears after |successful connection on 3G |successful connection on 3G |modm|modem -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 434408] New: Panel icon disappears after successful connection on 3G modm
https://bugs.kde.org/show_bug.cgi?id=434408 Bug ID: 434408 Summary: Panel icon disappears after successful connection on 3G modm Product: plasma-nm Version: 5.21.2 Platform: openSUSE RPMs OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jgrul...@redhat.com Reporter: andresbs2...@protonmail.com Target Milestone: --- Created attachment 136675 --> https://bugs.kde.org/attachment.cgi?id=136675=edit Disappeared icon SUMMARY After plugging in the USB modem and setting up the providerm, the icon disappears from the bottom panel. I can see for a breaf moment the signal bar and a U (presumably UMTS) STEPS TO REPRODUCE 1. Connnect the modem 2. Setup the internet at NM settings: - + button - mobile broadband - business as usual OBSERVED RESULT While the modem is connecting (blue circle in the panel icon) I can see the icon behind, but as soon as the blue circle disappears it looks like the attached screenshot. EXPECTED RESULT See the signal bar with the U indicating a connected modem. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20210307 KDE Plasma Version: 5.21.2 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.11.2-1-default OS Type: 64-bit Graphics Platform: X11 Graphics Processor: Mesa DRI Intel® HD Graphics 630 More info: I'm actually surprised that the modem worked out of the box. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 432260] Spectacle fails to create rectangular and active window screenshots on Wayland with multiple screens
https://bugs.kde.org/show_bug.cgi?id=432260 Andrés B.S. changed: What|Removed |Added CC||andresbs2...@protonmail.com --- Comment #26 from Andrés B.S. --- Not sure what the connection between this and the issue is, but I found out that the bug can be worked-around by launching spectacle as: QT_QPA_PLATFORM=wayland spectacle On Wayland, it seems to prefer xcb. Rectangular selection was working on the XOrg session. What I found out too, is that Spectacle itself would be part of the screenshot when doing rectangular selection, it would be sometimes caught in the middle of the animation (IIRC the effect is called "Scale"). Also, just a reminder that we currently have two Wayland sessions for openSUSE: "Full Wayland" forces QT_QPA_PLATFORM=GDK_BACKEND=wayland, while the "Wayland" session doesn't touch QT_QPA_PLATFORM. This issue does not happen on the Full Wayland for the reason mentioned above. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 430029] Touchpad not disabled with mouse plugged in until I click on Input Devices in system settings
https://bugs.kde.org/show_bug.cgi?id=430029 --- Comment #12 from Andrés B.S. --- Created attachment 135916 --> https://bugs.kde.org/attachment.cgi?id=135916=edit touchpad settings on wayland I switched to Tumbleweed yesterday since I was done adding a dozen repos to have the newest software I used to have that same menu as you until I launched a Wayland session on 5.20, since then I see the same reduced set of options as wayland, on xorg. I think this is a feature to have consistency, but I am not sure. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 430029] Touchpad not disabled with mouse plugged in until I click on Input Devices in system settings
https://bugs.kde.org/show_bug.cgi?id=430029 --- Comment #9 from Andrés B.S. --- I'm on 5.21 and don't see the option to disable the touchpad when a mouse is connected, not sure where or what are you looking at My touchpad did not want work after the update, but same as before, doing rm ~/.config/touchpad* fixed it -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428112] Download folder still points to old folder after change in settings
https://bugs.kde.org/show_bug.cgi?id=428112 Andrés B.S. changed: What|Removed |Added Version|5.18.5 |5.21.0 --- Comment #4 from Andrés B.S. --- Just confirmed, the issue persists on 5.21.0 (I haven't changed any folder settings since my previous comment) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432996] Squash effect minimizes applications to a non-existant panel after removing it
https://bugs.kde.org/show_bug.cgi?id=432996 --- Comment #3 from Andrés B.S. --- Created attachment 135744 --> https://bugs.kde.org/attachment.cgi?id=135744=edit xprops for several situations Attached xprop outputs for different conditions. One thing I also noticed is that the minimize button may be confusing if the panel is at the top since it points to the bottom, but it is also a minor thing and I don't think that many people will care about it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432996] Squash effect minimizes applications to a non-existant panel after removing it
https://bugs.kde.org/show_bug.cgi?id=432996 Andrés B.S. changed: What|Removed |Added Summary|Animations minize |Squash effect minimizes |applications to a |applications to a |non-existant panel after|non-existant panel after |removing it |removing it -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432996] New: Animations minize applications to a non-existant panel after removing it
https://bugs.kde.org/show_bug.cgi?id=432996 Bug ID: 432996 Summary: Animations minize applications to a non-existant panel after removing it Product: plasmashell Version: 5.20.90 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: andresbs2...@protonmail.com Target Milestone: 1.0 Messing around with my system I added a second panel (one at the top and already had one at the bottom). After minimizing some open applications and removing the top Panel, leaving only the bottom one, the animation (Squash effect) 'squahes' the windows to the just removed (top) Panel. Not a big deal, but it may help uncover other bugs. I am using an X.Org session. Operating System: openSUSE Leap 15.2 KDE Plasma Version: 5.20.90 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.3.18-lp152.63-default OS Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 431527] Screen lock when windows are minimized (Meta+D) could potentially leak private information
https://bugs.kde.org/show_bug.cgi?id=431527 Andrés B.S. changed: What|Removed |Added Status|RESOLVED|CLOSED --- Comment #2 from Andrés B.S. --- Perfect, thanks! -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 431527] New: Screen lock when windows are minimized (Meta+D) could potentially leak private information
https://bugs.kde.org/show_bug.cgi?id=431527 Bug ID: 431527 Summary: Screen lock when windows are minimized (Meta+D) could potentially leak private information Product: kscreenlocker Version: unspecified Platform: openSUSE RPMs OS: Other Status: REPORTED Severity: major Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: andresbs2...@protonmail.com CC: bhus...@gmail.com Target Milestone: --- SUMMARY When pressing Meta+D small previews of the minimized windows can be seen at the lock screen. This can be reproduced by pressing Meta+D and waiting or pressing Meta+L. Operating System: openSUSE Leap 15.2 KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Kernel Version: 5.3.18-lp152.57-default -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428112] Download folder still points to old folder after change in settings
https://bugs.kde.org/show_bug.cgi?id=428112 --- Comment #3 from Andrés B.S. --- Feel free to close if you want, due to the new Kickoff (I wasn't aware of it when reported). Unless the issue persists there, of course. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 431241] New: Tabs should have their own terminal session
https://bugs.kde.org/show_bug.cgi?id=431241 Bug ID: 431241 Summary: Tabs should have their own terminal session Product: kate Version: 20.12.0 Platform: Other OS: Other Status: REPORTED Severity: wishlist Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: andresbs2...@protonmail.com Target Milestone: --- Sometimes I wan't to switch between tabs and leave a command running on one tab while a different thing on the other. What happens is a cd command popping up constantly when switching (which is fine, but that's why this is classified as wishlist) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 391322] Meta key randomly stops opening Plasma launcher menu
https://bugs.kde.org/show_bug.cgi?id=391322 Andrés B.S. changed: What|Removed |Added CC||andresbs2...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425436] F2 rename does not work in the desktop
https://bugs.kde.org/show_bug.cgi?id=425436 Andrés B.S. changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 430340] Entries starting with a space are ignored when moving through the history
https://bugs.kde.org/show_bug.cgi?id=430340 Andrés B.S. changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 430340] Entries starting with a space are ignored when moving through the history
https://bugs.kde.org/show_bug.cgi?id=430340 Andrés B.S. changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |NOT A BUG --- Comment #2 from Andrés B.S. --- You are right! I did not know this was thing! ~> echo $HISTCONTROL ignoreboth Quote from them (GNU): "A value of ‘ignoreboth’ is shorthand for ‘ignorespace’ and ‘ignoredups’." -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 430340] New: Entries starting with a space are ignored when moving through the history
https://bugs.kde.org/show_bug.cgi?id=430340 Bug ID: 430340 Summary: Entries starting with a space are ignored when moving through the history Product: konsole Version: 20.12.0 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: history Assignee: konsole-de...@kde.org Reporter: andresbs2...@protonmail.com Target Milestone: --- Created attachment 134053 --> https://bugs.kde.org/attachment.cgi?id=134053=edit Testing the history with echo "test" As the title says: entries starting with a space are ignored when moving through the history. i.e. Try running " env", and press the up arrow Running "env" does show it in the history. Taking a look at ~/.bash_history shows the entry is not being stored, so I am not sure if this a bug or a feature. I attached screenshots that show the history before and after reopneing Konsole. The session at the left picture starts after the clear command in the history at the right picture. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 430029] Touchpad not disabled with mouse plugged in until I click on Input Devices in system settings
https://bugs.kde.org/show_bug.cgi?id=430029 --- Comment #5 from Andrés B.S. --- Yes! But you are on the LTS version (the one shipped with Leap by default). Honestly, my touchpad did disable itself when I plugged my mouse after deleting touchpadrc and tweaking my settings again. The thing that led me to that solution was that after switching to KDE repos, KDE Connect was showing duplicated notifications, which I also fixed by deleting all kdeconnect related settings at ~/.config and setting up everything again. Probably the version jump was big for my system. Other users reported issues with the touchpad disable option (Tumbleweed) on the openSUSE Telegram, first it disappeared, then it came back but did not work. They probably fixed it by now. I think it was when 5.20.3 came out. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 430029] Touchpad not disabled with mouse plugged in until I click on Input Devices in system settings
https://bugs.kde.org/show_bug.cgi?id=430029 Andrés B.S. changed: What|Removed |Added CC||andresbs2...@protonmail.com --- Comment #2 from Andrés B.S. --- I'm using Leap w/ KDE repos and Plasma 5.20.4. For me, the touchpad does not disable at all when I plug-in my mouse. Horizontal scrolling was not working for me, but deleting ~/.config/touchpadrc fixed it... no luck with disabling the touchpad, though. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 428568] When opening a pdf with open new files in tabs it opens on a separate window
https://bugs.kde.org/show_bug.cgi?id=428568 Andrés B.S. changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425661] Keyboard language distrution change overlay not showing
https://bugs.kde.org/show_bug.cgi?id=425661 Andrés B.S. changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425661] Keyboard language distrution change overlay not showing
https://bugs.kde.org/show_bug.cgi?id=425661 Andrés B.S. changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #1 from Andrés B.S. --- Deleted ~/.config a couple weeks ago and it started showing again. Apparently it has to with how I setup my shortcuts, it depends if I use Advanced, Main, 3rd level or Alternative. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 428568] New: When opening a pdf with open new files in tabs it opens on a separate window
https://bugs.kde.org/show_bug.cgi?id=428568 Bug ID: 428568 Summary: When opening a pdf with open new files in tabs it opens on a separate window Product: okular Version: 1.11.1 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: andresbs2...@protonmail.com Target Milestone: --- OS: Windows 10 (2004) If a PDF is openend from Okular (File<
[kdeconnect] [Bug 428246] Screen turns off while pointer is in use
https://bugs.kde.org/show_bug.cgi?id=428246 --- Comment #1 from Andrés B.S. --- I forgot to add, this behavior extends to the Android app, because it also lets the phone's display time out while the pointer is in use. Steady fingers are required, though. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 428246] New: Screen turns off while pointer is in use
https://bugs.kde.org/show_bug.cgi?id=428246 Bug ID: 428246 Summary: Screen turns off while pointer is in use Product: kdeconnect Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: plasmoid Assignee: albertv...@gmail.com Reporter: andresbs2...@protonmail.com Target Milestone: --- The screen times out when using kdeconnect's pointer (slideshow remote). That is, it dims and then it turns off as expected because of the power settings. I believe, kdeconnect is supposed to tell the system not to go idle while the pointer is in use (which is useful for things that aren't slideshows as well), a message should be seen at the Battery and Brightness plasmoid showing "kdeconnect is currently supressing power management", but that isn't the case. kdeconnect version: 20.04.2-lp152.2.3.1 Operating System: openSUSE Leap 15.2 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.71.0 Qt Version: 5.12.7 Kernel Version: 5.3.18-lp152.47-default -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428112] New: Download folder still points to old folder after change in settings
https://bugs.kde.org/show_bug.cgi?id=428112 Bug ID: 428112 Summary: Download folder still points to old folder after change in settings Product: plasmashell Version: 5.18.5 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: andresbs2...@protonmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 132643 --> https://bugs.kde.org/attachment.cgi?id=132643=edit This submenu SUMMARY After changing the Downloads folder at Locations (System Settings), the submenu "Computer" contains a link to the old Downloads folder, instead of the new one. Operating System: openSUSE Leap 15.2 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.71.0 Qt Version: 5.12.7 This was reproducible on the newest Tumbleweed snapshot (10/20/20 IIRC), as well. In order to prevent confusion, I'll attach a picture of the submenu I am talking about. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426260] NVIDIA Optimus: Plasma boots a black desktop on multi-screen setup; wallpaper returns after changing display setup
https://bugs.kde.org/show_bug.cgi?id=426260 --- Comment #8 from Andrés B.S. --- Created attachment 132372 --> https://bugs.kde.org/attachment.cgi?id=132372=edit journalctl and dmesg output journalctl was captured about 30 minutes before posting this. (the issue happened again that boot). I booted the system around 20:50, and hope these logs might shed some light on what's going on. Current versions: Operating System: openSUSE Leap 15.2 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.71.0 Qt Version: 5.12.7 Kernel Version: 5.3.18-lp152.44-default -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426260] NVIDIA Optimus: Plasma boots a black desktop on multi-screen setup; wallpaper returns after changing display setup
https://bugs.kde.org/show_bug.cgi?id=426260 --- Comment #7 from Andrés B.S. --- It happened today again, so at least I know it's not an NVIDIA driver thing because I checked the loaded modules and I could confirm I was using only nouveau. I also read the following report: https://bugs.kde.org/show_bug.cgi?id=369450 Seems to match my situation and the behavior is exactly the same. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426941] New: Weird resizing of the screen selector (Meta+P) if arrows are pressed while holding meta
https://bugs.kde.org/show_bug.cgi?id=426941 Bug ID: 426941 Summary: Weird resizing of the screen selector (Meta+P) if arrows are pressed while holding meta Product: plasmashell Version: 5.18.5 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: andresbs2...@protonmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 131920 --> https://bugs.kde.org/attachment.cgi?id=131920=edit Huge overlay SUMMARY This is expected behavior, but I still don't think it should be happening. Press Meta+P and the press Meta+[any arrow] and the overlay resizes (it gets huge!). See attached picture. This may happen with other overlays, but I didn't test further. Operating System: openSUSE Leap 15.2 (also happens on Tumbleweed 23/sept/2020) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.71.0 Qt Version: 5.12.7 Kernel Version: 5.3.18-lp152.41-default -- You are receiving this mail because: You are watching all bug changes.
