Public bug reported:
A system that's been extremely good and stable has all of a sudden
become completely unusable after running Software Update.
After the last update, my system won't load firefox properly half of the
time. After loading pages like youtube it crashes the tab or just
crashes the
I decided to do a memory test by booting Ubuntu with the shift-key held
down and selecting memtest and surprisingly there's some bad memory
around the end of the 32GB (there's 4x8GB sticks installed). Booting
with the kernel parameter mem=24000M seems to get the system back to
stability.
I guess
Hello, this happens also in ubuntu 18.04.
May 26 09:59:20 shadow kernel: [ 60.880888] nouveau :01:00.0: timeout
May 26 09:59:20 shadow kernel: [ 60.880933] WARNING: CPU: 7 PID: 81 at
/build/linux-hwe-B83fOS/linux-hwe-4.18.0/drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmgf100.c:207
gf100_vmm
Thank you for taking your time to report the bug.
Please in the future use: ubuntu-bug affectedpackage so relevant system info
and logs
are collected to the bug report and the developers can debug more easy.
You can still use apport-collect BUGID in this stage.
** Changed in: firefox (Ubuntu)
HI just an update Gnome-todo seems to be syncing both ways again.
When adding a task to Gnome-todo it will sync straight away to Google tasks.
When adding a task in Google tasks, for it to show up in Gnome-todo I ether
have to close it for around ten minutes and reopen or reboot the computer for
6.2.4 released to Eoan.
** Changed in: libreoffice (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1826468
Title:
[upstream] Libreo
6.2.4 released to Eoan.
** Changed in: libreoffice (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1828811
Title:
[Upstream] Applyi
6.2.4 released to Eoan.
** Changed in: libreoffice (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1826052
Title:
[upstream] LibreO
Public bug reported:
When exporting a document that contains both a Table of Contents and a
Table of Figures to PDF Writer does not correctly hyperlink whichever
table comes second.
Version: 6.2.3.2 (not present in 6.0.7.3 shipped with 18.04)
Severity: Normal.
Reproducible: Always
Steps to rep
Just tested this with the snap and this bug does not appear present, so
may have already been fixed upstream.
Version: 6.2.4.2.0+
Build ID: libreoffice-6.2.4.2-snap1
CPU threads: 4; OS: Linux 5.0; UI render: default; VCL: gtk3;
Locale: en-AU (en_AU.UTF-8); UI-Language: en-US
Calc: threaded
--
Y
This bug was fixed in the package poppler - 0.76.1-0ubuntu3
---
poppler (0.76.1-0ubuntu3) eoan; urgency=medium
* d/p/glyphless-font.patch: Support Tesseract's glyphless font (LP:
#1830473)
-- Julian Andres Klode Sat, 25 May 2019 12:31:14
+0200
** Changed in: poppler (Ubuntu)
The breeze icons are calmer, and they are clearer in a few cases: for
example, New (where elementary squanders đŸ—‹ recognisability in
redundantly conveying what kind of file will be created), Cut (where
elementary’s puffy scissors look to me like a rabbit using binoculars),
and, though it pains me to
Still a bug in 19.04. Accidentally triggered the screen reader,
absolutely no way to kill it in an obvious manner. I had to google for
what the screen reader is on Ubuntu to start with. No icons, no
warnings, nothing at all. In the end got rid of it by killing and
permanently removing it. Good ridd
Both breeze and colibre would be a great improvement over the elementary icons,
in terms of consistency.
If colibre fits you more due to it's colors, I would also +1 this decision, to
get rid of those eOS 3d icons, that really don't fit at all to the Yaru
symbolic icon set.
--
You received th
Using totem 3.32 and GNOME Nautilus 3.32.1.
If you select multiple video files in nautilus and select "Open with
Movie Player" only the last one will be played. In the previous version
of Totem, all of them were played, one after the other.
--
You received this bug notification because you are a
Public bug reported:
rhythmbox loses daap connection everytime the host (of rhythmbox) has to
renew his dhcp lease. The daap server has a static IP.
Here is the corresponding part of journalctl:
Mai 26 22:06:05 myhostname systemd-networkd[4173]: enp5s0: DHCP lease lost
Mai 26 22:06:05 myhostname
** Also affects: rhythmbox (Ubuntu)
Importance: Undecided
Status: New
** Changed in: rhythmbox-plugin-alternative-toolbar (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to rhythmbox in Ubunt
...because?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to rhythmbox in Ubuntu.
https://bugs.launchpad.net/bugs/1830551
Title:
rhythmbox loses daap connection everytime when dhcp lease expires
Status in rhythmbox package in Ubuntu:
Launchpad has imported 26 comments from the remote bug at
https://bugzilla.gnome.org/show_bug.cgi?id=758772.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help
When it will be released to public users?
I am running ubuntu 19.04 , still not got the latest fix release.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ibus-libpinyin in Ubuntu.
https://bugs.launchpad.net/bugs/1829947
Title:
bug wh
It will take a couple of weeks. First a member of the SRU team will
accept it to be built in disco-proposed, and then we need to test and
confirm again. Since both Sebastien and I have difficulties to really
understand how it makes a difference, I hope you can assist in the
process by installing fr
Link fixed. Sorry, the new Launchpad bug tracker for Gnome Shell was
broken and inserted bad links for a while.
** Bug watch added: bugzilla.gnome.org/ #762193
https://bugzilla.gnome.org/show_bug.cgi?id=762193
** Changed in: gnome-shell
Importance: Critical => Unknown
** Changed in: gnome-
Can someone experiencing this bug please report it to the PulseAudio
developers?
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/new
and then tell us the new bug ID.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio
*** This bug is a duplicate of bug 1769383 ***
https://bugs.launchpad.net/bugs/1769383
This bug is closed (via bug 1769383).
If you have any ongoing problems then please open a new bug by running:
ubuntu-bug gnome-shell-extension-ubuntu-dock
--
You received this bug notification because
This bug is closed.
If you have any problems then please open a new bug by running:
ubuntu-bug gnome-shell
--
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/1793595
Title:
[radeo
This bug might be getting confused...
Doug: You are reporting problems with the radeon graphics driver, and
VMware.
Gunnar: You are reporting different problems with the nouveau graphics
driver.
hugh: Please answer comment #20. Your feedback is most needed here.
--
You received this bug notifi
This is a bug in CUPS ultimately, it's driving Avahi using the D-BUS API
(as opposed to manual service files in /etc/avahi/services, this is only
really used for a sysadmin to manually add services, most other types of
advertisements such as printers are expected to use the API to advertise
it).
M
You have been subscribed to a public bug:
I've just upgraded to 18.10 from 18.04. Now when power manager (or
whoever) puts the screen to blank, I cannot login, because I do not see
anything. Befeore the upgrade, mouse move or keypress led to login
screen. Now does not.
Workaround:
When I go to te
Please try to take a video of the problem and attach it here. A video is
important because it tells us what type of "flickering" we are dealing
with.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because
@Daniel,
Sure I will provide the log tomorrow
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to webkit2gtk in Ubuntu.
https://bugs.launchpad.net/bugs/1804786
Title:
Garbage occurred when Playing the video in the Ubuntu Desktop Guide
St
Please:
1. Reproduce the problem again.
2. Use your workaround to recover. Do not reboot.
3. Run this command:
journalctl -b0 > journal.txt
4. Send us the file 'journal.txt'.
** Tags added: nouveau
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Summary changed:
- Do not see log
** Package changed: xorg (Ubuntu) => 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/1830489
Title:
I don't Know
Status in Ubuntu:
Incomplete
Bug description:
When the OP Unb
** Package changed: mutter (Ubuntu) => budgie-desktop (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1830482
Title:
budgie-wm overclock when plaing video, nvidia 390, profile
** Summary changed:
- [MS-7C02, Realtek ALC892, Red Line Out, Rear] No sound at all
+ [MSI B450 TOMAHAWK (MS-7C02), Realtek ALC892, Red Line Out, Rear] No sound at
all
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubunt
*** This bug is a duplicate of bug 1600053 ***
https://bugs.launchpad.net/bugs/1600053
Also, this sounds like bug 1600053 so let's group it there for now.
** This bug has been marked a duplicate of bug 1600053
system scaling factor ignored for page rendering
--
You received this bug noti
*** This bug is a duplicate of bug 1600053 ***
https://bugs.launchpad.net/bugs/1600053
Each graphics toolkit needs to fix this themselves. Unfortunately for
Firefox I think it uses its own so it must be fixed separately.
** Package changed: gdm3 (Ubuntu) => gnome-shell (Ubuntu)
** Summary ch
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: firefox (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1600
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.04 (vivid) reached end-of-life on February 4, 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.
Launchpad has imported 15 comments from the remote bug at
https://bugzilla.gnome.org/show_bug.cgi?id=762193.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help
** Summary changed:
- Display scaling problems when resizing windows
+ Window scaling factor changes erratically on a single display
** Package changed: gdm3 (Ubuntu) => mutter (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mu
** Changed in: totem (Ubuntu)
Assignee: Ubuntu Desktop Bugs (desktop-bugs) => (unassigned)
** Changed in: totem (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to totem in Ubuntu.
https:/
I was now able to try a few different versions leading to the following results:
* The bug does not affect kernel version 4.18.0-15 (Tested using a Live install
of 18.04.2)
* The bug does not affect kernel version 4.20.17-042017 (Tested on my install
of 19.04 with a manually installed kernel)
* T
Thank you for reporting this bug to Ubuntu.
Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015.
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. Bu
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.04 (vivid) reached end-of-life on February 4, 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.
Thank you for reporting this bug to Ubuntu.
Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015.
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. Bu
Thank you for reporting this bug to Ubuntu.
Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015.
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. Bu
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.04 (vivid) reached end-of-life on February 4, 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.
It sounds like you made a typo there. The points you list suggest the
regression started between kernels 5.0.1 and 5.1.5:
* The bug does not affect kernel version 5.0.1-050001 (Tested on my install of
19.04 with a manually installed kernel)
* The bug does affect newly build kernel version 5.1.5-0
Thank you for reporting this bug to Ubuntu.
Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015.
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. Bu
Thank you for reporting this bug to Ubuntu.
Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015.
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. Bu
Thank you for reporting this bug to Ubuntu.
Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015.
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. Bu
Thank you for reporting this bug to Ubuntu.
Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015.
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. Bu
Thank you for reporting this bug to Ubuntu.
Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015.
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. Bu
Thank you for reporting this bug to Ubuntu.
Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015.
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. Bu
Thank you for reporting this bug to Ubuntu.
Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015.
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. Bu
Thank you for reporting this bug to Ubuntu.
Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014.
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 13.10 (saucy) reached end-of-life on July 17, 2014.
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 13.10 (saucy) reached end-of-life on July 17, 2014.
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 13.10 (saucy) reached end-of-life on July 17, 2014.
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 13.10 (saucy) reached end-of-life on July 17, 2014.
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 13.10 (saucy) reached end-of-life on July 17, 2014.
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 13.10 (saucy) reached end-of-life on July 17, 2014.
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 13.10 (saucy) reached end-of-life on July 17, 2014.
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 13.10 (saucy) reached end-of-life on July 17, 2014.
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 13.10 (saucy) reached end-of-life on July 17, 2014.
Ubuntu 12.10 (quantal) reached end-of-life on May 16, 2014.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old an
[Expired for chromium-browser (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: chromium-browser (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubu
[Expired for chromium-browser (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: chromium-browser (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubu
[Expired for chromium-browser (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: chromium-browser (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubu
Please install this dkms, reboot and redo the test.
If the headset-mic still doesn't work, please enable dump_coeff and
generate an alsa-info.txt.
thanks.
** Attachment added: "oem-audio-hda-daily-dkms_0.1_all.deb"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1821269/+attachme
Indeed my conclusion was wrong because I mixed up the versions. The bug
does affect some newer versions although it seems that it was solved in
the meantime before reappearing again.
To correct, I observed the following:
* The bug does NOT affect kernel version 4.18.0-15 (Tested using a Live inst
Thanks. That is very helpful.
** Summary changed:
- [HP Laptop 14-ma0xxx] No sound after suspend
+ [HP Laptop 14-ma0xxx] No sound after suspend (kernels 5.0.0 and 5.1.5 faulty,
but not 5.0.1)
** Package changed: pulseaudio (Ubuntu) => linux (Ubuntu)
--
You received this bug notification becau
@Daniel:
The bug is about failures to view the gnome-getting-started-docs videos
via yelp. We (at least I) have learned that the videos can't be viewed
properly with certain combinations of graphics cards and drivers.
So besides nailing which hardware/driver combination the bug reporter is
using
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => ajay rahul (ajayrahulapiswi)
--
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/1681513
Title:
Ubuntu 17.04/
73 matches
Mail list logo
