[Touch-packages] [Bug 2056627] Re: PHPStorm crashes when opening a project
Also occurs with https://lmstudio.ai/ which is also AppImage based. I think the feature is broken in general ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2056627 Title: PHPStorm crashes when opening a project Status in apparmor package in Ubuntu: Confirmed Bug description: Filing mostly in case anyone else hits this and is looking for workarounds: Since the Update to 24.04 PHPStorm crashes on open for me. I think when it tries to preview a markdown file, like a README.md which is shown when opening a project. ``` [0309/094602.913394:FATAL:setuid_sandbox_host.cc(158)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /home/user/bin/phpstorm/jbr/lib/chrome-sandbox is owned by root and has mode 4755. ``` Workaround 1 (wont persist reboots, needs root): sudo sysctl -w kernel.apparmor_restrict_unprivileged_unconfined=0 sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0 Workaround 2 (persists and doesn't need root): thanks to https://youtrack.jetbrains.com/issue/IDEA-313202/IDE- crashes-due-to-chrome-sandbox-is-owned-by-root-and-has-mode-error- when-IDE-is-launching-the-JCEF-in-a- sandbox#focus=Comments-27-7059083.0-0 * Run `/bin/phpstorm.sh dontReopenProjects` (to avoid it crashing on start) * ctrl+shift+a * type "Registry..." and select it * disable the "ide.browser.jcef.sandbox.enable" option * Restart phpstorm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2056627/+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 1874393] [NEW] openswan VPN no longer works after upgrade to 20.04
Public bug reported: #nmcli con up 6cff80a9-24e9-4b19-89f1-1324ef966ceb Error: Connection activation failed: The VPN service 'org.freedesktop.NetworkManager.openswan' was not installed. #dpkg -l|grep -i swan ii libcharon-extauth-plugins 5.8.2-1ubuntu3 amd64strongSwan charon library (extended authentication plugins) ii libstrongswan 5.8.2-1ubuntu3 amd64strongSwan utility and crypto library ii libstrongswan-standard-plugins5.8.2-1ubuntu3 amd64strongSwan utility and crypto library (standard plugins) ii network-manager-strongswan1.4.5-2.1 amd64network management framework (strongSwan plugin) ii strongswan-libcharon 5.8.2-1ubuntu3 amd64strongSwan charon library ii strongswan-nm 5.8.2-1ubuntu3 amd64strongSwan plugin to interact with NetworkManager Where has the openswan plugin gone ? It's still an option in nm-applet ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu Apr 23 08:39:32 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.11.1 dev wlan0 proto dhcp metric 600 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.11.0/24 dev wlan0 proto kernel scope link src 192.168.11.50 metric 600 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: [connection] wifi.powersave = 2 mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 2017-10-16T20:52:50.502869 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1874393 Title: openswan VPN no longer works after upgrade to 20.04 Status in network-manager package in Ubuntu: New Bug description: #nmcli con up 6cff80a9-24e9-4b19-89f1-1324ef966ceb Error: Connection activation failed: The VPN service 'org.freedesktop.NetworkManager.openswan' was not installed. #dpkg -l|grep -i swan ii libcharon-extauth-plugins 5.8.2-1ubuntu3 amd64strongSwan charon library (extended authentication plugins) ii libstrongswan 5.8.2-1ubuntu3 amd64strongSwan utility and crypto library ii libstrongswan-standard-plugins5.8.2-1ubuntu3 amd64strongSwan utility and crypto library (standard plugins) ii network-manager-strongswan1.4.5-2.1 amd64network management framework (strongSwan plugin) ii strongswan-libcharon 5.8.2-1ubuntu3 amd64strongSwan charon library ii strongswan-nm 5.8.2-1ubuntu3 amd64strongSwan plugin to interact with NetworkManager Where has the openswan plugin gone ? It's still an option in nm-applet ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu Apr 23 08:39:32 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.11.1 dev wlan0 proto dhcp metric 600 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.11.0/24 dev wlan0 proto kernel scope link src 192.168.11.50 metric 600 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: [connection] wifi.powersave = 2 mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 2017-10-16T20:52:50.502869 nmcli-nm: RUNNING VERSION
[Touch-packages] [Bug 1764312] Re: fails to start in Bionic
sudo: apparmor_parser: command not found -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1764312 Title: fails to start in Bionic Status in apparmor package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: $ systemctl status apparmor ● apparmor.service - AppArmor initialization Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2018-04-16 07:46:13 BST; 1h 10min ago Docs: man:apparmor(7) http://wiki.apparmor.net/ Process: 635 ExecStart=/etc/init.d/apparmor start (code=exited, status=123) Main PID: 635 (code=exited, status=123) Apr 16 07:46:12 ev34 apparmor[635]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Apr 16 07:46:12 ev34 apparmor[635]: AppArmor parser error for /etc/apparmor.d/usr.lib.snapd.snap-confine.real in /etc/ap Apr 16 07:46:13 ev34 apparmor[635]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Apr 16 07:46:13 ev34 apparmor[635]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Apr 16 07:46:13 ev34 apparmor[635]: AppArmor parser error for /etc/apparmor.d/usr.lib.snapd.snap-confine.real in /etc/ap Apr 16 07:46:13 ev34 apparmor[635]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Apr 16 07:46:13 ev34 apparmor[635]:...fail! Apr 16 07:46:13 ev34 systemd[1]: apparmor.service: Main process exited, code=exited, status=123/n/a Apr 16 07:46:13 ev34 systemd[1]: apparmor.service: Failed with result 'exit-code'. Apr 16 07:46:13 ev34 systemd[1]: Failed to start AppArmor initialization. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1764312/+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 1764312] Re: fails to start in Bionic
installed it, and it says $ sudo apparmor_parser --replace /etc/apparmor.d/usr.lib.snapd.snap-confine.real File /etc/apparmor.d/usr.lib.snapd.snap-confine.real not found, skipping... $ sudo systemctl start apparmor $ sudo systemctl status apparmor ● apparmor.service - AppArmor initialization Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; vendor preset: enabled) Active: active (exited) since Tue 2018-04-17 20:06:52 BST; 4s ago Docs: man:apparmor(7) http://wiki.apparmor.net/ Process: 3101 ExecStart=/etc/init.d/apparmor start (code=exited, status=0/SUCCESS) Main PID: 3101 (code=exited, status=0/SUCCESS) Apr 17 20:06:51 wopr.house systemd[1]: Starting AppArmor initialization... Apr 17 20:06:51 wopr.house apparmor[3101]: * Starting AppArmor profiles Apr 17 20:06:51 wopr.house apparmor[3101]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Apr 17 20:06:51 wopr.house apparmor[3101]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox-esr Apr 17 20:06:52 wopr.house apparmor[3101]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Apr 17 20:06:52 wopr.house apparmor[3101]:...done. Apr 17 20:06:52 wopr.house systemd[1]: Started AppArmor initialization. so somehow it was part installed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1764312 Title: fails to start in Bionic Status in apparmor package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: $ systemctl status apparmor ● apparmor.service - AppArmor initialization Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2018-04-16 07:46:13 BST; 1h 10min ago Docs: man:apparmor(7) http://wiki.apparmor.net/ Process: 635 ExecStart=/etc/init.d/apparmor start (code=exited, status=123) Main PID: 635 (code=exited, status=123) Apr 16 07:46:12 ev34 apparmor[635]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Apr 16 07:46:12 ev34 apparmor[635]: AppArmor parser error for /etc/apparmor.d/usr.lib.snapd.snap-confine.real in /etc/ap Apr 16 07:46:13 ev34 apparmor[635]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Apr 16 07:46:13 ev34 apparmor[635]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Apr 16 07:46:13 ev34 apparmor[635]: AppArmor parser error for /etc/apparmor.d/usr.lib.snapd.snap-confine.real in /etc/ap Apr 16 07:46:13 ev34 apparmor[635]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Apr 16 07:46:13 ev34 apparmor[635]:...fail! Apr 16 07:46:13 ev34 systemd[1]: apparmor.service: Main process exited, code=exited, status=123/n/a Apr 16 07:46:13 ev34 systemd[1]: apparmor.service: Failed with result 'exit-code'. Apr 16 07:46:13 ev34 systemd[1]: Failed to start AppArmor initialization. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1764312/+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 1764312] Re: fails to start in Bionic
$ dpkg -l|grep appar rc apparmor2.12-4ubuntu4 amd64user-space parser utility for AppArmor ii libapparmor1:amd64 2.12-4ubuntu4 amd64changehat AppArmor library -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1764312 Title: fails to start in Bionic Status in apparmor package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: $ systemctl status apparmor ● apparmor.service - AppArmor initialization Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2018-04-16 07:46:13 BST; 1h 10min ago Docs: man:apparmor(7) http://wiki.apparmor.net/ Process: 635 ExecStart=/etc/init.d/apparmor start (code=exited, status=123) Main PID: 635 (code=exited, status=123) Apr 16 07:46:12 ev34 apparmor[635]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Apr 16 07:46:12 ev34 apparmor[635]: AppArmor parser error for /etc/apparmor.d/usr.lib.snapd.snap-confine.real in /etc/ap Apr 16 07:46:13 ev34 apparmor[635]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Apr 16 07:46:13 ev34 apparmor[635]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Apr 16 07:46:13 ev34 apparmor[635]: AppArmor parser error for /etc/apparmor.d/usr.lib.snapd.snap-confine.real in /etc/ap Apr 16 07:46:13 ev34 apparmor[635]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Apr 16 07:46:13 ev34 apparmor[635]:...fail! Apr 16 07:46:13 ev34 systemd[1]: apparmor.service: Main process exited, code=exited, status=123/n/a Apr 16 07:46:13 ev34 systemd[1]: apparmor.service: Failed with result 'exit-code'. Apr 16 07:46:13 ev34 systemd[1]: Failed to start AppArmor initialization. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1764312/+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 1764312] Re: fails to start in Bionic
** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1764312 Title: fails to start in Bionic Status in apparmor package in Ubuntu: New Bug description: $ systemctl status apparmor ● apparmor.service - AppArmor initialization Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2018-04-16 07:46:13 BST; 1h 10min ago Docs: man:apparmor(7) http://wiki.apparmor.net/ Process: 635 ExecStart=/etc/init.d/apparmor start (code=exited, status=123) Main PID: 635 (code=exited, status=123) Apr 16 07:46:12 ev34 apparmor[635]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Apr 16 07:46:12 ev34 apparmor[635]: AppArmor parser error for /etc/apparmor.d/usr.lib.snapd.snap-confine.real in /etc/ap Apr 16 07:46:13 ev34 apparmor[635]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Apr 16 07:46:13 ev34 apparmor[635]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Apr 16 07:46:13 ev34 apparmor[635]: AppArmor parser error for /etc/apparmor.d/usr.lib.snapd.snap-confine.real in /etc/ap Apr 16 07:46:13 ev34 apparmor[635]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Apr 16 07:46:13 ev34 apparmor[635]:...fail! Apr 16 07:46:13 ev34 systemd[1]: apparmor.service: Main process exited, code=exited, status=123/n/a Apr 16 07:46:13 ev34 systemd[1]: apparmor.service: Failed with result 'exit-code'. Apr 16 07:46:13 ev34 systemd[1]: Failed to start AppArmor initialization. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1764312/+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 1764312] [NEW] fails to start in Bionic
Public bug reported: $ systemctl status apparmor ● apparmor.service - AppArmor initialization Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2018-04-16 07:46:13 BST; 1h 10min ago Docs: man:apparmor(7) http://wiki.apparmor.net/ Process: 635 ExecStart=/etc/init.d/apparmor start (code=exited, status=123) Main PID: 635 (code=exited, status=123) Apr 16 07:46:12 ev34 apparmor[635]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Apr 16 07:46:12 ev34 apparmor[635]: AppArmor parser error for /etc/apparmor.d/usr.lib.snapd.snap-confine.real in /etc/ap Apr 16 07:46:13 ev34 apparmor[635]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Apr 16 07:46:13 ev34 apparmor[635]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Apr 16 07:46:13 ev34 apparmor[635]: AppArmor parser error for /etc/apparmor.d/usr.lib.snapd.snap-confine.real in /etc/ap Apr 16 07:46:13 ev34 apparmor[635]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Apr 16 07:46:13 ev34 apparmor[635]:...fail! Apr 16 07:46:13 ev34 systemd[1]: apparmor.service: Main process exited, code=exited, status=123/n/a Apr 16 07:46:13 ev34 systemd[1]: apparmor.service: Failed with result 'exit-code'. Apr 16 07:46:13 ev34 systemd[1]: Failed to start AppArmor initialization. ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1764312 Title: fails to start in Bionic Status in apparmor package in Ubuntu: New Bug description: $ systemctl status apparmor ● apparmor.service - AppArmor initialization Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2018-04-16 07:46:13 BST; 1h 10min ago Docs: man:apparmor(7) http://wiki.apparmor.net/ Process: 635 ExecStart=/etc/init.d/apparmor start (code=exited, status=123) Main PID: 635 (code=exited, status=123) Apr 16 07:46:12 ev34 apparmor[635]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Apr 16 07:46:12 ev34 apparmor[635]: AppArmor parser error for /etc/apparmor.d/usr.lib.snapd.snap-confine.real in /etc/ap Apr 16 07:46:13 ev34 apparmor[635]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Apr 16 07:46:13 ev34 apparmor[635]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Apr 16 07:46:13 ev34 apparmor[635]: AppArmor parser error for /etc/apparmor.d/usr.lib.snapd.snap-confine.real in /etc/ap Apr 16 07:46:13 ev34 apparmor[635]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Apr 16 07:46:13 ev34 apparmor[635]:...fail! Apr 16 07:46:13 ev34 systemd[1]: apparmor.service: Main process exited, code=exited, status=123/n/a Apr 16 07:46:13 ev34 systemd[1]: apparmor.service: Failed with result 'exit-code'. Apr 16 07:46:13 ev34 systemd[1]: Failed to start AppArmor initialization. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1764312/+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 1764106] [NEW] ca-certificates fails on update in Bionic
Public bug reported: Processing triggers for ca-certificates (20180409) ... Updating certificates in /etc/ssl/certs... 0 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d... done. Updating Mono key store /etc/ca-certificates/update.d/mono-keystore: 10: /etc/ca-certificates/update.d/mono-keystore: /usr/bin/cert-sync: not found ** Affects: ca-certificates (Ubuntu) Importance: Undecided Status: New ** Package changed: sddm (Ubuntu) => ca-certificates (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1764106 Title: ca-certificates fails on update in Bionic Status in ca-certificates package in Ubuntu: New Bug description: Processing triggers for ca-certificates (20180409) ... Updating certificates in /etc/ssl/certs... 0 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d... done. Updating Mono key store /etc/ca-certificates/update.d/mono-keystore: 10: /etc/ca-certificates/update.d/mono-keystore: /usr/bin/cert-sync: not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1764106/+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
