[Touch-packages] [Bug 1990863] Re: conversion from sshd service to socket is too bumpy
I don't have a complete solution to this, but I do have several points. - debconf prompts on upgrade are not, in general, good UX. It disrupts the flow of the upgrade. Sometimes it's necessary, but if all it's doing is telling the user they *may* have a broken config after upgrading, well, if every package for which that's true did that upgrades would be very slow indeed. And for users upgrading a large number of systems, that becomes one more nuisance. So no, I don't think we should add a prompt on upgrade for this. (There's also the practical problem that if we introduced such a prompt at this point in the release cycle, it would not realistically get translated, reducing accessibility for our users vs communicating this in other ways that could be localized out-of-band.) - As Robie pointed out in comment #4, there is no guarantee that ansible playbooks work consistently across releases. Regardless of whether we made changes that would have allowed the migration of settings in your case, if you had had to reinstall kinetic instead of upgrading from jammy, those changes in the openssh-server maintainer scripts would not have taken effect. Your ansible playbook is therefore buggy wrt kinetic, and should be fixed, which is out of scope for Ubuntu and the bug tracker. But the following contents in a file named /etc/systemd/system/ssh.socket.d/addresses.conf should set you on the right path: [Socket] ListenStream= ListenStream=$portnum - I have long been displeased with ucf's three-way-merge support. In particular, when identical content exists both in the user's version and in the new version but not in the base version, ucf will treat this as a merge conflict. This is awful, and specifically caused problems for upgrades from all cloud images when the user had not modified the sshd config at all (LP: #1990863). I've applied a workaround for this in openssh 1ubuntu7 (currently in the unapproved queue) that's specific to the cloud image case and ensures clean upgrades without prompting for users that have not modified sshd_config. I could generalize this to all users with modified configs, resulting in two prompts on upgrade but a better chance of successful three-way merging. Do you think that would be an improvement over the status quo? - Finally, there is some code I'm evaluating landing that would add a systemd generator for the listenstream settings. This would only take effect at boot, but would make it possible for users to continue managing their port/listenaddress settings in sshd.conf as before. However, we would not land this in time for the kinetic release, but would instead consider it for the next release to improve our LTS-to-LTS compatibility. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1990863 Title: conversion from sshd service to socket is too bumpy Status in openssh package in Ubuntu: New Bug description: During upgrade from Jammy to Kinetic, I get asked what to do because my sshd_config has been modified. I say to do a 3-way merge. It says 3-way merge fails. I shrug, figure I'll just restore my customizations with Ansible after the upgrade like I always do, and tell it to use the vendor version of the file. This removes my custom Port settings, so they are not migrated over to the ssh.socket settings like https://discourse.ubuntu.com/t/sshd-now-uses-socket-based-activation- ubuntu-22-10-and-later/30189 says they would be. I subsequently run my Ansible which restores the customizations and enables the ssh service, but now ssh.service and ssh.socket are enabled at the same time, sshd isn't listening on my specified ports, and everything is a mess. I've never used socket-based activation before and have no idea how to configure it so now I have to go reading man pages, Googling all over the place, and generally struggle to figure out what the heck is going wrong. I don't know what the right answer is here, but I really feel like some effort needs to be put into figuring out a smoother transition for people who are upgrading to Kinetic. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: openssh-server 1:9.0p1-1ubuntu6 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Sep 26 11:41:58 2022 InstallationDate: Installed on 2019-08-16 (1136 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: openssh UpgradeStatus: Upgraded to kinetic on 2022-09-24 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1990863/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-p
[Touch-packages] [Bug 1833863] Re: Incorrect logic for
** Bug watch added: gitlab.xfce.org/xfce/garcon/-/issues #32 https://gitlab.xfce.org/xfce/garcon/-/issues/32 ** Also affects: garcon via https://gitlab.xfce.org/xfce/garcon/-/issues/32 Importance: Unknown Status: Unknown ** Changed in: garcon (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pyxdg in Ubuntu. https://bugs.launchpad.net/bugs/1833863 Title: Incorrect logic for Status in Garcon: Unknown Status in PyXDG: New Status in garcon package in Ubuntu: Triaged Status in pyxdg package in Ubuntu: New Status in xubuntu-default-settings package in Ubuntu: Fix Released Bug description: XFCE & Xubuntu use in their menu files, which python-xdg currently (all current versions) does not handle correctly: https://gitlab.freedesktop.org/xdg/pyxdg/issues/12 I think the fix is as simple as --- Menu.py.a 2019-06-23 17:44:24.992850139 +0100 +++ Menu.py.b 2019-06-23 17:44:41.052807584 +0100 @@ -997,7 +997,7 @@ for menuentry in menu.MenuEntries: if menuentry not in tmp_e: menu.Entries.append(menuentry) -elif order[1] == "menus" or order[1] == "all": +if order[1] == "menus" or order[1] == "all": menu.Submenus.sort() for submenu in menu.Submenus: if submenu.Name not in tmp_s: But as it can also be trivially worked around by replacing with , I wonder if this should be done in XFCE/Xubuntu? To manage notifications about this bug go to: https://bugs.launchpad.net/garcon/+bug/1833863/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog
For 22.04, I can additionally confirm the problem for Vivaldi's save dialog. Whereas the seemingly identical dialog in LibreOffice works as intended. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1949340 Title: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog Status in Mozilla Firefox: New Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in gtk4 package in Ubuntu: Confirmed Status in xdg-desktop-portal-gnome package in Ubuntu: Confirmed Status in xdg-desktop-portal-gtk package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Open Chromium (release does not matter, here deb-packaged version from 18.04 LTS is used) 2a. Navigate to some page, press + 2b. Navigate to some page, with "Ask where to save each file before downloading" enabled try to download some file Actual result: * file chooser dialog is unfocused, user should select the window by mouse and then hit for specified location Expected result: * file chooser dialog is focused, user can simply hit to save in previously selected location. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1949340/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1910913] Re: Deprecating gdebi
https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1524053 ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1910913 Title: Deprecating gdebi Status in gdebi package in Ubuntu: Invalid Bug description: Purpose of gdebi is to allow installing packages from a file. However, it's been 6 years since apt supported installation from a file¹. Let's make it easier on both maintainers and the people who have to install/use `gdebi` and then may need to search nuances, like passing options to dpkg. As far as I read gdebi man page, its functional seems fully covered by apt. The only thing I'm a bit in doubts about is the `root` option. But from my reading of docs, it seems that `gdebi --root=/foo myfile.deb` would be analogous to `apt install -o Dpkg::Options::="-- root=/foo" ./myfile.deb`. So, my suggesttion: installing gdebi on currently supported releases should print a deprecation notice that explains how a user can install local files with `apt` instead. Then eventually remove gdebi from repositories. I tried contacting maintainers of gdebi to ask whether it's worth adding a deprecation notice, but haven't found any ways to do that, and so I went straight to creating a report here. 1: https://mvogt.wordpress.com/2015/11/30/apt-1-1-released/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1910913/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1524053] Re: Gdebi 0.9.5.7 doesn't show required dependencies list on non Xubuntu Session than a line.
Soon 7 years later, no improvement ? On 22.04 the part of window showing needed dependencies won't resize, only 3~4 lines displayed. Same kind of readability issues in « Users and Groups ( provided by gnome-system-tools ) see https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/1978245 ** Attachment added: "gdebi window that does not resize accordingly to its content." https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1524053/+attachment/5620446/+files/gdebi.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1524053 Title: Gdebi 0.9.5.7 doesn't show required dependencies list on non Xubuntu Session than a line. Status in gdebi package in Ubuntu: Confirmed Bug description: I've tried both Ubuntu Minimal+XFCE & Xubuntu 16.04 This gravely affect of XFCE, Openbox session on Ubuntu 16.04. However this doesn't happen on Xubuntu 16.04 Session at all it shows dependencies list normally But on XFCE, Openbox session it only shows a line. We need more tester to confirm other session as well such as: Unity, Ubuntu, KDE, Kubuntu, lxde, lxde, Lubuntu, Edubuntu, Mythbuntu, To confirm if it's only affect on non-Ubuntu flavor Sessions. or are they affect to all Sessions Except Xubuntu Session? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1524053/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958019]
You could share your dmesg. The other possibility is that the kernel doesn't include the configuration (arch IIRC?). On 10/1/22 04:48, bugzilla-dae...@kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=208555 > > --- Comment #698 from jochemp...@gmail.com --- > (In reply to Cameron Berkenpas from comment #697) >> Created attachment 301907 [details] >> attachment-12523-0.html >> >> Almost certainly your laptop doesn't have the _DSD entries needed to >> properly get sound working. >> >> Check dmesg for either of these messages: >> dmesg | grep -i "Platform not supported -EINVAL" >> or >> dmesg | grep -i "Error: ACPI _DSD Properties are missing for HID" >> >> For reference, see: >> https://www.spinics.net/lists/alsa-devel/msg146157.html >> https://bugzilla.kernel.org/show_bug.cgi?id=216194 >> >> I have the same problem with the Lenovo Legion 2022 Gen 7 (16IAX7). I >> filed a support ticket with Lenovo a few weeks back, but when support >> followed back they wanted to text during work hours, and I was too busy >> to deal with that then and too busy to deal with it since. I think I may >> actually have some time today. >> >> If you have either message in your dmesg, I'd suggest filing a support >> ticket. If enough people complain about these issues, it may compel them >> to add the proper _DSD entries into a BIOS update. >> >> There's no reason that Lenovo can't include this information in a BIOS >> update. It does seem that going forward that the intention of Cirrus >> Logic is for the vendors to include this information in the BIOS. For >> vendors where this is not the case, likely what's happening is that >> these values are hard coded in the vendor provided drivers or firmware. >> >> It doesn't require them to touch Linux at all. >> >> It should be relatively simple for them to add this information as >> there's already an incomplete entry in the ACPI table as it is. >> >> In the kernel bug linked above, I attached a hacky patch that gets sound >> working on the 16IAX7... But it's a hack where I guessed and hard-coded >> the values and these could physically damage your speakers if the >> settings are too inappropriate for your model of laptop (including the >> 16IAX7). This is very much a USE AT YOUR OWN RISK scenario, and I >> sincerely recommend against using my patches to avoid any possibility of >> damage to your laptop. Furthermore, sound doesn't work after resume anyway. >> >> Although it could be argued that if people start trying to use hacks >> like these to enable sound under Linux for their laptop, vendors such as >> Lenovo may need to issue BIOS updates to address this to avoid costly >> laptop repairs. >> >> On 9/30/22 05:11, bugzilla-dae...@kernel.org wrote: >>> https://bugzilla.kernel.org/show_bug.cgi?id=208555 >>> >>> jochemp...@gmail.com changed: >>> >>> What|Removed |Added >>> >> >>>CC||jochemp...@gmail.com >>> >>> --- Comment #696 fromjochemp...@gmail.com --- >>> I seem to have the same issue on a lenovo Legion S7 16ARHA7, here is my >>> alsa-info hopefully it's of some use: >>> http://alsa-project.org/db/?f=59acbf18b993b0a49edaaee0027d4b57fcf2055c >>> > Thanks for the info, appreciate it. > using grep i didn't find any of those messages though. so might not be the > same > issue after all then. > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic fail
[Touch-packages] [Bug 1958019]
(In reply to Cameron Berkenpas from comment #697) > Created attachment 301907 [details] > attachment-12523-0.html > > Almost certainly your laptop doesn't have the _DSD entries needed to > properly get sound working. > > Check dmesg for either of these messages: > dmesg | grep -i "Platform not supported -EINVAL" > or > dmesg | grep -i "Error: ACPI _DSD Properties are missing for HID" > > For reference, see: > https://www.spinics.net/lists/alsa-devel/msg146157.html > https://bugzilla.kernel.org/show_bug.cgi?id=216194 > > I have the same problem with the Lenovo Legion 2022 Gen 7 (16IAX7). I > filed a support ticket with Lenovo a few weeks back, but when support > followed back they wanted to text during work hours, and I was too busy > to deal with that then and too busy to deal with it since. I think I may > actually have some time today. > > If you have either message in your dmesg, I'd suggest filing a support > ticket. If enough people complain about these issues, it may compel them > to add the proper _DSD entries into a BIOS update. > > There's no reason that Lenovo can't include this information in a BIOS > update. It does seem that going forward that the intention of Cirrus > Logic is for the vendors to include this information in the BIOS. For > vendors where this is not the case, likely what's happening is that > these values are hard coded in the vendor provided drivers or firmware. > > It doesn't require them to touch Linux at all. > > It should be relatively simple for them to add this information as > there's already an incomplete entry in the ACPI table as it is. > > In the kernel bug linked above, I attached a hacky patch that gets sound > working on the 16IAX7... But it's a hack where I guessed and hard-coded > the values and these could physically damage your speakers if the > settings are too inappropriate for your model of laptop (including the > 16IAX7). This is very much a USE AT YOUR OWN RISK scenario, and I > sincerely recommend against using my patches to avoid any possibility of > damage to your laptop. Furthermore, sound doesn't work after resume anyway. > > Although it could be argued that if people start trying to use hacks > like these to enable sound under Linux for their laptop, vendors such as > Lenovo may need to issue BIOS updates to address this to avoid costly > laptop repairs. > > On 9/30/22 05:11, bugzilla-dae...@kernel.org wrote: > > https://bugzilla.kernel.org/show_bug.cgi?id=208555 > > > > jochemp...@gmail.com changed: > > > > What|Removed |Added > > > > > CC||jochemp...@gmail.com > > > > --- Comment #696 fromjochemp...@gmail.com --- > > I seem to have the same issue on a lenovo Legion S7 16ARHA7, here is my > > alsa-info hopefully it's of some use: > > http://alsa-project.org/db/?f=59acbf18b993b0a49edaaee0027d4b57fcf2055c > > Thanks for the info, appreciate it. using grep i didn't find any of those messages though. so might not be the same issue after all then. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pu
[Touch-packages] [Bug 1989803] Re: Adjust apport for the new Ubuntu debuginfod service
** Changed in: apport (Ubuntu) Assignee: Sergio Durigan Junior (sergiodj) => Benjamin Drung (bdrung) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1989803 Title: Adjust apport for the new Ubuntu debuginfod service Status in Apport: Fix Committed Status in apport package in Ubuntu: In Progress Bug description: With the new Ubuntu debuginfod service (https://debuginfod.ubuntu.com), and with the prospect of having the system automatically fetch debuginfo from the internet without user intervention, it is necessary to adjust apport to cope with this scenario. I had a conversation with bdmurray and he was concerned that having a debuginfod-enabled GDB generate the corefiles that are eventually submitted to Ubuntu can be a problem. My proposed solution is to disable GDB's debuginfod support when collecting the corefile. This should keep things as is and not disturb the retrace service. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1989803/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1967648] Re: lubuntu jammy - `ubuntu-bug lxqt-config` isn't opening firefox
*** This bug is a duplicate of bug 1973470 *** https://bugs.launchpad.net/bugs/1973470 Yes, xdg-open detects the desktop environment and behaves differently depending on it. This is a duplicate of bug #1973470. ** This bug has been marked a duplicate of bug 1973470 Ubuntu-bug command can't find Firefox on Lubuntu Kinetic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1967648 Title: lubuntu jammy - `ubuntu-bug lxqt-config` isn't opening firefox Status in apport package in Ubuntu: Confirmed Bug description: /usr/bin/xdg-open: 882: firefox: not found /usr/bin/xdg-open: 882: firefox: not found xdg-open: no method available for opening 'https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+filebug/9f12535a-b2f0-11ec-b9ed-40a8f0305cb4?' Lubuntu jammy install test on dell optiplex 780 I adjusted displays as mouse-movements were annoying me, noticed an issue thus filed a bug report using `ubuntu-bug lxqt-config` ** expected output on executing `ubuntu-but lxqt-config` I expected firefox to start ** actual output --- lubuntu@lubuntu:~$ ubuntu-bug lxqt-config *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. ... *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (19.6 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): s *** Uploading problem information The collected information is being sent to the bug tracking system. This might take a few minutes. 98% *** To continue, you must visit the following URL: https://bugs.launchpad.net/ubuntu/+source/lxqt- config/+filebug/9f12535a-b2f0-11ec-b9ed-40a8f0305cb4? You can launch a browser now, or copy this URL into a browser on another computer. Choices: 1: Launch a browser now C: Cancel Please choose (1/C): 1 /usr/bin/xdg-open: 882: firefox: not found /usr/bin/xdg-open: 882: firefox: not found xdg-open: no method available for opening 'https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+filebug/9f12535a-b2f0-11ec-b9ed-40a8f0305cb4?' --- ie. `firefox` doesn't start as it's now a snap package first attempt to file `ubuntu-bug apport` ended up with --- *** To continue, you must visit the following URL: https://bugs.launchpad.net/ubuntu/+source/lxqt- config/+filebug/9f12535a-b2f0-11ec-b9ed-40a8f0305cb4? You can launch a browser now, or copy this URL into a browser on another computer. Choices: 1: Launch a browser now C: Cancel Please choose (1/C): 1 /usr/bin/xdg-open: 882: firefox: not found /usr/bin/xdg-open: 882: firefox: not found xdg-open: no method available for opening 'https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+filebug/9f12535a-b2f0-11ec-b9ed-40a8f0305cb4?' lubuntu@lubuntu:~$ --- ** other notes - I don't know if this only impacts lubuntu, or others too - I've not (yet) looked for other/existing bugs ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apport 2.20.11-0ubuntu80 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: LXQt Date: Sun Apr 3 12:09:05 2022 LiveMediaBuild: Lubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220402) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1967648/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1991324] Re: Initramfs-tools: iSCSI boot resulting in modprobe not found error message
Herewitht the bootlog from serial console of the PI (btw this is from Kinetic Kudo e.g. bug is persistent in multiple versions 22.04.1 and 22.10) To reproduce: 1. Install pristine Ubuntu Server for PI/ARM64 on SD or USB. 2. Install open-iscsi, lvm2, nfs-common 3. Configure iSCSI initiator 4. Attach iSCSI volume from NAS 5. Create LVM on iSCSI volume 6. Reinstall linux-image, linux-modules and linux-modules-extra to generate initramfs 6. Rsync SD card to iSCSI 7. Copy /boot/firmware to TFTPBOOT dir on NAS 8. Alter cmdline.txt for iSCSI boot 9. Reboot PI from iSCSI 9a PI4 gets vmlinuz, cmdline.txt, config.txt and initrd.img from NAS 9b Kernel boots succesfully 9c Init in RAM disk complains about binaries that it cannot find Hope this helps ** Attachment added: "pi4-iscsi-initramfs-boot.log" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1991324/+attachment/5620431/+files/pi4-iscsi-initramfs-boot.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1991324 Title: Initramfs-tools: iSCSI boot resulting in modprobe not found error message Status in initramfs-tools package in Ubuntu: Incomplete Bug description: My RPi4's are having their rootvg on iSCSI and boot from them. The kernel modules etc are in the initramfs. However since 22.04 the initramfs is not generated corrected and while booting from it it results in error messages stating various binaries/scripts are not locatable. E.g. modprobe, systemd-udev, mdadm etc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1991324/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1711231] Re: xdiagnose me trajo hasta aqui por algun problema de xorg
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. This release of Ubuntu is no longer receiving maintenance updates. Is this issue still relevant when using a currently supported release of Ubuntu? If so then please let us know otherwise this report can be left to expire in approximately 60 days time. ** Description changed: no se darles mas detalles + + Google translation: + I don't know how to give you more details ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 .tmp.unity_support_test.0: - + ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Aug 16 19:15:53 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: - Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) -Subsystem: ASUSTeK Computer Inc. Broadwell-U Integrated Graphics [1043:196d] + Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) + Subsystem: ASUSTeK Computer Inc. Broadwell-U Integrated Graphics [1043:196d] InstallationDate: Installed on 2017-06-12 (65 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Lsusb: - Bus 001 Device 003: ID 0bda:57bc Realtek Semiconductor Corp. - Bus 001 Device 002: ID 8087:8001 Intel Corp. - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 001 Device 003: ID 0bda:57bc Realtek Semiconductor Corp. + Bus 001 Device 002: ID 8087:8001 Intel Corp. + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X751LAB ProcEnviron: - LANGUAGE=es_AR:es - PATH=(custom, no user) - LANG=es_AR.UTF-8 - SHELL=/bin/bash + LANGUAGE=es_AR:es + PATH=(custom, no user) + LANG=es_AR.UTF-8 + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic root=UUID=c128aeae-24fb-4403-b895-02ae42e88920 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/07/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X751LAB.507 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X751LAB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX751LAB.507:bd12/07/2015:svnASUSTeKCOMPUTERINC.:pnX751LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX751LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X751LAB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Aug 16 16:06:01 2017 xserver.configfile: default xserver.errors: - + xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1~16.04.2 xserver.video_driver: modeset ** Summary changed: - xdiagnose me trajo hasta aqui por algun problema de xorg + xdiagnose me trajo hasta aqui por algun problema de xorg (xdiagnose brought me here because of some xorg problem) ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1711231 Title: xdiagnose me trajo hasta aqui por algun problema de xorg (xdiagnose brought me here because of some xorg problem) Status in xorg package in Ubuntu: Incomplete Bug description: no se darles mas detalles Google translation: I don't know how to give you more details ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-
[Touch-packages] [Bug 1444895] Re: xrandr --brightness resets gamma ratio
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Unfortunately you didn't tell us with which Ubuntu release you were seeing the reported issue. Is this still relevant when using a currently supported release of Ubuntu? If so then please let us know which one(s) otherwise this report can be left to expire in approximately 60 days time. ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1444895 Title: xrandr --brightness resets gamma ratio Status in xorg package in Ubuntu: Incomplete Bug description: $ xrandr --verbose | grep -iE '(gamma|bright)' Gamma: 1.0:1.0:1.7 Brightness: 1.0 $ xrandr --output VGA1 --brightness .75 $ xrandr --verbose | grep -iE '(gamma|bright)' Gamma: 1.0:1.0:1.0 Brightness: 0.75 As can be seen in the above command output, changing the brightness with xrandr resets the gamma ratio to 1/1/1/ instead of 1/1/.6 (values in xrandr --verbose output are inverted...) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1444895/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1585957] Re: DPMS support removed?
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. This release of Ubuntu is no longer receiving maintenance updates. Is this issue still relevant when using a currently supported release of Ubuntu? If so then please let us know otherwise this report can be left to expire in approximately 60 days time. ** Changed in: xorg (Ubuntu) Status: New => Incomplete ** Tags added: xenial ** Package changed: xorg (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1585957 Title: DPMS support removed? Status in Ubuntu: Incomplete Bug description: I have a script in which I used: xset dpms standby 0 ; xset dpms suspend 0 ; xset dpms off 0 Today, when I run the script, I get: $ xset dpms standby 0 xset: unknown option standby [...synopsis of available commands...] $ xset dpms suspend 0 xset: unknown option suspend [...] However, reading the synopsis that is output after the error, I read: To control Energy Star (DPMS) features: -dpms Energy Star features off +dpms Energy Star features on dpms [standby [suspend [off]]] force standby force suspend force off force on (also implicitly enables DPMS features) a timeout value of zero disables the mode So standby and suspend are suposed to exist... There is either a bug in the code or in the doc! $ cat /etc/issue Ubuntu 16.04 LTS \n \l $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=16.04 DISTRIB_CODENAME=xenial DISTRIB_DESCRIPTION="Ubuntu 16.04 LTS" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1585957/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1593586] Re: Issue with two external screens
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Thank you for comment #4 Michael. I'm glad that your issue was resolved but so sorry that it has taken almost six years for anyone here to acknowledge that comment. I'm closing this as 'Fix Released' as it appears your issue was fixed with one or more Ubuntu updates. ** Changed in: xorg (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1593586 Title: Issue with two external screens Status in xorg package in Ubuntu: Fix Released Bug description: When I boot my Laptop (Dell latitude 7470 + Dell E-Port Plus II docking station) with two external Dell screens attached (via Display port, each separate connected) at the beginning of my session everything works fine. The lid is closed while booting. After starting Firefox the focus of the mouse is some how lost. Then it is not possible to open the context menu of Firefox. Typed letters appear on the other screen. The focus is also lost when I remove the Laptop from the dockingstation and attach it back to the docking station. The focus works fine when only the built-in display is used. WORKAROUND: Boot the laptop at the beginning with only one attached screen (cable disconnected). After login attach the second screen, open the "Displays" configuration menu, and click on something without changing the configuration. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Jun 17 08:16:07 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake Integrated Graphics [1028:06dc] InstallationDate: Installed on 2016-06-10 (6 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Latitude E7470 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-24-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.3 dmi.board.name: 0T6HHJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.3:bd04/18/2016:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7470 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Jun 17 08:04:44 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1168 vendor LGD xserver.version: 2:1.18.3-1ubuntu2.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1593586/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1667881] Re: hdmi
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. This release of Ubuntu is no longer receiving maintenance updates. Is this issue still relevant when using a currently supported release of Ubuntu? If so then please let us know otherwise this report can be left to expire in approximately 60 days time. ** Description changed: o sistema não reconhece a tyv, através da entrada/saída HDMI + + Google translation: + the system does not recognize the tyv, through the hdmi input/output ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44 Uname: Linux 4.4.0-64-generic x86_64 .tmp.unity_support_test.0: - + ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Feb 25 01:16:38 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: - i915-4.6.3-4.4.0, 1, 4.4.0-21-generic, x86_64: installed - i915-4.6.3-4.4.0, 1, 4.4.0-64-generic, x86_64: installed + i915-4.6.3-4.4.0, 1, 4.4.0-21-generic, x86_64: installed + i915-4.6.3-4.4.0, 1, 4.4.0-64-generic, x86_64: installed GraphicsCard: - Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) -Subsystem: Acer Incorporated [ALI] Core Processor Integrated Graphics Controller [1025:0487] + Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) + Subsystem: Acer Incorporated [ALI] Core Processor Integrated Graphics Controller [1025:0487] InstallationDate: Installed on 2017-02-21 (3 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Gateway NV55C ProcEnviron: - LANGUAGE=pt_BR:pt:en - PATH=(custom, no user) - LANG=pt_BR.UTF-8 - SHELL=/bin/bash + LANGUAGE=pt_BR:pt:en + PATH=(custom, no user) + LANG=pt_BR.UTF-8 + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic root=UUID=beab8c72-b619-44a3-a386-7c39ccfb2730 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/09/2011 dmi.bios.vendor: Gateway dmi.bios.version: V1.27 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NV55C dmi.board.vendor: Gateway dmi.board.version: V1.27 dmi.chassis.type: 10 dmi.chassis.vendor: Gateway dmi.chassis.version: V1.27 dmi.modalias: dmi:bvnGateway:bvrV1.27:bd11/09/2011:svnGateway:pnNV55C:pvrV1.27:rvnGateway:rnNV55C:rvrV1.27:cvnGateway:ct10:cvrV1.27: dmi.product.name: NV55C dmi.product.version: V1.27 dmi.sys.vendor: Gateway version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.75+git1702140630.f6499b~gd~x version.libgl1-mesa-dri: libgl1-mesa-dri 17.1~git1702241930.983348~gd~x version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.1~git1702241930.983348~gd~x version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.8.99+git1702221933.244d4b~gd~x version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git1702161933.860c36~gd~x version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.13+git1701262001.1516d3~gd~x xserver.bootTime: Sat Feb 25 01:05:52 2017 xserver.configfile: default xserver.errors: - + xserver.logfile: /var/log/Xorg.0.log xserver.outputs: - product id 732 - vendor LGD + product id 732 + vendor LGD xserver.version: 2:1.18.4-0ubuntu0.2 ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1667881 Title: hdmi Status in xorg package in Ubuntu: Incomplete Bug description: o sistema não reconhece a tyv, através da entrada/saída HDMI Google translation: the system does not recognize the tyv, through the hdmi input/output ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44 Uname: Linux 4.4.0-64-generic x86_64 .tmp.unity_support_test.0:
[Touch-packages] [Bug 1639017] Re: Unable to have Higher Resolution on Ubuntu 16.04
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. This release of Ubuntu is no longer receiving maintenance updates. Is this issue still relevant when using a currently supported release of Ubuntu? If so then please let us know otherwise this report can be left to expire in approximately 60 days time. ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1639017 Title: Unable to have Higher Resolution on Ubuntu 16.04 Status in xorg package in Ubuntu: Incomplete Bug description: Hi, I am only able to view the screen in 1024x768 resolution here is my output for lshw -c Video *-display description: VGA compatible controller product: Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 09 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:25 memory:f780-f7bf memory:e000-efff ioport:f000(size=64) I think the xorg driver is fully updated but still I am unable to run in higher resolution on ubuntu. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Nov 4 00:33:25 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [1458:d000] InstallationDate: Installed on 2016-10-31 (3 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic root=UUID=361b7ddd-636c-40e8-98a4-6f7c6ceb1f69 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/25/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61MS dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd06/25/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH61MS:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Nov 4 00:10:15 2016 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputVideo BusKEYBOARD, id 7 inputPower Button KEYBOARD, id 8 inputUSB Optical MouseMOUSE, id 9 inputAT Translated Set 2 keyboard KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.3-1ubuntu2.2 To ma
[Touch-packages] [Bug 1586659] Re: Notification don't appear when I'm in full screen mode
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. This release of Ubuntu is no longer receiving maintenance updates. Is this issue still relevant when using a currently supported release of Ubuntu? If so then please let us know otherwise this report can be left to expire in approximately 60 days time. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1586659 Title: Notification don't appear when I'm in full screen mode Status in Ubuntu: Incomplete Bug description: When I use full screen in different app. the notification about battery charge (especially when it's low) don't appear. When I don't use full screen, the notification appear. It's problematic because when the battery is low, I don't have notification before the laptop shut down. The same problem occur with Firefox and VLC. More info: The notification seem to be created but not showing on screen. If I'm in full screen and I return to regular mode, the notification appear. Also, if I'm in regular mode and the notification appear, when I change for the full screen mode, the notification stay on screen. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Sat May 28 11:36:06 2016 DistUpgraded: 2016-05-11 12:46:43,015 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 4.4.0-22-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] [1002:9851] (rev 45) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mullins [Radeon R4/R5 Graphics] [103c:80cb] InstallationDate: Installed on 2016-03-02 (87 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: HP HP Notebook ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed root=UUID=06f354f2-97a2-48a8-8ead-4bb66400bfa1 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to xenial on 2016-05-11 (16 days ago) dmi.bios.date: 10/19/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.1C dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 80CB dmi.board.vendor: HP dmi.board.version: 99.42 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.1C:bd10/19/2015:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn80CB:rvr99.42:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sat May 28 06:45:13 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.3-1ubuntu2 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1586659/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1696903] Re: 3d hardware problem
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. This release of Ubuntu is no longer receiving maintenance updates. Is this issue still relevant when using a currently supported release of Ubuntu? If so then please let us know otherwise this report can be left to expire in approximately 60 days time. ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1696903 Title: 3d hardware problem Status in xorg package in Ubuntu: Incomplete Bug description: Requested size (3200, 1080) exceeds 3D hardware limit (2048, 2048). You must either rearrange the displays so that they fit within a (2048, 2048) square. GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._gsd_2drr_2derror_2dquark.Code3: Requested size (3200, 1080) exceeds 3D hardware limit (2048, 2048). You must either rearrange the displays so that they fit within a (2048, 2048) square. this is showing when trying to connect to tv ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 Uname: Linux 4.8.0-36-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Jun 8 21:55:17 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [103c:30bb] Subsystem: Hewlett-Packard Company Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [103c:30bb] InstallationDate: Installed on 2017-06-07 (1 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Hewlett-Packard HP Pavilion dv6000 (RU696UA#ABL) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic root=UUID=01be26e4-ea37-4e70-9440-06c51957e7bb ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/22/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.2E dmi.board.name: 30BB dmi.board.vendor: Quanta dmi.board.version: 66.42 dmi.chassis.type: 10 dmi.chassis.vendor: Quanta dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.2E:bd03/22/2010:svnHewlett-Packard:pnHPPaviliondv6000(RU696UA#ABL):pvrRev1:rvnQuanta:rn30BB:rvr66.42:cvnQuanta:ct10:cvrN/A: dmi.product.name: HP Pavilion dv6000 (RU696UA#ABL) dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu Jun 8 21:19:32 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 13125 vendor SEC xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1696903/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1642929] Re: no screen output prior to login while in docking station
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. kringalf, thank you for comment #3. I'm sorry that it took nearly six years long for anyone to see that you had resolved the issue. I'm closing this as "Invalid" as Ubuntu 16.04 is no longer being maintained and the issue wasn't resolved by an Ubuntu update. ** Changed in: xorg (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1642929 Title: no screen output prior to login while in docking station Status in xorg package in Ubuntu: Invalid Bug description: while the laptop is in the docking station there is no output on any monitor as long as i'm not logged into kde. The output stops right after the password for the encrypted root disk and the screens stay blank until i login to kde if i start outside the docking station i get output on the screen through the whole boot process including the login process for kde ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Fri Nov 18 12:16:26 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: kubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0535] MachineType: Dell Inc. Latitude E6530 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-45-generic.efi.signed root=/dev/mapper/system-root_crypt ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/19/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0JC5MT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd08/19/2015:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn0JC5MT:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6530 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Nov 14 11:57:52 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 812 vendor LGD xserver.version: 2:1.18.4-0ubuntu0.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1642929/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1635872] Re: xorg freezes for long time after using virtual terminal
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. This release of Ubuntu is no longer receiving maintenance updates. Is this issue still relevant when using a currently supported release of Ubuntu? If so then please let us know otherwise this report can be left to expire in approximately 60 days time. ** Changed in: xorg (Ubuntu) Status: New => Incomplete ** Tags added: xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1635872 Title: xorg freezes for long time after using virtual terminal Status in xorg package in Ubuntu: Incomplete Bug description: Ubuntu: 16.04 xorg 1:7.7+13ubuntu3 Always reproducible, steps: a) start computer b) verify that Xorg is using some 0.7% CPU c) f1+ctrl+shift #go to virtual terminal d) f7+ctrl #back to the xorg Maybe 60 seconds mouse cursor can be barely moved, but keyboard and clicks are not responding after all. After that run script for monitoring CPU usage of Xorg. e) while [ 1 ] ; do top -b -n 1 | grep Xorg | awk {'print $9'} ; sleep 1; done CPU usage is almost 100% for 12...71 minutes and then calms down. Not sure if this relates display controllers (lspci | grep VGA): 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) 01:00.0 VGA compatible controller: NVIDIA Corporation GK107M [GeForce GT 650M Mac Edition] (rev a1) Or drivers (lsmod | grep video): video 40960 3 i915,nouveau,apple_gmux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1635872/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1665914] Re: Ubuntu 16.04 freezes on Thinkpad X61 Tablet when touched by the stylus
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Further to comments #3 and #4 I'm closing this bug report by changing the status to 'Fixed Released' as the issue was fixed by installing Ubuntu updates. I'm sorry that it took so long to respond to your comments. ** Changed in: xorg (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1665914 Title: Ubuntu 16.04 freezes on Thinkpad X61 Tablet when touched by the stylus Status in xorg package in Ubuntu: Fix Released Bug description: I have (up to date) Ubuntu 16.04 on IBM Thinkpad X61 Tablet. I can use the stylus to move the cursor – but when I touch the screen with it (i.e. click), the system immediately freezes. When I touch it without X, in the text mode (Ctrl+Alt+F1) it does not freeze. I tried to debug it over network, but the network also freezes at the same moment. When I try QubesOS (with kernel 4.1.13-9.pvops.qubes.x86_64) on the same machine, the stylus works correctly and the system does not freeze. Any tips how to debug it? Maybe using the serial port (I have the docking station with RS232). Or I can try some older releases and find the last one that was working if it helps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1665914/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1667133] Re: touch is constantly jumping around (ghost touching)
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. This release of Ubuntu is no longer receiving maintenance updates. Is this issue still relevant when using a currently supported release of Ubuntu? If so then please let us know otherwise this report can be left to expire in approximately 60 days time. ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1667133 Title: touch is constantly jumping around (ghost touching) Status in xorg package in Ubuntu: Incomplete Bug description: The issue I am having is very similar to this bug: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1574667 Depending on what applications are running the apparently random behavior may increase. Sometimes it is really bad and several times in one second the system detects random touches around the screen. As a result Ubuntu automatically zooms in or out or moves the content of screen around or the focus is stolen. Right now as I am typing this bug I am getting very dizzy because the UI is constantly zooming in and out. I have noticed this happens a lot (A LOT!) more frequently when chrome is opened. I have tried removing a few xorg input packages as a desperate attempt to stop this: ``` sudo apt-get remove --purge xserver-xorg-input-libinput sudo apt-get remove --purge xserver-xorg-input-synaptics sudo apt-get remove --purge xserver-xorg-input-wacom ``` Right now my touch screen is not working and my touchpad never worked. I have plugged in an external mouse and it works, up until the focus gets stolen from it by random touches around the screen. Before I removed libinput mouse pointer was also jumping constantly to a random location. But since I remove libinput, mouse cursor stays where it is but random touches seems to be happening anyway. This is extremely annoying behavious and is rendering my laptop useless. I am using Acer Spin 5 ``` $ lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 007: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 006: ID 0bda:57f3 Realtek Semiconductor Corp. Bus 001 Device 005: ID 2386:3111 Bus 001 Device 004: ID 04ca:3015 Lite-On Technology Corp. Bus 001 Device 009: ID 05b8:3279 Agiler, Inc. Bus 001 Device 008: ID 17ef:6019 Lenovo Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ``` ``` $ dmesg |grep touch [2.558494] hid-multitouch 0018:04F3:3018.0001: Ignoring the extra HID_DG_INPUTMODE [2.558662] hid-multitouch 0018:04F3:3018.0001: input,hidraw0: I2C HID v1.00 Mouse [ELAN0501:00 04F3:3018] on i2c-ELAN0501:00 [3.294025] hid-multitouch 0003:2386:3111.0006: input,hiddev0,hidraw1: USB HID v1.10 Device [Raydium Corporation Raydium Touch System] on usb-:00:14.0-6/input0 ``` ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-63.84-generic 4.4.44 Uname: Linux 4.4.0-63-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Feb 22 13:35:35 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:1139] InstallationDate: Installed on 2016-07-26 (211 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Acer Spin SP513-51 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-63-generic.efi.signed root=UUID=45f1b204-27f6-467d-97ee-0d12b3b14388 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.02 dmi.board.name: Drift_SK dmi.board.vendor: KBL dmi.board.version: V1.02 dmi.chassis.type: 31 dmi.chassis.vendor: Acer dmi.chassis.version: V1.02 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.02:bd10/20/2016:svnAcer:pnSpinSP513-51:pvrV1.02:rvnKBL:rnDrift_SK:rvrV1.02:cvnAcer:ct31:cvrV1.02: dmi.product.name: Spin SP513-51 dmi.product.version: V1.02 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: i
[Touch-packages] [Bug 1586787] Re: Wrong colors on external TV
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue when using a currently supported release of Ubuntu then please let us know otherwise this report can be left to expire in approximately 60 days time. (Your comment #3 has been noted by the way). ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1586787 Title: Wrong colors on external TV Status in xorg package in Ubuntu: Incomplete Bug description: Hi, On a Lenovo Thinkpad T420, with an Intel Core i5-2520M CPU and integrated graphics, when using a Samsung UE40J5200AW 40in TV with a DisplayPort to HDMI adapter and an HDMI cable, the colors are very wrong on the TV. This happens on a brand new Ubuntu 16.04 installation made from scratch, and it does not happen when I boot from a Linux Mint 17.3 "Rosa" Cinnamon 64-bit live DVD. So same laptop, same adapter, same cable, same TV, and the colors are fine on the TV in this case (Mint live DVD). Also, when switching the laptop with a Dell running Windows 8.1 (so the same adapter, cable, and TV are used), the colors are again fine. I have attached a picture that shows the laptop screen in front of the TV screen with the display mirrored. So both screens should look the same in the picture. But it looks like only the white color is the same, while the rest of the colors are very different. Thanks for your help, Alin. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun May 29 17:47:11 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:21ce] InstallationDate: Installed on 2016-05-06 (22 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 4236BH1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro noprompt persistent quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/05/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 83ET76WW (1.46 ) dmi.board.asset.tag: Not Available dmi.board.name: 4236BH1 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr83ET76WW(1.46):bd07/05/2013:svnLENOVO:pn4236BH1:pvrThinkPadT420:rvnLENOVO:rn4236BH1:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4236BH1 dmi.product.version: ThinkPad T420 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun May 29 17:45:29 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 738 vendor LGD xserver.version: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1586787/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net U
[Touch-packages] [Bug 1701349] Re: Nvidia display is slow
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue when using a currently supported release of Ubuntu then please let us know otherwise this report can be left to expire in approximately 60 days time. ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1701349 Title: Nvidia display is slow Status in xorg package in Ubuntu: Incomplete Bug description: Applications display is slow, mouse movement is delayed and movies cannot be played smoothly but frame by frame. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-56-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 375.66 Mon May 1 15:29:16 PDT 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Jun 29 21:53:50 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Skylake Integrated Graphics [1462:116b] Subsystem: Micro-Star International Co., Ltd. [MSI] GM107M [GeForce GTX 960M] [1462:116b] InstallationDate: Installed on 2017-04-12 (78 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 1770:ff00 Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Micro-Star International Co., Ltd. GS60 6QC ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-56-generic root=UUID=4742493d-f9c1-4072-9d91-f07611aac5da ro nomodeset quiet splash vt.handoff=7 SourcePackage: xorg UnitySupportTest: Error: command ['/usr/lib/nux/unity_support_test', '-p', '-f'] failed with exit code 5: Error: GLX is not available on the system UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16H8IMS.111 dmi.board.asset.tag: Default string dmi.board.name: MS-16H8 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16H8IMS.111:bd11/21/2016:svnMicro-StarInternationalCo.,Ltd.:pnGS606QC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16H8:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring: dmi.product.name: GS60 6QC dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu Jun 29 21:20:46 2017 xserver.configfile: default xserver.errors: [drm] Failed to open DRM device for (null): -22 Screen 0 deleted because of no matching config section. Failed to initialize GLX extension (Compatible NVIDIA X driver not found) xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserv
[Touch-packages] [Bug 1675680] Re: My graphic is not running well anymore
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue when using a currently supported release of Ubuntu then please let us know otherwise this report can be left to expire in approximately 60 days time. ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1675680 Title: My graphic is not running well anymore Status in xorg package in Ubuntu: Incomplete Bug description: After trying to install Sonos i couldn't shut down the usual way anymore so i restarted after deleting successfully Xorg says hardware doesn't use grapic support correctly! Thanks for helping ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Mar 24 09:24:42 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e12] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4 Series Chipset Integrated Graphics Controller [17aa:3047] Subsystem: Lenovo 4 Series Chipset Integrated Graphics Controller [17aa:3047] InstallationDate: Installed on 2017-03-21 (2 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 7628AE3 ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic root=UUID=0f2ed734-4a52-4f76-89cf-87d23eac183e ro recovery nomodeset Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/20/2009 dmi.bios.vendor: LENOVO dmi.bios.version: 5CKT46AUS dmi.board.name: LENOVO dmi.board.vendor: LENOVO dmi.board.version: NONE dmi.chassis.asset.tag: S4AH163 dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: NONE dmi.modalias: dmi:bvnLENOVO:bvr5CKT46AUS:bd03/20/2009:svnLENOVO:pn7628AE3:pvrThinkCentreM58:rvnLENOVO:rnLENOVO:rvrNONE:cvnLENOVO:ct3:cvrNONE: dmi.product.name: 7628AE3 dmi.product.version: ThinkCentre M58 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Mar 24 09:20:40 2017 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1675680/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1702766] Re: Wallch/xorg abberation
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue when using a currently supported release of Ubuntu then please let us know otherwise this report can be left to expire in approximately 60 days time. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1702766 Title: Wallch/xorg abberation Status in Ubuntu: Incomplete Bug description: Ubuntu 16.04 LTS Old Fresh Install Using Wallch set to auto start and pic of the day Ocassionally the display shows pic only as a portion with bottom portion grey-out as shown in attached. Sometime the greyed out portion occupies 80% of the screen always from the bottom up. Restart makes no difference This occurance happens only occasionally, and I've caught a snapshot today Usually wallch displays pic of the day correctly. On boot, I do see some different activity discussing blocks occasionally b/w screen.(related?) no other display aberrations appear in daily use. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 BootLog: [[0;32m OK [0m] Started LSB: Speech Dispatcher. [[0;32m OK [0m] Started LSB: Set the CPU Frequency Scaling governor to "ondemand". [[0;32m OK [0m] Started LSB: automatic crash report generation. CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Jul 6 13:35:33 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8670D] [1002:990c] (prog-if 00 [VGA controller]) Subsystem: Lenovo Richland [Radeon HD 8670D] [17aa:3674] InstallationDate: Installed on 2016-12-02 (216 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 10117 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic root=UUID=073e377f-0d1b-496e-8464-3d1b70ce67ba ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/05/2013 dmi.bios.vendor: LENOVO dmi.bios.version: I7KT31AUS dmi.board.vendor: LENOVO dmi.board.version: 31900058 STD dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvnLENOVO:bvrI7KT31AUS:bd11/05/2013:svnLENOVO:pn10117:pvrLenovoH535:rvnLENOVO:rn:rvr31900058STD:cvnLENOVO:ct3:cvr: dmi.product.name: 10117 dmi.product.version: Lenovo H535 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Thu Jul 6 12:41:37 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.2 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1702766/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1625473] Re: Xorg crashes with segfault
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. Thanks for the feedback Anders. I'm sorry that it took someone over five years in which to acknowledge your comment. I'm closing as "Invalid" as the Xenial release is no longer being maintained. ** Changed in: xorg (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1625473 Title: Xorg crashes with segfault Status in xorg package in Ubuntu: Invalid Bug description: Using Ubuntu 16.04 and a pretty modern workstation. Every once in a while (some times every other day, sometimes three times a day) X crashes and I'm kicked out to the login screen. From Xorg log: [432397.120] (EE) [432397.120] (EE) Backtrace: [432397.120] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x556c99c7b5ce] [432397.120] (EE) 1: /usr/lib/xorg/Xorg (0x556c99ac9000+0x1b6959) [0x556c99c7f959] [432397.120] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7f565086+0x354a0) [0x7f56508954a0] [432397.120] (EE) 3: ?? [0x556c9b83e310] [432397.120] (EE) [432397.120] (EE) Segmentation fault at address 0x556c9b83e310 [432397.121] (EE) Fatal server error: [432397.121] (EE) Caught signal 11 (Segmentation fault). Server aborting [432397.121] (EE) It seems pretty similar to this issue: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1522727 I understand that this is probably not enough information, but please let me know what more info you need and I'll try to get it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1625473/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1970402] Re: Initrd out of memory error after upgrade to 22.04
*** This bug is a duplicate of bug 1842320 *** https://bugs.launchpad.net/bugs/1842320 In case it helps: I just want to add that I had similar issues due to debug symbols present in my kernel modules (15x initrd size). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1970402 Title: Initrd out of memory error after upgrade to 22.04 Status in initramfs-tools package in Ubuntu: Confirmed Status in initramfs-tools source package in Jammy: Confirmed Bug description: After upgrading to 22.04 system is unbootable because of "out of memory" error when loading initial ramdisk. I was able to fix it by editing cat /etc/initramfs-tools/initramfs.conf and changing configuration to: MODULES=dep COMPRESS=xz RUNSIZE=15% Not sure which one helped, but I can test it if needed. System information: Description:Ubuntu 22.04 LTS Release:22.04 initramfs-tools: Installed: 0.140ubuntu13 Candidate: 0.140ubuntu13 Version table: *** 0.140ubuntu13 500 500 http://pl.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://pl.archive.ubuntu.com/ubuntu jammy/main i386 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970402/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1991452] [NEW] Kinetic boots to black screen
Public bug reported: I installed the kinetic beta this morning in VirtualBox VM (6.1.38-dfsg-3). On the first boot after install, it got as far as the Ubuntu logo and then the screen went black and I couldn't do anything. I tried to reboot it a few times to no avail. Eventually, I rebooted it into recovery mode and used the 'repair broken packages' option and that changed around some packages. The system resumed from recovery mode and brought me to the normal desktop. I used it stably for a while and I rebooted it twice in the normal course of what I was doing with it. It booted to the desktop fine both times. However, when I rebooted it a third time, it booted to the black screen again. I rebooted it into recovery mode and ran the 'repair' again. It didn't change any packages, but resuming from recovery booted me into a usable system. I filed this bug from the terminal directly after that reboot. Expected Result: Consistent boot to desktop Actual Result: Inconsistent boot to a black screen; seemingly fixed by entering and exiting recovery mode lsb_release -rd: Description:Ubuntu Kinetic Kudu (development branch) Release:22.10 apt policy xorg: Installed: 1:7.7+23ubuntu2 Candidate: 1:7.7+23ubuntu2 Version table: *** 1:7.7+23ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 1 13:26:51 2022 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2022-10-01 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Beta amd64 (20220927.1) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-15-generic root=UUID=2628bb97-3fa1-41ab-92ca-3d98c5e16424 ro recovery nomodeset dis_ucode_ldr SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.112-3ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1991452 Title: Kinetic boots to black screen Status in xorg package in Ubuntu: New Bug description: I installed the kinetic beta this morning in VirtualBox VM (6.1.38-dfsg-3). On the first boot after install, it got as far as the Ubuntu logo and then the screen went black and I couldn't do anything. I tried to reboot it a few times to no avail. Eventually, I rebooted it into recovery mode and used the 'repair broken packages' option and that changed around some packages. The system resumed from recovery mode and brought me to the normal desktop. I used it stably for a while and I rebooted it twice in the normal course of what I was doing with it. It booted to the desktop fine both times. However, when I rebooted it a third time, it booted to the black screen again. I rebooted it into recovery mode an
[Touch-packages] [Bug 1631528] Re: Blank screen after grub menu
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue when using a currently supported release of Ubuntu then please let us know otherwise this report can be left to expire in approximately 60 days time. ** Changed in: xorg (Ubuntu) Status: New => Incomplete ** Package changed: xorg (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1631528 Title: Blank screen after grub menu Status in Ubuntu: Incomplete Bug description: After a fresh install of Ubuntu Mate 16.04.1 on my laptop I have some problems booting. After the grub menu the screen goes blank and nothing happens after that. I think the system is booting properly apart from the screen not showing anything, I can change the volume using the hardware keys and I can connect with SSH from another machine. I've found two workarounds for this problem. 1) Select recovery mode from the grub meny and then resume normal boot, however, the screen resolution is not set properly. 2) Change my grub config file to boot into text mode. I commented out the line GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" and changed GRUB_CMDLINE_LINUX="" to GRUB_CMDLINE_LINUX=”text" and uncommented the line #GRUB_TERMINAL=console After running sudo update-grub and rebooting the system boots into MATE and the correct screen resolution is set. I've collected dmesg after a "blank screen" boot, let me know if there is anything else I should provide. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: MATE Date: Fri Oct 7 22:41:04 2016 InstallationDate: Installed on 2016-10-06 (1 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1631528/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1623518] Re: problemi accensione pc
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue when using a currently supported release of Ubuntu then please let us know otherwise this report can be left to expire in approximately 60 days time. ** Description changed: problemi scheda radeon + + Google translation: + radeon card problems ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 .tmp.unity_support_test.0: - + ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Sep 14 15:48:44 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: - Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7520G] [1002:9990] (prog-if 00 [VGA controller]) -Subsystem: Hewlett-Packard Company Trinity [Radeon HD 7520G] [103c:184a] - Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] [1002:6840] (rev ff) (prog-if ff) + Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7520G] [1002:9990] (prog-if 00 [VGA controller]) + Subsystem: Hewlett-Packard Company Trinity [Radeon HD 7520G] [103c:184a] + Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] [1002:6840] (rev ff) (prog-if ff) InstallationDate: Installed on 2015-07-20 (422 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic root=UUID=c2b360dd-7125-486f-911b-14f23fa0bc6b ro plymouth:debug=1=1=1=1=1=1=1=1=1=1=1=1=1=1=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.26 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 184A dmi.board.vendor: Hewlett-Packard dmi.board.version: 57.35 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.26:bd02/21/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088B1130591620100:rvnHewlett-Packard:rn184A:rvr57.35:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.version: 088B1130591620100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed Sep 14 15:47:08 2016 xserver.configfile: default xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.3-1ubuntu2.3 xserver.video_driver: radeon ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1623518 Title: problemi accensione pc Status in xorg package in Ubuntu: Incomplete Bug description: problemi scheda radeon Google translation: radeon card problems ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Sep 14 15:48:44 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7520G] [10
[Touch-packages] [Bug 1648890] Re: X Diagnostics
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue when using a currently supported release of Ubuntu then please let us know, giving us full details of the problems that you are experiencing, otherwise this report can be left to expire in approximately 60 days time. ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1648890 Title: X Diagnostics Status in xorg package in Ubuntu: Incomplete Bug description: After running X Diagnostics I ran in to some reported bugs. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Dec 9 22:34:13 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:0212] Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:0212] InstallationDate: Installed on 2016-11-18 (21 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: eMachines eMachines E525 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic root=UUID=d610160c-133b-4da2-b1f5-7fbdfda6271e ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/03/2009 dmi.bios.vendor: eMachines dmi.bios.version: V2.06 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: eMachines E525 dmi.board.vendor: eMachines dmi.board.version: V2.06 dmi.chassis.type: 10 dmi.chassis.vendor: eMachines dmi.chassis.version: V2.06 dmi.modalias: dmi:bvneMachines:bvrV2.06:bd08/03/2009:svneMachines:pneMachinesE525:pvrV2.06:rvneMachines:rneMachinesE525:rvrV2.06:cvneMachines:ct10:cvrV2.06: dmi.product.name: eMachines E525 dmi.product.version: V2.06 dmi.sys.vendor: eMachines version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Dec 9 21:51:50 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4332 vendor AUO xserver.version: 2:1.18.4-0ubuntu0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1648890/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1719223] Re: X authority
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. > I can't log into my root account. Obviously not a problem that still needs addressing. I'm sorry that no- one get back to you. ** Description changed: Não consigo me logar na minha conta root. + + Google translation: + I can't log into my root account. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 .tmp.unity_support_test.0: - + ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Sep 24 21:15:21 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: - Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 02) (prog-if 00 [VGA controller]) -Subsystem: Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:d606] + Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 02) (prog-if 00 [VGA controller]) + Subsystem: Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:d606] InstallationDate: Installed on 2017-01-09 (258 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: - LANGUAGE=pt_BR:pt:en - PATH=(custom, no user) - LANG=pt_BR.UTF-8 - SHELL=/bin/bash + LANGUAGE=pt_BR:pt:en + PATH=(custom, no user) + LANG=pt_BR.UTF-8 + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic root=UUID=3444d65d-fd04-45a7-b7c7-d4aa5810220e ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/28/2007 dmi.bios.vendor: Intel Corp. dmi.bios.version: NL94510J.86A.0017.2007.0828.1137 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: D945GCNL dmi.board.vendor: Intel Corporation dmi.board.version: AAE28768-100 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrNL94510J.86A.0017.2007.0828.1137:bd08/28/2007:svn:pn:pvr:rvnIntelCorporation:rnD945GCNL:rvrAAE28768-100:cvn:ct2:cvr: version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sun Sep 24 13:52:16 2017 xserver.configfile: default xserver.devices: - inputPower Button KEYBOARD, id 6 - inputSleep Button KEYBOARD, id 7 - inputPixArt USB Optical Mouse MOUSE, id 8 - inputHID 0b38:0010KEYBOARD, id 9 - inputHID 0b38:0010KEYBOARD, id 10 + inputPower Button KEYBOARD, id 6 + inputSleep Button KEYBOARD, id 7 + inputPixArt USB Optical Mouse MOUSE, id 8 + inputHID 0b38:0010KEYBOARD, id 9 + inputHID 0b38:0010KEYBOARD, id 10 xserver.errors: - + xserver.logfile: /var/log/Xorg.0.log xserver.outputs: - product id 42786 - vendor AOC + product id 42786 + vendor AOC xserver.version: 2:1.19.3-1ubuntu1~16.04.2 ** Changed in: xorg (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1719223 Title: X authority Status in xorg package in Ubuntu: Invalid Bug description: Não consigo me logar na minha conta root. Google translation: I can't log into my root account. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Sep 24 21:15:21 2017 DistUpgraded: Fresh install DistroCodename: xenial
[Touch-packages] [Bug 1730209] Re: Xorg crashed with SIGABRT in OsAbort()
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. This release of Ubuntu is no longer receiving maintenance updates but we're glad to see that you worked around the problem some time ago. I'm closing this now as this bug report is no longer valid but apologise for no-one getting back to you in response to your question. ** Changed in: xorg (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1730209 Title: Xorg crashed with SIGABRT in OsAbort() Status in xorg package in Ubuntu: Invalid Bug description: Every time I turn login this error appears. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Nov 5 19:41:15 2017 DistUpgraded: 2017-05-24 05:55:43,957 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8)) DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Haswell-ULT Integrated Graphics Controller [1025:0775] InstallationDate: Installed on 2015-02-06 (1002 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Acer Aspire V5-561G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic root=UUID=aeaf2e16-4b71-4c4a-8049-47b66cc8b8b6 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-05-24 (165 days ago) dmi.bios.date: 11/21/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HW dmi.board.vendor: Acer dmi.board.version: V2.13 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.13:bd11/21/2013:svnAcer:pnAspireV5-561G:pvrV2.13:rvnAcer:rnVA50_HW:rvrV2.13:cvnAcer:ct10:cvrChassisVersion: dmi.product.name: Aspire V5-561G dmi.product.version: V2.13 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Nov 5 19:05:00 2017 xserver.configfile: default xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1072 vendor LGD xserver.version: 2:1.18.4-0ubuntu0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1730209/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 396265] Re: Dash Missing after removeal of Evolution/Pilot
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. I'm setting the status of this bug to 'Invalid' as it's not seen any activity since the report was raised and does not make any reference to the release or flavour of Ubuntu that was being used. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s). However, please note that 'dash' is a POSIX compliant shell similar to bash but the problem seems to have affected an unknown desktop environment. ** Changed in: dash (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dash in Ubuntu. https://bugs.launchpad.net/bugs/396265 Title: Dash Missing after removeal of Evolution/Pilot Status in dash package in Ubuntu: Invalid Bug description: Binary package hint: dash Evolution would not uninstall via Add/Remove Used Synaptics then lost menu bar and desktop (had to do total reinstall) Found a post to remove evolution/pilot by sudo apt-uninstall evolution pilot (or something close) Reboot, desktop ok. Tried Computer Janitor - get DASH MISSING Used synaptics - shows Dash installed and grayed out reinstall option. ==> Lets make Evolution, Pilot, Floppy Drive and any other "accessory" easily and safely removable. Now what should I do??? (third reinstall of whole system?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dash/+bug/396265/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1582672] Re: Typing q in dash will close it
dash, the package that this issue was reported against, is a POSIX- compliant shell similar to bash. Presumably this issue was reported against 'dash' in error. 'unity' would probably have been the correct package. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. I'm closing this report as 'Invalid'. If the reported problem is still an issue using a currently supported release of Ubuntu then please open a new bug report against the Unity package. ** Changed in: dash (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dash in Ubuntu. https://bugs.launchpad.net/bugs/1582672 Title: Typing q in dash will close it Status in dash package in Ubuntu: Invalid Bug description: I wanted to search for SQL-Workbench. The dash closed as soon as I typed the letter q. WTH? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: dash 0.5.8-2.1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue May 17 13:45:39 2016 InstallationDate: Installed on 2016-04-25 (21 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: dash UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dash/+bug/1582672/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1967648] Re: lubuntu jammy - `ubuntu-bug lxqt-config` isn't opening firefox
** Changed in: apport (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1967648 Title: lubuntu jammy - `ubuntu-bug lxqt-config` isn't opening firefox Status in apport package in Ubuntu: Confirmed Bug description: /usr/bin/xdg-open: 882: firefox: not found /usr/bin/xdg-open: 882: firefox: not found xdg-open: no method available for opening 'https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+filebug/9f12535a-b2f0-11ec-b9ed-40a8f0305cb4?' Lubuntu jammy install test on dell optiplex 780 I adjusted displays as mouse-movements were annoying me, noticed an issue thus filed a bug report using `ubuntu-bug lxqt-config` ** expected output on executing `ubuntu-but lxqt-config` I expected firefox to start ** actual output --- lubuntu@lubuntu:~$ ubuntu-bug lxqt-config *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. ... *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (19.6 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): s *** Uploading problem information The collected information is being sent to the bug tracking system. This might take a few minutes. 98% *** To continue, you must visit the following URL: https://bugs.launchpad.net/ubuntu/+source/lxqt- config/+filebug/9f12535a-b2f0-11ec-b9ed-40a8f0305cb4? You can launch a browser now, or copy this URL into a browser on another computer. Choices: 1: Launch a browser now C: Cancel Please choose (1/C): 1 /usr/bin/xdg-open: 882: firefox: not found /usr/bin/xdg-open: 882: firefox: not found xdg-open: no method available for opening 'https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+filebug/9f12535a-b2f0-11ec-b9ed-40a8f0305cb4?' --- ie. `firefox` doesn't start as it's now a snap package first attempt to file `ubuntu-bug apport` ended up with --- *** To continue, you must visit the following URL: https://bugs.launchpad.net/ubuntu/+source/lxqt- config/+filebug/9f12535a-b2f0-11ec-b9ed-40a8f0305cb4? You can launch a browser now, or copy this URL into a browser on another computer. Choices: 1: Launch a browser now C: Cancel Please choose (1/C): 1 /usr/bin/xdg-open: 882: firefox: not found /usr/bin/xdg-open: 882: firefox: not found xdg-open: no method available for opening 'https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+filebug/9f12535a-b2f0-11ec-b9ed-40a8f0305cb4?' lubuntu@lubuntu:~$ --- ** other notes - I don't know if this only impacts lubuntu, or others too - I've not (yet) looked for other/existing bugs ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apport 2.20.11-0ubuntu80 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: LXQt Date: Sun Apr 3 12:09:05 2022 LiveMediaBuild: Lubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220402) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1967648/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1989959] Re: Incorrect ESM coverage information
Why do you count packages in the "universe"? I thought that the Ubuntu security team does not support them. https://ubuntu.com/16-04 says nothing about ESM coverage of packages in the "universe", and this does not imply such coverage. Also see comments in sources.list (APT) for the "universe": ## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu ## team. Also, please note that software in universe WILL NOT receive any ## review or updates from the Ubuntu security team. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1989959 Title: Incorrect ESM coverage information Status in software-properties package in Ubuntu: Triaged Bug description: Software Properties says that Extended Security Maintenance provides security updates for over 3 Ubuntu packages, see lines 1269 and 1346 in data/gtkbuilder/main.ui. According to https://ubuntu.com/16-04, Canonical provides extended security maintenance for binary packages that reside in the "main" Ubuntu repository, which contains about 7000 architecture-specific packages depending on the Ubuntu release. Moreover, ESM is only provided for a part of packages, not for all packages in the "main" repository. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1989959/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1991436] [NEW] "invalid argument" error from logger command when passing messages via STDIN
Public bug reported: When invoking the `logger` command on Ubuntu Jammy (bsdutils 2.37.2) with explicit PID and passing messages via STDIN ``` echo "some message" | logger -p local0.info --id="$$" ``` the command produces the following error instead of sending the message to syslog: > logger: send message failed: Invalid argument The error does not appear when the message is passed as an argument: ``` logger -p local0.info --id="$$" "some message" # this works! ``` When using process substitution the error only appears for the first log message: ``` exec > >(logger -p local0.info --id="$$") echo "first message" # throws error, message not logged echo "second message" # no error, message logged correctly ``` The issue does not exist in older versions (e.g. Ubuntu Xenial, bsdutils 2.27.1). Workaround: Omit `--id` and include the PID in a tag. ``` echo "some message" | logger -p local0.info -t "foo[$$]" ``` Expected Behavior - All messages passed via STDIN should be sent to syslog without throwing an error. OS Release -- Description:Ubuntu 22.04 LTS Release:22.04 Package Version --- bsdutils: Installed: 2.37.2-4ubuntu3 Candidate: 2.37.2-4ubuntu3 ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Tags: jammy ** Description changed: When invoking the `logger` command on Ubuntu Jammy (bsdutils 2.37.2) with explicit PID and passing messages via STDIN ``` echo "some message" | logger -p local0.info --id="$$" ``` - the command produces the following error: + the command produces the following error instead of sending the message + to syslog: > logger: send message failed: Invalid argument The error does not appear when the message is passed as an argument: ``` logger -p local0.info --id="$$" "some message" # this works! ``` When using process substitution the error only appears for the first log message: ``` exec > >(logger -p local0.info --id="$$") echo "first message" # throws error, message not logged echo "second message" # no error, message logged correctly - ``` + ``` The issue does not exist in older versions (e.g. Ubuntu Xenial, bsdutils 2.27.1). Workaround: Omit `--id` and include the PID in a tag. ``` echo "some message" | logger -p local0.info -t "foo[$$]" ``` Expected Behavior - All messages passed via STDIN should be sent to syslog without throwing an error. OS Release -- Description: Ubuntu 22.04 LTS Release: 22.04 Package Version --- bsdutils: - Installed: 2.37.2-4ubuntu3 - Candidate: 2.37.2-4ubuntu3 + Installed: 2.37.2-4ubuntu3 + Candidate: 2.37.2-4ubuntu3 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1991436 Title: "invalid argument" error from logger command when passing messages via STDIN Status in util-linux package in Ubuntu: New Bug description: When invoking the `logger` command on Ubuntu Jammy (bsdutils 2.37.2) with explicit PID and passing messages via STDIN ``` echo "some message" | logger -p local0.info --id="$$" ``` the command produces the following error instead of sending the message to syslog: > logger: send message failed: Invalid argument The error does not appear when the message is passed as an argument: ``` logger -p local0.info --id="$$" "some message" # this works! ``` When using process substitution the error only appears for the first log message: ``` exec > >(logger -p local0.info --id="$$") echo "first message" # throws error, message not logged echo "second message" # no error, message logged correctly ``` The issue does not exist in older versions (e.g. Ubuntu Xenial, bsdutils 2.27.1). Workaround: Omit `--id` and include the PID in a tag. ``` echo "some message" | logger -p local0.info -t "foo[$$]" ``` Expected Behavior - All messages passed via STDIN should be sent to syslog without throwing an error. OS Release -- Description: Ubuntu 22.04 LTS Release: 22.04 Package Version --- bsdutils: Installed: 2.37.2-4ubuntu3 Candidate: 2.37.2-4ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1991436/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp