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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1831039
Title:
\safari
>:]
** Attachment added: "web browser url (\safari)"
https://bugs.launchpad.net/ubuntu/+source/xfce4/+bug/1838154/+attachment/5362328/+files/2020%200428%20%20url%20name.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Sorry, I got confused with smb://.
...I've been doing a lot of tests because I'm not getting the same feedback:
laurent@laurent-iMac:~$ smbclient //192.168.1.1/USB1
Unknown parameter encountered: ", bind interfaces only"
Ignoring unknown parameter ", bind interfaces only"
protocol negotiation
** Also affects: firefox (Ubuntu)
Importance: Undecided
Status: New
** Also affects: chromium-browser (Ubuntu)
Importance: Undecided
Status: New
** Changed in: firefox (Ubuntu)
Importance: Undecided => Low
** Changed in: chromium-browser (Ubuntu)
Importance: Undecided
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1831039
Title:
** Tags added: eoan
** Summary changed:
- In Wayland sessions the onscreen keyboard does not open in text inputs for
many applications such as Firefox or Chrome
+ The onscreen keyboard does not open in text inputs for non-GTK applications
such as Firefox or Chrome
--
You received this bug
\safari
workspace name
>:] this might affect colors:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1875584
** Attachment added: "workspace name"
https://bugs.launchpad.net/ubuntu/+source/xfce4/+bug/1838154/+attachment/5362329/+files/2020%200428%20%20workspace%20name.png
**
*** This bug is a duplicate of bug 1831039 ***
https://bugs.launchpad.net/bugs/1831039
Thanks. It sounds like non-GTK apps are missing something here, so the
bug should probably be assigned to each of those apps/toolkits...
** Summary changed:
- eoan regression: OSK does not appear
I can't see edit possibility than I have little comment. I installed both Linux
distros using my second PC with unplugged boot HD (EFI), so in both cases Linux
installer had only one option, install system on external SSD. Now during
Huawei start I press F12 and I can choose which system I want
Hi Sven Meyer,
I'd like to address one bit of your article:
"... and I do not understand the reaction - Samuele Pedroni (pedronis)
wrote on 2020-04-23: "Contributing to the discussion with rudeness is
not conductive to collaboration, and will be moderated.""
The reason for Samuele's comment was
I'm using Ubuntu 20.04 and every time I start typing on my keyboard, the
"Keyboard battery low" alert pops up, obscuring a large part of the
screen. This is becoming really annoying. I do not want to completely
disable all power notifications as I'm using a laptop and need to know
when the laptop
Public bug reported:
It is impossible to use mod_filter in ejabberd 20, because it does not
accept acl.
But there is fix here
https://github.com/processone/ejabberd-contrib/issues/289
Could you, please, apply this patch in Ubuntu?
Thank you!
** Affects: ejabberd (Ubuntu)
Importance:
Tested in my PPA:
| https://launchpad.net/~hloeung/+archive/ubuntu/nagios-nrpe/+packages
With output:
| $ time ./check_http -I 127.0.0.1 -p 9103 -u /metrics -r haproxy_rate -t 50
| HTTP OK: HTTP/1.0 200 OK - 13239810 bytes in 1.157 second response time
|time=1.156696s;;;0.00;50.00
Looks like delete is impossible too?
My problem is probably solved, I wrote "probably" because during the
procedure I can saw few errors which I can't explain, so we'll see.
I use the first method from the "linuxconfig.org/ubuntu-boot-repair", im my
second PC I disconnected boot HD, then
Public bug reported:
I see that Live Ubuntu 20.04 is plagued by disk checking on boot.
Not just with Live USB but with Persistent USB also.
If not fast enough to cancel with ctl-c it starts on filesystem.squashfs
and runs until over 90% complete.
Very irritating. There have been quite a few
Public bug reported:
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x7fda9eb90401, pid=3238, tid=3250
#
# JRE version: OpenJDK Runtime Environment (11.0.6+10) (build
11.0.6+10-post-Ubuntu-1ubuntu118.04.1)
# Java VM: OpenJDK 64-Bit Server VM
Note, give it time and it will be happy with PPS at better accuracy.
chronyc> sources
210 Number of sources = 10
MS Name/IP address Stratum Poll Reach LastRx Last sample
===
#x GPS
Overall rules to go with seems to be
# required for pps initialization
capability dac_read_search,
capability sys_time,
/sys/devices/virtual/pps/ r,
# to submit data to chrony
ptrace read peer=/usr/sbin/chronyd,
# for libusb
/sys/devices/**/usb[0-9]*/** r,
# triggered on fusercount, not
--- Comment From cborn...@de.ibm.com 2020-04-28 02:27 EDT---
> Booting over the public internet FTP server, terrifies me. Because
> there is no secureboot verification of either kernel or the initrd.
> Meaning it's trivial to man-in-the-middle attack, and inject things
> into the
Hrm. The core20 kernel snap is bigger than the core18 snap and
increasing the VM memory to 2G seems to 'fix' this. I guess the question
is is there a way to handle this more gracefully than killing QEMU?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
The client can timeout while the daemon is still doing a lot of active
work.
There are 3 cases to take into account:
- daemon not started: give a timeout for the daemon to start before the client
exits. Ideally, we would pulse back to the client, but the entrypoint isn’t
I also have an RST problem on my HP-laptop, I followed the instructions and
went into my BIOS and my RST is in fact turned off. I canot get to the
partition screen due to it saying that RST is turned on which it is not. here
are my system specs:
Public bug reported:
Opening new sql_window generate pgadmin3 crash. This is log from
.xsession-errors:
(pgadmin3:18489): Gtk-CRITICAL **: 09:29:06.591: gtk_box_gadget_distribute:
assertion 'size >= 0' failed in GtkScrollbar
(pgadmin3:18489): Gtk-CRITICAL **: 09:29:06.647:
** Summary changed:
- The “show on” option in Ubuntu-settings-appearance-Dock has a bug. When I
would select a monitor instead of “All display”, nothing changes and it
reverts to “All display” again.
+ The “show on” option in Ubuntu-settings-appearance-Dock has a bug
--
You received this
I can confirm that with 2G the guest seems to start up now.
I agree that this should be more graceful, but it has to be triggered by the
guest.
So might the error path in the guest run into a dead-end if unable to load the
kernel that then is like a illegal instruction to the host or something
Essentially the check iterates over all /proc/
And there it does readlink to check if any has the target open.
In my example if any FD is a link to /dev/ttyUSB0
But this already is "graceful" the apparmor deny to
readlink(fdpath, linkpath, sizeof(linkpath)
is
apparmor="DENIED"
Seeing that this bug got considerable attention, I'd like to highlight another
bug that is even more serious (in my opinion) which relates to Chromium being
snap:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1741074
This other bug affects more people, breaks numerous apps
Dear everyone.
I use ubuntu-20.04 everyday,change to use nVidia driver 340.108 from nouveau.
I feel that mouse do not move smooth sometimes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872366
Sven, allow me to contribute a few corrections/clarifications to your
article:
« but as they use Chromium (the pre-installed open source version of the
Google Chrome browser) »
This is incorrect, chromium is not pre-installed. One has to go and
install it from the package manager/software store.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: davfs2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1859293
Title:
Ok, it seems after eliminating the above issue the sys_ptrace isn't triggered
anymore.
And even if it is it seems not required for the functionality and would be
rather unsafe.
Until I get a GPS lock chrony sees:
chronyc> sources
210 Number of sources = 10
MS Name/IP address Stratum
*** This bug is a duplicate of bug 1874662 ***
https://bugs.launchpad.net/bugs/1874662
The installation media is directly an ISO file from a SSD disk. No UDB
stick is involved. The logs say checksum of the ISO image is OK. Please
check again
ti 28. huhtik. 2020 klo 3.05 Chris Guiver
Yes. I win.
I install new systemd service with timer for power off NVidia after startup.
Problem:
New laptop Lenovo S540 (2020-made) + Ubuntu 18.04 LTS with NVidia 435 driver
eats battery for 2-3 hours.
Result:
12 hours on battery.
Before that the actions from comment #43 have been taken
Hopefully mutter 3.36.2 will be backported to Ubuntu 20.04 soon!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1852183
Title:
[X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04
To
** Changed in: zsys (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874304
Title:
grub-probe fails with failed to get canonical path of rpool with ZFS
Thank you for your bug report. Is the sound normal in other
applications? Could you go to the sound panel to see if the slider is
low for the webbrowser you are using while playing a video?
** Changed in: pulseaudio (Ubuntu)
Status: New => Incomplete
** Changed in: pulseaudio (Ubuntu)
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: monitoring-plugins (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875517
Thanks, the log has warnings from wpa-supplicant, could be an issue
there or in the driver
** Changed in: network-manager (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Package changed: ubiquity (Ubuntu) => gcc-9 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875532
Title:
trying to compile gcc make build and getting errors
To manage notifications
In the #8, the testing kernel was not installed successfully.
Please try to install this testing kernel:
https://people.canonical.com/~hwang4/25skipi915/, it is 5.4.0-25-generic which
has different version from yours.
sudo dpkg -i *.deb
then remove workaround temporarily
reboot, in the grub,
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: monitoring-plugins (Ubuntu Bionic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
I am getting a lot of:
GLib-GObject-WARNING **: 09:00:09.217: ../../../gobject/gsignal.c:2617: signal
'changed::' is invalid for instance '0x55b923a6b430' of type 'GSettings'
This is especially visible with Webkit2Gtk applications such as GNOME
Web.
A fix has landed
That should be:
loopback loop /snaps/pc-kernel_461.snap
in the previous commit #7.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875012
Title:
UC20 running in OVMF triggers qemu emulation error
IP of my pc : 192.168.1.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875354
Title:
No more smb access after migration to UBUNTU 20.04 from UBUNTU 19.10
To manage notifications about this bug
Public bug reported:
Ubuntu 20.04 live-server installation consistently fails when you try to
reuse existing partitions:
Traceback (full logfile attached):
get_blockdev_sector_size: (log=512, phys=512)
sda logical_block_size_bytes: 512
Verifying /dev/sda1 exists
Verifying /dev/sda1 size,
Ok it seems the kernel snap is causing this. Core20 grub can loopmount
pc-kernel_455.snap (from a core18 image) just fine but kills QEMU when
loopmounting pc-kernel_461.snap (the original core20 snap).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
In clean-installed 20.04 (amd64) using "linux" and "initrd.gz" found in
"netboot.tar.gz", kernel panic is caused by the missing
"initrd.img-*-lowlatency" on the first boot.
Procedure to reproduce the bug is as follows:
1.)Extract "netboot.tar.gz" and move the resulting
This bug has been closed for a few years so please open a new one by
running:
ubuntu-bug gnome-shell
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1725649
Title:
Fullscreen games lose
This bug closed automatically because the original reporter did not
respond. Please open a new bug by running:
ubuntu-bug gnome-shell
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798840
Title:
Dale, it sounds like you're experiencing a different issue like maybe
bug 1870736 and/or bug 1873403.
So that we can find out, please log a new bug by running:
ubuntu-bug mutter
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: linux (Ubuntu Eoan)
Status: New => In Progress
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873506
Public bug reported:
the error message in pop-up box "Installed initramfs-tools package post
installation script subprocess returned exit status 1"
in the lower box, title="installed linux-modules-nvidia-440-generic-hwe-20.04
(amd64)"
in the shell:
"ubuntu ubiquity:
All autopkgtests for the newly accepted systemd (237-3ubuntu10.40) for bionic
have finished running.
The following regressions have been reported in tests triggered by the package:
gvfs/1.36.1-0ubuntu1.3.3 (amd64)
prometheus-postgres-exporter/unknown (armhf)
systemd/237-3ubuntu10.40 (i386,
All autopkgtests for the newly accepted systemd (237-3ubuntu10.40) for bionic
have finished running.
The following regressions have been reported in tests triggered by the package:
gvfs/1.36.1-0ubuntu1.3.3 (amd64)
prometheus-postgres-exporter/unknown (armhf)
systemd/237-3ubuntu10.40 (i386,
1.7.3.4 has landed in Groovy, I tested
https://launchpad.net/ubuntu/+archive/primary/+files/socat_1.7.3.4-1_amd64.deb
in Focal and it works fine.
I also copied it to the Epoptes stable PPA,
https://launchpad.net/~epoptes/+archive/ubuntu/ppa/+packages.
Btw the regression is in socat, not in
Ok I can reproduce
One sees just quickly the bootloader flying by:
BdsDxe: loading Boot0001 "UEFI QEMU HARDDISK QM5 " from
PciRoot(0x0)/Pci(0x4,0x0)/Sata(0x0,0x,0x0)
BdsDxe: starting Boot0001 "UEFI QEMU HARDDISK QM5 " from
PciRoot(0x0)/Pci(0x4,0x0)/Sata(0x0,0x,0x0)
Can someone help to dissect the UC20 image and what it does differently here?
The cloud-image boots with the same OVMF/Uefi based config, but UC20 runs into
a crash.
Understanding what the UC20 boot does differently and any chance to
build that piece by piece (e.g. be able to skip some steps
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: open-vm-tools (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869074
The next critical one was cap "sys_ptrace", that comes from another part
of the code but also isn't strictly required for functionality. Let us
understand why that is triggered.
That one seems to be even more interesting.
It does trigger under gdb, but not when single stepped to find where it
** Also affects: monitoring-plugins (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875517
Title:
check_http inefficient and sometimes
Thanks, by white space you mean empty line right?
** Tags added: champagne
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875501
Title:
Remove white space from output
To manage notifications
The first thing that grub does when booting is:
loopback /snaps/pc-kernel_461.snap
which kills QEMU.
In core20 that snap is on an 'EFI System' partition (vfat) whereas in
core18 it's on a regular Linux (ext4) partition.
--
You received this bug notification because you are a member of Ubuntu
Thanks, could you also add your 'journalctl -b 0' log after getting the
issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875445
Title:
Volume slider doesn't produce sound
To manage
Thanks for your suggestion!
Actually, zsys does it a little bit differently:
- snapshots (state save) are taken everytime you modify your system by apt or
other things.
- In addition to this, everytime you reach graphical.target, we stamp the
current state (which can also be a clone) as the
Could you add the apport-collect informations requested and attach your
'journalctl -b 0' log after getting the issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875435
Title:
Re-logging occurs
Thank you for your bug report. It's a bug (lack of feature) in those
tools, not a bug in the theme
** Package changed: yaru-theme (Ubuntu) => unity-tweak-tool (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thank you for coming back.
So I'm going to start from a good base and delete what I did.
laurent@laurent-iMac:~$ pkill gvfs; pkill nautilus
pkill: le pid 1184 n'a pu être tué: Opération non permise
pkill: le pid 1199 n'a pu être tué: Opération non permise
pkill: le pid 1204 n'a pu être tué:
I opened a bug report that was closed as a duplicate of this bug, so I
think that this bug is the right place for me to post my comment now. I
just want to point out that this problem still exists under Ubuntu 20.04
and Libre Office 6.4.2.2. Ubuntu 20.04 went into production status a few
days ago
** Changed in: boot-repair
Assignee: Chris (lusciosdark) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/806291
Title:
[needs-packaging] Boot-Repair pre-installed in ISOs
To
Public bug reported:
The “show on” option in Ubuntu-settings-appearance-Dock has a bug. When
I would select a monitor instead of “All display”, nothing changes
and it reverts to “All display” again.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell-extension-ubuntu-dock
All autopkgtests for the newly accepted systemd (237-3ubuntu10.40) for bionic
have finished running.
The following regressions have been reported in tests triggered by the package:
gvfs/1.36.1-0ubuntu1.3.3 (amd64)
prometheus-postgres-exporter/unknown (armhf)
systemd/237-3ubuntu10.40 (i386,
All autopkgtests for the newly accepted systemd (237-3ubuntu10.40) for bionic
have finished running.
The following regressions have been reported in tests triggered by the package:
gvfs/1.36.1-0ubuntu1.3.3 (amd64)
prometheus-postgres-exporter/unknown (armhf)
systemd/237-3ubuntu10.40 (i386,
All autopkgtests for the newly accepted systemd (237-3ubuntu10.40) for bionic
have finished running.
The following regressions have been reported in tests triggered by the package:
gvfs/1.36.1-0ubuntu1.3.3 (amd64)
prometheus-postgres-exporter/unknown (armhf)
systemd/237-3ubuntu10.40 (i386,
All autopkgtests for the newly accepted systemd (237-3ubuntu10.40) for bionic
have finished running.
The following regressions have been reported in tests triggered by the package:
gvfs/1.36.1-0ubuntu1.3.3 (amd64)
prometheus-postgres-exporter/unknown (armhf)
systemd/237-3ubuntu10.40 (i386,
Public bug reported:
root@eu1:/var/log# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04 LTS
Release:20.04
Codename: focal
root@eu1:/var/log# apt-cache policy cryptsetup
cryptsetup:
Installed: (none)
Candidate: 2:2.2.2-3ubuntu2
All autopkgtests for the newly accepted systemd (237-3ubuntu10.40) for bionic
have finished running.
The following regressions have been reported in tests triggered by the package:
gvfs/1.36.1-0ubuntu1.3.3 (amd64)
prometheus-postgres-exporter/unknown (armhf)
systemd/237-3ubuntu10.40 (i386,
All autopkgtests for the newly accepted systemd (237-3ubuntu10.40) for bionic
have finished running.
The following regressions have been reported in tests triggered by the package:
gvfs/1.36.1-0ubuntu1.3.3 (amd64)
prometheus-postgres-exporter/unknown (armhf)
systemd/237-3ubuntu10.40 (i386,
This is the expected behaviour while we have module-switch-on-connect
enabled by default. So it's not a bug.
** Tags removed: fecal
** Tags added: focal
** Changed in: pulseaudio (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of
All autopkgtests for the newly accepted systemd (237-3ubuntu10.40) for bionic
have finished running.
The following regressions have been reported in tests triggered by the package:
gvfs/1.36.1-0ubuntu1.3.3 (amd64)
prometheus-postgres-exporter/unknown (armhf)
systemd/237-3ubuntu10.40 (i386,
All autopkgtests for the newly accepted systemd (237-3ubuntu10.40) for bionic
have finished running.
The following regressions have been reported in tests triggered by the package:
gvfs/1.36.1-0ubuntu1.3.3 (amd64)
prometheus-postgres-exporter/unknown (armhf)
systemd/237-3ubuntu10.40 (i386,
** Description changed:
In clean-installed 20.04 (amd64) using "linux" and "initrd.gz" found in
"netboot.tar.gz", kernel panic is caused by the missing
"initrd.img-*-lowlatency" on the first boot.
Procedure to reproduce the bug is as follows:
1.)Extract "netboot.tar.gz" and move the
All autopkgtests for the newly accepted systemd (237-3ubuntu10.40) for bionic
have finished running.
The following regressions have been reported in tests triggered by the package:
gvfs/1.36.1-0ubuntu1.3.3 (amd64)
prometheus-postgres-exporter/unknown (armhf)
systemd/237-3ubuntu10.40 (i386,
** Tags added: radeon
** Summary changed:
- The image breaks after exiting the mode suspend
+ [radeon] The image breaks after exiting the mode suspend
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This bug was fixed in the package spirv-tools - 2020.2-1
---
spirv-tools (2020.2-1) unstable; urgency=medium
* New upstream release. (LP: #1871754)
* control: Bump spirv-headers build-dependency.
-- Timo Aaltonen Thu, 09 Apr 2020 14:24:11 +0300
** Changed in: spirv-tools
** Project changed: mutter => ubuntu
** No longer affects: ubuntu
** Tags added: cursor
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873052
Title:
GNOME 3.36 Lands Scaled/Transformed Hardware
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Eoan)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Fix committed, scheduled for release in 1:3.36.1-1ubuntu6
** Changed in: gnome-control-center (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
After applying fractional scaling to 125 % I see around three quarter of
the workspace, the other part of the workspace I can see if I go to the
border of the screen with the mouse. The workspace starts to 'scroll'.
Everything is quite 'big' maybe on a level of 200 % scaling.
Reported #1875603.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1857383
Title:
Fractional scaling applies to both monitors when you only want it on
one
To manage notifications about this bug go
I think this should still be Low importance.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873184
Title:
Wired connection details has not enough height and items overlap
To manage notifications
*** This bug is a duplicate of bug 1873052 ***
https://bugs.launchpad.net/bugs/1873052
Sounds like a duplicate of bug 1873052. See also bug 1875528.
** Tags added: xrandr-scaling
** This bug has been marked a duplicate of bug 1873052
GNOME 3.36 Lands Scaled/Transformed Hardware Cursors
*** This bug is a duplicate of bug 1875113 ***
https://bugs.launchpad.net/bugs/1875113
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
** This bug has been marked a duplicate of bug 1875113
OpenGL not detected (Intel Ivy Bridge + Nvidia GeForce GT 635M)
--
You received this
The update has been synced to g-serie now
** Description changed:
- The bug is a placeholder for SRU information if needed
+ * Impact
+ That's the current GNOME stable update, including some fixes
+ https://gitlab.gnome.org/GNOME/glib-networking/-/blob/master/NEWS
+
+ * Test case
+
+ The
** Also affects: gdm via
https://gitlab.gnome.org/GNOME/gdm/-/issues/580
Importance: Unknown
Status: Unknown
** No longer affects: xorg (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872026
Title:
App icon aspect ratio in the panel is broken
To manage
Public bug reported:
* Impact
That's the current GNOME stable update, including some fixes and translation
updates
https://gitlab.gnome.org/GNOME/gnome-initial-setup/-/blob/master/NEWS
* Test case
The update is part of GNOME stable updates
https://wiki.ubuntu.com/StableReleaseUpdates/GNOME
*** This bug is a duplicate of bug 1870736 ***
https://bugs.launchpad.net/bugs/1870736
Thanks. This sounds like bug 1870736.
** This bug has been marked a duplicate of bug 1870736
[nvidia] Screen scaling 125% gives 200%
--
You received this bug notification because you are a member of
Please try:
1. rm -rf ~/.config/pulse/
2. Log out and in again.
** Changed in: pulseaudio (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875369
Title:
*** This bug is a duplicate of bug 1872026 ***
https://bugs.launchpad.net/bugs/1872026
** This bug has been marked a duplicate of bug 1872026
App icon aspect ratio in the panel is broken
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875424
Title:
[radeon] The image breaks after exiting
901 - 1000 of 1153 matches
Mail list logo
