[kdeconnect] [Bug 429690] KDE Connect detects phones but won't detect other computers
https://bugs.kde.org/show_bug.cgi?id=429690 --- Comment #5 from Daniel Tang --- On or before 2020-03-09, openssl-1.1.1j reached the main Ubuntu 21.04 repo. KDE Connect now works properly between my two Linux computers now. @Mauro: Did the update also reach you? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 434196] New: No touchscreen support in kmail
https://bugs.kde.org/show_bug.cgi?id=434196 Bug ID: 434196 Summary: No touchscreen support in kmail Product: kmail2 Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: danielzgtg.opensou...@gmail.com Target Milestone: --- SUMMARY I can't scroll the email list and folder tree with a touchscreen. STEPS TO REPRODUCE 1. Try to touch and scroll the list of emails with your finger 2. Try to touch and scroll the folder tree with your finger OBSERVED RESULT The touch is treated as if it was a mouse. This is not what one usually wants, and this makes it hard to scroll. EXPECTED RESULT The touch should scroll just like in Dolphin. The rest of the gestures from https://invent.kde.org/system/dolphin/-/commit/d7b33b76a18b14e9f286e4d8326b00910b9ea02a should also be supported. ANALYSIS I tried to add a QScroller to two classes with QTreeView in Akonadi Widgets. The folder tree started scrolling to touch, but the drag and drop was still active. This didn't work with the list of emails did not scroll at all. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 21.04 KDE Plasma Version: 5.21.2 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kmail: kmail2 5.16.3 (20.12.3) -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 429690] KDE Connect detects phones but won't detect other computers
https://bugs.kde.org/show_bug.cgi?id=429690 --- Comment #4 from Daniel Tang --- > Proposed solution: That is more like a hack rather than a solution. > can you try the above proposal? I tried it and it works. openssl-1.1.1h was missing so I used openssl-1.1.1j. However, I downgraded the packages right after confirming that they work. I don't want to break everything else on my machine. I also don't know the security implications of installing a cryptography package from an untrusted source like a PPA > It will definitely solved in 21.04 I am on 21.04. We're already in Feature Freeze and this bug still isn't fixed -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 433902] Missing unsubscribe link in email
https://bugs.kde.org/show_bug.cgi?id=433902 --- Comment #4 from Daniel Tang --- I reported this upstream at https://bugzilla.mozilla.org/show_bug.cgi?id=1696268 -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 433902] New: Missing unsubscribe link in email
https://bugs.kde.org/show_bug.cgi?id=433902 Bug ID: 433902 Summary: Missing unsubscribe link in email Product: bugs.kde.org Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: sysad...@kde.org Reporter: danielzgtg.opensou...@gmail.com CC: she...@kde.org Target Milestone: --- SUMMARY The emails sent by bugzilla_nore...@kde.org lack an unsubscribe button. The footer only contains plain text with "You are receiving this mail because" and a list of reasons. This is a problem: - This is against the law in many countries - Some spam filters might not like it - Most professional email bots include the link I just thought of this when I was checking my email today. No, I myself don't want to be removed from any CC list. I know how to remove myself or ignore bug mail STEPS TO REPRODUCE 1. Add yourself to the CC list for some bug 2. Comment 3. Open the email you received OBSERVED RESULT There is no unsubscribe link in the email EXPECTED RESULT There should be an unsubscribe link. It should behave just like the unsubscribe link in the emails from our GitLab SOFTWARE/OS VERSIONS BugZilla: I don't know -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 429690] KDE Connect detects phones but won't detect other computers
https://bugs.kde.org/show_bug.cgi?id=429690 Daniel Tang changed: What|Removed |Added CC||danielzgtg.opensource@gmail ||.com --- Comment #2 from Daniel Tang --- SUMMARY I can't connect two Linux computers together. Both of the computers connect fine to my Android though. STEPS TO REPRODUCE 1. Open the device list 2. Click refresh OBSERVED RESULT The other computer doesn't show up in the list. Sometimes it appears for a split second then disappears. When running `kdeconnectd` from the command line, I get the following errors logged: ``` kdeconnect.core: Disconnecting due to fatal SSL Error: "The issuer certificate of a locally looked up certificate could not be found" kdeconnect.core: Disconnecting due to fatal SSL Error: "No certificates could be verified" ``` EXPECTED RESULT Each computer should show up and appear properly on the other computer. ANALYSIS If I patch the code to also ignore `QSslError::UnableToGetLocalIssuerCertificate` and `QSslError::UnableToVerifyFirstCertificate`, the computers pair and connect properly. However, they stop working after `kdeconnectd` is stopped and restarted on any of them. When clicking refresh a bunch of times during the initial pairing, I see a lot of messages about the key being different for the same device. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 21.04 KDE Plasma Version: 5.21.1 KDE Frameworks Version: 5.79.0 Qt Version: 5.12.2 kdeconnect-kde: Git 44a7fc226fcd35bd082d78836ad2a3787ccde5b9 -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 433583] New: Jumping from description to title on details screen
https://bugs.kde.org/show_bug.cgi?id=433583 Bug ID: 433583 Summary: Jumping from description to title on details screen Product: drkonqi Version: 5.21.1 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: danielzgtg.opensou...@gmail.com Target Milestone: --- SUMMARY I had a hard time typing text in the crash reporter dialog. When I get to the part when it asks me for details, I am forcibly refocused to the title when I am entering the description. Eventually, I could only get the report filled out by typing what I wanted to say in Kate, then copy and pasting the text into the description text area. STEPS TO REPRODUCE 1. Have the crash dialog after experiencing the crash from https://bugs.kde.org/show_bug.cgi?id=433582 2. Choose the report the bug 3. Click through everything until it asks you to enter the details (a title and description) 4. Enter a title 5. Click on the description text area 6. Try to enter a description OBSERVED RESULT The first keystroke causes the same letter to be typed in both the title and description. Further keystrokes only go to the title, even though the description still appears visually focused blue. The title also appears focused at the same time. EXPECTED RESULT When I type in the description text area, the text should go there and only there. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 433582] New: Crash when searching process list
https://bugs.kde.org/show_bug.cgi?id=433582 Bug ID: 433582 Summary: Crash when searching process list Product: plasma-systemmonitor Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: danielzgtg.opensou...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Application: plasma-systemmonitor (5.21.1) Qt Version: 5.15.2 Frameworks Version: 5.79.0 Operating System: Linux 5.10.13-surface x86_64 Windowing System: X11 Drkonqi Version: 5.21.1 Distribution: Ubuntu Hirsute Hippo (development branch) -- Information about the crash: - What I was doing when the application crashed: I was searching the process list for a process. System monitor crashed before I could fully enter the name The reporter is unsure if this crash is reproducible. -- Backtrace: Application: System Monitor (plasma-systemmonitor), signal: Segmentation fault [KCrash Handler] #4 0x7f02ebf06831 in KDescendantsProxyModel::mapFromSource (this=0x55f0200733a0, sourceIndex=...) at ./src/core/kdescendantsproxymodel.cpp:607 #5 0x7f02ebf07be7 in KDescendantsProxyModelPrivate::sourceRowsAboutToBeRemoved (this=0x55f0200735c0, parent=..., start=27, end=28) at ./src/core/kdescendantsproxymodel.cpp:910 #6 0x7f02fe0a5b14 in doActivate (sender=0x55f01fb76200, signal_index=14, argv=argv@entry=0x7fff786ab6b0) at kernel/qobject.cpp:3898 #7 0x7f02fe09ec88 in QMetaObject::activate (sender=sender@entry=0x55f01fb76200, m=m@entry=0x7f02fe306640 , local_signal_index=local_signal_index@entry=11, argv=argv@entry=0x7fff786ab6b0) at kernel/qobject.cpp:3946 #8 0x7f02fe007722 in QAbstractItemModel::rowsAboutToBeRemoved (this=this@entry=0x55f01fb76200, _t1=..., _t2=, _t2@entry=27, _t3=, _t3@entry=28, _t4=...) at .moc/moc_qabstractitemmodel.cpp:599 #9 0x7f02fe00f7b6 in QAbstractItemModel::beginRemoveRows (this=0x55f01fb76200, parent=..., first=27, last=28) at itemmodels/qabstractitemmodel.cpp:2818 #10 0x7f02fe041335 in QSortFilterProxyModelPrivate::remove_proxy_interval (emit_signal=true, orient=Qt::Vertical, proxy_parent=..., proxy_end=28, proxy_start=27, proxy_to_source=..., source_to_proxy=..., this=0x55f020073830) at itemmodels/qsortfilterproxymodel.cpp:784 #11 QSortFilterProxyModelPrivate::remove_source_items (this=0x55f020073830, source_to_proxy=..., proxy_to_source=..., source_items=..., source_parent=..., orient=Qt::Vertical, emit_signal=true) at itemmodels/qsortfilterproxymodel.cpp:765 #12 0x7f02fe04189c in QSortFilterProxyModelPrivate::handle_filter_changed (this=0x55f020073830, source_to_proxy=..., proxy_to_source=..., source_parent=..., orient=Qt::Vertical) at itemmodels/qsortfilterproxymodel.cpp:1344 #13 0x7f02fe041c8d in QSortFilterProxyModelPrivate::filter_changed (this=0x55f020073830, source_parent=...) at itemmodels/qsortfilterproxymodel.cpp:1277 #14 0x7f02fe041d3a in QSortFilterProxyModelPrivate::filter_changed (this=0x55f020073830, source_parent=...) at itemmodels/qsortfilterproxymodel.cpp:1292 #15 0x7f02fe04287a in QSortFilterProxyModel::setFilterWildcard (this=, pattern=...) at itemmodels/qsortfilterproxymodel.cpp:2817 #16 0x7f02dc361966 in ProcessSortFilterModel::setFilterString (this=0x55f01fb76200, newFilterString=...) at ./src/table/ProcessSortFilterModel.cpp:114 #17 0x7f02dc35847b in ProcessSortFilterModel::qt_metacall (this=0x55f01fb76200, _c=QMetaObject::WriteProperty, _id=0, _a=0x7fff786abc10) at ./obj-x86_64-linux-gnu/src/table/TablePlugin_autogen/EWIEGA46WW/moc_ProcessSortFilterModel.cpp:233 #18 0x7f02ff5c15c2 in QQmlVMEMetaObject::metaCall (this=0x55f0200732f0, o=, c=QMetaObject::WriteProperty, _id=, a=0x7fff786abc10) at qml/qqmlvmemetaobject.cpp:954 #19 0x7f02ff4fd5a2 in QV4::QObjectWrapper::setProperty (engine=0x55f01dedfa10, object=0x55f020046220, property=0x7f02e4634cf8, value=...) at ../../include/QtQml/5.15.2/QtQml/private/../../../../../src/qml/qml/qqmlpropertydata_p.h:285 #20 0x7f02ff4fdbf7 in QV4::QObjectWrapper::setQmlProperty (value=..., revisionMode=QV4::QObjectWrapper::IgnoreRevision, name=, object=0x55f020046220, qmlContext=, engine=0x55f01dedfa10) at jsruntime/qv4qobjectwrapper.cpp:435 #21 QV4::QObjectWrapper::setQmlProperty (engine=0x55f01dedfa10, qmlContext=, object=0x55f020046220, name=, revisionMode=QV4::QObjectWrapper::IgnoreRevision, value=...) at jsruntime/qv4qobjectwrapper.cpp:418 #22 0x7f02ff4fdd95 in QV4::QObjectWrapper::virtualPut (m=0x7f02f11a4570, id=..., value=..., receiver=0x7f02f11a4570) at jsruntime/qv4qobjectwrapper.cpp:722 #23 0x7f02ff48e307 in QV4::Object::put (receiver=0x7f02f11a4570, v=..., name=0x7f02f11a4578, this=0x7f02f11a4570) at ../../include/QtQml/5.15.2/QtQml/private/../../../../../src/qml/jsruntime/qv4string_
[plasmashell] [Bug 432986] Can't tap on profile photo
https://bugs.kde.org/show_bug.cgi?id=432986 --- Comment #2 from Daniel Tang --- I can confirm this is fixed. Operating System: Ubuntu 21.04 KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 428914] Many Plasma Components do not work properly with a stylus, but work fine with touch
https://bugs.kde.org/show_bug.cgi?id=428914 --- Comment #18 from Daniel Tang --- Dolphin does not work properly for me. This might be because I am on 2x HiDPI. When I try to select a row in the file listing or the list containing places/devices, the selection is off by some distance. The misalignment worsens when I move Dolphin to the bottom right corner of my screen, as compared to the top left corner. This means I am unable to actually open any folders or files. Clicks to the list headers are also misaligned horizontally, causing clicks to the left part of "Name" to go to "Size" or "Modified". The good thing here though is that clicking actually has an effect. The big buttons, the address, and the bottom slider don't work. The window decorations do work. Also, I don't remember whether the alignment was fine a while ago or I am confusing this with my attempts at touch. This also affects System Settings. The taskbar's calendar, desktop switcher, opening Kickoff, launching pinned applications, focusing running applications, clicking tray icons, status and notifications, and show desktop work. The WiFi applet still doesn't work properly. I can't scroll or connect/disconnect. I can though enable/disable WiFi, search, and clear search. Touching the stylus down on an item causes it to expand and collapse. Switching from "Speed" to "Details" in the active item doesn't work. Nothing inside Kickoff works. Operating System: Ubuntu 21.04 KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Tablet: Intuos Pen Small [033B] -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 432989] New: Touchpad settings reset after reconnecting
https://bugs.kde.org/show_bug.cgi?id=432989 Bug ID: 432989 Summary: Touchpad settings reset after reconnecting Product: systemsettings Version: 5.20.90 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_touchpad Assignee: plasma-b...@kde.org Reporter: danielzgtg.opensou...@gmail.com Target Milestone: --- SUMMARY Touchpad settings are not applied after disconnecting and reconnecting the Surface Type Cover. STEPS TO REPRODUCE 1. Have a custom cursor speed, natural scrolling on, and tap-to-click on, unlike the defaults 2. Start up and log into tablet with the Surface Type Cover connected 3. Use the touchpad and observe the settings to be working 4. Detach the Surface Type Cover 5. Reattach the Surface Type Cover 6. Use the touchpad and observe again OBSERVED RESULT My settings are not applied. The cursor is slower than comfortable. The scroll direction is opposite to what I prefer, and I can't tap to click. The error state does not persist across a reboot. A workaround is to run "kcminit" or even just opening System Settings and clicking "Apply" on the touchpad settings after changing a setting away and back. EXPECTED RESULT My touchpad should keep the same settings before and after reconnecting it. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 21.04 KDE Plasma Version: 5.20.90 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION First reported at https://github.com/linux-surface/linux-surface/issues/342 linux-surface on Surface Pro 7 Type cover is probably this version: https://www.microsoft.com/en-ca/p/surface-pro-type-cover/91v4vtmhxwpm -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 423813] Touchpad settings aren’t automatically applied to bluetooth dock containing touchpad
https://bugs.kde.org/show_bug.cgi?id=423813 Daniel Tang changed: What|Removed |Added CC||danielzgtg.opensource@gmail ||.com --- Comment #1 from Daniel Tang --- Does running the command `kcminit` work just as well as "edit touchpad configuration and use apply"? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432986] Can't tap on profile photo
https://bugs.kde.org/show_bug.cgi?id=432986 Daniel Tang changed: What|Removed |Added Version|master |5.20.90 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432987] New: Wacom tablet input is ignored
https://bugs.kde.org/show_bug.cgi?id=432987 Bug ID: 432987 Summary: Wacom tablet input is ignored Product: plasmashell Version: 5.20.90 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: danielzgtg.opensou...@gmail.com CC: mikel5...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Kickoff completely ignores input from my Wacom tablet, unlike the rest of Plasmashell or KDE. STEPS TO REPRODUCE 1. Hover the pen until the cursor is above the KDE icon, then touch the pen down to the Wacom tablet to click 2. Do the same thing to move anywhere inside the menu, then click again OBSERVED RESULT Nothing happens. I've tried clicking "Applications", "Places", "Sleep", "Restart", "Shut Down", "Leave...", my username, my profile photo, all of my favourites, all of the categories, the arrows on the categories, and the scroll bars. I have also tried dragging (all 4 directions) to scroll the list of categories. Other parts of Plasmashell respond properly to the Wacom tablet, such as the desktop switcher, pinned applications, open windows, taskbar icons, the clock. Dolphin and System Settings also respond. Parts of Kickoff respond properly to a touchscreen and touchpad, but they completely ignore my Wacom tablet. EXPECTED RESULT Input from my Wacom tablet should elict the same response from Kickoff as input from my touchscreen SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 21.04 KDE Plasma Version: 5.20.90 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION linux-surface on Surface Pro 7 Intuos Pen Small [033B] The problem occurs even after kquitapp5 and kstart5 plasmashell -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432986] New: Can't tap on profile photo
https://bugs.kde.org/show_bug.cgi?id=432986 Bug ID: 432986 Summary: Can't tap on profile photo Product: plasmashell Version: master Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: danielzgtg.opensou...@gmail.com CC: mikel5...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 SUMMARY It is very hard to tap to open settings on a touchscreen. Tapping the profile picture in the menu works significantly less often than tapping a pinned icon in the taskbar. This does not occur with a touchpad, even when dragging. A while ago, I had to tap around 10 times for it to work. Today it only worked once after tapping a hundred times. STEPS TO REPRODUCE 1. Tap the KDE icon on the taskbar to open Kickoff 2. Tap your profile photo 3. Count the number of times you have to repeat step 2 before settings open OBSERVED RESULT I have to tap too many times for it to work. EXPECTED RESULT It should work after just one tap. Alternatively, if I'm not supposed to be able to open it on a touchscreen, there shouldn't be the outline that suggests clickability. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 21.04 (available in About System) KDE Plasma Version: 5.20.90 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION linux-surface on Surface Pro 7 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 427790] Lack of exit button
https://bugs.kde.org/show_bug.cgi?id=427790 --- Comment #13 from Daniel Tang --- > I just want to close the app How about a further "Disconnect from all devices" button on the settings screen that does the 3 things, causing the app and service to exit? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 427790] Lack of exit button
https://bugs.kde.org/show_bug.cgi?id=427790 --- Comment #11 from Daniel Tang --- I can see several ways to get this implemented though. The most direct way, adding an exit action on the notification, isn't a good idea. There is a limit to the number of actions that Android will allow before ignoring the rest. As an aside, I thinking about a debug screen. In that screen (I'm thinking of something like Facebook's internal settings), there could be menu items like "force crash" or "jvm exit". Although that would be some kind of button, I don't think it would be any more convenient than the force quit button so this won't be the main solution. To design a more comprehensive solution, I though of Termius, whose notifications are only active when there is an active connection. This also reminds me of KDE's WiFi settings. In those settings, there is a "connect automatically with priority" thing, similar to other OS's connect automatically checkbox. Unlike Termius, KDE Connect also receives incoming connections, so a separate toggle would be necessary for that. It is fortunate that plans already exist in the code, with this named as "discovery mode". So basically this solution would involve 3 changes: - Implement discovery mode (option to reject unknown devices when pairing is not open) - Add a "connect automatically" toggle for each device. When it's unchecked, disconnect if connected, and reject further connection attempt - Dismiss the notification and stop the background service if discovery mode is disabled and "connect automatically" is disabled for all devices. This could be considered an optimization that naturally follows from the fact that we will never have connections to any device if both the previous two options are disabled What do you think of this? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 427790] Lack of exit button
https://bugs.kde.org/show_bug.cgi?id=427790 --- Comment #9 from Daniel Tang --- > didn't have a service That sentence explicitly mentions apps with services. > See other apps like Google Fit and AccuBattery -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 365305] Unable to use gesture typing.
https://bugs.kde.org/show_bug.cgi?id=365305 Daniel Tang changed: What|Removed |Added CC||danielzgtg.opensource@gmail ||.com --- Comment #4 from Daniel Tang --- I am also hoping this bug would be fixed, but to support my different use case. This bug seems to boil down to supporting the input of text instead of key strokes. Compared to a smartphone, it is difficult to type mathematical symbols, emojis, and foreign languages on a computer. I was hoping to use KDE Connect for that, but this bug prevents me from doing that -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 398848] Catch sound key up/down buttons
https://bugs.kde.org/show_bug.cgi?id=398848 Daniel Tang changed: What|Removed |Added CC||danielzgtg.opensource@gmail ||.com --- Comment #1 from Daniel Tang --- At attempt at this seems to be in the code. However, it is currently broken for me. > remote volume of the connected device. However, first I would only do this > when you are at the media control screen Looking at the code, is a possibility that this may have been implemented as changing the volume of a single music application instead of the system. I wasn't able to verify though. > adjust it everywhere, so maybe add an option in the settings, so I can also > control it when the screen is off This would have been a huge security problem if the Android OS had allowed such a thing. Imagine all of your apps messing with the volume buttons in the background, and you scrambling to figure out which one is responsible. The most that should be possible is a notification that acts as a lockscreen widget containing the volume buttons. > if you could just add your own "audio channel" That would cause Android to try and send all the audio to KDE Connect, leaving the phone speakers silent. Until we can stream audio to the computer, this would only confuse the user -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 427790] Lack of exit button
https://bugs.kde.org/show_bug.cgi?id=427790 Daniel Tang changed: What|Removed |Added CC||firesm...@protonmail.com --- Comment #7 from Daniel Tang --- *** Bug 414754 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 414754] Easy option to exit app
https://bugs.kde.org/show_bug.cgi?id=414754 Daniel Tang changed: What|Removed |Added Resolution|--- |DUPLICATE CC||danielzgtg.opensource@gmail ||.com Status|REPORTED|RESOLVED --- Comment #1 from Daniel Tang --- *** This bug has been marked as a duplicate of bug 427790 *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 427790] Lack of exit button
https://bugs.kde.org/show_bug.cgi?id=427790 Daniel Tang changed: What|Removed |Added CC||danielzgtg.opensource@gmail ||.com --- Comment #6 from Daniel Tang --- This is a bad idea because it would complicate and confuse both the user and developers. Android apps should not have an explicit exit button: https://stackoverflow.com/a/6014098/10477326 . This is according to general Android UI principles. See other apps like Google Fit and AccuBattery. The force close button would indeed play the role of the exit button if you really need to close the app. There should be exactly one easy and obvious way for users to do things, and this is it. Additionally, on mobile devices, applications should be able to close themselves, but rather follow the operating system's patterns (such as dismissal from recents or force stop) for doing that -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 428167] Android 10+ clipboard access restrictions
https://bugs.kde.org/show_bug.cgi?id=428167 Daniel Tang changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED CC||danielzgtg.opensource@gmail ||.com --- Comment #2 from Daniel Tang --- This seems to have been fixed, as there is a "SEND CLIPBOARD" action in the notification now -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 431455] Use kdeconnect to enter computer passwords
https://bugs.kde.org/show_bug.cgi?id=431455 Daniel Tang changed: What|Removed |Added CC||danielzgtg.opensource@gmail ||.com --- Comment #3 from Daniel Tang --- > when some program asks This would require there to be a consistent autofill framework on Linux. The only two things I can think of to try and support this is writing extensions for Google Chrome and PolicyKit. The rest of the ecosystem is hopelessly fragmented, if those apps support autofill at all. Therefore, I don't think this feature is feasible -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 432520] New: Crash when tapping playback notification
https://bugs.kde.org/show_bug.cgi?id=432520 Bug ID: 432520 Summary: Crash when tapping playback notification Product: kdeconnect Version: unspecified Platform: Android OS: Android 11.x Status: REPORTED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: danielzgtg.opensou...@gmail.com Target Milestone: --- SUMMARY KDE Connect crashed when I did tapped something in my notifications. STEPS TO REPRODUCE 1. Play a music video in the background with NewPipe on the phone, and wait for it to end 2. Play an audio file using VLC on the paired computer 3. Close VLC 4. Shut down the computer 5. Open the notification shade on the phone 6. Tap on NewPipe's notification's dismiss button (swipe down first) (the notification in the Android 11 media controls section, the first of a 2-page viewpager-like UI, with the second being KDE connect's notification describing media on the computer) 7. Accidentally touch the KDE Connect notification (I'm not really sure what happened in the first place, and I haven't attempted to reproduce this yet) OBSERVED RESULT It crashed with the following stack trace: 01-22 03:30:58.497 4919 4919 E AndroidRuntime: android.os.FileUriExposedException: file:///home/[username]/[redacted].webm exposed beyond app through Intent.getData() 01-22 03:30:58.497 4919 4919 E AndroidRuntime:at android.os.StrictMode.onFileUriExposed(StrictMode.java:2141) 01-22 03:30:58.497 4919 4919 E AndroidRuntime:at android.net.Uri.checkFileUriExposed(Uri.java:2391) 01-22 03:30:58.497 4919 4919 E AndroidRuntime:at android.content.Intent.prepareToLeaveProcess(Intent.java:11183) 01-22 03:30:58.497 4919 4919 E AndroidRuntime:at android.content.Intent.prepareToLeaveProcess(Intent.java:11134) 01-22 03:30:58.497 4919 4919 E AndroidRuntime:at android.app.Instrumentation.execStartActivity(Instrumentation.java:1909) 01-22 03:30:58.497 4919 4919 E AndroidRuntime:at android.app.Activity.startActivityForResult(Activity.java:5326) 01-22 03:30:58.497 4919 4919 E AndroidRuntime:at androidx.fragment.app.FragmentActivity.startActivityForResult(FragmentActivity.java:675) 01-22 03:30:58.497 4919 4919 E AndroidRuntime:at android.app.Activity.startActivityForResult(Activity.java:5284) 01-22 03:30:58.497 4919 4919 E AndroidRuntime:at androidx.fragment.app.FragmentActivity.startActivityForResult(FragmentActivity.java:662) 01-22 03:30:58.497 4919 4919 E AndroidRuntime:at android.app.Activity.startActivity(Activity.java:5670) 01-22 03:30:58.497 4919 4919 E AndroidRuntime:at android.app.Activity.startActivity(Activity.java:5623) 01-22 03:30:58.497 4919 4919 E AndroidRuntime:at org.kde.kdeconnect.Plugins.MprisPlugin.MprisActivity.onOptionsItemSelected(MprisActivity.java:418) 01-22 03:30:58.497 4919 4919 E AndroidRuntime:at android.app.Activity.onMenuItemSelected(Activity.java:4275) 01-22 03:30:58.497 4919 4919 E AndroidRuntime:at androidx.fragment.app.FragmentActivity.onMenuItemSelected(FragmentActivity.java:383) 01-22 03:30:58.497 4919 4919 E AndroidRuntime:at androidx.appcompat.app.AppCompatActivity.onMenuItemSelected(AppCompatActivity.java:228) 01-22 03:30:58.497 4919 4919 E AndroidRuntime:at androidx.appcompat.view.WindowCallbackWrapper.onMenuItemSelected(WindowCallbackWrapper.java:109) 01-22 03:30:58.497 4919 4919 E AndroidRuntime:at androidx.appcompat.app.AppCompatDelegateImpl.onMenuItemSelected(AppCompatDelegateImpl.java:1176) 01-22 03:30:58.497 4919 4919 E AndroidRuntime:at androidx.appcompat.view.menu.MenuBuilder.dispatchMenuItemSelected(MenuBuilder.java:834) 01-22 03:30:58.497 4919 4919 E AndroidRuntime:at androidx.appcompat.view.menu.MenuItemImpl.invoke(MenuItemImpl.java:158) 01-22 03:30:58.497 4919 4919 E AndroidRuntime:at androidx.appcompat.view.menu.MenuBuilder.performItemAction(MenuBuilder.java:985) 01-22 03:30:58.497 4919 4919 E AndroidRuntime:at androidx.appcompat.view.menu.MenuPopup.onItemClick(MenuPopup.java:128) 01-22 03:30:58.497 4919 4919 E AndroidRuntime:at android.widget.AdapterView.performItemClick(AdapterView.java:330) 01-22 03:30:58.497 4919 4919 E AndroidRuntime:at android.widget.AbsListView.performItemClick(AbsListView.java:1210) 01-22 03:30:58.497 4919 4919 E AndroidRuntime:at android.widget.AbsListView$PerformClick.run(AbsListView.java:3202) 01-22 03:30:58.497 4919 4919 E AndroidRuntime:at android.os.Handler.handleCallback(Handler.java:938) 01-22 03:30:58.497 4919 4919 E AndroidRuntime:at android.os.Handler.dispatchMessage(Handler.java:99) 01-22 03:30:58.497 4919 4919 E AndroidRuntime:at android.os.Looper.loop(Looper.java:233) 01-22 03:30:58.497 4919 4919 E And
[kdeconnect] [Bug 422472] Light theme text is missing on non-US English
https://bugs.kde.org/show_bug.cgi?id=422472 Daniel Tang changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- Ever confirmed|0 |1 --- Comment #2 from Daniel Tang --- This bug is happening again -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 429402] Plasmaconnect still crashes when using pointer button in slideshow menu
https://bugs.kde.org/show_bug.cgi?id=429402 Daniel Tang changed: What|Removed |Added CC||danielzgtg.opensource@gmail ||.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 420687] Unable to open Konsole with keyboard after a while
https://bugs.kde.org/show_bug.cgi?id=420687 Daniel Tang changed: What|Removed |Added Status|NEEDSINFO |RESOLVED --- Comment #3 from Daniel Tang --- This bug hasn't occurred to me since. But again, I haven't being using Android Studio much either. I've thought about this, and it seems like the problem is with DBus as I remember seeing a kglobalaccel5 crash and having DBus problems right before this issue started happening. I think the problem might be because DBus enters an error state and my environment variables are still pointing to that errored DBus. Konsole might be trying to do something with DBus on startup, and ends up waiting forever. I haven't had any Konsole, kglobalaccel5, or DBus problems since and my system has been stable for months, so I think some bug has been fixed somewhere -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 422472] Light theme text is missing on non-US English
https://bugs.kde.org/show_bug.cgi?id=422472 Daniel Tang changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 422473] New: Light/dark theme option doesn't persist across force quits
https://bugs.kde.org/show_bug.cgi?id=422473 Bug ID: 422473 Summary: Light/dark theme option doesn't persist across force quits Product: kdeconnect Version: unspecified Platform: Android OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: danielzgtg.opensou...@gmail.com Target Milestone: --- SUMMARY The new light/dark theme option doesn't get applied on process startup. This was first reported by Philip C-C on Telegram. STEPS TO REPRODUCE 1. Make sure the Android system theme is set to light 2. Set the theme to dark inside the KDE Connect app global settings 3. Force quit KDE Connect (or restart Android) 4. Open KDE Connect 5. Look at the theme color 6. Repeat steps 1-5 with the opposite combination OBSERVED RESULT When launching the app after it died, the theme matches the system theme instead. The "Choose theme" setting has no effect until it is changed again. EXPECTED RESULT The theme always matches the one set in "Choose theme". SOFTWARE/OS VERSIONS KDE Connect: c318d609 (first bad commit), d5946faf (latest commit) Last good commit is e315cbd9 Device: Android Studio Skin: Pixel XL Image: Android 10.0 (Q) Google APIs Intel x86 Atom System Image, API 29, Revision 10 This also affects real physical devices. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 422472] New: Light theme text is missing on non-US English
https://bugs.kde.org/show_bug.cgi?id=422472 Bug ID: 422472 Summary: Light theme text is missing on non-US English Product: kdeconnect Version: unspecified Platform: Android OS: Android 10.x Status: REPORTED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: danielzgtg.opensou...@gmail.com Target Milestone: --- SUMMARY The text in KDE Connect global settings's choose light theme is corrupt for all languages except "English (United States)". This bug is especially severe because one would expect missing translations to just fall back to U.S. English. Instead, the l10n daemon inserted garbage. STEPS TO REPRODUCE 1. Make sure the Android system language is set to "English (Canada)" 2. Open the drawer 3. Tap "Settings" 4. Tap "Choose theme" 5. Look at the middle option 6. Select it 7. Look at the preference list item description text The bug similarly affects many other languages expect "English (United States)". OBSERVED RESULT "Not set" appears in the preference list item description. The middle item in the radio button list in the dialog does not have any text. This is confusing because "Not set" suggests "Set by Battery Saver" instead. EXPECTED RESULT "Light" appears for both. SOFTWARE/OS VERSIONS KDE Connect: bd1d7ca6 (first bad commit), d5946faf (latest commit) Last good commit is 74532f0c Device: Android Studio Skin: Pixel XL Image: Android 10.0 (Q) Google APIs Intel x86 Atom System Image, API 29, Revision 10 This also affects real physical devices. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 399646] Brightness control adjusts the wrong backlight control (multiple GPUs)
https://bugs.kde.org/show_bug.cgi?id=399646 Daniel Tang changed: What|Removed |Added CC||danielzgtg.opensource@gmail ||.com --- Comment #3 from Daniel Tang --- The relevant PowerDevil code is at https://cgit.kde.org/powerdevil.git/tree/daemon/backends/upower/backlighthelper.cpp?id=5602920aeb852b3703ba357394e43454820460f3#n80 The GNOME backlight code has been moved from gnome-power-manager to https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/blob/523ffa148ce16773c2d9f711edb2c0424411d7ac/plugins/power/gsd-backlight.c#L119 An alternative code solution would be to affect *all* of the backlights at once. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413165] Please add option to reduce screen brightness in kcm_nightcolor
https://bugs.kde.org/show_bug.cgi?id=413165 --- Comment #5 from Daniel Tang --- This would be really nice. I updated KDE one day and noticed that it added built-in Night Color. I promptly enabled it and uninstalled redshift. I soon noticed that I had the brightness dimmed in redshift but in KDE there wasn't an option for that. I am on a desktop with dual external monitors. I can't change the brightness on the monitors themselves because they don't let me change the brightness in SRGB mode. I also don't want to turn off SRGB because the monitors are slightly different models and the color would be weird. I tried setting the brightness using xrandr but that undid the effect of Night Mode. I would greatly appreciate it if KDE Night Mode could change both the color and the brightness -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413165] Please add option to reduce screen brightness in kcm_nightcolor
https://bugs.kde.org/show_bug.cgi?id=413165 Daniel Tang changed: What|Removed |Added CC||danielzgtg.opensource@gmail ||.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 420687] New: Unable to open Konsole with keyboard after a while
https://bugs.kde.org/show_bug.cgi?id=420687 Bug ID: 420687 Summary: Unable to open Konsole with keyboard after a while Product: konsole Version: 19.12.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: danielzgtg.opensou...@gmail.com Target Milestone: --- SUMMARY After a while I stop being able to open Konsole with the keyboard. STEPS TO REPRODUCE 1. Spend an hour doing something like using Android Studio 2. Try one of the following: - Press SHIFT + F4 in Dolphin - Press CTRL + ALT + T anywhere (make sure it's set as a custom shortcut) 3. Try one of the following - Press F4 in Dolphin - Open Konsole from the start menu - Open another Konsole window by typing "konsole" in Bash OBSERVED RESULT None of the things in Step 2 work. They are silently ignored. All of the things in step 3 work. I can get "CTRL + ALT + T" to work if I "kquitapp5 kded5" and "kstart5 kded5". I can't get "SHIFT + F4" until I log out and log back in. Both the "CTRL + ALT + T" and "SHIFT + F4" seem to stop working at the same time. EXPECTED RESULT To be always able to open Konsole. That is, for the things in step 2 to always work just as well as the things in step 3. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 20.04 KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION This started happening in April 2020 (but I also started using Android Studio at that time). -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420538] New: System Settings crashed after changing global theme
https://bugs.kde.org/show_bug.cgi?id=420538 Bug ID: 420538 Summary: System Settings crashed after changing global theme Product: systemsettings Version: 5.18.4 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: danielzgtg.opensou...@gmail.com Target Milestone: --- Application: systemsettings5 (5.18.4) Qt Version: 5.12.8 Frameworks Version: 5.68.0 Operating System: Linux 5.4.0-26-generic x86_64 Windowing system: X11 Distribution: Ubuntu 20.04 LTS -- Information about the crash: - What I was doing when the application crashed: 1. Make sure that Breeze Dark is the current global theme 2. Open System Settings 3. Open and switch between some random modules (I don't remember which) 4. Open the global theme module 5. Select "Breeze" 6. Click "Apply" 7. Notice that the system becomes a mix of both themes for a moment 8. Notice that the System Settings window disappears 9: Notice that the system is now in the Breeze theme -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc8626f5800 (LWP 3385))] Thread 20 (Thread 0x7fc8062e7700 (LWP 3431)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55f380edc4d8) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55f380edc488, cond=0x55f380edc4b0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55f380edc4b0, mutex=0x55f380edc488) at pthread_cond_wait.c:638 #3 0x7fc852dfc3db in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7fc852dfbfeb in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7fc85f899609 in start_thread (arg=) at pthread_create.c:477 #6 0x7fc860d42103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 19 (Thread 0x7fc804c16700 (LWP 3429)): #0 0x7fc85efd733d in g_mutex_lock () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fc85ef8a2ce in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc8612de583 in QEventDispatcherGlib::processEvents (this=0x7fc7fff0, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #3 0x7fc8612854db in QEventLoop::exec (this=this@entry=0x7fc804c15d80, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #4 0x7fc8610bd785 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #5 0x7fc8603441a9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7fc8610be9d2 in QThreadPrivate::start (arg=0x55f37e90e1f0) at thread/qthread_unix.cpp:361 #7 0x7fc85f899609 in start_thread (arg=) at pthread_create.c:477 #8 0x7fc860d42103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 18 (Thread 0x7fc806e27700 (LWP 3406)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55f37fa1663c) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55f37fa165e8, cond=0x55f37fa16610) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55f37fa16610, mutex=0x55f37fa165e8) at pthread_cond_wait.c:638 #3 0x7fc852dfc3db in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7fc852dfbfeb in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7fc85f899609 in start_thread (arg=) at pthread_create.c:477 #6 0x7fc860d42103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 17 (Thread 0x7fc8079f4700 (LWP 3405)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55f37f6d72c8) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55f37f6d7278, cond=0x55f37f6d72a0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55f37f6d72a0, mutex=0x55f37f6d7278) at pthread_cond_wait.c:638 #3 0x7fc852dfc3db in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7fc852dfbfeb in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7fc85f899609 in start_thread (arg=) at pthread_create.c:477 #6 0x7fc860d42103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 16 (Thread 0x7fc8189f6700 (LWP 3404)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55f37f17014c) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55f37f1700f8, cond=0x55f37f170120) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55f37f170120, mutex=0x55f37f1700f8) at pthread_cond_wait.c:638 #3 0x7fc852dfc3db in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7fc852dfbfeb in ?? () fro
