[Bug 1463072] Re: highlighting on left mouse double click ends at : (colon)
this worked for me to set all profiles as I wanted in 20.04 $ val='@ms
[Bug 1463072] Re: highlighting on left mouse double click ends at : (colon)
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 /org/gnome/terminal/legacy/profiles:/:b1dcc9dd-5262-4d8d-a863-c897e6d979b9 /word-char-exceptions '@ms
[Bug 1797120] Re: window menu does not include 'always on visible workspace'
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'm going to close this as 'Invalid'. ** Changed in: mutter (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1797120 Title: window menu does not include 'always on visible workspace' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1797120/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797120] Re: window menu does not include '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 the second monitor (the one the right) the 'Always on Visible Workspace' option is missing. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1797120 Title: window menu does not include 'always on visible workspace' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1797120/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795410] Re: cannot bring up window menu via keybinding (alt-space or otherwise)
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 => Fix Released ** Changed in: mutter (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1795410 Title: cannot bring up window menu via keybinding (alt-space or otherwise) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1795410/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797120] [NEW] window menu does not include 'always on visible workspace'
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. You can still create a custom shortcut in the gnome-control-center to toggle this, but that is not as useful or discoverable as in the window menu. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: mutter 3.30.1-1 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 10 09:21:40 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2015-07-23 (1175 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1797120 Title: window menu does not include 'always on visible workspace' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1797120/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795410] Re: cannot bring up window menu via keybinding (alt-space or otherwise)
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. https://bugs.launchpad.net/bugs/1795410 Title: cannot bring up window menu via keybinding (alt-space or otherwise) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1795410/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1749722] Re: NTP: take into account systemd-timesyncd where present
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 member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1749722 Title: NTP: take into account systemd-timesyncd where present To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1749722/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1751797] Re: dns resolution only works for domains in 'search'.
** 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 domains in 'search'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1751797/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1750884] Re: [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, leads to no DNS resolution
** 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 (raharper) -- 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/1750884 Title: [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, leads to no DNS resolution To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1750884/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1732028] Re: transient boot fail with overlayroot [open-iscsi dep8 tests]
** 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" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1732028/+attachment/5063566/+files/log.gz ** Summary changed: - transient boot fail with overlayroot [open-iscsi dep8 tests] + transient boot fail with overlayroot [open-iscsi autopkg tests] ** Also affects: open-iscsi (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/1732028 Title: transient boot fail with overlayroot [open-iscsi autopkg tests] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1732028/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1751797] [NEW] dns resolution only works for domains in 'search'.
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 server: $ systemd-resolve home.mosers.us home.mosers.us: 23.28.108.176 -- Information acquired via protocol DNS in 1.5ms. -- Data is authenticated: no $ systemd-resolve google.com google.com: resolve call failed: No appropriate name servers or networks for name found ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 26 09:35:32 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2015-07-23 (949 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic root=UUID=f897b32a-eacf-4191-9717-844918947069 ro quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.vendor: Intel Corporation ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "output of systemd-resolve --status" https://bugs.launchpad.net/bugs/1751797/+attachment/5063476/+files/systemd-resolv-status.txt -- 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 domains in 'search'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1751797/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot
** 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 http://nova.clouds.archive.ubuntu.com/ubuntu artful/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 4.13.0-16.19 + Candidate: 4.13.0-16.19 + Version table: + *** 4.13.0-16.19 500 + 500 http://nova.clouds.archive.ubuntu.com/ubuntu artful/main amd64 Packages + 100 /var/lib/dpkg/status 3. After creating some bcache devices and rebooting /dev/bcache/by-uuid/ -> ../../bcacheN symlinks point to the current bcache device which is caching the dev.uuid found after creating a backing device. 4. /dev/bcache/by-uuid does not exist and there are not symlinks underneath - - It appears that since the initramfs loads the bcache module which probes and finds all of the cache devices and backing devices then once the rootfs is mounted and udev gets to run, the bcache kernel module does not emit the CACHED_UUID value into the environment if the underlying devices are already registered. + It appears that since the initramfs loads the bcache module which probes + and finds all of the cache devices and backing devices then once the + rootfs is mounted and udev gets to run, the bcache kernel module does + not emit the CACHED_UUID value into the environment if the underlying + devices are already registered. In dmesg, one can see that prior to mounting the rootfs, we see bcache register events: [5.333973] bcache: register_bdev() registered backing device vdb2 [5.354138] bcache: register_bdev() registered backing device vdb4 [5.365665] bcache: register_bdev() registered backing device vdb3 [5.397720] bcache: bch_journal_replay() journal replay done, 0 keys in 1 entries, seq 1 [5.428683] bcache: register_cache() registered cache device vdb1 then rootfs ismounted and systemd starts systemd-udev [9.350889] systemd[1]: Listening on udev Kernel Socket. And then the coldplug replay of kernel events triggers /lib/udev/rules.d/69-bcache.rules which invokes /lib/udev/bcache-register which writes the device name (/dev/vdb1 or /dev/bcache0) into /sys/fs/bcache/register and results is the bcache kernel driver attempting to register the block device. However, there is already a bcache device associated already and registration fails [ 11.173141] bcache: register_bcache() error opening /dev/vdb2: device already registered [ 11.184617] bcache: register_bcache() error opening /dev/vdb3: device already registered [ 11.199130] bcache: register_bcache() error opening /dev/vdb1: device already registered [ 11.271694] bcache: register_bcache() error opening /dev/vdb4: device already registered The problem then is that only a kernel call to bch_cached_dev_run() which happens like this: bcache_register() - register_bdev() - bch_cached_dev_run() - kobject_uevent_env(_to_dev(d->disk)->kobj, KOBJ_CHANGE, env); - - where env includes: - "DRIVER=bcache", - kasprintf(GFP_KERNEL, "CACHED_UUID=%pU", dc->sb.uuid), - NULL, - NULL, - }; + register_bdev() + bch_cached_dev_run() + kobject_uevent_env(_to_dev(d->disk)->kobj, KOBJ_CHANGE, env); + + where env includes: + "DRIVER=bcache", + kasprintf(GFP_KERNEL, "CACHED_UUID=%pU", dc->sb.uuid), + NULL, + NULL, + }; Since that event is not emitted for any previously registered device, then the symlink will not be created. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: User Name 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 AlsaDevices: - total 0 - crw-rw 1 root audio 116, 1 Oct 31 22:09 seq - crw-rw 1 root audio 116, 33 Oct 31 22:09 timer + total 0 + crw-rw 1 root audio 116, 1 Oct 31 22:09 seq + crw-rw 1 root audio 116, 33 Oct 31 22:09 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Wed Nov 1 01:39:01 2017 Ec2AMI: ami-030b Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: - Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd - Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Bus 001 Device 002: ID 0627:0001 Adomax Technology Co.,
[Bug 1738194] Re: gnome-menus 3.13.3-6ubuntu5 failed to install/upgrade: triggers looping, abandoned - gnome-menus -> gconf2
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: /usr/share/applications libc-bin: ldconfig shim-signed: shim-secureboot-policy gconf2: /usr/share/GConf/gsettings: /usr/share/gconf/schemas ufw: /etc/ufw/applications.d dpkg: error processing package gnome-menus (--configure): triggers looping, abandoned ... Errors were encountered while processing: gnome-menus ... Setting up gnome-menus (3.13.3-11ubuntu1) ... ... Errors were encountered while processing:^M gnome-menus^M E: Sub-process /usr/bin/dpkg returned an error code (1) ** Attachment added: "log of apt-get dist-upgrade with failure" https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1738194/+attachment/5053607/+files/failed-upgrade.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1738194 Title: gnome-menus 3.13.3-6ubuntu5 failed to install/upgrade: triggers looping, abandoned - gnome-menus -> gconf2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1738194/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1734167] Re: DNS doesn't work in no-cloud as launched by ubuntu
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 nic -net user \
-drive file=disk.img,if=virtio \
-smbios "type=1,serial=ds=nocloud-net;s=$url"
Just for info, showing:
$ curl https://smoser.brickies.net/ubuntu/nocloud/user-data
#cloud-config
password: passw0rd
chpasswd: { expire: False }
ssh_pwauth: True
$ curl https://smoser.brickies.net/ubuntu/nocloud/meta-data
instance-id: iid-brickies-nocloud
** No longer affects: cloud-init (Ubuntu Bionic)
** Changed in: cloud-init (Ubuntu)
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/1734167
Title:
DNS doesn't work in no-cloud as launched by ubuntu
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1734167/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1730478] Re: using shift key to wake up display causes invalid password
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 least fill in the remaining info. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1730478 Title: using shift key to wake up display causes invalid password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1730478/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1718029] Re: cloudstack and azure datasources broken when using netplan/systemd-networkd
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 Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1718029 Title: cloudstack and azure datasources broken when using netplan/systemd- networkd To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1718029/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1734167] Re: DNS doesn't work in no-cloud as launched by ubuntu
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: Medium => High ** Changed in: systemd (Ubuntu Artful) Status: New => Confirmed ** Changed in: systemd (Ubuntu Artful) Importance: Undecided => High ** Changed in: systemd (Ubuntu Zesty) Status: New => Confirmed ** Changed in: systemd (Ubuntu Zesty) Status: Confirmed => Fix Released ** Changed in: cloud-init (Ubuntu Zesty) Status: New => 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/1734167 Title: DNS doesn't work in no-cloud as launched by ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1734167/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1734167] Re: DNS doesn't work in no-cloud as launched by ubuntu
$ 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 }
ssh_pwauth: True
$ cat data/meta-data
instance-id: i-test
## webserv is
http://bazaar.launchpad.net/~curtin-dev/curtin/trunk/view/head:/tools/webserv
$ webserve 44225 data
:: 44225
## backdoor the image so you can login with 'backdoor:passw0rd'
# backdoor-image is
http://bazaar.launchpad.net/~smoser/+junk/backdoor-image/view/head:/backdoor-image
$ sudo backdoor-image -v --password=passw0rd
$ url="http://qemu-host:44225/;
$ qemu-system-x86_64 -enable-kvm \
-device virtio-net-pci,netdev=net00 \
-netdev type=user,id=net00 \
-drive
file=artful-server-cloudimg-amd64.img,id=disk00,if=none,format=qcow2,index=0 \
-device virtio-blk,drive=disk00,serial=artful-server-cloudimg-amd64.img \
-vga none -nographic -snapshot -echr 0x5 \
-smbios type=1,serial=ds=nocloud-net;s=$url" -m 768
## console does show
## [ 20.388179] cloud-init[606]: 2017-11-24 17:03:13,786 - util.py[WARNING]:
Gett
## ing data from
failed
## login
$ pastebinit /var/log/cloud-init.log
http://paste.ubuntu.com/26035544/
## interesting part of that is
2017-11-24 17:03:12,779 - url_helper.py[DEBUG]: [9/11] open
'http://qemu-host:44667/meta-data' with {'url':
'http://qemu-host:44667/meta-data', 'allow_redirects': True, 'method': 'GET',
'headers': {'User-Agent': 'Cloud-Init/17.1'}} configuration
2017-11-24 17:03:12,782 - url_helper.py[DEBUG]: Please wait 1 seconds while we
wait to try again
2017-11-24 17:03:13,783 - url_helper.py[DEBUG]: [10/11] open
'http://qemu-host:44667/meta-data' with {'url':
'http://qemu-host:44667/meta-data', 'allow_redirects': True, 'method': 'GET',
'headers': {'User-Agent': 'Cloud-Init/17.1'}} configuration
2017-11-24 17:03:13,786 - handlers.py[DEBUG]: finish:
init-network/search-NoCloudNet: FAIL: no network data found from
DataSourceNoCloudNet
2017-11-24 17:03:13,786 - util.py[WARNING]: Getting data from failed
2017-11-24 17:03:13,794 - util.py[DEBUG]: Getting data from failed
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/cloudinit/sources/__init__.py", line
332, in find_source
if s.get_data():
File "/usr/lib/python3/dist-packages/cloudinit/sources/DataSourceNoCloud.py",
line 157, in get_data
(md_seed, ud) = util.read_seeded(seedfrom, timeout=None)
File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 932, in
read_seeded
md_resp = read_file_or_url(md_url, timeout, retries, file_retries)
File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 892, in
read_file_or_url
exception_cb=exception_cb)
File "/usr/lib/python3/dist-packages/cloudinit/url_helper.py", line 270, in
readurl
raise excps[-1]
cloudinit.url_helper.UrlError: HTTPConnectionPool(host='qemu-host',
port=44667): Max retries exceeded with url: /meta-data (Caused by
NewConnectionError(': Failed to establish a new connection: [Errno -3] Temporary
failure in name resolution',))
2017-11-24 17:03:13,802 - handlers.py[DEBUG]: start: init-network/search-None:
searching for network data from DataSourceNone
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Also affects: systemd (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/1734167
Title:
DNS doesn't work in no-cloud as launched by ubuntu
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1734167/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1732522] Re: [2.3] Ephemeral boot environment does not renew DHCP leases
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 foundations team is expecting to have dhcp transition correctly in 18.04. ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Also affects: cloud-initramfs-tools (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/1732522 Title: [2.3] Ephemeral boot environment does not renew DHCP leases To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1732522/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1732028] [NEW] transient boot fail with overlayroot
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[ [0;31m*[0;1;31m*[0m[0;31m*[0m] A start job is running for dev-disk…-UEFI.device (1min 29s / 1min 32s) [K[ [0;31m*[0;1;31m*[0m[0;31m* [0m] A start job is running for dev-disk…-UEFI.device (1min 30s / 1min 32s) [K[[0;32m OK [0m] Found device VIRTUAL-DISK UEFI. Mounting /boot/efi... --- There is information on the open-iscsi tests at [1]. [1] https://git.launchpad.net/~usd-import-team/ubuntu/+source/open-iscsi/tree/debian/tests/README-boot-test.md The tests set up an iscsi target and boot a kvm guest off that read-only root with overlayroot. # get open-iscsi source $ apt-get source open-iscsi $ cd open-iscsi-2.0.874/ $ sudo apt-get install -qy simplestreams tgt qemu-system-x86 \ cloud-image-utils distro-info $ cd open-iscsi-2.0.874/ ## we're now mostly following debian/tests/README-boot-test.md # download the image and get kernel/initrd $ PATH=$PWD/debian/tests:$PATH $ get-image bionic.d bionic $ sudo `which patch-image` \ --kernel=bionic.d/kernel --initrd=bionic.d/initrd bionic.d/disk.img $ tgt-boot-test -v bionic.d/disk.img bionic.d/kernel bionic.d/initrd Success is being able to log in with 'ubuntu' and 'passw0rd'. Failure as seen in the log is dropping into an emergency shell. Once inside (this was successful) you'll see a mostly sane system. Some things to note: a.) tgt-boot-test boots without kvm enabled. This is because using kvm with qemu in nested virt would cause system lockups. Its slower but more reliable to go wtihout. b.) under bug 1723183 I made overlayroot comment out the root filesystem from the rendered /etc/fstab. That was because systemd got confused and assumed that /media/root-ro had to be on top of /. c.) you can enable or disable kvm by setting _USE_KVM=0 or _USE_KVM=1 in your environment. $ grep -v "^# " /etc/fstab # # #LABEL=cloudimg-rootfs /media/root-ro/ ext4 ro,defaults,noauto 0 0 /media/root-ro/ / overlay lowerdir=/media/root-ro/,upperdir=/media/root-rw/overl ay/,workdir=/media/root-rw/overlay-workdir/_ 0 0 LABEL=UEFI /boot/efi vfat defaults 0 0 # overlayroot:fs-unsupported $ sudo blkid /dev/sda1: LABEL="cloudimg-rootfs" UUID="7b1980bd-9102-4356-8df0-ec7a0c062411" TYPE="ext4" PARTUUID="c0b5ace0-4703-4667-babb-3d38137cab88" /dev/sda15: LABEL="UEFI" UUID="B177-3CC9" TYPE="vfat" PARTUUID="0ab0b9fd-2c28-4724-857a-1559f0cf76ea" /dev/sda14: PARTUUID="221662d6-cab0-4290-ba1c-e72acf2bf193" $ cat /run/systemd/generator/local-fs.target.requires/boot-efi.mount # Automatically generated by systemd-fstab-generator [Unit] SourcePath=/etc/fstab Documentation=man:fstab(5) man:systemd-fstab-generator(8) Before=local-fs.target [Mount] Where=/boot/efi What=/dev/disk/by-label/UEFI Type=vfat Related bugs: * bug 1680197: Zesty deployments failing sporadically * bug 1723183: transient systemd ordering issue when using overlayroot ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 234-2ubuntu12 ProcVersionSignature: User Name 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu4 Architecture: amd64 Date: Mon Nov 13 21:06:36 2017 Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: TERM=vt220 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: nomodeset iscsi_initiator=maas-enlist iscsi_target_name=tgt-boot-test-7xuhwl iscsi_target_ip=10.0.12.2 iscsi_target_port=3260 iscsi_initiator=maas-enlist ip=maas-enlist:BOOTIF ro net.ifnames=0 BOOTIF_DEFAULT=eth0 root=/dev/disk/by-path/ip-10.0.12.2:3260-iscsi-tgt-boot-test-7xuhwl-lun-1-part1 overlayroot=tmpfs console=ttyS0 ds=nocloud-net;seedfrom=http://10.0.12.2:32600/ SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-artful dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-artful:cvnQEMU:ct1:cvrpc-i440fx-artful: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-artful dmi.sys.vendor: QEMU ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic uec-images ** Attachment added: "log from open-iscsi failure with debconf-1.5.64ubuntu2" https://bugs.launchpad.net/bugs/1732028/+attachment/5008460/+files/open-iscsi-2.0.874-4ubuntu3-with-debconf-1.5.64ubuntu2.log.gz -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu.
[Bug 1732002] [NEW] cloud images in lxc get ipv6 address
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 that the user configuration did not request ipv6 config, so its presence is a bug. $ for rel in xenial zesty artful bionic; do lxc launch ubuntu-daily:$rel $rel-demo; done Creating xenial-demo Starting xenial-demo .. Creating bionic-demo Starting bionic-demo $ sleep 10 $ lxc list $ lxc list +-+-+--+++---+ |NAME | STATE | IPV4 | IPV6 |TYPE| SNAPSHOTS | +-+-+--+++---+ | artful-demo | RUNNING | 10.75.205.208 (eth0) | fd42:eee5:7c43:3d62:3a42:611c:3f6f:1184 (eth0) | PERSISTENT | 0 | +-+-+--+++---+ | bionic-demo | RUNNING | 10.75.205.187 (eth0) | fd42:eee5:7c43:3d62:6f4:155b:39cc:fc3d (eth0) | PERSISTENT | 0 | +-+-+--+++---+ | xenial-demo | RUNNING | 10.75.205.143 (eth0) | | PERSISTENT | 0 | +-+-+--+++---+ | zesty-demo | RUNNING | 10.75.205.123 (eth0) | | PERSISTENT | 0 | +-+-+--+++---+ ## Here is the config that was provided by lxd $ lxc exec bionic-demo cat /var/lib/cloud/seed/nocloud-net/network-config version: 1 config: - type: physical name: eth0 subnets: - type: dhcp control: auto ## Here is the config that cloud-init rendered. $ lxc exec bionic-demo -- grep -v '^#' /etc/netplan/50-cloud-init.yaml network: version: 2 ethernets: eth0: dhcp4: true $ lxc exec bionic-demo cat /run/systemd/network/10-netplan-eth0.network [Match] Name=eth0 [Network] DHCP=ipv4 [DHCP] UseMTU=true RouteMetric=100 $ lxc exec bionic-demo -- systemctl status --no-pager --full systemd-networkd ● systemd-networkd.service - Network Service Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2017-11-13 18:37:34 UTC; 8min ago Docs: man:systemd-networkd.service(8) Main PID: 118 (systemd-network) Status: "Processing requests..." Tasks: 1 (limit: 4915) Memory: 2.0M CPU: 19ms CGroup: /system.slice/systemd-networkd.service └─118 /lib/systemd/systemd-networkd Nov 13 18:37:34 bionic-demo systemd[1]: Starting Network Service... Nov 13 18:37:34 bionic-demo systemd-networkd[118]: eth0: Gained IPv6LL Nov 13 18:37:34 bionic-demo systemd-networkd[118]: Enumeration completed Nov 13 18:37:34 bionic-demo systemd[1]: Started Network Service. Nov 13 18:37:37 bionic-demo systemd-networkd[118]: eth0: DHCPv6 address fd42:eee5:7c43:3d62:6f4:155b:39cc:fc3d/128 timeout preferred 3600 valid 3600 Nov 13 18:37:37 bionic-demo systemd-networkd[118]: eth0: DHCPv4 address 10.75.205.187/24 via 10.75.205.1 Nov 13 18:37:37 bionic-demo systemd-networkd[118]: Not connected to system bus, ignoring transient hostname. Nov 13 18:37:39 bionic-demo systemd-networkd[118]: eth0: Configured Nov 13 18:38:09 bionic-demo systemd-networkd[118]: Could not set hostname: Method call timed out ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nplan 0.30 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu4 Architecture: amd64 Date: Mon Nov 13 18:27:53 2017 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SourcePackage: nplan UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nplan (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic uec-images ** Also affects: systemd (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/1732002 Title: cloud images in lxc get ipv6 address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1732002/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com
[Bug 1730744] [NEW] sudo is slow (10 seconds) when hostname is not resolvable
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 a command line like: cloud-localds seed.img user-data meta-data qemu-system-x86_64 -enable-kvm \ -device virtio-net-pci,netdev=net00 \ -netdev type=user,id=net00 \ -drive file=root.img,id=disk00,if=none,index=0 \ -device virtio-blk,drive=disk00,serial=root.img \ -drive file=seed.img,id=disk01,if=none,index=1 \ -device virtio-blk,drive=disk01,serial=seed.img \ -m 768 Make sure that your hostname does not resolve (change it to 'bogus-host1'). Log into the guest and then just try sudo, you'll see something like: # time sudo ls sudo: unable to resolve host rooturl-trusty real0m10.029s user0m0.006s sys 0m0.011s ** Affects: systemd (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/1730744 Title: sudo is slow (10 seconds) when hostname is not resolvable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1730744/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1730478] Re: using shift key to wake up display causes invalid password
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 where the there is a split brain on the state of either caps lock or shift. I just noticed right now when trying to gpg sign something that *it* I had to put the caps lock key on *it* also. (this is the full screen dialog for gpg). I suspect that a reboot will cure this until I frantically start hitting 'shift' again when the screensaver is fading out. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1730478 Title: using shift key to wake up display causes invalid password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1730478/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1730478] [NEW] using shift key to wake up display causes invalid password
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 trouble logging in, as if my fingers weren't typing the right password. It took me a while to figure out what was going on, but i thought maybe that I'd inadvertantly hit 'caps-lock' and that was causing the issue. So I hit it again, and then logged in successfully. However, upon login I found that caps-lock was enabled. So to reproduce: a.) let the screen lock or lock it manually. b.) hit shift key (i hit left shift) c.) type password correctly: watch fail to login d.) note that you can hit caps-lock and then successfully login e.) note that after login, caps lock is set, that you didn't make this all up. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-screensaver 3.6.1-7ubuntu6 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 6 13:12:29 2017 EcryptfsInUse: Yes GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 300 InstallationDate: Installed on 2015-07-23 (837 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screensaver UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages wayland-session -- 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/1730478 Title: using shift key to wake up display causes invalid password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1730478/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1713803] Re: replacement of resolvconf with systemd needs integration
** 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 needs integration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android-androresolvd/+bug/1713803/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1718029] Re: cloudstack and azure datasources broken when using netplan/systemd-networkd
** 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 subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1718029 Title: cloudstack and azure datasources broken when using netplan/systemd- networkd To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1718029/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1707222] Re: usage of /tmp during boot is not safe due to systemd-tmpfiles-clean
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 Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1707222 Title: usage of /tmp during boot is not safe due to systemd-tmpfiles-clean To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1707222/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1718029] [NEW] cloudstack and azure datasources broken when using netplan/systemd-networkd
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:
* Azure reads option-245 from the dhclient response to find the IP address of
the metadata service.
* CloudStack reads the 'dhcp-server-identifier' option in the dhclient
response to get the address of the virtual router (metadata service). [1]
In ubuntu this happens to be done with systemd-networkd, so cloud-init
can possibly probably interact over the dbus with systemd-networkd to
get information. However that is less than ideal, as ultimately cloud-
init should not need to know that it systemd-networkd is involved. It
should be hidden via netplan. So there should be an interface to get
current networking configuratoin information from netplan including dhcp
lease response info.
--
[1]
http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/4.8/virtual_machines/user-data.html
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: cloud-init 0.7.9-280-ge626966e-0ubuntu1
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CloudName: Amazon - Ec2
Date: Mon Sep 18 19:56:40 2017
PackageArchitecture: all
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=C.UTF-8
SourcePackage: cloud-init
UpgradeStatus: No upgrade log present (probably fresh install)
user_data.txt:
#cloud-config
{}
** Affects: netplan
Importance: Undecided
Status: New
** Affects: cloud-init (Ubuntu)
Importance: Critical
Status: Confirmed
** Affects: nplan (Ubuntu)
Importance: Undecided
Status: New
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug artful uec-images
** Also affects: nplan (Ubuntu)
Importance: Undecided
Status: New
** Also affects: netplan
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Critical
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
--
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/1718029
Title:
cloudstack and azure datasources broken when using netplan/systemd-
networkd
To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1718029/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1713803] Re: replacement of resolvconf with systemd needs integration
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 apply the /etc/resolv.conf
changes from the initramfs to the "real root". I described how this *did* work
for the open-iscsi package in the past, but there was no centralized handling
of it (although there should have been).
** 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/1713803
Title:
replacement of resolvconf with systemd needs integration
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/android-androresolvd/+bug/1713803/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1713803] [NEW] replacement of resolvconf with systemd needs integration
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 /etc/resolvconf/update.d are:
- dnsmasq: This may be mostly covered by systemd-resolved itself (the dns
caching path).
- resolvconf: This probably isn't necessary in systemd-resolved path.
- unbound: This is another "validating, recursive, caching DNS resolver".
The list of Depends/Suggests/Recommends on resolvconf.
# for pkg in $(apt-cache rdepends resolvconf | grep -v openreso | grep -v
Reverse); do out=$(apt-cache show $pkg | grep resolvconf); src=$(apt-cache show
$pkg | awk '$1 == "Source:" { print $2 }'); [ -n "$src" ] || src=$pkg; case
"$out" in Depends:*resolvconf) r=depends;; Suggests:*) r=suggests;;
Recommends:*) r=recommends;; esac; echo "$r $src"; done | sort -u
depends android-androresolvd
recommends avahi
recommends dhcpcd5
recommends dibbler
recommends ndisc6
recommends whereami
suggests bind9
suggests dnscrypt-proxy
suggests dnsmasq
suggests dnssec-trigger
suggests fetchmail
suggests freedombox-setup
suggests isc-dhcp
suggests netscript-2.4
suggests openvpn
suggests postfix
suggests pppconfig
suggests pump
suggests resolvconf
suggests sendmail
suggests squid3
suggests vpnc
suggests vpnc-scripts
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: systemd 234-2ubuntu9
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
ApportVersion: 2.20.6-0ubuntu7
Architecture: amd64
Date: Tue Aug 29 18:53:50 2017
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=C.UTF-8
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic
root=UUID=f897b32a-eacf-4191-9717-844918947069 ro quiet splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.vendor: Intel Corporation
Related bugs:
* bug 1698181: Switch to netplan renderer in Artful
** Affects: android-androresolvd (Ubuntu)
Importance: Undecided
Status: New
** Affects: avahi (Ubuntu)
Importance: Undecided
Status: New
** Affects: bind9 (Ubuntu)
Importance: Undecided
Status: New
** Affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Affects: cloud-initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
** Affects: dhcpcd5 (Ubuntu)
Importance: Undecided
Status: New
** Affects: dibbler (Ubuntu)
Importance: Undecided
Status: New
** Affects: dnscrypt-proxy (Ubuntu)
Importance: Undecided
Status: New
** Affects: dnsmasq (Ubuntu)
Importance: Undecided
Status: New
** Affects: dnssec-trigger (Ubuntu)
Importance: Undecided
Status: New
** Affects: fetchmail (Ubuntu)
Importance: Undecided
Status: New
** Affects: freedombox-setup (Ubuntu)
Importance: Undecided
Status: New
** Affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
** Affects: isc-dhcp (Ubuntu)
Importance: Undecided
Status: New
** Affects: ndisc6 (Ubuntu)
Importance: Undecided
Status: New
** Affects: netscript-2.4 (Ubuntu)
Importance: Undecided
Status: New
** Affects: open-iscsi (Ubuntu)
Importance: Undecided
Status: New
** Affects: openvpn (Ubuntu)
Importance: Undecided
Status: New
** Affects: postfix (Ubuntu)
Importance: Undecided
Status: New
** Affects: pppconfig (Ubuntu)
Importance: Undecided
Status: New
** Affects: pump (Ubuntu)
Importance: Undecided
Status: New
** Affects: resolvconf (Ubuntu)
Importance: Undecided
Status: New
** Affects: sendmail (Ubuntu)
Importance: Undecided
Status: New
** Affects: squid3 (Ubuntu)
Importance: Undecided
Status: New
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Affects: unbound (Ubuntu)
Importance: Undecided
Status: New
** Affects: vpnc (Ubuntu)
Importance: Undecided
Status: New
** Affects: vpnc-scripts (Ubuntu)
Importance: Undecided
Status: New
** Affects: whereami (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug artful uec-images
** Also affects: unbound (Ubuntu)
Importance: Undecided
Status: New
** Also affects: resolvconf (Ubuntu)
Importance: Undecided
Status: New
** Also affects: dnsmasq (Ubuntu)
Importance: Undecided
Status: New
** Also affects: android-androresolvd (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
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
[Bug 1707222] [NEW] usage of /tmp during boot is not safe due to systemd-tmpfiles-clean
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 recall was that access to a file inside the mount point failed during 'c'. This seems possible as systemd-tmpfiles-clean may be running at the same time as cloud-init (cloud-init.service in this example). It seems that this service basically inhibits *any* other service from using tmp files. It's ordering statements are only: After=local-fs.target time-sync.target Before=shutdown.target So while in most cases only services that run early in the boot process like cloud-init will be affected, any service could have its tmp files removed. this service could take quite a long time to run if /tmp/ had been filled with lots of files in the previous boot. ** Affects: cloud-init Importance: Undecided Status: New ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Also affects: systemd (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/1707222 Title: usage of /tmp during boot is not safe due to systemd-tmpfiles-clean To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1707222/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1680597] [NEW] udev 60-block.rules does not watch bcache
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 settle ls -l /dev/disk/by-label/foobar We found this when chasing a curtin bug (bug 1680591). The result of it was that we were installing and an update-grub would choose to boot with root=/dev/bcache0 rather than UUID=. Related bugs: * bug 1680591: installed system boots with root=/dev/bcache0 rather than root=UUID when root is bcache ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: udev 232-19 ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5 Uname: Linux 4.9.0-15-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.4-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Thu Apr 6 16:28:59 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2015-07-23 (623 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-15-generic.efi.signed root=UUID=f897b32a-eacf-4191-9717-844918947069 ro quiet splash SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.vendor: Intel Corporation ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- 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/1680597 Title: udev 60-block.rules does not watch bcache To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1680597/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1671274] Re: network interface doesn't come up after installation in VM
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 not use mtu 9000 b.) use virtio devices ** No longer affects: cloud-init ** No longer affects: maas ** No longer affects: systemd (Ubuntu) ** Changed in: curtin 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/1671274 Title: network interface doesn't come up after installation in VM To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1671274/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1636912] Re: systemd-networkd runs too late for cloud-init.service (net)
** 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 in Ubuntu. https://bugs.launchpad.net/bugs/1636912 Title: systemd-networkd runs too late for cloud-init.service (net) To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1636912/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1647485] Re: NVMe symlinks broken by devices with spaces in model or serial strings
** 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 Xenial) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Trusty) Status: New => Confirmed ** Changed in: systemd (Ubuntu Xenial) Status: New => Confirmed ** Changed in: systemd (Ubuntu Yakkety) Status: New => Confirmed ** Changed in: systemd (Ubuntu Trusty) Importance: Undecided => High ** Changed in: systemd (Ubuntu Xenial) Importance: Undecided => High ** Changed in: systemd (Ubuntu Yakkety) Importance: Undecided => High ** Changed in: systemd (Ubuntu Zesty) Importance: Undecided => High -- 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/1647485 Title: NVMe symlinks broken by devices with spaces in model or serial strings To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1647485/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1636912] Re: systemd-networkd runs too late for cloud-init.service (net)
** 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 cloud-init.service (net) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1636912/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1636912] Re: systemd-networkd runs too late for cloud-init.service (net)
** 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 cloud-init.service (net) To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1636912/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1635382] [NEW] hostnamectl does not work
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 Service Loaded: loaded (/lib/systemd/system/systemd-hostnamed.service; static; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2016-10-20 19:19:16 UTC; 1min 9s ago Docs: man:systemd-hostnamed.service(8) man:hostname(5) man:machine-info(5) http://www.freedesktop.org/wiki/Software/systemd/hostnamed Process: 561 ExecStart=/lib/systemd/systemd-hostnamed (code=exited, status=225/NETWORK) Main PID: 561 (code=exited, status=225/NETWORK) Oct 20 19:19:16 y-hostname1 systemd[1]: Starting Hostname Service... Oct 20 19:19:16 y-hostname1 systemd[1]: systemd-hostnamed.service: Main process exited, code=exited, status=225/NETWORK Oct 20 19:19:16 y-hostname1 systemd[1]: Failed to start Hostname Service. Oct 20 19:19:16 y-hostname1 systemd[1]: systemd-hostnamed.service: Unit entered failed state. Oct 20 19:19:16 y-hostname1 systemd[1]: systemd-hostnamed.service: Failed with result 'exit-code'. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-9git1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Thu Oct 20 19:02:29 2016 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic.efi.signed root=UUID=f897b32a-eacf-4191-9717-844918947069 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.vendor: Intel Corporation ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug uec-images yakkety -- 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/1635382 Title: hostnamectl does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1635382/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1629797] Re: resolve service in nsswitch.conf adds 25 seconds to failed lookups before systemd-resolved is up
Intent is to work around this in cloud-init via 'Before=dbus.socket'. ** Changed in: cloud-init (Ubuntu) Status: Invalid => In Progress ** Changed in: cloud-init (Ubuntu) Importance: Undecided => Critical ** Changed in: cloud-init (Ubuntu) Assignee: Dan Watkins (daniel-thewatkins) => 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-resolved is up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1629797/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1620780] [NEW] dev-sda2.device job running and times out
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 Startup finished in 1min 30.373s (userspace) = 6d 2h 27min 41.963s $ lxc exec y3 -- journalctl > yakkety-lxd-journalctl.txt $ lxc exec y3 -- systemctl status dev-sda2.device ● dev-sda2.device Loaded: loaded Active: activating (tentative) since Tue 2016-09-06 18:38:31 UTC; 4min 39s ago Sep 06 18:40:01 y3 systemd[1]: dev-sda2.device: Job dev-sda2.device/start timed out. Sep 06 18:40:01 y3 systemd[1]: Timed out waiting for device dev-sda2.device. Sep 06 18:40:01 y3 systemd[1]: dev-sda2.device: Job dev-sda2.device/start failed with result 'timeout'. Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-5 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Tue Sep 6 18:38:48 2016 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9136-generic.efi.signed root=UUID=f897b32a-eacf-4191-9717-844918947069 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug uec-images yakkety ** Attachment added: "journalctl for container" https://bugs.launchpad.net/bugs/1620780/+attachment/4735665/+files/yakkety-lxd-journalctl.txt -- 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/1620780 Title: dev-sda2.device job running and times out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1620780/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1579130] Re: need to support renaming of devices in container and on first boot
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) Status: In Progress => 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/1579130 Title: need to support renaming of devices in container and on first boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1579130/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1579130] Re: need to support renaming of devices in container and on first boot
Hello, An SRU upload of cloud-init for 16.04 that contains a fix for this bug has been made under bug 1595302. Please track that bug if you are interested. ** Also affects: cloud-init (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: cloud-init (Ubuntu Xenial) Importance: Undecided => High ** Changed in: cloud-init (Ubuntu Xenial) Status: New => In Progress ** No longer affects: systemd (Ubuntu Xenial) ** Changed in: cloud-init (Ubuntu) Assignee: (unassigned) => 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/1579130 Title: need to support renaming of devices in container and on first boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1579130/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1579130] Re: need to support systemd.link renaming of devices in container
** 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: % cat /var/lib/cloud/seed/nocloud-net/network-config version: 1 config: - - type: physical - mac_address: "00:16:3e:3b:01:7a" - name: foo2 - subnets: - - type: dhcp - control: auto + - type: physical + mac_address: "00:16:3e:3b:01:7a" + name: foo2 + subnets: + - type: dhcp + control: auto $ lxc start x1 $ lxc exec x1 /bin/bash From inside we expect to have a device named 'foo2' at this point that has dhcp'd. + + We've run into a number of issues with this. + a.) we don't get coldplug events for devices in a container, so writing systemd.link (or 70-persistent-net.rules style udev rules files) wont "just work" to apply the name changes. + + b.) systemd.link does rename devices that have been renamed previously, and all lxd instance devices are renamed (from the kernel returned veth into 'eth0'). + That is implemented by check of /sys/devices/virtual/net/eth0/name_assign_type . Value of 4 means renamed. + + c.) systemd.link will not attempt to rename a device that does not have a driver. +To see that run: udevadm test-builtin net_setup_link /sys/class/net/eth0 +http://paste.ubuntu.com/16261974/ + + To force these systemd.link files to run in spite of 'b' on kvm guests + or bare metal, we have found that unbind and rebind of the device will + clear the state and rename would occur. that can be done as shown in + https://bugs.launchpad.net/ubuntu/+source/cloud- + init/+bug/1577844/comments/3 but since there is no 'driver' we cannot + unbind and rebind veth devices. + + Ultimately, we want to allow cloud-init to configure the system once and + then let renaming on reboots not require involvement of cloud-init. And + at the moment the ideal way to affect that would be through systemd.link + files such as /etc/systemd/network/50-cloud-init-foo2.link. + ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: udev 229-4ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Fri May 6 15:42:52 2016 MachineType: LENOVO 33672B7 ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) + TERM=xterm-256color + PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed root=UUID=19ac97d5-6973-4193-9a09-2e6bbfa38262 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G8ET96WW (2.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 33672B7 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG8ET96WW(2.56):bd12/18/2013:svnLENOVO:pn33672B7:pvrThinkPadX131e:rvnLENOVO:rn33672B7:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 33672B7 dmi.product.version: ThinkPad X131e dmi.sys.vendor: LENOVO ** Also affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Changed in: cloud-init (Ubuntu) Status: New => Confirmed ** Changed in: cloud-init (Ubuntu) Importance: Undecided => High ** 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: - % cat /var/lib/cloud/seed/nocloud-net/network-config + $ ncpath=/var/lib/cloud/seed/nocloud-net/network-config + $ sudo tee /var/lib/lxd/containers/x1/rootfs/$ncpath < into 'eth0'). - That is implemented by check of /sys/devices/virtual/net/eth0/name_assign_type . Value of 4 means renamed. + a.) we don't get coldplug events for devices in a container, so writing systemd.link (or 70-persistent-net.rules style udev rules files) wont "just work" to apply the name changes. - c.) systemd.link will not attempt to rename a device that does not have a driver. -To see that run: udevadm test-builtin net_setup_link /sys/class/net/eth0 -http://paste.ubuntu.com/16261974/ + b.) systemd.link does rename devices that have been renamed previously, and all lxd instance devices are renamed (from the kernel returned veth into 'eth0'). + That is implemented by check of /sys/devices/virtual/net/eth0/name_assign_type . Value of 4 means renamed. + + c.) systemd.link will not attempt to rename a device that does not have a
[Bug 1579130] [NEW] need to support systemd.link renaming of devices in container
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 /var/lib/cloud/seed/nocloud-net/network-config version: 1 config: - type: physical mac_address: "00:16:3e:3b:01:7a" name: foo2 subnets: - type: dhcp control: auto $ lxc start x1 $ lxc exec x1 /bin/bash >From inside we expect to have a device named 'foo2' at this point that has dhcp'd. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: udev 229-4ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Fri May 6 15:42:52 2016 MachineType: LENOVO 33672B7 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed root=UUID=19ac97d5-6973-4193-9a09-2e6bbfa38262 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G8ET96WW (2.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 33672B7 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG8ET96WW(2.56):bd12/18/2013:svnLENOVO:pn33672B7:pvrThinkPadX131e:rvnLENOVO:rn33672B7:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 33672B7 dmi.product.version: ThinkPad X131e dmi.sys.vendor: LENOVO ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug uec-images xenial -- 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/1579130 Title: need to support systemd.link renaming of devices in container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1579130/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1575572] Re: apache2 fails to start if installed via cloud config (on Xenial)
** 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 --image-project ubuntu-os-cloud --metadata-from-file user-data=cloud-config NAMEZONEMACHINE_TYPE PREEMPTIBLE INTERNAL_IP EXTERNAL_IPSTATUS xenial-160427-1050 europe-west1-d n1-standard-1 10.240.0.7 104.155.86.94 RUNNING $ ssh ubuntu@104.155.86.94 systemctl status apache2.service ● apache2.service - LSB: Apache2 web server -Loaded: loaded (/etc/init.d/apache2; bad; vendor preset: enabled) - Drop-In: /lib/systemd/system/apache2.service.d -└─apache2-systemd.conf -Active: inactive (dead) - Docs: man:systemd-sysv-generator(8) + Loaded: loaded (/etc/init.d/apache2; bad; vendor preset: enabled) + Drop-In: /lib/systemd/system/apache2.service.d + └─apache2-systemd.conf + Active: inactive (dead) + Docs: man:systemd-sysv-generator(8) + + Related Bugs: + * bug 1576692: fully support package installation in systemd ** 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 --image-project ubuntu-os-cloud --metadata-from-file user-data=cloud-config NAMEZONEMACHINE_TYPE PREEMPTIBLE INTERNAL_IP EXTERNAL_IPSTATUS xenial-160427-1050 europe-west1-d n1-standard-1 10.240.0.7 104.155.86.94 RUNNING $ ssh ubuntu@104.155.86.94 systemctl status apache2.service ● apache2.service - LSB: Apache2 web server Loaded: loaded (/etc/init.d/apache2; bad; vendor preset: enabled) Drop-In: /lib/systemd/system/apache2.service.d └─apache2-systemd.conf Active: inactive (dead) Docs: man:systemd-sysv-generator(8) Related Bugs: - * bug 1576692: fully support package installation in systemd + * bug 1576692: [cloud-init] fully support package installation in systemd ** No longer affects: cloud-init (Ubuntu Xenial) ** No longer affects: cloud-init (Ubuntu) -- 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/1575572 Title: apache2 fails to start if installed via cloud config (on Xenial) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1575572/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1576341] [NEW] fails in lxd container
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 --state=failed UNIT LOAD ACTIVE SUBDESCRIPTION ● dev-hugepages.mount loaded failed failed Huge Pages File System ● iscsid.serviceloaded failed failed iSCSI initiator daemon (iscsid) ● open-iscsi.serviceloaded failed failed Login to default iSCSI targets ● systemd-remount-fs.serviceloaded failed failed Remount Root and Kernel File Systems ● systemd-sysctl.serviceloaded failed failed Apply Kernel Variables ● lvm2-lvmetad.socket loaded failed failed LVM2 metadata daemon socket ● systemd-journald-audit.socket loaded failed failed Journal Audit Socket LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB= The low-level unit activation state, values depend on unit type. 7 loaded units listed. Pass --all to see loaded but inactive units, too. To show all installed unit files use 'systemctl list-unit-files'. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: open-iscsi 2.0.873+git0.3b4b4500-14ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Thu Apr 28 17:28:04 2016 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) SourcePackage: open-iscsi UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: open-iscsi (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: systemd (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug uec-images xenial ** Description changed: - $ lxc launch xenial x1 $ sleep 10 - $ lxc file pull x5/etc/cloud/build.info - + $ 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 --state=failed - UNIT LOAD ACTIVE SUBDESCRIPTION + UNIT LOAD ACTIVE SUBDESCRIPTION ● dev-hugepages.mount loaded failed failed Huge Pages File System ● iscsid.serviceloaded failed failed iSCSI initiator daemon (iscsid) ● open-iscsi.serviceloaded failed failed Login to default iSCSI targets ● systemd-remount-fs.serviceloaded failed failed Remount Root and Kernel File Systems ● systemd-sysctl.serviceloaded failed failed Apply Kernel Variables ● lvm2-lvmetad.socket loaded failed failed LVM2 metadata daemon socket ● systemd-journald-audit.socket loaded failed failed Journal Audit Socket LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB= The low-level unit activation state, values depend on unit type. 7 loaded units listed. Pass --all to see loaded but inactive units, too. To show all installed unit files use 'systemctl list-unit-files'. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: open-iscsi 2.0.873+git0.3b4b4500-14ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Thu Apr 28 17:28:04 2016 ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) + TERM=xterm-256color + PATH=(custom, no user) SourcePackage: open-iscsi UpgradeStatus: No upgrade log present (probably fresh install) ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Description changed: + 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 --state=failed UNIT LOAD ACTIVE SUBDESCRIPTION ● dev-hugepages.mount loaded failed failed Huge Pages File System ● iscsid.serviceloaded failed failed iSCSI initiator daemon (iscsid) ● open-iscsi.serviceloaded failed failed Login to default iSCSI targets ● systemd-remount-fs.serviceloaded failed failed Remount Root and Kernel File Systems ● systemd-sysctl.serviceloaded failed failed Apply Kernel Variables ● lvm2-lvmetad.socket loaded failed failed LVM2 metadata daemon socket ● systemd-journald-audit.socket loaded failed failed Journal Audit Socket LOAD = Reflects whether the
[Bug 1571761] Re: zfs-import-cache.service slows boot by 60 seconds
** 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 by 60 seconds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1571761/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1571761] Re: zfs-import-cache.service slows boot by 60 seconds
** 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: zfs-import-cache.service slows boot by 60 seconds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1571761/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1463072] Re: highlighting on left mouse double click ends at : (colon)
** 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. https://bugs.launchpad.net/bugs/1463072 Title: highlighting on left mouse double click ends at : (colon) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1463072/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1468102] [NEW] rc.local output does not go to console
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 1468103: rc.local runs too early. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: systemd 220-7ubuntu1 ProcVersionSignature: User Name 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 ApportVersion: 2.17.3-0ubuntu4 Architecture: amd64 Date: Tue Jun 23 20:26:30 2015 Ec2AMI: ami-0434 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: aki-0002 Ec2Ramdisk: ari-0002 Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-22-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 SourcePackage: systemd UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2011 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2011:svnOpenStackFoundation:pnOpenStackNova:pvr2014.1.4:cvnBochs:ct1:cvr: dmi.product.name: OpenStack Nova dmi.product.version: 2014.1.4 dmi.sys.vendor: OpenStack Foundation ** Affects: systemd (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug ec2-images wily ** Attachment added: user-data showing issue https://bugs.launchpad.net/bugs/1468102/+attachment/4419587/+files/my-userdata ** Description changed: 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 1468103: rc.local runs too early. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: systemd 220-7ubuntu1 ProcVersionSignature: User Name 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 ApportVersion: 2.17.3-0ubuntu4 Architecture: amd64 Date: Tue Jun 23 20:26:30 2015 Ec2AMI: ami-0434 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: aki-0002 Ec2Ramdisk: ari-0002 Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR=set - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR=set + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-22-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 SourcePackage: systemd UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2011 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2011:svnOpenStackFoundation:pnOpenStackNova:pvr2014.1.4:cvnBochs:ct1:cvr: dmi.product.name: OpenStack Nova dmi.product.version: 2014.1.4 dmi.sys.vendor: OpenStack Foundation ** Changed in: systemd (Ubuntu) Status: New = Confirmed -- 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/1468102 Title: rc.local output does not go to console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1468102/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1468103] [NEW] rc.local runs too early.
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 earlier.
Provided in the attached is user-data that tells cloud-init to write a
file in /usr/local/bin/rc-local-message and edit set rc.local to execute
it.
On current wily, under most scenarios the script will not be executed as
rc.local will most likely run before the cloud-init service has a chance
to update /etc/rc.local.
To reproduce:
a.) launch an instance with provided user-data
Expected behavior would be:
1. /run/rc-local-message exists with contents of /proc/uptime at the time it
was run
2. /rc-local-message.mark exists with the number of times this script has
been run ('1' after first boot)
3. /var/log/rc-local-message.log exists with a message like:
[/var/log/rc-local-message.log] date === successful boot 1
4. console log should also have message like in 3 with '/dev/console'
4 is broken as rc.local output is not sent to console as reported
separately at bug 1468102.
Related bugs:
* bug 1468102: rc.local output does not go to console
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: systemd 220-7ubuntu1
ProcVersionSignature: User Name 3.19.0-22.22-generic 3.19.8-ckt1
Uname: Linux 3.19.0-22-generic x86_64
ApportVersion: 2.17.3-0ubuntu4
Architecture: amd64
Date: Tue Jun 23 20:21:50 2015
Ec2AMI: ami-0434
Ec2AMIManifest: FIXME
Ec2AvailabilityZone: nova
Ec2InstanceType: m1.small
Ec2Kernel: aki-0002
Ec2Ramdisk: ari-0002
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: OpenStack Foundation OpenStack Nova
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=set
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-22-generic
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0
SourcePackage: systemd
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/01/2011
dmi.bios.vendor: Bochs
dmi.bios.version: Bochs
dmi.chassis.type: 1
dmi.chassis.vendor: Bochs
dmi.modalias:
dmi:bvnBochs:bvrBochs:bd01/01/2011:svnOpenStackFoundation:pnOpenStackNova:pvr2014.1.4:cvnBochs:ct1:cvr:
dmi.product.name: OpenStack Nova
dmi.product.version: 2014.1.4
dmi.sys.vendor: OpenStack Foundation
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: Confirmed
** Tags: amd64 apport-bug ec2-images wily
** Attachment added: user-data showing problem
https://bugs.launchpad.net/bugs/1468103/+attachment/4419597/+files/my-userdata
** Description changed:
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.
+ | 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 earlier.
Provided in the attached is user-data that tells cloud-init to write a
file in /usr/local/bin/rc-local-message and edit set rc.local to execute
it.
On current wily, under most scenarios the script will not be executed as
rc.local will most likely run before the cloud-init service has a chance
to update /etc/rc.local.
To reproduce:
- a.) launch an instance with provided user-data
+ a.) launch an instance with provided user-data
Expected behavior would be:
- 1. /run/rc-local-message exists with contents of /proc/uptime at the time
it was run
- 2. /rc-local-message.mark exists with the number of times this script has
been run ('1' after first boot)
- 3. /var/log/rc-local-message.log exists with a message like:
- [/var/log/rc-local-message.log] date === successful boot 1
- 4. console log should also have message like in 3 with '/dev/console'
+ 1. /run/rc-local-message exists with contents of /proc/uptime at the time
it was run
+ 2. /rc-local-message.mark exists with the number of times this script has
been run ('1' after first boot)
+ 3. /var/log/rc-local-message.log exists with a message like:
+ [/var/log/rc-local-message.log] date === successful boot 1
+ 4. console log should also have message like in 3 with '/dev/console'
4 is broken as rc.local output is not sent to console as reported
separately at bug 1468102.
+
+ Related bugs:
+ * bug 1468102: rc.local output does not go to console
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: systemd 220-7ubuntu1
ProcVersionSignature: User Name 3.19.0-22.22-generic 3.19.8-ckt1
Uname: Linux 3.19.0-22-generic x86_64
ApportVersion: 2.17.3-0ubuntu4
Architecture: amd64
Date: Tue Jun 23 20:21:50 2015
Ec2AMI: ami-0434
Ec2AMIManifest: FIXME
[Bug 1391354] Re: Failure to boot ephemeral image for Utopic Fast Installer deployment: no ID_PATH for iSCSI device any more
** 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 Installer deployment: no ID_PATH for iSCSI device any more To manage notifications about this bug go to: https://bugs.launchpad.net/maas-images/+bug/1391354/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1463072] Re: highlighting on left mouse double click ends at :
** 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 click ends at : To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1463072/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1463072] Re: highlighting on left mouse double click ends at :
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', 'bdddb09c-01fe-4230-90b0-331af6389b5f'] $ dconf read /org/gnome/terminal/legacy/profiles:/:63575bfd-baa0-4acd-86fc-6726b91ff51e/visible-name 'default' $ dconf write /org/gnome/terminal/legacy/profiles:/:63575bfd-baa0-4acd- 86fc-6726b91ff51e/word-char-exceptions '@ms -,:.;/?%#_=+@~·' I believe the default is: -,:.;/?%#_=+@~. and I just added ':' to the list. -- 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 click ends at : To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1463072/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1463072] Re: highlighting on left mouse double click ends at :
** 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. https://bugs.launchpad.net/bugs/1463072 Title: highlighting on left mouse double click ends at : To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1463072/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1463072] [NEW] highlighting on left mouse double click ends at :
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 (http://example.com/path) its selection stops at the ':'. This means i keep pasting people urls that look like /paste.ubuntu.com/11591324/ rather than http://paste.ubuntu.com/11591324/ . Note, mouse over the url *does* underline the whole url. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: gnome-terminal 3.16.2-1ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 Uname: Linux 3.19.0-20-generic x86_64 ApportVersion: 2.17.3-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jun 8 11:11:02 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-01-02 (156 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150101) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- 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 click ends at : To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1463072/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1463072] Re: highlighting on left mouse double click ends at :
** 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 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 click ends at : To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1463072/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1432829] Re: resolvconf not updated correctly for interfaces configured in initramfs
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) = systemd (Ubuntu) ** Changed in: systemd (Ubuntu) Importance: Undecided = High ** Changed in: systemd (Ubuntu) Status: New = Confirmed -- 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/1432829 Title: resolvconf not updated correctly for interfaces configured in initramfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1432829/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1432821] Re: something deleting /run/network after during boot
** 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. https://bugs.launchpad.net/bugs/1432821 Title: something deleting /run/network after during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1432821/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1290941] Re: gnome-terminal ignores 'Use custom default terminal size' setting
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 0.9.11+14.04.20140310-0ubuntu1 . The changelog for that is: compiz (1:0.9.11+14.04.20140310-0ubuntu1) trusty; urgency=low [ Marco Trevisan (Treviño) ] * CompWindow: make sure we don't move a window outside its workarea when setting the extents (LP: #1204307) -- Ubuntu daily release ps-jenk...@lists.canonical.com Mon, 10 Mar 2014 20:30:48 + so I suspect that either: a.) the above package fixed it in fix for bug 1204307. b.) a previous version of the package fixed it and I just hadn't re-loaded since that. (1:0.9.11+14.04.20140303-0ubuntu1 mentions bug 1282304, bug 1282305 and bug 1282304 and bug 1282305). marking fix-released. ** Changed in: gnome-terminal (Ubuntu) Status: Confirmed = Fix Released -- 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/1290941 Title: gnome-terminal ignores 'Use custom default terminal size' setting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1290941/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1290941] Re: gnome-terminal ignores 'Use custom default terminal size' setting
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 in Ubuntu. https://bugs.launchpad.net/bugs/1290941 Title: gnome-terminal ignores 'Use custom default terminal size' setting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1290941/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1290941] [NEW] gnome-terminal ignores 'Use custom default terminal size' setting
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 when this started happening, but I'm guessing it could be the same time that bug 1238111 was fixed. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-terminal 3.6.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5 Uname: Linux 3.13.0-16-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 11 12:26:21 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2011-10-19 (874 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to trusty on 2013-05-20 (295 days ago) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Attachment added: screenshot showing problem https://bugs.launchpad.net/bugs/1290941/+attachment/4018410/+files/show-bug.png -- 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/1290941 Title: gnome-terminal ignores 'Use custom default terminal size' setting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1290941/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1290941] Re: gnome-terminal ignores 'Use custom default terminal size' setting
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. https://bugs.launchpad.net/bugs/1290941 Title: gnome-terminal ignores 'Use custom default terminal size' setting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1290941/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 887946] Re: Deadlocks in main loop
** 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. https://bugs.launchpad.net/bugs/887946 Title: Deadlocks in main loop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/887946/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 887946] Re: Deadlocks in main loop
** 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 fix. Upstream fix: + https://mail.gnome.org/archives/commits-list/2010-November/msg01816.html - https://mail.gnome.org/archives/commits-list/2010-November/msg01816.html + [Impact] + Remove potential and demonstratable deadlocks in glib code. + + [Test Case] + * Install lucid + * add ubuntu-ha-maintainers lucid ppa and update repo: +apt-add-repository ppa:ubuntu-ha-maintainers/lucid-cluster ; apt-get update + * Install pacemaker: +apt-get -y install pacemaker + * Enable corosync (/etc/default/corosync) and start it: +sed -i -e 's/START=no/START=yes/' /etc/default/corosync +service corosync start + * Open two client-server connections: +lrmadmin -C ; lrmadmin -C +It deadlocks on second run (it actually never finishes the first run). + + * Kill lrmd and stop corosync: +killall -9 lrmd ; service corosync stop + * install fix +apt-get update apt-get install libglib2.0-0 + * Start corosync: +service corosync start + * Run the test again: +lrmadmin -C ; lrmadmin -C ; lrmadmin -C ; lrmadmin -C + * It doesn't deadlock. + + [Regression Potential] + Regression potential should be very small. This change is still present in almost unmodified upstream code to this day (g_source_unref_internal of glib/gmain.c). The upstream trunk commit is at http://git.gnome.org/browse/glib/commit/?id=b358202856682e5cdefb0b4b8aaed3a45d9a85fa . ** Summary changed: - Deadlocks in main loop + [SRU] Deadlocks in main loop -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/887946 Title: [SRU] Deadlocks in main loop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/887946/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 888662] Re: Web browsers should share the cache
** 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amaya/+bug/888662/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 966294] Re: Ubiquity loops forever from ubiquity_webcam_play
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. https://bugs.launchpad.net/bugs/966294 Title: Ubiquity loops forever from ubiquity_webcam_play To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/966294/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 919188] Re: unity-panel-service big memory leak
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. https://bugs.launchpad.net/bugs/919188 Title: unity-panel-service big memory leak To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/919188/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 937158] [NEW] brasero crashed with SIGABRT in raise()
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: brasero 3.2.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.2.0-16.25-generic 3.2.6 Uname: Linux 3.2.0-16-generic i686 NonfreeKernelModules: ath_hal ApportVersion: 1.91-0ubuntu1 Architecture: i386 Date: Mon Feb 20 13:47:23 2012 EcryptfsInUse: Yes ExecutablePath: /usr/bin/brasero InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta i386 (20110901) ProcCmdline: /usr/bin/brasero -a /home/username/Music/Loose\ Tooth/01.\ Loose\ Tooth.mp3 /home/username/Music/Loose\ Tooth/02.\ Lemonade.mp3 /home/username/Music/Loose\ Tooth/03.\ Fire\ Station.mp3 /home/username/Music/Loose\ Tooth/04.\ Freeze\ Tag.mp3 /home/username/Music/Loose\ Tooth/05.\ Sound\ Like\ An\ Elephant.mp3 /home/username/Music/Loose\ Tooth/06.\ Room's\ A\ Mess.mp3 /home/username/Music/Loose\ Tooth/07.\ I\ Wish\ I\ Could\ Tie\ My\ Shoes.mp3 /home/username/Music/Loose\ Tooth/08.\ Merry\ Go\ Round.mp3 /home/username/Music/Loose\ Tooth/09.\ Just\ Love\ Tonka\ Trucks.mp3 /home/username/Music/Loose\ Tooth/10.\ Wearin'\ Underwear.mp3 /home/username/Music/Loose\ Tooth/11.\ Raspberry\ Sorbet.mp3 /home/username/Music/Loose\ Tooth/12.\ Don't\ Stop\ Reading.mp3 /home/username/Music/Loose\ Tooth/13.\ Celebrate\ The\ Juice\ Box.mp3 ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=en_US.UTF-8 Signal: 6 SourcePackage: brasero StacktraceTop: raise () from /lib/i386-linux-gnu/libc.so.6 abort () from /lib/i386-linux-gnu/libc.so.6 g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 Title: brasero crashed with SIGABRT in raise() UpgradeStatus: Upgraded to precise on 2012-02-06 (13 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare ** Affects: brasero (Ubuntu) Importance: Undecided Status: New ** Tags: apport-crash i386 precise -- 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: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/937158/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 937158] Re: brasero crashed with SIGABRT in raise()
-- 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: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/937158/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 794771] Re: metacity doesn't start, dies with metacity:ERROR:ui/ui.c:754:meta_ui_get_default_window_icon: assertion failed: (default_icon)
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 is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/794771 Title: metacity doesn't start, dies with metacity:ERROR:ui/ui.c:754:meta_ui_get_default_window_icon: assertion failed: (default_icon) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/794771/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 794771] Re: metacity doesn't start, dies with metacity:ERROR:ui/ui.c:754:meta_ui_get_default_window_icon: assertion failed: (default_icon)
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
metacity1:2.34.1-1ubuntu4
xserver-xephyr 2:1.10.4-1ubuntu5
So it looks like fix-released to me.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in Ubuntu.
https://bugs.launchpad.net/bugs/794771
Title:
metacity doesn't start, dies with
metacity:ERROR:ui/ui.c:754:meta_ui_get_default_window_icon: assertion
failed: (default_icon)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/794771/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 877420] Re: .xsession-errors grows quickly and indefinitely
** 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. https://bugs.launchpad.net/bugs/877420 Title: .xsession-errors grows quickly and indefinitely To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-multiload/+bug/877420/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 877420] [NEW] .xsession-errors grows quickly and indefinitely
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 'gnome-session', as it was the first pid to have this file open. I'll attach full lsof output also so you can see all the processes with it open. I'll also attach a .xesssion-errors is being written to repeatedly with a message like the following: ' does not start with 'cpu1': Resource temporarily unavailable glibtop: 'intr 155804419 91091683 470583 0 0 0 0 0 0 1 27482 0 0 7440876 0 0 0 207225 6516 2129 0 69 249 0 5148256 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 212687 1317541 4489636 22517867 603 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ctxt 439474352 btime 1318528821 processes 1146706 procs_running 2 procs_blocked 0 softirq 92185829 2 23974943 10006 1285072 4697203 2 27171913 5804 16744 35024140 ' does not start with 'cpu1': Resource temporarily unavailable ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-session 3.2.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Tue Oct 18 09:05:16 2011 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.04 Lucid Lynx - Beta amd64 (20100318) PackageArchitecture: all ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=en_US.UTF-8 SourcePackage: gnome-session UpgradeStatus: Upgraded to oneiric on 2010-11-15 (336 days ago) --- ApportVersion: 1.23-0ubuntu3 Architecture: amd64 DistroRelease: Ubuntu 11.10 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.04 Lucid Lynx - Beta amd64 (20100318) Package: indicator-multiload 0.2-0+33~17~16~oneiric1 PackageArchitecture: amd64 ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=en_US.UTF-8 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Tags: oneiric running-unity Uname: Linux 3.0.0-12-generic x86_64 UnreportableReason: This is not a genuine Ubuntu package UpgradeStatus: Upgraded to oneiric on 2010-11-15 (336 days ago) UserGroups: adm admin audio cdrom dialout kvm libvirtd lpadmin plugdev sambashare sbuild ** Affects: indicator-multiload (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug apport-collected oneiric running-unity -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/877420 Title: .xsession-errors grows quickly and indefinitely To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-multiload/+bug/877420/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 877420] Re: .xsession-errors grows quickly and indefinitely
$ 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: gnome-session (Ubuntu) = indicator-multiload (Ubuntu) ** Tags added: apport-collected ** Description changed: 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 'gnome-session', as it was the first pid to have this file open. I'll attach full lsof output also so you can see all the processes with it open. I'll also attach a .xesssion-errors is being written to repeatedly with a message like the following: ' does not start with 'cpu1': Resource temporarily unavailable glibtop: 'intr 155804419 91091683 470583 0 0 0 0 0 0 1 27482 0 0 7440876 0 0 0 207225 6516 2129 0 69 249 0 5148256 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 212687 1317541 4489636 22517867 603 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ctxt 439474352 btime 1318528821 processes 1146706 procs_running 2 procs_blocked 0 softirq 92185829 2 23974943 10006 1285072 4697203 2 27171913 5804 16744 35024140 ' does not start with 'cpu1': Resource temporarily unavailable ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-session 3.2.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Tue Oct 18 09:05:16 2011 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.04 Lucid Lynx - Beta amd64 (20100318) PackageArchitecture: all ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=en_US.UTF-8 SourcePackage: gnome-session UpgradeStatus: Upgraded to oneiric on 2010-11-15 (336 days ago) + --- + ApportVersion: 1.23-0ubuntu3 + Architecture: amd64 + DistroRelease: Ubuntu 11.10 + EcryptfsInUse: Yes + InstallationMedia: Ubuntu 10.04 Lucid Lynx - Beta amd64 (20100318) + Package: indicator-multiload 0.2-0+33~17~16~oneiric1 + PackageArchitecture: amd64 + ProcEnviron: + SHELL=/bin/bash + PATH=(custom, user) + LANG=en_US.UTF-8 + ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 + Tags: oneiric running-unity + Uname: Linux 3.0.0-12-generic x86_64 + UnreportableReason: This is not a genuine Ubuntu package + UpgradeStatus: Upgraded to oneiric on 2010-11-15 (336 days ago) + UserGroups: adm admin audio cdrom dialout kvm libvirtd lpadmin plugdev sambashare sbuild -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/877420 Title: .xsession-errors grows quickly and indefinitely To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-multiload/+bug/877420/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 842768] Re: Cups notifies printer ' xxx ' may be not connected although printer is OK and printing is OK too
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 ubuntu-sponsors. If you disagree, please re-subscribe ubuntu-sponsors. If I'm right, then feel free to submit a merge proposal or attach a debdiff and re-subscribe sponsors. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/842768 Title: Cups notifies printer ' xxx ' may be not connected although printer is OK and printing is OK too To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/842768/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 862813] Re: Power Managment settings are being ignored
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 Managment settings are being ignored To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/862813/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 862813] Re: Power Managment settings are being ignored
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. https://bugs.launchpad.net/bugs/862813 Title: Power Managment settings are being ignored To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/862813/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 862813] Re: Power Managment settings are being ignored
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 Ubuntu. https://bugs.launchpad.net/bugs/862813 Title: Power Managment settings are being ignored To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/862813/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 802572] [NEW] cannot login after suspend -- empty grey box
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: gnome-screensaver 3.0.0-2ubuntu2 ProcVersionSignature: Ubuntu 3.0-1.2-generic 3.0.0-rc3 Uname: Linux 3.0-1-generic x86_64 Architecture: amd64 Date: Mon Jun 27 11:00:15 2011 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.04 Lucid Lynx - Beta amd64 (20100318) ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.utf8 LC_MESSAGES=en_US.utf8 SHELL=/bin/bash SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to oneiric on 2010-11-15 (223 days ago) ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oneiric running-unity unity-2d -- 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: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/802572/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 802572] Re: cannot login after suspend -- empty grey box
-- 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: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/802572/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 794771] Re: metacity doesn't start, dies with metacity:ERROR:ui/ui.c:754:meta_ui_get_default_window_icon: assertion failed: (default_icon)
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 = Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/794771 Title: metacity doesn't start, dies with metacity:ERROR:ui/ui.c:754:meta_ui_get_default_window_icon: assertion failed: (default_icon) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/794771/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 726558] Re: drawer in gnome-panel was emptied on upgrade
** 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 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 726558] [NEW] 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 development cycle. After the first, I removed the empty drawer and added a new one. I'm not sure what version I upgraded from (last dist-upgrade was ~ 2011-02-25), but the version upgraded to is gnome-panel 1:2.32.1-0ubuntu6 ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: gnome-panel 1:2.32.1-0ubuntu6 ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6 Uname: Linux 2.6.38-5-generic x86_64 Architecture: amd64 Date: Mon Feb 28 09:22:40 2011 EcryptfsInUse: Yes GConfNonDefault: /apps/panel/general/applet_id_list=[mixer_screen0,notification_area_screen0,indicator_applet_screen0,show_desktop_button_screen0,window_list_screen0,workspace_switcher_screen0,trashapplet_screen0,fast_user_switch_screen0,applet_0,applet_1,applet_2,applet_3,applet_4] /apps/panel/general/object_id_list=[object_0,menu_bar_screen0,browser_launcher_screen0,email_launcher_screen0,yelp_launcher_screen0,clock_separator_screen0,object_2,object_3,object_4] /apps/panel/general/toplevel_id_list=[top_panel_screen0] InstallationMedia: Ubuntu 10.04 Lucid Lynx - Beta amd64 (20100318) ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-panel UpgradeStatus: Upgraded to natty on 2010-11-15 (104 days ago) ** Affects: gnome-panel (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug 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 https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 726558] Re: drawer in gnome-panel was emptied on upgrade
-- 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 https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 494096] Re: Clicking the title of a window is bringing a window underneath it into focus
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 more straight forward for the sponsor to pull the branch and get the fix into lucid. Anyone able to do that? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in ubuntu. https://bugs.launchpad.net/bugs/494096 Title: Clicking the title of a window is bringing a window underneath it into focus -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 711442] Re: vinagre crashed with SIGSEGV in g_socket_send()
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 uses quilt for patches. You should apply your changes by adding a patch to debian/patches and debian/patches/series c.) The patch should ideally be in DEP-3 format -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to vinagre in ubuntu. https://bugs.launchpad.net/bugs/711442 Title: vinagre crashed with SIGSEGV in g_socket_send() -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 473705] Re: power management does not consistently power down inactive monitor
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 SDL_VIDEO_ALLOW_SCREENSAVER=1 in your environment. One place to do something like this is in ~/.bash_profile with: export SDL_VIDEO_ALLOW_SCREENSAVER=1 This may not be your problem. -- power management does not consistently power down inactive monitor https://bugs.launchpad.net/bugs/473705 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 473705] Re: power management does not consistently power down inactive monitor
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 consistently power down inactive monitor https://bugs.launchpad.net/bugs/473705 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 473705] Re: power management does not consistently power down inactive monitor
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 few seconds they'd be turned back on. ** Changed in: gnome-power-manager (Ubuntu) Status: New = Confirmed -- power management does not consistently power down inactive monitor https://bugs.launchpad.net/bugs/473705 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 310750] Re: Evince won't open USPS Click-n-Ship label
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 USPS label pdf http://launchpadlibrarian.net/22444276/usps-example-label.pdf -- Evince won't open USPS Click-n-Ship label https://bugs.launchpad.net/bugs/310750 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to poppler in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
