[Bug 1939592] Re: Login screen (gdm3) is purple blank after switching userA -> userB -> userA again
** Description changed:
Login screen (gdm3) is purple blank after switching userA -> userB ->
userA again.
Sometimes need to switch 5 times.. but definitely after around 5 times
gdm3 breaks (it shows just a blank purple screen with the cursor).
## Workaround
Ctrl+Alt+F3 (or F4.. F5...) until I get to the user I need to (and unlock the
screensaver there).
OR: switch to the console and run "exec sudo systemctl restart gdm3". ("exec"
is not necessary but highly desirable from the security point of view, so there
won't be a logged in session).
## Workaround 2
To not use gdm3. There are alternatives such as sddm or ligthdm:
sudo apt install sddm
OR
sudo apt install lightdm
-
Ctrl+Alt+F5 (drop to a console)
sudo systemctl stop gdm3
exec sudo systemctl start display-manager
-
## Details
arno@z390-linux:~$ dpkg -l gdm3
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==-===--=
ii gdm3 3.36.3-0ubuntu0.20.04.4 amd64GNOME Display Manager
arno@z390-linux:~$ cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-5.11.0-25-generic
root=UUID=a39515ec-3bed-493b-8286-3904a4aac9de ro quiet splash vt.handoff=7
arno@z390-linux:~$ nvidia-smi
Wed Aug 11 16:42:07 2021
+-+
| NVIDIA-SMI 460.91.03Driver Version: 460.91.03CUDA Version: 11.2
|
|---+--+--+
| GPU NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC
|
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M.
|
| | | MIG M.
|
|===+==+==|
| 0 GeForce RTX 207... Off | :01:00.0 On | N/A
|
| 0% 37CP817W / 215W |473MiB / 7979MiB | 1% Default
|
| | | N/A
|
+---+--+--+
+-+
| Processes:
|
| GPU GI CIPID Type Process name GPU Memory
|
|ID ID Usage
|
|=|
|0 N/A N/A 2211 G /usr/lib/xorg/Xorg 35MiB
|
|0 N/A N/A 10496 G /usr/lib/xorg/Xorg106MiB
|
|0 N/A N/A 10626 G /usr/bin/gnome-shell 157MiB
|
|0 N/A N/A 16828 G /usr/lib/xorg/Xorg 35MiB
|
|0 N/A N/A 38063 G ...A= --shared-files 80MiB
|
+-+
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gdm3 3.36.3-0ubuntu0.20.04.4
ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-25-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset
nvidia
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Aug 11 16:37:35 2021
InstallationDate: Installed on 2020-09-26 (318 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)
** Description changed:
Login screen (gdm3) is purple blank after switching userA -> userB ->
userA again.
Sometimes need to switch 5 times.. but definitely after around 5 times
gdm3 breaks (it shows just a blank purple screen with the cursor).
## Workaround
Ctrl+Alt+F3 (or F4.. F5...) until I get to the user I need to (and unlock the
screensaver there).
OR: switch to the console and run "exec sudo systemctl restart gdm3". ("exec"
is not necessary but highly desirable from the security point of view, so there
won't be a logged in session).
## Workaround 2
To not use gdm3. There are alternatives such as sddm or ligthdm:
-
- sudo apt install sddm
-
- OR
sudo apt install lightdm
Ctrl+Alt+F5 (drop to a console)
sudo systemctl stop gdm3
exec sudo systemctl start display-manager
## Details
arno@z390-linux:~$ dpkg -l gdm3
Desired=Unknown/Install/Remove/Purge/Hold
|
[Bug 1939592] Re: Login screen (gdm3) is purple blank after switching userA -> userB -> userA again
** Description changed:
Login screen (gdm3) is purple blank after switching userA -> userB ->
userA again.
Sometimes need to switch 5 times.. but definitely after around 5 times
gdm3 breaks (it shows just a blank purple screen with the cursor).
## Workaround
Ctrl+Alt+F3 (or F4.. F5...) until I get to the user I need to (and unlock the
screensaver there).
OR: switch to the console and run "exec sudo systemctl restart gdm3". ("exec"
is not necessary but highly desirable from the security point of view, so there
won't be a logged in session).
+ ## Workaround 2
+
+ To not use gdm3. There are alternatives such as sddm or ligthdm:
+
+ sudo apt install sddm
+
+ OR
+
+ sudo apt install lightdm
+
+
+ Ctrl+Alt+F5 (drop to a console)
+ sudo systemctl stop gdm3
+ exec sudo systemctl start display-manager
+
+
+ ## Details
+
arno@z390-linux:~$ dpkg -l gdm3
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==-===--=
ii gdm3 3.36.3-0ubuntu0.20.04.4 amd64GNOME Display Manager
- arno@z390-linux:~$ cat /proc/cmdline
+ arno@z390-linux:~$ cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-5.11.0-25-generic
root=UUID=a39515ec-3bed-493b-8286-3904a4aac9de ro quiet splash vt.handoff=7
- arno@z390-linux:~$ nvidia-smi
- Wed Aug 11 16:42:07 2021
+ arno@z390-linux:~$ nvidia-smi
+ Wed Aug 11 16:42:07 2021
+-+
| NVIDIA-SMI 460.91.03Driver Version: 460.91.03CUDA Version: 11.2
|
|---+--+--+
| GPU NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC
|
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M.
|
| | | MIG M.
|
|===+==+==|
| 0 GeForce RTX 207... Off | :01:00.0 On | N/A
|
| 0% 37CP817W / 215W |473MiB / 7979MiB | 1% Default
|
| | | N/A
|
+---+--+--+
-
+
+-+
| Processes:
|
| GPU GI CIPID Type Process name GPU Memory
|
|ID ID Usage
|
|=|
|0 N/A N/A 2211 G /usr/lib/xorg/Xorg 35MiB
|
|0 N/A N/A 10496 G /usr/lib/xorg/Xorg106MiB
|
|0 N/A N/A 10626 G /usr/bin/gnome-shell 157MiB
|
|0 N/A N/A 16828 G /usr/lib/xorg/Xorg 35MiB
|
|0 N/A N/A 38063 G ...A= --shared-files 80MiB
|
+-+
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gdm3 3.36.3-0ubuntu0.20.04.4
ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-25-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset
nvidia
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Aug 11 16:37:35 2021
InstallationDate: Installed on 2020-09-26 (318 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1939592
Title:
Login screen (gdm3) is purple blank after switching userA -> userB ->
userA again
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1939592/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939592] [NEW] Login screen (gdm3) is purple blank after switching userA -> userB -> userA again
Public bug reported:
Login screen (gdm3) is purple blank after switching userA -> userB ->
userA again.
Sometimes need to switch 5 times.. but definitely after around 5 times
gdm3 breaks (it shows just a blank purple screen with the cursor).
## Workaround
Ctrl+Alt+F3 (or F4.. F5...) until I get to the user I need to (and unlock the
screensaver there).
OR: switch to the console and run "exec sudo systemctl restart gdm3". ("exec"
is not necessary but highly desirable from the security point of view, so there
won't be a logged in session).
arno@z390-linux:~$ dpkg -l gdm3
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==-===--=
ii gdm3 3.36.3-0ubuntu0.20.04.4 amd64GNOME Display Manager
arno@z390-linux:~$ cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-5.11.0-25-generic
root=UUID=a39515ec-3bed-493b-8286-3904a4aac9de ro quiet splash vt.handoff=7
arno@z390-linux:~$ nvidia-smi
Wed Aug 11 16:42:07 2021
+-+
| NVIDIA-SMI 460.91.03Driver Version: 460.91.03CUDA Version: 11.2 |
|---+--+--+
| GPU NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
| | | MIG M. |
|===+==+==|
| 0 GeForce RTX 207... Off | :01:00.0 On | N/A |
| 0% 37CP817W / 215W |473MiB / 7979MiB | 1% Default |
| | | N/A |
+---+--+--+
+-+
| Processes: |
| GPU GI CIPID Type Process name GPU Memory |
|ID ID Usage |
|=|
|0 N/A N/A 2211 G /usr/lib/xorg/Xorg 35MiB |
|0 N/A N/A 10496 G /usr/lib/xorg/Xorg106MiB |
|0 N/A N/A 10626 G /usr/bin/gnome-shell 157MiB |
|0 N/A N/A 16828 G /usr/lib/xorg/Xorg 35MiB |
|0 N/A N/A 38063 G ...A= --shared-files 80MiB |
+-+
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gdm3 3.36.3-0ubuntu0.20.04.4
ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-25-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset
nvidia
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Aug 11 16:37:35 2021
InstallationDate: Installed on 2020-09-26 (318 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: gdm3 (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1939592
Title:
Login screen (gdm3) is purple blank after switching userA -> userB ->
userA again
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1939592/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904416] [NEW] gpg-agent 2.x poor performance / futex errors
Public bug reported: Hello, after upgrading from Ubuntu 16.04 to Ubuntu 18.04 we've noticed the issues which came along with the gpg v2.x. The gpg-agent produces millions of futex syscall errors during a very short time (a second or two) when it's being loaded either by the SaltStack's salt-master decrypting the pillars (our main use case) or when it is being directly tested with "parallel" tool from moreutils package. ``` $ sudo strace -f -p ... ...Ctrl+C just after couple of seconds while "gpg -d" commands are running in parallel (see below for details) ... % time seconds usecs/call callserrors syscall -- --- --- - - 96.35 2800.145231 305 9194103 2009552 futex 3.63 105.404136 373774 282 pselect6 0.010.431338 102 4246 read 0.000.104701 12 8490 write 0.000.029085 103 283 accept 0.000.016549 58 284 madvise 0.000.012201 22 567 close 0.000.010979 8 1410 getpid 0.000.010405 12 849 access 0.000.006341 22 284 284 wait4 0.000.004350 15 283 openat 0.000.003764 13 283 clone 0.000.002668 9 283 getsockopt 0.000.002568 9 283 fstat 0.000.002564 9 283 set_robust_list 0.000.001941 7 283 lseek -- --- --- - - 100.00 2906.188821 9212496 2009836 total ``` I'll describe the issue and steps to reproduce it. First, prepare the "enc" file: ``` cat /usr/share/doc/base-files/README | gpg -ear "some-4K-RSA-publick-key" > enc ``` Run parallel decryptions using "time" to measure it: ``` time parallel -j 30 sh -c "cat enc | gpg --no-tty -d -q -o /dev/null" -- $(seq 1 3000) ``` Running "gpg -d" (GPG v2.x, with the gpg-agent) in parallel as described above took: - 1minute 18seconds on a big HW; (48 cores, *gpg-agent 2.2.4*-1ubuntu1.2) - 32 seconds on my laptop; (4 cores, *gpg-agent 2.2.19*-3ubuntu2) Running the same commands but with GPG v1.4.20 (no agent): - 9 seconds on a big HW: (40 cores, *gnupg 1.4.20*-1ubuntu3.3) - 21 seconds on a VM; (1 core, *gnupg 1.4.20*-1ubuntu3.3) Note: in order to prevent "command 'PKDECRYPT' failed: Cannot allocate memory " error, the gpg-agent is running either with "--auto- expand-secmem 0x3" flag or with "auto-expand-secmem" in ~/.gnupg /gpg-agent.conf file. Since our use case is to have SaltStack's salt-master decrypt many pillars for hundreds of servers, the Ubuntu 16.04 => 18.04 upgrade severely degrades the SaltStack performance making it almost unusable, i.e. it becomes 10 times slower, requires us figuring workarounds such as increasing "gather_job_timeout" or probably even rolling back to gpg v1.x -- not sure if Ubuntu Bionic fully supports that and won't break though (we haven't tested the gpg 2.x => 1.x downgrade scenario yet -- any insights are highly appreciated!). Any suggestions? Kind regards, Andrey Arapov ** Affects: ubuntu Importance: Undecided Status: New ** Affects: gnupg2 (Ubuntu) Importance: Undecided Status: New ** Also affects: gnupg2 (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/1904416 Title: gpg-agent 2.x poor performance / futex errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1904416/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787712] Re: 16.04 to 18.04 do-release-upgrade fails with "Command terminated with exit status 1"
I've had this issue: # do-release-upgrade -f DistUpgradeViewNonInteractive Checking for a new Ubuntu release Get:1 Upgrade tool signature [819 B] Get:2 Upgrade tool [1240 kB] Fetched 1241 kB in 0s (0 B/s) authenticate 'bionic.tar.gz' against 'bionic.tar.gz.gpg' extracting 'bionic.tar.gz' MarkInstall libpam-cap [ amd64 ] < none -> 1:2.25-1.2 > ( libs ) FU=1 No candidate ver: linux-image-4.4.0-131-generic No candidate ver: linux-image-4.4.0-135-generic No candidate ver: linux-image-extra-4.4.0-131-generic No candidate ver: linux-image-extra-4.4.0-135-generic No candidate ver: linux-signed-image-4.4.0-131-generic No candidate ver: linux-signed-image-4.4.0-135-generic # echo $? 1 Then it worked after I ran: apt-get autoremove Not sure, though, whether that was the issue... I'd rather blame that had something to do with the network/mirror. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787712 Title: 16.04 to 18.04 do-release-upgrade fails with "Command terminated with exit status 1" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1787712/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796193] Re: DistUpgradeViewNonInteractive crashes / requires interaction
Each time I am upgrading Xenial to Bionic I'm getting exactly the same message after few minutes: "*** ntp.conf (Y/I/N/O/D/Z) [default=N] ? " Can this fix get delivered to Ubuntu Xenial? ubuntu-release-upgrader-core 1:16.04.26 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796193 Title: DistUpgradeViewNonInteractive crashes / requires interaction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1796193/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809819] Re: Ubuntu will not unlock non-root LUKS devices when booting without "splash" kernel argument
** Description changed: Ubuntu will not unlock non-root LUKS devices (with the same passphrase) when booting without "splash" kernel argument. Please see the video I've recorded (in VirtualBox) - https://my.nixaid.com/s/epxpwHckGipcB6D + https://my.nixaid.com/s/odG8zEJ2Z75TdHG It feels like systemd-ask-password-plymouth is trying to use the same passphrase to unlock the rest of the LUKS devices, whilst systemd-ask- password-console isn't. Ubuntu 18.04.1 64-bit. /etc/crypttab: sda5_crypt UUID=5ba77327-4680-45d1-ba03-ab1b4fc12abb none luks,discard c4129022-9a34-4eee-9971-0464d92881e0 UUID=c4129022-9a34-4eee-9971-0464d92881e0 none luks luks-b7e017d7-53c4-4503-b376-c62a1d383f17 UUID=b7e017d7-53c4-4503-b376-c62a1d383f17 none luks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809819 Title: Ubuntu will not unlock non-root LUKS devices when booting without "splash" kernel argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1809819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1015819] Re: sb_sasl_generic_pkt_length: received illegal packet length when using Active Directory and ldapsearch and sasl with ssl or tls
Thank you, Johnny Westerlund! At least adding "sasl_secprops minssf=0,maxssf=0" to /etc/openldap/ldap.conf works around the error, so things seem to work for me. Not sure whether it is different now for Michael Osipov. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1015819 Title: sb_sasl_generic_pkt_length: received illegal packet length when using Active Directory and ldapsearch and sasl with ssl or tls To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1015819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1015819] Re: sb_sasl_generic_pkt_length: received illegal packet length when using Active Directory and ldapsearch and sasl with ssl or tls
Exact same error here in 2019. I set Windows Server 2019 up, default AD DS & AD CS (for TLS). Clients tried: Ubuntu 18.04: libsasl2-modules-gssapi-mit:amd64 2.1.27~101-g0780600+dfsg-3ubuntu2 Alpine Edge: cyrus-sasl-gssapiv2-2.1.27-r1 Have anyone tried asking in Cyrus SASL mailing list? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1015819 Title: sb_sasl_generic_pkt_length: received illegal packet length when using Active Directory and ldapsearch and sasl with ssl or tls To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1015819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1483989] Re: apt prints wrong duration after update
Ubuntu 18.04.2 LTS here.. got same # apt update && apt -y upgrade && apt -y dist-upgrade && apt -y autoremove Hit:1 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic InRelease Hit:2 http://archive.ubuntu.com/ubuntu bionic InRelease Hit:3 http://ppa.launchpad.net/nextcloud-devs/client/ubuntu bionic InRelease Get:4 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB] Get:5 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB] Get:6 http://archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB] Get:7 http://archive.ubuntu.com/ubuntu disco InRelease [243 kB] Hit:8 http://archive.ubuntu.com/ubuntu disco-updates InRelease Get:9 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 DEP-11 Metadata [278 kB] Hit:10 http://security.ubuntu.com/ubuntu disco-security InRelease Get:11 http://archive.ubuntu.com/ubuntu bionic-updates/main DEP-11 48x48 Icons [66.6 kB] Get:12 http://archive.ubuntu.com/ubuntu bionic-updates/main DEP-11 64x64 Icons [123 kB] Get:13 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 DEP-11 Metadata [202 kB] Get:14 http://archive.ubuntu.com/ubuntu bionic-updates/universe DEP-11 48x48 Icons [176 kB] Get:15 http://archive.ubuntu.com/ubuntu bionic-updates/universe DEP-11 64x64 Icons [348 kB] Get:16 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse amd64 DEP-11 Metadata [2,468 B] Get:17 http://archive.ubuntu.com/ubuntu bionic-backports/universe amd64 DEP-11 Metadata [7,352 B] Get:18 http://archive.ubuntu.com/ubuntu disco/universe i386 Packages [9,115 kB] Get:19 http://security.ubuntu.com/ubuntu bionic-security/main amd64 DEP-11 Metadata [204 B] Get:20 http://archive.ubuntu.com/ubuntu disco/universe amd64 Packages [9,171 kB] Get:21 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 DEP-11 Metadata [20.8 kB] Get:22 http://security.ubuntu.com/ubuntu bionic-security/universe DEP-11 48x48 Icons [12.2 kB] Get:23 http://security.ubuntu.com/ubuntu bionic-security/universe DEP-11 64x64 Icons [45.2 kB] Get:24 http://security.ubuntu.com/ubuntu bionic-security/multiverse amd64 DEP-11 Metadata [2,464 B] Get:25 http://archive.ubuntu.com/ubuntu disco/universe amd64 DEP-11 Metadata [3,492 kB] Get:26 http://archive.ubuntu.com/ubuntu disco/universe DEP-11 48x48 Icons [2,757 kB] Get:27 http://archive.ubuntu.com/ubuntu disco/universe DEP-11 64x64 Icons [8,459 kB] Fetched 34.8 MB in 213503982334601d 6h 0min 21s (0 B/s) Reading package lists... Done Building dependency tree Reading state information... Done All packages are up to date. ... apt 1.6.8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1483989 Title: apt prints wrong duration after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1483989/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764417] Re: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop
Just got the same, shortly after I logged in, I opened VirtualBox (haven't started the VM yet), then Google Chrome -> went to my mails and ... just got logged out of my session! Ubuntu 18.04; gnome-session-bin 3.28.1-0ubuntu3. Logs: Jan 08 10:21:27 REDACTED gnome-session[4856]: gnome-session-binary[4856]: WARNING: Application 'org.gnome.SettingsDaemon.Keyboard.desktop' failed to register before timeout Jan 08 10:21:27 REDACTED gnome-session[4856]: gnome-session-binary[4856]: CRITICAL: We failed, but the fail whale is dead. Sorry Jan 08 10:21:27 REDACTED gnome-session-binary[4856]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Keyboard.desktop Jan 08 10:21:27 REDACTED gnome-session-binary[4856]: WARNING: Application 'org.gnome.SettingsDaemon.Keyboard.desktop' failed to register before timeout Jan 08 10:21:27 REDACTED gnome-session-binary[4856]: CRITICAL: We failed, but the fail whale is dead. Sorry Jan 08 10:21:27 REDACTED virtualbox.desktop[5400]: ICE default IO error handler doing an exit(), pid = 5400, errno = 11 Jan 08 10:21:27 REDACTED bluetoothd[2624]: Endpoint unregistered: sender=:1.107 path=/MediaEndpoint/A2DPSource Jan 08 10:21:27 REDACTED bluetoothd[2624]: Endpoint unregistered: sender=:1.107 path=/MediaEndpoint/A2DPSink Jan 08 10:21:27 REDACTED kernel: rfkill: input handler enabled Jan 08 10:21:27 REDACTED gnome-shell[4958]: gnome-shell: Fatal IO error 0 (Success) on X server :1. Jan 08 10:21:27 REDACTED polkitd(authority=local)[2802]: Unregistered Authentication Agent for unix-session:3 (system bus name :1.100, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_U Jan 08 10:21:27 REDACTED at-spi-bus-launcher[4934]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":1" Jan 08 10:21:27 REDACTED at-spi-bus-launcher[4934]: after 145 requests (145 known processed) with 0 events remaining. Jan 08 10:21:27 REDACTED gsd-power[5096]: gsd-power: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. Jan 08 10:21:27 REDACTED gsd-wacom[5117]: gsd-wacom: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. Jan 08 10:21:27 REDACTED gsd-xsettings[5118]: gsd-xsettings: Fatal IO error 104 (Connection reset by peer) on X server :1. Jan 08 10:21:27 REDACTED gsd-color[5141]: gsd-color: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. Jan 08 10:21:27 REDACTED gsd-clipboard[5137]: gsd-clipboard: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. Jan 08 10:21:27 REDACTED gsd-media-keys[5149]: gsd-media-keys: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. Jan 08 10:21:27 REDACTED gnome-terminal-[5507]: gnome-terminal-server: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. Jan 08 10:21:27 REDACTED gsd-color[4623]: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/xrandr_BenQ_Corporation_ZOWIE_XL_LCD_BCH00737SL0_arno_1000 Jan 08 10:21:27 REDACTED systemd[4821]: gnome-terminal-server.service: Main process exited, code=exited, status=1/FAILURE Jan 08 10:21:27 REDACTED systemd[4821]: gnome-terminal-server.service: Failed with result 'exit-code'. Jan 08 10:21:28 REDACTED acpid[2618]: client 4841[0:0] has disconnected Jan 08 10:21:28 REDACTED acpid[2618]: client connected from 3353[0:0] Jan 08 10:21:28 REDACTED acpid[2618]: 1 client rule loaded Jan 08 10:21:31 REDACTED gnome-shell[3400]: JS ERROR: TypeError: this._currentWindow is null _setCurrentRect@resource:///org/gnome/shell/ui/keyboard.js:536:13 wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22 _init/<@resource:///org/gnome/shell/ui/keyboard.js:503:13 Jan 08 10:21:31 REDACTED gnome-shell[3400]: JS ERROR: TypeError: this._currentWindow is null _setCurrentRect@resource:///org/gnome/shell/ui/keyboard.js:536:13 wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22 _init/<@resource:///org/gnome/shell/ui/keyboard.js:503:13 Jan 08 10:21:32 REDACTED gnome-shell[3400]: g_array_unref: assertion 'array' failed Jan 08 10:21:32 REDACTED gnome-shell[3400]: g_array_unref: assertion 'array' failed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764417 Title: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1764417/+subscriptions -- ubuntu-bugs
[Bug 1787729] Re: [FAILED] Failed to start Process error reports when automatic reporting is enabled.
This should fix the issue: # EDITOR=vim systemctl edit apport-autoreport.service [Unit] After=whoopsie.service Wants=whoopsie.service Save. Or instead of doing "systemctl edit", you can just drop these 3 lines to the "/etc/systemd/system/apport-autoreport.service.d/override.conf" file and issue "systemctl daemon-reload" command. Tested: systemctl stop whoopsie.service systemctl stop apport-autoreport.service systemctl start apport-autoreport.service This worked for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787729 Title: [FAILED] Failed to start Process error reports when automatic reporting is enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1787729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809819] Re: Ubuntu will not unlock non-root LUKS devices when booting without "splash" kernel argument
** Description changed: - Ubuntu won't unlock all LUKS devices (with the same passphrase) when - booting without "splash" kernel argument. + Ubuntu will not unlock non-root LUKS devices (with the same passphrase) + when booting without "splash" kernel argument. Please see the video I've recorded (in VirtualBox) https://my.nixaid.com/s/epxpwHckGipcB6D It feels like systemd-ask-password-plymouth is trying to use the same passphrase to unlock the rest of the LUKS devices, whilst systemd-ask- password-console isn't. - Ubuntu 18.04.1 64-bit + Ubuntu 18.04.1 64-bit. + + /etc/crypttab: + sda5_crypt UUID=5ba77327-4680-45d1-ba03-ab1b4fc12abb none luks,discard + c4129022-9a34-4eee-9971-0464d92881e0 UUID=c4129022-9a34-4eee-9971-0464d92881e0 none luks + luks-b7e017d7-53c4-4503-b376-c62a1d383f17 UUID=b7e017d7-53c4-4503-b376-c62a1d383f17 none luks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809819 Title: Ubuntu will not unlock non-root LUKS devices when booting without "splash" kernel argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1809819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809819] Re: Ubuntu will not unlock non-root LUKS devices when booting without "splash" kernel argument
** Summary changed: - Ubuntu won't unlock all LUKS devices when booting without "splash" kernel argument + Ubuntu will not unlock non-root LUKS devices when booting without "splash" kernel argument -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809819 Title: Ubuntu will not unlock non-root LUKS devices when booting without "splash" kernel argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1809819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371425] Re: linux-firmware 1.127.5, 1.127.6 causes unstable network connection (likely due to iwlwifi-7260-8.ucode)
** Summary changed: - linux-firmware 1.127.5, 1.127.6 causes instable network connection (likely due to iwlwifi-7260-8.ucode) + linux-firmware 1.127.5, 1.127.6 causes unstable network connection (likely due to iwlwifi-7260-8.ucode) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371425 Title: linux-firmware 1.127.5, 1.127.6 causes unstable network connection (likely due to iwlwifi-7260-8.ucode) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1371425/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809819] [NEW] Ubuntu won't unlock all LUKS devices when booting without "splash" kernel argument
Public bug reported: Ubuntu won't unlock all LUKS devices (with the same passphrase) when booting without "splash" kernel argument. Please see the video I've recorded (in VirtualBox) https://my.nixaid.com/s/epxpwHckGipcB6D It feels like systemd-ask-password-plymouth is trying to use the same passphrase to unlock the rest of the LUKS devices, whilst systemd-ask- password-console isn't. Ubuntu 18.04.1 64-bit ** Affects: 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/1809819 Title: Ubuntu won't unlock all LUKS devices when booting without "splash" kernel argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1809819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667838] Re: zpool export mpu1pool cannot export 'mpu1pool': pool is busy
Ok, this is not limited to ZFS. So that's solely due to namespace isolation. "It's not a bug, it's a feature" (c) :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667838 Title: zpool export mpu1pool cannot export 'mpu1pool': pool is busy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1667838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667838] Re: zpool export mpu1pool cannot export 'mpu1pool': pool is busy
Actually I've just figured why I could not export the pool. One of my docker containers was using the FS, so I could not see it with the "lsof" :/ (mount namespace). I figured when I saw multiple zfs kernel calls with bpftrace :-) I am wondering what would be required for the "zfs unmount -a" to actually fail when its FS is actually used in some other namespace? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667838 Title: zpool export mpu1pool cannot export 'mpu1pool': pool is busy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1667838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667838] Re: zpool export mpu1pool cannot export 'mpu1pool': pool is busy
Hum, just came across the same issue again: # modinfo zfs | head -2 filename: /lib/modules/4.15.0-43-generic/kernel/zfs/zfs/zfs.ko version:0.7.5-1ubuntu16.4 # sync # echo 3 > /proc/sys/vm/drop_caches # zfs unmount -a # swapoff -a # zpool export WD4Gpool cannot export 'WD4Gpool': pool is busy # lsof nor fuser do not show anything related to the WD4Gpool mountpoints. # dmsetup table does not show anything related to ZFS as expected (I do not have the volume datasets) Please re-open this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667838 Title: zpool export mpu1pool cannot export 'mpu1pool': pool is busy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1667838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667838] Re: zpool export mpu1pool cannot export 'mpu1pool': pool is busy
Hi, sorry, I have missed your reply of 2018-07-17. I wanted to highlight that ZFS's export was blocked until "swapoff -a" command was ran. Then, I have mentioned in the OP that the filesystem was unmounted, hence there was no possibility for any file to be opened. And what information was requested in the comment #1? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667838 Title: zpool export mpu1pool cannot export 'mpu1pool': pool is busy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1667838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779871] [NEW] Ubuntu automatically suspends the laptop for the background user when switching back to it from the foreground user.
Public bug reported: To reproduce: 1. Install Ubuntu 18.04 on a laptop 2. Create two user accounts 3. Login to the first account and switch to the second account 4. Disconnect the power plug and work (while on the battery) from one (or the other) account for some time (more than 20 minutes which is default according to the "gsettings get org.gnome.settings-daemon.plugins.power sleep-inactive-battery-timeout" CLI command) 5. When switching a user back to the other account, it will automatically suspend the laptop. Workaround: For each(!) user disable "Automatic suspend" in the Power settings or same with the CLI command: gsettings set org.gnome.settings-daemon.plugins.power sleep-inactive-battery-type 'nothing' Bug? I think it is as having the multiuser session, switching back to the background user it should not immediately force the laptop sleep due to the background user inactivity. How to solve it? gnome-settings-daemon should probably not take into account the inactivity timer (or rather reset it) when there are other foreground users are using Ubuntu. ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: bionic xenial ** Summary changed: - Ubuntu automatically suspends the laptop for the background user when switching back to it from the other user. + Ubuntu automatically suspends the laptop for the background user when switching back to it from the foreground user. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779871 Title: Ubuntu automatically suspends the laptop for the background user when switching back to it from the foreground user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1779871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''
The patch https://code.launchpad.net/~azzar1/ubiquity/+git/ubiquity/+merge/345056 did work for me on my mid-2017 MacBookPro (HW, not VM). Thank you, Andrea! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1751252 Title: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: '' To manage notifications about this bug go to: https://bugs.launchpad.net/cairo/+bug/1751252/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767720] Re: Ubiquity crashed during install of 18.04 with error 'BadAccess (attempt to access private resource denied)'
*** This bug is a duplicate of bug 1751252 *** https://bugs.launchpad.net/bugs/1751252 This patch worked for me https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1751252/comments/37 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767720 Title: Ubiquity crashed during install of 18.04 with error 'BadAccess (attempt to access private resource denied)' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1767720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1603600] Re: NetworkManager ignores pushed openvpn routes
The same issue :-/ Ubuntu 16.04.4 LTS network-manager-openvpn 1.1.93-1ubuntu1.1 network-manager-openvpn-gnome 1.1.93-1ubuntu1.1 I am usually setting: VPN connection settings -> IPv4 Settings -> Routes... -> [x] Use this connection only for resources on its network. So that my default GW is not changed as I need only the VPN routes. Except that with this bug, the VPN routes are not really applied on my system. When running openvpn on its own, everything is working. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1603600 Title: NetworkManager ignores pushed openvpn routes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1603600/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1674838] Re: kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129
Occurred again to me with Linux 4.10.0-20-generic #22-Ubuntu. I attached some logs. ** Attachment added: "linux-4.10.0-20-swapops-slabtop-logs.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674838/+attachment/4873407/+files/linux-4.10.0-20-swapops-slabtop-logs.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1674838 Title: kernel BUG at /build/linux- 7LGLH_/linux-4.10.0/include/linux/swapops.h:129 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1674838] Re: kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129
Hi there. I have encountered the same issue as Dennis Sheil in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674838/comments/18 post. The same way, was using firefox which in turn became unresponsive. The difference is that I am running firefox v53.0 in docker (v17.04.0-ce) using ``--kernel-memory=2G`` to limit it. Then I've increased that limit once it has been reached up to 4G. (``docker update --kernel-memory=4G firefox``). Shortly after that firefox became unresponsive. Please find attached dmesg logs in dmesg-firefox-kernel-swap-bug.txt Linux kernel ver. 4.10.0-19-generic And below are some outputs while I've hit that problem, hopefully some useful info in there: ``` $ df (hanged) root@sony:~# ps auxww |grep Z USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND arno 8866 5.0 0.0 0 0 ?Zl 00:18 70:14 [firefox] arno 8908 10.2 0.0 0 0 ?Z00:18 142:19 [Web Content] arno@sony:~$ mount |grep -i docker rpool/docker on /var/lib/docker type zfs (rw,nodev,noatime,xattr,noacl) rpool/docker on /var/lib/docker/zfs type zfs (rw,nodev,noatime,xattr,noacl) rpool/docker/96f7e9089ac7e330e9868d3ff4530b39364e574a3a32479d7c3ca41f2ad76476 on /var/lib/docker/zfs/graph/96f7e9089ac7e330e9868d3ff4530b39364e574a3a32479d7c3ca41f2ad76476 type zfs (rw,relatime,xattr,noacl) shm on /var/lib/docker/containers/7e253eea4f68195d1085aeb69d7f0428f0106cb414c66a27e03dab27a814b37f/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=2097152k) nsfs on /run/docker/netns/c1194198f0d2 type nsfs (rw) ``` Very strange part is that my SWAP file got reduced itself down to 16MiB: ``` root@sony:~# swapoff -a hanged ... though reduced swap usage down to 16M (and Swap Total !!) arno@sony:~$ free -mh totalusedfree shared buff/cache available Mem: 7.7G1.9G3.5G710M2.3G3.6G Swap: 16M 16M 0B arno@sony:~$ free -b totalusedfree shared buff/cache available Mem: 8270503936 2048671744 3625005056 745644032 2596827136 3855400960 Swap: 1705574417055744 0 ``` Whilst, I should normally have 8GiB swap: ``` root@sony:~# free -mh totalusedfree shared buff/cache available Mem: 7.7G2.0G4.1G473M1.6G4.4G Swap: 8.0G 0B8.0G root@sony:~# free -b totalusedfree shared buff/cache available Mem: 8270512128 2095005696 4448485376 496779264 1727021056 4701388800 Swap:8589930496 0 8589930496 root@sony:~# ``` ** Attachment added: "dmesg-firefox-kernel-swap-bug.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674838/+attachment/4867386/+files/dmesg-firefox-kernel-swap-bug.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1674838 Title: kernel BUG at /build/linux- 7LGLH_/linux-4.10.0/include/linux/swapops.h:129 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682427] Re: ernel BUG at /build/linux-Fk60NP/linux-4.10.0/include/linux/swapops.h:129
*** This bug is a duplicate of bug 1674838 *** https://bugs.launchpad.net/bugs/1674838 Same here... https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674838/comments/53 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682427 Title: ernel BUG at /build/linux- Fk60NP/linux-4.10.0/include/linux/swapops.h:129 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682427/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667838] [NEW] zpool export mpu1pool cannot export 'mpu1pool': pool is busy
Public bug reported: $ lsb_release -rd Description:Ubuntu 16.04.2 LTS Release:16.04 Linux 4.4.0-64-generic $ apt-cache policy zfsutils-linux zfsutils-linux: Installed: 0.6.5.6-0ubuntu15 # modinfo zfs |head filename: /lib/modules/4.4.0-64-generic/kernel/zfs/zfs/zfs.ko version:0.6.5.6-0ubuntu15 I was not able to unmount a ZFS pool: # zpool export mpu1pool cannot export 'mpu1pool': pool is busy The filesystems were unmounted and there was nothing that would be blocking them FS. Neither sync, echo 3 > /proc/sys/vm/drop_caches helped. The only way worked to export a ZFS pool was to turn off the SWAP: # lsof -Pn |grep -i mpu1 lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs Output information may be incomplete. # free -mh totalusedfree shared buff/cache available Mem: 7.7G5.1G502M837M2.1G1.0G Swap: 8.0G428M7.6G # swapoff -a # free -mh totalusedfree shared buff/cache available Mem: 7.7G1.5G4.8G366M1.4G5.2G Swap:0B 0B 0B # zpool export mpu1pool # echo $? 0 # swapon -a It is not obvious that the SWAP has to be freed before one can export ZFS pool. Would it be possible to improve this situation? Kind regards, Andrey Arapov ** Affects: zfs-linux (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/1667838 Title: zpool export mpu1pool cannot export 'mpu1pool': pool is busy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1667838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371425] Re: linux-firmware 1.127.5, 1.127.6 causes instable network connection (likely due to iwlwifi-7260-8.ucode)
Looks like linux-firmware 1.127.11 resolved the problem I had. If the problem will occur again, I'll write about it here. Otherwise please feel free to close this case if I don't update it for one-two weeks :-) Thanks! https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1398171 linux-firmware (1.127.11) trusty; urgency=medium * iwlwifi: update firmware for 3160 / 7260 / 7265 -LP: #1398171 -- Seth Forshee seth.fors...@canonical.com Mon, 01 Dec 2014 12:21:56 -0600 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371425 Title: linux-firmware 1.127.5, 1.127.6 causes instable network connection (likely due to iwlwifi-7260-8.ucode) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1371425/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371425] Re: linux-firmware 1.127.5, 1.127.6 causes instable network connection (likely due to iwlwifi-7260-8.ucode)
*Updating after testing* WiFi on 7260 is still buggy with linux-firmware [1.127.5-1.127.10] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371425 Title: linux-firmware 1.127.5, 1.127.6 causes instable network connection (likely due to iwlwifi-7260-8.ucode) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1371425/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371425] Re: linux-firmware 1.127.5, 1.127.6 causes instable network connection (likely due to iwlwifi-7260-8.ucode)
I guess this bug can be closed. I've installed linux-firmware 1.127.8 and also switched to the Channel 13 (Frequency:2.472 GHz). Not sure which one resolved, but both are definitely made it roll :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371425 Title: linux-firmware 1.127.5, 1.127.6 causes instable network connection (likely due to iwlwifi-7260-8.ucode) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1371425/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371425] Re: linux-firmware 1.127.5, 1.127.6 causes instable network connection (likely due to iwlwifi-7260-8.ucode)
Humm.. hurry to refute my previous comment... I went 1 more meter from the AP and the wireless started to get disconnected every minute almost... :-/ so linux-firmware 1.127.8 is not a solution ... rolling back to 1.127.4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371425 Title: linux-firmware 1.127.5, 1.127.6 causes instable network connection (likely due to iwlwifi-7260-8.ucode) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1371425/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371425] Re: linux-firmware 1.127.5, 1.127.6 causes instable network connection (likely due to iwlwifi-7260-8.ucode)
I've installed the linux-image-3.13.0-37-generic_3.13.0-37.64+iwlltr0001_amd64.deb kernel, however after the reboot I didn't see any wlan0 interface, neither there is a iwlwifi module in this kernel. I've attached the detailed logs to this post. ** Attachment added: report (with full dmesg output) https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1371425/+attachment/4236400/+files/toreport -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371425 Title: linux-firmware 1.127.5, 1.127.6 causes instable network connection (likely due to iwlwifi-7260-8.ucode) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1371425/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371425] Re: linux-firmware 1.127.5, 1.127.6 causes instable network connection (likely due to iwlwifi-7260-8.ucode)
To those who are looking for the working version of firmware, can get it here: http://nixaid.com/linux-firmware_1.127.4_all.deb here: https://web.archive.org/web/20140817233853/http://security.ubuntu.com/ubuntu/pool/main/l/linux-firmware/linux-firmware_1.127.4_all.deb (also tried to attach to this post) md5: d6fa4be684a2aaedecbd6f8383bcbba2 linux-firmware_1.127.4_all.deb sha256: c634800c17cfd6148dda909a20b839b04fb092b86d6f8a939b2f1124b224b20a linux-firmware_1.127.4_all.deb ** Attachment added: linux-firmware_1.127.4_all.deb that works well in my case https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1371425/+attachment/4226849/+files/linux-firmware_1.127.4_all.deb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371425 Title: linux-firmware 1.127.5, 1.127.6 causes instable network connection (likely due to iwlwifi-7260-8.ucode) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1371425/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371425] Re: linux-firmware 1.127.5, 1.127.6 causes instable network connection (likely due to iwlwifi-7260-8.ucode)
@Lathander you are right, 1.127 doesn't work as good as 1.127.4 does, but still better than 1.127.5, .6, .7 ones Even the ping to my AP was without a loss, any other external WAN IP resulted about ~7% packet loss, e.g.: --- google.com ping statistics --- 33 packets transmitted, 30 received, 9% packet loss, time 32067ms rtt min/avg/max/mdev = 27.453/55.770/514.347/90.367 ms So I'll rollback to 1.127.4 that works the best for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371425 Title: linux-firmware 1.127.5, 1.127.6 causes instable network connection (likely due to iwlwifi-7260-8.ucode) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1371425/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371425] Re: linux-firmware 1.127.5, 1.127.6 causes instable network connection (likely due to iwlwifi-7260-8.ucode)
I've just tried newer linux-firmware 1.127.7, and it has the same problem. arno@mint ~ $ ping 10.0.0.138 PING 10.0.0.138 (10.0.0.138) 56(84) bytes of data. 64 bytes from 10.0.0.138: icmp_seq=1 ttl=64 time=2.65 ms 64 bytes from 10.0.0.138: icmp_seq=2 ttl=64 time=2.00 ms 64 bytes from 10.0.0.138: icmp_seq=9 ttl=64 time=1.56 ms ^C --- 10.0.0.138 ping statistics --- 12 packets transmitted, 3 received, 75% packet loss, time 11052ms rtt min/avg/max/mdev = 1.568/2.075/2.652/0.445 ms Packet loss is very high, unstable network connection and lags. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371425 Title: linux-firmware 1.127.5, 1.127.6 causes instable network connection (likely due to iwlwifi-7260-8.ucode) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1371425/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1293569] Re: iwlwifi-7260-8.ucode causes network disconnections problems
Possibly related to the https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/1371425 try to downgrade to 1.127.4 at least or less than 1.127.4, likely the bug was introduced with linux-firmware 1.127.5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1293569 Title: iwlwifi-7260-8.ucode causes network disconnections problems To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1293569/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371425] Re: linux-firmware 1.127.5, 1.127.6 causes instable network connection (likely due to iwlwifi-7260-8.ucode)
Downgraded to 1.127 now and it works without a problem: (pinging my AP) --- 10.0.0.138 ping statistics --- 50 packets transmitted, 50 received, 0% packet loss, time 49079ms rtt min/avg/max/mdev = 1.212/11.625/216.669/41.491 ms So I'm almost certain that the bug was introduced with the linux- firmware 1.127.5 -- https://launchpad.net/ubuntu/+source/linux- firmware/1.127.5 Looks like similar problems (since 1.127.5 and above): https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1293569 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1373552 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371425 Title: linux-firmware 1.127.5, 1.127.6 causes instable network connection (likely due to iwlwifi-7260-8.ucode) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1371425/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1373552] Re: Can't connect to wireless network
Possibly related to the https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/1371425 try to downgrade to 1.127.4 at least or less than 1.127.4, likely the bug was introduced with linux-firmware 1.127.5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1373552 Title: Can't connect to wireless network To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1373552/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
