[Touch-packages] [Bug 1698248] Re: avahi-daemon constantly registers/withdraws IPv6 address record
On my network, tcpdump suggests this happened in response to the router sending an IPv6 router advertisement every few minutes, and was stopped after: ip6tables -A INPUT -p icmpv6 --icmpv6-type router-advertisement -j DROP -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1698248 Title: avahi-daemon constantly registers/withdraws IPv6 address record Status in avahi package in Ubuntu: Confirmed Bug description: Running Ubuntu 17.04, have avahi-daemon 0.6.32-1ubuntu1 installed. If I check syslog, every 5 - 10 seconds there is a set of messages like message like: Jun 15 20:53:01 dan-pc avahi-daemon[6673]: Registering new address record for 2001:1970:5ea2:c101:a899:2dfa:5a35:61fd on enp0s31f6.*. Jun 15 20:53:01 dan-pc avahi-daemon[6673]: Registering new address record for 2001:1970:5ea2:c101:64ee:d405:6df8:900a on enp0s31f6.*. Jun 15 20:53:01 dan-pc avahi-daemon[6673]: Withdrawing address record for 2001:1970:5ea2:c101:64ee:d405:6df8:900a on enp0s31f6. Jun 15 20:53:01 dan-pc avahi-daemon[6673]: Withdrawing address record for 2001:1970:5ea2:c101:a899:2dfa:5a35:61fd on enp0s31f6. etc..., which is clearly not normal. (This was also tested on a brand new installation of Ubuntu 17.04, same issue). Attached is a small sample of my syslog file. This also seems to impact other programs that use an ipv6 connection. For example, Google Chrome - half the time I try to load a webpage I get "your connection was interrupted; a network change was detected". After about a half-second, it proceeds to load the webpage, although often doesn't load it properly. This does not affect all websites (likely only those that support ipv6). See https://askubuntu.com/questions/905866/new-ubuntu-17-04-problem- your-connection-was-interrupted for other people experiencing the same bug, both in avahi and Chrome. Disabling ipv6 seems to work as a temporary workaround. I am also not sure whether this bug is caused by avahi, or whether it is just experiencing the most "symptoms". ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: avahi-daemon 0.6.32-1ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Thu Jun 15 20:42:19 2017 InstallationDate: Installed on 2017-06-10 (5 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: avahi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1698248/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1580308] Re: update-initramfs cryptsetup must correctly take into account PARTLABEL inside /etc/fstab
Are you using btrfs? If so, the relevant Debian bug report is probably https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784881 ** Bug watch added: Debian Bug tracker #784881 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784881 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1580308 Title: update-initramfs cryptsetup must correctly take into account PARTLABEL inside /etc/fstab Status in initramfs-tools package in Ubuntu: New Bug description: Systematically, - With a /etc/fstab using UUID or LABEL, update-initramfs works correctly - With a /etc/fstab using PARTLABEL, update-initramfs displays following error messages : cryptsetup: WARNING: failed to detect canonical device of PARTLABEL=Ubuntu-Gnome cryptsetup: WARNING: could not determine root device from /etc/fstab cryptsetup: WARNING: failed to detect canonical device of PARTLABEL=USR-Ubuntu The cryptsetup part of update-initramfs must correctly take into account PARTLABEL inside /etc/fstab Thank you in advance ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.122ubuntu8 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Tue May 10 21:14:24 2016 InstallationDate: Installed on 2014-11-03 (553 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: Upgraded to xenial on 2016-05-09 (1 days ago) mtime.conffile..etc.initramfs-tools.initramfs.conf: 2016-02-21T22:22:01 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1580308/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393205] Re: Intel q35 bug on Ubuntu 14.04 (Screen Artifacts)
** Also affects: xorg-server via https://bugs.freedesktop.org/show_bug.cgi?id=45092 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1393205 Title: Intel q35 bug on Ubuntu 14.04 (Screen Artifacts) Status in X.Org X server: Unknown Status in xorg package in Ubuntu: Incomplete Bug description: Picture simliar of my problem: http://i.stack.imgur.com/0ARuB.jpg I went on a Ubuntu support chat website and was told that either this problem is a "glitch" or intel q35 doesn't support Ubuntu 14.04. From the chat they told me i should downgrade to Ubuntu 12 which i did but i really want to use Ubuntu 14. They also told me to make a bug report of this. Is this a glitch or is my graphics card unsupportive. --- .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.6 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 82Q35 Express Integrated Graphics Controller [8086:29b2] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell OptiPlex 755 [1028:0211] Subsystem: Dell OptiPlex 755 [1028:0211] InstallationDate: Installed on 2014-12-07 (1 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) MachineType: Dell Inc. OptiPlex 755 Package: xorg 1:7.7+1ubuntu8 PackageArchitecture: i386 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic root=UUID=a6415cdd-4ad1-4159-845e-83a5d2c7eecc ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Tags: trusty ubuntu compiz-0.9 Uname: Linux 3.13.0-40-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/06/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0GM819 dmi.board.vendor: Dell Inc. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd04/06/2010:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0GM819:rvr:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 755 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Dec 8 16:17:35 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputMicrosoft Basic Optical Mouse MOUSE, id 8 inputDELL DELL USB Keyboard KEYBOARD, id 9 inputDELL DELL USB Keyboard KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 435 vendor ACR xserver.version: 2:1.15.1-0ubuntu2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1393205/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 592434] Re: ssh -X user@machine hangs when using exit to terminate
** Bug watch added: Debian Bug tracker #639647 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639647 ** Also affects: dbus (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639647 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/592434 Title: ssh -X user@machine hangs when using exit to terminate Status in D-Bus: Confirmed Status in dbus package in Ubuntu: Triaged Status in dbus package in Debian: Unknown Bug description: ssh -X user@server hangs when using exit to terminate Steps to reproduce: user@client:~$ ssh -X user@server user@server:~$ gedit At this point gedit from server will run locally. Closing the program and returning to the terminal you run: user@server:~$ exit logout At this point the terminal hangs on the echo logout, but does not return to the client prompt. The action has been consistent when connecting to a server running opensolaris or ubuntu 8.04. The client is using Ubuntu 10.04 and the server is using 8.04, and using default password authentication. As you will see in the video attached I can confirm the issue when using a clean Ubuntu 10.04 as a client and Ubuntu 8.04 as the server, using default password authentication. Workaround -- -When logging out with "exit" and it hangs, press Ctrl-C -If you would like to simply use gedit on another computer use the following command: $ dbus-launch gedit Date: Thu Jun 10 17:34:26 2010 To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/592434/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1520887] Re: Workaround Ubuntu 15.10. Network manager applet cannot stably activate mobile broadband using 4G USB modem ZTE MF820D.
*** This bug is a duplicate of bug 1438003 *** https://bugs.launchpad.net/bugs/1438003 settings/nm-settings-connection.c.955 - Connection didn't have requested setting 'ppp'" - see https://bugs.launchpad.net/ubuntu/+source/network- manager-applet/+bug/1508718 ** This bug has been marked a duplicate of bug 1438003 (1) Creating object for path '/org/freedesktop/NetworkManager/ActiveConnection/0' failed in libnm-glib. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1520887 Title: Workaround Ubuntu 15.10. Network manager applet cannot stably activate mobile broadband using 4G USB modem ZTE MF820D. Status in network-manager package in Ubuntu: Confirmed Bug description: Hi, I use Ubuntu 15.10, I have done a fresh install formerly using 14.04 on the same hardware setup. If I boot Ubuntu from power-off, then I must sometimes enter the PIN- code for the mobile broadband SIM-card, I also get prompted for my password (to make changes to the mobile broadband device); however, most of the time only my password is needed, and the saved PIN-code is used. After entering my password the 4G-USB-modem gets green light for establishing an 4G (or 3G) connection, but it is impossible to connect to the 4G-internet from the desktop drop down menu of network manager at this stage; I get an error message: "(Translated from Swedish- Activate connection failure) Creating object for path '/org/freedesktop/NetworkManager/ActiveConnection/1' failed in libnm- glib." (I have set up this 4G-internet-connention with help from the network- manager wizard, using defaults, except turning off roaming and setting "allow all users to connect.") However, if I choose to reboot without power-off, the green light on the USB-modem stays on during the reboot (keeps 4G-connected I presume), then it is possible to connect to internet from the drop down menu, most of the time. Some times I also had to deactivate- activate mobile broadband from the drop down menu before internet connection could be established. It is also not possible to edit the connections of the mobile broadband in the network manager applet; I get an error message: "(Translated from Swedish-Error initiating editor) settings/nm-settings-connection.c.955 - Connection didn't have requested setting 'ppp'". Editing the wifi-connection works just fine. Regards ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: network-manager 1.0.4-0ubuntu5.1 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Sun Nov 29 07:44:12 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 95.192.135.45 dev wwx0eb79c89dc58 proto static metric 750 95.192.135.44/30 dev wwx0eb79c89dc58 proto kernel scope link src 95.192.135.46 metric 750 169.254.0.0/16 dev wwx0eb79c89dc58 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: LANGUAGE=sv PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICETYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH cdc-wdm1 gsm connected /org/freedesktop/NetworkManager/Devices/3 Telia Telia 4G d851a986-be40-488b-9f96-36d2c9387b57 /org/freedesktop/NetworkManager/ActiveConnection/5 wlp3s0wifi disconnected /org/freedesktop/NetworkManager/Devices/2 -- ---- enp4s0ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- loloopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1520887/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1060081] Re: aptd crashed with UnicodeDecodeError in _emit_acquire_item(): 'utf-8' codec can't decode byte 0x93 in position 1: invalid start byte
This crash appears to be caused by a bug in apt, see Debian bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781858 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1060081 Title: aptd crashed with UnicodeDecodeError in _emit_acquire_item(): 'utf-8' codec can't decode byte 0x93 in position 1: invalid start byte Status in apt package in Ubuntu: New Status in aptdaemon package in Ubuntu: Confirmed Status in apt package in Debian: New Bug description: - ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: aptdaemon 0.45+bzr861-0ubuntu5 ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4 Uname: Linux 3.5.0-16-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 Date: Tue Oct 2 06:17:45 2012 ExecutablePath: /usr/sbin/aptd InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) InterpreterPath: /usr/bin/python3.2mu PackageArchitecture: all ProcCmdline: /usr/bin/python3.2 /usr/sbin/aptd ProcEnviron: PythonArgs: ['/usr/sbin/aptd'] SourcePackage: aptdaemon Title: aptd crashed with UnicodeDecodeError in _emit_acquire_item(): 'utf-8' codec can't decode byte 0x93 in position 1: invalid start byte UpgradeStatus: Upgraded to quantal on 2012-09-22 (9 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1060081/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1060081] Re: aptd crashed with UnicodeDecodeError in _emit_acquire_item(): 'utf-8' codec can't decode byte 0x93 in position 1: invalid start byte
** Also affects: apt (Ubuntu) Importance: Undecided Status: New ** Bug watch added: Debian Bug tracker #781858 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781858 ** Also affects: apt (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781858 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1060081 Title: aptd crashed with UnicodeDecodeError in _emit_acquire_item(): 'utf-8' codec can't decode byte 0x93 in position 1: invalid start byte Status in apt package in Ubuntu: New Status in aptdaemon package in Ubuntu: Confirmed Status in apt package in Debian: Unknown Bug description: - ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: aptdaemon 0.45+bzr861-0ubuntu5 ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4 Uname: Linux 3.5.0-16-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 Date: Tue Oct 2 06:17:45 2012 ExecutablePath: /usr/sbin/aptd InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) InterpreterPath: /usr/bin/python3.2mu PackageArchitecture: all ProcCmdline: /usr/bin/python3.2 /usr/sbin/aptd ProcEnviron: PythonArgs: ['/usr/sbin/aptd'] SourcePackage: aptdaemon Title: aptd crashed with UnicodeDecodeError in _emit_acquire_item(): 'utf-8' codec can't decode byte 0x93 in position 1: invalid start byte UpgradeStatus: Upgraded to quantal on 2012-09-22 (9 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1060081/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1060417] Re: mdadm BOOT_DEGRADED setting is ignored
*** This bug is a duplicate of bug 1302195 *** https://bugs.launchpad.net/bugs/1302195 ** This bug has been marked a duplicate of bug 1302195 System with degraded array boots regardless of BOOT_DEGRADED flag -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1060417 Title: mdadm BOOT_DEGRADED setting is ignored Status in initramfs-tools package in Ubuntu: Confirmed Bug description: The file: /usr/share/initramfs-tools/scripts/mdadm-functions is supossed to check for: BOOT_DEGRADED=true in file: /etc/initramfs-tools/conf.d/mdadm (also as per https://help.ubuntu.com/community/Installation/SoftwareRAID) however, it instead checks for it in the file: /conf/conf.d/mdadm which doesn't exit. Additionally, BOOT_DEGRADED should default to true and not false, at least for the Cloud Server images, otherwise on a RAID failure, you are left with an unbootable production system, which kind of defies the point of having the RAID in the first place. Thanks, J. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1060417/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1289243] Re: Regression in trusty, i965_dri.so crashes
*** This bug is a duplicate of bug 1378627 *** https://bugs.launchpad.net/bugs/1378627 ** This bug has been marked a duplicate of bug 1378627 chromium-browser crashed with SIGSEGV -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1289243 Title: Regression in trusty, i965_dri.so crashes Status in Mesa: Fix Released Status in mesa package in Ubuntu: Fix Released Status in mesa package in Debian: Confirmed Status in mesa package in Fedora: Unknown Bug description: I am now getting crashes like (gdb) bt #0 0x7fffe6d74958 in get_stencil_miptree (irb=0x7fffdd870080) at ../../../../../../../src/mesa/drivers/dri/i965/brw_misc_state.c:257 #1 brw_workaround_depthstencil_alignment (brw=brw@entry=0x7fffdc027018, clear_mask=clear_mask@entry=0) at ../../../../../../../src/mesa/drivers/dri/i965/brw_misc_state.c:273 #2 0x7fffe6d3197d in brw_try_draw_prims (indirect=0x0, max_index=11, min_index=0, ib=0x7fffe621da80, nr_prims=1, prims=0x7fffe621daa0, arrays=0x7fffdc211030, ctx=0x7fffdc027018) at ../../../../../../../src/mesa/drivers/dri/i965/brw_draw.c:415 #3 brw_draw_prims (ctx=0x7fffdc027018, prims=0x7fffe621daa0, nr_prims=1, ib=0x7fffe621da80, index_bounds_valid=optimized out, min_index=0, max_index=11, unused_tfb_object=0x0, indirect=0x0) at ../../../../../../../src/mesa/drivers/dri/i965/brw_draw.c:569 #4 0x7fffe6b8ec03 in vbo_handle_primitive_restart (ctx=ctx@entry=0x7fffdc027018, prim=prim@entry=0x7fffe621daa0, nr_prims=nr_prims@entry=1, ib=ib@entry=0x7fffe621da80, index_bounds_valid=index_bounds_valid@entry=0 '\000', min_index=min_index@entry=4294967295, max_index=max_index@entry=4294967295) at ../../../../src/mesa/vbo/vbo_exec_array.c:585 #5 0x7fffe6b8ff20 in vbo_validated_drawrangeelements (ctx=ctx@entry=0x7fffdc027018, mode=mode@entry=5, index_bounds_valid=index_bounds_valid@entry=0 '\000', start=start@entry=4294967295, end=end@entry=4294967295, count=count@entry=14, type=type@entry=5123, indices=indices@entry=0x7fffdc0c6bc0, basevertex=basevertex@entry=0, numInstances=numInstances@entry=1, baseInstance=baseInstance@entry=0) at ../../../../src/mesa/vbo/vbo_exec_array.c:1006 #6 0x7fffe6b90443 in vbo_exec_DrawElements (mode=5, count=14, type=5123, indices=0x7fffdc0c6bc0) at ../../../../src/mesa/vbo/vbo_exec_array.c:1156 #7 0x76744e0c in QSGDefaultRenderer::renderNodes (this=this@entry=0x7fffdc1cc670, nodes=optimized out, count=count@entry=40) at scenegraph/coreapi/qsgdefaultrenderer.cpp:536 #8 0x7674554c in QSGDefaultRenderer::render (this=0x7fffdc1cc670) at scenegraph/coreapi/qsgdefaultrenderer.cpp:281 #9 0x7674acc8 in QSGRenderer::renderScene (this=this@entry=0x7fffdc1cc670, bindable=...) at scenegraph/coreapi/qsgrenderer.cpp:271 #10 0x7674adf7 in QSGRenderer::renderScene (this=this@entry=0x7fffdc1cc670) at scenegraph/coreapi/qsgrenderer.cpp:229 #11 0x76754365 in QSGContext::renderNextFrame (this=optimized out, renderer=0x7fffdc1cc670, fboId=optimized out) at scenegraph/qsgcontext.cpp:270 #12 0x7678139a in QQuickWindowPrivate::renderSceneGraph (this=this@entry=0x662c10, size=...) at items/qquickwindow.cpp:349 #13 0x76863483 in QQuickRenderThreadSingleContextWindowManager::run (this=0x6634f0) at items/qquickthreadedwindowmanager.cpp:456 #14 0x77629186 in QThreadPrivate::start (arg=0x6634f0) at thread/qthread_unix.cpp:333 #15 0x75842182 in start_thread (arg=0x7fffe621e700) at pthread_create.c:312 #16 0x75b5312d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 When running some of the tests of unity8 where a few days ago it was fine. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1289243/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1289243] Re: Regression in trusty, i965_dri.so crashes
** Bug watch added: freedesktop.org Bugzilla #77402 https://bugs.freedesktop.org/show_bug.cgi?id=77402 ** Also affects: mesa via https://bugs.freedesktop.org/show_bug.cgi?id=77402 Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #757435 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757435 ** Also affects: mesa (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757435 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1289243 Title: Regression in trusty, i965_dri.so crashes Status in Mesa: Unknown Status in mesa package in Ubuntu: Fix Released Status in mesa package in Debian: Unknown Bug description: I am now getting crashes like (gdb) bt #0 0x7fffe6d74958 in get_stencil_miptree (irb=0x7fffdd870080) at ../../../../../../../src/mesa/drivers/dri/i965/brw_misc_state.c:257 #1 brw_workaround_depthstencil_alignment (brw=brw@entry=0x7fffdc027018, clear_mask=clear_mask@entry=0) at ../../../../../../../src/mesa/drivers/dri/i965/brw_misc_state.c:273 #2 0x7fffe6d3197d in brw_try_draw_prims (indirect=0x0, max_index=11, min_index=0, ib=0x7fffe621da80, nr_prims=1, prims=0x7fffe621daa0, arrays=0x7fffdc211030, ctx=0x7fffdc027018) at ../../../../../../../src/mesa/drivers/dri/i965/brw_draw.c:415 #3 brw_draw_prims (ctx=0x7fffdc027018, prims=0x7fffe621daa0, nr_prims=1, ib=0x7fffe621da80, index_bounds_valid=optimized out, min_index=0, max_index=11, unused_tfb_object=0x0, indirect=0x0) at ../../../../../../../src/mesa/drivers/dri/i965/brw_draw.c:569 #4 0x7fffe6b8ec03 in vbo_handle_primitive_restart (ctx=ctx@entry=0x7fffdc027018, prim=prim@entry=0x7fffe621daa0, nr_prims=nr_prims@entry=1, ib=ib@entry=0x7fffe621da80, index_bounds_valid=index_bounds_valid@entry=0 '\000', min_index=min_index@entry=4294967295, max_index=max_index@entry=4294967295) at ../../../../src/mesa/vbo/vbo_exec_array.c:585 #5 0x7fffe6b8ff20 in vbo_validated_drawrangeelements (ctx=ctx@entry=0x7fffdc027018, mode=mode@entry=5, index_bounds_valid=index_bounds_valid@entry=0 '\000', start=start@entry=4294967295, end=end@entry=4294967295, count=count@entry=14, type=type@entry=5123, indices=indices@entry=0x7fffdc0c6bc0, basevertex=basevertex@entry=0, numInstances=numInstances@entry=1, baseInstance=baseInstance@entry=0) at ../../../../src/mesa/vbo/vbo_exec_array.c:1006 #6 0x7fffe6b90443 in vbo_exec_DrawElements (mode=5, count=14, type=5123, indices=0x7fffdc0c6bc0) at ../../../../src/mesa/vbo/vbo_exec_array.c:1156 #7 0x76744e0c in QSGDefaultRenderer::renderNodes (this=this@entry=0x7fffdc1cc670, nodes=optimized out, count=count@entry=40) at scenegraph/coreapi/qsgdefaultrenderer.cpp:536 #8 0x7674554c in QSGDefaultRenderer::render (this=0x7fffdc1cc670) at scenegraph/coreapi/qsgdefaultrenderer.cpp:281 #9 0x7674acc8 in QSGRenderer::renderScene (this=this@entry=0x7fffdc1cc670, bindable=...) at scenegraph/coreapi/qsgrenderer.cpp:271 #10 0x7674adf7 in QSGRenderer::renderScene (this=this@entry=0x7fffdc1cc670) at scenegraph/coreapi/qsgrenderer.cpp:229 #11 0x76754365 in QSGContext::renderNextFrame (this=optimized out, renderer=0x7fffdc1cc670, fboId=optimized out) at scenegraph/qsgcontext.cpp:270 #12 0x7678139a in QQuickWindowPrivate::renderSceneGraph (this=this@entry=0x662c10, size=...) at items/qquickwindow.cpp:349 #13 0x76863483 in QQuickRenderThreadSingleContextWindowManager::run (this=0x6634f0) at items/qquickthreadedwindowmanager.cpp:456 #14 0x77629186 in QThreadPrivate::start (arg=0x6634f0) at thread/qthread_unix.cpp:333 #15 0x75842182 in start_thread (arg=0x7fffe621e700) at pthread_create.c:312 #16 0x75b5312d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 When running some of the tests of unity8 where a few days ago it was fine. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1289243/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1289243] Re: Regression in trusty, i965_dri.so crashes
** Bug watch added: Red Hat Bugzilla #1123691 https://bugzilla.redhat.com/show_bug.cgi?id=1123691 ** Also affects: mesa (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=1123691 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1289243 Title: Regression in trusty, i965_dri.so crashes Status in Mesa: Unknown Status in mesa package in Ubuntu: Fix Released Status in mesa package in Debian: Unknown Status in mesa package in Fedora: Unknown Bug description: I am now getting crashes like (gdb) bt #0 0x7fffe6d74958 in get_stencil_miptree (irb=0x7fffdd870080) at ../../../../../../../src/mesa/drivers/dri/i965/brw_misc_state.c:257 #1 brw_workaround_depthstencil_alignment (brw=brw@entry=0x7fffdc027018, clear_mask=clear_mask@entry=0) at ../../../../../../../src/mesa/drivers/dri/i965/brw_misc_state.c:273 #2 0x7fffe6d3197d in brw_try_draw_prims (indirect=0x0, max_index=11, min_index=0, ib=0x7fffe621da80, nr_prims=1, prims=0x7fffe621daa0, arrays=0x7fffdc211030, ctx=0x7fffdc027018) at ../../../../../../../src/mesa/drivers/dri/i965/brw_draw.c:415 #3 brw_draw_prims (ctx=0x7fffdc027018, prims=0x7fffe621daa0, nr_prims=1, ib=0x7fffe621da80, index_bounds_valid=optimized out, min_index=0, max_index=11, unused_tfb_object=0x0, indirect=0x0) at ../../../../../../../src/mesa/drivers/dri/i965/brw_draw.c:569 #4 0x7fffe6b8ec03 in vbo_handle_primitive_restart (ctx=ctx@entry=0x7fffdc027018, prim=prim@entry=0x7fffe621daa0, nr_prims=nr_prims@entry=1, ib=ib@entry=0x7fffe621da80, index_bounds_valid=index_bounds_valid@entry=0 '\000', min_index=min_index@entry=4294967295, max_index=max_index@entry=4294967295) at ../../../../src/mesa/vbo/vbo_exec_array.c:585 #5 0x7fffe6b8ff20 in vbo_validated_drawrangeelements (ctx=ctx@entry=0x7fffdc027018, mode=mode@entry=5, index_bounds_valid=index_bounds_valid@entry=0 '\000', start=start@entry=4294967295, end=end@entry=4294967295, count=count@entry=14, type=type@entry=5123, indices=indices@entry=0x7fffdc0c6bc0, basevertex=basevertex@entry=0, numInstances=numInstances@entry=1, baseInstance=baseInstance@entry=0) at ../../../../src/mesa/vbo/vbo_exec_array.c:1006 #6 0x7fffe6b90443 in vbo_exec_DrawElements (mode=5, count=14, type=5123, indices=0x7fffdc0c6bc0) at ../../../../src/mesa/vbo/vbo_exec_array.c:1156 #7 0x76744e0c in QSGDefaultRenderer::renderNodes (this=this@entry=0x7fffdc1cc670, nodes=optimized out, count=count@entry=40) at scenegraph/coreapi/qsgdefaultrenderer.cpp:536 #8 0x7674554c in QSGDefaultRenderer::render (this=0x7fffdc1cc670) at scenegraph/coreapi/qsgdefaultrenderer.cpp:281 #9 0x7674acc8 in QSGRenderer::renderScene (this=this@entry=0x7fffdc1cc670, bindable=...) at scenegraph/coreapi/qsgrenderer.cpp:271 #10 0x7674adf7 in QSGRenderer::renderScene (this=this@entry=0x7fffdc1cc670) at scenegraph/coreapi/qsgrenderer.cpp:229 #11 0x76754365 in QSGContext::renderNextFrame (this=optimized out, renderer=0x7fffdc1cc670, fboId=optimized out) at scenegraph/qsgcontext.cpp:270 #12 0x7678139a in QQuickWindowPrivate::renderSceneGraph (this=this@entry=0x662c10, size=...) at items/qquickwindow.cpp:349 #13 0x76863483 in QQuickRenderThreadSingleContextWindowManager::run (this=0x6634f0) at items/qquickthreadedwindowmanager.cpp:456 #14 0x77629186 in QThreadPrivate::start (arg=0x6634f0) at thread/qthread_unix.cpp:333 #15 0x75842182 in start_thread (arg=0x7fffe621e700) at pthread_create.c:312 #16 0x75b5312d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 When running some of the tests of unity8 where a few days ago it was fine. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1289243/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1284296] Re: screen blanks (as if computer is off) after grub but only sometimes
*** This bug is a duplicate of bug 1307097 *** https://bugs.launchpad.net/bugs/1307097 ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** This bug has been marked a duplicate of bug 1307097 Blank / Black screens on boot half the time [R9 280X] -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1284296 Title: screen blanks (as if computer is off) after grub but only sometimes Status in “linux” package in Ubuntu: New Status in “xorg” package in Ubuntu: Invalid Bug description: First of all, I appologize if I filed this bug wrong, this is my first time. I am also not 100% sure it is Xorg related, but that seemed the most appropriate choice when I was anwsering the questions in the ubuntu-bug utility. $ cat /proc/version_signature Ubuntu 3.13.0-12.32-generic 3.13.4 $ lsb_release -rd Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 I originally tried to install 13.10 but had this intermittent blank screen problem so I hoped 14.04 would have a fix but it did not and now I'm troubleshooting in 14.04. The problem is intermittently after I select ubuntu from grub my screen will blank (no signal) as if my computer were off. Here is a link to my forum post discussing the problem and what I've done to try to resolve it http://ubuntuforums.org/showthread.php?t=2207624. I'm not sure if the computer has crashed or its simply not outputing video, but the only way to recover is to do a hard restart and cross my fingers that it wont happen next time. I know there are many bugs about blank screens, but this one seems to be unique in that it happens seemingly at random (race condition?). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4 Uname: Linux 3.13.0-12-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu5 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 CurrentDesktop: Unity Date: Mon Feb 24 11:57:32 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti XT [Radeon HD 7970/R9 280X] [1002:6798] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. HD 7970 Black Edition [1682:3213] InstallationDate: Installed on 2014-02-24 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140223) MachineType: To be filled by O.E.M. To be filled by O.E.M. PlymouthDebug: Error: [Errno 13] Permission denied: '/var/log/plymouth-debug.log' ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-12-generic root=UUID=ef026b95-15a8-431b-8c0c-01dff07c163c ro drm.debug=0x4 plymouth:debug SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1604 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1604:bd10/16/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52+git1402191830.c5de5a~gd~t version.libgl1-mesa-dri: libgl1-mesa-dri 10.2~git1402240730.73c78c~gd~t version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.2~git1402240730.73c78c~gd~t version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Feb 24 11:08:13 2014
[Touch-packages] [Bug 1312282] Re: wifi fails to connect after resuming from sleep
*** This bug is a duplicate of bug 1286552 *** https://bugs.launchpad.net/bugs/1286552 ** This bug has been marked a duplicate of bug 1286552 No wifi after suspend -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1312282 Title: wifi fails to connect after resuming from sleep Status in “wpa” package in Ubuntu: New Bug description: wifi will successfully connect after resuming from sleep if process wpa_supplicant is killed. problem began after upgrading from ubuntu 13.10 to 14.4. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: wpasupplicant 2.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 Date: Thu Apr 24 12:13:25 2014 ExecutablePath: /sbin/wpa_supplicant InstallationDate: Installed on 2013-09-17 (218 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) ProcEnviron: SourcePackage: wpa UpgradeStatus: Upgraded to trusty on 2014-04-18 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1312282/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 930962] Re: dhcp3-server reports many bad udp checksums to syslog using virtio NIC
** Also affects: dhcp3 (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717217 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/930962 Title: dhcp3-server reports many bad udp checksums to syslog using virtio NIC Status in “dhcp3” package in Ubuntu: Fix Released Status in “isc-dhcp” package in Ubuntu: Fix Released Status in “lxc” package in Ubuntu: Fix Released Status in “dhcp3” source package in Lucid: Fix Released Status in “isc-dhcp” source package in Precise: Fix Released Status in “isc-dhcp” source package in Quantal: Fix Released Status in “dhcp3” package in Debian: Unknown Bug description: == Rationale == Machines using virtio (kvm/xen) and running a dhcp server in a VM won't receive the proper udp checksums which leads to dhcpd dropping the packets. This patch forces the checksum to be calculated in such case. == Test case == 1) Install a dhcp server in a VM using kvm/xen 2) Make sure you don't have iptables re-calculating the checksums for you 3) Check that the requests go through as expected == Regression potential == Raring has had that fix for a while, so does redhat, so it looks pretty safe to me. --- original bug report --- Tested with dhcp3-server ver. 3.1.3-2ubuntu3.3 in Ubuntu 10.04.3 Server, x64. The DHCP server reports that UDP packets sent to it have bad checksums: Feb 11 06:57:18 ... dhcpd: 5 bad udp checksums in 5 packets Feb 11 06:58:22 ... dhcpd: last message repeated 7 times Feb 11 06:59:17 ... dhcpd: last message repeated 7 times The DHCP server host is a KVM virtual machine using a virtio-based virtual NIC. This problem has been reported for other distros using KVM and virtio: https://bugs.mageia.org/show_bug.cgi?id=1243 http://www.mail-archive.com/kvm@vger.kernel.org/msg41958.html - suggests using iptables to write in a checksum http://pkgs.fedoraproject.org/gitweb/?p=dhcp.git;a=blob;f=dhcp-4.2.2-xen-checksum.patch;h=038d346d726e131f1ab2579fe015a72b49733a0d;hb=HEAD - Fedora patch to dhcp to avoid this The simplest workaround is to change the virtual NIC type from virtio to Intel e1000 in KVM. Apparently this driver calculates checksums. But virtio is the default driver type. Thanks, Tim Miller Dyck To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dhcp3/+bug/930962/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1178841] Re: [regression] iwl3945 0000:04:00.0: Radio disabled by HW RF Kill switch - wpa_supplicant causes high cpu load -
** Tags added: trusty ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1178841 Title: [regression] iwl3945 :04:00.0: Radio disabled by HW RF Kill switch - wpa_supplicant causes high cpu load - Status in “linux” package in Ubuntu: Confirmed Status in “wpa” package in Ubuntu: Confirmed Bug description: On this notebook wifi sometimes doesn't work (wifi led not on, no wlan0 device), this issue was already present in 12.10, but aside from the non-working wifi, nothing bad™ happened in this condition. After updating to 13.04 however, dmesg gets spammed by repeated messages May 10 23:28:09 piBook kernel: [ 21.048718] iwl3945 :04:00.0: Radio disabled by HW RF Kill switch May 10 23:28:09 piBook kernel: [ 21.048842] iwl3945 :04:00.0: Radio disabled by HW RF Kill switch May 10 23:28:09 piBook kernel: [ 21.049636] iwl3945 :04:00.0: Radio disabled by HW RF Kill switch May 10 23:28:09 piBook kernel: [ 21.049763] iwl3945 :04:00.0: Radio disabled by HW RF Kill switch May 10 23:28:09 piBook kernel: [ 21.051079] iwl3945 :04:00.0: Radio disabled by HW RF Kill switch May 10 23:28:09 piBook kernel: [ 21.051378] iwl3945 :04:00.0: Radio disabled by HW RF Kill switch May 10 23:28:09 piBook kernel: [ 21.052369] iwl3945 :04:00.0: Radio disabled by HW RF Kill switch May 10 23:28:09 piBook kernel: [ 21.052499] iwl3945 :04:00.0: Radio disabled by HW RF Kill switch May 10 23:28:09 piBook kernel: [ 21.053323] iwl3945 :04:00.0: Radio disabled by HW RF Kill switch May 10 23:28:09 piBook kernel: [ 21.053452] iwl3945 :04:00.0: Radio disabled by HW RF Kill switch May 10 23:28:09 piBook kernel: [ 21.054252] iwl3945 :04:00.0: Radio disabled by HW RF Kill switch May 10 23:28:09 piBook kernel: [ 21.054374] iwl3945 :04:00.0: Radio disabled by HW RF Kill switch May 10 23:28:09 piBook kernel: [ 21.055140] iwl3945 :04:00.0: Radio disabled by HW RF Kill switch a side effect of this is that now wpa_supplicant causes high CPU load, rendering the device almost unusable. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: wpasupplicant 1.0-3ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Fri May 10 23:32:16 2013 InstallationDate: Installed on 2013-03-05 (66 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: Upgraded to raring on 2013-04-25 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1178841/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
