I have been having this issue for months and I have now reached the stage where I may have to give up on Ubuntu. I can only log in via 'Recovery' and the resulting speed means that it's virtually useless to do so. I am 99.99% certain the issue arises from some type of conflict between my Radeon RX 5500/5500M graphics card and 22.04.05. I have tried every solution on the net that I can find (loading the recommended AMD drivers, updating, upgrading, editing GRUB four different ways (nomodeset, etc), reinstalling desktop, fixing firmware, Boot Repair, etc, etc.). Sometimes I can sort the issue but then every time I try to log back in - same issue. Since Xmas I have just been leaving the computer on after I last managed to sort the problem - no issues, the computer ran like silk. Then I got a message that updates were needed so I did that and rebooted, the problem returned. I know the machine can work properly so I really doubt it's a hardware issue and I don't understand why it reverts when I turn the computer off. I took careful notes the last time I managed a fix, none of that now works.

Grub is this:

GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=menu
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR="lsb_release -i -s 2\> /dev/null || echo Debian"
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash amdgpu.dc=0"
GRUB_CMDLINE_LINUX=""

The odd thing is that when I run journalctl -b I get notifications that 'nomodeset' is preventing certain lines loading but as you can see I am not using it in GRUB. Just running "quiet splash" does not work.

Happy to list the output of any log required on demand.

sudo dmesg | grep -i amdgpu gives:

[    8.385411] [drm] amdgpu kernel modesetting enabled.
[    8.385982] [drm] amdgpu version: 6.16.13
[    8.387222] amdgpu: Virtual CRAT table created for CPU
[    8.388841] amdgpu: Topology: Add CPU node
[    8.395085] amdgpu: probe of 0000:03:00.0 failed with error -22

sudo lshw -c video gives:

*-display                 
       description: VGA compatible controller
       product: Navi 14 [Radeon RX 5500/5500M / Pro 5500M]
       vendor: Advanced Micro Devices, Inc. [AMD/ATI]
       physical id: 0
       bus info: pci@0000:03:00.0
       logical name: /dev/fb0
       version: c5
       width: 64 bits
       clock: 33MHz
       capabilities: pm pciexpress msi vga_controller bus_master cap_list fb
       configuration: depth=32 latency=0 resolution=1024,768
       resources: memory:c0000000-cfffffff memory:d0000000-d01fffff ioport:e000(size=256) memory:fe400000-fe47ffff memory:c0000-dffff

Does anyone have an inkling of a suggestion as to what I can do??

OS: Ubuntu 24.04.3 LTS Kernel: 6.14.0-1015-oracle Container Runtime: cri-o://1.33.2 Platform: Oracle Container Engine for Kubernetes (OKE) CNI: OCI VCN-Native CNI

Description: We are running a Kubernetes cluster on OCI (OKE). We are observing a critical issue where a kernel OOM kill event on a worker node triggers a restart of the systemd-networkd service.

When systemd-networkd restarts, it appears to flush existing IP rules and routes managed by the OCI CNI plugin. Consequently, coredns and other pods on the affected node lose network connectivity (specifically DNS resolution failures) until the node is rebooted or the CNI is manually re-triggered.

The Sequence of Events:

1. The OOM Killer terminates processes in kubepods.slice.
2. Immediately following the kill (within milliseconds), systemd initiates a stop/start cycle for systemd-networkd.
3. The network service restart wipes the IP rules created by the CNI for the Pod networking.
4. CoreDNS and other pods on the node become unreachable or cannot resolve DNS.

Relevant Logs (/var/log/syslog):

1. The OOM Event kills the slice:

2026-01-30T06:38:49.280234+00:00 oke-node systemd[1]: kubepods-burstable.slice: A process of this unit has been killed by the OOM killer.
2026-01-30T06:38:49.281318+00:00 oke-node systemd[1]: kubepods.slice: A process of this unit has been killed by the OOM killer.

2. systemd immediately stops systemd-networkd (less than 100ms later):

2026-01-30T06:38:49.369548+00:00 oke-node kernel: systemd[1]: Stopping systemd-networkd.service - Network Configuration...
2026-01-30T06:38:49.421547+00:00 oke-node kernel: systemd[1]: systemd-networkd.service: Deactivated successfully.

3. systemd-networkd starts back up and re-enumerates links (resetting state):

2026-01-30T06:38:49.562636+00:00 oke-node systemd[1]: Starting systemd-networkd.service - Network Configuration...
2026-01-30T06:38:49.703047+00:00 oke-node systemd-networkd[181536]: ens3: Gained carrier
...
2026-01-30T06:38:49.718792+00:00 oke-node systemd[1]: Starting systemd-networkd-wait-online.service - Wait for Network to be Configured...

Questions:

1. Why does an OOM kill within kubepods.slice trigger a restart of systemd-networkd on Ubuntu 24.04? The network service does not appear to be the process being OOM killed.
2. Is there a systemd configuration (e.g., OnFailure or slice dependency) specific to the Oracle Kernel (6.14.0-1015-oracle) or Ubuntu cloud images that links the health of the kubepods slice to the network daemon?
3. How can we prevent systemd-networkd from restarting during high-memory events to preserve the CNI-configured IP rules?

Steps taken so far:

• Analyzed syslog to confirm systemd-networkd is not crashing, but being gracefully stopped and started by PID 1 immediately following the OOM event.

Any insights into this dependency chain or systemd behavior would be appreciated.

I am using Ubuntu Desktop 24.04 with x11 with NVIDIA proprietary driver 590. When I suspend the screen and come back after some time and try to get back to the screen then I don't see the screen. It's fully black and I can't do anything. I have to manually turn the laptop off with the power button and start it again. I am using an ASUS TUF A15 gaming laptop with mux switch, NVIDIA RTX 3050 graphics card, Ryzen 7 6800h CPU, 16 GB RAM and 1 TB SSD. Does anyone know how to fix this??

Not sure if this or a mathematica-focussed forum is the right place for this, but I suspect my issue is something with my ubuntu setup, so I am hoping someone here will have some ideas.

I am trying to install Mathematica from the official installer Wolfram_14.3.0_LIN_Bndl.sh, but it's being strangely annoying.

When I try running it, with any of ./Wolfram_14.3.0_LIN_Bndl.sh, sudo ./Wolfram_14.3.0_LIN_Bndl.sh, bash Wolfram_14.3.0_LIN_Bndl.sh or sudo bash Wolfram_14.3.0_LIN_Bndl.sh , I receive output of the form

Wolfram Mathematica 14.3.0 for LINUX Installer Archive

Verifying archive integrity. 
Error in MD5 checksums: 7b75ed1e8117f0a81eea3b41358b9e28 is different from b78ec7c79750834b95d15731c9903fa4

However, the wrong checksum is computed each time, e.g. the 7b75ed1e8117f0a81eea3b41358b9e28 will become f393c094e26d8506c0cca1bc8addb413 or something else each time I run it.

I downloaded the script from wolfram's website, so I know it is the correct/official one. I do not have any good guesses for why the wrong checksum is being computed or why it is different every time. I tried bypassing this check by manually editing the relevant function in the shell script, but then the install fails at the next step with output

Wolfram Mathematica 14.3.0 for LINUX Installer Archive

Verifying archive integrity. 
Extracting installer. ........Extraction failed. No space left on .625963
.Removing temporary files.

I am also confused by this. It seems some tar command is failing under the hood, but I do not know why. It certainly is not because of a lack of space; I have hundreds of gigabytes free, and while Mathematica is pretty big, it's not that big.

