Bug#1057045: picom frequent SIGABRT

2023-11-28 Thread Mihai Hanor
Package: picom Version: 10.2-1 Severity: normal X-Debbugs-Cc: quake2i...@gmail.com Dear Maintainer, * What led up to the situation? I'm not sure what is the context of the crash, my impression is that picom crashes after the PC is resuming from S3 sleep. * What exactly did you do (or not

Bug#1034795: amule process crashes after system resumes from S3 sleep

2023-04-24 Thread Mihai Hanor
Package: amule Version: 1:2.3.3-3 Severity: normal Dear Maintainer, * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? Resuming the PC while running amule connected to Kad network, one file in download queue. * What was the

Bug#1008224: mate-screenshot: area grab includes selection overlay

2022-03-25 Thread Mihai Hanor
After investigating the code a bit, I've opened an issue upstream: https://github.com/mate-desktop/mate-utils/issues/336

Bug#1008224: mate-screenshot: area grab includes selection overlay

2022-03-24 Thread Mihai Hanor
Package: mate-utils Version: 1.26.0-1 Severity: normal Dear Maintainer, When mate-screenshot is used with the option Select area to grab (when using Shift+Print Screen), the screenshot includes the overlay drawn when selecting the area. This is perfectly visible when using marco window with

Bug#1005900: linux.uml: uml_mconsole client becomes blocked on read after issuing commands stop and go

2022-02-17 Thread Mihai Hanor
I failed to mention that the block on read occurs by sending anything through uml_mconsole, after the go command has been processed.

Bug#1005900: linux.uml: uml_mconsole client becomes blocked on read after issuing commands stop and go

2022-02-16 Thread Mihai Hanor
Package: user-mode-linux Version: 5.16um1 Severity: normal File: /usr/bin/linux.uml X-Debbugs-Cc: quake2i...@gmail.com Dear Maintainer, * What is the problem: Issuing the commands stop followed by go, at the input of the uml_mconsole client, results in the client becoming blocked on read socket.

Bug#1005072: mate-tweak: Unpleasant transition from marco-compton to marco-picom

2022-02-16 Thread Mihai Hanor
Control: title -1 mate-tweak: Unpleasant transition from marco-compton to marco-picom

Bug#1005837: mate-tweak: marco-picom fails to start picom v9

2022-02-15 Thread Mihai Hanor
Package: mate-tweak Version: 22.04.1-1 Severity: normal X-Debbugs-Cc: quake2i...@gmail.com Dear Maintainer, * What is the problem: marco-picom fails to start picom 9-1. Checking after the user x-session has started, the picom process is missing from the list. * When manually running marco-picom

Bug#1005072: mate-tweak: Unpleasant transition from mate-compton to mate-picom

2022-02-06 Thread Mihai Hanor
Package: mate-tweak Version: 22.04.1-1 Severity: normal File: /usr/bin/mate-tweak X-Debbugs-Cc: quake2i...@gmail.com Dear Maintainer, After upgrading the packages and restarting the system (which was configured with compton as window manager in Mate Tweak), after logging in lightdm, all the

Bug#1004876: mate-panel: wnck-applet crash with SIGTRAP

2022-02-02 Thread Mihai Hanor
I've managed to find out about it and to set GDK_SYNCHRONIZE=1 for D-Bus session service org.mate.panel.applet.WnckletFactory and I will get back with a proper backtrace if it happens again.

Bug#993619: Remmina crashed in remmina-plugin-rdp.so

2021-11-18 Thread Mihai Hanor
Hello, You can close this bug. I see the fix in remmina sources version 4.21+dfsg-1 The commit on upstream is this one: https://gitlab.com/Remmina/Remmina/-/commit/25d3d44e4784b23341303ea3e952d505f508105f Kind regards, Mihai

Bug#993619: Remmina crashed in remmina-plugin-rdp.so

2021-09-03 Thread Mihai Hanor
Package: remmina-plugin-rdp Version: 1.4.20+dfsg-4 Severity: normal File: /usr/lib/x86_64-linux-gnu/remmina/plugins/remmina-plugin-rdp.so X-Debbugs-Cc: quake2i...@gmail.com Dear Maintainer, * What led up to the situation? After the existing RDP connection was lost, possibly interacted with

Bug#993210: mate-session-manager: mate-settings-daemon crashed

2021-08-28 Thread Mihai Hanor
Package: mate-session-manager Version: 1.24.1-2 Severity: normal X-Debbugs-Cc: quake2i...@gmail.com Dear Maintainer, * What led up to the situation? Before the problem occurred, I did the following: - enabled Alt+shift key for switching to another layout. - disabled New windows use active

Bug#873391: ppp-udeb.postinst and predictable network interfaces names

2017-08-27 Thread Mihai Hanor
Package: ppp Version: 2.4.7-1+4 Severity: normal Dear Maintainer, Booting a Debian Stretch or a Debian testing netinst ISO with modules=ppp-udeb parameter, the PPPoE configuration stage fails with a generic warning message, 'configuring ppp-udeb failed with code error 1', issued by the main-menu

Bug#716831: radvd crashes/segfaults with ::/64 prefix and DeprecatePrefix on

2014-11-17 Thread Mihai Hanor
This bug has been confirmed and fixed upstream: https://github.com/reubenhwk/radvd/issues/36 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#751778: dibbler-server: apt-get remove fails if dibbler-server is not running

2014-06-16 Thread Mihai Hanor
Package: dibbler-server Version: 1.0.0~rc1-1 Severity: normal Hello, When trying to remove the package (dibbler-server), apt-get / aptitude fail if dibbler-server is not running. Both versions,  the stable (0.8.2-1) and the unstable (1.0.0~rc1-1), are affected. Aptitude reports this:

Bug#716831: radvd crashes/segfaults with ::/64 prefix and DeprecatePrefix on

2014-06-15 Thread Mihai Hanor
This is how the stack looks like, when radvd_1.9.1-1.1_i386 crashes: *** Program received signal SIGSEGV, Segmentation fault. 0x80004c4d in yyparse () at gram.y:641 641 prefix-DeprecatePrefixFlag = $2; (gdb) bt #0  0x80004c4d in yyparse () at

Bug#751407: wide-dhcpv6-server: server sends reply from random UDP port

2014-06-12 Thread Mihai Hanor
Package: wide-dhcpv6-server Version: 20080615-12 Severity: normal Hello, The issue: After a client sends an information-request message, the server replies not from port 547, but from a random UDP port. I'm not sure if it's really a bug and I don't know what the standard says about this, but,