In my case it was random and appeared very recently. It would boot once
every 5-10 times.
The MODULE=dep seems to work so far.
Ubuntu 21.04 on Dell Precision 5750
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
Any workaround?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870261
Title:
gdm-session-wor error
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-key
Couldn't we just use 1.6 to do the same now? I read that 1.6 worked for
who got it compiled/installed in some way.
The sof-firmware is missing/buggy since 20.10, so everybody with a 2020
DELL XPS/Precision laptop has not being able to get any input/output
audio since months already.
Is there a wa
Public bug reported:
(Reading database ... 220533 files and directories currently installed.)
Preparing to unpack .../firmware-sof-signed_1.6.1-2_all.deb ...
Unpacking firmware-sof-signed (1.6.1-2) ...
dpkg: error processing archive
/var/cache/apt/archives/firmware-sof-signed_1.6.1-2_all.deb (--u
0.4.8 works here on 20.04.1!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1897563
Title:
Zsys changes the canmount property of persistent bpool/grub dataset
To manage notifications about this bug
0.4.8 works for me. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1897565
Title:
[SRU] Persistent dataset print strangely
To manage notifications about this bug go to:
https://bugs.launchpa
19.10 still has the corrupted desktop scattered image (an annoying grey-
yellow-white pattern) with nvidia-435. The same pattern appear also in
some images in the chromium browser window.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
None of the above worked here! Without the /etc/resolv.conf nothing
works obviously, then the dpkg-reconfigure resolvconf does nothing (i.e.
there is still no file after running it. Adding it manually solved a
part of the problem, but the Unknown group "power" still blocks starting
of the network.
Mine was about half in the battery slider and 0 in the AC slider.
On Fri, May 26, 2017, 12:11 PM Mario Limonciello
wrote:
> That sounds a little crazy that it can't reproduce in my opinion. When it
> "did" reproduce was the brightness at one of the extremes? Eg full high on
> shutdown or full lo
Changing the brightness in the BIOS video tab got rid of the problem!
Great!!!
I am glad that you stumble upon that only AFTER you could confirm that
the problem existed. :)
Thank you for your time and assistance!
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
About the reading in #20, it was the situation at that given time, not
after a reboot. Since the
/sys/class/backlight/intel_backlight/brightness was not 1500 (full
brightness after reboot) I obviously changed it.
The dynamic of what happens is shown in the "example" section of #23.
After every reb
Just discovered that the value returned by grep .
/var/lib/systemd/backlight/* is ALWAYS the value of cat
/sys/class/backlight/intel_backlight/brightness BEFORE reboot.
So to summarize:
1. the grep . /var/lib/systemd/backlight/* shows the value of the
brightness that was right before the last reb
Setting the multi-user.target causes a timeout error at boot,
complaining that it cannot connet lumetad (?).
BTW, as another possibly useful detail. After reboot the cat
/sys/class/backlight/intel_backlight/brightness and the grep .
/var/lib/systemd/backlight/* give both 1500 (the maximum). AS soo
$ cat /sys/class/backlight/intel_backlight/brightness
451
$ grep . /var/lib/systemd/backlight/*
75
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686268
Title:
Backlight brightness level not restor
1. The real value of the current brightness (e.g. 75)
2. As I said: after the reboot that value is the same (e.g. 75)
3. As soon as I move the slicer in the Gnome Shell Panel, the new value gets
saved into the file (e.g. 150)
To explain you better: it looks like the value in that file is kept in
Yes, that value is saved as soon as I change the brightness. After
reboot the brightness value is not restored (indeed the back-light is
actually full brightness), although the value in that file is still the
saved one.
However running the `sudo /lib/systemd/systemd-backlight load
backlight:intel_
I forgot to say that the above output comes after commenting out the
@reboot cron entry workaround and restarting, so it is exactly what it
does without any workaround.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
The exact command you wrote:
$ systemctl status systemd-backlight@intel_backlight.service
systemd-backlight@intel_backlight.service - Load/Save Screen Backlight
Brightness of intel_backlight
Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static;
vendor preset: enabled)
Act
Apparently, it was working with 16.10 (4.8.0-46), although I had a
different setup (GNOME desktop added on an official UBUNTU installation
from DELL).
The problem started with Ubuntu Gnome 17.04 (4.10.0-19) and persisted
with 4.10.0-20.
About testing the upstream kernel, I am willing to try. I ju
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1686268/+attachment/4868096/+files/ProcCpuinfoMinimal.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of U
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1686268/+attachment/4868095/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686268
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1686268/+attachment/4868092/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686268
Title:
apport information
** Tags added: apport-collected zesty
** Description changed:
I am not sure if this is the right place to report this, so feel free to
move it elsewhere.
It looks like the systemd-backlight service (/lib/systemd/system
/systemd-backlight@.service) does not restore t
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1686268/+attachment/4868094/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686268
Title:
Back
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1686268/+attachment/4868091/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686268
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1686268/+attachment/4868093/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/16862
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1686268/+attachment/4868090/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686268
Title:
Backli
Public bug reported:
I am not sure if this is the right place to report this, so feel free to
move it elsewhere.
It looks like the systemd-backlight service (/lib/systemd/system
/systemd-backlight@.service) does not restore the brightness level
(although it saves it before shut-down).
However th
28 matches
Mail list logo