At this point, I am very confused about what is causing these issues, so I thought I would turn to the interest for help. Does anyone here have any suggestions?

Some extra considerations

• I know the installation script itself is fine. I pulled out an old laptop and tried running it on there, and it worked with no issue. If it matters, my current computer is running Ubuntu 25.10, but the old one is running 25.04.

• The md5sum function on my (current) laptop also appears to being working correctly. I tested this via echo -n "The quick brown fox jumps over the lazy dog" | md5sum and comparing the output to this example given on Wikipedia.

• If it matters, my computer has two physical SSDs in it. One is basically a huge storage partition and is where the install script is downloaded. The other has my Linux partition (as well as a separate Windows partition for emergencies). I doubt this matters for anything, but figured I'd mention it just in case.

Let me know if I can provide any more information about my setup/computer, if I should provide any snippets of the installation shell script, or if I can share anything else that might be helpful. Also let me know if there is a better place to ask for help with this. Thanks.

I have Kubuntu 25.10 on a laptop with Intel internal graphics and an Nvidia 4060 laptop GPU. I installed Nvidia drivers (590-open) and now my boot gets stuck at Begin: Running /scripts/init-premount. When I Ctrl+Alt+F3 I can log in from a tty and run startplasma-wayland and it will load into the GUI and everything works, but if I reboot I get stuck at Begin: Running /scripts/init-premount. I changed the sddm settings to auto-login and I can boot with no issues from a shutdown, but then my computer is not locked with a password. Do you have any ideas?

Running Ubuntu 24.04 on a Bosgame Ecolite mini-PC, all updates applied.

When Firefox starts up, numerous messages of this form begin appearing in syslog:

gnome-shell [93321] Failed to make thread 'KMS thread' realtime scheduled: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.RealtimeKit1" does not exist

Web searches turn up only a handful of references to this error, all of which involved bug fixes that have since been incorporated.

Here's a full series where it first turns up in syslog:

