[kdelibs] [Bug 258890] KDE should optionally show warning before running executables.
https://bugs.kde.org/show_bug.cgi?id=258890 Alan Dacey Sr. changed: What|Removed |Added CC||gro...@ajinfosearch.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 409426] New: Make ability to run scripts more obvious
https://bugs.kde.org/show_bug.cgi?id=409426 Bug ID: 409426 Summary: Make ability to run scripts more obvious Product: dolphin Version: 18.12.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: gro...@ajinfosearch.com CC: elvis.angelac...@kde.org Target Milestone: --- SUMMARY Did a new install of Kubuntu 19.04 to use as a mobile workstation. I have shell scripts in Dropbox that I need for my work. When I tried to execute the scripts from my new laptop they opened in kate instead of doing what I needed them to do. They've been working for quite a while on my main workstation running Kubuntu 18.04 LTS I finally found that I needed to click the checkbox under Control--> Configure Dolphin --> General --> Confirmations --> under "Ask for permission..." section --> "Executing scripts or desktop files" This is most likely never discoverable to the average user. After I checked the correct checkbox a dialog came up asking me what I wanted to do. This dialog should appear whether or not the checkbox is checked. STEPS TO REPRODUCE 1. Install new OS 2. Click on an existing shell script 3. Opens in kate instead of running OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 19.04 KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwidgetsaddons] [Bug 409427] New: Folder View widget can not drop files into folders on default settings
https://bugs.kde.org/show_bug.cgi?id=409427 Bug ID: 409427 Summary: Folder View widget can not drop files into folders on default settings Product: frameworks-kwidgetsaddons Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: cf...@kde.org Reporter: gro...@ajinfosearch.com CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY New install of Kubuntu 19.04. Added the folder view widget to my desktop but could not drop files into the folders shown. Files dropped into the root folder that the widget was showing (such as ~/Documents/Work). Had to open Dophin's settings and click the "Open folders during drag operations" checkbox under Navigation to get it to work. This is a very odd default setting since everybody expects drag and drop to work everywhere. STEPS TO REPRODUCE 1. Install new OS 2. Add a Folder View widget to your desktop 3. Drag and drop a file into a folder in the widget 4. File drops into the widget's root folder and not where you want it to drop. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 19.04 KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 409427] Folder View widget can not drop files into folders on default settings
https://bugs.kde.org/show_bug.cgi?id=409427 --- Comment #2 from Alan Dacey Sr. --- There are no settings in the folder view widget that effect this behavior. So in search of trying to find a solution I thought that maybe some code is shared between the widget and dolphin. Seems I may be correct that changing how dolphin works fixes the problem in some bit of shared code. Perhaps my initial report is a case of too much information. Feel free to ignore all dolphin parts of this. The ability to drop files into folders in the widget is still broken with the default settings. That's not changed and also why I submitted this bug report. If you need anything else just let me know. --Thanks -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 404914] New: Dolphin crashed with breadcumb dropdown visible and moving files
https://bugs.kde.org/show_bug.cgi?id=404914 Bug ID: 404914 Summary: Dolphin crashed with breadcumb dropdown visible and moving files Product: dolphin Version: 17.12.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: gro...@ajinfosearch.com CC: elvis.angelac...@kde.org Target Milestone: --- Application: dolphin (17.12.3) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 4.15.0-45-generic x86_64 Distribution: Ubuntu 18.04.2 LTS -- Information about the crash: - What I was doing when the application crashed: Was about to move files from one folder to another in split view mode. Accidentally hovered over the dropdown folder menu (breadcrumb ??) and made it show all the subfolders. It partially covered the folder I was about to move the files to. With all the files still selected, moved away from the dropdown(it did not dissapear), tried to hover over the folder but hovered over the dropdown instead, moved the mouse away, and carefully hovered only over the folder. Let go of the mouse button and used the mouse to select the ' Move Here' option. Then Dolphin crashed. -- Backtrace: Application: Dolphin (dolphin), signal: Bus error Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7feab0d006c0 (LWP 25056))] Thread 5 (Thread 0x7faa59ffb700 (LWP 4223)): #0 0x7feaa565a9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x5574a9e118b0) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7feaa565a9f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x5574a9e11860, cond=0x5574a9e11888) at pthread_cond_wait.c:502 #2 0x7feaa565a9f3 in __pthread_cond_wait (cond=0x5574a9e11888, mutex=0x5574a9e11860) at pthread_cond_wait.c:655 #3 0x7feaaa56559b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7feaaa55dc0b in QSemaphore::acquire(int) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7faa7b4b380c in () at /usr/lib/x86_64-linux-gnu/qt5/plugins/texttospeech/libqttexttospeech_flite.so #6 0x7feaaa56416d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7feaa56546db in start_thread (arg=0x7faa59ffb700) at pthread_create.c:463 #8 0x7feab059488f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7fea86eb0700 (LWP 25062)): #0 0x7feab0587bf9 in __GI___poll (fds=0x7fea800049b0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7feaa34e3539 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7feaa34e364c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7feaaa79b90b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7feaaa7409ea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7feaaa55f22a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7feaaa56416d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7feaa56546db in start_thread (arg=0x7fea86eb0700) at pthread_create.c:463 #8 0x7feab059488f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7fea93455700 (LWP 25061)): #0 0x7feab05830b4 in __GI___libc_read (fd=7, buf=0x7fea93454b60, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7feaa3527cd0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7feaa34e3027 in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7feaa34e34e0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7feaa34e364c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7feaaa79b90b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7feaaa7409ea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7feaaa55f22a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7feaaac18d45 in () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #9 0x7feaaa56416d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7feaa56546db in start_thread (arg=0x7fea93455700) at pthread_create.c:463 #11 0x7feab059488f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7fea99bcf700 (LWP 25059)): #0 0x7feab0587bf9 in __GI___poll (fds=0x7fea99bceca8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7feaa2e24747 in () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7feaa2e2636a in xcb_wait_for_event () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7fea9c97c2a9 in
[dolphin] [Bug 395723] The median line width of icons view mode is the same as the small width
https://bugs.kde.org/show_bug.cgi?id=395723 Alan Dacey Sr. changed: What|Removed |Added CC||gro...@ajinfosearch.com --- Comment #1 from Alan Dacey Sr. --- Same bug here. Using Dolphin 17.12.3, KDE 5.44.0, Plasma 5.12.7 in Kubuntu 18.04. The spacing is the same for Small, Medium, and Large. Huge spacing is working but the rest seem to be set to large no matter which of the 3 width options you choose in View Modes. I noticed this in updates installed on March 21st or 22nd. I couldn't find any updates to dolphin in /var/log/dpkg.log -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 395723] The median line width of icons view mode is the same as the small width
https://bugs.kde.org/show_bug.cgi?id=395723 --- Comment #2 from Alan Dacey Sr. --- Update: I see this happening only in certain folders. I renamed then re-created a folder I use every day and the spacing issue disappeared. I didn't see any difference in the properties of either folder. Will save old folder is needed. -- You are receiving this mail because: You are watching all bug changes.
[krename] [Bug 389926] New: Missing Service Menus
https://bugs.kde.org/show_bug.cgi?id=389926 Bug ID: 389926 Summary: Missing Service Menus Product: krename Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: heire...@exherbo.org Reporter: gro...@ajinfosearch.com Target Milestone: --- Created attachment 110360 --> https://bugs.kde.org/attachment.cgi?id=110360&action=edit Service menu for file only rename I installed krename 4.0.9 on a new install of Kubuntu 17.10. There are no service menus included with this release. I'd like to have the option to right click on files and rename them. I copied the old service menus from an old Kubuntu 14.04 install and they work as expected. The missing files are attached. -- You are receiving this mail because: You are watching all bug changes.
[krename] [Bug 389926] Missing Service Menus
https://bugs.kde.org/show_bug.cgi?id=389926 --- Comment #1 from Alan Dacey Sr. --- Created attachment 110361 --> https://bugs.kde.org/attachment.cgi?id=110361&action=edit Service menu for folders -- You are receiving this mail because: You are watching all bug changes.
[krename] [Bug 389926] Missing Service Menus
https://bugs.kde.org/show_bug.cgi?id=389926 --- Comment #3 from Alan Dacey Sr. --- The service menus are in the wrong place, at least for Kubuntu and KDE 5. That folder is for KDE 4. I do indeed have the service menus in /usr/share/kde4/services/ServiceMenus but they need to be in /usr/share/kservices5/ServiceMenus for them to work. I moved my service menus out of the kservices5 folder and Krename did not show up in dolphin under Actions after right-clicking. I moved them back and it re-appeared. So I guess my bug report should read to put them in /usr/share/kservices5/ServiceMenus. -- You are receiving this mail because: You are watching all bug changes.
[krename] [Bug 389926] Missing Service Menus
https://bugs.kde.org/show_bug.cgi?id=389926 --- Comment #5 from Alan Dacey Sr. --- Thanks, Heiko! -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 377937] New: Keypad enter key is not recognized
https://bugs.kde.org/show_bug.cgi?id=377937 Bug ID: 377937 Summary: Keypad enter key is not recognized Product: Spectacle Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: gro...@ajinfosearch.com Target Milestone: --- in Spectacle, version Version 16.04.3 - So Much For Subtlety, the enter key on the keypad does nothing after selecting a rectangular region. A user must use the main enter key in order to save the screenshot. Please add support for both enter keys. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 377941] New: Would like to rename devices
https://bugs.kde.org/show_bug.cgi?id=377941 Bug ID: 377941 Summary: Would like to rename devices Product: kdeconnect Version: 1.0 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: gro...@ajinfosearch.com Target Milestone: --- Using Kdeconnect, 1.0.3-0ubuntu1~ubuntu16.10~ppa1 Would like the ability to rename devices. Currently my phone shows up as "Samsung SM-N910T3" which really doesn't mean anything to me. It's also not obvious which phone is which when there are multiple phones in the household. I would like to be able to rename them to something like "My phone" and "My wife's phone" -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 377941] Would like to rename devices
https://bugs.kde.org/show_bug.cgi?id=377941 --- Comment #2 from Alan Dacey Sr. --- Created attachment 104764 --> https://bugs.kde.org/attachment.cgi?id=104764&action=edit How can I tap on my computer? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 377941] Would like to rename devices
https://bugs.kde.org/show_bug.cgi?id=377941 --- Comment #4 from Alan Dacey Sr. --- Ah, I see now. I renamed the device on my phone and after a reboot the new name showed on my computer. I was looking for a way to rename the phone device from my computer. I found how to rename the computer from the computer. This isn't in the documentation, at least I don't see it. IMHO this needs fixing. How do I get involved with the KDE documentation team? Thanks for your help by the way, Albert! -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 378256] New: Kontack crashes when closing
https://bugs.kde.org/show_bug.cgi?id=378256 Bug ID: 378256 Summary: Kontack crashes when closing Product: kontact Version: 5.2.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: gro...@ajinfosearch.com Target Milestone: --- Application: kontact (5.2.3) Qt Version: 5.6.1 Frameworks Version: 5.28.0 Operating System: Linux 4.8.0-37-generic x86_64 Distribution: Ubuntu 16.10 -- Information about the crash: - What I was doing when the application crashed: Clicked on File --> Exit Kontact usually crashes whenI close it. Version 5.2.3 Kubuntu 16.10 -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa866ff9900 (LWP 25269))] Thread 24 (Thread 0x7fa7d8af0700 (LWP 1571)): #0 0x7fa87d1c70bd in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fa8769319d6 in g_main_context_poll (priority=, n_fds=1, fds=0x7fa7bc0022e0, timeout=, context=0x7fa7bc0020d0) at ././glib/gmain.c:4228 #2 0x7fa8769319d6 in g_main_context_iterate (context=context@entry=0x7fa7bc0020d0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ././glib/gmain.c:3924 #3 0x7fa876931aec in g_main_context_iteration (context=0x7fa7bc0020d0, may_block=1) at ././glib/gmain.c:3990 #4 0x7fa87dd0c4ab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fa87dcb40fa in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fa87dad9d43 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fa87dadec68 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fa87715e6ca in start_thread (arg=0x7fa7d8af0700) at pthread_create.c:333 #9 0x7fa87d1d30af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 23 (Thread 0x7fa7d92f1700 (LWP 1569)): #0 0x7fa87d1c70bd in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fa8769319d6 in g_main_context_poll (priority=, n_fds=1, fds=0x7fa7c8002e70, timeout=, context=0x7fa7c8003ca0) at ././glib/gmain.c:4228 #2 0x7fa8769319d6 in g_main_context_iterate (context=context@entry=0x7fa7c8003ca0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ././glib/gmain.c:3924 #3 0x7fa876931aec in g_main_context_iteration (context=0x7fa7c8003ca0, may_block=1) at ././glib/gmain.c:3990 #4 0x7fa87dd0c4ab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fa87dcb40fa in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fa87dad9d43 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fa87dadec68 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fa87715e6ca in start_thread (arg=0x7fa7d92f1700) at pthread_create.c:333 #9 0x7fa87d1d30af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 22 (Thread 0x7fa7db735700 (LWP 1567)): #0 0x7fa87d1c70bd in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fa8769319d6 in g_main_context_poll (priority=, n_fds=1, fds=0x7fa7d4005a80, timeout=, context=0x7fa7d4058550) at ././glib/gmain.c:4228 #2 0x7fa8769319d6 in g_main_context_iterate (context=context@entry=0x7fa7d4058550, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ././glib/gmain.c:3924 #3 0x7fa876931aec in g_main_context_iteration (context=0x7fa7d4058550, may_block=1) at ././glib/gmain.c:3990 #4 0x7fa87dd0c4ab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fa87dcb40fa in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fa87dad9d43 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fa87dadec68 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fa87715e6ca in start_thread (arg=0x7fa7db735700) at pthread_create.c:333 #9 0x7fa87d1d30af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 21 (Thread 0x7fa7da733700 (LWP 1565)): #0 0x7fa876977029 in g_mutex_lock (mutex=mutex@entry=0x7fa7d0003ca0) at ././glib/gthread-posix.c:1336 #1 0x7fa876931ad8 in g_main_context_iteration (context=0x7fa7d0003ca0, may_block=1) at ././glib/gmain.c:3989 #2 0x7fa87dd0c4ab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fa87dcb40fa in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fa87dad9d43 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fa87dadec68 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fa87715e6ca in start_t
[kontact] [Bug 379331] New: Kontact sometimes crashes when going to Akregator
https://bugs.kde.org/show_bug.cgi?id=379331 Bug ID: 379331 Summary: Kontact sometimes crashes when going to Akregator Product: kontact Version: 5.2.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: gro...@ajinfosearch.com Target Milestone: --- Application: kontact (5.2.3) Qt Version: 5.6.1 Frameworks Version: 5.28.0 Operating System: Linux 4.8.0-37-generic x86_64 Distribution: Ubuntu 16.10 -- Information about the crash: - What I was doing when the application crashed: Finished reading my mail. Wanted to read my news feeds. Clicked on the Akregator button in the Navigator toolbar and Kontact crashed. This happens from time to time but this is the first time I got a useful backtrace. KDE Plasma 5.8.5 Qt 5.6.1 NVIDIA Driver Version: 378.13 More information on request The crash can be reproduced sometimes. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f463a218900 (LWP 2218))] Thread 29 (Thread 0x7f453affd700 (LWP 10893)): #0 0x7f46503e60bd in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f4649b509d6 in g_main_context_poll (priority=, n_fds=1, fds=0x7f45580018c0, timeout=, context=0x7f45580037a0) at ././glib/gmain.c:4228 #2 0x7f4649b509d6 in g_main_context_iterate (context=context@entry=0x7f45580037a0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ././glib/gmain.c:3924 #3 0x7f4649b50aec in g_main_context_iteration (context=0x7f45580037a0, may_block=1) at ././glib/gmain.c:3990 #4 0x7f4650f2b4ab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f4650ed30fa in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f4650cf8d43 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f4650cfdc68 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f464a37d6ca in start_thread (arg=0x7f453affd700) at pthread_create.c:333 #9 0x7f46503f20af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 28 (Thread 0x7f453b7fe700 (LWP 10891)): #0 0x7f46503e60bd in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f4649b509d6 in g_main_context_poll (priority=, n_fds=1, fds=0x7f4594002270, timeout=, context=0x7f4594003ca0) at ././glib/gmain.c:4228 #2 0x7f4649b509d6 in g_main_context_iterate (context=context@entry=0x7f4594003ca0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ././glib/gmain.c:3924 #3 0x7f4649b50aec in g_main_context_iteration (context=0x7f4594003ca0, may_block=1) at ././glib/gmain.c:3990 #4 0x7f4650f2b4ab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f4650ed30fa in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f4650cf8d43 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f4650cfdc68 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f464a37d6ca in start_thread (arg=0x7f453b7fe700) at pthread_create.c:333 #9 0x7f46503f20af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 27 (Thread 0x7f453bfff700 (LWP 10889)): #0 0x7f4650cf5d99 in QMutex::unlock() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7f4650f2ab51 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f4649b4fed9 in g_main_context_prepare (context=context@entry=0x7f4598000990, priority=priority@entry=0x7f453bffeb80) at ././glib/gmain.c:3501 #3 0x7f4649b508fb in g_main_context_iterate (context=context@entry=0x7f4598000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ././glib/gmain.c:3909 #4 0x7f4649b50aec in g_main_context_iteration (context=0x7f4598000990, may_block=1) at ././glib/gmain.c:3990 #5 0x7f4650f2b4ab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f4650ed30fa in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f4650cf8d43 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f4650cfdc68 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f464a37d6ca in start_thread (arg=0x7f453bfff700) at pthread_create.c:333 #10 0x7f46503f20af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 26 (Thread 0x7f4557fff700 (LWP 8954)): #0 0x7f46503e1c8d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f4649b94c80 in read (__nbytes=16, __buf=0x7f4557ffeaa0, __fd=) at /usr/include/x86_64-linux-gnu/bits/unistd.h:44 #2 0x7f4649b94c80 in g_wakeup_acknowledge (wakeup=0x7f45a000
[kde] [Bug 493857] New: initramfs fails on upgrade
https://bugs.kde.org/show_bug.cgi?id=493857 Bug ID: 493857 Summary: initramfs fails on upgrade Classification: I don't know Product: kde Version: unspecified Platform: Kubuntu OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: gro...@ajinfosearch.com Target Milestone: --- SUMMARY After upgrading to 24.04 initramfs failed to install properly. this makes the system unbootalbe. STEPS TO REPRODUCE 1. click on the upgrade prompt 2. Wait for the upgrade to complete 3. Get a non-bootable OS OBSERVED RESULT I upgraded my computer while and got an message that initramfs installed with an error code of 1 and my system may not work, It was not able to boot. initramfs is broken for and upgrade from 22.04 to 24.04. EXPECTED RESULT the upgrade to 24.04 works correctly and I am able to restart my computer. SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
