[partitionmanager] [Bug 357114] New: Crash when trying to remove partition
https://bugs.kde.org/show_bug.cgi?id=357114 Bug ID: 357114 Summary: Crash when trying to remove partition Product: partitionmanager Version: 1.2.1 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: pavel.n...@gmail.com Application: partitionmanager (1.2.1) Qt Version: 5.5.1 Operating System: Linux 4.2.8-200.fc22.x86_64 x86_64 Distribution: "Fedora release 22 (Twenty Two)" -- Information about the crash: Tried several times to remove existing Fat32 partition from SD card. Every time KDE Partition Manager craches before this action (but after approving it) The crash can be reproduced every time. -- Backtrace: Application: KDE Partition Manager (partitionmanager), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fee18f068c0 (LWP 11702))] Thread 3 (Thread 0x7fedfb0f7700 (LWP 11703)): #0 0x7fee12e852fd in poll () at /lib64/libc.so.6 #1 0x7fee0f6bd182 in _xcb_conn_wait () at /lib64/libxcb.so.1 #2 0x7fee0f6bec77 in xcb_wait_for_event () at /lib64/libxcb.so.1 #3 0x7fedfd287da9 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5 #4 0x7fee13a923ce in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #5 0x7fee107a2555 in start_thread () at /lib64/libpthread.so.0 #6 0x7fee12e90b9d in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7fedd9ffb700 (LWP 11827)): #0 0x7fee12e8aeb9 in syscall () at /lib64/libc.so.6 #1 0x7fee0efb314a in g_cond_wait_until () at /lib64/libglib-2.0.so.0 #2 0x7fee0ef42a29 in g_async_queue_pop_intern_unlocked () at /lib64/libglib-2.0.so.0 #3 0x7fee0ef4304b in g_async_queue_timeout_pop () at /lib64/libglib-2.0.so.0 #4 0x7fee0ef95afa in g_thread_pool_thread_proxy () at /lib64/libglib-2.0.so.0 #5 0x7fee0ef950a5 in g_thread_proxy () at /lib64/libglib-2.0.so.0 #6 0x7fee107a2555 in start_thread () at /lib64/libpthread.so.0 #7 0x7fee12e90b9d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7fee18f068c0 (LWP 11702)): [KCrash Handler] #5 0x7fee18a3b88f in Partition::sectorsUsed() const () at /lib64/libpartitionmanagerprivate.so #6 0x7fee18ad8b2c in PartWidget::paintEvent(QPaintEvent*) () at /lib64/libpartitionmanagerprivate.so #7 0x7fee1499c428 in QWidget::event(QEvent*) () at /lib64/libQt5Widgets.so.5 #8 0x7fee1495941c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #9 0x7fee1495e8e6 in QApplication::notify(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #10 0x7fee13c7377b in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #11 0x7fee14994f09 in QWidgetPrivate::sendPaintEvent(QRegion const&) () at /lib64/libQt5Widgets.so.5 #12 0x7fee14995551 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () at /lib64/libQt5Widgets.so.5 #13 0x7fee149961fc in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () at /lib64/libQt5Widgets.so.5 #14 0x7fee149960e9 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () at /lib64/libQt5Widgets.so.5 #15 0x7fee149950c1 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () at /lib64/libQt5Widgets.so.5 #16 0x7fee149961fc in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () at /lib64/libQt5Widgets.so.5 #17 0x7fee149950c1 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () at /lib64/libQt5Widgets.so.5 #18 0x7fee149961fc in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () at /lib64/libQt5Widgets.so.5 #19 0x7fee149960e9 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () at /lib64/libQt5Widgets.so.5 #20 0x7fee149950c1 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () at /lib64/libQt5Widgets.so.5 #21 0x7fee14966caa in QWidgetBackingStore::doSync() () at /lib64/libQt5Widgets.so.5 #22 0x7fee14966e8c in QWidgetBackingStore::sync() () at /lib64/libQt5Widgets.so.5 #23 0x7fee1498503f in QWidgetPrivate::syncBackingStore() () at /lib64/libQt5Widgets.so.5 #24 0x7fee1499c228 in QWidget::event(QEvent*) () at /lib
[KScreen] [Bug 350874] After login, my dual head config is stubbornly messed up.
https://bugs.kde.org/show_bug.cgi?id=350874 Thomas Lübking changed: What|Removed |Added CC|thomas.luebk...@gmail.com | --- Comment #4 from Thomas Lübking --- Nope, there kscreen picks some (nonsense) reason because it's the bigger one and ignores(?) the other one, here it prefers to clone screens (and apparently doesn't save "corrected" settings) despite even accepting one screen to be rotated. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 357057] Ark requires rar and unrar for opening/extracting RAR archives (same for e.g. zip)
https://bugs.kde.org/show_bug.cgi?id=357057 --- Comment #7 from tago --- Thanks a lot... :) -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 355637] Kontact crashed when trying to view mail
https://bugs.kde.org/show_bug.cgi?id=355637 aux...@gmail.com changed: What|Removed |Added CC||aux...@gmail.com --- Comment #1 from aux...@gmail.com --- Same here on openSUSE Leap 42.1 with kontact5-15.12.0, libQt5Core5-5.5.0. -- You are receiving this mail because: You are watching all bug changes.
[krazy] [Bug 357115] New: Ignores .krazy file.
https://bugs.kde.org/show_bug.cgi?id=357115 Bug ID: 357115 Summary: Ignores .krazy file. Product: krazy Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: win...@kde.org Reporter: schwar...@kde.org Hi, in Kolf there is a .krazy file to ignore the "external" subdir https://quickgit.kde.org/?p=kolf.git&a=tree but the subdir is checked nevertheless. http://englishbreakfastnetwork.org/krazy/reports/kde-4.x/kdegames/kolf/index.html Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 357099] Stuck at connecting animation [regression]
https://bugs.kde.org/show_bug.cgi?id=357099 brancaleone changed: What|Removed |Added CC||cedric.devill...@gmail.com --- Comment #2 from brancaleone --- I'd like to confirm this. I'm curently using plasma 5.5.2, but it was already in 5.5.0 Note that for me i can also reproduce in different ways : * At startup : my home wifi need me to unlock kwallet. After it's done the wireless connection is working (even marked as "connected" in the applet details). * After resume from suspend, any connection previously active (wireless or wired) have the problem * Connecting a VPN from the applet (tried openvpn, pptp and openconnect). * Simply disconnecting and reconnecting any running connection. In all those cases, i have applet icon still "spinning" in systray, and in in connections details (right click on the applet icon) it is also a spinning icon, but the connection is marked "connected" and i have the option to disconnect. It also give me a high cpu usage of plasmashell. It can be fixed by simply killing and restarting plasmashell. The icon now show the correct status and cpu usage drops. But of course it restart each time you do one of the actions described previously. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 357099] Stuck at connecting animation [regression]
https://bugs.kde.org/show_bug.cgi?id=357099 --- Comment #3 from brancaleone --- Created attachment 96286 --> https://bugs.kde.org/attachment.cgi?id=96286&action=edit Screenshot of the "spinning icon" Here is a screenshot of what is shown when there is the problem. Note that below the connection i activated "BrancaPalace" the status is "connecté" (connected in french), and if i hover the mouse icon over that connection i have the option to "disconnect". -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 357116] New: Using a window rule to turn off compositing causes flickering windows when compositing is turned back on
https://bugs.kde.org/show_bug.cgi?id=357116 Bug ID: 357116 Summary: Using a window rule to turn off compositing causes flickering windows when compositing is turned back on Product: kwin Version: 5.5.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: anakin...@gmail.com I am now using a window rule to turn off compositing when I launch CS GO. When I exit CS GO, I see lot of flickering problems. For example, it happens to the decorations around some windows (although not all the time). It also just happened to the place where the yakuake window was (yakuake is hidden), when I switch between windows, I see a black window flickering at the same place as this window was. Grabbing a fullscreen window title bar (like firefox) and then moving it around causes huge flickering all over the screen. I am on a laptop with an optimus setup, so everything runs on the intel card, and the game on the nvidia card. The only way I have found to fix the issue is to restart kwin. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kde-windows] [Bug 357117] New: Changed ActivePerl version
https://bugs.kde.org/show_bug.cgi?id=357117 Bug ID: 357117 Summary: Changed ActivePerl version Product: kde-windows Version: unspecified Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: grave Priority: NOR Component: buildsystem Assignee: kde-wind...@kde.org Reporter: jonat...@imatix.com Just like https://bugs.kde.org/show_bug.cgi?id=341518, perl-all.py needs updating to reflect currently available versions of Perl. Reproducible: Always Steps to Reproduce: 1. Install perl with 'emerge perl' Actual Results: Scripts attempt to download Perl version 5.20.1, which is no longer available Expected Results: Should install correct version 5.22.0 Simple fix: --- a/portage/dev-util/perl/perl-all.py +++ b/portage/dev-util/perl/perl-all.py @@ -24,6 +24,9 @@ class subinfo(info.infoclass): self.targets['5.20.1'] = "http://downloads.activestate.com/ActivePerl/releases/5.20.1.2000/ActivePerl-5.20.1.2000-MSWin32-x64-298557.zip"; self.targetDigests['5.20.1'] = '53e840d2c95c5cda335069371b9da1109ec264ce' self.targetMergeSourcePath['5.20.1'] = "ActivePerl-5.20.1.2000-MSWin32-x64-298557\\perl" + self.targets['5.22.0'] = "http://downloads.activestate.com/ActivePerl/releases/5.22.0.2200/ActivePerl-5.22.0.2200-MSWin32-x64-299195.zip"; + self.targetDigests['5.22.0'] = '204e2287ec23c44cc8b8d2c06d46355e993ccd49' + self.targetMergeSourcePath['5.22.0'] = "ActivePerl-5.22.0.2200-MSWin32-x64-299195\\perl" else: self.targets['5.10.1'] = "http://downloads.activestate.com/ActivePerl/releases/5.10.1.1007/ActivePerl-5.10.1.1007-MSWin32-x86-291969.zip"; self.targetDigests['5.10.1'] = '9122a828b32d8b8499c73b61972eaec303698961' @@ -43,7 +46,11 @@ class subinfo(info.infoclass): self.targets['5.20.1'] = "http://downloads.activestate.com/ActivePerl/releases/5.20.1.2000/ActivePerl-5.20.1.2000-MSWin32-x86-64int-298557.zip"; self.targetDigests['5.20.1'] = '75e2b0c635e16693e2146fed65ba5e98d387a2bd' self.targetMergeSourcePath['5.20.1'] = "ActivePerl-5.20.1.2000-MSWin32-x86-64int-298557\\perl" -self.defaultTarget = '5.20.1' + self.targets['5.22.0'] = "http://downloads.activestate.com/ActivePerl/releases/5.22.0.2200/ActivePerl-5.22.0.2200-MSWin32-x64-299195.zip"; + self.targetDigests['5.22.0'] = '204e2287ec23c44cc8b8d2c06d46355e993ccd49' + self.targetMergeSourcePath['5.22.0'] = "ActivePerl-5.22.0.2200-MSWin32-x64-299195\\perl" + +self.defaultTarget = '5.22.0' def setDependencies( self ): self.buildDependencies['virtual/bin-base'] = 'default' A better solution could automatically detect and install the most recent version. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 356457] valgrind: m_mallocfree.c:2042 (vgPlain_arena_free): Assertion 'blockSane(a, b)' failed.
https://bugs.kde.org/show_bug.cgi?id=356457 --- Comment #9 from Philippe Waroquiers --- (In reply to Joost VandeVondele from comment #8) > I'll try something similar on the other machine, but the failure is not so > easy to trigger, seemingly. ... > There are many more static libraries involved, and all are compiled with > debug info. The binary is also large (~142Mb). According to the guest stacktrace, the corruption happens when mmap-ing a shared lib (so, when valgrind is reading the debug info of this library), so is probably related to the shared lib being loaded. When self-hosting, you will increase the chance to detect a possible buffer overrun by using --core-redzone-size=xxx with xxx being e.g; 100 bytes, or even 1000 bytes (if that does not give an out of memory) on the inner valgrind, -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 356996] Tracks become 'never played' after modifying the root Music directory
https://bugs.kde.org/show_bug.cgi?id=356996 --- Comment #5 from robert marshall --- I managed to replicate this in a slightly simpler form on another machine: - without amarok running I added a subdirectory to ~/Music containing (new to the collection) music tracks - I ran amarok and rescanned that directory so the new tracks were there - I then told amarok not to scan that new directory and let it do another rescan - with amarok running I moved the new subdirectory of ~/Music elsewhere (outside the directories contained in the collection) - using the `mv` shell command Then I see that the tracks at the top level in ~/Music are all shown as having never been played (before I went through these steps those tracks had been played!) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 343665] Standard shortcuts for applications with same assignment on standard and alternative give error message being ambiguous in applications (e.g. Kate)
https://bugs.kde.org/show_bug.cgi?id=343665 Rafael Jesús Alcántara Pérez changed: What|Removed |Added CC||rafaelalcantaraperez@gmail. ||com -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 354934] crash after connecting external screen
https://bugs.kde.org/show_bug.cgi?id=354934 andreas.sturmlech...@gmail.com changed: What|Removed |Added CC||andreas.sturmlechner@gmail. ||com --- Comment #1 from andreas.sturmlech...@gmail.com --- Since upgrade to plasma-5.5.1, same for 5.5.2, this same crash is now happening all the time after unlocking from screen standby. It is happening on a ThinkPad with dockingstation, lid closed, and a Displayport-connected external screen. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 357118] New: Can't switch graphics drivers
https://bugs.kde.org/show_bug.cgi?id=357118 Bug ID: 357118 Summary: Can't switch graphics drivers Product: systemsettings Version: 5.4.1 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: leh...@tutanota.com I just did a fresh install, because I messed my old one up. Now I can't change my graphics drivers from the noveau driver to the recommended one. Nothing happens when I click on "Apply". Reproducible: Always Steps to Reproduce: 1. Do a fresh Kubuntu install. 2. Try to change your graphics drivers. Actual Results: Still using the noveau driver. Expected Results: Switching to the recommended driver. My system also crashes every few minutes, so I'm hurrying typing this. Not sure if this is because of the driver. -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 356888] Kexi crashes at the attempt to create a table row.
https://bugs.kde.org/show_bug.cgi?id=356888 Jarosław Staniek changed: What|Removed |Added Status|NEEDSINFO |ASSIGNED Ever confirmed|0 |1 Resolution|WAITINGFORINFO |--- --- Comment #4 from Jarosław Staniek --- Confirmed, fix in progress, thanks! -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 356888] Kexi crashes at the attempt to create a table row.
https://bugs.kde.org/show_bug.cgi?id=356888 Jarosław Staniek changed: What|Removed |Added Assignee|kexi-b...@kde.org |stan...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 356888] Kexi crashes at the attempt to create a table row (invalid table)
https://bugs.kde.org/show_bug.cgi?id=356888 Jarosław Staniek changed: What|Removed |Added Target Milestone|--- |2.9.11 Summary|Kexi crashes at the attempt |Kexi crashes at the attempt |to create a table row. |to create a table row ||(invalid table) -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 356888] Kexi crashes at the attempt to create a table row (invalid table)
https://bugs.kde.org/show_bug.cgi?id=356888 --- Comment #5 from Jarosław Staniek --- Kexi broke the table internally in some way, this will be fixed so the "new" row will appear. Aside of that, even in case of the logical table defect (https://bugsfiles.kde.org/attachment.cgi?id=96196) Kexi should not crash but display error without allowing to proceed with data entry. And this is second fix we should have. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 357118] Can't switch graphics drivers
https://bugs.kde.org/show_bug.cgi?id=357118 --- Comment #1 from leh...@tutanota.com --- I should probably mention that I had to do an offline install, because the installer didn't recognize my USB Wi-Fi adapter. This may have affected my ability to use the proprietary drivers. Should I file that as a bug, too? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356874] Warn user about locked widgets in wallpaper settings
https://bugs.kde.org/show_bug.cgi?id=356874 --- Comment #3 from Thomas Pfeiffer --- Yes, a tooltip is the correct bandaid for the problem -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 357116] Using a window rule to turn off compositing causes flickering windows when compositing is turned back on
https://bugs.kde.org/show_bug.cgi?id=357116 --- Comment #1 from Thomas Lübking --- Sounds like a buffer age problem. KWin still running on the intel chip? Does it go away with KWIN_USE_BUFFER_AGE=0 kwin_x11 --replace & If not , does it happen on the xrender backend as well? Did you maybe export KWIN_EXPLICIT_SYNC=0 ? You do not get this when suspending/resuming the compositor by hand? Do you have fullscreen unredirection enabled? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357119] New: Crash while logging in via vncviewer
https://bugs.kde.org/show_bug.cgi?id=357119 Bug ID: 357119 Summary: Crash while logging in via vncviewer Product: plasmashell Version: master Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: Desktop Containment Assignee: se...@kde.org Reporter: j90...@yahoo.com Created attachment 96287 --> https://bugs.kde.org/attachment.cgi?id=96287&action=edit Crash log When logging in using vncviewer, the client computer's vnc login screen is black, with several windows telling that plasma crashed in server computer. All packages are updated in opensuse Leap 42.1. Application: Plasma (plasmashell), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f42a677a800 (LWP 1806))] Thread 7 (Thread 0x7f428e7a0700 (LWP 1812)): #0 0x7f429fccdc1d in poll () at /lib64/libc.so.6 #1 0x7f42a4bf4422 in () at /usr/lib64/libxcb.so.1 #2 0x7f42a4bf600f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7f4290f22c29 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f42a03c455f in () at /usr/lib64/libQt5Core.so.5 #5 0x7f429f4d70a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7f429fcd604d in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f4286ba1700 (LWP 1860)): #0 0x7ffcea7aab26 in clock_gettime () #1 0x7f429fce2c9d in clock_gettime () at /lib64/libc.so.6 #2 0x7f42a0474b06 in () at /usr/lib64/libQt5Core.so.5 #3 0x7f42a05f4089 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #4 0x7f42a05f4615 in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so.5 #5 0x7f42a05f582e in () at /usr/lib64/libQt5Core.so.5 #6 0x7f429c3ae4ad in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #7 0x7f429c3aed80 in () at /usr/lib64/libglib-2.0.so.0 #8 0x7f429c3aef7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #9 0x7f42a05f5a5b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #10 0x7f42a059ca63 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #11 0x7f42a03bf84a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #12 0x7f42a36a85f8 in () at /usr/lib64/libQt5Qml.so.5 #13 0x7f42a03c455f in () at /usr/lib64/libQt5Core.so.5 #14 0x7f429f4d70a4 in start_thread () at /lib64/libpthread.so.0 #15 0x7f429fcd604d in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f427b491700 (LWP 1904)): #0 0x7f429fce2682 in __libc_disable_asynccancel () at /lib64/libc.so.6 #1 0x7f429fcc9cf9 in read () at /lib64/libc.so.6 #2 0x7f4297e6af45 in () at /usr/lib64/tls/libnvidia-tls.so.340.93 #3 0x7f429c3efb60 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f429c3ae999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #5 0x7f429c3aedf8 in () at /usr/lib64/libglib-2.0.so.0 #6 0x7f429c3aef7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #7 0x7f42a05f5a5b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #8 0x7f42a059ca63 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #9 0x7f42a03bf84a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #10 0x7f42a36a85f8 in () at /usr/lib64/libQt5Qml.so.5 #11 0x7f42a03c455f in () at /usr/lib64/libQt5Core.so.5 #12 0x7f429f4d70a4 in start_thread () at /lib64/libpthread.so.0 #13 0x7f429fcd604d in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f4279a6f700 (LWP 1912)): #0 0x7f42a05f5995 in () at /usr/lib64/libQt5Core.so.5 #1 0x7f429c3ae4ad in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7f429c3aed80 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f429c3aef7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f42a05f5a5b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f42a059ca63 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f42a03bf84a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7f42a36a85f8 in () at /usr/lib64/libQt5Qml.so.5 #8 0x7f42a03c455f in () at /usr/lib64/libQt5Core.so.5 #9 0x7f429f4d70a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7f429fcd604d in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f4273fff700 (LWP 1913)): #0 0x7f429f4db05f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f42a5e5b7eb in () at /usr/lib64/libQt5Script.so.5 #2 0x7f42a5e5b819 in () at /usr/lib64/libQt5Script.so.5 #3 0x7f429f4d70a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f429fcd604d in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f41e7fff700 (LWP 1914)): #0 0x7f429c3f0d14 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f429c3aee0e in () at /u
[kphotoalbum] [Bug 355756] KPA settings dialog mangles annotation dialog layout and produces strange warning
https://bugs.kde.org/show_bug.cgi?id=355756 --- Comment #16 from Andreas Schleth --- Created attachment 96288 --> https://bugs.kde.org/attachment.cgi?id=96288&action=edit screenshot of startup message (latest git) This is, what I saw from the latest build. Seems to be somewhat a result of this discussion here (?) Johannes & Tobias, you are doing a great job. Merry Christmas! -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 299218] Amarok script API track signals are unreliable, undocumented
https://bugs.kde.org/show_bug.cgi?id=299218 mg changed: What|Removed |Added CC||madhurya@gmail.com --- Comment #9 from mg --- how can I access the code to work on fixing this bug? -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 299218] Amarok script API track signals are unreliable, undocumented
https://bugs.kde.org/show_bug.cgi?id=299218 --- Comment #10 from mg --- how can I access the code to work on fixing this bug? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 345456] Slow delay when drawing with tablet with OpenGL on. OpenGL off = zoom display problem on canvas.
https://bugs.kde.org/show_bug.cgi?id=345456 Abdurrahman Al Hanif changed: What|Removed |Added CC||abdurrahman.alhanif@gmail.c ||om --- Comment #6 from Abdurrahman Al Hanif --- Created attachment 96289 --> https://bugs.kde.org/attachment.cgi?id=96289&action=edit Krita log file Hello, I have problem when drawing with my Wacom Intuos small. When I draw a stroke, it feels like heavy/ slow/ lagging/ whatever you call it. It takes much time to only draw one line/ stroke. I use Krita 2.9.10 on Elementary OS Freya. I think it's about rendering so I tried to turn on OpenGL support but OMG it's being more lagging, so I turned it off again. However, I don't have problem when I draw with touch in my Wacom or with mouse, but here I want to draw with stylus/ pen. I attach the log file for inspecting. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 345456] Slow delay when drawing with tablet with OpenGL on. OpenGL off = zoom display problem on canvas.
https://bugs.kde.org/show_bug.cgi?id=345456 --- Comment #7 from Abdurrahman Al Hanif --- my system spec: Acer Aspire One 722 AMD dual-core 1.0 GHz with AMD Radeon HD Elementary OS Freya Krita 2.9.10 via Krita Lime PPA Brush that I often use is HB and 2B pencil. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 357118] Can't switch graphics drivers
https://bugs.kde.org/show_bug.cgi?id=357118 --- Comment #2 from leh...@tutanota.com --- After sudo apt-get update, some updates and restarts I was finally able to change the driver through the driver manager. Still, I think there needs to be done something: Either there should be a warning that offline-installations are not going to work fine or the process after the offline-installation should be improved. At the moment there is a notice that offline-installations are not a good idea, but I think there should be a warning. The updates need to get pulled immediately after starting the fresh installation for the first time, without having the user use the terminal. I know, sudo apt-get update is easy, but some users can't even do that. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 357120] New: Remember rectangular region when retaking screenshot
https://bugs.kde.org/show_bug.cgi?id=357120 Bug ID: 357120 Summary: Remember rectangular region when retaking screenshot Product: Spectacle Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: ximin...@gmail.com KSnapshot used to remember the rectangular region if you would retake a screenshot. I found this to be a very useful feature. Could this be added to Spectacle? Expected results: 1. Start Spectacle. 2. Select "Rectangular Region" in the "Area" combo box. 3. Press "Take New Screenshot". 4. Select a region and press enter. 5. Press "Take New Screenshot" again. 6. Previous rectangular region is selected. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 356855] Crash in scriptengine (MetaTypeExporter)
https://bugs.kde.org/show_bug.cgi?id=356855 --- Comment #1 from Anmol Ahuja --- Hey, sorry about the delayed response, I've been busy with grad school. I'm back home for the holidays, I'll fix this in the next few days. Maybe the scripting interface could use some tests? I forgot why we decided against it. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 357091] Why QSystemTrayIcon default Status is Passive
https://bugs.kde.org/show_bug.cgi?id=357091 Leslie Zhai changed: What|Removed |Added Resolution|--- |UPSTREAM Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 355756] KPA settings dialog mangles annotation dialog layout and produces strange warning
https://bugs.kde.org/show_bug.cgi?id=355756 --- Comment #17 from Tobias Leupold --- You're right :-) After a close inspection, we realized that those translatable category names cause some problems that actually can't be fixed at all. So we decided to remove them. If you want, you can test the current git state. It's about category names and the category settings dialog. Have a backup, we had to change a lot of code all over KPA ;-) If you find some bug/regression, please inform us (via mailing list or IRC). Merry Christmas and nice holidays :-) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 357116] Using a window rule to turn off compositing causes flickering windows when compositing is turned back on
https://bugs.kde.org/show_bug.cgi?id=357116 --- Comment #2 from AnAkkk --- (In reply to Thomas Lübking from comment #1) > Sounds like a buffer age problem. KWin still running on the intel chip? Yes, it is. Apparently, I have 3 different issues: 1) A black square in the top left corner when compositing is disabled, which is put on top of every window, this is actually the "button" which is on plasma desktop to access the desktop settings menu etc, for some reason it's totally black with compositing disabled. Happens even with ALT-SHIFT-F12. So actually that black square appears on top of the game as well. This disappear when reenabling the compositor. 2) Flickering when moving windows after compositing has been reenabled 3) Windows decorations having weird "buggy" black borders around them > Does it go away with > KWIN_USE_BUFFER_AGE=0 kwin_x11 --replace & That seem to fix 2), but doesn't fix 3) > > Did you maybe export KWIN_EXPLICIT_SYNC=0 ? No, I'm not exporting anything specific to kwin. > You do not get this when suspending/resuming the compositor by hand? No, only when suspended with the rules. > Do you have fullscreen unredirection enabled? No, it's impossible to enable it with an intel card. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 357116] Using a window rule to turn off compositing causes flickering windows when compositing is turned back on
https://bugs.kde.org/show_bug.cgi?id=357116 --- Comment #3 from AnAkkk --- To be more precise, I get 2) and 3) only when the compositor suspended by the rules and reenabled. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 357121] New: Timeline position indicator is missing
https://bugs.kde.org/show_bug.cgi?id=357121 Bug ID: 357121 Summary: Timeline position indicator is missing Product: kdenlive Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: richtip...@gmail.com No position indicator on the Timeline moves along as my video plays. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 146239] not greedy regular expression
https://bugs.kde.org/show_bug.cgi?id=146239 Till Seifert changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #16 from Till Seifert --- *** This bug has been confirmed by popular vote. *** -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 357122] New: KDE Login error
https://bugs.kde.org/show_bug.cgi?id=357122 Bug ID: 357122 Summary: KDE Login error Product: kdelibs Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: kded Assignee: unassigned-b...@kde.org Reporter: kiril...@yandex.ru Application: kded4 (4.14.13) KDE Platform Version: 4.14.13 Qt Version: 4.8.6 Operating System: Linux 3.13.0-45-generic i686 Distribution: Ubuntu 14.04.3 LTS -- Information about the crash: - What I was doing when the application crashed: 1) Start remote session using xrdp & X11rdp 2) After KDE first screen starts appear error message The crash can be reproduced every time. -- Backtrace: Application: Служба KDE (kded4), signal: Segmentation fault Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1". [KCrash Handler] #7 0xae438027 in XRandR11::config() const () from /usr/lib/kde4/plugins/kscreen/KSC_XRandR11.so #8 0xae40a956 in KScreen::Config::current() () from /usr/lib/libkscreen.so.1 #9 0xae563a65 in KScreenDaemon::monitorConnectedChange (this=this@entry=0x9936338) at /build/buildd/kscreen-1.0.2.1/kded/daemon.cpp:196 #10 0xae564284 in KScreenDaemon::KScreenDaemon (this=0x9936338, parent=0x97ee860) at /build/buildd/kscreen-1.0.2.1/kded/daemon.cpp:72 #11 0xae565121 in KPluginFactory::createInstance (parentWidget=0x0, parent=0x97ee860, args=...) at /usr/include/KDE/../kpluginfactory.h:477 #12 0xb70d0f44 in KPluginFactory::create (this=0x99315a8, iface=0xb71260e0 "KDEDModule", parentWidget=0x0, parent=0x97ee860, args=..., keyword=...) at ../../kdecore/util/kpluginfactory.cpp:203 #13 0xb52b8704 in create (args=..., parent=0x97ee860, this=) at ../../kdecore/util/kpluginfactory.h:507 #14 Kded::loadModule (this=0x97ee860, s=..., onDemand=onDemand@entry=false) at ../../kded/kded.cpp:409 #15 0xb52b9003 in Kded::initModules (this=0x97ee860) at ../../kded/kded.cpp:268 #16 0xb52b98ac in Kded::recreateDone (this=this@entry=0x97ee860) at ../../kded/kded.cpp:580 #17 0xb52b992b in Kded::recreate (this=0x97ee860, initial=true) at ../../kded/kded.cpp:547 #18 0xb52bc4c0 in KDEDApplication::newInstance (this=0xbfdbd2bc) at ../../kded/kded.cpp:833 #19 0xb7499b5f in KUniqueApplicationAdaptor::newInstance (this=this@entry=0x98e4c80, asn_id=..., args=...) at ../../kdeui/kernel/kuniqueapplication.cpp:442 #20 0xb7499be6 in KUniqueApplicationAdaptor::qt_static_metacall (_o=_o@entry=0x98e4c80, _id=_id@entry=0, _a=_a@entry=0xbfdbca8c, _c=QMetaObject::InvokeMetaMethod) at ./kuniqueapplication_p.moc:57 #21 0xb7499e73 in qt_static_metacall (_a=0xbfdbca8c, _id=0, _c=QMetaObject::InvokeMetaMethod, _o=0x98e4c80) at ./kuniqueapplication_p.moc:100 #22 KUniqueApplicationAdaptor::qt_metacall (this=0x98e4c80, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfdbca8c) at ./kuniqueapplication_p.moc:101 #23 0xb5b2721e in QDBusConnectionPrivate::deliverCall (this=this@entry=0x97f2660, object=object@entry=0x98e4c80, msg=..., metaTypes=..., slotIdx=4) at qdbusintegrator.cpp:951 #24 0xb5b2848e in QDBusConnectionPrivate::activateCall (this=0x97f2660, object=0x98e4c80, flags=337, msg=...) at qdbusintegrator.cpp:856 #25 0xb5b28b97 in QDBusConnectionPrivate::activateObject (this=0x97f2660, node=..., msg=..., pathStartPos=16) at qdbusintegrator.cpp:1427 #26 0xb5b28f78 in QDBusActivateObjectEvent::placeMetaCall (this=0x98fb1d8) at qdbusintegrator.cpp:1541 #27 0xb6d836fb in QObject::event (this=this@entry=0xbfdbd2bc, e=e@entry=0x98fb1d8) at kernel/qobject.cpp:1194 #28 0xb6d6ea9a in QCoreApplication::event (this=0xbfdbd2bc, e=0x98fb1d8) at kernel/qcoreapplication.cpp:1765 #29 0xb627bd0f in QApplication::event (this=0xbfdbd2bc, e=0x98fb1d8) at kernel/qapplication.cpp:2549 #30 0xb62767f4 in QApplicationPrivate::notify_helper (this=0x97f1848, receiver=0xbfdbd2bc, e=0x98fb1d8) at kernel/qapplication.cpp:4567 #31 0xb627d2d3 in QApplication::notify (this=0xbfdbd2bc, receiver=receiver@entry=0xbfdbd2bc, e=e@entry=0x98fb1d8) at kernel/qapplication.cpp:4353 #32 0xb7491ce4 in KApplication::notify (this=0xbfdbd2bc, receiver=0xbfdbd2bc, event=0x98fb1d8) at ../../kdeui/kernel/kapplication.cpp:311 #33 0xb6d69e4a in QCoreApplication::notifyInternal (this=0xbfdbd2bc, receiver=receiver@entry=0xbfdbd2bc, event=event@entry=0x98fb1d8) at kernel/qcoreapplication.cpp:953 #34 0xb6d6d70d in sendEvent (event=0x98fb1d8, receiver=0xbfdbd2bc) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #35 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x9784f80) at kernel/qcoreapplication.cpp:1577 #36 0xb6d6dc1c in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1470 #37 0xb6d9a23e in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236 #
[kwin] [Bug 357116] Using a window rule to turn off compositing causes flickering windows when compositing is turned back on
https://bugs.kde.org/show_bug.cgi?id=357116 --- Comment #4 from Thomas Lübking --- (In reply to AnAkkk from comment #2) > 1) A black square in the top left corner when compositing is disabled ie. an override_redirect (unmanaged) ARGB window. It's always above the other windows, but you can only see it when not compositing. Smells like a plasmashell bug to me? (Sounds as if it *should* be an input_only window and even that seems questionable) Can you "xprop" & "xwininfo" it? > 3) Windows decorations having weird "buggy" black borders around them Can you make a Screenshot? > > KWIN_USE_BUFFER_AGE=0 kwin_x11 --replace & > 2) Flickering when moving windows after compositing has been reenabled > That seem to fix 2), but doesn't fix 3) > No, only when suspended with the rules. Does it also happen if you eg. create a rule for a) xterm b) (windowed!) glxinfo -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357089] Crash if I right click on System Settings under Computer tab
https://bugs.kde.org/show_bug.cgi?id=357089 --- Comment #2 from sbsb...@gmail.com --- Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1b610f9800 (LWP 2018))] Thread 9 (Thread 0x7f1b4bfcb700 (LWP 2020)): #0 0x7f1b5b6c418d in poll () from /usr/lib/libc.so.6 #1 0x7f1b5f87eae2 in ?? () from /usr/lib/libxcb.so.1 #2 0x7f1b5f880757 in xcb_wait_for_event () from /usr/lib/libxcb.so.1 #3 0x7f1b4d6fd379 in ?? () from /usr/lib/libQt5XcbQpa.so.5 #4 0x7f1b5bdb9b8e in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7f1b5aec34a4 in start_thread () from /usr/lib/libpthread.so.0 #6 0x7f1b5b6cd13d in clone () from /usr/lib/libc.so.6 Thread 8 (Thread 0x7f1b496e3700 (LWP 2046)): #0 0x7f1b585f309e in ?? () from /usr/lib/libglib-2.0.so.0 #1 0x7f1b585f591a in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #2 0x7f1b585f5f60 in ?? () from /usr/lib/libglib-2.0.so.0 #3 0x7f1b585f60cc in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #4 0x7f1b5bff156b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7f1b5bf9857a in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #6 0x7f1b5bdb4be4 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #7 0x7f1b5e700055 in ?? () from /usr/lib/libQt5Qml.so.5 #8 0x7f1b5bdb9b8e in ?? () from /usr/lib/libQt5Core.so.5 #9 0x7f1b5aec34a4 in start_thread () from /usr/lib/libpthread.so.0 #10 0x7f1b5b6cd13d in clone () from /usr/lib/libc.so.6 Thread 7 (Thread 0x7f1b41673700 (LWP 2049)): #0 0x7f1b5aec907f in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f1b42c5ab33 in ?? () from /usr/lib/xorg/modules/dri/radeonsi_dri.so #2 0x7f1b42c5a287 in ?? () from /usr/lib/xorg/modules/dri/radeonsi_dri.so #3 0x7f1b5aec34a4 in start_thread () from /usr/lib/libpthread.so.0 #4 0x7f1b5b6cd13d in clone () from /usr/lib/libc.so.6 Thread 6 (Thread 0x7f1b4092a700 (LWP 2050)): #0 0x7f1b5b6c418d in poll () from /usr/lib/libc.so.6 #1 0x7f1b585f5fbc in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f1b585f60cc in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7f1b5bff156b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7f1b5bf9857a in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7f1b5bdb4be4 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7f1b5e700055 in ?? () from /usr/lib/libQt5Qml.so.5 #7 0x7f1b5bdb9b8e in ?? () from /usr/lib/libQt5Core.so.5 #8 0x7f1b5aec34a4 in start_thread () from /usr/lib/libpthread.so.0 #9 0x7f1b5b6cd13d in clone () from /usr/lib/libc.so.6 Thread 5 (Thread 0x7f1b3340b700 (LWP 2057)): #0 0x7f1b5863a614 in g_mutex_unlock () from /usr/lib/libglib-2.0.so.0 #1 0x7f1b585f5540 in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0 #2 0x7f1b585f5eeb in ?? () from /usr/lib/libglib-2.0.so.0 #3 0x7f1b585f60cc in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #4 0x7f1b5bff156b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7f1b5bf9857a in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #6 0x7f1b5bdb4be4 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #7 0x7f1b5e700055 in ?? () from /usr/lib/libQt5Qml.so.5 #8 0x7f1b5bdb9b8e in ?? () from /usr/lib/libQt5Core.so.5 #9 0x7f1b5aec34a4 in start_thread () from /usr/lib/libpthread.so.0 #10 0x7f1b5b6cd13d in clone () from /usr/lib/libc.so.6 Thread 4 (Thread 0x7f1b31b73700 (LWP 2059)): #0 0x7f1b5aec907f in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f1b60b52934 in ?? () from /usr/lib/libQt5Script.so.5 #2 0x7f1b60b52979 in ?? () from /usr/lib/libQt5Script.so.5 #3 0x7f1b5aec34a4 in start_thread () from /usr/lib/libpthread.so.0 #4 0x7f1b5b6cd13d in clone () from /usr/lib/libc.so.6 Thread 3 (Thread 0x7f1aab16b700 (LWP 2071)): #0 0x7f1b5b6c418d in poll () from /usr/lib/libc.so.6 #1 0x7f1b585f5fbc in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f1b585f60cc in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7f1b5bff156b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7f1b5bf9857a in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7f1b5bdb4be4 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7f1b5f0bd136 in ?? () from /usr/lib/libQt5Quick.so.5 #7 0x7f1b5bdb9b8e in ?? () from /usr/lib/libQt5Core.so.5 #8 0x7f1b5aec34a4 in start_thread () from /usr/lib/libpthread.so.0 #9 0x7f1b5b6cd13d in clone () from /usr/lib/libc.so.6 Thread 2 (Thread 0x7f1a9fb0b700 (LWP 2136)): #0 0x7f1b5b6c418d in poll () from /usr/lib/libc.so.6 #1 0x7f1b585f5fbc in ?? () from /usr/lib/libglib-
[konsole] [Bug 354082] high cpu usage for screen redrawing with qt5.5
https://bugs.kde.org/show_bug.cgi?id=354082 Sven Brauch changed: What|Removed |Added CC||m...@svenbrauch.de --- Comment #6 from Sven Brauch --- Same issue here, I can confirm the fix as well. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 357116] Using a window rule to turn off compositing causes flickering windows when compositing is turned back on
https://bugs.kde.org/show_bug.cgi?id=357116 --- Comment #5 from AnAkkk --- Created attachment 96290 --> https://bugs.kde.org/attachment.cgi?id=96290&action=edit Screenshot of firefox window after reenabling compositing -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 357116] Using a window rule to turn off compositing causes flickering windows when compositing is turned back on
https://bugs.kde.org/show_bug.cgi?id=357116 --- Comment #6 from AnAkkk --- (In reply to Thomas Lübking from comment #4) > Can you "xprop" & "xwininfo" it? Output of xprop: _NET_WM_WINDOW_OPACITY(CARDINAL) = 0 Output of xwininfo: xwininfo: Window id: 0x246 (has no name) Absolute upper-left X: 0 Absolute upper-left Y: 0 Relative upper-left X: 0 Relative upper-left Y: 0 Width: 32 Height: 32 Depth: 24 Visual: 0x20 Visual Class: TrueColor Border width: 0 Class: InputOutput Colormap: 0x22 (installed) Bit Gravity State: ForgetGravity Window Gravity State: NorthWestGravity Backing Store State: NotUseful Save Under State: no Map State: IsViewable Override Redirect State: yes Corners: +0+0 -1888+0 -1888-1048 +0-1048 -geometry 32x32+0+0 > > 3) Windows decorations having weird "buggy" black borders around them > Can you make a Screenshot? Attached a screenshot of the firefox window border. > Does it also happen if you eg. create a rule for > a) xterm > b) (windowed!) glxinfo a) No, doesn't seem to happen with xterm, maybe because it's not a fullscreen app b) windowed ? what do you mean? -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 357025] Application crash on creating new row
https://bugs.kde.org/show_bug.cgi?id=357025 Jarosław Staniek changed: What|Removed |Added CC||stan...@kde.org Component|General |Tables -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 357116] Using a window rule to turn off compositing causes flickering windows when compositing is turned back on
https://bugs.kde.org/show_bug.cgi?id=357116 --- Comment #7 from Thomas Lübking --- (In reply to AnAkkk from comment #6) > (In reply to Thomas Lübking from comment #4) > > Can you "xprop" & "xwininfo" it? > > Output of xprop: > _NET_WM_WINDOW_OPACITY(CARDINAL) = 0 Idiocracy. Seriously. Whatever it is, it's idiocracy. run "xkill" and click the window - the process it belongs to should die afterwards (maybe take a "ps fax" diff on before and after) Unfortunately there's no further hint what it belongs to :-( > Attached a screenshot of the firefox window border. Looks like the shadow texture is invalid (for whatever reason) > a) No, doesn't seem to happen with xterm, maybe because it's not a > fullscreen app I rather assume "because it's not a GL context". You can however turn any window fullscreen (except for xterm by default, because it demands certain aspect ratios, can be ignored by a rule as well) > b) windowed ? what do you mean? ... "glxgears", sorry :-) -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 357025] Application crash on creating new row
https://bugs.kde.org/show_bug.cgi?id=357025 Jarosław Staniek changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #2 from Jarosław Staniek --- Thanks Arseniy! I am fixing this issue already for 2.9.11. See https://bugs.kde.org/show_bug.cgi?id=356888. *** This bug has been marked as a duplicate of bug 356888 *** -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 357025] Application crash on creating new row
https://bugs.kde.org/show_bug.cgi?id=357025 Jarosław Staniek changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 356888] Kexi crashes at the attempt to create a table row (invalid table)
https://bugs.kde.org/show_bug.cgi?id=356888 Jarosław Staniek changed: What|Removed |Added CC||kdeu...@sauron.cf --- Comment #6 from Jarosław Staniek --- *** Bug 357025 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[gcompris] [Bug 357123] New: Allows cheating if I press arrow_key at the right moment
https://bugs.kde.org/show_bug.cgi?id=357123 Bug ID: 357123 Summary: Allows cheating if I press arrow_key at the right moment Product: gcompris Version: git master Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: bruno.coud...@gcompris.net Reporter: itatr...@gmail.com It's, undoubtedly, a bug. If we press "Arrow_key" at the finish multiple times it allows us to "jump" through a few levels above. Reproducible: Always Steps to Reproduce: 1. Start "Maze" activity. 2. Go through one maze. 3. At the moment of coming though the door to finish the lvl - press "arrow_key" multiple times. 4. Done! You're not on the "currentLvl + 1", but on the "currentLvl + 3(or 4)" Actual Results: I've mentioned above. Expected Results: Instead, it should bring you to the "currentLvl + 1" regardless of whether any buttons(arrow_key) were pressed or not. Tested on Android as well. Bug exists on all platforms and all OSes, therefore it's not platform related, but code. -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 357107] After importing vCard with typeless TEL numbers, kAddressbook does not show any labels next to the phone numbers.
https://bugs.kde.org/show_bug.cgi?id=357107 --- Comment #3 from Laurent Montel --- Ok I understand now the problem -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 354934] crash after connecting external screen
https://bugs.kde.org/show_bug.cgi?id=354934 --- Comment #2 from andreas.sturmlech...@gmail.com --- Created attachment 96291 --> https://bugs.kde.org/attachment.cgi?id=96291&action=edit ksmserver-20151224-151328.kcrash ...and here's my backtrace. Reproducible each time by just switching off and on the external DP screen while kscreenlocker is active. Can't reproduce it with LVDS only (no external screen attached). -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 357025] Application crash on creating new row
https://bugs.kde.org/show_bug.cgi?id=357025 --- Comment #3 from Arseniy --- Maybe this bug occurs because one of the fields of the table is «exists» — this is reserved word in SQLite. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 355380] 15.11.90: deleting topmost track with clip with transition does leave transition behind
https://bugs.kde.org/show_bug.cgi?id=355380 wegwerf-1-...@gmx.de changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #5 from wegwerf-1-...@gmx.de --- Works like a charm. Thank you very much! Happy Xmas! -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 357107] After importing vCard with typeless TEL numbers, kAddressbook does not show any labels next to the phone numbers.
https://bugs.kde.org/show_bug.cgi?id=357107 Laurent Montel changed: What|Removed |Added Version Fixed In||5.1.1 Resolution|--- |FIXED Latest Commit||http://commits.kde.org/kcon ||tacts/6496c1175a0061a765489 ||f4fb40fcb237e9d9973 Status|UNCONFIRMED |RESOLVED --- Comment #4 from Laurent Montel --- Git commit 6496c1175a0061a765489f4fb40fcb237e9d9973 by Montel Laurent. Committed on 24/12/2015 at 15:30. Pushed by mlaurent into branch 'Applications/15.12'. Fix Bug 357107 - After importing vCard with typeless TEL numbers, kAddressbook does not show any labels next to the phone numbers. FIXED-IN: 5.1.1 M +3-15 src/phonenumber.cpp M +2-1src/phonenumber.h M +3-3src/vcardtool.cpp http://commits.kde.org/kcontacts/6496c1175a0061a765489f4fb40fcb237e9d9973 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357124] New: A Plasma összeomlott, miután egy pendriveot újraformáztam.
https://bugs.kde.org/show_bug.cgi?id=357124 Bug ID: 357124 Summary: A Plasma összeomlott, miután egy pendriveot újraformáztam. Product: plasmashell Version: 5.2.2 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: logonye...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.2.2) Qt Version: 5.4.1 Operating System: Linux 3.19.0-21-generic i686 Distribution: Ubuntu 15.04 -- Information about the crash: Egy pendriveot, amelyre korábban egy lemezképet írtam, újra akartam formázni, mire a gép hibák sorozatát jelentette. Ezután nem is érzékelte a gép a pendriveot, erre néhányszor kihúztam és bedugtam, ezután a Plasma is leállt. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0xb1fc3980 (LWP 1768))] Thread 35 (Thread 0xb034fb40 (LWP 1780)): #0 0xb44c6fad in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #1 0xb44c7439 in g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0 #2 0xb08c32f5 in ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 #3 0xb44ee40a in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0xb4baf1aa in start_thread (arg=0xb034fb40) at pthread_create.c:333 #5 0xb4eadfde in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:122 Thread 34 (Thread 0xaf9ffb40 (LWP 1782)): #0 0xb44c6fe8 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #1 0xb44c7156 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #2 0xb44c71b0 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0xb44ee40a in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0xb4baf1aa in start_thread (arg=0xaf9ffb40) at pthread_create.c:333 #5 0xb4eadfde in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:122 Thread 33 (Thread 0xade94b40 (LWP 1796)): #0 0xb44c6b78 in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0 #1 0xb44c7089 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #2 0xb44c7156 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0xb53859fc in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #4 0xb5326d93 in QEventLoop::processEvents(QFlags) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #5 0xb53271fa in QEventLoop::exec(QFlags) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #6 0xb50f940d in QThread::exec() () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #7 0xb678b50f in ?? () from /usr/lib/i386-linux-gnu/libQt5Qml.so.5 #8 0xb50fe7eb in ?? () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #9 0xb4baf1aa in start_thread (arg=0xade94b40) at pthread_create.c:333 #10 0xb4eadfde in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:122 Thread 32 (Thread 0xaa3e9b40 (LWP 1813)): #0 0xb778a996 in __vdso_clock_gettime () #1 0xb4ebb740 in __GI___clock_gettime (clock_id=1, tp=0xaa3e9004) at ../sysdeps/unix/clock_gettime.c:115 #2 0xb519f498 in ?? () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #3 0xb5383321 in QTimerInfoList::updateCurrentTime() () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #4 0xb5383834 in QTimerInfoList::timerWait(timespec&) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #5 0xb5384db9 in ?? () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #6 0xb44c641b in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0 #7 0xb44c6f24 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #8 0xb44c7156 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #9 0xb53859fc in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #10 0xb5326d93 in QEventLoop::processEvents(QFlags) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #11 0xb53271fa in QEventLoop::exec(QFlags) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #12 0xb50f940d in QThread::exec() () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #13 0xb678b50f in ?? () from /usr/lib/i386-linux-gnu/libQt5Qml.so.5 #14 0xb50fe7eb in ?? () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #15 0xb4baf1aa in start_thread (arg=0xaa3e9b40) at pthread_create.c:333 #16 0xb4eadfde in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:122 Thread 31 (Thread 0xa8ae4b40 (LWP 1878)): #0 0xb44c7120 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #1 0xb53859fc in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #2 0xb5326d93 in QEventLoop::processEvents(QFlags) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #3 0xb53271fa in QEventLoop::exec(QFlags) () from /usr/lib/i386-linux-gnu/sse2/
[kmail2] [Bug 357060] Import of Thunderbird mails doesn't work
https://bugs.kde.org/show_bug.cgi?id=357060 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org --- Comment #1 from Laurent Montel --- What do you use as application ? kmail ? kmailcvt etc ? importwizard ? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357125] New: Cannot right-click favorites and sort by name
https://bugs.kde.org/show_bug.cgi?id=357125 Bug ID: 357125 Summary: Cannot right-click favorites and sort by name Product: plasmashell Version: 5.5.1 Platform: Archlinux Packages URL: https://forum.kde.org/viewtopic.php?f=289&t=130220 OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: marco_pari...@hotmail.com CC: plasma-b...@kde.org I used to click on the Application Launcher (AKA Kicker), see the list of favorites and right click > sort by name since Plasma 4.x through 5.4.3. Now on Manjaro 15.12, with Plasma 5.5.1, I can no longer do so. Was this function removed? Reproducible: Always Steps to Reproduce: 1. Left-click on Applications Launcher 2. See Favorites 3. Right-Click Actual Results: No option to sort by name. Expected Results: There used to be a sort by name. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 357116] Using a window rule to turn off compositing causes flickering windows when compositing is turned back on
https://bugs.kde.org/show_bug.cgi?id=357116 --- Comment #8 from AnAkkk --- (In reply to Thomas Lübking from comment #7) > Idiocracy. Seriously. Whatever it is, it's idiocracy. > run "xkill" and click the window - the process it belongs to should die > afterwards > (maybe take a "ps fax" diff on before and after) xkill has no effect on it, it's still here. > ... "glxgears", sorry :-) Just tried, I don't have issues 2) and 3) with glxgears. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 357121] Timeline position indicator is missing
https://bugs.kde.org/show_bug.cgi?id=357121 richtip...@gmail.com changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 354163] kscreen sets incorrect monitor resolution and doesn't allow resolution changes
https://bugs.kde.org/show_bug.cgi?id=354163 --- Comment #5 from Kenny Fairweather --- (In reply to e8h from comment #4) > In >Startup and Shutdown>Background Serivces> untick "KScreen2" and reboot. Hmm, that makes it worse. As plasma crashes every login, it leaves me with a mostly useless desktop. Thankfully krunner still works so I could easily revert by launching "System Settings" again -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 354163] kscreen sets incorrect monitor resolution and doesn't allow resolution changes
https://bugs.kde.org/show_bug.cgi?id=354163 Kenny Fairweather changed: What|Removed |Added Severity|normal |major -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355463] xembedsniproxy always crash when login
https://bugs.kde.org/show_bug.cgi?id=355463 --- Comment #11 from Raman Gupta --- (In reply to Dennis from comment #10) > (In reply to Damian Nowak from comment #8) > > Is there a remedy for that? Arch Linux forced everyone to update from KDE 4 > > to KDE 5, but KDE 5 is not usable because of this. Kind of stuck. > > I have the same problem, my workaround is to just start xembedsniproxy again > with krunner. I have considered making systemd handling it with a service, > but I believe that it will be fixed soon. Just for reference, here is my systemd user unit file: ~ cat .config/systemd/user/xembedsniproxy.service [Unit] Description=xembed SNI proxy daemon [Service] ExecStart=/usr/bin/xembedsniproxy Restart=on-failure [Install] WantedBy=graphical.target The "WantedBy" doesn't seem to work correctly, so it has to be started once manually after login: systemctl --user start xembedsniproxy.service but after that systemd keeps it alive perfectly. -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 337035] KDE does not play well with shared-mime-info after update from 1.2-2 to 1.3-1. "Breaks" .iso files (.txt file icon / behavior).
https://bugs.kde.org/show_bug.cgi?id=337035 J.M. 'Peng' Hardin changed: What|Removed |Added CC||peng.thinkb...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 357126] New: "Drucker freigeben" to unspecific and unsecure
https://bugs.kde.org/show_bug.cgi?id=357126 Bug ID: 357126 Summary: "Drucker freigeben" to unspecific and unsecure Product: print-manager Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: dantt...@gmail.com Reporter: c.bu...@posteo.jp Created attachment 96292 --> https://bugs.kde.org/attachment.cgi?id=96292&action=edit show the bug and version informations I am wondering why my KDELibs-Version 4.13.3 is not available here in the version-field of that bug-report. Can you explain? As you can see on the screenshot I am using Kubuntu 14.04.03 LTS in a German version. To describe the bug please see the red mark on the screenshot: When adding a new printer I can select with a checkbox if this printer should be published (my own translation) to other systems. As I learned in the german ubuntu forum this checkbox only affects the CUPS system - nothing more. It doesn't touch SAMBA. I was quite shocked to see that all my printers are available in the network rather I deactivated your checkbox. This situatin lower the security and disinform the user. Minimal solution: Modify the description of the checkbox and add the info about CUPS. Something like "publish the printer with CUPS". Nicer solution: Think about what your gui means for the user and what should the gui affect technicaly. So your gui could check for the SAMBA printer settings, too. Maybe there are more systems available how to publish printers in a network - you should check for them, too. If this is not possible for you be more specific in the description of that checkbox. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 357060] Import of Thunderbird mails doesn't work
https://bugs.kde.org/show_bug.cgi?id=357060 --- Comment #2 from wodenhof --- I use Kmail5 (Plasma). Click on leftmost entry in the top menu (Files), line "Import messages", then a popup comes where I first select mozilla/thunderbird then choose a target-folder. HTH. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 344879] memory leak in plasmashell - huge ram usage
https://bugs.kde.org/show_bug.cgi?id=344879 Elizabeth Myers changed: What|Removed |Added CC||elizab...@interlinked.me --- Comment #103 from Elizabeth Myers --- I am having the same problem as André Vitor de Lima Matos. Here's what I know: * Only killing the X server reclaims the memory (killing plasmashell/kwin_x11 doesn't release it); it leaks about 5GB per day * Plasma/kwin 5.5.2 (has been occurring for a while though) * EGL/OpenGL 2.0 are my compositing options, but it happens with xrender too * Using Intel driver 2.99.917-r2, Xorg 1.17.4, Kernel 4.3.3 * No real widgets besides the default * I run thunderbird from time to time (but leaks even when I don't run it), firefox (5 or so tabs, no inordinate memory usage), pidgin (a few conversations), konversation (about 35 tabs or so), and konsole (pretty much vim, htop, and basic system administration tasks). * plasmashell is using about 200M of memory, kwin_x11 is using about 40M of memory * xrestop shows nothing out of the ordinary * Suspending does not worsen it (I don't hibernate) * I run infinality * I have only one tray icon not from KDE: pidgin, and it blinking doesn't seem to worsen the problem after a cursory look * Closing/opening windows doesn't seem to cause it (though it changes memory usage slightly, it doesn't resolve the general leak) * Rolling over the task manager (looking at thumbnails) doesn't cause it I'm at a loss as to what more I can do, though, to elucidate the bug. It seems to happen under ill-defined circumstances. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 355390] Localized Dolphin crashes when I try to create new folder
https://bugs.kde.org/show_bug.cgi?id=355390 Rajiv Parfenov changed: What|Removed |Added CC||parfenov.ra...@yandex.ru -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 344879] memory leak in plasmashell - huge ram usage
https://bugs.kde.org/show_bug.cgi?id=344879 --- Comment #104 from Hussam Al-Tayeb --- (In reply to Elizabeth Myers from comment #103) > I am having the same problem as André Vitor de Lima Matos. Here's what I > know: > > * Only killing the X server reclaims the memory (killing > plasmashell/kwin_x11 doesn't release it); it leaks about 5GB per day Can you try my suggestion please? close all applications including system tray ones after disabling swap. restart kwin_x11/plasma and ctrl+alt+f3 or f4 and then ctrl+alt+f1 back to your X session. I would like to know if ctrl+alt+f* operations are triggering garbage collection in Xorg. > * I run infinality I think infinality patches can cause issues -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 357127] New: Shortcuts bound to F keys ignore state of ISO_Level3_Shift
https://bugs.kde.org/show_bug.cgi?id=357127 Bug ID: 357127 Summary: Shortcuts bound to F keys ignore state of ISO_Level3_Shift Product: frameworks-kglobalaccel Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: mgraess...@kde.org Reporter: k...@dhardy.name CC: kdelibs-b...@kde.org I have my keyboard set up with an extra layer; right-Alt is ISO_Level3_Shift, which gives many keys an extra layer (e.g. Alt+F9 is 7); this is because my ErgoDox does not have all the normal keys. [See https://github.com/dhardy/keyboard]. Both global and application-local shortcuts assigned to F-keys ignore the state of the level-3 shift key; that is if I bind a shortcut like "lower window" to F2, then this triggers whenever F2 **or Alt+F2** is pressed, and the application never receives the usual result of Alt+F2. Similarly with application shortcuts; e.g. Kate binds F11 to "show line numbers", and as a result Alt+F11 toggles line numbers and does not enter '9' into the text editor. Additionally, if I map a shortcut to something like Alt+F9, then in the shortcut box the character resulting from this keyboard mapping appears (7), and the shortcut does not work. Reproducible: Always Steps to Reproduce: 1. Configure XKB with a level-3 shift key and configure level 3 of some F-keys (or install my layout config to /usr/share/X11/xkb/symbols/cyborg16 then `setxkbmap cyborg16 colemak4`) 2. Open any application with a shortcut bound to an F-key (e.g. Konsole: F11 → fullscreen) 3. Press Alt+F11 (etc.) and observe that the shortcut is triggered, not the mapped action of Alt+F11 I am running Kate 15.08.3 with KDE Frameworks 5.17.0 (Fedora 23). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 344879] memory leak in plasmashell - huge ram usage
https://bugs.kde.org/show_bug.cgi?id=344879 --- Comment #105 from Elizabeth Myers --- (In reply to Hussam Al-Tayeb from comment #104) > Can you try my suggestion please? close all applications including system > tray ones after disabling swap. restart kwin_x11/plasma and ctrl+alt+f3 or > f4 and then ctrl+alt+f1 back to your X session. I usually don't have swap enabled. The memory usage goes down when I close the apps and switch to a TTY to kill plasma and kwin_x11 (more from closing apps than anything else) but the leaked memory seems to remain. Note though I only tried this when X was using about 300MB of memory (it starts with about 100). I will try it when the memory usage goes up again to the gigabyte range. > I think infinality patches can cause issues I've never had issues with them. I can try switching, but call me skeptical. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 344879] memory leak in plasmashell - huge ram usage
https://bugs.kde.org/show_bug.cgi?id=344879 --- Comment #106 from Hussam Al-Tayeb --- (In reply to Elizabeth Myers from comment #105) > I usually don't have swap enabled. The memory usage goes down when I close > the apps and switch to a TTY to kill plasma and kwin_x11 (more from closing > apps than anything else) but the leaked memory seems to remain. Thank you. That is what I was trying to figure out. If I understand correctly, closing an application and then switching to a TTY and back causes Xorg to release the xserver memory used for that application. If memory leaks remain afterwards, then this indicates issues with the xorg driver and the compositor (kwin_x11 in your case). -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 349397] Incorrect behavior for Desktop and System Settings
https://bugs.kde.org/show_bug.cgi?id=349397 hotmusic...@mail.bg changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[apper] [Bug 330639] Offline updates with Apper on startup?
https://bugs.kde.org/show_bug.cgi?id=330639 hotmusic...@mail.bg changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[tellico] [Bug 357128] New: Series TMDb search?
https://bugs.kde.org/show_bug.cgi?id=357128 Bug ID: 357128 Summary: Series TMDb search? Product: tellico Version: 2.3.11 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: ro...@periapsis.org Reporter: deced...@gmail.com I want add "Penny Dreadful" series but when Tellico searches in TMDb database, shows 3 movies but no the series info. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357129] New: Plasma crash
https://bugs.kde.org/show_bug.cgi?id=357129 Bug ID: 357129 Summary: Plasma crash Product: plasmashell Version: 5.4.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: ra...@pisem.net CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.4.3) Qt Version: 5.5.0 Operating System: Linux 4.1.13-5-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: updated from 13.2 to 42.1 leap distro in init 3 using zypper and rebooted The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f10c18ad800 (LWP 1584))] Thread 7 (Thread 0x7f10a98d3700 (LWP 1586)): #0 0x7f10badfdc1d in poll () at /lib64/libc.so.6 #1 0x7f10bfd24422 in () at /usr/lib64/libxcb.so.1 #2 0x7f10bfd2600f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7f10ac055c29 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f10bb4f455f in () at /usr/lib64/libQt5Core.so.5 #5 0x7f10ba6070a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7f10bae0604d in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f10a1f76700 (LWP 1615)): #0 0x7f10b74dee22 in () at /usr/lib64/libglib-2.0.so.0 #1 0x7f10b74def7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #2 0x7f10bb725a5b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #3 0x7f10bb6cca63 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f10bb4ef84a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #5 0x7f10be7d85f8 in () at /usr/lib64/libQt5Qml.so.5 #6 0x7f10bb4f455f in () at /usr/lib64/libQt5Core.so.5 #7 0x7f10ba6070a4 in start_thread () at /lib64/libpthread.so.0 #8 0x7f10bae0604d in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f1096885700 (LWP 1625)): #0 0x7f10b74dc1df in () at /usr/lib64/libglib-2.0.so.0 #1 0x7f10b74de83f in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #2 0x7f10b74dedf8 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f10b74def7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f10bb725a5b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f10bb6cca63 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f10bb4ef84a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7f10be7d85f8 in () at /usr/lib64/libQt5Qml.so.5 #8 0x7f10bb4f455f in () at /usr/lib64/libQt5Core.so.5 #9 0x7f10ba6070a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7f10bae0604d in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f1094eca700 (LWP 1629)): #0 0x7f10bb726532 in () at /usr/lib64/libQt5Core.so.5 #1 0x7f10b74de8f1 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #2 0x7f10b74dedf8 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f10b74def7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f10bb725a5b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f10bb6cca63 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f10bb4ef84a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7f10be7d85f8 in () at /usr/lib64/libQt5Qml.so.5 #8 0x7f10bb4f455f in () at /usr/lib64/libQt5Core.so.5 #9 0x7f10ba6070a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7f10bae0604d in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f108f3d8700 (LWP 1630)): #0 0x7f10ba60b05f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f10c0f8b7eb in () at /usr/lib64/libQt5Script.so.5 #2 0x7f10c0f8b819 in () at /usr/lib64/libQt5Script.so.5 #3 0x7f10ba6070a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f10bae0604d in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f108c8e0700 (LWP 1631)): #0 0x7f10b74b00f0 in poll@plt () at /usr/lib64/libglib-2.0.so.0 #1 0x7f10b74dee64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f10b74def7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f10bb725a5b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f10bb6cca63 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f10bb4ef84a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f10bf36bf82 in () at /usr/lib64/libQt5Quick.so.5 #7 0x7f10bb4f455f in () at /usr/lib64/libQt5Core.so.5 #8 0x7f10ba6070a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f10bae0604d in clone ()
[zanshin] [Bug 357130] New: Not able to enable or add todo collection (existing (sub)calendar on ownCloud server)
https://bugs.kde.org/show_bug.cgi?id=357130 Bug ID: 357130 Summary: Not able to enable or add todo collection (existing (sub)calendar on ownCloud server) Product: zanshin Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: general Assignee: er...@kde.org Reporter: mat...@suklje.name CC: mbe...@ipsquad.net In the Sources pane I don’t have all the calendars/sources that exist. This might be due to me adding, hiding etc. sources in the beta where buttons were not that transparent at what they do. But now that I want to add/enable/show those sources, I don’t seem to be able in any way. There is no button, no right-click menu, nothing useful in the Settings menu, nothing I can find. Reproducible: Always Steps to Reproduce: 1. Try to add/show/enable (re)source of todos in the Source pane 2. Try right-clikcing on it 3. Check the Settings menu Actual Results: not being there Expected Results: being there :) Mageia 5 KDE 4.14.5 Zanshin compiled from Git from commit 40b0ee611b74cda9a07a57339ce2bbbeff755352 (a.k.a. 0.3_rc1) -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 354112] Ḥ/ḥ and Ḷ/ḷ characters are not included into Oxygen fonts
https://bugs.kde.org/show_bug.cgi?id=354112 --- Comment #1 from Enol P. --- 2 months and no reply about this issue. Are there problems? -- You are receiving this mail because: You are watching all bug changes.
[knotes] [Bug 347272] Unable to create notes. Error with collections
https://bugs.kde.org/show_bug.cgi?id=347272 Sunil changed: What|Removed |Added CC||funt...@yahoo.com --- Comment #1 from Sunil --- Any leads on this bug? knotes is a very useful app for me and I have used it for a long time but I am now running this error:( -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357131] New: plasma crash
https://bugs.kde.org/show_bug.cgi?id=357131 Bug ID: 357131 Summary: plasma crash Product: plasmashell Version: 5.4.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: ra...@pisem.net CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.4.3) Qt Version: 5.5.0 Operating System: Linux 4.1.13-5-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: updated online using zypper from 13.2 to 42.1 leap in init 3 root The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4e63f9c800 (LWP 2322))] Thread 7 (Thread 0x7f4e4bfc2700 (LWP 2324)): #0 0x7f4e5d4ecc1d in poll () at /lib64/libc.so.6 #1 0x7f4e62413422 in () at /usr/lib64/libxcb.so.1 #2 0x7f4e6241500f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7f4e4e744c29 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f4e5dbe355f in () at /usr/lib64/libQt5Core.so.5 #5 0x7f4e5ccf60a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7f4e5d4f504d in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f4e43fff700 (LWP 2334)): #0 0x7f4e5d501c84 in clock_gettime () at /lib64/libc.so.6 #1 0x7f4e5dc93b06 in () at /usr/lib64/libQt5Core.so.5 #2 0x7f4e5de13089 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #3 0x7f4e5de13615 in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so.5 #4 0x7f4e5de1482e in () at /usr/lib64/libQt5Core.so.5 #5 0x7f4e59bcd4ad in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #6 0x7f4e59bcdd80 in () at /usr/lib64/libglib-2.0.so.0 #7 0x7f4e59bcdf7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #8 0x7f4e5de14a5b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #9 0x7f4e5ddbba63 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #10 0x7f4e5dbde84a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #11 0x7f4e60ec75f8 in () at /usr/lib64/libQt5Qml.so.5 #12 0x7f4e5dbe355f in () at /usr/lib64/libQt5Core.so.5 #13 0x7f4e5ccf60a4 in start_thread () at /lib64/libpthread.so.0 #14 0x7f4e5d4f504d in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f4e38f57700 (LWP 2335)): #0 0x7f4e5ccfc7bc in __lll_lock_wait () at /lib64/libpthread.so.0 #1 0x7f4e5ccf84a4 in _L_lock_986 () at /lib64/libpthread.so.0 #2 0x7f4e5ccf8306 in pthread_mutex_lock () at /lib64/libpthread.so.0 #3 0x7f4e58feee90 in () at /usr/X11R6/lib64/libGL.so.1 #4 0x7f4e58ff241e in () at /usr/X11R6/lib64/libGL.so.1 #5 0x7f4e58ff281b in () at /usr/X11R6/lib64/libGL.so.1 #6 0x7f4e55689fc0 in () at /usr/lib64/tls/libnvidia-tls.so.340.93 #7 0x7f4e59c0eb60 in () at /usr/lib64/libglib-2.0.so.0 #8 0x7f4e59bcd999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #9 0x7f4e59bcddf8 in () at /usr/lib64/libglib-2.0.so.0 #10 0x7f4e59bcdf7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #11 0x7f4e5de14a5b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #12 0x7f4e5ddbba63 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #13 0x7f4e5dbde84a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #14 0x7f4e60ec75f8 in () at /usr/lib64/libQt5Qml.so.5 #15 0x7f4e5dbe355f in () at /usr/lib64/libQt5Core.so.5 #16 0x7f4e5ccf60a4 in start_thread () at /lib64/libpthread.so.0 #17 0x7f4e5d4f504d in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f4e33480700 (LWP 2339)): #0 0x7f4e5ccfc7bc in __lll_lock_wait () at /lib64/libpthread.so.0 #1 0x7f4e5ccf84a4 in _L_lock_986 () at /lib64/libpthread.so.0 #2 0x7f4e5ccf8306 in pthread_mutex_lock () at /lib64/libpthread.so.0 #3 0x7f4e58feee90 in () at /usr/X11R6/lib64/libGL.so.1 #4 0x7f4e58ff241e in () at /usr/X11R6/lib64/libGL.so.1 #5 0x7f4e58ff281b in () at /usr/X11R6/lib64/libGL.so.1 #6 0x7f4e55689fc0 in () at /usr/lib64/tls/libnvidia-tls.so.340.93 #7 0x7f4e59c0eb60 in () at /usr/lib64/libglib-2.0.so.0 #8 0x7f4e59bcd999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #9 0x7f4e59bcddf8 in () at /usr/lib64/libglib-2.0.so.0 #10 0x7f4e59bcdf7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #11 0x7f4e5de14a5b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #12 0x7f4e5ddbba63 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #13 0x7f4e5dbde84a in QThread::exec() () at /usr/lib64/
[Spectacle] [Bug 356765] Spectacle doesn't work properly with QT_DEVICE_PIXEL_RATIO=2
https://bugs.kde.org/show_bug.cgi?id=356765 Weng Xuetian changed: What|Removed |Added Resolution|REMIND |DUPLICATE Status|NEEDSINFO |RESOLVED --- Comment #2 from Weng Xuetian --- *** This bug has been marked as a duplicate of bug 357022 *** -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 357022] Region selection screen does not take into account device pixel ratio
https://bugs.kde.org/show_bug.cgi?id=357022 Weng Xuetian changed: What|Removed |Added CC||wen...@gmail.com --- Comment #4 from Weng Xuetian --- *** Bug 356765 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357131] plasma crash
https://bugs.kde.org/show_bug.cgi?id=357131 --- Comment #1 from Rafis Kamaliev --- *** Bug 357129 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357129] Plasma crash
https://bugs.kde.org/show_bug.cgi?id=357129 Rafis Kamaliev changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Rafis Kamaliev --- *** This bug has been marked as a duplicate of bug 357131 *** -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 356870] Okteta doesn't support table files/custom character encodings.
https://bugs.kde.org/show_bug.cgi?id=356870 --- Comment #2 from Jeremy Andrews --- Yes, these are all one byte / one char encodings. I could probably make it work for my personal use by modifying the EBCDIC encoding file, and playing with the arrays and recompiling every time I wanted to use a new encoding. I was just thinking that a table file system could be useful for a lot of people if someone that knew enough to implement it correctly did it. Currently, I'm using a Windows-based hex editor in WINE because no Linux hex editor supports what I want to do. Well, if the structures tool view can be used to display text in different encodings, then it would be fine. But it mostly seems to put labels on various blocks of bytes instead. I'm not sure if there's another mode that does what I'm wanting, though. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 357132] New: Trying to open a file fromm a network drive causes an error
https://bugs.kde.org/show_bug.cgi?id=357132 Bug ID: 357132 Summary: Trying to open a file fromm a network drive causes an error Product: krita Version: 2.9.9 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: tylerecout...@gmail.com Krita can't open files from a network drive Reproducible: Always Steps to Reproduce: 1a. Drag an image file from a network drive into Krita OR 1b. File > Open any kind of file format (kra, png, jpg, etc) from a network drive With Krita closed, double clicking a .kra file on a network drive will open it in Krita Actual Results: Win 10, Krita 2.9.9: Unknown error code -2 File doesn't open Expected Results: File opens Tried on my home NAS, from Win10, Krita 2.9.9 --> Unknown error code -2 Tried from a school network from Win8, Krita 2.9.10 Also reported by others on IRC, including Samab network. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 357132] Trying to open a file fromm a network drive causes an error
https://bugs.kde.org/show_bug.cgi?id=357132 --- Comment #1 from tylerecout...@gmail.com --- >From IRC: boud - hmm I actually think deevad has reported a similar problem when accessing krita files on a samba share from linux Atirk - i can reproduce the error on windows 7 Atirk - i just did the same thing. trying to access files on a network drive doesn't seem to work. it says file does not exist. so it's not just him -- You are receiving this mail because: You are watching all bug changes.
[khotkeys] [Bug 352067] new key binding does not work
https://bugs.kde.org/show_bug.cgi?id=352067 --- Comment #2 from Thomas Lübking --- Still a problem after the patch? -- You are receiving this mail because: You are watching all bug changes.
[khotkeys] [Bug 354253] Windows key can not be addressed
https://bugs.kde.org/show_bug.cgi?id=354253 --- Comment #1 from Thomas Lübking --- Is this only a khotkeys problem, not affecting other global shortcuts (eg. to show krunner etc.)? Please notice that config writing pre-5.5 is known to be buggy, so please ensure to check whether the issue remains with 5.5. -- You are receiving this mail because: You are watching all bug changes.
[khotkeys] [Bug 348859] Tried to install a hotkey (Meta-C) to implement a shell program talk.sh. Hotkey didn't work.
https://bugs.kde.org/show_bug.cgi?id=348859 --- Comment #3 from Thomas Lübking --- Please notice that config writing pre-5.5 is known to be buggy, please check whether it's still an issue with 5.5. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 353926] Global shortcuts using wrong layout
https://bugs.kde.org/show_bug.cgi?id=353926 Thomas Lübking changed: What|Removed |Added CC||kim.lindber...@gmail.com --- Comment #5 from Thomas Lübking --- *** Bug 355729 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[khotkeys] [Bug 355729] Shortcut is bound to qwerty layout even if dvorak is active
https://bugs.kde.org/show_bug.cgi?id=355729 Thomas Lübking changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Thomas Lübking --- *** This bug has been marked as a duplicate of bug 353926 *** -- You are receiving this mail because: You are watching all bug changes.
[kxkb] [Bug 355788] shift-shift does not switch keyboard layout
https://bugs.kde.org/show_bug.cgi?id=355788 Thomas Lübking changed: What|Removed |Added Product|khotkeys|kxkb Component|general |general Version|5.4.2 |unspecified Assignee|k...@michael-jansen.biz |ary...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[khotkeys] [Bug 352073] "http://ksnapshot/" is opened in web browser if KSnapshot is not installed
https://bugs.kde.org/show_bug.cgi?id=352073 Thomas Lübking changed: What|Removed |Added CC||m...@baloneygeek.com --- Comment #2 from Thomas Lübking --- Spectacle authors promised to provide a hotkey definition update? -- You are receiving this mail because: You are watching all bug changes.
[khotkeys] [Bug 356296] Unable to edit a custom shortcut a second time
https://bugs.kde.org/show_bug.cgi?id=356296 Thomas Lübking changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #2 from Thomas Lübking --- Yupp, fixed it (was broken all along KDE 5... khotkeys is apparently unmaintained) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 350816] kglobalaccel5 load the wrong keyboard mapping/layout
https://bugs.kde.org/show_bug.cgi?id=350816 Thomas Lübking changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=353926 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 353926] Global shortcuts using wrong layout
https://bugs.kde.org/show_bug.cgi?id=353926 Thomas Lübking changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=350816 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 344567] Cannot create a new session
https://bugs.kde.org/show_bug.cgi?id=344567 Leo Davis changed: What|Removed |Added CC||lda...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 344879] memory leak in plasmashell - huge ram usage
https://bugs.kde.org/show_bug.cgi?id=344879 --- Comment #107 from AnAkkk --- I never had swap enabled, and didn't use infinality either. For some reason I haven't had the issue the last few days though, it looks like it fixed itself for me. I have no idea what changed, maybe this is after I updated to Plasma 5.5.2. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 357133] New: Please merge numpad +-,*/ (and perhaps numbers) with alphanumeric counterparts
https://bugs.kde.org/show_bug.cgi?id=357133 Bug ID: 357133 Summary: Please merge numpad +-,*/ (and perhaps numbers) with alphanumeric counterparts Product: frameworks-kglobalaccel Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: mgraess...@kde.org Reporter: thomas.luebk...@gmail.com CC: kdelibs-b...@kde.org QKeySequence (ie. the local action system) doesn't distinguish between them and (thus?) KKeySequenceButton and the other suspects do neither (you get "Ctrl++" whether you used the alphanum or the num block to enter it) In a way this is a regression (because one could distinguish years before and the keys are treated different by X11 and Qt sets the Qt::KeypadModifier on the event, but status quo is that the mentioned numeric block keys are virtually dead as shortcuts. So better take them as equivalent? Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 357025] Application crash on creating new row
https://bugs.kde.org/show_bug.cgi?id=357025 --- Comment #4 from Jarosław Staniek --- Yes, there are also related remarks in the wish https://bugs.kde.org/show_bug.cgi?id=332161. In the context of the db posted by you, after running this: insert into frames values (1, 0,0,0,"abc"); and this select "exists" from frames; -- the result will be: 0 And running this: select "exists1" from frames; returns: exists1 So a dangerous combination. Future Kexi will have support for proper identifier escaping, probably using []. The easiest approach we can use now, for Kexi 2.9, is to raise error in Table Designer for reserved words so tables with reserved words as identifiers cannot be even created. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 357133] Please merge numpad +-,*/ (and perhaps numbers) with alphanumeric counterparts
https://bugs.kde.org/show_bug.cgi?id=357133 Thomas Lübking changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=183458, ||https://bugs.kde.org/show_b ||ug.cgi?id=346806 -- You are receiving this mail because: You are watching all bug changes.
