[kdeconnect] [Bug 471313] KDE Connect doesn't find devices if computer is connected to more than one network
https://bugs.kde.org/show_bug.cgi?id=471313 --- Comment #4 from Andy3153 --- (In reply to Pedro V from comment #3) > I'm guessing that in both cases the issue is with broadcasting though, just > not sure how would that happen in the hotspot case with just one interface. > Maybe there are multiple interfaces in that case too even if they are not > connected to the same network, or there are interfaces not considered by the > users as they may not belong to physical connections. It clearly is an issue about broadcasting, and possibly just an issue about looking farther than the first network interface the computer connected to. As I said in the additional info part of my bug report, the problem is fixed if I disconnect the Ethernet, connect to the routerx then restsrt kdeconnectd. > Look at the findings I described in bug 470085 , you might have the same > issue, and it's actually not hard to check, it's not even necessary to > disconnect anything, the "Refresh" menu point on the phone side triggers > discovery, so you can either: > - Just spam and see if you can see a connection on either side for a > fraction of second > - Check the phone with logcat which is likely most feasible to use through > adb > - Check the PC by (optionally?) killing kdeconnectd and running: > QT_LOGGING_RULES="*.debug=true; qt.*.debug=false" > /usr/lib/x86_64-linux-gnu/libexec/kdeconnectd --replace > > I'm suspecting all these issues to be related even if the hotspot one is not > clear, but even there the remarks of adding by IP address suggests that > skipping the broadcast discovery phase is what fixes the issue. I'll try these when I get back home to my laptop, but, until then, could you point me to some documentation about android logcats? I have minimal ADB experience, none of which was related to logging/debugging android apps -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 471313] KDE Connect doesn't find devices if computer is connected to more than one network
https://bugs.kde.org/show_bug.cgi?id=471313 --- Comment #2 from Andy3153 --- (In reply to Pedro V from comment #1) > The issue may not be with the PC having two separate networks, the problem > may be a duplicate of bug 451154 instead. Nope. That bug report says that it happens every time with hotspot. Hotspot works every time for me if I am only connected to the hotspot. My problem appears only when the laptop is connected to two networks, ex. uni dorm room Ethernet cable and any WiFi router -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 471313] New: KDE Connect doesn't find devices if computer is connected to more than one network
https://bugs.kde.org/show_bug.cgi?id=471313 Bug ID: 471313 Summary: KDE Connect doesn't find devices if computer is connected to more than one network Classification: Applications Product: kdeconnect Version: 23.04.2 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: andy3...@protonmail.com CC: andrew.g.r.hol...@gmail.com Target Milestone: --- SUMMARY As I said, if the computer is connected to two networks, and the phone is on only one of those two networks, the computer and the phone won't detect eachother. STEPS TO REPRODUCE 1. Have a computer connected to two networks simultaneously (ex.: a laptop connected to both a network cable and WiFi) 2. Have a phone connected to one of those two networks (ex.: the WiFi) 3. Try to connect the devices with KDE Connect OBSERVED RESULT Neither device can observe the other device EXPECTED RESULT KDE Connect simply doesn't care the computer has two network cards that are both connected to two separate local networks and they just are able to find eachother normally SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux 6.3.8-zen1-1-zen (available in About System) KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION You might ask how I found out about this. I don't have a router where I currently live, so I usually keep my laptop plugged into Ethernet, and I use my phone with mobile data. But, when I wanna remotely control my laptop, I turn on mobile hotspot on my phone and have my laptop connect to both the Ethernet cable and my phone's hotspot (so, the laptop is connected to two local networks through two different network cards). What I need to do in order to get the two to connect together through KDE Connect is as follows: 1. Disconnect the laptop from Ethernet 2. Connect the laptop to the mobile hotspot so the phone and the laptop have a common local network for KDE Connect 3. Terminate kdeconnectd on the laptop 4. Open kdeconnect-app so that kdeconnectd starts back up with it 5. Reconnect the Ethernet cable 6. The laptop will be connected to both networks now, but KDE Connect will also function. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 447689] top latte panel ignores OnAllVirtualDesktops after startup
https://bugs.kde.org/show_bug.cgi?id=447689 --- Comment #14 from Andy3153 --- (In reply to Michail Vourlakos from comment #13) > feel free to test the patch Oh, sure! Could you please tell me how though? Is installing latte-dock-git from the AUR enough? Or do I need to manually clone the git repo and build it? -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 447689] top latte panel ignores OnAllVirtualDesktops after startup
https://bugs.kde.org/show_bug.cgi?id=447689 --- Comment #10 from Andy3153 --- (In reply to Michail Vourlakos from comment #9) > You can try to remove the widget and check results. > Without a proper way to reproduce in my system, such issues can not be > easily fixed. I just tried to remove the widget. Didn't do much. https://imgur.com/a/kfyO9Wh -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 447689] top latte panel ignores OnAllVirtualDesktops after startup
https://bugs.kde.org/show_bug.cgi?id=447689 --- Comment #8 from Andy3153 --- (In reply to Michail Vourlakos from comment #7) > unfortunately this is not reproducable in my system... > Are you sure this is not an issue with VirtualDesktopBar applet? > > you can try to remove it and check afterwards if it still happens in your > system How could that applet cause the problem when, firstly, it's not on the panel that has the problem, and secondly, the top dock remains on the virtual desktop Latte Dock has been opened on regardless of the method used to switch virtual desktops (either the widget or just KWin keyboard shortcuts)? -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 447689] top latte panel ignores OnAllVirtualDesktops after startup
https://bugs.kde.org/show_bug.cgi?id=447689 --- Comment #6 from Andy3153 --- (In reply to Michail Vourlakos from comment #5) > Does not open, what I need is, > > Right click dock, Layouts, Edit Layouts..., choose your layout, > Export...,Export as template Oh, export as template, okay, I did export as backup. Also Pastebin doesn't seem to work..? https://textdoc.co/uBpjwRqPZg9GI2xm -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 447689] top latte panel ignores OnAllVirtualDesktops after startup
https://bugs.kde.org/show_bug.cgi?id=447689 --- Comment #4 from Andy3153 --- (In reply to Michail Vourlakos from comment #3) > Ok I show it... > Please send also your latte layout to test it in my system. If by sending the layout you mean sending you a backup of it, here it is https://pastebin.com/7hzuMRRr -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 447689] One of my Latte docks doesn't move when switching virtual desktops
https://bugs.kde.org/show_bug.cgi?id=447689 --- Comment #1 from Andy3153 --- Created attachment 144958 --> https://bugs.kde.org/attachment.cgi?id=144958&action=edit Video showing the bug -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 447689] New: One of my Latte docks doesn't move when switching virtual desktops
https://bugs.kde.org/show_bug.cgi?id=447689 Bug ID: 447689 Summary: One of my Latte docks doesn't move when switching virtual desktops Product: lattedock Version: 0.10.6 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: andy3...@protonmail.com Target Milestone: --- SUMMARY On launch, one of my Latte panels doesn't move along with the change of the virtual desktop, while the other two do. STEPS TO REPRODUCE 1. Launch Latte Dock 2. Attempt to switch virtual desktops OBSERVED RESULT One of the panels remains on the virtual desktop that Latte Dock was first launched on. EXPECTED RESULT All Latte docks should move along with the virtual desktop since they are, well, docks. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION To make that panel move normally on other virtual desktops, I have to interact with a widget on it first. Info about the video: 1. I first close the currently running Latte Dock instance 2. I launch Latte Dock again 3. I show how the top panel doesn't move along with the other panels when I switch workspaces 4. I interact with a widget on the panel 5. I show how it fixes the problem after I do that I tried removing absolutely everything that has to do with Latte Dock (cache, configs) and re-making the entire layout. It did not fix things. (Also present in the video is the fact that "Hide background when not needed" is not working all the time, but that's another issue I might report a bug on.) -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 424247] After opening a file on FTP, MTP, trying to open another file will show an error
https://bugs.kde.org/show_bug.cgi?id=424247 --- Comment #2 from Andy3153 --- (In reply to Justin Zobel from comment #1) > I can't replicate this on kate from git master. > > Steps I used: > Open an ftp site in dolphin, opened a file that would load in kate > In the same dolphin window opened a text file from my home folder > > Both loaded OK > > Andy can you please re-test and confirm if this is still an issue for you? Now, with the latest version of Kate and anything related to KDE the bug doesn't occur anymore. So, I guess, great job devs! -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 424247] After opening a file on FTP, MTP, trying to open another file will show an error
https://bugs.kde.org/show_bug.cgi?id=424247 Andy3153 changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 424247] After opening a file on FTP, MTP, trying to open another file will show an error
https://bugs.kde.org/show_bug.cgi?id=424247 Andy3153 changed: What|Removed |Added Summary|Afteer opening a file on|After opening a file on |FTP, MTP, trying to open|FTP, MTP, trying to open |another file will show an |another file will show an |error |error -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 424247] New: Afteer opening a file on FTP, MTP, trying to open another file will show an error
https://bugs.kde.org/show_bug.cgi?id=424247 Bug ID: 424247 Summary: Afteer opening a file on FTP, MTP, trying to open another file will show an error Product: kate Version: 20.04.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: andy3...@protonmail.com Target Milestone: --- Created attachment 130144 --> https://bugs.kde.org/attachment.cgi?id=130144&action=edit Showing the error and the path it tries to go to SUMMARY If you open a file off of an FTP server/device with MTP that you connected to using Dolphin, if you open another file afterwards it will try to go into the previous file as if it was a folder. STEPS TO REPRODUCE 1. Open any file on an FTP server/device with MTP with File > Open or Ctrl + O 2. Try to open another file with the same dialog OBSERVED RESULT Instead of opening the folder the most recent file was opened from, it tries to open the most recent file as a folder, and give the "/path/to/file/file.txt is a file, but a folder was expected." EXPECTED RESULT After opening a file in the Open dialog or the Ctrl + O shortcut, and then opening another file using the same dialog, it should open the folder where the recently opened file is in SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux, Linux 5.7.8-arch1-1 (available in About System) KDE Plasma Version: 5.19.3 KDE Frameworks Version: 5.72.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION I am not sure if this only happens on FTP servers or MTP devices, it could as well happen for any other file transfer protocol that doesn't get mounted into the filesystem. I thought it happens with things connected through the network like the aforementioned FTP or maybe even WebDav, but it doesn't happen with SSHFS, since it gets actually mounted into the filesystem. And, I'm not sure it happens if you connect to the FTP server/MTP device with another program or with another method -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416312] New: Plasma crashed randomly
https://bugs.kde.org/show_bug.cgi?id=416312 Bug ID: 416312 Summary: Plasma crashed randomly Product: plasmashell Version: 5.17.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: andy3...@protonmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.17.5) Qt Version: 5.14.0 Frameworks Version: 5.66.0 Operating System: Linux 5.4.11-arch1-1 x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: Using Plasma normally. I think I switched virtual desktops - Custom settings of the application: I have the custom Thermal Monitor and the Application title plugin, both got form built-in widget installer I use Kvantum, using theme Sweet I also use glava, if it helps with anything. I keep it open basically non-stop The crash does not seem to be reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff8d049ecc0 (LWP 670))] Thread 16 (Thread 0x7ff8689bb700 (LWP 2004)): #0 0x7ff8d3f6dc45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7ff8d4b2dcc4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7ff8d4b2dda2 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7ff8d689b18b in () at /usr/lib/libQt5Quick.so.5 #4 0x7ff8d689b41b in () at /usr/lib/libQt5Quick.so.5 #5 0x7ff8d4b27fd6 in () at /usr/lib/libQt5Core.so.5 #6 0x7ff8d3f674cf in start_thread () at /usr/lib/libpthread.so.0 #7 0x7ff8d47aa2d3 in clone () at /usr/lib/libc.so.6 Thread 15 (Thread 0x7ff86a7fd700 (LWP 1916)): #0 0x7ff8d479f9ef in poll () at /usr/lib/libc.so.6 #1 0x7ff8d3008120 in () at /usr/lib/libglib-2.0.so.0 #2 0x7ff8d30081f1 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7ff8d4d5acdc in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7ff8d4d0139c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7ff8d4b26e62 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7ff8d4b27fd6 in () at /usr/lib/libQt5Core.so.5 #7 0x7ff8d3f674cf in start_thread () at /usr/lib/libpthread.so.0 #8 0x7ff8d47aa2d3 in clone () at /usr/lib/libc.so.6 Thread 14 (Thread 0x7ff86b7ff700 (LWP 1914)): #0 0x7ff8d479b42c in read () at /usr/lib/libc.so.6 #1 0x7ff8d2fb89f0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7ff8d30069e1 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7ff8d30080c8 in () at /usr/lib/libglib-2.0.so.0 #4 0x7ff8d30081f1 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7ff8d4d5acdc in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7ff8d4d0139c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7ff8d4b26e62 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7ff8d4b27fd6 in () at /usr/lib/libQt5Core.so.5 #9 0x7ff8d3f674cf in start_thread () at /usr/lib/libpthread.so.0 #10 0x7ff8d47aa2d3 in clone () at /usr/lib/libc.so.6 Thread 13 (Thread 0x7ff898ec0700 (LWP 1913)): #0 0x7ff8d479f9ef in poll () at /usr/lib/libc.so.6 #1 0x7ff8d3008120 in () at /usr/lib/libglib-2.0.so.0 #2 0x7ff8d30081f1 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7ff8d4d5acdc in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7ff8d4d0139c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7ff8d4b26e62 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7ff8d4b27fd6 in () at /usr/lib/libQt5Core.so.5 #7 0x7ff8d3f674cf in start_thread () at /usr/lib/libpthread.so.0 #8 0x7ff8d47aa2d3 in clone () at /usr/lib/libc.so.6 Thread 12 (Thread 0x7ff8998c1700 (LWP 1911)): #0 0x7ff8d3f6dc45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7ff8d4b2dcc4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7ff8d4b2dda2 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7ff8d689b18b in () at /usr/lib/libQt5Quick.so.5 #4 0x7ff8d689b41b in () at /usr/lib/libQt5Quick.so.5 #5 0x7ff8d4b27fd6 in () at /usr/lib/libQt5Core.so.5 #6 0x7ff8d3f674cf in start_thread () at /usr/lib/libpthread.so.0 #7 0x7ff8d47aa2d3 in clone () at /usr/lib/libc.so.6 Thread 11 (Thread 0x7ff89a8c2700 (LWP 1311)): #0 0x7ff8d3f6dc45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7ff8d4b2dcc4 in QWaitCondition::wait(QMutex*, QD
