I’m facing a frustrating black screen issue with Ubuntu on my Dell Latitude 5400 (i7). Live USB works great: When I select "Try Ubuntu," everything works perfectly. Graphics are smooth, the screen resolution is correct, and I can use the OS without any issues.

As soon as I finish the installation and reboot, I get a permanent black screen right after the Grub menu. The system seems to be running, but there’s no display.

I can only boot if I add nomodeset to the boot parameters, but this makes the UI laggy and I lose hardware acceleration. Settings and Troubleshooting: Secure Boot is OFF. SATA Mode is set to AHCI.

I've tried both Ubuntu 22.04 and 24.04, and the behavior is the same. Since the live USB works fine, I assume it's a driver initialization issue during the final boot process.

What could be causing the display to fail only after installation? Are there any specific Intel graphics kernel parameters (besides nomodeset) that I should try to get the i915 driver to load correctly?

I tried to dual boot my Ubuntu 24 OS with Windows suggestions of formatting partition to ntfs said to help the Windows installer work correctly, but after formatting with GParted I booted and the boot stopped at grub with message Minimal BASH-like line editing is supported...

I tried the suggestions of installing grub in partition, but I am a new inexperienced Ubuntu user. I finally ran Boot-Repair, but the suggested repair would not act on the boot.

Here is the Boot-Repair report.

============================== Boot Info Summary ===============================

 => Grub2 (v2.00) 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 
    for (,msdos1)/grub. It also embeds following components:
    
    modules
    ---------------------------------------------------------------------------
    fshelp ext2 part_msdos biosdisk
    ---------------------------------------------------------------------------

sda1: __________________________________________________________________________

    File system:       ext4
    Boot sector type:  -
    Boot sector info: 
    Operating System:  Ubuntu 24.04.1 LTS
    Boot files:        /boot/grub/grub.cfg /etc/fstab /etc/default/grub 
                       /grub/i386-pc/core.img /boot/grub/i386-pc/core.img

sda2: __________________________________________________________________________

    File system:       iso9660
    Boot sector type:  Unknown
    Boot sector info: 
    Operating System:  
    Boot files:        

sda3: __________________________________________________________________________

    File system:       xfs
    Boot sector type:  -
    Boot sector info: 
    Operating System:  
    Boot files:        /grub2/grub.cfg /grub2/i386-pc/core.img

sda4: __________________________________________________________________________

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

sda5: __________________________________________________________________________

    File system:       ntfs
    Boot sector type:  Unknown
    Boot sector info:  No errors found in the Boot Parameter Block.
    Operating System:  
    Boot files:        

sdb: ___________________________________________________________________________

    File system:       iso9660
    Boot sector type:  Grub2 (v1.99-2.00)
    Boot sector info:  Grub2 (v1.99-2.00) is installed in the boot sector of 
                       sdb and looks at sector 0 of the same hard drive for 
                       core.img, but core.img can not be found at this 
                       location.
    Mounting failed:   mount: /mnt/BootInfo/FD/sdb: /dev/sdb already mounted or mount point busy.
       dmesg(1) may have more information after failed mount system call.


================================ 1 OS detected =================================

OS#1 (linux):   Ubuntu 24.04.1 LTS on sda1

================================ Host/Hardware =================================

CPU architecture: 64-bit
Video: 2nd Generation Core Processor Family Integrated Graphics Controller from Intel Corporation
Live-session OS is Ubuntu 64-bit (Ubuntu 24.04.1 LTS, noble, x86_64)

===================================== UEFI =====================================

BIOS/UEFI firmware: F.28(15.40) from Hewlett-Packard
This live-session is in Legacy/BIOS/CSM mode (not in EFI mode).



============================= Drive/Partition Info =============================

Disks info: ____________________________________________________________________


Partitions info (1/3): _________________________________________________________


Partitions info (2/3): _________________________________________________________


Partitions info (3/3): _________________________________________________________


fdisk -l (filtered): ___________________________________________________________

Disk sda: 465.76 GiB, 500107862016 bytes, 976773168 sectors
Disk identifier: 0x7dd243c7
     Boot     Start       End   Sectors   Size Id Type
sda1  *         2048 662953983 662951936 316.1G 83 Linux
sda2       974645248 976773119   2127872     1G 83 Linux
sda3       819202048 821299199   2097152     1G 83 Linux
sda4       821301246 974645247 153344002  73.1G  5 Extended
sda5       821301248 974645247 153344000  73.1G  7 HPFS/NTFS/exFAT
Partition table entries are not in disk order.
Disk sdb: 7.2 GiB, 7736072192 bytes, 15109516 sectors
Disk identifier: EED3DE8A-ACD3-4541-BA15-9014C007D874
        Start      End  Sectors  Size Type
sdb1        64 12105119 12105056  5.8G Microsoft basic data
sdb2  12105120 12115263    10144    5M EFI System
sdb3  12115264 12115863      600  300K Microsoft basic data
sdb4  12115968 15108095  2992128  1.4G Linux filesystem

parted -lm (filtered): _________________________________________________________

sda:500GB:scsi:512:4096:msdos:ATA WDC WD5000BPVT-6:;
1:1049kB:339GB:339GB:ext4::boot;
3:419GB:421GB:1074MB:xfs::;
4:421GB:499GB:78.5GB:::;
5:421GB:499GB:78.5GB:ntfs::;
2:499GB:500GB:1089MB:::;
sdb:7736MB:scsi:512:512:gpt:Kingston DataTraveler 3.0:;
1:32.8kB:6198MB:6198MB::ISO9660:hidden, msftdata;
2:6198MB:6203MB:5194kB::Appended2:boot, esp;
3:6203MB:6203MB:307kB::Gap1:hidden, msftdata;
4:6203MB:7735MB:1532MB:ext4::;

Free space >10MiB: ______________________________________________________________

sda: 323708MiB:400001MiB:76293MiB

blkid (filtered): ______________________________________________________________

