I did a fresh installation of Ubuntu Cinnamon 26.4 LTS just after the date of release. It went well, except that I get this message every time I log in (not exactly after I log in but a little after... perhaps a minute). The message is:

"System program problem detected", and it comes together with the option of reporting the problem.

Has it happened to anybody else? Does anyone know what it could be?

Thanks!

Wifi does not work in the live session, but I have wired networking available. However, if I want to enable wifi connection, is it a good idea to install a proprietary driver for the hardware. And is it a problem, if I boot the USB Ubuntu in another computer that uses a different driver when it has the additional driver?

How can I install the driver?

I tried running sudo apt update with the following output:

And I tried to install software-properties-gtk. That one is needed in Ubuntu to install additional drivers, right?

@ubuntu @canonical

Kernel 6.17.0-22-generic on Ubuntu 24.04 LTS is causing initramfs boot failure! System gets stuck in BusyBox emergency shell. Workaround: boot older kernel via GRUB Advanced Options. Please fix! Others affected too.

While using remote desktop changing the primary mouse button from left to right has no effect on the remote mouse.

It seems to happen with all distros for this PC. I got a blank screen on boot if not in nomodeset. I tried many things in grub including amdgpu.dc=0, but they didn't work.

I'm from India, currently running Ubuntu 24.04.4 LTS. I am excited to upgrade to the newly released 26.04 LTS. However, even today's morning (Apr 25), my software updater couldn't find a newer version to upgrade to. Articles like (https://linuxconfig.org/upgrade-ubuntu-24-04-to-26-04) and (https://linuxize.com/post/how-to-upgrade-to-ubuntu-26-04/) suggest a manual upgrade via the terminal, first upgrading to a non-LTS version (25.10). I am not willing to wait till 26.04.1 LTS release.

How do I upgrade? Please help!

on X11 I was able to get immediate behavior through XKB, but on Wayland I can’t reproduce it. Is there any way to achieve this?

I’m running Ubuntu 26.04 LTS with GNOME 50.1 on Wayland and I don’t want the following behavior:

Press Caps Lock → LED turns on and activates immediately.
Press it again → the LED only turns off when the key is released.

Aa = AA x_x

I just upgraded to Ubuntu 26.04 and one thing I'm struggling with is not having a way to make my terminal background transparent. Did ubuntu or gnome kill this ability and if so, what terminal would be a good alternative?

I have an Ubuntu desktop that does not power all the way down. And i try to edit GRUB and modify GRUB_CMDLINE_LINUX_DEFAULT to be like this

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=force apm=power_off"

Then I updated Grub using sudo update-grub, but the problem still persists and the machine is not shutting down.

PC build:

• Motherboard: Asus TUF GAMING B460M-PLUS (WiFi)

• CPU: Intel Core i5-10400F CPU @ 2.90GHz

• GPU: RTX5050

Results of neofetch:

• OS: Ubuntu 24.04.4 LTS x86_64

• Kernel: 6.17.0-22-generic

• Uptime: 18 minutes

• Packages: 2284 (dpkg), 24 (snap)

• Shell: bash 5.2.21

• Resolution: 1920x1080

• DE: GNOME 46.0

• WM: Mutter

• WM Theme: Adwaita

• Theme: Orchis-Dark [GTK2/3]

• Icons: Tela-dark [GTK2/3]

• Terminal: gnome-terminal

• CPU: Intel i5-10400F (12) @ 4.300GHz

• GPU: NVIDIA 01:00.0 NVIDIA Corporation Device 2d83

• Memory: 4135MiB / 32008MiB

guiverc commented:

Problems when using non-standard tools (eg. a Debian upgrade of changing release codename only) will mean the Ubuntu specific upgrade steps (scripts) aren't run, if so I suggest you run them yourself or do whatever you didn't do that is done by the supported upgrade tool.

Debian-style upgrades are just a sources.list change and dist-upgrade change. I don't care about autoremove or Nvidia, but do-release-upgrade involves more importantly:

Release specific jobs:

• Plays with some configurations
• Runs release specific scripts:
  • For example, replaces Unity Desktop with Gnome Desktop.

