[neon] [Bug 371000] qtbase-abi conflicts with the current qtcreator package
https://bugs.kde.org/show_bug.cgi?id=371000 Roland Vet changed: What|Removed |Added CC|vet.rol...@gmail.com| -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411629] Syncthingtray in system tray causes crash
https://bugs.kde.org/show_bug.cgi?id=411629 --- Comment #1 from Roland Vet --- Also reported in the syncthingtray issue tracker [1] in case it's a problem on that end. [1] https://github.com/Martchus/syncthingtray/issues/55 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411629] New: Syncthingtray in system tray causes crash
https://bugs.kde.org/show_bug.cgi?id=411629 Bug ID: 411629 Summary: Syncthingtray in system tray causes crash Product: plasmashell Version: 5.16.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: vet.rol...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.16.5) Qt Version: 5.13.0 Frameworks Version: 5.61.0 Operating System: Linux 5.2.11-arch1-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: plasmashell crashes at log in/immediately when syncthingtray is installed/in the system tray widget. No syncthingtray -> no crash No system tray widget -> no crash Then adding system tray widget back -> crash The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1e4c279880 (LWP 27476))] Thread 12 (Thread 0x7f1e155a7700 (LWP 28085)): #0 0x7f1e50259415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f1e50d8a5a0 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f1e50d8a692 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f1e52b6e7bd in () at /usr/lib/libQt5Quick.so.5 #4 0x7f1e52b6ea6e in () at /usr/lib/libQt5Quick.so.5 #5 0x7f1e50d84520 in () at /usr/lib/libQt5Core.so.5 #6 0x7f1e5025357f in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f1e50a130e3 in clone () at /usr/lib/libc.so.6 Thread 11 (Thread 0x7f1e14d02700 (LWP 28047)): #0 0x7f1e50259415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f1e50d8a5a0 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f1e50d8a692 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f1e52b6e7bd in () at /usr/lib/libQt5Quick.so.5 #4 0x7f1e52b6ea6e in () at /usr/lib/libQt5Quick.so.5 #5 0x7f1e50d84520 in () at /usr/lib/libQt5Core.so.5 #6 0x7f1e5025357f in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f1e50a130e3 in clone () at /usr/lib/libc.so.6 Thread 10 (Thread 0x7f1e15e67700 (LWP 27902)): #0 0x7f1e50259415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f1e50d8a5a0 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f1e50d8a692 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f1e52b6e7bd in () at /usr/lib/libQt5Quick.so.5 #4 0x7f1e52b6ea6e in () at /usr/lib/libQt5Quick.so.5 #5 0x7f1e50d84520 in () at /usr/lib/libQt5Core.so.5 #6 0x7f1e5025357f in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f1e50a130e3 in clone () at /usr/lib/libc.so.6 Thread 9 (Thread 0x7f1e16e5a700 (LWP 27867)): #0 0x7f1e50a08667 in poll () at /usr/lib/libc.so.6 #1 0x7f1e4f22fa80 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f1e4f22fb51 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f1e50fa99bc in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f1e50f505ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f1e50d832f5 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f1e50d84520 in () at /usr/lib/libQt5Core.so.5 #7 0x7f1e5025357f in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f1e50a130e3 in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7f1e17ee6700 (LWP 27835)): #0 0x7f1e50a0418c in read () at /usr/lib/libc.so.6 #1 0x7f1e4f1e09f0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f1e4f22e311 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7f1e4f22fa28 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f1e4f22fb51 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7f1e50fa99bc in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f1e50f505ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7f1e50d832f5 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7f1e50d84520 in () at /usr/lib/libQt5Core.so.5 #9 0x7f1e5025357f in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f1e50a130e3 in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7f1e33fff700 (LWP 27609)): #0 0x7f1e50a08667 in poll () at /usr/lib/libc.so.6 #1 0x7f1e4f22fa80 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f1e4f22fb51 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f1e50fa99bc in QEventDispatcherGlib::processEvents(QFlags) () at
[systemsettings] [Bug 394778] Bluetooth adapter not visible warning
https://bugs.kde.org/show_bug.cgi?id=394778 Roland Vet changed: What|Removed |Added CC||vet.rol...@gmail.com --- Comment #6 from Roland Vet --- Is the addition of a 'dismiss' button/cross an idea? The 'not visible' warning message (which imo should be a info message) is eye catching and causes the Bluetooth Devices menu to have scroll bar. Being able to dismiss the message should be an option. Should I create a separate bug to discuss this? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 383181] [Request] Build i386 packages for i.a. wayland packages.
https://bugs.kde.org/show_bug.cgi?id=383181 --- Comment #8 from Roland Vet <vet.rol...@gmail.com> --- Sorry to harp on this issue, but again I ran into a situation where I wanted to install i386 packages but was ultimately stopped by a dependency blocked by a missing i386 build. In this case package: 'libharfbuzz0b' -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 388983] Systemsettings crashes setting "Default Web Shortcut"
https://bugs.kde.org/show_bug.cgi?id=388983 Roland Vet <vet.rol...@gmail.com> changed: What|Removed |Added CC|vet.rol...@gmail.com| -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 389133] New: Exiting Web Shortcuts crashes System Settings
https://bugs.kde.org/show_bug.cgi?id=389133 Bug ID: 389133 Summary: Exiting Web Shortcuts crashes System Settings Product: systemsettings Version: 5.11.5 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: vet.rol...@gmail.com Target Milestone: --- Application: systemsettings5 (5.11.5) Qt Version: 5.9.3 Frameworks Version: 5.42.0 Operating System: Linux 4.14.13-041413-generic x86_64 Distribution: KDE neon User Edition 5.11 -- Information about the crash: - What I was doing when the application crashed: When clicking through the shortcut menus/tabs system settings crashes after attempting to open after opening the Web Shortcuts menu. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fddd0a128c0 (LWP 1729))] Thread 18 (Thread 0x7fdd75497700 (LWP 1777)): #0 0x7fddc6704a79 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fddc66c0290 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fddc66c0712 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fdd757809d6 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x7fddc66e6bb5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fddc85476ba in start_thread (arg=0x7fdd75497700) at pthread_create.c:333 #6 0x7fddcc72f3dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 17 (Thread 0x7fdd778c5700 (LWP 1776)): #0 0x7fddcc71f24d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fddc67036f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fddc66bfe74 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fddc66c0330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fddc66c049c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fddc66c04d9 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7fddc66e6bb5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7fddc85476ba in start_thread (arg=0x7fdd778c5700) at pthread_create.c:333 #8 0x7fddcc72f3dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 16 (Thread 0x7fdd7e865700 (LWP 1769)): #0 0x7fddcc71f24d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fddc67036f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fddc66bfe74 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fddc66c0330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fddc66c049c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fddcd04a6cb in QEventDispatcherGlib::processEvents (this=0x7fdd78c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7fddccff2e2a in QEventLoop::exec (this=this@entry=0x7fdd7e864ce0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #7 0x7fddcce1b8f4 in QThread::exec (this=this@entry=0x19bea50) at thread/qthread.cpp:515 #8 0x7fddcaed0d25 in QQmlThreadPrivate::run (this=0x19bea50) at qml/ftw/qqmlthread.cpp:147 #9 0x7fddcce20709 in QThreadPrivate::start (arg=0x19bea50) at thread/qthread_unix.cpp:368 #10 0x7fddc85476ba in start_thread (arg=0x7fdd7e865700) at pthread_create.c:333 #11 0x7fddcc72f3dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 15 (Thread 0x7fdd7700 (LWP 1747)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fddaab773cb in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #2 0x7fddaab772e8 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #3 0x7fddc85476ba in start_thread (arg=0x7fdd7700) at pthread_create.c:333 #4 0x7fddcc72f3dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 14 (Thread 0x7fdd959fd700 (LWP 1746)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fddaab773cb in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #2 0x7fddaab772e8 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #3 0x7fddc85476ba in start_thread (arg=0x7fdd959fd700) at pthread_create.c:333 #4 0x7fddcc72f3dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 13 (Thread 0x7fdd961fe700 (LWP 1745)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fddaab773cb in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #2 0x7fddaab772e8 in ?? () from
[neon] [Bug 383181] [Request] Build i386 packages for i.a. wayland packages.
https://bugs.kde.org/show_bug.cgi?id=383181 --- Comment #7 from Roland Vet <vet.rol...@gmail.com> --- ^ my bad, can someone delete this comment and the previous one? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 383181] [Request] Build i386 packages for i.a. wayland packages.
https://bugs.kde.org/show_bug.cgi?id=383181 --- Comment #6 from Roland Vet <vet.rol...@gmail.com> --- Changed the title for a better fit. (In reply to Jonathan Riddell from comment #1) > It's because we don't build i386 packages. It's on the todo but not very > high priority. > > Why do you need i386 packages? > > Jonathan Hello Jonathan, any updates on building i386 packages? Out of curiosity, why not build i386? Is it a technical challenge or in a attempt to save resources? (In reply to Adam Lyall from comment #4) > I can confirm this issue with installing 32bit. It can be worked around by > installing the ubuntu repo version 1.12.0-1~ubuntu16.04.1 for both the > x86_64 and i386 versions. > ``` > apt install libwayland-client0=1.12.0-1~ubuntu16.04.1 > libwayland-client0:i386=1.12.0-1~ubuntu16.04.1 > ``` > should do the job. The issue seems to be with the packaging of > libwayland-client0:i386 as the one in the Neon repository refuses to install > next to the x86_64 version but the ones from other repositories is fine. > > I'm also using Padoka pkppa ppa. > > Note that 32bit Mesa is needed for the majority of proprietary games on > Linux. This does indeed work; downgrading the libwayland-client0 package to a version that is also built for i386. Optional is then to also pin the neon package with a lower priority so it does not show up as a 'not upgraded' package. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 383181] [Request] Build i386 packages for i.a. wayland packages.
https://bugs.kde.org/show_bug.cgi?id=383181 Roland Vet <vet.rol...@gmail.com> changed: What|Removed |Added Summary|'fix' dependencies to allow |[Request] Build i386 |for updated mesa i386 |packages for i.a. wayland |drivers |packages. --- Comment #5 from Roland Vet <vet.rol...@gmail.com> --- Changed the title for a better fit. (In reply to Jonathan Riddell from comment #1) > It's because we don't build i386 packages. It's on the todo but not very > high priority. > > Why do you need i386 packages? > > Jonathan Hello Jonathan, any updates on building i386 packages? Out of curiosity, why not build i386? Is it a technical challenge or in a attempt to save resources? (In reply to Adam Lyall from comment #4) > I can confirm this issue with installing 32bit. It can be worked around by > installing the ubuntu repo version 1.12.0-1~ubuntu16.04.1 for both the > x86_64 and i386 versions. > ``` > apt install libwayland-client0=1.12.0-1~ubuntu16.04.1 > libwayland-client0:i386=1.12.0-1~ubuntu16.04.1 > ``` > should do the job. The issue seems to be with the packaging of > libwayland-client0:i386 as the one in the Neon repository refuses to install > next to the x86_64 version but the ones from other repositories is fine. > > I'm also using Padoka pkppa ppa. > > Note that 32bit Mesa is needed for the majority of proprietary games on > Linux. This does indeed work; downgrading the libwayland-client0 package to a version that is also built for i386. Optional is then to also pin the neon package with a lower priority so it does not show up as a 'not upgraded' package. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385644] Memory leak freed by *starting* plasmashell
https://bugs.kde.org/show_bug.cgi?id=385644 --- Comment #3 from Roland Vet <vet.rol...@gmail.com> --- Not exactly proof, but this is a before and after a restart. $ free -h totalusedfree shared buff/cache available Mem:15G9.1G158M5.7G6.3G344M Swap: 15G1.9G 13G $ killall plasmashell && kstart plasmashell $ free -h totalusedfree shared buff/cache available Mem:15G7.1G7.5G128M996M7.9G Swap: 15G7.0M 15G ~9G of memory freed by performing the restart, and all I can do is promise that just the killing of plasmashell doesn't give this result. Do not know what else I can provide to confirm. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385644] Memory leak freed by *starting* plasmashell
https://bugs.kde.org/show_bug.cgi?id=385644 --- Comment #2 from Roland Vet <vet.rol...@gmail.com> --- (In reply to David Edmundson from comment #1) > That's not how Linux memory works. This is just what I observe. My guess is that in the process of starting plasmashell something else gets restarted which clears the leak. I can't pinpoint what the memory is being used for. All I know is that over the duration of a few hours the used memory pages increases to the point where swapping starts and eventually the entire system slows down to an unbearable crawl. If you could help me pinpoint the source I might be able to be more descriptive. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385644] New: Memory leak freed by *starting* plasmashell
https://bugs.kde.org/show_bug.cgi?id=385644 Bug ID: 385644 Summary: Memory leak freed by *starting* plasmashell Product: plasmashell Version: 5.10.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: vet.rol...@gmail.com Target Milestone: 1.0 Created attachment 108295 --> https://bugs.kde.org/attachment.cgi?id=108295=edit Example of high unreported memory consumption. Memory consumption of an unknown process (not listed in (h)top) becomes all consuming, taking up all available ram+swap space. The memory is not released after killing plasmashell (killall plasmashell) but is when restarting it (kstart plasmashell). -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 383181] 'fix' dependencies to allow for updated mesa i386 drivers
https://bugs.kde.org/show_bug.cgi?id=383181 --- Comment #2 from Roland Vet <vet.rol...@gmail.com> --- It's a steam requirement. Steam doesn't run unless the 32 bit drivers are also installed. Fwiw the git branch (https://launchpad.net/~paulo-miguel-dias/+archive/ubuntu/mesa) does not cause package conflicts. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 383181] New: 'fix' dependencies to allow for updated mesa i386 drivers
https://bugs.kde.org/show_bug.cgi?id=383181 Bug ID: 383181 Summary: 'fix' dependencies to allow for updated mesa i386 drivers Product: neon Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: vet.rol...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- Created attachment 107096 --> https://bugs.kde.org/attachment.cgi?id=107096=edit Output of apt when attempting to upgrade the mesa packages. Using the Padoka stable ppa to upgrade the (i386) mesa drivers (https://launchpad.net/~paulo-miguel-dias/+archive/ubuntu/pkppa) is not possible due to a package conflict. Attached are some example conflict issues. (aptconflicts.txt). The package of interest is libgl1-mesa-glx:i386 but attempting installation results in: The following packages have unmet dependencies. libgl1-mesa-glx:i386 : Depends: libwayland-client0:i386 (>= 1.11.0) but it is not going to be installed Trying to issue a command to install both packages requires removal of ~500 packages. Uncertain where the conflict is exactly. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 380509] lock screen doesn't accept password, timeout to suspend doesn't suspend
https://bugs.kde.org/show_bug.cgi?id=380509 Roland Vet <vet.rol...@gmail.com> changed: What|Removed |Added CC||vet.rol...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 371000] qtbase-abi conflicts with the current qtcreator package
https://bugs.kde.org/show_bug.cgi?id=371000 Roland Vet <vet.rol...@gmail.com> changed: What|Removed |Added CC||vet.rol...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 183458] Numpad (keypad) keys not mapped correctly when setting Global Shortcuts
https://bugs.kde.org/show_bug.cgi?id=183458 Roland Vet <vet.rol...@gmail.com> changed: What|Removed |Added CC||vet.rol...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
