Bug#1071080: Info received ((no subject))

Hello, I have correction to make, this error has just happened on 6.1.0-20-amd64 as well. So, it maybe deeper than latest kernel update. [50044.905648] [ cut here ] [50044.905651] WARNING: CPU: 12 PID: 1162 at

Bug#1071080: (no subject)

Dear Maintainer, I booted back to kernel 6.1.0-20-amd64 (previous kernel), and errors are no more. Everything is clean and stable like it used to. This seems to be a regression in 6.1.0-21-amd64.

Bug#1071080: Info received (Bug#1071080: Acknowledgement (linux-image-6.1.0-21-amd64: segfault at amdgpu_dm_atomic_commit_tail))

Looks like this error is persistent, it happened again. Same session still, no adverse effects from it so far. [44372.983756] [ cut here ] [44372.983762] amdgpu :10:00.0: drm_WARN_ON(atomic_read(>refcount) == 0) [44372.983807] WARNING: CPU: 0 PID: 0 at

Bug#1071080: Acknowledgement (linux-image-6.1.0-21-amd64: segfault at amdgpu_dm_atomic_commit_tail)

More crashes followed. I have not restarted my computer, it's still the same session. These errors have not happened before in previous linux kernel versions in Debian Stable. Maybe it's a regression? Headers of the crashes: amdgpu :10:00.0: drm_WARN_ON(atomic_read(>refcount) == 0)

Bug#1071080: linux-image-6.1.0-21-amd64: segfault at amdgpu_dm_atomic_commit_tail

Package: src:linux Version: 6.1.90-1 Severity: normal X-Debbugs-Cc: pior...@gmx.com Dear Maintainer, Today I found crash in linux kernel. Related to AMD Radeon graphics card I use. I have not seen it on previous versions of Linux kernel in Debian Stable. I was away from the computer at the

Bug#1054152: rasdaemon: frequent crashes of rasdaemon

(tai271828) wrote: Hi piorunz, The issue and the corresponding backport should have been included in the latest version in unstable/testing with version 0.8.0-2. If you have a moment, would you mind a try? Cheers, Tai On Sat, Jan 6, 2024 at 11:30 AM piorunz wrote: Hello Tai, Thanks for your

Bug#1054152: rasdaemon: frequent crashes of rasdaemon

Hello Tai, Thanks for your reply. Patch attached, for Debian Stable, following this commit for upstream version: https://github.com/mchehab/rasdaemon/commit/f1ea76375281001cdf4a048c1a4a24d86c6fbe48 It's 1 line change in 1 file (ras-events.c). --- ras-events.c2024-01-06

Bug#1054152: Info received (Bug#1054152: rasdaemon: frequent crashes of rasdaemon)

Hi all, I can happily report no further crashes of rasdaemon. And no SIGBUS, since one-line patch. If you prefer, you can close this bug report. I will report once again if I have any more problems. And SIGBUS patch definitely worth importing to Debian Stable for wider audience if this has not

Bug#1054152: rasdaemon: frequent crashes of rasdaemon

On 11/12/2023 14:20, Russell Coker wrote: We have 2 different issues here. The first one is a SEGV related to sqlite, that might be a sqlite bug. Have you tried writing a simple sqlite program or using a sqlite utility to see if it also crashes? Sorry, I have no ability to write such a

Bug#1054152: rasdaemon: frequent crashes of rasdaemon

or not. On 11/12/2023 12:20, Taihsiang Ho (tai271828) wrote: Hi Piorunz, Do you mind verifying if your issue is related to https://github.com/mchehab/rasdaemon/issues/77 ? If yes, we can consider to backport the corresponding upstream fix. Kind regards, Tai On Mon, Dec 11, 2023 at 10:15 AM piorunz wrote

Bug#1054152: rasdaemon: frequent crashes of rasdaemon

On 11/12/2023 04:20, Russell Coker wrote: If you stop rasdaemon, move aside /var/lib/rasdaemon/ras-mc_event.db, and then start it again does it still crash? Thanks for your reply. I stopped the service, moved ras-mc_event.db, and started service again. File has been recreated. No crashes so

Bug#1054152: (no subject)

My apologies for not including resolved process threads in debugging output. I just installed rasdaemon-dbgsym. Here are two latest backtraces from yesterday, please note that one process is ending with SIGBUS signal, one with SIGSEGV signal. sudo coredumpctl list --no-pager | grep rasdaemon |