2026-02-01T09:29:49.499526-06:00 MiniPC gnome-shell[93321]: Failed to make thread 'KMS thread' realtime scheduled: Message recipient disconnected from message bus without replying
2026-02-01T09:29:57.870019-06:00 MiniPC kernel: audit: type=1107 audit(1769959797.868:183): pid=924 uid=102 auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call"  bus="system" path="/org/freedesktop/RealtimeKit1" interface="org.freedesktop.DBus.Properties" member="Get" mask="send" name="org.freedesktop.RealtimeKit1" pid=134810 label="snap.firefox.firefox"
2026-02-01T09:29:57.870034-06:00 MiniPC kernel:  exe="/usr/bin/dbus-daemon" sauid=102 hostname=? addr=? terminal=?'
2026-02-01T09:29:59.561466-06:00 MiniPC gnome-shell[93321]: Failed to make thread 'KMS thread' realtime scheduled: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.RealtimeKit1" does not exist
2026-02-01T09:30:00.512017-06:00 MiniPC gnome-shell[93321]: Failed to make thread 'KMS thread' realtime scheduled: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.RealtimeKit1" does not exist
2026-02-01T09:30:01.225646-06:00 MiniPC CRON[134866]: (root) CMD ([ -x /etc/init.d/anacron ] && if [ ! -d /run/systemd/system ]; then /usr/sbin/invoke-rc.d anacron start >/dev/null; fi)
2026-02-01T09:30:10.594545-06:00 MiniPC gnome-shell[93321]: Failed to make thread 'KMS thread' realtime scheduled: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.RealtimeKit1" does not exist
2026-02-01T09:30:33.611440-06:00 MiniPC gnome-shell[93321]: message repeated 5 times: [ Failed to make thread 'KMS thread' realtime scheduled: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.RealtimeKit1" does not exist]

I dunno, maybe something to do with that apparmor DENIED message?

Maybe it's of no real effect, but I'm also dealing with some memory leak issues, and cleaning up the log and unnecessary errors can't hurt.

I have a laptop running Ubuntu 25.10. I'd like to make the following setup with three screens: The build-in laptop screen, a projector, connected via HDMI, and a portable USB-C monitor. I want to mirror the view on the laptop screen to the projector, and have an independent view on the USB-C monitor. The system settings as such don't allow me to do this. It's either three entirely separate views or the same view across all three screens. I have looked at this question, which is exactly what I want, but the solution there doesn't work for me.

I have tried the following gdctl command, without success:

$ gdctl set --logical-monitor --primary --monitor DP-3 --logical-monitor --monitor eDP-1 --monitor HDMI-1 --right-of DP-3
Failed to create configuration: Different monitor resolutions within the same logical monitor

Both eDP-1 (built-in laptop screen) and HDMI-1 (projector) are set to 1920x1080 at 60 Hz, so the error message doesn't make sense to me. Here's the output from gdctl show which hopefully helps to shed some light on this issue:

$ gdctl show
Monitors:
├──Monitor DP-3 (RTK 16")
│  ├──Vendor: RTK
│  ├──Product: SF16
│  ├──Serial: demoset-1
│  ├──Current mode
│  │   └──1920x1200@60.000
│  └──Preferences
│      └──Backlight: None
├──Monitor HDMI-1 (Acer Technologies)
│  ├──Vendor: ACR
│  ├──Product: Acer 4K PJ
│  ├──Serial: JTA110018400
│  ├──Current mode
│  │   └──1920x1080@60.000
│  └──Preferences
│      └──Backlight: None
└──Monitor eDP-1 (Built-in display)
   ├──Vendor: BOE
   ├──Product: 0x09dc
   ├──Serial: 0x00000000
   ├──Current mode
   │   └──1920x1080@60.001
   └──Preferences
       └──Backlight:
           ├──active ⇒  True
           ├──min ⇒  193
           ├──max ⇒  19393
           └──value ⇒  9792

Logical monitors:
├──Logical monitor #1
│  ├──Position: (1920, 0)
│  ├──Scale: 1.0
│  ├──Transform: normal
│  ├──Primary: yes
│  └──Monitors: (1)
│      └──eDP-1 (Built-in display)
├──Logical monitor #2
│  ├──Position: (0, 0)
│  ├──Scale: 1.0
│  ├──Transform: normal
│  ├──Primary: no
│  └──Monitors: (1)
│      └──DP-3 (RTK 16")
└──Logical monitor #3
   ├──Position: (3840, 0)
   ├──Scale: 1.0
   ├──Transform: normal
   ├──Primary: no
   └──Monitors: (1)
       └──HDMI-1 (Acer Technologies)

Can anyone suggest why gdctl set doesn't work?

I recently updated VirtualBox from version 7.2.4 to 7.2.6. I have several VMs, including an Ubuntu VM for which I decided to update the corresponding Virtual Guest Additions (VGA). Once I logged in I ran the executable to install the VGA, but I noticed something different during the process compared to previous VGA updates: it started downloading dependencies to install some modules (Unfortunately I don't have any further information about this.). After restarting the system, it didn't display the login screen. Instead it showed a Bash shell.

If I restart the virtual machine again, the GRUB menu appears. I select the first entry, and to see the system boot process I press the Esc key. I see that the boot process starts to take quite a while, and shortly after, several repetitive messages appear, like this one (finally, the Bash shell prompt appears again):

Feb 01 16:48:25 nokia-cts kernel: ata3.00: ATA-6: VBOX HARDDISK, 1.0, max UDMA/133
Feb 01 16:48:25 nokia-cts kernel: ata3.00: 209715200 sectors, multi 128: LBA48 MCQ (depth 32)
Feb 01 16:48:25 nokia-cts kernel: ata3.00: configured for UDMA/133
Feb 01 16:48:25 nokia-cts kernel: scsi 2:0:0:0: Direct-Access     ATA      VBOX HARDDISK    1.0  PQ: 0 ANSI: 5
Feb 01 16:48:25 nokia-cts kernel: sd 2:0:0:0: [sda] 209715200 512-byte logical blocks: (107 GB/100 GiB)
Feb 01 16:48:25 nokia-cts kernel: sd 2:0:0:0: Attached scsi generic sg1 type 0
Feb 01 16:48:25 nokia-cts kernel: sd 2:0:0:0: [sda] Write Protect is off
Feb 01 16:48:25 nokia-cts kernel: sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
Feb 01 16:48:25 nokia-cts kernel: sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 01 16:48:25 nokia-cts kernel: sd 2:0:0:0: [sda] Preferred minimum I/O size 512 bytes
Feb 01 16:48:25 nokia-cts kernel:  sda: sda1 sda2 sda3
Feb 01 16:48:25 nokia-cts kernel: sd 2:0:0:0: [sda] Attached SCSI disk
Feb 01 16:48:26 nokia-cts systemd[1]: Mounting sys-kernel-config.mount - Kernel Configuration File System...
Feb 01 16:48:26 nokia-cts systemd[1]: Mounted sys-kernel-config.mount - Kernel Configuration File System.
Feb 01 16:48:26 nokia-cts systemd[1]: Reached target sysinit.target - System Initialization.
Feb 01 16:48:26 nokia-cts systemd[1]: Reached target basic.target - Basic System.
Feb 01 16:48:26 nokia-cts systemd[1]: System is tainted: unmerged-bin
Feb 01 16:50:37 nokia-cts dracut-initqueue[309]: Warning: dracut-initqueue: timeout, still waiting for following initqueue hooks:
Feb 01 16:50:37 nokia-cts dracut-initqueue[309]: Warning: /lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2fmapper\x2fvgubuntu-root.sh: "if ! grep -q A>
Feb 01 16:50:37 nokia-cts dracut-initqueue[309]:          [ -e "/dev/mapper/vgubuntu-root" ]
Feb 01 16:50:37 nokia-cts dracut-initqueue[309]: fi"
Feb 01 16:50:37 nokia-cts dracut-initqueue[309]: Warning: dracut-initqueue: starting timeout scripts
Feb 01 16:50:37 nokia-cts dracut-initqueue[309]: Warning: dracut-initqueue: timeout, still waiting for following initqueue hooks:
Feb 01 16:50:37 nokia-cts dracut-initqueue[309]: Warning: /lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2fmapper\x2fvgubuntu-root.sh: "if ! grep -q A>
Feb 01 16:50:37 nokia-cts dracut-initqueue[309]:          [ -e "/dev/mapper/vgubuntu-root" ]
Feb 01 16:50:37 nokia-cts dracut-initqueue[309]: fi"
Feb 01 16:50:37 nokia-cts dracut-initqueue[309]: Warning: dracut-initqueue: starting timeout scripts
Feb 01 16:50:38 nokia-cts dracut-initqueue[309]: Warning: dracut-initqueue: timeout, still waiting for following initqueue hooks:
Feb 01 16:50:38 nokia-cts dracut-initqueue[309]: Warning: /lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2fmapper\x2fvgubuntu-root.sh: "if ! grep -q A>
Feb 01 16:50:38 nokia-cts dracut-initqueue[309]:          [ -e "/dev/mapper/vgubuntu-root" ]
Feb 01 16:50:38 nokia-cts dracut-initqueue[309]: fi"
Feb 01 16:50:38 nokia-cts dracut-initqueue[309]: Warning: dracut-initqueue: starting timeout scripts
Feb 01 16:50:38 nokia-cts dracut-initqueue[309]: Warning: dracut-initqueue: timeout, still waiting for following initqueue hooks:
Feb 01 16:50:38 nokia-cts dracut-initqueue[309]: Warning: /lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2fmapper\x2fvgubuntu-root.sh: "if ! grep -q A>
Feb 01 16:50:38 nokia-cts dracut-initqueue[309]:          [ -e "/dev/mapper/vgubuntu-root" ]
Feb 01 16:50:38 nokia-cts dracut-initqueue[309]: fi"
Feb 01 16:50:38 nokia-cts dracut-initqueue[309]: Warning: dracut-initqueue: starting timeout scripts
Feb 01 16:50:39 nokia-cts dracut-initqueue[309]: Warning: dracut-initqueue: timeout, still waiting for following initqueue hooks:
Feb 01 16:50:39 nokia-cts dracut-initqueue[309]: Warning: /lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2fmapper\x2fvgubuntu-root.sh: "if ! grep -q A>
Feb 01 16:50:39 nokia-cts dracut-initqueue[309]:          [ -e "/dev/mapper/vgubuntu-root" ]
Feb 01 16:50:39 nokia-cts dracut-initqueue[309]: fi"
Feb 01 16:50:39 nokia-cts dracut-initqueue[309]: Warning: dracut-initqueue: starting timeout scripts
Feb 01 16:50:39 nokia-cts dracut-initqueue[309]: Warning: dracut-initqueue: timeout, still waiting for following initqueue hooks:
Feb 01 16:50:39 nokia-cts dracut-initqueue[309]: Warning: /lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2fmapper\x2fvgubuntu-root.sh: "if ! grep -q A>
Feb 01 16:50:39 nokia-cts dracut-initqueue[309]:          [ -e "/dev/mapper/vgubuntu-root" ]
Feb 01 16:50:39 nokia-cts dracut-initqueue[309]: fi"
Feb 01 16:50:39 nokia-cts dracut-initqueue[309]: Warning: dracut-initqueue: starting timeout scripts
Feb 01 16:50:40 nokia-cts dracut-initqueue[309]: Warning: dracut-initqueue: timeout, still waiting for following initqueue hooks:
Feb 01 16:50:40 nokia-cts dracut-initqueue[309]: Warning: /lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2fmapper\x2fvgubuntu-root.sh: "if ! grep -q A>

Given that my VM is in this state, is there any procedure for the system to recover?

Feeling pretty stupid right now.

I went through the upgrade procedure to go from 22.04 to 24.04. I haven't lost any data and my machine is functional (thank goodness, since it's what I use for the day job).

But while enabling and upgrading third-party software I noted that sources.list was still using "jammy" instead of "noble".

Long story short, I got into the situation where I cannot upgrade anything because this happens.

1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up linux-image-6.8.0-94-generic (6.8.0-94.96) ...
Processing triggers for linux-image-6.8.0-94-generic (6.8.0-94.96) ...
/etc/kernel/postinst.d/dkms:
 * dkms: running auto installation service for kernel 6.8.0-94-generic
Sign command: /usr/bin/kmodsign
Signing key: /var/lib/shim-signed/mok/MOK.priv
Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der
Building module:
Cleaning build area...
make -j8 KERNELRELEASE=6.8.0-94-generic -C /lib/modules/6.8.0-94-generic/build M
=/var/lib/dkms/virtualbox-guest/6.1.50/build.....(bad exit status: 2)
ERROR (dkms apport): binary package for virtualbox-guest: 6.1.50 not found
Error! Bad return status for module build on kernel: 6.8.0-94-generic (x86_64)
Consult /var/lib/dkms/virtualbox-guest/6.1.50/build/make.log for more informatio
n.
dkms autoinstall on 6.8.0-94-generic/x86_64 succeeded for clevo-keyboard
dkms autoinstall on 6.8.0-94-generic/x86_64 failed for virtualbox-guest(10)
Error! One or more modules failed to install during autoinstall.Refer to previous errors for more information.
 * dkms: autoinstall for kernel 6.8.0-94-generic
   ...fail!
run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
dpkg: error processing package linux-image-6.8.0-94-generic (--configure):
 installed linux-image-6.8.0-94-generic package post-installation script subproc
ess returned error exit status 11
Errors were encountered while processing:
 linux-image-6.8.0-94-generic
E: Sub-process /usr/bin/dpkg returned an error code (1)

I was trying to follow various "fixes" from various articles but it's just got worse.

Any help in digging myself out of this mess would be appreciated.

EDIT 1: --- /etc/apt/sources.list (comments removed)

After the upgrade these were all still pointing at "jammy", I tried just changing them all and ran into errors, so (after other changes) started to edit them one by one, and this is as far as I got.

# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
# newer versions of the distribution.
deb http://gb.archive.ubuntu.com/ubuntu/ noble main restricted
deb http://gb.archive.ubuntu.com/ubuntu/ noble-updates main restricted
deb http://gb.archive.ubuntu.com/ubuntu/ jammy universe
deb http://gb.archive.ubuntu.com/ubuntu/ jammy-updates universe
deb http://gb.archive.ubuntu.com/ubuntu/ jammy multiverse
deb http://gb.archive.ubuntu.com/ubuntu/ jammy-updates multiverse
deb http://gb.archive.ubuntu.com/ubuntu/ jammy-backports main restricted universe multiverse
deb http://security.ubuntu.com/ubuntu jammy-security main restricted
deb http://security.ubuntu.com/ubuntu jammy-security universe
deb http://security.ubuntu.com/ubuntu jammy-security multiverse

EDIT 2: --- /etc/apt/sources.list.d/

The *.list files and what's in them...

-rw-r--r-- 1 root root  130 Feb  1 13:32 ansible-ubuntu-ansible-focal.list
deb http://ppa.launchpad.net/ansible/ansible/ubuntu noble main 

-rw-r--r-- 1 root root  134 Feb  1 14:44 dropbox.list
deb [arch=i386,amd64] http://linux.dropbox.com/ubuntu noble main

-rw-r--r-- 1 root root  118 Feb  1 13:42 expressvpn.list
## Fully commented out

-rw-r--r-- 1 root root  190 Feb  1 09:43 google-chrome.list
deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main

-rw-r--r-- 1 root root  225 Feb  1 13:44 hashicorp.list
deb [signed-by=/usr/share/keyrings/hashicorp-archive-keyring.gpg] https://apt.releases.hashicorp.com noble main

-rw-r--r-- 1 root root  136 Feb  1 13:53 junocomp-ubuntu-juno-apps-focal.list
deb http://ppa.launchpad.net/junocomp/juno-apps/ubuntu noble main

-rw-r--r-- 1 root root  120 Feb  1 14:10 ondrej-ubuntu-php-focal.list
deb http://ppa.launchpad.net/ondrej/php/ubuntu noble main

-rw-r--r-- 1 root root  163 Feb  1 15:49 virtualbox.list
deb [arch=amd64] http://download.virtualbox.org/virtualbox/debian jammy contrib 
#deb [arch=amd64] http://download.virtualbox.org/virtualbox/debian noble contrib

(I had tried upgrading virtualbox but I think that's where it started running into issues.)

Replaced Gnome with Enlightenment on 24.04, and got past the boot logo, even though it took a while where the throbber stopped spinning but my cursor was on screen, but this doesn't look anything like a desktop at all, so I shut it down.

Took a video and turned it into a gif with ffmpeg:

journalctl is reporting some red logs, when looking things up, feels like a similar report to this Bug 206225 - nouveau: Screen distortion and lockup on resume, given that I'm seeing well, distortion and the logs are mentioning nouveau, TRAP_MP_EXEC, and INVALID_OPCODE.

Maybe I also deleted the drivers for my NVIDIA GT 220 via apt autoremove?? Because I can't find any nvidia-driver entries in my installed packages. But neither can I install them via apt?

To give a quick explanation: A friend helped me rent a contabo server to which I connect using MobaXterm RDP and that session is running via Ubuntu LTS OS (Hopefully it makes sense, since I am not super tech savvy).

I don't run anything else other than a modded minecraft server. Problem is every day at around 10pm Central European Time (don't believe it's exact same time) the terminal which was running the server just shuts down, tried using a screen for this purpose, but that also turned up dead after this time. After using "uptime" turns out the server itself is not going offline. I also contacted Contabo customer support just in case and they just migrated my server and thats all nothing has been fixed.

Would love any information about how I could fix this issue or be directed to a place more appropriate for this question. Be it troubleshooting or direct fixes any extra information gained on what causes this and potential fixes would be awesome. Thank you for your time.

My laptop isn't booting. After what was probably a power failure directly after booting into my Ubuntu (Budgie) desktop, now BusyBox shell and (initramfs) are showing up right after decrypting drive (it's an encrypted system). I tried some recommendations I found online to fix this (typing exit, then run fsck on the mentioned filesys), but it's not working.

After typing "exit" I get the message that my root partition needs a manual fsck.

...
(Initramfs) Exit
/dev/mapper/vgubuntu--budgie-root: recovering journal
/dev/mapper/vgubuntu--budgie-root: Superblock needs_recovery flag is clear, but journal has data.
/dev/mapper/vgubuntu--budgie-root:Run journal anyway
/dev/mapper/vgubuntu--budgie-root: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.       (i.e., without -a or -p options)
fsck exited with status code 4
The root file system /dev/mapper/vgubuntu--budgie-root requires a manual fsck

When I try, it doesn't work (as in: not trying to fix-run) but gives error after zero time.

...
(Initramfs) fsck /dev/mapper/vgubuntu--budgie-root
dev/mapper/vgubuntu--budgie-root: recovering journal
Superblock needs_recovery flag is clear, but journal has data.
Run journal anyway<y>? Yes
fsck.ext4 unable to set Superblock flags on /dev/mapper/vgubuntu--budgie-root

dev/mapper/vgubuntu--budgie-root: **** warning: filesystem still has errors ****

Anyone has a solid idea what's the problem here and how to fix it?

Edit 1&2: added the complete code lines & description for clarity.

Edit 3: When

sudo fsck -b 32768 -y /dev/mapper/vgubuntu--budgie-root

(or any other superblock previously identified with mke2fs -n) it gives back

Superblock needs_recovery flag is clear, but journal has data
Recovery flag not set in backup superblock, so running journal anyway
...
fsck.ext4: unable to set superblock flags on /dev/mapper/vgubuntu--budgie-root
/dev/mapper/vgubuntu--budgie-root: **** FILE SYSTEM WAS MODIFIED****
/dev/mapper/vgubuntu--budgie-root: **** WARNING: Filesystem still has errors ****

For clarity: I'm meanwhile using a Live-USB Stick to boot into "try/install Ubuntu Budgie", from there decrypt the main partition (sda3) with cryptsetup, before performing further steps such as fsck. To see if anything "worked", I shut down, remove USB stick and try normal boot up.

edit 4: followed the next set of suggestions, report here:

After successfully unmounting and confirming that volume is writeable

sudo tune2fs -O has journal /dev/mapper/vgubuntu--budgie-root
...
Recovering journal.
tune2: Journal flags inconsistent while recovering journal
Please run e2fck -fy /dev/mapper/...
...
sudo fsck -fy /dev/mapper/vgubuntu--budgie-root

returns the same as above (Superblock needs_recovery flag is clear ... unable to set superblock flags).

I use Ubuntu Jammy Jellyfish 22.04.5 LTS with Gnome 42.9 on an ASUS E510 laptop. My internal microphone worked very well until I did an update several months ago. Now, it is dead even when set to 100%. In this condition, the record level in the settings panel shows a single bar which flashes on and off and appears to be picking up super quiet electronic interference noise but zero sound. At the time, if I rolled back my kernel the mike came to life again, so I know there is nothing physically wrong with the mike. I can now no longer use my mike AT ALL as that kernel is now no longer on my system to roll back to. Please help.

As requested here is the output from sudo lspci -vnn | awk -vRS= '/\[0403\]/':

00:1f.3 Audio device [0403]: Intel Corporation Device [8086:4dc8] (rev 01) (prog-if 80)
    Subsystem: ASUSTeK Computer Inc. Device [1043:1932]
    Flags: bus master, fast devsel, latency 32, IRQ 129, IOMMU group 10
    Memory at 6001120000 (64-bit, non-prefetchable) [size=16K]
    Memory at 6001000000 (64-bit, non-prefetchable) [size=1M]
    Capabilities: [50] Power Management version 3
    Capabilities: [80] Vendor Specific Information: Len=14 <?>
    Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
    Kernel driver in use: snd_hda_intel
    Kernel modules: snd_hda_intel, snd_sof_pci_intel_icl

I have installed xrdp on Ubuntu 22.04 Server where I also installed ubuntu-desktop for development and testing. When one user is logged in through remote desktop, others cannot login. How to allow multiple logins (different users)?

Also, how to allow some users to login using xrdp and disable xrdp login for other users? I have four users. I want to allow accesses for two and disable access for the other two.

For ssh, it can be done using DenyUsers as answered here. Does something similar exists for xrdp?

There is one accepted answer here but I couldn't make it work.

I have an Ubuntu dual boot on a partitioned Samsung SSD on a Windows 11 Lenovo Thinkbook 15-IIL. How do I fix BIOS errors and Kernel panics when booting up? The laptop boots up successfully, but it takes a little longer than it might with all of the errors.

How do I fix BIOS errors and kernel panics when booting up? Here is a sample of error messages that appear on black screen when booting:

BIOS Error (bug): Failure creating named object and Error: AE_ALREADY_EXISTS, During name lookup/catalog repetitions of these two phrases six times.

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) and end Kernel panic - not...

Note: command line has not finished processing/executing visual effects/framework (conceptual-psychology like 'framework', I mean) in the boot screens there.

BIOS Error (bug): Failure creating named object:

[    0.174778] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCIO.X
HC.RHUB.SS04._UPC], AE_ALREADY_EXISTS (20210730/dswload2-326)
[    0.174782] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (202107
30/psobject-220)
[    0.174785] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCIO.X
HC.RHUB.SS04._PLD], AE_ALREADY_EXISTS (20210730/dswload2-326)
[    0.174788] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (202107
30/psobject-220)
[    0.174793] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCIO.X
HC.RHUB.SS05._UPC], AE_ALREADY_EXISTS (20210730/dswload2-326)
[    0.174796] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (202107
30/psobject-220)
[    0.174800] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCIO.X
HC.RHUB.SS05._PLD], AE_ALREADY_EXISTS (20210730/dswload2-326)
[    0.174803] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (202107
30/psobject-220)
[    0.174807] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCIO.X
HC.RHUB.SS06._UPC], AE_ALREADY_EXISTS (20210730/dswload2-326)
[    0.174811] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (202107
30/psobject-220)
[    0.174814] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCIO.X
HC.RHUB.SS06._PLD], AE_ALREADY_EXISTS (20210730/dswload2-326)
[    0.174817] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (202107
30/psobject-220)
_

