> That sounds like bug 2084407 which is in progress.
Great to hear that. Meanwhile, I would like to know what to do when this
happens.
There is no documentation about resetting the monitors status to default in
this case.
> This file shows xdg-desktop-portal-gnome is crashing on login sometime
** Tags removed: fixed-in-mutter-47.1
** Tags added: fixed-in-mutter-46.7
--
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/2080602
Title:
[regression] GNOME 46/47 dropped support for
> The closest thing to a reset that GNOME has is [...]
I did that but did not help.
> In theory that can happen due to different ports or cables measuring
> different bandwidth [...]
I did change three cables but I still see 60Hz on the second monitor and
30Hz on the third even if they come fr
If the 30Hz issue persists even after swapping cables then it sounds
like a problem with one of the connectors or ports. Assuming the
monitors are absolutely identical. Because the product specs suggest a
4060 Ti can do at least 4x4K displays.
So that we can see more details, please run:
xrandr
While there is a definite fix here, I suggest this one be deferred until the
universal fix for all SIGKILL issues lands:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/4124
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutte
*** This bug is a duplicate of bug 2054761 ***
https://bugs.launchpad.net/bugs/2054761
Same problem here, except a new install of 24.04.1 but using the previous /home
from 22.04. I can only get DNS working by manually adding a DNS entry (e.g.
9.9.9.9) in /etc/systemd/resolved.conf. I've trie
Thanks. I can see you're using Xorg fractional scaling which can cause
multi-monitor problems. So please try selecting 'Ubuntu on Wayland' at
the login screen. If for some reason that's not available then please
try disabling fractional scaling in Settings > Displays.
In the worst case, if you don
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Changed in: xserver-xorg-input-libinput (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https:
BTW the 30Hz problem is usually caused by a low quality HDMI cable (when
it happens to other people). The best solution is to use DisplayPort as
much as possible. But if you are forced to use HDMI then make sure the
cable is rated for at least HDMI 2.0 or 2.1.
--
You received this bug notificatio
Thanks. I didn't ask about 24.10 because for most people changing
releases is too much to ask... But since you did, we can declare this
fixed in 24.10, somehow.
** Also affects: mutter via
https://gitlab.gnome.org/GNOME/mutter/-/issues/3788
Importance: Unknown
Status: Unknown
** Chan
Reported upstream here:
https://gitlab.gnome.org/GNOME/mutter/-/issues/3788
I tested Ubuntu 24.10 and could not reproduce the issue there.
I also realized that it doesn't matter whether the mouse cursor is over
the window or not.
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #378
** Changed in: shotwell (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to shotwell in Ubuntu.
https://bugs.launchpad.net/bugs/2080004
Title:
Shotwell bug - Out of memory #5123
To manage not
** Changed in: gnome-control-center
Status: New => Fix Released
--
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/2077117
Title:
settings - mouse&touchpad - scroll
> So that we can see more details, please run: [...]
I attached the xrandr output. Be advised the two monitors are using
different cables (HDMI and DisplayPort). I am going to buy a new
DisplayPort cable to further test this.
> Also we shouldn't be calling this a crash (per the title) unless
ther
This bug was fixed in the package sane-airscan - 0.99.29-1.1
Sponsored for Nathan Teodosio (nteodosio)
---
sane-airscan (0.99.29-1.1) unstable; urgency=medium
* Non-maintainer upload.
* New upstream version 0.99.29. Closes: #1073356.
* B-D libtiff-dev
-- Jérémy Lal Thu, 25 J
> There is no documentation about resetting the monitors status to
default in this case.
The closest thing to a reset that GNOME has is:
1. rm ~/.config/monitors.xml
2. Log in again.
> Even worse, two identical monitors are seen from Ubuntu with a
slightly different refresh frequency.
In theory
Public bug reported:
kf6-extra-cmake-modules replaces the old source extra-cmake-modules
source in debian and now plucky.
However src:extra-cmake-modules is on our i386 whitelist and kf6-extra-
cmake-modules is not, so kf6-extra-cmake-modulesneeds to build on i386
for remaining reverse build deps
Public bug reported:
Maximized GTK 2 apps does not restore maximized state when run under
"Ubuntu on Xorg" session in 24.04 and 24.10.
Steps to reproduce:
- Install gtk 2 app which saves windows state, e.g. GIMP.
- Start GIMP. Maximize GIMP window. Close GIMP.
- Start GIMP again.
Result:
GIMP
** Tags added: udeng-5205
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2085575
Title:
Seeking is unreliable and often causes video to stop
To manage notifications about this bug go
19 matches
Mail list logo