Bug#1054152: Acknowledgement (rasdaemon: frequent crashes of rasdaemon)

Crash from two days ago seems to be exactly the same. gdb bt attached.$ export DEBUGINFOD_URLS="https://debuginfod.debian.net; && sudo coredumpctl debug 2983550 PID: 2983550 (rasdaemon) UID: 0 (root) GID: 0 (root) Signal: 7 (BUS) Timestamp: Sun

Bug#1054152: rasdaemon: frequent crashes of rasdaemon

Package: rasdaemon Version: 0.6.8-1.1 Severity: important X-Debbugs-Cc: pior...@gmx.com Dear Maintainer, rasdaemon crashes frequently on my system. No user input is required at all. I just find crash logs in dmesg every now and then. crash from today: attached in dmesg.txt file gdb backtrace:

Bug#1037557: Acknowledgement (plasma-workspace: krunner crash almost everytime when start typing)

On 20/08/2023 19:26, Patrick Franz wrote: Hi, FYI, I've requested plasma-workspace to be updated in Debian Stable and will upload the fix to bookworm once the request is approved. That's amazing Patrick, thank you! ❤️ -- With kindest regards, Piotr. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal

Bug#1037557: plasma-workspace: krunner crash almost everytime when start typing

On 16/08/2023 21:01, Patrick Franz wrote: Hej Piotr, I've backported the fix to Plasma 5.27.5. Can you please be so kind and test it ? You can find the updated packages at https://people.debian.org/~deltaone/plasma-workspace/ Hi Patrick, I installed it and it's working! No more crashes. I

Bug#1037557: Info received (Bug#1037557: Acknowledgement (plasma-workspace: krunner crash almost everytime when start typing))

On 13/08/2023 18:56, Patrick Franz wrote: Hi, I was able to reproduce the bug on bookworm, but it is solved for me in testing ans unstable. Is it maybe this bug ? https://bugs.kde.org/show_bug.cgi?id=470219 That is solved in Plasma 5.27.6... Hi Patrick, Yes, exactly! I was able to dig this

Bug#1037557: Info received (Bug#1037557: Acknowledgement (plasma-workspace: krunner crash almost everytime when start typing)))))

Upstream bug report has been opened: https://bugs.kde.org/show_bug.cgi?id=473339

Bug#1037557: Info received (Bug#1037557: Info received (Bug#1037557: Info received (Bug#1037557: Acknowledgement (plasma-workspace: krunner crash almost everytime when start typing))))

Full gbd run with debuginfod symbols: $ gdb krunner GNU gdb (Debian 13.1-3) 13.1 Copyright (C) 2023 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO

Bug#1037557: Info received (Bug#1037557: Info received (Bug#1037557: Acknowledgement (plasma-workspace: krunner crash almost everytime when start typing)))

Crashing krunner directly from terminal, with gdb on: $ gdb krunner GNU gdb (Debian 13.1-3) 13.1 Copyright (C) 2023 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it.

Bug#1037557: Acknowledgement (plasma-workspace: krunner crash almost everytime when start typing)

Another crash just now, this one has subtly different stack trace.$ debug 2804705 PID: 2804705 (krunner) UID: 1000 (pioruns) GID: 1000 (pioruns) Signal: 11 (SEGV) Timestamp: Wed 2023-06-14 11:02:17 BST (1h 37min ago) Command Line: /usr/bin/krunner

Bug#1037557: plasma-workspace: krunner crash almost everytime when start typing

Package: plasma-workspace Version: 4:5.27.5-2 Severity: important X-Debbugs-Cc: pior...@gmx.com Dear Maintainer, I am experiencing krunner crash almost every time I start type something. For example I start typing 20491+20 and krunner dissapears, with notification from KDE Crash Handler,

Bug#1029810: dolphin / ark: Error when unpacking RAR archive while unrar is not installed

Package: dolphin Version: 4:22.12.1-1 Severity: normal X-Debbugs-Cc: pior...@gmx.com Dear Maintainer, How to reproduce: Make sure unrar and unrar-free packages are NOT installed. Right click on some RAR file, Extract -> Extract archive here * What was the outcome of this action? Dolphin will

Bug#1029774: kdepim-runtime: akonadi_imap_resource crashed with SIGSEGV

Package: kdepim-runtime Version: 4:22.12.0-2 Severity: normal X-Debbugs-Cc: pior...@gmx.com Dear Maintainer, Today I've noticed akonadi_imap_resource from kdepim-runtime has registered a SIGSEGV crash in my logs. Sending all details including backtrace below. System is Debian Testing AMD64,