Kernel panic - not syncing:

[    0.174811] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (202107
30/psobject-220)
[    0.174814] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCIO.X
HC.RHUB.SS06._PLD], AE_ALREADY_EXISTS (20210730/dswload2-326)
[    0.174817] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (202107
30/psobject-220)
[    7.222649] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[    7.222737] CPU: 4 PID: 1 Comm: swapper/0 Not tainted 5.15.0-43-generic #46-Ubuntu
[    7.222806] Hardware name: LENOVO 20SM/LNUNB161216, BIOS DJCN25WW 03/29/2021
[    7.222866] Call Trace:
[    7.222889]  <TASK>
[    7.222910]  show_stack+0x52/0x58
[    7.222945]  dump_stack_lvl+0x4a/0x5f
[    7.222983]  dump_stack+0x10/0x12
[    7.223014]  panic+0x149/0x321
[    7.223046]  mount_block_root+0x144/0x1d9
[    7.223087]  mount_root+0x10c/0x118
[    7.223120]  prepare_namespace+0x13f/0x18d
[    7.223158]  kernel_init_freeable+0x18c/0x1b1
[    7.223210]  ? rest_init+0x100/0x100
[    7.223253]  kernel_init+0x1b/0x150
[    7.223294]  ? rest_init+0x100/0x100
[    7.223328]  ret_from_fork+0x1f/0x30
[    7.223365]  </TASK>
[    7.223432] Kernel Offset: 0x14c00000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)
[    7.223527] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---
_

