Installing linux-alsa-driver-modules-2.6.35-19-generic killed all audio
outputs. See attached.
** Attachment added: "missing audio outputs.png"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/525149/+attachment/1549961/+files/missing%20audio%20outputs.png
--
[Realtek ID 275] No au
** Attachment added: "expected audio outputs.png"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/525149/+attachment/1549962/+files/expected%20audio%20outputs.png
--
[Realtek ID 275] No audio Sony VAIO VPCs111FM Lucid A2
https://bugs.launchpad.net/bugs/525149
You received this bug
There ya go.
** Attachment added: "alsa-info.txt.1f2vLBUiFV"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/525149/+attachment/1550660/+files/alsa-info.txt.1f2vLBUiFV
--
[Realtek ID 275] No audio Sony VAIO VPCs111FM Lucid A2
https://bugs.launchpad.net/bugs/525149
You received thi
Can you give me a pointer as to how to do that. I'm technical, so terse
instructions should do.
--
Pressing at GDM screen crashes X
https://bugs.launchpad.net/bugs/626723
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs m
Public bug reported:
Binary package hint: bluez
Description:Ubuntu maverick (development branch)
Release:10.10
Bluetooth was working fine in maverick until today's update, 20100906.
The panel widget, previously fine, is now absent.
bluetoothd is running
When I try to run /usr/bin/b
$ rfkill list
0: sony-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no
1: sony-bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
2: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
3: phy0: Wireless LAN
Soft blocked: no
Hard
$ hcitool scan
Scanning ...
$ hcitool dev
Devices:
hci02C:81:58:B9:F4:43
$ sudo hciconfig hci0 reset
$ hcitool scan
Scanning ...
$
--
Bluetooth device absent after 20100906 update to maverick
https://bugs.launchpad.net/bugs/631818
You received this bug notification because you are a
Possibly related to change here:
http://www.ubuntuupdates.org/packages/show/214599
which added build-depends on libgconf2-dev. Possible further dep issues,
since this is a dev package.
--
Bluetooth device absent after 20100906 update to maverick
https://bugs.launchpad.net/bugs/631818
You rece
I confirm crash reproduced after reboot. No change.
--
bluetooth-properties crashed with signal 5 in g_object_newv()
https://bugs.launchpad.net/bugs/631548
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubun
I did, of course, upgrade before rebooting.
Package: gnome-bluetooth
State: installed
Automatically installed: no
Version: 2.31.6-0ubuntu3
Priority: optional
Section: gnome
Maintainer: Ubuntu Developers
Uncompressed Size: 1,135k
--
bluetooth-properties crashed with signal 5 in
That said, my bug:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/631818
was marked as a duplicate of this bug, and it might well no be.
--
bluetooth-properties crashed with signal 5 in g_object_newv()
https://bugs.launchpad.net/bugs/631548
You received this bug notification because you
Hmm I prefer to stay with aptitude, so this should work:
$ sudo aptitude install =
and perhaps
$ sudo aptitude hold
So, now I need to know the package name and source, since I presume the
required package comes out of the lucid repos.
Currently,
$ aptitude versions gdm
i 2.30.5-0ubuntu2
After leaving the machine switched off over night, I can now, at least,
load bluetooth-properties.
However, the panel icon is still missing. I've tried restarting the
gnome panel a few times, but that doesn't improve things. Each time I
restart the panel I get the following msg in ~/.xsession-erro
I installed blueman and everything just works. Including the icon and
the ability to deactive bluetooth.
--
bluetooth-properties crashed with signal 5 in g_object_newv()
https://bugs.launchpad.net/bugs/631548
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
Tried on Ubuntu 10.10.
After loading there are 3 bluetooth process: blueman-applet, bluetoothd,
blueman-mechani
About 15 second after bluetooth is deactivated via the widget, first
blueman-mechani fails, then almost immediately bluetoothd.
Because of this I get:
$rfkill list
1: sony-bluetooth:
Dude, using a separate tool to determine, unequivocally, that all the
hardware components work and are inter-operate, removes any doubt that
the problem is machine-specific. In debugging terms, that's pretty darn
useful information.
As you might say, tu petes plus haut que ton cul.
--
bluetooth-
Yup, apache installed here too.
Nice find, Bilal.
--
init script resets isig flag in an incorrect manner
https://bugs.launchpad.net/bugs/626723
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
Oh, and btw, it's voilà. Viola is a big violin, and the female
protagonist in the Patrick Ness trilogy Chaos Walking ;)
Right, off to confirm your test findings.
--
init script resets isig flag in an incorrect manner
https://bugs.launchpad.net/bugs/626723
You received this bug notification becau
Not meaning to confuse things, but I upgraded to Maverick and there have
been some changes for me.
Speaker previously required linux-alsa-driver-modules-2.6.32-??-generic,
but they now work without this package; the kernel is now 2.6.35-19.
The inbuilt and plug-in mics still don't work, although
Fix noted here:
http://code.google.com/p/vaio-f11-linux/wiki/EnableMicrophone
Fill attached.
** Attachment added: "alsa-info.txt.DvImsQC6Lj"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/525149/+attachment/1540244/+files/alsa-info.txt.DvImsQC6Lj
--
[Realtek ID 275] No audio
Due to the lack of response, in desperation -- I was about to move to
Debian -- I upgraded to Maverick. The problem is no longer there. For me
Maverick is an improvement on Lucid in almost every way.
--
System freeze when plugging in USB audio device
https://bugs.launchpad.net/bugs/612077
You rec
Public bug reported:
Binary package hint: gdm
Boot machine.
gdm login screen appears.
Scenario one:
Type nothing
Hit send -> screen goes black, which looks like an X restart.
gdm login screen reappears.
Login as expected.
Scenario two:
Type user name
Hit send -> screen goes black, which looks l
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/630453/+attachment/1544189/+files/Dependencies.txt
--
Hitting send at login seems to restart X
https://bugs.launchpad.net/bugs/630453
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Perhaps I should add that I have checked
apps/gdm/simple-greeter/disable_user_list
--
Hitting send at login seems to restart X
https://bugs.launchpad.net/bugs/630453
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mail
Public bug reported:
Binary package hint: logrotate
Description:Ubuntu maverick (development branch)
Release:10.10
Version: 3.7.8-6ubuntu1
After upgrading from Lucid to Maverick, I received this email.
Subject:
Anacron job 'cron.daily' on blah
Body:
/etc/cron.daily/logrotate:
Appears to have been a one-time event. So please close.
--
cron.daily fails after upgrade to Maverick
https://bugs.launchpad.net/bugs/630922
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.u
There are so many regressions here it is getting very hard to test this.
The sound card is now only being recognised by the system randomly -- it
was 100% earlier. This would be okay if restarting PA (and gnome-volume-
control-applet, which appears to be far, far too tightly coupled to PA)
fixed th
While debugging #11, I found that if I didn't have the card plugged in
first then it would never be recognised.
The only way that it would randomly be recognised is if I started PA,
plugged in the card, then started gnome-volume-control-applet. When the
card wasn't "found", the following was produ
I notice that there is useful debug information in the attached
WifiSyslog.txt:
Jul 31 15:59:12 localhost kernel: [21311.163931] usb 2-1.5: new full speed USB
device using ehci_hcd and address 5
Jul 31 15:59:13 localhost kernel: [21311.679546] hub 2-1:1.0: unable to
enumerate USB device on port
101 - 129 of 129 matches
Mail list logo
