[Touch-packages] [Bug 2029464] Re: A stack overflow in GNU Tar
Actually I just got it working - no need to send PoC @kerneldude - I made my own. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tar in Ubuntu. https://bugs.launchpad.net/bugs/2029464 Title: A stack overflow in GNU Tar Status in tar package in Ubuntu: New Bug description: A stack overflow vulnerability exists in GNU Tar up to including v1.34, as far as I can see, Ubuntu is using v1.3. The bug exists in the function xattr_decoder() in xheader.c, where alloca() is used and it may overflow the stack if a sufficiently long xattr key is used. The vulnerability can be triggered when extracting a tar/pax archive that contains such a long xattr key. Vulnerable code: https://git.savannah.gnu.org/cgit/tar.git/tree/src/xheader.c?h=release_1_34#n1723 PoC tar archive is attached in a zip archive to reduce the size. I reported the vulnerability yesterday to GNU Tar maintainers and they replied that the issue was fixed in the version that was released two weeks ago: "Sergey fixed that bug here: https://git.savannah.gnu.org/cgit/tar.git/commit/?id=a339f05cd269013fa133d2f148d73f6f7d4247e4 and the fix appears in tar 1.35, released July 18. " To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tar/+bug/2029464/+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 2029464] Re: A stack overflow in GNU Tar
So I managed to create a tar file with an extended attribute name of length of ~ 36 bytes long (the largest I can do without exceeding the existing check on maximum extended header lengths it seems) but this is not able to trigger the vuln - so if you are able to share your PoC that would be great. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tar in Ubuntu. https://bugs.launchpad.net/bugs/2029464 Title: A stack overflow in GNU Tar Status in tar package in Ubuntu: New Bug description: A stack overflow vulnerability exists in GNU Tar up to including v1.34, as far as I can see, Ubuntu is using v1.3. The bug exists in the function xattr_decoder() in xheader.c, where alloca() is used and it may overflow the stack if a sufficiently long xattr key is used. The vulnerability can be triggered when extracting a tar/pax archive that contains such a long xattr key. Vulnerable code: https://git.savannah.gnu.org/cgit/tar.git/tree/src/xheader.c?h=release_1_34#n1723 PoC tar archive is attached in a zip archive to reduce the size. I reported the vulnerability yesterday to GNU Tar maintainers and they replied that the issue was fixed in the version that was released two weeks ago: "Sergey fixed that bug here: https://git.savannah.gnu.org/cgit/tar.git/commit/?id=a339f05cd269013fa133d2f148d73f6f7d4247e4 and the fix appears in tar 1.35, released July 18. " To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tar/+bug/2029464/+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 2045722] Re: Ubuntu freeze randomly
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Run these commands: journalctl -b0 > journal.txt journalctl -b-1 > prevjournal.txt and attach the resulting text files here. 2. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 3. If step 2 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete ** Tags added: nvidia -- 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/2045722 Title: Ubuntu freeze randomly Status in Ubuntu: Incomplete Bug description: Sometimes happens when I leave it (probably screen lock), sometimes happens when I about to shutdown, sometimes happens when running. The log shows it is related to xorg or nvidia. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.129.03 Thu Oct 19 18:56:32 UTC 2023 GCC version: gcc version 11.4.0 (Ubuntu 11.4.0-1ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Dec 6 10:53:21 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/535.129.03, 5.15.0-89-generic, x86_64: installed nvidia/535.129.03, 6.2.0-36-generic, x86_64: installed nvidia/535.129.03, 6.2.0-37-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company CometLake-H GT2 [UHD Graphics] [103c:878e] NVIDIA Corporation TU106M [GeForce RTX 2060 Max-Q] [10de:1f12] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TU106M [GeForce RTX 2060 Max-Q] [103c:878e] InstallationDate: Installed on 2021-06-05 (913 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP ENVY Laptop 15-ep0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-37-generic root=UUID=34001051-5122-4187-b21f-2032a99219e8 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2021 dmi.bios.release: 15.7 dmi.bios.vendor: AMI dmi.bios.version: F.07 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 878E dmi.board.vendor: HP dmi.board.version: 18.33 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 18.33 dmi.modalias: dmi:bvnAMI:bvrF.07:bd07/30/2021:br15.7:efr18.33:svnHP:pnHPENVYLaptop15-ep0xxx:pvr:rvnHP:rn878E:rvr18.33:cvnHP:ct10:cvrChassisVersion:sku16P91PA#AR6: dmi.product.family: 103C_5335KV HP ENVY dmi.product.name: HP ENVY Laptop 15-ep0xxx dmi.product.sku: 16P91PA#AR6 dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1
[Touch-packages] [Bug 2045722] Re: Ubuntu freeze randomly
** 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/2045722 Title: Ubuntu freeze randomly Status in xorg package in Ubuntu: New Bug description: Sometimes happens when I leave it (probably screen lock), sometimes happens when I about to shutdown, sometimes happens when running. The log shows it is related to xorg or nvidia. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.129.03 Thu Oct 19 18:56:32 UTC 2023 GCC version: gcc version 11.4.0 (Ubuntu 11.4.0-1ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Dec 6 10:53:21 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/535.129.03, 5.15.0-89-generic, x86_64: installed nvidia/535.129.03, 6.2.0-36-generic, x86_64: installed nvidia/535.129.03, 6.2.0-37-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company CometLake-H GT2 [UHD Graphics] [103c:878e] NVIDIA Corporation TU106M [GeForce RTX 2060 Max-Q] [10de:1f12] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TU106M [GeForce RTX 2060 Max-Q] [103c:878e] InstallationDate: Installed on 2021-06-05 (913 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP ENVY Laptop 15-ep0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-37-generic root=UUID=34001051-5122-4187-b21f-2032a99219e8 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2021 dmi.bios.release: 15.7 dmi.bios.vendor: AMI dmi.bios.version: F.07 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 878E dmi.board.vendor: HP dmi.board.version: 18.33 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 18.33 dmi.modalias: dmi:bvnAMI:bvrF.07:bd07/30/2021:br15.7:efr18.33:svnHP:pnHPENVYLaptop15-ep0xxx:pvr:rvnHP:rn878E:rvr18.33:cvnHP:ct10:cvrChassisVersion:sku16P91PA#AR6: dmi.product.family: 103C_5335KV HP ENVY dmi.product.name: HP ENVY Laptop 15-ep0xxx dmi.product.sku: 16P91PA#AR6 dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 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/2045722/+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 2045722] [NEW] Ubuntu freeze randomly
You have been subscribed to a public bug: Sometimes happens when I leave it (probably screen lock), sometimes happens when I about to shutdown, sometimes happens when running. The log shows it is related to xorg or nvidia. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.129.03 Thu Oct 19 18:56:32 UTC 2023 GCC version: gcc version 11.4.0 (Ubuntu 11.4.0-1ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Dec 6 10:53:21 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/535.129.03, 5.15.0-89-generic, x86_64: installed nvidia/535.129.03, 6.2.0-36-generic, x86_64: installed nvidia/535.129.03, 6.2.0-37-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company CometLake-H GT2 [UHD Graphics] [103c:878e] NVIDIA Corporation TU106M [GeForce RTX 2060 Max-Q] [10de:1f12] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TU106M [GeForce RTX 2060 Max-Q] [103c:878e] InstallationDate: Installed on 2021-06-05 (913 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP ENVY Laptop 15-ep0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-37-generic root=UUID=34001051-5122-4187-b21f-2032a99219e8 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2021 dmi.bios.release: 15.7 dmi.bios.vendor: AMI dmi.bios.version: F.07 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 878E dmi.board.vendor: HP dmi.board.version: 18.33 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 18.33 dmi.modalias: dmi:bvnAMI:bvrF.07:bd07/30/2021:br15.7:efr18.33:svnHP:pnHPENVYLaptop15-ep0xxx:pvr:rvnHP:rn878E:rvr18.33:cvnHP:ct10:cvrChassisVersion:sku16P91PA#AR6: dmi.product.family: 103C_5335KV HP ENVY dmi.product.name: HP ENVY Laptop 15-ep0xxx dmi.product.sku: 16P91PA#AR6 dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 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 freeze jammy ubuntu -- Ubuntu freeze randomly https://bugs.launchpad.net/bugs/2045722 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 2043234] Re: Symlink for resolv.conf is wrong on fresh install
In case if noone can find where is the problem just instal fresh OS and run nslookup google.com Then check the validity of the symlink on resolv.conf -- 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/2043234 Title: Symlink for resolv.conf is wrong on fresh install Status in systemd package in Ubuntu: Invalid Bug description: Hello. Sorry for disturb, may I ask you please to confirm if im not doing anything wrong with new installation? Its being a while since the problem exists AT LEAST IN MY CASE with "faulty path" for symlinc at resolv.conf I believe its keep happening since 18.04 version and even now in 22.04 So, in the fresh install the path looks like this: lrwxrwxrwx 1 root root 39 Feb 17 2023 resolv.conf -> ../run/systemd/resolve/stub-resolv.conf but once im running : sudo ln -sf /run/systemd/resolve/resolv.conf /etc/resolv.conf everything works fine. By everything I mean when I run nslookup. Regards, Vitalii Sharapov To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2043234/+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 2043234] Re: Symlink for resolv.conf is wrong on fresh install
@enr0n Nick, did you compare the full path of what i wrote? Also what do you mean if I could provide specific example? As i wrote in main question you dont need anything specific as i tried in fresh brand new Ubuntu 22.04. Just install fresh new operating system and try to resolve google.com and system wont resolve, as it appears, the path is wrong initially. If you read closely, the path that to resolv.conf in the OS has two dots, while it should have no dots in the beginning of the path. Thats why i tested and asked here thinking that there is a bug -- 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/2043234 Title: Symlink for resolv.conf is wrong on fresh install Status in systemd package in Ubuntu: Invalid Bug description: Hello. Sorry for disturb, may I ask you please to confirm if im not doing anything wrong with new installation? Its being a while since the problem exists AT LEAST IN MY CASE with "faulty path" for symlinc at resolv.conf I believe its keep happening since 18.04 version and even now in 22.04 So, in the fresh install the path looks like this: lrwxrwxrwx 1 root root 39 Feb 17 2023 resolv.conf -> ../run/systemd/resolve/stub-resolv.conf but once im running : sudo ln -sf /run/systemd/resolve/resolv.conf /etc/resolv.conf everything works fine. By everything I mean when I run nslookup. Regards, Vitalii Sharapov To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2043234/+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 2023322] Re: GTK internal browser does not render with Nvidia drivers
That bug was filed before we fixed Jammy on 2023-11-20 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/2023322 Title: GTK internal browser does not render with Nvidia drivers Status in Webkit: Confirmed Status in gnome-control-center package in Ubuntu: Invalid Status in gnome-online-accounts package in Ubuntu: Invalid Status in webkit2gtk package in Ubuntu: Fix Released Status in yelp package in Ubuntu: Invalid Status in webkit2gtk package in Debian: Fix Released Bug description: When I go into Settings > Online Accounts > Google, I get to the prompt for email address, once in a while it stops accepting input there. But often I can get to the password screen. Once I do, I can't type anything or paste anything. This is a fresh install of Ubuntu 23.04 and I have installed all updates. Nothing in /var/crash Jun 08 11:15:59 CCW-HAL systemd[3523]: vte-spawn-8b4a59a3-a060-4bdd-92e6-285656bdb9a2.scope: Consumed 3.448s CPU time. Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:29 CCW-HAL systemd[3523]: Started app-gnome-org.gnome.Terminal-10924.scope - Application launched by gnome-shell. Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.167' (uid=1000 pid=10927 comm="/usr/bin/gnome-terminal.real" label="unconfined") Jun 08 11:16:29 CCW-HAL systemd[3523]: Starting gnome-terminal-server.service - GNOME Terminal Server... Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Successfully activated service 'org.gnome.Terminal' Jun 08 11:16:29 CCW-HAL systemd[3523]: Started gnome-terminal-server.service - GNOME Terminal Server. Jun 08 11:16:29 CCW-HAL systemd[3523]: Started vte-spawn-9cee1911-372a-4bb4-8b57-694984e43990.scope - VTE child process 10955 launched by gnome-terminal-server process 10931. Jun 08 11:16:49 CCW-HAL gnome-control-c[8079]: Error showing account: Child process exited with code 1 Jun 08 11:16:53 CCW-HAL gnome-online-accounts-panel.desktop[9764]: GLib-GIO: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - kerberosGoaBackend: activated kerberos providerGLib-GIO: _g_io_module_get_default: Found default implementation gnutls (GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialog was dismissed Jun 08 11:16:53 CCW-HAL xdg-desktop-por[3907]: Realtime error: Could not map pid: Could not determine pid namespace: Could not find instance-id in process's /.flatpak-info Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Jun 08 11:17:01 CCW-HAL CRON[11094]: (root) CMD (cd / && run-parts --report /etc/cron.hourly) Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session closed for user root Jun 08 11:17:06 CCW-HAL kernel: WebKitWebProces[11026]: segfault at 55bd22ad9adc ip 55bd22ad9adc sp 7ffd1f6adbe8 error 14 likely on CPU 2 (core 2, socket 0) Jun 08 11:17:06 CCW-HAL kernel: Code: Unable to access opcode bytes at 0x55bd22ad9ab2. Jun 08 11:17:36 CCW-HAL gnome-shell[3803]: Window manager warning: WM_TRANSIENT_FOR window 0x3a02767 for 0x3a02778 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x3a006dc. Jun 08 11:17:42 CCW-HAL systemd[1]: Starting systemd-tmpfiles-clean.service - Cleanup of Temporary Directories... Jun 08 11:17:42 CCW-HAL systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully. Jun 08 11:17:42 CCW-HAL systemd[1]: Finished systemd-tmpfiles-clean.service - Cleanup of Temporary Directories. Jun 08 11:17:42 CCW-HAL systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated successfully. Jun 08 11:18:10 CCW-HAL gnome-shell[3803]: Window manager warning: WM_TRANSIENT_FOR window 0x3a029e2 for 0x3a029f0 window override-redirect is an override-redirect window and this is not
[Touch-packages] [Bug 2023322] Re: GTK internal browser does not render with Nvidia drivers
That comment was sparked by duplicate bug 2041664 on jammy. Either it's not really a duplicate or not a sufficiently new enough revision of 2.42 to contain the fix. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/2023322 Title: GTK internal browser does not render with Nvidia drivers Status in Webkit: Confirmed Status in gnome-control-center package in Ubuntu: Invalid Status in gnome-online-accounts package in Ubuntu: Invalid Status in webkit2gtk package in Ubuntu: Fix Released Status in yelp package in Ubuntu: Invalid Status in webkit2gtk package in Debian: Fix Released Bug description: When I go into Settings > Online Accounts > Google, I get to the prompt for email address, once in a while it stops accepting input there. But often I can get to the password screen. Once I do, I can't type anything or paste anything. This is a fresh install of Ubuntu 23.04 and I have installed all updates. Nothing in /var/crash Jun 08 11:15:59 CCW-HAL systemd[3523]: vte-spawn-8b4a59a3-a060-4bdd-92e6-285656bdb9a2.scope: Consumed 3.448s CPU time. Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:29 CCW-HAL systemd[3523]: Started app-gnome-org.gnome.Terminal-10924.scope - Application launched by gnome-shell. Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.167' (uid=1000 pid=10927 comm="/usr/bin/gnome-terminal.real" label="unconfined") Jun 08 11:16:29 CCW-HAL systemd[3523]: Starting gnome-terminal-server.service - GNOME Terminal Server... Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Successfully activated service 'org.gnome.Terminal' Jun 08 11:16:29 CCW-HAL systemd[3523]: Started gnome-terminal-server.service - GNOME Terminal Server. Jun 08 11:16:29 CCW-HAL systemd[3523]: Started vte-spawn-9cee1911-372a-4bb4-8b57-694984e43990.scope - VTE child process 10955 launched by gnome-terminal-server process 10931. Jun 08 11:16:49 CCW-HAL gnome-control-c[8079]: Error showing account: Child process exited with code 1 Jun 08 11:16:53 CCW-HAL gnome-online-accounts-panel.desktop[9764]: GLib-GIO: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - kerberosGoaBackend: activated kerberos providerGLib-GIO: _g_io_module_get_default: Found default implementation gnutls (GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialog was dismissed Jun 08 11:16:53 CCW-HAL xdg-desktop-por[3907]: Realtime error: Could not map pid: Could not determine pid namespace: Could not find instance-id in process's /.flatpak-info Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Jun 08 11:17:01 CCW-HAL CRON[11094]: (root) CMD (cd / && run-parts --report /etc/cron.hourly) Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session closed for user root Jun 08 11:17:06 CCW-HAL kernel: WebKitWebProces[11026]: segfault at 55bd22ad9adc ip 55bd22ad9adc sp 7ffd1f6adbe8 error 14 likely on CPU 2 (core 2, socket 0) Jun 08 11:17:06 CCW-HAL kernel: Code: Unable to access opcode bytes at 0x55bd22ad9ab2. Jun 08 11:17:36 CCW-HAL gnome-shell[3803]: Window manager warning: WM_TRANSIENT_FOR window 0x3a02767 for 0x3a02778 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x3a006dc. Jun 08 11:17:42 CCW-HAL systemd[1]: Starting systemd-tmpfiles-clean.service - Cleanup of Temporary Directories... Jun 08 11:17:42 CCW-HAL systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully. Jun 08 11:17:42 CCW-HAL systemd[1]: Finished systemd-tmpfiles-clean.service - Cleanup of Temporary Directories. Jun 08 11:17:42 CCW-HAL systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated successfully. Jun 08 11:18:10 CCW-HAL gnome-shell[3803]: Window manager warning:
[Touch-packages] [Bug 2045705] Re: FTBFS with default Java 21
What is the recommended source/target version that should nowadays be
used?
** Also affects: apport
Importance: Undecided
Status: New
** Changed in: apport
Milestone: None => 2.28.0
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/2045705
Title:
FTBFS with default Java 21
Status in Apport:
New
Status in apport package in Ubuntu:
New
Bug description:
Dear Maintainers,
The package apport ftbfs with default Java 21.
The relevant part of the build log:
---
running build_java_subdir
warning: [options] bootstrap class path not set in conjunction with -source 7
error: Source option 7 is no longer supported. Use 8 or later.
error: Target option 7 is no longer supported. Use 8 or later.
Traceback (most recent call last):
File "/<>/setup.py", line 119, in
DistUtilsExtra.auto.setup(
File "/usr/lib/python3/dist-packages/DistUtilsExtra/auto.py", line 125, in
setup
setuptools.setup(**attrs)
File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 107, in
setup
return distutils.core.setup(**attrs)
^
File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line
185, in setup
return run_commands(dist)
^^
File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line
201, in run_commands
dist.run_commands()
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line
969, in run_commands
self.run_command(cmd)
File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1233, in
run_command
super().run_command(command)
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line
988, in run_command
cmd_obj.run()
File
"/usr/lib/python3/dist-packages/setuptools/_distutils/command/build.py", line
131, in run
self.run_command(cmd_name)
File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py", line
318, in run_command
self.distribution.run_command(command)
File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1233, in
run_command
super().run_command(command)
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line
988, in run_command
cmd_obj.run()
File "/<>/setuptools_apport/java.py", line 35, in run
subprocess.check_call(javac + glob.glob("com/ubuntu/apport/*.java"))
File "/usr/lib/python3.11/subprocess.py", line 413, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['javac', '-source', '7', '-target',
'7', 'com/ubuntu/apport/ApportUncaughtExceptionHandler.java']' returned
non-zero exit status 2.
E: pybuild pybuild:395: build: plugin distutils failed with: exit code=1:
/usr/bin/python3 setup.py build
dh_auto_build: error: pybuild --build -i python{version} -p "3.12 3.11"
returned exit code 13
make[1]: *** [debian/rules:12: override_dh_auto_build] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:4: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status
2
Build finished at 2023-12-04T07:37:06Z
---
To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/2045705/+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 2045250] Re: pam_lastlog doesn't handle localtime_r related errors properly
** Tags added: architecture-s39064 bugnameltc-204450 severity-medium
targetmilestone-inin---
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/2045250
Title:
pam_lastlog doesn't handle localtime_r related errors properly
Status in pam package in Ubuntu:
New
Status in pam package in Fedora:
Fix Released
Bug description:
The pam version(s) in Debian (checked buster) and Ubuntu (checked focal to
noble) are affected by
https://bugzilla.redhat.com/show_bug.cgi?id=2012871
Customers report a command going through PAM crashing for a given user.
A potential follow on issue can be that no ssh remote connections to an
affected server are possible anymore, esp. painful with headless systems (was
reported on a different distro).
This is caused by an issue in modules/pam_lastlog/pam_lastlog.c:
with tm = localtime_r(...) that can be NULL and needs to be handled.
There are two such cases in modules/pam_lastlog/pam_lastlog.c (here noble):
314- ll_time = last_login.ll_time;
315: if ((tm = localtime_r (_time, _buf)) != NULL) {
316- strftime (the_time, sizeof (the_time),
317- /* TRANSLATORS: "strftime options for date of last
login" */
--
574-
575- lf_time = utuser.ut_tv.tv_sec;
576: tm = localtime_r (_time, _buf);
577- strftime (the_time, sizeof (the_time),
578- /* TRANSLATORS: "strftime options for date of last login" */
Case 1 (line 315) is properly handled, but not case 2 (line 576).
The second case got fixed by:
https://github.com/linux-pam/linux-pam/commit/40c271164dbcebfc5304d0537a42fb42e6b6803c
This fix should be included in Ubuntu (and Debian).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2045250/+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 2045705] [NEW] FTBFS with default Java 21
Public bug reported:
Dear Maintainers,
The package apport ftbfs with default Java 21.
The relevant part of the build log:
---
running build_java_subdir
warning: [options] bootstrap class path not set in conjunction with -source 7
error: Source option 7 is no longer supported. Use 8 or later.
error: Target option 7 is no longer supported. Use 8 or later.
Traceback (most recent call last):
File "/<>/setup.py", line 119, in
DistUtilsExtra.auto.setup(
File "/usr/lib/python3/dist-packages/DistUtilsExtra/auto.py", line 125, in
setup
setuptools.setup(**attrs)
File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 107, in
setup
return distutils.core.setup(**attrs)
^
File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line
185, in setup
return run_commands(dist)
^^
File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line
201, in run_commands
dist.run_commands()
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line
969, in run_commands
self.run_command(cmd)
File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1233, in
run_command
super().run_command(command)
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line
988, in run_command
cmd_obj.run()
File "/usr/lib/python3/dist-packages/setuptools/_distutils/command/build.py",
line 131, in run
self.run_command(cmd_name)
File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py", line 318,
in run_command
self.distribution.run_command(command)
File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1233, in
run_command
super().run_command(command)
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line
988, in run_command
cmd_obj.run()
File "/<>/setuptools_apport/java.py", line 35, in run
subprocess.check_call(javac + glob.glob("com/ubuntu/apport/*.java"))
File "/usr/lib/python3.11/subprocess.py", line 413, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['javac', '-source', '7', '-target',
'7', 'com/ubuntu/apport/ApportUncaughtExceptionHandler.java']' returned
non-zero exit status 2.
E: pybuild pybuild:395: build: plugin distutils failed with: exit code=1:
/usr/bin/python3 setup.py build
dh_auto_build: error: pybuild --build -i python{version} -p "3.12 3.11"
returned exit code 13
make[1]: *** [debian/rules:12: override_dh_auto_build] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:4: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
Build finished at 2023-12-04T07:37:06Z
---
** Affects: apport (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/2045705
Title:
FTBFS with default Java 21
Status in apport package in Ubuntu:
New
Bug description:
Dear Maintainers,
The package apport ftbfs with default Java 21.
The relevant part of the build log:
---
running build_java_subdir
warning: [options] bootstrap class path not set in conjunction with -source 7
error: Source option 7 is no longer supported. Use 8 or later.
error: Target option 7 is no longer supported. Use 8 or later.
Traceback (most recent call last):
File "/<>/setup.py", line 119, in
DistUtilsExtra.auto.setup(
File "/usr/lib/python3/dist-packages/DistUtilsExtra/auto.py", line 125, in
setup
setuptools.setup(**attrs)
File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 107, in
setup
return distutils.core.setup(**attrs)
^
File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line
185, in setup
return run_commands(dist)
^^
File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line
201, in run_commands
dist.run_commands()
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line
969, in run_commands
self.run_command(cmd)
File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1233, in
run_command
super().run_command(command)
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line
988, in run_command
cmd_obj.run()
File
"/usr/lib/python3/dist-packages/setuptools/_distutils/command/build.py", line
131, in run
self.run_command(cmd_name)
File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py", line
318, in run_command
self.distribution.run_command(command)
File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1233, in
run_command
[Touch-packages] [Bug 1380110] Re: comments inside parentheses mess up the syntax coloring of shell script
laurent@laurent-GL73-8SD:~$ vim --version VIM - Vi IMproved 9.0 (2022 Jun 28, compilé Oct 16 2023 18:21:01) Rustines incluses : 1-1672, 1840, 1846-1848, 1857-1858, 1873, 1969, 1992, 2010 Modifié par team+...@tracker.debian.org Compilé par team+...@tracker.debian.org Énorme version sans interface graphique. Fonctionnalités incluses (+) ou non (-) : +acl +file_in_path +mouse_urxvt -tag_any_white +arabic+find_in_path +mouse_xterm -tcl +autocmd +float +multi_byte+termguicolors +autochdir +folding +multi_lang+terminal -autoservername-footer-mzscheme +terminfo -balloon_eval +fork()+netbeans_intg +termresponse +balloon_eval_term +gettext +num64 +textobjects -browse-hangul_input +packages +textprop ++builtin_terms+iconv +path_extra+timers +byte_offset +insert_expand -perl +title +channel +ipv6 +persistent_undo -toolbar +cindent +job +popupwin +user_commands -clientserver +jumplist +postscript+vartabs -clipboard +keymap+printer +vertsplit +cmdline_compl +lambda+profile +vim9script +cmdline_hist +langmap -python+viminfo +cmdline_info +libcall +python3 +virtualedit +comments +linebreak +quickfix +visual +conceal +lispindent+reltime +visualextra +cryptv+listcmds +rightleft +vreplace +cscope+localmap -ruby +wildignore +cursorbind-lua +scrollbind+wildmenu +cursorshape +menu +signs +windows +dialog_con+mksession +smartindent +writebackup +diff +modify_fname +sodium-X11 +digraphs +mouse -sound -xfontset -dnd -mouseshape+spell -xim -ebcdic+mouse_dec +startuptime -xpm +emacs_tags+mouse_gpm +statusline-xsmp +eval -mouse_jsbterm -sun_workshop -xterm_clipboard +ex_extra +mouse_netterm +syntax-xterm_save +extra_search +mouse_sgr +tag_binary -farsi -mouse_sysmouse-tag_old_static fichier vimrc système : "/etc/vim/vimrc" fichier vimrc utilisateur : "$HOME/.vimrc" 2e fichier vimrc utilisateur : "~/.vim/vimrc" fichier exrc utilisateur : "$HOME/.exrc" fichier de valeurs par défaut : "$VIMRUNTIME/defaults.vim" $VIM par défaut : "/usr/share/vim" Compilation : gcc -c -I. -Iproto -DHAVE_CONFIG_H -Wdate-time -g -O2 -ffile-prefix-map=/build/vim-itVrJX/vim-9.0.1672=. -flto=auto -ffat-lto-objects -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -fdebug-prefix-map=/build/vim-itVrJX/vim-9.0.1672=/usr/src/vim-2:9.0.1672-1ubuntu2.1 -DSYS_VIMRC_FILE=\"/etc/vim/vimrc\" -DSYS_GVIMRC_FILE=\"/etc/vim/gvimrc\" -D_REENTRANT -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 Édition de liens : gcc -Wl,-Bsymbolic-functions -flto=auto -ffat-lto-objects -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -o vim -lm -ltinfo -lselinux -lsodium -lacl -lattr -lgpm -L/usr/lib/python3.11/config-3.11-x86_64-linux-gnu -lpython3.11 -ldl -lm laurent@laurent-GL73-8SD:~$ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1380110 Title: comments inside parentheses mess up the syntax coloring of shell script Status in vim package in Ubuntu: New Bug description: Hi, I've found the following bug with syntax coloring of shell scripts in vi and vim. If you add comments outside parenthesis, it works fine. But if you add comments inside parenthesis, or worse comments with quotes, the syntax coloring is totally messed up. I join a sample shell script to demonstrate the bug. Best regards, Laurent Lyaudet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1380110/+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 1380110] Re: comments inside parentheses mess up the syntax coloring of shell script
Hello Paul :), The bug is still here as can be seen in the screenshot I just took and attached to this comment. I just downloaded the "sample script to reproduce the bug" I attached 9 years ago and opened it with Vim on my laptop. You can see that the commands inside parentheses are white instead of yellow and that "test" in "test.txt" is yellow. Below are the informations regarding Vim version. It is the latest one given with Mantic Minotaur. Best regards, Laurent Lyaudet ** Attachment added: "Bug still here in 2023" https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1380110/+attachment/5726518/+files/Capture%20d%E2%80%99%C3%A9cran%20du%202023-12-05%2022-45-04.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1380110 Title: comments inside parentheses mess up the syntax coloring of shell script Status in vim package in Ubuntu: New Bug description: Hi, I've found the following bug with syntax coloring of shell scripts in vi and vim. If you add comments outside parenthesis, it works fine. But if you add comments inside parenthesis, or worse comments with quotes, the syntax coloring is totally messed up. I join a sample shell script to demonstrate the bug. Best regards, Laurent Lyaudet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1380110/+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 1380110] Re: comments inside parentheses mess up the syntax coloring of shell script
** Changed in: vim (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1380110 Title: comments inside parentheses mess up the syntax coloring of shell script Status in vim package in Ubuntu: New Bug description: Hi, I've found the following bug with syntax coloring of shell scripts in vi and vim. If you add comments outside parenthesis, it works fine. But if you add comments inside parenthesis, or worse comments with quotes, the syntax coloring is totally messed up. I join a sample shell script to demonstrate the bug. Best regards, Laurent Lyaudet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1380110/+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 2043234] Re: Symlink for resolv.conf is wrong on fresh install
This symlink looks correct to me. If you are still having an issue, please provide a specific example and instructions on how to reproduce it in another bug report. ** Changed in: systemd (Ubuntu) Status: Confirmed => Invalid -- 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/2043234 Title: Symlink for resolv.conf is wrong on fresh install Status in systemd package in Ubuntu: Invalid Bug description: Hello. Sorry for disturb, may I ask you please to confirm if im not doing anything wrong with new installation? Its being a while since the problem exists AT LEAST IN MY CASE with "faulty path" for symlinc at resolv.conf I believe its keep happening since 18.04 version and even now in 22.04 So, in the fresh install the path looks like this: lrwxrwxrwx 1 root root 39 Feb 17 2023 resolv.conf -> ../run/systemd/resolve/stub-resolv.conf but once im running : sudo ln -sf /run/systemd/resolve/resolv.conf /etc/resolv.conf everything works fine. By everything I mean when I run nslookup. Regards, Vitalii Sharapov To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2043234/+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 886450] Re: Gvim hangs with blank window if not maximized
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 11.10 (oneiric) reached end-of-life on May 9, 2013. The bug description implies that this isn't a vim bug as emacs is also affected and and comment #16 implies the issue is theme related. As almost 12 years have passed without any comment I'll close this as 'Invalid'. ** Changed in: vim (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/886450 Title: Gvim hangs with blank window if not maximized Status in vim package in Ubuntu: Invalid Bug description: If gvim is opened not maximized, it simply hangs without showing any content of the file (or the standard content ~s for new file). However, if it is maximized, it works. Again if gvim is unmaximized, it freezes the window content. I tried with removing .vimrc file and .vim directory. Same behavior persists. I tried with removing .gnome2/Vim file and calling /usr/bin/gvim -f. But same problem. However, I think it may not be a problem in Gvim because the same frozen window behavior happens for emacs. However, this problem is not there with gedit. I did not know how to file bug with the window management software, so i invoked "ubuntu-bug vim" from command window. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: vim (not installed) ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6 Uname: Linux 3.0.0-13-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Sat Nov 5 11:18:16 2011 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) ProcEnviron: LANGUAGE=en PATH=(custom, user) LANG=en_US.UTF-8 LC_MESSAGES=en_US.UTF-8 SHELL=/bin/bash SourcePackage: vim UpgradeStatus: Upgraded to oneiric on 2011-10-18 (18 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/886450/+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 1417978] Re: vim improperly displaying text when loaded in gnome-terminal with altered geometry
Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019. Issue never confirmed by another user. Reporter's account has been deactivated so closing. ** Changed in: vim (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1417978 Title: vim improperly displaying text when loaded in gnome-terminal with altered geometry Status in vim package in Ubuntu: Invalid Bug description: I use the following command to load vi(m) in a new gnome-terminal window with altered geometry: gnome-terminal --geometry 156x48+80+50 -e "/usr/bin/vi .bashrc" About 60% of the time, when I do this, it loads the text within vim as follows: 1. The top line of text seems to be the next line after the line of text that would have been displayed as the last line had I started vim in the default sized gnome-terminal window 2. After what seems to be the text normally displayed below that offset, after what seems to be the number of lines displayed as if it were in a default sized gnome-terminal window, the remaining lines are blank 3. The only way to correct the display is to scroll down until a full screen of text is normally displayed in vi(m), then everything starts working normally Note that this behavior happens only around 60-70% of the time - sometimes, issuing the command will work correctly, sometimes as described above. It is very repeatable though on my machine. This behavior happens on my native Ubuntu 14.04 box as well as on my 14.04.1 box within a virtual machine under Windows 8.1 (both for hyper-v and vmware) The reason I think it may be vim, not gnome-terminal, is that nano, irssi and the man pages all work fine every time when I issue the same command but substitute them inside the quotes above. * EDIT Further investigation may seem to point to vte3 (libvte). Looking at vte.c in the Gnome vte3 (libvte) source code from their git repo, the default number of lines for a terminal is hardcoded to be 24 lines and the terminal widget appears to be set to this size during the call to vte_terminal_init(). This is the same number of lines displayed before starting the blank lines going to the bottom of vim within the gnome-terminal ** End EDIT * ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: vim-tiny 2:7.4.052-1ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: Unity Date: Wed Feb 4 02:35:03 2015 ExecutablePath: /usr/bin/vim.tiny InstallationDate: Installed on 2015-02-02 (1 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: vim UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1417978/+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 1179722] Re: :help word[CTRL-D] doesn't search help
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 12.04 (precise) reached end-of-life on April 28, 2017. Looking at this bug report in 2023 I can't reproduce the reported problem using either Ubuntu 20.04 or 22.04. As the issue was never confirmed by another user and there have been no comments for over 10 years I'll mark it as being 'Invalid'. A local configuration problem? ** Changed in: vim (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1179722 Title: :help word[CTRL-D] doesn't search help Status in vim package in Ubuntu: Invalid Bug description: I launch vim by typing it's name. Inside vim I type :help word[CTRL-D] EXPECTED RESULT: search the vim documentation ACTUAL RESULT: I get the : command history The CTRL-D sequence is described in the :help help file. This is a very important feature for me and I suspect other vim users. This problem does not exist on 10.04. WORKAROUND: tab key instead of CTRL-D, but this isn't mentioned in the documentation. I can start vim either in a gnome-terminal with or without byobu running screen, I can also start via a virtual terminal by pressing ctrl-alt-F2 and I get the same result. All three entries of vim :set term?. vim :echo $TERM and vim :!echo $TERM are consistent in both cases, as screen in the first case and linux in the second case. With all three in agreement there is only the vim configuration left for interpreting the following command, right? ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: vim 2:7.3.429-2ubuntu2.1 ProcVersionSignature: Ubuntu 3.2.0-41.66-generic 3.2.42 Uname: Linux 3.2.0-41-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.0.1-0ubuntu17.2 Architecture: amd64 Date: Mon May 13 16:10:08 2013 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120315) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: vim UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1179722/+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 1772050] Re: 't' and 'T' command used in vi editor is not working its working only for first occurrence of character.
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 while 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: vim (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1772050 Title: 't' and 'T' command used in vi editor is not working its working only for first occurrence of character. Status in vim package in Ubuntu: Incomplete Bug description: 't' and 'T' command used in vi editor is not working its working only for first occurrence of character. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.14 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Fri May 18 20:28:09 2018 InstallationDate: Installed on 2018-05-17 (1 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1772050/+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 1393596] Re: Extreme slow syntax highlighting for Windows Registry Files
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. However, no Ubuntu version or flavour information has been given and as there has been no comment on the bug report for over nine years I'm closing this as being an invalid report. If this is still an issue while using a currently supported release of Ubuntu then please revert the bug status to 'New' and run the following command in a terminal: apport-collect 1393596 Thank you. ** Changed in: vim (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1393596 Title: Extreme slow syntax highlighting for Windows Registry Files Status in vim package in Ubuntu: Invalid Bug description: If exported Windows Registry Information is opened in vim, an very simple, but apropriate syntax highlighting is enabled. However, on any longer block of ASCII hex representation (and usual Registry data has a lot of that trash) the text rendering gets extremely slow, hugging CPU and make scrolling almost impossible. The simple scheme of marking keys and there values should not need such complex parsing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1393596/+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 1745902] Re: gvim will freeze when partial window is out of current desktop using Wayland
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 17.10 (artful) reached end-of-life on July 19, 2018. 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 while 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: vim (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1745902 Title: gvim will freeze when partial window is out of current desktop using Wayland Status in vim package in Ubuntu: Incomplete Bug description: Reproduce Steps: 0. Login ubuntu 17.10 using Wayland 1. Open Gvim 2. Move Gvim window to partially out of current desktop 3. Press i to change current mode to insert mode <- problem 4. Input some chars and new lines 5. Press ESC to return to normal mode 6. Press j or k to move cursor <- problem The problem is: gvim window will freeze unless: 1. you move your mouse 2. wait a few seconds ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: vim-gtk 2:8.0.0197-4ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 29 10:43:36 2018 InstallationDate: Installed on 2016-04-24 (644 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: vim UpgradeStatus: Upgraded to artful on 2017-10-23 (98 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1745902/+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 1499899] Re: Gvim displays lots of scary messages about UNITY_GTK_IS_MENU_SHELL
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.10 (wily) reached end-of-life on July 28, 2016. 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 while 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: vim (Ubuntu) Assignee: Lee moonhyoung (eobeauti2) => (unassigned) ** Changed in: unity (Ubuntu) Status: New => Incomplete ** Changed in: vim (Ubuntu) Status: Confirmed => Incomplete ** Changed in: unity Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1499899 Title: Gvim displays lots of scary messages about UNITY_GTK_IS_MENU_SHELL Status in Unity: Incomplete Status in unity package in Ubuntu: Incomplete Status in vim package in Ubuntu: Incomplete Bug description: When launched from a terminal the widely used text editor gvim displays lots WARNING and CRITICAL messages such as: ** (gvim:3608): WARNING **: (../../../lib/unity-gtk-menu- shell.c:176):unity_gtk_menu_shell_show_item: code should not be reached ** (gvim:3608): CRITICAL **: unity_gtk_menu_shell_handle_item_notify: assertion 'UNITY_GTK_IS_MENU_SHELL (shell)' failed This did not happen in 15.04. It is a most embarrassing bug. Gvim is an essential tool for many users. I am using Ubuntu 15.10 Beta 2. $ lsb_release -rd Description: Ubuntu Wily Werewolf (development branch) Release: 15.10 $ apt-cache policy vim-gnome vim-gnome: Installed: 2:7.4.712-2ubuntu3 Candidate: 2:7.4.712-2ubuntu3 Version table: *** 2:7.4.712-2ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ wily/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy vim-gtk vim-gtk: Installed: 2:7.4.712-2ubuntu3 Candidate: 2:7.4.712-2ubuntu3 Version table: *** 2:7.4.712-2ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ wily/universe amd64 Packages 100 /var/lib/dpkg/status I expected to be able to use Gvim. Now Gvim pollutes the terminal with scary messages, and disturbs the messages shown by other programs running in the terminal. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: vim-gnome 2:7.4.712-2ubuntu3 ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1 Uname: Linux 4.2.0-11-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Sep 26 00:40:37 2015 InstallationDate: Installed on 2015-09-25 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) SourcePackage: vim UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1499899/+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 1721280] Re: vim.gtk3 crashed with SIGSEGV in __new_sem_wait_fast()
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 17.10 (artful) reached end-of-life on July 19, 2018. 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 while 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: vim (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1721280 Title: vim.gtk3 crashed with SIGSEGV in __new_sem_wait_fast() Status in vim package in Ubuntu: Incomplete Bug description: Might be related to one of my extensions camelcasemotion lightline.vim vim-fetch inorirust.vim validator.vim vim-fugitive Please also double check that it's not a duplicate of #96263 "vim crashed with sigsegv" ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: vim-gtk3 2:8.0.0197-4ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Oct 4 16:13:33 2017 ExecutablePath: /usr/bin/vim.gtk3 InstallationDate: Installed on 2017-05-30 (127 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. ProcCmdline: vim update_test_projects.sh Signal: 11 SourcePackage: vim StacktraceTop: kill () at ../sysdeps/unix/syscall-template.S:84 mch_exit () getout () () at /lib/x86_64-linux-gnu/libpthread.so.0 __new_sem_wait_fast (definitive_result=0, sem=0x0) at sem_waitcommon.c:135 Title: vim.gtk3 crashed with SIGSEGV in kill() UpgradeStatus: Upgraded to artful on 2017-09-25 (8 days ago) UserGroups: dialout plugdev sudo wireshark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1721280/+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 293331] Re: vim-gnome mousewheel/scrollbar strange behavior
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 8.04 (hardy) reached end-of-life on May 12, 2011. 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 while 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: vim (Ubuntu) Status: New => Incomplete ** Tags added: hardy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/293331 Title: vim-gnome mousewheel/scrollbar strange behavior Status in vim package in Ubuntu: Incomplete Bug description: Binary package hint: vim-gnome 8.04 x86 and amd64 under gnome, run gvim and open a file or create text that has more lines than are shown. when hovering the mouse over the up and down buttons on the scrollbar and using the mouse scroll wheel, the bar moves according to the scroll wheel but the text moves as if you had pressed the scroll button with a left mouse click. i expect it to scroll as it would if i had the mouse over the text and used the mouse scroll wheel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/293331/+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 560157] Re: vim-gtk, vim-gnome menu_bar error
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 10.04 (lucid) reached end-of-life on May 9, 2013. 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 while 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: vim (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/560157 Title: vim-gtk,vim-gnome menu_bar error Status in vim package in Ubuntu: Incomplete Bug description: Binary package hint: vim vim-gtk,vim-gnome menu_bar error, only the item was show in the menu bar. Others have no context. but, export LANG=xxx can solve the problem. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: vim-gnome 2:7.2.330-1ubuntu2 ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1 Uname: Linux 2.6.32-19-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Sun Apr 11 01:12:41 2010 ExecutablePath: /usr/bin/vim.gnome InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318) ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=zh_CN.utf8 LANGUAGE=zh_CN:zh SourcePackage: vim To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/560157/+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 627332] Re: Scroll bars do not appear correctly on new splits
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 10.04 (lucid) reached end-of-life on May 9, 2013. 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 while 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: vim (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/627332 Title: Scroll bars do not appear correctly on new splits Status in vim package in Ubuntu: Incomplete Bug description: Binary package hint: vim-gnome vim-gnome 2:7.2.330-1ubuntu3 ubuntu 10.04.1 LTS Easiest steps to reproduce: - Open gvim - Maximise (currently reproduced under Compiz - not tried without) - Open a file with more lines than available. - :vsp Expected behaviour: New split has a scrollbar on the right Actual behaviour: Scrollbar exists, but appears to be attached to the outside of the maximised window, and thus not visible. Workaround: Restore gvim and maximise again. This is how it should originally have displayed. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: vim-gnome 2:7.2.330-1ubuntu3 ProcVersionSignature: Ubuntu 2.6.32-24.41-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-generic i686 NonfreeKernelModules: fglrx Architecture: i386 Date: Tue Aug 31 11:06:43 2010 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100427.1) ProcEnviron: PATH=(custom, user) LANG=en_GB.utf8 SHELL=/bin/bash SourcePackage: vim To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/627332/+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 778485] Re: Add nginx syntax to the default vim package
Looking at my 'jammy' installation I see that nginx.vim is installed in /usr/share/vim/vim82/syntax so I'm closing this report as being fixed. ** Changed in: vim (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/778485 Title: Add nginx syntax to the default vim package Status in vim package in Ubuntu: Fix Released Bug description: Binary package hint: vim Could you add the nginx.vim into the syntax directory and add the appropriate line into the filetype.vim ? Here are all you need : http://www.vim.org/scripts/script.php?script_id=1886 Thank you, ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: vim-runtime 2:7.3.035+hg~8fdc1210-1ubuntu7 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 Architecture: amd64 Date: Fri May 6 14:56:45 2011 Dependencies: InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: vim UpgradeStatus: Upgraded to natty on 2011-04-29 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/778485/+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 2028082] Re: Update glib to 2.76.4
This bug was fixed in the package glib2.0 - 2.76.4-0ubuntu1 --- glib2.0 (2.76.4-0ubuntu1) lunar; urgency=medium * New upstream release (LP: #2028082) -- Jeremy Bícha Tue, 18 Jul 2023 15:39:46 -0400 ** Changed in: glib2.0 (Ubuntu Lunar) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2028082 Title: Update glib to 2.76.4 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Lunar: Fix Released Bug description: Impact -- There is a new bugfix release in the stable 2.76 series The current release in Ubuntu 23.04 is 2.76.1 https://gitlab.gnome.org/GNOME/glib/-/blob/2.76.4/NEWS Test Case 1 --- glib has an extensive test suite. Failing tests will fail the build. This update will also trigger a lot of autopkgtests. Ensure that there aren't autopkgtest regressions triggered by this update and that the builds complete successfully Test Case 2 --- Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. If you reboot the machine and can get to the desktop, that's already tested GLib extensively. But also run applications like the terminal, the file browser and epiphany-browser What Could Go Wrong --- This update contains fixes in multiple places so multiple apps could be affected. The consequences of a broken GLib can range from some functions returning bad results sometimes, which have minimal runtime implications, up to the system simply crashing all the time. Other Info -- The upstream gnome-remote-desktop maintainer requested that we do this update to fix a frequent gnome-remote-desktop crash that shows on errors.ubuntu.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2028082/+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 2028082] Update Released
The verification of the Stable Release Update for glib2.0 has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2028082 Title: Update glib to 2.76.4 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Lunar: Fix Released Bug description: Impact -- There is a new bugfix release in the stable 2.76 series The current release in Ubuntu 23.04 is 2.76.1 https://gitlab.gnome.org/GNOME/glib/-/blob/2.76.4/NEWS Test Case 1 --- glib has an extensive test suite. Failing tests will fail the build. This update will also trigger a lot of autopkgtests. Ensure that there aren't autopkgtest regressions triggered by this update and that the builds complete successfully Test Case 2 --- Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. If you reboot the machine and can get to the desktop, that's already tested GLib extensively. But also run applications like the terminal, the file browser and epiphany-browser What Could Go Wrong --- This update contains fixes in multiple places so multiple apps could be affected. The consequences of a broken GLib can range from some functions returning bad results sometimes, which have minimal runtime implications, up to the system simply crashing all the time. Other Info -- The upstream gnome-remote-desktop maintainer requested that we do this update to fix a frequent gnome-remote-desktop crash that shows on errors.ubuntu.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2028082/+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 1965439] Re: [SRU] kdesu fails to authenticate with sudo from Jammy
It's working fine for me in Kubuntu 22.04 LTS now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1965439 Title: [SRU] kdesu fails to authenticate with sudo from Jammy Status in kdesu package in Ubuntu: Fix Released Status in kubuntu-settings package in Ubuntu: Fix Released Status in sudo package in Ubuntu: Won't Fix Status in ubuntustudio-default-settings package in Ubuntu: Fix Released Status in kdesu source package in Jammy: Fix Released Status in kubuntu-settings source package in Jammy: In Progress Status in sudo source package in Jammy: Won't Fix Status in ubuntustudio-default-settings source package in Jammy: Fix Released Status in kdesu source package in Kinetic: Fix Released Status in kubuntu-settings source package in Kinetic: Fix Released Status in sudo source package in Kinetic: Won't Fix Status in ubuntustudio-default-settings source package in Kinetic: Fix Released Status in kdesu package in Debian: Fix Released Bug description: kdesu fails to authenticate with sudo from Jammy. See upstream bug: KDE bug: https://bugs.kde.org/show_bug.cgi?id=452532 Examples: Launch Kubuntu driver manager from system setting, launching ksystemlog from the main menu, or trying to run krusader root mode option via its 'Tools > Start Krusader Root Mode' menu entry. Assuming that the current user is a member of the sudo group. On entering the correct password authentication is refused, stating that possibly an incorrect password has been entered. It appears that kdesu fails to cope with the sudo config change in this commit: https://salsa.debian.org/sudo- team/sudo/-/commit/59db341d46aa4c26b54c1270e69f2562e7f3d751 kdesu was fixed in Debian with: https://tracker.debian.org/news/1330116/accepted-kdesu-5940-2-source- into-unstable/ and fixed in kinetic with: https://launchpad.net/ubuntu/+source/kdesu/5.94.0-0ubuntu2 The issue can be worked around by adding /etc/sudoers.d/kdesu-sudoers with the contents Defaults!/usr/lib/*/libexec/kf5/kdesu_stub !use_pty [Impact] * Users are unable to authenticate to and launch applications via kdesu. * This should be backported to restore functionality that users expect. [Test Plan] * Launch Kubuntu driver manager from system setting, launching ksystemlog from the main menu, or trying to run krusader root mode option via its 'Tools > Start Krusader Root Mode' menu entry. Assuming that the current user is a member of the sudo group. * Confirm that the application authentcate and launch as successfully as in previous releases. [Where problems could occur] * While this update only returns sudo to its default behaviour (used in previous releases and virtually all other distributions) for kdesu, care should be taken to test some other applications that seek root permissions to confirm that no unexpected consequences occur. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdesu/+bug/1965439/+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 1785813] Re: gvim crashes when clicking on manager to shade the window
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 18.04 (bionic) reached end-of-standard-support on May 31, 2023. and the Xubuntu flavour around two years earlier in 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 while using a currently maintained release of Xubuntu then please let us know which one(s) otherwise this bug report can be left to expire in approximately 60 days time. ** Changed in: vim (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1785813 Title: gvim crashes when clicking on manager to shade the window Status in vim package in Ubuntu: Incomplete Bug description: I am running xubuntu 18.04 and when I click the "shade" button of gvim frame the window disappears with gvim crashing. It happens only to gvim all other windows I've tested are ok ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: vim-gtk3 2:8.0.1453-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Aug 7 14:08:10 2018 InstallationDate: Installed on 2017-11-02 (278 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) SourcePackage: vim UpgradeStatus: Upgraded to bionic on 2018-04-30 (99 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1785813/+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 1144487] Re: package vim 2:7.3.429-2ubuntu2.1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 2
*** This bug is a duplicate of bug 1144486 *** https://bugs.launchpad.net/bugs/1144486 ** This bug has been marked a duplicate of bug 1144486 package vim-gnome 2:7.3.429-2ubuntu2.1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1144487 Title: package vim 2:7.3.429-2ubuntu2.1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 2 Status in vim package in Ubuntu: Confirmed Bug description: 2013-04-03 No install vim packege and failed update. ProblemType: Package DistroRelease: Ubuntu 12.04 Package: vim 2:7.3.429-2ubuntu2.1 ProcVersionSignature: Ubuntu 3.0.0-31.48-generic 3.0.61 Uname: Linux 3.0.0-31-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 Date: Mon Mar 4 11:15:45 2013 ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 2 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MarkForUpload: True SourcePackage: vim Title: package vim 2:7.3.429-2ubuntu2.1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: Upgraded to precise on 2013-03-04 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1144487/+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 1394891] Re: evim search fails with message: "E486: Pattern not found: \\/\c" followed by the string searched for
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. If this is still an issue while 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: vim (Ubuntu) Status: New => Incomplete ** Tags added: trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1394891 Title: evim search fails with message: "E486: Pattern not found: \\/\c" followed by the string searched for Status in vim package in Ubuntu: Incomplete Bug description: Ubuntu Trusty 64 bit system built from the mini.iso with Openbox as the WM and sole DE as well. Vim version 2:7.4.052-1ubuntu3. Recently, search has started failing about half the time. In Evim, if I search for "some string that IS there somewhere" I'll get the following message: E486: Pattern not found: \\/\csome string that IS there somewhere as if it had prepended some stuff to what I what I wanted to search for and searched for that instead. Whenever it does this it is always the same string that gets prepended: \\/\c Seems the longer the string the more likely it is to happen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1394891/+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 253576] Re: Buffer content is lost when opening file over network that doesn't exsist
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 8.04 (hardy) reached end-of-life on May 12, 2011. 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 while 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. ** Tags added: hardy ** Changed in: vim (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/253576 Title: Buffer content is lost when opening file over network that doesn't exsist Status in vim package in Ubuntu: Incomplete Bug description: Binary package hint: vim I'm using VIM 7.1.138 (netrw v109) on Ubuntu 8.04. The fastest way to see this bug happening seems to be this: 1) Start vim, type :e ftp://u...@domain.xxx//path/to/existing/file 2) Enter the password - file content appears in the buffer. 3) Type :w 4) Type :sp ftp://u...@domain.xxx//path/to/NOT/existing/file What happens after this is: 1) 2 new buffers are opened: the first one says '/path/to/NOT/existing/file: No such file or directory', and the second is the buffer for that file. You can edit that buffer and save it, so a new file is created on the server. 2) The old buffer which had the contents of ftp://u...@domain.xxx//path/to/existing/file is empty. I expect that the second consequence above is a bug. If I was in a middle of editing in one buffer and opened another which would create a new file, all my work on the first one is lost - it's impossible to undo any changes, it says 'Already at oldest change', and the old buffer is cleared and not saved on the server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/253576/+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 808941] Re: gvim in ubuntu is slow when switching tabs or navigating lines
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 11.04 (natty) reached end-of-life on October 28, 2012. 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 while 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: vim (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/808941 Title: gvim in ubuntu is slow when switching tabs or navigating lines Status in vim package in Ubuntu: Incomplete Bug description: It's been like this forever really. Because I worked both on Ubuntu and MacOSX interchangeably I didn't care as much. Now I think maybe it's time to finally find out what is wrong with it. THE PROBLEM: when I switch tabs or navigate the lines with arrows or J,K keys and when I do it repeatedly (as if when trying to find the right tab holding Ctrl and hitting Tab) it seems to be delaying the action. When I stop hitting the keys gvim may still be finishing the operations (for instance, I stop hitting Ctrl+Tab, gvim may switch 5 more tabs - the number depends on how long I've been hitting Ctrl+Tab - before it stops). MacVim with similar settings in .vimrc works just fine. The delays are present both when Compiz is turned off and turned on. Any ideas? ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: vim-gnome 2:7.3.035+hg~8fdc1210-1ubuntu7 ProcVersionSignature: Ubuntu 2.6.39-0.5~20110427-generic 2.6.39-rc5 Uname: Linux 2.6.39-0-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon Jul 11 22:24:32 2011 ExecutablePath: /usr/bin/vim.gnome ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: vim UpgradeStatus: Upgraded to natty on 2011-06-05 (36 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/808941/+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 320700] Re: gvim rendering is slow
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. 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 while 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: vim (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/320700 Title: gvim rendering is slow Status in vim package in Ubuntu: Incomplete Bug description: Binary package hint: vim Rendering in gvim is very slow compared to previous Ubuntu releases. It's usable, but takes patience. I'm using vim/gvim 7.1.314-3ubuntu3.1 on Ubuntu 8.10. Others have reported this same issue on a thread from the vim mailing list. Many solutions have been tried w/o success: http://groups.google.com/group/vim_use/browse_thread/thread/dd1d8d9a799adf4a From the thread, someone provided this benchmark script: -- -- -- " Benchmark vim's redrawing speed let i = 0 while i < 2000 1 redraw $ redraw let i = i + 1 endwhile qa! -- -- -- I've run it with /etc/init.d/README as an input file (just to pick something consistent across Ubuntu machines): $ time vim -u NONE -U NONE -S test-redraw-speed.vim /etc/init.d/README real 0m5.407s user 0m0.568s sys 0m0.048s $ time gvim -u NONE -U NONE -f -S test-redraw-speed.vim /etc/init.d/README real 3m27.614s user 0m11.685s sys 0m0.312s As you can see gvim is almost 40x slower then vim (running in gnome- terminal). You'd expect gvim to be slower then vim, but not by this much. Note, from the thread, not all users experience this huge difference. Some only report 2-3x slowdown, which I'd be very happy with at this point :) I'm using the radeon X11 driver (open source) on a ThinkPad T42p, and do _not_ experience slow rendering in other apps (for example, gedit). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/320700/+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 788481] Re: Unity can't handle two GVIM's at the same time
** Changed in: vim (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/788481 Title: Unity can't handle two GVIM's at the same time Status in vim package in Ubuntu: Incomplete Bug description: Binary package hint: vim When I open two gvim's at the same time (from the command prompt), only one of them has a global menu, the other does not. This is not a duplicate of: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/781180 As I see no warnings. Just the first menu works, and the second GVIM has no menu. Which also means copy & paste between gvims using menu shortcuts is broken :( SInce only one instance has a menu... Alt+E 'C' is probably one of the most common things I do with two gvims open... Take care, -stu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/788481/+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 617841] Re: Gvim 7.2 paste into OpenOffice 3.2.0 fails
Thank you for reporting this bug to Ubuntu. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. Ubuntu 10.10 (maverick) reached end-of-life on April 10, 2012. Ubuntu 10.04 (lucid) reached end-of-life on May 9, 2013. This issue may well have been fixed sometime during the 12+ years since it was reported but as OpenOffice is no longer part of the Ubuntu distribution I'm closing this as 'Invalid'. FWIW, I can copy from GVim 8.2 and paste into LibreOffice Writer 7.3 (in Ubuntu 22.04). ** Changed in: vim (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/617841 Title: Gvim 7.2 paste into OpenOffice 3.2.0 fails Status in vim package in Ubuntu: Invalid Bug description: Binary package hint: vim Copying something from Gvim, either using the X clipboard or the menu commands, and then pasting it into OpenOffice, fails with the error "Requested clipboard format is not available". This behavior also happens with other programs such as Lotus Notes. As a workaround, using Paste Special and selecting plain text format (not HTML) will successfully paste the text. Alternatively, setting the following option in vim/vimrc prior to copying will also work: :set cb=autoselect,html,exclude:cons\|linux This bug was introduced in vim 7.2.201 and corrected in 7.2.442 (see http://ftp.vim.org/pub/vim/patches/7.2/README) Given the LTS status of Ubuntu 10.04 this fix should be trickled down to it since it affects basic functionality of Gvim. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: vim-common 2:7.2.330-1ubuntu3 ProcVersionSignature: Ubuntu 2.6.32-24.39-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Sat Aug 14 14:53:03 2010 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) LANG=en_GB.utf8 SHELL=/bin/zsh SourcePackage: vim To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/617841/+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 2045570] Re: dnsmasq crash when no servers in resolv.conf
Thanks for taking the time to report this bug and trying to make Ubuntu better. Also thanks for the pointers. According to the upstream discussion this is the needed fix: https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=d290630d31f4517ab26392d00753d1397f9a4114 It is included in version 2.87 onward, so it affects only Jammy. ** Changed in: dnsmasq (Ubuntu) Status: New => Triaged ** Tags added: server-todo ** Also affects: dnsmasq (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: dnsmasq (Ubuntu Jammy) Status: New => Triaged ** Changed in: dnsmasq (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/2045570 Title: dnsmasq crash when no servers in resolv.conf Status in dnsmasq package in Ubuntu: Fix Released Status in dnsmasq source package in Jammy: Triaged Bug description: upstream discussion: https://lists.thekelleys.org.uk/pipermail/dnsmasq- discuss/2022q3/016563.html in my journal, my dns service crash and restart just after: Dec 04 17:18:38 dnsmasq[199333]: no servers found in /run/NetworkManager/no-stub-resolv.conf, will retry oops report: https://errors.ubuntu.com/oops/29cf5e2e-92b1-11ee-9bdf- fa163ec44ecd ubuntu jammy, dnsmasq-base 2.86-1.1ubuntu0.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2045570/+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 876262] Re: Gvim launcher doesn't appear in dash; appears in launcher with bad icon
In 2023, does this bug have any relevance in a currently supported release? ** Tags added: natty oneiric trusty ** Changed in: vim (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/876262 Title: Gvim launcher doesn't appear in dash; appears in launcher with bad icon Status in vim package in Ubuntu: Incomplete Bug description: After installing vim-gnome a shortcut to Gvim text editor is not available in the dash. After starting it (e.g. Alt-F2 -> 'gvim') the icon it appears with in the launcher is not pretty. This is a regression from Ubuntu 11.04. /usr/share/applications/gvim.desktop exists in 11.10 and the only difference between this and the same file in 11.04 is: $ diff 11.10/gvim.desktop 11.04/gvim.desktop 75c75 < Icon=/usr/share/pixmaps/vim.svg --- > Icon=vim Furthermore, the icon used in 11.04 also exists in 11.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/876262/+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 919735] Re: vim.gnome crashed with SIGABRT in raise()
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 11.10 (oneiric) reached end-of-life on May 9, 2013. An almost 11 year old bug report against an Ubuntu release than has been 'end of life' for over 10 years is no longer useful so I'm closing this as being 'Invalid'. Please do report any further bugs that you might find while using Ubuntu. ** Changed in: vim (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/919735 Title: vim.gnome crashed with SIGABRT in raise() Status in vim package in Ubuntu: Invalid Bug description: Not sure what caused this: i was editing some files, and don't recall doing something particularly unusual. ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: vim-gnome 2:7.3.154+hg~74503f6ee649-2ubuntu3 ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9 Uname: Linux 3.0.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Fri Jan 20 23:49:27 2012 ExecutablePath: /usr/bin/vim.gnome InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) ProcCmdline: vim campaigns/workers/base.py Signal: 6 SourcePackage: vim StacktraceTop: raise () from /lib/x86_64-linux-gnu/libc.so.6 abort () from /lib/x86_64-linux-gnu/libc.so.6 ?? () from /lib/x86_64-linux-gnu/libc.so.6 ?? () from /lib/x86_64-linux-gnu/libc.so.6 free () from /lib/x86_64-linux-gnu/libc.so.6 Title: vim.gnome crashed with SIGABRT in raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: admin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/919735/+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 967084] Re: vim.gtk crashed with SIGSEGV in update_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 12.04 (precise) reached end-of-life on April 28, 2017. I'm closing this as 'Invalid' as neither the Ubuntu release or Vim release are currently supported. Please create a new bug report if you still see the reported problem in a currently supported release of Ubuntu. ** Changed in: vim (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/967084 Title: vim.gtk crashed with SIGSEGV in update_screen() Status in vim package in Ubuntu: Invalid Bug description: Vim crashed when I tried to quit. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: vim-gtk 2:7.3.429-2ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Wed Mar 28 14:10:55 2012 ExecutablePath: /usr/bin/vim.gtk InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) ProcCmdline: vim comm.c ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, user) SHELL=/bin/zsh TERM=screen-256color SegvReason: writing NULL VMA Signal: 11 SourcePackage: vim StacktraceTop: update_screen () main_loop () main () Title: vim.gtk crashed with SIGSEGV in update_screen() UpgradeStatus: Upgraded to precise on 2012-02-14 (43 days ago) UserGroups: adm admin cdrom dialout disk libvirtd lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/967084/+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 1065264] Re: gview does not display scrollbars where gvim does
Using Ubuntu 20.04 and 22.04 I'm not seeing the reported issue. There have been no comments supporting the reported bug for over 11 years so as the status is 'Confirmed' I'm closing this as being fixed. ** Tags added: precise ** Changed in: vim (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1065264 Title: gview does not display scrollbars where gvim does Status in vim package in Ubuntu: Fix Released Bug description: $lsb_release -rd Description: Ubuntu 12.04 LTS Release: 12.04 $ apt-cache policy vim-gnome vim-gnome: Installed: 2:7.3.429-2ubuntu2.1 Candidate: 2:7.3.429-2ubuntu2.1 Expected: Opening files in gview/gvimdiff (both /etc/alternatives point at vim.gnome) that do not fit in the window should result in scrollbars the same way they do in gvim. Instead: No visable scrollbars. Clicking and holding in the area where I would expect a scrollbar sometimes produced the scrollbar that is present in Gnome Terminal. This is not the same scrollbar as present in gvim and it is only visible while you click and hold. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1065264/+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 793703] Re: Format string bug in shtags.pl
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 closing this bug report as 'Invalid' as no version information was given for either Vim or Ubuntu and as over twelve years have passed without comment it is unlikely that an Ubuntu developer will even look at a bug report which probably needs to be fixed upstream by a Vim developer. ** Changed in: vim (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/793703 Title: Format string bug in shtags.pl Status in vim package in Ubuntu: Invalid Bug description: Binary package hint: vim-runtime vim/vim73/tools/shtags.pl have format string bug . test case : emanuel@emanuel-desktop:~$ echo 1 > '/tmp/a%n' emanuel@emanuel-desktop:~$ /usr/share/vim/vim73/tools/shtags.pl '/tmp/a%n' Modification of a read-only value attempted at /usr/share/vim/vim73/tools/shtags.pl line 142, <> line 1. the bug can be found at : printf "Using $shell for $ARGV\n"; fix : use %s for $shell and $ARGV printf "Using %s for %s\n" , $shell , $ARGV ; To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/793703/+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 1282345] Re: vim crashes on ruby files with very long lines
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 13.10 (saucy) reached end-of-life on July 17, 2014. 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 while 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: vim (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1282345 Title: vim crashes on ruby files with very long lines Status in vim package in Ubuntu: Incomplete Bug description: 1. edit a file to be called test in vim: vi test. 2. Insert the following line: vln = "Nowisthetimeforareallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyr eallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallreallyreallyreallyreallyreallyy" 3. Play with the file to reassure you have no problem editing it. 4. Exit vi and mv test test.rb. 5. vi test.rb. Note that now the file freezes up. You can exit the terminal, and try going back and forth. It is 100%. When the file is called test.rb, it freezes up, apparently from formatting for ruby. When it is called just test, it is fine. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: vim 2:7.4.000-1ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Wed Feb 19 17:37:36 2014 InstallationDate: Installed on 2013-10-25 (117 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: vim UpgradeStatus: Upgraded to saucy on 2013-10-26 (117 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1282345/+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 1305778] Re: Misinterpretation of key sequence
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 13.10 (saucy) reached end-of-life on July 17, 2014. 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 while 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: vim (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1305778 Title: Misinterpretation of key sequence Status in vim package in Ubuntu: Incomplete Bug description: Ubuntu 13.10 Vim: Installed: 2:7.4.000-1ubuntu2 Entering the commands to leave insert mode & insert a new line above the current one, beginning with certain letters, results in punctuation on the current line instead. To reproduce: Start vim, *quickly* type the keys: iOm Expected result: New line created above the current one with the letter 'm' in it Actual result: Hyphen inserted on current line Also affects: Letters j,k,n,o j gives *, k gives +, m gives -, n gives ., o gives / Vim version: 7.4 (as installed by Ubuntu 13.10) Happens on my machine, my co-worker's machine, several VMs and to some (not all) of the people I asked about it on IRC. Definitely requires that the typing is done quickly. Causes me problems very frequently because I write a lot of Perl and when I go to declare a variable, I get "-y $foo" on the current line instead of "my $foo" on the previous line. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: vim 2:7.4.000-1ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Thu Apr 10 11:51:03 2014 InstallationDate: Installed on 2013-11-27 (134 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: vim UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1305778/+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 1314238] Re: Account logged off when gvim is started from terminal
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 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. If this is still an issue while 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. ** Tags added: trusty ** Changed in: vim (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1314238 Title: Account logged off when gvim is started from terminal Status in vim package in Ubuntu: Incomplete Bug description: The issue: When I open a terminal and start gvim with gvim command, I'm immediately logged off. Before the login dialog appears, a text-only framebuffer appears briefly with nothing but cursor blinking on the first line, which leads me to believe it's an Unity or X crash. I have just installed a fresh copy of 14.04. unity version 7.2.0+14.04.20140416-0ubuntu1 vim-runtime version 2:7.4.052-1ubuntu3 This happens with both vim-gtk and vim-gnome packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1314238/+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 1380110] Re: comments inside parentheses mess up the syntax coloring of shell script
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. No version information has been given and with no comments for over nine years I'm closing this as 'Invalid'. If this issue is still relevant in a currently supported release of Ubuntu then please let us know which one(s) so that the Ubuntu developers can focus their attention on specific Ubuntu releases. You should also then change the status of the bug report back to 'New'. ** Changed in: vim (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1380110 Title: comments inside parentheses mess up the syntax coloring of shell script Status in vim package in Ubuntu: Invalid Bug description: Hi, I've found the following bug with syntax coloring of shell scripts in vi and vim. If you add comments outside parenthesis, it works fine. But if you add comments inside parenthesis, or worse comments with quotes, the syntax coloring is totally messed up. I join a sample shell script to demonstrate the bug. Best regards, Laurent Lyaudet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1380110/+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 1334168] Re: vim defaults for tm and ttm are wrong
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. If this is still an issue while 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: vim (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1334168 Title: vim defaults for tm and ttm are wrong Status in vim package in Ubuntu: Incomplete Bug description: While scouring the net for info on curious lag in vim that can eat keystrokes (devastating over a laggy link, which is one of the primary situations where vim is useful), every conversation pointed me to `:help ttm`, which says: A useful setting would be :set timeout timeoutlen=3000 ttimeoutlen=100 (time out on mapping after three seconds, time out on key codes after a tenth of a second). So it appears that insead of putting the correct defaults in as the defaults, vim chose to bury the information deep inside the documentation. As a distro packaging vim, we have an opportunity to fix this. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: vim 2:7.4.052-1ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jun 25 10:01:05 2014 InstallationDate: Installed on 2014-05-29 (26 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: vim UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1334168/+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 1647771] Re: Undefined variable in vim netrw when netrw_browse_split = 3
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 while 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. ** Tags added: xenial ** Changed in: vim (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1647771 Title: Undefined variable in vim netrw when netrw_browse_split = 3 Status in vim package in Ubuntu: Incomplete Bug description: To reproduce, open the netrw explorer in a new tab, and set opened files to go to a new tab: :let g:netrw_browse_split = 3 :Texplore When the user selects a file from the explorer with Enter, this error appears: Error detected while processing function 20_NetrwBrowseChgDir: line 135: E121: Undefined variable: b:netrw_curdir And this is displayed for a second: Invalid arguments for function SetRexDir Saw this after upgrade to Ubuntu 16.04 (vim 7.4.1689-3ubuntu1.2). The error didn't show with vim 7.4.052-1ubuntu3.1 on Ubuntu-14.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1647771/+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 1756418] Re: Error detected while processing /usr/share/vim/vim80/debian.vim
*** This bug is a duplicate of bug 1754999 *** https://bugs.launchpad.net/bugs/1754999 ** This bug has been marked a duplicate of bug 1754999 Error detected while processing /usr/share/vim/vim80/debian.vim: -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1756418 Title: Error detected while processing /usr/share/vim/vim80/debian.vim Status in vim package in Ubuntu: Confirmed Bug description: Just after virsh edit domain: Error detected while processing /usr/share/vim/vim80/debian.vim: line 29: E319: Sorry, the command is not available in this version: function! MapExists(name, modes) line 30: E319: Sorry, the command is not available in this version: for mode in split(a:modes, '\zs') line 34: E319: Sorry, the command is not available in this version: endfor line 35: E319: Sorry, the command is not available in this version: return 0 line 36: E319: Sorry, the command is not available in this version: endfunction Press ENTER or type command to continue ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: vim-common 2:8.0.1401-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 16 19:34:33 2018 InstallationDate: Installed on 2018-02-27 (16 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180227) PackageArchitecture: all SourcePackage: vim UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1756418/+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 560217] Re: vim-gnome omnicompletion mousewheel bug
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 9.10 (karmic) reached end-of-life on April 30, 2011. 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 while 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. ** Tags added: karmic ** Changed in: vim (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/560217 Title: vim-gnome omnicompletion mousewheel bug Status in vim package in Ubuntu: Incomplete Bug description: Binary package hint: vim-gnome Huge version with GTK2-GNOME GUI version has the mousewheel broken on the omni complete popup. It works on the command version in gnome-terminal. 9.10 / vim 7.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/560217/+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 96263] Re: vim crashed with sigsegv
Thank you for reporting this bug to Ubuntu. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. Ubuntu 7.04 (feisty) reached end-of-life on October 19, 2008. A sixteen year old bug report with few subsequent comments is of little use to Ubuntu's developers in 2023 so I'm closing this as 'Invalid'. If you're still using Ubuntu them please do continue to report any bugs that you might find. ** Changed in: vim (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/96263 Title: vim crashed with sigsegv Status in vim package in Ubuntu: Invalid Bug description: Vim crashes on my feisty machine; it's reproducible at least twice. I have a core file which shows this traceback: (gdb) bt #0 0xe410 in __kernel_vsyscall () #1 0xb712c226 in kill () from /lib/tls/i686/cmov/libc.so.6 #2 0x08149da7 in may_core_dump () at os_unix.c:2900 #3 0x0814be18 in mch_exit (r=1) at os_unix.c:2865 #4 0x0810fa60 in preserve_exit () at misc1.c:8277 #5 #6 do_highlight (line=0x81f20dc "", forceit=0, init=1) at syntax.c:6752 #7 0x0818f227 in init_highlight (both=1, reset=0) at syntax.c:6336 #8 0x080f9ec3 in main (argc=Cannot access memory at address 0x4 ) at main.c:546 I don't know what changed to break this, it was working a moment ago and I didn't upgrade it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/96263/+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 84735] Re: [apport] package vim-tiny failed to install/upgrade:
Thank you for reporting this bug to Ubuntu. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. I'm closing this as 'Invalid' as no version information has been provided and there has been no comments for over sixteen years. ** Changed in: vim (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/84735 Title: [apport] package vim-tiny failed to install/upgrade: Status in vim package in Ubuntu: Invalid Bug description: [apport] package ubuntu-minimal failed to install/upgrade: ProblemType: Package Date: Mon Feb 12 13:20:01 2007 ErrorMessage: ErrorMessage: dependency problems - leaving unconfigured Package: ubuntu-minimal SourcePackage: ubuntu-meta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/84735/+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 472082] Re: gvim corrupts text after Jaunty -> karmic upgrade
Thank you for reporting this bug to Ubuntu. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. A fourteen year old bug report which details an upgrade between releases which were both 'end of life' over twelve years ago is not useful in 2023 so I'm closing this as 'Invalid'. Please *do* report any problems that you might see when upgrading currently supported Ubuntu releases. ** Changed in: vim (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/472082 Title: gvim corrupts text after Jaunty -> karmic upgrade Status in vim package in Ubuntu: Invalid Bug description: Binary package hint: vim The installed gvim application was running fine under Jaunty (on an IBM T30). Now, having upgraded to Karmic (but booted into 2.6.28-14 - owing to consistent failure to boot to 2.6.31-14 documented elsewhere), the application opens showing an initial screen on which all text is corrupted and wholly unreadable. On entering insert mode, all text entered text is displayed in corrupt fashion. If the gvim window is minimised and then subsequently recovered, any text is rendered readable ... any new text inserted is unreadable until such time as the window undergoes another minimise/maximise cycle. The fault isn't, AFAICT, related to the font selected in the window - the same behaviour is exhibited irrespective of the selected font. The attached screen shot shows the state of the app after some text had been entered, a minimise/maximise cycle undergone, followed by further text entry. ProblemType: Bug Architecture: i386 Date: Tue Nov 3 02:35:30 2009 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/bin/vim.gnome Package: vim-gnome 2:7.2.245-2ubuntu2 ProcEnviron: PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.28-14.47-generic SourcePackage: vim Uname: Linux 2.6.28-14-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/472082/+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 788481] Re: Unity can't handle two GVIM's at the same time
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 11.04 (natty) reached end-of-life on October 28, 2012. 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 while 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. ** Tags added: natty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/788481 Title: Unity can't handle two GVIM's at the same time Status in vim package in Ubuntu: New Bug description: Binary package hint: vim When I open two gvim's at the same time (from the command prompt), only one of them has a global menu, the other does not. This is not a duplicate of: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/781180 As I see no warnings. Just the first menu works, and the second GVIM has no menu. Which also means copy & paste between gvims using menu shortcuts is broken :( SInce only one instance has a menu... Alt+E 'C' is probably one of the most common things I do with two gvims open... Take care, -stu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/788481/+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 751726] Re: gvim icon is low-res and blurry in Unity
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 11.04 (natty) reached end-of-life on October 28, 2012. 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 while 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: vim (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/751726 Title: gvim icon is low-res and blurry in Unity Status in vim package in Ubuntu: Incomplete Bug description: Binary package hint: vim The icon used for gvim in Unity is a low-res bitmap. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: vim-gnome 2:7.3.035+hg~8fdc1210-1ubuntu7 ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38 Uname: Linux 2.6.38-7-generic x86_64 NonfreeKernelModules: wl Architecture: amd64 Date: Tue Apr 5 20:48:39 2011 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110329.1) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: vim UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/751726/+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 1768026] Re: echo message hides cursor
Further to comment #3: Ubuntu 18.04 (bionic) reached end-of-standard-support on May 31, 2023. All currently supported releases as of today's date, that is focal and later, include this patch so I'm closing this bug report as being fixed. ** Changed in: vim (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1768026 Title: echo message hides cursor Status in vim: Fix Released Status in vim package in Ubuntu: Fix Released Bug description: https://github.com/w0rp/ale/issues/1536#issuecomment-385056702 upstream bug https://github.com/vim/vim/issues/2612 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: vim 2:8.0.1453-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 30 14:16:35 2018 InstallationDate: Installed on 2017-05-17 (347 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: vim UpgradeStatus: Upgraded to bionic on 2018-04-26 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/vim/+bug/1768026/+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 2017804] Re: "Don't show this message again" button has no effect
Same issue here as well, fresh install, but it's 23.10 Ubuntu Mate. Shall it be reported separately for mantic ? -- 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/2017804 Title: "Don't show this message again" button has no effect Status in network-manager package in Ubuntu: Confirmed Bug description: Since my upgrade to Ubuntu 23.04 I get annoying popups I've never seen before, especially when waking the computer from suspend, telling me e.g. that my connection to the WiFi network was lost or restored. Although these popups have a "Don't show this message again" button, that button seems to have no effect and I can't figure out how to stop the dialogs from appearing. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: network-manager 1.42.4-1ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Unity:Unity7:ubuntu Date: Wed Apr 26 13:26:32 2023 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-01-10 (1932 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) IpRoute: default via 192.168.1.1 dev wlp4s0 proto dhcp src 192.168.1.202 metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.1.0/24 dev wlp4s0 proto kernel scope link src 192.168.1.202 metric 600 SourcePackage: network-manager UpgradeStatus: Upgraded to lunar on 2023-04-21 (5 days ago) WifiSyslog: mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2017-10-21T17:11:24 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.42.4 connected started full enabled enabled enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2017804/+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 1454016] Re: "c{motion}" temporary cancels 'linebreak' option for current line
Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016.
Patch will be included in all currently supported releases of Ubuntu so closing
as being fixed.
** Tags added: vivid
** Bug watch added: Debian Bug tracker #774492
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774492
** Also affects: vim via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774492
Importance: Unknown
Status: Unknown
** Changed in: vim (Ubuntu)
Status: New => Fix Released
** No longer affects: vim
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1454016
Title:
"c{motion}" temporary cancels 'linebreak' option for current line
Status in vim package in Ubuntu:
Fix Released
Bug description:
When editing long text using the c command, vim seems to temporarily
disable the "linebreak" option. This can be very annoying when editing
long lines of text.
A thorough discussion of this bug can be found in the Debian BTS
774492 (http://bugs.debian.org/774492)
I am encountering this bug on Ubuntu 15.04 running vim
2:7.4.488-3ubuntu2.
Debian fixed this issue by backporting patch 7.4.576 into the vim
package 2:7.4.488-7. It would be great if Ubuntu could backport/sync.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1454016/+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 1195448] Re: Gvim problem
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017. 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 while 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: vim (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1195448 Title: Gvim problem Status in vim package in Ubuntu: Incomplete Bug description: Upon lauchaing GVIM to update a shell file I get (gvim:335): GLib-GObject-WARNING **: cannot retrieve class for invalid (unclassed) type `' The file is loaded without problem. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: vim-gnome 2:7.3.429-2ubuntu2.1 ProcVersionSignature: Ubuntu 3.2.0-48.74-generic-pae 3.2.46 Uname: Linux 3.2.0-48-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.3 Architecture: i386 Date: Thu Jun 27 12:54:21 2013 ExecutablePath: /usr/bin/vim.gnome InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) MarkForUpload: True SourcePackage: vim UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1195448/+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 1570393] Re: vim 'autochdir' doesn't work for the first file
No version information given as to which Ubuntu release was affected by the reported issue. I'm closing this as 'Fixed Released' as in 2023 all currently supported releases of Ubuntu will include the Vim patch referred to in the bug description. ** Changed in: vim (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1570393 Title: vim 'autochdir' doesn't work for the first file Status in vim package in Ubuntu: Fix Released Bug description: Please, update at least to version 7.4.1716 that fixes this issue with `autochdir`. https://github.com/vim/vim/releases/tag/v7.4.1716 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1570393/+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 938469] Re: vim cannot regain control of mouse
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 12.04 (precise) reached end-of-life on April 28, 2017. 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 while 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: vim (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/938469 Title: vim cannot regain control of mouse Status in vim package in Ubuntu: Incomplete Bug description: In Precise, vim is unable to reassert control of the mouse once it has started. The mouse works normally upon starting vim. If it loses control of the mouse in the pseudo-terminal, however, perhaps due to being suspended with ^Z, or turning the mouse off with ':set mouse=', then vim becomes unable to regain control of the mouse when it should, such as being resumed or ':set mouse=a'. The expected behavior is that suspending should have no effect on the mouse within vim, and clearing and resetting the mouse variable should also have no effect on the mouse. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/938469/+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 1074454] Re: resize during insert problem
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 12.10 (quantal) reached end-of-life on May 16, 2014. 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 while 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. ** Tags added: quantal ** Changed in: vim (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1074454 Title: resize during insert problem Status in vim package in Ubuntu: Incomplete Bug description: resize during insert seems to cause a problem. to reproduce: create a textfile using the 21 lines of text given below. resize an xterm to 12 lines long and 80 characters wide. in the xterm, edit (vim) the textfile. position the cursor on the / preceeding "vmlinuz", and type cB/ (with no escape)(still in insert mode) resize the xterm to 10 lines by 80 characters. vim is now in an inconsistent state. the first visible cue is the disappearance of text following the cursor. further inserted characters appear to insert on the wrong line. as things progress it may recover itself, or it may ABRT or SEGV. for example if at this point i hit (end the insert) type :ls (with no CR) enlarge the window i get Vim: Caught deadly signal SEGV Vim: preserving files... and it hangs thus. uuid 960c92bd-69d3-415f-93b6-2242187e3557 uuid 960c92bd-69d3-415f-93b6-2242187e3557 uuid 960c92bd-69d3-415f-93b6-2242187e3557 uuid 960c92bd-69d3-415f-93b6-2242187e3557 uuid 960c92bd-69d3-415f-93b6-2242187e3557 uuid 960c92bd-69d3-415f-93b6-2242187e3557 uuid 960c92bd-69d3-415f-93b6-2242187e3557 uuid 960c92bd-69d3-415f-93b6-2242187e3557 uuid 960c92bd-69d3-415f-93b6-2242187e3557 uuid 960c92bd-69d3-415f-93b6-2242187e3557 kernel/SL-60-i386/Install-DVD/vmlinuz quiet panic=30 method=hd:sda7: ksdevice= initrd/SL-60-i386/Install-DVD/initrd.img initrd/SL-60-i386/Install-DVD/initrd.img initrd/SL-60-i386/Install-DVD/initrd.img initrd/SL-60-i386/Install-DVD/initrd.img initrd/SL-60-i386/Install-DVD/initrd.img initrd/SL-60-i386/Install-DVD/initrd.img initrd/SL-60-i386/Install-DVD/initrd.img initrd/SL-60-i386/Install-DVD/initrd.img initrd/SL-60-i386/Install-DVD/initrd.img initrd/SL-60-i386/Install-DVD/initrd.img $ lsb_release -rd Description:Ubuntu 12.10 Release:12.10 $ apt-cache policy vim vim: Installed: 2:7.3.547-4ubuntu1 Candidate: 2:7.3.547-4ubuntu1 Version table: *** 2:7.3.547-4ubuntu1 0 500 http://ie.archive.ubuntu.com/ubuntu/ quantal/main i386 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1074454/+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 1157538] Re: vim.basic crashed with SIGSEGV in modify_fname()
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 13.10 (saucy) reached end-of-life on July 17, 2014. I'm setting the status of this bug to 'Invalid' as it's not seen any activity for some time and no-one has confirmed the issue. If this is still an problem while using a currently maintained release of Ubuntu then please let us know which one(s) and revert the status back to 'New'. ** Changed in: vim (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1157538 Title: vim.basic crashed with SIGSEGV in modify_fname() Status in vim package in Ubuntu: Incomplete Bug description: creating a desktop launcher ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: vim 2:7.3.547-6ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-12.21-generic 3.8.2 Uname: Linux 3.8.0-12-generic i686 ApportVersion: 2.9.1-0ubuntu1 Architecture: i386 CrashCounter: 1 Date: Wed Mar 20 04:49:43 2013 ExecutablePath: /usr/bin/vim.basic InstallationDate: Installed on 2013-03-15 (4 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130314) MarkForUpload: True ProcCmdline: vim Signal: 11 SourcePackage: vim StacktraceTop: modify_fname () _r_debug () ?? () ?? () Title: vim.basic crashed with SIGSEGV in modify_fname() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1157538/+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 616858] Re: Mouse cursor in gvim is sometimes invisible
Thank you for reporting this bug to Ubuntu. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. Ubuntu 10.04 (lucid) reached end-of-life on May 9, 2013. Ubuntu 12.10 (quantal) reached end-of-life on May 16, 2014. 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 while 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. ** Tags added: lucid quantal ** Changed in: vim (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/616858 Title: Mouse cursor in gvim is sometimes invisible Status in vim package in Ubuntu: Incomplete Bug description: Binary package hint: vim-gnome In some cases the mouse cursor within a gvim window disappears. It is still there, just not visible, or under the window. Left clicking and selecting text will make it reappear. Searching within gvim for matching text can (sometimes) make the cursor disappear again. This doesn't happen with every gvim window opened up, but even if it didn't happen when first opened, searching will cause it to disappear again. [opiet@doodle ~] --> lsb_release -rd Description: Ubuntu 10.04.1 LTS Release: 10.04 [opiet@doodle ~] --> [opiet@doodle ~] --> apt-cache policy vim-gnome vim-gnome: Installed: 2:7.2.330-1ubuntu3 Candidate: 2:7.2.330-1ubuntu3 Version table: *** 2:7.2.330-1ubuntu3 0 500 http://us.archive.ubuntu.com/ubuntu/ lucid/main Packages 100 /var/lib/dpkg/status [opiet@doodle ~] --> To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/616858/+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 1069413] Re: Remove vim-tiny from install media
** Package changed: vim (Ubuntu) => ubuntu-seeds ** Project changed: ubuntu-seeds => ubuntu-meta (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1069413 Title: Remove vim-tiny from install media Status in ubuntu-meta package in Ubuntu: New Bug description: Finally with Ubuntu 12.10 the full VIM is installed by default. However, the package vim-tiny is _also_ installed, and frustratingly it is the vim-tiny binary that is used when typing 'vim' on the CLI. Please remove the vim-tiny package from the default install as it is 1) redundant now that full VIM is installed by default, and 2) harmful in the fact that it masks the VIM binary. Note that there was a request to remove vim-tiny back in 2007, but it was (rightfully) rejected at the time due to space considerations in the install media. Now, removing vim-tiny will actually save space due to full VIM being installed by default anyway: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/100029 Thanks.:wq To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1069413/+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 2045668] Re: Please merge dbus 1.14.10-3 (main) from Debian unstable
Untagging rls-nn-incoming based on insights from the MIR team in #ubuntu-devel [1] schopin: ogayot: usr-is-merged seems to be an empty meta-package. It's source package src:usrmerge is already in main does that mean we can just ask an AA to promote it, no paperwork? so I'd say this doesn't need a MIR, as there is no new code. Maybe this new binary was added after the source package got promoted. You should not block on this. I don't think paperwork would be involved. It might show up as a component-mismatch, but should be resolved on the fast-path, by asking an AA. [1] https://irclogs.ubuntu.com/2023/12/05/%23ubuntu-devel.html ** Tags removed: rls-nn-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/2045668 Title: Please merge dbus 1.14.10-3 (main) from Debian unstable Status in dbus package in Ubuntu: In Progress Bug description: 1.14.10-3 Published in sid-release on 2023-10-30 dbus (1.14.10-3) unstable; urgency=medium * d/control: dbus Depends on usr-is-merged (>= 38~). Non-merged /usr has been unsupported since Debian 12, as per Technical Committee resolutions #978636 and #994388 (please see the Debian 12 release notes for details). The version of usr-is-merged shipped in Debian 12 had an undocumented opt-out mechanism intended for use on buildds and QA systems targeting Debian 12 (piuparts, reproducible-builds, autopkgtest and similar), to ensure that the upgrade path from Debian 11 to 12 will continue to work and continue to undergo automated tests. That opt-out is no longer applicable or available in trixie/sid, and was removed in usrmerge version 38. Since version 1.14.10-2, dbus ships its systemd units in /usr/lib/systemd/system, as part of the distro-wide transition away from making use of "aliased" paths. This is entirely valid on merged-/usr systems, but will no longer work in the unsupported filesystem layout with non-merged /usr, because for historical reasons, current versions of systemd on non-merged-/usr systems will only read units from /lib/systemd/system. In the case of dbus, the symptom when this assumption is broken is particularly bad (various key system services will not start, with long delays during boot, login and shutdown), so let's hold back this upgrade on unsupported non-merged-/usr systems until they have completed the switch to merged-/usr and can install usr-is-merged (>= 38~). (Closes: #1054650) -- Simon McVittie Mon, 30 Oct 2023 11:51:35 + 1.14.10-2 Superseded in sid-release on 2023-10-30 dbus (1.14.10-2) unstable; urgency=low * Backport packaging changes from experimental: - Install systemd system units into /usr/lib/systemd/system. This was allowed by TC resolution #1053901. The shared library is still in /lib, for now. Build-depend on debhelper 13.11.6~ to ensure that the units are still picked up by dh_installsystemd. - Build-depend on pkgconf rather than pkg-config - dbus-x11: Don't copy XDG_SEAT_PATH, XDG_SESSION_PATH to activation environment. These variables are specific to a single login session. * d/copyright: Drop unused entry for pkg.m4. This is no longer included in the upstream source release since 1.14.6. * d/dbus-tests.lintian-overrides: Drop unused overrides. Lintian no longer flags our RUNPATH as problematic. -- Simon McVittie Wed, 25 Oct 2023 15:56:36 +0100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/2045668/+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 2045668] Re: Please merge dbus 1.14.10-3 (main) from Debian unstable
Tagging rls-nn-incoming so that we can discuss the new dependency on usr-is-merged (>= 38). While src:usrmerge is in main, usr-is-merged is currently in universe. usrmerge | 9 | xenial/universe | source, all usrmerge | 17| bionic/universe | source, all usrmerge | 23| focal/universe | source, all usrmerge | 25ubuntu2 | jammy | source, all usrmerge | 33ubuntu1 | lunar | source, all usrmerge | 35ubuntu1 | mantic | source, all usrmerge | 35ubuntu1 | noble | source, all ubuntu: usr-is-merged | 33ubuntu1 | lunar/universe | all usr-is-merged | 35ubuntu1 | mantic/universe | all usr-is-merged | 35ubuntu1 | noble/universe | all ** Tags added: rls-nn-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/2045668 Title: Please merge dbus 1.14.10-3 (main) from Debian unstable Status in dbus package in Ubuntu: In Progress Bug description: 1.14.10-3 Published in sid-release on 2023-10-30 dbus (1.14.10-3) unstable; urgency=medium * d/control: dbus Depends on usr-is-merged (>= 38~). Non-merged /usr has been unsupported since Debian 12, as per Technical Committee resolutions #978636 and #994388 (please see the Debian 12 release notes for details). The version of usr-is-merged shipped in Debian 12 had an undocumented opt-out mechanism intended for use on buildds and QA systems targeting Debian 12 (piuparts, reproducible-builds, autopkgtest and similar), to ensure that the upgrade path from Debian 11 to 12 will continue to work and continue to undergo automated tests. That opt-out is no longer applicable or available in trixie/sid, and was removed in usrmerge version 38. Since version 1.14.10-2, dbus ships its systemd units in /usr/lib/systemd/system, as part of the distro-wide transition away from making use of "aliased" paths. This is entirely valid on merged-/usr systems, but will no longer work in the unsupported filesystem layout with non-merged /usr, because for historical reasons, current versions of systemd on non-merged-/usr systems will only read units from /lib/systemd/system. In the case of dbus, the symptom when this assumption is broken is particularly bad (various key system services will not start, with long delays during boot, login and shutdown), so let's hold back this upgrade on unsupported non-merged-/usr systems until they have completed the switch to merged-/usr and can install usr-is-merged (>= 38~). (Closes: #1054650) -- Simon McVittie Mon, 30 Oct 2023 11:51:35 + 1.14.10-2 Superseded in sid-release on 2023-10-30 dbus (1.14.10-2) unstable; urgency=low * Backport packaging changes from experimental: - Install systemd system units into /usr/lib/systemd/system. This was allowed by TC resolution #1053901. The shared library is still in /lib, for now. Build-depend on debhelper 13.11.6~ to ensure that the units are still picked up by dh_installsystemd. - Build-depend on pkgconf rather than pkg-config - dbus-x11: Don't copy XDG_SEAT_PATH, XDG_SESSION_PATH to activation environment. These variables are specific to a single login session. * d/copyright: Drop unused entry for pkg.m4. This is no longer included in the upstream source release since 1.14.6. * d/dbus-tests.lintian-overrides: Drop unused overrides. Lintian no longer flags our RUNPATH as problematic. -- Simon McVittie Wed, 25 Oct 2023 15:56:36 +0100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/2045668/+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 1584539] Re: 16.04 regression: exceptions in ruby code in plugins have started causing vim to segfault
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. 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 while 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: vim (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1584539 Title: 16.04 regression: exceptions in ruby code in plugins have started causing vim to segfault Status in vim package in Ubuntu: Incomplete Bug description: In 14.04, an exception in the ruby code of a plugin caused the error to be printed to stderr, after which vim would launch, skipping the offending plugin: Error detected while processing /mnt/terra/home/simon/dev/vim-livecoding/plugin/livecoding.vim: line 37: NameError: undefined local variable or method `undefined_method_causing_an_exception' for main:Object Press ENTER or type command to continue But in 16.04, the same thing causes vim to segfault: Vim: Caught deadly signal SEGV Vim: Finished. Segmentation fault (core dumped) --- Vim version in 14.04: VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Jan 2 2014 19:39:59) Included patches: 1-52 Modified by pkg-vim-maintain...@lists.alioth.debian.org Compiled by buildd@ Huge version with GTK2 GUI. Vim version in 16.04: VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Apr 08 2016 11:38:28) Included patches: 1-1689 Modified by pkg-vim-maintain...@lists.alioth.debian.org Compiled by pkg-vim-maintain...@lists.alioth.debian.org Huge version with GTK2 GUI. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: vim-gtk 2:7.4.1689-3ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Sun May 22 22:33:45 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2015-04-25 (392 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: vim UpgradeStatus: Upgraded to xenial on 2016-05-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1584539/+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 1069413] [NEW] Remove vim-tiny from install media
You have been subscribed to a public bug: Finally with Ubuntu 12.10 the full VIM is installed by default. However, the package vim-tiny is _also_ installed, and frustratingly it is the vim-tiny binary that is used when typing 'vim' on the CLI. Please remove the vim-tiny package from the default install as it is 1) redundant now that full VIM is installed by default, and 2) harmful in the fact that it masks the VIM binary. Note that there was a request to remove vim-tiny back in 2007, but it was (rightfully) rejected at the time due to space considerations in the install media. Now, removing vim-tiny will actually save space due to full VIM being installed by default anyway: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/100029 Thanks.:wq ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Remove vim-tiny from install media https://bugs.launchpad.net/bugs/1069413 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta 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 1971090] Re: OS fully crashes when I exit an app folder.
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 report has been filed against 'vim' but the bug description says that vim is not installed. You say 'When I leave a app folder in a specific place' but what does that mean? Which app? 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 while 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: vim (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1971090 Title: OS fully crashes when I exit an app folder. Status in vim package in Ubuntu: Incomplete Bug description: When I leave a app folder in a specific place, the OS crashes and I need to do a force shut down to restart. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: vim (not installed) ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 1 10:17:57 2022 InstallationDate: Installed on 2021-05-31 (334 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: vim UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1971090/+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 1903057] Re: vim confused by \~/
** Also affects: vim via https://github.com/vim/vim/issues/8015 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1903057 Title: vim confused by \~/ Status in vim: Unknown Status in vim package in Ubuntu: New Bug description: $ cd $ mkdir \~ $ echo content a>\~/a $ echo content b>b $ less \~/a b :n :e# :q $ vim \~/a b :n :e# less is not confused, but vim has forgotten where the first file was. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: vim 2:8.0.1453-1ubuntu1.3 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 Date: Thu Nov 5 08:50:54 2020 InstallationDate: Installed on 2019-11-16 (354 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LC_TIME=en_DK.utf8 TERM=screen PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: vim UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/vim/+bug/1903057/+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 1230374] Re: vi editor for loop syntax problem
Closing as 'Invalid' as a 10 year old bug report with no version information and no comments for some time is of little use to the developers of currently supported releases of Ubuntu. ** Changed in: vim (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1230374 Title: vi editor for loop syntax problem Status in vim package in Ubuntu: Invalid Bug description: for (( i=0; i<=5; i++ )) do echo "$i Echoed" done this is what wrote in "bubble.sh" with vi editor and it gave me this error "bubble.sh: 1: bubble.sh: Syntax error: Bad for loop variable " i don't seem to understand why this is happening..please help To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1230374/+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 1745889] Re: Cron overloading system since update to 17.10
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 17.10 (artful) reached end-of-life on July 19, 2018. 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 while 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. ** Tags added: artful ** Changed in: vim (Ubuntu) Status: New => Incomplete ** Package changed: vim (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1745889 Title: Cron overloading system since update to 17.10 Status in Ubuntu: Incomplete Bug description: Prior to updating to 17.10 this issue did not exist. Since the update pam_unix(cron:session): session opened for user root by (uid=0) Happens after a short time of being logged in through webmin. None of the cron systems prior to hand were edited. Whatever is going on is nearly maxing out CPU usage and if you are one webmin you get a message the connection was lost. pam_unix(cron:session): session opened for user root by (uid=0) Fills up the log file once it starts. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1745889/+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 320478] Re: Backport fix for bug 270386 to 8.04 LTS?
Closing as 'Invalid' but should be 'Wont Fix' as Ubuntu 8.04 was EOL in 2011. ** Changed in: vim (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/320478 Title: Backport fix for bug 270386 to 8.04 LTS? Status in vim package in Ubuntu: Invalid Bug description: Binary package hint: vim There is a reproducible bug in vim, bug #270386, which was marked as closed because it appears fixed in Ubuntu 8.10. Are there any plans on fixing this bug in 8.04 LTS? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/320478/+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 1822688] Re: it does not print on printer
Ubuntu 18.04 (bionic) reached end-of-standard-support on May 31, 2023. This bug report has been filed against the 'vim' package but according to the bug description vim is not installed so I'm closing this as 'Invalid'. If the reported problem is still an issue while using a currently supported release of Ubuntu then please create a new bug report fully describing the bug that you are seeing and confirm the application that is being used. ** Changed in: vim (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1822688 Title: it does not print on printer Status in vim package in Ubuntu: Invalid Bug description: os: ubuntu 18.04.2 ,trying to print with Canon Imageclass MF 6530 .message says: printing completed, but it does not print the document.dell computer xps 8930 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: vim (not installed) ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 1 15:50:56 2019 InstallationDate: Installed on 2019-03-29 (3 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANG=en_US.UTF-8 TERM=xterm-256color SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: vim UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1822688/+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 1535809] Re: Segfaults in current vim in xenial (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 while 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. ** Tags added: xenial ** Changed in: vim (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1535809 Title: Segfaults in current vim in xenial (16.04) Status in vim package in Ubuntu: Incomplete Bug description: Version: 2:7.4.826-1ubuntu2 I can't tell what causes it, but i haven't gotten such segfaults in 14.04 and my vimrc was the same. From vims changelog i see some segfaulting has been fixed in newer revisions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1535809/+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 1659542] Re: package vim-common 2:7.4.1689-3ubuntu1.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configura
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. Probably just a bad package download for which: apt-get clean, apt-get update, apt-get install vim-common would have fixed the issue. ** Changed in: vim (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1659542 Title: package vim-common 2:7.4.1689-3ubuntu1.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in vim package in Ubuntu: Invalid Bug description: Cannot run package manager ProblemType: Package DistroRelease: Ubuntu 16.04 Package: vim-common 2:7.4.1689-3ubuntu1.2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 AptOrdering: vim-common: Configure vim-tiny: Configure NULL: ConfigurePending Architecture: amd64 Date: Thu Jan 26 04:17:45 2017 DpkgTerminalLog: dpkg: error processing package vim-common (--configure): package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-01-13 (13 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.15ubuntu0.2 SourcePackage: vim Title: package vim-common 2:7.4.1689-3ubuntu1.2 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/vim/+bug/1659542/+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 1489489] Re: The org.freedesktop.DBus.GetConnectionAppArmorSecurityContext() method is deprecated
** Merge proposal unlinked: https://code.launchpad.net/~ogayot/ubuntu/+source/dbus/+git/dbus/+merge/456880 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to content-hub in Ubuntu. https://bugs.launchpad.net/bugs/1489489 Title: The org.freedesktop.DBus.GetConnectionAppArmorSecurityContext() method is deprecated Status in Ubuntu Online Accounts API: Confirmed Status in snapd: Confirmed Status in apparmor package in Ubuntu: Fix Released Status in biometryd package in Ubuntu: New Status in content-hub package in Ubuntu: Confirmed Status in dbus package in Ubuntu: Triaged Status in deepin-notifications package in Ubuntu: New Status in lomiri-download-manager package in Ubuntu: In Progress Status in mediascanner2 package in Ubuntu: Fix Released Status in signon-apparmor-extension package in Ubuntu: Fix Released Status in ubuntu-system-settings-online-accounts package in Ubuntu: Fix Released Bug description: When upstream D-Bus merged the AppArmor mediation patches, they did not like the GetConnectionAppArmorSecurityContext() bus method. Instead, they decided to expose a peer's AppArmor context using the org.freedesktop.DBus.GetConnectionCredentials() bus method. All users of the GetConnectionAppArmorSecurityContext() method should switch to the GetConnectionCredentials() method as soon as possible so that Ubuntu can drop the patch that implements GetConnectionAppArmorSecurityContext() by the time 16.04 LTS is released. In order to switch to the new method, you'll need to depend on libapparmor 2.10 or newer. I'll be adding example code that illustrates how to switch from GetConnectionAppArmorSecurityContext() to GetConnectionCredentials(). content-hub, media-hub, mediascanner2, signon-apparmor-extension, ubuntu-download-manager, and ubuntu-system-settings-online-accounts all need to transition to the new method of obtaining the AppArmor label. The apparmor package should be updated to drop the libapparmor- mention-dbus-method-in-getcon-man.patch patch and the dbus package should be updated to drop the aa-get-connection-apparmor-security- context.patch patch. To manage notifications about this bug go to: https://bugs.launchpad.net/online-accounts-api/+bug/1489489/+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 2045668] Re: Please merge dbus 1.14.10-3 (main) from Debian unstable
** Merge proposal linked: https://code.launchpad.net/~ogayot/ubuntu/+source/dbus/+git/dbus/+merge/456880 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/2045668 Title: Please merge dbus 1.14.10-3 (main) from Debian unstable Status in dbus package in Ubuntu: In Progress Bug description: 1.14.10-3 Published in sid-release on 2023-10-30 dbus (1.14.10-3) unstable; urgency=medium * d/control: dbus Depends on usr-is-merged (>= 38~). Non-merged /usr has been unsupported since Debian 12, as per Technical Committee resolutions #978636 and #994388 (please see the Debian 12 release notes for details). The version of usr-is-merged shipped in Debian 12 had an undocumented opt-out mechanism intended for use on buildds and QA systems targeting Debian 12 (piuparts, reproducible-builds, autopkgtest and similar), to ensure that the upgrade path from Debian 11 to 12 will continue to work and continue to undergo automated tests. That opt-out is no longer applicable or available in trixie/sid, and was removed in usrmerge version 38. Since version 1.14.10-2, dbus ships its systemd units in /usr/lib/systemd/system, as part of the distro-wide transition away from making use of "aliased" paths. This is entirely valid on merged-/usr systems, but will no longer work in the unsupported filesystem layout with non-merged /usr, because for historical reasons, current versions of systemd on non-merged-/usr systems will only read units from /lib/systemd/system. In the case of dbus, the symptom when this assumption is broken is particularly bad (various key system services will not start, with long delays during boot, login and shutdown), so let's hold back this upgrade on unsupported non-merged-/usr systems until they have completed the switch to merged-/usr and can install usr-is-merged (>= 38~). (Closes: #1054650) -- Simon McVittie Mon, 30 Oct 2023 11:51:35 + 1.14.10-2 Superseded in sid-release on 2023-10-30 dbus (1.14.10-2) unstable; urgency=low * Backport packaging changes from experimental: - Install systemd system units into /usr/lib/systemd/system. This was allowed by TC resolution #1053901. The shared library is still in /lib, for now. Build-depend on debhelper 13.11.6~ to ensure that the units are still picked up by dh_installsystemd. - Build-depend on pkgconf rather than pkg-config - dbus-x11: Don't copy XDG_SEAT_PATH, XDG_SESSION_PATH to activation environment. These variables are specific to a single login session. * d/copyright: Drop unused entry for pkg.m4. This is no longer included in the upstream source release since 1.14.6. * d/dbus-tests.lintian-overrides: Drop unused overrides. Lintian no longer flags our RUNPATH as problematic. -- Simon McVittie Wed, 25 Oct 2023 15:56:36 +0100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/2045668/+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 1489489] Re: The org.freedesktop.DBus.GetConnectionAppArmorSecurityContext() method is deprecated
** Merge proposal linked: https://code.launchpad.net/~ogayot/ubuntu/+source/dbus/+git/dbus/+merge/456880 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to content-hub in Ubuntu. https://bugs.launchpad.net/bugs/1489489 Title: The org.freedesktop.DBus.GetConnectionAppArmorSecurityContext() method is deprecated Status in Ubuntu Online Accounts API: Confirmed Status in snapd: Confirmed Status in apparmor package in Ubuntu: Fix Released Status in biometryd package in Ubuntu: New Status in content-hub package in Ubuntu: Confirmed Status in dbus package in Ubuntu: Triaged Status in deepin-notifications package in Ubuntu: New Status in lomiri-download-manager package in Ubuntu: In Progress Status in mediascanner2 package in Ubuntu: Fix Released Status in signon-apparmor-extension package in Ubuntu: Fix Released Status in ubuntu-system-settings-online-accounts package in Ubuntu: Fix Released Bug description: When upstream D-Bus merged the AppArmor mediation patches, they did not like the GetConnectionAppArmorSecurityContext() bus method. Instead, they decided to expose a peer's AppArmor context using the org.freedesktop.DBus.GetConnectionCredentials() bus method. All users of the GetConnectionAppArmorSecurityContext() method should switch to the GetConnectionCredentials() method as soon as possible so that Ubuntu can drop the patch that implements GetConnectionAppArmorSecurityContext() by the time 16.04 LTS is released. In order to switch to the new method, you'll need to depend on libapparmor 2.10 or newer. I'll be adding example code that illustrates how to switch from GetConnectionAppArmorSecurityContext() to GetConnectionCredentials(). content-hub, media-hub, mediascanner2, signon-apparmor-extension, ubuntu-download-manager, and ubuntu-system-settings-online-accounts all need to transition to the new method of obtaining the AppArmor label. The apparmor package should be updated to drop the libapparmor- mention-dbus-method-in-getcon-man.patch patch and the dbus package should be updated to drop the aa-get-connection-apparmor-security- context.patch patch. To manage notifications about this bug go to: https://bugs.launchpad.net/online-accounts-api/+bug/1489489/+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 2037604] Re: Backport packages for 22.04.4 HWE stack
** Description changed: [Impact] The graphics HWE stack from mantic needs to be backported for 22.04.4 directx-headers - build-dep of the new Mesa mesa - new major release (23.2.x) - new HW support, Meteor Lake.. [Test case] - We want to cover at least 2-3 different, widely used GPU and already previously supported generations from both AMD and Intel which are supported by this release, as those are the ones that cover most bases; nouveau users tend to switch to the NVIDIA blob after installation. No need to test ancient GPU's supported by mesa-amber. - - AMD: + We want to cover at least 2-3 different, widely used and already previously supported GPU generations from both AMD and Intel which are supported by this release, as those are the ones that cover most bases; nouveau users tend to switch to the NVIDIA blob after installation. No need to test ancient GPU's supported by mesa-amber. And best to focus on the newer generations (~5y and newer) as the older ones are less likely to break at this point. + - AMD: Vega, Navi1x (RX5000*), Navi2x (RX6000*), Navi3x (RX7000*) - Intel: gen9 (SKL/APL/KBL/CFL/WHL/CML), gen11 (ICL), gen12 (TGL/RKL/RPL/DG2) - - Install the new mesa and run some tests: + Install the new packages and run some tests: - check that the desktop is still using hw acceleration and hasn't fallen back to swrast/llvmpipe - run freely available benchmarks that torture the GPU (Unigine Heaven/Valley/Superposition) - run some games from Steam if possible - and in each case check if there are any gfx corruption happening + and in each case check that there is no gfx corruption happening or + worse. [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll try to catch any with testing. And since it shares bugs with mantic, we'd already know if there are serious issues. We will backport the final 23.2.x at a later stage, the first backport is needed for enabling Intel Meteor Lake. ** Description changed: [Impact] The graphics HWE stack from mantic needs to be backported for 22.04.4 directx-headers - build-dep of the new Mesa mesa - new major release (23.2.x) - new HW support, Meteor Lake.. [Test case] We want to cover at least 2-3 different, widely used and already previously supported GPU generations from both AMD and Intel which are supported by this release, as those are the ones that cover most bases; nouveau users tend to switch to the NVIDIA blob after installation. No need to test ancient GPU's supported by mesa-amber. And best to focus on the newer generations (~5y and newer) as the older ones are less likely to break at this point. - AMD: Vega, Navi1x (RX5000*), Navi2x (RX6000*), Navi3x (RX7000*) - Intel: gen9 (SKL/APL/KBL/CFL/WHL/CML), gen11 (ICL), gen12 (TGL/RKL/RPL/DG2) Install the new packages and run some tests: - check that the desktop is still using hw acceleration and hasn't fallen back to swrast/llvmpipe - run freely available benchmarks that torture the GPU (Unigine Heaven/Valley/Superposition) - run some games from Steam if possible and in each case check that there is no gfx corruption happening or worse. + Note that upstream releases have already been tested for OpenGL and + Vulkan conformance by their CI. + [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll try to catch any with testing. And since it shares bugs with mantic, we'd already know if there are serious issues. We will backport the final 23.2.x at a later stage, the first backport is needed for enabling Intel Meteor Lake. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037604 Title: Backport packages for 22.04.4 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in rust-bindgen package in Ubuntu: Invalid Status in rust-clang-sys package in Ubuntu: Invalid Status in directx-headers source package in Jammy: Fix Committed Status in mesa source package in Jammy: Incomplete Status in rust-bindgen source package in Jammy: Invalid Status in rust-clang-sys source package in Jammy: Invalid Bug description: [Impact] The graphics HWE stack from mantic needs to be backported for 22.04.4 directx-headers - build-dep of the new Mesa mesa - new major release (23.2.x) - new HW support, Meteor Lake.. [Test case] We want to cover at least 2-3 different, widely used and already previously supported GPU generations from both AMD and Intel which are supported by this release, as those are the ones that cover most bases; nouveau users tend to switch to the NVIDIA blob after installation. No need to test ancient GPU's supported by mesa-amber. And best to focus on the newer generations (~5y and
[Touch-packages] [Bug 2037604] Re: Backport packages for 22.04.4 HWE stack
** Description changed: [Impact] The graphics HWE stack from mantic needs to be backported for 22.04.4 directx-headers - build-dep of the new Mesa mesa - new major release (23.2.x) - new HW support, Meteor Lake.. [Test case] - Install the new mesa on various hw, see that everything still works like before or better. + We want to cover at least 2-3 different, widely used GPU and already previously supported generations from both AMD and Intel which are supported by this release, as those are the ones that cover most bases; nouveau users tend to switch to the NVIDIA blob after installation. No need to test ancient GPU's supported by mesa-amber. + - AMD: + - Intel: gen9 (SKL/APL/KBL/CFL/WHL/CML), gen11 (ICL), gen12 (TGL/RKL/RPL/DG2) + + + Install the new mesa and run some tests: + - check that the desktop is still using hw acceleration and hasn't fallen back to swrast/llvmpipe + - run freely available benchmarks that torture the GPU (Unigine Heaven/Valley/Superposition) + - run some games from Steam if possible + + and in each case check if there are any gfx corruption happening [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll try to catch any with testing. And since it shares bugs with mantic, we'd already know if there are serious issues. We will backport the final 23.2.x at a later stage, the first backport is needed for enabling Intel Meteor Lake. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037604 Title: Backport packages for 22.04.4 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in rust-bindgen package in Ubuntu: Invalid Status in rust-clang-sys package in Ubuntu: Invalid Status in directx-headers source package in Jammy: Fix Committed Status in mesa source package in Jammy: Incomplete Status in rust-bindgen source package in Jammy: Invalid Status in rust-clang-sys source package in Jammy: Invalid Bug description: [Impact] The graphics HWE stack from mantic needs to be backported for 22.04.4 directx-headers - build-dep of the new Mesa mesa - new major release (23.2.x) - new HW support, Meteor Lake.. [Test case] We want to cover at least 2-3 different, widely used GPU and already previously supported generations from both AMD and Intel which are supported by this release, as those are the ones that cover most bases; nouveau users tend to switch to the NVIDIA blob after installation. No need to test ancient GPU's supported by mesa-amber. - AMD: - Intel: gen9 (SKL/APL/KBL/CFL/WHL/CML), gen11 (ICL), gen12 (TGL/RKL/RPL/DG2) Install the new mesa and run some tests: - check that the desktop is still using hw acceleration and hasn't fallen back to swrast/llvmpipe - run freely available benchmarks that torture the GPU (Unigine Heaven/Valley/Superposition) - run some games from Steam if possible and in each case check if there are any gfx corruption happening [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll try to catch any with testing. And since it shares bugs with mantic, we'd already know if there are serious issues. We will backport the final 23.2.x at a later stage, the first backport is needed for enabling Intel Meteor Lake. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/2037604/+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 2045668] [NEW] Please merge dbus 1.14.10-3 (main) from Debian unstable
Public bug reported: 1.14.10-3 Published in sid-release on 2023-10-30 dbus (1.14.10-3) unstable; urgency=medium * d/control: dbus Depends on usr-is-merged (>= 38~). Non-merged /usr has been unsupported since Debian 12, as per Technical Committee resolutions #978636 and #994388 (please see the Debian 12 release notes for details). The version of usr-is-merged shipped in Debian 12 had an undocumented opt-out mechanism intended for use on buildds and QA systems targeting Debian 12 (piuparts, reproducible-builds, autopkgtest and similar), to ensure that the upgrade path from Debian 11 to 12 will continue to work and continue to undergo automated tests. That opt-out is no longer applicable or available in trixie/sid, and was removed in usrmerge version 38. Since version 1.14.10-2, dbus ships its systemd units in /usr/lib/systemd/system, as part of the distro-wide transition away from making use of "aliased" paths. This is entirely valid on merged-/usr systems, but will no longer work in the unsupported filesystem layout with non-merged /usr, because for historical reasons, current versions of systemd on non-merged-/usr systems will only read units from /lib/systemd/system. In the case of dbus, the symptom when this assumption is broken is particularly bad (various key system services will not start, with long delays during boot, login and shutdown), so let's hold back this upgrade on unsupported non-merged-/usr systems until they have completed the switch to merged-/usr and can install usr-is-merged (>= 38~). (Closes: #1054650) -- Simon McVittie Mon, 30 Oct 2023 11:51:35 + 1.14.10-2 Superseded in sid-release on 2023-10-30 dbus (1.14.10-2) unstable; urgency=low * Backport packaging changes from experimental: - Install systemd system units into /usr/lib/systemd/system. This was allowed by TC resolution #1053901. The shared library is still in /lib, for now. Build-depend on debhelper 13.11.6~ to ensure that the units are still picked up by dh_installsystemd. - Build-depend on pkgconf rather than pkg-config - dbus-x11: Don't copy XDG_SEAT_PATH, XDG_SESSION_PATH to activation environment. These variables are specific to a single login session. * d/copyright: Drop unused entry for pkg.m4. This is no longer included in the upstream source release since 1.14.6. * d/dbus-tests.lintian-overrides: Drop unused overrides. Lintian no longer flags our RUNPATH as problematic. -- Simon McVittie Wed, 25 Oct 2023 15:56:36 +0100 ** Affects: dbus (Ubuntu) Importance: Undecided Assignee: Olivier Gayot (ogayot) Status: In Progress ** Changed in: dbus (Ubuntu) Assignee: (unassigned) => Olivier Gayot (ogayot) ** Changed in: dbus (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/2045668 Title: Please merge dbus 1.14.10-3 (main) from Debian unstable Status in dbus package in Ubuntu: In Progress Bug description: 1.14.10-3 Published in sid-release on 2023-10-30 dbus (1.14.10-3) unstable; urgency=medium * d/control: dbus Depends on usr-is-merged (>= 38~). Non-merged /usr has been unsupported since Debian 12, as per Technical Committee resolutions #978636 and #994388 (please see the Debian 12 release notes for details). The version of usr-is-merged shipped in Debian 12 had an undocumented opt-out mechanism intended for use on buildds and QA systems targeting Debian 12 (piuparts, reproducible-builds, autopkgtest and similar), to ensure that the upgrade path from Debian 11 to 12 will continue to work and continue to undergo automated tests. That opt-out is no longer applicable or available in trixie/sid, and was removed in usrmerge version 38. Since version 1.14.10-2, dbus ships its systemd units in /usr/lib/systemd/system, as part of the distro-wide transition away from making use of "aliased" paths. This is entirely valid on merged-/usr systems, but will no longer work in the unsupported filesystem layout with non-merged /usr, because for historical reasons, current versions of systemd on non-merged-/usr systems will only read units from /lib/systemd/system. In the case of dbus, the symptom when this assumption is broken is particularly bad (various key system services will not start, with long delays during boot, login and shutdown), so let's hold back this upgrade on unsupported non-merged-/usr systems until they have completed the switch to merged-/usr and can install usr-is-merged (>= 38~). (Closes: #1054650) -- Simon McVittie Mon, 30 Oct 2023 11:51:35 + 1.14.10-2 Superseded in sid-release on 2023-10-30
[Touch-packages] [Bug 2037604] Re: Backport packages for 22.04.4 HWE stack
Access to the vendor CI's won't happen anytime soon, so I'll expand the test case for this stack. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037604 Title: Backport packages for 22.04.4 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in rust-bindgen package in Ubuntu: Invalid Status in rust-clang-sys package in Ubuntu: Invalid Status in directx-headers source package in Jammy: Fix Committed Status in mesa source package in Jammy: Incomplete Status in rust-bindgen source package in Jammy: Invalid Status in rust-clang-sys source package in Jammy: Invalid Bug description: [Impact] The graphics HWE stack from mantic needs to be backported for 22.04.4 directx-headers - build-dep of the new Mesa mesa - new major release (23.2.x) - new HW support, Meteor Lake.. [Test case] Install the new mesa on various hw, see that everything still works like before or better. [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll try to catch any with testing. And since it shares bugs with mantic, we'd already know if there are serious issues. We will backport the final 23.2.x at a later stage, the first backport is needed for enabling Intel Meteor Lake. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/2037604/+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 1489489] Re: The org.freedesktop.DBus.GetConnectionAppArmorSecurityContext() method is deprecated
** Merge proposal linked: https://code.launchpad.net/~ogayot/ubuntu/+source/lomiri-download-manager/+git/lomiri-download-manager/+merge/456875 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to content-hub in Ubuntu. https://bugs.launchpad.net/bugs/1489489 Title: The org.freedesktop.DBus.GetConnectionAppArmorSecurityContext() method is deprecated Status in Ubuntu Online Accounts API: Confirmed Status in snapd: Confirmed Status in apparmor package in Ubuntu: Fix Released Status in biometryd package in Ubuntu: New Status in content-hub package in Ubuntu: Confirmed Status in dbus package in Ubuntu: Triaged Status in deepin-notifications package in Ubuntu: New Status in lomiri-download-manager package in Ubuntu: In Progress Status in mediascanner2 package in Ubuntu: Fix Released Status in signon-apparmor-extension package in Ubuntu: Fix Released Status in ubuntu-system-settings-online-accounts package in Ubuntu: Fix Released Bug description: When upstream D-Bus merged the AppArmor mediation patches, they did not like the GetConnectionAppArmorSecurityContext() bus method. Instead, they decided to expose a peer's AppArmor context using the org.freedesktop.DBus.GetConnectionCredentials() bus method. All users of the GetConnectionAppArmorSecurityContext() method should switch to the GetConnectionCredentials() method as soon as possible so that Ubuntu can drop the patch that implements GetConnectionAppArmorSecurityContext() by the time 16.04 LTS is released. In order to switch to the new method, you'll need to depend on libapparmor 2.10 or newer. I'll be adding example code that illustrates how to switch from GetConnectionAppArmorSecurityContext() to GetConnectionCredentials(). content-hub, media-hub, mediascanner2, signon-apparmor-extension, ubuntu-download-manager, and ubuntu-system-settings-online-accounts all need to transition to the new method of obtaining the AppArmor label. The apparmor package should be updated to drop the libapparmor- mention-dbus-method-in-getcon-man.patch patch and the dbus package should be updated to drop the aa-get-connection-apparmor-security- context.patch patch. To manage notifications about this bug go to: https://bugs.launchpad.net/online-accounts-api/+bug/1489489/+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 1489489] Re: The org.freedesktop.DBus.GetConnectionAppArmorSecurityContext() method is deprecated
** Changed in: lomiri-download-manager (Ubuntu) Status: New => In Progress ** Changed in: lomiri-download-manager (Ubuntu) Assignee: (unassigned) => Olivier Gayot (ogayot) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to content-hub in Ubuntu. https://bugs.launchpad.net/bugs/1489489 Title: The org.freedesktop.DBus.GetConnectionAppArmorSecurityContext() method is deprecated Status in Ubuntu Online Accounts API: Confirmed Status in snapd: Confirmed Status in apparmor package in Ubuntu: Fix Released Status in biometryd package in Ubuntu: New Status in content-hub package in Ubuntu: Confirmed Status in dbus package in Ubuntu: Triaged Status in deepin-notifications package in Ubuntu: New Status in lomiri-download-manager package in Ubuntu: In Progress Status in mediascanner2 package in Ubuntu: Fix Released Status in signon-apparmor-extension package in Ubuntu: Fix Released Status in ubuntu-system-settings-online-accounts package in Ubuntu: Fix Released Bug description: When upstream D-Bus merged the AppArmor mediation patches, they did not like the GetConnectionAppArmorSecurityContext() bus method. Instead, they decided to expose a peer's AppArmor context using the org.freedesktop.DBus.GetConnectionCredentials() bus method. All users of the GetConnectionAppArmorSecurityContext() method should switch to the GetConnectionCredentials() method as soon as possible so that Ubuntu can drop the patch that implements GetConnectionAppArmorSecurityContext() by the time 16.04 LTS is released. In order to switch to the new method, you'll need to depend on libapparmor 2.10 or newer. I'll be adding example code that illustrates how to switch from GetConnectionAppArmorSecurityContext() to GetConnectionCredentials(). content-hub, media-hub, mediascanner2, signon-apparmor-extension, ubuntu-download-manager, and ubuntu-system-settings-online-accounts all need to transition to the new method of obtaining the AppArmor label. The apparmor package should be updated to drop the libapparmor- mention-dbus-method-in-getcon-man.patch patch and the dbus package should be updated to drop the aa-get-connection-apparmor-security- context.patch patch. To manage notifications about this bug go to: https://bugs.launchpad.net/online-accounts-api/+bug/1489489/+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 2023322] Re: GTK internal browser does not render with Nvidia drivers
We believe the original bug is fixed in webkit2gtk 2.42.2 and higher on Ubuntu 22.04 LTS and newer with disable-dmabuf-nvidia.patch My understanding is that Ubuntu's Nvidia drivers include libnvidia-egl- gbm1 but Debian's drivers do not so that shouldn't be an issue. If you are still experiencing an issue, please file a new bug. You can use a command like this: ubuntu-bug libwebkit2gtk-4.0-37 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/2023322 Title: GTK internal browser does not render with Nvidia drivers Status in Webkit: Confirmed Status in gnome-control-center package in Ubuntu: Invalid Status in gnome-online-accounts package in Ubuntu: Invalid Status in webkit2gtk package in Ubuntu: Fix Released Status in yelp package in Ubuntu: Invalid Status in webkit2gtk package in Debian: Fix Released Bug description: When I go into Settings > Online Accounts > Google, I get to the prompt for email address, once in a while it stops accepting input there. But often I can get to the password screen. Once I do, I can't type anything or paste anything. This is a fresh install of Ubuntu 23.04 and I have installed all updates. Nothing in /var/crash Jun 08 11:15:59 CCW-HAL systemd[3523]: vte-spawn-8b4a59a3-a060-4bdd-92e6-285656bdb9a2.scope: Consumed 3.448s CPU time. Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:29 CCW-HAL systemd[3523]: Started app-gnome-org.gnome.Terminal-10924.scope - Application launched by gnome-shell. Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.167' (uid=1000 pid=10927 comm="/usr/bin/gnome-terminal.real" label="unconfined") Jun 08 11:16:29 CCW-HAL systemd[3523]: Starting gnome-terminal-server.service - GNOME Terminal Server... Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Successfully activated service 'org.gnome.Terminal' Jun 08 11:16:29 CCW-HAL systemd[3523]: Started gnome-terminal-server.service - GNOME Terminal Server. Jun 08 11:16:29 CCW-HAL systemd[3523]: Started vte-spawn-9cee1911-372a-4bb4-8b57-694984e43990.scope - VTE child process 10955 launched by gnome-terminal-server process 10931. Jun 08 11:16:49 CCW-HAL gnome-control-c[8079]: Error showing account: Child process exited with code 1 Jun 08 11:16:53 CCW-HAL gnome-online-accounts-panel.desktop[9764]: GLib-GIO: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - kerberosGoaBackend: activated kerberos providerGLib-GIO: _g_io_module_get_default: Found default implementation gnutls (GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialog was dismissed Jun 08 11:16:53 CCW-HAL xdg-desktop-por[3907]: Realtime error: Could not map pid: Could not determine pid namespace: Could not find instance-id in process's /.flatpak-info Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Jun 08 11:17:01 CCW-HAL CRON[11094]: (root) CMD (cd / && run-parts --report /etc/cron.hourly) Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session closed for user root Jun 08 11:17:06 CCW-HAL kernel: WebKitWebProces[11026]: segfault at 55bd22ad9adc ip 55bd22ad9adc sp 7ffd1f6adbe8 error 14 likely on CPU 2 (core 2, socket 0) Jun 08 11:17:06 CCW-HAL kernel: Code: Unable to access opcode bytes at 0x55bd22ad9ab2. Jun 08 11:17:36 CCW-HAL gnome-shell[3803]: Window manager warning: WM_TRANSIENT_FOR window 0x3a02767 for 0x3a02778 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x3a006dc. Jun 08 11:17:42 CCW-HAL systemd[1]: Starting systemd-tmpfiles-clean.service - Cleanup of Temporary Directories... Jun 08 11:17:42 CCW-HAL systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully. Jun 08 11:17:42 CCW-HAL systemd[1]: Finished systemd-tmpfiles-clean.service -
[Touch-packages] [Bug 2045621] Re: Improve power consumption on Framework systems
For Jammy, Lunar, and Mantic, the correct fix is to add these rules in a 90-ubuntu-autosuspend.hwdb file in systemd-hwe. ** Changed in: systemd (Ubuntu Jammy) Status: Confirmed => Won't Fix ** Changed in: systemd (Ubuntu Lunar) Status: Confirmed => Won't Fix ** Changed in: systemd (Ubuntu Mantic) Status: Confirmed => Won't Fix -- 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/2045621 Title: Improve power consumption on Framework systems Status in OEM Priority Project: In Progress Status in systemd package in Ubuntu: Fix Committed Status in systemd-hwe package in Ubuntu: Invalid Status in systemd source package in Jammy: Won't Fix Status in systemd-hwe source package in Jammy: Confirmed Status in systemd source package in Lunar: Won't Fix Status in systemd-hwe source package in Lunar: Confirmed Status in systemd source package in Mantic: Won't Fix Status in systemd-hwe source package in Mantic: Confirmed Status in systemd source package in Noble: Fix Committed Status in systemd-hwe source package in Noble: Invalid Bug description: [ Impact ] * Framework systems that have DP or HDMI cards connected will have increased power consumption even when nothing is connected to DP or HDMI ports since the cards don't default to autosuspend. * Backporting upstream patch that adds rules in hwdb.d/60-autosuspend.hwdb for Framework's HDMI and DP extensions. [ Test Plan ] * DUT: Framework with DP and HDMI: $ lsusb | grep Framework Bus 007 Device 002: ID 32ac:0003 Framework DisplayPort Expansion Card Bus 001 Device 002: ID 32ac:0002 Framework HDMI Expansion Card 1. Autosuspend is not enabled before patch. Set to "on" in power/control $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-1/manufacturer Framework $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-1/power/control on $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-2/manufacturer Framework $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-2/power/control on 2. Install patch 3. Autosuspend is enabled for both extensions. Set to "auto" in power/control $ cat power/control auto [ Where problems could occur ] * During testing verified that both DP+HDMI display show good output after hot-plug, system suspend, and reboot. There might be some differences when hibernate and hotplug. [ Other Info ] * https://github.com/systemd/systemd/commit/9023630cb7025650aa4d01ee794b0bb68bfdf2c1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2045621/+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 2045075] Re: Framework Laptop Expansion Card enabling auto suspend
*** This bug is a duplicate of bug 2045621 *** https://bugs.launchpad.net/bugs/2045621 It seems bug (bug 2045621) has been opened which is proposing the same thing. That one has the SRU info required, so let's carry on there instead. ** This bug has been marked a duplicate of bug 2045621 Improve power consumption on Framework systems -- 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/2045075 Title: Framework Laptop Expansion Card enabling auto suspend Status in systemd package in Ubuntu: Invalid Status in systemd-hwe package in Ubuntu: Won't Fix Status in systemd-hwe source package in Jammy: Triaged Status in systemd-hwe source package in Lunar: Triaged Status in systemd-hwe source package in Mantic: Triaged Bug description: Framework provides expansion cards. For the HDMI and DisplayPort, these benefit power management via enabling auto suspend. Ubuntu 22.04.3 LTS 6.1.0-1026-oem systemd 249 (249.11-0ubuntu3.11) # # Framework # # HDMI Expansion Card usb:v32ACp0002* # DisplayPort Expansion Card usb:v32ACp0003* ID_AUTOSUSPEND=1 Commit in question: https://github.com/systemd/systemd/commit/9023630cb7025650aa4d01ee794b0bb68bfdf2c1 When looking at 60-autosuspend.hwdb for Ubuntu 22.04.3, we do not have the additional entry shown above available for HDMI and DisplayPort expansion cards. I'd like to see this added to 22.04 for future inclusion. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2045075/+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 2037906] Re: [Intel AX201] Bluetooth LE not working after upgrade from 22.04 to 23.10
ubuntu 23.10
kernel 6.5.0-14-generic
ASUS Vivobook X1504VA
new installation (in 22.04 I first tried it didn't recognize wifi either, so I
installed 23.10)
issue: bluetooth cannot startup. it says "turn on bluetooth to connect devices"
expected: to be able to turn on bluetooth and connect to devices
what I've tried:
0) boot with kernel 6.5.0-13 instead of 6.5.0-14. Nothing changed.
1) installing linux-image-6.5.0-1003-intel-opt with modules and extras. Nothing
happened, uninstalled
2) install --reinstall bluez gnome-bluetooth indicator-bluetooth
pulseaudio-module-bluetooth. Nothing happened, I left them installed
3) install libspa-0.2-bluetooth blueman-manager. Nothing happened, uninstalled.
4) /etc/init.d/bluetooth restart. Nothing happened.
5) systemctl restart bluetooth. Nothing happened.
All the above tried in reverse order with sudo command and reboot after every
try.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2037906
Title:
[Intel AX201] Bluetooth LE not working after upgrade from 22.04 to
23.10
Status in Linux Firmware:
New
Status in bluez package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Bug description:
syslog:
2023-09-20T09:32:54.138852+02:00 zaionc kernel: [ 13.539860] Bluetooth:
hci0: Waiting for firmware download to complete
2023-09-20T09:32:54.138857+02:00 zaionc kernel: [ 13.540223] Bluetooth:
hci0: Firmware loaded in 1706498 usecs
2023-09-20T09:32:54.138858+02:00 zaionc kernel: [ 13.540278] Bluetooth:
hci0: Waiting for device to boot
2023-09-20T09:32:54.154894+02:00 zaionc kernel: [ 13.555430] Bluetooth:
hci0: Malformed MSFT vendor event: 0x02
2023-09-20T09:32:54.154908+02:00 zaionc kernel: [ 13.555482] Bluetooth:
hci0: Device booted in 14872 usecs
2023-09-20T09:32:54.154910+02:00 zaionc kernel: [ 13.555913] Bluetooth:
hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc
2023-09-20T09:32:54.158856+02:00 zaionc kernel: [ 13.558300] Bluetooth:
hci0: Applying Intel DDC parameters completed
2023-09-20T09:32:54.158859+02:00 zaionc kernel: [ 13.559326] Bluetooth:
hci0: Firmware revision 0.4 build 249 week 27 2023
lshw:
*-usb:5
description: Bluetooth wireless interface
product: AX201 Bluetooth
vendor: Intel Corp.
physical id: a
bus info: usb@3:a
version: 0.02
capabilities: bluetooth usb-2.01
configuration: driver=btusb maxpower=100mA speed=12Mbit/s
root@zaionc:~# hcitool lescan
Set scan parameters failed: Input/output error
At first bluetooth stopped working at all due to Ubuntu bug = missing
firmware. It was fixed recently and now the bluetooth module seems
fine, but the whole BTLE part is not available. Particularly I cannot
detect/pair Logitech M720 mouse.
Platform: ThinkPad T14 Gen 2i
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2022-05-28 (494 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
Package: linux
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic
root=UUID=d0002130-adf6-4f18-93b1-fda536d8b499 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
RebootRequiredPkgs: Error: path contained symlinks.
Tags: mantic
Uname: Linux 6.5.0-5-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-09-03 (30 days ago)
UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/10/2023
dmi.bios.release: 1.56
dmi.bios.vendor: LENOVO
dmi.bios.version: N34ET56W (1.56 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20W000AMPB
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.42
dmi.modalias:
dmi:bvnLENOVO:bvrN34ET56W(1.56):bd05/10/2023:br1.56:efr1.42:svnLENOVO:pn20W000AMPB:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W000AMPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i:
dmi.product.family: ThinkPad T14 Gen 2i
dmi.product.name: 20W000AMPB
dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i
dmi.product.version: ThinkPad T14 Gen 2i
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: A0:E7:0B:23:70:E8 ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING
[Touch-packages] [Bug 2037906] Re: [Intel AX201] Bluetooth LE not working after upgrade from 22.04 to 23.10
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bluez (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2037906
Title:
[Intel AX201] Bluetooth LE not working after upgrade from 22.04 to
23.10
Status in Linux Firmware:
New
Status in bluez package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Bug description:
syslog:
2023-09-20T09:32:54.138852+02:00 zaionc kernel: [ 13.539860] Bluetooth:
hci0: Waiting for firmware download to complete
2023-09-20T09:32:54.138857+02:00 zaionc kernel: [ 13.540223] Bluetooth:
hci0: Firmware loaded in 1706498 usecs
2023-09-20T09:32:54.138858+02:00 zaionc kernel: [ 13.540278] Bluetooth:
hci0: Waiting for device to boot
2023-09-20T09:32:54.154894+02:00 zaionc kernel: [ 13.555430] Bluetooth:
hci0: Malformed MSFT vendor event: 0x02
2023-09-20T09:32:54.154908+02:00 zaionc kernel: [ 13.555482] Bluetooth:
hci0: Device booted in 14872 usecs
2023-09-20T09:32:54.154910+02:00 zaionc kernel: [ 13.555913] Bluetooth:
hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc
2023-09-20T09:32:54.158856+02:00 zaionc kernel: [ 13.558300] Bluetooth:
hci0: Applying Intel DDC parameters completed
2023-09-20T09:32:54.158859+02:00 zaionc kernel: [ 13.559326] Bluetooth:
hci0: Firmware revision 0.4 build 249 week 27 2023
lshw:
*-usb:5
description: Bluetooth wireless interface
product: AX201 Bluetooth
vendor: Intel Corp.
physical id: a
bus info: usb@3:a
version: 0.02
capabilities: bluetooth usb-2.01
configuration: driver=btusb maxpower=100mA speed=12Mbit/s
root@zaionc:~# hcitool lescan
Set scan parameters failed: Input/output error
At first bluetooth stopped working at all due to Ubuntu bug = missing
firmware. It was fixed recently and now the bluetooth module seems
fine, but the whole BTLE part is not available. Particularly I cannot
detect/pair Logitech M720 mouse.
Platform: ThinkPad T14 Gen 2i
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2022-05-28 (494 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
Package: linux
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic
root=UUID=d0002130-adf6-4f18-93b1-fda536d8b499 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
RebootRequiredPkgs: Error: path contained symlinks.
Tags: mantic
Uname: Linux 6.5.0-5-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-09-03 (30 days ago)
UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/10/2023
dmi.bios.release: 1.56
dmi.bios.vendor: LENOVO
dmi.bios.version: N34ET56W (1.56 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20W000AMPB
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.42
dmi.modalias:
dmi:bvnLENOVO:bvrN34ET56W(1.56):bd05/10/2023:br1.56:efr1.42:svnLENOVO:pn20W000AMPB:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W000AMPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i:
dmi.product.family: ThinkPad T14 Gen 2i
dmi.product.name: 20W000AMPB
dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i
dmi.product.version: ThinkPad T14 Gen 2i
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: A0:E7:0B:23:70:E8 ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING
RX bytes:22183 acl:0 sco:0 events:3531 errors:0
TX bytes:821193 acl:0 sco:0 commands:3510 errors:0
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux-firmware/+bug/2037906/+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 2038834] Update Released
The verification of the Stable Release Update for mesa has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2038834 Title: GPU acceleration via VirGL is broken in qemu Status in Release Notes for Ubuntu: New Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Mantic: Fix Released Status in mesa source package in Noble: Fix Released Bug description: [ Impact ] * Enabling GPU acceleration can cause host-side crashes on mantic/noble VMs * This was reported by someone else upstream and is already fixed by https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25580. [ Test Plan ] * I've tested the patch on an affected macOS host running Ubuntu in UTM with OpenGL enabled on both Mantic and Noble VMs. * Anyone else can do the same on an affected host by simply installing the patched package and booting to the desktop. [ Where problems could occur ] * This patch fixes an upstream mesa regression which caused libvirglrendrer to crash on the host side. * This makes a non-working use case work, VirGL on affected hosts cannot regress as it simply didn't work before. * Risk of breakage is mainly from other packages possible affected by a mesa rebuild. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2038834/+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 2038834] Re: GPU acceleration via VirGL is broken in qemu
This bug was fixed in the package mesa - 23.2.1-1ubuntu3.1 --- mesa (23.2.1-1ubuntu3.1) mantic; urgency=medium * patches: Avoid crashing virglrenderer when the host doesn't support PIPE_CAP_CLEAR_TEXTURE (LP: #2038834) -- Mate Kukri Tue, 07 Nov 2023 15:41:32 +0200 ** Changed in: mesa (Ubuntu Mantic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2038834 Title: GPU acceleration via VirGL is broken in qemu Status in Release Notes for Ubuntu: New Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Mantic: Fix Released Status in mesa source package in Noble: Fix Released Bug description: [ Impact ] * Enabling GPU acceleration can cause host-side crashes on mantic/noble VMs * This was reported by someone else upstream and is already fixed by https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25580. [ Test Plan ] * I've tested the patch on an affected macOS host running Ubuntu in UTM with OpenGL enabled on both Mantic and Noble VMs. * Anyone else can do the same on an affected host by simply installing the patched package and booting to the desktop. [ Where problems could occur ] * This patch fixes an upstream mesa regression which caused libvirglrendrer to crash on the host side. * This makes a non-working use case work, VirGL on affected hosts cannot regress as it simply didn't work before. * Risk of breakage is mainly from other packages possible affected by a mesa rebuild. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2038834/+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 2045621] Re: Improve power consumption on Framework systems
** Tags added: amd originate-from-2044861 -- 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/2045621 Title: Improve power consumption on Framework systems Status in OEM Priority Project: In Progress Status in systemd package in Ubuntu: Fix Committed Status in systemd-hwe package in Ubuntu: Invalid Status in systemd source package in Jammy: Confirmed Status in systemd-hwe source package in Jammy: Confirmed Status in systemd source package in Lunar: Confirmed Status in systemd-hwe source package in Lunar: Confirmed Status in systemd source package in Mantic: Confirmed Status in systemd-hwe source package in Mantic: Confirmed Status in systemd source package in Noble: Fix Committed Status in systemd-hwe source package in Noble: Invalid Bug description: [ Impact ] * Framework systems that have DP or HDMI cards connected will have increased power consumption even when nothing is connected to DP or HDMI ports since the cards don't default to autosuspend. * Backporting upstream patch that adds rules in hwdb.d/60-autosuspend.hwdb for Framework's HDMI and DP extensions. [ Test Plan ] * DUT: Framework with DP and HDMI: $ lsusb | grep Framework Bus 007 Device 002: ID 32ac:0003 Framework DisplayPort Expansion Card Bus 001 Device 002: ID 32ac:0002 Framework HDMI Expansion Card 1. Autosuspend is not enabled before patch. Set to "on" in power/control $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-1/manufacturer Framework $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-1/power/control on $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-2/manufacturer Framework $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-2/power/control on 2. Install patch 3. Autosuspend is enabled for both extensions. Set to "auto" in power/control $ cat power/control auto [ Where problems could occur ] * During testing verified that both DP+HDMI display show good output after hot-plug, system suspend, and reboot. There might be some differences when hibernate and hotplug. [ Other Info ] * https://github.com/systemd/systemd/commit/9023630cb7025650aa4d01ee794b0bb68bfdf2c1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2045621/+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 2045621] Re: Improve power consumption on Framework systems
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd-hwe (Ubuntu Mantic) Status: New => Confirmed -- 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/2045621 Title: Improve power consumption on Framework systems Status in OEM Priority Project: In Progress Status in systemd package in Ubuntu: Fix Committed Status in systemd-hwe package in Ubuntu: Invalid Status in systemd source package in Jammy: Confirmed Status in systemd-hwe source package in Jammy: Confirmed Status in systemd source package in Lunar: Confirmed Status in systemd-hwe source package in Lunar: Confirmed Status in systemd source package in Mantic: Confirmed Status in systemd-hwe source package in Mantic: Confirmed Status in systemd source package in Noble: Fix Committed Status in systemd-hwe source package in Noble: Invalid Bug description: [ Impact ] * Framework systems that have DP or HDMI cards connected will have increased power consumption even when nothing is connected to DP or HDMI ports since the cards don't default to autosuspend. * Backporting upstream patch that adds rules in hwdb.d/60-autosuspend.hwdb for Framework's HDMI and DP extensions. [ Test Plan ] * DUT: Framework with DP and HDMI: $ lsusb | grep Framework Bus 007 Device 002: ID 32ac:0003 Framework DisplayPort Expansion Card Bus 001 Device 002: ID 32ac:0002 Framework HDMI Expansion Card 1. Autosuspend is not enabled before patch. Set to "on" in power/control $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-1/manufacturer Framework $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-1/power/control on $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-2/manufacturer Framework $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-2/power/control on 2. Install patch 3. Autosuspend is enabled for both extensions. Set to "auto" in power/control $ cat power/control auto [ Where problems could occur ] * During testing verified that both DP+HDMI display show good output after hot-plug, system suspend, and reboot. There might be some differences when hibernate and hotplug. [ Other Info ] * https://github.com/systemd/systemd/commit/9023630cb7025650aa4d01ee794b0bb68bfdf2c1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2045621/+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 2045621] Re: Improve power consumption on Framework systems
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu Mantic) Status: New => Confirmed -- 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/2045621 Title: Improve power consumption on Framework systems Status in OEM Priority Project: In Progress Status in systemd package in Ubuntu: Fix Committed Status in systemd-hwe package in Ubuntu: Invalid Status in systemd source package in Jammy: Confirmed Status in systemd-hwe source package in Jammy: Confirmed Status in systemd source package in Lunar: Confirmed Status in systemd-hwe source package in Lunar: Confirmed Status in systemd source package in Mantic: Confirmed Status in systemd-hwe source package in Mantic: Confirmed Status in systemd source package in Noble: Fix Committed Status in systemd-hwe source package in Noble: Invalid Bug description: [ Impact ] * Framework systems that have DP or HDMI cards connected will have increased power consumption even when nothing is connected to DP or HDMI ports since the cards don't default to autosuspend. * Backporting upstream patch that adds rules in hwdb.d/60-autosuspend.hwdb for Framework's HDMI and DP extensions. [ Test Plan ] * DUT: Framework with DP and HDMI: $ lsusb | grep Framework Bus 007 Device 002: ID 32ac:0003 Framework DisplayPort Expansion Card Bus 001 Device 002: ID 32ac:0002 Framework HDMI Expansion Card 1. Autosuspend is not enabled before patch. Set to "on" in power/control $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-1/manufacturer Framework $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-1/power/control on $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-2/manufacturer Framework $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-2/power/control on 2. Install patch 3. Autosuspend is enabled for both extensions. Set to "auto" in power/control $ cat power/control auto [ Where problems could occur ] * During testing verified that both DP+HDMI display show good output after hot-plug, system suspend, and reboot. There might be some differences when hibernate and hotplug. [ Other Info ] * https://github.com/systemd/systemd/commit/9023630cb7025650aa4d01ee794b0bb68bfdf2c1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2045621/+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 2045621] Re: Improve power consumption on Framework systems
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu Lunar) Status: New => Confirmed -- 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/2045621 Title: Improve power consumption on Framework systems Status in OEM Priority Project: In Progress Status in systemd package in Ubuntu: Fix Committed Status in systemd-hwe package in Ubuntu: Invalid Status in systemd source package in Jammy: Confirmed Status in systemd-hwe source package in Jammy: Confirmed Status in systemd source package in Lunar: Confirmed Status in systemd-hwe source package in Lunar: Confirmed Status in systemd source package in Mantic: Confirmed Status in systemd-hwe source package in Mantic: Confirmed Status in systemd source package in Noble: Fix Committed Status in systemd-hwe source package in Noble: Invalid Bug description: [ Impact ] * Framework systems that have DP or HDMI cards connected will have increased power consumption even when nothing is connected to DP or HDMI ports since the cards don't default to autosuspend. * Backporting upstream patch that adds rules in hwdb.d/60-autosuspend.hwdb for Framework's HDMI and DP extensions. [ Test Plan ] * DUT: Framework with DP and HDMI: $ lsusb | grep Framework Bus 007 Device 002: ID 32ac:0003 Framework DisplayPort Expansion Card Bus 001 Device 002: ID 32ac:0002 Framework HDMI Expansion Card 1. Autosuspend is not enabled before patch. Set to "on" in power/control $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-1/manufacturer Framework $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-1/power/control on $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-2/manufacturer Framework $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-2/power/control on 2. Install patch 3. Autosuspend is enabled for both extensions. Set to "auto" in power/control $ cat power/control auto [ Where problems could occur ] * During testing verified that both DP+HDMI display show good output after hot-plug, system suspend, and reboot. There might be some differences when hibernate and hotplug. [ Other Info ] * https://github.com/systemd/systemd/commit/9023630cb7025650aa4d01ee794b0bb68bfdf2c1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2045621/+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