NAME   FSTYPE   UUID                                 PARTUUID                             LABEL                    PARTLABEL
sda                                                                                                                
├─sda1                                                                                                             
├─sda2                                                                                                             
├─sda3                                                                                                             
├─sda4                                                                                                             
└─sda5                                                                                                             
sdb    iso9660  2024-08-27-16-23-26-00                                                    Ubuntu 24.04.1 LTS amd64 
├─sdb1 iso9660  2024-08-27-16-23-26-00               eed3de8a-acd3-4541-ba14-9014c007d874 Ubuntu 24.04.1 LTS amd64 ISO9660
├─sdb2 vfat     3C53-CAEB                            eed3de8a-acd3-4541-ba17-9014c007d874 ESP                      Appended2
├─sdb3                                               eed3de8a-acd3-4541-ba16-9014c007d874                          Gap1
└─sdb4 ext4     d3624409-af7b-40c6-b255-3ba6484a8ed1 a8eb0859-3619-451d-b784-871024015d71 writable                 

Mount points (filtered): _______________________________________________________

                                                               Avail Use% Mounted on
/dev/sdb1                                                          0 100% /cdrom

Mount options (filtered): ______________________________________________________

/dev/sdb1                                                     iso9660         ro,noatime,nojoliet,check=s,map=n,blocksize=2048,iocharset=utf8

====================== sda1/boot/grub/grub.cfg (filtered) ======================

Ubuntu   aa61d74c-2935-40fd-b69b-c0735f9e314e
Oracle Linux Server 7.5 (on mapper/ol-root)   fd36dd4b-178c-4ce1-861a-3c2936bb9855
### END /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_uefi-firmware ###

========================== sda1/etc/fstab (filtered) ===========================

# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda1 during installation
UUID=aa61d74c-2935-40fd-b69b-c0735f9e314e /               ext4    errors=remount-ro 0       1
/dev/mapper/ol-swap none            swap    sw              0       0
/swapfile none swap sw 0 0

======================= sda1/etc/default/grub (filtered) =======================

GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=2
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""

==================== sda1: Location of files loaded by Grub ====================

           GiB - GB             File                                 Fragment(s)
   0.148139954 = 0.159064064    boot/grub/grub.cfg                             1
 268.156513214 = 287.930863616  grub/i386-pc/core.img                          1
 300.134799957 = 322.267287552  boot/grub/i386-pc/core.img                     1
  32.311737061 = 34.694463488   boot/vmlinuz                                   1
 289.077362061 = 310.394454016  boot/vmlinuz-6.8.0-44-generic                  1
  32.311737061 = 34.694463488   boot/vmlinuz-6.8.0-45-generic                  1
 289.077362061 = 310.394454016  boot/vmlinuz.old                               1
  51.267700195 = 55.048273920   boot/initrd.img                                2
  24.236244202 = 26.023469056   boot/initrd.img-6.8.0-44-generic               3
  51.267700195 = 55.048273920   boot/initrd.img-6.8.0-45-generic               2
  24.236244202 = 26.023469056   boot/initrd.img.old                            3

===================== sda1: ls -l /etc/grub.d/ (filtered) ======================

-rwxr-xr-x 1 root root 18683 Dec 18  2022 10_linux
-rwxr-xr-x 1 root root 43031 Dec 18  2022 10_linux_zfs
-rwxr-xr-x 1 root root 14387 Dec 18  2022 20_linux_xen
-rwxr-xr-x 1 root root 13369 Dec 18  2022 30_os-prober
-rwxr-xr-x 1 root root  1372 Dec 18  2022 30_uefi-firmware
-rwxr-xr-x 1 root root   700 Feb 21  2022 35_fwupd
-rwxr-xr-x 1 root root   214 Apr 15  2020 40_custom
-rwxr-xr-x 1 root root   215 Dec 18  2022 41_custom

======================== sda3/grub2/grub.cfg (filtered) ========================

Oracle Linux Server 7.5, with Unbreakable Enterprise Kernel 4.1.12-124.15.2.el7uek.x86_64   fd36dd4b-178c-4ce1-861a-3c2936bb9855
Ubuntu 17.10 (17.10) (on sdb1)   5860abff-eed9-4c0c-8384-14feb3185455
### END /etc/grub.d/30_os-prober ###

==================== sda3: Location of files loaded by Grub ====================

           GiB - GB             File                                 Fragment(s)
 391.376094818 = 420.236881920  grub2/grub.cfg                                 1
 390.785617828 = 419.602862080  grub2/i386-pc/core.img                         1
 390.743591309 = 419.557736448  vmlinuz-0-rescue-3cbfe8baf9be4ea49bdece307dc3b322  1
 390.634929657 = 419.441061888  vmlinuz-3.10.0-693.el7.x86_64                  1
 390.842624664 = 419.664072704  vmlinuz-3.10.0-862.3.2.el7.x86_64              1
 390.851856232 = 419.673985024  vmlinuz-4.1.12-124.15.2.el7uek.x86_64          1
 390.644039154 = 419.450843136  vmlinuz-4.1.12-94.3.9.el7uek.x86_64            1
 390.753078461 = 419.567923200  initrd-plymouth.img                            1
 390.738117218 = 419.551858688  initramfs-0-rescue-3cbfe8baf9be4ea49bdece307dc3b322.img  1
 390.814861298 = 419.634262016  initramfs-3.10.0-693.el7.x86_64.img            1
 390.909820557 = 419.736223744  initramfs-3.10.0-862.3.2.el7.x86_64.img        1
 390.782630920 = 419.599654912  initramfs-4.1.12-124.15.2.el7uek.x86_64.img    1
 390.864944458 = 419.688038400  initramfs-4.1.12-124.15.2.el7uek.x86_64kdump.img  1
 390.939392090 = 419.767975936  initramfs-4.1.12-94.3.9.el7uek.x86_64.img      1
 390.833065033 = 419.653808128  initramfs-4.1.12-94.3.9.el7uek.x86_64kdump.img  1

======================== Unknown MBRs/Boot Sectors/etc =========================

