** 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
** 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
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
k 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 =&
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'
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
** 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
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
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?
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
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:
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
** 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
** 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
** 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
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
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
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"
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':
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
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
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.
*** 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
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
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
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
*** 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.
wap: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)
Importa
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
*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
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
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
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
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
@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%
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:
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,
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-
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,
39 matches
Mail list logo
