Public bug reported:
Binary package hint: mongrel-cluster
Three problems:
1. The mongrel_cluster_ctl script defaults to "/etc/mongrel_cluster"
when it should be "/etc/mongrel-cluster"
2. The script looks for .conf files in the above directory. It should be
looking for symlinks in the sites-enab
The problem with mongrel_cluster_ctl is masked when using /etc/init.d
/mongrel-cluster, because the path is hardcoded.
While /etc/init.d/mongrel-cluster looks in /etc/mongrel-cluster/sites-
enabled for clusters to start, because it uses mongrel_cluster_ctl, then
the symlinks must be suffixed by .
I get this issue. To fix, I do the following:
- open the gnome registry editor
- check app/nautilus/preferences/show desktop
Make sure you switch it off again if you also use kde - and kill the
service it invokes - as it causes horrible desktop issues and
performance problems there. This is an
Does that mean waiting until 9.10?
If so, that's a deal breaker for me. This is a serious security flaw and
there's no way I can roll this out to a business. If you have to take
away the ability to suspend from kickoff, then so be it. That's what
happens when you have security issues, the solution
Public bug reported:
Whenever you insert a thum-drive or usb drive, nautilus launches in
kubuntu jaunty.
This can be switched off unchecking the nautilus option: Browse media
when inserted.
However, surely this shouldn't happen when using Kubuntu. In fact, after
a few week's use, it only started
I can also confirm this bug. I do have pulseaudio installed. This is a
deal breaker for me.
--
[Jaunty] Sound in GTK apps can't be disabled under KDE
https://bugs.launchpad.net/bugs/343677
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
What else is required for this to not be marked incomplete? Pray tell.
--
nVidia GLX-driver breaks console
https://bugs.launchpad.net/bugs/210458
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@li
Anything more I can do to get attention here?
--
GeForce 6600 not supported
https://bugs.launchpad.net/bugs/313306
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.ubuntu.com
https://lists.ub
Public bug reported:
Tested on Jaunty: Version: 4:4.2.2-0ubuntu4
Examples of file names followed by what Dolphin offers for rename/F2:
Adapting to Web Standards - CSS and Ajax for Big Sites (2008).pdf
and Ajax for Big Sites (2008).pdf
Advanced Ajax - Architecture and Best Practices (2008).pdf
B
I think I can see what causes this.
When renaming a file, and When 'Rename inline' is checked, the rename
area wraps. I'd argue that that is extremely counter-intuitive and very
ugly, frankly.
--
Rename does not always work as expected
https://bugs.launchpad.net/bugs/374516
You received this bug
not seen bu 321190, but don't understand it nor its relevance to this.
--
3rd + 4th layer for 'n' can't get set (on top of running qwertz-de layout)
https://bugs.launchpad.net/bugs/321189
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
Just to add that
# xmodmap -pke
shows these assignments as having been made successfully.
--
3rd + 4th layer for 'n' can't get set (on top of running qwertz-de layout)
https://bugs.launchpad.net/bugs/321189
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
I can confirm this problem for both n and e keys:
keycode 38 = a A a A aacute Aacute
keycode 26 = e E e E eacute Eacute
keycode 31 = i I i I iacute Iacute
keycode 32 = o O o O oacute Oacute
keycode 30 = u U u U uacute Uacute
keycode 57 = n N n N ntilde Ntilde
--
3rd + 4th layer for 'n' can
Okay, but how do you "convert" ~/.Xmodmap to evdev?
--
old .Xmodmap files can cause hotkeys to stop working in Intrepid
https://bugs.launchpad.net/bugs/269619
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
u
I think that this problem this is related to:
http://www.nvnews.net/vbulletin/showthread.php?t=81256&highlight=blank+tty&page=10
The suggested fix is:
cat /etc/modprobe.d/options | grep nvidia
options nvidia NVreg_UseVBios=0
But it can't be tried in Jaunty because /etc/modprobe.d/options ha
It's working okay on my clean install of Jaunty Kubuntu. I do have
Ubuntu installed too, though.
--
[Hardy] Ksnapshot not binding to PrtScrn.
https://bugs.launchpad.net/bugs/132001
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubun
I too agree that there needs to be a way to restart a hung X from within
X. I second ctrl+alt+bksp.
--
Ubuntu needs a command to restart X
https://bugs.launchpad.net/bugs/344818
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-
This was marked critical in January and it's still broken. Makes things
unusable for a traveller with laptop that doesn't speak geek.
--
Unable to make any changes in Date / Time kcontrol
https://bugs.launchpad.net/bugs/312569
You received this bug notification because you are a member of Ubuntu
Public bug reported:
Sending crash report
ProblemType: KernelOops
Annotation: This occured during a previous suspend and prevented it from
resuming properly.
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
InterpreterPath:
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/25330227/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/25330228/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/25330229/Dependencies.txt
** A
Hi, I'm using a GeForce 6600 on Jaunty with the 180.44 drivers. I use
KDE and Gnome. Here are the issues:
- Complex GL screensavers do not work, lightweight ones draw very, very slowly.
- Ctrl+Alt+F1, say, results in a strange fade effect on screen and then settles
to black. The console never app
** Attachment added: "Xorg.0.log"
http://launchpadlibrarian.net/25339803/Xorg.0.log
--
GeForce 6600 not supported
https://bugs.launchpad.net/bugs/313306
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubu
** Attachment added: "xorg.conf"
http://launchpadlibrarian.net/25339836/xorg.conf
--
GeForce 6600 not supported
https://bugs.launchpad.net/bugs/313306
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubunt
** Attachment added: "lspci"
http://launchpadlibrarian.net/25339881/lspci
--
GeForce 6600 not supported
https://bugs.launchpad.net/bugs/313306
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@l
Also, see:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-
modules-2.6.24/+bug/210458
--
GeForce 6600 not supported
https://bugs.launchpad.net/bugs/313306
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mai
Same problem exists with 180.44 on Jaunty. My bedug info is in:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-180/+bug/313306
--
nVidia GLX-driver breaks console
https://bugs.launchpad.net/bugs/210458
You received this bug notification because you are a member of Ubuntu
Bu
If I understood the notes I would have tested. The notes make no sense
to me at all. Judging by the lack of feedback, I guess that I'm not
alone!
--
GeForce 6600 not supported
https://bugs.launchpad.net/bugs/313306
You received this bug notification because you are a member of Ubuntu
Bugs, which
Public bug reported:
Binary package hint: kchmviewer
After installing kchmviewer, I noticed when right-clicking the "Open
with..." option in any KDE file manager, that there is an "KchmViewer"
entry.
On closer inpection in KDE System Settings/File Associations, I notice
that there is a KchmViewe
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/30053570/Dependencies.txt
** Attachment added: "DpkgTerminalLog.txt"
http://launchpadlibrarian.net/30053571/DpkgTerminalLog.txt
--
package envyng-core 2.0.1ubuntu1 failed to install/upgrade: subprocess
post-installatio
Public bug reported:
Binary package hint: envyng-core
Description:Ubuntu 9.04
Release:9.04
Install failed as per attached docs. Install script follows:
Setting up envyng-core (2.0.1ubuntu1) ...
Traceback (most recent call last
Sorry, my mistake, alternatives messed with my python config and wiped a
symlink causing this problem.
All is now good. Please close.
--
package envyng-core 2.0.1ubuntu1 failed to install/upgrade: subprocess
post-installation script returned error exit status 1
https://bugs.launchpad.net/bugs/4
Public bug reported:
Binary package hint: pida
Description:Ubuntu 9.04
Release:9.04
Package: pida
Version: 0.5.1-5ubuntu1
The PdfTex Preview plug-in install, but fails to start due to a missing
dependency on line 40 in pdftex_preview.py:
# other imports
import pdfv
Thanks for the feedback. I upgraded to KDE 4.2.4 and things looked good
until:
Application: KMail (kmail), signal SIGABRT
[Current thread is 0 (LWP 29034)]
Thread 2 (Thread 0xac451b90 (LWP 29283)):
#0 0xb8035430 in __kernel_vsyscall ()
#1 0xb5c657b1 in select () from /lib/tls/i686/cmov/libc.so.
Here with kdepim-dbg installed.
As before, this was when doing right-click, Empty wastebin on Local
folders/wastebin.
Application: KMail (kmail), signal SIGABRT
[Current thread is 0 (LWP 4645)]
Thread 2 (Thread 0xabb11b90 (LWP 4661)):
#0 0xb7fad430 in __kernel_vsyscall ()
#1 0xb5bdd7b1 in sele
Public bug reported:
I experience this bug about one in five times when emptying the
wastebin. The problem occurs when right-clicking either Local
Folders/Wastebin or /Trash, and clicking "Empty Wastebin".
Notes:
- All my email accounts are IMAP
- I am using the KDE wallet
$ lsb_release -rd
Desc
Public bug reported:
Binary package hint: xpn
The sorting column -- set in Prefs/Groups/Visualization -- is not
retained between sessions.
I set this option to Subject (ascending) and it resets to From.
Note that I also have the Threads Pane option set to From.
** Affects: xpn (Ubuntu)
Im
Public bug reported:
Binary package hint: xpn
I would like the option to download headers at start-up. Currently,
headers are only downloaded according to the "Minutes between downloads"
setting.
** Affects: xpn (Ubuntu)
Importance: Undecided
Status: New
--
xpn doesn't download h
Public bug reported:
Binary package hint: xpn
When reading an article, if the periodic header download kicks in, then
xpn clears the article in the article pane.
This is probably due to the fact that I do not display read articles,
and the header download causes a refresh. It shouldn't do this f
Public bug reported:
Binary package hint: vim-gtk
The current version of vim used in all vim and gvim packages is v6.4.6.
vim v7 and above is a significant upgrade that is essential for folk
working on multiple platforms - namely Windows and Linux.
A vim v7 package already exists for Edgy
** Af
Public bug reported:
Binary package hint: nginx
sudo aptitude remove nginx
results in:
The following packages will be REMOVED:
nginx
0 packages upgraded, 0 newly installed, 1 to remove and 1 not upgraded.
Need to get 0B of archives. After unpacking 528kB will be freed.
Writing extended stat
I fixed this by adding an entry to KDE Control Centre/Regional/Input
Actions.
Action name: Print screen
Action type: Keyboard shortcut -> Command/URL
Keyboard shortcut: Print
Command: ksnapshot
--
Ksnapshot not binding to PrtScrn.
https://bugs.launchpad.net/bugs/132001
You received this
I can confirm that it works okay. I use it constantly, including use of
the latex suite.
--
backport vim 7 to dapper
https://launchpad.net/bugs/52539
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Unfortunately, this problem was with a laptop that I returned last week,
so I'm unable to diagnose further. The problem was still there last
week, though.
--
automatic resume after suspend
https://bugs.launchpad.net/bugs/505190
You received this bug notification because you are a member of Ubuntu
All a bit of a mess. I've ended up, unconsciously, removing all the new
indicator/status applets and panels, and using replacements. One by one
they fell. I'm even back to Quod Libet to replace Rhythmbox whose
accessibility has been strangled by this change.
I regard this experiment as a failure.
Please close. I no longer use this application.
--
In KDE, adds a file association for every file type
https://bugs.launchpad.net/bugs/410484
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.
Feel free to close.
--
[Acer TravelMate 4650] suspend/resume failure [non-free: nvidia]
https://bugs.launchpad.net/bugs/360384
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.ubuntu.com
http
I use the battery applet mentioned here
http://ubuntuforums.org/showthread.php?p=9271002
gnome-volume-control-applet is fine. Just remove the indicator applet in
its entirely. Job done.
Bluetooth is an app icon in the regular notification area, not one of
the "indicator" applet entries.
Btw, if
I think this was an automated submission. I certainly haven't seen for a
long while.
--
[Acer TravelMate 4650] suspend/resume failure [non-free: nvidia]
https://bugs.launchpad.net/bugs/360384
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Public bug reported:
(`ubuntu-bug -p linux` performed and sent.)
$ lsb_release -rd
Description:Ubuntu 9.10
Release:9.10
After upgrading from jaunty to karmic suspend is behaving in the
following manner.
After booting, the first suspend works as normal. Subsequent attempts
result in
** Attachment added: "AlsaDevices.txt"
http://launchpadlibrarian.net/37648945/AlsaDevices.txt
** Attachment added: "AplayDevices.txt"
http://launchpadlibrarian.net/37648946/AplayDevices.txt
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/37648947/BootDmesg.txt
** Att
I confirm the above patch works. Thanks, Thomas.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1210936
Title:
Warnings in munin-graph.log during each graph rendering run
To manage notifications abo
A regular aptitude upgrade installed the updated nvida-173-modaliases
and has made my maverick machine useless. I get a black screen after
starting X. No gdm/login appears. /var/log/Xorg.0.log indicates no
problems at all; it reaches "enabled".
Maverick/GeForce GT 330M/Sony Vaio f-series
--
ABI
A regular aptitude upgrade installed the updated nvida-173-modaliases
and has made my maverick machine useless. I get a black screen after
starting X. No gdm/login appears. /var/log/Xorg.0.log indicates no
problems at all; it reaches "enabled".
Maverick/GeForce GT 330M/Sony Vaio f-series
--
Nvid
Hmm Well, X is 1.9 and nouveau is reporting that it is built for
1.8.99.905 (5 Aug, as it happens).
Then it loops through a bunch of drmOpenMinor calls, all of which return
-1 (geek for fail, I suspect).
Then finally reports
[drm] failed to open device
No devices detected.
Fatal server erro
Public bug reported:
Binary package hint: gnome-settings-daemon
Description:Ubuntu maverick (development branch)
Release:10.10
Regular boot via gdm. At end of desktop start-up graphics change to
1970s-style X
.xsession-errors ends:
Error grabbing key 173, 0x9812038
Error grabbing k
Public bug reported:
I run: sudo update-manager -d
Update manager says: You must check for updates manually. Options: Check and
Close.
I click: Check.
It does: Updating cache.
Then says: There are no updates to install.
It says: New Ubuntu release '14.04.3 LTS' is available.
I click: upgrade.
Mod
I resolved this by removing postgresql-9.3-postgis-2.1.
It would be great if the upgrade tools could give hints about possible
problems, or display `cat apt.log | grep -i broken` in /var/log/dist-
upgrade. Any pointers would be better than nothing, which is the status
quo.
** Changed in: update-m
I've just hit this problem. Are there any suggestions for a fix? Or
trying one?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1356033
Title:
package initramfs-tools 0.99ubuntu13.5 failed to install/
As with #4, I was/am trying to upgrade from 12.04 LTS to 14.04 LTS.
It appears that the 14.04 upgrade is trying to do:
update-initramfs: Generating /boot/initrd.img-3.2.0-89-generic-pae
which is the my kernel from 12.04. Whether or not it should be doing
this, I don't know.
The files it can't
This problem still occurs in Firefox v25.
Mozilla reported some changes to Google's API requirements that might be
the issue:
https://bugzilla.mozilla.org/show_bug.cgi?id=919153
To test:
https://developers.google.com/maps/documentation/javascript/examples
/map-geolocation
and
http://mozqa.com
I installed firefox v23.01 to /opt. It picked up my settings from
~/.mozilla and everything, including geolocation worked fine.
I then let it upgrade to v25. No problems, everything, including
geolocation, worked fine.
So, I swapped back to Ubuntu Firefox v25. Sadly, geolocation stopped
working.
Looking here:
https://bugzilla.mozilla.org/show_bug.cgi?id=919153
It seems that each distro needs a new key from Google for location
tracking, er, discovery. Presumably this is at the root of the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This is really astonishing, I just upgraded Ubuntu's Firefox to version
26.0 and geolocation is still not working. The identical version from
Mozilla works flawlessly.
I am very disappointed that there has been no acknowledgement of this
bug by Ubuntu.
--
You received this bug notification becau
Thanks, Chris.
It's sad for me, but this event was the straw the broke the camel's
back, and I have abandoned Linux on the desktop after ~15 years (Debian
hamm). If a so-called LTS release could not support an essential
function in one of the handful of its most important applications, then
I can
I just upgraded Ubuntu's firefox from the repos. It is now on version
25.0.1. Geoloacation is still not working in the Ubuntu version.
The identical version from Mozilla works flawlessly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Robert Dyer wrote: Just grab the source code and compile it yourself -
it isn't that hard!
Let's see:
1. googled for ubuntu gnome-do source
2. found it here: https://launchpad.net/ubuntu/maverick/+source/gnome-do
3. extracted the archive
4. cd'd into it
5. ran ./configure, which moaned:
config
Fair enough, but do you know why the upstream fix has not rippled
through? The fix has been in place for six months now. Is there anything
we can do expedite this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
This problem is still very much alive and well.
I now use a script alias to ease the pain:
alias snd='killall pulseaudio; killall gnome-volume-control-applet;
pulseaudio -D; nohup gnome-volume-control-applet > /tmp/gnome-
volume.log 2> /dev/null &'
pulseaudio goes to 100% on one cpu at every re
Thanks for the suggestion, but I really shouldn't have to be using
backports on a system that has always worked. That doesn't solve the
problem.
I have been running 10.10 since it went beta and have solved plenty of
issues since then, as is expected, but this is bonkers.
A mainline aptitude updat
Maverick/GeForce GT 330M/Sony Vaio f-series
Update to 260.19.06-0ubuntu1 has resulted in my system displaying a
black screen where gdm/login should occur, Logs show no issues. Machine
is currently unusable.
How do I revert this?
--
nvidia 256.53 xorg-server 1.9.0 performance regression with ant
Someone over on the nvidia forums kindly suggested installing 256.53
from the nvidia repos. That has me up and running. I have no idea how
this affects further Ubuntu updates, however. The "Additional drivers"
tool still says "(version current) [Recommended]", which seems
meaningless now. Why is th
The patronising straw man lecture is really not welcomed.
Can we please stick to the facts.
--
Nvidia 173 driver does not work with xserver 1.9
https://bugs.launchpad.net/bugs/626918
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
u
I workaround my issue by installing the 256.53 drivers directly from
nvidia. So anyone else facing an unusable machine that was fine before
the 260 downdate, give this a try.
--
nvidia 256.53 xorg-server 1.9.0 performance regression with antialiased text
https://bugs.launchpad.net/bugs/629910
You
@quiricada How long did you leave the blank screen before the login
screen appeared. Two minutes, five, ten, twenty?
--
nvidia 256.53 xorg-server 1.9.0 performance regression with antialiased text
https://bugs.launchpad.net/bugs/629910
You received this bug notification because you are a member o
The only person who mentioned "production machines" is you. Now, please,
please, go away, Mr Straw, we are trying to fix things around here.
--
Nvidia 173 driver does not work with xserver 1.9
https://bugs.launchpad.net/bugs/626918
You received this bug notification because you are a member of Ub
To be honest, looking at the nvidia package installed, I'm not clear
what I should or should not have. I've not had problems here before, so
I've never looked. For background, this machine was upgraded from Lucid.
I have the following installed:
nvidia-173-modaliases
nvidia-96-modaliases
nvidia-co
I left the machine for 1/2 hour, but it does not progress from the blank
screen. I simply cannot use 260.19.06-0ubuntu1. This is a huge
regression for me. I appreciate it is not this bug, but I cannot find
the appropriate bug to file against . Can anyone point me to the
appropriate bug for: Maveric
Kernel 260.19.12 didn't improve matters here :( Back to 256.53 for me.
--
NVRM: os_raise_smp_barrier(), invalid context!
https://bugs.launchpad.net/bugs/656279
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Seems that the Nvidia forum is down too. I'm getting 404s on
http://www.nvnews.net/vbulletin/, so can't report there atm.
--
NVRM: os_raise_smp_barrier(), invalid context!
https://bugs.launchpad.net/bugs/656279
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
As far as I remember, yes. I used ctrl+c while in gdb to get to the
prompt. But I'm pretty sure that it was still @ 100% CPU.
--
(On usb card removed) pulseaudio process goes to 100% CPU and cannot be
restarted
https://bugs.launchpad.net/bugs/636901
You received this bug notification because you
This is a colossal mess. The bottom line seems to be that one has to
recheck all service configs after an update, whether sysv or upstart.
One also has to "know" which services have been "upstarted" in order to
derive their expected behaviour.
Confidence in services' configs at reboot has just bee
Public bug reported:
When I plug in a Novation X-Station (a usb soundcard) and then try to
perform any other action, the whole system freezes. I cannot switch to
the terminal and SysRQ keys also don't work.
If I leave htop open in a terminal and then plug in the device, I can
see that modprobe la
** Attachment added: "AlsaDevices.txt"
http://launchpadlibrarian.net/52785684/AlsaDevices.txt
** Attachment added: "AplayDevices.txt"
http://launchpadlibrarian.net/52785685/AplayDevices.txt
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/52785686/BootDmesg.txt
** Att
I just tested the same device on the same machine with Linux Mint, which
is based on Lucid. The device works fine. Here is the dmesg:
[ 1119.152738] usb 2-1.5: new full speed USB device using ehci_hcd and address 6
[ 1119.628177] hub 2-1:1.0: unable to enumerate USB device on port 5
[ 1120.174983]
Just rebooted and the problem has gone.
--
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@lists.ubuntu.c
Confirmed fixed.
--
Bluetooth device absent after 20100906 update to maverick
https://bugs.launchpad.net/bugs/631818
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.ubuntu.com
https://lists.
I guess you _could_ call it a feature. A bit like having a car with an
engine that you can't ever switch off. Not a very useful feature. I have
a rule that says that removing something is not a feature. A "design"
choice, but not a feature.
I am in the same situation regarding a shared switch for
Both mics still not working using the PPA. File attached.
I can still get the ext mic working by using HDAanalyzer to toggle the
switches and set the volume.
These are my notes to myself:
1. node0x23 mute and unmute Val0 because it shows default unmuted but in
fact it is muted
2. increase
You might want to try the fix from here:
http://code.google.com/p/vaio-f11-linux/wiki/EnableMicrophone
#34 here worked for me:
http://code.google.com/p/vaio-f11-linux/issues/detail?id=2&can=1
This requires using the HDA anayzer from here:
http://www.alsa-project.org/main/index.php/HDA_An
Public bug reported:
Binary package hint: pulseaudio
Description:Ubuntu maverick (development branch)
Release:10.10
When I unplug my USB sound card, which works fine, the pulse audio
process goes to 100% CPU (on one processor) and remains in that state.
Attempts at a restart result
Attached is the result of:
echo autospawn = no >> ~/.pulse/client.conf
killall pulseaudio
LANG=C pulseaudio - > ~/pulseverbose.log 2>&1
pacmd set-log-time 1
sudo /etc/init.d/pulseaudio start
** Attachment added: "pulseverbose.log"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bu
$ pulseaudio --start
N: main.c: User-configured server at
{c10255de8cac4c5c96d4ac784c091d51}unix:/home/marc/.pulse/c10255de8cac4c5c96d4ac784c091d51-runtime/native,
not autospawning.
--
pulseaudio process goes to 100% CPU and cannot be restarted
https://bugs.launchpad.net/bugs/636901
You receive
To get restarted, I have to:
pulseaudio -D
killall gnome-volume
/usr/bin/gnome-volume-control-applet &
Seems to me that the last is a bug too. The applet disappears when
pulseaudio is killed, but remains in memory and doesn't reappear when
another pulseaudio instance is started.
--
pulseaudio
I forgot, I also deleted ~./pulse
--
pulseaudio process goes to 100% CPU and cannot be restarted
https://bugs.launchpad.net/bugs/636901
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.ubuntu
I mean ~/.pulse
--
pulseaudio process goes to 100% CPU and cannot be restarted
https://bugs.launchpad.net/bugs/636901
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.ubuntu.com
https://lists
Guess it's back to the drawing board then :(
--
[Realtek ID 275] No audio Sony VAIO VPCs111FM Lucid A2
https://bugs.launchpad.net/bugs/525149
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.
I rebooted with the USB sound card attached. Ubuntu sees this just fine.
I followed the instructions and attach the output. PA goes to 100%
immediately, within 1 second of removing the USB connection.
** Attachment added: "pulseverbose.log"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio
I also tried rebooting with the card disconnected. Then connected it
after login, then removed it. The same occurred as above.
I observed that memory use does not appear to be increasing while it
loops; I guess it's a loop.
--
pulseaudio process goes to 100% CPU and cannot be restarted
https://b
Further discovery. Once I have killed PA, as above, and relaunched it, I
cannot make it "rediscover" the USB sound card, even if I completely
remove ~./pulse
For the sound card to function again, I have to reboot.
--
pulseaudio process goes to 100% CPU and cannot be restarted
https://bugs.launch
Seems we've gone to 2.6.35-21
--
[Realtek ID 275] No audio Sony VAIO VPCs111FM Lucid A2
https://bugs.launchpad.net/bugs/525149
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.ubuntu.com
http
1 - 100 of 129 matches
Mail list logo
