Problem apparently solved (i.e., SDD wakes up from S3, can remove
"mem_sleep_default=shallow" from grub) with today's BIOS update to
2.0.2. Or with some firmware update associated with it. The problem with
Dell is that these firmware updates declare to address only obscure
security tickets, not
** Description changed:
System apparently correctly suspends (in various ways - from gnome menu,
with pm-suspend on bash, with echo ... > /sys/power/pm_test) and resumes
bringing up X, gnome, consoles, mouse, keyboard - but not the nvme SSD.
Since I have the OS on that, no command relying
** Attachment added: "dmesg.devices"
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1855892/+attachment/5311725/+files/dmesg.devices
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pm-utils in Ubuntu.
cat /sys/kernel/debug/suspend_stats > suspend_stats
** Attachment added: "suspend_stats"
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1855892/+attachment/5311729/+files/suspend_stats
--
You received this bug notification because you are a member of Desktop
Packages, which is
Attaching the dumps of:
cat /proc/acpi/wakeup > wakeup
echo > /sys/power/pm_test
sync && echo 1 > /sys/power/pm_trace && pm-suspend
dmesg > dmesg.
** Attachment added: "wakeup"
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1855892/+attachment/5311723/+files/wakeup
--
** Attachment added: "dmesg.core"
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1855892/+attachment/5311728/+files/dmesg.core
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pm-utils in Ubuntu.
** Attachment added: "dmesg.platform"
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1855892/+attachment/5311726/+files/dmesg.platform
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pm-utils in Ubuntu.
** Attachment added: "dmesg.freezer"
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1855892/+attachment/5311724/+files/dmesg.freezer
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pm-utils in Ubuntu.
** Attachment added: "dmesg.processors"
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1855892/+attachment/5311727/+files/dmesg.processors
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pm-utils in Ubuntu.
** Attachment added: "dmesg after an unsuccesful wake (with nvme disk off) from
S3"
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1855892/+attachment/5311508/+files/dmesg.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Public bug reported:
System apparently correctly suspends (in various ways - from gnome menu,
with pm-suspend on bash, with echo ... > /sys/power/pm_test) and resumes
bringing up X, gnome, consoles, mouse, keyboard - but not the nvme SSD.
Since I have the OS on that, no command relying on disk
Led by
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1250314/comments/2
, I tried 'rm ~/.local/share/zeitgeist -R', and that solved the problem
for me.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
Same happens with gedit 3.10.1 installed as described in
http://linuxg.net/how-to-install-gedit-3-9-3-on-ubuntu-13-10-saucy-
salamander-ubuntu-13-04-raring-ringtail-and-linux-mint-15-olivia/
However, that happens only usign gnome or gnome-flashback or fvwm-
crystal as session manager; gedit opens
There was a button for it, I removed the link to #26662 as duplicate.
** This bug is no longer a duplicate of bug 26662
using the filename to get the mimetype is not always correct
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
** Description changed:
- obvious checks in alsamixer, pavucontrol, System settings/Sound -
- capture input is turned on, unmuted. Yet no app receives input sound.
+ obvious checks in alsamixer, pavucontrol, System settings/Sound - capture
input is turned on, unmuted, mic is ok on another pc.
Public bug reported:
obvious checks in alsamixer, pavucontrol, System settings/Sound -
capture input is turned on, unmuted. Yet no app receives input sound.
Full config submitted also as http://www.alsa-
project.org/db/?f=01d87fcb289265cb4c8cb8a7067410778b88f09d
ProblemType: Bug
DistroRelease:
16 matches
Mail list logo
