[Touch-packages] [Bug 1993931] [NEW] package linux-image-5.15.0-52-generic 5.15.0-52.58~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: Ubuntu takes 2 minutes longer to boot up because of the bug. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-52-generic 5.15.0-52.58~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-48.54~20.04.1-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Oct 22 20:11:59 2022 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2021-08-26 (422 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: initramfs-tools Title: package linux-image-5.15.0-52-generic 5.15.0-52.58~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- 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/1993931 Title: package linux-image-5.15.0-52-generic 5.15.0-52.58~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: Ubuntu takes 2 minutes longer to boot up because of the bug. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-52-generic 5.15.0-52.58~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-48.54~20.04.1-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Oct 22 20:11:59 2022 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2021-08-26 (422 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: initramfs-tools Title: package linux-image-5.15.0-52-generic 5.15.0-52.58~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1993931/+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 1982218] Re: wait-online does not correctly identify managed links
[Expired for systemd (Ubuntu) because there has been no activity for 60 days.] ** Changed in: systemd (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1982218 Title: wait-online does not correctly identify managed links Status in systemd package in Ubuntu: Expired Bug description: Ubuntu's packaging of systemd-networkd-wait-online includes a patch (UBUNTU-wait-online-exit-if-no-links-are-managed) intended to exit if none of the present links are managed by systemd-networkd. However, the patch fails to identify links in the "configuring" state, which implies they are managed, but not yet fully online. This undermines the purpose of systemd-networkd-wait-online with the --any option, since at the time the systemd-networkd-wait-online service is started, managed links are _likely_ in a configuring, but-not-yet-configured state. Please see the attached patch. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218/+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 1993928] [NEW] Switching to new input method does nothing
Public bug reported: I have ibus-m17n installed, but switching to a different input method does nothing. STR: 1. Make sure my 2nd input method (in my case, "Sanskrit (sa-IAST (m17n))" appears under "Settings-->Keyboard-->Input sources." 2. Use alt-space to switch to my second input method. 3. Notice on the top panel that the indicator shows that the input method has changed. 4. Attempt to key in some special characters (using Gedit, LibreOffice, etc.). Expected result: The special characters will appear. Actual result: The keyboard behaves as if the input method were my usual "English (US)." No such problem with 22.04. Removing and re-adding "Sanskrit (sa-IAST (m17n))" in Settings doesn't solve the issue. Hardware: IBM ThinkPad Carbon X-1, 5th generation. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: ibus 1.5.27-2 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Oct 23 08:44:46 2022 InstallationDate: Installed on 2017-12-08 (1779 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ibus UpgradeStatus: Upgraded to kinetic on 2022-10-21 (1 days ago) ** Affects: ibus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1993928 Title: Switching to new input method does nothing Status in ibus package in Ubuntu: New Bug description: I have ibus-m17n installed, but switching to a different input method does nothing. STR: 1. Make sure my 2nd input method (in my case, "Sanskrit (sa-IAST (m17n))" appears under "Settings-->Keyboard-->Input sources." 2. Use alt-space to switch to my second input method. 3. Notice on the top panel that the indicator shows that the input method has changed. 4. Attempt to key in some special characters (using Gedit, LibreOffice, etc.). Expected result: The special characters will appear. Actual result: The keyboard behaves as if the input method were my usual "English (US)." No such problem with 22.04. Removing and re-adding "Sanskrit (sa-IAST (m17n))" in Settings doesn't solve the issue. Hardware: IBM ThinkPad Carbon X-1, 5th generation. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: ibus 1.5.27-2 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Oct 23 08:44:46 2022 InstallationDate: Installed on 2017-12-08 (1779 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ibus UpgradeStatus: Upgraded to kinetic on 2022-10-21 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1993928/+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
Re: [Touch-packages] [Bug 1951491] Re: Can't run snaps: .slice/session-1.scope is not a snap cgroup
@Akkana. My suspicion from digging around is that the problem happens during login, not session start. Certain steps in the sessiond login process need to be invoked for the session bus to work correctly. You will see from other reports that this issue is with the dbus session bus not being set up correctly. The report about cgroups is a consequence of that. The workarounds prove this. When I looked into the session start up process, the problem occurred before session start. systemd has documentation on what the login needs to do, and I don't think this is being followed when this problem occurs. I therefore think this is not about the sessions, but the login process. It's why I wondered if you were using a modern login manager (such as gdm3) because gdm3 is compliant with systemd's requirements. You could dp echo $DBUS_SESSION_BUS_ADDRESS from your console before you do startx, and see if it is valid. I'm going to guess that it is not. When I spent some time looking at this a few months ago, I had the impression that this variable needs to be set correctly before the gui session starts. On Sun, 23 Oct 2022 at 07:40, Akkana Peck <1951...@bugs.launchpad.net> wrote: > Tim Richardson: I'm not using a login manager, I'm logging in on the > console then running startx. > > This is clearly not an openbox-specific bug since people have seen it in > many different environments, and besides, it only happens on Ubuntu with > Ubuntu snaps. The problem seems to be that snap has started to require > [some unknown system service or configuration] that it didn't need > before, which some desktop environments start and others don't. If we > knew what it was looking for, then people who need to run snaps could > make sure it was configured in their environments. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1951491 > > Title: > Can't run snaps: .slice/session-1.scope is not a snap cgroup > > To manage notifications about this bug go to: > https://bugs.launchpad.net/x2go/+bug/1951491/+subscriptions > > -- Tim Richardson -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1951491 Title: Can't run snaps: .slice/session-1.scope is not a snap cgroup Status in X2Go: New Status in snapd package in Ubuntu: Invalid Status in systemd package in Ubuntu: Incomplete Status in x2goserver package in Ubuntu: Confirmed Status in snapd package in Debian: New Bug description: I just upgraded from hirsute to impish using do-release-upgrade. On the upgraded system, I can't run either firefox or chromium (both of which worked fine under hirsute). Both fail with: /user.slice/user-NNN.slice/session-1.scope is not a snap cgroup where NNN is my uid With firefox, I was able to fix the problem with: snap remove --purge firefox apt purge firefox apt install firefox Now firefox works. But I tried the same thing substituting chromium- browser for firefox, and it didn't help: chromium fails with the same error message. I guess there must be something left over from the hirsute version of snapd that isn't getting noticed or cleared by the impish version? Someone suggested this might be related to bug 1850667, but that bug is marked fixed as of a couple months ago, and I just did this upgrade today. Also, it doesn't mention the error message I'm seeing. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: snapd 2.53+21.10ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Nov 18 18:12:45 2021 InstallationDate: Installed on 2020-04-29 (568 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: snapd UpgradeStatus: Upgraded to impish on 2021-11-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/x2go/+bug/1951491/+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 1993870] Re: WiFi setting has no visible networks
** Package changed: ubuntu => network-manager (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1993870 Title: WiFi setting has no visible networks Status in network-manager package in Ubuntu: New Bug description: With ubuntu 22.10, I can not see any AP in WiFi setting. It's ok on previous versions. The driver is okay since I can scan with iwlist tool. Below are more details. $ sudo lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.10 Release: 22.10 Codename: kinetic $ ifconfig enx5e80011fa4e9: flags=4163 mtu 1500 inet 192.168.42.116 netmask 255.255.255.0 broadcast 192.168.42.255 inet6 fe80::cd60:eccc:f8d7:21e6 prefixlen 64 scopeid 0x20 ether 5e:80:01:1f:a4:e9 txqueuelen 1000 (Ethernet) RX packets 432320 bytes 621981996 (621.9 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 186680 bytes 22769110 (22.7 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73 mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1000 (Local Loopback) RX packets 11354 bytes 24889535 (24.8 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 11354 bytes 24889535 (24.8 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 wlp0s20f3: flags=4099 mtu 1500 ether 18:1d:ea:ed:34:16 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 $ sudo iwlist wlp0s20f3 scan wlp0s20f3 Scan completed : Cell 01 - Address: D0:79:80:DA:4F:F3 Channel:1 Frequency:2.412 GHz (Channel 1) Quality=29/70 Signal level=-81 dBm Encryption key:on ESSID:"CMCC-7S6H" Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s 24 Mb/s; 36 Mb/s; 54 Mb/s Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s Mode:Master Extra:tsf=00e793b8a899 Extra: Last beacon: 2164ms ago IE: Unknown: 0009434D43432D37533648 IE: Unknown: 010882848B962430486C IE: Unknown: 030101 IE: Unknown: 23021100 IE: Unknown: 2A0104 IE: Unknown: 32040C121860 IE: IEEE 802.11i/WPA2 Version 1 Group Cipher : CCMP Pairwise Ciphers (1) : CCMP Authentication Suites (1) : PSK IE: Unknown: 0B0539 IE: Unknown: 7F0804000840 IE: Unknown: DD7E0050F204104A0001101044000102103B000103104700105D2DBCBB9D644948047E083B1A419A72102100094669626572686F6D65102300094669626572686F6D651024000631323334353610420004313233341054000800060050F20400011011000B4669626572686F6D6541501008000220081049000600372A000120 IE: Unknown: DD0A001018020C01 IE: WPA Version 1 Group Cipher : CCMP Pairwise Ciphers (1) : CCMP Authentication Suites (1) : PSK IE: Unknown: DD180050F20201018C0003A227A442435E0062322F00 Cell 02 - Address: FC:DD:65:2B:6B:52 $ sudo dmesg | grep iwl [2.816274] iwlwifi :00:14.3: WRT: Overriding region id 0 [2.816285] iwlwifi :00:14.3: WRT: Overriding region id 1 [2.816289] iwlwifi :00:14.3: WRT: Overriding region id 2 [2.816293] iwlwifi :00:14.3: WRT: Overriding region id 3 [2.816297] iwlwifi :00:14.3: WRT: Overriding region id 4 [2.816300] iwlwifi :00:14.3: WRT: Overriding region id 6 [2.816304] iwlwifi :00:14.3: WRT: Overriding region id 8 [2.816307] iwlwifi :00:14.3: WRT: Overriding region id 9 [2.816311] iwlwifi :00:14.3: WRT: Overriding region id 10 [2.816314] iwlwifi :00:14.3: WRT: Overriding region id 11 [2.816318] iwlwifi :00:14.3: WRT: Overriding region id 15 [2.816322] iwlwifi :00:14.3: WRT: Overriding region id 16 [2.816326] iwlwifi :00:14.3: WRT: Overriding region id 18 [2.816330] iwlwifi :00:14.3: WRT: Overriding region id 19 [2.816333] iwlwifi :00:14.3: WRT: Overriding region id 20 [2.816360] iwlwifi :00:14.3: WRT: Overriding region id 21 [
[Touch-packages] [Bug 1993870] [NEW] WiFi setting has no visible networks
You have been subscribed to a public bug: With ubuntu 22.10, I can not see any AP in WiFi setting. It's ok on previous versions. The driver is okay since I can scan with iwlist tool. Below are more details. $ sudo lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.10 Release:22.10 Codename: kinetic $ ifconfig enx5e80011fa4e9: flags=4163 mtu 1500 inet 192.168.42.116 netmask 255.255.255.0 broadcast 192.168.42.255 inet6 fe80::cd60:eccc:f8d7:21e6 prefixlen 64 scopeid 0x20 ether 5e:80:01:1f:a4:e9 txqueuelen 1000 (Ethernet) RX packets 432320 bytes 621981996 (621.9 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 186680 bytes 22769110 (22.7 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73 mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1000 (Local Loopback) RX packets 11354 bytes 24889535 (24.8 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 11354 bytes 24889535 (24.8 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 wlp0s20f3: flags=4099 mtu 1500 ether 18:1d:ea:ed:34:16 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 $ sudo iwlist wlp0s20f3 scan wlp0s20f3 Scan completed : Cell 01 - Address: D0:79:80:DA:4F:F3 Channel:1 Frequency:2.412 GHz (Channel 1) Quality=29/70 Signal level=-81 dBm Encryption key:on ESSID:"CMCC-7S6H" Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s 24 Mb/s; 36 Mb/s; 54 Mb/s Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s Mode:Master Extra:tsf=00e793b8a899 Extra: Last beacon: 2164ms ago IE: Unknown: 0009434D43432D37533648 IE: Unknown: 010882848B962430486C IE: Unknown: 030101 IE: Unknown: 23021100 IE: Unknown: 2A0104 IE: Unknown: 32040C121860 IE: IEEE 802.11i/WPA2 Version 1 Group Cipher : CCMP Pairwise Ciphers (1) : CCMP Authentication Suites (1) : PSK IE: Unknown: 0B0539 IE: Unknown: 7F0804000840 IE: Unknown: DD7E0050F204104A0001101044000102103B000103104700105D2DBCBB9D644948047E083B1A419A72102100094669626572686F6D65102300094669626572686F6D651024000631323334353610420004313233341054000800060050F20400011011000B4669626572686F6D6541501008000220081049000600372A000120 IE: Unknown: DD0A001018020C01 IE: WPA Version 1 Group Cipher : CCMP Pairwise Ciphers (1) : CCMP Authentication Suites (1) : PSK IE: Unknown: DD180050F20201018C0003A227A442435E0062322F00 Cell 02 - Address: FC:DD:65:2B:6B:52 $ sudo dmesg | grep iwl [2.816274] iwlwifi :00:14.3: WRT: Overriding region id 0 [2.816285] iwlwifi :00:14.3: WRT: Overriding region id 1 [2.816289] iwlwifi :00:14.3: WRT: Overriding region id 2 [2.816293] iwlwifi :00:14.3: WRT: Overriding region id 3 [2.816297] iwlwifi :00:14.3: WRT: Overriding region id 4 [2.816300] iwlwifi :00:14.3: WRT: Overriding region id 6 [2.816304] iwlwifi :00:14.3: WRT: Overriding region id 8 [2.816307] iwlwifi :00:14.3: WRT: Overriding region id 9 [2.816311] iwlwifi :00:14.3: WRT: Overriding region id 10 [2.816314] iwlwifi :00:14.3: WRT: Overriding region id 11 [2.816318] iwlwifi :00:14.3: WRT: Overriding region id 15 [2.816322] iwlwifi :00:14.3: WRT: Overriding region id 16 [2.816326] iwlwifi :00:14.3: WRT: Overriding region id 18 [2.816330] iwlwifi :00:14.3: WRT: Overriding region id 19 [2.816333] iwlwifi :00:14.3: WRT: Overriding region id 20 [2.816360] iwlwifi :00:14.3: WRT: Overriding region id 21 [2.816363] iwlwifi :00:14.3: WRT: Overriding region id 28 [2.818423] iwlwifi :00:14.3: loaded firmware version 46.9d0122c0.0 9000-pu-b0-jf-b0-46.ucode op_mode iwlmvm [3.451691] iwlwifi :00:14.3: Detected Intel(R) Wireless-AC 9560 160MHz, REV=0x312 [3.514636] iwlwifi :00:14.3: base HW address: 18:1d:ea:ed:34:16, OTP minor version: 0x4 [3.584372] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs' [3.594287] iwlwifi :00:14.3 wlp0s20f3:
[Touch-packages] [Bug 1993920] [NEW] Some windows overflow to other monitors whenever they're near to border and wider than main screen
Public bug reported: After upgrading to Ubuntu 22.10, some applications (for example, VSCode and MySQL Workbench) are presenting weird behavior: if I move it to the secondary monitor and maximize the window, it gets mirrored in the main monitor. I've made some tests and realized that this issue occurs if I place the application window near to the divisor between the two monitors and this window's width is greater than the main monitor's one. Here is a link to a video that shows this issue: https://youtu.be/FmYSgpwS6Bk ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 22 18:19:27 2022 DistUpgraded: 2022-10-20 20:40:37,319 DEBUG icon theme changed, re-reading DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.15.0-52-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Comet Lake UHD Graphics [8086:9bca] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Comet Lake UHD Graphics [144d:c834] InstallationDate: Installed on 2022-10-15 (7 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: SAMSUNG ELECTRONICS CO., LTD. 550XCJ/550XCR ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-21-generic root=UUID=46adeab8-b7f5-472d-b479-38b045a695ff ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2022-10-20 (1 days ago) dmi.bios.date: 02/23/2022 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P12RFH.054.220223.HC dmi.board.asset.tag: No Asset Tag dmi.board.name: NP550XCJ-KF1BR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGLA664A0C-C01-G002-S0001+10.0.19041 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP12RFH.054.220223.HC:bd02/23/2022:br5.16:svnSAMSUNGELECTRONICSCO.,LTD.:pn550XCJ/550XCR:pvrP12RFH:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP550XCJ-KF1BR:rvrSGLA664A0C-C01-G002-S0001+10.0.19041:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-A5A5-A5A5-A5A5-PRFH: dmi.product.family: Notebook 5 Series dmi.product.name: 550XCJ/550XCR dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PRFH dmi.product.version: P12RFH dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-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 third-party-packages ubuntu wayland-session -- 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/1993920 Title: Some windows overflow to other monitors whenever they're near to border and wider than main screen Status in xorg package in Ubuntu: New Bug description: After upgrading to Ubuntu 22.10, some applications (for example, VSCode and MySQL Workbench) are presenting weird behavior: if I move it to the secondary monitor and maximize the window, it gets mirrored in the main monitor. I've made some tests and realized that this issue occurs if I place the application window near to the divisor between the two monitors and this window's width is greater than the main monitor's one. Here is a link to a video that shows this issue: https://youtu.be/FmYSgpwS6Bk ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 22 18:19:27 2022 DistUpgraded: 2022-10-20 20:40:37,319 DEBUG icon theme changed, re-reading DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.15.0-52-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-21-generic, x86_64: installed
[Touch-packages] [Bug 1951491] Re: Can't run snaps: .slice/session-1.scope is not a snap cgroup
Tim Richardson: I'm not using a login manager, I'm logging in on the console then running startx. This is clearly not an openbox-specific bug since people have seen it in many different environments, and besides, it only happens on Ubuntu with Ubuntu snaps. The problem seems to be that snap has started to require [some unknown system service or configuration] that it didn't need before, which some desktop environments start and others don't. If we knew what it was looking for, then people who need to run snaps could make sure it was configured in their environments. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1951491 Title: Can't run snaps: .slice/session-1.scope is not a snap cgroup Status in X2Go: New Status in snapd package in Ubuntu: Invalid Status in systemd package in Ubuntu: Incomplete Status in x2goserver package in Ubuntu: Confirmed Status in snapd package in Debian: New Bug description: I just upgraded from hirsute to impish using do-release-upgrade. On the upgraded system, I can't run either firefox or chromium (both of which worked fine under hirsute). Both fail with: /user.slice/user-NNN.slice/session-1.scope is not a snap cgroup where NNN is my uid With firefox, I was able to fix the problem with: snap remove --purge firefox apt purge firefox apt install firefox Now firefox works. But I tried the same thing substituting chromium- browser for firefox, and it didn't help: chromium fails with the same error message. I guess there must be something left over from the hirsute version of snapd that isn't getting noticed or cleared by the impish version? Someone suggested this might be related to bug 1850667, but that bug is marked fixed as of a couple months ago, and I just did this upgrade today. Also, it doesn't mention the error message I'm seeing. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: snapd 2.53+21.10ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Nov 18 18:12:45 2021 InstallationDate: Installed on 2020-04-29 (568 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: snapd UpgradeStatus: Upgraded to impish on 2021-11-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/x2go/+bug/1951491/+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
Re: [Touch-packages] [Bug 1981103] Re: System with DNS server in /etc/network/interfaces has bogus systemd-resolved config after upgrade to 22.04
*This* bug has the full information in the first post including all
needed to fix the problem. Actually there are more problems in the
script regarding syntax, so more issues exist, leading to unwanted
behavior.
Uwe
Am 22. Oktober 2022 22:05:59 MESZ schrieb David Kowis
<1981...@bugs.launchpad.net>:
>https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1910273
>
>This one seems to have the full patch repair in the bug description.
>None of the other bugs I've found relating to this have the full
>solution.
>
>--
>You received this bug notification because you are subscribed to the bug
>report.
>https://bugs.launchpad.net/bugs/1981103
>
>Title:
> System with DNS server in /etc/network/interfaces has bogus systemd-
> resolved config after upgrade to 22.04
>
>Status in ifupdown package in Ubuntu:
> Triaged
>
>Bug description:
> Description:Ubuntu 22.04 LTS
> Release:22.04
>
> ifupdown:
>Installed: 0.8.36+nmu1ubuntu3
>Candidate: 0.8.36+nmu1ubuntu3
>Version table:
> *** 0.8.36+nmu1ubuntu3 500
> 500 http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
> 100 /var/lib/dpkg/status
>
> After upgrading a server with classic ifupdown configuration after
> reboot the machine had no valid dns servers anymore.
>
> The problem is that the state file created by ifupdown using
> /etc/network/if-up.d/resolved looks like this:
>
> root@pangaea-pm:~# cat /run/network/ifupdown-inet-ens13
> "DNS"="134.102.20.20 134.102.200.14"
> "DOMAINS"="marum.de"
>
> The script later sources this file and causes the following errors,
> easy to see when you execute this:
>
> root@pangaea-pm:~# ifdown ens13; ifup ens13
> /etc/network/if-down.d/resolved: 12: mystatedir: not found
> /etc/network/if-up.d/resolved: 12: mystatedir: not found
> /etc/network/if-up.d/resolved: 71: DNS: not found
> /etc/network/if-up.d/resolved: 1: /run/network/ifupdown-inet-ens13:
> DNS=134.102.20.20 134.102.200.14: not found
> /etc/network/if-up.d/resolved: 2: /run/network/ifupdown-inet-ens13:
> DOMAINS=marum.de: not found
> Failed to parse DNS server address: DNS
> Failed to set DNS configuration: Invalid argument
>
> This happened to me on three different servers, so this is a serious
> bug and should be fixed before 22.04 upgrades are allowed for
> everybody. Most servers provided by data centers like Hetzner
> (Germany) are configure like that. After a do-release-upgrade you have
> no working DNS anymore, unless you disable systemd-resolved. I don't
> want to use netplan, so changing to this is no option.
>
> The fix is easy - remove the quotes in the script on the left side
> "$DNS" => $DNS; same for DOMAINS:
>
> if [ -n "$NEW_DNS" ]; then
> cat <"$mystatedir/ifupdown-${ADDRFAM}-$interface"
> $DNS="$NEW_DNS"
> EOF
> if [ -n "$NEW_DOMAINS" ]; then
> cat <>"$mystatedir/ifupdown-${ADDRFAM}-$interface"
> $DOMAINS="$NEW_DOMAINS"
> EOF
> fi
> fi
>
>To manage notifications about this bug go to:
>https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1981103/+subscriptions
>
--
Uwe Schindler
Achterdiek 19, 28357 Bremen
https://www.thetaphi.de
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1981103
Title:
System with DNS server in /etc/network/interfaces has bogus systemd-
resolved config after upgrade to 22.04
Status in ifupdown package in Ubuntu:
Triaged
Bug description:
Description:Ubuntu 22.04 LTS
Release:22.04
ifupdown:
Installed: 0.8.36+nmu1ubuntu3
Candidate: 0.8.36+nmu1ubuntu3
Version table:
*** 0.8.36+nmu1ubuntu3 500
500 http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
100 /var/lib/dpkg/status
After upgrading a server with classic ifupdown configuration after
reboot the machine had no valid dns servers anymore.
The problem is that the state file created by ifupdown using
/etc/network/if-up.d/resolved looks like this:
root@pangaea-pm:~# cat /run/network/ifupdown-inet-ens13
"DNS"="134.102.20.20 134.102.200.14"
"DOMAINS"="marum.de"
The script later sources this file and causes the following errors,
easy to see when you execute this:
root@pangaea-pm:~# ifdown ens13; ifup ens13
/etc/network/if-down.d/resolved: 12: mystatedir: not found
/etc/network/if-up.d/resolved: 12: mystatedir: not found
/etc/network/if-up.d/resolved: 71: DNS: not found
/etc/network/if-up.d/resolved: 1: /run/network/ifupdown-inet-ens13:
DNS=134.102.20.20 134.102.200.14: not found
/etc/network/if-up.d/resolved: 2: /run/network/ifupdown-inet-ens13:
DOMAINS=marum.de: not found
Failed to parse DNS server address: DNS
Failed to set DNS configuration: Invalid argument
This happened to me on three different servers, so this is a serious
bug and should be fixed before 22.04 upgrades are allowed for
[Touch-packages] [Bug 1907878] Re: wrong var declaration in if-up.d/resolved (nm-dispatcher[54417]: /etc/network/if-up.d/resolved: 12: mystatedir: not found)
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1910273 This one seems to have the full patch repair in the bug description. None of the other bugs I've found relating to this have the full solution. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1907878 Title: wrong var declaration in if-up.d/resolved (nm-dispatcher[54417]: /etc/network/if-up.d/resolved: 12: mystatedir: not found) Status in ifupdown package in Ubuntu: Fix Released Status in ifupdown source package in Jammy: Triaged Bug description: Syslog error: nm-dispatcher[...]: /etc/network/if-up.d/resolved: 12: mystatedir: not found I think it's because of this line: if systemctl is-enabled systemd-resolved > /dev/null 2>&1; then mystatedir statedir ifindex interface <- this is interpreted as a 'mystatedir' command and fails interface=$IFACE if [ ! "$interface" ]; then Perhaps the intention was to 'export mystatedir statedir ...' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1907878/+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 1981103] Re: System with DNS server in /etc/network/interfaces has bogus systemd-resolved config after upgrade to 22.04
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1910273
This one seems to have the full patch repair in the bug description.
None of the other bugs I've found relating to this have the full
solution.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1981103
Title:
System with DNS server in /etc/network/interfaces has bogus systemd-
resolved config after upgrade to 22.04
Status in ifupdown package in Ubuntu:
Triaged
Bug description:
Description:Ubuntu 22.04 LTS
Release:22.04
ifupdown:
Installed: 0.8.36+nmu1ubuntu3
Candidate: 0.8.36+nmu1ubuntu3
Version table:
*** 0.8.36+nmu1ubuntu3 500
500 http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
100 /var/lib/dpkg/status
After upgrading a server with classic ifupdown configuration after
reboot the machine had no valid dns servers anymore.
The problem is that the state file created by ifupdown using
/etc/network/if-up.d/resolved looks like this:
root@pangaea-pm:~# cat /run/network/ifupdown-inet-ens13
"DNS"="134.102.20.20 134.102.200.14"
"DOMAINS"="marum.de"
The script later sources this file and causes the following errors,
easy to see when you execute this:
root@pangaea-pm:~# ifdown ens13; ifup ens13
/etc/network/if-down.d/resolved: 12: mystatedir: not found
/etc/network/if-up.d/resolved: 12: mystatedir: not found
/etc/network/if-up.d/resolved: 71: DNS: not found
/etc/network/if-up.d/resolved: 1: /run/network/ifupdown-inet-ens13:
DNS=134.102.20.20 134.102.200.14: not found
/etc/network/if-up.d/resolved: 2: /run/network/ifupdown-inet-ens13:
DOMAINS=marum.de: not found
Failed to parse DNS server address: DNS
Failed to set DNS configuration: Invalid argument
This happened to me on three different servers, so this is a serious
bug and should be fixed before 22.04 upgrades are allowed for
everybody. Most servers provided by data centers like Hetzner
(Germany) are configure like that. After a do-release-upgrade you have
no working DNS anymore, unless you disable systemd-resolved. I don't
want to use netplan, so changing to this is no option.
The fix is easy - remove the quotes in the script on the left side
"$DNS" => $DNS; same for DOMAINS:
if [ -n "$NEW_DNS" ]; then
cat <"$mystatedir/ifupdown-${ADDRFAM}-$interface"
$DNS="$NEW_DNS"
EOF
if [ -n "$NEW_DOMAINS" ]; then
cat <>"$mystatedir/ifupdown-${ADDRFAM}-$interface"
$DOMAINS="$NEW_DOMAINS"
EOF
fi
fi
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1981103/+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 1993867] Re: Telegram sometimes start endless use 100% CPU
Added also libvpx to related package. Probably related with libvpx
package.I am not sure.
** Also affects: libvpx (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libvpx in Ubuntu.
https://bugs.launchpad.net/bugs/1993867
Title:
Telegram sometimes start endless use 100% CPU
Status in libvpx package in Ubuntu:
New
Status in telegram-desktop package in Ubuntu:
New
Bug description:
On Ubuntu 22.04 all was fine.
After upgrade to Ubuntu 22.10 Telegram was also updated. And
sometimes, randomly, TG starts to use 100% CPU.
Nothing on logs. But in starce i see a lot of these messages:
[pid 33581] poll([{fd=7, events=POLLIN}, {fd=8, events=POLLIN}, {fd=9,
events=POLLIN}, {fd=14, events=POLLIN}, {fd=19, events=POLLIN}, {fd=51,
events=POLLIN}], 6, 8) = 0 (Timeout)
PSA. Thousand messages.
In normal state, when TG use 0-2% CPU, i see same messages. So, not
related with bug.
Please, ask me additional information, i can provide any logs.
Today this bug occurs two times.
ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: telegram-desktop 4.1.1+ds-1ubuntu2
ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
Uname: Linux 5.19.0-21-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 22 01:53:36 2022
InstallationDate: Installed on 2018-05-02 (1633 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: telegram-desktop
UpgradeStatus: Upgraded to kinetic on 2022-10-20 (1 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvpx/+bug/1993867/+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 1993902] [NEW] package libgdk-pixbuf-2.0-0:i386 2.42.8+dfsg-1ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before att
Public bug reported: i cant not install wine in my ubuntu ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libgdk-pixbuf-2.0-0:i386 2.42.8+dfsg-1ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Oct 22 22:51:38 2022 DuplicateSignature: package:libgdk-pixbuf-2.0-0:i386:2.42.8+dfsg-1ubuntu0.1 Setting up libopenal-data (1:1.19.1-2build3) ... dpkg: error processing package libgdk-pixbuf-2.0-0:i386 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2022-10-21 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: i386 Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: gdk-pixbuf Title: package libgdk-pixbuf-2.0-0:i386 2.42.8+dfsg-1ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdk-pixbuf (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 jammy need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1993902 Title: package libgdk-pixbuf-2.0-0:i386 2.42.8+dfsg-1ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in gdk-pixbuf package in Ubuntu: New Bug description: i cant not install wine in my ubuntu ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libgdk-pixbuf-2.0-0:i386 2.42.8+dfsg-1ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Oct 22 22:51:38 2022 DuplicateSignature: package:libgdk-pixbuf-2.0-0:i386:2.42.8+dfsg-1ubuntu0.1 Setting up libopenal-data (1:1.19.1-2build3) ... dpkg: error processing package libgdk-pixbuf-2.0-0:i386 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2022-10-21 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: i386 Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: gdk-pixbuf Title: package libgdk-pixbuf-2.0-0:i386 2.42.8+dfsg-1ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1993902/+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 1993892] Re: Window area is unusable
** Package changed: ubuntu => xorg (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/1993892 Title: Window area is unusable Status in xorg package in Ubuntu: New Bug description: The window area becomes unusable without warning and the same visual artefacts are seen (see attached). The system taskbar is still responsive, so I can logout/login, which resolves the issues temporarily. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 22 16:10:38 2022 DistUpgraded: 2022-10-21 06:47:07,363 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:2081] InstallationDate: Installed on 2022-10-14 (7 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Intel(R) Client Systems NUC10i5FNH ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_ZA.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_6w0xyh@/vmlinuz-5.19.0-21-generic root=ZFS=rpool/ROOT/ubuntu_6w0xyh ro quiet splash vt.handoff=1 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2022-10-21 (1 days ago) dmi.bios.date: 04/09/2021 dmi.bios.release: 5.16 dmi.bios.vendor: Intel Corp. dmi.bios.version: FNCML357.0052.2021.0409.1144 dmi.board.asset.tag: Default string dmi.board.name: NUC10i5FNB dmi.board.vendor: Intel Corporation dmi.board.version: M38063-307 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 3.9 dmi.modalias: dmi:bvnIntelCorp.:bvrFNCML357.0052.2021.0409.1144:bd04/09/2021:br5.16:efr3.9:svnIntel(R)ClientSystems:pnNUC10i5FNH:pvrM38014-308:rvnIntelCorporation:rnNUC10i5FNB:rvrM38063-307:cvnIntelCorporation:ct35:cvr2.0:skuBXNUC10i5FNHN: dmi.product.family: FN dmi.product.name: NUC10i5FNH dmi.product.sku: BXNUC10i5FNHN dmi.product.version: M38014-308 dmi.sys.vendor: Intel(R) Client Systems version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1993892/+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 1993892] [NEW] Window area is unusable
You have been subscribed to a public bug: The window area becomes unusable without warning and the same visual artefacts are seen (see attached). The system taskbar is still responsive, so I can logout/login, which resolves the issues temporarily. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 22 16:10:38 2022 DistUpgraded: 2022-10-21 06:47:07,363 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:2081] InstallationDate: Installed on 2022-10-14 (7 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Intel(R) Client Systems NUC10i5FNH ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_ZA.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_6w0xyh@/vmlinuz-5.19.0-21-generic root=ZFS=rpool/ROOT/ubuntu_6w0xyh ro quiet splash vt.handoff=1 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2022-10-21 (1 days ago) dmi.bios.date: 04/09/2021 dmi.bios.release: 5.16 dmi.bios.vendor: Intel Corp. dmi.bios.version: FNCML357.0052.2021.0409.1144 dmi.board.asset.tag: Default string dmi.board.name: NUC10i5FNB dmi.board.vendor: Intel Corporation dmi.board.version: M38063-307 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 3.9 dmi.modalias: dmi:bvnIntelCorp.:bvrFNCML357.0052.2021.0409.1144:bd04/09/2021:br5.16:efr3.9:svnIntel(R)ClientSystems:pnNUC10i5FNH:pvrM38014-308:rvnIntelCorporation:rnNUC10i5FNB:rvrM38063-307:cvnIntelCorporation:ct35:cvr2.0:skuBXNUC10i5FNHN: dmi.product.family: FN dmi.product.name: NUC10i5FNH dmi.product.sku: BXNUC10i5FNHN dmi.product.version: M38014-308 dmi.sys.vendor: Intel(R) Client Systems version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-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 corruption kinetic third-party-packages ubuntu wayland-session -- Window area is unusable https://bugs.launchpad.net/bugs/1993892 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- 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 1646665] Re: System becomes unstable on resume
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. Reporter says in comment #5 that issue has been fixed. Sorry Mike, for not acknowledging your comment until now. I'm closing this now as being fixed as there have been no further comments for over five years now. ** Changed in: xorg (Ubuntu) Status: Confirmed => 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/1646665 Title: System becomes unstable on resume Status in xorg package in Ubuntu: Fix Released Bug description: After I come back from suspend the system looks fine, then once launching the Unity dash the system becomes unstable. The graphics start to render incorrectly and eventually the system will crash. Once this problem starts it can be stopped by switching to TTY1 and back to 7. I experience many of the following errors in dmesg every second until I swap TTY. [ 58.425802] NVRM: Xid (PCI::01:00): 56, CMDre 0001 00c0 000100b2 0007 The machine has been tested with Ubuntu 16.04 and .10, running all of the nvidia 367, 370, and 375 drivers. SPEC: i7 6700 Skylake Processor nVidia 1060 Graphics 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 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 367.57 Mon Oct 3 20:37:01 PDT 2016 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1) .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: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Dec 2 01:53:30 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed nvidia-367, 367.57, 4.4.0-31-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation Device [10de:1c60] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:6a04] InstallationDate: Installed on 2016-12-02 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 1c7a:0603 LighTuning Technology Inc. Bus 001 Device 002: ID 046d:c521 Logitech, Inc. Cordless Mouse Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook P65xRP ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=289b4b8b-3286-44d0-8713-84abcf69afc4 ro quiet splash i8042.reset i8042.nomux vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/21/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.07 dmi.board.asset.tag: Tag 12345 dmi.board.name: P65xRP dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.07:bd10/21/2016:svnNotebook:pnP65xRP:pvrNotApplicable:rvnNotebook:rnP65xRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.name: P65xRP dmi.product.version: Not Applicable dmi.sys.vendor: Notebook 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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A 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 Dec 2 01:51:08 2016 xserver.configfile: default xserver.errors: evdev: Chicony USB 2.0 Camera: Unable to open evdev device
[Touch-packages] [Bug 1993478] Re: package openssh-server 1:9.0p1-1ubuntu7 failed to install/upgrade: postinstall script returned 1
I deleted my account, so I had to create a new one. I used Linux headless, I'll move away to a Systemd Linux distro that doesn't pull shenanigans or tries to reinvent the wheel every update. Whomever pushed this script didn't test it with anything else than the default all commented ListenAddress and Port in the config. On my install it failed to convert a custom Listenaddress and Port formatted exactly as in the default sshd_config file: Port 622 ListenAddress 0.0.0.0 The machine that didn't return an openssh-server error post-upgrade had and almost untouched sshd_config with ListenAddress and Port commented to use opensshd-server default ListenAddress/Port. I know how to set ports with sockets. I didn't see the new # comment in the sshd_config at first I just didn't get why the third party systemd socket was taking precedence over the config from the original application package. The machine that didn't fail installing openssh-server post-upgrade had a /etc/systemd/system/ssh.socket.d/override.conf set. Sorry if I hijacked your bug report a bit. -- 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/1993478 Title: package openssh-server 1:9.0p1-1ubuntu7 failed to install/upgrade: postinstall script returned 1 Status in openssh package in Ubuntu: Triaged Bug description: update failed... ProblemType: Package DistroRelease: Ubuntu 22.10 Package: openssh-server 1:9.0p1-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: cpuid tcp_diag inet_diag tls authenc echainiv esp4 xfrm_user xfrm_algo sctp ip6_udp_tunnel udp_tunnel cfg80211 veth nft_chain_nat xt_REDIRECT nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_tcpudp nft_counter xt_policy nft_compat nf_tables nfnetlink bridge stp llc nls_iso8859_1 hid_generic joydev crct10dif_pclmul crc32_pclmul ghash_clmulni_intel usbhid virtio_net net_failover hid failover i2c_piix4 pata_acpi qemu_fw_cfg floppy sch_fq_codel ipmi_devintf ipmi_msghandler msr ramoops reed_solomon pstore_blk efi_pstore pstore_zone ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress dm_crypt raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx libcrc32c xor raid6_pq raid1 raid0 multipath linear bochs drm_vram_helper drm_ttm_helper ttm drm_kms_helper syscopyarea aesni_intel sysfillrect sysimgblt input_leds fb_sys_fops cec crypto_simd rc_core psmouse cryptd drm serio_raw virtio_scsi mac_hid ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Oct 19 08:41:28 2022 ErrorMessage: »installiertes post-installation-Skript des Paketes openssh-server«-Unterprozess gab den Fehlerwert 1 zurück InstallationDate: Installed on 2019-08-13 (1162 days ago) InstallationMedia: Ubuntu-Server 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.9ubuntu1 apt 2.5.3 SourcePackage: openssh Title: package openssh-server 1:9.0p1-1ubuntu7 failed to install/upgrade: »installiertes post-installation-Skript des Paketes openssh-server«-Unterprozess gab den Fehlerwert 1 zurück UpgradeStatus: Upgraded to kinetic on 2022-10-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1993478/+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 1686633] Re: Could not set the configuration for CRTC 64
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'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug 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/1686633 Title: Could not set the configuration for CRTC 64 Status in xorg package in Ubuntu: Incomplete Bug description: I am running on a dual screen installation with a razer blade laptop. At startup, I have a popup saying "Could not set the configuration for CRTC 64". If I close the popup, I loose all of my screens. If I let the popup opened, everything works fine except that some ubuntu components doesn't show up with the usual visual style (i.e. no 3d effect and no fancy color for OS buttons). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59 Uname: Linux 4.4.0-77-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.39 Tue Jan 31 20:47:00 PST 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) .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: Thu Apr 27 10:27:02 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: Razer USA Ltd. Skylake Integrated Graphics [1a58:674f] NVIDIA Corporation Device [10de:1c20] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Razer USA Ltd. Device [1a58:674f] InstallationDate: Installed on 2016-05-07 (355 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Razer Blade ProcEnviron: LANGUAGE=fr_FR TERM=xterm-256color PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-77-generic root=UUID=78c70b10-8984-4954-bb25-3d374dd77dd6 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/02/2016 dmi.bios.vendor: Razer dmi.bios.version: E1.00 dmi.board.name: Blade dmi.board.vendor: Razer dmi.board.version: Late 2016 dmi.chassis.type: 9 dmi.chassis.vendor: Razer dmi.chassis.version: Blade (Late 2016) dmi.modalias: dmi:bvnRazer:bvrE1.00:bd09/02/2016:svnRazer:pnBlade:pvr5.04:rvnRazer:rnBlade:rvrLate2016:cvnRazer:ct9:cvrBlade(Late2016): dmi.product.name: Blade dmi.product.version: 5.04 dmi.sys.vendor: Razer 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 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 Apr 27 10:22:39 2017 xserver.configfile: /etc/X11/xorg.conf xserver.errors: modeset(G0): failed to set mode: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1686633/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1639581] Re: New_nvidia_driver.
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'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug 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/1639581 Title: New_nvidia_driver. Status in xorg package in Ubuntu: Incomplete Bug description: It has something to do with the NVIDIA driver that has just been updated. It starts in low resolution with startup. Can startup in recovery modus. My GPU is Nvidia GEFORCE GTX 970 desktop. If I disable bootloader graphics and disable VESA framebuffer driver and disable PAT memory I get a cursor and a blackscreen. 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 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 367.57 Mon Oct 3 20:37:01 PDT 2016 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2) .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 Nov 6 15:07:37 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-45-generic, x86_64: installed nvidia-367, 367.57, 4.4.0-45-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Elitegroup Computer Systems GM204 [GeForce GTX 970] [1019:1029] InstallationDate: Installed on 2016-11-06 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: MEDION Akoya P5332 I/C124 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-45-generic root=/dev/mapper/ubuntu--vg-root ro recovery nomodeset SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/04/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 110EMW0X.102 dmi.board.name: H110H4-EM dmi.board.vendor: MEDION dmi.board.version: 2.0 dmi.chassis.type: 3 dmi.chassis.vendor: MEDION dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr110EMW0X.102:bd03/04/2016:svnMEDION:pnAkoyaP5332I/C124:pvr1.0:rvnMEDION:rnH110H4-EM:rvr2.0:cvnMEDION:ct3:cvr: dmi.product.name: Akoya P5332 I/C124 dmi.product.version: 1.0 dmi.sys.vendor: MEDION 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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1 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: Sun Nov 6 14:47:05 2016 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1639581/+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 1373448] Re: [ASUS X202E] Unable to set third button emulation on Atmel touchscreen
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 14.04 (trusty) reached end-of-standard-support on April 25, 2019. I'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. Dies this bug report have any relevance when using a currently maintained release of Ubuntu? If so, then please let us know which one(s) otherwise this bug 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/1373448 Title: [ASUS X202E] Unable to set third button emulation on Atmel touchscreen Status in xorg package in Ubuntu: Incomplete Bug description: My machine is ASUS X202E. It has an Atmel maXTouch Digitizer. I modified /usr/share/X11/xorg.conf.d/10-evdev.conf to add the following options to the touchscreen section: Option "EmulateThirdButton" "1" Option "EmulateThirdButtonButton" "3" Option "EmulateThirdButtonTimeout" "750" Option "EmulateThirdButtonThreshold" "50" and restarted X. Running xinput list-props shows that these properties are indeed set for the Atmel touchscreen device. However, when I touch and hold my finger in the same spot on the screen, nothing happens! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.4 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 Sep 24 16:09:59 2014 DistUpgraded: 2014-04-18 09:55:47,870 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:108d] InstallationDate: Installed on 2013-10-15 (343 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131007) MachineType: ASUSTeK COMPUTER INC. X202E ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic.efi.signed root=UUID=bcc104a1-a7cd-4485-b9ff-bf585e1eec22 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-04-18 (159 days ago) dmi.bios.date: 06/20/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X202E.210 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X202E 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.:bvrX202E.210:bd06/20/2013:svnASUSTeKCOMPUTERINC.:pnX202E:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX202E:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X202E dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Sep 24 16:08:42 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 12380 vendor AUO xserver.version: 2:1.15.1-0ubuntu2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1373448/+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 1733346] Re: package keyboard-configuration 1.166ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: console-setup (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1733346 Title: package keyboard-configuration 1.166ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in console-setup package in Ubuntu: Confirmed Bug description: no idee, the bug was displayed after i loged in ... ProblemType: Package DistroRelease: Ubuntu 17.10 Package: keyboard-configuration 1.166ubuntu7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.4 Architecture: amd64 Date: Sun Nov 19 21:10:16 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-11-19 (1 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: console-setup Title: package keyboard-configuration 1.166ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to artful on 2017-11-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1733346/+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 1730469] Re: Display session freezes constitently on login after Win10 dual boot crash - Ubuntu 16.04
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. Further to comment #10 I'm closing this as 'Invalid' as it doesn't appear from the information given that an update fixed the problem. Maxime, I'm sorry that it took someone almost five years to acknowledge your comment. Thanks for reporting your issue though. ** 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/1730469 Title: Display session freezes constitently on login after Win10 dual boot crash - Ubuntu 16.04 Status in xorg package in Ubuntu: Invalid Bug description: Hello, I have a Sandybridge-B970 X301-Asus laptop. I am used to dual boot on it : win10 and Ubuntu Xenial on a 275 GB SSD. Yesterday I manually forced shut down on win10 which looked hung on ~"preparation... do not shut down". Windows recovered, but Ubuntu was corrupted it seems. Grub2 launches, Ubuntu boots. I reach lightdm greeter. Then I cannot input mouse nor keyboard, and after a few inputs login prompt hangs. The UI displays "connected to ethernet". I cannot Alt Gr Fx to other ttys. I can REISUB, I can launch a recovery mode and get a root shell. I can SSH after normal boot from an external Debian system. Filesystem looks OK. Not sure but for some reason directories seems to have appeared in /root (git..) My SSD partitions : https://postimg.org/image/2hmo7pgfiz/, on top of debug info. Best regards! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Mon Nov 6 18:38:53 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [1043:14f7] InstallationDate: Installed on 2017-03-04 (247 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: ASUSTeK COMPUTER INC. X301A1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic.efi.signed root=UUID=84fd9c9d-fdb2-4ebf-a754-115d068500e0 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/02/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X301A1.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X301A1 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.:bvrX301A1.204:bd05/02/2012:svnASUSTeKCOMPUTERINC.:pnX301A1:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX301A1:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X301A1 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 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 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: Mon Nov 6 18:33:32 2017 xserver.configfile: default xserver.devices: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.7 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1730469/+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 1604742] Re: Black screen when booting without nomodeset
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'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug 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/1604742 Title: Black screen when booting without nomodeset Status in Ubuntu: Incomplete Bug description: It happens intermittently. Some times after a kernel upgrade it boots fine, but immediately after the screensaver turns on the screen gets black with the backlight on. After a good boot it returns to booting to a black screen. The system is working while the black screen is on. I am able to log in and shutdown via console (blindly) I have tried to write dmesg to a file while it is in this mode and I got this: [ 1835.947242] cfg80211: (5815000 KHz - 585 KHz @ 35000 KHz), (N/A, 3301 mBm), (0 s) [ 1835.947243] cfg80211: (1710 KHz - 1730 KHz @ 20 KHz), (N/A, 2000 mBm), (N/A) [ 1835.947244] cfg80211: (5700 KHz - 6600 KHz @ 216 KHz), (N/A, 4000 mBm), (N/A) [ 1835.952825] wlp3s0: Limiting TX power to 18 dBm as advertised by 04:da:d2:fd:7d:0e [ 1998.759411] [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many full retries, give up [ 1998.770230] [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many full retries, give up [ 1998.781095] [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many full retries, give up [ 1998.791896] [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many full retries, give up [ 1998.802880] [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many full retries, give up [ 1998.813780] [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many full retries, give up [ 1998.824569] [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many full retries, give up [ 1998.824747] [drm:intel_dp_start_link_train [i915_bpo]] *ERROR* failed to train DP, aborting This was after a boot failed. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 367.35 Mon Jul 11 23:14:21 PDT 2016 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1) .tmp.unity_support_test.1: 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: Wed Jul 20 11:41:21 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed nvidia-367, 367.35, 4.4.0-31-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Skylake Integrated Graphics [1558:1501] NVIDIA Corporation Device [10de:1667] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:1503] InstallationDate: Installed on 2016-07-09 (10 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1c7a:0603 LighTuning Technology Inc. Bus 001 Device 003: ID 5986:066d Acer, Inc Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N15_N17RF1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=32802ab4-59f5-434e-a6a4-8ee988bf7e24 ro nomodeset quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh
[Touch-packages] [Bug 1993478] Re: package openssh-server 1:9.0p1-1ubuntu7 failed to install/upgrade: postinstall script returned 1
@crhis34 actually socket activated ssh is not that difficult to setup. The issue for me is only that the upgrade of the configuration did not work quite right (and I think it is really challenging to do that right) but simply put you take the file /etc/systemd/system/ssh.socket.d/addresses.conf and write something like [Socket] ListenStream= ListenStream= (note the empty ListenStream=, that one is required to not listen on port 22) followed by a systemctl daemon-reload then if there is no /etc/systemd/system/ssh.service.d created by the upgrade script then what I did was systemctl enable ssh.socket && systemctl disable --now ssh.service && systemctl start ssh.socket an alternative might be doing that what the update script does: override_dir=/etc/systemd/system/ssh.service.d mkdir -p "$override_dir" echo '[Unit]' > "$override_dir"/00-socket.conf echo 'After=ssh.socket' >> "$override_dir"/00-socket.conf echo 'Requires=ssh.socket' >> "$override_dir"/00-socket.conf # deb-systemd-helper is inadequate for the task of # changing policy for the units on upgrade if [ -d /run/systemd/system ]; then systemctl daemon-reload systemctl disable ssh.service systemctl unmask ssh.service systemctl stop ssh.service systemctl enable ssh.socket fi -- 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/1993478 Title: package openssh-server 1:9.0p1-1ubuntu7 failed to install/upgrade: postinstall script returned 1 Status in openssh package in Ubuntu: Triaged Bug description: update failed... ProblemType: Package DistroRelease: Ubuntu 22.10 Package: openssh-server 1:9.0p1-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: cpuid tcp_diag inet_diag tls authenc echainiv esp4 xfrm_user xfrm_algo sctp ip6_udp_tunnel udp_tunnel cfg80211 veth nft_chain_nat xt_REDIRECT nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_tcpudp nft_counter xt_policy nft_compat nf_tables nfnetlink bridge stp llc nls_iso8859_1 hid_generic joydev crct10dif_pclmul crc32_pclmul ghash_clmulni_intel usbhid virtio_net net_failover hid failover i2c_piix4 pata_acpi qemu_fw_cfg floppy sch_fq_codel ipmi_devintf ipmi_msghandler msr ramoops reed_solomon pstore_blk efi_pstore pstore_zone ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress dm_crypt raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx libcrc32c xor raid6_pq raid1 raid0 multipath linear bochs drm_vram_helper drm_ttm_helper ttm drm_kms_helper syscopyarea aesni_intel sysfillrect sysimgblt input_leds fb_sys_fops cec crypto_simd rc_core psmouse cryptd drm serio_raw virtio_scsi mac_hid ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Oct 19 08:41:28 2022 ErrorMessage: »installiertes post-installation-Skript des Paketes openssh-server«-Unterprozess gab den Fehlerwert 1 zurück InstallationDate: Installed on 2019-08-13 (1162 days ago) InstallationMedia: Ubuntu-Server 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.9ubuntu1 apt 2.5.3 SourcePackage: openssh Title: package openssh-server 1:9.0p1-1ubuntu7 failed to install/upgrade: »installiertes post-installation-Skript des Paketes openssh-server«-Unterprozess gab den Fehlerwert 1 zurück UpgradeStatus: Upgraded to kinetic on 2022-10-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1993478/+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 1683271] Re: webGLSL: "return" ignored in "if"
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. This bug seems to have been fixed some time ago as I'm not seeing an issue when using Chrome and Firefox in both Ubuntu 20.04 and 22.04. Comments in the link above imply that is the case. Without any version information being given for Ubuntu, Firefox or Chrome I'm closing this as probably being fixed in updates since this bug report was raised. ** 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/1683271 Title: webGLSL: "return" ignored in "if" Status in xorg package in Ubuntu: Fix Released Bug description: This bug occurs in web GLSL ES since WebGl2.0 , on firefox and chrome. in some configurations (probably: divergent branches with only some having a "return"), "return" in "if" is ignored. see simple proof case here: https://www.shadertoy.com/view/MsScDm (this is also the cause of several existing shaders no longer working since WebGl2.0 ). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1683271/+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 1732116] Re: HDMI device is not working / not found
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'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug 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/1732116 Title: HDMI device is not working / not found Status in xorg package in Ubuntu: Incomplete Bug description: after conecting TV over HDMI, Ubuntu doenst find the external display ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-38-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 CurrentDesktop: Unity Date: Tue Nov 14 10:29:17 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G94GLM [Quadro FX 2700M] [10de:063a] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company G94GLM [Quadro FX 2700M] [103c:30ec] InstallationDate: Installed on 2017-09-10 (64 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Hewlett-Packard HP EliteBook 8730w PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver "pata_pcmcia" ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic root=UUID=95c3f524-8551-407a-91a0-65632f3854b3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/03/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PAD Ver. F.13 dmi.board.name: 30EC dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 91.25 dmi.chassis.asset.tag: CNU911000L dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PADVer.F.13:bd12/03/2010:svnHewlett-Packard:pnHPEliteBook8730w:pvrF.13:rvnHewlett-Packard:rn30EC:rvrKBCVersion91.25:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8730w dmi.product.version: F.13 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.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 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: Tue Nov 14 09:58:47 2017 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1~16.04.4 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1732116/+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 1682941] Re: graphics connection and resolution
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'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) and give us full details of any problem that you are seeing. Otherwise this bug 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/1682941 Title: graphics connection and resolution Status in xorg package in Ubuntu: Incomplete Bug description: Please see bug report. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49 Uname: Linux 4.4.0-72-generic i686 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Apr 14 17:22:54 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: VIA Technologies, Inc. VX900 Graphics [Chrome9 HD] [1106:7122] (prog-if 00 [VGA controller]) Subsystem: VIA Technologies, Inc. VX900 Graphics [Chrome9 HD] [1106:7122] InstallationDate: Installed on 2017-04-14 (0 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) MachineType: Hewlett-Packard HP t5565z Thin Client ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic root=UUID=6ed5fed6-7449-44ca-b3be-da8be55b0514 ro quiet vesafb.invalid=1 splash Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/10/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 786R9 v1.04 dmi.board.asset.tag: Astronaut dmi.board.name: 158Ch dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: MXL2150RT5 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr786R9v1.04:bd11/10/2011:svnHewlett-Packard:pnHPt5565zThinClient:pvr:rvnHewlett-Packard:rn158Ch:rvr:cvnHewlett-Packard:ct3:cvr: dmi.product.name: HP t5565z Thin Client dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 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 Apr 14 16:18:30 2017 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputSleep Button KEYBOARD, id 8 inputLogitech K400KEYBOARD, id 9 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/1682941/+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 1966787] Re: Totem crashes on launch | GStreamer-GL-CRITICAL **: Failed to flush Wayland connection | Gdk-Message: Error flushing display: Protocol error
*** This bug is a duplicate of bug 1965563 *** https://bugs.launchpad.net/bugs/1965563 Totem works in 22.10 -- 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/1966787 Title: Totem crashes on launch | GStreamer-GL-CRITICAL **: Failed to flush Wayland connection | Gdk-Message: Error flushing display: Protocol error Status in NVIDIA / egl-wayland: Unknown Status in egl-wayland package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in totem package in Ubuntu: Confirmed Bug description: If I launch totem, it crashes pretty much immediately. I resolved this by deleting .config/totem. I had moved some video files that had been previously opened within it recently, so possibly it was trying to reference them (for thumbnails or whatever) and that broke it. robin@malik:~$ totem (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection Gdk-Message: 18:00:17.844: Error flushing display: Protocol error robin@malik:~$ ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: totem 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 28 18:00:39 2022 InstallationDate: Installed on 2022-03-23 (5 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/egl-wayland/+bug/1966787/+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 1703129] Re: VCE init error and much more in my lappy please see it
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'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug 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/1703129 Title: VCE init error and much more in my lappy please see it Status in xorg package in Ubuntu: Incomplete Bug description: more errors see it ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67 Uname: Linux 4.4.0-81-generic x86_64 NonfreeKernelModules: openafs wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.6 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 Jul 8 20:48:24 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.4.0-81-generic, x86_64: installed openafs, 1.6.15, 4.4.0-79-generic, x86_64: installed openafs, 1.6.15, 4.4.0-81-generic, x86_64: installed GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Broadwell-U Integrated Graphics [103c:80c2] InstallationDate: Installed on 2016-11-24 (225 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard HP Notebook ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-81-generic.efi.signed root=UUID=f110cba6-8b9c-4548-8ed4-f543954307e6 ro splash quiet vesafb.invalid=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/17/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.21 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80C2 dmi.board.vendor: Hewlett-Packard dmi.board.version: 96.47 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.21:bd05/17/2016:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn80C2:rvr96.47:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId 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 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: Sat Jul 8 17:29:30 2017 xserver.configfile: default xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 20049 vendor SDC xserver.version: 2:1.18.4-0ubuntu0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1703129/+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 1659140] Re: x crashes when I log in and back out of a tty (console, cntrl-alt-F2 thing, whatever)
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'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. Does this bug report have any relevance when using a currently maintained release of Ubuntu? If so, please let us know which one(s) otherwise this bug report can be left to expire in approximately 60 days time. ** Tags removed: security startx tty ** Tags added: xenial ** 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/1659140 Title: x crashes when I log in and back out of a tty (console, cntrl-alt-F2 thing, whatever) Status in xorg package in Ubuntu: Incomplete Bug description: Observed behavior: When I get an alternate tty, or whatever it's called, with cntrl-alt- FN, where N is any digit, 2-6, inclusive; log in as the same user on the console; do stuff; and then log out with "exit": I'm suddenly back in tty1 and X has crashed. There is no x on any console. I can start it again with startx. Expected behavior: As it does in 14.04, I should just get a login prompt and stay in the same console. X running in tty1 should be unaffected, like x in tty7 would be unaffected in Trusty. This is 64 bit Xenial with a minimalist Openbox environment, built from the mini.iso. I start X with "startx". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1659140/+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 1708829] Re: Unable to detect correct resolution of external monitor
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'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug 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/1708829 Title: Unable to detect correct resolution of external monitor Status in xorg package in Ubuntu: Incomplete Bug description: My system is unable to detect the correct resolution of the monitor. This problem is not consistent and happens randomly. I think its a driver issue. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73 Uname: Linux 4.4.0-87-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: Sat Aug 5 17:51:25 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-87-generic, x86_64: installed bbswitch, 0.8, 4.4.0-89-generic, x86_64: installed nvidia-375, 375.66, 4.4.0-87-generic, x86_64: installed nvidia-375, 375.66, 4.4.0-89-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller [17aa:380a] Subsystem: Lenovo GK208M [GeForce GT 740M] [17aa:380a] InstallationDate: Installed on 2015-12-21 (593 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 20287 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-87-generic.efi.signed root=UUID=b2b670cf-975c-444c-b9be-75df78fb9323 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/24/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 8DCN40WW dmi.board.asset.tag: No Asset Tag dmi.board.name: VIUU4 dmi.board.vendor: LENOVO dmi.board.version: 31900059STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Z510 dmi.modalias: dmi:bvnLENOVO:bvr8DCN40WW:bd10/24/2014:svnLENOVO:pn20287:pvrLenovoIdeaPadZ510:rvnLENOVO:rnVIUU4:rvr31900059STD:cvnLENOVO:ct10:cvrLenovoIdeaPadZ510: dmi.product.name: 20287 dmi.product.version: Lenovo IdeaPad Z510 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.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 2:1.18.4-0ubuntu0.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.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Aug 4 23:58:05 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5565 vendor CMN xserver.version: 2:1.18.4-0ubuntu0.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1708829/+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 1655436] Re: HDMI-display not working
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'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug 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/1655436 Title: HDMI-display not working Status in xorg package in Ubuntu: Incomplete Bug description: Hi! Since I upgraded to Ubuntu 16.04 my HDMI-display is not recognized. I'm on an HP laptop (dv7-1095) with an Nvidia 9600M GT graphics card. Does anyone know what might cause this problem? :) Regards Emil ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.134 Fri Dec 9 11:30:02 PST 2016 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.4 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: Tue Jan 10 20:31:47 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-57-generic, x86_64: installed bbswitch, 0.8, 4.4.0-59-generic, x86_64: installed nvidia-304, 304.134, 4.4.0-59-generic, x86_64: installed GraphicsCard: NVIDIA Corporation G96M [GeForce 9600M GT] [10de:0649] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company G96M [GeForce 9600M GT] [103c:30f4] InstallationDate: Installed on 2017-01-08 (2 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-59-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/17/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.0A dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 30F4 dmi.board.vendor: Compal dmi.board.version: 99.55 dmi.chassis.type: 10 dmi.chassis.vendor: Compal dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.0A:bd07/17/2008:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvrF.0A:rvnCompal:rn30F4:rvr99.55:cvnCompal:ct10:cvrN/A: dmi.product.name: HP Pavilion dv7 Notebook PC dmi.product.version: F.0A 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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A 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: Tue Jan 10 20:26:54 2017 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory 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/1655436/+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 1665853] Re: HWE 16.04.2: Login Screen goes partially black after upgrade (Dual Screen)
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'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug report can be left to expire in approximately 60 days time. ** Changed in: lightdm (Ubuntu) Status: New => Incomplete ** 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 lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1665853 Title: HWE 16.04.2: Login Screen goes partially black after upgrade (Dual Screen) Status in gnome-flashback package in Ubuntu: Invalid Status in lightdm package in Ubuntu: Incomplete Status in xorg package in Ubuntu: Incomplete Bug description: I'm using ubuntu 16.04, up-to-date, HWE kernel 4.8.0-36-generic. On dual screen setup, during system login, the first screen stretches over a part of the second screen (about 25% of it), whereas the rest of the second screen is black. Like this: # # #<<|...# # Login# #<<|.Black.# # # #<<|...# The part marked with "<<" is the rightest part of the background image of the first screen. I've seen this after updating to xorg/xserver- hwe-16.04, whereas installing the hwe kernel alone did not make this happen. Nevertheless, I can login and everything is fine again. Both screens look as they should. (I had to reconfigure monitors once after updating to xorg/xserver-hwe-16.04). sylog shows: Feb 18 06:27:03 lat61 gnome-session[3242]: ** (gnome-flashback:3340): WARNING **: Could not assign CRTC to outputs, ignoring configuration Feb 18 06:27:03 lat61 gnome-session[3242]: ** (gnome-flashback:3340): WARNING **: Could not make default configuration for current output layout, leaving unconfigured ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-flashback 3.18.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 Uname: Linux 4.8.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Sat Feb 18 07:46:46 2017 InstallationDate: Installed on 2014-11-29 (812 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: gnome-flashback UpgradeStatus: Upgraded to xenial on 2016-06-15 (247 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-flashback/+bug/1665853/+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 1321426] Re: x11-apps -> Should be recommends?
** Changed in: xorg (Ubuntu) Status: New => Opinion -- 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/1321426 Title: x11-apps -> Should be recommends? Status in xorg package in Ubuntu: Opinion Bug description: Smells like bloat to me. Who actually uses any of those programs outside of a few minimalist WMs that depend on it explicitly... not to mention that recommends are installed by default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1321426/+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 1645352] Re: No HDMI output after upgrade to 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. I'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug 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/1645352 Title: No HDMI output after upgrade to 16.04! Status in xorg package in Ubuntu: Incomplete Bug description: Running Ubuntu 16.04 64bit, 4.4.8 Kernel on an ASUS Trio with Intel® Haswell graphics card and using i915 driver. After upgrade there is no HDMI output to the external screen that I use daily. I did the following: - Upgraded to 4.4.8 Kernel hoping that the issue would be resolved. - Checked for other reports of this issue and followed advise to use NVIDIA 364 drivers. - Checked Intel for the most recent driver which is already packaged with 16.04; it is the i915 driver which is in use. - Used Intel driver update tool to ensure that update is correct. - Purchased a HDMI adapter to use mini-display port; works and reports HDMI1 is in use, but HDMI2 is not recognized (when monitor is plugged in to HDMI2) - Someone has assisted and has confirmed that there seems to be no hardware issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1645352/+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 1490255] Re: changes in /etc/default/keyboard not loaded
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 15.04 (vivid) reached end-of-life on February 4, 2016. I'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this issue is still relevant when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug 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/1490255 Title: changes in /etc/default/keyboard not loaded Status in xorg package in Ubuntu: Incomplete Bug description: Description: Ubuntu 15.04 Release: 15.04 Variant:Xubuntu What you expected to happen: Changes in /etc/default/keyboard to be effective. What happened instead: Nothing. ex: File : /etc/default/keyboard # KEYBOARD CONFIGURATION FILE # Consult the keyboard(5) manual page. XKBMODEL="pc105" XKBLAYOUT="fr" XKBVARIANT="latin9" XKBOPTIONS="altwin:ctrl_alt_win" BACKSPACE="guess" Nothing happens after boot. (but setxkbmap -option alt win:ctrl_alt_win does works) Suggestion : -Remove /etc/default/keyboard as it doesn't seems to serve any purpose other than misleading people. -Make somehow working as it should. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1490255/+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 1716184] Re: failure of xrandr to find any outputs
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 sorry that it took almost five years for someone to acknowledge your comment. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. As this bug report was never confirmed by another user and seems to have been fixed by a change to the system hardware I'm closing this by changing the status to 'Invalid'. ** 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/1716184 Title: failure of xrandr to find any outputs Status in xorg package in Ubuntu: Invalid Bug description: I have a very new Lenovo X1 Yoga 2nd edition, with oled display. The exact model is 20JECTO1WW. The BIOS is N1NET27W. I am running a vanilla Ubuntu 16.04 lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.3 LTS Release: 16.04 Codename: xenial uname -a Linux gjs-yoga 4.11.0-14-generic #20~16.04.1-Ubuntu SMP Wed Aug 9 09:06:22 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Until recently things worked quite well. But on August 26 I got an update from Ubuntu and things began to decay. In particular, I can no longer display except on the built-in display: For example, xrandr cannot find any outputs, even though this laptop has a (working) HDMI output port. xrandr --verbose xrandr: Failed to get size of gamma for output default Screen 0: minimum 2560 x 1440, current 2560 x 1440, maximum 2560 x 1440 default connected primary 2560x1440+0+0 (0x272) normal (normal) 0mm x 0mm Identifier: 0x271 Timestamp: 33974 Subpixel: unknown Clones: CRTC: 0 CRTCs: 0 Transform: 1.00 0.00 0.00 0.00 1.00 0.00 0.00 0.00 1.00 filter: _GNOME_FLASHBACK_PRESENTATION_OUTPUT: 0 2560x1440 (0x272) 342.835MHz *current h: width 2560 start0 end0 total 2560 skew0 clock 133.92KHz v: height 1440 start0 end0 total 1440 clock 93.00Hz Notice there are no (even disconnected) outputs other than default. Another symptom is that system restart always turns off the power rather than rebooting. I looked at the manifest of the update that seems to have caused trouble and the only suspicious entry is a microcode update from Intel. Here is the entry from the apt history log: Start-Date: 2017-08-26 17:54:05 Commandline: aptdaemon role='role-commit-packages' sender=':1.87' Upgrade: intel-microcode:amd64 (3.20151106.1, 3.20170707.1~ubuntu16.04.0), I hope that someone knows what is the problem here. I am stumped. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Uname: Linux 4.11.0-14-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Sep 9 18:54:56 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:224e] InstallationDate: Installed on 2017-07-27 (44 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 003: ID 04f2:b5ce Chicony Electronics Co., Ltd Bus 001 Device 004: ID 056a:5087 Wacom Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20JECTO1WW ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-14-generic root=/dev/mapper/ubuntu--vg-root ro nomodeset Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1NET27W (1.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 20JECTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1NET27W(1.14):bd07/12/2017:svnLENOVO:pn20JECTO1WW:pvrThinkPadX1Yoga2nd:rvnLENOVO:rn20JECTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone: dmi.product.name: 20JECTO1WW dmi.product.version: ThinkPad X1 Yoga 2nd dmi.sys.vendor:
[Touch-packages] [Bug 1909695] Re: Software application hasn't been installed
This issue has sat without a response to comment #1 for almost two years so it is being closed as 'Invalid'. The reporter gave us no indication as to which 'LTS' release was being installed. Please feel free to re-open this bug report if this issue has any relevance when using a currently supported release of Ubuntu but please make sure you tell us in which release you still experience this issue. ** Changed in: ubuntu-meta (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1909695 Title: Software application hasn't been installed Status in ubuntu-meta package in Ubuntu: Invalid Bug description: I installed Ubuntu LTS with mini.iso. After choosing ubuntu-desktop in task selection gnome-software was not installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1909695/+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 1993478] Re: package openssh-server 1:9.0p1-1ubuntu7 failed to install/upgrade: postinstall script returned 1
Port Specifies the port number that sshd(8) listens on. The default is 22. Multiple options of this type are permitted. See also ListenAddress. Note: On Ubuntu, the openssh-server package is configured to use systemd socket-based activation by default. Therefore if you are using systemd with the default configuration, Port options will not be honored. Address configuration must be handled in /etc/systemd/system/ssh.socket.d instead. # Port and ListenAddress options are not used when sshd is socket-activated, # which is now the default in Ubuntu. See sshd_config(5) and # /usr/share/doc/openssh-server/README.Debian.gz for details. -- For me, the post upgrade error didn't happen on the machine that had the default openssh-server port 22, but on the machine that had a custom port and bind address. I had to purge and reinstall openssh-server to fix the broken, partially installed, package post-upgrade. I only noticed the new message in the sshd_config configuration file after purging/reinstalling openssh-server second time on one of my machine. I was multitasking during the upgrade process, if there was a message about the new port configuration being a systemd socket, I missed it. -- 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/1993478 Title: package openssh-server 1:9.0p1-1ubuntu7 failed to install/upgrade: postinstall script returned 1 Status in openssh package in Ubuntu: Triaged Bug description: update failed... ProblemType: Package DistroRelease: Ubuntu 22.10 Package: openssh-server 1:9.0p1-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: cpuid tcp_diag inet_diag tls authenc echainiv esp4 xfrm_user xfrm_algo sctp ip6_udp_tunnel udp_tunnel cfg80211 veth nft_chain_nat xt_REDIRECT nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_tcpudp nft_counter xt_policy nft_compat nf_tables nfnetlink bridge stp llc nls_iso8859_1 hid_generic joydev crct10dif_pclmul crc32_pclmul ghash_clmulni_intel usbhid virtio_net net_failover hid failover i2c_piix4 pata_acpi qemu_fw_cfg floppy sch_fq_codel ipmi_devintf ipmi_msghandler msr ramoops reed_solomon pstore_blk efi_pstore pstore_zone ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress dm_crypt raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx libcrc32c xor raid6_pq raid1 raid0 multipath linear bochs drm_vram_helper drm_ttm_helper ttm drm_kms_helper syscopyarea aesni_intel sysfillrect sysimgblt input_leds fb_sys_fops cec crypto_simd rc_core psmouse cryptd drm serio_raw virtio_scsi mac_hid ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Oct 19 08:41:28 2022 ErrorMessage: »installiertes post-installation-Skript des Paketes openssh-server«-Unterprozess gab den Fehlerwert 1 zurück InstallationDate: Installed on 2019-08-13 (1162 days ago) InstallationMedia: Ubuntu-Server 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.9ubuntu1 apt 2.5.3 SourcePackage: openssh Title: package openssh-server 1:9.0p1-1ubuntu7 failed to install/upgrade: »installiertes post-installation-Skript des Paketes openssh-server«-Unterprozess gab den Fehlerwert 1 zurück UpgradeStatus: Upgraded to kinetic on 2022-10-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1993478/+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 1993478] Re: package openssh-server 1:9.0p1-1ubuntu7 failed to install/upgrade: postinstall script returned 1
slightly off-topic for those who find this before the 22.10 documentation: https://discourse.ubuntu.com/t/sshd-now-uses-socket-based-activation-ubuntu-22-10-and-later/30189 This bug is about the postinst script not being able to convert (or keep) every configuration around. In my case this is because the script is unable to parse ListenAddress with port. The script should understand this formats (quote from man sshd_config): ListenAddress hostname|address ListenAddress hostname:port ListenAddress IPv4_address:port ListenAddress [hostname|address]:port only the first is supported (and [hostname|address] without port) example of working statements ListenAddress localhost ListenAddress 127.0.0.1 ListenAddress [::1] ListenAddress ::1 example of valid but not working statements: ListenAddress localhost: ListenAddress 0.0.0.0: ListenAddress [::]: When converting [::] I think BindIPv6Only=yes should be used, but that's another topic -- 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/1993478 Title: package openssh-server 1:9.0p1-1ubuntu7 failed to install/upgrade: postinstall script returned 1 Status in openssh package in Ubuntu: Triaged Bug description: update failed... ProblemType: Package DistroRelease: Ubuntu 22.10 Package: openssh-server 1:9.0p1-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: cpuid tcp_diag inet_diag tls authenc echainiv esp4 xfrm_user xfrm_algo sctp ip6_udp_tunnel udp_tunnel cfg80211 veth nft_chain_nat xt_REDIRECT nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_tcpudp nft_counter xt_policy nft_compat nf_tables nfnetlink bridge stp llc nls_iso8859_1 hid_generic joydev crct10dif_pclmul crc32_pclmul ghash_clmulni_intel usbhid virtio_net net_failover hid failover i2c_piix4 pata_acpi qemu_fw_cfg floppy sch_fq_codel ipmi_devintf ipmi_msghandler msr ramoops reed_solomon pstore_blk efi_pstore pstore_zone ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress dm_crypt raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx libcrc32c xor raid6_pq raid1 raid0 multipath linear bochs drm_vram_helper drm_ttm_helper ttm drm_kms_helper syscopyarea aesni_intel sysfillrect sysimgblt input_leds fb_sys_fops cec crypto_simd rc_core psmouse cryptd drm serio_raw virtio_scsi mac_hid ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Oct 19 08:41:28 2022 ErrorMessage: »installiertes post-installation-Skript des Paketes openssh-server«-Unterprozess gab den Fehlerwert 1 zurück InstallationDate: Installed on 2019-08-13 (1162 days ago) InstallationMedia: Ubuntu-Server 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.9ubuntu1 apt 2.5.3 SourcePackage: openssh Title: package openssh-server 1:9.0p1-1ubuntu7 failed to install/upgrade: »installiertes post-installation-Skript des Paketes openssh-server«-Unterprozess gab den Fehlerwert 1 zurück UpgradeStatus: Upgraded to kinetic on 2022-10-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1993478/+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 1928789] Re: bpool free space low caused package linux-firmware 1.187.12 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- 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/1928789 Title: bpool free space low caused package linux-firmware 1.187.12 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: Warning from zsys that bpool only had 11% free space when manually running "apt upgrade". There were also several packages that could be "auto-removed". Once apt autoremove was run, the linux-firmware was installed OK. Perhaps apt (or package install) could: a) detect low disk space b) note that free space can be made with autoremove c) stop and raise an error, rather than crashing. $ sudo apt autoremove Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED linux-headers-5.8.0-49-generic linux-hwe-5.8-headers-5.8.0-49 linux-image-5.8.0-49-generic linux-modules-5.8.0-49-generic linux-modules-extra-5.8.0-49-generic python3-appdirs python3-distlib python3-filelock python3-importlib-metadata python3-more-itertools python3-virtualenv python3-zipp 0 to upgrade, 0 to newly install, 12 to remove and 1 not to upgrade. 2 not fully installed or removed. After this operation, 391 MB disk space will be freed. Do you want to continue? [Y/n] y Requesting to save current system state ERROR couldn't save system state: Minimum free space to take a snapshot and preserve ZFS performance is 20%. Free space on pool "bpool" is 11%. Please remove some states manually to free up space. (Reading database ... 289639 files and directories currently installed.) Removing linux-headers-5.8.0-49-generic (5.8.0-49.55~20.04.1) ... Removing linux-hwe-5.8-headers-5.8.0-49 (5.8.0-49.55~20.04.1) ... Removing linux-modules-extra-5.8.0-49-generic (5.8.0-49.55~20.04.1) ... Removing linux-image-5.8.0-49-generic (5.8.0-49.55~20.04.1) ... /etc/kernel/prerm.d/dkms: dkms: removing: virtualbox 6.1.16 (5.8.0-49-generic) (x86_64) Uninstall Beginning Module: virtualbox Version: 6.1.16 Kernel: 5.8.0-49-generic (x86_64) - Status: Before uninstall, this module version was ACTIVE on this kernel. vboxdrv.ko: - Uninstallation - Deleting from: /lib/modules/5.8.0-49-generic/updates/dkms/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. vboxnetadp.ko: - Uninstallation - Deleting from: /lib/modules/5.8.0-49-generic/updates/dkms/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. vboxnetflt.ko: - Uninstallation - Deleting from: /lib/modules/5.8.0-49-generic/updates/dkms/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. depmod... DKMS: uninstall completed. /etc/kernel/postrm.d/initramfs-tools: update-initramfs: Deleting /boot/initrd.img-5.8.0-49-generic /etc/kernel/postrm.d/zz-update-grub: Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/init-select.cfg' Generating grub configuration file ... Found linux image: vmlinuz-5.8.0-53-generic in rpool/ROOT/ubuntu_l3g9y7 Found initrd image: initrd.img-5.8.0-53-generic in rpool/ROOT/ubuntu_l3g9y7 Found linux image: vmlinuz-5.8.0-50-generic in rpool/ROOT/ubuntu_l3g9y7 Found initrd image: initrd.img-5.8.0-50-generic in rpool/ROOT/ubuntu_l3g9y7 Found linux image: vmlinuz-5.4.0-58-generic in rpool/ROOT/ubuntu_l3g9y7@autozsys_8mgn83 Found initrd image: initrd.img-5.4.0-58-generic in rpool/ROOT/ubuntu_l3g9y7@autozsys_8mgn83 Found linux image: vmlinuz-5.4.0-56-generic in rpool/ROOT/ubuntu_l3g9y7@autozsys_8mgn83 Found initrd image: initrd.img-5.4.0-56-generic in rpool/ROOT/ubuntu_l3g9y7@autozsys_8mgn83 Found linux image: vmlinuz-5.4.0-53-generic in rpool/ROOT/ubuntu_l3g9y7@autozsys_8mgn83 Found initrd image: initrd.img-5.4.0-53-generic in rpool/ROOT/ubuntu_l3g9y7@autozsys_8mgn83 Found linux image: vmlinuz-5.4.0-58-generic in rpool/ROOT/ubuntu_l3g9y7@autozsys_z80dj8 Found initrd image: initrd.img-5.4.0-58-generic in rpool/ROOT/ubuntu_l3g9y7@autozsys_z80dj8 Found linux image: vmlinuz-5.4.0-56-generic in rpool/ROOT/ubuntu_l3g9y7@autozsys_z80dj8 Found initrd image: initrd.img-5.4.0-56-generic in rpool/ROOT/ubuntu_l3g9y7@autozsys_z80dj8 Found linux image:
