Public bug reported:
Steps to reproduce this bug:
- install Ubuntu 24 LTS server
- apt install ubuntu-desktop
- apt install tightvnc-standalone-server
- vncserver -geometry 1024x768 -localhost no
- connect to it and get "Oh no! Something has gone wrong. A problem has
occurred and
OK, fine, all valid points.
I'm not so sure about the "placebo effect", though.
I played the same piece a dozen times on my MIDI keyboard in various
configurations, with the following results:
realtime alsa: xruns 0, 0, 0
realtime jack: xruns 11, 0, 0
lowlatency jack: xruns 25, 5, 5, 6, 8
Admit
I'm not suggesting that Ubuntu Studio should ship with the realtime
kernel as of yet.
I'm suggesting that after "pro enable realtime-kernel", it should be at
the top of the boot priority.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Public bug reported:
Now that Ubuntu has released a realtime kernel, I suggest that Ubuntu
Studio's boot preference should be:
1. realtime
2. lowlatency
3. default
I've been running the realtime kernel for a week, haven't had any
problems with it, and am seeing noticeably fewer xruns in Ardour.
@Christian,
I haven't tried all of your combinations, but when I mount a second disk
using the growpart/e2fsck/resize2fs sequence that you suggest and then
mount it, it grows to 725 MB and then zerofree reports what you
observed:
baccala@osito:~/NPDC/GNS3/bug$ sudo zerofree -v /dev/nbd0p1
3/59636
I like the idea of working this into cloud-init clean.
My use case is that I use cloud-init to initially configure an instance
that will later be manually configured, so I don't want files lying around
that say things like "if you edit this file it will be overwritten on the
next boot" (I forget t
I'm still seeing this behavior on Ubuntu 20.04.4 LTS
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1455967
Title:
NM disables accept_ra for an IPv6 connection, where it should enable
it!
To manag
It also seems to leave build.info in /etc/cloud and doesn't remove that
directory for that reason.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1975744
Title:
purging cloud-init doesn't remove its
Public bug reported:
cloud-init creates /etc/netplan/50-cloud-init.yaml during its network
configuration step.
However, "apt purge cloud-init" leaves this file intact.
I've seen this behavior on Ubuntu 18, 20, and 22.
I can always remove the file manually, but I'm left wondering what other
file
@Christian - my lsblk output looks very similar to yours. In
particular, all device types are reporting discard support; the only
difference is the reported discard sizes.
I would suggest that at the end of your tests you check the disk with
"debugfs -R dump_unused". I'm seeing disk blocks fille
Incidentally, I was able to fix my immediate problem by switching the
disk type to scsi, based on the suggestions given by Christian Ehrhardt.
It's still an open bug that could cause other people some grief. It
sure caused me plenty.
--
You received this bug notification because you are a membe
I've come up with a more minimal test that doesn't require the whole
GNS3 infrastructure.
1. Create a one-line 'meta-data' file:
{instance-id: ubuntu, local-hostname: ubuntu}
2. Create the following 'user-data' file:
#cloud-config
hostname: ubuntu
network:
config: disabled
resize_rootfs: nobl
best guess as to the package
** Package changed: ubuntu => qemu (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1974100
Title:
inode lazy init in a VM fills virtual disk with garbage
To man
Public bug reported:
I encountered this problem using this script to create a GNS3 appliance:
https://github.com/BrentBaccala/NPDC/blob/master/GNS3/ubuntu.py
I'm running a stock gns3-server on Ubuntu 18. I called it like this:
./ubuntu.py -r 20 -s $((1024*1024)) --vnc --boot-script opendesktop
It's Ubuntu 18.04.1 LTS:
LSB Version:core-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch
Distributor ID: Ubuntu
Description:Ubuntu 18.04.1 LTS
Release:18.04
Codename: bionic
Desktop is Unity.
--
You received this bug notification because you are a member of Ubu
Public bug reported:
after changing the name of a VPN (using "Edit Connections..."), the name
change isn't immediately reflected in the "VPN connections" submenu from
the pull down network menu. After five minutes or so (the time it took
to file this bug report), the name change had taken effect.
Public bug reported:
I installed Ubuntu 17.04 server on a Cisco UCS configured to boot from
iSCSI with a static IP addresses. I ran through the standard
installation, configured the network interface with a manually assigned
IP address, logged in to the iSCSI target and configured the disk
partit
Public bug reported:
Installing and then removing initramfs-tools-ubuntu-touch leaves a
configuration file /etc/initramfs/post-update.d/zz-flash-touch-initrd
that calls /usr/sbin/flash-touch-initrd, which was removed when the
package was removed. This causes initramfs-tools to fail during its
pos
I saw this symptom, but for a different reason.
Installing and removing initramfs-tools-ubuntu-touch removes /usr/sbin
/flash-touch-initrd, but leaves the script /etc/initramfs/post-update.d
/zz-flash-touch-initrd, which attempts to call /usr/sbin/flash-touch-
initrd and fails.
My solution was to
19 matches
Mail list logo
