this worked for me to set all profiles as I wanted in 20.04
$ val='@ms
For my reference later.
The 'dconf read' with ':list' syntax has changed, so the comments above don't
work in 18.04.
Updated, this worked for me:
$ dconf list /org/gnome/terminal/legacy/profiles:/
:b1dcc9dd-5262-4d8d-a863-c897e6d979b9/
$ dconf write
Well, I think I found out what was happening.
In gnome-tweaks I had somehow gotten 'Workspaces' -> 'Display Handling'
set to 'Workspaces on primary display only'.
So what happened was that there was only a single workspace on the
"second" head and thus no need for "always on visible workspace".
I just now realized that this issue only occurs when the window is on my
"second" monitor.
If move the window to the primary display then the window menu has
Minimize, Maximize, Move, Resize, Always on Top, Always on Visible
Workspace, Move Workspace Down, Move to Monitor Right, Close
But on
Well, after an upgrade and reboot (including mutter 3.30.1-1), 'alt
space' now works to bring up the m enu.
However, there is no 'Always on visible workspace' option.
So I will close this bug as 'fix released' and I have opened bug
1797120.
** Changed in: mutter (Ubuntu)
Status: New =>
Public bug reported:
I filed bug 1795410 a few weeks ago complaining that the 'alt space'
didn't bring up the window menu. That is now fixed (seemingly likely
with mutter 3.3.0-6).
However, the window menu that does come up does not have an entry for
'Always on visible workspace' as it used to.
As a work around, I just configured some short cut (super w) to 'Toggle
window on all workspaces or one' in the gnome-control-center and that
seems to function.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
** Also affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1751797
Title:
dns resolution only works for
** No longer affects: maas
** No longer affects: nplan (Ubuntu)
** No longer affects: systemd (Ubuntu)
** Changed in: cloud-init
Status: New => Confirmed
** Changed in: cloud-init
Importance: Undecided => Medium
** Changed in: cloud-init
Assignee: (unassigned) => Ryan Harper
** Summary changed:
- transient boot fail with overlayroot
+ transient boot fail with overlayroot [open-iscsi dep8 tests]
** Attachment added: "bionic failure log 2.0.874-5ubuntu2
qemu/1:2.11+dfsg-1ubuntu2"
Public bug reported:
After reboot, dns was broken.
I've attached systemd-resolve --status output.
In order to file the bug I just modified /etc/resolv.conf to put the dns
server in directly.
Other information, it seems like it just will only look for dns under my
search domains from the dhcp
** Description changed:
1. $ lsb_release -rd
Description: Ubuntu 17.10
Release: 17.10
2. $ apt-cache policy linux-image-`uname -r`
linux-image-4.13.0-16-generic:
- Installed: 4.13.0-16.19
- Candidate: 4.13.0-16.19
- Version table:
- *** 4.13.0-16.19 500
- 500
I just ran into this today:
Setting up avahi-utils (0.7-3.1ubuntu1) ...
dpkg: cycle found while processing triggers:
chain of packages whose triggers are or may be responsible:
gnome-menus -> ufw
packages' pending triggers which are or may be unresolvable:
gnome-menus:
Marked as fix-released.
I tested today with 20180115.1 image from bionic.
wget http://cloud-images.ubuntu.com/bionic/20180115.1/bionic-server-
cloudimg-amd64.img -O bionic-server-cloudimg-amd64.img
url="https://smoser.brickies.net/ubuntu/nocloud/;
qemu-system-x86_64 -enable-kvm -m 768 \
-net
Well, I do not have 'Sticky keys' enabled now, and I doubt I ever did.
It really felt to me that the lock screen and "everything else" seemed to keep
independent state for shift (or caps lock possibly), and I happened to get them
out of sync.
I'm fine for this bug to expire, but figure I'd at
This bug is believed to be fixed in cloud-init in 1705804. If this is
still a problem for you, please make a comment and set the state back to
New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of
zesty does not show this problem. neither does xenial. I reflected that
in the status.
** Changed in: cloud-init (Ubuntu Artful)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu Artful)
Importance: Undecided => Medium
** Changed in: cloud-init (Ubuntu Artful)
Importance:
$ wget http://cloud-images.ubuntu.com/artful/20171122/artful-server-
cloudimg-amd64.img
## set up dns locally for 'qemu-host' to the default ip for user networking.
$ grep qemu-host /etc/hosts
10.0.2.2 qemu-host
$ cat data/user-data
#cloud-config
password: passw0rd
chpasswd: { expire: False }
This issue is discussed in a document at
https://docs.google.com/document/d/14xH2Q3VH_7ArXzRPhqogfACeOI0rmEinm_Q98imNWlc/
Its all about "transition" of networking information from the initramfs
environment which is configured by the kernel command line over to the
"real root".
The Ubuntu
Public bug reported:
This issue keeps cropping up. It shows itself in open-iscsi autopkg tests.
I think it might just be "really slow system". It seems the timeout is only
1 minute 30 seconds for the disk to appear, and in a happy run you
might see something very close:
[K[
Public bug reported:
I noticed that lxd (lxc list) reports that an lxc container has an ipv6
address in artful or bionic. It does not list this in xenial or zesty.
I suspect this change occurred in the switch over to netplan/networkd.
This may at first seem harmless or even desired, but note
Public bug reported:
I'm seeing very slow 'sudo' times in a qemu guest when the host uses
systemd-resolved.
If I change /etc/resolv.conf on the host to point directly to a dns server
(8.8.8.8) then the problem goes away.
To recreate, you can download a cloud image and boot it under qemu with
Daniel,
You're right that shift doesn't dismiss the lock screen.
I've asked some others to try to reproduce and they have failed also.
I think what is happening might instead be related to me hitting the
'shift' key repeatedly as my screen is going to sleep. It seems that
that causes an issue
Public bug reported:
Summary: hitting 'shift' before typing your password can get "stuck" down and
cause you to not be able to log in.
I have a habit of using the shift key wake the display of my system
after i've been away from it for a while, and then typing my password.
I started having
** Changed in: cloud-initramfs-tools (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1713803
Title:
replacement of resolvconf with systemd
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Fix Committed
** Changed in: cloud-init
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
This bug is believed to be fixed in cloud-init in 17.1. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of
Public bug reported:
In Ubuntu artful, cloud-init renders network configuration through netplan.
This means that there is no dhclient and thus no /var/lib/dhclient/*.leases.
Azure and CloudStack both are reading those leases file to get useful
information about the platform.
Specifically:
*
I've added open-iscsi and cloud-initramfs-tools and initramfs-tools as also
affects.
These packages are affected by the generic problem where 'configure_networking'
from initramfs-tools is executed in the initramfs ('ip=dhcp' for example) and
then the link is left up. In those cases we need to
Public bug reported:
There is a plan to remove resolvconf from the Ubuntu Server image.
resolvconf integrated with other parts of the system in 2 ways:
* hooks invoked on change (/etc/resolvconf/update.d/)
* resolvconf tool (invoked with -a and -d or -u)
Packages which install files into
Public bug reported:
Earlier this week on Zesty on Azure I saw a cloud-init failure in its
'mount_cb' function.
That function esentially does:
a.) make a tmp directory for a mount point
b.) mount some filesystem to that mount point
c.) call a function
d.) unmount the directory
What I
Public bug reported:
bcache devices do not have a watch on them from /lib/udev/rules.d/60-block.rules
The result is that this will fail:
mkfs.ext4 /dev/bcache0 -L foobar
udevadm settle
ls -l /dev/disk/by-label/foobar
where as it will work on
mkfs.ext4 /dev/vdb -L foobar
udevadm
The last screenshot (ipaddrdelifup.png) we think shows what went wrong.
Jason had an rtl device attached to this kvm vm. It doesn't seem to like
setting the MTU to 9000.
Possibly that is a bug in the driver, or possibly it is a limitation of the
(emulated or real) hardware.
2 fixes:
a.) do
** No longer affects: cloud-init
** No longer affects: cloud-init (Ubuntu)
** No longer affects: cloud-init (Ubuntu Xenial)
** No longer affects: cloud-init (Ubuntu Yakkety)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd
** Also affects: systemd (Ubuntu Zesty)
Importance: Undecided
Status: Confirmed
** Also affects: systemd (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu
** Also affects: cloud-init
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1636912
Title:
systemd-networkd runs too late for
** Changed in: cloud-init (Ubuntu)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1636912
Title:
systemd-networkd runs too late for
Public bug reported:
$ lxc launch ubuntu-daily:yakkety y-hostname1
$ sleep 10
$ lxc exec y-hostname1 -- hostnamectl set-hostname smoser
Could not set property: Connection timed out
$ lxc exec y-hostname1 -- systemctl status --no-pager -l systemd-hostnamed
● systemd-hostnamed.service - Hostname
atkins) => Scott Moser (smoser)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1629797
Title:
resolve service in nsswitch.conf adds 25 seconds to failed lookups
before systemd
Public bug reported:
$ lxc launch ubuntu-daily:yakkety y4
$ lxc exec y3 -- systemctl list-jobs
JOB UNITTYPE STATE
5 dev-sda2.device start running
1 jobs listed.
$ lxc exec y3 -- cat /etc/cloud/build.info
build_name: server
serial: 20160902
$ lxc exec y3 -- systemd-analyze
fix is now released to xenial under bug 1595302. daily cloud-images
with this newer version of cloud-init should appear in the next few
days. Any image with a serial number *newer* than 20160707 should have
cloud-init at 0.7.7~bzr1246-0ubuntu1~16.04.1 .
** Changed in: cloud-init (Ubuntu Xenial)
signed) => Scott Moser (smoser)
** Changed in: cloud-init (Ubuntu Xenial)
Assignee: (unassigned) => Scott Moser (smoser)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/15
** Description changed:
We're interested in supporting network configuration of lxc containers
via maas/cloud-init yaml format.
The end goal is to do:
$ lxc init xenial x1
# enter into container and modify
/var/lib/cloud/seed/nocloud-net/network-config
# to have something like:
Public bug reported:
We're interested in supporting network configuration of lxc containers
via maas/cloud-init yaml format.
The end goal is to do:
$ lxc init xenial x1
# enter into container and modify /var/lib/cloud/seed/nocloud-net/network-config
# to have something like:
% cat
** Description changed:
Using the following cloud config, apache2 will fail to start on
installation on Xenial:
#cloud-config
packages:
- apache2
See for example:
$ gcloud compute instances create xenial-$(date +%y%m%d-%H%M) --image
ubuntu-1604-xenial-v20160420c
Public bug reported:
The ubuntu:xenial image shows 'degraded' state in lxd on initial boot.
$ lxc launch xenial x1
$ sleep 10
$ lxc file pull x1/etc/cloud/build.info -
build_name: server
serial: 20160420-145324
$ lxc exc x1 systemctl is-system-running
degraded
$ lxc exec x1 systemctl
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1571761
Title:
zfs-import-cache.service slows boot
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Tags added: systemd-boot
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1571761
Title:
** Summary changed:
- highlighting on left mouse double click ends at :
+ highlighting on left mouse double click ends at : (colon)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
Public bug reported:
provided is user-data that should write:
[stdout] Tue, 23 Jun 2015 20:17:52 + == successfull boot 1 ===
to the console on the first boot.
currently in wily, rc.local's output is not being written to the
console, so you wont see this.
Related bugs:
* bug
Public bug reported:
per https://www.debian.org/doc/manuals/debian-faq/ch-customizing.en.html
| The rc.local script is executed at the end of each multiuser runlevel.
Generally speaking people expect rc.local to be run as the last thing
in boot.
currently it is being run by systemd much
** Changed in: maas-images
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1391354
Title:
Failure to boot ephemeral image for Utopic Fast
** Changed in: gnome-terminal (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1463072
Title:
highlighting on left mouse double
I marked this as Invalid as upstream says it is.
It is configurable via dconf. currently not configurable in the gnome-terminal
UI at all.
To show how to do this:
$ dconf read /org/gnome/terminal/legacy/profiles:/list
['63575bfd-baa0-4acd-86fc-6726b91ff51e',
** Changed in: gnome-terminal (Ubuntu)
Status: New = Confirmed
** Changed in: gnome-terminal (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
Public bug reported:
I'm not perfectly sure when this regression occurred. I know that
3.14.2-0ubuntu4 did not have the issue, and that 3.16.2-1ubuntu1 does.
Its terribly annoying when copy and pasting links.
I'm not sure how this works or where the change occurred.
When i double click on a url
** Bug watch added: GNOME Bug Tracker #750577
https://bugzilla.gnome.org/show_bug.cgi?id=750577
** Also affects: gnome-terminal via
https://bugzilla.gnome.org/show_bug.cgi?id=750577
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
I've made this affect systemd as that is where I have the fix for it.
I could fix in open-iscsi as it was in upstart, but I think adding general
infrastructure that considers open-iscsi is more sane than open-iscsi playing
around with tricking ifupdown.
** Package changed: resolvconf (Ubuntu)
** Changed in: ubuntu
Status: New = Confirmed
** Changed in: ubuntu
Importance: Undecided = High
** Package changed: ubuntu = systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
After latest dist-upgrade, this is now fixed for me in trusty.
gnome-terminal is still 3.6.2-0ubuntu1
I suspect this came with a compiz. per viwing my history.log, when i filed this
bug I was probably running compiz-gnome at
0.9.11+14.04.20140305-0ubuntu1 .
And i'm now running
some more info, it seems it ends up being slightly smaller than the target size.
Ie, if I set default size up to 90x25, i get windows that are 89x29.
80x25 goes to 79x23.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal
Public bug reported:
I have settings in gnome-terminal that say Use custom default terminal
size to be 80x25.
$ gnome-terminal --profile=Default
launches a new terminal that is not that size.
See the picture attached
$ dpkg-query --show gnome-terminal
gnome-terminal 3.6.2-0ubuntu1
Not sure
a bit more info, you can see the failure by running:
gnome-terminal --geometry 100x25
you'll end up with a terminal some size other htan 100x25.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
** Changed in: glib2.0 (Ubuntu Lucid)
Importance: Undecided = Medium
** Changed in: glib2.0 (Ubuntu Lucid)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
** Description changed:
Some applications get stuck in a deadlock when utilizing glib. One of
examples is lrmadmin, when connecting to lrmd. Upstream provided a fix
for this bug and Ubuntu's version 11.04 and newer do not have this
issue.
Ubuntu 10.04 and 10.10 do not contain the
** Changed in: elinks (Ubuntu)
Status: New = Opinion
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to epiphany-browser in Ubuntu.
https://bugs.launchpad.net/bugs/888662
Title:
Web browsers should share the cache
To manage
I hit this just now.
chose to work around by rrmod uvcvideo and for good measure rm
/lib/modules/*/kernel/drivers/media/video/uvc/uvc*.ko
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gstreamer0.10 in Ubuntu.
Its possible you're seeing bug 905854 (Reinhard's is a bit older and
marked as fixed). but basically, indicator-multiload and unity dont get
a long.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu.
Public bug reported:
This occurred on 2 different precise systems I have.
To recreate:
* insert blank cdrom
* open banshee
* select some songs
* right-click on songs, select Write CD
* brasero opens
* in Brasero File - burn
* crash
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package:
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to brasero in Ubuntu.
https://bugs.launchpad.net/bugs/937158
Title:
brasero crashed with SIGABRT in raise()
To manage notifications about this bug go to:
This was fixed somewhere in the oneiric development cycle.
I suspect it was related to lightdm, but it is not reproducible now.
** Changed in: metacity (Ubuntu)
Status: Incomplete = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
hm.m. strike my lightdm comment above as I said that I saw it under
Xephyr.
I just tested here on precise development system:
{ echo '#!/bin/sh'; echo metacity ; echo xterm; } /tmp/go ;
chmod 755 /tmp/go ;
xinit /tmp/go -- $(which Xephyr) :8
$ dpkg-query --show metacity xserver-xephyr
** Attachment added: lsof and initial (non-repeating) .xsession-errors file
https://bugs.launchpad.net/bugs/877420/+attachment/2557038/+files/debug-info.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
Public bug reported:
I'm logged into unity-2d, for at least 392245 seconds (per 'echo
$SECONDS' in a terminal i had open). That is ~ 108 hours, just over 4
days.
$ ls -altr .xsession-errors
-rw--- 1 smoser smoser 1433954001 2011-10-18 09:17 .xsession-errors
I've filed this bug against
$ dpkg-query --show indicator-multiload
indicator-multiload 0.2-0+33~17~16~oneiric1
I just noticed the 'glibtop', and the suspected indicator-multiload. I
did a 'tail -f .xsession-errors' and then closed indicator-multiload and
the log entries immediately stopped.
** Package changed:
In my reading of the bug above, it appears this is still open because:
| Added P-Series tasks for improving the human-readable text for the CUPS
| printer state reason connecting-to-device
I don't think this is ready for sponsorship or upload then for P, and am then
going to unsubscribe
This is a regression within the last few days. Definitely I did not see
this problem 1 week ago.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu.
https://bugs.launchpad.net/bugs/862813
Title:
Power
or i guess more likely in the new upstream release
(https://lists.ubuntu.com/archives/oneiric-
changes/2011-September/010417.html).
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu.
Using nothing other than changelog entries, i suspect regression
occurred here https://lists.ubuntu.com/archives/oneiric-
changes/2011-September/010574.html .
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in
Public bug reported:
After suspend, I'm unable to log in to gnome-screensaver.
Switching to a console, I can see that gnome-screensaver and
gnome-screensaver-dialog are running.
The dialog which would normally allow login is simply grey.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package:
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/802572
Title:
cannot login after suspend -- empty grey box
To manage notifications about this bug go to:
I've created a brand new user, login via recovery console, start metacity and
I see this.
It also reproduces under Xephyr. i can't manage to get metacity to work at all.
** Changed in: metacity (Ubuntu)
Importance: Undecided = High
** Changed in: metacity (Ubuntu)
Status: New =
** Changed in: gnome-panel (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-panel in Ubuntu.
https://bugs.launchpad.net/bugs/726558
Title:
drawer in gnome-panel was emptied on upgrade
Public bug reported:
Binary package hint: gnome-panel
I did a upgrade today on my natty system where I use the Classic Desktop.
In my panel I have 1 drawer. Prior to upgrade it had 3 launchers in it, after
upgrade it was empty.
This is the second time this has happened during the natty
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-panel in ubuntu.
https://bugs.launchpad.net/bugs/726558
Title:
drawer in gnome-panel was emptied on upgrade
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
I put together a branch with the patch for easier merging for someone
with rights to commit, and put a build in my ppa of 'metacity -
1:2.30.1-0ubuntu1.1~ppa0' (https://launchpad.net/~smoser/+archive/ppa).
If someone subscribed here could test that build and report back, it
would make it even
I'm not able reproduce this, just successfully connected to a vnc4server
vncserver running in 10.04 using vinagre 2.30.3-1ubuntu2.
That doesn't mean its not a bug, though.
@Jean-Louis,
A few things things.
a.) Thanks for taking the time to open the bug and find a fix!
b.) the vinagre package
Some applications disable the screensaver (and power management) when they're
running. qemu is one such application.
The times I've seen this were when I was running qemu.
you can stop qemu (and actually, all SDL applications) from disabling
the screensaver by putting
For me, one source of this problem is qemu/kvm. http://bugs.debian.org
/cgi-bin/bugreport.cgi?bug=578672 suggests setting
SDL_VIDEO_ALLOW_SCREENSAVER=1 .
** Bug watch added: Debian Bug tracker #578672
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=578672
--
power management does not
I've also seen this both on karmic and on lucid. I've no easy way to
reproduce it, nor a way to fix it (other than log out, log back in or
reboot).
One thing I noticed yesterday, was that 'xset dpms force off' would turn
off the monitors (both LCD of laptop and external monitor) but then
after a
For ease in debugging I'm attaching the example usps label. When
printing labels it gives the option to print a sample. I just saved
that example and attach here. It crashes evince, but is fine with xpdf.
The gdb backtrace looks the same as that attached above.
** Attachment added: Example
92 matches
Mail list logo
