[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/b
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bu
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]
** Changed in: bluez (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/b
Upstream xfwm4 marked WONTFIX.
** Changed in: xfwm4 (Ubuntu)
Status: Confirmed => Won't Fix
--
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/1054923
Title:
Window raise
@queen8387: Thanks for reporting the bug.
This will be fixed in a few days. I am not sure if there is a workaround
for this.
For now, you can open rhythmbox, and import the songs and play it from
there, rather than from GNOME File manager.
--
You received this bug notification because you are a
Refer https://gitlab.gnome.org/GNOME/glib/-/issues/1298 as well
** Bug watch added: gitlab.gnome.org/GNOME/rhythmbox/-/issues #1884
https://gitlab.gnome.org/GNOME/rhythmbox/-/issues/1884
** Also affects: rhythmbox via
https://gitlab.gnome.org/GNOME/rhythmbox/-/issues/1884
Importance: Unk
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: rhythmbox (Ubuntu)
Status: New => Confirmed
--
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/
I have also experienced this issue on my Ubuntu 20.04 Installation, and
the only method to resolve is to restart the computer. The method stated
by dmitry does not work for me.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in U
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: fonts-noto (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fonts-noto in Ubuntu.
https://bugs.launchpad.net/bug
Is this still Bug #1820859 ?
--
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/1922290
Title:
nautilus crashed with SIGSEGV in update_dbus_opened_locations()
Status in nautilus package
For verification I downloaded ubuntu-21.04-beta-desktop-amd64.iso
(Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1)) started it in
VirtualBox ("Try Ubuntu") and also experience a crash for the "nautilus
--version" command, see attachment.
** Attachment added: "Screenshot showing the crash"
Is there somewhere or somehow I can test your modified version of
Kubuntu by downloading it and attempting an install Rik?
--
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/1920665
Title:
U
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Bug reporting is mostly about finding & fixing problems thus preventing
future users from hitting the same bug.
I suspect a Support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. You can
Public bug reported:
A few days ago I installed PyCharm Professional to my computer. I had
some issues configuring my interpreter so I looked for help on the
internet. I ran a few commands and changed some sort of root file and
now my terminal won't run any commands at all. I tried fixing it mysel
To test the slight possibility that builds with the current toolchain
might be at fault, I rebuilt mesa 20.03.4 against current
release+proposed pockets and downgraded mesa to the result.
Ubiquity/greeter does not crash with that combination.
--
You received this bug notification because you are
Public bug reported:
what can i do to have autologin?
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: lightdm 1.30.0-0ubuntu3.1
ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94
Uname: Linux 5.4.0-70-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5Check
Public bug reported:
When i try to boot normally, it's power off automatically.
It boots properly, when i boot using recovery boot
I cannot boot in recovery mode every time.
My display drivers doesn't give scroll bar for brightness setting.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xo
17 matches
Mail list logo
