/dev/nvme1n1p1
Couldn't find valid filesystem superblock.
Changing the read of the superblock to Direct I/O solves the issue.
[Testcase]
Start an c5.large instance on AWS, and attach a 60gb gp3 volume for
use as a scratch disk.
Run the following script, courtesy of Krister Johansen
.
[Testcase]
Start an c5.large instance on AWS, and attach a 60gb gp3 volume for
use as a scratch disk.
Run the following script, courtesy of Krister Johansen and his team:
#!/usr/bin/bash
set -euxo pipefail
while true
do
parted /dev/nvme1n1 mklabel gpt mkpart
.
[Testcase]
Start an c5.large instance on AWS, and attach a 60gb gp3 volume for
use as a scratch disk.
Run the following script, courtesy of Krister Johansen and his team:
#!/usr/bin/bash
set -euxo pipefail
while true
do
parted /dev/nvme1n1 mklabel gpt mkpart
valid filesystem superblock.
Changing the read of the superblock to Direct I/O solves the issue.
[Testcase]
Start an c5.large instance on AWS, and attach a 60gb gp3 volume for
use as a scratch disk.
Run the following script, courtesy of Krister Johansen and his team:
#!/usr/bin
/dev/nvme1n1p1
Couldn't find valid filesystem superblock.
Changing the read of the superblock to Direct I/O solves the issue.
[Testcase]
Start an c5.large instance on AWS, and attach a 60gb gp3 volume for
use as a scratch disk.
Run the following script, courtesy of Krister Johansen
, courtesy of Krister Johansen and his team:
#!/usr/bin/bash
set -euxo pipefail
while true
do
parted /dev/nvme1n1 mklabel gpt mkpart primary 2048s 2099200s
sleep .5
mkfs.ext4 /dev/nvme1n1p1
mount -t ext4 /dev/nvme1n1p1 /mnt
Thanks for all the responses. I'm not sure how quickly I'll be able to
get to this either, so I'm hesitant to commit to fixing myself. That
said, if I can get time to send patches before your team gets to fixing
it, I'll do my best.
To answer the question about how frequently we see this: it
Public bug reported:
Hi,
We run ext4 on EBS volumes on EC2. During provisioning, cloud-init will
occasionally report that resize2fs has failed due to a superblock checksum
mismatch. We debugged this internally, and were able to come up with the
following reproducer:
#!/usr/bin/bash
Public bug reported:
This is the strangest bug I've encountered in my 20+ years of linux use.
See a video of the bug at:
https://drive.google.com/file/d/1StYD5kbL5pLRBOc6V-TXuE5DgymTdM0R/view?usp=sharing
Using an external monitor I am editing a Snakefile with vim and syntax
highlighting. Under
The problem is still present in Ubuntu 20.10 :(
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1410618
Title:
MacBook Air 6,2 TRRS Headset Mic Not Working
Status in
Thanks Sebastien, I've posted this bug upstream as
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1057
I've also noted some peculiarities with respect to different clients:
- computer: host/sink/server volume remains constant until source/client goes
to 0, then silent
- Android
Would anyone have an idea as to a workaround, or an idea of how I could
debug this problem?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1880198
Title:
Ubuntu as
Is this bug filed against the correct package?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1880198
Title:
Ubuntu as bluetooth speaker - volume on bluetooth client
I installed 1.22.10-1ubuntu2.1 and turned the hotspot on...
my clients can use the hotspot normally.
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
** Tags removed: verification-done
** Tags added: verification-needed
Public bug reported:
I'm using my 20.04 system as a media center. It's got a bluetooth
adapter plugged into a USB port. I can connect to the system with my
phone and ipad as an A2DP source and play music.
The problem is that the volume on the source device is not respected
When the volume on
The upstream report is here:
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/2f8a4e90
** Bug watch added:
gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues #450
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/450
--
You received this
Oops..
the upstream report is here:
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/450
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
Here are the relevant lines from jounalctrl:
May 21 14:13:03 praxis NetworkManager[1177]: [1590063183.1781] device
(wlan0): Activation: starting connection 'Julep-WiFi'
(7a3e625d-dfea-4423-aad6-a868b942407e)
May 21 14:13:03 praxis NetworkManager[1177]: [1590063183.1796] manager:
Public bug reported:
I upgraded my Ubuntu client to 20.04 and could continue to connect to my
WPA Hotspot running on an Ubuntu server. Upon update of the server to
20.04 I could no longer connect with any of my various client OSs.
After using the updated network-manager from
@seb128 Which package do you want me to report this against?
ubuntu-bug will not let me do it against network-manager because it is "not an
official Ubuntu package".
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
The "always gray" issue is indeed solved by clicking out of the wifi
setting and then back in.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1870359
Title:
My
On the computer with the hotspot, if I make the network open, with no
WPA, then I can connect and use the hotspot with all machines.
If I enable WEP in the hotspot settting (nm-connection-editor), all
machines can still connect and use the hotspot.
If I enbale WPA in the hotspot settings
With the new packages installed I can now connect and use the hotspot as long
as the WPA is disabled.
Thanks for the fix!
As soon as I re-enable the WPA, I can no longer connect with my Ubuntu laptop.
I can, however, connect from Android, Windows 10, and MacOS when the WPA in
enabled.
Is this
Another related bug is that the "Turn On WiFi Hotspots..." menu item is
always gray. The only way I can create or modify a hotspot is using the
nm-connection-editor. Is this a bug I should report elsewhere?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
/usr/sbin/iptables is a symlink to another name with is linked to
another name which is linked to /usr/sbin/xtables-legacy-multi
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
=> which iptables
/usr/sbin/iptables
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1870359
Title:
My machine as Wi-Fi Hotspot broken after upgrade to 20.04
=> iptables --version
iptables v1.8.4 (legacy)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1870359
Title:
My machine as Wi-Fi Hotspot broken after upgrade to
1. I removed the network from the Wi-Fi setting and "Turn On Wi-Fi Hotspot..."
is not grayed out.
2. I opened nm-connection-editor and click the +, then "Wi-Fi", then chose:
- Mode: Hotspot
- Device: wlp3s0
- No security
3. I connect with Ubuntu from another machine. There does appear to be
** Attachment added: "jrnlctl.txt"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1870359/+attachment/5373391/+files/jrnlctl.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
Hello, could someone please help me debug this problem?
This ubuntu 20.04 box is the only viable wifi router in my house!
I'm considering downgrading my system, but would prefer to find the bug.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Public bug reported:
I have a machine with a wired network connection and a wifi card. I've
been using the machine as a wireless router and server in my house. I've
attached a screenshot of the Wi-Fi network settings. It looks as
expected.
Upon updating to 20.04, none of my machines can use the
Gnome-shell will freeze at unexpected times when using the firefox
browser. The symptoms are the same as when watching videos with totem.
I've switched to chrome without having gnome-shell freeze on me.
Is there something particular about the way firefox 59 (Quantum)
interacts with my graphics
Today the fuzzy screen depicted in the attachment appears spontaneously
while using google maps. This time with a block around the pointer,
that continued to move with the pointer.
** Attachment added: "IMG_20180316_172748_697.jpg"
This bug is making it hard to work...
I just had the system freeze up on me again after less than 5 minutes.
This time, when doing ctrl-alt-F3 I got the strange snow-like screen depicted
in the attachement and none of the ctrl-alt terminals or GDM (at ctrl-alt-F1)
showed anything but snow!
More symptoms:
I can kill gnome-shell with "kill -KILL" from a ctrl-alt terminal.
The GDM screen then appears as usual. Logging in again, however, seems to hang
on a blank purple screen.
The GDM screen appears normal but moving the mouse over the top-right
corner to activate the menu results
I'm able to interact with the system normally using the ctrl-alt-F3
terminal, although none of the methods listed in
https://askubuntu.com/questions/455301/how-to-restart-gnome-shell-after-
it-became-unresponsive-freeze/496999 properly restart gnome-shell. It
seems to be related to graphics.
--
I tried using Unity instead of gnome-shell and am experiencing the same
problem. Does this mean it's not a problem with mutter?
What is worse, is that this problems seems to crop up every day or so during
work. In other words, everything will freeze except for the mouse even if I've
never
I'm sorry for dumping the dmesg output into the thread. Here it is in a
file. But it's from after reboot. Does this have the error messages in
it from the previous session? Do I have to get a file from /var/log/ ?
** Attachment added: "dmesg.txt"
Here's dmesg after a freeze of the system when watching a video with
VLC. The strange snow did not show up this time:
=> dmesg
[0.00] Linux version 4.15.0-10-generic (buildd@lgw01-amd64-036) (gcc
version 7.3.0 (Ubuntu 7.3.0-3ubuntu1)) #11-Ubuntu SMP Tue Feb 13 18:23:35 UTC
2018 (Ubuntu
=> lspci -k
00:00.0 Host bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D
DMI2 (rev 01)
Subsystem: Dell Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DMI2
00:01.0 PCI bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D
PCI Express Root Port 1 (rev 01)
I updated to kernel 4.10.1 but still no success. I also tried the
solutions mentioned above, but with no success :(
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
I have the same issue. None of the solutions described above works for
me (suspend/resume, Vart van Deenen's solution, "sudo alsa force-reload"
or anything else). The settings in control center/sound detects that the
headphones are plugged in, but sound comes out of them.
Sound from speakers work
@mulletinc: Thank you!
Comment #18 solved the problem for me.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-datetime in
Ubuntu.
https://bugs.launchpad.net/bugs/1633319
Title:
memory leak in indicator-datetime
*** This bug is a duplicate of bug 1342123 ***
https://bugs.launchpad.net/bugs/1342123
In "Online Accounts" settings, I removed my Google account completely.
This has not fixed the problem with indicator-datetime-service using all
of my memory and swap.
Please remove the duplicate marking.
*** This bug is a duplicate of bug 1342123 ***
https://bugs.launchpad.net/bugs/1342123
I found the correct Setting manager (the other one was for Unity8?) and
have tried to reproduce the behavior described by Jonathan. Disabling
the "Evolution Data Server" entry for my calendar does not fix
This occurs on both my desktop and laptop.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-datetime in
Ubuntu.
https://bugs.launchpad.net/bugs/1633319
Title:
memory leak in indicator-datetime
Status in
@brierjon: I don't see the same thing that you do in 16.10 (see attachment).
I am missing a Google account setting.
** Attachment added: "Scronlineaccounts.png"
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1633319/+attachment/4762383/+files/Scronlineaccounts.png
--
This is urgent, as it renders and upgraded system completely useless.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-datetime in
Ubuntu.
https://bugs.launchpad.net/bugs/1633319
Title:
memory leak in
*** This bug is a duplicate of bug 1633319 ***
https://bugs.launchpad.net/bugs/1633319
Public bug reported:
Upon upgrading to 16.10, yakkety yak, I cannot load Unity because the
indicator-datetime-service devours memory at an incredible pace before
being automatically killed, and restarting
gedit DOES have the issue.
Gimp, Inscape, LibreOffice do NOT.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1596513
Title:
"save to" dialogue no longer has recent
The use case I point to is actually the Firefox "save to" dialogue.
Now that I look at it...
this seems to be a problem with firefox. The other applications do include
the recent files dialogue.
Sorry for the false alarm.
** Package changed: gtk+3.0 (Ubuntu) => ubuntu
** Changed in: ubuntu
Public bug reported:
1. Plug in a wireless keyboard with a built-in trackpad (I have the logitech
K400 Plus).
2. open dconf-editor
3. go to org > gnome > settings-daemon > peripherals
4. see that there is no "touchpad" entry
My laptop has a touchpad entry that allows me to adjust
Public bug reported:
1. Setup multiple workspaces.
2. Create a window and move it so that the right side of the window is at the
right edge of the workspace (but not past the right edge).
3. Move right one workspace.
See that you can grab the window from the workspace to the left and
resize it
This seems to work all the time when the computer is unplugged...
when plugged in, it seems to work most of the time.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pm-utils in Ubuntu.
The workaround in #4 works for me as long as I do (as root):
echo medium_power /sys/class/scsi_host/host0/link_power_management_policy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pm-utils in Ubuntu.
Careful though, this does not work every time... just most of the time.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pm-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1311724
Title:
Macbook Air resumes immidiately
Public bug reported:
open firefox using the hotkey set for the web browser in the keyboard
setting.
see that the window opens but it is not on top.
one must click on it to use it.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.3+14.04.20140826-0ubuntu1
ProcVersionSignature:
Public bug reported:
1. Go to a desktop with now windows open.
2. Press altspace.
3. See that the window accessibility menu opens.
Clicking on entries in this menu causes problems with Unity.
For example if you click on Move Workspace Left, then many graphical issues
arrise.
ProblemType: Bug
58 matches
Mail list logo
