I also tried removing the Mesa Vulkan driver and set `export
LIBVA_DRIVER_NAME=i965`. That gets rid of the warning message but I
still get a hang with Vivaldi and nextcloud-desktop still does not work.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Thanks. Sounds similar. My nautilus and gnome-control center do work
strangely enough. But the more clues the better.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wayland in Ubuntu.
** Package changed: xorg (Ubuntu) => wayland
** Project changed: wayland => wayland (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2061257
Title:
After 24.04
I tried the same upgrade and test on an old Sandy Bridge laptop.
Everything works as expected there. So a Haswell issue perhaps?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
I tried the same test on an old Sandy Bridge laptop. Everything works
as expected there. So a Haswell issue?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2061257
Title:
** Summary changed:
- Many app failures under Wayland; no issues with Xorg
+ With 24.04: Many graphical app failures under Wayland; no issues with Xorg
** Summary changed:
- With 24.04: Many graphical app failures under Wayland; no issues with Xorg
+ After 24.04 upgrade, many graphical app
Public bug reported:
Many applications seem to fail under a Wayland session that work correctly with
an Xorg session. E.g.
- The nextcloud client app fails to contact the server and functions in the app
will not launch with Wayland while they work perfectly in Xorg
- The Vivaldi browser exits
I should also mention: this was an upgrade from 23.10 to 24.04 and all
of the apps worked correctly in 23.10.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2061257
Title:
Public bug reported:
We look to use / upgrade to Weston 13.0 on Ubuntu 22.04.3 LTS. We see
the following Weston-13.0 dependencies are not met for the same.
libwayland*: required version >= 1.22.0
So we request to upgrade these packages on Ubuntu 22.04.3 LTS.
The release of Ubuntu we are using:
Fantastic! I can confirm that this is fixed on Ubuntu 23.10.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mime-support in Ubuntu.
https://bugs.launchpad.net/bugs/1878617
Title:
Apple pages file type should be added to
ooo-thumbnailer is an abandoned project and is being removed from
Debian. Project link: https://launchpad.net/ooo-thumbnailer
** Changed in: ooo-thumbnailer (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Public bug reported:
In jammy (22.04) and focal (20.04) the executable /usr/bin/resolvectl is
provided by the package "systemd". If you install the packages libnss-
resolve and openfortivpn and run "openfortivpn vpn.example.com -u user
-v" you get undesired behavior:
[...]
INFO: Adding VPN
is caused by the new two patches in 0.3.48-1ubuntu2 which is fixed
the Cheese preview stuck issue on jammy
* d/p/0001-buffers-ensure-buffer-size-does-not-exceed-maxsize.patch
d/p/0002-gst-dequeue-a-shared-buffer-instead-of-original-pool.patch
- Camera output freeze when using
Public bug reported:
(base) walid@len:~$ lspci | grep VGA
:00:02.0 VGA compatible controller: Intel Corporation Device 9a78 (rev 01)
(base) walid@len:~$ sudo lshw -C video
[sudo] password for walid:
*-display
description: VGA compatible controller
product:
.debdiff
$ wget
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1987631/+attachment/5638528/+files/pipewire_0.3.48-1ubuntu4.debdiff
$ pull-lp-source gstreamer1.0 1.20.3-0ubuntu1
$ pull-lp-source gst-plugins-base1.0 1.20.1-1
$ pull-lp-source pipewire 0.3.48-1ubuntu3
$ patch -p1 -d gstreamer1.0
is fixed
the Cheese preview stuck issue on jammy
* d/p/0001-buffers-ensure-buffer-size-does-not-exceed-maxsize.patch
d/p/0002-gst-dequeue-a-shared-buffer-instead-of-original-pool.patch
- Camera output freeze when using pipewiresrc (LP: #1985057)
Here is a comment from
https
@binli - I never found a need to update pipewire; the gstreamer patches
(for gstreamer and gst-plugins-base) seem to be sufficient in my
testing.
I tested your gstreamer & gst-plugins-base packages and they work the same as
the ones I built. I think you could drop "-0ubuntu1binli1" from the
This bug does not seem to be present in Ubuntu 22.10, on the same
hardware.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1989602
Title:
Delay in updating charge status
orce the creation of the directory
and remove the test.
eg. change this;
OPTIONS="$(
if [ -r "$OPTIONFILE" ]; then
cat "$OPTIONFILE"
fi
if [ -d /etc/X11/Xsession.options.d ]; then
run-parts --list --regex '\.conf$' /etc/X11/Xsession.optio
to your opinion there.
The immediate work around is to create an empty directory so that the
test does not fail. Better still, force the creation of the directory
and remove the test.
eg. change this;
OPTIONS="$(
if [ -r "$OPTIONFILE" ]; then
cat "$OPTI
ur opinion there.
The immediate work around is to create an empty directory so that the
test does not fail. Better still, force the creation of the directory
and remove the test.
eg. change this;
OPTIONS="$(
if [ -r "$OPTIONFILE" ]; then
cat "$OPTIONFILE"
fi
** Description changed:
rsync 3.2.3 has a broken "--update" option.See the examples below.
The "--update" option incorrectly makes rsync say a file is newer than itself.
Remove the "--update" option, and rsync correctly says the file is "uptodate".
The right output should of course be
I'm not familiar with your SRU process, debdiff, dput, the "General
Requirements" document, the "security policy document", or your upload
process, and I'm not into learning about all that and filling out your
special form and making your special upload when there is no guarantee
that Ubuntu will
I knew nothing about your SRU process until now; the man page for
`ubuntu-bug` makes no mention of it. Who fills out the SRU Bug Template
and makes the fix actually happen? Is there anything more I need to do
here?
--
You received this bug notification because you are a member of Ubuntu
Touch
The problem was marked as Confirmed by Paride back on March 17.
Then today it gets marked Invalid.
Then later today it gets marked Confirmed again.
I don't understand your process.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Your incorrect statement "seems the issue does not actually exist" is
wrong. I told you exactly how to reproduce the problem on your latest
22.04.1 LTS release. I gave you the link to the upstream bug that Wayne
fixed over two years ago. This two-year-old bug does exist and it
exists in your
Your incorrect statement "seems the issue does not actually exist" is
wrong. I told you exactly how to reproduce the problem on your latest
22.04.1 LTS release. You were also given the link to the upstream bug
that Wayne fixed over two years ago. This two-year-old bug does exist
and it exists
Hey Ubuntu - I see now that this bug was reported and fixed at source in
September 2020, over two years ago. The real bug is: "Why didn't Ubuntu
apply the fix to the supported Ubuntu releases?"
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
The laptop is logged in and running Wayland: /usr/bin/Xwayland :0
My desktop is running X11: /usr/lib/xorg/Xorg -nolisten tcp :0
When I SSH into the laptop from the desktop, my DISPLAY is set to
"localhost:10".
When I start an xterm in the SSH session (running xterm on the laptop),
the xterm
Public bug reported:
I am using a Lenovo ThinkPad Yoga 370, running Ubuntu 22.04 LTS.
When plugging in the charger, the current charge status in the top bar and
Settings shows 'Not Charging' for a few minutes and then shows that the system
is charging normally.
When unplugging the charger the
Public bug reported:
I'm running Ubuntu 20.04 on my desktop. I SSH into my laptop running
22.04:
desktop$ ssh laptop
laptop$ sudo -sE
laptop#
If I now run most any X11 client applications (e.g. xload, xterm)
using this laptop SSH command line, they correctly open windows on my
Thank you for following this up and your reply. I will report it and see
if it is updated upstream.
Thank you again!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1988667
Unfortunately that didn't made any change. My
/etc/apparmor.d/usr.bin.redshift now looks like follows.
/usr/bin/redshift {
dbus send bus="system"
path="/org/freedesktop/DBus"
interface="org.freedesktop.DBus"
member="{GetNameOwner,StartServiceByName,AddMatch}",
dbus
Which would be?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1948752
Title:
apparmor is logging too many messages
Status in Redshift:
New
Status in apparmor package
*** This bug is a duplicate of bug 1956915 ***
https://bugs.launchpad.net/bugs/1956915
Verified internally with Ubuntu 20.04.4 + libegl-mesa0 version
"21.2.6-0ubuntu0.1~20.04.2" and confirmed the crash issue is resolved.
--
You received this bug notification because you are a member of
A fix was released upstream in shared-mime-info 2.2 (2022-03-27). Sadly,
this didn't make it to Ubuntu 22.04 LTS.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shared-mime-info in
Ubuntu.
This issue is no longer present in Ubuntu 22.04. Wile using Ubuntu 21.10, the
following workarounds also remedied the issue:
- Run a mainline 5.15.x kernel from
https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D
- Run the Jammy Jellyfish kernel from
https://packages.ubuntu.com/jammy/linux
Public bug reported:
4/23/2022: did apt-get update followed by apt-get dist-upgrade and this
is what happened.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-firmware 1.187.29
ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-35-generic
Updated and now I can't reproduce. Looks like some update made it go
away.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1951878
Title:
"gdk/x11/gdkwindow-x11.c:5653
fwiw I've checked Ubuntu 21.10/22.04, Fedora 35/36 and Arch. This only
happens in Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1951878
Title:
I am seeing this in 22.04 and an easy way for me to reproduce is on a
fresh login, open a terminal and watch the log, open Brave/Chrome, for
some reason the first time you open the browser it has a GTK title bar
which goes away on closing/reopening the app, now right clicking in the
terminal
I am not arguing about the behaviour, which is correct and apparently hasn't
changed.
I'm complaining about the unannounced change in message from "is uptodate" to
"is newer".
Three problems:
1. The message "is newer" is an unannounced change from all previous
versions of rsync that say "is
Public bug reported:
rsync 3.2.3 has a broken "--update" option.See the examples below.
The "--update" option incorrectly makes rsync say a file is newer than itself.
Remove the "--update" option, and rsync correctly says the file is "uptodate".
The right output should of course be "is
Hi Timo,
When we can expect that to be part of 'focal-updates' ?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1956915
Title:
New bugfix release 21.2.6
Status in mesa
*** This bug is a duplicate of bug 1956915 ***
https://bugs.launchpad.net/bugs/1956915
Hi Timo,
>From https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1956915, I
understood that Mesa 21.2.6 is backported to ubuntu0.1~20.04.1 and that
is currently under 'focal-proposed', when we can expect
I compiled several Ubuntu-5.13.0-x.x tags from
https://kernel.ubuntu.com/git/ubuntu/ubuntu-impish.git/refs/ but the backlight
issue seems to go far back in time. I tested:
- Ubuntu-5.13.0-25.26
- Ubuntu-5.13.0-21.21
- Ubuntu-5.13.0-20.20
- Ubuntu-5.13.0-19.19
- Ubuntu-5.13.0-16.16
In
I just tested signed Ubuntu kernel 5.13.0-28-generic which is in
Proposed right now, but it does not fix the issue. Brightness
adjustments work, but service fails during startup and screen is at full
brightness every boot (at gdm and at GNOME 3 desktop).
--
You received this bug notification
I tested some mainline 5.13.x kernels from
https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D and was able to
find a point release where this issue is resolved. Testing results:
Signed Ubuntu kernel 5.13.0-27-generic: brightness adjustments work, but
service fails during startup and screen
Public bug reported:
The rsyslog program mis-handles the "startswith_i" comparison when applied
to $programname. Details follow:
Put this file in /etc/rsyslog.d/10-idallen.conf (it precedes all other
files):
if ( $programname startswith 'foo' ) then {
/var/log/idallen-cron.log
I enabled debug logging for systemd with kernel cmdline:
systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M printk.devkmsg=on
New log attached to bug report is the output of 'journalctl -b':
systemd-debug.log
Filtering on "backlight" and omitting systemd-logind, this portion looks
Public bug reported:
Sometimes if I run `pulseaudio -k` a few times, sound returns.
Sometimes if I run `sudo alsa force-reload`, sound returns.
Sometimes if I shutdown and start the laptop, sound returns.
This first occurred a few months ago when I was running 20.04, and I
upgraded to 21.10 in
Created attachment 143424
New crash information added by DrKonqi
gwenview (20.12.3) using Qt 5.15.2
- What I was doing when the application crashed:
This is a little bizarre. I encountered this while rapidly scrolling
through thumbnails in a directory. One particular image reliably crashes
Hi Timo,
A similar crash is observed in mesa-egl and it is resolved in Mesa
master branch. Please refer the bug:
https://bugs.launchpad.net/mesa/+bug/1946621
Can you help backporting the fix to "Focal" series.
--
You received this bug notification because you are a member of Ubuntu
Touch
** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #5466
https://gitlab.freedesktop.org/mesa/mesa/-/issues/5466
** Also affects: mesa via
https://gitlab.freedesktop.org/mesa/mesa/-/issues/5466
Importance: Unknown
Status: Unknown
--
You received this bug notification
Public bug reported:
Unfortunately, this bug does not seem to be fixed yet.
My syslog is flooded with ALLOWED messages regarding redshift.
My system is a Kubuntu 21.04.
AppArmor is V. 3.0.0-0ubuntu7.1
Attached you'll find an excerpt from /var/log/syslog for the last 5
minutes.
** Affects:
PR: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/13302 is
merged on Mesa master branch:
https://gitlab.freedesktop.org/maniraj87/mesa/-/commit/796c9ab3fd6b897ae3b3c069568182178c7661d4
Please include this change in Mesa upgrades in "Focal" series.
--
You received this bug
Root caused the issue with Mesa-EGL, created a PR for the same:
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/13302
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
The crash happens only when calling eglReleaseThread() from destructor
of the process. Please find the attached simple app which can be used to
repro the issue.
With valgrind, I see there is some invalid memory access during the
eglReleaseThread() call. Find the logs below:
==5059== Invalid read
Public bug reported:
Crash in libegl-mesa0 (in eglReleaseThread API), please find the
backtrace:
#0 0xf7c86ac4 in __GI___pthread_mutex_lock (mutex=mutex@entry=0x8) at
pthread_mutex_lock.c:67
#1 0xf4a7d110 in mtx_lock (mtx=0x8) at
../include/c11/threads_posix.h:223
#2
Closing this bug as it works for me (Xubuntu 20.04) and we've not seen
any reports of this problem for many years.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/687689
Public bug reported:
So I'm getting a warning on syslog:
"ubuntu systemd-udevd[911]: Network interface NamePolicy= disabled on
kernel command line, ignoring."
I've seen another similar report which seems to be fixed back in 2015:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1411992
Will that be updated only on impish (21.10) ? Actually we need the
update on focal (20.04).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1940545
Title:
Update Mesa to
** Description changed:
With the recent MR
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9902 to Mesa,
- we have added ability to GBM to dynamically load the backends. So we
- request to upgrade mesa libs to its latest version (mesa-21.1.7) on
- Ubuntu 20.04 to use the added
Public bug reported:
With the recent MR
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9902 to Mesa,
we (NVIDIA) have added ability to GBM to dynamically load the backends.
So we request to upgrade mesa libs to its latest version (mesa-21.1.7)
on Ubuntu 20.04 to use the added feature
Tested on: Ubuntu 21.04
Package: evolution-data-server 3.40.1-2 (from Impish-proposed)
There aren't packages for hursuit (21.04) but I just tried the impish
(21.10) package and works.
Thanks again
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Tested on: Ubuntu 20.04.2 LTS
Package: evolution-data-server 3.36.5-0ubuntu1 amd64
Personal iCloud account, now is solved.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to evolution-data-server in
Ubuntu.
Public bug reported:
sh.service - OpenBSD Secure Shell server
Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset:
enabled)
Active: activating (auto-restart) (Result: exit-code) since Wed 2021-02-17
15:42:28 IST; 11ms ago
Docs: man:sshd(8)
Hello Daniel,
Packages named 'timidity' or 'pipewire' are not installed. File
packages.txt in attachment.
Regards, Dmitriy.
** Attachment added: "packages.txt"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1915198/+attachment/5462367/+files/packages.txt
--
You received this
Public bug reported:
installing plocate before mlocate
ProblemType: Package
DistroRelease: Ubuntu 20.10
Package: gzip 1.10-2ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
Uname: Linux 5.8.0-25-generic x86_64
NonfreeKernelModules: wl zfs zunicode zavl icp zcommon znvpair
** Changed in: apt (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1481779
Title:
apt-get autoremove crashes my system
Status in apt
Public bug reported:
Shouldn't these give the same results in dash, i.e. "/root"?
They give the same output in bash.
$ dash
$ var=~root
$ echo "$var"
/root
$ export var=~root
$ echo "$var"
~root
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: dash 0.5.10.2-6
ProcVersionSignature: Ubuntu
A workaround that worked for me was `pulseaudio -k`; having to do this
almost every time I need audio is a big PITA though.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
@Kai Kasurinen
>probably fixed on shared-mime-info 2.0:
>https://gitlab.freedesktop.org/xdg/shared-mime-info/-/commit/18bb7cfc6c43d710ecf60339b5dd9bd19c297cdf
Yeah, well. It's if they only used the same database.
--
You received this bug notification because you are a member of Ubuntu
Touch
If you wrap string in the proper tags you will get the same result, but
with different offset (28 chars):
tee "index.html" <
`printf "x"%.0s {1..228}`
use strict
eol # -> text/html
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
#ＩＮＴＲＯ
After digging up for a while I've found where the issue comes from for both
`.html` and `.py` (bug #1857824) files.
#ＳＨＯＲＴ
The culprit responsible for misidentification resides in `.xml` database which
specifies how to match mime-type against input data. It can be found here [2].
#ＬＯＮＧ
With the same setup I have the `mimetype` to output `text/html` for
`index.html`. It seems it workds correctly.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shared-mime-info in
Ubuntu.
** Also affects: kde-cli-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shared-mime-info in
Ubuntu.
https://bugs.launchpad.net/bugs/1890716
Title:
misidentifies
I've reported a new bug providing a complete and correct description:
https://bugs.launchpad.net/ubuntu/+source/kde-cli-tools/+bug/1896682
This one can be safely closed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
New bug reopened with complete and correct explanation:
https://bugs.launchpad.net/ubuntu/+source/kde-cli-tools/+bug/1896682
** Changed in: shared-mime-info (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
After running that commands I got the following output:
$ ...
Running kmimetypefinder5 "/home/alex/Desktop/index.html"
application/x-perl
It seems like that kmimetypefinder5 is major culprit here. I've found another
unrelated bugreport here which was reported about a year ago:
I just have tried a fresh new user. The output is identical. See
attached screenshot.
** Attachment added: "xdg-mime query wrong result"
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1890716/+attachment/5413048/+files/Screenshot_20200921_232318.png
--
You received this bug
why did you tag the report*
Bump.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shared-mime-info in
Ubuntu.
https://bugs.launchpad.net/bugs/1890716
Title:
xdg-mime query filetype index.html reports wrong type
Status in
Hi Sebastien. Thaks your for your reply.
I suggest you to do the following to see that even if file is starting
with proper tags it is recognized as `application/x-perl`:
$ tee "index.html" <
use strict
eol
$ xdg-mime query filetype index.html # -> application/x-perl - wrong
type
Why did you
Same issue here with Aukey EP-N5 bluetooth earbuds on 20.04.1. This is
a top-selling set of earbuds on Amazon so I thought they'd work.
The microphone doesn't appear at all in the list of input devices under
system Sound Settings.
Attempting to change the profile within Blueman to HSP/HFP
Public bug reported:
Initially added epson c60 stylus but it installed with filter error.
Deleted printer from cups , added new printer.
Added the epson printer , selected the .ppd file that worked in 1904 and
clicked add printer.
Cups just sits and thinks.
Same happens if I use the
As requested, here is an example of an Apple Pages document, taken from
an online templates website.
** Attachment added: "New Job Resignation Letter.pages"
https://bugs.launchpad.net/ubuntu/+source/mime-support/+bug/1878617/+attachment/5373328/+files/New%20Job%20Resignation%20Letter.pages
I created a bug report in shared-mime-info's issues tracker here:
https://gitlab.freedesktop.org/xdg/shared-mime-info/-/issues/136
** Bug watch added: gitlab.freedesktop.org/xdg/shared-mime-info/-/issues #136
https://gitlab.freedesktop.org/xdg/shared-mime-info/-/issues/136
--
You received
Public bug reported:
LibreOffice can open .pages files (from Apple pages). However, the mime
type for these files is incorrectly just application/zip:
$ file --mime-type example.pages
example.pages: application/zip
Instead, it should be application/vnd.apple.pages .
This would allow the user
This also happens on a Dell XPS 9570. My workaround after reboots, or
other events that disable the headphone audio, is to run this:
sudo alsactl restore
Then things are back to normal for a while.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Public bug reported:
I recently installed ubuntu 20.04 on my computer, and I am running into
an issue when I do the following:
* Login with a user on desktop
* Select switch user, and login as second user
* Switch user again, and return to original user
At this point, text and icons in the
I also experienced this bug. I was running Ubuntu 18.04, and I upgraded
to Ubuntu 20.20 yesterday by running `update-manager -d` on the command-
line, which launched the GUI. During the upgrade itself, I was shown a
dialog displaying an error relating to pam.
I've attached apt-term.log (for me
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1868474/+attachment/5341479/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "xdpyinfo.txt"
https://bugs.launchpad.net/bugs/1868474/+attachment/5341485/+files/xdpyinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "Xrandr.txt"
https://bugs.launchpad.net/bugs/1868474/+attachment/5341483/+files/Xrandr.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1868474/+attachment/5341480/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "MonitorsUser.xml.txt"
https://bugs.launchpad.net/bugs/1868474/+attachment/5341474/+files/MonitorsUser.xml.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "NvidiaBugReportLog.txt"
https://bugs.launchpad.net/bugs/1868474/+attachment/5341475/+files/NvidiaBugReportLog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "nvidia-settings.txt"
https://bugs.launchpad.net/bugs/1868474/+attachment/5341484/+files/nvidia-settings.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "XorgLogOld.txt"
https://bugs.launchpad.net/bugs/1868474/+attachment/5341482/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1868474/+attachment/5341478/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
1 - 100 of 285 matches
Mail list logo
