[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]
** Changed in: nautilus (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
[Expired for libinput (Ubuntu) because there has been no activity for 60
days.]
** Changed in: libinput (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libinput in Ubuntu.
shut down windos and rebooted Ubuntu.
No Sound
As SU ran echo 1 > parameters/dump_coef
Speaker sound works for about 10 seconds.
The following is the report from alsa-info
!!
!!ALSA Information Script v 0.4.64
!!
!!Script ran
After the sound quit I ran Alsa-info and got the following:
!!
!!ALSA Information Script v 0.4.64
!!
!!Script ran on: Tue May 21 03:48:17 UTC 2019
!!Linux Distribution
!!--
Ubuntu 19.04 \n \l DISTRIB_ID=Ubuntu
** Changed in: gnome-shell (Ubuntu)
Importance: Low => Wishlist
--
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/1829651
Title:
Caps Lock indicator on screen
Status in
In theory, adding model=auto (comment #3) doesn't affect your sound
driver since even without model=auto, the audio driver doesn't apply any
fixup models to your machine.
Please do a test:
cd /sys/module/snd_hda_codec
sudo su
echo 1 > parameters/dump_coef
Then test your speaker, when the
Update: The patches have been merged to drm-tip:
https://cgit.freedesktop.org/drm-
tip/commit/?id=1a74fc0b3f49a0603f230b6f087da33bda3d7c66.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
Please be sure to only report one problem per bug. We will make this bug
about the first problem you report only.
** Summary changed:
- misc. problems
+ problem with login to user account. Keeps going back to login window
--
You received this bug notification because you are a member of
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell
Yes those messages themselves are safe, but I think they may suggest the
kernel got stuck for a while (somewhere, anywhere). And that would
correlate with this bug.
If there were any other kernel log messages around that time then please
paste them here.
--
You received this bug notification
Thanks, but we will need more data points. We need to know at least one
kernel version which does not have the bug (if a version exists). And
then we need to know the earliest version where the bug was introduced.
--
You received this bug notification because you are a member of Desktop
I can't see any reason for the dock going permanently missing in that
log. It might be a good idea if anyone experiencing this problem opens a
new bug with all the required attachments, by running:
ubuntu-bug gnome-shell
which will do it automatically.
--
You received this bug notification
Someone probably needs to find a relevant upstream Xorg bug link to see
where/if it is being discussed there.
This is not the place where Xorg developers discuss such things.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server
** Tags added: disco eoan
--
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/1702151
Title:
gnome-shell crashed with SIGSEGV in
g_type_check_instance_is_fundamentally_a() from
Another reboot from Ubuntu back to Ubuntu and the Headset is still
silent, BUT now the speaker sound works. Connecting and disconnecting
the headset now has no effect on speaker sound except to mute when the
headset is plugged in. I apologize for scattershot troubleshooting.
--
You received
Correction. The sound through the speakers only lasts for about 10
seconds. When I plug the headset in there still no sound in the
headset, but when I unplug the headset the sound through the speakers
resumes but then quits after about 10 seconds.
--
You received this bug notification because
In accordance with this: https://docs.slackware.com/howtos:hardware
:audio_and_snd-hda-intel#how_to_find_the_right_options
I ran this: sudo echo "options snd-hda-intel model=auto" >
/etc/modprobe.d/snd-hda-intel.conf and rebooted.
That resulted in both the speakers and headphones working. But
Public bug reported:
Don't have details about the issue!
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
Public bug reported:
a) problem with login to user account. Keeps going back to login window
b) screen freeze after suspension. amdgup needs update
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
Uname: Linux
Same here in Ubuntu 18.04.
Monitor manager and other gnome extensions are disappearing from the top panel.
Alt-F2 r, like other said, helps to get them back. Extensions are still running
though when the bug appears.
I noticed this behavior some time ago, maybe 3-4 months ago, after an
upgrade
Hello, it looked like you had some problems connecting to wifi -- and
perhaps other hardware problems as well. I hope this helps:
[ 2164.414923] wlp1s0: deauthenticating from 26:0d:65:1e:76:1d by local choice
(Reason: 3=DEAUTH_LEAVING)
[ 2164.541523] wlp1s0: authenticate with 5c:99:60:97:1a:d0
[
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
** Changed in: mesa
Status: Unknown => New
--
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/1753677
Title:
es2gears_wayland on mutter sticks to 119 FPS on a 59.95Hz display
** Changed in: evince
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1829785
Title:
Evince: ∞ not found
Status in Evince:
Fix Released
Status
** Changed in: gcc-4.8 (Ubuntu)
Status: Incomplete => Invalid
--
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/1322784
Title:
Firefox crashes in flag_qsort during spellchecker
Bug report refers to the bbc plug-in which no longer exists
Closing as report is no longer valid
** Changed in: totem (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to totem in Ubuntu.
In comment 28, the freeze happened just before taking the log, yet the
last log entry was from ~1 minute earlier, so it doesn't look like there
were any relevant log entries.
However just now I had a freeze, and there are some messages in dmesg:
[10980.231902] perf: interrupt took too long (2512
It's committed in the disco packaging repository, but not uploaded. I
planned on bundling that change with other changes in an SRU.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
Sebastien, though the Russians the same symbol in mathematics for the
infinity, the infinity symbol ∞ itself is not Cyrillic. Have you tested
their solution, whatever it may be, simply to make sure that that's the
same issue?
--
You received this bug notification because you are a member of
OK, I've attached the requested info from my system. It goes back 4
days, so it should include the period when it stopped working.
Unfortunately I can't tell you exactly when that was - having the dock
autohide means it's pretty much hidden until I need it.
** Attachment added:
also on 18.04.02 LTS, also other people mentioned in comments
https://askubuntu.com/questions/114429/default-save-directory-for-gnome-
screenshot
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-screenshot in Ubuntu.
@Sebastien Bacher, another screenshot of "Volume mute" attached. Caps
Lock indicator also should be "on screen" looks like other indicators.
not on top bar or anywhere else. for example when Caps Lock is on bright
white A logo in the box, and when Caps Lock is off gray crossed A looks
like the
Hi. i am expecting a Caps Lock indicator by default (without need of
usage any 3rd party app which are not working proper tested few) like
the screenshot of Volume indicator as an example i attached. thanks.
** Attachment added: "example - Volume indicator on screen"
Could you add your journalctl log to the bug?
3.32.1 is also in disco-proposed so it would be good to also test if the
problem exist there/is really with gnome-shell
** Changed in: gnome-shell (Ubuntu)
Importance: Undecided => Low
** Changed in: gnome-shell (Ubuntu)
Status: New =>
The issue has been reported upstream in
https://gitlab.gnome.org/GNOME/evince/issues/1116
** Bug watch added: gitlab.gnome.org/GNOME/evince/issues #1116
https://gitlab.gnome.org/GNOME/evince/issues/1116
** Changed in: evince (Ubuntu)
Status: New => Triaged
** Also affects: evince via
Could you give details on what sort of indicator you expect? One in the
top panel? One in password/text widgets?
** Changed in: gnome-shell (Ubuntu)
Importance: Undecided => Low
** Changed in: gnome-shell (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification
This bug was fixed in the package cups-filters - 1.23.0-1
---
cups-filters (1.23.0-1) experimental; urgency=medium
* New upstream version 1.23.0
- cups-browsed: When removing a local queue on shutdown or
when DNS-SD reports the printer as disappeared check whether
it expired because no-one added the info requested in comment #18
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Closing then, it would be interesting to know if that can be trigger
again with some config (and which one) or if that was some sort of
corruption
** Changed in: ibus-libpinyin (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
** Changed in: network-manager (Ubuntu)
Importance: Undecided => High
--
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/1829566
Title:
network-manager 1.10.14-0ubuntu2
** Description changed:
+ [Impact]
+
+ ibus-libpinyin has proved to crash far too often. One or more files in
+ ~/.cache/ibus/libpinyin get corrupted somehow, and emptying that
+ directory allows the user to keep using ibus-libpinyin.
+
+ In disco (and eoan) ibus-libpinyin 1.11.0 and libpinyin
** Changed in: evince (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1829785
Title:
Evince: ∞ not found
Status in evince package in Ubuntu:
Looks like that the new version of network-manager is not working
correctly with the systemd-resolved of Bionic.
** Tags added: regression-update
** Also affects: network-manager (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a
I'm on 19.04 and I seem to be able to reproduce this at least once a day
while I leave my screen locked overnight.
Am willing to provide logs and core dumps if possible.
Just let me know how/what you need to capture.
Each morning when I log back in, the screen will sit and freeze for a
minute
Public bug reported:
Package: evince
Version: 3.32.0-1ubuntu0.1
OS: Disco 19.04
How to reproduce:
1) Open the attached document in Evince
2) Select the infinity symbol ∞ (U+221E) and copy it into clipboard
3) Press Ctrl+F and paste the symbol from the clipboard into the search field
4) Observe
Is there any update on this?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1823516
Title:
Nvidia driver installed but X apps are using software rendering
(LLVMpipe) in Wayland
It also affects kernel version 5.0.0-16 (installed from disco-proposed)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1829621
Title:
[HP Laptop 14-ma0xxx] No sound after suspend
I attach an example of a document that takes 20 secs to load, followed
by a cp/paste into a new document that loads very quickly.
** Attachment added: "LoadingSlowly_onewordonly.odt"
** Attachment added: "CpPasted_Now loading FAST_LoadingSlowly_onewordonly_.odt"
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1826757/+attachment/5265118/+files/CpPasted_Now%20loading%20FAST_LoadingSlowly_onewordonly_.odt
--
You received this bug notification because you are a
No crash has been recorded for 3.32.1-2ubuntu1 and SRU'ed version for
this, so marking as verified
** Tags removed: verification-needed verification-needed-disco
** Tags added: verification-done verification-done-disco
--
You received this bug notification because you are a member of Desktop
I have a similar setup and am experiencing the same thing since the
update. Thanks for narrowing it down to network-manager!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
No crash has been recorded by e.u.c in versions mayor than
3.32.1-2ubuntu1, so marking as verified.
** Tags removed: verification-needed verification-needed-disco
** Tags added: verification-done verification-done-disco
--
You received this bug notification because you are a member of Desktop
I can get the dock back with alt-f2-r to restart the gnome shell, so I
have a workaround for now. But this is obviously an issue.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
@vanvugt Thank you for your answer.
I tried the kernel versions 5.0.0-13 and 4.3.0-04 as well. For the first one,
the same problem occured (sound only after a fresh boot) and the second one
couldn't be installed correctly because of missing libraries (a boot was
possible, but e.g. the mouse
This bug hasn't been addressed and is obviously still an issue. Why was
it allowed to expire?
I have a relatively clean 18.04 install, and it's happening to me too.
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Status: Expired => Confirmed
--
You received this bug
*** This bug is a duplicate of bug 977228 ***
https://bugs.launchpad.net/bugs/977228
more people confirm in comments/solutions
https://askubuntu.com/questions/114429/default-save-directory-for-gnome-
screenshot
--
You received this bug notification because you are a member of Desktop
Will test om thursday
Den mån 20 maj 2019 16:30Łukasz Zemczak <1821...@bugs.launchpad.net>
skrev:
> Hello Per-Inge, or anyone else affected,
>
> Accepted nautilus into disco-proposed. The package will build now and be
> available at
>
`sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf.bckp`
`sudo apt install nvidia-driver-` (check in GUI "Additional Drivers",
mine is `430`)
everything works. Even the screen layout wasn't broken.
Thx to Dmitrii!
--
You received this bug notification because you are a member of Desktop
Packages,
Dell Precision 5520 freeze cuz of Nvidia confirmed.
`sudo apt purge 'nvidia*'` solved it. Let's see what happens after I install it
again.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
I think I am using ibus-libpinyin 1.11.0-1 when I first report this
issue. However, after removing the ibus cache as in my comment #6, I
haven't seen the crash since then. I guess we can close this issue.
Thanks.
--
You received this bug notification because you are a member of Desktop
Packages,
I like the helpful info you supply to your articles. I’ll bookmark your blog
and take a look at once more here frequently. I am somewhat sure I will be told
plenty of new stuff right right here! Good luck for the following!
https://www.writecdr.com/ipenz-ka02-new-zealand-skilled-migration/
I like the helpful info you supply to your articles. I’ll bookmark your blog
and take a look at once more here frequently. I am somewhat sure I will be told
plenty of new stuff right right here! Good luck for the following!
https://www.writecdr.com/ipenz-ka02-new-zealand-skilled-migration/
As I stated in the Chinese Ubuntu forum, I almost always stick to only the
LTS versions of Ubuntu. I made an exception wrt 18.04 LTS and moved up to
19.04 and even 19.10 because ibus-libpinyin 1.11 is not available in
18.04. However, 19.04 and 19.10 have their own problems and are not
Actually, I don't see an upload for bionic for fixing this bug. The task
was already set to 'Fix Committed' - where is the bionic fix committed?
Is it in the current bionic gnome-software already?
--
You received this bug notification because you are a member of Desktop
Packages, which is
Ok, so I have some trouble with the SRUs addressing this bug. Per SRU
policy [1], we in generall only should only aim for fixing 'high-impact
bugs'. This bug seems to be marked with an importance of Low, which
normally isn't per-se good SRU material (if it was bundled with some
other,
[1] https://wiki.ubuntu.com/StableReleaseUpdates#When
** Tags added: verification-needed verification-needed-disco
--
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/1735071
Title:
Hello Scott, or anyone else affected,
Accepted gnome-software into disco-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
software/3.30.6-2ubuntu4.19.04.1 in a few hours, and then in the
-proposed repository.
Please help us by testing this new
Hello Sebastien, or anyone else affected,
Accepted nautilus into disco-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/nautilus/1:3.32.1-0ubuntu0.19.04.0
in a few hours, and then in the -proposed repository.
Please help us by testing this new
Hello Per-Inge, or anyone else affected,
Accepted nautilus into disco-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/nautilus/1:3.32.1-0ubuntu0.19.04.0
in a few hours, and then in the -proposed repository.
Please help us by testing this new package.
I have hesitated about upgrading, since the problem seems to have been
present also with version 1.10 according to the crash reports.
However, in Ubuntu 19.04 ibus-libpinyin was upgraded to 1.11, and it
looks like there is a significant reduction of crashes in 19.04 compared
to 18.04 and 18.10.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-shell (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
The way I understand Mustafa's report this is about the general lack of
a caps lock state indicator on (so primarily post-login, in gnome-
shell). Bug #1734887 rather discusses the lack of an indicator pre-login
(gdm), so is a different issue.
** This bug is no longer a duplicate of bug 1734887
Thanks for your report!
ibus-libpinyin on Ubuntu 19.04 was updated to version 1.11 on
2019-02-06. Have you possibly noticed an improvement since then?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ibus-libpinyin in Ubuntu.
** Information type changed from Private to Public
--
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/1822403
Title:
ibus-engine-libpinyin assert failure: ibus-engine-libpinyin:
Public bug reported:
Summary:
If you insert video in Impress slideshow and the video is bigger than slide or
is partially out of slide, the libreoffice UI or "slideshow" breaks. See the
video [1]
This bug is related to "libreoffice-gtk3" and "gstreamer1.0-gtk3". The bug does
not accrue if
i am currently using Lenovo ThinkPad x230 which doesnt have physical
caps lock indicator on keyboard like some other ThinkPad laptops. i
noticed that on Ubuntu 18.04.2 there is no Caps Lock indicator on
screen. it would be perfect if you put it default as other on screen
indicators such as volume
** Changed in: nautilus
Status: Unknown => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1826586
Title:
Unable to drag Nautilus tab to new window
Status in Nautilus:
** Package changed: texinfo (Ubuntu) => apt (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to texinfo in Ubuntu.
https://bugs.launchpad.net/bugs/1829735
Title:
Fresh install of 18.10 stuck at initializing ramdisk after sudo apt
Upstream bug was closed "VERIFIED FIXED" on 2015-04-06
No further comments re bug here or upstream for over four years, closing as
fixed.
** Changed in: firefox (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages,
Public bug reported:
**Specs**
- Asus Zenbook 14 UX433FN (NVMe PCIe SSD)
- Ubuntu 18.10 and Windows 10 dual boot, Windows 10 working fine.
**Background**
After successful FRESH install of Ubuntu 18.10 desktop using LiveUSB, and
subsequent update using either command prompt (sudo apt upgrade) or
Could anyone who still has this problem supply a list of the routes he
has entered and how he has entered them and also attach the
/etc/NetworkManager/system-connections file to this bug report? Thanks.
** Changed in: network-manager (Ubuntu)
Status: Confirmed => Incomplete
--
You
Michael Gale, your issue is different to the OP's one. The routes the OP
has entered are all CIDR notable, he even uses CIDR when entering them
via command line.
So please report a new bug, showing which routes you have entered and
how they end up in /etc/NetworkManager/system-connections.
In
There is some activity upstream on the 1.14 branches, so there might be a
1.14.5, but I'm not sure:
https://gitlab.freedesktop.org/gstreamer/gst-plugins-base/merge_requests/223
https://gitlab.freedesktop.org/gstreamer/gst-plugins-good/merge_requests/198
Should this SRU wait for a 1.14.5 release?
I like the helpful info you supply to your articles. I’ll bookmark your blog
and take a look at once more here frequently. I am somewhat sure I will be told
plenty of new stuff right right here! Good luck for the following!
https://www.writecdr.com/ipenz-ka02-new-zealand-skilled-migration/
Public bug reported:
Hi,
We have a cups server (ubuntu) that centralize all our network printers.
Each desktop users on Ubuntu (16.04, 18.04) are looking in that print
server to retrieve those printers. It works fine but...
# /etc/cups/cups-browsed.conf in a desktop user
...
Upstream marked it as duplicate of
https://gitlab.gnome.org/GNOME/nautilus/issues/615
** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #615
https://gitlab.gnome.org/GNOME/nautilus/issues/615
** Changed in: nautilus
Status: Fix Released => Unknown
** Changed in: nautilus
** Changed in: nautilus
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1826586
Title:
Unable to drag Nautilus tab to new window
Status in
** Changed in: upower (Ubuntu)
Status: New => Fix Released
** Changed in: gnome-shell (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to upower in Ubuntu.
** Tags added: rls-ee-incoming
--
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/1829699
Title:
Switches are gone from the VPN menu
Status in gnome-shell package in Ubuntu:
New
I guess this is a new bug in gnome-shell 3.32.1, if it didn't exist in
3.32.0...?
--
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/1829699
Title:
Switches are gone from the VPN
fixed in 19.4 update
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1823134
Title:
Cannot change display brightness [HP ZBook 17 G5 with Nvidia Quadro
P1000 Mobile]
Status in
Thanks. That's good news.
If (while using supported graphics packages and not a PPA) you find the
problem returns, like with lots of desktop icons, then please reopen
this bug by changing the status back to New.
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Invalid
--
You
*** This bug is a duplicate of bug 1822026 ***
https://bugs.launchpad.net/bugs/1822026
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 1822026, so it is being marked as such. Please
** Also affects: libreoffice (Ubuntu Bionic)
Importance: Undecided
Status: New
--
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/1798074
Title:
LIbreoffice crashes on
Public bug reported:
password character is typed after about 1s when key is pressed and mouse
stops for about one sec when hovering over buttons (including user
profile button) sometimes instead ubuntu logo is text ubuntu which fixes
itself after while.
ProblemType: Bug
DistroRelease: Ubuntu
** Changed in: mutter (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
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/1763892
Title:
144Hz/120Hz monitor but mutter seems to
Greetings! I deleted everything from the desktop, I also deleted the
packages installed from oibaf-ppa and the problem no longer manifested
itself.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
The correct solution to the problem I've been facing was finally solved
on comment #58, thanks @prasanth-s-cmi. I've contacted the kernel
developer responsible for these patches introduced around Linux 4.16.1
on https://bugzilla.redhat.com/show_bug.cgi?id=1571330 , and he will
blacklist my laptop
1 - 100 of 101 matches
Mail list logo
