[Touch-packages] [Bug 1677626] Re: Unity started using gtk-greeter for screen-lock after update (Zesty)
out put of /usr/lib/lightdm/lightdm-greeter-session /usr/sbin/unity-greeter: -- unity-greeter.vala:80: Failed to connect to LightDM daemon: Unable to determine socket to daemon Note: I tried installing gnome-flashback-session which installed gnome- settings-daemon. But even after completely gnome-settings-daemon didn't fix the issue. (Unity & flashback, both session worked side-by-side in all previous releases, so I don't know if it is related.) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1677626 Title: Unity started using gtk-greeter for screen-lock after update (Zesty) Status in lightdm package in Ubuntu: New Status in lightdm-gtk-greeter package in Ubuntu: New Status in unity-settings-daemon package in Ubuntu: New Bug description: After today's update screen-locking suddenly started using gtk-greeter instead of unity-greeter. It looks similar to the old greeter of gdm /gnome-screensaver. I don't even have lightdm-gtk-greeter installed. How to reproduce: - 1. Reboot. It uses unity-greeter for login. 2. Login to unity and press CTRL + ALT + L Current Behavior: - It uses gtk-greeter instead of unity-greeter. Expected Behavior: It should use unity-greeter Using dm-tool lock: - Locks screen with unity greeter, but then after unlocking, it presents gtk-greeter again, I had to unlock it again to see desktop. And the lock is not smooth. It first blank the screen then load the unity-greeter and then lock it. Info: -- OS: Ubuntu 17.04 (32 bit) unity-settings-daemon: 15.04.1+17.04.20170328-0ubuntu1 gnome-screensaver: 3.6.1-7ubuntu5 unity: 7.5.0+17.04.20170301-0ubuntu1 lightdm: 1.22.0-0ubuntu1 lignome-desktop-3-12: 3.24.0-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1677626/+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 1673942] Re: pulseaudio suddenly stops. No dmesg entries. Nothing in the syslog
SOLVED - after a couple of hints with Tanu Kaskinen, this is solved with the following entry in /etc/pulse/default.pa .ifexists module-udev-detect.so load-module module-udev-detect tsched_buffer_size=16384 The suggested cause is that the kernel doesn't allow sufficient time to process the default 5 bytes. The pulseaudio daemon process has been running without error (in 5.1 configuration) for over 5.5 hours. Is this a hardware issue? Or a kernel parameter issue? or a combination of the two? -- 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 1678299] Re: Search in app drawer doens't seem to look in many fields
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity8 (Ubuntu) Status: New => Confirmed -- 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/1678299 Title: Search in app drawer doens't seem to look in many fields Status in Canonical System Image: New Status in unity8 package in Ubuntu: Confirmed Bug description: 1 - search for "Text Editor" You get the gedit icon, which has a "Text Editor" caption/name 2 - search for "gedit" You get nothing at all. Looks like app drawer search is not looking into all desktop file fields or something. 1 & 2 works in unity7 dash just fine. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1678299/+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 1514309] Re: Undefined Behavior in GCC 4.8 ios_base.h
** Changed in: gcc Status: Unknown => Fix Released ** Changed in: gcc Importance: Unknown => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu. https://bugs.launchpad.net/bugs/1514309 Title: Undefined Behavior in GCC 4.8 ios_base.h Status in gcc: Fix Released Status in gcc-4.8 package in Ubuntu: Fix Released Status in gcc-5 package in Ubuntu: Fix Released Status in gcc-4.8 source package in Trusty: Fix Released Status in gcc-5 package in Debian: Fix Released Bug description: On Linux, the distros often use libstdc++ rather than libc++ for Clang. Building libcxx is an art that I have never been able to untangle, and I think the maintainers have discovered the same. Below, I'm catching a UB finding when using Clang and libstdc++. This one has been around for some time. I first encountered it on Apple platforms. I regularly encounter it on Debian and Ubuntu. The fix is fairly easy, and I usually just do it: a couple of casts among unsigned and the flags. Also see http://lists.llvm.org/pipermail /cfe-dev/2015-January/040753.html. ** $ cat ub.cxx #include int main(int argc, char* argv[]) { std::cout << std::hex << argc << std::endl; std::cout << std::dec << argc << std::endl; return 0; } $ clang++ -fsanitize=undefined ub.cxx -o ub.exe $ ./ub.exe /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../include/c++/4.8/bits/ios_base.h:96:24: runtime error: load of value 4294967221, which is not a valid value for type 'std::_Ios_Fmtflags' /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../include/c++/4.8/bits/ios_base.h:76:67: runtime error: load of value 4294967221, which is not a valid value for type 'std::_Ios_Fmtflags' 1 1 ** $ g++ --version g++ (Ubuntu 4.8.4-2ubuntu1~14.04) 4.8.4 $ uname -a Linux ubuntu 3.13.0-66-generic #108-Ubuntu SMP Wed Oct 7 15:20:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release No LSB modules are available. ** $ apt-cache show g++ Package: g++ Priority: optional Section: devel Installed-Size: 34 Maintainer: Ubuntu Developers Original-Maintainer: Debian GCC Maintainers Architecture: amd64 Source: gcc-defaults (1.124ubuntu6) Version: 4:4.8.2-1ubuntu6 Provides: c++-compiler Depends: cpp (>= 4:4.8.2-1ubuntu6), gcc (>= 4:4.8.2-1ubuntu6), g++-4.8 (>= 4.8.2-5~), gcc-4.8 (>= 4.8.2-5~) Suggests: g++-multilib Filename: pool/main/g/gcc-defaults/g++_4.8.2-1ubuntu6_amd64.deb Size: 1490 MD5sum: 7332a4e9116b821e167a3d0236ca413a SHA1: 2c7201808be1029d21b7691c5a855535a4fcbd51 SHA256: 02c3d204efe6c34bf3de655aaf6a9ce524511977aedf92d7bce7093d0581f977 Description-en: GNU C++ compiler This is the GNU C++ compiler, a fairly portable optimizing compiler for C++. . This is a dependency package providing the default GNU C++ compiler. Description-md5: 4d44b18774ae5123b7c3f70d940cf655 Bugs: https://bugs.launchpad.net/ubuntu/+filebug Build-Essential: yes Origin: Ubuntu Supported: 5y To manage notifications about this bug go to: https://bugs.launchpad.net/gcc/+bug/1514309/+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 1195540] Re: [enhancement] Make able to get version information from client / server APIs
** Also affects: mir (Ubuntu) Importance: Undecided Status: New -- 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/1195540 Title: [enhancement] Make able to get version information from client / server APIs Status in Mir: Fix Committed Status in mir package in Ubuntu: New Bug description: It would be nice for shells / Mir clients to query what version of Mir they are using. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1195540/+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 1646375] Re: [ FAILED ] NestedInputWithMouse.mouse_pointer_coordinates_in_nested_server_are_accumulated
** Also affects: mir (Ubuntu) Importance: Undecided Status: New -- 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/1646375 Title: [ FAILED ] NestedInputWithMouse.mouse_pointer_coordinates_in_nested_server_are_accumulated Status in Mir: Fix Committed Status in mir package in Ubuntu: New Bug description: 04:37:34 [ RUN ] NestedInputWithMouse.mouse_pointer_coordinates_in_nested_server_are_accumulated ... 04:37:34 unknown file: Failure 04:37:34 04:37:34 Unexpected mock function call - returning default value. 04:37:34 Function call: handle(pointer_event(when=14575773119920512 (76.256763ms ago), from=2, motion, button_state=0, x=5, y=0, dx=5, dy=-2, vscroll=0, hscroll=0, modifiers=none)) 04:37:34 Returns: false 04:37:34 Google Mock tried the following 3 expectations, but none matched: 04:37:34 04:37:34 /<>/mir-0.25.0+yakkety3044bzr3857/tests/acceptance-tests/test_nested_input.cpp:321: tried expectation #0: EXPECT_CALL(nested_event_filter, handle(mt::InputDeviceStateEvent()))... 04:37:34 Expected arg #0: input device state event 04:37:34 Actual: pointer_event(when=14575773119920512 (28.550649ms ago), from=2, motion, button_state=0, x=5, y=0, dx=5, dy=-2, vscroll=0, hscroll=0, modifiers=none) 04:37:34 Expected: to be called once 04:37:34 Actual: called once - saturated and active 04:37:34 /<>/mir-0.25.0+yakkety3044bzr3857/tests/acceptance-tests/test_nested_input.cpp:326: tried expectation #1: EXPECT_CALL(nested_event_filter, handle(AllOf(mt::PointerEventWithPosition(initial_movement_x, initial_movement_y), mt::PointerEventWithDiff(initial_movement_x, initial_movement_y... 04:37:34 Expected arg #0: (pointer event with position (30, 30)) and (pointer event with diff (30, 30)) 04:37:34 Actual: pointer_event(when=14575773119920512 (71.013865ms ago), from=2, motion, button_state=0, x=5, y=0, dx=5, dy=-2, vscroll=0, hscroll=0, modifiers=none) 04:37:34 Expected: to be called once 04:37:34 Actual: never called - unsatisfied and active 04:37:34 /<>/mir-0.25.0+yakkety3044bzr3857/tests/acceptance-tests/test_nested_input.cpp:342: tried expectation #2: EXPECT_CALL(nested_event_filter, handle(AllOf(mt::PointerEventWithPosition(initial_movement_x + second_movement_x, initial_movement_y + second_movement_y), mt::PointerEventWithDiff(second_movement_x, second_movement_y... 04:37:34 Expected arg #0: (pointer event with position (35, 28)) and (pointer event with diff (5, -2)) 04:37:34 Actual: pointer_event(when=14575773119920512 (73.772187ms ago), from=2, motion, button_state=0, x=5, y=0, dx=5, dy=-2, vscroll=0, hscroll=0, modifiers=none) 04:37:34 Expected: to be called once 04:37:34 Actual: never called - unsatisfied and active 04:37:34 [2016-12-01 04:33:06.521662] mirserver: Stopping 04:37:34 [2016-12-01 04:33:06.601438] mirserver: Stopping 04:37:34 /<>/mir-0.25.0+yakkety3044bzr3857/tests/acceptance-tests/test_nested_input.cpp:326: Failure 04:37:34 Actual function call count doesn't match EXPECT_CALL(nested_event_filter, handle(AllOf(mt::PointerEventWithPosition(initial_movement_x, initial_movement_y), mt::PointerEventWithDiff(initial_movement_x, initial_movement_y... 04:37:34 Expected: to be called once 04:37:34 Actual: never called - unsatisfied and active 04:37:34 /<>/mir-0.25.0+yakkety3044bzr3857/tests/acceptance-tests/test_nested_input.cpp:342: Failure 04:37:34 Actual function call count doesn't match EXPECT_CALL(nested_event_filter, handle(AllOf(mt::PointerEventWithPosition(initial_movement_x + second_movement_x, initial_movement_y + second_movement_y), mt::PointerEventWithDiff(second_movement_x, second_movement_y... 04:37:34 Expected: to be called once 04:37:34 Actual: never called - unsatisfied and active 04:37:34 [ FAILED ] NestedInputWithMouse.mouse_pointer_coordinates_in_nested_server_are_accumulated (5578 ms) https://mir-jenkins.ubuntu.com/job/build-2-binpkg- mir/arch=amd64,compiler=clang,platform=mesa,release=yakkety/3016/consoleFull To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1646375/+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 1349660] Re: Touch screen coordinates don't rotate with the screen
** Also affects: mir (Ubuntu) Importance: Undecided Status: New -- 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/1349660 Title: Touch screen coordinates don't rotate with the screen Status in Mir: Fix Committed Status in mir package in Ubuntu: New Bug description: Touch screen coordinates don't rotate with the screen. Test case: 1. Find a laptop with a touch screen. 2. Start mir_demo_server_shell and a client or two. 3. Rotate the screen: Ctrl+Alt+Arrows Expected: Touch to also be rotated. Observed: Touch coordinates stay in the original native orientation - don't match up with fingers any more. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1349660/+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 1420334] Re: [enhancement] Missing client API for relative surface movement (e.g. dragging client-decorated windows)
** Also affects: mir (Ubuntu) Importance: Undecided Status: New -- 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/1420334 Title: [enhancement] Missing client API for relative surface movement (e.g. dragging client-decorated windows) Status in Mir: Fix Committed Status in MirAL: Incomplete Status in mir package in Ubuntu: New Status in xorg-server package in Ubuntu: Triaged Bug description: Mir needs a client API to allow surfaces to move themselves relatively. This is required to support full client-side decorations (bug 1398849), and also other apps like Google Chrome and Gnome Nautilus which can be dragged using part of their client areas. Later additions that are so similar I think they are part of the same bug: there need to be client APIs for "always on top" and "client initiate resize". To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1420334/+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 1613523] Re: [ FAILED ] NestedInput.nested_event_filter_receives_keyboard_from_host
** Also affects: mir (Ubuntu) Importance: Undecided Status: New -- 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/1613523 Title: [ FAILED ] NestedInput.nested_event_filter_receives_keyboard_from_host Status in Mir: Fix Committed Status in mir package in Ubuntu: New Bug description: Sounds like bug 1462033 but seems different... 06:57:59 [0;32m[ RUN ] [mNestedInput.nested_event_filter_receives_keyboard_from_host 06:57:59 unknown file: Failure 06:57:59 06:57:59 Unexpected mock function call - returning default value. 06:57:59 Function call: handle(key_event(when=529970166879 (1.635846ms ago), from=1, down, code=97, scan=30, modifiers=1)) 06:57:59 Returns: false 06:57:59 Google Mock tried the following 3 expectations, but none matched: 06:57:59 06:57:59 /build/mir-CSdSFG/mir-0.24.0+vivid1833bzr3644/tests/acceptance-tests/test_nested_input.cpp:195: tried expectation #0: EXPECT_CALL(nested_event_filter, handle(mt::InputDeviceStateEvent()))... 06:57:59 Expected arg #0: input device state event 06:57:59 Actual: key_event(when=529970166879 (1.214154ms ago), from=1, down, code=97, scan=30, modifiers=1) 06:57:59 Expected: to be called once 06:57:59 Actual: never called - unsatisfied and active 06:57:59 /build/mir-CSdSFG/mir-0.24.0+vivid1833bzr3644/tests/acceptance-tests/test_nested_input.cpp:196: tried expectation #1: EXPECT_CALL(nested_event_filter, handle(mt::KeyOfScanCode(30)))... 06:57:59 Expected: all pre-requisites are satisfied 06:57:59 Actual: the following immediate pre-requisites are not satisfied: 06:57:59 /build/mir-CSdSFG/mir-0.24.0+vivid1833bzr3644/tests/acceptance-tests/test_nested_input.cpp:195: pre-requisite #0 06:57:59 (end of pre-requisites) 06:57:59 Expected: to be called at least once 06:57:59 Actual: never called - unsatisfied and active 06:57:59 /build/mir-CSdSFG/mir-0.24.0+vivid1833bzr3644/tests/acceptance-tests/test_nested_input.cpp:200: tried expectation #2: EXPECT_CALL(nested_event_filter, handle(mt::KeyOfScanCode(54)))... 06:57:59 Expected arg #0: key of scan code 54 06:57:59 Actual: key_event(when=529970166879 (1.579538ms ago), from=1, down, code=97, scan=30, modifiers=1) 06:57:59 Expected: to be called twice 06:57:59 Actual: never called - unsatisfied and active 06:57:59 [0;31m[ FAILED ] [mNestedInput.nested_event_filter_receives_keyboard_from_host (200 ms) [https://mir-jenkins.ubuntu.com/job/device-runtests- mir/1323/device_type=krillin/consoleFull] To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1613523/+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 1646558] Re: [ FAILED ] NestedInputWithMouse.mouse_pointer_position_is_in_sync_with_host_server
** Also affects: mir (Ubuntu) Importance: Undecided Status: New -- 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/1646558 Title: [ FAILED ] NestedInputWithMouse.mouse_pointer_position_is_in_sync_with_host_server Status in Mir: Fix Committed Status in mir package in Ubuntu: New Bug description: 10:25:12 11: [ RUN ] NestedInputWithMouse.mouse_pointer_position_is_in_sync_with_host_server 10:25:12 11: [2016-12-01 10:25:12.937701] mirserver: Starting 10:25:12 11: [2016-12-01 10:25:12.938796] mirserver: Selected driver: mir:stub-graphics (version 0.26.0) 10:25:13 11: [2016-12-01 10:25:13.123066] mirserver: Using software cursor 10:25:13 11: [2016-12-01 10:25:13.136371] mirserver: Selected input driver: mir:stub-input (version: 0.26.0) 10:25:13 11: [2016-12-01 10:25:13.137063] mirserver: Mir version 0.26.0 10:25:13 11: [2016-12-01 10:25:13.294651] mirserver: Initial display configuration: 10:25:13 11: [2016-12-01 10:25:13.294952] mirserver: Output 1: VGA connected, used 10:25:13 11: [2016-12-01 10:25:13.295168] mirserver: Physical size 0.0" 0x0mm 10:25:13 11: [2016-12-01 10:25:13.295349] mirserver: Power is on 10:25:13 11: [2016-12-01 10:25:13.295559] mirserver: Current mode 1920x1080 60.00Hz 10:25:13 11: [2016-12-01 10:25:13.295788] mirserver: Preferred mode 1920x1080 60.00Hz 10:25:13 11: [2016-12-01 10:25:13.295979] mirserver: Orientation normal 10:25:13 11: [2016-12-01 10:25:13.296175] mirserver: Logical size 1920x1080 10:25:13 11: [2016-12-01 10:25:13.296365] mirserver: Logical position +0+0 10:25:13 11: [2016-12-01 10:25:13.328187] mirserver: Starting 10:25:13 11: [2016-12-01 10:25:13.745478] mirserver: Using nested cursor 10:25:13 11: [2016-12-01 10:25:13.803440] mirserver: Mir version 0.26.0 10:25:13 11: [2016-12-01 10:25:13.960211] mirserver: Initial display configuration: 10:25:14 11: [2016-12-01 10:25:13.960729] mirserver: Output 1: VGA connected, used 10:25:14 11: [2016-12-01 10:25:13.960948] mirserver: Physical size 0.0" 0x0mm 10:25:14 11: [2016-12-01 10:25:13.961124] mirserver: Power is on 10:25:14 11: [2016-12-01 10:25:13.961364] mirserver: Current mode 1920x1080 60.00Hz 10:25:14 11: [2016-12-01 10:25:13.961572] mirserver: Preferred mode 1920x1080 60.00Hz 10:25:14 11: [2016-12-01 10:25:13.961753] mirserver: Orientation normal 10:25:14 11: [2016-12-01 10:25:13.961931] mirserver: Logical size 1920x1080 10:25:14 11: [2016-12-01 10:25:13.962107] mirserver: Logical position +0+0 10:25:16 11: [2016-12-01 10:25:16.218016] mirserver: Stopping 10:25:16 11: [2016-12-01 10:25:16.266813] mirserver: Stopping 10:25:16 11: /<>/mir-0.25.0+yakkety3048bzr3857/tests/acceptance-tests/test_nested_input.cpp:368: Failure 10:25:16 11: Actual function call count doesn't match EXPECT_CALL(nested_event_filter, handle(AllOf(mt::PointerEventWithPosition(final_x, final_y), mt::PointerEventWithDiff(x[2], y[2]... 10:25:16 11: Expected: to be called once 10:25:16 11: Actual: never called - unsatisfied and active 10:25:16 11: [ FAILED ] NestedInputWithMouse.mouse_pointer_position_is_in_sync_with_host_server (3440 ms) https://mir-jenkins.ubuntu.com/job/build-2-binpkg- mir/arch=amd64,compiler=gcc,platform=mesa,release=yakkety/3020/consoleFull To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1646558/+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 1664562] Re: android complaint during mirscreencast of nested server
** Also affects: mir (Ubuntu) Importance: Undecided Status: New -- 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/1664562 Title: android complaint during mirscreencast of nested server Status in Mir: Fix Committed Status in mir package in Ubuntu: New Bug description: running mirscreencast against a nested server on android seems to occasionally cause: [2017-02-14 13:01:05.614843] MirBufferStreamAPI: Caught exception at client library boundary (in mir_buffer_stream_swap_buffers): /home/kdub/source/mir/mir/src/client/rpc/stream_socket_transport.cpp(168): Throw in function virtual void mir::client::rpc::StreamSocketTransport::send_message(const std::vector&, const std::vector&) Dynamic exception type: boost::exception_detail::clone_impl > std::exception::what: Failed to send message to server: Broken pipe 32, "Broken pipe" terminate called after throwing an instance of 'boost::exception_detail::clone_impl >' what(): Failed to send message to server: Broken pipe Seems limited to android. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1664562/+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 1661187] Re: [ FAILED ] DefaultInputManagerTest.forwards_pause_continue_state_changes_to_platform
** Also affects: mir (Ubuntu) Importance: Undecided Status: New -- 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/1661187 Title: [ FAILED ] DefaultInputManagerTest.forwards_pause_continue_state_changes_to_platform Status in Mir: Fix Committed Status in mir package in Ubuntu: New Bug description: 04:11:46 21: [ RUN ] DefaultInputManagerTest.forwards_pause_continue_state_changes_to_platform 04:11:46 21: /<>/mir-0.26.0+zesty3925bzr4005/tests/unit-tests/input/test_default_input_manager.cpp:171: Failure 04:11:46 21: Actual function call count doesn't match EXPECT_CALL(platform, pause_for_config())... 04:11:46 21: Expected: to be called once 04:11:46 21: Actual: never called - unsatisfied and active 04:11:46 21: [ FAILED ] DefaultInputManagerTest.forwards_pause_continue_state_changes_to_platform (65 ms) https://mir-jenkins.ubuntu.com/job/build-2-binpkg- mir/arch=amd64,compiler=gcc,platform=mesa,release=zesty/3883/consoleFull To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1661187/+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 1669752] Re: [regression] mir_proving_server mode hotkeys (Ctrl+Alt+=/-) cause the server to segfault
** Also affects: mir (Ubuntu) Importance: Undecided Status: New -- 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/1669752 Title: [regression] mir_proving_server mode hotkeys (Ctrl+Alt+=/-) cause the server to segfault Status in Mir: Fix Committed Status in mir package in Ubuntu: New Bug description: [regression] mir_proving_server mode hotkeys (Ctrl+Alt+=/-) cause the server to segfault. It appears there were two points of regression: r3996: Hotkey mode change worked but server segfaults on shutdown. r4012: Server segfaults on hotkeys pressed Changing modes with `mirout' continues to work perfectly though. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1669752/+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 1649354] Re: abi_check doesn't check mircore
** Also affects: mir (Ubuntu) Importance: Undecided Status: New -- 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/1649354 Title: abi_check doesn't check mircore Status in Mir: Fix Committed Status in mir package in Ubuntu: New Bug description: abi_check doesn't check mircore To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1649354/+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 1665271] Re: mirout reports logical size of a rotated display incorrectly
** Also affects: mir (Ubuntu) Importance: Undecided Status: New -- 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/1665271 Title: mirout reports logical size of a rotated display incorrectly Status in Mir: Fix Committed Status in mir package in Ubuntu: New Bug description: mirout reports logical size of a rotated display incorrectly. For example, if I rotate a 1920x1200 display 90 degrees right it reports: Output 48: DisplayPort, connected, "DELL U2413", 1920x1200+0+0, enabled, on, 520mm x 320mm (24.0"), right, 1.00x, unknown, monitor where "1920x1200+0+0" should actually be "1200x1920+0+0" since that's the logical rectangle now displayed. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1665271/+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 1655929] Re: [testsfail] PromptSessionClientAPI.client_pid_is_associated_with_session hangs and times out
** Also affects: mir (Ubuntu) Importance: Undecided Status: New -- 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/1655929 Title: [testsfail] PromptSessionClientAPI.client_pid_is_associated_with_session hangs and times out Status in Mir: Fix Committed Status in mir package in Ubuntu: New Bug description: https://mir-jenkins.ubuntu.com/job/build-2-binpkg- mir/arch=amd64,compiler=clang,platform=mesa,release=zesty/3466/console 13:24:57 9: --11870-- WARNING: unhandled amd64-linux syscall: 324 13:24:57 9: --11870-- You may be able to write your own handler. 13:24:57 9: --11870-- Read the file README_MISSING_SYSCALL_OR_IOCTL. 13:24:57 9: --11870-- Nevertheless we consider this a bug. Please report 13:24:57 9: --11870-- it at http://valgrind.org/support/bug_reports.html. 15:54:57 make: *** wait: No child processes. Stop. 15:54:57 make: *** Waiting for unfinished jobs 15:54:57 make: *** wait: No child processes. Stop. 15:54:57 Makefile:130: recipe for target 'test' failed 15:54:57 make[2]: *** [test] Terminated 15:54:57 debian/rules:19: recipe for target 'override_dh_auto_test' failed 15:54:57 make[1]: *** [override_dh_auto_test] Terminated 15:54:57 E: Build killed with signal TERM after 150 minutes of Also on amd64,gcc,xenial+overlay amd64,gcc,zesty https://mir-jenkins.ubuntu.com/job/build-2-binpkg- mir/arch=amd64,compiler=gcc,platform=mesa,release=xenial+overlay/3474/console https://mir-jenkins.ubuntu.com/job/build-2-binpkg- mir/arch=amd64,compiler=gcc,platform=mesa,release=zesty/3474/console And, probably related: i386,gcc,xenial+overlay https://mir-jenkins.ubuntu.com/job/build-2-binpkg- mir/arch=i386,compiler=gcc,platform=mesa,release=xenial+overlay/3470/console 15:37:14 11: --32166-- WARNING: unhandled x86-linux syscall: 375 15:37:14 11: --32166-- You may be able to write your own handler. 15:37:14 11: --32166-- Read the file README_MISSING_SYSCALL_OR_IOCTL. 15:37:14 11: --32166-- Nevertheless we consider this a bug. Please report 15:37:14 11: --32166-- it at http://valgrind.org/support/bug_reports.html. 18:07:14 Makefile:74: recipe for target 'test' failed To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1655929/+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 1671037] Re: [ FAILED ] PosixRWMutex.prefer_writer_nonrecursive_prevents_writer_starvation (Timeout waiting to acquire write lock)
** Also affects: mir (Ubuntu) Importance: Undecided Status: New -- 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/1671037 Title: [ FAILED ] PosixRWMutex.prefer_writer_nonrecursive_prevents_writer_starvation (Timeout waiting to acquire write lock) Status in Mir: Fix Committed Status in mir package in Ubuntu: New Bug description: PosixRWMutex.prefer_writer_nonrecursive_prevents_writer_starvation takes 5-10 minutes to complete then fails under valgrind: $ valgrind --trace-children=yes bin/mir_unit_tests --gtest_filter="PosixRWMutex.prefer*" ... Running main() from main.cpp Note: Google Test filter = PosixRWMutex.prefer* [==] Running 1 test from 1 test case. [--] Global test environment set-up. [--] 1 test from PosixRWMutex [ RUN ] PosixRWMutex.prefer_writer_nonrecursive_prevents_writer_starvation /home/dan/bzr/mir/trunk/tests/unit-tests/test_posix_rw_mutex.cpp:289: Failure Failed Timeout waiting to acquire write lock [ FAILED ] PosixRWMutex.prefer_writer_nonrecursive_prevents_writer_starvation (647342 ms) [--] 1 test from PosixRWMutex (647351 ms total) [--] Global test environment tear-down [==] 1 test from 1 test case ran. (647376 ms total) [ PASSED ] 0 tests. [ FAILED ] 1 test, listed below: [ FAILED ] PosixRWMutex.prefer_writer_nonrecursive_prevents_writer_starvation 1 FAILED TEST To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1671037/+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 1675331] Re: [regression] Mir is assigning the first output ID = 0 (== mir_display_output_id_invalid)
** Also affects: mir (Ubuntu) Importance: Undecided Status: New ** Changed in: mir (Ubuntu) Status: New => Invalid -- 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/1675331 Title: [regression] Mir is assigning the first output ID = 0 (== mir_display_output_id_invalid) Status in Mir: Fix Committed Status in mir package in Ubuntu: Invalid Bug description: Mir is assigning the first output ID = 0 (== mir_display_output_id_invalid): [2017-03-23 17:22:28.936000] mirserver: Initial display configuration: [2017-03-23 17:22:28.936026] mirserver: Output 0: HDMI-A disconnected [2017-03-23 17:22:28.936030] mirserver: Output 1: VGA disconnected [2017-03-23 17:22:28.936032] mirserver: Output 2: DisplayPort disconnected [2017-03-23 17:22:28.936035] mirserver: Output 3: HDMI-A disconnected [2017-03-23 17:22:28.936039] mirserver: Output 4: DisplayPort connected, used However we have already declared that: include/client/mir_toolkit/client_types.h:enum { mir_display_output_id_invalid = 0 }; To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1675331/+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 1661151] Re: [regression] mir_demo_server refuses to quit on Ctrl+Alt+Backspace or Ctrl+C in its terminal (deadlock in DefaultInputDeviceHub::add_device)
** Also affects: mir (Ubuntu) Importance: Undecided Status: New ** Changed in: mir (Ubuntu) Status: New => Invalid -- 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/1661151 Title: [regression] mir_demo_server refuses to quit on Ctrl+Alt+Backspace or Ctrl+C in its terminal (deadlock in DefaultInputDeviceHub::add_device) Status in Mir: Fix Committed Status in Mir 0.26 series: Invalid Status in mir package in Ubuntu: Invalid Bug description: mir_demo_server refuses to quit on Ctrl+Alt+Backspace It knows it should be quitting but doesn't, even when I try multiple times: [2017-02-02 12:13:12.670302] mirserver: Stopping [2017-02-02 12:13:13.070166] mirserver: Stopping [2017-02-02 12:13:13.302165] mirserver: Stopping [2017-02-02 12:13:13.510186] mirserver: Stopping [2017-02-02 12:13:13.686165] mirserver: Stopping [2017-02-02 12:13:13.870160] mirserver: Stopping [2017-02-02 12:13:14.062330] mirserver: Stopping [2017-02-02 12:13:14.254349] mirserver: Stopping [2017-02-02 12:13:14.438335] mirserver: Stopping [2017-02-02 12:13:14.622329] mirserver: Stopping [2017-02-02 12:13:14.830312] mirserver: Stopping Similarly, Ctrl+C no longer works: [2017-02-10 11:16:18.643952] mirserver: Logical position +0+0 [2017-02-10 11:16:18.643955] mirserver: Output 52: HDMI-A disconnected ^C^C^C^C^C^C^C^C^C^C^C To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1661151/+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 1674201] Re: cross-compile-chroot.sh (to zesty) fails to build [cannot find -ludev] due to libudev.so being in a different directory to where libudev.pc searches for it
** Also affects: mir (Ubuntu) Importance: Undecided Status: New -- 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/1674201 Title: cross-compile-chroot.sh (to zesty) fails to build [cannot find -ludev] due to libudev.so being in a different directory to where libudev.pc searches for it Status in Mir: Fix Committed Status in mir package in Ubuntu: New Status in systemd package in Ubuntu: Fix Committed Bug description: Mir fails to build on arm64 cross-compiled: [ 11%] Linking CXX shared library ../../lib/libmirplatform.so /usr/lib/gcc-cross/aarch64-linux-gnu/6/../../../../aarch64-linux-gnu/bin/ld: cannot find -ludev /usr/lib/gcc-cross/aarch64-linux-gnu/6/../../../../aarch64-linux-gnu/bin/ld: cannot find -ludev collect2: error: ld returned 1 exit status To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1674201/+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 1676320] Re: mirout commands don't work when followed by --
** Also affects: mir (Ubuntu) Importance: Undecided Status: New -- 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/1676320 Title: mirout commands don't work when followed by -- Status in Mir: Fix Committed Status in mir package in Ubuntu: New Bug description: mirout commands don't work when followed by -- $ mirout rotate right -- --desktop_file_hint=unity8 Unrecognized action `--' $ mirout off -- --desktop_file_hint=unity8 Unrecognized action `--' This is only a problem for Unity8, but still a problem. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1676320/+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 1598243] Re: Mir does not support multiple GPUs/cards simultaneously
** Changed in: mir Milestone: 0.27.0 => 0.28.0 -- 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/1598243 Title: Mir does not support multiple GPUs/cards simultaneously Status in Canonical System Image: In Progress Status in Mir: In Progress Status in mir package in Ubuntu: Triaged Bug description: I have a Lenovo laptop which has a hybrid graphics chipset. When I have a monitor connected to the displayport, the displayport monitor is on /dev/dri/card0 while the LVDS (integrated lcd) is at /dev/dri/card1. Our kms implementation only supports a single device; that which is found first with a valid connection. We need to support multiple devices. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1598243/+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 1118903] Re: [enhancement] Mir lacks a software rendering backend (and doesn't work in virtual machines)
** Changed in: mir Milestone: 0.27.0 => 0.28.0 -- 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/1118903 Title: [enhancement] Mir lacks a software rendering backend (and doesn't work in virtual machines) Status in Canonical System Image: Triaged Status in Mir: Triaged Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Triaged Bug description: As always, it's a critical requirement for Ubuntu to be able to render the same thing on any machine (metal or virtual), regardless of the availability of hardware acceleration. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1118903/+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 1569836] Re: demo server with CanonicalWindowManagerPolicy hides titlebar when vertmaximized
** Changed in: mir Milestone: 0.27.0 => 0.28.0 -- 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/1569836 Title: demo server with CanonicalWindowManagerPolicy hides titlebar when vertmaximized Status in Mir: In Progress Status in mir package in Ubuntu: New Bug description: run mir_demo_server with the CanonicalWindowManagerPolicy. Connect a client (like egltriangle). Hit Shift+F11 to transition client to vertmaximized. The titlebar is hidden (or off the top of the screen). It should be shown at the top. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1569836/+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 1539896] Re: [enhancement] Support Vulkan
** Changed in: mir Milestone: 0.27.0 => 0.28.0 -- 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/1539896 Title: [enhancement] Support Vulkan Status in Mir: In Progress Status in Ubuntu SDK IDE: Invalid Status in mir package in Ubuntu: Triaged Bug description: full support to the libraries vulkan in mir and in canonical system image. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1539896/+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 1600220] Re: Nested server needs full control over cursor position
** Changed in: mir Milestone: 0.27.0 => 0.28.0 -- 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/1600220 Title: Nested server needs full control over cursor position Status in Mir: In Progress Status in mir package in Ubuntu: Confirmed Bug description: Unity 8, a nested server of unity-system-compositor, needs full control over the cursor position. Mir doesn't have the needed context information to know how to move or position the cursor in all situations. Only Unity 8 has this information, which lives mainly in its QML scene. Once this is granted Unity 8 can dump its QML cursor implementation and move to use the more performant hardware cursor that mir has access to. Related to bug 1513883. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1600220/+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 1666178] Re: Qt & GTK apps are crashing with SIGABRT in mir_create_modal_dialog_window_spec() due to NULL parent pointer
** Changed in: mir Milestone: 0.27.0 => 0.28.0 -- 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/1666178 Title: Qt & GTK apps are crashing with SIGABRT in mir_create_modal_dialog_window_spec() due to NULL parent pointer Status in Canonical System Image: New Status in Mir: New Status in gtk+3.0 package in Ubuntu: New Status in kdenlive package in Ubuntu: New Status in mir package in Ubuntu: New Status in qtubuntu package in Ubuntu: New Status in synfigstudio package in Ubuntu: New Bug description: Qt & GTK apps are crashing with SIGABRT in mir_create_modal_dialog_window_spec() due to NULL parent pointer ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: synfigstudio 1.0.2-1build1 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: Mon Feb 20 11:43:49 2017 ExecutablePath: /usr/bin/synfigstudio InstallationDate: Installed on 2016-12-12 (69 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161108) ProcCmdline: synfigstudio Signal: 6 SourcePackage: synfigstudio StacktraceTop: mir_create_modal_dialog_window_spec () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 mir_connection_create_spec_for_modal_dialog () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: synfigstudio crashed with SIGABRT in mir_create_modal_dialog_window_spec() 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/1666178/+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 1655804] Re: Under Unity8, mir_demo_client_target is distorted and input in the wrong place on start-up
** Changed in: mir Milestone: 0.27.0 => 0.28.0 -- 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/1655804 Title: Under Unity8, mir_demo_client_target is distorted and input in the wrong place on start-up Status in Mir: In Progress Status in mir package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: Under Unity8, mir_demo_client_target is distorted and input in the wrong place on start-up. Test case: 1. $ sudo apt install mir-demos 2. $ mir_demo_client_target -- --desktop_file_hint=unity8 3. Wiggle the mouse around over the window The problem goes away after you manually resize the window. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1655804/+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 1628478] Re: Mir servers crash when using the Nvidia driver
** Changed in: mir Milestone: 0.27.0 => 0.28.0 -- 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/1628478 Title: Mir servers crash when using the Nvidia driver Status in Mir: In Progress Status in mir package in Ubuntu: Triaged Bug description: I select Unity8 from the log in screen, type in my credentials and it just hangs. Intel® Core™ i7-4710HQ CPU @ 2.50GHz × 8 GeForce GTX 860M/PCIe/SSE2 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1628478/+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 1654536] Re: unity-system-compositor crashed with src/platforms/android/server/gl_context.cpp(233): ... android::FramebufferGLContext::swap_buffers() ... std::exception::what: eg
** Changed in: mir Milestone: 0.27.0 => 0.28.0 -- 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/1654536 Title: unity-system-compositor crashed with src/platforms/android/server/gl_context.cpp(233): ... android::FramebufferGLContext::swap_buffers() ... std::exception::what: eglSwapBuffers failure: EGL_BAD_SURFACE (0x300d) Status in Canonical System Image: Confirmed Status in Mir: In Progress Status in mir package in Ubuntu: Confirmed Status in unity-system-compositor package in Ubuntu: Invalid Bug description: unity-system-compositor sometimes aborts on latest xenial/arm64 on frieza: $ system-image-cli -i current build number: 116 device name: frieza_arm64 channel: ubuntu-touch/staging/ubuntu last update: 2017-01-06 09:43:26 version version: 116 version ubuntu: 20170106 version device: 20161014.0 version custom: 20170106 /var/log/lightdm/unity-system-compositor.log has: ERROR: /build/mir-2omL3o/mir-0.25.0+16.04.20161203/src/platforms/android/server/gl_context.cpp(233): Throw in function virtual void mir::graphics::android::FramebufferGLContext::swap_buffers() const Dynamic exception type: boost::exception_detail::clone_impl > std::exception::what: eglSwapBuffers failure: EGL_BAD_SURFACE (0x300d) ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: unity-system-compositor 0.8.0+16.04.20161206-0ubuntu1 [origin: LP-PPA-ci-train-ppa-service-stable-phone-overlay] Uname: Linux 3.10.93+ aarch64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: arm64 Date: Fri Jan 6 10:20:54 2017 Disassembly: => 0x7fa41dd5e8: Cannot access memory at address 0x7fa41dd5e8 ExecutablePath: /usr/sbin/unity-system-compositor ExecutableTimestamp: 1480992789 GraphicsCard: ProcCmdline: unity-system-compositor --disable-overlays=false --spinner=/usr/bin/unity-system-compositor-spinner --file /run/mir_socket --from-dm-fd 11 --to-dm-fd 14 --vt 1 ProcCwd: / ProcEnviron: SegvAnalysis: Skipped: missing required field "Disassembly" Signal: 11 SourcePackage: unity-system-compositor StacktraceTop: () std::__exception_ptr::exception_ptr::_M_release() (this=0x7fa5647b20 <_ZN12_GLOBAL__N_121termination_exceptionE.lto_priv.2774>) at ../../../../src/libstdc++-v3/libsupc++/eh_ptr.cc:121 __cxa_finalize (d=0x7fa5646498) at cxa_finalize.c:56 __do_global_dtors_aux () at /usr/lib/aarch64-linux-gnu/libmirserver.so.42 _dl_fini () at dl-fini.c:235 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: version.libdrm: libdrm2 2.4.67-1ubuntu0.16.04.2 version.lightdm: lightdm 1.18.3-0ubuntu1 version.mesa: libegl1-mesa-dev N/A To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1654536/+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 1665307] Re: unity-system-compositor crashed with SIGSEGV in mir::frontend::detail::invoke
** Changed in: mir Milestone: 0.27.0 => 0.28.0 -- 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/1665307 Title: unity-system-compositor crashed with SIGSEGV in mir::frontend::detail::invokehttps://bugs.launchpad.net/mir/+bug/1665307/+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 1666259] Re: [kvm] Dolphin screen goes black opening Find dialog [mirclient: Caught exception at client library boundary (in mir_buffer_release) ... std::exception::what: error:
** Changed in: mir Milestone: 0.27.0 => 0.28.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1666259 Title: [kvm] Dolphin screen goes black opening Find dialog [mirclient: Caught exception at client library boundary (in mir_buffer_release) ... std::exception::what: error: use of MirBuffer when mir_buffer_is_valid() is false] Status in Canonical System Image: New Status in Mir: New Status in qtubuntu package in Ubuntu: New Bug description: Test case. - Install Dolphin. - Log in Unity8 session. - Open the Drawer and start Dolphin. - Go to Edit > Find. Expected result. - Find dialog opens. Actual result. - After clicking in Find, the Dolphin screen goes black. Tested in Zesty and Xenial + Overlay in a qemu-kvm VM (amd64). To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1666259/+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 1666181] Re: gnome-system-monitor crashed with SIGSEGV in make_protobuf_object() from mir::client::rpc::MirProtobufRpcChannel::on_data_available()
** Changed in: mir Milestone: 0.27.0 => 0.28.0 -- 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/1666181 Title: gnome-system-monitor crashed with SIGSEGV in make_protobuf_object() from mir::client::rpc::MirProtobufRpcChannel::on_data_available() Status in Mir: New Status in gnome-system-monitor package in Ubuntu: New Status in gtk+3.0 package in Ubuntu: New Status in mir package in Ubuntu: New Bug description: ubuntu 17.04 unity8 deb session gnome-system-monitor crashed with SIGSEGV ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: gnome-system-monitor 3.23.90-0ubuntu2 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 CurrentDesktop: Unity:Unity8 Date: Mon Feb 20 12:29:22 2017 ExecutablePath: /usr/bin/gnome-system-monitor InstallationDate: Installed on 2016-12-12 (69 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161108) ProcCmdline: gnome-system-monitor Signal: 11 SourcePackage: gnome-system-monitor StacktraceTop: ?? () ?? () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 ?? () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 ?? () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 ?? () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 Title: gnome-system-monitor crashed with SIGSEGV 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/mir/+bug/1666181/+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 1669524] Re: GTK window functions `Always on Top, Move and Resize' don't work in Mir/Unity8
** Changed in: mir Milestone: 0.27.0 => 0.28.0 -- 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/1669524 Title: GTK window functions `Always on Top, Move and Resize' don't work in Mir/Unity8 Status in Canonical System Image: In Progress Status in Mir: In Progress Status in MirAL: Triaged Status in gtk+3.0 package in Ubuntu: Confirmed Status in mir package in Ubuntu: Triaged Status in qtmir package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: ubuntu 17.04 unity8 [unity8] Always on Top, Move and Resize doesn't work open solitaire, right click on the title bar (see attachement) and then select Always on Top. the app doesn't stay on top. same with Move and Resize, does nothing To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1669524/+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 1672012] Re: Unity8 crashed right clicking on vlc [terminate called after throwing an instance of 'std::out_of_range' what(): map::at]
** Changed in: mir Milestone: 0.27.0 => 0.28.0 -- 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/1672012 Title: Unity8 crashed right clicking on vlc [terminate called after throwing an instance of 'std::out_of_range' what(): map::at] Status in Canonical System Image: Confirmed Status in Mir: Incomplete Status in Mir 0.26 series: Incomplete Status in MirAL: Incomplete Status in mir package in Ubuntu: Confirmed Status in miral package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: ubuntu 17.04 unity8 install vlc, launch it from app drawer or launcher try to use the menu, the menu shows for a split second and closes try to right click on vlc, here it just crashes/restarts unity8 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672012/+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 1672960] Re: unity-system-compositor crashed with SIGSEGV in invoke() from mir::frontend::detail::ProtobufMessageProcessor::dispatch:on_new_message() from on_read_size()
** Changed in: mir Milestone: 0.27.0 => 0.28.0 -- 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/1672960 Title: unity-system-compositor crashed with SIGSEGV in invoke() from mir::frontend::detail::ProtobufMessageProcessor::dispatch:on_new_message() from on_read_size() Status in Canonical System Image: Confirmed Status in Mir: Confirmed Status in Unity System Compositor: Confirmed Status in mir package in Ubuntu: Confirmed Status in unity-system-compositor package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity-system-compositor. This problem was most recently seen with package version 0.8.0+17.04.20161206-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/322176398baf670e4e9e5bb140a0aed0bbf0a00e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672960/+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 1678687] [NEW] screen crashes after restore from suspend
Public bug reported: dual screen. after the system being waken from the suspend, a mess rectangle appears surrounding any normal window or any pop-up menu. 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 x86_64 NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] 是一个目录: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 375.39 Tue Jan 31 20:47:00 PST 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 BootLog: 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 3 10:14:40 2017 DistUpgraded: 2016-09-08 00:19:31,601 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu DpkgLog: GraphicsCard: NVIDIA Corporation GM107 [GeForce GTX 745] [10de:1382] (rev a2) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GM107 [GeForce GTX 745] [10de:1065] InstallationDate: Installed on 2016-01-10 (448 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Dell Inc. XPS 8700 ProcEnviron: LANGUAGE=zh_CN:zh PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=zh_CN.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-71-generic root=UUID=ab94cc99-dabb-4a49-be5e-04ecd7d8954c ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to xenial on 2016-09-07 (207 days ago) dmi.bios.date: 11/22/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd11/22/2014:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA03:cvnDellInc.:ct3:cvr: dmi.product.name: XPS 8700 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A 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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A 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: Sun Apr 2 19:54:00 2017 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB Receiver KEYBOARD, id 8 inputLogitech USB Receiver KEYBOARD, id 9 inputLogitech M705MOUSE, id 10 xserver.errors: open /dev/fb0: No such file or directory 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: amd64 apport-bug compiz-0.9 corruption ubuntu xenial ** Attachment added: "2017-04-03 10-27-55屏幕截图.png" https://bugs.launchpad.net/bugs/1678687/+attachment/4853103/+files/2017-04-03%2010-27-55%E5%B1%8F%E5%B9%95%E6%88%AA%E5%9B%BE.png -- 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/1678687 Title: screen crashes after restore from suspend Status in xorg package in Ubuntu: New Bug description: dual screen. after the system being waken from the suspend, a mess rectangle appears surrounding any normal window or any pop-up menu. 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 x86_64 NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] 是一个目录: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 375.39 Tue Jan 31 20:47:00 PST 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 BootLog:
[Touch-packages] [Bug 1678299] Re: Search in app drawer doens't seem to look in many fields
** 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 unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1678299 Title: Search in app drawer doens't seem to look in many fields Status in Canonical System Image: New Status in unity8 package in Ubuntu: New Bug description: 1 - search for "Text Editor" You get the gedit icon, which has a "Text Editor" caption/name 2 - search for "gedit" You get nothing at all. Looks like app drawer search is not looking into all desktop file fields or something. 1 & 2 works in unity7 dash just fine. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1678299/+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 1678200] Re: XPS9365 2-in-1 doesn't automatically switch between desktop and tablet mode
** Summary changed: - XPS9365 2-in-1 doesn't switch desktop and tablet mode + XPS9365 2-in-1 doesn't automatically switch between desktop and tablet mode ** 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 unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1678200 Title: XPS9365 2-in-1 doesn't automatically switch between desktop and tablet mode Status in Canonical System Image: New Status in linux package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: New Bug description: Using the current Ubuntu 17.04 image and selecting the unity8 session, the XPS 9365 does not automatically switch modes. When switching to tablet mode, the ACPI driver INT33D6 which is bound to intel-vbtn will emit a few 0xcc events. When switching to desktop mode, the same driver will emit a 0xcd event. The intel-vbtn driver doesn't currently send anything to the OS about these events (just messages in dmesg about unknown, so Unity8 isn't able to pick them up. Unity will have to decide what key codes should be picked up, and the intel-vbtn driver will need to be configured to emit that event. I think it should be the SW_TABLET_MODE looking through the kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1678200/+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 1678209] Re: Running the music scope crashes the dash
** 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 unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1678209 Title: Running the music scope crashes the dash Status in Canonical System Image: New Status in unity8 package in Ubuntu: New Bug description: Selected music from manage and the dash crashed Added music as a favorite, scrolled to view it, and dash crashed Scrolled to it again and it displayed. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1678209/+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 1678270] Re: kdenlive opens some weird windows
** Tags added: unity8-desktop -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1678270 Title: kdenlive opens some weird windows Status in Canonical System Image: New Status in kdenlive package in Ubuntu: New Status in qtmir package in Ubuntu: New Status in qtubuntu package in Ubuntu: New Bug description: Ubuntu 17.04 unity8 kdenlive opens some weird windows install kdenlive, launch it without Xmir, not sure what's going on but it doesn't look like this on unity7, see screenshots To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1678270/+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 1672087] Re: [unity8] app drawer, clicking on "More apps in store" does nothing
** Tags added: unity8-desktop ** Changed in: unity8 (Ubuntu) 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/1672087 Title: [unity8] app drawer, clicking on "More apps in store" does nothing Status in Canonical System Image: Confirmed Status in unity8 package in Ubuntu: Triaged Bug description: ubuntu 17.04 unity 8 [unity8] app drawer, clicking on "More apps in store" does nothing open the app drawer, click on "More apps in store" :o) i'm sorry :D i just wanted to know what will happen To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672087/+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 1678273] Re: if you open a text file with kate from dolphin and then you close kate it also closes dolphin
** Tags added: unity8-desktop -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1678273 Title: if you open a text file with kate from dolphin and then you close kate it also closes dolphin Status in Canonical System Image: New Status in qtubuntu package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: ubuntu 17.04 unity8 if you open a text file with kate from dolphin and then you close kate it also closes dolphin start dolphin without Xmir, right click on some text file, Open With Kate. it will start kate fine, then close kate, it also closes dolphin. should only close kate To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1678273/+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 1678177] Re: [unity8] context menus and stuff should not be restricted to the screen area
We might have to clarify or split this bug: Menus: should always be moved to fit on screen. Browser address bar drop-down: should never be moved. -- 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/1678177 Title: [unity8] context menus and stuff should not be restricted to the screen area Status in Canonical System Image: New Status in Ubuntu UX: New Status in unity8 package in Ubuntu: New Bug description: ubuntu 17.04 unity8 context menus and stuff should not be restricted to the screen area, see screenshot. so now when you move an windows arround, child windows and context menus are not allowed to exit the screen area, but this is not good in many cases see screenshot (brakes the app) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1678177/+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 1678177] Re: [unity8] context menus and stuff should not be restricted to the screen area
** Tags added: unity8-desktop ** Also affects: ubuntu-ux Importance: Undecided Status: New ** No longer affects: qtubuntu (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1678177 Title: [unity8] context menus and stuff should not be restricted to the screen area Status in Canonical System Image: New Status in Ubuntu UX: New Status in unity8 package in Ubuntu: New Bug description: ubuntu 17.04 unity8 context menus and stuff should not be restricted to the screen area, see screenshot. so now when you move an windows arround, child windows and context menus are not allowed to exit the screen area, but this is not good in many cases see screenshot (brakes the app) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1678177/+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 1675448] Re: Unity 8 doesn't allow multiple Mir connections from an application instance
** Summary changed: - Unity 8 doesnt allow multiple mir connections from an application instance + Unity 8 doesn't allow multiple Mir connections from an application instance -- 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/1675448 Title: Unity 8 doesn't allow multiple Mir connections from an application instance Status in Canonical System Image: In Progress Status in qtmir package in Ubuntu: In Progress Status in unity8 package in Ubuntu: Invalid Bug description: Some clients like to probe to see if a mir connection is available such as SDL2 and SDL1.2. This is an issue in U8 as it doesnt seem to allow multiple connections in one process. Example: http://paste.ubuntu.com/24235399/ Output on U8: http://paste.ubuntu.com/24235406/ Proposed solution Related to bug #1589637 We need to accept multiple connections from the same application instance, relying on ubuntu-app-launch to tell us about instances and their lifecycle. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1675448/+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 1666435] Re: GTK apps have wrong font thickness/hinting under Mir
** Changed in: canonical-devices-system-image Status: New => In Progress ** Changed in: canonical-devices-system-image Importance: Undecided => Medium ** Changed in: gtk+3.0 (Ubuntu) Importance: Undecided => Medium ** Changed in: canonical-devices-system-image Milestone: None => u8c-z -- 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/1666435 Title: GTK apps have wrong font thickness/hinting under Mir Status in Canonical System Image: In Progress Status in GTK+: Fix Committed Status in gtk+3.0 package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Invalid Status in unity8-desktop-session package in Ubuntu: Confirmed Bug description: GTK apps have wrong font/thickness/hinting under Unity8/Mir (compared to Unity7 where they look much better). To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1666435/+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 1677626] Re: Unity started using gtk-greeter for screen-lock after update (Zesty)
** Also affects: lightdm-gtk-greeter (Ubuntu) Importance: Undecided Status: New ** Also affects: lightdm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1677626 Title: Unity started using gtk-greeter for screen-lock after update (Zesty) Status in lightdm package in Ubuntu: New Status in lightdm-gtk-greeter package in Ubuntu: New Status in unity-settings-daemon package in Ubuntu: New Bug description: After today's update screen-locking suddenly started using gtk-greeter instead of unity-greeter. It looks similar to the old greeter of gdm /gnome-screensaver. I don't even have lightdm-gtk-greeter installed. How to reproduce: - 1. Reboot. It uses unity-greeter for login. 2. Login to unity and press CTRL + ALT + L Current Behavior: - It uses gtk-greeter instead of unity-greeter. Expected Behavior: It should use unity-greeter Using dm-tool lock: - Locks screen with unity greeter, but then after unlocking, it presents gtk-greeter again, I had to unlock it again to see desktop. And the lock is not smooth. It first blank the screen then load the unity-greeter and then lock it. Info: -- OS: Ubuntu 17.04 (32 bit) unity-settings-daemon: 15.04.1+17.04.20170328-0ubuntu1 gnome-screensaver: 3.6.1-7ubuntu5 unity: 7.5.0+17.04.20170301-0ubuntu1 lightdm: 1.22.0-0ubuntu1 lignome-desktop-3-12: 3.24.0-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1677626/+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 1377033] Re: [Browser] Ability to switch to the desktop mode (desktop version)
** 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/1377033 Title: [Browser] Ability to switch to the desktop mode (desktop version) Status in Canonical System Image: Confirmed Status in Ubuntu UX: Triaged Status in webbrowser-app package in Ubuntu: Confirmed Bug description: As a mobile phone user I want to view the desktop version of website so that I can get most features out of the web. In stead of supporting to change user agents, I thinks it's fairly reasonable to be able to switch in between mobile and desktop mode for both desktop and touch version. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1377033/+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: 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/1253784 Title: Webbrowser doesn't respect the HTML5 "required" attribute Status in Canonical System Image: New 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/canonical-devices-system-image/+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 1436203] Re: [Dash] unity8-dash crashed with ASSERT: "eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE"
** Tags added: unity8-desktop ** Changed in: mir (Ubuntu) Status: Confirmed => Invalid ** Changed in: mir Status: New => Invalid -- 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/1436203 Title: [Dash] unity8-dash crashed with ASSERT: "eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE" Status in Mir: Invalid Status in mir package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Incomplete Bug description: Testing unity8 on a Lenovo IdeaPad s10-3t. The welcome wizard completed successfully. Unity8 loads, the indicators are visible and working. However, nothing else works: the scope shell doesn't load, only the splash screen is shown with the progress indicator spinning, and you can see that periodically it's restarted. Upstart logs for unity8-shell show an infinite loop of these: == Loading module: 'libubuntu_application_api_desktop_mirclient.so.2.9.0' [1427269742.137055] Loader: Loading modules from: /usr/lib/i386-linux-gnu/mir/client-platform/ [1427269742.137918] Loader: Loading module: /usr/lib/i386-linux-gnu/mir/client-platform/dummy.so [1427269742.139587] Loader: Loading module: /usr/lib/i386-linux-gnu/mir/client-platform/mesa.so.2 [1427269742.140657] Loader: Loading module: /usr/lib/i386-linux-gnu/mir/client-platform/mesa.so QSocketNotifier: Can only be used with threads started with QThread QSocketNotifier: Can only be used with threads started with QThread QObject::startTimer: Timers can only be used with threads started with QThread QIBusPlatformInputContext: invalid bus. file:///usr/share/unity8/Dash/Dash.qml:245: ReferenceError: scopeStyle is not defined UbuntuWindow - regular geometry file:///usr/share/unity8/Dash/Dash.qml:245: ReferenceError: scopeStyle is not defined ASSERT: "eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE" in file ../../../src/ubuntumirclient/glcontext.cpp, line 70 Loading module: 'libubuntu_application_api_desktop_mirclient.so.2.9.0' [1427269746.575630] Loader: Loading modules from: /usr/lib/i386-linux-gnu/mir/client-platform/ [1427269746.576432] Loader: Loading module: /usr/lib/i386-linux-gnu/mir/client-platform/dummy.so ... == ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: unity8 8.02+15.04.20150318-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic i686 ApportVersion: 2.16.2-0ubuntu4 Architecture: i386 Date: Tue Mar 24 17:31:02 2015 ExecutablePath: /usr/bin/unity8-dash InstallationDate: Installed on 2012-10-07 (898 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) ProcCmdline: unity8-dash --desktop_file_hint=/usr/share/applications/unity8-dash.desktop ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: unity8 StacktraceTop: QMessageLogger::fatal(char const*, ...) const () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 qt_assert(char const*, char const*, int) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 ?? () from /usr/lib/i386-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so ?? () from /usr/lib/i386-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so QOpenGLContext::destroy() () from /usr/lib/i386-linux-gnu/sse2/libQt5Gui.so.5 Title: unity8-dash crashed with SIGABRT in QMessageLogger::fatal() UpgradeStatus: Upgraded to vivid on 2015-01-31 (52 days ago) UserGroups: adm lpadmin nopasswdlogin sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1436203/+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: unity8-desktop -- 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 1678651] Re: Logging out of unity8 session doesn't return proper panel indicator for system settings in unity7
** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** 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/1678651 Title: Logging out of unity8 session doesn't return proper panel indicator for system settings in unity7 Status in Canonical System Image: New Status in indicator-session package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: Test case: log in to a unity8 session Log out & in to unity7 session Try to open System Settings from indicator What happens: nothing as it's attempting to open unity8's system settings A reboot is needed to return proper behavior in an unity7 session ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: unity8 8.15+17.04.20170328.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-15.17-generic 4.10.5 Uname: Linux 4.10.0-15-generic x86_64 ApportVersion: 2.20.4-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Sun Apr 2 13:53:08 2017 InstallationDate: Installed on 2017-03-30 (3 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170329) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1678651/+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
Same problem on new XPS 13 9360 with Mint Mate 18.1 Serena 64-bit -- 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 1575779] Re: hostnamectl fails under lxd unpriv container
** Merge proposal linked: https://code.launchpad.net/~wesley-wiedenmeier/cloud-init/+git/cloud-init/+merge/321029 -- 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/1575779 Title: hostnamectl fails under lxd unpriv container Status in apparmor package in Ubuntu: Triaged Bug description: 1. % lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.04 2. % apt-cache policy apparmor apparmor: Installed: 2.10.95-0ubuntu2 Candidate: 2.10.95-0ubuntu2 Version table: *** 2.10.95-0ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status % apt-cache policy lxd lxd: Installed: 2.0.0-0ubuntu4 Candidate: 2.0.0-0ubuntu4 Version table: *** 2.0.0-0ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3. lxc launch ubuntu-daily:xenial x1 lxc exec x1 /bin/bash root@x1:~# hostnamectl status Static hostname: x1 Icon name: computer-container Chassis: container Machine ID: 833b8548c7ce4118b4c9c5c3ae4f133d Boot ID: 9d5fbb053cf7494589c0863a0a4cf0ca Virtualization: lxc Operating System: Ubuntu 16.04 LTS Kernel: Linux 4.4.0-18-generic Architecture: x86-64 4. hostnamectl status hangs indefinitely On the host, there are some audit messages for each invocation of hostnamectl [411617.032274] audit: type=1400 audit(1461695563.731:100): apparmor="DENIED" operation="file_lock" profile="lxd- x1_" pid=17100 comm="(ostnamed)" family="unix" sock_type="dgram" protocol=0 addr=none It's related to socket activation. One can workaround this by running systemd-hostnamed in the background first root@x1:~# /lib/systemd/systemd-hostnamed & [1] 2462 root@x1:~# hostnamectl status Static hostname: x1 Icon name: computer-container Chassis: container Machine ID: 833b8548c7ce4118b4c9c5c3ae4f133d Boot ID: 9d5fbb053cf7494589c0863a0a4cf0ca Virtualization: lxc Operating System: Ubuntu 16.04 LTS Kernel: Linux 4.4.0-18-generic Architecture: x86-64 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apparmor 2.10.95-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Wed Apr 27 11:19:27 2016 InstallationDate: Installed on 2016-01-01 (117 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151209) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic root=UUID=e0b8b294-f364-4ef5-aa70-1916cdd37192 ro quiet splash vt.handoff=7 SourcePackage: apparmor Syslog: UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1575779/+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 1638842] Re: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method
*** This bug is a duplicate of bug 1658921 *** https://bugs.launchpad.net/bugs/1658921 Hi, may be a fix could be to remove network-manager from server setup. -- 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/1638842 Title: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method Status in network-manager package in Ubuntu: Won't Fix Bug description: Hello, I installed Ubuntu 16.10 using a chroot. I use network-manager to manage connections. My system is up-to-date (so I use network-manager 1.2.4-0ubuntu1). Wifi works perfectly but I cannot connect to wired networks and using my phone's Bluetooth connection. Corresponding devices are said to be unmanaged by network-manager. nmcli dev outputs: DEVICETYPE STATE CONNECTION enp1s0ethernet unmanaged -- wlp2s0wifi disconnected -- 6C:9B:02:2C:EE:2C btunmanaged -- hfp/org/bluez/hci0/dev_6C_9B_02_2C_EE_2C gsm unmanaged -- loloopback unmanaged -- The following command has no effect: sudo nmcli dev set enp1s0 managed yes I can connect to a wired connection by doing: ifconfig enp1s0 up dhclient enp1s0 There is nothing in the file /etc/network/interfaces. Everything works perfectly if I downgrade network-manager to this version: network-manager_1.2.2-0ubuntu0.16.04.3_amd64.deb (http://packages.ubuntu.com/xenial-updates/amd64/network- manager/download). I had to install libreadline6 and downgrade nplan to meet dependencies. I don't know what to join to this bug report so please ask in case anything is needed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1638842/+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 1676850] Re: Distorted menus in a lot of Qt apps under Unity8
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity8 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1676850 Title: Distorted menus in a lot of Qt apps under Unity8 Status in Canonical System Image: New Status in qtmir package in Ubuntu: Confirmed Status in qtubuntu package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: Ubuntu 17.04 Unity8 distorted context menu in a lot of qt apps (see attached screenshots) it happens fairly often and mostly the first time i launch/use the app launch without Xmir qupzilla, kate, kmines and right click on stuff, also try to move the mouse a bit to the left when you click. if i hover the distored menu with the mouse it seems to resize to the proper size To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1676850/+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 1676850] Re: Distorted menus in a lot of Qt apps under Unity8
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: qtubuntu (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1676850 Title: Distorted menus in a lot of Qt apps under Unity8 Status in Canonical System Image: New Status in qtmir package in Ubuntu: Confirmed Status in qtubuntu package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: Ubuntu 17.04 Unity8 distorted context menu in a lot of qt apps (see attached screenshots) it happens fairly often and mostly the first time i launch/use the app launch without Xmir qupzilla, kate, kmines and right click on stuff, also try to move the mouse a bit to the left when you click. if i hover the distored menu with the mouse it seems to resize to the proper size To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1676850/+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 1676850] Re: Distorted menus in a lot of Qt apps under Unity8
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: qtmir (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1676850 Title: Distorted menus in a lot of Qt apps under Unity8 Status in Canonical System Image: New Status in qtmir package in Ubuntu: Confirmed Status in qtubuntu package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: Ubuntu 17.04 Unity8 distorted context menu in a lot of qt apps (see attached screenshots) it happens fairly often and mostly the first time i launch/use the app launch without Xmir qupzilla, kate, kmines and right click on stuff, also try to move the mouse a bit to the left when you click. if i hover the distored menu with the mouse it seems to resize to the proper size To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1676850/+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 1678610] Re: ALC3661 audiochipset is wrongly identified as Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller
lspci -nn | grep -i audio 00:03.0 Audio device [0403]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller [8086:0c0c] (rev 06) 00:1b.0 Audio device [0403]: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller [8086:8c20] (rev 05) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1678610 Title: ALC3661 audiochipset is wrongly identified as Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller Status in alsa-driver package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: Audio chipset ALC3661 is wrongly identified as either Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller or Intel® 8/C220 Series Chipset Note : Using HDA driver in DKMS format from OEM audio daily hda dkms (open source) If additional logs and data are requested please advise. Regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1678610/+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 1678651] Re: Logging out of unity8 session doesn't return proper panel indicator for system settings in unity7
** Package changed: unity8 (Ubuntu) => indicator-session (Ubuntu) -- 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/1678651 Title: Logging out of unity8 session doesn't return proper panel indicator for system settings in unity7 Status in indicator-session package in Ubuntu: New Bug description: Test case: log in to a unity8 session Log out & in to unity7 session Try to open System Settings from indicator What happens: nothing as it's attempting to open unity8's system settings A reboot is needed to return proper behavior in an unity7 session ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: unity8 8.15+17.04.20170328.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-15.17-generic 4.10.5 Uname: Linux 4.10.0-15-generic x86_64 ApportVersion: 2.20.4-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Sun Apr 2 13:53:08 2017 InstallationDate: Installed on 2017-03-30 (3 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170329) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1678651/+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 1678653] [NEW] bug report sent to you in report
Public bug reported: I have switched from Ubuntu Mate to Ubuntu Nome and I wish to help you discover and fix any bugs or problems that may be evidenced within the Nome Operating System, but also seems to affect Ubuntu Mate. 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 x86_64 NonfreeKernelModules: nvidia_uvm nvidia wl .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.102 Mon Jan 16 13:06:29 PST 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Apr 2 11:01:29 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-71-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.4.0-71-generic, x86_64: installed nvidia-340, 340.102, 4.4.0-71-generic, x86_64: installed virtualbox, 5.0.32, 4.4.0-71-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation G84M [GeForce 8600M GT] [10de:0407] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. G84M [GeForce 8600M GT] [106b:00a3] InstallationDate: Installed on 2017-03-31 (1 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) MachineType: Apple Inc. MacBookPro4,1 ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-71-generic root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/27/08 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP41.88Z.00C1.B03.0802271651 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F42C89C8 dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 2 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F42C89C8 dmi.modalias: dmi:bvnAppleInc.:bvrMBP41.88Z.00C1.B03.0802271651:bd02/27/08:svnAppleInc.:pnMacBookPro4,1:pvr1.0:rvnAppleInc.:rnMac-F42C89C8:rvrPVT:cvnAppleInc.:ct2:cvrMac-F42C89C8: dmi.product.name: MacBookPro4,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A 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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A 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: Sun Apr 2 10:55:07 2017 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory 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: amd64 apport-bug 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/1678653 Title: bug report sent to you in report Status in xorg package in Ubuntu: New Bug description: I have switched from Ubuntu Mate to Ubuntu Nome and I wish to help you discover and fix any bugs or problems that may be evidenced within the Nome Operating System, but also seems to affect Ubuntu Mate. 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 x86_64 NonfreeKernelModules: nvidia_uvm nvidia wl .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.102 Mon Jan
[Touch-packages] [Bug 1678651] [NEW] Logging out of unity8 session doesn't return proper panel indicator for system settings in unity7
Public bug reported: Test case: log in to a unity8 session Log out & in to unity7 session Try to open System Settings from indicator What happens: nothing as it's attempting to open unity8's system settings A reboot is needed to return proper behavior in an unity7 session ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: unity8 8.15+17.04.20170328.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-15.17-generic 4.10.5 Uname: Linux 4.10.0-15-generic x86_64 ApportVersion: 2.20.4-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Sun Apr 2 13:53:08 2017 InstallationDate: Installed on 2017-03-30 (3 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170329) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- 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/1678651 Title: Logging out of unity8 session doesn't return proper panel indicator for system settings in unity7 Status in unity8 package in Ubuntu: New Bug description: Test case: log in to a unity8 session Log out & in to unity7 session Try to open System Settings from indicator What happens: nothing as it's attempting to open unity8's system settings A reboot is needed to return proper behavior in an unity7 session ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: unity8 8.15+17.04.20170328.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-15.17-generic 4.10.5 Uname: Linux 4.10.0-15-generic x86_64 ApportVersion: 2.20.4-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Sun Apr 2 13:53:08 2017 InstallationDate: Installed on 2017-03-30 (3 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170329) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1678651/+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 1678610] Re: ALC3661 audiochipset is wrongly identified as Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller
** Description changed: Audio chipset ALC3661 is wrongly identified as either - Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller - or + Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller + or Intel® 8/C220 Series Chipset Note : Using HDA driver in DKMS format from OEM audio daily hda dkms (open source) If additional logs and data are requested please advise. Regards. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1678610 Title: ALC3661 audiochipset is wrongly identified as Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller Status in alsa-driver package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: Audio chipset ALC3661 is wrongly identified as either Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller or Intel® 8/C220 Series Chipset Note : Using HDA driver in DKMS format from OEM audio daily hda dkms (open source) If additional logs and data are requested please advise. Regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1678610/+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 1515513] Re: /boot/initrd.img-*.old-dkms files left behind
Or update-initramfs could do more comprehensive deletion in its delete function: rm -f "${initramfs}" "${initramfs}".* instead of rm -f "${initramfs}" "${initramfs}.bak" -- 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/1515513 Title: /boot/initrd.img-*.old-dkms files left behind Status in dkms package in Ubuntu: Confirmed Status in initramfs-tools package in Ubuntu: New Status in dkms package in Debian: New Bug description: One notices *.old-dkms files being left behind still sitting on the disk after purging the related kernel. This can cause /boot to become full, and when it gets really bad, even sudo apt-get autoremove won't fix the problem - only deleting the old-dkms files manually solves the problem. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: dkms 2.2.0.3-2ubuntu3.3 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.7 Architecture: amd64 CurrentDesktop: KDE Date: Thu Nov 12 08:17:10 2015 InstallationDate: Installed on 2015-05-05 (190 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: dkms UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1515513/+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 1677189] Re: package apparmor 2.10.95-0ubuntu2.6 failed to install/upgrade: end of file on stdin at conffile prompt
** Changed in: apparmor (Ubuntu) Importance: Undecided => High -- 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 1678639] Re: amd
*** This bug is a duplicate of bug 1678640 *** https://bugs.launchpad.net/bugs/1678640 ** This bug has been marked a duplicate of bug 1678640 amd -- 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/1678639 Title: amd Status in xorg package in Ubuntu: New Bug description: no funciona ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-45.48~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-45-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Apr 2 18:53:31 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:04cd] Advanced Micro Devices, Inc. [AMD/ATI] Whistler [Radeon HD 6630M/6650M/6750M/7670M/7690M] [1002:6741] (rev ff) (prog-if ff) InstallationDate: Installed on 2017-03-15 (18 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Dell Inc. Vostro 3550 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-45-generic root=UUID=eb468df6-658a-45a9-8e3e-a67751221a14 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0PD77K dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA12:bd02/18/2014:svnDellInc.:pnVostro3550:pvrNotSpecified:rvnDellInc.:rn0PD77K:rvrA12:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Vostro 3550 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A 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 N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1678639/+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 1552939] Re: arm64 build doesn't use asm and is 4x-16x slower than it could be
Are there before and after numbers for ThunderX that are easy to share? I'm seeing aes-128-gcm 78608.06k 167039.08k 239836.84k 268366.17k 277192.70k with "OpenSSL 1.0.2g 1 Mar 2016" on Ubuntu 16.04 LTS aarch64 with "1.0 .2g-1ubuntu4.6", which almost certainly is a "with this patch" number. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1552939 Title: arm64 build doesn't use asm and is 4x-16x slower than it could be Status in OpenSSL: Invalid Status in openssl package in Ubuntu: Fix Released Status in openssl package in Debian: Fix Released Bug description: The openssl build for arm64 doesn't compile in the assembly that is present in openssl as of version 1.0.2 for aarch64 because the debian- targets.patch that is applied specifies a target that doesn't have assembly. The line at issue is debian-arm64 target which needs ${no_asm} changed to ${aarch64_asm}:linux64. Running openssl speed -evp aes-128-gcm shows a 4x-16x improvement in performance with this change made and the package rebuilt. Other aes and sha variants show similar performance gains by enabling asm. To manage notifications about this bug go to: https://bugs.launchpad.net/openssl/+bug/1552939/+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 1678639] [NEW] amd
Public bug reported: no funciona ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-45.48~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-45-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Apr 2 18:53:31 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:04cd] Advanced Micro Devices, Inc. [AMD/ATI] Whistler [Radeon HD 6630M/6650M/6750M/7670M/7690M] [1002:6741] (rev ff) (prog-if ff) InstallationDate: Installed on 2017-03-15 (18 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Dell Inc. Vostro 3550 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-45-generic root=UUID=eb468df6-658a-45a9-8e3e-a67751221a14 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0PD77K dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA12:bd02/18/2014:svnDellInc.:pnVostro3550:pvrNotSpecified:rvnDellInc.:rn0PD77K:rvrA12:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Vostro 3550 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A 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 N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 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/1678639 Title: amd Status in xorg package in Ubuntu: New Bug description: no funciona ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-45.48~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-45-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Apr 2 18:53:31 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:04cd] Advanced Micro Devices, Inc. [AMD/ATI] Whistler [Radeon HD 6630M/6650M/6750M/7670M/7690M] [1002:6741] (rev ff) (prog-if ff) InstallationDate: Installed on 2017-03-15 (18 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Dell Inc. Vostro 3550 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-45-generic root=UUID=eb468df6-658a-45a9-8e3e-a67751221a14 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0PD77K dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA12:bd02/18/2014:svnDellInc.:pnVostro3550:pvrNotSpecified:rvnDellInc.:rn0PD77K:rvrA12:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Vostro 3550 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu
[Touch-packages] [Bug 1678640] [NEW] amd
Public bug reported: no funciona ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-45.48~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-45-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Apr 2 18:55:12 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:04cd] Advanced Micro Devices, Inc. [AMD/ATI] Whistler [Radeon HD 6630M/6650M/6750M/7670M/7690M] [1002:6741] (rev ff) (prog-if ff) InstallationDate: Installed on 2017-03-15 (18 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Dell Inc. Vostro 3550 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-45-generic root=UUID=eb468df6-658a-45a9-8e3e-a67751221a14 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0PD77K dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA12:bd02/18/2014:svnDellInc.:pnVostro3550:pvrNotSpecified:rvnDellInc.:rn0PD77K:rvrA12:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Vostro 3550 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A 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 N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 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/1678640 Title: amd Status in xorg package in Ubuntu: New Bug description: no funciona ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-45.48~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-45-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Apr 2 18:55:12 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:04cd] Advanced Micro Devices, Inc. [AMD/ATI] Whistler [Radeon HD 6630M/6650M/6750M/7670M/7690M] [1002:6741] (rev ff) (prog-if ff) InstallationDate: Installed on 2017-03-15 (18 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Dell Inc. Vostro 3550 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-45-generic root=UUID=eb468df6-658a-45a9-8e3e-a67751221a14 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0PD77K dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA12:bd02/18/2014:svnDellInc.:pnVostro3550:pvrNotSpecified:rvnDellInc.:rn0PD77K:rvrA12:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Vostro 3550 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu
[Touch-packages] [Bug 1678635] [NEW] Some keys on Portuguese Apple aluminium are incorrect
Public bug reported: I use a Portuguese layout Apple aluminium keyboard on Ubuntu 16.10. While the mappings are correct for nearly all the keys, several keys are mapped incorrectly according to the legends on the keycaps: 1. the key left of z is marked as greater-than / less-than, yet when pressed yields the noncombining backtick and tilde characters. 2. The Euro symbol is shown as the alt-gr symbol on the three, yet this produces a £ sign (alt-gr E produces a Euro instead) 3. the section sign / plus-minus sign characters are shown on the key to the left of the "1", but this key produces the greater-than and less- than signs instead. I've enclosed the standard information in a zip file, plus a photo I took of the left hand side of the keyboard in case my explanations are a touch inadequate. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Attachment added: "apple-keyboard-issue.zip" https://bugs.launchpad.net/bugs/1678635/+attachment/4852790/+files/apple-keyboard-issue.zip ** Description changed: - I use a Portuguese layout Apple aluminium keyboard. While the mappings - are correct for nearly all the keys, several keys are mapped incorrectly - according to the legends on the keycaps: + I use a Portuguese layout Apple aluminium keyboard on Ubuntu 16.10. + While the mappings are correct for nearly all the keys, several keys are + mapped incorrectly according to the legends on the keycaps: 1. the key left of z is marked as greater-than / less-than, yet when pressed yields the noncombining backtick and tilde characters. 2. The Euro symbol is shown as the alt-gr symbol on the three, yet this produces a £ sign (alt-gr E produces a Euro instead) 3. the section sign / plus-minus sign characters are shown on the key to the left of the "1", but this key produces the greater-than and less- than signs instead. I've enclosed the standard information in a zip file, plus a photo I took of the left hand side of the keyboard in case my explanations are a touch inadequate. -- 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/1678635 Title: Some keys on Portuguese Apple aluminium are incorrect Status in xorg package in Ubuntu: New Bug description: I use a Portuguese layout Apple aluminium keyboard on Ubuntu 16.10. While the mappings are correct for nearly all the keys, several keys are mapped incorrectly according to the legends on the keycaps: 1. the key left of z is marked as greater-than / less-than, yet when pressed yields the noncombining backtick and tilde characters. 2. The Euro symbol is shown as the alt-gr symbol on the three, yet this produces a £ sign (alt-gr E produces a Euro instead) 3. the section sign / plus-minus sign characters are shown on the key to the left of the "1", but this key produces the greater-than and less-than signs instead. I've enclosed the standard information in a zip file, plus a photo I took of the left hand side of the keyboard in case my explanations are a touch inadequate. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1678635/+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 1678635] Re: Some keys on Portuguese Apple aluminium are incorrect
Here's the output of the "lsb_release" and "apt-cache policy" commands, which I forgot in the previous zip file. My apologies. ** Attachment added: "lsb_release and apt-cache policy outputs" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1678635/+attachment/4852794/+files/apple-keyboard-issue-2.zip -- 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/1678635 Title: Some keys on Portuguese Apple aluminium are incorrect Status in xorg package in Ubuntu: New Bug description: I use a Portuguese layout Apple aluminium keyboard on Ubuntu 16.10. While the mappings are correct for nearly all the keys, several keys are mapped incorrectly according to the legends on the keycaps: 1. the key left of z is marked as greater-than / less-than, yet when pressed yields the noncombining backtick and tilde characters. 2. The Euro symbol is shown as the alt-gr symbol on the three, yet this produces a £ sign (alt-gr E produces a Euro instead) 3. the section sign / plus-minus sign characters are shown on the key to the left of the "1", but this key produces the greater-than and less-than signs instead. I've enclosed the standard information in a zip file, plus a photo I took of the left hand side of the keyboard in case my explanations are a touch inadequate. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1678635/+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
Ed's solution worked for me: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1676621/comments/14 Thx Ed! -- 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
Re: [Touch-packages] [Bug 1678604] [NEW] package python3 3.5.1-3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 127
*** This bug is a duplicate of bug 1605657 *** https://bugs.launchpad.net/bugs/1605657 On Apr 02, 2017, at 12:25 PM, virendra singh wrote: >afer removing python2.7 and installing python3 and making >/usr/bin/python soft link from /usr/bin/python3 i am receiving this >error. Please suggest Changing /usr/bin/python to point to /usr/bin/python3 is not supported, therefore we do not recommend it and cannot guarantee things will work properly if you do this. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1678604 Title: package python3 3.5.1-3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 127 Status in python3-defaults package in Ubuntu: New Bug description: afer removing python2.7 and installing python3 and making /usr/bin/python soft link from /usr/bin/python3 i am receiving this error. Please suggest ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python3 3.5.1-3 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Sun Apr 2 17:25:22 2017 DuplicateSignature: package:python3:3.5.1-3 Removing python3 (3.5.1-3) ... /var/lib/dpkg/info/python3.prerm: 5: /var/lib/dpkg/info/python3.prerm: py3clean: not found dpkg: error processing package python3 (--remove): subprocess installed pre-removal script returned error exit status 127 ErrorMessage: subprocess installed pre-removal script returned error exit status 127 InstallationDate: Installed on 2016-06-23 (282 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.20 SourcePackage: python3-defaults Title: package python3 3.5.1-3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1678604/+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 1671606] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1
This bug also affects our boxes that have network-manager 1.2.6-0ubuntu0.16.0 amd64. Can confirm that one of our boxes, which is still on 14.04 LTS, and has network-manager 0.9.8.8-0ubuntu7.3 amd64 does not have these issues. In our case, we noticed that, when VPN is active, network-manager refuses to use the DNS servers defined by the VPN (openVPN). In stead, network-manager defaults to the "normal", "local" DNS server. This means a DNS leak, since the original (ISP) DNS can be seen. A workaround is setting 'Automatic (DHCP) addresses only" under IPv4 Settings in network-manager for the default network connection. This means however that, when no VPN, but the default net connection is used, network-manager has no DNS server, because this has to be entered manually in the DNS Servers field. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1671606 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1 Status in network-manager package in Ubuntu: Confirmed Status in resolvconf package in Ubuntu: Confirmed Bug description: I use my company's cisco vpn via network-manager in Ubuntu 16.04.2 LTS. After recent upgrade of network-manager:amd64 from version 1.2.2-0ubuntu0.16.04.4 to version 1.2.6-0ubuntu0.16.04.1 DNS resolution of VPN's server hostnames does not work. Roll back to version 1.2.2-0ubuntu0.16.04.4 solves the problem. Steps for reproducing: 1. upgrade network-manager:amd64 from version 1.2.2-0ubuntu0.16.04.4 to version 1.2.6-0ubuntu0.16.04.1 2. connect to VPN via network-manager applet 3. nslookop servername.internal --> ** server can't find servername.internal: NXDOMAIN 4. disconnect from VPN via network-manager applet 5. roll back network-manager via command: sudo apt-get install network-manager=1.2.2-0ubuntu0.16.04.4 6. restart network-manager via sudo service network-manager restart 7. connect to VPN via network-manager applet 8. nslookop servername.internal --> the server is resolved correctly ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.1 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 CurrentDesktop: Unity Date: Thu Mar 9 19:49:55 2017 InstallationDate: Installed on 2015-10-05 (520 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1671606/+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 1515513] Re: /boot/initrd.img-*.old-dkms files left behind
Here is the code as a file to retain text formatting. ** Attachment added: "Shell code for removing the backup initrd file for given kernel" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1515513/+attachment/4852757/+files/remove_initrd_backup -- 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/1515513 Title: /boot/initrd.img-*.old-dkms files left behind Status in dkms package in Ubuntu: Confirmed Status in initramfs-tools package in Ubuntu: New Status in dkms package in Debian: New Bug description: One notices *.old-dkms files being left behind still sitting on the disk after purging the related kernel. This can cause /boot to become full, and when it gets really bad, even sudo apt-get autoremove won't fix the problem - only deleting the old-dkms files manually solves the problem. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: dkms 2.2.0.3-2ubuntu3.3 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.7 Architecture: amd64 CurrentDesktop: KDE Date: Thu Nov 12 08:17:10 2015 InstallationDate: Installed on 2015-05-05 (190 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: dkms UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1515513/+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 1515513] Re: /boot/initrd.img-*.old-dkms files left behind
The Bourne shell script code to remove the backups could be added in kernel_prerm.d_dkms (or currently non-existing kernel_postrm.d_dkms) in dkms package source, but if the package was removed, there would be no code to remove the backups in conjunction with kernel removing. Thus, the code could be added to kernel/postrm.d/initramfs-tools (or currently non-existing kernel/prerm.d/initramfs-tools) in initramfs-tools package source, too: # This is applied from make_initrd function in dkms command, which # creates the possible initrd backup file. remove_initrd_backup() { for initrd in "initrd-$1.img" "initramfs-$1.img" "initrd.img-$1" "initrd-$1"; do rm -fv /boot/"${initrd}".old-dkms \ /boot/efi/efi/redhat/"${initrd}".old-dkms done } remove_initrd_backup "$1" -- 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/1515513 Title: /boot/initrd.img-*.old-dkms files left behind Status in dkms package in Ubuntu: Confirmed Status in initramfs-tools package in Ubuntu: New Status in dkms package in Debian: New Bug description: One notices *.old-dkms files being left behind still sitting on the disk after purging the related kernel. This can cause /boot to become full, and when it gets really bad, even sudo apt-get autoremove won't fix the problem - only deleting the old-dkms files manually solves the problem. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: dkms 2.2.0.3-2ubuntu3.3 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.7 Architecture: amd64 CurrentDesktop: KDE Date: Thu Nov 12 08:17:10 2015 InstallationDate: Installed on 2015-05-05 (190 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: dkms UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1515513/+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 1533343] Re: No sound from internal speakers after boot with connected headphones
I'm experiencing this issue on Ubuntu MATE. The front right speaker has stopped working on my ancient Sound Blaster Audigy. I think the problem started with a recent upgrade. The sound works normally when I boot into Windows. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1533343 Title: No sound from internal speakers after boot with connected headphones Status in alsa-driver package in Ubuntu: Confirmed Bug description: On Lenovo L450 laptop, when I boot the PC with headphones attached, then the sound via headphones will work, but there will be no sound from internal speakers when headphones are detached. I tested this couple of times and the problem is always reproduced. This is the procedure A: 1. When the problem is not present, sound is present in laptop's speakers, connect the headphones 2. initiate reboot 3. once booted, initiate playing of some audio and check the sound from headphones - it will work OK 4. disconnect the headphones - there is no sound from internal speakers Procedure B: 1. turn off the laptop (power off) 2. connect the headphones to the laptop 3. power on the laptop and boot into Ubuntu 15.10 4. once booted, initiate playing of some audio and check the sound from headphones - it will work OK 5. disconnect the headphones - there is no sound from internal speakers ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6 Uname: Linux 4.2.0-23-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ygzo 2125 F pulseaudio /dev/snd/controlC0: ygzo 2125 F pulseaudio CurrentDesktop: Unity Date: Tue Jan 12 20:44:49 2016 InstallationDate: Installed on 2015-10-05 (99 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_Type: Only some of outputs are working Title: [20DT0003XS, Realtek ALC3232, Speaker, Internal] Playback problem UpgradeStatus: Upgraded to wily on 2015-11-03 (70 days ago) dmi.bios.date: 08/19/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JDET54WW (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: Intel powered classmate PC dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJDET54WW(1.16):bd08/19/2015:svnLENOVO:pn20DT0003XS:pvrThinkPadL450:rvnLENOVO:rnIntelpoweredclassmatePC:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20DT0003XS dmi.product.version: ThinkPad L450 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1533343/+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 1675519] Re: Network Manager w/ dnsmasq Dies when VPN-ing
Hi, I had the same problem on Linux Mint 18.1 First time i start openvpn connexion all is ok. But if i stop it and start again via networkmanager, there are no DNS (but ping ip is ok). A reboot of the computer make dns come back. Or i found a temporary solution, modify the file /etc/NetworkManager/NetworkManager.conf and comment the line #dns=dnsmasq After this i stop / start many times openvpn connexion via network-manager and it works well. -- 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/1675519 Title: Network Manager w/ dnsmasq Dies when VPN-ing Status in network-manager package in Ubuntu: Triaged Bug description: Hello. Within the past week or so, a new bug has cropped up on Network Manager on 16.04. When Network Manager on 16.04 is configured to use dnsmasq and not systemd-resolved, one is expecting VPN DNS servers to be properly set and dnsmasq to properly route DNS requests to the Internet. However, when connecting to my OpenVPN connection, dnsmasq now fails extremely hard and no longer replies or routes data for DNS requests properly. This results in me having to use a fail-over workaround of enforcing resolvconf to use my local `bind9` instance on my own system for DNS, which is configured to route to Google for DNS requests. This, however, prohibits me from using my own DNS on my VPN connect, which are on the remote location and serve internal ranges and domains that I should be permitted to access. Given these issues, with `dnsmasq` just outright exploding in our faces and no longer being usable for DNS request routing over the VPN, I'm not even sure we can consider VPN DNS as a viable option anymore with 16.04. Note that this is only *very* recently a problem within the past few weeks, and I can't find any updates which would have impacted this. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.1 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 CurrentDesktop: Unity Date: Thu Mar 23 14:04:06 2017 InstallationDate: Installed on 2016-12-20 (92 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1675519/+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 1436203] Re: [Dash] unity8-dash crashed with ASSERT: "eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE"
> if it helps I can redo the installation and note the steps down exactly. uhm, no, sorry. I DID redo the installation, but now I can NOT reproduce the problem -- 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/1436203 Title: [Dash] unity8-dash crashed with ASSERT: "eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE" Status in Mir: New Status in mir package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Incomplete Bug description: Testing unity8 on a Lenovo IdeaPad s10-3t. The welcome wizard completed successfully. Unity8 loads, the indicators are visible and working. However, nothing else works: the scope shell doesn't load, only the splash screen is shown with the progress indicator spinning, and you can see that periodically it's restarted. Upstart logs for unity8-shell show an infinite loop of these: == Loading module: 'libubuntu_application_api_desktop_mirclient.so.2.9.0' [1427269742.137055] Loader: Loading modules from: /usr/lib/i386-linux-gnu/mir/client-platform/ [1427269742.137918] Loader: Loading module: /usr/lib/i386-linux-gnu/mir/client-platform/dummy.so [1427269742.139587] Loader: Loading module: /usr/lib/i386-linux-gnu/mir/client-platform/mesa.so.2 [1427269742.140657] Loader: Loading module: /usr/lib/i386-linux-gnu/mir/client-platform/mesa.so QSocketNotifier: Can only be used with threads started with QThread QSocketNotifier: Can only be used with threads started with QThread QObject::startTimer: Timers can only be used with threads started with QThread QIBusPlatformInputContext: invalid bus. file:///usr/share/unity8/Dash/Dash.qml:245: ReferenceError: scopeStyle is not defined UbuntuWindow - regular geometry file:///usr/share/unity8/Dash/Dash.qml:245: ReferenceError: scopeStyle is not defined ASSERT: "eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE" in file ../../../src/ubuntumirclient/glcontext.cpp, line 70 Loading module: 'libubuntu_application_api_desktop_mirclient.so.2.9.0' [1427269746.575630] Loader: Loading modules from: /usr/lib/i386-linux-gnu/mir/client-platform/ [1427269746.576432] Loader: Loading module: /usr/lib/i386-linux-gnu/mir/client-platform/dummy.so ... == ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: unity8 8.02+15.04.20150318-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic i686 ApportVersion: 2.16.2-0ubuntu4 Architecture: i386 Date: Tue Mar 24 17:31:02 2015 ExecutablePath: /usr/bin/unity8-dash InstallationDate: Installed on 2012-10-07 (898 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) ProcCmdline: unity8-dash --desktop_file_hint=/usr/share/applications/unity8-dash.desktop ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: unity8 StacktraceTop: QMessageLogger::fatal(char const*, ...) const () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 qt_assert(char const*, char const*, int) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 ?? () from /usr/lib/i386-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so ?? () from /usr/lib/i386-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so QOpenGLContext::destroy() () from /usr/lib/i386-linux-gnu/sse2/libQt5Gui.so.5 Title: unity8-dash crashed with SIGABRT in QMessageLogger::fatal() UpgradeStatus: Upgraded to vivid on 2015-01-31 (52 days ago) UserGroups: adm lpadmin nopasswdlogin sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1436203/+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 1678610] Re: ALC3661 audiochipset is wrongly identified as Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller
sudo lspci -v | grep -A7 -i "audio" 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06) Subsystem: Dell Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller Flags: bus master, fast devsel, latency 0, IRQ 32 Memory at d271 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00 Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel -- 00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 05) Subsystem: Dell 8 Series/C220 Series Chipset High Definition Audio Controller Flags: bus master, fast devsel, latency 0, IRQ 31 Memory at d2714000 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00 Capabilities: [100] Virtual Channel Kernel driver in use: snd_hda_intel -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1678610 Title: ALC3661 audiochipset is wrongly identified as Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller Status in alsa-driver package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: Audio chipset ALC3661 is wrongly identified as either Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller or Note : Using HDA driver in DKMS format from OEM audio daily hda dkms (open source) If additional logs and data are requested please advise. Regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1678610/+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 1678610] Re: ALC3661 audiochipset is wrongly identified as Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller
sudo aplay -l List of PLAYBACK Hardware Devices card 0: HDMI [HDA Intel HDMI], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: HDMI [HDA Intel HDMI], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: PCH [HDA Intel PCH], device 0: ALC3661 Analog [ALC3661 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1678610 Title: ALC3661 audiochipset is wrongly identified as Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller Status in alsa-driver package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: Audio chipset ALC3661 is wrongly identified as either Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller or Note : Using HDA driver in DKMS format from OEM audio daily hda dkms (open source) If additional logs and data are requested please advise. Regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1678610/+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 1678610] Re: ALC3661 audiochipset is wrongly identified as Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller
http://www.alsa- project.org/db/?f=0184dcc1f39b43cfc3523f743ac95e8f82bedeae ** Attachment added: "alsa_info_dump" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1678610/+attachment/4852698/+files/alsa_info_dump ** Description changed: - - Audio chipset ALC3661 audiochipset is wrongly identified as either - Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller or ALC3661 audiochipset is wrongly identified as Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller. + Audio chipset ALC3661 is wrongly identified as either + Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller + or Note : Using HDA driver in DKMS format from OEM audio daily hda dkms (open source) - If additional logs and data are requested please advise. Regards. ** Also affects: pulseaudio Importance: Undecided Status: New ** Also affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** No longer affects: pulseaudio -- 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/1678610 Title: ALC3661 audiochipset is wrongly identified as Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller Status in alsa-driver package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: Audio chipset ALC3661 is wrongly identified as either Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller or Note : Using HDA driver in DKMS format from OEM audio daily hda dkms (open source) If additional logs and data are requested please advise. Regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1678610/+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 1678610] Re: ALC3661 audiochipset is wrongly identified as Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller
** Attachment added: "alsamixer.png" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1678610/+attachment/4852697/+files/alsamixer.png -- 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/1678610 Title: ALC3661 audiochipset is wrongly identified as Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller Status in pulseaudio package in Ubuntu: New Bug description: Audio chipset ALC3661 audiochipset is wrongly identified as either Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller or ALC3661 audiochipset is wrongly identified as Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller. Note : Using HDA driver in DKMS format from OEM audio daily hda dkms (open source) If additional logs and data are requested please advise. Regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1678610/+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 1678610] [NEW] ALC3661 audiochipset is wrongly identified as Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller
Public bug reported: Audio chipset ALC3661 audiochipset is wrongly identified as either Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller or ALC3661 audiochipset is wrongly identified as Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller. Note : Using HDA driver in DKMS format from OEM audio daily hda dkms (open source) If additional logs and data are requested please advise. Regards. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: sound ** Tags added: sound -- 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/1678610 Title: ALC3661 audiochipset is wrongly identified as Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller Status in pulseaudio package in Ubuntu: New Bug description: Audio chipset ALC3661 audiochipset is wrongly identified as either Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller or ALC3661 audiochipset is wrongly identified as Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller. Note : Using HDA driver in DKMS format from OEM audio daily hda dkms (open source) If additional logs and data are requested please advise. Regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1678610/+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 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec
4.8.0-22 not 4.8.22 Sorry -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E200HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1563110/+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 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec
konstantinos: in official updates the keyboard stop working after 4.8.22 kernel. It is the latest which works fine in Ubuntu. With kernels 4.9 or newer I know it works in Fedora. You can choose the kernel in grub menu. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E200HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1563110/+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 1516025] Re: Realtek ALC3661 Alienware14 / Soundoutput / Jack
** Also affects: linux Importance: Undecided Status: New ** Project changed: linux => pulseaudio (Ubuntu) ** Changed in: pulseaudio (Ubuntu) Importance: Undecided => Unknown ** Changed in: pulseaudio (Ubuntu) Status: New => Unknown ** Changed in: pulseaudio (Ubuntu) Remote watch: None => Linux Kernel Bug Tracker #107851 -- 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/1516025 Title: Realtek ALC3661 Alienware14 / Soundoutput / Jack Status in ALSA driver: Unknown Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Unknown Bug description: When watching the following video (but also audio from other programs) with the volume at 100%, the audio loudness is lower in comparison to the same audio being played at 100% in Windows 10: https://www.youtube.com/watch?v=YQHsXMglC9A ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-18-generic 4.2.0-18.22 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: imran 1619 F pulseaudio /dev/snd/controlC1: imran 1619 F pulseaudio CurrentDesktop: Unity Date: Fri Nov 13 18:08:07 2015 HibernationDevice: RESUME=UUID=2401d43e-85ec-4c88-81c1-c597086504a1 InstallationDate: Installed on 2015-11-07 (5 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Alienware Alienware 14 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic root=UUID=a534221a-37cb-4092-8ce2-934940eede6d ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.2.0-18-generic N/A linux-backports-modules-4.2.0-18-generic N/A linux-firmware1.149.1 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2014 dmi.bios.vendor: Alienware dmi.bios.version: A09 dmi.board.name: 07MJ2Y dmi.board.vendor: Alienware dmi.board.version: A01 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A09 dmi.modalias: dmi:bvnAlienware:bvrA09:bd04/23/2014:svnAlienware:pnAlienware14:pvrA09:rvnAlienware:rn07MJ2Y:rvrA01:cvnAlienware:ct8:cvrA09: dmi.product.name: Alienware 14 dmi.product.version: A09 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1516025/+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 1678606] [NEW] [packaging] Missing dnsmasq-tools dependency causes wifi hotspot/network sharing feature broken
Public bug reported: In Ubuntu 17.04, the dnsmasq-tools dependency has been dropped from network-manager, and the wifi network sharing feature failed to work because of this: NetworkManager[874]: [1491134643.1581] device (wlp3s0): share: (wlp3s0) failed to start dnsmasq: Could not find "dnsmasq" binary In my opinion it should at least in Recommends, refer following for related info: Bug #992411 “network-manager: Please don't Depend on dnsmasq-bas...” : Bugs : network-manager package : Ubuntu https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/992411 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: network-manager 1.4.4-1ubuntu3 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: Unity:Unity7 Date: Sun Apr 2 20:28:25 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-03-30 (2 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) IpRoute: default via 192.168.1.1 dev enp4s0f2 proto static metric 100 10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.1.0/24 dev enp4s0f2 proto kernel scope link src 192.168.1.119 metric 100 NetworkManager.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANGUAGE=zh_TW:zh PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=zh_TW.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICETYPE STATE DBUS-PATH CONNECTIONCON-UUID CON-PATH enp4s0f2 ethernet connected /org/freedesktop/NetworkManager/Devices/1 由 DHCP 伺服器自動配發 IP 地址的網路 66cd739f-4bfd-4cbc-909f-1cd96e9ec8bb /org/freedesktop/NetworkManager/ActiveConnection/8 wlp3s0wifi connected /org/freedesktop/NetworkManager/Devices/2 林博仁的模擬 Wi-Fi 網路 2547ce2c-a517-4d31-83a2-4bb38fc704cb /org/freedesktop/NetworkManager/ActiveConnection/14 loloopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.4connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug packaging zesty ** Tags added: packaging -- 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/1678606 Title: [packaging] Missing dnsmasq-tools dependency causes wifi hotspot/network sharing feature broken Status in network-manager package in Ubuntu: New Bug description: In Ubuntu 17.04, the dnsmasq-tools dependency has been dropped from network-manager, and the wifi network sharing feature failed to work because of this: NetworkManager[874]: [1491134643.1581] device (wlp3s0): share: (wlp3s0) failed to start dnsmasq: Could not find "dnsmasq" binary In my opinion it should at least in Recommends, refer following for related info: Bug #992411 “network-manager: Please don't Depend on dnsmasq-bas...” : Bugs : network-manager package : Ubuntu https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/992411 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: network-manager 1.4.4-1ubuntu3 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: Unity:Unity7 Date: Sun Apr 2 20:28:25 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-03-30 (2 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) IpRoute: default via 192.168.1.1 dev enp4s0f2 proto static metric 100 10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.1.0/24 dev enp4s0f2 proto kernel scope link src 192.168.1.119 metric 100 NetworkManager.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANGUAGE=zh_TW:zh PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=zh_TW.UTF-8 SHELL=/bin/bash SourcePackage: ne
[Touch-packages] [Bug 992411] Re: network-manager: Please don't Depend on dnsmasq-base
P.S. in 17.04 the dnsmasq dependency has been drop, causing graphically silent fail when setting a wifi hotspot -- 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/992411 Title: network-manager: Please don't Depend on dnsmasq-base Status in network-manager package in Ubuntu: Triaged Bug description: dnsmasq in not required... Furthermore because you are over writing the Systems Administrators dhcp setting you have now made it a requirement to edit configurations on every dhcp client. cp@io:~$ dpkg -l dnsmasq-base bind9 dhcp3-server Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name VersionDescription +++-==-==- ii bind9 1:9.8.1.dfsg.P Internet Domain Name Server ii dhcp3-server 4.1.ESV-R4-0ub ISC DHCP server (transitional package) ii dnsmasq-base 2.59-4 Small caching DNS proxy and DHCP/TFTP server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/992411/+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 992411] Re: network-manager: Please don't Depend on dnsmasq-base
Hi, if network-manager don't install with dnsmasq-base the wifi hotspot feature won't work. Agreed that it should drop to recommends but it shouldn't be removed -- 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/992411 Title: network-manager: Please don't Depend on dnsmasq-base Status in network-manager package in Ubuntu: Triaged Bug description: dnsmasq in not required... Furthermore because you are over writing the Systems Administrators dhcp setting you have now made it a requirement to edit configurations on every dhcp client. cp@io:~$ dpkg -l dnsmasq-base bind9 dhcp3-server Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name VersionDescription +++-==-==- ii bind9 1:9.8.1.dfsg.P Internet Domain Name Server ii dhcp3-server 4.1.ESV-R4-0ub ISC DHCP server (transitional package) ii dnsmasq-base 2.59-4 Small caching DNS proxy and DHCP/TFTP server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/992411/+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 1516025] [NEW] Realtek ALC3661 Alienware14 / Soundoutput / Jack
You have been subscribed to a public bug: When watching the following video (but also audio from other programs) with the volume at 100%, the audio loudness is lower in comparison to the same audio being played at 100% in Windows 10: https://www.youtube.com/watch?v=YQHsXMglC9A ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-18-generic 4.2.0-18.22 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: imran 1619 F pulseaudio /dev/snd/controlC1: imran 1619 F pulseaudio CurrentDesktop: Unity Date: Fri Nov 13 18:08:07 2015 HibernationDevice: RESUME=UUID=2401d43e-85ec-4c88-81c1-c597086504a1 InstallationDate: Installed on 2015-11-07 (5 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Alienware Alienware 14 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic root=UUID=a534221a-37cb-4092-8ce2-934940eede6d ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.2.0-18-generic N/A linux-backports-modules-4.2.0-18-generic N/A linux-firmware1.149.1 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2014 dmi.bios.vendor: Alienware dmi.bios.version: A09 dmi.board.name: 07MJ2Y dmi.board.vendor: Alienware dmi.board.version: A01 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A09 dmi.modalias: dmi:bvnAlienware:bvrA09:bd04/23/2014:svnAlienware:pnAlienware14:pvrA09:rvnAlienware:rn07MJ2Y:rvrA01:cvnAlienware:ct8:cvrA09: dmi.product.name: Alienware 14 dmi.product.version: A09 dmi.sys.vendor: Alienware ** Affects: alsa-driver Importance: Unknown Status: Unknown ** Affects: pulseaudio (Ubuntu) Importance: Unknown Status: Unknown ** Affects: linux (Ubuntu) Importance: Medium Status: Confirmed ** Tags: amd64 apport-bug kernel-bug-exists-upstream latest-bios-a09 xenial yakkety -- Realtek ALC3661 Alienware14 / Soundoutput / Jack https://bugs.launchpad.net/bugs/1516025 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. -- 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 1678604] Re: package python3 3.5.1-3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 127
*** This bug is a duplicate of bug 1605657 *** https://bugs.launchpad.net/bugs/1605657 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 #1605657, 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. ** Tags removed: need-duplicate-check ** This bug has been marked a duplicate of bug 1605657 package python3 3.5.1-3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 127 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1678604 Title: package python3 3.5.1-3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 127 Status in python3-defaults package in Ubuntu: New Bug description: afer removing python2.7 and installing python3 and making /usr/bin/python soft link from /usr/bin/python3 i am receiving this error. Please suggest ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python3 3.5.1-3 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Sun Apr 2 17:25:22 2017 DuplicateSignature: package:python3:3.5.1-3 Removing python3 (3.5.1-3) ... /var/lib/dpkg/info/python3.prerm: 5: /var/lib/dpkg/info/python3.prerm: py3clean: not found dpkg: error processing package python3 (--remove): subprocess installed pre-removal script returned error exit status 127 ErrorMessage: subprocess installed pre-removal script returned error exit status 127 InstallationDate: Installed on 2016-06-23 (282 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.20 SourcePackage: python3-defaults Title: package python3 3.5.1-3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1678604/+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 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable
** Changed in: aptdaemon (Ubuntu) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/349469 Title: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable Status in Ambasa: New Status in Debconf: New Status in aptdaemon package in Ubuntu: Triaged Status in debconf package in Ubuntu: Triaged Bug description: Upgrading packages that use debconf sometimes fail with the following error: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/ambasa/+bug/349469/+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 1678604] [NEW] package python3 3.5.1-3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 127
*** This bug is a duplicate of bug 1605657 *** https://bugs.launchpad.net/bugs/1605657 Public bug reported: afer removing python2.7 and installing python3 and making /usr/bin/python soft link from /usr/bin/python3 i am receiving this error. Please suggest ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python3 3.5.1-3 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Sun Apr 2 17:25:22 2017 DuplicateSignature: package:python3:3.5.1-3 Removing python3 (3.5.1-3) ... /var/lib/dpkg/info/python3.prerm: 5: /var/lib/dpkg/info/python3.prerm: py3clean: not found dpkg: error processing package python3 (--remove): subprocess installed pre-removal script returned error exit status 127 ErrorMessage: subprocess installed pre-removal script returned error exit status 127 InstallationDate: Installed on 2016-06-23 (282 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.20 SourcePackage: python3-defaults Title: package python3 3.5.1-3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: python3-defaults (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1678604 Title: package python3 3.5.1-3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 127 Status in python3-defaults package in Ubuntu: New Bug description: afer removing python2.7 and installing python3 and making /usr/bin/python soft link from /usr/bin/python3 i am receiving this error. Please suggest ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python3 3.5.1-3 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Sun Apr 2 17:25:22 2017 DuplicateSignature: package:python3:3.5.1-3 Removing python3 (3.5.1-3) ... /var/lib/dpkg/info/python3.prerm: 5: /var/lib/dpkg/info/python3.prerm: py3clean: not found dpkg: error processing package python3 (--remove): subprocess installed pre-removal script returned error exit status 127 ErrorMessage: subprocess installed pre-removal script returned error exit status 127 InstallationDate: Installed on 2016-06-23 (282 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.20 SourcePackage: python3-defaults Title: package python3 3.5.1-3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1678604/+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 1543179] Re: Audio does not get routed to BT headset/speaker
I bought a JBL GO speaker. On my bq Aquaris E5 HD Ubuntu Edition (Ubuntu 15.04 OTA-15) I can connect to the speaker, but the sound is not working. The media player is not playing any mp3 (after pressing the play button, the time counter does not increment). After discnectig from the speaker (turn off speaker, or turn of bluetooh or disconect in bluetooth settings) the phone says it is still connected to headset (in sound indicator) and you can not turn off bluetooth after that (after returning to bluetooth indicator, or bluetooth setting it is still switched on). The only way is to restart the phone. But that is tricky too. You pres restart, and the phone goes black and nothing happens. You can not even turn it on normally. You have to hard-reset it (volume up + on switch). -- 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/1543179 Title: Audio does not get routed to BT headset/speaker Status in Canonical System Image: In Progress Status in bluez package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Confirmed Bug description: STEPS: 1. Flash the latest daily rc-proposed image to a phone 2. Connect a bluetooth headset to the phone 3. Connect a speaker to the phone. EXPECTED: I expect the devices to connect and play audio ACTUAL: Speakers just connect and instantly disconnect Headsets don't get trusted and disconnect instantly, Once you trust it and then turn the headset off and back on again it connect can accept calls but the audio from both the mic and earpiece don't function. Image: 242 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1543179/+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 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec
konstantinos: in official updates the keyboard stop working after 4.8.22 kernel. It is the latest which works fine in Ubuntu. With kernels 4.9 or newer I know it works in Fedora. You can choose the kernel in grub menu. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E200HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1563110/+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
** Description changed: 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. + Update: I tested different Kernel versions in the last days. So far + there were no issues with suspend/resume using Kernel 4.8 and 4.9. The + problem is present in 4.10 and 4.11. + 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 + 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 ** Summary changed: - Suspend - Freezing of tasks failed + Kernel 4.10+ regression: Suspend - Freezing of tasks failed -- 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: Kernel 4.10+ regression: 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. Update: I tested different Kernel versions in the last days. So far there were no issues with suspend/resume using Kernel 4.8 and 4.9. The problem is present in 4.10 and 4.11. 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
[Touch-packages] [Bug 1676918] Re: Kernel 4.10+ regression: blackscreen when trying to resume from suspend
** Summary changed: - blackscreen when trying to resume from suspend + Kernel 4.10+ regression: blackscreen when trying to resume from suspend ** Description changed: 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 + + Update: So far I did not encounter any issues with suspend/resume with + Kernel 4.8 and 4.9. This seems to be a regression in 4.10. --- 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 -- 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: Kernel 4.10+ regression: blackscreen when trying to resume from suspend Status in gnome-power-manager package in Ubuntu: New Status in linux package in Ubuntu: Confirmed 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 Update: So far I did not encounter any issues with suspend/resume with Kernel 4.8 and 4.9. This seems to be a regression in 4.10. --- 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 1515513] Re: /boot/initrd.img-*.old-dkms files left behind
** Also affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New -- 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/1515513 Title: /boot/initrd.img-*.old-dkms files left behind Status in dkms package in Ubuntu: Confirmed Status in initramfs-tools package in Ubuntu: New Status in dkms package in Debian: New Bug description: One notices *.old-dkms files being left behind still sitting on the disk after purging the related kernel. This can cause /boot to become full, and when it gets really bad, even sudo apt-get autoremove won't fix the problem - only deleting the old-dkms files manually solves the problem. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: dkms 2.2.0.3-2ubuntu3.3 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.7 Architecture: amd64 CurrentDesktop: KDE Date: Thu Nov 12 08:17:10 2015 InstallationDate: Installed on 2015-05-05 (190 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: dkms UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1515513/+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