Unknown BootLoader on sda2

Unknown BootLoader on sda5




Suggested repair: ______________________________________________________________

The default repair of the Boot-Repair utility would not act on the boot.

paste.ubuntu.com ko ()

Two years ago, I installed Windows Subsystem for Linux (WSL) on my Windows 11 Professional machine. And then due to other pressing issues, I just forgot about it.

Last night, thinking that I didn't have Ubuntu installed on my WSL instance, I installed the latest version of Ubuntu. But then when I went to document what I had done, I discovered that I had already installed Ubuntu into WSL. I am irritated at myself.

The important thing is I am new at using Ubuntu on my Windows machine. I want to do some development in Ubuntu as well as continuing to do development in Windows. But I'm wondering if the two instances of Ubuntu will cause me problems? Should I remove the Ubuntu version from 2 years ago? And if so, how do I do that?

Has anyone successfully used (1) an Intel PC running Ubuntu 24.04, (2) with an installed VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller (rev 80) card, and (3) a Sony DCR-TRV120 Digital8 Handycam?

I just install a PCI FireWire controller to transfer Digital8 video tapes to my PC. After several attempts to follow posted advice, I continue to receive the message, Error: no camera exists. The Handycam appears to be fully operational and supported video control / transfer in the past (~15-20 years ago) using older PCs, but I am having no luck with my current PC. It seems like others have encountered similar issues, and I have not discovered root cause.

Has anyone been successful in configuring and using this type of FireWire device? If so, please share your findings.

I have audacity - at least that opens up. Instructions on Audacity website is for windows only

Tried via the app center Audio recorder (unoffical) = no work Recorder KDE = no work, screws up screen making it flickering and unreadable

Clean new install 24.04 updates done laptop is a HP17

Before I waste any more time trying the next program would anybody please tell me what works because so far I'm batting zero here.

I'm using Ubuntu 24.04 LTS and I want to install Node.js 22 using the official NodeSource repository instead of the default Ubuntu package. I tried installing Node.js using: sudo apt update sudo apt install nodejs However, it installs an older version than I need.

My questions are:

What is the recommended way to install Node.js 22 on Ubuntu 24.04? Should I use NodeSource or another official method? How can I keep Node.js updated in the future? Is there any risk of conflicting with Ubuntu packages?

I have searched the Ubuntu documentation and several online guides, but I'm looking for the recommended approach from experienced Ubuntu users.

Bellow is the issue I am getting while installing packages using snap example Firefox is mention bellow. Can someone help me in this? is it related to organization certificate or Ubuntu?

PC info:

$ cat /etc/os-release 
PRETTY_NAME="Ubuntu 24.04.4 LTS"
NAME="Ubuntu"
VERSION_ID="24.04"
VERSION="24.04.4 LTS (Noble Numbat)"
VERSION_CODENAME=noble
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=noble
LOGO=ubuntu-logo

Example for firefox:

$ sudo apt-get install firefox
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
  firefox
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 77.3 kB of archives.
After this operation, 124 kB of additional disk space will be used.
Get:1 http://in.archive.ubuntu.com/ubuntu noble/main amd64 firefox amd64 1:1snap1-0ubuntu5 [77.3 kB]
Fetched 77.3 kB in 2s (40.4 kB/s)                      
Preconfiguring packages ...
(Reading database ... 226140 files and directories currently installed.)
Preparing to unpack .../firefox_1%3a1snap1-0ubuntu5_amd64.deb ...
=> Installing the firefox snap
==> Checking connectivity with the snap store
==> Installing the firefox snap
error: cannot perform the following tasks:
- Download snap "firefox" (8664) from channel "stable" (Get "https://canonical-bos01.cdn.snapcraftcontent.com/download-origin/canonical-lgw01/3wdHCAVyZEmYsCMFDE9qt92UV8rC8Wdk_8664.snap?interactive=1&token=1784829600_9662e0a160c85459a623a3f0789f9d939ffc92c5": tls: failed to verify certificate: x509: certificate signed by unknown authority)
dpkg: error processing archive /var/cache/apt/archives/firefox_1%3a1snap1-0ubuntu5_amd64.deb (--unpack):
 new firefox package pre-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 /var/cache/apt/archives/firefox_1%3a1snap1-0ubuntu5_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

After installing Ubuntu 26.04 in Asus Expertbook Ultra (X7 385H) why getting problem in some function keys. Like brightness increase / decrease, fingerprint option not showing in settings, and IR facial recognition login option is not working.

Ubuntu 26.04 Freezes After Playing or Exiting Friday Night Funkin

System Information

Operating System: Ubuntu 26.04 LTS Laptop: HP EliteBook 845 G8 CPU: AMD Ryzen Processor GPU: AMD Radeon Vega 7 (Integrated Graphics)

Issue Description

I'm experiencing a system freeze whenever I play Friday Night Funkin. The game itself appears to run normally while playing, but after exiting the game—or sometimes shortly after gameplay—the entire desktop becomes unresponsive.

The freeze affects the whole graphical session, making the system unusable until I force a reboot.

The desktop freezes after playing or exiting Friday Night Funkin. The display becomes unresponsive. A forced reboot is usually required to recover the system.

Hardware Information

Device: HP EliteBook 845 G8 Graphics: AMD Radeon Vega 7 (Integrated)

Possible Cause

Since the issue only occurs after running the game, I suspect it may be related to:

Wayland or X11 display server compatibility GPU reset or display rendering issue triggered after the game exits

However, I'm not certain whether this is a graphics driver problem, a Mesa bug, or an issue specific to Friday Night Funkin'.

Troubleshooting Request

Has anyone experienced a similar issue with AMD integrated graphics on Ubuntu?

I would appreciate guidance on:

How to identify whether the problem is caused by AMDGPU, Mesa, Wayland, or the game itself. Which log files or diagnostic commands should I check. Whether there are any known compatibility issues between Ubuntu 26.04 and AMD Radeon Vega 7 when running Friday Night Funkin'. Any recommended fixes or workarounds to prevent the desktop from freezing after exiting the game.