When I power off Ubuntu 20.04 any type of way it just stays on this screen that says my computer logo and the Ubuntu logo at the bottom. I'm new to Linux. I just want to go to bed with my PC completely shut down.

Whenever I boot up, my monitor's settings are always zoomed in about at 10, out of a scale of 0-100.

It also happens if I turn my monitor off and on again.

If I change my Display settings to rotate my screen orientation from Landscape to Portrait and back, but not Landscape to Flipped Landscape and back.

And changing the Scale in the Display Settings menu doesn't mess up the Zoom again, either.

I have a Dell SP2208WFP, and my Monitors.xml looks like:

<monitors version="2">
  <configuration>
    <logicalmonitor>
      <x>0</x>
      <y>0</y>
      <scale>0</scale>
      <primary>yes</primary>
      <monitor>
        <monitorspec>
          <connector>HDMI-A-1</connector>
          <vendor>DEL</vendor>
          <product>SP2208WFP</product>
          <serial>RR268831CT0U</serial>
        </monitorspec>
        <mode>
          <width>1680</width>
          <height>1050</height>
          <rate>59.954250335693359</rate>
        </mode>
      </monitor>
    </logicalmonitor>
  </configuration>
</monitors>

...

And now, Scale is reset to 1... Because I exited a fullscreen app or something??

...

It even happens in Recovery Mode, when I don't have a DISPLAY variable set.

...

But, it doesn't seem to happen if I connect through the screwy connection cables instead of HDMI...

I'm trying to shrink this /dev/mapper partition, which says it has 71 GB available space:

Filesystem                            Size  Used Avail Use% Mounted on
udev                                  2.1G     0  2.1G   0% /dev
tmpfs                                 413M  656k  412M   1% /run
/dev/mapper/vg-root                   133G   56G   71G  45% /
tmpfs                                 2.1G     0  2.1G   0% /dev/shm
tmpfs                                 5.3M     0  5.3M   0% /run/lock
tmpfs                                 2.1G     0  2.1G   0% /sys/fs/cgroup
/dev/sda1                             495M  494M     0 100% /boot
tmpfs                                 413M     0  413M   0% /run/user/1000

I boot my machine (Ubuntu 18.04 Server) using a GParted live CD, but when I open GParted it only says only 48 MB is available.

It's showing as unmount, but I can't shrink the volume to more than 48 MB. Do you have any idea why?

I am using the Ubuntu on Windows App running on Windows Subsystem for Linux. So an initial question is if Python virtual environments is supported. Given my as yet limited understanding of Python virtual environments I would think that they are supported in the Ubuntu on Windows App. Here is the version info:

