The Inspiron 3593 does not have a dedicated Trusted Platform Module (TPM
2.0), but instead the successor IntelĀ® Platform Trust Technology (IntelĀ®
PTT). Disabling this PTT in BIOS security settings has *NOT* improved
anything.
Workaround #1 does not work for me.
Entering 'rmmod tpm' leads to 'comm
Could this be a version mismatch?
All updates has changed from 2.02-2ubuntu8.21 to 2.02-2ubuntu8.23, except the
grub-efi-amd64-bin:amd64, whgich has been upgraded to 2.04-1ubuntu44.
The version numbers of the packages differ. Could this cause the
problem?
--
You received this bug notification
Same here on a Dell Inspiron 3593, Bios never updated, version V1.1.0,
ubuntu 18.04. It started suddenly one or two weeks ago, previously
running without problems.
Reboot always works, complete shutdown and boot within some seconds by
power button mostly fails.
On 2021-05-14 there was some update
~$ aplay -l
List of PLAYBACK Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC233 Analog [ALC233 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
--
HDMI device not detected
--
You received this bug notification because you are a member of Ubuntu
Bugs
This bug is affecting me, too.
System /kernel: Ubuntu 20.04.2 LTS
Linux 5.4.0-70-generic #78-Ubuntu SMP Fri Mar 19 13:29:52 UTC 2021 x86_64
x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
I got exactly the same problem - ubiquity crash - at the same step - trying to
re-install Ubuntu 18.04.1.
Two file systems are assigned the same mount point (/boot/efi)...
Please correct this by changing mount points
If I click OK I'm taken to the partition editor which appears to scan my
d
*** This bug is a duplicate of bug 1342624 ***
https://bugs.launchpad.net/bugs/1342624
Public bug reported:
I was install an HWE upgrade when this error was reported.
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.6
ProcVersionSignature: Ubuntu
I have the read-only bug under a slightly different condition: Its not a
external USB-Stick but a remounted partition.
For security reasons I have an archive partition which is mounted read-
only at startup of the notebook. When I mount the partition afterwards
in readwrite-mode then nautilus tell
** Changed in: dpkg (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1077010
Title:
package libqtgui4 4:4.8.1-0ubuntu4.3 failed to install/upgrade:
p
** Changed in: curl (Ubuntu)
Status: Invalid => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1258366
Title:
curl -k breaks for some certificates after USN-2048-1
To manage noti
After updating to ubuntu 13.10 Saucy Salamander this feature is
available again. So only Raring suffers from this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1176158
Title:
kipiplugin_htmlexp
Either this fix isn't complete or I have a similar problem.
On my fast hardware (a Clevo W370ET with SSD and a quad core i7) I
observe the same effects. Even after updating to latest versions I get
the fault. I'm running raring (XUbuntu 13.04).
I observe at 50% of booting a black screen with a bl
Public bug reported:
If I start rhytmbox on the new ubuntu 13.04 raring ringtail (amd64) then
i get the following message:
ERROR: Caught a segmentation fault while loading plugin file:
/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgsttypefindfunctions.so
Please either:
- remove it and restart.
- ru
After reading the previous comments I come to the conclusion that a
working solution needs a redefinition of the keycode. Each of the
working solutions have one of the following lines in it:
keycode 66 = Control_L
keysym Caps_Lock = ISO_Level3_Shift
keycode 66 =
keysym Caps_Lock = Shift_L
--
You
I can confirm this problem too on precise XUbuntu (12.04), 32bit
edition.
I tried to remove the lock from the caps lock, i.e. to behave it as a
normal shift. With xubuntu 10.10 I had the following working solution:
clear Lock
add shift = Caps_Lock
After the update to precise pangolin 12.04 on th
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/938033
Title:
package fglrx (not installed) failed to install/upgrade: subprocess
installed post-installation script returned error exit status 5
To m
Public bug reported:
I began to have fglrx problems shortly after an Ubuntu 10.04 update last
week. I don't know specifically which one.
I'm using Gnome with Compiz and Emerald for my desktop. I've switched
to the default open source drivers for Ubuntu.
ProblemType: Package
DistroRelease: Ubun
Public bug reported:
Binary package hint: libfprint0
Start fprint_demo and enroll a finger. This is successful.
Quit fprint_demo.
Start fprint_demo once more and try to enroll another finger. You get
'enroll failed with error -71'
Specifically:
upekts:error [__read_msg] msg read failed, code
Public bug reported:
Binary package hint: mozplugger
1. Open a pdf using evince.
2. Open firefox w/ mozplugger and click on a pdf-link.
Result: The linked pdf is not embedded.
Description:Ubuntu 8.04.1
Release:8.04
mozplugger:
Installed: 1.10.1-2ubuntu2
Candidate: 1.10.1-2ubun
19 matches
Mail list logo