[okular] [Bug 405507] New: Bookmark Tab Not refreshing
https://bugs.kde.org/show_bug.cgi?id=405507 Bug ID: 405507 Summary: Bookmark Tab Not refreshing Product: okular Version: unspecified Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: shooterb...@gmail.com Target Milestone: --- SUMMARY On Windows, When a bookmark is created with CTRL+b, the bookmarks tab on the left pane does not display the update. The update on the left pane only displays once Okular is restarted or the "Current Document Only" ribbon on the bottom left is clicked. STEPS TO REPRODUCE 1. Open pdf + click on bookmarks on the left pane 2. Go to page 3. Press CTRL+b OBSERVED RESULT The bookmarks pane does not update with the new bookmarks. EXPECTED RESULT The bookmarks pane should update with the new bookmarks. SOFTWARE/OS VERSIONS Windows: 10 ADDITIONAL INFORMATION Okular from the nightly windows build tested. Build #335 (Feb 14, 2019 6:07:00 PM) -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 465869] New: Unable to add Google drive via "KDE System Setting" or via "Dolphin File Manager"
https://bugs.kde.org/show_bug.cgi?id=465869 Bug ID: 465869 Summary: Unable to add Google drive via "KDE System Setting" or via "Dolphin File Manager" Classification: I don't know Product: kde Version: unspecified Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: bret.gr...@hotmail.com Target Milestone: --- SUMMARY *** Hello, attempting to add Google Drive to a new Garuda Linux install. I have used Garuda before and had no issues adding Google Drive. This makes me think there might be a KDE bug since there are no Online Accounts choices showing. *** STEPS TO REPRODUCE 1. Open KDE System Settings 2. Select "Online Accounts" 3. OBSERVED RESULT Opens blank window. Clicking on the "+ Add New Account" bar at lower right results in another blank window. FYI: Attempting to add a new account via Dolphin File Manager, same exact results as above. EXPECTED RESULT Was hoping to see a choice to add a Google Drive account. SOFTWARE/OS VERSIONS Garuda LXQT-Kwin Linux/KDE Plasma: Version 5.27.0 (available in About System) ADDITIONAL INFORMATION I have tried various "fixes" such as installing kio-drive, k-accounts, etc and having no luck. Admittedly I am a total greenhorn but I am trying the best I can. Reaching out to the experts here. Thank you all. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 465869] Unable to add Google account
https://bugs.kde.org/show_bug.cgi?id=465869 --- Comment #2 from Bret Green --- (In reply to Nate Graham from comment #1) > Can mostly reproduce. For me it's even worse: nothing happens at all when I > click on the Google item in the KAccounts KCM. Yikes. Thank you for the follow-up. Still looking into this weirdness : ) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408583] New: Loading clips never completes
https://bugs.kde.org/show_bug.cgi?id=408583 Bug ID: 408583 Summary: Loading clips never completes Product: kdenlive Version: 19.04.1 Platform: MS Windows OS: other Status: REPORTED Severity: major Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: clon...@gmail.com Target Milestone: --- Created attachment 120798 --> https://bugs.kde.org/attachment.cgi?id=120798&action=edit Screen capture of my project with the "loading clips" dialog and bug report dialog box. SUMMARY The loading project dialog box hangs at "Loading clips". Although it shows an animating progress bar, it never finishes loading the clips. (It's not a big project, and I've been waiting about an hour.) However, all other parts of the application appear to be working ok. The application does not seem to have crashed. STEPS TO REPRODUCE 1. Go to file, Open Recent 2. Open my project 3. Bam! OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: 19.04.1 using Windows 10 ADDITIONAL INFORMATION Sorry, that's all I've got -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 401337] New: Kmail crashes on hitting reply to email
https://bugs.kde.org/show_bug.cgi?id=401337 Bug ID: 401337 Summary: Kmail crashes on hitting reply to email Product: kontact Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: b...@savinogroup.com Target Milestone: --- Application: kontact (5.9.90 rc) Qt Version: 5.11.2 Frameworks Version: 5.53.0 Operating System: Linux 4.15.0-39-generic x86_64 Distribution: KDE neon Developer Edition -- Information about the crash: - What I was doing when the application crashed: Trying to reply to an email. - Unusual behavior I noticed: After the bug report helper installed Backtrace, opened kmail, all 4 replies open, tried to close the first and plasma crashed (pannel is gone). The crash can be reproduced every time. -- 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 0x7fb68e917b80 (LWP 12455))] Thread 33 (Thread 0x7fb61d7fa700 (LWP 14456)): #0 0x7fb686bbeed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7fb61d7f9780, expected=0, futex_word=0x7fb61d7f9968) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 __pthread_cond_wait_common (abstime=0x7fb61d7f9820, mutex=0x7fb61d7f9918, cond=0x7fb61d7f9940) at pthread_cond_wait.c:533 #2 __pthread_cond_timedwait (cond=0x7fb61d7f9940, mutex=0x7fb61d7f9918, abstime=0x7fb61d7f9820) at pthread_cond_wait.c:667 #3 0x7fb67c24c917 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7fb67c24ebf7 in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7fb67c24ece2 in base::WaitableEvent::TimedWait(base::TimeDelta const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7fb67c253d61 in base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7fb67c2550ff in base::internal::SchedulerWorker::Thread::ThreadMain() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7fb67c25dff1 in base::(anonymous namespace)::ThreadFunc(void*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7fb686bb86db in start_thread (arg=0x7fb61d7fa700) at pthread_create.c:463 #10 0x7fb68b2b388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 32 (Thread 0x7fb51a2f7700 (LWP 12556)): #0 0x7fb68b2a20b4 in __GI___libc_read (fd=130, buf=0x7fb51a2f6810, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7fb684d30cd0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb684cec027 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb684cec4e0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fb684cec64c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fb68bdf904b in QEventDispatcherGlib::processEvents (this=0x7fb5dc00bfd0, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #6 0x7fb68bd9d30a in QEventLoop::exec (this=this@entry=0x7fb51a2f6a20, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #7 0x7fb68bbc8bba in QThread::exec (this=) at thread/qthread.cpp:525 #8 0x7fb68bbd3adb in QThreadPrivate::start (arg=0x559377048900) at thread/qthread_unix.cpp:367 #9 0x7fb686bb86db in start_thread (arg=0x7fb51a2f7700) at pthread_create.c:463 #10 0x7fb68b2b388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 31 (Thread 0x7fb51d27a700 (LWP 12545)): #0 0x7fb68b2a6bf9 in __GI___poll (fds=0x7fb5400060e0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fb684cec539 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb684cec64c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb68bdf904b in QEventDispatcherGlib::processEvents (this=0x7fb540003980, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7fb68bd9d30a in QEventLoop::exec (this=this@entry=0x7fb51d279a20, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #5 0x7fb68bbc8bba in QThread::exec (this=) at thread/qthread.cpp:525 #6 0x7fb68bbd3adb in QThreadPrivate::start (arg=0x559372f46240) at thread/qthread_unix.cpp:367 #7 0x7fb686bb86db in start_thread (arg=0x7fb51d27a700) at pthread_create.c:463 #8 0x7fb68b2b388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 30 (Thread 0x7fb51da7b700 (LWP 12544)): #0 0x7fb684d32049 in g_mutex_lock () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fb684cebf5c in g_main_context_check () from
[kwin] [Bug 399778] Special Application/Window Settings not applying
https://bugs.kde.org/show_bug.cgi?id=399778 Bret J. Savino changed: What|Removed |Added CC||b...@savinogroup.com --- Comment #10 from Bret J. Savino --- Happening on all 3 of my Neon boxes. Set a window or application rule, click ok, nothing in the list of rules. You can set it manually from the systemsettings>windowsettings>windowrules with the same result. I have not tried exporting/importing. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399778] Special Application/Window Settings not applying
https://bugs.kde.org/show_bug.cgi?id=399778 Bret J. Savino changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #11 from Bret J. Savino --- Updated through 1 AM Mountain time Oct 20th 2018 have brought back the list of rules in Window rules and appear to be functioning. Rules can be added manually or ALT+F3 > more actions > Special Window Settings. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 401337] Kmail crashes on hitting reply to email
https://bugs.kde.org/show_bug.cgi?id=401337 --- Comment #4 from Bret J. Savino --- Same here (on the new mail crash). I wish i could understand your patch, mine was Kubuntu 18.10 on a separate partition. The new mesa looks awesome on an external. Kmail has such potential, this is the second major bug in as many months with Neon. Not complaining but maybe I juwt cant hack Neon. -- You are receiving this mail because: You are watching all bug changes.