Windows Ubuntu App 1804.2019.521.0

Ubuntu release 18.04 (bionic)

Python Version 3.6.7 (as best I remember this was installed by default).

My motivation for wanting to use venv is this reddit post:

venv by nature of being part of Python itself has access to the internals of Python which means it can do things the right way with far fewer hacks... ...So venv can be thought of virtualenv done right, with the blessing and support of the Python developers.

Similar questions came up when I entered my question, but I didn't find one that solved my problem.

One post:

Since you specifically installed python3.6 instead of Ubuntu's default python3 version, which is python3.5, you have to install python3.6-venv instead of python3-venv since that would resolve to python3.5-venv. To do so, you can use sudo apt install python3.6-venv

Another post from 01/2018 said that python3.6 -m venv myvenv worked after reinstalling Python3.6.4. I'm avoiding re-installation for the time being.

Here is what I tried to create a virtual environment:

1) Opened Ubuntu

2) Went to the directory where I want to create the virtual environment.

 /home/dgrucza/python-virtual-environments

3) Entered python3 -m venv env This returned the following:

The virtual environment was not created successfully because ensurepip is not available. On Debian/Ubuntu systems, you need to install the python3-venv package using the following command.

apt-get install python3-venv

You may need to use sudo with that command. After installing the python3-venv package, recreate your virtual environment.

Failing command: ['/home/dgrucza/python-virtual-environments/evn/bin/python3', '-Im', 'ensurepip', '--upgrade', '--default-pip']

4)Tried to install venv by entering sudo apt-get install python-venv After entering my password at the prompt this returned the following:

Reading package lists... Done Building dependency tree Reading state information... Done Package python3-venv is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source

E: Package 'python3-venv' has no installation candidate

5) Also tried entering python3.6 -m venv myenv, but received the same message.

The virtual environment was not created successfully because ensurepip is not available. On Debian/Ubuntu systems, you need to install the python3-venv package using the following command.

apt-get install python3-venv

You may need to use sudo with that command. After installing the python3-venv package, recreate your virtual environment.

Failing command: ['/home/dgrucza/myenv/bin/python3.6', '-Im', 'ensurepip', '--upgrade', '--default-pip']

My HP laptop using a Realtek network adapter is not able to connect to WiFi. As it shows Airplane Mode On: Use Hardware switch to turn off I tried pressing it 100 times, but it had no result.

I have a dual boot with Windows 10 and WiFi is working fine there. I also tried following many questions on forums, but all were for Lenovo or Dell and older versions of Ubuntu, and none of them worked.

My rfkill list all command shows:

0 : phy0 : Wireless LAN
    Soft blocked: no
    Hard blocked: yes

I tried:

1. rfkill unblock all
2. Blacklisting hp-wmi.conf
3. Suspending laptop (some weird tutorial from YouTube)

I have been struggling to dual boot Windows 10 with Ubuntu 18.04. I have Windows 10 already installed with all the latest updates as of 21st July 2018. The problem that I am facing is that when I boot Ubuntu from the USB drive, I am asked to install Ubuntu. When I choose that option, while proceeding I see that there is no option to install Ubuntu alongside Windows.

Only option to erase the disk and other options are available. I looked up in the Internet and found similar problem for Dell XPS model but in that question dual booting was being done with Ubuntu 16.04. In that post it was advised to enable ahci in sata controller option in BIOS mode and to disable fast boot mode. I have done all those things but still option to install Ubuntu alongside Windows is not showing.

What I am trying to say that above option is not showing but all the rest options from second onwards is showing. The laptop that I am using is Lenovo g5080. I have Windows 10 (64bit) already installed and I don't want my data to be erased. Why am I unable to dual boot Windows 10 with Ubuntu 18.04?

disk management system

I am also adding screenshots from Ubuntu installation pages. I don't see "install Ubuntu along with Windows" option as shown below :

and partitions in Ubuntu. the free space is what I intend to use for Ubuntu installation

I had Lubuntu 17.04 installed and when I wanted to upgrade to 17.10 version there was some problems.

Finally I solved the problem by disabling all repositories and now I have Lubuntu 17.10. but I have a new problem.

• First: I have disabled all repositories and it is not possible to enable theme from software & update settings. When I try to mark a theme to enable, nothing happens!

• Second: when I use sudo apt-get update I have the following output that does not seems good:

  Ign:1 http://ppa.launchpad.net/ubuntu-wine/ppa/ubuntu artful InRelease         
  Hit:2 http://archive.ubuntu.com/ubuntu artful InRelease
  Get:3 http://archive.ubuntu.com/ubuntu artful-updates InRelease [78.6 kB]      
  Err:4 http://ppa.launchpad.net/ubuntu-wine/ppa/ubuntu artful Release     
    404  Not Found
  Get:5 http://archive.ubuntu.com/ubuntu artful-backports InRelease [72.2 kB]
  Get:6 http://archive.ubuntu.com/ubuntu artful-security InRelease [78.6 kB]
  Reading package lists... Done                                 
  E: The repository 'http://ppa.launchpad.net/ubuntu-wine/ppa/ubuntu artful Release' does not have a Release file.
  N: Updating from such a repository can't be done securely, and is therefore disabled by default.
  N: See apt-secure(8) manpage for repository creation and user configuration details.
  

Question update:
out put from sudo nano /etc/apt/sources.list is :

# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to

# newer versions of the distribution.
deb http://archive.ubuntu.com/ubuntu artful main restricted
deb-src http://archive.ubuntu.com/ubuntu artful universe multiverse main restricted #Added by software-properties
# deb-src http://us.archive.ubuntu.com/ubuntu/ zesty main restricted

## Major bug fix updates produced after the final release of the
## distribution.
deb http://archive.ubuntu.com/ubuntu artful-updates main restricted
deb-src http://archive.ubuntu.com/ubuntu artful-updates universe multiverse main restricted #Added by software-properties
# deb-src http://us.archive.ubuntu.com/ubuntu/ zesty-updates main restricted

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team. Also, please note that software in universe WILL NOT receive any
## review or updates from the Ubuntu security team.
deb http://archive.ubuntu.com/ubuntu artful universe
# deb-src http://us.archive.ubuntu.com/ubuntu/ zesty universe
deb http://archive.ubuntu.com/ubuntu artful-updates universe
# deb-src http://us.archive.ubuntu.com/ubuntu/ zesty-updates universe

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu 
## team, and may not be under a free licence. Please satisfy yourself as to 
## your rights to use the software. Also, please note that software in 
## multiverse WILL NOT receive any review or updates from the Ubuntu
## security team.
deb http://archive.ubuntu.com/ubuntu artful multiverse
# deb-src http://us.archive.ubuntu.com/ubuntu/ zesty multiverse
deb http://archive.ubuntu.com/ubuntu artful-updates multiverse
# deb-src http://us.archive.ubuntu.com/ubuntu/ zesty-updates multiverse

## N.B. software from this repository may not have been tested as
## extensively as that contained in the main release, although it includes
## newer versions of some applications which may provide useful features.
## Also, please note that software in backports WILL NOT receive any review
## or updates from the Ubuntu security team.
deb http://archive.ubuntu.com/ubuntu artful-backports main restricted universe multiverse
deb-src http://archive.ubuntu.com/ubuntu artful-backports main restricted universe multiverse #Added by software-properties
# deb-src http://us.archive.ubuntu.com/ubuntu/ zesty-backports main restricted universe multiverse

