For anyone who is having this problem, you need to create a link to the
pulse-15.99* folder called pulseaudio. IE, as root:
cd /usr/lib
ln -s pulse-15.99.1+dfsg1/ pulseaudio
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Have this problem on a Dell XPS 13 running Ubuntu 23.10, kernel
6.5.0-35-generic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060727
Title:
The keyboard does not work after latest kernel update
Support should be added to the kernel as of:
b257187bcff4 ("ALSA: hda: cs35l41: Support additional ASUS Zenbook 2022
Models")
And firmware as of:
771968c68191 ("linux-firmware: Add firmware for Cirrus CS35L41 on ASUS
Laptops")
--
You received this bug notification because you are a member of
This persists and should be simple to replicate.
Why has it has no attention?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1273764
Title:
Grub ignores TIMEOUT options on /etc/default/grub
To
Just saw this on some field units that are iOT type devices and
sometimes get shutdown non-cleanly. We run apt-update on startup and we
noticed one machine would not update and had no knowledge of any
packages in one of the repos in the sources.list.
We noticed the Packages file has 0 size, and
Public bug reported:
ubuntu@ubuntu:~$ evolution
(process:23406): e-data-server-WARNING **: 08:04:00.506: module_load:
libevolution-rss-common.so: cannot open shared object file: No such file or
directory
Failed to load module: /usr/lib/evolution/modules/module-rss.so
(evolution:23406):
Actually, it may not be an issue even for Jammy HWE. My copy shows block
cloning as an option that's off.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2044657
Title:
Multiple data corruption
This issue is different. It's another problem with block copy. But
that's known to still be an issue. It's why block copy is disabled in
2.2.1. This is only an issue for the Jammy HWE, which has 2.2.0. No one
should be shipping 2.2.0 with anything. It should be replaced with 2.2.1
at least.
--
Same result with
export DEB_BUILD_PROFILES="nobiarch nocross"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058050
Title:
gcc-13 build-depends on gcc-multilib if !cross, not if cross
To manage
Public bug reported:
export DEB_BUILD_PROFILES=nocross
apt build-dep gcc-13
installs gcc-multilib, gnat-13, gdc-13, and 21 more lib32... & etc.
These should be installed for cross, not norcross
Version noble 13.2.0-4ubuntu3
** Affects: gcc-13 (Ubuntu)
Importance: Undecided
Public bug reported:
24.04 nightly from March 5.
This is a regression from 20.04. The same problem is present in 22.04
/etc/nfsmount.conf allows specifications of per-server options.
with the following:
[ NFSMount_Global_Options ]
vers=3
rsize=65536
wsize=393216
[ Server
** Tags added: regression-release
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056217
Title:
nmcli regression: can't set IPV6 token
To manage notifications about this bug go to:
Public bug reported:
24.04 nightly, downloaded Mar 5.
network-manager 1.45.90-1ubuntu1
In network manager, if you try to set ipv6.token, when you save it says
Error: connection verification failed: ipv6.token: only makes sense with
EUI64 address generation mode
This is the same as under
Since I was just referenced, note that I wouldn't favor putting 2.2 into
Jammy. I would, however, prefer to see the latest 2.1.x.
2.2 is still seeing a substantial number of bug fixes. It will probably
be ok by the release date of 24.04, but I still wouldn't change major
versions for Jammy.
--
Better to change the URL to the homepage listed on the above site, which
is: https://sourceforge.net/projects/mars-game/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055211
Title:
apt show
Public bug reported:
apt show marsshooter
Homepage: https://github.com/thelaui/M.A.R.S.
Note: the homepage listed above works if you type it into a web browser
with the period, but if you right click and select open link (at least
in Xubuntu) it opens as:
https://github.com/thelaui/M.A.R.S
Public bug reported:
apt show gnome-breakout
Homepage: www.users.on.net/~mipearson/
Clicking on the link redirects to
https://www.internode.on.net/nodesupport/guides/internode_members_webspace_end_of_life
The host has stopped providing free webspace.
Description:Ubuntu 22.04.4 LTS
Public bug reported:
sudo apt show njam
Homepage: http://njam.sourceforge.net
Clicking on this link redirects to
https://domyjavaassignment.com/writer.html, which is a server not found
error.
[lsb_release -rd]
Description:Ubuntu 22.04.4 LTS
[apt-cache policy njam]
njam:
Installed:
Because it is not production ready,
We use the livecd uninstalled.
Please make an exception for the kernel packages,
Please just put the kinetic kernels on the lunar livecds,
(And for all new)
So we dont have to roll our own livecd just to smoke test a new version,
So we dont get the avalanche
Charles
--
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
in.
May 09 21:11:49 x1 systemd-tmpfiles[1665]: Detected unsafe path
transition / (owned by charles) → /tmp (owned by root) during
canonicalization of /tmp.
After a chown,
ls -ld /
now shows ownership by root:root correctly and I no longer get errors in the
log.
Note this file is what creates
chown root:root /tmp/.X11-unix/
chown root:root /tmp/.ICE-unix/
Fixes the issue.
I see there's a masked x11-common service that seems to set permissions
on these directories.
Not sure how these directories are supposed to be created and why that's
going wrong.
I ran /etc/init.d/x11-common
Public bug reported:
On my system with Nvidia 510 drivers I found that if I'm logged in and
lock the session another user can't login. I reset the 2nd user's
account to verify that if I login and lock my session they can't login.
I found this in permission error in the logs.
May 09 21:58:20
I have an Intel Nuc, Product Name: D34010WYK, i3-4010U, its hooked up a
Samsung TV via hdmi. The sound defaults to HDMI/DisplayPort - Built-in
Audio, Digital Stereo (HDMI) Output but that doesn't work. If I flip
it to Digital Surround it works but since the TV only has a left/right
speaker I
Jeff,
The patches are queued up to be submitted to 5.18
https://git.infradead.org/git/nvme.git/log/refs/tags/nvme-5.18-2022-03-03
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1948626
Title:
Ubuntu
Also, can I interest you in 1918312 for 22.04? Everyone agrees it's a
security issue. It has a well-known 2-line fix (our version is 4 lines),
which we've been using in production for over a year.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
That's a sensible approach, but there are loads of web pages telling
people how to set up NFS, and they all claim that on current
distributions you no longer need to enable individual services. That's
not true for Ubuntu 20.
Please do make sure it's fix in 22.04.
The original reasoning had a
I conjecture that the problem occurred when moving from init scripts to
systemd. It's pretty clear that the default in the nfs-common init
script was to start statd. I conjecture that when converting to systemd,
someone forgot to put a Wants in nfs-server. It's got an after but not a
Wants.
Statd is used by both client and server. I think that note is for the
client usage.
Our servers don't necessariy do any NFS3 client mounts, so the client
start would't happen. Is it possible that at some point I mounted
something via NFS3 and that's the only reason statd was running? I can't
right. It's not failing. It's not running at all.
systemctl status rpc-statd
● rpc-statd.service - NFS status monitor for NFSv2/3 locking.
Loaded: loaded (/lib/systemd/system/rpc-statd.service; disabled; vendor
preset: enabled)
Active: inactive (dead)
Journalctl doesn't show that
** Summary changed:
- nfs v3 locking fails - 5.4.0-92 regression
+ nfs v3 locking fails - rpc-statd not started after minor upgrade
** Package changed: kernel-package (Ubuntu) => nfs-utils (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
It has nothing to do with the kernel. For some reasons rpc.statd isn't
getting started. The systemd declaration looks fine, but it isn't there.
Doing "systemctl start rpc-statd" and "enable" fixes it. The other parts
of nfs-utils seem fine.
--
You received this bug notification because you are a
The problem occurs on 4 different servers.
It does not occur on a server running Centos7 updated to kernel 5.4.170.
This implies that the problem is most likely an Ubuntu patch (or it was fixed
upstream between 5.4.157 and 5.4.170).
--
You received this bug notification because you are a member
** Summary changed:
- nfs v3 locking fails
+ nfs v3 locking fails - 5.4.0-92 regression
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956787
Title:
nfs v3 locking fails - 5.4.0-92 regression
To
Also, "lslocks" on the server shows no locks associated with lockd,
though there are locks associated with nfsd. (nfsd would be locks from
NFS 4 I believe.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
We just upgraded our nfs servers from 5.4.0-72 to 5.4.0-92.
We are using NFS v3 in a large computer science department, with several
hundred clients.
Lots of applications are now failing because locks don't work.
/var/log/syslog on the client reports lockd not responding.
Confirming this same error on a fresh install of 20.04 LTS as well
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905468
Title:
Ubuntu 20.04LTS vtund program fails to function
To manage
Brian
Have you been able to make any progress?
I dont understand as any further install I still get the same error when I
run sudo apt-get install -f:
dpkg-maintscript-helper: error: file '/usr/share/npm/node_modules/node-gyp'
not owned by package 'npm:all'
Do I have to change the owner and
Brian
I have attached /var/log/dist-upgrade/20211207-0850 and 20211207-0819 which
have the log file requested.
Many thanks
Charlie Simms
On Wed, 8 Dec 2021 at 16:35, Brian Murray <1953...@bugs.launchpad.net>
wrote:
> The following lines in VarLogDistUpgradeApttermlog.txt indicate where
> part
Chris
Thank you for your response.
I have ran apport-collect 1953524 which has updated my bug in launchpad.
Yes I was trying to upgrade to 21.04.
Regards
Charlie Simms
On Wed, 8 Dec 2021 at 01:41, Chris Guiver <1953...@bugs.launchpad.net>
wrote:
> Thank you for taking the time to report this
apport information
** Attachment added: "VarLogDistupgradeLspcitxt.txt"
https://bugs.launchpad.net/bugs/1953524/+attachment/5546144/+files/VarLogDistupgradeLspcitxt.txt
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: Incomplete => New
--
You received this bug notification
apport information
** Attachment added: "VarLogDistupgradeApttermlog.txt"
https://bugs.launchpad.net/bugs/1953524/+attachment/5546143/+files/VarLogDistupgradeApttermlog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "VarLogDistupgradeAptlog.txt"
https://bugs.launchpad.net/bugs/1953524/+attachment/5546142/+files/VarLogDistupgradeAptlog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "VarLogDistupgradeAptclonesystemstate.tar.gz"
https://bugs.launchpad.net/bugs/1953524/+attachment/5546141/+files/VarLogDistupgradeAptclonesystemstate.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Tags added: apport-collected dist-upgrade hirsute
** Description changed:
I ran the installation to upgrade using
https://help.ubuntu.com/community/ImpishUpgrades
section:- Upgrading Ubuntu Desktops to 21.10
but got the following message:
The upgrade will
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1953524/+attachment/5546138/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1953524/+attachment/5546139/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1953524
apport information
** Attachment added: "VarLogDistupgradeAptHistorylog.txt"
https://bugs.launchpad.net/bugs/1953524/+attachment/5546140/+files/VarLogDistupgradeAptHistorylog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
I ran the installation to upgrade using
https://help.ubuntu.com/community/ImpishUpgrades
section:- Upgrading Ubuntu Desktops to 21.10
but got the following message:
The upgrade will continue but the
'/tmp/apt-dpkg-install-ZM0HnK/0993-npm_7.5.2+ds-1_all.deb' package may not
*** This bug is a duplicate of bug 1883370 ***
https://bugs.launchpad.net/bugs/1883370
** This bug has been marked a duplicate of bug 1883370
system-config-printer hangs when trying to change driver
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Description:Ubuntu 20.04.3 LTS
Release:20.04
system-config-printer:
Installed: 1.5.12-0ubuntu1.1
Candidate: 1.5.12-0ubuntu1.1
Version table:
*** 1.5.12-0ubuntu1.1 500
500 http://ca.archive.ubuntu.com/ubuntu focal-updates/main amd64
Packages
** Description changed:
To reproduce:
1. launch Qasmixer
2. In Mixer Device list, click on 'arcam-av'.
- 3. Qasmixer crashes every time.
+ 3. Qasmixer crashes every time and disappears from the screen.
$ ubuntu-bug qasmixer
/usr/share/apport/apport-kde:129: DeprecationWarning: an
Public bug reported:
To reproduce:
1. launch Qasmixer
2. In Mixer Device list, click on 'arcam-av'.
3. Qasmixer crashes every time and disappears from the screen.
$ ubuntu-bug qasmixer
/usr/share/apport/apport-kde:129: DeprecationWarning: an integer is required
(got type float). Implicit
** Description changed:
To reproduce:
1. Go to Extra Devices tab.
2. Select 'Nvidia 0,0 capture and playback 0' in Select Device to Edit
drop down menu.
3. Click on Capture Port Count minus button to reduce it 0. This causes
Studio Controls to hang. The plus and minus boxes
** Description changed:
+ To reproduce:
+
+ 1. Go to Extra Devices tab.
+
+ 2. Select Nvidia 0,0 capture and playback 0' selected in Select Device
+ to Edit drop down menu.
+
+ 3. Click on Capture Port Count minus button to reduce it 0. This causes
+ Studio Controls to hang. The plus and minus
Public bug reported:
Traceback (most recent call last):
File "/usr/bin/studio-controls", line 1039, in xdev_changed
sub_db['rate'] = int(self.xdev_rate_drop.get_active_id())
TypeError: int() argument must be a string, a bytes-like object or a number,
not 'NoneType'
ProblemType: Bug
Using live USB.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945870
Title:
Ardour crashes on launch
To manage notifications about this bug go to:
Public bug reported:
Program crashes on launch.
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: ardour 1:6.9.0+ds0~ubuntu-0ubuntu1
ProcVersionSignature: Ubuntu 5.13.0-16.16-lowlatency 5.13.13
Uname: Linux 5.13.0-16-lowlatency x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon
solved the bug already i cleared some things and made an update
On Sun, Sep 26, 2021, 05:40 ian <1609...@bugs.launchpad.net> wrote:
> Any update on this? Having issues with sound working for some time,
> than suddenly stopping with a buzzing sound. Will attempt to modify
> patch for most
Public bug reported:
This output is copied from here: https://github.com/systemd/systemd/issues/20516
because I have not been able to capture the error messages. However what I am
seeing is identical.
sd-umoun[2406]: Failed to unmount /oldroot: Device or resource busy
sd-umoun[2407]: Failed to
Please close this bug. Found this old thread which still works:
https://askubuntu.com/questions/462629/how-to-disable-sticky-edges-in-ubuntu-14-04-ubuntu-13-10-and-earlier-had-a-opti
The workaround there is to use ccsm to set Edge Stop Velocity to 0 -- it
actually won't set it less than 1, but it
Hmm I don't seem to be able to close it. Someone else will have to.
Still doesn't explain why some shortcuts kept working and others didn't, but
there you go.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I am closing the bug after finding
https://askubuntu.com/questions/1197990/how-to-add-shortcut-starter-to-
file-program-or-folder-in-the-desktop-or-menu
This is a feasible though not perfect workaround. It seems desktop
shortcuts are more or less deprecated in the old form.
Procedure:
sudo
Additional information.
lsb_release -a:
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04.3 LTS
Release:20.04
Codename: focal
screenfetch -n:
cmeo@rodan
OS: Ubuntu 20.04 focal
Kernel: x86_64 Linux 5.4.0-81-generic
Uptime: 28m
Packages: 2814
Public bug reported:
I have recently upgraded from 18.04 LTS and all my desktop shortcuts are
disabled and open in text editor, they do not run the applications.
There does not seem to be any clear, documented procedure for fixing this, and
I wonder why it has happened in the first place.
**
Public bug reported:
Just upgraded to this:
`
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=20.04
DISTRIB_CODENAME=focal
DISTRIB_DESCRIPTION="Ubuntu 20.04.3 LTS"
`
I've turned off sticky edges but they're still sticky--sometimes!
What's weird about this is that it's only a problem going from the primary
I was also affected by this. rm -rf ~/.config/compiz-1 fixed it. Now
dash is working as expected. compiz-1 was re-created.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880336
Title:
Dash search
I've also seen this. I wondered if the problem is that the libraries and
utilities haven't been updated. I doubt that it's intended for a version
0.8.3 ZFS send and receive to run on a ZFS 2.0.2. kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
The 5.11 HWE for 20.04 has version 2.02 of ZFS, but it doesn't update
zfsutils. I found that a zfs send | receive pipe gives an error message,
though it seems to work. I don't know for sure that this is due to the
version mismatch, but it seems dangerous to use 0.8.3
Public bug reported:
Ubuntu 18.04.05 LTS AMD64 was what I was trying to install.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14.15
ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.16
Public bug reported:
I can't upgrade.
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: ubuntu-release-upgrader-core 1:20.10.15
ProcVersionSignature: Ubuntu 5.8.0-53.60-lowlatency 5.8.18
Uname: Linux 5.8.0-53-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu50.6
Architecture: amd64
Id be happy to help make changes to the relevant tools so I don't need
the hacks in that repository if any maintainers would be interested.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918312
I'm well aware of the problem. I see lots of reports that produce
discussions that wander off with nothing done, even though there's an
actual fix in the thread. I run a moderately large site that uses
Kerberos extensively, and kerberoized NFS. I have a whole github
repository full of workarounds
833837
Bug has been fixed upstream :
https://sourceware.org/git/?p=lvm2.git;a=commit;h=2d1fe38d84d499011d13ae1ea11535398528fc87
It seems to be included in version 2.03.10 :
https://sourceware.org/git/?p=lvm2.git;a=shortlog;h=refs/tags/v2_03_10
How can we get this patch included in Ubuntu 20.04 ?
Ki
Public bug reported:
Upstream patch eb3a145789b9eedd39b56e1d76f412435abaa747 adds code to
rpc.svcgssd to set an expiration date for nfs contexts. (It doesn't
work, but that's the subject of a different bug.) That code treats the
date is int32. It is sent into the kernel using code that ends up as
Public bug reported:
Try to install ubuntu 18 into my old window7 PC. As I don't need the
Window 7 anymore. I decided to erase all old data and system. Then I get
the message " grub-efi-amd64-signed" fail to install to target.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity
Public bug reported:
A fatal error has been detected by the Java Runtime Environment:
3 #
4 # SIGSEGV (0xb) at pc=0x007d74cf8e30, pid=6492, tid=6493
5 #
6 # JRE version: OpenJDK Runtime Environment (11.0.7+10) (build
11.0.7+10-post-Ubuntu-3ubuntu1)
7 # Java VM: OpenJDK 64-Bit Server VM
dules-extra-5.4.0-58-generic 5.4.0-58.64
> ii linux-modules-extra-5.8.0-36-generic 5.8.0-36.40~20.04.1
> ii linux-modules-extra-5.8.0-38-generic 5.8.0-38.43~20.04.1
>
> I tried as Charles Green said: Switching to tty2 and then back to tty1 causes
> the boot to comple
+f(num)
On 1/20/21 12:18 PM, Ben Hoyt wrote:
> Charles, very interesting. Though I wonder if yours is a different
> problem, partly because it's not in tty mode at all (for me it's in a
> graphical mode, sometimes with the Dell logo up). I can't seem to switch
> to tty2 using Alt-F2 or
I've got the same issue on a system76 gazelle - I just reinstalled 20.04
hoping that this would fix the issue, but the 5.8.0-38 kernel does not
complete the boot cycle by itself.
I have found that switching to tty2 and then back to tty1 causes the
boot to complete
--
You received this bug
@jsarka, Thanks for those clear instructions! As it turns out I already
figured out (I hope) how to revert to kernel 5.4. That has brought back
my wifi. If other things go bonkers, I'll get 5.8 back and follow your
steps.
The bump to 5.8 broke several things on my system, which is why I first
Public bug reported:
Within the last couple of hours there was a batch of system updates
presented to me by Discover in KDE. I installed them and restarted like
it said to. Upon restart, there is no wifi. If I do `nmcli dev`, I no
longer see my wifi device listed at all. It used to be listed
I'm new to Linux, so bear with me, but...Within the last hour or so I
installed a bunch of system updates in KDE Discover, and suddenly wifi
stopped working after the enforced restart.
By "stopped working", I mean I have no internet connection via wifi and
`nmcli dev` no longer lists my wireless
Public bug reported:
ERROR 2002 (HY000): Can't connect to local MySQL server through socket
'/var/run/mysqld/mysqld.sock' (2)
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: mysql-server-8.0 8.0.22-0ubuntu0.20.04.3
ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
Uname: Linux
Public bug reported:
when I try the sudo apt-get update command to fix apps not showing in
the gnome-software center it produces the following error
E: The repository 'http://ppa.launchpad.net/ehoover/compholio/ubuntu
hirsute Release' does not have a Release file.
** Affects: apt (Ubuntu)
on an
old Dell PrecisionT7500, it's an old enough system it should detect
things and just work;perhaps another bug.
THANK YOU for the work you do. I LOVE Linux when it works, but have to
keep Windows for when things won't work on Linux. I hope this
information is helpful.
Charles
ProblemType: Bug
Public bug reported:
Check if you are using third party repositories. If so disable them, since they
are a common source of problems.
Furthermore run the following command in a Terminal: apt-get install -f
Transaction failed: The package system is broken
The following packages have unmet
Public bug reported:
Could not calculate the upgrade
An unresolvable problem occurred while calculating the upgrade.
If none of this applies, then please report this bug using the command
'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. If you want to
investigate this yourself the log
** Changed in: libreoffice (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883886
Title:
Print dialogue's height in Libreoffice Writer is too high
I just wanted to comment that this is more than just Slack "owning" apps
opened from inside Slack. It also messes up the audio/video setup inside
the "owned" app. For example, if I launch snap Slack before Chrome and
try to join a Zoom call from Slack, then my A/V options are limited only
to the
This problem is bad news for users of Office 2010 running under Wine on
Ubuntu 20.04
The latest stable version of Wine seems to fix this issue:
fonts-wine5.0-3ubuntu1
libkwineffects12 4:5.18.5-0ubuntu0.1
** Package changed: ubuntu => gpm (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884536
Title:
Multiple-monitor Set Up Makes Mouse-pointer Jump About in 20.04
To manage notifications
** Tags added: lubuntu
** Tags added: libreoffice libreoffice-writer
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883886
Title:
Print dialogue's height in Libreoffice Writer is too high to see
Public bug reported:
Information via $ lsb_release -rd:
Description:Ubuntu 20.04 LTS
Release:20.04
Information via $ apt-cache policy hplip
hplip:
Installed: 3.20.3+dfsg0-2
Candidate: 3.20.3+dfsg0-2
Version table:
*** 3.20.3+dfsg0-2 500
500
Public bug reported:
I have relatively recently loaded Ubuntu 20.04 to dual-boot on a Packard
Bell with Windows 10 Home 64-bit already installed. The mouse-pointer
moves and clicks perfectly when the PC has a single-monitor. However,
for work as a developer, I should like to use a dual-monitor
/status
1:6.4.2-0ubuntu3 500
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
Just FYI in case it is necessary: I am using Lubuntu 20.04 LTS with LXQt.
Best regards,
Owen Charles
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: libreoffice-writer 1:6.4.3
Public bug reported:
Situation:
Ubuntu 20.04 LTS after fresh install, NOT upgrade on desktop (had 16.04 LTS
before). Printer was attached during fresh install of 20.04 LTS and internet
connection, third party downloads ticked.
Bug description:
USB connected HP Envy 4524 All In One is
Thanks for the response. "Bug" was resolved by Bartosz, reference:
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1869524
now when I run $ which simple-scan
the result is:
/usr/bin/simple-scan
as expected.
When I run $ ldd -r /usr/bin/simple-scan
the result is:
n also have a look at the `shared-mime-info` package for another
way to associate the `.pages` file suffix to the
`application/vnd.apple.pages` media type.
Have a nice day,
Charles Plessy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have a Dell XPS L501X with exactly the same problem. The fix above:
> volume control -> configuration to Analog Stereo Duplex (unplugged)
I the only thing that has worked for me.
I've tried multiple other suggestions on other sites, include renaming
.config/pulse folder then reboot,
1 - 100 of 6610 matches
Mail list logo
