** Package changed: python3-defaults (Ubuntu) => pygobject (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1259083
Title:
GTK window layout problems with python
To manage notifications about
** Changed in: indicator-session (Ubuntu)
Status: New => Confirmed
** Changed in: indicator-session (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/12588
** Also affects: indicator-session (Ubuntu)
Importance: Undecided
Status: New
** Also affects: indicator-session
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
** Branch unlinked: lp:~xnox/indicator-sound/ubiquity
** Summary changed:
- Indicators should still provide xdg autostart & dbus
+ Indicators should still provide dbus activation
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
at the moment indicator-sound is broken in ubiquity installer.
** Changed in: indicator-sound
Status: New => Confirmed
** Also affects: indicator-sound (Ubuntu)
Importance: Undecided
Status: New
** Changed in: indicator-sound (Ubuntu)
Status: New => Confirmed
** Changed
given how similar all the indicators are, i'm not sure why there is a
unique job for each one:
instance $INDICATOR
export INDICATOR
start on indicators-loaded or indicator-services-start
stop on desktop-end or indicator-services-end
respawn
exec /usr/lib/x86_64-linux-gnu/indicator-$INDICATOR/indic
I agree with larsu on this one. Can we revert this? Or instead e.g. fix
it properly - rebase upstart-dbus activation patches and still use dbus
activation.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
/sbin must be in all users path on Ubuntu. It is the default, and many
thing will not work, if /sbin is not the default path.
Default path on ubuntu is usually set in /etc/environment and has:
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games"
Can you
actually, if "init" is not on the path we could either add /sbin to path
in Xsession.d scripts, or fallback in Xsession.d to non-upstart managed
user-session.
Even better we could simply merge sbin -> bin, as well as complete the
/usr merge. =)
--
You received this bug notification because you a
This is not a problem with upstart packaging. /sbin is on the default
path in ubuntu, and hence "init" binary is shipped there and is a
reasonable location for the executable, same as e.g. ifconfig. Adding
"extra" symlinks, is not, since quite a lot of things will not work.
Other binaries that are
I have now applied a patch from Ted to "start indicators via upstart
user session in ubiquity" and it fails the installer in a similar
fashion. This clearly shows that "indicators under upstart user session"
tasks are not ready yet, nor were tested under lightdm & ubiquity.
** Changed in: lightdm
verified that discard option is available in partman and selected it
completed server install.
installed system has discard mount option specified in /etc/fstab, and has been
mounted with that option as verified in /proc/self/mountinfo
** Tags removed: verification-needed
** Tags added: verificat
ubiquity - automated installations all passed, manual smoke-test also
works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/978032
Title:
partitioning step doesn't have "discard" as a selectable moun
** Changed in: usb-creator (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1024405
Title:
Port to udisks2
To manage notifications about this bug g
** Changed in: usb-creator (Ubuntu Raring)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1024405
Title:
Port to udisks2
To manage notifications about this bu
** Attachment added: "bootlogs.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1235231/+attachment/3924816/+files/bootlogs.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/12352
On a regular trusty laptop with an SSD i did 6 boots (3 reboots and 3 cold
boots), and compared the boot.logs.
My expectation is to have no less than 6 instances of each unique boot
messages, that is not the case:
1 * Starting Bridge socket events into upstart
1 * Starting modem con
Public bug reported:
unity8 upstart job appears to be using bashism [1]
https://wiki.ubuntu.com/DashAsBinSh#A.24.7B7D
Please review and fix appropriately.
Offending line:
30: exec ${BINARY:-unity8} $ARGS
** Affects: unity8
Importance: Undecided
Status: New
** Affects: unity8
It looks racy - it does come up properly, but very rarely.
If it does come up in "dual-screen mode", $ service lightdm restart, causes it
to loose of the screens (turn black).
Upon login, the other display shows lightdm background with (13.10) instantly
which is later replaced by my user backgrou
Ordering of the splash ahead of emitting rc runlevel level has been done
before in Fedora, to properly show shutdown splash to avoid "scary
messages".
I have also noticed that there are additional messages generated on the
VT through the lifecycle of the machine - that is after lightdm cleared
it
Fedora reference:
https://git.fedorahosted.org/cgit/initscripts.git/commit/?id=9d1c6c1e3bf176d3f89de4ec5551f9960c4986ed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/967229
Title:
Text mode shown br
with external metadata formats in mdadm (ISW / DDF) one needs to
activate the "container" (the controller essentially) and then activate
raid devices configured with it (e.g. isw_raid_members). I see udev
events/rules for the arrays themself, but not for the controller.
--
You received this bug n
Public bug reported:
No reverse dependencies.
A couple of reverse-build dependencies, but they all list libtiff5-dev as first
in the list of alternatives.
Obsolete; superseded by tiff4
** Affects: tiff3 (Ubuntu)
Importance: Medium
Status: Confirmed
** Changed in: tiff3 (Ubuntu)
On 6 December 2013 02:12, Phillip Susi wrote:
> It has been possible in the past since they were managed by dmraid and
> grub had hooks to recognize that and understand that the bios recgonizes
> the array as a single drive. I started some discussion upstream maybe a
> year ago about how to proce
On 5 December 2013 23:20, Phillip Susi wrote:
> You built the raid array using the entire underlying disk drive so grub
> can not be installed on them. You must partition the drive and use a
> partition as the raid component.
>
But that would always be the case with container type raid arrays
(i
** Changed in: kde-workspace (Ubuntu)
Assignee: (unassigned) => Kubuntu Developers (kubuntu-dev)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1257760
Title:
Lightdm doesn't launch Plasma on Ku
On my machine, which is a default desktop I have the following:
$ swapon -s
FilenameTypeSizeUsedPriority
/dev/sdc3 partition 334366680
-1
/dev/zram0 partition 20
All ubiquity bugs are tracked against "Ubuntu distribution" - "package
ubiquity" bugtracker.
Indeed ubiquity upstream project on launchpad doesn't use any
facilities, apart from code hosting.
** Changed in: ubiquity (Ubuntu)
Status: New => Invalid
--
You received this bug notification be
How can one query the status of capslock from console which works in
UTF-8 and non-UTF-8 locales that may or may not use ShiftLock/CapsLock?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/608954
Title:
** Changed in: plymouth (Ubuntu)
Assignee: (unassigned) => Dmitrijs Ledkovs (xnox)
** Summary changed:
- [Plymouth] Progress of fsck isn't show with text logo
+ [Plymouth] Progress of fsck isn't show with ubun text logo
** Summary changed:
- [Plymouth] Progress of fsck is
*** This bug is a duplicate of bug 540645 ***
https://bugs.launchpad.net/bugs/540645
The details plugin shows the fsck now in Trusty. (if booted with splash
press Esc to see details or change/remove "splash" from default grub
linux kernel args in /etc/default/grub) -> that's resolve bug #54064
** Also affects: plymouth (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: plymouth (Ubuntu Trusty)
Importance: High
Assignee: Dmitrijs Ledkovs (xnox)
Status: In Progress
** Changed in: plymouth (Ubuntu Precise)
Status: New => Confirmed
--
u-keyboard (Ubuntu)
Status: Confirmed => Invalid
** Changed in: libpinyin (Ubuntu)
Status: New => Confirmed
** Changed in: libpinyin (Ubuntu)
Importance: Undecided => High
** Changed in: libpinyin (Ubuntu)
Assignee: (unassigned) => Dmitrijs Ledkovs (xnox)
--
** Changed in: upstart
Status: Fix Committed => Fix Released
** Also affects: upstart (Ubuntu Precise)
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/
resolved, once ubiquity got ported to new api to provision custom dbus
address.
** Changed in: ubiquity (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: autopilot (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of
On ubuntu, "ok" "cancel" are useless, instead actions should be dropped,
and at most a bubble (notify-osd) be shown.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1232454
Title:
"Computer will suspe
** Changed in: zsh (Ubuntu)
Importance: Low => Medium
** Changed in: zsh (Ubuntu)
Assignee: (unassigned) => Dmitrijs Ledkovs (xnox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
** Changed in: usb-creator (Ubuntu)
Status: Confirmed => Triaged
** Changed in: usb-creator (Ubuntu)
Importance: Undecided => High
** Changed in: usb-creator (Ubuntu)
Assignee: (unassigned) => Dmitrijs Ledkovs (xnox)
--
You received this bug notification because you are
This doesn't affect quantal and up does it? (As in using usb-creator
_from_ quantal and up to create boot images _of_ quantal and up?)
usb-creator should be SRUed to Precise with fixes, such that users can
prepare usb-sticks of the next release.
** Changed in: usb-creator (Ubuntu)
Status:
** Changed in: udisks (Ubuntu)
Status: Confirmed => Invalid
** Changed in: usb-creator (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: dbus (Ubuntu)
Status: Confirmed => Invalid
** Changed in: dbus (Ubuntu Quantal)
Status: Confirmed => Invalid
** Changed in:
Correct, this is fix released in 2.48, thus Ubuntu 13.04 and up.
** Also affects: mountall (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: mountall (Ubuntu Quantal)
Importance: Undecided
Status: New
** Changed in: mountall (Ubuntu Precise)
Status: N
I have added series tasks, to clearly reflect that this is fixed in
Ubuntu 13.04. In practice this message is shown at times too early, when
/tmp is still being cleared from files generated at previous boot. Thus
one can ignore and wait for it to go away.
--
You received this bug notification bec
** Changed in: plymouth (Ubuntu)
Assignee: (unassigned) => Dmitrijs Ledkovs (xnox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/540645
Title:
no fsck messages shown in details mode (no spl
Public bug reported:
wx-common binary package has moved from src:wxwidgets2.8 (with ubuntu
modifications) to src:wxwidgets3.0 (no ubuntu modifications needed yet).
please remove wx-common binary package
sync/fakesync wxwidgets3.0
autosync is not taking wxwidgets3.0, due to ubuntu modifications..
On 29 November 2013 16:22, Andy Whitcroft wrote:
> For clarity the error referred to in this bug is emitted by the kernel
> from its 16bit entry point. The same check is not made when booted via
> its 32bit entry point. This is arguably a bug, the kernel should check
> and refuse to run when req
** Also affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubiquity (Ubuntu)
Status: New => Fix Released
** Changed in: ubiquity (Ubuntu Precise)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
** Also affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubiquity (Ubuntu)
Status: New => Fix Released
** Changed in: ubiquity (Ubuntu Precise)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Ubiquity includes netcfg.
** Also affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubiquity (Ubuntu)
Status: New => Fix Released
** Changed in: ubiquity (Ubuntu Precise)
Status: New => In Progress
--
You received this bug notification because
** Also affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubiquity (Ubuntu Quantal)
Status: New => Won't Fix
** Changed in: ubiquity (Ubuntu Precise)
Status: New => In Progress
--
You received this bug notification because you are a member of Ub
On 29 November 2013 03:35, Franz Hsieh wrote:
> Hi Stéphane Graber,
>
> I saw your words but I found the partman-auto in ubiquity-2.10.26 is
> still 101ubuntu2, not 101ubuntu2.2. Has 101ubuntu2 integrated to
> ubiquity?
>
Indeed, ubiquity embeds some partman packages. I am opening a task to
rebui
Public bug reported:
git-annex adt tests do not run at all. this should be fixed.
** Affects: git-annex (Ubuntu)
Importance: High
Assignee: Dmitrijs Ledkovs (xnox)
Status: Triaged
** Tags: block-proposed
** Tags added: block-proposed
** Changed in: git-annex (Ubuntu
On 28 November 2013 23:02, David Kalnischkies
<1255...@bugs.launchpad.net> wrote:
> Still, could you please fix sbuild to not use options which do nothing
> Dmitrijs?
>
Please file a bug against sbuild package. I'm just the messenger.
apt-get, sbuild and cross-builds are critical pieces of softwar
On 28 November 2013 18:43, Michael Vogt wrote:
> Right, I'm sorry for the trouble and I agree that it would have been
> better to put the erroring into 0.10.0 instead of 0.9.13.
>
> I will add "-f" back so that sbuild is unbroken. Note that it has no
> effect on "buil-dep" (it does on "source").
** Bug watch added: Debian Bug tracker #720597
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720597
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1255806
Title:
apt-get --purge -yf build-dep h
On 28 November 2013 16:29, Michael Vogt wrote:
> Hey Dmitrijs,
>
> thanks for your bugreport. The "-f" flag means "--fix-broken" and is not
> used by apt the context of build-dep. This is why its complaining. If it
> breaks sbuild we can add it back, but note that it does not have any
> effect AF
Public bug reported:
apt-get --purge -yf build-dep hello, fails with E: Command line option
‘f’ [from -yf] is not known.
this thus breaks sbuild cross-builds. another regression ?
** Affects: apt (Ubuntu)
Importance: High
Status: Confirmed
** Changed in: apt (Ubuntu)
Status
** Tags removed: block-proposed
** Changed in: ffmpeg-php (Ubuntu)
Status: New => Fix Released
** Changed in: guymager (Ubuntu)
Status: In Progress => Fix Released
** Changed in: libavg (Ubuntu)
Status: New => Fix Released
** Changed in: gstreamer0.10-ffmpeg (Ubuntu)
** Changed in: samba (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1255581
Title:
samba4 -> samba transitional packages
To manage notifications abo
cgi?bug=730650
Importance: Unknown
Status: Unknown
** Changed in: samba (Ubuntu)
Assignee: Dmitrijs Ledkovs (xnox) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1255581
On 27 November 2013 10:42, roland aus köln wrote:
> i don`t have the skills for this and i don`t understand, why hpa
> forwarded discussion to lkml at this early stage, as it is a patch
> primary meant for the ubuntu kernel to adress an ubuntu specific
> problem.
>
I understand your concern. The
mp; src:samba) are allowed to go in.
** Affects: samba (Ubuntu)
Importance: Undecided
Assignee: Dmitrijs Ledkovs (xnox)
Status: Confirmed
** Affects: samba4 (Ubuntu)
Importance: Undecided
Assignee: Dmitrijs Ledkovs (xnox)
Status: Confirmed
** Tags: block-propose
** Attachment added: "xsession-errros.log"
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1255569/+attachment/3918401/+files/xsession-errros.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
process 1625: arguments to dbus_message_iter_open_container() were incorrect,
assertion "(type == DBUS_TYPE_ARRAY && contained_signature &&
*contained_signature == DBUS_DICT_ENTRY_BEGIN_CHAR) || (contained_signature ==
NULL || _dbus_check_is_valid_signature (contained_signature))" failed in file
** Attachment added: "left-processes.log"
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1255569/+attachment/3918402/+files/left-processes.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
Public bug reported:
Ursinha reports that upstart-app-launch fails, as it cannot connect to
session-init.
Turns out there is a stale .session file with pid 1625, yet pid 1625 is
not present. It appears that no other session-init started, nor original
one respawned.
xsession-error suggests that i
*** This bug is a duplicate of bug 871752 ***
https://bugs.launchpad.net/bugs/871752
I understand your concerns. At the moment ubiquity does have a keyboard
layout bug on every page of the installer, when user input is required.
It is possible to set / change keyboard layout via indicator (or
Well, my local rebuild failed, due to checks advising one to start
begging for mercy since "ext2" module got dropped =) i didn't do
ignores before but the wikipages explain it. I wonder if chacks can
verify that either ext2/3 modules are present or EXT4_USE_FOR_EXT23 is
enabled.
ps. ♩♯ ♪ ♫ ♬ ♭
** Changed in: mountall (Ubuntu)
Assignee: (unassigned) => Dmitrijs Ledkovs (xnox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/385882
Title:
if fsck exits with error code 4 no way for
** Changed in: mountall (Ubuntu)
Assignee: (unassigned) => Dmitrijs Ledkovs (xnox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1039887
Title:
fstab does not honor /proc mount options
See: https://fedoraproject.org/wiki/Features/UseExt4ForExt3AndExt2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1248270
Title:
Please set CONFIG_EXT3_FS=n and CONFIG_EXT2_FS=n and
CONFIG_EXT4_USE
** Description changed:
When the old code is disabled the ext4 driver takes over and does a
better job and gives a smaller kernel. Specifically the ext4 driver
does a better job of resisting fragmentation since it uses delayed
allocation, and supports online resize, whereas the ext2 drive
** Summary changed:
- Please set CONFIG_EXT[23]=n
+ Please set CONFIG_EXT3_FS=n and CONFIG_EXT2_FS=n and EXT4_USE_FOR_EXT23=y
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1248270
Title:
Please set
These keycodes are sent by Lenovo IdeaPad Yoga 13 as indication which
mode the laptop is in (noteboot, or flipped back enough to turn it into
a laptop mode). On the right side there a small button which is "screen
rotation" lock (portrait/landscape). None of the screen-rotations /
tablet-conversion
*** This bug is a duplicate of bug 630990 ***
https://bugs.launchpad.net/bugs/630990
Yeap, we have multiple keyboard layout related bugs.
https://wiki.ubuntu.com/Ubiquity/KeyboardBug
This one is a duplicate of
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/630990
** This bug has bee
** Changed in: kmediafactory (Ubuntu)
Status: New => Confirmed
** Changed in: kx11grab (Ubuntu)
Status: New => Confirmed
** Changed in: libomxil-components (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
popey: can you check, that e.g. 2fa is required to actually add/sync
UbuntuOne panel
xnox: it doesn't need 2fa. I loggedin via the panel and it used
user/pass and no 2fa. I can see my cloud files in the control panel thing
popey: right, i'd like that to be raised with u1 devs than. Because
ei
2fa handling seems inconsistent. It appears as if one can login in the
Ubuntu Control Panel without entering 2fa, yet on ubiquity side
authentication fails without providing 2fa code, when ubiquity suppose
to be able to get authentication for Ubuntu Control Panel at install
time.
--
You received
librime needs yaml-cpp re-introduced and then finally boost1.53 can be
removed.
** Changed in: openwalnut (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
At the moment, ubiquity & debian-installer do not support Intel Raid
volumes as best as they could. Full support for Intel Raid via mdadm is
planned.
RAID0 does not provide any data-redundancy. To fully utilise both hard-
disks, you can consider an option of deconfiguring raid and installing
onto
** Changed in: phonon-backend-vlc (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1165741
Title:
[needs packaging] phonon-vlc 0.6.2
To manage notifications abou
** Changed in: yaboot (Ubuntu)
Importance: Undecided => High
** Changed in: yaboot (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1254324
Title:
ybin shou
** No longer affects: libdlna (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1254011
Title:
remove from ubuntu archive - never in debian, no upstream ports to
libav9 / dead upstream
To ma
** No longer affects: zoneminder (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1253071
Title:
block migration & demote to proposed for libav transition (removed
from testing in Debian)
T
this was independantly fixed with an equivalent fix. sorry about that.
** Changed in: db (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1160445
Title:
FTB
Public bug reported:
ubuntu-keyboard & libpinyin have now transitioned to db5.3. Therefore it
is now possible to remove db (5.1) from the archive.
** Affects: db (Ubuntu)
Importance: High
Status: Confirmed
** Changed in: db (Ubuntu)
Status: New => Confirmed
** Changed in: d
** Changed in: db (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1178838
Title:
Update to 5.3
To manage notifications about this bug go to:
https://bugs.l
Not yet, still verifying and pushing the transition up. Once i believe
there is nothing else left in libav9 but removals, then i'll subscribe
ubuntu-archive & send a mail to ubuntu-release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
** Changed in: zoneminder (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1253071
Title:
block migration & demote to proposed for libav transition (removed
Public bug reported:
please remove stale arm* handbrake-dbg binaries, they are not
installable as the rest of the packages were not built.
** Affects: handbrake (Ubuntu)
Importance: Undecided
Status: Confirmed
** Changed in: handbrake (Ubuntu)
Status: New => Confirmed
--
Y
** Changed in: quantal-backports
Status: Incomplete => Invalid
** Changed in: handbrake (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1061691
this is entangled with libav9 transition, which was present in
experimental but only now getting resolved in trusty.
** Changed in: handbrake (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
openwalnut has been removed from debian testing. please remove
openwalnut from trusty-release, there is another openwalnut FTBFS in
trusty-proposed. It is now getting entangled with libav9 transition.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
Public bug reported:
gstreamer0.10-ffmpeg is going to be removed from the archive, as it is
holding up libav9 & samba4 transitions (> 90 source packages)
the upgrade path from gstreamer0.10-ffmpeg is to gstreamer1.0-libav.
This is tracked in bug #1221968.
However for trusty, libav has been demot
Public bug reported:
remove from ubuntu archive - never in debian, no upstream ports to
libav9 / dead upstream
** Affects: kmediafactory (Ubuntu)
Importance: Undecided
Status: New
** Affects: kx11grab (Ubuntu)
Importance: Undecided
Status: New
** Affects: libdlna (Ub
** Also affects: mplayer (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/1253071
Title:
block migration & demote to proposed for libav transition (
** Changed in: gstreamer0.10-ffmpeg (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1253071
Title:
block migration & demote to proposed for libav transition (rem
** Changed in: gstreamer0.10-ffmpeg (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1253071
Title:
block migration & demote to proposed for libav transition (rem
What's the progress here? gallery-app is one of the few remaining
packages that is holding back libav9 transition. In particular
gstreamer0.10-ffmpeg dependency must be drop, the upgrade path is to
depend on gstreamer1.0-libav instead.
** Changed in: gallery-app (Ubuntu)
Importance: Undecided =
** Changed in: guymager (Ubuntu)
Assignee: (unassigned) => Dmitrijs Ledkovs (xnox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1253071
Title:
block migration & demote to proposed fo
:
- demote to proposed for libav transition (removed from testing in Debian)
+ block migration & demote to proposed for libav transition (removed from
testing in Debian)
** Changed in: ffmpeg-php (Ubuntu)
Assignee: (unassigned) => Dmitrijs Ledkovs (xnox)
** Changed in: gstreamer0.10-ffmpeg
1 - 100 of 3522 matches
Mail list logo