I am tired of do-release-upgrade. I only understand it enough to run /tmp/ubuntu-release-upgrader-*/resolute to rerun it quickly and save time while rerunning it 30 times to debug its Python code to resolve a Surface Pro problem. Then it crashed and left apt unusable after disliking my local changes to /usr/share/X11/xkb/symbols. In previous releases, it prompted me about /etc/systemd/..., and I choose to launch a shell to run Vim, but I mistyped the path, and habitually pressed Ctrl+C or something instead of backspace, but this mistake killed do-release-upgrade. Also, I dislike its screen preventing touchscreen scrolling.

So where are the "Ubuntu specific upgrade steps (scripts)"? I prefer a single command to run that is constant across all releases, present and future, and that avoids me having to read all the Python code.

I have a coolermaster devastator II keyboard and the light doesn't work. I've tried xset on in terminal as well as brightnessctl with no luck.

I did a clean install of Ubuntu 26.04. After all the updates and setting it up, I set the display at 4k, but the highest refresh rate available is 29.97hz. In 24.04, I could get 59.97hz. How can I or anyone at Canonical fix this? I am assuming it's a Wayland issue, as I was always on Xorg before this. I am using a Asus ROG Strix gaming PC with GeForce 2070 Super graphics card. I use HDMI2 cable to my home theater, then to my TV. The install was fast and clean.

