quot;in-progress" to match that.
** Changed in: malcontent (Ubuntu)
Status: New => In Progress
** Changed in: malcontent (Ubuntu)
Assignee: Christian Ehrhardt (paelzer) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bu
** Changed in: malcontent (Ubuntu)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to malcontent in Ubuntu.
https://bugs.launchpad.net/bugs/1892456
Title:
[MIR] malcont
Nautilus Problem, möglich.
Kernel problem, halte ich für unwahrscheinlich aber nicht unmöglich.
Sicher ist allerdings das ohne Nachvollziehbare Schritte hier leider
keine weiterhelfen kann.
Ich aktualisiere den Fall dazu passend, aber ohne weitere Info wird
leider nichts mehr passieren.
P.S.
For anyone who's struggled to use the task switcher since 22.04 and
until this is finally fixed, a reasonably painless workaround is
available: https://askubuntu.com/a/1492396/145568
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
I managed to "solve" this problem by deleting the complete
~/.config/dconf/user file and reinstall every gnome extension i had
installed. Now i can start gnome on wayland, but also had to do again
every customisation i had. (Not sure if removing every extension was
necessary)
also see in:
Public bug reported:
Hello Ubuntu community,
I recently upgraded my system from Ubuntu 23.04 to 23.10 and since then
(1 Week) I've had problems starting GNOME under Wayland. Here are the
details of my system and the steps already taken:
System information:
Device: MS Surface Pro 5 (Intel Iris
Public bug reported:
Nautilus displays a big directory symbol alongside the message
"directory is empty" [or something to that effect] for empty
directories. However, it does not differentiate at all between
directories that are truly empty, and directories that contain only
hidden files and
FYI Undocked with just the laptop screen it does not trigger the issue.
But docking the running system to initialize all additional screens
makes it trigger up again once I leave into the activities screen (as
described before).
--
You received this bug notification because you are a member of
Considering it impossible to work with a system hanging every few hours
I debugged this over the weekend a few times, but sadly to no further
insight. Eventually I've given up and re-deployed Mantic on the system
trying to either "help by verifying the issue still exists" or "getting
out of it".
FYI: Since the signature of bug 2035016 is quite similar I checked, but
I already have the mutter components on 45.0-2ubuntu1.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
I see the same on Jammy, like the others it is reproducible easily by hitting
the meta key and exiting from there in any way (hit ESC, select anything to
start, ...).
Sadly setting fixed workspaces (10) did not work around the issues for me, like
it did for others.
Occasionally (seems to
Workaround: apt install lightdm lightdm-gtk-greeter.
Works OOTB for me, with the very big caveat that screen locking will be
disabled (that requires gdm).
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
with preexisting evolution configuration is
affected, in other user accounts on the machine (without evolution configured),
configuration wizard starts normally.
Any help is greatly appreaciated as I do'nt seem to be able to solve
this for me.
Greetings,
christian
--
You received this bug notification
as I first wanted to see whether others are facing this,
too, but as for now, I have no idea how to solve this.
Thanks for any help in advance!
christian
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution in Ubuntu.
https
Found the cause:
gsd-rfkill[2049]: Could not open rfkill device: Could not open RFKILL
control device, please verify your installation
GNOME's BT GUI needs access to /dev/rfkill to work. It's tagged
"uaccess" in udev, so in theory all logged-in users should get access
via an ACL, but in practice
Public bug reported:
I've set up a second seat via loginctl --attach, resulting in the
following udev rules:
TAG=="seat", ENV{ID_FOR_SEAT}=="drm-pci-_6e_00_0", ENV{ID_SEAT}="seat1"
TAG=="seat", ENV{ID_FOR_SEAT}=="input-pci-_6c_00_0-usb-0_11_1_0",
ENV{ID_SEAT}="seat1"
TAG=="seat",
Public bug reported:
I've set up a second seat via loginctl --attach, resulting in the
following udev rules:
TAG=="seat", ENV{ID_FOR_SEAT}=="drm-pci-_6e_00_0", ENV{ID_SEAT}="seat1"
TAG=="seat", ENV{ID_FOR_SEAT}=="input-pci-_6c_00_0-usb-0_11_1_0",
ENV{ID_SEAT}="seat1"
TAG=="seat",
Public bug reported:
When a second seat is set up via loginctl --attach, the greeter will not
come up on the second screen unless WaylandEnable=false is set in
/etc/gdm3/custom.conf (and gdm restarted).
For completeness' sake, the udev rules set up by loginctl are:
TAG=="seat",
Public bug reported:
In 22.04's default theme, it's almost impossible for me to make out
which app or window is the currently selected one in the window switcher
(alt-tab) or the application switcher (super-tab). The "highlighted"
item is just a slightly different shade of grey. I mean, I can
If it would be an MP I'd set it to needs-information, but this is a debdiff in
a bug.
I hope my questions and confusion was clear so that you can iterate and clarify.
I'll remove ubuntu-sponsors which I'll ask you to add back once this is
ready for review again.
--
You received this bug
Then the most recent applied patch says:
...
Since this is a helper service that is meant to be controlled by
"tracker-miner-fs", the install section shouldn't exist, as it allows
the service to enabled, meaning that its execution would be
controlled by systemd.
But I can't see where/how:
Some things just do not fit together.
You write
"... to update from default.target.wants to gnome-session.target.wants. ..."
But while 3.4.3-1ubuntu1 does:
+ [Install]
+-WantedBy=default.target
++WantedBy=gnome-session.target
Then later 3.4.3-1ubuntu2 does
+-[Install]
+-WantedBy=default.target
This is now the third revision of the change (3.4.3-1ubuntu1 + 3.4.3-1ubuntu2 +
this) and by identifying that this also needs to go to -devel I wonder if you
should not also use the chance to submit the outstanding Delta to Debian. That
will help them directly and mid-term ease maintenance.
I can see why you do the purge forgetting the old state to enable them as if
they were freshly installed.
I'm not sure how SRUable that will be afterwards as it is affecting behavior if
someone has set something else than the default. But for now, going forward to
mantic I agree that it will
Thanks for the clarification Matthew and Heitor - first I'll re-set the state
of the devel release then.
As it isn't completely fixed there.
** Changed in: tracker-miners (Ubuntu)
Status: Fix Released => Confirmed
** Changed in: tracker-miners (Ubuntu Lunar)
Status: Fix Released
There has been not further update for too long, for now we consider it invalid.
Feel free to re-open if there is effort backing it up and motivation to bring
it to main.
** Changed in: flatpak (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a
** Also affects: gtk+3.0 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2000739
Title:
Window actions (like maximize) no more
I have the same problem - any ongoing solutions ?
You can override the problem with a second plugged mouse too, if you
move it only one pixel at after startup the mousepointer appears and
stay until shutdown.
Maybe the problem is to initialise the pointer when using wacom ?
The Wacom pointer is
Same behaviour on Ubuntu 22.04.1 LTS with nemo 5.2.4-1 ...
The files seem to be moved there if you delete a directory of yours with files
from other users in it from the trash.
Proposal for behaviour changes:
1. Not create and use the "expunged" folder at all and just fail to delete
other
Public bug reported:
```
GNU Image Manipulation Program version 2.99.12
git-describe: GIMP_2_99_12
Build: unknown rev 0 for linux
# C compiler #
Using built-in specs.
COLLECT_GCC=/usr/bin/cc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/11/lto-wrapper
@ausbin: `aa-complain` is hardly a "fix": it bypasses AppArmor, which is
not optimal, knowing how PDF documents are often used as a malware
vector. Admittedly, malware is less likely to be targeted at Linux
desktops but still...
--
You received this bug notification because you are a member of
AFAIU https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1812456
needs to be completed to unblock this one here as well.
There is a discussion between Security and others - but that seems stalled for
almost a year now.
Maybe worth to ping there (or the involved people) to get it back on
Running APT evince 42.1-3 on stock Ubuntu 22.04/GNOME 42.0/Wayland.
My issue is Evince opening in a tiny window every time it's fired off;
this deployment was upgraded from 21.10, which didn't suffer from such
issue.
I attach below the output from `journalctl -f` while starting up Evince,
which
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1969896
Title:
Evince Document Viewer(42.0) does not remember last page in 22.04 and
opens in a tiny window when launched
To manage
Public bug reported:
This bug seems like #1826543, but I fled a new one because it is a
regression from 21.10.
While writing this, I also noticed that other elements only follow the
primary display scaling, like the numbers on the top left that say which
display is which, and the pop-up that
Public bug reported:
Whenever I try to select a different window from the dock (or add to
favourites/any other option in that menu), as soon as my mouse leaves
the dock for that menu, the dock hides, which makes the menu drop down.
This is very frustrating because at best I have to try again, and
Ok, it is there now:
https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.html
gnome-bluetooth3: gir1.2-gnomebluetooth-3.0 gnome-bluetooth-3-common
libgnome-bluetooth-3.0-13 libgnome-bluetooth-3.0-dev libgnome-bluetooth-doc
libgnome-bluetooth-ui-3.0-13
I can't test this reliably (as stated in the SRU description), but at
least I can say I haven't seen it in the last 24h :-) I think this is on
@gjolly to try to reproduce it in the mentioned azure test environment.
--
You received this bug notification because you are a member of Ubuntu
Desktop
I'm on Ubuntu 20.04 with gnome-calendar 3.36.2 and have the same problem:
Google calendar did not sync.
Then I removed the cache in "~/.cache/evolution/calendar/", and gnome calendar
showed no appointments at all (as expected).
Clicking the "sync now" menu item changed the calendar icon briefly
FYI the re-upload of a fuse3 open-vm-tools happened yesterday and it migrated
to jammy-release.
Any issues with the images?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1956949
@aakef - while I said unionfs-fuse might not be a blocker I'd still
recommend to upload the change switching to fuse3. On comment #12 it
seemed you are close. Any chance to get this done or did unexpected
blockers show up while trying?
The unionfs-fuse task here is assigned to Graham; @ginggs -
FYI according to
https://people.canonical.com/~ubuntu-archive/germinate-output/ubuntu.jammy/rdepends/ALL/fuse
https://people.canonical.com/~ubuntu-archive/germinate-output/ubuntu.jammy/rdepends/ALL/fuse3
This should no more be an issue now, so open-vm-tools will switch to
fuse3 again in the next
Hi Bernd,
I'm glad to heard that as we were not sure it would work well with fuse3.
As a reminder, the libs are co-installable it is "bin:fuse" vs "bin:fuse3" that
are conflicting.
So when you change that remember to also change fuse->fuse3.
In the meantime it was found that unionfs-fuse isn't
FYI - I uploaded a revert to the open-vm-tools change to un-block image builds
for now.
But maybe this was a good wake-up call.
Please have a look at gvfs, union-fuse (here) and grub2, s390-tools, snapd,
xdg-desktop-portal in bug 1934510.
--
You received this bug notification because you are a
@Marco Trevisan - I subscribed you in case you want to steal the Desktop
POV to this from Didier.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1956949
Title:
CPC AWS jammy builds
Also see
https://bugs.launchpad.net/ubuntu/+source/fuse3/+bug/1934510/comments/24
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1956949
Title:
CPC AWS jammy builds fail with: "fuse3
raham Inggs (ginggs)
** Changed in: open-vm-tools (Ubuntu)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1956949
Title:
CPC
FYI triggered again for me due to unattended upgrades.
The time in the journal when things go down matches the
unpack/configuee/install phase of
- accountsservice:amd64 0.6.55-0ubuntu12~20.04.5
- libaccountsservice0:amd64 0.6.55-0ubuntu12~20.04.5
- dbus:amd64 1.12.16-2ubuntu2.1
I - again - had
Public bug reported:
Hi
My desktop crashed and sent me back to login page. After input my
password display switched black again and then showed login screen. Just
reboot fixed my problem.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.9-0ubuntu0.20.04.2
As outlined in #55 unless we identify a smaller set of fixes I'm unsure
what we could do for Focal.
I'm out of ideas, the only one good thing is that it seems better in
later versions and got more rare. But I hate when I do not understand
all of a problem, here I might need help from
Mitigated in impish Steve via
https://launchpad.net/ubuntu/+source/xrdp/0.9.15-1ubuntu1
** Changed in: xrdp (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to xrdp in Ubuntu.
Also blocking isc-dhcp now, added a task
** Also affects: isc-dhcp (Ubuntu)
Importance: Undecided
Status: New
** Changed in: isc-dhcp (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
Public bug reported:
Hi,
as seen in
https://launchpadlibrarian.net/536144995/buildlog_ubuntu-impish-ppc64el.xrdp_0.9.15-1_BUILDING.txt.gz
https://launchpadlibrarian.net/536175263/buildlog_ubuntu-impish-s390x.xrdp_0.9.15-1_BUILDING.txt.gz
This currently fails to build on ppc64el and s390x.
As I said I tried to recreate this, but it worked.
It was fine under Focal/5.4.0-53-generic Host with the Impish-armhf container.
Upgrading the host to impish it Impish/5.11.0-16-generic still works fine.
It seems it only fails in autopkgtest infrastructure, not sure why yet
:-/
--
You received
Public bug reported:
Systemd 248.3-1ubuntu1 is rather new, but had 5 successful tests on armhf
before now slipping into a bad mode.
Now it seems all tests failed in boot-and-services by hanging until killed by
VirtSubproc.Timeout of autokgtest.
The last [1] test log has a bit more, it shows a
I was adding a few of the blocked packages as incomplete tasks to have
this bug update-excuse show up in excuses. Right now until we know
better I'd consider this a systemd issue.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3
bug 1922034 is gnome-terminal specific. The upstream issue was
https://gitlab.gnome.org/GNOME/mutter/-/issues/1723.
But this bug is generic for any Wayland client. And it also has been
fixed in the 3.38 release.
Now, this very issue is tagged "fixed-in-3.36.8" which is not correct I think.
At
I don't know why exactly, but I t seems to work again after I installed
telepathy-salut_0.8.1-5ubuntu1_amd64.deb from xenial. This package does
not exist in 20.04?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to empathy in Ubuntu.
Thank you for your help!
ubuntu-desktop was indeed not installed, probably because I removed one
of the dependent packages at one time because I did not want it.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in
It does indeed!
I wonder why this was not installed automatically.
Also, the title bars of Firefox , Thunderbird and Slack (Electron
Desktop) are white when using the "Standard" colors, but text editor,
control center + terminal have dark title bars. But this is probably a
different issue.
--
Clicking the themes in control center does change the gtk-theme setting.
It only does not modify anything layout-wise :)
$ dpkg -l | grep yaru
ii yaru-theme-gnome-shell 20.04.10.1 all Yaru GNOME Shell desktop theme
from the Ubuntu Community
Original setting:
$ gsettings get
Public bug reported:
Interactively resizing a Wayland window while it resizes itself results
in the window jumping out of the screen. This happens on GNOME Shell and
pure mutter on the 3.36 branch but has been resolved on newer versions
(3.37.1 onwards).
See
I did install Ubuntu 10.04 over ten years ago from a CD-Rom.
Maybe I once uninstalled the permanent dock, maybe it never was the in 16.04 or
18.04.
I did install the dock, but that changes nothing in regard to my
problem.
Attached is the log file.
** Attachment added: "jourctrl -b 0 > log"
I updated via focal-proposed to mutter and gnome-shell version 3.36.9
(3.36.9-0ubuntu0.20.04.1) but unfortunately my original issue reported
at https://gitlab.gnome.org/GNOME/mutter/-/issues/1700 still persists.
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1700
I'm using the official Gnome Shell packages. I don't know if it has a
dock; but the left-side menu with the favorite applications is visible
when clicking the top left "application" button.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
Apart from one line there seem to be no relevant log lines:
> No Ubuntu Dock is installed here. Panel disabled. Please fix your
installation.
** Attachment added: "journalctl-appearance.log"
Ping - how can I help track down this problem? I need telepathy-salut to
work. This package seems to have been removed - but is replaced with
what?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to empathy in Ubuntu.
Public bug reported:
When clicking on one of the "window colors" (Light, Standard, Dark) in
the Appearance section of gnome control center, nothing changes.
The window background stays light, the top window bar stays light.
Using gnome tweaks tool to change the appearance works, and then
A bit unrelated, but the reason that there is no "nautilus-dbgsym" for
the updated nautilus package (version 1:3.36.3-0ubuntu from "focal-
updates") is that the dbgsym index for the released version ("focal")
at:
http://ddebs.ubuntu.com/dists/focal/main/binary-amd64/Packages
shows the
After installing that dbgsym package, I still do not get a backtrace. It
just exits with "[Inferior 1 (process 116937) exited with code 01]" so
maybe it does not crash but the failed assertion makes it just quit?
Also, there is nothing in "/var/crash" which is another indicator that
the process
I have the ddebs sources added:
deb http://ddebs.ubuntu.com focal main restricted universe multiverse
deb http://ddebs.ubuntu.com focal-updates main restricted universe multiverse
deb http://ddebs.ubuntu.com focal-proposed main restricted universe multiverse
But the dbgsym version does not match
Public bug reported:
nautilus crashes when I try to create a symbolic link via drag and drop:
1. open an arbitrary folder in nautlus
2. hold 'Alt' and drag and drop a file
3. a context dialog will open with options to move, copy or link the file
4. chose any option
Choosing any option (even
I believe that this is the same issue that causes crashes for me in some
situations where a Wayland surface is committed without a window
geometry.
The upstream bug https://gitlab.gnome.org/GNOME/mutter/-/issues/1739
includes a backtrace of the crash on the "gnome-3-36" branch. So this
issue will
It would be helpful to also update the packages "mutter-dbgsym" and
"libmutter-6-0-dbgsym" to the corresponding point/patch versions.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
BTW, I purged/reinstalled empathy. Did not help.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to empathy in Ubuntu.
https://bugs.launchpad.net/bugs/1888399
Title:
After Update->20.04, Empathy/Salut stops working
To manage
Is there anything I can post here to fix this bug? What else information
do you need?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to empathy in Ubuntu.
https://bugs.launchpad.net/bugs/1888399
Title:
After Update->20.04,
** Merge proposal unlinked:
https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/399966
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1916705
Title:
I am a bit confused about the version scheme here. My "About" page in
the settings says I am already on GNOME Version 3.36.8, but the mutter
version is 3.36.7 and the gnome-shell version is 3.36.4.
How is this "GNOME Version" determined? Shouldn't all the GNOME packages
be on the same version
open-vm-tools fixed in
open-vm-tools (2:11.2.5-2ubuntu1) hirsute; urgency=medium
* d/p/fix-FTFBS-glib2.0-2.66.3.patch: fix FTBFS with glib2.0 >=2.66.3
-- Christian Ehrhardt Mon,
Public bug reported:
This is a request to update mutter to version 3.36.8 to fix various
issues that have been fixed upstream.
See https://gitlab.gnome.org/GNOME/mutter/-/issues/1700#note_1058654 for
the original mutter issue report that will be fixed by 3.36.8.
ProblemType: Bug
DistroRelease:
Forwarded to upstream open-vm-tools as
https://github.com/vmware/open-vm-tools/issues/500
Uploaded a fix for Ubuntu in
https://launchpad.net/ubuntu/+source/open-vm-tools/2:11.2.5-2ubuntu1
** Bug watch added: github.com/vmware/open-vm-tools/issues #500
Thanks Iain for the Fixes in glib.
I need to sort out how to adopt that in qemu for now ...
Also open-vm-tools is also FTBFS by this, so I need to add a task and work on
that as well.
** Also affects: open-vm-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
I am experiencing this issue on two laptops with 20.04.2. But I just
verified that it indeed works as expected with a Live ISO inside a VM.
Is there a way to debug this?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in
Public bug reported:
When extracting ZIP archives from within nautilus (e.g. right-click ->
"Extract Here") the extracted file structure is missing subfolders.
Reproduce:
1. download a ZIP archive that includes files and folders in the root (e.g.
Public bug reported:
qemu now breaks in Hirsute (it didn't 23h ago)
Broken:
https://launchpadlibrarian.net/524654684/buildlog_ubuntu-hirsute-amd64.qemu_1%3A5.2+dfsg-6ubuntu1_BUILDING.txt.gz
Good before:
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4471/+packages
Error:
This bug is still present in Ubuntu 20.10 / Gnome 3.38. This is a huge
issue especially in corporate environments.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/49579
Interesting thanks Jakub, 0.38 is in groovy and later
spice-gtk | 0.37-2fakesync1 | focal/universe | source
spice-gtk | 0.38-2ubuntu1 | groovy/universe | source
spice-gtk | 0.38-2ubuntu1 | hirsute/universe | source
But being a protocol change [1] I'm unsure we can SRU this to Focal
This seems to be fixed!
--
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/199
Title:
Window tiled to monitor where most of the window is in instead of
where the mouse is.
To
This is still an issue on Ubuntu 20.10, while the GNOME Shell remote-
desktop / screencast support on Wayland has been enabled for Fedora and
other distributions for some time now.
What is Ubuntu holding back from enabling Wayland remote-desktop support
(and consecutively a Wayland-by-default
Issue id is 3290.
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3290
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3290
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3290
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
Public bug reported:
Release: Ubuntu Groovy Gorilla (development branch) 20.10
Package version: 3.38.1-1ubuntu1
When I tile windows using edge tiling, I want the window to tile on the
same edge that I brought it to, however, if the window is mostly in
monitor 1 when I try to tile it to the left
** Bug watch added: Red Hat Bugzilla #1413858
https://bugzilla.redhat.com/show_bug.cgi?id=1413858
** Also affects: wayland-protocols (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=1413858
Importance: Unknown
Status: Unknown
--
You received this bug notification because
Since so many components are involved a fix/change might have been missed.
And since I recently didn't hear anything about this otherwise rather hot bug I
was giving focal a try.
It turns out that this was indeed improved. Only the user of pkg:ifmail user
fdt name "Fidonet" is still visible.
There were no extensions in:
'/home/paelzer/.local/share/gnome-shell/extensions': No such file or directory
I already disabled them via gnome-tweaks before, but doing so again the
ways you asked me to do that.
Getting back to the config showed a few of them enabled indeed, maybe that was
That was it, thanks Daniel!
Now I need to restore as much of my config as possible without breaking
it again ...
--
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/1896188
Title:
apport information
** Attachment added: "GsettingsChanges.txt"
https://bugs.launchpad.net/bugs/1896188/+attachment/5412103/+files/GsettingsChanges.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
Now the description is complete in regard to all things worth to try that came
to my mind.
Also the apport data as well as the video is attached.
Setting back to new for re-review by the Desktop Team.
P.S. is the overlay an application on it's own that I could try to kill from a
console?
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1896188/+attachment/5412105/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
The video shows:
00:09 - opening the "Show Applications" overlay works fine at first.
00:14 - searching an application in there works
00:16 - I open gedit and would expect to get back onto the desktop.
But I can't it sticks within the overlay.
I tried to hit the "Escape" key, clicking on
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1896188/+attachment/5412104/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
1 - 100 of 1295 matches
Mail list logo