Bug#1028197: plasmashell: Program terminated with signal SIGSEGV

On 24/01/2023 00:05, Bernhard Übelacker wrote: Am 24.01.23 um 00:30 schrieb piorunz: On 23/01/2023 22:46, Bernhard Übelacker wrote: https://bugs.debian.org/1028197 On Mon, 23 Jan 2023 21:48:23 + piorunz wrote: On 23/01/2023 13:35, Bernhard Übelacker wrote:   journalctl --user --since

Bug#1028208: plasma-discover: Program terminated with signal SIGSEGV

On 23/01/2023 13:35, Bernhard Übelacker wrote: (gdb) bt #0  0x7fbffc2a9ccc in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #1  0x7fbffc25aef2 in raise () from /lib/x86_64-linux-gnu/libc.so.6 #2  0x7fbffe79dbe1 in KCrash::defaultCrashHandler(int) () from

Bug#1028208: plasma-discover: Program terminated with signal SIGSEGV

Package: plasma-discover Version: 5.26.4-1+b1 Severity: normal X-Debbugs-Cc: pior...@gmx.com Dear Maintainer, I just noticed crash of plasma-discover on my Debian Testing machine. I am using Debian Testing, fully updated, on AMD64 machine with ECC RAM and RAID1 storage. Full gdb backtrace

Bug#1028197: plasmashell: Program terminated with signal SIGSEGV

Package: plasma-workspace Version: 4:5.26.4.1-1+b1 Severity: important X-Debbugs-Cc: pior...@gmx.com Dear Maintainer, plasmashell is crashing very often on Debian Testing. Latest crash happened just now, segmentation fault. Plasmashell, along with all icons and panels disappeared completely and

Bug#1026062: kded5: kded crashes with signal 11

Package: kded5 Version: 5.101.0-1 Followup-For: Bug #1026062 X-Debbugs-Cc: pior...@gmx.com Dear Maintainer, I can also observe this problem. Just booted my computer, first I see in "sudo coredumpctl list", is freshly crashed kded5: $ sudo coredumpctl list Sat 2023-01-07 08:09:54 GMT5500

Bug#1026984: Possible fix for pan crash

Hello Dominique, Fix 100% fixed this problem, I can browse this particular group again :) On 29/12/2022 10:14, Dominique Dumont wrote: Hi piorunz, could you try the fix proposed there: https://gitlab.gnome.org/GNOME/pan/-/merge_requests/41 All the best Dod -- With kindest regards

Bug#1026984: Info received (Bug#1026984: Acknowledgement (pan: segfault when opening a newsgroup))

I've managed to download symbols and run gdb again: coredumpctl gdb 3417359 bt (32000+ lines omitted) last 10 lines: #32622 0x563c46ae0e1f in pan::NNTP::on_socket_response (this=0x563c479e5bd0, sock=, line_in=...) at ./pan/tasks/nntp.cc:317 #32623 0x563c46b0e931 in

Bug#1012843: i2pd: Default install SEGV

(I tried to send this report from Reportbug but that seem to have failed, so resending as e-mail). Similar behaviour has been identified in Debian Stable. i2pd is broken and does not start anymore. $ sudo systemctl status i2pd ● i2pd.service - I2P Router written in C++ Loaded: loaded

Bug#1026984: Acknowledgement (pan: segfault when opening a newsgroup)

Latest crash - additional information: $ sudo coredumpctl list --no-pager | grep pan Sun 2022-12-25 16:40:26 GMT 2455385 1000 1000 SIGSEGV present /usr/bin/pan 5.0M Sun 2022-12-25 16:40:31 GMT 3338713 1000 1000 SIGSEGV present /usr/bin/pan

Bug#1026984: pan: segfault when opening a newsgroup

Package: pan Version: 0.153-1 Severity: important X-Debbugs-Cc: pior...@gmx.com Using fully updated Debian Bookworm (current testing). segfault when opening one of my subscribed newsgroups, which I've been using for months. All other groups are working ok. This is my first launch of Pan since

Bug#1021897: gnome-disk-utility: Crash when clicked X (cancel) on Deleting partition

Package: gnome-disk-utility Version: 43.0-1 Severity: normal X-Debbugs-Cc: pior...@gmx.com Crash occured when I tried to cancel Delete Partition operation which took too long. Steps: Mount SATA SSD disk via SATA cable. Disk has one Ext4 partition, otherwise it's clean and empty, zero files. MBR

