[Desktop-packages] [Bug 1955325] Re: Firefox cannot open files in /usr/local/doc
** Also affects: chromium (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1955325 Title: Firefox cannot open files in /usr/local/doc Status in chromium package in Ubuntu: New Status in firefox package in Ubuntu: New Bug description: Both Firefox and Chromium in Ubuntu 21.10 cannot open files in /usr/local/doc and show a File-not-found error. IMO this is a bug because this directory often contains HTML files from locally installed software that now cannot be browsed with these HTML browsers anymore. The cause is probably the apparmor configuration in /var/lib/snapd/apparmor/profiles/snap.firefox.firefox, which contains a read permission for /usr/doc, but not for /usr/local/doc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium/+bug/1955325/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%
same bug for me: ubuntu 21.04 nvidia driver 470 blacklisted nouveau fractional scale = 125% desktop is 200% scale, and right and bottom part of desktop is out of monitor. - ubuntu 21.10 have more bug with nvidia driver, so I have to use ubuntu 21.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1870736 Title: [nvidia] Screen scaling 125% gives 200% Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Procedure used: 1. Fully updated system via apt update && apt upgrade 2. Select the screen setup in gnome control center 3. Click the "Fractional scaling" toggle 4. Select 125% and click the green "use" button top right (it says "Anvend" in dansih) 5. Observe that the window has grown a lot, click the "use new settings" button 6. The window tells me, I am at 200% scaling. The "200%" option is now highlighted. 7. Switch back to 100% and file this bug. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.16 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 09:42:34 2020 InstallationDate: Installed on 2018-01-14 (810 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1955733] [NEW] [Inspiron 3501, Cirrus Logic CS8409/CS42L42, Speaker, Internal] Underruns, dropouts or crackling sound
Public bug reported: I have a dell inspiron 15 3000 with audio problems, bluetooth is working fine, hdmi speaker is working fine but internal speaker sounds bad. The sound kind of crackles. Information Description:Ubuntu 20.04.3 LTS Release:20.04 pulseaudio: Installed: 1:13.99.1-1ubuntu3.13 Candidate: 1:13.99.1-1ubuntu3.13 Version table: *** 1:13.99.1-1ubuntu3.13 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:13.99.1-1ubuntu3.8 500 500 http://archive.ubuntu.com/ubuntu focal-security/main amd64 Packages 1:13.99.1-1ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.13 ProcVersionSignature: Ubuntu 5.11.0-43.47~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Dec 25 00:30:18 2021 InstallationDate: Installed on 2021-12-09 (15 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: dic 24 23:12:16 valaro dbus-daemon[909]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.29' (uid=125 pid=2170 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") dic 24 23:13:22 valaro pulseaudio[2170]: After module unload, module 'module-null-sink' was still loaded! dic 24 23:13:22 valaro systemd[2152]: pulseaudio.service: Succeeded. dic 24 23:13:32 valaro systemd[2152]: pulseaudio.socket: Succeeded. Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [Inspiron 3501, Cirrus Logic CS8409/CS42L42, Speaker, Internal] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/05/2021 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 03TNDR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd07/05/2021:br1.7:svnDellInc.:pnInspiron3501:pvr:sku0A25:rvnDellInc.:rn03TNDR:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3501 dmi.product.sku: 0A25 dmi.sys.vendor: Dell Inc. modified.conffile..etc.pulse.daemon.conf: [modified] modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.daemon.conf: 2021-12-24T21:32:37.421378 mtime.conffile..etc.pulse.default.pa: 2021-12-24T22:17:32.506068 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1955733 Title: [Inspiron 3501, Cirrus Logic CS8409/CS42L42, Speaker, Internal] Underruns, dropouts or crackling sound Status in pulseaudio package in Ubuntu: New Bug description: I have a dell inspiron 15 3000 with audio problems, bluetooth is working fine, hdmi speaker is working fine but internal speaker sounds bad. The sound kind of crackles. Information Description: Ubuntu 20.04.3 LTS Release: 20.04 pulseaudio: Installed: 1:13.99.1-1ubuntu3.13 Candidate: 1:13.99.1-1ubuntu3.13 Version table: *** 1:13.99.1-1ubuntu3.13 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:13.99.1-1ubuntu3.8 500 500 http://archive.ubuntu.com/ubuntu focal-security/main amd64 Packages 1:13.99.1-1ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.13 ProcVersionSignature: Ubuntu 5.11.0-43.47~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Dec 25 00:30:18 2021 InstallationDate: Installed on 2021-12-09 (15 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: dic 24 23:12:16 valaro dbus-daemon[909]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.29'
[Desktop-packages] [Bug 1945203] Re: Wayland: Useage of touchscreen on dock freezes the dock
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1945203 Title: Wayland: Useage of touchscreen on dock freezes the dock Status in gnome-shell package in Ubuntu: Expired Bug description: General information: Ubuntu 21.04 Device: Dell XPS13 2-in-1 When using the touchscreen to start or switch between apps in the dock, the dock freezes after 1-5 events. A tooltip is shown permanently and the dock is no longer responsive and can't be used for app switching anymore. The top menu bar with wifi and bt settings etc. is also frozen. This problem only occurs with Wayland, not with classic X. And only touch events trigger the freeze. Other input devices such as the touchpad, the digitizer or an external mouse do not trigger this problem. Workaround: Alt+Tab is not affected and can still be used for app switching, but it sucks if the device is in tablet mode. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xwayland 2:21.1.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-36.40-generic 5.11.22 Uname: Linux 5.11.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Sep 27 15:05:59 2021 EcryptfsUse: Yes InstallationDate: Installed on 2021-09-15 (12 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: xwayland UpgradeStatus: Upgraded to hirsute on 2021-09-25 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1945203/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1853977] Re: nvidia-340 dpkg: error: version '-' has bad syntax: revision number is empty
Addition to the above comment by sarnold, I tried with the 5.4 kernel, and that seemed to compile ok. But it still fails for 5.11 installed on the same system, regardless of changing $KERNELS to $CURRENT_KERNEL. Here is some relevant output: sudo apt install nvidia-340 # after installing and booting linux 5.4 https://paste.ubuntu.com/p/HqJjsQk7hN/ contents of /var/lib/dkms/nvidia-340/340.108/build/make.log https://paste.ubuntu.com/p/nGtrn67VBJ/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1853977 Title: nvidia-340 dpkg: error: version '-' has bad syntax: revision number is empty Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: Hello, When installing `nvidia-340` there is an error is the postinst script: philippe@pv-desktop:~$ sudo apt install --reinstall nvidia-340 Reading package lists... Done Building dependency tree Reading state information... Done 0 to upgrade, 0 to newly install, 1 reinstalled, 0 to remove and 7 not to upgrade. Need to get 0 B/51.9 MB of archives. After this operation, 0 B of additional disk space will be used. (Reading database ... 309892 files and directories currently installed.) Preparing to unpack .../nvidia-340_340.107-0ubuntu0.18.04.4_amd64.deb ... Stopping nvidia-persistenced nvidia-persistenced: no process found Done. (snip) Setting up nvidia-340 (340.107-0ubuntu0.18.04.4) ... dpkg: error: version '-' has bad syntax: revision number is empty dpkg: error: version '-' has bad syntax: revision number is empty update-initramfs: deferring update (trigger activated) INFO:Enable nvidia-340 DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude Loading new nvidia-340-340.107 DKMS files... Building for 4.15.0-70-generic Building for architecture x86_64 Building initial module for 4.15.0-70-generic Done. The comment at https://askubuntu.com/questions/969352/uninstalling- and-then-reinstalling-nvidia-384-kills-colord tells us that /var/lib/dpkg/info/nvidia-340.postinst has a typo: replace $KERNELS with $CURRENT_KERNEL then `dpkg-reconfigure nvidia-340` works as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853977/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1853977] Re: nvidia-340 dpkg: error: version '-' has bad syntax: revision number is empty
Hello Alberto, any chance for a fix for this issue? Users are still finding this issue. In #ubuntu, 25 December 2021: Sat 25 00:12:58 < sem> if you're curious this is the dryrun: https://pastebin.ubuntu.com/p/N7kP5Z4mRj/ Sat 25 00:15:32 < Bashing-om> sem: I do want to know - looking ^ , Sat 25 00:17:13 < sem> do you think this message is relevant? "dpkg: error: version '-' has bad syntax: revision number is empty" https://pastebin.ubuntu.com/p/PGj9rjzKXF/ Thanks -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1853977 Title: nvidia-340 dpkg: error: version '-' has bad syntax: revision number is empty Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: Hello, When installing `nvidia-340` there is an error is the postinst script: philippe@pv-desktop:~$ sudo apt install --reinstall nvidia-340 Reading package lists... Done Building dependency tree Reading state information... Done 0 to upgrade, 0 to newly install, 1 reinstalled, 0 to remove and 7 not to upgrade. Need to get 0 B/51.9 MB of archives. After this operation, 0 B of additional disk space will be used. (Reading database ... 309892 files and directories currently installed.) Preparing to unpack .../nvidia-340_340.107-0ubuntu0.18.04.4_amd64.deb ... Stopping nvidia-persistenced nvidia-persistenced: no process found Done. (snip) Setting up nvidia-340 (340.107-0ubuntu0.18.04.4) ... dpkg: error: version '-' has bad syntax: revision number is empty dpkg: error: version '-' has bad syntax: revision number is empty update-initramfs: deferring update (trigger activated) INFO:Enable nvidia-340 DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude Loading new nvidia-340-340.107 DKMS files... Building for 4.15.0-70-generic Building for architecture x86_64 Building initial module for 4.15.0-70-generic Done. The comment at https://askubuntu.com/questions/969352/uninstalling- and-then-reinstalling-nvidia-384-kills-colord tells us that /var/lib/dpkg/info/nvidia-340.postinst has a typo: replace $KERNELS with $CURRENT_KERNEL then `dpkg-reconfigure nvidia-340` works as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853977/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1853977] Re: nvidia-340 dpkg: error: version '-' has bad syntax: revision number is empty
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1853977 Title: nvidia-340 dpkg: error: version '-' has bad syntax: revision number is empty Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: Hello, When installing `nvidia-340` there is an error is the postinst script: philippe@pv-desktop:~$ sudo apt install --reinstall nvidia-340 Reading package lists... Done Building dependency tree Reading state information... Done 0 to upgrade, 0 to newly install, 1 reinstalled, 0 to remove and 7 not to upgrade. Need to get 0 B/51.9 MB of archives. After this operation, 0 B of additional disk space will be used. (Reading database ... 309892 files and directories currently installed.) Preparing to unpack .../nvidia-340_340.107-0ubuntu0.18.04.4_amd64.deb ... Stopping nvidia-persistenced nvidia-persistenced: no process found Done. (snip) Setting up nvidia-340 (340.107-0ubuntu0.18.04.4) ... dpkg: error: version '-' has bad syntax: revision number is empty dpkg: error: version '-' has bad syntax: revision number is empty update-initramfs: deferring update (trigger activated) INFO:Enable nvidia-340 DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude Loading new nvidia-340-340.107 DKMS files... Building for 4.15.0-70-generic Building for architecture x86_64 Building initial module for 4.15.0-70-generic Done. The comment at https://askubuntu.com/questions/969352/uninstalling- and-then-reinstalling-nvidia-384-kills-colord tells us that /var/lib/dpkg/info/nvidia-340.postinst has a typo: replace $KERNELS with $CURRENT_KERNEL then `dpkg-reconfigure nvidia-340` works as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853977/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1948339] Re: Logon screen can be bypassed using various shortcuts
Hi all, narrowed it down and found out that arctica-greeter is invoking "marco" to make handling of windows opened by some of the indicators easier. However marco listens for any keybindings and that's the reason why keybindings are working on the logon screen. The affected code path was introduced with arctica-greeter 0.99.1.1 (Feb 6, 2019) and is located in https://github.com/ArcticaProject/arctica- greeter/blob/master/src/arctica-greeter.vala. I've also added a comment to the issue within the arctica-greeter repo. Should be a straight forward fix. Cheers, Basti -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1948339 Title: Logon screen can be bypassed using various shortcuts Status in Ubuntu MATE: New Status in arctica-greeter package in Ubuntu: New Status in lightdm package in Ubuntu: New Status in mate-settings-daemon package in Ubuntu: New Bug description: Hi, my little daughter discovered a logon screen bypass in Ubuntu Mate 21.10 after hitting the keyboard for a while. It turns out that several keyboard shortcuts are allowed while Ubuntu Mate is locked (arctica-greeter): - Mod4 + S (mate-search-tool) - Mod4 + E (Open Caja / File Explorer) - CTRL + Shift + Esc (mate-system-monitor) - PRNT (Screenshot) All of the mentioned shortcuts could be used to spawn a file explorer (Caja) or various other binaries as user "lightdm", who owns the logon screen. Although an interactive terminal like mate-terminal, xterm, lxterm etc. could not be opened directly, there are various options to run commands as the lightdm user, for example by creating a shell script using "caja", and execute it directly using the GUI. I've attached Proof-of-Concept GIFs for all shortcuts mentioned above. There might be additional shortcuts that could be used to achieve the same, however I'm not aware about every shortcut that is configured, but I suppose that the root cause is located somewhere in arctica- greeter, rather than within every single binary launched by shortcuts. The bug was reproduced on a fresh installation of Ubuntu Mate 21.10. I haven't tested other versions of Ubuntu Mate yet. Please find additional version details below: $ apt-cache policy lightdm lightdm: Installed: 1.30.0-0ubuntu4 Candidate: 1.30.0-0ubuntu4 Version table: *** 1.30.0-0ubuntu4 500 500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy arctica-greeter arctica-greeter: Installed: 0.99.1.5-2nmu1 Candidate: 0.99.1.5-2nmu1 Version table: *** 0.99.1.5-2nmu1 500 500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status Thanks, Basti To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1948339/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1608646] Re: ip4 static routes added in NetworkManager UI fail and prevent connection
I would like to revive this bug report. I will describe the problem in detail. I run an ovpn script from the command line and everything goes well. The ovpn file: client dev tun remote nl.vpn.**.org 443 resolv-retry infinite nobind persist-key persist-tun auth-nocache mute-replay-warnings route 10.0.1.0 255.255.255.0 10.0.2.136 route 10.0.0.0 255.255.255.0 10.0.2.136 route-delay 5 verb 3 explicit-exit-notify 5 remote-cert-tls server cipher AES-256-CBC comp-lzo no proto udp key-direction 1 I left out certivicates because they are here irrelevant. The route table before the execution of openvpn is: Destination Gateway Genmask Flags Metric RefUse Iface 0.0.0.0 10.0.2.136 0.0.0.0 UG10000 enp3s0 10.0.2.00.0.0.0 255.255.255.0 U 10000 enp3s0 10.0.2.136 is my home router. After the execution of sudo openvpn the route table is: Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 10.17.76.1 128.0.0.0UG0 0 0 tun0 0.0.0.0 10.0.2.136 0.0.0.0 UG1000 0 enp3s0 10.0.0.0 10.0.2.136 255.255.255.0UG0 0 0 enp3s0 10.0.1.0 10.0.2.136 255.255.255.0UG0 0 0 enp3s0 10.0.2.00.0.0.0 255.255.255.0U 1000 0 enp3s0 10.17.76.0 0.0.0.0 255.255.255.0U 0 0 0 tun0 128.0.0.0 10.17.76.1128.0.0.0UG0 0 0 tun0 213.152.162.73 10.0.2.136255.255.255.255 UGH 0 0 0 enp3s0 This looks a bit complicated to me but it is working. Note the two lines for the networks 10.0.1.0/24 and 10.0.0.0/24. They are needed to divert traffic for those networks to my home router 10.0.2.136. Traffic for my home network 10.0.2.0/24 stays in the home network. All other traffic goes to the tun0 device (the vpn provider). In the Network Manager I imported the ovpn file and the resulting network manager file /etc/NetworkManager/system-connections/vpnnl file is: id=provider_UDP-443 uuid=88baf716 type=vpn autoconnect=false permissions= [vpn] cert-pass-flags=0 cipher=AES-256-CBC comp-lzo=no-by-default connection-type=tls dev=tun key=***.pem remote=nl.vpn.provider.org:443 remote-cert-tls=server ta-dir=1 service-type=org.freedesktop.NetworkManager.openvpn [ipv4] dns-search= method=auto route1=10.0.1.0/24,10.0.2.136 route2=10.0.0.0/24,10.0.2.136 [ipv6] addr-gen-mode=stable-privacy dns-search= ip6-privacy=0 method=auto I left out some statements concerning security and privacy. Note the two route statements. When I make the vpn connection with this connections file I get the error message: connection failed because VPN service returned invalid configuration. When I remove the two route statements in the network-manager/ edit connections section the connection is properly made but ofcourse without the two route statements in the route table: Destination Gateway Genmask Flags Metric RefUse Iface 0.0.0.0 10.0.2.136 0.0.0.0 UG 100 00 enp3s0 10.0.2.00.0.0.0 255.255.255.0 U 100 00 enp3s0 10.0.2.136 0.0.0.0 255.255.255.255 UH 100 00 enp3s0 10.27.44.0 0.0.0.0 255.255.255.0 U 50 00 tun0 213.152.162.148 10.0.2.136 255.255.255.255 UGH 100 00 enp3s0 there are more differences that I don't fully understand. I can, ofcourse, add these route statements by hand but that is not the point. (I can also live for a short moment with an unreachable network). When I change the 2 extra route statement (10.0.2.136 changed in 0.0.0.0) (in the vpnnl file) the error message disappears but the two route statements (in the route table) divert the traffic then to tun0 (should be enp3s0). If you want to know more please ask. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1608646 Title: ip4 static routes added in NetworkManager UI fail and prevent connection Status in network-manager package in Ubuntu: Expired Bug description: lsb_release -rd: Description: Ubuntu 16.04.1 LTS Release: 16.04 Network Settings package version in Software Center: 15.04.0+16.04.20160705-0ubuntu1 Prior to upgrading to 16.04 LTS I was running 14.04 LTS. Using the "Edit Connections..." menu option I had created a custom Ethernet connection that had some custom routes added. These routes are required for me to connect to certain resources on
[Desktop-packages] [Bug 1955702] [NEW] Grafikkarte Treiber
Public bug reported: Grafikkarte Probleme ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 Uname: Linux 5.4.0-91-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Dec 24 10:52:06 2021 DistUpgraded: 2021-12-23 00:23:01,754 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7640G] [1002:9903] (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Trinity [Radeon HD 7640G] [144d:c0da] Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] [1002:6840] (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Radeon HD 7670M [144d:c0da] InstallationDate: Installed on 2021-12-22 (1 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: SAMSUNG ELECTRONICS CO., LTD. 355V4C/356V4C/3445VC/3545VC ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-91-generic root=UUID=fc93f578-a24f-400f-95c2-03eaf71b373f ro quiet splash Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2021-12-22 (1 days ago) dmi.bios.date: 07/04/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P07ABF dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NP355E7C-S09DE dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: BOARD REVISION 00 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP07ABF:bd07/04/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn355V4C/356V4C/3445VC/3545VC:pvrP07ABF.010.CP:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP355E7C-S09DE:rvrBOARDREVISION00:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.family: Eureka dmi.product.name: 355V4C/356V4C/3445VC/3545VC dmi.product.sku: P07ABF.010.CP dmi.product.version: P07ABF.010.CP dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.5 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.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-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1955702 Title: Grafikkarte Treiber Status in xorg package in Ubuntu: New Bug description: Grafikkarte Probleme ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 Uname: Linux 5.4.0-91-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Dec 24 10:52:06 2021 DistUpgraded: 2021-12-23 00:23:01,754 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7640G] [1002:9903] (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Trinity [Radeon HD 7640G] [144d:c0da] Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] [1002:6840] (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Radeon HD 7670M [144d:c0da] InstallationDate: Installed on 2021-12-22 (1 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: SAMSUNG ELECTRONICS CO., LTD. 355V4C/356V4C/3445VC/3545VC ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-91-generic root=UUID=fc93f578-a24f-400f-95c2-03eaf71b373f ro quiet splash Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2021-12-22 (1 days ago) dmi.bios.date: 07/04/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bi
[Desktop-packages] [Bug 1913775] Re: Copy from Firefox Wayland fails to be pasted anywhere else
Will there be a port of this fix to impish? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1913775 Title: Copy from Firefox Wayland fails to be pasted anywhere else Status in GTK+: Unknown Status in firefox package in Ubuntu: Invalid Status in gtk+3.0 package in Ubuntu: Fix Released Bug description: Running Firefox 84.0.2 for Ubuntu Canonical-1.0 on Ubuntu 20.04.1 LTS, on Wayland native Version 84.0.2 Build ID 20210105180113 Window Protocol wayland Desktop Environment gnome DESCRIPTION OF THE PROBLEM: If I copy text from a web page and try to paste it into another Firefox page, the text is pasted correctly. If I copy text from a web page and try to paste it in [gedit, libreoffice, thunderbird, terminal, slack (electron)] nothing happens. The Gnome Clipboard extension stays empty when content is copied from Firefox Wayland. Pasting *from* another app *to* Firefox works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1913775/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
