** Package changed: unattended-upgrades (Ubuntu) => webkit2gtk (Ubuntu)
** Changed in: webkit2gtk (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to webkit2gtk in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: evince (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
** Changed in: gdm3 (Ubuntu)
Status: New => Incomplete
** Changed in: gdm3 (Ubuntu Focal)
Status: New => Incomplete
** Changed in: gdm3 (Ubuntu Impish)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is
-1 on doing the rename before the LTS, we are past feature freeze, a
check on the old name shows quite some reverse depends call to the name
to trigger the settings
https://codesearch.debian.net/search?q=org.gnome.ControlCenter
We could start patching the rdepends but that's not useful work, we
** Description changed:
Long press/touch a directory won't trigger the context menu for it.
OS: 22.04, up to date @ Mar 8, 2022.
nautilus: 1:42~beta-1ubuntu1
+ mode: wayland
With a touch monitor, it will be useful if we can do more operation with
it.
If I long press a file
** Tags added: block-proposed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to webkit2gtk in Ubuntu.
https://bugs.launchpad.net/bugs/1964132
Title:
[FFe] webkit2gtk additionally built with libsoup3 support
Status in webkit2gtk package
Here's a better list of affected packages:
https://codesearch.debian.net/search?q=gnome-control-center.desktop=1
The network-manager plugins are for AppStream metadata and it's pretty
easy to support both names there.
budgie-control-center can be ignored since it's just a fork of gnome-
I am using ubuntu 18.04 in docker environment and running swtbot tests using
eclipse. I get the same error.
I updated my docker file to install libx11-6 but the problem still exists. The
tests execution is aborted with the following error message
[xcb] Unknown sequence number while processing
Public bug reported:
Request
---
Add the new libsoup3-using packages in webkit2gtk
Why Needed
--
Our webkit2gtk packaging is built with libsoup2 (webkitgtk's 4.0 API). Debian's
packaging recently added additional packages built with libsoup3 (webkitgtk's
4.1 API); these should not
Jeremy pointed out https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=1003907 which could be similar
** Changed in: wpa (Ubuntu)
Assignee: (unassigned) => Sebastien Bacher (seb128)
** Bug watch added: Debian Bug tracker #1003907
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003907
Was fixed in
https://launchpad.net/ubuntu/+source/gnome-session/41.3-1ubuntu1
- Ensure that systemd is preferred on startup (LP: #1959596)
** Package changed: gnome-shell (Ubuntu Jammy) => gnome-session (Ubuntu
Jammy)
** Changed in: gnome-session (Ubuntu Jammy)
Status: Confirmed =>
I have also added a PPA in the description.
** Description changed:
Switch from the apt bindings to the apt_pkg bindings for the ubuntu-
drivers tool.
This significantly improves performance (2,673s vs 13,751s , on my dated
Intel Ivy Bridge i7-3770K CPU).
[Attach sbuild log]
is there anything needed from gdm there?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1958488
Title:
[nvidia][xorg] display hangs on boot LOGO due to race of gdm and
gnome-control-center 42 changed its .desktop name. We either need to
backport that change to Jammy or revert gnome-shell 42's change. I
proposed the backport:
https://salsa.debian.org/gnome-team/gnome-control-
center/-/merge_requests/24
** Package changed: gnome-shell (Ubuntu) =>
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1947130
Title:
gnome-shell crashed with SIGSEGV in js::gc::Cell::storeBuffer from
JSObject::writeBarrierPost from
This bug was fixed in the package adsys - 0.8.1
---
adsys (0.8.1) jammy; urgency=medium
* Change chown logic on script directory and parents to avoid potential
vulnerability. (LP: #1961458)
* Separate readiness from session running to avoid unrefreshed user script
The fix is in this update
https://bugs.launchpad.net/ubuntu/+source/xorg-server/2:21.1.3-2ubuntu1
** Changed in: xorg-server (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: xorg-server (Ubuntu)
Assignee: (unassigned) => Timo Aaltonen (tjaalton)
--
You received this bug
The previous explanation suggests that's not really an issue and not
worth stable update so I'm going to wontfix,
William, those tasks were assigned to you so feel free to reopen and
upload anyway if you feel like it's worth doing but in the current state
it seems like that wasn't enough of a
Successful build logs for all PPA arches:
https://launchpad.net/~jbicha/+archive/ubuntu/arch/+sourcepub/13299512/+listing-archive-extra
The two reverted commits were easy enough to apply and feel like they
shouldn't interfere with pushing normal 42.* point releases to 22.04 LTS
later.
I believe
This bug was fixed in the package adsys - 0.8.1
---
adsys (0.8.1) jammy; urgency=medium
* Change chown logic on script directory and parents to avoid potential
vulnerability. (LP: #1961458)
* Separate readiness from session running to avoid unrefreshed user script
This bug was fixed in the package adsys - 0.8.1
---
adsys (0.8.1) jammy; urgency=medium
* Change chown logic on script directory and parents to avoid potential
vulnerability. (LP: #1961458)
* Separate readiness from session running to avoid unrefreshed user script
Public bug reported:
firefox-97.0.2+linuxmint1+tricia
I cannot connect to web interface of my old router that is on local LAN.
It supports only TLS v1.0 and support for TLS v1.0 & 1.1 was removed in
Firefox v97... I know I should replace my router with some better
device, I already tried several
Public bug reported:
Version (in jammy-proposed): 42~beta-1ubuntu1
Please see screenshot.
** Affects: gnome-shell (Ubuntu)
Importance: High
Status: New
** Attachment added: "system-menu.png"
https://bugs.launchpad.net/bugs/1964136/+attachment/5567026/+files/system-menu.png
You have been subscribed to a public bug:
On my Thinkpad W530 the external monitor attached to the dock only is
active until login. After login it disappears from available monitors,
loses signal and the internal monitor is active only.
Workaround: Uses X11 session.
So I don't need a solution.
** Package changed: ubuntu => wayland (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wayland in Ubuntu.
https://bugs.launchpad.net/bugs/1964126
Title:
Wayland does not detect external monitor
Status in wayland package in
** Changed in: wpa (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1958267
Title:
"Connection failed" for WPA Enterprise network eduroam
Status
The issue was reported on hirsute and sounds similar to bug #1231091
which was fixed in 21.10, is that still an issue on the current daily
image? is that flavor specific or do you get the issue on the ubuntu
ISO?
** Changed in: ubiquity (Ubuntu)
Status: Confirmed => Incomplete
** Changed
the ldd there doesn't show the missing symbols, is that cmd on the same
system which has the issue?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to modemmanager in Ubuntu.
https://bugs.launchpad.net/bugs/1961859
Title:
When we install
This works for me here. Tested on impish, with the thunderbird snap from
the stable channel (91.6.2, revision 192).
** Changed in: thunderbird (Ubuntu)
Status: New => Incomplete
** Tags added: snap
--
You received this bug notification because you are a member of Desktop
Packages, which
*** This bug is a security vulnerability ***
You have been subscribed to a public security bug:
Version: 2.34.6-0ubuntu0.20.04.1
This security update for focal does not seem to be automatically
upgradeable by unattended-upgrades:
2022-03-05 14:32:35,653 WARNING package libwebkit2gtk-4.0-37
StacktraceTop:
timeout_free (t=0x556675d5fa50) at glib-watch.c:206
connection_data_unref (d=0x556675d6f790) at
../avahi-common/dbus-watch-glue.c:81
connection_data_unref (d=0x556675d6f790) at
../avahi-common/dbus-watch-glue.c:76
start_timeout_callback (t=0x556675d5fa50) at glib-watch.c:252
** Attachment added: "Stacktrace.txt"
https://bugs.launchpad.net/bugs/1963758/+attachment/5567030/+files/Stacktrace.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups-filters in Ubuntu.
https://bugs.launchpad.net/bugs/1963758
** Attachment added: "ThreadStacktrace.txt"
https://bugs.launchpad.net/bugs/1963758/+attachment/5567032/+files/ThreadStacktrace.txt
** Attachment removed: "CoreDump.gz"
https://bugs.launchpad.net/bugs/1963758/+attachment/5566045/+files/CoreDump.gz
** Changed in: cups-filters (Ubuntu)
** Attachment added: "StacktraceSource.txt"
https://bugs.launchpad.net/bugs/1963758/+attachment/5567031/+files/StacktraceSource.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups-filters in Ubuntu.
Thank you for your bug report. Which desktop environment do you use?
Could you try to connect and then do
$ journalctl -b 0 > log
and attach the 'log' file to the report?
https://archived.forum.manjaro.org/t/cant-connect-to-eduroam-wifi/122684
also sounds similar, did you try to provide a
Public bug reported:
ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: gnome-shell 41.3-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
Uname: Linux 5.15.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu78
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop:
I'm closing this issue earlier than normal as I'm moving away from
reviewing bug reports that have received little or no attention in
recent times and there have been no comments to suggest that the
reported problem is still an issue when using a currently supported
release of Ubuntu.
Please feel
I'm closing this issue earlier than normal as I'm moving away from
reviewing bug reports that have received little or no attention in
recent times and there have been no comments to suggest that the
reported problem is still an issue when using a currently supported
release of Ubuntu.
Please feel
I'm closing this issue earlier than normal as I'm moving away from
reviewing bug reports that have received little or no attention in
recent times and there have been no comments to suggest that the
reported problem is still an issue when using a currently supported
release of Ubuntu.
Please feel
Public bug reported:
"ls" should never have been aliased in the first place. It was a
mistake. The emacs install de-aliases it unconditionally. Except I've
done that on my platform, so the "unalias ls" command fails and that
causes the installation to fail. Killing the alias is reasonable enough,
** Changed in: systemd (Ubuntu Jammy)
Status: New => In Progress
** Changed in: systemd (Ubuntu Jammy)
Assignee: (unassigned) => Lukas Märdian (slyon)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to accountsservice in
Never mind. The new release switches from straight GTK4 to
GTK4+libadwaita which we are trying to avoid for 22.04 LTS.
** Changed in: xdg-desktop-portal-gnome (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is
I've attached the journalctl output.
I'm running Kubuntu with plasma-nm 5.24.2-0ubuntu1.
I haven't provided a certificate or any authentication details, and the
security is set to none in the settings.
** Attachment added: "log"
Stacktrace:
#0 0x7fc4fe18aa7c in ?? ()
No symbol table info available.
Backtrace stopped: Cannot access memory at address 0x7ffd499cdaa0
StacktraceSource: #0 0x7fc4fe18aa7c in ?? ()
StacktraceTop: ?? ()
** Tags removed: need-amd64-retrace
--
You received this bug notification
I'm closing this issue earlier than normal as I'm moving away from
reviewing bug reports that have received little or no attention in
recent times and there have been no comments to suggest that the
reported problem is still an issue when using a currently supported
release of Ubuntu.
Please feel
Yes, I tried again tonight and it does work.
Very odd because it did not when I reported this, of course.
** Changed in: thunderbird (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Public bug reported:
> C-x 5 2 runs the command make-frame-command (found in global-map),
> which is an interactive compiled Lisp function in ‘frame.el’.
>
> It is bound to C-x 5 2, .
>
> (make-frame-command)
>
> Make a new frame, on the same terminal as the selected frame.
> If the terminal
This seems to be related to OWE
(https://en.wikipedia.org/wiki/Opportunistic_Wireless_Encryption). If I
disable this in the router, then I can connect without any issues.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in
I'm closing this issue earlier than normal as I'm moving away from
reviewing bug reports that have received little or no attention in
recent times and there have been no comments to suggest that the
reported problem is still an issue when using a currently supported
release of Ubuntu.
Please feel
I'm closing this issue earlier than normal as I'm moving away from
reviewing bug reports that have received little or no attention in
recent times and there have been no comments to suggest that the
reported problem is still an issue when using a currently supported
release of Ubuntu.
Please feel
Closing as no response from reporter.
** Changed in: xorg (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1577004
Title:
Graphic screen get
As I had not heard anything from you for a while I went ahead and
followed your directions
to return to the prior version as follows:
dhdurgee@z560:~/Downloads/debs$ sudo dpkg -i *.deb
[sudo] password for dhdurgee:
dpkg: warning: downgrading gir1.2-gtk-3.0:amd64 from 3.24.20-0ubuntu1.1
@Jeremy, I'm unsure to understand your point, what do you suggest doing
exactly? The shell revert seems the safest way there, unless you want to
provide compat with different names but what is the win for the LTS
users exactly?
--
You received this bug notification because you are a member of
I'm closing this issue earlier than normal as I'm moving away from
reviewing bug reports that have received little or no attention in
recent times and there have been no comments to suggest that the
reported problem is still an issue when using a currently supported
release of Ubuntu.
Please feel
I'm closing this issue earlier than normal as I'm moving away from
reviewing bug reports that have received little or no attention in
recent times and there have been no comments to suggest that the
reported problem is still an issue when using a currently supported
release of Ubuntu.
Please feel
I'm closing this issue earlier than normal as I'm moving away from
reviewing bug reports that have received little or no attention in
recent times and there have been no comments to suggest that the
reported problem is still an issue when using a currently supported
release of Ubuntu.
Please feel
I'm closing this issue earlier than normal as I'm moving away from
reviewing bug reports that have received little or no attention in
recent times and there have been no comments to suggest that the
reported problem is still an issue when using a currently supported
release of Ubuntu.
Please feel
I'm closing this issue earlier than normal as I'm moving away from
reviewing bug reports that have received little or no attention in
recent times and there have been no comments to suggest that the
reported problem is still an issue when using a currently supported
release of Ubuntu.
Please feel
** Package changed: ubuntu-release-upgrader (Ubuntu) => network-manager
(Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1962541
Title:
PEAP wifi can't connect (ubuntu
$ sudo apt remove libgail-common
it's more of a workaround to try, but check what it would potential
remove also if anything
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1962807
Adding back gnome-shell as affected package for now. Leaving it to
others to decide which route to take. ;)
** Also affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gnome-shell (Ubuntu)
Importance: Undecided => High
** Changed in: gnome-shell (Ubuntu)
Public bug reported:
System :
Ubuntu 21.10
Kernel 5.13.0-35
Session : Wayland
Each time I try to rip a CD with "abcde" gnome-shell crashes
What I understand from the logs :
Before the CD is ripped, abcde downloads a picture (from internet) as a cover
of the CD.
When tracker-extract discovers
The fix for this bug has been awaiting testing feedback in the -proposed
repository for focal for more than 90 days. Please test this fix and
update the bug appropriately with the results. In the event that the
fix for this bug is still not verified 15 days from now, the package
will be removed
I'm out of idea at this point, you could try to remove libgail-common
and see if that makes a difference but otherwise unsure why it's hitting
a segfault in the menu code...
** Changed in: gtk+2.0 (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a
Need fix in Ubuntu 20.04, gnome-shell-extension-ubuntu-dock
68ubuntu1~20.04.1
Patch in #7 failed 4/4 hunks
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
Here are the results:
dhdurgee@z560:~/Downloads$ sudo apt remove libgail-common
[sudo] password for dhdurgee:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
Public bug reported:
.
** Affects: xdg-desktop-portal-gnome (Ubuntu)
Importance: Undecided
Status: New
** Tags: jammy upgrade-software-version
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-desktop-portal-gnome in
I'm closing this issue earlier than normal as I'm moving away from
reviewing bug reports that have received little or no attention in
recent times and there have been no comments to suggest that the
reported problem is still an issue when using a currently supported
release of Ubuntu.
Please feel
I'm closing this issue earlier than normal as I'm moving away from
reviewing bug reports that have received little or no attention in
recent times and there have been no comments to suggest that the
reported problem is still an issue when using a currently supported
release of Ubuntu.
Please feel
Further to comment #2, issue won't expire due to 'New' status of snapd
task. With no response from reporter since 2022/01/24 I'm closing this
as "Invalid".
** Changed in: chromium-browser (Ubuntu)
Status: Incomplete => Invalid
** Changed in: snapd (Ubuntu)
Status: New => Invalid
How should I remove libgail-common? Could doing so cause other
problems?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1962807
Title:
segfault in libgtk-x11-2.0.so.0 with several
** Changed in: gnome-shell (Ubuntu)
Milestone: None => ubuntu-22.04-beta
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1962346
Title:
Ubuntu reboots instead of powering off
You have been subscribed to a public bug:
WPA2 enterprise can't connect PEAP
ubuntu 22.04 live/installer is not working too
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubuntu-release-upgrader-core 1:22.04.6
Uname: Linux 5.16.0-kali1-amd64 x86_64
ApportVersion: 2.20.11-0ubuntu78
Logging into 'Ubuntu on Wayland' is probably a good workaround because
it should avoid this problem completely. Although we would recommend
using Ubuntu 20.04 over 18.04.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libx11 in Ubuntu.
** Tags added: jammy regression
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1964136
Title:
Settings item not shown in System menu
Status in gnome-control-center package in
Hello kunal, or anyone else affected,
Accepted gstreamer1.0 into focal-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/gstreamer1.0/1.16.3-0ubuntu1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello kunal, or anyone else affected,
Accepted gst-plugins-good1.0 into focal-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/gst-
plugins-good1.0/1.16.3-0ubuntu1 in a few hours, and then in the
-proposed repository.
Please help us by testing this
Looks the same as these, which are also new in gnome-shell 42:
https://errors.ubuntu.com/problem/72ac8d41c03462cc0271527dec039025218b46d4
https://errors.ubuntu.com/problem/644a6cc9e462a67db78caff5570888f0fc956d0b
https://errors.ubuntu.com/problem/f87fbdb8562f83f5a04d1b4910b46dc111548b00
Frame #1
I've been running 21.10 since it was released and I haven't had the
problem on it. I honestly don't recall if I still had the issue on
21.04.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
Public bug reported:
When batch-count is set to 1, the output PDF cannot be opened with the
PDF tool.
The command line is as follows
scanimage --mode color --format=pdf --batch-count=1
When mode is set to gray or lineart, the output PDF is abnormal. (there were
three images in one sheet of
*** This bug is a duplicate of bug 1964120 ***
https://bugs.launchpad.net/bugs/1964120
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1964120, so it is being marked as such. Please
I'm not sure we should assign this to ubuntu-22.04-beta when it's only
ever been observed on 21.10.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1962346
Title:
Ubuntu reboots
** Also affects: xorg-server (Ubuntu Jammy)
Importance: High
Assignee: Timo Aaltonen (tjaalton)
Status: Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
The fix is already in 21.04 and later (comment #12). We're now talking
about 20.04.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/1905519
Title:
Syslog is
I'm guessing the dock uses DisplayLink, in which case the compositor
needs to have implemented special support for that (like mutter/gnome-
shell already has). To confirm this theory, please tell us the model of
dock as well as running:
lsmod > lsmod.txt
journalctl -b0 > journal.txt
and
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
Tracking upstream in
https://gitlab.freedesktop.org/xorg/xserver/-/issues/1306 or probably
more accurately:
https://gitlab.freedesktop.org/xorg/xserver/-/issues/1283
** No longer affects: gnome-shell (Ubuntu)
** Bug watch added: gitlab.freedesktop.org/xorg/xserver/-/issues #1306
Also fixed in
https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/842
** Bug watch added: gitlab.freedesktop.org/xorg/xserver/-/issues #1283
https://gitlab.freedesktop.org/xorg/xserver/-/issues/1283
** Changed in: xorg-server
Remote watch:
Sounds like the fix is in mutter 42.beta
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2235
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mutter (Ubuntu)
Status: New => Fix Committed
** Tags added: fixed-in-mutter-42.beta
** Summary changed:
- long touch/press a director won't trigger the context menu like file on empty
space. on touch monitor
+ long touch/press a directory won't trigger the context menu like file on
empty space. on touch monitor
--
You received this bug notification because you are a member
** Tags added: 2-in-1
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1964091
Title:
long touch/press a director won't trigger the context menu like file
on empty space. on touch
** Also affects: nvidia-graphics-drivers-340 (Ubuntu)
Importance: Undecided
Status: New
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-340 in
Are you sure 20.04 is affected? I can't see any reports of the issue on
20.04.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/1905519
Title:
Syslog is
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell
It looks like we're probably looking for a crash from 'Xwayland'.
** Tags added: wayland-session
** Also affects: xwayland (Ubuntu)
Importance: Undecided
Status: New
** Changed in: xwayland (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you
cheese version 41 is release at 2021-Nov-15,
https://download.gnome.org/sources/cheese/41/
quick check r40, it contains those patch in #6. and jammy have version
41.1-1
Given so, close this one.
** Changed in: oem-priority
Status: Confirmed => Fix Released
** Changed in: cheese (Ubuntu)
1. I check ubuntu21.10 system using glibc 2.34.
2. I am install MM1.16.6 into ubuntu21.10 but MM1.16.6 should using glibc
2.54.2.So I already install 2.54.2.
When I install that and I reboot system and check ldd -version is already
glibc 2.34.And system work fine.
WWan can using
Hi Seb,
FWIK, the fix from gdm is not mandatory.
The display-manager (inside u-d-c) will handle it.
but if any flavor which doesn't use u-d-c then gdm upstream also provide this
commit
https://gitlab.gnome.org/GNOME/gdm/-/commit/ecbd9694458194e24f356ba9d37fc4f3a515c3dd#note_1402863
to fix this
Although duplicate bug 1964254 is gnome-shell 41.
** Summary changed:
- gnome-shell crashed with SIGSEGV at ?+a7c
+ gnome-shell crashed with SIGSEGV at ?+a7c called from [heap address]
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Hello kunal, or anyone else affected,
Accepted gst-plugins-base1.0 into focal-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/gst-
plugins-base1.0/1.16.3-0ubuntu1 in a few hours, and then in the
-proposed repository.
Please help us by testing this
1 - 100 of 122 matches
Mail list logo
