Adding that there is a key "Placement" in org.gnome.gnome-
flashback.desktop.icons, which can be {'auto-arrange-icons','align-
icons-to-grid','free'}. However it doesn't help to set it in dconf-
editor, it is always resetted to auto. Unsurprising if unimplemented
otherwise, but I wish it was...
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855892
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 Ubuntu
Bugs, which is
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855892
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855892
** 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 Ubuntu
Bugs, which is subscribed to 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 Ubuntu
Bugs, which is subscribed to 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 Ubuntu
Bugs, 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
Public bug reported:
Ubuntu 13.10, visual-regexp 3.1-3ubuntu1.
traceback:
$ visual-regexp
0
Error in startup script: can't read data(w:menu): no such element in array
while executing
$data(w:menu) delete [expr 4+[llength $::regexp_db]/2] end
(procedure regexp::pattern:load line 14)
** Description changed:
Ubuntu 13.10, visual-regexp 3.1-3ubuntu1.
traceback:
$ visual-regexp
0
Error in startup script: can't read data(w:menu): no such element in array
- while executing
+ while executing
$data(w:menu) delete [expr 4+[llength $::regexp_db]/2] end
-
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
Isn't this a duplicate of bug 901289 ? The easy patch posted there WFM.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1022684
Title:
xpdf wrapper script prevents use of many -options
To manage
** 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:
I could start it in the following qd way in Lucid Lynx:
after building libhocr-0.10.17 and sudo make install, hocr-gtk is located for
me in /usr/local/bin, and hocr.py* lands in
/usr/local/lib/python2.6/site-packages.
I added the following two lines just before line 34 of /usr/local/bin/hocr-gtk
20 matches
Mail list logo