Running KDE and Ubuntu linux 24.04.4. After last update, netmanager(??), wl01 no longer appears in the window with the WIFI sources. Also, a connection that has worked for two years, (http://ares:10000) webmin, no longer works, connection cannot be found. However, if I use the local connection, 127.0.0.1, it connects to webmin.

Also, some links at websites no longer work. For example, I went to askubuntu.com and clicked on the 'login' button. I got a connection can't be found...however on another ubuntu linux box, all if fine. That how I'm entering this question. The second linux box is running Ubuntu 25.10.

I'm puzzled. It worked yesterday, today it doesn't and the only thing I did was to do the update. Any suggestions how to fix this?

The do-release-upgrade upgraded me to 26.04 LTS, but the Ubuntu Pro feature now found in Security Center tells me that my Ubuntu Pro is not compatible with my version of Ubuntu because it's not LTS. lsb_release -a tells me this is indeed 26.04 LTS.

My attempted solution was to install from downloaded media thinking the do-release-upgrade messed something up. Booting to this leaves me with a blank monitor, though booting appears to be successful as I heard the cute little tune when it boots.

Booting to hard disk failed then, leaving me with a blank monitor. Repeating the boot process 3-4 times eventually got the video functioning.

This is not ok. I don't really know what state my machine is in, but I'll leave it for now. I'm hoping things will be fixed in time.

Hardware: 2023 MSI Infinite RS 14NUI9-630US Gaming Desktop

Maia:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 26.04 LTS
Release:    26.04
Codename:   resolute

Bug 1: Ubuntu Pro isn't recognizing Ubuntu 26.04 LTS as supported

Bug 2: Ubuntu 26.04 installation media doesn't not support ultra-wide monitors.

Bug 3: The Ubuntu 26.04 installation media changes something in the computer video configuration so booting to the hard drive after a failed flash-drive installation doesn't return the computer to default configuration: the monitor is still blank upon booting to the installed Ubuntu 26.04. Several boots in succession is required to get the monitor functioning again.

When can we expect the Ubuntu Server 26.04 LTS image in MS Azure?

my computer is a Samsung Book 2 Pro 5G. The following System program problem detected message appeared while installing Ubuntu Desktop 26.04.

I am new to Linux. I have an RX 9060 XT and encountering a Linux-only issue where the GPU fails to initialize, resulting in a black screen when the monitor is connected to it.

The GPU works normally in Windows, but on Linux it fails during kernel driver initialization.

System information

• Kernel: 6.17.0-22-generic
• Mesa: Mesa 26.0.0-devel
• Distribution: Kubuntu 24.04
• GPU 1 (dGPU): AMD Radeon RX 9060 XT (Navi 44)
• GPU 2 (iGPU): AMD Ryzen 7 7700 Raphael (integrated)

Problem description

When the monitor is connected to the RX 9060 XT and the system boots:

• No display output. Not even the installation screen. When installing kubuntu I only see the menu where it says "Try or install kubuntu", after that is just black screen. (After connecting monitor to motherboard I get display so I can proceed to install)
• It only works when monitor is connected to iGPU
• GPU is detected in lspci, but driver initialization fails

lspci output

arib@arib-linux:~$ lspci -k | grep -A 3 -E "VGA|3D"
03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 44 [Radeon RX 9060 XT] (rev c0)
        Subsystem: Sapphire Technology Limited Device e493
        Kernel modules: amdgpu
03:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Navi 48 HDMI/DP Audio Controller
--
0e:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Raphael (rev c5)
        Subsystem: ASUSTeK Computer Inc. Raphael
        Kernel driver in use: amdgpu
        Kernel modules: amdgpu

As you can see there is no Kernel driver in use for the RX 9060 XT.

Kernel logs (amdgpu failure)

journalctl -b | grep -i amdgpu logs show:

[drm:amdgpu_bo_init [amdgpu]] *ERROR* Unable to set WC memtype for the aperture base
amdgpu 0000:03:00.0: amdgpu: sw_init of IP block <gmc_v12_0> failed -22
amdgpu 0000:03:00.0: amdgpu: amdgpu_device_ip_init failed
amdgpu 0000:03:00.0: amdgpu: Fatal error during GPU init
amdgpu 0000:03:00.0: amdgpu: probe with driver amdgpu failed with error -22

What I already tried:

sudo apt update
sudo apt install --only-upgrade linux-firmware

cd /tmp
git clone https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
cd linux-firmware
sudo cp -r amdgpu/* /lib/firmware/amdgpu/
sudo update-initramfs -u

• Updated system packages (apt upgrade)
• Updated linux-firmware
• Manually replaced AMD firmware from upstream linux-firmware repo
• Rebuilt initramfs (update-initramfs -u)

Verified BIOS settings:

• Above 4G decoding: enabled
• Resizable BAR: enabled

Also, I did not install any drivers from the AMD website.

What could be causing this issue?

I want to have a right hand mouse and a left hand mouse active at the same time in 24.04. I had used xinput on earlier versions but it does not look compatible with Xwayland server. I have loaded Input Remapper but I'm not understanding how to make the change. I get this far when changing one mouse to left hand but get stuck. How do I also change the left button? There is something basic I'm not understanding.

I think I have it now.

Somehow I ended with an unbootable system. I traced the problem to my /lib folder and possibly to other system folders

I currently have this ls -lsha lib lib32 lib64 libx32 usr/lib32/ usr/lib64 usr/libx32/

ubuntu@ubuntu:/media/ubuntu/8e5c9899-7541-4ab3-9577-27efa7337808$ ls -lsha lib lib32 lib64 libx32 usr/lib32/ usr/lib64 usr/libx32/
   0 lrwxrwxrwx 1 root root    9 Jun  4  2020 lib32 -> usr/lib32
   0 lrwxrwxrwx 1 root root    9 Jun  4  2020 lib64 -> usr/lib64
   0 lrwxrwxrwx 1 root root   10 Jun  4  2020 libx32 -> usr/libx32

lib:
total 12K
4.0K drwxr-xr-x  3 root root 4.0K May 14 16:22 .
4.0K drwxr-xr-x 22 root root 4.0K Jul  6 23:26 ..
4.0K drwxr-xr-x  3 root root 4.0K Feb 26  2020 terminfo

usr/lib32/:
total 8.0K
4.0K drwxr-xr-x  2 root root 4.0K Apr 23  2020 .
4.0K drwxr-xr-x 14 root root 4.0K Apr 23  2020 ..

usr/lib64:
total 8.0K
4.0K drwxr-xr-x  2 root root 4.0K Jan 27 16:29 .
4.0K drwxr-xr-x 14 root root 4.0K Apr 23  2020 ..
   0 lrwxrwxrwx  1 root root   32 Dec 16  2020 ld-linux-x86-64.so.2 -> /lib/x86_64-linux-gnu/ld-2.31.so

usr/libx32/:
total 8.0K
4.0K drwxr-xr-x  2 root root 4.0K Apr 23  2020 .
4.0K drwxr-xr-x 14 root root 4.0K Apr 23  2020 ..

My libs folders are empty.

When I try to boot I get this kernel panic:

/dev/sda5: clean, 781569/3751936 files, 9781643/15000064 blocks
run-init: can't execute '/sbin/init': No such file or directory
Target filesystem doesn't have requested /sbin/init.
run-init: can't execute '/sbin/init': No such file or directory
run-init: can't execute '/etc/init': Permission denied
[    4.121942] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100
[    4.121969] CPU: 1 PID: 1 Comm: run-init Not tainted 5.8.0-59-generic #66~20.04.1-Ubuntu
[    4.121991] Hardware name: System manufacturer System Product Name/PRIME A320M-K, BIOS 5007 06/18/2019
[    4.122016] Call Trace:
[    4.122033]  dump_stack+0x74/0x92
[    4.122044]  panic+0x101/0x2e3
[    4.122054]  do_exit.cold+0x54/0xa7
[    4.122068]  ? __prepare_exit_to_usermode+0x76/0x210
[    4.122083]  do_group_exit+0x43/0xa0
[    4.122094]  __x64_sys_exit_group+0x18/0x20
[    4.122108]  do_syscall_64+0x49/0xc0
[    4.122119]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[    4.122135] RIP: 0033:0x7ff4cc04e2c6
[    4.122147] Code: fa 41 b8 e7 00 00 00 be 3c 00 00 00 eb 15 66 0f 1f 44 00 00 89 d7 89 f0 0f 05 48 3d 00 f0 ff ff 77 22 f4 89
d7 44 89 c0 0f 05 <48> 3d 00 f0 ff ff 76 e2 f7 d8 64 41 89 01 eb da 66 2e 0f 1f 84 00
[    4.122193] RSP: 002b:00007ffca93c79b8 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
[    4.122214] RAX: ffffffffffffffda RBX: 00007ff4cc155610 RCX: 00007ff4cc04e2c6
[    4.122233] RDX: 0000000000000001 RSI: 000000000000003c RDI: 0000000000000001
[    4.122251] RBP: 0000000000000001 R08: 00000000000000e7 R09: ffffffffffffff80
[    4.122269] R10: 0000000000000002 R11: 0000000000000246 R12: 00007ff4cc155610
[    4.122288] R13: 0000000000000001 R14: 00007ff4cc158fc8 R15: 0000000000000000
[    4.122468] Kernel Offset: 0x3e00000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)
[    4.122516] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100 ]---
_

I'm guessing the only solution is to reinstall the system. Am I correct?

My system partition is OK, I think. As well as my home partition. I ran fsck with no problem.

ubuntu@ubuntu:~$ sudo fsck -f /dev/sda5
fsck from util-linux 2.34
e2fsck 1.45.5 (07-Jan-2020)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sda5: 781569/3751936 files (0.3% non-contiguous), 9781643/15000064 blocks
ubuntu@ubuntu:~$ sudo fsck -f /dev/sda6
fsck from util-linux 2.34
e2fsck 1.45.5 (07-Jan-2020)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sda6: 628676/3751936 files (0.6% non-contiguous), 9520496/15000064 blocks

I also executed boot-repair and I got this link https://paste.ubuntu.com/p/4CG9s4R9Dr/

Is there any way to recover the missing system files?

FWIW I think the culprit was a bad Debian package I built myself or the checkinstall program for that matter when I was compiling emacs.

ubuntu@ubuntu:/media/ubuntu/8e5c9899-7541-4ab3-9577-27efa7337808/usr/local/emacs$ ls -lsha backup-070620211826-pre-emacs-27.2-custom.tgz 
30M -rw-r--r-- 1 root root 30M Jul  6 23:26 backup-070620211826-pre-emacs-27.2-custom.tgz

It has the same contents I have in my /lib folder.

I am running Ubuntu 64-bit on my Raspberry Pi 3 B. There are several services running on that RPI but average system load is low, however, after some days I get a "soft lockup". The Raspberry Pi is not responsive anymore. Both the red and green LEDs are permanently on.

When I got the RPI connected to a monitor before the lockup, I got messages like these:

[36973.759872] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
[36973.765980] rcu: $2-...0: (1 GPs behind) idle=ee2/1/0x4000000000000002 softi
[Jul22 22:59] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
[  +0.006108] rcu: 2-...0: (1 GPs behind) idle=ee2/1/0x4000000000000002 so
[  +0.006185] (detected by 1, t=7977282 jiffies, g=2850229, q=53680)
[  +0.000005] Task dump for CPU 2:
[  +0.000007] node_exporter R running task 0 2174 1 0x0000000a
[  +0.000013] Call trace:
[  +0.000016]  __switch_to+0xf0/0x150
[  +0.000009]  0x0
[36999.951966] watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [swapper/1:0]
[ +26.179751] watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [swapper/1:0]
[  +0.006622] Modules linked in: joydev input leds hid generic usbhid binfmt mic

Common questions / troubleshooting:

What Ubuntu Version am I using? I tried 19.10 and 20.04 - the problem exists on both but seems to be worse on 20.04

What about the soft lockup kernel panic setting? Changing /proc/sys/kernel/softlockup_panic from 0 to 1 did not help - system still hangs and does not reboot.

Why do I use 64bit? Because a software package I use is only available in 64-bit.

What about the power supply? I made sure to use an original RPI power supply (2.5 A).

What about Raspbian OS? When running the same setup using Raspbian 64-bit I did not experience this soft lockups, but 64-bit support for Raspbian OS is still beta and I might have other problems instead.

Is this a known issue or a kernel bug? What to do next?

On Ubuntu 18.04 I run which gcc and the output is as expected.

ubuntu@USER1:~$ which gcc
/usr/bin/gcc

However when I activate my conda environment and run which gcc I get:

(tensorflow_p36) ubuntu@USER1:~$ which gcc
/home/ubuntu/anaconda3/envs/tensorflow_p36/bin/gcc

This location seems strange to me. I wan to use the normal system wide gcc.

I know this is not default behaviour as in my other Ubuntu instance when I run which gcc the output is correct:

(tensorflow_p36) ubuntu@USER2:~$ which gcc
/usr/bin/gcc

How can I get conda to use the default gcc as shown with USER2?

EDIT:

USER1 instance: conda 4.5.12

(tensorflow_p36) ubuntu@USER1:~$ gcc -v
Reading specs from /home/ubuntu/anaconda3/envs/tensorflow_p36/bin/../lib/gcc/x86_64-unknown-linux-gnu/4.8.5/specs
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/home/ubuntu/anaconda3/envs/tensorflow_p36/bin/../libexec/gcc/x86_64-unknown-linux-gnu/4.8.5/lto-wrapper
Target: x86_64-unknown-linux-gnu
Thread model: posix 
gcc version 4.8.5 (GCC)

but

ubuntu@USER1:~$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/8/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Thread model: posix
gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1~18.04.1) 

I have had Ubuntu for quite some time now and recently I have been having some problems with the generic drivers that have been causing kernel crashes and so many things went wrong that I can't fix anything because every problem keeps me from fixing the others. I discussed the problem about the generic drivers here: Ubuntu 18.04 having kernel panic on boot and I never found a fix.

Now I have decided that the easiest thing to do will be to boot Ubuntu fresh from a CD onto the computer in a different partition and then delete the old one. Now, I am wondering if there is a way to transfer my personal files from the previous partition (my personal files are fine despite the problems I have been having) into the my new boot as I am installing it. Is it even possible or would it pollute my new installation as well? Is it better to transfer the files manually after the installation? I also have Kali Linux and Windows 10 running on the same machine.

I've installed Ubuntu 18.04 LTS alongside Windows 10. I can access the Windows partition and can read the files. But I can't create any files or folders in that partition. All the options for "Cut", "Move to" and "Rename" are greyed out. How can I have write access to the partition from Ubuntu?

The output for df -H command

The contents of fstab file

The output for sudo lsblk -o NAME,SIZE,FSTYPE,MOUNTPOINT,LABEL

I know this is a common issue, and I've already searched and tried all I've found, but nothing works. I've been trying to install Ubuntu 16.04 on my desktop but I can't seem to make it work. I've tried both with USB and DVD (both checked for intregrity) with no differences.

The USB/DVD boots, and it shows the UEFI selection screen (try Ubuntu, install, check disk, etc...). Whichever I choose, it goes straigth to a blank screen.

I've tried booting in BIOS (legacy) mode, and the only difference is I don't get the selection screen, just a brief purple screen with the little guy on the bottom, and then again, blank screen.

I've also tried with the following grub boot methods: nomodeset, nolapic, acpi=off, and different combinations of them. Some combinations shows some processes going on, but no luck, some of them go to a kernel panic.

Here are my specs:

Gigabyte Gigabyte GA-970A-D3P (no on-board video)
AMD FX6300
Sapphire RX460

As far as I get:

I just installed Ubuntu 16.04 on my Windows 10 preinstalled desktop. Everything looks OK, but I cannot shut down on Ubuntu. Every time when I shut it down it gets stuck at a panic error like end kernel panic: not syncing: fatal exception in interrupt.

000
[  561.729332] Call Trace:
[  561.729934]  <IRQ>
[  561.729945]  [<ffffffff8e0c1aae>] ? rebalance_domains+0x27e/0x2d0
[  561.731104]  [<ffffffff8e0e0011>] __handle_irq_event_percpu+0x81/0x1a0
[  561.731684]  [<ffffffff8e0e0162>] handle_irq_event_percpu+0x32/0x80
[  561.732256]  [<ffffffff8e0e01ee>] handle_irq_event+0x3e/0x60
[  561.732819]  [<ffffffff8e0e38c2>] handle_fasteoi_irq+0xa2/0x160
[  561.733357]  [<ffffffff8e0302cd>] handle_irq+0x1d/0x30
[  561.733881]  [<ffffffff8e89d0db>] do_IRQ+0x4b/0xd0
[  561.734390]  [<ffffffff8e89b1c2>] common_interrupt+0x82/0x82
[  561.734889]  <EOI>
[  561.734899]  [<ffffffff8e71934b>] ? cpuidle_enter_state+0x12b/0x2d0
[  561.735869]  [<ffffffff8e719527>] cpuidle_enter+0x17/0x20
[  561.736366]  [<ffffffff8e0c7a0a>] call_cpuidle+0x2a/0x50
[  561.736865]  [<ffffffff8e0c7dee>] cpu_startup_entry+0x29e/0x350
[  561.737366]  [<ffffffff8e0518b1>] start_secondary+0x151/0x190
[  561.737871] Code: ff ff e9 a9 fc ff ff 4c 63 6b 5c 48 8b 43 50 8b 53 60 4c 8b
 43 68 48 89 c1 48 89 45 a8 44 89 6d d0 4c 89 e8 49 c1 e5 04 49 01 cd <41> 0f b7
 4d 00 66 89 4d a6 8b 4b 58 39 c8 89 4d c8 0f 8d 83 04
[  561.739462] RIP [<ffffffffc101fb0a>] i2c_dw_isr+0x49a/0x980 [i2c_designware_
core]
[  561.740501]  RSP <ffff9a7703dc3e38>
[  561.741034] CR2: 0000000000000000
[  561.741556] ---[ end trace 1333f9b6ecbe83ee ]---
[  561.742071] Kernel panic - not syncing: Fatal exception in interrupt
[  561.742629] Kernel Offset: 0xd000000 from 0xffffffff81000000 (relocation range: 
0xffffffff80000000-0xffffffffbfffffff)
[  561.743642] ---[ end Kernel panic - not syncing: Fatal exception in interrupt
_

By now I can only when I finish using Ubuntu: either restart and choose to log in on windows OS and shut down normally (since my Windows works normally), or press the physical power off button on the machine when I was trying to shut down and it froze in Ubuntu afterwards

Here is some information about the desktop and system:

   GPU: NVIDIA gtx-1080
   256 GB SSD
   2T HDD (100GB SSD and 500 GB HDD for Ubuntu)
   Ubuntu: '/' and 'swap' on SSD, '/home' on HDD

Please be patient with me as I am still learning how to do anything Linux, starting with Ubuntu.

I have installed Ubuntu 14.04 and had some issues playing around with it and petty much now it won't boot up which would be fine as I am using the computer to play with Ubuntu nothing more. But while on holidays, I had copied some family pics on the hard drive I moved there to watch on TV though HDMI, and my camera has since been stolen. so I want to try save the family pics \ vids which fortunately are on the Ubuntu drive... which I can't access.

But there is more... When I first installed Ubuntu... I selected to encrypt the drive. I do have the password. so that is not an issue. issue is I have tried to access the drive by booting up off an Ubuntu 15.10 I think.

SO I figured I will see the drive, be prompted for password and then I can access my data and save to USB drive. But no I don't have permission to access the drive. No request for password.

Help with instructions as I have limited (very Limited) Linux knowledge.

Jinn

As mailchimp & other online bulk email service provider companies allow their users to send bulk emails & keeps track of emails are sent / bounced / undelivered / opened / spammed / deleted

which utilities or packages do we need to install on ubuntu in order to provide such service ? Is it POSTFIX MAILX..? Or Do we need to install & configure a mail server; If so which packages / binaries we use?

For the past couple days, following an attempt to update the OS, my computer shows this kernel panic on boot-up:

[    0.469611] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[    0.469653] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.13.0-36-generic #63-Ubuntu
[    0.469693] Hardware name:                     /DG41RQ, BIOS RQG4110H.86A.0009.2
009.0108.1005 01/08/2009
[    0.469734]  0000000000000001 ffff880139a77df0 ffffffff8171e569 ffffffff81a3d0f8
[    0.469897]  ffff880139a77e68 ffffffff817176e0 3030623000000010 ffff880139a77e78
[    0.470059]  ffff880139a77e18 ffffff000307273 ffff880139a77e88 00000000000000b6
[    0.470222] Call Trace:
[    0.470261]  [<ffffffff8171e569>] dump_stack+0x45/0x56
[    0.470299]  [<ffffffff817176e0>] panic+0xc8/0x1d7
[    0.470338]  [<ffffffff81d36465>] mount_block_root+0x225/0x2b0
[    0.470376]  [<ffffffff81d3668d>] mount_root+0x53/0x56
[    0.470414]  [<ffffffff81d367fc>] prepare_namespace+0x16c/0x1a4
[    0.470453]  [<ffffffff81d36169>] kernel_init_freeable+0x1f3/0x200
[    0.470491]  [<ffffffff81d358e5>] ? do_early_param+0x88/0x88
[    0.470530]  [<ffffffff8170ca80>] ? rest_init+0x80/0x80
[    0.470567]  [<ffffffff8170ca8e>] kernel_init+0xe/0x130
[    0.470612]  [<ffffffff8172eefc>] ret_from_fork+0x7c/0xb0
[    0.470650]  [<ffffffff8170ca80>] ? rest_init+0x80/0x80
_

The only reason I'm using it right now is that I booted up from an older version, but I've had problems with installing new version before, and also getting error messages like this:

I believe I've also had problems removing old ones through the terminal.

What's the best route at this point?

Understanding it as a kernel panic, I managed to get some info on my boot files. Here's what came up.

 => Grub2 (v1.99) is installed in the MBR of /dev/sda and looks at sector 1 of 
    the same hard drive for core.img. core.img is at this location and looks 
    in partition 112 for .

sda1: 

    File system:       ext2
    Boot sector type:  -
    Boot sector info: 
    Operating System:  
    Boot files:        /grub/grub.cfg

sda2: 

    File system:       Extended Partition
    Boot sector type:  Unknown
    Boot sector info: 

sda5: 

    File system:       crypto_LUKS
    Boot sector type:  Unknown
    Boot sector info: 

ubuntu-vg-root': 

    File system:       
    Boot sector type:  Unknown
    Boot sector info: 
    Mounting failed:   mount: unknown filesystem type ''

ubuntu-vg-swap_1': 

    File system:       
    Boot sector type:  Unknown
    Boot sector info: 
    Mounting failed:   mount: unknown filesystem type ''
mount: unknown filesystem type ''

    ============================ Drive/Partition Info: =============================
    
    Drive: sda 
    
    Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
    255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    
    Partition  Boot  Start Sector    End Sector  # of Sectors  Id System
    
    /dev/sda1    *          2,048       499,711       497,664  83 Linux
    /dev/sda2             501,758 1,953,523,711 1,953,021,954   5 Extended
    /dev/sda5             501,760 1,953,523,711 1,953,021,952  83 Linux
    
    
    "blkid" output: 
    
    Device           UUID                                   TYPE       LABEL
    
    /dev/mapper/sda5_crypt mLMv6i-emLW-vtk7-IRqk-QNrh-WhXk-VLqRFf LVM2_member 
    /dev/mapper/ubuntu--vg-root 5077026c-b631-4601-b0e9-fc228c6860e9   ext4       
    /dev/sda1        8fb7c16b-f131-4622-86f0-e3a54e5272c3   ext2       
    /dev/sda5        37bfa81a-5253-4b9e-bfb3-963476e52b17   crypto_LUKS 
    
    ========================= "ls -R /dev/mapper/" output: =========================
    
    /dev/mapper:
    control
    sda5_crypt
    ubuntu--vg-root
    ubuntu--vg-swap_1
    
    ================================ Mount points: =================================
    
    Device           Mount_Point              Type       Options
    
    /dev/mapper/ubuntu--vg-root /                        ext4       (rw,errors=remount-ro)
    /dev/sda1        /boot                    ext2       (rw)
    
    
    ============================= sda1/grub/grub.cfg: ==============================

Specs:

 - Memory: 3.9 GiB
 - Processor: Intel® Core™2 Quad CPU Q8300 @ 2.50GHz × 4 
 - Graphics: Gallium 0.4 on NV96
 - OS: 64-bit
 - Disk: 980.1 GB (and yet it says I don't have enough space in boot)

This problem has been plaguing my boot for a while, it happens about half the times I start up my computer. Grub will load successfully, and wait ten seconds for me to choose which OS to boot into. When I choose Ubuntu, I am (4/5 times) confronted with this error:

error: attempt to read or write outside of disk `hd0`.
error: you need to load the kernel first.
Press any key to continue...

or this one:

error: attempt to read or write outside of disk `hd0`.
Press any key to continue...

When it displays the first error, pressing Enter will make it go back to the main menu, but when it is displaying the second error, without you need to load the kernel first, pressing any key will result in loading Ubuntu, and a kernel panic.

This doesn't happen every time, though if I try enough times it will work.

Debugging information:

$ fdisk -l
Disk /dev/sda: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders, total 234441648 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000d0b78

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *        2048    83886079    41942016    7  HPFS/NTFS/exFAT
/dev/sda2        83886080   234440703    75277312    5  Extended
/dev/sda5        83888128   109053951    12582912   83  Linux
/dev/sda6       109056000   234440703    62692352   83  Linux

$ sudo fsck -f /dev/sda5
fsck from util-linux 2.20.1
e2fsck 1.42 (29-Nov-2011)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sda5: 207541/786432 files (0.3% non-contiguous), 1389304/3145727 blocks

$ sudo fsck -f /dev/sda6
fsck from util-linux 2.20.1
e2fsck 1.42 (29-Nov-2011)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
ubuntu-home: 194036/3923968 files (0.6% non-contiguous), 11943110/15673088 blocks

boot-info summary from Boot-Repair: http://paste.ubuntu.com/6886738/

I've tried:

• Running sudo update-grub
• Running sudo grub-install /dev/sda
• Using boot-repair (more than once). I used the options Purge grub before reinstalling it and Purge kernels then reinstall last kernel. I've also tried Reset extra space after MBR.

I also saw other questions asking around the same thing, but as far as I can tell they all were about getting the grub rescue prompt with this error, rather than after selecting Ubuntu.

I can't boot to Ubuntu 12.04. I get a blinking cursor and my caps key LED keeps flashing.

I've tried recovery mode and it gives the same error messages. I've tried loading a previous version from the grub menu, but I still have the same error. It all started a week ago when I upgraded from 11.10 to UBUNTU 12.04 and in the final stages of the upgrade I noticed that my screen had gone blank as usual when you leave your computer unattended for a while. When I moved the mouse it prompted for the password as usual, but when I entered the password I couldn't get to the desktop environment. The Windows partition runs normally.

The error is as follows:

[  251.908847] Kernel panic: Not syncing: Attempting to kill init!
[  251.908862] PID 1, Comm: Init not tainted 2.6.38-8-generic #42-ubuntu

DRDY err 
Error {UNC} 
etc ----

I tried running sudo apt-get update using a live CD and got the same error messages.