Public bug reported:
The cryptsetup(8) manual page says (spurious lines omitted):
reencrypt or --active-name []
Run resilient reencryption (LUKS2 device only).
[...]
Reencryption process may be safely interrupted by a user via SIGTERM
signal (ctrl+c).
No: Control-C g
Apologies, I forget: You may want to change the title from
Sorry, I dont speak English
to something about the problem. As an example:
Программа установки завершила работу и отправила отчет (Installer
crashed and sent this report)
To change the title click on yellow circle next to the ti
Sorry, I do not have any idea.
Now that there is a description of what happened,
perhaps someone who is an expert on the installation
can study the problem. That may not happen quickly.
>From my own experience, if the system is basically
working despite the installer being upset, then the
system
Attached is the output of dmesg(1) shortly after a cold cold-boot when the
audio output seems Ok:
The KDE thing knows about the H/W and functions as expected, and all seems
happy.
This is mostly for information and comparison with the report's log (when
things (well,
at least the module & KDE) d
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
Please explain the problem in your language.
You do not need to use English.
Пожалуйста, объясните проблему на своем языке.
Вам не нужно использовать английский.
Pozhaluysta, ob"yasnite problemu na svoyem yazyke.
Vam ne nuzhno ispol'zovat' angliyskiy.
(Via Google Translate, I do not speak Russia
Public bug reported:
This is an odd one (or so it seems to me)...
Sometimes, after booting, my log is filled with messages similar to:
[ 208.746660] snd_hda_intel :00:1f.3: No response from codec, resetting
bus: last cmd=0x20a3b000
** 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
Bugs, which is subscribed to Ubuntu.
http
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
Obviously, I meant sha256sum(1) in the bug's title! (*sighs*)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902311
Title:
GNU sha256(1) &tc --check (-c) output depends on order of --quiet and
--
Public bug reported:
stegosuite(1) is a too-simple bash(1) script:
1 #!/bin/bash
2
3 DIRNAME="/usr/share/stegosuite"
4 STEGOSUITEJAR=$(echo $DIRNAME/stegosuite-*.jar)
5
6 # Setup the classpath
7 if [ ! -f "$STEGOSUITEJAR" ]; then
8 die "Missin
Public bug reported:
The weborf(1) manual page says, when describing the --cache (-C) option,
"[...] To flush the cache (empty that directory) you must send SIGUSR2
to the process. It is advised to flush the cache on reboot (manually
or with kill) because some items might be invalid after a reboo
This 2018 problem report (with the same name as this report!),
https://bitbucket.org/maugier/shatag/issues/9/modulenotfounderror-no-module-named
indicates that the problem was found and fixed.
It also mentions "shattr by @weakish clone shattr", which I seems to mean this
clone/rewrite,
https://
Public bug reported:
$ shatag --help
Traceback (most recent call last):
File "/usr/bin/shatag", line 11, in
load_entry_point('shatag==0.4.1', 'console_scripts', 'shatag')()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 480, in
load_entry_point
return get_distr
Follow-up to #2 (again, please note I am NOT the originator of this
report).
Searching through some old notes/logs, I found the attached information
about _my_ WiFi H/W (excerpted and slightly redacted because I have not
checked the complete notes/logs for sensitive information). Abbreviated
summ
I also use okular v1.3.3 all the time without the described issue.
It *might* have something to do with the _particular_ PDF you are
trying to open. I would suggest that, if possible, you attach the
failing PDF to this bug report.
Also, it's unclear (to me) from your description if the PDF which
NOTE: I am NOT the originator of this bug report,
but have a similar(? identical?) problem.
My machine is an Acer Aspire E17 E5-722-425Q,
and the built-in microphone (and also the mouse pad)
has never(?) been detected. (Since I use a USB mouse
and a USB headset-with-microphone, neither pr
Public bug reported:
$ sudo apt install ...
[...]
Unpacking python-pysqlite2-dbg (2.7.0-1) ...
Selecting previously unselected package python-pysqlite2-dbgsym.
Preparing to unpack .../22-python-pysqlite2-dbgsym_2.7.0-1_amd64.ddeb.deb ...
Unpacking python-pysqlite2-dbgsym (2.7.0-1) ...
dpkg: error
Here is a hypothesis for what is going on: It's working,
doing what it was told to do, but what it was told to do
is probably not what is intended.
First, a closer look at the example input PDF shows there
is an oddity (not wrong, just odd):
$ pdfinfo -box Micro-Magic_Plan_2016_V2.pdf
[...]
Now confirmed, using the PDF kindly attached in #3.
There actually is some output, the output file `Plan.pdf' has been created
and is --- slowly --- relentlessly growing. It grew to c.68MiB by letting
pdfposter(1) run for 10mins (real-time) solid, fully occupying one of my
cores (100% of one CPU).
Make sure your unit really is an r8169, and not an r8168.
Whilst (as I understand it) the r8169 module is supposed
to work with an r8168, at least on my laptop (Acer Aspire E17
(E5-722-425Q), currently 18.04 (up-to-date)),
using the r8169 module has resulted in "flakely" behaviour
for as long as I
I just tried (also 0.6.0 on 18.04 (up-to-date)) and it seemed to work.
(Unfortunately, I canNOT attach the test PDF I used because it contains
very sensitive information.)
This suggests there is something in the PDF you used which is causing this
behaviour.
As such, if it is possible, perhaps you
This problem does not seem to happen on 18.04:
# lsb_release -a
LSB Version:core-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch
Distributor ID: Ubuntu
Description:Ubuntu 18.04.3 LTS
Release:18.04
Codename: bionic
#
# atop -V
Version: 2.3.0 - 2017/03/25 09:59:59
I concur. Whilst 18.04's TeXlive-2017(?) is usually fine (for me),
it's age is starting to present a few annoyances.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855315
Title:
Please upgrade it t
This has also annoyed me, and is perhaps more of an issue (for me) as sometimes
some of the
functions don't function. For instance, at the moment I've lost bluetooth
completely; the
lack of bluetooth button hotkey feedback just adds to the confusion.
(The loss of bluetooth is known to unrelated
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
Starting with Disco Dingo (19.04) there is a new package `zram-tools'
which is roughly configurable as per many of the above wishes.
https://launchpad.net/ubuntu/+source/zram-tools
>From eyeballing it, it seems like it should work on earlier releases
(but see caveats below); however, I have no
I presume this is referring to the hardcoded calculations
for NRDEVICES and the critical calculation using it:
mem=$(((totalmem / 2 / ${NRDEVICES}) * 1024))
(There are a few others that perhaps should be more easily
adjusted.) Yes, this also has annoyed me, albeit, to-date,
the hardcoded valu
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:
CORRECTION: Apologies, I just realised (when attempting to modify su-to-root)
that lxsudo(1) & friends can only become superuser "root"; an arbitrary user
is not supported. Despite the name, su-to-root can become an arbitrary user;
i.e., it is not restricted to superuser "root". Hence, at least i
Public bug reported:
The su-to-root script has a limited selection of "known" su(1)/sudo(1)
front-ends.
A missing front-end is lxqt-sudo(1), i.e., lxsudo(1) and lxsu(1), which would
seem
to be a "natural fix" for LXqt as used by Lubuntu 18.10 (cosmic).
ProblemType: Bug
DistroRelease: Ubuntu 18.
That fix (commit 9a081a80b7c9 ("fix segfault on strtol")),
which is in usbauth v1.0.1, does seem to have fixed this
problem. Ubuntu 19.04(? disco) contains usbauth v1.0.1,
and installing that package on my 18.04 LTS (Ubuntu bionic)
system fixed the segfault.
Testing with invalid serial="..." valu
Public bug reported:
Under not entirely clear conditions, usbauth(1) will segfault
(see attached kern.log excerpt). In this particular case,
it is known the segfault is caused by the serial="..." Attribute
in /etc/usbauth.conf
allow idVendor==0x059f idProduct==0x1061
serial=="75686ff5
Public bug reported:
The current version of checkflac (in 18.10 LTS / Cosmic) is badly out-
of-date:
* It cannot handle filenames with spaces (fairly common for ripped .flac
files).
* It is hardwired to use /dev/hdc as the name of the CD drive.
* It does not report what the invalid Disc-ID _i
Yes, I can confirm that once Konqueror is started - with "Always try to
have one preloaded instance" enabled - a process (possibly the same one?
(didn't check)) does stay around, even after an clicking quit. This is
very annoying, since when shutting down the system (or possibly even
when logging
I can confirm this latest update also seems to be working fine (no blue
background):
Start-Date: 2019-02-26 18:47:20
Commandline: apt-get dist-upgrade
Requested-By: [redacted]
Upgrade: libldb1:amd64 (2:1.4.0+really1.3.5-2, 2:1.4.0+really1.3.5-2ubuntu0.1),
libgs9:amd64 (9.26~dfsg+0-0ubuntu0.18.10
I also confirmed this upgrade FIXED the blue-background problem:
Start-Date: 2019-02-23 19:52:39
Commandline: apt-get dist-upgrade
Requested-By: [redacted]
Upgrade: libgs9:amd64 (9.26~dfsg+0-0ubuntu0.18.04.5,
9.26~dfsg+0-0ubuntu0.18.04.6), ghostscript-dbg:amd64
(9.26~dfsg+0-0ubuntu0.18.04.5, 9.
this at
> <https://forums.linuxmint.com/viewtopic.php?f=47&t=288613#p159>
> and then sent an e-mail to marc.deslauri...@ubuntu.com (whose name was
> on the update information) who advised me to post this bug here.
>
> To manage notifications about this bug go to:
>
My printer does NOT auto-upgrade and it started having the problem immediately
after the `ghostscript' "upgrade".
There is no doubt about this, colour printing was working fine yesterday until
the upgrade, then it went all blue-background.
I have not (yet?) tried reverting `ghostscript', I am ha
tps://forums.linuxmint.com/viewtopic.php?f=47&t=288613#p159>
> and then sent an e-mail to marc.deslauri...@ubuntu.com (whose name was
> on the update information) who advised me to post this bug here.
>
> To manage notifications about this bug go to:
> https://bugs.launchpa
Also "(HP) Deskjet 1510 All in one", "HP Officejet 7310";
e.g., see
https://h30434.www3.hp.com/t5/Inkjet-Printing/Printer-has-suddenly-started-printing-solid-blue-background/td-p/7027024
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Some more info (in case it helps):
Ubuntu 18.04.2 LTS x86_64 [fully up-to-date Kubuntu]
HP OfficeJet Pro 6970 [has worked flawlessly]
A bit of searching on the 'Net has found complaints this is happening
for other printers not mentioned in _this_ bug report, including (but
not necessarily lim
I can also confirm setting "High Quality Grayscale" (in CUPS) works-around the
problem.
There's no colour (obviously), but also no wasting Blue ink on a useless
background.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
I also can confirm this started happening after the following upgrade:
Start-Date: 2019-02-21 20:42:54
Commandline: apt-get dist-upgrade
Requested-By: [redacted]
Upgrade: libgs9:amd64 (9.26~dfsg+0-0ubuntu0.18.04.4,
9.26~dfsg+0-0ubuntu0.18.04.5), ghostscript-dbg:amd64
(9.26~dfsg+0-0ubuntu0.18.04
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: "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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1581270
Title:
Hybrid Gr
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1581270
Title:
Hybri
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
,
Brian Foster
** Affects: cgoban (Ubuntu)
Importance: Undecided
Status: New
--
client freezes after a few minutes on IGS
https://bugs.launchpad.net/bugs/462478
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
51 matches
Mail list logo
