[Desktop-packages] [Bug 1211110] Re: network manager openvpn dns push data not updating system DNS addresses
As said above, it is fixed in 17.04 so you just have to upgrade. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/120 Title: network manager openvpn dns push data not updating system DNS addresses Status in network-manager package in Ubuntu: Confirmed Status in openvpn package in Ubuntu: Confirmed Bug description: [Triage Notes] This bug can no longer make progress. Please see comment 50 for details and further instructions. [Original Description] When IPv4 Method is set to Automatic VPN, DNS address recieved from OpenVPN server do not update resolv.conf. This can be achieved when using a standard openvpn config file by adding the lines: script-security 2 up /etc/openvpn/update-resolv-conf down /etc/openvpn/update-resolv-conf In Network-manager there seems to be no option to run connection specific scripts and the DNS data from the server is ignored. Ubuntu 13.04 Network-manager 0.9.8.0-0ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/120/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1211110] Re: network manager openvpn dns push data not updating system DNS addresses
@msclectera, the problem is not in OpenVPN config files. The problem is in NetworkManager (that does not store configs in .ovpn format and does not support running update-resolv-conf.sh). Most (if not all) of us are already using OpenVPN configs that include up and down scripts, nevertheless these settings get lost when imported into NM. Of course openvpn from terminal works, but that is not really the point of this bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/120 Title: network manager openvpn dns push data not updating system DNS addresses Status in network-manager package in Ubuntu: Expired Status in openvpn package in Ubuntu: Expired Bug description: [Triage Notes] This bug can no longer make progress. Please see comment 50 for details and further instructions. [Original Description] When IPv4 Method is set to Automatic VPN, DNS address recieved from OpenVPN server do not update resolv.conf. This can be achieved when using a standard openvpn config file by adding the lines: script-security 2 up /etc/openvpn/update-resolv-conf down /etc/openvpn/update-resolv-conf In Network-manager there seems to be no option to run connection specific scripts and the DNS data from the server is ignored. Ubuntu 13.04 Network-manager 0.9.8.0-0ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/120/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1644098] Re: Network Manager + OpenVPN does not respond to DNS server change on second connection attempt
I confirm the issue. One detail that should be noted is that during the first connection DNS works, but it leaks! I.e. if you are using a VPN service for privacy purposes you'd expect NM to pick up the DNS settings from the VPN provider (like openvpn from terminal does) and don't use your home router as a DNS server while the VPN is on. Subsequent connections don't have any DNS working, not even a leaky one. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1644098 Title: Network Manager + OpenVPN does not respond to DNS server change on second connection attempt Status in network-manager package in Ubuntu: Confirmed Bug description: Scenario: Discovered on Kubuntu 16.10, upgraded from a fresh install of 16.04. While I only have the one computer to test with, the 16.10 is definitely relevant (I did not have this problem on 16.04) but I can't tell if the upgrade is part of it, (the upgrade may or may not be relevant). Have "full time" wired or wireless connection (does not matter which used) Part time OpenVPN connection set up via NetworkManager. Steps to reproduce 1. Fresh boot 2. ping a device on the VPN network (eg amachine.remotelan ) Result: "ping: amachine.remotelan: Name or service not known" 3. Connect to the VPN service via Network Manager. 4. ping amachine.remotelan - result: PING amachine.remotelan (192.168.68.44) 56(84) bytes of data. 64 bytes from amachine.remotelan (192.168.68.44): icmp_seq=1 ttl=127 time=7.75 ms 5. Disconnect from the VPN service again. ping result again "ping: amachine.remotelan: Name or service not known" 6. Reconnect to the VPN again, and ping again Observed: "ping: amachine.remotelan: Name or service not known" However "ping 192.168.68.44" responds successfully as expected Expected: PING ... 192.168 64 bytes from .. etc to the ping by name --- Further info I'm going to add in a subsequent comment. (just annotating syslog right now!) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1644098/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1211110] Re: network manager openvpn dns push data not updating system DNS addresses
Indeed! And on Yakkety the situation is even worse. With the new VPN menu the first VPN connection leaks DNS, the following connections do not work until one changes the resolv.conf file to some static IP. Compare this to running openvpn from the terminal (which works perfectly) and you will see the problem is huge. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/120 Title: network manager openvpn dns push data not updating system DNS addresses Status in network-manager package in Ubuntu: Incomplete Status in openvpn package in Ubuntu: Incomplete Bug description: [Triage Notes] This bug can no longer make progress. Please see comment 50 for details and further instructions. [Original Description] When IPv4 Method is set to Automatic VPN, DNS address recieved from OpenVPN server do not update resolv.conf. This can be achieved when using a standard openvpn config file by adding the lines: script-security 2 up /etc/openvpn/update-resolv-conf down /etc/openvpn/update-resolv-conf In Network-manager there seems to be no option to run connection specific scripts and the DNS data from the server is ignored. Ubuntu 13.04 Network-manager 0.9.8.0-0ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/120/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1181106] Re: Failed to change profile to A2DP in 13.04 (Raring), 13.10 (saucy), and 14.04 (trusty)
I encountered the same issue in Ubuntu 15.10. Restarting the bluetooth service as per #35 fixes the problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1181106 Title: Failed to change profile to A2DP in 13.04 (Raring), 13.10 (saucy), and 14.04 (trusty) Status in Bluez Utilities: New Status in pulseaudio package in Ubuntu: Confirmed Status in pulseaudio package in Debian: Fix Released Bug description: I upgraded to 13.04 recently and my A2DP profile, which had been working great under 12.10 is suddenly gone. Neither my blueman applet nor the built-in bluetooth manager applet can connect my external bluetooth speaker to the A2DP profile. They can connect to the bluetooth device itself just fine. Steps I'm using: * using blueman, I can connect to the external bluetooth speaker and view the device in the devices listing * I can connect the device to the Audio sink and I get a message saying it is now connected and will "show in the PulseAudio mixer" * After connecting the external speaker to the audio sink, I can also see the device in the "Play sound through" listing in the Sound system control panel, but the icon has a circle with a line through it. * but if I right-click the device and choose "Audio Profile" from the context menu and try to select "High Fidelity Playback (A2DP)" as the new profile, I get an error message stating "failed to change profile to a2dp" I've already added "Enable=Socket" in /etc/bluetooth/audio.conf, without that I can't pair my headset. Now I can pair it, but I can't activate the A2DP profile. When I try to activate it, I see this message in my syslog : pulseaudio[2603]: [pulseaudio] module-bluetooth-device.c: Profile has no transport I tried the kernel 3.9.0 because of a sound problem with my soundcard, this kernel fixed my soundcard problem, but A2DP still doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1181106/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1211110] Re: network manager openvpn dns push data not updating system DNS addresses
Tristan, how is that a leak? Connections to 8.8.8.8 will go through the VPN, not outside of it. By the way, the problem remaining is that sometimes NM seems to still use the DNS of the router as well. It's as if without VPN you have say 192.168.0.1 as primary DNS, but with VPN you get these DNS servers: 8.8.8.8 8.8.4.4 192.168.0.1 (for example) Then sometimes the third DNS receives the query. I will experiment with setting the static DNS to the Wi-Fi connection as well. Of course it would be easier if this bug actually gets fixed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/120 Title: network manager openvpn dns push data not updating system DNS addresses Status in network-manager package in Ubuntu: Confirmed Status in openvpn package in Ubuntu: Confirmed Bug description: When IPv4 Method is set to Automatic VPN, DNS address recieved from OpenVPN server do not update resolv.conf. This can be achieved when using a standard openvpn config file by adding the lines: script-security 2 up /etc/openvpn/update-resolv-conf down /etc/openvpn/update-resolv-conf In Network-manager there seems to be no option to run connection specific scripts and the DNS data from the server is ignored. Ubuntu 13.04 Network-manager 0.9.8.0-0ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/120/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1211110] Re: network manager openvpn dns push data not updating system DNS addresses
A simple workaround is to edit your VPN connection (via NM) and set up static DNS, for example using Google servers: 8.8.8.8, 8.8.4.4 This way, the DNS request is sent through an external IP, hence it is routed using the VPN. If you were using the default DNS from your router (probably an internal IP like 192.168.x.y) then the DNS request would go outside the VPN. I just discovered that Google provides also IPv6 servers, by searching for "IPv6 DNS Servers" on DuckDuckGo (a very convenient table of DNS servers by provider shows up). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/120 Title: network manager openvpn dns push data not updating system DNS addresses Status in network-manager package in Ubuntu: Confirmed Status in openvpn package in Ubuntu: Confirmed Bug description: When IPv4 Method is set to Automatic VPN, DNS address recieved from OpenVPN server do not update resolv.conf. This can be achieved when using a standard openvpn config file by adding the lines: script-security 2 up /etc/openvpn/update-resolv-conf down /etc/openvpn/update-resolv-conf In Network-manager there seems to be no option to run connection specific scripts and the DNS data from the server is ignored. Ubuntu 13.04 Network-manager 0.9.8.0-0ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/120/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 978604] Re: Banshee/Rhythmbox regularly stop playing audio when left on in the background
I was encountering this bug after enabling the ReplayGain plug-in. I disabled it and the problem seems to be solved. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/978604 Title: Banshee/Rhythmbox regularly stop playing audio when left on in the background Status in pulseaudio package in Ubuntu: Confirmed Status in pulseaudio source package in Precise: Confirmed Bug description: If Banshee or Rhythmbox is left playing in the background they will randomly stop playing in the latest builds of Ubuntu 12.04. Starting a new piece of music usually fixes the problem. If left to its own devices, the music will start playing again at some random time, at some random position. This problem exists on both my desktop machine (custom built Intel machine) and my laptop (Macbook 5,1). It has been happening for several months now. I became frustrated enough to load up pulseaudio in debugging mode. The log shows that when the music player just finishes playing one piece, and tries to start the next piece, you see something like this: --- ( 335.399| 34.388) D: [alsa-sink] sink-input.c: Requesting rewind due to corking ( 335.400| 0.001) D: [alsa-sink] alsa-sink.c: Requested to rewind 65536 bytes. ( 335.400| 0.000) D: [alsa-sink] alsa-sink.c: Limited to 14820 bytes. ( 335.400| 0.000) D: [alsa-sink] alsa-sink.c: before: 3705 ( 335.400| 0.000) D: [alsa-sink] alsa-sink.c: after: 3705 ( 335.400| 0.000) D: [alsa-sink] alsa-sink.c: Rewound 14820 bytes. ( 335.400| 0.000) D: [alsa-sink] sink.c: Processing rewind... ( 335.400| 0.000) D: [alsa-sink] sink.c: latency = 1643 ( 335.400| 0.000) D: [alsa-sink] sink-input.c: Have to rewind 14820 bytes on render memblockq. ( 335.400| 0.000) D: [alsa-sink] sink-input.c: Have to rewind 14820 bytes on implementor. ( 335.400| 0.000) D: [alsa-sink] source.c: Processing rewind... ( 335.400| 0.000) D: [pulseaudio] module-suspend-on-idle.c: Sink alsa_output.pci-_00_1b.0.analog-stereo becomes idle, timeout in 5 seconds. ( 335.402| 0.001) D: [alsa-sink] alsa-sink.c: hwbuf_unused=0 ( 335.402| 0.000) D: [alsa-sink] alsa-sink.c: setting avail_min=15502 ( 335.402| 0.000) D: [alsa-sink] alsa-sink.c: Requested volume: 0: 34% 1: 34% ( 335.402| 0.000) D: [alsa-sink] alsa-sink.c:in dB: 0: -28.11 dB 1: -28.11 dB ( 335.402| 0.000) D: [alsa-sink] alsa-sink.c: Got hardware volume: 0: 34% 1: 34% ( 335.402| 0.000) D: [alsa-sink] alsa-sink.c: in dB: 0: -28.00 dB 1: -28.00 dB ( 335.402| 0.000) D: [alsa-sink] alsa-sink.c: Calculated software volume: 0: 100% 1: 100% (accurate-enough=yes) ( 335.402| 0.000) D: [alsa-sink] alsa-sink.c: in dB: 0: -0.11 dB 1: -0.11 dB ( 335.402| 0.000) D: [alsa-sink] sink.c: Volume not changing ( 335.402| 0.000) D: [alsa-sink] alsa-sink.c: Requested to rewind 65536 bytes. ( 335.402| 0.000) D: [alsa-sink] alsa-sink.c: Limited to 15300 bytes. ( 335.402| 0.000) D: [pulseaudio] module-suspend-on-idle.c: Sink alsa_output.pci-_00_1b.0.analog-stereo becomes idle, timeout in 5 seconds. ( 335.402| 0.000) D: [alsa-sink] alsa-sink.c: before: 3825 ( 335.402| 0.000) D: [pulseaudio] core.c: Hmm, no streams around, trying to vacuum. ( 335.402| 0.000) D: [alsa-sink] alsa-sink.c: after: 3825 ( 335.402| 0.000) D: [alsa-sink] alsa-sink.c: Rewound 15300 bytes. ( 335.402| 0.000) D: [alsa-sink] sink.c: Processing rewind... ( 335.402| 0.000) D: [alsa-sink] sink.c: latency = 1402 ( 335.402| 0.000) D: [alsa-sink] source.c: Processing rewind... ( 335.402| 0.000) I: [pulseaudio] sink-input.c: Freeing input 3 "'zero-project - 05 - Forest of the unicorns' by 'zero-project'" ( 335.402| 0.000) D: [pulseaudio] module-stream-restore.c: Not restoring device for stream sink-input-by-media-role:music, because already set to 'alsa_output.pci-_00_1b.0.analog-stereo'. ( 335.403| 0.000) D: [pulseaudio] module-intended-roles.c: Not setting device for stream Playback Stream, because already set. ( 335.403| 0.000) I: [pulseaudio] module-stream-restore.c: Restoring volume for sink input sink-input-by-media-role:music. ( 335.403| 0.000) I: [pulseaudio] module-stream-restore.c: Restoring mute state for sink input sink-input-by-media-role:music. ( 335.403| 0.000) D: [pulseaudio] module-suspend-on-idle.c: Sink alsa_output.pci-_00_1b.0.analog-stereo becomes busy. ( 335.403| 0.000) I: [pulseaudio] resampler.c: Forcing resampler 'copy', because of fixed, identical sample rates. ( 335.403| 0.000) I: [pulseaudio] resampler.c: Using resampler 'copy' ( 335.403| 0.000) I: [pulseaudio] resampler.c: Using float32le as working format. ( 335.403| 0.000) D: [pulseaudio] memblockq.c: memblockq requested: maxlength=33554432,
[Desktop-packages] [Bug 1445039] Re: Device '/dev/video0' is busy
«attempts to take a few pictures using root seem to clear this problem up» If you mean you run it with sudo, this does not work for me as workaround. I get the same error. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1445039 Title: Device '/dev/video0' is busy Status in cheese package in Ubuntu: Confirmed Bug description: First time I run cheese during the day, an attempt to take a picture typically results in an error being displayed on a black background in the preview pane There was an error playing video from the webcam (odd for two reasons, one I'm taking a picture, not video, and two... it's an error message that indicated something indeed went wrong) (cheese:2506): cheese-WARNING **: Device '/dev/video0' is busy: gstv4l2object.c(2838): gst_v4l2_object_set_format (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstV4l2Src:video_source: Call to S_FMT failed for YU12 @ 1280x720: Device or resource busy webcam: description: Video product: HD WebCam vendor: NC.21411.01N415006E5LM0002 physical id: 1 bus info: usb@3:1.1 version: 0.02 capabilities: usb-2.00 configuration: driver=uvcvideo maxpower=500mA speed=480Mbit/s linux: Linux Hedy 3.19.0-13-generic #13-Ubuntu SMP Thu Apr 9 22:56:40 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux ubuntu : 15.04 cheese: Installed: 3.14.1-2ubuntu4 Candidate: 3.14.1-2ubuntu4 The timer goes off, flash goes off, but no photo is saved in my ~/Webcam directory. Attempts to take video, or attempts to take a few pictures using root seem to clear this problem up and after I have done so, cheese seems to be initialized correctly, and it works fine for awhile. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: cheese 3.14.1-2ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3 Uname: Linux 3.19.0-13-generic x86_64 ApportVersion: 2.17.1-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Apr 16 10:20:25 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-07-09 (280 days ago) InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Alpha amd64 (20140708) SourcePackage: cheese UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1445039/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1282299] Re: Rhythmbox not added to indicator-sound menu
Confirmed. I noticed it today while installing Ubuntu 14.04 to a friend. Haven't noticed it before because on my laptop I used the upgrade tool. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1282299 Title: Rhythmbox not added to indicator-sound menu Status in “rhythmbox” package in Ubuntu: Confirmed Bug description: To reproduce: 1. If rhythmbox is already on your sound menu, use dconf-editor to reset /com/canonical/indicator/sound. 2. Run rhythmbox. Expected result: Rhythmbox is shown in the sound menu when left clicking the sound icon. Actual result: Rhythmbox is not shown. Workaround: Manually add rhythmbox to the list of interested players with dconf-editor. All other audio players are working correctly and showing up in the sound menu. This bug is also reproducable in a Unity session. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: rhythmbox 3.0.1-1ubuntu9 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Feb 19 22:55:51 2014 InstallationDate: Installed on 2014-02-11 (8 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140210) SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1282299/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1170832] Re: Facebook Requires Authorization when already authorized
The problem persists in Ubuntu 13.10. I think this bug affects a lot of users, so it should be addressed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to telepathy-gabble in Ubuntu. https://bugs.launchpad.net/bugs/1170832 Title: Facebook Requires Authorization when already authorized Status in Jabber/XMPP connection manager: Fix Released Status in “telepathy-gabble” package in Ubuntu: Confirmed Status in “telepathy-gabble” source package in Precise: Triaged Status in “telepathy-gabble” source package in Quantal: Triaged Status in “telepathy-gabble” source package in Raring: Triaged Status in “telepathy-gabble” source package in Saucy: Confirmed Status in “telepathy-gabble” package in Debian: Fix Released Bug description: I am running fully updated 13.04 64-bit. I simply cannot get empathy/UOA to connect to facebook. When I add the account in UOA everything seems to go well, facebook login page loads, it logs in successfully, facebook recognizes the session as safari on linux; but upon completing the setup in UOA empathy refuses to connect to it and keeps telling me it requires authorization. I've Tried the following: Removing the account from UOA Ending all active sessions on facebook and deleting the ubuntu app rebooting adding account in UOA, and allowing the ubuntu app to manage my messages etc... Didn't help at all. pidgin connects fine on the same computer. Sometimes it does let me add it and it works for a while, but eventually this issue happens again and leaves me totally unable to successfully add a facebook account for quite some time, until it randomly decides it wants to work again. Empathy/UOA in 13.04 has been unreliable to the point of ridiculousness, the application is basically unusable and can't handle the one basic task of an instant messaging program, which is connecting to my accounts reliably. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: empathy 3.6.4-0ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Fri Apr 19 16:57:50 2013 InstallationDate: Installed on 2013-04-17 (1 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130416) MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: empathy UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/telepathy-gabble/+bug/1170832/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 885492] Re: p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so
Since I test every tutorial I write and I've used it personally and I have a fully working Wine after that, could you check twice before saying my instructions don't work? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/885492 Title: p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/gnome- keyring-pkcs11.so Status in “gnome-keyring” package in Ubuntu: Confirmed Bug description: whenever I try to do a `git push`, I get this error: `p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory` Distributor ID: Ubuntu Description: Ubuntu precise (development branch) Release: 12.04 Codename: precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/885492/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 885492] Re: p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so
herta, I was replying to the comment immediately above, written by cement_head. :) If you have enabled email notifications you receive every comment made on this bug report. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/885492 Title: p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/gnome- keyring-pkcs11.so Status in “gnome-keyring” package in Ubuntu: Confirmed Bug description: whenever I try to do a `git push`, I get this error: `p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory` Distributor ID: Ubuntu Description: Ubuntu precise (development branch) Release: 12.04 Codename: precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/885492/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 885492] Re: p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so
Dirk, yes because it's a bit wrong, you need to do some symlinking. See here for my procedure (in Italian, but bash is always bash): http://andrealazzarotto.com/2012/08/27/quando-wine-non-trova-gnome- keyring-pkcs11-so/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/885492 Title: p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/gnome- keyring-pkcs11.so Status in “gnome-keyring” package in Ubuntu: Confirmed Bug description: whenever I try to do a `git push`, I get this error: `p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory` Distributor ID: Ubuntu Description: Ubuntu precise (development branch) Release: 12.04 Codename: precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/885492/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
