[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 Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
[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 Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
[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 Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
[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 Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
[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 Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
[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 Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
[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 Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
[Expired for gedit (Ubuntu) because there has been no activity for 60
days.]
** Changed in: gedit (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
[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 Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
[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 Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
[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 Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
[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 Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
[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 Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
[Expired for gnome-shell-extension-ubuntu-dock (Ubuntu) because there
has been no activity for 60 days.]
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
** Description changed:
To simplify reproduce steps, one only has to:
1. install (tested so far) Ubuntu Bionic
2. switch to other tty by pressing Ctrl+Alt+Fn
3. login and logout
Then it should try to switch back to GDM (no matter you have logged in GUI or
not), triggers vt-switch bug
I wanted to reconfigure an old PC to be a music server connected to our
HIFI. It took 3 days and 7 attempts to successfully install 18.04 due
to an issue with installing on PC with multiple drives. It refused to
correctly write the GRUB boot loader to the same partition it itself
installed
Please:
1. Remove all your extensions since extensions tend to cause most of the
bugs like this one...
b'org.gnome.shell' b'enabled-extensions' b"['ubuntu-
appindicat...@ubuntu.com', 'extensi...@abteil.org',
'hams...@projecthamster.wordpress.com', 'cont...@projecthamster.org',
*** This bug is a duplicate of bug 1818862 ***
https://bugs.launchpad.net/bugs/1818862
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 1818862, so it is being marked as such. Please
Please run:
apport-collect 1821426
to send us more information about the machine.
Please also try these potential workarounds and let us know which one(s)
work:
(a) Edit /etc/gdm3/custom.conf and uncomment the line:
#WaylandEnable=false
and reboot.
(b) Disable integrated
** Also affects: gnome-bluetooth (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gnome-bluetooth (Ubuntu)
Status: New => Confirmed
** Changed in: oem-priority
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
You have been subscribed to a public bug:
I'm uncertain which package is causing the problem, though I strongly
suspect it may be nvidia related.
This laptop runs 18.10 just fine, but attempting to boot 19.04 from a
USB disk (tried multiple USB boot disks) results in a blank screen after
Grub.
Public bug reported:
Without warning or apparent user action, my entire system froze aside
from the mouse cursor. I was able to switch to a VT to log in and
capture this bug report. After that, I had to `kill -9 gnome-shell`
after which it restarted properly and my session is now working fine
im suffering from this problem in 18.0.4
--
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 keyboard
To manage
Why has this SRU been pushed against the current 2.0 version of libnfs
in bionic and cosmic, when the Security Team has identified outstanding
concerns with 2.0 in the MIR bug (LP:# 1746598;
https://bugs.launchpad.net/ubuntu/+source/libnfs/+bug/1746598/comments/23)?
This does not look releasable
I have tested without gnome extensions and the same happens to me.
I've also tried the theory of ekimai by switching workspaces with mouse scroll
on right bottom corner, unfortunately with the same crash.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
Thanks for taking the time to report this bug.
Generally speaking snaps do not have dependencies as such, everything is
bundled inside the snap. Some snaps use platform snaps to provide some
core libs, but that's not relevant in this case. FWIW, I tested the
notepad++ snap from Taqi Raza and it
See LP: #1818862
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1821525
Title:
totem assert failure: totem: totem: gen9_mfd.c:649:
gen9_hcpd_get_reference_picture_frame_id:
You have been subscribed to a public bug:
Description:Ubuntu Disco Dingo (development branch)
Release:19.04 latest updates installed
To drag and drop a file to the Ubuntu/Gnome dock (favorites) is not working.
For example I tried to drag the file
** No longer affects: totem
** No longer affects: mesa
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1821525
Title:
totem assert failure: totem: totem: gen9_mfd.c:649:
** Package changed: ubuntu => gnome-shell-extension-ubuntu-dock (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock
in Ubuntu.
https://bugs.launchpad.net/bugs/1821585
Title:
Ubuntu/Gnome dock
** Changed in: mesa (Ubuntu)
Status: New => Invalid
** Description changed:
https://github.com/intel/intel-vaapi-driver/issues/451
- https://bugzilla.freedesktop.org/show_bug.cgi?id=110232
+ https://bugzilla.freedesktop.org/show_bug.cgi?id=110232 (No Mesa)
software-center does not provide snaps at all. This is either a problem
with the snap itself, or with gnome-software.
** Package changed: software-center (Ubuntu) => gnome-software (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
You have been subscribed to a public bug:
When testing some text editors I have stumbled over multiple problems,
after the software is installed.
The first test was with notepad++. After installing the snap nothing
worked. The program did not even start, nor provide some information
what is
This bug was fixed in the package nautilus - 1:3.26.4-0~ubuntu18.04.4
---
nautilus (1:3.26.4-0~ubuntu18.04.4) bionic; urgency=medium
* d/p/0015-tracker-search-engine-don-t-start-it-if-not-availabl.patch:
- update the patch to fix a logic error in the code which made tracker
Thank you for testing the package, I have promoted it to bionic-updates.
The cosmic counterpart still needs verification though. Could someone
test the 18.10 package so we could get it released as well?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
The verification of the Stable Release Update for nautilus 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
After adding the line "/usr/bin/xinit" to gdm3.service I get this in
every boot:
ProblemType: Crash
Architecture: amd64
Date: Mon Mar 25 19:17:11 2019
DistroRelease: Ubuntu 18.04
ExecutablePath: /usr/lib/xorg/Xorg
ExecutableTimestamp: 1543339632
ProcCmdline: /usr/lib/xorg/Xorg :0
...
Did you
Its look like the issue is on usage the connect/pair command.
When use a bluetoothctl 'connect' command, the connection is
established, with info:
[CHG] Device ServicesResolved: yes
[CHG] Device Paired: yes
Connection successful
but the [LinkKey] section is not stored in 'info' file.
When
Thanks.
Confirm, the tlp not installed.
Mouse: Acer MT1BF
One more thing, the use of bluetoothctl is not resolving issue.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-bluetooth in Ubuntu.
39 matches
Mail list logo
