Also, this is why I try suggesting really strongly to you guys not to
run -proposed during the development cycle because these kind of
removals happen.
(Maybe you just need to make sure you downgrade all the dconf binary
packages at the same time.)
--
You received this bug notification because
This bug was fixed in the package gnome-online-accounts -
3.27.92-1ubuntu3
---
gnome-online-accounts (3.27.92-1ubuntu3) bionic; urgency=medium
* debian/rules:
Make sure that gnome-online-accounts.pot is refreshed so the
strings from 0001-ubuntu-sso-provider.patch are
Thanks for your report.
Why kind of upgrade did you do that triggered this error ? a release
upgrade or a regular package upgrade?
** Changed in: gconf (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is
dino99, we can't easily just set the version higher since the
autopkgtest issue is triggered by 0.26.1 and higher versions.
http://autopkgtest.ubuntu.com/packages/n/notify-osd/bionic/armhf
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
When the bug task does not mention a specific ubuntu release, it means
"whatever is devel at the time". Now that means bionic, where it's fixed
and available, that's why the task was marked as fix released.
To have it fixed in Xenial and other stable releases, the procedure
outlined in
clamav explicitly mentions ifupdown in a debconf question regarding how
the user would like freshclam (updating the virus signatures db) to
work. One of the options is a ifupdown hook attached to what the user
calls "the internet interface". That option should be removed, or better
yet, migrated
Yeah but that tweak is quite dirty: try to downgrade from
0.26.1-3ubuntu2 to 0.26.0-2ubuntu3, and you are proposed to remove half
of the packages list.
Maybe set the proposed version higher than the previous proposed one to
bypass that issue.
--
You received this bug notification because you
The attachment "Translation update for Greek (file:
firefox/debian/firefox.desktop.in)" seems to be a patch. If it isn't,
please remove the "patch" flag from the attachment, remove the "patch"
tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the
team.
[This is an automated
*** This bug is a duplicate of bug 978120 ***
https://bugs.launchpad.net/bugs/978120
Hi Christian,
So, my impression, from what you've described is that this isn't the
same issue as the others in this bug (not least because the Postscript
error is different: "typecheck" rather than
How can I help this issue, I attached logs and would welcome running any
diag you might require.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-online-accounts in Ubuntu.
https://bugs.launchpad.net/bugs/1758930
Title:
No, that was "dconf" (rename) and that never migrated to bionic due to
armhf autopkgtest issues, I deleted that version to land that fix, the
update can be uploaded again if someone figures out the test issues
--
You received this bug notification because you are a member of Desktop
Packages,
This is what I have for
$ lsof | awk '{ print $1 }' | uniq -c | sort -rn | head
17808 dropbox
6042 dropbox
3504 JS\x20Hel
3024 JS\x20Hel
2628 DNS\x20Re
2456 JS\x20Hel
2056 JS\x20Hel
1856 JS\x20Hel
1752 mozStorag
1600 JS\x20Hel
--
You received this bug notification
Public bug reported:
Please apply the attached patch that updates the Greek translation
for the file "firefox/debian/firefox.desktop.in".
** Affects: firefox (Ubuntu)
Importance: Undecided
Status: New
** Tags: patch
** Patch added: "Translation update for Greek (file:
after nvidia-390 became nvidia-driver-390 I get back screen.
I have Acer vx5 laptop with nvidia 1050/Intel
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1752053
Title:
nvidia-390 fails
*** This bug is a duplicate of bug 1751324 ***
https://bugs.launchpad.net/bugs/1751324
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1751324, so is being marked as such.
This is happening in Ubuntu 18.04 updated as today, but always when
searching for updates from "Updates" tab, or installing a .deb package.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
*** This bug is a duplicate of bug 1751324 ***
https://bugs.launchpad.net/bugs/1751324
Public bug reported:
Remmina crashed while I tried to reconnect to my remote session after
locking my machine
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: remmina 1.2.0-rcgit.27+dfsg-4ubuntu1
Hi Daniel, the bug is now reported upstream here:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/166
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1759548
Title:
Fixed in 1.2.1~git20171128.5a854327+dfsg-0.1 which is in Bionic.
** Changed in: libimobiledevice (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libimobiledevice in Ubuntu.
*** This bug is a duplicate of bug 1748450 ***
https://bugs.launchpad.net/bugs/1748450
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1748450, so is being marked as such.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1676583
** Description changed:
Note that only the C library ("libsysmetrics1") and the command line
("ubuntu-report") packages are needed in main (we should also promote
"libsysmetrics-dev" package, even if not necessary). We don't need the
Go API "golang-github-ubuntu-ubuntu-report-dev" which
happens in every boot of the system, is very annoying.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/472450
Title:
gnome-keyring crashes for no apparent reason
Status in
Tell me how to get the information you need and I will gather it for
you.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/472450
Title:
gnome-keyring crashes for no apparent
** Tags added: artful zesty
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/1085706
Title:
pam_ecryptfs: seteuid error
Status in eCryptfs:
Confirmed
Status in GNOME
My bug is a duplicate, but I don't use Wayland.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1748450
Title:
gnome-shell crashed with SIGTRAP in _g_log_abort() from
*** This bug is a duplicate of bug 1748450 ***
https://bugs.launchpad.net/bugs/1748450
My bug is a duplicate, but I don't use Wayland.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
*** This bug is a duplicate of bug 1748450 ***
https://bugs.launchpad.net/bugs/1748450
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1748450, so is being marked as such.
*** This bug is a duplicate of bug 978120 ***
https://bugs.launchpad.net/bugs/978120
Hello everybody,
sorry for this late comment, this bug is really old and in this case or in many
cases all ready fixed (i hope).
In my case i have the same problem with a printer from HP manufacture. Why i
Debian builds:
akonadi-backend-postgresql_17.08.3-2_all.deb
akonadi-backend-postgresql_17.12.2-1_all.deb
Any reason why not to build this? The psql backend just works if you
configure it. And if you are already running postgresql you can
eliminate running a 2nd sql server.
--
You received this
Let's upload your fix for now so we unblock the translators
** Changed in: gnome-online-accounts (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-online-accounts in Ubuntu.
*** This bug is a duplicate of bug 1748450 ***
https://bugs.launchpad.net/bugs/1748450
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 1748450, so it is being marked as such. Please
** Changed in: d-conf (Ubuntu Bionic)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1735929
Title:
security problems with incorrect
d-conf (0.26.0-2ubuntu3) bionic; urgency=medium
* 0001-Don-t-create-the-user-config-dir-as-world-readable.patch:
- create the config dir with permissions 700 so it's not world readable
(lp: #1735929)
-- Sebastien Bacher Thu, 29 Mar 2018 11:01:28
+0200
uh !!
** Also affects: ubuntu-themes (Ubuntu)
Importance: Undecided
Status: New
** Also affects: dconf-editor (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-themes in
Public bug reported:
It crashed after login.
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
CurrentDesktop:
syslog
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/variety/+bug/1660568/+attachment/5094530/+files/syslog
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: network-manager (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
*** This bug is a duplicate of bug 1748450 ***
https://bugs.launchpad.net/bugs/1748450
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1748450, so is being marked as such.
** Changed in: udisks2 (Ubuntu Bionic)
Status: In Progress => Confirmed
** Changed in: udisks2 (Ubuntu Bionic)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
Could someone having the issue give the output from this command?
$ lsof | awk '{ print $1 }' | uniq -c | sort -rn | head
** Changed in: gnome-software (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is
Can't you read Vej?
People have to use "a workaround" which isn't explained anywhere in the
documentation if a backup gets corrupted. It isn't even obvious from the
error message that an earlier backup got corrupted.
--
You received this bug notification because you are a member of Desktop
** Tags added: rls-bb-incoming
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1577885
Title:
120sec delay during shutdown or reboot with still mounted cifs (via
Wifi)
William, I guess you set as incomplete for launchpad before the IRC
discussion? Seems the consensus was to try to backport the newest
gettext and make launchpad use it, Colin started poking at that it
seemed?
** Changed in: launchpad
Status: Incomplete => New
--
You received this bug
This bug was fixed in the package libxcb - 1.13-1
---
libxcb (1.13-1) unstable; urgency=medium
[ Julien Cristau ]
* Switch xcb.freedesktop.org URLs in packaging to https.
* Stop building -dbg packages, rely on automatic dbgsym packages instead.
[ Helmut Grohne ]
* Make
Sorry about that. You can correct your bug title by changing your bug
title to "eglnative" instead of "glnative".
But I suggest the best and only way forward here is for us to get a
crash file reported via the 'ubuntu-bug' command.
Please check that you have applied the workaround to bug 994921
Sorry for the delay :) Tell me if anything isn't as you expect!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1719462
Title:
[Translation] "Left" and "Right" must be
Upstream said it's a gnome-settings-daemon issue, see
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/6
** Changed in: gnome-control-center (Ubuntu)
Importance: Undecided => High
** Changed in: gnome-control-center (Ubuntu)
Status: Confirmed => Triaged
** Package changed:
Are you sure you're using a Wayland session? Xorg is still the default
in 18.04.
To check, try running 'xrandr' and tell us what the output is.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
when you have the issue can you try to start /usr/lib/gnome-settings-
daemon/gsd-media-keys manually? does it output any error? does it make
the keybindings work?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in
I mean Xorg is now the default in 18.04. It wasn't in 17.10.
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?
This will help us to find and resolve the problem.
** Information type changed from
** Package changed: gnome-session (Ubuntu) => gnome-shell (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1759760
Title:
Wayland: Out-of-memory results in unusable
Regarding the bug I filed with mutter, they sent me this, I am at a
loss:
"Jonas Ådahl commented:
First there is no such thing as "glnative" backend. Secondly, please
write proper bug reports. A very generic title and linking to an
external bug tracker is not enough."
--
You received this bug
mrt 28 19:58:45 hostname kernel: do_IRQ: 3.40 No irq handler for vector
Same as LP: #1752772?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1759644
Title:
[18.04]
** Package changed: network-manager (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1759644
Title:
[18.04] Regression: wired network does not work
The crash occurred in Mesa gallium code (so radeon or nouveau). However
the caller was mutter (gnome-shell) from its hybrid GPU logic, which is
only used in Wayland sessions.
I know that doesn't help users right now, but it's important information
for developers.
** Summary changed:
-
*** This bug is a duplicate of bug 1748450 ***
https://bugs.launchpad.net/bugs/1748450
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1748450, so is being marked as such.
*** This bug is a duplicate of bug 1706097 ***
https://bugs.launchpad.net/bugs/1706097
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1706097, so is being marked as such.
** Package changed: xorg (Ubuntu) => apparmor (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1759769
Title:
Failed to start AppArmor initialization.
Status in apparmor package
Why it is "fix released" while it's still affects Xenial? Xenial are LTS
and supported until 04-2021 and it should be fixed in Xenial. Every
other major distro has support for IDN for years. But for some reason
Ubuntu maintainers are ignoring this issue.
--
You received this bug notification
This crash seems to be limited to Ubuntu 12.10 and 13.04 (looking at the
duplicates and the linked upstream bug report). And that's no longer
supported.
Also the affected program is unmaintained for some years now.
** Changed in: pygobject (Ubuntu)
Status: Triaged => Fix Released
--
You
This info message about chrome_cryptauth_service.cc is strange, as this
is chromeOS-specific code…
Anyway, have you tried my second suggestion?
mv ~/.config/chromium ~/.config/chromium.bak
then launch chromium and let me know if that helped.
--
You received this bug notification because
(note that the above will start with a brand new profile)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1759590
Title:
Chromium-Browser Won't Sustain My Profile
Status in
Public bug reported:
ob for apparmor.service failed because the control process exited with error
code.
See "systemctl status apparmor.service" and "journalctl -xe" for details.
invoke-rc.d: initscript apparmor, action "restart" failed.
● apparmor.service - AppArmor initialization
Loaded:
Subscribers: While this is the bug that started the investigation into
gnome-shell smoothness, it's actually not the main issue.
For the full list of issues (AFAIK), please see this:
https://trello.com/c/Q6JYXPPs
--
You received this bug notification because you are a member of Desktop
** Information type changed from Private to Public
** Changed in: gnome-software (Ubuntu)
Importance: Medium => High
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1755064
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-calendar (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-calendar in Ubuntu.
*** This bug is a duplicate of bug 1755064 ***
https://bugs.launchpad.net/bugs/1755064
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1755064, so is being marked as such.
101 - 169 of 169 matches
Mail list logo