Hey Ian.
Nevermind. After looking at the patch file, I realized what I needed to
do and I can report that my m6700 from 9 years ago (what a journey) can
finally make use of the mic on my Bluetooth headset.
Cheers,
Anthony.
For anyone looking for the same instructions as I was, I used the
Hi Ian.
I've had my m6700 since 2012 and have never been able to use any
Bluetooth headset.
Any chance you can provide pointers on what incantations one needs to
call upon to get this fixed like you've done on your laptop?
Cheers,
Anthony.
--
You received this bug notification because you are
I too have been seeing this issue on my Ubuntu 16.04.6 LTS installation
and after living with it for a long long time, decided to hunt down
reports of others with the issue. As I now see, it is a known issue.
That sort of made me feel better - specifically that misery loves
company - :(.
Here is
** Attachment added: "syslog lines pertinent to vpn connection failure"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1640970/+attachment/4839770/+files/failure
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm also going to add to this.
I have just done a clean install of 16.04 LTS and OpenVPN connects
intermittently. Despite installing openvpn, network-manager-openvpn,
and network-manager-openvpn-gnome, the "Configure VPN..." option remains
grayed out.
In addition, after creating my VPN profile
** Attachment added: "syslog lines pertinent to vpn connection success"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1640970/+attachment/4839771/+files/success
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
In comparison, when attempting to lunch a VitualBox VM, it fails with a
slightly better error message at least directing one to investigate what
else would be using a hypervisor. But it also suggests some rather
drastic steps to do with recompiling the kernel to remove KVM kernel
extension - wow:
I've been struggling with this for nearly 2 hours before I realized that
I was running a virtualbox vm in headless mode. Was trying to create a
qemu-kvm vm and it kept failing with symptoms similar to those reported
here.
What would be good is getting qemu-kvm to at least check if another
This begs 2 questions from my end:
1. How does the removal of such a critical VPN component get past QA?
2. How is it that the very vulnerable PPTP VPN is still readily available while
a more secure option gets tossed to the gutter?
Can anyone at Canonical please answer these questions?
--
I too am getting the same issue. However, for me the crash doesn't
happen until I try to resize the window - like exiting from full screen
via F11 or even just exiting the application. In addition, just
attempting to switch to a different workspace also causes X/Unity to
hang!
On my system,
Being that I'm still having this issue on Ubuntu 15.10, I can only
conclude that this appears to be a design philosophy at Canonical rather
than a bug. Logical volumes that are not necessary for system boot
and/or are not on the primary disk where the OS is installed are not
made available /
I get this from time to time as well and it gets frustrating. I can
resolve the issue by restarting lightdm (or rebooting), but it is
frustrating as hell as I'm heavily dependent on that shortcut. For
instance, I currently have 6 VM's running on my laptop and right now
have to shut them down
Hi there.
I'm running Ubuntu Trusty Tahr (14.04) 64bit and I'm affected by this
bug.
By following the instructions here (especially comment #101 by Chris
(poser) on 2013-09-15), I was able to get HSP/HFP working on my system.
I realized something was broken when I tried to pair my Laptop with a
I have the same problem and the solution for me was to manually change the
profile. This post on the Ubuntu forums was very helpful:
http://askubuntu.com/questions/287254/ubuntu-13-04-bluetooth-a2dp-does-not-work
In essence, you need to run the following command to switch profile to
a2dp:
sudo
*** This bug is a duplicate of bug 1173623 ***
https://bugs.launchpad.net/bugs/1173623
It is time to leave the Ubuntu field and try something else. I pity
non-techies as they are left with no option but to cope with this
ridiculous crippling of a perfectly working feature just 'cause a
Forgot to add that the LV's are for media files and virtualbox vms so
the system could otherwise boot (if I chose to skip mounting the LV's
via 'S'). I'd than still have to run 'vgchange -ay' then manually mount
the partitions after the system was up.
Cheers,
ak.
--
You received this bug
Just wanted to add that after doing a vgrename without first doing a
vgchange -an, I ended up with a system that could not activate the LV's
on boot. I had to drop to a root shell (via 'M') then type vgchange
-ay followed by ctrl+d to get a system (re)boot to complete
successfully. I'll add that
UPDATE:
I got tired of the workaround and reverted to gnome-screensaver which
has since fixed my blank screen w/ mouse issue:
sudo apt-get install --reinstall ubuntu-desktop gnome-screensaver
sudo apt-get remove --purge xscreensaver* sudo apt-get autoremove
I'm now back to a bland blank screen
Recently I underwent a botched nvidia-prime install that left a bitter taste in
my mouth:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1249067
I had to purge my system of all nvidia drivers (apt-get --purge remove
nvidia\*), then reinstall them:
https://wiki.ubuntu.com/Bumblebee
In the end, I just gave up on nvidia-prime and went back to bumblebee:
https://wiki.ubuntu.com/Bumblebee
Hopefully by the time I'm migrating to the next LTS version, nvidia-
prime will be ready for prime time - ;)!
Cheers,
ak.
--
You received this bug notification because you are a member of
Let me add that although nvidia-prime maybe working for some, the above
statement should really have quantified it more to be specific to my use
case:
Dell Precision M6700 w/ Optimus Tech
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor
Graphics Controller (rev 09)
Below is a transcript of what happened (I ran the commands as root -
sudo su -):
# apt-get --purge remove nvidia-331-updates nvidia-331
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
nvidia-304
I'm using bumblebee to enable optimus. Is this functionality now built
into the Nvidia driver?
Cheers,
ak.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1249067
Title:
nvidia prime causes freeze
I've just noticed that when I attempt to purge nvidia-331*, systems
insists on installing nvidia-304. Why?
# apt-get --purge remove nvidia-331
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
** Attachment added: update-alternatives --display x86_64-linux-gnu_gl_conf
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1249067/+attachment/3970807/+files/1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: update-alternatives --display i386-linux-gnu_gl_conf
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1249067/+attachment/3970808/+files/2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
According to my apt history log:
Start-Date: 2014-02-05 08:00:40
Commandline: aptdaemon role='role-commit-packages' sender=':1.80'
Upgrade: nvidia-prime:amd64 (0.4.2~hybrid0.0.1, 0.5~hybrid0.0.2), lightdm:amd64
(1.2.3-0ubuntu2.3, 1.2.3-0ubuntu2.4), python-apt:amd64 (0.8.3ubuntu7.1,
Attaching /var/log/nvidia-prime-upstart.log
** Attachment added: nvidia-prime-upstart.log
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1249067/+attachment/3969442/+files/nvidia-prime-upstart.log
--
You received this bug notification because you are a member of Ubuntu
Bugs,
This morning (20140205 @ ~8am AEDST) accepted an update on my system
(nvidia-prime amongst others). However, I was unable to login
afterwards. After prowling my /var/log folder, I came across /var/log
/nvidia-prime-upstart.log (attached) which suggested that nvidia-prime
was the issue. I was
29 matches
Mail list logo
