Marking the ubiquity task as Invalid; let's switch it back if it turns
out there are some needed changes in ubiquity (as for wallpaper in
ubiquity-dm?)
** Changed in: ubiquity (Ubuntu Trusty)
Status: Confirmed = Invalid
** Changed in: ubiquity (Ubuntu)
Status: Incomplete = Invalid
No, it's not. I'm adding the Trusty task now.
** Also affects: systemd (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
be, if there was a backup, to import it explicitly from
evolution's Import option.
** Changed in: evolution (Ubuntu)
Assignee: Mathieu Trudel-Lapierre (mathieu-tl) = (unassigned)
** Changed in: evolution (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member
Did we not fix this already? I mentioned a session issue, but it seems
like this would have been fixed separately from whatever the mount
points might be.
** Changed in: mtp (Ubuntu)
Assignee: Mathieu Trudel-Lapierre (mathieu-tl) = (unassigned)
--
You received this bug notification because
)
Importance: Undecided = Medium
** Changed in: network-manager (Ubuntu)
Assignee: Mathieu Trudel-Lapierre (mathieu-tl) = (unassigned)
** Changed in: network-manager (Ubuntu Quantal)
Assignee: Mathieu Trudel-Lapierre (mathieu-tl) = (unassigned)
** Summary changed:
- network-manager does
Reassigning to the correct package. Use as Hotspot isn't something that
comes from NM; the underlying APIs do seem to work properly.
** Package changed: network-manager-applet (Ubuntu) = gnome-control-
center (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
to assign it to yourself and start up the dicussion again to
see if we can enable connectivity checking. This may be useful for
Ubuntu Touch as well.
** Changed in: network-manager (Ubuntu)
Assignee: Mathieu Trudel-Lapierre (mathieu-tl) = (unassigned)
** Changed in: network-manager (Ubuntu
No, I don't think it's an issue anymore -- so I'll remove the bug
assignment.
Jelmer, you filed the bug initially, do you still see such issues?
** Changed in: evolution (Ubuntu)
Assignee: Mathieu Trudel-Lapierre (mathieu-tl) = (unassigned)
** Changed in: evolution (Ubuntu)
Status
It seems like this would possibly be a good candidate for SRU; but this
requires that the bug be also fixed in the development release. Given
that there's already a tag for utopic and reports that it doesn't work
there, I suspect it also doesn't work yet in Vivid.
Alistair, maybe you'd be
The page should actually display a spinner for a second to show that it
changes from Not discoverable to Discoverable as you reach that page.
Could you try again to make sure whether you see that at the beginning
when the page is just opened? Otherwise we may need to increase the
timer.
**
** Changed in: urfkill (Ubuntu)
Status: Invalid = Triaged
** Changed in: urfkill (Ubuntu)
Importance: Critical = Wishlist
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to indicator-bluetooth in Ubuntu.
I can only reproduce this on Ubuntu if I use the old nautilus window
still pointing to the files; rather than the newly-opened window from
re-connecting the USB cable. This makes it not an issue in mtp; and it's
unclear whether this is actually fixable in nautilus/gvfs itself.
I'm marking this as
** Also affects: gnome-control-center (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: unity-control-center (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
I uploaded the fixes for both gnome-bluetooth and bluez to trusty;
pending review by the SRU team.
** Description changed:
+ [Impact]
+
+ * Fixes issues connecting bluetooth devices using SSP (Simple Secure
+ Pairing); which does include many newer bluetooth devices, especially
+ keyboards.
+
Uploaded the updated fix to Trusty; pending review.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-bluetooth in Ubuntu.
https://bugs.launchpad.net/bugs/1312349
Title:
Microsoft bluetooth mobile keyboard 6000 cannot be used
So I can see what was uploaded to trusty isn't the same code as what I
sponsored to utopic; let's remove that package and reupload the same fix
that got into utopic.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-bluetooth in
Anthony, your patch is still proposed for trusty, could you test it and
tell us whether things are working properly now, and in which releases?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-bluetooth in Ubuntu.
This isn't a NetworkManager bug; reassigning to gnome-control-center
/unity-control-center.
Looks like (at quick glance, without digging into the code) the switch
is triggering the wrong thing in NM, rather than disabling wired it's
doing something else.
** Package changed: network-manager
: Undecided = Medium
** Changed in: gnome-bluetooth (Ubuntu Trusty)
Importance: Undecided = High
** Changed in: gnome-bluetooth (Ubuntu Trusty)
Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)
** Changed in: bluez (Ubuntu Trusty)
Assignee: (unassigned) = Mathieu Trudel
** Project changed: gnome-control-center = gnome-control-center
(Ubuntu)
** Changed in: gnome-control-center (Ubuntu)
Importance: Undecided = High
** Changed in: gnome-control-center (Ubuntu)
Status: New = Triaged
** Changed in: unity-control-center (Ubuntu)
Status: New = In
** Changed in: unity-control-center (Ubuntu)
Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1354987
I believe this has been fixed in the latest gnome-bluetooth upload in
utopic.
It would be nice if you could test with a liveCD of the development
release to see if it works for you.
Thanks!
** Changed in: gnome-bluetooth (Ubuntu)
Status: New = Fix Released
** Changed in: gnome-bluetooth
This appears to me as an indicator bug, or related to rfkill switches,
reassigning...
** Package changed: gnome-bluetooth (Ubuntu) = indicator-bluetooth
(Ubuntu)
** Also affects: rfkill (Ubuntu)
Importance: Undecided
Status: New
** Changed in: rfkill (Ubuntu)
Status: New =
** Changed in: gnome-bluetooth (Ubuntu)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-bluetooth in Ubuntu.
https://bugs.launchpad.net/bugs/1237355
Title:
Logitech Ultrathin Touch Mouse
** Changed in: gnome-bluetooth (Ubuntu)
Status: Confirmed = Triaged
** Changed in: gnome-bluetooth (Ubuntu)
Importance: Undecided = High
** Changed in: gnome-bluetooth (Ubuntu)
Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)
--
You received this bug notification
** Changed in: rfkill (Ubuntu)
Status: New = Triaged
** Changed in: rfkill (Ubuntu)
Importance: Undecided = Medium
** Changed in: urfkill (Ubuntu)
Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)
** Changed in: rfkill (Ubuntu)
Assignee: (unassigned) = Mathieu Trudel
This bug seems to have been corrected in the development release. Here,
I can definitely see a pointer speed option. Could anyone please verify
using a liveCD, to make sure this has been properly fixed?
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Desktop
** Changed in: gnome-bluetooth (Ubuntu)
Status: Confirmed = In Progress
** Changed in: gnome-bluetooth (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-bluetooth in Ubuntu.
** Also affects: empathy (Ubuntu Saucy)
Importance: Undecided
Status: New
** Also affects: account-plugins (Ubuntu Saucy)
Importance: Undecided
Status: New
** Also affects: friends-app (Ubuntu Saucy)
Importance: Undecided
Status: New
** Changed in: empathy (Ubuntu
NetworkManager seems to have been restarted quite fast after the resume
from suspend, but this really looks like the issue we've had with the
systemd logind proxy for the PrepareSleep method.
Reassigning to systemd.
** Package changed: network-manager (Ubuntu) = systemd (Ubuntu)
--
You
Triaged/High since this is pretty obviously in part caused by an issue
with the metadata about the device that we export over MTP.
There also needs to be a task for shotwell..
** Also affects: shotwell (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification
I've been testing this, it seems like the issue might be due to the
session handling in the mtp daemon.
--
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/1283871
Title:
Default
: Undecided = Medium
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/991481
Title
No, it actually means there is nothing to fix I just have missed the
updates to the bug.
It's invalid according to GNOME because there is a way to change the system
hostname via System Information in the control panel:
http://www.hadess.net/2011/06/pretty-oh-so-pretty.html
As expressed above,
Well, it's expected that when that network connection gets removed,
g-c-c starts properly - it will try to parse existing connections and
then list networks in range.
I'll go ahead and upload the fix I have, I'm reasonably confident it
fixes the issue.
--
You received this bug notification
** Bug watch added: GNOME Bug Tracker #712749
https://bugzilla.gnome.org/show_bug.cgi?id=712749
** Also affects: gnome-control-center via
https://bugzilla.gnome.org/show_bug.cgi?id=712749
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
** Also affects: gnome-control-center (Ubuntu Saucy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1198315
Title:
** Changed in: gnome-control-center (Ubuntu Saucy)
Importance: Undecided = Medium
** Changed in: gnome-control-center (Ubuntu Saucy)
Status: New = In Progress
** Changed in: gnome-control-center (Ubuntu Saucy)
Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)
--
You
I uploaded a patch that seems to work for me (when trying with a local
ad-hoc network setup with the same characters for testing).
It's in my PPA; it would be nice if someone else could confirm that it
helps:
ppa:mathieu-tl/sru-staging
(https://launchpad.net/~mathieu-tl/+archive/sru-
I've used two monitors for a long while now, and never got this problem.
Could someone please describe the steps to reproduce the issue so that
someone can work on a fix acceptable upstream, and so that we can know
how to verify the issue since it will have to be shipped as SRU?
Thanks!
--
You
This isn't Fix Committed though, since it's not in the Ubuntu queue or
anything -- resetting to Triaged .
** Changed in: eog (Ubuntu)
Status: Fix Committed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to eog in
** Also affects: eog (Ubuntu Raring)
Importance: Undecided
Status: New
** Changed in: eog (Ubuntu Raring)
Status: New = Triaged
** Changed in: eog (Ubuntu Raring)
Importance: Undecided = Low
--
You received this bug notification because you are a member of Ubuntu
Desktop
Reassigning to gnome-control-center; this isn't an issue in
NetworkManager itself (seeing as we don't have any such Airplane mode
per se, which is something only in the control panel Network pane).
** Package changed: network-manager (Ubuntu) = gnome-control-center
(Ubuntu)
--
You received this
It's just the way things are done for the shutdown procedure.
As I mentioned above, you shouldn't need to run restart networking (in
fact, it probably needs to be renamed to something else to avoid
confusion), using ifdown and ifup to bring up and down network
interfaces directly will do the
gnome-settings-daemon indeed crashes in that case, which breaks a load
of things, including the desktop manager in general.
The reason for this is that when you restart the networking job, it
kills off the system dbus bus, which brings down quite a lot of stuff
with it.
** Package changed:
If you're looking to restart network-manager, you'll want to do 'sudo
restart network-manager', not 'sudo restart networking'.
If you're making changes to /etc/network/interfaces, running ifup -a
will usually suffice to apply the changes. (or you can ifdown
interface, then ifup interface.
--
Public bug reported:
[IMPACT]
Users of evolution on 12.10 are subjected to a number of bugs that were fixed
in recent micro-releases of Evolution and Evolution-Data-Server; both are under
a micro-release exception for SRU.
[Test cases]
Smoke-testing of Evolution-data-server using evolution;
This is already uploaded to Raring.
** Description changed:
+ [IMPACT]
+ Users of evolution on 12.10 are subjected to a number of bugs that were fixed
in recent micro-releases of Evolution and Evolution-Data-Server; both are under
a micro-release exception for SRU.
+
+ [Test cases]
+
Public bug reported:
[IMPACT]
Users of evolution on 12.10 are subjected to a number of bugs that were fixed
in recent micro-releases of Evolution and Evolution-Data-Server; both are under
a micro-release exception for SRU.
[Test cases]
Smoke-testing of Evolution; verify that the application
Sorry, but this isn't fixed in Raring yet -- setting back to fix
committed. It only gets fixed in 3.6.3; we'll upload 3.6.4 to raring
shortly.
** Changed in: evolution-data-server (Ubuntu)
Status: Fix Released = Fix Committed
--
You received this bug notification because you are a member
Where did you see this error? Could you please attach a screenshot of
the issue?
Sounds to me like it's probably a simple case of not being connected, or
the service being temporarily unavailable...
** Changed in: evolution (Ubuntu)
Status: New = Incomplete
** Changed in: evolution
What this needs is basically a workaround to keep the non-multiarch path
for pango available through the installation, although it's definitely
not needed at any point after the system is upgraded and rebooted.
Perhaps just providing that symlink which we can remove in later
upgrades of pango1.0.
No need to report this again on the gnome lists; this is already fixed
in evolution/e-d-s 3.6.2.
We'll ship 3.6.2 as a SRU shortly.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution in Ubuntu.
: evolution-data-server (Ubuntu)
Importance: Medium
Assignee: Mathieu Trudel-Lapierre (mathieu-tl)
Status: In Progress
** Changed in: evolution-data-server (Ubuntu)
Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)
** Changed in: evolution-data-server (Ubuntu
** Description changed:
Update evolution-data-server to 3.6.2 to get latest fixes from upstream,
including the evolution fix for the signatures being doubled (bug
1055497), e-d-s 3.6.2 is required for evolution 3.6.2.
There is a micro-release exception for GNOME that encompasses
. (Matthew Barnes)
[Test Case]
- Run evolution; add calendars with some future events existing,
- Verify that the events appear in indicator-datetime.
[Regression Potential]
** Affects: evolution (Ubuntu)
Importance: Medium
Assignee: Mathieu Trudel-Lapierre (mathieu-tl)
Status
No, we can't really say it's a duplicate yet -- this bug is missing a
backtrace for the crash.
Till, would you be able to reproduce the crasher (given that it's likely
tied to that particular device you used not reporting a bluetooth name),
and attach/paste a backtrace?
** Changed in:
Thank you for taking the time to report this issue and helping to make
Ubuntu better. We noticed that some of the sentences in this bug report
are not in English. If they were translated to English they would be
more understandable to triagers. Could you please translate them?
Additionally, I'm
Doesn't seem to be the same issue though; if operations stay in
cancelling but the rest of the UI is usable, whereas the original
reporter seems to indicate that none of the UI is responsive.
What is happening at the time? Are you doing specific actions in
Evolution when the freeze happens, or
Please update to the latest evolution-data-server packages, which should
have made it to the archive yesterday, it should fix the issue.
(https://launchpad.net/ubuntu/+source/evolution-data-
server/3.6.0-0ubuntu3)
If it's not the case, don't hesitate to set this bug back to New.
** Package
The branch is submitted against Precise, yet this is nominated to
Quantal. Was there a mistake? It doesn't seem to apply to quantal, the
UI is very different.
At the very least I'll target this to precise; but please follow
http://wiki.ubuntu.com/StableReleaseUpdates#Procedure to add the
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue that you reported is one that should be
reproducible with the live environment of the Desktop CD of the
development release - Quantal Quetzal. It would help us greatly if you
could test with it so we can
Jakob, please file a separate bug for your issue, this one has been
closed for a long while, and it definitely not the same problem.
** Changed in: evolution (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
** Changed in: evolution (Ubuntu)
Status: Confirmed = Triaged
** Changed in: evolution (Ubuntu)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution in Ubuntu.
The account addition will succeed if you uncheck the last two checkboxes
on the last screen -- those about adding a calendar and contacts to the
Google account.
I'm not sure exactly if it's a bug in Evo or in gnome-online-contacts,
but the issue is defined enough that we can move this to Triaged.
Set to High after all ;)
Is there anything showing up in ~/.xsession-errors, messages from
evolution that could explain the issue seen here?
Could you please attach the output of:
grep evolution ~/.xsession-errors
to this bug report?
Thanks!
--
You received this bug notification because you
Confirming, I can reproduce this easily. I'll look at fixing this up,
it's really annoying.
** Changed in: evolution (Ubuntu)
Status: New = Confirmed
** Changed in: evolution (Ubuntu)
Importance: Undecided = High
** Changed in: evolution (Ubuntu)
Assignee: (unassigned) = Mathieu
I'm not sure what to make of this; all indicates there was a crash deep
inside Glib, that's not really something directly affecting
modemmanager, so I've reassigned this to the 'glib2.0' source package.
Are you still able to reproduce this crash? There has been changes to
glib since this bug was
Andre linked the following rationale for the current state of Evolution's
webkit integration:
https://mail.gnome.org/archives/evolution-list/2012-September/msg00055.html
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution in
** Changed in: evolution (Ubuntu Quantal)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/1037669
Title:
gst-plugin-scanner and browser
Jeremy, mike: it doesn't. NetworkManager.conf is the new, correct name
for the file. If some application is expecting a different value (and
one would wonder why they go out to look for that file in the first
place); then it's that application that needs fixing.
If a part of the control center in
** Changed in: totem (Ubuntu Quantal)
Status: New = In Progress
** Changed in: totem (Ubuntu Quantal)
Importance: Undecided = Medium
** Changed in: totem (Ubuntu Quantal)
Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)
** Changed in: totem (Ubuntu Precise
** Changed in: evolution (Ubuntu Quantal)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/1037669
Title:
gst-plugin-scanner and browser
I looked quickly and couldn't figure out a way to fix this decently;
looks to me like the actual parsing in webkit is happening in a very
different part of the code than the bits that handle whether to show as
plain text or not, so fixing this (keeping in mind that plain-text stuff
is a module),
I can't make sense of why this would have crashed, looking at the new
code, or the EDS code as it was in 3.5.4. However I suspect there has
been changes in e-d-s' handling of imapx connections that would make
this not likely to happen again.
Please upgrade to the most recent version and let us
** Changed in: evolution (Ubuntu)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/1043862
Title:
gsettings-data-convert crashed with signal
/pango.modules 2
libpango1.0-common.postinst:rm -f /etc/pango/pango.modules
** Package changed: evolution (Ubuntu) = pango1.0 (Ubuntu)
** Changed in: pango1.0 (Ubuntu)
Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)
--
You received this bug notification because you are a member
So I misread this; libpango1.0-common.postinst was already removing
/etc/pango/pango.modules in Lucid; so it's a little more complicated an
issue than that.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pango1.0 in Ubuntu.
Plan is; I'm looking at this bug but it's still not obvious to me what
the source of the issue is. The end result is that some applications
will display broken text for a part of the upgrade procedure; but the
exact package causing this I'm not sure of yet.
We can certainly release note that such
I stepped through the entire upgrade process in a VM without reproducing
this bug. I wonder if it's somehow specific to running upgrades on
metal; that is, if compiz is running at the time?
The error message in question is indeed showing up from evolution-alarm-
notify (as per bug 965686); but
Revised release notes paragraph:
Users upgrading from previous releases may notice that newly started
applications during the upgrade procedure may display broken text, observable
as squares instead of the text meant to be displayed. This is observable as a
dialog that may popup during the
** Changed in: evolution (Ubuntu Precise)
Assignee: Ubuntu Desktop (ubuntu-desktop) = Mathieu Trudel-Lapierre
(mathieu-tl)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs
This would not be specific to 12.04.1; it would also have been present
in 12.04, it's just a little hard to reproduce -- needs just the right
environment to be noticeable.
Erick; mind confirming if at the time you see the dialog from Evolution,
you also see the same kind of behavior (boxes for
I can't seems to reproduce this when clicking around try to select text
over and over again in the chat scrolling window. Is there some detail
I'm missing to be able to reproduce this bug?
Looking at the stack trace, disassembly/registers and the gtk code for
that version, seems to me like the
There is no notification for this because you should be getting notified
of a connection being disconnected in that case. Regardless, the whole
concept of Airplane mode there (I'll assume it's in the control center),
need to be removed altogether. It has nothing to do with any kind of
airplane
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue that you reported is one that should be
reproducible with the live environment of the Desktop CD of the
development release - Quantal Quetzal. It would help us greatly if you
could test with it so we can
** Changed in: evolution (Ubuntu)
Assignee: Ubuntu Desktop Bugs (desktop-bugs) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/159546
Title:
Exists doesnt
This bug is a request for a new feature and has already been sent
upstream (see the link to the Gnome-bug 356551 at the top of the page).
It's up to upstream developers to implement the new feature, or to
someone interested to provide a patch for review and inclusion by the
developers.
I'm
Should it really be evolution to do this or postfix directly?
AFAIUI it makes more sense if it's done by postfix, if only to avoid
duplicating work in every application that might want to send mail...
and also because someone might want to manually send mail, and then
translating manually to an
** Changed in: evolution (Ubuntu)
Status: New = Triaged
** Changed in: evolution (Ubuntu)
Importance: Undecided = Wishlist
** Bug watch added: GNOME Bug Tracker #681616
https://bugzilla.gnome.org/show_bug.cgi?id=681616
** Also affects: evolution via
** Changed in: evolution (Ubuntu)
Status: Confirmed = In Progress
** Changed in: evolution (Ubuntu)
Importance: Undecided = Medium
** Changed in: evolution (Ubuntu)
Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)
--
You received this bug notification because you
This kind of error comes from the SMTP server used to send mail (either
as a direct connection to the remote mail server, or through the smart
host used).
What are your settings for Sending mail for your Evolution account? Are
you using a specific SMTP server, or are you using Sendmail? If you're
*** This bug is a duplicate of bug 1003884 ***
https://bugs.launchpad.net/bugs/1003884
Duplicate of bug 1003884; fixed in Quantal, and an update should be
available in precise-proposed shortly.
** This bug has been marked a duplicate of bug 1003884
Evolution freezes when you try to change
*** This bug is a duplicate of bug 1003884 ***
https://bugs.launchpad.net/bugs/1003884
Duplicate of bug 1003884; fixed in Quantal, and an update should be
available in precise-proposed shortly.
** This bug has been marked a duplicate of bug 1003884
Evolution freezes when you try to change
So this looks to me as though each change is applied separately, and
each with its own authentication: once for the system service, and
however many times for each gconf key that needs changing. There ought
to be a better way; I'll look at the code to see if I can figure it out.
** Changed in:
It's already using a global authentication mechanism similar to what
gksudo would do.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1018873
Title:
weird behavior
Uploaded the fix to precise-proposed, waiting for review by the SRU
team.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/950160
Title:
Unity blocks other programs
Status: New
** Changed in: gnome-control-center (Ubuntu Precise)
Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)
** Changed in: gnome-control-center (Ubuntu Precise)
Importance: Undecided = Low
** Changed in: gnome-control-center (Ubuntu Precise)
Status: New
** Description changed:
- For systems equipped with hot keys to adjust screen brightness, the
- brightness gauge in gnome-control-center screen is not responding to
- brightness hot-key actions.
+ [Impact]
+ Using brightness hotkeys currently changes brightness correctly, but such
changes fail
Fix Committed for Quantal: the patch is applied on the packaging branch
lp:~ubuntu-desktop/gnome-settings-daemon/ubuntu; pending upload once
compiz lands (since what is in the branch also changes gconf/gsettings
behavior and affects compiz)
** Also affects: compiz (Ubuntu Precise)
Importance:
101 - 200 of 721 matches
Mail list logo
