[Desktop-packages] [Bug 1665535] Re: WebRTC webcam support broken in firefox due to apparmor
This patch has been awaiting review from AppArmor Developers for a while now. Any suggestions on how to move it along? Thanks. -- 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/1665535 Title: WebRTC webcam support broken in firefox due to apparmor Status in firefox package in Ubuntu: New Bug description: In order to use sites that make use of WebRTC's webcam support, firefox needs access to the /dev/videoN device. When I applied the latest firefox update over the last week, apparmor was set to enforcing mode, which broke sites that use WebRTC, like https://talky.io. $ lsb_release -rd Description: Ubuntu 16.10 Release: 16.10 $ apt-cache policy firefox firefox: Installed: 51.0.1+build2-0ubuntu0.16.10.2 Candidate: 51.0.1+build2-0ubuntu0.16.10.2 Version table: *** 51.0.1+build2-0ubuntu0.16.10.2 500 500 http://us.archive.ubuntu.com/ubuntu yakkety-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu yakkety-security/main amd64 Packages 100 /var/lib/dpkg/status 49.0+build4-0ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1665535/+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 1665535] Re: WebRTC webcam support broken in firefox due to apparmor
** Branch unlinked: lp:~henn/firefox/fix-for-1665535 ** Branch linked: lp:~henn/apparmor/fix-for-1665535 -- 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/1665535 Title: WebRTC webcam support broken in firefox due to apparmor Status in firefox package in Ubuntu: New Bug description: In order to use sites that make use of WebRTC's webcam support, firefox needs access to the /dev/videoN device. When I applied the latest firefox update over the last week, apparmor was set to enforcing mode, which broke sites that use WebRTC, like https://talky.io. $ lsb_release -rd Description: Ubuntu 16.10 Release: 16.10 $ apt-cache policy firefox firefox: Installed: 51.0.1+build2-0ubuntu0.16.10.2 Candidate: 51.0.1+build2-0ubuntu0.16.10.2 Version table: *** 51.0.1+build2-0ubuntu0.16.10.2 500 500 http://us.archive.ubuntu.com/ubuntu yakkety-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu yakkety-security/main amd64 Packages 100 /var/lib/dpkg/status 49.0+build4-0ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1665535/+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 1665535] Re: WebRTC webcam support broken in firefox due to apparmor
** Branch linked: lp:~henn/firefox/fix-for-1665535 -- 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/1665535 Title: WebRTC webcam support broken in firefox due to apparmor Status in firefox package in Ubuntu: New Bug description: In order to use sites that make use of WebRTC's webcam support, firefox needs access to the /dev/videoN device. When I applied the latest firefox update over the last week, apparmor was set to enforcing mode, which broke sites that use WebRTC, like https://talky.io. $ lsb_release -rd Description: Ubuntu 16.10 Release: 16.10 $ apt-cache policy firefox firefox: Installed: 51.0.1+build2-0ubuntu0.16.10.2 Candidate: 51.0.1+build2-0ubuntu0.16.10.2 Version table: *** 51.0.1+build2-0ubuntu0.16.10.2 500 500 http://us.archive.ubuntu.com/ubuntu yakkety-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu yakkety-security/main amd64 Packages 100 /var/lib/dpkg/status 49.0+build4-0ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1665535/+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 1665535] [NEW] WebRTC webcam support broken in firefox due to apparmor
Public bug reported: In order to use sites that make use of WebRTC's webcam support, firefox needs access to the /dev/videoN device. When I applied the latest firefox update over the last week, apparmor was set to enforcing mode, which broke sites that use WebRTC, like https://talky.io. $ lsb_release -rd Description:Ubuntu 16.10 Release:16.10 $ apt-cache policy firefox firefox: Installed: 51.0.1+build2-0ubuntu0.16.10.2 Candidate: 51.0.1+build2-0ubuntu0.16.10.2 Version table: *** 51.0.1+build2-0ubuntu0.16.10.2 500 500 http://us.archive.ubuntu.com/ubuntu yakkety-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu yakkety-security/main amd64 Packages 100 /var/lib/dpkg/status 49.0+build4-0ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Package changed: apparmor (Ubuntu) => firefox (Ubuntu) -- 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/1665535 Title: WebRTC webcam support broken in firefox due to apparmor Status in firefox package in Ubuntu: New Bug description: In order to use sites that make use of WebRTC's webcam support, firefox needs access to the /dev/videoN device. When I applied the latest firefox update over the last week, apparmor was set to enforcing mode, which broke sites that use WebRTC, like https://talky.io. $ lsb_release -rd Description: Ubuntu 16.10 Release: 16.10 $ apt-cache policy firefox firefox: Installed: 51.0.1+build2-0ubuntu0.16.10.2 Candidate: 51.0.1+build2-0ubuntu0.16.10.2 Version table: *** 51.0.1+build2-0ubuntu0.16.10.2 500 500 http://us.archive.ubuntu.com/ubuntu yakkety-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu yakkety-security/main amd64 Packages 100 /var/lib/dpkg/status 49.0+build4-0ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1665535/+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 1575282] [NEW] NetworkManager applet (nm-applet) disappears after upgrading to xenial
Public bug reported: After upgrading from Ubuntu wily (15.10) to xenial (16.04, LTS), the NetworkManager control applet (nm-applet) ceased to show up. While running wily and even prior, I had modified /proc's "hidepid" argument to be 2, in accordance with hardening best practices in order to only allow users to see their own processes. Nm-applet was working just fine. Based on this Debian bug (https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=819808), I changed hidepid back to 0 (the default, which lets users see everyone's processes) and it's working again. Given that nm-applet was working just fine in wily and upgrading to xenial broke it, it seems like a regression. Wily version of network-manager: 1.0.4-0ubuntu5 Xenial version: 1.1.93-0ubuntu4 $ lsb_release -rd Description:Ubuntu 16.04 LTS Release:16.04 $ apt-cache policy network-manager network-manager: Installed: 1.1.93-0ubuntu4 Candidate: 1.1.93-0ubuntu4 Version table: *** 1.1.93-0ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status ** 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/1575282 Title: NetworkManager applet (nm-applet) disappears after upgrading to xenial Status in network-manager package in Ubuntu: New Bug description: After upgrading from Ubuntu wily (15.10) to xenial (16.04, LTS), the NetworkManager control applet (nm-applet) ceased to show up. While running wily and even prior, I had modified /proc's "hidepid" argument to be 2, in accordance with hardening best practices in order to only allow users to see their own processes. Nm-applet was working just fine. Based on this Debian bug (https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=819808), I changed hidepid back to 0 (the default, which lets users see everyone's processes) and it's working again. Given that nm-applet was working just fine in wily and upgrading to xenial broke it, it seems like a regression. Wily version of network-manager: 1.0.4-0ubuntu5 Xenial version: 1.1.93-0ubuntu4 $ lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.04 $ apt-cache policy network-manager network-manager: Installed: 1.1.93-0ubuntu4 Candidate: 1.1.93-0ubuntu4 Version table: *** 1.1.93-0ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1575282/+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 1510970] Re: Intel driver crashes on Ubuntu 15.10
FYI - I and others I know have hit this crash on at least 4 different machines using intel graphics after upgrading to 15.10. Please let me know if there's something I can do to assist in tracking down the bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1510970 Title: Intel driver crashes on Ubuntu 15.10 Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: The Xserver crashes randomly after upgrading to Ubuntu 15.10. Before the update everything was stable. The problem occured mostly while using Thunderbird but also once while using Firefox. The Xserver crashes and I'm logged out. It takes about 10 seconds until gdm fires up again and I'm able to login again. The last part of /var/log/Xorg.0.log says: [ 19778.602] (II) intel(0): resizing framebuffer to 3000x1920 [ 19778.617] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI2 using pipe 1, position (0, 0), rotation left, reflection none [ 19778.623] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI1 using pipe 0, position (1080, 406), rotation normal, reflection none [ 19798.610] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI1 using pipe 0, position (1080, 502), rotation normal, reflection none [ 20012.432] (EE) [ 20012.432] (EE) Backtrace: [ 20012.433] (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x55cab7c8f62e] [ 20012.433] (EE) 1: /usr/bin/X (0x55cab7adb000+0x1b8999) [0x55cab7c93999] [ 20012.433] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fe7c651d000+0x352f0) [0x7fe7c65522f0] [ 20012.433] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fe7c28f4000+0x24f18) [0x7fe7c2918f18] [ 20012.433] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fe7c28f4000+0x26157) [0x7fe7c291a157] [ 20012.433] (EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fe7c28f4000+0x2b4b1) [0x7fe7c291f4b1] [ 20012.433] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fe7c28f4000+0x804e4) [0x7fe7c29744e4] [ 20012.433] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fe7c28f4000+0x80e2c) [0x7fe7c2974e2c] [ 20012.433] (EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fe7c28f4000+0x82e1a) [0x7fe7c2976e1a] [ 20012.433] (EE) 9: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fe7c28f4000+0x4197c) [0x7fe7c293597c] [ 20012.433] (EE) 10: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fe7c28f4000+0x59906) [0x7fe7c294d906] [ 20012.433] (EE) 11: /usr/bin/X (_CallCallbacks+0x34) [0x55cab7b38654] [ 20012.433] (EE) 12: /usr/bin/X (WriteToClient+0x244) [0x55cab7c93274] [ 20012.433] (EE) 13: /usr/bin/X (WriteEventsToClient+0x1e2) [0x55cab7b3e502] [ 20012.433] (EE) 14: /usr/bin/X (0x55cab7adb000+0xf495a) [0x55cab7bcf95a] [ 20012.433] (EE) 15: /usr/bin/X (0x55cab7adb000+0xf5ef5) [0x55cab7bd0ef5] [ 20012.433] (EE) 16: /usr/bin/X (0x55cab7adb000+0x5818f) [0x55cab7b3318f] [ 20012.433] (EE) 17: /usr/bin/X (0x55cab7adb000+0x5c34b) [0x55cab7b3734b] [ 20012.433] (EE) 18: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x7fe7c653da40] [ 20012.433] (EE) 19: /usr/bin/X (_start+0x29) [0x55cab7b216c9] [ 20012.433] (EE) [ 20012.433] (EE) Segmentation fault at address 0x0 [ 20012.433] (EE) Fatal server error: [ 20012.433] (EE) Caught signal 11 (Segmentation fault). Server aborting [ 20012.433] (EE) [ 20012.433] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 20012.433] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 20012.433] (EE) [ 20012.433] (II) AIGLX: Suspending AIGLX clients for VT switch [ 20012.456] (EE) Server terminated with error (1). Closing log file. These parts of dmesg might be interesting: [1.661760] input: Logitech USB Keyboard as /devices/pci:00/:00:1a.0/usb3/3-1/3-1.6/3-1.6:1.1/0003:046D:C31C.0003/input/input8 [1.714657] hid-generic 0003:046D:C31C.0003: input,hidraw2: USB HID v1.10 Device [Logitech USB Keyboard] on usb-:00:1a.0-1.6/input1 [2.530993] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A [2.531006] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun [2.531018] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder B [2.531026] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder B FIFO underrun [2.561370] EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null) [2.586624] clocksource: Switched to clocksource tsc [2.652818] systemd[1]: Failed to insert module 'kdbus': Function not implemented [2.658814] systemd[1]: systemd 225 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP
