[Desktop-packages] [Bug 1965535] Re: Stop recommending snap
+1 For the record, Snap being forced upon users for critical packages is the primary reason why I recently dropped Ubuntu and stopped recommending the distro to others, after using it for over 15 years. Container-based packaging has its place. Snap has some interesting features compared to FlatPak and AppImage. However, none of them are suitable replacements for deb & apt, and this is really driven home when they're used for core packages like the web browser. Snap in particular has multiple fundamental design and implementation problems that make it intolerable. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1965535 Title: Stop recommending snap Status in ubuntu-meta package in Ubuntu: Opinion Bug description: Currently, ubuntu recommends installing snap by default, and some apps are slowly transitioning from DEB-based installation to Snap-based installation. APT is great, and facilitates having a clean, maintainable system. The snap project is not very well designed or engineered (just changing the location of where snap data is located is taking the project more than 5 years because it was hardcoded: https://bugs.launchpad.net/snapd/+bug/1575053). Snaps are large and VERY slow. The design of snap, as well as the way that decisions are made, are very questionable, and are receiving increasing amounts of criticism. I'd like to request that Ubuntu stops recommending snap, stops transitioning towards snaps, and we come back to defaulting to DEB/APT-based installation for all apps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1965535/+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 1547589] Re: rtkit-daemon flooding syslog
** Bug watch added: github.com/heftig/rtkit/issues #22 https://github.com/heftig/rtkit/issues/22 ** Also affects: rtkit via https://github.com/heftig/rtkit/issues/22 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rtkit in Ubuntu. https://bugs.launchpad.net/bugs/1547589 Title: rtkit-daemon flooding syslog Status in Rtkit: Unknown Status in rtkit package in Ubuntu: Confirmed Status in rtkit package in Debian: Confirmed Bug description: rtkit is flooding syslog with the following: Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 processes of 1 users. Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for user '1000', denying request. This may be related to but #1547585 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: rtkit 0.11-4 ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1 Uname: Linux 4.4.0-6-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 19 11:42:58 2016 InstallationDate: Installed on 2016-02-11 (7 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210) SourcePackage: rtkit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/rtkit/+bug/1547589/+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 1877219] Re: dozens of empty grilo-plugin-cache folders polluting /tmp
** Bug watch added: gitlab.gnome.org/GNOME/grilo-plugins/-/issues #70 https://gitlab.gnome.org/GNOME/grilo-plugins/-/issues/70 ** Also affects: grilo-plugins via https://gitlab.gnome.org/GNOME/grilo-plugins/-/issues/70 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to grilo-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1877219 Title: dozens of empty grilo-plugin-cache folders polluting /tmp Status in Grilo Plugins: Unknown Status in grilo-plugins package in Ubuntu: New Bug description: My /tmp folder has dozens of empty folders with names like grilo- plugin-cache-ABCDEF. I don't know anything about grilo-plugins, but surely they can do their job without leaving endless garbage directories behind when they're done? $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 19.10 Release: 19.10 Codename: eoan $ dpkg-query --show grilo-plugins-0.3-base grilo-plugins-0.3-base:amd64 0.3.9-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/grilo-plugins/+bug/1877219/+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 1877219] [NEW] dozens of empty grilo-plugin-cache folders polluting /tmp
Public bug reported: My /tmp folder has dozens of empty folders with names like grilo-plugin- cache-ABCDEF. I don't know anything about grilo-plugins, but surely they can do their job without leaving endless garbage directories behind when they're done? $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 19.10 Release:19.10 Codename: eoan $ dpkg-query --show grilo-plugins-0.3-base grilo-plugins-0.3-base:amd640.3.9-1ubuntu1 ** Affects: grilo-plugins (Ubuntu) Importance: Undecided Status: New ** Description changed: My /tmp folder has dozens of empty folders with names like grilo-plugin- cache-ABCDEF. I don't know anything about grilo-plugins, but surely they can do their job without leaving endless garbage directories behind when they're done? + + $ lsb_release -a + No LSB modules are available. + Distributor ID: Ubuntu + Description: Ubuntu 19.10 + Release: 19.10 + Codename: eoan + + $ dpkg-query --show grilo-plugins-0.3-base + grilo-plugins-0.3-base:amd64 0.3.9-1ubuntu1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to grilo-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1877219 Title: dozens of empty grilo-plugin-cache folders polluting /tmp Status in grilo-plugins package in Ubuntu: New Bug description: My /tmp folder has dozens of empty folders with names like grilo- plugin-cache-ABCDEF. I don't know anything about grilo-plugins, but surely they can do their job without leaving endless garbage directories behind when they're done? $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 19.10 Release: 19.10 Codename: eoan $ dpkg-query --show grilo-plugins-0.3-base grilo-plugins-0.3-base:amd64 0.3.9-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grilo-plugins/+bug/1877219/+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 1528173] Re: org.freedesktop.DBus.Properties.GetAll fails always for fi.w1.wpa_supplicant1.Interface interface
I'm actually a bit confused -- the bug status is "fix released" but it is not at all clear to me in what Ubuntu release this fix has been applied. Can someone clarify this for me? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1528173 Title: org.freedesktop.DBus.Properties.GetAll fails always for fi.w1.wpa_supplicant1.Interface interface Status in wpa package in Ubuntu: Fix Released Bug description: With our package for wpa-supplicant a call $ sudo gdbus call -y -d fi.w1.wpa_supplicant1 -o /fi/w1/wpa_supplicant1/Interfaces/1 -m org.freedesktop.DBus.Properties.GetAll 'fi.w1.wpa_supplicant1.Interface' fails always with Error: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: No readable properties in this interface The reason for this is that the internal properties getter routine will never return any result when one internal getter fails. The responsible property here is the "Stations" one which was added by a patch in Ubuntu and is not available upstream. Take a look at https://bazaar.launchpad.net/~ubuntu- branches/ubuntu/wily/wpa/wily/view/head:/debian/patches/dbus- available-sta.patch The getter method wpas_dbus_getter_stas expects the ap_iface element to be see which isn't always the case and if that isn't true it will return false and causes the whole Properties.GetAll call to fail. The expected result is that the getter just returns an empty list if it can't determine the actual value. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1528173/+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 1528173] Re: org.freedesktop.DBus.Properties.GetAll fails always for fi.w1.wpa_supplicant1.Interface interface
This bug completely breaks WiFi support on my system using ConnMan. Took a bit to hunt down and I also wrote my own patch before finding this bug report. Can we please get this fix pushed out? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1528173 Title: org.freedesktop.DBus.Properties.GetAll fails always for fi.w1.wpa_supplicant1.Interface interface Status in wpa package in Ubuntu: Fix Released Bug description: With our package for wpa-supplicant a call $ sudo gdbus call -y -d fi.w1.wpa_supplicant1 -o /fi/w1/wpa_supplicant1/Interfaces/1 -m org.freedesktop.DBus.Properties.GetAll 'fi.w1.wpa_supplicant1.Interface' fails always with Error: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: No readable properties in this interface The reason for this is that the internal properties getter routine will never return any result when one internal getter fails. The responsible property here is the "Stations" one which was added by a patch in Ubuntu and is not available upstream. Take a look at https://bazaar.launchpad.net/~ubuntu- branches/ubuntu/wily/wpa/wily/view/head:/debian/patches/dbus- available-sta.patch The getter method wpas_dbus_getter_stas expects the ap_iface element to be see which isn't always the case and if that isn't true it will return false and causes the whole Properties.GetAll call to fail. The expected result is that the getter just returns an empty list if it can't determine the actual value. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1528173/+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 1671273] [NEW] PulseAudio requirement breaks Firefox on ALSA-only systems
Public bug reported: Upgrading Firefox to version 52 on an ALSA-only system breaks audio on all websites. PulseAudio has apparently become a hard requirement in the latest official build of Firefox, but since PulseAudio is (due to its design) not viable on some systems, this renders Firefox useless as a general- purpose browser. The upstream code still contains ALSA support. Please re-enable it on Ubuntu. I have read that Arch Linux has already done so. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Description changed: Upgrading Firefox to version 52 on an ALSA-only system breaks audio on all websites. PulseAudio has apparently become a hard requirement in the latest - version of Firefox, but since PulseAudio is (due to its design) not - viable on some systems, this renders Firefox useless as a general- + official build of Firefox, but since PulseAudio is (due to its design) + not viable on some systems, this renders Firefox useless as a general- purpose browser. The upstream code still contains ALSA support. Please re-enable it on Ubuntu. I have read that Arch Linux has already done so. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1671273 Title: PulseAudio requirement breaks Firefox on ALSA-only systems Status in firefox package in Ubuntu: New Bug description: Upgrading Firefox to version 52 on an ALSA-only system breaks audio on all websites. PulseAudio has apparently become a hard requirement in the latest official build of Firefox, but since PulseAudio is (due to its design) not viable on some systems, this renders Firefox useless as a general- purpose browser. The upstream code still contains ALSA support. Please re-enable it on Ubuntu. I have read that Arch Linux has already done so. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1671273/+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 1661098] Re: NetworkManager-openvpn mishandles the comp-lzo option, thereby breaking the ovpn config and causing AUTH_FAILED
Turns out is triggered by NetworkManager-openvpn stripping the "comp-lzo no" option from the imported .ovpn config file, misrepresenting a 3-value option as a simple check box, and giving the user no way to enter the correct setting. Checking the "Use LZO data compression" box in the Advanced... config dialog *might* work around the problem. This does not map to the intended "comp-lzo no" setting in openvpn, but if the server is pushing the setting to the client, it might work anyway. More details in the upstream bug report. ** Summary changed: - auth_failed when attempting openvpn via networkmanager + NetworkManager-openvpn mishandles the comp-lzo option, thereby breaking the ovpn config and causing AUTH_FAILED -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1661098 Title: NetworkManager-openvpn mishandles the comp-lzo option, thereby breaking the ovpn config and causing AUTH_FAILED Status in NetworkManager-OpenVPN: Confirmed Status in network-manager-openvpn package in Ubuntu: New Bug description: Attempting to establish an OpenVPN session via network-manager-openvpn fails with a password authentication error, even though the username and password I entered are correct. The following messages in syslog: Feb 1 12:44:54 computer nm-openvpn[21582]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Feb 1 12:44:54 computer nm-openvpn[21582]: UDPv4 link local: [undef] Feb 1 12:44:54 computer nm-openvpn[21582]: UDPv4 link remote: [AF_INET]209.148.113.36:1194 Feb 1 12:44:54 computer nm-openvpn[21582]: WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1557', remote='link-mtu 1558' Feb 1 12:44:54 computer nm-openvpn[21582]: WARNING: 'comp-lzo' is present in remote config but missing in local config, remote='comp-lzo' Feb 1 12:44:54 computer nm-openvpn[21582]: [OpenVPN Server] Peer Connection Initiated with [AF_INET]209.148.113.36:1194 Feb 1 12:44:56 computer nm-openvpn[21582]: AUTH: Received control message: AUTH_FAILED Feb 1 12:44:56 computer nm-openvpn[21582]: SIGUSR1[soft,auth-failure] received, process restarting Feb 1 12:44:56 computer NetworkManager[1322]: nm-openvpn[21574] Password verification failed I am able to establish the session by manually running openvpn from the command line, using the same username, password, and the ovpn file from which NetworkManager imported the setttings. I'm running Xubuntu 16.10 (yakkety). I did not have this problem in Ubuntu 16.04 (xenial). To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-openvpn/+bug/1661098/+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 1661098] Re: auth_failed when attempting openvpn via networkmanager
NetworkManager 1.2.4
NetworkManager-openvpn 1.2.6 and 1.2.8 (same problem in both)
$ nmcli --version
nmcli tool, version 1.2.4
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.10
Release:16.10
Codename: yakkety
$ openvpn --version
OpenVPN 2.3.11 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [PKCS11] [MH]
[IPv6] built on Jun 22 2016
library versions: OpenSSL 1.0.2g 1 Mar 2016, LZO 2.08
Originally developed by James Yonan
Copyright (C) 2002-2010 OpenVPN Technologies, Inc.
Compile time defines: enable_crypto=yes enable_crypto_ofb_cfb=yes
enable_debug=yes enable_def_auth=yes enable_dependency_tracking=no
enable_dlopen=unknown enable_dlopen_self=unknown
enable_dlopen_self_static=unknown enable_fast_install=yes enable_fragment=yes
enable_http_proxy=yes enable_iproute2=yes enable_libtool_lock=yes
enable_lzo=yes enable_lzo_stub=no enable_maintainer_mode=no
enable_management=yes enable_multi=yes enable_multihome=yes
enable_pam_dlopen=no enable_password_save=yes enable_pedantic=no enable_pf=yes
enable_pkcs11=yes enable_plugin_auth_pam=yes enable_plugin_down_root=yes
enable_plugins=yes enable_port_share=yes enable_selinux=no enable_server=yes
enable_shared=yes enable_shared_with_static_runtimes=no enable_silent_rules=no
enable_small=no enable_socks=yes enable_ssl=yes enable_static=yes
enable_strict=no enable_strict_options=no enable_systemd=yes
enable_win32_dll=yes enable_x509_alt_username=yes with_aix_soname=aix
with_crypto_library=openssl with_gnu_ld=yes wit
h_mem_check=no with_plugindir='${prefix}/lib/openvpn' with_sysroot=no
$ tail -f /var/log/syslog
Feb 2 23:49:01 computer NetworkManager[1329]: [1486108141.0702] audit:
op="connection-activate" uuid="----"
name="example" pid=3136 uid=1000 result="success"
Feb 2 23:49:01 computer NetworkManager[1329]: [1486108141.0741]
vpn-connection[0x557d295f73c0,----,"example",0]:
Started the VPN service, PID 5074
Feb 2 23:49:01 computer NetworkManager[1329]: [1486108141.0828]
vpn-connection[0x557d295f73c0,----,"example",0]:
Saw the service appear; activating connection
Feb 2 23:49:01 computer nm-openvpn[5081]: OpenVPN 2.3.11 x86_64-pc-linux-gnu
[SSL (OpenSSL)] [LZO] [EPOLL] [PKCS11] [MH] [IPv6] built on Jun 22 2016
Feb 2 23:49:01 computer nm-openvpn[5081]: library versions: OpenSSL 1.0.2g 1
Mar 2016, LZO 2.08
Feb 2 23:49:01 computer NetworkManager[1329]: nm-openvpn[5074]
openvpn[5081] started
Feb 2 23:49:01 computer NetworkManager[1329]: [1486108141.1490]
vpn-connection[0x557d295f73c0,----,"example",0]:
VPN plugin: state changed: starting (3)
Feb 2 23:49:01 computer NetworkManager[1329]: [1486108141.1491]
vpn-connection[0x557d295f73c0,----,"example",0]:
VPN connection: (ConnectInteractive) reply received
Feb 2 23:49:01 computer nm-openvpn[5081]: NOTE: the current --script-security
setting may allow this configuration to call user-defined scripts
Feb 2 23:49:01 computer nm-openvpn[5081]: Control Channel Authentication:
using '/home/ubuntu/vpn/ovpn.example.net/networkmanager/example.ovpn.tls-auth'
as a OpenVPN static key file
Feb 2 23:49:01 computer nm-openvpn[5081]: NOTE: chroot will be delayed because
of --client, --pull, or --up-delay
Feb 2 23:49:01 computer nm-openvpn[5081]: NOTE: UID/GID downgrade will be
delayed because of --client, --pull, or --up-delay
Feb 2 23:49:01 computer nm-openvpn[5081]: UDPv4 link local: [undef]
Feb 2 23:49:01 computer nm-openvpn[5081]: UDPv4 link remote:
[AF_INET]10.10.10.10:1194
Feb 2 23:49:01 computer nm-openvpn[5081]: WARNING: 'link-mtu' is used
inconsistently, local='link-mtu 1557', remote='link-mtu 1558'
Feb 2 23:49:01 computer nm-openvpn[5081]: WARNING: 'comp-lzo' is present in
remote config but missing in local config, remote='comp-lzo'
Feb 2 23:49:01 computer nm-openvpn[5081]: [OpenVPN Server] Peer Connection
Initiated with [AF_INET]10.10.10.10:1194
Feb 2 23:49:04 computer nm-openvpn[5081]: AUTH: Received control message:
AUTH_FAILED
Feb 2 23:49:04 computer nm-openvpn[5081]: SIGUSR1[soft,auth-failure] received,
process restarting
Feb 2 23:49:04 computer NetworkManager[1329]: nm-openvpn[5074]
Password verification failed
Feb 2 23:49:06 computer NetworkManager[1329]: [1486108146.0884]
vpn-connection[0x557d295f73c0,----,"example",0]:
VPN plugin: requested secrets; state connect (4)
Feb 2 23:49:06 computer nm-openvpn[5081]: NOTE: the current --script-security
setting may allow this configuration to call user-defined scripts
Feb 2 23:49:06 computer nm-openvpn[5081]: UDPv4 link local: [undef]
Feb 2 23:49:06 computer nm-openvpn[5081]: UDPv4 link remote:
[AF_INET]10.10.10.10:1194
Feb 2 23:49:06 computer nm-openvpn[5081]: WARNING: 'link-mtu' is used
inconsistently, local='link-mtu 1557', remote='link-mt
[Desktop-packages] [Bug 1661098] [NEW] auth_failed when attempting openvpn via networkmanager
Public bug reported: Attempting to establish an OpenVPN session via network-manager-openvpn fails with a password authentication error, even though the username and password I entered are correct. The following messages in syslog: Feb 1 12:44:54 computer nm-openvpn[21582]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Feb 1 12:44:54 computer nm-openvpn[21582]: UDPv4 link local: [undef] Feb 1 12:44:54 computer nm-openvpn[21582]: UDPv4 link remote: [AF_INET]209.148.113.36:1194 Feb 1 12:44:54 computer nm-openvpn[21582]: WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1557', remote='link-mtu 1558' Feb 1 12:44:54 computer nm-openvpn[21582]: WARNING: 'comp-lzo' is present in remote config but missing in local config, remote='comp-lzo' Feb 1 12:44:54 computer nm-openvpn[21582]: [OpenVPN Server] Peer Connection Initiated with [AF_INET]209.148.113.36:1194 Feb 1 12:44:56 computer nm-openvpn[21582]: AUTH: Received control message: AUTH_FAILED Feb 1 12:44:56 computer nm-openvpn[21582]: SIGUSR1[soft,auth-failure] received, process restarting Feb 1 12:44:56 computer NetworkManager[1322]: nm-openvpn[21574] Password verification failed I am able to establish the session by manually running openvpn from the command line, using the same username, password, and the ovpn file from which NetworkManager imported the setttings. I'm running Xubuntu 16.10 (yakkety). I did not have this problem in Ubuntu 16.04 (xenial). ** Affects: network-manager-openvpn (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1661098 Title: auth_failed when attempting openvpn via networkmanager Status in network-manager-openvpn package in Ubuntu: New Bug description: Attempting to establish an OpenVPN session via network-manager-openvpn fails with a password authentication error, even though the username and password I entered are correct. The following messages in syslog: Feb 1 12:44:54 computer nm-openvpn[21582]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Feb 1 12:44:54 computer nm-openvpn[21582]: UDPv4 link local: [undef] Feb 1 12:44:54 computer nm-openvpn[21582]: UDPv4 link remote: [AF_INET]209.148.113.36:1194 Feb 1 12:44:54 computer nm-openvpn[21582]: WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1557', remote='link-mtu 1558' Feb 1 12:44:54 computer nm-openvpn[21582]: WARNING: 'comp-lzo' is present in remote config but missing in local config, remote='comp-lzo' Feb 1 12:44:54 computer nm-openvpn[21582]: [OpenVPN Server] Peer Connection Initiated with [AF_INET]209.148.113.36:1194 Feb 1 12:44:56 computer nm-openvpn[21582]: AUTH: Received control message: AUTH_FAILED Feb 1 12:44:56 computer nm-openvpn[21582]: SIGUSR1[soft,auth-failure] received, process restarting Feb 1 12:44:56 computer NetworkManager[1322]: nm-openvpn[21574] Password verification failed I am able to establish the session by manually running openvpn from the command line, using the same username, password, and the ovpn file from which NetworkManager imported the setttings. I'm running Xubuntu 16.10 (yakkety). I did not have this problem in Ubuntu 16.04 (xenial). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1661098/+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 1576454] [NEW] Superfluous Xsession.d script: 60x11-common_localhost
Public bug reported: Both of these scripts do the same thing, and both are installed by x11-common: /etc/X11/Xsession.d/35x11-common_xhost-local /etc/X11/Xsession.d/60x11-common_localhost 35x11-common_xhost-local is present in debian, while 60x11-common_localhost is not. I suspect the latter should be removed. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Duplicate Xsession.d script: 60x11-common_localhost + Superfluous Xsession.d script: 60x11-common_localhost -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1576454 Title: Superfluous Xsession.d script: 60x11-common_localhost Status in xorg package in Ubuntu: New Bug description: Both of these scripts do the same thing, and both are installed by x11-common: /etc/X11/Xsession.d/35x11-common_xhost-local /etc/X11/Xsession.d/60x11-common_localhost 35x11-common_xhost-local is present in debian, while 60x11-common_localhost is not. I suspect the latter should be removed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1576454/+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 772709] Re: Network Manager Icon Is not changin when VPN is connected (nm-device-wired-secure icon is missing)
Also, this is a security problem. It robs the user of the ability to easily see that the VPN is (still) connected. If the VPN goes down, and the user doesn't happen to see the momentary pop-up message (or if that message has been accidentally or deliberately suppressed), the user will think his communications are encrypted when they are actually exposed. It can easily be exploited: 1. Distract the user or wait until he looks away from his screen. 2. Interfere with the internet connection for a few seconds, causing the user's VPN to fail. 3. Capture the user's packets. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/772709 Title: Network Manager Icon Is not changin when VPN is connected (nm-device- wired-secure icon is missing) Status in GNOME Icon Theme: New Status in tango-icon-theme: Confirmed Status in elementary-icon-theme package in Ubuntu: Confirmed Status in gnome-icon-theme package in Ubuntu: Confirmed Status in lubuntu-artwork package in Ubuntu: Fix Released Status in network-manager-applet package in Ubuntu: Confirmed Status in tango-icon-theme package in Ubuntu: Confirmed Bug description: Binary package hint: gnome-icon-theme Ater upgrading to 11.04 in gnome icon the (humanity and unity themes works fine) is see bad icons when connecting VPN and VPN is connected. Connected VPN icon is the same as original Network Manager. And connectin icon doen't show the Network manager icon only the flashing yellow lock (that must be over network manger icon) ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: gnome-icon-theme 2.31.0-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Fri Apr 29 01:05:10 2011 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-icon-theme UpgradeStatus: Upgraded to natty on 2011-04-28 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-icon-theme/+bug/772709/+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 772709] Re: Network Manager Icon Is not changin when VPN is connected (nm-device-wired-secure icon is missing)
I also created an upstream bug report against the Tango icon theme, mainly to get more eyes on the problem. Honestly, though, I don't expect every icon theme developer will want to to modify their software in order to compensate for something that was broken by an Ubuntu-specific patch. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/772709 Title: Network Manager Icon Is not changin when VPN is connected (nm-device- wired-secure icon is missing) Status in GNOME Icon Theme: New Status in tango-icon-theme: Confirmed Status in elementary-icon-theme package in Ubuntu: Confirmed Status in gnome-icon-theme package in Ubuntu: Confirmed Status in lubuntu-artwork package in Ubuntu: Fix Released Status in network-manager-applet package in Ubuntu: Confirmed Status in tango-icon-theme package in Ubuntu: Confirmed Bug description: Binary package hint: gnome-icon-theme Ater upgrading to 11.04 in gnome icon the (humanity and unity themes works fine) is see bad icons when connecting VPN and VPN is connected. Connected VPN icon is the same as original Network Manager. And connectin icon doen't show the Network manager icon only the flashing yellow lock (that must be over network manger icon) ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: gnome-icon-theme 2.31.0-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Fri Apr 29 01:05:10 2011 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-icon-theme UpgradeStatus: Upgraded to natty on 2011-04-28 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-icon-theme/+bug/772709/+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 772709] Re: Network Manager Icon Is not changin when VPN is connected (nm-device-wired-secure icon is missing)
Removing nm-applet-use-indicator.patch (and refreshing the patches that depend on it) fixes this in Xubuntu. In other words, that patch causes the regression. I'm removing the invalid status on network-manager-applet (Ubuntu), in hopes of getting someone to reevaluate this. If Ubuntu maintainers are going to patch in special functionality just for Unity, how about doing it without breaking things? (This is not the first time a patch intended to make a package use Unity's Application Indicators has broken the package for Xubuntu and other desktops. I really wish the people responsible would be more careful.) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/772709 Title: Network Manager Icon Is not changin when VPN is connected (nm-device- wired-secure icon is missing) Status in GNOME Icon Theme: New Status in tango-icon-theme: Confirmed Status in elementary-icon-theme package in Ubuntu: Confirmed Status in gnome-icon-theme package in Ubuntu: Confirmed Status in lubuntu-artwork package in Ubuntu: Fix Released Status in network-manager-applet package in Ubuntu: Confirmed Status in tango-icon-theme package in Ubuntu: Confirmed Bug description: Binary package hint: gnome-icon-theme Ater upgrading to 11.04 in gnome icon the (humanity and unity themes works fine) is see bad icons when connecting VPN and VPN is connected. Connected VPN icon is the same as original Network Manager. And connectin icon doen't show the Network manager icon only the flashing yellow lock (that must be over network manger icon) ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: gnome-icon-theme 2.31.0-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Fri Apr 29 01:05:10 2011 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-icon-theme UpgradeStatus: Upgraded to natty on 2011-04-28 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-icon-theme/+bug/772709/+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 772709] Re: Network Manager Icon Is not changin when VPN is connected (nm-device-wired-secure icon is missing)
** Changed in: network-manager-applet (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/772709 Title: Network Manager Icon Is not changin when VPN is connected (nm-device- wired-secure icon is missing) Status in GNOME Icon Theme: New Status in tango-icon-theme: Confirmed Status in elementary-icon-theme package in Ubuntu: Confirmed Status in gnome-icon-theme package in Ubuntu: Confirmed Status in lubuntu-artwork package in Ubuntu: Fix Released Status in network-manager-applet package in Ubuntu: Confirmed Status in tango-icon-theme package in Ubuntu: Confirmed Bug description: Binary package hint: gnome-icon-theme Ater upgrading to 11.04 in gnome icon the (humanity and unity themes works fine) is see bad icons when connecting VPN and VPN is connected. Connected VPN icon is the same as original Network Manager. And connectin icon doen't show the Network manager icon only the flashing yellow lock (that must be over network manger icon) ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: gnome-icon-theme 2.31.0-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Fri Apr 29 01:05:10 2011 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-icon-theme UpgradeStatus: Upgraded to natty on 2011-04-28 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-icon-theme/+bug/772709/+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 772709] Re: Network Manager Icon Is not changin when VPN is connected (nm-device-wired-secure icon is missing)
** Bug watch added: freedesktop.org Bugzilla #91887 https://bugs.freedesktop.org/show_bug.cgi?id=91887 ** Also affects: tango-icon-theme via https://bugs.freedesktop.org/show_bug.cgi?id=91887 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/772709 Title: Network Manager Icon Is not changin when VPN is connected (nm-device- wired-secure icon is missing) Status in GNOME Icon Theme: New Status in tango-icon-theme: Unknown Status in elementary-icon-theme package in Ubuntu: Confirmed Status in gnome-icon-theme package in Ubuntu: Confirmed Status in lubuntu-artwork package in Ubuntu: Fix Released Status in network-manager-applet package in Ubuntu: Invalid Status in tango-icon-theme package in Ubuntu: Confirmed Bug description: Binary package hint: gnome-icon-theme Ater upgrading to 11.04 in gnome icon the (humanity and unity themes works fine) is see bad icons when connecting VPN and VPN is connected. Connected VPN icon is the same as original Network Manager. And connectin icon doen't show the Network manager icon only the flashing yellow lock (that must be over network manger icon) ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: gnome-icon-theme 2.31.0-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Fri Apr 29 01:05:10 2011 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-icon-theme UpgradeStatus: Upgraded to natty on 2011-04-28 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-icon-theme/+bug/772709/+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 1186801] Re: liferea is completely invisible when running on xubuntu
This regression is still present in vivid. ** Tags added: vivid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to liferea in Ubuntu. https://bugs.launchpad.net/bugs/1186801 Title: liferea is completely invisible when running on xubuntu Status in liferea package in Ubuntu: Triaged Bug description: The patch recently applied to liferea for Unity messaging menu support (port-to-messaging-menu.patch) broke liferea on xubuntu. It eliminated liferea's system tray icon, thereby making liferea inaccessible in xfce when running minimized or started in a minimized state (as is the case for most people who let it auto-start at login time). Here is the changelog entry corresponding to the offending patch: > liferea (1.8.10-0ubuntu2) raring; urgency=low > > * Port to messaging-menu. (LP: #1040259) > -- Dmitrijs Ledkovs Mon, 25 Mar 2013 16:55:30 + To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/liferea/+bug/1186801/+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 1440440] Re: gstreamer 0.10 apps prematurely stop parsing some flac files
I discovered the problem with Exaile, Totem, and Sound Converter. I verified it and narrowed it down with gst-launch. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-good0.10 in Ubuntu. https://bugs.launchpad.net/bugs/1440440 Title: gstreamer 0.10 apps prematurely stop parsing some flac files Status in gst-plugins-good0.10 package in Ubuntu: Confirmed Bug description: Gstreamer 0.10 stops processing certain flac files before their end is reached. When it happens, no error condition is reported. It fails silently, as if the file was truncated. This affects all applications that use gstreamer0.10-plugins-good, including clementine, exaile, soundconverter, and many others. Upstream git branch 0.10 has had patches since 2012 that seem to fix the problem, but they have not yet made it into an official 0.10.x release. The relevant changesets are: 5881603 flacparse: avoid indefinite extended search for frame end if possible 440d703 flacparse: perform additional frame crc check if applicable 32cddf6 flacparse: avoid some more frame misparsing by additional header sanity check The fixes are present in gstreamer 1.0, but applications that still depend on 0.10 (either directly or through python-gst) remain broken. This seems like a good reason to apply the fixes to 0.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good0.10/+bug/1440440/+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 1440440] Re: gstreamer 0.10 apps prematurely stop parsing some flac files
All I have is a couple of files that trigger the bug. Unfortunately, I don't have the rights to post them publicly, and I haven't found a way to extract a useful segment from them without remuxing (and hiding the problem). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-good0.10 in Ubuntu. https://bugs.launchpad.net/bugs/1440440 Title: gstreamer 0.10 apps prematurely stop parsing some flac files Status in gst-plugins-good0.10 package in Ubuntu: Confirmed Bug description: Gstreamer 0.10 stops processing certain flac files before their end is reached. When it happens, no error condition is reported. It fails silently, as if the file was truncated. This affects all applications that use gstreamer0.10-plugins-good, including clementine, exaile, soundconverter, and many others. Upstream git branch 0.10 has had patches since 2012 that seem to fix the problem, but they have not yet made it into an official 0.10.x release. The relevant changesets are: 5881603 flacparse: avoid indefinite extended search for frame end if possible 440d703 flacparse: perform additional frame crc check if applicable 32cddf6 flacparse: avoid some more frame misparsing by additional header sanity check The fixes are present in gstreamer 1.0, but applications that still depend on 0.10 (either directly or through python-gst) remain broken. This seems like a good reason to apply the fixes to 0.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good0.10/+bug/1440440/+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 1440440] Re: gstreamer 0.10 apps prematurely stop parsing some flac files
I have attached 3 upstream patches to fix the premature eos on some flac files: 0010-flacparse-avoid-indefinite-search-for-frame-end.patch 0011-flacparse-additional-frame-crc-check.patch 0012-flacparse-additional-header-sanity-check.patch These are suitable for adding to the debian/patches directory (and series file) of gst-plugins-good0.10-0.10.31. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-good0.10 in Ubuntu. https://bugs.launchpad.net/bugs/1440440 Title: gstreamer 0.10 apps prematurely stop parsing some flac files Status in gst-plugins-good0.10 package in Ubuntu: New Bug description: Gstreamer 0.10 stops processing certain flac files before their end is reached. When it happens, no error condition is reported. It fails silently, as if the file was truncated. This affects all applications that use gstreamer0.10-plugins-good, including clementine, exaile, soundconverter, and many others. Upstream git branch 0.10 has had patches since 2012 that seem to fix the problem, but they have not yet made it into an official 0.10.x release. The relevant changesets are: 5881603 flacparse: avoid indefinite extended search for frame end if possible 440d703 flacparse: perform additional frame crc check if applicable 32cddf6 flacparse: avoid some more frame misparsing by additional header sanity check The fixes are present in gstreamer 1.0, but applications that still depend on 0.10 (either directly or through python-gst) remain broken. This seems like a good reason to apply the fixes to 0.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good0.10/+bug/1440440/+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 1440440] Re: gstreamer 0.10 apps prematurely stop parsing some flac files
** Patch added: "0010-flacparse-avoid-indefinite-search-for-frame-end.patch" https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good0.10/+bug/1440440/+attachment/4366258/+files/0010-flacparse-avoid-indefinite-search-for-frame-end.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-good0.10 in Ubuntu. https://bugs.launchpad.net/bugs/1440440 Title: gstreamer 0.10 apps prematurely stop parsing some flac files Status in gst-plugins-good0.10 package in Ubuntu: New Bug description: Gstreamer 0.10 stops processing certain flac files before their end is reached. When it happens, no error condition is reported. It fails silently, as if the file was truncated. This affects all applications that use gstreamer0.10-plugins-good, including clementine, exaile, soundconverter, and many others. Upstream git branch 0.10 has had patches since 2012 that seem to fix the problem, but they have not yet made it into an official 0.10.x release. The relevant changesets are: 5881603 flacparse: avoid indefinite extended search for frame end if possible 440d703 flacparse: perform additional frame crc check if applicable 32cddf6 flacparse: avoid some more frame misparsing by additional header sanity check The fixes are present in gstreamer 1.0, but applications that still depend on 0.10 (either directly or through python-gst) remain broken. This seems like a good reason to apply the fixes to 0.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good0.10/+bug/1440440/+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 1440440] [NEW] gstreamer 0.10 apps prematurely stop parsing some flac files
Public bug reported: Gstreamer 0.10 stops processing certain flac files before their end is reached. When it happens, no error condition is reported. It fails silently, as if the file was truncated. This affects all applications that use gstreamer0.10-plugins-good, including clementine, exaile, soundconverter, and many others. Upstream git branch 0.10 has had patches since 2012 that seem to fix the problem, but they have not yet made it into an official 0.10.x release. The relevant changesets are: 5881603 flacparse: avoid indefinite extended search for frame end if possible 440d703 flacparse: perform additional frame crc check if applicable 32cddf6 flacparse: avoid some more frame misparsing by additional header sanity check The fixes are present in gstreamer 1.0, but applications that still depend on 0.10 (either directly or through python-gst) remain broken. This seems like a good reason to apply the fixes to 0.10. ** Affects: gst-plugins-good0.10 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-good0.10 in Ubuntu. https://bugs.launchpad.net/bugs/1440440 Title: gstreamer 0.10 apps prematurely stop parsing some flac files Status in gst-plugins-good0.10 package in Ubuntu: New Bug description: Gstreamer 0.10 stops processing certain flac files before their end is reached. When it happens, no error condition is reported. It fails silently, as if the file was truncated. This affects all applications that use gstreamer0.10-plugins-good, including clementine, exaile, soundconverter, and many others. Upstream git branch 0.10 has had patches since 2012 that seem to fix the problem, but they have not yet made it into an official 0.10.x release. The relevant changesets are: 5881603 flacparse: avoid indefinite extended search for frame end if possible 440d703 flacparse: perform additional frame crc check if applicable 32cddf6 flacparse: avoid some more frame misparsing by additional header sanity check The fixes are present in gstreamer 1.0, but applications that still depend on 0.10 (either directly or through python-gst) remain broken. This seems like a good reason to apply the fixes to 0.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good0.10/+bug/1440440/+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 1440440] Re: gstreamer 0.10 apps prematurely stop parsing some flac files
** Patch added: "0012-flacparse-additional-header-sanity-check.patch" https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good0.10/+bug/1440440/+attachment/4366260/+files/0012-flacparse-additional-header-sanity-check.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-good0.10 in Ubuntu. https://bugs.launchpad.net/bugs/1440440 Title: gstreamer 0.10 apps prematurely stop parsing some flac files Status in gst-plugins-good0.10 package in Ubuntu: New Bug description: Gstreamer 0.10 stops processing certain flac files before their end is reached. When it happens, no error condition is reported. It fails silently, as if the file was truncated. This affects all applications that use gstreamer0.10-plugins-good, including clementine, exaile, soundconverter, and many others. Upstream git branch 0.10 has had patches since 2012 that seem to fix the problem, but they have not yet made it into an official 0.10.x release. The relevant changesets are: 5881603 flacparse: avoid indefinite extended search for frame end if possible 440d703 flacparse: perform additional frame crc check if applicable 32cddf6 flacparse: avoid some more frame misparsing by additional header sanity check The fixes are present in gstreamer 1.0, but applications that still depend on 0.10 (either directly or through python-gst) remain broken. This seems like a good reason to apply the fixes to 0.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good0.10/+bug/1440440/+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 1440440] Re: gstreamer 0.10 apps prematurely stop parsing some flac files
** Patch added: "0011-flacparse-additional-frame-crc-check.patch" https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good0.10/+bug/1440440/+attachment/4366259/+files/0011-flacparse-additional-frame-crc-check.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-good0.10 in Ubuntu. https://bugs.launchpad.net/bugs/1440440 Title: gstreamer 0.10 apps prematurely stop parsing some flac files Status in gst-plugins-good0.10 package in Ubuntu: New Bug description: Gstreamer 0.10 stops processing certain flac files before their end is reached. When it happens, no error condition is reported. It fails silently, as if the file was truncated. This affects all applications that use gstreamer0.10-plugins-good, including clementine, exaile, soundconverter, and many others. Upstream git branch 0.10 has had patches since 2012 that seem to fix the problem, but they have not yet made it into an official 0.10.x release. The relevant changesets are: 5881603 flacparse: avoid indefinite extended search for frame end if possible 440d703 flacparse: perform additional frame crc check if applicable 32cddf6 flacparse: avoid some more frame misparsing by additional header sanity check The fixes are present in gstreamer 1.0, but applications that still depend on 0.10 (either directly or through python-gst) remain broken. This seems like a good reason to apply the fixes to 0.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good0.10/+bug/1440440/+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 1126185] Re: baobag count up or show size badly
When run on the cifs server, du -sh also reports 55G. When run on the client machine, it reports 170G, unless I use the --apparent-size option, which makes it report the correct value. It seems that baobab needs to be modified to act like du --apparent-size when it operates on cifs-mounted directories. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to baobab in Ubuntu. https://bugs.launchpad.net/bugs/1126185 Title: baobag count up or show size badly Status in baobab package in Ubuntu: Confirmed Bug description: i have a problem with baobad when baobab do analys show that /home/administrator uses 88GB but when show directories below it shows size about 1-2GB WHERE IS THE REST 86 GB !!! see enclosure ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: baobab 3.4.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-36.57-generic 3.2.35 Uname: Linux 3.2.0-36-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 Date: Fri Feb 15 13:45:37 2013 InstallationMedia: MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=cs_CZ.UTF-8 SHELL=/bin/bash SourcePackage: baobab UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/baobab/+bug/1126185/+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 1126185] Re: baobag count up or show size badly
I have this problem on ubuntu 14.04 LTS with baobab 3.8.2. Baobab is telling me that a cifs-mounted directory is 182 GiB, while Thunar reports the correct size of 55 GiB. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to baobab in Ubuntu. https://bugs.launchpad.net/bugs/1126185 Title: baobag count up or show size badly Status in baobab package in Ubuntu: Confirmed Bug description: i have a problem with baobad when baobab do analys show that /home/administrator uses 88GB but when show directories below it shows size about 1-2GB WHERE IS THE REST 86 GB !!! see enclosure ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: baobab 3.4.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-36.57-generic 3.2.35 Uname: Linux 3.2.0-36-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 Date: Fri Feb 15 13:45:37 2013 InstallationMedia: MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=cs_CZ.UTF-8 SHELL=/bin/bash SourcePackage: baobab UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/baobab/+bug/1126185/+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 1236619] Re: gvfs smb / cifs file copy performance is terribly slow
JensK, assuming that your manual command line mount uses mount.cifs, that is not a twist. It's the same thing that the rest of us are seeing when we don't use gvfs. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1236619 Title: gvfs smb / cifs file copy performance is terribly slow Status in gvfs package in Ubuntu: Confirmed Bug description: Copying moderate-size files to a samba share using gvfs is ridiculously slow compared to doing the same via mount.cifs. For example: $ ls -sh testfile 1.2G testfile $ time cp testfile ~/mnt/share-gvfs/ real 2m37.053s user 0m0.056s sys 0m5.120s $ time cp testfile ~/mnt/share/ real 0m26.134s user 0m0.004s sys 0m1.724s I'm running Xubuntu 13.04 (raring) amd64, gvfs 1.16.1-0ubuntu1.1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1236619/+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 608537] Re: Rhythmbox not support cue sheet for lossless audio disk image (external and embedded) and cue sheet for tracks
Found another player, thanks, bye. -- 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/608537 Title: Rhythmbox not support cue sheet for lossless audio disk image (external and embedded) and cue sheet for tracks Status in The GStreamer Multimedia Framework: Confirmed Status in The Rhythmbox Music Management Application: New Status in “rhythmbox” package in Ubuntu: Triaged Status in “rhythmbox” package in Debian: Confirmed Bug description: Rhythmbox not support cue sheet for lossless audio disk image (external and embedded) and cue sheet for tracks. It's a bit strange. There is a lot of peoples, who need support of cue sheet. There is a few open source players for Linux with proper cue sheet support (Audacious, DeaDBeeF, qmmp) - Rhythmbox and GStreamer developers can use code from this player for implement cue sheet support in Rhythmbox. Users ask Rhythmbox developers about that last five years (looks like the first time it happened here: http://www.mail-archive.com/rhythmbox-devel@gnome.org/msg02395.html ), but support of cue sheet still not implement in Rhythmbox. Even Amarok have basic cue sheet support since version 2.3. So, maybe it's a time for cooperate Rhythmbox and GStreamer developers and add cue sheet support to Rhythmbox? To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer/+bug/608537/+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 30378] Re: Joystick activity does not stop the screensaver
I wrote a program called joystickwake to work around this problem until display servers learn that joysticks are input devices. If you happen to be running Ubuntu Trusty, you can install it from my PPA: https://launchpad.net/~foresto/+archive/ubuntu/toys -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xscreensaver in Ubuntu. https://bugs.launchpad.net/bugs/30378 Title: Joystick activity does not stop the screensaver Status in GNOME Screensaver: Invalid Status in “gnome-screensaver” package in Ubuntu: Confirmed Status in “xscreensaver” package in Ubuntu: Confirmed Bug description: While playing games entirely with the joystick the screensaver is activated every few minutes. Input activity from a joystick should have the same results as activity from the mouse or keyboard. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/30378/+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 1271591] Re: upstart job race prevents gnome-keyring from being ssh agent
Based on the behavior I've observed, I think it's possible that there are two bugs in play here, and fixing one has revealed the other one. I'm running Xubuntu 14.04. Before this update, starting my terminal from the applications menu yielded a shell with SSH_AUTH_SOCK correctly pointing at gnome-keyring, while starting my terminal from a folder in Thunar file manager yielded a shell with SSH_AUTH_SOCK incorrectly pointing at an ssh-agent instance. The latter didn't work because I only have my ssh key loaded into gnome-keyring. After the update, starting my terminal from the applications menu yields a shell with SSH_AUTH_SOCK correctly pointing at gnome-keyring, while starting my terminal from a folder in Thunar file manager yields a shell with SSH_AUTH_SOCK not set at all. I haven't read the recently released patch yet, so I don't know what it's supposed to do, but it sure looks like it got rid of the ssh-agent instance that I thought I had disabled long ago (great!). That still leaves the problem of why SSH_AUTH_SOCK isn't propagating into my terminal when launched from my file manager. -- 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/1271591 Title: upstart job race prevents gnome-keyring from being ssh agent Status in “gnome-keyring” package in Ubuntu: Fix Released Status in “gnome-keyring” source package in Trusty: Fix Released Bug description: I expect gnome-keyring to be the ssh authentication agent when I am logged in to a graphical session. Because of what I suspect is a race in upstart jobs, I believe SSH_AUTH_SOCK is being overwritten after gnome-keyring starts. Perhaps the gnome-session job needs to make sure the ssh-agent job is finished? [testcase] 1) Perform desktop login 2) [ "$GNOME_KEYRING_CONTROL/ssh" = "$SSH_AUTH_SOCK" ] && echo Good || Fail Expected output: Good ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-session 3.9.90-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 Uname: Linux 3.13.0-5-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jan 22 10:25:59 2014 InstallationDate: Installed on 2013-11-26 (56 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) PackageArchitecture: all SourcePackage: gnome-session UpgradeStatus: Upgraded to trusty on 2014-01-17 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1271591/+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 1309605] Re: OSD (skip, pause) take full window (and fullscreen) height
I'm running Xubuntu 14.04, and the problem definitely exists here. Yes, the icon backgrounds are technically transparent, in that the underlying video is visible outside the icons' rounded corners, but the icons themselves are opaque and cover almost the entire video frame. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1309605 Title: OSD (skip, pause) take full window (and fullscreen) height Status in Totem Movie Player: Expired Status in “totem” package in Ubuntu: Confirmed Bug description: The OSD icons for forward/backward skip and pause have the wrong heigt. They take the full (sometimes even more) height on the player window and also full height in fullscreen mode. This appeared after the upgrade to trusty (totem 3.10.1) To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1309605/+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 1286836] Re: package libpostproc52 6:0.8.10-0ubuntu0.13.10.1 failed to install/upgrade: libpostproc52:amd64 6:0.git20120821-4 (Multi-Arch: no) is not co-installable with libpos
For the record: This happened to me during a distribution upgrade from 13.10 (saucy) to 14.04 (trusty). When it happened, the release upgrade tool interrupted itself with a dialog box containing this alarming and not very helpful message: Could not install the upgrades The upgrade has aborted. Your system could be in an unusable state. A recovery will run now (dpkg --configure -a). This dialog box was modal, preventing me from scrolling or copying the text in the Terminal widget to see what really happened. The text visible in the Terminal widget did not show up in any of the /var/log /dist-upgrade/* logs, but it was clearly a python exception and stack trace. Upon closing the dialog box, the upgrade continued, contrary to what the alarming message stated. (I guess the message was referring to one particular package, not the overall release upgrade, but most end users wouldn't know that, and even if they did the message didn't state which package.) As the upgrade continued, I was unable to copy & paste the stack trace before it was pushed out of the Terminal widget's rather short scroll buffer. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libav in Ubuntu. https://bugs.launchpad.net/bugs/1286836 Title: package libpostproc52 6:0.8.10-0ubuntu0.13.10.1 failed to install/upgrade: libpostproc52:amd64 6:0.git20120821-4 (Multi-Arch: no) is not co-installable with libpostproc52 which has multiple installed instances Status in “libav” package in Ubuntu: Confirmed Status in “libpostproc” package in Ubuntu: Confirmed Bug description: - ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libpostproc52 6:0.8.10-0ubuntu0.13.10.1 ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5 Uname: Linux 3.13.0-14-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 Date: Mon Mar 3 00:57:47 2014 Dependencies: gcc-4.9-base 4.9-20140222-0ubuntu1 libavutil51 6:0.8.10-0ubuntu0.13.10.1 [origin: unknown] libc6 2.19-0ubuntu2 libgcc1 1:4.9-20140222-0ubuntu1 multiarch-support 2.19-0ubuntu2 ErrorMessage: libpostproc52:amd64 6:0.git20120821-4 (Multi-Arch: no) is not co-installable with libpostproc52 which has multiple installed instances InstallationDate: Installed on 2013-12-12 (79 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: libav Title: package libpostproc52 6:0.8.10-0ubuntu0.13.10.1 failed to install/upgrade: libpostproc52:amd64 6:0.git20120821-4 (Multi-Arch: no) is not co-installable with libpostproc52 which has multiple installed instances UpgradeStatus: Upgraded to trusty on 2014-03-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1286836/+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 1247719] Re: crackling, popping, clicking in playback to audigy2 surround51 device
** Tags added: regression-release saucy
** Tags added: trusty
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1247719
Title:
crackling, popping, clicking in playback to audigy2 surround51 device
Status in “alsa-driver” package in Ubuntu:
New
Bug description:
After upgrading from Xubuntu 13.04 to 13.10, I hear lots of popping
(aka crackle, click noises) during playback to my Audigy2 surround51
device. This was never a problem before the upgrade. The noises do
not show up if I use the card's default, front, or rear devices
instead, but those leave me without surround sound, so they're no good
for movie playback.
The same problem shows up on the surround40 device. I haven't tried
the other surround* devices.
I can reproduce problem in Totem or gst-launch playbin with an .asoundrc
containing this:
pcm.!default {
type plug
slave.pcm "surround51"
}
I can reproduce problem in Exaile with the custom sink pipeline set to
"alsasink device=surround51" and no .asoundrc.
I'm running the amd64 build of Xubuntu.
My Audigy2 has the first alsa sound card slot, making it my default
sound card.
I am not using PulseAudio.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1247719/+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 1186801] Re: liferea is completely invisible when running on xubuntu
Still broken on 14.04 three months after release. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to liferea in Ubuntu. https://bugs.launchpad.net/bugs/1186801 Title: liferea is completely invisible when running on xubuntu Status in “liferea” package in Ubuntu: Triaged Bug description: The patch recently applied to liferea for Unity messaging menu support (port-to-messaging-menu.patch) broke liferea on xubuntu. It eliminated liferea's system tray icon, thereby making liferea inaccessible in xfce when running minimized or started in a minimized state (as is the case for most people who let it auto-start at login time). Here is the changelog entry corresponding to the offending patch: > liferea (1.8.10-0ubuntu2) raring; urgency=low > > * Port to messaging-menu. (LP: #1040259) > -- Dmitrijs Ledkovs Mon, 25 Mar 2013 16:55:30 + To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/liferea/+bug/1186801/+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 1286836] Re: package libpostproc52 6:0.8.10-0ubuntu0.13.10.1 failed to install/upgrade: libpostproc52:amd64 6:0.git20120821-4 (Multi-Arch: no) is not co-installable with libpos
Here's a cleaner variation of the workaround: sudo dpkg --purge --force-depends libpostproc52 sudo apt-get install libpostproc52 sudo apt-mark auto libpostproc52 The first line purges the package without removing any of the packages that depend on it. (This is fine, since we're going to reinstall the dependency immediately.) The second line reinstalls the package. The third line marks the package as automatically-installed (as it is in a stock ubuntu system), so the system knows to treat it as a dependency rather than something the user manually installed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libav in Ubuntu. https://bugs.launchpad.net/bugs/1286836 Title: package libpostproc52 6:0.8.10-0ubuntu0.13.10.1 failed to install/upgrade: libpostproc52:amd64 6:0.git20120821-4 (Multi-Arch: no) is not co-installable with libpostproc52 which has multiple installed instances Status in “libav” package in Ubuntu: Confirmed Status in “libpostproc” package in Ubuntu: Confirmed Bug description: - ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libpostproc52 6:0.8.10-0ubuntu0.13.10.1 ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5 Uname: Linux 3.13.0-14-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 Date: Mon Mar 3 00:57:47 2014 Dependencies: gcc-4.9-base 4.9-20140222-0ubuntu1 libavutil51 6:0.8.10-0ubuntu0.13.10.1 [origin: unknown] libc6 2.19-0ubuntu2 libgcc1 1:4.9-20140222-0ubuntu1 multiarch-support 2.19-0ubuntu2 ErrorMessage: libpostproc52:amd64 6:0.git20120821-4 (Multi-Arch: no) is not co-installable with libpostproc52 which has multiple installed instances InstallationDate: Installed on 2013-12-12 (79 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: libav Title: package libpostproc52 6:0.8.10-0ubuntu0.13.10.1 failed to install/upgrade: libpostproc52:amd64 6:0.git20120821-4 (Multi-Arch: no) is not co-installable with libpostproc52 which has multiple installed instances UpgradeStatus: Upgraded to trusty on 2014-03-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1286836/+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 1236619] Re: gvfs smb / cifs file copy performance is terribly slow
** Summary changed: - gvfs smb/cifs file copy performance is terribly slow + gvfs smb / cifs file copy performance is terribly slow -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1236619 Title: gvfs smb / cifs file copy performance is terribly slow Status in “gvfs” package in Ubuntu: Confirmed Bug description: Copying moderate-size files to a samba share using gvfs is ridiculously slow compared to doing the same via mount.cifs. For example: $ ls -sh testfile 1.2G testfile $ time cp testfile ~/mnt/share-gvfs/ real 2m37.053s user 0m0.056s sys 0m5.120s $ time cp testfile ~/mnt/share/ real 0m26.134s user 0m0.004s sys 0m1.724s I'm running Xubuntu 13.04 (raring) amd64, gvfs 1.16.1-0ubuntu1.1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1236619/+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 1247719] Re: crackling, popping, clicking in playback to audigy2 surround51 device
> # Enable basic debugging, do jiffies check and enable one shot dump of last
> 10 ring buffer positions
> # Usefull, when the position is broken only after some of time (to reduce
> ksyslog messages)
> echo 101 > /proc/asound/card0/pcm0p/xrun_debug
That doesn't seem to do anything.
Just to be clear, the crackling noises start immediately when playback begins;
it doesn't take time before they start.
> most of 5.1 audio are 48000Hz
> but you try to use it as default device to play audio at any rate
Like I said before, the problem occurs even with a 48000Hz PCM wav
file.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1247719
Title:
crackling, popping, clicking in playback to audigy2 surround51 device
Status in “alsa-driver” package in Ubuntu:
New
Bug description:
After upgrading from Xubuntu 13.04 to 13.10, I hear lots of popping
(aka crackle, click noises) during playback to my Audigy2 surround51
device. This was never a problem before the upgrade. The noises do
not show up if I use the card's default, front, or rear devices
instead, but those leave me without surround sound, so they're no good
for movie playback.
The same problem shows up on the surround40 device. I haven't tried
the other surround* devices.
I can reproduce problem in Totem or gst-launch playbin with an .asoundrc
containing this:
pcm.!default {
type plug
slave.pcm "surround51"
}
I can reproduce problem in Exaile with the custom sink pipeline set to
"alsasink device=surround51" and no .asoundrc.
I'm running the amd64 build of Xubuntu.
My Audigy2 has the first alsa sound card slot, making it my default
sound card.
I am not using PulseAudio.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1247719/+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 1247719] Re: crackling, popping, clicking in playback to audigy2 surround51 device
> did you find any message such as "PCM: hw_ptr skipping!" ?
No.
> did period update occur at period boundary ?
I don't know how to tell.
> are there any message by totem or gst ?
No messages from gst-launch.
These messages were produced by Totem, but they don't seem relevant:
(totem:5747): GStreamer-CRITICAL **: gst_mini_object_copy: assertion
'mini_object != NULL' failed
(totem:5747): GStreamer-CRITICAL **: gst_caps_get_size: assertion 'GST_IS_CAPS
(caps)' failed
(totem:5747): GStreamer-CRITICAL **: gst_mini_object_unref: assertion
'mini_object != NULL' failed
** (totem:5747): CRITICAL **: gst_pad_set_caps: assertion 'caps != NULL &&
gst_caps_is_fixed (caps)' failed
(totem:5747): Gtk-WARNING **: Calling Inhibit failed:
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
org.gnome.SessionManager was not provided by any .service files
(totem:5747): Gtk-WARNING **: Calling Inhibit failed:
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
org.gnome.SessionManager was not provided by any .service files
(totem:5747): Gtk-WARNING **: Calling Inhibit failed:
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
org.gnome.SessionManager was not provided by any .service files
(totem:5747): Gtk-WARNING **: Calling Inhibit failed:
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
org.gnome.SessionManager was not provided by any .service files
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1247719
Title:
crackling, popping, clicking in playback to audigy2 surround51 device
Status in “alsa-driver” package in Ubuntu:
New
Bug description:
After upgrading from Xubuntu 13.04 to 13.10, I hear lots of popping
(aka crackle, click noises) during playback to my Audigy2 surround51
device. This was never a problem before the upgrade. The noises do
not show up if I use the card's default, front, or rear devices
instead, but those leave me without surround sound, so they're no good
for movie playback.
The same problem shows up on the surround40 device. I haven't tried
the other surround* devices.
I can reproduce problem in Totem or gst-launch playbin with an .asoundrc
containing this:
pcm.!default {
type plug
slave.pcm "surround51"
}
I can reproduce problem in Exaile with the custom sink pipeline set to
"alsasink device=surround51" and no .asoundrc.
I'm running the amd64 build of Xubuntu.
My Audigy2 has the first alsa sound card slot, making it my default
sound card.
I am not using PulseAudio.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1247719/+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 1247719] Re: crackling, popping, clicking in playback to audigy2 surround51 device
> do jiffies check and enable one shot dump of last 10 ring buffer
positions
I don't know what a jiffies check is. I don't know how to dump ring
buffer positions.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1247719
Title:
crackling, popping, clicking in playback to audigy2 surround51 device
Status in “alsa-driver” package in Ubuntu:
New
Bug description:
After upgrading from Xubuntu 13.04 to 13.10, I hear lots of popping
(aka crackle, click noises) during playback to my Audigy2 surround51
device. This was never a problem before the upgrade. The noises do
not show up if I use the card's default, front, or rear devices
instead, but those leave me without surround sound, so they're no good
for movie playback.
The same problem shows up on the surround40 device. I haven't tried
the other surround* devices.
I can reproduce problem in Totem or gst-launch playbin with an .asoundrc
containing this:
pcm.!default {
type plug
slave.pcm "surround51"
}
I can reproduce problem in Exaile with the custom sink pipeline set to
"alsasink device=surround51" and no .asoundrc.
I'm running the amd64 build of Xubuntu.
My Audigy2 has the first alsa sound card slot, making it my default
sound card.
I am not using PulseAudio.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1247719/+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 573417] Re: disk utility should have udf as an option to format as
It would also be useful to those of us who want to use UDF on our flash drives / cards. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/573417 Title: disk utility should have udf as an option to format as Status in GNOME Disks: Unknown Status in “gnome-disk-utility” package in Ubuntu: Triaged Bug description: Binary package hint: gnome-disk-utility The choices of filesystems to format a disk with do not include the udf filesystem. This should be added. In order to properly use a dvd+rw, you need to format a udf filesystem on it, but there is no simple way to do this presently. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-disk-utility/+bug/573417/+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 1247719] Re: crackling, popping, clicking in playback to audigy2 surround51 device
$ ./chmap -D pulse query
ALSA lib pulse.c:243:(pulse_connect) PulseAudio: Unable to connect: Connection
refused
Cannot open PCM stream pulse for PLAYBACK
I guess this result is because this system is not running Pulse.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1247719
Title:
crackling, popping, clicking in playback to audigy2 surround51 device
Status in “alsa-driver” package in Ubuntu:
New
Bug description:
After upgrading from Xubuntu 13.04 to 13.10, I hear lots of popping
(aka crackle, click noises) during playback to my Audigy2 surround51
device. This was never a problem before the upgrade. The noises do
not show up if I use the card's default, front, or rear devices
instead, but those leave me without surround sound, so they're no good
for movie playback.
The same problem shows up on the surround40 device. I haven't tried
the other surround* devices.
I can reproduce problem in Totem or gst-launch playbin with an .asoundrc
containing this:
pcm.!default {
type plug
slave.pcm "surround51"
}
I can reproduce problem in Exaile with the custom sink pipeline set to
"alsasink device=surround51" and no .asoundrc.
I'm running the amd64 build of Xubuntu.
My Audigy2 has the first alsa sound card slot, making it my default
sound card.
I am not using PulseAudio.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1247719/+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 1247719] Re: crackling, popping, clicking in playback to audigy2 surround51 device
Setting xrun_debug to 29 and reproducing the problem yielded a ton of
debug hwptr_update and period_update messages in syslog. I'll attach
the messages that were logged when playing a few seconds of my 48000 Hz
test file.
** Attachment added: "xrun_debug messages from syslog"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1247719/+attachment/3910842/+files/syslog.hwptr.gz
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1247719
Title:
crackling, popping, clicking in playback to audigy2 surround51 device
Status in “alsa-driver” package in Ubuntu:
New
Bug description:
After upgrading from Xubuntu 13.04 to 13.10, I hear lots of popping
(aka crackle, click noises) during playback to my Audigy2 surround51
device. This was never a problem before the upgrade. The noises do
not show up if I use the card's default, front, or rear devices
instead, but those leave me without surround sound, so they're no good
for movie playback.
The same problem shows up on the surround40 device. I haven't tried
the other surround* devices.
I can reproduce problem in Totem or gst-launch playbin with an .asoundrc
containing this:
pcm.!default {
type plug
slave.pcm "surround51"
}
I can reproduce problem in Exaile with the custom sink pipeline set to
"alsasink device=surround51" and no .asoundrc.
I'm running the amd64 build of Xubuntu.
My Audigy2 has the first alsa sound card slot, making it my default
sound card.
I am not using PulseAudio.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1247719/+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 1247719] Re: crackling, popping, clicking in playback to audigy2 surround51 device
>> pcm.!default {
>>type plug
>>slave.pcm "surround51"
>>}
>
>this won't upmix stereo to 5.1 as you expected (center and lfe are just left
>and right)
I don't expect it to upmix anything. I use that setting so that media
players can succeed at playing movies with 5.1 audio.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1247719
Title:
crackling, popping, clicking in playback to audigy2 surround51 device
Status in “alsa-driver” package in Ubuntu:
New
Bug description:
After upgrading from Xubuntu 13.04 to 13.10, I hear lots of popping
(aka crackle, click noises) during playback to my Audigy2 surround51
device. This was never a problem before the upgrade. The noises do
not show up if I use the card's default, front, or rear devices
instead, but those leave me without surround sound, so they're no good
for movie playback.
The same problem shows up on the surround40 device. I haven't tried
the other surround* devices.
I can reproduce problem in Totem or gst-launch playbin with an .asoundrc
containing this:
pcm.!default {
type plug
slave.pcm "surround51"
}
I can reproduce problem in Exaile with the custom sink pipeline set to
"alsasink device=surround51" and no .asoundrc.
I'm running the amd64 build of Xubuntu.
My Audigy2 has the first alsa sound card slot, making it my default
sound card.
I am not using PulseAudio.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1247719/+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 1247719] Re: crackling, popping, clicking in playback to audigy2 surround51 device
$ ./chmap -D hw:0,0 query
Cannot query maps
$ ./chmap -D front query
Type = FIXED, Channels = 1
UNKNOWN
Type = FIXED, Channels = 2
FL FR
$ ./chmap -D rear query
Type = FIXED, Channels = 1
UNKNOWN
Type = FIXED, Channels = 2
RL RR
$ ./chmap -D center_left query
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM center_left
Cannot open PCM stream center_left for PLAYBACK
$ ./chmap -D center_lfe query
Type = FIXED, Channels = 1
UNKNOWN
Type = FIXED, Channels = 2
FC LFE
$ ./chmap -D surround40 query
Type = FIXED, Channels = 4
FL FR RL RR
$ ./chmap -D surround51 query
Type = FIXED, Channels = 6
FL FR RL RR FC LFE
$ ./chmap -D default query
Type = FIXED, Channels = 6
FL FR RL RR FC LFE
When I comment out my pcm.!default line in .asoundrc, I get this result:
$ ./chmap -D default query
Cannot query maps
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1247719
Title:
crackling, popping, clicking in playback to audigy2 surround51 device
Status in “alsa-driver” package in Ubuntu:
New
Bug description:
After upgrading from Xubuntu 13.04 to 13.10, I hear lots of popping
(aka crackle, click noises) during playback to my Audigy2 surround51
device. This was never a problem before the upgrade. The noises do
not show up if I use the card's default, front, or rear devices
instead, but those leave me without surround sound, so they're no good
for movie playback.
The same problem shows up on the surround40 device. I haven't tried
the other surround* devices.
I can reproduce problem in Totem or gst-launch playbin with an .asoundrc
containing this:
pcm.!default {
type plug
slave.pcm "surround51"
}
I can reproduce problem in Exaile with the custom sink pipeline set to
"alsasink device=surround51" and no .asoundrc.
I'm running the amd64 build of Xubuntu.
My Audigy2 has the first alsa sound card slot, making it my default
sound card.
I am not using PulseAudio.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1247719/+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 1247719] Re: crackling, popping, clicking in playback to audigy2 surround51 device
> did the problem occur with non 48000Hz audio ?
It definitely occurs with a 44100Hz PCM wav file. Gstreamer says this about
one file I'm using to test:
channels=(int)2, width=(int)16, depth=(int)16, signed=(boolean)true,
rate=(int)44100
It also occurs with a 48000Hz PCM wav file. I resampled the above file to
48000Hz using audacity. Here's what Gstreamer says about the resampled file:
channels=(int)2, width=(int)16, depth=(int)16, signed=(boolean)true,
rate=(int)48000
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1247719
Title:
crackling, popping, clicking in playback to audigy2 surround51 device
Status in “alsa-driver” package in Ubuntu:
New
Bug description:
After upgrading from Xubuntu 13.04 to 13.10, I hear lots of popping
(aka crackle, click noises) during playback to my Audigy2 surround51
device. This was never a problem before the upgrade. The noises do
not show up if I use the card's default, front, or rear devices
instead, but those leave me without surround sound, so they're no good
for movie playback.
The same problem shows up on the surround40 device. I haven't tried
the other surround* devices.
I can reproduce problem in Totem or gst-launch playbin with an .asoundrc
containing this:
pcm.!default {
type plug
slave.pcm "surround51"
}
I can reproduce problem in Exaile with the custom sink pipeline set to
"alsasink device=surround51" and no .asoundrc.
I'm running the amd64 build of Xubuntu.
My Audigy2 has the first alsa sound card slot, making it my default
sound card.
I am not using PulseAudio.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1247719/+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 1247719] Re: crackling, popping, clicking in playback to audigy2 surround51 device
All these sound fine:
speaker-test -d -c 2 -t wav -D front
speaker-test -d -c 2 -t wav -D rear
speaker-test -d -c 2 -t wav -D center_lfe
speaker-test -d -c 4 -t wav -D surround40
speaker-test -d -c 2 -t wav -D default
speaker-test -d -c 4 -t wav -D default
speaker-test -d -c 6 -t wav -D default
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1247719
Title:
crackling, popping, clicking in playback to audigy2 surround51 device
Status in “alsa-driver” package in Ubuntu:
New
Bug description:
After upgrading from Xubuntu 13.04 to 13.10, I hear lots of popping
(aka crackle, click noises) during playback to my Audigy2 surround51
device. This was never a problem before the upgrade. The noises do
not show up if I use the card's default, front, or rear devices
instead, but those leave me without surround sound, so they're no good
for movie playback.
The same problem shows up on the surround40 device. I haven't tried
the other surround* devices.
I can reproduce problem in Totem or gst-launch playbin with an .asoundrc
containing this:
pcm.!default {
type plug
slave.pcm "surround51"
}
I can reproduce problem in Exaile with the custom sink pipeline set to
"alsasink device=surround51" and no .asoundrc.
I'm running the amd64 build of Xubuntu.
My Audigy2 has the first alsa sound card slot, making it my default
sound card.
I am not using PulseAudio.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1247719/+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 1247719] Re: crackling, popping, clicking in playback to audigy2 surround51 device
speaker-test -c 6 -t wav -Dsurround51 produces clear test sounds; no
crackling.
I'm attaching the alsa-info.sh output.
$ pactl list
The program 'pactl' is currently not installed. You can install it by typing:
sudo apt-get install pulseaudio-utils
$ pactl stat
The program 'pactl' is currently not installed. You can install it by typing:
sudo apt-get install pulseaudio-utils
$ pulseaudio verbose log
The program 'pulseaudio' is currently not installed. You can install it by
typing:
sudo apt-get install pulseaudio
(As I said, I'm not using PulseAudio.)
** Attachment added: "alsa-info.sh output"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1247719/+attachment/3900079/+files/alsa-info.txt
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1247719
Title:
crackling, popping, clicking in playback to audigy2 surround51 device
Status in “alsa-driver” package in Ubuntu:
New
Bug description:
After upgrading from Xubuntu 13.04 to 13.10, I hear lots of popping
(aka crackle, click noises) during playback to my Audigy2 surround51
device. This was never a problem before the upgrade. The noises do
not show up if I use the card's default, front, or rear devices
instead, but those leave me without surround sound, so they're no good
for movie playback.
The same problem shows up on the surround40 device. I haven't tried
the other surround* devices.
I can reproduce problem in Totem or gst-launch playbin with an .asoundrc
containing this:
pcm.!default {
type plug
slave.pcm "surround51"
}
I can reproduce problem in Exaile with the custom sink pipeline set to
"alsasink device=surround51" and no .asoundrc.
I'm running the amd64 build of Xubuntu.
My Audigy2 has the first alsa sound card slot, making it my default
sound card.
I am not using PulseAudio.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1247719/+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 1247719] Re: crackling, popping, clicking in playback to audigy2 surround51 device
Possibly of interest: The noise occurs with both gst-launch-0.10 and
gst-launch-1.0.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1247719
Title:
crackling, popping, clicking in playback to audigy2 surround51 device
Status in “alsa-driver” package in Ubuntu:
New
Bug description:
After upgrading from Xubuntu 13.04 to 13.10, I hear lots of popping
(aka crackle, click noises) during playback to my Audigy2 surround51
device. This was never a problem before the upgrade. The noises do
not show up if I use the card's default, front, or rear devices
instead, but those leave me without surround sound, so they're no good
for movie playback.
The same problem shows up on the surround40 device. I haven't tried
the other surround* devices.
I can reproduce problem in Totem or gst-launch playbin with an .asoundrc
containing this:
pcm.!default {
type plug
slave.pcm "surround51"
}
I can reproduce problem in Exaile with the custom sink pipeline set to
"alsasink device=surround51" and no .asoundrc.
I'm running the amd64 build of Xubuntu.
My Audigy2 has the first alsa sound card slot, making it my default
sound card.
I am not using PulseAudio.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1247719/+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 1247719] [NEW] crackling, popping, clicking in playback to audigy2 surround51 device
Public bug reported:
After upgrading from Xubuntu 13.04 to 13.10, I hear lots of popping (aka
crackle, click noises) during playback to my Audigy2 surround51 device.
This was never a problem before the upgrade. The noises do not show up
if I use the card's default, front, or rear devices instead, but those
leave me without surround sound, so they're no good for movie playback.
The same problem shows up on the surround40 device. I haven't tried the
other surround* devices.
I can reproduce problem in Totem or gst-launch playbin with an .asoundrc
containing this:
pcm.!default {
type plug
slave.pcm "surround51"
}
I can reproduce problem in Exaile with the custom sink pipeline set to
"alsasink device=surround51" and no .asoundrc.
I'm running the amd64 build of Xubuntu.
My Audigy2 has the first alsa sound card slot, making it my default
sound card.
I am not using PulseAudio.
** Affects: alsa-driver (Ubuntu)
Importance: Undecided
Status: New
** Tags: regression
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1247719
Title:
crackling, popping, clicking in playback to audigy2 surround51 device
Status in “alsa-driver” package in Ubuntu:
New
Bug description:
After upgrading from Xubuntu 13.04 to 13.10, I hear lots of popping
(aka crackle, click noises) during playback to my Audigy2 surround51
device. This was never a problem before the upgrade. The noises do
not show up if I use the card's default, front, or rear devices
instead, but those leave me without surround sound, so they're no good
for movie playback.
The same problem shows up on the surround40 device. I haven't tried
the other surround* devices.
I can reproduce problem in Totem or gst-launch playbin with an .asoundrc
containing this:
pcm.!default {
type plug
slave.pcm "surround51"
}
I can reproduce problem in Exaile with the custom sink pipeline set to
"alsasink device=surround51" and no .asoundrc.
I'm running the amd64 build of Xubuntu.
My Audigy2 has the first alsa sound card slot, making it my default
sound card.
I am not using PulseAudio.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1247719/+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 1232575] Re: chrome.extension not available when called from extension scripts in Chromium but works on Chrome
Is there any indication of when it will appear in a saucy repo? I don't see it in -proposed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1232575 Title: chrome.extension not available when called from extension scripts in Chromium but works on Chrome Status in Chromium Browser: Unknown Status in “chromium-browser” package in Ubuntu: Fix Committed Bug description: When I updated to 13.10 and Chromium 29.0.1547.65-0ubuntu2, a few extensions stopped working properly. The easiest to reproduce is Reddit Enhancement Suite 4.3.0.1, it immediately fails on loading the extension with this error: chrome.extension is not available: 'extension' is not allowed for specified context type content script, extension page, web page, etc.). [VM] binding (22):427 Following from anywhere that called chrome.extension.sendMessage or chrome.extension.onMessage in the extension. Chromium's own bug tracker says this usage is deprecated (replaced by chrome.runtime namespace which does work) but testing against Chrome 29.0.1547.76 on the stable channel, the older namespace works correctly with the extensions. chromium-browser: Installed: 29.0.1547.65-0ubuntu2 Candidate: 29.0.1547.65-0ubuntu2 Version table: *** 29.0.1547.65-0ubuntu2 0 500 http://mirrors.cat.pdx.edu/ubuntu/ saucy/universe amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1232575/+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 1048105] Re: negative ref count in treeview selection function using python-dbg
This problem still exists in ubuntu 13.10 (saucy). ** Tags added: saucy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pygtk in Ubuntu. https://bugs.launchpad.net/bugs/1048105 Title: negative ref count in treeview selection function using python-dbg Status in “pygtk” package in Ubuntu: Confirmed Bug description: When you run python-dbg with the debug packages, if you call set_select_function on a treeview, whenever the function is called python-dbg will assert with the following error: Fatal Python error: gtktreeview.override:671 object at 0xb83fb0 has negative ref count -1 Attached is a test program that reproduces this each time you select the item in the treeview. Kubuntu 12.04.1 Python 2.7.3 PyGTK 2.24.0-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygtk/+bug/1048105/+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 1048105] Re: negative ref count in treeview selection function using python-dbg
...and just to be clear, it is important because it prevents us from debugging other programs. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pygtk in Ubuntu. https://bugs.launchpad.net/bugs/1048105 Title: negative ref count in treeview selection function using python-dbg Status in “pygtk” package in Ubuntu: Confirmed Bug description: When you run python-dbg with the debug packages, if you call set_select_function on a treeview, whenever the function is called python-dbg will assert with the following error: Fatal Python error: gtktreeview.override:671 object at 0xb83fb0 has negative ref count -1 Attached is a test program that reproduces this each time you select the item in the treeview. Kubuntu 12.04.1 Python 2.7.3 PyGTK 2.24.0-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygtk/+bug/1048105/+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 1233312] Re: udisksd crashed with SIGSEGV in ffi_call_unix64()
*** This bug is a duplicate of bug 1186525 *** https://bugs.launchpad.net/bugs/1186525 P.S. I'm on Raring amd64, udisks2 2.1.0-2, kernel 3.8.0-32-generic. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1233312 Title: udisksd crashed with SIGSEGV in ffi_call_unix64() Status in “udisks2” package in Ubuntu: Confirmed Bug description: Crash was reported shortly after login. No obvious reason. An external USB HDD was plugged in at the time. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: udisks2 2.1.0-4 ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2 Uname: Linux 3.11.0-9-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Mon Sep 30 18:37:38 2013 ExecutablePath: /usr/lib/udisks2/udisksd InstallationDate: Installed on 2013-08-19 (41 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130819) MachineType: LENOVO 4178CTO MarkForUpload: True ProcCmdline: /usr/lib/udisks2/udisksd --no-debug ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-9-generic root=UUID=0317bf16-0f96-4c2e-a5a9-10fef37c9d7e ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x4348a5: mov(%rax),%ebp PC (0x004348a5) ok source "(%rax)" (0x) not located in a known VMA region (needed readable region)! destination "%ebp" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: udisks2 StacktraceTop: ?? () ?? () ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 g_cclosure_marshal_generic () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: udisksd crashed with SIGSEGV in ffi_call_unix64() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 11/30/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 83ET73WW (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 4178CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr83ET73WW(1.43):bd11/30/2012:svnLENOVO:pn4178CTO:pvrThinkPadT420:rvnLENOVO:rn4178CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4178CTO dmi.product.version: ThinkPad T420 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1233312/+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 1233312] Re: udisksd crashed with SIGSEGV in ffi_call_unix64()
*** This bug is a duplicate of bug 1186525 *** https://bugs.launchpad.net/bugs/1186525 I logged in to find this crash report, too. I had an eSATA drive plugged in at the time. Launchpad is telling me this report is a duplicate, but won't let me see the report that it duplicates. Why not? That's not very helpful. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1233312 Title: udisksd crashed with SIGSEGV in ffi_call_unix64() Status in “udisks2” package in Ubuntu: Confirmed Bug description: Crash was reported shortly after login. No obvious reason. An external USB HDD was plugged in at the time. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: udisks2 2.1.0-4 ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2 Uname: Linux 3.11.0-9-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Mon Sep 30 18:37:38 2013 ExecutablePath: /usr/lib/udisks2/udisksd InstallationDate: Installed on 2013-08-19 (41 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130819) MachineType: LENOVO 4178CTO MarkForUpload: True ProcCmdline: /usr/lib/udisks2/udisksd --no-debug ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-9-generic root=UUID=0317bf16-0f96-4c2e-a5a9-10fef37c9d7e ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x4348a5: mov(%rax),%ebp PC (0x004348a5) ok source "(%rax)" (0x) not located in a known VMA region (needed readable region)! destination "%ebp" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: udisks2 StacktraceTop: ?? () ?? () ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 g_cclosure_marshal_generic () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: udisksd crashed with SIGSEGV in ffi_call_unix64() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 11/30/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 83ET73WW (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 4178CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr83ET73WW(1.43):bd11/30/2012:svnLENOVO:pn4178CTO:pvrThinkPadT420:rvnLENOVO:rn4178CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4178CTO dmi.product.version: ThinkPad T420 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1233312/+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 1186801] Re: liferea is completely invisible when running on xubuntu
** Tags added: saucy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to liferea in Ubuntu. https://bugs.launchpad.net/bugs/1186801 Title: liferea is completely invisible when running on xubuntu Status in “liferea” package in Ubuntu: Triaged Bug description: The patch recently applied to liferea for Unity messaging menu support (port-to-messaging-menu.patch) broke liferea on xubuntu. It eliminated liferea's system tray icon, thereby making liferea inaccessible in xfce when running minimized or started in a minimized state (as is the case for most people who let it auto-start at login time). Here is the changelog entry corresponding to the offending patch: > liferea (1.8.10-0ubuntu2) raring; urgency=low > > * Port to messaging-menu. (LP: #1040259) > -- Dmitrijs Ledkovs Mon, 25 Mar 2013 16:55:30 + To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/liferea/+bug/1186801/+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 1236619] [NEW] gvfs smb/cifs file copy performance is terribly slow
Public bug reported: Copying moderate-size files to a samba share using gvfs is ridiculously slow compared to doing the same via mount.cifs. For example: $ ls -sh testfile 1.2G testfile $ time cp testfile ~/mnt/share-gvfs/ real2m37.053s user0m0.056s sys 0m5.120s $ time cp testfile ~/mnt/share/ real0m26.134s user0m0.004s sys 0m1.724s I'm running Xubuntu 13.04 (raring) amd64, gvfs 1.16.1-0ubuntu1.1. ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1236619 Title: gvfs smb/cifs file copy performance is terribly slow Status in “gvfs” package in Ubuntu: New Bug description: Copying moderate-size files to a samba share using gvfs is ridiculously slow compared to doing the same via mount.cifs. For example: $ ls -sh testfile 1.2G testfile $ time cp testfile ~/mnt/share-gvfs/ real 2m37.053s user 0m0.056s sys 0m5.120s $ time cp testfile ~/mnt/share/ real 0m26.134s user 0m0.004s sys 0m1.724s I'm running Xubuntu 13.04 (raring) amd64, gvfs 1.16.1-0ubuntu1.1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1236619/+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 984785] Re: .goutputstream files polluting $HOME
(Oops: I guess launchpad doesn't recognize that format for bug links. Here's a direct link.) https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1175023 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/984785 Title: .goutputstream files polluting $HOME Status in The "G" Library - GLib: Fix Released Status in Light Display Manager: Fix Released Status in X.Org X server: New Status in “glib2.0” package in Ubuntu: Fix Committed Status in “lightdm” package in Ubuntu: Invalid Status in “glib2.0” source package in Precise: Triaged Status in “lightdm” source package in Precise: Invalid Bug description: .goutputstream files polluting $HOME. Which software or operation is creating these and why? ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xauth 1:1.0.6-1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 NonfreeKernelModules: nvidia & ati ApportVersion: 2.0.1-0ubuntu4 Architecture: amd64 Date: Wed Apr 18 13:29:31 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xauth UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/984785/+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 984785] Re: .goutputstream files polluting $HOME
See also: #1175023 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/984785 Title: .goutputstream files polluting $HOME Status in The "G" Library - GLib: Fix Released Status in Light Display Manager: Fix Released Status in X.Org X server: New Status in “glib2.0” package in Ubuntu: Fix Committed Status in “lightdm” package in Ubuntu: Invalid Status in “glib2.0” source package in Precise: Triaged Status in “lightdm” source package in Precise: Invalid Bug description: .goutputstream files polluting $HOME. Which software or operation is creating these and why? ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xauth 1:1.0.6-1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 NonfreeKernelModules: nvidia & ati ApportVersion: 2.0.1-0ubuntu4 Architecture: amd64 Date: Wed Apr 18 13:29:31 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xauth UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/984785/+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 1201163] [NEW] Totem forgets its custom menu accelerators
Public bug reported: Totem accepts my custom keyboard shortcuts (set via the standard GTK editable menu accelerator feature) and honors them for the current session, but it doesn't save them. The next time I run Totem, they're gone. I'm using Totem 3.6.3 on Xubuntu 13.04 (raring). ** Affects: totem Importance: Unknown Status: Unknown ** Affects: totem (Ubuntu) Importance: Undecided Status: New ** Bug watch added: GNOME Bug Tracker #704208 https://bugzilla.gnome.org/show_bug.cgi?id=704208 ** Also affects: totem via https://bugzilla.gnome.org/show_bug.cgi?id=704208 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1201163 Title: Totem forgets its custom menu accelerators Status in Totem Movie Player: Unknown Status in “totem” package in Ubuntu: New Bug description: Totem accepts my custom keyboard shortcuts (set via the standard GTK editable menu accelerator feature) and honors them for the current session, but it doesn't save them. The next time I run Totem, they're gone. I'm using Totem 3.6.3 on Xubuntu 13.04 (raring). To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1201163/+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 1192826] [NEW] totem.desktop description "Videos" is so vague as to be useless
Public bug reported: The .desktop file installed with totem in Xubuntu 13.04 has the application name "Videos". There are several problems with this: - It is not the name of the application. - It does not describe the purpose of the application. - It refers to only one kind of document that the application can handle. - It does not indicate that it can only play those documents, not modify or create them. - It does not distinguish itself from all the other applications that can handle the same documents. In short, it is so vague and ambiguous as to be confusing; basically less than useless. This is an issue in application launcher menus, MIME document associations, and in the "open with application..." context menus of certain file managers. In order to save unsuspecting users from madness, I suggest the .desktop file's Name field be updated to something like "Totem Movie Player" or "Media Player (Totem)". ** Affects: totem (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1192826 Title: totem.desktop description "Videos" is so vague as to be useless Status in “totem” package in Ubuntu: New Bug description: The .desktop file installed with totem in Xubuntu 13.04 has the application name "Videos". There are several problems with this: - It is not the name of the application. - It does not describe the purpose of the application. - It refers to only one kind of document that the application can handle. - It does not indicate that it can only play those documents, not modify or create them. - It does not distinguish itself from all the other applications that can handle the same documents. In short, it is so vague and ambiguous as to be confusing; basically less than useless. This is an issue in application launcher menus, MIME document associations, and in the "open with application..." context menus of certain file managers. In order to save unsuspecting users from madness, I suggest the .desktop file's Name field be updated to something like "Totem Movie Player" or "Media Player (Totem)". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1192826/+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 1192738] [NEW] nm-applet fails to alert the user when the Cloned MAC address cannot be set
*** This bug is a security vulnerability *** Public security bug reported: I have a netbook whose wifi driver seems to be refusing to allow a custom MAC address to be set. The Network Manager applet allows me to enter a value in the "Cloned MAC address" field, but when it comes time to actually set the MAC address and the driver doesn't accept it, the applet fails to notify me of the problem and exposes my hardware MAC address to the wireless network anyway. NetworkManager does log the problem to syslog, but relatively few users will notice this because the UI makes it look like everything worked just fine, and it doesn't solve the problem of quietly exposing the hardware MAC address without the user's permission. This is on an i386 Ubuntu 13.04 (raring) system, with network-manager- gnome 0.9.8.0-1ubuntu2. The wlan driver is rt8800pci. ** Affects: network-manager-applet Importance: Unknown Status: Unknown ** Affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New ** Information type changed from Private Security to Public Security ** Bug watch added: GNOME Bug Tracker #702702 https://bugzilla.gnome.org/show_bug.cgi?id=702702 ** Also affects: network-manager-applet via https://bugzilla.gnome.org/show_bug.cgi?id=702702 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1192738 Title: nm-applet fails to alert the user when the Cloned MAC address cannot be set Status in Network Manager GNOME Applet: Unknown Status in “network-manager-applet” package in Ubuntu: New Bug description: I have a netbook whose wifi driver seems to be refusing to allow a custom MAC address to be set. The Network Manager applet allows me to enter a value in the "Cloned MAC address" field, but when it comes time to actually set the MAC address and the driver doesn't accept it, the applet fails to notify me of the problem and exposes my hardware MAC address to the wireless network anyway. NetworkManager does log the problem to syslog, but relatively few users will notice this because the UI makes it look like everything worked just fine, and it doesn't solve the problem of quietly exposing the hardware MAC address without the user's permission. This is on an i386 Ubuntu 13.04 (raring) system, with network-manager- gnome 0.9.8.0-1ubuntu2. The wlan driver is rt8800pci. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-applet/+bug/1192738/+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 1186801] Re: lifrea is completely invisible when running on xubuntu
** Tags added: raring regression-release -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to liferea in Ubuntu. https://bugs.launchpad.net/bugs/1186801 Title: lifrea is completely invisible when running on xubuntu Status in “liferea” package in Ubuntu: New Bug description: The patch recently applied to liferea for Unity messaging menu support (port-to-messaging-menu.patch) broke liferea on xubuntu. It eliminated liferea's system tray icon, thereby making liferea inaccessible in xfce when running minimized or started in a minimized state (as is the case for most people who let it auto-start at login time). Here is the changelog entry corresponding to the offending patch: > liferea (1.8.10-0ubuntu2) raring; urgency=low > > * Port to messaging-menu. (LP: #1040259) > -- Dmitrijs Ledkovs Mon, 25 Mar 2013 16:55:30 + To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/liferea/+bug/1186801/+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 1040259] Re: FFE: libmessaging-menu transitions for quantal
The patch applied to liferea (port-to-messaging-menu.patch) breaks liferea on xubuntu. It prevents the system tray icon from appearing, thereby making liferea inaccessible when minimized or started in a minimized state (as is the case for most people who let it auto-start at login time). Here is the changelog entry corresponding to the offending patch: > liferea (1.8.10-0ubuntu2) raring; urgency=low > > * Port to messaging-menu. (LP: #1040259) > -- Dmitrijs Ledkovs Mon, 25 Mar 2013 16:55:30 > + -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gwibber in Ubuntu. https://bugs.launchpad.net/bugs/1040259 Title: FFE: libmessaging-menu transitions for quantal Status in Gmail Watcher: Triaged Status in Lightread: Triaged Status in Quassel Irc Client: New Status in Skype-wrapper: In Progress Status in “evolution-indicator” package in Ubuntu: Fix Released Status in “gm-notify” package in Ubuntu: Triaged Status in “guayadeque” package in Ubuntu: Fix Released Status in “gwibber” package in Ubuntu: Fix Released Status in “indicator-messages” package in Ubuntu: Fix Released Status in “kdenetwork” package in Ubuntu: New Status in “kdepim” package in Ubuntu: New Status in “libdbusmenu-qt” package in Ubuntu: New Status in “libunity-webapps” package in Ubuntu: Fix Released Status in “liferea” package in Ubuntu: Fix Released Status in “openfetion” package in Ubuntu: New Status in “pidgin” package in Ubuntu: Fix Released Status in “pidgin-libnotify” package in Ubuntu: Fix Released Status in “quassel” package in Ubuntu: New Status in “smuxi” package in Ubuntu: Fix Released Status in “telepathy-indicator” package in Ubuntu: Fix Released Status in “thunderbird” package in Ubuntu: Fix Released Status in “unity-mail” package in Ubuntu: Fix Released Status in “xchat-indicator” package in Ubuntu: Fix Released Status in “gm-notify” source package in Quantal: Triaged Status in “guayadeque” source package in Quantal: New Status in “gwibber” source package in Quantal: Fix Released Status in “indicator-messages” source package in Quantal: Fix Released Status in “kdenetwork” source package in Quantal: New Status in “kdepim” source package in Quantal: New Status in “libdbusmenu-qt” source package in Quantal: New Status in “libunity-webapps” source package in Quantal: Fix Released Status in “liferea” source package in Quantal: Triaged Status in “openfetion” source package in Quantal: New Status in “pidgin” source package in Quantal: Confirmed Status in “pidgin-libnotify” source package in Quantal: In Progress Status in “quassel” source package in Quantal: New Status in “smuxi” source package in Quantal: Fix Released Status in “telepathy-indicator” source package in Quantal: Fix Released Status in “thunderbird” source package in Quantal: Fix Released Status in “unity-mail” source package in Quantal: Fix Released Status in “xchat-indicator” source package in Quantal: Fix Released Bug description: indicator-messages got updated, introducing a new libmessaging-menu api (deprecating the old libindicate library) which should make application developper's life easier. The indicator work is done and the library is ready and we started porting applications The current stack is being tested in https://launchpad.net/~ubuntu- desktop/+archive/ppa/ It includes - indicator-messages - gwibber - indicator-telepathy - thunderbird (soon, work is being finished) which is what we consider the minimal set for landing the feature for quantal we will add those soon: - pidgin - xchat-indicator - evolution-indicator To manage notifications about this bug go to: https://bugs.launchpad.net/gmailwatcher/+bug/1040259/+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 1186801] [NEW] lifrea is completely invisible when running on xubuntu
Public bug reported: The patch recently applied to liferea for Unity messaging menu support (port-to-messaging-menu.patch) broke liferea on xubuntu. It eliminated liferea's system tray icon, thereby making liferea inaccessible in xfce when running minimized or started in a minimized state (as is the case for most people who let it auto-start at login time). Here is the changelog entry corresponding to the offending patch: > liferea (1.8.10-0ubuntu2) raring; urgency=low > > * Port to messaging-menu. (LP: #1040259) > -- Dmitrijs Ledkovs Mon, 25 Mar 2013 16:55:30 > + ** Affects: liferea (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to liferea in Ubuntu. https://bugs.launchpad.net/bugs/1186801 Title: lifrea is completely invisible when running on xubuntu Status in “liferea” package in Ubuntu: New Bug description: The patch recently applied to liferea for Unity messaging menu support (port-to-messaging-menu.patch) broke liferea on xubuntu. It eliminated liferea's system tray icon, thereby making liferea inaccessible in xfce when running minimized or started in a minimized state (as is the case for most people who let it auto-start at login time). Here is the changelog entry corresponding to the offending patch: > liferea (1.8.10-0ubuntu2) raring; urgency=low > > * Port to messaging-menu. (LP: #1040259) > -- Dmitrijs Ledkovs Mon, 25 Mar 2013 16:55:30 + To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/liferea/+bug/1186801/+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 792265] Re: BraseroDvdcss could not retrieve key
I believe I'm having the same problem on Ubuntu Quantal. While trying to rip a DVD image, Brasero fails with the error message, "Error while retrieving a key used for encryption." I am able to rip the same disc just fine using dd if=/dev/sr0, so I know it's not a problem with my drive. Brasero's error message suggests that I set DVDCSS_METHOD=title and try again, which I did, but it still failed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brasero in Ubuntu. https://bugs.launchpad.net/bugs/792265 Title: BraseroDvdcss could not retrieve key Status in “brasero” package in Ubuntu: Confirmed Bug description: Binary package hint: brasero When I try to back-up a dvd as futurama seasons 2 I get this error: fatal error in vts css key. This doesn't happen with every dvd. Libdvdcss ist installed and vlc/mplayer and totem have no issues playing the dvd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/792265/+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 792265] Re: BraseroDvdcss could not retrieve key
** Changed in: brasero (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brasero in Ubuntu. https://bugs.launchpad.net/bugs/792265 Title: BraseroDvdcss could not retrieve key Status in “brasero” package in Ubuntu: Confirmed Bug description: Binary package hint: brasero When I try to back-up a dvd as futurama seasons 2 I get this error: fatal error in vts css key. This doesn't happen with every dvd. Libdvdcss ist installed and vlc/mplayer and totem have no issues playing the dvd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/792265/+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 833073] Re: oneiric gdm picker list contains system user, rabbitmq
** Also affects: rabbitmq-server (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/833073 Title: oneiric gdm picker list contains system user, rabbitmq Status in “gdm” package in Ubuntu: Confirmed Status in “rabbitmq-server” package in Ubuntu: New Bug description: Probably related to #696038, which is marked as fixed in 11.04. Screen photo of picker attached. $ id rabbitmq uid=133(rabbitmq) gid=139(rabbitmq) groups=139(rabbitmq) $ ck-history --frequent |head -2 cmiller 294 rabbitmq 93 $ ck-list-sessions Session4: unix-user = '133' realname = 'RabbitMQ messaging server' seat = 'Seat1' session-type = '' active = FALSE x11-display = '' x11-display-device = '' display-device = '/dev/???' remote-host-name = '' is-local = TRUE on-since = '2011-08-24T14:50:45.556121Z' login-session-id = '' Session5: unix-user = '1000' realname = 'Chad MILLER' seat = 'Seat1' session-type = 'x11' active = TRUE x11-display = ':0' x11-display-device = '/dev/tty7' display-device = '' remote-host-name = '' is-local = TRUE on-since = '2011-08-24T14:54:20.599190Z' login-session-id = '' ii gdm3.0.4-0ubuntu9 ii rabbitmq-server 2.5.0-1ubuntu1 ii consolekit 0.4.5-1 "debsums" lists no local changes for either gdm or rabbitmq-server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/833073/+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 907059] Re: Print dialog crashes on entering any data into Locked Print, Document Server, or User Code fields
** Attachment added: "Screenshot showing three fields. If text is typed into any of these three fields, evince will crash." https://bugs.launchpad.net/bugs/907059/+attachment/2641781/+files/print_dialog_screenshot.png ** Visibility changed to: Private -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/907059 Title: Print dialog crashes on entering any data into Locked Print, Document Server, or User Code fields Status in “evince” package in Ubuntu: New Bug description: When any character is typed into any of the three fields circled in the attached screenshot, evince will crash. GtkPrintUnixDialog ? ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: evince 3.2.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9 Uname: Linux 3.0.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Tue Dec 20 12:21:59 2011 EcryptfsInUse: Yes ExecutablePath: /usr/bin/evince InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/907059/+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 907059] [NEW] Print dialog crashes on entering any data into Locked Print, Document Server, or User Code fields
Private bug reported: When any character is typed into any of the three fields circled in the attached screenshot, evince will crash. GtkPrintUnixDialog ? ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: evince 3.2.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9 Uname: Linux 3.0.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Tue Dec 20 12:21:59 2011 EcryptfsInUse: Yes ExecutablePath: /usr/bin/evince InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug oneiric running-unity -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/907059 Title: Print dialog crashes on entering any data into Locked Print, Document Server, or User Code fields Status in “evince” package in Ubuntu: New Bug description: When any character is typed into any of the three fields circled in the attached screenshot, evince will crash. GtkPrintUnixDialog ? ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: evince 3.2.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9 Uname: Linux 3.0.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Tue Dec 20 12:21:59 2011 EcryptfsInUse: Yes ExecutablePath: /usr/bin/evince InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/907059/+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 870297] Re: Lightdm logins not being logged in wtmp
This may be the underlying cause of bug #896663. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/870297 Title: Lightdm logins not being logged in wtmp Status in “lightdm” package in Ubuntu: Confirmed Bug description: When logged into a graphical session, I get no acknowledgement from who, w or last that I am logged in: $ who $ w 16:48:14 up 1 day, 1:08, 0 users, load average: 0.68, 0.83, 0.84 USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT last only reports tty logins, not graphical logins. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: lightdm 1.0.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.0.0-12.19-generic-pae 3.0.4 Uname: Linux 3.0.0-12-generic-pae i686 NonfreeKernelModules: fglrx ApportVersion: 1.23-0ubuntu2 Architecture: i386 Date: Fri Oct 7 16:47:23 2011 InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110921.3) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/870297/+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 887512] Re: telepathy/butterfly fails to connect due to 301 Moved Permanently
Upstream fix is here:
http://cgit.collabora.com/git/user/maiku/papyon.git/commit/?h=bug-42689&id=011201e47004538e732f247bfeb21634c6e1d97f
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to empathy in Ubuntu.
https://bugs.launchpad.net/bugs/887512
Title:
telepathy/butterfly fails to connect due to 301 Moved Permanently
Status in “empathy” package in Ubuntu:
Confirmed
Status in “empathy” package in Fedora:
Unknown
Bug description:
Looks like a permanent 301 Redirect to the new service for MSN Address
book ==> http://local-sn.contacts.msn.com/abservice/abservice.asmx
Relevant Debug:
==
papyon/butterfly-INFO: 11/08/2011 18:42:59.976038: Starting butterfly 0.5.14:
telepathy-python 0.15.17, papyon 0.5.1
butterfly/connection-INFO: 11/08/2011 18:43:00.64961: Using direct proxy: None
butterfly/connection-INFO: 11/08/2011 18:43:00.65222: Using http proxy: None
butterfly/connection-INFO: 11/08/2011 18:43:00.65342: Using https proxy: None
papyon/papyon.msnp2p.transport-INFO: 11/08/2011 18:43:00.68002: Registering
transport
butterfly/mailnotification-DEBUG: 11/08/2011 18:43:00.74275: Initialized
butterfly/handle-INFO: 11/08/2011 18:43:00.74774: New Handle
butterfly/connection-INFO: 11/08/2011 18:43:00.75059: Connection to the
account jweng_l...@hotmail.com created
.
papyon/papyon.service-DEBUG: 11/08/2011 18:43:05.650861: >>> POST
/abservice/SharingService.asmx HTTP/1.0
Content-Length: 1898
Proxy-Connection: Keep-Alive
SOAPAction: http://www.msn.com/webservices/AddressBook/FindMembership
Host: contacts.msn.com:80
.
papyon/papyon.service-DEBUG: 11/08/2011 18:43:06.91830: <<< HTTP/1.1 301
Moved Permanently
Cache-Control: private, max-age=0
Keep-Alive: true
Content-Length: 673
Content-Type: text/xml; charset=utf-8
Content-Encoding: gzip
Location: http://local-sn.contacts.msn.com/abservice/abservice.asmx
X-MSNSERVER: BAYCDP9012404
X-AspNet-Version: 4.0.30319
Date: Tue, 08 Nov 2011 10:43:08 GMT
Connection: keep-alive
stderr-ERROR: 11/08/2011 18:43:06.94547: Traceback (most recent call last):
stderr-ERROR: 11/08/2011 18:43:06.94579: File
"/usr/lib/pymodules/python2.6/papyon/service/SOAPService.py", line 228, in
_response_handler
stderr-ERROR: 11/08/2011 18:43:06.94741: handler(callback, errback,
response, user_data)
stderr-ERROR: 11/08/2011 18:43:06.94789: File
"/usr/lib/pymodules/python2.6/papyon/service/AddressBook/ab.py", line 182, in
_HandleABFindAllResponse
stderr-ERROR: 11/08/2011 18:43:06.94923: last_changes =
response[0].find("./ab:lastChange")
stderr-ERROR: 11/08/2011 18:43:06.94984: AttributeError: 'NoneType' object
has no attribute 'find'
papyon/papyon.service-DEBUG: 11/08/2011 18:43:06.135705: <<< HTTP/1.1 301
Moved Permanently
Cache-Control: private, max-age=0
Keep-Alive: true
Content-Length: 675
Content-Type: text/xml; charset=utf-8
Content-Encoding: gzip
Location: http://local-sn.contacts.msn.com/abservice/SharingService.asmx
X-MSNSERVER: BY2CDP5012811
X-AspNet-Version: 4.0.30319
Date: Tue, 08 Nov 2011 10:43:07 GMT
Connection: keep-alive
.
Thanks!
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: empathy 2.32.1-0ubuntu1.2
ProcVersionSignature: Ubuntu 2.6.35-30.61-generic-pae 2.6.35.13
Uname: Linux 2.6.35-30-generic-pae i686
NonfreeKernelModules: wl
Architecture: i386
Date: Tue Nov 8 18:49:59 2011
ExecutablePath: /usr/bin/empathy
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcEnviron:
LANG=en_US.utf8
SHELL=/bin/bash
SourcePackage: empathy
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/887512/+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 887512] Re: telepathy/butterfly fails to connect due to 301 Moved Permanently
** Bug watch added: Red Hat Bugzilla #750884
https://bugzilla.redhat.com/show_bug.cgi?id=750884
** Also affects: empathy (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=750884
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to empathy in Ubuntu.
https://bugs.launchpad.net/bugs/887512
Title:
telepathy/butterfly fails to connect due to 301 Moved Permanently
Status in “empathy” package in Ubuntu:
Confirmed
Status in “empathy” package in Fedora:
Unknown
Bug description:
Looks like a permanent 301 Redirect to the new service for MSN Address
book ==> http://local-sn.contacts.msn.com/abservice/abservice.asmx
Relevant Debug:
==
papyon/butterfly-INFO: 11/08/2011 18:42:59.976038: Starting butterfly 0.5.14:
telepathy-python 0.15.17, papyon 0.5.1
butterfly/connection-INFO: 11/08/2011 18:43:00.64961: Using direct proxy: None
butterfly/connection-INFO: 11/08/2011 18:43:00.65222: Using http proxy: None
butterfly/connection-INFO: 11/08/2011 18:43:00.65342: Using https proxy: None
papyon/papyon.msnp2p.transport-INFO: 11/08/2011 18:43:00.68002: Registering
transport
butterfly/mailnotification-DEBUG: 11/08/2011 18:43:00.74275: Initialized
butterfly/handle-INFO: 11/08/2011 18:43:00.74774: New Handle
butterfly/connection-INFO: 11/08/2011 18:43:00.75059: Connection to the
account jweng_l...@hotmail.com created
.
papyon/papyon.service-DEBUG: 11/08/2011 18:43:05.650861: >>> POST
/abservice/SharingService.asmx HTTP/1.0
Content-Length: 1898
Proxy-Connection: Keep-Alive
SOAPAction: http://www.msn.com/webservices/AddressBook/FindMembership
Host: contacts.msn.com:80
.
papyon/papyon.service-DEBUG: 11/08/2011 18:43:06.91830: <<< HTTP/1.1 301
Moved Permanently
Cache-Control: private, max-age=0
Keep-Alive: true
Content-Length: 673
Content-Type: text/xml; charset=utf-8
Content-Encoding: gzip
Location: http://local-sn.contacts.msn.com/abservice/abservice.asmx
X-MSNSERVER: BAYCDP9012404
X-AspNet-Version: 4.0.30319
Date: Tue, 08 Nov 2011 10:43:08 GMT
Connection: keep-alive
stderr-ERROR: 11/08/2011 18:43:06.94547: Traceback (most recent call last):
stderr-ERROR: 11/08/2011 18:43:06.94579: File
"/usr/lib/pymodules/python2.6/papyon/service/SOAPService.py", line 228, in
_response_handler
stderr-ERROR: 11/08/2011 18:43:06.94741: handler(callback, errback,
response, user_data)
stderr-ERROR: 11/08/2011 18:43:06.94789: File
"/usr/lib/pymodules/python2.6/papyon/service/AddressBook/ab.py", line 182, in
_HandleABFindAllResponse
stderr-ERROR: 11/08/2011 18:43:06.94923: last_changes =
response[0].find("./ab:lastChange")
stderr-ERROR: 11/08/2011 18:43:06.94984: AttributeError: 'NoneType' object
has no attribute 'find'
papyon/papyon.service-DEBUG: 11/08/2011 18:43:06.135705: <<< HTTP/1.1 301
Moved Permanently
Cache-Control: private, max-age=0
Keep-Alive: true
Content-Length: 675
Content-Type: text/xml; charset=utf-8
Content-Encoding: gzip
Location: http://local-sn.contacts.msn.com/abservice/SharingService.asmx
X-MSNSERVER: BY2CDP5012811
X-AspNet-Version: 4.0.30319
Date: Tue, 08 Nov 2011 10:43:07 GMT
Connection: keep-alive
.
Thanks!
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: empathy 2.32.1-0ubuntu1.2
ProcVersionSignature: Ubuntu 2.6.35-30.61-generic-pae 2.6.35.13
Uname: Linux 2.6.35-30-generic-pae i686
NonfreeKernelModules: wl
Architecture: i386
Date: Tue Nov 8 18:49:59 2011
ExecutablePath: /usr/bin/empathy
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcEnviron:
LANG=en_US.utf8
SHELL=/bin/bash
SourcePackage: empathy
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/887512/+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 864880] [NEW] nmcli con down gets immediately reverted on automatic connections
Public bug reported: Running nmcli con down id my-connection-name doesn't work properly when a connection is configured to "connect automatically". The connection comes down for only a second, then goes back up again. Bringing the same connection down via nm-applet works as expected. ** Affects: network-manager Importance: Unknown Status: Unknown ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Bug watch added: GNOME Bug Tracker #660719 https://bugzilla.gnome.org/show_bug.cgi?id=660719 ** Also affects: network-manager via https://bugzilla.gnome.org/show_bug.cgi?id=660719 Importance: Unknown Status: Unknown -- 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/864880 Title: nmcli con down gets immediately reverted on automatic connections Status in NetworkManager: Unknown Status in “network-manager” package in Ubuntu: New Bug description: Running nmcli con down id my-connection-name doesn't work properly when a connection is configured to "connect automatically". The connection comes down for only a second, then goes back up again. Bringing the same connection down via nm-applet works as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/864880/+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 483541] Re: File-roller drag'n drop is unreliable
This happens to me on Xubuntu Natty, dropping files to a Thunar window on a folder to which I have full permissions. I haven't yet found a pattern behind the failures. ** Changed in: file-roller (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/483541 Title: File-roller drag'n drop is unreliable Status in “file-roller” package in Ubuntu: Confirmed Bug description: Binary package hint: file-roller Drag'n drop of a file from file-roller in Gnome to a local folder is unreliable here. It fails 1 time out of 5 here approximately. When it fails, it gives the following error message: You don't have the right permissions to extract archives in the folder "file:///home/chris/Documents/ASSET/WP5-T1/VTT/VTT-TML-Integration/Code/Web%20services/xds.txttion" Note that I'm actually trying to drop the file to this location (where the permissions are ok): /home/chris/Documents/ASSET/WP5-T1/VTT/VTT-TML-Integration/Code/Web services/ I have no idea where the trailing "xds.txttion" comes from and of course it does not exist on my local filesystem. The error always refers to this folder name. Just a hint, I think it has something to do with the time you wait until you release the mouse button to actually drop the file in the folder. I think the behavior is as follows: 1. Press mouse button on a file in file-roller, drag the mouse to the local folder, wait until a '+' appears on the left of the dragged file icon and then release the button -> It works (If you wait a sufficient amount of time, it never crashes) 2. Press mouse button on a file in file-roller, drag the mouse to the local folder, immediately release the mouse button before the '+' appears on the left of the file icon -> It does not do anything, the file is not extracted, no error (probably too fast). 3. Crash case: I think it crashes if you release the mouse button relatively fast, just before the '+' appears on the icon (or maybe at this moment). I might be wrong but this is my best guess and I hope it can help identifying the issue since it is not easy to reproduce probably. I'm using: Version: 2.28.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/483541/+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 803734] Re: gdm ignores xubuntu-gdm-theme gconf settings
Update 2: Installing gnome-settings-daemon had the unfortunate side effect of this message being written to ~/.xsession-errors every few seconds, endlessly: ** (gnome-settings-daemon:2013): WARNING **: Connection failed, reconnecting... I have therefore removed gnome-settings-daemon from my xubuntu systems. I guess I'll have to wait for lightdm before I can have a good-looking login screen again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/803734 Title: gdm ignores xubuntu-gdm-theme gconf settings Status in “gdm” package in Ubuntu: New Status in “xubuntu-artwork” package in Ubuntu: Invalid Bug description: I'm on a new installation of xubuntu Natty. When I first rebooted after installing, the xubuntu-gdm-theme showed up correctly on the login screen. Since then, gdm has started ignoring those theme settings, leaving the login screen with a black background and what looks like default colors & icons on the panel bar. I tried purging and reinstalling the following packages: gdm xubuntu-gdm-theme xubuntu-artwork xubuntu-default-settings xubuntu-desktop ...but that didn't help. I have verified that the xubuntu-gdm-theme settings are present in gdm's gconf database... $ for i in /desktop/gnome/background/picture_filename /desktop/gnome/interface/icon_theme /desktop/gnome/interface/gtk_theme /desktop/gnome/interface/buttons_have_icons /desktop/gnome/interface/menus_have_icons ; do sudo -u gdm gconftool-2 --get $i; done /usr/share/xfce4/backdrops/xubuntu-greybird.png elementaryXubuntu greybird true true ...yet they seem to be ignored. For comparison, I'm attaching screen shots of my (broken) gdm screen and a correct one from a virtual machine. (Try to ignore the fact that they're different screen resolutions.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/803734/+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