Any suggestions or debugging steps would be greatly appreciated. Thank you!

Among snap folders in 26.04LTS x64 Desktop there are 116 files which have the text \x2d embedded in their names - why? ordinary bash utilities such as tar and stat are having trouble with these files, in a backup utility I am writing.

Why embed a backslash code in a pathname?

My Problem is that a group of files is revealed by ls as below (listA).

/etc/systemd/system/snap-gnome\x2d46\\x2d2404-153.mount
/etc/systemd/system/snap-gtk\x2dcommon\\x2dthemes-1535.mount
/etc/systemd/system/snap-desktop\x2dsecurity\\x2dcenter-151.mount
/etc/systemd/system/snap-firmware\x2dupdater-226.mount"
/etc/systemd/system/snap-mesa\x2d2404-1165.mount"

I am using tar to generate lists of files to be used in creating backups (Full and differential) and when it lists the above files it adds a backslash to each occurrence of \x2d and when a copy is tried using the modfied path the following error is generated (listB)

cannot STAT "/etc/systemd/system/snap-gnome\\x2d46\\x2d2404-153.mount"
cannot STAT "/etc/systemd/system/snap-gtk\\x2dcommon\\x2dthemes-1535.mount"
cannot STAT "/etc/systemd/system/snap-desktop\\x2dsecurity\\x2dcenter-151.mount"
cannot STAT "/etc/systemd/system/snap-firmware\\x2dupdater-226.mount"
cannot STAT "/etc/systemd/system/snap-mesa\\x2d2404-1165.mount"

It's not a big problem. I can write a small C filter to correct the sequences. I'm just puzzled as to why the hell was the sequence used at all when - would have done the job and created no problems?

And I'm posting a query on the offchance that I'm highlighting a problem no one else has commentsed on.

The only difference between current/selected/highlighted icons in the Alt+Tab switcher is only few percent of gray intensity for background color, which is only visible under ideal lighting condition. If I use any of my 2 laptops in a bright environment with a screen positioned at a slight angle (to reduce glare) then there is no way to see which application is selected/highlighted in the Alt+Tab switcher window. This looks the same on Ubuntu 24 and 26, with Light or Dark theme selected, with high contrast accessibility setting enabled or disabled.

In a screenshot, I see that switcher background color is 34,34,34, while selected background is 74,74,74: (74-34)/255 = 15% If I enable high contrast accessibility setting, then selected background is 94,94,94: (94-34)/255 == 24% So, the difference between high contrast a low contrast is only 9% and it is in the dark part of the spectrum, which only owls can see well, not humans.

My problem is not just with yaru, which unfortunaterly uses close to 50 shades of gray to represent states of objects and it is impossible for human eye to see so many shades, but with gnome/ubuntu, which makes it super hard to modify that setting. I wasted days begging ChatGpt and Claude to give me instructions on how to change that and all I got was one hallucination after another, some of them prevented system from loading and requiring reinstall.

Finally, with help from Claude, I came up with the following procedure, which works:

# On the first run make backup of the original resource
RESOURCE=/usr/share/gnome-shell/theme/Yaru/gnome-shell-theme.gresource
RESOURCE_ORIG=${RESOURCE}.bak # Original
if [ ! -e ${RESOURCE_ORIG} ]; then
  echo "sudo cp ${RESOURCE} ${RESOURCE_ORIG}"
  sudo cp ${RESOURCE} ${RESOURCE_ORIG}
fi

