[kopete] [Bug 272855] kopete fails to connect after network connection is switched to vpnc
https://bugs.kde.org/show_bug.cgi?id=272855 Phil changed: What|Removed |Added CC||phd...@gmail.com --- Comment #3 from Phil --- I am using Linux Mint 17.3 KDE. Kernel: 3.19.0-32-generic i686 (32 bit gcc: 4.8.2) Desktop: KDE Plasma 4.14.2 (Qt 4.8.6) Distro: Linux Mint 17.3 Rosa If I am connected to my Internet provider (ISP), without using a VPN provider's connection, Kopete, KDE-Telepathy, Kmail, Jitsi, and others, etc... will work perfectly, and fast, and connect to all my messaging accounts (xmpp, sip). As soon as I connect to a VPN server location using the openVPN protocol to a VPN provider, like "vpnbook", or "vpngate", they all stop working, and will not login to the various messenger accounts. But, I can connect using "qTox" no problem? I tried what Alexey Neyman 2012-05-19 12:14:30 EDT suggested, "Found where my problem was: In KNetworkManager, the open VPN configuration. In IPv4 tab, select "Routes" from the drop list and check "Use only for resources on this connection" box." That works for the messaging clients, but then the VPN connection does not work properly, which makes that option useless. I tested this using "ipleak.net", before and after making the changes "Alexey" tried. This is a problem that I would really like to know how to solve. Perhaps there is some other settings in the Network Manager, or the VPN Connection, or somewhere else, that would make the messaging clients work (connect) while using a VPN server connection? If so, could anyone tell me what they are, and how to implement them, please? Thank you very much, Phil -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 365044] New: Kopete, or Telepathy, will not connect to messaging accounts when a VPN is used.
https://bugs.kde.org/show_bug.cgi?id=365044 Bug ID: 365044 Summary: Kopete, or Telepathy, will not connect to messaging accounts when a VPN is used. Product: telepathy Version: unspecified Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: kde-telepathy-b...@kde.org Reporter: phd...@gmail.com I am using Linux Mint 17.3 KDE. Kernel: 3.19.0-32-generic i686 (32 bit gcc: 4.8.2) Desktop: KDE Plasma 4.14.2 (Qt 4.8.6) Distro: Linux Mint 17.3 Rosa If I am connected to my Internet provider (ISP), without using a VPN provider's connection, Kopete, KDE-Telepathy, Kmail, Jitsi, and others, etc... will work perfectly, and fast, and connect to all my messaging accounts (xmpp, sip). As soon as I connect to a VPN server location using the openVPN protocol to a VPN provider, like "vpnbook", or "vpngate", they all stop working, and will not login (will not connect) to the various messenger accounts. But, I can connect using "qTox" no problem? I tried what Alexey Neyman 2012-05-19 12:14:30 EDT suggested, "Found where my problem was: In KNetworkManager, the open VPN configuration. In IPv4 tab, select "Routes" from the drop list and check "Use only for resources on this connection" box." That works for the messaging clients, but then the VPN connection does not work properly, which makes that option useless. I tested this using "ipleak.net", before and after making the changes "Alexey" tried. This is a problem that I would really like to know how to solve. Perhaps there is some other settings in the Network Manager, or the VPN Connection, perhaps in "Kopete" or "Telepathy", or somewhere else, that would make the messaging clients work (connect) while using a VPN server connection? If so, could anyone tell me what they are, and how to implement them, please? My Kmail has problems as well when connected to a VPN. Thank you very much, Phil Reproducible: Always Steps to Reproduce: 1. Connect to a VPN provider's server location 2. Bring up "Kopete", or "Telepathy", and they will not connect, will not login, to the various messaging accounts. 3. Disconnect from the VPN, and the messaging clients have no problem connecting and logging in to the accounts. Actual Results: the same thing Expected Results: I expect my messaging clients, KDE (Kopete or Telepathy), or any other messaging clients, to work when I connect to a VPN server location. Using a VPN is practically a necessity today for privacy and security. KDE has great VPN options, but that should not stop other KDE program from functioning. My Kmail has problems as well when connected to a VPN. -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 365044] Kopete, or Telepathy, will not connect to messaging accounts when a VPN is used.
https://bugs.kde.org/show_bug.cgi?id=365044 Phil changed: What|Removed |Added CC||phd...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 355410] the scroll speed of QML scroll area is too slow with Libinput
https://bugs.kde.org/show_bug.cgi?id=355410 Phil changed: What|Removed |Added CC||phils...@phlexo.com -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 344392] Can't burn BD50 ISO image - Seems not to be a usable image
https://bugs.kde.org/show_bug.cgi?id=344392 Phil changed: What|Removed |Added CC||phd...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 344392] Can't burn BD50 ISO image - Seems not to be a usable image
https://bugs.kde.org/show_bug.cgi?id=344392 --- Comment #26 from Phil --- Hi Leslie Zhai, Thomas Schmitt, I have been reading this post. "K3b" is the most loved CD/DVD/Blu-Ray application for Linux Mint users, including me. If there are updates and or upgrades to this wonderful application, how can Linux Mint users install it on 32-bit and 64-bit systems on Linux Mint versions 17.x based on Ubuntu 14.04 or Linux Mint version 18 based on Ubuntu 16.04? Are there any easy to install and use Linux ".deb" files, or a PPA perhaps, that we can use to install these upgrades? Or, do we have to compile it, and if so, could you please detail those instructions? Also, since you are actively updating "K3b", I have another feature and or request. Can you do this, or should I create another "KDE bug - feature" request for the modification and or update to the "checksum" aspect of burning and or verifying ".iso" images to include a more current "sha256" checksum value, and maybe an option (auto or not) for comparing that to an existing "sha256sum.txt" file that is in the same folder (directory). Thank you, Phil D. KDE User: phd...@gmail.com Linux Mint forum user: phd21 phd21m...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 360184] k3b should offer option to select either md5 sum or sha256 when loading dvd iso
https://bugs.kde.org/show_bug.cgi?id=360184 Phil changed: What|Removed |Added CC||phd...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 360184] k3b should offer option to select either md5 sum or sha256 when loading dvd iso
https://bugs.kde.org/show_bug.cgi?id=360184 --- Comment #1 from Phil --- Dear KDE "K3b" developers and maintainers, +1 for the request for the modification and or update to the "checksum" aspect of burning and or verifying ".iso" images to include a more current "sha256" checksum value, and maybe an option (auto or not) for comparing that to an existing "sha256sum.txt" file that is in the same folder (directory). "K3b" is the most loved CD/DVD/Blu-Ray application for Linux Mint users, including me. If there are updates and or upgrades to this wonderful application, how can Linux Mint users install it on 32-bit and 64-bit systems on Linux Mint versions 17.x based on Ubuntu 14.04 or Linux Mint version 18 based on Ubuntu 16.04? Are there any easy to install and use Linux ".deb" files, or a PPA perhaps, that we can use to install these upgrades? Or, do we have to compile it, and if so, could you please detail those instructions? Thank you, Phil D. KDE Bug forum User: phd...@gmail.com Linux Mint forum user: phd21 phd21m...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 76115] Hidden files listing option will be good
https://bugs.kde.org/show_bug.cgi?id=76115 Phil changed: What|Removed |Added CC||phd...@gmail.com --- Comment #1 from Phil --- Dear KDE "K3b" developers and maintainers, +1 Please for adding an option to view and or add hidden files when creating discs. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[knemo] [Bug 368706] New: Where is Knemo for Ubuntu 16.04 and Linux Mint 18?
https://bugs.kde.org/show_bug.cgi?id=368706 Bug ID: 368706 Summary: Where is Knemo for Ubuntu 16.04 and Linux Mint 18? Product: knemo Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: general Assignee: jst...@mehercule.net Reporter: phd...@gmail.com Hi, Where is Knemo for Ubuntu 16.04 and Linux Mint 18? This is a great and very handy utility for the system tray panel. I sure would like to have it for use in the new KDE systems, please. If necessary, Is there source code available that we could compile a new version of it? IF so, where and how? Thank you Reproducible: Always Steps to Reproduce: 1. It is not in the repos? 2. 3. Actual Results: missing application Expected Results: to be able to install and use it -- You are receiving this mail because: You are watching all bug changes.
[knemo] [Bug 368706] Where is Knemo for Ubuntu 16.04 and Linux Mint 18?
https://bugs.kde.org/show_bug.cgi?id=368706 Phil changed: What|Removed |Added CC||phd...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 76115] Hidden files listing option will be good
https://bugs.kde.org/show_bug.cgi?id=76115 --- Comment #3 from Phil --- Created attachment 101060 --> https://bugs.kde.org/attachment.cgi?id=101060&action=edit K3b_v2.0.2_showHiddenFiles Hi Leslie, Thankyou for your quick replies. My Bad, I do see the use (show) hidden file option, even on my Linux Mint KDE 17.3 using K3b version 2.0.2. Thank you. :) -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 344392] Can't burn BD50 ISO image - Seems not to be a usable image
https://bugs.kde.org/show_bug.cgi?id=344392 --- Comment #32 from Phil --- (In reply to Thomas Schmitt from comment #29) > Hi, > > Leslie Zhai wrote: > > D-Pointer https://wiki.qt.io/D-Pointer > > Looks like somebody had to work around some consequences of the > decision to use C++. (Oh if only Bjarne Stroustrup had a real life > back in the 1980s !) > > > > headline stating "ISO 9660" > > https://forum.isoft-linux.org/viewtopic.php?f=3&t=47 > > Yep. The "Writing Data Project (virt)" window says "ISO 9660 Filesystem". > But that is not the text i see in k3biso9660imagewritingjob.cpp > "Simulating ISO 9660 Image" and ""Burning ISO 9660 Image". > > Question is where this comes from and how to provide the information > about ImageWritingDialog.foundImageType at that place. > > > Phil wrote: > > should I create another "KDE bug - feature" request > > If i shall join that discussion. i'd need a pointer to the thread > by email: scdbac...@gmx.net > (Google finds me places where people say "xorriso", "libburn", or > "growisofs". But "K3B" yields just too many hits per day.) > > > Have a nice day :) > > Thomas Dear Thomas Schmitt, Thank you for your replies. If I read your comments properly, you seemed to want to join in on this K3b feature request, so here is the link to that KDE Bug feature request: I also forwarded an email to your email address. Bug 360184 - k3b should offer option to select either md5 sum or sha256 when loading dvd iso https://bugs.kde.org/show_bug.cgi?id=360184 You have a nice day as well :-) . Best Regards, Phil -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 360184] k3b should offer option to select either md5 sum or sha256 when loading dvd iso
https://bugs.kde.org/show_bug.cgi?id=360184 --- Comment #4 from Phil --- Dear KDE "K3b" developers and maintainers, Leslie Zhai, Sebastian Trueg, Thomas Schmitt, 1. To all of you, Thank you for working on this great K3b application, and making it even better. 2. It looks like you are using "QT" development for some if not all of this? I do not yet know enough about "QT" to help with that. Although, the link from Thomas regarding the use of "QCryptographicHash::Sha256" (and its variations) look pretty good too me. I don't know if this will help or not, but when I use Linux Mint for evaluating checksum values, I can use the commands below. As far as I know, all Linux distros (and maybe MS Windows too) have the command "sha256sum" already installed. To get the checksum value: Example: sha256sum -b linuxmint-18-kde-32bit.iso Results in: ff8bacc631e7955fc6b0f86c9014ce27aa455e3ee0913de0b2bc6c366b63c693 *linuxmint-18-kde-32bit.iso To verify a checksum of a file with its downloaded checksum file (sha256sum.txt) in the same folder, I can use either of these console terminal commands: Example: sha256sum --check sha256sum.txt or sha256sum --check --ignore-missing sha256sum.txt Results in: linuxmint-18-cinnamon-32bit.iso: OK linuxmint-18-kde-32bit.iso: OK linuxmint-18-mate-32bit.iso: OK linuxmint-18-xfce-32bit.iso: OK 3.) I tried to compile "K3b" from the link below using the "install.txt" instructions, and could not successfully compile it on my Linux Mint KDE 32-bit system. Unfortunately, I only have an ancient 32- bit computer (11+ years old Pentium 4 computer (single core)) which cannot install any version of QT higher than "Qt v5.5" and 32-bit. So, I still need alternate compiling instructions (easy detailed ones please), or I would prefer easy to install ".deb" files, or a PPA. https://github.com/KDE/k3b Best regards to all of you and yours, Phil -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 363048] New: transaction error while updating kio-extras with apper
https://bugs.kde.org/show_bug.cgi?id=363048 Bug ID: 363048 Summary: transaction error while updating kio-extras with apper Product: kio-extras Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: default Assignee: plasma-de...@kde.org Reporter: val...@astro.umontreal.ca Below is the message displayed by apper. Error running transaction: file /usr/lib64/qt5/plugins/kactivitymanagerd_fileitem_linking_plugin.so from install of kio-extras-16.04.0-1.fc23.x86_64 conflicts with file from kactivities-workspace-5.5.0-3.fc23.x86_64 file /usr/lib64/qt5/plugins/kio_activities.so from install of kio-extras-16.04.0-1.fc23.x86_64 conflicts with file from kactivities-workspace-5.5.0-3.fc23.x86_64 file /usr/share/kservices5/kactivitymanagerd_fileitem_linking_plugin.desktop from install of kio-extras-16.04.0-1.fc23.x86_64 conflicts with file from kactivities-workspace-5.5.0-3.fc23.x86_64 Reproducible: Always Steps to Reproduce: 1.Run apper 2.Select to update kio-extras 3.fail and return error message Actual Results: Failed Expected Results: should succeed ! Using fedora 23 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 362768] New: KDevelop crashes after enabling code browsing plugins
https://bugs.kde.org/show_bug.cgi?id=362768 Bug ID: 362768 Summary: KDevelop crashes after enabling code browsing plugins Product: kdevelop Version: 4.7.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: phill.hildskj...@gmail.com Application: kdevelop (4.7.3) KDE Platform Version: 4.14.16 Qt Version: 4.8.7 Operating System: Linux 4.4.0-21-generic x86_64 Distribution: Ubuntu 16.04 LTS -- Information about the crash: - What I was doing when the application crashed: I was working on a Python file. I changed settings to get more code analysis. After saving the new settings, KDevelop crashed when I rested the mouse pointer on a class deinition (I was hoping for an info pop-up). - Custom settings of the application: Settings > Configure KDevelop * Language Support: Code Completion: ticked "Additional information for current item" and set "Detailed completion" to Always * Plugins: selected Class Browser and Code Browser I suspect these plugins, though I could not reproduce. In older KDevelop verions, a number of plugins were causing crashes. The crash can be reproduced sometimes. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb59c7e1940 (LWP 19705))] Thread 12 (Thread 0x7fb57ee7a700 (LWP 19707)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fb596a67e1a in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4 #2 0x7fb596a67e49 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4 #3 0x7fb59535a6fa in start_thread (arg=0x7fb57ee7a700) at pthread_create.c:333 #4 0x7fb598eb9b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 11 (Thread 0x7fb4fda42700 (LWP 19708)): #0 0x7ffd97f759a9 in ?? () #1 0x7ffd97f75cd5 in clock_gettime () #2 0x7fb598ec7fb6 in __GI___clock_gettime (clock_id=clock_id@entry=1, tp=tp@entry=0x7fb4fda419a0) at ../sysdeps/unix/clock_gettime.c:115 #3 0x7fb5995e0625 in do_gettime (frac=, sec=) at tools/qelapsedtimer_unix.cpp:127 #4 qt_gettime () at tools/qelapsedtimer_unix.cpp:144 #5 0x7fb5996c7165 in QTimerInfoList::updateCurrentTime (this=0x7fb4f80030e0) at kernel/qeventdispatcher_unix.cpp:354 #6 QTimerInfoList::timerWait (this=0x7fb4f80030e0, tm=...) at kernel/qeventdispatcher_unix.cpp:460 #7 0x7fb5996c599c in timerSourcePrepareHelper (src=, timeout=0x7fb4fda41a74) at kernel/qeventdispatcher_glib.cpp:143 #8 0x7fb5996c5a65 in timerSourcePrepare (source=, timeout=) at kernel/qeventdispatcher_glib.cpp:176 #9 0x7fb592e948ad in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x7fb592e9524b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x7fb592e9542c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x7fb5996c62ce in QEventDispatcherGlib::processEvents (this=0x7fb4f80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452 #13 0x7fb59969418f in QEventLoop::processEvents (this=this@entry=0x7fb4fda41c40, flags=...) at kernel/qeventloop.cpp:149 #14 0x7fb5996944f5 in QEventLoop::exec (this=this@entry=0x7fb4fda41c40, flags=...) at kernel/qeventloop.cpp:204 #15 0x7fb599583549 in QThread::exec (this=this@entry=0x247fdd0) at thread/qthread.cpp:538 #16 0x7fb599674223 in QInotifyFileSystemWatcherEngine::run (this=0x247fdd0) at io/qfilesystemwatcher_inotify.cpp:265 #17 0x7fb599585e3c in QThreadPrivate::start (arg=0x247fdd0) at thread/qthread_unix.cpp:352 #18 0x7fb59535a6fa in start_thread (arg=0x7fb4fda42700) at pthread_create.c:333 #19 0x7fb598eb9b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 10 (Thread 0x7fb4f7fff700 (LWP 19709)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225 #1 0x7fb599586384 in QWaitConditionPrivate::wait (time=1000, this=0x40019e0) at thread/qwaitcondition_unix.cpp:84 #2 QWaitCondition::wait (this=, mutex=0x40017f0, time=1000) at thread/qwaitcondition_unix.cpp:158 #3 0x7fb597e52ca6 in ?? () from /usr/lib/libkdevplatformlanguage.so.8 #4 0x7fb599585e3c in QThreadPrivate::start (arg=0x40017d0) at thread/qthread_unix.cpp:352 #5 0x7fb59535a6fa in start_thread (arg=0x7fb4f7fff700) at pthread_create.c:333 #6 0x7fb598eb9b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 9 (Thread 0x7fb4ed6fa700 (LWP 19710)): #0 __libc_disable_asynccancel () at ../sysdeps/unix/sysv/linux/x86_64/cancellation.S:98 #1 0x7fb598ea99d9 in read () at ../sysdeps/unix/syscall-template.S:84 #2 0x7fb592ed86c0 in ?? () from /lib/x8
[kwin] [Bug 361843] New: KWin crashes or hangs when opening certain windows
https://bugs.kde.org/show_bug.cgi?id=361843 Bug ID: 361843 Summary: KWin crashes or hangs when opening certain windows Product: kwin Version: 5.5.4 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: phill.hildskj...@gmail.com Application: kwin_x11 (5.5.4) Qt Version: 5.5.1 Operating System: Linux 4.2.0-35-generic x86_64 Distribution: Ubuntu 15.10 -- Information about the crash: - What I was doing when the application crashed: Opened emacs from Konsole. Using the breeze theme. - Unusual behavior I noticed: Similar behaviour started 3 logins ago (no upgrades immediately before). Opening some windows (new apps or new Firefox window) caused the window title bars to disappear, taskbar buttons to be drawn differently, and KWin to hang: I couldn't Alt-Tab and lost interaction with the windows still on screen. Only the top-most one had minimal interaction (blinking cursor, ability to press a button - but with no effect). In such cases KWin didn't restart with a segfault. The reported crash is the first time the behaviour I describe was followed by segfault and restart. The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f3be4a96840 (LWP 1636))] Thread 12 (Thread 0x7f3bc5705700 (LWP 1685)): #0 0x7f3be457b6f3 in select () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f3be2b46b7f in qt_safe_select (nfds=12, fdread=fdread@entry=0x7f3bb8000a78, fdwrite=fdwrite@entry=0x7f3bb8000d08, fdexcept=fdexcept@entry=0x7f3bb8000f98, orig_timeout=orig_timeout@entry=0x0) at kernel/qcore_unix.cpp:75 #2 0x7f3be2b4867e in QEventDispatcherUNIX::select (timeout=0x0, exceptfds=0x7f3bb8000f98, writefds=0x7f3bb8000d08, readfds=0x7f3bb8000a78, nfds=, this=0x7f3bb80008c0) at kernel/qeventdispatcher_unix.cpp:320 #3 QEventDispatcherUNIXPrivate::doSelect (this=this@entry=0x7f3bb80008e0, flags=..., flags@entry=..., timeout=timeout@entry=0x0) at kernel/qeventdispatcher_unix.cpp:196 #4 0x7f3be2b48bae in QEventDispatcherUNIX::processEvents (this=0x7f3bb80008c0, flags=...) at kernel/qeventdispatcher_unix.cpp:607 #5 0x7f3be2af250a in QEventLoop::exec (this=this@entry=0x7f3bc5704d60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7f3be290eac4 in QThread::exec (this=) at thread/qthread.cpp:503 #7 0x7f3bdd5c9c35 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7f3be2913a6e in QThreadPrivate::start (arg=0x22d8f10) at thread/qthread_unix.cpp:331 #9 0x7f3be3b756aa in start_thread (arg=0x7f3bc5705700) at pthread_create.c:333 #10 0x7f3be4584e9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 11 (Thread 0x7f3bbf7fe700 (LWP 1693)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f3be1a84194 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7f3be1a841d9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x7f3be3b756aa in start_thread (arg=0x7f3bbf7fe700) at pthread_create.c:333 #4 0x7f3be4584e9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 10 (Thread 0x7f3bc63a5700 (LWP 1955)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f3b32962d33 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #2 0x7f3b32962b97 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #3 0x7f3be3b756aa in start_thread (arg=0x7f3bc63a5700) at pthread_create.c:333 #4 0x7f3be4584e9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 9 (Thread 0x7f3b2f585700 (LWP 1956)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f3b32962d33 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #2 0x7f3b32962b97 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #3 0x7f3be3b756aa in start_thread (arg=0x7f3b2f585700) at pthread_create.c:333 #4 0x7f3be4584e9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 8 (Thread 0x7f3b2ed84700 (LWP 1957)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f3b32962d33 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #2 0x7f3b32962b97 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #3 0x7f3be3b756aa in start_thread (arg=0x7f3b2ed84700) at pthread_create.c:333 #4 0x7f3be4584e9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 7 (Thread 0x7f3b2e583700 (LWP 1958)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysde
[kwin] [Bug 361843] KWin crashes or hangs when opening certain windows
https://bugs.kde.org/show_bug.cgi?id=361843 --- Comment #2 from phil --- Thank you! I'll do that. -- You are receiving this mail because: You are watching all bug changes.
