** Also affects: webapps-sprint
Importance: Undecided
Status: New
** Changed in: webapps-sprint
Assignee: (unassigned) => Alberto Mardegan (mardy)
** Changed in: webapps-sprint
Milestone: None => sprint-25
--
You received this bug notification because you are a member of
** Changed in: webapps-sprint
Milestone: sprint-23 => sprint-24
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
https://bugs.launchpad.net/bugs/1551686
Title:
browser leaks old location data to web
** Changed in: webapps-sprint
Milestone: sprint-22 => sprint-23
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
https://bugs.launchpad.net/bugs/1551686
Title:
browser leaks old location data to web
** Changed in: location-service (Ubuntu)
Importance: Undecided => High
** Changed in: oxide
Status: In Progress => Invalid
** Changed in: webapps-sprint
Importance: Undecided => Critical
** Changed in: webapps-sprint
Importance: Critical => High
--
You received this bug
** Changed in: webapps-sprint
Milestone: sprint-21 => sprint-22
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
https://bugs.launchpad.net/bugs/1551686
Title:
browser leaks old location data to web
To summarize the analysis and the plan forward, we have identified a
series of fixes and improvements to various parts of the stack:
Oxide: the ubuntu-specific provider code or related logic could filter
out obvious bogus values returned by the location-service which do not
meet the maximumAge
** Changed in: location-service (Ubuntu)
Assignee: (unassigned) => Alberto Mardegan (mardy)
** Also affects: webapps-sprint
Importance: Undecided
Status: New
** Changed in: webapps-sprint
Assignee: (unassigned) => Alberto Mardegan (mardy)
** Changed in: webapps-sprint
Oxide is normally also pulling updates once permission has been granted:
http://bazaar.launchpad.net/~oxide-
developers/oxide/oxide.trunk/view/head:/qt/core/browser/oxide_qt_location_provider.cc#L352
Looking at that part, do you see something that would be at odds with
the logic in the other
** Changed in: webapps-sprint
Milestone: sprint-15 => None
** Changed in: webapps-sprint
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to shotwell in Ubuntu.
** Changed in: webapps-sprint
Milestone: sprint-14 => sprint-15
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to shotwell in Ubuntu.
https://bugs.launchpad.net/bugs/1453549
Title:
Cannot publish to Facebook
To manage
** Changed in: webapps-sprint
Milestone: sprint-11 => sprint-14
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to shotwell in Ubuntu.
https://bugs.launchpad.net/bugs/1453549
Title:
Cannot publish to Facebook
To manage
** Changed in: webapps-sprint
Milestone: sprint-10 = sprint-11
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to shotwell in Ubuntu.
https://bugs.launchpad.net/bugs/1453549
Title:
Cannot publish to Facebook
To manage
** Changed in: webapps-sprint
Status: New = Confirmed
** Changed in: webapps-sprint
Importance: Undecided = High
** Changed in: webapps-sprint
Assignee: (unassigned) = Alberto Mardegan (mardy)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
** Changed in: account-plugins
Status: In Progress = Fix Released
** Changed in: webapps-sprint
Status: In Progress = Fix Released
** Changed in: account-plugins (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of
** Also affects: webapps-sprint
Importance: Undecided
Status: New
** Changed in: webapps-sprint
Milestone: None = sprint-9
** Changed in: webapps-sprint
Milestone: sprint-9 = sprint-10
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
** Changed in: webapps-sprint
Status: Confirmed = In Progress
** Changed in: webapps-sprint
Milestone: sprint-8 = sprint-9
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to empathy in Ubuntu.
Public bug reported:
The bug occurs after removing location access authorization to an
application. The location is still available to the application, despite
the user having revoked access from within USS Privacy Location.
To reproduce:
1. Open a map application, like Here map
2. Allow
So the conclusion is that this is not a webbrowser-app/container problem
anymore at this stage. Marking invalid for the web part.
** Changed in: webbrowser-app
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
Indeed, the Location plugin in System settings does /hide/ unconfined
entries, because:
1. there is no way to get back to the actual application desktop file to
display its name and icon: we just know that an undefined unconfined
application was granted access
2. in theory unconfined applications
for now.
** Changed in: ubuntu-system-settings (Ubuntu)
Status: New = Confirmed
** Changed in: ubuntu-system-settings (Ubuntu)
Assignee: (unassigned) = David Barth (dbarth)
** Tags added: touch-2010-10-09
--
You received this bug notification because you are a member of Ubuntu
Desktop
@Ruben: for an LTS the process requires that things be fixed upstream first
(evolution 14.10 in that case) and then backported to the stable release.
This is to avoid fixes not being carried over because they applied to an
older release.
On Sun, Sep 7, 2014 at 3:29 PM, Coeur Noir
For reference, and testers in particular, you can start the service
manually with:
/usr/bin/trust-stored-skeleton \
--remote-agent DBusRemoteAgent --bus=system \
--local-agent MirAgent \
--trusted-mir-socket=/var/run/user/$(id -u)/mir_socket_trusted \
--for-service
** Also affects: account-plugins/13.10
Importance: Undecided
Status: New
** Also affects: account-plugins/12.10
Importance: Undecided
Status: New
** Also affects: account-plugins/13.04
Importance: Undecided
Status: New
** Also affects: friends-app (Ubuntu)
Our central Facebook API key has been revoked.
The impact is that Ubuntu users cannot use the Facebook integration
anymore, ie post messages or photos from applications using our central
key: Empathy, the Photo scope, the Friends app and Shotwell to a lesser
extent.
All releases (14.04, 12.10+)
** Branch linked: lp:~dbarth/account-plugins/fix-maintainer-scripts
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to empathy in Ubuntu.
https://bugs.launchpad.net/bugs/1304798
Title:
Unable to access Facebook online account
To
Considered fixed by the glib update. Re-open if the issue can still be
reproduced.
** Changed in: bamf (Ubuntu Precise)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
** No longer affects: metacity (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in Ubuntu.
https://bugs.launchpad.net/bugs/960434
Title:
Application title text on panel is now huge
To manage notifications about
** Changed in: metacity (Ubuntu)
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in Ubuntu.
https://bugs.launchpad.net/bugs/950774
Title:
metacity should report union of workspaces in
** Also affects: unity-2d
Importance: Undecided
Status: New
** Changed in: unity-2d
Status: New = In Progress
** Changed in: metacity (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
** Changed in: unity
Milestone: None = 5.6.0
** Changed in: unity (Ubuntu Precise)
Milestone: None = ubuntu-12.04-beta-1
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
** Changed in: unity
Milestone: 4.26.0 = 4.28.0
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/868354
Title:
Duplicate indicators bar and desktops with overlapped screens
To
** Changed in: unity-foundations
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/821290
Title:
[panel] Unable to access menus with Alt
** Changed in: unity-foundations
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/804009
Title:
clicking on the volume slider closes the
** Changed in: unity (Ubuntu Oneiric)
Assignee: Canonical Desktop Experience Team (canonical-dx-team) = Jason
Smith (jassmith)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
So that bug and bug 808918 seem to indicate that this is not a problem
in either u2d, u3d or bamf, but more a regression in gedit. It was
working in natty, and the part of the code that starts applications
didn't change in that regard. Besides the anomaly is limited to gedit
and other programs
So that bug and bug 827414 seem to indicate that this is not a problem
in either u2d, u3d or bamf, but more a regression in gedit. It was
working in natty, and the part of the code that starts applications
didn't change in that regard. Besides the anomaly is limited to gedit
and other programs
I think the original bug is definitely a gnome-settings-daemon crash.
The second crash related to unity-place-applications is a different
issue. If it's still reproducible it should be tracked as a separate
bug.
** Changed in: gnome-settings-daemon (Ubuntu)
Status: Confirmed = Invalid
**
We can either remove the option or gray it when the globalmenu is in
use.
Matthew: can you recommend one of the 2 alternatives?
** Also affects: ayatana-design
Importance: Undecided
Status: New
** Changed in: gnome-control-center (Ubuntu)
Status: Confirmed = Incomplete
**
** Also affects: unity
Importance: Undecided
Status: New
** Changed in: unity
Milestone: None = iteration-2
** Changed in: unity
Assignee: (unassigned) = Thomas Thurman (marnanel)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
** Also affects: unity
Importance: Undecided
Status: New
** Changed in: unity
Milestone: None = iteration-2
** Changed in: unity
Assignee: (unassigned) = Thomas Thurman (marnanel)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
** Tags removed: 0day-sru
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/740864
Title:
Find result is too light gray
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
Let me try to clarify and help find the right plan of action:
1. the release is closed now
2. it can't go as a 0day-sru, because we would have to have a clear definition
of what to put in, and a clear test plan, and do that for the next week before
the release; i don't see that happen right now
Additional information for the record.
The feature is currently enabled by default, with the applications
listed at: http://bazaar.launchpad.net/~ayatana-scrollbar-team/ayatana-
scrollbar/trunk/view/head:/os/os-utils.c#L57 It is based on the
application compatibility list captured at
Hereby requesting a review of the FFE request.
The gtk support patch is up for review at: https://bugs.launchpad.net
/ayatana-scrollbar/+bug/740276 (see comment #2) along with an updated
branch supporting whitelist, blacklist, and environment variable to
control when the feature should be active.
Sorry for the confusion, please consider the patch as of comment #3 here
https://bugs.launchpad.net/ayatana-scrollbar/+bug/740276/comments/3
It's been tested and validated with rev. 172 of the library
(http://bazaar.launchpad.net/~ayatana-scrollbar-team/ayatana-
scrollbar/trunk/revision/172)
It works on more than a fixed set of applications: the whitelist is
meant to enable it by default, for a set of applications that we are
testing more thoroughly. It should work for all gtk applications using
gtk_scrolled_window, ie most of the gnome applications we know of.
The missing LTR
** Changed in: unity-foundations
Milestone: unity-3.8.0-beta = unity-3.6.8
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in ubuntu.
https://bugs.launchpad.net/bugs/692194
Title:
Desktop menu adjustments for Natty
--
Hey Paolo ;)
Is there a way you can reproduce the issue? For example, try to remove
things from the launcher, and then try to re-add them.
I'm also interested in the other crash reports you listed in comment #3.
Just report as individual bugs with apport-bug /var/crash/crash file
path
Thanks
The main resource (Cimi) can't really help with the rest of the unity
issues. Cimi is dedicated to toolkit, theme and theme engine
improvements for Natty.
I understand however that bugs triggered by this optional module should
not impact the rest of the release. So we could update the gtk apport
Gord indicates it's a nautilus gconf settings. However, setting it would
break the classical gnome desktop.
Passing on to didrocks, to see if there is a mandatory key that could be
toggled depending on the session selected by the user.
** Also affects: unity
Importance: Undecided
** Also affects: unity-2d
Importance: Undecided
Status: New
** Changed in: unity-2d
Status: New = Confirmed
** Changed in: unity
Status: New = Confirmed
** Changed in: unity
Importance: Undecided = Low
--
You received this bug notification because you are a member
@Ted: not sure what's left to fix, but after the big refactoring, it's
worth checking if the problem is definitely fixed or not.
** Changed in: indicator-application
Assignee: Karl Lattimer (karl-qdh) = Ted Gould (ted)
--
You received this bug notification because you are a member of
Public bug reported:
The https://launchpad.net/ayatana-scrollbar project provides an
alternative scrollbar for GTK applications, to optimize for screen real-
estate.
The feature requires a patch to GTK+2.0 to optionally load the
replacement scrollbars.
This bug captures the request to integrate
** Also affects: ayatana-ubuntu
Importance: Undecided
Status: New
** Changed in: ayatana-ubuntu
Status: New = Confirmed
** Changed in: ayatana-ubuntu
Importance: Undecided = Medium
** Changed in: ayatana-ubuntu
Assignee: (unassigned) = Ted Gould (ted)
** Changed in:
** Changed in: ayatana-ubuntu
Milestone: natty-alpha-3 = ubuntu-11.04-beta
** Changed in: nautilus (Ubuntu Natty)
Milestone: natty-alpha-3 = ubuntu-11.04-beta-1
** Changed in: nautilus (Ubuntu Natty)
Importance: Medium = High
** Changed in: ayatana-ubuntu
Importance: Medium = High
Ryan: we need your help for fixing this issue rapidly, it's making the
life of compiz really miserable now (and Sam's as well). Thanks
** Changed in: glib2.0 (Ubuntu)
Assignee: (unassigned) = Ryan Lortie (desrt)
** Changed in: glib2.0 (Ubuntu)
Importance: Undecided = High
** Changed in:
Cimi: can you investigate the possibility of providing support for
relative font sizes / weights in the theme? Thanks.
** Also affects: ayatana-ubuntu
Importance: Undecided
Status: New
** Changed in: ayatana-ubuntu
Assignee: (unassigned) = Andrea Cimitan (cimi)
** Changed in:
xsplash has been obsoleted now.
** Changed in: xsplash (Ubuntu)
Status: Triaged = Invalid
** Changed in: xsplash (Ubuntu)
Assignee: David Barth (dbarth) = (unassigned)
** Changed in: xsplash
Status: Confirmed = Invalid
--
You received this bug notification because you
** Changed in: gnome-settings-daemon (Ubuntu)
Assignee: David Barth (dbarth) = (unassigned)
** Changed in: gnome-power-manager (Ubuntu)
Assignee: David Barth (dbarth) = (unassigned)
** Changed in: notify-osd
Assignee: Mirco Müller (macslow) = (unassigned)
--
You received
We don't have plans to implement focus-follows-mouse support in Natty.
We can review designs and patches in the flow of this bug report though.
** Changed in: gnome-control-center (Ubuntu)
Assignee: Canonical Desktop Experience Team (canonical-dx-team) =
(unassigned)
** Changed in:
Ted: What's the delta with the patch you already made to nautilus? What
is left to do or fix compared to Maverick?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in ubuntu.
https://bugs.launchpad.net/bugs/692194
Title:
I think the design, as defined by Mark, is fix-released, so the ball is
in the DX court.
** Changed in: ayatana-design
Status: New = Fix Released
** Changed in: nautilus (Ubuntu Natty)
Assignee: Canonical Desktop Experience Team (canonical-dx-team) = Ted
Gould (ted)
** Changed in:
Thanks for investigating the issue at the code level. Actually, the
latest set of fixes we're landing should fix the problem hopefully in
the following hours.
Keeping the bug open for now.
--
Paste in global application menu is not active whilst using gnome-terminal
@ted: assigning to you, but that should be fixed by your recent changes
in a few hours.
** Changed in: indicator-appmenu
Importance: Undecided = Low
** Changed in: indicator-appmenu
Status: New = Confirmed
** Changed in: indicator-appmenu
Milestone: None = ubuntu-10.10
** Changed
It's not a trivial change to determine when to ignore the config key at
runtime: there are many modules involved afaict: the window managers,
the gconf configuration repository, the control-center when it's
running.
** Changed in: gnome-control-center (Ubuntu)
Importance: Undecided = Wishlist
Cody: can you investigate this issue? see if it's related to appmenu-
gtk. Thanks
** Also affects: ayatana-ubuntu
Importance: Undecided
Status: New
** Changed in: ayatana-ubuntu
Milestone: None = ubuntu-10.10
** Changed in: ayatana-ubuntu
Assignee: (unassigned) = Cody Russell
@John: we're providing the indicator-datetime module for netbooks
instead, not as featureful as the gnome-clock, but we hope better
integrated with the panel, thanks to the app. indicator system.
--
If too many timezone are configured, lower ones are cut off the screen with no
way to see them
** Changed in: ayatana-ubuntu
Milestone: ubuntu-10.10-beta = ubuntu-10.10
** Changed in: gnome-settings-daemon (Ubuntu)
Milestone: ubuntu-10.10-beta = ubuntu-10.10
--
please drop icon from keyboard indicator
https://bugs.launchpad.net/bugs/620331
You received this bug notification
** Changed in: appmenu-gtk
Milestone: ubuntu-10.10-beta = None
--
wxbanker Segmentation Fault on start with appmenu gtk
https://bugs.launchpad.net/bugs/617385
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk+2.0 in ubuntu.
--
** Also affects: libindicate
Importance: Undecided
Status: New
** Changed in: libindicate
Importance: Undecided = High
** Changed in: libindicate
Assignee: (unassigned) = Ted Gould (ted)
** Changed in: libindicate
Milestone: None = ubuntu-10.10
--
rhythmbox crashed with
** Changed in: ayatana-ubuntu
Milestone: maverick-alpha-3 = None
--
emacs fails to start: X protocol error
https://bugs.launchpad.net/bugs/585196
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk+2.0 in ubuntu.
--
desktop-bugs
** Also affects: ayatana-ubuntu
Importance: Undecided
Status: New
--
evolution crashed with SIGSEGV in g_object_set()
https://bugs.launchpad.net/bugs/609390
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk+2.0 in ubuntu.
--
It's not nice to crash evolution.
** Changed in: ayatana-ubuntu
Importance: Undecided = Medium
** Changed in: ayatana-ubuntu
Status: New = Triaged
** Changed in: ayatana-ubuntu
Milestone: None = ubuntu-10.10-beta
** Changed in: ayatana-ubuntu
Assignee: (unassigned) = Cody
Proposing to add a gconf key (at least) to be able to hide the indicator
even if multiple layouts are installed/registered. That should bring us
closer to mpt's design
https://wiki.ubuntu.com/KeyboardMenu#5.%20User%20switches%20the%20keyboard%20menu%20on%20or%20off
And in a second step (if time
Public bug reported:
Binary package hint: gnome-power-manager
The status information displayed in the g-p-m indicator menu is
generally too long.
Mpt proposed a better set of strings to display the status information
for batteries: https://wiki.ubuntu.com/BatteryStatusMenu#Items
** Affects:
** Changed in: gnome-power-manager (Ubuntu)
Assignee: David Barth (dbarth) = (unassigned)
--
notifications for battery are too long
https://bugs.launchpad.net/bugs/332569
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power
I think this is solved now that we've moved to using the new panel
indicators.
** Changed in: gnome-power-manager (Ubuntu)
Status: New = Fix Released
--
Battery state notification bubbles - duplicated functionality
https://bugs.launchpad.net/bugs/475332
You received this bug notification
Hmm, actually not. The functionality duplication may still be present.
Only the auto-hide issue is gone.
** Changed in: gnome-power-manager (Ubuntu)
Status: Fix Released = New
** Changed in: gnome-power-manager (Ubuntu)
Status: New = Opinion
** Changed in: gnome-power-manager
** Changed in: gnome-screensaver (Ubuntu)
Importance: Undecided = Wishlist
** Changed in: gnome-screensaver (Ubuntu)
Status: New = Opinion
--
Locked screensaver and gdm switch user are conceptually the same
https://bugs.launchpad.net/bugs/605349
You received this bug notification
** Changed in: gtk+2.0 (Ubuntu Maverick)
Status: New = Triaged
** Changed in: gtk+2.0 (Ubuntu Maverick)
Milestone: None = maverick-alpha-3
** Also affects: ayatana-ubuntu
Importance: Undecided
Status: New
** Changed in: ayatana-ubuntu
Importance: Undecided = Medium
**
From the description, it seems to be a bug in the about-me dialog, which is a
gnome-control-center applet.
Keeping it as a whishlist on the me menu, and adding gnome-control-center to
track the rest of the bug.
** Changed in: indicator-me (Ubuntu)
Importance: Undecided = Wishlist
** Changed
Is that still an issue? Can you detail a procedure to reproduce the
issue, with an without the me menu btw, this way we'll know if it's
related or not. Thanks
** Changed in: indicator-me (Ubuntu)
Importance: Undecided = Low
** Changed in: indicator-me (Ubuntu)
Status: New = Incomplete
** Package changed: gnome-bluetooth (Ubuntu) = gtk+2.0 (Ubuntu)
--
bluetooth devices menu item not working in bluetooth indicator
https://bugs.launchpad.net/bugs/558841
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk+2.0 in ubuntu.
** Changed in: ayatana-ubuntu
Status: Triaged = In Progress
** Changed in: gtk+2.0 (Ubuntu Lucid)
Status: Triaged = In Progress
--
menu mouse-scrolling broken, when themes enable gtk-auto-mnemonics
https://bugs.launchpad.net/bugs/548652
You received this bug notification because
** Also affects: ayatana-ubuntu
Importance: Undecided
Status: New
** Changed in: ayatana-ubuntu
Importance: Undecided = Medium
** Changed in: ayatana-ubuntu
Status: New = Triaged
** Changed in: ayatana-ubuntu
Milestone: None = ubuntu-10.04-beta-2
** Changed in:
** Changed in: ayatana-ubuntu
Milestone: ubuntu-10.04-beta-2 = ubuntu-10.04
--
menu mouse-scrolling broken, when themes enable gtk-auto-mnemonics
https://bugs.launchpad.net/bugs/548652
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
** Changed in: notify-osd
Milestone: ubuntu-10.04-beta-2 = ubuntu-10.04
--
Rhythmbox Notification Bubble shows wrong cover art
https://bugs.launchpad.net/bugs/451086
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs
** Changed in: notify-osd
Importance: Undecided = High
** Changed in: notify-osd
Status: New = In Progress
** Changed in: notify-osd
Assignee: (unassigned) = Mirco Müller (macslow)
** Changed in: notify-osd
Milestone: None = ubuntu-10.04-beta-2
** Changed in: gtk+2.0 (Ubuntu
** Changed in: ayatana-ubuntu
Assignee: Kalle Valo (kvalo) = Cody Russell (bratsche)
** Changed in: gnome-panel (Ubuntu Lucid)
Assignee: Kalle Valo (kvalo) = Cody Russell (bratsche)
--
gnome-panel crashed with SIGSEGV in gtk_widget_show()
https://bugs.launchpad.net/bugs/448084
You
** Also affects: notify-osd
Importance: Undecided
Status: New
--
Unable to click items below notifications
https://bugs.launchpad.net/bugs/546650
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk+2.0 in ubuntu.
--
** Also affects: ayatana-ubuntu
Importance: Undecided
Status: New
** Changed in: ayatana-ubuntu
Importance: Undecided = High
** Changed in: ayatana-ubuntu
Status: New = In Progress
** Changed in: ayatana-ubuntu
Milestone: None = ubuntu-10.04-beta-2
** Changed in:
** Changed in: gnome-settings-daemon (Ubuntu)
Milestone: jaunty-updates = later
--
New osd-notify notifications should not have an empty title
https://bugs.launchpad.net/bugs/334292
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
This looks like the 22 pixel issue.
** Also affects: ayatana-ubuntu
Importance: Undecided
Status: New
** Changed in: ayatana-ubuntu
Importance: Undecided = Medium
** Changed in: ayatana-ubuntu
Milestone: None = ubuntu-10.04-beta-2
** Changed in: ayatana-ubuntu
Assignee:
** Changed in: gnome-panel (Ubuntu Lucid)
Assignee: Canonical Desktop Experience Team (canonical-dx-team) = Ted
Gould (ted)
--
gnome-panel crashed with SIGSEGV in gtk_widget_show()
https://bugs.launchpad.net/bugs/448084
You received this bug notification because you are a member of Ubuntu
Linking to the upstream project to get it under the end of cycle radar.
The distinction between HW support PK policy should help find a
solution.
** Also affects: indicator-session
Importance: Undecided
Status: New
** Changed in: indicator-session
Importance: Undecided = Medium
**
** Changed in: gnome-media (Ubuntu)
Importance: Wishlist = Medium
** Changed in: gnome-media (Ubuntu)
Milestone: None = lucid-alpha-3
** Changed in: gnome-media (Ubuntu)
Assignee: Canonical Desktop Experience Team (canonical-dx-team) = Conor
Curran (cjcurran)
** Changed in:
Marking gksu as affected, being the main blocker for the integration of
that in lucid. Cody is investigating the issue and preparing a fix for
that one in priority.
** Also affects: gksu (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gksu (Ubuntu)
Importance: Undecided =
Cody tracking that for the DX team.
** Also affects: ayatana-ubuntu
Importance: Undecided
Status: New
** Changed in: ayatana-ubuntu
Status: New = In Progress
** Changed in: ayatana-ubuntu
Importance: Undecided = Low
** Changed in: ayatana-ubuntu
Importance: Low = Medium
I don't see why it's related to the session menu. gnome-session is
managing that part, and I don't think the way we're managing session
shutdown calls can help resolve that issue. Intrinsically, the menu
shouldn't have to care about that.
** Changed in: indicator-session
Status: New =
It feels like the timed login patch may have triggered that issue.
** Also affects: gdm (Ubuntu)
Importance: Undecided
Status: New
** Changed in: xsplash (Ubuntu)
Status: New = Invalid
--
GDM: When auto timed login enabled, it doesnt allow to login immediately by
just
1 - 100 of 155 matches
Mail list logo
