[plasmashell] [Bug 444493] Wallpaper dissappears after restarting my machine
https://bugs.kde.org/show_bug.cgi?id=93 Harry Coin changed: What|Removed |Added CC||hgc...@gmail.com --- Comment #8 from Harry Coin --- This happens to me as well. I have a multimonitor setup. Every reboot it's anyone's bet whether the "Darkest Hour" image will be restored (as set on each monitor), or whether the monitor will be entirely black. Of some interest, when I launch "desktop folder settings -- Plasma" even on the monitors where the image is correct, you'd expect when I choose the current image the apply button would remain greyed out. It does not, it pops active even though the image I chose matched the one on the monitor already. Go figure. I can reset the background on each monitor, and it will remain until the next poweroff/reboot. Then, at least 2 monitors will be black. Which two seems to vary. Latest jammy, no pending updates as of 12/23/22. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427861] Sometimes desktop loses its settings (wallpaper, widgets, icons settings) after re-login
https://bugs.kde.org/show_bug.cgi?id=427861 Harry Coin changed: What|Removed |Added CC||hgc...@gmail.com --- Comment #99 from Harry Coin --- Well, "Me too". Latest Ubuntu LTS, fresh install: custom image wallpaper reverts to default on one to two of 6 attached monitors, and usually not the 'primary' one after screen lock or reboot. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 443398] Spectacle exits without taking screenshot, upon-relaunch is in 'select rectangle' mode.
https://bugs.kde.org/show_bug.cgi?id=443398 --- Comment #2 from Harry Coin --- administrator@ceo1homenx:/tmp$ export $(dbus-launch) administrator@ceo1homenx:/tmp$ spectacle QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-administrator' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-administrator' QDBusConnection: name 'org.kde.kglobalaccel' had owner '' but we thought it was ':1.1' ... dialog appears, hangs after asking for a screenshot ^C administrator@ceo1homenx:/tmp$ spectacle QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-administrator' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-administrator' dialog does not appear ^C Sometimes the dialog appears, sometimes not. From the command line, it always hangs. From the launcher, the second run allows taking a screenshot. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 443398] New: Spectacle exits without taking screenshot, upon-relaunch is in 'select rectangle' mode.
https://bugs.kde.org/show_bug.cgi?id=443398 Bug ID: 443398 Summary: Spectacle exits without taking screenshot, upon-relaunch is in 'select rectangle' mode. Product: Spectacle Version: 20.12.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: hgc...@gmail.com CC: k...@david-redondo.de Target Milestone: --- SUMMARY The spectacle app disappears from the screen as if it was never run just after the 'take a new screenshot' button is pressed, and 'rectangular region' was the mode. Then, when the spectacle app is re-launched, the screen goes into the mode of choosing a region (the app box itself does not appear). After a region is chosen normally, the menu box appears and operations are typical. STEPS TO REPRODUCE 1. Launch the app, specify a rectangular region. Choose take a screenshot 2. See the app disappear as if it was never launched at all. Totally normal appearance. 3. Launch the app again, the screen goes into 'select rectangle' mode and when selected normal spectacle ops continue. OBSERVED RESULT As above. The only difference I can think of is I have a multimonitor setup. EXPECTED RESULT SOFTWARE/OS VERSIONS Latest Ubuntu 'hirsute', all updates applied. Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 413259] Files >=512MB (movies) corrupted during transfer without warning
https://bugs.kde.org/show_bug.cgi?id=413259 Harry Coin changed: What|Removed |Added Version|unspecified |1.3.5 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 413259] New: Files >=512MB (movies) corrupted during transfer without warning
https://bugs.kde.org/show_bug.cgi?id=413259 Bug ID: 413259 Summary: Files >=512MB (movies) corrupted during transfer without warning Product: kdeconnect Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: hgc...@gmail.com Target Milestone: --- SUMMARY Phone videos are silently corrupted during transfer. STEPS TO REPRODUCE 1. Take a phone video >= 512MB. 2. Connect via KDEConnect's android app, open dolphin, surf to DCIM directory, select all, copy. 3. Surf to local directly, paste. 4. Wait. Normal termination reported. OBSERVED RESULT Movie files (larger) correctly match size, dates, names. However, the content is quite wrong. Proven by removing the memory chip from the phone, copying via direct connection, then comparing the files. Latest ubuntu eoan kdeconnect 1.3.5-0ubuntu1 Android kdeconnect version 1.13.2, Samsung galaxy s8 / verizon. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 412834] New: "Cannot refresh cache whilst offline" -- except I'm online.
https://bugs.kde.org/show_bug.cgi?id=412834 Bug ID: 412834 Summary: "Cannot refresh cache whilst offline" -- except I'm online. Product: Discover Version: 5.16.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: hgc...@gmail.com CC: aleix...@kde.org Target Milestone: --- SUMMARY "Cannot refresh cache whilst offline" -- except I'm not offline, obviously since I'm filing this report. STEPS TO REPRODUCE 1. Click the icon indicating updates are available in the task bar 2. Click 'check for updates'. 3. Notice it gives an error message and does nothing of any use. System is the latest Ubuntu 'eoan', though this bug has been around for a long time. My system's network is configured via systemd/networkd as is indicated in /etc/netplan. I don't use the network manager for anything. This bug appears whether the disused network-manager is enabled or disabled in systemd, or is running or not running. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 336043] SFTP: Should be able to browse external SD cards via SFTP too
https://bugs.kde.org/show_bug.cgi?id=336043 --- Comment #96 from Harry Coin --- When will it be out there for android updates to see it? On 3/8/19 11:35 AM, bugzilla_nore...@kde.org wrote: > https://bugs.kde.org/show_bug.cgi?id=336043 > > --- Comment #95 from ham...@laposte.net --- > Awesome ! I confirm, it works ! > Thanks much, we were waiting since a long time to see a fix :) > -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 336043] SFTP: Should be able to browse external SD cards via SFTP too
https://bugs.kde.org/show_bug.cgi?id=336043 --- Comment #88 from Harry Coin --- Confirmed on the s8 . The only failure appears to be listing the root directory of the so card. On March 6, 2019 5:56:20 PM CST, Rafael Linux User wrote: >https://bugs.kde.org/show_bug.cgi?id=336043 > >--- Comment #87 from Rafael Linux User >--- >> I'll just make a test tonight about this theory. > >I test and confirmed that permission to access SD Card are granted for >KDE >Connect in my Galaxy S7, but as we all know, there is no any moment in >which >KDE Connect let user try to access to the SD Card (as I said, that's >the >difference with other apps). >I can confirm too something someone wrote here. Once you access to SD >Card from >Dolphin, if you modify the path and add a existent subfolder, you have >READ >access to that subfolder!! > >Example: >My SD Card path thru KDEConnect is: >/run/user/1000/3511dfbdef1892ed/storage/0411-AFE2/ > >I know that I have a subfolder called "Music", so I put: >/run/user/1000/3511dfbdef1892ed/storage/0411-AFE2/Music >and mysteriously, I have read access to that folder. > >-- >You are receiving this mail because: >You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 401591] New: Dolphin crashed when looking in trash bucket.
https://bugs.kde.org/show_bug.cgi?id=401591 Bug ID: 401591 Summary: Dolphin crashed when looking in trash bucket. Product: dolphin Version: 18.04.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: hgc...@gmail.com CC: elvis.angelac...@kde.org Target Milestone: --- Application: dolphin (18.04.3) Qt Version: 5.11.1 Frameworks Version: 5.50.0 Operating System: Linux 4.18.0-11-generic x86_64 Distribution: Ubuntu 18.10 -- Information about the crash: - What I was doing when the application crashed: Previously I had chosen 'empty trash'. some minutes later, I looked in the bucket to see nothing had been deleted. I chose a folder at random asking it to delete that. Then in crashed. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f17288eb800 (LWP 6168))] Thread 6 (Thread 0x7f170fc45700 (LWP 8744)): #0 __GI___libc_read (fd=22, buf=0x7f170fc44bde, nbytes=10) at ../sysdeps/unix/sysv/linux/read.c:26 #1 0x7f172c7431f1 in pa_read () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-12.2.so #2 0x7f172e36bdbe in pa_mainloop_prepare () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7f172e36c820 in pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7f172e36c8e0 in pa_mainloop_run () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7f172e37a8f9 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7f172c7726f8 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-12.2.so #7 0x7f172e3bd164 in start_thread (arg=) at pthread_create.c:486 #8 0x7f1732297def in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f171cac1700 (LWP 6173)): #0 0x7f173228b6d9 in __GI___poll (fds=0x7f17080049b0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f172d21ae46 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f172d21af6c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f17301c115b in QEventDispatcherGlib::processEvents (this=0x7f1708000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f173016e16b in QEventLoop::exec (this=this@entry=0x7f171cac0da0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #5 0x7f172ffbd0b6 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #6 0x7f172ffc6c87 in QThreadPrivate::start (arg=0x5610f3f822e0) at thread/qthread_unix.cpp:367 #7 0x7f172e3bd164 in start_thread (arg=) at pthread_create.c:486 #8 0x7f1732297def in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f171ee20700 (LWP 6172)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x5610f3dfd028) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x5610f3dfcfd8, cond=0x5610f3dfd000) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x5610f3dfd000, mutex=0x5610f3dfcfd8) at pthread_cond_wait.c:655 #3 0x7f171f5df75b in ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so #4 0x7f171f5df4c7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so #5 0x7f172e3bd164 in start_thread (arg=) at pthread_create.c:486 #6 0x7f1732297def in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f1725cb6700 (LWP 6171)): #0 0x7f173228b6d9 in __GI___poll (fds=0x7f171801b200, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f172d21ae46 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f172d21af6c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f17301c115b in QEventDispatcherGlib::processEvents (this=0x7f1718000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f173016e16b in QEventLoop::exec (this=this@entry=0x7f1725cb5d70, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #5 0x7f172ffbd0b6 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #6 0x7f173047a545 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f172ffc6c87 in QThreadPrivate::start (arg=0x7f17304f4d60) at thread/qthread_unix.cpp:367 #8 0x7f172e3bd164 in start_thread (arg=) at pthread_create.c:486 #9 0x7f1732297def in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f1726e5a700 (LWP 6169)): #0 0x7f173228b6d9 in __GI___poll (fds=0x7f1726e59cb8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1
[kdeconnect] [Bug 336043] SFTP: Should be able to browse external SD cards via SFTP too
https://bugs.kde.org/show_bug.cgi?id=336043 Harry Coin changed: What|Removed |Added CC||hgc...@gmail.com --- Comment #81 from Harry Coin --- Add HTC M8 to the list. user:/run/user/1000/93928376705e8277$ ls -l ls: reading directory '.': Operation not permitted total 0 user:cd /sdcard user:/run/user/1000/93928376705e8277/sdcard$ ls -l total 148 -rw-rw-rw- 1 administrator admin 72245 Aug 19 2017 _deleted.vcf drwxrwxrwx 1 administrator admin 0 Jun 30 2017 Alarms -- You are receiving this mail because: You are watching all bug changes.
