** Changed in: accountsservice (Ubuntu Groovy)
Status: New => Invalid
** Changed in: accountsservice (Ubuntu Hirsute)
Status: New => Invalid
** Changed in: gnome-shell (Ubuntu Groovy)
Status: New => Invalid
** Changed in: gnome-shell (Ubuntu Hirsute)
Status: New => In
I filed an upstream bug with D-Bus:
https://gitlab.freedesktop.org/dbus/dbus/-/issues/337
Hopefully a maintainer there will be able to give a better opinion as to
what's going on here
** Bug watch added: gitlab.freedesktop.org/dbus/dbus/-/issues #337
https://gitlab.freedesktop.org/dbus/dbus/-/
Thanks! Here's where I think the problem starts:
Ok, let's authenticate to dbus:
Jun 16 08:54:54 alan-hirsute-base-aiamcicscciaelhaktpo systemd[1]: Bus
bus-api-system: changing state AUTHENTICATING → HELLO
...
Jun 16 08:54:54 alan-hirsute-base-aiamcicscciaelhaktpo systemd[1]: Bus
bus-api-syst
That's interesting actually. I thought this was an interaction between
reloading dbus-daemon and daemon-reloading systems at the same time. But
in this cloud case, I don't think dbus is being reloaded, is it?
It's going to be next to impossible for me to look into this in detail
without being able
Yeah, sorry, I don't think that's a reproducer for the bug. You killed
dbus, gdm and everything else, and they obligingly died on you. :)
My feeling is that this bug is about a deadlock that somehow happens
when dbus and/or systemd are reloaded, possibly at the same time. It
looks like dbus stops
Right. It's in the library. Programs will remain using the versions of
the libraries that were on the system when they started, so that means
that you need to upgrade, reboot, and *then* try the restart. I should
update the QA steps to make that more clear, will do.
** Description changed:
[ De
*** This bug is a duplicate of bug 1843982 ***
https://bugs.launchpad.net/bugs/1843982
It's not a regression. It is in fact the same bug happening one last
time. I just explained it in the other bug, hope that's clear.
(If I'm not understanding right, please un-dupe and re-open this bug.)
**
Okay, I've uploaded a fix to groovy and the review queue for 20.04.
** Description changed:
+ [ Description ]
+
+ When accountsservice's daemon is restarted - particularly when there is
+ a user configured for auto login - it can cause code using its library
+ to crash. This is bad because gnome
** Also affects: accountsservice (Ubuntu Focal)
Importance: High
Assignee: Iain Lane (laney)
Status: Triaged
** Changed in: accountsservice (Ubuntu Focal)
Milestone: None => ubuntu-20.04.1
--
You received this bug notification because you are a member of DX
Packages, which
** Description changed:
+ [ Description ]
+
+ When gnome-shell-extension-appindicator is installed and in use, and
+ indicator-application is also in use, there is a race condition that
+ means that Ubuntu sessions might not show any appindicators. They each
+ try to claim a bus name, and only on
t; In Progress
** Changed in: indicator-application (Ubuntu)
Assignee: (unassigned) => Iain Lane (laney)
** Changed in: indicator-application (Ubuntu Bionic)
Assignee: (unassigned) => Iain Lane (laney)
** Changed in: indicator-application (Ubuntu Cosmic)
Assignee: (unassigned)
** Branch linked: lp:~laney/indicator-application/no-autostart-
ubuntu-18.04
** Branch linked: lp:~laney/indicator-application/no-autostart-ubuntu
** Branch linked: lp:~laney/indicator-application/no-autostart-
ubuntu-18.10
--
You received this bug notification because you are a member of DX
Pa
They're all uploaded now. To the SRU team - these are quite delicate
SRUs. I think they're right, but more eyes would be appreciated.
The essence is that when nux-tools is removed-not-purged at a buggy
version, the leftover conffile is harmful. So we picked a core package,
x11-common, and made it
** Changed in: xorg (Ubuntu Artful)
Status: Confirmed => In Progress
** Changed in: xorg (Ubuntu Xenial)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to nux in Ubuntu.
Matching subscriptions: dx-
> Well, I just wanted to make sure this happened as early as possible,
since this is not related to what the package installs, I thought it was
better to handle this in preinst, so that this can be also just removed
at later times.
The thing about the preinst is that it runs super early, you can't
Cheers!
My nux-tools review comments apply to x11-common too. The following are
for x11-common:
What's the reason for doing this in preinst rather than postinst
configure? It's fine in this case but usually we do things in postinst
where possible.
What about adding a "Breaks: nux-tools (<<
4.0.8
Marco, I don't think there is a solution that satisfies all the
requirements and doesn't involve nux cooperating in some way. I've given
you mostly-working debdiffs now - can we please move forward with them?
--
You received this bug notification because you are a member of DX
Packages, which is
This is the solution that I proposed to you in private. It is a fix to
mesa (a "common" package) and a followup to nux-tools.
It needs some testing. In particular I don't think I picked the right
mesa package to use, and we also need to check with the mesa maintainer.
There are various version num
** Patch added: "mesa.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1768610/+attachment/5152448/+files/mesa.debdiff
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to nux in Ubuntu.
Matching subscriptions: dx-packages
https://bu
** Patch added: "nux.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1768610/+attachment/5152447/+files/nux.debdiff
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to nux in Ubuntu.
Matching subscriptions: dx-packages
https://bugs
I'm adding a mesa task, as this bug also needs to be fixed for people
who *already* removed the package without purging it. I suggest mesa,
because that's the package that LIBGL_ALWAYS_SOFTWARE=1 acts on
(mostly?) - so fixing it there will fix for everybody whereas ubuntu-
desktop or whatever might
(you can reassign that task from mesa to something else if it's going to
be fixed elsewhere)
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to nux in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1768610
Title:
l
buntu Artful)
Assignee: (unassigned) => Iain Lane (laney)
** Changed in: nux (Ubuntu Artful)
Assignee: Iain Lane (laney) => Marco Trevisan (Treviño) (3v1n0)
** Changed in: nux (Ubuntu Bionic)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
** Changed in: nux (Ubuntu)
** Also affects: gnome-session (Ubuntu Bionic)
Importance: High
Assignee: Sebastien Bacher (seb128)
Status: Triaged
** Also affects: dconf (Ubuntu Bionic)
Importance: High
Status: Triaged
** Also affects: d-conf (Ubuntu Bionic)
Importance: High
Assignee: Sebastien
Not sure desktop is going to have time to work on this for 17.10.
** Tags added: rls-aa-notfixinf
** Tags removed: rls-aa-notfixinf
** Tags added: rls-aa-notfixing
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
** Changed in: libunity-webapps (Ubuntu)
Status: Expired => Triaged
** Changed in: oxide-qt (Ubuntu)
Status: Expired => Triaged
** Changed in: webbrowser-app (Ubuntu)
Status: Incomplete => Triaged
** Changed in: libunity-webapps (Ubuntu)
Importance: Undecided => Medium
*
Moving from bug #1649310
On Thu, May 04, 2017 at 08:02:57PM -, Steve Langasek wrote:
> On Thu, May 04, 2017 at 03:20:01PM -, Dimitri John Ledkov wrote:
> > Notable things not listed:
> > * oxide/webbrowser app, still in use for amazon "app"
>·
> What pulls in the amazon app? I have heard
Initially assigning xnox, but feel free to move that.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to libunity-webapps in Ubuntu.
https://bugs.launchpad.net/bugs/1688395
Title:
Remove Oxide, webbrowser-app and the Unity webapps
Status in l
We think this is an undisclosed ABI break and we'll rebuild for it (in a
silo) to see if that works.
** Changed in: indicator-datetime (Ubuntu)
Status: New => Triaged
** Changed in: indicator-datetime (Ubuntu)
Importance: Medium => High
** Changed in: indicator-datetime (Ubuntu)
A
Huh, it seems like the new icon is actually shipped by Nautilus itself.
So symlinks in adwaita-icon-theme doesn't make sense. The rest of my
point still stands.
I think a-i-t and h-i-t are good now, so I will upload them.
--
You received this bug notification because you are a member of DX
Packa
I am trying to tell you to be less aggressive in the changes you're
pushing into Ubuntu, especially after feature freeze.
I don't think that making it easier to maintain a PPA is a good reason
to risk bugs in the release proper and to take up a fair amount of
reviewer time. We do not, and will not
The new ubuntu-mono packages symlink org.gnome.Nautilus.svg to system-
file-manager-panel.svg. This makes you get that icon as the icon for
Nautilus, which is wrong.
I think that change should be reverted. I also think that implies that
the -panel change in humanity is also wrong.
I'd really pref
laney@zesty> bzr diff -r tag:0.6.12
=== added symlink 'Humanity-Dark/status/16/org.gnome.Nautilus.svg'
=== target is u'system-file-manager-panel.svg'
=== added symlink 'Humanity-Dark/status/22/org.gnome.Nautilus.svg'
=== target is u'system-file-manager-panel.svg'
=== added symlink 'Humanity-Dark/st
uploaded, please test tomorrow once it hits an image
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to zeitgeist in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1666495
Title:
[Zesty] No default apps shown on fi
Typoed the bug number in the upload, but I think the new nautilus
(3.20.4) fixes this.
** Changed in: gtk+3.0 (Ubuntu)
Status: Confirmed => Invalid
** Changed in: overlay-scrollbar (Ubuntu)
Status: Confirmed => Invalid
** Changed in: nautilus (Ubuntu)
Status: Confirmed => Fi
Trevinho disagrees with me, but I want to put on the record that I think
comment #6's patch is wrong and that instead the VACUUM mode should
explicitly check if the database exists and "return 0" in that case.
Rationale:
It's reasonable to say that it's okay to run without having run the main
pro
** Changed in: humanity-icon-theme (Ubuntu)
Status: New => Fix Committed
** Also affects: ubiquity (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: humanity-icon-theme (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: ubiquity (Ubun
** Changed in: humanity-icon-theme (Ubuntu)
Status: Confirmed => Fix Committed
** Also affects: humanity-icon-theme (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: humanity-icon-theme (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You receive
** Also affects: humanity-icon-theme (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to humanity-icon-theme in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/162268
is fixed. But the fix
is elsewhere.
--
Iain Lane [ i...@orangesquash.org.uk ]
Debian Developer [ la...@debian.org ]
Ubuntu Developer [ la...@ubuntu.com ]
--
You received this bug notification be
I don't see how this can be v-done given the QA steps in the
description, since unity-gtk-module isn't accepted yet. Were those steps
followed? If so, maybe I was too hasty in linking u-g-m into the bug. If
not, please could u-g-m be reviewed and ideally accepted into x-proposed
so this can be re-v
** Description changed:
[ Description ]
In Xenial, when dbus-user-session is installed, dbus' upstart job still
starts a new bus. Things get confused about which bus to talk to.
[ Fix ]
Already fixed in Yakkety. Cherry-pick the upstart job. On top of
Yakkety's version, call `d
Both uploaded.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity-gtk-module in Ubuntu.
https://bugs.launchpad.net/bugs/1644323
Title:
Installing unity8-session-snap adversely effects unity7
Status in Canonical System Image:
Confirmed
unity-gtk-module needs to update the systemd environment now too
** Description changed:
+ [ Description ]
+
+ In Xenial, when dbus-user-session is installed, dbus' upstart job still
+ starts a new bus. Things get confused about which bus to talk to.
+
+ [ Fix ]
+
+ Already fixed in Yakkety. C
Public bug reported:
indicator-transfer is starting on unity 7, but it's not needed there
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: indicator-transfer 0.2+16.10.20160808.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0
Uname: Linux 4.8.0-21-generic x86_64
NonfreeKerne
On Sun, Oct 02, 2016 at 10:27:43AM -, Martin Pitt wrote:
> Iain Lane [2016-10-01 19:26 -]:
> > Hmm. Maybe this is saying that we should bind ubuntu-session.target to
> > something else - like unity7? You can't log in again with an active
> > unity7, so in theory (
ession dies, so it is a bad choice of leader while that is true.
--
Iain Lane [ i...@orangesquash.org.uk ]
Debian Developer [ la...@debian.org ]
Ubuntu Developer [ la...@ubuntu.com ]
--
You rece
ve
unity7, so in theory (if stop is propagated down to graphical-session
and graphical-session-pre) there wouldn't be a need to stop/restart in
the script since everything would be stopped by definition if you're
trying to start unity7 again.
--
Iain Lane
e: Undecided => Medium
** Changed in: gnome-session (Ubuntu)
Importance: High => Medium
** Changed in: gnome-session (Ubuntu)
Assignee: Martin Pitt (pitti) => Iain Lane (laney)
** Changed in: upstart (Ubuntu)
Assignee: Martin Pitt (pitti) => Iain Lane (laney)
--
You re
To restart everything when the session starts, add
systemctl --user stop graphical-session.target
to the systemd-graphical-session.conf and run-systemd-session, after the
block where all failed units are reset.
For the unity-in-upstart case, we might want to not override unity-gtk-
module? May
s/restart everything/stop everything from a previous graphical session/
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity-gtk-module in Ubuntu.
https://bugs.launchpad.net/bugs/1618886
Title:
unity-gtk-module.service is racy
Status in u
Please resubmit this as a merge proposal against lp:libindicator.
I think you should (as well as doing this) fix the earlier calls to
gtk_icon_theme_lookup_by_gicon to use
gtk_icon_theme_lookup_by_gicon_for_scale.
What does gtk_widget_get_scale_factor on the GtkImage give you? If
that's right, us
ion for 16.04.1?
Cheers,
--
Iain Lane [ i...@orangesquash.org.uk ]
Debian Developer [ la...@debian.org ]
Ubuntu Developer [ la...@ubuntu.com ]
--
You received this bug notification because you are a memb
I've blocked this change in xenial-proposed. They only got there because
the CI train bypasses the unapproved queue.
The FFe wasn't approved so they shouldn't really have been uploaded.
I think it's contentious to make HUD take over what was a bit of window
manager functionality, especially so cl
ted
** Changed in: pygobject (Ubuntu)
Assignee: Ubuntu Desktop (ubuntu-desktop) => Iain Lane (laney)
** Changed in: libunity (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to libunity
** Tags removed: rls-x-incoming
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity-lens-music in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1502094
Title:
libgee-0.8-dev should be used, libgee-dev will be
reverted, will make sure the .symbols are fixed before re-uploading the
original fixes
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-appmenu in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1513110
Ti
indicator-appmenu migrated before bamf, from which it uses new symbols,
due to bamf not having a correct .symbols file
** Package changed: unity (Ubuntu) => indicator-appmenu (Ubuntu)
** Changed in: unity
Status: Confirmed => Invalid
--
You received this bug notification because you are
** Also affects: ido (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to ido in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1350821
Title:
unity-panel-s
** Also affects: indicator-session (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: unity (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-sessio
I'm unduping this - bug #1295908 says that there are two ways to fix
(try again or check 'applications' in the filters list). This bug is
about being in a state where neither of these cases work - apps are
never returned until unity is restarted.
I got it once again a couple of weeks ago but I for
** Branch linked: lp:~laney/upstart/lp1433013
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity-lens-applications in Ubuntu.
https://bugs.launchpad.net/bugs/1433013
Title:
Super -> exec vs Alt-F2 -> exec have different environment
Stat
On Mon, Oct 05, 2015 at 08:30:29PM -, Bryan Quigley wrote:
> I haven't had this issue since upgrading to glib2.0 (2.46.0-2). Can
> this and related issues be closed as Fixed?
If they are fixed, then mark them as so.
--
Iain Lane [ i...@orangesq
*** This bug is a duplicate of bug 1480387 ***
https://bugs.launchpad.net/bugs/1480387
** This bug has been marked a duplicate of bug 1480387
Clicking a date to go back or forward a month causes repeated jumps between
two dates
--
You received this bug notification because you are a memb
I think this is fixed
** Changed in: indicator-datetime (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchp
** Changed in: unity-gtk-module (Ubuntu)
Status: Triaged => Invalid
** Changed in: glib2.0 (Ubuntu)
Status: Invalid => Triaged
** Changed in: glib2.0 (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of DX
Packages, which is s
I uploaded it to unstable and will sync when Launchpad picks it up,
thanks for the testing
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity-gtk-module in Ubuntu.
https://bugs.launchpad.net/bugs/1499747
Title:
gedit crashed with SIGABRT
Try the glib in ppa:ubuntu-desktop/ppa please
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity-gtk-module in Ubuntu.
https://bugs.launchpad.net/bugs/1499747
Title:
gedit crashed with SIGABRT in g_assertion_message()
Status in gedit pa
Oh and you can reproduce it by turning the External Tools plugin on
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity-gtk-module in Ubuntu.
https://bugs.launchpad.net/bugs/1499747
Title:
gedit crashed with SIGABRT in g_assertion_message
It's *probably* a bug in unity-gtk-module - Will has been looking into
this.
** Also affects: unity-gtk-module (Ubuntu)
Importance: Undecided
Status: New
** Changed in: unity-gtk-module (Ubuntu)
Status: New => Triaged
** Changed in: unity-gtk-module (Ubuntu)
Importance: Undec
Public bug reported:
This happens on my laptop with 2× but not my desktop with 1×
1. Install d-feet
2. Search for d-feet in the dash
3. Look at the icon - you see the top-left corner of it and not the whole thing
Screenshot is attached.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: unit
I just tried again. You need to have LIM on: Settings -> Appearance ->
Behaviour -> "In the window's title bar", then this bug still happens
(current wily here). Without this then the global bar doesn't have
controls to close the window.
** Changed in: unity
Status: Incomplete => New
** Ch
I think it makes sense. DBus in wily (>= 1.9) does similar for
Xsession.d managed sessions:
# unset login-session-specifics
unset XDG_SEAT
unset XDG_SESSION_ID
unset XDG_VTNR
# tell dbus-daemon --session (and systemd --user, if running)
# to put the Xsession's environment
** Branch linked: lp:~laney/indicator-datetime/timedated-timezone-
property
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1485659
Title:
Dat
We should instead watch timedated's Timezone property
** Changed in: indicator-datetime (Ubuntu)
Status: Confirmed => In Progress
** Changed in: indicator-datetime (Ubuntu)
Assignee: (unassigned) => Iain Lane (laney)
--
You received this bug notification because you are
I think it's a glib GFileMonitor problem - it works again if I build
2.44 and run with that. The code here is watching /etc/timezone to know
when it changes.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matchin
** Tags added: rls-w-incoming
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1308037
Title:
No results from application scope
Status in libunity:
Confi
Forgive me that I'm re-explaining the bug, but I just want it to be
clear. When I see this (I agree it is certainly not #1308037 - when that
happens [haven't seen it for a long time though], *no* searches ever
give a result until Unity is restarted - this is about some searches not
working & retryi
Public bug reported:
I asked in #ubuntu-desktop and people couldn't reproduce this in vivid
or trusty. It happened for me in the most recent wily iso.
Open the indicator, click one of the greyed dates at the start or end of
the month (sometimes requires more than one go). The active date starts
t
** Changed in: evolution-data-server (Ubuntu)
Status: In Progress => Fix Released
** Changed in: indicator-datetime (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in U
ough our correct
process.
Cheers,
--
Iain Lane [ i...@orangesquash.org.uk ]
Debian Developer [ la...@debian.org ]
Ubuntu Developer [ la...@ubuntu.com ]
--
You received this bug notification because you a
See
https://bugs.launchpad.net/ubuntu/+source/qtorganizer5-eds/+bug/1469208
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1460271
Title:
Upd
Uploading to ppa:laney/experimental prior to putting into wily
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1460271
Title:
Update evolution
** Changed in: evolution-data-server (Ubuntu)
Status: Triaged => In Progress
** Changed in: evolution-data-server (Ubuntu)
Assignee: (unassigned) => Iain Lane (laney)
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to ind
On Thu, Jun 11, 2015 at 01:13:14PM +0100, Iain Lane wrote:
> On Thu, Jun 11, 2015 at 11:57:31AM -, Rich Daley wrote:
> > +1 to pwuertz's comment. This is a wider issue than totem so marking it
> > as resolved when there's a workaround only for totem doesn't help
** Changed in: lyx (Ubuntu Vivid)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-appmenu in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1430059
Title:
LyX menu i
re two different bugs. I was checking on another report.
The vlc issue is bug #1340059.
--
Iain Lane [ i...@orangesquash.org.uk ]
Debian Developer [ la...@debian.org ]
Ubuntu Developer [ la.
This affects vlc too (originally reported in bug #1447224) - could you
upload this soon & SRU it?
** Also affects: lyx (Ubuntu Vivid)
Importance: Undecided
Status: New
** Also affects: indicator-appmenu (Ubuntu Vivid)
Importance: Undecided
Status: New
--
You received this bu
(Ubuntu Vivid)
Assignee: (unassigned) => Iain Lane (laney)
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-appmenu in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1447224
Title:
Regression: Unable
** Changed in: indicator-appmenu (Ubuntu)
Status: Confirmed => Invalid
** Changed in: indicator-appmenu (Ubuntu Vivid)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-appmenu in Ubuntu.
Mat
That patch uses gtk_popover_set_transitions_enabled, which is ≥ 3.16 :(
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-appmenu in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1447224
Title:
Regressi
Recording what we said on IRC
- No way to change languages/subtitles in fullscreen
- There's an empty menu when the file doesn't have selectable audio
languages. Can submenus be made insensitive? Or maybe add a "No languages" item.
- Doesn't backport cleanly to 3.14 for SRU to vivid & my
They're about to do this in Debian so we can get patches for free-ish
(or help out there) if we wait.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/
On Fri, May 22, 2015 at 04:18:50PM +0100, Iain Lane wrote:
> On Fri, May 22, 2015 at 03:01:43PM -, Pat McGowan wrote:
> > ** Changed in: canonical-devices-system-image
> >Status: Confirmed => Fix Released
>
> I'm not sure what that means but if it m
to wily. I think
seb128 is handling the rest (+ vivid/overlay).
--
Iain Lane [ i...@orangesquash.org.uk ]
Debian Developer [ la...@debian.org ]
Ubuntu Developer [ la...@ubuntu.com ]
--
You receiv
Can you please test this with the gnome-session in vivid-proposed /
wily? We think it might be the same issue.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs
rhythmbox has a function rb_application_link_shared_menus that might be
similar to what we want here
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-appmenu in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bu
rhythmbox has a function rb_application_link_shared_menus that might be
similar to what we want here
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-appmenu in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bu
Lars said he would take a look at this soon - looks to me (but I don't
know the most about this stuff) like totem's code is failing to populate
the traditional menubar but does for the gear menu - so there's a bug in
totem too in addition to any indicator-appmenu bug.
** Changed in: totem (Ubuntu)
** Changed in: notify-osd (Ubuntu)
Status: In Progress => Fix Released
** Changed in: telephony-service (Ubuntu)
Assignee: Iain Lane (laney) => (unassigned)
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to notify-osd in
1 - 100 of 164 matches
Mail list logo