Bug#1019952: gnome-disk-utility: segfault in libudisks2.so.0.0.0

Package: gnome-disk-utility Version: 43~rc-1 Severity: normal X-Debbugs-Cc: pior...@gmx.com Dear Maintainer, Managed to crash Gnome Disks today. My computer allows to plug and unplug SATA drives in and out, no problem, just like they were USB drives. I use this feature all the time when I need

Bug#1019401: QSGRenderThread[569483]: segfault after suspend/resume

On 09/09/2022 00:24, Lisandro Damián Nicanor Pérez Meyer wrote: To be honest that could be a gazillion things. This is clearly related to rendering, thus it can easily be an issue on the graphics driver... I am also figuring that it's complicated to replicate, right? Or you can easily replicate

Bug#1019401: QSGRenderThread[569483]: segfault after suspend/resume

Package: libqt5core5a Version: 5.15.4+dfsg-5 Severity: normal X-Debbugs-Cc: pior...@gmx.com Dear Maintainer, I Did suspend/resume cycle of my computer. Later I found in dmesg: [96111.865203] QSGRenderThread[569483]: segfault at 0 ip 7fe450b2bcfb sp 7fe411703950 error 4 in

Bug#1018968: clementine: Smart playlist Search term: File name - does not work

Package: clementine Version: 1.4.0~rc1+git347-gfc4cb6fc7+dfsg-2.1 Severity: normal X-Debbugs-Cc: pior...@gmx.com Dear Maintainer, Currently Search Term "File name" does not work in Smart Playlist. First of all, please rename this option to Filename, not File name. Now, to the bug itself. How to

Bug#1017352: Acknowledgement (thunderbird: Crash when sending newsgroup post)

I just tested thunderbird (1:104.0~b2-1) from experimental, via briefly changing my sources.list to include testing+sid+experimental and upgrading selection of relevant packages. thunderbird (1:104.0~b2-1) still crashes, same error.

Bug#1017352: thunderbird: Crash when sending newsgroup post

Package: thunderbird Version: 1:102.1.1-1 Severity: important X-Debbugs-Cc: pior...@gmx.com Crash is occuring every time I want to send a post to USENET newsgroup. How to reproduce: Navigate to folder with newsgroup. Open one group. Open thread and select some message. Click Followup. New window

Bug#1016406: telegram-desktop: Segfault in librlottie.so.0.1.0-1

Hello Nicholas, Thanks for prompt reply. Yes this happens as stickers gets populated and start animating, suddenly it crashes, most likely on same sticker. Anyway, your fix works. Thank you. After installing your version of the library telegram does not crash anymore. Well done! On 06/08/2022

Bug#1016406: telegram-desktop: Segfault in librlottie.so.0.1.0-1

Package: telegram-desktop Version: 4.0.2+ds-2 Severity: important X-Debbugs-Cc: pior...@gmx.com Steps to reproduce: 1. Open telegram-desktop 2. Type  character (select from emoticons menu) 3. Last used/favourite stickers will show up 4. Crash 1sec later Expected behaviour 4. No crash dmesg:

Bug#1002998: firejail-profiles: telegram-desktop not working with firejail

Yes, that worked! Thank you! On 02/01/2022 15:48, Reiner Herrmann wrote: Hi, On Sun, Jan 02, 2022 at 02:58:26PM +, piorunz wrote: Before upgrade to Testing, everything was working fine. Something is wrong with firejail profile? I request assistance. Thank you. This sounds similar

Bug#1002998: firejail-profiles: telegram-desktop not working with firejail

Package: firejail-profiles Version: 0.9.66-2 Severity: important X-Debbugs-Cc: pior...@gmx.com Dear Maintainer, I have used telegram-desktop with firejail on Debian 10. Everything was working fine. Two days ago, I updated to Debian Testing. System is clean and everything else is working. Only

Bug#1001234: (no subject)

By the way this is quick solution for people who want to painlessly upgrade unsupported Firefox ESR in Bullseye, folks on Debian User mailing list came up with this, I updated it a bit: How to download & maintain new Firefox ESR from Mozilla, point always to latest Firefox-ESR: wget -O

Bug#1001234: src:firefox-esr: fails to migrate to testing for too long: FTBFS on mipsel and unresolved RC bug

