I've filed that bug as https://bugs.launchpad.net/ubuntu/+source/debian-
installer/+bug/1737661
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1555904
Title:
opal-prd not installed by default on
Public bug reported:
When attempting a netboot install on bionic, it fails during base system
install, with the message:
. │ │ Debootstrap warning│ │
. │ │ Warning: Failure trying to run: chroot /target dpkg-deb -f │ │
. │ │
I see this earlier in the installer syslog:
Dec 11 08:58:45 debootstrap: tar: skipping unsafe symlink to '/lib
/powerpc64le-linux-gnu/ld-2.26.so' in archive, set
EXTRACT_UNSAFE_SYMLINKS=1 to extract
(along with another bunch of the same error for different symlinks).
I can provide the full
Just attempted with bionic 20101020ubuntu525 netboot installer. However,
this build fails to install on my machine:
│ │ Debootstrap warning│ │
│ │ Warning: Failure trying to run: chroot /target dpkg-deb -f │ │
│ │
Wait, wily has EOLed now. So, I am removing the verification-needed tag,
and adding verification-done.
If you need me to test on any particular version, please let me know
which.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
OK, all fine on trusty! Now checking wily.
** Tags removed: removal-candidate verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1512188
Title:
Sorry - missed this one. The update is fine for xenial, testing with
trusty now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1512188
Title:
Update request: skiboot 5.1.9 for OpenPower machines
Tim: will do; there's still some discussion on the patch, so it's likely
that there will be some changes before merging upstream.
Looks like I had an old initrd there; the ast.ko module is indeed
present in the current xenial installer. Sorry for the noise.
--
You received this bug notification
Any updates here?
=
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1549098
Title:
Systemd init script does not pass --pnor
To manage notifications about this bug go to:
For testing, a suitable check would be to ensure that the opal-prd
daemon is running; just a successful boot, then `service opal-prd
status` would be fine (and that also covers the --pnor argument too).
We can certainly test this on trusty and wily here.
--
You received this bug notification
** Tags added: taco-screen-team
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1555904
Title:
opal-prd not installed by default on ppc64el systems
To manage notifications about this bug go to:
Public bug reported:
Just tried an install with current 16.04 network media, using standard
server package selections, and it looks like opal-prd isn't installed by
default:
[jk@fstn ~]$ dpkg -l opal-prd
dpkg-query: no packages found matching opal-prd
This is required for RAS-type functions
Looks good on 16.04 too:
$ sudo modprobe ipmi_devintf
$ sudo service openipmi start
Job for openipmi.service failed because the control process exited with error
code. See "systemctl status openipmi.service" and "journalctl -xe" for details.
$ lsmod | grep ipmi
ipmi_devintf 13691 0
(That's with your fixed package installed. Without, we see the
ipmi_devintf module being removed)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1318317
Title:
openipmi startup script
Looks good on 16.04 too:
$ sudo modprobe ipmi_devintf
$ sudo service openipmi start
Job for openipmi.service failed because the control process exited with error
code. See "systemctl status openipmi.service" and "journalctl -xe" for details.
$ lsmod | grep ipmi
ipmi_devintf 13691 0
(That's with your fixed package installed. Without, we see the
ipmi_devintf module being removed)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1318317
Title:
openipmi startup script removes kernel
@Nish: I tested against 14.04. We can take a look at 16.04 too, if you
like.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1318317
Title:
openipmi startup script removes kernel
@Nish: I tested against 14.04. We can take a look at 16.04 too, if you
like.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1318317
Title:
openipmi startup script removes kernel modules
To manage
Or even better, (somehow) use the value from /etc/default/opal-prd.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1549098
Title:
Systemd init script does not pass --pnor
To manage notifications
Nish: looks good to me:
[jk@hab2 ~]$ sudo service openipmi stop
[jk@hab2 ~]$ sudo modprobe ipmi_devintf
[jk@hab2 ~]$ lsmod | grep ipmi
ipmi_devintf 13227 0
ipmi_powernv5657 0
ipmi_msghandler51494 2 ipmi_powernv,ipmi_devintf
[jk@hab2 ~]$ sudo service openipmi
Nish: looks good to me:
[jk@hab2 ~]$ sudo service openipmi stop
[jk@hab2 ~]$ sudo modprobe ipmi_devintf
[jk@hab2 ~]$ lsmod | grep ipmi
ipmi_devintf 13227 0
ipmi_powernv5657 0
ipmi_msghandler51494 2 ipmi_powernv,ipmi_devintf
[jk@hab2 ~]$ sudo service openipmi
** Tags added: taco-screen-team
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1549098
Title:
Systemd init script does not pass --pnor
To manage notifications about this bug go to:
Public bug reported:
We have a --pnor option that almost all opal-prd invocations will need.
In the debian packaging, we have an /etc/defaults file that controls
this:
[jk@pudge skiboot-5.1.1]$ grep PNOR debian/opal-prd.default
PNOR_DEVICE=/dev/mtd0
This is consumed by the sysv init script for
Hi Nish,
I'll give it a try, thanks!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1318317
Title:
openipmi startup script removes kernel modules
To manage notifications about this
Hi Nish,
I'll give it a try, thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1318317
Title:
openipmi startup script removes kernel modules
To manage notifications about this bug go to:
Also, for completeness: running the PRD daemon is only required on
machines that have the "diagnostics" OPAL firmware feature. At present
(and this is unlikely to change), the set of these machines is
equivalent to the set of OpenPOWER machines.
To be exact, this is indicated on a running system
Hi Steve,
> I also don't know
> which systems are already supported by the version of opal-prd in trusty;
> are the openpower systems the only ones we need to watch for regressions on,
> or are there others?
The former: opal-prd is only used on OpenPOWER machines, so that's all
we'll need to
@henrix: I'll need some help with testing this; it's not like we can
just boot into the new kernel directlyb. We'll chase this up with
#ubuntu-devel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
hi Tim,
Yep, that looks like it'll sort it. Is there any reference around for
building an installer image with this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1514711
Title:
Installer doesn't
Any news on this one? It's preventing folks from installing on OpenPOWER
machines if they're relying on VGA.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1514711
Title:
Installer doesn't include
thanks Nish! I just installed that package:
[jk@fstn2-p1 sources.list.d]$ sudo apt-get remove --purge openipmi
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
openipmi*
0 to upgrade, 0 to newly install, 1 to
thanks Nish! I just installed that package:
[jk@fstn2-p1 sources.list.d]$ sudo apt-get remove --purge openipmi
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
openipmi*
0 to upgrade, 0 to newly install, 1 to
>From comment #3:
> This breaks any system daemon that requires in-band IPMI.
To provide a little more detail here: the opal-prd daemon, necessary for
runtime system management on OpenPOWER machines, may communicate with
the BMC using IPMI. As part of that daemon's initialisation, it ensures
>From comment #3:
> This breaks any system daemon that requires in-band IPMI.
To provide a little more detail here: the opal-prd daemon, necessary for
runtime system management on OpenPOWER machines, may communicate with
the BMC using IPMI. As part of that daemon's initialisation, it ensures
We see the same on OpenPower machines. Since we don't use the ipmi_si
interface, the openipmi init script fails, which removes modules which
we do need.
root@g43L:~# grep -B2 IPMI_SI /etc/default/openipmi
# Enable standard hardware interfaces (KCS, BT, SMIC)
# You probably want this enabled.
We see the same on OpenPower machines. Since we don't use the ipmi_si
interface, the openipmi init script fails, which removes modules which
we do need.
root@g43L:~# grep -B2 IPMI_SI /etc/default/openipmi
# Enable standard hardware interfaces (KCS, BT, SMIC)
# You probably want this enabled.
Pavaman - thanks for verifying. The latter issue sounds like a BMC
problem, which we're following-up separately.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Pavaman - thanks for verifying. The latter issue sounds like a BMC
problem, which we're following-up separately.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Assigning to linux package, as per
https://wiki.ubuntu.com/Bugs/FindRightPackage.
** Package changed: ubuntu => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1514711
Title:
Funnily enough, I saw the same issue last night. Also caused by a cat.
The system seemed to be completely unresponsive, but I don't think it
had locked completely; after a few minutes of holding down backspace
(with no indication in the UI that characters are actually being
deleted), I managed to
Public bug reported:
When booting the Ubuntu 14.03.4 installer on an OpenPower machine with a
VGA monitor attached, we see no output - the only installer output is
over the physical UART (or SOL session).
Petitboot is displayed over both VGA and UART, but not the installer UI.
It seems like the
** Tags added: taco-screen-team
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1447500
Title:
Ubuntu creates cluttered Petitboot menu entries
To manage notifications about this bug go to:
@mathieu-tl: ok, super. Sorry, I didn't mean to be badgering you there,
just wanted to make sure it's tracked somewhere! :)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ipmitool in Ubuntu.
https://bugs.launchpad.net/bugs/1509896
@mathieu-tl: ok, super. Sorry, I didn't mean to be badgering you there,
just wanted to make sure it's tracked somewhere! :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1509896
Title:
IPMI USB
Is it possible to do the same for trusty too?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ipmitool in Ubuntu.
https://bugs.launchpad.net/bugs/1509896
Title:
IPMI USB SCSI endpoint discovery can fail on OpenPower machines
To
Is it possible to do the same for trusty too?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1509896
Title:
IPMI USB SCSI endpoint discovery can fail on OpenPower machines
To manage notifications
Public bug reported:
Trusty through xenial currently have version 5.1.1 of the skiboot source
package (producing opal-prd and opal-utils binary packages), while we've
had a number of updates since, which introduce compatibility for newer
hardware & firmware facilities.
Can we have this updated
Public bug reported:
The current ipmitool code can fail to find an IPMI device on my
OpenPower machine, due to bug in the USB SCSI device discovery process.
This will only happen if the user has adjusted the number of virtual USB
devices that the BMC exports. However, the failure mode isn't
Public bug reported:
The current ipmitool code can fail to find an IPMI device on my
OpenPower machine, due to bug in the USB SCSI device discovery process.
This will only happen if the user has adjusted the number of virtual USB
devices that the BMC exports. However, the failure mode isn't
@mathieu-tl: yes, if we can disable the OS prober when we're installing
onto a petitboot-based machine, that'd be great.
Since petitboot will parse the other OS' config files independently, we
don't need to include them in Ubuntu's list. Is there a current
mechanism to detect the machine type?
> Jeremy, I know that there are some needs on the kernel side, but there is a
> 4.2
> in experimental, would it be enough ?
Yes, that has the headers required.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
there's no package in any
That is not true. Wily (15.10) has the inital 5.0.4 version.
You trimmed off the part where it said Ubuntu release - wily isn't
released yet. :)
@mathieu-tl: looks good!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hi Frédéric,
The upgrade gives us Firestone platform support, and will mean we'll be
using code that has gone through IBM's own testing procedures.
Including 5.1.1 would mean fewer changes - there's no package in any
Ubuntu release yet, so there should be no trouble starting from this
version,
OK, 5.1.1 has just been tagged, that would be a great place to base this
on, as it has added support for future OpenPower platforms.
Ubuntu folks: do you need anything from IBM for this package?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
We've had a couple of bugfix changes go into upstream recently; I'd
suggest picking up the current stable branch, at or beyond commit
14d4ffa7.
This should get a tag for 5.0.6 any day now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Package changed: ubuntu = linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1482343
Title:
Trigger a checkstop on unrecoverable MCE/HMI errors to inform BMC/OCC
about the error.
To
Just booted 3.19.0-26-generic, all looks good!
** Tags removed: verification-needed-vivid
** Tags added: verification-done-vivid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1464560
Title:
Hi Chris,
The following commits should bring the PRD support into the current
vivid branch, using only pristine upstream changes:
d800ba1 powerpc/powernv: Move OPAL API definitions to opal-api.h
d7cf83f powerpc/powernv: Move opal-api.h closer to the Skiboot version
ed59190 powerpc/powernv: Add
And we've just had a couple of fixes hit linux-next too:
7185795 powerpc/powernv: fix construction of opal PRD messages
cdf2bc1 powerpc/include: Add opal-prd to installed uapi headers
Yes, as Breno has mentioned, we're looking at 3.19 and (if possible)
3.16.
--
You received this bug
We've just had the last of our feature-enablement patches hit linux-
next:
1cbb4a1 mtd: powernv: Add powernv flash MTD abstraction driver
The MTD driver is required for full PRD functionality, but I can open a
separate issue if you prefer.
--
You received this bug notification because you are
Public bug reported:
Following up on patches that were skipped in bug 1439562, this request
is for the PRD (Processor Runtime Diagnostics) support in the ppc64le
kernel.
Patches have recently hit linux-next:
0d7cd85 powerpc/powernv: Add opal-prd channel
594fcb9 powerpc/powernv: Expose OPAL APIs
OK, the prd changes have hit linux-next:
48c0615 powerpc/powernv: Merge common platform device initialisation
594fcb9 powerpc/powernv: Expose OPAL APIs required by PRD interface
0d7cd85 powerpc/powernv: Add opal-prd channel
Would you prefer me to open a separate LP issue for these?
Once these
Hi Chris,
Yes, 6a11e5c6 adds the IPMI driver. Is that not already in the vivid
tree?
The PRD and MTD changes are headed upstream, I was just sending to you
for an indication of what to expect.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hi Chris,
Thanks for taking this on for a utopic backport.
Instead of using that ubuntu/utopic branch in the openpower tree, I'd
suggest using the upstream commits that we have listed in this bug (and
Tim has applied); that way, you'll be getting the latest changes, and
have less merging to do
OK, we have a new set of patches merged. Would you like these in a
separate bug?
[the first does change a powerpc-specific syscall number, if that
affects your preference of SRU vs. freeze]
The following patches have been merged to linux-next:
1d9d9bd powerpc: Add a proper syscall for switching
Sure thing. The patch in my ubuntu-vivid git tree is slightly modified
from the upstream commit - just so we don't need to include those
prerequisites.
However, if you're after pristine upstream commits, the following will
work on top of the vivid tree (as at 83f803a6):
commit
Also, the 'powerpc/powernv: Support OPAL requested heartbeat' change
requires a couple of prereqs if you're looking to use the pristine
upstream version too:
commit 08135139430fabdeaa990da8a9e0d436aad0672b
Author: Michael Ellerman m...@ellerman.id.au
Date: Wed Jan 28 15:10:33 2015 +1100
This should do the trick:
git cherry-pick 4c3b2168 a4bcbe6a 529d235a \
08135139 c1c3a526 b921e902 \
3bf57561 e8a51e1b 5590f319
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1439562
Title:
OK, I'll keep this bug updated as the patches are merged.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1439562
Title:
backport request: include support for OpenPower hardware
To manage
Also:
744b976 powerpc/powernv: Add OPAL soft-poweroff routine
- in linus/master: 7f43e71e8c538356efd5b33a183e6d9ace4739a5
- this is a prerequisite for:
63df164 powerpc/powernv: reboot when requested by firmware
--
You received this bug notification because you are a member of Ubuntu
Bugs,
We've had a few patches merged to linux-next:
6f4b0f5 drivers/sbus/char/envctrl.c: ignore orderly_poweroff return value
- merged to linux-next/master: dc4f016cb8b67128c42f165802794f0b6d70405c
53cffb5 kernel/reboot.c: add orderly_reboot for graceful reboot
- merged to linux-next/master:
Tim - yes, they're both related to OpenPower hardware, and aren't
required for guest VMs. Sounds fine then.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1439562
Title:
backport request: include
Signed-off-by: Jeremy Kerr j...@ozlabs.org
commit e1c89541e7163494ad091f3c2622649d91ac7597
Author: Benjamin Herrenschmidt b...@kernel.crashing.org
Date: Mon Feb 16 14:59:08 2015 +1100
device: Add dev_of_node() accessor
Suggested by Arnd Bergmann, this gives a practical accessor
Also: these changes add a config var: CONFIG_MTD_POWERNV_FLASH, for the
presence of the powernv mtd driver.
Will the new ipmi_powernv and powernv_flash modules appear in the
linux-image package (rather than linux-image extras)?
--
You received this bug notification because you are a member of
Public bug reported:
I'd like to switch to/from 'Continuous' (View → Continuous) mode through
the HUD, but it seems like none of Evince's menu items are appearing in
the HUD.
Steps to reproduce:
1) Open a file with evince
2) Note that there is a Continuous option in the View menu
3) Hit Alt to
apport information
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/1088778/+attachment/3456960/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1088778
apport information
** Attachment added: KernLog.txt
https://bugs.launchpad.net/bugs/1088778/+attachment/3456961/+files/KernLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1088778
Title:
apport information
** Attachment added: ProcEnviron.txt
https://bugs.launchpad.net/bugs/1088778/+attachment/3456962/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1088778
apport information
** Attachment added: RelatedPackageVersions.txt
https://bugs.launchpad.net/bugs/1088778/+attachment/3456963/+files/RelatedPackageVersions.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Just committed this to sbsigntool, to use the updated mountpoint. v0.5
has this (and only this) change.
commit ab63e31bb8ba8ef4b51b8698cc5e89466e003989
Author: Jeremy Kerr jeremy.k...@canonical.com
Date: Mon Oct 8 12:07:43 2012 +0800
sbkeysync: change default efivarfs mountpoint to /sys
These patches, plus a documentation patch for efivars (91a8a30), are now
in Matt Fleming's next tree:
git://git.kernel.org/pub/scm/linux/kernel/git/mfleming/efi.git
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Also, that original link (to lkml.org) seems to be a superseded series.
The patchwork link has the most recent code.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1063061
Title:
please backport
Sorry, I stand corrected, it's the same.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1063061
Title:
please backport support for EFI vars 1KB
To manage notifications about this bug go to:
We'd need all three patches in that series:
https://patchwork.kernel.org/bundle/jk/efivarfs/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1063061
Title:
please backport support for EFI vars 1KB
Have upgraded to 3.4.2.1-0ubuntu1; the mute button seems to work now,
and mutes its pulse source rather than a (incorrect) sink.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1003945
Title:
Toggle
It sure does. However, shouldn't it be muting its own pulse sink, rather
than muting a pulse source?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1003945
Title:
Toggle Audio Transmission does not
I'm happy to arrange a call if you need a hand with testing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1003945
Title:
Toggle Audio Transmission does not mute SIP audio transmission
To manage
If I toggle empathy's mute button while having the 'Input devices' tab
of pavucontrol visible, I can see that the level sliders for my built-in
audio device are reduced to zero when mute is enabled.
However, I'm not using that device for input to empathy; I'm using a
second sound device, a pair
Public bug reported:
During a SIP call, empathy provides a button to mute audio transmission.
However, it looks like this does not work: audio is still transmitted to
the other party.
To reproduce:
1) Start a SIP call with colleagues
2) Talk to colleagues
3) Click 'Toggle Audio Transmission'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1003945
Title:
Toggle Audio Transmission does not mute SIP audio transmission
To manage notifications about this bug go to:
not
getting far enough to init a framebuffer or anything shiny.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Jeremy Kerr (jk-ozlabs)
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
From: Benjamin Herrenschmidt b...@kernel.crashing.org
BugLink: https://bugs.launchpad.net/bugs/959959
The code for powersurge SMP would kick in and cause a crash
at boot due to the lack of a NULL test.
Signed-off-by: Benjamin Herrenschmidt b...@kernel.crashing.org
Signed-off-by: Jeremy Kerr
Not possible to run apport-collect in this situation, confirming
manually.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/959959
Adam reports that this patch fixes the issue. Builds are at
http://people.canonical.com/~jk/powerpc-oldworld-smp/ , if anyone else
would like to test.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Anca,
Why not CC: lkml ?
Because it's already in mainline. Refer:
Cherry-picked from upstream commit
78c5c68a4cf4329d17abfa469345ddf323d4fd62
Cheers,
Jeremy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Can still reproduce on the 12.04 alpha.
However, after some further digging, this looks specific to gnome-
terminal windows; as described above, I have the following settings:
Decoration Windows: !(class=Gnome-terminal)
Shadow Windows: all
- in order to remove the decoration (but not shadow)
apport information
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/615234/+attachment/2773162/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/615234
Title:
apport information
** Attachment added: BootLog.gz
https://bugs.launchpad.net/bugs/615234/+attachment/2773163/+files/BootLog.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/615234
Title:
Not
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/615234/+attachment/2773164/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/615234
apport information
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/615234/+attachment/2773165/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/615234
1 - 100 of 319 matches
Mail list logo