WORK_DIR=~/temp
mkdir -p ${WORK_DIR}
rm -rf ${WORK_DIR}/*
cd ${WORK_DIR}

# Extract original resource to ~/temp directory
while IFS= read -r gpath; do
    local_rel="${gpath#/org/gnome/shell/theme/}"   # strip prefix
    mkdir -p "${WORK_DIR}/$(dirname "$local_rel")"
    gresource extract "${RESOURCE_ORIG}" "$gpath" > "${WORK_DIR}/$local_rel"
done < <(gresource list "${RESOURCE_ORIG}")

# Patch several "background-color" items under various "switcher-list" elemwnts, not clear which of them are really used
BACKGROUND="rgba(255, 255, 255, 1.0)"
PATCH_CSS=("gnome-shell-dark.css" "gnome-shell.css")
for css in "${PATCH_CSS[@]}"; do
    f="${WORK_DIR}/Yaru/$css"
    sed -i '/\.switcher-list \.item-box:selected {/{n;s/background-color: [^;]*;/background-color: '"$BACKGROUND"';/}' "${f}"
    sed -i '/\.switcher-list \.item-box:highlighted/{n;n;s/background-color: [^;]*;/background-color: '"$BACKGROUND"';/}' "${f}"
    sed -i '/\.switcher-list \.item-box:highlighted/{n;s/background-color: [^;]*;/background-color: '"$BACKGROUND"';/}' "${f}"
done

{
    echo '<?xml version="1.0" encoding="UTF-8"?>'
    echo '<gresources><gresource prefix="/org/gnome/shell/theme">'
    find "${WORK_DIR}" -type f | sort | while read -r f; do
        echo "  <file>${f#${WORK_DIR}/}</file>"
    done
    echo '</gresource></gresources>'
} > "${WORK_DIR}/theme.gresource.xml"

# Compile
(cd "${WORK_DIR}" && glib-compile-resources theme.gresource.xml)

# Deploy
sudo cp "${WORK_DIR}/theme.gresource" "${RESOURCE}"

# Reboot (or re-login)
sudo reboot

This works:

But it cannot be so complex!

Also, Claude suggested that there should be a way to modify the Yary theme locally instead of system level, but so far I did not get working instructions.

Is there a better way? Any suggestions?

(By the way, Windows simply paints a thin white rectangle around the selected icon, which is always perfectly visible).

Thank you

I also posted this question at https://github.com/ubuntu/yaru/issues/4477

My System

1. version of Ubuntu 24.04.4 LTS

2. GPU hardware name/model: GeForce GTX 1060 6GB

Because the screen size is 640x480 I can only see partial dialogs. Dialogs with interactive buttons are off screen. There is no known (to me) method to views dialogs that require a space larger than 640x480 pixels.

At the time when the screen size got stuck at 640x480 I was NOT updating anything. I was only using the computer in normal ways that users use computers.

At the time when the screen size got stuck at 640x480 I had unusual problems with my external USB drive not functioning correctly and acting weird. This led to rebooting my Ubuntu machine. This is when the resolution got stuck at 640x480.

At the time when the screen size got stuck at 649x480 I tried updating my Ubuntu machine thinking this may fix the problem. Things got worse. The updater couldn't accomplish certain things and gave errors. Due to the above condition I am unable to describe what these problems were for lack of visuals (i.e. dialogs off the screen).

I'd rather not reformat the entire system - but this may be the only option.

UPDATE 1:

After reading random solutions on the internet I have this really bad feeling that it's 100% impossible for me to fix this. If my system has recently updated to something absolutely incompatible with my GPU card then I guess I'm just hosed. There's no way I'll be able to "hack" a driver as others have suggested.

This is why I've always been against upgrades - especially when nothing was broken to begin with. At the very least there should be some method to roll back to the previous state if some problem like this were to occur.

EDIT 1 & 2 - (A) added Ubuntu version (B) added descriptive text. (C) deleted a paragraph (D) Deleted and added text at top

EDIT 3

I believe I have the Desktop version of Ubuntu - it just says Ubuntu 24.04.4 LTS with no mention about kernels. I installed the original Desktop version in January of 2026 using a bootable USB. Therefore, the version was likely version 22 (or close to that version).

I wasn't updating (yesterday) when the resolution got stuck at 640x480. Although it is possible that one or two or three or seven days ago I updated. I just don't know. But my machine was in high resolution mode when I booted it - it was only after rebooting (yesterday) that the resolution issue showed up. Regarding Updates: although I wasn't updating anything yesterday I began updating to try to fix the sudden resolution problem. Updating failed. I got error messages. I tried a partial update. I guess that worked. (except for the resolution).

I ran the following command to see if there were NVIDIA errors:

Sudo dmesg

I saved the above output to a text file, then searched for things like “error” – and found nothing. The output text is lengthy. The copy is on my MacBook). I am hesitant to post all this data online (it is lengthy). Therefore, it would be helpful if I had some idea what to look for.

I copied the dpkg.log file (to my MacBook). This should have information on system updates. Which there are because I deleted all NVIDIA stuff and then ran an update to force an update (this procedure is online somewhere). But there was an update prior to this (which was failing for some reason). Again, what should I look for here?

I created a bootable USB with Ubuntu 22.04.5 on it and observed that I could achieve a default resolution of 1080x1920 (and higher). I used the “Try Ubuntu” menu item (which is neat). I got the ISO from here: https://releases.ubuntu.com/jammy/

Prior to creating the above bootable USB I did the same, but using Ubuntu 26.04 for the bootable USB (the latest as of today’s date). I got this ISO from here: https://ubuntu.com/download/desktop This didn't work. I got the following error so I killed it

Ubuntu 26.04 [ 27.969569] Novacore0000:03:00.0 Unsupported chipset: boot42 = 0x136a1000 (architecture 0x13, implementation 0x6)

That's all I have for now - as of July 24, 2026.

Reinstalling an Ubuntu version that works for my NVIDA card is likely the most efficient. Long distance computer forensics will take years (sarcasm) to find the root problem. But, I think everybody already knows what the problem is. Ubuntu doesn't work with my graphics card. Pretty simple.

I now know that Ubuntu 22.04.5 works.

I am running Ubuntu release 22.04.5 Jammy Jellyfish.
When I connect the USB cables to my desktop, they do not see my Galaxy A16 5G phone?

How can that be repaired?

I have used 4 different cables. It ain't the cable.

Any out of the box thinkers ?

dmesg -W output:

[8354.516445] usb 1-5: new high-speed USB device number 12 using ehci -printer new USB device found, idVendor=04e8, idProduct=6860, bcdDevice= 5.04 Product:SAMSUNG_Android SerialNumber: RZCYA1MSBLV cdc_acm 1-5:1.1 ttyACM0: USB ACM device

After a routine fwupd firmware update my laptop's built-in screen became very dim, even at "100%" brightness. An external monitor on the same machine looks completely normal.

• Laptop: Dell Latitude 5430, Intel Iris Xe (Alder Lake, i915), internal eDP panel (AU Optronics).

• OS: Ubuntu 24.04, GNOME.

• Trigger: fwupd auto-flashed the Dell system BIOS from 1.36.0 to 1.39.1 (check with fwupdmgr get-history). The screen was fine before that.

What I already ruled out (none of these help):

• Not a kernel regression — dim on every kernel I tried; the panel is only bright in recovery mode / with nomodeset (i.e. when i915 is not driving it).

• Not gamma/ICC — xrandr Brightness 1.0, Gamma 1.0, no VCGT in the ICC profile.

• Not a software brightness slider — /sys/class/backlight/intel_backlight reports brightness == actual_brightness == max_brightness (1023), yet the panel is dim.

• Brightness keys only make it dimmer, never brighter.

• Downgrading the BIOS is blocked: LVFS only offers 1.39.1, so fwupdmgr / GNOME Firmware cannot roll back.

How do I get the panel bright again without a BIOS downgrade?

My professional laptop Dell Precision is under Noble 24.04 installed after delivery (delivered under Jammy).

I am french so I used fr (bepo) keyboard layout.

I stay with X11 to use Gimp, have no issue with web-conferencing app …

Early may

I still had kernel update (6.17.0-22) that switched me under wayland and qwerty keyboard layout, I run in CLI: setxkbmap fr bepo that returns me: WARNING: Running setxkbmap against an Xwayland server, I swithed back to kernel 6.17.0-20 and X11.

This morning (17th jully)

After a first use, my laptop locked up after being idle for a while, then when I entered my password, I can't connect… it switched to qwerty. I also connect to the docking station to have external screen, but it stayed black, no external screen detected in display parameters. I had no more wifi connection, I should connect by cable.

I didn't find under grub connection to switch back to X11, so I switched in /etc/gdm3/custom.conf the WaylandEnable=false, but if I switch with success to X11, I still had no wifi, external screen.

I've been trying to get my UB600 Bluetooth dongle to work, however it seems that it's not compatible out of the box. In fact, there's only 1 place with a solution how to get it to work however it seems the explanation on how to do it goes over my head. I've tried using what they gave me in konsole but some things just error and I can't seem to get around that. The fix I've been attempting is this. The issue I'm having is, it detects the Bluetooth dongle, but the computer is then unable to detect any Bluetooth devices at all. The lsusb is exactly as shown on that link as is the journalctl.

Results of lsusb | grep -i 'tp-link':

Bus 001 Device 012: ID 37ad:0600  TP-Link Bluetooth USB Adapter

Results of journalctl:

usb 1-1: new full-speed USB device number 12 using xhci_hcd
usb 1-1: New USB device found, idVendor=37ad, idProduct=0600, bcdDevice= 2.00
usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-1: Product: TP-Link Bluetooth USB Adapter
usb 1-1: Manufacturer:
usb 1-1: SerialNumber: 18694530DB8B
Bluetooth: MGMT ver 1.23

I ran sudo dmesg | grep -i bluetooth and got this:

server@server-z87hd3:~$ sudo dmesg | grep -i bluetooth
[sudo] password for server: 
[647887.635955] usb 1-1: Product: TP-Link Bluetooth USB Adapter
[647887.709668] Bluetooth: MGMT ver 1.23
[648046.220743] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761
[648046.221733] Bluetooth: hci0: RTL: rom_version status=0 version=1
[648046.222744] Bluetooth: hci0: RTL: btrtl_initialize: key id 0
[648046.222748] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin
[648046.224331] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin
[648046.224378] Bluetooth: hci0: RTL: cfg_sz 6, total sz 30210
[648046.376751] Bluetooth: hci0: RTL: fw version 0xdfc6d922
[648046.443866] Bluetooth: MGMT ver 1.23
[648062.029928] usb 1-1: Product: TP-Link Bluetooth USB Adapter
[648062.105001] Bluetooth: MGMT ver 1.23
[648220.950989] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761
[648220.951983] Bluetooth: hci0: RTL: rom_version status=0 version=1
[648220.952966] Bluetooth: hci0: RTL: btrtl_initialize: key id 0
[648220.952969] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin
[648220.953197] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin
[648220.953223] Bluetooth: hci0: RTL: cfg_sz 6, total sz 30210
[648221.105982] Bluetooth: hci0: RTL: fw version 0xdfc6d922
[648221.173128] Bluetooth: MGMT ver 1.23
[648256.225222] usb 1-1: Product: TP-Link Bluetooth USB Adapter
[648256.298247] Bluetooth: MGMT ver 1.23
[649742.374342] Bluetooth: MGMT ver 1.23
[682771.713073] usb 1-1: Product: TP-Link Bluetooth USB Adapter
[682771.785356] Bluetooth: MGMT ver 1.23

Is there any chance somebody could explain to me like I'm a 5 year old how to apply that patch, or better yet, create a solution for me? I am running Kubuntu 26.04 on kernel 7.0.0-27-27.

Edit: Following "david" in the comments advice results.

server@server-z87hd3:~$ sudo apt install bluetooth bluez -y
[sudo: authenticate] Password:       
bluez is already the newest version (5.85-4ubuntu0.1).
bluez set to manually installed.
Installing:                 
  bluetooth

Suggested packages:
  bluez-meshd

Summary:
  Upgrading: 0, Installing: 1, Removing: 0, Not Upgrading: 3
  Download size: 6,600 B
  Space needed: 36.9 kB / 180 GB available

Get:1 http://archive.ubuntu.com/ubuntu resolute-updates/universe amd64 bluetooth all 5.85-4ubuntu0.1 [6,600 B]
Fetched 6,600 B in 0s (121 kB/s)      
Selecting previously unselected package bluetooth.
(Reading database… 268329 files and directories currently installed.)
Preparing to unpack …/bluetooth_5.85-4ubuntu0.1_all.deb…
Unpacking bluetooth (5.85-4ubuntu0.1)…
Setting up bluetooth (5.85-4ubuntu0.1)…
server@server-z87hd3:~$ sudo systemctl start bluetooth
server@server-z87hd3:~$ sudo systemctl enable bluetooth
Synchronizing state of bluetooth.service with SysV service script with /usr/lib/systemd/systemd-sysv-install.
Executing: /usr/lib/systemd/systemd-sysv-install enable bluetooth
server@server-z87hd3:~$ bluetoothctl show | grep "Powered"
        Powered: yes
server@server-z87hd3:~$ bluetoothctl
[NEW] Media /org/bluez/hci1 
        SupportedUUIDs: 0000110a-0000-1000-8000-00805f9b34fb
        SupportedUUIDs: 0000110b-0000-1000-8000-00805f9b34fb
Agent registered
[CHG] Controller 18:69:45:30:DB:8B Discovering: yes
[bluetoothctl]> power on#
Invalid argument on#
[bluetoothctl]> power on
Changing power on succeeded
[bluetoothctl]> agent on
Agent is already registered
[bluetoothctl]> default-agent
Default agent request successful
[bluetoothctl]> discoverable on
hci1 new_settings: powered connectable bondable ssp br/edr le secure-conn ll-privacy 
[CHG] Controller 18:69:45:30:DB:8B Connectable: yes
hci1 new_settings: powered connectable discoverable bondable ssp br/edr le secure-conn ll-privacy 
Changing discoverable on succeeded
[CHG] Controller 18:69:45:30:DB:8B Discoverable: yes
[bluetoothctl]> pairable on
Changing pairable on succeeded
[bluetoothctl]> scan on
SetDiscoveryFilter success
Discovery started
[bluetoothctl]> 

Given a local package name, I would like to open the corresponding Launchpad project in the browser. apport-bug supports this, but requires first filing a bug. I would like to go on Launchpad to read the changelog or search for duplicate bugs.

My current manual workflow is this: Retrieve the package name from dpkg -S /path or apt list --upgradable. Convert to a project name if dpkg -s packagename has a Source: line. Manually type in https://launchpad.net/ubuntu/+source/projectname in Firefox.

I would like mycommand subcommand [pid | packagename | program path] to automatically open that one Launchpad page. Launchpad sometimes takes a few seconds to load, so I don't want to need to visit multiple Launchpad pages. Is there a built-in command that supports this?

Furthermore, the Launchpad.net search feature suggested by @user1898883 is broken. https://launchpad.net/+search?field.text=aspnetcore-runtime-10.0 and https://launchpad.net/+search?field.text=dotnet10&field.actions.search=Search both return the unrelated https://bugs.launchpad.net/bugs/10 and https://answers.launchpad.net/ubuntu/+question/10 .

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

I connect to the internet at public sites, usually my local library, which involves a network login page.

My problem is that before that can happen, the network xfinity often hijacks the login process by connecting itself to my laptop.

How can I permanently ban xfinity network from connecting to me. I use Network Manager on Lubuntu 24.04

I have problems with the Bluetooth adapter on Ubuntu 22.04. When turned on from the distribution interface, it immediately turns off.

Results of lsusb | grep -i bluetooth:

Bus 003 Device 003: ID 0bda:a728 Realtek Semiconductor Corp. Bluetooth 5.4 Radio

Results of hciconfig -a:

hci0:   Type: Primary  Bus: USB
    BD Address: 00:E0:43:61:90:F6  ACL MTU: 1021:6  SCO MTU: 255:12
    DOWN 
    RX bytes:15375 acl:0 sco:0 events:1116 errors:0
    TX bytes:47520 acl:0 sco:0 commands:1116 errors:0
    Features: 0xff 0xff 0xff 0xfe 0xdb 0xfd 0x7b 0x87
    Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
    Link policy: RSWITCH HOLD SNIFF PARK 
    Link mode: PERIPHERAL ACCEPT 

Results of dmesg | grep -i bluetooth:

[    1.904005] usb 3-10: Product: Bluetooth 5.4 Radio
[    8.691251] Bluetooth: Core ver 2.22
[    8.691292] NET: Registered PF_BLUETOOTH protocol family
[    8.691294] Bluetooth: HCI device and connection manager initialized
[    8.691297] Bluetooth: HCI socket layer initialized
[    8.691300] Bluetooth: L2CAP socket layer initialized
[    8.691305] Bluetooth: SCO socket layer initialized
[    8.969085] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761
[    8.970384] Bluetooth: hci0: RTL: rom_version status=0 version=1
[    8.970390] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin
[    8.971750] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin
[    8.972052] Bluetooth: hci0: RTL: cfg_sz 6, total sz 30210
[    9.139845] Bluetooth: hci0: RTL: fw version 0xdfc6d922
[   10.142665] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   10.142670] Bluetooth: BNEP filters: protocol multicast
[   10.142674] Bluetooth: BNEP socket layer initialized
[   10.143916] Bluetooth: MGMT ver 1.22
[   15.868987] Bluetooth: RFCOMM TTY layer initialized
[   15.868994] Bluetooth: RFCOMM socket layer initialized
[   15.868999] Bluetooth: RFCOMM ver 1.11
[   20.472187] Bluetooth: hci0: Opcode 0x2037 failed: -112

Results of dmesg | grep -i hci:

[    0.309077] ehci-pci 0000:00:1a.0: EHCI Host Controller
[    0.309083] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
[    0.309099] ehci-pci 0000:00:1a.0: debug port 2
[    0.313023] ehci-pci 0000:00:1a.0: irq 20, io mem 0xf7d1c000
[    0.319250] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
[    0.319330] usb usb1: Product: EHCI Host Controller
[    0.319331] usb usb1: Manufacturer: Linux 6.8.0-79-generic ehci_hcd
[    0.319659] ehci-pci 0000:00:1d.0: EHCI Host Controller
[    0.319666] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
[    0.319688] ehci-pci 0000:00:1d.0: debug port 2
[    0.323614] ehci-pci 0000:00:1d.0: irq 23, io mem 0xf7d1b000
[    0.330243] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
[    0.330297] usb usb2: Product: EHCI Host Controller
[    0.330298] usb usb2: Manufacturer: Linux 6.8.0-79-generic ehci_hcd
[    0.560251] usb 1-1: new high-speed USB device number 2 using ehci-pci
[    0.568248] usb 2-1: new high-speed USB device number 2 using ehci-pci
[    1.055719] xhci_hcd 0000:00:14.0: xHCI Host Controller
[    1.055726] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 3
[    1.057127] xhci_hcd 0000:00:14.0: hcc params 0x200077c1 hci version 0x100 quirks 0x0000000000009810
[    1.057874] xhci_hcd 0000:00:14.0: xHCI Host Controller
[    1.057879] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 4
[    1.057882] xhci_hcd 0000:00:14.0: Host supports USB 3.0 SuperSpeed
[    1.059440] usb usb3: Product: xHCI Host Controller
[    1.059441] usb usb3: Manufacturer: Linux 6.8.0-79-generic xhci-hcd
[    1.061597] ahci 0000:00:1f.2: version 3.0
[    1.062654] ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 6 Gbps 0x23 impl SATA mode
[    1.062659] ahci 0000:00:1f.2: flags: 64bit ncq led clo pio slum part ems apst 
[    1.077359] scsi host0: ahci
[    1.077793] usb usb4: Product: xHCI Host Controller
[    1.077794] usb usb4: Manufacturer: Linux 6.8.0-79-generic xhci-hcd
[    1.089140] scsi host1: ahci
[    1.108386] scsi host2: ahci
[    1.120202] scsi host3: ahci
[    1.127799] scsi host4: ahci
[    1.137641] scsi host5: ahci
[    1.530932] usb 3-9: new low-speed USB device number 2 using xhci_hcd
[    1.776225] usb 3-10: new full-speed USB device number 3 using xhci_hcd
[    8.691294] Bluetooth: HCI device and connection manager initialized
[    8.691297] Bluetooth: HCI socket layer initialized
[    8.969085] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761
[    8.970384] Bluetooth: hci0: RTL: rom_version status=0 version=1
[    8.970390] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin
[    8.971750] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin
[    8.972052] Bluetooth: hci0: RTL: cfg_sz 6, total sz 30210
[    9.139845] Bluetooth: hci0: RTL: fw version 0xdfc6d922
[   20.472187] Bluetooth: hci0: Opcode 0x2037 failed: -112

I have bought a Dell Latitude 7450-165 H laptop and the camera is not detecting initially. And I performed the below steps and they are detecing the camera, but after that, I get a black screen not giving any images.

1. sudo add-apt-repository ppa:oem-solutions-engineers/oem-projects-meta
2. sudo apt install oem-somerville-tentacool-meta
3. sudo apt update
4. sudo apt full-upgrade
5. sudo systemctl poweroff

Could someone please help me here...

After the update from 22.04 to 24.04 I get this message when connecting to ghost VPN. I check and see my IP location has not changed.

System-Product-Name:~$ sudo cyberghostvpn --traffic --country-code US --connect
Prepare OpenVPN connection ...
Select server ... sanfrancisco-s404-i11
Connecting ... 
Downloading configuration ...

I reran System-Product-Name:~$ sudo cyberghostvpn --setup. Nothing changed after the command.

I am using Ubuntu 24.04 with English and Japanese keyboards: gsettings get org.gnome.desktop.input-sources sources gives [('xkb', 'us'), ('ibus', 'mozc-jp')].

The Japanese layout can input roman letters (capital A sign is in top-right corner of the screen); or hiragana (hiragana あ is displayed in top-right corner).

The problem is, that while I can reliably switch with super + space from English to Japanese, I can only switch back, if the Japanese layout is set to roman letters. Switching back from hiragana to English occasionally might work, but usually does not.

In a terminal screen, having hiragana active, the combination super+space almost always results in a space (that is: as if the super key were ignored completely).

I might have read somewhere that "this has to do something with 2-byte character encoding", but I can't seem to find the source right now. This was not an issue prior with Ubuntu 22.04.

I have my laptop and Two monitors. I just want to use my two monitors as two separate displays, and don't care about my laptop. Under Settings -> Displays, when I select Join Display, I would have my laptop as display1 and two monitors as display2, so I can not use two monitors as two separate displays. Any Suggestion?

I am currently trying to install Lubuntu 20.04.2 LTS on a low-spec laptop (2 GB RAM, 30 GB SSD). I am finding the partition stage quite tricky to get it to work, as it keeps complaining about the EFI partition. The instructions in the Lubuntu installation manual are lacking in detail and all of the Q's & A's on this site and elsewhere on the web do not tell me what I need to know to get it working. After some trial and error, I came up with the following, which allowed me to get Lubuntu installed but is still wrong because /boot is FAT32 so fails on kernel upgrades:

As I say, the above installed but then failed on kernel upgrade.

I am currently trying the same as above but with /boot as ext4. But I'm still asking this question as it may or may not work and even the above might help some people.

So, questions:

1. The above is done with MBR partition table rather than GPT. Is that OK?

2. Is it necessary to have separate /boot, /boot/efi and / partitions? I would happily just have swap and / but the installer complains about efi so fair enough I can add /boot/efi but do I really need /boot as well? From trial and error it looks like maybe yes but I would rather do without it if possible.

3. Are the above file system types and flags correct (with /boot changed to ext4)? Just because the trial and error feedback loop is slow.

Thanks

I am very new to Ubuntu and I just installed Ubuntu 20.04 LTS today and trying to setup XRDP so that I can remote -in into my Ubuntu machine from Windows I executed the following steps:

sudo apt install xrdp 

I then tried all of these but only one at-a-time

sudo apt-get install kde-full
sudo apt-get install kde-desktop
sudo apt-get install kde-standard
sudo apt-get install kde-plasma-desktop

echo "startkde"  > ~/.xsession


sudo systemctl restart xrdp

when I try to connect, I get the login screen from xrdp and I select xorg and enter my username and password. But then RDP session ends immediately

Can someone please help me set up XRDP and figure out what might be the issue? I can't stand gnome desktop. I would like to have KDE with XRDP.

Thanks

I am doing documentation with rst about my Python project. When using Pycharm I get errors so I tried using another viewer.

I tried restview but had the same problem.

After some reasearch I found my problem here. Apparently is because Sphinx is something apart. So I just need a viewer to render my rst files LOCALLY.

I found sphinx-view but I believe is not working for the moment as I get the error:

sphinx.errors.ApplicationError: Source directory and destination directory cannot be identical

Which I believe has to do with this

I have a problem with Ubuntu 14.04. Suddenly, my second monitor isn't detected on Ubuntu. It worked fine before. When i try using Windows 7, it is detected. I'm using HP Pavilion G4 1212tx AMD ATI Radeon.

Why isn't it detected? Is there a problem with my VGA card?

I'm quite new to Ubuntu and want to create a backup. I'm really not sure what files and folders to include so that if I restore my system it will be as it is now. I can't seem to find good details of this anywhere. Hopefully someone could help me with this. Is it possible to backup everything as it is now so in the event of a system restore I don't have to reinstall programs and settings?

I have one speaker next to my computer which I use mostly as a headphone amplifier. On occasion I need to use it as a loudspeaker. Is it possible to quickly change the audio output from stereo to mono, either system-wide or as a plugin for a media player?