[Bug 296646] Re: fire fox title bar goes off the screen and is not accesible
Same problem here, I noticed that if I switch to fullscreen and back again (using the F11 key) the titlebar and panels reappear, but only for a minute or so, then they dissapear again. -- fire fox title bar goes off the screen and is not accesible https://bugs.launchpad.net/bugs/296646 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 293086] Re: firefox starts in fulscreen by default
*** This bug is a duplicate of bug 296646 *** https://bugs.launchpad.net/bugs/296646 ** This bug has been marked a duplicate of bug 296646 fire fox title bar goes off the screen and is not accesible -- firefox starts in fulscreen by default https://bugs.launchpad.net/bugs/293086 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901724] [NEW] Systemd user environment generator is not executable.
Public bug reported: On Ubuntu 20.04.1, with gnupg-agent 2.2.19-3ubuntu2 Using the GnuPG SSH agent with interactive terminal sessions works as expected, after manually setting up the usual environment variables in ~/.profile and .bashrc. But Nautilus is failing to open remote SFTP directories, it ask for username and password, where it just should use keys from the GnuPG SSH agent. Only if I manually restart the gvfs-daemon.service Nautilus starts to work as expected. After a fresh system startup and login the main pid of the gvfs-daemon service will not have SSH_AUTH_SOCK variable set. After a manual service restart they are correctly set. I noticed that the file /lib/systemd/user-environment-generators/90gpg- agent has no execution bit set. After changing the user environment script as executable everything works as expected. Steps to reproduce: 1. Reboot system and login. 3. Get the PID of your gvfs-daemon.service: $ systemctl --user status gvfs-daemon.service | grep "Main PID:" 4. Check the environment of that process: $ tr "\0" "\n" < /proc/$(pidof -s gvfsd)/environ Workaround: 1. Make the systemd user environment generator for gpg-agent executable: $ sudo chmod +x /lib/systemd/user-environment-generators/90gpg-agent 2. Reboot system and login. I also noticed while trying to find a workaround, that after simple logout and re-login of my Gnome session, it sometimes appeared to be working as expected. But then failed again after full system restart. ** Affects: gnupg2 (Ubuntu) Importance: Undecided Status: New ** Tags: gpg-agent systemd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901724 Title: Systemd user environment generator is not executable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnupg2/+bug/1901724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901724] Re: Systemd user environment generator is not executable.
> I thought gnome-shell started its own agent for ssh on startup? My keys are on hardware security devices and I also use gpg-agent-forwarding, so afaik gnome-keyring-ssh will not do in this setup. > Or did you configure your system to run the gnupg agent before starting gnome? The way I understand it, that is exactly what user-environment-generators/90gpg-agent does. ** Description changed: - On Ubuntu 20.04.1, with gnupg-agent 2.2.19-3ubuntu2 + Ubuntu 20.04.1 + gnupg-agent 2.2.19-3ubuntu2 + gnome-shell 3.36.4-1ubuntu1~20.04.2 + systemd 245.4-4ubuntu3.2 - Using the GnuPG SSH agent with interactive terminal sessions works as - expected, after manually setting up the usual environment variables in - ~/.profile and .bashrc. + + Using the GnuPG SSH agent with interactive terminal sessions works as expected, after manually setting up the usual environment variables in ~/.profile and .bashrc. But Nautilus is failing to open remote SFTP directories, it ask for username and password, where it just should use keys from the GnuPG SSH agent. Only if I manually restart the gvfs-daemon.service Nautilus starts to work as expected. After a fresh system startup and login the main pid of the gvfs-daemon service will not have SSH_AUTH_SOCK variable set. After a manual service restart they are correctly set. I noticed that the file /lib/systemd/user-environment-generators/90gpg- agent has no execution bit set. After changing the user environment script as executable everything works as expected. Steps to reproduce: 1. Reboot system and login. 3. Get the PID of your gvfs-daemon.service: - $ systemctl --user status gvfs-daemon.service | grep "Main PID:" + $ systemctl --user status gvfs-daemon.service | grep "Main PID:" 4. Check the environment of that process: - $ tr "\0" "\n" < /proc/$(pidof -s gvfsd)/environ + $ tr "\0" "\n" < /proc/$(pidof -s gvfsd)/environ Workaround: 1. Make the systemd user environment generator for gpg-agent executable: - $ sudo chmod +x /lib/systemd/user-environment-generators/90gpg-agent + $ sudo chmod +x /lib/systemd/user-environment-generators/90gpg-agent 2. Reboot system and login. - - I also noticed while trying to find a workaround, that after simple logout and re-login of my Gnome session, it sometimes appeared to be working as expected. But then failed again after full system restart. + I also noticed while trying to find a workaround, that after simple + logout and re-login of my Gnome session, it sometimes appeared to be + working as expected. But then failed again after full system restart. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901724 Title: Systemd user environment generator is not executable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnupg2/+bug/1901724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901724] Re: Systemd user environment generator is not executable.
Apparently the birthplace of that script is found here: GPG_AGENT_INFO and SSH_AUTH_SOCK not set in wayland sessions https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855868 ** Bug watch added: Debian Bug tracker #855868 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855868 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901724 Title: Systemd user environment generator is not executable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnupg2/+bug/1901724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 878188] Re: Network Manager assigns incorrect MAC address to eth devices
Its not NetworkManager. According to the NetworkManager.conf manpage the no-auto-default has nothing to do with it. Doing a Google search for that specific MAC address aa:00:04:00:0a:04 tells a different story. http://www.fantaghost.com/2010/06/eth0-mac-address-fixed-on- aa0004000a04/ Apparently installed DECnet software can do this on your system. I have found libdnet, dnet-common and xtrans-dev on my system. But don't ask me how it got there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/878188 Title: Network Manager assigns incorrect MAC address to eth devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/878188/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 782290] [NEW] package initramfs-tools 0.98.8ubuntu3 failed to install/upgrade: ErrorMessage: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
Public bug reported: Binary package hint: initramfs-tools boot patition, full. too many old kernels lingering there. ProblemType: Package DistroRelease: Ubuntu 11.04 Package: initramfs-tools 0.98.8ubuntu3 ProcVersionSignature: Ubuntu 2.6.35-29.51-generic 2.6.35.12 Uname: Linux 2.6.35-29-generic x86_64 Architecture: amd64 Date: Fri May 13 17:38:25 2011 ErrorMessage: ErrorMessage: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) PackageArchitecture: all SourcePackage: initramfs-tools Title: package initramfs-tools 0.98.8ubuntu3 failed to install/upgrade: ErrorMessage: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück UpgradeStatus: Upgraded to natty on 2011-05-13 (0 days ago) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package natty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/782290 Title: package initramfs-tools 0.98.8ubuntu3 failed to install/upgrade: ErrorMessage: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 782290] Re: package initramfs-tools 0.98.8ubuntu3 failed to install/upgrade: ErrorMessage: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/782290 Title: package initramfs-tools 0.98.8ubuntu3 failed to install/upgrade: ErrorMessage: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
