Your bug report is a month and a half old with enlightenment 0.24.2-8. A
development version is in constant movement. Installable now is
enlightenment 0.25.3-1.
I also had pointed out the following:
> Possibly the cause is how enlightenment was installed,
> root or sudo, tty or terminal (so with
e17 is the short name for enlightenment 0.17, so it is a version.
e17 is located in universe and is only available for Bionic, but has
reached EoS years ago. The package e17 was last updated 5 1/2 years ago.
https://packages.ubuntu.com/search?keywords=e17=names=all=all
"LTS" is promised anyway
It's a solution for you and for now.
You only need to search. The issue itself appears from time to time
since years, always only scattered (as you can see here - I have never
had this problem with Lubuntu or siduction and e17/e18/e19) and in
different distributions, e.g. also once in Arch. This
You could set the https://en.wikipedia.org/wiki/Setuid;>suid:
# chmod 4755 /usr/lib/x86_64-linux-gnu/enlightenment/utils/enlightenment_sys
# chmod 4755 /usr/lib/x86_64-linux-gnu/enlightenment/utils/enlightenment_system
--
You received this bug notification because you are a member of Ubuntu
A package e17 doesn't exist in Jammy. It's enlightenment with e25.
** Package changed: e17 (Ubuntu) => enlightenment (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1955844
Title:
> My default first boot device is Ubuntu and then windows and then USB
and network.. etc..
(...)
> I tried to run pratation magic.
How did you boot Partition Magic?
If this is on a DVD, the ODD must be before the HDD in the boot
sequence.
Then you could also just boot Focal64 for fixing.
--
Btw., Vicky, if Win8 is already running, the first thing I would do
would be to flash the last available UEFI, unfortunately also almost 5
years old.
https://pcsupport.lenovo.com/de/en/products/laptops-and-
netbooks/lenovo-z-series-laptops/lenovo-z50-70/downloads/DS100528
--
You received this
Vicky, your current issue has nothing to do with the UEFI issue in this
thread.
> I then select windows 8 and use windows 8.
Technically you only had to do an in-place upgrade to Win10.
This reliably ;-) overwrites Grub.
Officially, this has been possible free of charge for up to 1 year after
Before you have to scrap the notebook:
http://archive.ubuntu.com/ubuntu/dists/xenial-
updates/main/uefi/grub2-amd64/current/grubx64.efi.signed is much newer,
but should also work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Before you have to scrap the notebook...http://archive.ubuntu.com/ubuntu/dists/xenial-
updates/main/uefi/grub2-amd64/current/grubx64.efi.signed">http://archive.ubuntu.com/ubuntu/dists
/xenial-updates/main/uefi/grub2-amd64/current/grubx64.efi.signed is
much newer, but should also work.
--
You
You use nouveau, but have set the boot option nomodeset. So it is your
fault.
Bionic with kernel 5.3.0-26 and nouveau work fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860196
Title:
> Linux Mint 18.3 (Ubuntu 16.04.3)
At the first: Mint is *not* Ubuntu, it is only based on it with several
changes, additions and withheld packages.
As a basis I would always have flashed the last available BIOS/UEFI. But
216 is already on your Asus X451MA.
"r8169 can't disable aspm" (your
I mean Win 1803 of course, "1804" doesn't exist.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1734147
Title:
corrupted BIOS due to Intel SPI bug in kernel
To manage notifications about this bug
I mean Win 1803 of course.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1734147
Title:
corrupted BIOS due to Intel SPI bug in kernel
To manage notifications about this bug go to:
#592, #602
@Robert R (roremich)
17.10 w/o .1 is *toxic* (and anyway EoS, with .1 also). Already the
first boot up changes the value. The UEFI is destroyed, so to speak.
Btw., that would not have happened in CSM mode instead UEFI mode.
Hard cheese, inform in advance.
Installing a clean kernel in
> dmi.bios.date: 06/06/2008
> dmi.bios.vendor: LENOVO
> dmi.bios.version: 7LETB9WW (2.19 )
> (...)
> dmi.product.version: ThinkPad T61
At the first you should flash the current BIOS version 2.30-1.08 (!).
The Core 2 Duo has implemented the Intel64 extension. You should install
Bionic 64 bit
> dmi.bios.version: F4
> (...)
> dmi.board.name: B150M-D3H-CF
> dmi.board.vendor: Gigabyte Technology Co., Ltd.
At the first you should flash the current UEFI version F24g (!).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
#482
http://kernel.ubuntu.com/sru/versions.html
4.13.0-17.20 → dangerous, a corrupt (!) version.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1734147
Title:
corrupted BIOS due to Intel SPI bug
@Joseph Salisbury
No. That alone can _not_ solve the problem.
When starting the stick or the DVD, the option must be set before _and_
after the double dash:
" forcepae -- forcepae"
@Wesley Keener, execute this commands:
sudo sed -i 's/GRUB_CMDLINE_LINUX=""/GRUB_CMDLINE_LINUX="forcepae"/g'
What a cruel editor. The 1st is 1 line:
sudo sed -i 's/GRUB_CMDLINE_LINUX=""/GRUB_CMDLINE_LINUX="forcepae"/g'
/etc/default/grub
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740906
Title:
package
Plz post the output of:
cat /etc/default/grub | grep GRUB_CMDLINE_LINUX
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740906
Title:
package linux-image-4.13.0-21-generic (not installed) failed to
If it's the kernel bug, Bionic will not help. Additionally the
corrupting Artful kernel is still integrated in the image.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740229
Title:
Ubuntu 17.10
You don't have a BIOS, but a UEFI.
→ https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740614
Title:
lost bios
To manage notifications
@Ahmed Ibrahim (n0krashy), I wrote "suppose" and "could". I don't have
this notebook.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1734147
Title:
Ubuntu 17.10 corrupting BIOS - many LENOVO laptops
> What can I do with Lenovo Y50-70 with Windows 10 Only? Ubuntu is
removed.
olekcz, hm, do you have _this_ UEFI issue? I suppose, (re-)flashing of
the last UEFI version (https://tinyurl.com/ycq52ba5) could solve the
problem, it's a Windows executable.
--
You received this bug notification
You confuse a bug tracker with a support forum, for example
https://ubuntuforums.org/. There better help for the individual user is
possible, if you give useful information.
But...maybe you have this issue:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147. You should
check your UEFI.
Grr...sry about my handling mistakes. ;)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740229
Title:
Ubuntu 17.10 killed my notebook
To manage notifications about this bug go to:
You confuse a bug tracker with a support forum, for example https://ubuntuforums.org/;>ubuntuforums.org. There better help
for the individual user is possible, if you give useful information.
But...maybe you have https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147;>this
issue. You should
Public bug reported:
I upgraded to 9.10 and now 1024 X 768 display problems where parts of
windows disappear. I had to change to a display ratio of 800 X 600. And
still having issues.
ProblemType: KernelOops
Annotation: This occured during a previous suspend and prevented it from
resuming
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/34829073/AlsaDevices.txt
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/34829074/BootDmesg.txt
** Attachment added: Card0.Amixer.values.txt
UbuntuX wrote:
What is your graphics cards,
Usually Ubuntu Recognizes nVidia drivers. Most Dell Systems Have nVidia
graphic cards
This is a HP OmniBook 6100. The Graphics Card is ATI Technologies Inc
Radeon Mobility M6 LY. I think my problem is resolved. There is a
setting under -
Hello, sorry I am speak german...
2009/3/15 Mackenzie Morgan maco...@gmail.com
It was fixed a few weeks ago.
--
Brasero 0.9.1 breaking non-English systems
https://bugs.launchpad.net/bugs/325221
You received this bug notification because you are a direct subscriber
of the bug.
Public bug reported:
Ubuntu version: 8.10 beta Alternate CD i386
Kernel version: 2.6.27.4-generic
Mainboard chipset: Intel MCH P965 ICH 8
HD controller: ICH 8 SATA
Mainboard: Asus P5B
BIOS: latest, 1902
The Intrepid Ibex (alpha and beta) setup don't find a harddisk at ICH 8
SATA controller or
33 matches
Mail list logo
