This is a problem in Mantic too.
And if you never fix it it will be a problem in the next LTS release.
Just as it is a problem in the current LTS release.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to powermgmt-base in Ubun
Created attachment 144559
New crash information added by DrKonqi
gwenview (21.08.1) using Qt 5.15.2
- What I was doing when the application crashed:
Browsing through images with Dolphin. Select to open one in Gwenview.
Crashes every time.
-- Backtrace (Reduced):
#4 __pthread_kill_implementatio
(In reply to Gordon Lack from comment #21)
Seems to be related to how old the jpegs are.
2016 and earlier it crashes.
2017 and late its OK.
Roughly.
If I run gwenview on the command line for a failing one this is what I
see reported:
[gmllaptop]: gwenview DSCN1657.JPG
(In reply to Lukáš Karas from comment #24)
> Here is my proposed fix in Gwenview:
> https://invent.kde.org/graphics/gwenview/-/merge_requests/125
Do we need a prod on the libexiv2 package as well to indicate that it
needs an update to fix the cause of the crash? (The fix for gwenview to
handle suc
Public bug reported:
The replaces_id parameter to org.freedesktop.Notifications.Notify no longer
works correctly at 21.10.
It is OK on 21.04.
At 21.10 if a message with replaces_id === x ever times out then any
further message sent with that replaces_id never gets shown. The
timeout-over seems
This python program shows the problem
*=*=* Cut here *=*=*
#!/usr/bin/python3
# -*- coding: utf-8 -*-
#
from pydbus import SessionBus
from time import sleep
# Global constants
#
item= "org.freedesktop.Notifications"
path= "/org/freedesktop/Notifications"
interface
** Description changed:
The replaces_id parameter to org.freedesktop.Notifications.Notify no longer
works correctly at 21.10.
It is OK on 21.04.
- At 21.10 if a message with replaces_id === x ever times out then any
+ At 21.10 if a message with replaces_id == x ever times out then any
fu
Public bug reported:
Packages are now being released in Phased updates.
However, it seems that whereas apt (and apt-get, and even Discover?) are
aware of this, the command, "apt list --upgradeable" is unaware of it
and will report that there are upgradable packages which apt(-get)
upgrade will *n
Doesn't alter the point that if "apt --list --uprgadeable" doesn't
report what "apt update" would update then it makes it impossible to
script a check for whether there is anything to update.
And given that KDE no longer has any update warning in the System Tray
such a facility is needed, otherwis
I've tested /lib/systemd/systemd-ac-power on my laptop (which gives 0/1
for mains/battery) and it now returns 0 (mains) for my NUC10i3FNYHN.
(But the fix isn't in Lunar for on_ac_power.)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subs
/lib/systemd/systemd-ac-power works (on lunar). on_ac_power still does
not.
Perhaps on_ac_power should just be made a symlink to this - or the
script should exec that systemd executable if it exists?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
I have this issue on an Intel NUC (NUC10i357FN).
The sysfs entry for the power supply does contain a usb_type entry for
it, which contains:
[nuc]: cat usb_type
[C] PD
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to powermgm
Possibly this?
--- /bin/on_ac_power2019-07-20 16:43:51.0 +0100
+++ ./on_ac_power 2022-09-22 01:44:53.412558622 +0100
@@ -28,6 +28,17 @@
type="$(cat "${FN}/type")"
case "${type}" in
Mains|USB*|BrickID|Wireless)
+# If USB, is it input or output?
This is still an issue in Kinetic.
And it's now stopping unattended_upgrades running, as these (now?) have a
condition of ConditionACPower=true
which is not being met even though the system is running on AC (and has no
other way of running).
--
You received this bug notification because you ar
Actually, it turns out that systemd has its own code to check for AC
power (same/similar logic - perhaps this should be done in a single
system service rather than duplicated between sub-systems?).
So I'll open a bug for this against systemd as well and cross-reference
them.
--
You received this
Public bug reported:
The ConditionACPower testing code does not work correctly on some
systems. This prevents the unattended-updates systemd service running as
it thinks that a system (a NUC10i3FNYHN) is running on battery. It isn't
- it just has a power supply that can *provide* power over USB.
This also affects various other services.
apt-daily
e2scrub_all
logrotate
man-db
plocate-updatedb
** Description changed:
The ConditionACPower testing code does not work correctly on some
systems. This prevents the unattended-updates systemd service running as
it thinks that a system (a N
This has (apparently) been fixed by
https://github.com/systemd/systemd/pull/24220
** Also affects: e2fsprogs (Ubuntu)
Importance: Undecided
Status: New
** Also affects: logrotate (Ubuntu)
Importance: Undecided
Status: New
** Also affects: man-db (Ubuntu)
Importance: Undeci
** Also affects: unattended-upgrades (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
https://bugs.launchpad.net/bugs/1998872
Title:
unattended-update
This is still an issue in 23.04 (lunar)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1949615
Title:
Notify method not working correctly in 21.10 (impish)
Status in dbus pa
This is *still* an issue nearly a year on.
A better test line is actually this, which checks for anacron being
present before checking whether it is enabled:
( test -x /usr/sbin/anacron && systemctl -q is-enabled anacron )
The () are needed.
--
You received this bug notification because you ar
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1807286
Title:
systemd SEGV freezing on instal
Public bug reported:
The packagekit package has just been updated by discover (Kubuntu) from 1.1.7-1
to 1.1.7-1ubuntu0.1.
Discover reported that the packagekit daemon had crashed.
The resulting dpkg status is:
[parent]: dpkg-query -l 'packagekit*'
Desired=Unknown/Install/Remove/Purge/Hold
| Sta
This is still a bug in 18.04 (and was in 17.10 as well).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/688148
Title:
Unexpected behaviour when choosing "Other problem"
St
Public bug reported:
/etc/crontab uses
test -x /usr/sbin/anacron
for whether anacron is handling the daily/weekly/monthly cron jobs on a system.
This means that if anacron is installed it is assumed to be running.
However, this is a service, and can be disabled and since the package is
insta
Actually
systemctl -q is-enabled anacron 2>/dev/null
works to, and is shorter (and more intuitive).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cron in Ubuntu.
https://bugs.launchpad.net/bugs/1759846
Title:
Incorrec
> A lot of the time, people's login name gets renamed from a central
authority...
Another solution would be to get that policy changed, as it's not a good one.
Such a policy would be a nightmare in any industry that has to track who does
what for regulatory purposes, where user ids should be cons
It's not new. This has been reported before.
See:
https://bugs.launchpad.net/mos/+bug/1475019
--
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/1733070
Title:
ntp apparmo
Oh, and there is also:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1727202
with a proposed fix from a few a days ago, at least for some of this.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
htt
This isn't a 17.10 regression - it's been happening for a few years,
e.g.:
https://bugs.launchpad.net/mos/+bug/1475019
And, FWIW, I added the flags=(attach_disconnected) to the config file
yesterday on one of my systems and whereas it does seem to have removed
the operation="sendmsg" reports,
Happened again last night when:
gir1.2-packagekitglib-1.0
libpackagekit-glib2-18
packagekit
packagekit-tools
went from 1.1.9-1ubuntu2 to 1.1.9-1ubuntu2.18.04.1.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
>> I don't think there is a solution for this problem.
So why has it only started to happen recently?
What about treating it like a kernel update - don't restart the process
but schedule/request a reboot?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pack
Has it been fixed in/checked for 18.10 (Cosmic)?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1790613
Title:
Regression: packagekit crashes updating itself to a new v
I had a problem with a *missing* internal microphone today (well, I spotted it
today - probably been like this for ages...).
Note that this was PulseAudio saying that there were no input devices.
The problem (as I eventually spotted) was that I'd set the Profile to be
Analgue Stereo Output (under
Public bug reported:
I'm on 20.04 LTS (Focal Fossa). (Kubuntu)
openssl (I'm on 1.1.1f-1ubuntu2) appears to now be set to use a minimum
of TLSv1.2
This is despite the fact that the Changelog
(https://launchpad.net/ubuntu/+source/openssl/+changelog) says:
Revert "Enable system default confi
>> You can override this via command-line, a system config file, or a
local config file + environment variable pointing to it.
Some hints as to how to achieve that "local config file + environment variable"
would be extremely useful.
I've tried it and got nowhere, although I know that setting SEC
Also, wtmpdb only seems to record network logins. It doesn't record
console or X session logins.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2084854
Title:
last and
That might work for last - although it ignores the fact that
/var/log/wtmp is still being produced when there is no utility to read
it (and the btmp file for failed logins)
But there appears to be no replacement for lastb, and I'm *far* more
interested in who is trying to login and failing.
--
Y
Although it seems that, for my purposes, I can parse the output of
utmpdump.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2084854
Title:
last and lastb missing in 24.
Public bug reported:
The last and lastb commands have disappeared from util-linux at 24.10!
This is odd, as the binaries from 24.04 actually run on 24.10, so the
data is clearly still being collected and in the same format.
Ubuntu: 24.10 (Oracular Oriole).
Package: util-linux
Version: 2.40.2-1u
This is noted as Fix Released in Oracular.
This is INCORRECT. This command is STILL BROKEN in Oracular.
This is the result of running it on one of my Intel NUCs (which, I can
assure you, is *always* on AC power, as it has no battery).
[ganuc]: sh -x /usr/sbin/on_ac_power
+ set -e
+ OFF_LINE_P=
You can get *bad logins* by using utmpdump on btmp (tty logins are type
6).
But that requires the btmp file, and once you collect that you should
really be supplying lastb to process it, as utmpdump is supposed to just
be a debugging tool (see its man page).
--
You received this bug notification
>>> Question to the reporter: does systemd-ac-power work correctly in
the system you have where unpatched on_ac_power is incorrect?
Yes. See #7, where I suggested this (once the systemd version was
fixed).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pack
Would it not be simpler to assume that on_ac_power is True unless you
can find a working battery?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to powermgmt-base in Ubuntu.
https://bugs.launchpad.net/bugs/1980991
Title:
/usr
https://answers.launchpad.net/ubuntu/+source/util-linux/+question/820873
Which is, despite the url, a question to the developers.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.ne
Invert the logic?
Perhaps just look for any /sys/class/power_supply/BAT?/current_now that is
non-zero?
If any found, it's running on battery.
Else it must be on a mains-supply.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
[ganuc]: SYSTEMD_LOG_LEVEL=debug systemd-ac-power
port0: The USB type-C port is in power sink mode.
port1: The USB type-C port is in power sink mode.
ucsi-source-psy-USBC000:001: The USB type-C device has at least one port in
power sink mode.
ucsi-source-psy-USBC000:001: The power supply is curren
All of my Intel NUcs report the type-C port being in sink mode.
None of them can be powered by a USB-C port.
Even plugging in an external drive leaves the system reporting them all
in sink mode.
According to https://www.ti.com/lit/wp/slyy109b/slyy109b.pdf that is correct.
A sink is a port that wi
>> I think we are advised to look in other log files to track failed
logins
Happy to do that if they exist, but I haven't found such a log.
wtmpdb doesn't store them at all.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ut
You're right. journalctl does have the info.
And it does also log failed local attempts (although it seems to log all
unknown accounts as UNKNOWN, rather than what was actually tried).
>> Any suggestions or improvements are welcome.
I use a Perl script to get all failures since the last time it
50 matches
Mail list logo
