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
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
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
