Two years already. Will someone have a look on this bug ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961954
Title:
unstr (package fortune-mod) incorrectly reads data file
To manage notification
I proposed a patch here:
https://bugs.launchpad.net/ubuntu/+source/fortune-mod/+bug/1961954
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/127
Title:
unstr always fails with "data file corrupted"
** Description changed:
- Hot to reproduce :
+ How to reproduce :
$ strfile fort
"fort.dat" created
There were 36 strings
Longest string: 201 bytes
Shortest string: 25 bytes
$ ls -l fort*
-rw-rw-r-- 1 br br 3383 Feb 23 10:31 fort
-rw-rw-r-- 1 br br 172 Feb 23 10:31 fort.dat
Public bug reported:
Hot to reproduce :
$ strfile fort
"fort.dat" created
There were 36 strings
Longest string: 201 bytes
Shortest string: 25 bytes
$ ls -l fort*
-rw-rw-r-- 1 br br 3383 Feb 23 10:31 fort
-rw-rw-r-- 1 br br 172 Feb 23 10:31 fort.dat
$ unstr fort
Input file: fort
unstr: data fil
XUbuntu 20.04: In Screensaver Preferences, lock screen is disabled (in
fact when enabled it was a loop logging, impossible to unlock). However,
still locking (fortunately with no loop), don't know where this lock
comes from.
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
In screensaver preferences, Lock Screen tab:
For the "Lock Screen after the screensaver is active for" field, if we change
the value with the "+/-" buttons, everything is fine.
However, if we change the value manually, and quit, when we come back, the old
value is still the
Public bug reported:
The Exec line in /usr/share/applications/usbview.desktop is:
Exec=su-to-root -X -c /usr/bin/usbview
There is no such su-to-root program.
br.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: usbview 2.0-21-g6fe2f4f-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-2
Public bug reported:
Emacs is version 26.1 on Xubuntu 19.04. However, there is a bug for package
management (https://debbugs.gnu.org/cgi/bugreport.cgi?bug=36873,
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=36810,
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=36725).
I think the bug is fixed i
@psusi. You can add +1 to people having this issue. Don't say "1 million people
have no problem",
if you don't speak about 14.04. Also, the 89 number is from prople who were
able to boot.
My system is fresh 13.04, upgraded to 13.10, and 14.04.
I did not touch grub, and I was lucky enough to hav
A workaround, instead of editing /usr/bin/qemu-launcher is to (in Emulator tab):
- select Acceleration: Enable
- add "--enable-kvm" in Additional arguments
Tested on Saucy.
qemu-launcher 1.7.4-1ubuntu2
qemu 1.5.0+dfsg-3ubuntu5
--
You received this bug notification because you are a member of Ub
Hi Chuck,
Thanks, I don't get anymore the error after adding the group. However,
the user "ntp" does not belong to this group.
Regards,
Bruno.
--
package ntp 1:4.2.4p6+dfsg-1ubuntu5.1 failed to install/upgrade: subprocess
installed post-installation script returned error exit status 1
https:/
** Attachment added: "AptOrdering.txt"
http://launchpadlibrarian.net/36654659/AptOrdering.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/36654661/Dependencies.txt
** Attachment added: "Dmesg.txt"
http://launchpadlibrarian.net/36654662/Dmesg.txt
** Attachment
Public bug reported:
Binary package hint: ntp
I am running Koala, and every time I make a package update (whatever
the package is), I get the following error:
Setting up ntp (1:4.2.4p6+dfsg-1ubuntu5.1) ...
chown: invalid group: `ntp:ntp'
dpkg: error processing ntp (--configure):
subp
13 matches
Mail list logo
