A second use-case for this: I'm running nightlies of Firefox and want to
report a difficult-to-reproduce bug that has been occurring with enough
frequency to warrant a report on LP. However, because nightly moves
fast, the PPA package has likely changed since I was last able to
reproduce the bug.
Still using the old bios.
I just confirmed that I see the same error after a cold boot, too.
Bluetooth icon is there, Bluetooth Settings say bluetooth is ON, but the
phone still won't connect. Same error, Can't find device agent
appears in syslog.
mars@vulpes:~⟫ rfkill list
0:
I've tried upstream kernel v3.14-rc7, as requested in comment 3. No
change. I'm still having issues trying to re-enable bluetooth and
reconnect to devices.
** Tags added: kernel-bug-exists-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug
Public bug reported:
Providing additional information in response to bug 1244764, [ASUS
U31SD] ubuntu 13.10 bluetooth not working correctly.
Attempting to re-estabilish a bluetooth connection between my phone
(Nexus S) and my Thinkpad X230 laptop. The devices have been
successfully paired in
I have tried the workaround from bug 1244764 comment 6, but it had no
effect. My own workaround from bug 1244764 comment 14 doesn't
consistently work, either.
** Description changed:
- Providing additional information in response to bug 1244764, [ASUS
- U31SD] ubuntu 13.10 bluetooth not working
I'm running different hardware, a Thinkpad X230, so as @penalvch
requested, I've filed bug 1295206 to track the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1244764
Title:
[ASUS U31SD]
Public bug reported:
Vagrant uses NFS to bind directories on the host system to directories
in the guest. However, the vagrant package doesn't suggest or recommend
the nfs-common package.
Steps to reproduce:
1. Install a vagrant box and vagrant config file from a third party -
preferrably the
** Description changed:
Vagrant uses NFS to bind directories on the host system to directories
in the guest. However, the vagrant package doesn't suggest or recommend
- the nfs-common package.
+ the nfs-kernel-server package.
Steps to reproduce:
1. Install a vagrant box and vagrant
In addition to comment #6, I also had to run the command sudo service
bluetooth restart. After doing so the bluetooth indicator icon
reappeared and automatically re-paired with my devices.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
When switching between two user sessions with Gnome Screensaver, the
keystrokes of your password are sent to the Gnome Screensaver Lock
Screen and are also echoed into the focused application of the
underlying user session.
This bug only happens when switching between users
Public bug reported:
The 'compass version' command and 'compass -v' option are broken in the
packaged version of compass on Precise, 0.11.6~dfsg-1.
Here is the full traceback:
$ compass -v --trace
Errno::ENOENT on line 25 of
/usr/lib/ruby/vendor_ruby/sass/../compass/version.rb: No such file
apport brought me here with the same error: update-manager crashed when
I tried to use it to update a broken packaging system. One of the
packages has a broken Depends section.
In my case the python-uno package was broken after running the upgrade.
This bug tracks the broken package:
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/965476
Title:
Can't install Precise guest on Oneiric host
To manage notifications about this bug go to:
Public bug reported:
The lxc-create command fails when using the ubuntu template to install a
Precise guest on an Oneiric host. This is because the template tries to
install the lxcguest package in the Precise container, but that package
is no longer present in Precise.
Steps to reproduce:
On
cjwatson suggested the following workaround on IRC:
cjwatson maybe you can apply 0039-no-lxcguest-in-p-template from
http://launchpadlibrarian.net/92357679/lxc_0.7.5-3ubuntu19_0.7.5-3ubuntu20.diff.gz
** Attachment added: 0039-no-lxcguest-in-p-template
** Summary changed:
- Can't install Precise guest on Oneiric host
+ lxc-create fails creating a Precise container on an Oneiric host
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/965476
Public bug reported:
The lxc-create command fails when using the ubuntu template to install a
Precise guest on an Oneiric host. This is because the template tries to
install the lxcguest package in the Precise container, but that package
is no longer present in Precise.
Steps to reproduce:
On
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/965476
Title:
Can't install Precise guest on Oneiric host
To manage notifications about this bug go to:
cjwatson suggested the following workaround on IRC:
cjwatson maybe you can apply 0039-no-lxcguest-in-p-template from
http://launchpadlibrarian.net/92357679/lxc_0.7.5-3ubuntu19_0.7.5-3ubuntu20.diff.gz
** Attachment added: 0039-no-lxcguest-in-p-template
** Summary changed:
- Can't install Precise guest on Oneiric host
+ lxc-create fails creating a Precise container on an Oneiric host
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/965476
Title:
I have not seen this bug since upgrading to Onieric.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/828059
Title:
xchat crashes with SIGSEGV in g_str_hash() when closing conversation
windows
To
Public bug reported:
The Banshee application freezes just seconds after application startup,
putting all four(!) of my laptop's cpus at 95% usage.
The only way to shut down the application is to 'Force Quit'.
I ran banshee from the command line with 'banshee --debug' and have
attached the
** Attachment added: Debug log with crash tracebacks
https://bugs.launchpad.net/bugs/877016/+attachment/2556074/+files/banshee-crash-debug-log.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I encountered a very similar problem running a development version of
Oneiric, openssh-client 1:5.8p1-7ubuntu1.
Michael, try using 'curl -I --socks5 127.0.0.1:1080 http://thesite'. I
find that curl connects perfectly through the SOCKS SSH tunnel and that
Firefox 7.0.1+build1+nobinonly-0ubuntu1
Installing the FoxProxy Firefox extension allowed the Firefox SOCKS
proxy connection to start working. According to the SSH output the
browser now sets up proxy connections just like curl does.
debug1: Connection to port 12345 forwarding to socks port 0 requested.
debug2: fd 7 setting
I encountered a very similar problem running a development version of
Oneiric, openssh-client 1:5.8p1-7ubuntu1.
Michael, try using 'curl -I --socks5 127.0.0.1:1080 http://thesite'. I
find that curl connects perfectly through the SOCKS SSH tunnel and that
Firefox 7.0.1+build1+nobinonly-0ubuntu1
Installing the FoxProxy Firefox extension allowed the Firefox SOCKS
proxy connection to start working. According to the SSH output the
browser now sets up proxy connections just like curl does.
debug1: Connection to port 12345 forwarding to socks port 0 requested.
debug2: fd 7 setting
Public bug reported:
None of the settings windows opened from the System Settings dialog
respond to the Ctrl-w shortcut for closing windows.
Steps to reproduce:
1. Open the System Settings dialog via the indicator menu
2. Open a window for any individual setting (Sound, Keyboard, Power,)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/863549
Title:
Ctrl-w does not close control center windows
To manage notifications about this bug go to:
Is there a Human Interface Guideline document for GNOME that I could
reference in the report? Surely this is a violation.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/863549
Title:
Ctrl-w does
** Description changed:
None of the settings windows opened from the System Settings dialog
respond to the Ctrl-w shortcut for closing windows.
Steps to reproduce:
- 1. Open the System Settings dialog via the indicator menu
- 2. Open a window for any individual setting (Sound,
I just encountered this issue upgrading Natty to Oneiric. It is not
fixed. My system upgrade is now stuck: /etc/apt/sources.list points at
Oneiric, but /etc/lsb-release says Natty.
I tried a workaround of running Update Manager, which wants to update
all packages to Oneiric versions, but it
Public bug reported:
XChat often crashes when I close a pop-up or detached conversation
window.
I have not been able to come up with a series of steps to reliably
reproduce this bug. It somehow involves starting a conversation in a
new xchat dialog window, then closing the conversation window.
** Attachment added: gdb-xchat-2011-07-21_12:31:48.txt
https://bugs.launchpad.net/bugs/828059/+attachment/2285978/+files/gdb-xchat-2011-07-21_12%3A31%3A48.txt
** Summary changed:
- xchat crashed with SIGSEGV in g_str_hash() when closing conversation windows
+ xchat crashes with SIGSEGV in
This bug appears to be related to bug 490731, python-setuptools: import
setuptools returns ValueError: (Missing 'Version:' ...).
--
UserWarning: Unbuilt egg for setuptools [unknown version]
(/usr/lib/python2.6/dist-packages)
https://bugs.launchpad.net/bugs/576434
You received this bug
This completely breaks zc.buildout. If you are bitten by this, you will
see something similar to the following:
An internal error occured due to a bug in either zc.buildout or in a
recipe being used:
Traceback (most recent call last):
...
ValueError: (Missing 'Version:' header and/or PKG-INFO
I spoke too soon. It crashed out twice in a row on me, the second
crash within five minutes of the first. I have attached two new log
files showing this.
I wonder, could the runaway speech-dispatcher process cause the sound
input to crash sooner the second time? Usually when it crashes, I
Yes, it looks like tsched=0 might have lengthened the time between
crashes.
I bet speech-dispatcher is being used by Mumble, which has
text-to-speech messaging capabilities. It is possible that killing
pulseaudio, as I do after an input crash, is causing speech-dispatcher
to go nuts.
--
Well it took a while, but I finally managed to get a verbose log of the
voice input crashing while tsched=0 has been set.
I have also noticed that after the crash a there is a runaway speech-
dispatcher process hanging around. speech-dispatcher runs up to 100%
CPU utilization, and stays there.
Bug 520337 - This does not seem to be necessary. When I built a virtualenv
with a simple test package (e.g. the one in bug 517390) I did not get the
crash described in bug 520337. However, I did need to modify the virtualenv
command to add the --distribute flag:
From the virtualenv PyPi
People affected by this bug in Lucid may also want to track Bug #485944,
Upgrade to virtualenv 1.4.5.
--
[lucid] installs old version of setuptools
https://bugs.launchpad.net/bugs/517390
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Here is a verbose pulseaudio log file using the instructions you posted.
The first file is fine: I stopped logging, then unplugged the headset.
** Attachment added: Pulseaudio detailed log
http://launchpadlibrarian.net/44337671/pulseverbose.log.0
--
pulseaudio input crashes after an hour of
Here is another verbose log file, but this time I unplugged the headset
*before* terminating the log program. Perhaps the file will still be of
use.
** Attachment added: Pulseaudio detailed log #2
http://launchpadlibrarian.net/44337832/pulseverbose.log.1
--
pulseaudio input crashes after an
Public bug reported:
Binary package hint: pulseaudio
Pulseaudio sound input will stop working after an hour of continuous
use, such as a Skype call, or Mumble voice chat. On the Input tab of
the Sound Preferences panel, all of the controls are normal, but the
Input Level meter no longer shows
** Attachment added: Excerpt of input crash cycling from /var/log/syslog
http://launchpadlibrarian.net/44185306/pulseaudio-input-crash-syslog.txt
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/44182908/AlsaDevices.txt
** Attachment added: AplayDevices.txt
** Description changed:
Binary package hint: pulseaudio
- Pulseaudio sound input will crash after an hour of continuous use, such
- as a Skype call, or Mumble voice chat. On the Input tab of the Sound
- Preferences panel, all of the controls are normal, but the Input Level
- meter no longer
Sound output through the both the USB headphones and onboard speakers
still works fine, even after the input via the USB headset microphone
has crashed.
Just to be clear, the USB disconnected/connected messages in the log I
posted are me physically unplugging and replugging the headset in order
*** This bug is a duplicate of bug 223238 ***
https://bugs.launchpad.net/bugs/223238
** This bug has been marked a duplicate of bug 223238
Extremely slow Ajax/Javascript/CSS performance in Firefox 3 using non-free
nvidia-glx-new
--
Lucid firefox renders Launchpad very slowly
@Mike, good find.
No, we do not use the position :fixed css attribute, but from my
reading of bug 223238, it could be triggered by something as trivial as
using a repeating background image :/
Bug 223238 makes this sound pretty wide-spread. Launchpad will not be
the only site on which people
This appears to be an issue in Firefox. Launchpad is only the trigger
for the issue, so I am marking it as Invalid for Launchpad Foundations.
** Changed in: launchpad-foundations
Status: New = Invalid
--
Lucid firefox renders Launchpad very slowly
https://bugs.launchpad.net/bugs/537298
** Changed in: mountall (Ubuntu)
Status: Invalid = New
--
General error mounting filesystems why trying to use the recovery menu
https://bugs.launchpad.net/bugs/488462
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
kautilya, may I ask what your reason is for marking this bug as Invalid?
This really appears to be a bug in mountall, or some related system:
converting it to a question does not fix the issue.
--
General error mounting filesystems why trying to use the recovery menu
Public bug reported:
Binary package hint: mountall
When trying to boot into the recovery console from GRUB, the system will
load, draw the recovery menu options, then throw a General error
mounting filesystems message on the screen, and drop into a maintenance
shell. The error message and
*** This bug is a duplicate of bug 353503 ***
https://bugs.launchpad.net/bugs/353503
** This bug has been marked a duplicate of bug 353503
Report a Problem menu choice non functional
--
[jaunty] Report a Problem (bug report) no longer functions correctly
54 matches
Mail list logo
