[Bug 1856376] Re: "Dummy Output" -- built-in audio not detected
I do seem to have some things in that directory: alex@tapada:~$ ls -la /lib/modules/`uname -r`/kernel/sound/pci/hda/ total 1036 drwxr-xr-x 2 root root 4096 Dec 4 06:10 . drwxr-xr-x 26 root root 4096 Dec 4 06:10 .. -rw-r--r-- 1 root root 24081 Nov 14 06:10 snd-hda-codec-analog.ko -rw-r--r-- 1 root root 7297 Nov 14 06:10 snd-hda-codec-ca0110.ko -rw-r--r-- 1 root root 162449 Nov 14 06:10 snd-hda-codec-ca0132.ko -rw-r--r-- 1 root root 22593 Nov 14 06:10 snd-hda-codec-cirrus.ko -rw-r--r-- 1 root root 8561 Nov 14 06:10 snd-hda-codec-cmedia.ko -rw-r--r-- 1 root root 31113 Nov 14 06:10 snd-hda-codec-conexant.ko -rw-r--r-- 1 root root 105369 Nov 14 06:10 snd-hda-codec-generic.ko -rw-r--r-- 1 root root 89473 Nov 14 06:10 snd-hda-codec-hdmi.ko -rw-r--r-- 1 root root 89057 Nov 14 06:10 snd-hda-codec-idt.ko -rw-r--r-- 1 root root 202025 Nov 14 06:10 snd-hda-codec.ko -rw-r--r-- 1 root root 165681 Nov 14 06:10 snd-hda-codec-realtek.ko -rw-r--r-- 1 root root 13001 Nov 14 06:10 snd-hda-codec-si3054.ko -rw-r--r-- 1 root root 30721 Nov 14 06:10 snd-hda-codec-via.ko -rw-r--r-- 1 root root 76505 Nov 14 06:10 snd-hda-intel.ko Anything in particular I should be looking for? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856376 Title: "Dummy Output" -- built-in audio not detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1856376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856376] [NEW] "Dummy Output" -- built-in audio not detected
Public bug reported: I no longer seem to be getting audio on my laptop, and only "Dummy Output" shows up in the sound settings dialog. This sounds similar to LP #1781294 (including the same PCI device), though that seems to have been marked expired. alex@tapada:~$ lspci -v | grep -A7 -i "audio" 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) (prog-if 80) Subsystem: Lenovo Sunrise Point-LP HD Audio Flags: bus master, fast devsel, latency 64, IRQ 159 Memory at 2ffb028000 (64-bit, non-prefetchable) [size=16K] Memory at 2ffb00 (64-bit, non-prefetchable) [size=64K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel, snd_soc_skl alex@tapada:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.3 LTS Release:18.04 Codename: bionic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Fri Dec 13 23:38:35 2019 InstallationDate: Installed on 2019-08-31 (104 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET68W (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET68W(1.43):bd10/16/2019:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHCTO1WW dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-12-13T22:15:32.867642 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856376 Title: "Dummy Output" -- built-in audio not detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1856376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1794876] Re: Touchpad doesn't work out-of-the-box in Ubuntu 18.04.1 with ThinkPad X1 carbon
This impacted me as well (X1 Carbon Gen 6, 5.0.0-25-generic #26~18.04.1-Ubuntu) . Un-blacklisting the module (and update- initramfs'ing) seems to have worked. Previously my touchpad was *highly* inconsistent and the Trackpoint either didn't work as well or I just never noticed it working; now both seem fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794876 Title: Touchpad doesn't work out-of-the-box in Ubuntu 18.04.1 with ThinkPad X1 carbon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794876/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828525] [NEW] Fix Python3 comparison `TypeError` in `salt.modules.upstart` #46293
Public bug reported:
When I try to use the Apache formula, I get:
ID: apache
Function: service.running
Name: apache2
Result: False
Comment: An exception occurred in this state: Traceback (most recent call
last):
File "/usr/lib/python3/dist-packages/salt/state.py", line 1851,
in call
**cdata['kwargs'])
File "/usr/lib/python3/dist-packages/salt/loader.py", line
1795, in wrapper
return f(*args, **kwargs)
File "/usr/lib/python3/dist-packages/salt/states/service.py",
line 402, in running
if not _available(name, ret):
File "/usr/lib/python3/dist-packages/salt/states/service.py",
line 321, in _available
avail = __salt__['service.available'](name)
File "/usr/lib/python3/dist-packages/salt/modules/upstart.py",
line 317, in available
return name in get_all()
File "/usr/lib/python3/dist-packages/salt/modules/upstart.py",
line 345, in get_all
return sorted(get_enabled() + get_disabled())
File "/usr/lib/python3/dist-packages/salt/modules/upstart.py",
line 279, in get_enabled
if _sysv_is_enabled(name):
File "/usr/lib/python3/dist-packages/salt/modules/upstart.py",
line 229, in _sysv_is_enabled
return not _sysv_is_disabled(name)
File "/usr/lib/python3/dist-packages/salt/modules/upstart.py",
line 221, in _sysv_is_disabled
return not
bool(glob.glob('/etc/rc{0}.d/S*{1}'.format(_runlevel(), name)))
File "/usr/lib/python3/dist-packages/salt/modules/upstart.py",
line 155, in _runlevel
utmp = _find_utmp()
File "/usr/lib/python3/dist-packages/salt/modules/upstart.py",
line 100, in _find_utmp
if result > 0:
TypeError: '>' not supported between instances of 'dict' and 'int'
Started: 08:08:36.996021
Duration: 3.895 ms
Changes:
Upstream salt seems to have fixed this already
(https://github.com/saltstack/salt/pull/46293), but it seems like maybe
this warrants being backported into the 18.04 package?
root@salt-4:/# lsb_release -rd
Description:Ubuntu 18.04.2 LTS
Release:18.04
root@salt-4:/# apt-cache policy salt-common
salt-common:
Installed: 2017.7.4+dfsg1-1
Candidate: 2017.7.4+dfsg1-1
Version table:
*** 2017.7.4+dfsg1-1 500
500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
100 /var/lib/dpkg/status
root@salt-4:/# dpkg -S /usr/lib/python3/dist-packages/salt/modules/upstart.py
salt-common: /usr/lib/python3/dist-packages/salt/modules/upstart.py
** Affects: salt (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828525
Title:
Fix Python3 comparison `TypeError` in `salt.modules.upstart` #46293
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/salt/+bug/1828525/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1632407] [NEW] -package libssl1.0.0:i386 1.0.2g-1ubuntu4.5 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated)
Public bug reported: This came up while I was upgrading from 14.04 to 16.04. I initially tried by running update-manager from a terminal (so using the GUI). That eventually launched a dialog, which froze up. At some point, I think while using the GUI, there was a bunch of spew printed to the terminal about Dbpassword being unable to access /var/lib/something/passwords.dat or so. (Sorry, I didn't save the exact text, so I only remember the gist.) Then I tried apt-get dist-upgrade from the terminal. That failed; I think as soon as I said "Y", it spewed out a bunch of conflicts and told me to run apt-get install -f. That errored with something about url being in both texlive-latex-recommended-doc 2013 and texlive-latex-base- doc 2015. Per directions on the internet, I removed texlive-latex- recommended-doc, and tried apt-get install -f again. That had some more errors, but mostly progressed. After running that and dist-upgrade until things stopped, I rebooted. Immediately after logging in, I got a bunch of errors like "System software encountered a bug" or "Installing software was unsuccessful"; choosing to report on one of those sent me here, with a title like "package libssl1.0.0:amd64 1.0.2g-1ubuntu4.5 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated)". I'm kinda mystified by what happened, and I don't have great records, but perhaps some of this is helpful for finding some bug... I'm happy to try to answer questions. (Oh, and FWIW, I was running xmonad before and seem to have been dumped in a more standard UI post-upgrade. Conceivably that's related, but I assume not.) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libssl1.0.0:i386 1.0.2g-1ubuntu4.5 ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21 Uname: Linux 4.4.0-42-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Tue Oct 11 02:07:43 2016 ErrorMessage: subprocess installed post-installation script was killed by signal (Terminated) InstallationDate: Installed on 2014-05-23 (872 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: openssl Title: package libssl1.0.0:i386 1.0.2g-1ubuntu4.5 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated) UpgradeStatus: Upgraded to xenial on 2016-10-11 (0 days ago) ** Affects: openssl (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1632407 Title: -package libssl1.0.0:i386 1.0.2g-1ubuntu4.5 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1632407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1610759] Re: package shim-signed 1.18~14.04.1+0.8-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated)
*** This bug is a duplicate of bug 1607929 *** https://bugs.launchpad.net/bugs/1607929 ** This bug has been marked a duplicate of bug 1607929 (trusty, debconf passthrough) package shim-signed 1.17~14.04.1+0.8-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1610759 Title: package shim-signed 1.18~14.04.1+0.8-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1610759/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1607929] Re: (trusty, debconf passthrough) package shim-signed 1.17~14.04.1+0.8-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated)
I think update-manager? One of the standard GUI updater things. Here's a chunk of ps -AF --forest that might help: alex 6365 1 0 84088 18916 2 Jul30 ?00:00:00 /usr/bin/python /usr/lib/update-notifier/backend_helper.py show_updates alex 6370 6365 0 173663 123028 2 Jul30 ?00:00:11 \_ /usr/bin/python3 /usr/bin/update-manager --no-update alex 7919 6370 0 17241 14224 2 Jul30 ?00:00:00 \_ /usr/bin/perl -w /usr/bin/debconf-communicate root 7180 1 0 76314 66688 2 Jul30 ?00:00:04 /usr/bin/python3 /usr/sbin/aptd root 7189 7180 0 76315 47888 3 Jul30 pts/301:13:37 \_ /usr/bin/python3 /usr/sbin/aptd root 7916 7189 0 5261 10480 2 Jul30 pts/600:00:00 \_ /usr/bin/dpkg --status-fd 99 --configure shim-signed:amd64 dkms:all x11proto-randr-dev:all root 7917 7916 0 17788 14340 0 Jul30 pts/600:00:00 \_ /usr/bin/perl -w /usr/share/debconf/frontend /var/lib/dpkg/info/shim-signed.postinst configure 1.17~14.04.1+0.8-0ubuntu2 -- [...] alex 23733 1 0 84089 20524 3 20:54 ?00:00:00 /usr/bin/python /usr/lib/update-notifier/backend_helper.py show_updates alex 23738 23733 2 166574 182760 0 20:54 ?00:00:02 \_ /usr/bin/python3 /usr/bin/update-manager --no-update -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1607929 Title: (trusty, debconf passthrough) package shim-signed 1.17~14.04.1+0.8-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1607929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1610759] [NEW] package shim-signed 1.18~14.04.1+0.8-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated)
Public bug reported: This is presumably the same bug as bug 1607929. I figure the added debug info might be useful, but I'm not sure there's a way to upload to an existing bug... ProblemType: Package DistroRelease: Ubuntu 14.04 Package: shim-signed 1.18~14.04.1+0.8-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39 Uname: Linux 3.13.0-92-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 BootEFIContents: grub.cfg grubx64.efi MokManager.efi shimx64.efi Date: Sun Aug 7 20:56:05 2016 DpkgHistoryLog: DpkgTerminalLog: ErrorMessage: subprocess installed post-installation script was killed by signal (Terminated) InstallationDate: Installed on 2014-05-23 (807 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.14 SourcePackage: shim-signed Title: package shim-signed 1.18~14.04.1+0.8-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated) UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: shim-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1610759 Title: package shim-signed 1.18~14.04.1+0.8-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1610759/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1607929] [NEW] package shim-signed 1.17~14.04.1+0.8-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated)
Public bug reported: I'm not really sure whether this is a bug; I think the install was hanging for a while, with a blank window displaying. I killed the install and it went away, but it's certainly plausible that this is due to something local, not a bug. Feel free to close this if nobody else is seeing it. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: shim-signed 1.17~14.04.1+0.8-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36 Uname: Linux 3.13.0-85-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 BootEFIContents: grub.cfg grubx64.efi MokManager.efi shimx64.efi Date: Fri Jul 29 15:45:46 2016 DuplicateSignature: package:shim-signed:1.17~14.04.1+0.8-0ubuntu2:subprocess installed post-installation script was killed by signal (Terminated) ErrorMessage: subprocess installed post-installation script was killed by signal (Terminated) InstallationDate: Installed on 2014-05-23 (798 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.14 SourcePackage: shim-signed Title: package shim-signed 1.17~14.04.1+0.8-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated) UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: shim-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1607929 Title: package shim-signed 1.17~14.04.1+0.8-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1607929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1273014] Re: notification-daemon crashed with signal 5 in g_source_remove()
notification-daemon generally crashes for me ~immediately on both my personal Trusty machines -- any chance of getting this backported? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1273014 Title: notification-daemon crashed with signal 5 in g_source_remove() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notification-daemon/+bug/1273014/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1120917] [NEW] annotate-output should preserve whitespace
Public bug reported: annotate-output currently clobbers line-initial whitespace, and also interprets backslash sequences: adehnert@esp:~$ annotate-output echo ' foo\\' 01:37:31 I: Started echofoo\\ 01:37:31 O: foo\ 01:37:31 I: Finished with exitcode 0 I believe the attached patch fixes both these issues. Thanks, Alex ** Affects: devscripts (Ubuntu) Importance: Undecided Status: New ** Patch added: annotate-output.patch https://bugs.launchpad.net/bugs/1120917/+attachment/3522773/+files/annotate-output.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1120917 Title: annotate-output should preserve whitespace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/devscripts/+bug/1120917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1005422] Re: Indicator can no longer change size in cinnamon
I at least sort of figured out my problem. It looks like I only want to use indicator-multiload with Unity, and want to use the corresponding applet (maybe) with XMonad. I appear to be able to add it with alt- right-click in the panel area, and it uses up plenty of space. indicator-multiload should probably work better too, but this is good enough for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1005422 Title: Indicator can no longer change size in cinnamon To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1005422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1005422] Re: Indicator can no longer change size in cinnamon
** Also affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1005422 Title: Indicator can no longer change size in cinnamon To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1005422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1005422] Re: Indicator can no longer change size in cinnamon
I'm seeing this on my work computer (Ubuntu 12.04, 64 bit) when running the GNOME Classic and GNOME with Xmonad sessions, but not when using the Ubuntu/Unity session. I'm not seeing it at home under GNOME with xmonad, though... (Also Ubuntu 12.04, 64 bit...) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1005422 Title: Indicator can no longer change size in cinnamon To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1005422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1008225] Re: vmbuilder fails using tmpfs due to upstart restarting cron in the tmpfs
It looks to me like the issue is that while vmbuilder moves away initctl to avoid starting any services, upstart (or maybe another init?) gets reinstalled, replacing the moved initctl. As a result, it leaks a cron invocation. (I'm not totally sure why the policy-rc.d change that's in the guest isn't working --- my assumption is that initctl is contacting Upstart outside the chroot over D-Bus, and that Upstart sees the hosts' /usr/sbin/policy-rc.d. I guess vmbuilder could stash something in that policy-rc.d, but that seems slightly messy.) I've attached a patch that seems to allow me to build VMs running hardy, lucid, maverick, natty, oneiric, and precise (all amd64; I haven't tested other architectures). The earlier suites are no longer supported, so building those bails pretty quickly... ** Patch added: lucid-vm.patch https://bugs.launchpad.net/ubuntu/+source/vm-builder/+bug/1008225/+attachment/3208174/+files/lucid-vm.patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in Ubuntu. https://bugs.launchpad.net/bugs/1008225 Title: vmbuilder fails using tmpfs due to upstart restarting cron in the tmpfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vm-builder/+bug/1008225/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1008225] Re: vmbuilder fails using tmpfs due to upstart restarting cron in the tmpfs
It looks to me like the issue is that while vmbuilder moves away initctl to avoid starting any services, upstart (or maybe another init?) gets reinstalled, replacing the moved initctl. As a result, it leaks a cron invocation. (I'm not totally sure why the policy-rc.d change that's in the guest isn't working --- my assumption is that initctl is contacting Upstart outside the chroot over D-Bus, and that Upstart sees the hosts' /usr/sbin/policy-rc.d. I guess vmbuilder could stash something in that policy-rc.d, but that seems slightly messy.) I've attached a patch that seems to allow me to build VMs running hardy, lucid, maverick, natty, oneiric, and precise (all amd64; I haven't tested other architectures). The earlier suites are no longer supported, so building those bails pretty quickly... ** Patch added: lucid-vm.patch https://bugs.launchpad.net/ubuntu/+source/vm-builder/+bug/1008225/+attachment/3208174/+files/lucid-vm.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1008225 Title: vmbuilder fails using tmpfs due to upstart restarting cron in the tmpfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vm-builder/+bug/1008225/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 529381] Re: apticron uninstallable without cron
I've verified that stock apticron doesn't install on a new Lucid VM, but that the apticron from your PPA does. Thanks. -- apticron uninstallable without cron https://bugs.launchpad.net/bugs/529381 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 529381] [NEW] apticron uninstallable without cron
Public bug reported: Binary package hint: apticron apticron appears to require cron to be installed so that the /etc/cron.d/ directory exists. When cron isn't installed (as, for example, on a VM built by python-vm-builder), apticron will fail to install. Presumably, apticron should declare a dependency on cron (or recommend cron and install successfully without it or something). r...@novgorod:~# lsb_release -rd Description:Ubuntu 9.10 Release:9.10 r...@novgorod:~# apt-cache policy apticron apticron: Installed: 1.1.35 Candidate: 1.1.35 Running aptitude install apticron should install apticron. Instead, it fails: r...@novgorod:~# aptitude install apticron [...] Setting up apticron (1.1.35) ... Creating config file /etc/cron.d/apticron with new version cp: cannot create regular file `/etc/cron.d/apticron': No such file or directory dpkg: error processing apticron (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: apticron E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: Setting up apticron (1.1.35) ... Creating config file /etc/cron.d/apticron with new version cp: cannot create regular file `/etc/cron.d/apticron': No such file or directory dpkg: error processing apticron (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: apticron Reading package lists... Done ** Affects: apticron (Ubuntu) Importance: Undecided Status: New -- apticron uninstallable without cron https://bugs.launchpad.net/bugs/529381 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 528895] [NEW] git-core should depend on man-db
Public bug reported: Binary package hint: git-core git help requires /usr/bin/man to exist in order to display help, but man isn't necessarily installed (in particular, it isn't installed on machines installed with python-vm-builder). a...@masada ~ [09:09] $ git help foo warning: failed to exec 'man': No such file or directory fatal: no man viewer handled the request It seems like git-core should probably depend on or recommend man-db. ** Affects: git-core (Ubuntu) Importance: Undecided Status: New -- git-core should depend on man-db https://bugs.launchpad.net/bugs/528895 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 528894] [NEW] SSL name-based virtual hosts are supported
Public bug reported: Binary package hint: apache2.2-common a...@masada apache2 [09:18] $ lsb_release -rd Description:Ubuntu 9.10 Release:9.10 a...@masada apache2 [09:19] $ apt-cache policy apache2.2-common apache2.2-common: Installed: 2.2.12-1ubuntu2.1 Candidate: 2.2.12-1ubuntu2.1 Version table: *** 2.2.12-1ubuntu2.1 0 500 http://superconducktor.mit.edu karmic-updates/main Packages 500 http://security.ubuntu.com karmic-security/main Packages 100 /var/lib/dpkg/status 2.2.12-1ubuntu2 0 500 http://superconducktor.mit.edu karmic/main Packages The standard /etc/ports.conf provided claims: IfModule mod_ssl.c # SSL name based virtual hosts are not yet supported, therefore no # NameVirtualHost statement here Listen 443 /IfModule In reality, now that SNI is supported (LP: 184131), SSL name based virtual hosts *are* supported. I'd expect a snippet more like: IfModule mod_ssl.c NameVirtualHost *:443 Listen 443 /IfModule ** Affects: apache2 (Ubuntu) Importance: Undecided Status: New -- SSL name-based virtual hosts are supported https://bugs.launchpad.net/bugs/528894 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 528894] Re: SSL name-based virtual hosts are supported
Sorry, that should be /etc/apache2/ports.conf above, not /etc/ports.conf. -- SSL name-based virtual hosts are supported https://bugs.launchpad.net/bugs/528894 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 484098] [NEW] xm bash completion interacts poorly with bash aliases
Public bug reported:
Binary package hint: xen-tools
a...@borobudur ~ [01:40] $ lsb_release -rd
Description:Ubuntu 9.04
Release:9.04
a...@borobudur ~ [01:40] $ apt-cache policy xen-tools
xen-tools:
Installed: 3.9-6
Candidate: 3.9-6
Version table:
*** 3.9-6 0
500 http://us.archive.ubuntu.com jaunty/universe Packages
100 /var/lib/dpkg/status
3.8-4ubuntu4 0
1 http://us.archive.ubuntu.com hardy/universe Packages
What I tried:
sudo xm create vmnatab
What I got:
sudo xm create vmname.cfg@
What I expected to get:
sudo xm create vmname.cfg
I have alias ls='ls -F --color=tty' in my dotfiles, so the tab-completion was
including the @ that marks the file as a symlink. I think this can be resolved
by using /bin/ls instead of just ls in the bash_completion script:
--- /etc/bash_completion.d/xm.orig 2009-11-17 01:32:45.0 -0800
+++ /etc/bash_completion.d/xm 2009-11-17 01:33:01.0 -0800
@@ -41,7 +41,7 @@
return 0
;;
create)
- local names=$(for x in `ls -1 /etc/xen/*.cfg 2/dev/null`; do echo
${x/\/etc\/xen\//} ; done )
+ local names=$(for x in `/bin/ls -1 /etc/xen/*.cfg 2/dev/null`; do
echo ${x/\/etc\/xen\//} ; done )
COMPREPLY=( $(compgen -W ${names} -- ${cur}) )
return 0
;;
** Affects: xen-tools (Ubuntu)
Importance: Undecided
Status: New
--
xm bash completion interacts poorly with bash aliases
https://bugs.launchpad.net/bugs/484098
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 174832] Re: ubuntu gnome-terminal - wrong key mapping in bash with a french keyboard
This feels like the same bug as https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/204202. (Not that that is really likely to help anyone.) -- ubuntu gnome-terminal - wrong key mapping in bash with a french keyboard https://bugs.launchpad.net/bugs/174832 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 23244] Re: keyboard shortcut mixed when using several keymaps
This feels like the same bug as https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/204202. (Not that that is really likely to help anyone.) -- keyboard shortcut mixed when using several keymaps https://bugs.launchpad.net/bugs/23244 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 163835] Re: Ctrl-keys does not work in gutsy
*** This bug is a duplicate of bug 204202 *** https://bugs.launchpad.net/bugs/204202 This feels like the same bug as https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/204202. (Not that that is really likely to help anyone.) ** This bug has been marked a duplicate of bug 204202 Ctrl+Z in Terminal doesn't work with dvorak layout -- Ctrl-keys does not work in gutsy https://bugs.launchpad.net/bugs/163835 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 238549] Re: xen dom0 crashes with BUG: soft lockup - CPU#0 stuck for 11s!
I think I may have seen the same bug. At least, the Xen dom0 will occasionally completely freeze up. Moving the mouse does not cause the cursor to move in X11, pressing keys doesn't produce any visible result (in X11 or console), ssh sessions freeze up (to host and guest), other services are not responded to, and so forth. I haven't tried SysRq, though I will next time it goes down. Nothing appears in the log files (that I've seen). I haven't figured out a reliable way to reproduce the problem. However, it does seem to happen more when doing disk intensive operations (eg, rebuilding a RAID array). I've been seeing this problem fairly frequently since around when I got home for the summer and upgraded to 8.04 and installed ubuntu-desktop (previously, the machine was only serving as a server). I don't recall hitting the issue before the upgrade, but I may be mistaken. The bug occurs with 2.6.24-18-xen and 2.6.24-19-xen, although does not seem to occur when using the non-Xen kernels (admittedly, while I've tried to stress the non-Xen kernels, without a reliable way to cause the bug I'm not sure that means it isn't there, and I've used the Xen kernels much more). Let me know if there is a way to attach several files to one comment. I don't see one, so I'll submit a few more comments. Also, please let me know if you need anything else. ** Attachment added: dmesg.log http://launchpadlibrarian.net/16686392/dmesg.log -- xen dom0 crashes with BUG: soft lockup - CPU#0 stuck for 11s! https://bugs.launchpad.net/bugs/238549 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 238549] Re: xen dom0 crashes with BUG: soft lockup - CPU#0 stuck for 11s!
One Athlon64. ** Attachment added: cpuinfo.log http://launchpadlibrarian.net/16686394/cpuinfo.log -- xen dom0 crashes with BUG: soft lockup - CPU#0 stuck for 11s! https://bugs.launchpad.net/bugs/238549 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 238549] Re: xen dom0 crashes with BUG: soft lockup - CPU#0 stuck for 11s!
** Attachment added: lspci-vvnn.log http://launchpadlibrarian.net/16686399/lspci-vvnn.log -- xen dom0 crashes with BUG: soft lockup - CPU#0 stuck for 11s! https://bugs.launchpad.net/bugs/238549 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 238549] Re: xen dom0 crashes with BUG: soft lockup - CPU#0 stuck for 11s!
** Attachment added: uname-a.log http://launchpadlibrarian.net/16686400/uname-a.log -- xen dom0 crashes with BUG: soft lockup - CPU#0 stuck for 11s! https://bugs.launchpad.net/bugs/238549 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 238549] Re: xen dom0 crashes with BUG: soft lockup - CPU#0 stuck for 11s!
** Attachment added: version.log http://launchpadlibrarian.net/16686403/version.log -- xen dom0 crashes with BUG: soft lockup - CPU#0 stuck for 11s! https://bugs.launchpad.net/bugs/238549 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
