[Touch-packages] [Bug 1677239] Re: mir_demo_standalone_render_overlays fails to link
** Branch linked: lp:mir/0.26 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1677239 Title: mir_demo_standalone_render_overlays fails to link Status in Mir: Fix Committed Status in Mir 0.26 series: Fix Committed Status in mir package in Ubuntu: Triaged Bug description: https://mir-jenkins.ubuntu.com/job/build-2-binpkg- mir/arch=amd64,compiler=gcc,platform=mesa,release=zesty/4453/console 11:41:20 [ 52%] Linking CXX executable ../../../../bin/mir_demo_standalone_render_overlays.bin 11:41:20 cd /<>/mir-0.26.1+17.04.20170209.1+zesty4503bzr4124/obj-x86_64-linux-gnu/src/platforms/android/utils && /usr/bin/cmake -E cmake_link_script CMakeFiles/mir_demo_standalone_render_overlays.dir/link.txt --verbose=1 11:41:20 /usr/lib/ccache/c++ -g -O2 -fdebug-prefix-map=/<>/mir-0.26.1+17.04.20170209.1+zesty4503bzr4124=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -g -std=c++14 -Werror -Wall -fno-strict-aliasing -pedantic -Wnon-virtual-dtor -Wextra -fPIC -flto -ffat-lto-objects -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--as-needed -Wl,--no-undefined CMakeFiles/mir_demo_standalone_render_overlays.dir/render_overlays.cpp.o -o ../../../../bin/mir_demo_standalone_render_overlays.bin -rdynamic ../../../../lib/libmirplatform.so.16 ../../../../lib/libmircommon.so.7 ../../../capnproto/libmircapnproto.a -lkj -lcapnp ../../../../lib/libmircore.so.1 -lboost_date_time -lboost_system -lboost_program_options -lboost_filesystem -ldl -lEGL -lGLESv2 -lGLESv2 -L/lib/x86_64-linux-gnu -ludev -ludev 11:41:21 //usr/lib/x86_64-linux-gnu/libmirclient.so.9: undefined reference to `MirInputDeviceStateEvent::device_pressed_keys_for_index(unsigned long, unsigned long) const@MIR_COMMON_0.25_PRIVATE' 11:41:21 //usr/lib/x86_64-linux-gnu/libmirclient.so.9: undefined reference to `MirPointerEvent::set_x(float)@MIR_COMMON_0.25_PRIVATE' 11:41:21 //usr/lib/x86_64-linux-gnu/libmirclient.so.9: undefined reference to `MirTouchEvent::pressure(unsigned long) const@MIR_COMMON_0.25_PRIVATE' To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1677239/+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 1677239] Re: mir_demo_standalone_render_overlays fails to link
Fix committed to lp:mir/0.26 at revision 4053, scheduled for release in Mir 0.26.3 ** Changed in: mir/0.26 Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1677239 Title: mir_demo_standalone_render_overlays fails to link Status in Mir: Fix Committed Status in Mir 0.26 series: Fix Committed Status in mir package in Ubuntu: Triaged Bug description: https://mir-jenkins.ubuntu.com/job/build-2-binpkg- mir/arch=amd64,compiler=gcc,platform=mesa,release=zesty/4453/console 11:41:20 [ 52%] Linking CXX executable ../../../../bin/mir_demo_standalone_render_overlays.bin 11:41:20 cd /<>/mir-0.26.1+17.04.20170209.1+zesty4503bzr4124/obj-x86_64-linux-gnu/src/platforms/android/utils && /usr/bin/cmake -E cmake_link_script CMakeFiles/mir_demo_standalone_render_overlays.dir/link.txt --verbose=1 11:41:20 /usr/lib/ccache/c++ -g -O2 -fdebug-prefix-map=/<>/mir-0.26.1+17.04.20170209.1+zesty4503bzr4124=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -g -std=c++14 -Werror -Wall -fno-strict-aliasing -pedantic -Wnon-virtual-dtor -Wextra -fPIC -flto -ffat-lto-objects -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--as-needed -Wl,--no-undefined CMakeFiles/mir_demo_standalone_render_overlays.dir/render_overlays.cpp.o -o ../../../../bin/mir_demo_standalone_render_overlays.bin -rdynamic ../../../../lib/libmirplatform.so.16 ../../../../lib/libmircommon.so.7 ../../../capnproto/libmircapnproto.a -lkj -lcapnp ../../../../lib/libmircore.so.1 -lboost_date_time -lboost_system -lboost_program_options -lboost_filesystem -ldl -lEGL -lGLESv2 -lGLESv2 -L/lib/x86_64-linux-gnu -ludev -ludev 11:41:21 //usr/lib/x86_64-linux-gnu/libmirclient.so.9: undefined reference to `MirInputDeviceStateEvent::device_pressed_keys_for_index(unsigned long, unsigned long) const@MIR_COMMON_0.25_PRIVATE' 11:41:21 //usr/lib/x86_64-linux-gnu/libmirclient.so.9: undefined reference to `MirPointerEvent::set_x(float)@MIR_COMMON_0.25_PRIVATE' 11:41:21 //usr/lib/x86_64-linux-gnu/libmirclient.so.9: undefined reference to `MirTouchEvent::pressure(unsigned long) const@MIR_COMMON_0.25_PRIVATE' To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1677239/+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 1677455] [NEW] lose of sound
Public bug reported: loose of sound completely every update its becoming more difficult to restore ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-71.92-generic 4.4.49 Uname: Linux 4.4.0-71-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: i386 BootLog: [[0;32m OK [0m] Started LSB: Speech Dispatcher. [[0;32m OK [0m] Started LSB: Set the CPU Frequency Scaling governor to "ondemand". CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Mar 30 01:24:20 2017 DistUpgraded: 2016-11-11 10:42:31,618 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e22] (rev 03) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4 Series Chipset Integrated Graphics Controller [1043:8336] Subsystem: ASUSTeK Computer Inc. 4 Series Chipset Integrated Graphics Controller [1043:8336] InstallationDate: Installed on 2015-03-14 (746 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 (20130213) MachineType: ASUSTeK Computer INC. CM5570 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-71-generic root=UUID=b082e838-a6db-4326-b1f1-8b770239bbab ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-11-11 (138 days ago) dmi.bios.date: 08/11/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: CM5570 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0301:bd08/11/2009:svnASUSTeKComputerINC.:pnCM5570:pvrRevX.0x:rvnASUSTeKComputerINC.:rnCM5570:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: CM5570 dmi.product.version: Rev X.0x dmi.sys.vendor: ASUSTeK Computer INC. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Thu Mar 30 00:36:18 2017 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLite-On Technology Corp. USB Multimedia Keyboard KEYBOARD, id 8 inputLite-On Technology Corp. USB Multimedia Keyboard KEYBOARD, id 9 inputUSB Optical MouseMOUSE, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 ubuntu xenial -- 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/1677455 Title: lose of sound Status in xorg package in Ubuntu: New Bug description: loose of sound completely every update its becoming more difficult to restore ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-71.92-generic 4.4.49 Uname: Linux 4.4.0-71-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: i386 BootLog: [[0;32m OK [0m] Started LSB: Speech Dispatcher. [[0;32m OK [0m] Started LSB: Set the CPU Frequency Scaling governor to "ondemand". CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Mar 30 01:24:20 2017 DistUpgraded: 2016-11-11 10:42:31,618 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e22] (rev 03) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK
[Touch-packages] [Bug 1671121] Re: Deleting something from the history view breaks scrolling and the ability to click on some things
I explained 2) badly :) I was about to mean that use other component for delegate and put a button on it, so when you click it that button deletes the delegate. Just to rule out the ListItem itself. But the 1) already rules it out, so it is indeed the popover which does something bad. And probably it is related to the focus handling, as I do not see anything else the popover would affect the ListView functionalities. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1671121 Title: Deleting something from the history view breaks scrolling and the ability to click on some things Status in ubuntu-ui-toolkit package in Ubuntu: New Status in webbrowser-app package in Ubuntu: Confirmed Bug description: What happened: 1) Launch the webbrowser-app 2) Go to the history view 3) Scroll up/down and notice that the scrolling works 4) Right-click delete the first entry 5) Try to scroll up/down and notice that the scrolling doesn't work, notice you can't click on history entries, but you can select back in the header. Notice then you can't scroll the webviews or select any of the tabs. What I expected to happen: After step #4 for the scrolling/click focus to still function. $ lsb_release -rd Description: Ubuntu 16.04.2 LTS Release: 16.04 Xenial + overlay $ apt-cache policy webbrowser-app liboxideqt-qmlplugin webbrowser-app: Installed: 0.23+16.04.20170125.1-0ubuntu1 Candidate: 0.23+16.04.20170125.1-0ubuntu1 Version table: *** 0.23+16.04.20170125.1-0ubuntu1 500 500 http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 0.23+16.04.20161028-0ubuntu2 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 0.23+16.04.20160413-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages liboxideqt-qmlplugin: Installed: 1.20.4-0ubuntu0.16.04.1+overlay1 Candidate: 1.20.4-0ubuntu0.16.04.1+overlay1 Version table: *** 1.20.4-0ubuntu0.16.04.1+overlay1 500 500 http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 1.20.4-0ubuntu0.16.04.1 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 1.13.6-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1671121/+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 1676918] Re: blackscreen when trying to resume from suspend
Trying Kernel 4.11 since yesterday. So far no blackscreens but I think I should test it for a longer duration. Unfortunately Kernel 4.11 is no real solution for me because of another suspend/resume bug that as far as I can tell at the moment might exist since Kernel 4.9. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1676918 Title: blackscreen when trying to resume from suspend Status in gnome-power-manager package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: When trying to resume after suspending my Lenovo Yoga 3 11, sometimes the screen remains black. The power LED switches from blinking to continuous light like it should but nothing else happens. The system does not react to anything. I tried to find something in the logs, but at least kern.log syslog and xorg.log never have any entries from this event. This problem appeared with Ubuntu 16.04 and 17.04 with Xorg and Wayland. I'm currently testing Kernel 4.8 from the mainline ppa because of this other suspend resume bug, that appeared only with 17.04: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1676912 --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-03-24 (4 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) Package: systemd 232-19 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash Tags: zesty wayland-session Uname: Linux 4.8.17-040817-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1676918/+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 1676912] Re: Suspend - Freezing of tasks failed
I had some similar suspend/resume issues when trying mainline Kernels in 16.04. Every Kernel since 4.9 would cause terribly slow system after resuming. I will test Kernel 4.8 in next days to see if this problem is present there too. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1676912 Title: Suspend - Freezing of tasks failed Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Recently I replaced Ubuntu 16.04 on my Lenovo Yoga 3 11 with Ubuntu Gnome 17.04 and since then sometimes my Laptop won't suspend when I close the lid. The power led does not blink like it is supposed to do and when I open the Laptop the lockscreen appears but freezes after a short time, followed by a blackscreen until eventually it reappears and allows me to unlock it. After that certain application can not be started anymore and would freeze if they were running before. These include Chrome, Gedit and Gnome System Monitor for example. Also my Laptop will not connect to my WLAN until I restart it. In syslog I found the line: "Freezing of tasks failed after 20.005 seconds (18 tasks refusing to freeze, wq_busy=0):" According to syslog network-nanaeger whoopsie cups-browsed wpa-supplicant geoclue packagekitd several evolution-related processes goa-daemon gnome-software geary dropbox deja-dup-monitor are responsible. I tried disabling some of them, but it did not solve the problem. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: systemd 232-19 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Mar 28 16:27:34 2017 InstallationDate: Installed on 2017-03-24 (3 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) MachineType: LENOVO 80J8 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic.efi.signed root=UUID=8c63f102-527f-412a-bafe-7b9075ea6b56 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2015 dmi.bios.vendor: LENOVO dmi.bios.version: B8CN31WW(V2.09) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Paganini dmi.board.vendor: LENOVO dmi.board.version: 31900058 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 3 11 dmi.modalias: dmi:bvnLENOVO:bvrB8CN31WW(V2.09):bd07/15/2015:svnLENOVO:pn80J8:pvrLenovoYoga311:rvnLENOVO:rnPaganini:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga311: dmi.product.name: 80J8 dmi.product.version: Lenovo Yoga 3 11 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1676912/+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 1675357] Re: Mir sending key repeat events continually to nested shell after VT switch (causes Unity8 lockup for a while)
** Changed in: mir (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1675357 Title: Mir sending key repeat events continually to nested shell after VT switch (causes Unity8 lockup for a while) Status in Canonical System Image: In Progress Status in Mir: Fix Committed Status in Mir 0.26 series: Fix Committed Status in mir package in Ubuntu: Triaged Status in qtmir package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Invalid Bug description: Steps: * log in to unity8 * Ctrl+Alt+F* to a different vt, or log in to a different user session * go back to the unity8 vt Expected: * session is locked, but working Current: * unity8 starts spinning for a time proportional to the period it was inactive * if it was inactive long enough, it doesn't seem to recover at all It seems it's "catching up" in some way, maybe with input, maybe frames. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: unity8 8.15+17.04.20170321-0ubuntu1 [origin: LP-PPA-ci-train-ppa-service-2555] ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1 Uname: Linux 4.10.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Thu Mar 23 11:36:39 2017 InstallationDate: Installed on 2016-05-06 (320 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: unity8 UpgradeStatus: Upgraded to zesty on 2016-11-22 (120 days ago) Causes: The mir::input::KeyRepeatDispatcher is running inside the nested mirserver even though there is another instance running inside the host server. A few months ago qtmir used to replace the key repeater by replacing mirs dispatcher. And key repeat is not disabled within the nested server. So both the host and the nested server are producing repeat events. Now due to a logic error inside mirserver the key repeat dispatcher is not hooked up to the input device hub when running inside the nested server. The input device hub would tell the key repeater when devices get removed - i.e. due to vt switching. So it never notices that the devices go away continues to produce those events indefinitely. This applies to all currently pressed buttons. I.e. you can open an edit field and press 'w' while simultaneously pressing Ctrl+Alt+FX to switch to another VT. On return 'w' will be repeated indefinitely. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1675357/+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 1605327] Re: Opening terminal-app does not focus on password prompt
If it was fixed in upstream ubuntu-terminal-app then the fix still isn't in zesty. Zesty's terminal app is still: 0.7.218ubuntu2 release (main) 2016-10-18 ** Changed in: ubuntu-terminal-app (Ubuntu) Status: Invalid => Triaged ** Changed in: ubuntu-terminal-app (Ubuntu) Importance: Undecided => High ** Information type changed from Public to Public Security ** Tags added: unity8-desktop ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1605327 Title: Opening terminal-app does not focus on password prompt Status in Canonical System Image: New Status in Ubuntu Terminal App: Fix Released Status in ubuntu-terminal-app package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Invalid Status in unity8-desktop-session package in Ubuntu: Invalid Bug description: When I open the terminal app, I get asked for my password. If I just start typing, the password gets written in the terminal bash and not in the correct popup prompt. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1605327/+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 1672401] Re: Screen is black for too long during login to Unity8
As a prerequisite to removing Mir's initial black frame, we would want to modify mir-demos to ensure they (the demo servers) actively paint something on start-up. Otherwise you get the situation where you're looking at an old frame (VT?) indefinitely until a client is started. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1672401 Title: Screen is black for too long during login to Unity8 Status in Canonical System Image: Triaged Status in Mir: Triaged Status in Unity System Compositor: Confirmed Status in unity-system-compositor package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Triaged Bug description: This makes me worry there's something gone wrong on every login. It's only this slow on a cold boot. It's somewhat faster on a second login. It'd be nice for there to be something like: * Splash screen * Progress bar * User's wallpaper (blurred?) during this time. Maybe it's faster on bare metal, but I'm waiting a while in a Qemu VM. == Note == The experience might differ depending on whether you use unity-greeter (X11-based, default in 17.04) or unity8-greeter (not installed by default yet), which is better suited for this. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672401/+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 1672401] Re: Screen is black for too long during login to Unity8
I was thinking about this bug last night. It occurred to me the black screen is probably Mir's mesa-kms driver's first frame that it flips on start-up. As far as Mir is concerned this is a very low-severity issue since the shell should then render a proper frame 16ms later. However since Unity8 is taking several seconds to render a "proper" frame perhaps we need to change the start-up order... Presently: 1. User enters password successfully 2. unity-system-compositor starts and Mir's mesa-kms driver flips a black frame. 3. unity8 starts and Mir's mesa-kms driver flips another black frame that USC probably displays. 4. (several seconds later) unity8 has a proper frame ready and displays that. If we got rid of the dummy black frame from Mir (and we need to anyway since that is us hardcoding a dependency on the GL renderer in the driver) then the best case outcome from that might be several seconds of a frozen login screen before Unity8 appears. I'm not sure that's really any better than blackness. It might be better for Unity8 to take responsibility for this and flip some splash screen immediately on startup for the user to see that everything is OK while it compiles QML and whatever. Also nice would be for USC to display a spinner while Unity8 is not ready (hasn't displayed any frames). However we can't do that right now while Mir is inserting a black frame of its own, which would make USC think Unity8 is immediately ready. ** Also affects: mir Importance: Undecided Status: New ** Changed in: mir Status: New => Triaged ** Changed in: mir Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1672401 Title: Screen is black for too long during login to Unity8 Status in Canonical System Image: Triaged Status in Mir: Triaged Status in Unity System Compositor: Confirmed Status in unity-system-compositor package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Triaged Bug description: This makes me worry there's something gone wrong on every login. It's only this slow on a cold boot. It's somewhat faster on a second login. It'd be nice for there to be something like: * Splash screen * Progress bar * User's wallpaper (blurred?) during this time. Maybe it's faster on bare metal, but I'm waiting a while in a Qemu VM. == Note == The experience might differ depending on whether you use unity-greeter (X11-based, default in 17.04) or unity8-greeter (not installed by default yet), which is better suited for this. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672401/+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 1553328] Re: Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors, webbrowser-app or system settings
** Also affects: qtubuntu (Ubuntu) Importance: Undecided Status: New ** Changed in: qtubuntu (Ubuntu) Status: New => In Progress ** Changed in: qtubuntu (Ubuntu) Assignee: (unassigned) => Gerry Boland (gerboland) ** Changed in: qtmir (Ubuntu) Assignee: (unassigned) => Gerry Boland (gerboland) ** Changed in: qtmir (Ubuntu) Status: Confirmed => In Progress ** Changed in: qtubuntu (Ubuntu) Importance: Undecided => High ** Changed in: qtmir (Ubuntu) Importance: Medium => High ** Changed in: mir (Ubuntu) Importance: Critical => High ** Changed in: mir (Ubuntu) Status: Invalid => Triaged ** Changed in: unity-system-compositor Importance: Medium => High ** Changed in: unity-system-compositor Status: Confirmed => Triaged ** Changed in: mir Importance: Medium => High ** Changed in: mir Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1553328 Title: Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors, webbrowser-app or system settings Status in Canonical System Image: Triaged Status in Mir: Triaged Status in Nouveau Xorg driver: Unknown Status in Unity System Compositor: Triaged Status in libdrm package in Ubuntu: Triaged Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Triaged Status in qtmir package in Ubuntu: In Progress Status in qtubuntu package in Ubuntu: In Progress Bug description: Unit8 froze up while I was trying to open system settings. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: unity8 8.11+16.04.20160216.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3 Uname: Linux 4.4.0-9-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Fri Mar 4 19:12:54 2016 ExecutablePath: /usr/bin/unity8 InstallationDate: Installed on 2015-05-10 (299 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcCmdline: unity8 SegvAnalysis: Segfault happened at: 0x7f58d568706c:mov0x8(%rsi),%edx PC (0x7f58d568706c) ok source "0x8(%rsi)" (0x0008) not located in a known VMA region (needed readable region)! destination "%edx" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity8 StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 Title: unity8 crashed with SIGSEGV UpgradeStatus: Upgraded to xenial on 2015-11-07 (118 days ago) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1553328/+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 1667825] Re: Requesting Cherry Pick: dns/resolved: consider configuration from unmanaged devices
Well actually I'm lost now. The code I obtain with apt-get source network-manager is different from the one I obtain with bzr branch lp :network-manager. The latter is supposed to be the most current way of getting sources, but it doesn't have the file nm-dns-systemd-resolved.c. Any ideas? -- 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/1667825 Title: Requesting Cherry Pick: dns/resolved: consider configuration from unmanaged devices Status in network-manager package in Ubuntu: Confirmed Bug description: Please forgive me if this is not the proper channel to request a cherry-pick. I'm currently experiencing this issue on Ubuntu 17.04 using the network-manager-l2tp plugin. The Network Manager team recently patched an issue that breaks DNS resolution for certain VPN connections due to the PPP/TUN interface being unmanaged. The patch that corrects this is 913896721d7c7c65f7e4a24e8c0d9d275a9dfbaa. For more information, please see the upstream bug report: https://bugzilla.gnome.org/show_bug.cgi?id=779087 Please let me know if I need to submit additional information or if this is the incorrect channel to request this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1667825/+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 1665874] Re: messaging-app crashed with SIGABRT in qt_message_fatal()
** Information type changed from Private to Public ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Tags added: unity8-desktop -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1665874 Title: messaging-app crashed with SIGABRT in qt_message_fatal() Status in Canonical System Image: New Status in messaging-app package in Ubuntu: Confirmed Bug description: messaging-app crashed with SIGABRT in QMessageLogger::fatal() ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: messaging-app 0.1+17.04.20161130-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8 Uname: Linux 4.10.0-8-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity:Unity8 Date: Thu Feb 16 13:50:05 2017 ExecutablePath: /usr/bin/messaging-app InstallationDate: Installed on 2016-12-12 (67 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161108) ProcCmdline: messaging-app Signal: 6 SourcePackage: messaging-app StacktraceTop: QMessageLogger::fatal(char const*, ...) const () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 QSGRenderLoop::handleContextCreationFailure(QQuickWindow*, bool) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 QWindow::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 Title: messaging-app crashed with SIGABRT in QMessageLogger::fatal() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1665874/+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 1677187] Re: Applications aren't given input when launched from the launcher or the app drawer
*** This bug is a duplicate of bug 1605327 *** https://bugs.launchpad.net/bugs/1605327 Florian marked it fixed two days ago...(?) See bug 1605327 ** This bug has been marked a duplicate of bug 1605327 Opening terminal-app does not focus on password prompt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1677187 Title: Applications aren't given input when launched from the launcher or the app drawer Status in Canonical System Image: Triaged Status in unity8 package in Ubuntu: Triaged Bug description: Steps to reproduce: 1. Open the app drawer and type "terminal" 2. Select the ubuntu-terminal-app 3. The terminal will launch and the window style will make it look as though it has focus. It will display a password input prompt. 4. Type "Hello" 5. Open the app drawer again and see the input went to the search bar instead Expected result: The terminal password prompt should display "*" Actual result: The app drawer search bar will receive this input instead (despite not being visible) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1677187/+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 1677239] Re: mir_demo_standalone_render_overlays fails to link
** Also affects: mir/0.26 Importance: Undecided Status: New ** Changed in: mir/0.26 Milestone: None => 0.26.3 ** Changed in: mir/0.26 Assignee: (unassigned) => Alan Griffiths (alan-griffiths) ** Changed in: mir/0.26 Importance: Undecided => Critical ** Changed in: mir/0.26 Status: New => Triaged ** Also affects: mir (Ubuntu) Importance: Undecided Status: New ** Changed in: mir (Ubuntu) Status: New => Triaged ** Changed in: mir (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1677239 Title: mir_demo_standalone_render_overlays fails to link Status in Mir: Fix Committed Status in Mir 0.26 series: Triaged Status in mir package in Ubuntu: Triaged Bug description: https://mir-jenkins.ubuntu.com/job/build-2-binpkg- mir/arch=amd64,compiler=gcc,platform=mesa,release=zesty/4453/console 11:41:20 [ 52%] Linking CXX executable ../../../../bin/mir_demo_standalone_render_overlays.bin 11:41:20 cd /<>/mir-0.26.1+17.04.20170209.1+zesty4503bzr4124/obj-x86_64-linux-gnu/src/platforms/android/utils && /usr/bin/cmake -E cmake_link_script CMakeFiles/mir_demo_standalone_render_overlays.dir/link.txt --verbose=1 11:41:20 /usr/lib/ccache/c++ -g -O2 -fdebug-prefix-map=/<>/mir-0.26.1+17.04.20170209.1+zesty4503bzr4124=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -g -std=c++14 -Werror -Wall -fno-strict-aliasing -pedantic -Wnon-virtual-dtor -Wextra -fPIC -flto -ffat-lto-objects -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--as-needed -Wl,--no-undefined CMakeFiles/mir_demo_standalone_render_overlays.dir/render_overlays.cpp.o -o ../../../../bin/mir_demo_standalone_render_overlays.bin -rdynamic ../../../../lib/libmirplatform.so.16 ../../../../lib/libmircommon.so.7 ../../../capnproto/libmircapnproto.a -lkj -lcapnp ../../../../lib/libmircore.so.1 -lboost_date_time -lboost_system -lboost_program_options -lboost_filesystem -ldl -lEGL -lGLESv2 -lGLESv2 -L/lib/x86_64-linux-gnu -ludev -ludev 11:41:21 //usr/lib/x86_64-linux-gnu/libmirclient.so.9: undefined reference to `MirInputDeviceStateEvent::device_pressed_keys_for_index(unsigned long, unsigned long) const@MIR_COMMON_0.25_PRIVATE' 11:41:21 //usr/lib/x86_64-linux-gnu/libmirclient.so.9: undefined reference to `MirPointerEvent::set_x(float)@MIR_COMMON_0.25_PRIVATE' 11:41:21 //usr/lib/x86_64-linux-gnu/libmirclient.so.9: undefined reference to `MirTouchEvent::pressure(unsigned long) const@MIR_COMMON_0.25_PRIVATE' To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1677239/+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 1672444] Re: Negative number of tabs at left
** Tags added: unity8-desktop ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Summary changed: - Negative number of tabs at left + Negative number of tabs at left of the browser ** Changed in: canonical-devices-system-image Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1672444 Title: Negative number of tabs at left of the browser Status in Canonical System Image: Confirmed Status in webbrowser-app package in Ubuntu: Confirmed Bug description: I am not able to reproduce it. I opened the webbrowser-app after updating the silo to the new build, and maximized it. After minimizing it again, I spotted the negative number of hidden tabs at left. Not sure what steps do trigger this. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672444/+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 1677430] Re: Titlebar text shifts (changes length) when activating/deactivating a window
Please use bold for all the window titles. It would fix a couple of bugs! :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1677430 Title: Titlebar text shifts (changes length) when activating/deactivating a window Status in Canonical System Image: New Status in unity8 package in Ubuntu: New Bug description: Titlebar text shifts (changes length) when activating/deactivating a window. Seems to be because we're jumping between a bold and regular font. Ideally it should be the same font, just a different colour. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1677430/+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 1677258] Re: keyboard navigation from url search should populate field
** Tags added: unity8-desktop -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1677258 Title: keyboard navigation from url search should populate field Status in Canonical System Image: New Status in webbrowser-app package in Ubuntu: Confirmed Bug description: when searching from the url field, we should populate the url field with the search results when using arrow key to navigate the result list. For example: 1) type pastebin.ub 2) results show me http://pastebin.ubuntu.com/43434343434 http://pastebin.ubuntu.com/23232323232 3) use the arrow keys to navigate Expected results: the url field should be populated with the entry that has been navigated to. The enter button should not be executed so user can modify the url that is in the field Actual results: nothing is populated in the url field until a search result is selected, and this executes the search giving user no opportunity to edit the url string To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1677258/+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 1677259] Re: [regression] Search string not replaced in app drawer after Super+A
** Tags added: unity8-desktop -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1677259 Title: [regression] Search string not replaced in app drawer after Super+A Status in Canonical System Image: In Progress Status in unity8 package in Ubuntu: In Progress Bug description: Steps: * open the app drawer * type "foo" * close the app drawer * press Super+A to open the app drawer * type "bar" Expected: * search term is "bar" Current: * search term is "foobar" ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: unity8 8.15+17.04.20170321-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Wed Mar 29 16:00:37 2017 InstallationDate: Installed on 2016-05-06 (326 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: unity8 UpgradeStatus: Upgraded to zesty on 2016-11-22 (127 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1677259/+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 1677430] [NEW] Titlebar text shifts (changes length) when activating/deactivating a window
Public bug reported: Titlebar text shifts (changes length) when activating/deactivating a window. Seems to be because we're jumping between a bold and regular font. Ideally it should be the same font, just a different colour. ** Affects: canonical-devices-system-image Importance: Undecided Status: New ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Tags: unity8-desktop visual-quality ** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Tags added: unity8-desktop -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1677430 Title: Titlebar text shifts (changes length) when activating/deactivating a window Status in Canonical System Image: New Status in unity8 package in Ubuntu: New Bug description: Titlebar text shifts (changes length) when activating/deactivating a window. Seems to be because we're jumping between a bold and regular font. Ideally it should be the same font, just a different colour. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1677430/+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 1667825] Re: Requesting Cherry Pick: dns/resolved: consider configuration from unmanaged devices
I tried applying the patch in the version of network-manager that comes in Ubuntu 17.04 (1.4.4), and it didn't seem to work. In this version, the file nm-dns-systemd-resolved.c is in src/dns-manager instead of src/dns, but I assume it is the same. Daniel, did it work for you? -- 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/1667825 Title: Requesting Cherry Pick: dns/resolved: consider configuration from unmanaged devices Status in network-manager package in Ubuntu: Confirmed Bug description: Please forgive me if this is not the proper channel to request a cherry-pick. I'm currently experiencing this issue on Ubuntu 17.04 using the network-manager-l2tp plugin. The Network Manager team recently patched an issue that breaks DNS resolution for certain VPN connections due to the PPP/TUN interface being unmanaged. The patch that corrects this is 913896721d7c7c65f7e4a24e8c0d9d275a9dfbaa. For more information, please see the upstream bug report: https://bugzilla.gnome.org/show_bug.cgi?id=779087 Please let me know if I need to submit additional information or if this is the incorrect channel to request this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1667825/+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 1677260] Re: bad white flicker when switching tabs
Confirmed the webbrowser-app's whole window turns *white* when switching tabs sometimes. ** Tags added: unity8-desktop ** Tags added: visual-quality ** Changed in: canonical-devices-system-image Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1677260 Title: bad white flicker when switching tabs Status in Canonical System Image: Confirmed Status in webbrowser-app package in Ubuntu: Confirmed Bug description: when switching tabs from that are shown from a previous session, there is a bad white flicker/redraw before the new tab is shown. The transition should be smooth without any kind of flicker To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1677260/+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 1677260] Re: bad white flicker when switching tabs
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: webbrowser-app (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1677260 Title: bad white flicker when switching tabs Status in Canonical System Image: Confirmed Status in webbrowser-app package in Ubuntu: Confirmed Bug description: when switching tabs from that are shown from a previous session, there is a bad white flicker/redraw before the new tab is shown. The transition should be smooth without any kind of flicker To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1677260/+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 1677260] Re: bad white flicker when switching tabs
Confirmed the webbrowser-app's whole window turns while when switching tabs sometimes. Although please also verify you don't have an 'Xmir' process running which would be a whole different issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1677260 Title: bad white flicker when switching tabs Status in Canonical System Image: Confirmed Status in webbrowser-app package in Ubuntu: Confirmed Bug description: when switching tabs from that are shown from a previous session, there is a bad white flicker/redraw before the new tab is shown. The transition should be smooth without any kind of flicker To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1677260/+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 769314] Re: System bell completely silent because PulseAudio sample file undefined by default
This bug was fixed in the package pulseaudio - 1:10.0-1ubuntu2 --- pulseaudio (1:10.0-1ubuntu2) zesty; urgency=medium * debian/patches/0006-load-module-x11-bell.patch: - Upload bell.ogg sample via pactl for module-x11-bell. Original patch by Daniel Hahler. (LP: #769314) * debian/control: - Add ubuntu-sounds to Suggests list, since it ships the sound used by default in above patch now. -- Michael Terry Wed, 29 Mar 2017 14:24:19 -0400 ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/769314 Title: System bell completely silent because PulseAudio sample file undefined by default Status in Unity: Invalid Status in gnome-media package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Fix Released Status in unity package in Ubuntu: Invalid Bug description: Binary package hint: unity This bug is about problems using the system bell in Unity or another Compiz-based environment. For problems using the system bell in Ubuntu Classic/Metacity or another Metacity-based environment, please see bug #486154. The system bell (that beep when you backspace on an empty line on a terminal, i.e.) is badly broken using the Unity environment in the Natty beta 2. By default, no sound is produced, and several misconfigurations make it difficult to produce sound either from the PC speaker or Pulse Audio's module-x11-bell. Not knowing what the desired behavior is, I can't say exactly what needs to be fixed. But the combination of the following issues makes the system quite obviously broken. 1) pcskpr is blacklisted. The pcspkr module is necessary for the PC speaker to produce sound. It is blacklisted, so regular users cannot turn the bell on. It would be nice for this to be fixed, but the attitudes displayed in #77010 suggest that it won't be. Nonetheless, I note it here because it interacts with some of the following. 2) The X bell volume is set to 0. (no more true in xenial) As reported by `xset q`, the bell volume is 0 when Unity is started. Both the PC speaker and module-x11-bell respect this setting, so the volume must be turned up (with `xset b on` or `xset b 100`) for either to work. Since both the PC speaker and module-x11-bell are disabled by default, this setting only serves to frustrate attempts to turn them on; it never prevents unwanted sound. 3) module-x11-bell is loaded by /usr/bin/start-pulseaudio-x11 This is a system file, not a user file, so users cannot decide whether they want this module loaded or not. They could write a script to unload the module at login (and hope the module number doesn't vary between boots), but it would be much cleaner to have the modules loaded from a user file, possibly with defaults if the user file doesn't exist. 4) Sample bell.ogg is not loaded. When module-x11-bell is loaded, it is told to use the sample bell.ogg. But no sample is loaded into Pulse Audio. Thus, module-x11-bell traps system bell events (keeping them from going to the PC speaker) without producing any sound. If module-x11-bell is loaded, the sample it calls on should be loaded as well. (To fix this, run `pactl upload-sample /usr/share/sounds/ubuntu/stereo/bell.ogg bell.ogg`.) 5) gnome-volume-control doesn't. The "Sound Effects" tab of gnome-volume-control offers to set the volume and sound for system bell events, but these have no effect. This is because gnome-volume-control is trying to control system bells through metacity. Ideally, it should be rewritten to control module-x11-bell instead, but a temporary fix could be to simply disable this tab. 6) System bell settings don't transfer to the Ubuntu Classic environment. Because that is using metacity, which has it's own set of problems. See bug #486154. This has been from testing in a VM (virtualbox), but all of these behaviors have also been seen in Compiz in various previous versions of Ubuntu running on various hardware. I have reported this bug against several components, as it is really an integration issue. The eventual fix may not involve your component, but please do not mark this bug as invalid until we have at least a roadmap for fixing it. Otherwise, I fear responsibility will be passed from component to component without anything being fixed. Rationales: Unity - As the overarching environment, Unity should be responsible for getting everything integrated. Additionally, some of the problems relate to session startup settings. Pulse Audio - module-x11-bell is not loaded intelligently or correctly. Gnome Media - Own gnome-volume-control. Versions (but note the same behavior has been seen in many earlier versions): unity: 3.8.10-0ubuntu2 pulseaudio: 1:0.9.22+stable-qu
[Touch-packages] [Bug 1673557] Re: /proc/cpuinfo should be collected
This bug was fixed in the package whoopsie - 0.2.55 --- whoopsie (0.2.55) zesty; urgency=medium * src/whoopsie.c: Add ProcCpuinfoMinimal which can be larger than 1KB to the list of accepted fields. (LP: #1673557) -- Brian Murray Wed, 29 Mar 2017 12:41:31 -0700 ** Changed in: whoopsie (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1673557 Title: /proc/cpuinfo should be collected Status in apport package in Ubuntu: In Progress Status in whoopsie package in Ubuntu: Fix Released Bug description: apport does not currently collect data from /proc/cpuinfo and this would be useful to determine how many users can only run the i386 version of Ubuntu. The general Ubuntu hook, possibly add_kernel_info() could be used, should be modified such that the contents of /proc/cpuinfo are gathered. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1673557/+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 1577168] Re: Browser hangs Ubuntu 16.04
I have the same problem for Trusty Tahr 14.04.5 32bits, for the last six months (or maybe more). How to fix this bug ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1577168 Title: Browser hangs Ubuntu 16.04 Status in webbrowser-app package in Ubuntu: Invalid Bug description: When I activate Browser or click on Amazon button (which activates Browser), Ubuntu 16.04 hangs. This occurrence should not happen. An exception to this problem is that the mouse pointer is movable initially. In the extreme case, the mouse pointer hangs also. This problem does not occur when activating Firefox or Chromium. Occurs in a freshly installed Ubuntu 16.04 system. Description: Ubuntu 16.04 LTS Release: 16.04 N: Unable to locate package pkgname To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1577168/+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 1677175] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1677175/+attachment/4850129/+files/ProcEnviron.txt -- 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/1677175 Title: network-manager 1.2.6 won't connect to vpn and displays false connected message Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: I have been having a rather serious and incredibly annoying problem on the updated version of network-manager v1.2.6 on Ubuntu 16.04.2 LTS. Trying to manually connect to my VPN provider using openvpn through the network manager fails literally any time except bootup. Every godforsaken time. Waking the computer from suspend results in the network manager 'reconnecting' but no actual internet connection. Restarting the network manager using 'sudo service network-manager restart' sometimes doesn't work at all and I actually have to reboot the computer for it to connect to the internet. Despite the icon showing that I'm connected, in actuality I have no internet connection and cannot load any web pages. The critical thing is that this issue isn't present at all on v1.2.2, which I have downgraded to and used 'apt-mark hold' to keep it in place. I'm disappointed that the newer default version is so unstable. Any insight or confirmation of this issue would be appreciated. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes InstallationDate: Installed on 2017-03-19 (10 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Package: network-manager 1.2.2-0ubuntu0.16.04.4 PackageArchitecture: amd64 Tags: xenial Uname: Linux 4.9.16 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677175/+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 1677175] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1677175/+attachment/4850128/+files/JournalErrors.txt -- 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/1677175 Title: network-manager 1.2.6 won't connect to vpn and displays false connected message Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: I have been having a rather serious and incredibly annoying problem on the updated version of network-manager v1.2.6 on Ubuntu 16.04.2 LTS. Trying to manually connect to my VPN provider using openvpn through the network manager fails literally any time except bootup. Every godforsaken time. Waking the computer from suspend results in the network manager 'reconnecting' but no actual internet connection. Restarting the network manager using 'sudo service network-manager restart' sometimes doesn't work at all and I actually have to reboot the computer for it to connect to the internet. Despite the icon showing that I'm connected, in actuality I have no internet connection and cannot load any web pages. The critical thing is that this issue isn't present at all on v1.2.2, which I have downgraded to and used 'apt-mark hold' to keep it in place. I'm disappointed that the newer default version is so unstable. Any insight or confirmation of this issue would be appreciated. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes InstallationDate: Installed on 2017-03-19 (10 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Package: network-manager 1.2.2-0ubuntu0.16.04.4 PackageArchitecture: amd64 Tags: xenial Uname: Linux 4.9.16 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677175/+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 1677175] Re: network-manager 1.2.6 won't connect to vpn and displays false connected message
apport information ** Tags added: apport-collected xenial ** Description changed: I have been having a rather serious and incredibly annoying problem on the updated version of network-manager v1.2.6 on Ubuntu 16.04.2 LTS. Trying to manually connect to my VPN provider using openvpn through the network manager fails literally any time except bootup. Every godforsaken time. Waking the computer from suspend results in the network manager 'reconnecting' but no actual internet connection. Restarting the network manager using 'sudo service network-manager restart' sometimes doesn't work at all and I actually have to reboot the computer for it to connect to the internet. Despite the icon showing that I'm connected, in actuality I have no internet connection and cannot load any web pages. The critical thing is that this issue isn't present at all on v1.2.2, which I have downgraded to and used 'apt-mark hold' to keep it in place. I'm disappointed that the newer default version is so unstable. Any insight or confirmation of this issue would be appreciated. + --- + ApportVersion: 2.20.1-0ubuntu2.5 + Architecture: amd64 + CurrentDesktop: Unity + DistroRelease: Ubuntu 16.04 + EcryptfsInUse: Yes + InstallationDate: Installed on 2017-03-19 (10 days ago) + InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) + Package: network-manager 1.2.2-0ubuntu0.16.04.4 + PackageArchitecture: amd64 + Tags: xenial + Uname: Linux 4.9.16 x86_64 + UnreportableReason: The running kernel is not an Ubuntu kernel + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1677175/+attachment/4850127/+files/Dependencies.txt -- 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/1677175 Title: network-manager 1.2.6 won't connect to vpn and displays false connected message Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: I have been having a rather serious and incredibly annoying problem on the updated version of network-manager v1.2.6 on Ubuntu 16.04.2 LTS. Trying to manually connect to my VPN provider using openvpn through the network manager fails literally any time except bootup. Every godforsaken time. Waking the computer from suspend results in the network manager 'reconnecting' but no actual internet connection. Restarting the network manager using 'sudo service network-manager restart' sometimes doesn't work at all and I actually have to reboot the computer for it to connect to the internet. Despite the icon showing that I'm connected, in actuality I have no internet connection and cannot load any web pages. The critical thing is that this issue isn't present at all on v1.2.2, which I have downgraded to and used 'apt-mark hold' to keep it in place. I'm disappointed that the newer default version is so unstable. Any insight or confirmation of this issue would be appreciated. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes InstallationDate: Installed on 2017-03-19 (10 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Package: network-manager 1.2.2-0ubuntu0.16.04.4 PackageArchitecture: amd64 Tags: xenial Uname: Linux 4.9.16 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677175/+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 1648143] Re: tor in lxd: apparmor="DENIED" operation="change_onexec" namespace="root//CONTAINERNAME_" profile="unconfined" name="system_tor"
00:27 smb: is https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1648143/comments/26 correct? Wrong bug? 00:28 yeah, looked odd to me to, I don't see the link between that security fix and this bug 00:29 Let's reopen for now. If it's wrong, smb can re-close it perhaps? ** Changed in: linux (Ubuntu Yakkety) Status: Fix Released => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1648143 Title: tor in lxd: apparmor="DENIED" operation="change_onexec" namespace="root//CONTAINERNAME_" profile="unconfined" name="system_tor" Status in apparmor package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Released Status in tor package in Ubuntu: Invalid Status in apparmor source package in Xenial: New Status in linux source package in Xenial: Triaged Status in tor source package in Xenial: Invalid Status in apparmor source package in Yakkety: New Status in linux source package in Yakkety: Triaged Status in tor source package in Yakkety: Invalid Bug description: Environment: Distribution: ubuntu Distribution version: 16.10 lxc info: apiextensions: storage_zfs_remove_snapshots container_host_shutdown_timeout container_syscall_filtering auth_pki container_last_used_at etag patch usb_devices https_allowed_credentials image_compression_algorithm directory_manipulation container_cpu_time storage_zfs_use_refquota storage_lvm_mount_options network profile_usedby container_push apistatus: stable apiversion: "1.0" auth: trusted environment: addresses: 163.172.48.149:8443 172.20.10.1:8443 172.20.11.1:8443 172.20.12.1:8443 172.20.22.1:8443 172.20.21.1:8443 10.8.0.1:8443 architectures: x86_64 i686 certificate: | -BEGIN CERTIFICATE- -END CERTIFICATE- certificatefingerprint: 3048baa9f20d316f60a6c602452b58409a6d9e2c3218897e8de7c7c72af0179b driver: lxc driverversion: 2.0.5 kernel: Linux kernelarchitecture: x86_64 kernelversion: 4.8.0-27-generic server: lxd serverpid: 32694 serverversion: 2.4.1 storage: btrfs storageversion: 4.7.3 config: core.https_address: '[::]:8443' core.trust_password: true Container: ubuntu 16.10 Issue description -- tor can't start in a non privileged container Logs from the container: - Dec 7 15:03:00 anonymous tor[302]: Configuration was valid Dec 7 15:03:00 anonymous systemd[303]: tor@default.service: Failed at step APPARMOR spawning /usr/bin/tor: No such file or directory Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Main process exited, code=exited, status=231/APPARMOR Dec 7 15:03:00 anonymous systemd[1]: Failed to start Anonymizing overlay network for TCP. Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Unit entered failed state. Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Failed with result 'exit-code'. Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Service hold-off time over, scheduling restart. Dec 7 15:03:00 anonymous systemd[1]: Stopped Anonymizing overlay network for TCP. Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Failed to reset devices.list: Operation not permitted Dec 7 15:03:00 anonymous systemd[1]: Failed to set devices.allow on /system.slice/system-tor.slice/tor@default.service: Operation not permitted Dec 7 15:03:00 anonymous systemd[1]: message repeated 6 times: [ Failed to set devices.allow on /system.slice/system-tor.slice/tor@default.service: Operation not permitted] Dec 7 15:03:00 anonymous systemd[1]: Couldn't stat device /run/systemd/inaccessible/chr Dec 7 15:03:00 anonymous systemd[1]: Couldn't stat device /run/systemd/inaccessible/blk Dec 7 15:03:00 anonymous systemd[1]: Failed to set devices.allow on /system.slice/system-tor.slice/tor@default.service: Operation not permitted Logs from the host audit: type=1400 audit(1481119378.856:6950): apparmor="DENIED" operation="change_onexec" info="label not found" error=-2 namespace="root//lxd-anonymous_" profile="unconfined" name="system_tor" pid=12164 comm="(tor)" Steps to reproduce - install ubuntu container 16.10 on a ubuntu 16.10 host install tor in the container Launch tor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1648143/+subscriptions -- Mailing list: https://launchpad.net/~touch-pac
Re: [Touch-packages] [Bug 1576341] Re: systemd in degraded state on startup in LXD containers
On 29.03.2017 [03:19:16 -], Serge Hallyn wrote: > Thanks, Nish. My thoughts: > > 1.a sounds good Ack. > 1.b i'd like another way to do that, but not sure what a better way would > be. Yeah, I spent some time looking at the CPC generater and it seems like this is pretty hard-coded: 999-cpc-fixes.chroot: ## -- # for maverick and newer, use LABEL= for the '/' entry in fstab if [ -n "${root_fs_label}" ]; then bl="[:blank:]" lstr="LABEL=${root_fs_label}" sed -i "s,^[^#${bl}]*\([${bl}]*/[${bl}].*\),${lstr}\1," "${rootd}/etc/fstab" fi cat > /etc/fstab << EOM LABEL=cloudimg-rootfs / ext4 defaults 0 0 EOM > 1.c does lvm also fail in privileged containers? I can see no use to > running it (for now) in an unprivileged container, so the same solution > as 1.a seems reasonable. It also fails in privileged containers in the same way (see 2.b in comment 20). Note that it works if I manually start the socket after boot. > 1.d > CAP_ADMIN_READ is not a real capability. So if 1.d is fixed by that, > then something else is wrong. Right, follow-on comments indicated it was a thinko on my part. I think it make sense, based upon the context in the audit bug that perhaps we just don't do auditing in unprivileged containers (similar to the 1.a change)? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1576341 Title: systemd in degraded state on startup in LXD containers Status in lvm2 package in Ubuntu: Confirmed Status in lxd package in Ubuntu: Invalid Status in open-iscsi package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Confirmed Bug description: The ubuntu:xenial image shows 'degraded' state in lxd on initial boot. $ lxc launch xenial x1 $ sleep 10 $ lxc file pull x1/etc/cloud/build.info - build_name: server serial: 20160420-145324 $ lxc exec x1 systemctl is-system-running degraded $ lxc exec x1 -- systemctl --state=failed UNIT LOAD ACTIVE SUBDESCRIPTION ● dev-hugepages.mount loaded failed failed Huge Pages File System ● iscsid.serviceloaded failed failed iSCSI initiator daemon (iscsid) ● open-iscsi.serviceloaded failed failed Login to default iSCSI targets ● systemd-remount-fs.serviceloaded failed failed Remount Root and Kernel File Systems ● systemd-sysctl.serviceloaded failed failed Apply Kernel Variables ● lvm2-lvmetad.socket loaded failed failed LVM2 metadata daemon socket ● systemd-journald-audit.socket loaded failed failed Journal Audit Socket LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB= The low-level unit activation state, values depend on unit type. 7 loaded units listed. Pass --all to see loaded but inactive units, too. To show all installed unit files use 'systemctl list-unit-files'. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: open-iscsi 2.0.873+git0.3b4b4500-14ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Thu Apr 28 17:28:04 2016 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) SourcePackage: open-iscsi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1576341/+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 1645037] Re: apparmor_parser hangs indefinitely when called by multiple threads
This bug was fixed in the package linux - 4.8.0-45.48 --- linux (4.8.0-45.48) yakkety; urgency=low * CVE-2017-7184 - xfrm_user: validate XFRM_MSG_NEWAE XFRMA_REPLAY_ESN_VAL replay_window - xfrm_user: validate XFRM_MSG_NEWAE incoming ESN size harder -- Stefan Bader Fri, 24 Mar 2017 12:03:39 +0100 ** Changed in: linux (Ubuntu Yakkety) Status: Triaged => Fix Released ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2017-7184 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1645037 Title: apparmor_parser hangs indefinitely when called by multiple threads Status in apparmor package in Ubuntu: Triaged Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Triaged Status in linux source package in Yakkety: Fix Released Status in linux source package in Zesty: Fix Released Bug description: This bug surfaced when starting ~50 LXC container with LXD in parallel multiple times: # Create the containers for c in c foo{1..50}; do lxc launch images:ubuntu/xenial $c; done # Exectute this loop multiple times until you observe errors. for c in c foo{1..50}; do lxc restart $c & done After this you can ps aux | grep apparmor and you should see output similar to: root 19774 0.0 0.0 12524 1116 pts/1S+ 20:14 0:00 apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache /var/lib/lxd/security/apparmor/profiles/lxd-foo30 root 19775 0.0 0.0 12524 1208 pts/1S+ 20:14 0:00 apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache /var/lib/lxd/security/apparmor/profiles/lxd-foo26 root 19776 0.0 0.0 13592 3224 pts/1D+ 20:14 0:00 apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache /var/lib/lxd/security/apparmor/profiles/lxd-foo30 root 19778 0.0 0.0 13592 3384 pts/1D+ 20:14 0:00 apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache /var/lib/lxd/security/apparmor/profiles/lxd-foo26 root 19780 0.0 0.0 12524 1208 pts/1S+ 20:14 0:00 apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache /var/lib/lxd/security/apparmor/profiles/lxd-foo43 root 19782 0.0 0.0 12524 1208 pts/1S+ 20:14 0:00 apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache /var/lib/lxd/security/apparmor/profiles/lxd-foo34 root 19783 0.0 0.0 13592 3388 pts/1D+ 20:14 0:00 apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache /var/lib/lxd/security/apparmor/profiles/lxd-foo43 root 19784 0.0 0.0 13592 3252 pts/1D+ 20:14 0:00 apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache /var/lib/lxd/security/apparmor/profiles/lxd-foo34 root 19794 0.0 0.0 12524 1208 pts/1S+ 20:14 0:00 apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache /var/lib/lxd/security/apparmor/profiles/lxd-foo25 root 19795 0.0 0.0 13592 3256 pts/1D+ 20:14 0:00 apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache /var/lib/lxd/security/apparmor/profiles/lxd-foo25 apparmor_parser remains stuck even after all LXC/LXD commands have exited. dmesg output yields lines like: [41902.815174] audit: type=1400 audit(1480191089.678:43): apparmor="STATUS" operation="profile_load" profile="unconfined" name ="lxd-foo30_" pid=12545 comm="apparmor_parser" and cat /proc/12545/stack shows: [] aa_remove_profiles+0x88/0x270 21:19 brauner [] profile_remove+0x144/0x2e0 21:19 brauner [] __vfs_write+0x18/0x40 21:19 brauner [] vfs_write+0xb8/0x1b0 21:19 brauner [] SyS_write+0x55/0xc0 21:19 brauner [] entry_SYSCALL_64_fastpath+0x1e/0xa8 21:19 brauner [] 0x This looks like a potential kernel bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1645037/+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 1648143] Re: tor in lxd: apparmor="DENIED" operation="change_onexec" namespace="root//CONTAINERNAME_" profile="unconfined" name="system_tor"
This bug was fixed in the package linux - 4.8.0-45.48 --- linux (4.8.0-45.48) yakkety; urgency=low * CVE-2017-7184 - xfrm_user: validate XFRM_MSG_NEWAE XFRMA_REPLAY_ESN_VAL replay_window - xfrm_user: validate XFRM_MSG_NEWAE incoming ESN size harder -- Stefan Bader Fri, 24 Mar 2017 12:03:39 +0100 ** Changed in: linux (Ubuntu Yakkety) Status: Triaged => Fix Released ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2017-7184 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1648143 Title: tor in lxd: apparmor="DENIED" operation="change_onexec" namespace="root//CONTAINERNAME_" profile="unconfined" name="system_tor" Status in apparmor package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Released Status in tor package in Ubuntu: Invalid Status in apparmor source package in Xenial: New Status in linux source package in Xenial: Triaged Status in tor source package in Xenial: Invalid Status in apparmor source package in Yakkety: New Status in linux source package in Yakkety: Fix Released Status in tor source package in Yakkety: Invalid Bug description: Environment: Distribution: ubuntu Distribution version: 16.10 lxc info: apiextensions: storage_zfs_remove_snapshots container_host_shutdown_timeout container_syscall_filtering auth_pki container_last_used_at etag patch usb_devices https_allowed_credentials image_compression_algorithm directory_manipulation container_cpu_time storage_zfs_use_refquota storage_lvm_mount_options network profile_usedby container_push apistatus: stable apiversion: "1.0" auth: trusted environment: addresses: 163.172.48.149:8443 172.20.10.1:8443 172.20.11.1:8443 172.20.12.1:8443 172.20.22.1:8443 172.20.21.1:8443 10.8.0.1:8443 architectures: x86_64 i686 certificate: | -BEGIN CERTIFICATE- -END CERTIFICATE- certificatefingerprint: 3048baa9f20d316f60a6c602452b58409a6d9e2c3218897e8de7c7c72af0179b driver: lxc driverversion: 2.0.5 kernel: Linux kernelarchitecture: x86_64 kernelversion: 4.8.0-27-generic server: lxd serverpid: 32694 serverversion: 2.4.1 storage: btrfs storageversion: 4.7.3 config: core.https_address: '[::]:8443' core.trust_password: true Container: ubuntu 16.10 Issue description -- tor can't start in a non privileged container Logs from the container: - Dec 7 15:03:00 anonymous tor[302]: Configuration was valid Dec 7 15:03:00 anonymous systemd[303]: tor@default.service: Failed at step APPARMOR spawning /usr/bin/tor: No such file or directory Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Main process exited, code=exited, status=231/APPARMOR Dec 7 15:03:00 anonymous systemd[1]: Failed to start Anonymizing overlay network for TCP. Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Unit entered failed state. Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Failed with result 'exit-code'. Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Service hold-off time over, scheduling restart. Dec 7 15:03:00 anonymous systemd[1]: Stopped Anonymizing overlay network for TCP. Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Failed to reset devices.list: Operation not permitted Dec 7 15:03:00 anonymous systemd[1]: Failed to set devices.allow on /system.slice/system-tor.slice/tor@default.service: Operation not permitted Dec 7 15:03:00 anonymous systemd[1]: message repeated 6 times: [ Failed to set devices.allow on /system.slice/system-tor.slice/tor@default.service: Operation not permitted] Dec 7 15:03:00 anonymous systemd[1]: Couldn't stat device /run/systemd/inaccessible/chr Dec 7 15:03:00 anonymous systemd[1]: Couldn't stat device /run/systemd/inaccessible/blk Dec 7 15:03:00 anonymous systemd[1]: Failed to set devices.allow on /system.slice/system-tor.slice/tor@default.service: Operation not permitted Logs from the host audit: type=1400 audit(1481119378.856:6950): apparmor="DENIED" operation="change_onexec" info="label not found" error=-2 namespace="root//lxd-anonymous_" profile="unconfined" name="system_tor" pid=12164 comm="(tor)" Steps to reproduce - install ubuntu container 16.10 on a ubuntu 16.10 host install tor in the container Launch tor To manage notifications about this bug go to: https:/
[Touch-packages] [Bug 1661030] Re: regession tests failing after stackprofile test is run
This bug was fixed in the package linux - 4.8.0-45.48 --- linux (4.8.0-45.48) yakkety; urgency=low * CVE-2017-7184 - xfrm_user: validate XFRM_MSG_NEWAE XFRMA_REPLAY_ESN_VAL replay_window - xfrm_user: validate XFRM_MSG_NEWAE incoming ESN size harder -- Stefan Bader Fri, 24 Mar 2017 12:03:39 +0100 ** Changed in: linux (Ubuntu Yakkety) Status: Triaged => Fix Released ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2017-7184 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1661030 Title: regession tests failing after stackprofile test is run Status in apparmor package in Ubuntu: Fix Released Status in linux package in Ubuntu: Incomplete Status in apparmor source package in Xenial: Fix Committed Status in linux source package in Xenial: Triaged Status in apparmor source package in Yakkety: Fix Committed Status in linux source package in Yakkety: Fix Released Status in apparmor source package in Zesty: Fix Released Status in linux source package in Zesty: Incomplete Bug description: from source, I'm running the tests and the makefile fails at the end with: running stackprofile Makefile:303: recipe for target 'tests' failed make: *** [tests] Error 1 No idea why that is happening. It's breaking on our kernel team regression tests runs, so can this be investigated? The source was fetched using "apt-get source apparmor". A full run is below: king@ubuntu:~/apparmor-2.10.95/tests/regression/apparmor$ sudo make USE_SYSTEM=1 tests running aa_exec running access xfail: ACCESS file rx (r) xfail: ACCESS file rwx (r) xfail: ACCESS file r (wx) xfail: ACCESS file rx (wx) xfail: ACCESS file rwx (wx) xfail: ACCESS dir rwx (r) xfail: ACCESS dir r (wx) xfail: ACCESS dir rx (wx) xfail: ACCESS dir rwx (wx) running at_secure running introspect running capabilities (ptrace) (sethostname) (setdomainname) (setpriority) (setscheduler) (reboot) (chroot) (mlockall) (net_raw) (ioperm) (iopl) running changeprofile running onexec running changehat running changehat_fork running changehat_misc *** A 'Killed' message from bash is expected for the following test /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 12503 Killed $testexec "$@" > $outfile 2>&1 *** A 'Killed' message from bash is expected for the following test /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 12537 Killed $testexec "$@" > $outfile 2>&1 running chdir running clone running coredump *** A 'Segmentation Fault' message from bash is expected for the following test /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 12803 Segmentation fault (core dumped) $testexec "$@" > $outfile 2>&1 *** A 'Segmentation Fault' message from bash is expected for the following test /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 12833 Segmentation fault $testexec "$@" > $outfile 2>&1 *** A 'Segmentation Fault' message from bash is expected for the following test /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 12869 Segmentation fault $testexec "$@" > $outfile 2>&1 *** A 'Segmentation Fault' message from bash is expected for the following test /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 12905 Segmentation fault $testexec "$@" > $outfile 2>&1 *** A 'Segmentation Fault' message from bash is expected for the following test /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 12941 Segmentation fault $testexec "$@" > $outfile 2>&1 XFAIL: Error: corefile present when not expected -- COREDUMP (ix confinement) running deleted running environ Fatal Error (environ): Unable to run test sub-executable running exec running exec_qual running fchdir running fd_inheritance running fork running i18n running link running link_subset running mkdir running mmap running mount using mount rules ... running mult_mount running named_pipe running namespaces running net_raw running open running openat running pipe running pivot_root running ptrace using ptrace v6 tests ... running pwrite running query_label Alert: query_label passed. Test 'QUERY file (all base perms #1)' was marked as expected pass but known problem (xpass) xpass: QUERY file (all base perms #1) Alert: query_label passed. Test 'QUERY file (all base perms #2)' was marked as expected pass but known problem (xpass) xpass: QUERY file (all base perms #2) running regex ru
[Touch-packages] [Bug 1640320] Re: FTBFS in zesty
Based upon c#6 unsubscribing ubuntu-sponsors. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1640320 Title: FTBFS in zesty Status in location-service package in Ubuntu: In Progress Bug description: FTBFS in zesty during a no change rebuild against new boost Please see build logs at: https://launchpad.net/ubuntu/+source /location-service/3.0.0+16.10.20160912-0ubuntu2 Please help fix this [ 10%] Building CXX object src/location_service/com/ubuntu/location/CMakeFiles/ubuntu-location-service-connectivity.dir/connectivity/wireless_network.cpp.o cd /<>/location-service-3.0.0+16.10.20160912/obj-x86_64-linux-gnu/src/location_service/com/ubuntu/location && /usr/bin/g++ -DCOM_UBUNTU_LOCATION_SERVICE_HAVE_NET_CPP=1 -DCOM_UBUNTU_LOCATION_SERVICE_HAVE_UBUNTU_PLATFORM_HARDWARE_API -DCOM_UBUNTU_LOCATION_SERVICE_PROVIDERS_GEOCLUE -DCOM_UBUNTU_LOCATION_SERVICE_PROVIDERS_GPS -Dubuntu_location_service_connectivity_EXPORTS -I/<>/location-service-3.0.0+16.10.20160912/3rd-party -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/json-c -I/<>/location-service-3.0.0+16.10.20160912/include/location_service -I/<>/location-service-3.0.0+16.10.20160912/src/location_service -I/<>/location-service-3.0.0+16.10.20160912/obj-x86_64-linux-gnu/src/location_service -I/usr/include/ubuntu -g -O2 -fdebug-prefix-map=/<>/location-service-3.0.0+16.10.20160912=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++11 -Wall -fno-strict-aliasing -pedantic -Wextra -fPIC -Wno-error=unused-local-typedefs -fPIC -o CMakeFiles/ubuntu-location-service-connectivity.dir/connectivity/wireless_network.cpp.o -c /<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/connectivity/wireless_network.cpp In file included from /<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/providers/gps/sntp_client.h:21:0, from /<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/providers/gps/sntp_client.cpp:19: /<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/providers/gps/android_hardware_abstraction_layer.h:57:14: error: ‘vector’ in namespace ‘std’ does not name a template type std::vector xtra_hosts ^~ /<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/providers/gps/android_hardware_abstraction_layer.h:59:10: warning: extra ‘;’ [-Wpedantic] }; ^ /<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/providers/gps/android_hardware_abstraction_layer.h:66:18: error: ‘vector’ in namespace ‘std’ does not name a template type virtual std::vector download_xtra_data(const Configuration& config) = 0; ^~ make -f po/CMakeFiles/pofiles_70.dir/build.make po/CMakeFiles/pofiles_70.dir/depend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1640320/+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 1663695] Re: Kubuntu 16.04.1 discover empty after fresh install
Added a version of this patch which also fixes the automatic tests. ** Patch added: "Fix for the bug and autopkgtests" https://bugs.launchpad.net/ubuntu/+source/plasma-discover/+bug/1663695/+attachment/4850082/+files/lp1663695fix+tests.debdiff ** Changed in: appstream (Ubuntu) Status: New => Fix Committed ** Changed in: packagekit (Ubuntu) Status: Incomplete => Fix Released ** Changed in: packagekit (Ubuntu) Status: Fix Released => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1663695 Title: Kubuntu 16.04.1 discover empty after fresh install Status in appstream package in Ubuntu: Fix Committed Status in packagekit package in Ubuntu: Invalid Status in plasma-discover package in Ubuntu: Invalid Bug description: Also reported at (https://github.com/hughsie/PackageKit/issues/177) I tried discover just after installing Kubuntu 16.04.1 LTS, and some software was being displayed, but search was not working. I tried to install muon, and did some software update (which seemed to work fine), and after that discover would not display any software at all. Updates still work. Muon works fine, except that search stops working after a while. There are display issues on top of that, but that is not the worst problem. Having the default software used for installing software on Kubuntu fail completely is a rather big issue... I tried uninstalling plasma-discover and muon, purging them, and reinstalling them, but that did not change anything. The current version is plasma-discover 5.6.2. Is there anything I can do to work around the bug ? This is the output I get when starting it from the CLI: log_attica_plugin: Loaded paths from config: (QUrl("http://download.kde.org/ocs/providers.xml";)) knewstuff: Initializing KNS3::Engine from ' "/etc/xdg/comic.knsrc" ' knewstuff: Loading KNewStuff3 config: "/etc/xdg/comic.knsrc" knewstuff: Categories: ("Plasma Comic") knewstuff: Using registry file: "/home/damien/.local/share/knewstuff3/.knsregistry" knewstuff: Loading KNS2 registry of files for the component: "" knewstuff: Cache read... entries: 0 knewstuff: loading providers from "http://download.kde.org/ocs/providers.xml"; knewstuff: XmlLoader::load(): url: QUrl("http://download.kde.org/ocs/providers.xml";) log_attica_plugin: Loaded paths from config: (QUrl("http://download.kde.org/ocs/providers.xml";)) knewstuff: Initializing KNS3::Engine from ' "/etc/xdg/plasmoids.knsrc" ' knewstuff: Loading KNewStuff3 config: "/etc/xdg/plasmoids.knsrc" knewstuff: Categories: ("Plasma 5 Plasmoid") knewstuff: Loading KNS2 registry of files for the component: "" knewstuff: Cache read... entries: 0 knewstuff: loading providers from "http://download.kde.org/ocs/providers.xml"; knewstuff: XmlLoader::load(): url: QUrl("http://download.kde.org/ocs/providers.xml";) log_attica_plugin: Loaded paths from config: (QUrl("http://download.kde.org/ocs/providers.xml";)) no providers for "/etc/xdg/comic.knsrc" invalid kns backend! no providers for "/etc/xdg/plasmoids.knsrc" invalid kns backend! knewstuff: XmlLoader::slotJobData() knewstuff: XmlLoader::slotJobData() knewstuff: --Xml Loader-START-- knewstuff: "\n\napi.kde-look.org\n https://api.kde-look.org/ocs/v1/\n api.kde-look.org\n\n https://api.kde-look.org/theme/flatui/img/new/O-standard-logo.png\n \n https://api.kde-look.org/content/terms\n https://api.kde-look.org/register\n\n \n\n\n\n\n" knewstuff: --Xml Loader-END-- knewstuff: slotProvidersLoaded knewstuff: Provider attributes: "" log_attica_plugin: No credentials found knewstuff: Engine addProvider called with provider with id "https://api.kde-look.org/ocs/v1/"; knewstuff: XmlLoader::slotJobData() knewstuff: XmlLoader::slotJobData() knewstuff: --Xml Loader-START-- knewstuff: "\n\napi.kde-look.org\n https://api.kde-look.org/ocs/v1/\n api.kde-look.org\n\n https://api.kde-look.org/theme/flatui/img/new/O-standard-logo.png\n \n https://api.kde-look.org/content/terms\n https://api.kde-look.org/register\n\n \n\n\n\n\n" knewstuff: --Xml Loader-END-- knewstuff: slotProvidersLoaded knewstuff: Provider attributes: "" log_attica_plugin: No credentials found knewstuff: Engine addProvider called with provider with id "https://api.kde-look.org/ocs/v1/"; knewstuff: providerInitialized "api.kde-look.org" knewstuff: providers loaded knewstuff: providerInitialized "api.kde-look.org" knewstuff: providers loaded ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: plasma-discover 5.6.2-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-62.83-gen
[Touch-packages] [Bug 1677397] [NEW] lightdm-gtk-greeter SIGSEGV when invoked by Xvnc -inetd -query
Public bug reported: To reproduce: 1. Install Xubuntu 16.04 LTS, update fully 2. Install packages xinetd, vnc4server 3. Append to /etc/services: vnc 5900/tcp# VNC Virtual Network Computing 4. Append to /etc/lightdm/lightdm.conf: [XDMCPServer] enabled=true 5. Create /etc/xinetd.d/vnc: service vnc { disable = no socket_type = stream protocol= tcp group = tty wait= no user= nobody server = /usr/bin/Xvnc server_args = -inetd -query localhost -once -securitytypes=none -geometry 1024x768 } # NOTE: might need to add an arg like ":1" to get out of way of local X server # my case is special as I am trying to run headless, nobody is logged in on console 6. Signal xinetd and lightdm to reconfigure: $ sudo killall -1 xinetd $ sudo service lightdm restart # or however your init system works 7. Don't know if significant (I am 400 miles away from test host and can't test): do NOT have anyone logged in on the test host console. In fact, to most closely reproduce my case, shut down the test host, power it off, disconnect all monitors and keyboards, then power it on and access from the net. 8. From another system, connect to the test host: $ gvncviewer testhost:0 # Your favorite VNC viewer & test host name... 9. VNC connects briefly, displays grey hashed background, disconnects. Syslog on test host says: Mar 29 15:07:40 osmium lightdm[13828]: (lightdm:13828): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed Mar 29 15:07:40 osmium systemd[1]: Started Session c11 of user lightdm. Mar 29 15:07:40 osmium lightdm[13828]: ** (lightdm:13828): WARNING **: Error activating login1 session: GDBus.Error:org.freedesktop.DBus.Error.NotSupported: Operation not supported Mar 29 15:07:40 osmium kernel: [14985.100699] lightdm-gtk-gre[13972]: segfault at 0 ip 7f3f23bd09bf sp 7ffc64b32058 error 4 in libc-2.23.so[7f3f23b3b000+1bf000] Mar 29 15:07:41 osmium lightdm[13828]: /etc/modprobe.d is not a file Mar 29 15:07:41 osmium lightdm[13828]: message repeated 4 times: [ /etc/modprobe.d is not a file] Mar 29 15:07:41 osmium lightdm[13828]: update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf and core-like-thing ends up in /var/crash/... ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-70.91-generic 4.4.49 Uname: Linux 4.4.0-70-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Mar 29 14:52:52 2017 InstallationDate: Installed on 2017-03-28 (1 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 XDG_RUNTIME_DIR= SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm-gtk-greeter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug crash xenial ** Package changed: xorg (Ubuntu) => lightdm-gtk-greeter (Ubuntu) -- 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/1677397 Title: lightdm-gtk-greeter SIGSEGV when invoked by Xvnc -inetd -query Status in lightdm-gtk-greeter package in Ubuntu: New Bug description: To reproduce: 1. Install Xubuntu 16.04 LTS, update fully 2. Install packages xinetd, vnc4server 3. Append to /etc/services: vnc 5900/tcp# VNC Virtual Network Computing 4. Append to /etc/lightdm/lightdm.conf: [XDMCPServer] enabled=true 5. Create /etc/xinetd.d/vnc: service vnc { disable = no socket_type = stream protocol= tcp group = tty wait= no user= nobody server = /usr/bin/Xvnc server_args = -inetd -query localhost -once -securitytypes=none -geometry 1024x768 } # NOTE: might need to add an arg like ":1" to get out of way of local X server # my case is special as I am trying to run headless, nobody is logged in on console 6. Signal xinetd and lightdm to reconfigure: $ sudo killall -1 xinetd $ sudo service lightdm restart # or however your init system works 7. Don't know if significant (I am 400 miles away from test host and can't test): do NOT have anyone logged in on the test host console. In fact, to most closely reproduce my case, shut down the test host, power it off, disconnect all monitors and keyboards, then power it on and access from the net. 8. From another system, connect to the test host: $ gv
[Touch-packages] [Bug 1673942] Re: pulseaudio suddenly stops. No dmesg entries. Nothing in the syslog
no problems for several days while outputting through analog-stereo. Am i just wasting my time to think that somebody might actually look at this? Other people have reported what look like similar conditions, that never seem to meet a resolution. If there are some detailed instructions about generating some detailed logs, I can do that if it will help resolve this -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1673942 Title: pulseaudio suddenly stops. No dmesg entries. Nothing in the syslog Status in pulseaudio package in Ubuntu: New Bug description: this only happens when sound is through the PCI sound card. When i connect speakers to the motherboard output (I lose the 5.1 component), pulseaudio never dies. I have switched and replaced the sound card to no effect but I never really thought that was the issue. There seems to be no evidence of the failure unless I run it from the command line with -, when eventually I see a 'killed' message. The pulseaudio log collects initial messages, but nothing else is echoed to the log - which could be anything from 3-20 minutes [typically]. I'm more than happy to assist in getting whatever logs are required, but nothing I've seen documented seems to help. --- ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: julie 30342 F pulseaudio /dev/snd/controlC1: julie 30342 F pulseaudio /dev/snd/controlC2: julie 30342 F pulseaudio /dev/snd/controlC0: julie 30342 F pulseaudio DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2015-05-19 (670 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Package: pulseaudio 1:9.0-2ubuntu2.1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_NZ:en TERM=xterm-256color PATH=(custom, no user) LANG=en_NZ.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. Tags: yakkety Uname: Linux 4.2.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/25/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-78LMT-USB3 6.0 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-USB3 6.0 dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.pulse.daemon.conf: [modified] modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.daemon.conf: 2017-03-18T20:58:01.387562 mtime.conffile..etc.pulse.default.pa: 2015-12-20T08:49:47.368322 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1673942/+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 1633331] Re: /usr/bin/pyclean fails with python3
*doesn't really make sense to be running -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-defaults in Ubuntu. https://bugs.launchpad.net/bugs/161 Title: /usr/bin/pyclean fails with python3 Status in python-defaults package in Ubuntu: New Status in samba package in Ubuntu: Triaged Bug description: samba ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-samba 2:4.3.9+dfsg-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic i686 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 Date: Fri Oct 14 08:31:48 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2016-08-05 (69 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) NmbdLog: RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SambaServerRegression: Yes SmbConfIncluded: Yes SmbLog: SourcePackage: samba Title: package python-samba 2:4.3.9+dfsg-0ubuntu0.16.04.2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-08-06 (68 days ago) WindowsFailedConnect: Yes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/161/+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 1633331] Re: /usr/bin/pyclean fails with python3
Oh I missed this bit: "I'd assume this only triggers when the system is tweaked to run /usr/bin/python as python3? Does that match your case?" Yeah, don't do that! :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-defaults in Ubuntu. https://bugs.launchpad.net/bugs/161 Title: /usr/bin/pyclean fails with python3 Status in python-defaults package in Ubuntu: New Status in samba package in Ubuntu: Triaged Bug description: samba ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-samba 2:4.3.9+dfsg-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic i686 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 Date: Fri Oct 14 08:31:48 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2016-08-05 (69 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) NmbdLog: RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SambaServerRegression: Yes SmbConfIncluded: Yes SmbLog: SourcePackage: samba Title: package python-samba 2:4.3.9+dfsg-0ubuntu0.16.04.2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-08-06 (68 days ago) WindowsFailedConnect: Yes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/161/+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 1633331] Re: /usr/bin/pyclean fails with python3
It doesn't really make to be running /usr/bin/pyclean with Python 3. That's why we have /usr/bin/py3clean which is part of python3-minimal. samba isn't even ported to Python 3, so why is it trying to run pyclean as Python 3? (samba is really the last thing keeping Python 2 on desktop, and it's not just us that's blocked on that.) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-defaults in Ubuntu. https://bugs.launchpad.net/bugs/161 Title: /usr/bin/pyclean fails with python3 Status in python-defaults package in Ubuntu: New Status in samba package in Ubuntu: Triaged Bug description: samba ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-samba 2:4.3.9+dfsg-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic i686 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 Date: Fri Oct 14 08:31:48 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2016-08-05 (69 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) NmbdLog: RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SambaServerRegression: Yes SmbConfIncluded: Yes SmbLog: SourcePackage: samba Title: package python-samba 2:4.3.9+dfsg-0ubuntu0.16.04.2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-08-06 (68 days ago) WindowsFailedConnect: Yes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/161/+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 1677377] [NEW] ADT failure in boot-smoke test with linux-hwe-edge
Public bug reported: ADT boot-smoke test fails with 4.10 hwe-edge kernel in xenial. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-xenial/xenial/amd64/s/systemd/20170329_130746_29365@/log.gz checking that there are no running jobs FAIL: expected: '' actual: '663 lightdm.service start running' Possibly an issue with lightdm or the kernel, I haven't been able to determine the actual cause from the logs. I also haven't been able to reproduce this failure locally. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1677377 Title: ADT failure in boot-smoke test with linux-hwe-edge Status in systemd package in Ubuntu: New Bug description: ADT boot-smoke test fails with 4.10 hwe-edge kernel in xenial. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest- xenial/xenial/amd64/s/systemd/20170329_130746_29365@/log.gz checking that there are no running jobs FAIL: expected: '' actual: '663 lightdm.service start running' Possibly an issue with lightdm or the kernel, I haven't been able to determine the actual cause from the logs. I also haven't been able to reproduce this failure locally. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1677377/+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 1677367] [NEW] Browser displays text with no spaces on certain web pages on Ubuntu Touch OTA-15 (M10)
Public bug reported: Over the past few weeks my browser has been displaying text with no spaces whatsoever as in "Thissentencehasnospaces" on certain pages. It is also displaying numbers and hash symbols oddly, as large blue circles with the numbers printed with white lettering. Sites which are exhibiting this behaviour include Facebook, Google Mail in some instances, eBay and certain news sites. This also affects webapps which are derived from the web browser in Ubuntu Touch. Tellingly, this isn't a problem when using Firefox in a Libertine container, but Firefox is a bit too slow for regular tasks and lacks practical touch inputs. My MX4 doesn't exhibit this problem, but my M10 does. The latter has less free space on the system storage than the latter. Screenshot included. RELEASE: Ubuntu 15.04, OTA-15, M10 tablet PACKAGE VERSION: 0.23+15.04.20170125.1-0ubuntu1 EXPECTED BEHAVIOUR: For web pages on the sites described to display text with spaces between words and with proper number printing. ACTUAL BEHAVIOUR: Web pages do not display text with spaces between words or with proper number printing. ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New ** Tags: browser display formatting m10 text touch ** Attachment added: "screenshot20170329_204355395.png" https://bugs.launchpad.net/bugs/1677367/+attachment/4849991/+files/screenshot20170329_204355395.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1677367 Title: Browser displays text with no spaces on certain web pages on Ubuntu Touch OTA-15 (M10) Status in webbrowser-app package in Ubuntu: New Bug description: Over the past few weeks my browser has been displaying text with no spaces whatsoever as in "Thissentencehasnospaces" on certain pages. It is also displaying numbers and hash symbols oddly, as large blue circles with the numbers printed with white lettering. Sites which are exhibiting this behaviour include Facebook, Google Mail in some instances, eBay and certain news sites. This also affects webapps which are derived from the web browser in Ubuntu Touch. Tellingly, this isn't a problem when using Firefox in a Libertine container, but Firefox is a bit too slow for regular tasks and lacks practical touch inputs. My MX4 doesn't exhibit this problem, but my M10 does. The latter has less free space on the system storage than the latter. Screenshot included. RELEASE: Ubuntu 15.04, OTA-15, M10 tablet PACKAGE VERSION: 0.23+15.04.20170125.1-0ubuntu1 EXPECTED BEHAVIOUR: For web pages on the sites described to display text with spaces between words and with proper number printing. ACTUAL BEHAVIOUR: Web pages do not display text with spaces between words or with proper number printing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1677367/+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 1546310] Re: In CAR bluetooth not working
Hi Thomas, I raised this bug and I am still affected by the bug (e.g. with the Audi A3). Due to the switch to the snap based OS I do not expect to see any progress in the coming months for our phones (being a Aquaris e4.5 user). I think the expectation is that our phones only get security fixes. I nevertheless hope heavily that the devs are considering these issues with bluetooth, which have been encountered in the last years and find a solution for the future. It seems that this issue (bluetooth with cars, headsets, speakers, ...) is not as simple as implementing bluez 5.xx and that's it. Nevertheless the "alternative OS" developers find their solutions to this issue so I hope the Ubuntu team can do it alike. I am not a dev, just a user. So we can raise the awareness that this is still requested and work on this subject highly appreciated. Matthias -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1546310 Title: In CAR bluetooth not working Status in Canonical System Image: Fix Released Status in bluez package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Fix Committed Bug description: I have paired my phone with my car as always (connection did work in the past). Connection runs as expected and everything like display, phone book, ... but this evening I wanted to place a call from my car and it did not work. I was then also not able to take a call (I could not hear the conterpart and the counterpart could not hear me). Since yesterday I am on: current build number: 259 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-02-16 12:09:18 version version: 259 version ubuntu: 20160216 version device: 20160108-efc96d8 version custom: 20160111-926-36--vivid With OTA9 I did not have the issue. I have attached my logs. I have enabled the following bug-settings for bluetooth: sudo sed -i 's/exec \/usr\/sbin\/bluetoothd/exec \/usr\/sbin\/bluetoothd -d/g' /etc/init/bluetooth.conf sudo sed -i 's/--start/--start --log-level=debug/g' /usr/share/upstart/sessions/pulseaudio.conf I have modified the line in ofono.override to: exec ofonod -P -d provision,udev*,dun*,smart*,hfp_bluez5,stktest,sap I hope my reporting helps to trace down this issue. Uranicus To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1546310/+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 1677363] [NEW] does auditd work on armhf on precise?
Public bug reported: $ sudo /etc/init.d/auditd restart * Restarting audit daemon auditd Error sending add rule data request (Invalid argument) There was an error in line 17 of /etc/audit/audit.rules [ OK ] The non-comment lines before this were: -D -b 328 -w /etc/localtime -p wa -k time-change ... The watch rule on /etc/localtime is the first 'real' rule and it caused the error. The default rules file does almost nothing but seems to work okay. I'm guessing this is in part due to being on an armhf (armv7l) system. Thanks ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: auditd 1.7.18-1ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-1497.124-omap4 3.2.79 Uname: Linux 3.2.0-1497-omap4 armv7l ApportVersion: 2.0.1-0ubuntu17.15 Architecture: armhf Date: Wed Mar 29 12:20:43 2017 MarkForUpload: True ProcEnviron: TERM=rxvt-unicode PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: audit UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.audit.audit.rules: [modified] mtime.conffile..etc.audit.audit.rules: 2017-03-29T12:19:33.699968 ** Affects: audit (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug armhf precise -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to audit in Ubuntu. https://bugs.launchpad.net/bugs/1677363 Title: does auditd work on armhf on precise? Status in audit package in Ubuntu: New Bug description: $ sudo /etc/init.d/auditd restart * Restarting audit daemon auditd Error sending add rule data request (Invalid argument) There was an error in line 17 of /etc/audit/audit.rules [ OK ] The non-comment lines before this were: -D -b 328 -w /etc/localtime -p wa -k time-change ... The watch rule on /etc/localtime is the first 'real' rule and it caused the error. The default rules file does almost nothing but seems to work okay. I'm guessing this is in part due to being on an armhf (armv7l) system. Thanks ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: auditd 1.7.18-1ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-1497.124-omap4 3.2.79 Uname: Linux 3.2.0-1497-omap4 armv7l ApportVersion: 2.0.1-0ubuntu17.15 Architecture: armhf Date: Wed Mar 29 12:20:43 2017 MarkForUpload: True ProcEnviron: TERM=rxvt-unicode PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: audit UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.audit.audit.rules: [modified] mtime.conffile..etc.audit.audit.rules: 2017-03-29T12:19:33.699968 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/audit/+bug/1677363/+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 1677361] [NEW] package python3-crypto 2.6.1-6build1 failed to install/upgrade: el subproceso script pre-removal nuevo devolvió el código de salida de error 1
Public bug reported: python3-crypto2.6.1-6ubuntu0.16.10.3 ProblemType: Package DistroRelease: Ubuntu 16.10 Package: python3-crypto 2.6.1-6build1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 Date: Wed Mar 29 19:34:31 2017 ErrorMessage: el subproceso script pre-removal nuevo devolvió el código de salida de error 1 InstallationDate: Installed on 2017-03-27 (2 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.4 SourcePackage: python-crypto Title: package python3-crypto 2.6.1-6build1 failed to install/upgrade: el subproceso script pre-removal nuevo devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: python-crypto (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-crypto in Ubuntu. https://bugs.launchpad.net/bugs/1677361 Title: package python3-crypto 2.6.1-6build1 failed to install/upgrade: el subproceso script pre-removal nuevo devolvió el código de salida de error 1 Status in python-crypto package in Ubuntu: New Bug description: python3-crypto2.6.1-6ubuntu0.16.10.3 ProblemType: Package DistroRelease: Ubuntu 16.10 Package: python3-crypto 2.6.1-6build1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 Date: Wed Mar 29 19:34:31 2017 ErrorMessage: el subproceso script pre-removal nuevo devolvió el código de salida de error 1 InstallationDate: Installed on 2017-03-27 (2 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.4 SourcePackage: python-crypto Title: package python3-crypto 2.6.1-6build1 failed to install/upgrade: el subproceso script pre-removal nuevo devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-crypto/+bug/1677361/+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 1317437] Re: wubi kernel option "rw" required
The change, by itself, looks fine. However, I'd like to urge users to migrate away from wubi, as it is no longer supported (and 14.04 is about to be EOL too). This doesn't mean we can't make the change, just that there should be more testing done to see how it affects other boot methods, and exactly in which cases it is useful (since it needs proper test cases anyway). For this reason, please follow the steps at https://wiki.ubuntu.com/StableReleaseUpdates#Procedure to make sure this bug is all ready for the request to update stable releases. This mostly means updating the description with proper test cases and justification for the SRU. ** Changed in: initramfs-tools (Ubuntu) Status: New => Triaged -- 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/1317437 Title: wubi kernel option "rw" required Status in initramfs-tools package in Ubuntu: Triaged Bug description: We have installed ubuntu beta-64amd.iso (trusty tahr) as wubi on a windows 8.1. Since upgrade * busybox-initramfs from "1.20.0-8.1ubuntu1" to "1.21.0-1ubuntu1" * busybox-static from "1.20.0-8.1ubuntu1" to "1.21.0-1ubuntu1" the wubi installation won't work / start and ends with the massage: "Bei der Ueberpruefung des Laufwerkes auf / wurden schwere Fehler gefunden" "key: »I« zum Ignorieren, »S« ueberspringt das Einhaengen, »M« fuer manuelle Wiederherstellung" Changing the sequence of "/boot/grub/grub.cfg" inside the line: * linux /boot/vmlinuz-3.13.0-24-generic root=UUID=B65449E05449A449 loop=/ubuntu/disks/root.disk ro quiet splash $vt_handoff into * linux /boot/vmlinuz-3.13.0-24-generic root=UUID=B65449E05449A449 loop=/ubuntu/disks/root.disk rw quiet splash $vt_handoff (kernel option »ro« into »rw«) lets start the wubi installation without any restrictions. For further system-information see -> annex ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lupin-support 0.55 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 Date: Thu May 8 10:53:53 2014 ProcEnviron: LANGUAGE=de_DE TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: lupin UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1317437/+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 1673557] Re: /proc/cpuinfo should be collected
** Branch linked: lp:~ubuntu-core-dev/ubuntu/zesty/apport/ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1673557 Title: /proc/cpuinfo should be collected Status in apport package in Ubuntu: In Progress Status in whoopsie package in Ubuntu: Triaged Bug description: apport does not currently collect data from /proc/cpuinfo and this would be useful to determine how many users can only run the i386 version of Ubuntu. The general Ubuntu hook, possibly add_kernel_info() could be used, should be modified such that the contents of /proc/cpuinfo are gathered. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1673557/+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 769314] Re: System bell completely silent because PulseAudio sample file undefined by default
I've uploaded a version of Daniel Hahler's patch in comment #22 to zesty. Worked for me, I was able to hear the bell in gnome-terminal. I believe that's the last piece of this puzzle? I'll unsubscribe the sponsors team. Please re-subscribe if there's more to do that is ready to be uploaded. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/769314 Title: System bell completely silent because PulseAudio sample file undefined by default Status in Unity: Invalid Status in gnome-media package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Status in unity package in Ubuntu: Invalid Bug description: Binary package hint: unity This bug is about problems using the system bell in Unity or another Compiz-based environment. For problems using the system bell in Ubuntu Classic/Metacity or another Metacity-based environment, please see bug #486154. The system bell (that beep when you backspace on an empty line on a terminal, i.e.) is badly broken using the Unity environment in the Natty beta 2. By default, no sound is produced, and several misconfigurations make it difficult to produce sound either from the PC speaker or Pulse Audio's module-x11-bell. Not knowing what the desired behavior is, I can't say exactly what needs to be fixed. But the combination of the following issues makes the system quite obviously broken. 1) pcskpr is blacklisted. The pcspkr module is necessary for the PC speaker to produce sound. It is blacklisted, so regular users cannot turn the bell on. It would be nice for this to be fixed, but the attitudes displayed in #77010 suggest that it won't be. Nonetheless, I note it here because it interacts with some of the following. 2) The X bell volume is set to 0. (no more true in xenial) As reported by `xset q`, the bell volume is 0 when Unity is started. Both the PC speaker and module-x11-bell respect this setting, so the volume must be turned up (with `xset b on` or `xset b 100`) for either to work. Since both the PC speaker and module-x11-bell are disabled by default, this setting only serves to frustrate attempts to turn them on; it never prevents unwanted sound. 3) module-x11-bell is loaded by /usr/bin/start-pulseaudio-x11 This is a system file, not a user file, so users cannot decide whether they want this module loaded or not. They could write a script to unload the module at login (and hope the module number doesn't vary between boots), but it would be much cleaner to have the modules loaded from a user file, possibly with defaults if the user file doesn't exist. 4) Sample bell.ogg is not loaded. When module-x11-bell is loaded, it is told to use the sample bell.ogg. But no sample is loaded into Pulse Audio. Thus, module-x11-bell traps system bell events (keeping them from going to the PC speaker) without producing any sound. If module-x11-bell is loaded, the sample it calls on should be loaded as well. (To fix this, run `pactl upload-sample /usr/share/sounds/ubuntu/stereo/bell.ogg bell.ogg`.) 5) gnome-volume-control doesn't. The "Sound Effects" tab of gnome-volume-control offers to set the volume and sound for system bell events, but these have no effect. This is because gnome-volume-control is trying to control system bells through metacity. Ideally, it should be rewritten to control module-x11-bell instead, but a temporary fix could be to simply disable this tab. 6) System bell settings don't transfer to the Ubuntu Classic environment. Because that is using metacity, which has it's own set of problems. See bug #486154. This has been from testing in a VM (virtualbox), but all of these behaviors have also been seen in Compiz in various previous versions of Ubuntu running on various hardware. I have reported this bug against several components, as it is really an integration issue. The eventual fix may not involve your component, but please do not mark this bug as invalid until we have at least a roadmap for fixing it. Otherwise, I fear responsibility will be passed from component to component without anything being fixed. Rationales: Unity - As the overarching environment, Unity should be responsible for getting everything integrated. Additionally, some of the problems relate to session startup settings. Pulse Audio - module-x11-bell is not loaded intelligently or correctly. Gnome Media - Own gnome-volume-control. Versions (but note the same behavior has been seen in many earlier versions): unity: 3.8.10-0ubuntu2 pulseaudio: 1:0.9.22+stable-queue-24-g67d18-0ubuntu3 gnome-media: 2.32.0-0ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/769314/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.n
[Touch-packages] [Bug 1677189] Re: package apparmor 2.10.95-0ubuntu2.6 failed to install/upgrade: end of file on stdin at conffile prompt
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apparmor (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1677189 Title: package apparmor 2.10.95-0ubuntu2.6 failed to install/upgrade: end of file on stdin at conffile prompt Status in apparmor package in Ubuntu: Confirmed Bug description: Help me ProblemType: Package DistroRelease: Ubuntu 16.04 Package: apparmor 2.10.95-0ubuntu2.6 ProcVersionSignature: Ubuntu 4.8.0-41.44~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Tue Mar 28 18:54:30 2017 ErrorMessage: end of file on stdin at conffile prompt ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.8.0-41-generic root=UUID=0ab5d59c-4406-4d9d-b40a-139718895ca0 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: apparmor Syslog: Mar 28 18:51:36 Rodrigo-Inspiron dbus[899]: [system] AppArmor D-Bus mediation is enabled Mar 29 06:42:47 Rodrigo-Inspiron dbus[825]: [system] AppArmor D-Bus mediation is enabled Title: package apparmor 2.10.95-0ubuntu2.6 failed to install/upgrade: end of file on stdin at conffile prompt UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.init.apparmor.conf: 2016-10-04T17:49:43 mtime.conffile..etc.init.d.apparmor: 2016-10-04T17:49:43 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1677189/+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 1574667] Re: Mouse pointer occasionally jumps to the bottom-left corner
I also confirm the bug on my DELL Inspiron 7537 and Ubuntu 16.04.2 LTS with a fresh install. Even after all updates, the problem is still here: the cursor jumps randomly during selection, dragging and other clickpad operations. It literally drives me crazy. Applied all suggestions posted above, with attention to the reply #32 and other indications find on the web: https://forum.siduction.org/index.php?topic=6180.0 The clickpad feeling is still really bad, inaccurate, not suitable for daily use. PLEASE FIX IT, a pointer like this makes system unusable -- 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/1574667 Title: Mouse pointer occasionally jumps to the bottom-left corner Status in xorg package in Ubuntu: Confirmed Bug description: Sometimes the mouse pointer jumps directly to the bottom-left corner of the screen, which results in opening the trash window when clicking. This seems to be related: https://ubuntu-mate.community/t/mouse- pointer-jumps-on-clicking-touchpad/2932. Thanks, MZ ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 BootLog: /dev/sda6: clean, 276587/40779776 files, 15261626/163117056 blocks 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 Apr 25 15:55:54 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake Integrated Graphics [1028:06b2] InstallationDate: Installed on 2016-04-23 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 064e:920b Suyin Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5559 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed root=UUID=c5bc0a1d-3fe9-4ae5-81e9-de7d141b419c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.5 dmi.board.name: 06CMH7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn06CMH7:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5559 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Apr 25 13:43:44 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1156 vendor LGD xserver.version: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1574667/+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 1673625] Re: 10-globally-managed-devices.conf contained in wrong package
Reverting duplicate to make the conclusion for this bug clearer: This file belongs in NM and NM is supposed to make sure that it doesn't break things (which is why there is a bug for upgrade as bug 1676547). It should not be seen as an override but as Ubuntu shipping a default configuration meant to work on the majority of systems (see below). nplan is in standard and on all systems, whereas NM doesn't normally exist on servers. nplan should not leave unnecessary files around -- on servers, the file in /usr/lib would be unnecessary -- it only makes sense if NetworkManager is installed. On a typical desktop new install, netplan and NM would be installed, netplan would start at boot and write an override file to /run/NetworkManager/conf.d (as per its default configuration) to tell NM to manage all files. The networking behavior expected by our users would be maintained (ie. they don't need to run netplan, but we want to make it available and start educating on its use). On earlier installed desktop systems, netplan gets installed on upgrade but likely does not start at boot (and regardless should not break networking before a reboot happens) and NM should write its "default config" and override it via /etc/NetworkManager/conf.d/10-globally- managed-devices.conf by postinst on its own upgrade. This is done to ensure networking is not broken during upgrade, and that old behavior is maintained on upgraded systems. On servers, netplan is installed but not NetworkManager. netplan should not add unnecessary files to the install. Default behavior should already be maintained because the empty configuration shipped by default will not affect ifupdown/networkd; but users can start using netplan to configure their systems instead of ifupdown immediately. The intent here is to make sure that NM behaves the right way given that nplan is on all systems, and that it does so following whether netplan is in use or not (as much as possible). netplan is meant to replace ifupdown for static network configuration, and to configure NetworkManager or networkd (depending on what is available) appropriately to drive the networking story requested by the user. ** Changed in: network-manager (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: nplan (Ubuntu) Status: Incomplete => Won't Fix -- 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/1673625 Title: 10-globally-managed-devices.conf contained in wrong package Status in network-manager package in Ubuntu: Won't Fix Status in nplan package in Ubuntu: Won't Fix Bug description: /usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf is installed from network-manager but without nplan it has no benefit, and breaks networking until you override it. Since the config is there to change how NetworkManager behaves in the presence of nplan, the configuration file itself should actually be contained in the nplan package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1673625/+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 1633319] Re: memory leak in indicator-datetime
I have the same issue on an Ubuntu 16.10 VM in VirtualBox running on Windows 7. Evolution was running fine until I added a fifth account. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1633319 Title: memory leak in indicator-datetime Status in indicator-datetime package in Ubuntu: Confirmed Bug description: After upgrading from 16.04 to 16.10 on the System76 Serval WS indicator-datetime-service is consuming all the system memory from 3.7GB up to 32 GB in 30 seconds. The system kills the indicator- datetime-service process and indicator-datetime-service restarts and memory consumption repeats until killed again. All swap memory is consumed in this pattern. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: indicator-datetime 15.10+16.10.20160820.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 14 00:12:00 2016 EcryptfsInUse: Yes SourcePackage: indicator-datetime UpgradeStatus: Upgraded to yakkety on 2016-10-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1633319/+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 1673557] Re: /proc/cpuinfo should be collected
** Changed in: apport (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1673557 Title: /proc/cpuinfo should be collected Status in apport package in Ubuntu: In Progress Status in whoopsie package in Ubuntu: Triaged Bug description: apport does not currently collect data from /proc/cpuinfo and this would be useful to determine how many users can only run the i386 version of Ubuntu. The general Ubuntu hook, possibly add_kernel_info() could be used, should be modified such that the contents of /proc/cpuinfo are gathered. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1673557/+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 1673625] Re: 10-globally-managed-devices.conf contained in wrong package
** This bug is no longer a duplicate of bug 1676547 No network connectivity after upgrade from 16.04 to 16.10 -- 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/1673625 Title: 10-globally-managed-devices.conf contained in wrong package Status in network-manager package in Ubuntu: Won't Fix Status in nplan package in Ubuntu: Won't Fix Bug description: /usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf is installed from network-manager but without nplan it has no benefit, and breaks networking until you override it. Since the config is there to change how NetworkManager behaves in the presence of nplan, the configuration file itself should actually be contained in the nplan package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1673625/+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 1673557] Re: /proc/cpuinfo should be collected
Here's part of a report made using the above python code to gather ProcCpuinfo. PackageArchitecture: amd64 ProcCpuinfoMinimal: processor : 3 vendor_id : GenuineIntel cpu family : 6 model : 58 model name : Intel(R) Core(TM) i5-3570 CPU @ 3.40GHz stepping : 9 microcode : 0x17 cpu MHz: 3677.661 cache size : 6144 KB physical id: 0 siblings : 4 core id: 3 cpu cores : 4 apicid : 6 initial apicid : 6 fpu: yes fpu_exception : yes cpuid level: 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm epb tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt dtherm ida arat pln pts bugs : bogomips : 6819.49 clflush size : 64 cache_alignment: 64 address sizes : 36 bits physical, 48 bits virtual power management: ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1673557 Title: /proc/cpuinfo should be collected Status in apport package in Ubuntu: Triaged Status in whoopsie package in Ubuntu: Triaged Bug description: apport does not currently collect data from /proc/cpuinfo and this would be useful to determine how many users can only run the i386 version of Ubuntu. The general Ubuntu hook, possibly add_kernel_info() could be used, should be modified such that the contents of /proc/cpuinfo are gathered. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1673557/+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 1673557] Re: /proc/cpuinfo should be collected
I uploaded it to errors.u.c too to confirm that whoopsie let ProcCpuinfoMinimal through and it did. https://errors.ubuntu.com/oops/44d8b014-14a8-11e7-9db8-fa163ebeb28a -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1673557 Title: /proc/cpuinfo should be collected Status in apport package in Ubuntu: Triaged Status in whoopsie package in Ubuntu: Triaged Bug description: apport does not currently collect data from /proc/cpuinfo and this would be useful to determine how many users can only run the i386 version of Ubuntu. The general Ubuntu hook, possibly add_kernel_info() could be used, should be modified such that the contents of /proc/cpuinfo are gathered. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1673557/+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 1675364] Re: [regression] GTK and KDE apps fail to start under Unity8 (without gnome-session running)
Ok, I've traced this down to bug #1675448 being the root of the issue. Xmir is started no matter what and if an application natively supports Mir such as a Gtk or Qt app, then there are multiple connections to Mir, which is what the aforementioned bug is about. So a decision needs to be made. Either bug #1675448 needs to be fixed or we need to revert the Gtk probing order back and just use xmir for the time being. The longer term solution of only starting xmir when it is actually needed along with Mir supported toolkits probing for Mir first is the final solution (see bug #1672931). But that won't be done in time for the Zesty release, hence the other options presented above:) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1675364 Title: [regression] GTK and KDE apps fail to start under Unity8 (without gnome-session running) Status in Canonical System Image: Triaged Status in gtk+3.0 package in Ubuntu: Confirmed Status in libertine package in Ubuntu: Invalid Status in mir package in Ubuntu: Invalid Status in qtmir package in Ubuntu: Invalid Status in ubuntu-app-launch package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Bug description: Recently something has regressed and if i start konsole (using xmir) in unity8 all i get is the splash screen with a spinner forever. Looking at the ps output it seems that the konsole process has actually started. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1675364/+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 1676881] Re: package cups-daemon (not installed) failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
*** This bug is a duplicate of bug 1676380 *** https://bugs.launchpad.net/bugs/1676380 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1676380, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1676380 Update to cups-daemon 2.1.3-4ubuntu0.2 results in maintainer script failures -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1676881 Title: package cups-daemon (not installed) failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in cups package in Ubuntu: Confirmed Bug description: when i update ubuntu 16.04, there are error when download. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon (not installed) ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Mon Mar 27 21:39:48 2017 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2017-03-05 (23 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: cups Title: package cups-daemon (not installed) failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1676881/+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 1677115] Re: package cups-daemon (not installed) failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
*** This bug is a duplicate of bug 1676380 *** https://bugs.launchpad.net/bugs/1676380 ** This bug is no longer a duplicate of bug 1676881 package cups-daemon (not installed) failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 ** This bug has been marked a duplicate of bug 1676380 Update to cups-daemon 2.1.3-4ubuntu0.2 results in maintainer script failures -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1677115 Title: package cups-daemon (not installed) failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in cups package in Ubuntu: New Bug description: whenever i boot up my laptop, after login, a window pops up saying system failed : report it.Thats it ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon (not installed) ProcVersionSignature: Ubuntu 4.8.0-44.47~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-44-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Mon Mar 27 23:36:16 2017 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2017-03-25 (3 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: cups Title: package cups-daemon (not installed) failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1677115/+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 1677085] Re: package cups-daemon (not installed) failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
*** This bug is a duplicate of bug 1676380 *** https://bugs.launchpad.net/bugs/1676380 ** This bug is no longer a duplicate of bug 1676881 package cups-daemon (not installed) failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 ** This bug has been marked a duplicate of bug 1676380 Update to cups-daemon 2.1.3-4ubuntu0.2 results in maintainer script failures -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1677085 Title: package cups-daemon (not installed) failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in cups package in Ubuntu: New Bug description: I was just booting up and got the error... and the options to report a bug... ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon (not installed) ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Mon Mar 27 08:56:36 2017 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2017-03-27 (1 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: cups Title: package cups-daemon (not installed) failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1677085/+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 1568296] Re: Make JS dialogs app modal
** Branch linked: lp:~oxide-developers/oxide/packaging.vivid.overlay -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1568296 Title: Make JS dialogs app modal Status in Oxide: Fix Released Status in webbrowser-app package in Ubuntu: Triaged Bug description: Chrome only supports app-modal JS dialogs, and so does Blink (window.alert blocks the calling process). Oxide pretends to support tab-modal JS dialogs by having a per-WebContents dispatch queue. However, the behaviour is quite broken: - It's really app-modal in single process because there's only a single RenderThread. - In multi-process it's not really tab-modal - it's render-process modal (ie, only a single tab in a render process can show a JS dialog). So, if 2 tabs live in separate processes then they can display JS dialogs at the same time. But if they're from the same SiteInstance and live in the same process, they can't. We should just change the dispatch of JS dialogs to be application modal instead, so it behaves consistently in all configurations. To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1568296/+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 1623003] Re: udev-generated /dev/disk/by-path names broken for virtio disks
** Changed in: ubuntu-z-systems Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1623003 Title: udev-generated /dev/disk/by-path names broken for virtio disks Status in systemd: Unknown Status in Ubuntu on IBM z Systems: Fix Committed Status in systemd package in Ubuntu: Fix Committed Bug description: The udev-generated /dev/disk/by-path names for virtio disks are broken on z Systems as they have the format virtio-pci-h.h.[-partn], where h.h. is the CCW devno of the virtio device representing the whole disk. Historically, the standard CCW naming was applied, which was ccw-h.h.[-partn] ---uname output--- Linux ubuntu 4.4.0-36-generic #55-Ubuntu SMP Thu Aug 11 18:05:09 UTC 2016 s390x s390x s390x GNU/Linux Machine Type = 2964-703 running KVM for IBM z Systems ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Install Ubuntu LTS 16.04.1 on KVM for IBM z Systems 1.1.1 2. Issue ls -l /dev/disk/by-path Userspace tool common name: udev The userspace tool has the following bit modes: 64-bit Userspace rpm: udev Userspace tool obtained from project website: na There are basically two problems with this: 1. The naming is technically incorrect, since the virtio devices on z are no PCI devices but CCW devices 2. Then naming based on virtio- is backwards incompatible. This may seem not to be an issue for Xenial but customers may be confused if they have been running Linux on KVM for IBM z before. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1623003/+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 1676081] Re: No wifi connection after suspend with a MacBook Pro
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- 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/1676081 Title: No wifi connection after suspend with a MacBook Pro Status in network-manager package in Ubuntu: Confirmed Status in wpa package in Ubuntu: Confirmed Bug description: I installed Ubuntu 16.10 on a MacBook Pro and, even though the bug should have been fixed in Xenial (see bug 1422143), I lose my wifi connection each time I get back from suspend (when opening the lid). # Expected behavior: Not losing the wifi connection. # Actual behavior: Wifi connection is lost all the time. # Workaround: The workaround explained in the comment 50 of the previous bug worked for me: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1422143/comments/50 Side effect: it closes the VPN connection if there was one. # Note: I've been advised to create a new bug for this (see https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1422143/comments/63) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1676081/+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 1676081] Re: No wifi connection after suspend with a MacBook Pro
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: wpa (Ubuntu) Status: New => Confirmed -- 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/1676081 Title: No wifi connection after suspend with a MacBook Pro Status in network-manager package in Ubuntu: Confirmed Status in wpa package in Ubuntu: Confirmed Bug description: I installed Ubuntu 16.10 on a MacBook Pro and, even though the bug should have been fixed in Xenial (see bug 1422143), I lose my wifi connection each time I get back from suspend (when opening the lid). # Expected behavior: Not losing the wifi connection. # Actual behavior: Wifi connection is lost all the time. # Workaround: The workaround explained in the comment 50 of the previous bug worked for me: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1422143/comments/50 Side effect: it closes the VPN connection if there was one. # Note: I've been advised to create a new bug for this (see https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1422143/comments/63) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1676081/+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 1676912] Re: Suspend - Freezing of tasks failed
This problem also appears whenn using Kernel 4.11 from the mainline ppa. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1676912 Title: Suspend - Freezing of tasks failed Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Recently I replaced Ubuntu 16.04 on my Lenovo Yoga 3 11 with Ubuntu Gnome 17.04 and since then sometimes my Laptop won't suspend when I close the lid. The power led does not blink like it is supposed to do and when I open the Laptop the lockscreen appears but freezes after a short time, followed by a blackscreen until eventually it reappears and allows me to unlock it. After that certain application can not be started anymore and would freeze if they were running before. These include Chrome, Gedit and Gnome System Monitor for example. Also my Laptop will not connect to my WLAN until I restart it. In syslog I found the line: "Freezing of tasks failed after 20.005 seconds (18 tasks refusing to freeze, wq_busy=0):" According to syslog network-nanaeger whoopsie cups-browsed wpa-supplicant geoclue packagekitd several evolution-related processes goa-daemon gnome-software geary dropbox deja-dup-monitor are responsible. I tried disabling some of them, but it did not solve the problem. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: systemd 232-19 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Mar 28 16:27:34 2017 InstallationDate: Installed on 2017-03-24 (3 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) MachineType: LENOVO 80J8 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic.efi.signed root=UUID=8c63f102-527f-412a-bafe-7b9075ea6b56 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2015 dmi.bios.vendor: LENOVO dmi.bios.version: B8CN31WW(V2.09) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Paganini dmi.board.vendor: LENOVO dmi.board.version: 31900058 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 3 11 dmi.modalias: dmi:bvnLENOVO:bvrB8CN31WW(V2.09):bd07/15/2015:svnLENOVO:pn80J8:pvrLenovoYoga311:rvnLENOVO:rnPaganini:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga311: dmi.product.name: 80J8 dmi.product.version: Lenovo Yoga 3 11 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1676912/+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 1677259] Re: [regression] Search string not replaced in app drawer after Super+A
** Branch linked: lp:~mzanetti/unity8/fix-drawer-search-reset -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1677259 Title: [regression] Search string not replaced in app drawer after Super+A Status in Canonical System Image: In Progress Status in unity8 package in Ubuntu: In Progress Bug description: Steps: * open the app drawer * type "foo" * close the app drawer * press Super+A to open the app drawer * type "bar" Expected: * search term is "bar" Current: * search term is "foobar" ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: unity8 8.15+17.04.20170321-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Wed Mar 29 16:00:37 2017 InstallationDate: Installed on 2016-05-06 (326 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: unity8 UpgradeStatus: Upgraded to zesty on 2016-11-22 (127 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1677259/+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 1677259] Re: [regression] Search string not replaced in app drawer after Super+A
** Changed in: unity8 (Ubuntu) Status: Triaged => In Progress ** Changed in: canonical-devices-system-image Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1677259 Title: [regression] Search string not replaced in app drawer after Super+A Status in Canonical System Image: In Progress Status in unity8 package in Ubuntu: In Progress Bug description: Steps: * open the app drawer * type "foo" * close the app drawer * press Super+A to open the app drawer * type "bar" Expected: * search term is "bar" Current: * search term is "foobar" ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: unity8 8.15+17.04.20170321-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Wed Mar 29 16:00:37 2017 InstallationDate: Installed on 2016-05-06 (326 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: unity8 UpgradeStatus: Upgraded to zesty on 2016-11-22 (127 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1677259/+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 1188475] Re: ldap group doesn't work
Thank you for taking the time to report this bug and helping to make Ubuntu better. Sorry this got dropped over the years. This bug is present in Debian as well and Ubuntu currently does not make any changes to the Debian package. Therefore, this bug would be best fixed directly in Debian, and then Ubuntu will pick up the fix automatically. Would you mind filing a bug with Debian please? ** Tags added: bitesize needs-upstream-report ** Changed in: cyrus-sasl2 (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1188475 Title: ldap group doesn't work Status in cyrus-sasl2 package in Ubuntu: Triaged Bug description: Hello! I wrote almost the same mail to sasl mail list, but , I guess, it is good to fix in 12.04... This bug exists in 2.1.26 , and in 2.1.25 which is in 12.04 Problem is that after user is authentificated with ldap bind , ldap connection for checking user in group ( lak_group_member function ) is made with this user's bind, not bind parameters from config file. User can not ( and have not in our case- I don't know why , but this is not real problem ) have access to ldap groups. And so, authentication is always fail. I added unbind and anonymous bind ( enough in our case): /var/local/files/sasl/cyrus-sasl-2.1.26/saslauthd# diff -ur lak.c.orig lak.c --- lak.c.orig2013-06-07 09:15:20.098788278 +0400 +++ lak.c2013-06-07 09:22:31.504774185 +0400 @@ -1342,6 +1342,10 @@ if (rc != LAK_OK) goto done; +lak_unbind (lak ); +rc = lak_bind(lak, ""); + + rc = ldap_search_st(lak->ld, group_search_base, lak->conf->group_scope, group_filter, (char **) group_attrs, 0, &(lak->conf->timeout), &res); switch (rc) { case LDAP_SUCCESS: but, it is obvoius that rebind should be done with credintials from config, but this is over my head :-( Could you, please, fix this bug correctly? Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1188475/+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 1676621] Re: cups : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed
Hi @Tim, This bug isn't a duplicate of that bug. That bug is the original failure and has to do with subprocesses exiting failure. This bug is about broken package dependencies and I can't install cups now. They are certainly related, but that bug doesn't talk about how to fix it. ** This bug is no longer a duplicate of bug 1642966 package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1676621 Title: cups : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed Status in cups package in Ubuntu: Confirmed Bug description: This is related to this bug https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642790 After `sudo apt-get -f install`, it removed cups and marked a bunch of cups packages as unnecessary `sudo apt-get autoremove` removed them. Now when I try to re-install cups, I get this error: ``` ☀ sudo apt-get install cups cups-daemon cups-core-drivers Mod master Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: cups : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed Depends: libcupscgi1 (>= 1.4.2) but it is not going to be installed Depends: libcupsmime1 (>= 1.4.0) but it is not going to be installed Recommends: printer-driver-gutenprint but it is not going to be installed cups-core-drivers : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed cups-daemon : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed Depends: libcupsmime1 (>= 1.5.0) but it is not going to be installed Recommends: cups-browsed but it is not going to be installed E: Unable to correct problems, you have held broken packages. ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1676621/+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 1676621] Re: cups : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed
Robie, this bug report contains most of the workarounds for this problem. How should we treat it? Duplicate of bug 1642966? Duplicate of bug 1676380? Independent of all the other bugs? Or master bug for all the other bugs? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1676621 Title: cups : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed Status in cups package in Ubuntu: Confirmed Bug description: This is related to this bug https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642790 After `sudo apt-get -f install`, it removed cups and marked a bunch of cups packages as unnecessary `sudo apt-get autoremove` removed them. Now when I try to re-install cups, I get this error: ``` ☀ sudo apt-get install cups cups-daemon cups-core-drivers Mod master Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: cups : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed Depends: libcupscgi1 (>= 1.4.2) but it is not going to be installed Depends: libcupsmime1 (>= 1.4.0) but it is not going to be installed Recommends: printer-driver-gutenprint but it is not going to be installed cups-core-drivers : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed cups-daemon : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed Depends: libcupsmime1 (>= 1.5.0) but it is not going to be installed Recommends: cups-browsed but it is not going to be installed E: Unable to correct problems, you have held broken packages. ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1676621/+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 1676621] Re: cups : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed
@Tim, if I missed something about fixing the packages, happy to be wrong :-) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1676621 Title: cups : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed Status in cups package in Ubuntu: Confirmed Bug description: This is related to this bug https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642790 After `sudo apt-get -f install`, it removed cups and marked a bunch of cups packages as unnecessary `sudo apt-get autoremove` removed them. Now when I try to re-install cups, I get this error: ``` ☀ sudo apt-get install cups cups-daemon cups-core-drivers Mod master Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: cups : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed Depends: libcupscgi1 (>= 1.4.2) but it is not going to be installed Depends: libcupsmime1 (>= 1.4.0) but it is not going to be installed Recommends: printer-driver-gutenprint but it is not going to be installed cups-core-drivers : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed cups-daemon : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed Depends: libcupsmime1 (>= 1.5.0) but it is not going to be installed Recommends: cups-browsed but it is not going to be installed E: Unable to correct problems, you have held broken packages. ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1676621/+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 1677305] Re: /dev/sda1 is checked at every boot instead of once every N mounts
** Summary changed: - /dev/sda1 is checked at every boot instead of every 31 mounts + /dev/sda1 is checked at every boot instead of once every N mounts -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1677305 Title: /dev/sda1 is checked at every boot instead of once every N mounts Status in systemd package in Ubuntu: New Bug description: Every time I login I get the message: *** /dev/sda1 will be checked for errors at next reboot *** /dev/sda1 is my root partition. fsck was successfully run, but it looks like systemd is not aware of this, so fsck will be run again at the next boot. root@serverlinux:~# lsb_release -rd Description:Ubuntu 16.04.2 LTS Release:16.04 root@serverlinux:~# LANG=en_US apt-cache policy systemd systemd: Installed: 229-4ubuntu16 Candidate: 229-4ubuntu16 Version table: *** 229-4ubuntu16 500 500 http://it.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu10 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 229-4ubuntu4 500 500 http://it.archive.ubuntu.com/ubuntu xenial/main amd64 Packages root@serverlinux:~# cat /run/initramfs/fsck.log Log of fsck -C -a -T -t ext4 /dev/sda1 Wed Mar 29 00:26:26 2017 /dev/sda1: clean, 612205/6725632 files, 17326020/2688 blocks (check in 2 mounts) Wed Mar 29 00:26:26 2017 root@serverlinux:~# LANG=en_US ls -l /run/initramfs/ total 4 -rw-r--r-- 1 root root 0 Mar 29 02:26 fsck-root -rw-r--r-- 1 root root 194 Mar 29 02:26 fsck.log [There's a discrepancy between the time in fsck.log and the time of the fsck.log but I suspect this is a UTC/CEST issue: root@serverlinux:~# LANG=en_US date Wed Mar 29 17:43:17 CEST 2017 root@serverlinux:~# LANG=en_US date -u Wed Mar 29 15:43:21 UTC 2017 The system was planned for reboot at Mar 29 2:25 CEST (Mar 29 0:25 UTC)] This is the content of /etc/fstab: root@serverlinux:~# cat /etc/fstab # proc/proc procnodev,noexec,nosuid 0 0 # / was on /dev/sda1 during installation UUID=c50edc7d-9f0b-4958-8e44-00bb5433ba42 / ext4 errors=remount-ro,noatime,nodiratime,commit=60 0 1 # swap was on /dev/sda5 during installation UUID=93b413bc-8663-44b4-81de-1a225a2f90da noneswapsw 0 0 # /dev/sdb1 in ext4 250GB UUID=5f987a15-685a-4d2b-adf9-8bcde0eca04e /data ext4 errors=remount-ro,noatime,nodiratime,commit=60 0 1 The output of LANG=en_US dumpe2fs /dev/sda1 is: root@serverlinux:~# LANG=en_US dumpe2fs /dev/sda1 Filesystem created: Thu Apr 15 15:23:07 2010 Last mount time: Wed Mar 29 02:26:26 2017 Last write time: Wed Mar 29 02:26:26 2017 Mount count: 30 Maximum mount count: 31 Last checked: Tue Sep 6 02:46:17 2016 Check interval: 15552000 (6 months) Next check after: Sun Mar 5 01:46:17 2017 For some reason, "Last checked:" time is not up to date (see above for the content of /run/initramfs/fsck.log), hence the problem (I suppose). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1677305/+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 1677313] [NEW] Temporary keyboard and mouse freeze (5+ minutes) while copying big file
Public bug reported: While copying a big file from SSD to HD the whole interface froze, the only exception being that rhythmbox kept playing the radio stream with just 2 or 3 very minor hicups. After the copy finished, all went back to normal. This has happened before but only with very large files (> 1GB). With small files no problems arise. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8.2 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: Wed Mar 29 16:41:50 2017 DistUpgraded: 2016-10-29 20:59:03,871 DEBUG icon theme changed, re-reading DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems HD Graphics 530 [1179:f840] InstallationDate: Installed on 2016-05-16 (316 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:5652 IMC Networks Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TOSHIBA SATELLITE P50-C ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-41-generic root=UUID=244d0104-69e0-4b0e-98a5-f56d42d63020 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to yakkety on 2016-10-29 (150 days ago) dmi.bios.date: 10/08/2015 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.20 dmi.board.name: 06F4 dmi.board.vendor: FF50 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr1.20:bd10/08/2015:svnTOSHIBA:pnSATELLITEP50-C:pvrPSPUEE-00C008EP:rvnFF50:rn06F4:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.name: SATELLITE P50-C dmi.product.version: PSPUEE-00C008EP dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.10.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Wed Mar 29 08:51:32 2017 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) Unknown chipset: NV117 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu yakkety -- 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/1677313 Title: Temporary keyboard and mouse freeze (5+ minutes) while copying big file Status in xorg package in Ubuntu: New Bug description: While copying a big file from SSD to HD the whole interface froze, the only exception being that rhythmbox kept playing the radio stream with just 2 or 3 very minor hicups. After the copy finished, all went back to normal. This has happened before but only with very large files (> 1GB). With small files no problems arise. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8.2 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: Wed Mar 29 16:41:50 2017 DistUpgraded: 2016-10-29 20:59:03,871 DEBUG icon theme changed, re-reading DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too te
[Touch-packages] [Bug 1590590] Re: Touchpad not recognized on Dell Latitude E7470 Ultrabook
As far as I can tell the patch for hwdb sensitivity for Dell Latitude E7470 is shipped in zesty now. Is anything else required to have this resolved in zesty? Or hwdb update is all that is needed here? If that is the case, then we can remove all the other packages marked as affected and simply SRU the hwdb update. ** Also affects: xserver-xorg-input-synaptics (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: xserver-xorg-input-synaptics (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1590590 Title: Touchpad not recognized on Dell Latitude E7470 Ultrabook Status in linux package in Ubuntu: Triaged Status in systemd package in Ubuntu: Fix Released Status in xserver-xorg-input-synaptics package in Ubuntu: Confirmed Status in linux source package in Xenial: New Status in systemd source package in Xenial: New Status in xserver-xorg-input-synaptics source package in Xenial: New Status in linux source package in Yakkety: New Status in systemd source package in Yakkety: New Status in xserver-xorg-input-synaptics source package in Yakkety: New Bug description: Expected: Touchpad settings available in Mouse & Touchpad Settings dialog Actual result: Touchpad settings missing entirely Details: The touchpad on my Dell Ultrabook (Latitude E7470) functions mostly. The settings for the touchpad are not available at all in the Mouse and Touchpad settings (see http://i.imgur.com/YRGiOrj.png). Two-finger scrolling works as expected except it's using "Natural Scrolling" by default and there is no way to change it. xinput list does not display a touchpad at all: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ ELAN Touchscreenid=11 [slave pointer (2)] ⎜ ↳ ImPS/2 Generic Wheel Mouse id=13 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ Integrated_Webcam_FHD id=10 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=12 [slave keyboard (3)] ↳ Dell WMI hotkeysid=14 [slave keyboard (3)] ↳ DELL Wireless hotkeys id=15 [slave keyboard (3)] /proc/bus/input/devices lists the device as a "Generic Wheel Mouse" Output of `lsb_release -rd`: Description: Ubuntu 16.04 LTS Release: 16.04 xserver-xorg-input-synaptics version information: xserver-xorg-input-synaptics: Installed: 1.8.2-1ubuntu3 Candidate: 1.8.2-1ubuntu3 Version table: *** 1.8.2-1ubuntu3 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/linux/+bug/1590590/+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 1676621] Re: cups : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed
** This bug has been marked a duplicate of bug 1642966 package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1676621 Title: cups : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed Status in cups package in Ubuntu: Confirmed Bug description: This is related to this bug https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642790 After `sudo apt-get -f install`, it removed cups and marked a bunch of cups packages as unnecessary `sudo apt-get autoremove` removed them. Now when I try to re-install cups, I get this error: ``` ☀ sudo apt-get install cups cups-daemon cups-core-drivers Mod master Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: cups : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed Depends: libcupscgi1 (>= 1.4.2) but it is not going to be installed Depends: libcupsmime1 (>= 1.4.0) but it is not going to be installed Recommends: printer-driver-gutenprint but it is not going to be installed cups-core-drivers : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed cups-daemon : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed Depends: libcupsmime1 (>= 1.5.0) but it is not going to be installed Recommends: cups-browsed but it is not going to be installed E: Unable to correct problems, you have held broken packages. ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1676621/+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 1676621] Re: cups : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed
** This bug is no longer a duplicate of bug 1676380 Update to cups-daemon 2.1.3-4ubuntu0.2 results in maintainer script failures -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1676621 Title: cups : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed Status in cups package in Ubuntu: Confirmed Bug description: This is related to this bug https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642790 After `sudo apt-get -f install`, it removed cups and marked a bunch of cups packages as unnecessary `sudo apt-get autoremove` removed them. Now when I try to re-install cups, I get this error: ``` ☀ sudo apt-get install cups cups-daemon cups-core-drivers Mod master Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: cups : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed Depends: libcupscgi1 (>= 1.4.2) but it is not going to be installed Depends: libcupsmime1 (>= 1.4.0) but it is not going to be installed Recommends: printer-driver-gutenprint but it is not going to be installed cups-core-drivers : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed cups-daemon : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed Depends: libcupsmime1 (>= 1.5.0) but it is not going to be installed Recommends: cups-browsed but it is not going to be installed E: Unable to correct problems, you have held broken packages. ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1676621/+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 1677293] Re: pulseaudio crashed with SIGSEGV in avahi_client_get_state()
*** This bug is a duplicate of bug 1583840 *** https://bugs.launchpad.net/bugs/1583840 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1583840, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1677293/+attachment/4849837/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1677293/+attachment/4849840/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1677293/+attachment/4849842/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1677293/+attachment/4849843/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1677293/+attachment/4849845/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1677293/+attachment/4849847/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1677293/+attachment/4849848/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1583840 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1677293 Title: pulseaudio crashed with SIGSEGV in avahi_client_get_state() Status in pulseaudio package in Ubuntu: New Bug description: A random pulseaudio crash. ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: pulseaudio 1:10.0-1ubuntu1 Uname: Linux 4.10.6-041006-lowlatency x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bonnaudl 9405 F pulseaudio CurrentDesktop: MATE Date: Wed Mar 29 17:13:58 2017 ExecutablePath: /usr/bin/pulseaudio ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 11 SourcePackage: pulseaudio StacktraceTop: avahi_client_get_state () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3 ?? () from /usr/lib/pulse-10.0/modules/module-zeroconf-publish.so ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 pa_mainloop_dispatch () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 Title: pulseaudio crashed with SIGSEGV in avahi_client_get_state() UpgradeStatus: Upgraded to zesty on 2017-03-12 (17 days ago) UserGroups: adm admin cdrom dialout lpadmin lxd plugdev sambashare staff dmi.bios.date: 03/25/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: HM77-HT dmi.board.vendor: ASRock 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.:bvrP1.50:bd03/25/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM77-HT:rvr: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1677293/+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 1677305] [NEW] /dev/sda1 is checked at every boot instead of every 31 mounts
Public bug reported: Every time I login I get the message: *** /dev/sda1 will be checked for errors at next reboot *** /dev/sda1 is my root partition. fsck was successfully run, but it looks like systemd is not aware of this, so fsck will be run again at the next boot. root@serverlinux:~# lsb_release -rd Description:Ubuntu 16.04.2 LTS Release:16.04 root@serverlinux:~# LANG=en_US apt-cache policy systemd systemd: Installed: 229-4ubuntu16 Candidate: 229-4ubuntu16 Version table: *** 229-4ubuntu16 500 500 http://it.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu10 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 229-4ubuntu4 500 500 http://it.archive.ubuntu.com/ubuntu xenial/main amd64 Packages root@serverlinux:~# cat /run/initramfs/fsck.log Log of fsck -C -a -T -t ext4 /dev/sda1 Wed Mar 29 00:26:26 2017 /dev/sda1: clean, 612205/6725632 files, 17326020/2688 blocks (check in 2 mounts) Wed Mar 29 00:26:26 2017 root@serverlinux:~# LANG=en_US ls -l /run/initramfs/ total 4 -rw-r--r-- 1 root root 0 Mar 29 02:26 fsck-root -rw-r--r-- 1 root root 194 Mar 29 02:26 fsck.log [There's a discrepancy between the time in fsck.log and the time of the fsck.log but I suspect this is a UTC/CEST issue: root@serverlinux:~# LANG=en_US date Wed Mar 29 17:43:17 CEST 2017 root@serverlinux:~# LANG=en_US date -u Wed Mar 29 15:43:21 UTC 2017 The system was planned for reboot at Mar 29 2:25 CEST (Mar 29 0:25 UTC)] This is the content of /etc/fstab: root@serverlinux:~# cat /etc/fstab # proc/proc procnodev,noexec,nosuid 0 0 # / was on /dev/sda1 during installation UUID=c50edc7d-9f0b-4958-8e44-00bb5433ba42 / ext4 errors=remount-ro,noatime,nodiratime,commit=60 0 1 # swap was on /dev/sda5 during installation UUID=93b413bc-8663-44b4-81de-1a225a2f90da noneswapsw 0 0 # /dev/sdb1 in ext4 250GB UUID=5f987a15-685a-4d2b-adf9-8bcde0eca04e /data ext4 errors=remount-ro,noatime,nodiratime,commit=60 0 1 The output of LANG=en_US dumpe2fs /dev/sda1 is: root@serverlinux:~# LANG=en_US dumpe2fs /dev/sda1 Filesystem created: Thu Apr 15 15:23:07 2010 Last mount time: Wed Mar 29 02:26:26 2017 Last write time: Wed Mar 29 02:26:26 2017 Mount count: 30 Maximum mount count: 31 Last checked: Tue Sep 6 02:46:17 2016 Check interval: 15552000 (6 months) Next check after: Sun Mar 5 01:46:17 2017 For some reason, "Last checked:" time is not up to date (see above for the content of /run/initramfs/fsck.log), hence the problem (I suppose). ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1677305 Title: /dev/sda1 is checked at every boot instead of every 31 mounts Status in systemd package in Ubuntu: New Bug description: Every time I login I get the message: *** /dev/sda1 will be checked for errors at next reboot *** /dev/sda1 is my root partition. fsck was successfully run, but it looks like systemd is not aware of this, so fsck will be run again at the next boot. root@serverlinux:~# lsb_release -rd Description:Ubuntu 16.04.2 LTS Release:16.04 root@serverlinux:~# LANG=en_US apt-cache policy systemd systemd: Installed: 229-4ubuntu16 Candidate: 229-4ubuntu16 Version table: *** 229-4ubuntu16 500 500 http://it.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu10 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 229-4ubuntu4 500 500 http://it.archive.ubuntu.com/ubuntu xenial/main amd64 Packages root@serverlinux:~# cat /run/initramfs/fsck.log Log of fsck -C -a -T -t ext4 /dev/sda1 Wed Mar 29 00:26:26 2017 /dev/sda1: clean, 612205/6725632 files, 17326020/2688 blocks (check in 2 mounts) Wed Mar 29 00:26:26 2017 root@serverlinux:~# LANG=en_US ls -l /run/initramfs/ total 4 -rw-r--r-- 1 root root 0 Mar 29 02:26 fsck-root -rw-r--r-- 1 root root 194 Mar 29 02:26 fsck.log [There's a discrepancy between the time in fsck.log and the time of the fsck.log but I suspect this is a UTC/CEST issue: root@serverlinux:~# LANG=en_US date Wed Mar 29 17:43:17 CEST 2017 root@serverlinux:~# LANG=en_US date -u Wed Mar 29 15:43:21 UTC 2017 The system was planned for reboot at Mar 29 2:25 CEST (Mar 29 0:25 UTC)] This is the content of /etc/fstab: root@serverlinux:~# cat /etc/fstab # proc/proc procnodev,noexec,nosuid 0 0
[Touch-packages] [Bug 1644530] Re: keepalived fails to restart cleanly due to the wrong systemd settings
** Changed in: systemd (Ubuntu) Assignee: Dimitri John Ledkov (xnox) => (unassigned) ** Changed in: systemd (Ubuntu) Milestone: ubuntu-17.03 => None -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1644530 Title: keepalived fails to restart cleanly due to the wrong systemd settings Status in keepalived package in Ubuntu: Fix Released Status in systemd package in Ubuntu: New Status in keepalived source package in Xenial: Fix Committed Status in systemd source package in Xenial: New Status in keepalived package in Debian: New Bug description: [Impact] * Restarts of keepalived can leave stale processes with the old configuration around. * The systemd detection of the MainPID is suboptimal, and combined with not waiting on signals being handled it can fail on second restart killing the (still) remaining process of the first start. * Upstream has a PIDFile statement, this has proven to avoid the issue in the MainPID guessing code of systemd. [Test Case] * Set up keepalived, the more complex the config is the "bigger" is the reace window, below in the description is a trivial sample config that works well. * As a test run the loop restarting the service head-to-head while staying under the max-restart limit $ for j in $(seq 1 20); do sleep 11s; time for i in $(seq 1 5); do sudo systemctl restart keepalived; sudo systemctl status keepalived | egrep 'Main.*exited'; done; done Expectation: no output other than timing Without fix: sometimes MainPIDs do no more exist, in these cases the child processes are the "old" ones from last execution with the old config. [Regression Potential] * Low because * A PIDFile statement is recommended by systemd for type=forking services anyway. * Upstream keepalived has this statement in their service file * By the kind of change, it should have no functional impact to other parts of the service other than for the PID detection of the job by Systemd. * Yet regression potential is never zero. There might be the unlikely case, which were considered working before due to a new config not properly being picked up. After the fix they will behave correctly and might show up as false-positives then if e.g. config was bad. [Other Info] * Usually a fix has to be in at least the latest Development release before SRUing it. But as I outlined below in later Releases than Xenial systemd seems to have improved making this change not-required. We haven't identified the bits for this (there is a bug task here), and they might as well be very complex. I think it is correct to fix Xenial in this regard with the simple change to the service file for now. * To eventually match I created a Debian bug task to ask them for the inclusion of the PIDFile so it can slowly tickle back down to newer Ubuntu Releases - also there more often people run backports where the issue might occur on older systemd versions (just as it does for us on Xenial) --- Because "PIDFile=" directive is missing in the systemd unit file, keepalived sometimes fails to kill all old processes. The old processes remain with old settings and cause unexpected behaviors. The detail of this bug is described in this ticket in upstream: https://github.com/acassen/keepalived/issues/443. The official systemd unit file is available since version 1.2.24 by this commit: https://github.com/acassen/keepalived/commit/635ab69afb44cd8573663e62f292c6bb84b44f15 This includes "PIDFile" directive correctly: PIDFile=/var/run/keepalived.pid We should go the same way. I am using Ubuntu 16.04.1, kernel 4.4.0-45-generic. Package: keepalived Version: 1.2.19-1 === How to reproduce: I used the two instances of Ubuntu 16.04.2 on DigitalOcean: Configurations -- MASTER server's /etc/keepalived/keepalived.conf: vrrp_script chk_nothing { script "/bin/true" interval 2 } vrrp_instance G1 { interface eth1 state BACKUP priority 100 virtual_router_id 123 unicast_src_ip unicast_peer { } track_script { chk_nothing } } BACKUP server's /etc/keepalived/keepalived.conf: vrrp_script chk_nothing { script "/bin/true" interval 2 } vrrp_instance G1 { interface eth1 state MASTER priority 200 virtual_router_id 123 unicast_src_ip unicast_peer { } track_script { chk_nothing } } Loop based probing for the Error to exist: -- After the setup above start keepalived on both servers: $ sudo systemctl start keepalived.service Then run the follow
[Touch-packages] [Bug 1656801] Re: ntp: changing the default config from server to pool broke the dhcp hook
I've uploaded the patch in comment #3 to xenial. I've also added some SRU bits to the description -- if either Robie or Philip could maybe add some test case steps, that would be swell. Thanks! ** Description changed: In 1:4.2.8p3+dfsg-1, the default config was changed to "Use pool instead of server". This needs a corresponding update to /etc/dhcp/dhclient-exit-hooks.d/ntp, since the DHCP specified servers now get added to the default pool config instead of replacing them. This affects Xenial only as the Yakkety build includes the upstream fix (1:4.2.8p7+dfsg-1). - Original Debian busg https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809344 + Original Debian busg https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809344 & https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806676 + + [Test Case] + + mterry isn't sure on this. Robie or Philip, do you have simple + instructions? + + [Regression Potential] + + As noted in comments #1 and #2, this SRU might surface an issue if the + user is receiving a broken set of NTP servers. + + And as noted in comment #4, some people might be hackishly using the + distinction between spaces and tabs in the config file to trick our + current hook. Debian has gotten rid of that distinction, so that hack + will stop working on distro-upgrade anyway. The fix is *probably* going + to help more people who unintentionally mixed the two up rather than the + few that are relying on that bug. But that bit can be easily dropped + from the SRU if ya like. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1656801 Title: ntp: changing the default config from server to pool broke the dhcp hook Status in ntp package in Ubuntu: Fix Released Status in ntp source package in Xenial: Triaged Status in ntp package in Debian: Fix Released Bug description: In 1:4.2.8p3+dfsg-1, the default config was changed to "Use pool instead of server". This needs a corresponding update to /etc/dhcp/dhclient-exit-hooks.d/ntp, since the DHCP specified servers now get added to the default pool config instead of replacing them. This affects Xenial only as the Yakkety build includes the upstream fix (1:4.2.8p7+dfsg-1). Original Debian busg https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809344 & https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806676 [Test Case] mterry isn't sure on this. Robie or Philip, do you have simple instructions? [Regression Potential] As noted in comments #1 and #2, this SRU might surface an issue if the user is receiving a broken set of NTP servers. And as noted in comment #4, some people might be hackishly using the distinction between spaces and tabs in the config file to trick our current hook. Debian has gotten rid of that distinction, so that hack will stop working on distro-upgrade anyway. The fix is *probably* going to help more people who unintentionally mixed the two up rather than the few that are relying on that bug. But that bit can be easily dropped from the SRU if ya like. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1656801/+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 1672941] Re: FTBFS with older versions of OpenSSL
unsubscribing sponsors since that was uploaded and is just waiting for queue review -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1672941 Title: FTBFS with older versions of OpenSSL Status in cyrus-sasl2 package in Ubuntu: Fix Committed Bug description: cyrus-sasl2 currently FTBFS in Zesty because we have an older version of OpenSSL than in Debian (1.0.2 vs 1.1.0). There was a patch upstream to fix this: https://github.com/cyrusimap/cyrus- sasl/commit/ccb394dc857c0f1ef03a6be5011b5aedc1dbf042 debdiff attached. Tested building with pbuilder. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1672941/+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 1677301] [NEW] Investigate if tests can emulate touch devices
Public bug reported: Investigate if there is a way to create an automated test environment that resembles devices (phone, tablet) as closely as possible (e.g. run under Unity8, simulate touch events, with the right resolutions, etc.) ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Assignee: Florian Boucault (fboucault) Status: New ** Tags: next-candidates -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1677301 Title: Investigate if tests can emulate touch devices Status in webbrowser-app package in Ubuntu: New Bug description: Investigate if there is a way to create an automated test environment that resembles devices (phone, tablet) as closely as possible (e.g. run under Unity8, simulate touch events, with the right resolutions, etc.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1677301/+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 1677300] [NEW] Investigate what manual tests could be automated
Public bug reported: The webbrowser-app test plan (currently at https://wiki.ubuntu.com/Process/Merges/TestPlan/webbrowser-app , see bug #1677298) has a number of tests that could be automated, with some development effort. Let’s try to identify which ones can be automated, and file followup bugs to track their automation. ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Assignee: Andrew Hayzen (ahayzen) Status: New ** Tags: next-candidates -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1677300 Title: Investigate what manual tests could be automated Status in webbrowser-app package in Ubuntu: New Bug description: The webbrowser-app test plan (currently at https://wiki.ubuntu.com/Process/Merges/TestPlan/webbrowser-app , see bug #1677298) has a number of tests that could be automated, with some development effort. Let’s try to identify which ones can be automated, and file followup bugs to track their automation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1677300/+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 1623003] Re: udev-generated /dev/disk/by-path names broken for virtio disks
** Changed in: systemd (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1623003 Title: udev-generated /dev/disk/by-path names broken for virtio disks Status in systemd: Unknown Status in Ubuntu on IBM z Systems: Confirmed Status in systemd package in Ubuntu: Fix Committed Bug description: The udev-generated /dev/disk/by-path names for virtio disks are broken on z Systems as they have the format virtio-pci-h.h.[-partn], where h.h. is the CCW devno of the virtio device representing the whole disk. Historically, the standard CCW naming was applied, which was ccw-h.h.[-partn] ---uname output--- Linux ubuntu 4.4.0-36-generic #55-Ubuntu SMP Thu Aug 11 18:05:09 UTC 2016 s390x s390x s390x GNU/Linux Machine Type = 2964-703 running KVM for IBM z Systems ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Install Ubuntu LTS 16.04.1 on KVM for IBM z Systems 1.1.1 2. Issue ls -l /dev/disk/by-path Userspace tool common name: udev The userspace tool has the following bit modes: 64-bit Userspace rpm: udev Userspace tool obtained from project website: na There are basically two problems with this: 1. The naming is technically incorrect, since the virtio devices on z are no PCI devices but CCW devices 2. Then naming based on virtio- is backwards incompatible. This may seem not to be an issue for Xenial but customers may be confused if they have been running Linux on KVM for IBM z before. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1623003/+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 1677295] [NEW] Add automated check that prevents merging if test coverage decreases
Public bug reported: Once code coverage is enabled (see bug #1677292), it would be good to set up a mechanism that prevents merging if a merge request decreases significantly the code coverage. There would need to be a way to manually override this mechanism, of course. ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New ** Tags: next-candidates -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1677295 Title: Add automated check that prevents merging if test coverage decreases Status in webbrowser-app package in Ubuntu: New Bug description: Once code coverage is enabled (see bug #1677292), it would be good to set up a mechanism that prevents merging if a merge request decreases significantly the code coverage. There would need to be a way to manually override this mechanism, of course. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1677295/+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 1677290] [NEW] Add automated tests run for all MRs on staging branch
Public bug reported: Currently the system apps jenkins instance doesn't run CI for merge requests targeting lp:webbrowser-app/staging. It should. ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New ** Tags: next-candidates -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1677290 Title: Add automated tests run for all MRs on staging branch Status in webbrowser-app package in Ubuntu: New Bug description: Currently the system apps jenkins instance doesn't run CI for merge requests targeting lp:webbrowser-app/staging. It should. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1677290/+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 1677291] [NEW] Implement readable feedback on automated tests on MRs
Public bug reported: The output from jenkins on merge requests is hard to read. It could be made much more developer-friendly allow seeing at a glance what tests passed and what tests failed without having to navigate through several layers of jenkins. ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New ** Tags: next-candidates -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1677291 Title: Implement readable feedback on automated tests on MRs Status in webbrowser-app package in Ubuntu: New Bug description: The output from jenkins on merge requests is hard to read. It could be made much more developer-friendly allow seeing at a glance what tests passed and what tests failed without having to navigate through several layers of jenkins. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1677291/+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 1677292] [NEW] Generate test coverage metrics
Public bug reported: We need to enable code coverage metrics in webbrowser-app. Ideally this would include coverage from the QML tests, not just C++ unit tests. ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Assignee: Florian Boucault (fboucault) Status: New ** Tags: next-candidates ** Description changed: - We need to enable code coverage metrics in CI for webbrowser-app. + We need to enable code coverage metrics in webbrowser-app. Ideally this + would include coverage from the QML tests, not just C++ unit tests. ** Changed in: webbrowser-app (Ubuntu) Assignee: (unassigned) => Florian Boucault (fboucault) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1677292 Title: Generate test coverage metrics Status in webbrowser-app package in Ubuntu: New Bug description: We need to enable code coverage metrics in webbrowser-app. Ideally this would include coverage from the QML tests, not just C++ unit tests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1677292/+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 1677294] [NEW] Publish test coverage metrics automatically
Public bug reported: Code coverage metrics, once enabled (see bug #1677292), should be automatically published by the system apps jenkins instance. ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New ** Tags: next-candidates -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1677294 Title: Publish test coverage metrics automatically Status in webbrowser-app package in Ubuntu: New Bug description: Code coverage metrics, once enabled (see bug #1677292), should be automatically published by the system apps jenkins instance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1677294/+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 1677298] [NEW] Transfer manual tests from wiki to bzr branch
Public bug reported: The webbrowser-app test plan is currently published at https://wiki.ubuntu.com/Process/Merges/TestPlan/webbrowser-app. It should be transferred to a text file in the code repository. ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Assignee: Andrew Hayzen (ahayzen) Status: New ** Tags: next-candidates -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1677298 Title: Transfer manual tests from wiki to bzr branch Status in webbrowser-app package in Ubuntu: New Bug description: The webbrowser-app test plan is currently published at https://wiki.ubuntu.com/Process/Merges/TestPlan/webbrowser-app. It should be transferred to a text file in the code repository. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1677298/+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 1253784] Re: Webbrowser doesn't respect the HTML5 "required" attribute
** Tags added: next-candidates -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1253784 Title: Webbrowser doesn't respect the HTML5 "required" attribute Status in Oxide: Triaged Status in webbrowser-app: Invalid Status in webbrowser-app package in Ubuntu: Confirmed Bug description: The browser should prevent the form from being submitted ex: http://www.w3schools.com/html/tryhtml5_input_required.htm To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1253784/+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 1672444] Re: Negative number of tabs at left
** Tags added: next-candidates -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1672444 Title: Negative number of tabs at left Status in webbrowser-app package in Ubuntu: Confirmed Bug description: I am not able to reproduce it. I opened the webbrowser-app after updating the silo to the new build, and maximized it. After minimizing it again, I spotted the negative number of hidden tabs at left. Not sure what steps do trigger this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1672444/+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 1655782] Re: [FFe] Elfdalian layout + merge with Debian 2.19-1
I've uploaded this to zesty, thanks Gunnar! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1655782 Title: [FFe] Elfdalian layout + merge with Debian 2.19-1 Status in xkeyboard-config: Unknown Status in xkeyboard-config package in Ubuntu: In Progress Bug description: Please add the Elfdalian keyboard layout which has been added upstream (see the Freedesktop bug report). I also propose that we take this opportunity to merge with Debian xkeyboard-config 2.19-1. To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/1655782/+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 1656252] Re: Applications fail to start on the second use
** Tags added: next-candidates -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1656252 Title: Applications fail to start on the second use Status in Canonical System Image: In Progress Status in address-book-app package in Ubuntu: In Progress Status in camera-app package in Ubuntu: In Progress Status in gallery-app package in Ubuntu: In Progress Status in ubuntu-app-launch package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Invalid Status in webbrowser-app package in Ubuntu: New Bug description: zesty desktop unity8 session snap 349 Test Case: 1. Launch the webbrowser from the app scope 2. close it (or the app crashes) 3. Launch the webbrowser from the app scope Expected result: It starts twice Actual result It does not always starts and it hangs on the launch window (blank window, with the webbrowser icon and a spinning loading icon) When it occurs it is very reproducible and a reboot of the machine is required to make it work again. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1656252/+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 1677218] Re: Facebook uses mobile UI on desktop; probably wrong UA
** Tags added: next-candidates -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1677218 Title: Facebook uses mobile UI on desktop; probably wrong UA Status in webbrowser-app package in Ubuntu: Confirmed Bug description: Facebook uses mobile UI on desktop; probably wrong UA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1677218/+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 1675012] Re: browser not switching to picking mode when launched by the peer picker
** Tags added: next-candidates -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1675012 Title: browser not switching to picking mode when launched by the peer picker Status in Canonical System Image: Confirmed Status in webbrowser-app package in Ubuntu: Confirmed Bug description: When choose webbrowser-app as a source for content from the peer picker when the browser is not already running, it doesn't go into picking mode. However, if the browser is already running it switches nicely to picking mode. Maybe a race condition at startup missing the signal. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1675012/+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 1673625] Re: 10-globally-managed-devices.conf contained in wrong package
*** This bug is a duplicate of bug 1676547 *** https://bugs.launchpad.net/bugs/1676547 The issue is that NM is shipping the file along with its override, but the override logic broke due to a backport of NM in xenial. I'm marking this bug here as duplicate of bug 1676547; since it has more of the necessary logs to debug this. ** This bug has been marked a duplicate of bug 1676547 No network connectivity after upgrade from 16.04 to 16.10 -- 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/1673625 Title: 10-globally-managed-devices.conf contained in wrong package Status in network-manager package in Ubuntu: Confirmed Status in nplan package in Ubuntu: Incomplete Bug description: /usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf is installed from network-manager but without nplan it has no benefit, and breaks networking until you override it. Since the config is there to change how NetworkManager behaves in the presence of nplan, the configuration file itself should actually be contained in the nplan package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1673625/+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 1670715] Re: Last browser tab not fully displayed at app startup despite being current
** Tags added: next-candidates -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-extras in Ubuntu. https://bugs.launchpad.net/bugs/1670715 Title: Last browser tab not fully displayed at app startup despite being current Status in ubuntu-ui-extras package in Ubuntu: New Status in webbrowser-app package in Ubuntu: New Bug description: I have a browser session with 9 tabs open (more than fit in the app’s window’s width). The last tab is the current one. After I close the app and open it again, the current tab is correctly restored, but the tab handle is not fully in view. See attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-extras/+bug/1670715/+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