** Tags removed: artful
** Tags added: bionic
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1723678
Title:
Some code accessed the property 'discreteGpuAvailable' on the
** Changed in: oem-priority
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1811668
Title:
oem-config fails on Nvidia GPU machine on 18.04.1
To
Interesting that errors.ubuntu.com is showing zero reports of this crash
in 19.04, and zero reports in the final release version of Xorg for
18.10 onward. But those same Xorg versions are crashing in 18.04. So I
would have to conclude that this was fixed in mutter in Ubuntu 18.10
onward.
** Also
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 Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-control-center (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
** Changed in: mutter
Status: New => Fix Released
--
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/1820331
Title:
gnome-shell crashed with SIGABRT. Assertion failure in
** Changed in: gnome-shell
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1772791
Title:
Lock/login screen displays password in clear text
https://gitlab.gnome.org/GNOME/gnome-shell/issues/460#note_331931 seems
to offer a pretty compelling explanation of why this might be seen
inadvertently.
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #460
https://gitlab.gnome.org/GNOME/gnome-shell/issues/460
--
You received
** No longer affects: gdm3 (Ubuntu)
** Also affects: gnome-shell via
https://gitlab.gnome.org/GNOME/gnome-shell/issues/460
Importance: Unknown
Status: Unknown
** Description changed:
- https://gitlab.gnome.org/GNOME/gdm/issues/305
-
- ---
-
Hello, folks,
Today when I
Public bug reported:
This bug is about inputting data in "Programming Mode -> Binary mode" in
the gnome-calculator snap.
1)
Description:Ubuntu 18.10
Release:18.10
2) - Its the default snap - so I guess this?
gnome-calculator 3.32.0+git2.cae338ea 352 stable/…
1:3.26.4-0~ubuntu18.04.4 also fixed this bug for me in Bionic, thanks!
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1767817
Title:
Full text search does not work
To manage
*** This bug is a duplicate of bug 1772791 ***
https://bugs.launchpad.net/bugs/1772791
** This bug has been marked a duplicate of bug 1772791
Lock/login screen displays password in clear text occasionally
** Information type changed from Private Security to Public Security
--
You
** Changed in: oem-priority
Status: Expired => New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1811668
Title:
oem-config fails on Nvidia GPU machine on 18.04.1
To manage
** Description changed:
- Looking to the journal it looks like it's trying to use the wrong
- desktop name, e.g on vlc it gave an error "no such desktop file:
- io.snapcraft.vlc-"
+ [Impact]
+ The launch button on the notification shown after snaps are installed doesn't
work.
+
+ [Test
** Also affects: gst-plugins-good via
https://gitlab.freedesktop.org/gstreamer/gst-plugins-good/issues/579
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in Ubuntu.
And upstream has proposed a fix already :)
https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/467
** Also affects: gnome-shell via
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1094
Importance: Unknown
Status: Unknown
** Changed in: gnome-shell (Ubuntu)
Status:
** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu)
--
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/1820423
Title:
monitors.xml is not parsed or applied correctly during
*** This bug is a duplicate of bug 387957 ***
https://bugs.launchpad.net/bugs/387957
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gtk+2.0 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of
Jonas, that is bug 1812527 you have. Please comment in bug 1812527
instead.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1817682
Title:
Ubuntu 18.04 interface freeze -
I have exactly the same problem but it only happens when I talk to
people that uses Windows on their desktop. I attached a section of my
syslog where this happened.
** Attachment added: "Part of syslog when gnome crash occured"
*** This bug is a duplicate of bug 1812527 ***
https://bugs.launchpad.net/bugs/1812527
Yes, I think it is the same bug, just happen in different application.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
Re-pasting attachment cleaned from sensitive data.
** Attachment removed: "Part of syslog when gnome crash occured"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1817682/+attachment/5247755/+files/syslog_gnome_crash.txt
** Attachment added: "Part of syslog when gnome crash
Thank you for your bug report. What desktop environment do you use? Does
this happen on any document? Could you try on newer ubuntu series?
** Changed in: evince (Ubuntu)
Importance: Undecided => Low
** Changed in: evince (Ubuntu)
Status: New => Incomplete
--
You received this bug
Well, I still can't reproduce with those steps :/ When the new dialog
opens in 6-7 it's the main windows and not the details from the previous
step, such there is no < to use...
The warning might give a clue to someone looking at the problem though
(ideally it should be reported upstream)
--
*** This bug is a duplicate of bug 1798053 ***
https://bugs.launchpad.net/bugs/1798053
That's bug #1798053, which was fixed in gnome-software 3.30.2-0ubuntu8.
Just install the latest updates in your VM.
** This bug has been marked a duplicate of bug 1798053
[SRU] Click on the back icon in
Public bug reported:
Can't run from 'gnome find' - nothing happens.
Try to run from terminal - get this:
hbarta@karakum:~$ gnome-system-monitor
You need to connect this snap to the gnome platform snap.
You can do this with those commands:
snap install gnome-3-26-1604
snap connect
I have this issue both in 18.10 and 19.04. Using arrows and space does
not work, the only workaround I've found is "sudo software-properties-
gtk". Would be happy to provide any details that could be useful.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
** Description changed:
- WORKAROUND: replace gdm3 with slick-greeter + lightdm-settings + gnome-
- screensaver + numlockx(optionally)
+ WORKAROUND
+
+ Replace gdm3 with slick-greeter + lightdm-settings + gnome-screensaver +
+ numlockx(optionally)
+
TL;DR
+
+ Correct positioning and
Public bug reported:
Ubuntu 19.04, 64 bit machine, nvidia graphics drivers
Upon first and subsequent launches of gnome-terminal the window shows
but does not immediately gain focus to start typing in commands.
I expect it to immediately gain focus to type commands upon launch each
and every
I find that primary(left-clicking) up to 15 or 20+ times _eventually_
spawns the pkexec-gui box.
On Wed, Mar 20, 2019 at 9:26 AM Bjoern H. <1727...@bugs.launchpad.net>
wrote:
> I have this issue both in 18.10 and 19.04. Using arrows and space does
> not work, the only workaround I've found is
** Changed in: mutter
Status: Unknown => New
--
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/1796549
Title:
Xorg sessions have higher output lag than Wayland sessions
To
Public bug reported:
Sometimes it crashes, i think i was trying to move a window to the right
side of the screen when this happened.
Backtrace:
sudo gdb /usr/bin/budgie-wm /tmp/coredump.budgie-wm.12829.kedz-i7s850.1553090616
GNU gdb (Ubuntu 8.2-0ubuntu1) 8.2
Copyright (C) 2018 Free Software
Christian, first, it seems that you did "cupstestppd" on a PPD file
which is not auto-generated:
--
$ sudo cupstestppd /etc/cups/ppd/Kyocera-ECOSYS-P6026cdn.ppd
/etc/cups/ppd/Kyocera-ECOSYS-P6026cdn.ppd: FAIL
**FAIL** Missing choice *Option18 SDCard in UIConstraints "*KCCollate
Sure, here's my Xorg.log
** Attachment added: "Xorg.0.log"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/1820832/+attachment/5247765/+files/Xorg.0.log
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Jonas, that is bug 1812527 you have. Please comment in bug 1812527
instead.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1817682
Title:
Ubuntu 18.04 interface freeze -
Nikolay,
Please follow the steps in comment #9.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1817682
Title:
Ubuntu 18.04 interface freeze - during video call or screen
Thank you for your bug report. Confirmed and sent upstream
https://gitlab.freedesktop.org/gstreamer/gst-plugins-good/issues/579
** Bug watch added: gitlab.freedesktop.org/gstreamer/gst-plugins-good/issues
#579
https://gitlab.freedesktop.org/gstreamer/gst-plugins-good/issues/579
** Changed
Filed upstream at: https://gitlab.gnome.org/GNOME/gnome-
shell/issues/1094
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1094
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1094
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
Being discussed on https://forum.snapcraft.io/t/cant-run-gnome-system-
monitor-ubuntu-18-04/10495/1
** Changed in: gnome-system-monitor (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
*** This bug is a duplicate of bug 1758287 ***
https://bugs.launchpad.net/bugs/1758287
Public bug reported:
Open a .webm video clicking on it, click on the '<' icon top left ...
crash
ProblemType: Crash
DistroRelease: Ubuntu 19.04
Package: totem 3.32.0-1ubuntu1
ProcVersionSignature: Ubuntu
Christian, both your attached PPD files are auto-generated, and both
pass cupstestppd.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1813825
Title:
"driverless"
I think the problem here is CUPS' own method of generating temporary
queues for discovered driverless printers. gnome-control-center, and
probably other GUIs, like the GTK print dialog, cannot cope with this.
So we leave this bug report assigned to gnome-control-center for now.
Christian, if you
would it be possible to find out which update fixed this issue and back
port to 16.04? Majority of my systems (10+ boxes) are on 16.04 because
many things broke (otherwise) on 18.04. I do not plan to upgrade in the
next few years.
--
You received this bug notification because you are a member of
on another machine running Ubuntu 18.04, the rendering of this PDF looks
normal.
** Attachment added: "sample pdf that failed on 16.04"
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1820904/+attachment/5247895/+files/Solving_system_equations_using_math_tools.pdf
--
You received this
*** This bug is a duplicate of bug 1758287 ***
https://bugs.launchpad.net/bugs/1758287
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 #1758287, so is being marked as such.
** Tags added: disco
--
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/1758287
Title:
totem crashed with SIGTRAP in __glXSendError() from
MakeContextCurrent()
To manage
*** This bug is a duplicate of bug 1597439 ***
https://bugs.launchpad.net/bugs/1597439
Thanks Andreas, also I now have taken a look at the demotion.
The only reason to demote is was that the need from unity to pull it in went
away.
There was no explicit demotion reason filed.
Therefore we
Ubuntu 18.04.2 up to date at 20/3/2019
getting similar warnings:
Mar 20 19:57:28 RooTBooK gnome-shell[2561]: Some code accessed the
property 'WindowPreviewMenu' on the module 'windowPreview'. That
property was defined with 'let' or 'const' inside the module. This was
previously supported, but is
This is a *great* feature that it'd be really cool for Ubuntu to have
and I'm very pleased that the team has been working on it, but...
I really don't feel very good about this freeze exception request. It
doesn't seem right to me to be adding unmerged, experimental and
unfinished features into
*** This bug is a duplicate of bug 1723678 ***
https://bugs.launchpad.net/bugs/1723678
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
The snap is now working. (In other words, not able to reproduce.)
I'm not sure what made the change but I did reboot several times.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-system-monitor in Ubuntu.
> that runs a very high risk of either being disruptive to the release
Hum, my understanding is that it is basically be a no-op unless the
gsettings key is set? If so I see the risk for the release being low,
'go enable an experimental gsettings key and restart your session'
doesn't sound like a
52 matches
Mail list logo
