Activity log for bug #1881522

Date Who What changed Old value New value Message
2020-06-01 04:33:01 Willian bug added bug
2020-06-01 04:45:15 Willian description When installing a new server with Ubuntu 20.04 LTS with vtun_3.0.4-2_amd64.deb does not run the service. It has possibly errors in the compilation for Ubuntu Focal. It runs normally on version 3.0.3-4build1 on Ubuntu 18.04 and also on the version of the package available in the Debian repository in the same version at: http://ftp.us.debian.org/debian/pool/main/v/vtun /vtun_3.0.4-2_amd64.deb Error log in the current version Ubuntu(Focal). vtun_3.0.4-2_amd64.deb: Exact Size 61068 Byte (59.6 kByte) May 20 01:44:05 server vtun [3177]: * Starting virtual tunnel daemon server vtun May 20 01:44:05 server vtun [3186]: VTun see 3.X 11/11/2019 May 20 01:44:05 server vtun [3186]: Usage: May 20 01:44:05 server vtun [3186]: Server: May 20 01:44:05 server vtun [3186]: # 011vtund <-i> [-f file] [-P port] [-L local address] May 20 01:44:05 server vtun [3186]: Client: May 20 01:44:05 server vtun [3186]: # 011vtund [-f file] [-q] [-p] [-m] [-t timeout] <host profile> <server address> May 20 01:44:05 server systemd [1]: vtun.service: Control process exited, code = exited, status = 1 / FAILURE May 20 01:44:05 server systemd [1]: vtun.service: Failed with result 'exit-code'. May 20 01:44:05 server systemd [1]: Failed to start LSB: virtual tunnel over TCP / IP networks. In the version that works the following return: VTun ver 3.X 02/05/2018 Usage: Server: vtund <-s> [-f file] [-P port] [-L local address] Client: vtund [-f file] [-p] [-m] [-t timeout] <host profile> <server address> Version running of Debian: vtun_3.0.4-2_amd64.deb: Exact Size 71124 Byte (69.5 kByte) VTun ver 3.X 11/11/2019 Usage: Server: vtund <-s | -i> [-f file] [-P port] [-L local address] Client: vtund [-f file] [-q] [-p] [-m] [-t timeout] <host profile> <server address> In the log error, such as option -i in the new version Focal and in the previous versions running, -s for the server environment. #lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 vtun: Installed: 3.0.4-2 Candidate: 3.0.4-2 Version table: 3.0.4-2 500 500 http://br.archive.ubuntu.com/ubuntu focal/universe amd64 Packages *** 3.0.4-2 100 100 /var/lib/dpkg/status When installing a new server with Ubuntu 20.04 LTS with tun_3.0.4-2_amd64 does not run the service. It has possibly errors in the compilation for Ubuntu Focal. It runs normally on version 3.0.3-4build1 on Ubuntu 18.04 and also on the version of the package available in the Debian repository in the same version at: http://ftp.us.debian.org/debian/pool/main/v/vtun/vtun_3.0.4-2_amd64.deb Error log in the current version Ubuntu(Focal). vtun_3.0.4-2_amd64.deb: Exact Size 61068 Byte (59.6 kByte) May 20 01:44:05 server vtun [3177]: * Starting virtual tunnel daemon server vtun May 20 01:44:05 server vtun [3186]: VTun see 3.X 11/11/2019 May 20 01:44:05 server vtun [3186]: Usage: May 20 01:44:05 server vtun [3186]: Server: May 20 01:44:05 server vtun [3186]: # 011vtund <-i> [-f file] [-P port] [-L local address] May 20 01:44:05 server vtun [3186]: Client: May 20 01:44:05 server vtun [3186]: # 011vtund [-f file] [-q] [-p] [-m] [-t timeout] <host profile> <server address> May 20 01:44:05 server systemd [1]: vtun.service: Control process exited, code = exited, status = 1 / FAILURE May 20 01:44:05 server systemd [1]: vtun.service: Failed with result 'exit-code'. May 20 01:44:05 server systemd [1]: Failed to start LSB: virtual tunnel over TCP / IP networks. In the version that works the following return: VTun ver 3.X 02/05/2018 Usage:   Server:         vtund <-s> [-f file] [-P port] [-L local address]   Client:         vtund [-f file] [-p] [-m] [-t timeout] <host profile> <server address> Version running of Debian repository: vtun_3.0.4-2_amd64.deb: Exact Size 71124 Byte (69.5 kByte) VTun ver 3.X 11/11/2019 Usage:   Server:         vtund <-s | -i> [-f file] [-P port] [-L local address]   Client:         vtund [-f file] [-q] [-p] [-m] [-t timeout] <host profile> <server address> In the log error, such as option -i in the new version Focal and in the previous versions running, -s for the server environment. #lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 vtun:    Installed: 3.0.4-2    Candidate: 3.0.4-2    Version table:      3.0.4-2 500         500 http://br.archive.ubuntu.com/ubuntu focal/universe amd64 Packages  *** 3.0.4-2 100         100 /var/lib/dpkg/status
2020-06-02 06:36:58 Willian description When installing a new server with Ubuntu 20.04 LTS with tun_3.0.4-2_amd64 does not run the service. It has possibly errors in the compilation for Ubuntu Focal. It runs normally on version 3.0.3-4build1 on Ubuntu 18.04 and also on the version of the package available in the Debian repository in the same version at: http://ftp.us.debian.org/debian/pool/main/v/vtun/vtun_3.0.4-2_amd64.deb Error log in the current version Ubuntu(Focal). vtun_3.0.4-2_amd64.deb: Exact Size 61068 Byte (59.6 kByte) May 20 01:44:05 server vtun [3177]: * Starting virtual tunnel daemon server vtun May 20 01:44:05 server vtun [3186]: VTun see 3.X 11/11/2019 May 20 01:44:05 server vtun [3186]: Usage: May 20 01:44:05 server vtun [3186]: Server: May 20 01:44:05 server vtun [3186]: # 011vtund <-i> [-f file] [-P port] [-L local address] May 20 01:44:05 server vtun [3186]: Client: May 20 01:44:05 server vtun [3186]: # 011vtund [-f file] [-q] [-p] [-m] [-t timeout] <host profile> <server address> May 20 01:44:05 server systemd [1]: vtun.service: Control process exited, code = exited, status = 1 / FAILURE May 20 01:44:05 server systemd [1]: vtun.service: Failed with result 'exit-code'. May 20 01:44:05 server systemd [1]: Failed to start LSB: virtual tunnel over TCP / IP networks. In the version that works the following return: VTun ver 3.X 02/05/2018 Usage:   Server:         vtund <-s> [-f file] [-P port] [-L local address]   Client:         vtund [-f file] [-p] [-m] [-t timeout] <host profile> <server address> Version running of Debian repository: vtun_3.0.4-2_amd64.deb: Exact Size 71124 Byte (69.5 kByte) VTun ver 3.X 11/11/2019 Usage:   Server:         vtund <-s | -i> [-f file] [-P port] [-L local address]   Client:         vtund [-f file] [-q] [-p] [-m] [-t timeout] <host profile> <server address> In the log error, such as option -i in the new version Focal and in the previous versions running, -s for the server environment. #lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 vtun:    Installed: 3.0.4-2    Candidate: 3.0.4-2    Version table:      3.0.4-2 500         500 http://br.archive.ubuntu.com/ubuntu focal/universe amd64 Packages  *** 3.0.4-2 100         100 /var/lib/dpkg/status When installing a new server with Ubuntu 20.04 LTS with vtun_3.0.4-2_amd64 does not run the service. It has possibly errors in the compilation for Ubuntu Focal. It runs normally on version 3.0.3-4build1 on Ubuntu 18.04 and also on the version of the package available in the Debian repository in the same version at: http://ftp.us.debian.org/debian/pool/main/v/vtun/vtun_3.0.4-2_amd64.deb Error log in the current version Ubuntu(Focal). vtun_3.0.4-2_amd64.deb: Exact Size 61068 Byte (59.6 kByte) May 20 01:44:05 server vtun [3177]: * Starting virtual tunnel daemon server vtun May 20 01:44:05 server vtun [3186]: VTun see 3.X 11/11/2019 May 20 01:44:05 server vtun [3186]: Usage: May 20 01:44:05 server vtun [3186]: Server: May 20 01:44:05 server vtun [3186]: # 011vtund <-i> [-f file] [-P port] [-L local address] May 20 01:44:05 server vtun [3186]: Client: May 20 01:44:05 server vtun [3186]: # 011vtund [-f file] [-q] [-p] [-m] [-t timeout] <host profile> <server address> May 20 01:44:05 server systemd [1]: vtun.service: Control process exited, code = exited, status = 1 / FAILURE May 20 01:44:05 server systemd [1]: vtun.service: Failed with result 'exit-code'. May 20 01:44:05 server systemd [1]: Failed to start LSB: virtual tunnel over TCP / IP networks. In the version that works the following return: VTun ver 3.X 02/05/2018 Usage:   Server:         vtund <-s> [-f file] [-P port] [-L local address]   Client:         vtund [-f file] [-p] [-m] [-t timeout] <host profile> <server address> Version running of Debian repository: vtun_3.0.4-2_amd64.deb: Exact Size 71124 Byte (69.5 kByte) VTun ver 3.X 11/11/2019 Usage:   Server:         vtund <-s | -i> [-f file] [-P port] [-L local address]   Client:         vtund [-f file] [-q] [-p] [-m] [-t timeout] <host profile> <server address> In the log error, such as option -i in the new version Focal and in the previous versions running, -s for the server environment. #lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 vtun:    Installed: 3.0.4-2    Candidate: 3.0.4-2    Version table:      3.0.4-2 500         500 http://br.archive.ubuntu.com/ubuntu focal/universe amd64 Packages  *** 3.0.4-2 100         100 /var/lib/dpkg/status
2020-06-05 03:19:50 Willian description When installing a new server with Ubuntu 20.04 LTS with vtun_3.0.4-2_amd64 does not run the service. It has possibly errors in the compilation for Ubuntu Focal. It runs normally on version 3.0.3-4build1 on Ubuntu 18.04 and also on the version of the package available in the Debian repository in the same version at: http://ftp.us.debian.org/debian/pool/main/v/vtun/vtun_3.0.4-2_amd64.deb Error log in the current version Ubuntu(Focal). vtun_3.0.4-2_amd64.deb: Exact Size 61068 Byte (59.6 kByte) May 20 01:44:05 server vtun [3177]: * Starting virtual tunnel daemon server vtun May 20 01:44:05 server vtun [3186]: VTun see 3.X 11/11/2019 May 20 01:44:05 server vtun [3186]: Usage: May 20 01:44:05 server vtun [3186]: Server: May 20 01:44:05 server vtun [3186]: # 011vtund <-i> [-f file] [-P port] [-L local address] May 20 01:44:05 server vtun [3186]: Client: May 20 01:44:05 server vtun [3186]: # 011vtund [-f file] [-q] [-p] [-m] [-t timeout] <host profile> <server address> May 20 01:44:05 server systemd [1]: vtun.service: Control process exited, code = exited, status = 1 / FAILURE May 20 01:44:05 server systemd [1]: vtun.service: Failed with result 'exit-code'. May 20 01:44:05 server systemd [1]: Failed to start LSB: virtual tunnel over TCP / IP networks. In the version that works the following return: VTun ver 3.X 02/05/2018 Usage:   Server:         vtund <-s> [-f file] [-P port] [-L local address]   Client:         vtund [-f file] [-p] [-m] [-t timeout] <host profile> <server address> Version running of Debian repository: vtun_3.0.4-2_amd64.deb: Exact Size 71124 Byte (69.5 kByte) VTun ver 3.X 11/11/2019 Usage:   Server:         vtund <-s | -i> [-f file] [-P port] [-L local address]   Client:         vtund [-f file] [-q] [-p] [-m] [-t timeout] <host profile> <server address> In the log error, such as option -i in the new version Focal and in the previous versions running, -s for the server environment. #lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 vtun:    Installed: 3.0.4-2    Candidate: 3.0.4-2    Version table:      3.0.4-2 500         500 http://br.archive.ubuntu.com/ubuntu focal/universe amd64 Packages  *** 3.0.4-2 100         100 /var/lib/dpkg/status When installing a new server with Ubuntu 20.04 LTS with vtun_3.0.4-2_amd64 does not run the service as a server. It has possibly errors in the compilation for Ubuntu Focal. It runs normally on version 3.0.3-4build1 on Ubuntu 18.04 and also on the version of the package available in the Debian repository in the same version at: http://ftp.us.debian.org/debian/pool/main/v/vtun/vtun_3.0.4-2_amd64.deb Error log in the current version Ubuntu(Focal). vtun_3.0.4-2_amd64.deb: Exact Size 61068 Byte (59.6 kByte) May 20 01:44:05 server vtun [3177]: * Starting virtual tunnel daemon server vtun May 20 01:44:05 server vtun [3186]: VTun see 3.X 11/11/2019 May 20 01:44:05 server vtun [3186]: Usage: May 20 01:44:05 server vtun [3186]: Server: May 20 01:44:05 server vtun [3186]: # 011vtund <-i> [-f file] [-P port] [-L local address] May 20 01:44:05 server vtun [3186]: Client: May 20 01:44:05 server vtun [3186]: # 011vtund [-f file] [-q] [-p] [-m] [-t timeout] <host profile> <server address> May 20 01:44:05 server systemd [1]: vtun.service: Control process exited, code = exited, status = 1 / FAILURE May 20 01:44:05 server systemd [1]: vtun.service: Failed with result 'exit-code'. May 20 01:44:05 server systemd [1]: Failed to start LSB: virtual tunnel over TCP / IP networks. In the version that works the following return: VTun ver 3.X 02/05/2018 Usage:   Server:         vtund <-s> [-f file] [-P port] [-L local address]   Client:         vtund [-f file] [-p] [-m] [-t timeout] <host profile> <server address> Version running of Debian repository: vtun_3.0.4-2_amd64.deb: Exact Size 71124 Byte (69.5 kByte) VTun ver 3.X 11/11/2019 Usage:   Server:         vtund <-s | -i> [-f file] [-P port] [-L local address]   Client:         vtund [-f file] [-q] [-p] [-m] [-t timeout] <host profile> <server address> In the log error, such as option -i in the new version Focal and in the previous versions running, -s for the server environment. #lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 vtun:    Installed: 3.0.4-2    Candidate: 3.0.4-2    Version table:      3.0.4-2 500         500 http://br.archive.ubuntu.com/ubuntu focal/universe amd64 Packages  *** 3.0.4-2 100         100 /var/lib/dpkg/status
2021-10-01 18:50:12 Launchpad Janitor vtun (Ubuntu): status New Confirmed
2022-03-08 08:19:48 Stefán Heiðberg Halldórsson bug added subscriber Stefán Heiðberg Halldórsson
2024-02-07 19:34:34 Sudip Mukherjee bug added subscriber Sudip Mukherjee
2024-02-07 20:10:01 C de-Avillez nominated for series Ubuntu Mantic
2024-02-07 20:10:01 C de-Avillez bug task added vtun (Ubuntu Mantic)
2024-02-07 20:10:01 C de-Avillez nominated for series Ubuntu Jammy
2024-02-07 20:10:01 C de-Avillez bug task added vtun (Ubuntu Jammy)
2024-02-07 20:10:01 C de-Avillez nominated for series Ubuntu Noble
2024-02-07 20:10:01 C de-Avillez bug task added vtun (Ubuntu Noble)
2024-02-07 20:10:01 C de-Avillez nominated for series Ubuntu Focal
2024-02-07 20:10:01 C de-Avillez bug task added vtun (Ubuntu Focal)
2024-02-07 21:27:15 Sudip Mukherjee vtun (Ubuntu Focal): assignee Sudip Mukherjee (sudipmuk)
2024-02-07 21:27:17 Sudip Mukherjee vtun (Ubuntu Jammy): assignee Sudip Mukherjee (sudipmuk)
2024-02-07 21:27:19 Sudip Mukherjee vtun (Ubuntu Mantic): assignee Sudip Mukherjee (sudipmuk)
2024-02-07 21:27:21 Sudip Mukherjee vtun (Ubuntu Noble): assignee Sudip Mukherjee (sudipmuk)
2024-02-07 21:27:25 Sudip Mukherjee vtun (Ubuntu Focal): status New In Progress
2024-02-07 21:27:28 Sudip Mukherjee vtun (Ubuntu Jammy): status New In Progress
2024-02-07 21:27:30 Sudip Mukherjee vtun (Ubuntu Mantic): status New In Progress
2024-02-07 21:27:33 Sudip Mukherjee vtun (Ubuntu Noble): status Confirmed In Progress
2024-02-10 10:44:18 Sudip Mukherjee summary vtun not running on ubuntu 20.04 LTS [SRU] vtun not running on ubuntu 20.04 LTS
2024-02-10 10:44:38 Sudip Mukherjee description When installing a new server with Ubuntu 20.04 LTS with vtun_3.0.4-2_amd64 does not run the service as a server. It has possibly errors in the compilation for Ubuntu Focal. It runs normally on version 3.0.3-4build1 on Ubuntu 18.04 and also on the version of the package available in the Debian repository in the same version at: http://ftp.us.debian.org/debian/pool/main/v/vtun/vtun_3.0.4-2_amd64.deb Error log in the current version Ubuntu(Focal). vtun_3.0.4-2_amd64.deb: Exact Size 61068 Byte (59.6 kByte) May 20 01:44:05 server vtun [3177]: * Starting virtual tunnel daemon server vtun May 20 01:44:05 server vtun [3186]: VTun see 3.X 11/11/2019 May 20 01:44:05 server vtun [3186]: Usage: May 20 01:44:05 server vtun [3186]: Server: May 20 01:44:05 server vtun [3186]: # 011vtund <-i> [-f file] [-P port] [-L local address] May 20 01:44:05 server vtun [3186]: Client: May 20 01:44:05 server vtun [3186]: # 011vtund [-f file] [-q] [-p] [-m] [-t timeout] <host profile> <server address> May 20 01:44:05 server systemd [1]: vtun.service: Control process exited, code = exited, status = 1 / FAILURE May 20 01:44:05 server systemd [1]: vtun.service: Failed with result 'exit-code'. May 20 01:44:05 server systemd [1]: Failed to start LSB: virtual tunnel over TCP / IP networks. In the version that works the following return: VTun ver 3.X 02/05/2018 Usage:   Server:         vtund <-s> [-f file] [-P port] [-L local address]   Client:         vtund [-f file] [-p] [-m] [-t timeout] <host profile> <server address> Version running of Debian repository: vtun_3.0.4-2_amd64.deb: Exact Size 71124 Byte (69.5 kByte) VTun ver 3.X 11/11/2019 Usage:   Server:         vtund <-s | -i> [-f file] [-P port] [-L local address]   Client:         vtund [-f file] [-q] [-p] [-m] [-t timeout] <host profile> <server address> In the log error, such as option -i in the new version Focal and in the previous versions running, -s for the server environment. #lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 vtun:    Installed: 3.0.4-2    Candidate: 3.0.4-2    Version table:      3.0.4-2 500         500 http://br.archive.ubuntu.com/ubuntu focal/universe amd64 Packages  *** 3.0.4-2 100         100 /var/lib/dpkg/status [ Impact ] vtund can not be run as a server as the <-s> option is not available. The manpage at https://manpages.ubuntu.com/manpages/noble/en/man8/vtund.8.html says about <-s> which can be used to run vtud as a server. But the Ubuntu releases from Focal only have <-i> which allows vtund to run as a inted server. The current package when executed after installing shows: $ vtund vtund[3175]: Can not open /etc/vtund.conf VTun ver 3.X 11/24/2021 Usage: Server: vtund <-i> [-f file] [-P port] [-L local address] Client: vtund [-f file] [-q] [-p] [-m] [-t timeout] <host profile> <server address> The <-s> option is not there in the Server options. [ Test Plan ] 1. First simple test (no need to test the package even) - check the build log to see if it says autoconf has found fork(). With the bug fixed the log will have: checking for fork... yes checking for vfork... yes checking for working fork... yes checking for working vfork... (cached) yes 2. Test the package. - execute the command vtund. With the fixed package it will show: Usage: Server: vtund <-s|-i> [-f file] [-P port] [-L local address] [ Where problems could occur ] Looking at the diff between 3.0.3-4build1 and 3.0.4-2, I can see the code is mostly same for the server and listener. upstream has only added the check for fork() and then moved the server and listerner code in #ifdef. Since the (now) disabled part of the code has been used in pre-Focal, I think there should not be any regression. But again, this part of the code has never been used in Focal onwards, so I can not tell for sure that other parts of the system will not affect the server execution. [ Other Info ] Debian also had the same problem of fork() not getting detected and that was fixed in 3.0.4-2. But for some reason (I will really like to know why) Ubuntu build systems of Focal and Jammy could not detect fork() is present. And since the package was not rebuilt after Jammy, so the problem remained. This is the build log from Debian: https://buildd.debian.org/status/fetch.php?pkg=vtun&arch=amd64&ver=3.0.4-2&stamp=1573583517&raw=0 This is the build log from Ubuntu: https://launchpadlibrarian.net/451222645/buildlog_ubuntu-focal-amd64.vtun_3.0.4-2_BUILDING.txt.gz The Debian build log has: checking for fork... yes checking for vfork... yes checking for working fork... yes checking for working vfork... (cached) yes Whereas the build log from Ubuntu of the same version does not have fork in it. [ Original Bug Description ] When installing a new server with Ubuntu 20.04 LTS with vtun_3.0.4-2_amd64 does not run the service as a server. It has possibly errors in the compilation for Ubuntu Focal. It runs normally on version 3.0.3-4build1 on Ubuntu 18.04 and also on the version of the package available in the Debian repository in the same version at: http://ftp.us.debian.org/debian/pool/main/v/vtun/vtun_3.0.4-2_amd64.deb Error log in the current version Ubuntu(Focal). vtun_3.0.4-2_amd64.deb: Exact Size 61068 Byte (59.6 kByte) May 20 01:44:05 server vtun [3177]: * Starting virtual tunnel daemon server vtun May 20 01:44:05 server vtun [3186]: VTun see 3.X 11/11/2019 May 20 01:44:05 server vtun [3186]: Usage: May 20 01:44:05 server vtun [3186]: Server: May 20 01:44:05 server vtun [3186]: # 011vtund <-i> [-f file] [-P port] [-L local address] May 20 01:44:05 server vtun [3186]: Client: May 20 01:44:05 server vtun [3186]: # 011vtund [-f file] [-q] [-p] [-m] [-t timeout] <host profile> <server address> May 20 01:44:05 server systemd [1]: vtun.service: Control process exited, code = exited, status = 1 / FAILURE May 20 01:44:05 server systemd [1]: vtun.service: Failed with result 'exit-code'. May 20 01:44:05 server systemd [1]: Failed to start LSB: virtual tunnel over TCP / IP networks. In the version that works the following return: VTun ver 3.X 02/05/2018 Usage:   Server:         vtund <-s> [-f file] [-P port] [-L local address]   Client:         vtund [-f file] [-p] [-m] [-t timeout] <host profile> <server address> Version running of Debian repository: vtun_3.0.4-2_amd64.deb: Exact Size 71124 Byte (69.5 kByte) VTun ver 3.X 11/11/2019 Usage:   Server:         vtund <-s | -i> [-f file] [-P port] [-L local address]   Client:         vtund [-f file] [-q] [-p] [-m] [-t timeout] <host profile> <server address> In the log error, such as option -i in the new version Focal and in the previous versions running, -s for the server environment. #lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 vtun:    Installed: 3.0.4-2    Candidate: 3.0.4-2    Version table:      3.0.4-2 500         500 http://br.archive.ubuntu.com/ubuntu focal/universe amd64 Packages  *** 3.0.4-2 100         100 /var/lib/dpkg/status
2024-02-10 10:45:38 Sudip Mukherjee attachment added vtun_noble.debdiff https://bugs.launchpad.net/ubuntu/mantic/+source/vtun/+bug/1881522/+attachment/5745530/+files/vtun_noble.debdiff
2024-02-10 10:47:18 Sudip Mukherjee attachment removed vtun_noble.debdiff https://bugs.launchpad.net/ubuntu/mantic/+source/vtun/+bug/1881522/+attachment/5745530/+files/vtun_noble.debdiff
2024-02-10 10:47:53 Sudip Mukherjee attachment added vtun_noble.debdiff https://bugs.launchpad.net/ubuntu/mantic/+source/vtun/+bug/1881522/+attachment/5745531/+files/vtun_noble.debdiff
2024-02-10 10:48:16 Sudip Mukherjee attachment added vtun_mantic.debdiff https://bugs.launchpad.net/ubuntu/mantic/+source/vtun/+bug/1881522/+attachment/5745532/+files/vtun_mantic.debdiff
2024-02-10 10:48:39 Sudip Mukherjee attachment added vtun_jammy.debdiff https://bugs.launchpad.net/ubuntu/mantic/+source/vtun/+bug/1881522/+attachment/5745533/+files/vtun_jammy.debdiff
2024-02-10 10:48:59 Sudip Mukherjee attachment added vtun_focal.debdiff https://bugs.launchpad.net/ubuntu/mantic/+source/vtun/+bug/1881522/+attachment/5745534/+files/vtun_focal.debdiff
2024-02-10 10:49:13 Sudip Mukherjee vtun (Ubuntu Focal): status In Progress Confirmed
2024-02-10 10:49:15 Sudip Mukherjee vtun (Ubuntu Jammy): status In Progress Confirmed
2024-02-10 10:49:17 Sudip Mukherjee vtun (Ubuntu Mantic): status In Progress Confirmed
2024-02-10 10:49:19 Sudip Mukherjee vtun (Ubuntu Noble): status In Progress Confirmed
2024-02-10 10:49:22 Sudip Mukherjee vtun (Ubuntu Focal): assignee Sudip Mukherjee (sudipmuk)
2024-02-10 10:49:24 Sudip Mukherjee vtun (Ubuntu Jammy): assignee Sudip Mukherjee (sudipmuk)
2024-02-10 10:49:25 Sudip Mukherjee vtun (Ubuntu Mantic): assignee Sudip Mukherjee (sudipmuk)
2024-02-10 10:49:28 Sudip Mukherjee vtun (Ubuntu Noble): assignee Sudip Mukherjee (sudipmuk)
2024-02-10 10:50:01 Sudip Mukherjee bug added subscriber Ubuntu Sponsors
2024-02-15 11:53:45 Julian Andres Klode vtun (Ubuntu Focal): status Confirmed Incomplete
2024-02-15 11:53:47 Julian Andres Klode vtun (Ubuntu Jammy): status Confirmed Incomplete
2024-02-15 11:53:50 Julian Andres Klode vtun (Ubuntu Mantic): status Confirmed Incomplete
2024-02-15 11:53:52 Julian Andres Klode vtun (Ubuntu Noble): status Confirmed Incomplete
2024-02-18 14:39:37 Sudip Mukherjee attachment removed vtun_noble.debdiff https://bugs.launchpad.net/ubuntu/+source/vtun/+bug/1881522/+attachment/5745531/+files/vtun_noble.debdiff
2024-02-18 14:39:44 Sudip Mukherjee attachment removed vtun_mantic.debdiff https://bugs.launchpad.net/ubuntu/+source/vtun/+bug/1881522/+attachment/5745532/+files/vtun_mantic.debdiff
2024-02-18 14:39:50 Sudip Mukherjee attachment removed vtun_jammy.debdiff https://bugs.launchpad.net/ubuntu/+source/vtun/+bug/1881522/+attachment/5745533/+files/vtun_jammy.debdiff
2024-02-18 14:39:57 Sudip Mukherjee attachment removed vtun_focal.debdiff https://bugs.launchpad.net/ubuntu/+source/vtun/+bug/1881522/+attachment/5745534/+files/vtun_focal.debdiff
2024-02-18 14:40:24 Sudip Mukherjee attachment added vtun_noble.debdiff https://bugs.launchpad.net/ubuntu/+source/vtun/+bug/1881522/+attachment/5747060/+files/vtun_noble.debdiff
2024-02-18 14:41:03 Sudip Mukherjee attachment added vtun_mantic.debdiff https://bugs.launchpad.net/ubuntu/+source/vtun/+bug/1881522/+attachment/5747061/+files/vtun_mantic.debdiff
2024-02-18 14:41:15 Sudip Mukherjee attachment added vtun_jammy.debdiff https://bugs.launchpad.net/ubuntu/+source/vtun/+bug/1881522/+attachment/5747062/+files/vtun_jammy.debdiff
2024-02-18 14:41:27 Sudip Mukherjee attachment added vtun_focal.debdiff https://bugs.launchpad.net/ubuntu/+source/vtun/+bug/1881522/+attachment/5747063/+files/vtun_focal.debdiff
2024-02-18 14:41:52 Sudip Mukherjee vtun (Ubuntu Focal): status Incomplete Confirmed
2024-02-18 14:41:54 Sudip Mukherjee vtun (Ubuntu Jammy): status Incomplete Confirmed
2024-02-18 14:41:56 Sudip Mukherjee vtun (Ubuntu Mantic): status Incomplete Confirmed
2024-02-18 14:41:58 Sudip Mukherjee vtun (Ubuntu Noble): status Incomplete Confirmed
2024-02-20 14:43:43 Lukas Märdian vtun (Ubuntu Mantic): status Confirmed In Progress
2024-02-20 14:43:45 Lukas Märdian vtun (Ubuntu Jammy): status Confirmed In Progress
2024-02-20 14:43:47 Lukas Märdian vtun (Ubuntu Focal): status Confirmed In Progress
2024-02-20 14:43:49 Lukas Märdian vtun (Ubuntu Noble): status Confirmed Fix Committed
2024-02-20 14:43:53 Lukas Märdian removed subscriber Ubuntu Sponsors
2024-02-20 15:43:48 Ubuntu Archive Robot bug added subscriber Lukas Märdian
2024-02-20 16:47:03 Launchpad Janitor vtun (Ubuntu Noble): status Fix Committed Fix Released
2024-02-23 13:39:30 Timo Aaltonen vtun (Ubuntu Mantic): status In Progress Fix Committed
2024-02-23 13:39:32 Timo Aaltonen bug added subscriber Ubuntu Stable Release Updates Team
2024-02-23 13:39:36 Timo Aaltonen bug added subscriber SRU Verification
2024-02-23 13:39:40 Timo Aaltonen tags verification-needed verification-needed-mantic
2024-02-23 13:40:16 Timo Aaltonen vtun (Ubuntu Jammy): status In Progress Fix Committed
2024-02-23 13:40:19 Timo Aaltonen tags verification-needed verification-needed-mantic verification-needed verification-needed-jammy verification-needed-mantic
2024-02-23 13:40:57 Timo Aaltonen vtun (Ubuntu Focal): status In Progress Fix Committed
2024-02-23 13:41:03 Timo Aaltonen tags verification-needed verification-needed-jammy verification-needed-mantic verification-needed verification-needed-focal verification-needed-jammy verification-needed-mantic
2024-03-04 20:40:31 Sudip Mukherjee tags verification-needed verification-needed-focal verification-needed-jammy verification-needed-mantic verification-done verification-done-focal verification-done-jammy verification-done-mantic
2024-03-06 04:09:49 Launchpad Janitor vtun (Ubuntu Mantic): status Fix Committed Fix Released
2024-03-06 04:09:52 Chris Halse Rogers removed subscriber Ubuntu Stable Release Updates Team
2024-03-07 20:41:44 Andreas Hasenack bug added subscriber Andreas Hasenack
2024-03-14 13:48:13 Launchpad Janitor vtun (Ubuntu Jammy): status Fix Committed Fix Released
2024-03-14 13:48:26 Launchpad Janitor vtun (Ubuntu Focal): status Fix Committed Fix Released