## Uncomment the following two lines to add software from Canonical's
## 'partner' repository.
## This software is not part of Ubuntu, but is offered by Canonical and the
## respective vendors as a service to Ubuntu users.
## deb http://archive.canonical.com/ubuntu zesty partner
## deb-src http://archive.canonical.com/ubuntu zesty partner

deb http://archive.ubuntu.com/ubuntu artful-security main restricted
deb-src http://archive.ubuntu.com/ubuntu artful-security universe multiverse main restricted #Added by software-properties
# deb-src http://security.ubuntu.com/ubuntu zesty-security main restricted
deb http://archive.ubuntu.com/ubuntu artful-security universe
# deb-src http://security.ubuntu.com/ubuntu zesty-security universe
deb http://archive.ubuntu.com/ubuntu artful-security multiverse
# deb-src http://security.ubuntu.com/ubuntu zesty-security multiverse
# deb http://cran.um.ac.ir/bin/linux/ubuntu artful/
# deb-src http://cran.um.ac.ir/bin/linux/ubuntu artful/
# deb [arch=amd64,i386] https://cran.rstudio.com/bin/linux/ubuntu xenial/
# deb-src [arch=amd64,i386] https://cran.rstudio.com/bin/linux/ubuntu xenial/
# deb-src [arch=amd64,i386] https://cran.rstudio.com/bin/linux/ubuntu xenial/
deb https://cran.r-project.org/bin/linux/ubuntu zesty/
deb-src https://cran.r-project.org/bin/linux/ubuntu zesty/
# deb http://archive.canonical.com/ precise partner
# deb-src http://archive.canonical.com/ precise partner

deb https://dl.winehq.org/wine-builds/ubuntu/ artful main
# deb-src https://dl.winehq.org/wine-builds/ubuntu/ artful main

but sudo apt-get update still has following result :

Hit:1 http://archive.ubuntu.com/ubuntu artful InRelease
Ign:2 http://ppa.launchpad.net/ubuntu-wine/ppa/ubuntu artful InRelease         
Hit:3 http://archive.ubuntu.com/ubuntu artful-updates InRelease                
Hit:4 http://archive.ubuntu.com/ubuntu artful-backports InRelease              
Err:5 http://ppa.launchpad.net/ubuntu-wine/ppa/ubuntu artful Release           
  404  Not Found
Hit:6 http://archive.ubuntu.com/ubuntu artful-security InRelease               
Hit:7 https://cran.r-project.org/bin/linux/ubuntu zesty/ InRelease             
Hit:8 https://dl.winehq.org/wine-builds/ubuntu artful InRelease                
Reading package lists... Done                      
E: The repository 'http://ppa.launchpad.net/ubuntu-wine/ppa/ubuntu artful Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

where can I fix :

Err:5 http://ppa.launchpad.net/ubuntu-wine/ppa/ubuntu artful Release           
      404  Not Found

I can't find it in my sources.list

System info:

• Dell Inspiron 1318
• Ubuntu 16.04 LTS, single boot

System doesn't boot past BIOS:

My Ubuntu laptop was working like a charm until I hit a snag. I was trying to install a package using dpkg -i, when it prompted me that some dependencies are required and it recommended to run apt-get -f install.

I ran that and during the installation, I got a pop-up (which filled the entire screen) saying a reboot would be required, with <OK> button, so I restarted the computer and now I get a black screen after the BIOS.

Searching around, I tried pressing the Shift key several times which gave me the GRUB menu with:

• *Ubuntu
• *Advanced options for Ubuntu

I selected 'Advanced options...' after which I get more options, and I selected the second one ...0-98-generic (recovery mode):

I am having terminal access to everything using root. I'm not sure how to resolve this.

Here is a screen after running journalctl -xb. I'm not sure if there is a better way to show this information, since it gives me a long list of lines.

[FAILED] Failed to start LSB: AppArmor initialization.
See 'systemctl status apparmor.service' for details.
[  OK  ] Started LSB: Inform plymouth that /var/log is writable.
[  OK  ] Started Load/Save Random Seed.
[  OK  ] Started Flush Journal to Persistent Storage.
         Starting Create Volatile Files and Directories...
[  OK  ] Started Create Volatile Files and Directories.
         Starting Network Time Synchronization...
         Starting Update UTMP about System Boot/Shutdown...
[  OK  ] Started Network Time Synchronization.
[  OK  ] Started Update UTMP about System Boot/Shutdown.
[  OK  ] Reached target System Time Synchronized.
[ TIME ] Timed out waiting for device dev-di... \x2dad80\x2d31cb46a69724.device.
[DEPEND] Dependency failed for /dev/disk/by-...bf0-4ab5-49eb-ad80-31cb46a69724.
[DEPEND] Dependency failed for Swap.
[  OK  ] Reached target System Initialization.
[  OK  ] Started Rescue Shell.
[  OK  ] Reached target Rescue Mode.
         Starting Update UTMP about System Runlevel Changes...
[  OK  ] Started Update UTMP about System Runlevel Changes.
Welcome to rescue mode! After logging in, type "journalctl -xb" to view
system logs, "systemctl reboot" to reboot, "systemctl default" or ^D to
boot into default mode. 
Press Enter for maintenance 
(or press Control-D to continue):

Then I get the following boot messages:

