I recently installed Ubuntu on my old Samsung laptop. The laptop is connected to the internet OK via WiFi, and the laptop was perfectly fine with browsing the web before I installed Ubuntu. After installing Ubuntu I cannot access the internet at all using the laptop with no connection either through Firefox or through the built-in App Center.
This should be an easy one - but, how can I put different backgrounds on each 'joined' monitor/display?
Unit apache2.services could not be found
I have tried to get past this but it is a result of
Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages
how to fix all of this?
In any operating system I know, I can select text in the following way:
This does not work on my Ubuntu 25.10 machine (the cursor is repositioned, but the text is not selected). And as far as I'm aware of I have not set any special configuration for my keyboard or my mouse.
Is this the standard behaviour of Ubuntu? What can I do to change it?
Edit: This behaviour is not application specific – it is the same with Firefox, LibreOffice, VSCode, the default Ubuntu text editor and other applications.
Flatpak apps do not seem to be working properly on my Ubuntu 24.04 system.
I encrypted my Home directory using ecryptfs.
I installed flatpak from ubuntu's official repositories via sudo apt install flatpak, and followed all the setup steps described in flathub's guide for ubuntu (link: https://flathub.org/en/setup/Ubuntu). This installs flatpak version 1.14.6-1ubuntu0.1 .
I then proceeded to install flatpak apps from flathub's repository.
I am especially interested in the Pika Backup app, so I will focus on that. I tested a couple of other flatpak apps from flathub (such as Deja Dup and a game app called "muttum" just for the purpose of testing) and they display a similar behaviour, so it seems like a general problem with flatpak on ubuntu, at least on my system.
I installed the Pika Backup app via the command line with the command flatpak install flathub org.gnome.World.PikaBackup, as described in the flathub website (link: https://flathub.org/en/apps/org.gnome.World.PikaBackup).
However, the app does not launch either from Ubuntu's apps menu or from the command line (via the command flatpak run org.gnome.World.PikaBackup). The command displays the following error message:
error: mkdir(/home/uat/.var): Permission denied
When running the same command with the verbose option it gives the following output:
flatpak -v run org.gnome.World.PikaBackup
F: No installations directory in /etc/flatpak/installations.d. Skipping
F: Opening system flatpak installation at path /var/lib/flatpak
F: Opening user flatpak installation at path /home/uat/.local/share/flatpak
F: Opening user flatpak installation at path /home/uat/.local/share/flatpak
F: Opening system flatpak installation at path /var/lib/flatpak
F: Skipping parental controls check for app/org.gnome.World.PikaBackup/x86_64/stable since parental controls are disabled globally
F: Opening user flatpak installation at path /home/uat/.local/share/flatpak
F: Opening system flatpak installation at path /var/lib/flatpak
error: mkdir(/home/uat/.var): Permission denied
Trying the command with sudo: sudo flatpak run org.gnome.World.PikaBackup as a work-around gives the following output:
error: "flatpak run" is not intended to be run as `sudo flatpak run`.
Use `sudo -i` or `su -l` instead and invoke "flatpak run"
from inside the new shell.
I tried to run the program with sudo -i, followed by the same command flatpak run org.gnome.World.PikaBackup (even though I think it should have worked without sudo permissions, but for the purpose of troubleshooting I follow along). This way the app's graphical interface is launched, however it seems to not be working properly yet. For instance, when I try to select a folder for a new backup repository it opens a dialog box with the following message and does not proceed:
The session bus is not available
Does anyone have experience with working with flatpak apps on Ubuntu? If so, did you setup it differently from what is described in flathub's guide (https://flathub.org/en/setup/Ubuntu)? And do you need sudo permissions to run flatpak apps?
Some apps are only available as flatpaks, so it would be an important addition to my Ubuntu system. Otherwise, I might have to look into other alternative Linux operating systems which support flatpaks.
Thanks in advance!
namei -l ~/.var output:
f: /home/uat/.var~
drwxr-xr-x root root /
drwxr-xr-x root root home
dr-x------ uat uat uat
.var~ - No such file or directory
findmnt -T ~/ output:
TARGET SOURCE FSTYPE OPTIONS
/home/uat
/home/uat/.Private
ecrypt rw,nosuid,nodev,relatime,ecryptfs_fnek_sig=...
grep -r flatpak /etc/apparmor.d/ output:
/etc/apparmor.d/flatpak:profile flatpak /usr/bin/flatpak flags=(unconfined) {
/etc/apparmor.d/flatpak: include if exists <local/flatpak>
/etc/apparmor.d/usr.bin.evince: owner @{HOME}/.local/share/{,flatpak/exports/share/}mime/** r,
/etc/apparmor.d/usr.bin.evince: owner @{HOME}/.local/share/{,flatpak/exports/share/}mime/** r,
/etc/apparmor.d/tunables/share:@{flatpak_exports_root} = {flatpak/exports,flatpak/{app,runtime}/*/*/*/*/export}
/etc/apparmor.d/tunables/share:@{system_share_dirs} = /{usr,usr/local,var/lib/@{flatpak_exports_root}}/share
/etc/apparmor.d/tunables/share:@{user_share_dirs} = @{HOME}/.local{,/share/@{flatpak_exports_root}}/share
I recently purchased a Lenovo Thinkpad E14 gen 7 Intel (255H) model 21SX005CMX preinstalled with Windows on it. I did a firmware update for the BIOS version to the latest version included on the website at the moment (BIOS R30ET35W(1.09)). After that I removed the windows installation and replaced it with Ubuntu 24.04.3 from a USB stick. Installation went fine until browsing and doing configuration. After a few hours the computer freezes. I troubleshot the problem and discovered that the ACPI EC (Embedded Controller) throws an error on boot in the journalctl logs. Then I realized the fans are not working.
I've tried to change the acpi_osi kernel parameter to Windows 2022, which didn't help. Is there any advice I could look into? The fans work fine in BIOS setup, so there's no problem with the fans themselves, just the ACPI embedded controller. I'll put in the logs below with the relevant parts I've found:
Linux version 6.14.0-32-generic (buildd@lcy02-amd64-047) (x86_64-linux-gnu-gcc-13 (Ubuntu 13.3.0> Command line: BOOT_IMAGE=/boot/vmlinuz-6.14.0-32-generic root=UUID=60a6c825-aaff-496c-a3fd-7f0d0>
kernel: ACPI: Added _OSI(Module Device)
kernel: ACPI: Added _OSI(Processor Device)
kernel: ACPI: Added _OSI(Processor Aggregator Device)
kernel: ACPI BIOS Error (bug): Failure creating named object [\_GPE.AL6F], AE_ALREADY_EXISTS (20240827/d>
kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
kernel: ACPI: Skipping parse of AML opcode: Method (0x0014)
kernel: ACPI BIOS Error (bug): Failure creating named object [\_GPE._L21], AE_ALREADY_EXISTS (20240827/d>
kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
kernel: ACPI Error: Unknown class in reference(00000000daf75d46) - 0x00 (20240827/exoparg1-1051)
kernel:
kernel:
Initialized Local Variables for Method [ECRD]:
kernel: Local0: 00000000d1314e91 <Obj> Integer 0000000000000000
kernel:
kernel: Initialized Arguments for Method [ECRD]: (1 arguments defined for method invocation)
kernel: Arg0: 00000000daf75d46 <Obj> Integer 00000000000000EF
kernel:
kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC.ECRD due to previous error (AE_TYPE) (20240827/psp>
kernel: thinkpad_acpi: acpi_evalf((null), dd, ...) failed: AE_TYPE
kernel: thinkpad_acpi: Thinkpad ACPI EC unable to access EC version
kernel: ACPI Error: Unknown class in reference(00000000d1314e91) - 0x00 (20240827/exoparg1-1051)
kernel:
kernel:
Initialized Local Variables for Method [ECRD]:
kernel: Local0: 0000000038c6824c <Obj> Integer 0000000000000000
kernel:
kernel: Initialized Arguments for Method [ECRD]: (1 arguments defined for method invocation)
kernel: Arg0: 00000000d1314e91 <Obj> Integer 0000000000000078
kernel:
kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC.ECRD due to previous error (AE_TYPE) (20240827/psp>
kernel: thinkpad_acpi: acpi_evalf((null), dd, ...) failed: AE_TYPE
kernel: thinkpad_acpi: ThinkPad ACPI EC access misbehaving, disabling thermal sensors access
kernel: EDAC MC1: Giving out device to module igen6_edac controller Intel_client_SoC MC#1: DEV 0000:00:0>
kernel: EDAC igen6: v2.5.1
mtp-probe[582]: checking bus 3, device 3: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-7"
kernel: pci 0000:00:14.2: enabling device (0000 -> 0002)
kernel: ACPI Error: Unknown class in reference(0000000092c4bcfb) - 0x00 (20240827/exoparg1-1051)
kernel:
kernel:
Initialized Local Variables for Method [ECRD]:
kernel: Local0: 000000004b6aae06 <Obj> Integer 0000000000000000
kernel:
kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC.ECRD due to previous error (AE_TYPE) (20240827/psp>
kernel: thinkpad_acpi: acpi_evalf((null), dd, ...) failed: AE_TYPE
kernel: thinkpad_acpi: Failed to unmute the HW mute switch
kernel: ACPI Error: Unknown class in reference(0000000092c4bcfb) - 0x00 (20240827/exoparg1-1051)
kernel:
kernel:
Initialized Local Variables for Method [ECRD]:
kernel: Local0: 000000004b6aae06 <Obj> Integer 0000000000000000
kernel:
kernel: Initialized Arguments for Method [ECRD]: (1 arguments defined for method invocation)
kernel: Arg0: 0000000092c4bcfb <Obj> Integer 000000000000002F
kernel:
kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC.ECRD due to previous error (AE_TYPE) (20240827/psp>
kernel: thinkpad_acpi: acpi_evalf((null), dd, ...) failed: AE_TYPE
kernel: thinkpad_acpi: ThinkPad ACPI EC access misbehaving, fan status and control unavailable
I am trying to install mailutils but I run into a message regarding broken packages:
The following packages have unmet dependencies:
libpython3.12t64 : Depends: libpython3.12-stdlib (= 3.12.3-1ubuntu0.5) but 3.12.4-1+focal1 is to be installed
E: Unable to correct problems, you have held broken packages.
Trying to remove libpython3.12-stdlib leads only to more error messages caused by held packages. Is there anything I can do to resolve this issue?
I'm working with a lubuntu 22.04 distribution. I need to execute the following command by a user without root privileges:
> nmcli c add ifname enp3s0 type ethernet con-name 'connection-test'
The output of the previous command is the following:
Error: Failed to add 'connection-test' connection: Insufficient privileges
I have added the user to the group netdev (used the command sudo adduser <username> netdev) as suggested by this post, but the problem is not solved. The post reports this sentences:
On Debian, the "netdev" group gains access to using Network Manager. On Ubuntu, Network Manager access rights are gained by being at the system console, so the name of this entry in gnome-system-tools is misleading.
The "netdev" group can administer wicd and wpasupplicant.
The "netdev" group can set the avahi host name using DBus.
The "netdev" group can administer Bluetooth devices.
This means that on Ubuntu the name of the group netdev is different?
Is it possible to be able for a not root user to execute the nmcli c add command without sudo?
This other post treats the same topic and suggests to create a service, executed with root privilege, which creates the NetworkManager connection.
I dual boot Windows 11 & Ubuntu 22.04, and right after I choose Ubuntu from the GRUB menu, I get the following errors:
integrity: Problem loading X.509 certificate -65
The above screen shows momentarily and Ubuntu seems to continue to boot fine regardless.
I was able to solve the one related to VMX by enabling VMX from my BIOS settings, whereas I wasn't able to find anything there related to SGX (I don't know if it's listed in my settings under a different alias), and I don't really know the meaning of the one related to "integrity".
Does anyone have an idea about the source of these errors, especially the "integrity" one?
I've decided to start using linux (because... why not?), so I went through all the installation process without any problem, the system ask for rebooting, so I let it does, but when the machine restarted, my screen started turning on and off twice and these boot messages appeared:
/dev/sda5: clean, 209401/29278208 files, 4174894/117081088 blocks
[ 12.581934] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERRO
R* [CRTC:45:pipe A] flip_done timed out
[ 22.821918] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:45:pipe A] flip_done timed out
[ 23.081937] i915 0000:00:02.0: [drm] *ERROR* failed to disable transcoder A
[ 23.180711] i915 0000:00:02.0: [drm] *ERROR* uncleared pch fifo underrun on pch transcoder A
[ 23.180718] i915 0000:00:02.0: [drm] *ERROR* PCH transcoder A FIFO underrun
Ubuntu doesn't boot, and it stays stuck at a black scree like this forever.
The screen I'm using is plugged in to my PC with an HDMI cable (the only common port between both of them). When I use another screen with VGA, Linux boots up nicely.
I've read that maybe the recent kernel could be the cause of the issue, but I also tried installing Ubuntu 18.04, and the error still appears.
I've also tried modifying the kernel's default grub command (in /etc/default/grub) by adding video=SVIDEO-1:d to the "DEFAULT" line.
My machine is a dell OptiPlex 390 with an i3 and no additional graphic card.
And the result of inxi -G is:
Graphics:
Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics
driver: i915 v: kernel
Display: x11 server: X.Org 1.20.11 driver: modesetting
unloaded: fbdev,vesa resolution: 1680x1050~60Hz
OpenGL: renderer: Mesa DRI Intel HD Graphics 2000 (SNB GT1)
v: 3.3 Mesa 21.0.3
My laptop is an ASUS FX505DY. I bought it without any OS and installed Ubuntu 19.10, then upgraded it to 20.04 a few months later (no dual boot).
From time to time, the system doesn't boot normally and goes into "emergency mode" (it's actually the 3rd time after about 1 year of use). Each time the cause is fsck failing to check /home partition. journalctl gives me:
oct. 30 12:19:44 poulpito systemd-fsck[624]: fsck failed with exit status 4.
oct. 30 12:19:44 poulpito systemd[1]: Failed to start File System Check on /dev/disk/by-uuid/91e9d404-4089-4b8d-af58-5aebcd76b5a0.
I can easily fix it with: fsck.ext4 -v /dev/sda4. I hit enter to every questions and then I can reboot and enjoy an OS running normally. But I feel uneasy with the problem recurring and I would like to fix it permanently.
So my questions are:
Why file system get corrupted on this partition? Could it be a hardware problem? Do I need to change some parameters or configuration or switch to ext3? I've run smartctl -t short /dev/sda4 in recovery mode and no error were reported.
/home is on a sata HDD where I also have /var, /tmp and swap partitions. I never get any fsck check problem for these. Perhaps because the boot sequence just doesn't check these partitions? Or corruptions really happen just on /home?
The last time I had to run fsck.ext4, I got these questions:
pass 1: inode <inode id> seems to contain garbage and inode <inode id> passes checks, but checksum does not match inode, actually 16 messages of these kinds with contiguous inode numbers
pass 2: entry '<filename>' in <path> (<inode id>) has deleted/unused inode <inode id> (inode numbers suggest that it is a mere consequence of inodes cleared during pass 1
pass 4: inode <inode id> ref count is <count>, should be <count> (again, seems to be just a consequence of pass 2)
pass 5: inode and block bitmap differences, free inodes/free blocks/directories count wrong
Does this mean that I lose some data? Since all impacted inodes are related to application files in $HOME/.config/ or $HOME/.local/, I don't see directly the effect of a missing or corrupted file...
Here is a screenshot of the SMART data window in the Disks app.
smartctl gives roughly the same data in English:
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
2 Throughput_Performance 0x0005 100 100 050 Pre-fail Offline - 0
3 Spin_Up_Time 0x0027 100 100 001 Pre-fail Always - 1350
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 670
5 Reallocated_Sector_Ct 0x0033 100 100 050 Pre-fail Always - 0
7 Seek_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
8 Seek_Time_Performance 0x0005 100 100 050 Pre-fail Offline - 0
9 Power_On_Hours 0x0032 095 095 000 Old_age Always - 2224
10 Spin_Retry_Count 0x0033 113 100 030 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 509
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 48
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 10
193 Load_Cycle_Count 0x0032 098 098 000 Old_age Always - 24418
194 Temperature_Celsius 0x0022 100 100 000 Old_age Always - 34 (Min/Max 19/42)
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0
197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 253 000 Old_age Always - 0
220 Disk_Shift 0x0002 100 100 000 Old_age Always - 0
222 Loaded_Hours 0x0032 096 096 000 Old_age Always - 1931
223 Load_Retry_Count 0x0032 100 100 000 Old_age Always - 0
224 Load_Friction 0x0022 100 100 000 Old_age Always - 0
226 Load-in_Time 0x0026 100 100 000 Old_age Always - 263
240 Head_Flying_Hours 0x0001 100 100 001 Pre-fail Offline - 0
254 Free_Fall_Sensor 0x0032 100 100 000 Old_age Always - 0
SMART Error Log Version: 1
No Errors Logged
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 2218 -
Another screenshot of GParted:
As suggested I've upgraded my BIOS firmware. The upgrade went fine and didn't break anything. For sure, it's better to have firmware up-to-date in any case, but I must confess that I don't understand how the BIOS could be responsible of filesystem corruptions on a single partition of my hard drive and I can't see any way to verify that the problem is really solved. I've given up for now, and I'll update this post if the problem occurs again.
Update: the same error occurred again about two months after the original post and BIOS update.
More details, as requested by @heynnema.
$ free -h
total utilisé libre partagé tamp/cache disponible
Mem: 7,7Gi 2,3Gi 3,8Gi 49Mi 1,5Gi 5,0Gi
Partition d'échange: 15Gi 0B 15Gi
sudo lshw -C memory https://paste.ubuntu.com/p/Sq9qy9kxVb/
zgrep -i gnome-software /var/log/syslog* https://paste.ubuntu.com/p/Qqy99YnFvC/
$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/nvme0n1p2 during installation
UUID=cbee80f8-6637-44e3-8dbd-7f710be58e54 / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/nvme0n1p1 during installation
UUID=E06D-1632 /boot/efi vfat umask=0077 0 1
# /home was on /dev/sda4 during installation
UUID=91e9d404-4089-4b8d-af58-5aebcd76b5a0 /home ext4 defaults 0 2
# /tmp was on /dev/sda2 during installation
UUID=51e800d3-f199-490a-bb7a-d2f49635e71c /tmp ext4 defaults 0 2
# /var was on /dev/sda3 during installation
UUID=da892f2f-b8d2-47f5-a5e7-30e779fe9d2c /var ext4 defaults 0 2
# swap was on /dev/sda1 during installation
UUID=7317598f-60e6-475e-a7d0-38503bac42fc none swap sw 0 0
Hi guys since yesterday I have been trying to fix a problem regarding the rock-dkms and rocm-dkms, whenever i try to update or install any packages to my system this error occurs:
-------- Uninstall Beginning --------
Module: amdgpu
Version: 3.7-20
Kernel: 5.4.0-42-generic (x86_64)
-------------------------------------
Status: Before uninstall, this module version was ACTIVE on this kernel.
amdgpu.ko:
- Uninstallation
- Deleting from: /lib/modules/5.4.0-42-generic/updates/dkms/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
amdttm.ko:
- Uninstallation
- Deleting from: /lib/modules/5.4.0-42-generic/updates/dkms/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
amdkcl.ko:
- Uninstallation
- Deleting from: /lib/modules/5.4.0-42-generic/updates/dkms/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
amd-sched.ko:
- Uninstallation
- Deleting from: /lib/modules/5.4.0-42-generic/updates/dkms/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
Running the post_remove script:
depmod...
update-initramfs.........
DKMS: uninstall completed.
------------------------------
Deleting module version: 3.7-20
completely from the DKMS tree.
------------------------------
Done.
Loading new amdgpu-3.7-20 DKMS files...
Building for 5.4.0-42-generic 5.7.16-xanmod2
Building for architecture x86_64
Building initial module for 5.4.0-42-generic
Secure Boot not enabled on this system.
Done.
Forcing installation of amdgpu
amdgpu.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/5.4.0-42-generic/updates/dkms/
amdttm.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/5.4.0-42-generic/updates/dkms/
amdkcl.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/5.4.0-42-generic/updates/dkms/
amd-sched.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/5.4.0-42-generic/updates/dkms/
depmod...
Backing up initrd.img-5.4.0-42-generic to /boot/initrd.img-5.4.0-42-generic.old-
dkms
Making new initrd.img-5.4.0-42-generic
(If next boot fails, revert to initrd.img-5.4.0-42-generic.old-dkms image)
update-initramfs.........
DKMS: install completed.
Building initial module for 5.7.16-xanmod2
ERROR (dkms apport): kernel package linux-headers-5.7.16-xanmod2 is not supporte
d
Error! Bad return status for module build on kernel: 5.7.16-xanmod2 (x86_64)
Consult /var/lib/dkms/amdgpu/3.7-20/build/make.log for more information.
dpkg: error processing package rock-dkms (--configure):
installed rock-dkms package post-installation script subprocess returned error
exit status 10
Setting up libio-string-perl (1.08-3) ...
Setting up libcwidget4:amd64 (0.5.18-5build1) ...
Setting up aptitude-common (0.8.12-1ubuntu4) ...
Setting up aptitude (0.8.12-1ubuntu4) ...
update-alternatives: using /usr/bin/aptitude-curses to provide /usr/bin/aptitude
(aptitude) in auto mode
Setting up libsub-name-perl (0.26-1) ...
Setting up libfcgi-perl (0.79-1) ...
dpkg: dependency problems prevent configuration of rocm-dkms:
rocm-dkms depends on rock-dkms; however:
Package rock-dkms is not configured yet.
dpkg: error processing package rocm-dkms (--configure):
dependency problems - leaving unconfigured
Setting up libclass-accessor-perl (0.51-1) ...
No apport report written because the error message indicates its a followup erro
r from a previous failure.
Setting up libcgi-fast-perl (1:2.15-1) ...
Setting up libparse-debianchangelog-perl (1.2.0-13) ...
Processing triggers for man-db (2.9.1-1) ...
Processing triggers for libc-bin (2.31-0ubuntu9) ...
Errors were encountered while processing:
rock-dkms
rocm-dkms
E: Sub-process /usr/bin/dpkg returned an error code (1)
I am new to the Linux environment so I am not really sure what to do, I tried to look up for a solution but nothing seemed to work :/
I have tried installing Ubuntu about 10 times. It doesn't install. I first tried Ubuntu 18.04 and then Ubuntu 20.04. Both the times I have got the same screen telling me that system has crashed. Here is how it went for 10 times. First I downloaded Ubuntu 18.04. Then I created a 50GB partition in D drive. Then I used balenaEtcher for making a 32GB bootable USB flash drive.
Then I restarted my HP Omen laptop, pressed F10, went to BIOS changed the boot order to USB, find the Grub Menu -- Try Ubuntu without installing. Then Ubuntu loads, I go for installation and I choose "Installation Alongside Windows". It goes to the end, asks for a restart and hangs. Then I get a black screen for a while with a bunch of boot messages on it, and it hangs there.
The following are the screenshots of what I get on the screen.
Then after an hour it's still like this.
I left it for hours there and nothing more would happen. So I pressed down the power button for 5 seconds, shutdown my PC, and rebooted it. It gets stuck at this screen.
I tried doing this procedure for about 10 times with the same result. Following are the screenshot that I get.
Then I thought, I'll redownload Ubuntu and try again, but it didn't work. I downloaded Ubuntu 20.04, but it also didn't work. The results are the same.
Just tell me is there any problem with my system? Or is there any problem in my procedure. Just tell me what's wrong.
The following black screen captures my problem.
[ 2.759289] Couldn't get size: 0x800000000000000e
/dev/sda2 contains a file system with errors, check forced.
Inodes that were part of a corrupted orphan linked list found.
/dev/sda2: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
fsck exited with status code 4
The root filesystem on /dev/sda2 requires a manual fsck
BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1.4) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs) shutdown_
I have an Ubuntu 19.10 encrypted LVM2 setup.
I have followed all the guides I could find. I checked rootdelay, /proc/modules exists, did cryptsetup luksOpen etc. as described here - Update initramfs. I removed all my Nvidia drivers. I removed a broken lvm raid0 setup on drives specifically used to store data.
The result is no difference, but Ubuntu still can't boot.
lsblk` output
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 1.9G 1 loop
loop1 7:1 0 89.1M 1 loop
loop2 7:2 0 54.5M 1 loop
loop3 7:3 0 149.9M 1 loop
loop4 7:4 0 4.2M 1 loop
loop5 7:5 0 14.8M 1 loop
loop6 7:6 0 956K 1 loop
loop7 7:7 0 44.2M 1 loop
sda 8:0 0 55.9G 0 disk
sdb 8:16 0 55.9G 0 disk
sdc 8:32 0 223.6G 0 disk
├─sdc1 8:33 0 512M 0 part /boot/efi
├─sdc2 8:34 0 732M 0 part /boot
└─sdc3 8:35 0 222.4G 0 part
└─sdc3_crypt 253:0 0 222.3G 0 crypt
├─ubuntu--vg-root 253:1 0 221.4G 0 lvm /
└─ubuntu--vg-swap_1 253:2 0 976M 0 lvm
sdd 8:48 0 1.8T 0 disk
├─sdd1 8:49 0 245.9G 0 part
└─sdd2 8:50 0 808.4G 0 part
sde 8:64 0 59.6G 0 disk
sdf 8:80 1 7.5G 0 disk
├─sdf1 8:81 1 2.3G 0 part
├─sdf2 8:82 1 3.9M 0 part
└─sdf3 8:83 1 5.2G 0 part
sr0 11:0 1 1024M 0 rom
nvme0n1 259:0 0 238.5G 0 disk
└─nvme0n1p1 259:1 0 238.5G 0 part
Relevant part of fdisk -l
Disk /dev/mapper/sdc3_crypt: 222.3 GiB, 238734540800 bytes, 466278400 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 /dev/mapper/ubuntu--vg-root: 221.4 GiB, 237674430464 bytes, 464207872 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 /dev/mapper/ubuntu--vg-swap_1: 976 MiB, 1023410176 bytes, 1998848 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
My pastebin of boot-repair, which failed, http://pastebin.ubuntu.com/p/4WvZMF9ryt
root@ubuntu:/# lvdisplay /dev/ubuntu-vg
WARNING: Failed to connect to lvmetad. Falling back to device scanning.
--- Logical volume ---
LV Path /dev/ubuntu-vg/root
LV Name root
VG Name ubuntu-vg
LV UUID IG4WUN-mo8H-a00I-mSIp-CRXW-GscM-FtRJtI
LV Write Access read/write
LV Creation host, time ubuntu, 2019-06-16 12:14:27 +0100
LV Status available
# open 1
LV Size 221.35 GiB
Current LE 56666
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:1
--- Logical volume ---
LV Path /dev/ubuntu-vg/swap_1
LV Name swap_1
VG Name ubuntu-vg
LV UUID wMySoO-ylhz-0s9d-W5o9-lkc2-4O5B-hKwXB2
LV Write Access read/write
LV Creation host, time ubuntu, 2019-06-16 12:14:28 +0100
LV Status available
# open 0
LV Size 976.00 MiB
Current LE 244
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:2
Content of /etc/crypttab
sdc3_crypt UUID=11bc3fcd-1ac1-4b4c-a49d-56986510d151 none luks,discard
Content of /etc/fstab
/dev/mapper/ubuntu--vg-root / ext4 errors=remount-ro 0 1
# /boot was on /dev/sdc2 during installation
UUID=d62c1e94-2455-4b9d-80ff-eb6197d718d5 /boot ext4 defaults 0 2
# /boot/efi was on /dev/sdc1 during installation
UUID=485D-94E1 /boot/efi vfat umask=0077 0 1
/dev/mapper/ubuntu--vg-swap_1 none swap sw 0 0
UUID=7bb37d0e-00df-4580-be16-623fc5b0a86b /media/home ext4 defaults 0 2
/dev/disk/by-uuid/52f75980-12b1-44b7-b6d5-bd70ea3bd4cd /mnt/52f75980-12b1-44b7-b6d5-bd70ea3bd4cd auto nosuid,nodev$
/dev/disk/by-uuid/7538bb0e-c514-4b1e-a451-5a6b3fad49f4 /mnt/7538bb0e-c514-4b1e-a451-5a6b3fad49f4 auto nosuid,nodev$
/dev/disk/by-uuid/eb58ba0d-8dd6-418e-b8d3-8b7757f2d17e /mnt/eb58ba0d-8dd6-418e-b8d3-8b7757f2d17e auto nosuid,nodev$
/dev/disk/by-uuid/fecc8e85-2668-4593-be7d-314b4964e964
/mnt/fecc8e85-2668-4593-be7d-314b4964e964 auto nosuid,nodev$
What next to solve this issue?
UPDATE 1:
I tried the steps of the "Update initramfs" article linked to above again, after changing the crypttab file to this
sdc3_crypt /dev/sdc3 none luks,discard
Also changing the CRYPTSETUP=y in /etc/cryptsetup-initramfs/conf-hook
Then got this on the last step 'update-initramfs -c -k all'
cryptsetup: ERROR: Couldn't fnd sysfs directory for 253:1
Google search returned 7 posts, none of which explained the cause of the error, but I removed the CRYPTSETUP=y and retried. This completed the process, but the same error occurred on reboot.
I am currently using 384.111 drivers, which work just fine, however I tried upgrading to 390.12 initially, which caused this error, and 390.25 does too. I suspect 390.42 will have the same issue. I've installed both from the .run file on Nvidia's website and the nvidia-384 package.
Whenever I start up a 390.xx driver from the Ubuntu grub option, it loads with the regular splash screen and then into tty1, except it starts blinking as if the screen turns off and then on again. While the screen is off, none of my keystrokes are registered, meaning I have to spam a key a couple times for it to show up. This also makes it impossible to enter my password as I cannot see if a keystroke has been registered.
The thing is, when I select the Advanced options for Ubuntu grub option and then select recovery mode and then Resume, it boots normally into gdm3 and I can use the system as usual.
I tried booting into Ubuntu and then pressing Esc to show tty1, and saw a black screen with the following boot messages.
[ OK ] Stopped NVIDIA Persistence Daemon.
Starting NVIDIA Persistence Daemon...
[ OK ] Started NVIDIA Persistence Daemon.
[ OK ] Stopped NVIDIA Persistence Daemon.
Starting NVIDIA Persistence Daemon...
[ OK ] Started NVIDIA Persistence Daemon.
[ OK ] Stopped NVIDIA Persistence Daemon.
[FAILED] Failed to start NVIDIA Persistence Daemon.
See 'systemctl status nvidia-persistence.service' for details.
[ OK ] Stopped NVIDIA Persistence Daemon.
[FAILED] Failed to start NVIDIA Persistence Daemon.
See 'systemctl status nvidia-persistence.service' for details.
[ OK ] Stopped NVIDIA Persistence Daemon.
[FAILED] Failed to start NVIDIA Persistence Daemon.
See 'systemctl status nvidia-persistence.service' for details.
[ OK ] Stopped NVIDIA Persistence Daemon.
[FAILED] Failed to start NVIDIA Persistence Daemon.
See 'systemctl status nvidia-persistence.service' for details.
[ OK ] Started LSB: Start windscribe daemon at boot time.
[ OK ] Started TeamViewer remote control daemon.
[ OK ] Stopped NVIDIA Persistence Daemon.
[FAILED] Failed to start NVIDIA Persistence Daemon.
See 'systemctl status nvidia-persistence.service' for details.
[ OK ] Stopped NVIDIA Persistence Daemon.
[FAILED] Failed to start NVIDIA Persistence Daemon.
See 'systemctl status nvidia-persistence.service' for details.
[ OK ] Stopped NVIDIA Persistence Daemon.
[FAILED] Failed to start NVIDIA Persistence Daemon.
See 'systemctl status nvidia-persistence.service' for details.
[ OK ] Stopped NVIDIA Persistence Daemon.
[FAILED] Failed to start NVIDIA Persistence Daemon.
See 'systemctl status nvidia-persistence.service' for details.
[ OK ] Stopped NVIDIA Persistence Daemon.
[FAILED] Failed to start NVIDIA Persistence Daemon.
See 'systemctl status nvidia-persistence.service' for details.
[ OK ] Stopped NVIDIA Persistence Daemon.
[FAILED] Failed to start NVIDIA Persistence Daemon.
See 'systemctl status nvidia-persistence.service' for details.
[ OK ] Stopped NVIDIA Persistence Daemon.
[FAILED] Failed to start NVIDIA Persistence Daemon.
See 'systemctl status nvidia-persistence.service' for details.
[ OK ] Stopped NVIDIA Persistence Daemon.
[FAILED] Failed to start NVIDIA Persistence Daemon.
See 'systemctl status nvidia-persistence.service' for details.
[ OK ] Stopped NVIDIA Persistence Daemon.
[FAILED] Failed to start NVIDIA Persistence Daemon.
See 'systemctl status nvidia-persistence.service' for details.
[ OK ] Stopped NVIDIA Persistence Daemon.
[FAILED] Failed to start NVIDIA Persistence Daemon.
See 'systemctl status nvidia-persistence.service' for details.
Specs:
I'm not that advanced with computers, but I have tried to install Ubuntu 16.04.4 LTS on a completely new SSD in my Lenovo Yoga 11E.
I made a bootable USB drive using Rufus and was able to launch the Ubuntu installer on the laptop.
I was then able to install Ubuntu on the laptop.
...but when I restarted it to load the OS from the SSD, it wouldn't launch from the SSD, only from the USB.
I have tried this thread: Install ubuntu on thinkpad yoga
Here is what happens when I type sudo fdisk -l into the terminal.
Disk /dev/loop0: 1.5 GiB, 1564921856 bytes, 3056488 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 /dev/sda: 238.5 GiB, 256060514304 bytes, 500118192 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
Disklabel type: gpt
Disk identifier: 7B76C6F6-8D31-43AC-8E0F-86786319FB9E
Device Start End Sectors Size Type
/dev/sda1 2048 1050623 1048576 512M EFI System
/dev/sda2 1050624 491968511 490917888 234.1G Linux filesystem
/dev/sda3 491968512 500117503 8148992 3.9G Linux swap
Disk /dev/sdb: 7.5 GiB, 8053063680 bytes, 15728640 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
Disklabel type: dos
Disk identifier: 0x0921d6a2
Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 2048 15728639 15726592 7.5G c W95 FAT32 (LBA)
I checked to see if there was a boot flag on sda1, and there was one already and "esp".
Here is a screenshot of this.
Next I used this thread to reinstall GRUB: How do I manually install GRUB? While following the steps, there were problems with the "recover" step.
Steps I followed when reinstalling GRUB:
Response from the terminal using this code:
I followed the directions for installing a remote desktop server XRDP on my Lubuntu virtual machine. On the third step I am supposed to update the file
sudo nano /etc/xrdp/startwm.sh
for that update do I just go to the bottom of the file and add startxfce4?
I did that and it still does not work
Please advise, thank you
I followed these steps :
Step 1 – Install xRDP
Open Terminal (Crtl+Alt+T) and execute the following commands:
sudo apt-get update
sudo apt-get install xrdp
Step 2 – Install XFCE4 ( Unity doesn't seem to support xRDP in Ubuntu 14.04; although, in Ubuntu 12.04 it was supported ). That's why we install Xfce4.
sudo apt-get install xfce4
Step 3 – Configure xRDP
In this step, we modify two files to make sure xRDP uses Xfce4. First we need to create, or edit, our .xsession file in our home directory. We can either use nano or simply redirect an echo statement (easier):
echo xfce4-session >~/.xsession
The second file we need to edit is the startup file for xRDP, so it will start Xfce4.
sudo nano /etc/xrdp/startwm.sh
The content should look like this (pay attention to the last line and ignore . /etc/X11/Xsession):
#!/bin/sh
if [ -r /etc/default/locale ]; then
. /etc/default/locale
export LANG LANGUAGE
fi
startxfce4
Step 4 – Restart xRDP
I have a broken boot on a linux server that has 4 partitions (sda1-4).
We had a boot issue and resolved it by running grub repair. Once rebooted we updated to Ubuntu 16.04 (on sda2 where all our working directories are). The update resulted in a broken desktop where we couldn't sign in users (put password in and then screen flash and went back to user login). The partition was almost full, so it's possible the update wasn't complete, however there was no error message.
I made a new boot partition (sda4) with Ubuntu 14.04 and tried to delete Ubuntu 16.04, in case it was causing interference, from sda2 by booting from a live CD with the below commands, however it's still there. I also deleted files from sda2 to make space.
sudo mount /dev/sda2 /mnt
sudo mount --bind /sys /mnt/sys
sudo mount --bind /proc /mnt/proc
sudo mount --bind /dev /mnt/dev
sudo chroot /mnt
sudo apt-get remove --purge linux-headers_4.4.8*
sudo apt-get remove --purge image-headers_4.4.8*
I tried Boot-Repair after removal. It boots to grub rescue>. I tried Boot-Repair again and the log is here.
I noticed that for sda4 there is no "boot sector" information. Is this the issue?
Results of df:
Filesystem 1K-blocks Used Available Use% Mounted on
/cow 32979776 43984 32935792 1% /
udev 32935276 4 32935272 1% /dev
tmpfs 6595956 1252 6594704 1% /run
/dev/sr0 987136 987136 0 100% /cdrom
/dev/loop0 944256 944256 0 100% /rofs
none 4 0 4 0% /sys/fs/cgroup
tmpfs 32979776 1028 32978748 1% /tmp
none 5120 4 5116 1% /run/lock
none 32979776 76 32979700 1% /run/shm
none 102400 48 102352 1% /run/user
/dev/sda2 7338794732 5768586068 1200331900 83% /media/ubuntu/b697f249-e945-46f0-898b-438a8da6b100
/dev/sda4 47115636 4139200 40560052 10% /media/ubuntu/3ad839ec-2ceb-4123-aaa2-396634fde7bc
GParted:
New Boot-Repair report post Ubuntu 16.04 updates: https://pastebin.ubuntu.com/23549880/
As you can see in the below screenshot, my partitions are essentially empty.
I just installed Ubuntu today, I had created a brand new partition to support my Ubuntu OS. However, after it successfully partitioned itself my Windows 7 partition no longer works at all. At this point I do not care about restoring my Windows 7 OS, I just want to combine my much larger currently unallocated partition of +600GB with my new Ubuntu partition.
I have installed GParted and read other forums on the issue. However, whenever I try what they have suggested (as far as I can tell) resize/move only adjusts the size of the current partition. It has nothing to do with combining two separate partitions (which are both primary). Many other suggestions wanted me to delete the partition with the file system on it. I can't do that because that is the file system that I am currently using, so it won't let me delete it.
I can't think of what to do. I am seriously worried that I have ruined my computer.
My Ubuntu live USB hangs on boot. I suspect a driver is causing the hang. How can I identify which driver actually causes the freeze?
Here are the details:
acpi=off, noapic, edd=on, nodmraid and nomodeset options, then I edit boot line by removing quiet splash and adding no_console_suspend initcall_debug options and press enter. Ubuntu boots but at certain point hangs with kernel panic messages. Neither Ctrl-Alt-Del nor poweroff works. I need to hard power off the machine by keeping poweroff button for a few seconds.Kernel panic - not syncing: Attempted to kill init! at Ubuntu boot:
[ 5.681936] [<ffffffff81577909>] loop_add+0x1e9/0x270
[ 5.681998] [<ffffffff81faeffa>] loop_init+0x11d/0x170
[ 5.682061] [<ffffffff81faeedd>] ? max_loop_setup+0x1a/0x1a
[ 5.682124] [<ffffffff810021cf>] do_one_initcall+0x15f/0x200
[ 5.682187] [<ffffffff8109ff85>] ? parse_args+0x295/0x4b0
[ 5.682250] [<ffffffff81f5b1a5>] kernel_init_freeable+0x173/0x212
[ 5.682315] [<ffffffff81821540>] ? rest_init+0x80/0x80
[ 5.682377] [<ffffffff8182154e>] kernel_init+0xe/0xe0
[ 5.682439] [<ffffffff8182decf>] ret_from_fork+0x3f/0x70
[ 5.682501] [<ffffffff81821540>] ? rest_init+0x80/0x80
[ 5.682562] Code: 71 cf 81 48 c7 c7 a8 ff f1 81 e8 65 89 02 00 eb cc 0f 1f 00
55 48 85 ff 48 89 e5 41 54 53 48 89 fb 74 37 48 85 f6 49 89 f4 74 62 <f6> 47 3c
01 75 46 48 8d 43 08 c7 43 38 01 00 00 00 4c 89 63 28
[ 5.685169] RIP [<ffffffff813f3397>] kobject_init+0x17/0x90
[ 5.685269] RSP <ffff880159b97d18>
[ 5.685327] CR2: ffffe8ffffd00214
[ 5.685387] ---[ end trace b48cc3c525b1d710 ]---
[ 5.685494] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00
000009
[ 5.685494]
[ 5.685591] Kernel Offset: disabled
[ 5.685649] ---[ end Kernel panic - not syncing: Attempted to kill init! exit
code=0x00000009
[ 5.685649]
_
Is there any way I can identify which drivers that are being loaded to tell which driver causes the hang and possibly disable it?
So I recently installed windows 10 on my computer. Before that I had a dual boot windows 7/ubuntu 14.4. Now I wanted to boot ubuntu from a usb.
I created a live usb using unetbootin. After that I rebooted my pc, pressed F12 (to access boot menu) and selected USB Storage Device. But then nothing happened. My old OS started booting and nothing else happened. Since then I have changed a few settings in hope that my flash drive would be recognized by my computer, but it didn't. So if anybody has had a similar or the same problem and has figured it out please do share your solution. Thanks.
I want to mount the following directories using overlayfs:
(lowerdir) /chroot in /merged
(lowerdir) /home in /merged/home
(upperdir) /tmpfs in /merged
...so that the resulting merged directory is a COW system that contains both the /chroot and /home.
I cannot find any way to do that.
1) Trying multiple lower dirs:
mount -t overlay -o lowerdir=/chroot:/home,upperdir=/tmpfs,workdir=/workdir overlay /merged
ls /merged
==> failure, the /home contents merge with the /chroot contents directly in /merged without getting inside a /merged/home subdirectory.
2) Trying bind-mounts:
mount --bind /home /chroot/home
mount -t overlay -o lowerdir=/chroot,upperdir=/tmpfs,workdir=/workdir overlay /merged
ls /merged/home
==> empty, the /chroot/home submount contents do not show up in /merged/home.
Any ideas? Thank you.
Hardware: Very old Dell Inspiron 6400 laptop, onboard video, no driver support. Planning on buying a new computer soon, but wondering if this is a hardware issue which could be solved by buying a new machine, or a software issue which can be solved with the machine I have by me not being a dolt.
Anyway, I'm trying to play Hearthstone on Wine 1.7.14 under Ubuntu 13.10. I've set my Wine to have a virtual desktop, because otherwise starting up Hearthstone locks my computer, as if a new process is getting mouse focus, but since that process doesn't start properly I just lose the ability to use my mouse (keyboard works fine though, and the system doesn't lag at all, just the mouse dies). When I start up Hearthstone in my virtual desktop, I get a popup in my virtual desktop telling me something about screen resolution or some such. I'm not quite sure what the problem is or how to fix it, and was wondering if anyone here could be of assistance. Unfortunately I'm new to this site so I can't post an image of the error message, but here's the text of the message:
Couldn't setup OpenGL for the requested monitor resolution
GLContext: failed to share context 40000: Success
Screen: could not setup GL for resolution (1152x864 fs=1 hz=60 wi...[error message gets cut off here]
GLContext: failed to share context 30002: Success
Screen: could not setup GL for resolution (1152x864 fs=0 hz=0 win...
So here's the deal. I've created /etc/motd.tail as suggested by Ubuntu documentation which should append STATIC content to /etc/motd . However as well as this work, it displays the MOTD TWICE when I log on to the server via ssh.
W00t ?! Is there any way to fix this ? This does seem like a bug to me.
Thanks
I have made my Transcend USB 3.0 flash drive into a bootable Arch Linux USB flash drive using the dd command. After that it become read-only and I was not able to use it. I formatted as MBR with NTFS partition using Disk Utility in Ubuntu and there were no errors, but when I try to use it, it's saying read-only and not allowing me to copy anything.
Here is a screenshot of the error.
I had tried reformatting as GPT,the same error. I have tried EXT4 also.I have ran fsck command also, it says everything is clear. The following is the output of dmesg | tail -n25.
[ 5399.004036] [UFW BLOCK] IN=eth0 OUT= MAC=01:00:5e:00:00:01:2c:41:38:db:7e:b7:08:00 SRC=0.0.0.0 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2
[ 5413.351497] type=1400 audit(1386569943.739:66): apparmor="DENIED" operation="capable" parent=1 profile="/usr/sbin/cupsd" pid=8956 comm="cupsd" pid=8956 comm="cupsd" capability=36 capname="block_suspend"
[ 5438.323077] [UFW BLOCK] IN=eth0 OUT= MAC=01:00:5e:00:00:01:2c:41:38:c8:82:00:08:00 SRC=169.144.44.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=31744 PROTO=2
[ 5463.333598] [UFW BLOCK] IN=eth0 OUT= MAC=01:00:5e:00:00:01:2c:41:38:db:7e:b9:08:00 SRC=0.0.0.0 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2
[ 5472.271930] usb 2-1.5: USB disconnect, device number 3
[ 5479.546220] usb 2-1.5: new high-speed USB device number 4 using ehci_hcd
[ 5479.639030] usb 2-1.5: New USB device found, idVendor=8564, idProduct=1000
[ 5479.639039] usb 2-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 5479.639044] usb 2-1.5: Product: Mass Storage Device
[ 5479.639047] usb 2-1.5: Manufacturer: JetFlash
[ 5479.639052] usb 2-1.5: SerialNumber: 1250498862
[ 5479.639699] scsi17 : usb-storage 2-1.5:1.0
[ 5480.636704] scsi 17:0:0:0: Direct-Access JetFlash Transcend 8GB 1.00 PQ: 0 ANSI: 6
[ 5480.637548] sd 17:0:0:0: Attached scsi generic sg2 type 0
[ 5480.638034] sd 17:0:0:0: [sdb] 15433728 512-byte logical blocks: (7.90 GB/7.35 GiB)
[ 5480.638406] sd 17:0:0:0: [sdb] Write Protect is off
[ 5480.638415] sd 17:0:0:0: [sdb] Mode Sense: 23 00 00 00
[ 5480.638771] sd 17:0:0:0: [sdb] Write cache: disabled, read cache: disabled, doesn't support DPO or FUA
[ 5480.650924] sdb: sdb1
[ 5480.652992] sd 17:0:0:0: [sdb] Attached SCSI removable disk
[ 5480.798379] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
[ 5486.400055] [UFW BLOCK] IN=eth0 OUT= MAC=01:00:5e:00:00:01:2c:41:38:db:7e:ae:08:00 SRC=0.0.0.0 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2
[ 5486.826155] [UFW BLOCK] IN=eth0 OUT= MAC=01:00:5e:00:00:01:2c:41:38:db:7e:af:08:00 SRC=0.0.0.0 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2
[ 5487.220538] [UFW BLOCK] IN=eth0 OUT= MAC=01:00:5e:00:00:01:2c:41:38:db:7e:ba:08:00 SRC=0.0.0.0 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2
[ 5514.209561] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at byte 6
This is weird. I have formatted as FAT, I have checked the permissions, it is normal (-rw-r--r--). I have opened the terminal and used mkdir and created a directory. I am able to create files also from the command line, but whenever I try to access them using nautilus, the error mentioned at the start is occurring. I have checked in my friend's laptop, and there is no problem. I still can't understand the problem.
My question says it all: on Ubuntu, is there any way to mount a .dmg file (as produced by OS X's Disk Utility) that contains an AES-encrypted, FAT12 filesystem?
I've seen sporadic advice about how to mount .dmg files containing hfsplus filesystems, so I'd have thought the fat12 (aka, "msdos") filesystem would be even easier. The closest I've come is:
mount -oloop,encryption=aes-256 -t msdos privatedmg.dmg ~/mounted
But this gives me the error ioctl: LOOP_SET_STATUS: Invalid argument. I don't know much about linux filesystem mechanics, but am eager to learn!
I am using the Remmina remote desktop connection on Ubuntu 12.04 to create RDP connection. The system on the remote desktop is Windows Server 2003 RC Standard 64 edition which logs off by itself randomly. It terminates the connection, so you have to re-connect.
For example: Terminates when I want to switch to another application or simply change the desktop. On another PC (which is running on Windows) this problem does not occur.
Does the Remmina have timeout or logoff settings which can cause this problem? What could be the solution?
I have several builds of an application on my system (a dev build and many older released builds). When I'm trying to run an older release, the system invariably picks up the dynamic libraries from the dev build.
From /home/franz/Projects/appleseed/archives/releases/1.1.0-alpha-14-0-g4e46ed9/appleseed/bin which is the directory of the older release I'm trying to run:
$ ldd appleseed.studio
[stuff omitted]
libappleseed.so => /home/franz/Projects/appleseed/build/linux-gcc4/appleseed/libappleseed.so (0x00007fbcb090b000)
libappleseed.shared.so => /home/franz/Projects/appleseed/build/linux-gcc4/appleseed.shared/libappleseed.shared.so (0x00007fbcb030c000)
[more stuff omitted]
(/home/franz/Projects/appleseed/build/linux-gcc4/appleseed/ is the path to my dev build.)
Naturally I should set LD_LIBRARY_PATH correctly before running an older release:
$ export LD_LIBRARY_PATH=/home/franz/Projects/appleseed/archives/releases/1.1.0-alpha-14-0-g4e46ed9/appleseed/bin ; ./appleseed.studio
(LD_LIBRARY_PATH is initially empty so I don't bother with concatenation.)
However this doesn't work and the system continues to pick up the dev build of the dynamic libraries.
Am I doing something wrong? Any idea?
I am running a 64-bit build of Ubuntu 10.10 Maverick Meerkat (unsupported as of April 2012).
UPDATE: I have updated my system to Ubuntu 11.10 (Natty) and the problem persists.
I have one audio output and two audio inputs on my computer. But I have one microphone, stereo reproductors and headphones. In windows Realtek driver I could simple change the audio input to output, now I'm using Ubuntu 12.04 and PulseAudio. Is there any option to change the input to output and conversely?
Is there a way to tell nano to automatically show line numbering each time I open a file?