@3v1n0
Running PopOS 20.10 right from the installer gets fractional scaling
working fine (installed nvidia driver version is 455).
What is it that you said they already packaged? Is this supposed to be
fixed in Groovy?
--
You received this bug notification because you are a member of Ubuntu
Bug
Public bug reported:
See upstream report https://gitlab.gnome.org/GNOME/gnome-
shell/-/issues/3378.
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: gnome-shell 3.38.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
Uname: Linux 5.8.0-26-generic x86_64
ApportVersion: 2.20.11
You're assuming right https://github.com/micheleg/dash-to-
dock/issues/1330
** Bug watch added: github.com/micheleg/dash-to-dock/issues #1330
https://github.com/micheleg/dash-to-dock/issues/1330
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I confirm this is still happening after fully updating a few minutes
ago. It's too close to the release and gives quite a bad impression,
even if it doesn't affect usability in a crucial way I would say that
importance isn't Low because of its visibility.
--
You received this bug notification bec
Public bug reported:
My screen is 3000x2000. I use a scaling factor of 2x. Today I upgraded
to 19.10 and chromium became a snap package. It launches at the right
scaling factor, but if I restart gnome shell (Alt-F2 r) it rescales to
1x (I believe) and everything becomes absurdly tiny. Restarting c
Public bug reported:
This was reported upstream in
https://gitlab.gnome.org/GNOME/mutter/issues/853 and closed since it is
a problem in shell and not mutter. I requested the maintainer to move it
to gnome-shell tracker instead of merely closing the issue. Otherwise I
will file a new ticket.
It is
Done in https://bugs.chromium.org/p/chromium/issues/detail?id=1043494,
should I also report this to Gnome Gitlab?
Btw, the problem also happens with VSCode, which is not surprising given
that it's an Electron based app.
--
You received this bug notification because you are a member of Ubuntu
Bug
** Summary changed:
- Chromium/Chrome looks tiny in hidpi after gnome shell restart
+ Chromium/Chrome/Electron look tiny in hidpi after gnome shell restart
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
Public bug reported:
Simply:
~:: gnome-shell --version
GNOME Shell 3.32.1
~:: apt info gnome-shell
Package: gnome-shell
Version: 3.32.2-2ubuntu1~ubuntu19.04.1
** Affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are
I realized of the problem because of:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1325#note_596254
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1325
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1325
--
You received this bug notification because you are a member o
I've an up-to-date Ubuntu installation.
Also:
~:: ps `pgrep gnome-shell`
PID TTY STAT TIME COMMAND
1618 tty2 Sl+5:48 /usr/bin/gnome-shell
1674 ?Sl 0:00 /usr/lib/gnome-shell/gnome-shell-calendar-server
~:: which gnome-shell
/usr/bin/gnome-shell
~:: gnome-shell --vers
I'm not an apt expert (I've been using Arch for about 10 years before I
recently switched to Ubuntu) but maybe this throws some light on the
issue:
~:: dpkg -s gnome-shell
Package: gnome-shell
Status: install ok installed
...
Version: 3.32.1-1ubuntu1~19.04.1
~:: apt show gnome-shell
Package: gno
Ok, I had already done that and was checking if upgrading to 3.32.2
solved https://gitlab.gnome.org/GNOME/gnome-shell/issues/1325, which it
doesn't :(
I don't know why @vladox is assuming it's fixed in 3.32.2, and I'm not
sure whether to interpret Florian intervention as confirming that, but
if @v
Hi Daniel, for me is ubuntu-dock, I've not even tested this with
upstream dash-to-dock.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834967
Title:
Activities overview doesn't shrink some windows a
Just to be clear: I didn't mean to imply it is an Ubuntu dock bug, just
that I was using that dock when it happened (btw it still happens). So I
hope it wasn't moved here because of my answer alone.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I've tested this with latest 19.10 (updated today) using gnome-session
and upstream dash-to-dock installed from gnome-software (can't remember
the version now, but I installed it a few minutes ago). The problem is
still there when the dock is vertically expanded to fit the screen. I've
reported thi
Public bug reported:
This is a bug upstream but since Ubuntu has its own fractional scaling
patch for x11 you might be interested in working together with the gnome
shell team. I refer you to my detailed description and some preliminary
analysis of the cause of the problem in gnome gitlab
https:/
I've tested this in two up-to-date 19.10 installations running in very
different laptops, one with hi-dpi, the other one an old standard dpi
one, and both still show the issue. Both have the standard vertically
expanded dock. It perplexes me as this issue status is "Fix released"
since almost one m
Also I agree that giving it low priority is to mischaracterise it, the
bug is not specific of Ubuntu, it's a bug somewhere in Gnome shell or in
Dash-to-dock that manifests when the dock is vertically stretched, as
it happens to be Ubuntu default configuration. But this also happens,
for example, i
Hi Olivier, sorry for the delay, I've installed Chrome from the official
deb and it also happens there so it seems like a non-snap specific,
upstream bug.
Do you have any idea what kind of "signal" could the app be receiving
when shell restarts? It's really weird that it somehow resets to 1x
scale
Public bug reported:
Upstream reports:
* https://gitlab.gnome.org/GNOME/gnome-shell/issues/1805
* https://gitlab.gnome.org/GNOME/gnome-shell/issues/1803
** Affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a memb
Public bug reported:
This is for 19.10 (Eoan).
See comments https://discourse.ubuntu.com/t/the-gnome-3-34-migration-
what-are-your-bugs/12348/27?u=memeplex and
https://discourse.ubuntu.com/t/the-gnome-3-34-migration-what-are-your-
bugs/12348/29?u=memeplex in Ubuntu Discourse.
** Affects: gnome-s
** Description changed:
This is for 19.10 (Eoan).
See comments https://discourse.ubuntu.com/t/the-gnome-3-34-migration-
what-are-your-bugs/12348/27?u=memeplex and
https://discourse.ubuntu.com/t/the-gnome-3-34-migration-what-are-your-
- bugs/12348/29?u=memeplex in Ubuntu Discourse.
+ bug
See additional screenshots and comments in Ubuntu Discourse:
*
https://discourse.ubuntu.com/t/the-gnome-3-34-migration-what-are-your-bugs/12348/27
*
https://discourse.ubuntu.com/t/the-gnome-3-34-migration-what-are-your-bugs/12348/29
and others below these.
Is this a problem upstream?
--
You
I don't think the title of this report is accurate. The is no
"shrinking" involved. The bottom window previews in the overview are
just clipped out of the screen, not shrinked.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
Do you think the importance of this problem is just low? It affects a
very central part of the desktop in a way that is not only ugly but also
hinders usability. Hopefully it's not an upstream issue and will be
auto-magically fixed by an update.
--
You received this bug notification because you a
@vanvugt in case Robert is right, could you move this to dash-to-dock
launchpad? Or do you prefer me to create a new issue (and maybe another
one at https://github.com/micheleg/dash-to-dock/issues)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Still happening in beta, when installing and after installation. If I
move the dock to the bottom it stops happening, no matter how many
windows I open.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/18
I'm not seeing this issue in an up-to-date 20.04 installation.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750818
Title:
Already installed deb packages not showing as installed when opened
To ma
Public bug reported:
You can see a detailed description of this issue in
https://askubuntu.com/questions/628206/how-can-i-boot-into-arch-linux-
using-initramfs-in-ubuntus-grub
The fix suggested there by Naiky is simple and works with a little
modification described in comment https://askubuntu.co
Happens to me in up to date GG using amdgpu for xorg session with
fractional scaling. The mouse pointer in gdm gets stuck at the beginning
of the session.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
Marco's workaround in #7 works for me.
--
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:
Showing two cursors after login
To manage notifications about this bug go to:
https://bugs.launch
I'm not sure what are you using as energy_performance_preference but
I've seen important improvements in scaling speed when using
balance_performance instead of balance_power, without the need to set
the governor to full performance. I'm in Arch at this moment and can't
remember if Ubuntu defaults
FWIW today 3.38 was released to Arch stable repo and I tested it using
kernel 5.8.10 and 5.8.13. For the same governor, energy performance and
gpu min freq settings, stuttering in the overview has increased a bit
(HiDPI screen & 620, I think you already know that at this point).
Anyway I've seen ma
Public bug reported:
According to https://cgit.freedesktop.org/xorg/app/xrandr/refs:
- 1.5 is five years old
- 1.5.1 is available since 18 months ago
1.5.1 introduces an interesting --filter flag that lets the user choose
between bilinear and nearest.
** Affects: xrandr (Ubuntu)
Importance
Public bug reported:
This was first described upstream in https://gitlab.gnome.org/GNOME
/gnome-shell/-/issues/2697
I'm reporting it here as requested in https://discourse.ubuntu.com/t
/gnome-shell-performance-improvements-in-
ubuntu-20-04/15972/38?u=memeplex
ProblemType: Bug
DistroRelease: Ubun
** Description changed:
This was first described upstream in https://gitlab.gnome.org/GNOME
/gnome-shell/-/issues/2697
I'm reporting it here as requested in https://discourse.ubuntu.com/t
/gnome-shell-performance-improvements-in-
ubuntu-20-04/15972/38?u=memeplex
+
+ Please don't be m
** Attachment added: "lspcik.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1890533/+attachment/5399149/+files/lspcik.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890533
Tit
** Attachment added: "journal.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1890533/+attachment/5399150/+files/journal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890533
T
> Also remember to update your system because it appears to be out of
date...
Strange cause I manually run the GUI updater on a daily basis. But it's
showing no update while I get 7 upgradeable packages from the CLI. Done,
just small things, no difference.
--
You received this bug notification b
> 1. Reboot, make sure you still see stuttering and then run these
commands:
Done
> 2. Completely uninstall these extensions:
They weren't installed in fact, just remaining configurations of old
installations. I've removed every reference to them from my settings
now.
> 3. Disable 'Ubuntu AppI
> For me, only GNOME 3.38 (prerelease) is close to smooth at 4K.
Is there a reasonably simple way to test this in Ubuntu? Or maybe I
could look for a package in the AUR.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
Public bug reported:
I would like to revisit https://bugs.launchpad.net/ubuntu/+source
/evolution-data-server/+bug/1805666
For years, I've been closing both the "modern" notification popup and
the "classic" popup window at the same time, many times a day. This is
really annoying.
The only way of
Well, according to the XDG spec you can disable autostarting at the user
level in a way that won't be overwritten by future updated:
> If an application autostarts by having a .desktop file installed in
the system wide autostart directory, an individual user can disable the
autotomatic start of th
** Description changed:
I would like to revisit https://bugs.launchpad.net/ubuntu/+source
/evolution-data-server/+bug/1805666
For years, I've been closing both the "modern" notification popup and
- the "classic" popup window at the same time, many times a day. This is
- really annoying.
+
The Spotify snap has always shown a tiny mouse pointer in HiDPI screens.
The issue has been discussed in https://forum.snapcraft.io/t/very-ugly-
cursor-for-spotify-and-kde-snaps/17118 but the conclusion was that this
should be fixed upstream (here is the upstream report that presumably
nobody that
Public bug reported:
Please sync calibre 5.3.0+dfsg-1 (universe) from Debian unstable (main)
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971947
Ubuntu 20.04 LTS has shipped a beta version of calibre that is unable
to even start.
There has been a fix for five months now.
Please, eithe
I've reported this with the requestsync tool but:
> Changelog entries since current hirsute version
4.99.12+dfsg+really4.23.0-1:
seems wrong to me since my version is focal, not groovy nor hirsute.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
I know @teward, and this is probably already fixed in groovy (I've not
tested that), but the request is for focal despite what the description
says (see comment #1 above). It's specially important for focal since
the package is non-functional as it is and focal is an LTS relase.
--
You received t
Well, groovy is shipping
4.99.12+dfsg+really4.23.0-1
instead of
4.99.4+dfsg+really4.12.0-1build1:
which is in focal.
Both are beta releases, so probably both worth syncing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
See also https://askubuntu.com/questions/1285431/calibre-no-longer-
working
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901921
Title:
Sync calibre 5.3.0+dfsg-1 (universe) from Debian unstable (ma
I'm surely requesting an exception here since the package shipped in
focal doesn't even start, I believe you cannot go worse than that by
syncing.
** Description changed:
Please sync calibre 5.3.0+dfsg-1 (universe) from Debian unstable (main)
- See https://bugs.debian.org/cgi-bin/bugreport.c
Is it because that would imply syncing dependencies also? I've not
checked if that's the case. FWIW the workaround in comment
https://bugs.launchpad.net/calibre/+bug/1877180/comments/6 works for me
as far as I can see.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
When this started to happen? I would be surprised if it was an update to
focal (why?), but I have the feeling this was working at the beginning.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898904
T
** Description changed:
Please sync calibre 5.3.0+dfsg-1 (universe) from Debian unstable (main)
- See https://bugs.launchpad.net/calibre/+bug/1877180
+ See https://bugs.launchpad.net/ubuntu/+source/calibre/+bug/1898904
Ubuntu 20.04 LTS has shipped a beta version of calibre that is unable
I had confused the upstream tracker with the Ubuntu tracker for Calibre,
since both live in Launchpad, but now that I've seen the downstream
report at https://bugs.launchpad.net/ubuntu/+source/calibre/+bug/1898904
it seems like if this started happening recently (I vaguely remember
this was working
Maybe a python upgrade to 3.8.5 at some point since the release of
focal?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898904
Title:
Calibre crashes at startup with AttributeError: 'NoneType' obje
Ok, I'm marking this as invalid after having read this very detailed
description of the situation:
https://forum.snapcraft.io/t/package-calibre-epub-books-reader/20436/11
Besides this particular comment all the thread is worth reading.
** Changed in: calibre (Ubuntu)
Status: New => Invali
For future reference:
Upstream report: https://gitlab.gnome.org/GNOME/evolution-data-
server/-/issues/262
Workarounds:
- Disable autostart as described above, but this will cancel both Gnome Shell
and e-a-n notifications.
- Alternatively, set
/org/gnome/evolution-data-server/calendar/notify-w
I'm closing this since according to upstream they are the ones who
should fix this (but it's blocked on a Gnome Shell issue).
** Changed in: evolution-data-server (Ubuntu)
Status: Incomplete => Invalid
** Bug watch added: gitlab.gnome.org/GNOME/evolution-data-server/-/issues #262
https:
Sorry for the noise, but now I'm reading
https://lists.ubuntu.com/archives/ubuntu-devel/2020-October/041237.html
and there was a suggestion there to sync but from Groovy:
> I checked Calibre in Groovy (version 4.99.12+dfsg+really4.23.0-1) and
it works fine. As per bug report #1898904
(https://bugs
Here https://lists.ubuntu.com/archives/ubuntu-
devel/2020-October/041237.html is a suggestion to sync from Groovy to
Focal in order to fix the issue:
> I checked Calibre in Groovy (version 4.99.12+dfsg+really4.23.0-1) and
it works fine. As per bug report #1898904
(https://bugs.launchpad.net/ubuntu
Public bug reported:
This is a downstream report to help track upstream
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2697.
The issue has been described at length (maybe excessively) upstream, so
I'm pointing to a "sum up" comment here https://gitlab.gnome.org/GNOME
/gnome-shell/-/issues/26
I forgot to mention that resolution is 3000x2000, it's a hidpi screen
with 2x scaling factor. Of course, that makes things harder but, as I
said, it's working pretty well in Wayland 3.36 on Arch and Fedora.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
I'm experiencing this also but it's much worse than reported above, in
all of these environments performance is behind 19.10/3.34:
* gnome-session / X11
* gnome-session / Wayland
* ubuntu-desktop / X11
* ubuntu-desktop / Wayland
ubuntu-desktop / X11 is by far the worst combination, but in all ot
I've been doing some testing and disabling panel self refresh (PSR) on
the Intel driver seems to help quite a lot with frame dropping in X11,
this is a known fact for the Matebook Pro, at least for Windows. Still
not perfect, still a bit of stuttering, but an improvement anyway.
--
You received t
Further investigation shows that using linux-5.5 (from
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5/) has a very
positive impact on performance and gnome-session/Wayland becomes
comparable with Arch and Fedora. At least this points to a definite
cause, but it's somewhat of a sad outcome sinc
Public bug reported:
At some time there was the issue of Whatsapp not recognizing the user
agent of Chromium, which was closed because it was the understanding
that the problem should be fixed by Whatsapp and not Ubuntu:
https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/1808853?com
Seems that this has been fixed in 20.04, should I close it or leave it
open for 19.10?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1837670
Title:
After clicking "104 more" in the overview Nautilus
Created attachment 159915
Breeze SVG icons in HiDPI screen (LO 6.4.2.2 in Ubuntu 20.04/Arch/Fedora 32)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1738774
Title:
Pixeled icons with LibreOffice 5.1
> Just updated to Version: 6.4.0.3 (x64) Build ID:
b0a288ab3d2d4774cb44b62f04d5d28733ac6df8
> First build since tracking the blurry/poorly rendered icons on high
dpi screens that I've seen the issue fixed.
Well, lucky you. I'm on Ubuntu 20.04, LO 6.4.2.2 (also tested this in
Arch and Fedora 32) a
@vanvugt the fix was already merged upstream.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1831161
Title:
App-switcher icons too small with hidpi monitor and 1.25 scaling
To manage notifications a
This seems to be very old. I'm not seeing this at all in Gnome 3.32,
Ubuntu 19.04, neither in mid-dpi screens (with fractional scaling or
font scaling) nor in retina like screens (with 2x scaling).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
Clicking on a bookmark starts a drag&drop operation that you have to
cancel pressing Escape. This happens both in nautilus and in the
standard file dialog. It happens also when using the touchpad.
Since bookmarks are an important and standard feature, having them
crippled to
As I commented upstream
(https://gitlab.gnome.org/GNOME/nautilus/issues/963#note_555977) this is
probably a bug in general touchpad support because is affecting other
apps and components in similar ways. I would close this or move it to
some other project (maybe libinput?).
--
You received this b
** Changed in: nautilus (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835794
Title:
Bookmarks unusable because clicks drag them
To manage notifications a
Also happens in X11 with Ubuntu 19.04. Often moving anything in the
desktop to trash restarts the shell or simply hangs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832124
Title:
Right-click file
Public bug reported:
Currently there is a simplified Settings view for the novice user.
I see no reason to force the advanced user to use Dconf editor when the
extension provides a really great configuration dialog accesible from
Tweaks.
Tweaks is not for the casual user (it's not even pre-insta
I'm closing this because after having read this great documentation on
the thought process and actual implementation of the Ubuntu dock I'm
convinced that you made the right decision:
https://didrocks.fr/2017/08/18/ubuntu-gnome-shell-in-artful-day-5/
** Changed in: gnome-shell-extension-dashtodoc
Public bug reported:
In an ubuntu session the default shell theme is Yaru. In a vanilla gnome
session the default shell theme is Adwaita. In both cases, there is no
way to pick the other shell theme. Of course, I agree with the defaults,
but arguably one might be interested in using Yaru in a vani
** Description changed:
In an ubuntu session the default shell theme is Yaru. In a vanilla gnome
session the default shell theme is Adwaita. In both cases, there is no
way to pick the other shell theme. Of course, I agree with the defaults,
but arguably one might be interested in using Yar
One additional consideration. Maybe one answer to my request could be:
Ubuntu desktop is opinionated, provide a few extensions and restricted
customization options, you're not supposed to change the gtk widget
theme, let alone the shell theme for mere consistency with widgets, and
if you want to do
I know that Daniel, that is not what I meant. The problem is that
Adwaita is not listed for an Ubuntu session and, conversely, Yaru is not
listed for a vanilla session, because both are "Default" and the meaning
of default is contextual to the session and neither of them are listed
under /usr/share
Thanks for you careful considerations, Daniel.
> Because you say "there is no way to pick the other shell theme" which
is simply untrue.
I'm not quite following you here, what I mean is that when you are in
Yaru shell theme you can't pick Adwaita shell theme (that is, the other
theme in the "Adwa
Oh, I now see why I was not following you. I don't think the "Default"
name to be a problem, quite to the contrary. What I don't like is the
inability to select the other (the non-default) theme. Even if you
renamed Default to Yaru, that won't make Adwaita appear. And if in a
vanilla session you re
Just to make it crystal clear. I now enter my Ubuntu session, go to
Tweaks and get this shell themes list:
(1)
Default
Materia
Materia-compact
Materia-dark
Materia-dark-compact
Materia-light
Materia-light-compact
Nevertheless, Adwaita shell theme IS installed in my computer. Hence I
would like to
This is affecting me too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1831476
Title:
gpaste extension is broken on ubuntu 19.04 (needs update)
To manage notifications about this bug go to:
https:
Public bug reported:
I've reported this upstream (https://gitlab.gnome.org/GNOME/gnome-
shell/issues/1370), but given that this is an important part of the
Ubuntu desktop and that you're providing some patches for improving the
X11 experience with hidpi monitors, I'm notifying about the issue here
I've changed `baseIconSizes` from the looking glass and I get bigger
icons. This doesn't seem to be hard to fix really. Maybe the size
restriction should be checked *before* scaling up 2x. Maybe bigger icons
should be allowed.
--
You received this bug notification because you are a member of Ubun
Public bug reported:
I've tried this in two different hidpi monitors with different scaling
configurations:
1) A 1920x1080 screen with scale factor 1x and font scale factor 1.25.
2) A 3000x2000 screen with scale factor 2x.
In the first one, icons are too small, I have to change:
this._iconB
I've reported this in github also: https://github.com/ubuntu/gnome-
shell-extension-appindicator/issues/181. I'm not sure which is the
better place since upstream = distro here.
** Bug watch added: github.com/ubuntu/gnome-shell-extension-appindicator/issues
#181
https://github.com/ubuntu/gnome
See my report https://bugs.launchpad.net/ubuntu/+source/gnome-shell-
extension-appindicator/+bug/1832793
Indeed PANEL_ICON_SIZE is the wrong way to compute the icon size.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
Public bug reported:
(I'm unsure about the right package to report this to)
The qt experience out of the box is currently a mess. Short of proper
Yaru integration, why not install qt5ct with consistent Ubuntu fonts and
icons and Breeze by default? Every qt app will work just fine with
Breeze. Cur
I can confirm this is still happening in Ubuntu 19.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723117
Title:
Desktop icons goes under the Dock, if the Dock is set to auto-hide.
To manage not
Public bug reported:
Currently the shift action is set to launch a new application, exactly
the same than the control action. If there is more than one window for
an app (say in position 1), then super+1 will open a preview to switch
between them, which is nice but has some shortcomings:
1) It's
This report seems surprising to me, I never had problems using the
ubuntu branch of the extension nor the upstream one in 19.04 (and I'm
using it since the release). A couple of coworkers are using ubuntu
19.04 with a fully functional dock also. I also have used arch and
fedora with gnome 3.32 and
Public bug reported:
Every time you click on a desktop icon to do something (open it, open
the menu context, etc) the icon gets selected and the selection won't
disappear until you click elsewhere in the desktop. The behavior is
against the usual expectation that the thing gets selected just to ca
Public bug reported:
See details in my upstream report: https://github.com/micheleg/dash-to-
dock/issues/963
Also reporting here because it affects configurations supported by
Ubuntu.
** Affects: gnome-shell-extension-dashtodock (Ubuntu)
Importance: Undecided
Status: New
--
You r
Sorry, I realized the screenshot might be misleading: the "carlos" icon
(the one selected) is the one matching "Home" in Nautilus, the "home"
icon is just a folder with that name that happens to be un my Desktop
folder.
--
You received this bug notification because you are a member of Ubuntu
Bugs
Hi Sebastien:
* Ubuntu 19.04
* Session: ubuntu desktop (quite pure, the dock in the screenshot has just been
made to shrink but it's still the builtin one).
Nevertheless, as far as I can remember, this consistently happened every time I
used the desktop icons extension in the past, both in Fed
1 - 100 of 114 matches
Mail list logo