-- Logs begin at Wed 2017-11-15 12:12:05 EST, end at Wed 2017-11-15 12:15:11 EST. --
Nov 15 12:12:05 kedarps-Inspiron-1318 systemd-journald[202]: Runtime journal ( r
-- Subject: Disk space used by the journal
-- Defined-By: systemd
-- Support: [http://lists.freedesktop.org/mailman/listinfo/systemd-devel](http://lists.freedesktop.org/mailman/listinfo/systemd-devel)
-- Runtime journal (/run/log/journal/) is currently using 4.9M.
-- Maximum allowed usage is set to 39.4M.
-- Leaving at least 59.1M free (of currently available 389.0M of disk space).
-- Enforced usage limit is thus 39.4M, of which 34.4M are still available.
-- The limits controlling how much disk space is used by the journal 
-- may be configured with SystemMaxUse=, SystemKeepFree=, SystemMaxFileSize=,
-- RuntimeMaxUse=, RuntimeKeepFree=, RuntimeMaxFileSize= settings in
-- /etc/systemd/journald.conf. See journald.conf(5) for details.
Nov 15 12:12:05 kedarps-Inspiron-1318 kernel: microcode: CPU0 microcode updated
Nov 15 12:12:05 kedarps-Inspiron-1318 kernel: Initializing cgroup subsys cpuset
Nov 15 12:12:05 kedarps-Inspiron-1318 kernel: Initializing cgroup subsys cpu
Nov 15 12:12:05 kedarps-Inspiron-1318 kernel: Initializing cgroup subsys cpuacct
Nov 15 12:12:05 kedarps-Inspiron-1318 kernel: Linux version 4.4.0-96-generic (bu
Nov 15 12:12:05 kedarps-Inspiron-1318 kernel: Command line: BOOT_IMAGE=/boot/vml
Nov 15 12:12:05 kedarps-Inspiron-1318 kernel: KERNEL supported cpus:
Nov 15 12:12:05 kedarps-Inspiron-1318 kernel:   Intel GenuineIntel
Nov 15 12:12:05 kedarps-Inspiron-1318 kernel:   AMD AuthenticAMD

I tried reinstalling Ubuntu hoping that it would repair the installation. I made a live USB with Ubuntu and inserted it in the computer and selected Boot from USB Storage Device and I just get a black screen with a blinking cursor. It isn't moving to the 'Try Ubuntu', 'Install Ubuntu' screen.

I also tried fixing the AppArmor issue, by trying to install apparmor-easyprof-ubuntu as given here, but I'm not able to connect to the internet, hence I can't download using apt-get.

I connected an Ethernet cable and set-up wired internet and was able to fix the AppArmor issue by downloading and installing apparmor-easyprof-ubuntu. I also ran apt-get {update, upgrade, dist-upgrade} while in recovery mode. Now I NO longer get the 'Failed to start LSB' error, however I still get this error:

• Dependency failed for /dev/disk...
• Dependency failed for Swap

When I boot I only get terminal access. I can't see the login screen.

Here are the contents of the /etc/fstab file:

UUID=02f386fb-70ab-43d0-998c-8a30209872f5   /  ext4  errors=remount-ro 0  1
UUID=ab53ebf0-4ab5-49eb-ad80-31cb46a69724 none swap  sw                0  0

And here are the results after running blkid:

/dev/sda1: UUID="02f386fb-70ab-43d0-998c-8a30209872f5" TYPE="ext4" PARTUUID="bebca47d-01"
/dev/sda5: UUID="ab53ebf0-4ab5-49eb-ad80-31cb46a69724" TYPE="swap" PARTUUID="bebca47d-05"

I'm currently using Ubuntu Server 16.04 x86_64 on a Virtualbox VM.

I need to set up a dummy interface that comes up on boot. I have added the module dummy to /etc/modules and tried to bring it up puting the following lines in /etc/network/interfaces:

auto dummy0
iface dummy0 inet static
address 10.0.0.1
netmask 255.255.255.0
gateway 10.0.0.1

But after reboot I can't see the interface, if I made it manualy using ip link command it cames up without a problem so I'd like to ask if any one knows of a method to make this interface como up at boot.

Thanks in advance.

So I'm still with Ubuntu 16.04 on my Y700. I have installed the nvidia binary driver, though this happens with nouveau, too. When I open the 'Display' settings I see my internal laptop screen and my external screen. (Both enabled, extended desktop)

When I disable the internal screen (e.g. to run a game on the external screen only) the settings dialog becomes unreachable. It seems it's in the desktop region that was displayed before. When I click on the Icon in the window switcher I can see both windows of Screen settings but none becomes visible.

Is there any keyboard shortcut or something else to move all windows in the current display / desktop region?

I tried to record a video but 'RecordMyDesktop' crashed when disabling the second screen...

After a fresh install of Ubuntu 16.04, there was no sound on my 64 bit desktop pc. I followed the following link.

Installed Lubuntu 16.04 version no audio now

The sound worked. But on restart, it is not working.

Please help

I have followed the Step 3 of sound troubleshoot page and the output can be found in the following link. http://www.alsa-project.org/db/?f=09d65a90decc72f32dd97521497ae03894308c6e

This is somehow a follow up of this question:

How can I detect the BPM (beats per minute) of a song?

But now instead of detecting them in songs, I want to generate them.

I am looking for an application that will output a sound (something short like a beep) a configurable number of times per minute.

If I say 20bpm, it will output that sound every 3 seconds. (60/20)
If 60bpm, every sec.
If 120bpm every half a sec.

The reason for this is that I am learning how to play drum sets and the bpm looks really important. I am following this video on youtube.

update

Seems they are called metronomes and even Google got one. Cool Stuff.
https://www.google.com/search?q=metronomes
Thanks Nick.

I had a dual boot installation (Win8 & Ubuntu). I was not using Windows much and decided to have Ubuntu for the whole system. When I reinstalled Ubuntu, I got the error

error: no such partition
Entering rescue mode
grub rescue >

Then I tried the following at the grub rescue

set root=(hd1,1)
set prefix(hd1,1)/boot/grub
insmod normal
normal

When I tried these command, I got the Ubuntu boot menu where I was able to start the system. However, when I shut down the system and restarted I got the same grub rescue error. Can you please help?

I am not sure if this helps. Here is the output of sudo fdisk -l

I just stuck in another GPU to run two screens.

$ lspci | grep VGA
02:00.0 VGA compatible controller: NVIDIA Corporation G86 [GeForce 8500 GT] (rev a1)
03:00.0 VGA compatible controller: NVIDIA Corporation GT218 [GeForce 210] (rev a2)

but running xrandr I only see the first one:

$ xrandr
Screen 0: minimum 8 x 8, current 1920 x 1200, maximum 8192 x 8192
DVI-I-0 disconnected (normal left inverted right x axis y axis)
VGA-0 disconnected (normal left inverted right x axis y axis)
TV-0 disconnected (normal left inverted right x axis y axis)
DVI-I-1 connected 1920x1200+0+0 (normal left inverted right x axis y axis) 518mm x 324mm
   1920x1200      60.0*+
   1680x1050      60.0  
   1600x1200      60.0  
   1440x900       75.0     59.9  
   1280x1024      75.0     60.0  
   1280x800       74.9     59.8  
   1024x768       75.0     60.0  
   800x600        75.0     60.3  
   640x480        75.0     59.9  

And running gksudo nvidia-settings I only see the one GPU.

I found something about enabling two GPUs in the nvidia drivers so I tried this:

$ sudo nvidia-xconfig -a

Using X configuration file: "/etc/X11/xorg.conf".
NVIDIA: could not open the device file /dev/nvidia1 (Input/output error).

WARNING: Unable to use the nvidia-cfg library to query NVIDIA hardware.


ERROR: Unable to determine number of GPUs in system; cannot honor '--enable-all-gpus' option.

Backed up file '/etc/X11/xorg.conf' as '/etc/X11/xorg.conf.backup'
New X configuration file written to '/etc/X11/xorg.conf'

Any help highly appreciated!

I've got an HTPC that I built myself, with a Asus P5G41T-M Motherboard. It's got an on-board HDMI port, and I've been using that with no problems. I started out with Mythbuntu ( an older version ), and recently updated to 12.04.1 LTS without any issues.

I've been thinking about trying out XBMC for a while, and I decided to give it a go. Unfortunately, I seem to be running into quite a few issues.

I got XBMC installed from the repos without any issues, but when I try to run it from a console, a box pops up with the following:

XBMC needs hardware accelerated OpenGL rendering. Install an appropriate graphics driver.

Please consule XBMC Wiki for supported hardware http://wiki.xbmc.org/?title=Supported_hardware

In the console, it prints out the following:

X Error of failed request: BadRequest (invalid request code or no such operation)
  Major opcode of failed request:  136 (GLX)
  Minor opcode of failed request:  19 (X_GLXQueryServerString)
  Serial number of failed request:  12
  Current serial number in output stream:  12

When I run vainfo, I get this:

libva: VA-API version 0.32.0
libva: va_getDriverName() returns 0
libva: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva: va_openDriver() returns 0
vainfo: VA-API version: 0.32 (libva 1.0.15)
vainfo: Driver version: Intel i965 driver - 1.0.15
vainfo: Supported profile and entrypoints
      VAProfileMPEG2Simple            : VAEntrypointVLD
      VAProfileMPEG2Main              : VAEntrypointVLD

The file /usr/lib/x86_64-linux-gnu/dri/i964_drv_video.so exists:

# ls -l /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so 
-rw-r--r-- 1 root root 628728 Mar 29  2012 /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so

And in /var/log/Xorg.0.log the following error pops up:

GLX error: Can not get required symbols.

I'm not really sure where to go from here. I've tried searching all over for how to fix this problem. I've done "apt-get --reinstall xserver-xorg" ( as well as a few other video driver packages ) a few times, and no change.

Any help in getting this issue sorted out would be awesome.