Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
This should be considered high priority and a security risk. After locking the
computer, it is still possible to launch applications without unlocking.
I cannot understand why it is taking so long to define the importance of this
bug.
--
You received this bug notification because you are a mem
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Do you still see a problem related to the one that you reported?
Please let us know if you do otherw
Piotr,
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. You reported this bug some
time ago and there have been many changes in Ubuntu since that time.
Your prob
yes on normal desktop very well work
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1802638
Title:
Solution was simple: reinstall evolution-ews which was uninstalled on upgrade.
Sorry for the noise.
--
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/1798771
Title:
Exchange account
after restart OS normal work all lock screens
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1802638
Title:
bug (windows + L)
To manage notifications about this bug go to:
ht
Yes, I have now tested the proposed fix on two separate fresh
installations of cosmic. One HP and one Lenovo laptop. In both cases
they show a weird multi-stop gradient after the fix is installed. Looks
like the colour goes up-down-up-down instead of just down.
** Changed in: gnome-shell (Ubuntu
Does that mean you can't reproduce the original bug now?
** Changed in: gnome-shell (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs
I've experienced possibly this bug intermittently since moving to
Manjaro Gnome with Gnome 3.30.2. In my case it's not all the extensions
that are reset, but two that I've set different to default: Places
status indicator and Topicons plus. Furthermore, rebooting usually puts
it right; it's the loc
Lockal,
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Do you still see a problem related to the one that you reported?
Please let us know if you
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Do you still see a problem related to the one that you reported?
Please let us know if you do otherw
Devyn,
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Do you still see a problem related to the one that you reported?
Please let us know if you d
https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/1 :)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1769383
Title:
Ubuntu dock/launcher is shown on the lock screen
T
18.10 has no such issue, I don't use 16.10 now.
--
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/1637420
Title:
closing gedit in 16.10 sometimes closes whole gnome-fallback session
To
> The best way to get it fixed is to be able to disable mod extensions,
which is something I'm working on, and you can follow it on
https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/2. This will
probably be for dingo.
The correct link is https://gitlab.gnome.org/GNOME/gnome-
shell/merge_re
Thanks for your reply. Will close as "Invalid" as bug report was not
confirmed by another user.
** Changed in: gedit (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
https:
Saiph,
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. You reported this bug some
time ago and there have been many changes in Ubuntu since that time.
Your prob
Craig,
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Do you still see a problem related to the one that you reported?
Please let us know if you d
Public bug reported:
* Impact
The update is a GNOME stable update
(https://wiki.ubuntu.com/StableReleaseUpdates/GNOME), it include only important
bugfixes, it would be good to get into the LTS
* Test case
Nothing specific, test that your photos are still listed, than you can import
new ones, v
Closing on the main serie since cosmic has 0.30 which is newer and
includes those changes/fixes too
** Description changed:
- The update include only important bugfixes, it would be good to get into
- the LTS
+ * Impact
+ The update is a GNOME stable update
(https://wiki.ubuntu.com/StableRelease
The issue is still present on 16.04.
It would have taken less for you to try and see that than it probably
took to post comment #2 and close the issue.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
https://bugs.laun
Thank you for looking at the bug for the first time 2 years and a half
after it was reported.
The issue is still present at least on 16.04.
--
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/bu
** Description changed:
+ * Impact
+ Sometimes when scrolling in a photo collection the view becomes white and
shotwell needs to be restarted
+
+ * Test case
+ No specific steps, but it seems that scrolling on a big collection sometime
trigger the issue. It seems more likely on a 4k display. Sc
> please add a comment here telling us which new version it is in and
change the bug status to Confirmed
You should update the text of that comment and remove the part that says
to change the status to confirmed, because the system doesn't allow me
to do that.
--
You received this bug notificati
Daniel, ok you consider the fix here as problematic. Do we believe it's worth
unvalidating the SRU over it though? We have enough difficulties landing
gnome-shell SRUs fixing at the moment and the touch event one included in the
same update is important to oem.
If the background change is not pe
No activity for over five years
Reporter no longer uses Ubuntu
Issue not confirmed bu another user
So closing by marking "Invalid"
** Changed in: gedit (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscrib
Thank you for reporting this bug to Ubuntu.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Upstream bug report closed "RESOLVED FIXED"
Acknowledged by reporter there
Closing by marking "Fix Released"
** Changed in: gedit (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ub
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1769383
Title:
Ubuntu dock/laun
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-calculator (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-calculator in Ubuntu.
https://bugs.la
Is there a manual way to have it come-up ? From comment #10 :
"Because of alien toolkits there is always a need to summon on demand."
Ido not have touch screen Ineed the keyboard because my space key does not work
asitshould.
Still a very annoying bug.
--
You received this bug notification becau
@Fernando: we don't support hybrid graphics without using a display
manager, as that would prevent gpu-manager from running at the right
time.
@Michael: I can only assume there was some failure somewhere when
setting the power state of the NVIDIA GPU (the dmesg output might help).
There are indeed
** Summary changed:
- nautilus crashed with SIGABRT in g_assertion_message()
+ nautilus crashed with SIGABRT in g_assertion_message() (g_hash_table_lookup
(directory->details->file_hash, name) == NULL)
** Summary changed:
- nautilus crashed with SIGABRT in g_assertion_message() (g_hash_table_lo
The upstream fix was included in 3.30.2 which is disco now
https://gitlab.gnome.org/GNOME/gnome-control-center/commit/b8e2fd92
** Changed in: gnome-control-center (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop
Upstream doesn't want to fix the obvious problem because they disagree
g-c-c should be used outside out of GNOME, unassigning/setting back to
triaged since we don't want to enter into arguing about that
** Changed in: gnome-control-center (Ubuntu)
Status: In Progress => Triaged
** Changed
"when a custom display mode (960x540) is active" has been added to
description but (as I mentioned before) it's not true for the Steam Way
To Go game.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launc
There is still no easy way to edit files that need root, example files in /etc/
in gedit.
Even as of gedit 3.30.1.
--
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/1516332
Title:
Add
I've already got apport configured to report everything (i.e., I've
already done the workaround suggested in bug 994921), and there is no
crash either in /var/crash or on https://errors.ubuntu.com. I don't
think a crash is what's happening here.
Additional data:
* If, after I've woken up my lapto
The verification of the Stable Release Update for evince has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a r
This bug was fixed in the package evince - 3.30.1-1ubuntu1.2
---
evince (3.30.1-1ubuntu1.2) cosmic; urgency=medium
* debian/apparmor-profile:
- fine-tune the apparmor profile to allow the previous access in addition
to the new accesses to fix LP: #1798091
evince (3.30.1-1
The verification of the Stable Release Update for glib2.0 has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
The verification of the Stable Release Update for glib2.0 has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
This bug was fixed in the package glib2.0 - 2.56.3-0ubuntu0.18.04.1
---
glib2.0 (2.56.3-0ubuntu0.18.04.1) bionic; urgency=medium
* New upstream release (LP: #1794544)
+ The documentation for G_GNUC_MALLOC has changed to be more restrictive
to avoid miscompilations; you sho
This bug was fixed in the package glib2.0 - 2.56.3-0ubuntu0.18.04.1
---
glib2.0 (2.56.3-0ubuntu0.18.04.1) bionic; urgency=medium
* New upstream release (LP: #1794544)
+ The documentation for G_GNUC_MALLOC has changed to be more restrictive
to avoid miscompilations; you sho
This bug was fixed in the package mutter - 3.30.1-4
---
mutter (3.30.1-4) unstable; urgency=medium
[ Andrea Azzarone ]
* d/p/x11-close-display-in-an-idle-function.patch:
- close the x11 display in an idle function. This fixes a crash when running
'gnome-shell --replace'.
I don't think this is the case... At least I didn't get this regression
in my vm.
Is it yours clean?
Aslo I don't see how this could happen, as per the pure diff.
Is your gdm3 altrnative setup properly?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
Public bug reported:
I decided to leave my laptop and came back a few minutes later, and I
noticed that the dash was visible from the lockscreen. Not good. Running
Ubuntu 18.10 as a fresh install. Was able to quit and open applications
from the dash. Uncertain if that's a security risk or not. Unc
Public bug reported:
Every time I restart the system, my Ubuntu One account that is was
connected to ubuntu Software keeps disconnected. This doesn't happen
with the Snap account, only with the Ubuntu One account.
Description:Ubuntu 18.10
Release:18.10
gnome-software:
Instalado: 3.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nautilus (Ubuntu)
Status: New => Confirmed
--
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
*** This bug is a duplicate of bug 1769383 ***
https://bugs.launchpad.net/bugs/1769383
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1769383, so it is being marked as such. Please look
*** This bug is a duplicate of bug 1797851 ***
https://bugs.launchpad.net/bugs/1797851
** This bug has been marked a duplicate of bug 1797851
/usr/bin/nautilus:11:g_type_check_instance_cast:NAUTILUS_SEARCH_PROVIDER:nautilus_search_engine_stop:stop_search:disconnect_model_handlers
--
You
*** This bug is a duplicate of bug 1797851 ***
https://bugs.launchpad.net/bugs/1797851
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
nautilus. This problem was most recently seen with package version
1:3.26.4-0ubuntu8, the problem page a
*** This bug is a duplicate of bug 1797851 ***
https://bugs.launchpad.net/bugs/1797851
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
nautilus. This problem was most recently seen with package version
1:3.26.4-0ubuntu8, the problem page a
*** This bug is a duplicate of bug 1797851 ***
https://bugs.launchpad.net/bugs/1797851
** This bug has been marked a duplicate of bug 1797851
/usr/bin/nautilus:11:g_type_check_instance_cast:NAUTILUS_SEARCH_PROVIDER:nautilus_search_engine_stop:stop_search:disconnect_model_handlers
--
You
I did a clean install of Cosmic and the bug is present as well for me
also.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1769383
Title:
Ubuntu dock/launcher is shown on the l
Land for dingo? What are the possibilities of a backport to both 18.04
and 18.10? Couldn't this be considered a security vulnerability? It can
theoretically be used to close someone else's work out without saving,
depending on the application.
--
You received this bug notification because you are
There is not yet a fix for this problem. Do you known any reliable way to
reproduce it?
Il giorno lun 12 nov 2018, 23:50 Mike L <1769...@bugs.launchpad.net> ha
scritto:
> Land for dingo? What are the possibilities of a backport to both 18.04
> and 18.10? Couldn't this be considered a security vul
Hmm, that's not quite right. The Xorg fix has landed, but the Wayland
fix has not. Both require changes to mutter.
** Changed in: mutter (Ubuntu)
Status: Fix Released => In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
It does make this bug worse. The original bug was barely noticeable, but
with that fix it's really a bright and obvious glitch.
What we could do is release the SRU but just keep this bug open.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscri
the mutter tested version is: 3.28.3-2~ubuntu18.04.2, which is the same
as in #14.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1730211
Title:
Unable to type capital letters using
Test pass on bionic:
1. on a laptop with a touch screen, touch the file manager icon on the
launcher. Saw two file manager is launched.
2. enable proposed channel
3. apt install gnome-shell, it upgrades to version 3.28.3-0ubuntu0.18.04.3
4. log out and log in.
5. touch file manager icon on the lau
OK. This sounds related to bug 1723025 or one of:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bugs?field.tag=multimonitor
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
** Tags added: multimonitor
** Package changed: gnome-shell (Ubuntu) => gdm3 (Ubuntu)
--
You recei
** Changed in: gnome-shell (Ubuntu)
Importance: Low => Medium
** Changed in: mutter (Ubuntu)
Importance: Low => Medium
** Tags removed: artful
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launc
OK, I wiped another laptop and installed 18.04.1 fresh with only the
above fix.
Verified bug fixed with no regressions, using 3.28.3-0ubuntu0.18.04.3.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1730211
Title:
Unable to type capital letters using onscreen key
OK, I wiped another laptop and installed 18.04.1 fresh with only the
above fix.
Verified bug fixed with no regressions, using 3.28.3-0ubuntu0.18.04.3.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this b
On cosmic, even without turn on the proposed channel, with gnome-shell
3.30.1-2ubuntu1, I can't reproduce this issue.
With the gnome-shell 3.30.1-2ubuntu1.18.10.1 from the proposed channel,
it still works fine.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs
[Expired for libzmf (Ubuntu) because there has been no activity for 60
days.]
** Changed in: libzmf (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to libzmf in Ubuntu.
https://bugs.launchpad
[Expired for libstaroffice (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: libstaroffice (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to libstaroffice in Ubuntu.
h
** Changed in: libstaroffice (Ubuntu)
Status: Expired => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to libstaroffice in Ubuntu.
https://bugs.launchpad.net/bugs/1717930
Title:
[MIR] libstaroffice
To manage notifi
** Changed in: libzmf (Ubuntu)
Status: Expired => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to libzmf in Ubuntu.
https://bugs.launchpad.net/bugs/1717926
Title:
[MIR] libzmf
To manage notifications about this bu
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nautilus (Ubuntu)
Status: New => Confirmed
--
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
I don't have the time to do a testround again, but I can give pointers
for whoever has time to have a look:
The patch is
https://git.launchpad.net/~ubuntu-desktop/ubuntu/+source/gnome-shell/commit/?id=ddc4f511abd64d69c1150a41475d0a1ebac01dbb,
in particular:
systemBackground = new Meta.Background
83 matches
Mail list logo
