** Description changed:
Hello,
I am using Ubuntu 19.10 with 5.1 surround speakers.
I tried to configure 5.1 surround, but it still doesn't work.
I also installed Pulse audio.
Here is the info about my soundcard:
# aplay -l
Lista PLAYBACK de dispozitive
placa 0: PCH [HD
Public bug reported:
Hello,
I am using Ubuntu 19.10 with 5.1 surround speakers.
I tried to configure 5.1 surround, but it still doesn't work.
I also installed Pulse audio.
Here is the info about my soundcard:
# aplay -l
Lista PLAYBACK de dispozitive
placa 0: PCH [HDA Intel PCH], dispozi
Hi Jouni,
I will collect all the necessary information and open a new bug on the
right component.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872196
Title:
5.1 audio does not work
To m
** Changed in: grub-installer (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822377
Title:
cannot install GRUB (Ubuntu can boot only from USB)
To manage notif
$ speaker-test -c6 -l1 -twav
speaker-test 1.1.9
Playback device is default
Stream parameters are 48000Hz, S16_LE, 6 channels
WAV file(s)
Rate set to 48000Hz (requested 48000Hz)
Buffer size range from 32 to 349525
Period size range from 10 to 116509
Using max buffer size 349524
Periods = 4
was se
Public bug reported:
Hello,
I am using Ubuntu 19.10 with 5.1 surround speakers.
I tried to configure 5.1 surround, but it still doesn't work.
I also installed Pulse audio.
Here is the info about my soundcard:
# aplay -l
Lista PLAYBACK de dispozitive
placa 0: PCH [HDA Intel PCH], disp
Public bug reported:
Hello,
I cannot boot ubuntu anymore. It seems that GRUB is broken.
I booted from USB and tried to reinstall the OS, but it fails because GRUB
cannot be installed.
All that happend after I tried to boot from USB and chose 'check disks' option.
Please let me know what other de
Public bug reported:
-
ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: nvidia-331 331.89-0ubuntu5
ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
Uname: Linux 3.16.0-24-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.14.7-0ubuntu8
AptOrdering:
nvidia-331-uvm: Purge
This problems seems to affect other BT keyboards as well:
After hitting CapsLock, I have to do a re-connect of the Bluetooth keyboard. In
my case a Fujitsu LX360 keyboard at a CSR bluetooth dongle (USB ID 0a12:0001).
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Version 29 and 30 are affected as well
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1160569
Title:
[regression] GLib-CRITICAL **: g_slice_set_config: assertion
`sys_page_size == 0' failed
To man
Public bug reported:
ldconfig deferred processing now taking place
Si sono verificati degli errori nell'elaborazione:
owncloud
E: Sub-process /usr/bin/dpkg returned an error code (1)
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: owncloud 3.0.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.
** Changed in: cups (Ubuntu)
Status: New => Confirmed
--
cups 1.4.1 in ubuntu 9.10 defaults to duplex on everything. Setting manually to
simplex does not fix.
https://bugs.launchpad.net/bugs/487902
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
Any news here lately? I guess I have this problem, too:
LUKS-encrypted partitions (without LVM here). They get mounted on login via
pam_mount, but these -- already mounted -- devices show up as 'X GB
Filesystem's in the file browser. Extremely irritating...
--
Do not show LUKS devices of intern
I can confirm this. Though the passwords are not entirely forgotten: If
I restart the network-manager, the passwords reappear and a connection
is possible again (until the next time the system disconnects for some
reason and I have to restart the network-manager again...)
** Changed in: network-ma
Oh, I forgot to say that I never had a problem with Jaunty, though.
--
VPN connection fails: "unable to find valid VPN secrets" (auth dialog crash
when secrets exist)
https://bugs.launchpad.net/bugs/284212
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
I experience another variation of this problem:
My setup is: Karmic (i386 netbook remix, fresh install, fully updated),
vpnc-plugin, password-based VPN (user and group passwords saved via
network-manager)
- On first connection attempt after a boot everything is okay
- After a disconnect (manually
Okay, it sounds very much like a variation of #284212 ...
--
vpnc will only connect successfully on first try per session
https://bugs.launchpad.net/bugs/475814
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
@Matt: Yes, VPN via wireless.
I tried a few more things. Still the same problems, _but_ I am not sure
anymore if I am in the right discussion: Now I get this additional
syslog output on a failed connection attempt:
Nov 18 15:54:39 knuff NetworkManager: nm_vpn_connection_connect_cb():
VPN conne
I doubt that the problem is 64bit-specific. I experience the same
problem on a Asus eeePC 901. Karmic netbook remix i386, fresh install.
Hadn't had the problem with Jaunty, though.
--
vpnc will only connect successfully on first try per session
https://bugs.launchpad.net/bugs/475814
You received
This seems to be a problem with "asus-laptop".
If i make :
sudo modprobe -r asus-laptop
then
sudo modprobe asus-laptop
the led goes on, but If I press the Fn+F2 or Wifi switch, the led go
down (but wifi continue to work)
--
network manager doesn't manipulate sw kill switch correctly on asus c90s
Public bug reported:
Binary package hint: module-init-tools
The iwl3945 driver need "options disable_hw_scan=0" to work correctly.
If I don't have this option, the connection is instable with some network and
sometimes I need to force Networkmanager to connect to a network even if it's a
open
I Have the same problem.
When the system boot, the wireless led is on. But when network manager
is launch, this led go down (see with bootmap).
I have this error in "syslog" :
Found radio killswitch /org/freedesktop/Hal/devices/ipw_wlan_switch
killswitch_getpower_reply(): Error getting kill
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/18256043/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/18256044/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/18256045/Dependencies.txt
** A
Public bug reported:
Binary package hint: linux-image-2.6.27-5-generic
System Freeze and Caps Lock Led blink.
ProblemType: KernelOops
Architecture: amd64
DistroRelease: Ubuntu 8.10
NonfreeKernelModules: nvidia
Package: linux-image-2.6.27-5-generic 2.6.27-5.8 [modified:
lib/modules/2.6.27-5-gene
24 matches
Mail list logo