[Bug 1662552] Re: snaps don't work with NFS home
I purged and marked snapd hold to prevent reinstall. Get rid of it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1662552 Title: snaps don't work with NFS home To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1662552/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1662552] Re: snaps don't work with NFS home
I've solved my snap challenges problems with the following state entry in Saltstack cleanup_snapd: pkg.purged: - name: snapd pkg.held: - name: snapd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1662552 Title: snaps don't work with NFS home To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1662552/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1662552] Re: snaps don't work with NFS home
My solution has been to fully remove all snap functionality. sudo apt purge snapd sudo rm -vrf /snap /var/snap /var/lib/snapd /var/cache/snapd /usr/lib/snapd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1662552 Title: snaps don't work with NFS home To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1662552/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1774902]
The KDE_HOME_READONLY workaround stopped working and failure behavior changed last week after I applied updates to kubuntu 20.04. Instead of a logout as previously experienced, NFS home now results in a black screen with a mouse pointer. See attached apt history.log and .xsession-errors for more details. Please let me know what additional information I can provide to help resolve this issue. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1774902 Title: kubuntu - can't login with NFS $HOME To manage notifications about this bug go to: https://bugs.launchpad.net/kde-workspace/+bug/1774902/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1774902]
Created attachment 129548 apt history.log apt history log showing updates that correspond to timing of KDE_HOME_READONLY workaround no longer working. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1774902 Title: kubuntu - can't login with NFS $HOME To manage notifications about this bug go to: https://bugs.launchpad.net/kde-workspace/+bug/1774902/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1774902]
Created attachment 129549 .xsession-errors .xsession-errors file for new black screen behavior after recent updates. Note that the read-only home directory error is no longer displayed, so not sure how this relates to previous behavior. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1774902 Title: kubuntu - can't login with NFS $HOME To manage notifications about this bug go to: https://bugs.launchpad.net/kde-workspace/+bug/1774902/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1774902]
I can confirm this bug and workaround on kubuntu 20.04. $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04 LTS Release:20.04 Codename: focal $ $ ls -la $HOME/.config/plasma-workspace/env/nfs_home_workaround.sh -rwxr-xr-x 1 42 Jun 3 12:03 /vol/home//.config/plasma-workspace/env/nfs_home_workaround.sh $ $ cat $HOME/.config/plasma-workspace/env/nfs_home_workaround.sh #!/bin/sh export KDE_HOME_READONLY=TRUE $ -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to plasma-workspace in Ubuntu. https://bugs.launchpad.net/bugs/1774902 Title: kubuntu - can't login with NFS $HOME To manage notifications about this bug go to: https://bugs.launchpad.net/kde-workspace/+bug/1774902/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1878742] Re: KDE - can't login with NFS $HOME
** Package changed: snapd (Ubuntu) => kubuntu-meta (Ubuntu) ** Package changed: kubuntu-meta (Ubuntu) => kubuntu-packaging ** Project changed: kubuntu-packaging => kubuntu-meta (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878742 Title: KDE - can't login with NFS $HOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1878742/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1774902] Re: kubuntu - can't login with NFS $HOME
Reproducible on 20.04. kelleher@numbersix:~$ kelleher@numbersix:~$ lsb_release -rd Description:Ubuntu 20.04 LTS Release:20.04 kelleher@numbersix:~$ kelleher@numbersix:~$ apt-cache policy kubuntu-desktop kubuntu-desktop: Installed: 1.398 Candidate: 1.398 Version table: *** 1.398 500 500 http://us.archive.ubuntu.com/ubuntu focal/universe amd64 Packages 100 /var/lib/dpkg/status kelleher@numbersix:~$ kelleher@numbersix:~$ ls -la .xsession-errors -rw--- 1 kelleher kelleher 2816 May 14 22:33 .xsession-errors kelleher@numbersix:~$ kelleher@numbersix:~$ cat .xsession-errors Xsession: X session started for kelleher at Thu 14 May 2020 10:32:26 PM EDT dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/2000/bus dbus-update-activation-environment: setting DISPLAY=:0 dbus-update-activation-environment: setting XAUTHORITY=/vol/home/kelleher/.Xauthority localuser:kelleher being added to access control list dbus-update-activation-environment: setting QT_ACCESSIBILITY=1 dbus-update-activation-environment: setting SHELL=/bin/bash dbus-update-activation-environment: setting QT_ACCESSIBILITY=1 dbus-update-activation-environment: setting XDG_CONFIG_DIRS=/etc/xdg/xdg-plasma:/etc/xdg:/usr/share/kubuntu-default-settings/kf5-settings dbus-update-activation-environment: setting XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session2 dbus-update-activation-environment: setting DESKTOP_SESSION=plasma dbus-update-activation-environment: setting PWD=/vol/home/kelleher dbus-update-activation-environment: setting XDG_SESSION_DESKTOP=KDE dbus-update-activation-environment: setting LOGNAME=kelleher dbus-update-activation-environment: setting XDG_SESSION_TYPE=x11 dbus-update-activation-environment: setting GPG_AGENT_INFO=/run/user/2000/gnupg/S.gpg-agent:0:1 dbus-update-activation-environment: setting XAUTHORITY=/vol/home/kelleher/.Xauthority dbus-update-activation-environment: setting HOME=/vol/home/kelleher dbus-update-activation-environment: setting IM_CONFIG_PHASE=1 dbus-update-activation-environment: setting LANG=en_US.UTF-8 dbus-update-activation-environment: setting XDG_CURRENT_DESKTOP=KDE dbus-update-activation-environment: setting XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0 dbus-update-activation-environment: setting XDG_SESSION_CLASS=user dbus-update-activation-environment: setting USER=kelleher dbus-update-activation-environment: setting PAM_KWALLET5_LOGIN=/run/user/2000/kwallet5.socket dbus-update-activation-environment: setting DISPLAY=:0 dbus-update-activation-environment: setting SHLVL=1 dbus-update-activation-environment: setting XDG_RUNTIME_DIR=/run/user/2000 dbus-update-activation-environment: setting XDG_DATA_DIRS=/usr/share/plasma:/usr/local/share:/usr/share:/var/lib/snapd/desktop dbus-update-activation-environment: setting PATH=/vol/home/kelleher/.local/bin:/vol/home/kelleher/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/2000/bus dbus-update-activation-environment: setting _=/usr/bin/dbus-update-activation-environment kdeinit5: Aborting. No write access to $HOME directory (/vol/home/kelleher). The following installation problem was detected while trying to start KDE: No write access to $HOME directory (/vol/home/kelleher). KDE is unable to start. kelleher@numbersix:~$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1774902 Title: kubuntu - can't login with NFS $HOME To manage notifications about this bug go to: https://bugs.launchpad.net/kde-baseapps/+bug/1774902/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878742] [NEW] KDE - can't login with NFS $HOME
Public bug reported: If a users home directory is an NFS server, KDE fails to start with the error "No write access to $HOME directory". The fact that the error is logged to .xsession-errors in the users home directory is a bit ironic. This is reproducible on 20.04 and 18.04 kelleher@numbersix:~$ kelleher@numbersix:~$ lsb_release -rd Description:Ubuntu 20.04 LTS Release:20.04 kelleher@numbersix:~$ kelleher@numbersix:~$ apt-cache policy kubuntu-desktop kubuntu-desktop: Installed: 1.398 Candidate: 1.398 Version table: *** 1.398 500 500 http://us.archive.ubuntu.com/ubuntu focal/universe amd64 Packages 100 /var/lib/dpkg/status kelleher@numbersix:~$ kelleher@numbersix:~$ ls -la .xsession-errors -rw--- 1 kelleher kelleher 2816 May 14 22:33 .xsession-errors kelleher@numbersix:~$ kelleher@numbersix:~$ cat .xsession-errors Xsession: X session started for kelleher at Thu 14 May 2020 10:32:26 PM EDT dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/2000/bus dbus-update-activation-environment: setting DISPLAY=:0 dbus-update-activation-environment: setting XAUTHORITY=/vol/home/kelleher/.Xauthority localuser:kelleher being added to access control list dbus-update-activation-environment: setting QT_ACCESSIBILITY=1 dbus-update-activation-environment: setting SHELL=/bin/bash dbus-update-activation-environment: setting QT_ACCESSIBILITY=1 dbus-update-activation-environment: setting XDG_CONFIG_DIRS=/etc/xdg/xdg-plasma:/etc/xdg:/usr/share/kubuntu-default-settings/kf5-settings dbus-update-activation-environment: setting XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session2 dbus-update-activation-environment: setting DESKTOP_SESSION=plasma dbus-update-activation-environment: setting PWD=/vol/home/kelleher dbus-update-activation-environment: setting XDG_SESSION_DESKTOP=KDE dbus-update-activation-environment: setting LOGNAME=kelleher dbus-update-activation-environment: setting XDG_SESSION_TYPE=x11 dbus-update-activation-environment: setting GPG_AGENT_INFO=/run/user/2000/gnupg/S.gpg-agent:0:1 dbus-update-activation-environment: setting XAUTHORITY=/vol/home/kelleher/.Xauthority dbus-update-activation-environment: setting HOME=/vol/home/kelleher dbus-update-activation-environment: setting IM_CONFIG_PHASE=1 dbus-update-activation-environment: setting LANG=en_US.UTF-8 dbus-update-activation-environment: setting XDG_CURRENT_DESKTOP=KDE dbus-update-activation-environment: setting XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0 dbus-update-activation-environment: setting XDG_SESSION_CLASS=user dbus-update-activation-environment: setting USER=kelleher dbus-update-activation-environment: setting PAM_KWALLET5_LOGIN=/run/user/2000/kwallet5.socket dbus-update-activation-environment: setting DISPLAY=:0 dbus-update-activation-environment: setting SHLVL=1 dbus-update-activation-environment: setting XDG_RUNTIME_DIR=/run/user/2000 dbus-update-activation-environment: setting XDG_DATA_DIRS=/usr/share/plasma:/usr/local/share:/usr/share:/var/lib/snapd/desktop dbus-update-activation-environment: setting PATH=/vol/home/kelleher/.local/bin:/vol/home/kelleher/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/2000/bus dbus-update-activation-environment: setting _=/usr/bin/dbus-update-activation-environment kdeinit5: Aborting. No write access to $HOME directory (/vol/home/kelleher). The following installation problem was detected while trying to start KDE: No write access to $HOME directory (/vol/home/kelleher). KDE is unable to start. kelleher@numbersix:~$ ** Affects: kubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: kde nfs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878742 Title: KDE - can't login with NFS $HOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1878742/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1774902] Re: kubuntu - can't login with NFS $HOME
** Also affects: kde-baseapps Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1774902 Title: kubuntu - can't login with NFS $HOME To manage notifications about this bug go to: https://bugs.launchpad.net/kde-baseapps/+bug/1774902/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1774902] Re: kubuntu - can't login with NFS $HOME
Anyone know if this affects KDE on 19.10? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1774902 Title: kubuntu - can't login with NFS $HOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1774902/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1577575] Re: NFS share does not mount on boot using fstab
I did a little more testing and this looks to be specific to /home. Even mounting over /home (no linking) with autofs results in the same issue. All autofs files as well as the list of packages installed have been attached. As a side note, having /home as a link is an artifact of some very old build scripts and worked fine with an /etc/fstab NFS mount. autofs was deployed as a workaround for bug #1577575. The new workaround for both these bugs is to update all /etc/passwd entries to /vol/home/. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1577575 Title: NFS share does not mount on boot using fstab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1577575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1577575] Re: NFS share does not mount on boot using fstab
Sorry - those last two comments were meant for bug #1827286. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1577575 Title: NFS share does not mount on boot using fstab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1577575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827286] Re: autofs - "Too many levels of symbolic links" after apt upgrade
I did a little more testing and this looks to be specific to /home. Even mounting over /home (no linking) with autofs results in the same issue. All autofs files as well as the list of packages installed have been attached. As a side note, having /home as a link is an artifact of some very old build scripts and worked fine with an /etc/fstab NFS mount. autofs was deployed as a workaround for bug #1577575. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827286 Title: autofs - "Too many levels of symbolic links" after apt upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1827286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827286] Re: autofs - "Too many levels of symbolic links" after apt upgrade
** Attachment added: "chi.packages" https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1827286/+attachment/5261280/+files/chi.packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827286 Title: autofs - "Too many levels of symbolic links" after apt upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1827286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1577575] Re: NFS share does not mount on boot using fstab
** Attachment added: "chi.packages" https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1577575/+attachment/5261278/+files/chi.packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1577575 Title: NFS share does not mount on boot using fstab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1577575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827286] Re: autofs - "Too many levels of symbolic links" after apt upgrade
** Attachment added: "auto.master" https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1827286/+attachment/5261274/+files/auto.master -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827286 Title: autofs - "Too many levels of symbolic links" after apt upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1827286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827286] Re: autofs - "Too many levels of symbolic links" after apt upgrade
** Attachment added: "auto.direct1" https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1827286/+attachment/5261267/+files/auto.direct1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827286 Title: autofs - "Too many levels of symbolic links" after apt upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1827286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827286] Re: autofs - "Too many levels of symbolic links" after apt upgrade
** Attachment added: "auto.net" https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1827286/+attachment/5261269/+files/auto.net -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827286 Title: autofs - "Too many levels of symbolic links" after apt upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1827286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827286] Re: autofs - "Too many levels of symbolic links" after apt upgrade
** Attachment added: "auto.misc" https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1827286/+attachment/5261271/+files/auto.misc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827286 Title: autofs - "Too many levels of symbolic links" after apt upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1827286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827286] Re: autofs - "Too many levels of symbolic links" after apt upgrade
** Attachment added: "auto.smb" https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1827286/+attachment/5261268/+files/auto.smb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827286 Title: autofs - "Too many levels of symbolic links" after apt upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1827286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827286] Re: autofs - "Too many levels of symbolic links" after apt upgrade
** Attachment added: "autofs.conf" https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1827286/+attachment/5261266/+files/autofs.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827286 Title: autofs - "Too many levels of symbolic links" after apt upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1827286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827286] Re: autofs - "Too many levels of symbolic links" after apt upgrade
** Attachment added: "master.d_direct1.autofs" https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1827286/+attachment/5261265/+files/master.d_direct1.autofs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827286 Title: autofs - "Too many levels of symbolic links" after apt upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1827286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827286] Re: autofs - "Too many levels of symbolic links" after apt upgrade
Looks like the issue is symlinking to a director prior to autofs mounting it. Everything fine... root@numbersix:/# ssh chi uname -a Linux chi 4.4.0-146-generic #172-Ubuntu SMP Wed Apr 3 09:00:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux root@chi:~# ls -la /home ls: cannot access '/home': No such file or directory root@chi:~# root@numbersix:/# ssh chi 'ls -la /vol/*' /vol/home: total 8 drwxr-xr-x 1 root root 154 Apr 21 19:10 . drwxr-xr-x 5 root root 4096 Jul 2 2018 .. drwxr-xr-x 1 2005 2005 1070 Nov 17 2015 bethann [trimmed] /vol/media: total 4 drwxr-xr-x 1 root root 128 Apr 13 18:29 . drwxr-xr-x 5 root root 4096 Jul 2 2018 .. [trimmed] /vol/zhora-temp: total 24 dr-xr-xr-x 6 root root 4096 Mar 3 08:21 . drwxr-xr-x 5 root root 4096 Jul 2 2018 .. [trimmed] root@numbersix:/# Everything works fine if the link is made after... root@chi:/# ln -s /vol/home root@chi:/# ls -la /home lrwxrwxrwx 1 root root 9 May 2 12:11 /home -> /vol/home root@chi:/# root@chi:/# ls -la /vol/* /vol/home: total 8 drwxr-xr-x 1 root root 154 Apr 21 19:10 . drwxr-xr-x 5 root root 4096 Jul 2 2018 .. [trimmed] /vol/media: total 4 drwxr-xr-x 1 root root 128 Apr 13 18:29 . drwxr-xr-x 5 root root 4096 Jul 2 2018 .. [trimmed] /vol/zhora-temp: total 24 dr-xr-xr-x 6 root root 4096 Mar 3 08:21 . drwxr-xr-x 5 root root 4096 Jul 2 2018 .. [trimmed] root@chi:/# It breaks after the reboot... root@chi:/# init 6 Connection to chi closed by remote host. Connection to chi closed. root@numbersix:~# root@chi:/# init 6 Connection to chi closed by remote host. Connection to chi closed. root@numbersix:~# root@numbersix:~# root@numbersix:~# ssh chi Welcome to Ubuntu 16.04.6 LTS (GNU/Linux 4.4.0-146-generic x86_64) * Documentation: https://help.ubuntu.com * Management: https://landscape.canonical.com * Support:https://ubuntu.com/advantage 21 packages can be updated. 15 updates are security updates. New release '18.04.2 LTS' available. Run 'do-release-upgrade' to upgrade to it. root@chi:~# ls -la /vol/* ls: cannot open directory '/vol/home': Too many levels of symbolic links /vol/media: total 4 drwxr-xr-x 1 root root 128 Apr 13 18:29 . drwxr-xr-x 5 root root 4096 Jul 2 2018 .. [trimmed] /vol/zhora-temp: total 24 dr-xr-xr-x 6 root root 4096 Mar 3 08:21 . drwxr-xr-x 5 root root 4096 Jul 2 2018 .. [trimmed] root@chi:~# At this point, the link needs to be deleted and the VM rebooted to get back to a normal state - just restarting autofs won't clear it. ** Package changed: systemd (Ubuntu) => autofs5 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827286 Title: autofs - "Too many levels of symbolic links" after apt upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1827286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827286] Re: autofs - "Too many levels of symbolic links" after apt upgrade
** Tags added: autofs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827286 Title: autofs - "Too many levels of symbolic links" after apt upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1827286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827286] [NEW] autofs - "Too many levels of symbolic links" after apt upgrade
Public bug reported: Description:Ubuntu 16.04.6 LTS Release:16.04 I moved to autofs this week as a workaround for Bug #1577575 failing to mount NFS entries at boot. This worked file until I ran 'apt upgrade' today. Now trying to access /vol/home mount results in the following error: root@chi:~# ls -la /vol/home/ ls: cannot access '/vol/home/': Too many levels of symbolic links root@chi:~# Oddly enough, the other two autofs entries work fine (output trimmed): root@chi:~# ls -la /vol/media total 4 ... root@chi:~# root@chi:~# ls -al /vol/temp/ total 24 ... root@chi:~# I have a scratch VM I can break tonight by performing upgrades individually and testing after each. Will provide that detail when available. Here is /var/log/apt/history.log Start-Date: 2019-05-01 17:37:00 Commandline: apt upgrade Upgrade: libdns-export162:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12, 1:9.10.3.dfsg.P4-8ubuntu1.14), libisccfg140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12, 1:9.10.3.dfsg.P4-8ubuntu1.14), ureadahead:amd64 (0.100.0-19, 0.100.0-19.1), libldap-2.4-2:amd64 (2.4.42+dfsg-2ubuntu3.4, 2.4.42+dfsg-2ubuntu3.5), libirs141:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12, 1:9.10.3.dfsg.P4-8ubuntu1.14), bind9-host:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12, 1:9.10.3.dfsg.P4-8ubuntu1.14), dnsutils:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12, 1:9.10.3.dfsg.P4-8ubuntu1.14), libisc160:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12, 1:9.10.3.dfsg.P4-8ubuntu1.14), passwd:amd64 (1:4.2-3.1ubuntu5.3, 1:4.2-3.1ubuntu5.4), bind9utils:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12, 1:9.10.3.dfsg.P4-8ubuntu1.14), libisc-export160:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12, 1:9.10.3.dfsg.P4-8ubuntu1.14), liblwres141:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12, 1:9.10.3.dfsg.P4-8ubuntu1.14), login:amd64 (1:4.2-3.1ubuntu5.3, 1:4.2-3.1ubuntu5.4), iproute2:amd64 (4.3.0-1ubuntu3.16.04.4, 4.3.0-1ubuntu3.16.04.5), bind9:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12, 1:9.10.3.dfsg.P4-8ubuntu1.14), libdns162:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12, 1:9.10.3.dfsg.P4-8ubuntu1.14), unattended-upgrades:amd64 (0.90ubuntu0.10, 1.1ubuntu1.18.04.7~16.04.2), libisccc140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12, 1:9.10.3.dfsg.P4-8ubuntu1.14), libbind9-140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12, 1:9.10.3.dfsg.P4-8ubuntu1.14), uidmap:amd64 (1:4.2-3.1ubuntu5.3, 1:4.2-3.1ubuntu5.4), bind9-doc:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12, 1:9.10.3.dfsg.P4-8ubuntu1.14), tzdata:amd64 (2018i-0ubuntu0.16.04, 2019a-0ubuntu0.16.04) End-Date: 2019-05-01 17:37:24 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827286 Title: autofs - "Too many levels of symbolic links" after apt upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1827286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1577575] Re: NFS share does not mount on boot using fstab
Quick update - switched to autofs as a workaround for this 16.04 issue. That was fine until I ran 'apt upgrade' today. Now I get the following error: root@chi:~# ls -la /vol/home/ ls: cannot access '/vol/home/': Too many levels of symbolic links root@chi:~# I'll be opening a new bug for autofs while considering a move back to Debian or a jump to CentOS. If anyone is using autofs as a workaround for the systemd issue, be very careful with an apt upgrade. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1577575 Title: NFS share does not mount on boot using fstab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1577575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1577575] Re: NFS share does not mount on boot using fstab
I should note this is impacting an image built from 16.04.4. Another image built from 16.04.1 is working fine. Both have been pulled forward via apt dist-upgrade and their behaviors differ - concerning in it's own right. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1577575 Title: NFS share does not mount on boot using fstab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1577575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1577575] Re: NFS share does not mount on boot using fstab
Same issue here. NFS fails to mount at boot, but logging in and issuing a manual "mount -a" resolves until the next reboot. It should also be noted that there's a significant delay on boot with nfs entries in fstab - need to time it, but ~1 minute. Why issues with something as old/stable/boring as NFS? ** Also affects: nfs-utils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1577575 Title: NFS share does not mount on boot using fstab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1577575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1662552] Re: snaps don't work with NFS home
The issue appears larger than just NFS mounted $HOME. After I used the workaround provided to get the filebot snap to run with an NFS mounted $HOME, I was unable to use it to manipulate any files in my NFS mounted media library. I gave up and just loaded the deb package. Should this be reported as a separate bug? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1662552 Title: snaps don't work with NFS home To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1662552/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1774902] [NEW] kubuntu - can't login with NFS $HOME
Public bug reported: If $HOME is an NFS mount, startkde show a write error and fails to start ksmserver. Xsession: X session started for kelleher at Fri Jun 1 20:45:36 EDT 2018 localuser:kelleher being added to access control list openConnection: connect: No such file or directory cannot connect to brltty at :0 Loading stage "initial" 247 startkde: Starting up... dbus-update-activation-environment: warning: error sending to systemd: org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1 kdeinit5: Aborting. No write access to $HOME directory (/home/kelleher). kdeinit5_wrapper: Warning: connect(/run/user/1000/kdeinit5__0) failed: : No such file or directory The following installation problem was detected while trying to start KDE: No write access to $HOME directory (/home/kelleher). KDE is unable to start. startkde: Could not start ksmserver. Check your installation. startkde: Shutting down... kdeinit5_wrapper: Warning: connect(/run/user/1000/kdeinit5__0) failed: : No such file or directory Error: Can not contact kdeinit5! startkde: Done. Xsession: X session started for kelleher at Sun Jun 3 19:39:04 EDT 2018 dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus dbus-update-activation-environment: setting DISPLAY=:0 dbus-update-activation-environment: setting XAUTHORITY=/home/kelleher/.Xauthority localuser:kelleher being added to access control list dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge dbus-update-activation-environment: setting QT_ACCESSIBILITY=1 dbus-update-activation-environment: setting LANG=en_US.UTF-8 dbus-update-activation-environment: setting DISPLAY=:0 dbus-update-activation-environment: setting PAM_KWALLET5_LOGIN=/run/user/1000/kwallet5.socket dbus-update-activation-environment: setting MANDATORY_PATH=/usr/share/gconf/plasma.mandatory.path dbus-update-activation-environment: setting USER=kelleher dbus-update-activation-environment: setting DESKTOP_SESSION=plasma dbus-update-activation-environment: setting DEFAULTS_PATH=/usr/share/gconf/plasma.default.path dbus-update-activation-environment: setting PWD=/home/kelleher dbus-update-activation-environment: setting HOME=/home/kelleher dbus-update-activation-environment: setting QT_ACCESSIBILITY=1 dbus-update-activation-environment: setting XDG_SESSION_TYPE=x11 dbus-update-activation-environment: setting XDG_DATA_DIRS=/usr/share/plasma:/usr/local/share:/usr/share:/var/lib/snapd/desktop dbus-update-activation-environment: setting XDG_SESSION_DESKTOP=KDE dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge dbus-update-activation-environment: setting SHELL=/bin/bash dbus-update-activation-environment: setting XDG_SESSION_CLASS=user dbus-update-activation-environment: setting XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0 dbus-update-activation-environment: setting IM_CONFIG_PHASE=1 dbus-update-activation-environment: setting XDG_CURRENT_DESKTOP=KDE dbus-update-activation-environment: setting GPG_AGENT_INFO=/run/user/1000/gnupg/S.gpg-agent:0:1 dbus-update-activation-environment: setting SHLVL=1 dbus-update-activation-environment: setting LOGNAME=kelleher dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus dbus-update-activation-environment: setting XDG_RUNTIME_DIR=/run/user/1000 dbus-update-activation-environment: setting PAM_KWALLET_LOGIN=/run/user/1000/kwallet.socket dbus-update-activation-environment: setting XAUTHORITY=/home/kelleher/.Xauthority dbus-update-activation-environment: setting XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session1 dbus-update-activation-environment: setting XDG_CONFIG_DIRS=/etc/xdg/xdg-plasma:/etc/xdg:/usr/share/kubuntu-default-settings/kf5-settings dbus-update-activation-environment: setting PATH=/home/kelleher/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin dbus-update-activation-environment: setting _=/usr/bin/dbus-update-activation-environment kcm_input: Using X11 backend startkde: Starting up... kdeinit5: Aborting. No write access to $HOME directory (/home/kelleher). kdeinit5_wrapper: Warning: connect(/run/user/1000/kdeinit5__0) failed: : No such file or directory The following installation problem was detected while trying to start KDE: No write access to $HOME directory (/home/kelleher). KDE is unable to start. startkde: Could not start ksmserver. Check your installation. startkde: Shutting down... kdeinit5_wrapper: Warning: connect(/run/user/1000/kdeinit5__0) failed: : No such file or directory Error: Can not contact kdeinit5! startkde: Done. ** Affects: snapd (Ubuntu) Importance: Undecided Status: New ** Tags: kubuntu-desktop nfs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1774902 Title: kubuntu - can't login
[Bug 1567051] [NEW] package mysql-common 5.7.11-0ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
Public bug reported: Unable to install/update mysq[common|server]-5.7 on Ubuntu 16.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: mysql-common 5.7.11-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6 Uname: Linux 4.4.0-17-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 Date: Wed Apr 6 16:44:10 2016 Dependencies: DuplicateSignature: Setting up mysql-common (5.7.11-0ubuntu4) ... update-alternatives: error: alternative path /etc/mysql/my.cnf.fallback doesn't exist dpkg: error processing package mysql-common (--configure): subprocess installed post-installation script returned error exit status 2 ErrorMessage: subprocess installed post-installation script returned error exit status 2 InstallationDate: Installed on 2016-01-22 (74 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160122.2) Logs.var.log.daemon.log: Logs.var.log.mysql.error.log: MySQLConf.etc.mysql.conf.d.mysqld.safe.syslog.cnf: [mysqld_safe] syslog MySQLConf.etc.mysql.mysql.conf.d.mysqld.safe.syslog.cnf: [mysqld_safe] syslog MySQLVarLibDirListing: ['mysql_upgrade_info', 'xanterra_20150601', 'sys', 'mysql', 'ib_buffer_pool', 'ibtmp1', 'ideabase', 'hhi_20150115', 'ib_logfile0', 'auto.cnf', 'wordpress', 'performance_schema', 'debian-5.7.flag', 'postfixadmin', 'ibdata1', 'ib_logfile1', 'debian-5.6.flag'] PackageArchitecture: all ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-17-generic root=UUID=13e4da31-ec8c-4036-99d9-51b43200ff10 ro console RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.9 SourcePackage: mysql-5.7 Title: package mysql-common 5.7.11-0ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.mysql.conf.d.mysql.cnf: [deleted] modified.conffile..etc.mysql.conf.d.mysqldump.cnf: [deleted] modified.conffile..etc.mysql.my.cnf.fallback: [deleted] ** Affects: mysql-5.7 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check package-from-proposed xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1567051 Title: package mysql-common 5.7.11-0ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1567051/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1314587] Re: Windows slow/stall/freeze when minimizing/restoring/etc in Unity 7 14.04
Still affecting me pretty severely, I have all software updates. I'm using a Nvida Optimus card as well. Occurs with both Nouveau and Nvidia drivers, as reported. I'm using the Intel card with the Nvidia drivers. Minimize freezes the system about 90% of the time. I have to drop to shell and reboot to get usable system back. Launching Dash freezes the system occasionally as well. As long as I only task switch and show desktop, I'm mostly okay, but it's very irritating. I also disabled all the animations with CompizConfig Settings, but it didn't help much. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1314587 Title: Windows slow/stall/freeze when minimizing/restoring/etc in Unity 7 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1314587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1301490] Re: PRIME Profiles option no longer available in Nvidia Settings
Blacklisting the nouveau driver worked for me. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1301490 Title: PRIME Profiles option no longer available in Nvidia Settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1301490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1308187] Re: Python (v2.7) requires to install plugins to play media files of the following typ
Thanks for the patch, I was having the same issue and this fixed it for me as well. Much appreciated! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1308187 Title: Python (v2.7) requires to install plugins to play media files of the following typ To manage notifications about this bug go to: https://bugs.launchpad.net/soundconverter/+bug/1308187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 958492] Re: Network disconnected notification doesn't work after clicking Don't show this message again
It appears that this bug has been fixed in the latest Precise update. The notification disappears quickly now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/958492 Title: Network disconnected notification doesn't work after clicking Don't show this message again To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/958492/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 958492] Re: Network disconnected notification doesn't work after clicking Don't show this message again
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/958492 Title: Network disconnected notification doesn't work after clicking Don't show this message again To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/958492/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 958492] [NEW] Network disconnected notification doesn't work after clicking Don't show this message again
Public bug reported: In Gnome Shell when your computer comes out of Suspend mode, there is a notification that says Network Disconnected - You are now offline with a button that says Never show this message again. The intended behavior of this notification is that it will disappear as soon as the network is connected again. However, if you push the Never show this message again button, not only does it continue to show that notification at those times, but from that point on, you have to click the button to make it disappear, or it will just stay on the screen forever. Before I clicked that button the first time, the notification would disappear, like it is meant to. Obviously, the Never show this message again button is meant to never show that notification from that point on, but clicking that button makes it even worse than it was before. This bug is noticeable especially after your laptop lid has been shut and you open it to come out of Suspend mode. I have noticed this behavior in Ubuntu 11.10 and Precise. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-shell 3.3.90-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 Date: Sun Mar 18 07:48:38 2012 ExecutablePath: /usr/bin/gnome-shell InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: Upgraded to precise on 2012-03-13 (5 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/958492 Title: Network disconnected notification doesn't work after clicking Don't show this message again To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/958492/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 883443] Re: GNOME Shell 3.2.0 falsely states: Network Disconnected - you are now offline
This is my experience with this bug. It only happens when I am disconnected, usually from going into suspend mode when shutting my laptop lid. When I open the lid and come back into live mode, I get this notification, and it doesn't disappear until I click it. But one thing I have noticed is that it didn't start happening until after I did two things. The first thing I did was turn off notifications in the profile menu in the upper right corner. The second thing I did was click the button that said something like Never show this message again. I don't know which is the cause, but I suspect it is from turning off notifications in that menu. I just had to reinstall Ubuntu, and I can verify that with a fresh install and after setting up everything how I need it, the notification disappears after the timeout, like it is supposed to. I haven't done either of the two things mentioned earlier, and it is still working normally. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/883443 Title: GNOME Shell 3.2.0 falsely states: Network Disconnected - you are now offline To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/883443/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 428396] Re: gnometris doesn't display the game area
Ubuntu must use the open source Radeon DRI2 driver or ATI must support GL-on-GL. There is no other fix. -- gnometris doesn't display the game area https://bugs.launchpad.net/bugs/428396 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 428396] Re: gnometris doesn't display the game area
Ubuntu should be shipping radeon with KMS and DRI2 enabled. If they aren't, that's a bug. -- gnometris doesn't display the game area https://bugs.launchpad.net/bugs/428396 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
Re: [Bug 428396] Re: gnometris doesn't display the game area
The open source driver uses DRI2 and is not affected by fglrx's shortcomings. I would recommend the open source radeon driver. On Sat, Oct 17, 2009 at 8:48 PM, gavintlgold puttabu...@gmail.com wrote: It's unfortunate that this happens, but any way to disable the clutter graphics while desktop effects are running until the fgrlx bug is fixed? As it is, it's unplayable with standard Karmic settings, and a new user would be stumped. -- gnometris doesn't display the game area https://bugs.launchpad.net/bugs/428396 You received this bug notification because you are a direct subscriber of the bug. Status in “gnome-games” package in Ubuntu: Incomplete Bug description: Binary package hint: gnome-games When I run gnometris I can see: $ gnometris (gnometris:7026): ClutterGLX-CRITICAL **: Unable to make the stage window 0x520003c the current GLX drawable (gnometris:7026): ClutterGLX-CRITICAL **: Unable to make the stage window 0x5200057 the current GLX drawable You can see the attached image for more information. More info: $ dpkg -l gnometris Desired=Unknown/Install/Remove/Purge/Hold | Estado=No/Instalado/Config-files/Desempaquetado/Fallo-config/Medio-inst/espera-disparo/pendiente-disparo |/ Err?=(ninguno)/Retenido/Requiere-reinst/X=ambos problemas (Estado,Err: mayúsc.=malo) ||/ Nombre Versión Descripción +++-==-==- ii gnometris 1:2.27.92-0ubu Falling blocks game ProblemType: Bug Architecture: amd64 Date: Sat Sep 12 15:57:47 2009 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: fglrx wl Package: gnometris 1:2.27.92-0ubuntu1 ProcEnviron: PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-10.32-generic SourcePackage: gnome-games Uname: Linux 2.6.31-10-generic x86_64 -- gnometris doesn't display the game area https://bugs.launchpad.net/bugs/428396 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 428396] Re: gnometris doesn't display the game area
This is a bug in fglrx, not Gnometris (or Clutter). It works fine on Intel and NVidia. -- gnometris doesn't display the game area https://bugs.launchpad.net/bugs/428396 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
Re: [Bug 428396] Re: gnometris doesn't display the game area
Yes, 2.28 is the first release with Clutter. On Oct 5, 2009 7:30 PM, Serge se...@bobtheblueberry.com wrote: But it only happens in kramic koala not earlier releases -- gnometris doesn't display the game area https://bugs.launchpad.net/bugs/428396 You received thi... -- gnometris doesn't display the game area https://bugs.launchpad.net/bugs/428396 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 435633] Re: in Gnometris, the game option Show where the block will land doesn't take effect
This bug is already open upstream. https://bugzilla.gnome.org/show_bug.cgi?id=594970 ** Bug watch added: GNOME Bug Tracker #594970 http://bugzilla.gnome.org/show_bug.cgi?id=594970 -- in Gnometris, the game option Show where the block will land doesn't take effect https://bugs.launchpad.net/bugs/435633 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 428396] Re: gnometris doesn't display the game area
Hi, I am the upstream maintainer of Gnometris. This appears to be a bug in fglrx. The critical warnings are harmless, as far as I know--I get them they do not cause any issues. Can you try without compositing window manager? I think that fglrx is failing to render OpenGL while compositing. -- gnometris doesn't display the game area https://bugs.launchpad.net/bugs/428396 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 230163] Re: gnome-games should depend on python-glade2
gnome-sudoku IS NOT gnome-games. Please stop confusing the two; do not file any more bug reports on gnome-sudoku; it should have been removed from the Ubuntu repositories ages ago. -- gnome-games should depend on python-glade2 https://bugs.launchpad.net/bugs/230163 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 230163] Re: gnome-sudoku should be removed from ubuntu repos
I am upstream. The issue is that gnome-sudoku is still in your repos. despite being told repeatedly (elsewhere) to remove it. gnome-sudoku is part of Gnome Games now and uses the same .py files and paths that the (very) old gnome-sudoku uses. This is a case that python-support cannot handle correctly. That is the issue and that is why there is so much confusion over this bug. ** Summary changed: - gnome-games should depend on python-glade2 + gnome-sudoku should be removed from ubuntu repos ** Changed in: gnome-sudoku (Ubuntu) Sourcepackagename: gnome-games = gnome-sudoku Status: Incomplete = New -- gnome-sudoku should be removed from ubuntu repos https://bugs.launchpad.net/bugs/230163 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 207114] Re: package glchess 1.0+debian-1 failed to install/upgrade:
*** This bug is a duplicate of bug 234865 *** https://bugs.launchpad.net/bugs/234865 ** This bug has been marked a duplicate of bug 138509 package glchess None [modified: /var/lib/dpkg/info/glchess.list] failed to install/upgrade: trying to overwrite `/usr/share/applications/glchess.desktop', which is also in package gnome-games ** This bug is no longer a duplicate of bug 138509 package glchess None [modified: /var/lib/dpkg/info/glchess.list] failed to install/upgrade: trying to overwrite `/usr/share/applications/glchess.desktop', which is also in package gnome-games ** This bug has been marked a duplicate of bug 234865 Package glchess fails to install and ask removal of gnome-games -- package glchess 1.0+debian-1 failed to install/upgrade: https://bugs.launchpad.net/bugs/207114 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 234865] Re: Package glchess fails to install and ask removal of gnome-games
** This bug has been marked a duplicate of bug 138509 package glchess None [modified: /var/lib/dpkg/info/glchess.list] failed to install/upgrade: trying to overwrite `/usr/share/applications/glchess.desktop', which is also in package gnome-games ** This bug is no longer a duplicate of bug 138509 package glchess None [modified: /var/lib/dpkg/info/glchess.list] failed to install/upgrade: trying to overwrite `/usr/share/applications/glchess.desktop', which is also in package gnome-games -- Package glchess fails to install and ask removal of gnome-games https://bugs.launchpad.net/bugs/234865 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 239905] Re: glchess fails to render in 3d view
I have applied your patch to Gnome Games upstream. It will be in release 2.23.5. Thanks for the good work! ** Changed in: glchess (Ubuntu) Assignee: (unassigned) = Jason D. Clinton (me-jasonclinton) Status: New = Fix Committed -- glchess fails to render in 3d view https://bugs.launchpad.net/bugs/239905 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 230163] Re: gnome-sudoku won't start
On Debian, you need python-gnome2 and python-gnome2-desktop. ** Changed in: gnome-sudoku (Ubuntu) Status: New = Confirmed -- gnome-sudoku won't start https://bugs.launchpad.net/bugs/230163 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 230163] Re: gnome-sudoku won't start
Hi, I'm an Gnome Games maintainer in upstream. This appears to be a dependency problem in the Ubuntu package. It should depend on python.*gnome.*desktop. -- gnome-sudoku won't start https://bugs.launchpad.net/bugs/230163 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 153716] Re: Bad gnome vfs support
Hello. We are using firefox-2 on a large LTSP enterprise desktop roll- out and this bug is still there in Hardy. I have tested Debian unstable and the bug is not there so it's probably related to the way the firefox-2-gnome-support package is being built. -- Bad gnome vfs support https://bugs.launchpad.net/bugs/153716 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 153716] Re: Bad gnome vfs support
** Changed in: firefox (Ubuntu) Assignee: (unassigned) = Mozilla Team (mozillateam) -- Bad gnome vfs support https://bugs.launchpad.net/bugs/153716 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