On Thu, 9 Dec 2021 19:35:47 +0100 Paul Gevers wrote: Hi Piotr, Martin-Éric, Please stop bashing Mike. He's doing a great job. Hi Paul, I am not bashing anyone. My post was simply a copy of my e-mail I sent to Debian user group yesterday:

Bug#1001234: (no subject)

Debian Stable uses Firefox ESR 78.15.0, which is final update of 78 series. All further updates go to Firefox ESR 91, as Mozilla page says: https://www.mozilla.org/en-US/firefox/78.15.0/releasenotes "Version 78.15.0, first offered to ESR channel users on October 5, 2021 This is the final planned

Bug#1001016: telegram-desktop backports request

Guriev wrote: Hello! On Пт, 2021-12-03 at 19:44 +, piorunz wrote: Testing has got 3.1.1. I hope bullseye-backports can update it? CC to maintainer, Nicholas Guriev! Thanks in advance. I have uploaded this version to Backports. It is already available on mirrors and should work okay. https

Bug#995894: Acknowledgement (linux-image-5.10.0-8-amd64: Debian Bullseye: hard freeze on AMD GPU when turned on monitor)

Caught it again today. Same Debian Bullseye with latest updates, same hardware. I logged in via ssh to find Xorg dead, killing it didn't changed anything. Killed sddm too, no change. Tried to "sudo reboot", no reaction. Had to use SysRq key combination to kill Linux. dmesg: [22780.068010]

Bug#995894: linux-image-5.10.0-8-amd64: Debian Bullseye: hard freeze on AMD GPU when turned on monitor

Package: src:linux Version: 5.10.46-5 Severity: normal X-Debbugs-Cc: pior...@gmx.com Dear Maintainer, I was away from the computer. Come back. Turned on both monitors via power button. One monitor, on DP port, each time when it's turned off, Linux things it has been permanently disconnected.

Bug#994743: (no subject)

Just checked Trisquel GNU/Linux behaviour. Installed latest Triskel (KDE variation) in VM, results: $ sudo dpkg-reconfigure keyboard-configuration [sudo] password for pioruns: Your console font configuration will be updated the next time your system boots. If you want to update it now, run

Bug#994743: Info received ((no subject))

This is my discussion about this problem on Debian mail list: https://linux.debian.user.narkive.com/naFOIjLq/colemak-layout-at-boot-time

Bug#994743: (no subject)

This bug is related to two console-setup bug reports: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696773 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696774 -- With kindest regards, Piotr. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org ⠈⠳⣄

Bug#994743: keyboard-configuration should trigger update-initramfs or warn about it

Package: keyboard-configuration Version: 1.205 Severity: important X-Debbugs-Cc: pior...@gmx.com Dear Maintainer, 1. Changed my keyboard layout to GB Colemak via "dpkg-reconfigure keyboard- configuration" 2. Rebooted 3. All changed were ignored to my surprise. After a lot of digging and

Bug#993551: (no subject)

That is a very interesting project. If it could be installed alongside Wine and Steam, and used as wine replacement, for example in Lutris, that would be great. Fingers crossed for a new maintainer to get this in Debian! -- With kindest regards, Piotr. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal

Bug#991453: Info received (Bug#991453: Acknowledgement (linux-image-5.10.0-8-amd64: Radeon 6800 XT: 100% GPU core usage & 74 Watts when idle))

I can confirm this bug can be fixed by reverting this "drm/amdgpu/gfx10: enlarge CP_MEC_DOORBELL_RANGE_UPPER to cover full doorbell." commit mentioned in bugzilla.kernel.org discussion. I downloaded Debian 5.10 kernel, fixed one line in drivers/gpu/drm/amd/amdgpu/gfx_v10_0.c file, compiled kernel

Bug#991453: Acknowledgement (linux-image-5.10.0-8-amd64: Radeon 6800 XT: 100% GPU core usage & 74 Watts when idle)

Here is kernel.org bugzilla discussion: https://bugzilla.kernel.org/show_bug.cgi?id=213561

Bug#991453: linux-image-5.10.0-8-amd64: Radeon 6800 XT: 100% GPU core usage & 74 Watts when idle

has been fixed upstream: https://gitlab.freedesktop.org/drm/amd/-/issues/1632 Can you please make sure this will be backported to Debian 5.10 kernel? Thanks. Kind regards, piorunz -- Package-specific info: ** Version: Linux version 5.10.0-8-amd64 (debian-ker...@lists.debian.org) (gcc-10 (Debian