Re: How to file a Debian bug report? was: Debian 12.5: pigz 2.6-1 fails with error message (Upstream issue 111)
On 2 Apr 2024 10:27 +0200, from jch...@student.ethz.ch (Jonathan Chung): > Can someone help me to file a bug report? https://www.debian.org/Bugs/Reporting -- Michael Kjörling https://michael.kjorling.se “Remember when, on the Internet, nobody cared that you were a dog?”
Re: which package to file a bug report ?
On Tue Feb 27, 2024 at 7:12 AM GMT, Frank Weißer wrote: > So we are at my original question: Which package to file a bug report ? Package "debian-installer", I think; and/or submit an installation report, which can be done with reportbug against the "installation-report" pseudo package. See <https://d-i.debian.org/manual/en.amd64/ch05s04.html#submit-bug> -- Please do not CC me for listmail. Jonathan Dowland ✎j...@debian.org https://jmtd.net
Re: which package to file a bug report ?
Marco Moock: Am Fri, 23 Feb 2024 13:59:41 +0100 schrieb Frank Weißer : The installer does format it as ext4, but shows ext2 and places that in fstab, what ends up in emergency mode. That's why I'm here That is definitely a bug. So we are at my original question: Which package to file a bug report ? readU Frank
Re: which package to file a bug report ?
Am Fri, 23 Feb 2024 13:59:41 +0100 schrieb Frank Weißer : > First of all: I use german during installation; but I doubt that is > relevant. Try to reproduce it in English if you like. > Marco Moock: > > Am 22.02.2024 schrieb Frank Weißer : > > > >> I only choose ext2 for formatting the encrypted partition, because > >> nothing else is offered. > > > > That is really strange. If I did install Debian 12, it offered me a > > list of different file systems, including ext2/3/4. > > > It does on non-crypt partitions, but not if I choose 'physical volume > for encryption' there; then afterwards I only have the choices to use > it as ext2, swap or lvm or leave it unused for the encrypted > partition. I chose manual partitioning and I created the LUKS container manually and then created an ext4 partition inside. > >> Despite that the partition in fact is getting formatted ext4, so > >> the entry ext2 in /etc/fstab leads into emergency mode. > > > > Does the installer format it as ext4, but shows ext2 and places > > that in fstab? > > Or do you format it manually? > > > The installer does format it as ext4, but shows ext2 and places that > in fstab, what ends up in emergency mode. That's why I'm here That is definitely a bug.
Re: which package to file a bug report ?
First of all: I use german during installation; but I doubt that is relevant. Marco Moock: Am 22.02.2024 schrieb Frank Weißer : I only choose ext2 for formatting the encrypted partition, because nothing else is offered. That is really strange. If I did install Debian 12, it offered me a list of different file systems, including ext2/3/4. It does on non-crypt partitions, but not if I choose 'physical volume for encryption' there; then afterwards I only have the choices to use it as ext2, swap or lvm or leave it unused for the encrypted partition. Despite that the partition in fact is getting formatted ext4, so the entry ext2 in /etc/fstab leads into emergency mode. Does the installer format it as ext4, but shows ext2 and places that in fstab? Or do you format it manually? The installer does format it as ext4, but shows ext2 and places that in fstab, what ends up in emergency mode. That's why I'm here
Re: which package to file a bug report ?
Am 22.02.2024 schrieb Frank Weißer : > I only choose ext2 for formatting the encrypted partition, because > nothing else is offered. That is really strange. If I did install Debian 12, it offered me a list of different file systems, including ext2/3/4. > Despite that the partition in fact is getting formatted ext4, so the > entry ext2 in /etc/fstab leads into emergency mode. Does the installer format it as ext4, but shows ext2 and places that in fstab? Or do you format it manually? > I think the partitioning tool in installer should offer to format the > encrypted partition in ext4, as LUKS (?) does, instead of ext2 and > must write ext4 to /etc/fstab, as this is, how it ends up. LUKS is only a container and doesn't care about the file system inside. After opening it, it is a file under /dev/mapper that can be formatted like /dev/sdXY.
Re: which package to file a bug report ?
Marco Moock: Am 22.02.2024 um 13:18:48 Uhr schrieb Frank Weißer: I use to encrypt my swap and /var/tmp partitions during installation. That is LUKS. the partition tool in debian installer offers me randomized keys for that and has 'delete partition' set to 'yes', which costs lot of time, not necessary on new hdd/ssd and - my opinion - on randomized keys. I propose switching to 'no', when selecting randomized keys. Why? A user can rather easy select what he wants. As I said: My opinion; if you miss setting 'no' you have to wait a lot of time... Further I can select ext2 or swap for partition format. That is really strange. swap is only for the special-purpose swap partition. Yes, I choose it for the swap partition I use ext2 for /var/tmp, but - in /etc/crypttab the marker 'tmp' is missing for the /var/tmp partition Which marker? This one: frank@pc:~$ cat /etc/crypttab sda4_crypt /dev/sda4 /dev/urandom cipher=aes-xts- plain64,size=256,swap,discard sda5_crypt /dev/sda5 /dev/urandom cipher=aes-xts- plain64,size=256,tmp,discard ^^^ crypttab is only for decrypting the partition and creating a device file for the encrypted one. - in /etc/fstab ext2 is set instead of ext4, that cryptsetup defaults to. So on reboot I end up in emergency mode. If you format it in ext2, choose that. Or was that an automatic decision by the installer? I only choose ext2 for formatting the encrypted partition, because nothing else is offered. Despite that the partition in fact is getting formatted ext4, so the entry ext2 in /etc/fstab leads into emergency mode. I think the partitioning tool in installer should offer to format the encrypted partition in ext4, as LUKS (?) does, instead of ext2 and must write ext4 to /etc/fstab, as this is, how it ends up.
Re: which package to file a bug report ?
Am 22.02.2024 um 13:18:48 Uhr schrieb Frank Weißer: > I use to encrypt my swap and /var/tmp partitions during installation. That is LUKS. > the partition tool in debian installer offers me randomized keys for > that and has 'delete partition' set to 'yes', which costs lot of > time, not necessary on new hdd/ssd and - my opinion - on randomized > keys. I propose switching to 'no', when selecting randomized keys. Why? A user can rather easy select what he wants. > Further I can select ext2 or swap for partition format. That is really strange. swap is only for the special-purpose swap partition. > I use ext2 for /var/tmp, but > - in /etc/crypttab the marker 'tmp' is missing for the /var/tmp > partition Which marker? crypttab is only for decrypting the partition and creating a device file for the encrypted one. > - in /etc/fstab ext2 is set instead of ext4, that cryptsetup defaults > to. So on reboot I end up in emergency mode. If you format it in ext2, choose that. Or was that an automatic decision by the installer? -- Gruß Marco Spam und Werbung bitte an ichschickerekl...@cartoonies.org
which package to file a bug report ?
Hello! I use to encrypt my swap and /var/tmp partitions during installation. the partition tool in debian installer offers me randomized keys for that and has 'delete partition' set to 'yes', which costs lot of time, not necessary on new hdd/ssd and - my opinion - on randomized keys. I propose switching to 'no', when selecting randomized keys. Further I can select ext2 or swap for partition format. I use ext2 for /var/tmp, but - in /etc/crypttab the marker 'tmp' is missing for the /var/tmp partition - in /etc/fstab ext2 is set instead of ext4, that cryptsetup defaults to. So on reboot I end up in emergency mode. What package have I to file the bug report against? Please apologize my poor english. Kind regards readU Frank
Re: Bug report
Iman Hajibagheri wrote: > Hello > My laptop model is asus zenbook duo ux481 and I installed ubuntu desktop > After installation, when I log in to my account for the first time, a > welcome to ubuntu tab appears. I click on the help improve ubuntu section. > My laptop stops after the yes option and the operating system crashes. I > think this is due to the detection of the hardware of the second monitor. > It happens because whenever I get lshw or other hardware ls, the same thing > happens. > And it does not have the ability to adjust the brightness and other > features for the second screen. This is the Debian users mailing list. Ubuntu support is here: https://ubuntu.com/community/support
Bug report
Hello My laptop model is asus zenbook duo ux481 and I installed ubuntu desktop After installation, when I log in to my account for the first time, a welcome to ubuntu tab appears. I click on the help improve ubuntu section. My laptop stops after the yes option and the operating system crashes. I think this is due to the detection of the hardware of the second monitor. It happens because whenever I get lshw or other hardware ls, the same thing happens. And it does not have the ability to adjust the brightness and other features for the second screen.
Bug report
Hello guys, i'm running linux debian stable and i had troubles running gufw, i solved the issue by installing the package polkit-mate and then add to the startup programms the application: /usr/libexec/polkit-mate-authentication-agent-1. i am using xfce4, here is the output of dpkg --status apt: root@saetchmo:~# dpkg --status apt Package: apt Status: install ok installed Priority: required Section: admin Installed-Size: 4232 Maintainer: APT Development Team Architecture: amd64 Version: 2.6.1 Replaces: apt-transport-https (<< 1.5~alpha4~), apt-utils (<< 1.3~exp2~) Provides: apt-transport-https (= 2.6.1) Depends: adduser, gpgv | gpgv2 | gpgv1, libapt-pkg6.0 (>= 2.6.1), debian-archive-keyring, libc6 (>= 2.34), libgcc-s1 (>= 3.0), libgnutls30 (>= 3.7.5), libseccomp2 (>= 2.4.2), libstdc++6 (>= 11), libsystemd0 Recommends: ca-certificates Suggests: apt-doc, aptitude | synaptic | wajig, dpkg-dev (>= 1.17.2), gnupg | gnupg2 | gnupg1, powermgmt-base Breaks: apt-transport-https (<< 1.5~alpha4~), apt-utils (<< 1.3~exp2~), aptitude (<< 0.8.10) Conffiles: /etc/apt/apt.conf.d/01autoremove 879455db9b938ce287b23383629aedce /etc/cron.daily/apt-compat 1400ab07a4a2905b04c33e3e93d42b7b /etc/logrotate.d/apt 179f2ed4f85cbaca12fa3d69c2a4a1c3 Description: commandline package manager This package provides commandline tools for searching and managing as well as querying information about packages as a low-level access to all features of the libapt-pkg library. . These include: * apt-get for retrieval of packages and information about them from authenticated sources and for installation, upgrade and removal of packages together with their dependencies * apt-cache for querying available information about installed as well as installable packages * apt-cdrom to use removable media as a source for packages * apt-config as an interface to the configuration settings * apt-key as an interface to manage authentication keys
Re: bug report
On Sun, Sep 24, 2023 at 11:13:44AM +, Sarah Marsh wrote: > I am emailing to find information on how to file a bug report with Debian. https://www.debian.org/Bugs/Reporting > I received a message on my command line to file a report for the issue that I > am having with the command line and the Computer itself. The website says to > file through the command line but my commands do not work, We can't help you with that, if you don't tell us what commands you ran, and what their output was. In any case, if the "reportbug" command won't work for you, you can just send a properly formatted email to the appropriate address, as described on the page above. Please note that the message you sent to debian-user was NOT properly formatted for this kind of task. It was just one gigantic line of text. (I reformatted it in my reply.) The bug reporting system is going to need separate lines of text, containing the package name and the package version.
bug report
I am emailing to find information on how to file a bug report with Debian. I received a message on my command line to file a report for the issue that I am having with the command line and the Computer itself. The website says to file through the command line but my commands do not work, I am supposed to file a report giving the information that I got on the command line. If someone can help it would be greatly appreciated. Thank you. Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows
Re: bug report question
On Sep 07, 2023, duh_gently...@simplelogin.com wrote: > Thank you for your advice! No problem. > > lspci says: > 00:01.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models > 00h-0fh) PCIe GPP Bridge Okay so it's the root PCI bridge on the motherboard. Are there any BIOS/UEFI updates available? > > The only 2 PCIe devices I have are my video card and my m.2 drive. I have > had different kernel versions as I have had this problem for at least 6 > months (debian testing)... so I can't really say when it all started. What kernel are you running right now? -- |_|O|_| |_|_|O| Github: https://github.com/dpurgert |O|O|O| PGP: DDAB 23FB 19FA 7D85 1CC1 E067 6D65 70E5 4CE7 2860 signature.asc Description: PGP signature
Re: bug report question
Thank you for your advice! lspci says: 00:01.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge The only 2 PCIe devices I have are my video card and my m.2 drive. I have had different kernel versions as I have had this problem for at least 6 months (debian testing)... so I can't really say when it all started. But for me, at least a half-solution would be to stop these errors being logged, so that I can shut down the computer properly. When the root file system is full, many programs stop working, and even after a reboot, the user interface will not start. On 07/09/2023 12.24, Dan Purgert - dan at djph.net wrote: On Sep 07, 2023, duh_gently...@simplelogin.com wrote: Hello, I'd like to submit a bug, but I'm not quite sure which package it should be. I could not find anything similar in the bugtracker. The problem occurs every 10-20 times. After the system has been suspended and then resumed, the following message is written to kern.log and syslog: 2023-09-07T09:43:21.264297+02:00 host kernel: [527584.040221] pcieport :00:01.3: PME: Spurious native interrupt! [...] I accept that the message may indicate a valid problem, but having so many log messages is not OK either. Currently, when this happens, I am forced to manually delete the log file and reboot. At first glance, it seems to be hardware related. What device is plugged into that PCIe slot (or is it the PCIe Root)? In no particular order: - Check for a BIOS/UEFI update - Check with an older kernel - Check for an updated kernel module / driver - Reboot and revert to the previously working kernel revision / patch
Re: bug report question
On Sep 07, 2023, duh_gently...@simplelogin.com wrote: > Hello, > > I'd like to submit a bug, but I'm not quite sure which package it > should be. > I could not find anything similar in the bugtracker. > > The problem occurs every 10-20 times. After the system has been suspended > and then resumed, the following message is written to kern.log and syslog: > > 2023-09-07T09:43:21.264297+02:00 host kernel: [527584.040221] pcieport > :00:01.3: PME: Spurious native interrupt! > [...] > > I accept that the message may indicate a valid problem, but having so many > log messages is not OK either. Currently, when this happens, I am > forced to manually delete the log file and reboot. At first glance, it seems to be hardware related. What device is plugged into that PCIe slot (or is it the PCIe Root)? In no particular order: - Check for a BIOS/UEFI update - Check with an older kernel - Check for an updated kernel module / driver - Reboot and revert to the previously working kernel revision / patch -- |_|O|_| |_|_|O| Github: https://github.com/dpurgert |O|O|O| PGP: DDAB 23FB 19FA 7D85 1CC1 E067 6D65 70E5 4CE7 2860 signature.asc Description: PGP signature
bug report question
Hello, I'd like to submit a bug, but I'm not quite sure which package it should be. I could not find anything similar in the bugtracker. The problem occurs every 10-20 times. After the system has been suspended and then resumed, the following message is written to kern.log and syslog: 2023-09-07T09:43:21.264297+02:00 host kernel: [527584.040221] pcieport :00:01.3: PME: Spurious native interrupt! 2023-09-07T09:43:21.264297+02:00 host kernel: [527584.040225] pcieport :00:01.3: PME: Spurious native interrupt! 2023-09-07T09:43:21.264298+02:00 host kernel: [527584.040229] pcieport :00:01.3: PME: Spurious native interrupt! 2023-09-07T09:43:21.264298+02:00 host kernel: [527584.040233] pcieport :00:01.3: PME: Spurious native interrupt! 2023-09-07T09:43:21.264299+02:00 host kernel: [527584.040237] pcieport :00:01.3: PME: Spurious native interrupt! 2023-09-07T09:43:21.264299+02:00 host kernel: [527584.040241] pcieport :00:01.3: PME: Spurious native interrupt! 2023-09-07T09:43:21.264300+02:00 host kernel: [527584.040244] pcieport :00:01.3: PME: Spurious native interrupt! 2023-09-07T09:43:21.264301+02:00 host kernel: [527584.040248] pcieport :00:01.3: PME: Spurious native interrupt! 2023-09-07T09:43:21.264301+02:00 host kernel: [527584.040252] pcieport :00:01.3: PME: Spurious native interrupt! There are so many of them that within 10 minutes the log files are several GiB in size, filling the root filesystem and rendering the OS unusable. I accept that the message may indicate a valid problem, but having so many log messages is not OK either. Currently, when this happens, I am forced to manually delete the log file and reboot. Best regards, Peter
Bug Report Question
Hello Debian Team, I have a bug to report and have not done that before, thus, I need some assistance. My bug isn't with a specific package. If so, I am not sure which one. Below I will describe the issue. I use a Lenovo T560 with a Lenovo dock. It is the one that Lenovo made for this specific laptop. If I have it off of the dock and am using it, there is not an issue. However, if I have it locked or in hibernation mode, and place it on the dock while it is in one of those states, the computer locks up and I have to do a manual restart using the power button. The first time I thought it might have just been a fluke but it has happened every time. I have ran Debian 10 and Debian 11 on this laptop and it did not do that. That is why I think it might be a bug. Thank you, Chris
Re: Debian bug report etiquette
On 27/02/2023 19:58, Jonathan Dowland wrote: I see the maintainer has uploaded a new version with a fix for your issue (--execute), but they have pointed out that the original bug was complaining about something different (-c): I hadn't noticed the difference, and it seems only the former is a policy violation in their eyes. I hope the action properly addresses *your* issue. Indeed it does. I guess the issue of how to handle the arguments following -e is a bit tricky, and this *ought not to work*: x-terminal-emulator -e 'if true; then { echo "true"; bash;}; fi' although it does with some terminals. 'if true; then { echo "true"; bash;}; fi' doesn't work in an actual terminal interface though, because the whole quoted string is treated as a single command, and rejected. This works: x-terminal-emulator -e sh -c 'if true; then { echo "true"; bash;}; fi' Anyway the issue is fixed. :) -- John
Re: Debian bug report etiquette
On 28/02/2023 09:00, John Crawley wrote: On 27/02/2023 19:58, Jonathan Dowland wrote: I see the maintainer has uploaded a new version with a fix for your issue (--execute), but they have pointed out that the original bug was complaining about something different (-c): I hadn't noticed the difference, and it seems only the former is a policy violation in their eyes. I hope the action properly addresses *your* issue. I'll have to have another careful look at this. I was pretty sure that -e handling was broken, as described in Debian Policy - the part about accepting all following arguments as belonging to the invoked executable. There is no mention of the -c option in Debian Policy for x-terminal-emulator. PS I forgot to mention, Debian Policy does not refer to an --execute option either, only -e. -- John
Re: Debian bug report etiquette
On 27/02/2023 19:58, Jonathan Dowland wrote: I see the maintainer has uploaded a new version with a fix for your issue (--execute), but they have pointed out that the original bug was complaining about something different (-c): I hadn't noticed the difference, and it seems only the former is a policy violation in their eyes. I hope the action properly addresses *your* issue. I'll have to have another careful look at this. I was pretty sure that -e handling was broken, as described in Debian Policy - the part about accepting all following arguments as belonging to the invoked executable. There is no mention of the -c option in Debian Policy for x-terminal-emulator. -- John
Re: Debian bug report etiquette
On Sat, Feb 25, 2023 at 03:40:19PM +0900, John Crawley wrote: I've done this. [1] Great! I've sent a mail to cont...@bugs.debian.org to bump the severity to serious. Good. That seems to have done the trick: I see the maintainer has uploaded a new version with a fix for your issue (--execute), but they have pointed out that the original bug was complaining about something different (-c): I hadn't noticed the difference, and it seems only the former is a policy violation in their eyes. I hope the action properly addresses *your* issue. (They didn't merge your MR as part of the upload, it seems. You can probably close it if you are satisfied the issue is done.) I help to manage a small Debian derivative. [2] Our default terminal emulator used to be Terminator, and some of our users still like it. The recent issue has broken one of our utilities, if run with x-terminal-emulator set to terminator. I see, thank you for explaining! Thanks again! You're welcome, -- Please do not CC me for listmail. Jonathan Dowland ✎j...@debian.org https://jmtd.net
Re: Debian bug report etiquette
Hi Jonathan, thank you for your advice. On 24/02/2023 07:15, Jonathan Dowland wrote: [ honouring Reply-To as set ] Thanks, I'll drop that header in future. Debian Python Team maintain a huge number of packages (>2,000). Things can very easily slip through the cracks. Indeed, and everyone's extra busy now with the upcoming bookworm release. If you want to make it as easy as possible for someone with sufficient privileges to upload a fix, you could fork/clone that repository, make the necessary changes to the packaging source to include the patch (put it in debian/patches, make any other necessary changes), and raise a "Merge Request" on Salsa, pointing back at the Debian bug. Then the work required to integrate the fix is as small as possible. I've done this. [1] Have you tried emailing the python packaging maintainers? They're listed as Debian Python Team , although I'm not sure where that mail goes. You could try that and if you hear nothing, consider one of the Uploaders named on the package: they're the actual humans who have looked after it. If there's no response in a week or so I'll send an email. You could consider adjusting the bug's Severity. Is the relevant bit of Debian Policy that is violated described as a "must" or "required" directive (or similar)? In which case raising the bug severity to "serious" would be appropriate, and also cause the package to be flagged for dropping from Bookworm unless the bug is resolved Debian Policy 11.8.3 says: To be an x-terminal-emulator, a program must: Support the command-line option -e command, which creates a new terminal window and runs the specified command. may be multiple arguments, which form the argument list to the executed program. I've sent a mail to cont...@bugs.debian.org to bump the severity to serious. I'm curious therefore what is it about this particular bug that has grabbed your attention? I help to manage a small Debian derivative. [2] Our default terminal emulator used to be Terminator, and some of our users still like it. The recent issue has broken one of our utilities, if run with x-terminal-emulator set to terminator. Thanks again! [1] https://salsa.debian.org/python-team/packages/terminator/-/merge_requests/4 [2] https://wiki.debian.org/Derivatives/Census/BunsenLabs -- John
Re: Debian bug report etiquette
Hi, [ honouring Reply-To as set ] I might have missed many nuances in the situation but from what I've read, here's what I observe. On Thu, Feb 23, 2023 at 11:23:26AM +0900, John Crawley wrote: [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901245 This is the "right" bug for your issue. I also note it's quite old, and hasn't seen much attention. I was unsure whether to post a new bug report or append to the existing one, but did the latter [4]. That was the correct course of action. The issue is fixed by an upstream git commit [5] easily applied by a patch (confirmed), which would make the package fit for release. (Other maintainer options could be to drop the claim to provide x-terminal-emulator or drop the package itself.) I notice that the package source is maintained in git here <https://salsa.debian.org/python-team/packages/terminator> Debian Python Team maintain a huge number of packages (>2,000). Things can very easily slip through the cracks. If you want to make it as easy as possible for someone with sufficient privileges to upload a fix, you could fork/clone that repository, make the necessary changes to the packaging source to include the patch (put it in debian/patches, make any other necessary changes), and raise a "Merge Request" on Salsa, pointing back at the Debian bug. Then the work required to integrate the fix is as small as possible. My question: I'm in doubt whether the maintainer (Debian Python Team) will notice the issue in time for the Bookworm release - would posting a new bug report be seen as "nagging"? I'm not sure about "nagging" but it would not be helpful, because a bug describing the problem already exists. Your problem is getting anyone to take notice of it. The solution is to raise awareness (this mail to the user list, for example, is one way); another is to reduce the friction for fixing it for those who have the ability to do so (outlined above). Have you tried emailing the python packaging maintainers? They're listed as Debian Python Team , although I'm not sure where that mail goes. You could try that and if you hear nothing, consider one of the Uploaders named on the package: they're the actual humans who have looked after it. Is there a polite way to push the severity up from its current "normal"? How important is breaking Debian Policy? It can be a release blocker. You could consider adjusting the bug's Severity. Is the relevant bit of Debian Policy that is violated described as a "must" or "required" directive (or similar)? In which case raising the bug severity to "serious" would be appropriate, and also cause the package to be flagged for dropping from Bookworm unless the bug is resolved (that's one way to get attention!) <https://www.debian.org/Bugs/Developer#severities> Should I just leave it as it is? (I don't personally care all that much about Terminator itself.) I'm curious therefore what is it about this particular bug that has grabbed your attention? Also: is this the right mailing list to ask such questions? Not really. It doesn't hurt though! The question might be more on-topic on debian-devel. -- Please do not CC me for listmail. Jonathan Dowland ✎j...@debian.org https://jmtd.net
Debian bug report etiquette
Hello people, with the Bookworm soft freeze already under way, the time left for fixing packages is running low, and there's a specific case where I'd appreciate advice. The package is terminator[1], a python based extension (I think) of Gnome terminal. I don't use it myself, but the current Bookworm version breaks Debian Policy (it declares compliance with 4.6.1) in its handling of the -e option [2] when invoked as x-terminal-emulator. It declares Provides: x-terminal-emulator and sets itself as a Debian alternative for x-terminal-emulator in its maintainer scripts. There is an existing bug [3] with the title "Handling of -e violates policy for x-terminal-emulator" - the issue was fixed upstream some time ago but the bug remained open. The bug has now returned with the same result of breaking compliance with Debian Policy. I was unsure whether to post a new bug report or append to the existing one, but did the latter [4]. The issue is fixed by an upstream git commit [5] easily applied by a patch (confirmed), which would make the package fit for release. (Other maintainer options could be to drop the claim to provide x-terminal-emulator or drop the package itself.) My question: I'm in doubt whether the maintainer (Debian Python Team) will notice the issue in time for the Bookworm release - would posting a new bug report be seen as "nagging"? Should I just leave it as it is? (I don't personally care all that much about Terminator itself.) Is there some other action that would be more appropriate? Is there a polite way to push the severity up from its current "normal"? How important is breaking Debian Policy? Also: is this the right mailing list to ask such questions? Best wishes, John [1] https://packages.debian.org/bookworm/terminator [2] https://www.debian.org/doc/debian-policy/ch-customized-programs.html#packages-providing-a-terminal-emulator [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901245 [4] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901245#17 [5] https://github.com/gnome-terminator/terminator/commit/91cc928f0de1f9d6d51136cf50f06c35b5faca62
Re: Bug report help
On Mon, Nov 29, 2021 at 11:14:20PM -0500, Steven Sostrom wrote: > I am having audio problems in Debian GNU/Linux bookworm/sid running on a > Raspberry Pi 4. > Kernel: Linux 5.15.0-1-arm64 > Hi Steven, Any particular reason to be using Sid? Where did you source your download from? It sounds like a kernel/audio subsystem interaction problem but we'd need more details, I think. > I don't know that it is an issue with a package unless it is a firmware > package. > > Some of the audio devices cause applications to freeze or will play at a > slower than normal speed. The Default (pulseaudio) device usually works. > ALSA devices are more likely to fail. > > Often, after a reboot, pulseaudio will not start. I have to keep rebooting > until it works. > > Steve
Bug report help
I am having audio problems in Debian GNU/Linux bookworm/sid running on a Raspberry Pi 4. Kernel: Linux 5.15.0-1-arm64 I don't know that it is an issue with a package unless it is a firmware package. Some of the audio devices cause applications to freeze or will play at a slower than normal speed. The Default (pulseaudio) device usually works. ALSA devices are more likely to fail. Often, after a reboot, pulseaudio will not start. I have to keep rebooting until it works. Steve
Re: Debian bug report closed or open?
On Sun 12 Sep 2021 at 18:26:57 +0200, l0f...@tuta.io wrote: > Hi, > > 12 sept. 2021, 12:45 de bouncingc...@gmail.com: > > > Also, as an additional confirmation ... > > On the above bug page: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958402 > > the second link is the package name "sudo", which goes to > > https://bugs.debian.org/cgi-bin/pkgreport.cgi?package=sudo > > where under the heading > > "Resolved bugs -- Normal bugs" > > the bug number 958402 is shown with a strikethrough font > > (ie it has a horizontal line through the digits). > > > Yes, thank you David. > > 12 sept. 2021, 13:42 de a...@cityscape.co.uk: > > > A good tip. However, a point to bear in mind is that Resolved bugs are > > only visible for a few months (3?, 6?) after being closed. > > > Actually, it appears they get archived after some time. > > You can access them by appending "=yes" to the URL of the package on > the BTS. > > For example regarding sudo package: > https://bugs.debian.org/cgi-bin/pkgreport.cgi?package=sudo=yes Tha's another excellent tip! -- Brian.
Re: Debian bug report closed or open?
Hi, 12 sept. 2021, 12:45 de bouncingc...@gmail.com: > Also, as an additional confirmation ... > On the above bug page: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958402 > the second link is the package name "sudo", which goes to > https://bugs.debian.org/cgi-bin/pkgreport.cgi?package=sudo > where under the heading > "Resolved bugs -- Normal bugs" > the bug number 958402 is shown with a strikethrough font > (ie it has a horizontal line through the digits). > Yes, thank you David. 12 sept. 2021, 13:42 de a...@cityscape.co.uk: > A good tip. However, a point to bear in mind is that Resolved bugs are > only visible for a few months (3?, 6?) after being closed. > Actually, it appears they get archived after some time. You can access them by appending "=yes" to the URL of the package on the BTS. For example regarding sudo package: https://bugs.debian.org/cgi-bin/pkgreport.cgi?package=sudo=yes Best regards, l0f4r0
Re: Debian bug report closed or open?
On Sun 12 Sep 2021 at 20:45:13 +1000, David wrote: > On Sun, 12 Sept 2021 at 20:20, wrote: > > 12 sept. 2021, 10:00 de scdbac...@gmx.net: > > > l0f...@tuta.io wrote: > > > > > >> By the way, how can one see that a bug is closed and not open please? > > >> [1] : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958402 > > >> > > > I think you can recognize it by the "Done:" header on the web page: > > > > > > Done: Marc Haber <> mh+debian-packa...@zugschlus.de> > > > Also, as an additional confirmation ... > On the above bug page: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958402 > the second link is the package name "sudo", which goes to > https://bugs.debian.org/cgi-bin/pkgreport.cgi?package=sudo > where under the heading > "Resolved bugs -- Normal bugs" > the bug number 958402 is shown with a strikethrough font > (ie it has a horizontal line through the digits). A good tip. However, a point to bear in mind is that Resolved bugs are only visible for a few months (3?, 6?) after being closed. -- Brian.
Re: Debian bug report closed or open?
On Sun, 12 Sept 2021 at 20:20, wrote: > 12 sept. 2021, 10:00 de scdbac...@gmx.net: > > l0f...@tuta.io wrote: > > > >> By the way, how can one see that a bug is closed and not open please? > >> [1] : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958402 > >> > > I think you can recognize it by the "Done:" header on the web page: > > > > Done: Marc Haber <> mh+debian-packa...@zugschlus.de> > Also, as an additional confirmation ... On the above bug page: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958402 the second link is the package name "sudo", which goes to https://bugs.debian.org/cgi-bin/pkgreport.cgi?package=sudo where under the heading "Resolved bugs -- Normal bugs" the bug number 958402 is shown with a strikethrough font (ie it has a horizontal line through the digits).
Re: Debian bug report closed or open?
Hi, 12 sept. 2021, 10:00 de scdbac...@gmx.net: > l0f...@tuta.io wrote: > >> By the way, how can one see that a bug is closed and not open please? >> [1] : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958402 >> > I think you can recognize it by the "Done:" header on the web page: > > Done: Marc Haber <> mh+debian-packa...@zugschlus.de> > > Well spotted Thomas! It makes sense indeed with the email address used to close a bug. Thanks & have a great week-end! l0f4r0
Re: Debian bug report closed or open?
Hi, l0f...@tuta.io wrote: > By the way, how can one see that a bug is closed and not open please? > [1] : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958402 I think you can recognize it by the "Done:" header on the web page: Done: Marc Haber I see it in an old bug that was closed by a package release https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731023 but not in a still open bug which is awaiting closure by package release https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993646 (The release close mechanism can be seen in the debian/changelog of the affected package: * Introduced debian/xorriso.info list. (Closes: #731023) This way the maintainer does not have to remember solved bugs when the fixed release gets out.) Have a nice day :) Thomas
Debian bug report closed or open? (was: Will my reportbug report be seen?)
Hi, 11 sept. 2021, 18:52 de a...@cityscape.co.uk: > It's your submission; you can close it, In fact, any user can clos > it. > By the way, how can one see that a bug is closed and not open please? For example, I know that the bug #958402 [1] has been closed because I received an email notification for that (I'm the submitter) but it's written nowhere in the webpage itself (at least I can't find it...). [1] : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958402 l0f4r0
Re: Which package for bug report?
De Also watchdog0 sr@latn I am on a fight with Chinese corrupted google employee but nobody cares. Is mud stuffs is being stolen. They come by cell carries and cloned everything mine. Here is evidence links. The slice code I have it. It is unbelievable it shows how to hack any device on earth. I am not a professional. Just a regular window user. Fell fre to remote access my machines and see the files. links evidence pictures and videos. https://1drv.ms/a/s!AuPg3GzsWyeUgY1eeYmLFRf-iYXCjQ https://photos.app.goo.gl/BsBCuYtVtE4VwGUC9 leandro. Contact me over the phone I don't teus this my isp +552122366155 +552121796156 i want them on jail for the rest of they life's what they did to me and other person here is unacceptable Enviado via UOL Mail _ Assunto: Re: Which package for bug report? De: riveravaldezm...@gmail.com Enviado em: 27 de março de 2021 18:23 Para: debian-user@lists.debian.org Cópia: debian-user@lists.debian.org On 3/27/21, mshr wrote: > Hello, (...) > Despite turning bluetooth off, it turns itself back on after the laptop > wakes from sleep. > I'm using the plasma desktop, installed from the initial installation media. > What package should this bug relate to? Hi, I suppose you should first take a look at [0], and then maybe check packages 'bluedevil' and 'bluetooth' - maybe in that order. Hope this help you, kind regards. [0] https://wiki.debian.org/BluetoothUser
Re: Which package for bug report?
On 3/27/21, mshr wrote: > Hello, (...) > Despite turning bluetooth off, it turns itself back on after the laptop > wakes from sleep. > I'm using the plasma desktop, installed from the initial installation media. > What package should this bug relate to? Hi, I suppose you should first take a look at [0], and then maybe check packages 'bluedevil' and 'bluetooth' - maybe in that order. Hope this help you, kind regards. [0] https://wiki.debian.org/BluetoothUser
Which package for bug report?
Hello, I'd like to report a bug for Debian testing (bullseye/sid). Despite turning bluetooth off, it turns itself back on after the laptop wakes from sleep. I'm using the plasma desktop, installed from the initial installation media. What package should this bug relate to? Thank you.
Bug report concerning file /etc/resolv.conf and Connman
Hello, I'm writing to you, because I don't know precisely what package is responsible for bug- connman?, iw?,openresolv? I've just installed Buster with mini.iso. Due to age of my PC and small resources I tried to make my install as slim as possible. So I went with Openbox and decided to use connman and iwd. I've struggled a loth with getting this combo to work. I thought that the issue is with early stage of development of iwd, but it turned out that the situation is the same with wpasupplicant. What was wrong? I was able to connect to only one network- the one, which I used during installation with ethernet connection. I knew that installing gnome-network-manager would probably solve the issue- it wasn't my first attempt with connman, but as I've said- I tried to make my install minimal I figured out that I'm obtaining ip, but not dns name. After some more tries I thought of removing /etc/resolv.conf, hoping that after reboot connman will create this file with correct setup. That happened indeed and solved the issue, but it definitely shouldn't look like that. I hope that my problem wasn't caused by lack of some package- I've tried to install packages from task-lxde-desktop, to not get broken installation. I don't know if this problem affects only Buster or maybe Bullseye too, shortly before the release. Regards, Paweł Starzyński
Re: Finding related package for bug report regarding display output
On Jo, 11 mar 21, 08:19:50, Max Görner wrote: > Hello, > > since 26th of February I have problems with the DisplayPort outputs of my ^ > Lenovo ThinkPad T470p. If I use the notebooks output I can get one external > monitor to function but daisy chaining does not work. If I use the output of > the docking station, the external monitors do not work at all. > > At boot, betwenen GRUB and disk encryption, there is a error message that > reads relevant: > > [drm:drm_dp_send_link_address [drm_kms_helper]] *ERROR* Sending link > address failed with -5 > > > I wanted to file a bug but were discouraged because one should name the > related package. Those who do not know the related package shall reach out to > the mailing list. > > So here am I. Could you please help me to find out which package is affected > so I can then file a proper bug report? What changed on 26th of February? Does the issue go away if you revert to the previous version? BTW, it would help if you specified what Debian release and/or codename you are running. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser signature.asc Description: PGP signature
Re: Finding related package for bug report regarding display output
> > > > since 26th of February I have problems with the DisplayPort outputs > > of my Lenovo ThinkPad T470p. If I use the notebooks output I can get > > one external monitor to function but daisy chaining does not work. If > > I use the output of the docking station, the external monitors do not > > work at all. > It could be driver error, Xorg error or misconfiguration. I'd start with checking "$ xrandr" output. > > > > At boot, betwenen GRUB and disk encryption, there is a error message > > that reads relevant: > > > > [drm:drm_dp_send_link_address [drm_kms_helper]] *ERROR* Sending > > link address failed with -5 > > Sounds like a video driver issue. It may be related to your problem or not. If you are using Intel video, then drivers are part of the kernel. And for Nvidia there is a separate package (AFAIK)
Re: Finding related package for bug report regarding display output
On Thu, 11 Mar 2021 08:19:50 +0100 Max Görner wrote: > Hello, > > since 26th of February I have problems with the DisplayPort outputs > of my Lenovo ThinkPad T470p. If I use the notebooks output I can get > one external monitor to function but daisy chaining does not work. If > I use the output of the docking station, the external monitors do not > work at all. > > At boot, betwenen GRUB and disk encryption, there is a error message > that reads relevant: > > [drm:drm_dp_send_link_address [drm_kms_helper]] *ERROR* Sending > link address failed with -5 > > > I wanted to file a bug but were discouraged because one should name > the related package. Those who do not know the related package shall > reach out to the mailing list. > > So here am I. Could you please help me to find out which package is > affected so I can then file a proper bug report? > Generally it works if you just make your best guess, and the bug fixers will move it to the correct one. We mortals don't really know which package is the source of a bug, just which package it affects, so even if the package responsible appears to be obvious, it still often won't be the right one. The package in which you see the effects of the bug is usually a good start. It's more important that you can add details of variation of the bug e.g. 'it doesn't happen if I start the program by typing the program name in a terminal but I do see this warning:'. If you can use gdb and generate a backtrace, it's better still. -- Joe
Finding related package for bug report regarding display output
Hello, since 26th of February I have problems with the DisplayPort outputs of my Lenovo ThinkPad T470p. If I use the notebooks output I can get one external monitor to function but daisy chaining does not work. If I use the output of the docking station, the external monitors do not work at all. At boot, betwenen GRUB and disk encryption, there is a error message that reads relevant: [drm:drm_dp_send_link_address [drm_kms_helper]] *ERROR* Sending link address failed with -5 I wanted to file a bug but were discouraged because one should name the related package. Those who do not know the related package shall reach out to the mailing list. So here am I. Could you please help me to find out which package is affected so I can then file a proper bug report? Best regards Max Görner
Re: [BUG REPORT] luajit-2.1.0-beta3/jit/bcsave.lua:240: cannot convert 'nil' to 'unsigned short'
Ohh, this packages hasn't been update for so long. If no objection, I will upload the current git snapshot. Tiezhu Yang 于2021年2月24日周三 上午11:15写道: > > (1) Background > Source: luajit > Version: luajit_2.1.0~beta3+dfsg-5.3_mips64el.deb > Severity: important > Link: https://packages.debian.org/sid/luajit > > (2) Description of problem > When I build bcc, there exists the following build error: > [ 34%] Generating bcc.o > /usr/bin/luajit: /usr/share/luajit-2.1.0-beta3/jit/bcsave.lua:240: cannot > convert 'nil' to 'unsigned short' > [ 35%] Linking C executable bcc-lua > cc: error: bcc.o: No such file or directory > > (3) Steps to Reproduce > # According to https://packages.debian.org/source/sid/bpfcc, > # BCC build dependencies: > sudo apt-get install arping bison clang-format cmake dh-python \ >dpkg-dev pkg-kde-tools ethtool flex inetutils-ping iperf \ >libbpf-dev libclang-dev libclang-cpp-dev libedit-dev libelf-dev \ >libfl-dev libzip-dev linux-libc-dev llvm-dev libluajit-5.1-dev \ >luajit python3-netaddr python3-pyroute2 python3-distutils python3 > # In oreder to avoid "/bin/sh: 1: python: not found" > sudo apt-get install python > > git clone https://github.com/iovisor/bcc.git > mkdir bcc/build; cd bcc/build > cmake .. > make > > (4) Additional info > I just replace the following old file [1] with the latest new file [2], > then the error disappeared. > [1] /usr/share/luajit-2.1.0-beta3/jit/bcsave.lua > [2] https://github.com/LuaJIT/LuaJIT/blob/v2.1/src/jit/bcsave.lua > > It seems that this commit fixed it: > https://github.com/LuaJIT/LuaJIT/commit/94d0b53004a5 > > (5) Question and Suggestion > Could you please update the luajit package used with the latest source code? > > Thanks, > Tiezhu >
[BUG REPORT] luajit-2.1.0-beta3/jit/bcsave.lua:240: cannot convert 'nil' to 'unsigned short'
(1) Background Source: luajit Version: luajit_2.1.0~beta3+dfsg-5.3_mips64el.deb Severity: important Link: https://packages.debian.org/sid/luajit (2) Description of problem When I build bcc, there exists the following build error: [ 34%] Generating bcc.o /usr/bin/luajit: /usr/share/luajit-2.1.0-beta3/jit/bcsave.lua:240: cannot convert 'nil' to 'unsigned short' [ 35%] Linking C executable bcc-lua cc: error: bcc.o: No such file or directory (3) Steps to Reproduce # According to https://packages.debian.org/source/sid/bpfcc, # BCC build dependencies: sudo apt-get install arping bison clang-format cmake dh-python \ dpkg-dev pkg-kde-tools ethtool flex inetutils-ping iperf \ libbpf-dev libclang-dev libclang-cpp-dev libedit-dev libelf-dev \ libfl-dev libzip-dev linux-libc-dev llvm-dev libluajit-5.1-dev \ luajit python3-netaddr python3-pyroute2 python3-distutils python3 # In oreder to avoid "/bin/sh: 1: python: not found" sudo apt-get install python git clone https://github.com/iovisor/bcc.git mkdir bcc/build; cd bcc/build cmake .. make (4) Additional info I just replace the following old file [1] with the latest new file [2], then the error disappeared. [1] /usr/share/luajit-2.1.0-beta3/jit/bcsave.lua [2] https://github.com/LuaJIT/LuaJIT/blob/v2.1/src/jit/bcsave.lua It seems that this commit fixed it: https://github.com/LuaJIT/LuaJIT/commit/94d0b53004a5 (5) Question and Suggestion Could you please update the luajit package used with the latest source code? Thanks, Tiezhu
Re: How do I contribute patches to packages (GitLab merge requests or diff -u + bug report)?
Vishal Subramanyam wrote: > I wish to contribute patches to Debian packages, but I am confused > about how I should go about doing so. The Debian Handbook says that > using GitLab might make it easier for maintainers to merge changes, but > somebody on an IRC channel told me that the old email-based workflow is > still the dominant way of delivering patches to developers. > I find it easier to work with GitLab. What should I do? Should my > preference depend on the package maintainer's preferences? Yes, you should definitely send in patches in accordance with whichever method is currently being used by that package. Contact the package maintainer or the appropriate team list if you can't find clear documentation. If the patches aren't Debian-specific, you may wish to contribute them upstream, instead or simultaneously. -dsr-
How do I contribute patches to packages (GitLab merge requests or diff -u + bug report)?
Hey, I wish to contribute patches to Debian packages, but I am confused about how I should go about doing so. The Debian Handbook says that using GitLab might make it easier for maintainers to merge changes, but somebody on an IRC channel told me that the old email-based workflow is still the dominant way of delivering patches to developers. I find it easier to work with GitLab. What should I do? Should my preference depend on the package maintainer's preferences? Vishal
Re: Encountered a bug with a dependency of wondershaper, but I'm unsure which dependency, and how to proceed with submitting a bug report
On Wed 18 Nov 2020 at 19:34:10 +0100, Graham Bull wrote: > I am interested in getting the latest version of wondershaper into the > Debian repos. If the current maintainer is unreachable do you have any ideas > on how to proceed? You submit a bug report (severity: wishlist) using reportbug. -- Brian.
Re: Encountered a bug with a dependency of wondershaper, but I'm unsure which dependency, and how to proceed with submitting a bug report
On 11/17/20 9:34 PM, Dan Ritter wrote: Graham Bull wrote: I've been using wondershaper on Debian Stable for the past couple of years and it's been excellent. I got a new pc recently with modern hardware and thus I installed Debian Testing on it. I've noticed when I set the same rules within wondershaper on Stable and Testing, I get different behavior. Stable acts as expected, low latency and able to hit the limits set. Testing suffers a lot of latency and I'm only able to reach a fraction of the limit set. When I remove the wondershaper rules everything works as expected (I can max my internet connection on both computers). I've determined Stable and Testing use the same version of wondershaper=1.1a-10. Wondershaper has one dependency: Stable: iproute2=4.20.0-2 Testing: iproute2=5.9.0-1 iproute2 has around 8 dependencies. At this point I'm confused about how I should proceed with debugging my issue. Any advice of how to collect more info for debugging purposes or how to proceed would be very much appreciated! At this point, you might be better served by simply switching to fq_codel, unless you have a particularly odd network connection. In my /etc/network/interfaces on the firewall: up tc qdisc replace dev eth3 root fq_codel Wondershaper itself changed a lot after the 1.1 version that Debian packages; you might want to ping the nominal maintainer and see if they want to upgrade to 1.4.blah -- or, given the availability of fq_codel, just drop the package. -dsr- fq_codel seems to be a good replacement, thanks for the suggestion. However I decided to try the upstream version of wondershaper and to my surprise it worked perfectly. I then attempted to contact the Debian maintainer about upgrading the package but my email sadly bounced back. I am interested in getting the latest version of wondershaper into the Debian repos. If the current maintainer is unreachable do you have any ideas on how to proceed? Graham
Re: Encountered a bug with a dependency of wondershaper, but I'm unsure which dependency, and how to proceed with submitting a bug report
On Tue, Nov 17, 2020 at 09:15:15PM +0100, Graham Bull wrote: > I've noticed when I set the same rules within wondershaper on Stable and > Testing, I get different behavior. > Stable acts as expected, low latency and able to hit the limits set. > Testing suffers a lot of latency and I'm only able to reach a fraction of the > limit set. > > When I remove the wondershaper rules everything works as expected (I can max > my > internet connection on both computers). > > [...] > > Any advice of how to collect more info for debugging purposes or how to > proceed > would be very much appreciated! Short summary: I suggest to dump wondershaper and use CAKE instead. Please read on for details. On typical ISP access links, there are devices on both ends of the link that introduce high network latency under load (xDSL modem, DSLAM, cable modem, CMTS). This can be shown well by the DSLreports speed test: http://www.dslreports.com/speedtest Often, these devices use large network buffers and too simple buffer management, which cannot be changed by the user. Your only chance to reduce the latency is to set up a traffic shaper on a device under your control to make it a "choke point". I guess you know this since you are using wondershaper. A good solution is the combination of a shaper (e.g. HTB) with fq_codel. wondershaper does not use fq_codel yet. Personally, I use the CAKE qdisc since it is easier to set up and comes with even more improvements over HTB + fq_codel: man tc-cake https://www.bufferbloat.net/projects/codel/wiki/Cake/ My router runs the OpenWrt distribution, but CAKE should also work on Debian. Before giving further advice, I would like to know more about your network: - Does the Debian box in question manage your Internet access link, or - is there a separate router, and are there other devices using it? - What is the type (xDSL, cable, ...) and speed of your Internet link (down/up)? Regards, Mirko
Re: Encountered a bug with a dependency of wondershaper, but I'm unsure which dependency, and how to proceed with submitting a bug report
Graham Bull wrote: > I've been using wondershaper on Debian Stable for the past couple of years > and it's been excellent. > > I got a new pc recently with modern hardware and thus I installed Debian > Testing on it. > > I've noticed when I set the same rules within wondershaper on Stable and > Testing, I get different behavior. > Stable acts as expected, low latency and able to hit the limits set. > Testing suffers a lot of latency and I'm only able to reach a fraction of > the limit set. > > When I remove the wondershaper rules everything works as expected (I can > max my internet connection on both computers). > > I've determined Stable and Testing use the same version of > wondershaper=1.1a-10. > > Wondershaper has one dependency: > > Stable: iproute2=4.20.0-2 > Testing: iproute2=5.9.0-1 > > iproute2 has around 8 dependencies. > > At this point I'm confused about how I should proceed with debugging my > issue. > > Any advice of how to collect more info for debugging purposes or how to > proceed would be very much appreciated! At this point, you might be better served by simply switching to fq_codel, unless you have a particularly odd network connection. In my /etc/network/interfaces on the firewall: up tc qdisc replace dev eth3 root fq_codel Wondershaper itself changed a lot after the 1.1 version that Debian packages; you might want to ping the nominal maintainer and see if they want to upgrade to 1.4.blah -- or, given the availability of fq_codel, just drop the package. -dsr-
Encountered a bug with a dependency of wondershaper, but I'm unsure which dependency, and how to proceed with submitting a bug report
Hi all, I've been using wondershaper on Debian Stable for the past couple of years and it's been excellent. I got a new pc recently with modern hardware and thus I installed Debian Testing on it. I've noticed when I set the same rules within wondershaper on Stable and Testing, I get different behavior. Stable acts as expected, low latency and able to hit the limits set. Testing suffers a lot of latency and I'm only able to reach a fraction of the limit set. When I remove the wondershaper rules everything works as expected (I can max my internet connection on both computers). I've determined Stable and Testing use the same version of wondershaper=1.1a-10. Wondershaper has one dependency: Stable: iproute2=4.20.0-2 Testing: iproute2=5.9.0-1 iproute2 has around 8 dependencies. At this point I'm confused about how I should proceed with debugging my issue. Any advice of how to collect more info for debugging purposes or how to proceed would be very much appreciated! Regards, Graham
Re: Bug Report? - T14 Microphone Issue - Possible Missing Kernel Config?
On Ma, 27 oct 20, 20:15:13, Jonathan wrote: > Good Evening, > > I was attempting to get my microphone working on my T14 AMD as it is the > only non-functioning piece I was aware of. Browsing possible solutions I was > shown the following could fix the issue if added to the kernel config: > > CONFIG_SND_SOC_AMD_RENOIR=m > > CONFIG_SND_SOC_AMD_RENOIR_MACH=m > > > I wasn't sure how to properly post a bug report or if this was even a bug. I > apologize if this is an incorrect way to present this information. Hello, You should report this as a "bug" with severity: wishlist against the source package 'linux', asking for those options to be enabled in the Debian kernel. Typically this is done with reportbug[1], though it's possible to do it with a simple mail to sub...@bugs.debian.org if you put right at the top of the e-mail (the first two lines of your message) the following: Source: linux Severity: wishlist See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946260 for an example. [1] using reportbug with Source: linux may lead to including lots of additional information about your system which is not really necessary in this case. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser signature.asc Description: PGP signature
Bug Report? - T14 Microphone Issue - Possible Missing Kernel Config?
Good Evening, I was attempting to get my microphone working on my T14 AMD as it is the only non-functioning piece I was aware of. Browsing possible solutions I was shown the following could fix the issue if added to the kernel config: CONFIG_SND_SOC_AMD_RENOIR=m CONFIG_SND_SOC_AMD_RENOIR_MACH=m I wasn't sure how to properly post a bug report or if this was even a bug. I apologize if this is an incorrect way to present this information. Thank you Jonathan
Bug report - Samba version 4.9.5-Debian
Hi, Sorry, I am not able to use reportbug. I have installed two debian based OS in Proxmox system. I have a big issue with both of them. 1. Turnkey 16.0 Fileserver 2. OpenMediaVault 5.5.12-1 Both of them are using Samba version 4.9.5-Debian. It works well in both systems until I try to access, upload or download more files (35 000 or more) in total about 300 GB. Then the samba crashed!!! The time intervat to crash is various from 20 minutes to 2 hours from try to try. But the system is not usable as a file server for my use. I can reproduce the crash but the detail log is too huge. Is it only my problem? What should I try? I am already desperate. I never had such an issue in linux based system before. Thanks for help Best Regards Martin The example of log at crash: Oct 1 18:29:09 storage smbd[13319]: [2020/10/01 18:29:09.568347 Oct 1 18:29:09 storage smbd[13319]: === Oct 1 18:29:09 storage smbd[13319]: [2020/10/01 18:29:09.568441 Oct 1 18:29:09 storage smbd[13319]: INTERNAL ERROR: Signal 6 in pid 13319 (4.9.5-Debian) Oct 1 18:29:09 storage smbd[13319]: Please read the Trouble-Shooting section of the Samba HOWTO Oct 1 18:29:09 storage smbd[13319]: [2020/10/01 18:29:09.568468 Oct 1 18:29:09 storage smbd[13319]: === Oct 1 18:29:09 storage smbd[13319]: [2020/10/01 18:29:09.568483 Oct 1 18:29:09 storage smbd[13319]: PANIC (pid 13319): internal error Oct 1 18:29:09 storage smbd[13319]: [2020/10/01 18:29:09.599323 Oct 1 18:29:09 storage smbd[13319]: BACKTRACE: 13 stack frames: Oct 1 18:29:09 storage smbd[13319]: #0 /lib/x86_64-linux-gnu/libsamba-util.so.0(log_stack_trace+0x32) [0x7efce81058d2] Oct 1 18:29:09 storage smbd[13319]: #1 /lib/x86_64-linux-gnu/libsmbconf.so.0(smb_panic_s3+0x20) [0x7efce7d251c0] Oct 1 18:29:09 storage smbd[13319]: #2 /lib/x86_64-linux-gnu/libsamba-util.so.0(smb_panic+0x2f) [0x7efce81059df] Oct 1 18:29:09 storage smbd[13319]: #3 /lib/x86_64-linux-gnu/libsamba-util.so.0(+0x24c16) [0x7efce8105c16] Oct 1 18:29:09 storage smbd[13319]: #4 /lib/x86_64-linux-gnu/libpthread.so.0(+0x12730) [0x7efce8173730] Oct 1 18:29:09 storage smbd[13319]: #5 /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x10b) [0x7efce740e7bb] Oct 1 18:29:09 storage smbd[13319]: #6 /lib/x86_64-linux-gnu/libc.so.6(abort+0x121) [0x7efce73f9535] Oct 1 18:29:09 storage smbd[13319]: #7 /lib/x86_64-linux-gnu/libc.so.6(+0x79508) [0x7efce7450508] Oct 1 18:29:09 storage smbd[13319]: #8 /lib/x86_64-linux-gnu/libc.so.6(+0x7fc1a) [0x7efce7456c1a] Oct 1 18:29:09 storage smbd[13319]: #9 /lib/x86_64-linux-gnu/libc.so.6(+0x818a2) [0x7efce74588a2] Oct 1 18:29:09 storage smbd[13319]: #10 /lib/x86_64-linux-gnu/libc.so.6(+0x84af3) [0x7efce745baf3] Oct 1 18:29:09 storage smbd[13319]: #11 /lib/x86_64-linux-gnu/libpthread.so.0(+0x7fc9) [0x7efce8168fc9] Oct 1 18:29:09 storage smbd[13319]: #12 /lib/x86_64-linux-gnu/libc.so.6(clone+0x3f) [0x7efce74d04cf] Oct 1 18:29:09 storage smbd[13319]: [2020/10/01 18:29:09.599440 Oct 1 18:29:09 storage smbd[13319]: smb_panic(): calling panic action [/usr/share/samba/panic-action 13319] Oct 1 18:29:10 storage postfix/sendmail[13329]: fatal: chdir /var/spool/postfix: Permission denied Oct 1 18:29:31 storage smbd[13405]: [2020/10/01 18:29:31.68 Oct 1 18:29:31 storage smbd[13405]: === Oct 1 18:29:31 storage smbd[13405]: [2020/10/01 18:29:31.644533 Oct 1 18:29:31 storage smbd[13405]: INTERNAL ERROR: Signal 6 in pid 13405 (4.9.5-Debian) Oct 1 18:29:31 storage smbd[13405]: Please read the Trouble-Shooting section of the Samba HOWTO Oct 1 18:29:31 storage smbd[13405]: [2020/10/01 18:29:31.644559 Oct 1 18:29:31 storage smbd[13405]: === Oct 1 18:29:31 storage smbd[13405]: [2020/10/01 18:29:31.644584 Oct 1 18:29:31 storage smbd[13405]: PANIC (pid 13405): internal error Oct 1 18:29:31 storage smbd[13405]: [2020/10/01 18:29:31.645098 Oct 1 18:29:31 storage smbd[13405]: BACKTRACE: 13 stack frames: Oct 1 18:29:31 storage smbd[13405]: #0 /lib/x86_64-linux-gnu/libsamba-util.so.0(log_stack_trace+0x32) [0x7efce81058d2] Oct 1 18:29:31 storage smbd[13405]: #1 /lib/x86_64-linux-gnu/libsmbconf.so.0(smb_panic_s3+0x20) [0x7efce7d251c0] Oct 1 18:29:31 storage smbd[13405]: #2 /lib/x86_64-linux-gnu/libsamba-util.so.0(smb_panic+0x2f) [0x7efce81059df] Oct 1 18:29:31 storage smbd[13405]: #3 /lib/x86_64-linux-gnu/libsamba-util.so.0(+0x24c16) [0x7efce8105c16] Oct 1 18:29:31 storage smbd[13405]: #4 /lib/x86_64-linux-gnu/libpthread.so.0(+0x12730) [0x7efce8173730] Oct 1 18:29:31 storage smbd[13405]: #5 /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x10b) [0x7efce740e7bb] Oct 1 18:29:31 storage smbd[13405]: #6 /lib/x86_64-linux-gnu/libc.so.6(abort+0x121) [0x7efce73f9535] Oct 1 18:29:31 storage smbd[13405]: #7 /lib/x86_64-linux-gnu/libc.so.6(+0x79508)
Re: Bug Report
On Sb, 03 oct 20, 16:35:00, thinkingtw...@tutanota.com wrote: > Hello, > > Having gone through Debian's ReportBug system, I am unsure which > packages the issue is coming from hence the email contact. > > The problem is quite straightforward. After the last update from Linux > Kernel 4.19.0-10amd64 to 4.19.0-11amd64 on Debian Buster, there seems > to be a sound input/output issue with the Headphone Jack port. > > The sound comes out perfectly well through the speakers, however there > is a complete loss of sound output and voice input when using > headphones/earphones. > > Reverting back to Linux Kernel 4.19.0-10amd64 when in Grub fixes the > issue, therefore it seems to be related to the latest update? Indeed it suggests the issue was introduced by the kernel update, so you should file it against the kernel image package. Based on the above you should run something like reportbug linux-image-4.19.0-11-amd64 Please do check carefully that you wrote the correct package name (e.g. above you missed a hyphen). Even if it can be corrected later a lot of important information will be completely missing from your report. Especially for kernel packages reportbug should be including *lots* of information. You might want to inspect that to make sure everything is fine to be published in the open (the Debian Bug Tracking System is completely open). Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser signature.asc Description: PGP signature
Bug Report
Hello, Having gone through Debian's ReportBug system, I am unsure which packages the issue is coming from hence the email contact. The problem is quite straightforward. After the last update from Linux Kernel 4.19.0-10amd64 to 4.19.0-11amd64 on Debian Buster, there seems to be a sound input/output issue with the Headphone Jack port. The sound comes out perfectly well through the speakers, however there is a complete loss of sound output and voice input when using headphones/earphones. Reverting back to Linux Kernel 4.19.0-10amd64 when in Grub fixes the issue, therefore it seems to be related to the latest update? Best regards, Edouard H.
Re: Bug report: prog run via keyboard shortcut gets a different SSH agent?
On Tue, Sep 22, 2020 at 09:10:15AM +1000, Michael Slade wrote: > I don't know what package to assign this to so I guess I can't use the usual > bug reporting mechanism. > > I have a debian bullseye mate desktop with a custom keyboard shortcut set up > to run xterm. I noticed that an ssh agent is automatically set up for it, > but a different agent is set up for programs that are run other ways, > including via the default C-A-t shortcut for the default terminal. It sounds like MATE is starting to become more GNOME-3-like. What a shame. You'll want to talk to MATE or GNOME experts, but it sounds to me like the terminal that gets spawned by C-A-t is a child of dbus, rather than a child of the X or Wayland session. And just like in GNOME 3, when that happens, the terminal (and thus, the shell within it) does NOT inherit your normal environment. You could verify this yourself, perhaps, by printing a tree-view of your processes, and seeing who the parent of the offending terminal is. I bet it'll be dbus. With your xterm, on the other hand, I suspect that your keybaord shortcut is launching it as a child of your window manager, or some other part of your MATE session. Therefore, it inherits the same environment that your other desktop session programs have.
Bug report: prog run via keyboard shortcut gets a different SSH agent?
I don't know what package to assign this to so I guess I can't use the usual bug reporting mechanism. I have a debian bullseye mate desktop with a custom keyboard shortcut set up to run xterm. I noticed that an ssh agent is automatically set up for it, but a different agent is set up for programs that are run other ways, including via the default C-A-t shortcut for the default terminal. The same setup in buster doesn't have this issue. How should I more officially submit this report? What package should I submit under?
help with bug report for boot delay in networking
Hi, occasionally I experience a hang in booting during the network setup. The boot screen shows a timeout of 5min 7sec going to 6min 37sec after the former expired. Then the system starts normally and the networks work, including openvpn and barracudavpn (when in use). I didn't file a report with reportbug, since I believe it has to do with the interaction of packages and not a single package. As far as I remember, the behavior appeared when I installed openvpn. With it came the WiFi package and the first use of the Network-Manager-Applet. My normal network connection is cable based to a LAN and routed out via a DSL modem to the internet. It is configured manually via /etc/network/interfaces. Since my tower machine has no WiFi, I suspect that the WiFi package(s) look for one, for six and a half minutes and then gives up. Apart from this behavior I wonder, why WiFi packages would be in a dependency list of the openvpn package. I can't tell with certainty now, since I don't have detailed records, but the hang does not occur every boot, and may have some relation to hardware initialization, as it may be rarer or not happen, when I reboot into Debian from Windows 7. Sometimes the machine hangs in networking for about 2 minutes in shutdown too, again showing a timeout and counting seconds. My system runs Debian 10.5 now but the behavior is much older. If you tell me how, I can send you when I installed what. Kind Regards, Armin Faltl
Re: bug report
[it's likely you are not subscribed, sorry for the Cc: in case you are] On Sb, 20 iun 20, 07:58:33, gilleswicki wrote: > Hello, I found a bug on my system and tried to report it using the > reportbug software. But as I don't know which packet is the cause of > the bug, following the procedure of the reportbug software, I write > here to ask what I should do. Excelent! > My bug is that when I try to change the brightness of the screen > either using the keyboard shortcut for that or the cinnamon graphical > tool, the value in the file "brightness" located in > "/sys/class/backlight/acpi_video0" changes but the brightness of the > screen does not. Annoying. > I have Debian 10 with cinnamon as desktop environment. > My hardware is a laptop "Why! P775DM3" > What should I do to report this bug? This appears to be an issue with the kernel (improper support for your laptop), however... ... reporting the bug in Debian is not going to be very useful, because the kernel in Debian 10 (also known as 'buster') is quite "old" now, and because Debian uses mostly what the upstream kernel developers are providing. Even if a fix (patch) was available, it would have to be included in a newer version upstream before even considering to apply it to the kernel in buster (if ever). My suggestion would be to first try the kernel from "backports", which is reasonably recent. https://backports.debian.org/Instructions/ (you might want to install the package 'linux-image-amd64' from 'backports', this way your kernel will be automatically upgraded to the newest one available in 'backports') If this doesn't fix your issue and you are willing to experiment you could compile the latest kernel from upstream. In case that doesn't support your laptop's backlight controls either you could then report the issue there (not Debian). That would be outside the scope of this list, though you are likely to receive some useful advice here for that as well if you ask. Hope this helps, Andrei -- http://wiki.debian.org/FAQsFromDebianUser signature.asc Description: PGP signature
bug report
Hello, I found a bug on my system and tried to report it using the reportbug software. But as I don't know which packet is the cause of the bug, following the procedure of the reportbug software, I write here to ask what I should do. My bug is that when I try to change the brightness of the screen either using the keyboard shortcut for that or the cinnamon graphical tool, the value in the file "brightness" located in "/sys/class/backlight/acpi_video0" changes but the brightness of the screen does not. I have Debian 10 with cinnamon as desktop environment. My hardware is a laptop "Why! P775DM3" What should I do to report this bug? Thank you Gilles Wicki Sent with [ProtonMail](https://protonmail.com) Secure Email.
Re: bug report
On Thu, 30 Apr 2020 15:13:29 +0300 deuxb...@gmail.com wrote: > hello, > i would like to report a bug on Debian. > fresh install on my system (Chuwi minibook) - trying to shutdown causes > reboot (windows works without a problem). Thank you! Please use the reportbug' tool: https://www.debian.org/Bugs/Reporting Celejar
bug report
hello, i would like to report a bug on Debian. fresh install on my system (Chuwi minibook) - trying to shutdown causes reboot (windows works without a problem). thank you
Re: bug-report help : whole user input events freeze: doubts about the right package to submit against
In-Reply-To: <3685896c-ded1-395b-6312-cef63a9d2...@pouzenc.fr> >Ludovic Pouzenc >I have doubts about the right package to submit against (gnome-shell, >pulseaudio, wayland, udev, kernel) >Poor work-around : > >- enable accessibility feature "visual-bell". The problem vanishes, Since the workaround is changing an a11y feature, you could try one or more of the suggestions here to eliminate some of your list of possible pkgs for the bug report? https://wiki.debian.org/accessibility https://wiki.archlinux.org/index.php/GNOME/Troubleshooting
bug-report help : whole user input events freeze: doubts about the right package to submit against
Hi, I'm a french sysadmin in a school with ~250 computers (labs) running Debian 9 + Wayland. I am testing Debian 10 and I hit an annoying problem that persists (present in D9+ Wayland, and D10 default config), I can't find an already open bug for it, I have doubts about the right package to submit against (gnome-shell, pulseaudio, wayland, udev, kernel) and https://www.debian.org/Bugs/Reporting indicate to ask here. What : in a wayland gnome session, the keyboard and mouse event loop could be frozen during a little more than 1 second in all situations that fire a sound (if there isn't sound already in progress or very recently played). The mouse can't move, the keyboard can't do anything, not even VT-switch to console with Ctrl+Alt+F3. Bonus : If a key press event is processed, then the freeze occur, then a key release is queued but delayed, and the focus what in a text field, then the letter corresponding to the key is repeated many times. I didn't add fancy gnome-shell extensions. I've enabled Alternate-tab, nothing else different from fresh install defaults. Reproducer 1 : In a default Debian buster installation (testing 2019-04-21, gnome-shell 3.30.2-7, pulseaudio 12.2-4, libwayland-client0 1.16.0-1, udev 241-3, linux-image-4.19.0-4-amd64 4.19.28-2) with a first system user named testuser with a working sound configuration : - log in as testuser - start gnome-terminal - type some letters that are not a valid shell command prefix (lets says type "qwert"), see no lags for now - press tab and right after try to move mouse or typing anything else, everything is frozen for more than 1 second Reproducer 2 : In a default Debian buster installation (testing 2019-04-21, gnome-shell 3.30.2-7, pulseaudio 12.2-4, libwayland-client0 1.16.0-1, udev 241-3, linux-image-4.19.0-4-amd64 4.19.28-2) with a first system user named testuser with a working sound configuration : - log in as testuser - start firefox - browse https://www.debian.org - hit Ctrl+F to have focus in a search field, to to seek a word that in NOT in the page (but have some first letters that match some words in the page), lets say "windows" (wi matches "wiki", and I've got a nasty mood :) - you will observe the lag when firefox trigger "no match" sound after typing n, and the search box will contain around 71 or 72 "n" : "winnndows" Poor work-around : - enable accessibility feature "visual-bell". The problem vanishes, but the epileptic guys will go very disapointed. Severity : - technically : the right is usually done after a delay (~ low) - perception from users : make the system very annoying to use (important !) : my users reboot to get Windows to not have this problem :-/ On debian 9, I manage to see with strace the whole gnome-session and I've seen a open() on sound card device that blocks more than 400ms. On debian 10, I didn't manage to strace gnome-shell without entire lock-up. (suggestions are very welcome). I think that system sound triggering should not freeze all input event processing, in any case. It seems true with gnome session over Xorg, it seems false to me with gnome session over Wayland. Debian is very very great, hoping I can help a little bit to troubleshoot things here. Regards, Ludovic
Re: How to file a proper bug report
Hello, TJ Just a quick note on "AMD open driver": I assume you have been using the standard kernel in Buster, right? Have you tried this version? https://github.com/M-Bab/linux-kernel-amdgpu-binaries I have a Ryzen with embedded graphics and it works quite nicely, though I am no gamer. Regards, Andrea. Il giorno ven 15 feb 2019 alle ore 00:28 ha scritto: > I have a user question on how to file a proper Debian bug report under > certain circumstances. > > I've been testing Debian Buster off and on with Steam games. I have noted > that using the AMD open driver and Buster with Alien Isolation seems to > suffer some graphics regressions, specifically "blinking black squares." > This does not happen under Debian Stable with the kernel from > stretch-backports (needed for my AMD Radeon 580RX on a Ryzen 5 2600X). I'd > like to file a proper bug report, but I can't be confident that it Buster's > Mesa library that is the issue. I have no real experience debugging the > graphics stack, unfortunately. > > I've noted that this remains unaddressed in Ubuntu 18.04 LTS as well (if > that is actually helpful). > > What is the best/most productive way to proceed? > > Thank you! > T.J. >
Re: How to file a proper bug report
Thank you, David and Felix. Your comments have been very helpful. I'll look into those as soon as I get some free time! T.J.
Re: How to file a proper bug report
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Fri, 15 Feb 2019 11:20:54 +1100 Ben Finney wrote: > t.j.duch...@gmail.com writes: > > > I have a user question on how to file a proper Debian bug report under > > certain circumstances. > > Thank you for taking the care to find out what information is needed for > a good bug report. > > Your specific use cases seem to involve non-free software (Steam games > are, I assume, non-free in general, though there may be some exceptions) > so that makes it particularly difficult to diagnose problems. > > If there are reproducible behaviours, it can be helpful to run the > program under ‘strace’ and reproduce the behaviour, to get an extremely > verbose log of system calls being made at the time when the behaviour > occurs. > > When that is reproducible, it might be helpful to have two separate > ‘strace’ log outputs: one from the environment where you don't get the > buggy behaviour, one where you do. > I watch the mesa-dev ML. What you want to do is to log and post from both systems the following: 1. Xorg log (Typically called Xorg.0.log) from /var/log. 2. Run the program dmesg from the cmdline and log it to a file. HINT: Redirect to a file with > FILE. As in: PROG > FILE.txt 3. Install apitrace (cmdline command: apt install apitrace ) 4. Run the program wile apitrace'ing it. (Normally you run the command in the terminal wine example.exe) COMPRESS the output it will be HUGE!!! HINT: apitrace wine example.exe | xz -9ecvCsha256 > FILE.txt. 5. Uname -a (This, in particular, will give you the kernel version.) 6. Programs and versions (wine, mesa, llvm, xorg, example.exe, libdrm). Typically you run from the cmdline: PROG --version; apt show PROG. The proprietary game will not accept this method of course. 7. Fill out a bug with this info at: https://bugs.freedesktop.org/. Use attachments liberally with the add attachment feature. You can comment and attach several times for 1 bug so not everything has to be in the first post. Describe your problem throughly. Don't post screen shots unless you have to. See these for examples: https://bugs.freedesktop.org/show_bug.cgi?id=91251 https://bugs.freedesktop.org/show_bug.cgi?id=73739 Be aware that they might ask you to try a custom kernel/mesa/etc.. If you cannot do this they might need a copy of the game in question. They are friendly and will walk you through the above if you ask them to. No, I have not run the above to check for errors but it looks correct and I did check the man pages. Thanks for your report, David -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEL2N7+xWmVOJDQxWGm3XCrhg2YP8FAlxmQeEACgkQm3XCrhg2 YP/Hlg//fjfjBZtQzs+JN5k14mGg1/TagkS6Q+ZB7fEgJC088/Vm0hcSnMlEZUsS hffDU/UUG2sVbrqfHBLpmnGNZ5zTwQBUzJBujYUvoH4XFj0TWLA3zQW7MFPjO/kO oZFNiBv0nHpJByT5ehVdRJT86fP4HYtPAm9WDBP7f05bAZdu48aMW3vD2QiZeg0Q jA6Atv9He3AN7BXDJ+AGh8EpaKXDMOoAuk9bj+OXf81cthArXZaQ3rdqksVfqx0P 7Eoofg2dAS1sTNiq42h1PDpLG9GIpp+asYT2XIkwT9wJLnh8dvE6nKy8vVx4UNo5 GcqfMFPGxU3NGVoUqcXMCGPbvTZL/q6HQz1+A0gAfrh+/ikZPFviBTqjwdKnn8uu 5DZ7K9P8qtD2iB1U8rcjX6JFLmkSVnV9AhViT9xlHYoXxyv2HWDpBtiCJm8NVtQ2 W9quZJqlV/3vA7ncEH46LQCpS3Q+ZKqe83nwZxJ8ez7fFaH0Li9gWsveGmS99INn EILNtq2X5leoS5vGuPZMCgo33VoLdeKwHR5iiTOoktjGP4pXuCvGi6mthLYWwrRP Q68cCiZ7CouPWBlXdY6Emr9+zTGayrysUgXhubFiWjB8Zf8l8EqKk6RrmrIimsOP gnEPCNHPI11NDdOQ2Z4UlF53YUtkgXildR/0DKv1HxsYAyXnKmA= =aVk3 -END PGP SIGNATURE-
Re: How to file a proper bug report
t.j.duch...@gmail.com composed on 2019-02-14 17:27 (UTC-0600): > I have a user question on how to file a proper Debian bug report under > certain circumstances. > I've been testing Debian Buster off and on with Steam games. I have > noted that using the AMD open driver and Buster with Alien Isolation > seems to suffer some graphics regressions, specifically "blinking black > squares." This does not happen under Debian Stable with the kernel > from stretch-backports (needed for my AMD Radeon 580RX on a Ryzen 5 > 2600X). I'd like to file a proper bug report, but I can't be confident > that it Buster's Mesa library that is the issue. I have no real > experience debugging the graphics stack, unfortunately. > I've noted that this remains unaddressed in Ubuntu 18.04 LTS as well > (if that is actually helpful). > What is the best/most productive way to proceed? This is intended for all Intel hardware on Linux users, but it should be a useful template for anyone with Xorg driver trouble interested in reporting it wherever the right tracker happens to be: https://01.org/linuxgraphics/documentation/how-report-bugs -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
Re: How to file a proper bug report
t.j.duch...@gmail.com writes: > I spend most of my time working on Windows, so debugging Linux will be > something new. Thanks for helping me on that! If you don't mind, > I'll post back on what I find so I can do this the right way. You're welcome here to ask about using Debian, especially since you already have a motivation to help the Debian Project make it better :-) -- \ “Speech is human, silence is divine, yet also brutish and dead: | `\ therefore we must learn both arts.” —Thomas Carlyle, 1830 | _o__) | Ben Finney
Re: How to file a proper bug report
On Fri, 2019-02-15 at 11:20 +1100, Ben Finney wrote: > t.j.duch...@gmail.com writes: > > > I have a user question on how to file a proper Debian bug report > > under > > certain circumstances. > > Thank you for taking the care to find out what information is needed > for > a good bug report. > > Your specific use cases seem to involve non-free software (Steam > games > are, I assume, non-free in general, though there may be some > exceptions) > so that makes it particularly difficult to diagnose problems. > > If there are reproducible behaviours, it can be helpful to run the > program under ‘strace’ and reproduce the behaviour, to get an > extremely > verbose log of system calls being made at the time when the behaviour > occurs. > > When that is reproducible, it might be helpful to have two separate > ‘strace’ log outputs: one from the environment where you don't get > the > buggy behaviour, one where you do. > Thank you for the suggestion, Ben. I really do appreciate it, and will try that as soon as I have some free time. I have seen videos of a similar effect in other Steam games ported to Linux, so I am actually concerned that this may be a regression in Mesa (which is free software) as Debian Stable's older version does not have the issue. I spend most of my time working on Windows, so debugging Linux will be something new. Thanks for helping me on that! If you don't mind, I'll post back on what I find so I can do this the right way. Thanks again. T.J.
Re: How to file a proper bug report
t.j.duch...@gmail.com writes: > I have a user question on how to file a proper Debian bug report under > certain circumstances. Thank you for taking the care to find out what information is needed for a good bug report. Your specific use cases seem to involve non-free software (Steam games are, I assume, non-free in general, though there may be some exceptions) so that makes it particularly difficult to diagnose problems. If there are reproducible behaviours, it can be helpful to run the program under ‘strace’ and reproduce the behaviour, to get an extremely verbose log of system calls being made at the time when the behaviour occurs. When that is reproducible, it might be helpful to have two separate ‘strace’ log outputs: one from the environment where you don't get the buggy behaviour, one where you do. -- \ “If we don't believe in freedom of expression for people we | `\ despise, we don't believe in it at all.” —Noam Chomsky, | _o__) 1992-11-25 | Ben Finney
How to file a proper bug report
I have a user question on how to file a proper Debian bug report under certain circumstances. I've been testing Debian Buster off and on with Steam games. I have noted that using the AMD open driver and Buster with Alien Isolation seems to suffer some graphics regressions, specifically "blinking black squares." This does not happen under Debian Stable with the kernel from stretch-backports (needed for my AMD Radeon 580RX on a Ryzen 5 2600X). I'd like to file a proper bug report, but I can't be confident that it Buster's Mesa library that is the issue. I have no real experience debugging the graphics stack, unfortunately. I've noted that this remains unaddressed in Ubuntu 18.04 LTS as well (if that is actually helpful). What is the best/most productive way to proceed? Thank you! T.J.
Help filing a bug report
Good Evening, I have a rather specific bugthat I can reliably recreate, but I really don't know how to file it or how to give detailed logs on, and I would appreciate any advice. I am running Debian Stable with a Cimmamon Desktop, and have it set to sign me in automaically. I am running it on top of an encrypted ZFS set up. Recently, I purchased a 2TB hard drive and formatted it to ext4. I added this to my /etc/fstab: UUID=31320a26-0b89-413f-a628-b8e10041183f /home/chris/Android ext4 defaults 0 0 On the next reboot, Cinnamon did not automatically log me in, but presented the log in screen to me. WHen I logged in, the command line reappeared, then the log in screen reappeared. I could log in as root, and if I used ctrl+alt+F1 to log in as "chris" on CLI, I would log in no problem. I discovered this because I reverted the ZFS snapshot to before having the hard drive, and I could log in just fine. HOwever, adding that line again triggered the same error state. WHen I tried to remove the line from /etc/fstab and reboot, the error state persisted. I have additionally found that mounting the ext4 partition through Nemo does not trigger this behavior. As this is a rather odd bug, I am unsure how to gather more information, nor am I sure what is causing it, as I have a feeling that it is a compilation of issues. Any help would be appreciated. Thank you! Respectfully, Chris Talbot
Re: appropriate package for bug report about qualcomm atheros attansic l1
On Wed, 30 May 2018, Υπάτιος Μ. Μωυσιάδης wrote: > i want to send through email a bug report, for a bug that i think my pc has. > My problem/bug, is that i have a network card qualcomm atheros attansic l1 > gigabit ethernet (revb0) [1969:1048], that can't connect to the internet, > through ethernet which is the only option. From some commands that i found > in the internet i show in my pc a message [1.456178] atl1 probe of > :02:00.0 failed with error -5. This bug has already been reported: https://bugs.debian.org/779329 Your best bet is to try to reproduce it with a more modern kernel (or perhaps see if a backported kernel still shows the issue), and mail that bug report with details on how to reproduce it. -- Don Armstrong https://www.donarmstrong.com He was wrong. Nature abhors dimensional abnormalities, and seals them neatly away so that they don't upset people. Nature, in fact, abhors a lot of things, including vacuums, ships called the Marie Celeste, and the chuck keys for electric drills. -- Terry Pratchet _Pyramids_ p166
appropriate package for bug report about qualcomm atheros attansic l1
Hello, i want to send through email a bug report, for a bug that i think my pc has. My problem/bug, is that i have a network card qualcomm atheros attansic l1 gigabit ethernet (revb0) [1969:1048], that can't connect to the internet, through ethernet which is the only option. From some commands that i found in the internet i show in my pc a message [1.456178] atl1 probe of :02:00.0 failed with error -5. Which package should i use in my report? In the "How to report a bug in Debian using emai" that i found here https://www.debian.org/Bugs/Reporting#filedalready , says that these is the first step, but i have no idea what the package is. Also i can't use reportbug program, because my debian 9.4 machine doesn't have internet access and i'm writing from a windows machine. Thanks
Re: html page for bug report
Just to let you know I finally opt for a simple html page created with org-mode. I use the checkboxes (org-mode can export checkboxes in proper html) to allow visitors to check (ie mark a bug/feature as fixed/implemented.
Re: Bug Report
On Tue, 16 Jan 2018, songbird wrote: David Wright wrote: ... Un-trimming some evidence: On Mon 15 Jan 2018 at 23:27:30 (-0500), James Vibber wrote: [...] Unpacking libc6:armhf (2.26-2) over (2.19-18+deb8u10) ... Would it be better to upgrade jessie???stretch before stretch???buster? if that is what OP is doing, Judging by the libc6 versions, that is exactly what it looks like. then yes, skipping major versions has never been officially supported. at that stage it is often much more time efficient to re install from recent images. songbird
Re: Bug Report
David Wright wrote: ... > Would it be better to upgrade jessie→stretch before stretch→buster? if that is what OP is doing, then yes, skipping major versions has never been officially supported. at that stage it is often much more time efficient to re install from recent images. songbird
Re: Fwd: Bug Report
> > WARNING: The following essential packages will be removed. > > This should NOT be done unless you know exactly what you are doing! > > apt libapt-pkg4.12 (due to apt) libc6 (due to apt) libgcc1 (due to apt) > > libstdc++6 (due to apt) gnupg (due to apt) [...] On Tue, Jan 16, 2018 at 01:31:39PM +, Darac Marjal wrote: > Thirdly, (and I GUESS that this is why you're trying to report a bug), do > YOU see a differenve between: > > Yes, do as I say! > > and > > yes,do as I say! > > ? It's good that he failed to type it correctly. His system would NOT have survived had he confirmed this removal.
Re: Fwd: Bug Report
On Mon, Jan 15, 2018 at 11:31:02PM -0500, James Vibber wrote: -- Forwarded message -- From: "James Vibber" <[1]jvibbe...@gmail.com> Date: Jan 15, 2018 10:54 PM Subject: Bug Report To: <[2]deb...@gmail.com> Cc: WARNING: The following essential packages will be removed. This should NOT be done unless you know exactly what you are doing! apt libapt-pkg4.12 (due to apt) libc6 (due to apt) libgcc1 (due to apt) libstdc++6 (due to apt) gnupg (due to apt) base-passwd libdebconfclient0 (due to base-passwd) bash debianutils (due to bash) dash (due to bash) libncurses5 (due to bash) libtinfo5 (due to bash) bsdutils libsystemd0 (due to bsdutils) coreutils libacl1 (due to coreutils) libattr1 (due to coreutils) libselinux1 (due to coreutils) dpkg (due to dash) diffutils libbz2-1.0 (due to dpkg) liblzma5 (due to dpkg) zlib1g (due to dpkg) tar (due to dpkg) e2fsprogs e2fslibs (due to e2fsprogs) libblkid1 (due to e2fsprogs) libcomerr2 (due to e2fsprogs) libss2 (due to e2fsprogs) libuuid1 (due to e2fsprogs) util-linux (due to e2fsprogs) findutils grep libpcre3 (due to grep) gzip hostname init systemd-sysv (due to init) init-system-helpers perl-base (due to init-system-helpers) libc-bin login libaudit1 (due to login) libpam0g (due to login) libpam-runtime (due to login) libpam-modules (due to login) mount libmount1 (due to mount) libsmartcols1 (due to mount) ncurses-bin sed sysvinit-utils startpar (due to sysvinit-utils) initscripts (due to util-linux) tzdata (due to util-linux) libslang2 (due to util-linux) 43 upgraded, 33 newly installed, 1458 to remove and 172 not upgraded. 4 not fully installed or removed. Need to get 29.6 MB/41.1 MB of archives. After this operation, 2407 MB disk space will be freed. You are about to do something potentially harmful. To continue type in the phrase 'Yes, do as I say!' ?] yes,do as I say! Abort. root@loc Firstly, it's normal to accompany a bug report with some narrative. An isolated error message is not always useful to a developer. Adding "I was trying to install firefox and apt wanted to delete every other package' gives the developer some context. The above is akin to taking your car into a garage and pointed at the "Check Engine" light Secondly, I presume you're sending the message to debian-user@l.d.o because you don't know which package to report the bug against. In my opinion, that depends on what, exactly, you're complaining about. Are you complaining that making some change to packages caused apt to try to remove essential packages (but if it was that, you'd have told us what changes you were trying to make, any why you were willing to remove them)? Thirdly, (and I GUESS that this is why you're trying to report a bug), do YOU see a differenve between: Yes, do as I say! and yes,do as I say! ? References Visible links 1. mailto:jvibbe...@gmail.com 2. mailto:deb...@gmail.com -- For more information, please reread. signature.asc Description: PGP signature
Re: Bug Report
On Mon 15 Jan 2018 at 23:27:30 (-0500), James Vibber wrote: > http://ftp.debian.org/debian/ buster/main zsh-common all 5.4.2-3 [3529 kB] > Fetched 11.7 MB in 13s (846 kB/s) > Extracting templates from packages: 100% > Preconfiguring packages ... > cat: /sys/bus/usb/devices/*:*/bInterfaceClass: No such file or directory > cat: /sys/bus/usb/devices/*:*/bInterfaceSubClass: No such file or directory > cat: /sys/bus/usb/devices/*:*/bInterfaceProtocol: No such file or directory > (Reading database ... 146452 files and directories currently installed.) > Preparing to unpack .../libc6_2.26-2_armhf.deb ... > Checking for services that may need to be restarted... > Checking init scripts... > Failed to read /proc/cmdline. Ignoring: Permission denied > Unpacking libc6:armhf (2.26-2) over (2.19-18+deb8u10) ... Would it be better to upgrade jessie→stretch before stretch→buster? > dpkg: warning: subprocess old post-removal script was killed by signal > (Segmentation fault) > dpkg: trying script from the new package instead ... > dpkg: error processing archive /var/cache/apt/archives/libc6_2.26-2_armhf.deb > (--unpack): > subprocess new post-removal script was killed by signal (Segmentation fault) > dpkg: error while cleaning up: > subprocess installed pre-installation script was killed by signal > (Segmentation fault) > Processing triggers for libc-bin (2.19-18+deb8u10) ... > Error connecting: Could not connect: Connection refused > E: Sub-process /usr/bin/dpkg return Cheers, David.
Fwd: Bug Report
-- Forwarded message -- From: "James Vibber" <jvibbe...@gmail.com> Date: Jan 15, 2018 10:54 PM Subject: Bug Report To: <deb...@gmail.com> Cc: WARNING: The following essential packages will be removed. This should NOT be done unless you know exactly what you are doing! apt libapt-pkg4.12 (due to apt) libc6 (due to apt) libgcc1 (due to apt) libstdc++6 (due to apt) gnupg (due to apt) base-passwd libdebconfclient0 (due to base-passwd) bash debianutils (due to bash) dash (due to bash) libncurses5 (due to bash) libtinfo5 (due to bash) bsdutils libsystemd0 (due to bsdutils) coreutils libacl1 (due to coreutils) libattr1 (due to coreutils) libselinux1 (due to coreutils) dpkg (due to dash) diffutils libbz2-1.0 (due to dpkg) liblzma5 (due to dpkg) zlib1g (due to dpkg) tar (due to dpkg) e2fsprogs e2fslibs (due to e2fsprogs) libblkid1 (due to e2fsprogs) libcomerr2 (due to e2fsprogs) libss2 (due to e2fsprogs) libuuid1 (due to e2fsprogs) util-linux (due to e2fsprogs) findutils grep libpcre3 (due to grep) gzip hostname init systemd-sysv (due to init) init-system-helpers perl-base (due to init-system-helpers) libc-bin login libaudit1 (due to login) libpam0g (due to login) libpam-runtime (due to login) libpam-modules (due to login) mount libmount1 (due to mount) libsmartcols1 (due to mount) ncurses-bin sed sysvinit-utils startpar (due to sysvinit-utils) initscripts (due to util-linux) tzdata (due to util-linux) libslang2 (due to util-linux) 43 upgraded, 33 newly installed, 1458 to remove and 172 not upgraded. 4 not fully installed or removed. Need to get 29.6 MB/41.1 MB of archives. After this operation, 2407 MB disk space will be freed. You are about to do something potentially harmful. To continue type in the phrase 'Yes, do as I say!' ?] yes,do as I say! Abort. root@loc
Fwd: Bug Report
-- Forwarded message -- From: "James Vibber" <jvibbe...@gmail.com> Date: Jan 15, 2018 10:52 PM Subject: Bug Report To: <deb...@gmail.com> Cc: kage binutils-arm-linux-gnueabihf is not configured yet. dpkg: error processing package binutils (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: libc6:armhf libbinutils:armhf binutils-arm-linux-gnueabihf binutils Error connecting: Could not connect: Connection refused E: Sub-process /usr/bin/dpkg returned an error code (1) root@localhost:/#
Bug Report
http://ftp.debian.org/debian/ buster/main zsh-common all 5.4.2-3 [3529 kB] Fetched 11.7 MB in 13s (846 kB/s) Extracting templates from packages: 100% Preconfiguring packages ... cat: /sys/bus/usb/devices/*:*/bInterfaceClass: No such file or directory cat: /sys/bus/usb/devices/*:*/bInterfaceSubClass: No such file or directory cat: /sys/bus/usb/devices/*:*/bInterfaceProtocol: No such file or directory (Reading database ... 146452 files and directories currently installed.) Preparing to unpack .../libc6_2.26-2_armhf.deb ... Checking for services that may need to be restarted... Checking init scripts... Failed to read /proc/cmdline. Ignoring: Permission denied Unpacking libc6:armhf (2.26-2) over (2.19-18+deb8u10) ... dpkg: warning: subprocess old post-removal script was killed by signal (Segmentation fault) dpkg: trying script from the new package instead ... dpkg: error processing archive /var/cache/apt/archives/libc6_2.26-2_armhf.deb (--unpack): subprocess new post-removal script was killed by signal (Segmentation fault) dpkg: error while cleaning up: subprocess installed pre-installation script was killed by signal (Segmentation fault) Processing triggers for libc-bin (2.19-18+deb8u10) ... Error connecting: Could not connect: Connection refused E: Sub-process /usr/bin/dpkg return
Re: html page for bug report
On Fri, Jan 12, 2018 at 05:04:25PM +0100, Pétùr wrote: > On 12/01/18 05:57, Dan Ritter wrote: > >Every bug or ticket tracker expands to fit at least a minimal > >set of features: bug numbering, more states between "new" and > >"fixed", assignment to individuals... > > > >I like Request Tracker (RT) an awful lot. It's in Debian. It is > >not simple to set up, but it can be quite simple to use. > Thanks, it seems too powerful for my present needs (I don't want users > management, mysql database, etc.) but I will have a look. > > I will maybe create a html page with a form myself. But I don't see > how the visitor can modify an bug report (to mark as fixed). That's where the "complexity" of a database comes in. You need *somewhere* to store the submitted bugs so that they can be recorded, retrieved, and updated. Cheers, Tom -- Connection reset by some moron with a backhoe signature.asc Description: Digital signature
Re: html page for bug report
On 12/01/18 05:57, Dan Ritter wrote: On Fri, Jan 12, 2018 at 11:33:17AM +0100, Pétùr wrote: I am looking for a very simple way to create a bug report webpage. I would like to obtain a single html page where a visitor can create a bug report or feature request. Another visitor can mark the bug as fixed. No authentication. User have zero knowledge in html. Are you aware of such program or script? Every bug or ticket tracker expands to fit at least a minimal set of features: bug numbering, more states between "new" and "fixed", assignment to individuals... I like Request Tracker (RT) an awful lot. It's in Debian. It is not simple to set up, but it can be quite simple to use. Thanks, it seems too powerful for my present needs (I don't want users management, mysql database, etc.) but I will have a look. I will maybe create a html page with a form myself. But I don't see how the visitor can modify an bug report (to mark as fixed). Pétùr
Re: html page for bug report
On Fri, Jan 12, 2018 at 11:33:17AM +0100, Pétùr wrote: > I am looking for a very simple way to create a bug report webpage. I > would like to obtain a single html page where a visitor can create a bug > report or feature request. Another visitor can mark the bug as fixed. No > authentication. User have zero knowledge in html. > > Are you aware of such program or script? Every bug or ticket tracker expands to fit at least a minimal set of features: bug numbering, more states between "new" and "fixed", assignment to individuals... I like Request Tracker (RT) an awful lot. It's in Debian. It is not simple to set up, but it can be quite simple to use. -dsr-
html page for bug report
I am looking for a very simple way to create a bug report webpage. I would like to obtain a single html page where a visitor can create a bug report or feature request. Another visitor can mark the bug as fixed. No authentication. User have zero knowledge in html. Are you aware of such program or script? Pétùr
Re: bug report - I don't know what package the bug is in
On Thu, 05 Oct 2017, Sergey Storm wrote: > Hello. I have a problem with keyboard input and I don't know what > package the bug is in. Bugreport gave me this email address for > assistance. Help me please. > I use two languages and switch them using ctrl+shift. But combinations > ctrl+shift+'any letter' do not correctly work either in the browser, > or in the konsole. All combinations ctrl+shift+'any letter' run as > ctrl+'any letter' and language switch. Thank you. You almost certainly want something like grp:shifts_toggle (both shifts toggle) or similar, not grp:ctrl_shift (control/shift toggles). Otherwise you won't be able to type ctrl-shift-key combinations, because they will shift the layout. man 7 xkeyboard-config; for details about all of the possible grp: settings for toggling between layouts. -- Don Armstrong https://www.donarmstrong.com Some pirates achieved immortality by great deeds of cruelty or daring-do. Some achieved immortality by amassing great wealth. But the captain had long ago decided that he would, on the whole, prefer to achieve immortality by not dying. -- Terry Pratchet _The Color of Magic_
bug report - I don't know what package the bug is in
Hello. I have a problem with keyboard input and I don't know what package the bug is in. Bugreport gave me this email address for assistance. Help me please. I use two languages and switch them using ctrl+shift. But combinations ctrl+shift+'any letter' do not correctly work either in the browser, or in the konsole. All combinations ctrl+shift+'any letter' run as ctrl+'any letter' and language switch. Thank you.
Re: unable to determine which package my bug report should be filed against - please advise.
On Thu, 07 Sep 2017, DM wrote: > I am not sure exactly what may be the cause of the issue, and I am > reaching out to you for help to identify what part of Debain might be > causing this issue. This sounds like your monitor might not be returning the correct EDID or Debian isn't handling it appropriately. > The issue: I am using a second monitor (external monitor connected via > a displayport - LG 29UM57-P). External monitor connected to my laptop > - Lenovo T420. External monitor does not display video at the desired > resolution and the aspect ratio. > > Displayed resolution - 1920 x 1080 > Displayed aspect ratio - 16:9 > > Expected resolution - 2560 x 1080 > Expected ratio - 21:9 > > This same exact issue exist on my other machine Lenovo X230 with > external monitor of exact same model. These machines all use the intel graphics driver, so you should file this bug against the xserver-xorg-video-intel package. [You can verify that by checking /var/log/Xorg.0.log and seeing if you see lots of "intel(0)" lines there.] > Previous version of Debian 8 (jessie) worked with out any issue with > the monitor at the correct and expected resolution and the aspect > ratio. > > After installing a fresh version of Debian 9 (Stretch), I am unable to > use the external monitor at its maximum resolution. Debian 9 (Stretch) > was a full installation from scratch (not an upgrade). When you file the bug, please also include the output of xrandr --verbose; -- Don Armstrong https://www.donarmstrong.com They say when you embark on a journey of revenge dig two graves. They underestimate me. -- a softer world #560 http://www.asofterworld.com/index.php?id=560
Re: unable to determine which package my bug report should be filed against - please advise.
On Thu, 07 Sep 2017 16:51:25 -0400 DM <skyguide.b...@protonmail.com> wrote: > Hello Debian support team. I am a happy Dabian 9 user. I would like > to report an issue I am experiencing. In the past I used a package > 'reportbug' to report bugs, but by design, I have to identify what > package the issue is related to. > > I am not sure exactly what may be the cause of the issue, and I am > reaching out to you for help to identify what part of Debain might be > causing this issue. > > The issue: I am using a second monitor (external monitor connected > via a displayport - LG 29UM57-P). External monitor connected to my > laptop - Lenovo T420. External monitor does not display video at the > desired resolution and the aspect ratio. > > Displayed resolution - 1920 x 1080 > Displayed aspect ratio - 16:9 > > Expected resolution - 2560 x 1080 > Expected ratio - 21:9 > > This same exact issue exist on my other machine Lenovo X230 with > external monitor of exact same model. > > Previous version of Debian 8 (jessie) worked with out any issue with > the monitor at the correct and expected resolution and the aspect > ratio. > > After installing a fresh version of Debian 9 (Stretch), I am unable > to use the external monitor at its maximum resolution. Debian 9 > (Stretch) was a full installation from scratch (not an upgrade). > > All cables has been tested, and hardware issues has been ruled out. > > I am not sure if I should be filing a bug report identifying Gnome3, > or X11 as a cause of the issue or some other part of the OS. > > Could you please advise. > It saves a bit of time if you can identify the correct package, and it's often obvious, but it's not crucial to do so. Make your best guess and report the bug. If you're wrong, the Developer God will roll his eyes, mutter 'idiot', and reassign it to the correct package, though sometimes bugs get worked on significantly before the correct package can be identified. The important thing is to get it logged into the system. 'Gnome' is the wrong guess, as it's just a gigantic collection of somewhat-related packages, I'd go for xserver-xorg, itself a collection of packages, but a much smaller one, and it will cause all the X-related packages to be listed in the bug report. 'Gnome' would give you a bug report the size of an old-style telephone directory. You'll probably be asked to supply further information, by someone who knows what they want to see and where to find it. -- Joe
unable to determine which package my bug report should be filed against - please advise.
Hello Debian support team. I am a happy Dabian 9 user. I would like to report an issue I am experiencing. In the past I used a package 'reportbug' to report bugs, but by design, I have to identify what package the issue is related to. I am not sure exactly what may be the cause of the issue, and I am reaching out to you for help to identify what part of Debain might be causing this issue. The issue: I am using a second monitor (external monitor connected via a displayport - LG 29UM57-P). External monitor connected to my laptop - Lenovo T420. External monitor does not display video at the desired resolution and the aspect ratio. Displayed resolution - 1920 x 1080 Displayed aspect ratio - 16:9 Expected resolution - 2560 x 1080 Expected ratio - 21:9 This same exact issue exist on my other machine Lenovo X230 with external monitor of exact same model. Previous version of Debian 8 (jessie) worked with out any issue with the monitor at the correct and expected resolution and the aspect ratio. After installing a fresh version of Debian 9 (Stretch), I am unable to use the external monitor at its maximum resolution. Debian 9 (Stretch) was a full installation from scratch (not an upgrade). All cables has been tested, and hardware issues has been ruled out. I am not sure if I should be filing a bug report identifying Gnome3, or X11 as a cause of the issue or some other part of the OS. Could you please advise. Thank you. Damien
Re: Re: I need help to determine package name for a bug report.
No, but since every one works in memory, one of its segments may be defective. Memtest writes and reads ... but not concurrent. 2017-08-27 23:16 GMT+02:00 Fungi4All: > > From: zoltan...@gmail.com > To: Debian User > > I would try to exchange the memories by swapping... > > 2017-08-27 16:36 GMT+02:00 Alexander V. Makartsev : > >> Package: linux-image-4.9.0-3-amd64 >> Version: 4.9.30-2+deb9u3 >> Maintainer: Debian Kernel Team >> >> I've already checked memory with memtest86+ and found no errors. My >> hardware pretty recent (Skylake i5 CPU and H170 Chipset based mobo) >> Also these errors always begin with "kernel: alsa-sink-ALC88: Corrupted >> page table at address", so I doubt it is hardware problem. >> >> On 27.08.2017 15:35, Zoltán Herman wrote: >> > kernel team >> > linux-image- >> > >> > May be a memory error? >> > >> > > Do sound cards have memory chips on them? How can we tell? If they do > could this be a source of the above problem that memtest doesn't test? > >
Re: Re: I need help to determine package name for a bug report.
> From: zoltan...@gmail.com > To: Debian User> > I would try to exchange the memories by swapping... > > 2017-08-27 16:36 GMT+02:00 Alexander V. Makartsev : > >> Package: linux-image-4.9.0-3-amd64 >> Version: 4.9.30-2+deb9u3 >> Maintainer: Debian Kernel Team >> >> I've already checked memory with memtest86+ and found no errors. My >> hardware pretty recent (Skylake i5 CPU and H170 Chipset based mobo) >> Also these errors always begin with "kernel: alsa-sink-ALC88: Corrupted >> page table at address", so I doubt it is hardware problem. >> >> On [27.08.2017 15](tel:27.08.2017%2015):35, Zoltán Herman wrote: >>> kernel team >>> linux-image- >>> >>> May be a memory error? >>> Do sound cards have memory chips on them? How can we tell? If they do could this be a source of the above problem that memtest doesn't test?
Re: Re: I need help to determine package name for a bug report.
I would try to exchange the memories by swapping... 2017-08-27 16:36 GMT+02:00 Alexander V. Makartsev: > Package: linux-image-4.9.0-3-amd64 > Version: 4.9.30-2+deb9u3 > Maintainer: Debian Kernel Team > > I've already checked memory with memtest86+ and found no errors. My > hardware pretty recent (Skylake i5 CPU and H170 Chipset based mobo) > Also these errors always begin with "kernel: alsa-sink-ALC88: Corrupted > page table at address", so I doubt it is hardware problem. > > On 27.08.2017 15:35, Zoltán Herman wrote: > > kernel team > > linux-image- > > > > May be a memory error? > > > >
Re: Re: I need help to determine package name for a bug report.
Package: linux-image-4.9.0-3-amd64 Version: 4.9.30-2+deb9u3 Maintainer: Debian Kernel TeamI've already checked memory with memtest86+ and found no errors. My hardware pretty recent (Skylake i5 CPU and H170 Chipset based mobo) Also these errors always begin with "kernel: alsa-sink-ALC88: Corrupted page table at address", so I doubt it is hardware problem. On 27.08.2017 15:35, Zoltán Herman wrote: > kernel team > linux-image- > > May be a memory error? >
Re: I need help to determine package name for a bug report.
kernel team linux-image- May be a memory error? 2017. aug. 27. 12:13 ezt írta ("Alexander V. Makartsev" <avbe...@gmail.com >): Hello. On rare occasion, I have these strange system lockups that seems to be tied to "ALC88" sound driver\kernel module. I am unable to determine package name to file a bug report. All information I have is this syslog from previous boot. Got it with "journalctl -b -1" >From what I can tell it could be alsa, or pulseaudio, or kernel, or one of its modules. cut авг 25 20:45:59 fortune kernel: alsa-sink-ALC88: Corrupted page table at address 7f018fe0 авг 25 20:45:59 fortune kernel: PGD 442eb9067 авг 25 20:45:59 fortune kernel: PUD 423196067 авг 25 20:45:59 fortune kernel: PMD 80045fae08e7 cut авг 25 20:45:59 fortune kernel: sched: RT throttling activated авг 25 20:45:59 fortune kernel: BUG: unable to handle kernel paging request at fffeffa0005f авг 25 20:45:59 fortune kernel: IP: [] 0xfffeee19a725 авг 25 20:45:59 fortune kernel: PGD 346a0a067 авг 25 20:45:59 fortune kernel: PUD 0 авг 25 20:45:59 fortune kernel: авг 25 20:45:59 fortune kernel: Oops: [#2] SMP cut авг 25 20:46:33 fortune kernel: kernel BUG at /build/linux-me40Ry/linux-4.9.30/mm/slab.c:2981! авг 25 20:46:33 fortune kernel: invalid opcode: [#3] SMP cut авг 25 20:46:33 fortune kernel: NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [psensor:1185] cut