Yeah, I was confused by this at first too. Here's a hint, try "apt-mark
showhold":
$ apt-mark showhold
$
If nothing is printed (as above), then the "issue" PRESUMABLY isn't
local to your system; ergo, the cause is PROBABLY at the server, such as
a phased update. Relax. It will probably
I had what I _thought_ originally was a very similar issue with Kubuntu 20.04.1
LTS
on a Clevo-NJ70, but further investigation suggests my problem,
despite the same-ish messages, is somewhat different.
See bug #1904075 ("[NJ5x_NJ7xLU, Realtek ALC293, Speaker, Internal] No
sound at all (or so KDE
** Summary changed:
- GNU sha256(1) &tc --check (-c) output depends on order of --quiet and --warn
+ GNU sha256sum(1) &tc --check (-c) output depends on order of --quiet and
--warn
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribe
Obviously, I meant sha256sum(1) in the bug's title! (*sighs*)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/1902311
Title:
GNU sha256(1) &tc --check (-c) output depend
Public bug reported:
The output of GNU sha256sum --check (or -c), and related tools (i.e., sha1sum,
sha224sum, sha384sum, and sha512sum) depends on the order of the --quiet and
--warn options. This is counter-intuitive, not documented in the man(1) pages,
and unnecessary.
Simple example:
1$ d
Public bug reported:
After this morning's upgrade to "whoopsie 0.2.62ubuntu0.2"
plus "libwhoopsie0 0.2.62ubuntu0.2"(fix to bug #1830865),
whoopsie repeatedly crashes with a segfault (in what seems to be libc?).
An excerpt from /var/log/syslog (slightly redacted):
Oct 30 08:33:06 [REDACTED] system
This is not a bug, it is expected & reasonable behaviour.
The `-p DIR' and `--tmpdir[=DIR]' mktemp(1) options
are the same, excepting that the argument is
mandatory for -p and optional for --tmpdir. (See
the manpage (`man mktemp') or try `mktemp --help'.)
That is, the following are equivalent:
Same result for 4.4.10
On Jun 9, 2016 3:56 PM, "Levente Ábrók" wrote:
> Some news.
> I updated the kernel to 4.4.13. Now I don't have error messages is dmesg.
> Added radeon.dpm=1 radeon.modeset=1 to /etc/default/grub file (not sure if
> everything is needed).
> sudo update-grub and reboot
> Alth
# /etc/default/grub
...
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash radeon.modeset=1 radeon.drm=1
radeon.runpm=0"
...
Result of `DRI_PRIME=1 glxgears -info` attached. Visible and smooth
animation runs (no black window).
** Attachment added: "glxgears-2"
https://bugs.launchpad.net/ubuntu/+source
** Description changed:
dmesg shows issues with being able to use the discrete graphics card
(relevant dmesg lines attached).
- Grub does pass "radeon.modeset=1" and "radeon.startpm=1" to the kernel.
- I've tried all combinations and same results occur.
+ Grub does pass "radeon.modeset=1" b
** Attachment added: "glxgears"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1581270/+attachment/4661633/+files/glxgears
--
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/bug
Public bug reported:
dmesg shows issues with being able to use the discrete graphics card
(relevant dmesg lines attached).
Grub does pass "radeon.modeset=1" and "radeon.startpm=1" to the kernel.
I've tried all combinations and same results occur.
Attached are relevant dmesg lines, grep'd with 'd
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1581270/+attachment/4661631/+files/syslog
--
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/15
13 matches
Mail list logo