[Desktop-packages] [Bug 1496100] [NEW] nullmailer service doesn't start if already running in a child container under LXC
Public bug reported: If you are running containers with LXC and one or more has nullmailer running, then you can't start a nullmailer service on the host. This happens because the service script looks for an existing process by name. The child nullmailer process(es) is visible on the host under the same name. You could argue that the fault lies with inadequate isolation by LXC. Also the problem may disappear when (if) the service is updated to use systemd instead of a legacy rc script. As a work around make sure that the host nullmailer service is started before that in any child container. (Child containers do not see host processes or those of other containers.) Problem detected on Ubuntu 14.04.2 LTS ** Affects: nullmailer (Ubuntu) Importance: Undecided Status: New ** Tags: lxc nullmailer ** Package changed: compiz (Ubuntu) => nullmailer (Ubuntu) ** Description changed: If you are running containers with LXC and one or more has nullmailer running, then you can't start a nullmailer service on the host. This happens because the service script looks for an existing process by name. The child nullmailer process(es) is visible on the host under the same name. You could argue that the fault lies with inadequate isolation by LXC. Also the problem may disappear when (if) the service is updated to use systemd instead of a legacy rc script. As a work around make sure that the host nullmailer service is started before that in any child container. (Child containers do not see host processes or those of other containers.) + + Problem detected on Ubuntu 14.04.2 LTS -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1496100 Title: nullmailer service doesn't start if already running in a child container under LXC Status in nullmailer package in Ubuntu: New Bug description: If you are running containers with LXC and one or more has nullmailer running, then you can't start a nullmailer service on the host. This happens because the service script looks for an existing process by name. The child nullmailer process(es) is visible on the host under the same name. You could argue that the fault lies with inadequate isolation by LXC. Also the problem may disappear when (if) the service is updated to use systemd instead of a legacy rc script. As a work around make sure that the host nullmailer service is started before that in any child container. (Child containers do not see host processes or those of other containers.) Problem detected on Ubuntu 14.04.2 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nullmailer/+bug/1496100/+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 1441423] Re: printers not listed
I have the same problem. I can't find anything that allows the use of a remote printer (i.e. one shared by cups on another machine on the network). Local system is cups 2.02, remote is cups 1.7.2 (Ubuntu 14.04). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1441423 Title: printers not listed Status in cups package in Ubuntu: Confirmed Bug description: 1. system-config-printer is not showing all printers listed in cups web interface. 2. print dialog of applications not showing all printers listed in cups web interface. 3. lpstat -a (same result as in 1., 2.) === system-config-printer v1.5.6 cups v2.0.2 Linux zzz 3.19.0-12-generic #12-Ubuntu SMP Fri Apr 3 04:03:26 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Distributor ID: Ubuntu Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 Codename: vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1441423/+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 1467840] [NEW] zabbix-agent fails to start on boot
Public bug reported: zabbix-agent 1:2.2.2+dfsg-1 uses upstart to manage the service. By default the start clause reads start on (filesystem and net-device-up IFACE=lo) this can result in the following message in /var/log/upstart/zabix- agent.log chown: invalid user: 'zabbix:zabbix' The filesystem and networks have been brought up before the system is ready to accept non root accounts. This only happens on my new hex core (with hyperthreading) machines. Changing the start clause to start on runlevel [2345] solves the problem. ** Affects: zabbix (Ubuntu) Importance: Undecided Status: New ** Package changed: compiz (Ubuntu) = zabbix (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1467840 Title: zabbix-agent fails to start on boot Status in zabbix package in Ubuntu: New Bug description: zabbix-agent 1:2.2.2+dfsg-1 uses upstart to manage the service. By default the start clause reads start on (filesystem and net-device-up IFACE=lo) this can result in the following message in /var/log/upstart/zabix- agent.log chown: invalid user: 'zabbix:zabbix' The filesystem and networks have been brought up before the system is ready to accept non root accounts. This only happens on my new hex core (with hyperthreading) machines. Changing the start clause to start on runlevel [2345] solves the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zabbix/+bug/1467840/+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 1214906] Re: logitch M570 mouse stopped working in 13.04
I have now tested the mouse on Windows and found exactly the same thing. Oh well. -- 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/1214906 Title: logitch M570 mouse stopped working in 13.04 Status in “xorg” package in Ubuntu: Invalid Bug description: The logitech M570 wireless mouse used to work. But recently it became much less sensitive. I changed battery several time and it did not help. Wired mouse works fine. If I click on a window title bar, sometimes the window gets maximized. If I drag on a line of text to select, I may get a word selected. If I drag a window around, the window may stop moving even though the mouse pointer still moves. The mouse pointer moves without any issue. But the gui does not respond to the mouse action correctly. Attached is a syslog of the logitech M570 receiver. Aug 21 00:59:54 saturn kernel: [ 2849.606566] usb 7-2: new full-speed USB device number 8 using ohci_hcd Aug 21 00:59:54 saturn kernel: [ 2849.779163] usb 7-2: New USB device found, idVendor=046d, idProduct=c52b Aug 21 00:59:54 saturn kernel: [ 2849.779175] usb 7-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Aug 21 00:59:54 saturn kernel: [ 2849.779182] usb 7-2: Product: USB Receiver Aug 21 00:59:54 saturn kernel: [ 2849.779188] usb 7-2: Manufacturer: Logitech Aug 21 00:59:54 saturn kernel: [ 2849.801466] logitech-djreceiver 0003:046D:C52B.001B: hiddev0,hidraw0: USB HID v1.11 Device [Logitech USB Receiver] on usb-:00:16.0-2/input2 Aug 21 00:59:54 saturn mtp-probe: checking bus 7, device 8: /sys/devices/pci:00/:00:16.0/usb7/7-2 Aug 21 00:59:54 saturn mtp-probe: bus: 7, device: 8 was not an MTP device Aug 21 00:59:54 saturn kernel: [ 2849.806777] input: Logitech Unifying Device. Wireless PID:1028 as /devices/pci:00/:00:16.0/usb7/7-2/7-2:1.2/0003:046D:C52B.001B/input/input23 Aug 21 00:59:54 saturn kernel: [ 2849.807096] logitech-djdevice 0003:046D:C52B.001C: input,hidraw2: USB HID v1.11 Mouse [Logitech Unifying Device. Wireless PID:1028] on usb-:00:16.0-2:1 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Aug 21 08:33:59 2013 DistUpgraded: 2013-06-23 14:25:17,675 DEBUG enabling apt cron job DistroCodename: raring DistroVariant: ubuntu DkmsStatus: fglrx-updates, 9.012, 3.8.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices [AMD] nee ATI Redwood LE [Radeon HD 5550] [1002:68da] (prog-if 00 [VGA controller]) Subsystem: Hightech Information System Ltd. Device [1787:200d] InstallationDate: Installed on 2013-04-02 (141 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MachineType: Gigabyte Technology Co., Ltd. GA-890FXA-UD5 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic root=UUID=f630d0df-facb-47b4-b39a-be87a1252e93 ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to raring on 2013-06-23 (58 days ago) dmi.bios.date: 11/24/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F6 dmi.board.name: GA-890FXA-UD5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF6:bd11/24/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-890FXA-UD5:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-890FXA-UD5:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-890FXA-UD5 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.9~daily13.06.19~13.04-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.43-0ubuntu1.1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.3-0ubuntu0.3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2
[Desktop-packages] [Bug 1130571] Re: wired network disabled after resume
The problem seems to be the alx driver. The workaround here: http://www.webupd8.org/2013/01/fix-wireless-or-wired-network-not.html works. -- 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/1130571 Title: wired network disabled after resume Status in “network-manager” package in Ubuntu: New Bug description: I have both a wired network and wireless. On first boot both are functional, but on resuming from sleep the wired controller is disabled (wireless still works). This behaviour started with the latest kernel installed yesterday. From syslog on resume Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]: info Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889) Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]: info Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889) Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]: info (eth4): now managed Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]: info (eth4): device state change: unmanaged - unavailable (reason 'managed') [10 20 2] Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]: info (eth4): bringing up device. Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]: info (eth4): deactivating device (reason 'managed') [2] uname -a Linux mark-PBL21 3.5.0-24-generic #37-Ubuntu SMP Thu Feb 7 01:50:30 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux $ sudo lshw -C network [sudo] password for mthornton: *-network description: Wireless interface product: AR9485 Wireless Network Adapter vendor: Atheros Communications Inc. physical id: 0 bus info: pci@:03:00.0 logical name: wlan3 version: 01 serial: dc:85:de:03:c8:ce width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list rom ethernet physical wireless configuration: broadcast=yes driver=ath9k driverversion=3.5.0-24-generic firmware=N/A ip=192.168.41.214 latency=0 link=yes multicast=yes wireless=IEEE 802.11bgn resources: irq:17 memory:f790-f797 memory:f798-f798 *-network DISABLED description: Ethernet interface product: AR8161 Gigabit Ethernet vendor: Atheros Communications Inc. physical id: 0 bus info: pci@:04:00.0 logical name: eth4 version: 10 serial: 10:bf:48:9f:e9:c6 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi msix bus_master cap_list ethernet physical configuration: broadcast=yes driver=alx latency=0 multicast=yes resources: irq:19 memory:f780-f783 ioport:d000(size=128) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1130571/+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 1130571] Re: wired network disabled after resume
Now fixed as of Linux mark-PBL21 3.5.0-25-generic #39-Ubuntu SMP Mon Feb 25 18:26:58 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux -- 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/1130571 Title: wired network disabled after resume Status in “network-manager” package in Ubuntu: New Bug description: I have both a wired network and wireless. On first boot both are functional, but on resuming from sleep the wired controller is disabled (wireless still works). This behaviour started with the latest kernel installed yesterday. From syslog on resume Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]: info Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889) Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]: info Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889) Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]: info (eth4): now managed Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]: info (eth4): device state change: unmanaged - unavailable (reason 'managed') [10 20 2] Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]: info (eth4): bringing up device. Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]: info (eth4): deactivating device (reason 'managed') [2] uname -a Linux mark-PBL21 3.5.0-24-generic #37-Ubuntu SMP Thu Feb 7 01:50:30 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux $ sudo lshw -C network [sudo] password for mthornton: *-network description: Wireless interface product: AR9485 Wireless Network Adapter vendor: Atheros Communications Inc. physical id: 0 bus info: pci@:03:00.0 logical name: wlan3 version: 01 serial: dc:85:de:03:c8:ce width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list rom ethernet physical wireless configuration: broadcast=yes driver=ath9k driverversion=3.5.0-24-generic firmware=N/A ip=192.168.41.214 latency=0 link=yes multicast=yes wireless=IEEE 802.11bgn resources: irq:17 memory:f790-f797 memory:f798-f798 *-network DISABLED description: Ethernet interface product: AR8161 Gigabit Ethernet vendor: Atheros Communications Inc. physical id: 0 bus info: pci@:04:00.0 logical name: eth4 version: 10 serial: 10:bf:48:9f:e9:c6 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi msix bus_master cap_list ethernet physical configuration: broadcast=yes driver=alx latency=0 multicast=yes resources: irq:19 memory:f780-f783 ioport:d000(size=128) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1130571/+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 1130571] Re: wired network disabled after resume
Still present with next kernel $ uname -a Linux mark-PBL21 3.5.0-25-generic #38-Ubuntu SMP Mon Feb 18 23:27:42 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux -- 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/1130571 Title: wired network disabled after resume Status in “network-manager” package in Ubuntu: New Bug description: I have both a wired network and wireless. On first boot both are functional, but on resuming from sleep the wired controller is disabled (wireless still works). This behaviour started with the latest kernel installed yesterday. From syslog on resume Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]: info Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889) Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]: info Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889) Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]: info (eth4): now managed Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]: info (eth4): device state change: unmanaged - unavailable (reason 'managed') [10 20 2] Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]: info (eth4): bringing up device. Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]: info (eth4): deactivating device (reason 'managed') [2] uname -a Linux mark-PBL21 3.5.0-24-generic #37-Ubuntu SMP Thu Feb 7 01:50:30 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux $ sudo lshw -C network [sudo] password for mthornton: *-network description: Wireless interface product: AR9485 Wireless Network Adapter vendor: Atheros Communications Inc. physical id: 0 bus info: pci@:03:00.0 logical name: wlan3 version: 01 serial: dc:85:de:03:c8:ce width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list rom ethernet physical wireless configuration: broadcast=yes driver=ath9k driverversion=3.5.0-24-generic firmware=N/A ip=192.168.41.214 latency=0 link=yes multicast=yes wireless=IEEE 802.11bgn resources: irq:17 memory:f790-f797 memory:f798-f798 *-network DISABLED description: Ethernet interface product: AR8161 Gigabit Ethernet vendor: Atheros Communications Inc. physical id: 0 bus info: pci@:04:00.0 logical name: eth4 version: 10 serial: 10:bf:48:9f:e9:c6 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi msix bus_master cap_list ethernet physical configuration: broadcast=yes driver=alx latency=0 multicast=yes resources: irq:19 memory:f780-f783 ioport:d000(size=128) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1130571/+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 1130571] [NEW] wired network disabled after resume
Public bug reported: I have both a wired network and wireless. On first boot both are functional, but on resuming from sleep the wired controller is disabled (wireless still works). This behaviour started with the latest kernel installed yesterday. From syslog on resume Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]: info Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889) Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]: info Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889) Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]: info (eth4): now managed Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]: info (eth4): device state change: unmanaged - unavailable (reason 'managed') [10 20 2] Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]: info (eth4): bringing up device. Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]: info (eth4): deactivating device (reason 'managed') [2] uname -a Linux mark-PBL21 3.5.0-24-generic #37-Ubuntu SMP Thu Feb 7 01:50:30 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux $ sudo lshw -C network [sudo] password for mthornton: *-network description: Wireless interface product: AR9485 Wireless Network Adapter vendor: Atheros Communications Inc. physical id: 0 bus info: pci@:03:00.0 logical name: wlan3 version: 01 serial: dc:85:de:03:c8:ce width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list rom ethernet physical wireless configuration: broadcast=yes driver=ath9k driverversion=3.5.0-24-generic firmware=N/A ip=192.168.41.214 latency=0 link=yes multicast=yes wireless=IEEE 802.11bgn resources: irq:17 memory:f790-f797 memory:f798-f798 *-network DISABLED description: Ethernet interface product: AR8161 Gigabit Ethernet vendor: Atheros Communications Inc. physical id: 0 bus info: pci@:04:00.0 logical name: eth4 version: 10 serial: 10:bf:48:9f:e9:c6 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi msix bus_master cap_list ethernet physical configuration: broadcast=yes driver=alx latency=0 multicast=yes resources: irq:19 memory:f780-f783 ioport:d000(size=128) ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- 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/1130571 Title: wired network disabled after resume Status in “network-manager” package in Ubuntu: New Bug description: I have both a wired network and wireless. On first boot both are functional, but on resuming from sleep the wired controller is disabled (wireless still works). This behaviour started with the latest kernel installed yesterday. From syslog on resume Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]: info Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889) Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]: info Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889) Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]: info (eth4): now managed Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]: info (eth4): device state change: unmanaged - unavailable (reason 'managed') [10 20 2] Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]: info (eth4): bringing up device. Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]: info (eth4): deactivating device (reason 'managed') [2] uname -a Linux mark-PBL21 3.5.0-24-generic #37-Ubuntu SMP Thu Feb 7 01:50:30 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux $ sudo lshw -C network [sudo] password for mthornton: *-network description: Wireless interface product: AR9485 Wireless Network Adapter vendor: Atheros Communications Inc. physical id: 0 bus info: pci@:03:00.0 logical name: wlan3 version: 01 serial: dc:85:de:03:c8:ce width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list rom ethernet physical wireless configuration: broadcast=yes driver=ath9k driverversion=3.5.0-24-generic firmware=N/A ip=192.168.41.214 latency=0 link=yes multicast=yes wireless=IEEE 802.11bgn resources: irq:17 memory:f790-f797 memory:f798-f798 *-network DISABLED description: Ethernet interface product: AR8161 Gigabit Ethernet vendor: Atheros Communications Inc. physical id: 0 bus info: pci@:04:00.0 logical name: eth4 version: 10 serial: 10:bf:48:9f:e9:c6 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi msix bus_master cap_list
[Desktop-packages] [Bug 677555] Re: banshee unable to stream audio for more than a few minutes
Still present in Banshee 2.2.1 running ubuntu 11.10. At home BBC Radio 2 will play for up to an hour or so before stopping with buffering stuck. At my office it will stop within 15 minutes. Usually play can be restarted by simply double clicking on the station or using the start/stop buttons. Same behaviour with BBC Radio 3 except play time is less (higher bit rate and thus more susceptible to network quality). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to banshee in Ubuntu. https://bugs.launchpad.net/bugs/677555 Title: banshee unable to stream audio for more than a few minutes Status in “banshee” package in Ubuntu: Incomplete Bug description: Binary package hint: banshee I like to listen to various one hour long music podcasts from dance tunes radio. From their RSS feed I get the URL to a podcast and then in banshee Open Location and paste it in. Banshee will start playing the podcast but after anywhere from one to twenty minutes will suddenly stop. The screen will show it buffering and stuck, for example right now at 9%. The play pause button also changes to the green play icon. If I use wget against the podcast then it downloads just fine. An example feed is http://blog.dance- tunes.com/sensation/Sensation_Podcast.xml (No I don't want to do RSS feed subscription within banshee - I just want it to play URLs reliably.) ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: banshee 1.8.0-2ubuntu1~maverick1 ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Fri Nov 19 09:36:32 2010 ProcEnviron: PATH=(custom, user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: banshee To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/677555/+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
