dpkg: error processing package libssl3:amd64 (--configure):
installed libssl3:amd64 package post-installation script subprocess returned
error exit status 1
Errors were encountered while processing:
libssl3:amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)
--
You received this bug
and also get this from plesk
Hello, Winston Derek
Some problems occurred with the System Updates tool on your server
mystifying-swartz.212-227-218-70.plesk.page. Please resolve them manually.
Reason: 2023-06-03 06:25:22 INFO: pum is called with arguments: ['--list',
'--repo-info', '--json
This is the current complete log if could help.
Execution failed.
Command: autoinstaller
Arguments: Array
(
[0] => --select-product-id
[1] => plesk
[2] => --select-release-current
[3] => --upgrade-installed-components
)
Details: Downloading file products.inf3: 0%
Downloading file
I'm afraid I cant access the logs when that happened. Actually I don't
know the exact date that this started happening on the updates. The
thing is that I cant use apt anymore, I wanted to install a package to
create a complete copy of the server in case something goes wrong.
Maybe the best
This is what I got from ps faux | less" and "/frontend.
Do you think is ok to kill the process? I can't think about that update
running, has I always get the same response since 7 days.
root1422 0.0 0.0 15424 7740 ?Ss Mar30 2:37 sshd:
/usr/sbin/sshd -D [listener] 0 of
I have the same issue after running "sudo fuser -v
/var/cache/debconf/config.dat".
I get this result.
USERPID ACCESS COMMAND
/var/cache/debconf/config.dat:
root 1224024 F frontend
But no idea what process is it and if I can just kill it. Can I?
This is
Using Ubuntu 20.04.3 latest update Oct 19th
After the one but last update Oct 10th suddenly I had a problem
resolving DNS. Before the update my /etc/resolv.conf read :
nameserver 127.0.0.53
In my netmanager settings I had/have entered 2 DNS-Server IP adresses of
my ISP : 1xx.2xx.xxx.21
Sorry typo in my previous message ; it should read
I tried overwriting /run/systemd/resolve/resolv.conf with the correct
nameservers and then applied your solution :
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd
OS Ubuntu 20.04.3 LTS
After a recent update a working laptop suddently developped the following
problem :
- DNS problems for al Internet related apps
- Ping : termporary failure in Name resolution
editing manually allows internet access for short term until systemd-resolve
overwrites the
Public bug reported:
linux-image-5.8.0-48-generic also appear in the error list.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: initramfs-tools 0.136ubuntu6.3
ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-48-generic x86_64
NonfreeKernelModules:
-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
Uname: Linux 5.8.0-41-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.5
Architecture: amd64
AudioDevicesInUse:
- USERPID ACCESS COMMAND
- /dev/snd/controlC0: derek 1460 F pulsea
sion: 2.20.11-0ubuntu50.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: derek 1460 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 6 20:48:52 2021
InstallationDate: Installed on 2021-02-0
Have collected alsa-info output from non-working and working situations
as per the notes at
https://bugzilla.kernel.org/show_bug.cgi?id=195457#c11
echo 1 | sudo tee /sys/module/snd_hda_codec/parameters/dump_coef
sudo alsa-info --no-upload --output /home/derek/alsainfo_bad.txt
** Bug watch
0.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: derek 1460 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 6 20:48:52 2021
InstallationDate: Installed on 2021-02-04 (2 days ago)
InstallationMedia: Ubuntu 20
rtVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gdm1903 F pulseaudio
derek 2464 F pulseaudio
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-03-23 (5 days
Use:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gdm1903 F pulseaudio
derek 2464 F pulseaudio
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-03-23 (5 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bioni
Use:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gdm1903 F pulseaudio
derek 2464 F pulseaudio
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-03-23 (5 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver"
InUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gdm1903 F pulseaudio
derek 2464 F pulseaudio
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-03-23 (5 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bioni
Use:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gdm1903 F pulseaudio
derek 2464 F pulseaudio
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-03-23 (5 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver"
Use:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gdm1903 F pulseaudio
derek 2464 F pulseaudio
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-03-23 (5 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver"
d64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gdm1903 F pulseaudio
derek 2464 F pulseaudio
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-03-23 (5 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gdm1903 F pulseaudio
derek 2464 F pulseaudio
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-03-23 (5 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bioni
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gdm1903 F pulseaudio
derek 2464 F pulseaudio
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-03-23 (5 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bioni
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gdm1903 F pulseaudio
derek 2464 F pulseaudio
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-03-23 (5 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bioni
Use:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gdm1903 F pulseaudio
derek 2464 F pulseaudio
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-03-23 (5 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver"
ivation Cmd: "modprobe snd_hda_intel"
Config Status: cfg=new, avail=yes, need=no, active=unknown
+ ---
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.6
+ Architecture: amd64
+ AudioDevicesInUse:
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC0: gdm1903 F..
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gdm1903 F pulseaudio
derek 2464 F pulseaudio
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-03-23 (5 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bioni
Use:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gdm1903 F pulseaudio
derek 2464 F pulseaudio
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-03-23 (5 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver"
See post #5 at https://bugs.launchpad.net/ubuntu/+source/alsa-
driver/+bug/1784485
It references another Linux variant (eww). But, reading their thread
you will find that they made a patch in December 2018 to solve the 294
issue. Then, the bug report for Ubuntu let to y'all doing the same.
No, my point is that I tried other kernel versions to see if it was
patched. No kernel world with ACL274 on this machine. Windows works
great.
4.18, installed with Ubuntu 18.04.2, to 5.0 were tested with the same
results. The issue persists.
Sorry for the confusion.
How do I get this to stop
Apologies my first run of apport was mainline 5.0. I immediately
rebooted and use a standard default kernel for 18.04. I deleted both
mainlines since they didn't solve my issue anyway.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1821936
Title:
ALC274 unsupported
Status in
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1821936
Title:
ALC274 unsupported
Status
Public bug reported:
I find this to be an issue with current LTS 18.04's latest 4.19 kernel.
I tested this on mainline 4.20 and 5.0 kernels as well.
No audio because ALC274 not properly loaded for use, so no audio output.
A related card had a similar bug, which was fixed, and may be of use in
Public bug reported:
Crash Report when resuming from sleep.
Similar to https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1586223
This is a Sager NP8278 (Clevo P170SM-A) laptop with an Nvidia GeForce GTX 970M,
driver 390.77
The crash log doesn't have much info in it IMO, but I uploaded here
Unfortunately, this bug is unlikely to be fixed upstream:
"ConsoleKit is currently not actively maintained. The focus has shifted
to the built-in seat/user/session management of Software/systemd called
systemd-logind!"
https://www.freedesktop.org/wiki/Software/ConsoleKit/
--
You received this
The message is emitted by glib:
https://gitlab.gnome.org/GNOME/glib/commit/a919be3d39150328874ff647fb2c2be7af3df996
The commit log description is: "gmain: Warn when g_source_remove()
fails". So why is it calling g_critical() instead of g_warning()?
Obviously, it's not a critical error, if people
Public bug reported:
havent got a clue what happened
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libpam-systemd:amd64 229-4ubuntu21.4
ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134
Uname: Linux 4.4.0-131-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture:
Same issue here. Same exact install method.
--
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/1767880
Title:
apparmor prevents Chromium (snap) to run the 2nd time
Status
Public bug reported:
Release: Artful Aardvark 17.10
Package version: 1.0.28-4
The current version of libsndfile1-dev is not able to be marked Multi-
Arch: same, because the examples it provides includes an autoheader (?)
generated config.h file, which has architecture-specific defines like
Public bug reported:
Release: Artful Aardvark 17.10
Package version: 1.12.3-1
I modified the debian/gir1.2-gstreamer-1.0.install file to put its
girepository-1.0 files under the architecture-dependent directory, by
removing the target specifier (usr/lib). As far as I can tell, the non-
Public bug reported:
On my current version of Ubuntu (17.10) and packages libsrtp0 and
libsrtp0-dev at version 1.4.5~20130609~dfsg-2ubuntu1, these packages do
not actually have multiarch support.
I was able to download the package source, add Multi-Arch: same to both,
and build and install
Public bug reported:
Release: Artful Aardvark 17.10
Package version: 0.34.0-1
After modifying libpixman-1-dev to be Multi-Arch: same, and checking
that it installs architecture-specific files appropriately, and
successfully building and installing both the amd64 and i386 versions
simultaneously,
** Description changed:
Release: Artful Aardvark 17.10
Package Version: 0.7.1-2
As far as I can tell (after creating a local patch and building and
installing them as Multi-Arch: same) libxkbcommon-dev and
libxkbcommon-x11-dev can be safely marked as Multi-Arch: same with no
Public bug reported:
Release: Artful Aardvark 17.10
Package Version: 0.7.1-2
As far as I can tell (after creating a local patch and building and
installing them as Multi-Arch: same) libxkbcommon-dev and
libxkbcommon-x11-dev can be safely marked as Multi-Arch: same with no
additional changes.
I use KeePass 2 on Mono so I'm not too bothered by this. Wifi and
NetworkManager still have problems though.
On Google Chrome and likely Chromium I fixed the 2 minute start wait by
adding --password-store=basic the command line. You can add it the Exec
entry in your desktop file or by editing the
I am also having this issue. CPU pegged, large /var/log/wtmp. Also
running ProFTPd.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/1316830
Title:
I fixed the install by mv the current Trolltech.conf file to
Trolltech.conf.bak and running apt-get -f install. After running apt-get
Trolltech.conf does not exist so I don't know why it's complaining if
it's not going to write anything.
ls /etc/xdg/
autostart menus sni-qt.conf systemd Thunar
Public bug reported:
either python or software center not sure
ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: apport 2.19.1-0ubuntu3
ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6
Uname: Linux 4.2.0-23-generic x86_64
ApportLog:
ApportVersion: 2.19.1-0ubuntu3
Architecture:
I got this message on trusty 14.04:
Processing triggers for hicolor-icon-theme (0.13-1) ...
(gtk-update-icon-cache-3.0:31711): GdkPixbuf-WARNING **: Cannot open
pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk-
pixbuf-2.0/2.10.0/loaders.cache': No such file or directory
This
*** This bug is a duplicate of bug 619003 ***
https://bugs.launchpad.net/bugs/619003
** This bug has been marked a duplicate of bug 619003
GdkPixbuf-WARNING **: Cannot open pixbuf loader module file
'/usr/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache'
--
You received this bug notification
Public bug reported:
It is a bug for any display manager to read .profile--you guys are
absolutely killing me with this. The user's .profile is to be read by
the shell, on interactive shell (i.e. terminal) logins ONLY. The man
page for bash explains this in detail; it's also discussed in the
See also Bug #1468834.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1468832
Title:
lightdm sources .profile
Status in lightdm package in Ubuntu:
New
Bug
Public bug reported:
There is a decades-old standard protocol for starting up a user's X
session, which requires display managers to source the user's
~/.xsession file. lightdm fails to do this. See also Bug #1468832.
** Affects: lightdm (Ubuntu)
Importance: Undecided
Status: New
Sigh. Display managers should NEVER source .profile at all... that
file is exclusively for interactive shells, as is explicitly stated in
all of the man pages of every shell ever. I just opened Bug #1468832
about this, where I also explained how to properly accomplish what
people want here.
--
See also Bug #1468834.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/794315
Title:
lightdm forgets to source /etc/profile and ~/.profile
Status in Light Display
Try:
man xsession
The X window system has been reading this file since forever.
--
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/1468834
Title:
lightdm does not source
@Myself: in my description I repeatedly used interactive shell when I
meant login shell instead. The distinction is important, (and thus
the shell makes the distinction)--the user's .profile is only sourced in
the latter case. On all other interactive shells it sources .bashrc
instead. This is
Also slight correction: BASH does NOT automatically source .bashrc on
login shells; so .profile would need to source the environment file as
well.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
I don't follow the reason for closing this... It seems like maybe you're
thinking I said this bug is all wrong, but it's not. The point is that
instead of *sourcing* $HOME/.xsession, the Xsession system script should
*exec* it if it exists, completely bypassing the rest of the system
Xsession
From the debian manual:
any user who defines ~/.xsession or ~/.Xsession is able to
customize the action of /etc/X11/Xsession by completely overriding the
system code.
It does (or did) that by executing the script via exec...
--
You received this bug notification because you are a member of
In point of fact .xsession is supposed to be an executable shell script
with a shebang line, it's not supposed to be sourced at all, or at least
historically that has always been the case. Theoretically the .xsession
file could be a C shell script so as long as it is executed instead of
sourced,
Which is a good point actually... what if the user is a C shell user?
How does sourcing .profile help them? The classic way of setting this
up is clearly far superior.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm
It may well have, but it's a change that's bad. For what it's worth,
the Debian manuals still document this:
https://www.debian.org/doc/manuals/debian-
reference/ch07.en.html#_customizing_the_x_session_classic_method
I've been a member of the Linux community for 20 years--Take comfort in
the
I suspect that this bug is a duplicate of
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1350393
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
This may be a duplicate of bug 996791.
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/996791
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/1350393
@Gunnar, 0.6.35-0ubuntu7.2 may be improve performance in some cases, but
it does nothing to avoid the infinite hang that I characterized in
comment #4. The fact that it calls user_language_validate() just once
in the context of an LDAP user when the LDAP client isn't fully ready
will cause
Why lightdm behaves the way it does…
In common/user-list.c, load_users() calls load_passwd_file(). The
intended code path is is for load_passwd_file() to make use of the
org.freedesktop.Accounts.ListCachedUsers DBus call.[1] However, due to
the accounts-daemon failure[2], it falls back on the
I have found something close to a root cause, and I observe this hang
100% of the time under the following conditions:
1. Packages libnss-ldap_264-2.2ubuntu4.14.04.1 and
accountsservice_0.6.35-0ubuntu7.1 are installed.
2. /etc/nsswitch.conf contains passwd: files ldap
3. An LDAP user has logged
Ubuntu 14.04 installed from Canonical Live CD + all available upgrades
to 24 October 2014. Keyboard Input Methods used to select - English -
(English UK extended Winkeys). The seolected setting is retained for
current session only. Keyboard input reverts to English US on next boot.
--
You
I think this bug (and1310056, dup of this bug) should not be closed as
wont-fix, it should be reopened and reassigned to whatever software
component (Unity, presumably) is making this behavior change impossible.
It's absolutely shameful that the Linux desktop has been consistently
and brutally
Confirmed in 14.04.4
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/505278
Title:
ssh-add -D deleting all identities does not work. Also, why are all
identities
72 matches
Mail list logo
