Hey,
I agree, this should be equally fine to be promoted on Noble as well.
None of the critical elements are different.
Please land the addition of a matching Extra-Exclude in the noble branch
of the seeds before doing so.
** Also affects: malcontent (Ubuntu Noble)
Importance: Undecided
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.
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
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
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
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
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
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
** 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:
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,
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
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:
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
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.
apport information
** Attachment added: "monitors.xml.txt"
https://bugs.launchpad.net/bugs/1896188/+attachment/5412107/+files/monitors.xml.txt
** Description changed:
Hi,
this must sound odd, but to me most Desktop bugs do :-/
The issue:
- If I hit the meta key the usual "search
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1896188/+attachment/5412102/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
apport information
** Attachment added: "ShellJournal.txt"
https://bugs.launchpad.net/bugs/1896188/+attachment/5412106/+files/ShellJournal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
Hi Daniel, I'm on it ... :-)
Video just completed - I already wrote that I'll attach one.
And I separated the "potentially related, but other issues" into an
extra section for exactly the reason of keeping this bug to one issue,
but at the same time I want/need to provide all info that might be
** Description changed:
Hi,
this must sound odd, but to me most Desktop bugs do :-/
The issue:
- If I hit the meta key the usual "search app" overlay appears.
- I search for an application and start it
- the overlay does NOT disappear anymore
- the miniature images of the just
** Summary changed:
- Overlays do not refresh anymore and get the desktop stuck
+ GTK Overlays do not refresh/exit and get the desktop stuck
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
** Description changed:
Hi,
this must sound odd, but to me most Desktop bugs do :-/
The issue:
- If I hit the meta key the usual "search app" overlay appears.
- I search for an application and start it
- the overlay does NOT disappear anymore
- the miniature images of the just
** Description changed:
Hi,
this must sound odd, but to me most Desktop bugs do :-/
The issue:
- If I hit the meta key the usual "search app" overlay appears.
- I search for an application and start it
- the overlay does NOT disappear anymore
- the miniature images of the just
On backup I had:
mv: cannot stat '.gnome2': No such file or directory
mv: cannot stat '.gconfd': No such file or directory
mv: cannot stat '.metacity': No such file or directory
but worked for the rest
Also disabled all extensions (didn't have any active, but can't hurt)
Restarting into that now
Trying hard reset of my config via:
$ mkdir -p ~/.backup-gnome-config/ && for f in .gnome .gnome2 .gconf .gconfd
.metacity .config/dconf; do mv $f ~/.backup-gnome-config/; done
$ gnome-tweaks
# then reset to defaults
--
You received this bug notification because you are a member of Ubuntu
** Description changed:
Hi,
this must sound odd, but to me most Desktop bugs do :-/
The issue:
- If I hit the meta key the usual "search app" overlay appears.
- I search for an application and start it
- the overlay does NOT disappear anymore
- the miniature images of the just
** Description changed:
Hi,
this must sound odd, but to me most Desktop bugs do :-/
The issue:
- If I hit the meta key the usual "search app" overlay appears.
- I search for an application and start it
- the overlay does NOT disappear anymore
- the miniature images of the just
Public bug reported:
Hi,
this must sound odd, but to me most Desktop bugs do :-/
The issue:
- If I hit the meta key the usual "search app" overlay appears.
- I search for an application and start it
- the overlay does NOT disappear anymore
- the miniature images of the just started app seems
And on Bionic we only need to do so for amd64
Here is a new MP for Bionic:
https://code.launchpad.net/~paelzer/britney/hints-ubuntu-bionic-disable-systemd-v2/+merge/390793
** Branch linked: lp:~paelzer/britney/hints-ubuntu-bionic-disable-
systemd-v2
--
You received this bug notification because
The problem with Xenial is that there it isn't just flaky "systemd-
fsckd" much more seems to be broken. I'll revise my Bionic MP, but for
Xenial I'd like to hear from ddstreet/rbalint how they think we should
go on there ...
--
You received this bug notification because you are a member of
Focal test hint was accepted tonight and things moved there.
@Kelsey - Steve denied the hint as a reset since recently a few results were
good.
Maybe you want to submit the same as force-badtest and bring it up like that
for X?
The results for xenial really look similarly bad ...
xenial
** Branch linked: lp:~paelzer/britney/hints-ubuntu-focal-disable-systemd
--
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/1892358
Title:
autopkgtest success rate dropped inhibiting
Thanks rbalint for pointing me to the other bug for the s390x fail we see now.
I'll continue there and consider the Groovy portion of this one closed again.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
Groovy
It seems this isn't over for groovy, it was mentioned that the issues in the
subtest "tests-in-lxd" would be related to some fstab issues in those issues.
But recently all architectures, but s390x recovered. I assume that the fstab
issue is fixed but something else surfaces now.
groovy
[15:17] ddstreet: any updates on 1892358?
[15:18] @paelzer sorry not yet, i'll have systemd ready for upload
next week including fixing the autopkgtests
[15:21] ok
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
@ddstret - any update how to proceed?
If you have no time yet, then the MPs to ignore the fail until we have a new
version are up - just ack them and I guess the SRU Team will follow.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
If not going for marking the subtest flaky as in groovy, I have prepared
force-reset-test as alternatives in:
-
https://code.launchpad.net/~paelzer/britney/hints-ubuntu-focal-disable-systemd/+merge/390005
-
To match the open packages blocked on this in active releases I added
linux-meta for BIonic (thanks Kleber for the hint) and Focal (Thanks
Kelsey for the hint).
I think all of those had enough of retry-until-success and I'd ask again
for how we should proceed there. Masking/Resetting the test via
Util-linux SRU in Focal blocked as well, updating tags.
** Also affects: util-linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: util-linux (Ubuntu Focal)
Status: New => Confirmed
** Changed in: util-linux (Ubuntu)
Status: New => Invalid
--
You received
True @Kleber, here the stats of Bionic - at least on x86 you seem to
have barely a chance.
bionic
amd64
boot-smoke (F 40% S 0% B 0% => P 60%/)
...F.FFF.FF.FF..
upstream (F 5% S 0% B 0% => P 95%/)
..F.
systemd-fsckd
Here an (monospace) overview of recent focal tests.
focal
amd64
networkd-testpy(F 5% S 0% B 5% => P 90%/)
.B...F..
boot-and-services (F 5% S 0% B 5% => P 90%/)
.B...F..
upstream (F 5% S 0% B 5% =>
https://launchpad.net/ubuntu/+source/systemd/246.2-1ubuntu1 is still in
proposed and I was looking forward to a bunch of custom triggers this
morning.
But I found everything migrated this morning despite those new tests not being
done.
What is left is the similar situation in Focal (as mentioned before).
I have updated the tasks to reflect that properly and get update-excuse tagging
there.
In Focal it is currently blocking qemu and build-essential SRUs and I
wanted to ask if the plan is to do the same upload+test-reset there
[16:34] seb128, cpaelzer ahasenack sorry, i was out and apparently
forgot setting that in my email. the last systemd upload should fix everything
except for the livecd-rootfs revert that made fstab in lxd images invalide
[16:45] rbalint: " the last systemd upload" means groovy I guess,
what
Adding glib2.0 as it had a rebuild for libffi and will be blocke dby
this as well.
** Also affects: glib2.0 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: glib2.0 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of
The last two updates went smooth for me, not triggering it.
I'm still too afraid to "just update while working" as I did in the past since
it could drag things down thou :-/
I was feeling like this could be solved, but reading that Steve is also
affected I'm worried that I might just not hit the
xxhash was a code split from a package already in main and already promoted in
Disco/Eoan.
It came back now as dependency for rsync and (thanks Steve) Foundations is
subscribed to cover it.
Can be promoted to main in groovy
** Changed in: xxhash (Ubuntu)
Status: Incomplete => In
FYI: As mentioned int he MIR Team meeting, since doko had to run I've
sent a mail to vorlon asking if foundations is going to adopt it.
** Changed in: xxhash (Ubuntu)
Assignee: (unassigned) => Steve Langasek (vorlon)
--
You received this bug notification because you are a member of Ubuntu
I hit that again today on an upgrade.
Network manager didn't come up again.
Mai 20 11:04:46 Keschdeichel systemd[1]: NetworkManager.service: Unexpected
error response from GetNameOwner(): Connection terminated
Mai 20 11:04:46 Keschdeichel NetworkManager[1330]: [1589965486.9491]
caught
There are plenty of components involved in "trying" to fix this by spice
upstream.
The discussion in
https://gitlab.freedesktop.org/spice/linux/vd_agent/-/issues/9
is rather long.
It eventually seems to be fixed in
https://gitlab.freedesktop.org/spice/linux/vd_agent/-/merge_requests/4
I think
Since Daniel split up the "related but not the same" mutter changes to
bug 1852183 (thanks for that work BTW!) let us here focus on the spice
component.
Thanks lwk32 for identifying a fix for that, I'll be taking a look if
that is SRU-safely backportable to Focal.
** Also affects: spice-vdagent
> Thank you. Did you try it on Ubuntu or Kubuntu host?
Host was Ubuntu
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1872527
Title:
Clipboard doesn't work 100% of the time in
I can't recreate this on a 20.04 host neither with virt-manager open or not.
Only in the guest.
I tried editor (gnome) and kate (KDE editor) on y gnome based 20.04.
Very awkward issue, I hope my video helps and I'm looking forward to
what Desktop people say as well.
--
You received this bug
Here is an example,
- on the bottom you see keys pressed (all arrive int he guest)
- on the right you see xclip looped as shown in comment #2
- on the left you see the editor
I add a few lines of text in the editor to explain what is going on.
@John - does that somewhat match what you are
@Desktop Team:
For its similarity with bug 1852183 I'll start with `mutter`, but please
re-triage this to where you think this really belongs.
** Tags added: champagne
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in
Same happening for me, with two rows of screens, three on top two in the bottom
row.
Primary is top left.
** Attachment added: "Screenshot_20200408_130437-search-bar-half-visible.png"
Overview of the affected layout
** Attachment added: "Screenshot_20200408_132041-layout.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869571/+attachment/5349459/+files/Screenshot_20200408_132041-layout.png
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1869571 ***
https://bugs.launchpad.net/bugs/1869571
** Attachment added: "Screenshot_20200408_132041-layout.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1871607/+attachment/5349457/+files/Screenshot_20200408_132041-layout.png
** This
*** This bug is a duplicate of bug 1869571 ***
https://bugs.launchpad.net/bugs/1869571
[13:14] cpaelzer, what screen resolution/scaling factor/video
card do you use?
That would be:
eDP-1 connected primary 1920x1080+0+840 (normal left inverted right x axis y
axis) 344mm x 193mm
DP-1
** Attachment added: "Screenshot_20200408_130437-search-bar-half-visible.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1871607/+attachment/5349456/+files/Screenshot_20200408_130437-search-bar-half-visible.png
--
You received this bug notification because you are a member of
Public bug reported:
Hi,
since the upgrade to Focal I wonder why the "activities" overview isn't
readable anymore.
It is the one you get to when you click "activities" in the top let or hit the
"meta" key.
In my case this preview is only half an icon high, so I have to assume
what things are
Sure @seb128 - I'll let you know if it happens again (as I did a
cleaning-reboot now).
--
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/1871538
Title:
dbus timeout-ed during an
> could you add the journalctl log from that session, that might include
some hints
Sure attached here, you see in the initial report and the later comments
the time indexes to look out for.
Also FYI for the rtkit issue that you will see in there => bug 1871543
** Attachment added:
> Also do you have any gnome-shell/gdm crash collected in /var/crash?
No, just these:
$ ll /var/crash/*.crash
-rw-r- 1 paelzer whoopsie 3589735 Apr 6 08:34
/var/crash/_usr_bin_gnome-clocks.1000.crash
-rw-r- 1 paelzer whoopsie 53170176 Apr 8 10:36
> 1. Look in /var/crash for crash files and if found run:
>ubuntu-bug YOURFILE.crash
> Then tell us the ID of the newly-created bug.
Again, they all seem to be prior or follow on issues, but they already
have IDs in the error tracker.
/var/crash/_usr_bin_gnome-clocks.1000.uploaded
Hi Daniel,
none of the crashes that I had has the same signature as those that are
reported on the dup.
Furthermore as I outlined the crashes seem to be secondary issues after
soemthing breaks and recycles gnome-shell.
I'd ask for re-triage as that doesn't seem to be the same thing to me.
**
1 - 100 of 136 matches
Mail list logo