Public bug reported:
Package: afl++ 2.60c-1build2
Ubunut Focal on amd64:
Description:Ubuntu 20.04.1 LTS
Release:20.04
Though afl-fuzz is comipled with external Radamsa mutator enabled, the
Ubuntu package does not include the required libradamsa.so binary.
So, the -R option to
The bug with a long filename was never fixed, it is still here, in version 2.94.
Can be reproduced on a ext4 filesystem, for example with this file:
Public bug reported:
The package tar-scripts contains only shell scripts and no executables at all.
So, it should not be architecture (or platform) specific: it is the same for
all platforms.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: tar-scripts 1.28-2.1ubuntu0.1
According to Debian bugreport the problem is fixed in gcc-7/7.3.0-18,
gcc-8/8.1.0-2
These versions can be installed from a ppa:
https://launchpad.net/~ubuntu-toolchain-r/+archive/ppa
$ sudo add-apt-repository ppa:ubuntu-toolchain-r/ppa
$ sudo upgrade
$ gcc --version
gcc (Ubuntu
** Bug watch added: Debian Bug tracker #896057
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896057
** Also affects: afl (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896057
Importance: Unknown
Status: Unknown
--
You received this bug notification because
Public bug reported:
afl-gcc can not instrument binaries, so afl-fuzz complains "Looks like
the target binary is not instrumented!" and refuses to work.
The issue is described in depth in a blog post:
http://www.danielstender.com/blog/afl-ubuntu1804/
The same issue is reported in Debian
I've got the same problem with Ubuntu 16.04.2 LTS on ThinkPad x260
(default installation with Unity and Lightdm)
Had to switch to an alternative implementation "fingerprint-gui" from
https://launchpad.net/~fingerprint/+archive/ubuntu/fingerprint-gui
The experience is much better.
Specifically,
Anders Kaseorg: What version of Ubuntu are you talking about?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/520546
Title:
Alt-f2 switches to virtual terminal 2
To manage notifications about this
g0ukb: thank you for your suggestions.
I had modified the USB-Audio.conf exactly as you suggested.
ALSA is working with iec958 interface, which is routed to hw:1,1, but
pulseaudio still redirects "S/PDIF output" to hw:1,0 (that is: Analog Stereo).
Probably your friend is running a different
Raymond:
>Why are three playback devices?
1) is analog output
2) is digital S/PDIF stereo output
3) some other digital output
Playing to the third device lights the "digital output" indicator, but I do not
get any sound.
Looks like some sort of S/PDIF output, not supported by my external DAC.
can not attache more than one file to a comment, so here goes pactl list
(see above comment for details)
** Attachment added: "pactl list output"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1498129/+attachment/4585465/+files/pactl_list.txt
--
You received this bug
Raymond: thank you for your time and effort!
Following your advice I was able to configure iec958:CARD=U7 and point it at
the correct hardware device.
The following aplay command goes to the digital output:
$ aplay -D iec958:CARD=U7 test.wav
However, the pulseaudio still redirects both, Analog
I can not grok ALSA configuration files, sorry.
Please, help me put up a proper definition (overrides) for Xonar U7.
lsusb - output attached. Anything else?
Thanks in advance!
** Attachment added: "lsusb - output"
Public bug reported:
duplicate of Bug #1498129
I was not able to make ubuntu-bug to upload the information to the
original bug, sorry. It would not allow me to select alsa-driver
package, because "it is not installed".
I applied the patch suggested by Raymond:
** Description changed:
- Applied the patch
+ duplicate of Bug #1498129
+
+ I was not able to make ubuntu-bug to upload the information to the
+ original bug, sorry. It would not allow me to select alsa-driver
+ package, because "it is not installed".
+
+ I applied the patch suggested by
I've applied the patch, and got rid of errors in dmesg, and alsamixer
does not crash even without ignore_ctl_error=1 option.
Still, no luck with Pulseaudio and S/PDIF.
See Bug #1498676 for the full set of files collected by ubuntu-bug.
--
You received this bug notification because you are a
As far as I can tell, ALSA is working just fine. The problem is only
with Pulseaudio.
After restarting Pulseaudio with Xonar U7 attached I've got the "Xoanar
U7 Digital (S/PDIF)" choice in the Audio configuration, but this choice
actually selects Analog Output (no signal on digital S/PDIF output,
Thank you, Raymond. I will try this patch and see whether the error
message "cannot get ctl value" goes away.
However, as much as I can tell, my problem is not related to this error
message. ALsamixer works just fine (with "ignore_ctl_error=1", see
above), but pulseaudio does not recognize the
Public bug reported:
The external USB audio card Asus Xonar U7 is capable of both analog and digital
output.
ALSA name for the digital (S/PDIF) output is hw:1,1, and it is listed in aplay
-l output, and aplay can output to it:
aplay -D plughw:1,1 sample.wav. So, direct alsa sound works fine.
I've filed this bug against udisks in bugzilla at freedesktop.org.
The resolution is distressing: the bug will not be fixed upstream.
Resolution --- WONTFIX
Comment # 1 on bug 55742 from David Zeuthen
udisks 1.x is in maintenance mode and only security critical bugs will get any
Seems to be related to bug #466575: secure remove of external USB-HDD
produces error
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/908104
Title:
Error detaching: helper exited with exit code 1
To
The same problem on Ubuntu Precise:
sudo udisks --detach /dev/sdc
Detach failed: Error detaching: helper exited with exit code 1: Detaching
device /dev/sdc
USB device: /sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.7)
SYNCHRONIZE CACHE: FAILED: No such file or directory
(Continuing despite
Public bug reported:
Binary package hint: uck
The packages comes with .svn directories in /usr/share/doc/uck and /usr/lib/uck.
This is probably because the package was built from a working SVN directory,
while it is better done from an exported copy (see doc on svn export).
Here is the list of
OK. I think I figured this one out.
If one installs console-cyrillic package and selects Unicode (utf-8) input and
enables it at boot time, then the script cyr executes 'kbd_mode -u' at
startup, whith /dev/console as the standard input. Running 'kdb_mode -u
/dev/console' at any time triggers
I've uploaded the patch that fixes the usage of kbd_mode -u in console-
cyrillic, see bug 520546
But the fact that kbd_mode breaks keyboard in X session, looks like a
bug in kbd to me:
Run
kbd_mode -u -C /dev/console
and from now on pressing ALT+F2 will bring you to the text console
(VT-4).
I've uploaded the patch that fixes the usage of kbd_mode -u in
console-cyrillic, see bug 520546
Hopefully the patch fixes the bug.
However, there seems not much sense in installing console-cyrillic in
the first place. Most of its functionality is available from console-
setup package, which is
The bug is still here, in 10.10. Very annoying!
Submitted the same bug as Bug #730307
Disabling console-cyrillic at boot time solves the problem, but leaves console
without Russian characters.
I manually edited /etc/console-cyrillic, changing YES to NO in the following
line:
# Bootsetup: NO
Related bug: bug 463762
affects:ubuntu → console-cyrillic (Ubuntu)
The problem is apparently with console-cyrillic package. If console cyrillic is
not started at boot time, the bug does not appear.
However, the Cyrillic support is not enabled on the text console in this case!
Very
Related bug: bug 730307
Related bug: bug 520546
This same bug is reported a couple more times. Seems that console-cyrillic is
triggering the problem.
Uninstalling the package or disabling Bootsetup in /etc/console-cyrillic fixes
the problem, but leaves text console without Cyrillic support. The
** Package changed: xserver-xorg-video-intel (Ubuntu) = console-
cyrillic (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/730307
Title:
ALT-F[1-8] switches to text console in Maverik
--
A small investigation into console-cyrillic revealed that it is no more
than a bunch of key mapping definitions and a perl script executing
binaries from other packages, namely console-tools or kbd, On my
computer console-tools are not installed, so executables from kbd are
run.
The culprit is
Console-cyrillic calls kbd_mode -u. This command alone produces the
bug.
** Package changed: console-cyrillic (Ubuntu) = kbd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/730307
Title:
Console-cyrillic just calls kbd_mode -u. This command alone produces
the bug.
The bug is easy to reproduce: do not install console-cyrillic, but simply add
the kbd_mode -u command to /etc/rc.local.
On the GDM login screen press Alt+F2, and you will switch to text console!
So, the but is related
To reproduce the bug simply run
kbd_mode -u /dev/console
you can run it even from a Gnome Terminal and see the effect (the bug)
instantly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/730307
Even easier way to reproduce the bug.
Run the following command from X terminal emulator (Gnome terminal, xterm):
kbd_mode -u
and see the effect instantly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The same bug affected me after upgrade to 10.04 LTS on a Toshiba with
Nvidia video card, and also on a fresh install of 10.10 on ThinkPad
X200T with Intel Mobile 4 Series Chipset Integrated Graphics Controller.
Looks like a long standing and persistent problem in Ubuntu.
--
You received this bug
Public bug reported:
Binary package hint: xorg
Related bug: bug 463762 (probably exactly the same bug)
not only ALT-CTRL-F[1-8] switches to the text console from X-Server, but
also ALT-F[1-8] does this switching. I don't know where this comes from,
but it breaks lots of stuff, i.e. ALT-F4 to
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/730307
Title:
ALT-F[1-8] switches to text console in Maverik
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
38 matches
Mail list logo
