[frameworks-modemmanager-qt] [Bug 346527] plasmashell keeps on crashing after login
https://bugs.kde.org/show_bug.cgi?id=346527 Rick <rick_ree...@yahoo.com> changed: What|Removed |Added CC||rick_ree...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377088] New: Plasmashell crashing
https://bugs.kde.org/show_bug.cgi?id=377088 Bug ID: 377088 Summary: Plasmashell crashing Product: plasmashell Version: master Platform: openSUSE RPMs OS: other Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: rick_ree...@yahoo.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f599099f7c0 (LWP 6648))] Thread 8 (Thread 0x7f58c1191700 (LWP 6685)): #0 0x7f59896a903f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f598a59734b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQt5Core.so.5 #2 0x7f598e4b41cb in ?? () from /usr/lib64/libQt5Quick.so.5 #3 0x7f598e4b4663 in ?? () from /usr/lib64/libQt5Quick.so.5 #4 0x7f598a59632f in ?? () from /usr/lib64/libQt5Core.so.5 #5 0x7f59896a50a4 in start_thread () from /lib64/libpthread.so.0 #6 0x7f5989ea402d in clone () from /lib64/libc.so.6 Thread 7 (Thread 0x7f58d57ef700 (LWP 6673)): #0 0x7f59896a903f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f598a59734b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQt5Core.so.5 #2 0x7f598e4b41cb in ?? () from /usr/lib64/libQt5Quick.so.5 #3 0x7f598e4b4663 in ?? () from /usr/lib64/libQt5Quick.so.5 #4 0x7f598a59632f in ?? () from /usr/lib64/libQt5Core.so.5 #5 0x7f59896a50a4 in start_thread () from /lib64/libpthread.so.0 #6 0x7f5989ea402d in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7f58d6398700 (LWP 6671)): #0 0x7f598a7c8a63 in ?? () from /usr/lib64/libQt5Core.so.5 #1 0x7f59865784ad in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #2 0x7f5986578d80 in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7f5986578f7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7f598a7c8d8b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7f598a76fd53 in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #6 0x7f598a59161a in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #7 0x7f598e441282 in ?? () from /usr/lib64/libQt5Quick.so.5 #8 0x7f598a59632f in ?? () from /usr/lib64/libQt5Core.so.5 #9 0x7f59896a50a4 in start_thread () from /lib64/libpthread.so.0 #10 0x7f5989ea402d in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f595e27b700 (LWP 6669)): #0 0x7f59896a903f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f599007486b in ?? () from /usr/lib64/libQt5Script.so.5 #2 0x7f5990074899 in ?? () from /usr/lib64/libQt5Script.so.5 #3 0x7f59896a50a4 in start_thread () from /lib64/libpthread.so.0 #4 0x7f5989ea402d in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f595fbbd700 (LWP 6668)): #0 0x7f5989e97ccd in read () from /lib64/libc.so.6 #1 0x7f5982015f55 in ?? () from /usr/lib64/tls/libnvidia-tls.so.340.101 #2 0x7f59865b9b60 in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7f5986578999 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #4 0x7f5986578df8 in ?? () from /usr/lib64/libglib-2.0.so.0 #5 0x7f5986578f7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #6 0x7f598a7c8d8b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #7 0x7f598a76fd53 in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #8 0x7f598a59161a in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #9 0x7f598d8a5e18 in ?? () from /usr/lib64/libQt5Qml.so.5 #10 0x7f598a59632f in ?? () from /usr/lib64/libQt5Core.so.5 #11 0x7f59896a50a4 in start_thread () from /lib64/libpthread.so.0 #12 0x7f5989ea402d in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f59654c4700 (LWP 6667)): #0 0x7f598657858b in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #1 0x7f5986578d80 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f5986578f7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f598a7c8d8b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7f598a76fd53 in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7f598a59161a in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7f598d8a5e18 in ?? () from /usr/lib64/libQt5Qml.so.5 #7 0x7f598a59632f in ?? () from /usr/lib64/libQt5Core.so.5 #8 0x7f59896a50a4 in start_thread () from /lib64/libpthread.so.0 #9 0x7f5989ea402d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f59717b0700 (LWP )): #0 0x7f59865761c9 in ?? () from /usr/lib64/libglib-2.0.so.0
[digikam] [Bug 372684] No thumbnail shows for some files
https://bugs.kde.org/show_bug.cgi?id=372684 --- Comment #15 from Rick <r...@hallocks.us> --- Yes, Color management is enabled. (tried turning it off no difference) here are two pics one shows the thumbnail, one doesn't. The one that shows is same pic, just re-saved smaller. ThumbnailShows.jpg <http:///home/rick/Dropbox/Public/pics/ThumbnailShows.jpg> ThumbnailNoShows.jpg <https://dl.dropboxusercontent.com/u/3343817/pics/ThumbnailNoShows.jpg> On Mon, Nov 21, 2016 at 10:43 AM, <bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=372684 > > --- Comment #14 from caulier.gil...@gmail.com --- > Color Management : look in Setup Dialog, into CM panel. > > To share samples, use a cloud service from Internet > > Gilles Caulier > > -- > You are receiving this mail because: > You reported the bug. > -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372684] No thumbnail shows for some files
https://bugs.kde.org/show_bug.cgi?id=372684 --- Comment #23 from Rick <r...@hallocks.us> --- That makes them show up! :) On Tue, Nov 22, 2016 at 2:50 PM, Maik Qualmann <bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=372684 > > --- Comment #22 from Maik Qualmann <metzping...@gmail.com> --- > Please enable this option for testing: Settings->Image > Editor->Versioning->Always show original images > > Maik > > -- > You are receiving this mail because: > You reported the bug. > -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372684] No thumbnail shows for some files
https://bugs.kde.org/show_bug.cgi?id=372684 --- Comment #24 from Rick <r...@hallocks.us> --- Now anything else I can do to help? On Tue, Nov 22, 2016 at 7:17 PM, Rick Hallock <r...@hallocks.us> wrote: > That makes them show up! :) > > > On Tue, Nov 22, 2016 at 2:50 PM, Maik Qualmann <bugzilla_nore...@kde.org> > wrote: > >> https://bugs.kde.org/show_bug.cgi?id=372684 >> >> --- Comment #22 from Maik Qualmann <metzping...@gmail.com> --- >> Please enable this option for testing: Settings->Image >> Editor->Versioning->Always show original images >> >> Maik >> >> -- >> You are receiving this mail because: >> You reported the bug. >> > > > > -- > > Thanks > Rick > -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372684] No thumbnail shows for some files
https://bugs.kde.org/show_bug.cgi?id=372684 --- Comment #17 from Rick <r...@hallocks.us> --- I need the x86-64 appimage On Mon, Nov 21, 2016 at 9:38 PM, <bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=372684 > > --- Comment #16 from caulier.gil...@gmail.com --- > Rick > > No problem to show your dog picture with current digiKam 5.4.0 AppImage > bundle. > > Just to be sure, Crete a new account on your computer, download last > AppImage > (just updated on GDrive > https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM), and > start > it. Create a new empty collection and settings, and import your suspected > pictures. Look if all is fine. > > Gilles Caulier > > -- > You are receiving this mail because: > You reported the bug. > -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372684] No thumbnail shows for some files
https://bugs.kde.org/show_bug.cgi?id=372684 --- Comment #19 from Rick <r...@hallocks.us> --- I used a different Ubuntu user, ran the digikam-5.4.0-01-x86-64.appimage, went through the install questions, created a new album, copied the two pics into the folder. and only one pic shows up in the thumbnail view. (off to work now) On Tue, Nov 22, 2016 at 6:17 AM, <bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=372684 > > --- Comment #18 from caulier.gil...@gmail.com --- > the 64 bits AppImage is in the shared folder at this URL: > > https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM > > Gilles Caulier > > -- > You are receiving this mail because: > You reported the bug. > -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372684] No thumbnail shows for some files
https://bugs.kde.org/show_bug.cgi?id=372684 --- Comment #21 from Rick <r...@hallocks.us> --- It looks like I didn't make the link right for the ThumbnailShows <https://dl.dropboxusercontent.com/u/3343817/pics/ThumbnailShows.jpg> but the ThumbnailNoShows <https://dl.dropboxusercontent.com/u/3343817/pics/ThumbnailNoShows.jpg> link you sent back is right. What doesn't make sense is, if you got the ThumbnailNoShows, that is the one that the thumbnail does not show for me. On Tue, Nov 22, 2016 at 8:26 AM, <bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=372684 > > --- Comment #20 from caulier.gil...@gmail.com --- > 2 pictures ? > > I only get one picture from the cloud from you. Where is the second one ? > > Look links given in comment #15 : > > ThumbnailShows.jpg > <http:///home/rick/Dropbox/Public/pics/ThumbnailShows.jpg> > > ThumbnailNoShows.jpg > <https://dl.dropboxusercontent.com/u/3343817/pics/ThumbnailNoShows.jpg> > > Gilles Caulier > > -- > You are receiving this mail because: > You reported the bug. > -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372684] New: No thumbnail shows for files larger than 2MB
https://bugs.kde.org/show_bug.cgi?id=372684 Bug ID: 372684 Summary: No thumbnail shows for files larger than 2MB Product: digikam Version: 5.3.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Thumbnails Assignee: digikam-de...@kde.org Reporter: r...@hallocks.us Target Milestone: --- I just installed DigiKam 5.3.0 on Ubuntu 16.10. and copied my folders from my old computer (let DigiKam make a new db). Some pics don't show up in the the thumbnail view. The count is correct in the albums tree, but only some or none show up in the thumbnail view, they all show up in the Table view. A quick sampling suggests any jpg files > 2MB are not showing up. "Thumbnail generation fails on large files" says to change "kcontrol->kde components->file manager->Previes & Metadata (tab)->Maximum file size", but I don't have that on Ubuntu! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372684] No thumbnail shows for some files
https://bugs.kde.org/show_bug.cgi?id=372684 --- Comment #13 from Rick <r...@hallocks.us> --- Not sure of color management. I can share a couple sample pics when I get home tonight. (8-9 hours from now) 1 at a time, to stay under 4meg size limit? On Sun, Nov 20, 2016 at 11:58 PM, <bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=372684 > > --- Comment #12 from caulier.gil...@gmail.com --- > In your trace no error appear. So thumbnails are extracted as expected. The > problem is not here... > > Do you have color management enabled ? > > Can you share some suspect files to try to reproduce the problem here ? > > Gilles Caulier > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372684] No thumbnail shows for files larger than 2MB
https://bugs.kde.org/show_bug.cgi?id=372684 --- Comment #3 from Rick <r...@hallocks.us> --- No, I have not been able to get thumbnails to show up at all in the the thumbnail view for those files. Thumbnails to show up on table view. On Sun, Nov 20, 2016 at 5:32 AM, Maik Qualmann <bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=372684 > > Maik Qualmann <metzping...@gmail.com> changed: > >What|Removed |Added > > > CC||metzping...@gmail.com > > --- Comment #1 from Maik Qualmann <metzping...@gmail.com> --- > Are thumbnails displayed after reloading (F5)? > > Maik > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372684] No thumbnail shows for files larger than 2MB
https://bugs.kde.org/show_bug.cgi?id=372684 --- Comment #5 from Rick <r...@hallocks.us> --- I still get the same results using the digikam-5.4.0-01-x86-64 appimage. I never used an appimage before! that was pretty simple, pretty nice and I like it! Also it is not a 2MB size. I just was looking some more and there are larger files with thumbs showing up. It was just that the first dir I checked had only 2 out of 13 that showed and those 2 were less that 2MB, the next dir I checked had like 103 and only showed 15 and when I sorted it by size, there were 15 files less than 2MB. Then I tried to make one that show and one that doesn't smaller, so I could put them in my report question, but they both show up after converting them to a smaller size using the batch resize to make them tiny. It must be something in the header. The F5 does show doing thumbs but they still don't show up. Maybe related... in the thumbs view, any pics i see (have thumbs) the EXIF info changes when I click on them, in the table view it's flaky, I click on a different album in the tree, then click back and click a pic, then I can cursor up and down and exif data shows and changes, but as soon as I click a pic, exif data goes away, keyboard cursor up and down does not bring it back. On Sun, Nov 20, 2016 at 7:41 AM, <bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=372684 > > caulier.gil...@gmail.com changed: > >What|Removed |Added > > > CC||caulier.gil...@gmail.com > > --- Comment #2 from caulier.gil...@gmail.com --- > >"Thumbnail generation fails on large files" says to change "kcontrol->kde > >components->file manager->Previes & Metadata (tab)->Maximum file size" > > digiKam is fully independent of KDE here. In fact digiKam become more and > more > KDE free since 5.x release, especially about the settings. > > Can you imagine that we can release DK without to try to see if JPEG fiel > size > > 2MB are supported well in thumbnail view. It's ridiculous. > > So, i suspect a huge packaging problem here. Please try with digiKam > AppImage > bundle instead Kubuntu package. > > https://drive.google.com/open?id=0BzeiVr-byqt5Y0tIRWVWelRJenM > > Gilles Caulier > > > > > Gilles Caulier > > -- > You are receiving this mail because: > You reported the bug. > -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372684] No thumbnail shows for files larger than 2MB
https://bugs.kde.org/show_bug.cgi?id=372684
--- Comment #10 from Rick <r...@hallocks.us> ---
I think this must be the relevant info, it is from an F5 on a directory
where 2 out of 11 pics show up in the thumbnail view.
Or ah well I thought I saw some errors in there and I don't see them now!
either way this is what comes out when I do an f5
digikam.general: Using 8 CPU core to run threads
digikam.general: Action Thread run 11 new jobs
digikam.general: scan mode: ScheduleCollectionScan ::
("/media/rick/Pictures/years/2016/2016-08-17 Big Girl puppy/")
digikam.dimg: "/media/rick/Pictures/years/2016/2016-08-17 Big Girl
puppy/2016_08_17_18_31_00.jpg" : JPEG file identified
digikam.dimg: "/media/rick/Pictures/years/2016/2016-08-17 Big Girl
puppy/2016_08_17_18_32_00-2.jpg" : JPEG file identified
digikam.dimg: "/media/rick/Pictures/years/2016/2016-08-17 Big Girl
puppy/2016_08_17_18_32_00-1_v1.jpg" : JPEG file identified
digikam.dimg: "/media/rick/Pictures/years/2016/2016-08-17 Big Girl
puppy/2016_08_17_18_32_00-3.jpg" : JPEG file identified
digikam.dimg: "/media/rick/Pictures/years/2016/2016-08-17 Big Girl
puppy/2016_08_17_18_31_00-1.jpg" : JPEG file identified
digikam.dimg: "/media/rick/Pictures/years/2016/2016-08-17 Big Girl
puppy/2016_08_17_18_30_00.jpg" : JPEG file identified
digikam.dimg: "/media/rick/Pictures/years/2016/2016-08-17 Big Girl
puppy/2016_08_17_18_29_00.jpg" : JPEG file identified
digikam.dimg: "/media/rick/Pictures/years/2016/2016-08-17 Big Girl
puppy/2016_08_17_18_33_00-1.jpg" : JPEG file identified
digikam.metaengine: Orientation => Exif.Image.Orientation => 1
digikam.metaengine: Orientation => Exif.Image.Orientation => 1
digikam.metaengine: Orientation => Exif.Image.Orientation => 1
digikam.general: Event is dispatched to desktop notifier through DBUS
digikam.dimg: "/media/rick/Pictures/years/2016/2016-08-17 Big Girl
puppy/2016_08_17_18_31_00-3_v1.jpg" : JPEG file identified
digikam.geoiface:
digikam.general: Using 8 CPU core to run threads
digikam.general: One job is done
digikam.metaengine: Orientation => Exif.Image.Orientation => 1
digikam.general: Action Thread run 1 new jobs
digikam.metaengine: Orientation => Exif.Image.Orientation => 1
digikam.general: One job is done
digikam.dimg: "/media/rick/Pictures/years/2016/2016-08-17 Big Girl
puppy/2016_08_17_18_29_00-2.jpg" : JPEG file identified
digikam.metaengine: Orientation => Exif.Image.Orientation => 1
digikam.general: One job is done
digikam.dimg: "/media/rick/Pictures/years/2016/2016-08-17 Big Girl
puppy/2016_08_17_18_33_00.jpg" : JPEG file identified
digikam.metaengine: Orientation => Exif.Image.Orientation => 1
digikam.geoiface:
digikam.metaengine: Orientation => Exif.Image.Orientation => 1
digikam.general: One job is done
digikam.general: Cancel Main Thread
digikam.general: One job is done
digikam.dimg: "/media/rick/Pictures/years/2016/2016-08-17 Big Girl
puppy/2016_08_17_18_31_00-3_v1.jpg" : JPEG file identified
digikam.general: One job is done
digikam.general: One job is done
digikam.general: One job is done
digikam.dimg: "/media/rick/Pictures/years/2016/2016-08-17 Big Girl
puppy/2016_08_17_18_29_00-2.jpg" : JPEG file identified
digikam.metaengine: Orientation => Exif.Image.Orientation => 1
digikam.general: One job is done
digikam.metaengine: Orientation => Exif.Image.Orientation => 1
digikam.general: One job is done
digikam.metaengine: Orientation => Exif.Image.Orientation => 1
digikam.metaengine: Orientation => Exif.Image.Orientation => 1
digikam.metaengine: Orientation => Exif.Image.Orientation => 1
digikam.general: One job is done
digikam.dimg: "/media/rick/Pictures/years/2016/2016-08-17 Big Girl
puppy/2016_08_17_18_33_00.jpg" : JPEG file identified
digikam.general: One job is done
digikam.general: List of Pending Jobs is empty
digikam.general: Event is dispatched to desktop notifier through DBUS
digikam.general: Cancel Main Thread
digikam.general: Cancel Main Thread
digikam.metaengine: Orientation => Exif.Image.Orientation => 1
On Sun, Nov 20, 2016 at 4:55 PM, <bugzilla_nore...@kde.org> wrote:
> https://bugs.kde.org/show_bug.cgi?id=372684
>
> --- Comment #9 from caulier.gil...@gmail.com ---
> open a terminal, go to directory where AppImage file is (use "cd" CLI
> command),
> and to run it just use "./file_name"
>
> Gilles Caulier
>
> --
> You are receiving this mail because:
> You reported the bug.
>
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 372684] No thumbnail shows for files larger than 2MB
https://bugs.kde.org/show_bug.cgi?id=372684 --- Comment #6 from Rick <r...@hallocks.us> --- Everything always shows up in the tableview, (except sometimes EXIF info) but many pics do not show up in the thumbnails view. On Sun, Nov 20, 2016 at 4:02 PM, <bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=372684 > > --- Comment #4 from caulier.gil...@gmail.com --- > Rick, > > I'm not sure to understand your previous comment. > > Do mean that thumbnail are show properly in icon-view and not in > table-view, or > the inverse ? > > Gilles Caulier > > -- > You are receiving this mail because: > You reported the bug. > -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372684] No thumbnail shows for files larger than 2MB
https://bugs.kde.org/show_bug.cgi?id=372684
--- Comment #11 from Rick <r...@hallocks.us> ---
attached is the complete output, from startup. started up in in thumbnail
view of the album with 11 pics, 2 showing, clicked on the table view where
all 11 pics show up, then an F5
On Sun, Nov 20, 2016 at 5:13 PM, Rick Hallock <r...@hallocks.us> wrote:
> I think this must be the relevant info, it is from an F5 on a directory
> where 2 out of 11 pics show up in the thumbnail view.
> Or ah well I thought I saw some errors in there and I don't see them now!
> either way this is what comes out when I do an f5
>
> digikam.general: Using 8 CPU core to run threads
> digikam.general: Action Thread run 11 new jobs
> digikam.general: scan mode: ScheduleCollectionScan ::
> ("/media/rick/Pictures/years/2016/2016-08-17 Big Girl puppy/")
> digikam.dimg: "/media/rick/Pictures/years/2016/2016-08-17 Big Girl
> puppy/2016_08_17_18_31_00.jpg" : JPEG file identified
> digikam.dimg: "/media/rick/Pictures/years/2016/2016-08-17 Big Girl
> puppy/2016_08_17_18_32_00-2.jpg" : JPEG file identified
> digikam.dimg: "/media/rick/Pictures/years/2016/2016-08-17 Big Girl
> puppy/2016_08_17_18_32_00-1_v1.jpg" : JPEG file identified
> digikam.dimg: "/media/rick/Pictures/years/2016/2016-08-17 Big Girl
> puppy/2016_08_17_18_32_00-3.jpg" : JPEG file identified
> digikam.dimg: "/media/rick/Pictures/years/2016/2016-08-17 Big Girl
> puppy/2016_08_17_18_31_00-1.jpg" : JPEG file identified
> digikam.dimg: "/media/rick/Pictures/years/2016/2016-08-17 Big Girl
> puppy/2016_08_17_18_30_00.jpg" : JPEG file identified
> digikam.dimg: "/media/rick/Pictures/years/2016/2016-08-17 Big Girl
> puppy/2016_08_17_18_29_00.jpg" : JPEG file identified
> digikam.dimg: "/media/rick/Pictures/years/2016/2016-08-17 Big Girl
> puppy/2016_08_17_18_33_00-1.jpg" : JPEG file identified
> digikam.metaengine: Orientation => Exif.Image.Orientation => 1
> digikam.metaengine: Orientation => Exif.Image.Orientation => 1
> digikam.metaengine: Orientation => Exif.Image.Orientation => 1
> digikam.general: Event is dispatched to desktop notifier through DBUS
> digikam.dimg: "/media/rick/Pictures/years/2016/2016-08-17 Big Girl
> puppy/2016_08_17_18_31_00-3_v1.jpg" : JPEG file identified
> digikam.geoiface:
> digikam.general: Using 8 CPU core to run threads
> digikam.general: One job is done
> digikam.metaengine: Orientation => Exif.Image.Orientation => 1
> digikam.general: Action Thread run 1 new jobs
> digikam.metaengine: Orientation => Exif.Image.Orientation => 1
> digikam.general: One job is done
> digikam.dimg: "/media/rick/Pictures/years/2016/2016-08-17 Big Girl
> puppy/2016_08_17_18_29_00-2.jpg" : JPEG file identified
> digikam.metaengine: Orientation => Exif.Image.Orientation => 1
> digikam.general: One job is done
> digikam.dimg: "/media/rick/Pictures/years/2016/2016-08-17 Big Girl
> puppy/2016_08_17_18_33_00.jpg" : JPEG file identified
> digikam.metaengine: Orientation => Exif.Image.Orientation => 1
> digikam.geoiface:
> digikam.metaengine: Orientation => Exif.Image.Orientation => 1
> digikam.general: One job is done
> digikam.general: Cancel Main Thread
> digikam.general: One job is done
> digikam.dimg: "/media/rick/Pictures/years/2016/2016-08-17 Big Girl
> puppy/2016_08_17_18_31_00-3_v1.jpg" : JPEG file identified
> digikam.general: One job is done
> digikam.general: One job is done
> digikam.general: One job is done
> digikam.dimg: "/media/rick/Pictures/years/2016/2016-08-17 Big Girl
> puppy/2016_08_17_18_29_00-2.jpg" : JPEG file identified
> digikam.metaengine: Orientation => Exif.Image.Orientation => 1
> digikam.general: One job is done
> digikam.metaengine: Orientation => Exif.Image.Orientation => 1
> digikam.general: One job is done
> digikam.metaengine: Orientation => Exif.Image.Orientation => 1
> digikam.metaengine: Orientation => Exif.Image.Orientation => 1
> digikam.metaengine: Orientation => Exif.Image.Orientation => 1
> digikam.general: One job is done
> digikam.dimg: "/media/rick/Pictures/years/2016/2016-08-17 Big Girl
> puppy/2016_08_17_18_33_00.jpg" : JPEG file identified
> digikam.general: One job is done
> digikam.general: List of Pending Jobs is empty
> digikam.general: Event is dispatched to desktop notifier through DBUS
> digikam.general: Cancel Main Thread
> digikam.general: Cancel Main Thread
> digikam.metaengine: Orientation => Exif.Image.Orientation => 1
>
>
> On Sun, Nov 20, 2016 at 4:55 PM, <bugzilla_nore...@kde.org> wrote:
>
>> https://bugs.kde.org/show_bug.cgi?id=372684
>>
>> --- Comment #9 from caulier.gil...@gmail.com ---
>> open a terminal, go to directory where AppImage file is (use "cd" CLI
>> command),
>> and to run it just use "./file_name"
>>
>> Gilles Caulier
>>
>> --
>> You are receiving this mail because:
>> You reported the bug.
>>
>
>
>
> --
>
> Thanks
> Rick
>
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 372684] No thumbnail shows for files larger than 2MB
https://bugs.kde.org/show_bug.cgi?id=372684 --- Comment #8 from Rick <r...@hallocks.us> --- i don't know how to run an appimage from terminal. I just clicked it in nautilus On Sun, Nov 20, 2016 at 4:41 PM, <bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=372684 > > --- Comment #7 from caulier.gil...@gmail.com --- > Can you give the full trace of debug statements printed in the console > when you > run AppImage, especially when album contents must be show in icon view ? > > Gilles Caulier > > -- > You are receiving this mail because: > You reported the bug. > -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372684] No thumbnail shows for some files
https://bugs.kde.org/show_bug.cgi?id=372684 Rick <r...@hallocks.us> changed: What|Removed |Added Summary|No thumbnail shows for |No thumbnail shows for some |files larger than 2MB |files -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 381134] New: The equalizer is not working
https://bugs.kde.org/show_bug.cgi?id=381134 Bug ID: 381134 Summary: The equalizer is not working Product: amarok Version: 2.8.0 Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Tools/Equalizer Assignee: amarok-bugs-d...@kde.org Reporter: nicuju...@lucyu.com Target Milestone: 2.9 Created attachment 106062 --> https://bugs.kde.org/attachment.cgi?id=106062=edit Here is a screen shot which shows that the equalizer is not working In the application Amarock the Equalizer is not working with any songs even its in my home/music directory. Need to fix this minor issue . No modes of equalizer is working. I am using Mint(ubuntu) 18.1 on i3 with 8Gigs of ram -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 387211] Discover needs notification for required reboots
https://bugs.kde.org/show_bug.cgi?id=387211 --- Comment #2 from Rick <rick0...@gmail.com> --- No I didn't. I didn't see anything on my wife's PC either. On Wed, Nov 22, 2017 at 5:13 PM, Nate Graham <bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=387211 > > Nate Graham <pointedst...@zoho.com> changed: > >What|Removed |Added > > > CC||pointedst...@zoho.com > Resolution|--- |WAITINGFORINFO > Status|UNCONFIRMED |NEEDSINFO > > --- Comment #1 from Nate Graham <pointedst...@zoho.com> --- > Where aren't you seeing notifications? On Neon and Kubuntu, I get them. > There's > a little pop-up in the corner, and then there's a little rotating arrow > icon in > the system tray until you reboot. You don't see those? > > -- > You are receiving this mail because: > You reported the bug. > -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 387211] New: Discover needs notification for required reboots
https://bugs.kde.org/show_bug.cgi?id=387211 Bug ID: 387211 Summary: Discover needs notification for required reboots Product: Discover Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Updater Assignee: aleix...@kde.org Reporter: rick0...@gmail.com Target Milestone: --- Discover does not notify the user that a reboot is required to implement certain updates. Kernel and some other system updates require reboot. The developers should determine which updates require reboot and notify the user. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 398213] No sound on Linux Mint
https://bugs.kde.org/show_bug.cgi?id=398213 Rick changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393027] New: Plasma crashed when I clicked on an orphan icon from another distro (distro hopping)
https://bugs.kde.org/show_bug.cgi?id=393027 Bug ID: 393027 Summary: Plasma crashed when I clicked on an orphan icon from another distro (distro hopping) Product: plasmashell Version: 5.12.4 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: rick.g...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.12.4) Qt Version: 5.10.0 Frameworks Version: 5.44.0 Operating System: Linux 4.13.0-38-generic x86_64 Distribution: KDE neon User Edition 5.12 -- Information about the crash: - What I was doing when the application crashed: On a freshly-installed KDE Neon, I tried to click on a quicklaunch icon (quick launcher applet) that pointed to an application I hadn't installed on this distro yet (I had Linux Mint on my other partition, which had an earlier version of KDE plasma installed - so it had my quicklaunch icons there, except Clementine which I hadn't installed on this partition). But I had JUST installed said application, even though the icon hadn't refreshed after I finished installing. So I think I right-clicked to see if the icon would refresh, or maybe I moved the mouse a little and resulted in a drag, I'm not sure. But this was after I clicked the icon and the application began loading. Plasma crashed, and suddenly the application loaded before Plasma restarted. -- Backtrace: Application: Plasma (plasmashell), signal: Bus error Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f973c16a8c0 (LWP 2129))] Thread 23 (Thread 0x7f9630ff6700 (LWP 2350)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f9735e6c67b in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x610cdd0) at thread/qwaitcondition_unix.cpp:143 #2 QWaitCondition::wait (this=, mutex=0x60a3630, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #3 0x7f96517f078f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #4 0x7f96517f4868 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #5 0x7f96517ef9ed in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7f96517f48c2 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7f96517ef9ed in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7f96517f23e0 in ThreadWeaver::Thread::run() () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7f9735e6b6eb in QThreadPrivate::start (arg=0x7f9628002f90) at thread/qthread_unix.cpp:376 #10 0x7f9734cf46ba in start_thread (arg=0x7f9630ff6700) at pthread_create.c:333 #11 0x7f973576c41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 22 (Thread 0x7f96317f7700 (LWP 2349)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f9735e6c67b in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x610cdd0) at thread/qwaitcondition_unix.cpp:143 #2 QWaitCondition::wait (this=, mutex=0x60a3630, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #3 0x7f96517f078f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #4 0x7f96517f4868 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #5 0x7f96517ef9ed in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7f96517f23e0 in ThreadWeaver::Thread::run() () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7f9735e6b6eb in QThreadPrivate::start (arg=0x7f9620002d90) at thread/qthread_unix.cpp:376 #8 0x7f9734cf46ba in start_thread (arg=0x7f96317f7700) at pthread_create.c:333 #9 0x7f973576c41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 21 (Thread 0x7f9631ff8700 (LWP 2348)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f9735e6c67b in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x610cdd0) at thread/qwaitcondition_unix.cpp:143 #2 QWaitCondition::wait (this=, mutex=0x60a3630, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #3 0x7f96517f078f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from
[kdenlive] [Bug 398213] New: No sound on Linux Mint
https://bugs.kde.org/show_bug.cgi?id=398213 Bug ID: 398213 Summary: No sound on Linux Mint Product: kdenlive Version: 18.04.1 Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: r...@rickmacgillis.com Target Milestone: --- I've created an MP4 4K video and it has sound. However, I muted the sound from the video, and used the MP3 from Audacity that was recorded with a quality microphone. (Blue Yeti) The MP3 works just fine on its own, as does the MP4. When I add them both to Kdenlive, mute the video's embedded audio while keeping the MP3's audio working, I can hear it just fine. Next, I save the project in Kdenlive's format, and then I reopen the file. No audio plays from the same MP3. If I unmute the audio embedded in the video, it plays the embedded audio without issue. Regardless of if I created the project from scratch in the same session, or if I saved and reopened it, Kdenlive does not save the sound to the exported MP4. Just an FYI, I saw the multitude of issues with libmlt6, and I'm using the latest version. apt-get: `libmlt6 is already the newest version (6.6.0-1build1).` I installed `http://ppa.launchpad.net/kdenlive/kdenlive-stable/ubuntu bionic InRelease` to grab Kdenlive, and before that, I used the built-in repos that came with Linux Mint to install Kdenlive 17.x which I upgraded originally hoping it would fix the problem. FYI, I'm using the Cinnamon desktop environment in case it matters. Let me know if you need any other info to help fix this issue. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 398213] No sound on Linux Mint
https://bugs.kde.org/show_bug.cgi?id=398213 Rick changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 398213] No sound on Linux Mint
https://bugs.kde.org/show_bug.cgi?id=398213 Rick changed: What|Removed |Added Status|CONFIRMED |UNCONFIRMED Ever confirmed|1 |0 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 398213] No sound on Linux Mint
https://bugs.kde.org/show_bug.cgi?id=398213 --- Comment #2 from Rick --- You're a life saver! I'm the gummy worm that now has working software. Thanks for your help. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405715] kicker loses binding
https://bugs.kde.org/show_bug.cgi?id=405715 Rick changed: What|Removed |Added CC||rick.avloni...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405715] New: kicker loses binding
https://bugs.kde.org/show_bug.cgi?id=405715 Bug ID: 405715 Summary: kicker loses binding Product: plasmashell Version: 5.15.2 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Menu (Kicker) Assignee: h...@kde.org Reporter: rick.avloni...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY On a laptop (HP probook 450 G5), after the lid closes and is reopened, kicker loses its binding to the meta key. The other meta key shortcuts still work and alt+F1 works. STEPS TO REPRODUCE 1. Close the lid of the laptop. The power settings are set (on power, battery and low battery) to "do nothing" 2. Upon opening the lid, the meta binding to kicker is lost. This happens 80% of the time. The alt+F1 binding still works. The other meta+XYZ bindings still work (I have meta+T configured to toggle touchpad and it always works.) 3. Also, before I installed synaptics, the touchpad would lose its tapping ability. This has abated since I installed synaptics. 4. Logging out remedies the problem. 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.
[plasmashell] [Bug 391322] Super (Meta) Key stops working
https://bugs.kde.org/show_bug.cgi?id=391322 --- Comment #10 from Rick --- (In reply to Christoph Feck from comment #6) > If this happens again, please issue this dbus command: > > qdbus org.kde.plasmashell /PlasmaShell > org.kde.PlasmaShell.activateLauncherMenu > > If it shows the application launcher, the bug is in kwin. If it does not, > the bug is in plasmashell. The bug is in plasma shell. I've opened the lid of my laptop and the kicker bug was there. I ran the command in terminal and kicker started up. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391322] Super (Meta) Key stops working
https://bugs.kde.org/show_bug.cgi?id=391322 --- Comment #11 from Rick --- um, I meant the bug must be in kwin -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407361] Notifications in the history lack interactive features that are in their pop-ups (buttons, draggable images, etc)
https://bugs.kde.org/show_bug.cgi?id=407361 --- Comment #6 from Rick --- In case it's helpful info: I've noticed that when you get the popup notification that is visible for 5 seconds: If I click the notification tray during that 5 seconds while it's visible, there is a button under the notification that says 'Activate'. If you click the 'Activate' button, it will take you to the correct link. If you wait for the popup to go away, the activate button will no longer be available, and you will not get a relevant link. I have also noticed a minor difference between Chromium and Firefox: When I subscribe to the push notifications in Chromium, I do get a link to the root of the website. In Firefox, there is no link at all. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407361] Notifications in the history lack interactive features that are in their pop-ups (buttons, draggable images, etc)
https://bugs.kde.org/show_bug.cgi?id=407361 Rick changed: What|Removed |Added CC||rick...@gmail.com --- Comment #5 from Rick --- I'm having this issue on Manjaro 18.04. Are there any workarounds to keep notification history with a working link? Is this fixed on Neon or other releases? -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 416830] Elisa crashes on start Kubuntu 20.04
https://bugs.kde.org/show_bug.cgi?id=416830 Rick changed: What|Removed |Added CC||rickjcar...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 416830] Elisa crashes on start Kubuntu 20.04
https://bugs.kde.org/show_bug.cgi?id=416830 Rick changed: What|Removed |Added CC|rickjcar...@gmail.com | -- 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 #32 from Rick --- The binding always breaks after first suspend. I pressed *alt+shift+f12* and the screen blinked. I then closed the lid and the binding broke. I restored with *kwin_x11 --replace & disown*. I restarted my machine for the next test because after I restore, I can't reliably reproduce the problem by closing the lid - it becomes random. But when I freshly login and close the lid I can break it 100% of the time. When I logged in after the restart, I entered *sudo udevadm trigger -s input* into the console It didn't trigger the meta key binding breakage. I then closed my laptop lid and I triggered the meta key binding breakage. On Wed, Nov 25, 2020 at 11:14 PM David Edmundson wrote: > https://bugs.kde.org/show_bug.cgi?id=391322 > > --- Comment #31 from David Edmundson --- > Could you also see if: > > sudo udevadm trigger -s input > > reliably triggers it? > > -- > You are receiving this mail because: > You are on the CC list for the bug. > You voted for the bug. -- 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 #35 from Rick --- Created attachment 133912 --> https://bugs.kde.org/attachment.cgi?id=133912=edit logs for xkbcli interactive-x11 -- 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 #36 from Rick --- All that typing gone when I attached that file! On a fresh restart, I ran 'dbus-monitor' from the terminal and streamed the output to kate. I grepped for 'member=activateLauncherMenu'. There were no hits. I launched kicker successfully and there was 1 hit. I closed the lid and activated the bug. I grepped again but got no new hits. The hit total stands at 1. I restarted my machine because I can 100% reproduce the bug on the first time. I setup my gdb and then ran 'xkbcli interactive-x11'. I pressed meta and then clicked on the desktop to close the menu. Then I launched kicker again, and with the menu open, I closed the lid. The bug activated. I restarted my pc to post the results and the log file (kwin.dbg). I'm happy to assist further. -- 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 #40 from Rick --- (In reply to David Edmundson from comment #38) > hypothetically are you able to build your own kwin if I provided some > patches? Yes I could. I'd like to help solve this bug. -- 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 #39 from Rick --- (In reply to David Edmundson from comment #37) > That attached file doesn't look like the output of "xkbcli interactive-x11" > it looks like a stack trace. Is it the right file? Apologies. Here is the output: keysyms [ Super_L ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layo
[kwin] [Bug 391322] Meta key randomly stops opening Plasma launcher menu
https://bugs.kde.org/show_bug.cgi?id=391322 --- Comment #29 from Rick --- KWin stops working when I close my laptop lid. My power options are set to "do nothing". When I open the lid, the meta key has lost its binding. I started my pc and opened a terninal. I entered echo 0 | sudo tee /proc/sys/kernel/yama/ptrace_scope gdb -pid $(pidof kwin_x11) -batch -ex "set logging file kwin.gdb" -ex "set logging on" -ex "continue" -ex "thread apply all backtrace" -ex "quit" and closed the lid. The meta key lost its binding. Then I opened another terminal and entered win_x11 --replace & disown to restore functionality. Below is the stacktrace from kwin.gdb. I hope it helps. Thread 1 "kwin_x11" received signal SIGINT, Interrupt. 0x7fe0da57156e in ppoll () from /usr/lib/libc.so.6 Thread 10 (Thread 0x7fe0ce58e640 (LWP 51981) "QSGRenderThread"): #0 0x7fe0d9ddc6a2 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fe0da9220d4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7fe0d96d52fb in () at /usr/lib/libQt5Quick.so.5 #3 0x7fe0d96d789b in () at /usr/lib/libQt5Quick.so.5 #4 0x7fe0da91be8f in () at /usr/lib/libQt5Core.so.5 #5 0x7fe0d9dd63e9 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fe0da57c293 in clone () at /usr/lib/libc.so.6 Thread 9 (Thread 0x7fe0cc850640 (LWP 34522) "kwin_x11"): #0 0x7fe0d9ddc6a2 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fe0da26afee in () at /usr/lib/libQt5Script.so.5 #2 0x7fe0da26b019 in () at /usr/lib/libQt5Script.so.5 #3 0x7fe0d9dd63e9 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fe0da57c293 in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7fe0bcbf8640 (LWP 34477) "kwin_x1:disk$3"): #0 0x7fe0d9ddc6a2 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fe0beced8dc in () at /usr/lib/dri/iris_dri.so #2 0x7fe0beced7d8 in () at /usr/lib/dri/iris_dri.so #3 0x7fe0d9dd63e9 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fe0da57c293 in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7fe0bd3f9640 (LWP 34476) "kwin_x1:disk$2"): #0 0x7fe0d9ddc6a2 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fe0beced8dc in () at /usr/lib/dri/iris_dri.so #2 0x7fe0beced7d8 in () at /usr/lib/dri/iris_dri.so #3 0x7fe0d9dd63e9 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fe0da57c293 in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7fe0bdbfa640 (LWP 34475) "kwin_x1:disk$1"): #0 0x7fe0d9ddc6a2 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fe0beced8dc in () at /usr/lib/dri/iris_dri.so #2 0x7fe0beced7d8 in () at /usr/lib/dri/iris_dri.so #3 0x7fe0d9dd63e9 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fe0da57c293 in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7fe0be3fb640 (LWP 34474) "kwin_x1:disk$0"): #0 0x7fe0d9ddc6a2 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fe0beced8dc in () at /usr/lib/dri/iris_dri.so #2 0x7fe0beced7d8 in () at /usr/lib/dri/iris_dri.so #3 0x7fe0d9dd63e9 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fe0da57c293 in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7fe0cdabc640 (LWP 34410) "QQmlThread"): #0 0x7fe0da57156e in ppoll () at /usr/lib/libc.so.6 #1 0x7fe0dab568ab in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7fe0dab57fed in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7fe0dab0065c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fe0da91aca2 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7fe0d938c4b9 in () at /usr/lib/libQt5Qml.so.5 #6 0x7fe0da91be8f in () at /usr/lib/libQt5Core.so.5 #7 0x7fe0d9dd63e9 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fe0da57c293 in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7fe0cf79f640 (LWP 34353) "QDBusConnection"): #0 0x7fe0da57156e in ppoll () at /usr/lib/libc.so.6 #1 0x7fe0dab568ab in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7fe0dab57fed in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7fe0dab0065c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fe0da91aca2 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7fe0dbc05098 in () at /usr/lib/libQt5DBus.so.5 #6 0x7fe0da91be8f in () at /usr/lib/libQt5Core.so.5 #7 0x7fe0d9dd63e9 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fe0da57c293 in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7fe0d4a99640 (LWP 3433
[dolphin] [Bug 445976] Cannot write to samba share
https://bugs.kde.org/show_bug.cgi?id=445976 --- Comment #1 from Rick --- Libreoffice exits without saving file or leaving partial file on server. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 445976] New: Cannot write to samba share
https://bugs.kde.org/show_bug.cgi?id=445976 Bug ID: 445976 Summary: Cannot write to samba share Product: dolphin Version: 21.08.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: rick0...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Client can read and create files and folders but cannot overwrite existing files on samba share. STEPS TO REPRODUCE 1. Open shared file on samba server through Dolphin 2. Edit file in kwrite, kate, libreoffice 3. Save file OBSERVED RESULT The following error appears: Could not rename partial file smb://raspberrypi.local/pi/shared/filename.part. Please check permissions. A partial file is left on server. EXPECTED RESULT Save file without issues SOFTWARE/OS VERSIONS Windows: 11 macOS: Linux/KDE Plasma: 5.11.0.40-generic(64-bit) (available in About System) KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION Windows 11 Notepad works perfectly through Windows file explorer Dolphin version 20.12.2 works perfectly Linux kernel: 5.10.0-9-amd64 KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 445976] Cannot write to samba share
https://bugs.kde.org/show_bug.cgi?id=445976 --- Comment #3 from Rick --- just checked and yes it is installed. Krusader works in place of Dolphin but I hate that app. On Tue, Nov 23, 2021 at 12:14 PM Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=445976 > > Nate Graham changed: > >What|Removed |Added > > > Resolution|--- |WAITINGFORINFO > CC||n...@kde.org > Status|REPORTED|NEEDSINFO > > --- Comment #2 from Nate Graham --- > Do you have kio-fuse installed? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 445976] Cannot write to samba share
https://bugs.kde.org/show_bug.cgi?id=445976 --- Comment #5 from Rick --- I've changed my distro from KDE Neon to MX Linux KDE version. This distro uses Dolphin 20.12.2 and everything is running fine. The only change in my setup is the distro; hardware, network and server are all the same. I'll keep a version of KDE Neon around to help you with troubleshooting but it is not my daily use distro anymore. -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 446580] Contact synchronization with google doesn't work.
https://bugs.kde.org/show_bug.cgi?id=446580 Rick changed: What|Removed |Added CC||rhs.mess...@gmail.com --- Comment #2 from Rick --- Operating System: FreeBSD 13.0 KDE Plasma Version: 5.24.1 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 13.0-RELEASE-p7 (64-bit) Graphics Platform: X11 Memory: 15.9 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 3000 Not only is the Gcontact import stub not working, but, manually trying to add a Vcard file will not work either. You now have to request your data be sent to you by google if you want a vcard formated list of your contacts. This should at the minimum work locally. What a disappointment after successfully setting up what seems to be a very good imap server with Kmail. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 453666] Pen is acting super funny
https://bugs.kde.org/show_bug.cgi?id=453666 Rick changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 453666] New: Pen is acting super funny
https://bugs.kde.org/show_bug.cgi?id=453666 Bug ID: 453666 Summary: Pen is acting super funny Product: krita Version: 5.0.6 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Tablets (tablet issues are only very rarely bugs in Krita!) Assignee: krita-bugs-n...@kde.org Reporter: rick.g.phi...@gmail.com Target Milestone: --- SUMMARY *** Just today, when I try to use my pen on my Huion GT-190 tablet screen, it senses the pen from too far away and won't let go of it. Even after i pull my pen and arm away from the tablet, the program is still trying to sense the pen and will continue to draw as if I was putting pressure on the pen, even if I move the mouse around. *** STEPS TO REPRODUCE 1. Close program 2. Open Program 3. Draw OBSERVED RESULT Program acts as if the pen is pressing against the screen when it actually is away from screen. EXPECTED RESULT To draw normally SOFTWARE/OS VERSIONS Windows: 10 (86_64) (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: 5.12.12 ADDITIONAL INFORMATION I have tried to recalibrate my pen and drawing tablet, but it hasn't worked. I have also restarted my computer and programs and it hasn't worked. I have tested this out on other programs, like Paint.net and photoshop, and I don't have a problem with them. I had this problem on a previous version, (It was 4.4 something) and I thought updating it would fix it. It hasn't. -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 458047] New: black screen
https://bugs.kde.org/show_bug.cgi?id=458047 Bug ID: 458047 Summary: black screen Product: skrooge Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: guillaume.deb...@gmail.com Reporter: anrimer...@yahoo.com CC: steph...@mankowski.fr Target Milestone: --- SUMMARY *** used sudo command to install Skrooge, rebooted on completed install, clicked icon and received a black screen NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. 2. 3. 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.
[systemsettings] [Bug 458971] New: Add a section in system settings "About This System" page to change device\host name of the computer
https://bugs.kde.org/show_bug.cgi?id=458971 Bug ID: 458971 Summary: Add a section in system settings "About This System" page to change device\host name of the computer Product: systemsettings Version: 5.24.6 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: s.snide...@gmail.com Target Milestone: --- Created attachment 151967 --> https://bugs.kde.org/attachment.cgi?id=151967=edit Example of the device name from Ubuntu and tool tip example SUMMARY I have noticed that there is no GUI way to change the computer\machine\Host name or even view the name in KDE Plasma. This is a basic function that is even implemented in Gnome settings. This would be a great addition for user friendliness and an UI improvement. STEPS TO REPRODUCE 1. There are no steps to reproduce as this is a feature request. EXPECTED RESULT I think this computer name change feature could be simply added to the "About This System" page. It can be setup exactly like the Hardware and Software sections are setup. The header would be called "Device Name" and under it an editable box with the current device name. One name is inputted prompt for reboot if required. Additional as a tool tip, when you hoover over the editable box a tool tip should appear explaining that this sections changes the name of the device and the new name will be how it appears throughout your network and a reboot may be required. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 22.04.1 (available in About System) KDE Plasma Version: 5.24.6 KDE Frameworks Version: 5.95 Qt Version: 5.15.3 ADDITIONAL INFORMATION None -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 458971] Add a section in system settings "About This System" page to change device\host name of the computer
https://bugs.kde.org/show_bug.cgi?id=458971 --- Comment #1 from Rick --- Created attachment 151968 --> https://bugs.kde.org/attachment.cgi?id=151968=edit Example form Ubuntu -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 458971] Add a section in system settings "About This System" page to change device\host name of the computer
https://bugs.kde.org/show_bug.cgi?id=458971 Rick changed: What|Removed |Added Attachment #151967|Example of the device name |tool tip example description|from Ubuntu and tool tip| |example | -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 460161] Unable to run commands from Power menu
https://bugs.kde.org/show_bug.cgi?id=460161 --- Comment #1 from Rick --- Created attachment 152663 --> https://bugs.kde.org/attachment.cgi?id=152663=edit unable to run command popup error -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 460161] New: Unable to run commands from Power menu
https://bugs.kde.org/show_bug.cgi?id=460161 Bug ID: 460161 Summary: Unable to run commands from Power menu Classification: Applications Product: kdeconnect Version: unspecified Platform: Android OS: Android 12.x Status: REPORTED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: meeseekslifeish...@tutanota.com Target Milestone: --- SUMMARY When I try to run commands like Unlock, Suspend I am able to run those from KDE Connect application but when I try to run the same through power menu device control it says not found. Control is unavilable STEPS TO REPRODUCE 1. Add commands to execute in kde Connect app 2. Now enable device control in android 3. add the commands to device control 4. Press power button and try to launch the commands from the power menu OBSERVED RESULT It says not found, Control is unavailable. EXPECTED RESULT Ability to run commands from power menu SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 36 (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.
[kded-appmenu] [Bug 466036] New: kded5 crash after resume from blank
https://bugs.kde.org/show_bug.cgi?id=466036 Bug ID: 466036 Summary: kded5 crash after resume from blank Classification: Plasma Product: kded-appmenu Version: 5.27.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Titlebar menu button/popup Assignee: plasma-b...@kde.org Reporter: dxq7...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** kded5 crash after resume from blank ``` Application: kded5 (kded5), signal: Segmentation fault [KCrash Handler] #4 0x7f49d62ad270 in KScreen::Output::id() const () from /lib64/libKF5Screen.so.8 #5 0x7f49d62a01f8 in KScreen::Config::setOutputPriority(QSharedPointer const&, unsigned int) () from /lib64/libKF5Screen.so.8 #6 0x7f49d62a9ca2 in KScreen::SetConfigOperation::start() () from /lib64/libKF5Screen.so.8 #7 0x7f4a11907d00 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #8 0x7f4a127a544e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #9 0x7f4a118dc1e8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #10 0x7f4a118df181 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #11 0x7f4a11934413 in ?? () from /lib64/libQt5Core.so.5 #12 0x7f4a1051ba90 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #13 0x7f4a1051be48 in ?? () from /lib64/libglib-2.0.so.0 #14 0x7f4a1051bedc in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #15 0x7f4a11933c16 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #16 0x7f4a118dac5b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #17 0x7f4a118e2dc6 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #18 0x55f59658b976 in ?? () #19 0x7f4a1102caf0 in __libc_start_call_main () from /lib64/libc.so.6 #20 0x7f4a1102cbb9 in __libc_start_main_impl () from /lib64/libc.so.6 #21 0x55f59658bb75 in ?? () [Inferior 1 (process 2368) detached] ``` STEPS TO REPRODUCE 1. settings -> power management -> display off after 1 minute 2. resume display after the screen black 3. get kded5 crash error, tray icon not working and maybe others OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: archlinux/opensuse tumbleweed (available in About System) KDE Plasma Version:plasma 5.27.0 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 373055] New: CSV importer opens some modal windows behind parent windows
https://bugs.kde.org/show_bug.cgi?id=373055 Bug ID: 373055 Summary: CSV importer opens some modal windows behind parent windows Product: kmymoney4 Version: 4.8.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: csvimporter Assignee: kmymoney-de...@kde.org Reporter: r...@firefang.com Target Milestone: --- When using the CSV importer, it has a tendency to open modal windows behind the CSV importer window, which makes KMyMoney appear to have locked up. You can't even move the window that's blocking the new dialogue, because the new dialogue is modal. I've noticed this on warning messages, as well as on selecting the account to import into at the end of the process. Here's one way to reproduce it: 1) Open a KMyMoney file with a CSV banking profile already set up. 2) File -> Import -> CSV 3) Select an existing CSV profile 4) Click the 'clear' button to the right of the profile name. 5) KMyMoney will pop up a modal 'Delete or Edit Profile Name' dialogue UNDER the "CSVWizard" window to which it's parented. Workarounds: 1) Make sure you move the CSVWizard window AWAY from the centre of the screen before doing anything with it, so it won't be blocking any windows that pop up. 2) On Windows, you can use Alt+Space,M to enter 'move window' mode. Use the cursor keys to move the window out into the open. The core of the problem seems to be that the CSVWizard window is a topmost window, staying on top even when other applications are open. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 373057] New: More line filter options in CSV importer
https://bugs.kde.org/show_bug.cgi?id=373057 Bug ID: 373057 Summary: More line filter options in CSV importer Product: kmymoney4 Version: 4.8.0 Platform: Other OS: All Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: csvimporter Assignee: kmymoney-de...@kde.org Reporter: r...@firefang.com Target Milestone: --- On the 'Lines' page of the CSV importer, I'd like to see another filter option, like so: Include rows where column [column number dropdown] contains [text input] For instance, I could set it to: Include rows where column [7] contains [USD] and if my CSV includes some rows that say 'USD' and other rows that say 'CAD', it would only include the rows that say 'USD'. Rationale: PayPal effectively gives you different accounts for each currency, but in order to get all the details of your transactions, you need to download a CSV file with all the currencies mixed together, like so: Date, Time, Time Zone, Name, Type, Status, Currency, Amount, Receipt ID, Balance, "21/11/2016","09:43:15","PST","Dotster","Preapproved Payment Sent","Completed","USD","-9.99","","0.00", "21/11/2016","09:43:15","PST","From Canadian Dollar","Currency Conversion","Completed","USD","9.99","","9.99", "21/11/2016","09:43:15","PST","To U.S. Dollar","Currency Conversion","Completed","CAD","-13.84","","0.00", "21/11/2016","09:43:15","PST","Bank Account","Add Funds from a Bank Account","Completed","CAD","13.84","","13.84", "06/11/2016","03:15:16","PST","Thomas McDiarmid","Express Checkout Payment Sent","Completed","USD","-79.95","","0.00", "06/11/2016","03:15:16","PST","From Canadian Dollar","Currency Conversion","Completed","USD","74.07","","79.95", "06/11/2016","03:15:16","PST","To U.S. Dollar","Currency Conversion","Completed","CAD","-102.20","","0.00", "06/11/2016","03:15:16","PST","Bank Account","Add Funds from a Bank Account","Completed","CAD","25.60","","102.20", Notice the 'Currency' column. I'd like an easy way to import different lines into my "PayPal USD" account and my "PayPal CAD" account. With the feature I'm requesting, I can just import the same CSV twice with different filters and have it work fine. Of course, you could write more complicated features to handle this better. For instance, the 'Banking' page could include an 'Account' column and a table that lets me associate cells that say 'USD' with the 'PayPal USD' account, but that's a lot more complicated than this feature, and I think this feature is useful in any case. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 358265] Can't select AM while setting Start/Due time for a To-do
https://bugs.kde.org/show_bug.cgi?id=358265 Rick Harris <rickfhar...@yahoo.com.au> changed: What|Removed |Added CC||rickfhar...@yahoo.com.au --- Comment #1 from Rick Harris <rickfhar...@yahoo.com.au> --- Confirmed. Still occurring in 16.12. Mornings have been deprecated in Korganizer or it's a glaring regression :D -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 358265] Can't select AM while setting Start/Due time for a To-do
https://bugs.kde.org/show_bug.cgi?id=358265 --- Comment #2 from Rick Harris <rickfhar...@yahoo.com.au> --- (In reply to Rick Harris from comment #1) > Confirmed. > > Still occurring in 16.12. > > Mornings have been deprecated in Korganizer or it's a glaring regression :D Similar problem from another user here -> https://www.kubuntuforums.net/showthread.php?69327-Kontact-Doesn-t-Provide-AM-Times However trying the same workaround of setting a different Timezone from the actual location (how can this be good?) doesn't actually work either because setting Timezone's don't stick in KDE5 either. Judging by the lack of response to this bug in nearly a year I'd guess that no-one is seriously using this software anymore anyway :( -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 169336] Events excluded or deleted in a recurring event block still show in other clients subscribed to a calendar (see RFC 2445 re. EXDATE)
https://bugs.kde.org/show_bug.cgi?id=169336 Rick Harris <rickfhar...@yahoo.com.au> changed: What|Removed |Added Version|4.8.x |5.4.0 Resolution|UNMAINTAINED|--- Status|RESOLVED|REOPENED -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 169336] Events excluded or deleted in a recurring event block still show in other clients subscribed to a calendar (see RFC 2445 re. EXDATE)
https://bugs.kde.org/show_bug.cgi?id=169336 --- Comment #11 from Rick Harris <rickfhar...@yahoo.com.au> --- Re-opened as this bug is still present in the latest 5.4.0 version (16.12). This bug is extremely easy to reproduce, can we please only close bugs when they're fixed and not because the software gets version bumped - thanks :) -- 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 #54 from Rick J <r...@activeservice.co.uk> --- Hi Albert I'm happy to test out any code changes you want to try. I see the same sympton as others are reporting on AOS 7 (no write access, and can't browse the top-level of the external card - see comment 50). Let me know if I can be any help. -- 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 Rick J <r...@activeservice.co.uk> changed: What|Removed |Added CC||r...@activeservice.co.uk --- Comment #50 from Rick J <r...@activeservice.co.uk> --- I've just encountered this bug on a new phone (LG G5) running AOS 6. When I open the device in Dolphin I get: > Camera pictures(Internal storage) Camera pictures(SD card) > Internal storage SD card "SD card" is a real card, "Internal storage" is the emulated card. No directories are detected on the SD card. But if I step into the apparently empty SD card directory, then edit the path and add /DCIM on the end (or any other directory that exists) its contents appear. The contents are readable but nothing is writeable, which is a bit of a limitation. I believe the (bonkers) restrictions on the external card introduced in AOS 4 were removed in 5 & 6, so the SD card should be browseable. Non-privileged file managers such as Explorer (non-root version) can see the directories on the card, so KDEconnect should be able to as well. Is there maybe a new API since AOS 4 for doing this? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 374482] the 'impossible' happened: run_innerloop detected host state invariant failure
https://bugs.kde.org/show_bug.cgi?id=374482 Rick R. <rick.ramstetter+...@gmail.com> changed: What|Removed |Added Attachment #103159|0 |1 is obsolete|| --- Comment #1 from Rick R. <rick.ramstetter+...@gmail.com> --- Created attachment 103160 --> https://bugs.kde.org/attachment.cgi?id=103160=edit 'dpkg -l' output from the container -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 374482] New: the 'impossible' happened: run_innerloop detected host state invariant failure
https://bugs.kde.org/show_bug.cgi?id=374482 Bug ID: 374482 Summary: the 'impossible' happened: run_innerloop detected host state invariant failure Product: valgrind Version: 3.12.0 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: rick.ramstetter+...@gmail.com Target Milestone: --- Created attachment 103159 --> https://bugs.kde.org/attachment.cgi?id=103159=edit dpkg --get-selections output for the 14.04 userspace The execution environment is a 32bit Docker container with an Ubuntu 14.04 userspace (via Ubuntu Core project). The host is a 64 bit installation of Ubuntu 16.04. The system kernel was recently updated from 4.8.1 to 4.9. Various container packages were recently updated via `apt-get upgrade`. $ valgrind --tool=none /bin/false ==13039== Nulgrind, the minimal Valgrind tool ==13039== Copyright (C) 2002-2015, and GNU GPL'd, by Nicholas Nethercote. ==13039== Using Valgrind-3.12.0 and LibVEX; rerun with -h for copyright info ==13039== Command: /bin/false ==13039== valgrind: m_scheduler/scheduler.c:1611 (vgPlain_scheduler): the 'impossible' happened. valgrind: VG_(scheduler), phase 3: run_innerloop detected host state invariant failure host stacktrace: ==13039==at 0x380B4116: show_sched_status_wrk (m_libcassert.c:343) ==13039==by 0x380B4256: report_and_quit (m_libcassert.c:419) ==13039==by 0x380B437B: vgPlain_assert_fail (m_libcassert.c:485) ==13039==by 0x3805AD9A: vgPlain_scheduler (scheduler.c:1609) ==13039==by 0x3806CE86: run_a_thread_NORETURN (syswrap-linux.c:103) sched status: running_tid=1 Thread 1: status = VgTs_Runnable (lwpid 13039) ==13039==at 0x4007FEA: _dl_map_object (dl-load.c:2317) ==13039==by 0x400133E: map_doit (rtld.c:626) ==13039==by 0x400EC05: _dl_catch_error (dl-error.c:187) ==13039==by 0x40008B0: do_preload (rtld.c:815) ==13039==by 0x4003F66: dl_main (rtld.c:1629) ==13039==by 0x4014F5A: _dl_sysdep_start (dl-sysdep.c:249) ==13039==by 0x40049DA: _dl_start (rtld.c:331) ==13039==by 0x40010D6: ??? (in /lib/i386-linux-gnu/ld-2.19.so) $ valgrind --version valgrind-3.12.0 # author note: source install via valgrind-3.12.0.tar.bz2 $ getconf LONG_BIT 32 $ uname -m x86_64 $ ldd --version ldd (Ubuntu EGLIBC 2.19-0ubuntu6.9) 2.19 $ gcc --version gcc (Ubuntu/Linaro 4.6.4-6ubuntu2) 4.6.4 $ ld --version GNU ld (GNU Binutils for Ubuntu) 2.24 I will endeavor to switch the machine back to kernel 4.8.1 and gauge impact. Valgrind works as expected on the 16.04 host. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 374482] the 'impossible' happened: run_innerloop detected host state invariant failure
https://bugs.kde.org/show_bug.cgi?id=374482 Rick R. <rick.ramstetter+...@gmail.com> changed: What|Removed |Added CC||rick.ramstetter+kde@gmail.c ||om -- You are receiving this mail because: You are watching all bug changes.
[knotes] [Bug 358973] Knotes do not drag, they only drop at the location of the released mouse-button
https://bugs.kde.org/show_bug.cgi?id=358973 Rick Alther <alt...@acm.org> changed: What|Removed |Added CC||alt...@acm.org --- Comment #3 from Rick Alther <alt...@acm.org> --- This is still a problem (no dragging, the note just moves where you release the mouse button). I'm on Fedora 24: KNotes: 16.08.3 KDE Framework: 5.27.0 Qt: 5.6.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378355] 'Desktop Switcher' in Panel does not update highlighted desktop when user has switched to a another.
https://bugs.kde.org/show_bug.cgi?id=378355 Rick Stockton <rickstock...@reno-computerhelp.com> changed: What|Removed |Added Keywords||regression, usability -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378355] New: 'Desktop Switcher' in Panel does not update highlighted desktop when user has switched to a another.
https://bugs.kde.org/show_bug.cgi?id=378355
Bug ID: 378355
Summary: 'Desktop Switcher' in Panel does not update
highlighted desktop when user has switched to a
another.
Product: plasmashell
Version: 5.9.4
Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Desktop Dashboard
Assignee: notm...@gmail.com
Reporter: rickstock...@reno-computerhelp.com
CC: bhus...@gmail.com
Target Milestone: 1.0
Using openSUSE Plasma 5.9.4-1 with corresponding kwin5. ("Tumbleweed" latest
and greatest, built 2017-03-21).
When switching desktops within the primary panel's "desktop switcher widget",
and also when switching via shortcut (keyboard or mouse switching), then
"desktop switcher widget" does not show that you have moved to a different
desktop. The highlighted desktop indication is "stuck", and does not move.
With Plasma-5 (or kwin, I don't know where the "responsibility" lies) unable to
provide different desktop back ground images per desktop, the pager becomes
more critical to see "where you are" among your virtual desktops.
The pager works great for moving application windows among desktops - it just
doesn't update the highighted "desktop" correctly.
--
You are receiving this mail because:
You are watching all bug changes.
[kate] [Bug 378579] kate (and kwrite) on large files: version 3.7 is fine, version 15 sucks
https://bugs.kde.org/show_bug.cgi?id=378579 --- Comment #5 from Rick Graves <gravesricha...@yahoo.com> --- The Thinkpad T500 uses the ATI Mobility Radeon HD 3650 display adapter (http://www.thinkwiki.org/wiki/Category:T500). I have the same problem with kate and kwrite on my home desktop, which has a dual core Athlon II CPU and 16 GB of memory, on which kinfocenter says the display adapter is NVIDIA GT218 [GeForce 210]. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 378579] kate (and kwrite) on large files: version 3.7 is fine, version 15 sucks
https://bugs.kde.org/show_bug.cgi?id=378579 --- Comment #6 from Rick Graves <gravesricha...@yahoo.com> --- How does one activate highlighting? I am mostly using the default configuration. For kate, I set the line length limit to zero and I use spaces not tabs. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 378579] kate (and kwrite) on large files: version 3.7 is fine, version 15 sucks
https://bugs.kde.org/show_bug.cgi?id=378579 --- Comment #3 from Rick Graves <gravesricha...@yahoo.com> --- Bug 378330 seems to be related, but that one is only about the paste delay. I use kate for small files (python scripts) and have no problem pasting into small files. If my only problem was the paste delay, I would live with it and I would never have complained. For me, the much bigger aggravation is the arrow keys do not work with keyboard repeat in 16.04 and 16.10, kate version 5/15 (kate says version 15, kwrite says kate version 5). -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 378579] kate (and kwrite) on large files: version 3.7 is fine, version 15 sucks
https://bugs.kde.org/show_bug.cgi?id=378579 --- Comment #4 from Rick Graves <gravesricha...@yahoo.com> --- Created attachment 104929 --> https://bugs.kde.org/attachment.cgi?id=104929=edit Thinkpad T500 with kubuntu drives for 14.04 & 16.04 One laptop, two hard drives, 1) kubuntu 14.04 & 2) kubuntu 16.04. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378355] 'Desktop Switcher' in Panel does not update highlighted desktop when user has switched to a another.
https://bugs.kde.org/show_bug.cgi?id=378355 Rick Stockton <rickstock...@reno-computerhelp.com> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #1 from Rick Stockton <rickstock...@reno-computerhelp.com> --- Looking more carefully, it *is* working. The too-subtle-for-me-to-see highlighting would be a theme issue, if we see a bunch of duplicate reports in the future. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 378579] kate (and kwrite) on large files: version 3.7 is fine, version 15 sucks
https://bugs.kde.org/show_bug.cgi?id=378579 --- Comment #10 from Rick Graves <gravesricha...@yahoo.com> --- Created attachment 104985 --> https://bugs.kde.org/attachment.cgi?id=104985=edit 4 core i5 3230M 2.60GHz laptop laptop on which kate/kwrite performance is good on big files. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 378579] kate (and kwrite) on large files: version 3.7 is fine, version 15 sucks
https://bugs.kde.org/show_bug.cgi?id=378579 --- Comment #11 from Rick Graves <gravesricha...@yahoo.com> --- Good news. See the picture I uploaded -- a 4 core i5 3230M 2.60GHz laptop (Lenovo Thinkpad Edge E431, came with Windows 8). Testing as described using kubuntu 16.04 (kate/kwrite version 5/15), performance is good. For use on big files, it seems the minimum hardware requirements for the kate editor exceed the minimum hardware requirements for kubuntu. Is the bottom line that for big files, kate needs 4 cores, 2 cores are not enough? In an ideal world, this would be up front, and people like me would not have to discover it by trial and error. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 378330] Kate is very slow when deleting or pasting a lot of text
https://bugs.kde.org/show_bug.cgi?id=378330 Rick Graves <gravesricha...@yahoo.com> changed: What|Removed |Added CC||gravesricha...@yahoo.com --- Comment #2 from Rick Graves <gravesricha...@yahoo.com> --- See https://bugs.kde.org/show_bug.cgi?id=378579#c11 Maybe kate now needs more cores in the CPU. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 378579] kate (and kwrite) on large files: version 3.7 is fine, version 15 sucks
https://bugs.kde.org/show_bug.cgi?id=378579 --- Comment #7 from Rick Graves <gravesricha...@yahoo.com> --- Created attachment 104933 --> https://bugs.kde.org/attachment.cgi?id=104933=edit testing kubuntu 16.04 (kate version 5/15) on a kubuntu 14.04 (kate version 3) desktop On my alternate office desktop, I unplugged the hard drive on which kubuntu 16.04 (kate version 3) is installed and installed kubuntu 16.04 (kate version 5/15) on a spare hard drive. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 378579] kate (and kwrite) on large files: version 3.7 is fine, version 15 sucks
https://bugs.kde.org/show_bug.cgi?id=378579 --- Comment #8 from Rick Graves <gravesricha...@yahoo.com> --- I tried kubuntu 16.04 (kate version 5/15) on my alternate office desktop (see the picture I uploaded just now). Following the test procedure described, after hitting paste (Ctrl-V), the text took 5 seconds to appear, and after hitting down arrow once, it took 6 seconds for the cursor to appear one line down from the top. The hardware is an Athlon II dual core CPU, 8 GB of memory, nVidia GeForce 8400GS display card, monitor with 1920 x 1080 pixels resolution. Yes on this hardware kate version 3 (kubuntu 14.04) performs well, the pasted text appears instantly, the cursor appears one line down instantly. I believe my hardware all greatly exceeds the minimum recommended for kubuntu. Two questions: 1) What is the minimum recommended hardware to run a QT5 application? (I looked and did not find on google.) 2) What hardware does the maintainer use to test kate and kwrite? Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 378579] New: kate (and kwrite) on large files: version 3.7 is fine, version 15 sucks
https://bugs.kde.org/show_bug.cgi?id=378579 Bug ID: 378579 Summary: kate (and kwrite) on large files: version 3.7 is fine, version 15 sucks Product: kate Version: 15.12 Platform: Debian stable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: gravesricha...@yahoo.com Target Milestone: --- Created attachment 104928 --> https://bugs.kde.org/attachment.cgi?id=104928=edit It shows the cursor one line down from the top. I am on kubuntu, so I get the kate (and kwrite) version the ubuntu people give me. I have been using kwrite to maintain a big file (25 mb). (Note that kwrite uses the kate editor.) On kubuntu 14.04 (kate version 3), kwrite worked great. When I first tried kubuntu 16.04 (kate version 5/15) in early 2016, kwrite was clearly not the same: 1. For the arrow keys, keyboard repeat works at the top of the file, but not further down. In kate version 5/15, the display does not update -- you cannot see where the cursor is. If you hold an arrow key down for a while and release, after some seconds, the cursor freezes then reappears somewhere. In kate version 3, anywhere in the file, you see exactly where the cursor is at every instant, you can release the arrow key when you want, and the cursor is where you expect it to be. 2. Pasting text into the file (anywhere except the top), kate version 5/15 takes several seconds for the text to appear. Using kate version 3, the text appeared instantly. After evaluating kubuntu 16.04 in early 2016, the kwrite problem was a show stopper -- I declined to upgrade kubuntu, and I have been on 14.04 until recently. But then in March, a more pressing consideration made me upgrade to 16.04, and kwrite is still a problem on my big file. In 2016, I tried tweaking settings in hope of fixing the problem, but I did not find a solution. Note that I encountered this problem using the same hardware. Right now, I have two hard drives for my Lenovo Thinkpad T500 laptop with 8 GB memory, one hard drive with kubuntu 14.04 (kate version 3), and another hard drive with kubuntu 16.04 (kate version 5/15). I can shut the laptop down and swap hard drives. You can say my laptop is too slow, but kate version 3 works perfectly OK on my laptop -- no complaints. But on the same laptop, kate version 5/15 sucks. I have encountered deniers, so I assembled a big file -- anyone can try it themselves. I googled "Richard Stallman", went to some hit pages, and copied some text by or about him. I pasted into a file and duplicated. I used the fmt utility to break the long lines into shorter lines (the file I edit in real life has mostly short lines). The file is almost 27 mb (too big to attach). I gzipped it, and uploaded it here: http://www.advanced-app.com.hk/MiscJunk/Stallman_Richard_short.txt.gz For both the following tests, I used wget to download the file and gzip -d to extract it. For the latter of the two tests below, see the attached picture. It shows the cursor one line down from the top. The test, conducted near the bottom of the file, is to determine, after pressing down arrow once, how long it takes for the cursor to appear one line down from the top (as explained in detail below). On the Lenovo Thinkpad T500 laptop with 8 GB memory running kubuntu 16.04 (kate version 5/15): I went to the bottom of the file, and from the bottom I selected up to and including the line "The consequences:". I copied the selected text. I used PgUp several times until I came to the heading "The GNU Manifesto". Above that heading, I hit Paste (Ctrl-V), and counted "one thousand one, one thousand two, one thousand three, ..." The inserted text appeared between one thousand five and one thousand six. I hit Ctrl-Z. I pressed the up arrow key, and kept pressing it while I counted ""one thousand one, one thousand two, one thousand three, one thousand four, one thousand five" then I released the up arrow key, immediately pressed down arrow once (quickly) and started counting again. The cursor did not appear one line down from the top until AFTER I counted up to one thousand eight. On the SAME Lenovo Thinkpad T500 laptop with 8 GB memory, running kubuntu 14.04 (kate version 3): I went to the bottom of the file, and from the bottom I selected up to and including the line "The consequences:". I copied the selected text. I used PgUp several times until I came to the heading "The GNU Manifesto". Above that heading, I hit Paste (Ctrl-V). There was no need to count, as the inserted text appeared instantaneously (to my human perception). I hit Ctrl-Z. I pressed the up arrow key, and kept pressing it while I counted ""one thousand one, one thousand two, one thousand three, one thousand four, one thousand five" then I released the up arrow key, immediately pressed down arrow once
[neon] [Bug 379254] ksmserver errors after updating to Plasma 5.9.5
https://bugs.kde.org/show_bug.cgi?id=379254 Rick Beldin <rick.bel...@gmail.com> changed: What|Removed |Added CC||rick.bel...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 379811] New: segfault while using plasma-discover
https://bugs.kde.org/show_bug.cgi?id=379811 Bug ID: 379811 Summary: segfault while using plasma-discover Product: Discover Version: 5.9.4 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: rick.bel...@gmail.com Target Milestone: --- Application: plasma-discover (5.9.4) Qt Version: 5.7.1 Frameworks Version: 5.31.0 Operating System: Linux 4.10.0-20-generic x86_64 Distribution: Ubuntu 17.04 -- Information about the crash: - What I was doing when the application crashed: I was searching for various plasma themes. I had run it manually with plasma-discover --compact full. The crash ended with this on the screen: org.kde.knewstuff.core: Redirected to "https://download.kde.org/khotnewstuff/korganizercalenders/korganizercalenders.xml; ... org.kde.knewstuff.core: Redirected to "https://distribute.kde.org/khotnewstuff/korganizercalenders/korganizercalenders.xml; ... KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = plasma-discover path = /usr/bin pid = 11328 KCrash: Arguments: /usr/bin/plasma-discover --compact full KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 QSocketNotifier: Invalid socket 25 and type 'Write', disabling... QSocketNotifier: Invalid socket 8 and type 'Read', disabling... QSocketNotifier: Invalid socket 16 and type 'Read', disabling... QSocketNotifier: Invalid socket 13 and type 'Read', disabling... QSocketNotifier: Invalid socket 34 and type 'Read', disabling... QSocketNotifier: Invalid socket 19 and type 'Read', disabling... QSocketNotifier: Invalid socket 26 and type 'Write', disabling... QSocketNotifier: Invalid socket 32 and type 'Write', disabling... QSocketNotifier: Invalid socket 20 and type 'Read', disabling... QSocketNotifier: Invalid socket 40 and type 'Write', disabling... QSocketNotifier: Invalid socket 27 and type 'Write', disabling... The crash can be reproduced sometimes. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f712f3ee8c0 (LWP 11328))] Thread 19 (Thread 0x7f70d97fa700 (LWP 11456)): #0 0x7f712a99e18d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f7125650576 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f712565068c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f712b5caf2b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f712b57488a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f712b3a1fe3 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f712b3a6c98 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f71277816da in start_thread (arg=0x7f70d97fa700) at pthread_create.c:456 #8 0x7f712a9aa17f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 18 (Thread 0x7f70daffd700 (LWP 11430)): #0 0x7f712f2cfe15 in __GI___tls_get_addr (ti=0x7f712b9bf660) at dl-tls.c:834 #1 0x7f712b3a5b26 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f712b5ca67a in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f712564fa6d in g_main_context_prepare () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f712565049b in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f712565068c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f712b5caf2b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f712b57488a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f712b3a1fe3 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f712b3a6c98 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f71277816da in start_thread (arg=0x7f70daffd700) at pthread_create.c:456 #11 0x7f712a9aa17f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 17 (Thread 0x7f70f0afa700 (LWP 11428)): #0 0x7f712a999cad in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f7125694b30 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f7125650042 in g_main_context_check () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f7125650514 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f712565068c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f712b5caf2b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f712b57488a in QEventLoop::exec(QFlags) () at
[dolphin] [Bug 379665] search is not working in "from here"
https://bugs.kde.org/show_bug.cgi?id=379665 Rick Graves <gravesricha...@yahoo.com> changed: What|Removed |Added CC||gravesricha...@yahoo.com --- Comment #2 from Rick Graves <gravesricha...@yahoo.com> --- Created attachment 105600 --> https://bugs.kde.org/attachment.cgi?id=105600=edit "From Here" option is not working. In the uploaded screen shot, here is /home/Common/pyPacks, yet as one can see, Dolphin is finding files in /usr/lib/python2.7/encodings. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 379665] search is not working in "from here"
https://bugs.kde.org/show_bug.cgi?id=379665 --- Comment #3 from Rick Graves <gravesricha...@yahoo.com> --- BTW, I am using Dolphin 4.13.3, via kubuntu 14.04 (I am back to 14.04 because the kate & kwrite that come with 16.04 require at least a 4 core CPU to work acceptably on large files -- large files are not a problem with the kate & kwrite that come with 14.04. Yes there is a posted bug for this problem, https://bugs.kde.org/show_bug.cgi?id=378579 To solve my problem quickly, it was easier for me to revert to 14.04, and assemble 4 core CPU desktop systems & acquire 4 core CPU laptops at my leisure.) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 384753] crash / lock up when setting Icon View font in settings/configure
https://bugs.kde.org/show_bug.cgi?id=384753 --- Comment #2 from Rick Mason <rick.az.ma...@gmail.com> --- Hi Giles, I'll need some more time to do a re-compile for debug. While I have some IT background, I'm new enough to Linux that I'll have to do some learning. But, the good news is that while ver 5.6 has the same issues (I installed it first), 5.7 fixes it. So what ever changed between 5.6 and 5.7 did it. I can run 5.7 directly by clicking on the appimage file in downloads, but how do I "install" it so the launcher sees it? Currently, it still calls 5.6 The instructions I found *here <http://ubuntuhandbook.org/index.php/2017/06/digikam-5-6-0-released-how-to-install-it-in-ubuntu/>* say "The first launch will ask you if to install a shortcut for the AppImage.", but that was not the case for me, at least for the 5.7 image I downloaded via the link you provided. Let me know if a debug dump is still needed given that 5.7 worked. Thanks for the assist! Rick On Fri, Sep 15, 2017 at 7:56 PM, <bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=384753 > > caulier.gil...@gmail.com changed: > >What|Removed |Added > > > Status|UNCONFIRMED |RESOLVED > Resolution|--- |BACKTRACE > > --- Comment #1 from caulier.gil...@gmail.com --- > We need a gdb backtrace to hack. Please follow instructions here : > > https://www.digikam.org/contribute/ > > Also, please try to reproduce the problem with digiKam 5.7.0 Linux AppImage > just released : > > https://www.digikam.org/download/ > > -- > You are receiving this mail because: > You are on the CC list for the bug. > You reported the bug. > -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 384790] New: "Places" in Dolphin disappear
https://bugs.kde.org/show_bug.cgi?id=384790 Bug ID: 384790 Summary: "Places" in Dolphin disappear Product: kdeconnect Version: 1.3 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: r...@activeservice.co.uk Target Milestone: --- Whenever a kdeconnect device attaches or detaches, all the default places in Dolphin's panel disappear. This includes Home, Root, etc, all under Recently Saved and Search For, but not other Devices. The items that disappear are everything that's listed only in ~/.kde/share/apps/kfileplaces/bookmarks.xml, what remains is what's listed in ~/.local/share/user-places.xbel. At the instant it happens, ~/.local/share/user-places.xbel gets updated. I've looked at other bugs related to Dolphin Places, but they don't describe what I'm seeing. It doesn't happen when other devices (USB drives etc.) attach or detach, only kdeconnect. I'm running Kubuntu 16.04 LTS with KDE5. kdelibs is version 4:4.14.22. Let me know if you need any other info. Thanks -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 384753] New: crash / lock up when setting Icon View font in settings/configure
https://bugs.kde.org/show_bug.cgi?id=384753 Bug ID: 384753 Summary: crash / lock up when setting Icon View font in settings/configure Product: digikam Version: 5.4.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: Setup-LightTable Assignee: digikam-bugs-n...@kde.org Reporter: rick.az.ma...@gmail.com Target Milestone: --- Select Settings -> Configure DigiKam from menu bar Select Views on left bar Icon View font: Click System Font, pull down and select Custom Font Click Choose. Program will lock up. This is repeatable. Running DigiKam 5.4.0 Build date: Jan 28 2017 (target: Debian) Libraries: - KDE Frameworks 5.31.0 - Qt 5.7.1 (built against 5.7.1) - The xcb windowing system OS is: Ubuntu 17.04 System is: Lenovo Thinkpad Yoga 14 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 384753] crash / lock up when setting Icon View font in settings/configure
https://bugs.kde.org/show_bug.cgi?id=384753 Rick Mason <rick.az.ma...@gmail.com> changed: What|Removed |Added CC||rick.az.ma...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 384790] "Places" in Dolphin disappear
https://bugs.kde.org/show_bug.cgi?id=384790 Rick J <r...@activeservice.co.uk> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Rick J <r...@activeservice.co.uk> --- Hi, thanks for your comment. It is indeed a version issue - I've just installed Kubuntu 17.04 on a new machine, using the default version of kdeconnect, and the problem is gone. I'll either do a full upgrade on the other machine, or use the varlesh PPA. I wasn't aware of that one before. Cheers -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 378579] kate (and kwrite) on large files: version 3.7 is fine, version 15 sucks
https://bugs.kde.org/show_bug.cgi?id=378579 --- Comment #13 from Rick Graves <gravesricha...@yahoo.com> --- Some thoughts: 1) Package maintainers are volunteers and guys like me appreciate their efforts. 2) kubuntu is not kde, but kde needs distributions. 3) Ideally, kde could encourage package maintainers to test using systems that approximate the minimum hardware recommended by some popular distributions. If package maintainers only test using much more powerful hardware, they can remain oblivious to, and in denial of, the problems encountered by some rank and file users. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 389127] New: message and folder selection unresponsive
https://bugs.kde.org/show_bug.cgi?id=389127 Bug ID: 389127 Summary: message and folder selection unresponsive Product: kmail2 Version: 5.5.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: rsme...@aardvarr.ca Target Milestone: --- Left click on folders and messages in either folder pane or message list becomes unresponsive, the last viewed message is frozen in the message pane. Drop down menu items seem to work, eg view-message-list-sorting-aggregation can be selected and box ticked. Minimizing the window and then restoring will return Kmail to normal operation most of the time. Rarely, I would have to quit and restart kmail. This fault occurs on an average of once every twelve hours of continuous usage. First noticed last year with openSUSE leap 42.2 and is now manifest with leap 42.3. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 398426] New: konqueror crashes immediately no matter what I do -- it is unusable
https://bugs.kde.org/show_bug.cgi?id=398426 Bug ID: 398426 Summary: konqueror crashes immediately no matter what I do -- it is unusable Product: konqueror Version: 5.0.97 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: gravesricha...@yahoo.com Target Milestone: --- Created attachment 114857 --> https://bugs.kde.org/attachment.cgi?id=114857=edit screen shot of what I got after konqueror crashed at amazon.com Since I switched to kubuntu 18.04, I have tried to use konqueror on several occasions, but the only thing it has done for me is crash immediately when I try to open anything. Most recently I tried to open the index.html in /usr/share/doc/python2.7/html. I tried to generate an error report, but it said it could not, and I should report the bug here. Just now I opened it to get the version number, I hit home, and it opened https://www.kde.org/ OK for a second, then it crashed. Just now I went to amazon.com, and it crashed. I went in again, and took the attached screen shot. I want to have another browser available, but konqueror does not function as a browser. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 320006] Dolphin crashes while trying to mount HDD
https://bugs.kde.org/show_bug.cgi?id=320006 --- Comment #45 from Rick Alther <alt...@acm.org> --- Been 4 years since I reported my crash in Dolphin, but I'm not able to reproduce it now. Plug USB drive in/out, Dolphin already open/not open, sitting in USB directory when unpluggged. Dolphin handled all those scenarios. I'm currently running: Dolphin 17.0.4.1 KDE Frameworks: 5.44.0 Qt: 5.9.4 Kernel: 4.15.17 Legacy KDE 4.x or Qt 4.x (or even old kernel) bug? -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 398426] konqueror crashes immediately no matter what I do -- it is unusable
https://bugs.kde.org/show_bug.cgi?id=398426 --- Comment #4 from Rick Graves --- I'm back from my travels and can troubleshoot this. BTW, I am having this problem on my residence desktop. A few days ago, the hard drive died on my office desktop. I installed kubuntu 18.04 on a replacement hard drive. I installed konqueror and tried to load it, and yes it crashed instantly. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 398426] konqueror crashes immediately no matter what I do -- it is unusable
https://bugs.kde.org/show_bug.cgi?id=398426 --- Comment #1 from Rick Graves --- On my laptop, konqueror is working OK -- I am using it now. In Help About, konqueror says version 5.0.97. It was installed from ubuntu packages konqueror amd64 4:17.12.3-0ubuntu1 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 399128] New: Trying to view folders on SanDisk sansa clip+ gives error code 150 and asks for bug report
https://bugs.kde.org/show_bug.cgi?id=399128 Bug ID: 399128 Summary: Trying to view folders on SanDisk sansa clip+ gives error code 150 and asks for bug report Product: dolphin Version: 18.04.1 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: panels: folders Assignee: dolphin-bugs-n...@kde.org Reporter: rjroads...@yahoo.com Target Milestone: --- Created attachment 115257 --> https://bugs.kde.org/attachment.cgi?id=115257=edit Screen shot on SanDisk sansa clip+ error SUMMARY STEPS TO REPRODUCE 1. Attach SanDisk sansa clip+ (shows as folder) 2. Try to expand folder 3. OBSERVED RESULT Error 150 appears EXPECTED RESULT SOFTWARE VERSIONS (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.
[konqueror] [Bug 398426] konqueror crashes immediately no matter what I do -- it is unusable
https://bugs.kde.org/show_bug.cgi?id=398426 --- Comment #3 from Rick Graves --- > Are you using the same distribution on both? Yes, kubuntu 18.04 Konq always/only crashes on my desktop and is working on my laptop. I am traveling, and I will get back to my desktop on October 31st. We can experiment then. (It is OK to put this on hold until then.) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 399128] Trying to view folders on SanDisk sansa clip+ gives error code 150 and asks for bug report; changed mode on player to MSC now it sees folders but not music files
https://bugs.kde.org/show_bug.cgi?id=399128 Rick Jones changed: What|Removed |Added Summary|Trying to view folders on |Trying to view folders on |SanDisk sansa clip+ gives |SanDisk sansa clip+ gives |error code 150 and asks for |error code 150 and asks for |bug report |bug report; changed mode on ||player to MSC now it sees ||folders but not music files -- You are receiving this mail because: You are watching all bug changes.
[calligrasheets] [Bug 108019] After upgrade, date format (dd-mon-yyyy) is missing
https://bugs.kde.org/show_bug.cgi?id=108019 --- Comment #5 from Rick Wagner --- Andrew, I am not currently using Calligra Sheets. However, a quick look still shows the formatting as not an option. I do note that there is a (grayed out) "Custom Format" option, which may allow for this formatting. Since I am no longer using this feature, and there appear to be no other requests, this could probably be closed as not interested. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 419951] New: dh_view.html missing
https://bugs.kde.org/show_bug.cgi?id=419951 Bug ID: 419951 Summary: dh_view.html missing Product: valgrind Version: 3.15 SVN Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: dhat Assignee: jsew...@acm.org Reporter: rstan...@rsiny.com Target Milestone: --- SUMMARY Installation or re-installation of valgrind through apt-get, does not include dh_view.html, nor is it created when valgrind run as: "valgrind --tool=dhat ./app" Searched for missing file unsuccessfully through the entire systems, not just in the directory indicated. "/usr/libexec/valgrind/" directory was not created. STEPS TO REPRODUCE 1. Install valgrind through apt-get 2. Run as "valgrind --tool=dhat ./app" 3. Output file created but cannot run dh_view.html OBSERVED RESULT Cannot be run, nor dh_view.html can be found EXPECTED RESULT dh_view,html can be run SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION version reported as: valgrind-3.15.0 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 419951] dh_view.html missing
https://bugs.kde.org/show_bug.cgi?id=419951 Rick Stanley changed: What|Removed |Added CC||rstan...@rsiny.com -- You are receiving this mail because: You are watching all bug changes.
